Develop Bugs

[Q] G2 stuck at HTC screen.

Hey guys, I tried to perma root my wife's G2 last night using Visionary+ r14 but when it tried to reboot it doesn't get past the green and white "HTC" screen, so now I have a couple of questions.
I bought this phone from someone off of Craigslist and it was working great until I tried to root it so it is technically out of warranty do you think I can get it replaced since everything is still stock?
Also I tried to apply the HTC OTA update to fix it and I still have the problem, is there anything I can do to repair this phone? Thanks in advance guys and mahalo!

Okay pull your battery out and put it back in..after dat press power button and volume down button until you get to the recovery screen and do a factory reset..
Sent from my HTC Vision using XDA App

Thanks for the reply jboiii15. I did a factory reset before I flashed the OTA update and I have factory reset several times but still no go. I appreciate you taking the time to help me out.

Did you try this? http://forum.xda-developers.com/showthread.php?t=842495

aznsnake666 said:
Did you try this? http://forum.xda-developers.com/showthread.php?t=842495
Click to expand...
Click to collapse
I haven't tried it because I can't get ADB to work with the phone the way it is, Fastboot works but ADB just shows nothing there while I'm in recovery or the boot screen. Thank you also for the reply. My wife is pissed lol.

Try to extract the ROM from the official RUU and rename it to PC10IMG.zip. Put this on the root of your SD card and boot into bootloader and leave it to work. This should solve your problem Fingers Crossed
JD

do you have s-off??

I don't have S-OFF as I just started the rooting procedure when it decided to take a dump on me, after this I don't think my wife will want me to root any more of her phones although I know she'll miss it after having a rooted G1 running CM and a rooted Slide running Chromatic. Good thing I didn't sell her Slide yet lol.
I'll try to find information on the PC10IMG.zip method now and see what can be done.
Thank you guys for all the help, I really appreciate it all.

itsmekeoni said:
I don't have S-OFF as I just started the rooting procedure when it decided to take a dump on me, after this I don't think my wife will want me to root any more of her phones although I know she'll miss it after having a rooted G1 running CM and a rooted Slide running Chromatic. Good thing I didn't sell her Slide yet lol.
I'll try to find information on the PC10IMG.zip method now and see what can be done.
Thank you guys for all the help, I really appreciate it all.
Click to expand...
Click to collapse
I think the rooting process has corrupted your kernel or rom, it is rare to get a brick from just the visionary process, but i know there has at least been one that this has happened to.
Report back to tell us if the extracted ROM worked for you, there is still hope;')
JD

Oh man this is just getting worse lol. I had the phone sitting here plugged into my laptop while the phone was in the Hboot screen where you can select Fastboot, Recovery and so on. All of a sudden my here Windows give off the noise as if something was connected or disconnected from my computer and I see the screen shut off on the G2 with a red light blinking. Now the phone doesn't power on and the red light blinks while the phone is plugged into the computer but doesn't power on.
As I was typing this the red light came on solid as if it is charging now, maybe it doesn't charge while in that screen and the battery just died I dunno, strange.

JupiterDroid said:
I think the rooting process has corrupted your kernel or rom, it is rare to get a brick from just the visionary process, but i know there has at least been one that this has happened to.
Report back to tell us if the extracted ROM worked for you, there is still hope;')
JD
Click to expand...
Click to collapse
Well I called T-Mobile and they are sending out a new phone, I'm unsure if I should still mess with it or not. I did flash the TMOUSA OTA update and that didn't help, I didn't unpack it to see if it contained a new Kernel but I'm sure it had a new system.img, still think it is one of those that is messed up?
I'm having a hard time finding the things to get the PC10IMG.zip going, work is calling me in different directions and my A.D.D is kicking in lol.

try this http://forum.xda-developers.com/showthread.php?t=855764 i had the same problem like you, steviewevie told me to do it, if you have problem to connect your g2 with sdk download pda net, it works for me and now i have my g2 back with the new root... just do what it said on that link believe me works...
P.D. I am a androidnoober always have a iphone and this was my first time using sdk adb or whatever name is and I did it

