Related
So I rooted and installed CWM, and now when I try to charge my phone WHILE it is off, the charging light wont come on, which means is not charging while off at all. Has this happened to anyone else? When the phone is on, it charges just fine.
EDIT: Just tried it with FastBoot on, and now it charges when powered off. So to anyone having the issue, try this.
EDIT 2: It appears this only happens when on CWM recovery. TWRP does not exhibit this problem.
I've noticed the same on my end.
Try a different recovery.
Locked & Loaded
same
Same result here, i woke up to a dead phone this morning.
Happen to me too with different recovery.
Sent from my PG86100 using Tapatalk
Out of curiosity, were your phones _off_, or in the hibernation state that is used for Fast Boot?
blakejohnson86 said:
Out of curiosity, were your phones _off_, or in the hibernation state that is used for Fast Boot?
Click to expand...
Click to collapse
Mine was in the "hibernation" state, but before I had root, I could charge the phone while off with either FastBoot off or on. Anyway, I already changed recoveries to TeamWin's, and Im in the process of a Nandroid backup, so as soon as its done, I will try to charge with both FB on and off to see what happens, and I will post results. BTW, I've seen that this has happened to quite a few more people, so it might be a widespread problem that not a lot of people know because most of us dont ever turn off the phone to charge it.
I dunno.. havent tried that but why do u turn your phone off to charge it anyways lol
brownhornet said:
I dunno.. havent tried that but why do u turn your phone off to charge it anyways lol
Click to expand...
Click to collapse
Well, if you run your battery until the phone turns off, it'd be great to be able to charge it in your own phone instead of an external charger or non-rooted/s-on phone.
brownhornet said:
I dunno.. havent tried that but why do u turn your phone off to charge it anyways lol
Click to expand...
Click to collapse
For one, the phone charges faster this way because its not using any power at all.
I have fastboot turned off in the menu and mine charges fine when I turn it off. I'm using Teamwin Recovery
devgrp said:
I have fastboot turned off in the menu and mine charges fine when I turn it off. I'm using Teamwin Recovery
Click to expand...
Click to collapse
I can also confirm this, so it appears to be a bug related to CWM recovery, can any of the guys that still have that recovery and is experiencing this problem try to charge with FB off while the phone is off and confirm if it works or not?
Droga said:
I can also confirm this, so it appears to be a bug related to CWM recovery, can any of the guys that still have that recovery and is experiencing this problem try to charge with FB off while the phone is off and confirm if it works or not?
Click to expand...
Click to collapse
Same here. I did notice however, the light would not turn green while off... It was on the charger for 7+ hours. Weird. I'm using TWPR.
It's definitely the cwm-4.0.1.4-shooter.img recovery. I just tested with both twrp and cwm. twrp allows the phone to charge with fastboot off and phone off.
Fastboot on isn't really a 'fix' because the phone never goes off completely from what I understand. I just want to know I can charge a dead battery in my phone if I ever needed to.
mwalt2 said:
It's definitely the cwm-4.0.1.4-shooter.img recovery. I just tested with both twrp and cwm. twrp allows the phone to charge with fastboot off and phone off.
Fastboot on isn't really a 'fix' because the phone never goes off completely from what I understand. I just want to know I can charge a dead battery in my phone if I ever needed to.
Click to expand...
Click to collapse
This.
This might be a serious problem to anyone whos using this recovery and their phone dies before they can get to an A/C outlet (for example, on a car w/o a car charger, etc). I will send the developers a quick note for them to check this out.
Good work on figuring this out... Im sure we will see more folks wondering wtf is goin on with their batteries
Sent from my Evo3D
I can confirm this. Using CWM the phone does not charge when powered off. Whats the best way to remove CWM and install TWR?
when you turn off the phone and plug in the charger, the red light does go off in a few seconds, but my phone was fully charged overnight (without the red light on)
Mine charged to 100% this morning. I stuck with CWM, I also flashed OMJ deodexed rom before I went to bed. I plugged it in when the phone was on and awake.
c19932 said:
when you turn off the phone and plug in the charger, the red light does go off in a few seconds, but my phone was fully charged overnight (without the red light on)
Click to expand...
Click to collapse
I also wondered if it was just that the led wasn't on, but was really charging. I tried having the phone off with cwm, plugged in charger, led came on/went off, and left it for 30 minutes. It did not charge my battery at all.
str8upx said:
Mine charged to 100% this morning. I stuck with CWM, I also flashed OMJ deodexed rom before I went to bed. I plugged it in when the phone was on and awake.
Click to expand...
Click to collapse
Yeah, the problem does not happen if the phone is on and charging.
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 accidently installed cwm on my phone with Rom manager and let it die. Obviously it wouldn't charge up because i was using cwm. So I popped in the extended battery and installed amon ra 3.15 with Scotts cleanflash tool. The dead battery still won't charge. How do I fix it?
Sent from my ADR6425LVW using Tapatalk
have you tried turning your phone off then putting in the dead battery. place it on the charger while the phone is still off and try to charge it. enable/disable fast boot may help also.
when testing cwm a few months back I ran into the same issue, but it was solved by switching to amon ra and charging the dead battery once in a standalone charger.
***EDIT: I just came across this thread when doing a search:
http://forum.xda-developers.com/showthread.php?t=1489687
This should help you out.
randpost said:
have you tried turning your phone off then putting in the dead battery. place it on the charger while the phone is still off and try to charge it. enable/disable fast boot may help also.
when testing cwm a few months back I ran into the same issue, but it was solved by switching to amon ra and charging the dead battery once in a standalone charger.
***EDIT: I just came across this thread when doing a search:
http://forum.xda-developers.com/showthread.php?t=1489687
This should help you out.
Click to expand...
Click to collapse
Thanks. Im still toying with it but so far all I get is a flicker of the orange light after I hit the power button. Will try with fast boot enabled.
Sent from my ADR6425LVW using Tapatalk
pmania said:
Thanks. Im still toying with it but so far all I get is a flicker of the orange light after I hit the power button. Will try with fast boot enabled.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
excerpt from another post:
"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!"
If it comes down to it, just take the battery into VZ and get a defect replacement.
randpost said:
excerpt from another post:
"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!"
If it comes down to it, just take the battery into VZ and get a defect replacement.
Click to expand...
Click to collapse
I did something similar to this. Reboot phone to bootloader while plugged in, then swap to the dead battery then rebooted. Then I let it charge to about 40% before I had to take it off. It died a while ago and the charging problem persists.
Sent from my ADR6425LVW using Tapatalk
pmania said:
I did something similar to this. Reboot phone to bootloader while plugged in, then swap to the dead battery then rebooted. Then I let it charge to about 40% before I had to take it off. It died a while ago and the charging problem persists.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
try the recovery method with the battery in question, meaning: don't use the extended. just throw the the phone onto usb with the dead battery and try adb recovery.
hopefully you can save yourself a trip to VZ.
randpost said:
try the recovery method with the battery in question, meaning: don't use the extended. just throw the the phone onto usb with the dead battery and try adb recovery.
hopefully you can save yourself a trip to VZ.
Click to expand...
Click to collapse
I will tomorrow. I don't have computer access now. I'll keep the extended charged though
Sent from my ADR6425LVW using Tapatalk
pmania said:
I will tomorrow. I don't have computer access now. I'll keep the extended charged though
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Let us know how it goes! Good luck and happy Easter!
randpost said:
Let us know how it goes! Good luck and happy Easter!
Click to expand...
Click to collapse
Welp I just tried the adb reboot recovery and I am still getting the flashing light.
Will try again.
When this happened to me I had to keep plugging and unplugging the charging cable while holding the power button to get it to turn on. It's worth a try!
I did what others did n plugged into computer n booted to bootloader/ect
My rezound died this week end and wouldnt charge. Took it the VZ store and found out they no longer had in-store tech support. Anyway, the in store person concluded the charge port somehow wouldnt take a charge. Ended up calling tech support for a replacement. Should be here by Tues
Well I figured it out. I just got home to try again and I looked at the cmd window. It turns out I only typed "adv reboot recover" so yea my bad . Worked like a charm!
Sent from my ADR6425LVW using Tapatalk
pmania said:
Well I figured it out. I just got home to try again and I looked at the cmd window. It turns out I only typed "adv reboot recover" so yea my bad . Worked like a charm!
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
awesome man. glad you got it working.
Hi, so I recently put the BAMF custom rom on the phone last night, and it seemed to work alright, I got a couple of random reboots and bootloops, but I figured I would fix it in the morning, so I left my phone on the side, and in the morning when I woke up, it wouldn't even turn on, I've left it plugged in for a couple of hours into a wall charger, the front and back of my computer and nothing. If I take out the battery, and plug it in, the little orange light does appear at the top for about 5 seconds then disappears, nothing on the screen though at all. When it is plugged into my computer, I do near the noise that means it recognized something was plugged in but that's it.
Thanks
Neil
This is why you don't use clockworkmod
Your phone died somehow and is unable to charge because of clockwork
You have to charge the battery either in another phone or with a battery charger
Good luck
Sent from my ADR6425LVW using Tapatalk 2
neilman01 said:
Hi, so I recently put the BAMF custom rom on the phone last night, and it seemed to work alright, I got a couple of random reboots and bootloops, but I figured I would fix it in the morning, so I left my phone on the side, and in the morning when I woke up, it wouldn't even turn on, I've left it plugged in for a couple of hours into a wall charger, the front and back of my computer and nothing. If I take out the battery, and plug it in, the little orange light does appear at the top for about 5 seconds then disappears, nothing on the screen though at all. When it is plugged into my computer, I do near the noise that means it recognized something was plugged in but that's it.
Thanks
Neil
Click to expand...
Click to collapse
What recovery ?..if clockwork recovery sounds like battery ran down . If so search clockwork charging problems and you will find numerous threads with fixes. If you can get into hboot I would flash amon ra recovery then let phone charge.
Sent from my ADR6425LVW using xda premium
Omg, I'm an idiot lol....thanks a lot guys really appreciate it! This should fix it, ill post back though once I can try
Alright fixed it i think! Thanks a lot, not using CWM should be sticked lol!!!
I have been playing with Team Win RP. Its ok, has issues with kernels but over all I'm impressed.
Sent from my ADR6425LVW using xda premium
So I'll start off by saying I'm on Cyanogenmod 11.0 12/15 nightly, running CWM 6.0.4.5, and crpalmers kernel for nightlies 5.2.11.
While trying to take a picture today my phone turned off (had 50% battery left) and would not turn back on. When I plugged it into power it took a little while to power on, as if the battery was dead. When it finally turned on it booted to recovery, stayed on for a bit then turned off before I could do anything. When it restarted again I tried to re-install the rom but it died again before it could start. So i figured i would just keep it turned off and let it charge. As soon as I plug it in, it boots. Plug it into the computer, same thing. Any ideas???
Update: So I found a more powerful charger, 1150mV over a 1000mV, and that was enough to keep the screen on and charge the battery enough to let the phone boot normally. But now the phone only stays on for about 20 min before it reboots. Still not sure whats going on but atleast it boots.
Sounds like a bad battery to me.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Yeah that's what i was thinking. Strange considering it was a warranty phone.
i have the same problem do you fix it ?
GaMaRS said:
i have the same problem do you fix it ?
Click to expand...
Click to collapse
Once I let the battery charge fully I just returned back to stock. The how-to is in the forum some where, I can find it later but I'm on my way out the door. As of right now I'm s-off but completely stock and seems to be working fine. Maybe try a different kernel first and see if that helps.
steve013 said:
Once I let the battery charge fully I just returned back to stock. The how-to is in the forum some where, I can find it later but I'm on my way out the door. As of right now I'm s-off but completely stock and seems to be working fine. Maybe try a different kernel first and see if that helps.
Click to expand...
Click to collapse
it's my problem http://forum.xda-developers.com/showthread.php?t=2588101