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:

Help: sending 'system' (1550356 KB)... FAILED (remote: data too large)

I have tried to flash a new system on my new Pixel but I am getting the above message.
I am using Ubuntu Linux with the stock android-tools-adb and andoid-tools-fastboot installed.
The same tools are working fine on my nexus5 phones.
Yes I enabled USB debugging and unlocked the bootloader.
Can anyone tell me what is different with Pixel phones?
adb version gives: Android Debug Bridge version 1.0.31

Have you tried the latest version of Android tools? I haven't used adb or fastboot with the pixel yet but know with past nexus devices I have experienced this error because I wasn't using the latest Android tools

I can't remember the exact specifics since I do not have a factory image available to me atm...
BUT, I believe you extract the contents of the image.zip and then use a text editor to individually add the flash commands for the content found inside the image.zip to the flash-all.sh (i.e. "fastboot flash system system.img.")

metricusa said:
...
adb version gives: Android Debug Bridge version 1.0.31
Click to expand...
Click to collapse
Update your ADB tools. The latest version is 1.0.36, I believe.

sn0warmy said:
Update your ADB tools. The latest version is 1.0.36, I believe.
Click to expand...
Click to collapse
This version of ADB is the latest in the ubuntu repositories. I did not find a newer version there.
Can anyone tell me how I can get a newer ADB and fastboot? It's not in the Android SDK package.
I want only the binary not the whole SDK as I have nothing to do with it.

metricusa said:
This version of ADB is the latest in the ubuntu repositories. I did not find a newer version there.
Can anyone tell me how I can get a newer ADB and fastboot? It's not in the Android SDK package.
I want only the binary not the whole SDK as I have nothing to do with it.
Click to expand...
Click to collapse
Here Download the Portable Version it worked great for me
http://forum.xda-developers.com/showthread.php?t=2317790

McMarius11 said:
Here Download the Portable Version it worked great for me
http://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
I have Ubuntu Linux. The link seems to have only windows executables.

