Database Users

MyTouch 4G freezes every time after reboot or factory reset, I'm stuck, please HELP..

Ok, I know I am a noob to android phones and to this forum, but I already spent many hours online researching the problem and didn't find anything that helped.
So, here's what happened:
I got my MyTouch 4G about 2 weeks ago unlocked. I wanted to get rid of a lot of the garbage that came with it, so I followed the steps and successfully rooted it and then removed several of the preinstalled apps with Titanium backup. So far, no noticeable problems.
Then I wasn't happy with how quickly my battery was draining, so I installed Advanced Task Killer, and set it to automatically kill certain apps periodically.
A few days later when I was trying to add a widget to the desktop, I got the familiar to some message "Sorry, com.htc.launcher has stopped working". Everything else was still working fine on the phone. I researched the problem and the first proposed solution to clear the data for the process from Settings/Applications, did not help. The second proposed solution was to do a factory reset. So, I rebooted with volume down + power pressed together and chose factory reset.
After 4-5 min, I got into the welcome screen where I did the initial setup. After this was complete, the phone checked off that everything was setup correctly (apps, widgets, etc). Then it started loading the desktop and the message "loading..." appeared. This is where it froze.
Basically, I can't get past the "loading..." message on the home screen, no desktop ever loads, and I have access to nothing other than the camera key.
I let it stay for hours to see if it will eventuall load, but nothing happened. I also rebooted and tried factory reset many times and it always get stuck at the same point. I tried all of the above with and without a SIM card, with and without a memory card - basically I exhausted all possible combinations but I always get the same frozen "loading..." screen.
Has anyone experienced this problem? I feel helpless rebooting or reseting the phone from the phone itself because it always get stuck. Is there a way to factory reset from a computer?
Thank you so much if you can help me with any advice and Happy New Year!
Vess

Sounds like u deleted something dealing with the launcher. Doing factory reset well not put it back. I would say, do a nandroid backup, flash iced glacier rom. U could just download another launcher, but being that u wiped the phone, u can't even get to market in that state.

esincho said:
Sounds like u deleted something dealing with the launcher. Doing factory reset well not put it back. I would say, do a nandroid backup, flash iced glacier rom. U could just download another launcher, but being that u wiped the phone, u can't even get to market in that state.
Click to expand...
Click to collapse
Hi, thank you for your message. I think you are correct about deleting the launcher and factory reset not fixing it.
But I don't know how to do "nandroid backup, flash iced glacier rom". Could you point me to instructions on that? Sorry, I'm really new to android phones.

I'm on my phone, go to the development section for this rom. You're see iced glacier. Instructions on the first post

esincho said:
I'm on my phone, go to the development section for this rom. You're see iced glacier. Instructions on the first post
Click to expand...
Click to collapse
I did what you suggested but from what I understand to flash a rom I need to be able to boot into Recovery mode, which I can't do either. Every time I choose Recovery I get the "!" screen and I'm stuck. Am I doing something wrong?
Thank you.

vess22 said:
so I followed the steps and successfully rooted it
Click to expand...
Click to collapse
You didn't by any chance install Clockwork ROM Manager, flash ClockworkMod Recovery and then make a Nandroid backup before doing all of this, did you?

shlongwoodian said:
You didn't by any chance install Clockwork ROM Manager, flash ClockworkMod Recovery and then make a Nandroid backup before doing all of this, did you?
Click to expand...
Click to collapse
No sir, I didn't do any of the above unfortunately. From what I understand had I done that, I wouldn't have a problem booting into Recovery mode, correct?

I believe you might still be able to get to what you need via adb. That's not my specialty though, even though I can mash out a few commands and comprehend what I'm doing. It would be remiss of me to guide you any further, but I don't think all hope is lost for you. Search the forums for 'adb' and 'recovery' and let's also see who replies back with some better advice.

Find the raw .img of cw recovery then adb flash_recovery /location/of/recovery.img
If that doesn't work you'll need to use fastboot assuming you updated to eng spl.
Sent from my HTC Glacier using XDA App

sounds like your boot.img is borked.... try flashing one of the many available kernels (make sure it will work with your rom first... if you haven't flashed a rom or flashed a sense based rom then use an HTC kernel if you're running CM or MIUI use a CM based kernel) and then when you get it running read this and understand why task killers are bad FAQ: You shouldn't be using a task killer with Android

