[Guide] Pixel XL Android 8.1 (OREO) Unlock/Root/Install Images/Kernels/Recovery +

Homeboy76

Senior Member
Aug 24, 2012
2,365
1,114
188
Just a nitpick as this is a great guide. For sub points would it help to use something like a,b,c or I, ii, iii for clarity and less confusion? Leave main points as 1,2,3? Thoughts?
The comments after the title of each category i.e. #8 and before 'a' are notes. The main points are a, b, c, etc.
 

Homeboy76

Senior Member
Aug 24, 2012
2,365
1,114
188
Thanks, but I think you misunderstood me. I meant how #3 in #8 was achieved (3. Install BusyBox to /sbin/supersu/xbin.), but I will give root with SuperSU a new try.
Ok!
If you use Stericsons, free, BusyBox from Google's play store it install to the correct directory/folder.
 
Last edited:

mancman

Senior Member
Jan 17, 2011
172
25
58
Munich
Hello @ all,

things do work and safetynet test passed for me.

First disable security as mentioned above in Android.

I did the factory image flash-all without wiping, then did a temp TWRP 3.2.0-0 flashed from there SU and SUhide.

I did not flash TWRP at all to the device.

enabled Security again and tested for safteynet.

All fine.
 

woody1

Senior Member
May 2, 2010
768
103
43
Atlanta
So, I just got a new Pixel XL and decided to go ahead and update and root. I was already updated to 8.1. So, I unlocked and installed TWRP and Magisk. I decided to factory wipe so I could just set the phone up fresh again, but after the wipe I got into a bootloop, where it kept rebooting into TWRP. I read that somebody else had this problem after installing Magisk.

So, I installed the factory image, which fixed the bootloop problem then re-installed TWRP. This time, I installed SuperSU with the Hide root option. No problems this time. I don't know if Magisk caused the problem, but just in case anybody else has a simliar problem, SuperSU seems more reliable for this purpose.

---------- Post added at 09:57 AM ---------- Previous post was at 09:55 AM ----------

Any guide on how to install OTA updates after root? Thank you!
I'd like to know the status on this, too. Anybody?
 

Homeboy76

Senior Member
Aug 24, 2012
2,365
1,114
188
So, I just got a new Pixel XL and decided to go ahead and update and root. I was already updated to 8.1. So, I unlocked and installed TWRP and Magisk. I decided to factory wipe so I could just set the phone up fresh again, but after the wipe I got into a bootloop, where it kept rebooting into TWRP. I read that somebody else had this problem after installing Magisk.


So, I installed the factory image, which fixed the bootloop problem then re-installed TWRP. This time, I installed SuperSU with the Hide root option. No problems this time. I don't know if Magisk caused the problem, but just in case anybody else has a simliar problem, SuperSU seems more reliable for this purpose.

---------- Post added at 09:57 AM ---------- Previous post was at 09:55 AM ----------



I'd like to know the status on this, too. Anybody?
The reason, I think, your phone bootlooped is you did not flash the boot.img or the factory image after you factory wiped the phone. Magisk #9 or # 10 work if you follow the instructions.


#7 has instructions for sideloading the OTA.zip
I don't think you can install an OTA on a rooted Pixel or Pixel XL.
 
Last edited:

woody1

Senior Member
May 2, 2010
768
103
43
Atlanta
The reason, I think, your phone bootlooped is you did not flash the boot.img or the factory image after you factory wiped the phone. Magisk #9 or # 10 work if you follow the instructions.

That's probably right. I didn't realize that a factory wipe required the factory image to be installed again.


#7 has instructions for sideloading the OTA.zip
I don't think you can install an OTA on a rooted Pixel or Pixel XL.
The only time I took an OTA was when I first got the phone, before I unlocked or rooted. After I unlocked, I didn't connect to the internet until after I successfully rooted the phone.
 

Homeboy76

Senior Member
Aug 24, 2012
2,365
1,114
188
Do SuperSU work with Android 8.1 and TWRP 3.2.1.0?
SuperSU v2.82 SR5, Yes

Edit1: I read on the TWRP RC1 thread that it works if you do not flash twrp 3.2.1-0.zip
Edit2: Maybe, I found this in the OP of TWRP 3.2.1-0 for Pixel Devices by Dees_Troy:
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.

I tested SuperSU and Magisk, Magisk worked.
a. Flashed Factory Image with Flash-all.bat (#5 in OP)
b. Fastboot twrp-3.2.1-0.img
c. Installed twrp-3.2.1-0.zip
d. Reboot recovery
e. Installed Magisk 14.5 (1456)
f. Reboot System
 
Last edited:

Mtsprite

Senior Member
Oct 2, 2013
138
56
0
Houston
So, ive been out of the loop for a bit. I have an untoched verizon Pixel XL on 8.1. I just wanted to confirm if this guide will work. Im a little confused seeing as how i thought the OEM Unlocking toggle used to be switched off and unable to be switched on. If anyone could clarify that would be great thanks. :)
 

Valkyrie743

Senior Member
Nov 19, 2011
290
43
28
So, ive been out of the loop for a bit. I have an untoched verizon Pixel XL on 8.1. I just wanted to confirm if this guide will work. Im a little confused seeing as how i thought the OEM Unlocking toggle used to be switched off and unable to be switched on. If anyone could clarify that would be great thanks. :)
if you have an verizon pixel XL that has a locked bootloader and is currently on 8.1 you're out of luck getting root or unlocking the bootloader.
 

dagnisaun

Member
Jan 1, 2011
44
19
0
San Francisco
What if it is on 8.0? am i still out of luck?
the Verizon could unlock bootloader only on 7.1.0 and earlier.

if your phone becomes defective and need a replacement under warranty, you can talk with Google and possibly get a Google version if you ask nicely :)
my Verizon XL died one day and I got a Google version warranty replacement.
 

640k

Senior Member
Apr 18, 2008
1,367
289
0
so i was force upgraded to 8.1 and i'm trying to follow steps to root and it's not sticking. anyone know why?
 
Last edited:

Homeboy76

Senior Member
Aug 24, 2012
2,365
1,114
188
So why make it part of the guide when talking about using TWRP 3.2.1????? What to use with TWRP 3.2.1 if SuperSU SR5 is out-dated???

---------- Post added at 11:58 AM ---------- Previous post was at 11:28 AM ----------

"There is an internal problem" error when following this guide PRECISELY. I absolutely loathe how these guides are written... No offense, but it's a huge mess. Please re-write or just delete.
What #step did you follow 'PRECISELY" that caused the "There is an internal problem" error? Maybe, I can help you fix it.

No offense, but there is another option to re-writing or deleting guides that you "loathe" how they are written. You could stop reading them.
 
  • Like
Reactions: xonelith

TonikJDK

Senior Member
Dec 9, 2012
2,620
1,301
183
What #step did you follow 'PRECISELY" that caused the "There is an internal problem" error? Maybe, I can help you fix it.

No offense, but there is another option to re-writing or deleting guides that you "loathe" how they are written. You could stop reading them.
He got that by using Magisk. It patches the dtbo.img which causes that error on reboot. It can be ignored, or 14.6 allows you to not patch dtbo.
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone