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

Needing help restoring phone!!

While I was attempting to flash the Nitrogen ROM I was having issues and ended up wiping my SD card. I got some help with restoring the ROM but realized I had flashed the wrong factory image along the way. I flashed the Fi image. So, as advised by the individual helping me, I tried flashing the correct factory files and I now cannot get past the white startup screen that says Google and shows the boot loader unlocked icon. I've tried the full factory restore and I get the same result. Was hoping I could get some help here.
This is what it sends back to me after I flash-all.bat
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N950U using Tapatalk

I would suggest that you read and follow this Guide.
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Great Solid Info and you should be able to figure it out.
Good luck

chazall1 said:
I would suggest that you read and follow this Guide.
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Great Solid Info and you should be able to figure it out.
Good luck
Click to expand...
Click to collapse
While I do appreciate the advice, that's where I was when I was told to create a new post here. I've already done those steps and nothing.
Sent from my SM-N950U using Tapatalk

brackett5 said:
While I do appreciate the advice, that's where I was when I was told to create a new post here. I've already done those steps and nothing.
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
This has saved my bacon more than once since Version 1:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Make extremely sure that your ADB/fastboot tools are up to date like today.

So...going off of what I was saying in [GUIDE] Unlock/Flash/Root for Pixel 2 XL (taimen) post #1753 (which can be found HERE), I'd like to try resetting/reformatting your system partition. The failure/error stated that it couldn't "determine partition type". I'm hoping by reformatting things, it'll set it correctly to that partition type it wants...
So, if you can prepare it as if you were going to install/flash a Full Factory image -- phone in bootloader mode, command prompt/powershell open, your platform-tools directory open (make sure it is the latest most up-to-date version of the platform-tools) where it shows fastboot and adb -- please input the following commands:
Code:
fastboot --version
*to make sure fastboot is working and to establish a connection
next I want to confirm some information... enter the command:
Code:
fastboot getvar all
*this will show which partitions aren't in the right format and what format we should reformat it in...
please copy and paste here (preferably in the CODE html tags) what it all returns...
Good luck to ya!
Also, @brackett5, you should request a forum moderator/administrator to move this to the Q&A section (I forgot to mention this when advising how to set up this thread) instead of this section... If anything and if any mods are listening, I concur in moving this to the Q&A section as @Az Biker mentioned in this post...Unless you would want brackett5 to create a whole new thread in that section, but leaving any/all the progress made here in this one.........

Sorry about that. I'll have to wait to see if anything works. I managed to also dump over my fiancees vase over into my laptop.
Sent from my SM-N950U using Tapatalk

This will be moved to the Help, Q & A section, as only Roms, Kernels, Recoveries, and other Mods currently being developed belong in this section, (as the title of this section suggests)

brackett5 said:
Sorry about that. I'll have to wait to see if anything works. I managed to also dump over my fiancees vase over into my laptop.
Click to expand...
Click to collapse
Eeek! I know I've been there! (not necessarily a vase but still...) Take ur time to get back here for ur issue after dealing with ur fiance, vase, and laptop...:silly:
Az Biker said:
This will be moved to the Help, Q & A section, as only Roms, Kernels, Recoveries, and other Mods currently being developed belong in this section, (as the title of this section suggests)
Click to expand...
Click to collapse
Again, you're the best! Thanks!
Sent from my Google Pixel 2 XL using XDA Labs