Thanks AndroidNoober, I've seen that link in my search for an answer to my problem. One of the issues that is making this harder is that after the phone "bricked" it lost ADB connectivity. I've tried it on two computers that have a properly working ADB (I test it with my N1 and 3G Slide) and it used to work with the G2 but now I can't get it to see the phone, I've heard Recovery has ADB blocked.

semi bricked attempting permaroot
i attempted permaroot and semi bricked my phone. will not boot past htc screen. i can't get adb to work. i am trying to get pdanet installed but it keeps getting stuck on installing on phone. can it install while phone is in recovery mode? i have had no sucess trying to figure this out on my own and phone is not covered with a warranty
i have gotten the phone to read an update.zip file.
it is reading the pc10img.zip as well.
now i just have to get past the htc screen.
i do have s-on as i had just started the process.
any help would be appreciated

[Q] Boot Loop with No Recovery

So before everyone yells because of my inability to search the forum, please understand that not only have i searched this forum, but just about every other one. And if someone finds a thread with an answer to my question than i will admit defeat and have myself stoned and crucified.
I will greatly appreciate anyone's and everyone's help.
History in cliffnotes
Rooted with Unrevoked about a month ago, since then been running CM 6.
Have been happy with just using stock CM 6 and nothing else, haven't flashed any other kernels, radios, or for that matter roms.
Have always had problems with random reboots but didn't care.
Last night my phone appeared to have the desire to random reboot, and on start up got into a boot loop, just HTC splash boot loop. I can get into bootloader but if i try to go to recovery it is just more boot loops.
I'm running mac OS X however i eventually just tried running RUU on my roommates computer but to no avail, mostly, i think, because my phone can't boot into a state where its recognized by the program or sync, etc...
The real problem
As of now i've gone as far as basically completely unrooting, using a pc36img that i found through you guys here
So if you guys have any ideas, at this point, i'm completely willing to try them because, this was completely random that it happened, and i really am at a complete loss as to what to do besides buy a new phone.
i love you all in a masculine plutonic way. thanks.

well you could always re-root with unrevoked. all it needs is bootloader mode to root it and then once its done, flash a rooted rom on it, then proceed to unroot.
EDIT:
btw, i am a mac user too and unrevoked works great. if it fails, run it again. and no need to use an ruu, look up a thread in our development section titled shpped roms and they have pc36img versions of the ruu. you will be able to root with your mac and unroot all on the device. unrevoked has an s-on zip on their web page. to unroot it, flash the s-on zip then run the pc36img zip from the base of your sd card. thats all!
EDIT#2:
YOU CAN ALWAYS FLASH A RECOVERY VIA BOOTLOADER ALSO AND FLASH A ROM. LET ME KNOW WHICH RECOVERY YOU PREFFER, I GOT BOTH CLOCKWORKMOD AND RA.
EDIT#3: LOL, Sorry i didnt see that you mentioned a pc36img to unroot.

why dont you just download download the recovery img of amon_ra 2.2.1 in pc36img format and run it from boot loader. done, problem solved.
if that doesnt work download caukulins format all zip and run it and them reload your recovery and rom

t3project said:
why dont you just download download the recovery img of amon_ra 2.2.1 in pc36img format and run it from boot loader. done, problem solved.
if that doesnt work download caukulins format all zip and run it and them reload your recovery and rom
Click to expand...
Click to collapse
I am not trying to thread jack, but i too am having the same problem. I am not a noob at flashing and I am stuck at the white Evo screen and it just reboots when I click on recovery from the boot loader.
I too have flashed the recovery image from amen ra and it flashed ok, but each time I reboot and try to get into recovery it just reboots, so that did not fix getting into recovery.
The problem with the above suggestion is that you need to be able to boot into a recovery to use Caukulins format all zip, and if you can't get into recovery it does no good.
If anyone has any other suggestions please let the both of us know!

Well since you can't get into recovery, we suggested to flash a recovery in pc36img.zip format in bootloader mode.
Sent From My HTC Evo 4G On The Now Network From Sprint Using Tapatalk Pro!

paulieb81 said:
I am not trying to thread jack, but i too am having the same problem. I am not a noob at flashing and I am stuck at the white Evo screen and it just reboots when I click on recovery from the boot loader.
I too have flashed the recovery image from amen ra and it flashed ok, but each time I reboot and try to get into recovery it just reboots, so that did not fix getting into recovery.
The problem with the above suggestion is that you need to be able to boot into a recovery to use Caukulins format all zip, and if you can't get into recovery it does no good.
If anyone has any other suggestions please let the both of us know!
Click to expand...
Click to collapse
thats why i said flash a recovery in pc36img format first. more specifically this:
http://forum.xda-developers.com/attachment.php?attachmentid=483320&d=1294435056
rename to pc36img.zip and boot into bootloader

t3project said:
thats why i said flash a recovery in pc36img format first. more specifically this:
http://forum.xda-developers.com/attachment.php?attachmentid=483320&d=1294435056
rename to pc36img.zip and boot into bootloader
Click to expand...
Click to collapse
If you read my message you will see that I DID flash a recovery, that same one you just linked, and it flashed ok, but when i restart and choose to enter the recovery the phone just reboots again!

Did you solve this?

Yes I did, I went back to the store and had them replace the phone. I could not get it to boot into recovery for some reason.

I dont know what causes this, but this is like the 10th person on a CM rom that's had this exact scenario. Its weird how it happens out of the blue, and then RUU and pc36img just don't work. Very strange. I was just trying to help a guy the other day in this exact scenario. Nothing would get him out of the splash screen. No RUU, PC36IMG of recovery OR a factory ROM, fastboot RUU didn't work. Nothing. Just bricked at the bootloader somehow. I always thought if you could get to the bootloader then you could recovery, but lately there have been quite a few of this exact scenario, and each one was on the same rom. I would love to know what causes this, when the phone is just sitting there, and then goes into a bootloop out of the blue, and then this is the result. It's leaving me frightened to run CM, seriously. What on earth could be causing this type of thing?
Sent from my PC36100 using XDA App

heppened to me too and since then ive seen at least 5 cases of this exact same problem from cm7 roms. so far no one has found a way to fix it that has been posted here. we have all had to have our phones replaced.

ChacocII said:
heppened to me too and since then ive seen at least 5 cases of this exact same problem from cm7 roms. so far no one has found a way to fix it that has been posted here. we have all had to have our phones replaced.
Click to expand...
Click to collapse
Did they give you any problems about s-off being visible in the bootloader when you got your phone replaced? I'm to that point of taking it back with the EXACT same problem but I didn't know if it was an issue. (or is there any trick to get s-on back without being able to load into recovery i.e. a fastboot command?)

i was worried about the s-off as well because i also was unable to change that. all i could find for that was the s-on tool but since u cant actually flash anything, had to leave it s-off. i even tried a battery pull during the radio update on a pc36img so that they wouldnt be able to get to bootloader but i couldnt even brick it. i live more than 50 miles from a sprint store so they didnt make me drive to a sprint store. they sent me a replacement and i mailed my evo back. on the paperwork for the new phone they said i could still be charged 75 dollars for a recoverable phone and 125 for an unrecoverable phone. it was probably 2 weeks ago or so when i sent my old broken evo back and i havent been billed yet so i dont know what if anything they will charge. when i talked to the sprint tech on the phone i told him it was rooted because i knew they would see the s-off and i didnt want to get screwed when i sent them my broken phone and they said "u rooted, ur problem" but he said he would still replace it and he did.

k2buckley said:
I dont know what causes this, but this is like the 10th person on a CM rom that's had this exact scenario. Its weird how it happens out of the blue, and then RUU and pc36img just don't work. Very strange. I was just trying to help a guy the other day in this exact scenario. Nothing would get him out of the splash screen. No RUU, PC36IMG of recovery OR a factory ROM, fastboot RUU didn't work. Nothing. Just bricked at the bootloader somehow. I always thought if you could get to the bootloader then you could recovery, but lately there have been quite a few of this exact scenario, and each one was on the same rom. I would love to know what causes this, when the phone is just sitting there, and then goes into a bootloop out of the blue, and then this is the result. It's leaving me frightened to run CM, seriously. What on earth could be causing this type of thing?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm in the same boat buckley. I don't get it?! I did run cm for a couple days but I was always looking at my phone wondering if something was going to happen. Almost gave myself a panic attack so I just went back to sense, lol.

