Related
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
Hello All
I purchased a phone from a friend of a friend so I don't have all the history of the phone. It looks like they attempted to root it and failed.
I only got it to boot op fully one time. (and I can't get it to boot up fully again) It goes to the htc incredible logo and starts over.) So here's what I know. I didn't see a superuser apk the one time I got it to boot. It has the radio that ends in 07.28. It has s-on. It has a recovery but not one that I'm used to (like on ogdroid)
Its says android system recovery <3e>
reboot
apply update.zip
wipe/factory
wipe cache partition
and at the bottom
E: Can't open /cache/recovery/command
I've tried the unroot method to try to get it going, but no luck. I'm stuck. Any thoughts? Thanks for any help.
You can follow this thread, part 2
http://forum.xda-developers.com/showthread.php?t=786436
Basically, download this file
http://www.fourty.net/~berzerker/stockstuff/PB31IMG_3.26.605.1_RUU.zip
Rename it to PB31IMG.zip, put it on the root of your SD card, boot the phone into the bootloader (hold vol + & pwr when turning on) and let it update. It should return it to a completely stock 2.2 with no root. From there you can go root it or do whatever you would like.
Ok I tried that. The update goes through successfully but I'm still stuck in the loop.
Is there a way to root or get s-off with out booting the phone? (I'm using a mac)
this happened to me recently - I reloaded RUU - hard reset - removed sd - left battery out for a while - used my wifes battery - power plugged in - Wiped everything possible in cwr (before ruu)
The phone is completely stock and wont stay on for more than 5 seconds if it even gets to the lock screen at all. In the end I had to put s-on and request a replacement
one thing I did notice though (hope this helps) I left my battery out of the phone overnight and in the morning without power connected it did boot all the way and I popped on to the market and used the browser for about 15 minutes - then fell back in to a boot loop and I wasn't able to reproduce that working state again.
Incredible
Try looking for a Ruu to return it stock,
make sure you wipe all.
Sometimes it helps to be patient and watch out for heat issues.
Not sure if this is related but My Hd2 on 2.3 and Mytouch 4g on 2.3 would boot loop when it got a little warm Remove the batter and let it sit for 10 minutes.
Ok
It's back to stock. I still have the same issue. It is the same problem that h0x90 had. This phone isn't activated and I'm not sure if it has a warranty or not. I would rather try to fix it if I can. Can I root it with adb or otherwise in its current state? I wonder if a rom would fix the problem. It seems to be software and not hardware, correct?
Before I was desperate enough to wipe everything (ruu) I loaded several different roms and loaded my backups - so in my case it was a hardware issue.
Verizon told me they cover the phone for 12 months from purchase date - and they're overnighting a refurb to me for free which is nice. Maybe if nothing else you can get a hold of the previous owner and attempt to get a replacement.
Best of luck though either way!
nothing0 said:
Ok
It's back to stock. I still have the same issue. It is the same problem that h0x90 had. This phone isn't activated and I'm not sure if it has a warranty or not. I would rather try to fix it if I can. Can I root it with adb or otherwise in its current state? I wonder if a rom would fix the problem. It seems to be software and not hardware, correct?
Click to expand...
Click to collapse
As the Incredible hasn't been on the market for a year yet, it's assuredly still within the warranty period.. As for trying to fix it yourself, I can all but guarantee that you cannot since what you're experiencing seems to be a relatively common hardware failure.
I finally gave up. I did find out that PCD at 1.800.229.1235 does warranty work for HTC. Maybe that information will help others. Thanks to all that helped.
Ok I'm lost. I'm working today and my phone tries to reboot for no apparent reason and is put into a boot loop that I cannot get out of no matter what. In boot loader I have no recovery. Downloaded amon ra recovery's PC36IMG.zip. Booted into bootloader it said it updated the recovery but after I've rebooted I still have no recovery. I don't think this is very good.
Bootloader asked you to update and reboot and it went through completely?
Yeah, it said update was succesful. Thats why I'm so confused.
So when you go into recovery from the bootloader, do you see the triangle?
Nope just back to white screen boot loop. Trying to flash sprint lovers with the pcm36img over it maybe that will bring me back to stock rooted stat.
Edit: Back to white screen boot loop.
this same thing happened to me a week ago. were u running a cm7 rom?
yeah ex10 i was going to switch last night guess its too late
Damn I feel bad for you
I had that same problem when i first rooted and flashed my evo. I suddenly got into an infinite boot loop where i no longer had a recovery. Sorry man i had to take it to a sprint store after i tried flashing a different bootloader and then retry flashing a different recovery from clockwork to amon. and then even tried to flash the stock rom none work. if none of those work then you most likely is going to have to go to a sprint store.
Well, you could try running an RUU. This will leave you unrooted and completely stock so you will need to root again.
Here's a how-to over on Android Central.
http://forum.androidcentral.com/htc-evo-4g-rooting-roms-hacks/19278-how-unroot-return-stock.html
when this happened to me last friday i looked around xda and i found a couple other people who had this problem as well. everyone i found (myself included) was running a cm7 rom. i still cannot get any farther than bootloader without a white screen loop. sprint sent me a replacement on warranty because i live too far from the sprint store for them to make me drive there but i have to send my old one back. its still s-off tho and even running the stock ruu does nothing to fix that. anyone know of how to get s-on without the ability to enter recovery or anything else? or a way to brick it completely so it wont boot to bootloader where they can see s-off?
Threw mine out of the window of my car and called sprint and told them I lost it. Cost me $100 to get a replacement and now I'm going to have to spend forever getting back to root and eng boot ect... sucks.
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies? Because I'm really wanting to go to the CM7 nightlies but not if the chance this is going to happen again.
ChacocII said:
when this happened to me last friday i looked around xda and i found a couple other people who had this problem as well. everyone i found (myself included) was running a cm7 rom. i still cannot get any farther than bootloader without a white screen loop. sprint sent me a replacement on warranty because i live too far from the sprint store for them to make me drive there but i have to send my old one back. its still s-off tho and even running the stock ruu does nothing to fix that. anyone know of how to get s-on without the ability to enter recovery or anything else? or a way to brick it completely so it wont boot to bootloader where they can see s-off?
Click to expand...
Click to collapse
Does the bootloader let you run a PC36IMG.zip? If so, try running one (of a factory unrooted ROM), and when it goes to reboot and shows the green arrow facing down (if it gets that far) yank the battery at that point. I think that is when it's writing the radio image. If you can get it to that point, and then pull the battery, I'm pretty sure you'll have a brick. Aside from a battery pull during the radio flash, I'm not sure how to make a brick, without it being obvious of what you've done. You could rig your phone charger up to a 230 volt outlet from a drier or something, and plug it in. haha. maybe that would fry it, tell sprint you got a power surge when it was charging, and then it wouldnt turn on. (only 1/8 serious on that last part )
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies?
Happened to me with official cm7 rc1
Does the bootloader let you run a PC36IMG.zip?
yes, but it doesn't actually do anything. it will go thru the whole update process but still goes back to a white screen loop and no recovery. tried a battery pull during the radio update a couple hours ago (i thought the same thing) but it did nothing. i think its because its not actually doing anything when u run the pc36img other than going thru the motions on the screen.
maybe i can microwave it hahaha
edit: after a couple battery pulls during the radio update in the pc36img im using, it will no longer go thru the full radio update when running the zip so i definately screwed up the phone. it still gets to bootloader no problem tho so ive accomplished nothing.
ChacocII said:
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies?
Happened to me with official cm7 rc1
Does the bootloader let you run a PC36IMG.zip?
yes, but it doesn't actually do anything. it will go thru the whole update process but still goes back to a white screen loop and no recovery. tried a battery pull during the radio update a couple hours ago (i thought the same thing) but it did nothing. i think its because its not actually doing anything when u run the pc36img other than going thru the motions on the screen.
maybe i can microwave it hahaha
edit: after a couple battery pulls during the radio update in the pc36img im using, it will no longer go thru the full radio update when running the zip so i definately screwed up the phone. it still gets to bootloader no problem tho so ive accomplished nothing.
Click to expand...
Click to collapse
Damn, so you can still see s off? I have no clue how to get it to s on then, or make it so you can't even get to the bootloader. Yea, if you microwaved it (haha) i'm sure it wouldnt ever turn on again. However, whoever looks at it would be able to tell that something went very, very wrong, and it wasn't the phone's fault. ha. Maybe it won't even matter that it's s off. I've heard of people having luck with sprint looking at a phone that is s off, but I've also heard the oppositte (more often).
i actually told the sprint tech on the phone that i had rooted it and he still warranty replaced mine. im just hoping they dont change their minds when they get it back and see s-off and try to charge me 500 bucks for my new one.
Wow. Yeah, if it won't even run a PC36.img from bootloader, you're kinda SOL. That's pretty much a last resort. Granted, you should try a few different img's (different d/l sources) before assuming it's screwed. Sometimes, you can get a bad download. I had a stock Evo that wouldn't go into recovery, so I flashed a RUU from bootloader, and everything was fine. Best of luck with your replacement though, brother.
well i have 14 more days before i have to send it back. there must be some way to get it to not turn on at all without physical damage, just gotta figure it out.
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
Hey guys my verizon g4 is stuck in bootloop and im not rooted, i cant get the past the lg boot screen, it stays on their for around 20 seconds goes black and back to lg screen.
I can get into recovery but none of the options do anything ive tried safe mode, usb debug mode i even tried factory reset they all just go back to the lg screen.
I was just watching a video on facebook when it froze restarted and now im stuck, ive been restarting it all day and i was able to get it to boot up twice but it froze again within seconds any help is appreciated
it might be the defective motherboard issue that people are having. you could try reflashing the system, but if that doesn't work you probably need a new motherboard/phone
Not an answer, but an experience.
I have an HTC ONE M8, VZW. I s-offed it and rooted it right when I got it. I began adding some of my google apps and it did what your G4 is doing, stuck on VZW screen.
Since I was s-off I was able to get a recovery in and ready. I was able to get a custom rom onto the phones external sd. I flashed it with the recovery and the flash took, no more vzw screen lock up.
Your experience makes me wonder what VZW is doing to force bootloops on unlocked or rooted phones with their retail products. Paranoid maybe, but I can see VZW deliberately adding code to stick it to rooted users.....................................I say this still knowing that many have rooted the current run of devices without issues...........................
luck
i read about the problems with the motherboard going bad, im assuming thats what happened to mine. Lg sent me a replacement under warranty
Update!
i called verizon they sending me a replacement. just to let you know i flashed 13B KDZ but the bootloop was still there i let my phone on and finally turned on quickly i did a factory reset and booted up normal and its working again. still im gonna send it back. just sharing my experience maybe for other people might work too.
killa408shark said:
Update!
i called verizon they sending me a replacement. just to let you know i flashed 13B KDZ but the bootloop was still there i let my phone on and finally turned on quickly i did a factory reset and booted up normal and its working again. still im gonna send it back. just sharing my experience maybe for other people might work too.
Click to expand...
Click to collapse
What is the 13B KDZ and how did you flash it? Im having same exact issue.
My G4 tanked over the weekend. I was browsing news and the phone locked up, then it shut off and turned back on. It just bootloops now. If I stick it in the freeze for a few minutes, sometimes it will boot to the OS where it starts to optimize the apps. It will get through about 20 before it shuts off and starts the bootloop process again. I haven't even been able to get the download mode to stay on, and when it does enter download mode, it is not detected by the computer. I think my problem is the motherboard. I'm just hoping that they aren't able to figure out I had it rooted!
I'm still waiting to hear back from Verizon about a replacement.
Does anyone have any ideas on how I can flash a stock rom back on this thing to try to save my tail? I am betting not since the phone won't stay on long enough to even flash the rom.
b3y0ndd34th said:
My G4 tanked over the weekend. I was browsing news and the phone locked up, then it shut off and turned back on. It just bootloops now. If I stick it in the freeze for a few minutes, sometimes it will boot to the OS where it starts to optimize the apps. It will get through about 20 before it shuts off and starts the bootloop process again. I haven't even been able to get the download mode to stay on, and when it does enter download mode, it is not detected by the computer. I think my problem is the motherboard. I'm just hoping that they aren't able to figure out I had it rooted!
I'm still waiting to hear back from Verizon about a replacement.
Does anyone have any ideas on how I can flash a stock rom back on this thing to try to save my tail? I am betting not since the phone won't stay on long enough to even flash the rom.
Click to expand...
Click to collapse
+
My phone was rooted and got into the bootloop also and I sent it in as is and nothing happened. So I think it would be fine to send it without the stock rom.
mainlygreen said:
+
My phone was rooted and got into the bootloop also and I sent it in as is and nothing happened. So I think it would be fine to send it without the stock rom.
Click to expand...
Click to collapse
Thank you for this information, this makes me feel a little better!
The replacement is already in the mail!
same issue of mine I was out then it cut off & wouldn't come back on but now it charges up & makes it to the boot screen
b3y0ndd34th said:
Thank you for this information, this makes me feel a little better!
The replacement is already in the mail!
Click to expand...
Click to collapse
did you send the faulty unit first or they are sending it on your complaint. I am outside US and my G4 got bootloop issue n i was wondering how to get the replacement through somebody as i wont be coming for another year.
thanks
bhuvesh89 said:
did you send the faulty unit first or they are sending it on your complaint. I am outside US and my G4 got bootloop issue n i was wondering how to get the replacement through somebody as i wont be coming for another year.
thanks
Click to expand...
Click to collapse
They mailed me a new one, no battery, no back. I put my battery, sim card, sd card, and back on the new phone, fired it up. Rolled it back, rooted it, then I mailed the old one back.
Personally, I love this phone, but I think I will be getting a nexus next.