I'm running the LG8 OTA update and i am rooted. Seems like certain times when I'm using dolphin browser i get "shell blah blah", dolphin freezes, then force closes. Any suggestions guys?
I get this to in stick rooted Len i think
Most recent was when I downloaded a zip file clicked it on my notification bar thinking root explorer would open it instead gamboid attempted to open that's when I saw it
Sent from my Galaxy Emperor using Psycommu
Bump for help
Dubez said:
Bump for help
Click to expand...
Click to collapse
Go to applications and clear data, reboot, try it..if it still does it, I would uninstall and reinstall.
I would update superuser too, could be a binary issue.
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
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.
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
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)?