Stock .21 firmware. Never tried any other ROMs. Battery went down to 1% last night, charged it on stock charger to 30% then moved it to a different charger. An hour after that I got a call, I hanged up and about 1 hour later I heard the phone buzzing every 30 sec or so, I looked at it and realized it's in bootloop. If I press Vol- and Power I can get it in fastboot and with Vol+ and Power in Recovery. Can't figure out what to do from there though.
Update: Pressed -+ and left it the whole day in that mode. Came home, and it booted up and looked fine for about 3 minutes then it shut down by itself. It seems to me that there's some sort of memory/storage corruption. Any suggestions on how to proceed from here?
Phone booted normally and I was able to use it for about 12 hours. I was doing a Whatsapp backup this morning when it shut down and got into the bootloop again.
nwaves said:
Phone booted normally and I was able to use it for about 12 hours. I was doing a Whatsapp backup this morning when it shut down and got into the bootloop again.
Click to expand...
Click to collapse
If you are using stock, immediately get rid of your usb c cable and buy a new one. There could be an issue with the cable that is causing problems with your battery.
Try to keep the charge percentage between 20% and 80%
Finally, your battery stats may be off. To resolve a battery stats issue you will need to reset the phone. Which again, if you are using stock and have never used a custom rom. You should definitely do a factory reset.
Same issue on 2 different chargers with 2 different cables that used to work well until now. None of the cables are stock. One of the chargers is stock, the other one aftermarket. My wife's S3 doesn't have any issues using the same cables and chargers. Issue seems to be happening when battery is full or almost full. Phone gets into a soft reset bootloop. I let it drain yesterday and was able to get in and do a factory reset. I then added my account and left it installing and updating apps overnight, while connected to the charger. Woke up with the phone off and after pressing power for 12 sec it got into the bootloop again. As you can imagine, it's impossible to keep the battery under 80%. Would it help if I try a custom rom? Maybe a new battery? I'm open to any suggestions as I really like this phone and can't find anything similar at a reasonable price.
So phone still reboots when battery is high. I can however get into Fastboot Mode and Tool All-In-One detects it. Tried to unlock the bootloader in the tool but it failed. I'm willing to try anything to get the phone back up and running but not sure where to start. Would really appreciate some guidance.
It really sounds like the battery is bad. You can buy a new battery for $8 .
If you replace the battery : Do NOT use a hairdryer to remove the screen. You will need a heat gun, they cost 7 dollars at harbor freight.
With a heat gun the lcd screen will practically fall off into your gloved hand.
I was going to offer to connect remotely and help with unlocking the bootloader and installing TWRP, Root and a Rom. But I sincerely believe that you need to get a new battery first.
Related
Okay so i've updated to Cyanogen 5.0 beta 2 no problems installed 2.6.32 then went back down to 2.6.29.6 and extra ram works and everything but now my phone wont charge the battery.
I'm quite sad as this is the problem, someone mentioned to let the charge die and then try charging it then. So i did that and now its stuck at 0 and when i remove the charger it instantly dies. Only one other member had the same problem but he hasn't replied to my pm or the thread yet so i'll wait for him as he had this abit earlier.
I've done multiple wipes, reinistalls, nandbackups and now i'm too afraid to do anymore flashing as the phone's battery is on 0%. If at any point it requires phone battery to flash it will die and i'll have a brick.
Hopefully someone out there might have a solution
I dont think its a ROM problem since you wiped. Perhaps its a hardware problem?
i dont know. Does anyone know if its safe to flash? As in if the charger is in it should be okay right?
Okay i think i'm screwed for awhile. The battery is drop dead and now i cant enter bootloader mode. Theres a orange led at top indicating its still working but wont enter bootloader due to insufficient power. Damn i was going to try to flash it
Now i need someone with either a nexus one or another battery
FML
Have you tried another charger or the USB cable?
Same problem here
I'm experiencing the same problem myself.
Installed Cyanogenmod 5.0b2, everything worked fine for the day.
tried JIT, had reboots, reverted back to fast
Upgraded to .32 kernel, my sdcard wasn't compatible so re flashed 5.0b2
called it an evening, my battery was full but I plug it into the charger overnight since it's my alarm clock.
Yesterday morning on the way to work, was playing music and noticed my battery had jumped from full down to around 12% in 30minutes. plugged it into car charger, and while it didn't drop anymore it didn't charge either.
Left it in pc usb charger off and on all day where the off times it dropped down to around 9% and never got above it. Eventually let it die on the way home thinking I'll re train the battery.
Left it off and plugged into wall charger for 4 hours, but batter stays at 0%
I'm glad I didn't sell my Dev G1 yet, as at least I have a working phone for the moment.
FYI I ran into this same problem running superboot himem on ERE27. My battery died and then nothing would charge it, even sitting it on AC power for 8 hours (while I slept) when I woke up my battery was stuck at 0% and would auto shutdown if I unplugged it.
I nandroid restored to stock ERE27 and immediately my battery started again. I think there might be some weird problem with himem mods. Not sure. Just to be safe I am totally over flashing custom stuff on my phone. My phone is too important to me to risk stuff like this happening.
I had my epic 4g and Odined to Dk28 with gps fix, clockwork, etc.
I played paintball and some of the dust went inside but when i got home i wiped the keyboard and slider. slider seems fine
I had the GPS running for about 2 hours until I got home. There was about 1/3 or 1/2 juice left but then It shut down and restarting, stating it only had no power left.
I took out the battery and it still boot loops (it gets to home screen - loads sd card/usb debugging/wifi and gps are on, but then reboots. im not even able to turn it off.
I tried pressing 1 and power for odin, it worked once or twice, but i wasnt able to flash it and restore it. (Yellow Com) but failed or not work.
after that 1 and power doesnt do anything, and neither does power, vol down, and camera.
please help, as i need to go back to work tomorrow.
thanks in advance.
Boot into Download Mode, flash back to stock (check the Epic Wiki for instructions), start over. Sounds like you've just got a bug somewhere in the whole process. Unless you've deleted, moved or whatever'd something you shouldn't have, you shouldn't be having this issue.
There is a thread for fixing bricked Epics.
If you press pwr, 1+pwr, vol. down+camera+pwr and nothing comes on nor charge light (red) comes on when plug in, then you have a very shiny expensive paper weight.
Sorry bro. I have one sitting on my desk with no insurance (OUCH)...
no light when i plug into usb or charger. cannot get into download mode. Wow i could brick a phone in under 3 weeks of getting it. going to sprint store.
Let us know what they say, Last time i went into the sprint store for an exchange they intentionally split water on the water damage film to try to say I voided my warranty. the reality is that they had already done diagnostics on the phone before they did this little trick so i was able to threaten to call my lawyer and got a replacement. I hate sprint so much....
Ouch, how did you know they already ran a diagnoses on it?
fone magically unbricked itself so i was able to get into download mode an Odin a 2.2 again. but the battery seems iffy...and this is only 3 week using the phone. its at 9% charged but shuts off. need to see if i can fully charge it. but may end up getting new phone at sprint store since its under 30 days and fone still looks new.
Maybe you just got a bad battery
Sent from my ComBadge
Sounds like you need to reset your battery stats.
didnt get new phone yet since phone hasnt bricked itself again yet.
i fully charged it last night and took it off teh charger before i went to sleep. now 10 hours later. its at 66% is that NORMAL?
sprint cust support said i should use default CHARGER to get best charging results. im using a ebay generic CABLE on USB does that matter? do they mean charger or cable or both?
A plain USB cable used to charge on a PC only draws 380mA to charge. A wall charger, like the one included with the phone, will charge at 600mA.
But still, neither should take the 10 hours you are seeing really. Wall charger is usually 3-3.5 hrs and USB charging is somewhere around 5-6.
victric said:
didnt get new phone yet since phone hasnt bricked itself again yet.
i fully charged it last night and took it off teh charger before i went to sleep. now 10 hours later. its at 66% is that NORMAL?
sprint cust support said i should use default CHARGER to get best charging results. im using a ebay generic CABLE on USB does that matter? do they mean charger or cable or both?
Click to expand...
Click to collapse
66% after 10hrs of use seems normal to me.
sry double post. using tether internet...
UH OH!
I was installing from some apks and the phone got into boot loop AGAIN!
I'm thinking about going to sprint and exchanging it. But im afraid of rooting it again...bc i think it might trigger the boot loop again. Any ideas?
re: last post, 66% after 10 hours of idle with screen off (this is "use"?) is normal?
victric said:
UH OH!
I was installing from some apks and the phone got into boot loop AGAIN!
I'm thinking about going to sprint and exchanging it. But im afraid of rooting it again...bc i think it might trigger the boot loop again. Any ideas?
re: last post, 66% after 10 hours of idle with screen off (this is "use"?) is normal?
Click to expand...
Click to collapse
Odin that thing back to 2.1 and exchange it.
Hello guys, this is my first time posting up in XDA and I am encountering a very weird problem with my N4
Disclaimer, the following is a long write but please bear with me and give a read.
Here's my problem after flashing the simple asop 29/5 build for mako. I come from same rom build 21/5 but i did a clean flash for the latest build. As soon as success flashing the latest build with gapps, then as usual will proceed reboot the system. Just right before the boot animation, the phone immediately went dead. I am sure that the phone is still left with 50%+ of battery at the moment.
Anyhow, I decided to plug it into charger. And voila, the phone now able to go through the boot animation and everything just fine. After setting up and restoring backups, I unplugged the charger, its 75%+ on the battery. Within 10-15 seconds, the phone immediately go dead again. I hit the power button and tried to boot up. Again, right after the Google logo screen, the phone went dead.
Commonly this indicate a problem with the battery. Yeah, but I went into recovery twrp and disabled the screen timeout & max the brightness. Guess what, surprisingly it lasted more than an hour which proves that this wasn't battery fault.
What had I tried so far, is just switched off the phone and plugged into charge for 2 hours. And obviously it doesnt solve the problem. I am backing up all the data at the moment and plans to drain the battery all the way down just leaving it screen on at recovery.
Anyone who know what happening with my n4 or encounter similar experience, please feel free to share the solution. Many thanks
Jz Chong said:
Hello guys, this is my first time posting up in XDA and I am encountering a very weird problem with my N4
Disclaimer, the following is a long write but please bear with me and give a read.
Here's my problem after flashing the simple asop 29/5 build for mako. I come from same rom build 21/5 but i did a clean flash for the latest build. As soon as success flashing the latest build with gapps, then as usual will proceed reboot the system. Just right before the boot animation, the phone immediately went dead. I am sure that the phone is still left with 50%+ of battery at the moment.
Anyhow, I decided to plug it into charger. And voila, the phone now able to go through the boot animation and everything just fine. After setting up and restoring backups, I unplugged the charger, its 75%+ on the battery. Within 10-15 seconds, the phone immediately go dead again. I hit the power button and tried to boot up. Again, right after the Google logo screen, the phone went dead.
Commonly this indicate a problem with the battery. Yeah, but I went into recovery twrp and disabled the screen timeout & max the brightness. Guess what, surprisingly it lasted more than an hour which proves that this wasn't battery fault.
What had I tried so far, is just switched off the phone and plugged into charge for 2 hours. And obviously it doesnt solve the problem. I am backing up all the data at the moment and plans to drain the battery all the way down just leaving it screen on at recovery.
Anyone who know what happening with my n4 or encounter similar experience, please feel free to share the solution. Many thanks
Click to expand...
Click to collapse
Have you tried making a clean wipe and trying either stock or another ROM, to see if it works then?
Your test doesn't prove it's not the battery's fault. Flash back to stock, see if the problem persists and if it does then you know you have a hardware problem. Could be the battery.
DrFredPhD said:
Your test doesn't prove it's not the battery's fault. Flash back to stock, see if the problem persists and if it does then you know you have a hardware problem. Could be the battery.
Click to expand...
Click to collapse
Hello, much appreciate your reply. I flashed back to stock 5.1.1 now and yet this problem is still persisting. Thus pretty obvious thats an hardware faulty.
In another forum, a guy with Nexus 7 had similar situation as me, and he suggests that its the battery or the circuit board at the charging port went kaput.
Guess nothing else I could do right now, gonna send in the phone for repair and hope the bill wont cost as much as a used nexus 4
So, 2 days ago I was charging my device (XT - 1562 Indian Version 16GB) and when I saw the phone after 2 hours the battery was still at 15%... so I got into the battery options to check if the battery was charging and it was showing "Not charging"(SS attached) so I rebooted my phone and it was still showing not charging, I also did a factory reset and still the problem was not solved so I booted into the fastboot mode and there it was showing that the battery is charging. I was confused so I thought that there may be a firmware problem(6.0), so I downloaded factory images of 6.0.1 and flashed them(the BL was locked) and still the problem was there then I unlocked the BL and flashed 5.1.1 and problem still persists. Guys pls help me. :crying:
Also please tell me how can I flash 6.0.1 again via Fastboot mode. I am still at stock 5.1.1
Edit : Update : Now I have installed a custom ROM (CM 13.1 by Temasek) and now the phone is charging like it should but it charges till 82~85% and then stops charging. Cant give the phone to the service center because I unlocked the BL.
thesaurabh7777 said:
So, 2 days ago I was charging my device (XT - 1562 Indian Version 16GB) and when I saw the phone after 2 hours the battery was still at 15%... so I got into the battery options to check if the battery was charging and it was showing "Not charging"(SS attached) so I rebooted my phone and it was still showing not charging, I also did a factory reset and still the problem was not solved so I booted into the fastboot mode and there it was showing that the battery is charging. I was confused so I thought that there may be a firmware problem(6.0), so I downloaded factory images of 6.0.1 and flashed them(the BL was locked) and still the problem was there then I unlocked the BL and flashed 5.1.1 and problem still persists. Guys pls help me. :crying:
Also please tell me how can I flash 6.0.1 again via Fastboot mode. I am still at stock 5.1.1
Click to expand...
Click to collapse
Maybe fault in hardware.
Automated reply by JARVIS
K.khiladi said:
Maybe fault in hardware.
Automated reply by JARVIS
Click to expand...
Click to collapse
Thanks for the reply bro. I have updated the thread so can you tell me what is the problem.
are you using the original charger and cable ?? charge the Device when it's off then turn onforum.xda-developers.com/showthread.php?t=1782420
I'm having this exact same problem on my xt1575. I bought it from a nice dude on Swappa, but he seemed pretty green concerning phones in general. He rooted/unlocked it, then appears that he kept the stock ROM while flashing the franken kernel. I didn't notice this for the first day or two as I opened it and poked around for some signs of something loose/water damage: nothing.
I couldn't sleep last night, so all morning I've been doing what I can to play around with clearing caches, flashing different ROMs, and anything else I can find in the software side, but aside from somehow getting it to get past the previous cap of 4% to a whopping 25% before slamming down to 11% (percentages waver constantly), I'm stuck and desperate to figure it out. I've even tried the stock turbo charger, the stock charger for an old Moto X 2014, and as of writing this just now a Samsung quick charger for the giggles.
I have parts for all kinds of Moto X 2014/Nexus 6 lying around, so I took the risk of connecting a Moto X 2014 battery up to see how it behaved. It read the battery level around mid-seventies and didn't seem to drop at any exaggerated rate but still kind of bounced around a tad. It would charge at times, but otherwise still wouldn't show the battery as being charged. I didn't think too much of it because the 2014 is of course a different model at a much smaller capacity, so I didn't want to try leaving it on the charger for fear of overcharging. The only thing left that I haven't done is hook up the Play battery to another motorola because I don't have any screens to monitor progress and see how consistently it reads to determine if it's the battery that's somehow gone wonky.
So in summation/where I'm at right now: I'm having this same problem; I've tried both hardware and software tinkering to no avail; I feel this is still somehow kernel/software related, but I'm not sure how to completely obliterate everything to start from stock. Please forgive how scatterbrained I am right now, I'm tired yet wide awake and irritated with the whole situation; there's NOTHING I can find in the forums or elsewhere outside of stock replies like "are you using the original charger?"
My moto x play not change in normal it only charge in factory mode that to 75-82℅ only.
Let it discharge fully then put on charge without booting up
PSxplay said:
Let it discharge fully then put on charge without booting up
Click to expand...
Click to collapse
I have did that still it's not charging, it's showing power symbol without percentage showing.
Shajj99 said:
I have did that still it's not charging, it's showing power symbol without percentage showing.
Click to expand...
Click to collapse
I have tried after battery fully drain, still it's not charging again I am charging mobile in factory mode. Is there any solution please help me. In factory mode i am not getting signal.
So no change in behavior. I did notice that when in TWRP that the CPU Temp value is crazy, and any reporting software says the battery is at -23.8° C and always cold, even on a brand new replacement battery (obviously send like that is what's keeping it from charging). I even went as far as to put a heat gun on it from a distance to artificially actuate any sensors and got nothing. The one time it did report normal temps it charged fine for a whole day but hasn't returned to normal since. This **** is maddening...
I know this is a long shot, but have you tried resetting the battery stats?
http://forum.xda-developers.com/showthread.php?t=1699687
I had this problem but yesterday I can solve that
First I put stock firmware
Wait for fully discharge
And wait full shutdown
I put an moto g 2013 charger (550mA 5V)and led stay on around 5 min but not charge
After put Nokia n86 charger (1A 3.5V)5 min and not charge
After i put an orginal moto turbo charger
And start to charge wait for 9%
Turn on the phone
Clear battery stats with battery calibration app
Wait for full discharge
Wait for full turn off
I put a Nokia n86 charger wait 5 minutes vibrates and start to charge like the beginning
Any other suggestions or solutions? Still my phone only charges in recovery mode. I have a aukey fast charger. Tried different kernels and roms without success.
The solution with the nokia chargers seems really strange and i dont have that type of charger.
Regards
Someone fixed this? I have the same problem and can't solve it. I have cm 13 by temasek and the first time the x play charged up to 83% but after a full discharge and a clean of battery stats, I olny could charge it via factory mode, like in stock 6.0.1
I dont know why but after i opened the phone and disassembled the battery it worked after putting it back together. Disconnected the cable to mainboard as well as nfc antenna. Then carefully pried the battery out. Its slightly glued to the mb. Then I held power button down for a few sec as read in a different forum. Afterwards I connected power cable back but left the battery next to the phone. Booted the phone and charging worked. Than I reassembled the phone Ehen I was sure everything worked. I was about to change the battery but now it works. I flashed different Roms and kernels without any improvment before. After I got it working I flashed a nandroid backup of a resurection Rom image that didnt worked before. Now its running perfect.
pulpokraken said:
I dont know why but after i opened the phone and disassembled the battery it worked after putting it back together. Disconnected the cable to mainboard as well as nfc antenna. Then carefully pried the battery out. Its slightly glued to the mb. Then I held power button down for a few sec as read in a different forum. Afterwards I connected power cable back but left the battery next to the phone. Booted the phone and charging worked. Than I reassembled the phone Ehen I was sure everything worked. I was about to change the battery but now it works. I flashed different Roms and kernels without any improvment before. After I got it working I flashed a nandroid backup of a resurection Rom image that didnt worked before. Now its running perfect.
Click to expand...
Click to collapse
So, may the problem be in the pins when the battery is plugged into the mb? I'll try that! thanks!
Still having this issue, the solution with the chargers didn't work for me, neither the battery solution, suggestions?
How to solve the problem?
Please
Same issue
My Moto X Play has the same issue. It will only charge in Factory Mode. I had this issue before at 10-11 months old and had it 'fixed' under warranty, now 2-3 months later the same issue has occurred. Of course the warranty is only 1 year...
Glad I am not alone in this issue but i wish there was an easy fix! Putting me off getting another Moto...
Same problem occurred with me( Moto X Play).
My phone was not charging, it was stuck in some percentage and was not increasing or neither decreasing while plugged in to charger. But when i put it into recovery mode, it charges. But that was not the solution to the problem.
So, i have tried factory reset.
but problem was not solved.
i googled for the solution, but couldn't find the right solution. And i was stressed (I have a girlfriend, and living in very distance relationship, for me a smartphone is very important).
And was thinking of buying a new phone but not the Motorola, but couldn't afford at the time.
At the same time, i thought of repairing it by myself, by fixing the battery properly.
Without thinking about voiding the warranty and Motorola support, i unbolt every screw of the phone. and finally , finally, finally i made it by removing the battery and fixing it again(charger was plugged while removing the battery and fixing, and phone switched off while removing).
And now my phone is charging properly.
Hope I have helped every person concern to this same problem.
Thank you
So. My phone has this problem, and its pretty weird (IMO). It is possible that it is a hardware problem.
I going to work and I dropped my phone. Didn't think much of it. The phone worked fine for several hours. It started around 40% and only declined somewhat, until about 2-3 hours later where it dropped rapidly to 6%. It was in my pocket when it dropped. I figured at the time that I had just forgotten to turn the screen off, so it drained much more battery. I then plugged it in, and it charged for a little while on a non-turbo charged cord, getting to 21% (which is what it said when it was off). After I turned it on however, it was only at 12%. I didn't bother with it at the moment, but after about 5 minutes it dropped to zero in about 5-10 seconds from when it started dropping. This was concerning, but I had to go back to work so I plugged it back in. When I came back and rebooted it showed 11%, and it stayed at 11% for several hours while I was using it, even though I wasn't charging it. Then randomly it dropped super quickly and died. I turbo charged it overnight. In the morning I booted it up and it immediately shut down claiming there was 0% battery life. It will not boot up without being plugged in. This goes on.
Usually, I charge it for a while and it will give a higher number than it will say when it boots up. It sticks at that boot up number for longer than it should, then dies rapidly. Occasionally it will boot up to be 0% and immediately die. I have tried turning in on and off again (without it dying) and it wont turn back on claiming too low of power regardless of how charged it said it was before. I have tried various charging cables and wall outlets. I have tried several battery repair apps, which did nothing. I was going to try and do a root version, since I figured that would be better but cannot root it. (Using adb to sideload comes up with an error (signature verification failed), trying to flash twrp fails (pre-flash validation failed) and normal root methods fail.) Oh yeah, and I've also factory reset it a few times.
So it seems to me that it's a software problem, namely the battery driver, since it appears to be charging and holding a charge for the most part, but then shutting down randomly due to the driver saying it is at 0% battery life. Alternatively, it could be a problem with the battery or charging port, although nothing seems to be wrong with the charging port visually.
Also potentially of note is that my normal turbo charger, when plugged in, puts a lightning bolt icon in the battery symbol, but on battery usage it says not charging. This could also be the chargers fault, since it had begun to fail previously (only working at certain angles) but it worked earlier the same day and now doesn't.
I didn't install any new updates to the OS or installed any new apps before this occurred either.
Any idea whats going on and how to fix it?
EDIT: I've been trying to look up and see if there was a driver or something for the battery that I could reinstall but I couldn't find anything. So, I ordered a replacement battery of Amazon. Now the question becomes will that fix my problem if I replace the battery?
Think so this might solve your issue ,but getting it checked before ordering would be wise.
Going through your rooting steps , i didnt see that you unlocked your device thats why you are getting errors of signature verification failed.
There is no separate battrey driver for Android its the part of OS itself so you dont need to mess up with that area
Uh... yeah well, Droid Turbo 2's can't root. It wont work. The bootloader is locked up tight, even if you select it in developer options it does nothing.
JWeller said:
Uh... yeah well, Droid Turbo 2's can't root. It wont work. The bootloader is locked up tight, even if you select it in developer options it does nothing.
Click to expand...
Click to collapse
HI,
has your problem resolved after replaced the battery?