Develop Bugs

Bootloader Reports Unlocked, Unable to Flash Custom Recovery/Re-Lock Bootloader

Greetings,
So I suppose I made the mistake of not locking the bootloader before flashing the factory NRD91D image. Current situation is that my Pixel C is reporting unlocked bootloader but I can't flash TWRP. Fastboot indicates a successful recovery flash but when booting into recovery it comes up with the sad little dead android and "No command".
My goal is to get rooted N, obviously. TWRP would be nice.
I think I read somewhere that I can:
1. Flash factory 6.0.1
2. Flash TWRP
3. Wipe everything
4. Root
5. Lock bootloader
6. Flash factory OTA to N using Flashfire with SuperSU Injection.
I've been trying adb fastboot and I sprung for skipsoft hoping it could magically bail me out but no luck.
Anybody else stuck in this situation? Does anybody have 7.0.0 rooted with TWRP? If so what steps did you use?
Thanks in advance for any help or advice.

I been using Skipsoft and its saying the device is unlocked. The bootloader screen says its unlocked at the bottom, but also says no recovery OS is corrupted. I've tried to lock it with oem lock/unlock as well as flashing unlock. The system does not report errors while unlocking/locking, but I'm unable to flash anything.
sending 'bootloader' (16384 KB)...
OKAY [ 0.423s]
writing 'bootloader'...
FAILED (remote: unsupported command)
or
$ fastboot boot twrp.img
creating boot image...
creating boot image - 13035520 bytes
downloading 'boot.img'...
OKAY [ 0.388s]
booting...
FAILED (remote: image verification failed)
finished. total time: 0.391s
This happens on my Mac and Windows machine (in case someone thinks its a driver issue)

type fastboot flashing/flash lock ( try flash or flashing)
wait that user data partition is regolar formatted
and now you are able of unlock and wait for userdata formatted
now you can flash rom

Alessandro999 said:
type fastboot flashing/flash lock ( try flash or flashing)
wait that user data partition is regolar formatted
and now you are able of unlock and wait for userdata formatted
now you can flash rom
Click to expand...
Click to collapse
Thank for replying.
Keep in mind When I click [Reboot into Android Recovery] it only reboots to the bootloader I've included a picture of that.
jatilq$ ./fastboot flashing lock
...
OKAY [ 3.963s]
finished. total time: 3.963s
jatilq$ ./fastboot flashing unlock
...
OKAY [ 2.306s]
finished. total time: 2.306s
jatilq$ ./fastboot boot twrp.img
< waiting for any device >
creating boot image...
creating boot image - 13035520 bytes
downloading 'boot.img'...
OKAY [ 0.369s]
booting...
FAILED (remote: image verification failed)
finished. total time: 0.372s
jatilq$ ./fastboot oem lock
...
OKAY [ 23.284s]
finished. total time: 23.284s
jatilq$ ./fastboot oem unlock
...
OKAY [ 2.683s]
finished. total time: 2.683s
jatilq$ ./fastboot flash bootloader bootloader-dragon-google_smaug.7900.67.0.img
target reported max download size of 268435456 bytes
sending 'bootloader' (16384 KB)...
OKAY [ 0.480s]
writing 'bootloader'...
FAILED (remote: unsupported command)
finished. total time: 0.482s
It finishes about 5 min after 'archive does not contain system.sig
jatilq$ ./fastboot -w update image-ryu-n2g48b.zip
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 57825820672
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14117632
Block groups: 431
Reserved block group size: 1024
Created filesystem with 11/3530752 inodes and 267682/14117632 blocks
wiping cache...
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
--------------------------------------------
Bootloader Version...: Google_Smaug.7900.50.0
Baseband Version.....: N/A
Serial Number........: unknown variable
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking partition-size:system...
OKAY [ 0.016s]
erasing 'boot'...
FAILED (remote: unsupported command)
finished. total time: 0.029s
./fastboot flash boot recovery.img
target reported max download size of 268435456 bytes
erasing 'boot'...
FAILED (remote: unsupported command)
finished. total time: 0.001s
These are most of the commands I've tried. This is on my mac. The windows machine SKipSoft will say it's unlocked, but during flashing will throw back that it's locked (bootloader reports unlocked)
I included photos to show it does say it locks/unlocks.
I contacted Google and that was a disturbing experience. Both times you can tell support is reading from a script. They both promised someone from 2 tier would contact me, so far nothing. I'm willing to pay to have the thing repaired, but sadly you need the 2nd tier person to call you to even find out if that's possible.

ok but you must wait that after lock/unlock bootloader the userdata is formatted automaticcaly!
reboot into fastboot
type fastboot flashing/flash lock and waith that userdata is auto formatted
flash stock firmware
if you dont do this the error still persist due to damaged userdata partition
---------- Post added at 10:17 AM ---------- Previous post was at 10:07 AM ----------
i want help you .... i ve got this error last month and i fixed with this.... follow this tut:
- use a pc with windows 7 installed
-download google usb driver ( adb and fastboot) latest
reboot device into bootloader mode , connect it and open terminal and use fastboot flash/ flashing lock ( now pixel c will automatic format userdata partition corrupted)
after the process is ended( 5/10 minutes) you are able to back to stock ... dont try to flash tpwr , first i reccomend factory image 7.1.2 august for pixel c
after flash stock reboot configure the sofware , go on setting and if the device is already unlock reboot info fastboot and flash tpwr ( fastboot flash recovery recoveryname.img)
i reccoment latest stable tpwr
actually i have this and i have resurrection remix latest + f2fs data cache+ xceed foolowsi kernel with fsync off, zen scheduler
very smooth and fast
every time you lock/unlock bootloader you must wait that userdata is formatted by device ( this during 5/10 minutes usually)

I pasted the output before to show that I've done as you suggested several times. It says its unlocked after the lock/unlock process (look at my previous commands). Once you input those commands, you hit power to say yes and the device will reboot. The below process is from SkipSoft Android Toolkit to better explain the issue as explained in the title of this thread.
Are you ready to start? Type y[yes] or n[no]:y
Device mode detected: Fastboot Mode
Device Serial Number:
Device Bootloader State: Locked
When prompted, Press the Power button on the device to Unlock the Bootloader.
If it is already unlocked then this will just be skipped and your device will not
be wiped. After unlocking the device will reboot to recovery to erase the device.
Sending flashing unlock command to device..
Device bootloader is already unlocked so no data will be wiped
Rebooting back to Android..
rebooting...
finished. total time: -0.000s
Press any key to return to the Main Menu..

jatilq said:
erasing 'boot'...
FAILED (remote: unsupported command)
Click to expand...
Click to collapse
I had this issue and fixed it with fwtool
boot into recovery, then
Code:
adb shell
fwtool vbnv write dev_boot_fastboot_full_cap 1

jatilq said:
Thank for replying.
Keep in mind When I click [Reboot into Android Recovery] it only reboots to the bootloader I've included a picture of that.
jatilq$ ./fastboot flashing lock
...
OKAY [ 3.963s]
finished. total time: 3.963s
jatilq$ ./fastboot flashing unlock
...
OKAY [ 2.306s]
finished. total time: 2.306s
jatilq$ ./fastboot boot twrp.img
< waiting for any device >
creating boot image...
creating boot image - 13035520 bytes
downloading 'boot.img'...
OKAY [ 0.369s]
booting...
FAILED (remote: image verification failed)
finished. total time: 0.372s
jatilq$ ./fastboot oem lock
...
OKAY [ 23.284s]
finished. total time: 23.284s
jatilq$ ./fastboot oem unlock
...
OKAY [ 2.683s]
finished. total time: 2.683s
jatilq$ ./fastboot flash bootloader bootloader-dragon-google_smaug.7900.67.0.img
target reported max download size of 268435456 bytes
sending 'bootloader' (16384 KB)...
OKAY [ 0.480s]
writing 'bootloader'...
FAILED (remote: unsupported command)
finished. total time: 0.482s
It finishes about 5 min after 'archive does not contain system.sig
jatilq$ ./fastboot -w update image-ryu-n2g48b.zip
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 57825820672
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14117632
Block groups: 431
Reserved block group size: 1024
Created filesystem with 11/3530752 inodes and 267682/14117632 blocks
wiping cache...
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
--------------------------------------------
Bootloader Version...: Google_Smaug.7900.50.0
Baseband Version.....: N/A
Serial Number........: unknown variable
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking partition-size:system...
OKAY [ 0.016s]
erasing 'boot'...
FAILED (remote: unsupported command)
finished. total time: 0.029s
./fastboot flash boot recovery.img
target reported max download size of 268435456 bytes
erasing 'boot'...
FAILED (remote: unsupported command)
finished. total time: 0.001s
These are most of the commands I've tried. This is on my mac. The windows machine SKipSoft will say it's unlocked, but during flashing will throw back that it's locked (bootloader reports unlocked)
I included photos to show it does say it locks/unlocks.
I contacted Google and that was a disturbing experience. Both times you can tell support is reading from a script. They both promised someone from 2 tier would contact me, so far nothing. I'm willing to pay to have the thing repaired, but sadly you need the 2nd tier person to call you to even find out if that's possible.
Click to expand...
Click to collapse
Hello,
I have the exact error that you show in the screenshots. I follow your steps and I´m stuck with the same problem. Finally you can solve the problem? I´m totally frustrated withg this tablet and need some help.
Thanks in advance.

Istvan_86 said:
Hello,
I have the exact error that you show in the screenshots. I follow your steps and I´m stuck with the same problem. Finally you can solve the problem? I´m totally frustrated withg this tablet and need some help.
Thanks in advance.
Click to expand...
Click to collapse
Unfortunately I jumped through many hoops with Google before then sent me a one time replacement. I sold the tablet and now I'm on a Samsung Galaxy Tab3.

jatilq said:
Unfortunately I jumped through many hoops with Google before then sent me a one time replacement. I sold the tablet and now I'm on a Samsung Galaxy Tab3.
Click to expand...
Click to collapse
Hello and thanks for your answer. So basically I must contact Google as you did?
I think that I'm totally done with this tablet......

