My phone was working fine until this morning when I tried to start wifitether and got the message "no SU binary installed" Does this mean I lost root somehow and have to root it again?
ilogik said:
My phone was working fine until this morning when I tried to start wifitether and got the message "no SU binary installed" Does this mean I lost root somehow and have to root it again?
Click to expand...
Click to collapse
Its possible that you removed root permissions solely for wifitether by accident. Uninstall and reinstall then when it fires up make sure you select allow when superuser popup comes on. If you know your way around you can avoid the uninstall by simply going into superuser app and fixing permissions for wifi tether. If not then you'll need to boot into recovery and reflash supersu as you did during the original root process.
hope this helps!
When I open superSU it tells me there is no SU binary and SuperSU cannot install it.
ilogik said:
When I open superSU it tells me there is no SU binary and SuperSU cannot install it.
Click to expand...
Click to collapse
Ok thats your first problem. you should NOT be using SuperSU app, its not compatible with the SU binaries we have installed on this phone. Until further notice this app is NOT compatible and wont be supported. Do to the binaries we used during the root process you must use the "superuser" app from the market. Some people have hacked in different binaries but unless it is specified that SuperSU is compatible then always is superuser.:angel:
---------- Post added at 08:47 AM ---------- Previous post was at 08:44 AM ----------
jonesin said:
Ok thats your first problem. you should NOT be using SuperSU app, its not compatible with the SU binaries we have installed on this phone. Until further notice this app is NOT compatible and wont be supported. Do to the binaries we used during the root process you must use the "superuser" app from the market. Some people have hacked in different binaries but unless it is specified that SuperSU is compatible then always is superuser.:angel:
Click to expand...
Click to collapse
Also if you have difficulties removing it then you may have to use tibu to freeze then uninstall SuperSU. If that doesnt work your only option will be ADB, it may just uninstall fine it may not it depends. But you need to get rid of it.
ilogik said:
When I open superSU it tells me there is no SU binary and SuperSU cannot install it.
Click to expand...
Click to collapse
I was having issues like this. I had to swap between supersu and superuser. But it just never worked right. Once I flashed a new Rom it worked just fine.
sent from my rooted DNA
jonesin said:
Ok thats your first problem. you should NOT be using SuperSU app, its not compatible with the SU binaries we have installed on this phone. Until further notice this app is NOT compatible and wont be supported. Do to the binaries we used during the root process you must use the "superuser" app from the market. Some people have hacked in different binaries but unless it is specified that SuperSU is compatible then always is superuser.:angel:
---------- Post added at 08:47 AM ---------- Previous post was at 08:44 AM ----------
Also if you have difficulties removing it then you may have to use tibu to freeze then uninstall SuperSU. If that doesnt work your only option will be ADB, it may just uninstall fine it may not it depends. But you need to get rid of it.
Click to expand...
Click to collapse
Given the phone is S-On the only real way to ensure a permanent, functional root on stock would be to first remove the SuperSU binary and app. It has been confirmed that SuperSU does not work.
This can be done directly from TWRP's file manager or ADB with the unsecured kernel:
The binary can be found at: /system/xbin/su
And the app can be found at: /system/app/superuser.apk
BOTH FILES must be removed. Freezing SuperSU will not work
Next download and then flash the following zip in TWRP or CWM:
Superuser Binary+App
At this point you should have fully functional root on stock
S121Guy said:
I was having issues like this. I had to swap between supersu and superuser. But it just never worked right. Once I flashed a new Rom it worked just fine.
sent from my rooted DNA
Click to expand...
Click to collapse
Again, simply flashing Superuser over SuperSU will not work, the app and binary must be removed before flashing.
Jarocks said:
Given the phone is S-On the only real way to ensure a permanent, functional root on stock would be to first remove the SuperSU binary and app.
This can be done directly from TWRP's file manager or ADB with the unsecured kernel:
The binary can be found at: /system/xbin/su
And the app can be found at: /system/app/superuser.apk
BOTH MUST be removed to avoid any issues
Next download and flash the following zip in TWRP or CWM:
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip
At this point you should have fully functional root on stock
Click to expand...
Click to collapse
Your methods will remove the ability to provide root permissions to any apps...?
Sent from my HTC6435LVW using Tapatalk 2
---------- Post added at 11:16 AM ---------- Previous post was at 11:14 AM ----------
jonesin said:
Your methods will remove the ability to provide root permissions to any apps...?
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
You need the binaries and the app to get root perm on anything from within the rom. I don't recommend this.
Sent from my HTC6435LVW using Tapatalk 2
jonesin said:
Your methods will remove the ability to provide root permissions to any apps...?
Sent from my HTC6435LVW using Tapatalk 2
---------- Post added at 11:16 AM ---------- Previous post was at 11:14 AM ----------
You need the binaries and the app to get root perm on anything from within the rom. I don't recommend this.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
The zip contains both the superuser app and corresponding su binary.
Jarocks said:
The zip contains both the superuser app and corresponding su binary.
Click to expand...
Click to collapse
I overlooked the zip portion of your comment. I thought that you were saying to simply remove the app and the binary and reboot. However the binaries wont load from SuperSU in the first place so you should eb good to just get rid of SuperSU and install superuser. If everyone has been following the recommended rooting steps that is. But if that were the case noone would be installing SuperSU
My system folder only contains /bin and nothing else. is there another system folder I should be in?
ilogik said:
My system folder only contains /bin and nothing else. is there another system folder I should be in?
Click to expand...
Click to collapse
are you in adb or are you using a file explorer?
TWRP file explorer
I'm having the same issue-- in TWRP file manager I see only system/bin. If I try to delete the files with adb it complains about a read-only filesystem.
droidmark said:
I'm having the same issue-- in TWRP file manager I see only system/bin. If I try to delete the files with adb it complains about a read-only filesystem.
Click to expand...
Click to collapse
I know this is an old thread but if it helps others, I had the same issue with TWRP, there is an option in SuperSu to unistall and switch to a another superuser app. Put the superuser zip above on the phones memory card, then just install regular superuser from the market. Now go into SuperSu and pick the option to switch to another app, once done go into file explorer and delete the files stated above if they are there. Now reboot into recovery & flash the new superuser zip..
That's very helpful information. Somehow I solved it back in December but I don' know how!
Related
is there any way to use the new super su instead of superuser?? how do i get rid of the superuser app?? thanks!
Install SuperSU from the market, then run it a popup will come up asking to update binary say yes.
Then use a file manager to go to /system/app and delete SuperUser.apk
After that the system will use supersu for everything asking you to grant permission just like superuser.
smokin1337 said:
Install SuperSU from the market, then run it a popup will come up asking to update binary say yes.
Then use a file manager to go to /system/app and delete SuperUser.apk
After that the system will use supersu for everything asking you to grant permission just like superuser.
Click to expand...
Click to collapse
good looks bro.. worked perfect!!!!
evod3 said:
good looks bro.. worked perfect!!!!
Click to expand...
Click to collapse
Simply , you should have went to the official xda thread of super su by chain fire and should have flashed the zip. The zips removes the super user and replace it with super su
evo401 said:
is there any way to use the new super su instead of superuser?? how do i get rid of the superuser app?? thanks!
Click to expand...
Click to collapse
Here is how I replaced SuperUser with SuperSU. It is really easy to do!
Just follow the steps and you'll be up and running with SuperSU in a couple of minutes!
If you do not have "Root Explorer", any file manager with Root access will work.
Just make sure that it has Write access to the System partition. Even when in
Root Explorer, I think you have to turn this feature on. Not sure. Just check.
1) Use Root Explorer and delete SuperUser.Apk from the /system/app folder.
2) Go to the Android Market and download and install Super User.
3) Use Root Explorer again and delete SU from /system/bin.
4) Go to the Market and uninstall Super User.
5) Go to the Market and install SuperSU & Pro Key.
Zeuszoos said:
Here is how I replaced SuperUser with SuperSU. It is really easy to do!
Just follow the steps and you'll be up and running with SuperSU in a couple of minutes!
If you do not have "Root Explorer", any file manager with Root access will work.
Just make sure that it has Write access to the System partition. Even when in
Root Explorer, I think you have to turn this feature on. Not sure. Just check.
1) Use Root Explorer and delete SuperUser.Apk from the /system/app folder.
2) Go to the Android Market and download and install Super User.
3) Use Root Explorer again and delete SU from /system/bin.
4) Go to the Market and uninstall Super User.
5) Go to the Market and install SuperSU & Pro Key.
Click to expand...
Click to collapse
Wrong! Now you cannot grant root access to any app since you don't have the binary.
If you do the 3rd step you will lose root and you will have to root your phone again from recovery.
The correct step should be to just download supersu from play store and update the binary then remove the old superuser apk as smokin1337 said. Your steps are lengthy and will never work.
Or just flash the zip file.
Zeuszoos said:
Originally Posted by Zeuszoos
Here is how I replaced SuperUser with SuperSU. It is really easy to do!
Just follow the steps and you'll be up and running with SuperSU in a couple of minutes!
If you do not have "Root Explorer", any file manager with Root access will work. Just make sure that it has Write access to the System partition. Even when in Root Explorer, I think you have to turn this feature on. Not sure. Just check.
1) Use Root Explorer and delete SuperUser.Apk from the /system/app folder.
2) Go to the Android Market and download and install Super User.
3) Use Root Explorer again and delete SU from /system/bin.
4) Go to the Market and uninstall Super User.
5) Go to the Market and install SuperSU & Pro Key.
Click to expand...
Click to collapse
mnomaanw said:
Wrong! Now you cannot grant root access
to any app since you don't have the binary. If you do the 3rd step you will
lose root and you will have to root your phone again from recovery.
The correct step should be to just download supersu from play store
and update the binary then remove the old superuser apk as smokin1337 said.
Your steps are lengthy and will never work.
Click to expand...
Click to collapse
First off, I don't understand the hostility.
Secondly, I'm not the one who's wrong. You are, sir. And I find it pretty arrogant for someone to be so rude and make such a statement to someone as if iwhat they're saying is a fact, when the person they're commenting to just finished stating that they had already done it. Don't ya think?
Or did you not read the part where I said, "This is how I DID IT."???
In fact, I had just finished performing these same steps on my "Samsung Galaxy Note 2" and my "Samsung Galaxy Galaxy Tablet", not an hour before I posted them here and guuess what? I have Root access on both and no recovery was necessary!
Now you can continue making the same claim if you wish. Or you can acknowledge that "I did it successfully" outranks you saying "it won't work".
The steps I posted above work just fine. You don't have to worry about losing Root access when you boot your device, because you never reboot your phone before SuperSU is on it and you have the binary installed again. I mean, what do you think SuperSU puts on your phone? Could it be a binary, hello??? <lol>
Of course, the one thing to note is whether you have it installed in /bin or /xbin. If you don't find "su" in /bin then you now know where to look.
Zeuszoos said:
First off, I don't understand the hostility.
Secondly, I'm not the one who's wrong. You are, sir. And I find it pretty arrogant for someone to be so rude and make such a statement to someone as if iwhat they're saying is a fact, when the person they're commenting to just finished stating that they had already done it. Don't ya think?
Or did you not read the part where I said, "This is how I DID IT."???
In fact, I had just finished performing these same steps on my "Samsung Galaxy Note 2" and my "Samsung Galaxy Galaxy Tablet", not an hour before I posted them here and guuess what? I have Root access on both and no recovery was necessary!
Now you can continue making the same claim if you wish. Or you can acknowledge that "I did it successfully" outranks you saying "it won't work".
The steps I posted above work just fine. You don't have to worry about losing Root access when you boot your device, because you never reboot your phone before SuperSU is on it and you have the binary installed again. I mean, what do you think SuperSU puts on your phone? Could it be a binary, hello??? <lol>
Of course, the one thing to note is whether you have it installed in /bin or /xbin. If you don't find "su" in /bin then you now know where to look.
Click to expand...
Click to collapse
Oh ok I did not want to sound rude sorry.
I was under the impression that deleting su binary will not allow the supersu to install its su binary, but yeah if you have mounted the system rw then supersu should be able to install the binary. And your method should work without doing the 2nd and 4th step I guess. If you have more devices then maybe give it a try without doing 2nd and 4th step.
mnomaanw said:
Oh ok I did not want to sound rude sorry.
I was under the impression that deleting su binary will not allow the supersu to install its su binary, but yeah if you have mounted the system rw then supersu should be able to install the binary. And your method should work without doing the 2nd and 4th step I guess. If you have more devices then maybe give it a try without doing 2nd and 4th step.
Click to expand...
Click to collapse
No problem.
As for mounting it read/write, yes, that does need to be done. I should have included that. Thanks for noting it.
There is a utility that will mount your system partition as writable when you boot it up. It's called "mount r/w" or something like that. It's in the Google Play Market. I think it has an icon of a yellow folder with a lock, or something like that. Most people recommend against doing that and if you don't want to do it that way, as I'm sure you know, root explorer can mount it writable until you tell it not to, or reboot..
I installed the leaked ICS update, but I have apparently lost root. I tried using Voodoo, but it just says that it has been denied Superuser permissions and that there is no root backup available.
So I tried just plain rooting it using the Motofail method again, to no avail. It says that it is successful in completing the exploit.
However, no matter what app that requires root that I open, it says that the app has been denied Superuser permissions without even prompting me. Root checker says I am not rooted.
I went into the Superuser app, and I went to update the SU Binary. It says that Superuser has been granted Superuser permissions. But then it fails out at the end and says "This updater cannot update the su binary on phones that have some kind of write protection like S-ON. You can continue to use Superuser with your outdated binary, or update su with ROM manager."
I shouldn't even need to update the binary though, since it says I have the latest one installed.
What can/should I do? It's getting kind of annoying not having root on my phone.
Something along the same line happened to me too bro,I also made a thread about it but to no avail:-/ if you find something out,let me know and I'll do the same.
Sent from my DROID RAZR using xda premium
kevintstephens said:
I installed the leaked ICS update, but I have apparently lost root. I tried using Voodoo, but it just says that it has been denied Superuser permissions and that there is no root backup available.
So I tried just plain rooting it using the Motofail method again, to no avail. It says that it is successful in completing the exploit.
However, no matter what app that requires root that I open, it says that the app has been denied Superuser permissions without even prompting me. Root checker says I am not rooted.
I went into the Superuser app, and I went to update the SU Binary. It says that Superuser has been granted Superuser permissions. But then it fails out at the end and says "This updater cannot update the su binary on phones that have some kind of write protection like S-ON. You can continue to use Superuser with your outdated binary, or update su with ROM manager."
I shouldn't even need to update the binary though, since it says I have the latest one installed.
What can/should I do? It's getting kind of annoying not having root on my phone.
Click to expand...
Click to collapse
Try this on ics terminal
Code:
./system/su-backup
mount -o remount,rw /dev/block/system /system
rm /system/bin/su
ln -s /system/su-backup /system/bin/su
Sent from my XT910 using Tapatalk 2
This also happened to me, and ive had no luck rooting either. I used the terminal trick and it says theres nothing to recover i su.
mcnabb311 said:
This also happened to me, and ive had no luck rooting either. I used the terminal trick and it says theres nothing to recover i su.
Click to expand...
Click to collapse
Of course, you need a su bkp first.
Here's mine
http://db.tt/L9TLf2xg
Cheers
Sent from my XT910 using Tapatalk 2
Thanks alot, i must try this.
---------- Post added at 07:46 PM ---------- Previous post was at 07:14 PM ----------
So if you dont have root access, will the terminal move the unzipped su file? How can you apply this to your sysytem? Voodoo doesnt give you options to search for the file either. Of course, nothing has superuser permissions without root either. I guess Im too much of a n00b.
Same here
Na dude its not noobish,im tryna figure out everything myself,I've been flashing since the hd2,so i know a couple things but this is just mind boggeling lol
I'm at a loss. I've downloaded your su-backup file, but I don't know how to move it to the /system folder, as it is write protected, and I don't have root to bypass that. And whenever I tried typing things in using the terminal, it just denied everything.
kevintstephens said:
I'm at a loss. I've downloaded your su-backup file, but I don't know how to move it to the /system folder, as it is write protected, and I don't have root to bypass that. And whenever I tried typing things in using the terminal, it just denied everything.
Click to expand...
Click to collapse
You can't move this file to system folder because you have a non-rooted device. Be patient, we are working hard on that....
I should have replied to the SuperSU thread but since I have less than 10 posts...
I was doing a fresh flash/install. The first thing to do of course is to root the phone.
Installed SuperSU 0.94, open it up, says that I need to update the binary, clicked OK, Installation Failed, tried that several times via 3G/Wifi.
Tested under Better Terminal, typed su: not found.
Then I installed Superuser 3.1.3, run SuperSU again and the binary update worked.
Tested under Better Terminal, typed su: # it worked.
Uninstalled Superuser and tested under Better Terminal
SU gone again.
The binary update failure happened before when version<0.7.3.
So why is this? Why do I need to install Superuser to get SuperSU to work?
It depends on what su binary is installed when you root your phone or what app the author of the ROM prefers. You can download the supersu zip package and install it after you install a ROM but even then you'll have to update binary via launching the app itself.
Sent from my Nexus 7
Because every app that uses Superuser permissions needs a a management app to get access to su.
Sent from my DROID RAZR using Tapatalk 2
Leviathan26 said:
Because every app that uses Superuser permissions needs a a management app to get access to su.
Click to expand...
Click to collapse
Oh, by Supuruser I'm talking about Superuser - the old app, not the superuser permission.
evonc said:
It depends on what su binary is installed when you root your phone
Click to expand...
Click to collapse
Yep, you're right, I was just stupid not paying attention to the bat root script. I removed the old Superuser.apk from the scirpt but not the binary.
When I replaced the su with SuperSU binary, no errors anymore. Thanks.
Help. I dont know much about rooting. I just rooted my phone and superuser keeps coming up with an annoying notification saying that my su binary is outdated. Ive tried multiple times to do this and this is what it says:
Downloading manifest... okay!
Parsing manifest... okay!
Latest version = 3.1.1
Checking installed version = 2.3.1-ef
Then I touch update then it says:
Fixing database... okay!
Unpacking subtools...okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Gaining root access... okay!
Remounting /system as rw...okay!
copying su to /system fail!
I touch Try again and it says the same thing. Please help.
NOTE:Admin, please remove.
Download a busybox installer and put in bin. If you still have issue put it in xbin also. I think that's how I got that to work. Its been awhile.
Sent from my SGH-T959 using xda premium
Busybox doesn't work
samsgun357 said:
Download a busybox installer and put in bin. If you still have issue put it in xbin also. I think that's how I got that to work. Its been awhile.
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
"It looks like busybox is installed, but it does not appear to be the version that you selected to have installed, you may want to try the installation again but this time try using a different installation location" I've tried and every time it comes with this message. I actually got this app right after I rooted the phone. BTW the current installation location is system/bin. I haven't tried xbin yet. Ill keep you posted if it works or not.
Even xbin wont work
samsgun357 said:
Download a busybox installer and put in bin. If you still have issue put it in xbin also. I think that's how I got that to work. Its been awhile.
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
LOL I thought xbin was an app. I figured it out though. Neither of them worked, and they bothcome up with the same message.
Try this, it's from the axura thread, I had the same issue and this fixed it for me.
http://forum.xda-developers.com/showpost.php?p=29111715&postcount=4
God damnit
kxlling said:
Try this, it's from the axura thread, I had the same issue and this fixed it for me.
http://forum.xda-developers.com/showpost.php?p=29111715&postcount=4
Click to expand...
Click to collapse
I think my phone hates me. I think its against the prophesy for me to update Busybox and my Su binary. God damn. That didnt work either...
Well then how about trying this Superuser Update Fixer from the market. It is older but last time I had a binary problem, this fixed it.
su binary
To update su binary, download SuperSu from Play Store.
This is what I did because superuser having issues with Therese new roms . I had to end up installing busy box 1.19. Then superuser got on track
Sent from my SGH-T959 using xda premium
Crona said:
To update su binary, download SuperSu from Play Store.
Click to expand...
Click to collapse
ut when you install another Superuser uninstalling SuperSu..problem reappears
---------- Post added at 08:33 PM ---------- Previous post was at 08:24 PM ----------
naturallight said:
This is what I did because superuser having issues with Therese new roms . I had to end up installing busy box 1.19. Then superuser got on track
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
which Busy Box are you talking about?? I mean, of which developer??
Perseverance pays dividends.....
........but so does banging your head against a wall,,,I think.
Seriously though,,,
I just had the same problem, even after 1 year (start of this thread) the updater still hasn't been fixed.
I fixed it by REPEATEDLY UPDATING until it took..........
About 1/2 Hr or so.
Good luck to the next person that comes across this thread......
Wow
Seriously... keep on trying till it loads... most of the information here is helpful... installed busy box and kept trying till it loaded... thank you!!!!
How to update superuser binary
I ve found out by accident on how to update my su binary after endless on searching on the internet…
i use xperia x8 by the way
Use flashtool coz I use it
Turn on ur laptop, download and run flastool on pc.
Download and install root explorer on phone coz I use that
[root explorer is not free anymore,search the free one outside app store/android market]
Go to root explorer,system and click R/W to change to R/O
Download the latest superuser in app store,move and install in system app using root explorer
Find the old superuser in system app and delete
Turn on usb debugging and check on unknown source on ur phone
Use usb cabel to connect ur phone to the pc
Do not click connect phone,just let it be
Open flashtool up
Wait until flashtool write Root Access Allowed
Go to superuser on ur phone while it is still connecting to the pc
Turn on wifi or mobile network,that works better
Click on outdated su binary to update
Click on update
And just wait…done?
Ur welcome^^
*don’t try to be cool by reclick the update button
I rooted my strange tablet using Kingo and apparently it was succesful:
http://i1312.photobucket.com/albums/t539/talos910/Screenshot_2015-09-11-17-08-20_zpsurdgzj8p.png
But I have been trying for days to erase a file in /system and I have not been able to do it, I think I have read every relevant thread about this problem but no luck, I tried using ES and changed /system to r/w in the root options but when trying to delete the file all I get is operation failed, the same happens with all the other root explorers and tools. I even tried the solution on this thread: http://forum.xda-developers.com/ascend-p7/help/edit-replace-write-files-set-immutable-t2884172
but still can't delete it.
Also the app root toolkit for android gives me this weird error too:
http://i1312.photobucket.com/albums/t539/talos910/Screenshot_2015-09-11-17-08-06_zps4nrxqiev.png
http://i1312.photobucket.com/albums/t539/talos910/Screenshot_2015-09-11-17-08-02_zpsa1ycwdwl.png
Do you have an app like root explorer that specifically asks for root permissions? It doesn't matter if you have root if the explorer can't use it
Sent from my Nexus 5 using Tapatalk
Yes all the file manager apps I used always ask for root permission, that is the problem they have root permission but still can't delete the file, which is weird because I can use apps that definitely need root like scr screen recorder and greenify just fine.
Try installing root explorer and then attempt to delete the file, then it should instantly open a window asking for root. The of course grant the permission. That should always work, but if it doesn't just restart the tablet, if it still doesn't work it must mean you are deleting a file that is in use by the system. Otherwise i have no idea whats wrong
Sent from my Nexus 5 using Tapatalk
Talos91 said:
Yes all the file manager apps I used always ask for root permission, that is the problem they have root permission but still can't delete the file, which is weird because I can use apps that definitely need root like scr screen recorder and greenify just fine.
Click to expand...
Click to collapse
What recovery did you install...twrp, cwm, philz?
Sent from my Nexus 6 using Tapatalk
JMink said:
What recovery did you install...twrp, cwm, philz?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Rooted my device using kingo root, I didn't intall other recovery.
Bad idea to try and remove system files without a custom recovery and a nandroid backup made and stored in a safe spot. What are you trying to remove?
I am trying to delete /system/sbin/su because I read in another thread this was the solution to fixing the issue of the app supersu not updating binaries when rooting your device using Kingo.
Talos91 said:
I am trying to delete /system/sbin/su because I read in another thread this was the solution to fixing the issue of the app supersu not updating binaries when rooting your device using Kingo.
Click to expand...
Click to collapse
That is the binary. If you remove it, you wouldn't be rooted. Can you link the thread you are looking at? There's an app made specifically for replacing that su binary with SuperSU and it's binary called Super-SUme, though I believe it is a paid app.
I know it is the binary but according to this guy:
http://forum.xda-developers.com/apps/supersu/support-update-failures-t2907365/page23
(post 223)
""It appears kango wrote to /system/sbin/su whereas supersu wrote /system/xbin/su and subsequently supersu would keep wanting to update 'su' then fail.
The long and the short of it is once I manually removed /system/sbin/su supersu stopped telling me 'su' was outdated. I don't know android but I do know linux.
$PATH on my tablet has /system/sbin/ prior to /system/xbin/ so it would appear supersu is issuing 'su -V' as opposed to '/system/xbin/su -V' when it checks the version. The kingo 'su' was older than the supersu 'su'.
Dunno what the solution is 'cos the older 'su' is going to get called first & I figure there's nothing but trouble to be gained from changing $PATH globally. Nevertheless it might be enough to check $PATH for unwanted 'su' and flag them, possibly offer to remove them? In my case I renamed it "/system/sbin/su.ORIGINAL" so that it's still runnable in an emergency"""
If you rename it, it won't be able to run, and won't require removal.
That's the thing I can't rename the file either for some reason. Using es and other root explorers doesn’t work.
Talos91 said:
That's the thing I can't rename the file either for some reason. Using es and other root explorers doesn’t work.
Click to expand...
Click to collapse
Seems like the SU binary that Kingroot included is pretty finicky and only works for some things. I've rooted 100s of devices and have never had issues like that. Have seen complaints about other various oddities with Kingroot too. It's nice that it's easy and works on a variety of devices, but if you have only limited control then that kind of defeats part of the purpose of rooting it...
Tried using SuperSUme but the app says I am not rooted with Kingo? wtf? Do you guys know of any other reason why i can't erase the system file sbin/su?
Talos91 said:
Tried using SuperSUme but the app says I am not rooted with Kingo? wtf? Do you guys know of any other reason why i can't erase the system file sbin/su?
Click to expand...
Click to collapse
With Root Explorer, does it let you set the system to R/W? There's a little button at the top of the app that will say R/O or R/W for Read Only or Read Write. If you don't have R/W to the system, then you are unable to make changes to it.
I just renamed file su and then it became able to be deleted.
Talos91 said:
Tried using SuperSUme but the app says I am not rooted with Kingo? wtf? Do you guys know of any other reason why i can't erase the system file sbin/su?
Click to expand...
Click to collapse
Connect your android tablet device to your windows computer. Then enable usb debugging on your android tablet. Then open the windows program called cmd. Then do these commands.
Code:
adb root
Code:
adb remount
Code:
adb shell rm /system/sbin/su