Stuck rooting

[smokeydriver]

Hi all, so I have Verizon's Pixel XL. I have unlocked it successfully and had rooted. I asked on the forums about upgrading the OTA update and was told it was fine. After doing so, I noticed my SuperSU was gone (although I might have lost it earlier and not noticed). So after trying to get it back and keeping getting stuck, I bit the bullet and ADB sideloaded the factory image from google (NDE63X) and got it able to boot up. Yay.

So then I ran the 'adb reboot bootloader' command, then verified my device was connected with 'fastboot devices' and finally I ran 'fastboot boot boot-to-root.img'. And here I am, stuck on the splash screen again.

So I looked around and saw some mentions of people that had used older versions of Chainfire's SuperSU. I tried the newer one (2.78 SR3) and the same thing happened. I do see that there is a SR5, but I also see Chainfire's comment "Do not use the SuperSU ZIP on work-in-progress TWRP releases for Pixel, it will not work - use the model specific links above instead.

I can get it to run just fine without using chainfire's supersu...but then I don't have the supersu app or any real gains from having rooted.

So, I feel like I must be doing something wrong. Any suggestions?

 

[cam30era]

@smokeydriver,

You probably should update your Android SDK package. This problem can also be caused by an obsolete fastboot.

 

[smokeydriver]

@smokeydriver,

You probably should update your Android SDK package. This problem can also be caused by an obsolete fastboot.

I can give it a shot, but I only installed minimal adb yesterday on my new laptop. Thanks!

 

[cam30era]

I can give it a shot, but I only installed minimal adb yesterday on my new laptop. Thanks!

I understand. Here's the thing: I don't know if minimal has up to date ADB and fastboot for Android 7.1.1.

 

[smokeydriver]

I understand. Here's the thing: I don't know if minimal has up to date ADB and fastboot for Android 7.1.1.

The OTA update I took only got me to a new version of 7.1, not 7.1.1 (from NDE63P to NDE63X). It still shows an available update to 7.1.1 which I have *not* done.

 

[Nitemare3219]

Try using the Unified Toolkit. It saved me from having a bootloop disaster when I tried upgrading from 7.1.1 due to poor instruction availability around the web. It should fix whatever problem you are having, even if that means flashing the factory image first again.

 

[smokeydriver]

Try using the Unified Toolkit. It saved me from having a bootloop disaster when I tried upgrading from 7.1.1 due to poor instruction availability around the web. It should fix whatever problem you are having, even if that means flashing the factory image first again.

I've tried, but keep getting an error 21 code that it can't install...I tried this with SR5 and SR2.

 

[FreeSoftwareServers]

How I Rooted

Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.

Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)

AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.

Flash TWRP, then SuperSU.

Reboot into OS, confirm root, give it 5 minutes.

Reboot back to Recovery and flash Kernel if desired.

Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb twrp.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.

 

[smokeydriver]

Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.

Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)

AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.

Flash TWRP, then SuperSU.

Reboot into OS, confirm root, give it 5 minutes.

Reboot back to Recovery and flash Kernel if desired.

Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb boot.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.

Ok, I must be doing something wrong on a very basic level. It gave me error 21 (signature verification error) when trying to use the unified android tookit to install 7.1. Anyways, I'll just move on and skip that step and see what happens.

 

[spotmark]

Flashing SuperSU SR5 works just fine with TWRP RC1. All you have to do is delete the file you're told to before flashing.

How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.

 

[smokeydriver]

Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.

Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)

AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.

Flash TWRP, then SuperSU.

Reboot into OS, confirm root, give it 5 minutes.

Reboot back to Recovery and flash Kernel if desired.

Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb twrp.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.

I transferred those 2 files to my download folder on my phone, ran the twrp.img script, and then when I go in...the file names are not normal. Everything is random letters and numbers. Again, I feel like I'm making some stupid basic mistake that I don't understand (and I've rooted plenty of phones).

 

[smokeydriver]

Flashing SuperSU SR5 works just fine with TWRP RC1. All you have to do is delete the file you're told to before flashing.

So I go in TWRP to advanced, file manager, and I don't see the names of those files. Are they buried in a folder?

 

[spotmark]

So I go in TWRP to advanced, file manager, and I don't see the names of those files. Are they buried in a folder?

You have TWRP RC1 installed?

 

[smokeydriver]

You have TWRP RC1 installed?

Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.

 

[spotmark]

Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.

Ah, I see. I misunderstood. I thought you were just under the impression that you couldn't flash SU with RC1. My apologies.

 

[smokeydriver]

Ok, so can someone tell me why I am getting stuck with 1 thing. I go to my stock recovery and into ADB sideload. When I tell it the file, it keeps failing to verify whole-file signature. What is wrong with this one step?

Or alternatively...when I'm in TWRP Alpha 2- why are all the files within the sdcard random letters and numbers?

 

[toknitup420]

Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.

Twrp is not decrypting you're data. Try rebooting twrp from fastboot a second time.

 

[smokeydriver]

Twrp is not decrypting you're data. Try rebooting twrp from fastboot a second time.

Son-of-a B#[email protected]#$. It asks me to 'decrypt data' by entering a password. I had hit cancel. What's the password??

 

[smokeydriver]

Son-of-a B#[email protected]#$. It asks me to 'decrypt data' by entering a password. I had hit cancel. What's the password??

Never mind...it's my 4 digit password that's used when my finger unlock doesn't work. Ugh- I knew it was something simple and dumb I was doing!

 

[notsointeresting]

Ok, so can someone tell me why I am getting stuck with 1 thing. I go to my stock recovery and into ADB sideload. When I tell it the file, it keeps failing to verify whole-file signature. What is wrong with this one step?

Or alternatively...when I'm in TWRP Alpha 2- why are all the files within the sdcard random letters and numbers?

Can I ask you how you fixed this? I'm having the same issue and this post popped up on Google.