Need a Bootloader - Google Pixel 2 XL Questions & Answers

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

Related

Cannot install stock rom: FAILED (remote: data too large)

I tried installing Cyanogenmod on a Nexus 5X, and it didn't work, so now I'm trying to install the stock rom from this site: https://developers.google.com/android/images#bullhead.
I'm doing this on Ubuntu 15.10. When I run the flash-all.sh script (on any of them), I get this output:
target reported max download size of 536870912 bytes
sending 'bootloader' (4382 KB)...
OKAY [ 0.195s]
writing 'bootloader'...
OKAY [ 0.077s]
finished. total time: 0.272s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
target reported max download size of 536870912 bytes
sending 'radio' (56614 KB)...
OKAY [ 1.715s]
writing 'radio'...
OKAY [ 0.338s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: BHZ10i
Baseband Version.....: M8994F-2.6.22.0.56
Serial Number........: 00a9164559592811
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
OKAY [ 0.020s]
sending 'boot' (11469 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.073s]
sending 'recovery' (12521 KB)...
OKAY [ 0.393s]
writing 'recovery'...
OKAY [ 0.092s]
erasing 'system'...
OKAY [ 0.089s]
sending 'system' (1950236 KB)...
FAILED (remote: data too large)
finished. total time: 1.210s
I'm not seeing many resources online about this error. The only thing I've seen is to update fastboot, but I've already got the latest installed with this ppa: http://askubuntu.com/questions/34702/how-do-i-set-up-android-adb
Is there anything that I can do to get it working correctly?
adanedhel728 said:
I tried installing Cyanogenmod on a Nexus 5X, and it didn't work, so now I'm trying to install the stock rom from this site: https://developers.google.com/android/images#bullhead.
I'm doing this on Ubuntu 15.10. When I run the flash-all.sh script (on any of them), I get this output:
target reported max download size of 536870912 bytes
sending 'bootloader' (4382 KB)...
OKAY [ 0.195s]
writing 'bootloader'...
OKAY [ 0.077s]
finished. total time: 0.272s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
target reported max download size of 536870912 bytes
sending 'radio' (56614 KB)...
OKAY [ 1.715s]
writing 'radio'...
OKAY [ 0.338s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: BHZ10i
Baseband Version.....: M8994F-2.6.22.0.56
Serial Number........: 00a9164559592811
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
OKAY [ 0.020s]
sending 'boot' (11469 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.073s]
sending 'recovery' (12521 KB)...
OKAY [ 0.393s]
writing 'recovery'...
OKAY [ 0.092s]
erasing 'system'...
OKAY [ 0.089s]
sending 'system' (1950236 KB)...
FAILED (remote: data too large)
finished. total time: 1.210s
I'm not seeing many resources online about this error. The only thing I've seen is to update fastboot, but I've already got the latest installed with this ppa: http://askubuntu.com/questions/34702/how-do-i-set-up-android-adb
Is there anything that I can do to get it working correctly?
Click to expand...
Click to collapse
the system image always is too large and usually it gets transferred in smaller pieces automatically. I'd try to flash all the images manually on a Windows mashine, following this guide (section 10).
I did it many times this way without issues.
ulxerker said:
the system image always is too large and usually it gets transferred in smaller pieces automatically. I'd try to flash all the images manually on a Windows mashine, following this guide (section 10).
I did it many times this way without issues.
Click to expand...
Click to collapse
Well, I can't get it working on Windows at all, because the driver won't install. (At least I assume that's the reason why-- The driver won't install and fastboot won't show any devices.)
I tried fixing that, but with no luck.
I did also try section 10 from Ubuntu, with the same results for the system part:
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.284s]
sending sparse 'system' (514493 KB)...
OKAY [ 12.333s]
writing 'system'...
OKAY [ 3.149s]
sending sparse 'system' (514543 KB)...
OKAY [ 12.427s]
writing 'system'...
OKAY [ 3.117s]
sending sparse 'system' (524291 KB)...
FAILED (remote: data too large)
finished. total time: 31.327s
Fastboot is too old. Remove it from system. apt remove android-tools-fastboot . Place fastboot from dl link into a folder where is your system img. Change permissions if needed and exexute it with ./fastboot
https://mega.nz/#!CYYjHYSK!yjhPZ-OYQNhFxq-0JXVibtUps7AwoFDtvk0yPu_194s
Even better is to place fastboot file into a system /bin folder from where you can execute command in any folder.
Best regards.
icrunchbanger said:
Fastboot is too old. Remove it from system. apt remove android-tools-fastboot . Place fastboot from dl link into a folder where is your system img. Change permissions if needed and exexute it with ./fastboot
https://mega.nz/#!CYYjHYSK!yjhPZ-OYQNhFxq-0JXVibtUps7AwoFDtvk0yPu_194s
Even better is to place fastboot file into a system /bin folder from where you can execute command in any folder.
Best regards.
Click to expand...
Click to collapse
My gosh, that finally worked, and I didn't believe it would. I had thought that the one I had gotten from that PPA was the newest, but, apparently not. I actually got it directly from Google (which was a chore in itself, but outside the scope of this thread).
Thank you very much. Now, let's see if I can find out how to mark this as solved...
adanedhel728 said:
My gosh, that finally worked, and I didn't believe it would. I had thought that the one I had gotten from that PPA was the newest, but, apparently not. I actually got it directly from Google (which was a chore in itself, but outside the scope of this thread).
Thank you very much. Now, let's see if I can find out how to mark this as solved...
Click to expand...
Click to collapse
Your welcome. Never trust PPA ?
I got issuse
icrunchbanger said:
Fastboot is too old. Remove it from system. apt remove android-tools-fastboot . Place fastboot from dl link into a folder where is your system img. Change permissions if needed and exexute it with ./fastboot
https://mega.nz/#!CYYjHYSK!yjhPZ-OYQNhFxq-0JXVibtUps7AwoFDtvk0yPu_194s
Even better is to place fastboot file into a system /bin folder from where you can execute command in any folder.
Best regards.
Click to expand...
Click to collapse
Bro link doesnt work, can you sent me app via email: [email protected]
suleymanov5 said:
Bro link doesnt work, can you sent me app via email: [email protected]
Click to expand...
Click to collapse
You can download android tools from Google
https://dl.google.com/android/repository/platform-tools-latest-linux.zip
Also you can check my github for some nifty scripts .
https://github.com/icrunchbanger/android

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.

Trying to flash factory to my unlocked bootloader P2XL. Please help!

I'm trying to flash a factory image. I'm using the guide here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 . I really have no idea what I'm doing wrong... the procedure is so simple, download the factory image and run flash-all.bat It goes, but I get errors. I searched but all I could find was a guy flashing the wrong image. I am using "taimen-opd1.170816.025-factory-907c4030" from https://developers.google.com/android/images. I was on 8.1.1 and want to go back due to multi-touch issues. Below is my log:
target reported max download size of 536870912 bytes
sending 'bootloader' (55680 KB)...
OKAY [ 1.252s]
writing 'bootloader'...
OKAY [ 0.564s]
finished. total time: 104.574s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.358s]
writing 'radio'...
OKAY [ 0.563s]
finished. total time: 1.931s
rebooting into bootloader...
OKAY [ 0.004s]
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...: TMZ10n
Baseband Version.....: g8998-00122-1708311414
Serial Number........: 712KPHG1155193
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
OKAY [ 0.004s]
checking version-baseband...
OKAY [ 0.004s]
sending 'boot' (40960 KB)...
OKAY [ 0.940s]
writing 'boot'...
OKAY [ 0.376s]
sending sparse 'system' (524284 KB)...
OKAY [ 13.421s]
writing 'system'...
OKAY [ 2.436s]
sending sparse 'system' (524284 KB)...
OKAY [ 13.139s]
writing 'system'...
OKAY [ 2.408s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.975s]
writing 'system'...
OKAY [ 2.416s]
sending sparse 'system' (338968 KB)...
OKAY [ 8.364s]
writing 'system'...
OKAY [ 1.568s]
sending 'vendor' (349428 KB)...
OKAY [ 7.941s]
writing 'vendor'...
OKAY [ 1.607s]
erasing 'userdata'...
OKAY [ 0.591s]
sending 'userdata' (140898 KB)...
OKAY [ 3.031s]
writing 'userdata'...
OKAY [ 1.496s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 72.790s
Press any key to exit...
Well, it always happens this way - I create the thread and the issue is instantly fixed. I was using a usb2 hub hearing it was more stable. Remove the hub and flash and it works... FYI if anyone runs into the same issue.
machx1111 said:
Well, it always happens this way - I create the thread and the issue is instantly fixed. I was using a usb2 hub hearing it was more stable. Remove the hub and flash and it works... FYI if anyone runs into the same issue.
Click to expand...
Click to collapse
Glad you got it fixed.
Adb & flashing rules:
1. Connect phone directly to computer. Don't use USB hub
2. Use the USB cable that came with phone, if possible
3. If it still fails, try a different cable or USB port
If adb recognizes the device, that means your adb environment is setup correctly and adb is working. If flashing still fails at this point, that means your cable or port is bad.

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

Categories

Resources