simplepinoi177 said:
So...going off of what I was saying in [GUIDE] Unlock/Flash/Root for Pixel 2 XL (taimen) post #1753 (which can be found HERE), I'd like to try resetting/reformatting your system partition. The failure/error stated that it couldn't "determine partition type". I'm hoping by reformatting things, it'll set it correctly to that partition type it wants...
So, if you can prepare it as if you were going to install/flash a Full Factory image -- phone in bootloader mode, command prompt/powershell open, your platform-tools directory open (make sure it is the latest most up-to-date version of the platform-tools) where it shows fastboot and adb -- please input the following commands:
Code:
fastboot --version
*to make sure fastboot is working and to establish a connection
next I want to confirm some information... enter the command:
Code:
fastboot getvar all
*this will show which partitions aren't in the right format and what format we should reformat it in...
please copy and paste here (preferably in the CODE html tags) what it all returns...
Good luck to ya!
Also, @brackett5, you should request a forum moderator/administrator to move this to the Q&A section (I forgot to mention this when advising how to set up this thread) instead of this section... If anything and if any mods are listening, I concur in moving this to the Q&A section as @Az Biker mentioned in this post...Unless you would want brackett5 to create a whole new thread in that section, but leaving any/all the progress made here in this one.........
Click to expand...
Click to collapse
Sorry, I have to send pics, I'm at work and won't connect to their WiFi.
Sent from my SM-N950U using Tapatalk

I know you're at work and things might not be all too flexible or available, but if you can temp boot into TWRP, do an Advanced Wipe of Dalvik / ART Cache, reboot to bootloader, and run the same flash-all.bat and attempt once again to flash the Full Factory image. Please copy and paste anything in the log of the flashing...
Good luck!

