My 4.4.3 OTA installed just fine this afternoon and I immediately grabbed the latest SuperSU .zip and installed it with TWRP to get re-rooted, but after I told SuperSU to get itself re-installed from Google Play, it wanted to update the binary, and the "normal" method wouldn't work, even after a couple of reboots and retrys.
I don't have TWRP installed on my Nexus 7, instead just using fastboot to boot it when I need it for something, so the technique that finally got the binary updated was to tell SuperSU to use the TWRP update mode, then when it I got the popup saying it was about to reboot to recovery, I plugged in the USB cable and ran:
adb reboot bootloader
fastboot boot openrecovery-twrp-2.7.1.0-flo.img
That worked. As soon as TWRP booted, it installed the script SuperSU had prepared for it, and the binary was indeed updated.
I never had a problem with the "normal" binary update method before. Something new and "helpful" in 4.4.3 I guess.
You can share the script SuperSU?
RazrBR said:
You can share the script SuperSU?
Click to expand...
Click to collapse
If still having issues, try the 1.99r4 from the link in my signature.
Related
I just got the KRT16S OTA update, how can I update keeping root? Would root keeper do the trick?
You'll lose root, but you can root it again by installing supersu binary from recovery mode or custom recovery.
Sent from my Nexus 7
Worked. Thanks
I received the OTA update (SRT16S) this evening. I was previously rooted with SuperSU 1.69 and TWRP.
When I boot into recovery, it comes up and says "No command" -- how do I re-install SuperSU?
My Nexus 7 works fine otherwise, just no root.
ncshawng said:
I received the OTA update (SRT16S) this evening. I was previously rooted with SuperSU 1.69 and TWRP.
When I boot into recovery, it comes up and says "No command" -- how do I re-install SuperSU?
Click to expand...
Click to collapse
Same way you installed the first time.
boot to bootloader
fastboot boot twrp.img
choose install
select supersu update.zip
sfhub said:
Same way you installed the first time.
boot to bootloader
fastboot boot twrp.img
choose install
select supersu update.zip
Click to expand...
Click to collapse
Ok, thanks -- that's what I figured it would have to be but wanted a confirmation.
Since I rooted my Nexus 5X, whenever I'll go into the SuperSU app, it'll ask me to update my binary but a few seconds after I go to do that, it pops up with the message "Installation failed ! Please reboot and try again." However even after reboot it won't work. Has anyone had the same problem, or have any idea how to fix it?
Other things to know is that I'm using a Mac so if I need to use it, I'll have to use Terminal commands on Command Prompt, the version of SuperSU I flashed was Beta 2.56 and the custom recovery I'm using is TWRP.
Thanks in advance.
guessing you flashed SuperSU to your phone via TWRP. after you flashed it, did TWRP ask you again specifically if it should flash SuperSU?
if that was the case the solution is easy: repeat the process and decline that offer from TWRP, because that replaces the version of SU you initially flashed.
Has anyone upgraded their firmware to PK6 and attempted to root? I don't have any issues flashing TWRP with Odin. None whatsoever. When I flash a SuperSU zip or a PHH Superuser zip, I cannot get past the T-Mobile boot animation. It freezes every time. Once this happens I cannot boot to recovery. I can only boot to Download Mode. Hell, I can't even power down my device after I flash a root zip. Just curios if anyone has dealt with this issue. I have attempted to flash SuperSu zips starting with the 2.71 Beta up to the 2.78 SR5 with zero luck. I've also tried with PHH Superuser and I get the same results. Can anyone shed and light on the subject?
After several failed attempts to root my Galaxy S6 Edge+ (SM-G928T) with the latest firmware update to 6.0.1, G928TUVU4DPK6, this is what I had to do to get a working root solution. At no time did I ever have a problem installing TWRP with Odin. Ive been using Odin 3.12.3 but I had the same issues with Odin 3.10.7.
I started with a clean slate and performed a fresh install of the stock firmware which I downloaded from here:
http://forum.xda-developers.com/tmo...al/sm-g928t-stock-odin-g928tuvu4dpk6-t3516310
After flashing the stock firmware with Odin 3.12.3 I did the basic setup on my device to make sure I could boot and everything was working. Next, I shut down my device and booted to Download Mode by using the key combination of Volume Down + Home + Power. Once booted into Download Mode I used Odin again to flash TWRP 3.0.2-0, which is available here:
https://dl.twrp.me/zenltetmo/
After the flash was complete I booted to recovery using Volume Up + Home + Power. When TWRP starts it will ask you if you want to swipe to allow system modification. If you swipe to allow system modifications you will trigger DM-Verity and you will not be able to boot normally unless you flash a custom kernel that has DM-Verity disabled in the fstab or you can flash the no-verity-opt-encrypt.zip that I dowloaded from here:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
The newest version available is 5.0
So, I swiped to allow system modifications. Next, I transferred the no-verity-opt-encrypt.zip from my PC to my device and installed the zip in TWRP. Once this was completed, I transferred my root zip from my PC to my device. I used the PHH Superuser to root my device which is available here:
https://superuser.phh.me/superuser.zip
I installed the root zip in TWRP, wiped cache/dalvik cache and then selected Reboot System. I didnt know if I would be able to boot or not. I could never get past the T-Mobile boot animation each time I attempted to root this damn thing but low and behold everything went as planned and I was fully booted up and running. I went through the setup wizard and everything was working as it should.
I am using PHH Superuser instead of Chainfires SuperSU. Its a personal choice for me as I have been using PHH Superuser since the hand off of SuperSU to a new company, CCMT, LLC.
Once I was finally able to boot normally I downloaded PHH's app in the Play Store from here:
https://play.google.com/store/apps/details?id=me.phh.superuser
This is just my experience of what I had to do to get root working on my S6 Edge+. All of my root apps are working as designed. I cant remember the last time I didnt have a rooted device and it was starting to bother me. I was having root withdrawals. If anyone decides to upgrade to the latest firmware from T-Mobile and wants a working root solution, here is what worked for me. I have not tried to use Chainfires SuperSU again. If you dont want to use PHH Superuser and wanted to use SuperSU instead, try to insert SuperSU in place of PHH Superuser and see what happens. Do this at your own risk because I have not tested it with this solution that I found. Good luck. Happy Rooting!!
fast69mopar said:
Has anyone upgraded their firmware to PK6 and attempted to root? I don't have any issues flashing TWRP with Odin. None whatsoever. When I flash a SuperSU zip or a PHH Superuser zip, I cannot get past the T-Mobile boot animation. It freezes every time. Once this happens I cannot boot to recovery. I can only boot to Download Mode. Hell, I can't even power down my device after I flash a root zip. Just curios if anyone has dealt with this issue. I have attempted to flash SuperSu zips starting with the 2.71 Beta up to the 2.78 SR5 with zero luck. I've also tried with PHH Superuser and I get the same results. Can anyone shed and light on the subject?
Sent from my SM-G928T using XDA-Developers mobile app
Click to expand...
Click to collapse
Here is the one I used. works great
Venal_System said:
Here is the one I used. works great
Click to expand...
Click to collapse
I tried that version too and I ended up with the same problem each time. I figured it out last night though. Im going to update my OP with the steps I had to take to get it working and that way if anyone upgrades to the latest PK6 firmware for their G928T and has this problem my thread is available with a solution.
Pixel XL running 8.0.0 OPR3.170623.007, developer options and USB Debugging are both on.
I was rooted for a while now, then I tried using one of my root-only apps and it told me it can't get root access.
I looked for SuperSU, which was missing.
I unrooted and rerooted using Skipsoft Unified Android Toolkit.
It flashed SuperSU 2.82 and flashed TWRP 3.1.1.1. The TWRP flashed just fine, but no matter how many times I flash SuperSU, it doesn't show up in my app drawer and the phone is still not rooted. I tried SuperSU 2.82 and the SR5 stable beta, neither worked. I also tried installing it through the Play Store after flashing it, it goes through the install process then just give me the option to install again, never fixes my issue.
Any idea on what I can do next?
edit: I updated to 3.2.0.0 and was able to root. Flashing the most recent beta and non-beta Magisk versions did not work, neither did installing the SuperSU APK. Once I updated to 3.2.0.0 I was able to root with Magisk just fine.
Flash the stock boot.img to both slots and reroot. Use SR5.
I would also advise to start by flashing the stock boot image. I would then boot twrp, flash twrp, then flash latest su.
If that doesn't work I would try going with the latest magisk zip (14.5)
I should have mentioned this, Unified Tool Kit flashed the factory boot image before releasing the latest TWRP and then flashing the most recent SuperSU. I did try flashing SR5 with negative results.
I'll give Magisk a try.
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
I followed 1,2,3,4,8, zero issues on 8.1.
I had a problem rooting with SuperSU. When i TWRP flashed it, it wouldnt show up in my apps, but my device was still rooted. For some reason the app just wasnt showing up so im using Magisk 14.5 instead...
DeviceManagent said:
I had a problem rooting with SuperSU. When i TWRP flashed it, it wouldnt show up in my apps, but my device was still rooted. For some reason the app just wasnt showing up so im using Magisk 14.5 instead...
Click to expand...
Click to collapse
Common issue. You can grab the app apk from inside the zip and install it.
I tried flashing both beta and non-beta Magisk versions and installing the SuperSU APK, nothing worked.
I saw that a new TWRP got released, 3.2.0.0. I flashed that and was able to successfully root. Thanks for your help, guys.
Hi!
I'm currently using flash rom and kernel. As I've always done so, I like to flash TWRP and then SuperSU to enjoy the little tweaks offered by root.
Since the last 8.1 update, I'm facing a few issues that in my opinion are correlated.
First, flashing TWRP works well, but it seems not to be systemless, i.e. when I reboot my device the proper way, TWRP disappears.
Secondly, when I try to flash the latest stable SuperSU zip through my working TWRP (it's a one shot...), the process gives me no error, but then on the first boot, I get stuck on the huge Google logo... The only thing I can do is re-flashing boot.img but obviously the SuperSU app didn't install...
What should I do? Install a beta SuperSU version? Try Magisk (honestly, I don't really like it...)
Thanks for your help and patience!
azertguigui said:
Hi!
I'm currently using flash rom and kernel. As I've always done so, I like to flash TWRP and then SuperSU to enjoy the little tweaks offered by root.
Since the last 8.1 update, I'm facing a few issues that in my opinion are correlated.
First, flashing TWRP works well, but it seems not to be systemless, i.e. when I reboot my device the proper way, TWRP disappears.
Secondly, when I try to flash the latest stable SuperSU zip through my working TWRP (it's a one shot...), the process gives me no error, but then on the first boot, I get stuck on the huge Google logo... The only thing I can do is re-flashing boot.img but obviously the SuperSU app didn't install...
What should I do? Install a beta SuperSU version? Try Magisk (honestly, I don't really like it...)
Thanks for your help and patience!
Click to expand...
Click to collapse
Do this, first boot twrp, don't flash it. Once booted flash SU 2.82 SR5. Then boot back into the bootloader from twrp and flash twrp. Works for me.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Do this, first boot twrp, don't flash it. Once booted flash SU 2.82 SR5. Then boot back into the bootloader from twrp and flash twrp. Works for me.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Huge thanks for this!!! I was having the exact same problem (boot hangs at Google logo) and this resolved it!
I noticed that afterwards in the apps drawer I could not find any SuperSU, but doing adb shell and then invoking su worked, so I then just installed the supersu app from the play store to handle prompts (it seems without the app, root is enabled silently and doesn't seem like that great of an idea).
-----------EDIT------------
After installing the app from play store, DO NOT allow it to update the supersu binaries! I ran into bootloop again after that, and had to re-flash SR5 again. Seems like that's the magical version to use!
You're right about having super su update. I had the same problem.
Edit, I just checked and I'm actually using SR3. SuperSu then updated those binaries without a problem.
Hi, thanks for the answers. What do you guys mean by 'booting twrp without flashing it'? What's the fastboot command?
azertguigui said:
Hi, thanks for the answers. What do you guys mean by 'booting twrp without flashing it'? What's the fastboot command?
Click to expand...
Click to collapse
fastboot boot (drag and drop twrp.img file here)
Sent from my Nexus 5X using Tapatalk
Well for the record, I did the following
Code:
fastboot boot twrp-3.2.1-0-bullhead
Then, I installed SuperSU downloaded here. I went back to fastboot and used
Code:
fastboot flash twrp-3.2.1-0-bullhead
but I still got stuck on the Google logo, meaning that my boot was corrupted or something... I then flashed the original Google boot.img
Code:
fastboot flash boot.img
and re-did the process of flashing SuperSU but I wisely chose to find a SR5 version of the file. I didn't flash TWRP after that and my phone booted normally with supersu.apk installed in it and the root privileges granted ... I don't know if I should try flashing TWRP again since my phone is working fine right now, but thanks anyway for the tip of booting to TWRP and not flashing it directly!