ChacocII said:
heppened to me too and since then ive seen at least 5 cases of this exact same problem from cm7 roms. so far no one has found a way to fix it that has been posted here. we have all had to have our phones replaced.
Click to expand...
Click to collapse
And I just wanted to say, that although you've seen 5, and I've seen around 10, and that does suck, that the fact is, that this is an EXTREMELY low percentage of CM users that are experiencing this problem. With that noted, it's still enough for me to use a different rom, at least until someone can at least figure out what caused that to happen. I am just extremely curious, as to what the actual malfunction with the device is, when this sort of things happens. And why it seems to only be happening on CM. (at least from the reports I've seen around here)

Add me to the list of people with this problem. I think I'm going to try my chances at the Sprint store. They've been good to me so far.

k2buckley said:
I dont know what causes this, but this is like the 10th person on a CM rom that's had this exact scenario. Its weird how it happens out of the blue, and then RUU and pc36img just don't work. Very strange. I was just trying to help a guy the other day in this exact scenario. Nothing would get him out of the splash screen. No RUU, PC36IMG of recovery OR a factory ROM, fastboot RUU didn't work. Nothing. Just bricked at the bootloader somehow. I always thought if you could get to the bootloader then you could recovery, but lately there have been quite a few of this exact scenario, and each one was on the same rom. I would love to know what causes this, when the phone is just sitting there, and then goes into a bootloop out of the blue, and then this is the result. It's leaving me frightened to run CM, seriously. What on earth could be causing this type of thing?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
It has nothing to do with CM. It is clearly a hardware problem. It has happened on other roms, but more likely to happen to someone using CM as it is the most used Rom.
Sent from my PC36100 using XDA Premium App

Sorry to open this again, but I'm having the same issue. I'm actually on the HTC Sensation, but I'm posting this here because after hours of searching, this is the ONLY place that seemed to address this seriously.
The reboots began even on the original stock rom. I bought it from a guy on Craigslist, but I'm fairly certain it was the original stock rom, with S-off, unrooted, etc. I thought flashing other roms would help, but they haven't.
Here's my furthest observations thus far:
I have actually found a way to get out of this incessant boot loop. As you said, even recovery is impossible. I was so confused when everyone kept telling me to just go into bootloader mode and go to recovery. I can always get into bootloader mode, but recovery, as you guys said, is pointless, because it just boot loops.
However! I have found that if I leave the battery out for an extended period of time, maybe an hour to several hours later, upon inserting the battery back in, I'm able to load up correctly. But that doesn't last long. Usually I only get one chance. If I use that chance to go into recovery mode the next time it'll just boot loop again.
So now I really think it's something to do with the battery, because when I leave it out for a while, I can finally boot up the phone or get into recovery. I do know that HTC has that lame battery problem of boot looping when the battery is low, so do you guys think that it could be related to the battery stats? When my next "battery-free shift" is over, I'm going to try charging the phone and wiping battery stats.
Sometimes the other way I can get out of the boot loop is to charge the phone fully until it's green, so I'm just not sure. This is insane... any input at all would be greatly appreciated..