simplepinoi177 said:
I know you're at work and things might not be all too flexible or available, but if you can temp boot into TWRP, do an Advanced Wipe of Dalvik / ART Cache, reboot to bootloader, and run the same flash-all.bat and attempt once again to flash the Full Factory image. Please copy and paste anything in the log of the flashing...
Good luck!
Click to expand...
Click to collapse
target reported max download size of 536870912 bytes
sending 'bootloader' (36344 KB)...
OKAY [ 0.915s]
writing 'bootloader'...
OKAY [ 0.563s]
finished. total time: 1.477s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
sending 'radio' (60412 KB)...
OKAY [ 1.558s]
writing 'radio'...
OKAY [ 0.828s]
finished. total time: 2.464s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
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: 120909180928
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29518843
Block groups: 901
Reserved block group size: 1024
Created filesystem with 11/7380992 inodes and 511380/29518843 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: TMZ12bb
Baseband Version.....: g8998-00202-1802061358
Serial Number........: $%^&*())_))_*^%$####
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
OKAY [ 0.000s]
sending 'boot' (40960 KB)...
OKAY [ 1.125s]
writing 'boot'...
OKAY [ 0.531s]
sending sparse 'system' (524284 KB)...
OKAY [ 21.422s]
writing 'system'...
OKAY [ 2.203s]
sending sparse 'system' (524284 KB)...
OKAY [ 21.047s]
writing 'system'...
OKAY [ 2.219s]
sending sparse 'system' (524284 KB)...
OKAY [ 20.871s]
writing 'system'...
OKAY [ 2.203s]
sending sparse 'system' (411388 KB)...
OKAY [ 16.320s]
writing 'system'...
OKAY [ 1.734s]
sending 'vendor' (354904 KB)...
OKAY [ 9.344s]
writing 'vendor'...
OKAY [ 1.500s]
erasing 'userdata'...
OKAY [ 1.531s]
sending 'userdata' (144997 KB)...
OKAY [ 3.734s]
writing 'userdata'...
OKAY [ 1.672s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 107.614s
Press any key to exit...
Same results as before. It did let me boot into twrp though.

ok, so I decided to check if ADB is picking up my device and again, its not reading it. I checked it earlier and it was. Its not saying outdated, but when I type the cmd adb devices, it doesn't list it.

brackett5 said:
target reported max download size of 536870912 bytes
sending 'bootloader' (36344 KB)...
OKAY [ 0.915s]
writing 'bootloader'...
OKAY [ 0.563s]
finished. total time: 1.477s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
sending 'radio' (60412 KB)...
OKAY [ 1.558s]
writing 'radio'...
OKAY [ 0.828s]
finished. total time: 2.464s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
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: 120909180928
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29518843
Block groups: 901
Reserved block group size: 1024
Created filesystem with 11/7380992 inodes and 511380/29518843 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: TMZ12bb
Baseband Version.....: g8998-00202-1802061358
Serial Number........: $%^&*())_))_*^%$####
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
OKAY [ 0.000s]
sending 'boot' (40960 KB)...
OKAY [ 1.125s]
writing 'boot'...
OKAY [ 0.531s]
sending sparse 'system' (524284 KB)...
OKAY [ 21.422s]
writing 'system'...
OKAY [ 2.203s]
sending sparse 'system' (524284 KB)...
OKAY [ 21.047s]
writing 'system'...
OKAY [ 2.219s]
sending sparse 'system' (524284 KB)...
OKAY [ 20.871s]
writing 'system'...
OKAY [ 2.203s]
sending sparse 'system' (411388 KB)...
OKAY [ 16.320s]
writing 'system'...
OKAY [ 1.734s]
sending 'vendor' (354904 KB)...
OKAY [ 9.344s]
writing 'vendor'...
OKAY [ 1.500s]
erasing 'userdata'...
OKAY [ 1.531s]
sending 'userdata' (144997 KB)...
OKAY [ 3.734s]
writing 'userdata'...
OKAY [ 1.672s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 107.614s
Press any key to exit...
Same results as before. It did let me boot into twrp though.
Click to expand...
Click to collapse
...and u did this after wiping the cache in TWRP? And...just to confirm...you are using the most up to date platform-tools? Maybe re download them just in case...
Sent from my Google Pixel 2 XL using XDA Labs

simplepinoi177 said:
...and u did this after wiping the cache in TWRP? And...just to confirm...you are using the most up to date platform-tools? Maybe re download them just in case...
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
So, I've been doing some research and I was wondering; I had a version of ADB that I installed for use with Andromeda for my note 8, could this be interfering with it? I heard I have to remove it from my computer, but I've deleted it so I wonder how to do so.
Sent from my SM-N950U using Tapatalk

I downloaded the one you provided.
simplepinoi177 said:
...and u did this after wiping the cache in TWRP? And...just to confirm...you are using the most up to date platform-tools? Maybe re download them just in case...
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Sent from my SM-N950U using Tapatalk

simplepinoi177 said:
...and u did this after wiping the cache in TWRP? And...just to confirm...you are using the most up to date platform-tools? Maybe re download them just in case...
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
It changed!!!!
Sent from my SM-N950U using Tapatalk

brackett5 said:
So, I've been doing some research and I was wondering; I had a version of ADB that I installed for use with Andromeda for my note 8, could this be interfering with it? I heard I have to remove it from my computer, but I've deleted it so I wonder how to do so.
Click to expand...
Click to collapse
Sorry...in the midst of a road trip...
I know I mentioned before to use the most up to date ADB/platform-tools (it's what causes like 80% of the troubles in this device's forum). But YES use a different ADB! And the most up to date one (r27.0.1) at that...
but yea changing this and using the URL I have might (or a good chance to) bear a different outcome...
Sent from my Google Pixel 2 XL using XDA Labs

Upon first glance, it looks like you have two things going on;
1) your files for flashing in fastboot are possibly not all in the correct platform tools folder with the fastboot application
your TWRP.IMG file, flash-all.bat, and your factory image files ALL need to be in the same platform tools folder as the fastboot application (.exe)
2) your SDK tools are the latest and greatest, you need to switch your USB cable (2.0 to 3.0 or 3.0 to 2.0) or change USB ports.
Try these things, report back

Az Biker said:
Upon first glance, it looks like you have two things going on;
1) your files for flashing in fastboot are possibly not all in the correct platform tools folder with the fastboot application
your TWRP.IMG file, flash-all.bat, and your factory image files ALL need to be in the same platform tools folder as the fastboot application (.exe)
2) your SDK tools are the latest and greatest, you need to switch your USB cable (2.0 to 3.0 or 3.0 to 2.0) or change USB ports.
Try these things, report back
Click to expand...
Click to collapse
They are all in the same folder. The flash-all.bat is in a sub folder in the platform tools. I'll try and send a video or pictures of howy set up is later.
Sent from my SM-N950U using Tapatalk

Az Biker said:
Upon first glance, it looks like you have two things going on;
1) your files for flashing in fastboot are possibly not all in the correct platform tools folder with the fastboot application
your TWRP.IMG file, flash-all.bat, and your factory image files ALL need to be in the same platform tools folder as the fastboot application (.exe)
2) your SDK tools are the latest and greatest, you need to switch your USB cable (2.0 to 3.0 or 3.0 to 2.0) or change USB ports.
Try these things, report back
Click to expand...
Click to collapse
You are my HERO!!!!!!!!!
Sent from my SM-N950U using Tapatalk

Bootloop after Android 10 OTA uodate!

I just received my Android 10 update and after the update when it asked to reboot I tapped reboot and now it has been stuck in a continuous bootloop. My phone was not rooted or modded in any way. I was able to boot into the recovery selection menu but cant go into the actual recovery (it just says "no item" when I select recovery).
Any help/suggestions?

You can reflash the ROM using the full OTA package, as is stated by Google in https://developers.google.com/android/ota : This page contains full OTA update packages that allow you to restore your Nexus or Pixel device's original factory firmware. You will find these files useful if you have experienced a failure to take an OTA. This has the same effect as flashing the corresponding factory image, but without the need to wipe the device or unlock the bootloader." You also have in that page instructions of the whole process.
All you need to do is reboot into recovery, enter adb sideload mode from whitin it and send the zip OTA file using your PC and adb. Download QP1A.190711.020 version under Pixel 2 XL.
In order to boot into recovery, when you see the Android robot with the "no item" message keep pressed the power button and then short-press volume up until the recovery options show up.
It after that it's still failing, just format within recovery or flash the full firmware stock package.

fdgd1998 said:
You can reflash the ROM using the full OTA package, as is stated by Google in https://developers.google.com/android/ota : This page contains full OTA update packages that allow you to restore your Nexus or Pixel device's original factory firmware. You will find these files useful if you have experienced a failure to take an OTA. This has the same effect as flashing the corresponding factory image, but without the need to wipe the device or unlock the bootloader." You also have in that page instructions of the whole process.
All you need to do is reboot into recovery, enter adb sideload mode from whitin it and send the zip OTA file using your PC and adb. Download QP1A.190711.020 version under Pixel 2 XL.
In order to boot into recovery, when you see the Android robot with the "no item" message keep pressed the power button and then short-press volume up until the recovery options show up.
It after that it's still failing, just format within recovery or flash the full firmware stock package.
Click to expand...
Click to collapse
thank you for the helpful reply
i had already started the process and have already downloaded all the files
but i cant unlock the bootloader as it says in the tutorial
am i doing something wrong? or is there any way to flash without unlocking the bootloader?
Edit: I dont have the "oem unlock" option turned on.
PLZ HELP

areebiqbal said:
thank you for the helpful reply
i had already started the process and have already downloaded all the files
but i cant unlock the bootloader as it says in the tutorial
am i doing something wrong? or is there any way to flash without unlocking the bootloader?
Edit: I dont have the "oem unlock" option turned on.
PLZ HELP
Click to expand...
Click to collapse
Are you flashing the OTA or the full firmware? For the OTA bootloader unlock isn't necessary.
And in the instructions are stated the opposite, you must have misread it.

fdgd1998 said:
Are you flashing the OTA or the full firmware? For the OTA bootloader unlock isn't necessary.
And in the instructions are stated the opposite, you must have misread it.
Click to expand...
Click to collapse
hi, so luckily i had oem unlocking checked before this happened, but after the october update ive been stuck in bootloop.
ive tried both sideloading the ota in recovery, and also full firmware flash via fastboot.
after several attempts at both, i can't seem to access the recovery and bootloop persists.
any ideas?
[pixel sailfish never been rooted]

ku81na said:
hi, so luckily i had oem unlocking checked before this happened, but after the october update ive been stuck in bootloop.
ive tried both sideloading the ota in recovery, and also full firmware flash via fastboot.
after several attempts at both, i can't seem to access the recovery and bootloop persists.
any ideas?
[pixel sailfish never been rooted]
Click to expand...
Click to collapse
Have you looked into the Dueces recovery scrip?
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

no dice. appreciate the suggestion though

