Database Develop

[Q][Solved] Cannot update to 4.2 - assert failed: apply_patch_check...

Hi,
I tried to update to Android 4.2 (from 4.1.2) today, but it failed at the stock recovery saying:
[..]
assert failed: apply_patch_check("/system/app/Books.apk", ........
Installation aborted.
Screenshot: https://www.dropbox.com/s/b8lk0n147cbcfuv/20121114_121646_4_bestshot.jpg
Using Titanium Backup I used to make Google Books a Userland application and uninstalled it a while ago, because I wanted to remove some bloatware. I installed the backup I had and made it a system-application again, but its still giving me that error. Even factory reset didnt help.
What options do I have? How can I flash the full image?
Kind regards
Alex

Nevermind, I found the factory image at
https://developers.google.com/android/nexus/images#nakasijop40c
Downloaded it, did a titanium backup, flashed image via flash-all.bat, restored root, restored backup and 4.2 with root is all up and running now.

Same problem with apply_patch_check error bij update.
Also try to flash full factory image 4.2 by fastboot.
After install and reboot, Google icon in screen, doesn't startup.
That 5x but no success.
Same install with factory image 4.1.2 and no problem.
Help!
---------- Post added at 01:10 PM ---------- Previous post was at 01:02 PM ----------
Hello Alex,
You said, flashed bij Flash-all.bat.
How does that work? You may have a brief description of how you do it?
Thank you!

In the .zip you downloaded, there is a file called flash-all.bat. For example it does this for the WiFi version:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.13.img
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jop40c.zip
echo Press any key to exit...
pause >nul
exit
Check your version an run it in platform-tools with all content beeing there of course. Its quite easy

You sense about PATH I do not understand.
The rest I have indeed done in cmd
I have indeed PlatformTools and I have all five files in that folder.
Same folder where adb.exe also capable.
I've done in cmd in the platformtools path:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.13.img
fastboot reboot-bootloader
fastboot -w update image-nakasi-jop40c.zip
Then start the nexus7 but remains on the startup screen on the google logo.
Am I forgetting something?

whats the output of the fastboot commands from above?

I have the same problem but with GooglePinyinime.apk.
Have just worked out how to sideload using adb and am getting stuck on this error.
I did freeze this app using titanium pro, then unfroze it when I upgraded to 4.1.2 ota successfully, so can't understand why its pulling up an error now?
Am a bit of a noob with these commands so would be very grateful for any help.
Am on stock rom, rooted and no custom recovery.
Thanks.
Sent from my Nexus 7 using Tapatalk 2

simacca said:
I have the same problem but with GooglePinyinime.apk.
Have just worked out how to sideload using adb and am getting stuck on this error.
I did freeze this app using titanium pro, then unfroze it when I upgraded to 4.1.2 ota successfully, so can't understand why its pulling up an error now?
Am a bit of a noob with these commands so would be very grateful for any help.
Am on stock rom, rooted and no custom recovery.
Thanks.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Do you have fastboot installed on your computer? I am not in front of my development computer so I can't give you specific details but I had a several modifications to /system so I didn't bother trying to reverse them and instead flashed the original 4.1.2 system.img.
The (rough) procedure for this is:
1. Backup your current 4.1.2 rom in case you can't live with 4.2
2. Plug the nexus into your computer and boot into the bootloader (up vol + down vol + power)
3. On your computer, download the 4.1.2 factory image from https://dl.google.com/dl/android/aosp/nakasi-jzo54k-factory-973f190e.tgz
4. Unzip the image and then unzip the zip file that was inside the image (I can't remember the name but I believe there is only one)
5. If you unzipped everything correctly you should have a system.img file, open a command window and navigate to the directory that contains the system.img file and type:
Code:
fastboot flash system system.img
Sorry I don't have the specific details. If no one else has filled in the missing file names by the time I get home and you are comfortable with this procedure I will update this with the proper names.

C:\android-sdk-windows\platform-tools>fastboot flash bootloader bootloader-group
er-4.13.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.290s]
writing 'bootloader'...
OKAY [ 1.252s]
finished. total time: 1.548s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.022s
C:\android-sdk-windows\platform-tools>fastboot -w update image-nakasi-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.13
Baseband Version.....: N/A
Serial Number........: 015d2578a3140811
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.018s]
sending 'boot' (4942 KB)...
OKAY [ 0.599s]
writing 'boot'...
OKAY [ 0.405s]
sending 'recovery' (5444 KB)...
OKAY [ 0.660s]
writing 'recovery'...
OKAY [ 0.348s]
erasing 'system'...
OKAY [ 0.155s]
sending 'system' (477136 KB)...
OKAY [ 60.010s]
writing 'system'...
OKAY [ 23.794s]
erasing 'userdata'...
OKAY [ 1.092s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 27.895s]
erasing 'cache'...
OKAY [ 0.119s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 1.940s]
rebooting...
finished. total time: 117.197s
C:\android-sdk-windows\platform-tools>

