Obtaining Root/unlocked BootloaderU

msmall82

Senior Member
May 9, 2011
98
10
0
So I finally got root/bootloader unlocked but I have yet to activate my XL (just have so much on my note wanted to make sure I had everything backed up).

Once I connected via WIFI it found the OTA update.

I just wanted to confirm what I've already read. If I install the OTA update all I have to do is re-root, correct? Since I already have SU ZIP on my internal storage all I have to do is flash it again using a temp boot of TWRP from a fastboot command, correct?

I've read a bunch of threads saying users had all sorts of trouble but I am guessing those are users who actually flashed TWRP, not just a temp boot into TWRP to flash SU.

I don't feel like dealing with a softbrick as I am trying to move everything over to my Pixel XL from my Note today.

Figured I would ask all of you who have done this before....thank you in advance. I wouldn't have been able to unlock my bootloader/root if it weren't for XDA!
 
Last edited:

TonikJDK

Senior Member
Dec 9, 2012
2,620
1,301
183
So I finally got root/bootloader unlocked but I have yet to activate my XL (just have so much on my note wanted to make sure I had everything backed up).

Once I connected via WIFI it found the OTA update.

I just wanted to confirm what I've already read. If I install the OTA update all I have to do is re-root, correct? Since I already have SU ZIP on my internal storage all I have to do is flash it again using a temp boot of TWRP from a fastboot command, correct?

I've read a bunch of threads saying users had all sorts of trouble but I am guessing those are users who actually flashed TWRP, not just a temp boot into TWRP to flash SU.

I don't feel like dealing with a softbrick as I am trying to move everything over to my Pixel XL from my Note today.

Figured I would ask all of you who have done this before....thank you in advance. I wouldn't have been able to unlock my bootloader/root if it weren't for XDA!
Updating with root is a crapshoot. It might update ok and yes you reroot exactly lime you describe.

Or the update might fail, but it won't break your phone. It will fail before the install.
 
  • Like
Reactions: msmall82

msmall82

Senior Member
May 9, 2011
98
10
0
Updating with root is a crapshoot. It might update ok and yes you reroot exactly lime you describe.

Or the update might fail, but it won't break your phone. It will fail before the install.
OTA update failed, it downloaded it and then failed. I am guessing if I want to upgrade to 7.1.1 I would have to do it manually using the IMG from Google and flash it in TWRP?
 

TonikJDK

Senior Member
Dec 9, 2012
2,620
1,301
183
OTA update failed, it downloaded it and then failed. I am guessing if I want to upgrade to 7.1.1 I would have to do it manually using the IMG from Google and flash it in TWRP?
Well, I do it the longer way but it is easier for me and I know I got a cleanish phone each month. I download the full image and extract it into my fastboot/adb folder. Then I edit the flash-all.bat file and remove the -w from near the end and save it. Removing the -w stops it from flashing the user partition. So all your data, settings and apps are left alone. Then I boot twrp and install SU.

Another option that might work is to download the full OTA image and ADB sideload it. OTA and instructions here:
https://developers.google.com/android/ota

Used to be able to use Flashfire to install OTA's, last I heard it didn't work on Pixel's. But maybe that has changed.
 

msmall82

Senior Member
May 9, 2011
98
10
0
Updating with root is a crapshoot. It might update ok and yes you reroot exactly lime you describe.

Or the update might fail, but it won't break your phone. It will fail before the install.
Well, I do it the longer way but it is easier for me and I know I got a cleanish phone each month. I download the full image and extract it into my fastboot/adb folder. Then I edit the flash-all.bat file and remove the -w from near the end and save it. Removing the -w stops it from flashing the user partition. So all your data, settings and apps are left alone. Then I boot twrp and install SU.

Another option that might work is to download the full OTA image and ADB sideload it. OTA and instructions here:
https://developers.google.com/android/ota

Used to be able to use Flashfire to install OTA's, last I heard it didn't work on Pixel's. But maybe that has changed.
Are there any major improvements that were released? I think I might just leave it on 7.1 for now.

I am guessing I would download the latest version of 7.1.1 from the Google site? 7.1.1 NOF27C is the latest from what I am seeing on the list?

Do the instructions work on the Google site exactly as described or do those of us with unlocked bootloaders need to do anything differently? I'm not versed enough yet in how we have different partitions, ect on the Pixel?

I don't mind sideloading it as I haven't even activated the phone yet so I don't care if it wipes everything....
 

msmall82

Senior Member
May 9, 2011
98
10
0
Well, I do it the longer way but it is easier for me and I know I got a cleanish phone each month. I download the full image and extract it into my fastboot/adb folder. Then I edit the flash-all.bat file and remove the -w from near the end and save it. Removing the -w stops it from flashing the user partition. So all your data, settings and apps are left alone. Then I boot twrp and install SU.

Another option that might work is to download the full OTA image and ADB sideload it. OTA and instructions here:
https://developers.google.com/android/ota

Used to be able to use Flashfire to install OTA's, last I heard it didn't work on Pixel's. But maybe that has changed.
I went ahead and sideloaded 7.1.1 and SU is still installed? Shouldn't it have wiped my phone and removed SU? I can also still unlock with my fingerprint? I thought all of my settings would get wiped?
 

5.1

Senior Member
Mar 18, 2012
1,316
546
143
haguenau
I went ahead and sideloaded 7.1.1 and SU is still installed? Shouldn't it have wiped my phone and removed SU? I can also still unlock with my fingerprint? I thought all of my settings would get wiped?
Hi...

Sideloading is just like installing an official OTA pushed by Google. So it doesn't wipe anything. SU is systemless I guess, so it didn't remove it. :)
 

msmall82

Senior Member
May 9, 2011
98
10
0
Hi...

Sideloading is just like installing an official OTA pushed by Google. So it doesn't wipe anything. SU is systemless I guess, so it didn't remove it. :)
Yea the app was installed but it wasn't actually "rooted". I still had to boot back into TWRP and reflash SU for the SU App to actually open and work properly.
 

TonikJDK

Senior Member
Dec 9, 2012
2,620
1,301
183
Yea the app was installed but it wasn't actually "rooted". I still had to boot back into TWRP and reflash SU for the SU App to actually open and work properly.
Right, the app is a user setting just like the rest of your apps so it would have stayed.