i did the tutorial on galaxys4root.com and it worked but when i open super user it says it needs to update the binary and i hit install but it has an error does anyone know what i have to do to make my superuser work properly thanks
Sounds like you aren't rooted. Install Root checker basic and see what it says.
Related
Hello,
I rooted my 8.9" and lose root after i installed busybox. Right now, i cannot install SU binary. I tried factory reset, unroot, and reroot without any success. Is there a way i can install SU binary manually?
Thanks.
anyone???
It appears that I will have to live with it.
Thanks.
auky said:
It appears that I will have to live with it.
Thanks.
Click to expand...
Click to collapse
I don't know what or how you did what you did. You won't get many answers without providing specific examples.
I for one have NEVER heard of ANYONE losing root from BusyBox, but everyone I know, including myself, uses BusyBox Pro v. 10.5 currently. Most of the people I know also use SuperSU from Chainfire. Generically saying tha some busybox installation messed with some generic root or SU installation/binary, really does not give anyone much to go on.
You can apply the root exploit again. There is no issue with that, or you can use adb to copy the su binary over, set permissions & ownership & the cp it to the correct directory.
At any rate, there are too many possibilities & possible solutions depending on what you did & how you did it.
GSLEON3 said:
I don't know what or how you did what you did. You won't get many answers without providing specific examples.
I for one have NEVER heard of ANYONE losing root from BusyBox, but everyone I know, including myself, uses BusyBox Pro v. 10.5 currently. Most of the people I know also use SuperSU from Chainfire. Generically saying tha some busybox installation messed with some generic root or SU installation/binary, really does not give anyone much to go on.
You can apply the root exploit again. There is no issue with that, or you can use adb to copy the su binary over, set permissions & ownership & the cp it to the correct directory.
At any rate, there are too many possibilities & possible solutions depending on what you did & how you did it.
Click to expand...
Click to collapse
Hi GSLEON3,
You have given me hope. Thank you for the respond. I rooted my HDX 8.9 with no issue. Without knowing if I have busybox, I downloaded and installed the attached busybox apk. After that, I lose root. When I open SuperSU, I was asked to install SU binary, but when I click "Normal", the SU binary installation will fail. I tried unrooting and rerooting (with Bin4ry method as well as manual) without any success. Error messages such as "must be SUID to work properly" when I tried unroot and reroot. Guess i lose write ability. I will really appreciate it if you can tell me how to adb to copy SU binary or help me get root back.
Thanks.
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.)
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
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.