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.

Bricked Evo? Stuck in Boot Loop

I'm rooted, unrevoked; I'm currently stuck in a boot loop. I can not reach recovery. I can not get to my rom. I can only access bootloader.
So far I have taken these steps to cure my problem:
Ran RUU software in Windows (with and without sd card in evo)
Flashed RUU as PC36IMG in bootloader
Cleared Storage using fastboot in command prompt
Cleared Recovery and then Flashed Amon Ra's Recovery and Clockwork using fastboot in command prompt
Flashed Amon Ra's Recovery and Clockwork as PC36IMG in hboot
Flashed Sprint Lover's as PC36IMG in hboot
Flashed eng-PC36IMG from Toastctfh's Old Root Tutorial as PC36IMG in hboot
Each of these methods flashed successfully as far as I can tell... yet I still go into an infinite boot loop.
Before the bootloop this is what I was doing:
I had the initial CM7 nightly installed for about 2 weeks. It was buggy, and a few days ago restarted and deleted all my texts, and desynced from google. On rebooting, google apps acted as if I had never ran the phone before - it asked me to enter google account info, etc, upon reboot.
I decided CM7 was too unstable and so I wiped data and davlik, and flashed CM6. When CM6 booted google apps was already on, before I had even flashed it! Anyways I figured I wanted to give MIUI a run, so I wiped data and davlik, and flashed MIUI. It ran fine for about two hours, and then rebooted out of nowhere... and never came out of the boot loop.
I'm really starting to sweat this as I have gone three days now without a phone. Does anyone have any ideas that may help me? Thanks.

If I am unable to get out of my boot loop, does anyone know if I would be able to unroot my phone and then take it into Sprint and get another?

Are you able to boot into recovery?
Sent from my PC36100 using XDA App

unfortunately, nope

Hmm then I'm not to sure what to tell you. That was my only idea.
Sent from my PC36100 using XDA App

bump, maybe with a new day a new person will have a new idea?

Hopefully
Sent from my PC36100 using XDA App

bump to this as I am also experiencing this same situation. Phone stuck in an infinite bootloop to the white htc screen then all over again. can get into bootloader but not into recovery.
tried all the above. this was out of nowhere.

This problem is all over the Evo section, especially in Q&A and I don't think I've seen anyone come out of it.
On the positive side, I also don't think I've seen anyone take theirs back to Sprint and have a tech even check to see if their phone was rooted or not, and btw, next time you flash a new ROM, not saying this is the cause, wipe EVERYTHING, not just cache and dalvik-cache

Having the same problem here also...

didi you try the clear storage mode in the boot loader cause if you already flashed the PC36IMGyou wouldnt have a custom recovery just the triangle screen i recomend doing it with the original 2.1 zip file then just re rooting it put the rom then flash radio and g apps

dominirican said:
didi you try the clear storage mode in the boot loader cause if you already flashed the PC36IMGyou wouldnt have a custom recovery just the triangle screen i recomend doing it with the original 2.1 zip file then just re rooting it put the rom then flash radio and g apps
Click to expand...
Click to collapse
I have tried everything you have mentioned and nothing works...

The OP's list of attempted fixes looks like he ran the gamut.
Unless there's a fix that I haven't read about, it's time for a trip to the Sprint store....

I have someone working on mine that claims he can get it fixed...has access to things I don't. We will see. I will report the results.

Ok...He did it and its up and running. I was trying to flash mine to Boost Mobile so thats how i got mine into a boot loop but he got mine out of it with this...Download the
README_EVO.docx
http://forum.xda-developers.com/showthread.php?t=805612&page=4

[Q] OK so i know my GF's phone isnt bricked but...

Hey MT4G guru's i need your assistance.
1st off im an Evo user..rooted and all so im not to shabby at doing this. 2nd I rooted her phone using visionary.
So on to the problem. I tried to flash her a theme. I nandrioded (backup) first as usual. The theme which ended up being a full ROM--> http://forum.xda-developers.com/showthread.php?t=929101
It flashed successfully but when i rebooted it gets stuck at the white MT4G screen and stays there forever.
**I can still get into the bootloader & recovery.**
Tried to restore...NO LUCK. It restores, I reboot then the Same white screen.
Tried to factory reset, dalvik & cache wipe..... NO LUCK
Tried Update.zip Nothing!!!
Even tried pd15img in the bootloader. NOTHING!! It doesnt even recognize it!!
Guys i even looked into odin which i found out it isnt needed on phones with recovery.
Hate to sound like a noob but Help!!!!
...A fixed phone will result in 30,000 "thanks" button presses.....cause shes pissed to say the least....
Edit: Ok i believe i found the problem. I had clockwork 2.5.1.2 instead of 3 on her phone. Ok so now that i found the problem how do i fix it??

go to this link http://goo.gl/K0xTy and follow the instructions. you are flashing a cm7 rom and for this phone requires a different recovery. Then flash your rom

