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...
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!
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
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