Obtaining Root/unlocked BootloaderU

msmall82

Senior Member
May 9, 2011
98
10
0
Exactly, power on with no sim and skip any set up including wifi. No reason to do any set up as the bootloader unlock with wipe the device. Enable ADB and get to unlocking straight away. No sim and no wifi means there is zero way it can update itself on you.

Sent from my Pixel XL using Tapatalk
Thanks everyone, I will keep you updated !
 

msmall82

Senior Member
May 9, 2011
98
10
0
There are a lot of ways because this phone was so different, so a lot of what you see is the testing and changes that can from that.

So, after it is unlocked update it to 7.1.1 and then:

Download 2.7.9 SR3 SuperUser and copy it to your phone.

https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Download TWRP RC3 and copy it to your fastboot folder.

https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312

Using other versions than above will bootloop you. Reboot the phone into bootloader mode. Power and Vol down.

fastboot BOOT twrpFilename.img Where twrpfilename.img is the name of the TWRP file you just downloaded. Note is says boot in the command, not flash.

That will boot the phone into TWRP. Select Install and install the SU zip you copied to the phone above. And reboot the phone, done.

---------- Post added at 01:06 AM ---------- Previous post was at 01:05 AM ----------

And here is the link to the proper fastboot version.

https://developer.android.com/studio/releases/platform-tools.html
Multiple people have told me not to update to 7.1.1 even after unlocking the bootloader. Are you sure that is a good idea??
 

TonikJDK

Senior Member
Dec 9, 2012
2,620
1,301
183
Multiple people have told me not to update to 7.1.1 even after unlocking the bootloader. Are you sure that is a good idea??
First I have ever heard anyone say that. Would love to hear their reasoning. Updating after unlock is what everyone is doing from what I see around here. I honestly can't think of any harm. Once you depixl8 it, it is a wide open phone, you can update, downgrade, ROM...what ever you want. Just don't relock it.
 

msmall82

Senior Member
May 9, 2011
98
10
0
There are a lot of ways because this phone was so different, so a lot of what you see is the testing and changes that can from that.

So, after it is unlocked update it to 7.1.1 and then:

Download 2.7.9 SR3 SuperUser and copy it to your phone.

https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Download TWRP RC3 and copy it to your fastboot folder.

https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312

Using other versions than above will bootloop you. Reboot the phone into bootloader mode. Power and Vol down.

fastboot BOOT twrpFilename.img Where twrpfilename.img is the name of the TWRP file you just downloaded. Note is says boot in the command, not flash.

That will boot the phone into TWRP. Select Install and install the SU zip you copied to the phone above. And reboot the phone, done.

---------- Post added at 01:06 AM ---------- Previous post was at 01:05 AM ----------

And here is the link to the proper fastboot version.

https://developer.android.com/studio/releases/platform-tools.html
First I have ever heard anyone say that. Would love to hear their reasoning. Updating after unlock is what everyone is doing from what I see around here. I honestly can't think of any harm. Once you depixl8 it, it is a wide open phone, you can update, downgrade, ROM...what ever you want. Just don't relock it.
Have the commands changed for depixel8? From what I've read, install ADB/Fastboot (going to use the minimal ADB/Fastboot available here in the forums) and run these commands :

Run "adb push dePixel8 /data/local/tmp",
"adb shell chmod 755 /data/local/tmp/dePixel8"
Run program "adb shell /data/local/tmp/dePixel8"

Wait for the phone to reboot to the bootloader.

ssue the command "fastboot oem unlock", this will open up the unlock prompt and warning on the screen. You can now unlock. If you get an error, about unlocking not being allowed, start all over

---------- Post added at 01:59 PM ---------- Previous post was at 01:57 PM ----------

Have the commands changed for depixel8? From what I've read, install ADB/Fastboot (going to use the minimal ADB/Fastboot available here in the forums) and run these commands :

Run "adb push dePixel8 /data/local/tmp",
"adb shell chmod 755 /data/local/tmp/dePixel8"
Run program "adb shell /data/local/tmp/dePixel8"

Wait for the phone to reboot to the bootloader.

ssue the command "fastboot oem unlock", this will open up the unlock prompt and warning on the screen. You can now unlock. If you get an error, about unlocking not being allowed, start all over
My phone has arrived, running home to grab it, will let everyone know if it is still 7.1

I have a feeling it will be. A co-worker just got his Pixel XL 2 days ago and his was on 7.1 (silvery gray). Another friend ordered the regular Pixel and his was 7.1.1

---------- Post added at 02:02 PM ---------- Previous post was at 01:59 PM ----------

There are a lot of ways because this phone was so different, so a lot of what you see is the testing and changes that can from that.

So, after it is unlocked update it to 7.1.1 and then:

Download 2.7.9 SR3 SuperUser and copy it to your phone.

https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Download TWRP RC3 and copy it to your fastboot folder.

https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312

