Supersonic evt2-3 ship s-off
hboot-2.02.0000
microp-041f
touch panel-atmel224-16ab
radio-2.15.00.09.01
root evo, i flashed my phone with some kind of rom i forgot the name, it flashed in all on clockwork, then after a day it the battery went dead and then when i charged it it boots to the htc evo 4g white screen and just sits there..i did the pow+vol down..went to the bootloader, then go to recovery and it still sits on the white screen,i did the pcimg36 method that didnt work either.....i think this phone is screwed
501rockstar said:
Supersonic evt2-3 ship s-off
hboot-2.02.0000
microp-041f
touch panel-atmel224-16ab
radio-2.15.00.09.01
root evo, i flashed my phone with some kind of rom i forgot the name, it flashed in all on clockwork, then after a day it the battery went dead and then when i charged it it boots to the htc evo 4g white screen and just sits there..i did the pow+vol down..went to the bootloader, then go to recovery and it still sits on the white screen,i did the pcimg36 method that didnt work either.....i think this phone is screwed
Click to expand...
Click to collapse
What did you flash a PC36IMG of? An RUU, or did you try to reflash a recovery. My first suggestion would have been to reflash recovery, using a PC36IMG, and see if that gets you recovery back. Is that what you already tried? If not, try it. I will attatch a PC36IMG of Amon Ra recovery. Flash it with the bootloader, and see if you can get into recovery once it's finished flashing. If that works, then try doing a complete wipe (wipe EVERYTHING except your sd card, maybe even use a Format all.zip). Then reflash a rom. If you're unsuccessful with flashing the recovery, I'd suggest trying an RUU or a PC36IMG of an RUU again.
Again, the PC36IMG I attatched is of Amon Ra V 2.3.
Find RUU's and PC36IMG's here: http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
Or try this PC36IMG of the 3.70 RUU here: http://db.tt/gqTAPS1
"Some kind've ROM"?
That's a little vague, isn't it?
501rockstar said:
Supersonic evt2-3 ship s-off
hboot-2.02.0000
microp-041f
touch panel-atmel224-16ab
radio-2.15.00.09.01
root evo, i flashed my phone with some kind of rom i forgot the name, it flashed in all on clockwork, then after a day it the battery went dead and then when i charged it it boots to the htc evo 4g white screen and just sits there..i did the pow+vol down..went to the bootloader, then go to recovery and it still sits on the white screen,i did the pcimg36 method that didnt work either.....i think this phone is screwed
Click to expand...
Click to collapse
You don't remember the rom you flashed? Seriously? Did you not download it from somewhere and if so, can you not get on your computer, go to that particular site where you downloaded the rom from and retrieve its name? After flashing the rom, what other changes, if any, did you make to your device? Was the phone performing fine before the battery drained? C'mon man, help us help you?....
posting & replying via the XDA Premium app.
HipKat said:
"Some kind've ROM"?
That's a little vague, isn't it?
Click to expand...
Click to collapse
That's what I was thinking. Not remembering the name doesn't sound hopeful either.
OP, do you know if it was AOSP or Sense? 2.2 or 2.3? Did you get it from xda?
More importantly, did you do a nandroid backup before flashing? If so, you need a PC36IMG.zip of Clockwork so you can go in and restore your backup.
Recovery image of clockwork provided; remove the -1 in the name, place on the root of your sdcard, and flash it in the bootloader.
ok im gonna do it and see what happens
downloaded.. RUU_SuperSonic_S_Sprint_WWE_3.29.651.5_Radio_2.15. 00.09.01_NV_1.77_CNV_release_150224_signed.exe (192.95 MB)
open the app and got a error saying error 170 usb connection(the evo is and stuck at the htc evo 4g white screen)
and when i plug in my evo while its on white screen it will say drivers not install..then i check my device manage and the evo drivers are known as qualcomm cdma technologies msm
the rom that messed my phone up was Myn’s Warm TwoPointTwo, i tried flashing the zip through clockwork...but it failed. now i cant get into clockwork and flash any zip nomore ...when i go to recovery it sits on the white htc evo 4g screen
You need to connect you evo in fastboot from the bootloader, then run the ruu from the pc.
501rockstar said:
the rom that messed my phone up was Myn’s Warm TwoPointTwo, i tried flashing the zip through clockwork...but it failed. now i cant get into clockwork and flash any zip nomore ...when i go to recovery it sits on the white htc evo 4g screen
Click to expand...
Click to collapse
Nope. That particular rom did not mess up your device, unless of course, the zip was corrupted somehow. Flashing it through ClockworkMod probably did. Why are you using an older software version (3.29)? The latest version is 3.70.
UPDATE: Once you've flashed the recovery via the bootloader, as directed by others, download the SECOND FILE from the link below, copy it to your SD card and then flash it from within recovery. It is the rooted stock rom.
http://forum.xda-developers.com/showthread.php? t=884060
posting & replying via the XDA Premium app.
Ive flashed probably a hundred times and ive never had a ROM brick my phone, and that includes Myn 2.2.
Either something went wrong with the flash, which i find highly unlikely, or the rom was corrupted. Do you know for sure that the download finished completely, and that you didnt flash a corrupted ROM? And are you absolutely sure that you flashed a ROM for the evo? I dont particularly like Myn, so im not an expert on it, but are you sure you didnt flash a version not meant for the evo?
But whatever you did, it seems like your boot image is corrupted. Since you can get to the bootloader you should be able to fix any software problem through an RUU or using fastboot to flash a new recovery.
The unfortunate thing is, a lot of people seem to be having this same problem and no software flash seems to be able to fix it.
See this thread: http://forum.xda-developers.com/showthread.php?t=1009672&page=32
The conclusion ive come to, and i am by no means an expert, is that the NAND memory has worn out. Its called Read Only Memory for a reason. NAND flash memories can be written to but theyre meant to be read from and dont take to well to constant writing. Normal use wares out all types of solid state memories, particularly NAND flash memories. If you have too many bad blocks that there isnt enough good blocks to fit the files you need (boot image, recovery image, system image, etc), then no amount of software flashes will fix it because its a hardware problem.
This doesnt mean that this is your problem. I couldnt possibly know that for sure. but if RUU's and fastboot commands do not work your out of luck, and its probably a hardware problem. If you have S-on you can take it to sprint since it wont even boot and they couldnt tell its rooted. Theyll run a diagnostic tool that will tell them how many bad blocks your memory has and probably just give you a new one.
If your phone has S-off i wouldnt take it back to sprint, they wont like that. If the bootloader says S-off (and you cant fix it) your better off buying insurance and "losing" the phone. Keep trying a bunch of different PC36IMG.zip's, some people with this problem have been able to turn their phone from s-off to s-on.
yea after i looked around im becoming more convinced that its bad blocks. Look around the forums about "the white screen of death". Again, i cant be sure at all that this is the problem until you try every software solution. But this problem has just popped up a little bit ago and you have pretty much all the symptoms. I've never seen an evo not be able to boot to recovery after a flash. It simply doesnt make sense since the rom wouldn't have included new recovery or boot images. The only thing that really makes sense is that one unfortunate flash ruined one too many memory cells and the phone no longer has enough free memory to execute the boot files.
in short, fastboot and the bootloader are your new best friends. Are you familiar with fastboot commands?
Also, how old is your phone. Is the hardware version lower than 0003?
Related
EDIT: Check post 10 for an update on progress after running the stock RUU
Been reading XDA for awhile, first time posting. I'll try to put as much information on here as possible so please excuse the long drawn out post.
Have been running MIUI 11.16 release on Evo 4g until two days ago. My evo began bootlooping in my pocket, which happens sometimes but usually on the splash screen. This is usually fixed by a battery pull and a ROM reflash in Clockwork Recover. However, on this occasion my phone has been bootlooping on the HTC screen. I booted into bootloader and attempted to then boot into recovery but the loop continued.
I have the original PC361.zip still on my SD card so decided to run the update and see if that would reset things. The update was successful and I attempted to boot recovery . The HTC screen flashes and proceeds to a black screen with 5 vibrates and a blinking LED. This now happens every time I turn on the phone with booting into the bootloader.
I attempted (perhaps incorrectly) to flash clockwork recovery through Fastboot USB through my Mac Terminal, but have been unable to do so as it won't allow a remote flash.
./fastboot flash /recovery /Users/****/Desktop/android-sdk-mac_x86/tools/recovery-clockwork-1.8.1.7-supersonic.zip
sending '/recovery' (808 KB)... OKAY
writing '/recovery'... FAILED (remote: not allowed)
So, to recap. Normal boot results in 5 vibrates and a green LED flash that is only reset by a battery pull. Fastboot access is available, but perhaps not usable by remote access. No access to recovery. Cannot mount SD card onto my Mac (not sure if that's a given). Top of bootloader screen says the following:
Supersonic EVT2- 3 ship s-off
HBOOT-0.79.0000
MicroP-041f
Touch Panel-ATMEL224_16ab
Radio-1.39.00.04.26
April 14 2010, 15:41:34
I've done a lot of forum hopping and reading and it seems like this is the most relevant information for trying to fix this problem. At this point, my only real goal is to make a phone call or two so I'm not worried about keeping my root since that can be fixed later. Any suggestions would be much appreciated and I can furnish any information you might need.
Thanks
Have you tried flashing a stock ROM RUU updater from www.shipped-roms.com?
This may not get you into your rooted state with your custom rom, but should at least get you into a usable state.
You should still be rooted afterwards, but will need to run UNREVOKED FOREVER, to get your clockwork recovery back.
Just downloaded an executable RUU filed from Shipped ROM's. I'll go find a Windows system and give it a shot. I'll update in a bit.
I think the .exe is finding the android device, but doesn't do anything after update is hit. Is there a way to connect my phone to the computer to run this .exe through bootloader?
agrim0091 said:
I think the .exe is finding the android device, but doesn't do anything after update is hit. Is there a way to connect my phone to the computer to run this .exe through bootloader?
Click to expand...
Click to collapse
Select hboot usb and make sure the drivers install (probably windows only, sorry) then run the ruu. I think the needed drivers are included with the htc sync software (windows only as well I believe)
DomSim said:
Select hboot usb and make sure the drivers install (probably windows only, sorry) then run the ruu. I think the needed drivers are included with the htc sync software (windows only as well I believe)
Click to expand...
Click to collapse
Just tried with hboot usb plug hooked up and it didn't recognise. I'll try to install HTC Sync and give it another shot. Thank you guys for the help so far.
The RUU successfully installed and booting the phone no longer causes the 5 vibrations and the green LED. The phone is still bootlooping at the HTC screen going to a black screen and then rebooting.
This is the first breakthrough I've made in days. Any ideas on where I should go from here?
I would think maybe flash radio, then they to flash recovery. Maybe wait until someoe else chimes in though
DomSim said:
I would think maybe flash radio, then they to flash recovery. Maybe wait until someoe else chimes in though
Click to expand...
Click to collapse
I tried to flash recovery through Fastboot and my Mac terminal, but I'm still being denied remote access.
A quick update on the situation to try to consolidate any progress so far...
I successfully flashed the stock RUU which should have returned everything back to stock. I'm still stuck in a bootloop from the HTC screen to black screen but no longer have the 5 vibrates and the flashing green LED.
My Bootloader heading is as thus...
Supersonic EV2-3 Ship S-off
hboot- 0.93.0000
microp-014f
Touch Panel-ATMEL224_16ab
Radio-2.15.00.07.28
Jul 23 2010, 16:41:47
Booting into recovery from Bootloader still causes the boot cycle meaning that the RUU didn't fix everything. Also, S-OFF still seems to mean that the root appears to be in place (maybe?) so no luck of returning it to sprint. Still cannot remote flash from the command prompt in windows.
I'm not sure what to do next. If I had to wager a guess it would have something to do with the PC36img.zip file, even though I'm not totally sure what this means or which one I should attempt to load. If this is the case, I can go buy an SD card reader today and attempt to load another up if anyone can suggest one.
Again, thanks for all of the help.
agrim0091 said:
A quick update on the situation to try to consolidate any progress so far...
I successfully flashed the stock RUU which should have returned everything back to stock. I'm still stuck in a bootloop from the HTC screen to black screen but no longer have the 5 vibrates and the flashing green LED.
My Bootloader heading is as thus...
Supersonic EV2-3 Ship S-off
hboot- 0.93.0000
microp-014f
Touch Panel-ATMEL224_16ab
Radio-2.15.00.07.28
Jul 23 2010, 16:41:47
Booting into recovery from Bootloader still causes the boot cycle meaning that the RUU didn't fix everything. Also, S-OFF still seems to mean that the root appears to be in place (maybe?) so no luck of returning it to sprint. Still cannot remote flash from the command prompt in windows.
I'm not sure what to do next. If I had to wager a guess it would have something to do with the PC36img.zip file, even though I'm not totally sure what this means or which one I should attempt to load. If this is the case, I can go buy an SD card reader today and attempt to load another up if anyone can suggest one.
Again, thanks for all of the help.
Click to expand...
Click to collapse
did you try to unroot don't know if you used unrevoked but if you did try to flash the s-on tool and then flash the 3.29 ruu that should put you back up to stock and load good but if it doesn't then you may have a corrupted nand. Don't take my word for it cause i know computers more than these phones i know enough to get me by thats about it but if they are anything like computers i would venture that as the problem
Jbcarrera said:
did you try to unroot don't know if you used unrevoked but if you did try to flash the s-on tool and then flash the 3.29 ruu that should put you back up to stock and load good but if it doesn't then you may have a corrupted nand. Don't take my word for it cause i know computers more than these phones i know enough to get me by thats about it but if they are anything like computers i would venture that as the problem
Click to expand...
Click to collapse
Any idea how to flash this through Fastboot or the Bootloader?
agrim0091 said:
Any idea how to flash this through Fastboot or the Bootloader?
Click to expand...
Click to collapse
adb but i'm trying to find out how for you
Jbcarrera said:
adb but i'm trying to find out how for you
Click to expand...
Click to collapse
Just realized my old BlackBerry has microSD support. So I can load something onto my Evo SD card via that quite easily if you think a certain PC36img.zip file would work. I just have no idea what those PC36img.zip files are or do. :/
Jbcarrera said:
adb but i'm trying to find out how for you
Click to expand...
Click to collapse
Just found a PC36img.zip file for clockwork recover. Update was "Successful" but the Boot cycle continues.
Is this the pc36img you tried? If not try it.
http://forum.xda-developers.com/showthread.php?t=780141
Try hboot usb and start adb type push unrevokeds-on.zip that should give you s-on then run the 3.29 Thu that should work
sent from my EVO at the edge of hell
No internet access last night at the apartment for some reason :/. I'll try flashing the PC36img.zip and if that doesnt work i'll try to adb push the s-on file and get it back to total stock to bring it back to sprint.
Thinking about it though, I'm not sure if I had adb access from hboot. I'll update you guys soon.
DomSim said:
Is this the pc36img you tried? If not try it.
http://forum.xda-developers.com/showthread.php?t=780141
Click to expand...
Click to collapse
Flashed this PC36IMG.zip. Update was successful but the phone is still looping.
Jbcarrera said:
Try hboot usb and start adb type push unrevokeds-on.zip that should give you s-on then run the 3.29 Thu that should work
sent from my EVO at the edge of hell
Click to expand...
Click to collapse
I can't get adb to recognize my device with hboot usb plug showing. I tried adb devices and nothing will pop up.
I'm having this same exact issue you did. Did you ever end up finding a solution?
Hi, hoping someone can help me. My phone seems to have bricked itself. A few weeks ago i had CM6 on my phone then i reverted back to the stock rom from HTC. The phone worked fine for a few weeks then about a week ago i started having random data connection issues, yesterday the phone started resetting by itself, after the third or fourth reset the phone stopped booting at all. all i get now is the white HTC EVO 4G screen or the bootloader when i hold the volume down button.
Here are the version numbers on the bootloader screen.
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-2.02.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.09.01
Oct 14 2010, 19:14:47
i can only get windows to recognize the phone through usb by using the HBOOT USB option and installing the android bootloader interface driver. I don't really know how to use ADB and i'm not even sure if it is seeing the phone. All i want to do it get this back to official firmware.
any and all help is appreciated
thanks.
Well, it's not bricked if you get into that menu. Can you get into your recovery? If so, try wiping everything and reflashing the rom.
No i can't get into recovery, i even tried reapplying clockwork recovery trough there and all it does is install it, say it's installed ok then i reboot and try to go to recovery mode and it just goes to the white HTC EVO 4G screen
What version of hboot do you have?
*Nevermind* Apparently I can't read. xD
What root method did you use?
that's if i even installed it right.
i'm not sure if it even is rooted anymore because i had put the official firmware back on, when i had CM6 installed i used clockwork recovery and unrevoked
well if you were able to install a custom rom like cm6 then you are more then likely rooted. you say that you cant get into recovery? you should just try running the ruu.exe and returning to complete stock and then reroot if you want.
the official RUU.exe doesn't see the phone. when i connect hboot in the bootloader, device manager see's the phone as android bootloader interface and it i let the boot normally and let it crash at the evo 4g screen it show's up as "Qualcomm CDMA Technologies MSM" and doesn't have a driver. I am running Windows 7 x64
maybe you should try slashing the stock pc36img.zip maybe that will get you back on track.
Edit: this is the link to the thread with the stock pc36img.zip
http://forum.xda-developers.com/showthread.php?t=791019
and just for future reference. it is not that hard to do a search of the information that is needed. while i was here posting these things i found with the search all the info i hae given. just food for thought.
What caguirr4 said. With that file (or since you have s-off you can TRY getting a rom zip and renaming it to pc36img.zip) your phone will read it automatically when you boot using the volume down technique. That should at least get your phone to boot up and you can continue trouble shooting from there if you have more problems.
Remember: Conserve your battery! You don't want the juice to run out while the phone is in the middle of flashing something. THAT is how bricks are made.
i ran the update you gave me, the phone said that all the stages of the update were sucessful and asked me to reboot, i did so and now my phone won't power on and when i plug it into the wall it won't show any charging lights.
zerozr1 said:
i ran the update you gave me, the phone said that all the stages of the update were sucessful and asked me to reboot, i did so and now my phone won't power on and when i plug it into the wall it won't show any charging lights.
Click to expand...
Click to collapse
You ran the updates that who gave you? Various things were suggested on this thread.
sorry for not clarifying,i ran the original stock image that was linked to me by caguirr4 in post #9. According to the update it ran fine but after that the phone died when it had me reboot.
zerozr1 said:
sorry for not clarifying,i ran the original stock image that was linked to me by caguirr4 in post #9. According to the update it ran fine but after that the phone died when it had me reboot.
Click to expand...
Click to collapse
Ok, so you press the power button, and it does nothing? That doesn't sound good at all. Hopefully, your battery is just dead and the drivers for the USB port didn't install right. In which case, you need this:
http://forum.xda-developers.com/showthread.php?t=695243
Do you have any extra batteries you can try to make sure that battery isn't just dead?
I ended up taking it to a sprint service center, they tested the phone with thier own battery and the phone was dead. they are replacing the phone for me now. thanks you everyone for trying to help.
You could of just overwritten the ENG bootloader u had installed...
I am having the exact same problem. I can get to the bootloader but not recovery. Here's my specs
SUPERSONIC EVT2-2 SHIP S-ON
HBOOT-0.79.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.07.21
I had cyanogen 6.1.1 installed on it and it was was working fine. I just felt the thing vibrate and took it out of my pocket to see the "htc EVO 4G" screen and it just keeps rebooting unless I hold the volume button to get into the bootloader.
I REALLY don't want the stock firmware back on here and would like to avoid loosing root if possible.
I tried putting the PC36IMG.zip from here and at first it asked me if I wanted to flash it and after the first thing it restarted and now gives an error Main Version is older!
Update Fail!
Any ideas? I would really like to keep this phone.
Thanks,
Justin
I've tried basically everything I can think of. After attempting to flash the first PC36IMG.zip file I get the main version error for every other one.
Is there somewhere I can get the latest PC36IMG that will be newer and I can try to flash? At this point I don't really care if I lose root (if I haven't already) I just want my phone back.
embmicro said:
I've tried basically everything I can think of. After attempting to flash the first PC36IMG.zip file I get the main version error for every other one.
Is there somewhere I can get the latest PC36IMG that will be newer and I can try to flash? At this point I don't really care if I lose root (if I haven't already) I just want my phone back.
Click to expand...
Click to collapse
Just run the ruu.exe and get it back to stock.
Sent from my PC36100 using XDA App
I tried that. I even tried flashing the stock PC36IMG.zip (which flashed successfully) but I had the same problem. I finally gave up after like 8 hours of working on it and took it into Sprint. I am going to pick it up at 7. They said if they couldn't fix it they would give me a new one for $35 since I'm out of warranty which doesn't seem bad.
Okay so first off, let me just thank everyone who's willing to contribute to helping my issue ahead of time. I highly respect this community, and everything that everyone has done towards making android what it has become.
ANYWAY - I'm completely screwed, or so it seems. I cannot boot into anything, no ROM, no recovery. I've tried replacing the PC36IMG.zip on the root of my SD card. I've even downloaded the "RUU_SuperSonic_S_Sprint_WWE_3.30.651.3_Radio_2.15.00.09.01_NV_1.77_003_release_157088_signed.exe", and tried to start over completely, but even that did not work.
Whenever I try to restart my phone, or enter recovery from the HBOOT menu, I get a constant boot loop of the EVO white screen. Over and over, that's all it does. On my HBOOT menu I am showing:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.02.000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.09.01
Oct 14 2010, 19:14:47
I don't know what other options I have in order to restore my phone. Everything was working fine. I was running MIUI 12.3, with the stable CFS kernel. I woke up this morning, phone worked normally, then decided to randomly reboot. After that, it was over. I couldn't reboot into recovery, or simply reboot the phone.
If anyone can help out, it's greatly appreciated.
I'm not much help for that, but try this file:http://db.tt/AQItwCr
It's clock work mod recovery. If you can boot into hboot, you can flash that. Although, I'm assuming your rooted because you flashed mui*. So its pointless if your not rooted. Let me know what happens.
Sent From My HTC Evo 4G Using Tapa Talk Pro!
Rydah805 said:
I'm not much help for that, but try this file:http://db.tt/AQItwCr
It's clock work mod recovery. If you can boot into hboot, you can flash that. Although, I'm assuming your rooted because you flashed mui*. So its pointless if your not rooted. Let me know what happens.
Click to expand...
Click to collapse
I placed the .zip file on my SD card, and boot my phone into the HBOOT menu. It loaded the file, then put me back at the menu. I attempted to enter recovery > same issue. I'm placed at the white EVO 4G screen, and it keeps boot looping...
xxjuicymintxx said:
I placed the .zip file on my SD card, and boot my phone into the HBOOT menu. It loaded the file, then put me back at the menu. I attempted to enter recovery > same issue. I'm placed at the white EVO 4G screen, and it keeps boot looping...
Click to expand...
Click to collapse
Pretty fukkin weird. It shouldn't even boot up, it should just go into recovery.
What recovery were you running before?
Sent From My HTC Evo 4G Using Tapa Talk Pro!
Once you RUU back to stock, you should be able to reboot into the phone. Don't go into recovery because you don't have a recovery anymore. If the phone doesn't boot up into Sense, then the RUU you grabbed is corrupt and you need to re-download or grab from somewhere else. Your hboot is now showing S-ON because you basically unrooted your phone so there wouldn't be any recovery.
mizzos4 said:
Once you RUU back to stock, you should be able to reboot into the phone. Don't go into recovery because you don't have a recovery anymore. If the phone doesn't boot up into Sense, then the RUU you grabbed is corrupt and you need to re-download or grab from somewhere else. Your hboot is now showing S-ON because you basically unrooted your phone so there wouldn't be any recovery.
Click to expand...
Click to collapse
This is true. I didn't even think of that. You will need to reroot after that. Can somebody post a link for this guy? We can help each other out.
Sent From My HTC Evo 4G Using Tapa Talk Pro!
mizzos4 said:
Once you RUU back to stock, you should be able to reboot into the phone. Don't go into recovery because you don't have a recovery anymore. If the phone doesn't boot up into Sense, then the RUU you grabbed is corrupt and you need to re-download or grab from somewhere else. Your hboot is now showing S-ON because you basically unrooted your phone so there wouldn't be any recovery.
Click to expand...
Click to collapse
I just ran it again, and the install process completes. Everything seems to go smoothly. The phone reboots, and you see the HTC EVO 4G white screen, but then it just goes black, restarts, and repeats.
I'm still unsure as to why I can't seem to boot into anything. Don't know what caused this. I do a lot of reading in these forums, and I've never heard of anything like this. Did quite a bit of googling, trying to read up on others that might've 'bricked' their phone, etc.
Also, the RUU file that I used, I gained from this thread:
http://forum.xda-developers.com/showthread.php?t=840843
Try running the RUU a second time. Same thing happened to me with one of my EVOs, and I had to run the RUU twice to get it to work.
_MetalHead_ said:
Try running the RUU a second time. Same thing happened to me with one of my EVOs, and I had to run the RUU twice to get it to work.
Click to expand...
Click to collapse
I've tried this as well, with no success.
xxjuicymintxx said:
I've tried this as well, with no success.
Click to expand...
Click to collapse
Sucks.... ;(
Sent From My HTC Evo 4G Using Tapa Talk Pro!
Welp.... do you have TEP? If you file your claim with them tonight you should have your replacement by tomorrow.
_MetalHead_ said:
Welp.... do you have TEP? If you file your claim with them tonight you should have your replacement by tomorrow.
Click to expand...
Click to collapse
Haha, I'm not sure actually. I'm on a friends plan.
But, there's gotta be a way to get past the problem I'm having, with THIS Evo.
Shouldn't be a need to order a new one.
Hopefully someone in these forums can figure out a solution.
xxjuicymintxx said:
Okay so first off, let me just thank everyone who's willing to contribute to helping my issue ahead of time. I highly respect this community, and everything that everyone has done towards making android what it has become.
ANYWAY - I'm completely screwed, or so it seems. I cannot boot into anything, no ROM, no recovery. I've tried replacing the PC36IMG.zip on the root of my SD card. I've even downloaded the "RUU_SuperSonic_S_Sprint_WWE_3.30.651.3_Radio_2.15.00.09.01_NV_1.77_003_release_157088_signed.exe", and tried to start over completely, but even that did not work.
Whenever I try to restart my phone, or enter recovery from the HBOOT menu, I get a constant boot loop of the EVO white screen. Over and over, that's all it does. On my HBOOT menu I am showing:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.02.000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.09.01
Oct 14 2010, 19:14:47
I don't know what other options I have in order to restore my phone. Everything was working fine. I was running MIUI 12.3, with the stable CFS kernel. I woke up this morning, phone worked normally, then decided to randomly reboot. After that, it was over. I couldn't reboot into recovery, or simply reboot the phone.
If anyone can help out, it's greatly appreciated.
Click to expand...
Click to collapse
You were using an AOSP ROM with the new hboot? Didn't you have to use the HTC kernel?
xxjuicymintxx said:
Haha, I'm not sure actually. I'm on a friends plan.
But, there's gotta be a way to get past the problem I'm having, with THIS Evo.
Shouldn't be a need to order a new one.
Hopefully someone in these forums can figure out a solution.
Click to expand...
Click to collapse
I wish I could be of more help. Good luck and godspeed.
xHausx said:
You were using an AOSP ROM with the new hboot? Didn't you have to use the HTC kernel?
Click to expand...
Click to collapse
Yes, I was using MIUI 12.3, which is AOSP based. I don't think I had the new hboot until sometime after this problem started. One of the PC36IMG.zip's that I put on the root of my SD I believe was from somewhere in the new HBOOT Root thread on this forum, but I can't remember 100%.
Prior to that, I had the old HBOOT, I'm quite sure. I've never had a problem until. I've flashed plenty of ROMS, and recovery has always booted for me. MIUI wasn't giving me any issues, until earlier today. Randomly, POOF...it restarted...only, it boot looped. Didn't think it'd effect my recovery, though. I've had boot loop issues with other ROM's before, and have just booted into recovery, and solved the problem from there.
Who knows what happened to me earlier, or why, but it really is a pain. It's hard not having a phone. Especially when you've been blessed with an Evo!
xxjuicymintxx said:
Yes, I was using MIUI 12.3, which is AOSP based. I don't think I had the new hboot until sometime after this problem started. One of the PC36IMG.zip's that I put on the root of my SD I believe was from somewhere in the new HBOOT Root thread on this forum, but I can't remember 100%.
Prior to that, I had the old HBOOT, I'm quite sure. I've never had a problem until. I've flashed plenty of ROMS, and recovery has always booted for me. MIUI wasn't giving me any issues, until earlier today. Randomly, POOF...it restarted...only, it boot looped. Didn't think it'd effect my recovery, though. I've had boot loop issues with other ROM's before, and have just booted into recovery, and solved the problem from there.
Who knows what happened to me earlier, or why, but it really is a pain. It's hard not having a phone. Especially when you've been blessed with an Evo!
Click to expand...
Click to collapse
I think you screwed yourself by updating hboot. Haus* is working on an easy 2.02 hboot root.
Sent From My HTC Evo 4G Using Tapa Talk Pro!
xxjuicymintxx said:
Yes, I was using MIUI 12.3, which is AOSP based. I don't think I had the new hboot until sometime after this problem started. One of the PC36IMG.zip's that I put on the root of my SD I believe was from somewhere in the new HBOOT Root thread on this forum, but I can't remember 100%.
Prior to that, I had the old HBOOT, I'm quite sure. I've never had a problem until. I've flashed plenty of ROMS, and recovery has always booted for me. MIUI wasn't giving me any issues, until earlier today. Randomly, POOF...it restarted...only, it boot looped. Didn't think it'd effect my recovery, though. I've had boot loop issues with other ROM's before, and have just booted into recovery, and solved the problem from there.
Who knows what happened to me earlier, or why, but it really is a pain. It's hard not having a phone. Especially when you've been blessed with an Evo!
Click to expand...
Click to collapse
That's what it was, the 2.02 hboot is not compatible with older phones and vice versa. Is your NAND still unlocked? (shows S-OFF) If so you may be able to do something with it.
xHausx said:
That's what it was, the 2.02 hboot is not compatible with older phones and vice versa. Is your NAND still unlocked? (shows S-OFF) If so you may be able to do something with it.
Click to expand...
Click to collapse
No, it's not unlocked. It' showing S-ON.
&& this problem occurred BEFORE I was even running the hboot 2.02 --
I don't remember exactly what I had before, I believe it was the .76 hboot.
Everything was working perfectly fine.
I had just installed MIUI 12.3 a day earlier. Used it fine. Had everything set up the way I liked it. Went to sleep, woke up, phone still worked fine. Then it randomly reboot, and this problem started there.
The hboot 2.2 was only applied, I believe, when I put a PC36IMG.zip on my SD card root, that I had read about in a reply from someone on the 2.02 hboot thread.
Now it seems that I have only further screwed myself, apparently? idk.
I've tried running the latest RUU stock, to restore my phone to normal. NO luck.
Tried running it twice in a row, as per advice of someone earlier -- still no luck.
Endless reboots, no matter what. Yet, I can still get into the hboot menu. that's about it.
There's BOUND to be a way to fix this...
I can load PC36IMG.zip's ....but nothing else.
is there something that someone can package for me to revert back?
I have no idea, hence the reason I'm here.
HELP!
[and big thanks, of course!!]
Same thing happened to me. Lost recovery, and couldn't boot into rom. Just rebooted on splash screen over and over. Couldn't pull a logcat. Tried flashing recovery through fastboot, through bootloader, flashed renamed roms, the pc36img that I originally used from toasts 2part, etc. Nothing failed or threw errors. Only change I noted was that it reverted my custom splash screen to stock. Last ditch effort I ran an RUU with the phone in bootloader, which took a few tries but successfully "updated." Still couldn't boot into the OS. RUU restored me from engineering s-off back to ship s-on and I replaced it via warranty, $35 new phone on the spot.
Good luck, hope you manage to find something that works for you. After fastboot flashing failed I jumped on here and google hoping to find a fix, and searched for a week to no avail.
I've been running Warm 2.2 for a couple of months now, but lately I've been getting a lot of internet connection issues, today - I spent the entire day not being able to connect to 3G, don't know why so I figured I'd update the Radio,
Whatever that means..
managed to find updated versions on this website of the Radio, Wimax, Hboot and all those PIC, PICM, whatever it's called..
Rebooted to recovery, and flashed all the zip files, and now i'm STUCK there. Every time the phone restarts it just brings me back to the same old screen that says:
SUPERSONIC EVT2-2 SHIP S-ON
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Oct 15 2010
HBOOT
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
What do I do now? can I flash a new ROM using the USB cable? I don't think i have a micro sd card reader on me...
Anyway to fix this? I'd rather not wipe my device, but I can do it if I have to.
HELP
THANK YOU.
i might be wrong but i think your s-on means you lost root. but is you see the recovery option, i would go in there and try to restore a backup, hopefully you have one
Ahha.. a backup.. that would be nice :\
no backup here..
yoerz said:
I've been running Warm 2.2 for a couple of months now, but lately I've been getting a lot of internet connection issues, today - I spent the entire day not being able to connect to 3G, don't know why so I figured I'd update the Radio,
Whatever that means..
managed to find updated versions on this website of the Radio, Wimax, Hboot and all those PIC, PICM, whatever it's called..
Rebooted to recovery, and flashed all the zip files, and now i'm STUCK there. Every time the phone restarts it just brings me back to the same old screen that says:
SUPERSONIC EVT2-2 SHIP S-ON
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Oct 15 2010
HBOOT
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
What do I do now? can I flash a new ROM using the USB cable? I don't think i have a micro sd card reader on me...
Anyway to fix this? I'd rather not wipe my device, but I can do it if I have to.
HELP
THANK YOU.
Click to expand...
Click to collapse
Go to the following site http://forum.xda-developers.com/showthread.php?t=715485 and download the EVO_Radio, the WiMAX, PRI and NV "individually". Afterwards, connect your EVO to your computer and boot up. If you're taken to the bootloader screen like you stated in your post, select recovery from the list of options. Hopefully, you're using amon RA v2.3. Anyway, If you can get into recovery, select the MS-USB option. Your computer should detect your SD card shortly afterward. Copy the files you downloaded to your SD card. When complete, eject/unmount the SD card from your computer first and then push the power button on your EVO to unmount from within recovery. Now go to the wipe menu and wipe the cache & dalvik. After that, go to the flash menu and flash the PRI. You should reboot to the radio update screen. Be patient and DO NOT PULL THE BATTERY. When complete, you should reboot back into recovery. If you happen to reboot back to the bootloader, simply select recovery from the available options. Now flash the EVO_Radio. Like before, you will reboot to the radio update screen. Be patient and DO NOT PULL THE BATTERY. After some time, you should reboot back into recovery. If not, get to recovery from within the bootloader screen. Do the same thing for the NV and the WiMAX. You *may* have to reflash the HBOOT. Anyway, after you've updated your radios, reflash the recovery. I HIGHLY recommend RA v2.3 You can download the PC36IMG.zip file for it here: http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=PC36IMG.zip
After that, see if you can boot to your homescreen. If you can, great. If you cannot, try reflashing the rom. Remember, after flashing the radios and preparing to boot to your homescreen, you will appear to hang at the white EVO screen. Be patient and DO NOT PULL THE BATTERY. It will eventually clear. Hopefully, this will help you. Take care.
emcp422 said:
i might be wrong but i think your s-on means you lost root. /QUOTE]
Great catch!...... I totally missed seeing the "S-ON" in the OP's post and you're right, that usually means he is no longer rooted and need to re-root his device. OP, disregard my last post and RE-ROOT your device.
Click to expand...
Click to collapse
yoerz said:
I've been running Warm 2.2 for a couple of months now, but lately I've been getting a lot of internet connection issues, today - I spent the entire day not being able to connect to 3G, don't know why so I figured I'd update the Radio,
Whatever that means..
managed to find updated versions on this website of the Radio, Wimax, Hboot and all those PIC, PICM, whatever it's called..
Rebooted to recovery, and flashed all the zip files, and now i'm STUCK there. Every time the phone restarts it just brings me back to the same old screen that says:
SUPERSONIC EVT2-2 SHIP S-ON
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Oct 15 2010
HBOOT
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
What do I do now? can I flash a new ROM using the USB cable? I don't think i have a micro sd card reader on me...
Anyway to fix this? I'd rather not wipe my device, but I can do it if I have to.
HELP
THANK YOU.
Click to expand...
Click to collapse
Well, if you can get to the bootloader, it's unlikely that you're bricked. You *should* be able to recover here. The other guy is correct, since you're now S on, you lost root. Do you still have recovery? When you select 'recovery' from the bootloader, what result are you left with? (do you successfully boot to custom recovery, does it bring you back to the bootloader, or does it show you a black screen with a red triangle in it? If you still have recovery (I doubt you do, for some reason), then you should be able to flash the Unrevoked Forever S off tool, to set you back to S off. From that point, you should be able to flash a new rom.
However, I'm guessing that you lost recovery (for whatever reason), and you'll probably need to run an RUU, to try to flash the phone back to stock. From that point, you could re root again.
You can find an RUU here, http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu. Download the newest one, i believe it's the first on the page (3.70 software).
Edit: And about wiping your device, it seems as though that's already happened, ha. I don't think your stuff is coming back. Your only hope to get it back would be a nandroid backup, but you said you don't have one. We don't even know if you have recovery or not. Once you find that out, we'll know a lot more. If you're lucky, and still have recovery, it will be quick and easy for you to get back up and running.
Double Edit: OP. What recovery were you using? Did the radio flash seem to be successful, and then you just couldn't boot up afterward? Did you recieve any error messages when flashing it or anything like that?
Bricked means it won't even turn on...you just lost root. Do what the other posters said and please, read and take your time. You don't seem to have a firm grip on the whole rooting process.
You probably upgraded your hboot which is why you lost s-off and your phone won't boot. You can flash a kernel to get it to boot but you will need to get s-off back before you will be able to flash the radios.
Sent from my PC36100 using XDA Premium App
Just put pc36img.zip to root of sdcard and let it do its update then go from there.
Sent from my PC36100 using XDA Premium App
I've been looking through threads for hours and have tried a lot of what has been suggested. At first it just started randomly bootlooping ( white htc screen, restart). I then tried some guide on a thread that had me ADB then RUU, once that was all done It got to the white htc evo screen, turned black then vibrated 5 times and the green light started to flash. I can't get into the recovery menu, I click it and it just goes straight to white htc screen. I've flashed multiple PC36IMG's with different recoveries, with no luck.
My fuse is burnin low...
Supersonic EVT2-3 SHIP S-OFF
HBOOT-0.79.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-1.39.00.04.26
APR 14 2010, 15:41:34
*update-
I tried another RUU, a newer version.
http://forum.xda-developers.com/showthread.php?p=7529500#post7529500
Now it seems to be in a bootloop, no 5 vibrate+ flashing light though..
IxHaku said:
*update-
I tried another RUU, a newer version.
http://forum.xda-developers.com/showthread.php?p=7529500#post7529500
Now it seems to be in a bootloop, no 5 vibrate+ flashing light though..
Click to expand...
Click to collapse
OK......so basically you got no RECOVERY?....so when you boot into the BOOTLOADER to install the PC36IMG....does it recognize the image?.......and does it ask u to install and reboot?......we'll start there
What rom were you running? Some users have had a bootloop of death, no coming out of it, on CM7. I think it has happened on other AOSP roms as well, but you mainly see it on CM7 - probably because of the larger user base.
I have yet to see a solution for it, I think everyone else had to report it lost and pay the $100 deductible through insurance. The only hope is to keep running RUUs and hopefully one will stick.
(from... Evo/MIUI/Tapatalk)
Yeah I can see the image and to install and reboot.
And I was running CM7. FFFFFF I don't have insurance... Don't really want to take it to the sprint store with S-off.. So i guess ill keep trying to run RUU's... probably wont work though
IxHaku said:
Yeah I can see the image and to install and reboot.
And I was running CM7. FFFFFF I don't have insurance... Don't really want to take it to the sprint store with S-off.. So i guess ill keep trying to run RUU's... probably wont work though
Click to expand...
Click to collapse
If the pc RUU isn't working, trying using the same firmware RUU, but in PC36IMG file, which you flash in the bootloader.
@plainjane : For those that had the issue on CM7 [some users on MIUI], and they we chalked it up to bad nand blocks? But we still have no 'cure' for it.
teh roxxorz said:
If the pc RUU isn't working, trying using the same firmware RUU, but in PC36IMG file, which you flash in the bootloader.
@plainjane : For those that had the issue on CM7 [some users on MIUI], and they we chalked it up to bad nand blocks? But we still have no 'cure' for it.
Click to expand...
Click to collapse
Does it matter which RUU I use? (2.1,2.2)
reverepats said:
OK......so basically you got no RECOVERY?....so when you boot into the BOOTLOADER to install the PC36IMG....does it recognize the image?.......and does it ask u to install and reboot?......we'll start there
Click to expand...
Click to collapse
Exactly! Do not worry about flashing a RUU at this time. Click on amon RA in my signature to download the PC36IMG.zip for amon RA and place it on the root of your SD card. Remove any other file with that name. Boot onto the bootloader (simultaneously press the DOWN volume & power button until your device starts) and then follow the prompts to install. Installation should take no more than 10 seconds. Afterwards, enter your new recovery, connect your device to your computer, select the USB-MS option and then copy the contents of your SD card onto a folder on your computer. After that, select the USB-MS option again to disengage. Now go to the wipe menu and wipe EVERYTHING it. When you're done, download a fresh copy of the rom you want to flash and flash it or copy a nandroid backup to your SD card and restore it. Be patient, either way, with the initial bootup.
pecking & swyping from my EVO 4G (XDA Premium)
Alright so I tried everything I could... So I took it into a sprint store. Told the guy this happened when doing the most recent update. Right there he went into the bootloader menu, I thought I was screwed... but he didn't say anything about the S-OFF. Eventually I came back and they ordered me another one.. probably a refurb. He said it was going to be free, and I don't have insurance. Guess I got lucky.
Thanks everyone for the input.