Please Help

[KDaves88]

Okay, I have HTC EVO 4G, idk what information you guys need but I'll just put some here first

This is on HBOOT screen.

SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00

Now my problem, I rooted my phone approximately 2-3 weeks ago. I used Unrevoked 3. I was running the latest version of MikFroyo and I decided I wanted to try CM7. I wiped everything multiple times, just in case, and then I installed CM7. I used Clockwork to do all this but later I changed to Amon-RA only because I heard it clears the caches better... Idk myself. I didn't change any kernels but I was using SetCPU and had it overclocked to 1113Mhz, that's what it showed up as. Everything was running smoothly for about a week. This last Saturday I was using my phone, talking with someone, and as I went to hang up the screen went black. I tried to press the power button but nothing happened. Also, the screen wasn't just black, I could tell it was lit-up, it was just blank. I then preceded to remove the battery after fiddling with it for a couple of minutes. Re-inserted the battery and the white boot screen comes on, vibrates, and then reboots... Does this over and over. So I'm nervous and I think it's the ROM. I go home and start up HBOOT and try to go into recovery. Boots into recovery with a blank screen... Lit up but blank. Now after researching this up and down and trying millions of different things I have come here to ask for help and to see if anyone knows how to fix this. I tried re-installing the PC36IMG.zip multiple times. I tried messing with ADB but I do not know very much about that. I've read that I probably have the Boot Loop Of Death and that there is no fix to it. I really don't want to accept that. There is no way into my recovery, that I know of, and I can't get into my phone at all. I ran RUU and it went through succesfully but still a problem with the screen being blank/black. One thing I also need to mention is that when I allow it to boot up completely after the white splash screen in the beginning, I can hear the OEM Sprint start up sound but I CANNOT see it... I then wait a few more seconds and it's still a black screen. I hit the power button and the screen turns off and when I turn the screen back on it displays the lock screen as if it's working. I try to drag the bar down but now the screen is unresponsive. I have no idea what is going on. Seems to me like it's a hardware issue possibly caused by either, CM7 kernel or ROM, or because I had it overclocked. I was just curious if anyone knew of a way to fix this. Sorry I made this so long, I didn't know any other way to describe everything...

Edited: One thing I forgot to include, I just tried doing the PC36IMG.zip again and when I go into recovery it stays black but at the very bottom of the screen it just shows

Build:

That's it..

 

[eldub1]

Did you try the battery pull. Hit the power button and volume down at the same time to get to manual recovery?

 

[KDaves88]

What exactly is a manual recovery? I may not have tried it seeing as I don't know what it is...

Thanks for your response...

Bump

 

[SmokeCrawler]

What exactly is a manual recovery? I may not have tried it seeing as I don't know what it is...

Thanks for your response...

Bump

Its just recovery. Where you do everything manually from recovery instead of having an app like Rom Manager do it for you.

 

[KDaves88]

Oh... Yeah, that's all I used. I didn't use APPS to do any flashing. Always did everything from recovery. Now I can't even get into it.. Like I said, after entering recovery from HBOOT all I see is

Build :

That is at the very bottom of the screen in the left hand corner. It stays there forever. Big problem here, is it fixable?

 

[mr.seth.price]

this happened to me the other day on Myns rom...though i may have been..."messing" with it. I eventually got it to boot into recovery and flashed the first Nandroid that I had from like 7 months ago and it worked well for me. Well I lost a bunch of texts and whatnot...but you know.

 

[KDaves88]

I eventually got it to boot into recovery and flashed the first Nandroid that I had from like 7 months ago and it worked well for me.

Do you remember what you did to get back into recovery?? I tried reflashing the PC36IMG.zip many many times.

 

[SmokeCrawler]

My guess is you could have a sort or something with your screen. As you described you can hear the boot animation sound but can't see anything until the lockscreen. Have you tried to install both types of recoveries from your bootloader?

 

[KDaves88]

My guess is you could have a sort or something with your screen. As you described you can hear the boot animation sound but can't see anything until the lockscreen. Have you tried to install both types of recoveries from your bootloader?

