Database Info

boolloop on Pixel 1 after OTA update, cant fix

I am from Russia,i buy Pixel in travel in Europe. After 2 mounth a have OTA update to adnroid Q beta. after this my Pixel go to Bootloop, nothing helps. Today i try to fix it. I have unlock the bootloader, flash the 9.0.0 (PQ3A.190801.002, Aug 2019) by Bootloader, but it doesnt fix, i try to switch to slot b and try flash again, but it doesnt help me. I have a bootlooped pixel! this is the latest flash log, i dont know what to do///
Sending 'bootloader_b' (32424 KB) OKAY [ 1.047s]
Writing 'bootloader_b' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 1.705s]
Finished. Total time: 3.314s
Rebooting into bootloader OKAY [ 0.007s]
Finished. Total time: 0.011s
Sending 'radio_b' (57156 KB) OKAY [ 1.837s]
Writing 'radio_b' OKAY [ 0.496s]
Finished. Total time: 2.793s
Rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.012s
--------------------------------------------
Bootloader Version...: 8996-012001-1904111134
Baseband Version.....: 8996-130281-1903110834
Serial Number........: FA6880302520
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.083s]
Checking 'version-bootloader' OKAY [ 0.037s]
Checking 'version-baseband' OKAY [ 0.045s]
Setting current slot to 'b' OKAY [ 0.098s]
extracting boot.img (29 MB) to disk... took 0.320s
archive does not contain 'boot.sig'
Sending 'boot_b' (29825 KB) OKAY [ 1.000s]
Writing 'boot_b' OKAY [ 0.253s]
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
archive does not contain 'vbmeta.img'
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'
archive does not contain 'product.img'
extracting system.img (1949 MB) to disk... took 69.630s
archive does not contain 'system.sig'
Sending sparse 'system_b' 1/4 (524284 KB) OKAY [ 17.460s]
Writing 'system_b' OKAY [ 3.497s]
Sending sparse 'system_b' 2/4 (524284 KB) OKAY [ 17.404s]
Writing 'system_b' OKAY [ 3.487s]
Sending sparse 'system_b' 3/4 (524284 KB) OKAY [ 17.316s]
Writing 'system_b' OKAY [ 3.484s]
Sending sparse 'system_b' 4/4 (423068 KB) OKAY [ 13.953s]
Writing 'system_b' OKAY [ 2.851s]
archive does not contain 'system_ext.img'
extracting system_other.img (313 MB) to disk... took 8.649s
archive does not contain 'system.sig'
Sending 'system_a' (320532 KB) OKAY [ 9.934s]
Writing 'system_a' OKAY [ 2.184s]
extracting vendor.img (259 MB) to disk... took 6.972s
archive does not contain 'vendor.sig'
Sending 'vendor_b' (265808 KB) OKAY [ 8.253s]
Writing 'vendor_b' OKAY [ 1.813s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 1.960s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 6509568 4k blocks and 1630208 inodes
Filesystem UUID: ce6d7638-cb3b-11e9-ae84-7d8dd3baf4b8
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4272 KB) OKAY [ 0.165s]
Writing 'userdata' OKAY [ 0.099s]
Rebooting OKAY [ 0.046s]
Finished. Total time: 243.010s
Press any key to exit...
I can do all witw phone. lock\unlock bootloader , go to stock recowery, flash and boot into temp TWRP, but nothing helps, some guys say that may be "persist" problems, i am a lamer little bit, i cant find guide for this.

Have you tried flashing the full factory image? Since the bootloader is unlocked, it should be pretty straightforward. You will need a computer, though.

Can not flash factory img:

Hi,
at some point I messed up the flahs of LineageOS and now I would like to get back to the stock img but it does not work anymore. I tried
flash-all.bat but with the same error as shown below.
Code:
C:\Users\XXXX>fastboot flash bootloader "C:\Users\XXX\smartphone\sargo-qp1a.191105.003\bootloader-sargo-b4s4-0.2-5736883.img"
target reported max download size of 268435456 bytes
sending 'bootloader' (8349 KB)...
OKAY [ 0.279s]
writing 'bootloader'...
(bootloader) Flashing Pack version b4s4-0.2-5736883
(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.586s]
finished. total time: 0.865s
C:\Users\XXX>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\XXX>fastboot flash radio "C:\Users\XXX\smartphone\sargo-qp1a.191105.003\radio-sargo-g670-00025-190805-b-5781381.img"
target reported max download size of 268435456 bytes
sending 'radio' (73196 KB)...
OKAY [ 1.673s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g670-00025-190805-B-5781381
(bootloader) Flashing partition modem_b
OKAY [ 0.555s]
finished. total time: 2.244s
C:\Users\XXX>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.038s]
finished. total time: 0.053s
C:\Users\XXX>fastboot -w update "C:\Users\XXX\smartphone\sargo-qp1a.191105.003\image-sargo-qp1a.191105.003.zip"
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'
W/ (15016): Zip: unable to truncate file to 485105848: File too large
failed to extract 'vendor.img': I/O Error
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-5736883
Baseband Version.....: g670-00025-190805-B-5781381
Serial Number........: 97AAY1041S
--------------------------------------------
checking product...
OKAY [ 0.053s]
checking version-bootloader...
OKAY [ 0.063s]
checking version-baseband...
OKAY [ 0.069s]
sending 'boot' (65536 KB)...
OKAY [ 1.520s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.006s
Thank you in advance!
Simon

simhagen said:
Hi,
at some point I messed up the flahs of LineageOS and now I would like to get back to the stock img but it does not work anymore. I tried
flash-all.bat but with the same error as shown below.
Thank you in advance!
Simon
Click to expand...
Click to collapse
I had exactly this issue.
https://forum.xda-developers.com/pixel-3a/how-to/problem-flashing-stock-image-t3997513
You need to update adb fastboot.

Is the drive that you have the zip file saved on nearing it's storage capacity? I suspect it is.
They key line in your log is, "Zip: unable to truncate file to 485105848: File too large" You will get this file if there isn't enough room to properly unzip the file completely. It takes up a decent amount of space on the hard drive.

Horgar said:
I had exactly this issue.
https://forum.xda-developers.com/pixel-3a/how-to/problem-flashing-stock-image-t3997513
You need to update adb fastboot.
Click to expand...
Click to collapse
Ok, so far so good. I tried it on Windows with the newest version, same problem. Than I switched to Linux and it worked up to the point "Sending sparse 'vendor_b' 1/3 (262140 KB)" than it gets stuck and nothing happens.
Code:
[[email protected] MyApplication]$ sudo fastboot flash bootloader /home/XXXX/Downloads/sargo-pd2a.190115.029/bootloader-sargo-b4s4-0.1-5262905.img
Sending 'bootloader_b' (8349 KB) OKAY [ 0.340s]
Writing 'bootloader_b' (bootloader) Flashing Pack version b4s4-0.1-5262905
(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.541s]
Finished. Total time: 1.074s
[[email protected] MyApplication]$ sudo fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.015s]
Finished. Total time: 0.065s
[[email protected] MyApplication]$ sudo fastboot flash radio /home/XXXX/Downloads/sargo-pd2a.190115.029/radio-sargo-g670-00011-190213-b-5306579.img
Sending 'radio_b' (72988 KB) OKAY [ 2.230s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g670-00011-190213-B-5306579
(bootloader) Flashing partition modem_b
OKAY [ 0.880s]
Finished. Total time: 3.315s
[[email protected] MyApplication]$ sudo fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.015s]
Finished. Total time: 0.065s
[[email protected] MyApplication]$ sudo fastboot update -w /home/XXXX/Downloads/sargo-pd2a.190115.029/image-sargo-pd2a.190115.029.zip
--------------------------------------------
Bootloader Version...: b4s4-0.1-5262905
Baseband Version.....: g670-00011-190213-B-5306579
Serial Number........: xxxxxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.051s]
Checking 'version-bootloader' OKAY [ 0.052s]
Checking 'version-baseband' OKAY [ 0.052s]
Setting current slot to 'b' OKAY [ 0.063s]
extracting boot.img (64 MB) to disk... took 0.284s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 1.990s]
Writing 'boot_b' OKAY [ 0.729s]
extracting dtbo.img (8 MB) to disk... took 0.056s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.340s]
Writing 'dtbo_b' OKAY [ 0.133s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (4 KB) OKAY [ 0.120s]
Writing 'vbmeta_b' OKAY [ 0.064s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting system.img (2271 MB) to disk... took 11.015s
archive does not contain 'system.sig'
Sending sparse 'system_b' 1/9 (262140 KB) OKAY [ 7.389s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 2/9 (262140 KB) OKAY [ 7.840s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 3/9 (262140 KB) OKAY [ 7.830s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 4/9 (262140 KB) OKAY [ 7.760s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 5/9 (262140 KB) OKAY [ 7.870s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 6/9 (262140 KB) OKAY [ 7.810s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 7/9 (262140 KB) OKAY [ 7.810s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 8/9 (258620 KB) OKAY [ 7.690s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 9/9 (232288 KB) OKAY [ 7.020s]
Writing 'system_b' OKAY [ 1.920s]
archive does not contain 'system_ext.img'
extracting system_other.img (391 MB) to disk... took 1.914s
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/2 (262140 KB) OKAY [ 7.850s]
Writing 'system_a' OKAY [ 0.370s]
Sending sparse 'system_a' 2/2 (138668 KB) OKAY [ 4.200s]
Writing 'system_a' OKAY [ 1.380s]
extracting vendor.img (523 MB) to disk... took 2.502s
archive does not contain 'vendor.sig'
Sending sparse 'vendor_b' 1/3 (262140 KB)

sic0048 said:
Is the drive that you have the zip file saved on nearing it's storage capacity? I suspect it is.
They key line in your log is, "Zip: unable to truncate file to 485105848: File too large" You will get this file if there isn't enough room to properly unzip the file completely. It takes up a decent amount of space on the hard drive.
Click to expand...
Click to collapse
Should not be the issue since nothing was on the phone to begin with, other than the first running system.

My issue was resetting the path in windows.
https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
If it helps this is what I followed.
Your phone should boot into fastbootd when flashing. That's when I realised it was flashing ok.

Horgar said:
My issue was resetting the path in windows.
https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
If it helps this is what I followed.
Your phone should boot into fastbootd when flashing. That's when I realised it was flashing ok.
Click to expand...
Click to collapse
Thanks,
link does not work for me though...

simhagen said:
Should not be the issue since nothing was on the phone to begin with, other than the first running system.
Click to expand...
Click to collapse
It's not the space on the phone. You don't download and install these factory images from your phone. You have to download them to a computer and install them that way. If you computer is short on storage space, it will give the same error when it tries to upzip the factory image during the installation process. I've had it happen to me before and had to clear up space on my computer in order to finish flashing a factory image.
For example, if you have ADB installed on your C: drive and your C: drive doesn't have several GB of storage space available, you will get this error. It won't help if you have space available on other drives, because ADB only interacts with the folder it is installed on. So having 100 GB free on another drive won't help as an example.

sic0048 said:
It's not the space on the phone. You don't download and install these factory images from your phone. You have to download them to a computer and install them that way. If you computer is short on storage space, it will give the same error when it tries to upzip the factory image during the installation process. I've had it happen to me before and had to clear up space on my computer in order to finish flashing a factory image.
Click to expand...
Click to collapse
That as wll should not be the case or the unzip will be larger than 30 GB? That is the space left on my notebook

simhagen said:
That as wll should not be the case or the unzip will be larger than 30 GB? That is the space left on my notebook
Click to expand...
Click to collapse
No. As long as that space is available on your main drive (see my edit above), 30 GB should be plenty of space. I'm thinking it takes around 5 GB if I remember correctly.

simhagen said:
Thanks,
link does not work for me though...
Click to expand...
Click to collapse
https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Try this

Hi,
so with the last post the update of fastboot worked fine and the flashing went well. Thanks! Stange thing was, it did not work under Linux it stopped at flashing vendor_b (nothing happend for half an hour or so, tried it several times with different Android 10 versions):
Code:
extracting vendor.img (523 MB) to disk... took 2.502s
archive does not contain 'vendor.sig'
Sending sparse 'vendor_b' 1/3 (262140 KB)
under Windows I didn't get this problem. So system is up and running again.
Thank you!

simhagen said:
Hi,
so with the last post the update of fastboot worked fine and the flashing went well. Thanks! Stange thing was, it did not work under Linux it stopped at flashing vendor_b (nothing happend for half an hour or so, tried it several times with different Android 10 versions):
under Windows I didn't get this problem. So system is up and running again.
Thank you!
Click to expand...
Click to collapse
Glad to hear you're sorted. It took me a while to work out I just needed to update fastboot. Someone on XDA helped me with it.

simhagen said:
Ok, so far so good. I tried it on Windows with the newest version, same problem. Than I switched to Linux and it worked up to the point "Sending sparse 'vendor_b' 1/3 (262140 KB)" than it gets stuck and nothing happens.
Click to expand...
Click to collapse
I had the exact same problem as you did. I tried different versions of the stock ROM, I tried different versions of the fastboot tool (including sdkmanager --update to get to the latest, etc.). It failed at the same time, every time: "Sending sparse 'vendor_a'"
What actually worked for me was plugging the USB cable into a port directly on the laptop, instead of a hub built into the docking station.
**** you not, worked perfectly. Same cable, same fastboot binary, same laptop, same OS, just switching to a different port did the trick. Don't plug the cable into a USB hub.

Pixel bricked, need help

My Pixel( G-2PW4100) doesn't boot up. I tried some steps to flash, unbrick it, but no success so far. Can someone help?
I put it to fastboot, and downloaded the latest factory image, run flash-all command (as below).
The device still doesn't power up, showing "Your device software cannot be checked for corruption......"
then I ran "fastboot flashing lock" to relock the bootloader, it still failed to power up, showing "no command"
I tried: "adb sideload sailfish-ota-qp1a.191005.007.a3-394b5899.zip". It still doesn't power up. What should I do??? Thanks in advance.
adb sideload sailfish-ota-qp1a.191005.007.a3-394b5899.zip
serving: 'sailfish-ota-qp1a.191005.007.a3-394b5899.zip' (~94%) adb: failed to read command: No error
sailfish-qp1a.191005.007.a3>flash-all.bat
Sending 'bootloader_a' (32480 KB) OKAY [ 0.840s]
Writing 'bootloader_a' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 1.996s]
Finished. Total time: 3.037s
Rebooting into bootloader OKAY [ 0.008s]
Finished. Total time: 0.014s
Sending 'radio_a' (57156 KB) OKAY [ 1.492s]
Writing 'radio_a' OKAY [ 0.448s]
Finished. Total time: 2.120s
Rebooting into bootloader OKAY [ 0.038s]
Finished. Total time: 0.044s
--------------------------------------------
Bootloader Version...: 8996-012001-1908071822
Baseband Version.....: 8996-130361-1905270421
Serial Number........: xxxxxxxxxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.048s]
Checking 'version-bootloader' OKAY [ 0.048s]
Checking 'version-baseband' OKAY [ 0.048s]
Setting current slot to 'a' OKAY [ 0.069s]
extracting boot.img (30 MB) to disk... took 0.177s
archive does not contain 'boot.sig'
Sending 'boot_a' (30793 KB) OKAY [ 0.784s]
Writing 'boot_a' OKAY [ 0.263s]
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
archive does not contain 'vbmeta.img'
archive does not contain 'vbmeta_system.img'
archive does not contain 'vbmeta_vendor.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
archive does not contain 'product.img'
extracting system.img (1989 MB) to disk... took 9.375s
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/4 (524284 KB) OKAY [ 13.014s]
Writing 'system_a' OKAY [ 3.399s]
Sending sparse 'system_a' 2/4 (524284 KB) OKAY [ 13.087s]
Writing 'system_a' OKAY [ 3.430s]
Sending sparse 'system_a' 3/4 (524284 KB) OKAY [ 13.161s]
Writing 'system_a' OKAY [ 3.409s]
Sending sparse 'system_a' 4/4 (464416 KB) OKAY [ 11.451s]
Writing 'system_a' OKAY [ 3.095s]
archive does not contain 'system_ext.img'
extracting system_other.img (293 MB) to disk... took 1.669s
archive does not contain 'system.sig'
Sending 'system_b' (300296 KB) OKAY [ 7.362s]
Writing 'system_b' OKAY [ 2.009s]
extracting vendor.img (253 MB) to disk... took 1.414s
archive does not contain 'vendor.sig'
Sending 'vendor_a' (259272 KB) OKAY [ 6.421s]
Writing 'vendor_a' OKAY [ 1.743s]
archive does not contain 'vendor_dlkm.img'
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 1.652s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 6509568 4k blocks and 1630208 inodes
Filesystem UUID: ffe940a8-945f-11ec-8982-07edb72ed496
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (180 KB) OKAY [ 0.057s]
Writing 'userdata' OKAY [ 0.046s]
Rebooting OKAY [ 0.039s]
Finished. Total time: 100.707s
Press any key to exit...

Hello, have you solved this problem?

No.

eso esta gratis en google

raikigsm said:
eso esta gratis en google
Click to expand...
Click to collapse
Any pointers? I searched a lot, but cannot find a solution.
After relocking bootloader and reboot, it shows a google screen, and then "No command"

Is it because bootloader is locked? I did try to use fastboot command to unlock. It said "success".

Question Help ? What am i doing wrong

Hi, flashing android 9 gsi roms, works fine on my device(TA-1191). But any/all A11 gsi's just don't. Ok so i flashed the a9 nokia firmware from the unlock guide, then did an OTA update and flashed magisk. Everything is fine up to this point. But flashing the following gsi's don't work:
Corvus_vS3.0-Revenant-treble_arm64_ab_vndklite-Beta-Official-0800.img
Corvus_vS4.0-Leviathan-treble_arm64_ab_vndklite-Official-0038.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bvS-vndklite.img
system-roar-arm64-ab-vndklite-floss.img
And a few other unamed/system gsis...
This the method or guide being followed:
Code:
PS C:\adb\platform-tools_r31.0.3-windows> fastboot devices
HZAL1670EAJ81901791 fastboot
PS C:\adb\platform-tools_r31.0.3-windows> fastboot flash system lineage-20.0-20230324-UNOFFICIAL-arm64_bvS-vndklite.img
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/17 (131028 KB) OKAY [ 5.882s]
Writing 'system_b' OKAY [ 1.966s]
Sending sparse 'system_b' 2/17 (131052 KB) OKAY [ 5.944s]
Writing 'system_b' OKAY [ 1.928s]
Sending sparse 'system_b' 3/17 (131064 KB) OKAY [ 5.973s]
Writing 'system_b' OKAY [ 2.396s]
Sending sparse 'system_b' 4/17 (131056 KB) OKAY [ 5.940s]
Writing 'system_b' OKAY [ 2.449s]
Sending sparse 'system_b' 5/17 (131052 KB) OKAY [ 5.922s]
Writing 'system_b' OKAY [ 1.948s]
Sending sparse 'system_b' 6/17 (131056 KB) OKAY [ 5.940s]
Writing 'system_b' OKAY [ 1.919s]
Sending sparse 'system_b' 7/17 (131068 KB) OKAY [ 5.947s]
Writing 'system_b' OKAY [ 1.920s]
Sending sparse 'system_b' 8/17 (131052 KB) OKAY [ 5.899s]
Writing 'system_b' OKAY [ 2.532s]
Sending sparse 'system_b' 9/17 (131068 KB) OKAY [ 5.942s]
Writing 'system_b' OKAY [ 1.920s]
Sending sparse 'system_b' 10/17 (131060 KB) OKAY [ 5.895s]
Writing 'system_b' OKAY [ 1.925s]
Sending sparse 'system_b' 11/17 (130928 KB) OKAY [ 5.920s]
Writing 'system_b' OKAY [ 1.988s]
Sending sparse 'system_b' 12/17 (130525 KB) OKAY [ 5.967s]
Writing 'system_b' OKAY [ 2.680s]
Sending sparse 'system_b' 13/17 (131032 KB) OKAY [ 5.931s]
Writing 'system_b' OKAY [ 2.488s]
Sending sparse 'system_b' 14/17 (131048 KB) OKAY [ 6.210s]
Writing 'system_b' OKAY [ 1.942s]
Sending sparse 'system_b' 15/17 (131060 KB) OKAY [ 5.928s]
Writing 'system_b' OKAY [ 1.927s]
Sending sparse 'system_b' 16/17 (131068 KB) OKAY [ 5.913s]
Writing 'system_b' OKAY [ 1.920s]
Sending sparse 'system_b' 17/17 (57706 KB) OKAY [ 2.675s]
Writing 'system_b' OKAY [ 1.900s]
Finished. Total time: 150.659s
PS C:\adb\platform-tools_r31.0.3-windows> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_b' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta_b' OKAY [ 0.002s]
Finished. Total time: 0.032s
PS C:\adb\platform-tools_r31.0.3-windows> fastboot -w
Erasing 'userdata' OKAY [ 0.224s]
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
PS C:\adb\platform-tools_r31.0.3-windows> fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.004s
PS C:\adb\platform-tools_r31.0.3-windows>
And the issue eperienced is either Bootlooping or rebooting into twrp recovery. Also formating data in twrp makes no difference. The vbmeta.img used, is from the ota updated firmware base.
I don't if i might be flashing the wrong gsi images ? If someone could correct me please.
Thanks.

Still can't seem to fix it. Help anyone ?

Ok realized that the los 20 and the above gsi's are a12/13 based. And that the gsi rom should match your base firmware android version. So I tried the following gsi's that are a11 and still no luck:
bless-v306-210502-arm64-bvZ-lite.img
caos-v316-220321-arm64-bvZ-lite.img
HavocOS-arm64-bvN-lite.img (also a11)
system-roar-arm64-ab-vndklite-vanilla.img (also a11)
Could anyone share some links of working android 11 gsi's ? Please ?

Question Android 14 Beta 1 factory image flash fails with error

# Phone Config
Pixel 7 Pro, running Android 14 DP2, Magisk 26.1.
I downloaded the 14 Beta 1 factory image today from the official site, and verified that the checksum matches.
Extracted the zip into my existing platform-tools folder (on Windows), removed the -w flag from the flash-all.bat and ran it. (After connecting the phone in bootloader mode to the computer via USB cable.)
Everything runs fine, until the very end, where it failed to flash the vendor img. Here's the full log -
Code:
Sending 'bootloader_a' (13927 KB) OKAY [ 0.109s]
Writing 'bootloader_a' (bootloader) Flashing pack version cloudripper-14.0-9701414
(bootloader) flashing platform gs201
(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_a
(bootloader) Validating partition pbl_a
(bootloader) Validating partition bl2_a
(bootloader) Validating partition abl_a
(bootloader) Validating partition bl31_a
(bootloader) Validating partition tzsw_a
(bootloader) Validating partition gsa_a
(bootloader) Validating partition ldfw_a
(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_a
(bootloader) Flashing partition pbl_a
(bootloader) Flashing partition bl2_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition bl31_a
(bootloader) Flashing partition tzsw_a
(bootloader) Flashing partition gsa_a
(bootloader) Flashing partition ldfw_a
(bootloader) Loading sideload ufsfwupdate
OKAY [ 0.262s]
Finished. Total time: 0.380s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.003s
< waiting for any device >
Sending 'radio_a' (111960 KB) OKAY [ 0.917s]
Writing 'radio_a' (bootloader) Flashing pack version g5300q-230217-230224-M-9650069
(bootloader) Flashing partition modem_a
OKAY [ 0.571s]
Finished. Total time: 1.496s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.004s
< waiting for any device >
--------------------------------------------
Bootloader Version...: cloudripper-14.0-9701414
Baseband Version.....: g5300q-230217-230224-B-9650069
Serial Number........: REDACTING
--------------------------------------------
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 'a' OKAY [ 0.080s]
extracting boot.img (64 MB) to disk... took 0.196s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.535s]
Writing 'boot_a' OKAY [ 0.231s]
extracting init_boot.img (8 MB) to disk... took 0.022s
archive does not contain 'init_boot.sig'
Sending 'init_boot_a' (8192 KB) OKAY [ 0.068s]
Writing 'init_boot_a' OKAY [ 0.015s]
extracting dtbo.img (16 MB) to disk... took 0.029s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (16384 KB) OKAY [ 0.139s]
Writing 'dtbo_a' OKAY [ 0.019s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.003s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_a' (1024 KB) OKAY [ 0.009s]
Writing 'pvmfw_a' OKAY [ 0.003s]
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' (12 KB) OKAY [ 0.000s]
Writing 'vbmeta_a' OKAY [ 0.003s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system_a' OKAY [ 0.001s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor_a' OKAY [ 0.002s]
extracting vendor_boot.img (64 MB) to disk... took 0.186s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_a' (65536 KB) OKAY [ 0.554s]
Writing 'vendor_boot_a' OKAY [ 0.075s]
extracting vendor_kernel_boot.img (64 MB) to disk... took 0.128s
archive does not contain 'vendor_kernel_boot.sig'
Sending 'vendor_kernel_boot_a' (65536 KB) OKAY [ 0.554s]
Writing 'vendor_kernel_boot_a' OKAY [ 0.080s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
Sending 'super' (5 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 1.039s]
Resizing 'product_a' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.002s]
Resizing 'system_dlkm_a' OKAY [ 0.002s]
Resizing 'system_ext_a' OKAY [ 0.003s]
Resizing 'system_b' OKAY [ 0.002s]
Resizing 'vendor_a' OKAY [ 0.003s]
Resizing 'vendor_dlkm_a' OKAY [ 0.003s]
Resizing 'vendor_b' OKAY [ 0.002s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (2925 MB) to disk... took 11.503s
archive does not contain 'product.sig'
Resizing 'product_a' OKAY [ 0.008s]
Sending sparse 'product_a' 1/12 (262112 KB) OKAY [ 0.996s]
Writing 'product_a' OKAY [ 0.753s]
Sending sparse 'product_a' 2/12 (262124 KB) OKAY [ 0.982s]
Writing 'product_a' OKAY [ 0.944s]
Sending sparse 'product_a' 3/12 (262128 KB) OKAY [ 0.966s]
Writing 'product_a' OKAY [ 1.011s]
Sending sparse 'product_a' 4/12 (262120 KB) OKAY [ 0.968s]
Writing 'product_a' OKAY [ 0.936s]
Sending sparse 'product_a' 5/12 (262124 KB) OKAY [ 0.979s]
Writing 'product_a' OKAY [ 1.052s]
Sending sparse 'product_a' 6/12 (262128 KB) OKAY [ 0.970s]
Writing 'product_a' OKAY [ 0.933s]
Sending sparse 'product_a' 7/12 (262124 KB) OKAY [ 0.984s]
Writing 'product_a' OKAY [ 1.052s]
Sending sparse 'product_a' 8/12 (262124 KB) OKAY [ 0.966s]
Writing 'product_a' OKAY [ 0.999s]
Sending sparse 'product_a' 9/12 (262128 KB) OKAY [ 0.971s]
Writing 'product_a' OKAY [ 1.063s]
Sending sparse 'product_a' 10/12 (262124 KB) OKAY [ 0.977s]
Writing 'product_a' OKAY [ 0.968s]
Sending sparse 'product_a' 11/12 (262092 KB) OKAY [ 0.968s]
Writing 'product_a' OKAY [ 0.819s]
Sending sparse 'product_a' 12/12 (102712 KB) OKAY [ 0.394s]
Writing 'product_a' OKAY [ 0.161s]
extracting system.img (899 MB) to disk... took 3.753s
archive does not contain 'system.sig'
Resizing 'system_a' OKAY [ 0.042s]
Sending sparse 'system_a' 1/4 (262116 KB) OKAY [ 1.028s]
Writing 'system_a' OKAY [ 0.526s]
Sending sparse 'system_a' 2/4 (262116 KB) OKAY [ 0.994s]
Writing 'system_a' OKAY [ 0.965s]
Sending sparse 'system_a' 3/4 (262140 KB) OKAY [ 0.972s]
Writing 'system_a' OKAY [ 1.174s]
Sending sparse 'system_a' 4/4 (131716 KB) OKAY [ 0.496s]
Writing 'system_a' OKAY [ 0.556s]
extracting system_dlkm.img (0 MB) to disk... took 0.001s
archive does not contain 'system_dlkm.sig'
Resizing 'system_dlkm_a' OKAY [ 0.006s]
Sending 'system_dlkm_a' (340 KB) OKAY [ 0.003s]
Writing 'system_dlkm_a' OKAY [ 0.045s]
extracting system_ext.img (256 MB) to disk... took 1.042s
archive does not contain 'system_ext.sig'
Resizing 'system_ext_a' OKAY [ 0.008s]
Sending sparse 'system_ext_a' 1/1 (262068 KB) OKAY [ 1.016s]
Writing 'system_ext_a' OKAY [ 0.939s]
extracting system_other.img (16 MB) to disk... took 0.086s
archive does not contain 'system.sig'
Resizing 'system_b' OKAY [ 0.011s]
Sending 'system_b' (17264 KB) OKAY [ 0.064s]
Writing 'system_b' OKAY [ 0.093s]
extracting vendor.img (699 MB) to disk... took 2.624s
archive does not contain 'vendor.sig'
Resizing 'vendor_a' OKAY [ 0.007s]
Sending sparse 'vendor_a' 1/3 (262120 KB) OKAY [ 0.996s]
Writing 'vendor_a' OKAY [ 1.194s]
Sending sparse 'vendor_a' 2/3 (262116 KB) OKAY [ 0.992s]
Writing 'vendor_a' OKAY [ 0.504s]
Sending sparse 'vendor_a' 3/3 (189388 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
Press any key to exit...
I noticed that the platform-tools was an old version (33.0.3). So, I downloaded the latest 34.0.0 RC2 from the Android developer site and reran the falsh-all.bat. This time, the flash fails with a different error (I'm not pasting the bootloader / radio part of the log here, as they were fine.) -
Code:
--------------------------------------------
Bootloader Version...: cloudripper-14.0-9701414
Baseband Version.....: g5300q-230217-230224-B-9650069
Serial Number........: REDACTING
--------------------------------------------
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 'a' OKAY [ 0.077s]
extracting boot.img (64 MB) to disk... took 0.186s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.529s]
Writing 'boot_a' OKAY [ 0.075s]
extracting init_boot.img (8 MB) to disk... took 0.020s
archive does not contain 'init_boot.sig'
Sending 'init_boot_a' (8192 KB) OKAY [ 0.069s]
Writing 'init_boot_a' OKAY [ 0.017s]
extracting dtbo.img (16 MB) to disk... took 0.028s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (16384 KB) OKAY [ 0.134s]
Writing 'dtbo_a' OKAY [ 0.019s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.004s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_a' (1024 KB) OKAY [ 0.009s]
Writing 'pvmfw_a' 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_a' (12 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.001s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system_a' OKAY [ 0.002s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_vendor_a' OKAY [ 0.002s]
extracting vendor_boot.img (64 MB) to disk... took 0.173s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_a' (65536 KB) OKAY [ 0.542s]
Writing 'vendor_boot_a' OKAY [ 0.075s]
extracting vendor_kernel_boot.img (64 MB) to disk... took 0.122s
archive does not contain 'vendor_kernel_boot.sig'
Sending 'vendor_kernel_boot_a' (65536 KB) OKAY [ 0.553s]
Writing 'vendor_kernel_boot_a' OKAY [ 0.074s]
extracting super_empty.img (0 MB) to disk... took 0.001s
extracting product.img (2925 MB) to disk... took 10.295s
[liblp] Partition product_a will resize from 0 bytes to 3067695104 bytes
extracting system.img (899 MB) to disk... took 3.202s
[liblp] Partition system_a will resize from 0 bytes to 943325184 bytes
extracting system_dlkm.img (0 MB) to disk... took 0.001s
[liblp] Partition system_dlkm_a will resize from 0 bytes to 348160 bytes
extracting system_ext.img (256 MB) to disk... took 0.948s
[liblp] Partition system_ext_a will resize from 0 bytes to 269307904 bytes
extracting system_other.img (16 MB) to disk... took 0.074s
[liblp] Partition system_b will resize from 0 bytes to 17678336 bytes
extracting vendor.img (699 MB) to disk... took 7.555s
[liblp] Partition vendor_a will resize from 0 bytes to 733212672 bytes
extracting vendor_dlkm.img (42 MB) to disk... took 0.115s
[liblp] Partition vendor_dlkm_a will resize from 0 bytes to 44281856 bytes
archive does not contain 'vendor_other.img'
Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
fastboot: error: Command failed
Press any key to exit...
Platform tools 34.0.0 RC2 throws this same error when trying to flash 14 DP2 too. Platform tools 33.0.3 flashes 14 DP2 fine.
Anyone else has faced this issue and knows a fix?

People have been having issues with Platform Tools 34 since its release. The only fix I know is to uninstall 34 and revert to installing 33.03. I haven't had any problems flashing the latest stable build on 33.03 and it looks like people have had success with flashing the latest Android 14 beta with it as well.

synesthete said:
People have been having issues with Platform Tools 34 since its release. The only fix I know is to uninstall 34 and revert to installing 33.03. I haven't had any problems flashing the latest stable build on 33.03 and it looks like people have had success with flashing the latest Android 14 beta with it as well.
Click to expand...
Click to collapse
I get the platform tools from here. The download is just a portable zip, not an installer needing any uninstall / install. I deleted the 34 RC2 download and went back to my previous 33.0.3 download. But through that too, I'm getting this error for 14B1 -
Code:
Sending sparse 'vendor_a' 3/3 (189388 KB) FAILED (Write to device failed (Unknown error))
14DP2 flashes fine with 33.0.3.

I got this also as did others in the Android 14 thread. I don't know what Google are on. First the platform tools bug which still isn't fixed and now this. I get and fully expect to run into issues within the OS itself, but not even being able to flash the build?
I'll laugh/cry if this also affects the non-pro and even the Pixel 6, but even without that just a single device failing flash seems like a complete amature mistake to have made.
We are all just going to have to avoid the build and hope someone at Google cares enough to fix it, or wee just wait until beta 2 next month I guess, and rely on having to use using OTA updates until then.

Dave_247 said:
I got this also as did others in the Android 14 thread.
Click to expand...
Click to collapse
Can you please give me a link to that thread?

Just use android flash tool to install this a14 beta
Working properly

cultofluna said:
Just use android flash tool to install this a14 beta
Working properly
Click to expand...
Click to collapse
I haven't used that before. Does that provide an option to flash without wipe or does that mandatorily wipe the device while flashing?

bagarwa said:
I haven't used that before. Does that provide an option to flash without wipe or does that mandatorily wipe the device while flashing?
Click to expand...
Click to collapse
Yes you can choose any option you want ..
With or without wipe/ or disable verity/ verification

cultofluna said:
Yes you can choose any option you want ..
With or without wipe/ or disable verity/ verification
Click to expand...
Click to collapse
I only used Android Flash Tool once, but I don't believe it could disable verity & verification...
Did you by chance mean badabing2003's PixelFlasher? I know for sure that that program does this, and it most likely can flash Android 14 as well...

cultofluna said:
Yes you can choose any option you want ..
With or without wipe/ or disable verity/ verification
Click to expand...
Click to collapse
I tried the flashing tool now, but that too kept failing, this time at flashing product 11/12.
{
"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"
}
But I finally managed to finish the flash on my local. I used a different USB C to C cable (previously I was using A to C) on a different port of the laptop. The file transfer from PC to phone (the "Sending sparse..." parts) were much slower this time (~6 seconds for each part, compared to less than 1 second before). But the flash finally successfully finished. And now I've booted into 14B1.

simplepinoi177 said:
I only used Android Flash Tool once, but I don't believe it could disable verity & verification...
Did you by chance mean badabing2003's PixelFlasher? I know for sure that that program does this, and it most likely can flash Android 14 as well...
Click to expand...
Click to collapse
You can disable verity/ verification with android flash tool
And i don't mean Pixel flasher

bagarwa said:
I tried the flashing tool now, but that too kept failing, this time at flashing product 11/12.
But I finally managed to finish the flash on my local. I used a different USB C to C cable (previously I was using A to C) on a different port of the laptop. The file transfer from PC to phone (the "Sending sparse..." parts) were much slower this time (~6 seconds for each part, compared to less than 1 second before). But the flash finally successfully finished. And now I've booted into 14B1.
Click to expand...
Click to collapse
Interesting, I always get 6 seconds using my C-to-C cable too.

bagarwa said:
Can you please give me a link to that thread?
Click to expand...
Click to collapse
Here's the thread. It was started folowingf the devloper preview versions of 14 but has not sahifted to the beta versions.
June 7, 2023 - Beta 3 UPB3.230519.008 Global - Android 14 "Upside Down Cake" - Pixel 7 Pro [Cheetah]
Android 14 Beta program for the Pixel 7 Pro [Cheetah] Download links in the middle of the OP. Welcome to the Android 14 Developer Preview! This first release is for developers only, to help with early development, testing, and feedback...
forum.xda-developers.com

cultofluna said:
Just use android flash tool to install this a14 beta
Working properly
Click to expand...
Click to collapse
bagarwa said:
I tried the flashing tool now, but that too kept failing, this time at flashing product 11/12.
View attachment 5887309
But I finally managed to finish the flash on my local. I used a different USB C to C cable (previously I was using A to C) on a different port of the laptop. The file transfer from PC to phone (the "Sending sparse..." parts) were much slower this time (~6 seconds for each part, compared to less than 1 second before). But the flash finally successfully finished. And now I've booted into 14B1.
Click to expand...
Click to collapse
I was getting the same error so I gave up and manually flashed the developer preview 2 then did a OTA update to get to Beta 1. There has to be something wrong with the build itself to be having this many issues for so many people.