Related
My Evo can't boot in android, it just turn on and restart after the Evo logo appear. And when I press power + volume down button I go in hboot mode, click on recovery and after that it's freeze with a picture of a phone , an "!" in a triangle.
I wonder If I can install recovery in this case or not? and how?
I've download PC36IMG.ZIP and supersonic recovery with sdk tool, so how anyone please help me, I need to try to install another ROM to sure it's hardware problem or ROM problem.
If you give me ten minutes I will attach it for you when I get to lappy.
Edit: Tada. Boot into the bootloader, select yes to update and then reboot.
teh roxxorz said:
If you give me ten minutes I will attach it for you when I get to lappy.
Edit: Tada. Boot into the bootloader, select yes to update and then reboot.
Click to expand...
Click to collapse
thank you for your help.
but is PC36IMG.zip needed to put into the sdcard, right?
no rename, just update?
I'l try and tell you the result.
btw, one more 'thank'!
kaizvn said:
...but is PC36IMG.zip needed to put into the sdcard, right?...
Click to expand...
Click to collapse
yes, put on sdcard, allow bootloader to read and update and you are good to go as far as recovery is concerned. good luck!
agentphantom said:
yes, put on sdcard, allow bootloader to read and update and you are good to go as far as recovery is concerned. good luck!
Click to expand...
Click to collapse
excuse me agentphantom, I've install go to bootloader and run that file, but I still can not access the recovery to flash rom.
anymore suggestion?
p/s: may I know what is the pc36IMG used for?
kaizvn said:
excuse me agentphantom, I've install go to bootloader and run that file, but I still can not access the recovery to flash rom.
anymore suggestion?
p/s: may I know what is the pc36IMG used for?
Click to expand...
Click to collapse
The PC36IMG is the system file the bootloader recognizes as like a system updater. And did you select update and then to reboot, once prompted?
teh roxxorz said:
The PC36IMG is the system file the bootloader recognizes as like a system updater. And did you select update and then to reboot, once prompted?
Click to expand...
Click to collapse
sorry but I don't see the "update" to choose.
I press power + volume down button => it take me to the hboot interface.
The menu there are : fastboot - recovery - clear storage - simlock - hboot usb.
5s later it start to run the PC36IMG file with no notification and log, very fast and disappear.
So, what would I do now?
kaizvn said:
sorry but I don't see the "update" to choose.
I press power + volume down button => it take me to the hboot interface.
The menu there are : fastboot - recovery - clear storage - simlock - hboot usb.
5s later it start to run the PC36IMG file with no notification and log, very fast and disappear.
So, what would I do now?
Click to expand...
Click to collapse
Two things to double check, to be sure that that the bootloader will recognize PC36IMG. 1) the PC36IMG must be named exactly that. It has to be capital letters, and you do not want it to say PC36IMG.zip, just PC36IMG. The phone automatically recognizes and labels it as a zip file. So if you named it PC36IMG.zip, it will ultimately be named PC36IMG.zip.zip, and will not be recognized.
2) Be sure that the PC36IMG is on the root (main directory) of your SD card, and not within any folders. It won't be recognized if it is in a folder.
If you make sure of those two things, then the bootloader should scan and find the PC36IMG, and instead of seeing it searching and the green lettering pop up, then disappear, you will see it ask you if you want to update, use volume up to select yes. Hope that helps you out.
Edit: And yes, I went to download the PC36IMG attatched above in this thread, and it is indeed labeled PC36IMG.zip. Rename it to PC36IMG (just remove the .zip) That should take care of it.
Also, I never saw this confirmed in the thread, but you were previously rooted and had a custom recovery prior to this problem, correct? And you are indeed s off at the bootloader?
k2buckley said:
Two things to double check, to be sure that that the bootloader will recognize PC36IMG. 1) the PC36IMG must be named exactly that. It has to be capital letters, and you do not want it to say PC36IMG.zip, just PC36IMG. The phone automatically recognizes and labels it as a zip file. So if you named it PC36IMG.zip, it will ultimately be named PC36IMG.zip.zip, and will not be recognized.
2) Be sure that the PC36IMG is on the root (main directory) of your SD card, and not within any folders. It won't be recognized if it is in a folder.
If you make sure of those two things, then the bootloader should scan and find the PC36IMG, and instead of seeing it searching and the green lettering pop up, then disappear, you will see it ask you if you want to update, use volume up to select yes. Hope that helps you out.
Edit: And yes, I went to download the PC36IMG attatched above in this thread, and it is indeed labeled PC36IMG.zip. Rename it to PC36IMG (just remove the .zip) That should take care of it.
Click to expand...
Click to collapse
I do in correctly, download the file at #2, put in root and go to bootloader.
I see the green line run on screen but havce no confirm form Update or not.
My phone is not rooted, no recovery, can't boot into android ROM, just start and restart at EVO logo.
Help me to install recovery to flash another ROM, I hope it will wake up my phone.
Okay so it was never rooted? What did you do right before your phone stopped working?
do nothing
this is my friend's phone.
He give me to try to flash a new rom for it.
but it's not root or recovery....
Okay so it wasn't working when he gave it to you right?
kaizvn said:
do nothing
this is my friend's phone.
He give me to try to flash a new rom for it.
but it's not root or recovery....
Click to expand...
Click to collapse
If you're s on and not rooted yet, I dont think you'll just be able to flash recovery. You need to root it first, then flash recovery. You should download an RUU or a PC36IMG of a factory rom. That will get you back to stock. From there, you can run Unrevoked to root it first though (you need to be rooted to flash roms). I will attatch a link with all of the PC36IMG's (you run from bootloader) and RUU's (you run from computer). You can use either method to get the phone back to stock condition (what I recommend). You will at least be able to boot then. From there you can decide if you want to root it and flash a ROM. Read up a bit more also, it will benefit you.
http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
k2buckley said:
If you're s on and not rooted yet, I dont think you'll just be able to flash recovery. You need to root it first, then flash recovery. You should download an RUU or a PC36IMG of a factory rom. That will get you back to stock. From there, you can run Unrevoked to root it first though (you need to be rooted to flash roms). I will attatch a link with all of the PC36IMG's (you run from bootloader) and RUU's (you run from computer). You can use either method to get the phone back to stock condition (what I recommend). You will at least be able to boot then. From there you can decide if you want to root it and flash a ROM. Read up a bit more also, it will benefit you.
http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
Click to expand...
Click to collapse
thank you very much!
I'll try anything to wake up it, I thing it's not the Hardware problem because the phone can start but can't go in the OS. But, mine is Sprint CDMA Evo, do you have any CDMA stock ROM for me to download and flash?
kaizvn said:
thank you very much!
I'll try anything to wake up it, I thing it's not the Hardware problem because the phone can start but can't go in the OS. But, mine is Sprint CDMA Evo, do you have any CDMA stock ROM for me to download and flash?
Click to expand...
Click to collapse
It's not a hardware problem, well, most likely not. Download a PC36IMG from the link I provided for you. It's hard to say which one you need, but try this one first. http://db.tt/gqTAPS1. That is a factory, unrooted ROM for the Evo. It is the latest software, 3.70. It may or may not work for you (you may need an older one, but not sure) What you need to do is download that file, rename it exactly PC36IMG. Put it on the main directory of your SD card. Shut the phone off completely. Hold Volume down and Power simultaneously until you reach the bootloader. At this point, the bootloader should scan the sd card, find the pc36img and ask you to update. You would then press volume up to select yes. Once it starts, let it run through its course. It should take a few minutes to complete, and you will see a couple different screens. whateveer you do, dont pull the battery while it's updating, and be sure you're battery has some charge on it, so it doesnt die in the process. I hope that helps. If that update successfully completes, the phone should be exactly how it came out of the box. Factory Rom. Good luck.
k2buckley said:
It's not a hardware problem, well, most likely not. Download a PC36IMG from the link I provided for you. It's hard to say which one you need, but try this one first. http://db.tt/gqTAPS1. That is a factory, unrooted ROM for the Evo. It is the latest software, 3.70. It may or may not work for you (you may need an older one, but not sure) What you need to do is download that file, rename it exactly PC36IMG. Put it on the main directory of your SD card. Shut the phone off completely. Hold Volume down and Power simultaneously until you reach the bootloader. At this point, the bootloader should scan the sd card, find the pc36img and ask you to update. You would then press volume up to select yes. Once it starts, let it run through its course. It should take a few minutes to complete, and you will see a couple different screens. whateveer you do, dont pull the battery while it's updating, and be sure you're battery has some charge on it, so it doesnt die in the process. I hope that helps. If that update successfully completes, the phone should be exactly how it came out of the box. Factory Rom. Good luck.
Click to expand...
Click to collapse
thank you k2, I'm downloading and will flash it A.S.A.P, I'll tell you the result.
Bit off topic but not really...
My EVO was rooted running cm7 with the latest clockwork gotten from and installed from rom manager.
Ran fine for about a week. Then right after pressing send on a replied email, reboot!
Crap I thought I was gonna have to retype the whole thing again...
Nope, it turns out the email had enough time to send but the phone never did reboot.
Just got itself in a loop. White HTC logo, vibrate, white htc logo,vibrate...
Could get to boot loader but when trying to access recovery I would go back into the same loop.
Kinda gave me the impression that the recovery partition was corrupted.
I was already out so I thought "what the hell" and took it to the sprint store. The tech was looking and working on the thing for literally over an hour on my phone (took about 3 hours from when I brought it in). Then finally the tech came out and asked for me. I was positive he had finally figured out it was rooted and was gonna tell me to screw off. Well, instead he said "honestly, I can't figure out what the heck is wrong with this thing, I'm just going to replace it for you,I'll be right back".
OK so now I'm expecting a refurbed phone with my battery and ad card shoved in it. He came back with a new EVO box...
Then he handed me the new one with the 8gb (I only had a 2 in mine) card and the original battery (I have the extended one). Then he said "your card battery charger and everything else is in the box".
SCORE! Haha sometime I actually like sprint...
Moral of the story: if all else fails take it to the store.s
Sent from my PC36100 using XDA Premium App
Dang that's awesome! yeah every store I've been to has been more than happy to just throw a new phone at me haha
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
jenic said:
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
Click to expand...
Click to collapse
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
RMarkwald said:
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
Click to expand...
Click to collapse
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
jenic said:
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
Click to expand...
Click to collapse
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Your concise post is most appreciated. I will do as you instruct and post results back here when finished.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Hit an unfortunate snag right away. fastboot (nor adb) is detecting the device. Screen is showing XC SHIP S-OFF as it should, it is in FASTBOOT USB mode and my computer detects the USB itself just fine.
dmesg output:
[346853.772041] usb 2-6: new high speed USB device using ehci_hcd and address 17
[346853.922917] usb 2-6: configuration #1 chosen from 1 choice
Click to expand...
Click to collapse
Thank you though that was a great suggestion! (Was very hopeful for a second there
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
RMarkwald said:
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
Click to expand...
Click to collapse
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
RMarkwald said:
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
Click to expand...
Click to collapse
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
cf9182 said:
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
Click to expand...
Click to collapse
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
jenic said:
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
Click to expand...
Click to collapse
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
jaba14 said:
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
Click to expand...
Click to collapse
That was definitely a laugh. Thank you I will see if I can get it replaced! I've been kinda just ignoring the fact that I do not have a phone all this time... Thankfully I had setup the phone to forward calls to google voice. It has been a lifesaver.
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 can get my Evo into the bootloader, but it won't allow me to reboot (it goes to the HTC Evo screen, then the screen goes dark and vibrates 5 times), I'll pull the battery and go back into the bootloader, I'll try to go into recovery and its does the same as rebooting. If someone can advise me what I can do to fix this, I would appreciate it. I messed up when I flashed an old Radio (2.15.00.07.21) Wont do that ever again :-(!
Specs: HBoot 2.10
Radio: 2.15.00.07.21
S-Off
3.29.651.5
I am a noob at this so please be nice, I also get the radio_v2 fail-pu when trying to update the phone, I'm not sure if i have the right PC36IMG file, thank you for your time!
raidernation said:
I can get my Evo into the bootloader, but it won't allow me to reboot (it goes to the HTC Evo screen, then the screen goes dark and vibrates 5 times), I'll pull the battery and go back into the bootloader, I'll try to go into recovery and its does the same as rebooting. If someone can advise me what I can do to fix this, I would appreciate it. I messed up when I flashed an old Radio (2.15.00.07.21) Wont do that ever again :-(!
Specs: HBoot 2.10
Radio: 2.15.00.07.21
S-Off
3.29.651.5
I am a noob at this so please be nice, I also get the radio_v2 fail-pu when trying to update the phone, I'm not sure if i have the right PC36IMG file, thank you for your time!
Click to expand...
Click to collapse
I don't even recognize that as any radio I've seen for the Evo. The last one ended in. 11.19 or something like that. The one before that ended with. 01.09 I believe. I don't recognize the one you used. Are you positive it was an Evo radio...? Your situation doesn't sound good though. I would try running an RUU from fastboot, but if you did flash a non evo radio, your probably in trouble...someone correct me if im wrong and that is indeed an evo radio.
Sent from my PC36100 using XDA App
Have you attempted running a 3.29 RUU?
http://www.shipped-roms.com/shipped/Supersonic/
Download the 3.29 version, boot your phone into the bootloader, select fastboot, connect to your pc. Once it shows fastboot usb on the phone, run the ruu exe.
k2buckley said:
I don't even recognize that as any radio I've seen for the Evo. The last one ended in. 11.19 or something like that. The one before that ended with. 01.09 I believe. I don't recognize the one you used. Are you positive it was an Evo radio...? Your situation doesn't sound good though. I would try running an RUU from fastboot, but if you did flash a non evo radio, your probably in trouble...someone correct me if im wrong and that is indeed an evo radio.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
It is, I just checked; its rolled back 3 versions from the 11.19 version.
Can't he place a PGimg.zip on root of his SD card and fastboot from his phone to return him to stock s -off ?
sent from a sweet paper weight.
ibsk8 said:
Can't he place a PGimg.zip on root of his SD card and fastboot from his phone to return him to stock s -off ?
sent from a sweet paper weight.
Click to expand...
Click to collapse
He can place a PC36IMG form of the RUU and do it that way, but if he wanted s-on, he'd need to flash the unrevoked s-on tool from recovery, which he can't get to.
raidernation said:
I can get my Evo into the bootloader, but it won't allow me to reboot (it goes to the HTC Evo screen, then the screen goes dark and vibrates 5 times), I'll pull the battery and go back into the bootloader, I'll try to go into recovery and its does the same as rebooting. If someone can advise me what I can do to fix this, I would appreciate it. I messed up when I flashed an old Radio (2.15.00.07.21) Wont do that ever again :-(!
Specs: HBoot 2.10
Radio: 2.15.00.07.21
S-Off
3.29.651.5
I am a noob at this so please be nice, I also get the radio_v2 fail-pu when trying to update the phone, I'm not sure if i have the right PC36IMG file, thank you for your time!
Click to expand...
Click to collapse
Try to basicaly reroot id try to hook to pc and run the hboot driver to fix the driver hopefully that will get you back into recovery. And id stick with flashin roms not radios its to risky. Did you back up your wimax keys?
Borked
Ok hi. So here's the deal:
My EVO can boot into bootloader, and it can get into recovery. Cool right? NO!!!
here's where the problem starts: I installed a corrupted ROMand of course, like every ROM, I wiped everything before flashing that one, and ended up not having a system to fall back on... And now the only thing I can do is get into the Bootloader and recovery.
The following issues I'm having, and the thins I have tried are:
1. I have tried putting the PC36IMG.ZIP at the root of the sd card.
- That didnt work though, and I figured that would only make sense, due to the fact that in recovery, it says "E: cant mount sd card"... So why/how would it work in bootloader?
2. It says "wrong image" when it tries to update the IMG file
3. I'm not a complete noob, I am willing to try ADB, I just dont know the commands to use :-( and IDK what to "push" or, even how to get the computer (PC, NOT a mac) to recognize the phone since it's... well, borked, I guess.
4. I' guessing that's the ONLY way to truly fix the phone and flash another ROM... is from the PC? But if so, HOW? Please help me.
Enmund said:
Ok hi. So here's the deal:
My EVO can boot into bootloader, and it can get into recovery. Cool right? NO!!!
here's where the problem starts: I installed a corrupted ROMand of course, like every ROM, I wiped everything before flashing that one, and ended up not having a system to fall back on... And now the only thing I can do is get into the Bootloader and recovery.
The following issues I'm having, and the thins I have tried are:
1. I have tried putting the PC36IMG.ZIP at the root of the sd card.
- That didnt work though, and I figured that would only make sense, due to the fact that in recovery, it says "E: cant mount sd card"... So why/how would it work in bootloader?
2. It says "wrong image" when it tries to update the IMG file
3. I'm not a complete noob, I am willing to try ADB, I just dont know the commands to use :-( and IDK what to "push" or, even how to get the computer (PC, NOT a mac) to recognize the phone since it's... well, borked, I guess.
4. I' guessing that's the ONLY way to truly fix the phone and flash another ROM... is from the PC? But if so, HOW? Please help me.
Click to expand...
Click to collapse
Make sure your sdcard is formatted FAT32.
Sent from my Galaxy Nexus using Tapatalk 2
fastboot oem enableqxdm 0
fastboot reboot
Use these commands through adb
Sent from my PC36100 using xda premium
That will remount your SD card
Sent from my PC36100 using xda premium
stevenskanse said:
fastboot oem enableqxdm 0
fastboot reboot
Use these commands through adb
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Hey that sounds like it would work, but my question is...How do I get the phone detected on the pc, if the phone cant read the sd card? You get what I'm saying? Like, what buttons do I press to enable the USB to be picked up on the computer? Thnks a lot man.
That happened to me. You have to hold BOTH the Vol+ and Vol- Buttons at the same time until it starts vibrating. You also have to connect it to the computer in order to make it vibrate.
EDIT: You have to take out the battery while plugged in. Sorry for forgetting
When u put the PC36IMG.zip (named exactly like that) on your SD card, are u sure it wasn't named PC36IMG.zip.zip or any other variant of the correct name? Use a card adapter to put file in main folder of SD then put it back in phone. Then boot to bootloader n test. What recovery did u have installed when you tried to flash a radio? Clockwork will not flash radios
{ParanoiA} said:
When u put the PC36IMG.zip (named exactly like that) on your SD card, are u sure it wasn't named PC36IMG.zip.zip or any other variant of the correct name? Use a card adapter to put file in main folder of SD then put it back in phone. Then boot to bootloader n test. What recovery did u have installed when you tried to flash a radio? Clockwork will not flash radios
Click to expand...
Click to collapse
Yes I did... It says wrong image
Ok I need some help, I unrooted my phone because I had to take into sprint to get a new screen. The problem is this. After unrooting the Evo it constantly reboots itself and on top of that it will not recognize the SD card. Any ideas on how to fix this.
First, being that the phone is no longer rooted, take it to Sprint and have them troubleshoot it. If you don't want to do that, you can try booting into recovery to see if the card will mount there.
dougjamal said:
First, being that the phone is no longer rooted, take it to Sprint and have them troubleshoot it. If you don't want to do that, you can try booting into recovery to see if the card will mount there.
Click to expand...
Click to collapse
If the phone is *properly* unrooted (s-on zip, RUU) there shouldn't be a recovery to boot into.
OP, did you unroot the way I mentioned?
(from... Evo/MIUI/Tapatalk)
plainjane said:
If the phone is *properly* unrooted (s-on zip, RUU) there shouldn't be a recovery to boot into.
OP, did you unroot the way I mentioned?
(from... Evo/MIUI/Tapatalk)
Click to expand...
Click to collapse
I was under the impression that there is a stock recovery.
dougjamal said:
I was under the impression that there is a stock recovery.
Click to expand...
Click to collapse
From what I understand, the stock recovery is no recovery. On a brand new not rooted phone, if you try to go into recovery, you get the black screen with red triangle.
At least that's what I've always heard. The Evo I had before this one was freaking out - it had never been rooted. I went into the bootloader to clear storage and out of curiosity chose recovery afterwards. I got the no recovery screen.
Running the RUU should give you the same result.
(from... Evo/MIUI/Tapatalk)
plainjane said:
From what I understand, the stock recovery is no recovery. On a brand new not rooted phone, if you try to go into recovery, you get the black screen with red triangle.
At least that's what I've always heard. The Evo I had before this one was freaking out - it had never been rooted. I went into the bootloader to clear storage and out of curiosity chose recovery afterwards. I got the no recovery screen.
Running the RUU should give you the same result.
(from... Evo/MIUI/Tapatalk)
Click to expand...
Click to collapse
Oh Okay. Thanks for clearing that up for me. Take care, my friend...
Thanks for the info, I did unroot it the way you mentioned in the thread. And it is unrooted the s zip is on and when I try to get into recovery I do get the red triangle warning. So I guess my best bet is to take it to Sprint. Is there a way to root the phone thru bootloader or do I have to have the phone turned on to root it. As far as the SD card issue any ideas.
killwrath said:
Thanks for the info, I did unroot it the way you mentioned in the thread. And it is unrooted the s zip is on and when I try to get into recovery I do get the red triangle warning. So I guess my best bet is to take it to Sprint. Is there a way to root the phone thru bootloader or do I have to have the phone turned on to root it. As far as the SD card issue any ideas.
Click to expand...
Click to collapse
so you didnt run an RUU? Did you just flash a PC36IMG.zip from the bootloader? The problem with that method is that you dont know what all was in the zip, or if it included everything. Theres a lot of PC36IMG.zip's out there that all serve different purposes. Go download the official RUU on your computer, plug your phone in and boot into fastboot (or just bootloader, not sure), wait for the process to finish, and your phone will be back to stock 100% no matter what. This is what sprint will do to restore a phone, so its official.
Ok one more quick question, how do I get my computer to recognize my phone after I plug it in. I found the official RUU and when I plugged my phone in and booted to bootloader the computer did not find it. As a result running the RUU did nothing. I went thru all the warning screens and then when it was searching for the phone and then gave me a warning that no phone was connected. So if I could get the phone connected to the computer then I am sure I can run the RUU and see if that helps. Any ideas?
killwrath said:
Ok one more quick question, how do I get my computer to recognize my phone after I plug it in. I found the official RUU and when I plugged my phone in and booted to bootloader the computer did not find it. As a result running the RUU did nothing. I went thru all the warning screens and then when it was searching for the phone and then gave me a warning that no phone was connected. So if I could get the phone connected to the computer then I am sure I can run the RUU and see if that helps. Any ideas?
Click to expand...
Click to collapse
check my guide have a link to the ruu you need just place it PC36IMG.ZIP on SD card and run get into boot loader mode and there you go.
Ok the phone wins. It is going back to sprint to see what they can do. All of your suggestions have been great, thanks for them. I just cant get the computer to recognize the phone when its plugged in. And the phone cant detect the SD card even in bootloader. And it will only charge when its is turned off. DAMN YOU TECHNOLOGY!!! hahahaha
Again thanks a ton for all your help. Warms the heart to know there are lots of fellow phone hackers willing to help out.
First thing is Thank You Everyone for all your help and suggestions.
Here is the update. The phone won and I had to take it to Sprint. And much to my suprise and honestly relief, they could not get the software reinstalled, it was stuck in a boot cycle is what they said. Ok if you say so. So they are going to send me a new phone. WOO HOO!!!!!
Thanks again for everything. Guess I get to try out Auto Root this time.
Yeah Rooting.