Android hatch hd2 nandroid. Mdj cm6.11 and nexus stock and desire hd and jdms. I have tried everything. I had a great android build going nut now it wont charge. I plug it In and the battery slowly goes down. Help please
Sent from my HTC bravo using XDA App
lineage404 said:
Android hatch hd2 nandroid. Mdj cm6.11 and nexus stock and desire hd and jdms. I have tried everything. I had a great android build going nut now it wont charge. I plug it In and the battery slowly goes down. Help please
Sent from my HTC bravo using XDA App
Click to expand...
Click to collapse
Does it charge ok in WinMO or WinPho?
Have you tried a different USB cable or charger?
have you tried different battery?
Does it charge while turned off?
What exactly happens when you plug in the cable?
ok so its totally dead now. i plug it in and the orange light comes one. then it boots without me touching it. then dies. then boots then dies then boots then dies. then when its dead i unplug it and plug it back in then it repeats. its wont just charge. and what it was doing before was like when i had it pluged in it would sometimes charge. like 18 percent one minute then like 24 percent one minute. then it would be at like 6 percent an hour later after being plugged in. and no it has never done this before. on my winmo or anything. i havent run winmo for a while lol been android last 6 months. and i have been running nand for about 1 month and no problem
I had the same thing , But it suddenly started to funcion again, It started to function when I went from sd to nand, longshot but...
well i am on nand now. and have been. its just like it is not even trying to charge anything ya know
i think the female plug in the phone might be bad lol
Take out the battery and wait +/- 1 minute (or a bit more)
After this put the battery back in the HD2 and try charging it again.
Related
Well, I don't think I had seen any yet but I might be the first device/battery failure as a result of using one of the new superior charging kernels.
I have been using the Netarchy 4.2.2 beta kernal (aggressive with havs) I believe and everything has been fine for the past week or so.
This afternoon I plugged my phone into USB and laid down for a nap. I woke up not long ago and my phone is completely dead now. It will not power on or indicate that it is plugged in or anything. I don't have another battery to test, but could it just be a battery failure? Or is it possible the whole device is hosed?
deathsled said:
Well, I don't think I had seen any yet but I might be the first device/battery failure as a result of using on of the new superior charging kernel.
I have been using the Netarchy 4.2.2 beta kernal (aggressive with havs) I believe and everything has been fine for the past week or so.
This afternoon I plugged my phone into USB and laid down for a nap. I woke up not long ago and my phone is completely dead now. It will not power on or indicate that it is plugged in or anything. I don't have another battery to test, but could it just be a battery failure? Or is it possible the whole device is hosed?
Click to expand...
Click to collapse
Anything is possible. Chances are that it was not the kernel though. Try a different charger and maybe a different battery. If all else fails take it in for repair.
How full was your battery before you plugged it in? You could try pulling the battery and waiting an hour or so before putting it back in and powering on.
I was down to about 30% when I plugged it in so it was getting a full charge. I remember getting a phone call during my nap that I ignored. When I finally got up the device was completely dark. I've got it unplugged and the battery out for now. Hopefully it will power back up in an hour or so....
If not I will have to try a buddy's battery in here tomorrow to see if that does anything. If not I'm simply out the device, there is no "taking it in for repair for me" unfortunately.
I hope it powers back up for you. If not, it would be good to try your friends battery so you could start trouble shooting.
Was this the original stock battery?
Sent from my blah blah blah blah
Try a different cable. A little while back I thought my phone borked on me as it would not charge even though the charge light was on. When my wife's did the same thing I got suspicous and tried a different cable. Like magic, the problem went away.
I don't think the phone is hosed, might be just the battery, I had that exact situation happen to me back in december, when plugged in theres not even a light. I tried drastic measures to get it working even heating the battery to 120f for 5 min then letting it cool for 10 over and over, it finally worked when I got to a sprint store and they plugged it in to one of their wall chargers, I was shocked after hours of doing things with no results. to this day im still using the same battery and it has the same life as when new
still using sbc kernels too
been running SBC and have had no negative effects
Original red oem battery. I've tried my usb cable and my 2 wall chargers so far. Still no lights.
I did see the screen blip on for a fraction of a second a moment ago while pressing at the the power button, so that gives me glimmer of hope. About to see what happens with a car charger on the way over to my friend's to try another battery.
Wish me luck!
The fact that you where using the SBC can mean absolutely nothing. I have a friend with an Evo as well, I flashed every experimental kernel and Rom I can find and have had no real issue, hardware wise. Him, on the other had, had only updated via the Sprint OTA, never flashed any custom roms or kernels, never even Rooted.
one night while texting a reply to me, his phone flat out died. it was plugged in and everything, just went black and charge light went out. I put my battery in his phone the next day, swapped SD cards, etc,etc. nothing brought it back to life, it was gone.
Sprint actually replaced it for him, just tell them that you where simply charging it and it wouldn't turn on the next day. they won't be able to get it to boot up because it's dead.. no idea why his did it, I kindof feel that is what happened with yours. I don't think the kernel had anything to do with it.
Well it's been confirmed to be the battery by trying another one.
Today is the first time I've ever let the phone do an extended charge over USB using one of these sbc kernels and the battery just happens to take a **** during the process? That's one killer coincidence...
try the battery again tomorrow out after sitting for a bit, it will charge and work again
deathsled said:
Well, I don't think I had seen any yet but I might be the first device/battery failure as a result of using one of the new superior charging kernels.
I have been using the Netarchy 4.2.2 beta kernal (aggressive with havs) I believe and everything has been fine for the past week or so.
This afternoon I plugged my phone into USB and laid down for a nap. I woke up not long ago and my phone is completely dead now. It will not power on or indicate that it is plugged in or anything. I don't have another battery to test, but could it just be a battery failure? Or is it possible the whole device is hosed?
Click to expand...
Click to collapse
This happened to me when I was using a Zendroid kernel a couple weeks ago. You should be able to just plug your phone back in and charge it again. The orange light may blink at first or not turn on for a couple minutes, but it should charge.
I'm honestly not entirely sure, though. I put my dead battery in my sister's Evo, and the light thing is what happened to me. I let it charge in my sister's phone, and it turned out fine. Worked in the morning. Hopefully, you can do it in your own phone if you don't have another way to charge it.
deathsled said:
Well, I don't think I had seen any yet but I might be the first device/battery failure as a result of using one of the new superior charging kernels.
I have been using the Netarchy 4.2.2 beta kernal (aggressive with havs) I believe and everything has been fine for the past week or so.
This afternoon I plugged my phone into USB and laid down for a nap. I woke up not long ago and my phone is completely dead now. It will not power on or indicate that it is plugged in or anything. I don't have another battery to test, but could it just be a battery failure? Or is it possible the whole device is hosed?
Click to expand...
Click to collapse
4.2.2 should not have SBC.
It would not be surprising to hear that a stock battery just quits working. Sprint replaces these for peeps all the time. Li-Poly batteries are cheap to produce and like anything else, there are always bad ones in the bunch.
Seriously doubt it was caused by whatever is loaded on the phone otherwise there would be more coming up with same issue. Unless there is something with the beta and USB charging method. Still doesn't sound very likely.
deathsled said:
Well it's been confirmed to be the battery by trying another one.
Today is the first time I've ever let the phone do an extended charge over USB using one of these sbc kernels and the battery just happens to take a **** during the process? That's one killer coincidence...
Click to expand...
Click to collapse
What does your Battery Monitor Widget log say?
deathsled said:
Well it's been confirmed to be the battery by trying another one.
Today is the first time I've ever let the phone do an extended charge over USB using one of these sbc kernels and the battery just happens to take a **** during the process? That's one killer coincidence...
Click to expand...
Click to collapse
That is a killer coincidence...but I do believe it is just a coincidence. I am at CES right now (well prep meetings and such) and the only way I charge when I travel is through USB. I have been using the 4.3 with SBC straight off of Net's thread (http://forum.xda-developers.com/showthread.php?t=719763) and have had no issues. Good to see you have your phone back, but I am willing to bet it was a faulty battery, not the kernal.
Hope it doesn't turn you away from the SBC kernals, it is so much nicer to see it stay between 100% and 90% for hours on end instead of 10 minutes like before.
It's the kernel from my experience mostly tied to sbc kernels. My phone did the exact thing. I mean exact. Pulled battery, used different cables etc. One thing I did not use was the OEM HTC charger. I have PCs around me all the time or the car charger. My phone died in my room where I have other wall mounted usb chargers. Didn't think anything of it. A few hours later phone died. It was 54% or so when I plugged it in. I came back to a dead phone. Nothing i tried initially worked. Sprint tech support same thing. I knew they couldn't resolve it. I have spare batteries but this OEM battery was too new. I wanted to know the problem so as to not repeat it. Sprint offered to replace my phone but I said let me get back on that. Since I knew the kernels were playing with voltage and that over or under voltage can mess with the phone. I plugged the OEM HTC wall adapter in and sure enough I had a orange blinking light. I waited for a few mins. Booted into recovery and installed a nandroid backup with sense. It booted great and guess what my battery percentage was? 55%. The battery did not die but the system shut down and it wanted the exact voltage from the HTC charger to kick start it. Since then for me personally I have stayed away from sbc kernels. It might work for some but not for me.
Sent from my PC36100 using XDA App
mrmomoman said:
It's the kernel from my experience mostly tied to sbc kernels. My phone did the exact thing. I mean exact. Pulled battery, used different cables etc. One thing I did not use was the OEM HTC charger. I have PCs around me all the time or the car charger. My phone died in my room where I have other wall mounted usb chargers. Didn't think anything of it. A few hours later phone died. It was 54% or so when I plugged it in. I came back to a dead phone. Nothing i tried initially worked. Sprint tech support same thing. I knew they couldn't resolve it. I have spare batteries but this OEM battery was too new. I wanted to know the problem so as to not repeat it. Sprint offered to replace my phone but I said let me get back on that. Since I knew the kernels were playing with voltage and that over or under voltage can mess with the phone. I plugged the OEM HTC wall adapter in and sure enough I had a orange blinking light. I waited for a few mins. Booted into recovery and installed a nandroid backup with sense. It booted great and guess what my battery percentage was? 55%. The battery did not die but the system shut down and it wanted the exact voltage from the HTC charger to kick start it. Since then for me personally I have stayed away from sbc kernels. It might work for some but not for me.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Um, SBC and undervolting/HAVS aren't the same thing.
SBC is a new, experimental charging method that "just" came out.
I'm not sure what just happened but I'm hoping y'all can shed some light on it. I was charging my Evo on Usb pulled it off read 88 percent, not thirty seconds later it died completely. It wasn't even able to power back on. Can any one tell me what happend.
Specs
myns warm 2.2 Rls5
Netarchy 4.31 cfs havs
Sent from my PC36100 using XDA App
battery might be toast.
Spoon201 said:
I'm not sure what just happened but I'm hoping y'all can shed some light on it. I was charging my Evo on Usb pulled it off read 88 percent, not thirty seconds later it died completely. It wasn't even able to power back on. Can any one tell me what happend.
Specs
myns warm 2.2 Rls5
Netarchy 4.31 cfs havs
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I've never been able to reliably charge my phone through my USB port since Froyo. It will say it's charging but it will actually be DISCHARGING. Creepy right? One time I was talking to someone on the phone while plugged in via USB and my phone; despite the charging LED being GREEN, actually died mid-call and would NOT turn back on for at least 5 minutes until the orange light stopped blinking.
Freeza that sounds almost exactly like what happend to me. I was unaware there was a problem with USB charging since Froyo. This was the first time I had really ever attempted to charge from USB.
Sent from my PC36100 using XDA App
Spoon201 said:
Freeza that sounds almost exactly like what happend to me. I was unaware there was a problem with USB charging since Froyo. This was the first time I had really ever attempted to charge from USB.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well, when I was on Eclair (2.1) that's all I did was charge through USB. For some reason the update to Froyo has pretty much killed USB charging for me through most USB hubs. Plugging it directly into the back of my computer works OK I suppose. Maybe Google changed the current draw from hubs in Froyo or something. Needless to say, all I do now is charge from AC.
USB 2 ports can only give maybe 500ma so if your phone is using more than that it will take the rest from the battery. The wall charger on the other hand give a full Amp, 1000mA.
i accidentally let my kf die, and it wont turn back on. i have FFF and twrp 2.0 installed aswell as the latest cm9. i left my stock charger at school, so i wont be able to get it until sunday, but anybody have a suggestion as to how i can get this thing to charge? when i plug it up to my phone charger it lights up the fff screen and then it goes into boot loop. and it wont get past there and i know its completely dead so its almost as if its using the charger to turn on, and then it is trying to use the battery to boot up. but since the battery is dead it cant turn on fully causing it to "loop"?
thanks
TBG
That Baker Guy said:
i accidentally let my kf die, and it wont turn back on. i have FFF and twrp 2.0 installed aswell as the latest cm9. i left my stock charger at school, so i wont be able to get it until sunday, but anybody have a suggestion as to how i can get this thing to charge? when i plug it up to my phone charger it lights up the fff screen and then it goes into boot loop. and it wont get past there and i know its completely dead so its almost as if its using the charger to turn on, and then it is trying to use the battery to boot up. but since the battery is dead it cant turn on fully causing it to "loop"?
thanks
TBG
Click to expand...
Click to collapse
You NEED the stock charger. Otherwise it won't charge.
Sent from my HTC Sensation XE with Beats Audio using XDA
That's what I figured, I usually top it off with my phone charger when I'm at work but I figured that since its actually dead it will have to be the stock one.
Thanks
Sent from my ADR6300 using xda premium
jmcoffey said:
You NEED the stock charger. Otherwise it won't charge.
Sent from my HTC Sensation XE with Beats Audio using XDA
Click to expand...
Click to collapse
I've done it with a htc charger from death
Sent from my Amazon Kindle Fire using XDA
Not only stock. IPad 2 and sumsung 10.1 chargers also will work. Main idea in charge current. It need to be about 1.85 A
So I've got a dx I'm getting set up for my wife...
Originally installed paranoid android but was having problems sometimes getting past a bootloop and did not realize that it won't charge during recovery,,,, it also would not charge while off it kept trying to reboot which would then loop....
So i searched and read about cutting an old cable and rigging it so it would work with dead battery..
That worked and seemed to be going fine, wound up doing an sbf and starting over, rooted again ,,, all was good,, (or so i thought) took off the cable rig,,,
and now if i try to charge it it shows a green light and icon animates like it's charging,,, but it's really not. It died again...
Thought maybe just the battery was old and gave up the ghost...
So i ordered another BH5X,, got it in and same thing happens with it,,, and if i try to charge from a powered off state it will try and boot up fully but then quickly display a large battery with a question mark and then reboot, starting the cycle over again...
What gives??? Did I screw something up internally, with the cable hack???
Sent from my SCH-I500 using xda premium
looks like you fried the phone
Sent from my XT862 using xda premium
hhp_211 said:
So I've got a dx I'm getting set up for my wife...
Originally installed paranoid android but was having problems sometimes getting past a bootloop and did not realize that it won't charge during recovery,,,, it also would not charge while off it kept trying to reboot which would then loop....
So i searched and read about cutting an old cable and rigging it so it would work with dead battery..
That worked and seemed to be going fine, wound up doing an sbf and starting over, rooted again ,,, all was good,, (or so i thought) took off the cable rig,,,
and now if i try to charge it it shows a green light and icon animates like it's charging,,, but it's really not. It died again...
Thought maybe just the battery was old and gave up the ghost...
So i ordered another BH5X,, got it in and same thing happens with it,,, and if i try to charge from a powered off state it will try and boot up fully but then quickly display a large battery with a question mark and then reboot, starting the cycle over again...
What gives??? Did I screw something up internally, with the cable hack???
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Had the same problem here. It seemed like charging but then fell out almost directly. Like he's using too much power while charging (even when power is off). After an extremely long charging he finally gave up 4% .. But went dead again after like 15 minutes......
Somebody any idea? Lot a thanks if you have any!..
if you did something like [Howto] Fix "Battery Low - Cannot program
you likely fried your phone and there is no fix
but phone not charging can be one of several problems
bad software: fix with sbf
bad charger: buy new charger
bad usb charging port: no fix at least not easy anyways Replacement Micro USB Charging Port
bad battery: buy new battery
also may want to buy a Battery Charger for Motorola Droid X (MB810)
or a TBH’s Motorola Programming Cable Adapter
I've had this problems about a week after I got my N7.
The Micro USB cable that came shipped with my tablet charged it while I was using it for about a week.
After that week, the battery would just plateau around whatever percentage I had before charging.
A few days later, it wouldn't charge fast enough and the battery percentage just dropped.
I switched to a First Gen Nook Micro USB cable, which worked like a charm.
Up until now...
The charge seems to be close to plateauing again, because it charged a good 3% every 10 minutes, now I barely get 10% every hour.
What the hell is going on?
I spend $250 on something I expect to at least run on AC without any problems.
Sorry the post is long, and thank you all tremendously for your help.
blahman179 said:
I've had this problems about a week after I got my N7.
The Micro USB cable that came shipped with my tablet charged it while I was using it for about a week.
After that week, the battery would just plateau around whatever percentage I had before charging.
A few days later, it wouldn't charge fast enough and the battery percentage just dropped.
I switched to a First Gen Nook Micro USB cable, which worked like a charm.
Up until now...
The charge seems to be close to plateauing again, because it charged a good 3% every 10 minutes, now I barely get 10% every hour.
What the hell is going on?
I spend $250 on something I expect to at least run on AC without any problems.
Sorry the post is long, and thank you all tremendously for your help.
Click to expand...
Click to collapse
a few people have had this prob , i think i sometimes have it, as if i use a certain usb charger it charges to 100% in about 2.5 hours, with the other one it'll take 3-4 hours to reach 100%.
im not sure but i think there is a app on market to show what recharge voltage your getting while plugged in, i cant remember the name thou srry:crying:
Why do you think the Nook wire stopped working though?
It just seems odd that both wires worked at one point, but slowly stopped working...
Then logic would tell me that it's not in fact related to what cable you are using, but a problem with either the battery itself or the main board. First thing I would do is let the battery die, pop the back cover off, unplug the battery, let it sit for a while, then charge it back up. That may or may not solve the problem, but it's worth trying.
ynrozturk said:
Then logic would tell me that it's not in fact related to what cable you are using, but a problem with either the battery itself or the main board. First thing I would do is let the battery die, pop the back cover off, unplug the battery, let it sit for a while, then charge it back up. That may or may not solve the problem, but it's worth trying.
Click to expand...
Click to collapse
Thanks, I'll try that when I head off to bed.
Are you also using the factory wall charger, I think its output is 2.1a
davidoff59 said:
Are you also using the factory wall charger, I think its output is 2.1a
Click to expand...
Click to collapse
just realized lol
my sgs3 charges better from asus usb charger
and my nexus 7 asus charges better from the samsung charger lmao