Issues with SuperSU - Nexus 7 (2013) Q&A

I just flashed the latest twrp and the SuperSU 5.0 image coming from stock 5.0.2 last night and was having trouble with granting permissions, it would just get stuck and wouldn't let me choose anything. I went ahead and backed up in twrp and flashed a custom rom and all went well. Although I still have the sticking on the permission windows and the SuperSU app isn't showing up in the app tray and won't allow me to open it from the play store. I was recommended to flash the SuperSU 2.45 update which I did successfully in twrp and I'm still getting stuck on the permission window, any help or suggestions I would be very much appreciate. Thanks!
Edit: fixed it, just needed to uninstall and reinstall SuperSU! Thanks y'all

whmgreen said:
I just flashed the latest twrp and the SuperSU 5.0 image coming from stock 5.0.2 last night and was having trouble with granting permissions, it would just get stuck and wouldn't let me choose anything. I went ahead and backed up in twrp and flashed a custom rom and all went well. Although I still have the sticking on the permission windows and the SuperSU app isn't showing up in the app tray and won't allow me to open it from the play store. I was recommended to flash the SuperSU 2.45 update which I did successfully in twrp and I'm still getting stuck on the permission window, any help or suggestions I would be very much appreciate. Thanks!
Click to expand...
Click to collapse
I am using stock L 5.0.2, and used Chainfire Auto Root to flash it on 5.0/.1/.2 without issue. I am running SuperSU 2.40 currently, and it does not appear to have an update pending on the Play store.
Did you try using 2.45 on a clean install that had not previously used 5.0? Wondering if something is getting gummed up from that, and sticking around on the older version.
Maybe try a fresh clean install on stock or whatever ROM you want and try 2.40/2.45 first before 5.0.

Related

[Q] SuperUser Issues for the S4 SGH-M919

I have rooted my S4 with the motochopper and it keeps on telling me to update the Superuser from clockworkmod and i updated thru the plays store and it still asks for an update how can i fix this? and if i install the other superuser by chainfire it doesnt have the SU binary installed.... please help
re: SuperSU
MrDiaz said:
I have rooted my S4 with the motochopper and it keeps on telling me to update the Superuser from clockworkmod and i updated thru the plays store and it still asks for an update how can i fix this? and if i install the other superuser by chainfire it doesnt have the SU binary installed.... please help
Click to expand...
Click to collapse
Your problem is almost fixed, here is what you need: http://batakang.com/ftp/SGH-M919/MDB-SetUIDOff.zip
Flash it using CWM or TWRP recovery and reboot the phone and you will see the magic!
After doing this go to the play store and see if there is an update of SuperSU if there is then install it and reboot the computer.
(do not install superuser).
Good luck!
Misterjunky said:
Your problem is almost fixed, here is what you need: http://batakang.com/ftp/SGH-M919/MDB-SetUIDOff.zip
Flash it using CWM or TWRP recovery and reboot the phone and you will see the magic!
After doing this go to the play store and see if there is an update of SuperSU if there is then install it and reboot the computer.
(do not install superuser).
Good luck!
Click to expand...
Click to collapse
It still says it doesnt have the binary installed but it still grants any rooted applications lol.... ill keep messing around with it maybe i did a mistake when i did it on the motochopper
The latest version of superuser does not play well with twrp... Titanium Backup, CPU Sleeper, etc..still have superuser access... After flashing I just chose ignore but if you select 'fix' it will restore the old version of superuser. To update binary, I flashed Phantom kernel v1 from Infamous S4 thread. That fixed me up.
Your are the BEST news you have gave me how to fix the problem on t-mobile binary problem to root the galaxy s4 .IT DID WORK THANK YOU VERY MUCH the other top dogs that they root their phones dont know about this fix in you tube.. thank u again.
Misterjunky said:
Your problem is almost fixed, here is what you need: http://batakang.com/ftp/SGH-M919/MDB-SetUIDOff.zip
Flash it using CWM or TWRP recovery and reboot the phone and you will see the magic!
After doing this go to the play store and see if there is an update of SuperSU if there is then install it and reboot the computer.
(do not install superuser).
Good luck!
Click to expand...
Click to collapse
Sir, I love you. I searched for hours trying to figure this out.
sent from my jelly bean droid (SGH-M919)