Nexus root toolkit works
Nexus root toolkit works like a champ for restoring stock if you need it.
Works flawlessly in windows 7 for me.
http://www.wugfresh.com/nrt/
The real issue with the the assert errors is that you changed something you should not have. The 4.2 update hash checks the original system apps for consistency. If you changed any of the System apps outside of an official update you get the assert errors when trying to flash the new update.

Have the same problem...
[..]
assert failed: apply_patch_check("/system/app/Books.apk", ........
Installation aborted.
Anyone manage ti fix it without restoring original rom would be nice....

alex2308 said:
Nevermind, I found the factory image at
https://developers.google.com/android/nexus/images#nakasijop40c
Downloaded it, did a titanium backup, flashed image via flash-all.bat, restored root, restored backup and 4.2 with root is all up and running now.
Click to expand...
Click to collapse
Hi Alex,
Did flashed factory image returned our Nexus like a new phone or just restoring system files? I want to flash factory image but afraid if it's like a factory reset

everyday_ said:
Hi Alex,
Did flashed factory image returned our Nexus like a new phone or just restoring system files? I want to flash factory image but afraid if it's like a factory reset
Click to expand...
Click to collapse
Its like a full factory reset, everything is gone (also the /sdcard folder with the downloads and stuff). Restoring was pretty easy, I copied the /sdcard stuff via USB to my computer and used titanium backup to backup the apps with settings (and copied that too to my computer). The only thing I had to setup again was WiFi, Homescreen and Email (although you can backup them via Titanium, which I didnt).

Mathijs17 said:
C:\android-sdk-windows\platform-tools>fastboot flash bootloader bootloader-group
er-4.13.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.290s]
writing 'bootloader'...
OKAY [ 1.252s]
finished. total time: 1.548s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.022s
C:\android-sdk-windows\platform-tools>fastboot -w update image-nakasi-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.13
Baseband Version.....: N/A
Serial Number........: 015d2578a3140811
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.018s]
sending 'boot' (4942 KB)...
OKAY [ 0.599s]
writing 'boot'...
OKAY [ 0.405s]
sending 'recovery' (5444 KB)...
OKAY [ 0.660s]
writing 'recovery'...
OKAY [ 0.348s]
erasing 'system'...
OKAY [ 0.155s]
sending 'system' (477136 KB)...
OKAY [ 60.010s]
writing 'system'...
OKAY [ 23.794s]
erasing 'userdata'...
OKAY [ 1.092s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 27.895s]
erasing 'cache'...
OKAY [ 0.119s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 1.940s]
rebooting...
finished. total time: 117.197s
C:\android-sdk-windows\platform-tools>
Click to expand...
Click to collapse
Did you do a erase or just flash over them?

[Q] Blank phone?

So I did a major mistake here. I had the liquid rom but it was so glitchy and all that nothin worked. so then i went to my cwm 6.0.2.8 recovery to delete cache and wipe data to flash the new rom but then it turns out the new rom I wanted to flash was incomplete and now my phone is completely blank now. Oh i am unlocked bootloader too. please help me guys! plus i now have a problem that it says (internal sd card) E: cant mount /sdcard/ and also android_secure is gone. I was able to flash a rom within my sdcard but it gets into a bootloop and wont boot up since of the internal sd card error.

