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

[KennyG123]

@nathanchance
It may be important to note in the OP that sideloading OTA's does not require an unlocked bootloader nor root.
Thanks for this thread! :good:

 

[nathanchance]

@nathanchance
It may be important to note in the OP that sideloading OTA's does not require an unlocked bootloader nor root.
Thanks for this thread! :good:

Oh yeah duh :silly: will update shortly, thanks Kenny!

Sent from my Pixel 2 XL using XDA Labs

 

[iamjimmy]

Not to hijack the thread, but is is possible to add certain features which are available in Custom ROMs, manually. Assuming Root.
Are there any apps or other ways to edit files and get these features. Ex:

1) Navigation bar Tuner to add and change placement of Nav buttons (the app in play store only allows VERY limited customization).
2) Double tap lockscreen/nav bar to sleep
3) Long press power menu options.
4) Kill back button etc

 

[Scettles]

I really dont want to flash to stock lol. I dont want to go through the backing up and what not... lol is that okay? how would i do it without reverting back to stock

 

[Veritech]

So if we're on September 8.0 and have rooted with Magisk, how do we go about implementing the November OTA? The only module from Magisk I installed was the tethering one. I have not installed TWRP Alpha (if it's needed) but I have already downloaded the OTA from Google's website. Thanks in advance!

 

[nathanchance]

So if we're on September 8.0 and have rooted with Magisk, how do we go about implementing the November OTA? The only module from Magisk I installed was the tethering one. I have not installed TWRP Alpha (if it's needed) but I have already downloaded the OTA from Google's website. Thanks in advance!

Restore the stock boot image in Magisk, do the sideload using the steps in the OP, patch the boot image with Magisk, then flash it.

Alternatively, you can following Magisk's OTA guide: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

 

[the1dynasty]

@nathanchance I have a Pixel 2 XL that I am sending back to Google because I got the replacement device today... I was on the dev preview for 8.1 and wanted to return it to stock at least for them... I ran the following:

fastboot flashing unlock

followed by

fastboot flashing unlock_critical

I then flashed the Sept release 8.0.0 (OPD1.170816.010, Sep 2017) and after it flashed successfully, I ran the following commands

fastboot flashing lock

After a quick erase, the phone got stuck in a bootloop... And because I had never seen the _critical command... I ran just for good measure...

fastboot flashing lock_critical

I keep getting an error that the system may be corrupt and it's stuck in a bootloop... I started over with unlocking again and then I flashed (successfully) the latest image (8.0.0 (OPD1.170816.025, Nov 2017)) after reading the OP...

I am still stuck with the same problem as flashing the first image... it's bootlooping and I cannot figure it out... any suggestions?

 

[nathanchance]

@nathanchance I have a Pixel 2 XL that I am sending back to Google because I got the replacement device today... I was on the dev preview for 8.1 and wanted to return it to stock at least for them... I ran the following:

fastboot flashing unlock

followed by

fastboot flashing unlock_critical

I then flashed the Sept release 8.0.0 (OPD1.170816.010, Sep 2017) and after it flashed successfully, I ran the following commands

fastboot flashing lock

After a quick erase, the phone got stuck in a bootloop... And because I had never seen the _critical command... I ran just for good measure...

fastboot flashing lock_critical

I keep getting an error that the system may be corrupt and it's stuck in a bootloop... I started over with unlocking again and then I flashed (successfully) the latest image (8.0.0 (OPD1.170816.025, Nov 2017)) after reading the OP...

I am still stuck with the same problem as flashing the first image... it's bootlooping and I cannot figure it out... any suggestions?

1. Are you running the flash-all script with the "-w" added? You should because that will fully wipe the device.

2. Don't lock the bootloader until you know the device boots successfully.

Only thing I could think of is the downgrade is failing from AVB but that doesn't make sense otherwise Google would have warned about it.

 

[the1dynasty]

1. Are you running the flash-all script with the "-w" added? You should because that will fully wipe the device.

2. Don't lock the bootloader until you know the device boots successfully.

Only thing I could think of is the downgrade is failing from AVB but that doesn't make sense otherwise Google would have warned about it.

I ended up booting to recovery and sideloading via ADB the Nov OTA taimen-ota-opd1.170816.025-f62d726d and it booted up fine...

Still has the warning at the beginning saying "This device is corrupt........" any idea how to get rid of that??

---------- Post added 10th November 2017 at 12:36 AM ---------- Previous post was 9th November 2017 at 11:53 PM ----------

Still has the warning at the beginning saying "This device is corrupt........" any idea how to get rid of that??

I fixed this by manually flashing the boot.img by pulling it from the downloaded factory image I was on... then I ran these commands

fastboot erase boot

fastboot flash boot boot.img

fastboot flashing lock_critical

fastboot flashing lock

The error went away and all is well again :good:

 

[KennyG123]

I ended up booting to recovery and sideloading via ADB the Nov OTA taimen-ota-opd1.170816.025-f62d726d and it booted up fine...

Still has the warning at the beginning saying "This device is corrupt........" any idea how to get rid of that??

---------- Post added 10th November 2017 at 12:36 AM ---------- Previous post was 9th November 2017 at 11:53 PM ----------



I fixed this by manually flashing the boot.img by pulling it from the downloaded factory image I was on... then I ran these commands

fastboot erase boot

fastboot flash boot boot.img

fastboot flashing lock_critical

fastboot flashing lock

The error went away and all is well again :good:

Was never found a way to get rid of the corrupt notice. It is still there in the Nexus 6P.

 

[beezar]

So why wouldn't you want to do the critical unlock vs just the standard unlock? Are there disadvantages other than accidentally flashing the wrong bootloader and bricking your phone? And if you do brick it that way, is it recoverable?

 

[nathanchance]

So why wouldn't you want to do the critical unlock vs just the standard unlock? Are there disadvantages other than accidentally flashing the wrong bootloader and bricking your phone? And if you do brick it that way, is it recoverable?

I don't know why you wouldn't want to do a critical unlock lol.

I don't know if flashing an incorrect bootloader is recoverable.

Sent from my Pixel 2 XL using XDA Labs

 

[chazall1]

Your Guide is informative and should relieve some of the basic issues
if everyone reads it and understands dont panic.

Thank You.

 

[Cowbell_Guy]

Once we root and install magisk, is this (link below) the best and most appropriate way to continue getting OTAs while maintaining magisk root?

https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

 

[chazall1]

Yes it is. The A/B slots are always switching to the active slot during every update. Updated done by OTA, or adb sideload will change your active slot. If you run, fastboot getvar current-slot, it will give you your current active slot. Lets say your active slot is (a). You receive and OTA or sideload the update. Your new active slot will be (b). and so on. On the safe side For the boot.img I always flash to both slot_a and slot_b.

 

[probono10]

Make the Pixel 2 XL Ad-Free?

Will the links you posted allow for the device to be ad-free via Adaway? I've only rooted 2 devices before using TWRP, and simply don't want to go back to a phone that's like one never ending commercial.

Should I take the warnings that I could brick this brand new device more seriously than the warnings posted in the past prior to Google launching the Pixel brand?

 

[nathanchance]

Will the links you posted allow for the device to be ad-free via Adaway? I've only rooted 2 devices before using TWRP, and simply don't want to go back to a phone that's like one never ending commercial.

Should I take the warnings that I could brick this brand new device more seriously than the warnings posted in the past prior to Google launching the Pixel brand?

Yes, Magisk should allow Adaway to work fine.

No, this is just like any other Google device, unlocking the bootloader should be a safe procedure. I just put warnings so that nobody can claim I bricked their device :silly:

 

[probono10]

OTA 8.0.0

In your opinion should I install the new OTA 8.0.0 update prior to doing this?

 

[slaydog]

The Pixel isn't really a successor to the Nexus line because these are geared purely to consumers. It's Google's iPhone.

Ugh, I LOVE this phone, but an active XDA community is a must for me. I've never even looked at the Pixel 1's development forums, just assumed they were similar to the 6Ps...

I hope the OP5T comes out soon, because if that's where the development is, they deserve my money. And much less of it, I might add, lol...

 

[nathanchance]

Ugh, I LOVE this phone, but an active XDA community is a must for me. I've never even looked at the Pixel 1's development forums, just assumed they were similar to the 6Ps...

I hope the OP5T comes out soon, because if that's where the development is, they deserve my money. And much less of it, I might add, lol...

Eh OnePlus isn't without its flaws either. The release cycle is annoying, kernel source is terrible compared to Google, and the fragmentation between ROMs is frustrating. But those are more developer gripes than anything; from a user's perspective, it's like the ROMs of old lol. It's all about priorities. If a strong development community is what you value, you can't go wrong with OnePlus.

Sent from my Pixel 2 XL using XDA Labs