Database Users

Can't root, did before though

Ok so I've done a bit of searching and asking on androidforums but nobody can figure out my an answer to my problem. Alright, first off originally the phone had android 1.5 but when sprint released the 2.1 update I did it. From there, I used regaws tutorial on rooting the official 2.1 release which worked great. Basically I was on a mission at this point, a mission to try out all the 2.1 based custom rims. I had been using the rom manager app for its ability to wipe and flash new roms without even rebooting to recovery. As you are probably aware, to do anything with rom manager, you have to have their clockwork mod recovery flashed, which is simple to do with this app. So one day I wiped and flashed a new rom, aloysius I think, and after it was trying to boot the new rom it gave me some error message and the installation failed. I think at this point I tried to restore my nandroid, which also didn't work, I'm guessing that you have to be using the same recovery you were using when you created the nandroid? No matter what I did from recovery I could not restore my nandroid, as a last ditch effort I did a factory wipe and then rebooted. I didn't think it would reboot at all, honestly I was way scared and thought that I had bricked the phone but after about 5 minutes it finished booting up. Now I don't understand why or how, but when it came to it was quite obvious, I was back at stock 2.1. I immediately look in the app tray for the superuser app and obviously it isn't there, I've been dealing with the phone as is for about a month. A couple of weeks ago I decided to get back to work, sat down at the computer and tried to root it again using the same exact method. After like 5 attempts I get the same problem, I get to the step where command prompt spells out "UNREVOKED" really big but I notice that instead of having a "$" like it shows in the picture I have a "#". At this point the guide instructs you to open the Superuser app on the app tray on the phone, sure enough, I don't have one. I have tried this probably like 7 times all with the same result. I've even tried to install that .6 update to patch whatever remnant of root access I have and go from there as I'm sure the fact I was rooted once and lost it has something to do with my failure. I've tried running RUU's many times as well and always wind up getting an error 171 USB connection error. I havent heard of anyone else having an issue like this. I'm not sure whether I posted this thread in the right place to really get help either so if this needs to be moved to development or whatever don't hesitate. I'd really appreciate anyone trying to figure this out as I am tired of running the slow stock rom but have exhausted virtually every option that I am aware of, PLEASE HELP ME!

I know everyone is probably still reading that book I posted, but once you get to the end lol please gimme some advice, i've tried everything and don't wanna live with the phone as is for the next year....

It's a little hard to read your original post, but I'll do my best to help. From the sound of it you may still have root.
I haven't had to root on stock 2.1 install, so I'm not familiar with the new method. If you get to a bash shell or terminal prompt that is a '#' rather than a '$', you still have root.
You said that you did a factory wipe on the phone. Did you RUU or did you simply wipe through recovery? Are you still able to get to the clockwork recovery?
If you can get back to your modded recovery, you're golden. I would STRONGLY recommend you flash the newest Amon_RA. http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1
If you can get that far, you should just be able to wipe and flash a new ROM.

have you tried to update your sync/drivers on your computer lately?
Sent from my Hero CDMA using XDA App

Oh well I finally got it all figured out, had to rum the ruu twice back to back whole the phone was still frozen at the bootloader. From there I finally was able to re root it.

[Q] n00b bricks glacier with Rom Manager

So, disgusted by the bloatware that came with my myTouch, I figured I'd try to get my ducks in a row and root the sucker.
I read that temproot using Visionary is pretty safe, so I did that. It was nice to be able to get into the familiar CLI and do "rm amazonmp3.apk", etc., but of course everything comes back on restart.
So, I thought, before I permroot, I should back up the ROM. I downloaded Rom Manager and clicked the Backup Current Rom button. It downloaded ClockworkMod and the screen went black, and now it shows no signs of life.
Have I killed it good and dead?
Is it possible to fix it at all? I haven't given the SDK a good look yet - is that likely to be my salvation?

lucre said:
So, disgusted by the bloatware that came with my myTouch, I figured I'd try to get my ducks in a row and root the sucker.
I read that temproot using Visionary is pretty safe, so I did that. It was nice to be able to get into the familiar CLI and do "rm amazonmp3.apk", etc., but of course everything comes back on restart.
So, I thought, before I permroot, I should back up the ROM. I downloaded Rom Manager and clicked the Backup Current Rom button. It downloaded ClockworkMod and the screen went black, and now it shows no signs of life.
Have I killed it good and dead?
Is it possible to fix it at all? I haven't given the SDK a good look yet - is that likely to be my salvation?
Click to expand...
Click to collapse
Can you get into hboot? Hold vol down when you start up the phone.
If so grab this image here: http://www.filefactory.com/file/b4f....140e_26.03.02.26_M_release_155771_signed.zip
Rename it PD15IMG.zip, pop it on the SD card root and let hboot restore the stock image/recovery/bootloader
More info: http://forum.xda-developers.com/showthread.php?t=863899

