[GUIDE] Unlock/Flash/Root for the Pixel 2 XL (taimen)

[Waxillium]

Pixel XL 2: Thanks for this guide! I followed the steps, and encountered no issues up to the point where I attempted to boot from the patched_boot.img. Now I'm getting a boot loop with "No command". Any advice on how to continue? I'm a little worried because the adb command prompt doesn't see the device... at least it isn't listed under connected devices.

Edit: I managed to get into recovery mode and re-install the OPD1.170816.010 image and it boots fine, phew

 

[pvtjoker42]

so, followed the steps, and tried to flash the patched boot.img and i get "FAILED (remote: flashing is not allowed in Lock State)
Yet if i try and run the fastboot flashing unlock_critical, it comes back saying device already unlocked.

update.. so apparently i had to fastboot flashing unlock, for it to register as unlocked (and redo everything on my phone again) so i'll get back to where i was and see if i'm able to flash from there.

 

[Jchap808]

Unlock Bootloader

Currently unable to unlock the bootloader.

I get stuck at fastboot flashing unlock

Its prompting my a Failed unlock. Any fix?

Looked around seems to be associated with the OEM Unlocking being greyed out.

 

[Golf c]

Currently unable to unlock the bootloader.

I get stuck at fastboot flashing unlock

Its prompting my a Failed unlock. Any fix?

Looked around seems to be associated with the OEM Unlocking being greyed out.

Verizon phone? Cannot be unlocked.

 

[mackentosh]

Followed all steps and I rebooted, it's staying on the boot screen "G" and it's acting like it's loading but it's been on the G screen for 20 mins now. Is that normal?

 

[nathanchance]

Followed all steps and I rebooted, it's staying on the boot screen "G" and it's acting like it's loading but it's been on the G screen for 20 mins now. Is that normal?

Which steps? There are a lot in the OP lol.

Sent from my Pixel 2 XL using XDA Labs

 

[bajasur]

Currently unable to unlock the bootloader.

I get stuck at fastboot flashing unlock

Its prompting my a Failed unlock. Any fix?

Looked around seems to be associated with the OEM Unlocking being greyed out.

This usually means you haven't enabled OEM unlocking developer options first

 

[cmexec]

I did the fastboot flashing unlock and have been using the P2XL unlocked for a couple of weeks, including Nov update sideloaded. In order to use the procedure in OP to Root, will I have to do fastboot flashing unlock_critical, which will wipe the phone (factory reset)?
-Paul

 

[nathanchance]

I did the fastboot flashing unlock and have been using the P2XL unlocked for a couple of weeks, including Nov update sideloaded. In order to use the procedure in OP to Root, will I have to do fastboot flashing unlock_critical, which will wipe the phone (factory reset)?
-Paul

If you only plan to sideload OTAs, you don't need to unlock_critical.

Sent from my Pixel 2 XL using XDA Labs

 

[krash2k]

Hey everyone, when I try to patch taimen-opd1.170816.010-factory-c796ddb4.zip with Magisk Manager it just keeps crashing. It gets to the black screen with the outputs, says "extracting files", then "use boot image: ....", then Magisk Manager keeps stopping [close app].

Tried uninstalling everything, re-downloading the img, clearing the data/cache of magisk, same problem every time.

 

[mackentosh]

Hey everyone, when I try to patch taimen-opd1.170816.010-factory-c796ddb4.zip with Magisk Manager it just keeps crashing. It gets to the black screen with the outputs, says "extracting files", then "use boot image: ....", then Magisk Manager keeps stopping [close app].

Tried uninstalling everything, re-downloading the img, clearing the data/cache of magisk, same problem every time.

You have to extract "taimen-opd1.170816.010-factory-c796ddb4.zip" and find the boot.img then place it on your internal sd

 

[krash2k]

You have to extract "taimen-opd1.170816.010-factory-c796ddb4.zip" and find the boot.img then place it on your internal sd

Yep yep that makes more sense now. That worked.. I flashed the patched_boot.img but now it just hangs at the white "G" screen with the moving progress bar on booting. Doh. ;/

 

[Cowbell_Guy]

If you only plan to sideload OTAs, you don't need to unlock_critical.

What are the downsides of unlocking critical?

 

[mackentosh]

Yep yep that makes more sense now. That worked.. I flashed the patched_boot.img but now it just hangs at the white "G" screen with the moving progress bar on booting. Doh. ;/

That's cause it's been corrupted, I went thru the same thing for like 6 hours. You have to extract the file properly, so you can trash that patched file you currently have and download the image again. Extract it right in the download folder then go in and find the boot img copy it and paste it to your phones SD then go thru Magisk app and patch it. After you do that follow the commands in post. *The main thing that had me screwed up was the fact that the cable that came with phone didn't work as far as communicating with my laptop. I had to go get the cable out my car which was a USB to USB-C cable instead of the USB-C to USB-C cable the phone came with

 

[krash2k]

That's cause it's been corrupted, I went thru the same thing for like 6 hours. You have to extract the file properly, so you can trash that patched file you currently have and download the image again. Extract it right in the download folder then go in and find the boot img copy it and paste it to your phones SD then go thru Magisk app and patch it. After you do that follow the commands in post. *The main thing that had me screwed up was the fact that the cable that came with phone didn't work as far as communicating with my laptop. I had to go get the cable out my car which was a USB to USB-C cable instead of the USB-C to USB-C cable the phone came with

Hmmm.... okay I can try that but right now I just need to figure out how to get this thing to boot again.

I can get to fastboot and I've been trying to use the skipsoft tool kit (I have ultimate) to flash just a stock image so I can boot but it is just fighting for some reason.

 

[mackentosh]

Make sure you have the proper cable, if skipsoft says bootloader locked even tho it's unlocked then it's the cable.

When you open skipsoft select #4 "Root/Unroot/Disable Ecryption/flash stock boot/check root status" then select #5 Flash stock boot/Recovery image. If your cable works you shouldn't have any problems and that'll boot up your phone

 

[slaydog]

Hmmm.... okay I can try that but right now I just need to figure out how to get this thing to boot again.

I can get to fastboot and I've been trying to use the skipsoft tool kit (I have ultimate) to flash just a stock image so I can boot but it is just fighting for some reason.

Maybe try to push the original, non modified boot.img to your phone go get it to boot first..?

Sent from my Pixel 2 XL using XDA Free mobile app

 

[krash2k]

Maybe try to push the original, non modified boot.img to your phone go get it to boot first..?

Tried doing this.. still wouldn't boot. I don't have anything on the phone that I'm trying to save so at this point I don't mind just wiping it and starting fresh just to get it working again.

I just tried downloading the factory image and using the flash-all script to just start over but now it's just saying my device is corrupt and hangs at the google splash screen. Was hoping that was going to work because now I'm feeling out of options.

EDIT: I'm going to start a new thread in the Q&A forum because I feel like I'm hijacking this guide with stuff that isn't really related to it.

 

[cmexec]

If you only plan to sideload OTAs, you don't need to unlock_critical.

Sent from my Pixel 2 XL using XDA Labs

Okay thanks. So, rooting will not require bootloader install and therefore unlock_critical?

Sent from my Pixel 2 XL using Tapatalk

 

[nathanchance]

Okay thanks. So, rooting will not require bootloader install and therefore unlock_critical?

Sent from my Pixel 2 XL using Tapatalk

No, it does not. If you can afford an unlock_critical (as in wiping and setting up again), I would recommend it but if not, you'll most likely never run into any issues.