It's happened to everyone and is scattered around everywhere, but how do I go about fixing this error? None of my root apps can access anything anymore and I get this error in Terminal when trying to "su".
lukekirstein said:
It's happened to everyone and is scattered around everywhere, but how do I go about fixing this error? None of my root apps can access anything anymore and I get this error in Terminal when trying to "su".
Click to expand...
Click to collapse
What were you doing before it was denying SU?
Usually a wipe will fix that. Recovery (Home + Power) => Alt-W => Alt-S with your preferred ROM.
I am M3 said:
Usually a wipe will fix that. Recovery (Home + Power) => Alt-W => Alt-S with your preferred ROM.
Click to expand...
Click to collapse
Well the OTA update may have had something to do with it...so who knows.
You installed an OTA update? Of course you're going to lose root. Now you've given yourself the task of re-rooting.
maxisma said:
AHH! Please forgive me! This should work:
mount system
cat /system/bin/sh > /system/bin/su
chmod 04755 /system/bin/su
if that doesn't fix the issue, try the same , but replace last line with chmod 4755 /system/bin/su
Click to expand...
Click to collapse
try that in RECOVERY (just to be safe)
i'm not sure what I was doing before I lost it...I know it worked before a shutdown/restart, and then the phone came on without it working. I'm using a theme which I flashed but SU worked fine. Never installed an OTA update.
I'll try those prompts in recovery.
Did you turn off USB Debugging? I've had problems with su and the SU Permission app if I turn that off under the Application > Development section.
lukekirstein said:
i'm not sure what I was doing before I lost it...I know it worked before a shutdown/restart, and then the phone came on without it working. I'm using a theme which I flashed but SU worked fine. Never installed an OTA update.
I'll try those prompts in recovery.
Click to expand...
Click to collapse
Please let us know if it works, a lot of people have had this problem
B-man007 said:
Please let us know if it works, a lot of people have had this problem
Click to expand...
Click to collapse
Yup, those prompts worked indeed. Did it in the recovery counsel and got SU to work
lukekirstein said:
Yup, those prompts worked indeed. Did it in the recovery counsel and got SU to work
Click to expand...
Click to collapse
good to know it wasn't any major haha. Can you change the title of the thread and put [SOLVED] so people can look here for it?
B-man007 said:
good to know it wasn't any major haha. Can you change the title of the thread and put [SOLVED] so people can look here for it?
Click to expand...
Click to collapse
No problem, thanks for the solution
help me root i unrooted and know stuck in rc29
i rooted my phone then i tried to install a ro got stuck on the su part it says denied so i unrootd dont know how or when i get back cupcake what do i do never had a chance to experiance anything?
digitalmixer said:
i rooted my phone then i tried to install a ro got stuck on the su part it says denied so i unrootd dont know how or when i get back cupcake what do i do never had a chance to experiance anything?
Click to expand...
Click to collapse
That has nothing to do with this thread. Please ask elsewhere.
Yahrghrr said:
Did you turn off USB Debugging? I've had problems with su and the SU Permission app if I turn that off under the Application > Development section.
Click to expand...
Click to collapse
wooww, MAJOR thanks , I never thought of this and I almost recovered my whole setup (since I had a amonRA rec that was not for dream, without terminal..)
all the time things were crashing, I thought the build was bugged.. thanks
Never had this problem. Still have USB Debugging turned on and I can access SuperUser via both Terminal Emulator and SUFBS Terminal.
Did you get that app that promises root or did you downgrade to RC29 first?
blackknightavalon said:
Never had this problem. Still have USB Debugging turned on and I can access SuperUser via both Terminal Emulator and SUFBS Terminal.
Did you get that app that promises root or did you downgrade to RC29 first?
Click to expand...
Click to collapse
the problem occurs when its OFF
Related
rcvd an orange branded DHD yesterday but was able to run Visionary 14 and run temproot then permroot as device wasn't upgraded.
Applied jkoljo easy one click radio off, sim unlock and super cid thing with all looking good with radio s-off confirmed. Also from terminal emulator I have #su access.
Via clockwork Mod installed a modaco custom rom - all looking good.
My problem now is that titanium backup says it could not acquire root privileges?
I have tried downloading a clean busybox but it fails on the verify stage. Sometimes I get error: application superuser (process com.noshufou.android.su) has stopped unexpectedley.
I've also tried clearing data for both TB and SU from settings > apps > manage apps... no good.
Any ideas?
beaverHausen said:
rcvd an orange branded DHD yesterday but was able to run Visionary 14 and run temproot then permroot as device wasn't upgraded.
Applied jkoljo easy one click radio off, sim unlock and super cid thing with all looking good with radio s-off confirmed. Also from terminal emulator I have #su access.
Via clockwork Mod installed a modaco custom rom - all looking good.
My problem now is that titanium backup says it could not acquire root privileges?
I have tried downloading a clean busybox but it fails on the verify stage. Sometimes I get error: application superuser (process com.noshufou.android.su) has stopped unexpectedley.
I've also tried clearing data for both TB and SU from settings > apps > manage apps... no good.
Any ideas?
Click to expand...
Click to collapse
if you flash your backup (you did make one right?) I assume root and SU are still intact, if so possibly a bad flash of modaco, try reflashing or flashing a different ROM and report back
I did make a backup but hadn't tried re-flashing. I'm giving it a go now.
OK so dropped into clockword mod recovery, cleaned dalvik, wiped fatory reset and cache then re-flashed modaco rom.
All installs fine however still have the force close when trying to run titanium backup and get the error can't get root privilege.
SU reports it is up to date but trying to run su in terminal emulator gives the com.noshufou.android.su stopped message.
Apart from not being able to restore/backup using TB at least I can still install ROM.
The root problem is in the rom you are using, try for example Android Revolution 2.0.3. Some 1.72 based roms have problems with superuser.
try re-installing updating Superuser via the market see if that helps as it does sound like an issue with Superuser itself
ghostofcain said:
try re-installing updating Superuser via the market see if that helps as it does sound like an issue with Superuser itself
Click to expand...
Click to collapse
Thanks but that doesn't work.
beaverHausen said:
Thanks but that doesn't work.
Click to expand...
Click to collapse
which MCR are you using? is it a pre-baked or cooked one?
A baked one on the r2.
beaverHausen said:
A baked one on the r2.
Click to expand...
Click to collapse
appears to be a known issue with MCR r2 a possible work around is after a FC run superuser yourself and then the app might run normally if you try launching it again.
Edit: on further investigation, there is a patched SU available over on the G2 Forums apparently it's and issue on all 1.72.x.x Sense ROMs, wouldn't know personally as I don't use Sense
ghostofcain said:
Last edited by ghostofcain
Click to expand...
Click to collapse
Totally off topic, but going off your name, you're a fellow NMA fan?
iridium21 said:
Totally off topic, but going off your name, you're a fellow NMA fan?
Click to expand...
Click to collapse
Not 'alf mate
ghostofcain said:
on further investigation, there is a patched SU available
Click to expand...
Click to collapse
Cheers buddy, I ran the patch and now have Titanium Backup, Clockword Mod and Terminal Emulator all with SU!
hie guys, i have juz unrooted my phone using the se update
service. so now i would like to know whether the unrooting is successful!
Use ROOTCHECKER app....attached to this post.....
PRESS THANKS IF I HELPED......
Well, check if the su app is still there or not
Sent from my X8 using XDA App
well i already checked whther su was there or not bt it is not. more on its not difficult to install it from the market. doesn't mean that when you have su, it means your phone is rooted.
You can also try Titanium Backup - it will show You an error if Your phone is not rooted
just try some apps, what require root.
GROSS23456 said:
well i already checked whther su was there or not bt it is not. more on its not difficult to install it from the market. doesn't mean that when you have su, it means your phone is rooted.
Click to expand...
Click to collapse
BUT did you install it from the market?
i guess not.
if SU isnt their and you haven't downloaded it from the market + you have tried apps that require Root access and have gave you an error, then your not rooted
Bolussimo said:
You can also try Titanium Backup - it will show You an error if Your phone is not rooted
Click to expand...
Click to collapse
we seem to be getting somewhere now LOL
CaH9 said:
just try some apps, what require root.
Click to expand...
Click to collapse
Even better. Hope he gives results soon
CONCLUSION: A sigh *sigh*
Hey guys, can u help me, i cant update SU binary, i dont know why? I had some custom ROM and i went back to the stock, but today i wanted to root my phone again, and when SU shown, i go there to update it and binary, but binary wont update... Can anyone tell me whats the problem?
Sorry for my english...
vujkeraf said:
Hey guys, can u help me, i cant update SU binary, i dont know why? I had some custom ROM and i went back to the stock, but today i wanted to root my phone again, and when SU shown, i go there to update it and binary, but binary wont update... Can anyone tell me whats the problem?
Sorry for my english...
Click to expand...
Click to collapse
You have to connected to internet
SnowPluralism said:
You have to connected to internet
Click to expand...
Click to collapse
I am always connected to the internet, but it fails to update... Dont know why
Reroot the phone is your only option
Sent via that ninja standing right behind you
vujkeraf said:
I am always connected to the internet, but it fails to update... Dont know why
Click to expand...
Click to collapse
Go to market ... Update superuser app and try again
Sent from my GT-S5830 using xda premium
http://forum.xda-developers.com/showthread.php?t=1837056
Here u will find latest SU app.
Flash from Recovery
vujkeraf said:
Hey guys, can u help me, i cant update SU binary, i dont know why? I had some custom ROM and i went back to the stock, but today i wanted to root my phone again, and when SU shown, i go there to update it and binary, but binary wont update... Can anyone tell me whats the problem?
Sorry for my english...
Click to expand...
Click to collapse
I had this issue too, but i coudnt fix it, updating the SU app wont change your phones binaries, i updated but in the end it couldn ask for root permisions and update failed, so i decided to go to options and hide the outdated binaries notification and troubles solved, i know its not the best way but at least it wont bother me anymore lol
try superSU, i tried on my friend tablet when superuser didn't want to update then it automatically solve the problem.
idk if it will works on yours but it never hurts to try...
look if superuser is listed on the list with apps that get root (in superuser-app)
if yes => delete it, close it, reopen it and try again to update
if not => reboot, DONT DO ANYTHING BESIDES THE FASTEST WAY into superuser app and then try updating
if 2 is not working, retry it about 5 times. worked for me once. (not exactly at 5 times, but i ha to repeat this and on one try it suddenly worked. strange but....well...did the job)
Thx guys, it helped. I just rooted my phone again and the problem is solved.
I have sought on way to update my SU app,
but i flash many root's app and the old version persists
any idea ?
Reynaldo Aguiar said:
I have sought on way to update my SU app,
but i flash many root's app and the old version persists
any idea ?
Click to expand...
Click to collapse
Could always use adb interface and push latest su binary to it. Then try to load supersu app.
bunny12 said:
thanks it did work for the time.... but why its still written update when su binary is already updated to its latest version can you tell please
Click to expand...
Click to collapse
Ignore it, even if you update it again it is just the same...
Sent from my GT-S5830 using Tapatalk 2
thats all i did, how can i get my root back?
did u just lose the supersu??
maybe u dont know, then go to playstore and get it again
it it works, problem solved
Yes I still have the app but no su binary
iamflamez said:
Yes I still have the app but no su binary
Click to expand...
Click to collapse
Do you have an update about the situation?
Very curious if more people have that problem.
iamflamez said:
Yes I still have the app but no su binary
Click to expand...
Click to collapse
Keep resetting your phone until root comes back, it's just luck if the phone boots with root or not. One of the many bugs with 4.3 I wish I didn't update it has nothing that benefits me over 4.2.2
Apologies if this is blindingly obvious, but I've googled and searched and have found a lot of conflicting information this, so bear with me:
I went through the Moto bootloader unlock process for my Rogers Moto X and when I boot into fastboot it says it's unlocked. I then installed SuperSU and it seems to be working when I launch apps that require SU access. And some sites say if I'm on 4.4.3 it's impossible to make /system writeable. Basically, I'm still unable to install stuff that writes to /system like Busybox.
I've read about how /system is write-protected but haven't figured out how to actually fix this - some posts say start in recovery and I should be able to write to /system, others say it should work after I've gone through the Moto bootloader unlock process.
Can anyone here help a rsomewhat-newb get this sorted?
neil.io said:
Apologies if this is blindingly obvious, but I've googled and searched and have found a lot of conflicting information this, so bear with me:
I went through the Moto bootloader unlock process for my Rogers Moto X and when I boot into fastboot it says it's unlocked. I then installed SuperSU and it seems to be working when I launch apps that require SU access. And some sites say if I'm on 4.4.3 it's impossible to make /system writeable. Basically, I'm still unable to install stuff that writes to /system like Busybox.
I've read about how /system is write-protected but haven't figured out how to actually fix this - some posts say start in recovery and I should be able to write to /system, others say it should work after I've gone through the Moto bootloader unlock process.
Can anyone here help a rsomewhat-newb get this sorted?
Click to expand...
Click to collapse
You flashed the latest version of TWRP custom recovery?
samwathegreat said:
You flashed the latest version of TWRP custom recovery?
Click to expand...
Click to collapse
Think so - this was the image file I used: twrp-2.6.3.1-ghost-4.4.img
neil.io said:
Think so - this was the image file I used: twrp-2.6.3.1-ghost-4.4.img
Click to expand...
Click to collapse
That might be the issue. It might not be compatible with 4.4.3
Try this one: http://techerrata.com/browse/twrp2/ghost
Also, which version of SuperSU are you using? There was a new one released recently. Find it here: http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip (Flash it from within TWRP - install ZIP)
Please update, and then advise whether or not your issue is resolved.
EDIT: Also, make sure you are using the "stericson" busybox variant. Others have been reported to cause issues.
Thanks a lot for the fast responses - really appreciated.
I redid recovery using the version you linked to and also reinstalled SuperSU (I was using the current version already). When I try to install Busybox using the Stericson version as you mentioned I get an immediate error that it wasn't able to open a shell w/ root access. Running Root Checker tells me that root access is working, so I'm not sure what I've missed.
Again, many thanks!
neil.io said:
Thanks a lot for the fast responses - really appreciated.
I redid recovery using the version you linked to and also reinstalled SuperSU (I was using the current version already). When I try to install Busybox using the Stericson version as you mentioned I get an immediate error that it wasn't able to open a shell w/ root access. Running Root Checker tells me that root access is working, so I'm not sure what I've missed.
Again, many thanks!
Click to expand...
Click to collapse
Open SuperSU, and check to see if busybox is listed under apps. There should be a green "#" symbol next to it. It SHOULD have prompted you to grant access to it, so perhaps at some point you either denied the su request, or didn't see it. If you see a RED "#" symbol, tap it, and change to "Grant".
Please advise...
It is, and it did have a green # beside it. I tried removing it and it requested permission as expected, but still failed.
I can't seem to get anything to install to system - Adaway also fails, for example.
neil.io said:
It is, and it did have a green # beside it. I tried removing it and it requested permission as expected, but still failed.
I can't seem to get anything to install to system - Adaway also fails, for example.
Click to expand...
Click to collapse
I would suggest a full return to stock (follow the return to stock thread in the general sub-forum). This is not normal....
You appear to be using the XT1053, correct? Take caution to NOT downgrade or you could end up with a brick.
Flashing the entire stock SBF can actually fix a corrupted filesystem - this is my best guess at what might fix your issue.
samwathegreat said:
Flashing the entire stock SBF can actually fix a corrupted filesystem - this is my best guess at what might fix your issue.
Click to expand...
Click to collapse
Thanks again for the help. I just flashed the stock SBF and that seems to have fixed whatever was blocking Adaway from properly writing its hosts file, but Busybox stubbornly refuses to install. I got the permission request for SU when I launched it, but it fails just after I initiate the install. I tried changing the location to /system/bin with no luck.
Any other suggestions? I'm ready to give up for now, but it's frustrating when my Nexus 4 was so simple to set up.
neil.io said:
Thanks again for the help. I just flashed the stock SBF and that seems to have fixed whatever was blocking Adaway from properly writing its hosts file, but Busybox stubbornly refuses to install. I got the permission request for SU when I launched it, but it fails just after I initiate the install. I tried changing the location to /system/bin with no luck.
Any other suggestions? I'm ready to give up for now, but it's frustrating when my Nexus 4 was so simple to set up.
Click to expand...
Click to collapse
How did you SBF to stock? Did you use RSD Lite? Did you retain userdata, or wipe everything (suggested)?
The stericson variant installs fine for me...granted I'm on 4.4.2 (the latest for my variant).
I did NOT use smart install...just used regular install to /system/xbin (You might consider trying smart install if you haven't yet...)
Honestly, I'm out of ideas. Although the "stericson" variant is recommended, perhaps you should try another version from the market if you need busybox.
I've done extensive searches and haven't found anyone else having a similar issue - even with Moto X on 4.4.3
I gave up and used the recovery method. Really odd - it does seem like the other installer apps couldn't mount /system as writeable, but it's weird that other apps that installed to that area worked.
Anyway, thanks again!