I have tried both recoveries. Any other ideas? =(

 

[SmokeCrawler]

You can try from the android terminal emulator if you want. You will have to download Amon's .img from xda instead of the .zip that you have now.

Open the terminal and allow superuser.
When you first start you will see a "$" sign. After entering su you will see "#" sign just to let you know.

 su
flash_img recovery /sdcard/recovery-RA-supersonic-v2.3.img
reboot recovery

If that doesn't work then maybe use adb.

 

[KDaves88]

You can try from the android terminal emulator if you want. You will have to download Amon's .img from xda instead of the .zip that you have now.

Open the terminal and allow superuser.
When you first start you will see a "$" sign. After entering su you will see "#" sign just to let you know.

 su
flash_img recovery /sdcard/recovery-RA-supersonic-v2.3.img
reboot recovery

If that doesn't work then maybe use adb.

Do you think you could get me a link on how to do that step by step? I've tried using ADB a little bit and I've tried looking for something to walk me through but idk if I was doing it right. I wasn't getting any results. Also, about Superuser, does it come with the emulator or something? When I did the RUU to my phone I'm guessing that I do not have Superuser anymore.

Thanks a lot for comments, sorry for the hassle, I tried to make this my last resort.

Update: I think I found something I can try... Is this what you're talking about? http://forum.xda-developers.com/showthread.php?t=705026
I can't get into the app obviously because my phone won't turn on. Idk if ADB will work or not. I'll try it when I get home from work.

 

[SmokeCrawler]

Do you think you could get me a link on how to do that step by step? I've tried using ADB a little bit and I've tried looking for something to walk me through but idk if I was doing it right. I wasn't getting any results. Also, about Superuser, does it come with the emulator or something? When I did the RUU to my phone I'm guessing that I do not have Superuser anymore.

Thanks a lot for comments, sorry for the hassle, I tried to make this my last resort.

Update: I think I found something I can try... Is this what you're talking about? [Recovery] [09-Feb-2011] RA-supersonic-v2.3 - xda-developers
I can't get into the app obviously because my phone won't turn on. Idk if ADB will work or not. I'll try it when I get home from work.

By running the RUU you just put the unrooted stock rom on your phone. So no you don't have superuser. The emulator and Rom Manager won't work.

Do you still have s-off? Right now this is important.

Yes that is the website I was referring to.

 

[KDaves88]

By running the RUU you just put the unrooted stock rom on your phone. So no you don't have superuser. The emulator and Rom Manager won't work.

Do you still have s-off? Right now this is important.

Yes that is the website I was referring to.

Yeah, I ran the RUU when this first started happening hoping that it would fix the problem, obviously I was incorrect in my assumptions...

Yes, I do still have S-OFF.

 

[SmokeCrawler]

I've tried using ADB a little bit and I've tried looking for something to walk me through but idk if I was doing it right. I wasn't getting any results.

Sorry for not addressing this earlier.

Did you have usb debugging on?
Did you go into adb shell?

To make sure your phone is being seen do this. (type in how you have your folder name for your android sdk) I'll put mine in just to show how it goes.

cd c:\androidsdk\platformtools
adb devices

If it shows your device then we will move on.

We will remount and go into our shell.
Once in adb shell you will see a #. Now you will put in the command as the terminal. (I'm trying to find a vid to give you a visual aid)

adb remount
adb shell
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img
reboot recovery

Hope this works for you.

Edit: Couldn't find any vids for you. If this doesn't work then I'm out of suggestions.

 

[KDaves88]

Sorry for not addressing this earlier.

Did you have usb debugging on?
Did you go into adb shell?

To make sure your phone is being seen do this. (type in how you have your folder name for your android sdk) I'll put mine in just to show how it goes.

cd c:\androidsdk\platformtools
adb devices

If it shows your device then we will move on.

We will remount and go into our shell.
Once in adb shell you will see a #. Now you will put in the command as the terminal. (I'm trying to find a vid to give you a visual aid)

adb remount
adb shell
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img
reboot recovery

Hope this works for you.

Edit: Couldn't find any vids for you. If this doesn't work then I'm out of suggestions.

A few questions; 1. Does it matter if I am in fastboot or HBOOT? 2. I'm using my command prompt from windows... Should I be using something else? 3. Am I using the correct driver? (HTC Bootloader) 4. Do I need anything else installed on my computer? Currently have Android SDK software, ADB software, and the aforementioned driver.

If none of those things need to be changed, then when I changed my directory to C:\Program Files (x86)\Android\android-sdk\platform-tools this is what I get...

>cd  C:\Program Files (x86)\Android\android-sdk\platform-tools

C:\Program Files (x86)\Android\android-sdk\platform-tools> adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached

C:\Program Files (x86)\Android\android-sdk\platform-tools> adb remount
devices not found

I hope I'm doing something wrong. Otherwise my device is not recognized at all.... =( It is recognized in fastboot but not ADB. I reflashed RUU from a .zip file, still the same start-up thing, no picture, only sound.. Freezes on lock screen, touchscreen unresponsive.

Edit: Well, I found this site, I got to page seven so far and it's looking pretty grim. Thanks for all your help but I think reading through the rest of this forum should answer any further questions I have. I really appreciate your time though. Hopefully someone figures this thing out. I need sleep now.

Here is the forum link: http://forum.xda-developers.com/showthread.php?t=1009672&page=7