Flash cm6 first it will boot with 2.5
twiztid

If you made a nandroid backup, which you always should do before flashing a new rom, you can restore it using clockwork 2.5.1.2. If you don't have a backup you can do two things. You can use fastboot to flash clockwork recovery v3.0.0.5 to the phone then reboot into recovery and successfully flash CM7. If you don't know how to use fastboot then you can use the existing recovery to flash a froyo based rom on the phone. Either iced glacier or CM6 will flash ok. Perform a full wipe before you flash. Once you have a froyo rom working you can follow TrueBlue_Drew's thread about getting clockwork 3 on the phone without issue. I'm on my phone so I can't provide the link but it is in the mt4g development section. It is in a sticky called Resource Bible. In the OP, scroll until you see the header Recoveries and choose the link called Easiest way to install clockwork 3.0.0.5 by TrueBlue_Drew. Follow his instructions and you'll be able to switch between clockwork versions with no hassle. Of course, once you have clockwork 3 working you can flash CM7.
EDIT: Drew replied before I finished writing so follow his link once you are able to boot successfully.
Phillysphinest1 said:
Hey MT4G guru's i need your assistance.
1st off im an Evo user..rooted and all so im not to shabby at doing this. 2nd I rooted her phone using visionary.
So on to the problem. I tried to flash her a theme. I nandrioded (backup) first as usual. The theme which ended up being a full ROM--> http://forum.xda-developers.com/showthread.php?t=929101
It flashed successfully but when i rebooted it gets stuck at the white MT4G screen and stays there forever.
**I can still get into the bootloader & recovery.**
Tried to restore...NO LUCK. It restores, I reboot then the Same white screen.
Tried to factory reset, dalvik & cache wipe..... NO LUCK
Tried Update.zip Nothing!!!
Even tried pd15img in the bootloader. NOTHING!! It doesnt even recognize it!!
Guys i even looked into odin which i found out it isnt needed on phones with recovery.
Hate to sound like a noob but Help!!!!
...A fixed phone will result in 30,000 "thanks" button presses.....cause shes pissed to say the least....
Edit: Ok i believe i found the problem. I had clockwork 2.5.1.2 instead of 3 on her phone. Ok so now that i found the problem how do i fix it??
Click to expand...
Click to collapse
Swyped on my rooted MyTouch4G

XfooYen said:
If you made a nandroid backup, which you always should do before flashing a new rom, you can restore it using clockwork 2.5.1.2. If you don't have a backup you can do two things. You can use fastboot to flash clockwork recovery v3.0.0.5 to the phone then reboot into recovery and successfully flash CM7. If you don't know how to use fastboot then you can use the existing recovery to flash a froyo based rom on the phone. Either iced glacier or CM6 will flash ok. Perform a full wipe before you flash. Once you have a froyo rom working you can follow TrueBlue_Drew's thread about getting clockwork 3 on the phone without issue. I'm on my phone so I can't provide the link but it is in the mt4g development section. It is in a sticky called Resource Bible. In the OP, scroll until you see the header Recoveries and choose the link called Easiest way to install clockwork 3.0.0.5 by TrueBlue_Drew. Follow his instructions and you'll be able to switch between clockwork versions with no hassle. Of course, once you have clockwork 3 working you can flash CM7.
EDIT: Drew replied before I finished writing so follow his link once you are able to boot successfully.
Swyped on my rooted MyTouch4G
Click to expand...
Click to collapse
Dooohhh!!! Thanks for cleaning this up for me. I forgot to tell him he needed to DL and install a 2.2 rom using his current recovery if he cant restore the nandroid. on a side note....I'm typing this from my laptop that is using my wifi hotspot from my friends truck somewhere (middle of nowhere) in Colorado in a snow storm. got to love technology. I am also downloading the latest nightly. Only 28 minutes left on this slow edge connection, but at least its working

TrueBlue_Drew said:
Dooohhh!!! Thanks for cleaning this up for me. I forgot to tell him he needed to DL and install a 2.2 rom using his current recovery if he cant restore the nandroid. on a side note....I'm typing this from my laptop that is using my wifi hotspot from my friends truck somewhere (middle of nowhere) in Colorado in a snow storm. got to love technology. I am also downloading the latest nightly. Only 28 minutes left on this slow edge connection, but at least its working
Click to expand...
Click to collapse
Stay warm..
Swyped on my rooted MyTouch4G

TrueBlue_Drew said:
go to this link http://goo.gl/K0xTy and follow the instructions. you are flashing a cm7 rom and for this phone requires a different recovery. Then flash your rom
Click to expand...
Click to collapse
twiztidmyt4g said:
Flash cm6 first it will boot with 2.5
twiztid
Click to expand...
Click to collapse
UPDATE:
Ok.........(drum roll please)..........and the winner to the simplest answer that i should of thought of myself but i didnt cause i paniced is.....
TrueBlue Drew & Twiztidmy4g
All I needed to do was full wipe & flash a compatible ROM & it booted up fine!!!
**Attention XDA**
National crisis averted!!!! Woman is now satisfied. We nearly missed a nucular meltdown!! Thanks guys!!!!!
MODS PLEASE CLOSE OR COMPLETELY BURN & DELETE THIS WORTHLESS THREAD!!!!!