jkxklutz said:
Sorry to open this again, but I'm having the same issue. I'm actually on the HTC Sensation, but I'm posting this here because after hours of searching, this is the ONLY place that seemed to address this seriously.
The reboots began even on the original stock rom. I bought it from a guy on Craigslist, but I'm fairly certain it was the original stock rom, with S-off, unrooted, etc. I thought flashing other roms would help, but they haven't.
Here's my furthest observations thus far:
I have actually found a way to get out of this incessant boot loop. As you said, even recovery is impossible. I was so confused when everyone kept telling me to just go into bootloader mode and go to recovery. I can always get into bootloader mode, but recovery, as you guys said, is pointless, because it just boot loops.
However! I have found that if I leave the battery out for an extended period of time, maybe an hour to several hours later, upon inserting the battery back in, I'm able to load up correctly. But that doesn't last long. Usually I only get one chance. If I use that chance to go into recovery mode the next time it'll just boot loop again.
So now I really think it's something to do with the battery, because when I leave it out for a while, I can finally boot up the phone or get into recovery. I do know that HTC has that lame battery problem of boot looping when the battery is low, so do you guys think that it could be related to the battery stats? When my next "battery-free shift" is over, I'm going to try charging the phone and wiping battery stats.
Sometimes the other way I can get out of the boot loop is to charge the phone fully until it's green, so I'm just not sure. This is insane... any input at all would be greatly appreciated..
Click to expand...
Click to collapse
If its anything like the evo you might want to try and wipe cache and dalvik cache when you get into recovery let it boot back up if that doesn't work try to fix permission if that doesn't work wipe battery stats when your phone is at 100% using battery calibration app and if none of that works do a full wipe and flash a new ROM or unroot and run the ruu of the stock ROM .
Sorry I know nothing about that phone so IDK if any of that will work for you just trying to help and those are pretty much the steps I would take.
Sent from my PC36100 using XDA App

Happened to me
Hey guys this happened to me and i was running cm and sense roms i have had alot of experience with this and its an actual glitch that causes the os to stack on each other and confuse the boot the only way to fix is to wipe the entire phone back to stock if that dosent work call sprint and they gladly replace ur phone due to manufacture defect its been happening to unrooted phones also from the updatesnot being installed properly phone needs to be wiped every time u do a new rom

[Q] Boot Looping + No Recovery Access

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.

[Q] Boot Loop, no recovery.

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

[Q] Trouble with LG G2 (Sprint)

Hello Im Terry
Well this is far from my first root and flashing roms to phones....
i recently got a lg g2 sprint device 4.2.2, and of course i came here to root it, now the root was simple went through fine using a method i found here on the site... after this i wanted to put a different rom on it... well i installed twrp recovery, then i was trying to boot up into recovery, it wouldnt work at all whatsoever, wether i tried turning the phone off and holding the power and volume down button, releasing when screen turns on for a second then pushing them both again... this would just load the normal sprint screen, so i would try through the twrp program to reboot into recovery and the exact same thing happened.....so i googled it and i found this method to "supposably" fix it...
teamw.in /project/twrp2/197 <----- sorry about the space there but the forum wouldnt let me post the link and i cant describe what i did to cause my problem if i cant post this link.
i used the method here with the file for sprint phones.
now after doing this i tried to reboot into recovery mode using the power and volume down method, still nothing, so then i tried through the twrp program, well what happens is a screen comes up, which when ive searched this its only people that cant get past this screen and there phone is soft bricked.... [470] fastboot mode started and on the line under that it says [520] udc_start()
this is a black screen and it stays there.... now i found a file here that a guy put on the phone to help get wifi working, which i can be happy with the phone if i cant figure out how to put a rom on the phone if i can atleast be able to tether my phone since that is one of the main reasons i root, well when i tried to flash this file using the twrp program with the phone on it rebooted to the black screen with fastboot and udc_start
so basically i cant get into recovery mode at all, and i havent been able to this entire time, i could never even get to the initial sprint option to erase all settings holding those 2 buttons down.
now obviously i want to fix this, i want to figure out how to get into recovery mode. and i just got this phone from sprint 2 days ago so it already has the sprint spark update, im not sure if that what might be causing all of this if its incompatible with sprint spark or not... i know the 1 rom i looked into said it was incompatible with it, but i didnt see anything with the others....
so after figuring out how to get into recovery mode and fix my recovery mode can someone please tell me which of the roms that are currently out for my phone are compatible with sprint spark if any. thanks so much and i hope somebody can help me. have a great day and take care

well just a quick update, i uninstalled and reinstalled twrp now this is what i get when trying to boot into recovery from the app
[470] fast mode started
520 udc_start()
690 - reset -
700 -port change-
890 STALL GET_DESCRIPTOR 128 6 1006 0 18
60710 fastboot: processing commands