Sdk will probably help but this happened to me also the first time I backed up my first rom. Did you flash cw recovery? If so what I did was a battery pull then power back on holding volume down and pressing power. It then booted into recovery and did the backup properly and everything was fine.
But don't hold me to this could be a fluke.
Sent from my HTC Glacier using XDA App

Also, you need to flash CW at least twice for it to take.

CBConsultation said:
Also, you need to flash CW at least twice for it to take.
Click to expand...
Click to collapse
Not necessarily, it only took once for me.
I think the reason he's having problems is because he flashed the recovery before perm rooting. You're not supposed to attempt a recovery flash while only temp rooted.

lucre said:
So, disgusted by the bloatware that came with my myTouch, I figured I'd try to get my ducks in a row and root the sucker.
I read that temproot using Visionary is pretty safe, so I did that. It was nice to be able to get into the familiar CLI and do "rm amazonmp3.apk", etc., but of course everything comes back on restart.
So, I thought, before I permroot, I should back up the ROM. I downloaded Rom Manager and clicked the Backup Current Rom button. It downloaded ClockworkMod and the screen went black, and now it shows no signs of life.
Have I killed it good and dead?
Is it possible to fix it at all? I haven't given the SDK a good look yet - is that likely to be my salvation?
Click to expand...
Click to collapse
First thing's first. Pull the battery for about a minute. Reinstall it then plug in the phone but don't try to boot. If the orange light comes on that's good. If not you might be in trouble but all hope is not lost yet.
krohnjw said:
Can you get into hboot? Hold vol down when you start up the phone.
If so grab this image here: http://www.filefactory.com/file/b4f....140e_26.03.02.26_M_release_155771_signed.zip
Rename it PD15IMG.zip, pop it on the SD card root and let hboot restore the stock image/recovery/bootloader
More info: http://forum.xda-developers.com/showthread.php?t=863899
Click to expand...
Click to collapse
This is your best bet. Re-image it completely and start over, this time READ THE ENTIRE TUTORIAL BEFORE TOUCHING IT!!
jjjackson56 said:
Sdk will probably help but this happened to me also the first time I backed up my first rom. Did you flash cw recovery? If so what I did was a battery pull then power back on holding volume down and pressing power. It then booted into recovery and did the backup properly and everything was fine.
But don't hold me to this could be a fluke.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
ADB probably won't be much help since he's not perm-rooted; it won't let him do anything. Just re-image the sucker.
CBConsultation said:
Also, you need to flash CW at least twice for it to take.
Click to expand...
Click to collapse
In order to perform a nandroid backup you need:
1. Perm root, NOT temp root, PERM ROOT.
2. S-OFF so you can successfully flash clockwork recovery.
Not trying to be harsh just want to be perfectly clear.
TeeJay3800 said:
Not necessarily, it only took once for me.
I think the reason he's having problems is because he flashed the recovery before perm rooting. You're not supposed to attempt a recovery flash while only temp rooted.
Click to expand...
Click to collapse
Yup.

Possible Brick I Dunno what I did

So I'm fairly new to rooting but I have had android since the day it came out and I am good with the system. I have a g2 running a root of Visionary. I wanted to install a custom rom, so i was in Rom manager and i flashed in Clockwork Recovery, that went fine, and then i clicked back up current rom. I changed the name to original Rom, then the phone went blank then it had a g2 with a red triangle with an exclamation point in it. Does that mean the phone was bricked or what mode was that in? I pulled the battery and powered the phone on while holding the volume down. I think clicked the recovery option and the phone produced the same black screen with a G2 with a red triangle with an exclamation point in it. I then pulled the battery again, powered it up with the volume down button and did a factory reset and now my phone is back to how it was out the box running regular software.
Any idea what I did wrong? Or what went wrong? I would like to throw visionary back on and do a temp root and throw in a custom rom. My end goal is to do it once and have the phone run flawlessly and fast and never mess with any settings again. Help please!

Just for your information use the root method in wiki thats on this forum its easy. I think the visionary is outdated.
Sent from my HTC Vision using XDA App.