wadamean said:
So I did a major mistake here. I had the liquid rom but it was so glitchy and all that nothin worked. so then i went to my cwm 6.0.2.8 recovery to delete cache and wipe data to flash the new rom but then it turns out the new rom I wanted to flash was incomplete and now my phone is completely blank now. Oh i am unlocked bootloader too. please help me guys! plus i now have a problem that it says (internal sd card) E: cant mount /sdcard/ and also android_secure is gone. I was able to flash a rom within my sdcard but it gets into a bootloop and wont boot up since of the internal sd card error.
Click to expand...
Click to collapse
I've been in the situation a couple of times all you need to do is fastboot flash back to stock using skeevydudes tutorial under general or use rsd lite

I will surely try that. I cant use rsd since i have mac though.

help
frog1982 said:
I've been in the situation a couple of times all you need to do is fastboot flash back to stock using skeevydudes tutorial under general or use rsd lite
Click to expand...
Click to collapse
plus can u post the link to the guide and please to which exact stock rom i need for my unlocked bootlaoder. thanks so much.

wadamean said:
plus can u post the link to the guide and please to which exact stock rom i need for my unlocked bootlaoder. thanks so much.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2226527
There is a section for going back to stock jelly bean with links to the different firmwares. I would suggest mexico retail it is the most bug free and has very little bloat. But if you've never read this post by skeevydude I was just read the whole initial post because it is extremely good to know all this information so that way you can fix anything that goes wrong software wise with your phone. If you have a more questions about it just let me know. Also there is a small section on how to regain root after you do this but your unlocked boot loader will not be affected.

frog1982 said:
http://forum.xda-developers.com/showthread.php?t=2226527
There is a section for going back to stock jelly bean with links to the different firmwares. I would suggest mexico retail it is the most bug free and has very little bloat. But if you've never read this post by skeevydude I was just read the whole initial post because it is extremely good to know all this information so that way you can fix anything that goes wrong software wise with your phone. If you have a more questions about it just let me know. Also there is a small section on how to regain root after you do this but your unlocked boot loader will not be affected.
Click to expand...
Click to collapse
For the /data wipe (not necessary for switching ROMs, just /system and factory reset) you need to fastboot to stock. Checked out that link, and I don't believe that is for fastbooting. That's for flashing a stock ROM via CWM, which won't do anything for you. You need to fastboot a real stock ROM (from the android sbf site) to fix this. And I would recommend flashing manually because I haven't used RSD and Myth always gave me problems.
Sent from my MB886 using xda app-developers app
EDIT: Took a sip of coffee, reskimmed that thread and it's the right one. My bad.

can I have step by step instructions? and the exact file i need. thanks a bunch!

wadamean said:
can I have step by step instructions? and the exact file i need. thanks a bunch!
Click to expand...
Click to collapse
Step by step instructions are located in the link.

instructions please
penser said:
For the /data wipe (not necessary for switching ROMs, just /system and factory reset) you need to fastboot to stock. Checked out that link, and I don't believe that is for fastbooting. That's for flashing a stock ROM via CWM, which won't do anything for you. You need to fastboot a real stock ROM (from the android sbf site) to fix this. And I would recommend flashing manually because I haven't used RSD and Myth always gave me problems.
Sent from my MB886 using xda app-developers app
EDIT: Took a sip of coffee, reskimmed that thread and it's the right one. My bad.
Click to expand...
Click to collapse
can I have step by step instructions? and the exact file i need. thanks a bunch!

ohhhh
frog1982 said:
Step by step instructions are located in the link.
Click to expand...
Click to collapse
where exactly? i cant seem to find them. and which file do i need to fastboot to stock?
i have the MX retail one zip file.

