Develop Bugs

Bootloader unlocked, factory image flashed...but still bootlooping :(

Hi!
I tried flashing the March Factory image (9.0.0 (PQ2A.190305.002, Mar 2019)).
In adb:
fastboot devices
fastboot oem unlock - message on phone screen, volume up then power. Unlocked ok
flash-all
Devices reboots, but still boot loops. I also tried flashing each item separately (i recall once on my Nexus 6P this worked when flash-all didn't work).
fastboot flash boot <boot image file name>.img
fastboot flash bootloader <bootloader image file name>.img
fastboot reboot-bootloader
fastboot flash radio <radio image file name>.img
fastboot flash recovery <recovery file name>.img
fastboot flash system <system file name>.img
fastboot flash vendor <vendor file name>.img
fastboot reboot
Any ideas what I could try next?
EDIT: I somehow managed to get it to boot into recovery. I see I can wipe data/factory reset. I am a little hesitant to do this, as will this remove the ADB USB debugging ability and then lock me out of ADB?

SD Platform tools up to date?
Maybe a corrupt flash or file.
https://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378

crackerjack1957 said:
SD Platform tools up to date?
Maybe a corrupt flash or file
Click to expand...
Click to collapse
Following instructions from there, and also trying a different cable. I have the same issue, it still bootloops.
PHP:
C:\Users\Obsidian>cd C:/platform-tools
C:\platform-tools>fastboot devices
HT6A30206491 fastboot
C:\platform-tools>flash-all
Sending 'bootloader_a' (32424 KB) OKAY [ 0.842s]
Writing 'bootloader_a' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 16.264s]
Finished. Total time: 17.268s
rebooting into bootloader OKAY [ 0.015s]
Finished. Total time: 0.015s
< waiting for any device >
Sending 'radio_a' (57140 KB) OKAY [ 1.793s]
Writing 'radio_a' OKAY [ 0.852s]
Finished. Total time: 2.791s
rebooting into bootloader OKAY [ 0.010s]
Finished. Total time: 0.011s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 8996-012001-1811131534
Baseband Version.....: 8996-130181-1811270246
Serial Number........: HT6A30206491
--------------------------------------------
Checking product OKAY [ 0.050s]
Checking version-bootloader OKAY [ 0.049s]
Checking version-baseband OKAY [ 0.049s]
extracting boot.img (30 MB) to disk... took 0.795s
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 'odm.img'
archive does not contain 'product.img'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (1953 MB) to disk... took 14.468s
archive does not contain 'system.sig'
extracting system_other.img (312 MB) to disk... took 1.951s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (259 MB) to disk... took 1.690s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 29939712 4k blocks and 7487488 inodes
Filesystem UUID: 370a14d6-4260-11e9-a75f-5fe718f1534e
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'boot_a' (31001 KB) OKAY [ 0.801s]
Writing 'boot_a' OKAY [ 0.603s]
Sending sparse 'system_a' 1/4 (524284 KB) OKAY [ 12.109s]
Writing sparse 'system_a' 1/4 OKAY [ 3.998s]
Sending sparse 'system_a' 2/4 (524284 KB) OKAY [ 11.960s]
Writing sparse 'system_a' 2/4 OKAY [ 3.952s]
Sending sparse 'system_a' 3/4 (524284 KB) OKAY [ 11.916s]
Writing sparse 'system_a' 3/4 OKAY [ 4.045s]
Sending sparse 'system_a' 4/4 (427564 KB) OKAY [ 9.706s]
Writing sparse 'system_a' 4/4 OKAY [ 3.348s]
Sending 'system_b' (319668 KB) OKAY [ 7.904s]
Writing 'system_b' OKAY [ 2.646s]
Sending 'vendor_a' (266192 KB) OKAY [ 6.558s]
Writing 'vendor_a' OKAY [ 2.295s]
Setting current slot to 'a' OKAY [ 0.406s]
Erasing 'userdata' OKAY [ 29.008s]
Sending 'userdata' (4672 KB) OKAY [ 0.196s]
Writing 'userdata' OKAY [ 0.206s]
Rebooting
Finished. Total time: 136.871s
Press any key to exit...

I assume you kept the (-w) in the flash-all so all data was wiped?
Have looked here for instructions......maybe try #5 and sideload if all else fails.
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866

Error Flashing Latest Update

I've tried to install the latest OTA update (October 2019) without success. I'm rooted and when I try to install the update OTA it either hangs at "Preparing system update" without ever finishing or telling me to try again (I have tried via cell signal or wifi without success).
I tried downloading the latest factory image and flashing that instead without the -w via fastboot and now get the following error:
I have upgraded fastboot (platform-tools) to the latest and still get the same error.
Code:
OKAY [ 0.060s]
checking version-bootloader...
OKAY [ 0.059s]
checking version-baseband...
OKAY [ 0.058s]
sending 'boot_a' (65536 KB)...
OKAY [ 2.840s]
writing 'boot_a'...
OKAY [ 0.714s]
sending 'dtbo_a' (8192 KB)...
OKAY [ 0.400s]
writing 'dtbo_a'...
OKAY [ 0.094s]
sending sparse 'system_a' 1/4 (262140 KB)...
OKAY [ 12.270s]
writing 'system_a' 1/4...
FAILED (remote: Partition should be flashed in fastbootd)
finished. total time: 17.136s
Press any key to exit...
Appreciate any help!
Thanks!

You need to be unrooted to take the OTA. Flash the stock boot image again then you can update. Or just sideload the OTA but either way you'll need to reroot.

I understand the need to unroot to take the OTA but why is it failing when trying to flash the factory image?

Code:
Need help!
I've tried several times to flash the factory image with the same results each time (flash-all without -w). I've downloaded the factory image again to make sure it wasn't corrupted.
I booted into fastboot via ADB and it got me into fastbootd mode and I tried doing flash-all from there but it rebooted back into regular fastboot after flashing the bootloader and failed again with the same error. I rebooted back into fastbootd and did the update command (fastboot update image-bonito-qp1a.191005.007.zip) directly from there and looks like it went through flashing system_a but failed when writing system_b (Operation not allowed). The phone now reports that the phone is corrupt (Your device is corrupt. It can't be trusted and may not work properly). It just displays the Google logo but nothing else happens. I can get to fastboot but unsure how to get past this issue.
Here's the output when flashing the factory image...
Code:
flash-all
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8349 KB)...
OKAY [ 0.691s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b4s4-0.2-5736883
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
OKAY [ 0.607s]
finished. total time: 1.303s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
target reported max download size of 268435456 bytes
sending 'radio_a' (73196 KB)...
OKAY [ 5.316s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g670-00025-190805-B-5781381
(bootloader) Flashing partition modem_a
OKAY [ 0.469s]
finished. total time: 5.790s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.071s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.583s
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.047s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (782 MB) to disk... took 32.955s
archive does not contain 'system.sig'
extracting system_other.img (119 MB) to disk... took 3.449s
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 (462 MB) to disk... took 19.669s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
--------------------------------------------
Bootloader Version...: b4s4-0.2-5736883
Baseband Version.....: g670-00025-190805-B-5781381
Serial Number........: XXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking version-bootloader...
OKAY [ 0.057s]
checking version-baseband...
OKAY [ 0.057s]
sending 'boot_a' (65536 KB)...
OKAY [ 2.447s]
writing 'boot_a'...
OKAY [ 0.631s]
sending 'dtbo_a' (8192 KB)...
OKAY [ 0.410s]
writing 'dtbo_a'...
OKAY [ 0.109s]
sending sparse 'system_a' 1/4 (262140 KB)...
OKAY [ 7.744s]
writing 'system_a' 1/4...
FAILED (remote: Partition should be flashed in fastbootd)
finished. total time: 12.159s
Press any key to exit...
Appreciate any help!

Damn it. Found the issue. Although I downloaded the latest fastboot and placed it in my usual folder, the PC was still pointing to an old version of fastboot in a different folder.
All is good now.

EDIT - removed ( platform-tools_r31.0.0 )

Can't update 1/2020 flash, phone stuck in bootloader please help!

ETA: YAY, I'M BACK UP AND RUNNING AFTER USING STOCK RECOVERY TO SIDELOAD THE FULL OTA. THANKS EVERYONE, YOU'VE MADE MY DAY!!!
Hello all, I'm hoping someone has some advice:
I downloaded the 1/2020 factory image, removed the -w from the .bat file so I didn't lose data, and tried to flash the update via fastboot. Unfortunately, after the phone rebooted into fastbootd during the process, I got an error that says "write to device failed" when sending product. I can't get my system back up, but I can reboot into bootloader and enter recovery. Here is the output from when I tried to flash-all.bat from my computer to write the january update:
PS C:\Users\lukef\Documents\Phone stuff\Pixel 3 XL\crosshatch-qq1a.200105.002> .\flash-all.bat
Sending 'bootloader_a' (8521 KB) OKAY [ 0.141s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b1c1-0.2-5946827
(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.281s]
Finished. Total time: 0.672s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.062s
Sending 'radio_a' (71404 KB) OKAY [ 0.484s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g845-00086-191011-B-5933466
(bootloader) Flashing partition modem_a
OKAY [ 0.297s]
Finished. Total time: 1.031s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 894Y03RLY
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.055s]
Checking 'version-bootloader' OKAY [ 0.050s]
Checking 'version-baseband' OKAY [ 0.046s]
Setting current slot to 'a' OKAY [ 0.062s]
extracting boot.img (64 MB) to disk... took 0.250s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.453s]
Writing 'boot_a' OKAY [ 0.203s]
extracting dtbo.img (8 MB) to disk... took 0.063s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.125s]
Writing 'dtbo_a' OKAY [ 0.063s]
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_a' (4 KB) OKAY [ 0.109s]
Writing 'vbmeta_a' OKAY [ 0.062s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.047s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.000s]
Updating super partition OKAY [ 0.031s]
Resizing 'product_a' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.000s]
Resizing 'vendor_a' OKAY [ 0.010s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1984 MB) to disk... took 8.416s
archive does not contain 'product.sig'
Sending 'product' (2032548 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Press any key to exit...
This happens with both the .002 factory image (the correct one for my at&t phone), and the .003 TMO/Fi image. Anyone have any ideas? I'm desperate!

lukefgoogler said:
Hello all, I'm hoping someone has some advice:
I downloaded the 1/2020 factory image, removed the -w from the .bat file so I didn't lose data, and tried to flash the update via fastboot. Unfortunately, after the phone rebooted into fastbootd during the process, I got an error that says "write to device failed" when sending product. I can't get my system back up, but I can reboot into bootloader and enter recovery. Here is the output from when I tried to flash-all.bat from my computer to write the january update:
...
archive does not contain 'product.sig'
Sending 'product' (2032548 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Press any key to exit...
This happens with bothe the .002 factory image (the correct one for my at&t phone), and the .003 TMO/Fi image. Anyone have any ideas? I'm desperate!
Click to expand...
Click to collapse
Seems odd. Did you try a different cable or USB port? Do you have the latest ADB / SDK on your PC?

swieder711 said:
Seems odd. Did you try a different cable or USB port? Do you have the latest ADB / SDK on your PC?
Click to expand...
Click to collapse
Thanks for the quick reply, those are all good ideas. Before asking for help I tried 2 different USB ports and 2 different cables. I fully updated my Android Studio before starting this, which includes the latest SDK, platform tools, etc., I was current with everything before starting.I have no idea how to fix this, I haven't hears a lot of people having issues flashing the january update so I assume its something on my end. I DO use Magisk and Kirisakura custom kernel, but I dont know how to disable either one via fastboot, which is all I have available.

lukefgoogler said:
Thanks for the quick reply, those are all good ideas. Before asking for help I tried 2 different USB ports and 2 different cables. I fully updated my Android Studio before starting this, which includes the latest SDK, platform tools, etc., I was current with everything before starting.I have no idea how to fix this, I haven't hears a lot of people having issues flashing the january update so I assume its something on my end. I DO use Magisk and Kirisakura custom kernel, but I dont know how to disable either one via fastboot, which is all I have available.
Click to expand...
Click to collapse
Is there a way to disable Magisk via Fastboot? I was able install the December update with just -w removed. I had Magisk+modules enabled along with Kiris kernel installed. I haven't installed the Jan update yet because I am waiting for the new kernel.
Other than disabling Magisk, you might have to try installing the update with the -w option. Hopefully you have some good backups offline!

swieder711 said:
Is there a way to disable Magisk via Fastboot? I was able install the December update with just -w removed. I had Magisk+modules enabled along with Kiris kernel installed. I haven't installed the Jan update yet because I am waiting for the new kernel.
Other than disabling Magisk, you might have to try installing the update with the -w option. Hopefully you have some good backups offline!
Click to expand...
Click to collapse
I tried to do a factory reset via recovery, other than nuke my personal data it didn't seem to do much, still only able to boot to bootloader with either a or b partition active. Starting to get worried...

lukefgoogler said:
I tried to do a factory reset via recovery, other than nuke my personal data it didn't seem to do much, still only able to boot to bootloader with either a or b partition active. Starting to get worried...
Click to expand...
Click to collapse
Have you tried sideloading the OTA with the stock recovery?

To not lose data you need to flash the "Full Ota" image and not the factory one... Then you need to do nothing just flash it...
Also from your console output it seems that the image you downloaded is corrupted as it's missing files...

lukefgoogler said:
Hello all, I'm hoping someone has some advice:
I downloaded the 1/2020 factory image, removed the -w from the .bat file so I didn't lose data, and tried to flash the update via fastboot. Unfortunately, after the phone rebooted into fastbootd during the process, I got an error that says "write to device failed" when sending product. I can't get my system back up, but I can reboot into bootloader and enter recovery. Here is the output from when I tried to flash-all.bat from my computer to write the january update:
PS C:\Users\lukef\Documents\Phone stuff\Pixel 3 XL\crosshatch-qq1a.200105.002> .\flash-all.bat
Sending 'bootloader_a' (8521 KB) OKAY [ 0.141s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b1c1-0.2-5946827
(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.281s]
Finished. Total time: 0.672s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.062s
Sending 'radio_a' (71404 KB) OKAY [ 0.484s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g845-00086-191011-B-5933466
(bootloader) Flashing partition modem_a
OKAY [ 0.297s]
Finished. Total time: 1.031s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 894Y03RLY
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.055s]
Checking 'version-bootloader' OKAY [ 0.050s]
Checking 'version-baseband' OKAY [ 0.046s]
Setting current slot to 'a' OKAY [ 0.062s]
extracting boot.img (64 MB) to disk... took 0.250s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.453s]
Writing 'boot_a' OKAY [ 0.203s]
extracting dtbo.img (8 MB) to disk... took 0.063s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.125s]
Writing 'dtbo_a' OKAY [ 0.063s]
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_a' (4 KB) OKAY [ 0.109s]
Writing 'vbmeta_a' OKAY [ 0.062s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.047s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.000s]
Updating super partition OKAY [ 0.031s]
Resizing 'product_a' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.000s]
Resizing 'vendor_a' OKAY [ 0.010s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1984 MB) to disk... took 8.416s
archive does not contain 'product.sig'
Sending 'product' (2032548 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Press any key to exit...
This happens with both the .002 factory image (the correct one for my at&t phone), and the .003 TMO/Fi image. Anyone have any ideas? I'm desperate!
Click to expand...
Click to collapse
The failure at product started during Q beta. To this day, I have seen nobody with an exact reason for it, but there is a fairly easy solution. When the error happens, don't unplug anything or even turn off command prompt. You are still in fastbootd. Press a key on the computer to get back to a command line. Go to recovery on the phone, and start an OTA sideload. If you don't already have the OTA downloaded, you will need to do that. Going from fastbootd to recovery will get you the ability to run adb sideload XXX from command prompt. It will run, complete, change slots and you will not lose data. I have had to do it a few times with my wife's P3. This month before running the flash-all (without -w), I flashed the Dec stock boot.img to both slots and then while still in BL ran the flash-all. Guess what? It took just fine with no product failure.

lukefgoogler said:
Hello all, I'm hoping someone has some advice:
I downloaded the 1/2020 factory image, removed the -w from the .bat file so I didn't lose data, and tried to flash the update via fastboot. Unfortunately, after the phone rebooted into fastbootd during the process, I got an error that says "write to device failed" when sending product. I can't get my system back up, but I can reboot into bootloader and enter recovery. Here is the output from when I tried to flash-all.bat from my computer to write the january update:
PS C:\Users\lukef\Documents\Phone stuff\Pixel 3 XL\crosshatch-qq1a.200105.002> .\flash-all.bat
Sending 'bootloader_a' (8521 KB) OKAY [ 0.141s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b1c1-0.2-5946827
(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.281s]
Finished. Total time: 0.672s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.062s
Sending 'radio_a' (71404 KB) OKAY [ 0.484s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g845-00086-191011-B-5933466
(bootloader) Flashing partition modem_a
OKAY [ 0.297s]
Finished. Total time: 1.031s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 894Y03RLY
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.055s]
Checking 'version-bootloader' OKAY [ 0.050s]
Checking 'version-baseband' OKAY [ 0.046s]
Setting current slot to 'a' OKAY [ 0.062s]
extracting boot.img (64 MB) to disk... took 0.250s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.453s]
Writing 'boot_a' OKAY [ 0.203s]
extracting dtbo.img (8 MB) to disk... took 0.063s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.125s]
Writing 'dtbo_a' OKAY [ 0.063s]
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_a' (4 KB) OKAY [ 0.109s]
Writing 'vbmeta_a' OKAY [ 0.062s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.047s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.000s]
Updating super partition OKAY [ 0.031s]
Resizing 'product_a' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.000s]
Resizing 'vendor_a' OKAY [ 0.010s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1984 MB) to disk... took 8.416s
archive does not contain 'product.sig'
Sending 'product' (2032548 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Press any key to exit...
This happens with both the .002 factory image (the correct one for my at&t phone), and the .003 TMO/Fi image. Anyone have any ideas? I'm desperate!
Click to expand...
Click to collapse
Make sure the USB is not plugged into a charging port

I owe a big "Thank You!" to EVERYONE who replied, sideloading the full OTA using the stock recovery worked like a charm! (Wish I didn't wipe data when I was casting about for a fix...)
Thanks all, you rock.

Stuck on G after running flash-all.bat

Downloaded the most recent and correct firmware for the 3a XL. I unzipped it and ran flash-all.bat.
It has been stuck on G forever. I have tried to then run flash-all.bat from the August firmware and Android 10 with the same result, stuck on G.
Any help appreciated.

OKAY [ 0.300s]
writing 'bootloader'...
(bootloader) Flashing Pack version b4s4-0.2-6355063
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
OKAY [ 0.285s]
finished. total time: 0.600s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
target reported max download size of 268435456 bytes
sending 'radio' (73340 KB)...
OKAY [ 2.072s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g670-00042-200421-B-6414611
(bootloader) Flashing partition modem_a
OKAY [ 0.564s]
finished. total time: 2.636s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.062s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: variable not found)
--------------------------------------------
Bootloader Version...: b4s4-0.2-6355063
Baseband Version.....: g670-00042-200421-B-6414611
Serial Number........: 937AX05B5P
--------------------------------------------
checking product...
OKAY [ 0.069s]
checking version-bootloader...
OKAY [ 0.062s]
checking version-baseband...
OKAY [ 0.054s]
sending 'boot' (65536 KB)...
OKAY [ 1.992s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.471s
Press any key to exit...

Is it failing to flash? Do I do flash-all.bat in fastboot?

Holysmoke99 said:
Is it failing to flash? Do I do flash-all.bat in fastboot?
Click to expand...
Click to collapse
You don't use the flash-all.bat in fastboot. You simply run the bat file (or equivalent) on your computer that you have downloaded the files to and hooked your phone up to. The directions are listed here: https://developers.google.com/android/images
That being said, it does appear to be failing for some reason. Triple check that you have downloaded the correct version for your phone and also check the SHA-256 checksum to ensure the file is not corrupted. Make sure you are on the latest Android SDK Platform Tools as well.

sic0048 said:
You don't use the flash-all.bat in fastboot. You simply run the bat file (or equivalent) on your computer that you have downloaded the files to and hooked your phone up to. The directions are listed here: https://developers.google.com/android/images
That being said, it does appear to be failing for some reason. Triple check that you have downloaded the correct version for your phone and also check the SHA-256 checksum to ensure the file is not corrupted. Make sure you are on the latest Android SDK Platform Tools as well.
Click to expand...
Click to collapse
I had the same issue with a Pixel 3 some time ago and the resolution was to use the latest Android SDK Platform Tools.

Question flash-all.sh vendor partition non-existing

Update: Problem fixed as @Lughnasadh said: flash.android.com fixes the issue a buggy fastboot version can create.
=======
First the log:
Bash:
┬─[[email protected]:~/D/raven-tq2a.230305.008.e1]─[13:36:16]─[I]
╰─>$ sudo ./flash-all.sh
Sending 'bootloader_b' (12094 KB) OKAY [ 0.405s]
Writing 'bootloader_b' (bootloader) Flashing pack version slider-1.2-9465321
(bootloader) flashing platform gs101
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_b
(bootloader) Validating partition pbl_b
(bootloader) Validating partition bl2_b
(bootloader) Validating partition abl_b
(bootloader) Validating partition bl31_b
(bootloader) Validating partition tzsw_b
(bootloader) Validating partition gsa_b
(bootloader) Validating partition ldfw_b
(bootloader) Flashing partition ufs
(bootloader) Flashing partition ufs
(bootloader) Flashing partition partition:0
(bootloader) Flashing partition partition:1
(bootloader) Flashing partition partition:2
(bootloader) Flashing partition partition:3
(bootloader) Flashing partition bl1_b
(bootloader) Flashing partition pbl_b
(bootloader) Flashing partition bl2_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition bl31_b
(bootloader) Flashing partition tzsw_b
(bootloader) Flashing partition gsa_b
(bootloader) Flashing partition ldfw_b
(bootloader) Loading sideload ufsfwupdate
OKAY [ 3.015s]
Finished. Total time: 3.422s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.053s
< waiting for any device >
Sending 'radio_b' (94452 KB) OKAY [ 3.189s]
Writing 'radio_b' (bootloader) Flashing pack version g5123b-112825-230302-M-9675756
(bootloader) Flashing partition modem_b
OKAY [ 0.121s]
Finished. Total time: 3.316s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.050s
< waiting for any device >
--------------------------------------------
Bootloader Version...: slider-1.2-9465321
Baseband Version.....: g5123b-112825-230302-B-9675756
Serial Number........: 23041FDEE005AM
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'b' OKAY [ 0.085s]
extracting boot.img (64 MB) to disk... took 0.524s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.094s]
Writing 'boot_b' OKAY [ 0.076s]
archive does not contain 'init_boot.img'
extracting dtbo.img (16 MB) to disk... took 0.054s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.521s]
Writing 'dtbo_b' OKAY [ 0.022s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.007s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_b' (1024 KB) OKAY [ 0.034s]
Writing 'pvmfw_b' OKAY [ 0.003s]
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' (12 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.002s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_b' OKAY [ 0.002s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor_b' OKAY [ 0.002s]
extracting vendor_boot.img (64 MB) to disk... took 0.473s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (65536 KB) OKAY [ 2.145s]
Writing 'vendor_boot_b' OKAY [ 0.077s]
archive does not contain 'vendor_kernel_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
extracting product.img (2620 MB) to disk... took 21.866s
[liblp] Partition product_b will resize from 0 bytes to 2747355136 bytes
extracting system.img (827 MB) to disk... took 7.403s
[liblp] Partition system_b will resize from 0 bytes to 867323904 bytes
extracting system_ext.img (358 MB) to disk... took 3.044s
[liblp] Partition system_ext_b will resize from 0 bytes to 376356864 bytes
extracting system_other.img (25 MB) to disk... took 0.215s
[liblp] Partition system_a will resize from 0 bytes to 27095040 bytes
extracting vendor.img (517 MB) to disk...fastboot: error:
failed to extract 'vendor.img': I/O error
I seem to not have a vendor partition. when i tried flashing manually, i got the following output:
Bash:
┬─[[email protected]:~/D/raven-tq1a.230105.002]─[13:33:06]─[I]
╰─>$ sudo fastboot flash vendor_b vendor.img
Resizing 'vendor_b' FAILED (remote: 'Invalid command resize-logical-partition:vendor_b:534085632')
fastboot: error: Command failed
┬─[[email protected]:~/D/raven-tq1a.230105.002]─[13:34:08]─[I]
╰─>$ sudo fastboot flash --slot=b vendor vendor.img
Warning: vendor does not support slots, and slot b was requested.
Sending sparse 'vendor' 1/3 (254972 KB) OKAY [ 8.301s]
Writing 'vendor' FAILED (remote: 'partition (vendor) not found')
fastboot: error: Command failed
Background:
I had magisk and a custom kernel installed and so i didnt get any updates anymore after the december update. I removed magisk and flashed the old kernel, but still i didnt get any official update. so in the and, i downloaded latest factory image. i unzipped, removed the "delete userdata"/"-w" part from flash-all.sh and then executed that script.
from the first time i got that i/o error regarding vendor.img - i tried the january and february factory images, too. with no changed to that error....
i dont dare to boot without a vendor partition, so please tell me what i could do. I am prepared to lose my userdata partition in worst case, but i hope this wont happen

the solution might be:
Bash:
fastboot create-logical-partition vendor 518
is that right?
Edit: nope, didnt work:
Bash:
┬─[[email protected]:~/D/raven-tq2a.230305.008.e1]─[13:53:07]─[I]
╰─>$ sudo fastboot create-logical-partition vendor 518
Creating 'vendor' FAILED (remote: 'Invalid command create-logical-partition:vendor:518')
fastboot: error: Command failed
┬─[[email protected]Sofa:~/D/raven-tq2a.230305.008.e1]─[13:53:11]─[I]
╰─>$ sudo fastboot create-logical-partition vendor 534085632
Creating 'vendor' FAILED (remote: 'Invalid command create-logical-partition:vendor:534085632')
fastboot: error: Command failed
┬─[[email protected]:~/D/raven-tq2a.230305.008.e1]─[13:53:13]─[I]
╰─>$ sudo fastboot resize-logical-partition vendor 534085632
Resizing 'vendor' FAILED (remote: 'Invalid command resize-logical-partition:vendor:534085632')
fastboot: error: Command failed

I am having a hard time imagining flashing factory image doesnt work.
So i wonder, is it me removing the -w command line option? if i delete userdata, is there more room for vendor?

mad-murdock said:
I am having a hard time imagining flashing factory image doesnt work.
So i wonder, is it me removing the -w command line option? if i delete userdata, is there more room for vendor?
Click to expand...
Click to collapse
What version of Platform Tools are you using? Versions 34.0.0 & 34.0.1 aren't working properly. Version 33.0.3 is working properly so maybe try that if you haven't.

You were right, i was using 34.0.1.
Problem: With the vendor partition missing, it cannot start fastbootd so ne partition can be created
dilemma!
PLEASE gurus of XDA, show me how to fix this. Or is it so briken i deserve a new phone?

Update: Problem fixed as @Lughnasadh said: flash.android.com fixes the issue a buggy fastboot version can create.