ku81na said:
no dice. appreciate the suggestion though
Click to expand...
Click to collapse
if you can confirm a couple things for me....
Are you actually getting into the recovery, but not seeing any "items"; because in stock recovery, you just see a broken/dead android image, and only get selections revealed/not-hidden but holding the volume-up & power button at the same time momentarily.
But, then again, you claim that you have attempted to "sideload the ota in recovery", so I imagine you already did this…but then, again again, you don’t describe what “error” or outcome actually happened and it could possibly be that, when you attempted, you just couldn’t or didn’t know how to get into the stock recovery…
Also, the recovery resides in the boot partition; I suggest you download the Full Factory image file (from the Google Developers site), extract it until you can find the boot.img, then manually flash it to overwrite and maybe fix the boot & recovery; to further explain, copy the extracted “boot.img” file to platform-tools folder where adb and fastboot reside, then run the command “fastboot flash boot boot.img” – although, if the flash-all is successfully executed, it would be doing this anyways…..
Which brings me to my next thing…if you could edit the “flash-all.bat” file and remove the word “exit” at the end – and for that matter, if you wish to save your data, remove the -w as well – and if you could please copy the output/log of you running the flash-all; usually this resolves everything & it all, so maybe it’s here that something is going wrong…
And running Deuce’s famous rescue script has saved/recovered countless people and their device (taimen)…it definitely is a good idea to attempt it…
But, then again, this is assuming that you made sure to run (and successfully execute) the fastboot command “fastboot flashing unlock” and/or (depending on your bootloader version) “fastboot flashing unlock_critical”.
Good luck, hopefully you can get back to me/us on some of this stuff, and hopefully all this ends up being helpful…

simplepinoi177 said:
if you can confirm a couple things for me....
Are you actually getting into the recovery, but not seeing any "items"; because in stock recovery, you just see a broken/dead android image, and only get selections revealed/not-hidden but holding the volume-up & power button at the same time momentarily.
But, then again, you claim that you have attempted to "sideload the ota in recovery", so I imagine you already did this…but then, again again, you don’t describe what “error” or outcome actually happened and it could possibly be that, when you attempted, you just couldn’t or didn’t know how to get into the stock recovery…
Also, the recovery resides in the boot partition; I suggest you download the Full Factory image file (from the Google Developers site), extract it until you can find the boot.img, then manually flash it to overwrite and maybe fix the boot & recovery; to further explain, copy the extracted “boot.img” file to platform-tools folder where adb and fastboot reside, then run the command “fastboot flash boot boot.img” – although, if the flash-all is successfully executed, it would be doing this anyways…..
Which brings me to my next thing…if you could edit the “flash-all.bat” file and remove the word “exit” at the end – and for that matter, if you wish to save your data, remove the -w as well – and if you could please copy the output/log of you running the flash-all; usually this resolves everything & it all, so maybe it’s here that something is going wrong…
And running Deuce’s famous rescue script has saved/recovered countless people and their device (taimen)…it definitely is a good idea to attempt it…
But, then again, this is assuming that you made sure to run (and successfully execute) the fastboot command “fastboot flashing unlock” and/or (depending on your bootloader version) “fastboot flashing unlock_critical”.
Good luck, hopefully you can get back to me/us on some of this stuff, and hopefully all this ends up being helpful…
Click to expand...
Click to collapse
yes i've tried everything you've suggested (flashing boot separately/removing exit from flash-all/running deuces script), however i haven't been able to access the recovery since i last messaged so i haven't been able to retry an ota flash from recovery. (the screen is all black and a green line of fuzz blinks across the middle of the screen when holding power and volume up) i did however get into it successfully once, and when i did there were no errors at all.
the strange thing is there are no errors when flashing either. it just does not get passed "Google" without rebooting. i just tried another flash-all after flashing unlock & unlock_critical so here is the full log in case im missing something:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32480 KB)...
OKAY [ 0.847s]
writing 'bootloader_b'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.107s]
finished. total time: 4.965s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_b' (57156 KB)...
OKAY [ 1.434s]
writing 'radio_b'...
OKAY [ 0.458s]
finished. total time: 1.903s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.055s
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-1908071822
Baseband Version.....: 8996-130361-1905270421
Serial Number........: FXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.046s]
checking version-baseband...
OKAY [ 0.046s]
sending 'boot_b' (30793 KB)...
OKAY [ 0.797s]
writing 'boot_b'...
OKAY [ 0.294s]
erasing 'system_b'...
OKAY [ 0.316s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 13.692s]
writing 'system_b' 1/4...
OKAY [ 3.460s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 13.802s]
writing 'system_b' 2/4...
OKAY [ 3.481s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.816s]
writing 'system_b' 3/4...
OKAY [ 3.451s]
sending sparse 'system_b' 4/4 (461052 KB)...
OKAY [ 11.950s]
writing 'system_b' 4/4...
OKAY [ 3.087s]
erasing 'system_a'...
OKAY [ 0.246s]
sending 'system_a' (298348 KB)...
OKAY [ 7.005s]
writing 'system_a'...
OKAY [ 2.036s]
erasing 'vendor_b'...
OKAY [ 0.112s]
sending 'vendor_b' (259272 KB)...
OKAY [ 6.400s]
writing 'vendor_b'...
OKAY [ 1.747s]
Setting current slot to 'b'...
OKAY [ 0.081s]
erasing 'userdata'...
OKAY [ 1.853s]
sending 'userdata' (138957 KB)...
OKAY [ 3.089s]
writing 'userdata'...
OKAY [ 1.293s]
rebooting...
finished. total time: 92.497s
Press any key to exit...