OK so I upgraded fastboot and adb. Actually upgraded my ubuntu to latest version.
fastboot getvar version prompts version 0.5 for fastboot.
I managed to load the latest version NMF26Q onto the pixel but I am still getting an error. The Pixel appears to boot and work OK.
I am worried about the error though and wondered if anyone can figure out what it means and how I could mitigate it. See below output from flash-all.sh
Again, please remember I use Linux (ubuntu)
+++++++++++
~/Downloads/sailfish-nmf26q$ sudo ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (32728 KB)...
OKAY [ 0.831s]
writing 'bootloader'...
(bootloader) Valid bootloader version.
OKAY [ 0.709s]
finished. total time: 1.541s
rebooting into bootloader...
OKAY [ 4.155s]
finished. total time: 4.255s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (57192 KB)...
OKAY [ 1.422s]
writing 'radio'...
OKAY [ 0.564s]
finished. total time: 1.986s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.147s
< 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-1610061102
Baseband Version.....: 8996-012511-1611190200
Serial Number........: FAxxx
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.051s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot' (24821 KB)...
OKAY [ 0.642s]
writing 'boot'...
(bootloader) Flashing active slot "_a"
OKAY [ 0.311s]
sending sparse 'system' (516463 KB)...
OKAY [ 12.712s]
writing 'system'...
OKAY [ 5.004s]
sending sparse 'system' (520623 KB)...
OKAY [ 12.805s]
writing 'system'...
OKAY [ 7.138s]
sending sparse 'system' (517483 KB)...
OKAY [ 12.772s]
writing 'system'...
OKAY [ 5.491s]
sending 'vendor' (235186 KB)...
OKAY [ 5.806s]
writing 'vendor'...
OKAY [ 3.796s]
erasing 'userdata'...
OKAY [ 1.805s]
sending 'userdata' (138957 KB)...
OKAY [ 3.451s]
writing 'userdata'...
OKAY [ 1.301s]
erasing 'cache'...
(bootloader) Erasing active slot "_a"
FAILED (remote: Partition table doesn't exist)
finished. total time: 73.441s

Follow Method 2 here - it worked for me, as i had the same issue as you:
http://www.theandroidsoul.com/flash-firmware-factory-image-google-pixel/

OK I finally figured it out.
To clarify, the purpose was to burn a factory image and start from scratch. (no sideload). All without having to install Android studio or the SDK manager or whatever. This is a guide for Linux but I believe this method works in Windows as well with appropriate syntax.
1. First rule is to NEVER try to use a version of fastboot other than the one "prescribed" for the image you want to burn. To learn what version to use check Google's SKD Platform release Notes here: https://developer.android.com/studio/releases/platforms.html (my major mistake was to think that ubuntu would have the latest fastboot available in its repositories. Don't even try!)
2. Find the SDK Platform Tools version indicated on the above page. (In my case: Android SDK Platform-Tools 25.0.1 as I wanted to burn Android 7.1.1.). Google does not make them available AFAIK but other people do. I found them here: http://androidsdkoffline.blogspot.com/p/android-sdk-platform-tools.html OR do a Google Search.
3. Unpack the platform tools and the Factory image you wish to burn. Then copy fastboot from the Platform Tools directory to the image directory.
4. run fastboot from inside the directory. You can do this in at least 2 ways:
4a- manually run one-by-one the commands listed in the flash-all.sh script making sure you add sudo ./ in front of each fastboot command
4b- edit flash-all.sh and add sudo ./ in front of each fastboot command. Then run the flash-all script by typing ./flash-all.sh
There are of course more ways but I found this to be the simplest method as it doesn't involve installing any package and/or modifying your system variables. Plus, after you are done you can simply delete all files and directories you created.
Hope this helps other people too.
A final observation: It appears to me that starting with pixel the phones have 2 bootable sectors "slot a" and "slot b". See output below:
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
--------------------------------------------
Bootloader Version...: 8996-012001-1610061102
Baseband Version.....: 8996-012511-1611190200
Serial Number........: FAxxxx
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.051s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot_a' (24821 KB)...
OKAY [ 0.642s]
writing 'boot_a'...
OKAY [ 0.299s]
erasing 'system_a'...
OKAY [ 0.415s]
sending sparse 'system_a' 1/3 (516463 KB)...
OKAY [ 12.799s]
writing 'system_a' 1/3...
OKAY [ 5.009s]
sending sparse 'system_a' 2/3 (520623 KB)...
OKAY [ 14.101s]
writing 'system_a' 2/3...
OKAY [ 7.052s]
sending sparse 'system_a' 3/3 (517483 KB)...
OKAY [ 12.818s]
writing 'system_a' 3/3...
OKAY [ 5.449s]
erasing 'system_b'...
OKAY [ 0.354s]
sending sparse 'system_b' 1/4 (522362 KB)...
OKAY [ 12.856s]
writing 'system_b' 1/4...
OKAY [ 3.890s]
sending sparse 'system_b' 2/4 (514082 KB)...
OKAY [ 12.758s]
writing 'system_b' 2/4...
OKAY [ 4.302s]
sending sparse 'system_b' 3/4 (524026 KB)...
OKAY [ 12.967s]
writing 'system_b' 3/4...
OKAY [ 3.839s]
sending sparse 'system_b' 4/4 (88446 KB)...
OKAY [ 2.260s]
writing 'system_b' 4/4...
OKAY [ 0.842s]
erasing 'vendor_a'...
OKAY [ 0.153s]
sending 'vendor_a' (235186 KB)...
OKAY [ 5.804s]
writing 'vendor_a'...
OKAY [ 3.846s]
Setting current slot to 'a'...
OKAY [ 0.099s]
erasing 'userdata'...
OKAY [ 1.806s]
sending 'userdata' (138957 KB)...
OKAY [ 3.451s]
writing 'userdata'...
OKAY [ 1.301s]
rebooting...
finished. total time: 129.610s

How can i flash the factory image without encrypting?

Hi all,
I recently rooted my Pixel and was plagued by the 15% battery issue. I found in the Pixel XL forum to fix it i should flash boot_a boot.img but that erased all my data.
I figured I'd start fresh and looked up a few websites who had instructions (androidcentral being one of them) and it seems like any other google phone, except i started getting FAILED to flash. so i ended up doing the following and now my device is encrypted.
fastboot flash bootloader bootloader-img
fastboot reboot bootloader
fastboot flash radio radio-img
fastboot reboot bootloader
fastboot flash boot_a boot.img
fastboot flash system_a system.img
fastboot flash userdata userdata.img
fastboot flash vendor_a vendor.img
fastboot format userdata (have to do this in order to get phone to read as 128GB)
---
so now when i boot up, it goes through the setup but it's encrypted.
I guess my question is, with the way Pixel's will be handling updates, what are all of the extra .img files from the factory image and should i be flashing them in a particular order?
here are the contents:
aboot.img
apdp.img
boot.img
bootlocker.img
cmnlib32.img
cmnlib64.img
devcfg.img
hosd.img
hyp.img
keymaster.img
modem.img
pmic.img
rpm.img
system_other.img
system.img
tz.img
userdata.img
vendor.img
xbl.img
Any assistance would be greatly appreciated!
Thanks!