Trippinshrumes said:
Hello Im Terry
Well this is far from my first root and flashing roms to phones....
i recently got a lg g2 sprint device 4.2.2, and of course i came here to root it, now the root was simple went through fine using a method i found here on the site... after this i wanted to put a different rom on it... well i installed twrp recovery, then i was trying to boot up into recovery, it wouldnt work at all whatsoever, wether i tried turning the phone off and holding the power and volume down button, releasing when screen turns on for a second then pushing them both again... this would just load the normal sprint screen, so i would try through the twrp program to reboot into recovery and the exact same thing happened.....so i googled it and i found this method to "supposably" fix it...
teamw.in /project/twrp2/197 <----- sorry about the space there but the forum wouldnt let me post the link and i cant describe what i did to cause my problem if i cant post this link.
i used the method here with the file for sprint phones.
now after doing this i tried to reboot into recovery mode using the power and volume down method, still nothing, so then i tried through the twrp program, well what happens is a screen comes up, which when ive searched this its only people that cant get past this screen and there phone is soft bricked.... [470] fastboot mode started and on the line under that it says [520] udc_start()
this is a black screen and it stays there.... now i found a file here that a guy put on the phone to help get wifi working, which i can be happy with the phone if i cant figure out how to put a rom on the phone if i can atleast be able to tether my phone since that is one of the main reasons i root, well when i tried to flash this file using the twrp program with the phone on it rebooted to the black screen with fastboot and udc_start
so basically i cant get into recovery mode at all, and i havent been able to this entire time, i could never even get to the initial sprint option to erase all settings holding those 2 buttons down.
now obviously i want to fix this, i want to figure out how to get into recovery mode. and i just got this phone from sprint 2 days ago so it already has the sprint spark update, im not sure if that what might be causing all of this if its incompatible with sprint spark or not... i know the 1 rom i looked into said it was incompatible with it, but i didnt see anything with the others....
so after figuring out how to get into recovery mode and fix my recovery mode can someone please tell me which of the roms that are currently out for my phone are compatible with sprint spark if any. thanks so much and i hope somebody can help me. have a great day and take care
Click to expand...
Click to collapse
Since your phone is only new, have you tried calling the tech support of Sprint? Or have you tried going to Sprint store to help you out with that?

to the post above me... yea that sounds like a great idea, hey sprint can you help me root my phone so i can tether without you charging me? thanks guys!... can you please not troll? if you're not going to help you dont have to respond. Thanks!
so i followed this post now, what i didnt do was patch loki on the newer vza firmware.... so i followed this thread here which is supposed to fix that... and yet im still having the same thing, btw as i posted the change in commands before its because i had my phone plugged into my computer that it showed me that.
forum.xda-developers.com/showthread.php?t=2522965
im not sure what im doing wrong here, but as i go through this i will surely document it incase someone else runs into the same problem in the future.
thanks for any help in advance

i made a mistake when i was doing this.... after everything when it says to use flashify to find the file... it wants you to find what is now the updated twrp 2.6.3.3 version and flash that as the last step... this is now complete. if anyone else runs into this in the future hopefully you dont do something slightly stupid like i did. thanks again xda developers cuz your all some genius ass people with all this info here

Trippinshrumes said:
well just a quick update, i uninstalled and reinstalled twrp now this is what i get when trying to boot into recovery from the app
[470] fast mode started
520 udc_start()
690 - reset -
700 -port change-
890 STALL GET_DESCRIPTOR 128 6 1006 0 18
60710 fastboot: processing commands
Click to expand...
Click to collapse
Turns out you have to downgrade your ABOOT, I had the same problem .. ...
http://forum.xda-developers.com/showthread.php?t=2627765
Follow those instructions to downgrade to zv7-aboot.img, then use FLASHIFY to flash the TWRP recovery image .. ...

also, the problem i was having with booting into recovery is i just have to hold the power and volume down buttons till i get the recovery menu.... not let go when the light comes on like a bunch of things say....

also if anyone knows, it says the d3rp g2 rom doesnt work on spark that it will guaranteed brick my device, now i have it fully backed up and i could just do a test run and see... although i dont feel like having to mess with that....
has anyone successfully flashed d3rp to the spark version? and if that is incompatible none of the other roms mention anything about it.... so if someone could tell me which roms do work on the spark version i would appreciate that...
also +1 to the guy that offered help after i figured it out. i appreciate it!