[Q] Lost root and Recovery with TWRP after Update

Okay be gentle...
After the last update to JSSR15R I lost root and SU, doing the rebbot into recovery (vol down + power button) TWRP launches but when I select to go to recovery via the vol buttons and select it with the power button, all I get is the exclamation point android.
While I'm not a total idiot (debatable of course), is there a way to re-establish root and su without wiping off 15gigs of music and playlists and starting from scratch? Rooting the Nexus 7 (flo) the first time (at least for me) was a fight I eventually won, but for me it was a fight. tia Tutor
Same thing happened to me. I installed TWRP via goomanager. Then, I flashed SU update. Now I'm back rooted and going strong.
Like previous poster mentioned, just reinstall twrp and su.
Your bootloader should already be unlocked. Unlocking the bootloader is the only step that causes you to lose data.
Reinstalling twrp and su will not cause you to lose data, unless you had locked after installing them last time, and now need to unlock again to reinstall.
I reinstalled TWRP via the playstore but while it shows my directory file structure it won't install my copy of Update SuperSU 1.5.1.zip also I went to install goomanager but the descrription says you have to have root prior to installing.
As a sidenote while in TWRP if I go into rebooting the device none of the actions work except when I hit the "Bootloader" option the a error box pops up stating the option isn't available on your device. Tutor
Only way I know of to install TWRP is go to the TWRP web site and download it from there to your PC. You will find flash instructions on the web site.
Sent from my Nexus 7 using xda app-developers app
Download Goo manager from Playstore. Choose Flash Roms, It will tell you that you need a custom recovery to do this and ask if you have one or would like Goo to find one. Choose find one for me and it will download and install TWRP 2.6.3.0. After said process is complete flash SU update. Profit..
Same happened to me, but I reflashed TWRP and root access... Just curious how come that never happened with Clockwork Mod recovery being lost after applying an update to the system on the old N7.
If you don't want to lose root or recovery, it is very simple.
Boot to twrp
Install OTA update.zip
Install SuperSU 1.55 update.zip (Prior to reboot, use 1.55 as 1.65 has issues)
You will maintain root and keep twrp if you do it in this exact order.
sfhub said:
If you don't want to lose root or recovery, it is very simple.
Boot to twrp
Install OTA update.zip
Install SuperSU update.zip (Prior to reboot)
You will maintain root and keep twrp if you do it in this exact order.
Click to expand...
Click to collapse
Can TWRP generally find the latest OTA update.zip on it's own?
Lastb0isct said:
Can TWRP generally find the latest OTA update.zip on it's own?
Click to expand...
Click to collapse
Nope, download the ota manually and place on your virtual sdcard, then boot to twrp and select the file for install
installing through goomanager didn't work for me. It would say it installed but wouldn't really install. I did it using the fastboot method instead and that seemed to work fine.
Well nothing I seemed to do would allow me to re-root the Nexus 7 after the 15R update, I finally went as re-rooted from scratch using the sticky post at the beginning of this subdivision forum for the Nexus. Back up and running in root and su... thx to all those that attempted to help me thru this
CallMeTut said:
Well nothing I seemed to do would allow me to re-root the Nexus 7 after the 15R update, I finally went as re-rooted from scratch using the sticky post at the beginning of this subdivision forum for the Nexus. Back up and running in root and su... thx to all those that attempted to help me thru this
Click to expand...
Click to collapse
I used Wugfresh tool. Everything worked until I flashed the updated SU 1.65. I could never get root. I read earlier that others were using SU 1.5, so I manually went back into TWRP and flashed SU 1.5 and bam, had root! Then SU upgraded itself via the play store to the newer version. Go figure!
jyams said:
I used Wugfresh tool. Everything worked until I flashed the updated SU 1.65. I could never get root. I read earlier that others were using SU 1.5, so I manually went back into TWRP and flashed SU 1.5 and bam, had root! Then SU upgraded itself via the play store to the newer version. Go figure!
Click to expand...
Click to collapse
The update.zip for SU 1.65 is broken. A "placeholder" install script was included that does nothing.
IMO SuperSU 1.55 is the best version to use right now. The install script works, it doesn't mess with a bunch of file permissions for your *other* files in /system to support the new ota survival mode, and it has the fix for the problem that used to break the OTA installs.

