Got it fixed, turns out my charging hole for the phone was loose and it couldn't charge.
Yesterday around 11pm my HTC Rezound completely ran out of battery. Then this morning I was charging it for like 7 hours, but the phone will not turn on at all, not even the orange light shows. I have tried holding VOL down and POWER but nothing happens. When I keep clicking the POWER button, the orange lights comes on for like 3 seconds, and then i goes out. Please help me fix this, thanks
MY PHONE IS ROOTED AND UNLOCKED!! JUST SAYING
izink said:
Yesterday around 11pm my HTC Rezound completely ran out of battery. Then this morning I was charging it for like 7 hours, but the phone will not turn on at all, not even the orange light shows. I have tried holding VOL down and POWER but nothing happens. When I keep clicking the POWER button, the orange lights comes on for like 3 seconds, and then i goes out. Please help me fix this, thanks
MY PHONE IS ROOTED AND UNLOCKED!! JUST SAYING
Click to expand...
Click to collapse
try a different battery. it sometimes happen the battery get way to low and it does now want to charge.
If you have CWM as your recovery, that's the problem. Get some juice in your battery some other way, and flash Amon Ra.
twolasrnames said:
If you have CWM as your recovery, that's the problem. Get some juice in your battery some other way, and flash Amon Ra.
Click to expand...
Click to collapse
I already flashed Amon Ra on my phone like 3 weeks ago. What should I do from there??
izink said:
I already flashed Amon Ra on my phone like 3 weeks ago. What should I do from there??
Click to expand...
Click to collapse
Find someone with a rezound(verizon store maybe?). Try there charged battery. Boots your good if not your phone is fubar. Work forward from there.
Sent from my ADR6425LVW using XDA
Don't know if you found a remedy yet, but the same happened to me yesterday. Ended up being the battery. I brought it to Verizon and they replaced it.
Sent from my ADR6425LVW using XDA
i had this same problem look you going to need to to on a pc and use cmd
to fix this battery death ....once you have your cmd open type in adb reboot
then wait a bit it will turn on then give it a bit for it to charge then go back to cmd and type adb reboot bootloader and let it charge then reboot you phone normaly as it should do
Thanks.
cflo360 said:
i had this same problem look you going to need to to on a pc and use cmd
to fix this battery death ....once you have your cmd open type in adb reboot
then wait a bit it will turn on then give it a bit for it to charge then go back to cmd and type adb reboot bootloader and let it charge then reboot you phone normaly as it should do
Click to expand...
Click to collapse
This actually worked. But a better look for telling people is:
I had the same problem. To fix it it:
Plug the phone into the computer, and load up command prompt.
Type in "cd [directory of adb.exe]"
Type "adb reboot"
It should say "daemon not running. Starting it on port XXXX"
Then "daemon started successfully. After less than a minute, your phone will turn on.
Leave it there to charge for a little while, then, type:
"adb reboot bootloader". From there, let it charge.
After it has charged, reboot your phone as you normally would.
The only part of these instructions I couldn't get to was getting the phone to reboot properly.
This has worked for me so far, and it was pissing me off the whole day that it wouldn't charge.
For what it's worth, I bought a bricked phone from Craigslist and just keeping the battery out of it for 48 hours fixed it. Otherwise the phone was completely dead (No nothing, no charging, LED, ADB, NOTHING)
So if you have a bricked phone, you may want to try this too.
GoghAndroid said:
For what it's worth, I bought a bricked phone from Craigslist and just keeping the battery out of it for 48 hours fixed it. Otherwise the phone was completely dead (No nothing, no charging, LED, ADB, NOTHING)
So if you have a bricked phone, you may want to try this too.
Click to expand...
Click to collapse
OMG... I left my battery out for 12 hours... now I have to do it for 48 hours??? Is that extra time going to make a difference? All the things that work for other people don't work for me and it makes me very, very sad.
My Rezound was running TWRP and CM10.1. It had an extended battery in it. I ran the battery down and it wouldn't charge, so I put the original battery back in. It was okay for a couple weeks until I let that run down and it wouldn't charge. I ordered a Kidigi dock with external battery charger and the Rezound sat in a drawer with no battery for a week while I waited for the dock to arrive from Hong Kong. The dock came in yesterday. I charged the original battery in it, then put it into the Rezound and...nothing. I can't get the LED to light or anything. I connected the Rezound to my PC and ran ADB DEVICES, but my PC finds no devices. I've got a Mugen extended battery coming in the mail. I'll give that a try, and I'll also drop into a Verizon store and see if they have a charged battery I can try in my Rezound, but I've pretty much run out of hope for this phone.
Related
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
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.
As per feralicious' suggestion I've created a poll to collect data. Information on the issue below. Sorry about the long poll.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
So I'm on Rezound #2 right now. Both of the phones had the same exact problem when the battery died ie. they simply wouldn't charge. Now I thought the problem was hardware (which is why i got the replacement), but after being able to boot up my replacement phone with my girlfriend's battery, I relocked and RUU'd back to stock. I then threw in my dead battery and VOILA it began charging. I let the battery die again just to see if i can recreate the problem, and havent had the issue since.
Now i really want to unlock my phone again but my girlfriend isn't here all the time for me to test out if this was an issue with either the unlocked bootloader, a kernel issue, ROM issue, or if I'm actually having hardware issues. I'm hoping someone here with an extra battery or external charger here can recreate the problem and hopefully we can pinpoint this. Just for reference the ROM I was using was CleanROM GBE 1.6.5 *SP1* - Base: OTA 2.01.605.11 and whatever kernel that came with it. If this is a ROM and/or Kernel issue, we need to get a hold of scrosler and let him know.
Any help would be much appreciated guys thanks!
EDIT: Just to let you guys know. I did do all the OTA updates prior to unlocking the bootloader in the first place.
UPDATE: So I've been sitting with my phone literally all day trying to pinpoint what could be the cause of this. Clockworkmod seems to be the culprit. I'm going to be testing more right now so I'll keep you guys updated.
UPDATE #2: Success! The battery not charging while dead and powered off issue was resolved on my end. ClockworkMod definitely was to blame. I noticed it stopped charging while powered off/dead as soon as I flashed ClockwordMod and shut down my phone while it was connected to my PC (This was after my 5th go around with the bootloader unlock). I then flashed over Amon Ra to see if it really was ClockworkMod or if it was the recovery in general, and what do you know Amon Ra allows me to charge while powered down and dead. If you guys are having this very problem with your phone and you're running any version of ClockworkMod I suggest you try flashing Amon Ra 3.13 and posting your results so we can see if this is universal.
Instructions to flash recovery with adb and fastboot for Windows below:
Note you only need to do this if for some reason you can't boot into the bootloader using Vol. Down + Power. I am not responsible for bricked phones.
Prerequisites:
1. ADB & Fastboot (found with the Android SDK)
2. Amon Ra IMG (Use ver. 3.15 if you've flashed ICS RUU)
3. Battery with a charge.
Instructions:
1. Pull out battery, and unplug from charger/computer
2. Reinsert battery
3. Plug in your USB cable to computer and phone (your charge indicator light should go on for 1-3 seconds and shut off, then your drivers should load afterwards.)
4. Place the Amon Ra img file in the folder where ADB and Fastboot reside.
5. Once drivers have loaded open up Command Prompt, and find your way to where you set up ADB and Fastboot. Type cd <folder path>
6. Now type the command adb reboot bootloader (Note: if you get some sort of error try again a few more times. if it keeps giving you error try redoing steps 1-3 before doing 5 again)
7. Your phone should have now loaded directly into Fastboot. When in Fastboot go back to the command prompt and type in fastboot flash recovery <amon_ra_file.img>
8. When the process is done shutdown your phone and test the charging.
**ADDED** If you can run ADB commands while the phone is off, dead, and not charging, type adb reboot. The OS should boot up and begin charging. I would say let it charge till 40% before you flash an alternate recovery. If you're unsuccessful in rebooting with adb try leaving your phone plugged into the charger for 2-5 hours (this seems to have worked for some people to get a charge). If that doesn't work I recommend you get another battery or use an external charger. (Thanks excellentnuke)
If you are coming from a dead battery the charge light indicator should turn on for a few seconds then turn off for a few seconds then begin flashing continuously. When the light becomes solid you should be able to boot. When coming from a charged battery the same thing should happen, except instead of the charge indicator flashing continuously it should come back solid.
UPDATE #3: I've also discovered this problem isn't relegated to having a dead battery. Simply disabling Fast Boot and shutting off your phone can recreate the problem with CWM.
UPDATE #4: I can say that I think I've gotten enough feedback to determine that this issue was solved by what I've written above. I would highly advise people to switch over to Amon Ra until we get a bug fix/update for CWM to address this issue.
Thanks to everyone that was involved in this thread to help determine the cause of this; I appreciate it.
You should set up a poll and change the thread title to indicate that.
I am on Ineffabilis GB and accidentally let the battery die yesterday and it charged no problem. I was ready for a problem, thankfully it went straight to charging. I had also let it die once before unlocking and no problem then either.
feralicious said:
You should set up a poll and change the thread title to indicate that.
Click to expand...
Click to collapse
Good idea. Done!
My phone shut off last night due to battery death, when I woke up I plugged it in and the charge indicator came on after about 10 minutes of charging.
I have been running different ROMs and had it die a few times...
When I plug it in the LED comes on and starts blinking, after a few minutes of the blinking, I unplug then re-plug in the phone to the charger and the light comes on and stays on. I never let it sit there long enough to stop blinking on its own. I get impatient LOL.
UgXvibe said:
My phone shut off last night due to battery death, when I woke up I plugged it in and the charge indicator came on after about 10 minutes of charging.
Click to expand...
Click to collapse
I take it you're running stock still? or a custom rom? It seems odd that the charge indicator would take that long to start. I left mine on the charger for about 30 minutes when it was unlocked without any progress.
This happened to me, I took my phone to verizon and they just gave me a new battery... it took a little while, them trying different batteries, looking for a 'test' rezound battery before pulling a packaged battery to try and finally they were satisfied then swapped it out... all my boot logos and screens were stock but my launcher was not... they never went as far as checking phone specs or asking about root/unlock... they did check the phone settings to check on charge at one point... I was just thankful it wasn't a bad micro connector because I didn't want to have to wait for a new phone
I'm having the same problem once my phone dies i can't get it to charge. it starts charging for two sec and it stop charging and i does that with both of my batteries i have a 3.8v that came with the phone and a 3.7v that verizon sent me because my phone was over heating. I'm unlock and running CleanROM GBE 1.6.5 *SP1*
Before I knew about this issue I actually had my phone die when I had my 3.8v battery, I had no issues what-so-ever plugging it in to charge. I've been afraid ever since, I also have the 3.7v battery now.
I bought my phone from a trade of my GNEX, so I do not have the 1 year manufacturer warranty, so no refurbs for me, and I had to buy the 3.7v battery
I'm getting rare blue screen flickers like the ones from ICS ROMS on GB ROMS too. no fun!
andybones said:
Before I knew about this issue I actually had my phone die when I had my 3.8v battery, I had no issues what-so-ever plugging it in to charge. I've been afraid ever since, I also have the 3.7v battery now.
I bought my phone from a trade of my GNEX, so I do not have the 1 year manufacturer warranty, so no refurbs for me, and I had to buy the 3.7v battery
I'm getting rare blue screen flickers like the ones from ICS ROMS on GB ROMS too. no fun!
Click to expand...
Click to collapse
What's interesting is that I keep reading about issues with the 3.8v battery but nobody talking about the 3.7v's. I'm on a 3.7v and this issue is occuring, but i'm beginning to think it has something to do with either an unlocked bootloader or ROM issue.
drinkhere said:
I'm having the same problem once my phone dies i can't get it to charge. it starts charging for two sec and it stop charging and i does that with both of my batteries i have a 3.8v that came with the phone and a 3.7v that verizon sent me because my phone was over heating. I'm unlock and running CleanROM GBE 1.6.5 *SP1*
Click to expand...
Click to collapse
I would highly suggest you relock and go back to stock. It seems to have made the issue subside. Since you have 2 batteries if you wanna do further testing with other roms and configs that would help out a lot. No pressure though i understand if you dont want to do it.
I've also had the problem with it not charging after it's died and thus had Verizon send me a new 3.7v battery. And now Ive had the same problem with the 3.7v.
This is how i've fix both the 3.7v and 3.8v when they wont charge.
Battery pull and replace. Then plug in. Dont hit power or touch the phone. Just leave alone. Orange light will come on for a few seconds then off. Still leave it alone. I swear it took an hour but it finally booted on it's own. Weirdly it had 40% battery when it was finally on.
I'm on stock OTA rooted and running chad's beta 4 but i've had the problem with beta 3-1 as well. I did have Force fast charge enabled in incrediControl. Most of the reason the phone died was because it bootlooped for hours(?) while i was sleeping and it wasnt plugged in.
I did have a similar problem when i first got my incredible... dunno what i was running at the time could have been stock.
What i'm guessing happens is that you drain the battery so much it takes forever for it to get a strong enough charge to boot on it's own.
I had this happen for the first time today. Phone wouldn't start,battery wouldn't charge. My fix.... Open command prompt. Plug phone in to computer. Type " adb reboot recovery" when recovery opens the battery starts charging. Push reboot and Pooooof! A charging phone!
Sent from my ADR6425LVW using xda premium
joel4832 said:
I've also had the problem with it not charging after it's died and thus had Verizon send me a new 3.7v battery. And now Ive had the same problem with the 3.7v.
This is how i've fix both the 3.7v and 3.8v when they wont charge.
Battery pull and replace. Then plug in. Dont hit power or touch the phone. Just leave alone. Orange light will come on for a few seconds then off. Still leave it alone. I swear it took an hour but it finally booted on it's own. Weirdly it had 40% battery when it was finally on.
I'm on stock OTA rooted and running chad's beta 4 but i've had the problem with beta 3-1 as well. I did have Force fast charge enabled in incrediControl. Most of the reason the phone died was because it bootlooped for hours(?) while i was sleeping and it wasnt plugged in.
I did have a similar problem when i first got my incredible... dunno what i was running at the time could have been stock.
What i'm guessing happens is that you drain the battery so much it takes forever for it to get a strong enough charge to boot on it's own.
Click to expand...
Click to collapse
Hmmm... I'm beginning to suspect its either an unlocked bootloader issue or a kernel issue and not a ROM issue.
Now thats cool that your phone was able to boot up after an hour on the charger without the charge indicator light telling you it was charging (my phone was probably doing the same thing) but it still shouldnt take that long to be able to boot up the device.
When stock my charge indicator blinks continuously until it's ready to boot up, then it becomes solid. This only takes about 4-5 minutes. When running custom ROM/Kernel it would give me the same thing it gave yours ie. charge indicator turns on for 1-3 seconds and turns off and nothing else.
afmracer6 said:
I had this happen for the first time today. Phone wouldn't start,battery wouldn't charge. My fix.... Open command prompt. Plug phone in to computer. Type " adb reboot recovery" when recovery opens the battery starts charging. Push reboot and Pooooof! A charging phone!
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I'm definitely going to take this into account and try it when i unlock my phone again. Thanks man!
IrvChynaman said:
What's interesting is that I keep reading about issues with the 3.8v battery but nobody talking about the 3.7v's. I'm on a 3.7v and this issue is occuring, but i'm beginning to think it has something to do with either an unlocked bootloader or ROM issue.
Click to expand...
Click to collapse
Update in OP!
Im unlocked and on the senselessICS.
Ive had this issue happen to me several times. However today it was bad. I had it plugged in for 6+ hours with out it being able to turn on.
I had the 3.7v battery in the device.
i messed with it a bit with in that 6hour time frame. Pressing buttons pulling battery, etc. About 4 hours into this whole ordeal... it turned on, on its own. But stayed on the white HTC screen for about 45mins before i pulled the battery and tried to turn it on again. However, it would not turn on. Infact it never turned on....
Heres where it gets interesting. I had the 3.7v. My girlfriend comes home and has the 3.8v. I pop hers out, put it in my device. Fires right up... still sticks on the white HTC screen. While im impatiently waiting, i stick my 3.7v that my phone wouldnt boot with in her device. Fires right up.
I wasnt able to fully boot. Recovery/computer wouldnt mount my SDcard. Though... reformatting it from within recovery allowed it to be mountable again. I also had to wipe and reflash my rom in order to get the POS to boot.
edit: i would also like to note, when putting the battery [my 3.7v] into my girlfriends device. It showed about 80% battery.
krstnsn said:
Im unlocked and on the senselessICS.
Ive had this issue happen to me several times. However today it was bad. I had it plugged in for 6+ hours with out it being able to turn on.
I had the 3.7v battery in the device.
i messed with it a bit with in that 6hour time frame. Pressing buttons pulling battery, etc. About 4 hours into this whole ordeal... it turned on, on its own. But stayed on the white HTC screen for about 45mins before i pulled the battery and tried to turn it on again. However, it would not turn on. Infact it never turned on....
Heres where it gets interesting. I had the 3.7v. My girlfriend comes home and has the 3.8v. I pop hers out, put it in my device. Fires right up... still sticks on the white HTC screen. While im impatiently waiting, i stick my 3.7v that my phone wouldnt boot with in her device. Fires right up.
I wasnt able to fully boot. Recovery/computer wouldnt mount my SDcard. Though... reformatting it from within recovery allowed it to be mountable again. I also had to wipe and reflash my rom in order to get the POS to boot.
Click to expand...
Click to collapse
are you running clockworkmod recovery? Your issue sounds identical to mine and I MAY have a solution. I'm testing right now on my own phone right now.
IrvChynaman said:
are you running clockworkmod recovery?
Click to expand...
Click to collapse
yes. the touch one. However i had this issue prior with the unofficial clockwork.
krstnsn said:
yes. the touch one. However i had this issue prior with the unofficial clockwork.
Click to expand...
Click to collapse
Ok try flashing Amon Ra 3.13. Clockwork mod seems to be the culprit from my end. what was weird is when the phone was shut down I was able to run adb commands and every time i ran "adb devices" it showed my phone as recovery. It seems like clockwork mod recovery was trying to load before anything else preventing the phone from charging and booting up
I'm not sure if I'm slightly ****ed or totally bricked...
HOWEVER, I have: ClockworkMod Recovery, CleanROM (GB version). Installed last night.
Today, I was flying/traveling, and my phone lasted 5 hours (HURRAY!); I turned it off on my second flight because the power was at 11%...figured I'd save my phone in the event I needed the juice.
Well, now I have a brick ATM because now there is no screen magic. The only sign of life is a little orange light that is lit for maybe 10 seconds if I plug the phone after removing batt/plug and re-insert and press power.
I don't know how this could go from working, shut down, then **** you I'm dead?
I'm totally stumped. :/
Edit: I remember reading a while back that if these 3.8v batteries die on an ICS rom or something, then they don't charge? Or something like that.
Have a look at this thread.
http://forum.xda-developers.com/showthread.php?t=1489687&highlight=cwm+battery
It should help you out.
Try pulling the cover off, take the battery out, put it back in and restart normally. My wifes phone would not start one day so I pulled the battery and then it worked fine.
Alright; taken care of. Battery was dead but did that "adb reboot bootloader" command and was then able to restart via the bootloader and it loaded right into Android and charged the battery. Will be flashing Amon Ra shortly though.
Thank you!
All,
I recently rooted my Rezound following the guide at (http://theunlockr.com/2012/08/24/how-to-root-the-htc-rezound-video/)
I had superuser app issues with the recovery image included with the instructions so I loaded Amon Ra 3.16 from here (http://forum.xda-developers.com/showthread.php?t=1339679) and the superuser app worked as it should. I kept the ROM stock.
Everything had been working fine but I did notice that my phone would be completely off at times when checking and I had to power it back up. Then today my phone rang but the screen was black and I could not answer. I pulled the battery and powered back up but it remained black. The phone went through its normal start up cycle from what I can tell because I felt a quick vibrate feedback upon power up. But again, nothing on the screen. I repeated this a couple of times even leaving the battery out for about 15 mins. Nothing.
Reading forums, it seemed like I was experiencing the same issues outlined here (http://forum.xda-developers.com/showthread.php?t=1339679) regarding the clockworkmod charging issue. The symptoms of seeing the orange LED for a few moments after inserting battery and trying to start up is what I see. I followed the instructions but I could not get "adb devices" to show my Rezound. I went ahead and finished the procedure thinking maybe this would work anyway. But still nothing.
I tried to get into HBOOT but cannot access.
I'm stuck...any ideas??
Thanks for your help!!
~kanin247
Is your battery charged? Do you see the charging light when it is plugged in?
joeymagnus1 said:
Is your battery charged? Do you see the charging light when it is plugged in?
Click to expand...
Click to collapse
The battery was not fully charged when I first noticed the screen would not come on when I received a phone call. Probably 40%.
And yes, I do see a charging light when plugged in...though it only illuminates for about 5 seconds and then disappears and never re-appears unless I unplug/re-plug.
I left it plugged in all night without any luck.
Thanks!
Might have a bad battery or connection. I have a PSP that will shut off after 15 minutes on the fully charged battery. But not when it's plugged in. Maybe you could go to a Verizon store and see if they have a battery to test it. Or you could pick one up on Amazon for like 8 to 10 bucks.
I'm no expert by any means. But that's what I would try
joeymagnus1 said:
Might have a bad battery or connection. I have a PSP that will shut off after 15 minutes on the fully charged battery. But not when it's plugged in. Maybe you could go to a Verizon store and see if they have a battery to test it. Or you could pick one up on Amazon for like 8 to 10 bucks.
I'm no expert by any means. But that's what I would try
Click to expand...
Click to collapse
Thanks! I ordered a battery and will see what happens.