Poco Pixel 11 Plus Rom Loop Wont switch on - Xiaomi Poco F1 Questions & Answers

Greetings,
I have been using my poco f1 for 4 years now and it has stood by me strongly. I only replaced the battery once due to excessive usage from covid (hotspot on almost 12+ hrs of the day).
It had pixel plus 11 rom in it and I was very happy with it too. Over the past 1 week, i noticed it was behaving strangely.
1. The charge time took almost 3hrs even though it showed charing rapidly
2. When I switch off the phone and keep it for the charge, it charges comparatively faster.
3. At certain times, it would freeze and restart.
4. Would heat up during charging, so I would keep it near a window or anywhere there is a breeze so that it doesn't overheat.
As of yesterday, the phone went into a complete loop after charging (It was off while being charged, once it reached 95% I unplugged and switched it on) with poco symbol followed by the 'G' icon appearing.
I thought i'd wait it out, but no luck. The weirdest thing was, when i reconnected my charger (Charge ON), it would switch on. And when i'd unplug it, the phone would switch off and go back into the loop.
The phone was near full charged, but i figured this is probably a rom issue and needs a good flash. So, I plugged the phone in for charging again so that I could switch it on and then took the necessary backups.
In parallel, I downloaded the latest rom (Pixel 12 stable build) thinking that if i flashed it would solve everything.
I connected the phone via USB to the laptop to copy the rom file, but it didn't swith on. It would only do so by charger. (Weird!). I tried it a couple of times, and managed to switch the phone via USB cable connected from laptop. But it didnt last for long as the phone would switch off shortly. Fortunately, it was on for just enough time and i mean, a couple of times till I could copy the file into storage for flashing.
I reconnected it back to the wall charger, switched on and took backups. At this point the phone has reached 100% for about 2hrs or so, but there's nothing i can do in order to get it to be on.
I proceeded to flash pixel rom 12 via twrp after clearing the cache, davlik and all of that. It was successful (no error messages appeared) and when i rebooted it I could see that the rom went through fine as the charging '100%' icon has changed (Its more graphic) but the phone still wont switch on and continues to be on this loop.
Can anyone please advise me on how I can tackle this? I dont want to buy a new phone as I feel there is nothing out there that would match this phone for its value. (I can use pixel rom, good battery, durability)
Any help in this matter would be highly appreciated.
I'd be more than happy to make a contribution to anyone who can provide me with a solution that works. I'd rather be happy with my old phone and you can treat yourself to a nice meal rather than having to buy a brand new phone. (So far, im looking at mi 11x, s20 fe, mi 11 lite, oneplus 9R, but to be honest they just don't appeal to me. You know what they say, once you go poco, you go loco!!!!)
Thankyou
Be safe

AshPocoPixel said:
Greetings,
I have been using my poco f1 for 4 years now and it has stood by me strongly. I only replaced the battery once due to excessive usage from covid (hotspot on almost 12+ hrs of the day).
It had pixel plus 11 rom in it and I was very happy with it too. Over the past 1 week, i noticed it was behaving strangely.
1. The charge time took almost 3hrs even though it showed charing rapidly
2. When I switch off the phone and keep it for the charge, it charges comparatively faster.
3. At certain times, it would freeze and restart.
4. Would heat up during charging, so I would keep it near a window or anywhere there is a breeze so that it doesn't overheat.
As of yesterday, the phone went into a complete loop after charging (It was off while being charged, once it reached 95% I unplugged and switched it on) with poco symbol followed by the 'G' icon appearing.
I thought i'd wait it out, but no luck. The weirdest thing was, when i reconnected my charger (Charge ON), it would switch on. And when i'd unplug it, the phone would switch off and go back into the loop.
The phone was near full charged, but i figured this is probably a rom issue and needs a good flash. So, I plugged the phone in for charging again so that I could switch it on and then took the necessary backups.
In parallel, I downloaded the latest rom (Pixel 12 stable build) thinking that if i flashed it would solve everything.
I connected the phone via USB to the laptop to copy the rom file, but it didn't swith on. It would only do so by charger. (Weird!). I tried it a couple of times, and managed to switch the phone via USB cable connected from laptop. But it didnt last for long as the phone would switch off shortly. Fortunately, it was on for just enough time and i mean, a couple of times till I could copy the file into storage for flashing.
I reconnected it back to the wall charger, switched on and took backups. At this point the phone has reached 100% for about 2hrs or so, but there's nothing i can do in order to get it to be on.
I proceeded to flash pixel rom 12 via twrp after clearing the cache, davlik and all of that. It was successful (no error messages appeared) and when i rebooted it I could see that the rom went through fine as the charging '100%' icon has changed (Its more graphic) but the phone still wont switch on and continues to be on this loop.
Can anyone please advise me on how I can tackle this? I dont want to buy a new phone as I feel there is nothing out there that would match this phone for its value. (I can use pixel rom, good battery, durability)
Any help in this matter would be highly appreciated.
I'd be more than happy to make a contribution to anyone who can provide me with a solution that works. I'd rather be happy with my old phone and you can treat yourself to a nice meal rather than having to buy a brand new phone. (So far, im looking at mi 11x, s20 fe, mi 11 lite, oneplus 9R, but to be honest they just don't appeal to me. You know what they say, once you go poco, you go loco!!!!)
Thankyou
Be safe
Click to expand...
Click to collapse
Firstly make sure you followed this installation guide.
Then if you are sure that flashing is correct, I think it's your battery issue. You should replace it.

Retrial said:
Firstly make sure you followed this installation guide.
Then if you are sure that flashing is correct, I think it's your battery issue. You should replace it.
Click to expand...
Click to collapse
Hi there!
Thanks for replying!
I tried the same out all day yesterday and had no luck.
I have given it to a mobile repair shop nearby (we have a separate market for mobiles here).
Hopefully they can sort it out or else I'll go for a used S20 FE 5G, saw a couple of them ranging from $300 - $400

AshPocoPixel said:
Hi there!
Thanks for replying!
I tried the same out all day yesterday and had no luck.
I have given it to a mobile repair shop nearby (we have a separate market for mobiles here).
Hopefully they can sort it out or else I'll go for a used S20 FE 5G, saw a couple of them ranging from $300 - $400
Click to expand...
Click to collapse
You could just buy and replace the battery by urself with 5min YouTube video
In repair shop they may ask extra money or try to show u that needs more than battery.
I am sure it's battery tho.

Retrial said:
You could just buy and replace the battery by urself with 5min YouTube video
In repair shop they may ask extra money or try to show u that needs more than battery.
I am sure it's battery tho.
Click to expand...
Click to collapse
Hi there!
Thanks for replying. So, my phone did get fixed, apparently, the issue was due to the charger port and battery connection. Somewhere there was a short circuit causing that issue.
They mentioned this happens due to overcharging or using the phone when on charge or running heavy applications.
Yes, a battery replacement would add a few more hours of battery life I'm sure as I currently average 6 hours on heavy usage.
I plan to use this phone till it no longer runs as the alternatives out there arent really all that great with respect to value for money and reliability. I hope to get my hands on the mi 12x, it looks really appealing!

AshPocoPixel said:
Hi there!
Thanks for replying. So, my phone did get fixed, apparently, the issue was due to the charger port and battery connection. Somewhere there was a short circuit causing that issue.
They mentioned this happens due to overcharging or using the phone when on charge or running heavy applications.
Yes, a battery replacement would add a few more hours of battery life I'm sure as I currently average 6 hours on heavy usage.
I plan to use this phone till it no longer runs as the alternatives out there arent really all that great with respect to value for money and reliability. I hope to get my hands on the mi 12x, it looks really appealing!
Click to expand...
Click to collapse
I am glad you found the problem and you got it fixed
For sure hardware of POCO F1 is still good and worth the money. Enjoy the paradise of custom ROMs

Related

Battery will not charge due to high/low temperature (not a battery defect)

Hey there,
I have my Vibrant for a good year now since it came out pretty much. Last week it just stopped charging out the blue. The battery is completely empty and shows a thermometer with a warning sign and stops charging seconds after its plugged in. So I assumed it might be a battery malfunction and I got my spare battery in as soon as I came home and tried charging - same problem. I think it is highly unlikely that both batteries fail at the same time. Therefore, I assume there is something wrong with the temp sensor in the phone. I saw a few people have a similar problem with the epic 4G, but the discussion got really side tracked by other issues. My phone is rooted, but I was running stock froyo, so that shouldn't be the problem or should it?
I just wanna know if anybody had the same problems and if there is a quick solution, I google and forum searched a while but as soon as you throw in the term battery it gets spammed with battery life discussions.I just checked my files I have on the phone, apparently I have the premium insurance - does that mean I just can go to the next Tmo store and get a replacement? Any feedback is greatly appreciated.
Phill
Well for your problem, i suggest you try a different rom and see if the problem persists... maybe its a bug
And as for insurance, you mail the phone in and pay a deductible, which should be like 135$ or so. They send you a refurb.. or if you say it wus lost, you dont have to mail in phone
Sent from a cell tower to the XDA server to you.
thanks for the quick reply. Is there a way to reflash without a battery?
I don't see it as a bad thing. If your phone gets too hot and keeps charging that's going to burn something inside. When my phone won't charge I know I have let it down. So it can cool down. But to fix your problem reboot the phone. You can keep charging it after it boots up
Sent from my SGH-T959 using Tapatalk
pro1st said:
thanks for the quick reply. Is there a way to reflash without a battery?
Click to expand...
Click to collapse
As long as your phone can run successfully for a couple minutes, i dont see why not
Sent from a cell tower to the XDA server to you.
Mine did something similar. I picked it up after putting it on the charger. It was hot and would not come on. I unplugged it and let it cool off for a while and it cleared up.
I got that message once...
Vibrant was in a car dock, with power.
It was *HOT* out and sun was hitting the back of the unit. (A/C on of course)
Google Navigation was running (display brightness max)
Google Listen was running
Bluetooth was passing music to a speakerphone
When I run the phone with that setup, the charger can't even keep up with the phone power needs. The battery level slowly drops. No question the phone is working hard.
This was a true heat issue... I removed the charger and turned off the display to let it cool off a bit. (I was almost home).
So the question again, is your phone hot or is it a false reading?
Robert
Hey,
I am sorry I didn't clarify the actual battery temp. It is normal - so its neither in the sun or in a too cold spot when I try charging it. The phone probably runs for one for a few seconds before turning off so there is no chance of the battery stats wipe. I think I will try to find an external charger and try to charge the batteries this way to have enough juice for flashing a new rom. Thanks for all the replies!
Does it charge the battery with the phone off? If not, I don't think a new ROM will help.
Hey there! Wondering if you got around to solving this. I've got a Vibrant doing the same exact thing. Battery being cool it sais that is overheating. Did changing the ROM solved it or not?
c0olcast said:
Hey there! Wondering if you got around to solving this. I've got a Vibrant doing the same exact thing. Battery being cool it sais that is overheating. Did changing the ROM solved it or not?
Click to expand...
Click to collapse
Sorry for resurrecting an old thread, but a resolution never seemed to be made here. Has anybody found a fix to this?
As of yesterday, my wife is having the same issue with my old Vibrant phone which she now uses. It's flashed with Bionix V 1.3.1 and Tigerblood overclock to 1.2ghz. This could be the issue, the Tiger Blood overclock, but I'm not sure. I'm out of the country for three weeks and currently she's left with a dud of a phone that keeps giving her the temperature warning in the triangle when plugged in while the phone is powered off followed by it stop charging. When she turns it on, she gets to the SD card check and then the phone completely freezes. Once in a while it's able to stay on for a minute or so before freezing, but more often than not the phone does not fully turn on and just goes frozen after a few seconds, sometimes at the Tigerblood logon screen before making it to the desktop. Me being 4000 miles away doesn't make it easier to help her but I've recommended she leave the phone unplugged, battery out for the night to see what happens. I also told her to take off her silicon case thinking maybe that has something to do with the overheating. Well after 7 hours of her letting it sit to cool off like that, with the case off, she plugged it back in and is having the same issues as yesterday. Absolutely no progress made. One of her colleagues said she should try leaving the phone in rice confused:) so she's giving that a go and another guy in a phone shop who she went to for advice after work said that the motherboard might need replacing. I'm convinced all it needs is to have the Tigerblood removed or reflash a rom onto it but there's really no knowing unless I have it in my hand.
Is there any quick fix to this problem without having to do all that? Surely there must be a way to charge the phone without it heating up and freezing up. She's tried plugging it into different rooms, on her laptop, etc, none seem to get rid of the temperature problem. I've had the phone since August 2010 and never had any issues with it. I also never once saw that temperature error message so was taken aback when she showed me it over skype. I just upgraded to the S3 and gave her the phone 2 weeks ago, but surely it shouldn't just die out just like that? Thought the Vibrants were made tougher than that?
Any help would be greatly appreciated. Much thanks in advance
Its most probably a kernel issue or a bug in the rom; so the only way to find out is to flash another kernel/rom..
P.s Vibrants are rock solid
Sent from my SGH-T959 using xda app-developers app
Update- Phone doesn't even turn on anymore, no signs of life
danny_extremex said:
Its most probably a kernel issue or a bug in the rom; so the only way to find out is to flash another kernel/rom..
P.s Vibrants are rock solid
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Will be looking into reflashing another kernel/rom when I get home in a few weeks time, but it must be noted that the phone has been showing no signs of life for the last few days now. After letting it sit out for 7 hours on the first night, battery out and everything, she went to plug it in the following morning and this time absolutely no notification came up. Not even a lighting up of the phone or anything. No signs of life at all. Every time she hit the power button nothing occurred. The phone still heats up and after a few minutes while plugged in and gets very hot to the touch again but no matter how many times she attempts to turn it on, nothing happens.. She's tried plugging it into her computer via usb, into electric sockets in other rooms, even in the bathroom in one of the 115 volt electric shaver outlets in the bathroom (we live in the UK currently), and none of these ideas worked. Still no signs of life. It has been this way for three days now and is frustrating as I can offer no advice to her to get the phone to turn on anymore.
What on earth can be the problem? Has this happened to anyone before? And is there a fix to this or can we consider the phone to be a paperweight at this point?
polosprt009 said:
Will be looking into reflashing another kernel/rom when I get home in a few weeks time, but it must be noted that the phone has been showing no signs of life for the last few days now. After letting it sit out for 7 hours on the first night, battery out and everything, she went to plug it in the following morning and this time absolutely no notification came up. Not even a lighting up of the phone or anything. No signs of life at all. Every time she hit the power button nothing occurred. The phone still heats up and after a few minutes while plugged in and gets very hot to the touch again but no matter how many times she attempts to turn it on, nothing happens.. She's tried plugging it into her computer via usb, into electric sockets in other rooms, even in the bathroom in one of the 115 volt electric shaver outlets in the bathroom (we live in the UK currently), and none of these ideas worked. Still no signs of life. It has been this way for three days now and is frustrating as I can offer no advice to her to get the phone to turn on anymore.
What on earth can be the problem? Has this happened to anyone before? And is there a fix to this or can we consider the phone to be a paperweight at this point?
Click to expand...
Click to collapse
Some kernels require a certain amount of power to fully boot the phone up and will not charge until it has 5% battery or so. I personally think her battery may be unable to hold a charge or like I said before it doesn't have enough juice to boot the phone because of the kernel. There is a way to charge the battery with the phone off. You can use ANY kind of usb cord, I used an old printer usb cable when I had to do this. All you do is cut off the side that is not usb and strip the positive and negative wires(red and black), then place the stripped wires on the positive and negative connectors on the back of the phone and insert the battery (make sure it's a snug fit). Plug the usb end into your pc and charge the battery that way, DO NOT let charge for over 2 minutes at a time. Wait five minutes and do it again if you have to. If she gets it to boot up, I would definitely flash a new kernel first to see if thats how the problem originated.
Sent from my SGH-T959 using xda premium

[Q] Weird battery and screen issues

Hey guys and gals
this is my first post here. although a lot here is about rooted devices with custom ROMs, I hope you can help me out - you sure have a lot of expertise here compared to many other forums.
For the past two days I've been running into some of the weirdest problems with my Galaxy S2. Before i go into detail, here is the summary:
1. Screen time-out doesn't work while device is not plugged to a charger or computer
2. Notification shows 100% charge for a very long time (hours after heavy usage)
3. Not sure if charging actually works
4. Booting up seems to fail when not connected to a charger
it started yesterday when I noticed the phone light up and say it was charging. The problem is it wasn't - it was in my pocket.
Then I noticed that the screen didn't time out. I changed the setting, nothing - it remained on. I could push the power to make the screen turn off and on again but it wouldn't time out itself.
The charging info went away... at some point. I left it to charge over night and in the morning it indeed showed 100% in the notification bar. The problem is it remained 100% for A LONG time. In the settings menu under the battery it says it has been running on batter for 0 secs and showed 100% charge. For hours... There were no info about any apps or function using the battery. that part was clear.
Then i discovered that the screen time out problem goes away while connecting the charger or via USB to a PC. Then it times out. As soon as i unplug the charger it never times out....
I'm actually not sure if the charging works. Indeed it shows charging but sometimes it magically reaches 100% rather quickly.
Because I suspected a battery fault I used another battery. let it drain completely and then tried to recharge. Can't - when booting it shows a battery icon with question mark and then goes to show that the battery is 100% charged. Then the question mark and then 100% again. Seems to be in some sort of loop.
I've done the factory reset, I had a new firmware installed via Odin just in case. The problem still remains.
Booting the device seems to be an issue and only work with charger or USB cable attached. Ot it will be in that "what battery" and "100% charge" cycle...
I've searched high and low today but couldn't find anyone with the same problem.
Have any of you an idea? Really down't want to get a new phone! Seems to be a very bad month going on because a few weeks ago I had really serious issues with my brand new hybrid camera which i have to buy ... again! sold it for parts for pocket money....
Any help would be really appreciated! thanks!
That's really strange....try getting out the battery,charge it to max va an external charger,or borrow a friend's Galaxy S2.Leave the phone withou battery for an hour.Then when you put it in,go to recovery,and "wipe battery stats"(Root it if it's not).See if that works.
GamingDj said:
That's really strange....try getting out the battery,charge it to max va an external charger,or borrow a friend's Galaxy S2.Leave the phone withou battery for an hour.Then when you put it in,go to recovery,and "wipe battery stats"(Root it if it's not).See if that works.
Click to expand...
Click to collapse
thanks for your thoughts. i will try to root it wipe battery stats. i've never rooted before so i hope i find the single best tutorial to do that
thanks again!
kuldark said:
thanks for your thoughts. i will try to root it wipe battery stats. i've never rooted before so i hope i find the single best tutorial to do that
thanks again!
Click to expand...
Click to collapse
How long have you had the phone? The usb flex cable has issues over time. A symptom of this is the charging when not connected to the charger.
If it is this issue the part is cheap (around 5$ I believe).

Moto Z update ruined phone

Ok I've had the Moto Z for a while and its a great phone. Or it was until a few weeks ago. In the space of a couple of weeks a few official updates were sent to my phone and thinking nothing of it I updated as requested. The last update has seriously messed the phone up.
Problems since the update:-
- Battery drain now has the phone running out in about 10 hours. This problem seems to be intermittent, the majority of the time it happens and drains the phone quickly but not all of the time and usually its Android OS using between 25-50%. Also safe mode has no effect on the problem.
- Phone speaker stops working. Start the phone up and its working, but after a undetermined amount of time (no more than a hour or so) the speaker no longer works. If I get a call I have to turn on speaker phone to be able to hear anyone. Reset the phone and it works normally, only to happen again soon after.
- Phone charging stops working. Again start the phone and plug in the charger and it works fine. But after its charged, again after a undetermined amount of time, charge no longer works. Plug the charger in and the phone indicates its charging with the little light coming on at the top. But nothing else on the phone indicates its charging and the battery continues to drain. Reset the phone and suddenly it chargers normally. Same thing then happens again given time.
What I've tried to do about it:-
- I've tried running in safe mode, which makes no difference
- I've tried a full reset, which makes no difference
- I even unlocked the bootloader and installed a custom OS (Lineage). Thinking that obviously this will wipe out the new update from Lenovo and the phone would have to work properly again. But no, nothing changes, somehow Lenovo have done something beneath the OS that's causing these problems.
The question:-
Does anyone have any idea what could be causing this or have you at least seen these issues before?
I fail to gasp what is the purpose of the topic and I don't see a question.... If you're looking for compassion, I think the internet is the wrong place.
If you're sure that the problems is the updates, downgrade to the latest version that worked well for you. Since you've already unlocked the bootloader, try any of the variety of roms available here to verify you don't have a hardware problem.
apocalypse_bg said:
I fail to gasp what is the purpose of the topic and I don't see a question.... If you're looking for compassion, I think the internet is the wrong place.
Click to expand...
Click to collapse
The point of my post is obvious, I've got a issue with my phone and want to know if anyone has seen this issue with the Moto Z before and if they have any idea what may fix it. The question is right there near the end:
"Does anyone have any idea what could be causing this or have you at least seen these issues before?"
Click to expand...
Click to collapse
apocalypse_bg said:
If you're sure that the problems is the updates, downgrade to the latest version that worked well for you. Since you've already unlocked the bootloader, try any of the variety of roms available here to verify you don't have a hardware problem.
Click to expand...
Click to collapse
I've tried a different ROM:
- I even unlocked the bootloader and installed a custom OS (Lineage).
Click to expand...
Click to collapse
Honestly don't know how my post was unclear at all, but I've gone and tried to make it even more clear with a quick edit, hope that helps.
I have exactly the same problem. For me it occurred after updating to nougat. So fare I tried nearly everything. Disabling nearly everything to the bare minimum, custom ROMs, resetting, trying to flash only parts of the Android 6 firmware (modem, Bluetooth, DSP) since a complete downgrade is not possible, using all kinds of battery tools with a rooted device, using custom kernels... I always ended up with a constant battery drain of 3 to 8 percent per hour no matter what I did. Same in flight modus. Since under Android 6 the device didn't show this behavior I think that the problem must be somewhere in the firmware beneath the OS level. An the cruel thing is that sometimes without a reason for maybe an hour or two my moto z doesn't drain an works fine so that I do not believe in a hardware problem.
Thanks for the post. Yeah it seems like something has been changed underneath the OS. I know that sometimes memory config gets changed with newer Android operating systems (at least I think so?), but could that cause all these problems?
BTW, do you have all three of the problems I mentioned? Battery drain, sound stops working and charging stops working?
Since in this condition the Moto z is not really usable for me I switched back to my old phone and I am not using it that much as a daily device, I cannot really tell about sound or charging problems. So far I did not notice those problems.
DonnieDio said:
Problems since the update:-
- Battery drain now has the phone running out in about 10 hours. This problem seems to be intermittent, the majority of the time it happens and drains the phone quickly but not all of the time and usually its Android OS using between 25-50%. Also safe mode has no effect on the problem.
Click to expand...
Click to collapse
I feel like battery life is a bit worse than with M, but I didn't experience anything as bad as you did. I switched to a custom ROM after updating to 7.0.1
DonnieDio said:
- Phone speaker stops working. Start the phone up and its working, but after a undetermined amount of time (no more than a hour or so) the speaker no longer works. If I get a call I have to turn on speaker phone to be able to hear anyone. Reset the phone and it works normally, only to happen again soon after.
- Phone charging stops working. Again start the phone and plug in the charger and it works fine. But after its charged, again after a undetermined amount of time, charge no longer works. Plug the charger in and the phone indicates its charging with the little light coming on at the top. But nothing else on the phone indicates its charging and the battery continues to drain. Reset the phone and suddenly it chargers normally. Same thing then happens again given time.
Click to expand...
Click to collapse
None of the above ever happended to me
StarStorm said:
I feel like battery life is a bit worse than with M, but I didn't experience anything as bad as you did. I switched to a custom ROM after updating to 7.0.1
None of the above ever happended to me
Click to expand...
Click to collapse
I've never seen anything like it before. Its so random as well. I mean yesterday I rebooted and then charged the phone before I left for Football at 4pm. At about 11pm that night I heard the battery low sound (45% of the battery had be used by Android OS..). First thing I thought of was that usually the phone wouldn't still be making sounds by now. Since as I said earlier usually the speaker stops working along with charging within a hour or so of a reboot and this had been over 7 hours without a reboot. So I tried plugging it in and it started to charge. But then when I woke up this morning again the sound was disabled and it won't charge, it just took longer for the problem to occur this time..
How can we stop asking to update to this patch?
I has already disabled this on the developer preferences but still asking every 10 minutes
Any suggest please
Mine even worst. Battery drain fast and mobile away very warm. It suddenly reboot and shown low battery. Battery drain from 50 to 3 percent in a second! Have you guy come across this?
doug107hk said:
Mine even worst. Battery drain fast and mobile away very warm. It suddenly reboot and shown low battery. Battery drain from 50 to 3 percent in a second! Have you guy come across this?
Click to expand...
Click to collapse
Yep I've also had that as part of my problem, though it had only happened a few times over the course of the month so I forgot about it with all the other problems I mentioned going on.
Basically my phone would be sitting on, say 40%, and after a reboot it would start up in the single digits.
I recently tried changing to a custom kernel to see if maybe that was causing the problem (I'd already tried changing OS). But all the problems are still there using the new kernel. Think my next step should be to try to go back to a 7.0 Android version. Are there any custom Android ROMs using 7.0?
It is said that the Motorola Manager can rescuer lost data even if the data has been covered on phone , is it true ?
Just curious what came of this. My Z, unrooted, has started running crazy hot and the battery life is not good. 6-10 hours. When I connect it to my Anker PowerDrive 2 in the car, the battery actually discharges faster or I get the slow charge warning.
Hi I have exactly the same problems as the op and tried resetting to no avail.Its driving me nuts.
Short update about the massive battery drain problem: like I wrote above, in the past weeks I tried everything from custom kernels to custom roms, resetting, deleting and so on. Nothing helped. So I went back to stock and didn't use the phone the last weeks. Today I read in an other thread about bluetooth problems that a fix for the not working bluetooth was to activate flight mode, restart the phone and deactivate flight mode. So I activated flight mode, pressed the power button for 10 seconds or so until the phone restarted an deactivated flight mode. And now the absolute strangest thing happened: for the last 5 hours the phone lost 0% battery in standby with wifi and lte on. Since I did all the mentioned things above without any effect I do not understand this at all but right now I think that this could be a (temporally) fix also for the battery drain problem.

Redmi Note 4x 4/64 Mtk - Stuck in the bootloop after battery drainage, cannot charge.

Dear all,
I hope there is someone here, who can help me with my issue. I lost my hope after trying almost everything found in the internet.
So here is the problem: I was using my phone as a navigation in my car. The battery was low, so I used the car charger and kept it plugged, while driving. I observed, that even though I was charging my phone via car charger, the battery continued to get low and finally the phone turned off. After reaching home, I plugged my phone with an original quick charger from Xiaomi. Unfortunately I was not able to charge my phone and it got stuck in a bootloop, with a phone showing Mi Logo, vibrating and switching off repeatedly.
When I connect the phone with the laptop, it is shortly recognized (when it is booting) and then disconnected and again and again. I can go to fastboot mode but I cannot flash my phone using MiFlash, because I get an error: Failed. Low battery.
Does anyone know the solution? I would really appreciate any help.
adka said:
Dear all,
I hope there is someone here, who can help me with my issue. I lost my hope after trying almost everything found in the internet.
So here is the problem: I was using my phone as a navigation in my car. The battery was low, so I used the car charger and kept it plugged, while driving. I observed, that even though I was charging my phone via car charger, the battery continued to get low and finally the phone turned off. After reaching home, I plugged my phone with an original quick charger from Xiaomi. Unfortunately I was not able to charge my phone and it got stuck in a bootloop, with a phone showing Mi Logo, vibrating and switching off repeatedly.
When I connect the phone with the laptop, it is shortly recognized (when it is booting) and then disconnected and again and again. I can go to fastboot mode but I cannot flash my phone using MiFlash, because I get an error: Failed. Low battery.
Does anyone know the solution? I would really appreciate any help.
Click to expand...
Click to collapse
Are you on miui or a custom rom?
I think I know what problem you are facing, your device's battery is actually drained of all the power, like it empty. So drained that it doesn't even have the energy to turn on the phone to get power. I had a lenovo a560 last year, and it had the same problem, so what i had to do was either leave it for charging and pray that it begins charging (and sometimes after 3 or 4 hours the battery started charging as normal when it got 1% battery), or the second method was that i took the removable battery out and charged it externally using wires. The second method worked since the battery got enough power, to keep the phone on during charging.
Now the problem is that redmi note 4 doesn't have a removable battery, so either you can leave the phone for charging, and actually forget about it for a day, or the only other thing is that you have to visit a service center.
Not joking about the charging process but that is the only thing you can do.
---------- Post added at 06:15 PM ---------- Previous post was at 06:12 PM ----------
adka said:
Dear all,
I hope there is someone here, who can help me with my issue. I lost my hope after trying almost everything found in the internet.
So here is the problem: I was using my phone as a navigation in my car. The battery was low, so I used the car charger and kept it plugged, while driving. I observed, that even though I was charging my phone via car charger, the battery continued to get low and finally the phone turned off. After reaching home, I plugged my phone with an original quick charger from Xiaomi. Unfortunately I was not able to charge my phone and it got stuck in a bootloop, with a phone showing Mi Logo, vibrating and switching off repeatedly.
When I connect the phone with the laptop, it is shortly recognized (when it is booting) and then disconnected and again and again. I can go to fastboot mode but I cannot flash my phone using MiFlash, because I get an error: Failed. Low battery.
Does anyone know the solution? I would really appreciate any help.
Click to expand...
Click to collapse
But wait, if the phone is able to stay in fastboot mode, why not charge it there? Like just open fastboot mode, and connect the charger. It will atleast charge some percent.
MyNameIsRage said:
Are you on miui or a custom rom?
I think I know what problem you are facing, your device's battery is actually drained of all the power, like it empty. So drained that it doesn't even have the energy to turn on the phone to get power. I had a lenovo a560 last year, and it had the same problem, so what i had to do was either leave it for charging and pray that it begins charging (and sometimes after 3 or 4 hours the battery started charging as normal when it got 1% battery), or the second method was that i took the removable battery out and charged it externally using wires. The second method worked since the battery got enough power, to keep the phone on during charging.
Now the problem is that redmi note 4 doesn't have a removable battery, so either you can leave the phone for charging, and actually forget about it for a day, or the only other thing is that you have to visit a service center.
Not joking about the charging process but that is the only thing you can do.
---------- Post added at 06:15 PM ---------- Previous post was at 06:12 PM ----------
But wait, if the phone is able to stay in fastboot mode, why not charge it there? Like just open fastboot mode, and connect the charger. It will atleast charge some percent.
Click to expand...
Click to collapse
Hi, i thought about it before, but the phone was staying in fastboot mode for a very short time, to short to charge any resonable amount of power, and kept rebooting quickly. I left the phone for two days without trying to fix it and I tried just now to go into fastboot and try to charge. It stays now for quite a time in fastboot so I will keep my fingers crossed that I will be able to charge. I will update here if it was a success or not. Meanwhile, thank you for all your ideas! Lets see what happens...
adka said:
Hi, i thought about it before, but the phone was staying in fastboot mode for a very short time, to short to charge any resonable amount of power, and kept rebooting quickly. I left the phone for two days without trying to fix it and I tried just now to go into fastboot and try to charge. It stays now for quite a time in fastboot so I will keep my fingers crossed that I will be able to charge. I will update here if it was a success or not. Meanwhile, thank you for all your ideas! Lets see what happens...
Click to expand...
Click to collapse
Best of luck brother.
MyNameIsRage said:
Best of luck brother.
Click to expand...
Click to collapse
Unfortunately, no good results. I kept my phone in fastboot mode multiple times, but I was not able to charge my phone. Turning off fastboot is only causing phone to stuck in bootloop.
I also had an impression, that the phone was not warm at the back, where the battery is. Now I am starting to think that the battery is completely dead and I have to change it. But how is it even possible, that after 8 MONTHS the battery is completely f***ed up?
Can I somehow check the state of the battery? I would like to be sure, that there is no way to bring the battery back to life and I really have to go somewhere to change it. I am really reluctant to have a battery from some unknown company. :crying:
adka said:
Unfortunately, no good results. I kept my phone in fastboot mode multiple times, but I was not able to charge my phone. Turning off fastboot is only causing phone to stuck in bootloop.
I also had an impression, that the phone was not warm at the back, where the battery is. Now I am starting to think that the battery is completely dead and I have to change it. But how is it even possible, that after 8 MONTHS the battery is completely f***ed up?
Can I somehow check the state of the battery? I would like to be sure, that there is no way to bring the battery back to life and I really have to go somewhere to change it. I am really reluctant to have a battery from some unknown company. :crying:
Click to expand...
Click to collapse
Are you rooted?
This is really a kernel fault man, I had the same issues with mediatek Chipsets before, but you are saying in "8 months", so that means you are well covered in warranty. You can send an e-mail to Xiaomi customer care or visit a service centre with the phone bill. I am pretty sure a faulty battery or such happening can be covered using warranty, plus I would suggest NOT to get the battery changed from a 3rd party store.
MyNameIsRage said:
Are you rooted?
This is really a kernel fault man, I had the same issues with mediatek Chipsets before, but you are saying in "8 months", so that means you are well covered in warranty. You can send an e-mail to Xiaomi customer care or visit a service centre with the phone bill. I am pretty sure a faulty battery or such happening can be covered using warranty, plus I would suggest NOT to get the battery changed from a 3rd party store.
Click to expand...
Click to collapse
Sorry, I actually don't know much about the phones, so I don't know what 'rooted' means. I never did anything with my phone, software or whatever more than required.
With the warranty there is a different problem in my case: I bought my phone in China when I was there for my business trip and I live in Europe (yeah I know, my own fault, I should have bought it at home). I have bill and everything but I guess it will not help. Besides, Xiaomi gives 6 months warranty for battery (in case this is really the battery).
adka said:
Sorry, I actually don't know much about the phones, so I don't know what 'rooted' means. I never did anything with my phone, software or whatever more than required.
With the warranty there is a different problem in my case: I bought my phone in China when I was there for my business trip and I live in Europe (yeah I know, my own fault, I should have bought it at home). I have bill and everything but I guess it will not help. Besides, Xiaomi gives 6 months warranty for battery (in case this is really the battery).
Click to expand...
Click to collapse
Knowing that you are not rooted is a positive thing when regarding the warranty, ok so here is the thing which you should do. But first of all please stop the battery charging process, since this can now be harmful and can damage the components. Ok so here's what you should do -
[email protected]
Send an email to that address regarding the battery problem. And provide the details including about the drainage of battery, and the methods which you tried. Plus attach the bill also. It doesn't really matter where you bought it, because the bill serves as to give them information that the device you own is actually bought by you, and it contains details about device like IMEI etc. If they respond and say that you can send your device to them, (in this case they will give you an address) you should do that. If they say they cannot help it, then consider getting a repair from a local shop.
I just checked my phone's inside and found out that you cannot externally charge the battery, so this means you need a repair, unfortunately.
Before ending this reply I just wanna clear the fact that,
The battery isn't damaged, it just isn't able to get power,(here it is because of the device) this means that if somehow some energy can be provided to the battery, the battery need not be replaced.
I wish you luck , may you be able to fix your phone again.
adka said:
Dear all,
I hope there is someone here, who can help me with my issue. I lost my hope after trying almost everything found in the internet.
So here is the problem: I was using my phone as a navigation in my car. The battery was low, so I used the car charger and kept it plugged, while driving. I observed, that even though I was charging my phone via car charger, the battery continued to get low and finally the phone turned off. After reaching home, I plugged my phone with an original quick charger from Xiaomi. Unfortunately I was not able to charge my phone and it got stuck in a bootloop, with a phone showing Mi Logo, vibrating and switching off repeatedly.
When I connect the phone with the laptop, it is shortly recognized (when it is booting) and then disconnected and again and again. I can go to fastboot mode but I cannot flash my phone using MiFlash, because I get an error: Failed. Low battery.
Does anyone know the solution? I would really appreciate any help.
Click to expand...
Click to collapse
Any aftermath? What happened?
MyNameIsRage said:
Any aftermath? What happened?
Click to expand...
Click to collapse
I am still waiting for the response from Global Service. If nothing happens, I will go to local 'mi center', where I know they can repair xiaomi phones, but not on warranty.
Apart from that, phone is still dead, but I have not tried yet anything else. I found this: https://xiaomifirmware.com/guides-and-tips/fix-bootloop-redmi-note-4-mtk/
But I am not sure, if this should work. Anyone have tried?
adka said:
I am still waiting for the response from Global Service. If nothing happens, I will go to local 'mi center', where I know they can repair xiaomi phones, but not on warranty.
Apart from that, phone is still dead, but I have not tried yet anything else. I found this: https://xiaomifirmware.com/guides-and-tips/fix-bootloop-redmi-note-4-mtk/
But I am not sure, if this should work. Anyone have tried?
Click to expand...
Click to collapse
That post shows you how to enter deep flash mode. You can give it a try. If that works, Voila, If it does't better go the service center.
So I got the response from service (it took them ages). Maybe it will help someone:
With respect to your concern, I would request you to please follow some troubleshooting steps in order to resolve your issue:
Try to charge your device with another compatible charger for at least 30 minutes
Long press power button for 10-15 seconds and check whether the device is responding or not
If the issue persists please follow the below mentioned steps:
Note: The below mentioned procedure deletes the data you have on your phone.
Sign Out from your Mi Account :-
Go to the settings
Select Mi Account
Confirm to Sign out
Create a backup : -
Go to the settings
Go to the additional settings
Go to the backup and reset
Go to the local backup
Go to the backup
Select system and apps
Then, select backup so that a backup would be created
After creating the backup, you can find your backup file through the below mentioned steps:
Go to the "explorer"
Select "storage" option
Then, "MIUI"
You will get a "backup" option
Select "all backup"
In this folder, you will be able to see your "backup file"
(Note :- Please save the backup file on your PC/Laptop so that your important data would be prevented)
Factory data reset :-
Go to the settings
Go to the additional settings
Go to the backup and reset
Tap on factory data reset
In order to restore your backup file, please follow the below mentioned steps:
Go to the settings
Go to the additional settings
Go to the backup and reset
Go to the local backup
After that, select your "backup file"
Then, "restore" it
I did not try anything from this yet, I have my phone at home, but maybe it will help some of you.
btw. the previous method from the link (deep flash mode) is not working for me.
PEOPLE I FIXED MY PHONE!!! I used again and again this method, which I have already posted before: https://xiaomifirmware.com/guides-and-tips/fix-bootloop-redmi-note-4-mtk/
I didn't work at the beginning, so I left my phone and actually wanted to wait till I go back home to my country for the weekend and visit Xiaomi service, but FINALLY IT WORKED!!! I cannot explained what was the reason that this time it clicked. My phone was completely drained, left for long time without touching. As a result I have a battery icon now and it is charging, no bootloop anymore. Hope this method would help someone. Be patient and try multiple times!
So it is not software problem causing the bootloop
So it is not a software, but only hardware - the battery - as the only problem in this case. I am facing a very similar case with my Redmi Note 4x Mediatek (4/64 Memory) just starting Friday morning (9Feb). I thought it was charging overnight, but in the morning found the power totally drained, and stucked not be able to recharge for hours. This phone is still under warranty (9month use) but ridiculously the Official Service Agent said they need up to 40days to fix this phone. This is worst experience comparing to other phones I ever had.

Battery problems and early shutdown? give this a try!

Hi people, nexus 6P owner since 2 years now. I remember when I received the phone I could reach without worries 5 to 6 hours of Screen but then, after nougat and now Oreo, I've never achieved again that numbers.
After rooting my phone, flashing carbon rom and installing elemental X kernel, I played with governor profiles and improved my SOT a little over this year but it was getting worser and worser by every day (2 to 3 hours of screen on time and heavy idle drain). Finally, the real problem came the other day when for the first time my phone shutdown at 29% suddenly after opening the camera.
So I read internet and found in the nexus 6 (not 6P) forums that someone suggested a solution concerning a problem with how the phone meter the battery remaining, suggesting doing a series of steps of charge discharge that I will list here. This, and changing to ABC rom may have done the trick, as now I'm getting much more normal battery life (considering the degradation of 2 years, 2700mah left approximately) of 4, 4 and a half hours (yours will be better) SoT and an idle drain of less than 0,5% per hour, and apparently it didn't shutdown early anymore.
So, give this steps a try if you tried everything like I did and you still having problems with battery drain.
STEPS THAT MAY SOLVE EARLY SHUTDOWN PROBLEM:
- Charge your phone to 100% and use it until it shutdowns (look at what percentage).
- Boot to recovery by pressing power and vol - button, and once in there let it drain the battery until it shutdowns by itself (may take a lot of time so increase brightness to maximum in the recovery menu under settings to consume it faster).
- Now it has really reached 0% and if you try to power it on it won't let you by blinking red in the notification led.
- Plug the charger and leave the phone off until the battery indicator show it's full.
- Unplug it and turn it on, it should show you the battery at less than 100%, like 95%, 90% or even less depending on how bad it was calibrated (mine showed 95%).
- Plug it to the charger without turning it off until reaching 100% and only then unplug it first and then turn it off quickly.
- Plug it one more time (off) until the icon shows it is full and then unplug it and turn it on, now it should say a number closer than before, like 98% or 99% (mine was 99) or it may be 100%. If it shows 100% then you're good to go with the calibration, but if it shows less, repeat the process by letting charge until 100 and then doing the same steps as before until you turn it on without charging and finally it shows 100% battery.
Please report back if this steps worked for you, because for me I think it made the trick.
Now for the battery drain what I did was this steps,
STEPS THAT MAY STOP THE POST-NOUGAT HEAVY BATTERY DRAIN (android OS drain, etc):
-Unlock and Root the phone
- Install ABC rom (check the post here in XDA)
- Flash ElementalX kernel (also here)
- Install the app "ex kernel manager" from the play store
- Enter settings and disable printers (you still can enable them if you have to print something)
- Install Greenify from the play store and select all the apps that don't use notifications.
- Uninstall unnecessary apps that you don't use anymore.
- In the Ex Kernel manager app go to CPU -> governor options and select "load". Choose one of the following recommended profiles: Excalibur V2, Dragon Fly v1, Butterfly or DeadPool. (Or check the guide in XDA about governor profiles).
- Finally activate the run on boot option and reboot to recovery, wipe dalvik and cache and then boot into system.
If you have luck like me, your phone will run very smooth and battery life will be normal to it's current degradation. My phone now last me all day like before and I don't have to charge it twice or three times like I did and best of all, when I don't use it, it almost don't lose battery (2 to 3% overnight).
Also I've never seen again that android system process consuming the same amount as the screen!
I hope this serve someone and maybe save some phones too , I never resigned my 6p because it's a great phone with one of the best cameras out there even today and with great speakers too.
Please let me know if it worked for you! Of course I don't promise it will, but you have nothing to lose anyway! Good luck.
Pd. Sorry for my English , I'm from Argentina
UPDATE: Today my nexus shutdown at 10% but only because I opened on purpose the camera to check if that is the problem, and aparently it is. I've read that when then phone has low power, an app that consumes a lot of battery like the camera may cause shutdown to prevent the phone damaging internal components. So no fix for that at the moment, just don't use the camera with low percentage.
Hi, I don't know if this thread is still on but I'd like to say that I had the same issue. I have a Nexus 6, as you said, and I've installed on it the Resurrection Remix ROM (Neo version). After that, the phone suddenly shut down everytime it reaches 20 or 30 %. I tried two solutions they suggested me;
1) In bootloader menu, go on bootloader logs and press start button for 10 seconds more or less (when you get Google logo and the phone actually boot)
2) Try to reboot the phone in Safe mode and then back in Normal mode
I've also tried to calibrate again the battery (maybe I did it wrong); I followed a guide on it but I can't remember every step of it (if interested I'll try to find it again). Nothing worked, the phone still presents the same issue and I really don't know what to do. I'd like to try this too hoping it works otherwise the last thing I can do, I guess, try to flash again the ROM. Do you have any suggestions? Thanks so much
P.S.
The battery works PERFECTLY; before I flashed the ROM it worked so damn good so I really can't believe that it needs to be replaced, I know that the phone is really old but it always worked fine so it's more logical presume that the problem is with the flashing
Using Stock Nexus 6 Shamu Kernel, with last TWRP and RR OS
Just replace your battery - you might think it's the flashing etc, but at the end of the day my money is on your battery just having called it day, which they can do quite suddenly.
I found that once that early shut down starts it gets worse quick.
It's not that big of deal to change out on these phones anyway and if you do it yourself it's cheap (15 dollars or so). - I've just done it for the second time, not that I was having early shutdowns with my first replacement but after about 18 months life was starting to wane.
Just sharing my experience with my nexus 6p.
Early shutdown problem sure gives us headache. Already tried several methods like calibration, reflashing to factory images, downgrade to minor build or major build, none of them works.
The only solutions that works for me is replace the battery, only cost between $10 to $20 for me (it depend on type battery that you buy, mine is OEM one)
Hello, giving a try to the OP guide regarding early battery shut down. Just a quick question - how long does it take for battery to drain out while in recovery mode? Screens been on for like 2hours now, I see top right screen corner the battery % completely disappear, but recovery still usable. Just wonder, how long it will take for phone to auto shutdown while in recovery mode?
And if this does not work, I'll just replace battery, like @reintakura wrote above.
This device is a disaster. Does it really work?
I tried this the other day. The phone shut off when the low battery came on. I kept powering it up. The first few times it shut off immediately. The next time it turned on and said I had 10% left. Let that 10% run down, it powered off. I kept powering it on... it would boot. I did this maybe 50 times, every time it would boot and then shut down. Then the last time it got "stuck" on the Shutting Down screen. I let it sit like that for a good 10 minutes. It never powered off, it just was stuck on the shutting down screen. I held the power button down to initiate a hard shut down. Plugged it into the charger, device off. Screen said it was 100% a few hours later. Turned on device, device reported 100% used it until it got to 70% and then the low battery light came on and it powered off. Let it charge overnight with device off. Right now it's slowly losing battery, I'm at 76% and it hasn't shut down.
Strange stuff going on.
i was facing the same problem, two days ago i returned to 8.1 abc rom
i'm getting 4h sot and no early shutdown
I can't believe I spent $200 on this **** phone and waited 3 years to get it thinking its the best thing since fried rice, mine started shutting down at 20-30% now it shuts down anywhere from 30-85%!!!!!!!! ahahahahahaha in the end its my fault for buying refurbished, someone obviously sent this crap back already and they did nothing to fix it and conned me into buying it.
Paquinho said:
Please let me know if it worked for you! Of course I don't promise it will, but you have nothing to lose anyway! Good luck.
Click to expand...
Click to collapse
Hi, there. This reply is way late, but I've been away for years and I've only now decided to come back, so I'm necroposting on everything that's relevant to me right now. I hope that's not a serious offense.
I've had my 6P since August 2016. I bought it NOS from Google Fi at a slight discount. It worked like a charm for me for years until around winter 2018/2019, when it started shutting down in the cold. I figured that was understandable. I bike a lot, even in sub-zero temperatures, and I tended to keep my phone in the breast pocket of my windbreaker.
It didn't care too much for that.
So, I started putting it into my backpack and it stopped shutting down.
Then, this summer (2020), the battery went off a cliff. It's been dying anywhere from 80 to 10% since June. Maps and the Camera are the big killers, but the battery will plummet from literally any use.
Yet, it will idle for days if leave it alone.
I recently decided to just wipe the thing back to factory and see if that solved anything. It was quite a feeling to scuttle all of my SMS (I backed them up to my Google account, but it seems like they've gone to some mysterious corner of the Internet from which they cannot be retrieved. Alas). It was kind of a catharsis to throw it all away.
I did back up all my media, however.
The factory reset solved nothing, so I tried the OP's recommendation. I loaded into the bootloader and, instead of waiting on the primary screen, I went into (stock) Recovery (my phone isn't yet rooted) and ran the display test a bunch of times. I alternated between that and selecting "Barcodes" since the all white screen is a bigger drain on the battery than the black and green default.
Eventually, the thing died, but it took hours. This, despite that it would die at the snap of the fingers when in the OS. Strange. I charged the device while off until it said it was full. It came on at 95%. I followed the OP's guide until it turned on at 100.
Yet, it still started draining immediately.
The current culprit is "Mobile Network Standby," which is rich because this phone has no SIM, so why is it even bothering to try and futz with the mobile network? I had been keeping the device on Airplane Mode, but I'd forgotten to turn it back on. I just reactivated that mode, so we'll see if that helps.
However, if I watch a guitar repair video on YouTube (pretty staid, not like gaming or an action movie), the battery just nosedives again.
I don't think that rooting and flashing a new ROM is going to solve this issue.
I bought a replacement battery. I'm just not eager to try and install it. So I may just try root and flash, since it's easier. I guess we'll see what happens.
wedel219 said:
Hi, there. This reply is way late, but I've been away for years and I've only now decided to come back, so I'm necroposting on everything that's relevant to me right now. I hope that's not a serious offense.
I've had my 6P since August 2016. I bought it NOS from Google Fi at a slight discount. It worked like a charm for me for years until around winter 2018/2019, when it started shutting down in the cold. I figured that was understandable. I bike a lot, even in sub-zero temperatures, and I tended to keep my phone in the breast pocket of my windbreaker.
It didn't care too much for that.
So, I started putting it into my backpack and it stopped shutting down.
Then, this summer (2020), the battery went off a cliff. It's been dying anywhere from 80 to 10% since June. Maps and the Camera are the big killers, but the battery will plummet from literally any use.
Yet, it will idle for days if leave it alone.
I recently decided to just wipe the thing back to factory and see if that solved anything. It was quite a feeling to scuttle all of my SMS (I backed them up to my Google account, but it seems like they've gone to some mysterious corner of the Internet from which they cannot be retrieved. Alas). It was kind of a catharsis to throw it all away.
I did back up all my media, however.
The factory reset solved nothing, so I tried the OP's recommendation. I loaded into the bootloader and, instead of waiting on the primary screen, I went into (stock) Recovery (my phone isn't yet rooted) and ran the display test a bunch of times. I alternated between that and selecting "Barcodes" since the all white screen is a bigger drain on the battery than the black and green default.
Eventually, the thing died, but it took hours. This, despite that it would die at the snap of the fingers when in the OS. Strange. I charged the device while off until it said it was full. It came on at 95%. I followed the OP's guide until it turned on at 100.
Yet, it still started draining immediately.
The current culprit is "Mobile Network Standby," which is rich because this phone has no SIM, so why is it even bothering to try and futz with the mobile network? I had been keeping the device on Airplane Mode, but I'd forgotten to turn it back on. I just reactivated that mode, so we'll see if that helps.
However, if I watch a guitar repair video on YouTube (pretty staid, not like gaming or an action movie), the battery just nosedives again.
I don't think that rooting and flashing a new ROM is going to solve this issue.
I bought a replacement battery. I'm just not eager to try and install it. So I may just try root and flash, since it's easier. I guess we'll see what happens.
Click to expand...
Click to collapse
your battery is probably aged, I got the same problem and replacing battery is the only solution that'll work.
Sent from my angler using XDA Labs
Ata Ur Rehman said:
your battery is probably aged, I got the same problem and replacing battery is the only solution that'll work.
Click to expand...
Click to collapse
I reckon that you are correct. However, I am noticing that my phone hasn't crashed since I followed the OPs charging guide. That's something, at least.
Although monstrous battery drain is still a huge problem. I will be swapping the battery.
My question is: root first and flash something custom, just to see what happens? For evidence gathering ... in the name of empiricism.
Or just go ahead with the swap before doing anything else?
wedel219 said:
I reckon that you are correct. However, I am noticing that my phone hasn't crashed since I followed the OPs charging guide. That's something, at least.
Although monstrous battery drain is still a huge problem. I will be swapping the battery.
My question is: root first and flash something custom, just to see what happens? For evidence gathering ... in the name of empiricism.
Or just go ahead with the swap before doing anything else?
Click to expand...
Click to collapse
yeah try root and installing ABC oreo ROM if that doesn't make differ at all then replacing battery is the only solution.
Sent from my angler using XDA Labs

Categories

Resources