Hey, So today trying to install saved wifi password app (root). I realised there was no superSU. I mean i tried the root checker but it said "Problems with root" Then i reflashed superSU but no luck. Tried kingroot again but root failed. Safetrap is working fine. I dont know whats wrong. I am currently using latest cm11.
when u install cynogenmod with safstrap you might have forgotten to install supersu too, search in how to install cm11 in fire phone there you will know how to get root, may this helps.
Related
I followed all the instructions in this thread to root my HTC M8: http://forum.xda-developers.com/showthread.php?t=2699065&highlight=binary
I've got the TWRP recovery installed and did the "perm root" thing, which appeared to work as the SuperSU app was in the app launcher.
Now today when I tried to install xposed framework I discovered that the root apparently doesn't work. Opening up the SuperSU application gave this following warning:
"There is no SU binary installed and SuperSU can’t install it"
I googled around but didn't find anything concrete on what to do. I did find this one page that has a supposed fix in the comments, which I tried using but that hasn't done anything: http://www.theandroidsoul.com/root-new-htc-one-2014-m8/
I then thought I'd re-do the "perm root" step again, so I tried that using the all-in-one app, but now when I boot the phone up the SuperSU app doesn't show up in the app drawer at all and doesn't appear to be installed on the device at all, but the flashing step in the recovery doesn't give any errors at all.
So I'm stuck and don't know what to do now. I tried manually doing the flashing that the "perm root" step does but that hasn't given any other results either.
Searched the forum for "supersu binary" and found this thread, which had the solution to this problem: http://forum.xda-developers.com/htc-one-m8/help/help-accidentally-hit-ota-upgrade-t2852100
EDIT: Success!
Turns out I needed to re-flash my SuperSU binary from TWRP. I re-flashed the version I had first which actually removed the SuperSU apk. I re-downloaded it from Play Store, then flashed the 2.01 update. Runs like a charm.
Thanks to everyone for the help.
Click to expand...
Click to collapse
This worked for me. Just went to the store and got supersu. Upon running it, it tells me to upgrade, the Normal mode didn't work but the Recovery mode did. Now after that, root checker says I'm successfully rooted and another app I has can get root permissions too.
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
My phone is rooted with TWRP installed using the H811 extreme rom. Superuser is installed and seems to be working correctly for the most part. I'm prompted to grant access to most apps like TiBackup, Greenify, Amplify, and some others I have installed.
Problem is some apps are telling me my device has no root access. One of them is Quick Boot, which is installed with the custom rom I downloaded and installed. Another one is iFont. I don't even know if iFont will work on my G4 but I would like to give it a shot. When I use root checker from the play store it tells me my device has no root access? I tried uninstalling and re-installing SuperSu and it's no different. Certain apps working fine, others not, and root checker says no root access. Any ideas on what the problem could be?
Edit: Problem is fixed. I didn't have SuperSu installed to /system. I thought that would happen automatically if using TWRP to install the zip.
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
I recently bought, rooted, installed LeeDroid on HTC 10.
Im trying to figure out a few issues.
When i flashed Leedroid it added Superuser app. But I already had SuperSu. Do i need both or are they doing the same thing. I tried to install Adaway and it says it wasnt given root access. When i try to open SuperSu it says there is no SU binary. Do i just flash SuperSU again in twrp. Or should superuser be granting root?
Is Xposed safe to use with Leedroid?
How can i download directly to the sd card?
Once i flash a leedroid update can i delete the .zip?
Okay i reflashed SuperSU and it seems to be okay. Still not sure if thats the right thing since superuser was on there...Its runs through what seems 2 boot cycles now. Which is odd.
Hi there, I have a thread about xposed and a couple of modules in the guides section I think it is. Leedroids and venoms roms are both compatible with xposed.