wadamean said:
where exactly? i cant seem to find them. and which file do i need to fastboot to stock?
i have the MX retail one zip file.
Click to expand...
Click to collapse
unzip the file, download the snapdragon fastboot file and put it in the same folder as the unzipped Mex retail then run these fastboot commands while the phone is hooked up to the computer and fastboot mode
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot -w
fastboot reboot

FAiled
frog1982 said:
unzip the file, download the snapdragon fastboot file and put it in the same folder as the unzipped Mex retail then run these fastboot commands while the phone is hooked up to the computer and fastboot mode
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
Last login: Fri Aug 16 04:43:13 on ttys000
-bash: sdkfolder: No such file or directory
Hector-Garnicas-iMac:~ hectorgarnica$ cd /Users/hectorgarnica/Atrix\ hd/MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml
Hector-Garnicas-iMac:MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml hectorgarnica$ ./fastboot devices
-bash: ./fastboot: No such file or directory
Hector-Garnicas-iMac:MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml hectorgarnica$ cd /Users/hectorgarnica/adt-bundle-mac/sdk/tools Hector-Garnicas-iMac:tools hectorgarnica$ ./fastboot devices
TA300036RY fastboot
Hector-Garnicas-iMac:tools hectorgarnica$ ./fastboot flash boot /Users/hectorgarnica/adt-bundle-mac/sdk/tools/MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml/boot.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.800s]
writing 'boot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 1.057s
Hector-Garnicas-iMac:tools hectorgarnica$ ./fastboot flash /Users/hectorgarnica/adt-bundle-mac/sdk/tools/MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml/device_tree.bin
unknown partition '/Users/hectorgarnica/adt-bundle-mac/sdk/tools/MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml/device_tree.bin'
error: cannot determine image filename for '/Users/hectorgarnica/adt-bundle-mac/sdk/tools/MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml/device_tree.bin'
Hector-Garnicas-iMac:tools hectorgarnica$ ./fastboot flash devtree device_tree.bin
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'devtree' (512 KB)...
OKAY [ 0.047s]
writing 'devtree'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.300s
Hector-Garnicas-iMac:tools hectorgarnica$ ./fastboot flash system /Users/hectorgarnica/adt-bundle-mac/sdk/tools/MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml/system.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 517990560 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 486529184 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 455063712 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 423610528 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 392153248 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 360532128 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 329078944 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 297834656 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 266279072 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 236382368 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 204929184 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 173467808 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 142014624 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 111741088 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 81475744 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 50006176 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 18520224 is not a multiple of the block size 4096
sending sparse 'system' (30716 KB)...
error: write_sparse_skip_chunk: don't care size 517990560 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 517990560 is not a multiple of the block size 4096
OKAY [ 2.865s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 3.122s
Hector-Garnicas-iMac:tools hectorgarnica$ ./fastboot -w
erasing 'userdata'...
OKAY [ 2.347s]
formatting 'userdata' partition...
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
OKAY [ 0.106s]
erasing 'cache'...
OKAY [ 1.321s]
formatting 'cache' partition...
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
OKAY [ 0.105s]
finished. total time: 3.879s
Hector-Garnicas-iMac:tools hectorgarnica$ ./fastboot reboot
rebooting...
finished. total time: 0.006s
Hector-Garnicas-iMac:tools hectorgarnica$
what i kept getting failed. i did all step by step.

wadamean said:
Last login: Fri Aug 16 04:43:13 on ttys000
-bash: sdkfolder: No such file or directory
Hector-Garnicas-iMac:~ hectorgarnica$ cd /Users/hectorgarnica/Atrix\ hd/MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml
Hector-Garnicas-iMac:MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml hectorgarnica$ ./fastboot devices
-bash: ./fastboot: No such file or directory
Hector-Garnicas-iMac:MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml hectorgarnica$ cd /Users/hectorgarnica/adt-bundle-mac/sdk/tools Hector-Garnicas-iMac:tools hectorgarnica$ ./fastboot devices
TA300036RY fastboot
Hector-Garnicas-iMac:tools hectorgarnica$ ./fastboot flash boot /Users/hectorgarnica/adt-bundle-mac/sdk/tools/MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml/boot.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.800s]
writing 'boot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 1.057s
Hector-Garnicas-iMac:tools hectorgarnica$ ./fastboot flash /Users/hectorgarnica/adt-bundle-mac/sdk/tools/MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml/device_tree.bin
unknown partition '/Users/hectorgarnica/adt-bundle-mac/sdk/tools/MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml/device_tree.bin'
error: cannot determine image filename for '/Users/hectorgarnica/adt-bundle-mac/sdk/tools/MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml/device_tree.bin'
Hector-Garnicas-iMac:tools hectorgarnica$ ./fastboot flash devtree device_tree.bin
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'devtree' (512 KB)...
OKAY [ 0.047s]
writing 'devtree'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.300s
Hector-Garnicas-iMac:tools hectorgarnica$ ./fastboot flash system /Users/hectorgarnica/adt-bundle-mac/sdk/tools/MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml/system.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 517990560 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 486529184 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 455063712 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 423610528 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 392153248 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 360532128 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 329078944 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 297834656 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 266279072 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 236382368 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 204929184 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 173467808 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 142014624 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 111741088 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 81475744 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 50006176 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 18520224 is not a multiple of the block size 4096
sending sparse 'system' (30716 KB)...
error: write_sparse_skip_chunk: don't care size 517990560 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 517990560 is not a multiple of the block size 4096
OKAY [ 2.865s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 3.122s
Hector-Garnicas-iMac:tools hectorgarnica$ ./fastboot -w
erasing 'userdata'...
OKAY [ 2.347s]
formatting 'userdata' partition...
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
OKAY [ 0.106s]
erasing 'cache'...
OKAY [ 1.321s]
formatting 'cache' partition...
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
OKAY [ 0.105s]
finished. total time: 3.879s
Hector-Garnicas-iMac:tools hectorgarnica$ ./fastboot reboot
rebooting...
finished. total time: 0.006s
Hector-Garnicas-iMac:tools hectorgarnica$
what i kept getting failed. i did all step by step.
Click to expand...
Click to collapse
did you download the snapdragon fastboot file from the link and place it in the folder as the unzipped stock file

frog1982 said:
did you download the snapdragon fastboot file from the link and place it in the folder as the unzipped stock file
Click to expand...
Click to collapse
yes i did

frog1982 said:
did you download the snapdragon fastboot file from the link and place it in the folder as the unzipped stock file
Click to expand...
Click to collapse
unless i have the wrong file. i have had it from a long while ago plus the link doesnt provide it. i loooked.

wadamean said:
unless i have the wrong file. i have had it from a long while ago plus the link doesnt provide it. i loooked.
Click to expand...
Click to collapse
Don't use the stock\SDK fastboot binary for flashing /
system.
An updated fastboot binary for Lin\Win\Mac can be found here on
the Batakang FTP from our local, neighborhood Mattlgroff.
Linux -- Rename the file to moto-fastboot and add it to a directory
in your $PATH -- Ubuntu\Debian users can just add it to ~/bin
(enabled by default)
Windows -- Rename the file to moto-fastboot and put it somewhere
handy...that's on you to decide.
that is second paragraph in the link and I double checked the link it is active.
when you download it there will be three folders just copy the files from the Mac folder and put them in your Mex retail file then everything should work fine.
let me know how it goes.
PS I keep this file setup on both my Linux and windows so that at anytime I can fix my phone and suggest that everybody who is flashaholic or developer do the same.

frog1982 said:
Don't use the stock\SDK fastboot binary for flashing /
system.
An updated fastboot binary for Lin\Win\Mac can be found here on
the Batakang FTP from our local, neighborhood Mattlgroff.
Linux -- Rename the file to moto-fastboot and add it to a directory
in your $PATH -- Ubuntu\Debian users can just add it to ~/bin
(enabled by default)
Windows -- Rename the file to moto-fastboot and put it somewhere
handy...that's on you to decide.
that is second paragraph in the link and I double checked the link it is active.
when you download it there will be three folders just copy the files from the Mac folder and put them in your Mex retail file then everything should work fine.
let me know how it goes.
PS I keep this file setup on both my Linux and windows so that at anytime I can fix my phone and suggest that everybody who is flashaholic or developer do the same.
Click to expand...
Click to collapse
ima try it and let you know

frog1982 said:
Don't use the stock\SDK fastboot binary for flashing /
system.
An updated fastboot binary for Lin\Win\Mac can be found here on
the Batakang FTP from our local, neighborhood Mattlgroff.
Linux -- Rename the file to moto-fastboot and add it to a directory
in your $PATH -- Ubuntu\Debian users can just add it to ~/bin
(enabled by default)
Windows -- Rename the file to moto-fastboot and put it somewhere
handy...that's on you to decide.
that is second paragraph in the link and I double checked the link it is active.
when you download it there will be three folders just copy the files from the Mac folder and put them in your Mex retail file then everything should work fine.
let me know how it goes.
PS I keep this file setup on both my Linux and windows so that at anytime I can fix my phone and suggest that everybody who is flashaholic or developer do the same.
Click to expand...
Click to collapse
i still keep getting the failed (remote failure)

wadamean said:
i still keep getting the failed (remote failure)
Click to expand...
Click to collapse
are you putting your phone into ap fastboot first
also does mac have any kind sudo, superuser or admin mode that you can try it in.

Yes of course I go to ap fastboot mode first prior to hooking it up to my mac and starting the process. And idk about the sudo or superuser but I'm sure there is administrator stuff for the mac
Sent from my Droid using xda app-developers app

[Q] Auto-update (4.4.2- 11.4.1.27) -> black screen

Hello, (I apologize for my bad english)
Since one week with the update 4.4.2-11.4.1.27 I've got a problem with "black screen". Indeed I need to get lucky with the power button to wake up the screen.
I try lots of things but it was hard to install a new rom without seeing the recovery.
So I tried to use fastboot instead of the recovery.
In first, I tried this :
fastboot erase system -w
fastboot erase boot
fastboot update [CROMi-X 7.0.3][11.4.1.17].zip
but it doesn't work, I had this message :
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Then, I tried this :
fastboot erase system -w
fastboot erase boot
fastboot -i 0x0B05 flash boot boot.img
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 flash system UL-K00C-WW-11.4.1.17-user.zip
And it failed again :'( with this error text :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash system
UL-K00C-WW-11.4.1.17-user.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 345823125 is not a multiple of
he block size 4096
erasing 'system'...
OKAY [ 1.227s]
sending sparse 'system' (602018 KB)...
error: write_sparse_skip_chunk: don't care size 345823125 is not a multiple of
he block size 4096
error: write_sparse_skip_chunk: don't care size 345823125 is not a multiple of
he block size 4096
OKAY [ 81.624s]
writing 'system'...
OKAY [ 17.300s]
sending sparse 'system' (337720 KB)...
OKAY [ 45.821s]
writing 'system'...
OKAY [ 9.322s]
finished. total time: 155.295s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Thank you for helping me, I don't understand where is the mistake....

How could I recovery my Nexus 6

Hi,
I was trying to update my Nexus 6 to Android Nougat(nbd90z) today, the system image failed to be flashed. And then I locked the device by mistake. Then I became unable to flash any images.
If I tried to flash any image, it failed and the message is below.
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
If I tried to unlock the device, it failed and the message is below.
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
And because the system image failed to flash, so I can't boot the device to check the 'Allow OEM Unlock'.
Is there any way to recovery my device? Thanks very much for the help.

Below is the text from the command terminal where I tried.
<pre>
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.528s]
finished. total time: 0.657s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.617s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.609s]
finished. total time: 5.226s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 28474998784
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6951904
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
--------------------------------------------
Bootloader Version...: moto-apq8084-71.21
Baseband Version.....: D4.01-9625-05.42+FSG-9625-02.113
Serial Number........: ZX1G22H7C4
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (8535 KB)...
OKAY [ 0.269s]
writing 'boot'...
OKAY [ 0.161s]
sending 'recovery' (13921 KB)...
OKAY [ 0.439s]
writing 'recovery'...
OKAY [ 0.208s]
sending sparse 'system' (508909 KB)...
OKAY [ 16.031s]
writing 'system'...
OKAY [ 7.247s]
sending sparse 'system' (524036 KB)...
FAILED (status read failed (Protocol error))
finished. total time: 28.751s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot devices
ZX1G22H7C4 fastboot
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot oem lock
...
^C
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot oem lock
...
(bootloader) Device state transition will erase userdata.
(bootloader) Are you sure you want to continue this transition?
(bootloader)
(bootloader) Press POWER key to continue.
(bootloader) Press VOL UP or VOL DOWN key to cancel state transition.
(bootloader) State transition confirmed!
(bootloader) Phone is locked successfully!
OKAY [ 24.319s]
finished. total time: 24.319s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ls
bootloader-shamu-moto-apq8084-71.21.img flash-all.bat flash-all.sh flash-base.sh image-shamu-nbd90z.zip radio-shamu-d4.01-9625-05.42+fsg-9625-02.113.img
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.132s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.617s]
writing 'radio'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 3.622s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 28474998784
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6951904
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
--------------------------------------------
Bootloader Version...: moto-apq8084-71.21
Baseband Version.....: D4.01-9625-05.42+FSG-9625-02.113
Serial Number........: ZX1G22H7C4
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (8535 KB)...
OKAY [ 0.269s]
writing 'boot'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.288s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ls
bootloader-shamu-moto-apq8084-71.21.img flash-all.bat flash-all.sh flash-base.sh image-shamu-nbd90z.zip radio-shamu-d4.01-9625-05.42+fsg-9625-02.113.img
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ geany flash-base.sh
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ./flash-base.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.132s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.617s]
writing 'radio'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 3.622s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot oem
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot oem --help
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.001s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot reboot
rebooting...
finished. total time: 0.151s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ls
bootloader-shamu-moto-apq8084-71.21.img flash-all.bat flash-all.sh flash-base.sh image-shamu-nbd90z.zip radio-shamu-d4.01-9625-05.42+fsg-9625-02.113.img
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot flash radio radio-shamu-d4.01-9625-05.42+fsg-9625-02.113.img
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.617s]
writing 'radio'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 3.622s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot devices
ZX1G22H7C4 fastboot
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ cd /home/zhiming/Project/Nexus/Images/shamu-mob31e/
[email protected]:~/Project/Nexus/Images/shamu-mob31e$ ls
bootloader-shamu-moto-apq8084-71.18.img flash-all.bat flash-all.sh flash-base.sh image-shamu-mob31e.zip radio-shamu-d4.01-9625-05.34+fsg-9625-02.111.img
[email protected]:~/Project/Nexus/Images/shamu-mob31e$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.327s]
writing 'bootloader'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.332s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
sending 'radio' (115508 KB)...
OKAY [ 3.617s]
writing 'radio'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 3.622s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 28474998784
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6951904
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
--------------------------------------------
Bootloader Version...: moto-apq8084-71.21
Baseband Version.....: D4.01-9625-05.42+FSG-9625-02.113
Serial Number........: ZX1G22H7C4
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'moto-apq8084-71.21'.
Update requires 'moto-apq8084-71.18'.
finished. total time: 2.498s
[email protected]:~/Project/Nexus/Images/shamu-mob31e$ cd /home/zhiming/Project/Nexus/Images/shamu-nbd90z/
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ls
bootloader-shamu-moto-apq8084-71.21.img flash-all.bat flash-all.sh flash-base.sh image-shamu-nbd90z.zip radio-shamu-d4.01-9625-05.42+fsg-9625-02.113.img
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ./flash-base.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.135s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.113s
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.617s]
writing 'radio'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 3.622s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.001s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$
</pre>

