Database Info

[Q] "Bricked" One... not able to start it - FIXED

Hi all,
I just completely bricked my One
I wanted update my AOKPk to the newer version, but some of the apps always failed... so I decided to wipe One completely and install everything from scratch...
So made backup, took off SIM card and went to the TWRP and did:
- dalvik cache
- system
- data
- internal storage
- cache
and install this:
- aokpk_bacon_kitkat_daily_1409231727.zip
- pa_gapps-modular-pico-4.4.4-20140923-signed.zip
- pa_gapps_playservices-games_update_20140923-signed.zip
but I was not able to download any app from GappStore... I tried all 3 guides I googled, but nothing helped...
So wipe one more time:
- dalvik cache
- system
- data
- internal storage
- cache
+ Factory reset (in TWRP)
+ Format data
Installed:
- aokpk_bacon_kitkat_daily_1409231727.zip
- pa_gapps-modular-pico-4.4.4-20140923-signed.zip
- pa_gapps_playservices-games_update_20140923-signed.zip
and then when One boot up to "Welcome ... set your language" it reset... and boot again to Welcome... and reset... never ending reset loop...
So wipe One again:
- dalvik cache
- system
- data
- internal storage
- cache
+ Factory reset (in TWRP)
and install SlimKat:
- Slim-bacon-4.4.4.build.8.0-WEEKLY-6972.zip
- Slim_mini_gapps.BETA.4.4.4.build.8.x-289.zip
and again when One boot up to "Welcome ... set your language" it reset... and boot again to Welcome... and reset... never ending reset loop...
So wipe One again:
- dalvik cache
- system
- data
- internal storage
- cache
And went to the fastboot and tried to insert boot.img there... but...
d:\aaa>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (5560 KB)...
OKAY [ 0.170s]
writing 'boot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.180s
The "Device not unlocked" was quite surprise, as I already had CM11s > CM11 > SlimKat > AOKPk and all of them works OK
So I ran command:
d:\aaa>fastboot oem unlock
...
OKAY [ -0.000s]
finished. total time: -0.000s
but One restarted to the TWRP only... and when I went back to the fastboot I ended up with same "Device not unlocked" message
So, now I have One with CM11s (cm-11-20140924-NIGHTLY-bacon.zip) installed via TWPR, but once it boot up and Welcome screen with languages appeared it reset and boot up and reset and .... :crying:
Please please please help...

Just now I tried the guide from here: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Unziped the cm-11.0-XNPH33R-bacon-signed-fastboot_64GB.zip, to the same folder as I have the OPO_64GB.zip tool...
and here is output...
d:\aaa>flash-all.bat
target reported max download size of 536870912 bytes
sending 'modem' (56337 KB)...
OKAY [ 1.778s]
writing 'modem'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 1.778s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.016s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.016s]
writing 'dbi'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.016s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.016s]
writing 'aboot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.031s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.016s]
writing 'rpm'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.016s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ 0.016s]
writing 'tz'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.016s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.296s]
writing 'LOGO'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.296s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
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'
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: c9a88403
--------------------------------------------
checking product...
OKAY [ 0.016s]
sending 'boot' (5560 KB)...
OKAY [ 0.172s]
writing 'boot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.187s
Press any key to exit...

Sounds like you have a locked BL. Lots of people have been experiencing problems with there one after the OTA update. Corrupted bootloaders/device locking its BL again. Try this out and see if it works (If you can get into fastboot, which you never stated in the second post) http://forum.xda-developers.com/oneplus-one/help/oneplus-one-unable-to-unlock-bootloader-t2845626

