Develop Bugs

Superuser app does not remember "Allow" option

Anyone having this problem? I reboot many times and the app still doesnt remember all the alloweds.
Im perm.rooted.

androidtoy09 said:
Anyone having this problem? I reboot many times and the app still doesnt remember all the alloweds.
Im perm.rooted.
Click to expand...
Click to collapse
Which version of Superuser are you running? I have the one by ChainsDD (available in the Market) and I do not have that problem.

I had the same issue. Installing BaconBits will fix that for you.

This is happening for me too, but only on Titanium. I have installed baconbits 0.3, i've reinstalled busybox via the "Problems?" button in Ti, and I've reinstalled chainsDD Superuser.apk from the market. I can't figure out what is going on and I have a thread going on legendroid forums, but so far no luck.

I found a fix guys. Updated SU Binaries through Rom Manager and things are fine now.
I think the SU app I pushed into my phone while perm. rooting was older than what is currently on RM.

I just had this issue about 10 minutes ago where the "Allow or deny" prompt would come up and it wouldn't remember it. I fixed it by loading Superuser, going to the Settings tab, scrolling down and selecting Su binary to check for updates. There was one, applied it, and it's now remembering.

I fixed my issue by uninstalling su. It reverted to a very old version, and it's remembering my settings, even in Ti.

Superuser auto-update? WTF? WHY? Now my Rom is F'd

I'm running CM7 #211 and yesterday my SUperuser app decided to RANDOMLY auto update itself. I didnt even know you could download the superuser app from the Market. Now all my apps are force closing. I uninstalled the update but my ROM is still F'd force closing on everything. I've tried clearing both caches and fixing permissions and it's still messed up. Any ideas? HOW DO I GET SUPERUSER TO NOT AUTO UPDATE?

I wiped my phone and restored to a backup last week and everything seems fine for the moment.... I just need to figure out how to force the market not to auto update any of my apps.

Since froyo rolled out, you have an option in the market to auto update. The part that sucks is this is within each app so if you have thirty apps, then you have to go into all thirty apps in the market and de-select the auto update option.
And yes, SU has been available for some months in the market as well as in XDA.

cowman4000 said:
I'm running CM7 #211 and yesterday my SUperuser app decided to RANDOMLY auto update itself. I didnt even know you could download the superuser app from the Market. Now all my apps are force closing. I uninstalled the update but my ROM is still F'd force closing on everything. I've tried clearing both caches and fixing permissions and it's still messed up. Any ideas? HOW DO I GET SUPERUSER TO NOT AUTO UPDATE?
Click to expand...
Click to collapse
im running CM7 nightly 211 with the newest SU and it works just fine. if you go to the SU app and update the binary it will fix all the FC.
The latest night will have the updated binary and SU in the zip.

Update the binary? Is that done from within the superuser app?

cowman4000 said:
Update the binary? Is that done from within the superuser app?
Click to expand...
Click to collapse
yep go to the app. click menu button then preferences.
at the bottom you will see "tap to check for updates"
that way you can enjoy the new app and have the new binary's. without breaking CM7

Thanks I'll try that.

In TB you can disassociate apps from the market which is very handy so those you don't ever want to update such as themed or custom.

SlimSnoopOS said:
Since froyo rolled out, you have an option in the market to auto update. The part that sucks is this is within each app so if you have thirty apps, then you have to go into all thirty apps in the market and de-select the auto update option.
And yes, SU has been available for some months in the market as well as in XDA.
Click to expand...
Click to collapse
My superuser app was also auto-updated contrary to my will, i feel raped
First i need to say that everything in the update went fine, updated superuser app and binary are up and working OK.
But regarding what you said, i have eclair 2.1 and so i have the old Market 2.3.6. I also have the option "Allow automatic updating" present in all of my apps, so i can use it or not, it is up to me.
BUT the problem is that in Superuser app this option is not available. See pics:
ttp://i297.photobucket.com/albums/mm203/lanosalf/2011-10-7-14-46-19.jpg
ttp://i297.photobucket.com/albums/mm203/lanosalf/2011-10-7-14-46-45.jpg
PS:
Add the "h" to "ttp" to get "http" and complete image link.
The XDA forum board don't let me put images, it says"to prevent spam new users cant post links..." or something That's okay but, in my opinion, links inserted in between [image] should be permitted.
EDIT: ALL OK NOW. When version 3.04 appear in Market, it also appears the option "Allow automatic updating", so know i can uncheck it if i want, and i did...