CM6 download
New to mt4g and have the same problem, i know i cant got o rom manager because i cant boot, can you provide a link to a cm6.zip file that i can run using clockwork 2.5.1.2
Thanks and yes i searched ont he forums for mt4g and i only see cm7 ....

"You can use fastboot to flash clockwork recovery v3.0.0.5 to the phone then reboot into recovery and successfully flash CM7. "
So how do you use fastboot to flash clockwork ? need help here i have clockwork on the sd card and installed using recovery but when i power volume down i am still in clockwork 2.5.1.2
How do i change clockwork to 3.0.0.5 from fastboot ?
Found it.... http://forum.xda-developers.com/showthread.php?t=876632
Installed it and then updated clockwork now in CM& ... wow Thanks .... ?

cmboud said:
So how do you use fastboot to flash clockwork ? need help here ......
Found it.... http://forum.xda-developers.com/showthread.php?t=876632
Installed it and then updated clockwork now in CM& ... wow Thanks .... ?
Click to expand...
Click to collapse
Didn't even have to reply. The search button is a marvelous thing. Good lad!
Swyped on my rooted MyTouch4G

Bootlooping =\

Hopefully this is the right place. Ive searched and not quite found exactly my situation, so if there are similar threads, I apologize..
So I have CyanogenMod 6.1.2 on my Evo, with MattedBlues skinned over it.
Last night it rebooted randomly in the middle of me writing a text and went into bootlooping from the HTC EVO 4G splash. I cannot get into recovery and Ive tried running the stock RUU .exe (as I did last time I bricked my phone) and I get error 170 over and over (from HBOOT USB and FastBOOT USB menus).
What can I do? I dont have the cash right now to pay the deductible for a new phone and I *must* have a phone.
I rooted using Unrevoked 3, but I believe my recovery image is damaged, and my HBoot is 0.97.00 when Ive read I need 0.76.
How can I fix my phone?
If I can get adb to recognize my phone, can I just push/flash a new recovery using adb since I cant get into recovery through the phone?

Shaihalud9 said:
Hopefully this is the right place. Ive searched and not quite found exactly my situation, so if there are similar threads, I apologize..
So I have CyanogenMod 6.1.2 on my Evo, with MattedBlues skinned over it.
Last night it rebooted randomly in the middle of me writing a text and went into bootlooping from the HTC EVO 4G splash. I cannot get into recovery and Ive tried running the stock RUU .exe (as I did last time I bricked my phone) and I get error 170 over and over (from HBOOT USB and FastBOOT USB menus).
What can I do? I dont have the cash right now to pay the deductible for a new phone and I *must* have a phone.
I rooted using Unrevoked 3, but I believe my recovery image is damaged, and my HBoot is 0.97.00 when Ive read I need 0.76.
How can I fix my phone?
If I can get adb to recognize my phone, can I just push/flash a new recovery using adb since I cant get into recovery through the phone?
Click to expand...
Click to collapse
Should have posted this in the q&a but try THIS post and we'll go from there.

I should have, but thanks, I will try that.

Shaihalud9 said:
I should have, but thanks, I will try that.
Click to expand...
Click to collapse
If your having issues running the ruu and the error your not completely out of luck. I have unrooted several times that way. I would recommend try rebooting your computer first off. After that before you run the ruin reboot the bootloader a couple Times, in fastboot you'll see the reboot option. This has always solved the issue for me, may take a few times but its still worth a shot.
Sent from my PC36100 using XDA App

Yellowcard8992 said:
If your having issues running the ruu and the error your not completely out of luck. I have unrooted several times that way. I would recommend try rebooting your computer first off. After that before you run the ruin reboot the bootloader a couple Times, in fastboot you'll see the reboot option. This has always solved the issue for me, may take a few times but its still worth a shot.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Rebooting the bootloader doesnt help, still getting Error 170, so hopefully flashing a new recovery from HBoot will.

Okay so copying the PC36IMG to my SDcard, the bootloader recognizes it, and reads it, and I get a progress bar on the right.... but no option to flash the image, and booting into recovery does nothing.
Im going to try an HBoot run of the PCIMG36 RUUs I found on another page... I dont mind going back to stock, I just want the damn phone to work.

Double post.

So I used the latest PC36IMG Signed zip from here: http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu&page=7, and it went through, did all the updates, but when asked to reboot, which I did, I get a blinking yellow LED that goes solid, boots up, get the EVO 4G white splah for a few moments... then nothing.
Im hoping its just a dead battery. =\ Gonna try it again in a bit.
Nope. Still getting bootloops, even with the new PCIMG flashed. What the f*cking hell.

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.