Related
Some how I lost root access to my phone. I was having memory issues with the phone and after uninstalling everything it was suggested I install a memory manager. I did and it didn't work so I uninstalled it and I think my root access went with it.
At any rate I was instructed to open a command line on my phone and type SU and see what happens. I installed ConnectBot so I could get the command line access and typed SU and it came back access denied. So I guess that proves I lost my root access. But my question now is what guide do I use to get it back? The original guide I used said it was for v1.5. The other guides listed are for people that have done the OTA and have the Sprint 2.1 running on their phones. Well I'm in between and I have Damages 2.09.1 rom.
So what is my next move to get the root back? In reality do I need root at this point? What would happen if I just reflashed DC's rom again?
Help or comments will be appreciated.......
Lisa
You didn't lose root, you lost Superuser, search the DC2.8 thread about SU...
I did and either didn't find the right threads or didn't find the solution but I didn't get it fixed. All I found was that debugging needed to be checked and it is. Still no SU access. Give me. More help if you can......
Thanks...
Lisa
I did and either didn't find the right threads or didn't find the solution but I didn't get it fixed. All I found was that debugging needed to be checked and it is. Still no SU access. Give me. More help if you can......
Thanks...
Lisa
Download superuser from the site below and flash it though recovery. That should fix it. Make sure to get the proper zip for your version of Android.
http://handheld.softpedia.com/get/System-Utilities/Enhancements/Superuser-106560.shtml
Open your app drawer...Do you see anything that says Superuser Permissions?
What memory issues were you having? If it was storage problems, perhaps try Apps2SD -- usually takes care of any internal storage issues when you get it working. This thread here is for A2SD: http://forum.xda-developers.com/showthread.php?t=715116
Reflashing the DC ROM really wouldn't hurt anything either, you'd just have to re-setup your accounts, preferences, etc. and redownload all your market apps.
Lots of good information in these two responses. I have some questions. First what Rom do I have? Cupcake, eclair, donut? Just know its DC's last Rom.
Next could you explain how to "flash from recovery". Is that done through Nandroid?
Next I do have SU in my app drawer. It will open and has a green button besides my to programs that use SU. But SU doesn't seem to be working.
Finally flashing the Rom again is something I want to avoid as I really don't want to start from scratch.....
Thanks for your help.........
Lisa
mslisaj said:
Lots of good information in these two responses. I have some questions. First what Rom do I have? Cupcake, eclair, donut? Just know its DC's last Rom.
Click to expand...
Click to collapse
These refer to versions of Android. You have 2.1 which is aka "eclair". 1.5 was aka "cupcake", 1.6 was "donut". Almost all ROMs here are 2.1 eclair, with the exception of the cyanogenmod which is android 2.2 aka "froyo".
mslisaj said:
Next could you explain how to "flash from recovery". Is that done through Nandroid?
Click to expand...
Click to collapse
No, it is done in recovery. To boot into recovery, hold Home then press Power on your phone. One of your recovery menu options will be "Flash zip from sd card". After you put any .zip files on the base/root of your SD card, this is how you will flash (or install) them. "Nandroid" only refers to the process of backing up and restoring your data, which is a separate option in the recovery console (Backup/Restore)
Did you try reinstalling the Superuser.apk? It may just need to be reinstalled.
Mr. chromiumleaf.....
Thanks so much for the information here. I have "flashed" from recovery but didn't realize that was what it was technically called. I have in my own terms refered to "Recovery Mode" as Nandroid. But now I will associate both as one. Thanks for clarifying what version Rom I'm running. I didn't want to guess so I asked. I think I will uninstall the Superuser that I have now and then reflash the new version that I will down load. I will report back. This would be so cool if this settled my problem............
So appreciate it and I will let you know..........
Lisa
I am following through as I alway do to thank you all for your help and tell you how I resolved the problem. I received some great advice from everyone and the last tip, which is usually my luck was the best.
The bottom line someone questioned why I thought I lost root. I explained what was going on and the best and final suggestion was to down load the latest Superuser.apk and flash through "recovery". Yes I had to ask exactly what that meant but I followed the directions and did it. Problem solved. I had SU working on my phone for Root Explorer and Titanium Backup. Then I downloaded Cachecleaner and it worked this time perfectly and it found 25MB of junk on my phone and cleared it out. So now I'm running 40MB of internal memory with all my programs working rather snappy now. In my estimation I screwed up the SU with the memory manager that was recommended somewhere along the line. When it didn't do anything for me I uninstalled it and I think my SU went with it. But the phone is fixed and I want to thank you all for your time in responding to my problem and requests. Sometimes multiple............
Thanks again.....
Lisa
Good to hear you got everything fixed. Glad to have helped out.
Yeah...and that's why there are people in this world more patient than I.
Sent from my HERO200 using XDA App
Used the 1 click method to root the Vibrant, overclocked it, and did the lag fix. Was getting horrible distortion when on calls, using the Vibrant 2.1 Vanilla ROM, so I decided to 1 click unroot. For some reason upadate.zip was not on my SD but on phone HD so the unroot was unsuccessfull. Now Im stuck with the root, recovery mode allows me to select reinstal packages - nothing happens - and I'm back to the same rom/root - once phone reboots. I even put the update.zip back on the sd - but phone is not recognizing it or installing it for some reason. I somehow lost superuser as well. Please help me get back to unroot - if its possible!
Thanks
i'm a noob here too. but this happened to me before (the pc doesnt recgnze the sd card or phone storage. )
just place in one of the drive that PC recognize and then use eStrong or some file manager to copy & paste it... hope this help..
Dropbox is a nice tool too.. figure it out.. it's really useful
I will definitely try that! Thanks. I tried downloading/installing Titanium Backup - as I previously backed up apps - it asked for Busy Box, which disappeared! I downloaded busy Box - it said my phone was not rooted! WTF! It looks rooted - just like Vanilla ROM - defiantly not like stock, when I bought it. I just hope I didnt mess it up. After i initially "1 click" unrooted - I thought it had worked, I restored phone to factory settings - this might also be causing my predicament! I just cant get passed the , reinstall packages, in the boot menu, like before - phone reboots itself right away, after partially/or not at all installing the update.zip from SD!
I think I may need a manual way of getting unrooted/ back to stock!
Please help! Phone works fine otherwise - just looks like the Vanila Rom and root, without any of the benefits!
boot into download mode and flash back to stock using ODIN if you look around you should be able to find some tutorials for it. You'll need to have the android SDK and samsung's drivers installed on your PC though
OK, thanks - sounds like I have to reroot my Vibrant, since it has a lot of the root stuff missing afyter I accidently reset to factory settings while rooted! After I root Ill just have to unroot, right!
Ill look for tutorials, thanks!
Hi all,
I just had a little problem with my CW recovery not finding /cache/update.zip and not working properly. Doing some searching I came up with warnings about people getting bricked by using ROM Manager. Some are recommending not using RM
I also read a post that I did not understand saying that ROM Manager installs "fake" versions of CW recovery.
I reflashed CW in ROM Manager to fix the problem I had. I see I have an update.zip on the root of my sd card. I'm wondering if this is necessary for my system now and I'm hesitant to delete it.
I'm more afraid of getting bricked!
BTW- hope I'm posting in the right forum!
I also see that i cannot delete ROM Manager. Even Titanium can't delete it. Gives error saying it cannot find apk. I know it can be deleted manually.
So what's the verdict here?
ROMmanager has been broken on my incredible too ever since the new string of updates. You can install everything manually after it gives you the error. it is a pain in the butt, but i like to flash everything manually anyways... i suggest getting a file manager like ASTRO and after downloading from rom manager, moving the files from Clockwork/Downloads to your root, then going into recovery using quickboot... this has given me he best results when i do not have my pooter present, and i want to mess around. there are many others that are having a problem with RM on their dinc's as well. (i am guessing you are on a Dinc by your sig and problem)
you are not alone. Deleting the update.zip wont hurt. neither will keeping it until you need to install another updae.zip. wish i could help fix it, but manual install is he best i have found. i think you can dig through your SD in CWM also without ASTRO...
Honestly, most issues are user error, I have never had an issue with rom manager, both on my droid and incredible.
the updae.zip can be removed also.
and rom manager can't brick your phone, but installing bad files or roms with it can.
Honestly, most issues are user error, I have never had an issue with rom manager, both on my droid and incredible.
Click to expand...
Click to collapse
Well I didn't do anything except hit "backup current rom" in RM. Never had a recovery problem before that and I have used recovery a lot.
http://forum.xda-developers.com/showthread.php?p=8450800
http://androidforums.com/incredible-all-things-root/187837-rom-manager-problem.html#post1696863
http://androidforums.com/incredible-all-things-root/187412-what-did-i-do-wrong.html
http://androidforums.com/incredible-all-things-root/139689-rom-manager-problem.html
http://forum.xda-developers.com/showthread.php?t=745547
http://www.droidforums.net/forum/droid-hacks/64061-rom-manager-clockwork-recovery-problem.html
ROM Manager can't brick your phone. Unrevoked delivers a permanent recovery mechanism, while updates comes as fakeflashes, which are completely temporary.
Koush! The man himself. I'm honored. No intention of ragging on your good work. I had read a post yesterday regarding what you are are saying now. ROM manager can't mess with the recovery flashed with unrevoked.
I did have that weird problem. Used RM to initiate a rom backup. Then wanted install some extra. Was getting error message in recovery "can't find /cache/update.zip . Also was getting what I think was the old recovery screen with the triangle and exclamation point. Get remember the sequence of what happened when. Finally I used RM to re-flash the clockwork mod and that fixed it.
Then read some scary "brick" posts regarding RM. Made me leery.
Anyway, thanks for checking in on my post. I am now going directly to purchase the premium version of Rom Manager so I can have more fun while sitting around at work!
Best..........mm
Is anyone else having trouble getting TWRP Recovery to work right? I have literally tried everything with both the L720 models I have owned and I get screwed by TWRP every time... I have the L720-T model right now Running 5.0.1 and both a 64GB and 16GB SD Card. TWRP won't write crap to the 64GB Sandisk SD card... and when I use the 16GB Patriot SD Card, I can write a backup to it, but that's about all I can do...
When I reboot into recovery trying to restore from the backup I have created, the stupid thing just sits there for 15-20 minutes trying to verify the MD5. Finally after that 15-20 minute period, the stupid thing crashes and reboots... I really love TWRP and it worked amazing with my Droid Razr Maxx, but now it appears to be a total waste of space and time... What the crap..... Is anyone else having issues or have any guidance?
I have tried multiple TWRP versions...
2.5.0.0
2.7.0.0 (current)
2.8.7.0
Rooted with....
I should also note that I used KingRoot to root [a crazy Japanese rooting .apk because it was the only one that would work as all other filed for the FreedomPop Firmware, and I actually like it a lot bt dubs because it actually blocks auto start stuff 100% unlike most root tools that say they do, only for you to see it running in the Application Manager, it gives no fukks what the process system or not and says no ]
SD Fix as follows...
I downloaded a program to fix the write permissions, but with my 64GB SD It never would write to sd, so I even went so far as to manually change the platform.xml file myself in root->system->etc->Permissions->platform.xml to change "WRITE_EXTERNAL_STORAGE" to contain sdcard_rw, sdcard_r and media_rw as well as change "WRITE_MEDIA_STORAGE" to contain sdcard_rw and media_rw
I can't do a custom ROM, because FreedomPop just doesn't work as good on any rom other than theirs.
If anyone can help me out, I would love you forever, or if someone can point me away from TWRP with something that works and is easy to backup and restore with, then that works also... I am just tired to getting BURNED by TWRP... I Know Titanium is an option, but I would like something that basically backs it up as a snapshot so that there is no setup crap to deal with later, I can just restore on the go and I am good.
mr.ctt said:
Is anyone else having trouble getting TWRP Recovery to work right? I have literally tried everything with both the L720 models I have owned and I get screwed by TWRP every time... I have the L720-T model right now Running 5.0.1 and both a 64GB and 16GB SD Card. TWRP won't write crap to the 64GB Sandisk SD card... and when I use the 16GB Patriot SD Card, I can write a backup to it, but that's about all I can do...
When I reboot into recovery trying to restore from the backup I have created, the stupid thing just sits there for 15-20 minutes trying to verify the MD5. Finally after that 15-20 minute period, the stupid thing crashes and reboots... I really love TWRP and it worked amazing with my Droid Razr Maxx, but now it appears to be a total waste of space and time... What the crap..... Is anyone else having issues or have any guidance?
I have tried multiple TWRP versions...
2.5.0.0
2.7.0.0 (current)
2.8.7.0
Rooted with....
I should also note that I used KingRoot to root [a crazy Japanese rooting .apk because it was the only one that would work as all other filed for the FreedomPop Firmware, and I actually like it a lot bt dubs because it actually blocks auto start stuff 100% unlike most root tools that say they do, only for you to see it running in the Application Manager, it gives no fukks what the process system or not and says no ]
SD Fix as follows...
I downloaded a program to fix the write permissions, but with my 64GB SD It never would write to sd, so I even went so far as to manually change the platform.xml file myself in root->system->etc->Permissions->platform.xml to change "WRITE_EXTERNAL_STORAGE" to contain sdcard_rw, sdcard_r and media_rw as well as change "WRITE_MEDIA_STORAGE" to contain sdcard_rw and media_rw
I can't do a custom ROM, because FreedomPop just doesn't work as good on any rom other than theirs.
If anyone can help me out, I would love you forever, or if someone can point me away from TWRP with something that works and is easy to backup and restore with, then that works also... I am just tired to getting BURNED by TWRP... I Know Titanium is an option, but I would like something that basically backs it up as a snapshot so that there is no setup crap to deal with later, I can just restore on the go and I am good.
Click to expand...
Click to collapse
Do a factory reset get everything back to pre rooted, then root by flashing SuperSU in twrp, instead of Kingroot
mattzeller said:
Do a factory reset get everything back to pre rooted, then root by flashing SuperSU in twrp, instead of Kingroot
Click to expand...
Click to collapse
I really don't want to do that. Twrp, has permissions and I have never had any Root issues with the KingRoot regarding permissions. It always propts me of any and all requests, and also any problems that may arise, so I am extremely impressed with it. This makes me believe that doing this will not help anything. I also had the same issue on my old L720 using towel root and SuperSU. So again, I don't see how this will do anything for me, other than take away 2-3 hours of my life. If you could give me a little more to go off of as to why you think it is KingRoot, I would consider it, or tell me what you think KingROot ins't doing and how to test that, I would. However, without something to support this suggestion, I am lost.
So let me put in a disclaimer that I am a complete novice when it comes to rooting, installing and using custom recovery, and installing custom ROMs, but nothing ventured, nothing gained so I thought I'd give it a go.
I have a Samsung Galaxy S5 SM-G900i running Android Lollipop 5.0, and I absolutely detest the stock OS with all its bloatware. So I was looking into installing the custom PAC ROM for it. After what I presumably thought was enough research into how to perform a root of the device, how to install the custom recovery and finally install the custom ROM, I set off on my journey to begin rooting, it couldn't be that hard right? How wrong I was.
Downloading the latest version of Odin for my particular device, and installing the latest Samsung Drivers was a breeze. I followed the tutorial for rooting the Galaxy S5 , although the UI of Odin differed slightly to what was described. I made my way through it, doubly making sure to not have Re-Partition checked. It installed, or "flashed", if I'm using the term correctly, very quickly. I booted up my device and found the SuperSu app installed. Opening the app, the tutorial says I should have received a prompt to do an update, one which I did not receive. I closed down the app, opened it again, once again no prompt, so I rebooted the device. After several reboots, I googled the issue and found I should try a manual install of SuperSu using the .apk from the ChainFire website. I did as instructed, and the next time SuperSu was opened the update prompt appeared. So I proceeded to follow the steps of the tutorial again, until I was not prompted to disable KNOX. Once again after google searches, I found that this was probably not a big deal, and I could still grant root permissions so I continued on. I've also performed a root check with Root Checker, which has assured me that my device is rooted successfully.
Next I installed TWRP, it went without any relative hitches. But after trying to create a NANDbackup, which everywhere tells me I should do before trying to flash custom ROMs, my microSD card will no longer allow me to write to it from Windows. All attempts result in "Cannot copy item - The device has either stopped responding or been removed", I've formatted the microSD card, I've unmounted and mounted it again. But I can still not write to it via Windows. I'm trying to copy the two .zip files for the PAC ROM and GApps, onto it so I can install from there. But no luck.
I apologise if this post seems long winded, I just wanted as much information in here as possible so that I could get some assistance in fixing my issue, as well as anyone that also has any similar issues can find this as descriptive as possible.
Rooting sm-g900i
Hi thanks for the thread i hope you get your answer, another way is to kind of chat with one of the senior XDA members. i think i'm much more new to this android rooting technology and am hoping to follow in your footsteps (without your current issue). could you pls give a NOOB some sound advise to what i need to do. i would like to go the ODIN way as i want to learn that program, but now there s that "oneclickroot" with the .APK file. which way do you think i should follow. Also what other preperations do i need to take eg NANObackup, remove bootloader(?) etc.
thanks for your time