I figured this was a long shot, but one of my RHOD's is stuck on the white HTC screen (the first one that pops up after booting).
Now I can get to the tri-color boot screen. I have been able to flash via USB and SD, however no matter what I flash it fails.
The device does have hSPL applied. I have tried flashing EnergyROM, just radio's, stock ROM's (which includes radio, ROM, etc... all of it!), task29... nothing seems to actually fix it. Every time it just goes back to hanging on that white HTC logo.
So any ideas? Anything I haven't tried? I am hoping it's not bricked since it does turn on, and I can flash... Thanks!!
Does it give any errors when it fails to flash? Have you tried another SD card? Have you formatted your SD card with the HP tool? Have you tried sacrificing a demon goat? http://www.youtube.com/watch?v=NQbxmXilRew
Your nand memory might be toast if even task 29 fails. All it does is wipe the nand memory.
This is a real longshot, but it looks like you have tried everything else. Can you re-flash HardSPL? Or maybe try to downgrade hSPL and then upgrade again?
I really want to help (even if giving arrrghhh advice seems so backwards!) but can't think of much else you haven't tried.
You have CDMA right? so no SIM... On my GSM I would try to boot with SIM inserted to see if it makes any difference...
Sorry, if I have any major brain waves I'll be back.
Oh! Can you flash a NAND Android ROM? I read about some people with HD2's that could flash android/WP7 but everytime they flashed WM it would freeze at the white screen.
wizardknight said:
Does it give any errors when it fails to flash? Have you tried another SD card? Have you formatted your SD card with the HP tool? Have you tried sacrificing a demon goat? http://www.youtube.com/watch?v=NQbxmXilRew
Your nand memory might be toast if even task 29 fails. All it does is wipe the nand memory.
Click to expand...
Click to collapse
This was a tester phone, wasn't even used that much... But I guess the guy before me could've burned it out.
Also, I see I wasn't so clear in my OP. No errors, everything flashes fine. task29 flashes fine. ROM's flash fine. Radio's as well... everything seems great until you try to boot the damned thing.
Not sure what vid that is, I'll check it out later. Thanks.
Caldair said:
This is a real longshot, but it looks like you have tried everything else. Can you re-flash HardSPL? Or maybe try to downgrade hSPL and then upgrade again?
I really want to help (even if giving arrrghhh advice seems so backwards!) but can't think of much else you haven't tried.
You have CDMA right? so no SIM... On my GSM I would try to boot with SIM inserted to see if it makes any difference...
Sorry, if I have any major brain waves I'll be back.
Oh! Can you flash a NAND Android ROM? I read about some people with HD2's that could flash android/WP7 but everytime they flashed WM it would freeze at the white screen.
Click to expand...
Click to collapse
Well thanks for at least tryin . I haven't tried messing with hSPL, but I guess since that's now semi-open I can try without much risk of not being able to go back (used to be a big issue...)
I do have CDMA, but these are 'world-phones'. So they have SIM slots... that's a good point, maybe I should try without the SIM - as my 'main' TP2 doesn't have a SIM and has never had such problems. This one came with the Sprint SIM which I've never used either, but for whatever reason I've kept it around .
I'm pretty sure I tried putting LK on the phone, and the same result. It's been a while since I've tried to flash anything on it tho, so perhaps I'll try that again.
Thanks for the advice, I'll get back to you .
Does it just sit at the loading screen or will it not go beyond the tricolor screen?
It's a long shot, but I have a flash that does nothing but change the white htc screen to something else. It is small. Might be worth a try to see if that works.
I have heard of the sim chips causing issues, but have never experienced them myself. No harm in pulling it out of there.
wizardknight said:
Does it just sit at the loading screen or will it not go beyond the tricolor screen?
It's a long shot, but I have a flash that does nothing but change the white htc screen to something else. It is small. Might be worth a try to see if that works.
I have heard of the sim chips causing issues, but have never experienced them myself. No harm in pulling it out of there.
Click to expand...
Click to collapse
Yea, when I task29'd I think it changed this screen to say Touch Pro2 at one point... Stock ROM flash changed it back to the white HTC logo.
I can always make it past the tri-color screen - however, I never get past the 'initial' boot screen. I'll try just flashing that just for grins tonight.
What I posted will not put any OS on there. It will let you see if you are writing to the nand at all though. So if you see a new boot flash screen, you are getting somewhere.
... another longshot. After you flash a rom etc. and it fails to boot perform a hardware hard-reset. With the device turned off, press and hold the TALK, END and POWER then release and press VOL UP when you see the message.
I don't know, this probably won't help since I can't see anything surviving Task29... but I'm grasping at straws at this point...
OK, sorry that took so long... I've been slackin
Flashed the new boot logo, looks cool... but still frozen. Then I flashed EnergyROM, no dice. Did a hard reset (thanks Caldair forgot about that key sequence)... still no dice.
I guess I'll try relocking, can't hurt at this point.
Edit - wow, relocking seems to have done the trick. It downgraded the bootloader, and then the stock ROM updated it. I am now getting the red text at the bottom of the first boot screen... It seems to be proceeding to WinMo! Unbricked!!
arrrghhh said:
OK, sorry that took so long... I've been slackin
Flashed the new boot logo, looks cool... but still frozen. Then I flashed EnergyROM, no dice. Did a hard reset (thanks Caldair forgot about that key sequence)... still no dice.
I guess I'll try relocking, can't hurt at this point.
Edit - wow, relocking seems to have done the trick. It downgraded the bootloader, and then the stock ROM updated it. I am now getting the red text at the bottom of the first boot screen... It seems to be proceeding to WinMo! Unbricked!!
Click to expand...
Click to collapse
Sweet deal.
arrrghhh said:
... getting the red text at the bottom of the first boot screen... It seems to be proceeding to WinMo! Unbricked!!
Click to expand...
Click to collapse
Yeah Man! Congrats! Seeing that ^^ has got to be one of the sweetest feelings, resurrecting a device that you've written off as dead. Love it!
arrrghhh said:
Edit - wow, relocking seems to have done the trick. It downgraded the bootloader, and then the stock ROM updated it. I am now getting the red text at the bottom of the first boot screen... It seems to be proceeding to WinMo! Unbricked!!
Click to expand...
Click to collapse
Nice and Yay!! Good job! =]
Related
First time I tried flashing I got a error 270. And that was after running the SDA app unlock. So then I tried using the USPL error 270 fix. The problem I'm having Is right when it says "the screen should turn almost black". The screen turns white. At that point active sync doesn't recongnize the phone anymore, and the phone is stuck unresponsive, with a white screen.
So heres a few questions to make sure I'm doing this right.
When I run the sda unlock. Should the phone respond in any way? When I press the ok button I get a instant verification that the phone is unlocked. The phones screen doesn't light up or anything of the sorts. It almost seems like nothing happened.
When you say reboot (yeah this is a dumb question!) I'm just turning the phone off, and then turning it back on again. Is the correct way to do it?
It is a brand new excalibur I'm working with. The one with the all black face. I just figured I should throw that in there in case there was any little difference that would be causing me problems.
I can't wait to get this phone flashed! Looking at all the tweaks and tricks and not being able to try them out is killing me!
oilspot said:
First time I tried flashing I got a error 270. And that was after running the SDA app unlock. So then I tried using the USPL error 270 fix. The problem I'm having Is right when it says "the screen should turn almost black". The screen turns white. At that point active sync doesn't recongnize the phone anymore, and the phone is stuck unresponsive, with a white screen.
So heres a few questions to make sure I'm doing this right.
When I run the sda unlock. Should the phone respond in any way? When I press the ok button I get a instant verification that the phone is unlocked. The phones screen doesn't light up or anything of the sorts. It almost seems like nothing happened.
When you say reboot (yeah this is a dumb question!) I'm just turning the phone off, and then turning it back on again. Is the correct way to do it?
It is a brand new excalibur I'm working with. The one with the all black face. I just figured I should throw that in there in case there was any little difference that would be causing me problems.
I can't wait to get this phone flashed! Looking at all the tweaks and tricks and not being able to try them out is killing me!
Click to expand...
Click to collapse
Yes rebooting is when your phone turns off and back on. Soft reset is when you power the phone off and power it back on.
Did you follow these instructions to T?http://forum.xda-developers.com/showthread.php?t=415225
http://forum.xda-developers.com/showpost.php?p=2807194&postcount=485
stylez said:
http://forum.xda-developers.com/showpost.php?p=2807194&postcount=485
Click to expand...
Click to collapse
ran both, failed at 0% this time. Left the phone stuck with the tri colored screen. But, in that thread, it says I may have to try it a few times. I'll give it another shot and see what happens.
really wish rebooting the phone was quicker!
tried again. phone locked up and didn't want to connect with active sync.
overall I've tried several times. Is it normal to have this many problems? I'm starting to get frustrated!
Don't get me wrong. I really appreciate all the info and help I'm getting with this. The frustration is just not being able to make it work.
oilspot said:
ran both, failed at 0% this time. Left the phone stuck with the tri colored screen. But, in that thread, it says I may have to try it a few times. I'll give it another shot and see what happens.
really wish rebooting the phone was quicker!
tried again. phone locked up and didn't want to connect with active sync.
overall I've tried several times. Is it normal to have this many problems? I'm starting to get frustrated!
Don't get me wrong. I really appreciate all the info and help I'm getting with this. The frustration is just not being able to make it work.
Click to expand...
Click to collapse
No it normally doesn't give you that many problems, except if you made a mistake flashing. I flashed three times within my first week before I found the rom I liked, and never had a single problem. See what I did was print all the instructions on flashing and had them on my lap while I was flashing and double checking every step before going to the next. Is very important that you follow the steps to a T so nothing like this happens. If you can get the bootloader screen , I would suggest to reinstall the official 6.0 rom, get the phone back to factory, and then try again to flash to 6.1.
Do you know the bootloader procedure?
I'm following these instructions... to a T.
http://forum.xda-developers.com/showthread.php?t=415225
I'm not sure if you would call that a bootloader procedure? Is there something else I need to know how to do?
I've had it completely lock up during the flashing process, and have had to pull the battery to get the phone to work again. The phone works just like normal after I've had to do that. Are you saying that I need to re flash the stock rom before I can flash it to a different one?
oilspot said:
I'm following these instructions... to a T.
http://forum.xda-developers.com/showthread.php?t=415225
I'm not sure if you would call that a bootloader procedure? Is there something else I need to know how to do?
I've had it completely lock up during the flashing process, and have had to pull the battery to get the phone to work again. The phone works just like normal after I've had to do that. Are you saying that I need to re flash the stock rom before I can flash it to a different one?
Click to expand...
Click to collapse
The phone is working normally now? so nothing happened? are you still on the 6.0 and everything is operational? If you are then you don't need the bootloader.
yeah the phone works fine. No glitches.
Got frustrated with it yesterday so I just left it. Going to try again today.
Does it make any differance that it's the new black faced excalibur? I read that not much changed except the color.
WOO-HOO!
I got it! Did the same things I did before, for some reason this time it worked.
Have only had a few minutes playing with it but so far I love it! I was dissapointed with the lack of configuration in the "stock" OS. I've already got everything moved around just where I want it.
Thank you soo much for the help! You guys are great!
oilspot said:
WOO-HOO!
I got it! Did the same things I did before, for some reason this time it worked.
Have only had a few minutes playing with it but so far I love it! I was dissapointed with the lack of configuration in the "stock" OS. I've already got everything moved around just where I want it.
Thank you soo much for the help! You guys are great!
Click to expand...
Click to collapse
Awesome, glad you figured it out. Enjoy.
Ok so my GF's incredible was working just fine, had been with the same rom for a month with no problems.
One hour ago, it just rebooted out of nowhere. Now, it wont boot to rom, it boots to hboot, try recovery and it shows CWM for 1 second and reboots again, tried factory reset, or clear storage, and it reboots and the same as CWM, it shows 1 second and reboots.
It seems like if everytime it loads the kernel, any kernel, recovery or rom one it reboots.
Any thoughts? Oh, also, I flashed the "build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip" file it flashed fine, rebooted and again with the bootloop. It just shows the white Incredible screen and reboots!
Any suggestions are appriciated
pmcnano said:
Ok so my GF's incredible was working just fine, had been with the same rom for a month with no problems.
One hour ago, it just rebooted out of nowhere. Now, it wont boot to rom, it boots to hboot, try recovery and it shows CWM for 1 second and reboots again, tried factory reset, or clear storage, and it reboots and the same as CWM, it shows 1 second and reboots.
It seems like if everytime it loads the kernel, any kernel, recovery or rom one it reboots.
Any thoughts? Oh, also, I flashed the "build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip" file it flashed fine, rebooted and again with the bootloop. It just shows the white Incredible screen and reboots!
Any suggestions are appriciated
Click to expand...
Click to collapse
when you say it shows the white screen and it reboots..... what do you mean be the white splash screen always shows up first then it boots.... are you saying it bootloops [which means it starts the whole process over again]? and im asuming you flashed an RUU Through hboot..... how long did you let it try and boot because it takes awhile after flashing back to stock...... give me a liittl more info and i might be able to help.....
Yea the white splash screen that always shows up. IT reboots and it goes to the white splash screen again, and again...In fact wait me a second i will take a video of everything! But, yea after flashing the RUU it does exactly the same, in fact I just flashed the RUU again via fastboot and the same. I will record it anyway, one second.
Lol, and on my evo Qik is force closing, nice! Well, Sorry couldnt record but yea,
normalboot-->white inc screen-->black screen--->reboot
voldownboot---hboot--->recovery--->recovery screen --1sec-->reboot
I'd try to RUU back to stock and re-root.
Sent from my ADR6300 using XDA Premium App
like I said, done the RUU didnt work. !
pmcnano said:
Yea the white splash screen that always shows up. IT reboots and it goes to the white splash screen again, and again...In fact wait me a second i will take a video of everything! But, yea after flashing the RUU it does exactly the same, in fact I just flashed the RUU again via fastboot and the same. I will record it anyway, one second.
Lol, and on my evo Qik is force closing, nice! Well, Sorry couldnt record but yea,
normalboot-->white inc screen-->black screen--->reboot
voldownboot---hboot--->recovery--->recovery screen --1sec-->reboot
Click to expand...
Click to collapse
are you positive the ruu flashed..... when it loaded up did it ask you if you want to update vol + and then it flashes stuff for about 5 mins until it finialy says its done and asks you if you want to reboot....
yep! I did, I even flashed it via fastboot again, same thing happens :S
pmcnano said:
yep! I did, I even flashed it via fastboot again, same thing happens :S
Click to expand...
Click to collapse
Bro it sounds like hardware problem to me.... the only other thing i can think of is to try and get into recovery with adb and try to wipe do a wipe and see what happens.... but if that dont work doug piston is the best around at getting the incredible restored ill give you link to his site if you cant get him tonight he'll answer in the morning
http://dougpiston.com/
you can also talk to him at Droid Forums good luck let me know what it was please and hit that thanks button if i helped
haha yes you did, I really think its a HW problem too
Hey bro let me know what you figure out so I can help people in the future
Sent from my Incredible using XDA App
Ok, finally had a chance to actually read your thread. Looks like you've tried just about everything I suggested via twitter already.
Oddly enough I had someone from this forum contact me about a similar situation about a week ago. If I remember correctly we tried everything and came to the same reboot. He fixed it though we weren't sure on the full solution show I'll discribe what he did and you can give it a shot.
Flash the RUU through Hboot one more time, once it is complete it will ask if you would like to reboot, select no. Once it gets back into hboot pull the battery wait a minute and re-insert the battery leave the device plugged in and powered off for about an hour. Come back and try to reboot.
Like I said I have no clue on how this method recovered the device but it did. It makes no logical sense to me but its worth a shot.
Thanks for all your help doug, Will try in a sec, was playing soccer!
Will let you know from twitter
doug piston said:
Ok, finally had a chance to actually read your thread. Looks like you've tried just about everything I suggested via twitter already.
Oddly enough I had someone from this forum contact me about a similar situation about a week ago. If I remember correctly we tried everything and came to the same reboot. He fixed it though we weren't sure on the full solution show I'll discribe what he did and you can give it a shot.
Flash the RUU through Hboot one more time, once it is complete it will ask if you would like to reboot, select no. Once it gets back into hboot pull the battery wait a minute and re-insert the battery leave the device plugged in and powered off for about an hour. Come back and try to reboot.
Like I said I have no clue on how this method recovered the device but it did. It makes no logical sense to me but its worth a shot.
Click to expand...
Click to collapse
Stuck in a similiar situation. I tried the above instruction and the device booted. I still do not have a working recovery .Tried to root several times but my device will only boot cleanly once and I have to pull the battery and wait atleast ten minutes but nothing works where can I find instructions on wiping thru adb
I think that the nand is ****ed up or i dont know D: mine didnt boot
Hi Guys, Idon't post too often as you can see, but I have had a great time rooting my Evo and learning from all the awesome members here. I do my research, and until now I have not run across a problem I could not fix on my own.
I am running CM7 nightly 26, and out of nowhere today, my phone rebooted and proceeded to get stuck in a boot loop. I am not surprised by that kind of thing at this point, but for the first time ever, I was not able to boot into recovery. If I select that option from the boot loader, I just get the white Evo 4G screen and it proceeds to boot loop.
Ok, I thought, maybe my recovery was corrupted somehow, so I pull the SD card and put Amon Ra 2.3 in the root directory and named it PC36IMG.zip and flashed it. No good. I still can't get into recovery.
I also tried downloading the stock (rooted) sprint ROM, putting on the root of my SD card and naming it PC36IMG.zip. After the bootloader detects it and the progress bar finishes, it says "Parsing PC36IMG.zip", and then it just takes me back to the bootloader main menu without an option to flash anything.
Also, is there a way to get S-ON back (with my only access being to the bootloader) in the event that I have to take it in? The alternative would be to drown it or smash it (as a last resort)
Any ideas? Thanks very much in advance for any help!
Westibone said:
Hi Guys, Idon't post too often as you can see, but I have had a great time rooting my Evo and learning from all the awesome members here. I do my research, and until now I have not run across a problem I could not fix on my own.
I am running CM7 nightly 26, and out of nowhere today, my phone rebooted and proceeded to get stuck in a boot loop. I am not surprised by that kind of thing at this point, but for the first time ever, I was not able to boot into recovery. If I select that option from the boot loader, I just get the white Evo 4G screen and it proceeds to boot loop.
Ok, I thought, maybe my recovery was corrupted somehow, so I pull the SD card and put Amon Ra 2.3 in the root directory and named it PC36IMG.zip and flashed it. No good. I still can't get into recovery.
I also tried downloading the stock (rooted) sprint ROM, putting on the root of my SD card and naming it PC36IMG.zip. After the bootloader detects it and the progress bar finishes, it says "Parsing PC36IMG.zip", and then it just takes me back to the bootloader main menu without an option to flash anything.
Also, is there a way to get S-ON back (with my only access being to the bootloader) in the event that I have to take it in? The alternative would be to drown it or smash it (as a last resort)
Any ideas? Thanks very much in advance for any help!
Click to expand...
Click to collapse
Many of us are racking our brains trying to figure out what is causing this situation. Everyone who are experiencing this were using CM7, like you, and it happened to of nowhere and for no known reason. I don't think anyone has figured out a workaround, but I could be wrong. I haven't ready through the forums today regarding this issue. Just know that you are not alone, my friend....
Well, it doesn't look too hopeful from what I have seen so far, but thanks for the support. It's good to know that I am not alone.
If you can still access the bootloader, you should still be able to run an RUU through fastboot.
It happened to me, I was one of the first on the forum it happened to, in January. Was never able to fix it, you could spend a loonnngggg time, and get no results. If you search for my threads you can see the ones I started about the subject.
Long story short, I was never able to fix the problem or get S-On. However by doing a battery pull while flashing a rom with a different radio, during the radio installation, I bricked my phone to the point that it wouldn't even turn on. So thats basically your only way out that I know of. You'll have to perform the battery pull upwards 20 times probably before you get the phone to fully brick.
I'm on CM7 nightlies. What are the HW specs of those having these problems? I thought it was due to CWM but there have been some on RA experiencing this too. Just wondering if this is more specific to the newer HW builds/hboots or occurs with all phones.
My Evo is hardware version 003 for what it's worth.
Westibone said:
My Evo is hardware version 003 for what it's worth.
Click to expand...
Click to collapse
When you select recovery, what happens?
I had same issue in Jan after flashing miui.
tried the suggestions on this thread..but nothing worked:
http://androidforums.com/evo-4g-support-troubleshooting/267018-struck-boot-loop.html
Had to replace my phone...that seems to be the only way out of this.
This is the reason I have stayed away from CM for so long. I keep seeing these horror stories about bootlooping, etc. I know its awesome when its running, but when it comes to the point where bricking your phone on purpose is a good thing, something is wrong For those that it has happened to above, did you get your new one and go back to CM (or any other AOSP rom)?
teh roxxorz said:
When you select recovery, what happens?
Click to expand...
Click to collapse
When I select recovery, it just goes back to the white Evo 4G screen and proceeds to boot loop. Over and over again
My God, another one. It's weird these seem to be happening more and more...
Westibone said:
When I select recovery, it just goes back to the white Evo 4G screen and proceeds to boot loop. Over and over again
Click to expand...
Click to collapse
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip Rename it to PC36IMg. Its 3.70 ruu, flash it in the bootloader, then re-root.
teh roxxorz said:
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip Rename it to PC36IMg. Its 3.70 ruu, flash it in the bootloader, then re-root.
Click to expand...
Click to collapse
Hopefully, your RUU will work. Others who have attempted to this this very thing still couldn't make it work. Me, k2buckley and others have yet to figure it out and believe me, we've tried everything within our experience range. A solution will be found, I have no doubt about that, but "when" is the question that I cannot answer.
teh roxxorz said:
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip Rename it to PC36IMg. Its 3.70 ruu, flash it in the bootloader, then re-root.
Click to expand...
Click to collapse
Don't know why this keeps happening dude. Just like all the other ones. I promise (unfortunately) that this guy isn't going to be able to recovery. Same as the others. THe RUU won't work, neither will the PC36IMG. I don't know why. THey may appear to complete successfully, but the result will still be hanging at the splash screen. That is my prediction, let's see his results. I hope I'm wrong, truly, I do.
k2buckley said:
Don't know why this keeps happening dude. Just like all the other ones. I promise (unfortunately) that this guy isn't going to be able to recovery. Same as the others. THe RUU won't work, neither will the PC36IMG. I don't know why. THey may appear to complete successfully, but the result will still be hanging at the splash screen. That is my prediction, let's see his results. I hope I'm wrong, truly, I do.
Click to expand...
Click to collapse
I hope you are too, but I have saved 1 person with the RUU, so I can hope to save more, but yea, I don't know what's causing this pandemic cuz I've been flashing the latest nightlies, reflashing my kernel, with no problems...I hope it works.
Same Here
Wow, what a coincidence, this just happend to me last night. I had just finished installing and flashing the new, SavagedZen(MOD)-RC1-Evo4G, Rom. Went to bed and sometime during the night the phone got stuck on restarting on the EVO white screen and turning off and on continusly. I have tried all the efforts of putting the stock ROM back on and everything else mentioned in this thread, but to no avail. Like you said, cant get into recovery or anything, just keeps looping through startin and stopping.
With all that is said so far on this thread, it looks like a new phone is the only way to fix this.
Westibone said:
Hi Guys, Idon't post too often as you can see, but I have had a great time rooting my Evo and learning from all the awesome members here. I do my research, and until now I have not run across a problem I could not fix on my own.
I am running CM7 nightly 26, and out of nowhere today, my phone rebooted and proceeded to get stuck in a boot loop. I am not surprised by that kind of thing at this point, but for the first time ever, I was not able to boot into recovery. If I select that option from the boot loader, I just get the white Evo 4G screen and it proceeds to boot loop.
Ok, I thought, maybe my recovery was corrupted somehow, so I pull the SD card and put Amon Ra 2.3 in the root directory and named it PC36IMG.zip and flashed it. No good. I still can't get into recovery.
I also tried downloading the stock (rooted) sprint ROM, putting on the root of my SD card and naming it PC36IMG.zip. After the bootloader detects it and the progress bar finishes, it says "Parsing PC36IMG.zip", and then it just takes me back to the bootloader main menu without an option to flash anything.
Also, is there a way to get S-ON back (with my only access being to the bootloader) in the event that I have to take it in? The alternative would be to drown it or smash it (as a last resort)
Any ideas? Thanks very much in advance for any help!
Click to expand...
Click to collapse
By some awkward chance, have you tried a full wipe, and then flash a sense rom?
teh roxxorz said:
I hope you are too, but I have saved 1 person with the RUU, so I can hope to save more, but yea, I don't know what's causing this pandemic cuz I've been flashing the latest nightlies, reflashing my kernel, with no problems...I hope it works.
Click to expand...
Click to collapse
There was actually one guy that I was able to help recover. (it was short lived though). After trying like 10 different RUU's, one of them had finally took. The phone booted up into a stock sense rom, and the kid was stoked. About 10 minutes after he was up again, his phone rebooted again. Stuck at the splash screen again (this was stock, and he still had s off, because we couldn't ever turn it on). I had him try flashing a recovery again, and low and behold it worked, and he flashed a sense rom. Things seemed fine, and I didn't hear back from him. A few days later, he PM'd be back, saying that it randomly rebooted again, and was stuck at the same splash screen loops. He ended up exchanging his phone. He was the ONLY one, out of quite a few that I've tried to assist through this problem, that was actually able to boot the phone again. Unfortunately, it wasn't stable for him, and then it ended up doing the same thing. Somehow, some way, I believe that the damage was already done, and he just got lucky to be able to squeeze a few extra days out of his Evo, but it was still a short lived recovery.
It's a very perplexing phenomenon that's going on here.
k2buckley said:
There was actually one guy that I was able to help recover. (it was short lived though). After trying like 10 different RUU's, one of them had finally took. The phone booted up into a stock sense rom, and the kid was stoked. About 10 minutes after he was up again, his phone rebooted again. Stuck at the splash screen again (this was stock, and he still had s off, because we couldn't ever turn it on). I had him try flashing a recovery again, and low and behold it worked, and he flashed a sense rom. Things seemed fine, and I didn't hear back from him. A few days later, he PM'd be back, saying that it randomly rebooted again, and was stuck at the same splash screen loops. He ended up exchanging his phone. He was the ONLY one, out of quite a few that I've tried to assist through this problem, that was actually able to boot the phone again. Unfortunately, it wasn't stable for him, and then it ended up doing the same thing. Somehow, some way, I believe that the damage was already done, and he just got lucky to be able to squeeze a few extra days out of his Evo, but it was still a short lived recovery.
It's a very perplexing phenomenon that's going on here.
Click to expand...
Click to collapse
I hope my case doesn't come back to haunt me. Seems like we got a T Virus of phone crashings going around...those already along their way [like you and I] are imune...the newer ones get sucked in. we haz to fix this soon-ishly.
Signed up for XDA because I got problems, and you guys seems to know everything when I need to use my googl-fu to solve a problem.
Have lurked for hours trying to figure this out. Nothing solves it.
Phone specs: Phone is babied, never dropped etc. Evo 4g on sprint, rooted unrevoked3 method, was running CM7 nightly95.
Have been running this for several days no issue, (since nightly95 came out.)
Was running a CM7 stable build before this. No issues.
And then the problem: Was just using my phone like normal at work it decided it wanted to reboot on me, once, restarts fine, and about an hour later reboots into a boot loop. It was on a charge cable to wall outlet, not pc when this happened, if that matters.
From the boot loop, just starts, vibrates, shows the htc evo screen maybe 10 seconds and reboots.
I can get into Hboot, (power + vol down) but can not get into recovery. if it's selected the boot looping starts again.
I have tried clearing storage, and flashing a couple PC36IMG.ZIP Since it seems to fix other peoples. Since the most I can figure out is putting the SD card into the computer and try loading files from Hboot.
Last one being this: http://forum.xda-developers.com/showthread.php?t=791019
Still boot looping, no recovery.
Any help is appreciated. But I am noob when it comes to command line adb stuff. Just so you know.
what PC36IMG are you trying to flash exactly?
try this one, its amon ra 2.3, its the one i have as a backup in case mine foks up, just take amonra out of the name so its only
PC36IMG.zip, then put in the root of your sd card, turn on phone while pressing volume down, to go into bootloader let the phone recognize it and select yes when asked to update, if thats gets your recovery up try wiping and restoring a backup
If all else fails, try the attached doc.
First, boot into the bootloader, look at the top of the screen and see if it still displays "S-OFF". If it does not, you need to re-root your device. If it displays "S-ON" then If you have a card reader, connect it to your PC or Mac and copy the contents of the SD card to your computer. Afterwards, re-format the card. Now copy a freshly downloaded rom and a freshly downloaded copy of the PC36IMG.zip file for amon-RA recovery version 2.3 to the root of your SD card (not in any folder). Re-insert the card in your EVO and boot to the bootloader. The PC36IMG.zip file *should* be automatically detected and you *should* be prompted to install it. Follow the prompts to install. Installation will take approximately 10 seconds. Afterwards, boot into your new recovery. Go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card. After that, flash the rom. Be patient during the initial boot process. You *should* be good to go afterwards.
posting & replying via the XDA Premium app.
HipKat said:
If all else fails, try the attached doc.
Click to expand...
Click to collapse
Tried this a bit ago.
Now it doesn't loop. But it's not any better.
It just boots, htc evo for a few seconds, and then vibrates approx 5 times and screen goes black and the top led flashes green.
Anybody else think this sounds like the bootloop of death? If so, there's no known fix. You can run the PC36IMG, but if that's what it is, you'll never get recovery or any rom to boot up.
I hope I'm wrong, though.
(from... Evo/MIUI/Tapatalk)
this sounds just like what happened to my phone. After spending hours on the forums and PM'ing back with a few people, I diagnosed it as the bootloop of death. Which sounds like exactly your going through....
no fix unfortunately...if your s on you can go back to sprint and get a brand new one. If not (like me) smash it pay the $100 deductible and get a refurb. Sucks I know.
For a more in depth thread search "boot loop + no recovery".
If I understand correctly, it's a problem with a partition size and was common with a certain Hardware version (0002?)
The good ole bootloop of death, that I fear so deeply. I hope this never happens to me. I'm sorry for your luck, but it sounds like plainjane is right. I agree, you got the bootloop of death, and most likely won't recover from it. Do you you have insurance ?
Sent from my PC36100 using XDA App
k2buckley said:
The good ole bootloop of death, that I fear so deeply. I hope this never happens to me.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
My fear, too. Every time I boot up in the morning, I hold my breath a little til the Evo screen goes off and the boot.ani starts...
Well, After HipKat first suggestion I can get to s-on. I may try it again with a different RUU but I think it's dead too.
So, since it will be S-on, hopefully there is a new phone in my future, without any money out of pocket.
Thanks for the help guys. I'll let you know if anything fixes it, or what sprint says.
HipKat said:
My fear, too. Every time I boot up in the morning, I hold my breath a little til the Evo screen goes off and the boot.ani starts...
Click to expand...
Click to collapse
From what I remember reading about a month ago, when this seemed to be happening a lot, was that it was random.
Didn't start when you were trying to boot up, just suddenly, randomly, terrifyingly, and like death in the night....power off, and never to fully boot again. Just typing about it now kinda scares me like a hex. I hope to finish typing this sentance.
@ OP, really sorry about your luck, man. We all feel you.
Sent from my PC36100 using XDA Premium App
Thats crazy, the same exact thing happened to my brother running CM7 lke a month a go.. is this limited to just AOSP ROMs? I know there's always the potential of bricking your phone flashing, but from what I've been reading it seems its happening to lots of people on AOSP ROMs
fergie716 said:
Thats crazy, the same exact thing happened to my brother running CM7 lke a month a go.. is this limited to just AOSP ROMs? I know there's always the potential of bricking your phone flashing, but from what I've been reading it seems its happening to lots of people on AOSP ROMs
Click to expand...
Click to collapse
No, it's not limited to AOSP ROMs, but it does seem that most of the cases were people running CM7 and/or Clockwork Mod. I know there was an argument that it's just that there are so many people running CM that it just seems like CM was the culprit, but it was odd to me, anyhow, how overwhelmingly I saw that it was happening to people running that mod
HipKat said:
No, it's not limited to AOSP ROMs, but it does seem that most of the cases were people running CM7 and/or Clockwork Mod. I know there was an argument that it's just that there are so many people running CM that it just seems like CM was the culprit, but it was odd to me, anyhow, how overwhelmingly I saw that it was happening to people running that mod
Click to expand...
Click to collapse
Yea I was reading this happened a few days ago to a guy who was on Decks 2.3.4.. IDK I told my brother to just flash a radio and pull the battery while flashing to try and get a replacement.. But the whole thing freaked me out lol.. Feel bad cuz it could happen to anyone I suppose
Your lucky to get S-ON, I only read about one other person able to get S ON after bootlooping.....take it to the Sprint Store, they should give you a new one on the spot if they have stock, if not they order one overnight. Could have been way worse...
Right now it says s-off again. But acts likes it's on, can't erase anything through fastboot/adb.
Going to try to repeat the RUU install a few times to see if I can get it back to s-on then take it in.
I was one of the first 3 or so people to report about this on the forum - it happened to me over 4 months ago. Anyways, if you flash a PC36IMG-eng and pull the battery at exactly the right time, while the radio is updating your phone will completely brick - it won't even turn on. Then you can take your phone in and just tell sprint it wont turn on. Note, it took me over 20 battery pulls before it finally wouldn't turn on, but its your best option if you can't get S-ON.
Wow that's crazy. I've never heard of the bootloop of death.
Sent from my PC36100 using Tapatalk
Do a search for Boot loop white screen and you'll find a ton of threads/posts about it
Okay, my touch pro 2 is messed up beyond belief. I tried to install a custom rom and I did it all by the instructions. Then it turned off when it was restarting and afterwards once it was restarting it just stayed on the HTC screen. It will not go any further. I have hard reset the thing many times along with trying to reinstall the roms. I honestly hope there is something that I can do... I have also tried doing the SD flash. Either way please comment ASAP.
Bootloader Info
RHOD400 32M SS-BC
SPL-1.00.OliNex
MicroP(LED) 0x0A
MicroP(KEY) 0x04
Turbro HW/Turbo SW
TP MFG DATA
496,521 764,841
763,207 245,198
227,841 Calibrated
This is what is shown in bootloader
the rhod400 is a cdma device, go to the tp2 cdma development and flash a rom from there
this is only for GSM devices
Is that why it would be stuck in the HTC Screen everytime?
pablotheescobar said:
Is that why it would be stuck in the HTC Screen everytime?
Click to expand...
Click to collapse
yeah, you installed a GSM rom, which is not compatible with your device
here is the link to the CDMA forum, good luck
http://forum.xda-developers.com/forumdisplay.php?f=517
Well, the thing is that I have tried to flash ROMS on there before and it still goes to the same screen. I don't know what I need to do because every forum is just saying try flashing it and I already have tried that and it goes to the same screen every time.
pablotheescobar said:
Well, the thing is that I have tried to flash ROMS on there before and it still goes to the same screen. I don't know what I need to do because every forum is just saying try flashing it and I already have tried that and it goes to the same screen every time.
Click to expand...
Click to collapse
did you run the "task 29" tool before flashing?
No, I never did do that... In the tutorial it never had that. I had to unlocked it with the hardSPL and I did that and it just restarted fine and then once I did that I installed the other one and it did the custom Rom and this is the outcome of that...
pablotheescobar said:
No, I never did do that... In the tutorial it never had that. I had to unlocked it with the hardSPL and I did that and it just restarted fine and then once I did that I installed the other one and it did the custom Rom and this is the outcome of that...
Click to expand...
Click to collapse
just do that before every flash and you'll be fine
Yeah, but my phone won't load anymore. It turns on and stays at the white HTC screen.
ok what task 29 does is deleting everything on the internal storage, read the cdma faq, so dont expect it to boot, click the button sequence that gets you in the boot loader, connect to usb, run the update utility, and profit. can't be anymore simple
good luck
NEVERMIND!
I installed the LEAD ROM, and it went through the ROM process and it came to the HTC screen and then it started loading I was so happy! Thanks for your guys help!
pablotheescobar said:
I installed the LEAD ROM, and it went through the ROM process and it came to the HTC screen and then it started loading I was so happy! Thanks for your guys help!
Click to expand...
Click to collapse
ur welcome, don't forget the thx button
pablotheescobar said:
Yeah, but my phone won't load anymore. It turns on and stays at the white HTC screen.
Click to expand...
Click to collapse
have you formatted your micro sd card to fat32?
then flash the rom from the sd card.
bro heres what you gotta do to fix your pfoblem, first format your sd card to fat32 then copy the nbh file onto the card, rename it to RHODIMG insert the sd card then enter the boot loader menu by first taking out the battery, and reinserting it. now with the phone off hold the volume down button while pressing the power button this forces the device into bootloader mode. your screen WILL read RHODIMG os. now press the power button again to install whatever rom you want but I would recommend using a stock rom or one that you know works, ie- from past experience.
trust me bro do this and all will be fine again,
HAPPY FLASHING
oh dont forget to press the soft reset button once the rom installation is done when the screen says installation successful,
once again HAPPY Flashing>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>
next thing is to try a different cable.
try this and if it doesnt work pm me and I will walk you through some more complicated steps. I have an epic now so I am not on this page much anymore. but I am very familiar with the rhodium. and like to come by every once in a while to see if anyone needs any help!
sapperpipo said:
have you formatted your micro sd card to fat32?
then flash the rom from the sd card.
bro heres what you gotta do to fix your pfoblem, first format your sd card to fat32 then copy the nbh file onto the card, rename it to RHODIMG insert the sd card then enter the boot loader menu by first taking out the battery, and reinserting it. now with the phone off hold the volume down button while pressing the power button this forces the device into bootloader mode. your screen WILL read RHODIMG os. now press the power button again to install whatever rom you want but I would recommend using a stock rom or one that you know works, ie- from past experience.
trust me bro do this and all will be fine again,
HAPPY FLASHING
oh dont forget to press the soft reset button once the rom installation is done when the screen says installation successful,
once again HAPPY Flashing>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>
next thing is to try a different cable.
try this and if it doesnt work pm me and I will walk you through some more complicated steps. I have an epic now so I am not on this page much anymore. but I am very familiar with the rhodium. and like to come by every once in a while to see if anyone needs any help!
Click to expand...
Click to collapse
look above it says problem solved, and that ungrateful n00b did not even hit the thanks button, don't waste your breath
Yeah your right.
Sent from my SPH-D700 using XDA App
Hey, I am going through the same thing too. I hope that someone can really help. I am a beginner when it comes to this.
pablotheescobar said:
Okay, my touch pro 2 is messed up beyond belief. I tried to install a custom rom and I did it all by the instructions. Then it turned off when it was restarting and afterwards once it was restarting it just stayed on the HTC screen. It will not go any further. I have hard reset the thing many times along with trying to reinstall the roms. I honestly hope there is something that I can do... I have also tried doing the SD flash. Either way please comment ASAP.
Click to expand...
Click to collapse