Database Info

Need help finding stock sprint recovery from nougat

Here's my issue. Some time back I installed TWRP in order to install the Pixel Launcher as a system app. When Nougat came out I tried to install the ota. No go. So I installed a stock recovery and relocked the bootloader. Still no luck. I've tried every way possible to install Nougat: ruu.exe, from sd card, flash through adb. Nothing.
I think my stock recovery is problematic. When I try and get into it through the bootloader I get the dreaded red triangle with exclamation mark. So I've tried two ways of extracting the recovery.img from the Nougat update. I've used process monitor and the trick of looking in %temp% after starting the ruu.exe. I get the correct size zip, but when I unzip, whether through 7zip or winzip, I just get a series of 22 smaller zips and have no idea where in all those the recovery image is hiding.
Anyone have any ideas what I'm doing wrong or where I can download the nougat recovery image for sprint?

revcp said:
Here's my issue. Some time back I installed TWRP in order to install the Pixel Launcher as a system app. When Nougat came out I tried to install the ota. No go. So I installed a stock recovery and relocked the bootloader. Still no luck. I've tried every way possible to install Nougat: ruu.exe, from sd card, flash through adb. Nothing.
I think my stock recovery is problematic. When I try and get into it through the bootloader I get the dreaded red triangle with exclamation mark. So I've tried two ways of extracting the recovery.img from the Nougat update. I've used process monitor and the trick of looking in %temp% after starting the ruu.exe. I get the correct size zip, but when I unzip, whether through 7zip or winzip, I just get a series of 22 smaller zips and have no idea where in all those the recovery image is hiding.
Anyone have any ideas what I'm doing wrong or where I can download the nougat recovery image for sprint?
Click to expand...
Click to collapse
The recovery isn't related to anything in the RUU process, it doesn't matter what version you have. If you want to upgrade from marshmallow to Nougat using a RUU you'll first need to update the firmware so your phone can read HTC's new digital signature, without doing that you'll always get signature errors when flashing the ruu. You can find the sprint RUU and firmware in my RUU collection thread (general section).
FYI, ruu are encrypted. You can't simply unzip these files. You need to decrypt using the correct decryption key.

Thank you. It's been a while since I've dived down into a phone. Is there a step by step on how to update the firmware?

So, tried to update the firmware. Here's the result (after doing the "fastboot oem rebootRUU" step):
D:\Android\platform-tools>htc_fastboot flash zip firmware2.18.651.2.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 800000000 bytes
sending 'zip' (99604 KB)...
OKAY [ 4.927s]
writing 'zip'...
(bootloader) HOSD CL#747079
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8 RU_SIGNATURE_FAIL )
finished. total time: 19.760s
htc_fastboot finished. total time: 19.925s

And now trying the .zip on root of sd method I get this after executing command:
8 RU_SIGNATURE_FAIL
8 RU_SIGNATURE_FAIL
FAIL8 RU_SIGNATURE_FAIL

revcp said:
So, tried to update the firmware. Here's the result (after doing the "fastboot oem rebootRUU" step):
D:\Android\platform-tools>htc_fastboot flash zip firmware2.18.651.2.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 800000000 bytes
sending 'zip' (99604 KB)...
OKAY [ 4.927s]
writing 'zip'...
(bootloader) HOSD CL#747079
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8 RU_SIGNATURE_FAIL )
finished. total time: 19.760s
htc_fastboot finished. total time: 19.925s
Click to expand...
Click to collapse
Sorry I thought your phone was S-OFF, this firmware package is decrypted so it can't be flashed on a S-ON phone. If you can find the 2.18.651.2 ota zip file, you can extract the signed firmware from it. (signed version can be flashed with S-ON). You should be able to get the ota file from your phone by selecting "download and install later". Once downloaded you can transfer the ota from your phone to your computer and extract the firmware.zip file from it using winrar / 7zip.

There's another thing I don't understand about this.
The FAQ directions in https://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344 say to " rename the RUU zip file '2PQ9IMG.zip'". But there is no RUU zip file. There is RUU.EXE and the firmware zip file.

revcp said:
There's another thing I don't understand about this.
The FAQ directions in https://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344 say to " rename the RUU zip file '2PQ9IMG.zip'". But there is no RUU zip file. There is RUU.EXE and the firmware zip file.
Click to expand...
Click to collapse
These instructions are for flashing ruu in zip format. how to flash.exe ruu explained just below.
.zip ruu can be extracted from the .exe version if needed (on some pc, a .exe ruu can be problematic, e.g. you double click the file to launch the process and nothing happen...)
---------- Post added at 11:54 AM ---------- Previous post was at 11:51 AM ----------
Btw if you can share your firmware.zip extracted from the OTA it would be really nice for other Sprint users in the same situation. I wasn't able to find the Sprint ota zip file anywhere yet.

alray said:
Sorry I thought your phone was S-OFF, this firmware package is decrypted so it can't be flashed on a S-ON phone. If you can find the 2.18.651.2 ota zip file, you can extract the signed firmware from it. (signed version can be flashed with S-ON). You should be able to get the ota file from your phone by selecting "download and install later". Once downloaded you can transfer the ota from your phone to your computer and extract the firmware.zip file from it using winrar / 7zip.
Click to expand...
Click to collapse
That's what I need! Thanks! Any idea where the dl is saved on the phone? I should have noted that I was s-on. Sorry.

revcp said:
That's what I need! Thanks! Any idea where the dl is saved on the phone? I should have noted that I was s-on. Sorry.
Click to expand...
Click to collapse
For the M9 it was in data/data/com.htc.updater/files I guess it should be similar for the A9. Maybe someone else could confirm this...

Well, I'm dead in the water. I've tried every way possible to dl the ota, but when I go to /android/data/com/htc.updater/files there is nothing there. A 2.18.651.2 ota zip file is nowhere to be found. If anyone has that for spring I would love to get my hands on it.

Flash OTA with root

Is this the most up to date instructions? https://www.xda-developers.com/flash-monthly-security-update-google-pixel/

Pixel noob alert! I have basically the same question. I've done a bunch of reading and it seems like I can:
1) Use flash-all on the factory image after removing "-w"
2) ADB sideload the OTA zip file
3) TWRP install the OTA zip file
I'm not clear which, if any, is really "best" and in each case whether I'll need to reboot TWRP, reinstall TWRP and reinstall Magisk?
Thanks for any help on this!

Oof, I'm in the same boat. I messed installing TWRP and had to flash the factory images over the weekend, so I'm a little gun shy to flash this until I know exactly what to do.

On my Pixel 2 I've been doing the below -- I do not install TWRP but I do have a custom kernel and magisk:
1) flash stock boot img from previous month to remove Magisk and custom kernel (I *assume* that removing magisk via magisk manager would also accomplish this if magisk was installed before custom kernel - but I have never bothered doing this)
2) sideloading OTA (via stock recovery)
3) installing magisk and custom kernel
There are cases where Google says on their factory image page that you must take the OTA (rather than flashing to a new image) - that fact is enough reason to me to sideload the OTA rather than flashing the entire new month's image

ktdt00 said:
Pixel noob alert! I have basically the same question. I've done a bunch of reading and it seems like I can:
1) Use flash-all on the factory image after removing "-w"
2) ADB sideload the OTA zip file
3) TWRP install the OTA zip file
I'm not clear which, if any, is really "best" and in each case whether I'll need to reboot TWRP, reinstall TWRP and reinstall Magisk?
Thanks for any help on this!
Click to expand...
Click to collapse
1 or 2. Not 3. Either way you will have to re root and install TWRP if you want.
Both are equally good.

Sideloading through TWRP did not work for me at all with this phone so I had to download the Nov factory firmware, delete the -w on the flash-all.bat file. Then flashed this through fastboot, rebooted to make sure I was on the Nov update. After that, booted back to bootloader and reflashed TWRP and Maigisk, now all is fine.

Archangel said:
Sideloading through TWRP did not work for me at all with this phone so I had to download the Nov factory firmware, delete the -w on the flash-all.bat file. Then flashed this through fastboot, rebooted to make sure I was on the Nov update. After that, booted back to bootloader and reflashed TWRP and Maigisk, now all is fine.
Click to expand...
Click to collapse
I've tried to flash-all the Nov. factory image like 4 times now, and every time I check the build number and it's still the Oct version. Can someone please help me figure out what I'm doing wrong? I've extracted and copied all the .img files into the adb directory. This is super long but here is the cmd readout I get after flash-all:
PS - what is the -w thing about? I don't see it in the names of any downloaded files.
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8489 KB)...
OKAY [ 0.289s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5004167
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.642s]
finished. total time: 0.936s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.071s
target reported max download size of 268435456 bytes
sending 'radio_a' (71148 KB)...
OKAY [ 1.659s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00023-180917-B-5014671
(bootloader) Flashing partition modem_a
OKAY [ 0.463s]
finished. total time: 2.122s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.070s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.226s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.022s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2157 MB) to disk... took 9.974s
archive does not contain 'system.sig'
extracting system_other.img (418 MB) to disk... took 1.930s
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 (444 MB) to disk... took 2.022s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5004167
Baseband Version.....: g845-00023-180917-B-5014671
Serial Number........: 897X0687T
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.361s
Press any key to exit...

I had this happen to me and the variable not found error is due to your platform tools being out of date. I updated mine,,, unfortunately I cant remember where,,or I would give that you to,,,if you do a google search on updated platform tools/xda it will come up and just take the most recent one you see. Once you swap out the platform tools folders you should be good to go. Once I did mine the flash completed and I am on Nov update.
Oh and the -w is a part of a line of code that you will find in the flash-all.bat file once you have extracted the Nov system image. Look for that flash-all.bat file then right click on it and open it up with Note+. Find the line at the bottom that has a -w in it and delete it out. Once that is done go to the top and hit save just dont exit out or it will not work. Once you hit save then you can hit the flash-all.bat and it will flash the Nov entire system up without erasing your current data. Hope this helps.
Troy The Great said:
I've tried to flash-all the Nov. factory image like 4 times now, and every time I check the build number and it's still the Oct version. Can someone please help me figure out what I'm doing wrong? I've extracted and copied all the .img files into the adb directory. This is super long but here is the cmd readout I get after flash-all:
PS - what is the -w thing about? I don't see it in the names of any downloaded files.
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8489 KB)...
OKAY [ 0.289s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5004167
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.642s]
finished. total time: 0.936s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.071s
target reported max download size of 268435456 bytes
sending 'radio_a' (71148 KB)...
OKAY [ 1.659s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00023-180917-B-5014671
(bootloader) Flashing partition modem_a
OKAY [ 0.463s]
finished. total time: 2.122s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.070s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.226s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.022s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2157 MB) to disk... took 9.974s
archive does not contain 'system.sig'
extracting system_other.img (418 MB) to disk... took 1.930s
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 (444 MB) to disk... took 2.022s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5004167
Baseband Version.....: g845-00023-180917-B-5014671
Serial Number........: 897X0687T
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.361s
Press any key to exit...
Click to expand...
Click to collapse

Archangel said:
Sideloading through TWRP did not work for me at all with this phone so I had to download the Nov factory firmware, delete the -w on the flash-all.bat file. Then flashed this through fastboot, rebooted to make sure I was on the Nov update. After that, booted back to bootloader and reflashed TWRP and Maigisk, now all is fine.
Click to expand...
Click to collapse
Archangel said:
I had this happen to me and the variable not found error is due to your platform tools being out of date. I updated mine,,, unfortunately I cant remember where,,or I would give that you to,,,if you do a google search on updated platform tools/xda it will come up and just take the most recent one you see. Once you swap out the platform tools folders you should be good to go. Once I did mine the flash completed and I am on Nov update.
Oh and the -w is a part of a line of code that you will find in the flash-all.bat file once you have extracted the Nov system image. Look for that flash-all.bat file then right click on it and open it up with Note+. Find the line at the bottom that has a -w in it and delete it out. Once that is done go to the top and hit save just dont exit out or it will not work. Once you hit save then you can hit the flash-all.bat and it will flash the Nov entire system up without erasing your current data. Hope this helps.
Click to expand...
Click to collapse
You are a genius, the updated platform tools worked; all rooted and good to go. Thank you so much for your help

Why does the XDA guide not talk about re-rooting?
Followed XDAs instructions on unlocked bootloader, rooted with Magisk and now getting the "device is corrupt" message. Ugh.

I'm now 100% back to stock. Took forever. How the heck do I do this right next time? Working on restoring my data.

Update your platform tools often.

so is there a working step by step somewhere now?

Updated tools
Archangel said:
I had this happen to me and the variable not found error is due to your platform tools being out of date. I updated mine,,, unfortunately I cant remember where,,or I would give that you to,,,if you do a google search on updated platform tools/xda it will come up and just take the most recent one you see. Once you swap out the platform tools folders you should be good to go. Once I did mine the flash completed and I am on Nov update.
Oh and the -w is a part of a line of code that you will find in the flash-all.bat file once you have extracted the Nov system image. Look for that flash-all.bat file then right click on it and open it up with Note+. Find the line at the bottom that has a -w in it and delete it out. Once that is done go to the top and hit save just dont exit out or it will not work. Once you hit save then you can hit the flash-all.bat and it will flash the Nov entire system up without erasing your current data. Hope this helps.
Click to expand...
Click to collapse
Glad I found your post. I bricked my new 3XL I received today and was unable to get the factory image installed. Getting the new tools resolved the problem. I bricked when I used Magisk 17.1. After I got it going again, I used 17.3. Now she runs great.

km8j said:
I'm now 100% back to stock. Took forever. How the heck do I do this right next time? Working on restoring my data.
Click to expand...
Click to collapse
Anyone?

km8j said:
Anyone?
Click to expand...
Click to collapse
Look at post 6
https://forum.xda-developers.com/showthread.php?p=78083312
Sent from my [device_name] using XDA-Developers Legacy app

gvsukids said:
Look at post 6
https://forum.xda-developers.com/showthread.php?p=78083312
Click to expand...
Click to collapse
#1 is basically what I did already

km8j said:
#1 is basically what I did already
Click to expand...
Click to collapse
I have sideloaded the Nov OTA zip in stock recovery and not lost data. Pixel 3, unlocked bootloader, unrooted.

Soft brick while attempting to root

I tried rooting my Pixel 3 - - OEM Unlock, bootloader unlocked, got into TWRP, but for some reason couldn't access any files on the system to install a zip. I tried wiping the file system to start from scratch and that didn't work. I then rebooted multiple times and fastbooted back into TWRP -- I had found a thread saying to change the file system type if you couldn't see the internal storage in TWRP -- I think that's where I went wrong. After I did that, I could no longer fastboot into TWRP. I tried downloading a factory image from google and fastbooting the recovery with no luck. I even tried the guide here : https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849 to un-brick without success. I performed the erase commands "fastboot erase system_a
, fastboot erase system_b, fastboot erase boot_a, fastboot erase boot_b, fastboot reboot-bootloader then running the flash all command and the results below show and still unable to boot:
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8493 KB)...
OKAY [ 0.308s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5191736
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.899s]
finished. total time: 1.208s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
target reported max download size of 268435456 bytes
sending 'radio_a' (71132 KB)...
OKAY [ 1.907s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00009-181130-B-5157073
(bootloader) Flashing partition modem_a
OKAY [ 0.482s]
finished. total time: 2.393s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.376s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.041s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2189 MB) to disk... took 24.932s
archive does not contain 'system.sig'
extracting system_other.img (419 MB) to disk... took 4.880s
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 (445 MB) to disk... took 5.342s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5191736
Baseband Version.....: g845-00009-181130-B-5157073
Serial Number........: 89DX08FVQ
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.362s
Press any key to exit...
any advise would be greatly appreaciated.

cmorin543 said:
I tried rooting my Pixel 3 - - OEM Unlock, bootloader unlocked, got into TWRP, but for some reason couldn't access any files on the system to install a zip. I tried wiping the file system to start from scratch and that didn't work. I then rebooted multiple times and fastbooted back into TWRP -- I had found a thread saying to change the file system type if you couldn't see the internal storage in TWRP -- I think that's where I went wrong. After I did that, I could no longer fastboot into TWRP. I tried downloading a factory image from google and fastbooting the recovery with no luck. I even tried the guide here : https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849 to un-brick without success. I performed the erase commands "fastboot erase system_a
, fastboot erase system_b, fastboot erase boot_a, fastboot erase boot_b, fastboot reboot-bootloader then running the flash all command and the results below show and still unable to boot:
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8493 KB)...
OKAY [ 0.308s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5191736
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.899s]
finished. total time: 1.208s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
target reported max download size of 268435456 bytes
sending 'radio_a' (71132 KB)...
OKAY [ 1.907s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00009-181130-B-5157073
(bootloader) Flashing partition modem_a
OKAY [ 0.482s]
finished. total time: 2.393s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.376s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.041s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2189 MB) to disk... took 24.932s
archive does not contain 'system.sig'
extracting system_other.img (419 MB) to disk... took 4.880s
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 (445 MB) to disk... took 5.342s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5191736
Baseband Version.....: g845-00009-181130-B-5157073
Serial Number........: 89DX08FVQ
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.362s
Press any key to exit...
any advise would be greatly appreaciated.
Click to expand...
Click to collapse
Hello,
I wonder ? do you have pixel 3 phone?
I see that you have the bootloader of the crossheath for the google pixel 3 XL installed.
bootloader-crosshatch-b1c1-0.1-5191736.img
Maybe you should download the google pixel 3 OTA or Factory.img.

That's so weird -- I used the blueline factory image from here: https://developers.google.com/android/images#blueline
I'll try it again though. Thanks for noticing that.

cmorin543 said:
That's so weird -- I used the blueline factory image from here: https://developers.google.com/android/images#blueline
I'll try it again though. Thanks for noticing that.
Click to expand...
Click to collapse
Succes, and let me know if you succeeded flashing.
9.0.0 (PQ2A.190405.003, Apr 2019) Link c12f40f0b189eb2daa80d029917bc9a8841da89cfcafa21b8f61b0d9f90826e7

Still no luck. I double checked and then redownloaded the .img file you referenced and it is the same as I tried and gives the same results.

I think you need to fastboot format userdata, but I have not used that command on this device. If it wont do it automatically you probably need to do it manually. Look into that option. There should have never been a need to mess with any of the file systems on this device.

cmorin543 said:
Still no luck. I double checked and then redownloaded the .img file you referenced and it is the same as I tried and gives the same results.
Click to expand...
Click to collapse
Strange, and if you download the factory image?
You can flash it in all in one tool or with ADB.
So try factory with flash_all .bat
Succes!!

wangdaning said:
I think you need to fastboot format userdata, but I have not used that command on this device. If it wont do it automatically you probably need to do it manually. Look into that option. There should have never been a need to mess with any of the file systems on this device.
Click to expand...
Click to collapse
I should've mentioned that I did do the format of userdata at one point and it didn't make a difference.
sakerhetz said:
Strange, and if you download the factory image?
You can flash it in all in one tool or with ADB.
So try factory with flash_all .bat
Succes!!
Click to expand...
Click to collapse
I tried using the flash_all.bat with no joy and I also tried using twrp (when I was actually able to boot into it) to sideload the OTA zip still with no joy.
I think I'm just going to contact Google and see what they can do -- the phone is technically still under warranty and I am still able to re-lock the bootloader... I appreciate the help.

Maybe try:
1) fastboot erase userdata
2) flash-all.bat
If no good:
1) fastboot erase userdata
2) fastboot format userdata
3) flash-all.bat
Everything will be gone, but already is from what you have said.

if you have downloaded the correct factory image as you mentioned then it should wipe out everything and fix your userdata even if its corrupt with flash.all bat script.
you could alternatively take a look at the detailed steps here just download the blueline img instead of crosshatch... https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
Steps are exactly the same.

SacredDeviL666 said:
if you have downloaded the correct factory image as you mentioned then it should wipe out everything and fix your userdata even if its corrupt with flash.all bat script.
you could alternatively take a look at the detailed steps here just download the blueline img instead of crosshatch... https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
Steps are exactly the same.
Click to expand...
Click to collapse
That link you provided is the guide I attempted to use when the flash_all.bat didn't work.

cmorin543 said:
That link you provided is the guide I attempted to use when the flash_all.bat didn't work.
Click to expand...
Click to collapse
Are you using the most recent ADB? I have had that exact missing variable error during a factory image flash and updating to the newest ADB fixed it for me.

pacman420 said:
Are you using the most recent ADB? I have had that exact missing variable error during a factory image flash and updating to the newest ADB fixed it for me.
Click to expand...
Click to collapse
I will double check that. Thanks!

cmorin543 said:
That link you provided is the guide I attempted to use when the flash_all.bat didn't work.
Click to expand...
Click to collapse
just to confirm.
a) you booted to bootloader using power + volume down key and then use volume down key to change it to bootloader and press power again (this reboots the bootloader)
b) while you are inside the ADB folder use shift + right click while you are inside the adb folder and then select the option -- open command window here.
c) considering that you have already connected your pixel to pc via usb type the command " fastboot devices " in the command prompt window to ensure that your device is detected.
d) once it has detected the device/s proceed to unzip the april factory image from https://dl.google.com/dl/android/aosp/blueline-pq2a.190405.003-factory-c12f40f0.zip in the same folder as ADB
e) Double click on flash.all bat file and let us know the result.
I am sure you might have followed above steps but just to make sure if everything is covered. as the above should actually fix all partition errors.

pacman420 said:
Are you using the most recent ADB? I have had that exact missing variable error during a factory image flash and updating to the newest ADB fixed it for me.
Click to expand...
Click to collapse
You are a genius -- apparently I did have the newest version of ADB in my downloads folder, but I was so used to using a specific directory with platform-tools for my old phone, I didn't realize it was an old version -- tried it with the newest version of ADB and it worked like a charm... too bad I already contacted google and they're sending me a new phone.. :-\
Thanks again for all your help guys.

pixel 3 sideload successful but doesn't have any effect, still original image

Hi!
I just finished sideloading the latest image for Pixel 3 (9.0.0 (PQ3A.190505.002, May 2019)
I did everything correct by following all the steps:
- unlocked bootloader
- executed flash_all.bat
- locked bootloader
At the end, after I rebooted the phone, I got into the system and checked the version.. it's still PD1A from september 2018!
Everything is wiped out as a result of unlocking the bootloader so something did work.. but the system isn't PQ3A.
Here is the flash_all.bat log:
Code:
E:\android\blueline-pq3a.190505.002>flash-all.bat
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8493 KB)...
OKAY [ 0.288s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5343672
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.220s]
finished. total time: 0.510s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
target reported max download size of 268435456 bytes
sending 'radio_a' (71132 KB)...
OKAY [ 1.684s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00017-190312-B-5369743
(bootloader) Flashing partition modem_a
OKAY [ 0.420s]
finished. total time: 2.114s
rebooting into bootloader...
OKAY [ 0.067s]
finished. total time: 0.067s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.223s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.021s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2196 MB) to disk... took 10.381s
archive does not contain 'system.sig'
extracting system_other.img (421 MB) to disk... took 1.999s
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 (445 MB) to disk... took 2.062s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5343672
Baseband Version.....: g845-00017-190312-B-5369743
Serial Number........: 8ATX0Z2PL
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.363s
Press any key to exit...
Can you help me understand what I did wrong?

change active slots
Use this command:
fastboot getvar current-slot
This will return the active slot ( either a or b)
then use this command:
fastboot set_active (enter a or b here)
If the first command gives you a enter b and vice versa into the command above, then reflash.

Hi!
Thank you for your suggestion! Before I try it, I want to understand what I did wrong.
First, I realised I was using the 27.0.0-4455170 version of ADB so the first thing I did was to update it to 28.0.3-5475833.
Ok, so from what I understand, there are two boot slots, a and b; a being the one in which the stock image came and b the one which I flashed yesterday.
Because I had an outdated fastboot version, the flashing was successful but the slot wasn't automatically changed (this explains the "remote: variable not found" error at the end of my log).
So the system still used slot a to boot and, of course, I returned to the same stock image the phone came with. Am I correct?
So now, in order to use the second image, I simply need to do "fastboot set_active b" and reboot my phone so it uses that slot instead.
This is where I don't understand why you wrote "[...] into the command above, then reflash", Is that a typo and you actually meant "then reboot"? why should I reflash if slot b is already flashed?
Also, if I were to repeat the flashing sequence with the new adb tool, then I think I don't need to set slot b active manually as this will be done automatically now.

No valid slot to boot - any way to back up data?

Does anyone have a way to get around: "no valid slot to boot"
I have a stock Pixel 4XL and just tried to upgrade to Android 11 with the latest images from Google.
I tried to patch the extracted boot image with Magisk and when I try to boot, I'm stuck in fastboot mode with "no valid slot to boot"
I then tried to recover to unrooted stock using an edited flash-all.sh script (removed -w flag). Now, I see the "G" logo and the progress bar cycles a couple of times, then I'm back in fastboot mode with "no valid slot to boot"
Is there any way to recover the device?

J.L.C. said:
Does anyone have a way to get around: "no valid slot to boot"
I have a stock Pixel 4XL and just tried to upgrade to Android 11 with the latest images from Google.
I tried to patch the extracted boot image with Magisk and when I try to boot, I'm stuck in fastboot mode with "no valid slot to boot"
I then tried to recover to unrooted stock using an edited flash-all.sh script (removed -w flag). Now, I see the "G" logo and the progress bar cycles a couple of times, then I'm back in fastboot mode with "no valid slot to boot"
Is there any way to recover the device?
Click to expand...
Click to collapse
boot into Safe mode then reboot.

Homeboy76 said:
boot into Safe mode then reboot.
Click to expand...
Click to collapse
How do I get into safe mode from fastboot?
If I switch back and forth with `set_active a/b` I can get it to the G logo with the progress bar, but it gets stuck there regardless of which buttons I press or hold down.

J.L.C. said:
How do I get into safe mode from fastboot?
If I switch back and forth with `set_active a/b` I can get it to the G logo with the progress bar, but it gets stuck there regardless of which buttons I press or hold down.
Click to expand...
Click to collapse
ok. Flash the stock boot.img to both slots:
fastboot flash boot --slot all boot.img

Homeboy76 said:
ok. Flash the stock boot.img to both slots:
fastboot flash boot --slot all boot.img
Click to expand...
Click to collapse
Unfortunately, I still end up stuck in fastboot with no valid slot to boot
I just tried to adb sideload an OTA through stock recovery recovery, and now I'm stuck at the G logo.

J.L.C. said:
Unfortunately, I still end up stuck in fastboot with no valid slot to boot
I just tried to adb sideload an OTA through stock recovery recovery, and now I'm stuck at the G logo.
Click to expand...
Click to collapse
@J.L.C. try this:
First, make sure you have the latest:
- Platform-tools r30.0.4 installed on your computer
- The latest Android 11 (R) extracted in the Platform-tools folder
- Make sure you can see these files bootloader.img, radio.img, image....zip and fastboot.exe in the Platform-tools folder
Second, when you connect the phone to your computer make sure you do not plug the USB cable into a charging USB port.
Third, cd to the Platform-tools folder (Mac/Linux) or open a command prompt in the Platform-tools folder (Windows - see OP [Post 1] #1 in the Guide below) and type the following commands and press enter after each command:
Notes:
- If you are using a Mac or Linux computer put this ./ in front of every command.
- Guide
fastboot reboot bootloader
fastboot flash bootloader --slot all <complete name of bootloader.img>
fastboot reboot bootloader
fastboot flash radio --slot all <complete name of radio.img>
fastboot reboot bootloader
fastboot update -w <complete name of image-coral-....zip> --skip-reboot --slot all
(this will wipe your phone data and internal storage)
I suggest you do it this way because something is jacked on your phone this will clear out all the gremlings
fastboot reboot bootloader
fastboot reboot
If it works thank this post: https://forum.xda-developers.com/showpost.php?p=83509975&postcount=9

Homeboy76 said:
@J.L.C. try this:
First, make sure you have the latest:
- Platform-tools r30.0.4 installed on your computer
- The latest Android 11 (R) extracted in the Platform-tools folder
- Make sure you can see these files bootloader.img, radio.img, image....zip and fastboot.exe in the Platform-tools folder
Second, when you connect the phone to your computer make sure you do not plug the USB cable into a charging USB port.
Third, cd to the Platform-tools folder (Mac/Linux) or open a command prompt in the Platform-tools folder (Windows - see OP [Post 1] #1 in the Guide below) and type the following commands and press enter after each command:
Notes:
- If you are using a Mac or Linux computer put this ./ in front of every command.
- Guide
fastboot reboot bootloader
fastboot flash bootloader --slot all <complete name of bootloader.img>
fastboot reboot bootloader
fastboot flash radio --slot all <complete name of radio.img>
fastboot reboot bootloader
fastboot update <complete name of image-coral-....zip> --skip-reboot --slot all
(this will wipe your phone data and internal storage)
I suggest you do it this way because something is jacked on your phone this will clear out all the gremlings
fastboot reboot bootloader
fastboot reboot
If it works thank this post: https://forum.xda-developers.com/showpost.php?p=83509975&postcount=9
Click to expand...
Click to collapse
Is there any way to pull the data from the phone from fastboot or recovery? Like an idiot, I didn't back up before attempting the upgrade.

J.L.C. said:
Is there any way to pull the data from the phone from fastboot or recovery? Like an idiot, I didn't back up before attempting the upgrade.
Click to expand...
Click to collapse
@J.L.C.try this:
I hope you are using a Windows computer, I don't know how to do this on a Mac or Linux computer.
1. Add the path to the Platform-tools folder to Windows environment variables.
2. Create a folder on your computer that you want to copy the files from your Pixel 4 XL to.
3. Open a command prompt in that folder and type:
adb pull "/storage/emulated/0/"
(This should backup your internal storage.)
Note: USB debugging should be enabled on phone

It happened to me, I just flashed stock 10 then ota 11

stevoswifty said:
It happened to me, I just flashed stock 10 then ota 11
Click to expand...
Click to collapse
:good:

I'm back up and running but had to do a full wipe, including userdata (-w flag).
I tried fastboot installs of older 10 and 11 images and always ran into the same issue.
OTA upgrades over adb were failing with status 1.
So, phone recovered, data not so much.

J.L.C. said:
I'm back up and running but had to do a full wipe, including userdata (-w flag).
I tried fastboot installs of older 10 and 11 images and always ran into the same issue.
OTA upgrades over adb were failing with status 1.
So, phone recovered, data not so much.
Click to expand...
Click to collapse
:good:

I had the same problem, ADB was unauthorised, so I was unable to to do anything with that.
When I was in the 'Fastboot Mode', the command:
$ fastboot devices
was unable to find my device, and therefore I was unable to flash the stock boot.img.
I solved it by selecting 'Power Off' in 'Fastboot Mode' and when the screen turned black, I did press and hold the Volume Down button until the device rebooted into 'Fastboot Mode'. Now my device was detected in when calling the command '$ fastboot devices'.
I do not remember if my device was connected via USB to the computer at that time of reboot.
Then I reflashed the stock boot.img (as flashing the magisk_boot.img never succeeded), and my telephone booted succesfully up unrooted. Then I generated a new patched boot image via Magisk, and rerooted the device without any problems.

Hello, I've run into the same/a similar problem. My Pixel 4a is in a bootloop after attempting to unroot.
I've flashed the stock factory image in accordance to these instructions and I'm still met with the bootloader upon a power cycle.
I've tried doing it on both slots to see if anything might help, but it hasn't yet.
My phone tells me "no valid slot to boot" for the reason just like those above, but nothing seems to help.
EDIT: I cannot apply an OTA update, either. Seeing as I can't unlock the device and validate the RSA key, the device is 'unauthorized' for ADB.

use.logic said:
Hello, I've run into the same/a similar problem. My Pixel 4a is in a bootloop after attempting to unroot.
I've flashed the stock factory image in accordance to these instructions and I'm still met with the bootloader upon a power cycle.
I've tried doing it on both slots to see if anything might help, but it hasn't yet.
My phone tells me "no valid slot to boot" for the reason just like those above, but nothing seems to help.
EDIT: I cannot apply an OTA update, either. Seeing as I can't unlock the device and validate the RSA key, the device is 'unauthorized' for ADB.
Click to expand...
Click to collapse
I don't know if this will help you, but hopefully it will help someone else:
I was unable to get my pixel 4a (sunfish) to boot after flashing stock, as well, with an error about no valid boot slot. However, running the flash tool through the browser fixed the problem. You'll need a chromium-based browser like Brave, but it got my phone working again.

I just stumbled across this issue when I flashed the wrong image to my Pixel 4a5G - accidentally downloaded "redfin" instead of "bramble". I'd previously patched the included boot.img using Magisk on my 4a5G and then tried to flash the rooted image using flash-all.bat (with -w removed, of course):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can see, it flashed a new bootloader and radio, then stopped due to not being able to identify the phone as 'redfin'. The phone then obviously bootlooped - no surprise there. It showed "unknown" as the device type in Fastboot instead of Bramble.
It took me a while to get things working again, as I really didn't want to have to wipe the phone:
1. First of all I tried to just flash a working bootloader - basically deleted everything from flash-all.bat below the line "fastboot flash bootloader ...". That restored the device type "Bramble" in Fastboot, but resulted in the "no valid slot" bootloop.
2. I then found this thread and tried the suggestion of "fastboot flash boot --slot all boot.img", which didn't help. I tried both the stock boot.img from the image I was already running (June 2021) and the stock boot.img from the image I was trying to update to (August 2021) - both appeared to flash successfully but didn't help get rid of the error - after a few boot attempts the phone would always land back on Fastboot showing the "no valid slot" message.
3. I then tried flashing the entire stock June 2021 image using flash-all.bat with -w removed. Process completed successfully but didn't get rid of "no valid slot"
4. I then figured I would have to wipe the phone - but as a last ditch effort, I tried flashing the entire stock August 2021 image using flash-all.bat with -w removed. Process completed successfully and to my surprise, the phone booted! I was able to reinstall Magsik normally, patch a boot.img file and then re-root normally using flash-all.bat.
The two reasons I'm posting this:
1. Don't get discouraged and keep trying different images - maybe it'll work
2. Why did the August image work, but the June one didn't? Is it because the Redfin image I accidentally flashed was from August? Are downgrades with flash-all.bat generally not possible?

I have this same problem.. I've tried to flsah using the android flash tool (the browser one) it goes through and says it completed successfully then when booting the Google logo shows up and the little loading bar underneath then takes me back to the bootloader and its back to square one again from there. I tried flashing manually. but it didnt work either. Any advice?

I had to try multiple different images manually before I got back to a working system. I'm starting to suspect that the trick was using an image with a newer time stamp that the one I was running before. Which images are you using exactly?

bemymonkey said:
I had to try multiple different images manually before I got back to a working system. I'm starting to suspect that the trick was using an image with a newer time stamp that the one I was running before. Which images are you using exactly?
Click to expand...
Click to collapse
i've been trying the most recent ones

OK I managed to get it to work by using the android flash tool but instead of picking the most recent build i picked the beta build of android 12 and voila it worked ... dont know why but thanks for the response

Yes. Even I am also stuck with same issue :
RootDevice_GooglePixel4a\platform-tools_r31.0.3-windows (2)\platform-tools>fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.053s]
Finished. Total time: 0.061s
RootDevice_GooglePixel4a\platform-tools_r31.0.3-windows (2)\platform-tools>fastboot flash bootloader --slot all
unknown partition 'bootloader'
fastboot: error: cannot determine image filename for 'bootloader'
RootDevice_GooglePixel4a\platform-tools_r31.0.3-windows (2)\platform-tools>fastboot flash bootloader --slot all bootloader-bramble-b5-0.4-7758094.img
Sending 'bootloader_a' (8762 KB) OKAY [ 0.318s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b5-0.4-7758094
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition uefisecapp_a
(bootloader) Flashing partition featenabler_a
(bootloader) Flashing partition logfs
OKAY [ 0.388s]
Sending 'bootloader_b' (8762 KB) OKAY [ 0.317s]
Writing 'bootloader_b' (bootloader) Flashing Pack version b5-0.4-7758094
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition featenabler_b
(bootloader) Flashing partition logfs
OKAY [ 0.432s]
Finished. Total time: 2.100s
RootDevice_GooglePixel4a\platform-tools_r31.0.3-windows (2)\platform-tools>fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.040s]
Finished. Total time: 0.056s
\RootDevice_GooglePixel4a\platform-tools_r31.0.3-windows (2)\platform-tools>fastboot flash radio --slot all radio-bramble-g7250-00161-211008-b-7807492.img
Sending 'radio_a' (149780 KB) OKAY [ 3.665s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g7250-00161-211008-B-7807492
(bootloader) Flashing partition modem_a
OKAY [ 0.824s]
Sending 'radio_b' (149780 KB) OKAY [ 3.636s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g7250-00161-211008-B-7807492
(bootloader) Flashing partition modem_b
OKAY [ 1.085s]
Finished. Total time: 9.842s
RootDevice_GooglePixel4a\platform-tools_r31.0.3-windows (2)\platform-tools>fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.044s]
Finished. Total time: 0.053s
RootDevice_GooglePixel4aplatform-tools_r31.0.3-windows (2)\platform-tools>fastboot update -w image-bramble-sq1a.211205.008.zip --skip-reboot --slot all
Warning: slot set to 'all'. Secondary slots will not be flashed.
--------------------------------------------
Bootloader Version...: b5-0.4-7758094
Baseband Version.....: g7250-00161-211008-B-7807492
Serial Number........: 15191JECB01734
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.075s]
Checking 'version-bootloader' OKAY [ 0.056s]
Checking 'version-baseband' OKAY [ 0.072s]
Setting current slot to 'a' OKAY [ 0.145s]
extracting boot.img (96 MB) to disk... took 0.244s
archive does not contain 'boot.sig'
Sending 'boot_a' (98304 KB) OKAY [ 2.440s]
Writing 'boot_a' OKAY [ 0.679s]
archive does not contain 'boot.sig'
terminating with uncaught exception of type std:ut_of_range: basic_string