Related
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
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.
Hi everyone, I am facing a bootloop problem with my Pixel 2 XL with Android 10 (Build 190711.020) and unlocked bootloader
THE PROBLEM
When I turn the phone on it boots until the Google splash screen then the phone turns off and on again, the issue also occurs when I try to boot to recovery mode or when I plug the phone to a charger or USB. The only thing I can boot fine to is the Bootloader
WHAT I DID PRIOR
A couple of hours ago the phone was not rooted and was working fine and I did the following
1. Rooted the phone with Magisk 19.4 beta,
2. Enabled Gmail dark mode by editing flags with solid explorer
3. Reboot the phone
4. Used it for sometimes
5. Boot into bootloader and flashed boot.img to unroot
6. Boot the phone and used it fine for hours
7. I went to settings and enabled forced dark in developer options
8. Reboot the phone and the bootloops begins
WHAT I HAVE TRIED
After the hone started to bootloop did the following
1. I flashed Android 10 factory image >> Still bootloops
2. Formated userdata >> Still bootloopps
3. Used [TOOL] Deuces Bootloop-Recovery & Flashing Script v5.0 >> Still bootloop
4. Change to boot slot a and flash factory image, change to boot slot b and flash factory image >> Still bootloop
Does anyone have any insight on how to solve this problem?*
Thanks
NingaR said:
Hi everyone, I am facing a bootloop problem with my Pixel 2 XL with Android 10 (Build 190711.020) and unlocked bootloader
THE PROBLEM
When I turn the phone on it boots until the Google splash screen then the phone turns off and on again, the issue also occurs when I try to boot to recovery mode or when I plug the phone to a charger or USB. The only thing I can boot fine to is the Bootloader
WHAT I DID PRIOR
A couple of hours ago the phone was not rooted and was working fine and I did the following
1. Rooted the phone with Magisk 19.4 beta,
2. Enabled Gmail dark mode by editing flags with solid explorer
3. Reboot the phone
4. Used it for sometimes
5. Boot into bootloader and flashed boot.img to unroot
6. Boot the phone and used it fine for hours
7. I went to settings and enabled forced dark in developer options
8. Reboot the phone and the bootloops begins
WHAT I HAVE TRIED
After the hone started to bootloop did the following
1. I flashed Android 10 factory image >> Still bootloops
2. Formated userdata >> Still bootloopps
3. Used [TOOL] Deuces Bootloop-Recovery & Flashing Script v5.0 >> Still bootloop
4. Change to boot slot a and flash factory image, change to boot slot b and flash factory image >> Still bootloop
Does anyone have any insight on how to solve this problem?*
Thanks
Click to expand...
Click to collapse
What is the output/log for when you run the flash-all?
Also, confirm you have the most up-to-date platform-tools as well as using a USB-A to USB-A (avoid USB-C as much as possible, at least with taimen) cord and various different ports.
I'm thinking, instead of flashing the boot.img, you should've just "Uninstalled" within Magisk -- essentially restores the stock boot.img, but with the 2 different slots, it may have some other safeguards or something. But, in any case, loading flash-all and/or deuce's script should've/would've resolved anything that went wrong anyways...
Are you sure you didn't accidentally flash/restore using Pie instead of Q/10?
If nothing else after answering these inquiries, I will walk you through using fastboot commands within bootloader mode to manually format the boot and system partitions....
simplepinoi177 said:
What is the output/log for when you run the flash-all?
Click to expand...
Click to collapse
Here is the output I have attached a .txt file too
Code:
PS C:\Users\Ninga\Desktop\taimen-qp1a.190711.020> .\flash-all.bat
Sending 'bootloader_b' (36352 KB) OKAY [ 0.799s]
Writing 'bootloader_b' OKAY [ 0.277s]
Finished. Total time: 1.242s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.007s
Sending 'radio_b' (60388 KB) OKAY [ 1.339s]
Writing 'radio_b' OKAY [ 0.820s]
Finished. Total time: 2.467s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.005s
--------------------------------------------
Bootloader Version...: TMZ30h
Baseband Version.....: g8998-00012-1905270706
Serial Number........: 711KPRW0625214
--------------------------------------------
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 'b' OKAY [ 0.009s]
extracting boot.img (40 MB) to disk... took 0.264s
archive does not contain 'boot.sig'
Sending 'boot_b' (40960 KB) OKAY [ 0.901s]
Writing 'boot_b' OKAY [ 0.538s]
extracting dtbo.img (8 MB) to disk... took 0.033s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.181s]
Writing 'dtbo_b' OKAY [ 0.104s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_b' OKAY [ 0.003s]
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 (2374 MB) to disk... took 43.496s
archive does not contain 'system.sig'
Sending sparse 'system_b' 1/5 (524284 KB) OKAY [ 12.074s]
Writing 'system_b' OKAY [ 2.236s]
Sending sparse 'system_b' 2/5 (524284 KB) OKAY [ 12.060s]
Writing 'system_b' OKAY [ 2.234s]
Sending sparse 'system_b' 3/5 (524284 KB) OKAY [ 12.096s]
Writing 'system_b' OKAY [ 2.223s]
Sending sparse 'system_b' 4/5 (524284 KB) OKAY [ 12.006s]
Writing 'system_b' OKAY [ 2.237s]
Sending sparse 'system_b' 5/5 (334556 KB) OKAY [ 7.730s]
Writing 'system_b' OKAY [ 1.409s]
archive does not contain 'system_ext.img'
extracting system_other.img (304 MB) to disk... took 5.215s
archive does not contain 'system.sig'
Sending 'system_a' (311784 KB) OKAY [ 6.870s]
Writing 'system_a' OKAY [ 1.312s]
extracting vendor.img (340 MB) to disk... took 4.238s
archive does not contain 'vendor.sig'
Sending 'vendor_b' (348532 KB) OKAY [ 7.695s]
Writing 'vendor_b' OKAY [ 1.482s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 0.620s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 29518843 4k blocks and 7380992 inodes
Filesystem UUID: 36d24c48-e00a-11e9-8d7d-0f0cf6c3abaa
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 'userdata' (4672 KB) OKAY [ 0.103s]
Writing 'userdata' OKAY [ 0.035s]
Rebooting OKAY [ 0.000s]
Finished. Total time: 804.680s
Press any key to exit...
Also, confirm you have the most up-to-date platform-tools as well as using a USB-A to USB-A (avoid USB-C as much as possible, at least with taimen) cord and various different ports.
Click to expand...
Click to collapse
Yes I have up-to-date platform-tools and I am using USB-A to USB-C (I have been using this cable to update monthly)
I'm thinking, instead of flashing the boot.img, you should've just "Uninstalled" within Magisk -- essentially restores the stock boot.img, but with the 2 different slots, it may have some other safeguards or something. But, in any case, loading flash-all and/or deuce's script should've/would've resolved anything that went wrong anyways....
Are you sure you didn't accidentally flash/restore using Pie instead of Q/10?
Click to expand...
Click to collapse
Yes, I should just have just uninstalled magisk by using the uninstaller zip but I wanted to remove TWRP too and No I did not flash Pie just the same Android 10 build I cleaned flashed when I was updating to Android 10
If nothing else after answering these inquiries, I will walk you through using fastboot commands within bootloader mode to manually format the boot and system partitions....
Click to expand...
Click to collapse
Thank you so much for helping sir.
NingaR said:
Here is the output I have attached a .txt file too
Code:
PS C:\Users\Ninga\Desktop\taimen-qp1a.190711.020> .\flash-all.bat
Sending 'bootloader_b' (36352 KB) OKAY [ 0.799s]
Writing 'bootloader_b' OKAY [ 0.277s]
Finished. Total time: 1.242s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.007s
Sending 'radio_b' (60388 KB) OKAY [ 1.339s]
Writing 'radio_b' OKAY [ 0.820s]
Finished. Total time: 2.467s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.005s
--------------------------------------------
Bootloader Version...: TMZ30h
Baseband Version.....: g8998-00012-1905270706
Serial Number........: 711KPRW0625214
--------------------------------------------
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 'b' OKAY [ 0.009s]
extracting boot.img (40 MB) to disk... took 0.264s
archive does not contain 'boot.sig'
Sending 'boot_b' (40960 KB) OKAY [ 0.901s]
Writing 'boot_b' OKAY [ 0.538s]
extracting dtbo.img (8 MB) to disk... took 0.033s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.181s]
Writing 'dtbo_b' OKAY [ 0.104s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_b' OKAY [ 0.003s]
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 (2374 MB) to disk... took 43.496s
archive does not contain 'system.sig'
Sending sparse 'system_b' 1/5 (524284 KB) OKAY [ 12.074s]
Writing 'system_b' OKAY [ 2.236s]
Sending sparse 'system_b' 2/5 (524284 KB) OKAY [ 12.060s]
Writing 'system_b' OKAY [ 2.234s]
Sending sparse 'system_b' 3/5 (524284 KB) OKAY [ 12.096s]
Writing 'system_b' OKAY [ 2.223s]
Sending sparse 'system_b' 4/5 (524284 KB) OKAY [ 12.006s]
Writing 'system_b' OKAY [ 2.237s]
Sending sparse 'system_b' 5/5 (334556 KB) OKAY [ 7.730s]
Writing 'system_b' OKAY [ 1.409s]
archive does not contain 'system_ext.img'
extracting system_other.img (304 MB) to disk... took 5.215s
archive does not contain 'system.sig'
Sending 'system_a' (311784 KB) OKAY [ 6.870s]
Writing 'system_a' OKAY [ 1.312s]
extracting vendor.img (340 MB) to disk... took 4.238s
archive does not contain 'vendor.sig'
Sending 'vendor_b' (348532 KB) OKAY [ 7.695s]
Writing 'vendor_b' OKAY [ 1.482s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 0.620s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 29518843 4k blocks and 7380992 inodes
Filesystem UUID: 36d24c48-e00a-11e9-8d7d-0f0cf6c3abaa
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 'userdata' (4672 KB) OKAY [ 0.103s]
Writing 'userdata' OKAY [ 0.035s]
Rebooting OKAY [ 0.000s]
Finished. Total time: 804.680s
Press any key to exit...
Yes I have up-to-date platform-tools and I am using USB-A to USB-C (I have been using this cable to update monthly)
Yes, I should just have just uninstalled magisk by using the uninstaller zip but I wanted to remove TWRP too and No I did not flash Pie just the same Android 10 build I cleaned flashed when I was updating to Android 10
Thank you so much for helping sir.
Click to expand...
Click to collapse
I haven't read the whole post, but I wanted to come on here real quick after a cursory look and suggest something...
There are some things that changed with the Full Factory images for Q/10 -- namely where the flash-all resides -- and I'm completely unsure if things have changed, but AFAIK, for Linux, you are supposed to use the flash-all.sh, NOT the flash-all.bat. I'm sure it's a subtle but significant difference...!
And i'll be sure to read and consider the rest later tonight...
And I am very happy to help!
simplepinoi177 said:
I haven't read the whole post, but I wanted to come on here real quick after a cursory look and suggest something...
There are some things that changed with the Full Factory images for Q/10 -- namely where the flash-all resides -- and I'm completely unsure if things have changed, but AFAIK, for Linux, you are supposed to use the flash-all.sh, NOT the flash-all.bat. I'm sure it's a subtle but significant difference...!
And i'll be sure to read and consider the rest later tonight...
And I am very happy to help!
Click to expand...
Click to collapse
I am using windows, I just run .\flash-all.bat on PowerShell as I was unable to copy the output code in CMD but I get the same output from CMD and PowerShell.
NingaR said:
I am using windows, I just run .\flash-all.bat on PowerShell as I was unable to copy the output code in CMD but I get the same output from CMD and PowerShell.
Click to expand...
Click to collapse
So, actually, I strongly suggest using CMD versus PowerShell. If anything, you make sure to run it “as Administrator” (either by right-clicking, or searching Command Prompt and right-clicking) and then directing to and running the flash-all.bat. And to keep the window from closing, you edit the file – in the same way you would to remove the “-w” – by right-clicking and selecting “Edit”. At the very end, remove/erase the word “exit”; this should keep it from closing out the window. You should do this from here on out. Also, you probably don’t have to do the “./” thing, but I’m not sure if it matters at all or not.
At this point, I (personally) would go through the process of manually formatting the system, boot, dtbo, and data partitions using fastboot commands in the bootloader; but I’m worried it might affect the bootloader in some inadvertent way and completely brick the device – which is why I’d only do it myself with only myself to blame. I super really bricked one device already by accidentally formatting the bootloader partition, then before reflashing/re-installing the stock bootloader, I accidentally rebooted and I couldn’t even recover anything because there was no Bootloader Mode to do it from. So what I suggest to you is this…
I suggest you download TWRP image file and temporarily boot into that custom recovery to “wipe” and format everything. You can do this by downloading and moving the TWRP .img file to the platform-tools folder that has the adb and fastboot executables/files. Then run the command “fastboot boot twrp.img” (replace “twrp” with the actual file name). In there, I would go to the “Wipe” section and wipe the system, data, and internal storage partition – If there was an option to wipe the boot partition I would suggest that; but we’ll get to that if need be – if you go into the “Advanced Wipe” section. While there, you might even try the “Repair or Change File System”. After all of this, you should reboot back into the bootloader and load up a CMD after clicking “Run as Administrator” and run the flash-all.bat again.
If it still is struggling afterwards, you might want to try obtaining the stock boot.img and dtbo.img -- you should be able to find it in the Full Factory image .zip file; you just have to delve deep enough through the multiple .zips -- and manually flashing it to the device; command would be “fastboot flash boot boot.img” & “fastboot flash dtbo dtbo.img” – remember you will have to move the .img files to the same platform-tools folder as fastboot and adb .exe files.
Some thoughts; I really wonder if it is the new Q/10 OS version or something and/or the new way Google has assembled the Full Factory images, but most of the time running the flash-all with the “-w” intact resolves any boot and system issues! None of these steps are usually necessary further than that. I was suspecting something was happening in the flashing, but your log shows that everything is flashing and installing without error. I might’ve even suggested that you redownload and check the checksum (SHA-256), but then again you would have had a bunch of errors if even one byte was off!
Here’s hoping one of these things works…good luck to you!
simplepinoi177 said:
So, actually, I strongly suggest using CMD versus PowerShell. If anything, you make sure to run it “as Administrator” (either by right-clicking, or searching Command Prompt and right-clicking) and then directing to and running the flash-all.bat. And to keep the window from closing, you edit the file – in the same way you would to remove the “-w” – by right-clicking and selecting “Edit”. At the very end, remove/erase the word “exit”; this should keep it from closing out the window. You should do this from here on out. Also, you probably don’t have to do the “./” thing, but I’m not sure if it matters at all or not.
At this point, I (personally) would go through the process of manually formatting the system, boot, dtbo, and data partitions using fastboot commands in the bootloader; but I’m worried it might affect the bootloader in some inadvertent way and completely brick the device – which is why I’d only do it myself with only myself to blame. I super really bricked one device already by accidentally formatting the bootloader partition, then before reflashing/re-installing the stock bootloader, I accidentally rebooted and I couldn’t even recover anything because there was no Bootloader Mode to do it from. So what I suggest to you is this…
I suggest you download TWRP image file and temporarily boot into that custom recovery to “wipe” and format everything. You can do this by downloading and moving the TWRP .img file to the platform-tools folder that has the adb and fastboot executables/files. Then run the command “fastboot boot twrp.img” (replace “twrp” with the actual file name). In there, I would go to the “Wipe” section and wipe the system, data, and internal storage partition – If there was an option to wipe the boot partition I would suggest that; but we’ll get to that if need be – if you go into the “Advanced Wipe” section. While there, you might even try the “Repair or Change File System”. After all of this, you should reboot back into the bootloader and load up a CMD after clicking “Run as Administrator” and run the flash-all.bat again.
If it still is struggling afterwards, you might want to try obtaining the stock boot.img and dtbo.img -- you should be able to find it in the Full Factory image .zip file; you just have to delve deep enough through the multiple .zips -- and manually flashing it to the device; command would be “fastboot flash boot boot.img” & “fastboot flash dtbo dtbo.img” – remember you will have to move the .img files to the same platform-tools folder as fastboot and adb .exe files.
Some thoughts; I really wonder if it is the new Q/10 OS version or something and/or the new way Google has assembled the Full Factory images, but most of the time running the flash-all with the “-w” intact resolves any boot and system issues! None of these steps are usually necessary further than that. I was suspecting something was happening in the flashing, but your log shows that everything is flashing and installing without error. I might’ve even suggested that you redownload and check the checksum (SHA-256), but then again you would have had a bunch of errors if even one byte was off!
Here’s hoping one of these things works…good luck to you!
Click to expand...
Click to collapse
I can not even boot to TWRP the only thing I can boot is the bootloader, booting TWRP or boot to stock recovery from bootloader results to a bootloop, even if I power down the device and plug the charger without doing anything the phone start to bootloop.
I have used both Powershell and CMD(as admin I still get the same result)
Code:
Microsoft Windows [Version 10.0.18362.356]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd C:\Users\Ninga\Desktop\A10
C:\Users\Ninga\Desktop\A10>fastboot devices
711KPRW0625214 fastboot
C:\Users\Ninga\Desktop\A10>flash-all.bat
Sending 'bootloader_b' (36352 KB) OKAY [ 0.803s]
Writing 'bootloader_b' OKAY [ 0.276s]
Finished. Total time: 1.241s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.004s
Sending 'radio_b' (60388 KB) OKAY [ 1.332s]
Writing 'radio_b' OKAY [ 0.819s]
Finished. Total time: 2.400s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.005s
--------------------------------------------
Bootloader Version...: TMZ30h
Baseband Version.....: g8998-00012-1905270706
Serial Number........: 711KPRW0625214
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.001s]
Setting current slot to 'b' OKAY [ 0.009s]
extracting boot.img (40 MB) to disk... took 0.240s
archive does not contain 'boot.sig'
Sending 'boot_b' (40960 KB) OKAY [ 0.898s]
Writing 'boot_b' OKAY [ 0.535s]
extracting dtbo.img (8 MB) to disk... took 0.051s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.180s]
Writing 'dtbo_b' OKAY [ 0.103s]
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_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.003s]
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 (2374 MB) to disk... took 63.201s
archive does not contain 'system.sig'
Sending sparse 'system_b' 1/5 (524284 KB) OKAY [ 12.061s]
Writing 'system_b' OKAY [ 2.228s]
Sending sparse 'system_b' 2/5 (524284 KB) OKAY [ 12.036s]
Writing 'system_b' OKAY [ 2.231s]
Sending sparse 'system_b' 3/5 (524284 KB) OKAY [ 12.034s]
Writing 'system_b' OKAY [ 2.218s]
Sending sparse 'system_b' 4/5 (524284 KB) OKAY [ 12.271s]
Writing 'system_b' OKAY [ 2.237s]
Sending sparse 'system_b' 5/5 (334556 KB) OKAY [ 8.023s]
Writing 'system_b' OKAY [ 1.411s]
archive does not contain 'system_ext.img'
extracting system_other.img (304 MB) to disk... took 5.676s
archive does not contain 'system.sig'
Sending 'system_a' (311784 KB) OKAY [ 6.852s]
Writing 'system_a' OKAY [ 1.315s]
extracting vendor.img (340 MB) to disk... took 4.352s
archive does not contain 'vendor.sig'
Sending 'vendor_b' (348532 KB) OKAY [ 7.676s]
Writing 'vendor_b' OKAY [ 1.479s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 0.620s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 29518843 4k blocks and 7380992 inodes
Filesystem UUID: e5ba5316-e02a-11e9-92a6-a7920be70672
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 'userdata' (4672 KB) OKAY [ 0.102s]
Writing 'userdata' OKAY [ 0.035s]
Rebooting OKAY [ 0.000s]
Finished. Total time: 171.544s
Press any key to exit...
I don't know much but what does this code means?
Code:
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'
At this point I would try anything possible as I was 99% giving up and prepared to buy a new phone, but if there is even a 0.05% chance of something to work I would try that.
Thanks
NingaR said:
I can not even boot to TWRP the only thing I can boot is the bootloader, booting TWRP or boot to stock recovery from bootloader results to a bootloop, even if I power down the device and plug the charger without doing anything the phone start to bootloop.
I have used both Powershell and CMD(as admin I still get the same result)
Code:
Microsoft Windows [Version 10.0.18362.356]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd C:\Users\Ninga\Desktop\A10
C:\Users\Ninga\Desktop\A10>fastboot devices
711KPRW0625214 fastboot
C:\Users\Ninga\Desktop\A10>flash-all.bat
Sending 'bootloader_b' (36352 KB) OKAY [ 0.803s]
Writing 'bootloader_b' OKAY [ 0.276s]
Finished. Total time: 1.241s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.004s
Sending 'radio_b' (60388 KB) OKAY [ 1.332s]
Writing 'radio_b' OKAY [ 0.819s]
Finished. Total time: 2.400s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.005s
--------------------------------------------
Bootloader Version...: TMZ30h
Baseband Version.....: g8998-00012-1905270706
Serial Number........: 711KPRW0625214
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.001s]
Setting current slot to 'b' OKAY [ 0.009s]
extracting boot.img (40 MB) to disk... took 0.240s
archive does not contain 'boot.sig'
Sending 'boot_b' (40960 KB) OKAY [ 0.898s]
Writing 'boot_b' OKAY [ 0.535s]
extracting dtbo.img (8 MB) to disk... took 0.051s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.180s]
Writing 'dtbo_b' OKAY [ 0.103s]
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_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.003s]
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 (2374 MB) to disk... took 63.201s
archive does not contain 'system.sig'
Sending sparse 'system_b' 1/5 (524284 KB) OKAY [ 12.061s]
Writing 'system_b' OKAY [ 2.228s]
Sending sparse 'system_b' 2/5 (524284 KB) OKAY [ 12.036s]
Writing 'system_b' OKAY [ 2.231s]
Sending sparse 'system_b' 3/5 (524284 KB) OKAY [ 12.034s]
Writing 'system_b' OKAY [ 2.218s]
Sending sparse 'system_b' 4/5 (524284 KB) OKAY [ 12.271s]
Writing 'system_b' OKAY [ 2.237s]
Sending sparse 'system_b' 5/5 (334556 KB) OKAY [ 8.023s]
Writing 'system_b' OKAY [ 1.411s]
archive does not contain 'system_ext.img'
extracting system_other.img (304 MB) to disk... took 5.676s
archive does not contain 'system.sig'
Sending 'system_a' (311784 KB) OKAY [ 6.852s]
Writing 'system_a' OKAY [ 1.315s]
extracting vendor.img (340 MB) to disk... took 4.352s
archive does not contain 'vendor.sig'
Sending 'vendor_b' (348532 KB) OKAY [ 7.676s]
Writing 'vendor_b' OKAY [ 1.479s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 0.620s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 29518843 4k blocks and 7380992 inodes
Filesystem UUID: e5ba5316-e02a-11e9-92a6-a7920be70672
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 'userdata' (4672 KB) OKAY [ 0.102s]
Writing 'userdata' OKAY [ 0.035s]
Rebooting OKAY [ 0.000s]
Finished. Total time: 171.544s
Press any key to exit...
I don't know much but what does this code means?
Code:
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'
At this point I would try anything possible as I was 99% giving up and prepared to buy a new phone, but if there is even a 0.05% chance of something to work I would try that.
Thanks
Click to expand...
Click to collapse
Yeah..the "archive does not contain" alerts are normal...I think it has something to do with Google covering all their bases and having their install/flashing code be able to apply to other various devices that do have those partitions/images.
Man...yeah I can't think of any reason why your phone shouldn't be working or at least being able to boot to the recovery, even temporarily.
I guess just two things, just "for sh*ts and g*ggles"; please try running the "fastboot flashing unlock" & "fastboot flashing unlock_critical". The next is to try installing the Full Factory image of Android Pie/9 instead of Q/10; maybe something in the new OS version is causing issues -- I might even go a couple months back since they recently changed some stuff in the Full Factory where the flash-all file is located in a different place!
Outside of these 2 things, I can't think of anything more; never have I seen absolutely no errors and completely normal flash-all (or Deuce's script) process and still have this blaring issue.
Hopefully these do something, but if it doesn't, sorry I couldn't do more. Good luck to you...
simplepinoi177 said:
Yeah..the "archive does not contain" alerts are normal...I think it has something to do with Google covering all their bases and having their install/flashing code be able to apply to other various devices that do have those partitions/images.
Man...yeah I can't think of any reason why your phone shouldn't be working or at least being able to boot to the recovery, even temporarily.
I guess just two things, just "for sh*ts and g*ggles"; please try running the "fastboot flashing unlock" & "fastboot flashing unlock_critical". The next is to try installing the Full Factory image of Android Pie/9 instead of Q/10; maybe something in the new OS version is causing issues -- I might even go a couple months back since they recently changed some stuff in the Full Factory where the flash-all file is located in a different place!
Outside of these 2 things, I can't think of anything more; never have I seen absolutely no errors and completely normal flash-all (or Deuce's script) process and still have this blaring issue.
Hopefully these do something, but if it doesn't, sorry I couldn't do more. Good luck to you...
Click to expand...
Click to collapse
Thank you so much for your help mate, I will keep searching and try if I can get it to boot.
simplepinoi177 said:
What is the output/log for when you run the flash-all?
Also, confirm you have the most up-to-date platform-tools as well as using a USB-A to USB-A (avoid USB-C as much as possible, at least with taimen) cord and various different ports.
Click to expand...
Click to collapse
Why avoid USB-C cables?
quera said:
Why avoid USB-C cables?
Click to expand...
Click to collapse
I think he meant to use USB-A to USB-C cable rather than using USB-C to USB-C cable
NingaR said:
Thank you so much for your help mate, I will keep searching and try if I can get it to boot.
Click to expand...
Click to collapse
I have a pixel 2 xl patched boot image that would boot a phone with root but magisk core-only mode.
You are welcome to try it. This has not been zipped. Just rename it. Suffix was added so it could be uploaded.
fastboot boot image-new.img
https://www.androidfilehost.com/?fid=1899786940962594367
So did you finally managed to solve your issue?
Yeah...I'm curious if running a Full Factory Pie/9 produced anything different...
but I'm betting @Ninjar probably called it quits and is sending it "in" or something...
But yes, an update would be great!
arismelachrinos said:
So did you finally managed to solve your issue?
Click to expand...
Click to collapse
Unfortunately No, still same thing.
simplepinoi177 said:
Yeah...I'm curious if running a Full Factory Pie/9 produced anything different...
but I'm betting @Ninjar probably called it quits and is sending it "in" or something...
But yes, an update would be great!
Click to expand...
Click to collapse
I ordered another phone, and I can not send this one in as I bought it from AliExpress.
NingaR said:
I ordered another phone, and I can not send this one in as I bought it from AliExpress.
Click to expand...
Click to collapse
Did you try booting with the modified boot image?
Tulsadiver said:
Did you try booting with the modified boot image?
Click to expand...
Click to collapse
Yes but still same thing, someone said it could be a hardware problem. :crying:
NingaR said:
I ordered another phone, and I can not send this one in as I bought it from AliExpress.
Click to expand...
Click to collapse
Well...since it seems that you may not be doing anything else with "this one", I might just walk you through manually formatting the partitions since/if it might be okay to merely "go for broke" even if there's a risk of permanently bricking it...
let me know here if you'd like to proceed...
simplepinoi177 said:
Well...since it seems that you may not be doing anything else with "this one", I might just walk you through manually formatting the partitions since/if it might be okay to merely "go for broke" even if there's a risk of permanently bricking it...
let me know here if you'd like to proceed...
Click to expand...
Click to collapse
Sure, lets proceed
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.
Update: Problem fixed as @Lughnasadh said: flash.android.com fixes the issue a buggy fastboot version can create.
=======
DISCLAIMER:
this might look like a double post.
if I could change the topic, i would have continued the old thread. I saw the topic doesnt reflect that problem very well anymore. I hope I dont break any rules by this.
So, for the history of all this, you can check this post which contains lots of logs: https://forum.xda-developers.com/t/flash-all-sh-vendor-partition-non-existing.4570905/
It also contains the Tip from @Lughnasadh solving the first huddle: fastboot 34+ is flawed, i downgraded to fastboot 33.0.1 and all the inital problems were gone.
=========
PROBLEM
=========
I dont talk about the why. If you want to know, look at the outdated post.
Situation: Vendor partition missing. Flashing firmware image isnt possbile because fastbootd cannot be started, because there is no vendor partition. Plus you can only create or modify partitions in fastbootd, not in fastboot.
Is this a classical hen-egg problem and I have a soft bricked phone, or is there any way around I dont see?
Here is some log for you:
Bash:
┬─[[email protected]:~/D/raven-tq2a.230305.008.e1]─[03:50:35]─[I]
╰─>$ fastboot update image-raven-tq2a.230305.008.e1.zip
--------------------------------------------
Bootloader Version...: slider-1.2-9465321
Baseband Version.....: g5123b-112825-230302-B-9675756
Serial Number........: 23041FDEE005AM
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'b' OKAY [ 0.124s]
extracting boot.img (64 MB) to disk... took 0.339s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.116s]
Writing 'boot_b' OKAY [ 0.116s]
archive does not contain 'init_boot.img'
extracting dtbo.img (16 MB) to disk... took 0.065s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.522s]
Writing 'dtbo_b' OKAY [ 0.028s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.009s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_b' (1024 KB) OKAY [ 0.034s]
Writing 'pvmfw_b' OKAY [ 0.003s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (12 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.002s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_b' OKAY [ 0.002s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor_b' OKAY [ 0.002s]
extracting vendor_boot.img (64 MB) to disk... took 0.367s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (65536 KB) OKAY [ 2.130s]
Writing 'vendor_boot_b' OKAY [ 0.116s]
archive does not contain 'vendor_kernel_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Hmm, while copying this I wonder, if I can supply a vendor_kernel_boot.img, add it to the update zip and then start fastbootd this way. where do i get an up to date vendor_kernel_boot.img though?
Starting googling now. Dont hessitate to meanwhile answer
mad-murdock said:
DISCLAIMER:
this might look like a double post.
if I could change the topic, i would have continued the old thread. I saw the topic doesnt reflect that problem very well anymore. I hope I dont break any rules by this.
So, for the history of all this, you can check this post which contains lots of logs: https://forum.xda-developers.com/t/flash-all-sh-vendor-partition-non-existing.4570905/
=========
PROBLEM
=========
I dont talk about the why. If you want to know, look at the outdated post.
Situation: Vendor partition missing. Flashing firmware image isnt possbile because fastbootd cannot be started, because there is no vendor partition. Plus you can only create or modify partitions in fastbootd, not in fastboot.
Is this a classical hen-egg problem and I have a soft bricked phone, or is there any way around I dont see?
Here is some log for you:
Bash:
┬─[[email protected]:~/D/raven-tq2a.230305.008.e1]─[03:50:35]─[I]
╰─>$ fastboot update image-raven-tq2a.230305.008.e1.zip
--------------------------------------------
Bootloader Version...: slider-1.2-9465321
Baseband Version.....: g5123b-112825-230302-B-9675756
Serial Number........: 23041FDEE005AM
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'b' OKAY [ 0.124s]
extracting boot.img (64 MB) to disk... took 0.339s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.116s]
Writing 'boot_b' OKAY [ 0.116s]
archive does not contain 'init_boot.img'
extracting dtbo.img (16 MB) to disk... took 0.065s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.522s]
Writing 'dtbo_b' OKAY [ 0.028s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.009s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_b' (1024 KB) OKAY [ 0.034s]
Writing 'pvmfw_b' OKAY [ 0.003s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (12 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.002s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_b' OKAY [ 0.002s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor_b' OKAY [ 0.002s]
extracting vendor_boot.img (64 MB) to disk... took 0.367s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (65536 KB) OKAY [ 2.130s]
Writing 'vendor_boot_b' OKAY [ 0.116s]
archive does not contain 'vendor_kernel_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Hmm, while copying this I wonder, if I can supply a vendor_kernel_boot.img, add it to the update zip and then start fastbootd this way. where do i get an up to date vendor_kernel_boot.img though?
Starting googling now. Dont hessitate to meanwhile answer
Click to expand...
Click to collapse
Try Android Flash Tool. You can force flash partitions with it.
Also, did you try with Platform Tools 33.0.3 as I mentioned in your other post? That version doesn't have a problem booting into fastbootd like 34+ does.
For future notice, just report your post, asking that it be recatogorized.
Lughnasadh said:
Try Android Flash Tool. You can force flash partitions with it.
Also, did you try with Platform Tools 33.0.3 as I mentioned in your other post? That version doesn't have a problem booting into fastbootd like 34+ does.
Click to expand...
Click to collapse
Oh yes, all this new stuff is based on your super good tip with using 33.0.3 over 34+...
I use arch linux, I am an seasoned linux admin, I accidentally installed a non-stable fastboot and that was the reason the first flash-all.sh was breaking.
Thanks for pointing this out, @Lughnasadh , that totally solved the first part. Sorry I didnt make this clear. I will update the OP to more clearly reflect this.
Its late here in germany, I will try tomorrow morning what you said. I guess it will work.
P.S.: Do you agree the original topic was misleading?
Arealhooman said:
For future notice, just report your post, asking that it be recatogorized.
Click to expand...
Click to collapse
Thanks. Thats the better solution and is noted for next time. I am not very active here anymore, but this is still the best place to get information if something goes wrong. XDA or nagging one of my old android os developers I had the honor to work with in my life...
Thanks for showing me a cool use of the report button, too
Lughnasadh said:
Try Android Flash Tool. You can force flash partitions with it.
Also, did you try with Platform Tools 33.0.3 as I mentioned in your other post? That version doesn't have a problem booting into fastbootd like 34+ does.
Click to expand...
Click to collapse
Sorry it took a while, my life is wonderful and full of people... sooo...
I think i got it working with flash.android.com
I confess the flash.android.com is new to me. I lost close contact with the android open source scene a few years back (sorry steve kondik ... and so in some regards I am a noob, while in others i got the needed background info.
to me the flash.android.com flasher seems to only detect phones in adb while booted to the system. but from what you say, there should be a way to force the flash also while not having anything than fastboot. But, i cannot find that anywhere. I am probably blind, but can you explain the process a bit more detailed. I tried a few google searches, but couldnt find a guide.
Cheers
Update: Problem fixed as @Lughnasadh said: flash.android.com fixes the issue a buggy fastboot version can create.