EDIT #1: I just locked and then unlocked the bootloader to see if that allows me to setup as unencrypted. It's taking a while to boot so I doubt it.
EDIT #2: Still encrypted after set up.
Wellp... i wonder what flashing these after the initial order above will do...
EDOT#3:
lock / unlock botloader
fastboot flash system_a system.img
fastboot flash system_b system_other.img
... still encrypted, it booted up a bit quicker (or maybe i'm going nuts)
EDIT #4:
lock / unlock botloader
fastboot flash system_a system.img
fastboot flash system_b system_other.img
fastboot flash keymaster_a keymaster.img
andddd.... still encrypted... can anyone help out?

updating android sudio/sdk

So on the newest SDK, the fastboot flash system system.img will automatically detect and erase system_a.
probably a good idea to be on the latest sdk platform-tools

lockd / unlocked bootloader
bash update-all.sh
CRUD... still encrypted.
here's the output if anyone would like:
Code:
Marcs-MacBook-Pro:sailfish-nde63p root# bash flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32820 KB)...
OKAY [ 1.404s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
OKAY [ 1.040s]
finished. total time: 2.444s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
sending 'radio_a' (57048 KB)...
OKAY [ 2.457s]
writing 'radio_a'...
OKAY [ 0.869s]
finished. total time: 3.326s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 122633060352
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29939712
Block groups: 914
Reserved block group size: 1024
Created filesystem with 11/7487488 inodes and 518062/29939712 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609191801
Serial Number........: NOPE :)
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.051s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot_a' (25073 KB)...
OKAY [ 0.982s]
writing 'boot_a'...
OKAY [ 0.600s]
erasing 'system_a'...
OKAY [ 1.201s]
sending sparse 'system_a' 1/4 (518936 KB)...
OKAY [ 29.084s]
writing 'system_a' 1/4...
OKAY [ 5.336s]
sending sparse 'system_a' 2/4 (506887 KB)...
OKAY [ 28.523s]
writing 'system_a' 2/4...
OKAY [ 13.352s]
sending sparse 'system_a' 3/4 (491777 KB)...
OKAY [ 28.733s]
writing 'system_a' 3/4...
OKAY [ 6.808s]
sending sparse 'system_a' 4/4 (32756 KB)...
OKAY [ 1.732s]
writing 'system_a' 4/4...
OKAY [ 0.619s]
erasing 'system_b'...
OKAY [ 1.181s]
sending sparse 'system_b' 1/4 (517263 KB)...
OKAY [ 30.183s]
writing 'system_b' 1/4...
OKAY [ 4.555s]
sending sparse 'system_b' 2/4 (513954 KB)...
OKAY [ 25.261s]
writing 'system_b' 2/4...
OKAY [ 5.386s]
sending sparse 'system_b' 3/4 (523846 KB)...
OKAY [ 33.335s]
writing 'system_b' 3/4...
OKAY [ 4.485s]
sending sparse 'system_b' 4/4 (88422 KB)...
OKAY [ 7.907s]
writing 'system_b' 4/4...
OKAY [ 1.348s]
erasing 'vendor_a'...
OKAY [ 0.520s]
sending 'vendor_a' (234137 KB)...
OKAY [ 7.342s]
writing 'vendor_a'...
OKAY [ 6.647s]
Setting current slot to 'a'...
OKAY [ 0.400s]
erasing 'userdata'...
OKAY [ 28.688s]
sending 'userdata' (145102 KB)...
OKAY [ 4.998s]
writing 'userdata'...
OKAY [ 2.393s]
rebooting...
finished. total time: 282.030s
Marcs-MacBook-Pro:sailfish-nde63p root#

tried factory reset and flashing some of the other images... no luck, still encrypted. guess i'll need to wait for TWRP to come out and figure out how to decrypt :-/

spunks3 said:
tried factory reset and flashing some of the other images... no luck, still encrypted. guess i'll need to wait for TWRP to come out and figure out how to decrypt :-/
Click to expand...
Click to collapse
Thanks friend!:laugh:

Modifiy the kernel

omegear said:
Modifiy the kernel
Click to expand...
Click to collapse
How?

Hey spunks, I'm in the same boat with you. Cant decrypt. I don't even remember encrypting in the first place!

Oface82 said:
Hey spunks, I'm in the same boat with you. Cant decrypt. I don't even remember encrypting in the first place!
Click to expand...
Click to collapse
I think it'll just be a waiting game... This happened to me when I flashed the original boot image using an out of date SDK.

Can you point me in the direction of the factory images? I need to start over

Why are you so desperate to decrypt? It's encrypted by default, and stops you from nothing at this moment, and likely won't be a road block in the future either.
Sent from my Pixel using Tapatalk

I had a similar issue. I tried to unroot in order to install the new OTA, because it failed. So I tried to flash the factory boot image via
Code:
fastboot flash boot boot.img
fastboot flash boot_b boot.img
After the next boot I got the nice "erasing" screen...
My phone was unencrypted before (dunno why) and now all my data is gone and it is encrypted... Maybe there are some devices, which are not encrypted by default and factory resetting after updates...

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

i soft bricked my pixel 2.. can anyone help?

i unlocked the bootloader used twrp to install magisk and installed a custom kernel, all of that went fine, then i decided to try and flash twrp which also worked... reinstalled magisk and kernel etc and it was getting stuck at the google logo,
i then decided to try and uninstall twrp and now i do not get the google logo, it won't go past the bootloader screen, bootloader seems to be functional and is accepting fastboot requests, however, the recovery is not working no matter what option i choose it will always take me back to the bootloader, tried reflashing stock images to get it working again but im getting an error with the bootloader remote command flash error.
any help is appreciated

xsanikax said:
i unlocked the bootloader used twrp to install magisk and installed a custom kernel, all of that went fine, then i decided to try and flash twrp which also worked... reinstalled magisk and kernel etc and it was getting stuck at the google logo,
i then decided to try and uninstall twrp and now i do not get the google logo, it won't go past the bootloader screen, bootloader seems to be functional and is accepting fastboot requests, however, the recovery is not working no matter what option i choose it will always take me back to the bootloader, tried reflashing stock images to get it working again but im getting an error with the bootloader remote command flash error.
any help is appreciated
Click to expand...
Click to collapse
Download the factory image for your current build.Unzip.
In flash-all, remove the -w so it doesn't wipe your device.
Ensure you have newest ADB &Fastboot.
While your device is in fastboot:
Code:
fastboot devices
Ensure you see your device serial number
Double click flash-all
That should reflash recovery so you can start over.
NOTE: You cannot flash TWRP, Kernel, and Magisk all at the same time. It causes issues.
Read this thread: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye). There are a lot of people that have had issues and have had help solving within it.

