So, my phone's kinda stuck right now. Decided to do a bit of a clean slate and just flash up from 8 to 9. Downloaded the latest factory image from google, updated the platform tools, and ran the flash-all.bat
And I get this:
Sending 'bootloader_a' (36336 KB) OKAY [ 0.829s]
Writing 'bootloader_a' OKAY [ 0.373s]
Finished. Total time: 1.213s
rebooting into bootloader OKAY [ 0.010s]
Finished. Total time: 0.012s
Sending 'radio_a' (60388 KB) OKAY [ 31.819s]
Writing 'radio_a' OKAY [ 0.569s]
Finished. Total time: 32.404s
rebooting into bootloader OKAY [ 0.008s]
Finished. Total time: 0.011s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: TMZ20k
Baseband Version.....: g8998-00253-1805232234
Serial Number........: <Removed>
--------------------------------------------
Checking product OKAY [ 0.004s]
Checking version-bootloader OKAY [ 0.002s]
Checking version-baseband OKAY [ 0.001s]
extracting boot.img (40 MB) to disk... took 0.164s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.030s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (2207 MB) to disk... took 11.705s
archive does not contain 'system.sig'
extracting system_other.img (322 MB) to disk... took 1.760s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.002s
archive does not contain 'vbmeta.sig'
extracting vendor.img (351 MB) to disk... took 1.914s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Sending 'boot_a' (40960 KB) OKAY [ 0.933s]
Writing 'boot_a' OKAY [ 0.376s]
Sending 'dtbo_a' (8192 KB) OKAY [ 0.190s]
Writing 'dtbo_a' OKAY [ 0.081s]
Sending sparse 'system_a' 1/5 (524284 KB) OKAY [ 12.344s]
Writing sparse 'system_a' 1/5 OKAY [ 2.452s]
Sending sparse 'system_a' 2/5 (524284 KB) OKAY [ 12.275s]
Writing sparse 'system_a' 2/5 OKAY [ 2.389s]
Sending sparse 'system_a' 3/5 (524284 KB) OKAY [ 12.322s]
Writing sparse 'system_a' 3/5 OKAY [ 2.444s]
Sending sparse 'system_a' 4/5 (521176 KB) OKAY [ 12.111s]
Writing sparse 'system_a' 4/5 OKAY [ 2.375s]
Sending sparse 'system_a' 5/5 (166784 KB) OKAY [ 3.961s]
Writing sparse 'system_a' 5/5 OKAY [ 0.768s]
Sending 'system_b' (330216 KB) OKAY [ 7.476s]
Writing 'system_b' OKAY [ 1.505s]
Sending 'vbmeta_a' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta_a' OKAY [ 0.019s]
Sending 'vendor_a' (360340 KB) FAILED (Write to device failed in Sendbuffer() (Unknown error))
Finished. Total time: 138.377s
If I want to try flashing again I need to restart the bootloader from the phone. And worse is that I can't actually boot my phone. It pops up the warning that it's corrupted, and if I continue anyway it just sits on the google screen.
So... any ideas for solutions? I've seen some suggestions through googling that mention trying using different usb cables and ports. Unfortunately this is the only C cable and port I have, so limited options for the moment. But since most of the other large files seemed to transfer ok, would that really do it? And until I can get hold of such a cable, is there anything else I can do to try and get my phone working in the meantime?
Thanks!
Edit: I've now also tried it using the September image as well as the October one. Exactly the same problem with exactly the same file. No idea what that means or if that info helps, but I guess it means the problem wasn't with a bad download or anything.
ivivaitylin said:
So, my phone's kinda stuck right now. Decided to do a bit of a clean slate and just flash up from 8 to 9. Downloaded the latest factory image from google, updated the platform tools, and ran the flash-all.bat
And I get this:
Sending 'bootloader_a' (36336 KB) OKAY [ 0.829s]
Writing 'bootloader_a' OKAY [ 0.373s]
Finished. Total time: 1.213s
rebooting into bootloader OKAY [ 0.010s]
Finished. Total time: 0.012s
Sending 'radio_a' (60388 KB) OKAY [ 31.819s]
Writing 'radio_a' OKAY [ 0.569s]
Finished. Total time: 32.404s
rebooting into bootloader OKAY [ 0.008s]
Finished. Total time: 0.011s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: TMZ20k
Baseband Version.....: g8998-00253-1805232234
Serial Number........: <Removed>
--------------------------------------------
Checking product OKAY [ 0.004s]
Checking version-bootloader OKAY [ 0.002s]
Checking version-baseband OKAY [ 0.001s]
extracting boot.img (40 MB) to disk... took 0.164s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.030s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (2207 MB) to disk... took 11.705s
archive does not contain 'system.sig'
extracting system_other.img (322 MB) to disk... took 1.760s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.002s
archive does not contain 'vbmeta.sig'
extracting vendor.img (351 MB) to disk... took 1.914s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Sending 'boot_a' (40960 KB) OKAY [ 0.933s]
Writing 'boot_a' OKAY [ 0.376s]
Sending 'dtbo_a' (8192 KB) OKAY [ 0.190s]
Writing 'dtbo_a' OKAY [ 0.081s]
Sending sparse 'system_a' 1/5 (524284 KB) OKAY [ 12.344s]
Writing sparse 'system_a' 1/5 OKAY [ 2.452s]
Sending sparse 'system_a' 2/5 (524284 KB) OKAY [ 12.275s]
Writing sparse 'system_a' 2/5 OKAY [ 2.389s]
Sending sparse 'system_a' 3/5 (524284 KB) OKAY [ 12.322s]
Writing sparse 'system_a' 3/5 OKAY [ 2.444s]
Sending sparse 'system_a' 4/5 (521176 KB) OKAY [ 12.111s]
Writing sparse 'system_a' 4/5 OKAY [ 2.375s]
Sending sparse 'system_a' 5/5 (166784 KB) OKAY [ 3.961s]
Writing sparse 'system_a' 5/5 OKAY [ 0.768s]
Sending 'system_b' (330216 KB) OKAY [ 7.476s]
Writing 'system_b' OKAY [ 1.505s]
Sending 'vbmeta_a' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta_a' OKAY [ 0.019s]
Sending 'vendor_a' (360340 KB) FAILED (Write to device failed in Sendbuffer() (Unknown error))
Finished. Total time: 138.377s
If I want to try flashing again I need to restart the bootloader from the phone. And worse is that I can't actually boot my phone. It pops up the warning that it's corrupted, and if I continue anyway it just sits on the google screen.
So... any ideas for solutions? I've seen some suggestions through googling that mention trying using different usb cables and ports. Unfortunately this is the only C cable and port I have, so limited options for the moment. But since most of the other large files seemed to transfer ok, would that really do it? And until I can get hold of such a cable, is there anything else I can do to try and get my phone working in the meantime?
Thanks!
Edit: I've now also tried it using the September image as well as the October one. Exactly the same problem with exactly the same file. No idea what that means or if that info helps, but I guess it means the problem wasn't with a bad download or anything.
Click to expand...
Click to collapse
Change cable and make sure latest version of adb n fastboot are being used
Sent from my Pixel 2 XL using Tapatalk
piyush7243 said:
Change cable and make sure latest version of adb n fastboot are being used
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Well, got some good news and some bad news. Good news, went and got a new cable, and it's flashed fine now.
Bad news, in my annoyance and after repeated downloads of the image to make sure it wasn't corrupt, I forgot to remove the -w from the flash-all.bat
Welp, at least the phone's working.
ivivaitylin said:
Well, got some good news and some bad news. Good news, went and got a new cable, and it's flashed fine now.
Bad news, in my annoyance and after repeated downloads of the image to make sure it wasn't corrupt, I forgot to remove the -w from the flash-all.bat
Welp, at least the phone's working.
Click to expand...
Click to collapse
And it's clean as a whistle now. A good flushing isn't bad from time to time. That is if you backed up your data before you started! :laugh:
I had the same problem, and I tried multiple cables: 2 USB C cables directly from Google, 1 USB C cable from Apple, and 2 different USB 3 to USB C cables. They all didn't work.
Then I had the hail mary idea to try doing this again on a Mac (I had been using a PC). And miraculously, it worked. But for anyone thinking about flashing their Pixel with the factory image, be careful and be ready for failure! I will never try anything like this again.
Related
I picked up my Pixel 2 XL yesterday. I set it up to check it out and everything worked fine on it. It is a google version and I haven't put my Verizon SIM in it just yet. I started off with unlocked the bootloader and bootloader_critical without any issues. I then want to upgrade from 8.0 to 8.1 by flashing the stock image. I flashed it using the flash-all.sh on a linux machine. The flash when just fine but now my device won't accept touch input. I am able to interact with it using a wireless mouse via the usb-c to usb adapter.
My question is, has anyone experienced this and what should I do to fix this issue?
I have tried flashing back to the most recent 8.0 using stock factory image on both a linux and windows machine. I haven also used the Android ToolKit with the most update to date version. I've looked around online and I didn't see someone else with this issue but if this has been posted before, I'm sorry for posting this again. I also want to say that I did post this over on reddit on /r/AndroidQuestions last night.
Have you downloaded the 8.1 factory image and just installed from scratch using the flash all?
CyberpodS2 said:
Have you downloaded the 8.1 factory image and just installed from scratch using the flash all?
Click to expand...
Click to collapse
Yeah, I just tried that. I downloaded the 8.1 image and flashed using the flash-all.bat. Below I have the output from the terminal.
Code:
E:\Downloads\taimen-opm1.171019.011-factory-2df1c1cb\taimen-opm1.171019.011>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (36344 KB)...
OKAY [ 0.769s]
writing 'bootloader_a'...
OKAY [ 0.230s]
finished. total time: 1.002s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 1.277s]
writing 'radio_a'...
OKAY [ 0.844s]
finished. total time: 2.123s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.160s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.023s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1936 MB) to disk... took 8.534s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 3.011s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took -0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (349 MB) to disk... took 1.823s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 29518843 4k blocks and 7380992 inodes
Filesystem UUID: 4b8c28b4-e04f-11e7-9be1-e19bdc4c5f9d
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: TMZ12a
Baseband Version.....: g8998-00164-1710262031
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot_a' (40960 KB)...
OKAY [ 0.865s]
writing 'boot_a'...
OKAY [ 0.554s]
sending 'dtbo_a' (8192 KB)...
OKAY [ 0.174s]
writing 'dtbo_a'...
OKAY [ 0.105s]
erasing 'system_a'...
OKAY [ 0.050s]
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 11.581s]
writing 'system_a' 1/4...
OKAY [ 2.212s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 11.559s]
writing 'system_a' 2/4...
OKAY [ 2.220s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 11.579s]
writing 'system_a' 3/4...
OKAY [ 2.212s]
sending sparse 'system_a' 4/4 (410112 KB)...
OKAY [ 9.067s]
writing 'system_a' 4/4...
OKAY [ 1.724s]
erasing 'system_b'...
OKAY [ 0.039s]
sending sparse 'system_b' 1/2 (524284 KB)...
OKAY [ 11.477s]
writing 'system_b' 1/2...
OKAY [ 2.207s]
sending sparse 'system_b' 2/2 (57588 KB)...
OKAY [ 1.262s]
writing 'system_b' 2/2...
OKAY [ 0.247s]
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.004s]
writing 'vbmeta_a'...
OKAY [ 0.004s]
erasing 'vendor_a'...
OKAY [ 0.017s]
sending 'vendor_a' (357904 KB)...
OKAY [ 7.623s]
writing 'vendor_a'...
OKAY [ 1.508s]
Setting current slot to 'a'...
OKAY [ 0.013s]
erasing 'userdata'...
OKAY [ 0.813s]
sending 'userdata' (5341 KB)...
OKAY [ 0.115s]
writing 'userdata'...
OKAY [ 0.046s]
rebooting...
finished. total time: 79.315s
Press any key to exit...
The phone will not boot now I have tried formatting vendor but still fails.
Sending 'bootloader_b' (36380 KB) OKAY [ 0.819s]
Writing 'bootloader_b' OKAY [ 0.389s]
Finished. Total time: 1.213s
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Sending 'radio_b' (60412 KB) OKAY [ 1.338s]
Writing 'radio_b' OKAY [ 0.575s]
Finished. Total time: 1.922s
rebooting into bootloader OKAY [ 0.004s]
Finished. Total time: 0.004s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: TMZ12g
Baseband Version.....: g8998-00202-1802061358
Serial Number........: 710KPAE0179280
--------------------------------------------
Checking product OKAY [ 0.003s]
Checking version-bootloader OKAY [ 0.002s]
Checking version-baseband OKAY [ 0.002s]
extracting boot.img (40 MB) to disk... took 0.212s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.031s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'recovery.img'
extracting system.img (1937 MB) to disk... took 11.356s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 3.965s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
extracting vendor.img (346 MB) to disk... took 2.332s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Sending 'boot_b' (40960 KB) OKAY [ 0.930s]
Writing 'boot_b' OKAY [ 0.360s]
Sending 'dtbo_b' (8192 KB) OKAY [ 0.200s]
Writing 'dtbo_b' OKAY [ 0.082s]
Sending sparse 'system_b' 1/4 (524284 KB) OKAY [ 12.101s]
Writing sparse 'system_b' 1/4 OKAY [ 6.493s]
Sending sparse 'system_b' 2/4 (524284 KB) OKAY [ 11.968s]
Writing sparse 'system_b' 2/4 OKAY [ 3.886s]
Sending sparse 'system_b' 3/4 (524284 KB) OKAY [ 11.869s]
Writing sparse 'system_b' 3/4 OKAY [ 2.911s]
Sending sparse 'system_b' 4/4 (411464 KB) OKAY [ 9.432s]
Writing sparse 'system_b' 4/4 OKAY [ 1.991s]
Sending sparse 'system_a' 1/2 (524284 KB) OKAY [ 11.871s]
Writing sparse 'system_a' 1/2 OKAY [ 2.475s]
Sending sparse 'system_a' 2/2 (57612 KB) OKAY [ 1.304s]
Writing sparse 'system_a' 2/2 OKAY [ 0.273s]
Sending 'vbmeta_b' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_b' OKAY [ 0.004s]
Sending 'vendor_b' (354932 KB) FAILED (data write failure (Unknown error))
Finished. Total time: 113.236s
Press any key to exit...
joeyddr said:
The phone will not boot now I have tried formatting vendor but still fails.
Sending 'bootloader_b' (36380 KB) OKAY [ 0.819s]
Writing 'bootloader_b' OKAY [ 0.389s]
Finished. Total time: 1.213s
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Sending 'radio_b' (60412 KB) OKAY [ 1.338s]
Writing 'radio_b' OKAY [ 0.575s]
Finished. Total time: 1.922s
rebooting into bootloader OKAY [ 0.004s]
Finished. Total time: 0.004s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: TMZ12g
Baseband Version.....: g8998-00202-1802061358
Serial Number........: 710KPAE0179280
--------------------------------------------
Checking product OKAY [ 0.003s]
Checking version-bootloader OKAY [ 0.002s]
Checking version-baseband OKAY [ 0.002s]
extracting boot.img (40 MB) to disk... took 0.212s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.031s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'recovery.img'
extracting system.img (1937 MB) to disk... took 11.356s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 3.965s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
extracting vendor.img (346 MB) to disk... took 2.332s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Sending 'boot_b' (40960 KB) OKAY [ 0.930s]
Writing 'boot_b' OKAY [ 0.360s]
Sending 'dtbo_b' (8192 KB) OKAY [ 0.200s]
Writing 'dtbo_b' OKAY [ 0.082s]
Sending sparse 'system_b' 1/4 (524284 KB) OKAY [ 12.101s]
Writing sparse 'system_b' 1/4 OKAY [ 6.493s]
Sending sparse 'system_b' 2/4 (524284 KB) OKAY [ 11.968s]
Writing sparse 'system_b' 2/4 OKAY [ 3.886s]
Sending sparse 'system_b' 3/4 (524284 KB) OKAY [ 11.869s]
Writing sparse 'system_b' 3/4 OKAY [ 2.911s]
Sending sparse 'system_b' 4/4 (411464 KB) OKAY [ 9.432s]
Writing sparse 'system_b' 4/4 OKAY [ 1.991s]
Sending sparse 'system_a' 1/2 (524284 KB) OKAY [ 11.871s]
Writing sparse 'system_a' 1/2 OKAY [ 2.475s]
Sending sparse 'system_a' 2/2 (57612 KB) OKAY [ 1.304s]
Writing sparse 'system_a' 2/2 OKAY [ 0.273s]
Sending 'vbmeta_b' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_b' OKAY [ 0.004s]
Sending 'vendor_b' (354932 KB) FAILED (data write failure (Unknown error))
Finished. Total time: 113.236s
Press any key to exit...
Click to expand...
Click to collapse
I would download the factory image again, reboot your pc and start over for starters :good:
joeyddr said:
The phone will not boot now I have tried formatting vendor but still fails.
Sending 'bootloader_b' (36380 KB) OKAY [ 0.819s]
Writing 'bootloader_b' OKAY [ 0.389s]
Finished. Total time: 1.213s
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Sending 'radio_b' (60412 KB) OKAY [ 1.338s]
Writing 'radio_b' OKAY [ 0.575s]
Finished. Total time: 1.922s
rebooting into bootloader OKAY [ 0.004s]
Finished. Total time: 0.004s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: TMZ12g
Baseband Version.....: g8998-00202-1802061358
Serial Number........: 710KPAE0179280
--------------------------------------------
Checking product OKAY [ 0.003s]
Checking version-bootloader OKAY [ 0.002s]
Checking version-baseband OKAY [ 0.002s]
extracting boot.img (40 MB) to disk... took 0.212s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.031s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'recovery.img'
extracting system.img (1937 MB) to disk... took 11.356s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 3.965s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
extracting vendor.img (346 MB) to disk... took 2.332s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Sending 'boot_b' (40960 KB) OKAY [ 0.930s]
Writing 'boot_b' OKAY [ 0.360s]
Sending 'dtbo_b' (8192 KB) OKAY [ 0.200s]
Writing 'dtbo_b' OKAY [ 0.082s]
Sending sparse 'system_b' 1/4 (524284 KB) OKAY [ 12.101s]
Writing sparse 'system_b' 1/4 OKAY [ 6.493s]
Sending sparse 'system_b' 2/4 (524284 KB) OKAY [ 11.968s]
Writing sparse 'system_b' 2/4 OKAY [ 3.886s]
Sending sparse 'system_b' 3/4 (524284 KB) OKAY [ 11.869s]
Writing sparse 'system_b' 3/4 OKAY [ 2.911s]
Sending sparse 'system_b' 4/4 (411464 KB) OKAY [ 9.432s]
Writing sparse 'system_b' 4/4 OKAY [ 1.991s]
Sending sparse 'system_a' 1/2 (524284 KB) OKAY [ 11.871s]
Writing sparse 'system_a' 1/2 OKAY [ 2.475s]
Sending sparse 'system_a' 2/2 (57612 KB) OKAY [ 1.304s]
Writing sparse 'system_a' 2/2 OKAY [ 0.273s]
Sending 'vbmeta_b' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_b' OKAY [ 0.004s]
Sending 'vendor_b' (354932 KB) FAILED (data write failure (Unknown error))
Finished. Total time: 113.236s
Press any key to exit...
Click to expand...
Click to collapse
Can you boot to TWRP? If so, try a factory reset in TWRP.Also, while in TWRP see if vendor is mounted. Is so, try to unmount it.
Got the same thing again after redownload..... on another note i went to my friends house and it worked there..... now i have to figure out why its doing it on both of my pc's
joeyddr said:
Got the same thing again after redownload..... on another note i went to my friends house and it worked there..... now i have to figure out why its doing it on both of my pc's
Click to expand...
Click to collapse
You using an older version of fastboot? Something very similar happened to me on my home PC (old fastboot) but worked fine on my work computer (new fastboot).
EvilDobe said:
You using an older version of fastboot? Something very similar happened to me on my home PC (old fastboot) but worked fine on my work computer (new fastboot).
Click to expand...
Click to collapse
Yes i downloaded the latest platform tools, and the same damn cable and platform tools worked on my friends pc... I'm kinda lost not as to why
Hi!
I tried flashing the March Factory image (9.0.0 (PQ2A.190305.002, Mar 2019)).
In adb:
fastboot devices
fastboot oem unlock - message on phone screen, volume up then power. Unlocked ok
flash-all
Devices reboots, but still boot loops. I also tried flashing each item separately (i recall once on my Nexus 6P this worked when flash-all didn't work).
fastboot flash boot <boot image file name>.img
fastboot flash bootloader <bootloader image file name>.img
fastboot reboot-bootloader
fastboot flash radio <radio image file name>.img
fastboot flash recovery <recovery file name>.img
fastboot flash system <system file name>.img
fastboot flash vendor <vendor file name>.img
fastboot reboot
Any ideas what I could try next?
EDIT: I somehow managed to get it to boot into recovery. I see I can wipe data/factory reset. I am a little hesitant to do this, as will this remove the ADB USB debugging ability and then lock me out of ADB?
SD Platform tools up to date?
Maybe a corrupt flash or file.
https://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
crackerjack1957 said:
SD Platform tools up to date?
Maybe a corrupt flash or file
Click to expand...
Click to collapse
Following instructions from there, and also trying a different cable. I have the same issue, it still bootloops.
PHP:
C:\Users\Obsidian>cd C:/platform-tools
C:\platform-tools>fastboot devices
HT6A30206491 fastboot
C:\platform-tools>flash-all
Sending 'bootloader_a' (32424 KB) OKAY [ 0.842s]
Writing 'bootloader_a' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 16.264s]
Finished. Total time: 17.268s
rebooting into bootloader OKAY [ 0.015s]
Finished. Total time: 0.015s
< waiting for any device >
Sending 'radio_a' (57140 KB) OKAY [ 1.793s]
Writing 'radio_a' OKAY [ 0.852s]
Finished. Total time: 2.791s
rebooting into bootloader OKAY [ 0.010s]
Finished. Total time: 0.011s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 8996-012001-1811131534
Baseband Version.....: 8996-130181-1811270246
Serial Number........: HT6A30206491
--------------------------------------------
Checking product OKAY [ 0.050s]
Checking version-bootloader OKAY [ 0.049s]
Checking version-baseband OKAY [ 0.049s]
extracting boot.img (30 MB) to disk... took 0.795s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (1953 MB) to disk... took 14.468s
archive does not contain 'system.sig'
extracting system_other.img (312 MB) to disk... took 1.951s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (259 MB) to disk... took 1.690s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 29939712 4k blocks and 7487488 inodes
Filesystem UUID: 370a14d6-4260-11e9-a75f-5fe718f1534e
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'boot_a' (31001 KB) OKAY [ 0.801s]
Writing 'boot_a' OKAY [ 0.603s]
Sending sparse 'system_a' 1/4 (524284 KB) OKAY [ 12.109s]
Writing sparse 'system_a' 1/4 OKAY [ 3.998s]
Sending sparse 'system_a' 2/4 (524284 KB) OKAY [ 11.960s]
Writing sparse 'system_a' 2/4 OKAY [ 3.952s]
Sending sparse 'system_a' 3/4 (524284 KB) OKAY [ 11.916s]
Writing sparse 'system_a' 3/4 OKAY [ 4.045s]
Sending sparse 'system_a' 4/4 (427564 KB) OKAY [ 9.706s]
Writing sparse 'system_a' 4/4 OKAY [ 3.348s]
Sending 'system_b' (319668 KB) OKAY [ 7.904s]
Writing 'system_b' OKAY [ 2.646s]
Sending 'vendor_a' (266192 KB) OKAY [ 6.558s]
Writing 'vendor_a' OKAY [ 2.295s]
Setting current slot to 'a' OKAY [ 0.406s]
Erasing 'userdata' OKAY [ 29.008s]
Sending 'userdata' (4672 KB) OKAY [ 0.196s]
Writing 'userdata' OKAY [ 0.206s]
Rebooting
Finished. Total time: 136.871s
Press any key to exit...
I assume you kept the (-w) in the flash-all so all data was wiped?
Have looked here for instructions......maybe try #5 and sideload if all else fails.
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866
Hello Users and Seniors of the forum
Hope that you all will be in the best of your health.
I am using a Google Pixel 2 XL and I am facing the following issues.
First of all I am using Mac so keep me post mac apps and related things.
1- While Using the phone sometimes apps crashing.
2- Sometimes it restart automatically
3- and finally when I restart the phone it say your phone is corrupted and may not working properly. I tried side load but it failed.
Kindly guide me step by step to resolve my Issue.
Thanks and Regards
grjamal said:
Hello Users and Seniors of the forum
Hope that you all will be in the best of your health.
I am using a Google Pixel 2 XL and I am facing the following issues.
First of all I am using Mac so keep me post mac apps and related things.
1- While Using the phone sometimes apps crashing.
2- Sometimes it restart automatically
3- and finally when I restart the phone it say your phone is corrupted and may not working properly. I tried side load but it failed.
Kindly guide me step by step to resolve my Issue.
Thanks and Regards
Click to expand...
Click to collapse
Is your phone bootloader unlocked? If so I would fastboot flash the latest image. You could try removing the -w from the script first so that you don't need to lose all your data, otherwise you may need a full wipe.
crixley said:
Is your phone bootloader unlocked? If so I would fastboot flash the latest image. You could try removing the -w from the script first so that you don't need to lose all your data, otherwise you may need a full wipe.
Click to expand...
Click to collapse
How do you take -w from the script sorry for noob question
SirFronts said:
How do you take -w from the script sorry for noob question
Click to expand...
Click to collapse
where is the script and you can say I am new so please could you write in details.
SirFronts said:
How do you take -w from the script sorry for noob question
Click to expand...
Click to collapse
Edit the flash-all.bat file with notepad or whatever you use on your pc. Toward the end of the script, you'll see the -w flag. Delete those two characters, then leave a single space between the remaining words. Save your edit, and done :good:
---------- Post added at 02:57 AM ---------- Previous post was at 02:55 AM ----------
grjamal said:
where is the script and you can say I am new so please could you write in details.
Click to expand...
Click to collapse
The script is the flash-all.bat file. You'll see it after you extract the factory image :good:
Badger50 said:
Edit the flash-all.bat file with notepad or whatever you use on your pc. Toward the end of the script, you'll see the -w flag. Delete those two characters, then leave a single space between the remaining words. Save your edit, and done :good:
---------- Post added at 02:57 AM ---------- Previous post was at 02:55 AM ----------
The script is the flash-all.bat file. You'll see it after you extract the factory image :good:
Click to expand...
Click to collapse
Thank you
SirFronts said:
Thank you
Click to expand...
Click to collapse
I didn't see the flash-all.bat file. I have Latest firmware and platform tools with adb commands
grjamal said:
I didn't see the flash-all.bat file. I have Latest firmware and platform tools with adb commands
Click to expand...
Click to collapse
Did you download the OTA, or the factory image from here? https://developers.google.com/android/images
The OTA doesn't have the flash-all.bat file.
Badger50 said:
Did you download the OTA, or the factory image from here? https://developers.google.com/android/images
The OTA doesn't have the flash-all.bat file.
Click to expand...
Click to collapse
let me check
I got it but can I do "radio-taimen-g8998-00012-1905270706" old version on the latest version.
For MAC Users they will change/edit flash-all.sh file
grjamal said:
I got it but can I do "radio-taimen-g8998-00012-1905270706" old version on the latest version.
Click to expand...
Click to collapse
You can fastboot radios anytime :good:
I am downloading the latest version. If I have any issue I will post here. Thanks for your support my seniors.
The following process done.
l$ ./flash-all.sh
Sending 'bootloader_a' (36352 KB) OKAY [ 0.950s]
Writing 'bootloader_a' OKAY [ 0.557s]
Finished. Total time: 1.513s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.001s
Sending 'radio_a' (60388 KB) OKAY [ 1.299s]
Writing 'radio_a' OKAY [ 0.409s]
Finished. Total time: 1.712s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.001s
--------------------------------------------
Bootloader Version...: TMZ30k
Baseband Version.....: g8998-00017
Serial Number........: 801KP
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.001s]
Checking 'version-baseband' OKAY [ 0.001s]
Setting current slot to 'a' OKAY [ 0.008s]
extracting boot.img (40 MB) to disk... took 0.317s
archive does not contain 'boot.sig'
Sending 'boot_a' (40960 KB) OKAY [ 0.875s]
Writing 'boot_a' OKAY [ 0.251s]
extracting dtbo.img (8 MB) to disk... took 0.037s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.175s]
Writing 'dtbo_a' OKAY [ 0.049s]
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.001s]
Writing 'vbmeta_a' OKAY [ 0.003s]
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 (2392 MB) to disk... took 21.359s
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/5 (524284 KB) OKAY [ 14.086s]
Writing 'system_a' OKAY [ 3.286s]
Sending sparse 'system_a' 2/5 (524284 KB) OKAY [ 14.100s]
Writing 'system_a' OKAY [ 3.274s]
Sending sparse 'system_a' 3/5 (524284 KB) OKAY [ 14.049s]
Writing 'system_a' OKAY [ 3.272s]
Sending sparse 'system_a' 4/5 (524284 KB) OKAY [ 13.949s]
Writing 'system_a' OKAY [ 3.264s]
Sending sparse 'system_a' 5/5 (352908 KB) OKAY [ 9.325s]
Writing 'system_a' OKAY [ 2.214s]
archive does not contain 'system_ext.img'
extracting system_other.img (306 MB) to disk... took 2.778s
archive does not contain 'system.sig'
Sending 'system_b' (313536 KB) OKAY [ 6.986s]
Writing 'system_b' OKAY [ 1.993s]
extracting vendor.img (340 MB) to disk... took 3.217s
archive does not contain 'vendor.sig'
Sending 'vendor_a' (349148 KB) OKAY [ 8.615s]
Writing 'vendor_a' OKAY [ 2.178s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 2.655s]
mke2fs 1.45.4 (23-Sep-2019)
Creating filesystem with 13902843 4k blocks and 3481600 inodes
Filesystem UUID: b9208eba-4966-4866-899e-623a9f9abe48
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4400 KB) OKAY [ 0.094s]
Writing 'userdata' OKAY [ 0.068s]
Rebooting OKAY [ 0.000s]
Finished. Total time: 132.938s
grjamal said:
The following process done.
l$ ./flash-all.sh
Sending 'bootloader_a' (36352 KB) OKAY [ 0.950s]
Writing 'bootloader_a' OKAY [ 0.557s]
Finished. Total time: 1.513s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.001s
Sending 'radio_a' (60388 KB) OKAY [ 1.299s]
Writing 'radio_a' OKAY [ 0.409s]
Finished. Total time: 1.712s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.001s
--------------------------------------------
Bootloader Version...: TMZ30k
Baseband Version.....: g8998-00017-1910041814
Serial Number........: 801KPBF1518925
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.001s]
Checking 'version-baseband' OKAY [ 0.001s]
Setting current slot to 'a' OKAY [ 0.008s]
extracting boot.img (40 MB) to disk... took 0.317s
archive does not contain 'boot.sig'
Sending 'boot_a' (40960 KB) OKAY [ 0.875s]
Writing 'boot_a' OKAY [ 0.251s]
extracting dtbo.img (8 MB) to disk... took 0.037s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.175s]
Writing 'dtbo_a' OKAY [ 0.049s]
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.001s]
Writing 'vbmeta_a' OKAY [ 0.003s]
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 (2392 MB) to disk... took 21.359s
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/5 (524284 KB) OKAY [ 14.086s]
Writing 'system_a' OKAY [ 3.286s]
Sending sparse 'system_a' 2/5 (524284 KB) OKAY [ 14.100s]
Writing 'system_a' OKAY [ 3.274s]
Sending sparse 'system_a' 3/5 (524284 KB) OKAY [ 14.049s]
Writing 'system_a' OKAY [ 3.272s]
Sending sparse 'system_a' 4/5 (524284 KB) OKAY [ 13.949s]
Writing 'system_a' OKAY [ 3.264s]
Sending sparse 'system_a' 5/5 (352908 KB) OKAY [ 9.325s]
Writing 'system_a' OKAY [ 2.214s]
archive does not contain 'system_ext.img'
extracting system_other.img (306 MB) to disk... took 2.778s
archive does not contain 'system.sig'
Sending 'system_b' (313536 KB) OKAY [ 6.986s]
Writing 'system_b' OKAY [ 1.993s]
extracting vendor.img (340 MB) to disk... took 3.217s
archive does not contain 'vendor.sig'
Sending 'vendor_a' (349148 KB) OKAY [ 8.615s]
Writing 'vendor_a' OKAY [ 2.178s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 2.655s]
mke2fs 1.45.4 (23-Sep-2019)
Creating filesystem with 13902843 4k blocks and 3481600 inodes
Filesystem UUID: b9208eba-4966-4866-899e-623a9f9abe48
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4400 KB) OKAY [ 0.094s]
Writing 'userdata' OKAY [ 0.068s]
Rebooting OKAY [ 0.000s]
Finished. Total time: 132.938s
Click to expand...
Click to collapse
Congrats........I guess?
Now updates are in progress lets hope it will not repeat the issues again.
grjamal said:
Now updates are in progress lets hope it will not repeat the issues again.
Click to expand...
Click to collapse
update:
The phone restart after 5 hrs automatically while I was using it.
grjamal said:
update:
The phone restart after 5 hrs automatically while I was using it.
Click to expand...
Click to collapse
Random reboots can happen for no apparent reason at times. Having said that, it could be an app, magisk module, kernel or a behind the scenes google system update. I would just let your device run through a couple of charge cycles to see if the problem persists :good:
Badger50 said:
Random reboots can happen for no apparent reason at times. Having said that, it could be an app, magisk module, kernel or a behind the scenes google system update. I would just let your device run through a couple of charge cycles to see if the problem persists :good:
Click to expand...
Click to collapse
today I got the same issue, I mean your phone is corrupted and may not working properly.
what to do know? need your suggessions
grjamal said:
today I got the same issue, I mean your phone is corrupted and may not working properly.
what to do know? need your suggessions
Click to expand...
Click to collapse
Fastboot the factory image again to your inactive slot without the -w first. Make sure to disable any magisk modules, themes, and set screen lock to swipe before you begin. If that doesn't help, you may have to factory reset.
Hello,
I was trying to flash the factory image via fastboot and I am getting a failed message in the part where it says "sending product". I have pasted the last part of the information from the CMD prompt below. Now I cannot boot into anything. I was trying to restore the same factory image that the phone was already on which was Android 10 005 update. Bootloader is unlocked. Phone had Magisk Root before I tried to do this. I tried switching to slot B and still same error. I can't seem to find anything on google about this error.
Anyone know what I can do? I need to get the phone back up and running, I don't care about losing any data.
--------------------------------------------
Bootloader Version...: b1c1-0.2-6085603
Baseband Version.....: g845-00096-200114-B-6134206
Serial Number........: 91PY17NNE
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.057s]
Checking 'version-bootloader' OKAY [ 0.058s]
Checking 'version-baseband' OKAY [ 0.057s]
Setting current slot to 'a' OKAY [ 0.068s]
extracting boot.img (64 MB) to disk... took 0.237s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.332s]
Writing 'boot_a' OKAY [ 0.364s]
extracting dtbo.img (8 MB) to disk... took 0.021s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.129s]
Writing 'dtbo_a' OKAY [ 0.100s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (4 KB) OKAY [ 0.112s]
Writing 'vbmeta_a' OKAY [ 0.060s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.057s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.006s]
Deleting 'system_b' OKAY [ 0.005s]
Deleting 'vendor_b' OKAY [ 0.005s]
Resizing 'product_a' OKAY [ 0.005s]
Resizing 'system_a' OKAY [ 0.006s]
Resizing 'vendor_a' OKAY [ 0.006s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1980 MB) to disk... took 12.201s
archive does not contain 'product.sig'
Sending 'product' (2027860 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
sharky17 said:
Hello,
I was trying to flash the factory image via fastboot and I am getting a failed message in the part where it says "sending product". I have pasted the last part of the information from the CMD prompt below. Now I cannot boot into anything. I was trying to restore the same factory image that the phone was already on which was Android 10 005 update. Bootloader is unlocked. Phone had Magisk Root before I tried to do this. I tried switching to slot B and still same error. I can't seem to find anything on google about this error.
Anyone know what I can do? I need to get the phone back up and running, I don't care about losing any data.
--------------------------------------------
Bootloader Version...: b1c1-0.2-6085603
Baseband Version.....: g845-00096-200114-B-6134206
Serial Number........: 91PY17NNE
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.057s]
Checking 'version-bootloader' OKAY [ 0.058s]
Checking 'version-baseband' OKAY [ 0.057s]
Setting current slot to 'a' OKAY [ 0.068s]
extracting boot.img (64 MB) to disk... took 0.237s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.332s]
Writing 'boot_a' OKAY [ 0.364s]
extracting dtbo.img (8 MB) to disk... took 0.021s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.129s]
Writing 'dtbo_a' OKAY [ 0.100s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (4 KB) OKAY [ 0.112s]
Writing 'vbmeta_a' OKAY [ 0.060s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.057s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.006s]
Deleting 'system_b' OKAY [ 0.005s]
Deleting 'vendor_b' OKAY [ 0.005s]
Resizing 'product_a' OKAY [ 0.005s]
Resizing 'system_a' OKAY [ 0.006s]
Resizing 'vendor_a' OKAY [ 0.006s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1980 MB) to disk... took 12.201s
archive does not contain 'product.sig'
Sending 'product' (2027860 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Click to expand...
Click to collapse
Normally, it is nothing more than a dodgy cable. Try using a new A>C cable and a different port. To get yourself up and running immediately, when the error happens (you are in fastbootd), keep your command prompt or terminal up and go to recovery from fastbootd. Download the OTA, and from fastbootd>recovery start an ADB sideload of the downloaded OTA file.
sharky17 said:
Hello,
I was trying to flash the factory image via fastboot and I am getting a failed message in the part where it says "sending product". I have pasted the last part of the information from the CMD prompt below. Now I cannot boot into anything. I was trying to restore the same factory image that the phone was already on which was Android 10 005 update. Bootloader is unlocked. Phone had Magisk Root before I tried to do this. I tried switching to slot B and still same error. I can't seem to find anything on google about this error.
Anyone know what I can do? I need to get the phone back up and running, I don't care about losing any data.
--------------------------------------------
Bootloader Version...: b1c1-0.2-6085603
Baseband Version.....: g845-00096-200114-B-6134206
Serial Number........: 91PY17NNE
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.057s]
Checking 'version-bootloader' OKAY [ 0.058s]
Checking 'version-baseband' OKAY [ 0.057s]
Setting current slot to 'a' OKAY [ 0.068s]
extracting boot.img (64 MB) to disk... took 0.237s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.332s]
Writing 'boot_a' OKAY [ 0.364s]
extracting dtbo.img (8 MB) to disk... took 0.021s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.129s]
Writing 'dtbo_a' OKAY [ 0.100s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (4 KB) OKAY [ 0.112s]
Writing 'vbmeta_a' OKAY [ 0.060s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.057s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.006s]
Deleting 'system_b' OKAY [ 0.005s]
Deleting 'vendor_b' OKAY [ 0.005s]
Resizing 'product_a' OKAY [ 0.005s]
Resizing 'system_a' OKAY [ 0.006s]
Resizing 'vendor_a' OKAY [ 0.006s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1980 MB) to disk... took 12.201s
archive does not contain 'product.sig'
Sending 'product' (2027860 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Click to expand...
Click to collapse
The exact same thing has happened to me BUT if I kept repeating the process it would finally work. Try flashing 3 or 4 more times. This has happened to me the last 2 or three updates I tried to flash. Don't think it was the cable in my case because I tried different ones. I just keep trying and finally it'll work.
Same experience as @sliding_billy, its usually a cable issue or port issue, assuming your download isnt corrupted.
Daisymae said:
The exact same thing has happened to me BUT if I kept repeating the process it would finally work. Try flashing 3 or 4 more times. This has happened to me the last 2 or three updates I tried to flash. Don't think it was the cable in my case because I tried different ones. I just keep trying and finally it'll work.
Click to expand...
Click to collapse
I originally tried a few times before I posted this. But today I came back and tried again and it worked . SMH, that is weird. Thanks!!!