It's my brother's phone. out of nowhere, it started boot-looping. I tried everything I know to fix it, I was pretty sure it's a hardware issue once i saw it. It keeps trying to boot, some times it passes the google logo to the colored dots but with a very slow-motioned animation, then it boot-loops again. sometimes it boots though but once I try to put the google account and stuff it boot-loops again.
I started by clearing cache and data. I tried then installing the last factory image, when it didn't work I tried also last month's image and MM image, nothing worked. I went on and tried PureNexus, LineageOs, and a punch of kernels.
I left the phone boot-looping over night and when I woke up it was booted. The battery was 5% so I connected the charger and started putting my account and fingerprint. Suddenly it boot looped again at 12% battery. I unplugged the charger and left the phone. It kept boot-looping for a while the booted up with 10% battery. I didn't try to charge it again and everything went smoothly. I started trying the stock roms again, even the beta 7.1.2, I'm now sure that it only boot-loops above 10% battery, lower that 10% it works like a charm even with games and heat.
I know it's a long A$$ post but I'm not sorry ?. What do you guys think of that issue? anyone else had the same problem?
Hrmmm... Try disabling battery saver all together. A similar situation I had with my Pixel XL. Good luck. I miss my 6P!...:crying:
nagoo1 said:
It's my brother's phone. out if nowhere, it started bootlooping.
Click to expand...
Click to collapse
Fastboot format userdata, system and cache then install NOF27B full image using flash-all.bat.
v12xke said:
Fastboot format userdata, system and cache then install NOF27B full image using flash-all.bat.
Click to expand...
Click to collapse
Isn't NOF27B a PIXEL rom? ... If yuo mean N4F26T for nexus 6p, then I sadly tried that. I did it with twrp recovery though.
nagoo1 said:
Isn't NOF27B a PIXEL rom? ... If yuo mean N4F26T for nexus 6p, then I sadly tried that. I did it with twrp recovery though.
Click to expand...
Click to collapse
Yes, sorry N4F26T. You cannot install a full image with TWRP. You need to fastboot format your cache, userdata and system partitions (not wipe with TWRP) and then fastboot flash the full Google image (not the OTA) using flash-all. bat.
v12xke said:
Yes, sorry N4F26T. You cannot install a full image with TWRP. You need to fastboot format your cache, userdata and system partitions (not wipe with TWRP) and then fastboot flash the full Google image (not the OTA) using flash-all. bat.
Click to expand...
Click to collapse
I meant that I wiped everything with twrp then flashed factory image with Flash-all. I don't know if formatting with fastboot will make a difference but I will try it, hope it works.
Thanks man
nagoo1 said:
I meant that I wiped everything with twrp then flashed factory image with Flash-all. I don't know if formatting with fastboot will make a difference but I will try it, hope it works.
Thanks man
Click to expand...
Click to collapse
Yes, formatting is different than wipe. Note any errors during the formatting. Cap your screen if you get any. Good luck.
v12xke said:
Yes, formatting is different than wipe. Note any errors during the formatting. Cap your screen if you get any. Good luck.
Click to expand...
Click to collapse
I tried formatting, got no errors, and the same freakin boot-loop. The thing is we bought this phone from USA and the warranty expired 3 weeks ago :s .. anyways, if you have any other ideas plz suggest
Thanks
@nagoo1
Your case is different from (almost) all others. People with the BLOD have no recovery mode and you are using TWRP with no issues. A few have recovery but cannot format userdata or cache and get terminal errors attempting to format. You say the phone works normally under 10% but not above. Maybe there is something wrong with the battery? Try running an app called Accubattery. Once installed, charge the phone from below 10% until the APP tells you the phone is full. Don't go by what the phone says. Don't take it off the charger until Accubattery tells you it is full. After doing this check under the "Health" tab for the estimated battery capacity.
v12xke said:
@nagoo1
Your case is different from (almost) all others. People with the BLOD have no recovery mode and you are using TWRP with no issues. A few have recovery but cannot format userdata or cache and get terminal errors attempting to format. You say the phone works normally under 10% but not above. Maybe there is something wrong with the battery? Try running an app called Accubattery. Once installed, charge the phone from below 10% until the APP tells you the phone is full. Don't go by what the phone says. Don't take it off the charger until Accubattery tells you it is full. After doing this check under the "Health" tab for the estimated battery capacity.
Click to expand...
Click to collapse
Thanks for replying. I'd like to try your method but I don't think it's gonna work for me as the phone starts bootlooping after the 10% mark and the app wouldn't stop it from doing that. I also think that battery health is OK because if I keep charging it up to a 100% while off then try to boot it, it keeps bootlooping for about 5 hours until it reaches 10% then boots normally.
I don't know if I said this before, sometimes it boots up at a higher percentage but as soon as I start using it (open any thing or even swipe left and right), it bootloops again till it reaches 10%
I tend to believe that it's a ram issue as I've seen this before in other phones, PCs and Laptops, but what does any thing have to do with this 10% battery??????
nagoo1 said:
I don't know if I said this before, sometimes it boots up at a higher percentage but as soon as I start using it (open any thing or even swipe left and right), it bootloops again till it reaches 10%
Click to expand...
Click to collapse
Did you watch the kernel logs? dmesg and after reboot /proc/last_kmsg (which will be empty unfortunately if RAM stops being powered)
rchtk said:
Did you watch the kernel logs? dmesg and after reboot /proc/last_kmsg (which will be empty unfortunately if RAM stops being powered)
Click to expand...
Click to collapse
Never done this before, I'll look it up and try to get it. I think I saw an option in twrp to copy logs.
nagoo1 said:
It's my brother's phone. out of nowhere, it started boot-looping. I tried everything I know to fix it, I was pretty sure it's a hardware issue once i saw it. It keeps trying to boot, some times it passes the google logo to the colored dots but with a very slow-motioned animation, then it boot-loops again. sometimes it boots though but once I try to put the google account and stuff it boot-loops again.
I started by clearing cache and data. I tried then installing the last factory image, when it didn't work I tried also last month's image and MM image, nothing worked. I went on and tried PureNexus, LineageOs, and a punch of kernels.
I left the phone boot-looping over night and when I woke up it was booted. The battery was 5% so I connected the charger and started putting my account and fingerprint. Suddenly it boot looped again at 12% battery. I unplugged the charger and left the phone. It kept boot-looping for a while the booted up with 10% battery. I didn't try to charge it again and everything went smoothly. I started trying the stock roms again, even the beta 7.1.2, I'm now sure that it only boot-loops above 10% battery, lower that 10% it works like a charm even with games and heat.
I know it's a long A$$ post but I'm not sorry . What do you guys think of that issue? anyone else had the same problem?
Click to expand...
Click to collapse
happened to me just now, been bootlooping since morning, phone was being charged alternately with my wall charger and usb connected to my charger, in the middle of me trying to find a solution, so the phone was adequately charged. finally getting tired of the whole trial and error i forgot to charge and was busy restoring my old recoveries when an oct 2016 backup suddenly started booting with the running colored dots and when the security screen came in and the phone died because of low battery. I had tried the same backup before but it didnt boot. can this be true ? that the bootloops are battery related..
My bootloader shows Battery as OK and i can access TWRP recovery.
anikadam said:
happened to me just now, been bootlooping since morning, phone was being charged alternately with my wall charger and usb connected to my charger, in the middle of me trying to find a solution, so the phone was adequately charged. finally getting tired of the whole trial and error i forgot to charge and was busy restoring my old recoveries when an oct 2016 backup suddenly started booting with the running colored dots and when the security screen came in and the phone died because of low battery. I had tried the same backup before but it didnt boot. can this be true ? that the bootloops are battery related..
My bootloader shows Battery as OK and i can access TWRP recovery.
Click to expand...
Click to collapse
Seems to be the same issue. I hope we both can find a solution for this.
Here are two dmesg.log I got from TWRP, I got one below 10% and one above 10% (bootlooping). I really don't know what to do with these, so we'll need some experience here
Edit: too much characters for the post, I'll attach them instead
I hope this is actually what you guys are looking for.
View attachment 4089615
View attachment 4089616
It actually sounds like you might have a hardware issue where if the phone gets too hot from running or charging the phone bootloops. This could be because of damaged memory, a damaged CPU or damaged connections to the motherboard. The phone might work at 10% or less because the phone is running cooler when the battery is close to running out since the phone is trying to preserve what is left of the charge. I seriously doubt that there is anything you can do software wise to fix that phone. You could bring it into a repair shop. Frequently they give free estimates on a repair. Good luck.
jhs39 said:
It actually sounds like you might have a hardware issue where if the phone gets too hot from running or charging the phone bootloops. This could be because of damaged memory, a damaged CPU or damaged connections to the motherboard. The phone might work at 10% or less because the phone is running cooler when the battery is close to running out since the phone is trying to preserve what is left of the charge. I seriously doubt that there is anything you can do software wise to fix that phone. You could bring it into a repair shop. Frequently they give free estimates on a repair. Good luck.
Click to expand...
Click to collapse
Yeah I think it's a HW failure too, but what makes it work without any issues under 10%? keep in mind that sometimes I leave it bootloop for hours before it reaches 10% and boots-up, which means the device is hot. Also, if i leave it to cool down with airplane mode for a while, it keeps working. I even tried playing asphalt till the phone reached 0% and shut down. It has nothing to do with heat i think, which means its not connection issue like we used to see in graphics cards before.
I just wanna know what gets triggered under 10% that makes the phone work normally? it's not battery saving mode cause i've tried it, but I'm pretty sure something changes at exactly 10% that makes it work.
I don't have a service center that I can trust over here, I called them and they told me they will try flashing the SW (not free of-course) and that if ti's not SW then they will change the main board for almost the same price as a new phone :laugh:
I could be wrong but I think the battery saver feature basically turns off your radios and reduces brightness so you can still make calls for as long as possible. But I think even with that off your phone likely consumes less energy when the battery is down to 10% because the cpu cores will no longer operate at full strength. You might be able to use the phone somewhat if you install Francos kernel and use the most battery restraining governor settings possible to keep the phone cooler and processor use at the minemum but even if that worked you would basically be turning the 6P into the equivalent of a hundred dollar phone usability wise so it's kind of pointless. I asked a repair shop here what it would cost to replace the motherboard and they said it was essentially replacing the whole phone and wouldn't make sense cost wise. I don't think any of these 6Ps will be around in a few years. It doesn't seem like they were built to last.
I knew it wouldn't work, but I had to try
I found a thread over here that fixes bootloop for a certain situation, i knew it wouldn't work but i tried it anyways.
https://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938
Following the guide I have to Restore a backup through TWRP, It further proved that It's a HW issue when it kept freezing and rebooting when trying to restore. I left the battery drain till it reached 10% then tried to restore again and it worked and booted up, but again when I tried to charge beyond 10% it bootlooped :crying:
jhs39 said:
I could be wrong but I think the battery saver feature basically turns off your radios and reduces brightness so you can still make calls for as long as possible. But I think even with that off your phone likely consumes less energy when the battery is down to 10% because the cpu cores will no longer operate at full strength. You might be able to use the phone somewhat if you install Francos kernel and use the most battery restraining governor settings possible to keep the phone cooler and processor use at the minemum but even if that worked you would basically be turning the 6P into the equivalent of a hundred dollar phone usability wise so it's kind of pointless. I asked a repair shop here what it would cost to replace the motherboard and they said it was essentially replacing the whole phone and wouldn't make sense cost wise. I don't think any of these 6Ps will be around in a few years. It doesn't seem like they were built to last.
Click to expand...
Click to collapse
Nice Idea, but I don't know which kernel manager to use with franco & what settings would be best for limiting cpu. if there's a topic about that please point it to me or give me ur thoughts
Related
One day i was found that my magic isn't charged fully - charging level is stuck at same % (say 66%) although charger was plugged in during all the night.
Beginning from this moment the phone doesn't detect battery level correctly and don't charging up to 100% nor when it is on nor when it is off. For example it can show me one value but after reboot shows differently another value (for example was 46% but after rebooting is 8%, or in some cases battery level can be even more, than before i performing reboot - say was 22% but after rebooting is 78%).
I'd tried wipe, erase system partition and re-flash rom, flash another roms - all without any luck. So i decided that my battery is died. But when i got a brand new battery (from another just bought magic), i got the same issue as in case of my battery. Also another magic works perfect with my battery.
It appears that problem in the phone itself? Anybody got the same issue?
intruders said:
One day i was found that my magic isn't charged fully - charging level is stuck at same % (say 66%) although charger was plugged in during all the night.
Beginning from this moment the phone doesn't detect battery level correctly and don't charging up to 100% nor when it is on nor when it is off. For example it can show me one value but after reboot shows differently another value (for example was 46% but after rebooting is 8%, or in some cases battery level can be even more, than before i performing reboot - say was 22% but after rebooting is 78%).
I'd tried wipe, erase system partition and re-flash rom, flash another roms - all without any luck. So i decided that my battery is died. But when i got a brand new battery (from another just bought magic), i got the same issue as in case of my battery. Also another magic works perfect with my battery.
It appears that problem in the phone itself? Anybody got the same issue?
Click to expand...
Click to collapse
Me too....
did you try wiping battery stats (from recovery)?
I'm not sure if this is supposed to done from a full or empty battery though
adavis159 said:
did you try wiping battery stats (from recovery)?
I'm not sure if this is supposed to done from a full or empty battery though
Click to expand...
Click to collapse
That is what i waa going to say, but I'm sure it doesnt matter what level your battery is when you do this aslong as it doesnt die during the process. Anyways you could have a faulty phone reading the levels wrong if changing roms and doing this doesnt work.
luminiz said:
Me too....
Click to expand...
Click to collapse
I found several similar cases on this forum but no one answer that actually explain what and why it happens.
In my case i got this issue after performing battery calibration procedure. Maybe is just coincidence, i don't know.
adavis159 said:
did you try wiping battery stats (from recovery)?
Click to expand...
Click to collapse
Yep, of course i tried do this from recovery and manually deleting battery stats file - both with no luck. Also during rom flashing battery stats also was erased.
Tried un-root my phone by flashing Android 1.5 from MT3G - issue isn't disappear. After a week maximum detected battery level is falling down and i can't get even 40% of charge. Now, two weeks later, maximum charging level is only few %. Damn it
i keep trying every rom available for my phone
and in every rom is the same the 100% battery last for like 3 hours then after that the battery drops like every minute even when screen is off?
how can i make battery life last longer?
thanks in advance
Lucky for you I still had copy of it in message box as I got 5-6 requests few hours ago regarding that.
BlackSHELF said:
Well the borderline idea is the same as you already know you have to completely drain it. Now never use any volt meter those people use to completely discharge it as the negative effect I already explained to you in that post. So best way is to do it by recalibrating so what you do is:
1) Fully charge it.
2) Drain it till you get 1%.
3) Go in recovery and wipe battery, reboot (batterystats.bin created).
4) As you still have battery low now let it charge till 100%.
5) Do the cycle again.
NOTE: This is what I would recommend but as we know the whole issue with CWM restarting while phone is off as you can flash the stock recovery and go back as it takes 3sec. If not follow the above.
1) Heavily use your phone so it drain the battery till its 1%
As you will see the low battery light flashing just so you don't lose your data save it by rebooting.
2) As you still have some battery power left you can now go to Recovery and wipe battery stats.
Or you can manually do it from adb shell by using remove command "rm /data/system/batterystats.bin".
3) Keep it on till its turns itself off.
As you may have guessed it still has power left so keep using the device till its drained completely I would recommend rebooting and going in bootloader as it uses more power due to bight screen as Recovery uses less power on display.
4) Now turn it back on again in bootloader till it turns off again.
It will keep turning itself of as no power left, this is what you want. This is safe way to discharge it without having negative adverse effect.
5) Now let it charge via A/C instead of USB.
Now when the light turns green unplug it and replug it till its green again, keep doing that till you see its green only. Now once you reboot in Android it will rebuild the batterystats.bin and you will be fully recalibrated.
Click to expand...
Click to collapse
if i cant go back to stock recovery which procedure do i try the 1st procedure or the 2nd one?
nulights said:
if i cant go back to stock recovery which procedure do i try the 1st procedure or the 2nd one?
Click to expand...
Click to collapse
First one is better for you. Do the cycle fully twice and you will be good to go and it will solve those most common issue like getting green light while its still not 100% or sticking it at 100% for long time and then dropping faster than you can count lol I just did it few hours ago, normally I do it once every 2weeks.
Alright thanks,
Ill try this out
BlackSHELF said:
Lucky for you I still had copy of it in message box as I got 5-6 requests few hours ago regarding that.
Click to expand...
Click to collapse
I don't see a way to wipe battery stats in stock recovery. Doesn't that mean I have to wipe stats, reboot phone, switch to stock recovery then bootloader drain the phone? Will that reboot adversely effect the rebuilding of the bin file? Can I just delete the batterystats.bin file with root explorer before I power down the phone to start the bootloader drain process?
Edit: I'm at 3%, #push knowledge darinmc GOGOGOGOGOGOGOGOGOGOGO
darinmc said:
I don't see a way to wipe battery stats in stock recovery. Doesn't that mean I have to wipe stats, reboot phone, switch to stock recovery then bootloader drain the phone? Will that reboot adversely effect the rebuilding of the bin file? Can I just delete the batterystats.bin file with root explorer before I power down the phone to start the bootloader drain process?
Edit: I'm at 3%, #push knowledge darinmc GOGOGOGOGOGOGOGOGOGOGO
Click to expand...
Click to collapse
Sorry was asleep but yeah you can manually do it from terminal (su), adb (shell), root exp (enable r/w). Then power down as you saying you reverted back to stock recovery I am guessing you are on 3.0.0.6 supporting the 2.5.1.4 stock. So in that case just reboot and follow the same meth. This would clear out those lag (sticking at 100% for long time and then dropping faster than you can count) and wrong data (exp: 80% after rebooted 83%). I just recalibrated it yesterday which is the reason I spoke about it which caused this whole massive PM attacks and threads like this. Which is fine just do it once every 2weeks or once a month as doing it every week is not particle even for me.
BlackSHELF said:
Sorry was asleep but yeah you can manually do it from terminal (su), adb (shell), root exp (enable r/w). Then power down as you saying you reverted back to stock recovery I am guessing you are on 3.0.0.6 supporting the 2.5.1.4 stock. So in that case just reboot and follow the same meth. This would clear out those lag (sticking at 100% for long time and then dropping faster than you can count) and wrong data (exp: 80% after rebooted 83%). I just recalibrated it yesterday which is the reason I spoke about it which caused this whole massive PM attacks and threads like this. Which is fine just do it once every 2weeks or once a month as doing it every week is not particle even for me.
Click to expand...
Click to collapse
Thanks! Needed to do this for a while.
BlackSHELF said:
Lucky for you I still had copy of it in message box as I got 5-6 requests few hours ago regarding that.
Click to expand...
Click to collapse
thanks for that. I have been searching for that kinda guide on here for awhile! It was like looking for a needle in a haystack there are ten million about it, But none this detailed infomation!
SetCPU can help with your battery life. It did wonders on my HD2 running android.
Some suggestions in this thread: **HOW TO MAKE YOUR BATTERY LIFE LAST** Members Tips & Tricks
can someone clarify the steps "Go into recovery and wipe battery"?
I am running stock rom.
I am able to go into the bootloader menu. But when I select recovery, all i get is an icon with a picture of a phone and a triangle w/ an exclamation point at the corner. I don't know to leave this screen other than battery pull.
Where do I delete batterystats.bin?
Wiping battery stats help
I tried to wipe battery stats after my battery was drained to 1%, but nothing happened. I didnt see any scripts run that confirmed battery stats command had gone through. Was that supposed to happen? I'm really confused by this because I saw that my battery was drained to 1% but when I rebooted to recharge the phone, it showed that I was not fully drained. It read that I was at 20% and charging!? Please help guys. Thanks in advance
longhornguy said:
I tried to wipe battery stats after my battery was drained to 1%, but nothing happened. I didnt see any scripts run that confirmed battery stats command had gone through. Was that supposed to happen? I'm really confused by this because I saw that my battery was drained to 1% but when I rebooted to recharge the phone, it showed that I was not fully drained. It read that I was at 20% and charging!? Please help guys. Thanks in advance
Click to expand...
Click to collapse
Download and use "battery calibration" app from the market. Its pretty easy to understand and follow.
Sent from my HTC Glacier
Thanks man, i greatly appreciate it. I'll download and see what happens
Hi all;
so over the last few months i have flashed many custom roms, kernels etc...and always had battery issues...i have tried jugs battery fix, wiping battery stats..following many other battery optimization threads..but i never got the battery life i once had (when i first bought my phone)...
a few days ago my phone totally crashed..wouldnt charge etc..and i ended up having to do a complete restore..i did this by following these instructions
http://www.youtube.com/watch?v=hRFJJFW-XxI
....so from there, i unlocked again, reloaded CWM etc and i loaded 2.3.4 flashable zip (found in the forums) via CWM.
and voila..battery life AMAZING....after 8hours im usually still at 85%...by evening time after using the phone all day im still at about 60%
from here do what you want with roms..
i loaded the alien rom without adding the themes..and the battery life is as stated above..
so if you are having issues try hard resetting the phone then re unlocking the BL and upgrading via cwm to 2.3.4
my battery life i back to amazing.....
p.s. would be great if someone else who is having issues tried this and reported back as well...
p.s. this worked for me but i am not responsible if you mess up your phone!
Erm..
Ok Ill bite >,>
Where are these camera buttons your referring to in this guide of yours Atrix has three hard buttons and four soft buttons power, vol- and vol+ and menu home back and search.... you hard mod a camera button into this already packed phone Ill like to hear it XP
Interesting..
Couple of q's:
- which camera button?
- unlock bootloader again? Once unlocked it stays unlocked.
- I don't understand how doing a reset leads you to unlocking the bootloader again?
Sent from my Motorola Olympus using XDA Premium App.
updated the hard reset instructions to reference a youtube video (not mine but describes how to do it)
http://www.youtube.com/watch?v=hRFJJFW-XxI
it doesn't actually re-lock the bootloader. The BootLogo is replaced with the stock logo, which does NOT include the "UNLOCKED" in the upper left hand corner
sorry i didnt realize that..so skip this step for anyone that is going to try it...
jakew02 said:
it doesn't actually re-lock the bootloader. The BootLogo is replaced with the stock logo, which does NOT include the "UNLOCKED" in the upper left hand corner
Click to expand...
Click to collapse
well dont have the old recovery and even if i did cant read the things at all quality is very bad
me too really can't understand it properly, i need to get back that battery time, but How? can anyone else explain it Please?
Anyone except TC try this with sucess? I have Alien 4 with stock kernel and i am getting about 15 to 20 hours before death.
I could be wrong, but I'm fairly confident that the following information is correct:
Doing a factory reset on the stock android recovery simply wipes data, cache, and dalvik - all of which can be done with any of the after market recoveries.
I am unsure as to whether or not factory reset also wipes the battery stats in the stock android recovery.
Edit: It is highly recommended to wipe the battery stats after you install a new ROM or kernel. To do so the quick and easy way - charge the phone to 100%, reboot to recovery, clear battery, reboot. If is then recommended that you let the phone die (or at least get low) followed by a full charge 2-3 times to make the battery accurate. The most involved way to reset the battery stats is to charge to full with the phone off. When it says 100%, pull the battery, plug it back in, let it charge for an additional hour or two while still off like this. It will likely not show 100% after an hour or two, that's fine. Boot into recovery, wipe stats, start up the phone, then unplug it. Follow this will drains and full charges 2-3 times and you will be set. This helps to fix poor battery life when it is caused by a battery that will not fully charge.
OP you should try to drain the battery down to nothing. A lot of people who screw up their battery stats end up with bad battery, however at times you can get a very slow draining batter that will give you 20 hours with 60% left, and then when the phone hits 53% (random example), the battery will fall from there to dead in just a few minutes. This happened to me when I first flashed Ninja SF. I was amazed the battery until I decided to let the phone actually die.
DK
Well im on Cm7 so far only 48% left after 18 hours of moderate use
Sent from my MB860 using xda premium
hi i did try what you said below and it didnt give me the same results...
DeathKoil said:
I could be wrong, but I'm fairly confident that the following information is correct:
Doing a factory reset on the stock android recovery simply wipes data, cache, and dalvik - all of which can be done with any of the after market recoveries.
I am unsure as to whether or not factory reset also wipes the battery stats in the stock android recovery.
Edit: It is highly recommended to wipe the battery stats after you install a new ROM or kernel. To do so the quick and easy way - charge the phone to 100%, reboot to recovery, clear battery, reboot. If is then recommended that you let the phone die (or at least get low) followed by a full charge 2-3 times to make the battery accurate. The most involved way to reset the battery stats is to charge to full with the phone off. When it says 100%, pull the battery, plug it back in, let it charge for an additional hour or two while still off like this. It will likely not show 100% after an hour or two, that's fine. Boot into recovery, wipe stats, start up the phone, then unplug it. Follow this will drains and full charges 2-3 times and you will be set. This helps to fix poor battery life when it is caused by a battery that will not fully charge.
OP you should try to drain the battery down to nothing. A lot of people who screw up their battery stats end up with bad battery, however at times you can get a very slow draining batter that will give you 20 hours with 60% left, and then when the phone hits 53% (random example), the battery will fall from there to dead in just a few minutes. This happened to me when I first flashed Ninja SF. I was amazed the battery until I decided to let the phone actually die.
DK
Click to expand...
Click to collapse
My Nook Color with internal CM 7.1 shuts off if not plugged in. I had CM 7.1 on my Nook Color for months with out any issues then about 2 weeks ago it started to completely shut off if not plugged in. I didn't install any apps or it wasn't changed in anyway, it would just began to shut off. I then decided to install CM 7.2 to resolve the issue but it does the exact same thing. I have no idea was is going on.
cnnsucks said:
My Nook Color with internal CM 7.1 shuts off if not plugged in. I had CM 7.1 on my Nook Color for months with out any issues then about 2 weeks ago it started to completely shut off if not plugged in. I didn't install any apps or it wasn't changed in anyway, it would just began to shut off. I then decided to install CM 7.2 to resolve the issue but it does the exact same thing. I have no idea was is going on.
Click to expand...
Click to collapse
Sounds like battery issues. By shut off, do you mean just goes dead instantly as soon as you unplug it? Or some other thing?
leapinlar said:
Sounds like battery issues. By shut off, do you mean just goes dead instantly as soon as you unplug it? Or some other thing?
Click to expand...
Click to collapse
Yes, it goes dead.
What does your battery show? Percentagewise, that is. Try booting to CWM and doing a wipe battery stats.
It goes dead instantly and the battery status is 100%.
I wiped the battery stats and it still shuts off.
I'm having this exact same issue. I checked using one of those battery calibration tools from the app store, and my battery is reading 4207mv. Not sure what is going on but I don't really want to have to replace the battery on this thing already. Anyone have a way to actually discharge the battery while it's out of the nook and see if it can get re-calibrated that way?
Try backing up your system and then reinstalling stock. It has a small zip file (charging.zip) that goes on the boot partition and gets activated by the system when the system thinks it needs it. I don't know if it has anything to do with problems you guys are having, but we are grasping at straws here. I have a version of stock that has been modified to be flashable with CWM. Get it here.
http://d01.megashares.com/index.php?d01=CiYdDmP
leapinlar said:
Try backing up your system and then reinstalling stock. It has a small zip file (charging.zip) that goes on the boot partition and gets activated by the system when the system thinks it needs it. I don't know if it has anything to do with problems you guys are having, but we are grasping at straws here. I have a version of stock that has been modified to be flashable with CWM. Get it here.
http://d01.megashares.com/index.php?d01=CiYdDmP
Click to expand...
Click to collapse
Cool, I'm downloading it now. I don't mind wiping this device since it's just a test device, is there any reason to backup /system other than to save my current rom? Also, if I flash that modded stock, does it already have root and will it affect my recovery or will I still be able to boot to twrp?
Thanks
catawalks said:
Cool, I'm downloading it now. I don't mind wiping this device since it's just a test device, is there any reason to backup /system other than to save my current rom? Also, if I flash that modded stock, does it already have root and will it affect my recovery or will I still be able to boot to twrp?
Thanks
Click to expand...
Click to collapse
The backup is just so you have yourself one. If you don't need it don't do it. It is vanilla stock, not rooted. And your TWRP will be gone. Stock recovery will be there. That is part of my reason for suggesting it. This just a test to see if the stock system fixes your problem.So maybe a nandroid backup is good so that you can just restore the nandroid and everything is as you had it, TWRP and all.
leapinlar said:
The backup is just so you have yourself one. If you don't need it don't do it. It is vanilla stock, not rooted. And your TWRP will be gone. Stock recovery will be there. That is part of my reason for suggesting it. This just a test to see if the stock system fixes your problem.So maybe a nandroid backup is good so that you can just restore the nandroid and everything is as you had it, TWRP and all.
Click to expand...
Click to collapse
Sounds like a plan. I'll give it a shot in the AM when I get a chance to put it back together. Since it was acting up I decided it would be a good idea to do a little teardown of it and see what was inside.
Thanks
leapinlar said:
Try backing up your system and then reinstalling stock. It has a small zip file (charging.zip) that goes on the boot partition and gets activated by the system when the system thinks it needs it. I don't know if it has anything to do with problems you guys are having, but we are grasping at straws here. I have a version of stock that has been modified to be flashable with CWM. Get it here.
Click to expand...
Click to collapse
I tried reinstalling stock like you said and it does the exact same thing. shoot. thanks for the help.
cnnsucks said:
I tried reinstalling stock like you said and it does the exact same thing. shoot. thanks for the help.
Click to expand...
Click to collapse
Well, at least you have stock on it if you want to take it to B&N for them to look at. If still under warranty, maybe they will do something.
I tried reinstalling stock as well, it boots normally with it plugged in and still dies when unplugged but I'm gonna try to recondition the battery. With a little luck I might be able to get it back to working. I found some useful info for people about batteries that would be good to know for your nook. I didn't know these things before hand that that's probably why my nook's battery is dead.
Taken from here:
3: Allow partial discharges and avoid full ones (usually)
Unlike NiCad batteries, lithium-ion batteries do not have a charge memory. That means deep-discharge cycles are not required. In fact, it’s better for the battery to use partial-discharge cycles.
There is one exception. Battery experts suggest that after 30 charges, you should allow lithium-ion batteries to almost completely discharge. Continuous partial discharges create a condition called digital memory, decreasing the accuracy of the device’s power gauge. So let the battery discharge to the cut-off point and then recharge. The power gauge will be recalibrated.
4: Avoid completely discharging lithium-ion batteries
If a lithium-ion battery is discharged below 2.5 volts per cell, a safety circuit built into the battery opens and the battery appears to be dead. The original charger will be of no use. Only battery analyzers with the boost function have a chance of recharging the battery.
Also, for safety reasons, do not recharge deeply discharged lithium-ion batteries if they have been stored in that condition for several months.
5: For extended storage, discharge a lithium-ion battery to about 40 percent and store it in a cool place
I’ve always had an extra battery for my notebook, but it would never last as long as the original battery. I know now that it’s because I was storing the battery fully charged. That means oxidation of lithium-ion is at its highest rate. Storing lithium-ion batteries at 40 percent discharge and in the refrigerator (not freezer) is recommended
Click to expand...
Click to collapse
I've let this one sit for months on end being dead, then I would fully charge it and use if for a day or two trying some stuff out for work, then let it sit and slowly discharge and be dead for weeks if not months again. Probably not a good idea.
catawalks said:
Taken from here:
Click to expand...
Click to collapse
Thanks catawalks for that very informative link. I am going to add that link to my tips thread for other users to read.
You might want to install an app called Battery Monitor Widget Pro by 3C. I think they have a free version on play store. It gives you useful info about you battery's condition and charging history.
Keep us posted about your success or failure about reconditioning your battery.
leapinlar said:
Thanks catawalks for that very informative link. I am going to add that link to my tips thread for other users to read.
You might want to install an app called Battery Monitor Widget Pro by 3C. I think they have a free version on play store. It gives you useful info about you battery's condition and charging history.
Keep us posted about your success or failure about reconditioning your battery.
Click to expand...
Click to collapse
Feel free to use it. All is good. I'll give that app a try too and will definitely keep updating with status on the battery.
Couldn't find this exact shut down thing and none of the recent spate of 0% all of a sudden threads covers the 97% battery shutdown aspect to this. I ramble a bit, bare with me.
Had the nexus 10 from new (fk knows how long - 6+ years?)
Replaced the battery from a reputable supplier maybe 9months ago.
All has been good.
I installed lineage 14 and life was better.
Its essentially a youtube,iplayer, email terminal now.
Past few nights it just started shutting down. (fully charged)
Sometimes when switching Youtube videos, sometimes just skipping forward.
It worked for a bit whilst plugged in but even that isn't happening any more.
Its behaving like the battery is empty but when plugged in the battery indicator says full.
I have just tried to reflash. Got new lineage on it through twrp.
Boots to recovery and then I'm just trying to put gappsPICO on and it shuts down again, and thats whilst its plugged in!
Wont boot through to lineage setup even (i know it would fail/dead screen without gapps but I thought I'd try)
*Live update*
I deleted the battery stats file and it was still showing full charge but whilst typing its changed its mind and is accepting a charge!
Hope it was just the battery stats file (means I've just scrubbed it for no good reason other than that new lineage is better lineage right?)
Assuming the battery doesn't over charge and blow up and that the shutdown behaviour continues - this smells like a hardware fault right? A.k.A R.I.P Manta?
Wow, rambling. Sorry
Charged overnight. Reflashed and even got gappsPICO on as well.
Started to setup firstboot and the issue came back.
Thermally related hardware fault is my guess.
What's the current options for a similar product? High Res screen, doesn't need to game, nougat or later OS.
I thought there would be a cheap option but all I can find are things like the Samsung galaxy Tab 2. 300quid...
What say you?
Maybe helps.
olly230 said:
Couldn't find this exact shut down thing and none of the recent spate of 0% all of a sudden threads covers the 97% battery shutdown aspect to this. I ramble a bit, bare with me.
Had the nexus 10 from new (fk knows how long - 6+ years?)
Replaced the battery from a reputable supplier maybe 9months ago.
All has been good.
I installed lineage 14 and life was better.
Its essentially a youtube,iplayer, email terminal now.
Past few nights it just started shutting down. (fully charged)
Sometimes when switching Youtube videos, sometimes just skipping forward.
It worked for a bit whilst plugged in but even that isn't happening any more.
Its behaving like the battery is empty but when plugged in the battery indicator says full.
I have just tried to reflash. Got new lineage on it through twrp.
Boots to recovery and then I'm just trying to put gappsPICO on and it shuts down again, and thats whilst its plugged in!
Wont boot through to lineage setup even (i know it would fail/dead screen without gapps but I thought I'd try)
*Live update*
I deleted the battery stats file and it was still showing full charge but whilst typing its changed its mind and is accepting a charge!
Hope it was just the battery stats file (means I've just scrubbed it for no good reason other than that new lineage is better lineage right?)
Assuming the battery doesn't over charge and blow up and that the shutdown behaviour continues - this smells like a hardware fault right? A.k.A R.I.P Manta?
Wow, rambling. Sorry
Click to expand...
Click to collapse
--- Hi i used/tried 4 new batteries until i gave up hope. One day i started to feel that i have to get my nexus 10 working so i started testing different stuff. My fix was, dont use any rom/kernel that is 3.4.67. Use 3.4.113 using roms or install that kernel. I hope this helps and please tell me if it helps
Do I need to kind a rom based on it or can I just flash a new one?
olly230 said:
Do I need to kind a rom based on it or can I just flash a new one?
Click to expand...
Click to collapse
Hi, try rhis 5.8.5 resurection remix for nexus 10
Fingers crossed
Nah its terminal.
Screen now flickers whilst in recovery.
3 finger salute works
I can flash in new recovery ok.
I can navigate recovery menus fine, change interface settings but the miute I ask it to actually do anything, wipe, set for sideload or flash zip already on the device it flickers then dies.
Poor thing
Who'd have thunk it. Replacement battery died after 9 months.
Put the old one in ( cracking it open being the last resort)
Back in business.
Lineage 15.1 and oreo.
Boom, back in the game.