This issue started yesterday. My setup at that moment was as following:
Multirom : Installed
Primary Rom: Lineage OS 14.1
Secondary Rom: TugaPower 48.0
I was using TugaPower rom. I opened music player and the phone got switched off. I tried restarting but into the middle of the booting process, again it shut down. I tried booting into primary rom but the same issue happened. Then I connected it into a charger and it booted normally. Phone's battery level was >80% at that moment. I unplugged the charger and kept it idle, it stayed on. However, if I try to perform any action like opening an app, it switches off if not connected to a charger. So, I kept the phone on charge entire day to use it.
Today I thought of fixing the problem by wiping it clean. So I wiped everything in the phone including Internal Storage. Then I flashed Lineage OS again but the same issue is there. It won't work without a charger despite the battery being full. Please note that TWRP was working fine without a charger so I don't think the battery is faulty. Anyway, I decided to flash COS 13 using fastboot. The issue was still there. then I flashed TWRP again but this time it is also getting shut down in the middle of installing Lineage OS. I plugged it, but still Rom is flashing fine but in the middle of Open Gapps flashing process, it shuts down despite being connected to charger. Now it won't boot to any rom. Just shuts down when it starts to boot.
So now I have a dead OPO with working TWRP(?) and fastboot. Another thing I noticed is that when it is connected to PC via MTP it does not show the available space it used to. Just Internal storage
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am not able to identify the actual issue. Is it a hardware problem? or any partition is corrupted?
Are the days of OPO are finally over?
EDIT: It was the battery all along! Thank you everyone for your feedback and helping me sort out the issue. OPO is still running fine.
Mystel said:
This issue started yesterday. My setup at that moment was as following:
Multirom : Installed
Primary Rom: Lineage OS 14.1
Secondary Rom: TugaPower 48.0
I was using TugaPower rom. I opened music player and the phone got switched off. I tried restarting but into the middle of the booting process, again it shut down. I tried booting into primary rom but the same issue happened. Then I connected it into a charger and it booted normally. Phone's battery level was >80% at that moment. I unplugged the charger and kept it idle, it stayed on. However, if I try to perform any action like opening an app, it switches off if not connected to a charger. So, I kept the phone on charge entire day to use it.
Today I thought of fixing the problem by wiping it clean. So I wiped everything in the phone including Internal Storage. Then I flashed Lineage OS again but the same issue is there. It won't work without a charger despite the battery being full. Please note that TWRP was working fine without a charger so I don't think the battery is faulty. Anyway, I decided to flash COS 13 using fastboot. The issue was still there. then I flashed TWRP again but this time it is also getting shut down in the middle of installing Lineage OS. I plugged it, but still Rom is flashing fine but in the middle of Open Gapps flashing process, it shuts down despite being connected to charger. Now it won't boot to any rom. Just shuts down when it starts to boot.
So now I have a dead OPO with working TWRP(?) and fastboot. Another thing I noticed is that when it is connected to PC via MTP it does not show the available space it used to. Just Internal storage
I am not able to identify the actual issue. Is it a hardware problem? or any partition is corrupted?
Are the days of OPO are finally over?
Click to expand...
Click to collapse
I'm pretty sure it's the battery.
replace the batteries and everything will be solved...no need to format of flash anything...
Mr.Ak said:
I'm pretty sure it's the battery.
Click to expand...
Click to collapse
Is there a way to confirm?
iPusak Gaoq™ said:
replace the batteries and everything will be solved...no need to format of flash anything...
Click to expand...
Click to collapse
Ok now you are telling that also means the battery is the main culprit..
Should I buy a battery from ebay ir contact OP service centre?
Now even twrp won't boot without power!
Mystel said:
Is there a way to confirm?
Ok now you are telling that also means the battery is the main culprit..
Should I buy a battery from ebay ir contact OP service centre?
Now even twrp won't boot without power!
Click to expand...
Click to collapse
There you go,the confirmation.
Anyways,have a look at battery thread in accessories,they have some nice recommendations there.
OP SVC don't have any batteries left,so don't bother contacting 'em.
Mystel said:
Ok now you are telling that also means the battery is the main culprit..
Should I buy a battery from ebay ir contact OP service centre?
Now even twrp won't boot without power!
Click to expand...
Click to collapse
Yes...i know this problem first hand cause i'm one of the first that have this problem 1 years ago...when a phone required a constant power from charger to boot normally then it is a clear sign of a dying batteries...don't be fool the with batteries percentage while you connect the phone cause it is not accurate anymore...
if you have OP service center nearby then i suggest you buy new batteries from them but if there no service center then buy new batteries in ebay, amazon or etc but you might get OEM's batteries instead of original batteries if you bought it online....still using OEM's batteries can give you around 3-4 hours of SOT depend on how you use it....
iPusak Gaoq™ said:
Yes...i know this problem first hand cause i'm one of the first that have this problem 1 years ago...when a phone required a constant power from charger to boot normally then it is a clear sign of a dying batteries...don't be fool the with batteries percentage while you connect the phone cause it is not accurate anymore...
if you have OP service center nearby then i suggest you buy new batteries from them but if there no service center then buy new batteries in ebay, amazon or etc but you might get OEM's batteries instead of original batteries if you bought it online....still using OEM's batteries can give you around 3-4 hours of SOT depend on how you use it....
Click to expand...
Click to collapse
I was getting around 1.5 - 2 hr SOT so I think OEM batteries will be fine too. I will still contact oneplus service center to inquire about battery replacement cost. I have seen some videos on youtube. Do you think changing battery by myself will be fairly easy?
Mr.Ak said:
There you go,the confirmation.
Anyways,have a look at battery thread in accessories,they have some nice recommendations there.
OP SVC don't have any batteries left,so don't bother contacting 'em.
Click to expand...
Click to collapse
Ok I will check the threads if there is any good battery recommendation in India, Thank you!
Mystel said:
I was getting around 1.5 - 2 hr SOT so I think OEM batteries will be fine too. I will still contact oneplus service center to inquire about battery replacement cost. I have seen some videos on youtube. Do you think changing battery by myself will be fairly easy?
Click to expand...
Click to collapse
Easy AF.
Mystel said:
I was getting around 1.5 - 2 hr SOT so I think OEM batteries will be fine too. I will still contact oneplus service center to inquire about battery replacement cost. I have seen some videos on youtube. Do you think changing battery by myself will be fairly easy?
Click to expand...
Click to collapse
Yes easy to change it yourself...even i change the batteries myself back then....
Mystel said:
This issue started yesterday. My setup at that moment was as following:
Multirom : Installed
Primary Rom: Lineage OS 14.1
Secondary Rom: TugaPower 48.0
I was using TugaPower rom. I opened music player and the phone got switched off. I tried restarting but into the middle of the booting process, again it shut down. I tried booting into primary rom but the same issue happened. Then I connected it into a charger and it booted normally. Phone's battery level was >80% at that moment. I unplugged the charger and kept it idle, it stayed on. However, if I try to perform any action like opening an app, it switches off if not connected to a charger. So, I kept the phone on charge entire day to use it.
Today I thought of fixing the problem by wiping it clean. So I wiped everything in the phone including Internal Storage. Then I flashed Lineage OS again but the same issue is there. It won't work without a charger despite the battery being full. Please note that TWRP was working fine without a charger so I don't think the battery is faulty. Anyway, I decided to flash COS 13 using fastboot. The issue was still there. then I flashed TWRP again but this time it is also getting shut down in the middle of installing Lineage OS. I plugged it, but still Rom is flashing fine but in the middle of Open Gapps flashing process, it shuts down despite being connected to charger. Now it won't boot to any rom. Just shuts down when it starts to boot.
So now I have a dead OPO with working TWRP(?) and fastboot. Another thing I noticed is that when it is connected to PC via MTP it does not show the available space it used to. Just Internal storage
I am not able to identify the actual issue. Is it a hardware problem? or any partition is corrupted?
Are the days of OPO are finally over?
Click to expand...
Click to collapse
I can confirm it is a problem with the batteries because I had almost the same issue on my one running RR.
Just got mine replaced 30 minutes ago and its running smooth. Just need to do few power cycles for calibration.
Good Luck!
Mystel said:
This issue started yesterday. My setup at that moment was as following:
Multirom : Installed
Primary Rom: Lineage OS 14.1
Secondary Rom: TugaPower 48.0
I was using TugaPower rom. I opened music player and the phone got switched off. I tried restarting but into the middle of the booting process, again it shut down. I tried booting into primary rom but the same issue happened. Then I connected it into a charger and it booted normally. Phone's battery level was >80% at that moment. I unplugged the charger and kept it idle, it stayed on. However, if I try to perform any action like opening an app, it switches off if not connected to a charger. So, I kept the phone on charge entire day to use it.
Today I thought of fixing the problem by wiping it clean. So I wiped everything in the phone including Internal Storage. Then I flashed Lineage OS again but the same issue is there. It won't work without a charger despite the battery being full. Please note that TWRP was working fine without a charger so I don't think the battery is faulty. Anyway, I decided to flash COS 13 using fastboot. The issue was still there. then I flashed TWRP again but this time it is also getting shut down in the middle of installing Lineage OS. I plugged it, but still Rom is flashing fine but in the middle of Open Gapps flashing process, it shuts down despite being connected to charger. Now it won't boot to any rom. Just shuts down when it starts to boot.
So now I have a dead OPO with working TWRP(?) and fastboot. Another thing I noticed is that when it is connected to PC via MTP it does not show the available space it used to. Just Internal storage
I am not able to identify the actual issue. Is it a hardware problem? or any partition is corrupted?
Are the days of OPO are finally over?
Click to expand...
Click to collapse
Try reflashing an older version of TWRP/ modded version and if that doesn't work, try an AOSP ROM. I had the same problem and got OMNI and AOSP 8.xx to boot.
valvze said:
Try reflashing an older version of TWRP/ modded version and if that doesn't work, try an AOSP ROM. I had the same problem and got OMNI and AOSP 8.xx to boot.
Click to expand...
Click to collapse
Now TWRP shuts down in the middle of flashing rom so no other ways. Sorry I was busy these days and OPO was lying dead. I just ordered one battery from eBay and will update once I replace the battery.
Well, I have the exact same issue & coincidentally or not, I was also running Tugapower 49. Phone will boot only with the charger connected. So, battery issue is confirmed.
I'll join your club. About 3 weeks ago had a similar problem but managed to get the phone to boot after an over night charge. The battery was around 13 months old. Ordered a new battery from ebay. Fitted it two days ago and flashed an updated lineage rom last night. My oneplus 1 is now stuck in a boot loop. After flashing and leaving it over night to update, it was still in the boot up logo this morning. Held in power button to kill power. Numerous attempts to boot up the phone failed. Only twice have I managed to get it to boot to TWRP recovery. Both times I have tried to resort to flashing the previous ROM, but still get stuck in the loop. I'm waiting to let it get to a full charge, then I'll try a fastboot method and pray that that works. I'll update if/when I get sorted
---------- Post added at 10:34 PM ---------- Previous post was at 09:48 PM ----------
Well.... had phone plugged into laptop charging. Wrote the above post. not 10 mins after, booted into Recovery first time, reflashed and got it working again........ wish I knew what was going off here but, its working now.
Had the same issue 4 months ago and I'm 99% sure it's the battery. Change it.
Replaced th battery.But in the process something messed up. First, touch would not recognize. Upper connector was loose. Now reconnected that and flashed lineage os. Having ghost touch constantly on "wipe" button position of twrp. This just started after setting up lineage. But the main issue was battery!
Mr.Ak said:
I'm pretty sure it's the battery.
Click to expand...
Click to collapse
iPusak Gaoq™ said:
replace the batteries and everything will be solved...no need to format of flash anything...
Click to expand...
Click to collapse
Quoting you if you have any idea about the ghost touches I am having after replacing the battery. The main issue is gone.
Mystel said:
Quoting you if you have any idea about the ghost touches I am having after replacing the battery. The main issue is gone.
Click to expand...
Click to collapse
There shouldn't be ghost touch problem after you changes the batteries unless you disconnect other ribbons and didn't reconnect it properly...dissemble the phone and disconnect all ribbon and reconnect it again for further test....
Sent from my A0001 using Tapatalk
iPusak Gaoq™ said:
There shouldn't be ghost touch problem after you changes the batteries unless you disconnect other ribbons and didn't reconnect it properly...dissemble the phone and disconnect all ribbon and reconnect it again for further test....
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Here is a sample video I just took. only the area between sim tray and power button is affected.
https://ufile.io/iql19
Related
Hi All, a few hours ago something really weird happened, I stopped using my phone with 60%+ of battery, one hour later when I tried to use it again it was off and would not turn on. I thought that something ate my battery so I placed it in my car's charger with no signs of life, so I thought that maybe the battery was fully discharged and it needed a few minutes before I could turn it on, but nothing. Once I got home, I plugged it in the original charger with the original cable and left it a few minutes and then unplugged it (trying to move the charger to another plug) and it suddenly booted up by itself with me not even pushing the on button, and once it booted the phone had 60%+ battery so it was never the battery.
Has anyone experienced something like that? what could cause my phone to shutdown and not respond until plugging and unplugging it? I'm attaching my last_kmsg
I'm running rooted stock 38R with Franco Kernel r27
i also experienced the same thing, randon deaths with more than 40%, have to put the phone to charger, it would say low battery but battery,would say 40% after it started up. please help!!!
boomsheklau said:
i also experienced the same thing, randon deaths with more than 40%, have to put the phone to charger, it would say low battery but battery,would say 40% after it started up. please help!!!
Click to expand...
Click to collapse
Me too! Rooted on fk r28. Still have not find out a solution.
potpit said:
Me too! Rooted on fk r28. Still have not find out a solution.
Click to expand...
Click to collapse
Google the following and you will find the instruction: How to fix One Plus One sudden death bug resulting in boot loops
but I don't know how to! Can anyone walk us through it? what is TWRP and how do I run a command??
boomsheklau said:
Google the following and you will find the instruction: How to fix One Plus One sudden death bug resulting in boot loops
but I don't know how to! Can anyone walk us through it? what is TWRP and how do I run a command??
Click to expand...
Click to collapse
My OPO did not go into boot loops. It died not reaching 0% of battery life, which is weird & able to boot up when I plug in the charger.
But, for those facing the same problem I faced, download 'Battery Calibration' app from play store (free). Your OPO need to be rooted. Today, my OPO worked normally. My batt is at 17% whilst writing this & it's still alive. Will continue to monitor these few days.
What is TWRP & how to run a command, see here: http://forum.xda-developers.com/showthread.php?t=2788632
boomsheklau said:
Google the following and you will find the instruction: How to fix One Plus One sudden death bug resulting in boot loops
but I don't know how to! Can anyone walk us through it? what is TWRP and how do I run a command??
Click to expand...
Click to collapse
I Had the boot loop today(out of the blue, didn't know why it rebooted in the first place), i thought was just a random boot loop because i had so many xposed modules installed but later i got to know it was because of the "persist" partition getting corrupted during the reboot. if you have this problem just do the following and you will be ok.
adb shell
make_ext4fs /dev/block/mmcblk0p15
Click to expand...
Click to collapse
source:http://www.androidpolice.com/2014/10/13/heres-easy-fix-oneplus-one-sudden-death-bug-results-neverending-boot-loops/
I've had exactly the same problem, twice now. The phone dies after being WiFi hotspot for some time; it isn't hot, it won't turn back on, it won't show charging.... both times I have managed to get it going again with persistence pressing the power button vol up or down with the power plugged in.
Given the age of the phone, perhaps the problem really is the battery; pity it isn't user replaceable (easily). Such a pity as it is a good phone, still, it seems to be abandoned now as I only have 6.0.1 with old security updates in Sept. 2016.
affinityvision said:
Such a pity as it is a good phone, still, it seems to be abandoned now as I only have 6.0.1 with old security updates in Sept. 2016.
Click to expand...
Click to collapse
Our OPO is far than being abandoned. Even if it will receive no more official CyanogenOS or OxygenOS updates, here at XDA you will find several Android 7.1.1 ROM alternatives.
I personally use TugaPowerN (based on Lineage OS 14.1).
Latest N25 build features Feb. 2017 Android security updates.
fastleo63 said:
Our OPO is far than being abandoned. Even if it will receive no more official CyanogenOS or OxygenOS updates, here at XDA you will find several Android 7.1.1 ROM alternatives.
I personally use TugaPowerN (based on Lineage OS 14.1).
Latest N25 build features Feb. 2017 Android security updates.
Click to expand...
Click to collapse
Well, that would be good, but it then matters how much work it will take to keep it up to date; and that would be a problem if the device itself continues to have occurrences of random shutdown. I'm doing a battery calibration, hope that helps, if it does, then I'll consider changing ROM from stock.
TugaPower ROMs are often and constantly updated. Not only Nougats, but even Marshmallow version.
IMHO even if discontinued, the above ROMs will be more secure than the latest original stock Cyanogen OS (13.1.2).
First stop using unofficial kernel. Return to stock.
Can someone please help me. After the 5.1.1 OTA update my phone randomly shuts off (like pulling the plug off an appliance). I already did the factory reset and it still has this problem.
I have the same problem, and the only way to switch it back on, is to plug it in the charger, wait for the battery icon to appear, and then try to switch it on.
It shut off twice while I was using the camera, and I thought it was caused by the HDR+ bug, but it also happened twice later, while idle in my pocket.
Anyone else seen this?
Android 5.1.1, stock, Rooted.
Sent using Tapatalk.
Same
I have the same problem. For the last two weeks it only crashed when I was using my camera. Yesterday it crashed while I used maps and gmail. This is very frustrating and have made the phone useless. I'm really surprised this has not gotten more attention.
I have seen people say that replacing the battery has solved the problem.
igimmi said:
I have the same problem. For the last two weeks it only crashed when I was using my camera. Yesterday it crashed while I used maps and gmail. This is very frustrating and have made the phone useless. I'm really surprised this has not gotten more attention.
I have seen people say that replacing the battery has solved the problem.
Click to expand...
Click to collapse
The battery has been replaced about a month ago.
I've used all the tricks I know, (wipe cache, dalvic, clear data from some core apps).
There seems to be no pattern to the lock-ups. It happened 5 times since last Saturday, when it first appeared.
God have mercy on our phones [emoji26]
Sent using Tapatalk.
kted said:
The battery has been replaced about a month ago.
I've used all the tricks I know, (wipe cache, dalvic, clear data from some core apps).
There seems to be no pattern to the lock-ups. It happened 5 times since last Saturday, when it first appeared.
God have mercy on our phones [emoji26]
Sent using Tapatalk.
Click to expand...
Click to collapse
Are you running 5.1.1?
I'm afraid to update my wife's Nexus 4 to 5.1.1.
Damn 5.1.1
I had no issues with 5.1.1, so you all probably should just flash factory images through fastboot.
I am with stock 5.1.1, rooted, xposed+gravitybox, after a clean install.
It worked fine at first, the random shutdowns started a week ago.
What annoys me most, is that after the shutdown, the only way to power on the phone, is to plug it in a charger. As soon as the battery icon shows, you can power on. It happened again a few hours ago, during a photo (with HDR+), and I had to wait till I returned home and plugged it in.
Sent using Tapatalk.
kted said:
I am with stock 5.1.1, rooted, xposed+gravitybox, after a clean install.
It worked fine at first, the random shutdowns started a week ago.
What annoys me most, is that after the shutdown, the only way to power on the phone, is to plug it in a charger. As soon as the battery icon shows, you can power on. It happened again a few hours ago, during a photo (with HDR+), and I had to wait till I returned home and plugged it in.
Sent using Tapatalk.
Click to expand...
Click to collapse
I wonder if we have to wait for an official bug fix from Android.
I have this same problem, I did have issues prior to the 5.1.1 update with having to press the power button 2-3 times OCCASIONALLY to present the lockscreen and have it stay on so unlock (it would present itself and go off the first few times). But that was a pretty intermittent problem, and not that annoying.
Now with 5.1.1 OTA instead of that issue, merely tapping the power button brings up the power off dialogue and the phone automatically shuts off. This seems to pop up every other day or so. Seems like a pretty horrid bug. Trying a cache partition wipe again now.
My Nexus 5 on lollipop has been all sorts of problems. I love the new design and changes, but reliability is gone to cow patties
HEY!!!
kted said:
I am with stock 5.1.1, rooted, xposed+gravitybox, after a clean install.
It worked fine at first, the random shutdowns started a week ago.
What annoys me most, is that after the shutdown, the only way to power on the phone, is to plug it in a charger. As soon as the battery icon shows, you can power on. It happened again a few hours ago, during a photo (with HDR+), and I had to wait till I returned home and plugged it in.
Sent using Tapatalk.
Click to expand...
Click to collapse
Xposed for 5.1.x is unofficial, even Official Xposed for 5.0.x is in alpha phase, so don't use it yet if you're aiming for stability.
igimmi said:
I wonder if we have to wait for an official bug fix from Android.
Click to expand...
Click to collapse
tesla45 said:
I have this same problem, I did have issues prior to the 5.1.1 update with having to press the power button 2-3 times OCCASIONALLY to present the lockscreen and have it stay on so unlock (it would present itself and go off the first few times). But that was a pretty intermittent problem, and not that annoying.
Now with 5.1.1 OTA instead of that issue, merely tapping the power button brings up the power off dialogue and the phone automatically shuts off. This seems to pop up every other day or so. Seems like a pretty horrid bug. Trying a cache partition wipe again now.
My Nexus 5 on lollipop has been all sorts of problems. I love the new design and changes, but reliability is gone to cow patties
Click to expand...
Click to collapse
Regardless, you all need to go back to stock, a fresh start, by flashing factory images from Google. I'm sure you know how to do it, so take your backups and go do it.
beekay201 said:
HEY!!!
Xposed for 5.1.x is unofficial, even Official Xposed for 5.0.x is in alpha phase, so don't use it yet if you're aiming for stability.
Regardless, you all need to go back to stock, a fresh start, by flashing factory images from Google. I'm sure you know how to do it, so take your backups and go do it.
Click to expand...
Click to collapse
The thing is it started all of a sudden, a week ago...
Sent using Tapatalk.
I'm going to run in SAFE MODE for a day and see how it goes. Maybe it's an app is not working well with 5.1.1 What I noticed that each time it shuts off ALL the apps have to be optimized again.
GripR said:
I'm going to run in SAFE MODE for a day and see how it goes. Maybe it's an app is not working well with 5.1.1 What I noticed that each time it shuts off ALL the apps have to be optimized again.
Click to expand...
Click to collapse
Safe mode didn't work for me.
My problem is not the same, it seems.
It happens one in every two times I take a photo with HDR+.
The phone switches off instantly, and the only way to switch it on again, is to plug it into a charger.
Sent using Tapatalk.
Safe mode didn't work...
I have the same issue.
Started like a week ago while came back from M preview to cataclysm. Was very frustrating and made a clean install of stock, reboot continued, more accurately it seems like a reboot with the Google logo, and then it turns off.
Happens with and without xposed.
What I have noticed though is that it happens much much less when WiFi is off.
Any updates on this?
Happens to me too. Just shuts of. Not like a reboot... just goes of. When I try to power it on again it begins to boot, but after a while on the bootanimation it shuts of again. Only If plug it in the charger it boot completely again. (mostly with optimizing all apps afterwards, but not every time. I also noticed that when maybe the battery is at 50 when it is shutting down, then after I plugged it in the charger for like 5 minutes and boot it, Battery is showing arround 90% already. (can't be, right?... ?)
So I think it's the battery, Imo.
Tomorrow I will clean flash the Google 5.1.1 stock factory image to check if it happens there too. If so then I have to send it in I guess...
I'm on BlissPop 5.1.1 + ElementalX atm, but tried many things already. Once without ElementalX, once with stock bliss kernel and a clean flash after factory reset. I even flashed the 5.0.1 bootloader and radio again + the 5.0.1 rom I used a few weeks before where everything was ok. (ExodusRom) but it happend too. So it almost must be the hardware (motherboard, battery etc.)
Greetings, Strainhunter
Gesendet von meinem Nexus 5 mit Tapatalk
strainhunter said:
Any updates on this?
Happens to me too. Just shuts of. Not like a reboot... just goes of. When I try to power it on again it begins to boot, but after a while on the bootanimation it shuts of again. Only If plug it in the charger it boot completely again. (mostly with optimizing all apps afterwards, but not every time. I also noticed that when maybe the battery is at 50 when it is shutting down, then after I plugged it in the charger for like 5 minutes and boot it, Battery is showing arround 90% already. (can't be, right?... )
So I think it's the battery, Imo.
Tomorrow I will clean flash the Google 5.1.1 stock factory image to check if it happens there too. If so then I have to send it in I guess...
I'm on BlissPop 5.1.1 + ElementalX atm, but tried many things already. Once without ElementalX, once with stock bliss kernel and a clean flash after factory reset. I even flashed the 5.0.1 bootloader and radio again + the 5.0.1 rom I used a few weeks before where everything was ok. (ExodusRom) but it happend too. So it almost must be the hardware (motherboard, battery etc.)
Greetings, Strainhunter
Gesendet von meinem Nexus 5 mit Tapatalk
Click to expand...
Click to collapse
I also think it's the battery. I will be be changing the battery soon. if there is any improvements after that I will provide update.
So today, my phone kept dying when the battery was around 40%. So I said screw it and got the battery replaced.
The old battery (on the right) looked bloated compared to the new one. The battery could have been the cause of all our problems.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi everyone, i know the title seems like it's just a trival matter, but trust me it's not.
The phone was bought new in August of last year (2015).
The story so far: I've been using sultanxda ROM for over 6 months without any issues, but i decided to test a different ROM, so i downloaded Darkobas rom and GAPPS, the ROM and Gapps installed fine but when i started the device and i was doing the initial configuration the phone rebooted by itself. It happened about 3/4 times and after that the phone had entered a bootloop. I tried to reflash the ROM and gapps, but the phone was restarting during the flash in TWRP. I decided to go stock Cyanogen OS, so i did a clean fastboot install of cyanogen OS. Everything went well the phone was working fine, but a few hours after installation the phone was randomly rebooting again, i decided i'll live with it and wait and see if it goes away by itself.
The phone was rebooting 2/3 times a day, during different acitivities so it was hard to pinpoint what might the issue be (even when locked in my pocket with all apps killed). After a few days of usage it just went straight to bootloop, after that i had issues to even install a rom (even via fastboot), because it would install everything fine and then it wouldn't start properly and would be in a bootloop (straight after installation).
I also tried the Bacon Root Toolkit installation as well as formatting everything and wiping everything. But even with the usage of Bacon Root Toolkit the random reboots happened.
So i installed an older TWRP recovery, i wiped everything re-formatted the phone to F2FS (was EXT 4 b4) and installed a F2FS compatible ROM (can't remember which one), after that installation everything seemed to work fine, but after a day or so the random reboots came back to haunt me again. So i reformatted the phone to EXT-4 again, installed stock cyanogenmod via fastboot (the 4.4.2 version), and updated it to 6.0.1 via OTA (during the course of a day or so, but even when the phone was on 4.4.2 i had a random reboot once), and the reboots returned ( i tried many different solutions, even the command line in TWRP "make_ext4fs /dev/block/mmcblk0p15"). I had NO IDEA what might be causing them but i thought that maybe the processor is ****ed and it's overheating, i returned to sultanxda rom (with the underclock to 1957 mHz).
After returning the phone booted correctly after a clean install via TWRP, but now it's rebooting again, and sometimes it happens 4/5 times in a ROW, sometimes it doesnt even reboot, but goes to black screen and I have to push the power button for 6 + seconds for it to reboot.
I've tried the stability test, or running antutu a few times in a row to verify if maybe it's the processor's/RAM's fault, but the phone didn't care, it rebooted randomly (sometimes 6/7 antutu runs in a row and nothing happened, sometimes rebooting in my pocket with all apps shut down). I've tried different launchers/messing with WiFi options/turning off the proximity check/turning off the trust agents nothing seems to make a difference. At this point I'm at a loss of what to do so i came here to ask for any advice. Is there any way to check if the phones internal memory is corrupted in some way ? I've tried searching for some apps but nothing turned out.
oski131 said:
Hi everyone, i know the title seems like it's just a trival matter, but trust me it's not.
The phone was bought new in August of last year (2015).
Click to expand...
Click to collapse
flash this solved my problem http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Flashed the persist.img the problem still occurs. 15 minutes after the flash the phone shutdown, black screen.
Your phone battery is dying...replace your phone battery and all the problem will go away....random reboot a couple of times and then goes straight to bootloop is a sign of a dying battery....trust me i know this cause it happen to me before and i'm sure you have the same problems....
this problems will get worst when you can only boot into your rom while your phone is connected to the charger and goes straight to bootloop when you disconnect the charger....
iPusak Gaoq� said:
Your phone battery is dying...replace your phone battery and all the problem will go away....random reboot a couple of times and then goes straight to bootloop is a sign of a dying battery....trust me i know this cause it happen to me before and i'm sure you have the same problems....
this problems will get worst when you can only boot into your rom while your phone is connected to the charger and goes straight to bootloop when you disconnect the charger....
Click to expand...
Click to collapse
Shouldn't the battery meter go crazy after reboots or something ? Well i guess i'll try this, the battery is not a costly component. Are there perhaps any bigger batteries than the original one with bigger backs ?
oski131 said:
Shouldn't the battery meter go crazy after reboots or something ? Well i guess i'll try this, the battery is not a costly component. Are there perhaps any bigger batteries than the original one with bigger backs ?
Click to expand...
Click to collapse
Nope...the battery remains like normal but random reboot will happen more regularly until bootloop....
Not sure if there is a bigger battery but there is one thread here that show one battery with 3600mAh and don't buy OP2 battery as it is not compatible with OPO...
Sent from my A0001 using Tapatalk
Ok thanks for the help, will report back with new battery.
Switched the battery, the random reboots still happen, decided to do a clean flash, after wiping the phone in TWRP during the flash of GAPPS the phone rebooted itself and is in a boot loop currently.
Ok so the reboots stopped, it was a battery issue, but now i have a problem with battery indicator it's stuck at 50 % all the time and the phone does not show when it's charging (no information, no LED color), but the battery is being charged because when i shut it down and connect the charge and battery level (which shows when the phone is off) increases.
I've tried to use it untill it shuts down then i charged it while it was off for 6 hours, but after turning it on it still showed 50 %. I've also deleted the batterystats.bin using TWRP but it still did not help. Any ideas how to make it show the correct % ?
oski131 said:
Ok so the reboots stopped, it was a battery issue, but now i have a problem with battery indicator it's stuck at 50 % all the time and the phone does not show when it's charging (no information, no LED color), but the battery is being charged because when i shut it down and connect the charge and battery level (which shows when the phone is off) increases.
I've tried to use it untill it shuts down then i charged it while it was off for 6 hours, but after turning it on it still showed 50 %. I've also deleted the batterystats.bin using TWRP but it still did not help. Any ideas how to make it show the correct % ?
Click to expand...
Click to collapse
told you it was a battery issues but look like you have another battery issues here...try disconnect the battery from the motherboard for 1 minutes before connect it again and do offline charge for atleast 30 minutes....after 30 minutes reboot the phone and look at the battery percentages...if its goes above 50% then you have solved your problems....if it doesn't then you might bought a bad battery....you need to contact the seller that sell you the battery and asked for replacement....
Well unfortunately after changing the battery for a second one (the random reboots started again on the new one) the issue still prevails, so i'm currently writing a ticket to oneplus in hopes of some help.
Thank you iPusak Gaoq™
iPusak Gaoq™ said:
Your phone battery is dying...replace your phone battery and all the problem will go away....random reboot a couple of times and then goes straight to bootloop is a sign of a dying battery....trust me i know this cause it happen to me before and i'm sure you have the same problems....
this problems will get worst when you can only boot into your rom while your phone is connected to the charger and goes straight to bootloop when you disconnect the charger....
Click to expand...
Click to collapse
You Sir iPusak Gaoq™ are amazing. I 've searched for 2 whole weeks and no one was able to zero in on the issue.
After reading your post, I changed my battery. 3 days back. Till now my phone is as good as new.
I cannot thank you enough. I tried everything from recovery to rom to stock.
Thank you Thank you thank you.
What peace of mind now !!!!!!!
You can try this it solved my problem without changing battery :-
https://forum.xda-developers.com/k5-plus/how-to/solving-random-reboots-problem-t3682037
My OPO is having a reboot issue, was on cos13, cm14.1 and ubuntu with mutirom,
Symptoms
1. the phone stays on if connected to a charger or powerbank.
and without charger it bootloops at the 1+ logo
2. in switched off state, when charger is connected the battery sometimes shows 0% and increases to 100%
3. with charger i entered cm recovery, removed the charger, the phone stayed all night long with cm recovery menu display on.
after draining the battery, i plugged back charger and the phone in switched off state did show the regular charging animation and took the usual time to full charge.
after full charge I removed the charger, tried to power on the phone boot loops at 1+ logo.
4. without charger it can enter fastboot mode.
5. with charger it can boot into os, shows charging, led lit up, but after removing charger it won't stay long, also if opening camera it turns off.
6. even on powerbank it can boot up and stay switched on. and work normally (camera etc anything)
(7. while turned off and on charger the animation shows charging but the top led isn't on.) - I don't remember it lighting up on charging while switched off
8. the night before this issue occured, my phone rebooted twice while watching youtube. and in the previous nights also I noticed battery dropping overnight.
what all I tried,
1. fastboot flashed cos, - not solved
2. flashed using Qualcomm USB port tool - not solved.
3. ran the make_ext4fs /dev/block/mmcblk0p15 command in twrp. - not solved.
4. erased and flashed persist.img - not solved.
so what could be the problem, opo is now my secondary phone, now using op3 as primary.
The battery is at its end of its life....replace the battery and all your problem will be gone...
you're not the only one that have experiences this problem (i have seen more then 10 people having the same problem)...last year and this year there a lot of people having bootloop problem due to dying battery...factory reset, flash stock rom and etc won't help you solved this problem...
i personally have this problem last year and after i replace the battery all my problem gone...i think Oneplus made OPO batteries only lasted for 2 and a half year....
iPusak Gaoq™ said:
The battery is at its end of its life....replace the battery and all your problem will be gone...
you're not the only one that have experiences this problem (i have seen more then 10 people having the same problem)...last year and this year there a lot of people having bootloop problem due to dying battery...factory reset, flash stock rom and etc won't help you solved this problem...
i personally have this problem last year and after i replace the battery all my problem gone...i think Oneplus made OPO batteries only lasted for 2 and a half year....
Click to expand...
Click to collapse
thanks for the reply i guessed that, but still wasn't sure, can it be also due to any issues to board, anyway since i've done with flashing and all i'll try an OP service center, and hope it won't costs me big.
jnraj said:
thanks for the reply i guessed that, but still wasn't sure, can it be also due to any issues to board, anyway since i've done with flashing and all i'll try an OP service center, and hope it won't costs me big.
Click to expand...
Click to collapse
Nope it is not issues with the motherboard but batteries...the phone can be turn on like normal when charger is connected and goes into bootloop once the charger is disconnected....its a clear sign that the battery is dying...when it connected to the charger, it may look like the battery is full but it is not...just buy a new battery and all your problem will be gone...you can try flashing lot of rom, revert to stock or whatever you do in fastboot but it ain't gonna help you...it might boot normally but within an hour it will goes back to bootloop....
like i said before i was on the same pages as you last year...all the flashing stuff didn't work until i replace the battery....there no issues with the motherboard whatsoever....my phone still work atm without any bootloop problem...
feel free to go to OP services center if you want, if they tell you it was a motherboard issues then you have been screwed by the services center by repairing something that is still in good condition and you gonna pay more then just a batteries afterwards...
iPusak Gaoq™ said:
Nope it is not issues with the motherboard but batteries...the phone can be turn on like normal when charger is connected and goes into bootloop once the charger is disconnected....its a clear sign that the battery is dying...when it connected to the charger, it may look like the battery is full but it is not...just buy a new battery and all your problem will be gone...you can try flashing lot of rom, revert to stock or whatever you do in fastboot but it ain't gonna help you...it might boot normally but within an hour it will goes back to bootloop....
like i said before i was on the same pages as you last year...all the flashing stuff didn't work until i replace the battery....there no issues with the motherboard whatsoever....my phone still work atm without any bootloop problem...
feel free to go to OP services center if you want, if they tell you it was a motherboard issues then you have been screwed by the services center by repairing something that is still in good condition and you gonna pay more then just a batteries afterwards...
Click to expand...
Click to collapse
I have almost exactly the same problem. The thing is I cannot find a way to enter multirom recovery even on a charger. When on a charger it tries to boot into my primary rom but gets stuck on it endlessly.
Are you sure its the battery? I mean, mine charges to 100% when plugged in and doesnt seem to have any problem with charging. Mine did it a few days ago, it went into a bootloop for no reason. I havent touched anything for a year and it happened so randomly and lost everything I had on it...
MetalmanIX said:
I have almost exactly the same problem. The thing is I cannot find a way to enter multirom recovery even on a charger. When on a charger it tries to boot into my primary rom but gets stuck on it endlessly.
Are you sure its the battery? I mean, mine charges to 100% when plugged in and doesnt seem to have any problem with charging. Mine did it a few days ago, it went into a bootloop for no reason. I havent touched anything for a year and it happened so randomly and lost everything I had on it...
Click to expand...
Click to collapse
Yes i'm sure of it...i have seen more then 10 opo user in my country that have the same problem as me and when they all replace the battery after my suggestion...all their problem go away without having reflash anything...
Sent from my A0001 using Tapatalk
iPusak Gaoq™ said:
Yes i'm sure of it...i have seen more then 10 opo user in my country that have the same problem as me and when they all replace the battery after my suggestion...all their problem go away without having reflash anything...
Click to expand...
Click to collapse
Hey dude Thanks a lot... I was facing exactly same issue for last 2 days... I bought OPO on Dec 5 th 2014... I think its battery only works 2 years...
@iPusak Gaoq™, tried to get a suitable battery online but the shipping charge killed most deals, some were even counterfeits, so finally I decided to visit an op service centre, they replaced the battery with a new one, now my OPO is good as new. thanks again.
I was just going to post, about my issue, but the forum suggested your post. I read the first post, and yes, I am facing the exact same problem. Taking a picture and the phone shuts off. Vibrating from getting a notification and restart.
And the saddest part, the phone won't boot into OS if is it not plugged to PC or AC power.
My Opo is almost two years old. Can you suggest a good battery replacement for me?
leokook said:
I was just going to post, about my issue, but the forum suggested your post. I read the first post, and yes, I am facing the exact same problem. Taking a picture and the phone shuts off. Vibrating from getting a notification and restart.
And the saddest part, the phone won't boot into OS if is it not plugged to PC or AC power.
My Opo is almost two years old. Can you suggest a good battery replacement for me?
Click to expand...
Click to collapse
Hard to suggest which batteries is good if you planning to bought it online cause there no way you can know whether the batteries you gonna buy is original or OEM...only when you bought the batteries in a retail store then you can see whether its original or OEM and yes the differences between both batteries is noticeable...
Sent from my A0001 using Tapatalk
Hello All, Don't know whether posting in right thread or wrong!....
My OPO is almost 3 years old, it is rebooting automatically i.e Powered by Android screen showing & then again it will restart with the same. Continuously rebooting the same until long press the power button for force shutdown. I need a solution , kindly help me out.
Am not an software engineer to understand the programming terms, hence if you share line to line steps, i can try..
Harishxda said:
Hello All, Don't know whether posting in right thread or wrong!....
My OPO is almost 3 years old, it is rebooting automatically i.e Powered by Android screen showing & then again it will restart with the same. Continuously rebooting the same until long press the power button for force shutdown. I need a solution , kindly help me out.
Am not an software engineer to understand the programming terms, hence if you share line to line steps, i can try..
Click to expand...
Click to collapse
Replace the battery of your Phone, it will be back to normal.
Changed battery but issue is sill there..
Will i found original battery at Ahmedabad Service Center
jnraj said:
@iPusak Gaoq™, tried to get a suitable battery online but the shipping charge killed most deals, some were even counterfeits, so finally I decided to visit an op service centre, they replaced the battery with a new one, now my OPO is good as new. thanks again.
Click to expand...
Click to collapse
as i m facing same issue since last sunday, i think i shall go to Oneplus Service center here in ahmedabad for replacement of battery, how much they charged for battery replacement.??
thanks..
samiran das 03 said:
Changed battery but issue is sill there..
Click to expand...
Click to collapse
you still having OPO? Did issue resolve?
Background information:
Oneplus 6 is rooted with magisk (but magisk hasn't been updated)
Able to charge and connect to pc as a Qualcomm modem
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My Oneplus 6 phone randomly after charging went black and was stuck in a bootloop, after a while I was able to escape the bootloop. Shortly after the screen goes black and now I am prompted with "Battery is too low" screen. After trying many other things of trying to recover the phone, such as: Fully draining the battery then charging it again, charging it for over 24 hours, to "trickle" charging the phone. I wasn't able to bring the phone back.
I don't really know if it this is a battery coordination error or an actual battery error. My goal is to try to recover the phone with no data loss, I've been looking around other forms trying to see how to recover data using QFIL of writing the storage then writing it back to the phone. I have also purchased a 64gb Micro SD card in hope of being able to recover the data using TWRP which I do have on my phone, but I am not able to acess recovery mode, because I am stuck in the "battery too low" screen.
Any help is appreciated. My current last resort option would probably be trying to "unbrick" the phone using MSM downloader tool. My goal here is to try to reserve the data on my phone and be able to hopefully revive my phone, because I don't believe I am in a hard brick.
I had a sucessful operation using MSM tool upgrading the os with "enchilada_22_J.50_210121.ops" but is still stuck in battery is too low.
it may be a stupid solution but have you tried pressing the power button for a while?
another solution can be addressed in physically removing the battery for a while. You'll need the glue or the new adhesive tape at least
Alex261099 said:
it may be a stupid solution but have you tried pressing the power button for a while?
another solution can be addressed in physically removing the battery for a while. You'll need the glue or the new adhesive tape at least
Click to expand...
Click to collapse
yes I have tried the first solution but I will try removing the battery, cause I was able to open my phone up
also do you mind linking me the page / link to where the person fixed it by removing the battery. I would like to try to follow his/her solution
From the photo you provided, your phone enters Emergency Download Mode (EDL mode)when connected to the computer so you may search for related data about EDL mode.
LR7875 said:
From the photo you provided, your phone enters Emergency Download Mode (EDL mode)when connected to the computer so you may search for related data about EDL mode.
Click to expand...
Click to collapse
Oh yea, I've already went through and finished with that incase I was in a boot loop, behind the battery is too low screen. I was successful in flashing stock rom onto my phone but I am still stuck in the battery is too low screen.
elangtales said:
Oh yea, I've already went through and finished with that incase I was in a boot loop, behind the battery is too low screen. I was successful in flashing stock rom onto my phone but I am still stuck in the battery is too low screen.
Click to expand...
Click to collapse
Then I cannot help you much but to make sure the battery is not the problem, you may have to replace the battery.
LR7875 said:
Then I cannot help you much but to make sure the battery is not the problem, you may have to replace the battery.
Click to expand...
Click to collapse
no worries appreciate the help, just trying to brute force anything now in trying to fix my phone.
elangtales said:
yes I have tried the first solution but I will try removing the battery, cause I was able to open my phone up
also do you mind linking me the page / link to where the person fixed it by removing the battery. I would like to try to follow his/her solution
Click to expand...
Click to collapse
Sorry i was busy with an exam.
I've had a similar issue on a Sony Xperia Z2 and a Sony Xperia Z3 and after disconnecting the battery I've managed to solve the problem.
the oneplus 6 it's simplier to disassemble but i would suggest you to change the battery as said by @LR7875, just in case.
Alex261099 said:
Sorry i was busy with an exam.
I've had a similar issue on a Sony Xperia Z2 and a Sony Xperia Z3 and after disconnecting the battery I've managed to solve the problem.
the oneplus 6 it's simplier to disassemble but i would suggest you to change the battery as said by @LR7875, just in case.
Click to expand...
Click to collapse
Replaced the battery but the same problem still persists. I was searching online and appearently oneplus phones have a chip to lock the phone from charging. Is there any way to bypass this?
elangtales said:
Replaced the battery but the same problem still persists. I was searching online and appearently oneplus phones have a chip to lock the phone from charging. Is there any way to bypass this?
Click to expand...
Click to collapse
Also able to do full process of MSMdownloadtool, is there anyway I can force charge from pc through the program. (seems pretty far-fetched)
elangtales said:
Replaced the battery but the same problem still persists. I was searching online and appearently oneplus phones have a chip to lock the phone from charging. Is there any way to bypass this?
Click to expand...
Click to collapse
Usually using a low Ampere (<1A) charger would solve the issue. Leave the phone connected in charge for 1h and let us know.
Alex261099 said:
Usually using a low Ampere (<1A) charger would solve the issue. Leave the phone connected in charge for 1h and let us know.
Click to expand...
Click to collapse
Is there anything to do after charging on a low Ampere charger? the faint red led is still showing on the phone.
elangtales said:
Is there anything to do after charging on a low Ampere charger? the faint red led is still showing on the phone.
Click to expand...
Click to collapse
Nothing still is happening, also tried removing the battery and the phone is still the same as before.
elangtales said:
Nothing still is happening, also tried removing the battery and the phone is still the same as before.
Click to expand...
Click to collapse
I don't know what to say...
You can try this last thing...
1.Remove the battery.
2. Unplug anything from the phone.
3.Using a paperclip or something made out of metal connect the positive and the negative battery connectors ON THE PHONE for a few seconds.
4. Reconnect battery.
5. Reconnect 1A 5V adapter.
DO NOT SHORT-CIRCUIT THE BATTERY! IT CATCHES FIRE AND EXPLODES!
Alex261099 said:
I don't know what to say...
You can try this last thing...
1.Remove the battery.
2. Unplug anything from the phone.
3.Using a paperclip or something made out of metal connect the positive and the negative battery connectors ON THE PHONE for a few seconds.
4. Reconnect battery.
5. Reconnect 1A 5V adapter.
DO NOT SHORT-CIRCUIT THE BATTERY! IT CATCHES FIRE AND EXPLODES!
Click to expand...
Click to collapse
My Phone was charging for a second when connected to my pc, but this was during my time off of the PC. If I were to recall the events to the best of my knowledge. I believe my phone was just plugged in (old battery), for a long period of time (1-5 hours) then after I turned off my pc for about (2-4 hours) and when I turned it back on it was charging but stayed at only 1% and unable to restart or anything. I wanted to try to recreate this with the new bought battery installed but I was unable to recreate this. I believe this confirms your theory before of charging it with a low ampere for an extended amount of time.
elangtales said:
My Phone was charging for a second when connected to my pc, but this was during my time off of the PC. If I were to recall the events to the best of my knowledge. I believe my phone was just plugged in (old battery), for a long period of time (1-5 hours) then after I turned off my pc for about (2-4 hours) and when I turned it back on it was charging but stayed at only 1% and unable to restart or anything. I wanted to try to recreate this with the new bought battery installed but I was unable to recreate this. I believe this confirms your theory before of charging it with a low ampere for an extended amount of time.
Click to expand...
Click to collapse
Alright, so please do the following:
-Unplug the battery for 1h (it will allow condenser to discharge).
-Plug-in the battery (the new one)
-Plug in the low-amp charger for one night (8h or so)
You'll have to try many times: even changing the order of the last 2 passages however it's not recommended to plug the charger first but in my case it worked.
NB. If it starts charging let it plugged until reaches at least 20%, boot the phone and switch with a 1A charger then power it off with the 1A charger.
Alex261099 said:
Alright, so please do the following:
-Unplug the battery for 1h (it will allow condenser to discharge).
-Plug-in the battery (the new one)
-Plug in the low-amp charger for one night (8h or so)
You'll have to try many times: even changing the order of the last 2 passages however it's not recommended to plug the charger first but in my case it worked.
NB. If it starts charging let it plugged until reaches at least 20%, boot the phone and switch with a 1A charger then power it off with the 1A charger.
Click to expand...
Click to collapse
Ill try this tonight and update ya if there is any change, thanks!
elangtales said:
Ill try this tonight and update ya if there is any change, thanks!
Click to expand...
Click to collapse
news?
just to share.
i charge a Op6 with this error together with a usb tester. and i find the amp jump when i press the power button. so i press the power & vol+ for around 5 min to warm up the low temp battery.... and it works!
but this trick doesnt work on my another 8 pro and 9 pro