I'm hoping I did not brick this thing because I literally just got it replaced because of screen issues and a blown speaker and broken usb port. Anyway, got the replacement home and wasted no time to use unrevoked 3 on it. Worked great. installed Fresh Evo Rom 4, installed perfect. Tested - working fine. Then I tried installing the Radio, Wimax, NV, and PRI updates. Radio and Wimax installed correctly. Went to install the NV and PRI updates and it just said installation aborted ( I was driving to pick up dinner for the family so I just let it run for a few minutes then checked on it). I then decided to just restart and start putting in my contacts and stuff. It restarted to a screen with a box and what looks like a droid jumping out of it. Removed the battery and tried again after a minute or so, same thing. Tried the VOL - and Power method to boot into Hboot, same screen. Removed my SD card per some instructions on here , same screen. Replaced the battery with another one I had per some people getting the same issue here , same thing. Frustrated I ate dinner and came back to it. Now it wont turn on at all. No charging LED light at all. Tried both batteries, one red and one black, no go. Doesnt boot at all and doesnt look like its charging. Am I royally f*kt ? Anyone have any ideas for me to try ?
From what you said...yes....I guess its time to plead ignorance and get another replacement
Sent from my nightly EVO
So what went wrong ? I've done this same method about 6 other times with my previous phone and friends phones with absolutely no problems. Any insight so this doesn't happen again ? I'm on my way through traffic to a sprint store to pick up another one and want to root it but not brick this guy too.
My guess would be that it was either interrupted or a bad install...I really couldn't tell you though
Sent from my nightly EVO
tayden812 said:
I'm hoping I did not brick this thing because I literally just got it replaced because of screen issues and a blown speaker and broken usb port. Anyway, got the replacement home and wasted no time to use unrevoked 3 on it. Worked great. installed Fresh Evo Rom 4, installed perfect. Tested - working fine. Then I tried installing the Radio, Wimax, NV, and PRI updates. Radio and Wimax installed correctly. Went to install the NV and PRI updates and it just said installation aborted ( I was driving to pick up dinner for the family so I just let it run for a few minutes then checked on it). I then decided to just restart and start putting in my contacts and stuff. It restarted to a screen with a box and what looks like a droid jumping out of it. Removed the battery and tried again after a minute or so, same thing. Tried the VOL - and Power method to boot into Hboot, same screen. Removed my SD card per some instructions on here , same screen. Replaced the battery with another one I had per some people getting the same issue here , same thing. Frustrated I ate dinner and came back to it. Now it wont turn on at all. No charging LED light at all. Tried both batteries, one red and one black, no go. Doesnt boot at all and doesnt look like its charging. Am I royally f*kt ? Anyone have any ideas for me to try ?
Click to expand...
Click to collapse
Whenever you flash a radio, NV, or PRI or something like that, when you first flash it, it then tells you that you need to reboot to complete the installation. When it reboots, you will see that odd screen, which will either be an arrow facing down with a phone, an arrow with a box, or some kind of a droid guy with a box or something. That is very important to not pull the battery during that phase (it's when it's actually writing the radio, or pri, or whatever), otherwise a brick is the result, 99% of the time. Never pull the battery during any kind of a radio flash whatsoever. As far as why it told you that the installation was aborted, I've got no idea on that one. Maybe the file you were trying to flash was corrupted, or something to that nature.
If you're sure the battery is charged up, yet you get no LED light when the phone is powered down and plugged in, the phone won't boot to the bootloader, and seems completely unresponsive, then you are most likely indeed bricked. Sorry for the bad news. Don't pull the battery during any kind of a flash, especially a radio, pri, wimax, hboot, recovery flash etc. Battery pull during flashing of important things = bad idea.
EDIT: after thinking about it for a few minutes, after you updated your radio and wimax (which you said updated successfully), did you complete the installation by rebooting? After you flashed the radio, did you reboot, and see the black screen with an arrow coming out of a box, or something like that (that screen varies based upon your hboot version or recovery version)? If not, and you just tried flashing all of them, one after the other, without rebooting inbetween each one...then that may be why the installation of the pri aborted. Then when you went to reboot, it tried to finish the installation of the radio and wimax (which if you didnt reboot initially after selecting to flash, those installations would not have been complete, so as soon as you tried to reboot, it'd have tried to finish writing the radio image, which appears to be where you pulled the battery out)
If I remember right, that screen is part of the radio update. After it flashes, when you reboot you will see that screen. You're supposed to wait until it finishes and it should send you back to the recovery screen. After that you can reboot into the rom.
I'm scratching my head though because you said the installation aborted. Maybe part of it flashed successfully but the rest didn't?
EDIT: Didn't see that the radio flashed successfully. If you can still get to that screen, letting it run it's course should eventually solve the problem.
EDIT 2: K2buckley beat me to the punch. At least I know I was right and not giving you wrong info. Sometimes it takes pulling the battery 20 or so times to actually brick the phone, so hopefully you can still recover.
My Evo + xda Premium App = This post.
Thanx for the quick responses. After the radio and wimax update it went back to the install from zip screen in clockwork. From there I ran the other update. I let it sit on that installation aborted screen as I was driving. I ran in , grabbed dinner, came back within 5 minutes and it was still on that screen. Thats when I figured I'd just put contacts and stuff after I remove the battery. Still didnt work. If I indeed "bricked" this phone, is there any way ANYONE can fix it ? HTC or otherwise ? BTW - I already bought a new phone. Just scared to root and stuff now. I mainly want root to put in ROMS that have better battery life. Although now I have 3 batteries for it because of this brick lol.
tayden812 said:
Thanx for the quick responses. After the radio and wimax update it went back to the install from zip screen in clockwork. From there I ran the other update. I let it sit on that installation aborted screen as I was driving. I ran in , grabbed dinner, came back within 5 minutes and it was still on that screen. Thats when I figured I'd just put contacts and stuff after I remove the battery. Still didnt work. If I indeed "bricked" this phone, is there any way ANYONE can fix it ? HTC or otherwise ? BTW - I already bought a new phone. Just scared to root and stuff now. I mainly want root to put in ROMS that have better battery life. Although now I have 3 batteries for it because of this brick lol.
Click to expand...
Click to collapse
Unfortunately, if its bricked there's nothing that can be done. Since it doesn't turn on, sprint wont be able to tell it was rooted. Just be sure your SD card is "clean", and take it to sprint. See what they say about it. I'd just tell them it wont turn on. Still under 1 yr warranty...
Sent from my PC36100 using XDA App
Great idea. Never even crossed my mind to take it back. I know if they know its rooted they wont touch it which is why I was hesitant to take it back. I'm gonna try that tomorrow, thanks.
BTW - Any suggestions as to a ROM and kernel for absolutely the best battery life without sacrificing any of the Evo's stock options ?
Again, thanks for all the help guys.
Related
He ran the original OTA update the day before yesterday, he didn't run it twice like everyone else that had issues.. He's not bricked in the "won't power on or boot" sense of the term, it WILL boot up. But it's pretty much completely unusable, it keeps trying to remove and install widgets on its own, the touch screen does the opposite of whatever he touches, swiping between screens hangs and sits in between each screen, it keeps opening the htc weather widget and won't let you back out of it.. voice search keeps popping up randomly. It tries to install the htc coin flip widget, a lot. It basically takes 5 to 10 tries to get anything to work right, and when something does work right it's only for a minute.
He wasn't rooted in any way, and he tried doing a factory restore through the settings menu, as well as formatting the sd card.
Radio shack has no eta on a replacement and sprint says to just return the phone and get a different kind of phone if they are out of evo's (seriously..? wtf).
You guys are smart, is there anything he can do to try and troubleshoot this?
there currently isnt a way to root after the ota update, so the suggestion to try some cooked roms is out the window.
i dont want to be the bearer of bad news, but it doesnt look good.
I think he can try restoring to factory.
Download this:
http://www.joeyconway.me/evo/stock/...Radio_1.39.00.05.31_release_171253_signed.zip
Rename it PC36IMG.zip and put it on the root of the SD card.
Turn off the phone, hold volume down and turn it on, it should boot into hboot, sort of a factory recovery
It will automatically detect the zip file and ask if you want to apply it. Select yes, and it should restore to factory.
If you continue to have problems, then there is probably something wrong with the phone and it'll need to be returned.
Hope this helps!
Could this in anyway void my warrenty or make sprint un-willing to give me a new phone/ repair my phone if this fix does not work?
if that is stock, they would not be able to find out even if it further messed up the phone by attempting that method
...err taking a look, if he has the newest ota, then I am not sure if that link will work because it is a lower version. you would need to find the one that is for 1.47...
I am not even sure if that would work, but hey it is worth a shot if the phone doesnt work already
Use this ruu
It'll bring you back to stock with the latest OTA included.
So I flashed the Deodexed version of the new stock 3.70 ROM this weekend and it re-booted with no problem. I played with it for a few minutes, and then went back into Recovery using CWM and flashed the Radio/WiMax combo and it flashed unusually quick. The on screen message then prompted me to Re-boot to complete initialization or something to that effect. So then I re-boot and it takes a second for the screen to shut off like usual and then where it normally brings up my splash screen it brings up the little cigarette looking box with the arrow pointing towards the Android guy standing outside the box and the RED TRIANGLE image. I didn't panic and did a battery pull as I have had this happen once before. I put the battery back in and try to power on and the same image pops up. I did a battery pull again and tried to turn on the device in Hboot mode and then something bad happened, the same image popped up again. FML. I have waited 24 hours and attempted to go back into HBoot and the same thing happens over and over. I downloaded both the ROM and the radio/wimax file from my phone, but I did notice the Radio/Max file downloaded unusually quick ( Bad download maybe???) and I also performed a NANDROID back up but without being able to access my HBOOT, it's pretty much useless to me. Needless to say, I am currently the owner of a $500 dollar paper weight ( A very nice one might I add). I do have insurance and can make a claim if need be. But I would really like to avoid having to pay the deductible if at all possible. I have used these forums religiously and am now hoping that some kind soul might be able to save me from the depths of BRICKED EVO HELL. Any links to a guide or input on correcting the problem would be greatly and absolutely appreciated. Or if you just want to be brutally honest and tell me my EVO is doomed from now until eternity I would appreciate it also... Thanks for reading if you made it this far and I anxiously await any and all responses
Well hopefully u didnt screw up the phone by pulling the battery put that sign with the arrow pointing down is just writting the new radio down on the phone just let it set for awhile takes a good 5 min the most
Have you tried to boot up the phone without the SD card?
Edit:
Sorry for the short response but I said that because I believe that the CWM recovery is stored on the SD card or at least part of it. Maybe that'll work. If not I'll try and think of something else.
WOW... SMH
Words can not express how much of an idiot I feel like right now. I have never flashed a radio and did not realize that image was indicating writing of the radio. If I just bricked my phone because my dumb ass didn't do it right... I have flashed countless times and always made sure to feel comfortable before doing so and now this happens. My phone is in my car and im here at work. Do you think I should just power on the device and let it sit there at that image or what? I hope pulling the battery in the middle of instillation didn't brick it forever. Damn, I am so pissed at my self its not even funny
Try that. If that doesn't work maybe you can have someone upload the files you need to place on your SD card for CWM. You can pop out your SD card and place it into a reader/laptop and delete the ClockWork folder and replace with the new files.
Hopefully someone with more knowledge can lend their expertise but that's just some things I would try if I were in your situation.
My guess is that you can turn it on but it probably won't do anything because you popped the battery out mid cycle instead of waiting. Hopefully it picks up from where the installation left off but I doubt it.
::: By doing that you'll delete your backup so I'd recommend placing that file somewhere on your computer :::
Pimp. I had the same thing happen to me, I flash the newest 3.70 update and it change everything and I could not go back to my old nandroid so, all I did was flash the sprint lovers with the 3.30 update. It cames with evrythign you need. I hope that this helps you. Put this on the root of the sd card and than press the - volume button and the power button, the phone will look for the pcm36img.zip.and update.
http://www.megaupload.com/?d=D454VSVN
whooo...(huge sigh of relief sound)
So pretty sure I just took a smoke break and went and got my phone. Turned it on, let it sit there for about three minutes, it went through two boot loops ( I was biting my nails ) and then it finally booted up into the new stock ROM ( Thank god ). Thanks for everyone's responses as I had no idea that image was indicating a process on the phone and I thought it was an error message. But you live and you learn, I will try to delete this thread so it doesn't take up any more space. Or maybe leave it up in case someone has a similar problem.. Either way, whatever the moderators want is fine by me... Thanks again a million...
You very likly screwed up your RSA keys for 4g. That happened to me when I pulled the bat as it was writing the radio.
Only way to get those back is via nandroid restore (and hope you have amanra 1.8)
DAMN
You are correct my friend. Everything is fully functional but 4G and I dont use Amon RA, im a ClockWork man. It keeps saying scanning, connecting to sprint, and where it normally says obtaining IP address it just starts saying scanning again. It does this over and over until I turn 4G off. Should I just re-flash the radio/wimax .zip or what? Any links to a guide would be greatly appreciated. So looks like my phone isn't bricked but 4G is broken, so goes the life of a MODDER... SMH
Through adb shell check /data/misc/wimax and do an ls there.
If it is creating a file called 0016......tree.xml, basically a number other than your wimax MAC address (located under battery on sticker) then you have the same problem I did.
There is a thread on XDA that allows you to verify your wimac MAC.
http://forum.xda-developers.com/showthread.php?t=715525
Basically, I deleted the *.tree.xml files that were in my /data/misc/wimax
I did the fastboot process and corrected my wimax MAC.
After I did that, and I verified that it was correct by rebooting phone and turning on 4g. This created a new file in /data/misc/wimax that was my actual MAC address.
It was still stuck scanning. Looking at logcat I saw that the RSA keys were invalid.
Luckily I had a backup of a past rom where 4g was working. Amonra 1.8 includes the wimax partition and gets your RSA keys. I don't know if clocks does that.
I restored that backup, booted up and 4g would connect and work.
Having a problem here. Today I got a refurbished dinc, and tried to root w/ unrev. 3.2 and it went all the way through the process up to the point where it says waiting on reboot (could take 5 mins.) After that U.R said it lost its connection with the phone and rebooted. since then its been stuck in boot loops. S-off was never achieved and clockwork wasn't installed. I've tried resets and a 2.2 pb13img and nothing can stop the loops. Once in a while of random resets and fumbling around in the stock recovery it will boot to the phone program screen to call *228. It reboots and loops right after it goes to mount storage. I've tried taking out the card thinking it might be that.
It's a amoled screen.
I've rooted before and have no issues on my other dinc.
Plz help.
Sent from my ADR6300 using XDA App
riley614 said:
Having a problem here. Today I got a refurbished dinc, and tried to root w/ unrev. 3.2 and it went all the way through the process up to the point where it says waiting on reboot (could take 5 mins.) After that U.R said it lost its connection with the phone and rebooted. since then its been stuck in boot loops. S-off was never achieved and clockwork wasn't installed. I've tried resets and a 2.2 pb13img and nothing can stop the loops. Once in a while of random resets and fumbling around in the stock recovery it will boot to the phone program screen to call *228. It reboots and loops right after it goes to mount storage. I've tried taking out the card thinking it might be that.
It's a amoled screen.
I've rooted before and have no issues on my other dinc.
Plz help.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
What is your HBOOT version?
Hboot 0.92
Radio 2.15.00.07.28
Clockwork 2.5.1.2
Un.Rev. 3
Un.Rev. Forever
Incredibly re-engineered 2.2
Update -
Managed to get Un.Rev. to install with cw. And installed a Rom. Now I still get random reboots. Everything will be fine...ill update and install a bunch of apps. and I can use the phone for a while. Then all of a sudden it reboots over and over. To get it to stop, I have to re-do everything. Wipe cache, wipe dalvik, wipe battery stats, data/factory reset. I get an error after dalvik clear though "can't mount /dev/block/mmeblk12 (file exists)"
That puts me to square one.
Everything will be ok and then.....reboots...randomly at different points. sometimes right away and some times after an hour or two. No real pattern. I have a gut feeling it has to do with onboard memory?
Are you overclocking? What kernel are you using?
Try installing a different kernel, make sure it is a sense based kernel as you are using a sense based rom.
You can pick one from here - http://forum.xda-developers.com/showthread.php?t=866736
No I'm not over clocking. And I'm using the kernel that came with the Rom.
I do, however, seem to remember reading something about dincs overheating and rebooting until they cool. Maybe this is the case with mine.
I had the exact same issue when i received my refurbished phone. It is not uncommon that these issues - and others, will occur. Even before rooting i was having the issue.
I did notice that it will happen when i pushed the phone a bit, like talking and trying to download something from the market at the same time.
My suggestion is to unroot, everything stock, test the phone and see if it happens again. The Verizon representative tried to reset the phone and it started boot looping right in front him! And then they order another refurbished phone, which also had issues. Long story short, they gave me a new phone after i begged. (thank u VZ local store, which btw i sent a few customers your way )
According to some inside people i talked to, the 3rd party companies (or individuals) that fix these phones do a terrible job at it and the Verizon stores see quite a few people everyday with similar issues. I have no way of verifying this, just what i was told.
riley614 said:
No I'm not over clocking. And I'm using the kernel that came with the Rom.
I do, however, seem to remember reading something about dincs overheating and rebooting until they cool. Maybe this is the case with mine.
Click to expand...
Click to collapse
I would still try another kernel first, HeyItsLou or Ziggy IMO. If you still have the problems then, flash back to complete stock and take it to Verizon.
Yea, ill give that a try. If I have no luck, ill send it back. After unrooting of course.
Sent from my ADR6300 using XDA App
Riley, were you able to fix it? I'm really interested in some analysis of the problem and investigating issues with refurbished phones boot looping. Someone else just posted a similar problem.
Nah. No luck here. Still randomly looping. Nothing seems to have an effect in when it why it loops. It'll loop even w/o any apps installed.Even after a "fresh" install of a rom and system wipe.
Gonna send it back.
riley614 said:
Nah. No luck here. Still randomly looping. Nothing seems to have an effect in when it why it loops. It'll loop even w/o any apps installed.Even after a "fresh" install of a rom and system wipe.
Gonna send it back.
Click to expand...
Click to collapse
Sorry to hear that, as i said i had the same issue and i had to get another one. if you get a second "lemon" refurb go to Verizon and talk to a manager. They might do an out of the box replacement and put it in the system as defective under warranty. Good luck.
My battery indicator gets stuck so that it does not show battery drain.
When I unplug from my AC wall charger in the morning it stays at 100% all day long, unless I reboot my phone or connect to my computer via USB. Rebooting the phone causes it to show a reasonable battery level, but connecting it to computers via USB has the weird effect of making the battery level show a gradual decrease, even though I think it is charging! Connecting it to the wall charger just makes the level go up from wherever it currently is, and does not seem to trigger the reevaluation of current battery level. I tried loading the app "Battery Indicator" and it showed the same results as the stock indicator.
It has been happening for a couple months now, but I'm not sure if it has anything to do with Verizon's Nov OTA update (which I had to do manually because I use PagePlus Cellular, or because I'm rooted, or something). I have tried multiple batteries, and I even tried restoring my phone back to right after the Nov OTA using a Nandroid backup. I was tempted to restore the pre Nov OTA Nandroid bkup, but was scared of bricking my phone.
It's a rooted S-off DINC, software version 3.26.605.1, and I'm just running the stock ROM, Kernel, etc. Nothing fancy here, and the only apps I have that require root are Ti Backup Pro, Root Explorer Pro, and AdFree. My wife has the same phone & setup and does not have the problem.
It's a refubished phone and it came with a Motorola wall charger instead of a DINC charger, as did my wife's.
Any ideas on whether this is a hardware or software issue, and how I can resolve this?
btw, this is an awesome forum/community and I really appreciate all the hard work put in by developers, super users, and other nice people.
I would do part 2 in this guide to get back to comeplete stock, no root.
http://forum.xda-developers.com/showthread.php?t=786436
Just copy the at PB31IMG to the root of your sd card, boot into bootloader and let it update from there. Then see if the problem still persists, if so, take it back to verizon for a new one.
If the battery starts working normally, then re root it, and lets us know if the problem comes up again after re rooting. (it shouldn't)
Have you tried clearing battery stats thru clockworkmod? And fixing permissions they rom manager?
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.09.01
g00s3y said:
I would do part 2 in this guide to get back to comeplete stock, no root.
http://forum.xda-developers.com/showthread.php?t=786436
Just copy the at PB31IMG to the root of your sd card, boot into bootloader and let it update from there. Then see if the problem still persists, if so, take it back to verizon for a new one.
If the battery starts working normally, then re root it, and lets us know if the problem comes up again after re rooting. (it shouldn't)
Click to expand...
Click to collapse
I went back to complete stock per your instructions, but unfortunately it didn't do the trick.
I have now gone back to my Nandroid backup, and I'm hoping something else comes along because I can't take the phone back to Verizon. I bought it from ebay from a seller that refurbishes them, so I guess I'm stuck with the phone. At least it's not a huge problem.
Thanks for the suggestion and the link. Any other suggestions would still be welcome.
rigman said:
Have you tried clearing battery stats thru clockworkmod? And fixing permissions they rom manager?
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.09.01
Click to expand...
Click to collapse
Thanks for the suggestions. I forgot to mention that I have tried clearing the battery stats thru clockworkmod, but that didn't fix the problem.
I don't have rom manager. I don't know much about it, but do you think that might help, given that going back to stock did'nt work? If so, is it pretty self explanitory (if I download it from the mkt)?
I would just pick an established ROM, do a wipe with recovery and install the ROM.
I highly recommend ROM Manager since it is a one stop way to install the ROM. Just put the ROM on your SD card, start ROM Manager, pick install from SD Card, select the ROM, choose wipe and OK
Yeah since you bought it off of ebay you can't take it back. Have you tried a program like battstatt? Install that and see if that will give you the correct percentage. I know it doesn't fix your problem, but if that always says 100% then it isn't a rom problem but a hardware problem i would think.
I have tha same problem, only solution is moded battery indicator with percentage, works flawlessly.
nedooo said:
I have tha same problem, only solution is moded battery indicator with percentage, works flawlessly.
Click to expand...
Click to collapse
Thanks! I have tried a couple with no luck, so I'm glad to hear there is one out there that will work. Can you please let me know which app worked for you?
I had cyanogenmod 7 installed on my EVO and one day my phone just turned itself off. This time it will only boot up to the white HTC EVO screen then power itself back off and continue to cycle. I loaded into bootloader and tried to go into recovery. As soon as I select recovery it goes right back to the white screen and continues to loop. I tried to clear storage and recieved the same results. I searched a tone online and tried to find a resolution. As far as I can get is install the boot interface driver and HBOOT USB the phone. All root programs get stuck at the "waiting for device". Any help would be much appreciated.
Drake13 said:
I had cyanogenmod 7 installed on my EVO and one day my phone just turned itself off. This time it will only boot up to the white HTC EVO screen then power itself back off and continue to cycle. I loaded into bootloader and tried to go into recovery. As soon as I select recovery it goes right back to the white screen and continues to loop. I tried to clear storage and recieved the same results. I searched a tone online and tried to find a resolution. As far as I can get is install the boot interface driver and HBOOT USB the phone. All root programs get stuck at the "waiting for device". Any help would be much appreciated.
Click to expand...
Click to collapse
sorry but you're pretty much S O L on this, has something to do with a bad boot.img and you can't get it to take another one might as well file a lost phone claim and pay the $100 and get a new one thats what i had to do and they just happened to have sent me the 3d instead so i guess i got a bit lucky.
i still have my evo 4g and still working on it but its been about a month and i haven't had any luck with it.
Sounds like you have no recovery or not completely rooted. You could try to put a recovery CWM or Amon-Ra file renamed PC36IMG.zip onto your sd card from your computer, put card back into phone then go in to hboot see if it will flash you a recovery then try to go into it
If that doesn't work search for a stock ruu file for the Evo, rename PC36IMG.zip, place on your card, put card back in phone, flash through hboot. This will return your phone to stock unrooted, then you try the process again
Sent from my PC36100 using XDA Premium App
That's what happened to my phone also..It just happened out of nowhere..
I tried everything and in the end I had to file an insurance claim.
And once again, a phone running CM7 goes into this mysterious unfixable bootloop.
What is up with that?
What is up with that, I'm about to remove this rom its not really all that. Its already messed up my keyboard, sometimes I have to take the battery out just to restart it.
I Loved CM7 when I had it, but then i started seeing all these bootloop issues start up in the early part of Summer, and I refuse to put it back on. Sorry to those that dev and support it, but seriously, out of all the cases on here, and there have been a bunch, only one was on a phone that didn't have CM7 on it.
HipKat said:
I Loved CM7 when I had it, but then i started seeing all these bootloop issues start up in the early part of Summer, and I refuse to put it back on. Sorry to those that dev and support it, but seriously, out of all the cases on here, and there have been a bunch, only one was on a phone that didn't have CM7 on it.
Click to expand...
Click to collapse
Most of those phones from the 'CM Scare" had bad nand blocks, and it had to be replaced. They had them frothe very beginning, but just decided to act up then. It also happen to some users using MIUI.
Okay my speaker got distorted so I decided to unrooted to take it in for service. Now the phone is unrooted but theres only one problem! Now the phone will boot up to the normal home screen but within 2 to five minutes, it shuts itself down and boot back up to home screen again and the cycle starts again. I have reset few times but same ting' happens. Now sprint is ordering a new phone for me hope its not the 3D i don't think I like it. So now I have my evo still but will give it to sprint once my new phone is in at the sprint store tuesday! Oh by the way, beside the speaker problem the phone was working fine as normal before the unrooting. thx
teh roxxorz said:
t also happen to some users using MIUI.
Click to expand...
Click to collapse
No! Don't say that!!
tony_2018 said:
What is up with that, I'm about to remove this rom its not really all that. Its already messed up my keyboard, sometimes I have to take the battery out just to restart it.
Click to expand...
Click to collapse
I've been using CM for about a year and NEVER had either of those two problems. There has to be an issue with something else you've loaded onto the phone that isn't playing nice.
Concordium said:
I've been using CM for about a year and NEVER had either of those two problems. There has to be an issue with something else you've loaded onto the phone that isn't playing nice.
Click to expand...
Click to collapse
No one ever said every install of CM7 will lead to this bootloop, but almost every case of this bootloop, the user was running CM7
HipKat said:
No! Don't say that!!
Click to expand...
Click to collapse
Miui is based of cm's fixes and what not right?
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
No, MIUI is not based on CM. It's a completely different ROM
Yeah but I'm pretty sure they use their fixes since its a port
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
It's true that most of the cases happened on CM7, but from what I understand it can happen on any rom... and has happened on Sense and AOSP.
There's no known fix. You can try to RUU, but even if the RUU flashes properly, the phone will never boot. You're eternally stuck with hboot/fastboot. File an insurance claim, that's about all you can do. I had a similar problem with a stock, never-been-rooted Evo. I got a replacement through insurance without paying the deductible, but I was s-on.
Hopefully I don't get slammed for suggesting this, but if you don't want to pay the deductible for a "lost" phone, you can flash a radio through hboot and pull the battery. If you do it at the right time, the phone will completely brick and never turn on again. It may take a few tries. Then you can take it in and you shouldn't have to pay the deductible, as long as you play dumb of course.
I think this happens due to bad nand blocks on your boot partition, so the main cause is hardware. Something in the rom triggers the never-ending splashscreen bootloop (I'm assuming something related to the boot.img). I could be entirely wrong about this though.
You can't live in fear, if it happens it happens. It's one of the risks you take when rooting and flashing. The number of cases is small compared to the number of people with rooted Evos, especially considering only a portion of people are active on this site, and a lot of the reports come from members that wouldn't post or even be a member if they didn't have the problem. I wouldn't let the possibility deter you from running whatever rom you want.
Sent from my Evo + MIUI using Tapatalk!
I myself am stuck with same issue. Nothing takes. So where does hboot reside when loaded? I also have looked in vain for diagnostic flashes....
Now one thing I noticed is that I installed PDAnet and it shows it installed an app to the phone, however I cant connect. I think cause I cant boot the phone and enable what it telling me to...so how is it this software can load an apk and I cant?
Overall, I am now however learning and it has become a hobby.
Theres an answer somewhere I would think. Thinking maybe its time to tear apart and look for jtag points....
I have had this happen to me a few times, I leave the RUU on the sd card and when this happens and do what bimmerman7 wrote on the first page. This has always worked for me when I get stuck in a bootloop when trying to access recovery.