• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help boot doesn't get beyond "Google" display after twrp install of SuperSU

hstroph

Android Expert
Greetings,

Tonight I successfully flashed angler-opm5.171019.015 onto my Nexus 6P, and reboots were normal as far as mail etc goes.

Then fastboot twrp-3.2.1-0-angler.img and twrp recovery came up fine. From twrp I installed SuperSU-v2.82-201705271822.zip which was in /sdcard/Download/, There were no apparent problems.

However, a system reboot from within twrp is hung at "Google" on the display, so nothing is functional after almost an hour.

Your help is needed and much appreciated, please.
 
I was able to get back to the bootloader and re-flashed the android factory image, then the twrp, so at least I have a phone and navigation available for Monday, thank you.

The root is important for several apps that are required though, so is there a known problem with twrp-3.2.1-0-angler.img installing SuperSU-v2.82-201705271822.zip on the Nexus 6P with this android img, please?
 
Was your device encrypted before you flashed TWRP? If yes, you'll probably need to wipe data and flash a no dm-verity zip before you install SU/Magisk.

Which guide did you follow to get to where you are right now?
 
Was your device encrypted before you flashed TWRP?
Negative.
If yes, you'll probably need to wipe data and flash a no dm-verity zip before you install SU/Magisk.
I know nothing about "SU/Magisk" and am in the habit of using SuperSU.
Which guide did you follow to get to where you are right now?
I've been rooting Andoid since October 2013 using the same technique ... flash the latest Android factory image without a wipe (except 7.x to 8.x), flash the latest TWRP for the particular phone(s) (Nexus 4,5, and currently 6P), then use the TWRP to install the latest SuperSU.

Since flashing angler-opm5.171019.015 this past Sunday, twrp-3.2.1-0-angler.img and SuperSU-v2.82-201705271822.zip, the boot "freeze" happens. Even reverting to SR3-SuperSU-v2.79-SR3-20170114223742.zip with angler-opm5.171019.015 causes the boot "freeze", so currently the phone is not rooted, as mentioned above.

It appears that angler-opm5.171019.015 has a problem with SuperSU, and that's the problem I need to solve now.

Thanks for your participation
 
A lot has changed since 2013 though, is this the first time you've rooted a device that shipped with Marshmallow or above?

Google requires that all devices (included their own Nexus and Pixel range) which ship with 6.0 or above have FDE, Full Device Encryption, enabled out of the box. As a consequence of this, you may have to decrypt or format the data partition if you want to root, or the device won't boot.

At any point in the process have you formatted the data partition?

https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Also, are you on Nougat or Oreo at the moment?
 
Last edited:
Back
Top Bottom