ZhimingWU said:
Is there any way to recovery my device? Thanks very much for the help.
Click to expand...
Click to collapse
Flash an OTA image. They're intended to be flashed even on locked systems.

Strephon Alkhalikoi said:
Flash an OTA image. They're intended to be flashed even on locked systems.
Click to expand...
Click to collapse
Thank you for the reply. Does flashing OTA images needs to boot system normally? My phone is unable to boot system normally due to failure of flashing system image.

Strephon Alkhalikoi, thank you very much. I got my device recovered.
I followed the instructions at https://developers.google.com/android/nexus/ota, except replacing Step 3 by below steps to boot into recovery mode.
a. Hold Volume Down key and press Power key to enter fastboot mode.
b. Press Volume Down key to navigate to "Recovery mode" and press Power key.

ZhimingWU said:
Thank you for the reply. Does flashing OTA images needs to boot system normally? My phone is unable to boot system normally due to failure of flashing system image.
Click to expand...
Click to collapse
Do you have recovery installed?
If yes and hopefully TWRP which is best option, just go to recovery, mount phone, transfer OTA image, factory reset, and flash it.
Also, if upgrading from 6.x.x to 7.0.0 you must flash the Nougat bootloader img. which in order to do it, i recommand using Nexus toolkit which you could access only via phone being on.
So what i do recommand is the next thing:
download 6.x.x ota and install it.
boot into phone, unlock developer options and usb debugging, also check the "oem unlocking".
plug the phone to the pc while using an adb program like nexus tookit, unlock bootloader.
then download the Nougat bootloader img, and radio img (not a must). into the pc, and flash it via nexus root toolkit once again.
After your'e done flashing, all you have to do is go to recovery mode and flash the Nougat rom.
And before all that, make sure you have the latest TWRK recovery.