Thank you very much...
d:\aaa>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
So, I am in the status: 2) Unlock Bit - FALSE , Tamper Bit - TRUE
But when I run: fastboot oem unlock
One reset to the TWRP, exactly it is described in the here: http://forum.xda-developers.com/oneplus-one/help/oneplus-one-unable-to-unlock-bootloader-t2845626
But I dont understand how to unlock it... this not make any sence to me
There are generally 2 bits present on some partition of the phone for keeping track of unlocking.
1) lock / unlock bit
2) tamper bit
edit 1: I tried this... but...
d:\aaa>fastboot.exe boot OnePlusOne-OnlyBootloaderToggle.zip
creating boot image...
creating boot image - 4096 bytes
downloading 'boot.img'...
OKAY [ 0.004s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.007s

djha53k said:
Thank you very much...
d:\aaa>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
So, I am in the status: 2) Unlock Bit - FALSE , Tamper Bit - TRUE
But when I run: fastboot oem unlock
One reset to the TWRP, exactly it is described in the here: http://forum.xda-developers.com/oneplus-one/help/oneplus-one-unable-to-unlock-bootloader-t2845626
But I dont understand how to unlock it... this not make any sence to me
There are generally 2 bits present on some partition of the phone for keeping track of unlocking.
1) lock / unlock bit
2) tamper bit
edit 1: I tried this... but...
d:\aaa>fastboot.exe boot OnePlusOne-OnlyBootloaderToggle.zip
creating boot image...
creating boot image - 4096 bytes
downloading 'boot.img'...
OKAY [ 0.004s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.007s
Click to expand...
Click to collapse
Can't really help except when I purchased my phone as a used device I had the problem with google play store, wouldn't sign in or anything.Wiped and factory reset did nothing to help so I just went to the rooting guide and started from scratch. Once I had completed the guide all was good. Make sure your not using 2.8.x TWRP only 2.7.x.

Yes, I have TWRP 2.8.0.1 installed, but I am not able to downgrade it...
Even when I use any tool ... I got...
target reported max download size of 536870912 bytes
sending 'recovery' (15294 KB)...
OKAY [ 0.484s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.487s
so, I am completely f*c* :crying:
edit: so I tried to lock and then unlock... nothing
Code:
d:\aaa>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.006s
d:\aaa>fastboot.exe boot recovery.img
downloading 'boot.img'...
OKAY [ 0.236s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.239s
d:\aaa>fastboot.exe oem lock
...
OKAY [ 0.002s]
finished. total time: 0.002s
d:\aaa>
d:\aaa>
d:\aaa>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
d:\aaa>fastboot.exe oem unlock
...
OKAY [ 0.013s]
finished. total time: 0.013s

djha53k said:
Yes, I have TWRP 2.8.0.1 installed, but I am not able to downgrade it...
Even when I use any tool ... I got...
target reported max download size of 536870912 bytes
sending 'recovery' (15294 KB)...
OKAY [ 0.484s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.487s
so, I am completely f*c* :crying:
edit: so I tried to lock and then unlock... nothing
Code:
d:\aaa>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.006s
d:\aaa>fastboot.exe boot recovery.img
downloading 'boot.img'...
OKAY [ 0.236s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.239s
d:\aaa>fastboot.exe oem lock
...
OKAY [ 0.002s]
finished. total time: 0.002s
d:\aaa>
d:\aaa>
d:\aaa>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
d:\aaa>fastboot.exe oem unlock
...
OKAY [ 0.013s]
finished. total time: 0.013s
Click to expand...
Click to collapse
i would recommend to flash CM with fastboot again:
<http>://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip
Code:
fastboot flash boot boot.img
fastboot flash userdata userdata_64G.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
[B]fastboot oem unlock
fastboot reboot-bootloader
fastboot flash recovery twrp.img
fastboot reboot[/B]
everything should be fine and you should have an unlocked bootloader and twrp. ofc it'll wipe _anything_ on your device

kemals said:
i would recommend to flash CM with fastboot again:
<http>://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip
Code:
fastboot flash boot boot.img
fastboot flash userdata userdata_64G.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
[B]fastboot oem unlock
fastboot reboot-bootloader
fastboot flash recovery twrp.img
fastboot reboot[/B]
everything should be fine and you should have an unlocked bootloader and twrp. ofc it'll wipe _anything_ on your device
Click to expand...
Click to collapse
Hello,
thank you... but...
I have the cm-11.0-XNPH33R-bacon-signed-fastboot.zip file already and tried it to install...
Anyway here is new try...
File "cm-11.0-XNPH33R-bacon-signed-fastboot.zip" unziped to the d:\aa folder, and the "AndroidSDKSlim.zip" unziped to the same folder
Code:
d:\aa>fastboot devices
c9a88403 fastboot
d:\aa>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (5560 KB)...
OKAY [ 0.180s]
writing 'boot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.180s
Or have I done it wrong way??? After 20 hours trying I am desperate... :crying:
edit: I red this topic "http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912" but I tried many time, but anything worked...
Please can you provide exact command sequence? Maybe I really dont understand how to perform it completlly

First thing you have to do is unlock the bootloader again, but this will wipe the phone
fastboot oem unlock
Once that's done, you'll then be able to flash a new ROM
EDIT: Seems you've tried that so you could have a corrupt partition somewhere due to all the stuff you've done to now. I think it happens as it factory resets the unit using the stock recovery and as you have TWRP it can't carry out the process...

did you tried to flash the boot.img like "fastboot -c flash boot boot.img"? the -c is for override the kernel (i think the kernel is in the "boot.img" but not sure so check where is the kernel and the do it with the right file name)

djha53k said:
d:\aaa>fastboot.exe boot OnePlusOne-OnlyBootloaderToggle.zip
Click to expand...
Click to collapse
LOL! That's the script you need in order to unlock your bootloader again...but you don't have to boot it!
You just must flash it via recovery...

First of all wiping internal is a horrible idea. Never do that. That's the worst thing you can do.
Now please tell me do you have the persist block?
It is located in dev/block/platform/msm_sdcc.1/by name?
If you don't then see my help thread http://forum.xda-developers.com/showthread.php?p=55488755

markbencze said:
First of all wiping internal is a horrible idea. Never do that. That's the worst thing you can do.
Now please tell me do you have the persist block?
It is located in dev/block/platform/msm_sdcc.1/by name?
If you don't then see my help thread http://forum.xda-developers.com/showthread.php?p=55488755
Click to expand...
Click to collapse
OK, thank you for advice... I will never do it again...
Anyway... finally I the unlock worked...
Code:
d:\a>adb push OnePlusOne-BootUnlocker.zip /sdcard
68 KB/s (2182 bytes in 0.031s)
d:\a>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
finished. total time: 0.016s
Stock CM11s installed:
Code:
d:\a>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (56337 KB)...
OKAY [ 1.778s]
writing 'modem'...
OKAY [ 0.889s]
finished. total time: 2.668s
d:\a>fastboot flash sbl1 sbl1.mbn
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ -0.000s]
writing 'sbl1'...
OKAY [ 0.016s]
finished. total time: 0.016s
d:\a>fastboot flash dbi sdi.mbn
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.016s]
writing 'dbi'...
OKAY [ 0.000s]
finished. total time: 0.016s
d:\a>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.016s]
writing 'aboot'...
OKAY [ 0.016s]
finished. total time: 0.031s
d:\a>fastboot flash rpm rpm.mbn
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ -0.000s]
writing 'rpm'...
OKAY [ 0.016s]
finished. total time: 0.016s
d:\a>fastboot flash tz tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ 0.016s]
writing 'tz'...
OKAY [ -0.000s]
finished. total time: 0.016s
d:\a>fastboot flash LOGO logo.bin
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.312s]
writing 'LOGO'...
OKAY [ 0.156s]
finished. total time: 0.468s
d:\a>fastboot update -w cm-11.0-XNPH33R-bacon-signed-fastboot.zip
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'
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: c9a88403
--------------------------------------------
checking product...
OKAY [ 0.000s]
sending 'boot' (5560 KB)...
OKAY [ 0.187s]
writing 'boot'...
OKAY [ 0.094s]
sending 'recovery' (7412 KB)...
OKAY [ 0.234s]
writing 'recovery'...
OKAY [ 0.125s]
erasing 'system'...
OKAY [ 0.047s]
sending sparse 'system' (523960 KB)...
OKAY [ 17.956s]
writing 'system'...
OKAY [ 25.428s]
sending sparse 'system' (250580 KB)...
OKAY [ 8.424s]
writing 'system'...
OKAY [ 8.642s]
erasing 'userdata'...
OKAY [ 2.246s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 59914792960
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14627635
Block groups: 447
Reserved block group size: 1024
Created filesystem with 11/3661824 inodes and 275906/14627635 blocks
sending 'userdata' (141075 KB)...
writing 'userdata'...
OKAY [ 18.876s]
erasing 'cache'...
OKAY [ 0.031s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
sending 'cache' (10432 KB)...
writing 'cache'...
OKAY [ 0.827s]
rebooting...
finished. total time: 83.148s
But my troubles does not ends
When CM11s boot up, at least I dont have repeating restarts... but now I see this:
Code:
Unfortunately, AudioFX has stopped...
On background is Welcome... choose language...
But AudioFX failure popup is on the top and I did click on it about 20 times, but it is still re-appearing :crying:
I cannot move anywhere... just shutdown One by long holding power button

djha53k said:
OK, thank you for advice... I will never do it again...
Anyway... finally I the unlock worked...
Code:
d:\a>adb push OnePlusOne-BootUnlocker.zip /sdcard
68 KB/s (2182 bytes in 0.031s)
d:\a>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
finished. total time: 0.016s
Stock CM11s installed:
Code:
d:\a>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (56337 KB)...
OKAY [ 1.778s]
writing 'modem'...
OKAY [ 0.889s]
finished. total time: 2.668s
d:\a>fastboot flash sbl1 sbl1.mbn
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ -0.000s]
writing 'sbl1'...
OKAY [ 0.016s]
finished. total time: 0.016s
d:\a>fastboot flash dbi sdi.mbn
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.016s]
writing 'dbi'...
OKAY [ 0.000s]
finished. total time: 0.016s
d:\a>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.016s]
writing 'aboot'...
OKAY [ 0.016s]
finished. total time: 0.031s
d:\a>fastboot flash rpm rpm.mbn
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ -0.000s]
writing 'rpm'...
OKAY [ 0.016s]
finished. total time: 0.016s
d:\a>fastboot flash tz tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ 0.016s]
writing 'tz'...
OKAY [ -0.000s]
finished. total time: 0.016s
d:\a>fastboot flash LOGO logo.bin
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.312s]
writing 'LOGO'...
OKAY [ 0.156s]
finished. total time: 0.468s
d:\a>fastboot update -w cm-11.0-XNPH33R-bacon-signed-fastboot.zip
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'
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: c9a88403
--------------------------------------------
checking product...
OKAY [ 0.000s]
sending 'boot' (5560 KB)...
OKAY [ 0.187s]
writing 'boot'...
OKAY [ 0.094s]
sending 'recovery' (7412 KB)...
OKAY [ 0.234s]
writing 'recovery'...
OKAY [ 0.125s]
erasing 'system'...
OKAY [ 0.047s]
sending sparse 'system' (523960 KB)...
OKAY [ 17.956s]
writing 'system'...
OKAY [ 25.428s]
sending sparse 'system' (250580 KB)...
OKAY [ 8.424s]
writing 'system'...
OKAY [ 8.642s]
erasing 'userdata'...
OKAY [ 2.246s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 59914792960
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14627635
Block groups: 447
Reserved block group size: 1024
Created filesystem with 11/3661824 inodes and 275906/14627635 blocks
sending 'userdata' (141075 KB)...
writing 'userdata'...
OKAY [ 18.876s]
erasing 'cache'...
OKAY [ 0.031s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
sending 'cache' (10432 KB)...
writing 'cache'...
OKAY [ 0.827s]
rebooting...
finished. total time: 83.148s
But my troubles does not ends
When CM11s boot up, at least I dont have repeating restarts... but now I see this:
Code:
Unfortunately, AudioFX has stopped...
On background is Welcome... choose language...
But AudioFX failure popup is on the top and I did click on it about 20 times, but it is still re-appearing :crying:
I cannot move anywhere... just shutdown One by long holding power button
Click to expand...
Click to collapse
yep you wiped your persist block.
go to my thread and fix it and stop flashing before extensive reading!
and i forbid you from wiping internal again

Uff too late... after 24 hours trying... I was so happy that it works... so I already did this...
d:\a>fastboot boot TWRP-2.7.1.0.img
downloading 'boot.img'...
OKAY [ 0.484s]
booting...
OKAY [ 0.016s]
finished. total time: 0.499s
d:\a>adb push Slim-bacon-4.4.4.build.8.0-WEEKLY-6972.zip /sdcard
5046 KB/s (165353599 bytes in 31.995s)
d:\a>adb push Slim_mini_gapps.BETA.4.4.4.build.8.x-289.zip /sdcard
5343 KB/s (61713022 bytes in 11.278s)
d:\a>adb push SuperSU-v2.02.zip /sdcard
5260 KB/s (1260473 bytes in 0.234s)
Click to expand...
Click to collapse
and I am in the never ending restarts again, aaaaaaaaa :crying:
edit: OK, so back to CM11s 33R.. with failed AudioFX... gonna read your post how to fix this...
After 24hour trying to make One works again... I will be happy with any ROM, fully working...

So, I reinstall CM11s 33R again and I have AudioFX failing error msg again...
I downloaded:
- NEVER_SETTLE_lite_fix.zip
- ONEPLUS_ONE_Nightmare_fix.zip
I am in the Fastboot Mode now, then I supposed to do:
- fastboot erase persist
- fastboot flash persist persist.img
- fastboot erase reserve4
- fastboot flash reserve4 reserve4.img
But I have no idea how to perform this:
open terminal --- which terminal?? I have W7 on my PC, so currently I accessing One by cmd
su
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
Or flash persist.img and reserve4.img fix the issue?
I am sorry, but after 24 hour "fixing" this... Iam dead

djha53k said:
So, I reinstall CM11s 33R again and I have AudioFX failing error msg again...
I downloaded:
- NEVER_SETTLE_lite_fix.zip
- ONEPLUS_ONE_Nightmare_fix.zip
I am in the Fastboot Mode now, then I supposed to do:
- fastboot erase persist
- fastboot flash persist persist.img
- fastboot erase reserve4
- fastboot flash reserve4 reserve4.img
But I have no idea how to perform this:
open terminal --- which terminal?? I have W7 on my PC, so currently I accessing One by cmd
su
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
Or flash persist.img and reserve4.img fix the issue?
I am sorry, but after 24 hour "fixing" this... Iam dead
Click to expand...
Click to collapse
you need to enter those commands with your device in fastboot mode (the .img files)
once you are up and running do the efs backup.

OK, thank you very much for advice...
Done now:
d:\a>fastboot erase persist
erasing 'persist'...
OKAY [ 0.031s]
finished. total time: 0.031s
d:\a> fastboot flash persist persist.img
target reported max download size of 536870912 bytes
sending 'persist' (4244 KB)...
OKAY [ 0.140s]
writing 'persist'...
OKAY [ 0.265s]
finished. total time: 0.406s
d:\a>fastboot erase reserve4
erasing 'reserve4'...
OKAY [ 1.622s]
finished. total time: 1.622s
d:\a> fastboot flash reserve4 reserve4.img
target reported max download size of 536870912 bytes
sending 'reserve4' (5176 KB)...
OKAY [ 0.172s]
writing 'reserve4'...
OKAY [ 0.234s]
finished. total time: 0.406s
Click to expand...
Click to collapse
and I am going to google what is the "efs backup" and how to do it
Before I will boot up CM11s 33R
edit: hmm, so as per google results I have to install TWRP and then make backup in the TWRP...
but I dont have TWRP yet, as I am on fully stock CM11s ROM...
So should I flash TWRP and then make backup??
edit 1: so as the TWRP scr*w it up last time, should I use the CWM Recovery instead???
edit final: successfully installed TWRP, made backup
successufully boot to CM11s 33R... no repeating restart... no AudioFX stopped working..
jupiiiiiiiiiiiiii, Thank you very much...

djha53k said:
OK, thank you very much for advice...
Done now:
and I am going to google what is the "efs backup" and how to do it
Before I will boot up CM11s 33R
edit: hmm, so as per google results I have to install TWRP and then make backup in the TWRP...
but I dont have TWRP yet, as I am on fully stock CM11s ROM...
So should I flash TWRP and then make backup??
edit 1: so as the TWRP scr*w it up last time, should I use the CWM Recovery instead???
edit final: successfully installed TWRP, made backup
successufully boot to CM11s 33R... no repeating restart... no AudioFX stopped working..
jupiiiiiiiiiiiiii, Thank you very much...
Click to expand...
Click to collapse
Happy days, I will tread carefully with my one before its a 1-1=0

Ohh yeah... but...
As I had SlimKat and AOKPk before... I have to say the CM11s is quite (how to say it) "poor" :angel:
Also strange is that there are only two folders on the SDCARD: Android and TWRP... that´s it... nothing else
Apex laucher configured... backuped files copied back to One...
Gonna restore app data via TitaniumBackup... and hopefully it will works for sometime again...
I have done with flashing other ROMs for sometime... :good:

fastboot error messages, are these serious? [solved]

Yesterday I flashed the NMF26U factory image on my Pixel using flash-all. I didn't remove the '-w' because I wanted a clean install. I saved the terminal output and there are several things that have me quite concerned even though my phone appears to be working fine.
Note the two places where it says "FAILED". Am I in trouble but don't know it yet?
Code:
E:\MobileDevices\Minimal ADB and Fastboot>flash-all
target reported max download size of 536870912 bytes
sending 'bootloader' (32980 KB)...
OKAY [ 1.154s]
writing 'bootloader'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 16.255s]
finished. total time: 17.410s
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.047s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (57192 KB)...
OKAY [ 1.919s]
writing 'radio'...
OKAY [ 1.092s]
finished. total time: 3.026s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
< waiting for device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
--------------------------------------------
Bootloader Version...: 8996-012001-1611091517
Baseband Version.....: 8996-012511-1611190200
Serial Number........: FA6C10300677
--------------------------------------------
checking product...
OKAY [ 0.047s]
checking version-bootloader...
OKAY [ 0.031s]
checking version-baseband...
OKAY [ 0.047s]
sending 'boot' (24821 KB)...
OKAY [ 0.889s]
writing 'boot'...
(bootloader) Flashing active slot "_a"
OKAY [ 0.655s]
sending sparse 'system' (516459 KB)...
OKAY [ 18.018s]
writing 'system'...
OKAY [ 6.802s]
sending sparse 'system' (520631 KB)...
OKAY [ 18.470s]
writing 'system'...
OKAY [ 10.998s]
sending sparse 'system' (517487 KB)...
OKAY [ 18.096s]
writing 'system'...
OKAY [ 7.597s]
sending 'vendor' (235186 KB)...
OKAY [ 7.956s]
writing 'vendor'...
OKAY [ 6.599s]
erasing 'userdata'...
OKAY [ 6.848s]
sending 'userdata' (138957 KB)...
OKAY [ 4.696s]
writing 'userdata'...
OKAY [ 1.342s]
erasing 'cache'...
(bootloader) Erasing active slot "_a"
FAILED (remote: Partition table doesn't exist
)
finished. total time: 109.403s
Press any key to exit...

because flash all is bat file, it contains many items which maybe not included in the factory image to be fashed.
Almost, I got same information.
by the way, how can we save or input the flash all results. I am on windows

bush911 said:
by the way, how can we save or input the flash all results. I am on windows
Click to expand...
Click to collapse
Right click the menu bar in the command box and select edit then 'selec all's. Right click again, edit then copy. Paste it into a document.

I had to re-flash back to 7.1.0, then upon setting up the phone, it began taking the OTA 7.1.1 update, which is fine. Now that the phone is unlocked and updated, what is the best method to gain root access from this point? boot-to-root or install the latest SU or ?? Thanks.

Your fastboot binary is out of date. Make sure you're using the latest version.

wbxp99 said:
Your fastboot binary is out of date. Make sure you're using the latest version.
Click to expand...
Click to collapse
Thank you! It's nice to receive a definitive answer on this. I flashed again with the latest fastboot version and the log output is very different from the first time. I am confident now that everything is in its proper place.

pstgh said:
I had to re-flash back to 7.1.0, then upon setting up the phone, it began taking the OTA 7.1.1 update, which is fine. Now that the phone is unlocked and updated, what is the best method to gain root access from this point? boot-to-root or install the latest SU or ?? Thanks.
Click to expand...
Click to collapse
This a thread about fastboot error messages. There are guide in the SU and TWRP threads. Very easy I don't personally think you need anything like boot to root. Just follow the instructions and make sure you use TWRP RC1 and SU 2.79 SR 2

"FAILED (remote: Command Flash Error)" -- When flashing bootloader

When I was flashing factory updates on my Pixel 2 last night, I got an error at the first step (using the flash-all.sh method), when it flashes the bootloader:
Code:
sending 'bootloader_a' (38728 KB)...
OKAY [ 2.095s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 2.099s
This happened both trying to flash the original .010 factory image and the .018 November update (haven't tried .025 yet). I had problems getting .010 to work (I was trying to downgrade, long story, it seemed to get stuck at the G logo, I gave up). But .018 worked fine, even with the flash of the bootloader failing. In fact, the bootloader version is the same as in .010, the September factory image, so I guess for .018 it just did not matter that the bootloader did not flash.
But anyway, I'm worried about this "Command Flash Error." What does it mean? If a new bootloader really can't be flashed on my device that seems like a problem.
I saw a mention of this problem in these two places: https://www.xda-developers.com/pixel-2-failing-flash-factory-images/ (in the comments) and https://www.reddit.com/r/AndroidPre...one_unlock_the_pixel_2_bootloader_without_an/. But there's no real explanation or solution.
[Edit: Just tried flashing just the bootloader manually, from the .018 and .025 factory images, and it failed in the same way. It's the identical bootloader in both images so it's not surprising. So, indeed, the bootloader cannot be flashed on my device. Or at least the one that comes in .010, .018, and .025 cannnot: bootloader-walleye-mw8998-002.0059.00.img.]
[Edit, 12/7/17: The December update solves this problem. If you sideload the December OTA image, using adb, it updates the bootloader. After that it is possible to flash a bootloader image directly using fastboot as expected. So something was just wrong with the original bootloader on this device or how it was installed. The only situation in which this solution will not work, I think, is if you have a custom recovery, i.e. TWRP. I think then you cannot sideload an OTA image. You would need, I believe, to restore the stock recovery first, by flashing the stock boot.img that goes with you current version of Android.]

@CB74 hi, did you find a way to solve this ?

Bumping this thread as I'm in the same boat: "Command Flash Error" when flashing any bootloader.
Really annoyed with Google rn, because now that I recovered my phone to a previous factory image, I am now getting FC's on Pixel Setup and cannot even set up my phone again.

I never found a solution. But I just saw this thread where someone says he found a way to fix it: https://forum.xda-developers.com/showpost.php?p=74728097&postcount=8
It does require locking the device and unlocking the bootloader again, which of course wipes it. I am hesitant to do that. I do wonder from what's said in that thread if there is just something weird about the original bootloader that came with the device and that once the person in that thread got a a new version of the bootloader by signing up for the developer preview of Android that solved the problem. If that's the case then it would seem that sideloading the December OTA update might accomplish the same thing, without locking and unlocking the bootloader. I think the December OTA ought to also update the bootloader. I haven't tried this yet though. Just don't have time to mess with updates right now.
I did find with the November update that the OTA worked fine, even though the factory image would not flash the bootloader.

Can confirm sideloading the OTA according to Googles instructions on the download page also updates the bootloader.

kendong2 said:
Can confirm sideloading the OTA according to Googles instructions on the download page also updates the bootloader.
Click to expand...
Click to collapse
I managed to update to 8.1.0 through a bit of a Frankenstein method.... but not without a ton of stress. I tried side-loading the OTA, which updated the bootloader, but then something failed later about 95% of the way in.
Apparently, the phone switched itself to the B system partition, and I was able to the 8.1.0 factory image without a problem. 8.1.0 boots and everything works fine, but I am getting a warning message to contact the manufacturer when booting up.
I think there is an issue with the bootloader slot in my A system partition, because I had some other random errors when unlocking etc. Hopefully Google will send me a new replacement phone because this one has been a headache.

I posted the solution here...
https://www.reddit.com/r/GooglePixel/comments/7ht2tr/failed_remote_failed_to_loadauthenticate_boot/

I had this issue when trying to flash 8.1 Factory Image over 8.0.
I fixed it by flashing back stock boot.img and then ADB sideloading 8.1 OTA update.
Bootloader/8.1 updated successfully.

peikojose said:
I posted the solution here...
https://www.reddit.com/r/GooglePixel/comments/7ht2tr/failed_remote_failed_to_loadauthenticate_boot/
Click to expand...
Click to collapse
The problem in your thread at reddit seems to have to do with flashing the boot.img, which is not the same issue here. This thread is about problems flashing the bootloader. The boot.img and the bootloader image are not the same thing.

Okay, so I did my own experiment and I was right. I sideloaded the December OTA image. That updated the bootloader, as others have reported. After that whatever the problem was with flashing the bootloader from a factory image went away. I extracted the bootloader image from the December factory image zip, rebooted into the bootloader, and flashed the bootloader .img file using fastboot without a problem. So I assume going forward it should be possible to flash factory images, rather than sideoading OTA images, without issues regarding the bootloader.

Seems like sideloading the December OTA is the only solution here.

** So this is how I fixed my issue.
I used Deuces v4 script to flash all 8.1, after it was done was stuck in bootloader and wouldnt reboot out.
So then I used Google's flash-all.bat, then at the end I got a error missing boot.img, check folder and it was there.
So I re-used Deuces v4 script and flashed it again.
This time after it was done I was in 8.1 and all good.
Hope this helps!

I started that reddit thread. I'd try to sideload the OTA but I can't even get into recovery. It just goes right back to the bootloader.
---------- Post added at 09:52 AM ---------- Previous post was at 08:56 AM ----------
razrlover said:
** So this is how I fixed my issue.
I used Deuces v4 script to flash all 8.1, after it was done was stuck in bootloader and wouldnt reboot out.
So then I used Google's flash-all.bat, then at the end I got a error missing boot.img, check folder and it was there.
So I re-used Deuces v4 script and flashed it again.
This time after it was done I was in 8.1 and all good.
Hope this helps!
Click to expand...
Click to collapse
This worked! Thanks! I was able to get it to erase through recovery and it booted!

I received my Pixel2 (not XL! Europe free version) today. It came with Android 8.0 (November). I tried to flash 8.1 factory image (walleye-opm1.171019.011-factory-f74dd4fd.zip) via fastboot. But same "Command Flash Error" here while update bootloader. My bootloader version was 0059. The update requires 0066. (See Code 1).
The "Deuces v4 script" DIDN'T help me. It installed 8.1 on system-partition without update bootloader and some other partitions. uuh. I was scared of it for a moment, but the device starts Android 8.1 but bootloader stay at 0059.
My solution
- i added my google account to the phone
- i registered my pixel 2 for beta program via android.com/beta (with computer)
- i checked systemupdates, downloaded & installed 8.1 beta (round about 1.1GB)
- phone reboots and stucked 30 minutes at the G-logo
- i pressed power and volume-down till it reboots into bootloader
- i saw, that now the bootloader is version 0066!
- now i could run flash-all.sh without problems (i started the flash-all.sh commands manually, see Code 2)
- i was in Slot B, i switched to Slot A with: fastboot --set-active=_a; adb reboot-bootloader
- i saw, the Slot A bootloader was the old version 0059, i tried to flash it, without success, same error
- i switched to Slot B again and flashed the A bootloader: fastboot flash bootloader_a bootloader-walleye-mw8998-002.0066.00.img (see Code 3).
- now both bootloader are version 0066
I hope it will help you.
Code 1:
Code:
# fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img
target reported max download size of 536870912 bytes
sending 'bootloader' (38644 KB)...
OKAY [ 1.594s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.598s
# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
# fastboot flash radio radio-walleye-g8998-00164-1710262031.img
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 2.420s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.544s]
finished. total time: 2.964s
# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
# fastboot -w update image-walleye-opm1.171019.011.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Creating filesystem with parameters:
Size: 57071874048
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13933563
Block groups: 426
Reserved block group size: 1024
Created filesystem with 11/3489792 inodes and 265112/13933563 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: xxxxxxxxx
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0066.00'.
finished. total time: 0.004s
Code 2:
Code:
# fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38644 KB)...
OKAY [ 1.768s]
writing 'bootloader_b'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
(bootloader) Updating: partition:1 @0000D000 sz=0000B000
(bootloader) Updating: partition:2 @00018000 sz=0000B000
(bootloader) Updating: partition:3 @00023000 sz=0000B000
(bootloader) Updating: partition:4 @0002E000 sz=0000B000
(bootloader) Updating: partition:5 @00039000 sz=0000B000
(bootloader) Updating: cmnlib64 @00044000 sz=00048000
(bootloader) Updating: cmnlib @0008C000 sz=00037000
(bootloader) Updating: devcfg @000C3000 sz=0000F000
(bootloader) Updating: hyp @000D2000 sz=00040000
(bootloader) Updating: keymaster @00112000 sz=00046000
(bootloader) Updating: lockbooter @00158000 sz=00016000
(bootloader) Updating: pmic @0016E000 sz=0000D000
(bootloader) Updating: rpm @0017B000 sz=0003A000
(bootloader) Updating: tz @001B5000 sz=001DB000
(bootloader) Updating: xbl @00390000 sz=003A2000
(bootloader) Updating: apdp @00732000 sz=00004000
(bootloader) Updating: msadp @00736000 sz=00004000
(bootloader) Updating: hosd @0073A000 sz=01E1E000
(bootloader) Updating: abl @02558000 sz=00065000
OKAY [ 0.889s]
finished. total time: 2.658s
# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.201s
# fastboot flash radio radio-walleye-g8998-00164-1710262031.img
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 2.727s]
writing 'radio_b'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.545s]
finished. total time: 3.272s
# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.101s
# fastboot -w update image-walleye-opm1.171019.011.zip
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.202s
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.033s
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 11.869s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 4.173s
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 (347 MB) to disk... took 2.423s
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: 9c0d344d-4d88-428e-99a4-ccef9c9cf298
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.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: xxxxxxxxx
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot_b' (32768 KB)...
OKAY [ 1.495s]
writing 'boot_b'...
OKAY [ 0.001s]
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.679s]
writing 'dtbo_b'...
OKAY [ 0.000s]
erasing 'system_b'...
OKAY [ 0.396s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 22.653s]
writing 'system_b' 1/4...
OKAY [ 0.001s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 26.109s]
writing 'system_b' 2/4...
OKAY [ 0.000s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 25.569s]
writing 'system_b' 3/4...
OKAY [ 0.000s]
sending sparse 'system_b' 4/4 (393508 KB)...
OKAY [ 20.279s]
writing 'system_b' 4/4...
OKAY [ 0.000s]
erasing 'system_a'...
OKAY [ 1.999s]
sending sparse 'system_a' 1/2 (524284 KB)...
OKAY [ 23.680s]
writing 'system_a' 1/2...
OKAY [ 0.000s]
sending sparse 'system_a' 2/2 (57592 KB)...
OKAY [ 5.069s]
writing 'system_a' 2/2...
OKAY [ 0.000s]
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.269s]
writing 'vbmeta_b'...
OKAY [ 0.000s]
erasing 'vendor_b'...
OKAY [ 0.141s]
sending 'vendor_b' (355428 KB)...
OKAY [ 16.130s]
writing 'vendor_b'...
OKAY [ 0.000s]
Setting current slot to 'b'...
OKAY [ 1.682s]
erasing 'userdata'...
OKAY [ 0.942s]
sending 'userdata' (4669 KB)...
OKAY [ 0.224s]
writing 'userdata'...
OKAY [ 0.000s]
rebooting...
finished. total time: 147.489s
Code 3:
Code:
# fastboot --set-active=_a
Setting current slot to 'a'...
OKAY [ 0.016s]
finished. total time: 0.016s
# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.251s
# fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img
target reported max download size of 536870912 bytes
sending 'bootloader' (38644 KB)...
OKAY [ 1.812s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.724s
# fastboot flash bootloader_a bootloader-walleye-mw8998-002.0066.00.img
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38644 KB)...
OKAY [ 1.733s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.737s
# fastboot --set-active=_b
Setting current slot to 'b'...
OKAY [ 0.015s]
finished. total time: 0.015s
# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.051s
# fastboot flash bootloader_a bootloader-walleye-mw8998-002.0066.00.img
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38644 KB)...
OKAY [ 1.735s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
(bootloader) Updating: partition:1 @0000D000 sz=0000B000
(bootloader) Updating: partition:2 @00018000 sz=0000B000
(bootloader) Updating: partition:3 @00023000 sz=0000B000
(bootloader) Updating: partition:4 @0002E000 sz=0000B000
(bootloader) Updating: partition:5 @00039000 sz=0000B000
(bootloader) Updating: cmnlib64 @00044000 sz=00048000
(bootloader) Updating: cmnlib @0008C000 sz=00037000
(bootloader) Updating: devcfg @000C3000 sz=0000F000
(bootloader) Updating: hyp @000D2000 sz=00040000
(bootloader) Updating: keymaster @00112000 sz=00046000
(bootloader) Updating: lockbooter @00158000 sz=00016000
(bootloader) Updating: pmic @0016E000 sz=0000D000
(bootloader) Updating: rpm @0017B000 sz=0003A000
(bootloader) Updating: tz @001B5000 sz=001DB000
(bootloader) Updating: xbl @00390000 sz=003A2000
(bootloader) Updating: apdp @00732000 sz=00004000
(bootloader) Updating: msadp @00736000 sz=00004000
(bootloader) Updating: hosd @0073A000 sz=01E1E000
(bootloader) Updating: abl @02558000 sz=00065000
OKAY [ 0.890s]
finished. total time: 2.625s
# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.050s

depii said:
I received my Pixel2 (not XL! Europe free version) today. It came with Android 8.0 (November). I tried to flash 8.1 factory image (walleye-opm1.171019.011-factory-f74dd4fd.zip) via fastboot. But same "Command Flash Error" here while update bootloader. My bootloader version was 0059. The update requires 0066. (See Code 1).
The "Deuces v4 script" DIDN'T help me. It installed 8.1 on system-partition without update bootloader and some other partitions. uuh. I was scared of it for a moment, but the device starts Android 8.1 but bootloader stay at 0059.
My solution...
Click to expand...
Click to collapse
You really made that hard on yourself.
If you had read the whole thread you would have seen that simply sideloading the December OTA image, with adb, updates the bootloader and solves the problem. After that you can flash the bootloader with fastboot successfully (though it's unnecessary for now, since it has already been updated--but in the future should hopefully mean there will be no more problems flashing bootloaders).

I have the same problem.
But I solved it.
This is a bug,it already fixed in 2017/12 OTA File.
use adb sideload otafile.zip
or
check system update
Bug will fix after update.
Bootloader version is mw8998-002.0066.00 .
good luck.

cb474 said:
If you had read the whole thread you would have seen that simply sideloading the December OTA image, with adb, updates the bootloader and solves the problem.
Click to expand...
Click to collapse
cb474 said:
The only situation in which this solution will not work, I think, is if you have a custom recovery, i.e. TWRP.
Click to expand...
Click to collapse
Hm okay. Sideload didn't work for me. How can i sideload the ZIP to a stock system without TWRP?
In bootloader:
# adb sideload test.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
In "download mode" the phone display says: "ERROR: Operation Denied"
In "recovery mode" the phone display says: "No command"

depii said:
Hm okay. Sideload didn't work for me. How can i sideload the ZIP to a stock system without TWRP?
In bootloader:
# adb sideload test.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
In "download mode" the phone display says: "ERROR: Operation Denied"
In "recovery mode" the phone display says: "No command"
Click to expand...
Click to collapse
The steps are right on Googles OTA images page. Need to hold power button and press volume up when in recovery. Then a list of options will appear, one being Apply update from ADB.

Ra6idr0y said:
The steps are right on Googles OTA images page. Need to hold power button and press volume up when in recovery. Then a list of options will appear, one being Apply update from ADB.
Click to expand...
Click to collapse
EDIT: aaah i found my error I had overlooked that I have to press Power and Vol-Up, when i see the red exclamation mark (with "No command"). Thanks!
1) adb reboot recovery
2) The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
3) Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.