Istvan_86 said:
Hello and thanks for your answer. So basically I must contact Google as you did?
I think that I'm totally done with this tablet......
Click to expand...
Click to collapse
As I said you will have to jump through many hoops. They will want you to email support, then you have to wait for a call back. Expect no one to be able to help you, even though they will keep bouncing you around. I'm not sure if its 100% guarantee they will send a replacement after a few contacts. If they do send you one, prepare to have them hold around $550 for the refurbished unit to be sent and the old one returned to them. I sold the new one as fast as I could on swappa, because of the lack of recovery options for the device and the messed up unlock/lock flag error that this thread is talking about.

Using fwtool command worked beautifully
xavierbutt said:
I had this issue and fixed it with fwtool
boot into recovery, then
Code:
adb shell
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
I had a situation where I locked and unlocked in fastboot and still had TWRP recovery installed so the OS protection kicked in and prevented me from booting up normally.
I booted into TWRP recovery where TWRP has built in root access.
I copied the fwtool to the SDcard while the tablet was booted up normally using the PC but, if you can't boot up, ADB push command from a PC would have also placed the fwtool onto the tablet sdcard (adb push fwtool /sdcard).
I used the command adb shell and thus was sitting on the sdcard root where the fwtool was placed. I issued the fwtool command directly from the sdcard location. I did not copy the fwtool to any place else.
adb shell
fwtool vbnv write dev_boot_fastboot_full_cap 1
The command was successful and, I was then able to have full flash access back.
Regards galearned

Thanks @galearned your instruction saved me! Because I didn't get adb to work I used the terminal of TWRP and it worked!
---------- Post added at 09:54 PM ---------- Previous post was at 09:54 PM ----------
Thanks @galearned your instruction saved me! Because I didn't get adb to work I used the terminal of TWRP and it worked!

Thanks @galearned greatful my pixel c is worked again
---------- Post added at 03:36 PM ---------- Previous post was at 03:36 PM ----------
Thanks @galearned greatful my pixel c is worked again

Sorry for the Resurrection. Can somebody explain how they fixed this, I have the same situation exactly. Access to TWRP and fastboot etc, but the dreaded FAILED (remote: unsupported command) stops me in my tracks. I can only lock and unlock the bootloader.

How to flash factory image?

I'm not new to flashing the images... But Jesus Christ there's a lot going on with the pixel... There's not just a system, vendor, boot, recovery, and cache IMG now... There's a ****load and I'm not sure how to flash them... And when I run the flash all.bat I keep getting an error during the flash and it just pauses... Same goes for the skipsoft tool. Anyone know how to flash these?

Drivers. Search on how to verify your drivers are up to date and installed.

Am I able to flash the images separately though? I do I have to use the flash all script?

swapavi said:
Am I able to flash the images separately though? I do I have to use the flash all script?
Click to expand...
Click to collapse
Not usually.
And some dev's hate the bat due to Windows being stupid sometimes.
Many folks will flash individual files one at a time.
I however, am unfamiliar with the Pixel XL partition setup too, so I would totally wait for a higher level dev to come along and answer before I do anything.
I actually posted a similar question in the factory images thread over on the development sub forum for Pixel XL.

I am also having issue flashing the marlin-nde63p using the flash-all.bat with the 128GB Pixel XL phone from google. It keeps erroring out with the following [FAILED (remote: partition [boota] doesn't exist)]. Anyone know how to fix this?
C:\pixelxl\marlin-nde63p>
C:\pixelxl\marlin-nde63p>flash-all
target reported max download size of 536870912 bytes
sending 'bootloadera' (32820 KB)...
OKAY [ 0.823s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
OKAY [ 1.046s]
finished. total time: 1.877s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.018s
target reported max download size of 536870912 bytes
sending 'radioa' (57048 KB)...
OKAY [ 1.349s]
writing 'radioa'...
OKAY [ 0.895s]
finished. total time: 2.251s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.018s
< waiting for any 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'
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........:XXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.047s]
checking version-baseband...
OKAY [ 0.046s]
sending 'boota' (26481 KB)...
OKAY [ 0.689s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.156s
Press any key to exit...

Ok I literally just did this because I messed up my pixel xl 128gb after rooting it today.
First off I had my luck with minimum adb and fastboot, install it and go to your computer and find where its downloaded. (Ex. Mine was in C:> programs x86> minimal adb and fastboot folder). After you have located, find you image you just downloaded from Google and extract the files there should be 6 (I am a Verizon user and used the H update from the Google site). Copy all those 6 extracted files into that folder you located earlier (minimal adb and fastboot) and just click on the flash-all file you just dropped in there an sit back and let it do its thing

jscharf10 said:
Ok I literally just did this because I messed up my pixel xl 128gb after rooting it today.
First off I had my luck with minimum adb and fastboot, install it and go to your computer and find where its downloaded. (Ex. Mine was in C:> programs x86> minimal adb and fastboot folder). After you have located, find you image you just downloaded from Google and extract the files there should be 6 (I am a Verizon user and used the H update from the Google site). Copy all those 6 extracted files into that folder you located earlier (minimal adb and fastboot) and just click on the flash-all file you just dropped in there an sit back and let it do its thing
Click to expand...
Click to collapse
------------------------------
hi all semi-noob here... pls excuse any silly comments i make
background - i have twrp installed on my vzn pixel xl... bootloader is unlocked
so i copied all the 6 extracted files into the minimal adb and fastboot folder
i ran the flash-all file
cmd window popped up and just says "< waiting for any device >"
my phone is plugged into my pc via usb cable
question - what mode do i need to be in to flash the factory image?

@peterlee928
2 simple things to make sure one you have all your drivers installed and two that you are in bootloader mode!
---------- Post added at 04:55 PM ---------- Previous post was at 04:54 PM ----------
[/COLOR @peterlee928
2 simple things to make sure one you have all your drivers installed and two that you are in bootloader mode!

jscharf10 said:
@peterlee928
2 simple things to make sure one you have all your drivers installed and two that you are in bootloader mode!
---------- Post added at 04:55 PM ---------- Previous post was at 04:54 PM ----------
[/COLOR @peterlee928
2 simple things to make sure one you have all your drivers installed and two that you are in bootloader mode!
Click to expand...
Click to collapse
thx jscharf

Use The Unified Android Toolkit
swapavi said:
I'm not new to flashing the images... But Jesus Christ there's a lot going on with the pixel... There's not just a system, vendor, boot, recovery, and cache IMG now... There's a ****load and I'm not sure how to flash them... And when I run the flash all.bat I keep getting an error during the flash and it just pauses... Same goes for the skipsoft tool. Anyone know how to flash these?
Click to expand...
Click to collapse
I had the exact same issue that you are having, another user on here recommended that I use the Unified Android Toolkit to flash the factory image. It works perfectly, and also has a bunch of other useful features (some will be more useful as the community figures out this system partition thing).
The toolkit is great and no necessary features must be paid for. This will solve your error issue. Best of luck!
Find the toolkit here: https://skipsoft.net/

Pixel 2 XL bricked

I was trying to flash android 8.1 to my new Pixel 2 XL after it didn't OTA well, then the device got stuck in bootloop,
then decided to go back to 8.0 and got the error: Cannot generate image for userdata
full :
target reported max download size of 536870912 bytes
sending 'bootloader_a' (55680 KB)...
OKAY [ 47.517s]
writing 'bootloader_a'...
OKAY [ 0.552s]
finished. total time: 48.072s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 51.809s]
writing 'radio_a'...
OKAY [ 0.566s]
finished. total time: 52.379s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.253s
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.034s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1867 MB) to disk... took 12.752s
archive does not contain 'system.sig'
extracting system_other.img (590 MB) to disk... took 4.501s
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 (341 MB) to disk... took 2.588s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
CreateProcess failed: %1 is not a valid Win32 application. (193)
error: Cannot generate image for userdata
Press any key to exit...
anyone has any idea how to solve it ?
before flashing the device was rooted with magisk and had twrp installed

I had the same error on MacOS, no idea how to resolve it so I used the skipsoft toolkit to flash-all

Make sure you have the latest fastboot binary installed from Google.
I'd try and flash January Security again. It should work if you run the flash-all

you can try this method, it really helped me when an update didn't work. I use it now to make every update, so I don't have any problems.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

thanks for the answers I tried flash-all with the latest android platform tools this is what gave me the error of image for userdata...
SkipSoft doesn't seem to support the new 2017 Pixel 2 XL..

phildenice said:
you can try this method, it really helped me when an update didn't work. I use it now to make every update, so I don't have any problems.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
yeah I tried it gave me the same error of the userdata image..

You could try to unzip system.img and flash individually

hi I also tried flashing individualy (after flash-all failed) and I got the same error - userdata.img

You could try to unzip system.img and flash individually

You might wanna try using fastboot to format the userdata partition; be sure to format partition on both a & b slots...
If you need help or more clarification, let me know...
Hope this helps...

Sorry I didn't see your answer
---------- Post added at 11:27 AM ---------- Previous post was at 11:18 AM ----------
And try :
fastboot format userdata
to see if solves the issue

REM_8 said:
I was trying to flash android 8.1 to my new Pixel 2 XL after it didn't OTA well, then the device got stuck in bootloop,
then decided to go back to 8.0 and got the error: Cannot generate image for userdata
.................................
Click to expand...
Click to collapse
A few things to check that have messed other users up as well:\
make sure you unzipped the factory image then unzip the second zip file for the boot img
make sure OEM unlock is ON
make sure USB Debugging is ON
make sure you have a 2.0 USB cable
try rebooting your PC
make sure your SDK tools are the LATEST version
make sure you're getting your command prompt in the same folder as your platform tools
not saying these will fix your issue, but have seen these trip up others..
Good luck.

Az Biker said:
A few things to check that have messed other users up as well:\
make sure you unzipped the factory image then unzip the second zip file for the boot img
make sure OEM unlock is ON
make sure USB Debugging is ON
make sure you have a 2.0 USB cable
try rebooting your PC
make sure your SDK tools are the LATEST version
make sure you're getting your command prompt in the same folder as your platform tools
not saying these will fix your issue, but have seen these trip up others..
Good luck.
Click to expand...
Click to collapse
Flash-all doesn't like unzipping the second folder. At least it didn't for me.

Larzzzz82 said:
Flash-all doesn't like unzipping the second folder. At least it didn't for me.
Click to expand...
Click to collapse
Extract the secondary zip, and place it in your SDK platform-tools folder. Then try again.

I did that. That's why I said flash-all doesn't like that. I moved the unzipped second folder into my platform tools folder and all went well.
Flashing this device is nothing like Shamu was.

Larzzzz82 said:
I did that. That's why I said flash-all doesn't like that. I moved the unzipped second folder into my platform tools folder and all went well.
Flashing this device is nothing like Shamu was.
Click to expand...
Click to collapse
I hear that bro. Not like the 6p either. But we'll manage :good:

Lost and need help after unrooting

As the title says, I had rooted my device, but after about 2 months, decided I wanted to unroot, and go back to normal. I will let you know the steps I took, and the problem I am currently facing to see if anyone can provide some help.
1. I performed a factory reset
2. I flashed my stock boot.img that I backed up prior to rooting with Magisk
3. I booted the device, and factory reset again
4. I locked my bootloader, and then tried to apply my OTA Update (installation failed).
5. After referencing a few google support articles, they suggested to flash the latest Factory Image with the flash-all script.
6. I unlocked my bootloader
7. booted to fastboot, and ran flash-all.bat
8. The Factory image failed on Sending 'product'
9. I modified the flash-all.bat file, and removed the -w from the fastboot update section, and ran it again.
10. Factory image failed on Sending 'product' again
11. I manually sent the command through fastboot. "fastboot update image-crosshatch-qp1a.191005.007.zip (please note, I this is the October factory image, I also tried all of the above with the November factory image with the same failuer).
This is what is displayed when the update is attempted. can someone help me understand what steps I am missing.
C:\Android\Sdk\platform-tools>fastboot update image-crosshatch-qp1a.191005.007.zip
--------------------------------------------
Bootloader Version...: b1c1-0.2-5672671
Baseband Version.....: g845-00048-190722-B-5745561
Serial Number........: 8CRY16G6K
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.057s]
Checking 'version-bootloader' OKAY [ 0.058s]
Checking 'version-baseband' OKAY [ 0.056s]
Setting current slot to 'b' OKAY [ 0.372s]
extracting boot.img (64 MB) to disk... took 0.300s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 0.325s]
Writing 'boot_b' OKAY [ 0.207s]
extracting dtbo.img (8 MB) to disk... took 0.029s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.126s]
Writing 'dtbo_b' OKAY [ 0.074s]
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.116s]
Writing 'vbmeta_b' OKAY [ 0.057s]
archive does not contain 'vbmeta_system.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.057s]
< waiting for any device >
Sending 'system_b' (4 KB) OKAY [ 0.002s]
Updating super partition OKAY [ 0.022s]
Resizing 'product_b' OKAY [ 0.006s]
Resizing 'system_b' OKAY [ 0.006s]
Resizing 'vendor_b' OKAY [ 0.006s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1985 MB) to disk... took 13.550s
archive does not contain 'product.sig'
Sending 'product' (2033548 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed

Khilbron said:
As the title says, I had rooted my device, but after about 2 months, decided I wanted to unroot, and go back to normal. I will let you know the steps I took, and the problem I am currently facing to see if anyone can provide some help.
1. I performed a factory reset
2. I flashed my stock boot.img that I backed up prior to rooting with Magisk
3. I booted the device, and factory reset again
4. I locked my bootloader, and then tried to apply my OTA Update (installation failed).
5. After referencing a few google support articles, they suggested to flash the latest Factory Image with the flash-all script.
6. I unlocked my bootloader
7. booted to fastboot, and ran flash-all.bat
8. The Factory image failed on Sending 'product'
9. I modified the flash-all.bat file, and removed the -w from the fastboot update section, and ran it again.
10. Factory image failed on Sending 'product' again
11. I manually sent the command through fastboot. "fastboot update image-crosshatch-qp1a.191005.007.zip (please note, I this is the October factory image, I also tried all of the above with the November factory image with the same failuer).
This is what is displayed when the update is attempted. can someone help me understand what steps I am missing.
C:\Android\Sdk\platform-tools>fastboot update image-crosshatch-qp1a.191005.007.zip
--------------------------------------------
Bootloader Version...: b1c1-0.2-5672671
Baseband Version.....: g845-00048-190722-B-5745561
Serial Number........: 8CRY16G6K
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.057s]
Checking 'version-bootloader' OKAY [ 0.058s]
Checking 'version-baseband' OKAY [ 0.056s]
Setting current slot to 'b' OKAY [ 0.372s]
extracting boot.img (64 MB) to disk... took 0.300s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 0.325s]
Writing 'boot_b' OKAY [ 0.207s]
extracting dtbo.img (8 MB) to disk... took 0.029s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.126s]
Writing 'dtbo_b' OKAY [ 0.074s]
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.116s]
Writing 'vbmeta_b' OKAY [ 0.057s]
archive does not contain 'vbmeta_system.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.057s]
< waiting for any device >
Sending 'system_b' (4 KB) OKAY [ 0.002s]
Updating super partition OKAY [ 0.022s]
Resizing 'product_b' OKAY [ 0.006s]
Resizing 'system_b' OKAY [ 0.006s]
Resizing 'vendor_b' OKAY [ 0.006s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1985 MB) to disk... took 13.550s
archive does not contain 'product.sig'
Sending 'product' (2033548 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Click to expand...
Click to collapse
Do you have the latest sdk platform tools?

jd1639 said:
Do you have the latest sdk platform tools?
Click to expand...
Click to collapse
I thought I was, I just checked, and apparently I need to update my platform-tools, as they changed with the November build release. I will update and get back to you.
EDIT:
I will note, I had the latest platform-tools as of 10/28/2019, but when I checked Android studio, it showed there was a new version.

Khilbron said:
I thought I was, I just checked, and apparently I need to update my platform-tools, as they changed with the November build release. I will update and get back to you.
EDIT:
I will note, I had the latest platform-tools as of 10/28/2019, but when I checked Android studio, it showed there was a new version.
Click to expand...
Click to collapse
Looks like your fastboot directory is not mapped properly in environment variables. The easy way past that error is with your phone still connected and in fastbootd use the arrow keys to go to recovery and then do sideload from ADB and slieload the same version as you were trying to flash. that will do the same thing as flash-all (without -w) except it will change your slots.

sliding_billy said:
Looks like your fastboot directory is not mapped properly in environment variables. The easy way past that error is with your phone still connected and in fastbootd use the arrow keys to go to recovery and then do sideload from ADB and slieload the same version as you were trying to flash. that will do the same thing as flash-all (without -w) except it will change your slots.
Click to expand...
Click to collapse
I actually tried that while waiting on a reply to this post, when I did the sideload on the update file, it failed due to signature.
I then downloaded the Full OTA, and was able to sideload it sucessfully, but I would much rather prefer to flash the latest Factory Image, and have comfort knowing that my issue was an issue with the platform tools version.

jd1639 said:
Do you have the latest sdk platform tools?
Click to expand...
Click to collapse
Alright, using Platform Tools 29.0.5, I am still receiving the same error when attempting to run flash-all.bat with and without the -w. Even when manually executing fastboot update image-crosshatch-qp1a.191105.003.zip
I know that I can boot to recovery, and ADB sideload the latest Full OTA, that was previously successful. However, I want to make sure that I won't encounter any future problems doing OTA updates through the device.
Do you have any additional suggestions?

Khilbron said:
Alright, using Platform Tools 29.0.5, I am still receiving the same error when attempting to run flash-all.bat with and without the -w. Even when manually executing fastboot update image-crosshatch-qp1a.191105.003.zip
I know that I can boot to recovery, and ADB sideload the latest Full OTA, that was previously successful. However, I want to make sure that I won't encounter any future problems doing OTA updates through the device.
Do you have any additional suggestions?
Click to expand...
Click to collapse
- Change USB port or change USB Cable.
- Make sure the USB port you are using is not a charging USB port.
Also, if you are going to lock the bootloader make sure you are 100 percent stock if you do not want to brick your phone. Flash factory image with -w.

Khilbron said:
I actually tried that while waiting on a reply to this post, when I did the sideload on the update file, it failed due to signature.
I then downloaded the Full OTA, and was able to sideload it sucessfully, but I would much rather prefer to flash the latest Factory Image, and have comfort knowing that my issue was an issue with the platform tools version.
Click to expand...
Click to collapse
Glad you at least got out of the error, and as you noticed I did mean the full OTA. Just be sure to add the directory containing Fastboot to your PATH environment variable (the flash-all script must be able to find it). Easy way to check if your path is mapped OK, shift+right click to open a command prompt somewhere other than where you have fastboot (like your desktop) and run a fatboot devices command from there to see if it executes.

Homeboy76 said:
- Change USB port or change USB Cable.
- Make sure the USB port you are using is not a charging USB port.
Also if you are going to lock the bootloader make sure you are 100 percent stock if you do not want to brick your phone. Flash factory image with -w.
Click to expand...
Click to collapse
I've tried both USB 3.0 ports on my laptop, both USB 3.0 ports on my Docking station, as well as the Type-C port on both the laptop and docking station, all give the same error.
I have tried flashing the factory image with and without -w, which is where this problem comes, It fails everytime trying to flash it. I have currently sideloaded the latest Full OTA, and I am awaiting additional steps that I haven't thought of before I re-lock.

sliding_billy said:
Glad you at least got out of the error, and as you noticed I did mean the full OTA. Just be sure to add the directory containing Fastboot to your PATH environment variable (the flash-all script must be able to find it).
Click to expand...
Click to collapse
I modified the Flash-All script to change the path to the platform-tools installation directory, which did not resolve the issue.
Until further information I haven't tried comes up, I have sideloaded the Full OTA, and will sit with my bootloader unlocked for the time being.

Khilbron said:
I modified the Flash-All script to change the path to the platform-tools installation directory, which did not resolve the issue.
Until further information I haven't tried comes up, I have sideloaded the Full OTA, and will sit with my bootloader unlocked for the time being.
Click to expand...
Click to collapse
Just one thing before you waste any more time doing other stuff, loading the OTA only installs to the opposite slot. Do it once more to get back to your original slot and have the OTA in both. Is your hesitance to check the path due to running a MAC? If so, just dump the extracted image (including the flash-all .bat or .sh) directly into your fastboot directory including fastboot itself.

sliding_billy said:
Just one thing before you waste any more time doing other stuff, loading the OTA only installs to the opposite slot. Do it once more to get back to your original slot and have the OTA in both. Is your hesitance to check the path due to running a MAC? If so, just dump the extracted image (including the flash-all .bat or .sh) directly into your fastboot directory including fastboot itself.
Click to expand...
Click to collapse
Naa, I'm on a PC. I have tried 2 flash-all files, the original with the files copied to SYSTEM32, and a modified one, that points directly to my platform-tools directory.
This is the default Flash-All
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-crosshatch-b1c1-0.2-5672671.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-crosshatch-g845-00048-190722-b-5745561.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-crosshatch-qp1a.191105.003.zip
echo Press any key to exit...
pause >nul
exit
Click to expand...
Click to collapse
and this is the modified file, both generate the same issue
PATH=%PATH%;"C:\Users\cmears\AppData\Local\Android\Sdk\platform-tools"
fastboot flash bootloader bootloader-crosshatch-b1c1-0.2-5672671.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-crosshatch-g845-00048-190722-b-5745561.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-crosshatch-qp1a.191105.003.zip
echo Press any key to exit...
pause >nul
exit
Click to expand...
Click to collapse
Note: I also have another copy of the original Flash-All without the -w, that also generates the error.

Khilbron said:
I modified the Flash-All script to change the path to the platform-tools installation directory, which did not resolve the issue.
Until further information I haven't tried comes up, I have sideloaded the Full OTA, and will sit with my bootloader unlocked for the time being.
Click to expand...
Click to collapse
Khilbron said:
I modified the Flash-All script to change the path to the platform-tools installation directory, which did not resolve the issue.
Until further information I haven't tried comes up, I have sideloaded the Full OTA, and will sit with my bootloader unlocked for the time being.
Click to expand...
Click to collapse
There is no need the modify the flash-all.bat file.
- Did you extract the factory image in the Platform-tools folder or whatever folder that has fastboot in it?
- Did you open a 'command prompt' in the Platform-tools folder?
- Did you check the sha256 of the factory image you downloaded?
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Look at #4 in the guide.

Homeboy76 said:
There is no need the modify the flash-all.bat file.
- Did you extract the factory image in the Platform-tools folder or whatever folder that has fastboot in it?
- Did you open a 'command prompt' in the Platform-tools folder?
- Did you check the sha256 of the factory image you downloaded?
https://forum.xda-developers.com/pi...-10-q-root-t3996969/post80774791#post80774791
Look at #4 in the guide.
Click to expand...
Click to collapse
1. Yes, I extracted it to the platform-toosl directory
2. Yes I executed the flash-all from command prompt, in the platform-tools directory.
3. Yes, the Hash matches the Checksum listed on the Factory Image page for Google
Just for record, during the flash-all process, it successfully flashes the Bootloader, and the radio. It only fails on the update flash, at the Product stage.

Khilbron said:
1. Yes, I extracted it to the platform-toosl directory
2. Yes I executed the flash-all from command prompt, in the platform-tools directory.
3. Yes, the Hash matches the Checksum listed on the Factory Image page for Google
Just for record, during the flash-all process, it successfully flashes the Bootloader, and the radio. It only fails on the update flash, at the Product stage.
Click to expand...
Click to collapse
Ok!

Homeboy76 said:
There is no need the modify the flash-all.bat file.
- Did you extract the factory image in the Platform-tools folder or whatever folder that has fastboot in it?
- Did you open a 'command prompt' in the Platform-tools folder?
- Did you check the sha256 of the factory image you downloaded?
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Look at #4 in the guide.
Click to expand...
Click to collapse
Khilbron said:
1. Yes, I extracted it to the platform-toosl directory
2. Yes I executed the flash-all from command prompt, in the platform-tools directory.
3. Yes, the Hash matches the Checksum listed on the Factory Image page for Google
Click to expand...
Click to collapse
I wonder if Google did something with the flash-all script in November or if it is having problems with fastbootd, or if it based on the October install leading up to it because there seem to be more than a normal amount of flash-all issues. I'm on custom, so I am using a sideload method. Strange idea, but since ultimately you are looking to clean wipe. Do a factory reset and then a flash-all to both slots.

sliding_billy said:
I wonder if Google did something with the flash-all script in November or if it is having problems with fastbootd, or if it based on the October install leading up to it because there seem to be more than a normal amount of flash-all issues. I'm on custom, so I am using a sideload method. Strange idea, but since ultimately you are looking to clean wipe. Do a factory reset and then a flash-all to both slots.
Click to expand...
Click to collapse
If he does a factory reset on his phone, I don't think a flash-all is necessary.

Homeboy76 said:
If he does a factory reset on his phone, I don't think a flash-all is necessary.
Click to expand...
Click to collapse
No, just wondering if the command script will work.

Homeboy76 said:
If he does a factory reset on his phone, I don't think a flash-all is necessary.
Click to expand...
Click to collapse
I did do a factory reset on my device, after I sideloaded the October OTA. But when I tried to download the update manually through my device, It failed to install, so I had to unlock my bootloader again, and sideload the november OTA. I am trying to get away from having to sideload any OTA updates, and just update directly through my phone, so I don't have to keep it tethered to a PC to update. And I want to keep my bootloader locked, to avoid issues with Google Pay.

Khilbron said:
I did do a factory reset on my device, after I sideloaded the October OTA. But when I tried to download the update manually through my device, It failed to install, so I had to unlock my bootloader again, and sideload the november OTA. I am trying to get away from having to sideload any OTA updates, and just update directly through my phone, so I don't have to keep it tethered to a PC to update. And I want to keep my bootloader locked, to avoid issues with Google Pay.
Click to expand...
Click to collapse
if you are 100 percent stock you should have no problem taking the OTA without unlocking the bootloader.

Please Help. unable to flash Factory Image for Pixel XL

Hi guys,
Please help me with my phone.
I have my pixel XL rooted and accidentally upgraded to android 10 and lost my root.
However, when i was in the process of trying to re-root the phone, i probably did something stupid and got my phone soft bricked with the phone turning into to a bootloop showing the Google sign and the screen on booting up.
I am able to enter the bootloader screen and tried to flash the Factory Stock image, from the old version such as 7.1.0 to the new version 10.0.0 but failed.
This is the message i got every time i flash the factory image.
============================================================
Microsoft Windows [版本 10.0.18362.720]
(c) 2019 Microsoft Corporation. 著作權所有，並保留一切權利。
D:\Program Files (x86)\Android\Minimal ADB and Fastboot\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32480 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.060s]
finished. total time: 2.950s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_a' (57156 KB)...
OKAY [ 1.550s]
writing 'radio_a'...
OKAY [ 0.498s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.053s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (30 MB) to disk... took 0.325s
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 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1998 MB) to disk... took 9.441s
archive does not contain 'system.sig'
extracting system_other.img (293 MB) to disk... took 1.527s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (253 MB) to disk... took 1.275s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
CreateProcess failed: 蝟餌絞?曆??唳?摰?瑼???(2)
error: Cannot generate image for userdata
Press any key to exit...
;urgently need your help.
sam

