Hey guys - I am getting the following error when trying to flash the 11 preview, any ideas?
[email protected] ~/Downloads $ fastboot -w update image-sargo-rpp1.200123.016.zip
--------------------------------------------
Bootloader Version...: b4s4-0.2-6110009
Baseband Version.....: g670-00038-200117-B-6143243
Serial Number........: 93HAY0BGZZ
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.059s]
Checking 'version-bootloader' OKAY [ 0.059s]
Checking 'version-baseband' OKAY [ 0.060s]
Setting current slot to 'a' OKAY [ 0.143s]
extracting boot.img (64 MB) to disk... took 0.318s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 2.270s]
Writing 'boot_a' OKAY [ 0.414s]
extracting dtbo.img (8 MB) to disk... took 0.064s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.370s]
Writing 'dtbo_a' OKAY [ 0.094s]
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.120s]
Writing 'vbmeta_a' OKAY [ 0.065s]
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.060s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.011s]
Resizing 'product_a' OKAY [ 0.005s]
Resizing 'system_a' OKAY [ 0.006s]
Resizing 'system_ext_a' OKAY [ 0.004s]
Resizing 'vendor_a' OKAY [ 0.005s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1644 MB) to disk...ziparchive W 03-03 12:34:08 17940 17940 Zip: inflate zerr=-3 (nIn=0x5af378892b33 aIn=31341 nOut=0x5af37889eac0 aOut=15088)
fastboot: error:
failed to extract 'product.img': Zlib error
Not sure what to do.. Im sure i've encountered this before but cant remember how to fix
Try to adb sideload it. It will work. I've been going back and forth. Sideload works & with the factory image, it only wants to work if I remove -w from the batch file which is weird.
Related
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.
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".
Updated the image on a Pixel 6a today and my eye caught this error. So I flased it again and again the same error? Is this normal? What is it? See log below.
Thanks
C:\ADB>adb devices
List of devices attached
12345ABCD12345 device
C:\ADB>adb reboot bootloader
C:\ADB>flash-all.bat
Sending 'bootloader_a' (11558 KB) OKAY [ 0.288s]
Writing 'bootloader_a' (bootloader) Flashing pack version bluejay-1.2-8893284
(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_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 [ 2.862s]
Finished. Total time: 3.178s
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.001s
Sending 'radio_a' (82772 KB) OKAY [ 2.051s]
Writing 'radio_a' (bootloader) Flashing pack version g5123b-102852-220720-M-8851166
(bootloader) Flashing partition modem_a
OKAY [ 0.143s]
Finished. Total time: 2.205s
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.002s
--------------------------------------------
Bootloader Version...: bluejay-1.2-8893284
Baseband Version.....: g5123b-102852-220720-B-8851166
Serial Number........: 12345ABCD12345
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'a' OKAY [ 0.069s]
extracting boot.img (64 MB) to disk... took 0.250s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 1.619s]
Writing 'boot_a' OKAY [ 0.112s]
archive does not contain 'init_boot.img'
extracting dtbo.img (16 MB) to disk... took 0.042s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (16384 KB) OKAY [ 0.405s]
Writing 'dtbo_a' OKAY [ 0.024s]
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.026s]
Writing 'pvmfw_a' OKAY [ 0.004s]
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.002s]
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.003s]
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.001s]
Writing 'vbmeta_vendor_a' OKAY [ 0.002s]
extracting vendor_boot.img (64 MB) to disk... took 0.271s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_a' (65536 KB) OKAY [ 1.618s]
Writing 'vendor_boot_a' OKAY [ 0.116s]
archive does not contain 'vendor_kernel_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.022s]
Resizing 'product_a' OKAY [ 0.006s]
Resizing 'system_a' OKAY [ 0.004s]
Resizing 'system_ext_a' OKAY [ 0.004s]
Resizing 'system_b' OKAY [ 0.004s]
Resizing 'vendor_a' OKAY [ 0.003s]
Resizing 'vendor_dlkm_a' OKAY [ 0.003s]
Resizing 'vendor_b' OKAY [ 0.003s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (2761 MB) to disk... took 11.348s
Invalid sparse file format at header magic
archive does not contain 'product.sig'
Resizing 'product_a' OKAY [ 0.011s]
Sending sparse 'product_a' 1/11 (262116 KB) OKAY [ 6.789s]
Writing 'product_a' OKAY [ 0.414s]
Sending sparse 'product_a' 2/11 (262120 KB) OKAY [ 6.782s]
Writing 'product_a' OKAY [ 0.385s]
Sending sparse 'product_a' 3/11 (262128 KB) OKAY [ 6.773s]
Writing 'product_a' OKAY [ 0.417s]
Sending sparse 'product_a' 4/11 (262120 KB) OKAY [ 6.785s]
Writing 'product_a' OKAY [ 0.378s]
Sending sparse 'product_a' 5/11 (262120 KB) OKAY [ 6.774s]
Writing 'product_a' OKAY [ 0.402s]
Sending sparse 'product_a' 6/11 (262124 KB) OKAY [ 6.781s]
Writing 'product_a' OKAY [ 0.373s]
Sending sparse 'product_a' 7/11 (262124 KB) OKAY [ 6.807s]
Writing 'product_a' OKAY [ 0.437s]
Sending sparse 'product_a' 8/11 (262128 KB) OKAY [ 6.831s]
Writing 'product_a' OKAY [ 0.393s]
Sending sparse 'product_a' 9/11 (262132 KB) OKAY [ 6.804s]
Writing 'product_a' OKAY [ 0.401s]
Sending sparse 'product_a' 10/11 (262096 KB) OKAY [ 6.809s]
Writing 'product_a' OKAY [ 0.408s]
Sending sparse 'product_a' 11/11 (197804 KB) OKAY [ 5.233s]
Writing 'product_a' OKAY [ 0.323s]
extracting system.img (831 MB) to disk... took 3.673s
Invalid sparse file format at header magic
archive does not contain 'system.sig'
Resizing 'system_a' OKAY [ 0.010s]
Sending sparse 'system_a' 1/4 (262116 KB) OKAY [ 6.908s]
Writing 'system_a' OKAY [ 0.411s]
Sending sparse 'system_a' 2/4 (262116 KB) OKAY [ 6.871s]
Writing 'system_a' OKAY [ 0.425s]
Sending sparse 'system_a' 3/4 (262140 KB) OKAY [ 6.825s]
Writing 'system_a' OKAY [ 0.423s]
Sending sparse 'system_a' 4/4 (62708 KB) OKAY [ 1.645s]
Writing 'system_a' OKAY [ 0.173s]
archive does not contain 'system_dlkm.img'
extracting system_ext.img (345 MB) to disk... took 1.538s
Invalid sparse file format at header magic
archive does not contain 'system_ext.sig'
Resizing 'system_ext_a' OKAY [ 0.010s]
Sending sparse 'system_ext_a' 1/2 (262132 KB) OKAY [ 6.850s]
Writing 'system_ext_a' OKAY [ 0.436s]
Sending sparse 'system_ext_a' 2/2 (90052 KB) OKAY [ 2.356s]
Writing 'system_ext_a' OKAY [ 0.166s]
extracting system_other.img (23 MB) to disk... took 0.130s
archive does not contain 'system.sig'
Resizing 'system_b' OKAY [ 0.007s]
Sending 'system_b' (24428 KB) OKAY [ 0.636s]
Writing 'system_b' OKAY [ 0.083s]
extracting vendor.img (489 MB) to disk... took 2.212s
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
Resizing 'vendor_a' OKAY [ 0.012s]
Sending sparse 'vendor_a' 1/2 (262116 KB) OKAY [ 6.895s]
Writing 'vendor_a' OKAY [ 0.414s]
Sending sparse 'vendor_a' 2/2 (237176 KB) OKAY [ 6.201s]
Writing 'vendor_a' OKAY [ 0.396s]
extracting vendor_dlkm.img (39 MB) to disk... took 0.128s
archive does not contain 'vendor_dlkm.sig'
Resizing 'vendor_dlkm_a' OKAY [ 0.010s]
Sending 'vendor_dlkm_a' (39996 KB) OKAY [ 1.028s]
Writing 'vendor_dlkm_a' OKAY [ 0.115s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 1.823s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.012s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Rebooting OKAY [ 0.001s]
Finished. Total time: 174.356s
Press any key to exit...
Click to expand...
Click to collapse
Bad Bimr said:
Updated the image on a Pixel 6a today and my eye caught this error. So I flased it again and again the same error? Is this normal? What is it? See log below.
Thanks
Click to expand...
Click to collapse
Yes, it's "normal". You can safely ignore it. I believe it has something to do with fastboot sending an image in an unexpected sparse format. Seriously, nothing to worry about.
It's funny that I flashed hundreds of times and never noticed it. Maybe I should be more attentive. LOL.
This link is a reasonable description of what a "sparse file' is: https://en.wikipedia.org/wiki/Sparse_file
The errors you highlight seem to indicate the downloaded file's contents doesn't match the file's internal description(s), also included in the download. (The so-called "meta data.")
Perhaps the download was incomplete or had an error. I'd re-fetching the material(s) and if there's a hash associated with the downloaded materials, ensure the hash matches. Sometimes files get mucked up during downloads... it happens.
I've not tried what you're doing myself and, as some are saying, perhaps it's normal, if still alarming. ;-)
I'm 99.9% sure I checked the hash file because I always do. But to be certain, I'll check it again just in case this time I didn't.
Bad Bimr said:
I'm 99.9% sure I checked the hash file because I always do. But to be certain, I'll check it again just in case this time I didn't.
Click to expand...
Click to collapse
You'll get that message every time. I do. No worries...
{
"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"
}
Hows it going guys,
im following this guide:
How to Install and Run 32-Bit Apps on Pixel 7 Pro
In this comprehensive tutorial, we will show you the detailed steps to install and run 32-bit apps on your Google Pixel 7/Pro.
www.droidwin.com
I am on the step where you flash the image.zip file you drag out of the stock ota image file and rename. I did this and then followed the next step, I run into this problem when I am executing the commands.
C:\Users\Gogop\Desktop\platform-tools>fastboot --skip-reboot -w update image.zip
--------------------------------------------
Bootloader Version...: cloudripper-1.0-9288096
Baseband Version.....: g5300g-220923-221028-B-9229469
Serial Number........: 28101FDH300AX6
--------------------------------------------
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.117s]
extracting boot.img (64 MB) to disk... took 0.145s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.088s]
Writing 'boot_b' OKAY [ 0.161s]
extracting init_boot.img (8 MB) to disk... took 0.016s
archive does not contain 'init_boot.sig'
Sending 'init_boot_b' (8192 KB) OKAY [ 0.257s]
Writing 'init_boot_b' OKAY [ 0.016s]
extracting dtbo.img (16 MB) to disk... took 0.036s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.515s]
Writing 'dtbo_b' OKAY [ 0.039s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.002s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_b' (1024 KB) OKAY [ 0.032s]
Writing 'pvmfw_b' OKAY [ 0.005s]
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.000s]
Writing 'vbmeta_b' OKAY [ 0.003s]
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.003s]
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.000s]
Writing 'vbmeta_vendor_b' OKAY [ 0.004s]
extracting vendor_boot.img (64 MB) to disk... took 0.143s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (65536 KB) OKAY [ 2.069s]
Writing 'vendor_boot_b' OKAY [ 0.162s]
extracting vendor_kernel_boot.img (64 MB) to disk... took 0.110s
archive does not contain 'vendor_kernel_boot.sig'
Sending 'vendor_kernel_boot_b' (65536 KB) OKAY [ 2.066s]
Writing 'vendor_kernel_boot_b' OKAY [ 0.155s]
extracting super_empty.img (0 MB) to disk... took 0.000s
extracting product.img (2778 MB) to disk... took 7.526s
extracting system.img (841 MB) to disk... took 2.387s
extracting system_dlkm.img (0 MB) to disk... took 0.000s
extracting system_ext.img (356 MB) to disk... took 1.017s
extracting system_other.img (24 MB) to disk... took 0.079s
extracting vendor.img (636 MB) to disk... took 1.678s
extracting vendor_dlkm.img (40 MB) to disk... took 0.081s
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
I have tried to just continue past this and not do anything else about it and then flash the patched init_boot but after successfully doing this I am still unable to install 32 bit apps. Please help.
androidoverapple1 said:
Hows it going guys,
im following this guide:
How to Install and Run 32-Bit Apps on Pixel 7 Pro
In this comprehensive tutorial, we will show you the detailed steps to install and run 32-bit apps on your Google Pixel 7/Pro.
www.droidwin.com
I am on the step where you flash the image.zip file you drag out of the stock ota image file and rename. I did this and then followed the next step, I run into this problem when I am executing the commands.
C:\Users\Gogop\Desktop\platform-tools>fastboot --skip-reboot -w update image.zip
--------------------------------------------
Bootloader Version...: cloudripper-1.0-9288096
Baseband Version.....: g5300g-220923-221028-B-9229469
Serial Number........: 28101FDH300AX6
--------------------------------------------
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.117s]
extracting boot.img (64 MB) to disk... took 0.145s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.088s]
Writing 'boot_b' OKAY [ 0.161s]
extracting init_boot.img (8 MB) to disk... took 0.016s
archive does not contain 'init_boot.sig'
Sending 'init_boot_b' (8192 KB) OKAY [ 0.257s]
Writing 'init_boot_b' OKAY [ 0.016s]
extracting dtbo.img (16 MB) to disk... took 0.036s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.515s]
Writing 'dtbo_b' OKAY [ 0.039s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.002s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_b' (1024 KB) OKAY [ 0.032s]
Writing 'pvmfw_b' OKAY [ 0.005s]
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.000s]
Writing 'vbmeta_b' OKAY [ 0.003s]
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.003s]
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.000s]
Writing 'vbmeta_vendor_b' OKAY [ 0.004s]
extracting vendor_boot.img (64 MB) to disk... took 0.143s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (65536 KB) OKAY [ 2.069s]
Writing 'vendor_boot_b' OKAY [ 0.162s]
extracting vendor_kernel_boot.img (64 MB) to disk... took 0.110s
archive does not contain 'vendor_kernel_boot.sig'
Sending 'vendor_kernel_boot_b' (65536 KB) OKAY [ 2.066s]
Writing 'vendor_kernel_boot_b' OKAY [ 0.155s]
extracting super_empty.img (0 MB) to disk... took 0.000s
extracting product.img (2778 MB) to disk... took 7.526s
extracting system.img (841 MB) to disk... took 2.387s
extracting system_dlkm.img (0 MB) to disk... took 0.000s
extracting system_ext.img (356 MB) to disk... took 1.017s
extracting system_other.img (24 MB) to disk... took 0.079s
extracting vendor.img (636 MB) to disk... took 1.678s
extracting vendor_dlkm.img (40 MB) to disk... took 0.081s
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
I have tried to just continue past this and not do anything else about it and then flash the patched init_boot but after successfully doing this I am still unable to install 32 bit apps. Please help.
Click to expand...
Click to collapse
1. Try using this guide.
2. Use Platform Tools v33.0.3 instead of v34.0.0 because the latter seems to skip fastbootd. This bug will cause the error you got.
Lughnasadh said:
1. Try using this guide.
2. Use Platform Tools v33.0.3 instead of v34.0.0 because the latter seems to skip fastbootd. This bug will cause the error you got.
Click to expand...
Click to collapse
I went with the reccomendation and im still not gaining access.
--------------------------------------------
Bootloader Version...: cloudripper-1.0-9288096
Baseband Version.....: g5300g-220923-221028-B-9229469
Serial Number........: 28101FDH300AX6
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.001s]
Checking 'version-baseband' OKAY [ 0.001s]
Setting current slot to 'b' OKAY [ 0.114s]
extracting boot.img (64 MB) to disk... took 0.165s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.068s]
Writing 'boot_b' OKAY [ 0.145s]
extracting init_boot.img (8 MB) to disk... took 0.024s
archive does not contain 'init_boot.sig'
Sending 'init_boot_b' (8192 KB) OKAY [ 0.260s]
Writing 'init_boot_b' OKAY [ 0.016s]
extracting dtbo.img (16 MB) to disk... took 0.030s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.519s]
Writing 'dtbo_b' OKAY [ 0.039s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.002s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_b' (1024 KB) OKAY [ 0.033s]
Writing 'pvmfw_b' OKAY [ 0.005s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (12 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.003s]
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.003s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor_b' OKAY [ 0.003s]
extracting vendor_boot.img (64 MB) to disk... took 0.178s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (65536 KB) OKAY [ 2.063s]
Writing 'vendor_boot_b' OKAY [ 0.151s]
extracting vendor_kernel_boot.img (64 MB) to disk... took 0.127s
archive does not contain 'vendor_kernel_boot.sig'
Sending 'vendor_kernel_boot_b' (65536 KB) OKAY [ 2.068s]
Writing 'vendor_kernel_boot_b' OKAY [ 0.154s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Sending 'super' (5 KB) OKAY [ 0.000s]
Updating super partition OKAY [ 1.037s]
Resizing 'product_b' OKAY [ 0.006s]
Resizing 'system_b' OKAY [ 0.005s]
Resizing 'system_dlkm_b' OKAY [ 0.003s]
Resizing 'system_ext_b' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.003s]
Resizing 'vendor_b' OKAY [ 0.005s]
Resizing 'vendor_dlkm_b' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.004s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (2778 MB) to disk... took 11.696s
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.010s]
Sending sparse 'product_b' 1/11 (262112 KB) OKAY [ 8.436s]
Writing 'product_b' OKAY [ 0.370s]
Sending sparse 'product_b' 2/11 (262124 KB) OKAY [ 8.416s]
Writing 'product_b' OKAY [ 0.364s]
Sending sparse 'product_b' 3/11 (262128 KB) OKAY [ 8.473s]
Writing 'product_b' OKAY [ 0.376s]
Sending sparse 'product_b' 4/11 (262120 KB) OKAY [ 8.442s]
Writing 'product_b' OKAY [ 0.407s]
Sending sparse 'product_b' 5/11 (262116 KB) OKAY [ 8.456s]
Writing 'product_b' OKAY [ 0.368s]
Sending sparse 'product_b' 6/11 (262128 KB) OKAY [ 8.503s]
Writing 'product_b' OKAY [ 0.411s]
Sending sparse 'product_b' 7/11 (262128 KB) OKAY [ 8.540s]
Writing 'product_b' OKAY [ 0.405s]
Sending sparse 'product_b' 8/11 (262124 KB) OKAY [ 8.509s]
Writing 'product_b' OKAY [ 0.409s]
Sending sparse 'product_b' 9/11 (262128 KB) OKAY [ 8.491s]
Writing 'product_b' OKAY [ 0.388s]
Sending sparse 'product_b' 10/11 (262116 KB) OKAY [ 8.565s]
Writing 'product_b' OKAY [ 0.395s]
Sending sparse 'product_b' 11/11 (215056 KB) OKAY [ 7.057s]
Writing 'product_b' OKAY [ 0.337s]
extracting system.img (841 MB) to disk... took 2.719s
archive does not contain 'system.sig'
Resizing 'system_b' OKAY [ 0.012s]
Sending sparse 'system_b' 1/4 (262116 KB) OKAY [ 8.561s]
Writing 'system_b' OKAY [ 0.383s]
Sending sparse 'system_b' 2/4 (262120 KB) OKAY [ 8.560s]
Writing 'system_b' OKAY [ 0.375s]
Sending sparse 'system_b' 3/4 (262140 KB) OKAY [ 8.576s]
Writing 'system_b' OKAY [ 0.377s]
Sending sparse 'system_b' 4/4 (71952 KB) OKAY [ 2.345s]
Writing 'system_b' OKAY [ 0.146s]
extracting system_dlkm.img (0 MB) to disk... took 0.001s
archive does not contain 'system_dlkm.sig'
Resizing 'system_dlkm_b' OKAY [ 0.006s]
Sending 'system_dlkm_b' (340 KB) OKAY [ 0.013s]
Writing 'system_dlkm_b' OKAY [ 0.040s]
extracting system_ext.img (356 MB) to disk... took 1.097s
archive does not contain 'system_ext.sig'
Resizing 'system_ext_b' OKAY [ 0.009s]
Sending sparse 'system_ext_b' 1/2 (262136 KB) OKAY [ 8.552s]
Writing 'system_ext_b' OKAY [ 0.397s]
Sending sparse 'system_ext_b' 2/2 (101724 KB) OKAY [ 3.335s]
Writing 'system_ext_b' OKAY [ 0.189s]
extracting system_other.img (24 MB) to disk... took 0.089s
archive does not contain 'system.sig'
Resizing 'system_a' OKAY [ 0.008s]
Sending 'system_a' (25220 KB) OKAY [ 0.832s]
Writing 'system_a' OKAY [ 0.096s]
extracting vendor.img (636 MB) to disk... took 2.468s
archive does not contain 'vendor.sig'
Resizing 'vendor_b' OKAY [ 0.013s]
Sending sparse 'vendor_b' 1/3 (262120 KB) OKAY [ 8.551s]
Writing 'vendor_b' OKAY [ 0.434s]
Sending sparse 'vendor_b' 2/3 (262140 KB) OKAY [ 8.498s]
Writing 'vendor_b' OKAY [ 0.409s]
Sending sparse 'vendor_b' 3/3 (124972 KB) OKAY [ 4.073s]
Writing 'vendor_b' OKAY [ 0.202s]
extracting vendor_dlkm.img (40 MB) to disk... took 0.094s
archive does not contain 'vendor_dlkm.sig'
Resizing 'vendor_dlkm_b' OKAY [ 0.010s]
Sending 'vendor_dlkm_b' (41116 KB) OKAY [ 1.332s]
Writing 'vendor_dlkm_b' OKAY [ 0.088s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 2.059s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.019s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 226.485s
C:\Users\Gogop\Desktop\platform-tools>fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.003s
C:\Users\Gogop\Desktop\platform-tools>fastboot devices
28101FDH300AX6 fastboot
C:\Users\Gogop\Desktop\platform-tools>fastboot flash init_boot C:\Users\Gogop\Desktop\magisk_patched_boot.img
Sending 'init_boot_b' (8192 KB) OKAY [ 0.262s]
Writing 'init_boot_b' OKAY [ 0.055s]
Finished. Total time: 0.346s
C:\Users\Gogop\Desktop\platform-tools>fastboot flash init_boot magisk_patched_boot.img
Sending 'init_boot_b' (8192 KB) OKAY [ 0.260s]
Writing 'init_boot_b' OKAY [ 0.073s]
Finished. Total time: 0.336s
C:\Users\Gogop\Desktop\platform-tools>fastboot flash C:\Users\Gogop\Desktop\magisk_patched_boot.img
unknown partition 'C:\Users\Gogop\Desktop\magisk_patched_boot.img'
fastboot: error: cannot determine image filename for 'C:\Users\Gogop\Desktop\magisk_patched_boot.img'
C:\Users\Gogop\Desktop\platform-tools>fastboot devices
28101FDH300AX6 fastboot
C:\Users\Gogop\Desktop\platform-tools>fastboot flash
fastboot: usage: expected argument
C:\Users\Gogop\Desktop\platform-tools>fastboot flash C:\Users\Gogop\Desktop\platform-tools\magisk_patched_boot.img
unknown partition 'C:\Users\Gogop\Desktop\platform-tools\magisk_patched_boot.img'
fastboot: error: cannot determine image filename for 'C:\Users\Gogop\Desktop\platform-tools\magisk_patched_boot.img'
C:\Users\Gogop\Desktop\platform-tools>fastboot flash init_boot C:\Users\Gogop\Desktop\platform-tools\magisk_patched_boot.img
Sending 'init_boot_b' (8192 KB) OKAY [ 0.271s]
Writing 'init_boot_b' OKAY [ 0.074s]
Finished. Total time: 0.347s
i tried changing how i flashed the init boot but it seems like its not patching the magisk delta patch. There were failures in there as well. Any ideas?
androidoverapple1 said:
I went with the reccomendation and im still not gaining access.
--------------------------------------------
Bootloader Version...: cloudripper-1.0-9288096
Baseband Version.....: g5300g-220923-221028-B-9229469
Serial Number........: 28101FDH300AX6
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.001s]
Checking 'version-baseband' OKAY [ 0.001s]
Setting current slot to 'b' OKAY [ 0.114s]
extracting boot.img (64 MB) to disk... took 0.165s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.068s]
Writing 'boot_b' OKAY [ 0.145s]
extracting init_boot.img (8 MB) to disk... took 0.024s
archive does not contain 'init_boot.sig'
Sending 'init_boot_b' (8192 KB) OKAY [ 0.260s]
Writing 'init_boot_b' OKAY [ 0.016s]
extracting dtbo.img (16 MB) to disk... took 0.030s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.519s]
Writing 'dtbo_b' OKAY [ 0.039s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.002s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_b' (1024 KB) OKAY [ 0.033s]
Writing 'pvmfw_b' OKAY [ 0.005s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (12 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.003s]
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.003s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor_b' OKAY [ 0.003s]
extracting vendor_boot.img (64 MB) to disk... took 0.178s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (65536 KB) OKAY [ 2.063s]
Writing 'vendor_boot_b' OKAY [ 0.151s]
extracting vendor_kernel_boot.img (64 MB) to disk... took 0.127s
archive does not contain 'vendor_kernel_boot.sig'
Sending 'vendor_kernel_boot_b' (65536 KB) OKAY [ 2.068s]
Writing 'vendor_kernel_boot_b' OKAY [ 0.154s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Sending 'super' (5 KB) OKAY [ 0.000s]
Updating super partition OKAY [ 1.037s]
Resizing 'product_b' OKAY [ 0.006s]
Resizing 'system_b' OKAY [ 0.005s]
Resizing 'system_dlkm_b' OKAY [ 0.003s]
Resizing 'system_ext_b' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.003s]
Resizing 'vendor_b' OKAY [ 0.005s]
Resizing 'vendor_dlkm_b' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.004s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (2778 MB) to disk... took 11.696s
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.010s]
Sending sparse 'product_b' 1/11 (262112 KB) OKAY [ 8.436s]
Writing 'product_b' OKAY [ 0.370s]
Sending sparse 'product_b' 2/11 (262124 KB) OKAY [ 8.416s]
Writing 'product_b' OKAY [ 0.364s]
Sending sparse 'product_b' 3/11 (262128 KB) OKAY [ 8.473s]
Writing 'product_b' OKAY [ 0.376s]
Sending sparse 'product_b' 4/11 (262120 KB) OKAY [ 8.442s]
Writing 'product_b' OKAY [ 0.407s]
Sending sparse 'product_b' 5/11 (262116 KB) OKAY [ 8.456s]
Writing 'product_b' OKAY [ 0.368s]
Sending sparse 'product_b' 6/11 (262128 KB) OKAY [ 8.503s]
Writing 'product_b' OKAY [ 0.411s]
Sending sparse 'product_b' 7/11 (262128 KB) OKAY [ 8.540s]
Writing 'product_b' OKAY [ 0.405s]
Sending sparse 'product_b' 8/11 (262124 KB) OKAY [ 8.509s]
Writing 'product_b' OKAY [ 0.409s]
Sending sparse 'product_b' 9/11 (262128 KB) OKAY [ 8.491s]
Writing 'product_b' OKAY [ 0.388s]
Sending sparse 'product_b' 10/11 (262116 KB) OKAY [ 8.565s]
Writing 'product_b' OKAY [ 0.395s]
Sending sparse 'product_b' 11/11 (215056 KB) OKAY [ 7.057s]
Writing 'product_b' OKAY [ 0.337s]
extracting system.img (841 MB) to disk... took 2.719s
archive does not contain 'system.sig'
Resizing 'system_b' OKAY [ 0.012s]
Sending sparse 'system_b' 1/4 (262116 KB) OKAY [ 8.561s]
Writing 'system_b' OKAY [ 0.383s]
Sending sparse 'system_b' 2/4 (262120 KB) OKAY [ 8.560s]
Writing 'system_b' OKAY [ 0.375s]
Sending sparse 'system_b' 3/4 (262140 KB) OKAY [ 8.576s]
Writing 'system_b' OKAY [ 0.377s]
Sending sparse 'system_b' 4/4 (71952 KB) OKAY [ 2.345s]
Writing 'system_b' OKAY [ 0.146s]
extracting system_dlkm.img (0 MB) to disk... took 0.001s
archive does not contain 'system_dlkm.sig'
Resizing 'system_dlkm_b' OKAY [ 0.006s]
Sending 'system_dlkm_b' (340 KB) OKAY [ 0.013s]
Writing 'system_dlkm_b' OKAY [ 0.040s]
extracting system_ext.img (356 MB) to disk... took 1.097s
archive does not contain 'system_ext.sig'
Resizing 'system_ext_b' OKAY [ 0.009s]
Sending sparse 'system_ext_b' 1/2 (262136 KB) OKAY [ 8.552s]
Writing 'system_ext_b' OKAY [ 0.397s]
Sending sparse 'system_ext_b' 2/2 (101724 KB) OKAY [ 3.335s]
Writing 'system_ext_b' OKAY [ 0.189s]
extracting system_other.img (24 MB) to disk... took 0.089s
archive does not contain 'system.sig'
Resizing 'system_a' OKAY [ 0.008s]
Sending 'system_a' (25220 KB) OKAY [ 0.832s]
Writing 'system_a' OKAY [ 0.096s]
extracting vendor.img (636 MB) to disk... took 2.468s
archive does not contain 'vendor.sig'
Resizing 'vendor_b' OKAY [ 0.013s]
Sending sparse 'vendor_b' 1/3 (262120 KB) OKAY [ 8.551s]
Writing 'vendor_b' OKAY [ 0.434s]
Sending sparse 'vendor_b' 2/3 (262140 KB) OKAY [ 8.498s]
Writing 'vendor_b' OKAY [ 0.409s]
Sending sparse 'vendor_b' 3/3 (124972 KB) OKAY [ 4.073s]
Writing 'vendor_b' OKAY [ 0.202s]
extracting vendor_dlkm.img (40 MB) to disk... took 0.094s
archive does not contain 'vendor_dlkm.sig'
Resizing 'vendor_dlkm_b' OKAY [ 0.010s]
Sending 'vendor_dlkm_b' (41116 KB) OKAY [ 1.332s]
Writing 'vendor_dlkm_b' OKAY [ 0.088s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 2.059s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.019s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 226.485s
C:\Users\Gogop\Desktop\platform-tools>fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.003s
C:\Users\Gogop\Desktop\platform-tools>fastboot devices
28101FDH300AX6 fastboot
C:\Users\Gogop\Desktop\platform-tools>fastboot flash init_boot C:\Users\Gogop\Desktop\magisk_patched_boot.img
Sending 'init_boot_b' (8192 KB) OKAY [ 0.262s]
Writing 'init_boot_b' OKAY [ 0.055s]
Finished. Total time: 0.346s
C:\Users\Gogop\Desktop\platform-tools>fastboot flash init_boot magisk_patched_boot.img
Sending 'init_boot_b' (8192 KB) OKAY [ 0.260s]
Writing 'init_boot_b' OKAY [ 0.073s]
Finished. Total time: 0.336s
C:\Users\Gogop\Desktop\platform-tools>fastboot flash C:\Users\Gogop\Desktop\magisk_patched_boot.img
unknown partition 'C:\Users\Gogop\Desktop\magisk_patched_boot.img'
fastboot: error: cannot determine image filename for 'C:\Users\Gogop\Desktop\magisk_patched_boot.img'
C:\Users\Gogop\Desktop\platform-tools>fastboot devices
28101FDH300AX6 fastboot
C:\Users\Gogop\Desktop\platform-tools>fastboot flash
fastboot: usage: expected argument
C:\Users\Gogop\Desktop\platform-tools>fastboot flash C:\Users\Gogop\Desktop\platform-tools\magisk_patched_boot.img
unknown partition 'C:\Users\Gogop\Desktop\platform-tools\magisk_patched_boot.img'
fastboot: error: cannot determine image filename for 'C:\Users\Gogop\Desktop\platform-tools\magisk_patched_boot.img'
C:\Users\Gogop\Desktop\platform-tools>fastboot flash init_boot C:\Users\Gogop\Desktop\platform-tools\magisk_patched_boot.img
Sending 'init_boot_b' (8192 KB) OKAY [ 0.271s]
Writing 'init_boot_b' OKAY [ 0.074s]
Finished. Total time: 0.347s
i tried changing how i flashed the init boot but it seems like its not patching the magisk delta patch. There were failures in there as well. Any ideas?
Click to expand...
Click to collapse
If you are trying to flash a patched init_boot.img, the command is:
Code:
fastboot flash init_boot <name of patched init_boot.img>
# 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.