Related
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.
Sounds like there weren't any ideas in Q&A for this one, and I haven't seen much in terms of not being able to access recovery, so here goes...
I was happily using CM7, and while reading through a Diablo III news page (hopefully it comes out soon ), my phone rebooted into a boot loop. Weird, but I figured at worst I would wipe data and reinstall a ROM. Unfortunately, I can't get into recovery any longer.
If I boot the phone normally, I see the white HTC splash screen for a few seconds, then it reboots. I can use HBOOT fine, but as soon as I try to reboot normally / boot into recovery / boot into Restore Factory Defaults, my phone will reset. Let me clarify...
Pull and replace battery
Boot into HBOOT (volume down + power)
Select Recovery
Phone reboots and reaches CWM Recovery 3 for about 1/2 second, not long enough for me to click anything
Phone reboots into boot loop
I've used HBOOT to flash to CWM Recovery 3.0.0.8, downgraded to the stock radio, run the 2.2 RUU. I'm still running up against the same boot loop problem.
I wouldn't be surprised if it was a hardware problem, but I'm anxious to hear if anyone has ideas to try first. Additionally, is there any way to restore to S-ON through HBOOT in case I need to bring this into a Verizon store? I have fastboot.exe that can recognize the device over USB while the device is in HBOOT, maybe this will help?
Thanks!
Current state: Ran 2.2 RUU, S-OFF, HBOOT-0.92.0000, AMOLED, 2.15.00.07.28 radio
Thanks again.
Had this exact issue while running cm7. First couple of from when it was crackflashers. I couldn't find anything to help or fix it. I got a new dinc because I can't afford to be without for long.
Good luck dude.
Sent from my ADR6300 using Tapatalk
Thanks for the note. Maybe my fate will be the same. Did you get any sympathy from Verizon?
Doesn't sound like there are even any suggestions using fastboot, lol. [crickets chirping]
Can you flash cwm 2.5.x and try? Not sure if it will help but worth a shot?
sent from a phone
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into bootloader (volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon
hope that helps
@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk
popasmurfn23 said:
@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
You are correct.
popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
phaze one said:
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon
Click to expand...
Click to collapse
Thanks for the replies.
I tried this method to flash back to the stock 2.2 image before I started this thread. That's what I meant by "I've used HBOOT to ... run the 2.2 RUU." The stock image seemed to install properly in HBOOT. I have evidence that it successfully went back to stock, since I get the original ! triangle graphic instead of CWM when I try to enter recovery from HBOOT. However, I only see the graphic pop up for a brief second before it reboots again. Trying to boot into recovery or the ROM itself still result in a reboot.
I cannot achieve S-ON without having access to recovery, at least there's no way that I've found to do it through HBOOT.
Any other thoughts? I think it's a hardware problem. It appears the phone is back to stock (except it's still S-OFF), but everything outside of HBOOT causes a boot loop. I stopped in at Verizon this afternoon and they'll be sending a new phone to arrive by Tuesday. At this point, it'd be nice to try all avenues of repair for the future benefit of others that run into this problem.
Probably bad memory chips on the phone. Since it happened all of a sudden during normal use it usually indicates hardware failure.
That is pretty much what I determined. Bad hardware. Sorry for your trouble but is nice to know I'm not the only person to ever have this. Also nice to know I didn't miss something that could've brought it back to life.
I filed an insurance claim. Figured since I have had it for years and never used it I'd take advantage.
Sent from my ADR6300 using Tapatalk
You can boot your phone like regular right? Just let it launch up or do you get loops?
Nevermind i see what ur saying. when i was flashing incorrect kernals i would get the same behavior from my phone. So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked
I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad
Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
If that doesn't work, (I'm assuming that you can boot the phone normally at this point) try re-rooting with the Unrevoked tool.
Then use Rom Manager to flash a newer Recovery (be sure to check Erase Previous Recovery under Settings). If that still doesn't work, I'll see about packaging an RUU in a PB31IMG.zip with a valid version of CWM as the recovery.img within that zip. I'm not sure about the practicality of this final option, but if it comes down to it, I'll attempt to package that up for you.
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Sent via my Incredible CM7 Gingerbread sorcery.
Crans said:
I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad
Click to expand...
Click to collapse
This would work if he could access CWM Recovery, but he can't, thus the issue.
I wonder if he could mount something from within hboot and replace the binary code for the recovery image with a bunch of zeroes and then try flashing another through hboot again.
Sent via my Incredible CM7 Gingerbread sorcery.
I was JUST about to post the same topic when I came across this. I have done the stock image restore, restored BACK to hboot 0.92, back to the most current INC radio, and have tried flashing CW3.0 and Amon_RA. Everything flashes fine but the boot loop continues and if I try to enter recovery, it lasts maybe one full second before rebooting again. The only thing that I can think of that would create this situation for me was that earlier I was trying to update the PRL via *228 on MIUI but the dialpad never popped up so I hung up.
popasmurfn23 said:
So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked
Click to expand...
Click to collapse
I'll take another crack at it, but I don't think I had gotten the wrong image. No worries though, it's easy enough to try again using the link on page 1 directly. Can't hurt, right ;-)
RegnierD said:
Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
Click to expand...
Click to collapse
Sure. Once again, worth a shot.
RegnierD said:
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Click to expand...
Click to collapse
Thanks for the sympathy . Like I mentioned, I visited the Verizon store and a new one is on its way... doesn't that mean that it doesn't matter (other than for science sake) whether this gets S-On or even fixed?
[waiting for flash of build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
It just seems unlikely that this is a problem with flashing the wrong recovery, or the wrong stock image, since booting into recovery and booting normally both exhibit the same behavior. If I could boot normally into recovery but not boot into a stock image, I would suspect that I had flashed the wrong image. Since both have the same problem, I think it might be something else.
[finished flashing build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
Same behavior. White htc Incredible splash screen -> darkness for a second (presumably while the ROM tries to boot) -> reboot.
Alternatively, HBOOT -> Recovery -> White htc Incredible screen -> Triangle / ! error screen for a half second -> reboot.
[finished flashing CWM 2.5.0.5]
Same behavior:
HBOOT -> Recovery -> White htc Incredible screen -> CWM recovery 2.5.0.5 for a half second (this confirms that it flashed properly) -> reboot.
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
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?
alright here is what happened. i was in twrp2 rc0.2 and was flashing a theme .zip made from the zipthemer app. i wiped cache and dalvik and flashed like normal and then after the flash it gave me an option to reboot system. i clicked it and it should have booted into my rom. instead it showed what would have been the white htc evo splash screen (mine is different) and then went to a black screen, vibrated 5 times, and i have the green notification light flashing.
i pulled the battery. booted into the bootloader and tried to go to recovery. ended up doing the same black screen vibrate etc. so i went back to bootloader to try to reflash the recovery since i still had the pc36img.zip on my sd. it scanned for the file looked like it read it but instead skipped past it and never gave me an option to flash the recovery. i tried multiple times, a series of battery pulls and no luck.
anyone got a clue as to whats up? im thinking i have a bad block and i heard of some jtag program or something to fix it but i have no idea what it is or how to use it.
p.s. yes i did google and i didn't find anything of much use... hell of a Christmas huh?
EDIT: odd. i have been rooted since january and now after this started it says im s-on. think i could use an ruu? the sd wont mount and im pretty sure they run from your sd so is there a way of using and ruu from a computer?
PhxkinMassacre said:
alright here is what happened. i was in twrp2 rc0.2 and was flashing a theme .zip made from the zipthemer app. i wiped cache and dalvik and flashed like normal and then after the flash it gave me an option to reboot system. i clicked it and it should have booted into my rom. instead it showed what would have been the white htc evo splash screen (mine is different) and then went to a black screen, vibrated 5 times, and i have the green notification light flashing.
i pulled the battery. booted into the bootloader and tried to go to recovery. ended up doing the same black screen vibrate etc. so i went back to bootloader to try to reflash the recovery since i still had the pc36img.zip on my sd. it scanned for the file looked like it read it but instead skipped past it and never gave me an option to flash the recovery. i tried multiple times, a series of battery pulls and no luck.
anyone got a clue as to whats up? im thinking i have a bad block and i heard of some jtag program or something to fix it but i have no idea what it is or how to use it.
p.s. yes i did google and i didn't find anything of much use... hell of a Christmas huh?
EDIT: odd. i have been rooted since january and now after this started it says im s-on. think i could use an ruu? the sd wont mount and im pretty sure they run from your sd so is there a way of using and ruu from a computer?
Click to expand...
Click to collapse
You can run a ruu through fastboot
Sent from my PC36100 using XDA App
evo4gnoob said:
You can run a ruu through fastboot
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
im downloading a 2.2 ruu. ill get back to you as to if it works or not
ok. i try to run the ruu and it gives me a main-version ERROR so i hit close and disconnect my phone. but then a window pops up saying update. so i plug in my phone again go to fastboot but then fastboot freezes and i cant navigate up and down with the volume keys. i then hit update but it just hangs at rebooting to bootloader and wont do anything...
If you can get back to Hboot, try to find a pc36img for the ruu you need and use the Ruu for the phone you have, not just any Ruu.
Use this site: http://goo-inside.me/supersonic/ruu to find your RUU
HipKat said:
If you can get back to Hboot, try to find a pc36img for the ruu you need and use the Ruu for the phone you have, not just any Ruu.
Use this site: http://goo-inside.me/supersonic/ruu to find your RUU
Click to expand...
Click to collapse
i tried the sdcard ruu for the latest gb update. it goes through. installs everything ok. but then when it reboots it goes back to the same 5 vibrates and black screen with flashing light.
after i did the sdcard ruu the windows ruu was able to go through unlike before. so i plugged in my phone it did its thing successfully. and again to no avail its still got the 5 vibrate etc.
and other options such as a block remap? i was running decks at the time which is based off cyanogen and i heard that cyanogen had been screwing blocks lately...
edit: i have no idea how a block remap would work... i just saw it in a thread that i believe you posted in like 3 days ago or so...
The 5 vibrates means it's in maintenance mode. (Diagnostics?)
I'm not sure what that means, exactly, but I don't think you're bricked, however, you DID say you were S-on, I believe, so if you are, try to re-root (look up root method for your hboot version) and them flash a recovery (Prefer Amon Ra) if it is successful.
If that works, wipe everything you can, except SD Card, wipe Dalvik Cache and Cache twice, then flash a ROM.
HipKat said:
The 5 vibrates means it's in maintenance mode. (Diagnostics?)
I'm not sure what that means, exactly, but I don't think you're bricked, however, you DID say you were S-on, I believe, so if you are, try to re-root (look up root method for your hboot version) and them flash a recovery (Prefer Amon Ra) if it is successful.
If that works, wipe everything you can, except SD Card, wipe Dalvik Cache and Cache twice, then flash a ROM.
Click to expand...
Click to collapse
He can't get sd to mount
Sent from my PC36100 using XDA App
ok. i went to a friends house and just let my evo chill out on my desk and when i got back it booted right up since i got 1 successful ruu in. now that being said it only stays up for about 3 minutes and then shuts off and goes into the vibrate and blink stage so im gonna try a logcat and see if i can get anything useful out of it. there is some hope here boys
ok. i have tried ruu 2 more times. i tried to root a few times. all to no avail. nothing works. i still turns on for only 3 minutes at a time and then goes blank and vibrates.
my device is less than year old but i didn't get a warranty so does anyone know what the deal is with getting a replacement? my bootloader says s-on and its on a stock rom due to the 934759345734 ruu's i did so they won't know i was rooted. so is there like a 1 year manufacturer warranty for this without having to break out $100?
Best bet is to just call Sprint and find out. They may just offer you a trade in.