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
Related
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.
I'm currently stuck in a boot loop, with no way to access my rom or recovery. I can only access bootloader. The boot loop began happening soon (around 2hrs) after flashing MIUI; The rom was running, and out of nowhere it just began cycling. Any ideas on how I can get out of this boot loop?
Edit: I'm no longer in a boot loop after installing a different full system PC36IMG.zip. Instead after the initial splash screen my evo goes black and vibrates 5 times, then my green LED starts flashing. It stays this way until I remove the battery.
So far I have tried:
Flashing RA's recovery image using fastboot. (The flash was successful)
Using RA's recovery PC36IMG.zip. (The installation was successful)
Using an RUU file renamed to PC36IMG.zip (The installation was successful)
Using a Sprint Lover's file renamed to PC36IMG.zip (The installation was successful)
For all of these the process of installing and flashing went fine. Yet when I would turn on my phone it would just go right back into the boot loop.
*I've been editing this post as I've tried new things, so you don't need to read through the thread to help me.
Anyways I'm at my wits end here, pretty worried, and phoneless, so any help would be amazing.
Have you tried ADB from bootlaoder or fastboot. May be able to get recovery that way.
I'm trying to do a bit of research, but am a little confused on what adb is. It's part of the android sdk? I can't seem to find it, or know how to launch it. Is there a thread somewhere that covers it? I'll keep doing my research, thanks for the tip.
Its a command terminal but if you are not familiar with it you probably wont get it right away! I am just starting to learn this myself. VERY VERY useful tool though! Here a link.......
http://forum.xda-developers.com/showthread.php?t=502010
I really appreciate you trying to help out. I'm trying to figure it out right now, but how do i get to the terminal? Theres a couple of different guides I see, but none seem to be while in bootloader. The thread you showed me seems to be mostly commands. Sorry for the hassle, I really appreciate you helping me. I wouldn't be quite so pestering if I wasn't without a phone, haha.
ahhh, also, if adb is an exe that opens up in cmd.exe (which i'm starting to think), its not included in my sdk.
edit 2: haha, ok i just found out i have to install adb through sdk, from a little txt file. sorry. i'll get back to ya soon!
thanamesjames said:
I really appreciate you trying to help out. I'm trying to figure it out right now, but how do i get to the terminal? Theres a couple of different guides I see, but none seem to be while in bootloader. The thread you showed me seems to be mostly commands. Sorry for the hassle, I really appreciate you helping me. I wouldn't be quite so pestering if I wasn't without a phone, haha.
ahhh, also, if adb is an exe that opens up in cmd.exe (which i'm starting to think), its not included in my sdk.
edit 2: haha, ok i just found out i have to install adb through sdk, from a little txt file. sorry. i'll get back to ya soon!
Click to expand...
Click to collapse
Jeez sounds like you have a better grasp on this than me already! LMAO
haha, well i'm not too sure. Have you gotten you're evo to be found? Right now while using adb, I'm just told "device not found." All my drivers should be properly installed because I had to install them when I used unrevoked. So I choose fastboot on my evo, and then it shows up on my computer as "android 1.0" under devices and printers... but adb doesn't find it.
I was told to get rid of my drivers and re install the recommended ones before starting. It recognized mine right away. YouTube also has nice how to videos on ADB.
Is there any way you can point me to the recommended drivers? I think that second link you gave me is the same as the first also.
Edit: Every single guide I see on the internet about adb, says use debug mode within the actual rom. However I'm obviously not in a rom, i'm in bootloader, and for the life of me can't get adb to find my phone.
Edit2: Ok, so maybe I can only use fastboot. Right now when trying fastboot it just says "waiting for device," even if it didn't say that, what would i need to do to get on the road to recovery?
So I'm starting to get scared. At first I figured this was something I could fix... and now I'm not positive it is. I've used fastboot from terminal, trying to flash recovery and it says "FAILED (remote: not allowed)" I'm starting to get desperate, does anyone have any ideas?
I'm sorry to bump this, but I'm really struggling here... because I'm phoneless and all , I worked at this for 5 hours last night from 9-2, and now I'm at it again... and very worried. I've read that theres almost no way to completely brick your phone, but I'm starting to feel like I did. It seems like no matter what I flash it just keeps boot cycling. Thanks for the help.
go to the bootloader and ruu it
I have... I took the ruu file and renamed it PC36IMG.zip, went into bootloader and it went through all the steps with "OK"s, rebooted, and went right back into the boot loop.
Specifically I used "RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip" from here,
http://goo-inside.me/evo/stock/RUU/
Is there a specific number version of RUU I should try? I just tried the most recent.
You have to use the ruu that matches your radios/software etc. How did this boot loop start? Give us all your phone info, rom, hboot version, radios etc.
Sent from my iphone slayer 4G
I flashed a CM7 nightly, from CM, about 2 weeks ago. Yesterday, still using the same nightly (build 1 or something) my phone seemingly out of nowhere rebooted - I wasn't even using it at the time. When it went back into CM7 it acted as if I had never linked a google account to my phone. The first thing that came up was the android google apps screen. Anyways, I decided I wouldn't stick with CM7 until at least an RC was out, so I wiped data, cache, and davlik and flashed MIUI. I used it for about two hours, didn't do anything out of the ordinary, and once again seemingly out of nowhere it rebooted... except when it did it went into a cycle and never reached MIUI, and wouldn't go into recovery, I could only access bootloader.
Anyways, I'll tell you what bootloader says my phone versions are, but I do believe the info all changed this morning when I flashed the ruu file.
SUPERSONIC EVT2-3 SHIP S-off
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00
Check your pm
Sent from my iphone slayer 4G
Are there any other thoughts on how to get on my feet?
In addition to booting an RUU file as PCIMG36 I've also tried a Sprint Lover's image as PCIMG36. Even though both installed properly, my phone still staid in the boot cycle afterwards for both.
I've been suggested, and have seen other users suggest on other threads, to try adb commands, but I don't know if i can access adb while the phone is in bootloader. I have however accessed fastboot, are there any commands that might help me? If not, can I use adb while in bootloader? Thanks.
Well I tried a new PC36IMG.zip file and I'm no longer stuck in a boot loop... instead as soon as the HTC EVO 4G splash disappears my phone goes black and vibrates 5 times, and my green LED flashes.
Good? Bad?
This would be the 300th something thread I've read on this subject and this is exactly were I'm at with my EVO minus the last post... I was using warms2p2 with the hdmi kernal everything working fine then I went to change my notification ringtone and bam went into boot loop and never came out. SOOO! it would be nice to save this unit... any help forum members would be great I've tried every RUU out there from fastboot from sd card nothing.
Very intesting that this thread ended this way... please share if you think you got this whooped. Thank you in advanced.
Love the revival of old threads...but did you try changing the kernel?
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip 3.70 RUU, just rename to PC36IMG and flash in the bootloader if you want to run the RUU.
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
jenic said:
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
Click to expand...
Click to collapse
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
RMarkwald said:
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
Click to expand...
Click to collapse
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
jenic said:
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
Click to expand...
Click to collapse
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Your concise post is most appreciated. I will do as you instruct and post results back here when finished.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Hit an unfortunate snag right away. fastboot (nor adb) is detecting the device. Screen is showing XC SHIP S-OFF as it should, it is in FASTBOOT USB mode and my computer detects the USB itself just fine.
dmesg output:
[346853.772041] usb 2-6: new high speed USB device using ehci_hcd and address 17
[346853.922917] usb 2-6: configuration #1 chosen from 1 choice
Click to expand...
Click to collapse
Thank you though that was a great suggestion! (Was very hopeful for a second there
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
RMarkwald said:
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
Click to expand...
Click to collapse
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
RMarkwald said:
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
Click to expand...
Click to collapse
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
cf9182 said:
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
Click to expand...
Click to collapse
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
jenic said:
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
Click to expand...
Click to collapse
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
jaba14 said:
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
Click to expand...
Click to collapse
That was definitely a laugh. Thank you I will see if I can get it replaced! I've been kinda just ignoring the fact that I do not have a phone all this time... Thankfully I had setup the phone to forward calls to google voice. It has been a lifesaver.
I thought I had it all figured. Root, with Clockwork Recovery, Rom Manager. Nothing could go wrong. Now I am stuck at the splash screen with no Clockwork Recovery.
I searched fourum after forum to find a solution, but mine seems to be different. Just so you know I am 21, and a freelance computer technician so I am not afraid of the command line
What have I done to my device:
=Originally it had 2.1
=I rooted the phone via exploid method
=I installed CyanogenMod 6.1.1
+My computer only recognized my phone in HBoot mode, I think usb debugging is turned off though because I cannot acces my sd while it is in my phone.
I do have a microsd card reader
+I tried Esprimg.zip updates. It works .but I still cannot get into recovery mode.
For extra precaution, I backed up all of my sd card data on my pc.
Symptoms and problems:
+I am stuck at the white My tough slide 3g splash screen.
Holding up and power for at least 30 seconds does not get me in recovery mode. All I see is the white My tough slide 3g splash screen. No Black screen with a triangle(Biggest Problem)
+Holding down and power does get me into the HBoot.
+The recovery option will make the Mytouch slide reboot, but it will freeze at the splash screen.
+The clear storage option executed, but it did not solve my problems.
+I have also removed the battery, sim, and sd card.
Summuaray-
I need to get Into Recovery mode, but when I press up and power it does not work. I only see a white.I never though there would be a day where I could not get into recovery.
Also, I constantly charge the device so it wont turn off during an update.
Do you have S-OFF? If you do it should not be hard to recover.
If you don't I can't think of any other method now. But just to make sure which Esprimg.zip method did you tried? Because that should work in the first place.
Mine says S-On
Esprimg.zip
I used my microsd card reader to put esprimg.zip on the sd card. Boot the device while holding down and power. I let the phone check for the esprimg.zip and then the update was successful.
Conclusion:
I hold up and power and i cannot access recovery mode.
Possible causes:
By doing the clear storage, would that change my device to s-on. Honestly I never noticed s-on until now. However, I was able to root and get clockword mod 6.1.1 and it ran smoothly for a weeks.
darko4 said:
By doing the clear storage, would that change my device to s-on.
Click to expand...
Click to collapse
No. Only by flashing another bootloader will you get S-ON back. You probably did not have S-OFF before anyways but FYI Esprimg.zip does flash the bootloader so you're stuck on S-ON for now.
If the Esprimg.zip update method was successful it should have flashed back the stock recovery for you. I can't think of anything that could go wrong at this point except that u have a bad or corrupted Esprimg.zip. Did you use the champion build or the ENG build? If me I'd try to download it again and give it another go.
Good luck!
Ok so Esprimg.zip may be bad, and pretty much that is my only saviour;ok I understand.
I was using Esprimg.zip from other guides. Those were 137 mb
This time I used the one from here.
HOW-TO * Flash the Eng-Release to the Slide *6/15/2010
http://forum.xda-developers.com/showthread.php?t=703076
I am going to assume this the the eng build. It was 137.1 mb.
If this does not work the I guess I have to go champion build.
------------------------------------------------------------------
Failed
Champion build esprimg.zip is next.
A few more ideas.
manually install the recovery using fastboot.
troubleshooting without simcard?
My spl s-on so would that be possible?
Is there a way to maybe re root?
I read in one post that a guy sold it on ebay..i would hate to do that with just a month of ownership. would Htc make a warranty request even though I bought it used. Besides you only see bootloader and hboot spl s-on so how could they tell?
So you reach the screen where it asked you whether you want to install the update, you choose "yes" and it goes on to flash everything, radio, bootloader, yada yada, and it fails to boot?
Basically with S-OFF you can boot into fastboot and run
fastboot flash recovery recovery.img
in this case recovery img is CWM recovery. With S-ON fastboot flash is disable so it's not possible.
EDIT: If you do have the champion build on it's basically stock.
I have this exact same issue right now, I've tried the champion and engineering builds of ESPRIMG but with no success. I can't think of anything else that would be causing this in the first place, which is making it so difficult to troubleshoot. The only difference is that I was using CM7 instead of 6, but the exact same thing is going on. I have tried everything that the OP has with no luck. The only possible cause I can think of is that something was somehow corrupted while the phone was on and sitting on my table...because when I picked it back up, it was off and when I tried to boot, I got splash screen... Any other ideas?? I'm all out and just sitting here waiting for some genius light bulb to go off....attic's kinda dusty though..
With S-ON fastboot flash is disable so it's not possible.
So basically these are my options
esprimg.zip (if that does not work then use different)
Hboot clear memory,
with S-ON I have limited option
and keep it charged.
Although with fastboot and s-on is there something I could do?
Would rerooting be an option
darko4 said:
Would rerooting be an option
Click to expand...
Click to collapse
I don't see a root method in the forum that does not involve booting into a usable system.
Wait, you guys were able to flash the esprimg.zip right? Because in the guide when it says it requires root it's for flashing the mtd0.img first before rebooting into HBoot. Since you don't have a working system you cannot do that and if HBoot refuse to take your esprimg.zip then you need to do the Goldcard method. Otherwise I don't see why having root will make a difference.
So at this stage of the game I should do this..
1.get on my knees
2.put my hands together.
3.and just pray?
ok all jokes aside. Continue to try Esprimg.zip and update(all are successful but I still get splash)
I can't change my recovery since I have s-on
and no way of getting s off since i cant get in the phone, not even recovery,just h boot
So in a sense i have a lovely soft bricked mytouch 3g slide.
Later I might compose a list of the programs i had on the device, but i doubt that would make a difference. I appreciate the help and assistance, I am going to click the thank button for you gents.
In the mean while i got a tmobile comet for 136 one day shipping..No rooting on this one cause finals are coming and I do not have time to troubleshoot for hours. I love android cause of custom roms, but not being able to get in recovery mode...ah say no more. I am going to be one of those people who just downloads free software and complain to phone carriers about OTA.
Same here. I held off rooting and all until my exams were over because I know I'm going to go all the way until I get S-OFF.
I know many discourage S-OFF because it can potentially brick during the process but if you do read up and follow instructions very carefully it is really not that risky. And it'll be very useful in situations like this.
I'm sorry to hear you have a soft-brick. Maybe a dev will stumble upon and provides new insights but I afraid this is all we have in the forum for now.
to be honest i skimmed through the post, and im sure you did try this but just want to ask have you tried the official RUU update to see if you can get things back up running that way?
yeah I understand following directions carefully, but when you follow all of directions and get it working,and make backups, but then you turn the phone off and then turn it on. Then all of this happens.
ah let me stop my whining and download more esprimg.zip .
I just want to know what caused it. was it an application, cause if that is the case then I want to know so no one else get hurt.
(one interesting note, avg antivirus said my device was infected with viruses. It said with the apps, I did not clean it. i uninstalled avg. I presumed it was a false alarm cause the phone is rooted with applications with high privileged) Oh well
---------------------------------------------------------------------------------------------------------------------------------------------------
oh well. back to the esprimg.zip
never tried RUU, if it comes in a esprimg.zip then i guess i can try. if not then i do not know how to use it with mine in its current state
S on (so no advanced fast boot options
Hboot only
no recovery.
clear memory
only productive thing is successful esprimg.zip updates
its the official update to froyo, and need HTCsync and the RUU from htc how the installs procces goes i dont really know, but im sure there is a RUU update that you can use to update via bootloader,
ok i got htc sync
and the official exe.
my pc only detects the device in hboot. The device will read usb hboot.
1 might fiddle around for 20 mins to see whats what.
.
If it was like a esmprimg.zip then it would seem more feasible.
goood luck hope you get your phone back up and running
well a week ago it finally booted. I felt that it was a fluke so I pressed the power button to reboot. I tried to turn it back on then it was stuck at the splash screen.
I am now starting to think it is a hardware problem. Either way the unrooted tmobile comet,yes it is small, is doing wonders. The battery life is way better then a iphone 3g.
Just remember guys, if you get an android phone, make sure it is a popular one. That way you are more likely to get support because of the bigger fan base. Oh well it was fun while it lasted. The only thing I hate is that i could have gotten an xbox 360 for the same price. oh well, thanks for the assistance. i will lets you know any further updates.
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.