Develop Bugs

[Q] Not booting anymore and no recovery

Hello,
i am just thinking i bricked my Galaxy Nexus.
But first i will describe what happened:
My device was running fine with 4.3 Cyanonogenmod Nighlty builds for a few days but yesterday in the car the device suddenly was stuck in a bootloop.
After arriving home i tried to fix that by removing the battery and give it a few minutes.
But my device was stuck in a bootloop after that.
I tried to reflash ROM and RADIO few times but nothing helped.
I was in TWRP Recovery and wanted to get CWM just to rescue some files via USB before flashing stock ROM.
So i got the toolkit and tried to flash a recovery and the script told me all worked, but there seems not to be any recovery on the device anymore.
When i boot into bootloader and select Recovery i am just getting the battery symbol and nothing more happens.
I flashed a stock ROM via toolkit without wiping userdata but this did not help, too.
Now i am stuck with a device that does not seem to have a recovery and does not boot behind the Google Logo.
Also the device only reacts to the power button anymore when on external power via USB wire, not on battery.
Any suggestions how to continue or just rescue my files from the "sdcard" ?

myxor said:
Hello,
i am just thinking i bricked my Galaxy Nexus.
But first i will describe what happened:
My device was running fine with 4.3 Cyanonogenmod Nighlty builds for a few days but yesterday in the car the device suddenly was stuck in a bootloop.
After arriving home i tried to fix that by removing the battery and give it a few minutes.
But my device was stuck in a bootloop after that.
I tried to reflash ROM and RADIO few times but nothing helped.
I was in TWRP Recovery and wanted to get CWM just to rescue some files via USB before flashing stock ROM.
So i got the toolkit and tried to flash a recovery and the script told me all worked, but there seems not to be any recovery on the device anymore.
When i boot into bootloader and select Recovery i am just getting the battery symbol and nothing more happens.
I flashed a stock ROM via toolkit without wiping userdata but this did not help, too.
Now i am stuck with a device that does not seem to have a recovery and does not boot behind the Google Logo.
Also the device only reacts to the power button anymore when on external power via USB wire, not on battery.
Any suggestions how to continue or just rescue my files from the "sdcard" ?
Click to expand...
Click to collapse
Drop the toolkit, learn how to do it proper or stop flashing stuff before you hurt your device.

beekay201 said:
Drop the toolkit, learn how to it proper or stop flashing stuff before you hurt your device.
Click to expand...
Click to collapse
I guess it's already to late
I just tried to install the CWM Recovery via fastboot
D:\gn\adt-bundle-windows-x86_64
sending 'recovery' (6214 KB)...
OKAY [ 0.631s]
writing 'recovery'...
OKAY [ 0.759s]
finished. total time: 1.392s
D:\gn\adt-bundle-windows-x86_64
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
Click to expand...
Click to collapse
But when i select Recovery from the bootloader menu i only get the charging battery icon.
Anything i can do?

I've never had a similar experience so but from reading several similar topics I will suggest that you flash a factory image. Not a STOCK ROM, but the actual factory image. It *should* re-lock the boot loader and default you to complete stock.Your files will be gone but assuming the files aren't overwritten you can still recover them per the instructions on this thread. As others have suggested, lay off the toolkit. Without it, you will be absolutely sure as to what is going on with your phone. Read, read, read, read before doing anything you're unfamiliar with.

iLeopard said:
I've never had a similar experience so but from reading several similar topics I will suggest that you flash a factory image. Not a STOCK ROM, but the actual factory image. It *should* re-lock the boot loader and default you to complete stock.Your files will be gone but assuming the files aren't overwritten you can still recover them per the instructions on this thread. As others have suggested, lay off the toolkit. Without it, you will be absolutely sure as to what is going on with your phone. Read, read, read, read before doing anything you're unfamiliar with.
Click to expand...
Click to collapse
Thank you for your advices but the results are not what i hoped for:
After flashing the factory image from https://developers.google.com/android/nexus/images#instructions with the following output:
Code:
sending 'bootloader' (2308 KB)...
OKAY [ 0.236s]
writing 'bootloader'...
OKAY [ 0.605s]
finished. total time: 0.841s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.233s]
writing 'radio'...
OKAY [ 2.590s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: XXXXXXXXXXXXXXXX (censored by author)
--------------------------------------------
checking product...
OKAY [ 0.006s]
checking version-bootloader...
OKAY [ 0.008s]
checking version-baseband...
OKAY [ 0.007s]
sending 'boot' (4376 KB)...
OKAY [ 0.438s]
writing 'boot'...
OKAY [ 0.380s]
sending 'recovery' (4924 KB)...
OKAY [ 0.497s]
writing 'recovery'...
OKAY [ 0.761s]
erasing 'system'...
OKAY [ 0.013s]
sending 'system' (474180 KB)...
OKAY [ 46.800s]
writing 'system'...
OKAY [ 47.830s]
erasing 'userdata'...
OKAY [ 0.550s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14539534336
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3549691
Block groups: 109
Reserved block group size: 871
Created filesystem with 11/887696 inodes and 97200/3549691 blocks
sending 'userdata' (137559 KB)...
writing 'userdata'...
OKAY [ 25.975s]
erasing 'cache'...
OKAY [ 0.015s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 452984832
Block size: 4096
Blocks per group: 32768
Inodes per group: 6912
Inode size: 256
Journal blocks: 1728
Label:
Blocks: 110592
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27648 inodes and 3566/110592 blocks
sending 'cache' (8832 KB)...
writing 'cache'...
OKAY [ 3.136s]
rebooting...
finished. total time: 126.458s
Press any key to exit...
the device is stuck in the Google Logo now for about 10 Minutes and nothing is happening :crying:

Was this issued using flash-all.bat?
Sent from my Galaxy Nexus using xda app-developers app

myxor said:
Thank you for your advices but the results are not what i hoped for:
After flashing the factory image from https://developers.google.com/android/nexus/images#instructions with the following output:
Code:
sending 'bootloader' (2308 KB)...
OKAY [ 0.236s]
writing 'bootloader'...
OKAY [ 0.605s]
finished. total time: 0.841s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.233s]
writing 'radio'...
OKAY [ 2.590s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: XXXXXXXXXXXXXXXX (censored by author)
--------------------------------------------
checking product...
OKAY [ 0.006s]
checking version-bootloader...
OKAY [ 0.008s]
checking version-baseband...
OKAY [ 0.007s]
sending 'boot' (4376 KB)...
OKAY [ 0.438s]
writing 'boot'...
OKAY [ 0.380s]
sending 'recovery' (4924 KB)...
OKAY [ 0.497s]
writing 'recovery'...
OKAY [ 0.761s]
erasing 'system'...
OKAY [ 0.013s]
sending 'system' (474180 KB)...
OKAY [ 46.800s]
writing 'system'...
OKAY [ 47.830s]
erasing 'userdata'...
OKAY [ 0.550s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14539534336
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3549691
Block groups: 109
Reserved block group size: 871
Created filesystem with 11/887696 inodes and 97200/3549691 blocks
sending 'userdata' (137559 KB)...
writing 'userdata'...
OKAY [ 25.975s]
erasing 'cache'...
OKAY [ 0.015s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 452984832
Block size: 4096
Blocks per group: 32768
Inodes per group: 6912
Inode size: 256
Journal blocks: 1728
Label:
Blocks: 110592
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27648 inodes and 3566/110592 blocks
sending 'cache' (8832 KB)...
writing 'cache'...
OKAY [ 3.136s]
rebooting...
finished. total time: 126.458s
Press any key to exit...
the device is stuck in the Google Logo now for about 10 Minutes and nothing is happening :crying:
Click to expand...
Click to collapse
4.3 first bootup times is much slower than previous versions. Let it boot until it reboots itself or something. If after 45min it still going at it, I think you have two options:
- my first suggestion is to return to the bootloader, and follow this thread's first post. No need to reflash bootloader or radio, as far as I can tell, nothing's wrong with those two. Erase, then format all the remaining partitions.
Code:
fastboot erase partition_name
fastboot format partition_name
Flash all the remaining partitions: boot, recovery (a custom recovery if you'd like, beware of 4.3 changes - not sure all the custom recoveries have updated accordingly, check dev section), system, userdata, cache.
Code:
fastboot flash partition /path/to/filename.img
- my second suggestion is that you search of a way to enable adbd, to see whats going on. That might require some extra steps, such as editing init.rc i believe.
Anyways, if you return to the bootloader, and try to
Code:
fastboot boot /path/to/cwm_or_twrp.img
What does it do? Can you use your custom recovery now?

beekay201 said:
4.3 first bootup times is much slower than previous versions. Let it boot until it reboots itself or something. If after 45min it still going at it, I think you have two options:
- my first suggestion is to return to the bootloader, and follow this thread's first post. No need to reflash bootloader or radio, as far as I can tell, nothing's wrong with those two. Erase, then format all the remaining partitions.
Code:
fastboot erase partition_name
fastboot format partition_name
Flash all the remaining partitions: boot, recovery (a custom recovery if you'd like, beware of 4.3 changes - not sure all the custom recoveries have updated accordingly, check dev section), system, userdata, cache.
Code:
fastboot flash partition /path/to/filename.img
- my second suggestion is that you search of a way to enable adbd, to see whats going on. That might require some extra steps, such as editing init.rc i believe.
Anyways, if you return to the bootloader, and try to
Code:
fastboot boot /path/to/cwm_or_twrp.img
What does it do? Can you use your custom recovery now?
Click to expand...
Click to collapse
I ran through the linked post and erased + formated all possible partitions.
Is it normal that o can not format some partitions like the recovery partition?
Code:
>fastboot format recovery
formatting 'recovery' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.009s
After that i flashed the partitions once by once per
Code:
fastboot flash partitions /path/file.img
with the files from the factory image.
Sadly no boot possible.
Then i tried to boot my recovery by
Code:
fastboot boot /path/to/cwm_or_twrp.img
but it happens the same as before:
after selecting to boot into recovery from fastboot mode the google logo appears for a few seconds then the screens goes black and returns with the battery charging symbol.
After turning the phone off and booting again into fastboot mode i can read in red letters: "FASTBOOT MODE - NO BOOT OR RECOVERY IMG".
This stays the same after flashing a recovery image via fastboot :crying:

myxor said:
I ran through the linked post and erased + formated all possible partitions.
Is it normal that o can not format some partitions like the recovery partition?
Code:
>fastboot format recovery
formatting 'recovery' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.009s
After that i flashed the partitions once by once per
Code:
fastboot flash partitions /path/file.img
with the files from the factory image.
Sadly no boot possible.
Then i tried to boot my recovery by
Code:
fastboot boot /path/to/cwm_or_twrp.img
but it happens the same as before:
after selecting to boot into recovery from fastboot mode the google logo appears for a few seconds then the screens goes black and returns with the battery charging symbol.
After turning the phone off and booting again into fastboot mode i can read in red letters: "FASTBOOT MODE - NO BOOT OR RECOVERY IMG".
This stays the same after flashing a recovery image via fastboot :crying:
Click to expand...
Click to collapse
Use omapflash to restore your bootloader. See this thread's post with useful links. http://forum.xda-developers.com/showthread.php?t=1812959

I sent in the device to the repair and got it back a few days ago.
Some "broken parts" were changed and i got a new battery.
Now my Galaxy Nexus works again like a charm
Don't really know what parts were broken but it seemed that it was a hardware failure.
Thanks to everyone who helped! :good:

Need Help Unbricking my Pixel XL

need help unbricking my pixel xl.
i downloaded the factory image from google and ran the flashall.bat but it keeps failing.
target reported max download size of 536870912 bytes
sending 'bootloadera' (32820 KB)...
OKAY [ 0.770s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
OKAY [ 1.038s]
finished. total time: 1.812s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.009s
target reported max download size of 536870912 bytes
sending 'radioa' (57048 KB)...
OKAY [ 1.302s]
writing 'radioa'...
OKAY [ 0.897s]
finished. total time: 2.201s
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.016s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 122633060352
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29939712
Block groups: 914
Reserved block group size: 1024
Created filesystem with 11/7487488 inodes and 518062/29939712 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609191801
Serial Number........: HT69D0200852
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.048s]
sending 'boota' (26481 KB)...
OKAY [ 0.641s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.097s
Press any key to exit...

I had the same problem. You need to extract everything within the file you downloaded for the factory in same directory(there should be another zip in there)... and then flash everything individually like the flash all file would do. So flash bootloader... Radio... (Reboot bootloader after this****)... And then flash everything else individually.. then try and start phone

I thought I read that you need the latest SDK in order for flash-all to work. I ran into issues like this when trying to restore my Pixel C to stock. As mentioned, flashing each image separately will work as well.

Shacocka said:
I had the same problem. You need to extract everything within the file you downloaded for the factory in same directory(there should be another zip in there)... and then flash everything individually like the flash all file would do. So flash bootloader... Radio... (Reboot bootloader after this****)... And then flash everything else individually.. then try and start phone
Click to expand...
Click to collapse
What he said
Mike02z said:
I thought I read that you need the latest SDK in order for flash-all to work. I ran into issues like this when trying to restore my Pixel C to stock. As mentioned, flashing each image separately will work as well.
Click to expand...
Click to collapse
I have old sdk and still can flash. You just have to do each step manually.

SDK platform-tools 25 is required for fastboot to automatically recognize a partition being used as the default partition. It is the only version of fastboot that can handle the Pixel partition layout using "fastboot flash update.zip" or any flash scripts which rely on this automated process.

Pixel XL is bricked.

Hi folks. Friend managed to brick his pixel XL. Keeps booting into the no-command image, and cannot boot into safe mode. He would like to avoid factory resetting it as not all of his pictures are uploaded into his google drive. (He doesn't like the idea of big brother spying on him). Is there any way to recover the images?

How did he brick it?

ThatZeldaFan50 said:
Keeps booting into the no-command image
Click to expand...
Click to collapse
I can't think of what this is.
Are you talking about the android laying on its side like in my forum picture?
If the phone can be rebooted to Recovery mode, then your friend can use a Computer to transfer the files off the phone.

Mr. Orange 645 said:
How did he brick it?
Click to expand...
Click to collapse
He has no idea. According to him, it just happened during the day.
CZ Eddie said:
I can't think of what this is.
Are you talking about the android laying on its side like in my forum picture?
If the phone can be rebooted to Recovery mode, then your friend can use a Computer to transfer the files off the phone.
Click to expand...
Click to collapse
Sadly, he cannot boot into Recovery mode. It say "/cache not found" or something like that. Sorry, I don't have the phone with me, and I'm not at his house right now.

If he can get to Fastboot then he can flash the stock image on top of the current image without losing any setup apps/data/pics.
Just remove the -w from the script.
My guide will walk him through the process.
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Remember to remove the -w from the script though!
Or download the -w modded script I added to my thread.
If he can't get to either Fastboot OR Recovery then I'd consider that a "hard brick".
Are you sure he really knows how to boot to Fastboot and Recovery? Maybe he's doing that wrong. It's easy to mess up.

ThatZeldaFan50 said:
Keeps booting into the no-command image
Click to expand...
Click to collapse
Oh, is that the stock Recovery?
Cool.
He can use ADB from there to recover and transfer files & stuff.

CZ Eddie said:
If he can get to Fastboot then he can flash the stock image on top of the current image without losing any setup apps/data/pics.
Just remove the -w from the script.
My guide will walk him through the process.
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Remember to remove the -w from the script though!
Or download the -w modded script I added to my thread.
If he can't get to either Fastboot OR Recovery then I'd consider that a "hard brick".
Are you sure he really knows how to boot to Fastboot and Recovery? Maybe he's doing that wrong. It's easy to mess up.
Click to expand...
Click to collapse
If I am running Resurrection and I am on slot B, can just use the flashall in adb regardless of which slot I'm on?
Sent from my Pixel XL using XDA-Developers Legacy app

yankeesfan714 said:
If I am running Resurrection and I am on slot B, can just use the flashall in adb regardless of which slot I'm on?
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've never tested that before.
It does write *something* to both slots though.
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32980 KB)...
OKAY [ 0.909s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 4.709s]
finished. total time: 5.617s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.062s
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'radio_a' (57192 KB)...
OKAY [ 1.445s]
writing 'radio_a'...
OKAY [ 0.570s]
finished. total time: 2.015s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1611091517
Baseband Version.....: 8996-012511-1611190200
Serial Number........: HT6920203793
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boot_a' (26209 KB)...
OKAY [ 0.690s]
writing 'boot_a'...
OKAY [ 0.298s]
erasing 'system_a'...
OKAY [ 0.367s]
sending sparse 'system_a' 1/4 (515538 KB)...
OKAY [ 13.254s]
writing 'system_a' 1/4...
OKAY [ 5.541s]
sending sparse 'system_a' 2/4 (521786 KB)...
OKAY [ 13.566s]
writing 'system_a' 2/4...
OKAY [ 5.138s]
sending sparse 'system_a' 3/4 (491987 KB)...
OKAY [ 12.766s]
writing 'system_a' 3/4...
OKAY [ 6.688s]
sending sparse 'system_a' 4/4 (32756 KB)...
OKAY [ 0.848s]
writing 'system_a' 4/4...
OKAY [ 0.350s]
erasing 'system_b'...
OKAY [ 0.402s]
sending sparse 'system_b' 1/4 (517080 KB)...
OKAY [ 13.417s]
writing 'system_b' 1/4...
OKAY [ 3.986s]
sending sparse 'system_b' 2/4 (514384 KB)...
OKAY [ 13.119s]
writing 'system_b' 2/4...
OKAY [ 4.297s]
sending sparse 'system_b' 3/4 (524287 KB)...
OKAY [ 13.508s]
writing 'system_b' 3/4...
OKAY [ 3.888s]
sending sparse 'system_b' 4/4 (85782 KB)...
OKAY [ 2.247s]
writing 'system_b' 4/4...
OKAY [ 0.810s]
erasing 'vendor_a'...
OKAY [ 0.153s]
sending 'vendor_a' (235322 KB)...
OKAY [ 5.841s]
writing 'vendor_a'...
OKAY [ 3.752s]
Setting current slot to 'a'...
OKAY [ 0.058s]
erasing 'userdata'...
OKAY [ 2.286s]
sending 'userdata' (138957 KB)...
OKAY [ 3.450s]
writing 'userdata'...
OKAY [ 1.300s]
rebooting...
finished. total time: 132.460s
Press any key to exit...

yankeesfan714 said:
If I am running Resurrection and I am on slot B, can just use the flashall in adb regardless of which slot I'm on?
Click to expand...
Click to collapse
It doesn't matter which slot you're on. You can use the flash all. It will automatically flash to the active slot.

Need a Bootloader

Hello,
I'm not new to flashing / rooting / modding or Nexus / Pixel scene.. But that is a first for me.
I've updated my Pixel 2 XL to the latest version and I wanted to try out the P preview.. The problem is that apparently I have an newer version of the bootloader.
Device version-bootloader is 'TMZ12bb'.
Update requires 'TMZ20f'.
So if anyone could upload the TMZ20f I would really appreciate it.

That error is usually because you didn't unlock critical.

TonikJDK said:
That error is usually because you didn't unlock critical.
Click to expand...
Click to collapse
Hmm.. So I need to relock the bootloader and unlock it again?

Welp! I've unlocked critical.. But now I get "check console" error. Great.

Bucika said:
Welp! I've unlocked critical.. But now I get "check console" error. Great.
Click to expand...
Click to collapse
Are you using the latest version of fastboot?

RMarkwald said:
Are you using the latest version of fastboot?
Click to expand...
Click to collapse
I tought I do. I mean I could unlock the phone before.. now it says it's unlocked, and If I try to lock it it says it's locked. Device status is locked tho, at least thats what the bootloader says.
Btw when i've relocked the bootloader the phone finally booted up, so the phone is indeed working, but I can't unlock nor lock it, apperently it's both.

target reported max download size of 536870912 bytes
sending 'bootloader_a' (36344 KB)...
OKAY [ 0.901s]
writing 'bootloader_a'...
FAILED (remote: Flashing is not allowed in Lock State)
checking product...
OKAY [ 0.016s]
checking version-bootloader...
FAILED
Device version-bootloader is 'TMZ12bb'.
Update requires 'TMZ20f'.
but when I do unlock comad (dose not matter if oem unlock, or unlock_critical it says failed cuz is unlocked.
It was all working fine (with unlocked bootloader via oem unlock command) until I've tried to flash the P. .then there was at first the wrong bootloader thing, and then I've just unlocked the unlocked bootloader again this time via the critical unlock, and the phone did not load the P it said the console thing.. and the phone didn't want to boot up, until I've flashed oem lock.. it boots up fine, but it's apperently locked and unlocked at the same time, lol. So I cant flash anything..But the phone does work, tho.
So I am basicially back to start, just can't do anything lol!

Bucika said:
I tought I do. I mean I could unlock the phone before.. now it says it's unlocked, and If I try to lock it it says it's locked. Device status is locked tho, at least thats what the bootloader says.
Btw when i've relocked the bootloader the phone finally booted up, so the phone is indeed working, but I can't unlock nor lock it, apperently it's both.
Click to expand...
Click to collapse
You should verify you have the latest version of the Android SDK Platform Tools from here.
Are you running via fastboot the following two commands (back to back)?:
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
From there, proceeding with the instructions on flashing the Android P Dev Preview images (link)?

RMarkwald said:
You should verify you have the latest version of the Android SDK Platform Tools from here.
Are you running via fastboot the following two commands?:
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
From there, proceeding with the instructions on flashing the Android P Dev Preview images (link)?
Click to expand...
Click to collapse
target reported max download size of 536870912 bytes
sending 'bootloader' (36344 KB)...
OKAY [ 0.815s]
writing 'bootloader'...
OKAY [ 0.371s]
finished. total time: 1.194s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.342s]
writing 'radio'...
OKAY [ 0.579s]
finished. total time: 1.930s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Creating filesystem with parameters:
Size: 56946044928
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13902843
Block groups: 425
Reserved block group size: 1024
Created filesystem with 11/3481600 inodes and 264598/13902843 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: TMZ20f
Baseband Version.....: g8998-00202-1801251558
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (40960 KB)...
OKAY [ 0.923s]
writing 'boot'...
OKAY [ 0.377s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.593s]
writing 'system'...
OKAY [ 2.431s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.585s]
writing 'system'...
OKAY [ 2.445s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.252s]
writing 'system'...
OKAY [ 2.438s]
sending sparse 'system' (521136 KB)...
OKAY [ 12.083s]
writing 'system'...
OKAY [ 2.412s]
sending sparse 'system' (109860 KB)...
OKAY [ 2.632s]
writing 'system'...
OKAY [ 0.512s]
sending 'vendor' (374836 KB)...
OKAY [ 8.308s]
writing 'vendor'...
OKAY [ 1.734s]
erasing 'userdata'...
OKAY [ 0.289s]
sending 'userdata' (140898 KB)...
OKAY [ 3.125s]
writing 'userdata'...
OKAY [ 1.517s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 78.718s
Press any key to exit...

I did downloaded the latest one.. where do I need to put it? Even tho I'm pretty sure I do have the latest one, as I use Android Studio daily.. Btw now It did unlocked again with oem unlock..

Bucika said:
I did downloaded the latest one.. where do I need to put it? Even tho I'm pretty sure I do have the latest one, as I use Android Studio daily.. Btw now It did unlocked again with oem unlock..
Click to expand...
Click to collapse
Once you have extracted the factory image, place all of the extracted contents in the platform-tools folder. Like in the pic, then open up the command prompt on the platform-tools folder :good:

Badger50 said:
Once you have extracted the factory image, place all of the extracted contents in the platform-tools folder. Like in the pic, then open up the command prompt on the platform-tools folder :good:
Click to expand...
Click to collapse
You sir, are a Legend! :good::highfive:
Saved me!! This is absolutely the first time something like that happened to me in years of owning and tinkering with phones.
Thank you once again.

Bucika said:
You sir, are a Legend! :good::highfive:
Saved me!! This is absolutely the first time something like that happened to me in years of owning and tinkering with phones.
Thank you once again.
Click to expand...
Click to collapse
Oh please bruh!...legend? No..just old. Just helping out my fellow tech brothers/sisters to keep more hair on their heads, and not turn phones into desktop paperweights! ???

Pixel 2 XL Android 10 Bootloop

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