Related
Hey guys
Im looking for some help, although im not sure theres much that can be done...
These are the steps i did on an Australian p6810 stock device:
Install ICS using odin
Using temporary CWM, root the device
Flash CM9 to it
Wiped dalvik, batt stats, cache, factory restore (in both stock and cwm)
Boot to CM9 fine, but wifi doesnt work
Apply the wifi.zip fix as well as gapps
Boot to CM9 fine, but wifi doesnt work and gapps arent visible (or installed)
Applied the fix and gapps again, still didnt fix
So i decided to reflash CM9
Flashed CM9 and straight after did gapps and wifi.zip
Did a CWM factory reset
During the reset process (which took a loooong time), my device turned off (pretty sure it had plenty of battery)
BRICK
Now i cant turn my tab on at all. The screen doesnt respond, no matter how long or how many times i press the power button
Any help?!
have you try to charge your tab... then try to go to download mode... if it still working... flash stock ics again...
edan1979 said:
have you try to charge your tab... then try to go to download mode... if it still working... flash stock ics again...
Click to expand...
Click to collapse
its been charging for about half an hour. still not turning on so cant get to download mode!
I was reading a post on here about bricking and battery issue with the tab 7.7 which should be easy for you to find...Google it
On that post they spoke about taking the tab to any cell shop and having different battery packs put to it and this had revived the tab, the two guys who had got it working again said they had used a bigger voltage / amp battery to kick it back to life again. do a search and see what you find.
Now dont get me wrong, I have no idea how they got to do that as the battery is built in and the power connection is through the 30pin cable....maybe they plugged in the 30pin and used a transformer on the USB side to jump the battery back to life, I have done something like that before on a old phone that didnt charge and it worked, but its not the safest as wrong voltage could pop something.
Or the only other thing I can think of is the battery is totally dead or broken, in that case I would suggest a repair shop....but thats last on the list!
I am sure it might not have been enough charge before you strated...I had my battery die over night and it took a good 30min on charge to start showing any charge life at all.
Once you get the power working, I am sure we can un-brick your baby for you
slide200sx said:
I was reading a post on here about bricking and battery issue with the tab 7.7 which should be easy for you to find...Google it
On that post they spoke about taking the tab to any cell shop and having different battery packs put to it and this had revived the tab, the two guys who had got it working again said they had used a bigger voltage / amp battery to kick it back to life again. do a search and see what you find.
Now dont get me wrong, I have no idea how they got to do that as the battery is built in and the power connection is through the 30pin cable....maybe they plugged in the 30pin and used a transformer on the USB side to jump the battery back to life, I have done something like that before on a old phone that didnt charge and it worked, but its not the safest as wrong voltage could pop something.
Or the only other thing I can think of is the battery is totally dead or broken, in that case I would suggest a repair shop....but thats last on the list!
I am sure it might not have been enough charge before you strated...I had my battery die over night and it took a good 30min on charge to start showing any charge life at all.
Once you get the power working, I am sure we can un-brick your baby for you
Click to expand...
Click to collapse
Thanks for the advice! I'm not sure it's a battery problem though? Is there anyway I can tell?
To be honest, the only way you are going to know if the battery is the issue is if you take it for a battery swop....will be a samsung outlet and cost you. I have heard that some 7.7's that have done wipes from in CWM and not the 3e recovery have caused bricking, it may be that this has happened to you. please check the other brick posts on here and I am sure after reading them all you will have a better idea of what is going on. before I do anything on mine I check all the bricking posts to see what could cause the problem and stay away from those changes or mods....if possible
sometimes plugging it in and out of the wall charger and then computer and back again to wall might help, I dont promise anything.
how long have tried holding the power button, and have you tried holding the power button while pluggin it in....
let me know what happen's please....
slide200sx said:
To be honest, the only way you are going to know if the battery is the issue is if you take it for a battery swop....will be a samsung outlet and cost you. I have heard that some 7.7's that have done wipes from in CWM and not the 3e recovery have caused bricking, it may be that this has happened to you. please check the other brick posts on here and I am sure after reading them all you will have a better idea of what is going on. before I do anything on mine I check all the bricking posts to see what could cause the problem and stay away from those changes or mods....if possible
sometimes plugging it in and out of the wall charger and then computer and back again to wall might help, I dont promise anything.
how long have tried holding the power button, and have you tried holding the power button while pluggin it in....
let me know what happen's please....
Click to expand...
Click to collapse
So i took apart my tab in hopes i could do a battery pull:
http://www.jtagbox.com/jtag-news/ri...y-tab-77-unbrick-boot-repair-supported-world/
and no luck, it doesnt auto power on
Im considering doing jtag... but hmmmmm
https://www.dropbox.com/sh/rqhhgs34vuzt4u4/fGwL0TiSYc
i pulled out the power/battery cable, plugged the tab into the computer and then plugged the power in. nothing.
it also didnt work when i plugged it into the wall
When plugged in my wifi chip gets warm... hmmm
@Scottyn...
Dude, you need to do the swopping of power from wall socket to computer then back again and again and again......all the time while doing this holding the power button in.....try it
Also, if you have puled the thing apart now you should be able to test the battery for power with a volt meter or something....
does the battery have power...
does the battery get power from the cable or pin running to the battery?
Can you turn the tablet on with a different power source to the battery terminal on the phone?
I would check these things first, then hold thumbs....I dont know, if it's not the battery then it may very well be a dead hardware issue and not a data issue or fried memory as they will normally boot the tablet to a point.....
May very well be the battery cooked
Im too scared to attach a an external powersource to replace the battery. I have the equipment, but it could easily fry the rest of the board
Ive closed the device back up, so ill have to reopen it before i chuck a voltmeter on the batteries
and ive swapped from computer to the wall about 10 times (swapping every 5 seconds). Nothing
Plus; if i diagnose the problem as a fried battery then cant really do anything about it
scottyn said:
Hey guys
Im looking for some help, although im not sure theres much that can be done...
These are the steps i did on an Australian p6810 stock device:
Install ICS using odin
Using temporary CWM, root the device
Flash CM9 to it
Wiped dalvik, batt stats, cache, factory restore (in both stock and cwm)
Boot to CM9 fine, but wifi doesnt work
Apply the wifi.zip fix as well as gapps
Boot to CM9 fine, but wifi doesnt work and gapps arent visible (or installed)
Applied the fix and gapps again, still didnt fix
So i decided to reflash CM9
Flashed CM9 and straight after did gapps and wifi.zip
Did a CWM factory reset
During the reset process (which took a loooong time), my device turned off (pretty sure it had plenty of battery)
BRICK
Now i cant turn my tab on at all. The screen doesnt respond, no matter how long or how many times i press the power button
Any help?!
Click to expand...
Click to collapse
We had a similar faith. It was when this wiping thingy messed up my Tab. My only consolation was that my Tab is under warranty and did some make up story at the service center. Had replaced the motherboard and now up and running. I'd promised myself that I'll limit my "genius" with rooting and flashing an official fw. Custom rom is a big no for me, no matter how great and stable it was. The wiping part is like kiss of brick. Yes, i know...there's a disclaimer.
sweet. Ive decided to send it all back over to australia. annoying, but ill get a guaranteed fix
I think ill stick to stock ICS from now on
scottyn said:
So i took apart my tab in hopes i could do a battery pull:
http://www.jtagbox.com/jtag-news/ri...y-tab-77-unbrick-boot-repair-supported-world/
Do you mean you opened up the tabs case?
how did you do this?
any pics?
I ve read you have to lift the screen from the back cover..
It scares me to think about levering it and cracking the screen or something..
Click to expand...
Click to collapse
Trying to fix a family members xt907 so here's the situation which has been nothing but headaches for me:
1. The Phone is only 7 months old and the bootloader is unlocked so warranty exchange is out of the question. She let the battery run down until the phone died. Then without charging the phone she turned it back on and it died again. From that point she couldn't get it to charge or turn back on while plugged in. At this point she brought it to me.
2. I got the phone and did a soft reset which finally got the charging screen to come up (showed the actual charging icon and the fill meter would flash up and then back down periodically). Problem is it never went past 0% after charging all night. I went ahead and tried to power it up thinking maybe it was just a glitch with the charging screen. Phone wouldnt boot. Just stuck at the Motorola logo. Another soft reset and the phone finally boots but now the battery icon showed a '?' and status showed '5% - Unknown'.
3. Performed a factory reset. No change. So I used RSD to flash the stock 4.1.2 firmware/kernel/modem, etc... What I found strange here is that despite the low battery Fastboot AP showed battery as OK, not low and let me flash (bootloader is unlocked, not sure if that affects low battery flashing or if that safeguard just wasnt built into the M).
4. So phone boots back up and shows 7% battery. Plugging in the charger at first notice has no affect. Battery stats shows '7% - Not Charging'. So I unplug the charger and the low battery warning pops up. Plug it back in and phone still doesnt register as charging, but says 'Not Charging'. Then I notice that the lockscreen shows '7% Charging'. Weird. Regardless of all that, the battery was not charging. The percentage never goes up and after reboots the percentage will remain the same. The battery does slowly discharge on the charger if I have it powered on.
5. I tried flashing a couple different roms before flashing back to stock and all had the same problem. I've formated /system hoping it was a problem with the OS but it didnt help. All of these charging tests were performed with the stock Motorola usb cable plugged into the wall charger. I tested the Motorola charger against my S4 to verify it works and also tried my Samsung charger on the Razr and it made no difference. However, booting the Razr M up with the Samsung charger resulted in the '?' in the battery icon and a notification in the status bar saying something about a CommServer starting. This notification was persistant and could not be dismissed. If I reboot the phone with the Motorola charger or no charger then that notification and the '?' dont appear.
6. I should also point out that I opened the phone up and disconnected the battery from the board and discharged the board. As a last resort I completely removed the battery and peeled back the tape on the bottom of the battery to expose the + and - terminals on the battery and wired it up to a stripped down charger and left it for a bit. Upon putting the battery back in the phone it showed a charge of 30% but still had all the same problems otherwise. So the battery is capable of taking a charge, it just wont take it through the phone, whether powered on or off. Thats what leads me to believe the battery itself is not bad. Its not practical for her to pull the battery to charge it, obviously. The phone detects the cable being plugged in and I can transfer files via usb cable to/from the computer no problem, so I'm fairly sure the Micro usb port is ok. Just refuses to charge.
A little lengthy but I'm at my wits end on this and really dont want to have her buy a $50 battery and then its a problem with the phone. I dont usually get stumped when it comes to fixing something but this one really has me. So if anybody can shed some light on this situation it would be greatly appreciated.
CallMeAria said:
Trying to fix a family members xt907 so here's the situation which has been nothing but headaches for me:
1. The Phone is only 7 months old and the bootloader is unlocked so warranty exchange is out of the question. She let the battery run down until the phone died. Then without charging the phone she turned it back on and it died again. From that point she couldn't get it to charge or turn back on while plugged in. At this point she brought it to me.
2. I got the phone and did a soft reset which finally got the charging screen to come up (showed the actual charging icon and the fill meter would flash up and then back down periodically). Problem is it never went past 0% after charging all night. I went ahead and tried to power it up thinking maybe it was just a glitch with the charging screen. Phone wouldnt boot. Just stuck at the Motorola logo. Another soft reset and the phone finally boots but now the battery icon showed a '?' and status showed '5% - Unknown'.
3. Performed a factory reset. No change. So I used RSD to flash the stock 4.1.2 firmware/kernel/modem, etc... What I found strange here is that despite the low battery Fastboot AP showed battery as OK, not low and let me flash (bootloader is unlocked, not sure if that affects low battery flashing or if that safeguard just wasnt built into the M).
4. So phone boots back up and shows 7% battery. Plugging in the charger at first notice has no affect. Battery stats shows '7% - Not Charging'. So I unplug the charger and the low battery warning pops up. Plug it back in and phone still doesnt register as charging, but says 'Not Charging'. Then I notice that the lockscreen shows '7% Charging'. Weird. Regardless of all that, the battery was not charging. The percentage never goes up and after reboots the percentage will remain the same. The battery does slowly discharge on the charger if I have it powered on.
5. I tried flashing a couple different roms before flashing back to stock and all had the same problem. I've formated /system hoping it was a problem with the OS but it didnt help. All of these charging tests were performed with the stock Motorola usb cable plugged into the wall charger. I tested the Motorola charger against my S4 to verify it works and also tried my Samsung charger on the Razr and it made no difference. However, booting the Razr M up with the Samsung charger resulted in the '?' in the battery icon and a notification in the status bar saying something about a CommServer starting. This notification was persistant and could not be dismissed. If I reboot the phone with the Motorola charger or no charger then that notification and the '?' dont appear.
6. I should also point out that I opened the phone up and disconnected the battery from the board and discharged the board. As a last resort I completely removed the battery and peeled back the tape on the bottom of the battery to expose the + and - terminals on the battery and wired it up to a stripped down charger and left it for a bit. Upon putting the battery back in the phone it showed a charge of 30% but still had all the same problems otherwise. So the battery is capable of taking a charge, it just wont take it through the phone, whether powered on or off. Thats what leads me to believe the battery itself is not bad. Its not practical for her to pull the battery to charge it, obviously. The phone detects the cable being plugged in and I can transfer files via usb cable to/from the computer no problem, so I'm fairly sure the Micro usb port is ok. Just refuses to charge.
A little lengthy but I'm at my wits end on this and really dont want to have her buy a $50 battery and then its a problem with the phone. I dont usually get stumped when it comes to fixing something but this one really has me. So if anybody can shed some light on this situation it would be greatly appreciated.
Click to expand...
Click to collapse
I presumed you tried to wipe the battery stats via the battery calibration app? not that I think it would make a difference. another option is enable/disable USB debugging. you could also try charging into a PC or a different outlet (perhaps that outlet does not provide a good current)?
not really sure, just tossing out some ideas...
jco23 said:
I presumed you tried to wipe the battery stats via the battery calibration app? not that I think it would make a difference. another option is enable/disable USB debugging. you could also try charging into a PC or a different outlet (perhaps that outlet does not provide a good current)?
not really sure, just tossing out some ideas...
Click to expand...
Click to collapse
I actually installed cwm recovery just to wipe battery stats. Im assuming it works the same way but I'll give the app a try. I'll try anything at this point. Tried your other ideas already though and didnt make any difference.
I appreciate the input. I'll give that app a try and see if it does something different from wiping battery stats in recovery.
CallMeAria said:
I actually installed cwm recovery just to wipe battery stats. Im assuming it works the same way but I'll give the app a try. I'll try anything at this point. Tried your other ideas already though and didnt make any difference.
I appreciate the input. I'll give that app a try and see if it does something different from wiping battery stats in recovery.
Click to expand...
Click to collapse
Doubt it. However, the issue seems to be with the hardware, and since it is not a software issue, Motorola could honor the warranty. Last resort would be to unroot and see if you can get an exchange.
Sent from my XT907 using xda app-developers app
have you tried a non moto cable? the one that came with my fone was total crap, would continuously connect and disconnect when i hooked it up to my comp or try to charge it, so i tried my old samsung cable and i didnt have any disconnect problems at all. just a suggestion
CallMeAria said:
I actually installed cwm recovery just to wipe battery stats. Im assuming it works the same way but I'll give the app a try. I'll try anything at this point. Tried your other ideas already though and didnt make any difference.
I appreciate the input. I'll give that app a try and see if it does something different from wiping battery stats in recovery.
Click to expand...
Click to collapse
Did you ever find a solution? I am having the same issues with my xt907.
What did you have it plugged in to? The fact that it said it was not charging indicates maybe you didn't have enough power coming through the charging port...
Sent from my XT907 using Tapatalk 4 Beta
uthkuknwme said:
have you tried a non moto cable? the one that came with my fone was total crap, would continuously connect and disconnect when i hooked it up to my comp or try to charge it, so i tried my old samsung cable and i didnt have any disconnect problems at all. just a suggestion
Click to expand...
Click to collapse
yeah I tried my Samsung cable as well.
jgramkow said:
Did you ever find a solution? I am having the same issues with my xt907.
Click to expand...
Click to collapse
No. Verizon finally sent her a refurb replacement. I got the battery to charge up by taking it out and rigging a charger to it. But the phone still wouldnt accept a charge with the battery back in and it lost the charge it did have 2-3 times faster than normal. Battery Stats also showed the battery was showing a pretty decent voltage so unless the battery itself has a low charge circuit that gets tripped I'd be hesitant to point to the battery itself. And the charger port transfered files just fine and the phone recognized when the charger was plugged in (would go from 'discharging' to 'not charging'. So yeah, I was left stumped. Hopefully somebody else can get this solved for you.
CallMeAria said:
yeah I tried my Samsung cable as well.
No. Verizon finally sent her a refurb replacement. I got the battery to charge up by taking it out and rigging a charger to it. But the phone still wouldnt accept a charge with the battery back in and it lost the charge it did have 2-3 times faster than normal. Battery Stats also showed the battery was showing a pretty decent voltage so unless the battery itself has a low charge circuit that gets tripped I'd be hesitant to point to the battery itself. And the charger port transfered files just fine and the phone recognized when the charger was plugged in (would go from 'discharging' to 'not charging'. So yeah, I was left stumped. Hopefully somebody else can get this solved for you.
Click to expand...
Click to collapse
Just an update: I ended up buying a replacement battery and it fixed the charging issue. I rsd back to stock. Then, playing around with it, I booted to bootloader and selected "Factory" and it immediately booted back to stock, but, the battery had a "?" again. Ready to throw the damn phone against the wall, I rebooted it. The "?" is mysteriously gone. What is the "Factory" setting? I think I tried it before, but had CM10.1 installed. My theory is that this "factory" boot from bootloader actually soft bricked the phone. Either that or the issue was truly the battery and simply replacing it fixed things. I am up and running now, cm10.1 is flawless, imho. Thanks for the quick reply and I hope this helps anyone with similar issues.
Beware of the "Factory" bootloader option...........
Here we go again. Upon a reboot into recovery. Recovery is twrp 2.5. What I notice is the motorola boot img takes an extremely long time (2 minutes) to turn off and cyanogenmod to begin. Could there be something corrupt in the bootloader? Is there any way to reload the bootloader on this device? Anyone have any ideas? Could it be Recovery?
Hi folks,
Fortunately I've not had much necessity to post here for help. However, that's now change.
I am looking for suggestions on:
1) What might be the cause of an issue with my N4
2) What I might be able to do about it.
Here's the background:
My N4 was working fine. Stock device, 4.4.2, no rooting, etc.
The other day it spontaneously turned off. I was not able to turn it back on. "Google" would appear on the screen, but a few seconds later would vanish and device was off again.
I did figure out I could turn it on (most of the time) when it was plugged into a power source. But detaching from that power source (whilst it was running) would result in it turning off within a couple of seconds at most.
I managed to back up most of my data, whilst having it plugged in and turned on.
A few days later device tells me there's a 4.4.3 update. I update it.
Issue remains.
I then try to initiate a factory reset.
Device reboots during that process. But fails to restart.
I could no longer restart it whether plugged in or not.
It can sit in bootloader mode without being plugged in, for as long as it takes to run the battery down.
It can't be in recovery mode without ext power.
I load the TWRP recovery image. That is on and working fine.
I can access the device with fastboot command (via Windows 7)... which is how I got the TWRP image on there.
In recovery mode the device is not detected by windows, and adp command can't see the device.
This is about where I have come unstuck. I was attempting to install a clean Android 4.4.3 image onto the device. But I can't get ADB access to it. Tried on a Mac and a Windows 7 PC.
UPDATE: I did manage to complete instructions for installing new Android 4.4.3 image over fastboot mode. But even after completing the steps successfully, device won't start. Just "Google" flashes up, and devices stops after few seconds.
HARDWARE FAILURE?: It's possible this whole issue is hardware related and I'll have to ditch the device. If that likely? I've seen some people mentioning similar issues, which they resolved by replacing the USB port board. Is that likely to cause this kind of issue?
Does some kind person have any suggestions on steps I can from here?
I'd really like to recover this beast... it's my first and only smart phone, and would hate to drop to a cheap replacement cell phone for the foreseeable future.
Thank you...
Somehow my title was blank (just a [Q]). Might explain why I got no replies so far :silly:
Updated.
If its happening even after a full reset and flashing of the factory image, that most likely means it is a hardware issue, maybe the battery. You can try changing it yourself or getting someone else to do it. This is what I think the issue is.
lolcakes203 said:
If its happening even after a full reset and flashing of the factory image, that most likely means it is a hardware issue, maybe the battery. You can try changing it yourself or getting someone else to do it. This is what I think the issue is.
Click to expand...
Click to collapse
Hi there,
Thanks.
Regarding the battery... I had considered that. Although the battery was working fine right up to the time the N4 started having issues. Even during the issues... I could charge and discharge the battery as per normal. I tested this by discharging it by leaving the N4 in bootloader mode, and unplugged. After about 12 hours it would discharge completely. I was then able to charge it up, as per normal.
So that had me thinking it was not likely the battery at fault. What are your thoughts?
Very strange situation here. It seems somehow that booting into android causes some sort of power delivery issue and that results in the phone shutting down. I don't understand how that power delivery issue can exist within the android os but not within the bootloader if it was a hardware issue, especially after flashing the full factory image. I'm not sure, but I would still bet it a hardware issue, although perhaps not the battery.
Sent from my Nexus 4 using XDA Free mobile app
It sounds like the battery to me, running in bootloader mode requires nowhere near the current that the full OS does.
DrFredPhD said:
It sounds like the battery to me, running in bootloader mode requires nowhere near the current that the full OS does.
Click to expand...
Click to collapse
I apologise for taking so long to respond. I don't seem to be getting notifications. Will check into that.
With regard to the battery... When the phone is fully charged (and it was just like normal... prior to me toasting the OS in an attempt to refresh the device, AND it charges normally by plugging it in when turned off or in BL mode), it takes perhaps 12 hours or more to discharge, with the screen on permanently, whilst I leave it in BL mode. So if the battery is the issue, it's certainly got nothing to do with the battery being able to receive and take a charge. That happens absolutely per normal.
What I am wondering, however, if perhaps the USB board could be faulty? I actually replaced the USB board a month or two ago, as the connector on the original one died and Google refused to repair it on warranty because there was a crack on the back glass. The replacement is an LG part. I am wondering if there might be something in that logic of that board that is screwing up... such that when the cable is unplugged the device somehow "thinks" it is plugged in and thus in charge mode, rather than drawing from the battery. I am not sure where the logic for the device to determine whether to draw current from battery or USB resides. But is it feasible that this might be going on?
I'd love to revive this little brick back to smart-phone status.
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
Hi, just got my new Nexus 6P right out of the box, charged it and set it up.
I had some OTA updates waiting to be installed and 1 of them was upgrading to Nougat.
Since the update I'm having SERIOUS trouble when it comes to charging my phone.
No wall charger works, tried plugging it into the PC, charges for about 30 seconds and stops.
Tried charging via a power bank, worked for about a minute or two and I'm back to square one.
Battery continues draining in the meantime. I'm feeling pretty helpless and hope some of you have more experience to troubleshoot that issue.
Things I tried -
1. Restart
2. Clearing cache
3. Factory reset (Unfortunately, still nougat)
I did think about flashing the previous rom but I can't connect it to the PC and I'm at about 10%.
Would REALLY appreciate any help.
Thank you,
B1T3X.
Info
B1T3X said:
Hi, just got my new Nexus 6P right out of the box, charged it and set it up.
I had some OTA updates waiting to be installed and 1 of them was upgrading to Nougat.
Since the update I'm having SERIOUS trouble when it comes to charging my phone.
No wall charger works, tried plugging it into the PC, charges for about 30 seconds and stops.
Tried charging via a power bank, worked for about a minute or two and I'm back to square one.
Battery continues draining in the meantime. I'm feeling pretty helpless and hope some of you have more experience to troubleshoot that issue.
Things I tried -
1. Restart
2. Clearing cache
3. Factory reset (Unfortunately, still nougat)
I did think about flashing the previous rom but I can't connect it to the PC and I'm at about 10%.
Would REALLY appreciate any help.
Thank you,
B1T3X.
Click to expand...
Click to collapse
check if your PC recognize it when it is on fastboot mode or recovery mode
then try to flash new factory image
:good: