Develop Bugs

Can't use superuser permissions?

I rooted my phone and installed Cyanogen Mod and as part of the process of installing it I made sure I had it rooted and had superuser permissions. Now, though for some reason whenever my phone tries to ask me for the permissions it says that the app superuser permissions has errored out and needed to be force closed. What could be causing this? I used unrEVOked to root my phone and it's worked fine in the past. Any ideas?
Sent from my ADR6300 using XDA App

Aneruin said:
I rooted my phone and installed Cyanogen Mod and as part of the process of installing it I made sure I had it rooted and had superuser permissions. Now, though for some reason whenever my phone tries to ask me for the permissions it says that the app superuser permissions has errored out and needed to be force closed. What could be causing this? I used unrEVOked to root my phone and it's worked fine in the past. Any ideas?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Go into Settings > Applications > Manage Applications > Superuser, then hit clear data. That may fix the problem.
If not go into Rom Manager > Fix Permissions, let that go through, reboot, and see if that worked.
If neither of those work I would try uninstalling and reinstalling the SU app.

Thanks a bunch. I went ahead and did them both so I couldn't tell you which one fixed it but thanks!
Sent from my ADR6300 using XDA App

[Q] Superuser upgrade

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.

For those with the SU Bug

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

Unable to install busybox

I'm in the middle of trying to get things setup so I can try out the arm version of Bt5. Running stock rom, 2.3.4, using busybox installer downloaded from the market. Tried a few versions of busybox and the best I get is a restart. My suspicions are that it can't write to that part of the nand even with root unless I'm in recovery or something close to that. Anyone who has had this problem in the past care to shed some light on the subject?
Sent from my ADR6300 using XDA App

brenton1786 said:
I'm in the middle of trying to get things setup so I can try out the arm version of Bt5. Running stock rom, 2.3.4, using busybox installer downloaded from the market. Tried a few versions of busybox and the best I get is a restart. My suspicions are that it can't write to that part of the nand even with root unless I'm in recovery or something close to that. Anyone who has had this problem in the past care to shed some light on the subject?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Are you s-off? Do you have superuser installed and functioning? Which busybox installer are you using, stericsons or jrummys? Does it install fine and then crash when accessing it or will it not even install? Does it give any certain error messages?

Try this from the V6 OP.
http://forum.xda-developers.com/attachment.php?attachmentid=873978&d=1327609636
Flashable zip of newest busybox.
Backup first, just in case.
Thanks to wraithdu and zep.

cmlusco said:
Are you s-off? Do you have superuser installed and functioning? Which busybox installer are you using, stericsons or jrummys? Does it install fine and then crash when accessing it or will it not even install? Does it give any certain error messages?
Click to expand...
Click to collapse
Superuser is installed and running, was trying jrummy, the app installs and loads. Busybox does not install at all and I was getting no errors, it would force the dinc to restart.
Sent from my ADR6300 using XDA App

omniatic said:
Try this from the V6 OP.
http://forum.xda-developers.com/attachment.php?attachmentid=873978&d=1327609636
Flashable zip of newest busybox.
Backup first, just in case.
Thanks to wraithdu and zep.
Click to expand...
Click to collapse
Flash via recovery, just like an update/rom?
Sent from my ADR6300 using XDA App

brenton1786 said:
Flash via recovery, just like an update/rom?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Worth a try, cant hurt anything.

Have busybox installed but still can not load Bt5. I'm going to try some screen shots and see if that might give some better ideas as to what the issue might be.
Sent from my ADR6300 using XDA App

Terminal emulator reboots?

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