Using other versions than above will bootloop you. Reboot the phone into bootloader mode. Power and Vol down.

fastboot BOOT twrpFilename.img Where twrpfilename.img is the name of the TWRP file you just downloaded. Note is says boot in the command, not flash.

That will boot the phone into TWRP. Select Install and install the SU zip you copied to the phone above. And reboot the phone, done.

---------- Post added at 01:06 AM ---------- Previous post was at 01:05 AM ----------

And here is the link to the proper fastboot version.

https://developer.android.com/studio/releases/platform-tools.html
I checked the TWRP site in the link you provided and it does not have RC3 for Marlin. Only Alpha1, Alpha2 and RC1?
 

msmall82

Senior Member
May 9, 2011
98
10
0
Sorry, I'm an idiot and do that often. I get the 3 on Superuser and the 1 on TWRP mixed up.

It is TWRP RC1 that you want.
You're no idiot, you have been a huge help. I haven't had a non-rooted phone in about 6-7 years. I don't know what I would do without a rooted phone. Seems easy enough, run the depixel8 commands, copy the SU zip to my phone, fastboot and temp boot into TRWP (don't flash it with the zip, just boot with the IMG). Once in TWRP install the SU zip.

I had an older phone where I flashed TWRP and could boot into it whenever I wanted, I am guessing due to how these phones are setup we don't actually flash TWRP we just boot into it temporarily to flash SU...

So if we ever need to use TWRP again how do we do that? We can't flash it on our phones so it is always available?
 

TonikJDK

Senior Member
Dec 9, 2012
2,620
1,301
183
So if we ever need to use TWRP again how do we do that? We can't flash it on our phones so it is always available?
So when you go to the TWRP page you will see two RC1 files. One is a .img file, you use that to boot to TWRP. The other is a .zip file, you can copy that to your phone...and then boot to TWRP as described before and then install that .zip. Just as you are going to do with SU.

Chainfire suggests not installing TWRP at this time. Has something to do with how recovery and boot are kind of intertwined now...I don't totally understand it. Since I don't really do much other than root and a custom kernel I don't need TWRP all the time...so I follow his advice. If I need TWRP again I just boot to it via my PC again. I don't flash anything unless I am near a PC, so I don't mind doing it that way.

That said, there are lots of peeps here that have TWRP installed and I don't see anyone complaining much.
 
  • Like
Reactions: msmall82

msmall82

Senior Member
May 9, 2011
98
10
0
So when you go to the TWRP page you will see two RC1 files. One is a .img file, you use that to boot to TWRP. The other is a .zip file, you can copy that to your phone...and then boot to TWRP as described before and then install that .zip. Just as you are going to do with SU.

Chainfire suggests not installing TWRP at this time. Has something to do with how recovery and boot are kind of intertwined now...I don't totally understand it. Since I don't really do much other than root and a custom kernel I don't need TWRP all the time...so I follow his advice. If I need TWRP again I just boot to it via my PC again. I don't flash anything unless I am near a PC, so I don't mind doing it that way.

That said, there are lots of peeps here that have TWRP installed and I don't see anyone complaining much.
You're the man, I'm right there with you. Don't think I'll be using TWRP much since I am not flashing any roms, I used it before to do nandroid backups of slots on my old Galaxy device, since I just need it to flash SU I'll just temporarily boot with the IMG like you said,

With that being said, I don't need to copy the ZIP as you mentioned, just use Fastboot into TWRP temporarily and flash SU,

What custom kernel are you using if you don't mind me asking? Might as well drop a new kernel on it as well.
 

TonikJDK

Senior Member
Dec 9, 2012
2,620
1,301
183
You're the man, I'm right there with you. Don't think I'll be using TWRP much since I am not flashing any roms, I used it before to do nandroid backups of slots on my old Galaxy device, since I just need it to flash SU I'll just temporarily boot with the IMG like you said,

With that being said, I don't need to copy the ZIP as you mentioned, just use Fastboot into TWRP temporarily and flash SU,

What custom kernel are you using if you don't mind me asking? Might as well drop a new kernel on it as well.
I'm using Franco's. His battery life is pretty epic.
 

frugalling

Member
Mar 3, 2017
8
0
0
vz pixel xl still shipping with 7.1

just wanted to let people know that it is still possible to get a 7.1 with verizon. came in the mail today and just depixel8ed.
 

napoleontheruler

Senior Member
Mar 17, 2009
410
12
0
I just got my pixel from Verizon and it's running 7.1 not 7.1.1 but the oem unlocking options is greyed out how do I change it

Sent from my SM-G935U using XDA Free mobile app
 

msmall82

Senior Member
May 9, 2011
98
10
0
I just got my pixel from Verizon and it's running 7.1 not 7.1.1 but the oem unlocking options is greyed out how do I change it

