2 days ago when charging my phone, my phone gave me a Battery Temperature warning and stopped charging the phone. I checked the Phone for overheating but it was cold not hot, I even used a temperature gun to check. I assumed It was just acting weird but eventually in the middle of the night when I went off to sleep It drained to zero. The next morning I plug it in assuming that it works now and no response from the phone, No vibrations, back light flicker, and no notification light. I tried entering Recovery, Nothing. I tried safe mode boot, Nothing. But ODIN/Download mode would work if only connected to usb. I tried flashing the latest firmware on the phone. It flashed successfully but didn't reboot. I tried flashing custom firmware but was blocked by FRP lock. Right now the phone is a paperweight and lifeless. Everything was backed up on Dec 8th online luckily, but I don't have the money for a new phone. Any help or tips?
Related
A few days ago my phone got soaked through my pants as I was working in the rain. I came home, dried it out, etc. and tried to turn it on. Wouldn't turn on, so I started charging it. I eventually got it to turn on and it seemed to be working fine except for some reason it said the battery life was at 0 %. Note that it was still working normally otherwise.
I went into recovery, made a backup, and did a factory reset to see if that would fix the problem. It didn't, so I restored the backup. Now the phone won't turn on at all.
When plugged in, it shows the charging battery symbol, and if you hold power to turn the phone on it will sometimes begin to start, but it gets to the boot animation and simply stays there forever (I've left it at the boot animation for several hours to no effect). If I try to boot into recovery it simply does not work; it will either just restart the battery charging animation or boot normally (and then get stuck on the boot animation).
In a last ditch effort, I was going to try to flash a stock ROM from Heimdall. However, I plugged my phone in and tried to enter download mode and was greeted with the error: "LOW BATTERY!! CAN'T DOWNLOAD!!." This was after charging the phone all night. I then proceeded to charge the phone for another hour then try again, to the same error. And now here I am. It seems the problem is that my phone will charge, and the battery will be full but for some reason the phone doesn't recognize that the battery has a charge, so it just thinks it's at 0%. I've tried a different battery and was unsuccessful. Is there any way that I can either force my phone to enter download mode or somehow get it to recognize the charge on the battery? Or is there some other way I could resolve this? Or is my phone simply gone for good?
I am (was) running a rooted I777 with Slim Bean ROM ( I believe v8) 4.2.
Have you tried using a JIG it can be an option
If a JIG doesn't work you can try removing the battery, then plug the phone to the PC and go to download.
But for me the problem is with the battery. If after flashing the ROM you get the same results, don't think it and BUY A NEW BATTERY.
Good luck.
Sent from my Nexus 7 2012.
If I'm bad at English is because I'm from Argentina and I'm learning.
I has the same problema, I spend two days searching on the web, but i didnt have any idea.., ,y problem is. when we conect to ANY charger (car/wall/PC-USB..) appears on screen a batery logo, but the batery never charged..., I tried to enter to the CW but, the keys combination doesnt make anything on the phone, and without live on it, I cant access to CW..., I wait for 2 hrs, with these cell phone conected to charger to see if the it gone works...
ANYONE has another idea for how we resolve these issue? My phone has a stable version of CyanogenMod..
same with me but what i did was put a different battery in, let it charge for a bit then put the original one in and it only started charging after i used my car charger as i was driving to work so thats how i fixed mine.
I rooted my phone with Cyanogenmod 11 (nightly) two weeks ago, it was fine, no issues. On monday morning phone was fully charged, but with very little to no use it was completely discharged in 7 hours. When I connected phone to a charger (original and working) it didn't want to turn on, it did NOTHING, black screen. When I borrowed battery from my brother's S2 wich was charged almost fully, it booted KitKat but it showed that the battery has to be recharged. I put it back to brother's phone but it showed only approx. 15% less than before, it was okay. I tried charging my phone with brother's battery, but it was incredibly overheating , not like when you play games, I was afraid it was going to blow up. It is overheating even when phone is turned off and charging or even when normally turned on, on battery. I tried enabling airplane mode, I even installed stock ROM with Odin, but it is still overheating. It is not overheating near the camera but on the left side of the screen, I don't know what that chip is there for. Stock ROM now gives me error after 2 min. saying "Charging paused, battery temperature too high." Now my battery is discharged and phone is unable to charge it, only black screen again. Could this be done by rooting it with Cyanogenmod ? it was the only ROM that I installed through the step-by-step process on their site and for couple of days it worked fine. Is this a hardware issue that would occur even if I wouldn't root my phone, also is it somehow fixable, or would I need to change motherboard completely ? PLS HELP !
Yuki8san said:
or would I need to change motherboard completely ?
Click to expand...
Click to collapse
That.
Hey, so, firstly I have a blue life one x. I love the phone and haven't had any problems until now.
I got an android update and my phone restarted, which has happened with the last two updates I got, so I didn't think anything of it. However, my phone was practically dead when this started and it restarted and got to the screen where it says "Android is starting... Optimizing application 1 of 143"
It would get to around 100 and turn off, restart and get to about 100 and turn off again.
I googled around and found a thing called bootloop. By what now seems to be a stroke of luck, my phone eventaully charged to about 40% and I got it to turn on and everything was fine but a few days ago, it died again and I ran into the same problem.
I went back to the boot loop instructions and tried it to no avail.
My phone has a fixed battery, so removing it wasn't an option. I left of the phone off the charger for 30 minutes and held the power button for two minutes(to discharge any remaining power?). Plugged it back in and it went right back to trying to boot back up and optimize apps.
I then removed the case, detached the ribbon that connects the battery to the board, held the power button for two minutes and let it sit for 3 hours. I connected the ribbon, plugged the charger back in and it instantly tried to boot up back into the optimizing screen and turned off.
I did all this again but left it for the past two days and now its back to rebooting over and over...
Things of note:
The light indicator turns red when the phone is connected to a charger, whether the battery ribbon is connected or not.
When it displays the blu splash screen, the optimizing applications screen, or recovery mode, the light indicator is off.
I can get into recovery mode, but I can't do anything before the phone turns off and reboots again.
Any help would be appreciated!
My Galaxy Alpha was completely stock and I only had a few 3rd party Play store apps installed. I had not done anything to the phone, no rooting (was unlocked from factory), no odin, no recovery mode, nothing.
I charged my phone overnight and used it when I got up. I left it on top of my bed and left the room.
I came back to get my phone and my wife said she found it under the blanket and that is was warm.
I looked at my phone and I saw the blue notification light was on. I hit the power button to turn the screen on but the screen did not respond. I reseated the battery but my phone is a brick.
Wifi was on and the phone was set to only update firmware on wifi but my phone was also setup to kill wifi if the screen was locked.
I will get a new phone but I would like to get my stuff off of my old phone.
Thanks!
svtfast said:
My Galaxy Alpha was completely stock and I only had a few 3rd party Play store apps installed. I had not done anything to the phone, no rooting (was unlocked from factory), no odin, no recovery mode, nothing.
I charged my phone overnight and used it when I got up. I left it on top of my bed and left the room.
I came back to get my phone and my wife said she found it under the blanket and that is was warm.
I looked at my phone and I saw the blue notification light was on. I hit the power button to turn the screen on but the screen did not respond. I reseated the battery but my phone is a brick.
Wifi was on and the phone was set to only update firmware on wifi but my phone was also setup to kill wifi if the screen was locked.
I will get a new phone but I would like to get my stuff off of my old phone.
Thanks!
Click to expand...
Click to collapse
Looks Like A Hardware Damage :/ Probably problem in display (Completely Turned Off) Due to short circuit or may be another reason but i am sure it is not a software side problem
A couple of days ago I replaced the battery on my Poco F1, because the phone is 2.5 years old and AccuBattery reckoned it was at 71% health. There were no issues with the phone, only that the battery life wasn’t as good as it once was (it was still running from 100% - 0% battery charge).
I bought the battery from AliExpress (this one to be precise) and the process of switching it out was easy and faultless, as far as I could tell.
The reassembled phone booted up fine and the new battery was at ~ 50% capacity. On the AliExpress listing it said to run the battery flat, which is what I did and it lasted quite a few hours - all good.
I then recharged the phone to full, as stated in the instructions. Regretfully, I interrupted the first recharge a couple of times by unplugging the phone for a few minutes each time. I'm telling you this for full disclosure - I'm unsure if this is likely to have caused the problem that I am now facing.
The fully recharged phone lasted a few hours and then shut itself down, whilst on ~ 70% battery I believe. This was the first time I realised there was a problem. The phone would not turn back on - holding down the power button and/or any combination of volume buttons did absolutely nothing. However, plugging the phone in caused the battery charging screen to appear instantly and subsequently, holding the power button whilst still plugged in would turn the phone on as normal. The phone would then boot up and battery percentage would be at ~70%, as it was when it shutdown (once booted, volume keys work fine). The phone would appear to charge as normal, but whenever I unplugged the phone, it would eventually shutdown on a high percentage after anything from a few seconds up to around an hour.
I thought I must have gotten a dodgy battery, so I took it out and put the original one back in. Now the old battery has all of the same symptoms as the new one – it won’t turn on unless plugged in and randomly shuts down after a period of time. If I manually turn the phone off when unplugged, it won’t turn back on unless it is plugged in. Also, a reboot just shuts it down.
I happened to have a spare charging port board, so I put that in to see if I’d fried something on there, but that hasn’t helped.
I’m tempted to reset the phone to stock (currently running Pixel Experience with TWRP installed) but am worried that it will brick the phone if it tries to reboot during the flashing process. Also, I believe that the fact I can’t force boot into fastboot with volume down/power buttons proves it is a hardware issue?
Any ideas are very welcome.
I think unless you have access to an EDL authorised account it's better to not flash MIUI at this stage. Risk of bricking the device...
07lema said:
A couple of days ago I replaced the battery on my Poco F1, because the phone is 2.5 years old and AccuBattery reckoned it was at 71% health. There were no issues with the phone, only that the battery life wasn’t as good as it once was (it was still running from 100% - 0% battery charge).
I bought the battery from AliExpress (this one to be precise) and the process of switching it out was easy and faultless, as far as I could tell.
The reassembled phone booted up fine and the new battery was at ~ 50% capacity. On the AliExpress listing it said to run the battery flat, which is what I did and it lasted quite a few hours - all good.
I then recharged the phone to full, as stated in the instructions. Regretfully, I interrupted the first recharge a couple of times by unplugging the phone for a few minutes each time. I'm telling you this for full disclosure - I'm unsure if this is likely to have caused the problem that I am now facing.
The fully recharged phone lasted a few hours and then shut itself down, whilst on ~ 70% battery I believe. This was the first time I realised there was a problem. The phone would not turn back on - holding down the power button and/or any combination of volume buttons did absolutely nothing. However, plugging the phone in caused the battery charging screen to appear instantly and subsequently, holding the power button whilst still plugged in would turn the phone on as normal. The phone would then boot up and battery percentage would be at ~70%, as it was when it shutdown (once booted, volume keys work fine). The phone would appear to charge as normal, but whenever I unplugged the phone, it would eventually shutdown on a high percentage after anything from a few seconds up to around an hour.
I thought I must have gotten a dodgy battery, so I took it out and put the original one back in. Now the old battery has all of the same symptoms as the new one – it won’t turn on unless plugged in and randomly shuts down after a period of time. If I manually turn the phone off when unplugged, it won’t turn back on unless it is plugged in. Also, a reboot just shuts it down.
I happened to have a spare charging port board, so I put that in to see if I’d fried something on there, but that hasn’t helped.
I’m tempted to reset the phone to stock (currently running Pixel Experience with TWRP installed) but am worried that it will brick the phone if it tries to reboot during the flashing process. Also, I believe that the fact I can’t force boot into fastboot with volume down/power buttons proves it is a hardware issue?
Any ideas are very welcome.
Click to expand...
Click to collapse
Exactly the problem I am going through. It's all started today. I am currently running stock MIUI. It keeps boot looping if I do not plug the charger. But once it's plugged, it will load up normal.
amn1987 said:
I think unless you have access to an EDL authorised account it's better to not flash MIUI at this stage. Risk of bricking the device...
Click to expand...
Click to collapse
I did flash stock MIUI in the end. Did not brick it, but also did not fix it. The phone now turns off immediately after being unplugged every time. I got myself a black Friday Poco X3 Pro so I'm now selling this phone for parts in UK
https://www.ebay.co.uk/itm/154819038771?mkevt=1&mkcid=16&mkrid=710-127635-2958-0
07lema said:
I did flash stock MIUI in the end. Did not brick it, but also did not fix it. The phone now turns off immediately after being unplugged every time. I got myself a black Friday Poco X3 Pro so I'm now selling this phone for parts in UK
https://www.ebay.co.uk/itm/154819038771?mkevt=1&mkcid=16&mkrid=710-127635-2958-0
Click to expand...
Click to collapse
It could be a buggy PMIC issue similar to https://forum.xda-developers.com/t/...android-11-0-vayu-bhima.4267263/post-85119331
Third-party batteries are mostly crap and probably the original battery is completely drained and the BMS isn't allowing it to be charged as a safety measure?
https://t.me/crDroidPoco/207293 Available in the EU.