Yes, I'm starting to realize that now my only option is to do flash recovery through adb. So, I've spent all night last night trying to understand what adb is. I installed and updated the sdk, but my adb shell doesn't see my phone as a listed device, so I'm stuck at this point. And yes, I read probably 5 tutorials on installing various usb drivers/ modifying sdk ini files/etc to make your computer recognize the phone as an adb device. I tried everything that was suggested but no luck so far.
I've spent nearly 30 hours so far since this whole disaster started and although I haven't made much progress, I've learned quite a few things.
And, no, I won't mess with Advanced Task Killer or Titanium Backup any more, just give me my phone back and working

Are you s=off with eng boot loader, I don't think you will be able to get a stable adb connection with the ROM acting all wonky.
Best bet is fastboot flash recovery
Sent from my HTC Glacier using XDA App

ESKIMOn00b said:
Are you s=off with eng boot loader, I don't think you will be able to get a stable adb connection with the ROM acting all wonky.
Best bet is fastboot flash recovery
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Yes, s=off with eng boot loader. However, I never did a custom ROM flash, so I cannot go to recovery mode from the phone. I thought even for fastboot flash recovery I need an adb connection, no? How else can I do that?
Thanks.

vess22 said:
Yes, s=off with eng boot loader. However, I never did a custom ROM flash, so I cannot go to recovery mode from the phone. I thought even for fastboot flash recovery I need an adb connection, no? How else can I do that?
Thanks.
Click to expand...
Click to collapse
Boot into fastboot and then you should have access to adb. You can then use fastboot to flash clockwork recovery.
There is a STOCK NANDROID RESTORE somewhere in the development section here. Use clockwork recovery to restore that nandroid, boot up and go on your merry way.
EDIT:
download clockwork recovery and save it to c:\android-sdk-windows\tools (or maybe platform-tools, depending on where the fastboot.exe file is located)
CLOCKWORK RECOVERY LINK
power off phone
hold vol down + power
select FASTBOOT
connect phone to computer - let windows do it's hardware detecting/installing thing
open a command prompt and navigate to your sdk tools folder
type this, without quotes "fastboot flash recovery recovery.img"
disconnect phone and power off/reboot/etc
You should now have access to clockwork recovery and be able to flash whatever you want

Phateless said:
Boot into fastboot and then you should have access to adb. You can then use fastboot to flash clockwork recovery.
There is a STOCK NANDROID RESTORE somewhere in the development section here. Use clockwork recovery to restore that nandroid, boot up and go on your merry way.
EDIT:
download clockwork recovery and save it to c:\android-sdk-windows\tools (or maybe platform-tools, depending on where the fastboot.exe file is located)
CLOCKWORK RECOVERY LINK
power off phone
hold vol down + power
select FASTBOOT
connect phone to computer - let windows do it's hardware detecting/installing thing
open a command prompt and navigate to your sdk tools folder
type this, without quotes "fastboot flash recovery recovery.img"
disconnect phone and power off/reboot/etc
You should now have access to clockwork recovery and be able to flash whatever you want
Click to expand...
Click to collapse
Thank you, thank you! You saved my life. Finally a solution that worked for me. God bless you
BTW, I was never able to get adb detect my phone but fastboot did! So, I followed the steps you suggested and it worked. So relieved now
Vess

vess22 said:
Thank you, thank you! You saved my life. Finally a solution that worked for me. God bless you
BTW, I was never able to get adb detect my phone but fastboot did! So, I followed the steps you suggested and it worked. So relieved now
Vess
Click to expand...
Click to collapse
lol, glad I could help! ADB should be working in Clockwork Recovery now, btw.
You should have seen how I freaked out the first time I tried to root my mt3g. I forgot to wipe and it kept freezing on boot, lol.
So what are you gonna do now? Load a custom rom or stay with stock?

Phateless said:
lol, glad I could help! ADB should be working in Clockwork Recovery now, btw.
You should have seen how I freaked out the first time I tried to root my mt3g. I forgot to wipe and it kept freezing on boot, lol.
So what are you gonna do now? Load a custom rom or stay with stock?
Click to expand...
Click to collapse
I just loaded ice glacier 1.1.4 unthemed. To be honest I don't see much difference except that the bloatware is gone, so I'm happy with it. I don't know if it makes sense to go back to stock. My phone is not under warranty. Is there another reason one might want stock?

vess22 said:
I just loaded ice glacier 1.1.4 unthemed. To be honest I don't see much difference except that the bloatware is gone, so I'm happy with it. I don't know if it makes sense to go back to stock. My phone is not under warranty. Is there another reason one might want stock?
Click to expand...
Click to collapse
You make an appealing case for Iced Glacier.
Stock tends to be the most stable and reliable, plus you get OTA updates. Other than that, not much reason. I can tell you from recent experience that my phone gets a gps lock much quicker with stock than with cm6, but I'll do further testing to see if that's really the case.

