Strange Battery Issue After May Update (3XL) - Google Pixel 3 XL Questions & Answers

A couple of weeks ago, my wife installed the May update (OTA) and since then her battery percentage is stuck at 5%. At least, that's what the phone reports. However, the phone does hold a charge as it normally did before the update was installed. We went about factory resetting the phone and starting over from nothing, yet the phone still shows only 5% battery remaining.
Anyone else experiencing anything similar to this?

brand0nYates said:
A couple of weeks ago, my wife installed the May update (OTA) and since then her battery percentage is stuck at 5%. At least, that's what the phone reports. However, the phone does hold a charge as it normally did before the update was installed. We went about factory resetting the phone and starting over from nothing, yet the phone still shows only 5% battery remaining.
Anyone else experiencing anything similar to this?
Click to expand...
Click to collapse
Try flashing the latest factory image. That should fix it.

wazza1991 said:
Try flashing the latest factory image. That should fix it.
Click to expand...
Click to collapse
Unfortunately, due to it being a verizon variant, I can't flash the factory image. And because the phone thinks its at 5%, it refuses to download/install the June update -- even when the phone is plugged in.

Related

OTA update bricked my phone?

I have recently updated to 4.3 using the software update option and my phone has been working fine for about a day. Tonight when I picked it up after charging it a bit, it was off. So I tried to turn it back on but nothing happened. Once I popped the battery out and put it back in, the Samsung screen showed up, and then for a few seconds the Galaxy S3 loading screen appeared. After that it shuts off completely. The only way to get it to turn on is by removing and reinserting the battery... Is there anyway to fix this? ( I have no modifications to my phone, it is completely stock)
MasonGL said:
I have recently updated to 4.3 using the software update option and my phone has been working fine for about a day. Tonight when I picked it up after charging it a bit, it was off. So I tried to turn it back on but nothing happened. Once I popped the battery out and put it back in, the Samsung screen showed up, and then for a few seconds the Galaxy S3 loading screen appeared. After that it shuts off completely. The only way to get it to turn on is by removing and reinserting the battery... Is there anyway to fix this? ( I have no modifications to my phone, it is completely stock)
Click to expand...
Click to collapse
Attempt a factory reset.
Aerowinder said:
Attempt a factory reset.
Click to expand...
Click to collapse
With me it was bricked immediately after the upgrade.
Factory reset doesn't help.
I am still trying to deal with this. Any idea will be welcome.
And if anyone has an image of the FOTA upgrade for the i9300 for me to try to re-flash, I will be grateful.
heliod said:
With me it was bricked immediately after the upgrade.
Factory reset doesn't help.
I am still trying to deal with this. Any idea will be welcome.
And if anyone has an image of the FOTA upgrade for the i9300 for me to try to re-flash, I will be grateful.
Click to expand...
Click to collapse
Ask in the i9300 section, anything in this section will be useless to you and most likely cause further damage to your phone.

Constantly rebooting (stock, nonrooted, no physical damage)

