[Q] Nexus 5 shutdown immediately after boot - Nexus 5 Q&A, Help & Troubleshooting

Any ideas on why this is happening to my phone?
Attached is a logcat of the phone at boot before I did a full wipe. The problem still persists after wiping.

Now i noticed it is not charging, any ideas?

are you 100% stock?

Yes. only rooted the device

Try using another usb cable, if your device isn't even charging that could be one of the issues. A 2nd option is to let it charge while its powered off then after a half hr to an hr power it back on

I've identified the issue to be a faulty temperature sensor readings.
Is there anyway to ignore the readings or override them?
I've edited thermal-engine.conf but it does not solve the issue

Related

Battey shows "Unknown" and always at 0%

HI,
Looking for some help to get my nexus 5 working. The phones battery indicator is always at 0% not matter what I’ve tried (I’ve played youtube for like 3 hrs so I know there is juice in the battery)
[*]Whats wrong :
The phone battery indicator is always showing that it needs to be charged.
The phone battery indicator is always at 0%.
Settings -> Battery shows battery as “Unknown”
When powered on the screen does not show anything (you can tell its on cuz it connects to the computer. The battery cable has to be disconnected and reconnected as mentioned below to get the screen and phone working.)
Things done with no results
Swapped batteries from a working nexus.
Reinstalled stock ROM (L)
Left to charge overnight.
Cleaned cache from Recovery Mode
Used app to recalibrate the battery
The phone itself will boot up with a blank screen. I have to unplug the battery connector and then plug in the power USB. At this point it only shows the battery with flash. Its on for some seconds and the reboots over and over again.
I get it to work by connecting back the battery to the main board during one of the loops. (Sometimes holding the power +Volume up to get to the google display and then connecting)
Any help ??
When you installed L did you use the Google flash all bat file?
Sent from my Android L Nexus 5 via Tapatalk
Yes ..I ran the flash-all.bat
The phone itself was in Kit Kat when I got it with this issue. I tried it with L to see if the issue would go away.
Other than flashing 4.4.4 clean...with wipes and seeing how it is...it could be a hardware issue unfortunately.
You've discovered the holy grail of infinite battery usage? I'm not seeing any issue here. JK, it's probably a bug in the preview software as can be expected.
Could be a bad battery as well.
already tried that as well.
The phone boots up to a blank screen. Only way to see anything on the screen is to unplug and replug the battery wire. Then everythings normal up until you have to restart.
nevermindzz00 said:
already tried that as well.
The phone boots up to a blank screen. Only way to see anything on the screen is to unplug and replug the battery wire. Then everythings normal up until you have to restart.
Click to expand...
Click to collapse
I am on the same page. My Nexus is showing same results. I have also replaced the battery with a new one. Only one thing different in mine, I started noticing signal drops then the radio completely started to went off. Now the battery is at 0% always whenever I get it to boot that is. Otherwise it's blank with vibrations.
A fix is in great need. Also, I have tried multiple ROMs right now I am on the latest L Build.
Can you replace your flex cable with a working Nexus and write the results? I think it might fix it from the hardware side. Where I live, the flex cable isn't available! :-/

5.1 random crash and "imaginary" battery drain

Hi guys, I'm hoping someone can help..
For the last few weeks my Nexus 5 has been randomly crashing, this has progressively worsened. The phone crashes and completely shuts off, one second it will be working the next it will be off. When I turn the phone back on it thinks the battery is almost completely drained and, when the problem wasn't as bad, the battery level would slowly increase when left.
Now the problem has increased that, when it crashes, the phone will either not fully boot or crash again very soon after starting. The only way to keep the phone on it to have it plugged in, this also seems to prevent the crashes.
I have factory reset the phone and reflashed the latest factory image. I am also rooted.
I've attached two logcat files that I started recording before the phone crashed.
Any advice on how to fix this issue would be appreciated.
Thanks
slightperil said:
Hi guys, I'm hoping someone can help..
For the last few weeks my Nexus 5 has been randomly crashing, this has progressively worsened. The phone crashes and completely shuts off, one second it will be working the next it will be off. When I turn the phone back on it thinks the battery is almost completely drained and, when the problem wasn't as bad, the battery level would slowly increase when left.
Now the problem has increased that, when it crashes, the phone will either not fully boot or crash again very soon after starting. The only way to keep the phone on it to have it plugged in, this also seems to prevent the crashes.
I have factory reset the phone and reflashed the latest factory image. I am also rooted.
I've attached two logcat files that I started recording before the phone crashed.
Any advice on how to fix this issue would be appreciated.
Thanks
Click to expand...
Click to collapse
It's normally an issue with the battery. When the device thinks the battery is dead (due to sudden voltage drop probably), it shuts down.
Aerowinder said:
It's normally an issue with the battery. When the device thinks the battery is dead (due to sudden voltage drop probably), it shuts down.
Click to expand...
Click to collapse
Thanks for replying. Does this mean if it have the battery repaired/replaced that the issue should go away? Are there any apps anyone could recommend to check if the voltage is the issue?

Nexus 5 won't charge the battery, shows -30degrees and cold temp

Hey All,
i have a nexus 5 running android 5.1.1, which recently i have encountered some battery issues, the battery drained very fast (6-7 hours from 100% to 0%).
but then, it stopped charging the battery, no matter what i changed - nothing worked! (new cables, different chargers and so on).
yesterday i have bought a new battery and replaced the original faulty battery, but nothing is changed, the new battery won't charge.
i tried to charge it when the nexus is on or off, doesn't matter, same result...
i am very frustrated from the situation, and basically can not use the nexus any more..
one more thing, i tried also google suggestion (when the cell is off, to press power+volume buttons, and then scrolling down to shut down and inserting the charger - >didn't work for me).
i tried to upgrade to Marshmallow (6.0.1) but there is not enough battery power to allow it...
when i dial *#*#INFO#*#*, and check the battery properties,
why the temp is always -30 degrees for the two batteries?
Is it a sensor issue?
do you have any suggestion?
Thanks!
anyone?
i will really appreciate your suggestion..
Connect the phone to a Windows machine and look to see if any new devices appear in Device Manager.
Thanks for the reply.
I connected the nexus to my laptop, it was recognized and i could reach the storage, but the battery remained the same, not charging ..
So the nexus 5 appears in Windows explorer? Possible charging port problem?
audit13 said:
So the nexus 5 appears in Windows explorer? Possible charging port problem?
Click to expand...
Click to collapse
well, maybe. havn't tried it so far..
have you encountered this issue of wrong temp alert of -30 degrees for other users ?
and replacing the charging port solved it?
I haven't encountered the battery temp issue.
Since the old and new battery behave the same way, there wouldn't be too many culprits which is why I mentioned the USB charging port. Has the ever been dropped? Any way you could test the batteries in another phone?
the problem was resolved!!!
finally, after so many hours trying to make it work, i encountered a thread here in XDA which explains that the sensor is located on the cable connecting the battery to the motherboard.
Apparently it was a bit loose, so i put something above the connection and put the cover tightly.
then, the temp was reasonable again and my nexus was coming back to live!
:laugh::laugh::laugh::laugh::laugh:
Same problem
gorzany said:
Hey All,
i have a nexus 5 running android 5.1.1, which recently i have encountered some battery issues, the battery drained very fast (6-7 hours from 100% to 0%).
but then, it stopped charging the battery, no matter what i changed - nothing worked! (new cables, different chargers and so on).
yesterday i have bought a new battery and replaced the original faulty battery, but nothing is changed, the new battery won't charge.
i tried to charge it when the nexus is on or off, doesn't matter, same result...
i am very frustrated from the situation, and basically can not use the nexus any more..
one more thing, i tried also google suggestion (when the cell is off, to press power+volume buttons, and then scrolling down to shut down and inserting the charger - >didn't work for me).
i tried to upgrade to Marshmallow (6.0.1) but there is not enough battery power to allow it...
when i dial *#*#INFO#*#*, and check the battery properties,
why the temp is always -30 degrees for the two batteries?
Is it a sensor issue?
do you have any suggestion?
Thanks!
Click to expand...
Click to collapse
Hey, I have the same same problem , what did you do to fix it? I've been almost a year without using my nexus because it only works when it's plugged. Can you tell me what thread did you read or the solution? Thank you
See my last post....
Anyway, The problem was at the connection port of the battery - when you remove the nexus cover, you will see that the battery is connected by a connector with 9-10 pins to the board. Apparently those pins weren't connected properly and were loose, so I put something from above to make some pressure on the connector, then screw back everything and close the cover. Since then, my nexus is working great!
I hope it will work the same for you...

Phone not charging above 0%

Hey guys,
I am having the issue that my OPO is not charging. It remains at 0% when plugged in indefinitely. As soon as I unplug the charger it will turn off immediately. When plugged in, however, it functions perfectly fine. I reset the phone and also tried different ROMS but I am assuming some hardware issue because switching ROMS or using a different charger and cable did not help. I assumed a faulty battery, so, I replaced the original battery but also that does not fix the issue. Did you experience a similar issue? I know that some hardware part is very likely not working properly but which one is it? Thanks in advance. I am hoping someone can help!
No idea dude..
My OPO works fine with the stock battery even after 4 & half years also gives 4.15hrs of screen on time.

Phone only charges in recovery mode

I have a moto g6 I used a while ago. I upgraded my phone when it stopped charging. I thought it was the USB-C port, and moved on to a new phone.
I just took the old phone out again and booted into recovery mode this morning. I plugged it in and it charged (in recovery mode). It trickle (slow) charged for most of the day. I then booted the phone up about 2 hours ago and it was mostly charged.
I tried plugging the charger back in, and again..... no charging.
I booted back into recovery mode and alas. Charges. Albeit slowly.
It only charges when it's booted in recovery mode. Any thoughts?
<bump>
⌐(ಠ۾ಠ)¬
Does it charge when powered off?
Nope. When it's powered off, it will start powering up as soon as I plug it in. If the battery is full, it just boots up the phone when I plug it in. If the battery is dead, it will show the boot logo, battery 0%, and restart. On loop.
It only charges/detects there is a charger plugged in when booted into recovery mode.
blackhawk said:
Does it charge when powered off?
Click to expand...
Click to collapse
zaep0b said:
Nope. When it's powered off, it will start powering up as soon as I plug it in. If the battery is full, it just boots up the phone when I plug it in. If the battery is dead, it will show the boot logo, battery 0%, and restart. On loop.
It only charges/detects there is a charger plugged in when booted into recovery mode.
Click to expand...
Click to collapse
You mean when it's been completely powered off ie shutdown it boots up by itself up when you plug in the charger?
Completely power off the phone and try the charger.
Sorry, just tested again and I'm wrong, slightly.
When I plug it in while turned off, it will show the lightning icon, then a battery percentage, then restart. It never boots up by itself when plugging it in.
blackhawk said:
You mean when it's been completely powered off ie shutdown it boots up by itself up when you plug in the charger?
Click to expand...
Click to collapse
zaep0b said:
Sorry, just tested again and I'm wrong, slightly.
When I plug it in while turned off, it will show the lightning icon, then a battery percentage, then restart. It never boots up by itself when plugging it in.
Click to expand...
Click to collapse
Are you commanding it to restart ie hitting the power button?
If not it's either a firmware failure or more likely a hardware failure.
Self-restarts. Without any action on my part. It just shows the current battery % and then boot loops.
I had the USB port tested at one of those 'fix your phone' places (when the problem first occurred) and they said the USB port is fine and it's something else causing the problem.
I just find it super strange that in recovery mode, it will actually charge. I had given up on this device and I'm using a new phone now, but the fact that it charges in recovery makes me want to get this thing back up as a spare.
I spent a LOT of time on google for this and I have not found any useful information or ideas.
blackhawk said:
Are you commanding it to restart ie hitting the power button?
If not it's either a firmware failure or more likely a hardware failure.
Click to expand...
Click to collapse
Try a factory reset if stock.
Reflash firmware to known stable version.
Hopefully that will fix it but don't count on it.
If that doesn't get it than it's a mobo failure or less likely an issue with a connector.
Depending how it's laid out it could be a failure in a subassembly rather than mobo.
Sorry...
Epic necro, but wanted to reply to say I have the exact same issue with a Oneplus 5T right now. But I think I can add one note: I installed AccuBattery and that shows that the phone *does* charge when connected under Android (even though the charging icon doesn't show), but very slowly; it's charging at 500mA, which I believe is the base USB spec max for power transfer.
In typical use it's entirely possible you consume more power than that, so the battery percentage would still drop and the phone wouldn't appear to be charging. I suspect it's actually doing the same in recovery mode, but recovery mode uses much less power - so 500mA is actually enough to trickle-charge it - and does show the + sign to indicate charging.
I haven't found any fix yet either I do suspect blackhawk is right and it must be a hardware issue. I'm gonna take it to some repair places and see if I can avoid a big replacement bill.
Is the battery good? Or is SOT short?
Could be a failed battery.
Any swelling is a failure.
Erratic fast charging is a symptom of a battery failure.
Li's can fail at any time in their life cycle.
Typically in a heavily used device they last 1-2 years. When they reach 80% of their original capacity they have reach the end of their service life, are degraded and should be replaced. A degraded Li is more likely to fail.
An easy fix if so.
Nope, already replaced the battery not long ago. It was indeed the port: took it in for repair and the guy said the trace connecting the port to the motherboard was basically gone, probably wear/damage over time (this phone is five years old and has been dropped a few times). He fixed that and it's back to charging like a champ and connecting to PCs fine again. So, if OP is still trying to fix their G6, might want to try a different repair shop...
Actually its a software bug. Factory reset ur device from recovery mode may problem will be solve.

Categories

Resources