I'm having a similar problem and I'm following these steps, but not having any luck.
Info on my phone: It's a MT4G that I got just this past week from eBay, worked fine up until this morning. Does not have an SD card and the one I have from my previous phone (Vibrant) is a highly suspect piece of junk so it's not in the phone right now. I was running VISIONary+ on it and had just set it to temp root on boot, but never got it to reboot. I plugged it in to charge this morning, thought it was plugged all the way in (maybe it wasn't? Would that cause this kind of borking?) and the phone froze. Rebooting didn't help. Actually I had pulled the battery, rebooted it, stuffed it in my pocket and then 2 hours later realized it was still on the boot up screen. That's when I got scared. It's running ADW, Superpower, TIBackup and Tasker, but there's no other software I can think of on the phone that might have mattered. Never installed Clockwork or anything like that before, regretting that now.
On the hboot screen I have:
GLACIER PVT SHIP S-ON
HBOOT 0.86.0000
MICROP-0429
RADIO 26.03.02.26_M
eMMC-boot
Sep 27 2010, 11:12:59
Click to expand...
Click to collapse
Going to Fastboot, I can get the phone to be recognized as an HTC Bootloader in my device manager, and I can try and get the recovery.img loaded as was instructed above using adb but it always fails. Output from that is:
sending 'recovery' (8701 KB)... OKAY [471.891s]
writing 'recover'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 473.125s
Click to expand...
Click to collapse
When I try and do recovery, I get a quick flash of a phone with a red exclamation point over it, then black screen of nothing. Booting regular leads to a constant white MyTouch4g screen, no change. Trying Factor Reset leads to the skateboarding androids, no change even after a long time. In any of these cases, I have to pull the battery before I can try anything again.
Did I bork my phone? How the heck did I do that? Is there any way to further save it? Any help you guys could give me would be massively appreciated, thanks in advance.

RedDonkey said:
I'm having a similar problem and I'm following these steps, but not having any luck.
Info on my phone: It's a MT4G that I got just this past week from eBay, worked fine up until this morning. Does not have an SD card and the one I have from my previous phone (Vibrant) is a highly suspect piece of junk so it's not in the phone right now. I was running VISIONary+ on it and had just set it to temp root on boot, but never got it to reboot. I plugged it in to charge this morning, thought it was plugged all the way in (maybe it wasn't? Would that cause this kind of borking?) and the phone froze. Rebooting didn't help. Actually I had pulled the battery, rebooted it, stuffed it in my pocket and then 2 hours later realized it was still on the boot up screen. That's when I got scared. It's running ADW, Superpower, TIBackup and Tasker, but there's no other software I can think of on the phone that might have mattered. Never installed Clockwork or anything like that before, regretting that now.
On the hboot screen I have:
Going to Fastboot, I can get the phone to be recognized as an HTC Bootloader in my device manager, and I can try and get the recovery.img loaded as was instructed above using adb but it always fails. Output from that is:
When I try and do recovery, I get a quick flash of a phone with a red exclamation point over it, then black screen of nothing. Booting regular leads to a constant white MyTouch4g screen, no change. Trying Factor Reset leads to the skateboarding androids, no change even after a long time. In any of these cases, I have to pull the battery before I can try anything again.
Did I bork my phone? How the heck did I do that? Is there any way to further save it? Any help you guys could give me would be massively appreciated, thanks in advance.
Click to expand...
Click to collapse
The instructions above only pertain to a rooted phone. Your phone is not rooted and you dont have eng bootloader. Without superuser access you cant even flash recovery like you were trying. A factory reset didnt fix your problem?
Side note, im an opponent of doing the whole temp rooting only thing cause if you screw something up you dont have access to tools to fix anything, your just screwed if something happens like this.

[Q] MyTouch 4g: Multiple problems... PLEASE help.

Okay, I've searched and searched and no one seems to have the specific problem that I'm having with my phone, so I'm taking to the forums myself. I've been rooting since the G1, I know how to adb push things, I have used google and multiple forums to try to fix this problem. So here goes, anyone that can help I thank you in advance.
1-My phone, like some other MT4G users, reboots itself each time it's plugged in. Initially I thought this was because I was using a Kindle cord to plug it into the pc, so I bought an MT4G usb cable from tmobile, and still it boot loops (just the first white screen for maybe 4 seconds, then black then again and again). The only way to charge it is to let it start boot looping, take the battery out, turn it on, and if I'm lucky enough that it begins to boot up correctly I plug it in mid boot. If I wait til it's fulled loaded it just starts rebooting again.
2-It will not at all from any angle go into Recovery mode. If I try to go to recovery from Rom Manager, or from the screen you get when holding power and lower volume key or by flashing a rom through Rom Manager, it just boot loops just like mentioned above, until I pull the battery for a while (it is currently sitting next to me with the battery out) and then put it back in.
3-If by chance it's on, and plugged into the computer, it is not at all recognized. Ever. While it's booting up my computer finds something, but doesn't know what it is, and doesn't allow me to view any folders on the SD card. Yes I've installed the HTC drivers file. I've adb'ed things to this phone before, now it says device not found. I don't know when it stopped being recognized...
4-I've even tried to fastboot something over to it, but to no avail, still not found.
If I try to do a factory reset, it boot loops. If I sneeze it boot loops.... I don't know what to do, and if I trade it in under warranty, I have to reset it to stock rom, or they're going to charge me for a new phone. Any ideas!?
I have Cyanogen mod 7 on here.

have you tried a fastboot wipe? or have you tried to reboot to recovery from adb?

First, I don't trust using the actual ROM Manager app to do the flashing/installing.
Since you've been flashing since the G1 days why not use Clockwork Recovery? Just go into recovery and do the necessary wipes.
So I suggest to do a complete full wipe in Clockwork, meaning wipe data, cache, and dalvik cache. Install the newest CM nightly (Which is working wonderfully BTW) and see if your problems still persists.
Edit: I didn't realize you tried to enter recovery, oops. But yeah try what the buy above me said. Try re-installing the latest CWM recovery, if that still fails then try heading into there via ADB.

mackster248 said:
First, I don't trust using the actual ROM Manager app to do the flashing/installing.
Since you've been flashing since the G1 days why not use Clockwork Recovery? Just go into recovery and do the necessary wipes.
So I suggest to do a complete full wipe in Clockwork, meaning wipe data, cache, and dalvik cache. Install the newest CM nightly (Which is working wonderfully BTW) and see if your problems still persists.
Click to expand...
Click to collapse
I second that, flashing ROMs from ROM Manager a terrible idea.

Well...if all else fails and if you are really thinking about returning it and still under warranty...few seconds in the microwave method should work just fine. They wont be able to see that its rooted if the phone wouldn't turn on, would they???

glimmer of hope...
So by the grace of god I did get it flashed back to unrooted, stock 2.2 by putting it as pd15img.zip on my sd card and going into bootloader. Once that was done I thought I would be out of the woods... I even plugged it in last night and no boot loop!! but this morning I unpllugged it (and I'm using a tmobile cable for the phone attached to my pc) and here it sits, next to me again with the battery out of it because everytime I try to turn it on (for over 40 minutes now) it boot loops to that stupid white screen (that is honestly driving me insane at this point). I know that it isn't rooted (because I dl'ed rom manager and it won't let me do anything without being rooted) so do we think that I'm safe to go to the store today to request a new one be sent? Thoughts? And thanks for the help thus far!

yeah I would send that back

Bad emmc chip? I'm sorry man, that's a terrible story.
Sent from my HTC Glacier using XDA App

[Q] Boot loop but can get into recover and flash

OK heres the deal. I have done tons of searching and it looks like I SHOULD be able to get out of this, but I cant figure it out and I may have gone to far(by unrooting with 4.24 and bootloader 2.16).
So long story short, my launch day evo got lost about a month after I got it. Got a replacement from Sprint(or whoever their insurance is), my original Evo got found about a month or so after that. It has not been powered on since then(a year realistically) with no battery or SD card in it. I got bored and decided to power it up and update everything(because I cant do **** with my new Evo3d, yet since im on a Mac and have no access to a PC). Here are where things went bad.
Phone was rooted with the very original Toast method including S-off with the .76 Eng boot loader. I was running some form of CM6 on it when I lost it.
-Went to power it up and it boot looped at the white Evo4g screen.
-Went into bootloader and tried to get into recovery(had Amon RA 1.7 I think). No go.
-Flashed the new TWRP recovery and got into recovery just fine.
-Flashed the CM7.1.0-RC1
-reboot into a boot loop
-battery pull and a reboot and it loaded, but after about 30 seconds, reboot into a boot loop.
-Thought maybe TWRP didnt like the phone so I flashed Amon RA 2.3
-went into recovery just fine. Did complete wipes of everything using Calkulin Wipe all.zip
-re-flashed CM7.1.0 RC1
-boot loop
-flashed latest radios
-rebooted back into recovery
-reflashed cm7.1.0 rc1
-boot loop
During all of the reboots I would occasionally get the CM7 splash screen and then a reboot into boot loops. I THINK everything was flashing ok.
At this point I was frustrated and was thinking it was something I was doing that was jacked up so I decided to unroot and I flashed the newest RUU(which obviously removes root, S-off, .76 boot loader, etc...) so I did it. Figured I was just trying to get the phone running to sell anyway. Flashed was successful, chose to reboot and guess what. Boot loop. I pulled the battery out for about 10 minutes and it boots into the rom, runs for about 10-15 seconds in the rom and then reboots, back into the rom at least, but only about 10-15 seconds later, another reboot.
Every thread I read on these infinite boot loops were guys saying they couldnt even get into recovery or flash anything, which I had no problem doing(obviously cant really do that anymore with losing root and s-off). So I am stuck.
So current state of the phone is boot loader 2.16 S-on with 4.24.651.1 with all current radios, etc... flashed(as far as I can tell) from the RUU posted on Goo-inside.me.
Does anybody have any ideas for me to try? It seems like I am so close to getting it running because it will run for about 60 seconds but then reboot. I am guessing a hardware issue, but I honestly at this point have no clue.

Sounds like a hardware issue to me.
Sent from my PC36100 using XDA Premium App

Rem3Dy said:
Sounds like a hardware issue to me.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Thats what I am leaning towards, but why, if a hardware issue, will the phone run in the boot loader or recovery for basically forever without rebooting? It will also successfully(or did) flash everything I asked it to. I would think it would always reboot around that 60 second time frame if it was a hardware issue.

damn, too bad you ran RUU & lost s-off. now you couldn't do anything to test/troubleshoot even if you wanted to.

drdrewdown said:
damn, too bad you ran RUU & lost s-off. now you couldn't do anything to test/troubleshoot even if you wanted to.
Click to expand...
Click to collapse
I know. I probably should have posted up and waited, but I got impatient and thought that was a last ditch effort anyway since I tried everything else I knew to try.

rjacobs said:
but why, if a hardware issue, will the phone run in the boot loader or recovery for basically forever without rebooting? It will also successfully(or did) flash everything I asked it to. I would think it would always reboot around that 60 second time frame if it was a hardware issue.
Click to expand...
Click to collapse
because in the boot loader and recovery menu I'm sure the phone is not accessing radios, audio components, gps, and all manner of other hardware components that get activated once the phone tries to boot up for real.

It sounds like according to this thread: http://forum.xda-developers.com/showthread.php?t=805612&page=4
That my NV is FUBAR, but since I ran RUU and lost S-off, I cant do the fix. Oh well, I am sure eventually somebody will crack the boot loader and then I can fix it. Otherwise I have to send it off to HTC and I am sure pay them to fix it.

Just to clarify. The thread you linked to is for people who wrote nv items to their device.
What I'm afraid you are experiencing is the bootloop commonly complained about by those running CM roms.
I have yet to find a solution to the CM bootloop and all signs point to hardware failure.
Sent from my Evo using XDA Premium App

Boot loop not past Evo Splash screen

I know this is a known issue but I wanted to see if anyone has had any luck yet.
My phone only gets to the HTC Evo splash screen and reboots. I can get into hboot and when i choose recovery from hboot it goes back into the boot loop.
This just happened to me a few days ago. I went from MikG to Deck to CM7. I just flashed CM7 over Decks 1.3 wiping only cache and dalvik. I was starting to really dig CM7 and I was planning on sticking with it. When it happened I was using the stock web aplication. I finished reading the page I was on and hit the back button (the one at the bottom of the phone) and next thing I knew my phone started rebooting. It never made it past the Evo splash screen since. I've been able to flash different hboots and it takes but it does not take any of the recoveries or RUUs. Has anyone had any luck with this yet? Or does anyone have any different advice with the extra info I have provided?
To reiterate I cannot get into recovery only hboot.
Thanks a ton in advance all.

nanstedt said:
I know this is a known issue but I wanted to see if anyone has had any luck yet.
My phone only gets to the HTC Evo splash screen and reboots. I can get into hboot and when i choose recovery from hboot it goes back into the boot loop.
This just happened to me a few days ago. I went from MikG to Deck to CM7. I just flashed CM7 over Decks 1.3 wiping only cache and dalvik. I was starting to really dig CM7 and I was planning on sticking with it. When it happened I was using the stock web aplication. I finished reading the page I was on and hit the back button (the one at the bottom of the phone) and next thing I knew my phone started rebooting. It never made it past the Evo splash screen since. I've been able to flash different hboots and it takes but it does not take any of the recoveries or RUUs. Has anyone had any luck with this yet? Or does anyone have any different advice with the extra info I have provided?
To reiterate I cannot get into recovery only hboot.
Thanks a ton in advance all.
Click to expand...
Click to collapse
Try getting this:
http://goo-inside.me/amon_ra/supersonic/recovery-RA-supersonic-v2.3-PC36IMG.zip
To thee root of your SD card and then boot into HBOOT to load it.
Make sure it is named PC36IMG.zip
You may be missing your recovery.

atapia984 said:
Try getting this:
http://goo-inside.me/amon_ra/supersonic/recovery-RA-supersonic-v2.3-PC36IMG.zip
To thee root of your SD card and then boot into HBOOT to load it.
Make sure it is named PC36IMG.zip
You may be missing your recovery.
Click to expand...
Click to collapse
I appreciate the link but my issue is that I can flash the recovery files from hboot but to my dismay I still cannot get to recovery from the recovery selection within hboot. There seems to be an issue where hboot hands the reins off to recovery or android. I'm not sure how to troubleshoot or overcome something like that. Maybe my assumption is wrong but who knows.

You don't have to go into recovery to flash a pc36img. It happens in Hboot.
In theory, you should be able to flash that, then flash recovery.

HipKat said:
You don't have to go into recovery to flash a pc36img. It happens in Hboot.
In theory, you should be able to flash that, then flash recovery.
Click to expand...
Click to collapse
Is the link provided not Amra recovery? That is what it looks like to me, but I could be wrong. Please advise. I can flash the recoveries in hboot but when i go to recovery from the hboot screen and select it the boot loops commence.

Unfortunately, that is a problem that you can search and see a fair number of people have had and I don't think anyone has fixed it as it means bad blocks and/or something to do with partitions being resized and I hate to even say this, but all but a very few cases were running CM7

HipKat said:
Unfortunately, that is a problem that you can search and see a fair number of people have had and I don't think anyone has fixed it as it means bad blocks and/or something to do with partitions being resized and I hate to even say this, but all but a very few cases were running CM7
Click to expand...
Click to collapse
Yes, i've noticed that. I was hoping that since it had been a while that someone had found a solution. Hopefully a dev will chime in and give some steps that I haven't taken yet.

nanstedt said:
Yes, i've noticed that. I was hoping that since it had been a while that someone had found a solution. Hopefully a dev will chime in and give some steps that I haven't taken yet.
Click to expand...
Click to collapse
I hope you hear something. Mine is exhibiting a similar behavior. Maybe time to trash this phone or at least flash it back to stock so I can take it back to Sprint.

jerrykur said:
I hope you hear something. Mine is exhibiting a similar behavior. Maybe time to trash this phone or at least flash it back to stock so I can take it back to Sprint.
Click to expand...
Click to collapse
I wish i could flash it back to stock so i could use it again. I paid $200 for this thing. I'd like to get a few more years out of it. Nothing like the OG. I've tried running the RUU files from windows while in hboot and the files do change as I flash different versions. I noticed this when during the ruu program it shows you the from/to screen. So I know the RUU programs are working, it's just that the hboot recovery/ROM handshake is not happening. I guess I'm hosed ATM.

Evo 4G stuck in hboot

EVO 4G rooted with Unrevoked. Right now I can only boot into bootloader and fastboot. There is no ROM and It will not let me load ROM or recovery from fastboot or sdcard. I can fumble around fastboot and adb but most of the time I get an error.
sending 'recovery' (209 KB)...
OKAY [ 0.273s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.274s​
Here is the bootloader info:
SUPERSONIC EVT3 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​
Any help greatly appreciated! If I am in the wrong place, very sorry

Which recovery are you trying to flash and how?? via PC36IMG?

Thanks for the reply!!! recovery-RA-supersonic-v2.3.img. and update-cm-7.1.0-Supersonic-signed.zip I tried both as pc36img from HBoot and via fast boot. neither worked. I also tried to install to change boot.img via fastboot. same message.

Look for the Amon Ra thread in the Development section, grab the PC36IMG.zip Make sure that it's named exactly like that and flash that in Hboot. That should give you recovery.

i wish there was odin for htc devices

Will try that again first thing in the a.m. Been working on it all day and the brain is mush! I'll post the result as soon as I'm done. Thanks!
Sent from my PG86100 using XDA App

i am having a similar problem. nothing will put my phone into recovery. I even went to sprint and the guy there had rooted 2 of his phones and he couldnt help me.
-Revolutionary-
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.0808
i have been rooted for a while and i have changed ROMS many times. but the other day i flashed fresh evo and my phone wouldnt reboot and i thought i screwed it up but then after a minute it came on. realized that ROM wasnt what i wanted and i flashed myn warm 2.2 and it rebooted just fine but when my phone turned on, it just kept initializing and didnt end up running. then i realized i didnt flash the radio and wimax updater it came with. so i went into recovery and wiped everything then reflashed the rom and radio wimax and it just froze in the white htc evo 4g screen. getting to hboot and bootloader works fine but freezes when i try to go to recovery.
if i didnt make sense or said something stupid i apologize!! i am a 4 month noob. any help is appreciated!! thanks!!

johnnyboy1409 said:
i am having a similar problem. nothing will put my phone into recovery. I even went to sprint and the guy there had rooted 2 of his phones and he couldnt help me.
-Revolutionary-
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.0808
i have been rooted for a while and i have changed ROMS many times. but the other day i flashed fresh evo and my phone wouldnt reboot and i thought i screwed it up but then after a minute it came on. realized that ROM wasnt what i wanted and i flashed myn warm 2.2 and it rebooted just fine but when my phone turned on, it just kept initializing and didnt end up running. then i realized i didnt flash the radio and wimax updater it came with. so i went into recovery and wiped everything then reflashed the rom and radio wimax and it just froze in the white htc evo 4g screen. getting to hboot and bootloader works fine but freezes when i try to go to recovery.
if i didnt make sense or said something stupid i apologize!! i am a 4 month noob. any help is appreciated!! thanks!!
Click to expand...
Click to collapse
That was what happened to me sorta. I have been flashing that phone since November of last year. Something must have hiccuped during the last flash process because I have never had that happen before. This is my first possible brick and I am really pissed that I can't figure it out!!! Arrrgg! Off to start over with the new Amon RA recovery! Wish me luck!

johnnyboy1409 said:
i am having a similar problem. nothing will put my phone into recovery. I even went to sprint and the guy there had rooted 2 of his phones and he couldnt help me.
-Revolutionary-
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.0808
i have been rooted for a while and i have changed ROMS many times. but the other day i flashed fresh evo and my phone wouldnt reboot and i thought i screwed it up but then after a minute it came on. realized that ROM wasnt what i wanted and i flashed myn warm 2.2 and it rebooted just fine but when my phone turned on, it just kept initializing and didnt end up running. then i realized i didnt flash the radio and wimax updater it came with. so i went into recovery and wiped everything then reflashed the rom and radio wimax and it just froze in the white htc evo 4g screen. getting to hboot and bootloader works fine but freezes when i try to go to recovery.
if i didnt make sense or said something stupid i apologize!! i am a 4 month noob. any help is appreciated!! thanks!!
Click to expand...
Click to collapse
Well this happened to me once, what i did was i put on my sd card any other rom (i was using cm7 nightlies so i put another nightly in) and then i wiped cache and flashed it, however it might also help if from this link http://forum.xda-developers.com/showthread.php?t=1295702 you get the format all zip and use that to wipe everything. once you have flashed another rom and your phone turns on wait a little bit and then try once again to flash the first rom you were trying to flash.
[email protected] said:
That was what happened to me sorta. I have been flashing that phone since November of last year. Something must have hiccuped during the last flash process because I have never had that happen before. This is my first possible brick and I am really pissed that I can't figure it out!!! Arrrgg! Off to start over with the new Amon RA recovery! Wish me luck!
Click to expand...
Click to collapse
can you go to the recovery? if you can try to do what i told johnnyboy1409

HipKat said:
Look for the Amon Ra thread in the Development section, grab the PC36IMG.zip Make sure that it's named exactly like that and flash that in Hboot. That should give you recovery.
Click to expand...
Click to collapse
Holy Cannoli!! Ok that .zip worked for the recovery (I tried several different downloads!) Now I have to see if I can copy an image. Wish me luck!

Thanks for the info. I totally though the phone was bricked. Actually the phone would load in HBoot and Fastboot but I couldn't get a recovery on or a ROM. In other words there was no ROM to boot to. In addition to that, wether I tried from SD card or fastboot, I couldn't get any .img, .zip etc to install. So here I was with an HBoot - S-off and no way to get a recovery or ROM on the puppy. I am still working on this and still jammed up but the recovery gives me hope. Please stick around in case I have a meltdown. (hasn't happened yet but I can feel it getting closer!) LOL
Stick around for the detail of what I did If I can get this ROM onboard! Maybe this will help someone else.

Success!!! I have a recovery and a ROM!
Here are the details...First I believe my SD card was/is corrupted. I am still using it and I formatted it several times but I think something was squirrely which is now fixed. Second, the Amon Ra PC36IMG.zip that I downloaded at : http://forum.xda-developers.com/showthread.php?t=705026&highlight=recovery
worked awesome to get a working recovery via HBoot and SD Card. Next, I used the new recovery to load my ROM. and Voila a working phone.
Moral of the story, Check the SD card, USB drivers, and file downloads for corruption. I think one or all of these played a part in my crash.
@ Johnboy this is an excellent group of developers and members here at XDA, I have been flashing both Winmo and Android for a long time but can always rely on the forums to bring me back to center when I crash and burn! Thanks everyone for your help.

You should try wiping everything but your SDcard: option and flashing a ROM first and see what happens

HipKat said:
You should try wiping everything but your SDcard: option and flashing a ROM first and see what happens
Click to expand...
Click to collapse
That's Funny, I just did that and everything is fine. I just reloaded the ROM and looks like something just got corrupted and all I needed was a little help from my friends to figure things out

[email protected] said:
Success!!! I have a recovery and a ROM!
Here are the details...First I believe my SD card was/is corrupted. I am still using it and I formatted it several times but I think something was squirrely which is now fixed. Second, the Amon Ra PC36IMG.zip that I downloaded at : http://forum.xda-developers.com/showthread.php?t=705026&highlight=recovery
worked awesome to get a working recovery via HBoot and SD Card. Next, I used the new recovery to load my ROM. and Voila a working phone.
Moral of the story, Check the SD card, USB drivers, and file downloads for corruption. I think one or all of these played a part in my crash.
@ Johnboy this is an excellent group of developers and members here at XDA, I have been flashing both Winmo and Android for a long time but can always rely on the forums to bring me back to center when I crash and burn! Thanks everyone for your help.
Click to expand...
Click to collapse
np ^_^ hope i helped, whenever i think my phone has an issue booting or something i just automatically assume that it's fixable, i haven't had my phone die on me yet and i'm not planning on it... *cough cough* Screw Apple *cough cough*

johnnyboy1409 said:
i am having a similar problem. nothing will put my phone into recovery. I even went to sprint and the guy there had rooted 2 of his phones and he couldnt help me.
-Revolutionary-
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.0808
i have been rooted for a while and i have changed ROMS many times. but the other day i flashed fresh evo and my phone wouldnt reboot and i thought i screwed it up but then after a minute it came on. realized that ROM wasnt what i wanted and i flashed myn warm 2.2 and it rebooted just fine but when my phone turned on, it just kept initializing and didnt end up running. then i realized i didnt flash the radio and wimax updater it came with. so i went into recovery and wiped everything then reflashed the rom and radio wimax and it just froze in the white htc evo 4g screen. getting to hboot and bootloader works fine but freezes when i try to go to recovery.
if i didnt make sense or said something stupid i apologize!! i am a 4 month noob. any help is appreciated!! thanks!!
Click to expand...
Click to collapse
Johnnyboy1409 Did you ever get this fixed?

No it won't let me go into recovery to flash anything. All I need is a trick to get into recovery and I can wipe everything then perform a nandroid restore. I already have had the pc36img.zip on the root of the zip. It is copied correctly but idk if I spelled it right on here cuz I'm on my girlfriends phone and can't remember it.everytime I boot into hboot that zip updates but doesn't help...

johnnyboy1409 said:
No it won't let me go into recovery to flash anything. All I need is a trick to get into recovery and I can wipe everything then perform a nandroid restore. I already have had the pc36img.zip on the root of the zip. It is copied correctly but idk if I spelled it right on here cuz I'm on my girlfriends phone and can't remember it.everytime I boot into hboot that zip updates but doesn't help...
Click to expand...
Click to collapse
when you go to boot loader and it loads, it then should ask if you want to update splash - hit no, then to reboot - hit no, then you should be able to go one down and hit recovery. do you get those options?

I get those options but when I click recovery it goes to the white htc Evo 4g screen and stays there no matter how long I wait.

johnnyboy1409 said:
No it won't let me go into recovery to flash anything. All I need is a trick to get into recovery and I can wipe everything then perform a nandroid restore. I already have had the pc36img.zip on the root of the zip. It is copied correctly but idk if I spelled it right on here cuz I'm on my girlfriends phone and can't remember it.everytime I boot into hboot that zip updates but doesn't help...
Click to expand...
Click to collapse
I know I sound like a broken record but try formatting your SD card or using a different known good card and also use the link in my post above to re-download the pc36img.zip Amon RA Recovery. Then you know all the components are "clean and without erro". Then you can start to figure out the problem.