If you have been experiencing the issue where apps are denied SU permission, it appears to be related to the SU beta.
I found that by flashing the older SU that ACS put out awhile back, everything works once again. This will probably only work if you are using an uprooted kernel.
I don't have the link with me but I try to find it later. You can also check out the ACS site.
Hope this helps....
Sent from my SPH-D710 using xda premium
Related
i am currently running randomRom with the genocide 2.0 kernal and today i was going to change some setting in voltage control and found that i did not have an updated su permission. then upon trying to update it, i got an error saying it could not get su. can i just re run the oneclickroot to get it back and have it up-to-date?
Also can someone explain the different settings in voltage control? Not too sure what they mean. never used a cpu app so not too sure what everything means. thanks for the help.
Try reflashing the rom
U dont need to wipe
Sent from my SPH-D710 using xda premium
mine did the same just right now. i am on SRF with Twilight and it says that the su is not up to date, i tried to update and it says that it can't because the su's install path is /sbin/su and its not compatible to update it. i have no idea what to do.
any help?
Wow...not 5 minutes ago the samething happened with me. I just blew it off. :-!
Sent from my SPH-D700 using XDA App
Uninstall su & reinstall
Same thing happened to me and I uninstalled Superuser and reinstalled it from the Market. That seemed to work.
Was posted about a week ago, now on page 3.
http://forum.xda-developers.com/showthread.php?t=1279238
I got a superuser update and while updating one day it updated succesfully.. now all of a sudden ts prompting update again and its not updating.. its throwing a update failed error message.
Anything that needs root access like titanium says cant get root acces..
whats going on?
The kernel you are using may not have the proper signature to update to the 3.0 binary. You can try the superuser update fixer from the market, and then update the binary, or just uninstall the new superuser from the market to revert back. I find the update fixer works temporarily for me untill I reboot, then it tells me to update binary again. I just reverted back for now.
Sent from my SPH-D700 using xda premium
I had a similar issue, where I would get something like "Obtaining root access: Failed" whenever I tried to update the binary file. I would also get a random FC of Superuser.
I uninstalled Superuser to get to the original one when I rooted my phone, and updated again via Market. It updated the binary file fine now. Hope that helps!
Note, I do also have Superuser Elite, but I didn't modify that at all.
hardrock121 said:
I got a superuser update and while updating one day it updated succesfully.. now all of a sudden ts prompting update again and its not updating.. its throwing a update failed error message.
Anything that needs root access like titanium says cant get root acces..
whats going on?
Click to expand...
Click to collapse
Had this happen a while back. Just clear the su cache and re-try, that should fix the error
Sent from my SPH-D700 using xda premium
Lol works fine on the stock kernel.
(I keep telling people that stock has its benefits) lol
Roll Tide
Works fine on ET4G stock kernel too.
Sent from my SPH-D710 using xda premium
JohnCorleone said:
Works fine on ET4G stock kernel too.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Sent you a pm, btw.
Roll Tide
Check the market, they've been updating the Superuser app, like crazy the last few days. I've now had about 3-4 updates (at least one per day).
Uninstall the update then unistall the super user app. Reinstall the super user app, reinstall the update, and then try again. This worked for me.
I had automatic updates enabled, I think it screws it up. So uncheck it and manually update it whenever it needs to be.
Here's a quoted answer from http://forum.xda-developers.com/showpost.php?p=18212299&postcount=2646
styles420 said:
The developer of su stated on his website that the binary cannot be updated if it is installed in /sbin, because that directory is actually a part of boot.img, which remains read only even if the system partition is mounted with read-write access. This is exactly how it is installed in SRF 1.2 (and probably all earlier versions, as well as several other Epic roms).
Rom developers will need to change the su install directory in order for the su app to be able to update the binary.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
But if you're using a stock setup, perhaps one of the other answers here would be more helpful.
Anyone having an issue with updating Su and getting nothing but lag and fc's?
I was able to use the cwm flashable Su binary, for manually adding Su. That was able to fix the compatibility issue.
Just wanted to share my findings.
Sent from my ADR6350 using xda premium
8on3s said:
Anyone having an issue with updating Su and getting nothing but lag and fc's?
I was able to use the cwm flashable Su binary, for manually adding Su. That was able to fix the compatibility issue.
Just wanted to share my findings.
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
This seems to be the case for many others.
In preferences I changed automatic response from prompt to allow and that bypasses the FC but doesn't fix the problem.
I did a fix permissions with ROM Manager and restarted my phone. So far no FC's.
Sent from my ADR6350 using xda premium
I had the same force close experience with SU 3.05. I loaded SU 2.3.6.1 on the phone and had similar problems. Then tried SU 2.3.6.3 and no force closes.
Jackie
MedleHed said:
I did a fix permissions with ROM Manager and restarted my phone. So far no FC's.
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
This cleared the fc issues? Killer to learn. Thanks for the info.
Sent from my ADR6350 using xda premium
i've tried all the options above, fixing permissions, downgrading to 2.3.6.1/2.3.6.3/3.0.2, updating the binaries and I still get the SU FC whenever it opens. Does anyone have any other suggestions to get this dumb problem fixed?
**Edit: 3.0.6 fixed it
I'm not getting FC's, but i have to go through hoops to get root access in adb. I used to just type
Code:
adb remount
adb shell
and i'm in shell as root.
Now i have to type
Code:
adb shell
su
I do recall in terminal emulator I used to be able to "su" and then "reboot recovery", straight to recovery I would go. Maybe my memory is foggy and perhaps it was my nexus one and G2 that did it and not this phone. I think at one point it worked on this device, now It just returns "sh: reboot: not found" . Was this perhaps something that changed from GB/ICS? Any insight would be helpful. Thanks
Sent from my BMF-D710 using xda premium
veritasaequita said:
I do recall in terminal emulator I used to be able to "su" and then "reboot recovery", straight to recovery I would go. Maybe my memory is foggy and perhaps it was my nexus one and G2 that did it and not this phone. I think at one point it worked on this device, now It just returns "sh: reboot: not found" . Was this perhaps something that changed from GB/ICS? Any insight would be helpful. Thanks
Sent from my BMF-D710 using xda premium
Click to expand...
Click to collapse
Nope it works great. I just checked it on my ICS build
In order for it it work there has to be the reboot binary in sbin and xbin. If reboot isn't working in terminal check those direcotories and make sure there is a reboot. If it isn't there. Find a ROM that has it and copy the file into both directories and set permissions. Not sure right off what the permissions are but look at the permissions of a file already in there and set the new file to the same.
cool thanks for the info. ill look and see but if memory serves me correct it hasn't worked on any custom ics that ive ran yet. i still cant remember if blazer on GB did it or not.
Sent from my SPH-D710 using xda premium
rujelus22 said:
Nope it works great. I just checked it on my ICS build
Click to expand...
Click to collapse
thanks for the heads up..i do have to admit yours is one of the only 2 ics i haven't ran yet. ima check it out tonight though
Sent from my SPH-D710 using xda premium
It is something being removed, rather than added, as it works in stock ICS (and GB) using the ODIN OneClicks.
sfhub said:
It is something being removed, rather than added, as it works in stock ICS (and GB) using the ODIN OneClicks.
Click to expand...
Click to collapse
cool thanks for the heads up mr. hub. just throwing this out there but i can recall a time back when i would flash most custom roms there was a t.emu that showed in sayyy titanium backup but couldnt be run. i would generally download a 2nd t.emu from the play store like the one in the pic and the reboot commands worked. im currently on frankenstein ego rom and upon fresh flash there is no t.emu showing in titanium backup. Like previous times i just grabbed it from play store and it was a "no go". could that be the issue of what is being taken away?
just wanted to throw this pic up because this is deff different than the "root" response i used to get.
Sent from my SPH-D710 using xda premium
Do this..
su
mount -o remount,rw /dev/block/mmcblk0p9 /system
ln -s /sbin/recovery /system/bin/reboot
mount -o remount,ro /system
reboot recovery
Or something like that..
Sent from my SPH-D710 using XDA
thanks chris, that did it. anybody have any thoughts on that 2nd pic i posted? with the "whoami" it used to always return "root" up until about the same time i noticed the reboot issue. i guess that one confuses me because i tuped "su" and the superuser allow/deny popped up and i clicked allow as isual. so with knowing that it seems odd to me that "whoami" returns "unknown". is that the same issue that was stopping the reboot command? sorry guys, i know its not real important it just helps me understand a little better about how things work.
Sent from my SPH-D710 using xda premium
I use the stock 4.0.3 rom, rooted by flashing the su binary to system.
Now I updated to the latest superuser market app, and it sees that there's a new version of su binary.
But when I try to update to this new su binary, everything else goes fine, but when it reaches the last step "Making sure new su works...", it says "Fail!".
What's going on?
Problem
I HAVE THIS PROBLEM Too i contacted chainfire but he doesnt answer me back.
Same issue here as well. It still grants all my apps superuser privileges though. I wonder if it matters?
Sent from my SGH-T989D using xda app-developers app
Should I make a flashable zip with the latest su? That would work.
Sent from a sexy turtle.
Same, lost root after cm10 flash, su fail.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
yes I'm having the same issue after flashing new ROM...but Tit Backup won't gain Root! ^^
Same issue.. The newest SU update is a fail. It's a total shock because it's always been solid in the past. We wouldn't be doing half the things we do on our phone without it
Sent from my SGH-T989 using xda premium
I also noted this when trying to update the binary on my GTab 7510. Only things I can suggest are choosing a ROM that has the latest Superuser + binary included, re-rooting with a newer root package, or uninstalling the update (although you constantly get the update notification which is annoying).
Same thing used to happen to me whenever I would try switching from SuperSU to Super User. Seems like SU anything from the market doesn't play nice with our phones.
i just reflash a root zip or superuser zip and that usually fixes it for me. no idea why its happening though.