[Q] Super SU binary update issues

I used the CF-Auto-Root package, which contained Odin3-v3.07.exe and CF-Auto-Root-lt01wifi-lt01wifixx-smt310.tar.md5, to root my Samsung Galaxy Tab 3 8.0 (SM T310) running Android 4.4.2 stock. This root installed some version of SuperSu and no custom recovery. I was able to run SuperSU and installed a couple of root apps like Greenify and Titanium BU. No problem. Then, after I purchased the Pro version and rebooted, SuperSU started requesting a binary update. The Normal update failed. No custom recovery was included with the root but I tried that option but it also failed with a signature verification error. After the signature error SuperSU did run and I was able to go into settings and did the uninstall/reinstall. Uninstalled the pro key and then reinstalled SuperSU from Play Store. This time when it asked to update binary, I chose Normal and it succeeded! I did not reinstall Pro. That lasted until I did the first power off. When it came back up, it asked to update binary. It still seems to function, as I did install another root app and it granted access. Any ideas where I go from here?
cv91913 said:
I used the CF-Auto-Root package, which contained Odin3-v3.07.exe and CF-Auto-Root-lt01wifi-lt01wifixx-smt310.tar.md5, to root my Samsung Galaxy Tab 3 8.0 (SM T310) running Android 4.4.2 stock. This root installed some version of SuperSu and no custom recovery. I was able to run SuperSU and installed a couple of root apps like Greenify and Titanium BU. No problem. Then, after I purchased the Pro version and rebooted, SuperSU started requesting a binary update. The Normal update failed. No custom recovery was included with the root but I tried that option but it also failed with a signature verification error. After the signature error SuperSU did run and I was able to go into settings and did the uninstall/reinstall. Uninstalled the pro key and then reinstalled SuperSU from Play Store. This time when it asked to update binary, I chose Normal and it succeeded! I did not reinstall Pro. That lasted until I did the first power off. When it came back up, it asked to update binary. It still seems to function, as I did install another root app and it granted access. Any ideas where I go from here?
Click to expand...
Click to collapse
Use Odin to install a custom recovery; then flash the latest SuperSu zip in recovery.
Sent from my SM-T310 using Tapatalk
gr8nole said:
Use Odin to install a custom recovery; then flash the latest SuperSu zip in recovery.
Sent from my SM-T310 using Tapatalk
Click to expand...
Click to collapse
Will that work if the tablet is already rooted and SuperSU is already installed? SuperSU is working as long as I don't run the UI. Sorry, I am new to this rooting stuff. Thanks for the response.
I have P5210 Tab3 10 Wifi
We used chainfire=> http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip
And in our model yes we even write over old not working su. KK 4.4.2 does not like to be rooted and kills it. As gr8nole said. we too are force to install UPDATE-SuperSU-v2.02.zip on recovery. This one does survive KK attacks. Clearly this one, you installed from Recovery. But you can go to
http://forum.xda-developers.com/showthread.php?t=1538053
For other installation methods

SuperSU on CM13