jjp023 said:
red triangle with an exclamation point in it.
Click to expand...
Click to collapse
The red triangle is the pre-screen to the stock recovery. At that screen if you press Vol + and Power (IIRC), it will take you to the recovery. I am not sure why you got this screen if you flashed clockwork recovery from ROM manager.
If the phone is not properly rooted, it probably cannot flash a custom recovery. Make sure you follow the instructions for rooting via Gfree in the wiki.

you are just soft rooted you will need to go through the root through adb

jjp023 said:
So I'm fairly new to rooting but I have had android since the day it came out and I am good with the system. I have a g2 running a root of Visionary. I wanted to install a custom rom, so i was in Rom manager and i flashed in Clockwork Recovery, that went fine, and then i clicked back up current rom. I changed the name to original Rom, then the phone went blank then it had a g2 with a red triangle with an exclamation point in it. Does that mean the phone was bricked or what mode was that in? I pulled the battery and powered the phone on while holding the volume down. I think clicked the recovery option and the phone produced the same black screen with a G2 with a red triangle with an exclamation point in it. I then pulled the battery again, powered it up with the volume down button and did a factory reset and now my phone is back to how it was out the box running regular software.
Any idea what I did wrong? Or what went wrong? I would like to throw visionary back on and do a temp root and throw in a custom rom. My end goal is to do it once and have the phone run flawlessly and fast and never mess with any settings again. Help please!
Click to expand...
Click to collapse
You can't load a custom recovery with only temp root (I'm guessing that's all you had). What you saw was the stock recovery (so your phone was actually fine and you didn't have to factory reset). If you want to load a custom ROM, you will need to follow one of the permanent root guides first (use the wiki or I just wrote another guide if you can't get ADB working). If you did have permanent root (check for S-OFF in the bootloader), try flashing the ClockworkMod recovery again (sometimes it doesn't take the first time).

ianmcquinn said:
You can't load a custom recovery with only temp root (I'm guessing that's all you had). What you saw was the stock recovery (so your phone was actually fine and you didn't have to factory reset). If you want to load a custom ROM, you will need to follow one of the permanent root guides first (use the wiki or I just wrote another guide if you can't get ADB working). If you did have permanent root (check for S-OFF in the bootloader), try flashing the ClockworkMod recovery again (sometimes it doesn't take the first time).
Click to expand...
Click to collapse
Sent from my T-Mobile G2 using XDA App
Thanks for the help, I appreciate the quick responses. I hade visionary. I temp rooted it and then perm rooted by jus clicking the perm root on visionary. Not sure if that would do the same. I dnt think I have the confidence yet to perm room through terminal and writing scripts. what way would u suggest to perm room and What roms would u suggest that are relativly novice leve and provide signifcant improvement

jjp023 said:
Sent from my T-Mobile G2 using XDA App
Thanks for the help, I appreciate the quick responses. I hade visionary. I temp rooted it and then perm rooted by jus clicking the perm root on visionary. Not sure if that would do the same. I dnt think I have the confidence yet to perm room through terminal and writing scripts. what way would u suggest to perm room and What roms would u suggest that are relativly novice leve and provide signifcant improvement
Click to expand...
Click to collapse
Not positive how Visionary attempts to permroot, but you should check to see if you have it. Hold the volume down while powering on to enter the bootloader. The first line will say S-OFF if you have root and S-ON if you don't. If you have S-OFF, go ahead and try to flash the ClockworkMod recovery again (it just may not have worked that first time). If you have S-ON, or still have problems flashing the recovery, you can use either of the guides I linked to in the earlier post (you don't have to write scripts, but will need to use terminal---just follow the instructions carefully and watch for typos).
As far as ROMs, once rooted, you can try any of them really easily to see what you like best (be sure to make a backup first and you can always revert back). They are all pretty friendly to use right out of the box.

My phone is back to stock so I can't check lol. The link you posted titled guide seems pretty user friendly. I will attempt that root tnite... I will not do the h boot bc I dnt want more risk of a brick. Once I root I will flash clockworkrecovery. So in rom manager i should flash clockworkrecovery then scroll down to the bottom of it and backup current rom.how can I confirm its backed up? And once it is backed up I am clear to install new roms correct
Sent from my T-Mobile G2 using XDA App

