Help! Reboot Loop, S-On PCIMG36 Not Working, what next.

[nuffstylez]

Hi, got a serious that I can't figure out, on day 8 with no change. Here's the details
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.16.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.00808
Mar 8 2011, 17:02:15

The phone is unrooted. This is my sisters phone and I took out the battery without turning off the phone. (I do it all the time with my touchpro2, will never do it again!) I put my SD card in and turned it back on and now it's in a reboot loop. It starts up, shows the white screen with the htc EVO 4G then reboots to the same thing over and over. I could get into the bootloader. I tried all of the options. Recovery just goes to the white screen again with the htc evo 4g logo and starts the reboot loop. I did clear storage, and when it reboots it starts the loop too.
I tried loading the PC36img.zip file to a formatted sd card and the phone reads it but doesnt give me any prompts to install or anything, it just goes to the regular bootloader screen, and recovery still doesn't work. I tried loading some shipped roms but I think Im on the latest rom so it won't let me install any roms because I'm not rooted. I get an error 140 -bootloader version error. What else can I do? I am so stressed over this and my eyes are killing me from all of the seaching. I tried setting up sdk and adb but couldnt get it to work and don't think it would read my phone cause it won't start up to set up the usb debug mode. I tried renaming a rom pc36img seeing if the phone will read it. Please help me. Im out of options.

 

[AlphaTango414]

Download the latest stock RUU and run it. goo-inside.me/supersonic

DumpedDuce Approves This Message Via HTC Evo 4g

 

[nuffstylez]

okay, I downloaded the latest RUU which is the one I am on now 4.54.651. Ran it and it loaded up and went through the whole process. When it finishes, it reboots and starts the loop again. I also put the correct PC36IMG file on my SD card and it found it and the phone loaded it. But still the same thing. I dunno what to do next.

 

[nuffstylez]

Oh yeah, I also tried the UnlockBootloader thing from HTCDEV. But when I get to step 8 to enter the command, the phone gives an error. But the computer finds the phone in fastboot.

 

[vipersinu2]

I have the exact same problem, fastboot will read device. adb will not. we need a way to repair the recovery. which I get an error trying to flash a new recovery in fast boot. or find a way to get s-off thru fast boot. is there a RUU made with s-off already in it?

 

[vipersinu2]

does anybody have info on Jtag?

 

[vipersinu2]

I downloaded ruu 4.54.651.1.
when installing the ruu go to start, run, cmd, type %temp%
leave your mouse on the folders to highlight and see the size of the folders.
look for anything over 200mb
inside you will find the rom.zip, you have to search while ruu is running other wise
when ruu is complete the files delete. copy and paste rom.zip. then put on the sdcard and lable PC36IMG.zip
(make sure the rom is not labled zip.zip)
here is what I get in hboot vol up to update

parsing sd zip
1 radio v2 OK
2 recovery REBOOTs phone
3 bootloader OK
4 wimax
5 splash1
6 boot
7 userdata
8 system

reboots and comes back to bootloader , press power to get to hboot
sd checking files, volume up

1 recovery ok
2 wimax ok
3 splash ok
4 boot ok
5 user data ok
6 system ok
finishes do you want to reboot device vol up yes

reboots back into boot loop, no recovery, adb devices nothing listed, fastboot devices has my serial number
but when I try to command fail bad signature.
I am s-on
hboot 2.16.0001
radio 2.15.00.080

 

[nuffstylez]

Vipersinu2, I've done everything and more that you did and came up with the same outcomes. I came to the conclusion that since the phone is unrooted (S-On), we are assed out. There is nothing we could do to fix our phones. I ended up buying one off of ebay, a factory refurb. My first thing to do when I get the phone is to root it. Hopefully, you could figure something out to get the phone fixed, but I just gave up. I spent endless hours on this phone and finally gave up.

 

[vipersinu2]

looking for some help with adb, does the phone have to be on and booted for adb to work. my two other evo's at bootloader screen return device not found, when I turn them on and let them boot it finds the serial numbers in adb, So I am thinking adb is usless on the bricked phone?

 

[nuffstylez]

I think for the phone to work with adb, it has to boot up all the way and you have to be able to go to the menu and enable usb debugging. Since our phones don't, we can't do anything with adb. And I looked up about jtag, it seems a little complicated and probably not worth it since the prices on these phones have dropped. I think that the real problem with these (our) phones is that the NV values are corrupted, since this is what loads first when you turn on the phone. Even if you run a RUU, it doesnt do anything to the NV values, thus the problem with reboot loops. If the phone was rooted, then we could mess with the partitions and rewrite the NV values.