Diesel_Jeremiah said:
Download the factory image for your current build.Unzip.
In flash-all, remove the -w so it doesn't wipe your device.
Ensure you have newest ADB &Fastboot.
While your device is in fastboot:
Code:
fastboot devices
Ensure you see your device serial number
Double click flash-all
That should reflash recovery so you can start over.
NOTE: You cannot flash TWRP, Kernel, and Magisk all at the same time. It causes issues.
Read this thread: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye). There are a lot of people that have had issues and have had help solving within it.
Click to expand...
Click to collapse
thanks for the reply but i'm still getting the same error doing that.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38644 KB)...
OKAY [ 0.895s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.902s

xsanikax said:
thanks for the reply but i'm still getting the same error doing that.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38644 KB)...
OKAY [ 0.895s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.902s
Click to expand...
Click to collapse
Are you on 8.0 or 8.1?
Which bootloader are you on?
If you are in the bootloader, does it have the error line at the bottom?
If you cycle your volume buttons and reboot bootloader, does the error go away?
If the error goes away, try flash-all again.
If not:
From the bootloader, try booting the TWRP image.
If that works, reinstall TWRP using the zip.
Ensure you are using the 3.2.1.0 IMG and ZIP. Mismatching will cause problems.
I think you might have caused an issue when you deleted the TWRP recovery without replacing the stock recovery.
This post here might help.
Replace the Magisk with current version.

Diesel_Jeremiah said:
Are you on 8.0 or 8.1?
Which bootloader are you on?
If you are in the bootloader, does it have the error line at the bottom?
If you cycle your volume buttons and reboot bootloader, does the error go away?
If the error goes away, try flash-all again.
If not:
From the bootloader, try booting the TWRP image.
If that works, reinstall TWRP using the zip.
Ensure you are using the 3.2.1.0 IMG and ZIP. Mismatching will cause problems.
I think you might have caused an issue when you deleted the TWRP recovery without replacing the stock recovery.
This post here might help.
Replace the Magisk with current version.
Click to expand...
Click to collapse
was running 8.1 before this happened. bootloader version says mw8998-002.0059.00
there is no error that i can see in the bootloader, looks the same as when it was all functional
trying to boot twrp gives me this error
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.689s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.696s
it seems most things that i try and do give me a remote error, i feel like the partitions might be jacked up but i have no idea how to fix them

xsanikax said:
was running 8.1 before this happened. bootloader version says mw8998-002.0059.00
there is no error that i can see in the bootloader, looks the same as when it was all functional
trying to boot twrp gives me this error
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.689s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.696s
it seems most things that i try and do give me a remote error, i feel like the partitions might be jacked up but i have no idea how to fix them
Click to expand...
Click to collapse
You probably have already done it, but ensure you have the newest ADB, that's what screwed me up.

I had the same problem turns out I wasn't using the latest platform tools.
I couldn't do anything. Would boot strait to bootloader. I couldn't even power down and plug I to charge. It would take me to bootloader with an error. I managed to screw up even more by flashing the wrong image using old tools. Then I lost all options except bootloader ( no recovery or download mode).
I feel as long as you have an unlocked bootloader and you are able to use fastboot you shouldn't worry. I'm only saying this because I was scared as hell haha.
I did notice it would try to boot when switching boot slots. But I screwed that up too by trying to flash with old tools. In the end all I needed was latest Platform tools:
https://developer.android.com/studio/releases/platform-tools.html

iamnotreallyhere said:
I had the same problem turns out I wasn't using the latest platform tools.
I couldn't do anything. Would boot strait to bootloader. I couldn't even power down and plug I to charge. It would take me to bootloader with an error. I managed to screw up even more by flashing the wrong image using old tools. Then I lost all options except bootloader ( no recovery or download mode).
I feel as long as you have an unlocked bootloader and you are able to use fastboot you shouldn't worry. I'm only saying this because I was scared as hell haha.
I did notice it would try to boot when switching boot slots. But I screwed that up too by trying to flash with old tools. In the end all I needed was latest Platform tools:
https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
thanks a lot dude this is what im getting at the minute
target reported max download size of 536870912 bytes
sending 'bootloader' (38644 KB)...
OKAY [ 0.818s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.825s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.270s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.544s]
finished. total time: 1.815s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
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........: FA7AK1A08325
--------------------------------------------
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.009s
Press any key to exit...
however i have found a problem when i tried just reflashing the recovery by itself
C:\Unified_Android_Toolkit\recovery\GooglePixel2>fastboot flash recovery recovery-twrp-3.2.1.0-walleye.img
target reported max download size of 536870912 bytes
sending 'recovery' (32768 KB)...
OKAY [ 0.689s]
writing 'recovery'...
FAILED (remote: No such partition.)
finished. total time: 0.691s
seems my partitions are all jacked up, is there a way to sort that out?
oh as a side note my problems are all the same as yours i can only access the bootloader and adb will not recognize my device but fastboot will

this is what happens if i try to flash the version with the same bootloader as the one that it says is on the device
target reported max download size of 536870912 bytes
sending 'bootloader' (38728 KB)...
OKAY [ 0.815s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.821s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.271s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.544s]
finished. total time: 1.816s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
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-00122-1708311414
Serial Number........: FA7AK1A08325
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (32768 KB)...
OKAY [ 0.690s]
writing 'boot'...
OKAY [ 0.300s]
sending sparse 'system' (524284 KB)...
OKAY [ 11.668s]
writing 'system'...
OKAY [ 4.745s]
sending sparse 'system' (524284 KB)...
OKAY [ 11.632s]
writing 'system'...
OKAY [ 4.755s]
sending sparse 'system' (524284 KB)...
OKAY [ 11.597s]
writing 'system'...
OKAY [ 4.732s]
sending sparse 'system' (322348 KB)...
OKAY [ 7.126s]
writing 'system'...
OKAY [ 2.915s]
sending 'vendor' (346992 KB)...
OKAY [ 7.342s]
writing 'vendor'...
OKAY [ 3.169s]
erasing 'userdata'...
OKAY [ 0.736s]
sending 'userdata' (140906 KB)...
OKAY [ 2.954s]
writing 'userdata'...
OKAY [ 1.502s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 75.881s
Press any key to exit...

It still sounds like you are not using the latest tools. Are you installing the platform tools or are you using the extracted zip?
the script is going to use whatever is installed on your system.
The first thing I did was download: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
I used this image Android 8.1 stock: https://dl.google.com/dl/android/aosp/taimen-opm1.171019.011-factory-2df1c1cb.zip
I extracted platform tools to my desktop. I opened the file location and did a Shift > Right click - within the folder containing the tools and opened CMD or Powershell( or you can just CD to the directory).
I copied all the commands from the script and ran them one at a time making sure I was using the tools from the zip file and not my system.
and just went down the line.
Like this:
PS C:\Users\myusername\Desktop\platform-tools> C:\Users\myusername\Desktop\platform-tools\fastboot.exe --set-active=b
Setting current slot to 'b'...
OKAY [ 0.016s]
finished. total time: 0.017s
PS C:\Users\myusername\Desktop\platform-tools> cd C:\Users\myusername\Downloads\nv3
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe flash bootloader bootloader-walleye-mw8998-002.0066.00.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38644 KB)...
OKAY [ 0.829s]
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.894s]
finished. total time: 1.724s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe flash radio radio-walleye-g8998-00164-1710262031.img
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 1.293s]
writing 'radio_b'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.552s]
finished. total time: 1.848s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe -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.134s
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.020s
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 8.309s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 2.987s
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 1.721s
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: 1f46fc9a-edc7-11e7-aa2c-2daa660ba492
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........: HT696969696969
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot_b' (32768 KB)...
OKAY [ 0.699s]
writing 'boot_b'...
OKAY [ 0.001s]
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.477s]
writing 'dtbo_b'...
OKAY [ 0.001s]
erasing 'system_b'...
OKAY [ 0.316s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 11.667s]
writing 'system_b' 1/4...
OKAY [ 0.001s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 13.907s]
writing 'system_b' 2/4...
OKAY [ 0.001s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.876s]
writing 'system_b' 3/4...
OKAY [ 0.002s]
sending sparse 'system_b' 4/4 (393508 KB)...
OKAY [ 11.018s]
writing 'system_b' 4/4...
OKAY [ 0.001s]
erasing 'system_a'...
OKAY [ 2.084s]
sending sparse 'system_a' 1/2 (524284 KB)...
OKAY [ 11.561s]
writing 'system_a' 1/2...
OKAY [ 0.001s]
sending sparse 'system_a' 2/2 (57592 KB)...
OKAY [ 3.758s]
writing 'system_a' 2/2...
OKAY [ 0.001s]
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.288s]
writing 'vbmeta_b'...
OKAY [ 0.001s]
erasing 'vendor_b'...
OKAY [ 0.116s]
sending 'vendor_b' (355428 KB)...
OKAY [ 7.594s]
writing 'vendor_b'...
OKAY [ 0.001s]
Setting current slot to 'b'...
OKAY [ 1.722s]
erasing 'userdata'...
OKAY [ 0.759s]
sending 'userdata' (4669 KB)...
OKAY [ 0.108s]
writing 'userdata'...
OKAY [ 0.001s]
rebooting...
finished. total time: 80.060s
fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img
fastboot reboot-bootloader
fastboot flash radio radio-walleye-g8998-00164-1710262031.img
fastboot reboot-bootloader
fastboot -w update image-walleye-opm2.171019.012.zip

iamnotreallyhere said:
It still sounds like you are not using the latest tools. Are you installing the platform tools or are you using the extracted zip?
the script is going to use whatever is installed on your system.
The first thing I did was download: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
I used this image Android 8.1 stock: https://dl.google.com/dl/android/aosp/taimen-opm1.171019.011-factory-2df1c1cb.zip
I extracted platform tools to my desktop. I opened the file location and did a Shift > Right click - within the folder containing the tools and opened CMD or Powershell( or you can just CD to the directory).
I copied all the commands from the script and ran them one at a time making sure I was using the tools from the zip file and not my system.
and just went down the line.
Like this:
PS C:\Users\myusername\Desktop\platform-tools> C:\Users\myusername\Desktop\platform-tools\fastboot.exe --set-active=b
Setting current slot to 'b'...
OKAY [ 0.016s]
finished. total time: 0.017s
PS C:\Users\myusername\Desktop\platform-tools> cd C:\Users\myusername\Downloads\nv3
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe flash bootloader bootloader-walleye-mw8998-002.0066.00.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38644 KB)...
OKAY [ 0.829s]
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.894s]
finished. total time: 1.724s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe flash radio radio-walleye-g8998-00164-1710262031.img
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 1.293s]
writing 'radio_b'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.552s]
finished. total time: 1.848s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe -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.134s
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.020s
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 8.309s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 2.987s
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 1.721s
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: 1f46fc9a-edc7-11e7-aa2c-2daa660ba492
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........: HT696969696969
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot_b' (32768 KB)...
OKAY [ 0.699s]
writing 'boot_b'...
OKAY [ 0.001s]
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.477s]
writing 'dtbo_b'...
OKAY [ 0.001s]
erasing 'system_b'...
OKAY [ 0.316s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 11.667s]
writing 'system_b' 1/4...
OKAY [ 0.001s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 13.907s]
writing 'system_b' 2/4...
OKAY [ 0.001s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.876s]
writing 'system_b' 3/4...
OKAY [ 0.002s]
sending sparse 'system_b' 4/4 (393508 KB)...
OKAY [ 11.018s]
writing 'system_b' 4/4...
OKAY [ 0.001s]
erasing 'system_a'...
OKAY [ 2.084s]
sending sparse 'system_a' 1/2 (524284 KB)...
OKAY [ 11.561s]
writing 'system_a' 1/2...
OKAY [ 0.001s]
sending sparse 'system_a' 2/2 (57592 KB)...
OKAY [ 3.758s]
writing 'system_a' 2/2...
OKAY [ 0.001s]
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.288s]
writing 'vbmeta_b'...
OKAY [ 0.001s]
erasing 'vendor_b'...
OKAY [ 0.116s]
sending 'vendor_b' (355428 KB)...
OKAY [ 7.594s]
writing 'vendor_b'...
OKAY [ 0.001s]
Setting current slot to 'b'...
OKAY [ 1.722s]
erasing 'userdata'...
OKAY [ 0.759s]
sending 'userdata' (4669 KB)...
OKAY [ 0.108s]
writing 'userdata'...
OKAY [ 0.001s]
rebooting...
finished. total time: 80.060s
fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img
fastboot reboot-bootloader
fastboot flash radio radio-walleye-g8998-00164-1710262031.img
fastboot reboot-bootloader
fastboot -w update image-walleye-opm2.171019.012.zip
Click to expand...
Click to collapse
im doing exactly what i'm being told to but i'm still getting the same remote command flash error and the boot slot is set to a it won't let me change it to b

okay i have an update i'm all up and running again everything is fine, turns out i had to download the older version of oreo 8.0.0 from november the latest november update, then i had to download a slightly older version of fastboot and that seems to have fixed it just ran the flash-all batch file thanks everyone for their input

Nice! Now that I think of it I did try flashing Oreo 8.0 before I tried flashing 8.1. 8.0 didn't work by itself tho. So then I flashed 8.1. Maybe that's the trick to fix the partitions.

Thanks a lot
xsanikax said:
okay i have an update i'm all up and running again everything is fine, turns out i had to download the older version of oreo 8.0.0 from november the latest november update, then i had to download a slightly older version of fastboot and that seems to have fixed it just ran the flash-all batch file thanks everyone for their input
Click to expand...
Click to collapse
Thank you for the idea of using an older version of fastboot. I somehow screwed up my Pixel 2 and loaded bootloader 59 on it and couldn't update it back to 66. I had the right image but was still using the newest version of fastboot. Ended up with 26.0.2 which was the first version with Pixel 2 support. It can be found here: https://xiaomifirmware.com/downloads/download-platform-tools-adb-fastboot-r-26-0-0/
Thanks again! :good:

Unlocked my pixel 2 and tried to root through magisk and kinda screwed it up. Tried flashing older Oreo 8.0 and 8.1 as you guys tried before but now I cant get past the fastboot screen. Whenever I try to load the earlier 8.0 it tells me it requires 8.1 to upgrade. any ideas would help
target reported max download size of 536870912 bytes
sending 'bootloader' (38644 KB)...
OKAY [ 0.829s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.848s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.007s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.296s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.543s]
finished. total time: 1.845s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.006s
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........: HT7AR1A01164
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0066.00'.
finished. total time: 0.070s
Press any key to exit...

