Hello all. I'm sort of new to this.
Okay, here's the story.
After trying for half a month trying to perm root, I read somewhere that I should do a Nandroid backup first. I then downloaded ROM Manager and installed ClockworkRecovery via the app. Before this, I had temp. rooted my g2 using Visionary + r14 (Perm root wouldn't work no matter how many times I tried).
I pressed the backup rom button, and my screen turned black, then an icon of a phone with a red triangle with a ! point inside of it appeared. I am not sure whether that mean it is still backing up or if I screwed up my phone.
Any advice? Or do I have to reset or something?
You need to root before you can do a full system backup.
blackknightavalon said:
You need to root before you can do a full system backup.
Click to expand...
Click to collapse
Correct. But don't worry; your phone isn't screwed up ATM. just pull the battery and reboot.
Draketh said:
Okay, here's the story.
After trying for half a month trying to perm root, I read somewhere that I should do a Nandroid backup first. I then downloaded ROM Manager and installed ClockworkRecovery via the app. Before this, I had temp. rooted my g2 using Visionary + r14 (Perm root wouldn't work no matter how many times I tried).
I pressed the backup rom button, and my screen turned black, then an icon of a phone with a red triangle with a ! point inside of it appeared. I am not sure whether that mean it is still backing up or if I screwed up my phone.
Click to expand...
Click to collapse
I think your phone hasn't got its recovery flashed properly. After you flash Clockwork, you should really test it by selecting the "Reboot into Recovery" option from ROM Manager. Very often the first time you try that it doesn't work, and you need to flash Clockwork for a second time, and then it works.
It's not backing up, you haven't screwed your phone. Just boot it normally, go into ROM Manager, flash Clockwork again, and test booting into recovery. If that works, then you can do your backup.
There was a known issue with clockwork recovery where if you tried to install it it would give the screen you described. However, upon doing a battery pull, rebooting the phone and installing clockword recovery again usually was a success. Some people said it took them three times, but the majority of users said doing it a second time worked (second time worked for me).
Sent from my T-Mobile G2 using XDA App
Took 2 installs for me. If you still have trouble you can manually install it. Just do a search for manual clockwork recovery.
Sent from my HTC Vision using XDA App
No gold, guys.
Eh... No good on the clockwork backup. Tried the methods: Re-install Rom Manager, clear data cache for rom manager, re-flash recovery, restart phone, went to ymca and worked out, and reboot into recovery (didn't work) then reflashed recovery again. I can't think of anything else to try. Every method results in that dumb phone with the red triangle...
Is this a common problem?
EDIT: Oh, and I got permanent root finally, and tried all of these steps again. Still no success.
UPDATE 2: Uh-oh. I went into hboot (power+volumedown), and it showed that I still have s-on. I've heard that means bad things if you are rooted with s-on still. Is this relevant?
Draketh said:
UPDATE 2: Uh-oh. I went into hboot (power+volumedown), and it showed that I still have s-on. I've heard that means bad things if you are rooted with s-on still. Is this relevant?
Click to expand...
Click to collapse
I think that you'll have to get S-OFF if you want to flash custom recovery.
Its not a bad thing to have s on. You just cant flash any non official update without s off. At this point you i think you will want to follow the gfree instructions for full unlocking. After that you should be good to go. Also did you hit vol-up plus power when you got that triangle?
Sent from my HTC Vision using XDA App
K I looked at gfree
And yes, I have been pressing volume up + power when the trianglE appears. It doesn't make a difference. Isn't gfree the same thing as visionary?
UPDATE: I can't get gfree to work, because my stupid XP computer won't install drivers (tried all ways of getting 'em on, just throws me an error)
I saw a sticky'd post that boasts g2 guide for perm root and s-off individually. It says that I can put the hboot.img in /data/local/, and enter a command line into Terminal, and then command "sync", and it will s-off it. BUT it also says above that by typing the command wrong, or not having the right program could cripple or paperweight my phone. Should I try that?
Draketh said:
And yes, I have been pressing volume up + power when the trianglE appears. It doesn't make a difference. Isn't gfree the same thing as visionary?
UPDATE: I can't get gfree to work, because my stupid XP computer won't install drivers (tried all ways of getting 'em on, just throws me an error)
I saw a sticky'd post that boasts g2 guide for perm root and s-off individually. It says that I can put the hboot.img in /data/local/, and enter a command line into Terminal, and then command "sync", and it will s-off it. BUT it also says above that by typing the command wrong, or not having the right program could cripple or paperweight my phone. Should I try that?
Click to expand...
Click to collapse
No, Visionary isn't the same thing as gfree. Visionary can get you root (both temporary and permanent). As can an alternative called rage.
What gfree gets you is radio S-OFF (so you can flash custom ROMs), plus SuperCID and SIM Unlock.
Don't do the thing with hboot, that's more risky, as it says.
As for the drivers, download and install HTC Sync from HTC's website, that includes USB drivers.
Rage method worked like a charm for me. Visionary was to buggy.
I recommend you use the Rage method and report back.
xomikronx said:
Rage method worked like a charm for me. Visionary was to buggy.
I recommend you use the Rage method and report back.
Click to expand...
Click to collapse
Agreed. I read a lot of bad things about visionary that I rooted just using rage.
I did it using visionary following the tutorials @ theunlockr.com
That site has great tutorial step by step as well as vids to go along with it. Used it for s-off and permroot, as well as loading custom roms.
Sent from my HTC Vision using XDA App
steviewevie said:
No, Visionary isn't the same thing as gfree. Visionary can get you root (both temporary and permanent). As can an alternative called rage.
What gfree gets you is radio S-OFF (so you can flash custom ROMs), plus SuperCID and SIM Unlock.
Don't do the thing with hboot, that's more risky, as it says.
As for the drivers, download and install HTC Sync from HTC's website, that includes USB drivers.
Click to expand...
Click to collapse
UPDATE: Installed Desire Z's HTC Sync, drivers appear to work like a charm. I'll post back later and see if s-off helps nandroid recovery.
Related
Hi I'm new to the mytouch slide family coming from a Motorola Defy and I'm having a hard time going into the recovery mode. Everytime I try get the red triangle warning. I've watched videos, read ROM bible and other post and still no luck. My slide is rooted by VISIOnary Temproot but with root at boot selected. I've been at this for 3 days trying not to bother anyone on the forum for a solution but now I need help!!!! Also I have ROM Manager and loaded Clockwork Recovery through ROM Manager.
Thanks-
Under ROM manager the 2nd option says reboot into recovery. Im pretty sure you tried that right? You can also get to this by turning off the phone and hold the vol down button and press power.
Oops. then select recovery
hoped this helped
htccraze said:
Under ROM manager the 2nd option says reboot into recovery. Im pretty sure you tried that right? You can also get to this by turning off the phone and hold the vol down button and press power.
Oops. then select recovery
hoped this helped
Click to expand...
Click to collapse
Thanks for the quick reply but yes I've done the the power button with the down vol button and once I select recovery I get the same outcome (Red Triangle). I've even selected the boot into recovery from ROM Manager and the same thing happens (Red Triangle).
Sorry i couldn't be of any help. I did a quick search on yahoo and found this. Seems you aren't alone. Maybe you'll find what you need here.
http://www.droidforums.net/forum/droid-hacks/28278-cant-get-into-recovery.html
http://androidforums.com/evo-4g-all-things-root/181591-red-triangle-explanation-mark.html
htccraze said:
Sorry i couldn't be of any help. I did a quick search on yahoo and found this. Seems you aren't alone. Maybe you'll find what you need here.
http://www.droidforums.net/forum/droid-hacks/28278-cant-get-into-recovery.html
http://androidforums.com/evo-4g-all-things-root/181591-red-triangle-explanation-mark.html
Click to expand...
Click to collapse
Thanks I'll take a look.
Still no luck. Someone please help!
Ive never heard of that root method. Are you sure youre rooted? You did say you used a temp root method. Every time you power down youre probably breaking root. First, download an app that needs root, like titanium backup. If it fails to load, you dont have root and that will be why you get a red triangle everytime. I would try rooting using a full proof way listed in the development section. Also, i dont use rom manager but i've heard of issues using that to get recovery.
Sent from my T-Mobile myTouch 3G Slide using XDA App
guitarist5122 said:
Ive never heard of that root method. Are you sure youre rooted? You did say you used a temp root method. Every time you power down youre probably breaking root. First, download an app that needs root, like titanium backup. If it fails to load, you dont have root and that will be why you get a red triangle everytime. I would try rooting using a full proof way listed in the development section. Also, i dont use rom manager but i've heard of issues using that to get recovery.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
VISIONary is used to temp root the G2. With VISIONary you can select to temp root your phone on boot, so that's what I selected.I tried it on my slide and it worked. May I ask what method you use? I will try the full proof way.
Thanks-
I cant give you a link since im not at a computer, but its called " [UTIL] New Root Method as of 8/13! -> UPDATED 12/30 for NOOBS! <- " and its stickied in the development section. I used this the second time i rooted my phone (decided to update with tmobile's ota and it broke my first root).
Sent from my T-Mobile myTouch 3G Slide using XDA App
I think I may have found the solution to my problem but I'm looking for the HTCsync.zip that I cannot find. If somebody know where I could find please let me know.
Thanks-
Htc sync? What would you need that for. As long as you phone is visible to the computer you shouldnt need htc sync. I know i have never used it
Sent from my T-Mobile myTouch 3G Slide using XDA App
at the red triangle screen you push vol up + power I believe -- can't remember exactly and no longer have stock recovery to check with. But it is just another button combination.
HTH
Temp root apps don't root your phone, regardless of boot settings. You need to have the eng build flashed through hboot to be able to get into a recovery that will flash self signed zips such as clockwork. No matter what you do, without fully rooting using a method in the development section, you will not be able to flash clockwork or any custom rom. Temp root only allows you to run root apps inside of android.
Sent from my T-Mobile myTouch 3G Slide
Thanks I finally got it rooted!
guitarist5122 said:
Htc sync? What would you need that for. As long as you phone is visible to the computer you shouldnt need htc sync. I know i have never used it
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
As for that, it's the easiest way of obtaining the ADB drivers for the slide, as the slide is only plug n play as far as mass storage, not its adb interface. I'm sure there are other methods, but installing HTC sync is the easiest.
Need help!!! Recovery
I have succesfully root my girlfriends slide and s-off. but i tried to flash cwm 2.5 thru fastboot and now cannot get into recovery neither factory with triangle or cwm. How do i fix this or will i have to unroot bascially and start over to get the recovery .img again? Also, who can help with permanently flashing cw recovery so that i do not have to use the update.zip method.?
poor2rican1 said:
I have succesfully root my girlfriends slide and s-off. but i tried to flash cwm 2.5 thru fastboot and now cannot get into recovery neither factory with triangle or cwm. How do i fix this or will i have to unroot bascially and start over to get the recovery .img again? Also, who can help with permanently flashing cw recovery so that i do not have to use the update.zip method.?
Click to expand...
Click to collapse
Did you try to fastboot flash the update.zip? That's not good, you should've flashed the cw2.5 .img file. No, you don't have to reroot or res-off, but download the .img file for the latest clockwork recovery on koush's website, for our device. Then, on your computer, while in fastboot mode and plugged into usb, type
fastboot flash recovery filename.img
obviously replacing filename.img with the actual file name/location.
Please help me figure this out...
I also cannot get into recovery mode. Here's my story:
I have a rooted (Supersonic EVT2-2 SHIP S-OFF; HBOOT-0.93.0000) EVO (I know that this is a MyTouch thread, but I couldn't find any similar issues at the EVO thread) that I'm running Warm 2.2 RLS 4 on. I have it set up the way that I wanted and it is running perfect (enough for me).
Yesterday, I caught a glimpse of the MIUI ROM that has an iPhone theme so I wanted to try it out. So, I used Titanium to back up my apps and data to my SD card (8GB with 3GB open). Then, I went to ROM Manager to back up my ROM. I saw that there was an update for the ClockworkMod Recovery so flashed it up to 3.0.0.5. Then I went to Backup Current ROM, kept the suggested name, and hit OK. After a few seconds, the Splash Screen briefly shows, the phone buzzes and then I'm on the initial Bootloader menu screen (with the three Androids at the bottom).
I highlight Bootloader, then I hit the Power button to go to the next set of menus, and the phone does it's checks. After the checks, I push the Volume Down button to go to Recovery, then hit the Power button. The splash screen (white HTC EVO 4G) shows again, the phone buzzes, and I'm back at the initial Bootloader screen.
Whether I use the Quick Boot app, the ROM Manager app, or the Power and Volume Down method, I cannot get past the Bootloader screen to get into Recovery. All I get is Splash, buzz, then the initial Bootloader. Warm 2.2 RLS4 is a nice stable ROM, but I am starting to feel limited, which is why I rooted the phone a few months ago.
Could someone PLEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEZZZZSSSSSSEEEEE help me with this? I am far from a comp engineer, but I can follow instructions pretty well.
Thanks a million!
njgoodfella2199: You're really going to be better off asking in the EVO forums. Good luck!
Yeah, we don't know much about the evo or how it works compared to our gsm phones. The way rom manager updates it may be different. You might be able to use the same solution, find the img file of the latest clockwork and fastboot flash it, but ask on the evo q&a.
Sent from my T-Mobile myTouch 3G Slide
After running the Universal Auto Update v2.4, my phone almost makes it almost all the way. It gets stuck on the screen with the red triangle exclamation mark. On my computer screen, I kept getting the same repeating error messages..."ADB server didn't ACK", "Failed to start daemon" etc, until eventually it gives up. I pulled the battery out to turn the phone off. Turned it on into bootloader and selected recovery. All that does is take me back to the red triangle exclamation mark screen. And also, since the phone was fairly new to me, I went ahead and reset it to factory defaults before I started any of this.
Any help? any other useful information I could give?
Do you have S-ON or S-OFF in bootloader? If you connect phone to a pc does it recognize the device? Do you know how to use adb commands?
The red triangle is you trying to boot into recovery, but no recovery is there. Flash the file I attached, leaving it exactly as it is, no name changing, or extracting, boot into the bootloader, apply update, reboot, reboot into recovery, and you'll be on amon_ra 2.3
Heaterz16 said:
Do you have S-ON or S-OFF in bootloader? If you connect phone to a pc does it recognize the device? Do you know how to use adb commands?
Click to expand...
Click to collapse
It is S-ON. Yes, my computer will recognize the device. And, No, I am not familiar with abd commands.
teh roxxorz said:
The red triangle is you trying to boot into recovery, but no recovery is there. Flash the file I attached, leaving it exactly as it is, no name changing, or extracting, boot into the bootloader, apply update, reboot, reboot into recovery, and you'll be on amon_ra 2.3
Click to expand...
Click to collapse
I didn't think you could flash anything if your phone is not already rooted. Since my phone is not rooted, I'm lost.
golopogas said:
It is S-ON. Yes, my computer will recognize the device. And, No, I am not familiar with abd commands.
I didn't think you could flash anything if your phone is not already rooted. Since my phone is not rooted, I'm lost.
Click to expand...
Click to collapse
If your phone was S off, I'd say you could flash a custom recovery using your bootloader, and you'd be good to go. However, since the autoroot seemed to fail, and you're s on, I don't think you can just flash the recovery...I'm not sure though. If you could get the custom recovery flashed, in theory you could then flash the Unrevoked S-off tool, and you'd be S off with recovery. But I've never tried doing anything like that. If I were you, I'd run the latest RUU, or flash the latest PC36IMG (from here: http://unrevoked.com/rootwiki/doku.php/public/unrevoked3 ). Then once you're back to stock, I personally would run Unrevoked. I've used unrevoked probably a dozen times, and never had a hiccup with it.
Follow these instructions (but don't use the files linked in this post, they're out of date. Use these instructions, but use the files from the actual unrevoked site, as they're up do date) http://forum.xda-developers.com/showthread.php?t=787304
Download Unrevoked 3 from here: http://unrevoked.com/recovery/
Download Hboot drivers here : http://unrevoked.com/rootwiki/doku.php/public/unrevoked3
Sounds like a process, but I think it's your best bet, just flashing back to stock and then starting the process again. Good luck, and let me know if you run into any issues.
EDIT: oops, instead of linking you to RUU's, I somehow copied the wrong URL and sent you to unrevoked. Sorry. Here's the right one.
http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
golopogas said:
I didn't think you could flash anything if your phone is not already rooted. Since my phone is not rooted, I'm lost.
Click to expand...
Click to collapse
Ah, I misunderstood you, but use the links k2buckley sent and you'll be good.
I agree with K2buckley, when auto root's error who knows exactly when and what went wrong in the process. I would RUU as he suggested, here is a link to all RUU's: http://forum.xda-developers.com/showthread.php?t=884060
Select the RUU that matches your phone's SW Version, Radio etc. that you were last running.
Then, I would personally recommend the long method of rooting, that way in case something goes wrong, it is easy to help you along: http://forum.xda-developers.com/showthread.php?t=829045
Heaterz16 said:
I agree with K2buckley, when auto root's error who knows exactly when and what went wrong in the process. I would RUU as he suggested, here is a link to all RUU's: http://forum.xda-developers.com/showthread.php?t=884060
Select the RUU that matches your phone's SW Version, Radio etc. that you were last running.
Then, I would personally recommend the long method of rooting, that way in case something goes wrong, it is easy to help you along: http://forum.xda-developers.com/showthread.php?t=829045
Click to expand...
Click to collapse
I agree that rooting manually, using the 'longer method' is the best way to go, but the OP stated in a previous post that he wasn't familiar with ADB. I would suggest being at least a little familiar with adb, and be somewhat comfortable with it before trying to root a manual way. I guess ya gotta learn somewhere though, why not just dive right on in? I used unrevoked to root first, and then gradually learned ADB, which I use frequently now, and am comfortable with. I always did kind of wish that I learned ADB first, and learned things in the proper order. I learned backwards though.
k2buckley said:
I agree that rooting manually, using the 'longer method' is the best way to go, but the OP stated in a previous post that he wasn't familiar with ADB. I would suggest being at least a little familiar with adb, and be somewhat comfortable with it before trying to root a manual way. I guess ya gotta learn somewhere though, why not just dive right on in? I used unrevoked to root first, and then gradually learned ADB, which I use frequently now, and am comfortable with. I always did kind of wish that I learned ADB first, and learned things in the proper order. I learned backwards though.
Click to expand...
Click to collapse
That's a good point, whichever way he goes is up to him. As long as he figures it out, doesn't really matter to me. I rooted my Hero through adb and had no clue what I was doing which was scary, and then learned adb afterwards along the way like you.
k2buckley said:
I agree that rooting manually, using the 'longer method' is the best way to go, but the OP stated in a previous post that he wasn't familiar with ADB. I would suggest being at least a little familiar with adb, and be somewhat comfortable with it before trying to root a manual way. I guess ya gotta learn somewhere though, why not just dive right on in? I used unrevoked to root first, and then gradually learned ADB, which I use frequently now, and am comfortable with. I always did kind of wish that I learned ADB first, and learned things in the proper order. I learned backwards though.
Click to expand...
Click to collapse
Don't feel bad, I used unrevoked, but that was because I got my evo in november shortly after 2.2 was released and the adb commands wouldn't work. But I feel just as comfortable with adb as the people that used it originally. I originally started using it, but had system errors do the the firmware.
Here's an update. Ran the RUU and it got my phone back to the state it was in before I ran the factory reset, so I made a little progress. I went with the easier method and ran unrevoked. However, I again had an issue with recovery. I got the error msg, "Failed to push recovery. Terminating"
What about this? I read about z4root, which does a temporary root. If I can give it a temp root, and flash with the pc36img, would that get my recovery working? That seems to be the problem. I'd like to hear what you guys think before I try anything else. I feel like the more I do to my phone, the more complicated I'm making the solution.
golopogas said:
Here's an update. Ran the RUU and it got my phone back to the state it was in before I ran the factory reset, so I made a little progress. I went with the easier method and ran unrevoked. However, I again had an issue with recovery. I got the error msg, "Failed to push recovery. Terminating"
What about this? I read about z4root, which does a temporary root. If I can give it a temp root, and flash with the pc36img, would that get my recovery working? That seems to be the problem. I'd like to hear what you guys think before I try anything else. I feel like the more I do to my phone, the more complicated I'm making the solution.
Click to expand...
Click to collapse
hey man glad you got your phone back up and running for one. now as to using z4root to give yourself temp root than flash the PC36IMG.zip, that won't work because as soon as you turn off your phone you lose root. try this method, it takes a little work but you won't have any problems afterward
http://forum.xda-developers.com/showthread.php?t=829045
golopogas said:
Here's an update. Ran the RUU and it got my phone back to the state it was in before I ran the factory reset, so I made a little progress. I went with the easier method and ran unrevoked. However, I again had an issue with recovery. I got the error msg, "Failed to push recovery. Terminating"
What about this? I read about z4root, which does a temporary root. If I can give it a temp root, and flash with the pc36img, would that get my recovery working? That seems to be the problem. I'd like to hear what you guys think before I try anything else. I feel like the more I do to my phone, the more complicated I'm making the solution.
Click to expand...
Click to collapse
After running unrevoked, are you now S on or S off? I've seen a few times where unrevoked succesffully rooted, but failed to push the recovery image to the device. You need to power the phone down, then boot into the bootloader, and see if it says S off. If it does, you're almost done. We can manually flash the recovery image. Again, if you're s off, then download the PC36IMG i attatch. Be sure it's named exactly PC36IMG. Place the file on the main directory of your sd card. Power down the phone. Boot to the bootloader. It will find the PC36IMG, and then ask you to update. Press volume up, to say yes. Once it's done, from the bootloader, select recovery. At that point you should then boot into Amon Ra V2.3. If all that's successful, youll be fully rooted, s off, with a custom recovery.
Now if you check the bootloader, and you're still s on, I would try running Unrevoked a second time, and see if that works. Hope that helps, and again, if you're currently s off, you're almost there, just one more step. Good luck.
Also, when running unrevoked, you need to make 100% sure that there's no programs on your computer that could potentiall talk to your phone. You need to disable your anti virus as well. Some examples would be things like pdanet, htc sync, dropbox, any music syncing/sharing programs you may have. Basically be sure that the only program on your computer that can communicate with your Evo is Unrevoked.
k2buckley, spot on as usual. Also op, a quick way to help resolve issues is if you just restart your pc really quick.
I ran unrevoked a few more times. Still nothing. I decided to uninstall all htc drivers and reboot the pc, and restart the phone again. Ran unrevoked and it finally worked, sorta. Its on S-OFF now, I still need to flash pc36img, but I think I've pretty much got it. Damn I don't what I would have done without you guys. You have all been thanked!
golopogas said:
I ran unrevoked a few more times. Still nothing. I decided to uninstall all htc drivers and reboot the pc, and restart the phone again. Ran unrevoked and it finally worked, sorta. Its on S-OFF now, I still need to flash pc36img, but I think I've pretty much got it. Damn I don't what I would have done without you guys. You have all been thanked!
Click to expand...
Click to collapse
That's good that you're s off now. Flash the pc36img (although unrevoked should push recovery, but that's ok that it didn't, for whatever reason) and you'll be good. That's a better recovery than what unrevoked wouldve provided anyways. Report back, let us know how you make out.
Sent from my PC36100 using XDA App
Hey guys,
I tried to root my my evo 4g with the instructions from the sticky and when I started the autoroot file as it said, it would get to found root then establishing something and the cmd would close out and my phone would stay in the bootloader mode. Instructions said to go to recovery if it didn't continue and I did go into recovery and all it gave me was a black screen with the red triangle and nothing was happening so I pulled out the battery to restart the phone. Now my phone boots up normally and it just freezes up after maybe 30 seconds of use everytime and just reboots and it repeats over and over again nonstop. It won't be recognized by my computers and it just says unidentified with the CDMA drivers not working and the phone does not recognize the SD card when its running and booted up. Please help if you guys know what I could do to make it stop restarting. Thanks in advance!
Try re-rooting via unrevoked. Click on unrevoked in my signature and follow the directions, but first, boot into the bootloader screen (after shutting off the device, simultaneously press the DOWN volume button and the power button until the device starts). Look at the top of the screen and see if it displays "S-OFF". If it does, great, you're rooted, bit if it displays "S-ON" then follow the rooting method of unrevoked or retry the method you used. If it does indeed display "S-OFF", I suggest you flash a custom recovery like amon_RA.
posting & replying via the XDA Premium app.
Well I can't do that since it won't recognize the phone through USB or recognize the SD card
Update: I just flashed my evo with the stock 3.70.651.1 rom using a card reader putting the PC36IM something file on the SD card and used bootloader to flash and It's still not recognizing the SD card and it's still freezing up 1 minute after it has booted up and restarts and repeats the loop.
I sorta have a similar problem. I have a rooted evo running CM7 .
trying to use HDMI cable with a 1080p vizio LCD TV. Nothing happens. Does CM7 support the HDMI video out.
Sent from my PC36100 using XDA Premium App
SprintTouchPro2 said:
Hey guys,
I tried to root my my evo 4g with the instructions from the sticky and when I started the autoroot file as it said, it would get to found root then establishing something and the cmd would close out and my phone would stay in the bootloader mode. Instructions said to go to recovery if it didn't continue and I did go into recovery and all it gave me was a black screen with the red triangle and nothing was happening so I pulled out the battery to restart the phone. Now my phone boots up normally and it just freezes up after maybe 30 seconds of use everytime and just reboots and it repeats over and over again nonstop. It won't be recognized by my computers and it just says unidentified with the CDMA drivers not working and the phone does not recognize the SD card when its running and booted up. Please help if you guys know what I could do to make it stop restarting. Thanks in advance!
Click to expand...
Click to collapse
can you send me the autorootlog.txt file? that should show what happened to it. And def don't try rooting it with anything else while the phone is in an inconsistent state, that is just asking to corrupt it.
Use unrevoked 3 my guide has all you need links and so on
I like unrevoked 3 easy to root and unroot . All the other programs that work for rooting can make unrooting a pain in the butt. Do what you want you want .
You don't have a recovery installed that's why you get black screen and triangles . Use amon 2.3
reaper24 said:
Use unrevoked 3 my guide has all you need links and so on
I like unrevoked 3 easy to root and unroot . All the other programs that work for rooting can make unrooting a pain in the butt. Do what you want you want .
Click to expand...
Click to collapse
how is unrooting different?
xHausx said:
how is unrooting different?
Click to expand...
Click to collapse
I'm not going to war with you on that man just saying turn s off flash a stock Ruu the latest and your good to go. Trying to find a auto or one click unrooting program to unroot can be a pain to do if your h boot is to new or old .
I'm sure your way is good I just prefer unrevoked 3 is all. Not dogging your root way. Just familiar with unrevoked 3 use it to root everyone's phone I know.
reaper24 said:
I'm not going to war with you on that man just saying turn s off flash a stock Ruu the latest and your good to go. Trying to find a auto or one click unrooting program to unroot can be a pain to do if your h boot is to new or old .
I'm sure your way is good I just prefer unrevoked 3 is all. Not dogging your root way. Just familiar with unrevoked 3 use it to root everyone's phone I know.
Click to expand...
Click to collapse
Well you're saying there's a difference in how you have to unroot when it's not true. Or at least that I know of, if there is I'm curious as to how.
Autoroot will try to downgrade the hboot to the unlocked engineering leak, if successful it's finished and all you have to do to unroot is run the RUU. If it's unable to downgrade the hboot it will bring up the stock recovery and use unrevoked forever to unlock the nand; when this is used you have to flash the s-on tool (that is left on the sdcard as URFSOn.zip) and then flash the RUU to unroot.
Unrevoked 3 breaks in through the hboot and unlocks the nand through the radio, so you will also have to use the s-on tool and flash the RUU.
You're also telling him to keep trying to root when his phone is obviously in a weird state, that's bad advice unless you want him to end up bricked like a ton of people did when the latest firmware came out.
xHausx said:
Well you're saying there's a difference in how you have to unroot when it's not true. Or at least that I know of, if there is I'm curious as to how.
Autoroot will try to downgrade the hboot to the unlocked engineering leak, if successful it's finished and all you have to do to unroot is run the RUU. If it's unable to downgrade the hboot it will bring up the stock recovery and use unrevoked forever to unlock the nand; when this is used you have to flash the s-on tool (that is left on the sdcard as URFSOn.zip) and then flash the RUU to unroot.
Unrevoked 3 breaks in through the hboot and unlocks the nand through the radio, so you will also have to use the s-on tool and flash the RUU.
You're also telling him to keep trying to root when his phone is obviously in a weird state, that's bad advice unless you want him to end up bricked like a ton of people did when the latest firmware came out.
Click to expand...
Click to collapse
no I'm not telling him to brick his phone. He doesn't have a recovery on his phone that is what he needs . Just saying if he does end up rerooting at some point he can try unrevoked 3 just a suggestion. My advice isn't bad not new to rooting or flashing. Pretty good at trouble shooting .
Well how do I get a recovery? I thought I have one since I have the option to go there? Gives me a red triangle with a phone under it. Once i mash the volume up and down and power button at the same time and hold it in for a bit a menu pops up to update from SD card or to clear storage and some other options. But anyway I reflashed the stock rom from bootloader and it's still doing the freeze after 30 seconds of use and restarts over and over again. So how do I actually get recovery and what do I do after that to make this stupid restarting of my phone to stop.
SprintTouchPro2 said:
Well how do I get a recovery? I thought I have one since I have the option to go there? Gives me a red triangle with a phone under it. Once i mash the volume up and down and power button at the same time and hold it in for a bit a menu pops up to update from SD card or to clear storage and some other options. But anyway I reflashed the stock rom from bootloader and it's still doing the freeze after 30 seconds of use and restarts over and over again. So how do I actually get recovery and what do I do after that to make this stupid restarting of my phone to stop.
Click to expand...
Click to collapse
I'll need to take a look at your autorootlog.txt file in order to find out what's up with your phone. It should be in the autoroot folder and you can post it by using the 'manage attachments' button, if it doesn't want to let you for some reason you can also email it to me.
edit: odds are you're phone is still locked but it won't hurt to try flashing the recovery, all you have to do to flash it is run the FlashZip script that came with AutoRoot and select the one that says Amon RA - hausmod. That's if it's unlocked of course, if it says s-on or that the security is still on then your phone will reject it.
There you go, there is my autorootlog
I'm not too worried about this as I took the phone to sprint and they ordered me a new phone since they didn't know what was wrong with it and I'll get it today or tomorrow but I just want to figure out what went wrong so that I know what to do if I am to root my new phone..cause this autoroot I used on this website messed up and I followed every step perfectly.
Hello everyone. First of all, sorry if this post is not in the right forum.
My problem is that I rooted my HTC Desire a few months ago using unrevoked3, or at least I think so. I know I tried to do that, but right now I don't remember if I succeeded or I gave up.
The question is, how can I know if my phone is rooted? I have the "superuser permission" icon in my menu but if I run Terminal Emulator and type "su" I get "permission denied".
I know that sounds kind of stupid. I was convinced my phone was rooted but since I am getting the "permission denied" message something must not be working...
Any help?
Thank you in advance.
Boot to recovery. If you have clockworkmod you are rooted
Nothing happens
If I do that, a mobile phone image appears with a "warning" sign besides (an exclamation mark inside a red triangle) and nothing happens. What does that mean?
Thanks.
Easy way to know if you are rooted, is to download an app that requires root and if it works then u are rooted. If not try again
Sent from my HTC Desire using XDA Premium App
Dj Telo said:
If I do that, a mobile phone image appears with a "warning" sign besides (an exclamation mark inside a red triangle) and nothing happens. What does that mean?
Thanks.
Click to expand...
Click to collapse
It seems that you could've lost the root access.
To make sure, download any apps with root prerequisite from the market and see if they work (as suggested).
Do Unrevoked again if you are sure that you have lost the root access.
Note:
I will loose the root access if you flash any official RUU from HTC that si why you should better turn the automatic firmware update off.
Dj Telo said:
If I do that, a mobile phone image appears with a "warning" sign besides (an exclamation mark inside a red triangle) and nothing happens. What does that mean?
Thanks.
Click to expand...
Click to collapse
Yep, you're unrooted
Dj Telo said:
Hello everyone. First of all, sorry if this post is not in the right forum.
My problem is that I rooted my HTC Desire a few months ago using unrevoked3, or at least I think so. I know I tried to do that, but right now I don't remember if I succeeded or I gave up.
The question is, how can I know if my phone is rooted? I have the "superuser permission" icon in my menu but if I run Terminal Emulator and type "su" I get "permission denied".
I know that sounds kind of stupid. I was convinced my phone was rooted but since I am getting the "permission denied" message something must not be working...
Any help?
Thank you in advance.
Click to expand...
Click to collapse
What hardwarerevision does your desire have? You find this out, when you boot into bootloader and read the number behind the word "pvt" (first line). If there stands a 4, you have to run unrevoked with custom recovery (amonra 2.0.1) again. Reason: unrevoked flashes clockworkmod recovery. But this recovery does not work with pvt4- desires. You have to download amonra-recovery:
http://www.android-hilfe.de/attachm...-0-0-14-11-2010-recovery-ra-desire-v2.0.1.zip (link extracted from serious german forum)
Original xda Thread:
[Recovery] [14-Nov-2010] RA-desire-v2.0.0 [GSM] - xda-developers
After downloading and extracting the zip, integrate this recovery into unrevoked (File>custom recovery>choose downloaded amonra recovery) and run unrevoked again:
http://forum.xda-developers.com/showthread.php?t=788044
No warranty for any damage.
MatDrOiD said:
What hardwarerevision does your desire have? You find this out, when you boot into bootloader and read the number behind the word "pvt" (first line). If there stands a 4, you have to run unrevoked with custom recovery (amonra 2.0.1) again. Reason: unrevoked flashes clockworkmod recovery. But this recovery does not work with pvt4- desires. You have to download amonra-recovery:
http://www.android-hilfe.de/attachm...-0-0-14-11-2010-recovery-ra-desire-v2.0.1.zip (link extracted from serious german forum)
Original xda Thread:
[Recovery] [14-Nov-2010] RA-desire-v2.0.0 [GSM] - xda-developers
After downloading and extracting the zip, integrate this recovery into unrevoked (File>custom recovery>choose downloaded amonra recovery) and run unrevoked again:
http://forum.xda-developers.com/showthread.php?t=788044
No warranty for any damage.
Click to expand...
Click to collapse
Hi again.
I downloaded an app from the market with root requisites and it doesn't work, so it means I lost my root access, in case I ever had it. Maybe I lost it when I updated to 2.2 via OTA.
About what MatDroid said, my hardware version is pvt3, so I shouldn't have that problem.
Anyway, I have tried to run unrevoked again and, after the computer makes my phone reboot, unrevoke gets stuck and displays "Waiting for bootloader, make sure the driver is installed". I have been asking google for a possible solution to that but I just haven't succeeded.
I am sure the driver for my phone is installed, as I have been messing around with ADB in the last week to unlock the "move to sd" option in every app and it worked. Or is it a different driver, perhaps?
Thank you for all your replies.
You can check if your driver is installed in two ways:
1.) Start adb and type
Code:
adb devices
Now the serial number of your device should appear
2.) Connect phone in usb debug mode and on "only charge" and "never ask" to your computer, start windows devices manager and check wether there is the device "android 1.0" or "android phone" or something like that.
Maybe install hboot drivers again:
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
And conclusive, do not say thanks, use the thanks button.
MatDrOiD said:
You can check if your driver is installed in two ways:
1.) Start adb and type
Code:
adb devices
Now the serial number of your device should appear
2.) Connect phone in usb debug mode and on "only charge" and "never ask" to your computer, start windows devices manager and check wether there is the device "android 1.0" or "android phone" or something like that.
Maybe install hboot drivers again:
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
And conclusive, do not say thanks, use the thanks button.
Click to expand...
Click to collapse
It appears in the "adv devices" list and in the devices manager, both. Anyway, I am going to try to install the drivers again, because I still get stuck in the "Waiting for bootloader..." screen.
Well... Aftef having tried lots of things during this evening, reinstalling drivers in different computers and running different versions of unrevoked, I finally got it to work.
But...
Here is the thing... Although unrevoked ran correctly untill the "Done" message was shown, I still have "S-ON" in the screen when I turn on the phone with the volume down key pressed. I continuously get "permission denied" messages in adb console as well.
Before unrevoked showed "Done", I had tu run it a couple of times because it got stuck in "Rebooting to recovery" or something like that. Is there a problem with that? I have been asking google about that and I found some people with the same problem, but they re-ran unrevoked as I did and their problem solved.
I feel that I am really close to getting full root access but still need a bit more help... Thank you all!
With unrevoked you do not root your phone. To get full root access you need to be s-off:
http://alpharev.nl/
Is that what I need, for instance, to run the "Ad Free" app from the market? Is that what they mean when they say "you need root access"? Thanks.
Dj Telo said:
Is that what I need, for instance, to run the "Ad Free" app from the market? Is that what they mean when they say "you need root access"? Thanks.
Click to expand...
Click to collapse
No. You can run adfree without to be s-off. If there is written, one needs root excess to run this app, you can run all of these apps (the where it's not needed, anyway). Only if there is written, you need to be s-off, then you need to be s-off. But i only remember one app (a game, so not really important). Conclusion: You have the right access to run apps which need root access.
Well, it happens that I tried to run it but my phone rebooted. It made me think that maybe it was due to some kind of root access issue. I'll ask for a solution in some Ad Free thread.
The app System Tools is not working properly either when I try to perform root required actions. In case it may mean something.
Well, it is finally working now. Seems that this bad dream is over. Thank you!
Sent from my HTC Desire using xda premium app.
Normaly unrevocked root perfectly the phone...
Search market for 'root checker'. Easiest way to check if your rooted or not.
Sent from Soft-Rooted HTC Desire using Tapatalk
Amandroid said:
Normaly unrevocked root perfectly the phone...
Click to expand...
Click to collapse
Normally, you got it mate.
Swyped from my HTC Desire using XDA App
Remember the group of people sometime last year who got into infinite bootloops, with access to bootloader but no recovery?
Yeah. That's me right now. Problem is, I can't remember if we ever found a solution, if anything would work. So I come before y'all for any help
Was running latest CM build before with Tiamat 4.1.0, just shut off during Google Navigation while charging and entered infinite bootloop.
004 Evo
2.18.0001 HBOOT S-OFF
Newest radio, Wimax, PRI, NV
Amon Ra (No access)
It does charge (or says it does - light is on)
So yeah. Access to HBOOT, no access to recovery, still have S-Off. Any help appreciated
tropicalbrit said:
Remember the group of people sometime last year who got into infinite bootloops, with access to bootloader but no recovery?
Yeah. That's me right now. Problem is, I can't remember if we ever found a solution, if anything would work. So I come before y'all for any help
Was running latest CM build before with Tiamat 4.1.0, just shut off during Google Navigation while charging and entered infinite bootloop.
004 Evo
2.18.0001 HBOOT S-OFF
Newest radio, Wimax, PRI, NV
Amon Ra (No access)
It does charge (or says it does - light is on)
So yeah. Access to HBOOT, no access to recovery, still have S-Off. Any help appreciated
Click to expand...
Click to collapse
have you attempted to reflash recovery?
Had this happen the other day and pulled battery and then held power button and volume button down and it went right into Recovery... 1st time ever for me
Just reflashed recovery. Still nothing. Goes into bootloop as I enter recovery.
Note: It does not show boot animation, only splash screen. Just clarifying
Give it some time some times after a crash/hotstart takes a little longer..
Sent from my EVO using XDA App
tropicalbrit said:
Just reflashed recovery. Still nothing. Goes into bootloop as I enter recovery.
Note: It does not show boot animation, only splash screen. Just clarifying
Click to expand...
Click to collapse
Tried a ruu yet?
Sent from my PC36100 using XDA App
evo4gnoob said:
Tried a ruu yet?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Just did. 2.16.0001 HBOOT S-OFF with 2.15.00.0808 radio.
No access to recovery (HTC or custom after flashing recovery)
Same bootloop.
tropicalbrit said:
Just did. 2.16.0001 HBOOT S-OFF with 2.15.00.0808 radio.
No access to recovery (HTC or custom after flashing recovery)
Same bootloop.
Click to expand...
Click to collapse
might need to wait till Captian_Throwback gets online he'll probably know a way to fix it. He fixed his when he got bricked by TWRP
No, there never was a solution, other than the doc I attached, which may not work and again.. someone running CM get's this Boot Loop issue....
evo4gnoob said:
might need to wait till Captian_Throwback gets online he'll probably know a way to fix it. He fixed his when he got bricked by TWRP
Click to expand...
Click to collapse
Nice of you to think of me!
Umm, yeah . . . my problem was a little bit different, as I was still able to boot into a ROM. So, any suggestions I offer here will be purely theoretical. But, perhaps the same fix will apply. Maybe the misc partition needs to be "reset"? Since you have access to fastboot, we'll need you to flash a bootloader version where fastboot commands will work. Since you have a hardware 0004, I think 2.18 is the only option. Get that from here: PC36IMG_HBOOT_2.18.0001.zip (flashable via bootloader). You'll also need to download the "mtd-eng.img" file from toast's thread here: mtd.eng.zip, and you'll need the fastboot.exe from the Android SDK.
After you get the 2.18 HBOOT flashed, select fastboot to get into FASTBOOT USB mode. I assume you already have the fastboot drivers installed on your computer, so I won't get into detail on that.
Put the mtd-eng.img in the folder with fastboot and open a command prompt. Navigate to that folder and issue the commandEDIT: I just tried this and it didn't work. I think you're going to have to go with the above method . It was a good ol' college try, I guess.
Code:
fastboot flash misc mtd-eng.img
It should flash successfully, since you're S-OFF. Once that's done, try rebooting the bootloader, and see if you can get into recovery.
The mtd partition seems to be the thing that messes everything up, so I figure that's the best place to start and see if it's that easy to fix .
EDIT: I guess if the above doesn't work, HipKat's method will be the next thing to try. I don't envy you if you have to try that . . .
Captain_Throwback said:
Since you have a hardware 0004, I think 2.18 is the only option. Get that from here: PC36IMG_HBOOT_2.18.0001.zip (flashable via bootloader). You'll also need to download the "mtd-eng.img" file from toast's thread here: mtd.eng.zip, and you'll need the fastboot.exe from the Android SDK.
After you get the 2.18 HBOOT flashed, select fastboot to get into FASTBOOT USB mode. I assume you already have the fastboot drivers installed on your computer, so I won't get into detail on that.
Click to expand...
Click to collapse
I get the error attached below in attachments, fails to write. I am up to 2.18.0001 HBOOT S-OFF with the HBOOT you included
HipKat, the RUU is downloading. The Evo Softbrick.zip link you have in there leads to me to: "The file link that you requested is not valid."
very simple
reflash by doing adb push update update.zip then format sd
by adb mount/sdcard
then adb erase sdcard
then do fastboot flash update update.zip
erase all data
then should be good to go.....
thats how i fixed mine
HipKat said:
No, there never was a solution, other than the doc I attached, which may not work and again.. someone running CM get's this Boot Loop issue....
Click to expand...
Click to collapse
I just ran the RUU, that is all I've done because of the down link. I'm now at 0.79.0000 HBOOT S-OFF with 1.39.00.0426 radio. Now whenever I turn on my phone it goes straight to bootloader. Entering recovery gives me 5 vibrations with notification light blinking green
Edit: It no longer goes to bootloader whenever I turn it on. It gives me 5 vibrations with blinking green notification light. Still have access to HBOOT
That means it's in maintenance mode. As for that document, it's s few months old.maybe you can do a search for that missing file.
Swyped From The Hippest MIUI'd phone Using XDA Premium
I now have HBOOT 2.10 ENG S-OFF (Hex-edited one from here). So I have fastboot command capabilities. Trying to flash mtd-eng.img gives me the attached error.
Going to start searching for that file. I have fastboot capabilities, so I think I need the nv.img so it's time to go hunting
Edit: So I had HBOOT 2.10 ENG S-OFF. I followed the document HipKat posted, was unable to erase nv, microp, and radio. I flashed nv.img, then I ran the RUU again.
Back to .79 HBOOT S-OFF. Turning the phone on vibrates it 5 times and flashes green light. No access to recovery either.
Starting to think we are out/almost out of options... Guess it is time to start talking about getting S-On with somewhat recent HBOOT and radios.
you don't have to get S-on. If all it does is go to that Maintenance Mode, then just take it to Sprint. They'll probably replace it
HipKat said:
you don't have to get S-on. If all it does is go to that Maintenance Mode, then just take it to Sprint. They'll probably replace it
Click to expand...
Click to collapse
I can still access HBOOT, however. I have a couple of friends at the local Sprint store (due to a Samsung Intercept for my sister - worst phone ever). The problem is, several of the managers there check the HBOOT. They've checked it in front of me (I had S-On) and for recovery on the Intercept. When I asked why they checked, they said they support repairs but not replacements (could go through Asurion) with rooted devices.
Sent from my SPH-M900 using xda premium
Wow, that's the first time I've seen that someone at Sprint checks for Root.
HipKat said:
Wow, that's the first time I've seen that someone at Sprint checks for Root.
Click to expand...
Click to collapse
They do check them. I had mine checked the two times I needed service. Last time they even updated the phone to the latest 4.67 update without consent.
atapia984 said:
They do check them. I had mine checked the two times I needed service. Last time they even updated the phone to the latest 4.67 update without consent.
Click to expand...
Click to collapse
I've seen so many posts about Sprint doing updates without consent. If you ask them to not do the update, they ask questions.
Well, I shall search for a way to get S-On with no access to recovery; I'll continue flashing to see if I can get something to stick before that though. My fallback plan is a Samsung Moment I have sitting around...