samsam2020 said:
Hi guys,
Please help me with my phone.
I have my pixel XL rooted and accidentally upgraded to android 10 and lost my root.
However, when i was in the process of trying to re-root the phone, i probably did something stupid and got my phone soft bricked with the phone turning into to a bootloop showing the Google sign and the screen on booting up.
I am able to enter the bootloader screen and tried to flash the Factory Stock image, from the old version such as 7.1.0 to the new version 10.0.0 but failed.
This is the message i got every time i flash the factory image.
============================================================
Microsoft Windows [版本 10.0.18362.720]
(c) 2019 Microsoft Corporation. 著作權所有，並保留一切權利。
D:\Program Files (x86)\Android\Minimal ADB and Fastboot\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32480 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.060s]
finished. total time: 2.950s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_a' (57156 KB)...
OKAY [ 1.550s]
writing 'radio_a'...
OKAY [ 0.498s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.053s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (30 MB) to disk... took 0.325s
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 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1998 MB) to disk... took 9.441s
archive does not contain 'system.sig'
extracting system_other.img (293 MB) to disk... took 1.527s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (253 MB) to disk... took 1.275s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
CreateProcess failed: 蝟餌絞?曆??唳?摰?瑼???(2)
error: Cannot generate image for userdata
Press any key to exit...
;urgently need your help.
sam
Click to expand...
Click to collapse
You installed an Android 10 factory image, please DO NOT try installing an Android 7xx factory image.
If your bootloader is unlocked try this using this Guide:
- First, remove (uninstall) Minimal ADB from your computer.
- Second, download and install SDK Platform-tools r29.0.6 on your computer. There is a link in the guide: Prerequisites c.
- You are on Android 10 Factory Image (10.0.0 (QP1A.191005.007.A3, Dec 2019)) so just do # 9 in the guide to root/reroot.
Note: Check your bootloader and radio version.
Why? You tried to flash an Android 7xx factory image and it look like the Android 7xx bootloader and radio replaced the Android 10 bootloader and radio.
If your bootloader and radio are not:
- bootloader-marlin-8996-012001-1908071822.img
- radio-marlin-8996-130361-1905270421.img
Open a command prompt #1 in the guide and flash them:
Code:
fastboot flash bootloader bootloader-marlin-8996-012001-1908071822.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-130361-1905270421.img
fastboot reboot-bootloader

Homeboy76 said:
You installed an Android 10 factory image, please DO NOT try installing an Android 7xx factory image.
If your bootloader is unlocked try this using this Guide:
- First, remove (uninstall) Minimal ADB from your computer.
- Second, download and install SDK Platform-tools r29.0.6 on your computer. There is a link in the guide: Prerequisites c.
- You are on Android 10 Factory Image (10.0.0 (QP1A.191005.007.A3, Dec 2019)) so just do # 9 in the guide to root/reroot.
Note: Check your bootloader and radio version.
Why? You tried to flash an Android 7xx factory image and it look like the Android 7xx bootloader and radio replaced the Android 10 bootloader and radio.
If your bootloader and radio are not:
- bootloader-marlin-8996-012001-1908071822.img
- radio-marlin-8996-130361-1905270421.img
Open a command prompt #1 in the guide and flash them:
Code:
fastboot flash bootloader bootloader-marlin-8996-012001-1908071822.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-130361-1905270421.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
:good::good::good:
Very GOOD man!
Just tried and i was able to restore the factory image
also rooted my phone again!!
Million thanks for your help.