Related
Okay so first off, let me just thank everyone who's willing to contribute to helping my issue ahead of time. I highly respect this community, and everything that everyone has done towards making android what it has become.
ANYWAY - I'm completely screwed, or so it seems. I cannot boot into anything, no ROM, no recovery. I've tried replacing the PC36IMG.zip on the root of my SD card. I've even downloaded the "RUU_SuperSonic_S_Sprint_WWE_3.30.651.3_Radio_2.15.00.09.01_NV_1.77_003_release_157088_signed.exe", and tried to start over completely, but even that did not work.
Whenever I try to restart my phone, or enter recovery from the HBOOT menu, I get a constant boot loop of the EVO white screen. Over and over, that's all it does. On my HBOOT menu I am showing:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.02.000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.09.01
Oct 14 2010, 19:14:47
I don't know what other options I have in order to restore my phone. Everything was working fine. I was running MIUI 12.3, with the stable CFS kernel. I woke up this morning, phone worked normally, then decided to randomly reboot. After that, it was over. I couldn't reboot into recovery, or simply reboot the phone.
If anyone can help out, it's greatly appreciated.
I'm not much help for that, but try this file:http://db.tt/AQItwCr
It's clock work mod recovery. If you can boot into hboot, you can flash that. Although, I'm assuming your rooted because you flashed mui*. So its pointless if your not rooted. Let me know what happens.
Sent From My HTC Evo 4G Using Tapa Talk Pro!
Rydah805 said:
I'm not much help for that, but try this file:http://db.tt/AQItwCr
It's clock work mod recovery. If you can boot into hboot, you can flash that. Although, I'm assuming your rooted because you flashed mui*. So its pointless if your not rooted. Let me know what happens.
Click to expand...
Click to collapse
I placed the .zip file on my SD card, and boot my phone into the HBOOT menu. It loaded the file, then put me back at the menu. I attempted to enter recovery > same issue. I'm placed at the white EVO 4G screen, and it keeps boot looping...
xxjuicymintxx said:
I placed the .zip file on my SD card, and boot my phone into the HBOOT menu. It loaded the file, then put me back at the menu. I attempted to enter recovery > same issue. I'm placed at the white EVO 4G screen, and it keeps boot looping...
Click to expand...
Click to collapse
Pretty fukkin weird. It shouldn't even boot up, it should just go into recovery.
What recovery were you running before?
Sent From My HTC Evo 4G Using Tapa Talk Pro!
Once you RUU back to stock, you should be able to reboot into the phone. Don't go into recovery because you don't have a recovery anymore. If the phone doesn't boot up into Sense, then the RUU you grabbed is corrupt and you need to re-download or grab from somewhere else. Your hboot is now showing S-ON because you basically unrooted your phone so there wouldn't be any recovery.
mizzos4 said:
Once you RUU back to stock, you should be able to reboot into the phone. Don't go into recovery because you don't have a recovery anymore. If the phone doesn't boot up into Sense, then the RUU you grabbed is corrupt and you need to re-download or grab from somewhere else. Your hboot is now showing S-ON because you basically unrooted your phone so there wouldn't be any recovery.
Click to expand...
Click to collapse
This is true. I didn't even think of that. You will need to reroot after that. Can somebody post a link for this guy? We can help each other out.
Sent From My HTC Evo 4G Using Tapa Talk Pro!
mizzos4 said:
Once you RUU back to stock, you should be able to reboot into the phone. Don't go into recovery because you don't have a recovery anymore. If the phone doesn't boot up into Sense, then the RUU you grabbed is corrupt and you need to re-download or grab from somewhere else. Your hboot is now showing S-ON because you basically unrooted your phone so there wouldn't be any recovery.
Click to expand...
Click to collapse
I just ran it again, and the install process completes. Everything seems to go smoothly. The phone reboots, and you see the HTC EVO 4G white screen, but then it just goes black, restarts, and repeats.
I'm still unsure as to why I can't seem to boot into anything. Don't know what caused this. I do a lot of reading in these forums, and I've never heard of anything like this. Did quite a bit of googling, trying to read up on others that might've 'bricked' their phone, etc.
Also, the RUU file that I used, I gained from this thread:
http://forum.xda-developers.com/showthread.php?t=840843
Try running the RUU a second time. Same thing happened to me with one of my EVOs, and I had to run the RUU twice to get it to work.
_MetalHead_ said:
Try running the RUU a second time. Same thing happened to me with one of my EVOs, and I had to run the RUU twice to get it to work.
Click to expand...
Click to collapse
I've tried this as well, with no success.
xxjuicymintxx said:
I've tried this as well, with no success.
Click to expand...
Click to collapse
Sucks.... ;(
Sent From My HTC Evo 4G Using Tapa Talk Pro!
Welp.... do you have TEP? If you file your claim with them tonight you should have your replacement by tomorrow.
_MetalHead_ said:
Welp.... do you have TEP? If you file your claim with them tonight you should have your replacement by tomorrow.
Click to expand...
Click to collapse
Haha, I'm not sure actually. I'm on a friends plan.
But, there's gotta be a way to get past the problem I'm having, with THIS Evo.
Shouldn't be a need to order a new one.
Hopefully someone in these forums can figure out a solution.
xxjuicymintxx said:
Okay so first off, let me just thank everyone who's willing to contribute to helping my issue ahead of time. I highly respect this community, and everything that everyone has done towards making android what it has become.
ANYWAY - I'm completely screwed, or so it seems. I cannot boot into anything, no ROM, no recovery. I've tried replacing the PC36IMG.zip on the root of my SD card. I've even downloaded the "RUU_SuperSonic_S_Sprint_WWE_3.30.651.3_Radio_2.15.00.09.01_NV_1.77_003_release_157088_signed.exe", and tried to start over completely, but even that did not work.
Whenever I try to restart my phone, or enter recovery from the HBOOT menu, I get a constant boot loop of the EVO white screen. Over and over, that's all it does. On my HBOOT menu I am showing:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.02.000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.09.01
Oct 14 2010, 19:14:47
I don't know what other options I have in order to restore my phone. Everything was working fine. I was running MIUI 12.3, with the stable CFS kernel. I woke up this morning, phone worked normally, then decided to randomly reboot. After that, it was over. I couldn't reboot into recovery, or simply reboot the phone.
If anyone can help out, it's greatly appreciated.
Click to expand...
Click to collapse
You were using an AOSP ROM with the new hboot? Didn't you have to use the HTC kernel?
xxjuicymintxx said:
Haha, I'm not sure actually. I'm on a friends plan.
But, there's gotta be a way to get past the problem I'm having, with THIS Evo.
Shouldn't be a need to order a new one.
Hopefully someone in these forums can figure out a solution.
Click to expand...
Click to collapse
I wish I could be of more help. Good luck and godspeed.
xHausx said:
You were using an AOSP ROM with the new hboot? Didn't you have to use the HTC kernel?
Click to expand...
Click to collapse
Yes, I was using MIUI 12.3, which is AOSP based. I don't think I had the new hboot until sometime after this problem started. One of the PC36IMG.zip's that I put on the root of my SD I believe was from somewhere in the new HBOOT Root thread on this forum, but I can't remember 100%.
Prior to that, I had the old HBOOT, I'm quite sure. I've never had a problem until. I've flashed plenty of ROMS, and recovery has always booted for me. MIUI wasn't giving me any issues, until earlier today. Randomly, POOF...it restarted...only, it boot looped. Didn't think it'd effect my recovery, though. I've had boot loop issues with other ROM's before, and have just booted into recovery, and solved the problem from there.
Who knows what happened to me earlier, or why, but it really is a pain. It's hard not having a phone. Especially when you've been blessed with an Evo!
xxjuicymintxx said:
Yes, I was using MIUI 12.3, which is AOSP based. I don't think I had the new hboot until sometime after this problem started. One of the PC36IMG.zip's that I put on the root of my SD I believe was from somewhere in the new HBOOT Root thread on this forum, but I can't remember 100%.
Prior to that, I had the old HBOOT, I'm quite sure. I've never had a problem until. I've flashed plenty of ROMS, and recovery has always booted for me. MIUI wasn't giving me any issues, until earlier today. Randomly, POOF...it restarted...only, it boot looped. Didn't think it'd effect my recovery, though. I've had boot loop issues with other ROM's before, and have just booted into recovery, and solved the problem from there.
Who knows what happened to me earlier, or why, but it really is a pain. It's hard not having a phone. Especially when you've been blessed with an Evo!
Click to expand...
Click to collapse
I think you screwed yourself by updating hboot. Haus* is working on an easy 2.02 hboot root.
Sent From My HTC Evo 4G Using Tapa Talk Pro!
xxjuicymintxx said:
Yes, I was using MIUI 12.3, which is AOSP based. I don't think I had the new hboot until sometime after this problem started. One of the PC36IMG.zip's that I put on the root of my SD I believe was from somewhere in the new HBOOT Root thread on this forum, but I can't remember 100%.
Prior to that, I had the old HBOOT, I'm quite sure. I've never had a problem until. I've flashed plenty of ROMS, and recovery has always booted for me. MIUI wasn't giving me any issues, until earlier today. Randomly, POOF...it restarted...only, it boot looped. Didn't think it'd effect my recovery, though. I've had boot loop issues with other ROM's before, and have just booted into recovery, and solved the problem from there.
Who knows what happened to me earlier, or why, but it really is a pain. It's hard not having a phone. Especially when you've been blessed with an Evo!
Click to expand...
Click to collapse
That's what it was, the 2.02 hboot is not compatible with older phones and vice versa. Is your NAND still unlocked? (shows S-OFF) If so you may be able to do something with it.
xHausx said:
That's what it was, the 2.02 hboot is not compatible with older phones and vice versa. Is your NAND still unlocked? (shows S-OFF) If so you may be able to do something with it.
Click to expand...
Click to collapse
No, it's not unlocked. It' showing S-ON.
&& this problem occurred BEFORE I was even running the hboot 2.02 --
I don't remember exactly what I had before, I believe it was the .76 hboot.
Everything was working perfectly fine.
I had just installed MIUI 12.3 a day earlier. Used it fine. Had everything set up the way I liked it. Went to sleep, woke up, phone still worked fine. Then it randomly reboot, and this problem started there.
The hboot 2.2 was only applied, I believe, when I put a PC36IMG.zip on my SD card root, that I had read about in a reply from someone on the 2.02 hboot thread.
Now it seems that I have only further screwed myself, apparently? idk.
I've tried running the latest RUU stock, to restore my phone to normal. NO luck.
Tried running it twice in a row, as per advice of someone earlier -- still no luck.
Endless reboots, no matter what. Yet, I can still get into the hboot menu. that's about it.
There's BOUND to be a way to fix this...
I can load PC36IMG.zip's ....but nothing else.
is there something that someone can package for me to revert back?
I have no idea, hence the reason I'm here.
HELP!
[and big thanks, of course!!]
Same thing happened to me. Lost recovery, and couldn't boot into rom. Just rebooted on splash screen over and over. Couldn't pull a logcat. Tried flashing recovery through fastboot, through bootloader, flashed renamed roms, the pc36img that I originally used from toasts 2part, etc. Nothing failed or threw errors. Only change I noted was that it reverted my custom splash screen to stock. Last ditch effort I ran an RUU with the phone in bootloader, which took a few tries but successfully "updated." Still couldn't boot into the OS. RUU restored me from engineering s-off back to ship s-on and I replaced it via warranty, $35 new phone on the spot.
Good luck, hope you manage to find something that works for you. After fastboot flashing failed I jumped on here and google hoping to find a fix, and searched for a week to no avail.
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.
I've been looking through threads for hours and have tried a lot of what has been suggested. At first it just started randomly bootlooping ( white htc screen, restart). I then tried some guide on a thread that had me ADB then RUU, once that was all done It got to the white htc evo screen, turned black then vibrated 5 times and the green light started to flash. I can't get into the recovery menu, I click it and it just goes straight to white htc screen. I've flashed multiple PC36IMG's with different recoveries, with no luck.
My fuse is burnin low...
Supersonic EVT2-3 SHIP S-OFF
HBOOT-0.79.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-1.39.00.04.26
APR 14 2010, 15:41:34
*update-
I tried another RUU, a newer version.
http://forum.xda-developers.com/showthread.php?p=7529500#post7529500
Now it seems to be in a bootloop, no 5 vibrate+ flashing light though..
IxHaku said:
*update-
I tried another RUU, a newer version.
http://forum.xda-developers.com/showthread.php?p=7529500#post7529500
Now it seems to be in a bootloop, no 5 vibrate+ flashing light though..
Click to expand...
Click to collapse
OK......so basically you got no RECOVERY?....so when you boot into the BOOTLOADER to install the PC36IMG....does it recognize the image?.......and does it ask u to install and reboot?......we'll start there
What rom were you running? Some users have had a bootloop of death, no coming out of it, on CM7. I think it has happened on other AOSP roms as well, but you mainly see it on CM7 - probably because of the larger user base.
I have yet to see a solution for it, I think everyone else had to report it lost and pay the $100 deductible through insurance. The only hope is to keep running RUUs and hopefully one will stick.
(from... Evo/MIUI/Tapatalk)
Yeah I can see the image and to install and reboot.
And I was running CM7. FFFFFF I don't have insurance... Don't really want to take it to the sprint store with S-off.. So i guess ill keep trying to run RUU's... probably wont work though
IxHaku said:
Yeah I can see the image and to install and reboot.
And I was running CM7. FFFFFF I don't have insurance... Don't really want to take it to the sprint store with S-off.. So i guess ill keep trying to run RUU's... probably wont work though
Click to expand...
Click to collapse
If the pc RUU isn't working, trying using the same firmware RUU, but in PC36IMG file, which you flash in the bootloader.
@plainjane : For those that had the issue on CM7 [some users on MIUI], and they we chalked it up to bad nand blocks? But we still have no 'cure' for it.
teh roxxorz said:
If the pc RUU isn't working, trying using the same firmware RUU, but in PC36IMG file, which you flash in the bootloader.
@plainjane : For those that had the issue on CM7 [some users on MIUI], and they we chalked it up to bad nand blocks? But we still have no 'cure' for it.
Click to expand...
Click to collapse
Does it matter which RUU I use? (2.1,2.2)
reverepats said:
OK......so basically you got no RECOVERY?....so when you boot into the BOOTLOADER to install the PC36IMG....does it recognize the image?.......and does it ask u to install and reboot?......we'll start there
Click to expand...
Click to collapse
Exactly! Do not worry about flashing a RUU at this time. Click on amon RA in my signature to download the PC36IMG.zip for amon RA and place it on the root of your SD card. Remove any other file with that name. Boot onto the bootloader (simultaneously press the DOWN volume & power button until your device starts) and then follow the prompts to install. Installation should take no more than 10 seconds. Afterwards, enter your new recovery, connect your device to your computer, select the USB-MS option and then copy the contents of your SD card onto a folder on your computer. After that, select the USB-MS option again to disengage. Now go to the wipe menu and wipe EVERYTHING it. When you're done, download a fresh copy of the rom you want to flash and flash it or copy a nandroid backup to your SD card and restore it. Be patient, either way, with the initial bootup.
pecking & swyping from my EVO 4G (XDA Premium)
Alright so I tried everything I could... So I took it into a sprint store. Told the guy this happened when doing the most recent update. Right there he went into the bootloader menu, I thought I was screwed... but he didn't say anything about the S-OFF. Eventually I came back and they ordered me another one.. probably a refurb. He said it was going to be free, and I don't have insurance. Guess I got lucky.
Thanks everyone for the input.
I purchased a used droid incredible off of ebay to fix. The phone powers on but doesn't get past the droid incredible splash screen. It is able to boot into HBOOT but when the recovery option is selected it just goes back to the white splash screen. There is no sd card but I have put one in myself..it's not formatted and it's empty. Any help would be greatly appreciated!
What info is detailed in hboot? S-on, s-off, etc; provide any relevant info that you see once you boot into hboot. Do you know what os the phone is on: froyo, GB? Did the seller provide info on how the phone got in this situation?
Here's a photo of hboot. The owner said one day it just turned off and went to the splash screen. It was not rooted.
Sent from my Galaxy Nexus using XDA
Aight, you may have to perform a factor reset. Have you done that yet? If so, you may have to download an RUU from here:
pvillecomp.com
It is under "Stock images." One download link is for the froyo RUU and the other is for Gingerbread. Place the file onto the root of your sd card in no folders and then boot into hboot. Hboot should prompt you to upgrade using the volume buttons.
Factory reset did not work. I will try the second option and get back to you
thanks!!
Sent from my Galaxy Nexus using XDA
I would not do the gingerbread ruu as that will upgrade the radio making it harder to root. I would try the froyo ruu first, if that works run unrevoked.
When I boot into hboot nothing happens. I'd this because the RUU is an exe?
Edit: I'm downloading the PB31IMG file now
Edit 2: The PB31IMG didn't seem to work. It said SD checking ..loading PB31IAG.zip: no image. And the same for PB31DIAG.nbh, PB31IMG.zip and .nbh
Sent from my Galaxy Nexus using XDA
Is your sdcard fat32?
Yes it is. PB31img didn't work and RUU says I have under 30% battery so I'm just charging the phone. If the phone wasn't even rooted in the first place what could the cause of the problem be?
jared, did you ever get this to work? I have one that is doing the exact same thing.
I did not! I tried to use the RUU through the computer and it seemed to restore everything but the radios but then failed. I was then prompted to do a recovery and try again but the phone went black and would not power on no matter how much I charged it.
That sucks....thanks for the reply though.
So I figured I would give you an update.
I ended up trying several micro SD cards (ones that I had laying around the house), started with SanDisk 2GB, then a Transcend 1GB, and finally a generic 4GB HC. When I used the generic 4GB, the Inc was able to see the PM31img file and downloaded and did the upgrade. Only problem is that I used the gingerbread image, and not sure what happened (my guess is slcd issue) but the radio failed everything else passed. When it rebooted I have nothing, no display and it doesn't look like it will even power up.
So I figured I would let you know, since I was having basically the identical issue you were, that it might be your micro SD card. But make sure you have the correct image on it too before you start swapping SD cards.
Ok, so I have an old droid incredible that has not been used in years, I charged it up and when I turned it on, all it would show is the droid incredible logo and it will vibrate, then turn on and repeat.
On hboot it states this
IncredibleC XC SHIP S-ON
HBOOT -0.92
and some other stuff
Ive tried doing recovery, clear storage, factory reset, but they all lead to the same loop again as if nothing happened.
I have also tried installing some other recoveries but all that happens is that it states something like wrong name or not found (something like that)
Anyways, Im like 80% sure that this phone worked before it was sent to sleep till I decided to use it again.
And im 100% sure that this phone was completely stock, no root, nada, probably one of the most squeaky clean phones, at least I hoped it was. Its my bro's and he doesn't root any of his android devices.
sasdas said:
Ok, so I have an old droid incredible that has not been used in years, I charged it up and when I turned it on, all it would show is the droid incredible logo and it will vibrate, then turn on and repeat.
On hboot it states this
IncredibleC XC SHIP S-ON
HBOOT -0.92
and some other stuff
Ive tried doing recovery, clear storage, factory reset, but they all lead to the same loop again as if nothing happened.
I have also tried installing some other recoveries but all that happens is that it states something like wrong name or not found (something like that)
Anyways, Im like 80% sure that this phone worked before it was sent to sleep till I decided to use it again.
And im 100% sure that this phone was completely stock, no root, nada, probably one of the most squeaky clean phones, at least I hoped it was. Its my bro's and he doesn't root any of his android devices.
Click to expand...
Click to collapse
Do an ruu thru hboot. Download this file http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip, and place it on your sdcard in no folders named exactly how it is (PB31IMG.zip). Boot to hboot, wait a few secs and it should find the file, parse it, and then prompt you to press vol up to install. Once done it will prompt you to press vol up to reboot. If hboot says it cant find the file, you may need to reformat your sdcard fat32 with a pc and then try again.
Ok, so it seemed to had found it, and a bar on the right appear and it said loading, but once that was done, it would state checking that zip, and then it just showed the hboot screen again.
sasdas said:
Ok, so it seemed to had found it, and a bar on the right appear and it said loading, but once that was done, it just showed the hboot screen again.
Click to expand...
Click to collapse
What radio (baseband) version does it say in hboot? Try this one http://dinc.does-it.net/Stock_Images/4.08.605.2/PB31IMG.zip.
cmlusco said:
What radio (baseband) version does it say in hboot? Try this one http://dinc.does-it.net/Stock_Images/4.08.605.2/PB31IMG.zip.
Click to expand...
Click to collapse
This one didnt do anything, stating something like not found, but im unable to reformat the card again since its late now, the previous one worked I believed because I reformat it before I even tried it.
Anyways, the radio states
RADIO-2.15.10.07.07
sasdas said:
This one didnt do anything, stating something like not found, but im unable to reformat the card again since its late now, the previous one worked I believed because I reformat it before I even tried it.
Anyways, the radio states
RADIO-2.15.10.07.07
Click to expand...
Click to collapse
sorry for double posting, anyways it turned on and it was loading and everything, it even showed the lockscreen, and just as I was about to unlock it, it went back to boot loop.