Hi guys, today my phone started to become unresponsive and crash. I have to hard-reset the phone with the emergency power-off switch under the flap. When I power up again Superuser alerts me that "the Superuser binary (su) must be updated", and that I can "cancel" or "Recovery Install" ... neither option fixes anything. I have never got this option before, even after updating to the latest 4.4.4 firmware.
I have the latest SuperSU installed ... is there a way I can get rid of Superuser and rely solely upon SuperSU only? I tried removing Superuser by using the automated removal process that SuperSU offered, but it just hangs and does nothing. I assume that Superuser and SuperSU perform the same role?
Perhaps I can safely disable Superuser knowing that SuperSU will do the job?
I have a feeling that there is a conflict with Superuser and SuperSU and is why my phone keeps crashing!
Any ideas?
Cheers.
Reflash a stock ftf and start from scratch in these situations, it's quicker than a Q&A trying to find out how and why you've ended up with both SU and Superuser installed in the first place.
Ok great, thanks for the info. Excuse my ignorance, but will this mean i lose all data? Ie do i need to do the whole root process again? Cheers
if you have root access just delete the apk from systrm/app
yes you will loose data if you flash stock
Related
May seem wierd but i seem to have this. I rooted my phone with a package THE-E (thnx for the root package) posted. I thought "get supersu" so i did but then i pressed clear binary as i saw no point in it but then su dissapeared but it was still in my system. So i used the unroot package (again THE-E thnx) but didnt delete supersu because i forgot. I pressed root explorer (as i wanted to delete it) but supersu was givin me that notification. I thought id check if everything from the root package got deleted and it did but supersu acts like su even though the packages required are gone. I was thinking of going back to root just in case my phone went haywire and it succeded but still...rooted while unrooted...anyone know what might of went wrong? Im using stock btw. This is not an everyday thing even for...idk...google them selves.
Sent From The Phone Of Gamers
why did you have to clear binary? that is needed for Root access.
are your applications that needs root still working fine?
you can download busybox installer, and it will update your SU app and binaries just in case. if it wont work, you have to root your phone again (to install the binaries again).
Supersu (created by someone else) has its own binary. I dowloaded that binary but thought super su is nothing but a space taker so i deleted the binary. I did get a message before saying you can update the binary again via superuser (normal version) but before i know it the binary is gone, superuser is gone and all packages required for root are gone but supersu still works even though superuser is gone. Superuser gives supersu root permisions but now every root file is gone im rooted while unrooted. Is this ok? Could i brick it without an app or anything (reboot maybe?)
Sent From The Phone Of Gamers
Seems like there are fragments of SU that you can't see in a folder. I had the same problem, just experimenting what happed if i deleted files that i don't need. Since that time the system runs stable (Bionic Cow) and also SU-rights are given to me without having these SU-files in the folder...
so im not the only one...
Sent From The Phone Of Gamers
UPDATE: Problem Already Solved
Hi there! So I installed Android 4.3, along with the SuperSU1.43 update. Now when version 1.45 came out, it required that I installed the updated binary, I lost my root. I've tried reinstalling but I still don't have root. At first it appears as if I have root, but the moment an app asks for root it says that root was denied. Now I did a cleanup of SuperSU and am going to try to reinstall it with the Auto-Root by Chainfire. Still, if this doesn't work, what do I do?
P.S: I'm new to xda so if this is the wrong forum, can a mod please move it to the correct one? Thanks.
finestrocker said:
Hi there! So I installed Android 4.3, along with the SuperSU1.43 update. Now when version 1.45 came out, it required that I installed the updated binary, I lost my root. I've tried reinstalling but I still don't have root. At first it appears as if I have root, but the moment an app asks for root it says that root was denied. Now I did a cleanup of SuperSU and am going to try to reinstall it with the Auto-Root by Chainfire. Still, if this doesn't work, what do I do?
P.S: I'm new to xda so if this is the wrong forum, can a mod please move it to the correct one? Thanks.
Click to expand...
Click to collapse
Assuming you put this thread in the Q/A forum, and a mod didn't move it here, you chose wisely.
The first thing I would suggest doing is looking at the su binary. Download a terminal program if you don't have one and type:
ls -la /system/xbin/su
The first part should look like this:
rwsr-sr-x
If the file isn't there, then you definitely need to reinstall it as 'root' is gone. If the permissions don't look identical to what is above (specifically the s's, then you lost your suid root permissions on the file and will need to reinstall it. If the file is there, and has the above permissions, it should be good. Try typing 'su' in a terminal and see if your prompt changes from $ to #. It should pop up asking if you want to allow it to have root. If that doesn't happen, there is a possibility that the 'upgrade' to su somehow corrupted it. You can't replace su without having su, so you will likely need to flash the zip file again in custom recovery.
In all honesty, there isn't much you can do to troubleshoot outside of just reflashing SuperSU.zip. Regardless of how it's broken, if it is, it will need to be replaced that way.
On a related note, I too received that upgrade message and ran into issues with su afterwards. A reboot fixed it. Have you tried that yet?
phonic said:
Assuming you put this thread in the Q/A forum, and a mod didn't move it here, you chose wisely.
The first thing I would suggest doing is looking at the su binary. Download a terminal program if you don't have one and type:
ls -la /system/xbin/su
The first part should look like this:
rwsr-sr-x
If the file isn't there, then you definitely need to reinstall it as 'root' is gone. If the permissions don't look identical to what is above (specifically the s's, then you lost your suid root permissions on the file and will need to reinstall it. If the file is there, and has the above permissions, it should be good. Try typing 'su' in a terminal and see if your prompt changes from $ to #. It should pop up asking if you want to allow it to have root. If that doesn't happen, there is a possibility that the 'upgrade' to su somehow corrupted it. You can't replace su without having su, so you will likely need to flash the zip file again in custom recovery.
In all honesty, there isn't much you can do to troubleshoot outside of just reflashing SuperSU.zip. Regardless of how it's broken, if it is, it will need to be replaced that way.
On a related note, I too received that upgrade message and ran into issues with su afterwards. A reboot fixed it. Have you tried that yet?
Click to expand...
Click to collapse
I ran the command as you said and got the identical permissions. Still that one app I'm trying to use says that the system denied root even though I granted it. Thanks for the help. I don't get the binary error anymore.
PS: Why don't I see the new SuperSU icon on my tablet, but I do in Google Play?
finestrocker said:
Hi there! So I installed Android 4.3, along with the SuperSU1.43 update. Now when version 1.45 came out, it required that I installed the updated binary, I lost my root. I've tried reinstalling but I still don't have root. At first it appears as if I have root, but the moment an app asks for root it says that root was denied. Now I did a cleanup of SuperSU and am going to try to reinstall it with the Auto-Root by Chainfire. Still, if this doesn't work, what do I do?
P.S: I'm new to xda so if this is the wrong forum, can a mod please move it to the correct one? Thanks.
Click to expand...
Click to collapse
I experienced the same issue yesterday.
To resolve the issue I went to the app management screen , uninstalled updates, force stop and then disabled and re-enabled super user
I then proceeded back to flash the su zip via TWRP recovery
Upon rebooting device, there was an update available in the play store, I went ahead and installed this update
After installation, I opened the super user app and it prompted me to update the binary. I did that and root has been fine for me since then.
Hello to all,
I recently rooted my sgs3 sph-L710 v4.3 and am experiencing some problems. Whenever I try to open superusers it automatically closes, and I receive a notification saying, "security notice an attempt to access a secure area on your phone without authorization has been blocked." After doing some research online I discovered that the 4.3 version is protected by KNOX. Online sources state that in order to defeat the KNOX system you must update supersu, but I am not sure how to do that. Whenever I download supersu from the Google play store there is no option to update it. I would really appreciate any help thanks.
kingart93 said:
Hello to all,
I recently rooted my sgs3 sph-L710 v4.3 and am experiencing some problems. Whenever I try to open superusers it automatically closes, and I receive a notification saying, "security notice an attempt to access a secure area on your phone without authorization has been blocked." After doing some research online I discovered that the 4.3 version is protected by KNOX. Online sources state that in order to defeat the KNOX system you must update supersu, but I am not sure how to do that. Whenever I download supersu from the Google play store there is no option to update it. I would really appreciate any help thanks.
Click to expand...
Click to collapse
Have you checked to make sure you haven't lost root? When you install an app from Google play, you get the latest version.
sent from my GS3
Also, have you actually opened up the SuperSU app? You need to open it up (not just download it) so that it will prompt you about disabling Knox, and it might also prompt you to update the binaries. And which custom recovery are you using? If need be, you can flash the SuperSU zip from recovery, and if you are using Philz Touch (HIGHLY recommended) there is an option to have it check for root before booting back into system.
I did it!!!
Mr. Struck said:
Also, have you actually opened up the SuperSU app? You need to open it up (not just download it) so that it will prompt you about disabling Knox, and it might also prompt you to update the binaries. And which custom recovery are you using? If need be, you can flash the SuperSU zip from recovery, and if you are using Philz Touch (HIGHLY recommended) there is an option to have it check for root before booting back into system.
Click to expand...
Click to collapse
Yes I finally got it to work I just re rooted the device and superuser was gone. However, i downloaded supersu and it prompted me to update, i did and I was able to bypass knox! I think it was a problem with the method I used to get my phone rooted the first time. The video tutorial I watched the first time told me to uncheck the 2 boxes that come prechecked on odin i believe one of them was auto reboot i cant recall the other one. Then I took out the battery of the phone and selected the root file through mod recovery mode and that was it. The second time around I left the boxes checked and my phone auto restarted. I then downloaded supersu updated,rebooted, and Visalia!!!
Thanks guys I appreciate the help.
I need some help with Superuser. Currently running Mustaavalkosta 's CM11 BR4 and Superuser version 3.1.3 (46).
After clean installing the ROM, Superuser works and allows me to grant root permission to apps. Temp unroot works but updating the binary immediately results in 'downloading manifest... fail!' and if I click the 'try again' button, Superuser crashes. No big deal cause everything that I need it to do, works. A couple of days later however it just stops working and no longer grants permissions... I still have root. Temp unroot stops working and crashes Superuser when I try to use it. The file /system/bin/su still exists.
Things I tried:
- clear Superuser data
- uninstall Superuser and reinstall from Play Store
- install SuperSU
None of the above works.
Please somebody help me out here, I don't want to keep restoring my Nandroid cause it still is alot of work. Thanks
After doing some more research I think I fixed the problem by flashing the latest SuperSU.zip instead of installing it from the Play Story where it wouldn't let me update the binaries. I can now grant root access again to apps.
Still no idea what caused the Superuser issues but I 'm glad with this 'workaround'.
[Q] Root "disabled" itself!? (Rooted phone that is no longer allowing root access)
Anyone here with this phone (or any) - that is rooted - have it just seemingly act as if it is no longer rooted? or unjustly denying root access for no apparent reason....
Have been rooted since purchase and have never seen or had any issue with this..have flashed custom recovery and rom's hundreds of times...no problems...currently using Task's latest KK 4.4.4 rom and had no issues from beginning...
It comes with SuperUser...i do usually install SuperSU instead but hadn't tried yet...it was fine and apps that needed root appeared ok..even SuperUser has three or four listed apps in the "allow" section...but all of a sudden I can't seem to give root access to anything else now..
First noticed the other day when trying to sideload an apk..couldn't...tried to do it manually by just copying it to system/apps folder and that's when the first message came up saying "it appears your device may not be rooted"...quite odd I thought.. i then tried to install SuperSU and it when SuperUser popped up to give it allowable root access it would only timeout and say denied...i then tried a bunch of other apps that require root and they would all just get denied by SuperUser...
Anyone seen this before or know what causes this and/or how to fix?
THanks for any help or suggestions
ps.. i'm no noob and have been doing this a long time and have rooted/modded dozens of phones, hundreds of times...but this issue is a new one for me.. IF i have to completely wipe and even go back to stock image and then start over to re-root and re-mod... I will and can do so easily..but that would be last resort if necessary...thanks!
In SuperSU, try the clean-up for reinstallation option.
DocHoliday77 said:
In SuperSU, try the clean-up for reinstallation option.
Click to expand...
Click to collapse
when launching SuperSU it needs root access to begin with and SuperUser wont allow..this clean up for reinstall is still doable?
Get the recovery flashable SuperSU then. It'll get rid of the other one in the process. You can get it from my sig, but it'll need to be updated after.