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
Related
Guys
I don't get this at all, can anyone please help out?
I have a Nexus One. Have been running Cyanogen since purchase, upgraded to 5.0.6-N1 few weeks ago. Obviously, root access and all that. Just a few days ago, I backed up the device with nandroid and flashed it with a Enoc theme. That also went well, but I suddenly noticed apparent lack of root access. Apps that require it wouldn't work (like QuickBoot, MarketEnabler). So I wiped the device and flashed with a clean 5.0.6-N1 and restored the backup prior to theme update, but now I cant get the root access back no matter which backup I restore (even older ones).
Any clues on what might have caused it? I cant think of any indications that the theme update might have anything to do with it, but that is pretty much only update I've done to the phone.
Thanks
what recovery image do you have?
Hey, thanks for the reply. I don't have any recovery image.
I just tried booting in recovery mode, wiping the phone and then flashing with the Cyanogen 5.0.6. That should get me a fresh install on which I then apply a nandroid restore of the OS prior to the theme update I mentioned above.
Besides, I see that applying the recovery image via terminal starts with 'su' command. That one gives me 'permission denied' after my problem occured. Its almost as if my phone wasn't rooted at all, which it definetly is.
So here is my issue. I have a Droid X. Used EasyRoot to root before 2.2, once 2.2 came out i ditched easyroot, DLed 2.2 and then did the Droid2 Method of installing root. Since I finally got froyo (and figured Ginger woudlnt be out for awhile) i figured i would try my hands at adding some themes. I installed ROM Manager and Bootstrapper (both paid) and flashed clokworkmod and played around with them for a day or so, and kinda figured it wasnt really what i wanted to get into, and decided to go back to just plain root.
So i UNinstalled both root manager and Bootstrapper, and did a batt pull... Now everytime i do a batt pull the "clockwork recovery" screen comes up asking if i want to recover my device. Why is this still on the phone if i uninstalled ROM Manager? There is a folder in my files labeled "Clockwork" but im almost afraid now that if i delete it ill get a Bloop.
How do i go about getting clockwork off my phone? Also, with the Droid2 root method, if i just remove the root, will clockwork and everything else go with it? then i can just re-root?
Clockwork Recovery is seperate from ROM Manager.
ROM Manager can be used to control Clockwork Recovery, but it is NOT CR.
I don't own a DroidX, so I don't know if it's possible to get back to the stock recovery, but no matter what, you shouldn't have to worry about anything.
Clockwork should stay on your phone pretty much regardless of anything else. Even if you factory restore your phone, it'll still be there because it's your recovery partition.
Basically, think of it as that message on an HP/Dell/Others that says "Press F11 to enter recovery mode" and from there you can reinstall a factory refresh of windows.
Same thing here, except you'd restore a backup you've made previously.
You could also flash a ROM you've found online.
You could also initiate a factory reset, but if you've messed with anything in the /system directory, it might not work.
That makes sense. So I guess my next question is Ifi have to take the phone back to vzw will that flag it as voided? Even if I remove root? And will I have problems with any future OTAs?
Sent from my DROIDX using Tapatalk
So, I purchased my Samsung Galaxy S (Captivate) last weekend. I had it rooted and everything was fine. Then I got rid of some of the bloatware. I wrote a couple of programs for myself to use, so I needed to enable side-loading. I did that-successfully.
First sign of a problem was when I went to the marketplace and it would not download any single app that I tried. So, I went to restore the phone using the backup I made, but some reason it wasn't there.
Then I decided to revert to factory settings. I did a hard reset, but the problem was still not resolved. Then I found a thread on here about Odin 3. I've been trying to use that all night but the best I've gotten is to the File Analysis step. I've tried at least 10 different times.
I'm trying to get everything back up and running and preferably rooted again so that I can use my Titanium backup to restore all my apps and settings.
I'm at my wits end, and any help would be greatly appreciated.
Thanks.
Factory reset would not solve any problems that may have been caused by deleting core apps. Is your phone rooted and nand unlocked (baseband) or just rooted? Are you running a custom rom? If so you need to reflash the rom after clearing cache and dalvik cache. If you still have the original rom then you can reflash an official samsung firmware using odin, look for your handsets firmware on www.samfirmwares.com
Other than that you could try finding out which apps are needed and using root explorer you may be able to fix the version you have. If the market is your only issue then try clearing data and cache settings/manage apps/market and download manager (two different apps)
How did you root your phone? Did you install a custom ROM yet? What bloatware did you remove, and how did you go about it?
Ok. In the wee hours this morning I finally got Odin to work and now everything works as it should. I switched computers and the program worked right away. Intersting tidbit though, I accidentally left the sim card in during the reflash and I had no ill effects. I'm actually wondering if that helped me.
Thanks tina333.
nenol, I used the one touch root. I have not installed a custom rom and I don't remember exactly which of the programs I uninstalled. I used Titanium backup to both backup my apps and to delete the bloatware.
There are very few system apps that are not needed by the system, titanium only backs up data by default. Be careful what you delete and always research first
I should phrase the question, "Can I lose root if I do not update with an HTC/TMO update?".
I walked through guide (http://forum.xda-developers.com/showthread.php?t=1192300) to root my Sensation and it worked with no issues. I had the root phone for several weeks and decided to try a couple new ROMs. I did my due diligence and did a full backup with Titanium and then a CM backup. The problem arose when I flashed in the Revolution HD ROM. Once installed, I could not get Titanium to work. It kept saying it could not get root permission. I checked SuperUser, and it was there, but would not prompt to allow root access for any of my apps. I restored back to my original ROM and again, I do not seem to have root. All my applications are there, SuperUser is set to prompt me when an app requests root, but none of the root apps will work anymore. I grabbed a root checking app off the market, and it says it cannot obtain root too. I checked fastboot and it still shows S-OFF. I've never had this issue with any of my other Android devices once I rooted them. I was able to get my root access back by following step 3 of the guide, but I'm curious how I lost root by flashing in another custom ROM. Any ideas?
You didn't lose root you lost root access. It happened with two of my nandroids from CWM. I just erased them and started over from a fresh rom install and everything was fine. It kinda suxs though lol when SU tells you it can't get access. There are a few if us that this happened too. Its been mentioned in yje Clockwork thread.
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.