BenHolliday said:
In TB you can disassociate apps from the market which is very handy so those you don't ever want to update such as themed or custom.
Click to expand...
Click to collapse
On my phone superuser doesn't show up in titanium backup. While other system apps show up in red. If anyone knows a way to make superuser show up in titanium please post it.

Guys, stop freaking out about the SU update. Just do like Synisterwolf said. You'll be fine.

Getting constant f/c on mine, even get them after clicking to update the binary.
Looking over the reviews for SU in the Market many are running into this problem with the latest update.

I had no issues with the update in CM7 but updating past SU app 3.0.2 and binary v2.3.2 running McSense 2.4 was a whole 'nother story. Basically locked down every root permissions app on my phone. Was able to nandroid back to 3.0.2 and disable updating in the market for that ROM. I'll just ignore the nag until the next update.
daj

BTW how are more people not talkign about this? Just about every review across many different roms and phones says the same thing:
http://www.appbrain.com/app/superuser/com.noshufou.android.su

I have no idea if this will help anyone with the SU program or not, or what effects it might have on certain roms.
So after hearing about the force closing on SU I grabbed my phone which I had just updated the binarys on the other day, and today installed a SU update. FC's all over the place as been described. No way to uninstall it from the market, (didn't try the main applications app) so I went to my astro program and from there I was able to uninstall it....well not the entire thing I guess but just the latest updates.
I can now enter back into it without it FC on me. I went to market and made sure auto update was now off and didn't update it when prompted as you open the app.
Seems to work now but I honestly never use it per se unless it prompts me to grant SU permissions when doing something else, so ymmv if doing as I did.
Just thought I'd put it out there in case it helped some folks.

Updated the app to 3.0.5. As long as I don't update the binary past 2.3.2, I'm good running McSense 2.4.
daj

wildstang83 said:
Guys, stop freaking out about the SU update. Just do like Synisterwolf said. You'll be fine.
Click to expand...
Click to collapse
It's very likely that you won't. For me, 3.0.4 worked for the most part, but it never worked with adbWireless. I updated to 3.0.5 and started getting very frequent force closes. Superuser 3 is not ready for prime time. I'm back to superuser 2.3.6.3 su binary 2.3.2 and will stay there for a while.

Ok people this will fix the FC on superuser 3.0.5 with binary 3.0!!!!!
1. Go setting/application/manage applications and clear data on superuser
2. Go to market and install update
3. open superuser and preferences change automatic response to "allow"
The list will not show apps but log will and the first time the app accesses little lag but no FC.
Not sure if you already installed 3.0.5 if will fix... Can try clearing data and then change automatic response.

Tanks RL.
I read something like that lastt night and changing it to "allow" fixed the f/c for me.
But this whole thing is so stupid. So many times someone takes something that is perfectly fine and updates it till it is broken. If it's not broke don't fix it. Especially something as important as this.

rlacrossjr said:
Ok people this will fix the FC on superuser 3.0.5 with binary 3.0!!!!!
1. Go setting/application/manage applications and clear data on superuser
2. Go to market and install update
3. open superuser and preferences change automatic response to "allow"
The list will not show apps but log will and the first time the app accesses little lag but no FC.
Not sure if you already installed 3.0.5 if will fix... Can try clearing data and then change automatic response.
Click to expand...
Click to collapse
Tried again using this except I uninstalled all updates first. Everything looked OK at first but I started getting FCs when opening TiBU. Cleared data for both SU and TiBU and tried again and it worked fine but as I started opening other root apps, the FCs came back. YMMV
daj

[Q] rooted while un-rooted

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

[Q] Lost SU Binary

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.

Disabling Knox on Tab S 8.4 4G

I'm brand new to this website, and have only signed up because I cannot find a solution for this problem. I have always used the forum to get answers, but never though to join! My Galaxy Tab S 8.4 4G T705Y was put through the CF-Auto-Root method, and no a glitch at all. Very smooth. By the way I checked the ChainFire website to make sure I was using the latest. When my device started up I noticed, as I have done before with my Nexus phones, that SuperSU has been added. Good Sign!
But when I open SuperSU I was prompted to update the Binary. Then I pressed 'continue', used the 'normal' method, and waited. It then asked me if I would like to Disable Knox. Yes I would! FAILED TO DISABLE KNOX. Shut down SuperSU. Unhappy Face. As you can see at this point, I am not very up to speed with my rooting knowledge.
So then I decided to select the 'never' option to updating SuperSU, and still it failed to update the binary, I'd say due to Knox stopping it from gaining access.
So my pickle is this: I can't update SuperSU because Knox will not allow me to use SuperSU. I cannot simply hit yes to disabling Knox in SuperSU, as that didn't work for me. I also tried finding something called Knox on my tablet and it seems to be very elusive. I tried updating SuperSU on Play Store also, but to no avail!
I am also unable to use any third party app to do so as I need to grant them access in SuperSU before they can begin! And around I go...
There is a guide here http://forum.xda-developers.com/showthread.php?t=2540761 but it's not for my device so I'm a bit hesitant to start trying random things, as my device is working great atm!
Any info or help would be greatly appreciated!

