Related
I went away for xmass, and the last thing I did before leaving (this is stupid i know) was to upgrade my XDAII to 2003SE 2.02 rom.
I brought only my USB charge cable because i didnt want to carry too much.
Now, when I plugged it in to charge on my PC it said charging and the light came on as usual. However, it seems it wasnt charging. I left it overnight expecting to have a charged unit, only to find it completely dead the next day.
Now, when I plug it in, the charge light comes on RED for about 2 minutes, then the unit comes on from a hard reset and shows both charge levels at ZERO.
It stays on for about 10 minutes pretending to charge, but only the backup battery charges, the main one doesnt charge at all. Then it goes off totally and the light goes red again.
If I turn the unit off while it goes red straigh away and wont come back on.
After a few minutes it comes back on and pretends to charge again. The Backup battery reached "100 %" but the main battery will not charge. its still at 0% and wont charge.
Ive connected it to a 5v2amp psu as it requires but this was via a powered usb charger so using the same lead, not the official cradle.
Im worried there is something wrong but dont have access to the cradle.
Has anyone else ever had experiance of a total discharge state on an XDAII ?
UPDATE
I travelled 50 miles today to get to the nearest charge cradle for an XDA2, put my battery in and it charged fine. I put it back in the XDA and it worked. However, when I got home I plugged it into the USB charge lead, and it came on and said charging again, with the yellow light and all seemed well. I left if for a bit and the battery was then dead again with no charge and back to showing the red light. it wont come on at all now.
This is the same lead i used previously and the only change is the 2003SE rom, has anyone else had a problem charging after doing this rom upgrade? Can I revert back to 172 ? how? help please.
Please help. IM screwed unless I can find a solution, has anyone got any idea?
Dude, I have the same problem on my 1.72 version. I have (of course) dropped by xda2 several times on the floor, but it works charging from the cradle (which again has a adapter connected to it) but not from my brand new USB sync+Charge cable. I have also tried another cable and even on a different PC. Only thing that happens, is that it says it is charging, but nooooo... it's all flat after a little while. It's as if the cable uses my XDA power to change the PC instead of the other way around
It's funny. So now I have to drag that big-ass charger along with me to work every day instead of that neat little USB cable.
Life is unfair!
As for your problems, I can only say that you're not alone.
Hi, thanks for the reply.
I havent ever dropped mine, ive taken good care of it, so I dont think that is the cause. It does sound like the same issue however, I dont have my cradle here to test it though, just a usb sync+charge cable.
Does it work with the charge adaptor and psu alone? I mean the little thing that goes on the end of the mains psu to connect directly to the XDA without the cradle. How about on the cradle without the PSU plugged in?
I think this may be a hardware fault that needs repair, so its off back to o2 for mine if it is, you may find they would repair yours too.
Anyone else got an idea?
http://forum.xda-developers.com/viewtopic.php?t=4330
With my charger alone, it charges perfectly. In the Cradle with the charger connected, it works too. I havn't tried to use the cradle alone using only the USB cable to the PC.
I think I might bring it to the repair-dudes when it's so trashed that it is not working at all Until then, i will keep on using it.
I have exactly the same problem. i am not sure if it was because of the upgrade, but this is what happened to me, I upgraded to 1.72wwe from the factory 1.66wwe and it was working fine when I noticed that sometimes when it was charging after pulling out the plug, the unit will display 0% charge from the external battery and then after plugging it again the power is at 100%, It happened twice and was ok again, I presumed it was just a glitch from the system and promptly dismissed it as such. After a week, it was hardresetting everytime i got it out of the plug. I brought it to the service center and they replaced the battery (it was under warranty) It was working fine then I upgraded to 2003se the unit was ok for about 3 days then i noticed that the unit was loosing charge and hardresetting everytime. I brought it to the service center again and they said they replaced the motherboard this time and was back to 1.66wwe. So far its ok and working fine.
I was flashing a new rom. And after it said 100% on the phone it turned black and never lit up again. I waited i didnt pull out the usb. 15 min later i checked it again still black. i pulled the usb out. hit the power button and nothing happend. i did a hard reset and still the phone wount power on. The phone's charging led light wount even come on when i plug it up. So i assume i have bricked me phone ?
I have HSPL3
miri19v
froyostone 3.1v
is there any way to bring it back to life or do i toss it in the trash?
thanks for the help
i have also tried to go into boot loader and NIL!
from your use of the word 'trash' can i assume you have a tmous hd2? if so, what did you flash? was it a non tmous stock rom (meaning a bad radio)?
(oh, first job tho, check for bent battery pins)
the pins are fine. yeah i was actually flashing a stock tmou rom.
got the full filename for the rom you downloaded please? (just checking you havent downloaded a t mobile rom that isnt tmous)
the reason im pushing that line of enquiry is that the symptoms you describe are consistent with either
wrong radio (from the wrong stock rom)
bent battery pin
over discharged battery
to test the over discharged battery you can take it out, plug usb in with wall charger, then put battery in. this lets it charge without trying to turn on the phone. the light may not come one for some time, so leave it a good hour or two.
Hey Sam,
I'm having this issue too. I am relatively positive it's from an over-discharged battery. The phone conked out a few nights ago, and later when trying to charge it I got nothing - until yanking the battery for a bit, plugging in the charger, then popping in the battery. Now, every time the battery drains I have to do this.
Is the battery "damaged" now, or do you have any suggestions to fix the prob? I see this posted a bit but no one has any solutions that I've found.
Thanks!
Ryan
well i know the principals of these batteries, but not really the mechanics, so yes id guess the battery is defective, (but it could be the phones internal battery control circuits too, again just guessing) but no i dont know if there is a cure, other than try another battery, and if it cures it, ok, but if not then it would be a warranty issue.
are you using android? cos from what ive read it discharges quickly under android or something? (never used it so cant tell)
So the past two nights iv let my rezound battery go dead. The problem is it wont charge a dead battery. It charges if there is some battery and its on but when it is dead it is dead. The fix was I had to put the rezound battery in my tbolt to get a little bit of juice.
Any ideas or similar problems? I am unlocked with the htc unlock tool and running nils business sense?
Could it be a rom bug?
Don't let your battery die. It's bad for it anyway.
Sent from the Rez Beast
Once the battery is dead what does the LED on the phone do? If it blinks for a while it is either too hot or too dead to turn on, but it can still charge eventually. If the LED is not coming on at all I would pull the battery out and connect the charger with no battery and see if the LED comes on. If still no luck, get a new charger.
Blinks then Charges
I had the battery die on me once (on a prior battery and prior rezound). The phone will blink orange for a WHILE (I tried 3 different chargers not knowing what it was), but eventually started to charging. I think patience is needed. If, after 15 minutes, you still aren't charging, then that's something (but longer if the phone was also hot).
If I hit he power button with or without the battery in the led will light for a short time. I had it plugged in all night and no charge. I used two different plugs.
As for not letting it die. I know its not ideal but I couldn't help it.
jdmba said:
I had the battery die on me once (on a prior battery and prior rezound). The phone will blink orange for a WHILE (I tried 3 different chargers not knowing what it was), but eventually started to charging. I think patience is needed. If, after 15 minutes, you still aren't charging, then that's something (but longer if the phone was also hot).
Click to expand...
Click to collapse
+1. Same thing here.
KORM via the beast known as the Rezound.
I let my phone die completely once. I freaked out that my phone wasn't charging. I went onto HTC's site and it said that it could take 20 or more for the led to turn on while charging if the phone was completely dead. Just plug it in and be patient. It will charge and the led will eventually turn on.
Sent from my Vigor using xda premium
I had this problem too, and am a little concerned I have a defective phone
So I had this issue happen this weekend. My daughter was using the phone when it died. Couldn't get it restarted. (I am unlocked via HTC, stock ROM with bloat removed. Phone is a week old.)
After messing with it using the factory charger/cable and other chargers/cable combinations I got nothing. Light would only intermittently come on for a second or two then go back off.
I charged it over night with the factory charger/cable. Didn't work the next day. Charged it all day and night with my old charger/cable that I know works. Didn't work.
Tried multiple variations of taking out the Battery/Sim/SD card and using the plug-in chargers & CPU USB variations with no success.
Luckily, I had ordered a new spare battery and it came in the mail before I returned the phone. Plugged it and it started up fine.
But my concern is that my phone is not properly charging. I have also had other similar charging/battery life issues that raise concern.
As far as not letting it die, **** happens and phones die, if this is a reoccurring problem, that in my mind is pretty unacceptable. A phone should charge when its plugged in no matter what. I may end up returning it to see If just got a defective phone/battery.
My phone will turn on then off and im starting to think it has something to do with the battery. But when it started it was in tue yelllow on the status bar, now i have it charging without being turned on and the indicator light is on but hopping mine will fire up soon. This all just happened to me within the last two hours lol, already called verizon to get a replacement but still going down there tomorrow.
Sent from my SCH-I800 using xda premium
DLink888 said:
So I had this issue happen this weekend. My daughter was using the phone when it died. Couldn't get it restarted. (I am unlocked via HTC, stock ROM with bloat removed. Phone is a week old.)
After messing with it using the factory charger/cable and other chargers/cable combinations I got nothing. Light would only intermittently come on for a second or two then go back off.
I charged it over night with the factory charger/cable. Didn't work the next day. Charged it all day and night with my old charger/cable that I know works. Didn't work.
Tried multiple variations of taking out the Battery/Sim/SD card and using the plug-in chargers & CPU USB variations with no success.
Luckily, I had ordered a new spare battery and it came in the mail before I returned the phone. Plugged it and it started up fine.
But my concern is that my phone is not properly charging. I have also had other similar charging/battery life issues that raise concern.
As far as not letting it die, **** happens and phones die, if this is a reoccurring problem, that in my mind is pretty unacceptable. A phone should charge when its plugged in no matter what. I may end up returning it to see If just got a defective phone/battery.
Click to expand...
Click to collapse
As far as not letting it die, **** happens and phones die.
--I agree, but once it gets down to 5%, why not just turn it off knowing the problems people are having so wide spread now.
Under the exact same conditions I have had the same problem with a warm battery reboot. It seems to occur when you are talking on the phone and let it die. Once it dies the phone will not reboot. My wife has the exact same phone. When I put her battery in my phone the phone works fine. My wife’s phone dies every night and she simply plugs it in the wall and it charges no problem. Again the conditions seem to be related to the battery dying while it is hot. If the battery dies while the phone is cool and not used then it seems to reboot no problem. I will go to Verizon tomorrow to look for a fix. I will let you know what happens.
I'm also having this problem but i can return my phone because i unlock it or can i return it ?
Check and see if your battery is 3.7 or 3.8v . I wonder if it is related to the charging issue with the 3.8v battery some people seem to be having.
mjh68 said:
Check and see if your battery is 3.7 or 3.8v . I wonder if it is related to the charging issue with the 3.8v battery some people seem to be having.
Click to expand...
Click to collapse
it's a 3.8v what do you recommend i do ?
I had this happen, and here is what worked:
Unplug charger
remove battery
plug charger in
insert battery (while charger is plugged in)
I got an immediate orange LED and after a little while I was able to run the phone back on.
gsgleason said:
I had this happen, and here is what worked:
Unplug charger
remove battery
plug charger in
insert battery (while charger is plugged in)
I got an immediate orange LED and after a little while I was able to run the phone back on.
Click to expand...
Click to collapse
I had the same issue with my OG Droid. Would kill the battery and it would stay dead, even after a whole night of charging. The above method seemed to work for me.
I make 100% sure mine never goes totally dead after an experience I had with my Droid Charge.
I accidentally let it die completely (I fell asleep when it was almost dead & it ran all night). The next morning it was off, I put in a fully charged battery & it fired right up but started FCing like crazy. Every single thing I clicked on force closed immediately, I had never seen anything like it.
I was running a custom ROM & kernel & had done a nandroid BU the day before. I restored the BU & the phone ran perfectly again, but that scared me enough that I made darn sure it never happened again LOL........
gsgleason said:
I had this happen, and here is what worked:
Unplug charger
remove battery
plug charger in
insert battery (while charger is plugged in)
I got an immediate orange LED and after a little while I was able to run the phone back on.
Click to expand...
Click to collapse
That didn't work for me i just won't let it run down i guess.
Holy ****!!! I think I may have found the fix! I have had the same exact problem as everyone in here. It seems to happen once I root. My Rezound would die completely, then after plugging it in, the light would come on for 5 seconds or less then shut off. I plugged it into my computer and Windows makes the USB Connected sound, so I figured something is happening.
I went into my command prompt and *adb devices*. It showed my device, but says in recovery mode. I then *adb reboot bootloader* and the bastard rebooted into bootloader! From there, I chose "REBOOT" and it fired right back up! Anyone who is having this problem, please try this and let me know if it works for you!
***UPDATE***
It appears when the battery dies all the way and then doesn't charge, the phone is automatically going into recovery mode even though nothing shows on the screen. I had my SIM card out when I tried this the first time, then when putting my SIM back in, it started doing the same thing. But again, it was going directly into recovery mode. This time, I tried a simple *adb reboot* and BAM! I'm back up and running! Again, let me know if this works for you, or if you need help doing this, let me know.
thehomebiscuit said:
Holy ****!!! I think I may have found the fix! I have had the same exact problem as everyone in here. It seems to happen once I root. My Rezound would die completely, then after plugging it in, the light would come on for 5 seconds or less then shut off. I plugged it into my computer and Windows makes the USB Connected sound, so I figured something is happening.
I went into my command prompt and *adb devices*. It showed my device, but says in recovery mode. I then *adb reboot bootloader* and the bastard rebooted into bootloader! From there, I chose "REBOOT" and it fired right back up! Anyone who is having this problem, please try this and let me know if it works for you!
***UPDATE***
It appears when the battery dies all the way and then doesn't charge, the phone is automatically going into recovery mode even though nothing shows on the screen. I had my SIM card out when I tried this the first time, then when putting my SIM back in, it started doing the same thing. But again, it was going directly into recovery mode. This time, I tried a simple *adb reboot* and BAM! I'm back up and running! Again, let me know if this works for you, or if you need help doing this, let me know.
Click to expand...
Click to collapse
Yes... HTC phones never charge "powered off" When you turn it off and then put it on the charger, it is actually entering/booting a special screen off recovery mode during charging.
CWM recovery on the rezound has trouble charging a completely dead battery.
Use Amon RA recovery.
So last night before I went to sleep, my NT had about 40% battery life left in it. I'm currently running the final alpha build of CM7. I've been experiencing really bad wifi loss issues and have kept the 'Never' option enabled under the wifi sleep policy (thinking that would help hold the connection).
I woke up to find the NT was turned off. Figured that was odd as I was only asleep for about 5hrs. I turned it on and then noticed it got into the OS and then died. I did see the battery icon was red briefly.
I then plugged it into the wall and it was boot looping. I saw the 'n' logo pop up, screen went black, 'n' logo, etc. etc.
After numerous attempts of holding down the power button for 20+ seconds, holding power+vol down for 10 seconds, plugging it with or without an sd card into the wall and computer, nothing is happening.
The computer does see something as I'm hearing the common connected/disconnected tone from the USB port. Now I'm noticing that plugged into the wall, the 'n' on the cable stays orange. It never turns green.
Did it go 'poof' in the night somehow?
[EDIT] Ok after leaving it plugged into the wall for about 15mins, it suddenly turned on but had a google framework FC error. Yeah, not sure what I should do at this point. It appears to be charging...
It's been noted by others that if the power level goes below 15% you mustn't turn the device off if you don't have the original charger nearby. If it dies you need to charge it with the original charger for a bit before it'll power back up.
I assume this means that you can't run it off the cable while you've got a completely dead battery. That kind of stinks but isn't too surprising, a lot of devices are like that.
So does that mean that if the device is <40% of battery I need to plug it in if I won't be around it for a while? Not sure I'm cool with that. Battery life was great all day yesterday but somehow it dropped 40% in under 5hrs while asleep.
I can't really say much as I haven't dealt with it personally. People were talking about it in a couple threads about the NT's charger and unique 12 pin cable.
Here's what I understand from what I've read:
You can run it until it's empty all you like. You'll just need to use the Nook's factory charger (or a compatible 2A charger with bridged D- and D+ pins) AND (this is the important one) the factory USB cable to charge it.
If you run it until it dies you have to charge it for a little while before it'll turn on again, BUT you have to use the original cord and charger. It won't charge off of a regular micro USB cable nor will it work if you're using a 2A or smaller charger that doesn't have the middle two pins bridges (the Apple UBS chargers won't work nor will your PC's USB ports, for example).
The NT will charge, albeit slowly, if connected with a third party cable or USB charger (without the data lines D- and D+ bridged), but not if the device's power has been depleted.
So I suspect something sucked up a lot of juice while you weren't using your NT. Not a huge deal, but definitely annoying. Plug it in for 15 minutes and you can get rolling again.... BUT only if you're using the original charger and cable. Lovely isn't it? It's not a huge problem but it is annoying. I wish you could at least use the device with a dead battery while plugged in.
I just mention the charger/stock cable thing because I'm sure someone will probably see this post in the future and may be having that particular problem resuscitating their NT.
Cool, yeah I don't specifically set out to run it down to zero but since the device is clean with minimal stuff running in the background, it's difficult to know when this might happen again. I assumed I'd wake up with like 20-25% battery left. The framework FC is also something I'm concerned about but maybe it was just a fluke.
Ah well, really do appreciate your input and I'll be sure to keep the stock cable/adapter on hand when I'm on the go.
Battery showed fully charged, I rebooted to do another CWM backup and then when it came back up it showed 84% charged. Lol. And this pic made me laugh even more. Time to get that lady from Poltergeist involved I think...
The Google Framework force close is typical of stock rooted NTs. I don't believe it ever did any harm to anything though. Just that it sometimes appears on reboot.
I'll ask one additional question as to not make another topic since it's related.
Opinions on battery calibration with the NT? That was one of the reasons I didn't charge it last night as I wanted to fully run it down and then fully charge it back up. Does the NT require this with a new rom install? That pic above shows the battery gauge clearly wasn't correct initially.
Your battery is draining overnight because wifi is running the whole time (as you stated in your first post).
Sent from my SCH-I500 using Tapatalk
ckevinwelch said:
Your battery is draining overnight because wifi is running the whole time (as you stated in your first post).
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
That's what I obviously thought of at first but it didn't drain nearly as much when I was using it throughout the day. The only thing I can think of is maybe the fuel gauge itself was wrong from the start, which refers back to my calibration question.
My GS2 has the sleep policy set to 'Never' as well and only loses maybe 7-8% after being asleep for around 7-8hrs and it certainly uses more juice in sleep due to the cell communication, etc.
Hello,
I have Galaxy S2 and having some charging issue. Yesterday, when I plugged it in the wall charger, it didn't get charged (i.e. even the flash on battery was not coming up) and when I tried to restart the phone, it powered off but didn't switch on. I tried holding the power button to turn it on but it didn't. So, I pulled out the battery and left the cell for some time like 20 mins or so. After re-inserting the battery, it turned on but still was not getting charged. I tried to change the USB cable as well but nothing helped. I then tried to charge it via my Laptop it actually started the charging process but with error on Laptop saying "USB Device not recognized".
Today, I tried the wall charger again and here's I found something: when my phone is ON and I plug it in the wall charger it doesn't charge but as soon as I turn the phone OFF, my phone starts getting charged (Battery image comes on screen which usually comes when the phone is off). So, that's how I am charging my phone.
I went to the repair shop today, he said it's a charging port issue on which I have some doubts that why it is even charging in this way if it's a port issue. I just want to make sure if whatever he's saying can be somewhat true.
Can you please help me out? I would be really thankful to you.
I look forward to hearing from you soon!
Thank you!
PS: I tried to search about the port issues but I couldn't find anyone having this kind of issue so please!
The issues you have mentioned really do all point to a faulty USB board......it is common (with a faulty board) for some functionality to work while other functionality is lost. The part itself costs pocket change and is reasonably easy to DIY replace......
If you want to go down that path, check my profile for threads I've started.....you'll find a guide explaining exactly how to do it.
Just make sure to read and note the section on 'rev versions' it is VERY important to get the correct one......
My wife says I'm a phone geek....She's probably right