here's the background: galaxy s3, nonrooted, stock firmware, no physical damage that i'm aware of.
my friend's gs3 is constantly rebooting. essentially, it even reboots at boot up at any of the various splash screens during boot up and does not even boot up fully at all before it'll decide to crap out again. i figured that it may possibly be related to some rogue app so i told her to load up in safe mode but even then, the phone would reboot and attempt to restart again to ultimately fail and repeat. it did manage to boot up for a minute or two under safe mode yet it would restart again. i actually spoke to her last night but when she woke up, her phone wouldn't even stay on. after she had hung up, all she did was charge her phone and found it in it's current condition. we've attempted to remove the battery for a minute or so but the problem persists. the only other assumption was that there might have been an ota update that went bad. unfortunately i have a rooted gs4 so i'm not sure if there was an ota update for the gs3 that i wasn't aware of.
does anyone else have an idea on how to fix this or what may be the problem?
ender127 said:
here's the background: galaxy s3, nonrooted, stock firmware, no physical damage that i'm aware of.
my friend's gs3 is constantly rebooting. essentially, it even reboots at boot up at any of the various splash screens during boot up and does not even boot up fully at all before it'll decide to crap out again. i figured that it may possibly be related to some rogue app so i told her to load up in safe mode but even then, the phone would reboot and attempt to restart again to ultimately fail and repeat. it did manage to boot up for a minute or two under safe mode yet it would restart again. i actually spoke to her last night but when she woke up, her phone wouldn't even stay on. after she had hung up, all she did was charge her phone and found it in it's current condition. we've attempted to remove the battery for a minute or so but the problem persists. the only other assumption was that there might have been an ota update that went bad. unfortunately i have a rooted gs4 so i'm not sure if there was an ota update for the gs3 that i wasn't aware of.
does anyone else have an idea on how to fix this or what may be the problem?
Click to expand...
Click to collapse
there was an ota update a bit ago, 4.3...um, is it under warranty or does she have insurance, if so, go to the sprint techs and have them look at it, if not, what you can do/try for it is to completely flash the 4.3 ota update again using odin and download mode...you can do this by clicking on the 2nd link in my signature and see what happens, fixed my phone like this after 4.3 and myself messed it up lol and it's the exact same thing the sprint techs would do for it if you brought it in
so there's your options man...good luck, any questions just post up but the guide is very simple and straight fwd to follow and I provided all that is needed in my download bundle from my dropbox account
edit...if you can't boot up to enable the usb debugging mode, it should still work but it's recommended to do but again, shouldn't really matter, as long as it boots into download mode you should be ready to go
ender127 said:
here's the background: galaxy s3, nonrooted, stock firmware, no physical damage that i'm aware of.
my friend's gs3 is constantly rebooting. essentially, it even reboots at boot up at any of the various splash screens during boot up and does not even boot up fully at all before it'll decide to crap out again. i figured that it may possibly be related to some rogue app so i told her to load up in safe mode but even then, the phone would reboot and attempt to restart again to ultimately fail and repeat. it did manage to boot up for a minute or two under safe mode yet it would restart again. i actually spoke to her last night but when she woke up, her phone wouldn't even stay on. after she had hung up, all she did was charge her phone and found it in it's current condition. we've attempted to remove the battery for a minute or so but the problem persists. the only other assumption was that there might have been an ota update that went bad. unfortunately i have a rooted gs4 so i'm not sure if there was an ota update for the gs3 that i wasn't aware of.
does anyone else have an idea on how to fix this or what may be the problem?
Click to expand...
Click to collapse
This isn't an uncommon problem with the S3. I just recently went through this. In my case, and in many other cases, it's a faulty motherboard. Nothing you can do to fix it other than get Sprint to replace the handset.
For me, if I left it completely off for a long time, when I turned it back in it was stable for a couple of hours. Not sure if it was a coincidence, happened a couple of times that way.

