I used the towelroot method and it seems to have gotten my phone rooted. A basic root checker confirms it. I installed SuperSU and when I open it, the app says the binaries need to be updated, however it fails to do that when I click "normal". I also installed the Wireless Tether for Root Users app (play version and the v3.2 beta when that wasnt' working). I've tried various configurations to no avail. It pops up asking for root access from SuperSU which I grant. When I start the tethering it says there are errors and to check the log file, however when I click on "show log" it says "unable to find log-file. File does not exist". I've also tried Barnacle WiFi tethering and it doesn't work either.
Any advice is appreciated.
Algo2 said:
I used the towelroot method and it seems to have gotten my phone rooted. A basic root checker confirms it. I installed SuperSU and when I open it, the app says the binaries need to be updated, however it fails to do that when I click "normal". I also installed the Wireless Tether for Root Users app (play version and the v3.2 beta when that wasnt' working). I've tried various configurations to no avail. It pops up asking for root access from SuperSU which I grant. When I start the tethering it says there are errors and to check the log file, however when I click on "show log" it says "unable to find log-file. File does not exist". I've also tried Barnacle WiFi tethering and it doesn't work either.
Any advice is appreciated.
Click to expand...
Click to collapse
until you have updated your binaries, rooted apps will do this....
if you have safe strap installed and working, you can download the updated SU 1.99 zip and flash it thru safestrap....other methods are talked about I believe in the towel root threads but I haven't done that myself
Algo2 said:
I used the towelroot method and it seems to have gotten my phone rooted. A basic root checker confirms it. I installed SuperSU and when I open it, the app says the binaries need to be updated, however it fails to do that when I click "normal". I also installed the Wireless Tether for Root Users app (play version and the v3.2 beta when that wasnt' working). I've tried various configurations to no avail. It pops up asking for root access from SuperSU which I grant. When I start the tethering it says there are errors and to check the log file, however when I click on "show log" it says "unable to find log-file. File does not exist". I've also tried Barnacle WiFi tethering and it doesn't work either.
Any advice is appreciated.
Click to expand...
Click to collapse
The version of SuperSU on the playstore is outdated, you have to do the folowing:
5. Download http://download.chainfire.eu/448/SuperSU/UPDATE-SuperSU-v1.99r5.zip
6. Use ES File Explorer https://play.google.com/store/apps/details?id=com.estrongs.android.pop or other unzipers and unzip the file
7. Open the /common folder in the unzipped file, and copy the SuperUser.apk to the /system/app/ folder in the root of the phone, confirm any SuperUser Access requests at this point.
You can also use the safestrap method:
Note: SafeStrap doesn't work with encryption turned on (disabled by default). If you don't know if you don't have encryption on/your phone isn't a business phone (in which case you shouldn't be doing this!!!) then you most likely don't have encryption on!!
5. Use this app to change your SELinux mode to "Permissive" https://play.google.com/store/apps/details?id=com.mrbimc.selinux, this is required to use SafeStrap
6. Install SafeStrap 3.72 APK from this thread http://forum.xda-developers.com/showthread.php?t=2448925, NOT 3.71 FROM THE VERIZON THREAD!!! Then click install in the SafeStrap App
7. Flash http://download.chainfire.eu/448/SuperSU/UPDATE-SuperSU-v1.99r5.zip, this step is NOT OPTIONAL, without this file, your SU Binaries will not update!!! (This is important!)
Credits to @npjohnson
SuperSU in the Playstore has been updated top 2.0 and is the latest, greatest version now.
Related
Hi XDA Community,
Your forums have helped me in the past and I spent some time scouring the posts before posting this one as I couldn't find anything that was specific to my issue. Since this is my first post, I thought that I would save a ping pong of responses, by being fairly expansive on what the problem is and what I have tried; thus hoping to pinpoint my issue a little quicker.
Device Details:
---------------------
Model Number: GT-I9100
Android Version: 4.0.3
Kernel Version: [email protected] #3
Build Number: IML74K.XWLP3
ROM Firmware: Samsung-Updates.com-GT-I9100_O2U_1_20120326173406_jiut50pyip.zip (via Samsung Kies)
Rooting Method / Kernel: Odin3v185 / CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5
Summary
--------------
Since the beginning of July 2012, I successfully upgraded from Gingerbread v2.3.6 to ICS v4.0.3 using Samsung Kies then initiated root privileges by using the CF-Root Kernel via Odin (versions shown above) - All has been working fine 100%.....
However, it appears that I seem to have lost my SU permissions and may have disabled my root access, even though my device was rooted and I would appreciate any assistance from anyone who might have time to shed some light on the situation.
Behaviour of Apps I have tried that require root
-------------------------------------------------------------------
SuperSU
SuperSU Pro v0.96 lists in the 'Apps' tab (denoted by a green # symbol) that I have granted all relevant Apps that require SU privileges. This includes AdFree, BusyBox Pro, Root Checker Basic, Root Explorer, SetCPU, Terminal Emulator, Titanium Backup, Triangle Away.
Terminal Emulator
Terminal Emulator displays the following and when I enter the su command at the prompt, I just see a carriage return with a grey block. In other words, I do not see the # symbol denoting I have su privileges.
a/local/bin:$PATH
[email protected]:/ $su
Root Explorer
Root Explorer no longer displays a directory listing and simply displays a pop up from SuperSU after tapping on Root Explorer, "Root Explorer has been granted superuser permission for an interactive shell." then the following message from Root Explorer itself:
"Root Explorer has not yet managed to obtain root access. Because of issues with Superuser, this often happens the first time the app is run but is usually fine from then on."
Root Checker Basic
Apart from the App stating "Please wait for Root Check to be complete. Systems appears to be running very slow" after tapping on the [Verify Root Access] button. It never seems to provide an output after a few minutes waiting. My conclusion is that it cannot get su permissions.
BusyBox Pro
SuperSU displays the message that Titanium Backup has been given root access, however I get the following message:
"Asking for root rights..."
Then after a few minutes I receive this most enlightening output:
"Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted and includes BusyBox and try again.
This attempt was made using the "/system/xbin/su" command."
I read somewhere that Titanium Backup uses it's own BusyBox installation and not the system wide BusyBox package so I went in to the Titanium Backup preferences and selected 'Troubleshooting settings' then chose 'Force system BusyBox' to see if my issue was a BusyBox specific problem. Again, it failed so not sure if it is BusyBox or my SU permissions that have somehow got corrupted or been disabled.
Additional Information
-------------------------------
Using 'ES File Explorer', I can confirm that the following file's exist at the appropriate location paths:
/system/xbin/su
/system/xbin/busybox
Conclusion so far
-------------------------
It appears that on the face of it that I have lost my root permissions, so I removed apps from SuperSU, then uninstalled the App (e.g. Root Explorer, Terminal Emulator et al.); then performed the rooting procedure again via ODIN and the CF-Root kernel. The process itself worked flawlessly and so after it rebooted, I installed the Apps in question from the Google Play Store again and they prompted to be granted SuperSU privileges. Unfortunately, the same issues arose where it appears that it cannot communicate with either the su command or BusyBox to do what it requires.
Does anyone have any ideas as the phone is fine apart from this and although performing a Titanium Backup backup around two weeks ago, I would sooner not have to wipe everything if I can help it. I wonder if it is an update that somehow confused things...Either way, I cannot use Titanium Backup to backup/restore due to it requiring SU/root permissions, of which I do not seemingly have anymore.
Any ideas please as I am scratching my head and have gone blurry eyed at spending hours viewing various forums and posts?
follow this steps:
1. Unroot your phone with the unroot method here
2. To be sure, unroot again with the method here
3. ROOT your phone again using Any of the Rooting methods in the links provided in step 1 or 2.
Good luck
ICS 4.0.3 Lost su permissions even though device was rooted - Resolved
:good: Issue Resolved :good:
Many thanks for contributing to my issue. I had come across the post before in your links and although the directions were not completely related, there was a section pertaining to a zip file that I must have missed.
Conclusion
----------------
As can be read in the post, I was unsure if my issue related to losing root, a possible corrupt su file itself or BusyBox. As you will see on the link below, Busy Box actually creates hundreds of symbolic links (symlinks) and due to my perhaps overzelous approach to wanting a quick fix; I must have inadvertently created too many links with different versions of Busy Box and therefore when an App that was correctly added and granted SU permissions within SuperSU, when it then communicated with Busy Box / su to authenticate; I can only imagine it got confused and was lost with all the dead symlinks. The net result was that although SuperSU stated that it had granted permissions to the Apps requiring root, it never got to communicate with the su file contained within /system/xbin. I hope that makes sense, well at least I am pretty sure that is what happened.
Solution
------------
Firstly, I cleared all entries contained within SuperSU and therefore removing all Apps from being granted with root access (they didn't have it anyway at the moment).
I saved the zip file contained at the following link on to my external SD card and choosing to 'install zip from sd card' within the CWM Recovery (Volume Up + Power + Home button); effectively this uninstalls Busy Box completely from your device, including hundreds of symlink files - including many which in my instance was causing issues with Apps that required root to function correctly.
Busy Box Uninstaller v1.0 here
I restarted my device and downloaded Busy Box from Google Play Store and when I opened Root Explorer and the other aforementioned Apps shown in this post, they prompted to be granted root permissions (SuperSU) and voila....it worked ! :good:
I hope this may help other droid users experiencing similar symptoms.
Here simple tool for busybox installation. This is specially designed for stock ROM and kernel users. Without busybox many root app may not work correctly so made a simple one Click Tool for same. Also it have one more function to enable Broeser secret mode with password/fingerprint.
This application requires root.
1.Intall attached Busybox MM apk
2.open app - grant su
3.read status of busybox. And select to install if it is not installed.
4.once busybox installed, restarting app should show new status.
5.Also added small Tool to enable browser secret tab (with password / fingerprint) but that require to have busybox. So first install busybox before activating it.
Really I couldn't test this so recommend to make nandroid (at least before some report comes)
Cant install busybox, every time i install it and reboot it's gone.
Tamir_Hazut said:
Cant install busybox, every time i install it and reboot it's gone.
Click to expand...
Click to collapse
I have the same issue with Norma rom (Note 7 port). After restart I need to reinstall again.
I'm having one issue that I can not seem to fix. My Nexus 9 volantis wifi is showing that it is rooted when I check the root checker by Super user from the google play store. It says Root Access: Device is rooted. The next line down says Super User: SU NOT FOUND. I am using the current 2.74 beta. I have the latest vendor image MOB3OM. I am running the latest Pure Nexus 6-21-2016 build. I'm running the latest GAPPS and fire and ice kernel. When I go to an app that needs SU permission I get the pop up that ask me to grant permission. So I know that my device is partly rooted. When I try to turn on the root explorer function in ES file explorer it says, "Sorry test failed. This feature can not run on your device." I originally started with stock factory image. I rooted and installed recovery with Nexus Root Toolkit. TI backup tells me "Mount namespace seperation" settung in SUPERSU might not work reliably on some platforms. What am I doing wrong?
You're not doing anything wrong. I just checked that app and got the same thing you did. I think it's an issue with the app. My device is definitely rooted. Use the checker by joeykrim
Sent from my Nexus 9 using XDA Free mobile app
The OP got a reply in the SuperSU thread.
Enable Compatibility Mode of SuperSU, Or use a different root explorer app.
Solid Explorer File Manager is currently on sale, get the unlocker from within the app.
Edit: - Sale has finished.
Just flashed SuperSU v2.76 with out Compatibility Mode and can confirm Solid Explorer can get root access.
I don't know whereto put this thread although ths seems like a right forum,anyway, I have a problem with this persistent king root, and I want to remove it but these chinese 'communist' devs won't let me. I tried the following things:
1 Manually delete kinguser app from /system/app part, and then install supersu from play store. The result it just says what su binary is occupied.
2. Install BusyBox. Download this popular replace_kinguser_with_supersu_2.4.zip and 2.0 files (this ones with mrw folder) and run it. Supersu installs, asks for update and su binary update. Yes, yes, looks great, but doesn't work. When running any root app, like terminal emulator, nothing happens, no auth prompt pops up.
3. Reroot with older kingroot version (4.5), do the same as 2. Same result
4. Set auth mode in Supersu settings to allow/deny, when oddly it works. Allows or denies immediately, and I can find this in Supersu's log.
So, everything seems working fine except what Supersu doesn't want to show me my root promts when I need them.
If any information about my device needed, I will be happy to provide it. For starters, my device is ITELL K3300, I am not sure what else coud be needed if you want to help?
Hi,
I need to root a Zebra TC56 to install some other apps that require rooted Android. There is very little information in the way of rooting the Zebra TC56. I 'm pretty set on using Chainfire's superSU, but I cannot find any information on whether it will work on this hardware. Does anyone know if the superSU works on this device with Android 6? If not, is there another Root Tool that will work.
Any advice appreciated.
THANK YOU!
VK
1. Install BusyBox applet-suite what contains the SU-binary
2. Install latest SuperSU APK
jwoegerbauer said:
1. Install BusyBox applet-suite what contains the SU-binary
2. Install latest SuperSU APK
Click to expand...
Click to collapse
BusyBox installed fine.
SuperSU will not install all the way. When I select to root, it says root not detected and then, "How to Root", which launches my browser to a site that no longer exists.
Now what?
Thank You!
edit: Still stuck at this point. I read about TWRP, KingoRoot and some other random apps. I cannot brick this touch computer; it is $1600; that would be a very expensive brick. :crying:
So, I have no idea if I am right, but maybe I need to open the terminal emulator and "su" install the SuperSU apk. But I have no idea and I don't want to experiment. Hopefully, someone can help me.
@vidarr_kerr
Don't confuse things:
SU is the super user who unrestrictedly can perform any operation on Android OS. As soon as SU got installed Android is rooted! Again: BusyBox you successfully installed contains the su applet.
SuperSU is merely a root-manager app: it maintains a database where is stored what app can act as super user. SuperSU app doesn't grant super user rights.
BTW:
TWRP has nothing to do with rooting device's Android, as this is also true with Magisk.
The device is still not rooted after the "BusyBox Installer (No Root)", from your link, was installed.
I installed BusyBox, I followed the directions to then copy a command, then open a terminal, paste the command in and hit enter, then nothing happened. SuperSU was not installed with it.
So, as you told me, I then installed the latest SuperSU APK from your link. It says it installed, but when I run it, it says root not detected and then has a link named, "How to Root", which launches my browser to a site that no longer exists.
I followed what you said. Where did I go wrong?
Thank You!
You didn't get it. Sorry to say this.
jwoegerbauer said:
You didn't get it. Sorry to say this.
Click to expand...
Click to collapse
Didn't get what?
I installed the BusyBox you gave me the link to.
I semi-installed the SuperSU you gave me the link to.
SuperSU did not fully install, because the Android is NOT rooted..
BusyBox had no SuperSU as part of it --the file you said to use even says "BusyBox Installer (No Root)".
(That should have tipped me off right away you had no clue, but I thought maybe you knew something.
So, you gave me the links for both of those files and it doesn't work.
I don't think you have any idea what you are doing; and shouldn't be explaining things you do not understand.
The "no root" BusyBox, does not include SuperSU.
If it did, why did you give me the link for the separate SuperSU file?
All the "no root" BB did was install a terminal emulator (with no su abilities).
The SuperSU didn't install, because the Android is NOT rooted.
If the Android WAS rooted, SuperSU would run and allow me to grant su privilges to the apps that require it to work.
You basically just wasted my time.
I would have just said "thank you" and moved on, but you are rude.
You don't know what you are talking about either.
Hopefully, this will help others, to not do what you say to do.
vidarr_kerr said:
Didn't get what?
I installed the BusyBox you gave me the link to.
I semi-installed the SuperSU you gave me the link to.
SuperSU did not fully install, because the Android is NOT rooted..
BusyBox had no SuperSU as part of it --the file you said to use even says "BusyBox Installer (No Root)".
Click to expand...
Click to collapse
You're right: BusyBox (No Root) doesn't come with SU-binary. Wasn't aware of this. I misinterpreted APK's title. Pitty.
ERRARE HUMANUM EST ( To err is human ).
Installing BusyBox containing SU-binary requires your device's bootloader got unlocked before, because Android's /system partition gets modified. Hence manage to unlock device's bootloader as 1st thing of all things. Good luck.
DL BusyBox latest: https://github.com/meefik/busybox/releases/download/1.31.1/busybox-1.31.1-46.apk
My last 2 cents here: SuperSU and SU binary are totally different things.