[ROOT] SuperSU

Search This thread

schwem

Senior Member
Oct 15, 2014
2,215
761
35
Auburn Hills
Yes flashing the image worked flawlessly it's getting root back after sideloading the Ota is what's getting stuck. After sideload I go to fastboot and try to reroot and get stuck there
Hmmm... Try booting android, updating play services to 10 (440-xxxxxxx) then get the OTA loaded through android then try rooting. That's how I did it.
 

canemaxx

Senior Member
Aug 23, 2012
541
59
Wilder,VT
Samsung Galaxy S21 Ultra
Yes apply update from adb in recovery
I booted into bootloader before I started the reroot process

---------- Post added at 08:28 PM ---------- Previous post was at 08:27 PM ----------

I booted into bootloader before I started the reroot process
It was enabled prior to that because I clicked on always allow from this computer
 

canemaxx

Senior Member
Aug 23, 2012
541
59
Wilder,VT
Samsung Galaxy S21 Ultra
I believe that's your issue, because adb works out of the box in recovery. So humor me and try and enable it in android then flash boot to root.
I'm just going to take the Ota and root ...if I lose root oh well I've been at this for 19 hours now lol

---------- Post added at 08:32 PM ---------- Previous post was at 08:30 PM ----------

He can't boot back into Android after the failed OTA sideload. He'll need to reflash image and start fresh. I assume
Correct and that's what I just did.
 

superchilpil

Senior Member
Sep 26, 2009
4,276
1,426
Texas
OnePlus 8 Pro
He can't boot back into Android after the failed OTA sideload. He'll need to reflash image and start fresh. I assume
There should be no reason why he couldn't boot back. If the sideload failed then everything is as it was, and if the boot to root failed then again everything should be as it was.
Heck even if it was messed up we have two of every partition so he could use fastboot set_active to change it the other.

Sent from my Pixel XL using Tapatalk
 

canemaxx

Senior Member
Aug 23, 2012
541
59
Wilder,VT
Samsung Galaxy S21 Ultra
There should be no reason why he couldn't boot back. If the sideload failed then everything is as it was, and if the boot to root failed then again everything should be as it was.
Heck even if it was messed up we have two of every partition so he could use fastboot set_active to change it the other.
After the sideload I could boot, then I tried to root and it didn't fail it just hangs at the bouncing dots
 

canemaxx

Senior Member
Aug 23, 2012
541
59
Wilder,VT
Samsung Galaxy S21 Ultra
There should be no reason why he couldn't boot back. If the sideload failed then everything is as it was, and if the boot to root failed then again everything should be as it was.
Heck even if it was messed up we have two of every partition so he could use fastboot set_active to change it the other.
This time after flashing image ....it's automatically installing the update ....VERY slowly

---------- Post added at 08:40 PM ---------- Previous post was at 08:37 PM ----------

He can't boot back into Android after the failed OTA sideload. He'll need to reflash image and start fresh. I assume
Let me clarify. I installed the Ota via sideload initially and was able to boot, tried to reroot after I had already booted up the device and it hung up (usb debugging was on) I flashed stock image tried again without booting just going from recovery after sideload to bootloader to reroot and had the same issue
 

Top Liked Posts

  • There are no posts matching your filters.
  • 192
    This 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)
    30
    Chain fire was your tester able to verify if the system UI issue was fixed? Just curious I have yet to experience it my self and was just currently below 15%

    Yes, the 15% issue is fixed. Release probably later today or tomorrow. Have some other bugs to fix as well.
    27
    Fanboys just admit that the you can't install RC1 fresh and the op is misleads users to try that route. Dev gave instructions thant don't work. I think it was not tested, however, just flash twrp RC1 and SU5 and the dev assumed it world work. No problem, but many of us wasted hours trying to prove an assumption... Maybe we need SU6? Update: I forgot to say I was trying to root, too. So yes, I can install RC1 but can't root. Srry, dev and those I rubbed the wrong way. My bad.

    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).