If you were already S-OFF, doing the factory reset shouldn't return you to S-ON, so you could still check if you wanted to.
As far as backing up goes, once you choose backup in ROM Manager, your phone will boot into the custom recovery and you'll actually see all of the files getting backed up (there's also a progress bar). The backups are stored on your SD card in the clockworkmod directory (if you want to check to make sure it's there). After you have the backup, you're free to start testing new ROMs.

ianmcquinn said:
If you were already S-OFF, doing the factory reset shouldn't return you to S-ON, so you could still check if you wanted to.
As far as backing up goes, once you choose backup in ROM Manager, your phone will boot into the custom recovery and you'll actually see all of the files getting backed up (there's also a progress bar). The backups are stored on your SD card in the clockworkmod directory (if you want to check to make sure it's there). After you have the backup, you're free to start testing new ROMs.
Click to expand...
Click to collapse
So jus confirmed s on... so I will root using the guide u provided tnite.. few more questions jus to be safe I dnt wanna be a annoying but I appreciate the help...
1. Once rooted and in rom manager I should first flash clockworkrecovery then click back up current rom?
2.if I get back to the g2 with red triangle screen I should clikc power and volume down and which option should I choose at that screen?
Sent from my T-Mobile G2 using XDA App

jjp023 said:
1. Once rooted and in rom manager I should first flash clockworkrecovery then click back up current rom?
Click to expand...
Click to collapse
Yup.
jjp023 said:
2.if I get back to the g2 with red triangle screen I should clikc power and volume down and which option should I choose at that screen?
Click to expand...
Click to collapse
This just means the ClockworkMod recovery did not flash properly (and you are seeing the stock recovery). Just boot the phone normally and try flashing the recovery again in ROM Manager. If that doesn't work, there are other options we can try, but it should work fine once you are actually permrooted.

Sounds good. I'm trying to prepare myself to do this root later tnite.
I want to make sure I get the command right in terminal.
After the money sign and number signs there are spaces correct?
So my keystrokes shoule be (I dnt press $ or #)
$(space)su(enter)
#(space)cp(space)/sdcard/root_files/perm_root/data/local/perm_root(enter)
#(space)chmod(space)777(space)/data/local/*(enter)
#(space)/data/local/perm_root(enter)
Sent from my T-Mobile G2 using XDA App

You don't need to type the space at the start of the commands (they will already be there). Also you are missing a space in the second line:
cp(space)/sdcard/root_files/perm_root(space)/data/local/perm_root(enter)
Otherwise, looks good.

I know exactly what you're talking about with the triangle and red exclamation mark. Happened to me when i first flashed clockwork mod (CWM). What fixed it for me was to flash it TWICE when using Rom Manager. The first time you try to flash it, it doesn't always work, so you just reboot as normal (not into recovery) and flash CWM again and it should fix it.
Sent from my HTC Vision using XDA App

[Q] Nandroid Backup Issue

I seem to have encountered a rather unusual issue with my nandroid back up. I was planning on flashing CM7 to test it out, and then after my test return to my backup. CM7 worked like a charm, but I was going to wait until I had more time on my hands to fully explore the rom, so I decided to do a nandroid restore using Clockwork Mod 3.0.2.4. It worked... sort of. After the restore, I rebooted. It brought me to my normal unlock screen, but when I unlocked it, I was presented with the MT4G initial setup, as if I had done a restore with the stock img. I knew my data is still in there, because it remembered little things, like my initial lock screen, my wifi settings and a couple of other things. I went hunting through a couple of forums, and found that the MT4G has issues when using clockwork 3.0.2.4 to flash non-Gingerbread, and that you ought to use clockwork 2.5.1.2. Thinking that may have been my problem, I tried, and it then told me there was a MD5 mismatch. I followed the recommendations found in this post http://forum.xda-developers.com/showthread.php?t=976453 for finding and correcting mismatched MD5s (the data.img file was the one with the mismatch if that helps). Now it flashed properly, but resulted in the same problem I had earlier... after reboot, I am presented with my lock screen, but then taken through the MT4G setup. I have a TI backup, so I'm not really worried, but, I am curious if anyone can shed some light on what happened to my restore so that it doesn't happen in the future, and so that if someone else has this problem, they can have it a little easier than I have.
Thanks in advance for your help,
WestBC

Any thoughts!

Basically, stick with froyo or GB. Don't jump back and fourth.

[Q] Phone Boot problem, won't mound SD

Sorry about the post as this may not be the best place for it.
My phone got low on memory so was trying to clear stuff, it rebooted then on the loading screen (Myn RLS 5) perpetually restarted. So went into recovery
and tried to do a backup (so could format as my last backup was old) and it threw an error in mid -backup (did write it down, doh!!)
Now the phone does the 5 vibration thing and does boot. Also SD won't mount get " /dev/block/mmcblk0p1" error. Also I now notice the phone reset to "S-on" I had a long time ago rooted with unRevoked Forever.
I have read several posts about this , but confused on the best way (instructions) to get a img file on and reinstalled. I have used adb before but only basically , unfortunately my computer at work doesn't have adb installed so cannot test things now.
So if anyone has a good one or two methods for me to try tonight, would be much appreciated. Also totally surprised that security went to "on" so probably have to address that first.
Oh phone is EVO, HBOOT 0.93 , Radio 2.15.00.05.02 . If I should post this somewhere please feel free to direct me there.
EDIT: I have ClockworkMod Recovery 2.6.01 installed and can get into it.
Thanks so much.
Kevin

First I woud try the sd card fix found here:http://forum.xda-developers.com/showthread.php?t=695243&highlight=sd+card+won't+mount Then I would downgrade your radio to 2.15.00.11.19 using a flashable pc36.img file.All radio versions can be found in the development section.If the first 2 steps are successful,run a 3.70 ruu(can also be found in development).If that is successful,reroot using unrevoked forever and you should be good to go.I' not sure if the radio downgrade will work with s-on,but I think if you use the flashable pc36.img version it will go thru,if it doesn't,you can still try the 3.70 ruu.I ran into some incompatability issues with trying to run the 2.15.00.5.02 radio with older software and hboot versions.

@BrianBusby2038,
Thanks for the post, good information I will give it a try. Interestingly the phone did eventually boot into Myn for a few minutes before the 5 vibrations of death started again.
So looked and it def. doesn't see the SD. So hopefully can recover.
I am wondering if the AData SD card I have is not reliable. Thankfully have the original 8GB card so hopefully can get things going again.
Anybody have a good recommendation for a 16GB microSD that is fast (buying from Newegg) ?
thanks again

No problem,hope it works out ok.
Sent from my PC36100 using XDA App

I had this same problem a few days ago and I had to get a replacement ordered (a 2.3 preloaded replacement ). Make sure that your USB is still working, because both my SD card and USB stopped working, S-ON went on, and the five vibrations/green light shut down problem happened. I was able to get S-Card operational, but USB was no go. I could not log in as super user and could not enter the commands necessary to fix usb. No USB = No root = no fix for USB. Now I'm stuck with a 2.3 evo, at least its shiny and new .
Hope you fix yours, I wonder how this problem has happened to so many of us randomly. PS: when you take it to sprint store, don't complicate matters and revert to stock.

Crude, fastboot on PC throwing driver error, how do I tell if the right driver is installed.
This is really sucking, Ive only ever installed one driver and could connect with adb.
So not sure what to do.
EDIT: says can't start because AdbWinApi.dll is missing

@robertsaurus,
not sure how I could go to stock if I cant re-image. Yeah definitely don't want to make a fuss, ugh

I lost clockwork mod and ended up only being able to access default Android recovery menu. I think an option on there will restore the factory Rom and make it look like it was never rooted. I know people have been able to fix theirs but I gave up after a days worth of trying
Sent from my PC36100 using XDA App

Well I had partial success. I restored a signed Sprint Rom, but phone keeps rebooting and USB doesn't work. the 5 vibrations seemed to have gone away. Though since I can get usb to work I can't do a RUU install and remove clockwork.
I did talk to Sprint and they are willing to early upgrade me and buy the EVO back for 125 so long as it boots and it does .
So going to give that a whirl , I have 30 days so may give a few other things on the evo a try before I return. Doing the upgrade I just lose out on some of the rooting so we'll see how that impacts me.

I had the exact issue. I think if you do a wipe from the boot menu (power and vol down) it will get rid of it all. And then take it to sprint and play dumb . Worked for me, new shiny evo lol
Sent from my PC36100 using XDA App

yeah I played dumb, but since it was out of warranty 1month and 10 days. they wouldn't replace . But at least get upgrade and buy back on the EVO which is not bad.
Though I am over the next couple of days try and get the EVO rescued, so long its still bootable I can take advantage of the buyback

yeah I played dumb, but since it was out of warranty 1month and 10 days. they wouldn't replace . But at least get upgrade and buy back on the EVO which is not bad.
Though I am over the next couple of days try and get the EVO rescued, so long its still bootable I can take advantage of the buyback

That sucks, hope it works out for you
Sent from my PC36100 using XDA App

robertsaurus said:
That sucks, hope it works out for you
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Interestingly I could get the 5 vibrations thing to go away if I applied unrevoked forever s-on. the phone will still reboot and usb not functioning yet. Going to try and get a shell script running to fix usb , or try and do a re-rooting via the auto root, maybe hboot usb will work (fastboot did)
I did get the photon (we'll see how it works, though miss my rooting and evo)
so if like hopefully they will unlock the bootloader.