I am attempting to "unroot" my phone and when i try to flash the factory image there is an error "FAILED (remote: Command Flash Error)"
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38652 KB)...
OKAY [ 0.869s]
writing 'bootloader_b'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.881s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 1.349s]
writing 'radio_b'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.543s]
finished. total time: 1.896s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.168s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.027s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1920 MB) to disk... took 10.391s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 3.813s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took -0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (345 MB) to disk... took 2.220s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 13933563 4k blocks and 3489792 inodes
Filesystem UUID: caba058e-0ebc-11e8-a919-19e9115ff992
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: HT7AC1A00496
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0067.00'.
finished. total time: 0.020s
I tried a tutorial i found online where i sideloaded a OTA with adb but that spikes an incompatibility error
"failed to verify package compatibility runtime info and framework compatibility matrix are incompatible"
I just want to factory reset it and lock the device.
IAmRoot_Console said:
I am attempting to "unroot" my phone and when i try to flash the factory image there is an error "FAILED (remote: Command Flash Error)"
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38652 KB)...
OKAY [ 0.869s]
writing 'bootloader_b'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.881s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 1.349s]
writing 'radio_b'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.543s]
finished. total time: 1.896s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.168s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.027s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1920 MB) to disk... took 10.391s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 3.813s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took -0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (345 MB) to disk... took 2.220s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 13933563 4k blocks and 3489792 inodes
Filesystem UUID: caba058e-0ebc-11e8-a919-19e9115ff992
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: HT7AC1A00496
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0067.00'.
finished. total time: 0.020s
I tried a tutorial i found online where i sideloaded a OTA with adb but that spikes an incompatibility error
"failed to verify package compatibility runtime info and framework compatibility matrix are incompatible"
I just want to factory reset it and lock the device.
Click to expand...
Click to collapse
I would first try a different USB cable then if that doesn't work try another PC. It also appears that your trying to flash the B partition and not the A partition of your device
What next
@enzyne Ok just tried a new cable and a new pc and niether did work. Also how do i flash to Partition a of the device and would the be the source of my problems? because right now i can go into recoverymode and the bootloader screen and that is it.
Not partition found?
Now when i try to flash Slot a it says "FAILED (remote: No such partition.)"
target reported max download size of 536870912 bytes
sending 'slot_a' (32768 KB)...
OKAY [ 0.735s]
writing 'slot_a'...
FAILED (remote: No such partition.)
finished. total time: 0.738s
Same on slot b could be because the same img is on there
To be clear you still have an unlocked bootloader correct? What platform tools are you using? The latest ones from google?
enzyne said:
To be clear you still have an unlocked bootloader correct? What platform tools are you using? The latest ones from google?
Click to expand...
Click to collapse
I am using the latest Platform-tools (ADB/Fastboot) tools from google and the bootloader is unlocked. My problem is that when i try to flash the factory image all it does is spit out the Command Flash Error. I got it into recovery mode by flashing boot.img to the two slots (a and b) and i tried to sideload the OTA but i got a compatibility error so now im stuck on what to do
IAmRoot_Console said:
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: HT7AC1A00496
------------------------
FAILED
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0067.00'.
Click to expand...
Click to collapse
Are you flashing an older version than what's installed on your phone?
Sent from my Pixel 2 using Tapatalk
ajrty33 said:
Are you flashing an older version than what's installed on your phone?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Now i feel like an idiot i just had to flash 8.0 and now it is working and is stock
There is another way. You can edit the checkpoint to override and flash any version of bootloader.
---------- Post added at 06:52 PM ---------- Previous post was at 06:34 PM ----------
SOLVED BY TRIAL. IN CASE ANYONE ELSE IS GETTING THE SAME ERRORS, DO THIS -->
OPEN THE image-walleye-opm1.1****.zip in winzip, winrar, 7z - and open the android-info.txt by notepad++ or noptepad and edit the "require version-bootloader=mw.8898-002.00***.*** to the one that is asked for in the cmd error log and rerun the flash-all.bat
I had Sailfish-US-PVT edition Google Pixel I tried to downgrade from Beta Android P to lower version and I faced this error through bootloop and now I am stuck. I need HELP big time. Much appreciate the help.
Code :
Code:
Sending 'bootloader_b' (32380 KB) OKAY [ 1.943s]
Writing 'bootloader_b' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 12.412s]
Finished. Total time: 14.475s
rebooting into bootloader OKAY [ 0.016s]
Finished. Total time: 0.017s
< waiting for any device >
Sending 'radio_b' (57240 KB) OKAY [ 1.950s]
Writing 'radio_b' OKAY [ 0.852s]
Finished. Total time: 2.939s
rebooting into bootloader OKAY [ 0.010s]
Finished. Total time: 0.011s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 8996-012001-1704121145
Baseband Version.....: 8996-012901-1703291803
Serial Number........: FA6AE0309571
--------------------------------------------
Checking product OKAY [ 0.050s]
Checking version-bootloader OKAY [ 0.048s]
Checking version-baseband OKAY [ 0.048s]
extracting boot.img (24 MB) to disk... took 0.237s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'recovery.img'
extracting system.img (1537 MB) to disk... took 26.129s
archive does not contain 'system.sig'
extracting system_other.img (1641 MB) to disk...W/ziparchive( 6720): Zip: unable to truncate file to 1721089412: File too large
fastboot: error:
failed to extract 'system_other.img': I/O error
Press any key to exit...
Please guide me
#NOOBQUESTIONS !
adnanjabbar said:
I had Sailfish-US-PVT edition Google Pixel I tried to downgrade from Beta Android P to lower version and I faced this error through bootloop and now I am stuck. I need HELP big time. Much appreciate the help.
Code :
Code:
Sending 'bootloader_b' (32380 KB) OKAY [ 1.943s]
Writing 'bootloader_b' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 12.412s]
Finished. Total time: 14.475s
rebooting into bootloader OKAY [ 0.016s]
Finished. Total time: 0.017s
< waiting for any device >
Sending 'radio_b' (57240 KB) OKAY [ 1.950s]
Writing 'radio_b' OKAY [ 0.852s]
Finished. Total time: 2.939s
rebooting into bootloader OKAY [ 0.010s]
Finished. Total time: 0.011s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 8996-012001-1704121145
Baseband Version.....: 8996-012901-1703291803
Serial Number........: FA6AE0309571
--------------------------------------------
Checking product OKAY [ 0.050s]
Checking version-bootloader OKAY [ 0.048s]
Checking version-baseband OKAY [ 0.048s]
extracting boot.img (24 MB) to disk... took 0.237s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'recovery.img'
extracting system.img (1537 MB) to disk... took 26.129s
archive does not contain 'system.sig'
extracting system_other.img (1641 MB) to disk...W/ziparchive( 6720): Zip: unable to truncate file to 1721089412: File too large
fastboot: error:
failed to extract 'system_other.img': I/O error
Press any key to exit...
Please guide me
#NOOBQUESTIONS !
Click to expand...
Click to collapse
I too faced this issue. I think the free memory in your hard disk is low. Try in a drive with more free memory
Hi,
at some point I messed up the flahs of LineageOS and now I would like to get back to the stock img but it does not work anymore. I tried
flash-all.bat but with the same error as shown below.
Code:
C:\Users\XXXX>fastboot flash bootloader "C:\Users\XXX\smartphone\sargo-qp1a.191105.003\bootloader-sargo-b4s4-0.2-5736883.img"
target reported max download size of 268435456 bytes
sending 'bootloader' (8349 KB)...
OKAY [ 0.279s]
writing 'bootloader'...
(bootloader) Flashing Pack version b4s4-0.2-5736883
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
OKAY [ 0.586s]
finished. total time: 0.865s
C:\Users\XXX>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\XXX>fastboot flash radio "C:\Users\XXX\smartphone\sargo-qp1a.191105.003\radio-sargo-g670-00025-190805-b-5781381.img"
target reported max download size of 268435456 bytes
sending 'radio' (73196 KB)...
OKAY [ 1.673s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g670-00025-190805-B-5781381
(bootloader) Flashing partition modem_b
OKAY [ 0.555s]
finished. total time: 2.244s
C:\Users\XXX>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.038s]
finished. total time: 0.053s
C:\Users\XXX>fastboot -w update "C:\Users\XXX\smartphone\sargo-qp1a.191105.003\image-sargo-qp1a.191105.003.zip"
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
W/ (15016): Zip: unable to truncate file to 485105848: File too large
failed to extract 'vendor.img': I/O Error
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: variable not found)
--------------------------------------------
Bootloader Version...: b4s4-0.2-5736883
Baseband Version.....: g670-00025-190805-B-5781381
Serial Number........: 97AAY1041S
--------------------------------------------
checking product...
OKAY [ 0.053s]
checking version-bootloader...
OKAY [ 0.063s]
checking version-baseband...
OKAY [ 0.069s]
sending 'boot' (65536 KB)...
OKAY [ 1.520s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.006s
Thank you in advance!
Simon
simhagen said:
Hi,
at some point I messed up the flahs of LineageOS and now I would like to get back to the stock img but it does not work anymore. I tried
flash-all.bat but with the same error as shown below.
Thank you in advance!
Simon
Click to expand...
Click to collapse
I had exactly this issue.
https://forum.xda-developers.com/pixel-3a/how-to/problem-flashing-stock-image-t3997513
You need to update adb fastboot.
Is the drive that you have the zip file saved on nearing it's storage capacity? I suspect it is.
They key line in your log is, "Zip: unable to truncate file to 485105848: File too large" You will get this file if there isn't enough room to properly unzip the file completely. It takes up a decent amount of space on the hard drive.
Horgar said:
I had exactly this issue.
https://forum.xda-developers.com/pixel-3a/how-to/problem-flashing-stock-image-t3997513
You need to update adb fastboot.
Click to expand...
Click to collapse
Ok, so far so good. I tried it on Windows with the newest version, same problem. Than I switched to Linux and it worked up to the point "Sending sparse 'vendor_b' 1/3 (262140 KB)" than it gets stuck and nothing happens.
Code:
[[email protected] MyApplication]$ sudo fastboot flash bootloader /home/XXXX/Downloads/sargo-pd2a.190115.029/bootloader-sargo-b4s4-0.1-5262905.img
Sending 'bootloader_b' (8349 KB) OKAY [ 0.340s]
Writing 'bootloader_b' (bootloader) Flashing Pack version b4s4-0.1-5262905
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
OKAY [ 0.541s]
Finished. Total time: 1.074s
[[email protected] MyApplication]$ sudo fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.015s]
Finished. Total time: 0.065s
[[email protected] MyApplication]$ sudo fastboot flash radio /home/XXXX/Downloads/sargo-pd2a.190115.029/radio-sargo-g670-00011-190213-b-5306579.img
Sending 'radio_b' (72988 KB) OKAY [ 2.230s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g670-00011-190213-B-5306579
(bootloader) Flashing partition modem_b
OKAY [ 0.880s]
Finished. Total time: 3.315s
[[email protected] MyApplication]$ sudo fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.015s]
Finished. Total time: 0.065s
[[email protected] MyApplication]$ sudo fastboot update -w /home/XXXX/Downloads/sargo-pd2a.190115.029/image-sargo-pd2a.190115.029.zip
--------------------------------------------
Bootloader Version...: b4s4-0.1-5262905
Baseband Version.....: g670-00011-190213-B-5306579
Serial Number........: xxxxxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.051s]
Checking 'version-bootloader' OKAY [ 0.052s]
Checking 'version-baseband' OKAY [ 0.052s]
Setting current slot to 'b' OKAY [ 0.063s]
extracting boot.img (64 MB) to disk... took 0.284s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 1.990s]
Writing 'boot_b' OKAY [ 0.729s]
extracting dtbo.img (8 MB) to disk... took 0.056s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.340s]
Writing 'dtbo_b' OKAY [ 0.133s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (4 KB) OKAY [ 0.120s]
Writing 'vbmeta_b' OKAY [ 0.064s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting system.img (2271 MB) to disk... took 11.015s
archive does not contain 'system.sig'
Sending sparse 'system_b' 1/9 (262140 KB) OKAY [ 7.389s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 2/9 (262140 KB) OKAY [ 7.840s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 3/9 (262140 KB) OKAY [ 7.830s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 4/9 (262140 KB) OKAY [ 7.760s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 5/9 (262140 KB) OKAY [ 7.870s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 6/9 (262140 KB) OKAY [ 7.810s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 7/9 (262140 KB) OKAY [ 7.810s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 8/9 (258620 KB) OKAY [ 7.690s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 9/9 (232288 KB) OKAY [ 7.020s]
Writing 'system_b' OKAY [ 1.920s]
archive does not contain 'system_ext.img'
extracting system_other.img (391 MB) to disk... took 1.914s
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/2 (262140 KB) OKAY [ 7.850s]
Writing 'system_a' OKAY [ 0.370s]
Sending sparse 'system_a' 2/2 (138668 KB) OKAY [ 4.200s]
Writing 'system_a' OKAY [ 1.380s]
extracting vendor.img (523 MB) to disk... took 2.502s
archive does not contain 'vendor.sig'
Sending sparse 'vendor_b' 1/3 (262140 KB)
sic0048 said:
Is the drive that you have the zip file saved on nearing it's storage capacity? I suspect it is.
They key line in your log is, "Zip: unable to truncate file to 485105848: File too large" You will get this file if there isn't enough room to properly unzip the file completely. It takes up a decent amount of space on the hard drive.
Click to expand...
Click to collapse
Should not be the issue since nothing was on the phone to begin with, other than the first running system.
My issue was resetting the path in windows.
https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
If it helps this is what I followed.
Your phone should boot into fastbootd when flashing. That's when I realised it was flashing ok.
Horgar said:
My issue was resetting the path in windows.
https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
If it helps this is what I followed.
Your phone should boot into fastbootd when flashing. That's when I realised it was flashing ok.
Click to expand...
Click to collapse
Thanks,
link does not work for me though...
simhagen said:
Should not be the issue since nothing was on the phone to begin with, other than the first running system.
Click to expand...
Click to collapse
It's not the space on the phone. You don't download and install these factory images from your phone. You have to download them to a computer and install them that way. If you computer is short on storage space, it will give the same error when it tries to upzip the factory image during the installation process. I've had it happen to me before and had to clear up space on my computer in order to finish flashing a factory image.
For example, if you have ADB installed on your C: drive and your C: drive doesn't have several GB of storage space available, you will get this error. It won't help if you have space available on other drives, because ADB only interacts with the folder it is installed on. So having 100 GB free on another drive won't help as an example.
sic0048 said:
It's not the space on the phone. You don't download and install these factory images from your phone. You have to download them to a computer and install them that way. If you computer is short on storage space, it will give the same error when it tries to upzip the factory image during the installation process. I've had it happen to me before and had to clear up space on my computer in order to finish flashing a factory image.
Click to expand...
Click to collapse
That as wll should not be the case or the unzip will be larger than 30 GB? That is the space left on my notebook
simhagen said:
That as wll should not be the case or the unzip will be larger than 30 GB? That is the space left on my notebook
Click to expand...
Click to collapse
No. As long as that space is available on your main drive (see my edit above), 30 GB should be plenty of space. I'm thinking it takes around 5 GB if I remember correctly.
simhagen said:
Thanks,
link does not work for me though...
Click to expand...
Click to collapse
https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Try this
Hi,
so with the last post the update of fastboot worked fine and the flashing went well. Thanks! Stange thing was, it did not work under Linux it stopped at flashing vendor_b (nothing happend for half an hour or so, tried it several times with different Android 10 versions):
Code:
extracting vendor.img (523 MB) to disk... took 2.502s
archive does not contain 'vendor.sig'
Sending sparse 'vendor_b' 1/3 (262140 KB)
under Windows I didn't get this problem. So system is up and running again.
Thank you!
simhagen said:
Hi,
so with the last post the update of fastboot worked fine and the flashing went well. Thanks! Stange thing was, it did not work under Linux it stopped at flashing vendor_b (nothing happend for half an hour or so, tried it several times with different Android 10 versions):
under Windows I didn't get this problem. So system is up and running again.
Thank you!
Click to expand...
Click to collapse
Glad to hear you're sorted. It took me a while to work out I just needed to update fastboot. Someone on XDA helped me with it.
simhagen said:
Ok, so far so good. I tried it on Windows with the newest version, same problem. Than I switched to Linux and it worked up to the point "Sending sparse 'vendor_b' 1/3 (262140 KB)" than it gets stuck and nothing happens.
Click to expand...
Click to collapse
I had the exact same problem as you did. I tried different versions of the stock ROM, I tried different versions of the fastboot tool (including sdkmanager --update to get to the latest, etc.). It failed at the same time, every time: "Sending sparse 'vendor_a'"
What actually worked for me was plugging the USB cable into a port directly on the laptop, instead of a hub built into the docking station.
**** you not, worked perfectly. Same cable, same fastboot binary, same laptop, same OS, just switching to a different port did the trick. Don't plug the cable into a USB hub.
Hey guys - I am getting the following error when trying to flash the 11 preview, any ideas?
[email protected] ~/Downloads $ fastboot -w update image-sargo-rpp1.200123.016.zip
--------------------------------------------
Bootloader Version...: b4s4-0.2-6110009
Baseband Version.....: g670-00038-200117-B-6143243
Serial Number........: 93HAY0BGZZ
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.059s]
Checking 'version-bootloader' OKAY [ 0.059s]
Checking 'version-baseband' OKAY [ 0.060s]
Setting current slot to 'a' OKAY [ 0.143s]
extracting boot.img (64 MB) to disk... took 0.318s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 2.270s]
Writing 'boot_a' OKAY [ 0.414s]
extracting dtbo.img (8 MB) to disk... took 0.064s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.370s]
Writing 'dtbo_a' OKAY [ 0.094s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (4 KB) OKAY [ 0.120s]
Writing 'vbmeta_a' OKAY [ 0.065s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.060s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.011s]
Resizing 'product_a' OKAY [ 0.005s]
Resizing 'system_a' OKAY [ 0.006s]
Resizing 'system_ext_a' OKAY [ 0.004s]
Resizing 'vendor_a' OKAY [ 0.005s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1644 MB) to disk...ziparchive W 03-03 12:34:08 17940 17940 Zip: inflate zerr=-3 (nIn=0x5af378892b33 aIn=31341 nOut=0x5af37889eac0 aOut=15088)
fastboot: error:
failed to extract 'product.img': Zlib error
Not sure what to do.. Im sure i've encountered this before but cant remember how to fix
Try to adb sideload it. It will work. I've been going back and forth. Sideload works & with the factory image, it only wants to work if I remove -w from the batch file which is weird.
I followed the instructions on Google's site, but when I ran the script, it failed.
Output:
Code:
[email protected]:~/hammerhead-m4b30z$ ./flash-all.sh
< waiting for any device >
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.310s]
writing 'bootloader'...
OKAY [ 0.524s]
finished. total time: 0.834s
rebooting into bootloader...
OKAY [ 0.100s]
finished. total time: 0.150s
target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [ 1.740s]
writing 'radio'...
OKAY [ 3.131s]
finished. total time: 4.871s
rebooting into bootloader...
OKAY [ 0.100s]
finished. total time: 0.150s
extracting android-info.txt (0 MB)...
extracting boot.img (8 MB)...
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (9 MB)...
archive does not contain 'recovery.sig'
extracting system.img (996 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
archive does not contain 'vendor.img'
wiping userdata...
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.45.5 (07-Jan-2020)
/tmp/TemporaryFile-FXsDZt: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata