Ok heres is what happen yesterday, I successfully root my HD XT925 using Dan's motochopper (Thanks Dan!!) no problem at all then I found a bootanimation thread I pick the bootanimation_dna.zip and I went to system/media and rename the original bootanimation.zip to bootanimationOLD.zip, copy the DNA file and rename it to bootanimation.zip, everything OK so far... then I restart my XT925 and it starts doing the DNA bootanimation BUT almost to finish it got stuck!! and since then I was not able to use the phone, I try to recovery, wipe data etc. etc. and nothing it starts booting, show motorola logo then the animation starts and it gets stuck...
so after several hours of unsuccessful tries to get it work and looking into several places, I found the stock firmware (JB 4.1.2 Telcel -MX) I downloaded to flash it and see if that works... bad idea!!
I tried flash the firmware with fastboot and using RSD lite (v6.1.5) with the same results:
fastboot reason: boot menu selected
usb conected
downgrade security version
update gpt_main version failed
preflash validation failed for gpt
now the cell is stuck on fastboot mode, it says: Fastboot Reason: Flash Failure
So I'm overwhelm and I don't know what to do...
a couple of things, I try using the firmware directly as I downloaded and the RSD gave me this error:
"Flailed flashing process. Unknonw fastboot command. (getvar)"
then I read somewhere here at XDA that I should remove a line from the xml fle... <step operation="getvar" var="max-download-size" />
try again and I got this:
"Failed flashing process. 2/22 flash partition "partition_signed" -> Phone returned FAIL.
and the cell shows:
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
Any idea what I'm doing wrong???
Thakns guys!!
no one?
same problem, help please !
Foxtom, you're spamming many threads. Please stop.
Sent from my RAZR Maxx HD
Since you have an XT925, if you don't mind unlocking your bootloader (through motorola no need for any hacks), you can then flash anything through RSD and it won't fail because of version errors or anything
Sent from my GT-N5110 using XDA Premium 4 mobile app
I personnaly used a self made script to flash stock roms, RSD Lite is always bugging me for instructions like this one.
Here is an example :
Code:
@echo off
fastboot flash sbl1 sbl1_signed
fastboot flash sbl2 sbl2_signed
fastboot flash sbl3 sbl3_signed
fastboot flash rpm rpm_signed
fastboot flash tz tz_signed
fastboot flash aboot aboot_signed
fastboot reboot-bootloader
echo. When the screen comes back on, press any key to continue!
pause
fastboot flash partition partition_signed
fastboot flash sbl1 sbl1_signed
fastboot flash sbl2 sbl2_signed
fastboot flash sbl3 sbl3_signed
fastboot flash rpm rpm_signed
fastboot flash tz tz_signed
fastboot flash aboot aboot_signed
fastboot flash boot boot_signed
fastboot erase cache
fastboot flash system system_signed
fastboot flash recovery recovery_signed
fastboot flash modem modem_signed
fastboot flash devtree devtree_signed
fastboot flash logo logo
fastboot flash cdrom cdrom_signed
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg_signed
fastboot erase cache
fastboot erase tombstones
echo. Press a key to reboot the phone
pause
fastboot reboot
All you have to do, is replace the "xxxx_signed" with the filenames you have in your rom.
And save this in a textfile called "xxxx.bat".
Then (if the fastboot.exe files are in the same folder) execute the script and it will flash your XT925.
I personnaly used that script with the stock rom Retail/France and it worked perfectly.
Tell me if you need more details.
rename the original bootanimation.zip to bootanimationOLD.zip,
here's your problem, if you see tutorials in the themes and apps section, it tell you to rename your old one .bak as in backup
and then paste new bootanimation...try that out!
Quick background: I had a battery status software issue. Opo tech support gave me a fix for it. The fix wiped the phone and removed root access. I knew it would wipe the phone but they told me that it would not remove root access, and nothing they said after that point was helpful. I am able to get root access again, but am fairly certain the wipe involved in unlocking the bootloader removed the fix they gave me. What I would like to know is how to apply the fix while maintaining root access. Or to root after applying it without removing it.
I am on the latest ota update, 11.0-XNPH05Q and only have the fix applied currently.
If anyone has a good idea of what I need to alter to get this working I would greatly appreciate the input.
It isn't as simple as removing the "oem lock" command is it?
The fix consisted of 2 batch files:
Batch file 1:
MENTION=279333]ECHO[/MENTION] off
fastboot oem unlock
fastboot reboot-bootloader
sleep 5
Batch file 2:
MENTION=279333]ECHO[/MENTION] off
echo ######### This patch is Created by ONEPLUS Technical Support. #######
echo ###### This patch should only be used for ONEPLUS ONE 64GB Global Version. ######
@ECHO off
fastboot erase persist
fastboot flash persist persist.img
fastboot erase reserve4
fastboot flash reserve4 reserve4.img
fastboot erase oppostanvbk
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot oem lock
fastboot reboot
echo It is done Now
pause
The fix hasn't actually done anything apart from a simple erase and reflash of the partitions on your phone. Unlocking the bootloader again won't remove the fix. The wipe that occurs during the bootloader unlock performs a factory reset, which basically just erases any user data, not system data or any other partition on the device. So go ahead and unlock again, but, you will lose your user data in the process obviously.
Wonderful, thanks for the help!
Hello guys,
on a One Plus One of a friend I insert in the fastboot this 2 codes:
fastboot erase modemst1
fastboot erase modemst2
because he had problems with the gps and I fixed this problem on my Moto X in this way. But after i did this his phone cannot read the sim card. I tried to reboot and to hard reset but the problem is still there. He has Cm13 no-rooted and bootloader is still locked. How can i fix this?
Welp, this is one of the partitions used to store IMEI and Modem of the device. You can try flashing a modem http://forum.xda-developers.com/oneplus-one/general/firmware-modem-oneplus-one-lollipop-t3300907 or you will have to search on the internet and find those 2 partitions from someone who has them backed up.
//edit// i found something here its only modemst1 tho http://forum.xda-developers.com/oneplus-one/general/guide-imei-efs-backup-t3252618
If i backup the file from another phone maybe the IMEI can be changed?
Jekodark said:
Hello guys,
on a One Plus One of a friend I insert in the fastboot this 2 codes:
fastboot erase modemst1
fastboot erase modemst2
because he had problems with the gps and I fixed this problem on my Moto X in this way. But after i did this his phone cannot read the sim card. I tried to reboot and to hard reset but the problem is still there. He has Cm13 no-rooted and bootloader is still locked. How can i fix this?
Click to expand...
Click to collapse
You can try unlocking his bootloader using
Code:
fastboot oem unlock
because you can't flash anything to the phone while its unlocked
Backup his stuff in internal storage (pics, vids etc) to a PC before you do the bootloader unlock
Do the commands above again
Code:
fastboot erase modemst1
fastboot erase modemst2
Then fastboot flash a modem, c6. 241
https://www.androidfilehost.com/?fid=24052804347825946
Extract and just copy paste the below commands, or alternatively use TWRP to flash it
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
Reboot and see if the SIM issue persists
I solved flashing the oxygen!
Good morning, after searching and reading endless post of solutions I did not find any. To if I prepared to post the problem here and see if any solution arises, since we are several affected by this.
I pass the following: When I try to flash firmware stock con ABDtool . First flicks (Prevalidation Failed) Bootloader when flashing:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
It could be caused by not unlocking the boot loader, but My bootloader it unlocked
The bootloader data:
AP Fastoboot Flash Mode (Secure)
BL:80.CB (sha-cfa8344, 2015-11-20 18:51.42)
Baseband: Not found
Product Variant: osprey XT1542 8 GB P2B
Serial Nmber zY2232NR5Q
CPU: MSM8916
eMMC: (GB Micron RV= 06 PV= 12 TY= 17
DRAM: 1024MB Elpida S8 SDRAM DIE= 4GB
Console (NULL): null
Battery Ok
Device is UNLOCKED. Status code 3
Software Status: Modified
Connect USB Data Cable.
You can flash the stock in the same way without flashing those 2 lines, but the terminal lights up and goes straight to Fastboot. Any way to fix it ??
For example I reboot from the Android menu and start in fastboot and I have to press Star to start android.
The ADB commands
fastboot devices
**************
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
*****************
fastboot flash logo logo.bin
If you searched, you would know preflash validation errors mean your device has newer firmware then you are trying to flash. locked devices do no support​ downgrading, if you can't skip gpt.bin and bootloader.bin and get it booting, you're probably out of luck.
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