Bricked my device Need URGENT help please look at the pics posted

i accidentally flashed a wrong rom and now it is stuck in fastboot and im unable to flash recovery or system through fastboot. i will show the error i get in picture below
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.428s]
writing 'recovery'...
OKAY [ 0.256s]
finished. total time: 1.687s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (41812 KB)...
OKAY [ 0.918s]
writing 'recovery'...
OKAY [ 0.176s]
finished. total time: 1.097s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot system raphael.tgz
fastboot: usage: unknown command system
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
375d8e65 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system raphael.tgz
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 3492589356 is not a multiple of the block size 4096
erasing 'system'...
OKAY [ 0.102s]
sending sparse 'system' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 3492589356 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 3492589356 is not a multiple of the block size 4096
OKAY [ 0.021s]
writing 'system' 1/1...
OKAY [ 0.003s]
finished. total time: 0.129s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (41812 KB)...
FAILED (remote: Error: Last flash failed : Bad Buffer Size)
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.731s]
writing 'recovery'...
OKAY [ 0.250s]
finished. total time: 1.983s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system raphael.tgz
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 3492589356 is not a multiple of the block size 4096
erasing 'system'...
OKAY [ 0.025s]
sending sparse 'system' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 3492589356 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 3492589356 is not a multiple of the block size 4096
OKAY [ 0.034s]
writing 'system' 1/1...
OKAY [ 0.004s]
finished. total time: 0.124s

was trying to unbrick it by going to edl mode not working
Sending 'recovery' (65536 KB) OKAY [ 1.432s]
Writing 'recovery' OKAY [ 0.249s]
Finished. Total time: 5.519s
Sending 'boot.img' (65536 KB) OKAY [ 1.392s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
Press any key to continue . . .

Use Xiaomi Flash Tool to Flash Stock Rom for your device.
Sent from my Redmi K20 Pro using Tapatalk

@albysprx @phantomDuck @Fantomduck please help guys

@albysprx @phantomDuck @Fantomduck please help guys

Are you trying to flash system without extracting it? It's kind of confusing so correct me if I'm wrong. From what I can gather you're trying to flash system.tgz, you need to extract the fastboot rom twice until you get system.img, move that to platform tools then open cmd and type "fastboot flash system system.img"
Or better yet once fastboot rom has been extracted properly flash the full rom