[ROOT] SuperSU
- Thread starter Chainfire
- Start date
Ok I took the Ota without sideloading , I'm about to try and root the same way I did initially. If this fails to boot after rooting I'll just stop. Not trying to cause conflict here or waste my time trying to do something that just won't work lol
Will the OTA work while rooted (not break anything other than root)? Then just re-root after (permitting everything is working fine)?
No..it won't install with root. Root has to be removed before taking the Ota . If I was able to unroot via SuperSU I guess I should have tried that but wasn't sure if I should have so I followed what everyone was saying to do
what version of root were you on?
SR3 I think the unroot inside the SU app was supposed to be updated and fixed to work.
I never upgraded to SR3, Im currently still on 2, so id have to flash the OEM boot.img
I was on sr3. Just started it from scratch made sure usb debugging was on adb reboot bootloader, fastboot boot boot-to-root.img and the same thing is happening phone will NOT boot
---------- Post added at 08:58 PM ---------- Previous post was at 08:55 PM ----------
I'm done. This didn't work either. After trying every way that everyone had mentioned I am still not able to get root after the Ota...so I will flash all again for the 4th time in 24 hours and be done with this
The OTA would not work for me while rooted. However, I was able to sideload V, install ElementalX kernel, and root again without any issues. I'm not sure why people are getting stuck at boot. Maybe they aren't using the SR3 update?
This is why I hate verizon ....sucked in to another 2 years with another phone I can't root smh
I've done everything the way the threads and the help I've got said to do it and I am still not able to boot after trying to reroot
No errors at all everything works as it should it just won't boot after I run fastboot boot boot-to-root.img yes the bootloader is already unlocked
I'm having the same issue you are, and I have tried everything as well, even made sure all the USB drivers and adb and fastboot were current, and all that happens is it goes to the bouncing dots and sits there until I power off the phone, and to get the phone operational again, I have to sideload the update. I even tried this on a couple different computers to rule out something related to my computer setup or something. I also have the regular pixel, and not the XL version.
I just flash-all again so it's going to be a few minutes . After I flash all and update is applied what exactly should I be doing to reroot just so I am double sure I am doing it right
---------- Post added at 09:33 PM ---------- Previous post was at 09:27 PM ----------
What about in dev option where it says verify apps over usb/adb....should that be on?
---------- Post added at 09:40 PM ---------- Previous post was at 09:33 PM ----------
It restarts twice and then hangs at the dots. I'm about to do it again and send a screen shot
I'm sorry but I can/will only help if you follow along.
I want a screen shot of the terminal/command prompt from when you try to boot the "boot to root" image.
I want a screen shot of the terminal/command prompt from when you try to boot the "boot to root" image.
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
192This thread was originally for Pixel-specific rooting instructions, but by now the SuperSU ZIP and TWRP are fully supported:
- Fastboot boot TWRP
- Install latest SuperSU ZIP (v2.79-SR3 at the time of writing)
Note that at this time I recommend against fastboot flashing TWRP. With the Pixel's new partition layout, the recovery files are inside the boot partition, and so is SuperSU. If you flash both, SuperSU's internal boot image backup will not be of the original boot image, but of TWRP. This means that neither the 'full unroot' option in SuperSU, nor incremental OTA update through FlashFire, will work as expected.
OR
- Use CF-Auto-Root for Pixel (not released at the time of writing, but should be released soon)36v2.78 SR3 released - with 15% crash fix - https://plus.google.com/+Chainfire/posts/24xhJN724HG30
Yes, the 15% issue is fixed. Release probably later today or tomorrow. Have some other bugs to fix as well.29SuperSU compatible with the TWRP alpha: https://plus.google.com/+Chainfire/posts/CBL8pnKtA8F27
The instructions worked at that release time (weeks ago), it's not my fault TWRP was updated a few days ago in an incompatible way. Nor is it Dees_Troy's fault - it's just how things turned out.
There will be an update to SuperSU to fix this. In the mean time, just use alpha2 instead of rc1.
Or, you could continue being a complete asshat, in which case, please get the hell out of my thread (and/or off my planet).
