[Q] my nexus 4 keeps shutting off :( - Nexus 4 Q&A, Help & Troubleshooting

After i downloaded android 5.1 my nexus 4 keeps shutting off and most of the time its doesnt turn on until i plug it in the charger i tried alot of roms after i thought its a software problem but none of them worked :/ please somebody tell me what to do it shuts off even when its 80% battery and when i turn it on the battery is 5 or 10% :/

This could be a battery problem. I would recommend flashing stock android (from google's website), then re-locking the bootloader. Then, send your phone in for repairs. If this doesn't work, then I don't know.

Related

[Q] Help with nexus 7 battery issue!

Hello people!
I've had my Nexus 7 for about 4 months now, and it started having battery problems a couple of weeks ago.
After the battery had drained completely, it wouldn't charge at all. I followed some steps to solve this problem, and managed to get it up again, but after that, charging it has been a nightmare.
To sum up:
When my tablet is on and plugged in, it shows that it's charging, but the battery slowly drains even if I don't use it for hours. If the tablet is off and plugged in it shows that it's charging, but it is not.
After it's completely drained, I have to go through the whole recovery mode, turn off, thirty second button push process to revive the tablet (which otherwise does not work at all) and let it charge while off. After that the tablet works fine, but does not charge.
I even did a factory reset, but nothing happened. Also I'm using the charger that came with the tablet.
Should I ask for a new one with my Guarantee or is there a fix for my problem?
maybe its some internal issue, if it came with a warranty. maybe go to the place where you bought it and see if they will replace it with a working N 7.

[Q] Nexus 4 will boot unless connected to a charger

My son have a nexus 4. Not rooted and an original rom. Since he updated to lollipop the phone had gone crazy. Bootting is not good and the phone hase a life of his own. We reveterd back to kitkat and now the phone will not boot unless it is connected to the charger. I have no ideas as to what had gone wrong.
if i leave the phone off for 3 days it boots up nicely but after several restarts it will not boot again. I am sick of the 4 dancing balls. I put in a new battery and no good.
Pls advise as to what could be the problem

Phone wont lasted 10 seconds without plugging in ,But not battery problem.

Hello guys, this is my first time posting up in XDA and I am encountering a very weird problem with my N4
Disclaimer, the following is a long write but please bear with me and give a read.
Here's my problem after flashing the simple asop 29/5 build for mako. I come from same rom build 21/5 but i did a clean flash for the latest build. As soon as success flashing the latest build with gapps, then as usual will proceed reboot the system. Just right before the boot animation, the phone immediately went dead. I am sure that the phone is still left with 50%+ of battery at the moment.
Anyhow, I decided to plug it into charger. And voila, the phone now able to go through the boot animation and everything just fine. After setting up and restoring backups, I unplugged the charger, its 75%+ on the battery. Within 10-15 seconds, the phone immediately go dead again. I hit the power button and tried to boot up. Again, right after the Google logo screen, the phone went dead.
Commonly this indicate a problem with the battery. Yeah, but I went into recovery twrp and disabled the screen timeout & max the brightness. Guess what, surprisingly it lasted more than an hour which proves that this wasn't battery fault.
What had I tried so far, is just switched off the phone and plugged into charge for 2 hours. And obviously it doesnt solve the problem. I am backing up all the data at the moment and plans to drain the battery all the way down just leaving it screen on at recovery.
Anyone who know what happening with my n4 or encounter similar experience, please feel free to share the solution. Many thanks 
Jz Chong said:
Hello guys, this is my first time posting up in XDA and I am encountering a very weird problem with my N4
Disclaimer, the following is a long write but please bear with me and give a read.
Here's my problem after flashing the simple asop 29/5 build for mako. I come from same rom build 21/5 but i did a clean flash for the latest build. As soon as success flashing the latest build with gapps, then as usual will proceed reboot the system. Just right before the boot animation, the phone immediately went dead. I am sure that the phone is still left with 50%+ of battery at the moment.
Anyhow, I decided to plug it into charger. And voila, the phone now able to go through the boot animation and everything just fine. After setting up and restoring backups, I unplugged the charger, its 75%+ on the battery. Within 10-15 seconds, the phone immediately go dead again. I hit the power button and tried to boot up. Again, right after the Google logo screen, the phone went dead.
Commonly this indicate a problem with the battery. Yeah, but I went into recovery twrp and disabled the screen timeout & max the brightness. Guess what, surprisingly it lasted more than an hour which proves that this wasn't battery fault.
What had I tried so far, is just switched off the phone and plugged into charge for 2 hours. And obviously it doesnt solve the problem. I am backing up all the data at the moment and plans to drain the battery all the way down just leaving it screen on at recovery.
Anyone who know what happening with my n4 or encounter similar experience, please feel free to share the solution. Many thanks 
Click to expand...
Click to collapse
Have you tried making a clean wipe and trying either stock or another ROM, to see if it works then?
Your test doesn't prove it's not the battery's fault. Flash back to stock, see if the problem persists and if it does then you know you have a hardware problem. Could be the battery.
DrFredPhD said:
Your test doesn't prove it's not the battery's fault. Flash back to stock, see if the problem persists and if it does then you know you have a hardware problem. Could be the battery.
Click to expand...
Click to collapse
Hello, much appreciate your reply. I flashed back to stock 5.1.1 now and yet this problem is still persisting. Thus pretty obvious thats an hardware faulty.
In another forum, a guy with Nexus 7 had similar situation as me, and he suggests that its the battery or the circuit board at the charging port went kaput.
Guess nothing else I could do right now, gonna send in the phone for repair and hope the bill wont cost as much as a used nexus 4

Note 4 n910f battery charge stuck

Hi all my gf just bought a brand new note 4 it's came with lollipop and it charged fine however I updated it to marshmallow through the manual update and since that it won't charge past about 78%.. I them have to remove the battery reinsert it and then charge the rest with the phone turned off till 100%..
I've read on another forum that it's seems a problem with the marshmallow update. I've tried clearing the cache by booting into the recovery but made no difference.
Anyone know how to fix this.. would using a custom rom do it been thinking off putting one of the note 7 ports on it for her.
At the moment everything is fully stock no root and still got know
Thanks
Calibrate it. Empty it completely and then charge it again
Thanks will try it. Does the phone have to be on or off for charging after I've emptied it
I drained the battery till it wouldn't turn back on left it off while charging and it got stuck at 73% have to keep disconnect and reconnect the charger to get it to charge more

Note 4 total shutdown. Any possible reasons?

We all know that since the stock marshmallow update everything has gone mad with the note 4.
My situation was when I was going home i had 52% battery and it kept discharging so fast that around 20% it just turned off.
After i got home for about 2 hrs, i tried charging the phone and it wasnt charging and was not turning on. No vibrations no anything.
So i decided to borrow a friend's note 4 to use its battery on my device, thinking that my battery was just damaged. But again it did not power on.
Tried connecting the phone to adb after pressing long to the power button and still cannot be detected.
Is this bricking due to the marshmallow update? And if so, how do you fix this problem?
trevourlance27 said:
We all know that since the stock marshmallow update everything has gone mad with the note 4.
My situation was when I was going home i had 52% battery and it kept discharging so fast that around 20% it just turned off.
After i got home for about 2 hrs, i tried charging the phone and it wasnt charging and was not turning on. No vibrations no anything.
So i decided to borrow a friend's note 4 to use its battery on my device, thinking that my battery was just damaged. But again it did not power on.
Tried connecting the phone to adb after pressing long to the power button and still cannot be detected.
Is this bricking due to the marshmallow update? And if so, how do you fix this problem?
Click to expand...
Click to collapse
Does it boot to download mode?
I'd take your device to a Samsung Service Center and let them take a look at it.
trevourlance27 said:
We all know that since the stock marshmallow update everything has gone mad with the note 4.
My situation was when I was going home i had 52% battery and it kept discharging so fast that around 20% it just turned off.
After i got home for about 2 hrs, i tried charging the phone and it wasnt charging and was not turning on. No vibrations no anything.
So i decided to borrow a friend's note 4 to use its battery on my device, thinking that my battery was just damaged. But again it did not power on.
Tried connecting the phone to adb after pressing long to the power button and still cannot be detected.
Is this bricking due to the marshmallow update? And if so, how do you fix this problem?
Click to expand...
Click to collapse
Have a look under the thread "Note keeps freezing and restarting" there's a lot of information there! I am using the app mentioned on the "partial wake lock" option and so far it seems to be OK!

Categories

Resources