So last night I was using My Backup Pro to back up my files before I tried flashing the new CM for our phone and noticed that I didn't have busybox installed. I installed it and backed the phone up overnight. In the morning I noticed that my WiFi wouldn't turn on and that I couldn't flash anything. Ran root checker and my root is bad now. Anyone else experience any problems with rootbox? That and backing up my stuff are the only things I've done different lately. My phone is rooted with towelroot and bumped. I really don't feel like unrooting and returning back to stock to start the process over again but IDK how to fix the root. Root checker gives these error messages.....
Don't know much about the code, anyone have any suggestions?
kinjo1023 said:
So last night I was using My Backup Pro to back up my files before I tried flashing the new CM for our phone and noticed that I didn't have busybox installed. I installed it and backed the phone up overnight. In the morning I noticed that my WiFi wouldn't turn on and that I couldn't flash anything. Ran root checker and my root is bad now. Anyone else experience any problems with rootbox? That and backing up my stuff are the only things I've done different lately. My phone is rooted with towelroot and bumped. I really don't feel like unrooting and returning back to stock to start the process over again but IDK how to fix the root. Root checker gives these error messages.....
Don't know much about the code, anyone have any suggestions?
Click to expand...
Click to collapse
What does SuperSU or Superuser state when opened? Have you updated the binary or is that even an option?
Everything was up to date when I checked last night and supersu was working fine. I ended up unrooting and reverting back to stock and starting from scratch.
Related
I rooted my Epic 4G a few weeks ago. I had problems with the 3G, so I eventually had to do a full wipe with Odin (just flashing the kernel never worked, it kept failing. Only a full wipe worked.) So I re-rooted so I could restore all my backups with Titanium Backup and just kept root.
Well, today I went back into Titanium Backup only to discover that it said I was NOT rooted. This didn't make any sense...I did get one OTA update to my phone, but I was under the impression that these didn't remove root.
So I thought maybe it was my BusyBox...I used the link within Titanium to DL BusyBox. Went into the BusyBox installer, and it's main screen said I WAS rooted...the Heck?
So I tried to install, but I got the error saying it failed. The exact wording was "The application failed, either because your device is not nand unlocked or we were unable to remount."
So what gives?
I tried to re-root using the one-click, that didn't work. I tried to uninstall the root using the one-click uninstaller, that didn't work. The windows just hang up and don't do anything. I tried to re-flash the kernel with Odin and, just like last time, it didn't work. I get the feeling I'll have to do what I did last time and do a complete wipe with Odin, which will really suck because I'm not able to recreate any backups this time around.
sounds like a superuser permission issue to me.
ota removes root, always, just reroot
i tried searching the forums and google and couldnt find much of anything. i rooted using he debugfsroot tool and unlocked with adams tool. ive been running fne for a week or so i still have superuser installed and it gives permissions to titanium backup but hwen i tried to run the battery calibration app it said im not rooted. i downloaded root check basic and it says im not rooted either... i confused as ive not received any updates to my knowledge.. i delted the process that supposedly checks for updates... any ideas? i did try to reroot with the debugfsroot tool again and it all went through teh same steps and said successful etc. but i have the same problem.
did you update super user to the latest?
Yes i updated superuser and binary
any other ieas? is rooting through odin any worse of a way to root besides the fact that it will wipe my phone? it just seems wierd that would have happened.
Got it resolved. Superuser was set to auto allow.. for some reaskn it denied a few apps. Set it to prompt i allow and it works
My phone's been rooted ever since i got it and the only reason i was looking into unrooting it is because work email app won't install on a rooted device. i didn't want to return to stock and lock my bootloaders and all that as i really like the rom i'm using, which is Trickdroid 8.1. a lot of searching on the internet and several discussions pointed to using the unroot feature in supersu but i was under the impression that data on the phone would not be lost/deleted. boy was i wrong.
i went ahead to unroot in supersu and it took sometime to remove itself along with superuser app. unrooting seem to have worked as i am now able to install work email app BUT i just noticed all of my data is gone. anyone know what the hell happened?
I know there's not chance for me to get the files back but i'd just like to understand where I went wrong (if not). other than not backing up everything beforehand of course.
Q] Root "disabled" itself!? (Rooted phone that is no longer allowing root access)
Anyone here with a modded Galaxy S3 phone (or any) - that is rooted - have it just seemingly act as if it is no longer rooted? or unjustly denying root access for no apparent reason....
Have been rooted since purchase and have never seen or had any issue with this..have flashed custom recovery and rom's hundreds of times...no problems...currently using Task's latest KK 4.4.4 rom and had no issues from beginning...
It comes with SuperUser...i do usually install SuperSU instead but hadn't tried yet...it was fine and apps that needed root appeared ok..even SuperUser has three or four listed apps in the "allow" section...but all of a sudden I can't seem to give root access to anything else now..
First noticed the other day when trying to sideload an apk..couldn't...tried to do it manually by just copying it to system/apps folder and that's when the first message came up saying "it appears your device may not be rooted"...quite odd I thought.. i then tried to install SuperSU and it when SuperUser popped up to give it allowable root access it would only timeout and say denied...i then tried a bunch of other apps that require root and they would all just get denied by SuperUser...
Anyone seen this before or know what causes this and/or how to fix?
THanks for any help or suggestions
ps.. i'm no noob and have been doing this a long time and have rooted/modded dozens of phones, hundreds of times...but this issue is a new one for me.. IF i have to completely wipe and even go back to stock image and then start over to re-root and re-mod... I will and can do so easily..but that would be last resort if necessary...thanks!
pchemerys said:
Anyone here with a modded Galaxy S3 phone (or any) - that is rooted - have it just seemingly act as if it is no longer rooted? or unjustly denying root access for no apparent reason....
Have been rooted since purchase and have never seen or had any issue with this..have flashed custom recovery and rom's hundreds of times...no problems...currently using Task's latest KK 4.4.4 rom and had no issues from beginning...
It comes with SuperUser...i do usually install SuperSU instead but hadn't tried yet...it was fine and apps that needed root appeared ok..even SuperUser has three or four listed apps in the "allow" section...but all of a sudden I can't seem to give root access to anything else now..
First noticed the other day when trying to sideload an apk..couldn't...tried to do it manually by just copying it to system/apps folder and that's when the first message came up saying "it appears your device may not be rooted"...quite odd I thought.. i then tried to install SuperSU and it when SuperUser popped up to give it allowable root access it would only timeout and say denied...i then tried a bunch of other apps that require root and they would all just get denied by SuperUser...
Anyone seen this before or know what causes this and/or how to fix?
THanks for any help or suggestions
ps.. i'm no noob and have been doing this a long time and have rooted/modded dozens of phones, hundreds of times...but this issue is a new one for me.. IF i have to completely wipe and even go back to stock image and then start over to re-root and re-mod... I will and can do so easily..but that would be last resort if necessary...thanks!
Click to expand...
Click to collapse
i have no explanation for what happened, actually never heard it happen before.
why not try to re-root and see what happens. if that doesn't work, i would think your only option would be to flash it clean and start over.
Reroot. Or unroot then reroot.
yeah i was thinking that might have to be done.. was hoping not and that this was some sort of known or fixable issue...but may have no choice..will wait another couple days to see if i find anything and do it if no other option..
pchemerys said:
yeah i was thinking that might have to be done.. was hoping not and that this was some sort of known or fixable issue...but may have no choice..will wait another couple days to see if i find anything and do it if no other option..
Click to expand...
Click to collapse
well, i haven't seen any root methods that require wiping the phone, so why wait to try re-rooting?
I would try a new busybox with kinguser and reroot.
I have stock rom on my phone but had it rooted under 4.2.2.
Now i upgraded to 4.4.2 and something went wrong. The phone is still rooted and su is there but the root permission is gone.
I wonder now how i can get it back without reinstalling everything again.
So far, all programs i previously froze are still frozen which is great. But i can not use Titanium Backup at the moment since the permission is gone.
What would be the best route to go to fix this problem.
btw. i can not rooted it again since for example stump will tell me that its already rooted.