Related
I know this is a common problem as I've seen it in other threads on other sites, but I haven't been able to find a cause/solution. My Evo 3D randomly reboots, frequently. It has happened with every firmware version since I got the phone, and with every rom/kernel I have installed. It doesn't seem to be an overheating issue. I've tried uninstalling a few apps to see if they might be the cause. Basically I'm ready to call it a hardware defect. Does anyone have any idea what causes this or how to fix it? I bought my phone unsubsidized online so it isn't easy to return, but I may have to try anyways. My 3D is useless as it is right now.
Return it.....
Sent from my EVO3D
I bought it from eBay so that's not an easy return. HTC wants me to pay to ship it to them and they want my credit card number, then if they decide it's not an issue covered by warranty then they will charge me both for looking at it and also to send it back. Basically they will hold my phone hostage if they decide they want money from me. I have filed a complaint against HTC with the Better Business Bureau over their warranty policy.
If on stock ROM, return it. Sometimes on custom roms it reboots like crazy for me when using browser.
It reboots on stock and custom roms.
Return it...
I've talked to three people at Sprint and they won't accept it as a return. They say I have to take it back to the store it was purchased at, and though I've talked to the person I bought it from, he's in another state, so Sprint says I'm SOL.
SeeNev said:
I've talked to three people at Sprint and they won't accept it as a return. They say I have to take it back to the store it was purchased at, and though I've talked to the person I bought it from, he's in another state, so Sprint says I'm SOL.
Click to expand...
Click to collapse
Try different Roms. My buddies had the same problem. Flashed supra and flashed silver needle kernel. Flashing a custom kernel can easily fix it. The stock kernel argues with the stock OS and the phone is tricked into thinking there is harm. Therefore reboots to try and save your phone from any damage. For sure switch the rom and kernel.
Sent from my PG86100 using Tapatalk
I reboot alot also and its been on all my roms and stock but better now on synergy rom
Sent from my PG86100 using XDA App
tnh196 said:
I reboot alot also and its been on all my roms and stock but better now on synergy rom
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Most reboots are due to using unstable software or user error, if these aren't in question then your phone is a bad apple
Sent from my PG86100 using Tapatalk
Have a look at the battery contacts. I have read of some people solving reboots by wedging in a piece of thin cardboard on the opposite end of the battery to give it more solid contact.
SeeNev said:
I know this is a common problem as I've seen it in other threads on other sites, but I haven't been able to find a cause/solution. My Evo 3D randomly reboots, frequently. It has happened with every firmware version since I got the phone, and with every rom/kernel I have installed. It doesn't seem to be an overheating issue. I've tried uninstalling a few apps to see if they might be the cause. Basically I'm ready to call it a hardware defect. Does anyone have any idea what causes this or how to fix it? I bought my phone unsubsidized online so it isn't easy to return, but I may have to try anyways. My 3D is useless as it is right now.
Click to expand...
Click to collapse
replace your sd card.
*EDIT.... just for the sake of being a little more informational and contributing.... a bad sd card will cause this. your phone, like a computer, can detect a bad disk and will reboot itself to check it.
i had the same problem when i first got my phone... i had my old sd card in there... random reboots. replaced the sd card, problem went away immediately.
i KNEW it was the sd card, though, as soon as i powered up the phone with the new sd card installed because on my old phone whenever i would transfer apps to sd i would get this error pretty often "failed to move application" and i would do it again and it would work.
so after i put the old one in my new 3d i would get that same error... along with the reboots, and thats how i figured it was the card.
so when i powered the phone up with the new card, i went to move my apps from the internal disk to the card and EVERY single one of them moved over the first try. and the phone has not rebooted itself once since then.
also, i heard somewhere that HTC sent some phones out with bad sd cards.... so if you are using the one that came with the phone, that could still be your issue. replace the card.
I had a horrible time with my 3vo rebooting, then got a replacement through Sprint TEP (a new one, thank goodness; ##786# tells you refurbished status) but I had the new one do the same.
Once either of mine had a single reboot, it would then continue to a complete load (booting properly) but would then reboot again after 1-5 minutes. After pulling/reconnecting the battery, it is fine for a day.
The old one had the initial reboot WAY more often than the replacement (the old one had several in a day, this one has had only one per day for the past 2 days).
How to fix: You cannot fix it. You can, however, get a good day before it begins its rebooting sequence. To so this, you have to pull the battery. I have waited until it has rebooted, then I hit shutdown and disconnect-reconnect the battery before restarting.
I hope the issue is taken care of and the initial reboot is gotten rid of.
This has happened on bare stock unrooted and rooted cleanrom 2.1 and 2.2. Also, with 2 different SD cards and 2 different batteries and 2 different 3vos. I have HTC's fastboot off.
Cause: My best guess is that HTC fastboot is not completely off even when unchecked--something differentiates what is loaded during a random reboot from what is loaded after a battery pull, but I don't know what. That, or something differentiates a shutdown and the reboot that the phone does when it reboots randomly. I could be wrong. My sample size is only 2 corrections, but it literally rebooted 12 times then stopped completely after the battery pull and the same thing happened one additional time.
I appreciate the insights you guys have given. I have pulled the battery several times and I don't believe it has done any good, though I will test that further. I am using a 32gb sd card that I purchased when I had my evo 4g and it always worked before, but I will try using the 8gb that came with the phone. The battery is snug and I even 2 two spare battery that also don't fix the problem when being used. I had a lucky 2 days without any reboots, then back to about a dozen reboots a day. So far it's happened with every rom I've tried.
I have noticed that the problem seems to get worse in areas where there is no reception. I took it into the hoover dam and it rebooted like 20 times. Also at Disneyland in different ride buildings where there's no reception it would often reboot.
Yes, marginal reception areas are usually, but not exclusively, where mine starts its reboot routine. The other is during the airvana handoff.
Neither the battery or SD card made any difference. It seems to be getting worse now. All I have to do is run an application and half the time it will reboot. I've tried wiping the system and cache and reinstalling roms. Nothing works.
I was wrong before. It is the shutdown that makes the difference. Difference got home and it began to reset itself every 5 minutes or so. I pulled tjw battery during startup and it did not break the rebooting.
After it finished reboting, I selected shutdown then poweres it back on. After it came back up, it stayed up and has been stable since.
It looks like this might be something I have to get used to. If it begins to reboot, I have to give it a clean shutdown to relieve the issue (well, for 20 hours or so, at least). Again, HTC fastboot is always off.
so this guy came into my store who had a rezound, never once had a problem with it ever...then the battery died fully overnight because he forgot to charge it..
so when he woke up, it was dead obviously. he then plugged it in, and the orange light came on for 5 seconds...then shuts off. and nothing happens. this even happened when he brought it in for me to try. so i'm like, wtf, probably a bad battery maybe?
so i put in a good one we've got...same thing. so i ask if he's rooted or anything, he says no...but i did a search, and found some posts that when people had bad flashes of roms, it would stick at the white screen, and they had to restore a backup in CWM for it to work.
so i tried to see if maybe he was rooted...went into bootloader, hit recovery, and the phone just died. just shut off. so i was like, thats weird...so then i tried to do a factory reset....same thing, i hit factory reset, the white HTC screen came rgiht up, then the phone just died...and this was with a fully charged battery, too.
eventually we had to just call up and get him sent a refurb, but still, has anyone seen this problem? nothing i could do could get it to boot, and that's such a ****ty feeling especially if this guy said that he NEVER had a problem with any HTC phone, especially this rezound, until that battery died and it would'nt turn on again.
I've had that problem after a bad flash, but it still let me get into hboot and recovery without problems, so I doubt it was that. Don't have a clue what it could be though... at least you got him taken care of with a refurb. Maybe the inability to boot to recovery could be not having amon ra or cwm installed (never tried without one) and if he wiped /data or /system I don't know if factory reset would know what to reset to (again, never tried).
Edit: Also, with me, the phone never died. White HTC screen would stay up until I pulled the battery and it would still recognize the charger.
exactly! it's a problem after a bad flash. i wonder if this dude was lying and tried to flash something, his battery died, and it bricked it
I am currently experiencing the exact same problem; I was able to replicate everything you describe, including what happened when you tried to go into recovery or factory reset mode. I have NOT tried to root or do anything else untoward with the phone ... if anyone has any idea what I can do other than get a new phone and lose all my data, I would really appreciate it!
edit - there is one difference: my battery never died. I took my phone out of my pocket at 5:40 to look at it, and it was fine. I looked at it again at around 5:50 and I had the white htc screen. At this point I pulled the battery and started googling.
second edit - could the forced update have something to do with it??
nope, he brought his in before the update.
have you gotten anything to work? when we called customer service, they just replaced his phone for him..i hope it works out for you, man. maybe try to get into fastboot and wipe the phone, or something? i know i was able to get into the bootloader..maybe you can push a factory reset from the comp
avertist said:
I am currently experiencing the exact same problem; I was able to replicate everything you describe, including what happened when you tried to go into recovery or factory reset mode. I have NOT tried to root or do anything else untoward with the phone ... if anyone has any idea what I can do other than get a new phone and lose all my data, I would really appreciate it!
Click to expand...
Click to collapse
If you want to at least get the data off of it you can try using testdisk.
http://www.cgsecurity.org/wiki/TestDisk
I used it for my external sd card that wouldn't read in the phone or computer anymore and had all my nands and other backups on it. It seems like it won't work on Android but it will, but since I formatted it in the phone it didn't seem to have a volume name.
After you select the drive and it comes up with the partition table list, select [None].
Then select [Analyse]
I think that's when it will list all your directories.
You might be able to hook up your phone and get stuff off the internal card if you leave it at the white htc screen, not sure. But I have used testdisk successfully on a drive and the sd card that all systems said was unreadable and needed to be formatted. Anyway, it's worth a shot to see if you can get your stuff off it even if you have to return it.
jayochs said:
so this guy came into my store who had a rezound, never once had a problem with it ever...then the battery died fully overnight because he forgot to charge it..
so when he woke up, it was dead obviously. he then plugged it in, and the orange light came on for 5 seconds...then shuts off. and nothing happens. this even happened when he brought it in for me to try. so i'm like, wtf, probably a bad battery maybe?
so i put in a good one we've got...same thing. so i ask if he's rooted or anything, he says no...but i did a search, and found some posts that when people had bad flashes of roms, it would stick at the white screen, and they had to restore a backup in CWM for it to work.
so i tried to see if maybe he was rooted...went into bootloader, hit recovery, and the phone just died. just shut off. so i was like, thats weird...so then i tried to do a factory reset....same thing, i hit factory reset, the white HTC screen came rgiht up, then the phone just died...and this was with a fully charged battery, too.
eventually we had to just call up and get him sent a refurb, but still, has anyone seen this problem? nothing i could do could get it to boot, and that's such a ****ty feeling especially if this guy said that he NEVER had a problem with any HTC phone, especially this rezound, until that battery died and it would'nt turn on again.
Click to expand...
Click to collapse
Yeah I had a lot of white screen time when I had the Evo! A co-worker of mine had this happen on his Evo. It was from overheating. Now I realize this is the Rezound we're talking about but brilliant phones do think alike.
Sent from my ADR6425LVW using Tapatalk
happened to me when the kernel didn't flash but the rom did. Had to boot into fastboot and flash a kernel through a command prompt on my PC.
Just finished dealing with this after a bad flash. I couldn't boot, couldn't flash a new rom because of the Mainver error and couldn't get into recovery. Finally fixed it by deleting the PH98IMG.zip file. That let me get into recovery. Then had to flash back from ICS to Gingerbread. The I could follow the instructions to fix the Maiver error.
I had heard reports that people had data loss issues from the battery dying all the way in the rezound? Something tells me running the RUU on the phone would have fixed it.
Sent from my ADR6425LVW using XDA App
Well I went to flash a test mod I made last night trying out the new vrtheme engine and pretty much bricked my phone. Not sure what happened worst I expected was a boot loop :silly:
I have a new one on the way but figured I'd give one last try incase I missed something. When flashing the mod I got an error, then rebooted the device to see if the mod took or not and my phone went dead and won't turn back on. I tried different batteries- fully charged (I have 3), using amonra so I know its not the CWM bug. I get nothing, no recovery or hboot, no adb or fastboot, No charge indicators, no physical mutations no nothing.
The only thing I get is 2 quick beeps when I plug it into my laptop. My work computer doesn't have the drivers so I get a device not recognized but nothing else.
Ideas anyone????
would like to know what happened so I don't do it again but I can't even check .
i did something similar.
i was attempting to build a rom and the phone booted then the screen went black and now pretty much the same thing, but i don't even get the 2 beeps.
it kills me, lol. I've flashed hundreds if not thousands of tests builds and "experiments" to my phones, done mods and themes for multiple phones never had an issue then something that is essentially a meta-morph breaks my phone, I'm more in awe than upset.
edit: please don't think that I'm blaming vr theme engine. I've flashed other vrthemes and was fine, this is something I did with a mod I was working on, just not sure what went wrong.
Run an RUU?
Tried, just waits for device for the exe version and cant get to hboot for the other. My phone was due to be returned at some point I had major heat issues saw the 150*f 's a few times and other quirks. Still think it was the mod though.
Well replacement just got here. It was nice of Verizon to ship out a replacement Incredible that is years old but now I have to wait 2 more days for my replacement Rezound....sigh @ Verizon....
Just got this same issue as well on my phone.
Only difference being that mine wasn't installing a theme.
I had just flashed the newest Ineffebilis Deus (1.1), had an issue where I only saw the menubar, rebooted, wiped and flashed again. Told it to restart, now it won't do anything. No charge light, etc. Using AmunRa, btw.
I have no other batteries to test with, unfortunately.
adb shows no devices and even the wall charger doesn't do anything.
Just my luck that it does this two days before I get on a plane, haha.
Phone shut off and will not turn on, will not charge, will not boot, nothing.... here's the backstory.
I root my girls EVO LTE for her just for the sake of backing up data and pictures and texts. She also enjoys Fresh ROM, but I never got around to putting it on this phone, bc at the time there was no need. Also, I never did get around to turning S-OFF, just rooted, stock rom, nothing else.
About 3 months ago, she had a random boot loop, which, after some googling, seemed to be a random problem that some people were experiencing, unrelated to root or anything. So we fixed her phone, updated it, at the time, and have since done nothing to it. A few weeks ago, she started have major problems. Texts would take 5 minutes to open, contacts would also, and sometimes she couldn't dial out. Problems that I hadn't gotten around to looking into.
Today, her phone just completely turned off and hasn't done anything since. Won't turn on, charging does not give it a light. I tried to boot into recovery etc. Is the phone completely BRICKED?
It's within the year warranty, but I know if sprint gets it back on and see it's rooted, they'll be assholes about it, even though it doesn't seem to be related.
jirafabo said:
Phone shut off and will not turn on, will not charge, will not boot, nothing.... here's the backstory.
I root my girls EVO LTE for her just for the sake of backing up data and pictures and texts. She also enjoys Fresh ROM, but I never got around to putting it on this phone, bc at the time there was no need. Also, I never did get around to turning S-OFF, just rooted, stock rom, nothing else.
About 3 months ago, she had a random boot loop, which, after some googling, seemed to be a random problem that some people were experiencing, unrelated to root or anything. So we fixed her phone, updated it, at the time, and have since done nothing to it. A few weeks ago, she started have major problems. Texts would take 5 minutes to open, contacts would also, and sometimes she couldn't dial out. Problems that I hadn't gotten around to looking into.
Today, her phone just completely turned off and hasn't done anything since. Won't turn on, charging does not give it a light. I tried to boot into recovery etc. Is the phone completely BRICKED?
It's within the year warranty, but I know if sprint gets it back on and see it's rooted, they'll be assholes about it, even though it doesn't seem to be related.
Click to expand...
Click to collapse
Does it show in device manager when you connect to a pc?
njfoses said:
Does it show in device manager when you connect to a pc?
Click to expand...
Click to collapse
Well I dont have the drivers installed bc I recently added an ssd and started from scratch, and like I said, I don't mess with her phone too often.
But it doesn't do anything when I plug it in via usb, doesn't make a sound, nothing pops up, and it doesn't try and connect. It's lifeless.
Some have had good results plugging into a wall charger for 6-8 hours and then it comes back to life.
It may work.
Sent from my PC36100 using xda app-developers app
Your timing is good, bricks tend to happen during major updates
Have your gf take her phone back to the Sprint store and say it won't turn on, charge etc. if the phone is truly bricked, they can't tell it was rooted or whatever. They should replace it because it's within the warranty period. If she has an SD card, take it out (especially if it had ROMs on it).
The key is have your girl friend do this, better would be to have someone's mother take it in.
bigmoogle said:
Your timing is good, bricks tend to happen during major updates
Have your gf take her phone back to the Sprint store and say it won't turn on, charge etc. if the phone is truly bricked, they can't tell it was rooted or whatever. They should replace it because it's within the warranty period. If she has an SD card, take it out (especially if it had ROMs on it).
The key is have your girl friend do this, better would be to have someone's mother take it in.
Click to expand...
Click to collapse
This is exactly what I done when I bricked downgrading firmware. An OTA had just been released and I told them I took the update and the phone died. They replaced it immediately no questions asked.
Sent from my EVO using xda premium
I am totally stock, unrooted.It all started after I turned on Google Now. I was trying it out for a few days, didnt like it so I turned it off. After that, I noticed a considerable dip in battery life. After checking with better battery stats app I found that the phone would no longer go into deep sleep and the culprit was "mhl-kernel-wakelock". I have tried everything to get rid of this wakelock.
I have tried: phone reboot, battery pull, wipe data from all media player apps and usb service, deleted all my apps, reinstalled them. I tried a full data wipe/reset and wiped cache.I tried charging my phone while off. I deleted all my media off of my sd card and got a new sd card. I tried connecting to windows based pc. Nothing works, the wakelock remains.
I have never used my note 2 to connect to the tv or anything like that. Also my usb functionality no longer works. It wont talk to the computer. The phone will charge though. I have searched google extensively and there is very little information regarding this wakelock. I'm afraid it might be at the hardware level. The only other thing I can think of is buying an MHL cable to HDMI and hook it up and hopefully when I disconnect it it will shut off the MHL mode that it is stuck in. Obviously I could also root and flash a ROM with a different kernel, but I really enjoy stock and the spen features etc.
If anyone has any suggestions im wide open. Thanks
EDIT (2/1/13): I also realized that when I tried Google Now was around the same time that my house lost power during the night and the power flickered WHILE my phone was charging from the wall outlet. I initially attributed the problem to Google Now, while in actuality it makes much more sense that a power surge fried my USB port on my phone.
I know this probably isn't the answer you were hoping for but I think it might be a good idea to go ahead and, assuming you're comfortable doing this, root and unlock your device. I recommend you try out Jelly'Beans' Build 4 ROM. It has all the great features of stock with the bonus of being much lighter on your phone (smaller system ROM file) and you can set it up to look like AOSP Jelly Bean. Or if you really don't want that look and prefer TouchWiz, you can do that too.
I would do this anyway as imho, it's better to be unlocked and free for the remainder of days you own this device, rather than get an OTA and lose the possibility of unlocking ever again.
And this has a good chance to resolve your situation as you would be totally wiping the system partition and chances are thats where the issue is.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
back up whatever you dont want to lose and wipe data/factory reset from stock recovery. you can try a cache wipe first, but a data wipe will fix guranteed.
droidstyle said:
back up whatever you dont want to lose and wipe data/factory reset from stock recovery. you can try a cache wipe first, but a data wipe will fix guranteed.
Click to expand...
Click to collapse
Thanks.I already tried this several times. I tried it from the OS and from the recovery. I also lost my usb functionality so im not even sure if I can flash a new rom with odin.
I think I'm screwed. I can't even access the hidden menu from the dialer pad to attempt change the USB mode. It looks like a hardware failure, even though I haven't done anything out of the ordinary. It would explain why its stuck in MHL mode with the constant wakelock (despite multiple factory resets and data wipes). and why no USB ( tried 3 different cables) cable or any number of computers (3 different computers) cannot recognize, connect, or exchange information with it via USB. This blows.
I registered with Samsung and am trying to fill out a service request through their website, but it just says the troubleshooting guide is unavailable right now and it won't let me get past that step to actually request a service repair. FTW
Just an update in case anyone has this problem. I was able to get the battery drain under control. However, I'm not absolutely sure which setting it was, but under screen settings it was either auto-rotate or screen timeout, but I pretty much changed them all back to default, rebooted and changed them back to the way I liked them. For some reason it disengaged the MHL mode that it was stuck on. This is even after 3 factory resets and data wipes.. all it took was to switch one of those on and off.
The other problem I had was that my USB hub quit working, although it would charge, but not communicate with any computer. After a couple more days though, it stopped working altogether. It wouldn't charge my phone or do anything. I tested my charger and cord with another phone and computer it works/charges flawlessly.
After that, I took it into Verizon (crossing my fingers, since I got my Note II on release day with no insurance... so way passed the 14 day return period) and told them that I did get my phone back in late November, but I had never tried to plug it into my computer since I got it (even though I had and new about this problem for awhile) so I told them it was probably defective from the release date, I just didn't know about it. Long story short, after talking with 3 of the reps and them mindlessly googling dead-end solutions that I had already tried, the manager issued DOA on my device and shipped me a new Note II for free.
F yeah... very happy at this point. The new one I got is not a refurb, runs flawlessly. I rooted, unlocked, and running Clean ROM... all right before the OTA hit.
facing same problem with mhl wake lock and my n7100 note 2 is not detected any more when connecting to PC