depii said:
EDIT: aaah i found my error I had overlooked that I have to press Power and Vol-Up, when i see the red exclamation mark (with "No command"). Thanks!
1) adb reboot recovery
2) The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
3) Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Click to expand...
Click to collapse
Yeah, the stock recovery is a little confusing. You get to the image of the Android lying on its back with the red exclamation mark and no menus and you think: OMG what happened?! Did I brick my device?
I don't know why it doesn't just boot to the menu, rather than hiding it behind a secret set of key presses. I guess that's to keep people who don't know what they are doing from messing things up? But then, wouldn't such people never boot to the recovery anyway? You already have to have gone out of your way to figure that out, so hiding the menu at that point seems a bit silly.

HELP: Request some advice on how to fix this error

Hey Everyone,
It's been a while since I've flashed a phone but I recently bought the pixel 2 and I was having a lot of freezing + restarting issues right from the start. I thought it was probably because the latest December update may be causing issues. Rather than return it, I thought I'd at least try to flash a clean factory image and see if that helped. My phone is a stock Pixel 2 64GB (not tied to any service provider). I first downloaded the latest adb drivers and installed them:
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Then I downloaded the latest stock image from the Android website :
8.1.0 (OPM1.171019.011, Dec 2017) - f74dd4fd9c7816a694901b01ba922c5033acb972f5fe5e51630400e4bfb07700
unpacked the zip file
Ran adb reboot bootloader
It loaded into Bootloader successfully
Then ran fastboot flashing unlock
that unlocked the bootloader successfully. Details in first picture:
Then went to the folder in which the image was unpacked and ran flash-all.bat.
Here I ran into an error with vendor_b
Here's the dump:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38644 KB)...
OKAY [ 0.968s]
writing 'bootloader_b'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
(bootloader) Updating: partition:1 @0000D000 sz=0000B000
(bootloader) Updating: partition:2 @00018000 sz=0000B000
(bootloader) Updating: partition:3 @00023000 sz=0000B000
(bootloader) Updating: partition:4 @0002E000 sz=0000B000
(bootloader) Updating: partition:5 @00039000 sz=0000B000
(bootloader) Updating: cmnlib64 @00044000 sz=00048000
(bootloader) Updating: cmnlib @0008C000 sz=00037000
(bootloader) Updating: devcfg @000C3000 sz=0000F000
(bootloader) Updating: hyp @000D2000 sz=00040000
(bootloader) Updating: keymaster @00112000 sz=00046000
(bootloader) Updating: lockbooter @00158000 sz=00016000
(bootloader) Updating: pmic @0016E000 sz=0000D000
(bootloader) Updating: rpm @0017B000 sz=0003A000
(bootloader) Updating: tz @001B5000 sz=001DB000
(bootloader) Updating: xbl @00390000 sz=003A2000
(bootloader) Updating: apdp @00732000 sz=00004000
(bootloader) Updating: msadp @00736000 sz=00004000
(bootloader) Updating: hosd @0073A000 sz=01E1E000
(bootloader) Updating: abl @02558000 sz=00065000
OKAY [ 0.902s]
finished. total time: 1.873s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 1.915s]
writing 'radio_b'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.540s]
finished. total time: 2.459s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.627s
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.030s
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 13.534s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 4.217s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
extracting vendor.img (347 MB) to disk... took 2.421s
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: f11aec18-ea16-11e7-baf7-f7ba65016da5
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.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.003s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot_b' (32768 KB)...
OKAY [ 0.710s]
writing 'boot_b'...
OKAY [ 0.002s]
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.475s]
writing 'dtbo_b'...
OKAY [ 0.002s]
erasing 'system_b'...
OKAY [ 0.245s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 11.908s]
writing 'system_b' 1/4...
OKAY [ 0.002s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 14.046s]
writing 'system_b' 2/4...
OKAY [ 0.001s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.996s]
writing 'system_b' 3/4...
OKAY [ 0.002s]
sending sparse 'system_b' 4/4 (393508 KB)...
OKAY [ 11.145s]
writing 'system_b' 4/4...
OKAY [ 0.001s]
erasing 'system_a'...
OKAY [ 1.916s]
sending sparse 'system_a' 1/2 (524284 KB)...
OKAY [ 11.917s]
writing 'system_a' 1/2...
OKAY [ 0.002s]
sending sparse 'system_a' 2/2 (57592 KB)...
OKAY [ 3.716s]
writing 'system_a' 2/2...
OKAY [ 0.002s]
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.264s]
writing 'vbmeta_b'...
OKAY [ 0.001s]
erasing 'vendor_b'...
OKAY [ 0.111s]
sending 'vendor_b' (355428 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 79.559s
Press any key to exit...
Now I'm facing the issue in the second screen.
I still have access to fastboot. I've tried to re-flash the image but same error. Can someone please help me here. I can't use my phone anymore.

Make sure you have latest adb and fastboot.
Try different usb cable ,A to C not C to C.
Try changing slots from b to a.

gm007 said:
Make sure you have latest adb and fastboot.
Try different usb cable ,A to C not C to C.
Try changing slots from b to a.
Click to expand...
Click to collapse
Hi, Thank you for your response. I believe I have the latest adb and fastboot because I just downloaded them off the Google website today.
I currently have a C to C cable but I don't have an A to C
Can you please elaborate more about the "Try changing slots part". I apologize for the noobie questions but its been a long time since I last flashed an image.
Thank you!
#EDIT#
Ran to the store and got a USB A to C cable, downloaded the November 8.0.0 build and tried to reflash and it worked. PHEW!
Quick question, can I try to flash 8.1.0 December build or should I just not take a risk and let things be as they are.?

You can flash 8.1 the same way with no problem or it should already be pushed by ota.
Anyway if you tried and got problem flashing 8.1 you need to update the bootloader first manually by fastboot.

Can not flash factory img:

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.