Anyone have this issue? Whenever I shut my phone down and plug it in, it boots into clockwork mod after about 10 seconds. Is there a way to charge the phone without it even turning on? Im trying to see if my charging issues are due to the abismal kernel these phones have, or something else. It seems HTC packed in a nice 10% trickle discharge to this phone which could easily be the cause of everyones battery issues.
Either way, I cant charge the phone when its off... it keeps turning on into CWM. Tired of my battery dropping to 93% after 5 minutes of being unplugged... And yes ive tried calibrating it.
This is mentioned/discussed in numerous threads in the general section already, and also in the rooting instructions thread...
Cant find it :\ Been looking. was there a remedy?
Turn on fast boot. Menu > settings > applications.
Sent from my ADR6400L using XDA App
Odinist said:
Turn on fast boot. Menu > settings > applications.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Didnt fix anything. I found the thread about this, but they seem to not have a fix there either. This didnt work for everyone.
How do you remove CWM and let the stock recovery always load? I just want to disable it for a bit until I can bump charge the battery, then put it back on.
fastboot mode appears to be some sort of hibernate mode by the way it works; with that in mind, your phone never really turns off with it, which is why you don't get the clockwork boot after turning that feature on. This would suggest that it's a bit of a battery drainer by itself. Does fastboot "off" charging behave as expected? That is, like a non-rooted phone?
As far as bump charging, not sure about restoring stock recovery, or that it would address the issue. Supposedly the phone charges in clockwork anyways. You could bump charge with a third party charger for battery only, if they're out yet.
distortedloop said:
fastboot mode appears to be some sort of hibernate mode by the way it works; with that in mind, your phone never really turns off with it, which is why you don't get the clockwork boot after turning that feature on. This would suggest that it's a bit of a battery drainer by itself. Does fastboot "off" charging behave as expected? That is, like a non-rooted phone?
As far as bump charging, not sure about restoring stock recovery, or that it would address the issue. Supposedly the phone charges in clockwork anyways. You could bump charge with a third party charger for battery only, if they're out yet.
Click to expand...
Click to collapse
I was thinking about a 3rd party charger for this... hmmm
Related
I have a new (one week old) Vibrant. I haven't done any mods, or rooted or anything like that. My GPS sucks (as most do), so I changed some settings under LBSTestMode. Now my phone is really screwed up. I don't know why, but it randomly turns itself off, locks up when running ANY app, and if I allow the screen to sleep, I can't get it to turn back on. My battery was almost completely dead, so I plugged in, and now I see the "Swipe to Unlock" screen, but I can't swipe it or do anything at all.
I've done a couple of battery pulls but no change. I'm at a complete loss for what to do. I'm sure it's something silly I'm missing, but I'm brand new to Android and freaking out.
Can anyone help a stressed-out noob?
Try odin to stock . Can you get to download mode? Pull battery plug in usb hold volume up and down and put the battery . Should see android with a broom and should be yellow
Sent from my SGH-T959 using XDA Premium App
Can I do all of that with a (basically) dead battery? Or should I charge first? I tried plugging in to charge but it wasn't charging. So I pulled the battery, then plugged in the phone without turning it on to see if it would charge.
Try the method i post but make sure you have the drivers installed on your oc
Sent from my SGH-T959 using XDA Premium App
download vibrant toolbox it will help u
Maybe I just haven't found the answer, but has anyone else had the problem with the phone being dead the next day even though it had power when turning it off? I've been getting great battery life but the other night when powering down I had 30-something percent only to not be able to turn it on this morning. I plugged it in via usb to charge for 10 minutes and after turning on it said 31, so it wasn't dead. Same thing happened last time I needed to charge but it happened before using batterminder and the system-battery level showed 1/4 charge left.
Since I'm using batterminder to determine percentage I was wondering if the levels are being misreported. Yesterday I ran the phone dead and batterminder counted all the way down so I don't think its misreporting.
Any ideas?
Holding the power button down long enough? And is fast boot enabled
Bussin Caps n 3D
Yep. Turn off fast boot should fix it. Your phone doesn't turn completely off with that option enabled.
Sent from my HTC Evo 3D.
aimbdd said:
Yep. Turn off fast boot should fix it. Your phone doesn't turn completely off with that option enabled.
Sent from my HTC Evo 3D.
Click to expand...
Click to collapse
im sure with the phone off EVEN in fastboot that it cant be using that much battery at all
i mean, its not like the phone is sleeping(where as if you have data sync on it'll still use 3g/wifi to get data at intervals with the screen off)
even if you use fastboot the phone is OFF,as in doing completely nothing
so what exactly is the phone doing while its off to use battery? i assume its like the sleep function on a computer,but even so, it should draw VERY little power
I turned off fastboot to see if anything changes, but with the phone being completely turned off I don't see why the battery would drain. Anyway, thanks for the suggestion, I'll report back my results.
So I rooted and installed CWM, and now when I try to charge my phone WHILE it is off, the charging light wont come on, which means is not charging while off at all. Has this happened to anyone else? When the phone is on, it charges just fine.
EDIT: Just tried it with FastBoot on, and now it charges when powered off. So to anyone having the issue, try this.
EDIT 2: It appears this only happens when on CWM recovery. TWRP does not exhibit this problem.
I've noticed the same on my end.
Try a different recovery.
Locked & Loaded
same
Same result here, i woke up to a dead phone this morning.
Happen to me too with different recovery.
Sent from my PG86100 using Tapatalk
Out of curiosity, were your phones _off_, or in the hibernation state that is used for Fast Boot?
blakejohnson86 said:
Out of curiosity, were your phones _off_, or in the hibernation state that is used for Fast Boot?
Click to expand...
Click to collapse
Mine was in the "hibernation" state, but before I had root, I could charge the phone while off with either FastBoot off or on. Anyway, I already changed recoveries to TeamWin's, and Im in the process of a Nandroid backup, so as soon as its done, I will try to charge with both FB on and off to see what happens, and I will post results. BTW, I've seen that this has happened to quite a few more people, so it might be a widespread problem that not a lot of people know because most of us dont ever turn off the phone to charge it.
I dunno.. havent tried that but why do u turn your phone off to charge it anyways lol
brownhornet said:
I dunno.. havent tried that but why do u turn your phone off to charge it anyways lol
Click to expand...
Click to collapse
Well, if you run your battery until the phone turns off, it'd be great to be able to charge it in your own phone instead of an external charger or non-rooted/s-on phone.
brownhornet said:
I dunno.. havent tried that but why do u turn your phone off to charge it anyways lol
Click to expand...
Click to collapse
For one, the phone charges faster this way because its not using any power at all.
I have fastboot turned off in the menu and mine charges fine when I turn it off. I'm using Teamwin Recovery
devgrp said:
I have fastboot turned off in the menu and mine charges fine when I turn it off. I'm using Teamwin Recovery
Click to expand...
Click to collapse
I can also confirm this, so it appears to be a bug related to CWM recovery, can any of the guys that still have that recovery and is experiencing this problem try to charge with FB off while the phone is off and confirm if it works or not?
Droga said:
I can also confirm this, so it appears to be a bug related to CWM recovery, can any of the guys that still have that recovery and is experiencing this problem try to charge with FB off while the phone is off and confirm if it works or not?
Click to expand...
Click to collapse
Same here. I did notice however, the light would not turn green while off... It was on the charger for 7+ hours. Weird. I'm using TWPR.
It's definitely the cwm-4.0.1.4-shooter.img recovery. I just tested with both twrp and cwm. twrp allows the phone to charge with fastboot off and phone off.
Fastboot on isn't really a 'fix' because the phone never goes off completely from what I understand. I just want to know I can charge a dead battery in my phone if I ever needed to.
mwalt2 said:
It's definitely the cwm-4.0.1.4-shooter.img recovery. I just tested with both twrp and cwm. twrp allows the phone to charge with fastboot off and phone off.
Fastboot on isn't really a 'fix' because the phone never goes off completely from what I understand. I just want to know I can charge a dead battery in my phone if I ever needed to.
Click to expand...
Click to collapse
This.
This might be a serious problem to anyone whos using this recovery and their phone dies before they can get to an A/C outlet (for example, on a car w/o a car charger, etc). I will send the developers a quick note for them to check this out.
Good work on figuring this out... Im sure we will see more folks wondering wtf is goin on with their batteries
Sent from my Evo3D
I can confirm this. Using CWM the phone does not charge when powered off. Whats the best way to remove CWM and install TWR?
when you turn off the phone and plug in the charger, the red light does go off in a few seconds, but my phone was fully charged overnight (without the red light on)
Mine charged to 100% this morning. I stuck with CWM, I also flashed OMJ deodexed rom before I went to bed. I plugged it in when the phone was on and awake.
c19932 said:
when you turn off the phone and plug in the charger, the red light does go off in a few seconds, but my phone was fully charged overnight (without the red light on)
Click to expand...
Click to collapse
I also wondered if it was just that the led wasn't on, but was really charging. I tried having the phone off with cwm, plugged in charger, led came on/went off, and left it for 30 minutes. It did not charge my battery at all.
str8upx said:
Mine charged to 100% this morning. I stuck with CWM, I also flashed OMJ deodexed rom before I went to bed. I plugged it in when the phone was on and awake.
Click to expand...
Click to collapse
Yeah, the problem does not happen if the phone is on and charging.
So I rooted my EVO 3D using the HTC method. Then I installed CWR and SU. Installed Titanium backup and took a couple of backups. Everything was fine. Then I had this bright idea of installing ROM Manager. I run ROM Manager and I see this option for backing up existing ROM. I click on it and it asks me to install a boot loader or something. I install it. Then click backup again. BAM ! Phone reboots and goes blank. Now the red LED is consistently blinking every short while and the phone wont start.
Tried removing the battery and holding power to drain the cap. Then tried holding power. No dice. Tried holding power + Volume - no dice. The phone simply wont boot.
How do I fix it ? Is it bricked for good ? Anyone else have this problem ?
Try unplugging and then turning it on. Shouldn't be bricked either way. Hope this helps.
Try running the HTC method again
Sent from my PG86100 using xda premium
If the suggestions already given do not work try hooking it up to your
PC and seeing if adb works? Them try to boot into fastboot, then fastboot recovery.
If not, try hooking into sync and seeing if you can initiate an Ruu. The Ruu will more than likely not be successful because you are unlocked and would need to lock first, but some communication between your phone and pc is a great sign.
also there is a thread here (I think sticky) that says "think you broke your phone, look here". Check that thread out to see if any suggestions.
Edit: added link
http://forum.xda-developers.com/showthread.php?t=1281729
Sent from my PG86100 using XDA App
To try all of that it needs to power on and the screen needs to show something. It simplywont power on. Red led keeps blinking. Tried charging it, connecting it to my Mac. A DB reboot. A DB reboot recovery. Says device not cnected.
nimkar said:
To try all of that it needs to power on and the screen needs to show something. It simplywont power on. Red led keeps blinking. Tried charging it, connecting it to my Mac. A DB reboot. A DB reboot recovery. Says device not cnected.
Click to expand...
Click to collapse
Well if the red light is blinking I highly doubt it is bricked.
If Adb doesn't work, try running an Ruu through sync. Even if it says there is no device connected to sync, run the Ruu anyhow. I can tell you that I had an issue Once where I hooked it up to sync and it said there was no device connected. I tried to run Ruu anyhow and it initiated. It didn't complete because I was still locked, but at least it was a sign of life. And after it did it's partial run, I was able to but back into hboot.
Try it. You've got nothing to lose. Me though....I'm losing sleep and have to get up early tomorrow so I'm going to bed. I'll subscribe to this thread to try to keep up with it in the morning to see where you are at. Good luck.
oh. And sleep on it too if you find yourself getting frustrated. Sometimes I find that a night to sleep on it really clears my head to and let's me look at it with a fresh perspective the next morning.
Sent from my PG86100 using XDA App
All suggested up is what I'd recommend. I wish you best of luck.
remove power from the thing for 10 minutes - this means take the battery out, do not have it plugged in... then try again... sometimes they freak the f out over nothing...
Wife's stock EVO has done that when an app tried to reboot the thing.
Try typing fastboot oem boot in terminal with your phone connected obvs
Sounds like a dead battery. Try leaving it plugged in overnight or switch out the battery with a good one.
wrong section btw
Sent from my Touchpad using xda premium
thanx all for your responses. I appreciate them all. The only thing I haven't tried from suggestions above is keeping the battery out for extended period of time. Trying that now. Also since I am a complete noob what is ruu and is I avaliabe or Mac.
I had this issue with the 1.0.x versions on twrp
charge the battery externally if you can. then put it back in and try to turn it back on
do you have insurance? if nothing works take it to sprint service and act all dumb
mildlydisturbed said:
remove power from the thing for 10 minutes - this means take the battery out, do not have it plugged in... then try again... sometimes they freak the f out over nothing...
Wife's stock EVO has done that when an app tried to reboot the thing.
Click to expand...
Click to collapse
This was the fix that worked. Removed the battery for 2 hrs. Phone was fine after that. Posting from phone !
I had a the exact same thing happend to mine.
Repeated battery pulls did not help and it would just blink.
Took it to a sprint keosk at a mall and they just pulled the batter and replaced it with another battery and it booted fine, and then they put my battery back in and it was fine after that, although the battery needed to be charged.
Yeah that happened to my og evo I was all flippin out over a dead battery hahaha
Yep, dead battery. Freaked me out the first time this happened also.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
This is not a dead battery issue but more accurately a "You phone thinks the battery is dead when its actually not" issue. I charged the battery for a long time using usb cable and my Mac and then using the stock charger and even that did not help. Repeated battery pulls also did not help. Only when the battery was taken out and left for a extended period was it fixed.
Here is my theory. All EVOs have a powerful capacitor inside them somewhere where they store the "Battery is almost dead" info and this capacitor takes some time to discharge. Every time you pull the battery and put it back in again the capacitor is not fully discharged and retains the "battery is almost dead" flag and never updates it even after repeated charging. The only solution is to pull the battery and leave it out for some time ( I left it out for 2 hours, someone here suggested 15+ minutes is good enough) and let the capacitor fully discharge at which point it will loose its "Battery is almost dead" flag. Then plug in the battery and everything is fine.
This explanation is a complete assumption but it is based on my observations and expriments. I have seen a lot of people post the same problem however no clear solution and tried solution as the one above so I hope this post helps others like me.
nimkar said:
This is not a dead battery issue but more accurately a "You phone thinks the battery is dead when its actually not" issue. I charged the battery for a long time using usb cable and my Mac and then using the stock charger and even that did not help. Repeated battery pulls also did not help. Only when the battery was taken out and left for a extended period was it fixed.
Here is my theory. All EVOs have a powerful capacitor inside them somewhere where they store the "Battery is almost dead" info and this capacitor takes some time to discharge. Every time you pull the battery and put it back in again the capacitor is not fully discharged and retains the "battery is almost dead" flag and never updates it even after repeated charging. The only solution is to pull the battery and leave it out for some time ( I left it out for 2 hours, someone here suggested 15+ minutes is good enough) and let the capacitor fully discharge at which point it will loose its "Battery is almost dead" flag. Then plug in the battery and everything is fine.
This explanation is a complete assumption but it is based on my observations and expriments. I have seen a lot of people post the same problem however no clear solution and tried solution as the one above so I hope this post helps others like me.
Click to expand...
Click to collapse
Glad you got it working.
Sent from my PG86100 using XDA App
After my battery got really low, Power Saver mode turned in. I have it set to go on at 15% . Normally the settings return to normal once plugged back into a charger or the battery level goes back up. This last time I let the battery get down to 5% (I know..) . You know how when it gets that low, it will dim the screen really fast and disable tactile feedback? Well the thing is, it nwver reset itself. I even changed the power settinf and reboot the phone. I had to go into the screen and touch settings to reset them manually.
Anyone know why the settings did not return to normal?
I had the same thing happen. I don't know why it didn't reset. I had to change everything back manually too... I forgot my extra battery on Christmas...
Sent from my HTC Rezound
If anyone else gets this, please post here. If it happens again, I'd be interested to know if there is a fix...thanks.
I also just noticed background data got disabled. Market would not load . I had to manually turn that back on.
happened to me as well. the haptic feedback was disabled when my phone shut itself down. when i charged it back up, it didnt reset the settings to normal.
Same here... happened this morning... could it be due to the unlock?
Sent from my ADR6425LVW using Tapatalk
Yep, that sucks. Same thing happens here. Unlocked bootloader, though I doubt that is the reason.
Sent from my ADR6425LVW using Tapatalk
I have the same issue.
Unlocked bootloader with amon recovery and CleanRom 1.2
When economy mode kicks in due to low battery level, certain settings are not restored upon charge, namely the background data, though I found it was set to CDMA only with LTE disabled as well.
When I tried a Sense3.5 rom on my incredible it did the same thing, so I think this is an issue with Sense, not just the Rezound.
I think we need to start opening tickets with Verizon/HTC for them to address their issue.
fully stock over here, same issue!
I too am experiencing this issue, currently using cleanrom 2.2 sp1
Also have this issue. Stock everything.
yup, stock, same issue.
disabled 'power saver mode' so it never happens again.
Had it happen again. Batt was at 8% when I plugged in. Stock ROM ,no unlock performed. Anyone with a different version of Sense get this issue?