Sent from my SM-G935U using XDA Free mobile app
Read this thread...please. I think everyone jumped in and explained it pretty well. Even to someone like me who has rooted 4/5 phones this pixel is complicated. Have to enable Dev options/USB debugging (don't put your SIM in or enable WIFI and let the OTA update run) then use depixel8 to unlock the boot loader, then fastboot into TWRP and flash SU.
 
  • Like
Reactions: TonikJDK

msmall82

Senior Member
May 9, 2011
98
10
0
How does it update if no sim or wifr

Sent from my SM-G935U using XDA Free mobile app
That's the whole point you don't want it to udpate, once it goes to 7.1.1 you can't unlock. Go to about phone > and i think you push 7 times on the version number of the phone and that enables the ability to enable (going to pick mine up from the UPS store right now, will let you know shortly)
 

napoleontheruler

Senior Member
Mar 17, 2009
410
12
0
Yea I did that went to about phone unlocked developer options turned on USB debugging but oem unlocking is greyed out

Sent from my SM-G935U using XDA Free mobile app
 

msmall82

Senior Member
May 9, 2011
98
10
0
How does it update if no sim or wifr

Sent from my SM-G935U using XDA Free mobile app
Prerequisites to unlock Google Pixel or Pixel XL bootloader
Enable Developer options on your Google Pixel: go to Settings > About phone > Build number and tap it 7 times.
Enable USB Debugging: go to Settings > Developer options and enable USB Debugging and OEM unlocking.
Make sure your Google Pixel is either plugged into a power source or is charged to 80%.
Backup data on your Google Pixel or Pixel XL.
Download ADB and Fasboot and install it on your computer.
 

msmall82

Senior Member
May 9, 2011
98
10
0
Thats what depixel8 does, it toggles the greyed out unlock option. Thats also what 7.1.1 patched.

Sent from my Pixel XL using Tapatalk
I just got my phone and it is indeed NDE63P 7.1 !!!

In progress of depixel8 right now

---------- Post added at 08:08 PM ---------- Previous post was at 07:56 PM ----------

I just got my phone and it is indeed NDE63P 7.1 !!!

In progress of depixel8 right now
Blah, minimal ADB/Fastboot is not recognizing my device even though I installed the drivers, ugh. So excited to get this thing finally!

When I run adb devices it finds my phone but when I run the command to fastboot to the image it just says "waiting for devices"

Anyone seen this before?

---------- Post added at 08:22 PM ---------- Previous post was at 08:08 PM ----------

I just got my phone and it is indeed NDE63P 7.1 !!!

In progress of depixel8 right now

---------- Post added at 08:08 PM ---------- Previous post was at 07:56 PM ----------



Blah, minimal ADB/Fastboot is not recognizing my device even though I installed the drivers, ugh. So excited to get this thing finally!

When I run adb devices it finds my phone but when I run the command to fastboot to the image it just says "waiting for devices"

Anyone seen this before?
When I run adb devices it finds my phone but when I run the command to fastboot to the image it just says "waiting for devices"

Anyone seen this before?

---------- Post added at 09:04 PM ---------- Previous post was at 08:22 PM ----------

I just got my phone and it is indeed NDE63P 7.1 !!!

In progress of depixel8 right now

---------- Post added at 08:08 PM ---------- Previous post was at 07:56 PM ----------



Blah, minimal ADB/Fastboot is not recognizing my device even though I installed the drivers, ugh. So excited to get this thing finally!

When I run adb devices it finds my phone but when I run the command to fastboot to the image it just says "waiting for devices"

Anyone seen this before?

---------- Post added at 08:22 PM ---------- Previous post was at 08:08 PM ----------



When I run adb devices it finds my phone but when I run the command to fastboot to the image it just says "waiting for devices"

Anyone seen this before?
OK GOT IT!!! Here the EXACT STEPS TO GET YOUR 7.1 WORKING

download dePixel8 in the same folder where you have installed ADB/Fastboot files.

Enable Developer options on your Google Pixel: go to Settings > About phone > Build number and tap it 7 times.
Enable USB Debugging: go to Settings > Developer options and enable USB Debugging


Connect your Google Pixel or Pixel XL to the PC using a USB cable.

Navigate to the folder where you have extracted the ADB and Fastboot files and open cmd (press Shift + Right click on empty space inside the folder and select Open command prompt).

Enter the following commands:

adb push dePixel8 /data/local/tmp

adb shell chmod 755 /data/local/tmp/dePixel8

adb shell /data/local/tmp/dePixel8

This installs dePixel8 and reboots the phone into fastboot mode, you then type "fastboot oem unlock"

Your phone will then prompt you to unlock the bootloader, telling you that you may void your warranty by doing so, hit the UP Volume for Yes, then the power button. You now reboot your phone and your bootloader is unlocked. When I go to developer options OEM Unlocking is still grayed out but it now says "Bootloader is already unlocked"

Proceed with TWRP and SU installation, as I am doing right now!
 
Last edited: