I had rooted Celkon Q 500 with some method, I do not remember exactly. May be Root Genius. For some reason I unrooted using SuperSu. I wanted to re-root. But I am finding it difficult. ( I have not got any OTA update after rooting)One root checker says it is rooted, another says it is not. I can explore files in root explorer of ROM Tool Box Pro I had installed earlier. But I can not reboot through ROM Tool Box Pro. One root checker provided me this information : subinary available via $PATH null null, then in the next line it says : -rwsr -sr -x root root, subinary location is system/bin/su. Second thing it says : I have installed two busybox one at (a) data/local/busybox and another at /system/xbin/busybox. I had tried to un-install and re-install SuperSu and Busybox 2/3 times. Then after opening Supersu I got an erratic message : su binary needs updating and when Itried to update it , it failed several times. One root checker app says ADB root is available, Root Genius says root available. So, I am quite confused. I do not know how to go about it. I will be thankful, if somebody guides me in right direction.:crying: (I also found a root checker app said SELinux enforcing.)
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.
Hi there,
I have a Rockchip RK3188 Tablet with Android 4.2.2, which I need to root ON DEVICE. Actually, the device was already rooted (using a Laptop via the adb bridge), so I already have busybox installed and I have one of my own apps in /system/app. However I managed to delete the su program (yeah great!) and therefore don't have root access any more. I know I can easily root the device again if I connect it to my laptop again, but that is not possible, because the device is at my parent's place and I can't go over there any time soon.
Therefore I want to root the device just with an app. Actually I would only need to copy su to /system/xbin.
These are the things I already tried (without success):
Framaroot (doesn't work, because framaroot does not support Rockchip tablets)
Writing my own app, which contains su in the assets and using this su for temporary root
Using adb (on the device) for a local connection (adb connect localhost), because if I connect from my PC I automatically have root (doesn't work because Android 4.2.2 has increased security on adb)
Start telnetd via busybox and then execute my commands via nc (doesn't work, because I can't start telnetd in a way that it ends up with a root shell)
Any other ideas?
My last idea is, that I could maybe gain temporary root access with the app I already have in /system/app. Basically this would be similar to the Master Key Exploit, except that I do not have to fiddle around with the apk and instead install it normally. However I don't know how to continue from that point. I know, I have special permissions if I have an app in /system/app, but which permissions are that? And how can I use those permissions to make /system writeable (and copy my su file there)?
Thank you for your help,
Tobias
ToBe_HH said:
Hi there,
I have a Rockchip RK3188 Tablet with Android 4.2.2, which I need to root ON DEVICE. Actually, the device was already rooted (using a Laptop via the adb bridge), so I already have busybox installed and I have one of my own apps in /system/app. However I managed to delete the su program (yeah great!) and therefore don't have root access any more. I know I can easily root the device again if I connect it to my laptop again, but that is not possible, because the device is at my parent's place and I can't go over there any time soon.
Therefore I want to root the device just with an app. Actually I would only need to copy su to /system/xbin.
These are the things I already tried (without success):
Framaroot (doesn't work, because framaroot does not support Rockchip tablets)
Writing my own app, which contains su in the assets and using this su for temporary root
Using adb (on the device) for a local connection (adb connect localhost), because if I connect from my PC I automatically have root (doesn't work because Android 4.2.2 has increased security on adb)
Start telnetd via busybox and then execute my commands via nc (doesn't work, because I can't start telnetd in a way that it ends up with a root shell)
Any other ideas?
My last idea is, that I could maybe gain temporary root access with the app I already have in /system/app. Basically this would be similar to the Master Key Exploit, except that I do not have to fiddle around with the apk and instead install it normally. However I don't know how to continue from that point. I know, I have special permissions if I have an app in /system/app, but which permissions are that? And how can I use those permissions to make /system writeable (and copy my su file there)?
Thank you for your help,
Tobias
Click to expand...
Click to collapse
are you rooted check with root checker if yes(as you alredy said)
install super su or super user to gain root acces controls
but iam not sure from your question you are rooted or not or are you trying to root
P.S deleting super su will not unroot you
sangalaxy said:
are you rooted check with root checker if yes(as you alredy said)
install super su or super user to gain root acces controls
but iam not sure from your question you are rooted or not or are you trying to root
P.S deleting super su will not unroot you
Click to expand...
Click to collapse
Root checker says: "Sorry! This device does not have proper root access."
Right now, I am NOT rooted. So the device WAS rooted and then /system/xbin/su was deleted. Meaning: everything else is in place (SuperUser, Busybox, etc.) but I cannot execute anything as root, because I cannot switch the user to root (what su does). Although I am not really unrooted, I cannot do anything any more. So basically I would like to re-root my device.
The goal is to get fully rooted again.
ToBe_HH said:
Root checker says: "Sorry! This device does not have proper root access."
Right now, I am NOT rooted. So the device WAS rooted and then /system/xbin/su was deleted. Meaning: everything else is in place (SuperUser, Busybox, etc.) but I cannot execute anything as root, because I cannot switch the user to root (what su does). Although I am not really unrooted, I cannot do anything any more. So basically I would like to re-root my device.
The goal is to get fully rooted again.
Click to expand...
Click to collapse
I don't think you can root without any pc
If your phone has recovery just flash the root files :thumbup:
Sent from my Xperia Live with Walkman using xda app-developers app
ToBe_HH said:
Root checker says: "Sorry! This device does not have proper root access."
Right now, I am NOT rooted. So the device WAS rooted and then /system/xbin/su was deleted. Meaning: everything else is in place (SuperUser, Busybox, etc.) but I cannot execute anything as root, because I cannot switch the user to root (what su does). Although I am not really unrooted, I cannot do anything any more. So basically I would like to re-root my device.
The goal is to get fully rooted again.
Click to expand...
Click to collapse
Have you tried looking in /system/bin/su instead of /system/xbin/su
i am trying to root some cheap tablet. its based on arm9 wm8800 dual core ,running android 4.4. in developers options there is option to set super user permission (always ask,etc) but it doesnt do anything,when i ran root checker it shows its not rooted,and when i installed superuser from play store it says something about SU binary also apps that require root wont work etc.. so i tried several other options.. after running z4root there's no more su binary problem. root checker shows its not properly rooted,it shows that su binary is there in system/xbin/su but there's red text with some permissions .like i need to fix them,but dont know what to do.. i have rooted many devices,but this is hard.. any help??
After rooting we instal busybox and SuperSU (or Superuser) and avail the benefits of rooting. When we unroot through SuperSU, is it possible that 'su' still remains inside '/system' folder? I came across a strange phenomenon : I rooted my Celkon Q 500 ( by Root Genius or One-click method or something else, I do not remember) and installed many root apps. After somedays, I decided to unroot, I uninstalled super su, busybox. Then, I tried to root it again. But, I noticed that one root checker says ur device is rooted(specifically through Root Genius PC software I got the message rooted and pressed the 'unroot' button, but it said failed), 2nd root checker says it is non-rooted, 3rd one says it has root access through ADB. I checked 'su' is present in some folder inside '/system', which could not be deleted , because I think, I do not have RW privilege. I had tried many method to root it again, but all failed. When I open Supersu, it throws an immediate message that 'su binary' needs to be updated and when I try it fails everytime. Can anyone meke me understand, what is the real proble.? Celkon Q 500 is Broadcom chip based, running android 4.4.2. Also I found One message in the root checker that "SELinux enforced".
Eversmile23 said:
After rooting we instal busybox and SuperSU (or Superuser) and avail the benefits of rooting. When we unroot through SuperSU, is it possible that 'su' still remains inside '/system' folder? I came across a strange phenomenon : I rooted my Celkon Q 500 ( by Root Genius or One-click method or something else, I do not remember) and installed many root apps. After somedays, I decided to unroot, I uninstalled super su, busybox. Then, I tried to root it again. But, I noticed that one root checker says ur device is rooted(specifically through Root Genius PC software I got the message rooted and pressed the 'unroot' button, but it said failed), 2nd root checker says it is non-rooted, 3rd one says it has root access through ADB. I checked 'su' is present in some folder inside '/system', which could not be deleted , because I think, I do not have RW privilege. I had tried many method to root it again, but all failed. When I open Supersu, it throws an immediate message that 'su binary' needs to be updated and when I try it fails everytime. Can anyone meke me understand, what is the real proble.? Celkon Q 500 is Broadcom chip based, running android 4.4.2. Also I found One message in the root checker that "SELinux enforced".
Click to expand...
Click to collapse
reinstall super su from play store go to settings in super su app and unroot there
selinux enforced means that your kernel is not permissive. has nothing to do with root
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.