Hey all. I just flash that ROM. Works really nice. But I can't find SuperSu installed. Also apps which needs root permission didn't worked. I just go do download SuperSu from market and the program shows me an error told me to reboot and try again. Can you please help me? Thanks in advance.
Erosa13 said:
Hey all. I just flash that ROM. Works really nice. But I can't find SuperSu installed. Also apps which needs root permission didn't worked. I just go do download SuperSu from market and the program shows me an error told me to reboot and try again. Can you please help me? Thanks in advance.
Click to expand...
Click to collapse
You ALREADY HAVE root with CM-SU. To enable it, just go to developer option and give root permissions to app. Some SuperSU's versions are incompatible afaik. CM-SU preinstalled is just fine.
Erosa13 said:
Hey all. I just flash that ROM. Works really nice. But I can't find SuperSu installed. Also apps which needs root permission didn't worked. I just go do download SuperSu from market and the program shows me an error told me to reboot and try again. Can you please help me? Thanks in advance.
Click to expand...
Click to collapse
SuperSU is an issue for itself. Installing 2.74 using TWRP on my G3 lead to boot problems because of a boot image patch that SuperSU installs. If I restore boot partition before rebooting, SuperSU doesn't install. Using Play Store version fails to install su binaries.
Conclusion: use CM own root. It works nicely, just lost FolderMount but, well, I prefer that instead of losing phone.
Mnldr/D855/16G/CM13
Meneldur said:
SuperSU is an issue for itself. Installing 2.74 using TWRP on my G3 lead to boot problems because of a boot image patch that SuperSU installs. If I restore boot partition before rebooting, SuperSU doesn't install. Using Play Store version fails to install su binaries.
Conclusion: use CM own root. It works nicely, just lost FolderMount but, well, I prefer that instead of losing phone.
Mnldr/D855/16G/CM13
Click to expand...
Click to collapse
Have you try this method http://forum.xda-developers.com/lg-g2/general/bump-supersu-t3273251
CustomPatcherScript_Bump.zip + UPDATE-SuperSU-v2.65-20151226141550.zip
But it's also can cause reboot loop
Do backup before doing flash that script
That worked fine with my D855 32Gb + CM13

Problems post super su install

So I installed TWRP and then moved on to install super su which is where the problem started. First I attempted to install SR1-SuperSU-v2.78-SR1-20160915123031.zip. Everything ran but after it led to a boot loop. After that I realized I had tried to install the latest file but not the latest STABLE file, so I then tried to install UPDATE-SuperSU-v2.78-20160905010000.zip to no avail. I then noticed when I go in to download mode i get a "FILE /mnt/media_rw/ext_sd/OPJAIMG.zip File Not FOUND" error on the bottom. Any idea how i could sort this out? (like a fool I did not make a backup before doing this) I downloaded the RUU (RUU_HIMA_UL_M60_SENSE70_ATT_MR_Cingular_US_3.38.502.17) but I wanted some advice before i do that so i don't mess it up more.
ATT m9
os 3.38.502.21
s-on
TWRP 3.0.2-0
Download Mode checks for this file to update the Firmware. If you are not planning on updating that, you don't need that file on your Phone. It's more a notice that an actuall error
Alright, that's encouraging. Any idea why i would get a boot loop after trying to install super su though? That's where I'm stuck right now. I'm not opposed to going back to stock and starting over if that's the only option. I just want my phone to be usable again.
Well if it installed in Systemless mode, it can cause a bootloop for a while, you might just need to be patient. Otherwise, i would maybe try an older version of SuperSu. I think 2.76 was pretty safe to install
I let it boot loop over night so no dice there. I'll give the older version a try. Hopefully that works.
No luck with 2.76. It boot looped for a half hour. Any other thoughts?
erics87 said:
No luck with 2.76. It boot looped for a half hour. Any other thoughts?
Click to expand...
Click to collapse
Yes, don't flash any newer version than 2.65. Updating via the play store afterwards is safe, though.
Sent from my HTC One S using XDA Labs
I had the exact problem, lucky enough i could fetch some log files during boot and sent them to chainfire, maybe we will see a fix someday
SuperSU 2.65 seems to be the latest version working in system-less mode on the HTC One M9, updating through Google Play Store works fine tho.
I will look for the log in a couple minutes and post it here for all that are interested
But don't worry, atleast it didn't brick our phone

Categories

Resources