ku81na said:
yes i've tried everything you've suggested (flashing boot separately/removing exit from flash-all/running deuces script), however i haven't been able to access the recovery since i last messaged so i haven't been able to retry an ota flash from recovery. (the screen is all black and a green line of fuzz blinks across the middle of the screen when holding power and volume up) i did however get into it successfully once, and when i did there were no errors at all.
the strange thing is there are no errors when flashing either. it just does not get passed "Google" without rebooting. i just tried another flash-all after flashing unlock & unlock_critical so here is the full log in case im missing something:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32480 KB)...
OKAY [ 0.847s]
writing 'bootloader_b'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.107s]
finished. total time: 4.965s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_b' (57156 KB)...
OKAY [ 1.434s]
writing 'radio_b'...
OKAY [ 0.458s]
finished. total time: 1.903s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.055s
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-1908071822
Baseband Version.....: 8996-130361-1905270421
Serial Number........: FXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.046s]
checking version-baseband...
OKAY [ 0.046s]
sending 'boot_b' (30793 KB)...
OKAY [ 0.797s]
writing 'boot_b'...
OKAY [ 0.294s]
erasing 'system_b'...
OKAY [ 0.316s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 13.692s]
writing 'system_b' 1/4...
OKAY [ 3.460s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 13.802s]
writing 'system_b' 2/4...
OKAY [ 3.481s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.816s]
writing 'system_b' 3/4...
OKAY [ 3.451s]
sending sparse 'system_b' 4/4 (461052 KB)...
OKAY [ 11.950s]
writing 'system_b' 4/4...
OKAY [ 3.087s]
erasing 'system_a'...
OKAY [ 0.246s]
sending 'system_a' (298348 KB)...
OKAY [ 7.005s]
writing 'system_a'...
OKAY [ 2.036s]
erasing 'vendor_b'...
OKAY [ 0.112s]
sending 'vendor_b' (259272 KB)...
OKAY [ 6.400s]
writing 'vendor_b'...
OKAY [ 1.747s]
Setting current slot to 'b'...
OKAY [ 0.081s]
erasing 'userdata'...
OKAY [ 1.853s]
sending 'userdata' (138957 KB)...
OKAY [ 3.089s]
writing 'userdata'...
OKAY [ 1.293s]
rebooting...
finished. total time: 92.497s
Press any key to exit..
.
Click to expand...
Click to collapse
Curious....
I would suggest you try Deuce's script -- again, it has assisted and recovered countless taimens. And, if that doesn't help, I would suggest you try temporarily booting into TWRP custom recovery. If you do not know how to do that, download the TWRP .img file from twrp.me (you'll have to direct yourself to the Google Pixel 2 XL [taimen] section), put it where you put the flash-all and other image files, then run the fastboot command "fastboot boot twrp.img" (replace "twrp.img" with the actual filename of the twrp image file). There you can erase/format the system and/or other partitions, or even "repair" the filesystem! You can also run adb commands, so you might have some luck and be able to install/flash an OTA image file as well....
Good luck and hope this helps...!

[GUIDE]T-Mobile Brand Conversion to Global Firmware [Updated]

nolimit78 pieced together a lot of good info and I just wanted to post a revision on that with some clarification for those who may not be too familiar with this process. The link to this is at the bottom.
For the record, I performed this on a OnePlus 7T (Model HD1907), Build 10.0.12.HD63CB, Android Version 10
1. Update System Software
Ensure the phone is on the latest system software (which should be at least 10.0.6) to make the conversion easier. This will keep you from having to step through an intermediate firmware version:
In the Settings, go to System > System Update and click 'Check for update' or resume/install an ongoing update
2. SIM Unlock (Carrier Unlock)
This requires putting in a request with T-Mobile and took about 3 days for me.
Request SIM unlock from T-Mobile on Facebook (message them from here: https://www.facebook.com/TMobile/)
They will ask for your IMEI and phone number, then verify that you are not on a contract.
I've heard results may vary with this, but I didn't have any issue and I did two phones
Once they confirm it is unlocked, performed the following to unlock on the phone:
In Settings, go to Wi-Fi & internet > SIM & network > Network Unlock.
Choose unlock type: Permanent Unlock
3. Boot Unlock (Bootloader Unlock)
Enable Developer Settings:
Go to Settings > About Phone
Tap on "Build Number" 7 times and you will see a message at the bottom of the screen the developer options are enabled
Use Developer Settings to enable OEM Unlock:
Go to Settings > System > Developer options
Enable "OEM unlocking" (shown disabled below)
Get IMEI by dialing *#06# or in Settings > About Phone > Status
Enter fastboot mode to get the unlock code:
If you haven't already, install the OnePlus 7T USB Drivers by connecting it to your PC while the phone is powered on normally. It will mount a drive for "OnePlus Drivers" from which you can run the driver installation. Note: For me, the installer got stuck at the 'executing commands' step and I had to restart the PC and reinstall, then it installed quickly.
Download “fastboot_windows.zip” and unzip it on your computer.
Power off the OnePlus 7T.
Press and hold the “Volume +” and “Volume -” and then "Power" keys until the “fastboot mode” menu appears
With this menu open on the phone, connect the phone to your computer via USB
Open a command prompt (not Powershell) on Windows, switch to the fastboot directory and run it using the following commands:
Note: If it says 'waiting for device', then you need to install the OnePlus USB drivers or determine why the driver isn't working
Code:
cd <fastboot directory>
fastboot.exe oem get_unlock_code
Submit the the information found above at this link and wait 7 days for them to send you the unlock file: https://www.oneplus.com/unlock_token
THESE NEXT STEPS WILL WIPE YOUR USER DATA! BE SURE YOU HAVE BACKED UP YOUR DATA BEFORE DOING THIS!
After receiving the unlock_code.bin file from OnePlus, put them in the fastboot directory and run the following commands:
Code:
fastboot flash cust-unlock unlock_code.bin
fastboot oem unlock
A warning will appear on the screen after the last command explaining that once the boot loader is unlocked and a custom OS is installed, they cannot verify the integrity of the system. Use the “Volume +” and “Volume -” buttons to highlight the unlock the bootloader option, then press "Power" button to select it. The phone will wipe your user data and then reboot. It may take a while to reboot while it displays the "T-Mobile" loading screen. Let it sit at least 10 minutes before trying to reboot.
Note: Your device will display a warning at boot until you re-lock the bootloader. Many have recommended not re-locking the bootloader due to various issues with it.
4. Installing Global Firmware
For this step, you *might* need adb tools installed. I think that everything you need is contained in the ROM archive from step 1 below, but if you get an error, download SDK Platform Tools for Windows from this link and install it.
Download the newest *GLOBAL-OnePlus7TOxygen*.zip from this link: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7T/
Extract the contents of the zip file for use later.
Return to the fastboot menu on the phone:
Power off the OnePlus 7T.
Press and hold the “Volume +” and “Volume -” and then "Power" keys until the “fastboot mode” menu appears
Connect your Phone to the PC via USB.
Open a command prompt and change into the directory for the *GLOBAL-OnePlus7TOxygen*.zip
From the command prompt, run the flash-all.bat file
Note: At one point, the phone will reboot and mine showed a menu with a language selection screen instead of the normal Fastboot menu. DON'T TOUCH THE PHONE, BE SURE TO STAY AT THE LANGUAGE SELECTION SCREEN. I clicked through it and went back to the fastboot menu and that made everything else fail.
FYI, I received the following errors, but it seemed to work:
Code:
# Error 1D:\Downloads\OnePlus 7T Unlock\Global Fastboot ROM (Latest)\10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT>fastboot flash reserve reserve.img
Sending 'reserve' (250164 KB) OKAY [ 5.863s]
Writing 'reserve' FAILED (remote: '(reserve_b) No such partition')
fastboot: error: Command failed
# Error 2
D:\Downloads\OnePlus 7T Unlock\Global Fastboot ROM (Latest)\10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT>fastboot flash opproduct opproduct.img
Invalid sparse file format at header magic
Sending sparse 'opproduct_b' 1/1 (391796 KB) OKAY [ 9.447s]
Writing 'opproduct_b' OKAY [ 3.180s]
Finished. Total time: 14.376s
# Error 3
D:\Downloads\OnePlus 7T Unlock\Global Fastboot ROM (Latest)\10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT>fastboot flash system system.img
Invalid sparse file format at header magic
Resizing 'system_b' OKAY [ 0.005s]
Sending sparse 'system_b' 1/5 (523136 KB) OKAY [ 12.658s]
Writing 'system_b' OKAY [ 3.076s]
Sending sparse 'system_b' 2/5 (523148 KB) OKAY [ 12.544s]
Writing 'system_b' OKAY [ 3.071s]
Sending sparse 'system_b' 3/5 (523640 KB) OKAY [ 12.597s]
Writing 'system_b' OKAY [ 3.074s]
Sending sparse 'system_b' 4/5 (524256 KB) OKAY [ 12.526s]
Writing 'system_b' OKAY [ 3.083s]
Sending sparse 'system_b' 5/5 (197932 KB) OKAY [ 4.786s]
Writing 'system_b' OKAY [ 1.364s]
Finished. Total time: 77.293s
# Error 4
D:\Downloads\OnePlus 7T Unlock\Global Fastboot ROM (Latest)\10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT>fastboot flash vendor vendor.img
Invalid sparse file format at header magic
Resizing 'vendor_b' OKAY [ 0.005s]
Sending sparse 'vendor_b' 1/2 (523681 KB) OKAY [ 12.737s]
Writing 'vendor_b' OKAY [ 3.065s]
Sending sparse 'vendor_b' 2/2 (427876 KB) OKAY [ 10.438s]
Writing 'vendor_b' OKAY [ 2.626s]
Finished. Total time: 32.395s
Once the phone reboots, you should see the OnePlus boot-up screen instead of the T-Mobile one and all should be working.
References
Retrieve unlock token: https://www.oneplus.com/unlock_token
Unlocking bootloader: https://support.oneplus.com/app/ans...-to-unlock-bootloader-for-oneplus-smart-phone
Install process: https://forum.xda-developers.com/t/...conversion-to-rooted-global-firmware.4019495/

@hypercoyote THREAD CLOSED as a subject matter related thread, what you correctly indicated, already exists: https://forum.xda-developers.com/t/...conversion-to-rooted-global-firmware.4019495/. Your post has been copied to there.
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse
I acknowledge your positive intentions.