Look in the android development section for my updated builds of cf_autoroot and flash that.
If you still get issues flash supersu v2.49 with twrp.

ashyx said:
Look in the android development section for my updated builds of cf_autoroot and flash that.
If you still get issues flash supersu v2.49 with twrp.
Click to expand...
Click to collapse
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.

clint.fish said:
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
Click to expand...
Click to collapse
UPDATE: So now I have managed to try and install the version of superSU that you have released in the dev thread, using TWRP. seemed to work fine, but i still got the same binary missing error.

clint.fish said:
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
Click to expand...
Click to collapse
Whoah way way way over complicating things. You just install twrp with odin and that's it.
Then you flash this with twrp http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip

ashyx said:
Whoah way way way over complicating things. You just install twrp with odin and that's it.
Then you flash this with twrp
Click to expand...
Click to collapse
So this is what I do.
Power off device.
Restart in Download Mode.
Use Odin to install the cf-autoroot-twrp-t705.tar from the development section.
When device restarts I put supersu version 2.52 (beta) on the devices memory, then turn off device.
Restart in TWRP Recovery mode, hit install, choose the zip file, install, reboot device.
When device reboots, open superuser and get this message: "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device".
I swear i'm not blonde. :good:

Something is blocking supersu from installing. Which firmware build is this device running and is reactivation lock disabled?

ashyx said:
Something is blocking supersu from installing. Which firmware build is this device running and is reactivation lock disabled?
Click to expand...
Click to collapse
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.

clint.fish said:
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
Click to expand...
Click to collapse
UPDATE: So I went into my Samsung account and Performed a factory reset. Only had the device a few days so no biggy. Then as it reset i chose not to put in and Samsung details and skip all the options i could, assuming this would help. Flashed cf autoroot with odin, then updated supersu through twrp... still nothing

clint.fish said:
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
Click to expand...
Click to collapse
UPDATE: SUCCESS! I used the latest version of Kingroot available on this forum. From looking around, you are a very patient person ashyx. Thanks for all your help!

clint.fish said:
UPDATE: SUCCESS! I used the latest version of Kingroot available on this forum. From looking around, you are a very patient person ashyx. Thanks for all your help!
Click to expand...
Click to collapse
This doesn't make sense. Something is amiss if you can't root with cf_autoroot or twrp. You are the only one as far as I'm aware that has experienced this.
Reactivation lock is under 'Find my phone' in security settings.

clint.fish said:
I'm brand new to this website, and have only signed up because I cannot find a solution for this problem. I have always used the forum to get answers, but never though to join! My Galaxy Tab S 8.4 4G T705Y was put through the CF-Auto-Root method, and no a glitch at all. Very smooth. By the way I checked the ChainFire website to make sure I was using the latest. When my device started up I noticed, as I have done before with my Nexus phones, that SuperSU has been added. Good Sign!
But when I open SuperSU I was prompted to update the Binary. Then I pressed 'continue', used the 'normal' method, and waited. It then asked me if I would like to Disable Knox. Yes I would! FAILED TO DISABLE KNOX. Shut down SuperSU. Unhappy Face. As you can see at this point, I am not very up to speed with my rooting knowledge.
So then I decided to select the 'never' option to updating SuperSU, and still it failed to update the binary, I'd say due to Knox stopping it from gaining access.
So my pickle is this: I can't update SuperSU because Knox will not allow me to use SuperSU. I cannot simply hit yes to disabling Knox in SuperSU, as that didn't work for me. I also tried finding something called Knox on my tablet and it seems to be very elusive. I tried updating SuperSU on Play Store also, but to no avail!
I am also unable to use any third party app to do so as I need to grant them access in SuperSU before they can begin! And around I go...
There is a guide here http://forum.xda-developers.com/showthread.php?t=2540761 but it's not for my device so I'm a bit hesitant to start trying random things, as my device is working great atm!
Any info or help would be greatly appreciated!
Click to expand...
Click to collapse
Chimed in with some feedback but noticed your problem solved after I replied. Unable to delete. Glad to see you're good to go though.