I seriously need help. I have perma-root and have flashed clockwork recovery properly and have installed bacon bits but when i rebooted and went into setcpu to overclock it said that it doesnt have permission. so then to see if superuser permissions was working i went into rom manager and tried to do something and it said not able to perform privileged tasks. so i uninstalled superuser permissions and that didnt work. I reinstalled setcpu because i remembered i had a similar problem before when set cpu wasnt getting permission and required reinstalling. i can get into the clockwork recovery and have ran the vision bacon bits a couple of times to see if it would work. nope. i went into superuser permissions' settings and check for updates and found one but the thing couldnt install it so it saved the .zip in my sdcard and told me to flash it from recovery. wehn i do that the clockwork recovery replies back that the file is bad. I dont know what to do. I dont want to reset the whole device becauseu i dont want to loose all the apps i have. please help. please. I am a noob and this was my first android phone and i think i might have screwed it up.
Try running visionary then go into terminal type su hit enter then type sync and hit enter, reboot and you should be fine
Sent from my T-Mobile G2 using XDA App
When I type in su it says that it couldn't get permission. That's my problem ntohing can get super user permission
Sent from my T-Mobile G2 using XDA App
Did Superuser re-install when you ran Visionary again?
Go to Settings>Applications>Manage Applications and hit the 'All' tab. scroll down to Superuser and Clear Data. You might have denied 'Su' at one point. Go back and try to 'Su' in terminal and it should ask for permission again. Click 'always allow'. Hopefully that fixes everthing.
Nope I did that and it still says permission denied.
Sent from my T-Mobile G2 using XDA App
Uninstall visionary and SU completely. Reboot the phone. Grab the newest visionary apk from modaco (not on market anymore) and install it via whatever method you choose (adb or on-device package manager, whatever). Run visionary and let it do its thing and try setcpu again.
Also, I highly highly recommend downloading and learning to use titanium backup once you're fully rooted. It's a lifesaver.
The visionary method is a pain in the ass... The rage method is much more reliable... I sent you another message with better instructions... Just uninstall visionary first
Nevermind omarsalmin helped me fix it. Thanks man.
Sent from my T-Mobile G2 using XDA App
Related
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
Some apps like root explorer, rom manager and faster fix, which needs a phone rooted to work, are not working anymore. I have noticed these apps are not working when I flashed the latest radio- 26.14.04.28 and kernel Lordmod 8.5 cfs.
I reflashed to radio 26.09.04.11 (the recommended radio to use), reinstalled the apps but still none works.
I'm currently using cyanogenmod 7.1.0.
Does anyone know how to fix this problem?
Try uninstalling super user and then reinstalling. Also when you re install check for update through program.
Sent from my Inspire 4G using xda premium
It won't let me to uninstall superuser but by denying i got fastet fix to work. Thanks
That means superuser is in system/app. You can uninstall superuser using adb if you know how. In terminal you would type "adb uninstall /system/app/superuser.apk". Then type adb reboot. After it boots install superuser from market. You may have to type "adb root" before trying to uninstall to receive root access.
Sent from my Inspire 4G using xda premium
That also didn't work. I just flashed the rom again, which was a bummer but it fixed everthing.
Thanks for your help mate
How the hell did I lose root access? I flashed with unrevoked like 2 years ago... and all of a sudden my root apps are force closing...
I tried to re-root it using unrevoked and it says failed to obtain root...
WTF? in Hboot I have S-off still im on hboot 92
Did you get/apply an OTA?
No.... Im running cyanogen mod 7.1
Did you change anything ? flash a new rom? flash anything? update super user? install a new app? anything like that?
what version of superuser app and what version of busybox are installed?
--edit--
are the apps force closing, but after they initially launch successfully?
in other words... the problem is not with granting root permission , but simply with stability?
try this...
go in the settings of superuser app and enable logging;
try to launch the apps that you are having problems with;
check superuser log to see if root permission was granted when apps were launched;
if permissions were granted the problem is not root access....
Busy box are broken. wipe all and make a fresh install of your favorite room. That must fix it
Sorry 4 muy bad english
Sent from my ADR6300 using xda premium
Well. i think i fixed my problem..
I installed Super SU on top of superuser... and then uninstalled Super SU...
Then superuser would not grant root access to my apps...
So then i reinstalled SuperSU and had it manage my root.. and got rid of superuser.
Gorilla* said:
Well. i think i fixed my problem..
I installed Super SU on top of superuser... and then uninstalled Super SU...
Then superuser would not grant root access to my apps...
So then i reinstalled SuperSU and had it manage my root.. and got rid of superuser.
Click to expand...
Click to collapse
thar confuses me... but whatever... it is super you got it worked out... super super even
How do you go about switching from superuser to supersu?
Sent from my SPH-L710 using xda app-developers app
I dont think I understand your question. The su text entered into the terminal gives the terminal su access and is denoted by this symbol #, giving the terminal su access, but the superuser app always has access and asks you if you want to allow certain apps that require it access as well. Hope that helps!!
sent from my thumbs
youdoofus said:
I dont think I understand your question. The su text entered into the terminal gives the terminal su access and is denoted by this symbol #, giving the terminal su access, but the superuser app always has access and asks you if you want to allow certain apps that require it access as well. Hope that helps!!
sent from my thumbs
Click to expand...
Click to collapse
Let me try to clear it up a bit...I just got the s3 and I noticed that most roms use the root app "superuser" I have had better luck with android 4.0 + using the other root app by chainfire "supersu" my quesion is what is the best way to switch the root app that you use to grant su permissions...thanks for your help!
Sent from my SPH-L710 using xda app-developers app
Gotcha. Read the description of the app...
https://play.google.com/store/apps/details?id=eu.chainfire.supersu
sent from my thumbs
*sigh* There are times I wish we had a thumbs down option....
Here was the steps I was given, it worked for me without a problem.
1. Install SuperSu from Play and update binaries. Make sure it achieves root.
2. Delete Superuser.apk from system/app using a root file manager.
3. Install Superuser from Play.
4. Uninstall Superuser thru Play.
5. Reboot phone.
This will permanently get rid of Superuser and SuperSU should retain root functionality.
jdogg836 said:
*sigh* There are times I wish we had a thumbs down option....
Here was the steps I was given, it worked for me without a problem.
1. Install SuperSu from Play and update binaries. Make sure it achieves root.
2. Delete Superuser.apk from system/app using a root file manager.
3. Install Superuser from Play.
4. Uninstall Superuser thru Play.
5. Reboot phone.
This will permanently get rid of Superuser and SuperSU should retain root functionality.
Click to expand...
Click to collapse
thanks, i did the first half, didnt think about the reinstall though
Im currently running JMT which uses SuperSU. I would like to use Superuser. Ive tried just flashing Superuser, but how to remove SuperSU?
I posted this in the ROM's thread, but never got an answer so hoping someone here will know
Delete the Superuser.apk in the ROM (it's really SuperSU) and pull the "real" Superuser.apk from somewhere else.
Sent from my Nexus 4 using xda premium
android88 said:
Delete the Superuser.apk in the ROM (it's really SuperSU) and pull the "real" Superuser.apk from somewhere else.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I did so (system-->app), installed superuser, rebooted, cleared dalvik and fixed permissions...still getting the supersu shell message with apps, and still showing up on installed programs...what did I miss?
blackangst said:
I did so (system-->app), installed superuser, rebooted, cleared dalvik and fixed permissions...still getting the supersu shell message with apps, and still showing up on installed programs...what did I miss?
Click to expand...
Click to collapse
I'm curious, but would it just be a matter of updating the binaries with Superuser?
treefrog321 said:
I'm curious, but would it just be a matter of updating the binaries with Superuser?
Click to expand...
Click to collapse
Well, I downloaded a fresh copy from the market, and when I open it it doesn't update. Just shows no apps are assigned to it..
Sent from my SGH-T989 using xda app-developers app
blackangst said:
I did so (system-->app), installed superuser, rebooted, cleared dalvik and fixed permissions...still getting the supersu shell message with apps, and still showing up on installed programs...what did I miss?
Click to expand...
Click to collapse
There are some /bin and /xbin files too.
Sent from my Nexus 4 using xda premium
blackangst said:
Im currently running JMT which uses SuperSU. I would like to use Superuser. Ive tried just flashing Superuser, but how to remove SuperSU?
I posted this in the ROM's thread, but never got an answer so hoping someone here will know
Click to expand...
Click to collapse
Um, even easier...
Download SuperUser recovery flash zip and while still inside Android on device go to file manager open /system/apps and delete the SuperSU.apk
Now restart to recovery clear the cache and dalvick cache
choose install from SDCard
Find where you downloaded SuperUser.zip and flash
Restart
SuperSU is WAY better at handling Super User requests [for instance, it has a wait state on the pop-up where it does not go quite as fast so some apps that take a min to request super user and another min to display the pop you aren't already at 1 - 2 seconds] and for instance for quite some time Super User was known to seg fault [basically an error happens and it doesn't work to grant access right when that happens] whereas SuperSU was created later to kinda address that and some other issues in SuperUser [not saying SuperUser is bad it is updated and does it's job, it's just SuperSU does it better].
Just if any guide says use SuperUser just replace SuperUser with SuperSU when doing something and in app drawer just look under SuperSU for it's app and not SuperUser.
Thanks for the help and input guys
blackangst said:
Thanks for the help and input guys
Click to expand...
Click to collapse
Did you get it working the way you wanted?
RealPariah said:
Did you get it working the way you wanted?
Click to expand...
Click to collapse
Im gonna follow the advice that supersu is better and use it for awhile
RealPariah said:
Um, even easier...
Download SuperUser recovery flash zip and while still inside Android on device go to file manager open /system/apps and delete the SuperSU.apk
Now restart to recovery clear the cache and dalvick cache
choose install from SDCard
Find where you downloaded SuperUser.zip and flash
Restart
SuperSU is WAY better at handling Super User requests [for instance, it has a wait state on the pop-up where it does not go quite as fast so some apps that take a min to request super user and another min to display the pop you aren't already at 1 - 2 seconds] and for instance for quite some time Super User was known to seg fault [basically an error happens and it doesn't work to grant access right when that happens] whereas SuperSU was created later to kinda address that and some other issues in SuperUser [not saying SuperUser is bad it is updated and does it's job, it's just SuperSU does it better].
Just if any guide says use SuperUser just replace SuperUser with SuperSU when doing something and in app drawer just look under SuperSU for it's app and not SuperUser.
Click to expand...
Click to collapse
Can I do this with replacing Superuser with SuperSU (I'm running Avatar ROM & I miss using SuperSU)?