[Q] Samsung Note N7100 stuck boot loop when unplug,but when charging loads the KitKat

Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Dennis_Arlo said:
Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Click to expand...
Click to collapse
Ive just encountered the same problem. Were u able to find a solution?
Shahin7631 said:
Ive just encountered the same problem. Were u able to find a solution?
Click to expand...
Click to collapse
I exactly encounter the same issue on my Note II. It seems that the automatic reboot (then the boot loop) when the phone is unplugged is generated with apps (or system) using internet connection or the camera.
Please help ! :crying:
Dennis_Arlo said:
Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Click to expand...
Click to collapse
I had a similar problem with my note 2 N7100.
It used to reboot every 30 minutes.
The best solution was to reinstall the firmware using ODIN.
First you need to download the firmware from sammobile and put the phone in download mode and install it.
Hope this solution helps you too.
anish100 said:
I had a similar problem with my note 2 N7100.
It used to reboot every 30 minutes.
The best solution was to reinstall the firmware using ODIN.
First you need to download the firmware from sammobile and put the phone in download mode and install it.
Hope this solution helps you too.
Click to expand...
Click to collapse
Thank you anish. I already tried this solution (with stock firmware and Cyanogenmod 10.3 &11) but it didn't work for me
The phone boot only happens when I unplug the USB cable and launch an app. If I do nothing after unplugging the cable the phone don't boot immediatly.
GStriker said:
Thank you anish. I already tried this solution (with stock firmware and Cyanogenmod 10.3 &11) but it didn't work for me
The phone boot only happens when I unplug the USB cable and launch an app. If I do nothing after unplugging the cable the phone don't boot immediatly.
Click to expand...
Click to collapse
Hi guys ! I finally found a temporary work around to avoid automatic reboot. After multiple tests I noticed that the issue seems to come from CPU usage.My phone never went to deep sleep and often stayed around 1600MHz.
The work around was to go to Preferences > Performances > Processor/CPU > Strategy select "userspace" . The CPU goes down to 800MHz but I don't have any more automatic reboot when the USB cable is unplugged.
After reboot the boot loop is still there (so I need to put back in the USB cable to boot normally). I was wondering if the boot loop comes from the boot.img file...
GStriker said:
I exactly encounter the same issue on my Note II. It seems that the automatic reboot (then the boot loop) when the phone is unplugged is generated with apps (or system) using internet connection or the camera.
Please help ! :crying:
Click to expand...
Click to collapse
Ive literally tried everything .even repartioned the phone . it works fine in recovery and download mode but as soon as i want too boot to android unplugged it restarts . when plugged it has no problem
Funny thing. I have a factory Sprint Note 2 with the latest kitkat updat and I am experiencing the same problem. Phone has not been rooted or messed with. If anybody come across a solution let me know. I booted the phone and unplugged the power button to verify and it does the same thing. Only stays on when in airplane mode or charging.
One more thing. I tried somewhat to do what was posted above about performance / cpu power. I put the phone in powersave mode and checked limit cpu and is is fully operation. problem gone. If I turn power save mode off I'm back to square one.
To late. Took a picture by mistake and phone jumped into boot loop.
i have GT-N7100 and same problem phone is stuck on boot loop when unpluged
---------- Post added at 04:22 PM ---------- Previous post was at 03:24 PM ----------
i just tought maybe it needs new battery. cause before i unpluged it it showed 67% then bootlooped 2x then i pluged back in and it shows me only 5%. i think its battery cause it cant dishcharge in 1 or 2min
My initial problems were that it would drop signal and show an x with no bars intermittently. then i started having problems anytime the phone demanded use. Picture, internet, video. tried a few things listed above. Still would go into a boot loop when not plugged in. Battery would charge normally and show it percentage like normal. It would reach 100% with no difference in charge time. When battery saver is on it would not have a problem unless I use an app that demands more cpu usage, network connection, battery consumption. Put a new battery and problem is gone. some people say the battery show swelling but my battery looks identical to the new one. no swelling and it is not deformed in any way.
It also solves the problem for me ...but i dont know what to do after the restart ...have u found a permenant solution
Shahin7631 said:
It also solves the problem for me ...but i dont know what to do after the restart ...have u found a permenant solution
Click to expand...
Click to collapse
I was thinking. If you flashed with a bad battery whats there to keep it from affecting the flash / update. The stock system doesn"t allow an update unless the battery is charged. It doesn't know if the battery is faulty. Try to reflash after a new battery has been reinstalled and charged to full. It's just a thought.
dcmobiletech said:
I was thinking. If you flashed with a bad battery whats there to keep it from affecting the flash / update. The stock system doesn"t allow an update unless the battery is charged. It doesn't know if the battery is faulty. Try to reflash after a new battery has been reinstalled and charged to full. It's just a thought.
Click to expand...
Click to collapse
Ive tried already with another battery ....its a very strange situation while everything works fine in download or recovery mode when its unplugged ...i have ordered a third party battery to see if it'll make a difference or not ....i'll keep u updated tomorrow
GStriker said:
Hi guys ! I finally found a temporary work around to avoid automatic reboot. After multiple tests I noticed that the issue seems to come from CPU usage.My phone never went to deep sleep and often stayed around 1600MHz.
The work around was to go to Preferences > Performances > Processor/CPU > Strategy select "userspace" . The CPU goes down to 800MHz but I don't have any more automatic reboot when the USB cable is unplugged.
After reboot the boot loop is still there (so I need to put back in the USB cable to boot normally). I was wondering if the boot loop comes from the boot.img file...
Click to expand...
Click to collapse
Where is the Preferences section? I am unable to find that on my Note 2 settings.
Experienced the same thing and this is the first time I had this. I was playing a game after I fully charged my battery and suddenly it turns off. So I waited for it to turn on where I noticed that it keeps on turning on and off and stuck on the " Samsung Galaxy Note 2" logo screen. Then I tried several things like clearing the cache and dalvik but it just do the same thing. I re-flashed the 4.4 ROM that I was using but sadly it does the same thing. I then noticed that if I plug in the charger it works normally and does not boot loop. And as soon as I remove the charger it will keep on restarting on and off on that screen. I was thinking that it might be a hardware failure or the battery itself. So I went to recovery mode and unplugged the charger, it stays on. Went to download mode without the charger and it stays on. Freakin' weird. I am about to flash a different ROM and will wipe everything and see what happens...
Fully charged the battery to 100%, unplugged the charger and it started to boot loop again. I allowed it to boot loop once and immediately went to recovery mode and saw that my fully charged battery went down to 3%. Tried different ROMS (Omega, DN3, and Phoenix), I still have this issue. Now can use my Note2 as long as the charger is plugged in...
Change your battery and solve the problem ?
Sent from my GT-N7100 using XDA Free mobile app
I did. Case closed!
red_hanks said:
I did. Case closed!
Click to expand...
Click to collapse
is it working fine after battery change? does it still get stuck in boot loop? mobile networks?
It works perfectly !

Endless Loop

My unlocked phone will only work if it is plugged into the charger.
If I unplug it it will go into an endless loop of the amazon start screen.
Stock rom and I just upgraded to the new firmware.
Please help!
Please help!
Can you access recovery?
updated below
not even the stock recovery?
I can access stock recovery only when the phone is plugged into the charger
Will not work if the phone is plugged into the computer via usb
xjakerobertsx said:
I can access stock recovery only when the phone is plugged into the charger
Will not work if the phone is plugged into the computer via usb
Click to expand...
Click to collapse
then this is out of my league.
xjakerobertsx said:
I can access stock recovery only when the phone is plugged into the charger
Will not work if the phone is plugged into the computer via usb
Click to expand...
Click to collapse
I'm guessing this means you have a faulty battery. The fact that it works on the charger and not unplugged or plugged in via USB is indicative the phone believes the battery is completely drained.
I would try to following before contacting Amazon for a warranty replacement: Try to factory reset from the Amazon Stock Recovery (assuming you're certain you are on FireOS). I would then let it charge turned off for a couple hours and try to turn on. If it works, great. If not, I'm afraid working with Amazon is your only avenue.
Any update on the case? I had the same situation. My fire phone having endless bootloop. Only if I connect to charger it can work.
Manage to go to recovery, wipe all, problem still persist.
Same thing
Went into stock recovery
Wipe the phone clean and it still gives me the endless loop
Anyone got an fixes for this? How can I pull all my pics off if this if it keeps rebooting
bump for help
blazin6969 said:
Anyone got an fixes for this? How can I pull all my pics off if this if it keeps rebooting
Click to expand...
Click to collapse
Try to charge your phone and turn it on. If can, you can use WiFi file explorer from play store to pull your data. Make sure fire phone and pc or laptop connect to the same WiFi.
Mine will goes to bootloop if direct connect to pc or laptop.
I just started having this problem yesterday, same exact symptoms. Wiping cache took an incredibly long time, factory reset went smoothly, but neither fixed the issue. It went in to another boot loop immediately after the reset completed, and only came out if it when I plugged it in to a charger again.
That said, it told me a little later that it had updated its firmware, congrats yada yada... and so far (fingers crossed) it hasn't acted up again.
It's now on Fire OS 4.6.6.1 (466001420), I couldn't say what it was before. Can anyone still experiencing this report what version you are on right now?
Also, it may or may not be relevant that I allowed the phone to charge for over 12 hours before disconnecting it.
Have you tried booting into stock recovery then pushing amazon update file to the phone via adb (adb sideload)?
sirkero said:
I just started having this problem yesterday, same exact symptoms. Wiping cache took an incredibly long time, factory reset went smoothly, but neither fixed the issue. It went in to another boot loop immediately after the reset completed, and only came out if it when I plugged it in to a charger again.
That said, it told me a little later that it had updated its firmware, congrats yada yada... and so far (fingers crossed) it hasn't acted up again.
It's now on Fire OS 4.6.6.1 (466001420), I couldn't say what it was before. Can anyone still experiencing this report what version you are on right now?
Also, it may or may not be relevant that I allowed the phone to charge for over 12 hours before disconnecting it.
Click to expand...
Click to collapse
Is it possible do to update you fix your issue? I had charge my phone for more than 12 hours but no luck...
I will try to update via sideload adb. If anyone can show me the link for the how to appreciate it.
Sent from my MI 4LTE using XDA-Developers mobile app
Update on mine:
The firmware update did not fix the problem. It is still possible that it alleviated the situation for a time, but much more likely it was just coincidental timing.
My Fire Phone behaved itself for most of a day and a half, then suddenly went back to the boot loop. I left it this way overnight to try to deep cycle the battery.
After draining completely, it took several hours on the charger before it began showing a charging screen, which comes and goes in intervals just like the Amazon logo had before. It has not progressed beyond 0% charge since then. I'm assuming a faulty battery at this point, or perhaps a corrupt battery stats file (but that should have cleared with the factory reset correct?)
My sincere apologies for any false hopes I may have given anyone.
sirkero said:
Update on mine:
The firmware update did not fix the problem. It is still possible that it alleviated the situation for a time, but much more likely it was just coincidental timing.
My Fire Phone behaved itself for most of a day and a half, then suddenly went back to the boot loop. I left it this way overnight to try to deep cycle the battery.
After draining completely, it took several hours on the charger before it began showing a charging screen, which comes and goes in intervals just like the Amazon logo had before. It has not progressed beyond 0% charge since then. I'm assuming a faulty battery at this point, or perhaps a corrupt battery stats file (but that should have cleared with the factory reset correct?)
My sincere apologies for any false hopes I may have given anyone.
Click to expand...
Click to collapse
It's OK mate, we all trying to find possible solutions for our problem.
Cheers.
Sent from my MI 4LTE using XDA-Developers mobile app
Solved replacing battery
I had this problem weeks ago, solved by:
1.- Drained battery to 0% (may skip this step? idk)
2.- Replaced battery for a new one (Search for one in amazon)
3.- Fully charged the new battery.
4.- Turned on fire phone.
cramosa said:
I had this problem weeks ago, solved by:
1.- Drained battery to 0% (may skip this step? idk)
2.- Replaced battery for a new one (Search for one in amazon)
3.- Fully charged the new battery.
4.- Turned on fire phone.
Click to expand...
Click to collapse
+1 for this.
I had this problem and just replaced battery. Fire Phone worked great again !
Can't believe a. faulty battery cause many problems.
Btw, if you replace battery by yourself, please notice the attached glue between battery and case. Try to remove them all gently - can search on YouTube how to replace Fire phone battery.

Question Bootloop when low battery

Since not so long ago I've experienced the following:
If I leave the phone two have low battery like 10% when it dies it enters a boot loop I cannot stop and I just can only plug it in and wait while it bootloops without being able to stop it and a long time later (20/30 min) it will finally boot up, last time it had 30% battery when it finally booted up.
What could it be? It may have been the last update? Has anybody experienced this?
If you did a major firmware upgrade without a factory reset, do a factory reset now.
Otherwise clear the system cache.
It it persists, factory reset.
If it still continues it maybe hardware. It could be corrupted firmware but trying to reflash may end up causing it to brick if it acts up during the reflash. Consider your options carefully at this point especially if under warranty or insured.
I have the same thing. The phone just starts to vibrate indicating a startup, then after a few seconds it vibrates again, and continues in this loop. The screen doesn't display anything.
I'm having the same thing right now, I tried wiping the cache from bootloader and charging the phone to 100%, but it doesn't seem to be fixed
Maybe on an unlocked bootloader it doesn't work? Something related to offline charging?
IronHulk27 said:
I'm having the same thing right now, I tried wiping the cache from bootloader and charging the phone to 100%, but it doesn't seem to be fixed
Click to expand...
Click to collapse
I have not had it happen lately the other day I had 5% battery and it worked fine.
I think it might be an unsupported charger?

Categories

Resources