jzablocki15 said:
Unlocked my pixel 2 and tried to root through magisk and kinda screwed it up. Tried flashing older Oreo 8.0 and 8.1 as you guys tried before but now I cant get past the fastboot screen. Whenever I try to load the earlier 8.0 it tells me it requires 8.1 to upgrade. any ideas would help
target reported max download size of 536870912 bytes
sending 'bootloader' (38644 KB)...
OKAY [ 0.829s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.848s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.007s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.296s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.543s]
finished. total time: 1.845s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.006s
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........: HT7AR1A01164
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0066.00'.
finished. total time: 0.070s
Press any key to exit...
Click to expand...
Click to collapse
My dude, you would not believe the hell I went through to figure this out. So it started with me getting the Verizon Pixel 2's bootloader unlocked. I downloaded TWRP onto it, rooted it, and then downloaded a ZIP that would add various modifications to my version of android. Well, I downloaded it, flashed it , and of course it didn't work as intended. Tried finding a way to undo what I'd done (absolutely imbecilic me, I didn't back up my phone WHEN THERE WAS NO SYSTEM IMAGE FOR A VERIZON PHONE YET). I figured the Google images would work fine, but they put you through hell and highwater before they do. I attempted to revert to the current stock image. It screwed my whole system up. Couldn't boot into android, couldn't boot into ANY recovery, etc. It was essentially bricked. I went through countless different errors and threads and forums and files, until I found this one right here. Tried reverting to the old version of Oreo with old ADB and fastboot. Progress, no more error popping up. Then I tried booting up and it stayed in fastboot. Tried then updating to the latest version available from Google as you had and got the exact same line of code. With the OLD ADB AND FASTBOOT and with a file I had downloaded and tinkered with earlier and with the LATEST IMAGE FROM GOOGLE (after your step), I tried it, came up with several "faileds" and other errors, but after the script was done, I rebooted and it got to the boot animation (as it had done before) and FINALLY brought my phone to the setup wizard.
The file I used was this one: https://forum.xda-developers.com/pixel-2/development/tool-deuces-bootloop-recovery-flashing-t3725778
Recap:
Download old ADB and Fastboot
Download the latest Android 8.0 Oreo Stock Image
Flash all bat
Download latest Android 8.1 Oreo Stock Image
From there, put the downloaded script in with the image file of the latest available Android 8.1 Oreo Stock Image and run the script.
Should show errors
Reboot once it's finished
Should be fine.
Keep in mind, this was a Verizon Pixel 2 and it worked fine for me. Couldn't guarantee it'd work for you, and there may have even been precursor steps before this post that I took and didn't keep track of that might have contributed to an extremely lucky brick save.
Long story short folks, if you're on an unlocked bootloader Verizon, don't do anything you can't live with for a while until we've got a proper backdoor developed for us.

Read my message right above your original post. Get the image for oreo 8.0 (nov) and use the fastboot version fron the site I linked to. Should have the 59 bootloader. After it boots, just do the OTA update twice. Check the build number and then get that image from Google to root the boot.img file. All good.

Yupp, just used the tool and saved a couple hundred bucks and a pair of underwear. Really is phone saver. And I'm for sure going to wait until a less risky root is available. I was able to flash the tool with factory image 66 version bootloader, just make sure to have tool in the same folder as the unzipped bootloader and files.

I haven't posted in at least 2 years. Wanted to thank everyone in this thread for the detailed troubleshooting. I locked my bootloader without doing the prep work and this saved me from a fiasco the week before my vacation.