Develop Bugs

New Pixel 3 XL - flash with latest factory images fails?

I'm trading my Pixel 3 for the Pixel 3 XL.
I received the 3XL and I first want to update to the latest image.
About says Build Number PQ2A.190205.001.
I downloaded "crosshatch-pq3a.190801.002-factory-15db810d.zip", and unzipped to a temporary directory on a Windows 10 system (the same system I successfully performed a factory flash on the Pixel 3, using the same process, in April)
I ran flash-all.bat, and have the following log output:
Code:
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>flash-all.bat
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8493 KB)...
OKAY [ 0.253s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5578427
(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.591s]
finished. total time: 0.850s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.074s
target reported max download size of 268435456 bytes
sending 'radio_a' (71132 KB)...
OKAY [ 1.657s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00017-190312-B-5369743
(bootloader) Flashing partition modem_a
OKAY [ 0.282s]
finished. total time: 1.945s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.074s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5578427
Baseband Version.....: g845-00017-190312-B-5369743
Serial Number........: 8A******C1
--------------------------------------------
checking product...
OKAY [ 0.061s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.365s
Press any key to exit...
After this process the phone boots to the factor reset startup process. It is still at Build Number PQ2A.190205.001.
In the log (above), there are multiple messages of the form "archive does not contain '*.img'"
At the end "FAILED (remote: variable not found)"
Any guidance on what went wrong?
I can verify that in the Temp folder I extracted the downloaded ZIP file to, there is another ZIP. image-crosshatch-pq3a.190801.002.zip. That ZIP passes an integrity check. Inside that ZIP there are 20 files (.img and other)

timg11 said:
I'm trading my Pixel 3 for the Pixel 3 XL.
I received the 3XL and I first want to update to the latest image.
About says Build Number PQ2A.190205.001.
I downloaded "crosshatch-pq3a.190801.002-factory-15db810d.zip", and unzipped to a temporary directory on a Windows 10 system (the same system I successfully performed a factory flash on the Pixel 3, using the same process, in April)
I ran flash-all.bat, and have the following log output:
Code:
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>flash-all.bat
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8493 KB)...
OKAY [ 0.253s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5578427
(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.591s]
finished. total time: 0.850s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.074s
target reported max download size of 268435456 bytes
sending 'radio_a' (71132 KB)...
OKAY [ 1.657s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00017-190312-B-5369743
(bootloader) Flashing partition modem_a
OKAY [ 0.282s]
finished. total time: 1.945s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.074s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5578427
Baseband Version.....: g845-00017-190312-B-5369743
Serial Number........: 8A******C1
--------------------------------------------
checking product...
OKAY [ 0.061s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.365s
Press any key to exit...
After this process the phone boots to the factor reset startup process. It is still at Build Number PQ2A.190205.001.
In the log (above), there are multiple messages of the form "archive does not contain '*.img'"
At the end "FAILED (remote: variable not found)"
Any guidance on what went wrong?
I can verify that in the Temp folder I extracted the downloaded ZIP file to, there is another ZIP. image-crosshatch-pq3a.190801.002.zip. That ZIP passes an integrity check. Inside that ZIP there are 20 files (.img and other)
Click to expand...
Click to collapse
Make sure you have the latest sdk platform tools.

Tulsadiver said:
Make sure you have the latest sdk platform tools.
Click to expand...
Click to collapse
Code:
>adb version
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
>fastboot --version
fastboot version 0e9850346394-android
I'll check to see if there are any newer, but this version worked properly on Pixel 3 in April.

Updated Android Platform Tools to platform-tools_r29.0.2-windows.zip
Code:
>fastboot --version
fastboot version 0e9850346394-android
>adb version
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
Same result:
Code:
>fastboot -w update image-crosshatch-pq3a.190801.002.zip
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5578427
Baseband Version.....: g845-00017-190312-B-5369743
Serial Number........: 8A*****C1
--------------------------------------------
checking product...
OKAY [ 0.061s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.364s
This item seems odd: "target reported max download size of 268435456 bytes"
That logged after command "fastboot -w update image-crosshatch-pq3a.190801.002.zip", which is 1.75 Gbytes in size.
The reported max download size is 268 Mbytes 268,435,456
The phone has 128 Gbytes of storage.

No the download size is normal. You're not writing directly to the internal storage but to a ramdisk, where stuff gets unpacked and written to the correct partition afterwards. Your problem is definitely the "checking partition-exists... FAILED" part. Don't know what could cause that off the top of my head though.

timg11 said:
Updated Android Platform Tools to platform-tools_r29.0.2-windows.zip
Code:
>fastboot --version
fastboot version 0e9850346394-android
>adb version
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
-------------------------
checking product...
OKAY [ 0.061s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.364s
[/CODE]
This item seems odd: "target reported max download size of 268435456 bytes"
That logged after command "fastboot -w update image-crosshatch-pq3a.190801.002.zip", which is 1.75 Gbytes in size.
The reported max download size is 268 Mbytes 268,435,456
The phone has 128 Gbytes of storage.
Click to expand...
Click to collapse
I believe that is why system images are broken down into parts. This isn't the problem. At this point your phone is supposed to boot into fastbootd and something is preventing this. Have you tried doing a factory reset first?
Edit: can you run bash script? I run flash-all.sh on my windows 10.

Tulsadiver said:
I believe that is why system images are broken down into parts. This isn't the problem. At this point your phone is supposed to boot into fastbootd and something is preventing this. Have you tried doing a factory reset first?
Edit: can you run bash script? I run flash-all.sh on my windows 10.
Click to expand...
Click to collapse
Download the ota image, and ad sideload from recovery, providing you've not corrupt the phone, it will work. The full factory image flash is messed up imho. Having to unlock the phone to flash a factory image just says it all.

I found the issue - A Windows Path problem. The path was pointing to an older installation of Android Platform Tools different from where I installed the update.
I looked at the versions before and after updating and they were the same. There should have been at least some change.
I fixed the path, and just copied the tools to the update directory as a short term fix.
Here is how the versions look for the latest tools:
Code:
>fastboot --version
fastboot version 29.0.2-5738569
Installed as D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002\fastboot.exe
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>adb version
Android Debug Bridge version 1.0.41
Version 29.0.2-5738569
Installed as D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002\adb.exe
Here's how a successful factory update flash looks for anyone else who needs a reference:
Code:
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>flash-all.bat
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>fastboot flash bootloader bootloader-crosshatch-b1c1-0.1-5578427.img
Sending 'bootloader_a' (8493 KB) OKAY [ 0.284s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b1c1-0.1-5578427
(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.512s]
Finished. Total time: 1.050s
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>fastboot reboot-bootloader
Rebooting into bootloader OKAY [ 0.045s]
Finished. Total time: 0.052s
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>ping -n 5 127.0.0.1 1>nul
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>fastboot flash radio radio-crosshatch-g845-00017-190312-b-5369743.img
Sending 'radio_a' (71132 KB) OKAY [ 1.689s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g845-00017-190312-B-5369743
(bootloader) Flashing partition modem_a
OKAY [ 0.296s]
Finished. Total time: 2.300s
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>fastboot reboot-bootloader
Rebooting into bootloader OKAY [ 0.046s]
Finished. Total time: 0.053s
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>ping -n 5 127.0.0.1 1>nul
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>fastboot -w update image-crosshatch-pq3a.190801.002.zip
--------------------------------------------
Bootloader Version...: b1c1-0.1-5578427
Baseband Version.....: g845-00017-190312-B-5369743
Serial Number........: 8A*****C1
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.050s]
Checking 'version-bootloader' OKAY [ 0.058s]
Checking 'version-baseband' OKAY [ 0.058s]
Setting current slot to 'a' OKAY [ 0.071s]
extracting boot.img (64 MB) to disk... took 0.263s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 1.567s]
Writing 'boot_a' OKAY [ 0.209s]
extracting dtbo.img (8 MB) to disk... took 0.055s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.273s]
Writing 'dtbo_a' OKAY [ 0.071s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (4 KB) OKAY [ 0.114s]
Writing 'vbmeta_a' OKAY [ 0.054s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (194 MB) to disk... took 0.669s
archive does not contain 'product.sig'
Sending 'product_a' (199284 KB) OKAY [ 4.628s]
Writing 'product_a' OKAY [ 0.572s]
extracting system.img (2201 MB) to disk... took 9.765s
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/9 (262140 KB) OKAY [ 6.222s]
Writing 'system_a' OKAY [ 0.062s]
Sending sparse 'system_a' 2/9 (262140 KB) OKAY [ 6.132s]
Writing 'system_a' OKAY [ 0.059s]
Sending sparse 'system_a' 3/9 (262140 KB) OKAY [ 6.184s]
Writing 'system_a' OKAY [ 0.362s]
Sending sparse 'system_a' 4/9 (262140 KB) OKAY [ 6.186s]
Writing 'system_a' OKAY [ 0.361s]
Sending sparse 'system_a' 5/9 (262140 KB) OKAY [ 6.215s]
Writing 'system_a' OKAY [ 0.363s]
Sending sparse 'system_a' 6/9 (262140 KB) OKAY [ 6.076s]
Writing 'system_a' OKAY [ 0.364s]
Sending sparse 'system_a' 7/9 (262140 KB) OKAY [ 6.199s]
Writing 'system_a' OKAY [ 0.364s]
Sending sparse 'system_a' 8/9 (258820 KB) OKAY [ 6.068s]
Writing 'system_a' OKAY [ 0.364s]
Sending sparse 'system_a' 9/9 (160160 KB) OKAY [ 3.829s]
Writing 'system_a' OKAY [ 0.762s]
archive does not contain 'system_ext.img'
extracting system_other.img (422 MB) to disk... took 1.934s
archive does not contain 'system.sig'
Sending sparse 'system_b' 1/2 (262140 KB) OKAY [ 6.162s]
Writing 'system_b' OKAY [ 0.363s]
Sending sparse 'system_b' 2/2 (170820 KB) OKAY [ 4.096s]
Writing 'system_b' OKAY [ 0.853s]
extracting vendor.img (446 MB) to disk... took 1.973s
archive does not contain 'vendor.sig'
Sending sparse 'vendor_a' 1/2 (262140 KB) OKAY [ 6.295s]
Writing 'vendor_a' OKAY [ 0.364s]
Sending sparse 'vendor_a' 2/2 (195404 KB) OKAY [ 4.609s]
Writing 'vendor_a' OKAY [ 0.870s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 15.316s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.100s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Rebooting OKAY [ 0.044s]
Finished. Total time: 128.702s
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>
Interesting to note that there are still various "archive image does not contain...." and "file system not supported" messages, but apparently they are normal.

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.

no more root

Hello, this morning I got a google pay notification that I can't make a payment.
I tried to follow the last tutorial to remove the root, but now I can no longer root my phone or even use google pay.
So I tried to flash my rom via fastboot (crosshatch-qq1a.200105.002), but I get the following error message:
Code:
target reported max download size of 268435456 bytes
sending 'bootloader' (8521 KB)...
OKAY [ 0.333s]
writing 'bootloader'...
(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_b
(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 cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
(bootloader) Flashing partition logfs
OKAY [ 0.506s]
finished. total time: 0.840s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
target reported max download size of 268435456 bytes
sending 'radio' (71404 KB)...
OKAY [ 2.431s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g845-00086-191011-B-5933466
(bootloader) Flashing partition modem_b
OKAY [ 0.457s]
finished. total time: 2.892s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.055s
< waiting for device >
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate 840814800 bytes
error: update package missing system.img
Press any key to exit...
how can i fix my phone please?

chuppito said:
Hello, this morning I got a google pay notification that I can't make a payment.
I tried to follow the last tutorial to remove the root, but now I can no longer root my phone or even use google pay.
So I tried to flash my rom via fastboot (crosshatch-qq1a.200105.002), but I get the following error message:
how can i fix my phone please?
Click to expand...
Click to collapse
Guide
Do #4 'keep data', then #9 to root.
Make sure you have the latest SDK platform-tools, there is a link in the guide.
Also, make sure the USB is not plugged in to a charging USB port.

Hi, thanks it was an adb version issue.
I had done a factory restore and attempted root without success.
I am trying to flash the factory image to test the root again.
The last factory version did not work, I put back the one I had and that worked.
Thank you
Edit : suddenly, I have a bootloop

chuppito said:
Hi, thanks it was an adb version issue.
I had done a factory restore and attempted root without success.
I am trying to flash the factory image to test the root again.
The last factory version did not work, I put back the one I had and that worked.
Thank you
Edit : suddenly, I have a bootloop
Click to expand...
Click to collapse
There's also a thread in here about how to use Gpay with root. You can search for it.

Hi, I managed to install the system cleanly then root. I followed the new google pay tutorial and couldn't make it work. Does it work for you?

Hello it works with this tutorial not with others for me
https://www.xda-developers.com/enable-quick-wallet-access-google-pay-pixel-android-10/

chuppito said:
Hi, I managed to install the system cleanly then root. I followed the new google pay tutorial and couldn't make it work. Does it work for you?
Click to expand...
Click to collapse
I have used the following method (the OP only and not all of the Magisk module stuff) since the day it was posted. I have redone it many times when moving to A10 as well as when going to various ROMs on both a P3 and PX3. GPay has never once failed me since setting it up this way.
https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950

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.

Can't flash bonito-sp1a.211105.002 ( 12.0.0 (SP1A.211105.002, Nov 2021) ) - "Not enough space"

So I'm having the weirdest issue right now and it's driving me crazy.
I have a Pixel 3a XL. All good. It prompted me about updates for a while and now I had some time to do it.
I grabbed the (title) rom file from Google's site, extracted it and changed "flash-all" so it would not wipe storage. (It's the -w switch).
Like I've done a 100 times already. Nothing fancy, nothing new.
I also removed all images from DCIM and my recordings, etc. So there was like a ton of space on the device when I started.
And yet... I run the script and I get this:
Code:
PS D:\_rom\bonito-sp1a.211105.002> .\flash-all.bat
target reported max download size of 268435456 bytes
sending 'bootloader' (8377 KB)...
OKAY [ 0.307s]
writing 'bootloader'...
(bootloader) Flashing Pack version b4s4-0.4-7617386
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
OKAY [ 0.326s]
finished. total time: 0.635s
rebooting into bootloader...
OKAY [ 0.051s]
finished. total time: 0.051s
target reported max download size of 268435456 bytes
sending 'radio' (73372 KB)...
OKAY [ 1.873s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g670-00129-210806-B-7617386
(bootloader) Flashing partition modem_b
OKAY [ 0.473s]
finished. total time: 2.348s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
error: failed to load 'image-bonito-sp1a.211105.002.zip': Not enough space
Press any key to exit...
PS D:\_rom\bonito-sp1a.211105.002>
I am without a clue and I would really need my device.
Please help?
OS is Windows 11, ADB drivers are from the Google USB package (and fastboot commands go out as you can see so that should be fine).
Not sure what else could be amiss.

Okay, another "self-solved mistery".
I've had the latest platform-tools in my PATH, yet something must have messed it up.
So I ran "flash-all.bat" (while removing -w of course) and then once it gets stuck with "not enough space", I simply run the .exe file directly from the new platform-tools folder, with "update ....zip" and that worked.
Man, every update, something gives me a heart attack.