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
Related
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
Hello Hox owners,
I rooted my hox a while ago.
Just before the latest update came.
To get the last update, I needed to go back to stock recovery.
This went well I thought but since I have the Wifi problems i was looking at my phone closer and saw I got the stock recovery but SU app still installed.
I want to gain root access again, remove the superuser app, and unroot it fully because I need to send my phone back for repair soon (I hope).
The clockwork was installed succesfully, the latest version of superuser as well, update binaries also flawless but somehow still no root access according to es filemanager and titanium backup...
What do I need to do to get this fix?
Thnx in advance!
Ralph
twistednl said:
Hello Hox owners,
I rooted my hox a while ago.
Just before the latest update came.
To get the last update, I needed to go back to stock recovery.
This went well I thought but since I have the Wifi problems i was looking at my phone closer and saw I got the stock recovery but SU app still installed.
I want to gain root access again, remove the superuser app, and unroot it fully because I need to send my phone back for repair soon (I hope).
The clockwork was installed succesfully, the latest version of superuser as well, update binaries also flawless but somehow still no root access according to es filemanager and titanium backup...
What do I need to do to get this fix?
Thnx in advance!
Ralph
Click to expand...
Click to collapse
Maybe those apks were denied permissions for some reason. Try going into superuser & clearing all app default settings & reboot.
Sent from my HTC One X using xda premium
rayford85 said:
Maybe those apks were denied permissions for some reason. Try going into superuser & clearing all app default settings & reboot.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thnx for the reply but no apps are visible inside SuperSU.
Titanium was installed after I "rerooted" my hox.
There is no clear cache option inside SuperSU, right?
twistednl said:
Thnx for the reply but no apps are visible inside SuperSU.
Titanium was installed after I "rerooted" my hox.
There is no clear cache option inside SuperSU, right?
Click to expand...
Click to collapse
Can you get root checker from the market. & confirm that the Su binaries we installed correctly? If that app says your rooted then maybe try clearing superuser data. & reopening your apps.
Sent from my HTC One X using xda premium
rayford85 said:
Can you get root checker from the market. & confirm that the Su binaries we installed correctly? If that app says your rooted then maybe try clearing superuser data. & reopening your apps.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes! Exactly what needed to be done. Thnx a lot!
Sent from my HTC One X using XDA
Hi, I recently got a GSM Google Nexus from the Play store. Rooted it on ICS. Than got OTA for JB.
After the update I noticed that my Superuser permissions are acting weird like Rom Manager, Superuser itself and Quickboot are getting denied.
Also, Apex launcher reset itself to default without me doing anything.
And my GPS doesn't work on T-Mobile.
Is it one major problem, with a root issue or multiple problems with multiple issues?
Sent from my Galaxy Nexus using xda app-developers app
smartedpanda said:
Hi, I recently got a GSM Google Nexus from the Play store. Rooted it on ICS. Than got OTA for JB.
After the update I noticed that my Superuser permissions are acting weird like Rom Manager, Superuser itself and Quickboot are getting denied.
Also, Apex launcher reset itself to default without me doing anything.
And my GPS doesn't work on T-Mobile.
Is it one major problem, with a root issue or multiple problems with multiple issues?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
update your su. get the SuperSU app from the play store, open it, update your su.
I cant updated Superuser nor SuperSU
smartedpanda said:
I cant updated Superuser nor SuperSU
Click to expand...
Click to collapse
explain? what do you mean you cant update?
heres a flashable in recovery SuperSU. flash it, boot up, open the app, and update to the most recent.
I can't update it, I downloaded SuperSU from the Playstore, hit update it says Superuser has been denied. I tried to update Superuser, it denies itself. It can't flash anything in recover because it won't reboot into clockmodROM, it says clockmodRom denied too.
smartedpanda said:
I can't update it, I downloaded SuperSU from the Playstore, hit update it says Superuser has been denied. I tried to update Superuser, it denies itself. It can't flash anything in recover because it won't reboot into clockmodROM, it says clockmodRom denied too.
Click to expand...
Click to collapse
I had a similar problem where my root permissions were acting weird after the OTA to JB. Also, my su binary was out of date and I couldn't update through Superuser. So I put the phone to debugging mode and hacked away with adb. I made sure I mounted system to r/w (which I could, I dunno why), I updated the su binary with a push and downloaded SuperSU through Google Play.
I am running AOKP JB B1, just like suddenly, some of my Apps like DX tool box and DX power booster can't gain root access anymore, but other apps like root explorer work fine, I tried to update supersu and binary, no good.
Then I thought maybe I screw up the system because lots kernel flashed, so I just reflash AOKP JB B1 with full wipe , but still no good...
Could it be application compatibility problem or something wrong at my end?
Sent from my Galaxy Nexus using xda premium
qtwrk said:
I am running AOKP JB B1, just like suddenly, some of my Apps like DX tool box and DX power booster can't gain root access anymore, but other apps like root explorer work fine, I tried to update supersu and binary, no good.
Then I thought maybe I screw up the system because lots kernel flashed, so I just reflash AOKP JB B1 with full wipe , but still no good...
Could it be application compatibility problem or something wrong at my end?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Just a guess but some apps look for Superuser.apk to confirm root access. If your ROM has SuperSU.apk as SuperSU.apk that could be the issue. When I flash a ROM with SuperSU I always change the name to Superuser.apk.
HTH
3rdstring said:
Just a guess but some apps look for Superuser.apk to confirm root access. If your ROM has SuperSU.apk as SuperSU.apk that could be the issue. When I flash a ROM with SuperSU I always change the name to Superuser.apk.
HTH
Click to expand...
Click to collapse
No good, I tried installed superuser
Sent from my Galaxy Nexus using xda premium
3rdstring said:
Just a guess but some apps look for Superuser.apk to confirm root access. If your ROM has SuperSU.apk as SuperSU.apk that could be the issue. When I flash a ROM with SuperSU I always change the name to Superuser.apk.
HTH
Click to expand...
Click to collapse
the supersu apk is named Superuser.apk as well for compatibily purpose
@OP flash in recovery SuperSU.zip solve all ur problems
andQlimax said:
the supersu apk is named Superuser.apk as well for compatibily purpose
@OP flash in recovery SuperSU.zip solve all ur problems
Click to expand...
Click to collapse
still no good , DX tool box still says "Root not allowed, the operation is denied"
i also tried in CodenaAndroid and XeonHD , doesn't work on both of them , it should be applications compatibly preblem.
qtwrk said:
still no good , DX tool box still says "Root not allowed, the operation is denied"
i also tried in CodenaAndroid and XeonHD , doesn't work on both of them , it should be applications compatibly preblem.
Click to expand...
Click to collapse
a. update your busybox, use stericsons busybox updater from the play market. open the app, update busybox.
b. open your superuser or supersu app and make sure that your binaries are updated and that root is enabled. superuser has known issues with jelly bean.
c. if aokp has an optional root or no choice, enable root.
simms22 said:
a. update your busybox, use stericsons busybox updater from the play market. open the app, update busybox.
b. open your superuser or supersu app and make sure that your binaries are updated and that root is enabled. superuser has known issues with jelly bean.
c. if aokp has an optional root or no choice, enable root.
Click to expand...
Click to collapse
unfortunately , still can't , busybox is updated. SuperSu has updated the binaries as well and i even set to gain permission without asking, still can't
all other apps like ROOT EXPLORER , TRITIUM BACK UP, FRANCO KERNEL UPDATER, PGM2 and something more were able to gain access to root , only these 2 can't
this is the app that can not gain access ...
qtwrk said:
unfortunately , still can't , busybox is updated. SuperSu has updated the binaries as well and i even set to gain permission without asking, still can't
all other apps like ROOT EXPLORER , TRITIUM BACK UP, FRANCO KERNEL UPDATER, PGM2 and something more were able to gain access to root , only these 2 can't
this is the app that can not gain access ...
Click to expand...
Click to collapse
its the app. and on top of it, it doesnt want to close, it wants to run itself and download/send data. i uninstalled it really quick.
simms22 said:
its the app. and on top of it, it doesnt want to close, it wants to run itself and download/send data. i uninstalled it really quick.
Click to expand...
Click to collapse
It's app for system optimization or something like firewall, kill auto run apps, process management...
Ok... were you able to get root access?
Sent from my Galaxy Nexus using xda premium
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