Nexus 5 dead for good? - Nexus 5 Q&A, Help & Troubleshooting

Hi all, I'm stumped.
My phone won't stay on. Screen goes black after some time (seconds or minutes). It seems to last longer if I let it sit for a while before trying to turn it on. Same behavior in recovery mode. My cache is probably corrupted (see below), but I don't think that's contributing to the bigger problem. Help?
Full story: On Friday (August 25) I woke up to find my Nexus 5 powered off (while on charge). I couldn't get it to turn on, either. With many attempts, it occasionally starts to boot, but then the screen goes black before it finishes booting. I tried booting to recovery and clearing the cache partition, but the screen went black and I presumably now have a corrupted cache as well. My battery has been underperforming for a long time now, so I thought perhaps the battery is finally toast. I ordered a replacement battery (from Encompass), and swapped it out today (August 30). When I put it on charge, I saw the half-full battery indicator, which is the first time I've seen it since before it died on Friday. I left it on charge for about 3.5 hours. I then booted to recovery and attempted to format the cache partition again. I know it can take a long time, so I left it be, and after probably five or ten minutes, I noticed the screen was black again. Back to square one. Same behavior as before the battery swap. It might just be my imagination, but it seems like it stays powered on longer when I leave it off for a while. I'll take any help I can get.
Thanks all!
EDIT: I'll also mention that I'm in the DC area, if anyone wants to take a hands-on look, or if anyone can recommend a repair shop.

Are you sure you're not suffering from a erratic/failing power button?

daedric said:
Are you sure you're not suffering from a erratic/failing power button?
Click to expand...
Click to collapse
No. I'm not sure.
The screen stayed on for several minutes while reformatting the cache, but the screen still eventually went black (without me touching anything). Could a potentially-faulty power button have engaged without me touching it? Sure, maybe, but I suspect the issue is something else.
Can you describe a procedure to test for a faulty power button?

UPDATE: Just noticed that while in recovery mode, using the volume buttons to cycle through the options, the phone locks up and becomes unresponsive for a few seconds before the screen goes black.

For any future readers who may be having similar problems: I took my phone to a repair shop where it was disassembled and thoroughly tested. There is an electrical fault in the mainboard, likely a short of some kind. The power button was not responsible. The battery was also not responsible.
I'm now looking for replacement devices to hold me over until Google's next Pixel releases. I may get another Nexus 5 with a shattered display and swap parts, I don't know yet.
Thanks!

Related

Phone keeps restarting before Samsung logo

I recently flashed CM9 (throwing that out there incase it is of some reasoning but I doubt it) and I've had my phone since November.
I flashed CM9 9/25 Nightly like 2 or 3 days ago (absolutely love it by the way, smoothest build/rom for the Skyrocket thus far) No problems with the Rom I might add, just my phone had just randomly restarted on its own twice while using it (nothing happened, just started right back up).
However the 3rd time, it randomly restarted and never booted back up. It vibrates and then reboots before it even gets to the Samsung screen and reboots/vibrates again (2 second intervals or so). The furthest it gets is like 5 seconds into the CM9 logo and then it'll reboot. It does the usual thin white line as it restarts and just gets stuck there. Can't get to Recovery for more than a few seconds before it reboots (not long enough for Touch to settle and do anything) and it won't get to Download Mode fast enough. Any ideas or any way to get data off /emmc? Don't want to lose a bunch of pictures/videos.
I have a replacement coming within the next days so I have about 2 weeks to either get lucky and get up long enough to save my data or somehow find a solution (doubt it). I already took it apart and swapped screens because I had busted the screen before and put the broken one in incase by some miracle the new one was causing it (no luck).
No water damage or anything to the phone, just randomly rebooted those times while texting or listening to music/what not and now it's pooped.
Any suggestions?
Tried without the battery (via usb/pc or AC source), without sim/microsd, etc. and nothing. Assuming I'm just SOL.
Edit: Side note, I got terrible battery life with this phone. I could only get 2 hours of screen-on time if I was LUCKY on Mobile and maaaybe 3 if I was on WIFI. The most I ever got was 5 hours on WIFI with a 3850mAh Extended Battrey (so even though it was a cheap battery, I'm thinking the phone had a problem from the get-go).
You Could Have A Stuck Power Button. To Fix That Try To Repeatedly Keep Pushing The Power Button Hard To Try To Unstick It. or try taking it apart and clean the power button
vincom said:
You Could Have A Stuck Power Button. To Fix That Try To Repeatedly Keep Pushing The Power Button Hard To Try To Unstick It. or try taking it apart and clean the power button
Click to expand...
Click to collapse
This was my first thought, didn't make a difference no matter how I did it. Appreciate the idea though.
[SOLVED] It is indeed the power button.
I took it apart again and thoroughly mashed the power button plenty and gave it a good few breaths of fresh air.
After that I realized that, I put it back together and realized that if I held the power button right after the phone vibrated it seemed to get to the CM9 symbol more often.
So I mashed the power button a ton more, shook the phone like hell and smashed it against my palm a few times and...it booted! I was able to get everything off of it and reset flash/counter/restore to stock all without ever touching the power button. Screen Timeout @ 30 and using ADB is your friend. Now just to see if it magically works till my replacement gets here lol.
hd2k10 said:
[SOLVED] It is indeed the power button.
I took it apart again and thoroughly mashed the power button plenty and gave it a good few breaths of fresh air.
After that I realized that, I put it back together and realized that if I held the power button right after the phone vibrated it seemed to get to the CM9 symbol more often.
So I mashed the power button a ton more, shook the phone like hell and smashed it against my palm a few times and...it booted! I was able to get everything off of it and reset flash/counter/restore to stock all without ever touching the power button. Screen Timeout @ 30 and using ADB is your friend. Now just to see if it magically works till my replacement gets here lol.
Click to expand...
Click to collapse
i know its sounds too simplistic as to blame a sticky power button and users dismiss the idea because they'll blame themselves, a bad flash, or the rom, but a reboot at a 8-10sec interval is the power button internal switch making contact, sometimes its an easy fix or sometimes it takes more than a few tries, or taking it apart to clean the internals
My phone goes anywhere now from 10 seconds to a full day without having a reboot with continuous vibration at 2 second intervals. Flashed to stable ROM's so that's definitely not the issue. I've had this phone since Christmas 2011 so I'm assuming I don't have warranty? You guys just unscrewed the screws and got into the internals I'm assuming?

[Q] GS4G keeps reseting every 3 seconds

Hello.
I have searched the forums about my issue, and although there are a lot of threads about phones rebooting, there was none about such exact problem as I am experiencing. I apologize if I missed a thread which tackled this problem.
Symptoms:
1. my galaxy S 4G reboots about every 3 seconds: it only gets to the very first "Samsung Galaxy S 4G T-mobile" logo, and reboot
2. it is possible to access boot menu (volume up+down), but only for a split second, and phone reboots again
3. rebooting starts as soon as in put battery in, no need to even press the power button
All that started by itself yesterday. I thought it was a mechanical fault with power switch, I opened the phone, unscrewed covers, cleaned everything, but found no mechanical issue. I switched batteries, tried starting the phone of plugged-in charger, on usb cable, took out sd card, sim card, put a different sim card in... and nothing helped.
Phone runs on Gingerbread 2.3, stock by T-mobile, never had any other roms on it. Device is rooted.
If anyone has an idea how to approach this issue, please let me know. Or reply with a link to somewhere I can read more. I was not able to find much on this...
Thank you!
Malarz
The phone sometimes does a reboot loop if u take the battery out of the phone without turning the power off. Just keep trying to turn it on, and eventually it would reboot properly. Take the battery out of the phone for a few minutes, put it back and try to turn it on again. Do this a few times to see if it boot back properly.
Hit the thanks button if it helps. It's my motivator to be more helpful.
gizmoscoop said:
The phone sometimes does a reboot loop if u take the battery out of the phone without turning the power off. Just keep trying to turn it on, and eventually it would reboot properly. Take the battery out of the phone for a few minutes, put it back and try to turn it on again. Do this a few times to see if it boot back properly.
Hit the thanks button if it helps. It's my motivator to be more helpful.
Click to expand...
Click to collapse
Thank you for a prompt reply!
I did take out battery for a long time, well over one hour, and took out sim card and sd card as well. Unfortunately reboot loop started immediately when I placed battery back in the phone. That's what made me think it was a mechanical issue with power button.
I will try keeping battery out a few times again today.
One other thing: the phone had been in hot and humid environment for about 30 minutes before this happened. Not the first time for this phone to experience high humidity, though. However, I did not find any moisture inside the unit.
Malarz
I had this happened to my phone. Just wait it out and keep trying to reboot, it will come around. Take the battery out and put it back on. Keep on repeating this step.
Also, when the phone is on, try to hold the volume - + and power button at the same time to see if u can get into boot mode.
Also u can use hair blow dryer to blow dry area around the power button.
Hit the thanks button if it helps. It's my motivator to be more helpful.
Or, batt is dead...
You have a stuck power button. Take apart the phone and clean the power bottom with compressed air. Then rapidly push the button in and out for a while.
Resolution:
I took the phone apart, and checked the power button (which had been my first guess), and was seemingly all right.
The battery was also not the issue, as I tried 3 different batteries.
Having no other choice, I put the battery back in, and let the phone happily reboot at its own leisure. After over 20 reboots, the system came on. Then a few minutes later the device rebooted again, and the loop started all over. After a while it booted up again. This time I did not wait for the device to reboot by itself, and I switched the phone off with power button, and then turned back on, and it booted normally. Repeated this once more - normal boot again. One more power off, and I entered the boot menu and did factory reset. Once the stock reinstalled, everything would work perfectly - no more issues with boot loop.
So it seems to me as a software problem more than anything else.
Side note: for the last several weeks the phone displayed strange behavior, that is the screen would light up for no reason by itself, and quickly go off. Sometimes it happened once every few minutes, sometimes it happened several times a minute. Did it have anything to do with the boot loop? No idea. But it strengthens my hunch about a software issue, as that behavior also went away after factory reset.
Sorry for the lengthy post, but since I have not found a similar case anywhere in the forums, I though someone might find this interesting. I do not deal with phones except as a user, but some of you guys do it maybe professionally, so maybe this will be a curious puzzle for you to solve.
Malarz
It sounds like Gremlins....
Sent from my Amazon Kindle Fire using xda app-developers app
Do you have notifications set up? It could notify that u have incoming messages such as a text or an email.
Hit the thanks button if it helps. It's my motivator to be more helpful.
Malarz said:
Resolution:
I took the phone apart, and checked the power button (which had been my first guess), and was seemingly all right.
The battery was also not the issue, as I tried 3 different batteries.
Having no other choice, I put the battery back in, and let the phone happily reboot at its own leisure. After over 20 reboots, the system came on. Then a few minutes later the device rebooted again, and the loop started all over. After a while it booted up again. This time I did not wait for the device to reboot by itself, and I switched the phone off with power button, and then turned back on, and it booted normally. Repeated this once more - normal boot again. One more power off, and I entered the boot menu and did factory reset. Once the stock reinstalled, everything would work perfectly - no more issues with boot loop.
So it seems to me as a software problem more than anything else.
Side note: for the last several weeks the phone displayed strange behavior, that is the screen would light up for no reason by itself, and quickly go off. Sometimes it happened once every few minutes, sometimes it happened several times a minute. Did it have anything to do with the boot loop? No idea. But it strengthens my hunch about a software issue, as that behavior also went away after factory reset.
Sorry for the lengthy post, but since I have not found a similar case anywhere in the forums, I though someone might find this interesting. I do not deal with phones except as a user, but some of you guys do it maybe professionally, so maybe this will be a curious puzzle for you to solve.
Malarz
Click to expand...
Click to collapse
Hardware not software. You had a stuck power button. By forcing the reboot with the power button you unstuck it. If you don't believe it research Occam's razor. Glad you got it fixed(unstuck) though.:victory:
EDIT: Here are some other people who have had the same issue on samsung phones.
Stuck power button
Stuck power button
Stuck power button
If you need any more let me know. lol

Won't power on

My myTouch worked for a really long time, even while overclocked. Today, when I was playing a game (Minecraft) it gets much hotter than normal. So I place it on my fan, just a floor fan, to let it cool down. Once it's cooled down, I resume my game. Out of nowhere, it just freezes and shuts off, then restarts, then turns off again once the BIOS splash goes away. It doesn't power on until I press the power button, then it only runs the BIOS splash and shuts off again. I try again, and it powers on to the boot screen, and then it shuts off again shortly after. I try it again, then just BIOS. And yet again, then a successful boot after letting it charge for about 10 minutes. I take a shower and when I come out it works fine, but 10 seconds into use, while I pressed the Bluetooth notification drawer widget button, it freezes and shuts off. From here on, it won't power on at all. I plug it into computer, nothing. All that works is the dim red LED on the trackpad. I press the power button, trackpad light turns on for a few seconds, then off. I press again, turns on for a second then off. When I hold the power button, the light is on and blinks every 10 seconds. No key combos work. Charge light does not come on when plugged in to either computer or wall charger. Any fix for this?
Not a fun situation, very possible your emmc is fried but there is a chance its just the battery. Let it charge overnight and if possible test a new battery
But there is a high likelihood you're going to need a new logicboard
If you're after a new device I do have a few oneplus one invites left...
Best of luck!
demkantor said:
Not a fun situation, very possible your emmc is fried but there is a chance its just the battery. Let it charge overnight and if possible test a new battery
But there is a high likelihood you're going to need a new logicboard
If you're after a new device I do have a few oneplus one invites left...
Best of luck!
Click to expand...
Click to collapse
I have a very similar problem, i recently came across the mytouch 4g slide in the closet and remembered that it died due to charging overnight, 2-3 years ago lol, well the phone still does what it did after it died, no vibrations screen etc, the only sign of life is the two red lights one at the top left of the screen and the trackpad, could this be just the battery that got fried that night? Should of gotten this fixed those years ago but just got a new phone instead.
Possible but could also be a sign of a bad logic board
I have an extra one if any of you want it, not selling it, I can just mail it to ya, PM me about it, whatever. It's got moderate chips and dents, but works fine except sometimes the soft keys don't always work and you have to restart the phone. It has the latest CWM recovery and the latest 4.4.4 ION ROM. No SD card ships, but baseband and all wireless works, but uh, it's SIM locked and S is still ON. Bootloader is unlocked. I'll give you an extra screen and an extra battery, too.
I fixed the one I posted this thread about after I realized I could buy a new motherboard directly from HTC with a few hidden strings pulled (I'm just that special) and before that I ordered the one I'm talking about now that I'm trying to get rid of on Amazon.
So, yeah. best way to fix one is to get a new motherboard, the one from HTC's old stock warehouse that I got took a week or so to ship, and I cracked the casing opening it and almost ripped a connector ribbon, and I also think that this phone surpasses the G1 as the most mechanically intricate device I've disassembled. I've done a few, but man, this blew the top.

Nexus S [CM11] - hardbricked, no vigration, no computer detection!

My phone: Nexus S, 16Gb, Rom CM11, Android 4.4.4 (List of updates: https://download.cyanogenmod.org/?device=crespo)
My story
Yesterday, (about 9.00pm 13/12/2015) my phone got some laggy, so I powered him off. I left it there, 15 minutes later I came back, and I forgot that he had been powered off, so I thought it was just sleeping. I picked him up and press PowerButton. Nothing happended!
Then I got a look at CM rom, found that interesting is my Rom just got a new update at 2.00pm 13/12/2015. I think that my phone has auto-updated!!
In the past, sometime he behaved the same: PowerButton not respond. So, after that 1st press, about 5 sec later, I started to press the PowerButton repeatedly and rapidly, hopefully the phone would wake up.
But no, the reality was that he was being off. There were about 6-7 presses, I will describe slowly below (assume between each press is 0.2 sec):
1st and 2nd press: nothing happened
3rd press: the phone vibrated, and Google logo appeared
4th press: (I had no mean to continue pressing, but it was too fast, I couldn't stop) suddenly, the Google logo disappeared (so the logo stayed on screen just for about 0.2 sec; while normally, it should stay there for atleast 5 sec)
5th and 6th press: nothing happened!
And from then on, no more, anything happened.
What I tried
Hold PowerButton for even 1 minute: nothing happen!
Hold PowerButton + VolumeUP for even 1 minute: none!
Hold PowerButton + VolumeUPandDOWN for even 1 minute: none too!
Connect to charger (wall or pc): no Battery Animation show up! BUT the phone and Battery get warming up!
Take out the Battery for even 15 minutes, then put it back, and PowerButton: nothing!
And the phone not get recognized by PC too.
Sumary
No display
No vigration
No recognized by PC (because of this, I can not follow this method: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
More Information
In the past, the VolumeDOWN sometimes seems get stucked, cause the phone silent and auto boot to safemode, after many try to press and reboot, the phone may get out of safemode (because VolumeDOWN back to normal)
PowerButton sometimes not respond.
My Battery is not good, sometimes it drops too much! Eg: having 50%, after reboot, dropped to 3%, and start to increase slowly, max around 30% and become normally.
Hope you guys have some ideas! I still can't do anything, when the phone is not regconized by PC!!
Thanks for reading!
Thank you!
Hey,
2 things come to mind and I bet are both the problems. First off you need a new battery and you seem to know this, very cheap now a days but still buy a good one as cheap knock offs are abundant and don't support the power they say, try mugen, anker or stock oem
Also you need to replace power button, this phone was always notorious with bad ones, a new one is cheap but many often found just a loose connection so if you open up the phone, check the ribbon connections and then throw in that new battery all should be well, hopefully
Best of luck!
demkantor said:
Hey,
2 things come to mind and I bet are both the problems. First off you need a new battery and you seem to know this, very cheap now a days but still buy a good one as cheap knock offs are abundant and don't support the power they say, try mugen, anker or stock oem
Also you need to replace power button, this phone was always notorious with bad ones, a new one is cheap but many often found just a loose connection so if you open up the phone, check the ribbon connections and then throw in that new battery all should be well, hopefully
Best of luck!
Click to expand...
Click to collapse
Thank you. I'll try your suggest ASAP.
But I'm wondering, that do you think that CM Update maybe also a reason?
I kind of doubt it as that should only effect the software, if you were getting a bootloop or anything to that extant yeah, but being it won't power on at all I doubt it
thank you
Nope, I've seen these symptoms before - exactly the same thing. Dude, I think your phone is Superbricked.
I've got a stack of 3 Nexus S 4G's that have exactly the same problem - the eMMC card is trashed by a buggy "secure erase" implementation. See: https://wiki.cyanogenmod.org/w/EMMC_Bugs
My "working" one was working great, even set it up to sell on eBay, when I went to wipe its data with a factory-reset from the settings menus. When it shut down to reboot, I pulled the battery. That's what bricked it - because the eMMC was halfway through a background erase/rewrite procedure, it wiped out the boot loader somehow and completely bricked the phone. It now does precisely, exactly the same thing you describe - absolutely nothing, except when it's plugged in, it warms up after a while.
Best I can tell, the only way out from here is to use a JTAG device to reflash the chip, but even then, the eMMC itself might be "unbootable" (i.e. can't start up, can't be read or written, can't be reformatted/restored).
I just called it "end of life" for those phones and now they're just a sour reminder on my shelf
FalconFour said:
Nope, I've seen these symptoms before - exactly the same thing. Dude, I think your phone is Superbricked.
I've got a stack of 3 Nexus S 4G's that have exactly the same problem - the eMMC card is trashed by a buggy "secure erase" implementation. See:
My "working" one was working great, even set it up to sell on eBay, when I went to wipe its data with a factory-reset from the settings menus. When it shut down to reboot, I pulled the battery. That's what bricked it - because the eMMC was halfway through a background erase/rewrite procedure, it wiped out the boot loader somehow and completely bricked the phone. It now does precisely, exactly the same thing you describe - absolutely nothing, except when it's plugged in, it warms up after a while.
Best I can tell, the only way out from here is to use a JTAG device[/URL] to reflash the chip, but even then, the eMMC itself might be "unbootable" (i.e. can't start up, can't be read or written, can't be reformatted/restored).
I just called it "end of life" for those phones and now they're just a sour reminder on my shelf
Click to expand...
Click to collapse
thank you!!
my heart just stop breathing :'( :'(
God, I wish there were a solution to it. I'd really like to donate a phone to anyone that thinks they have the tools or skills to make a "how I did it" explanation - involving whatever tools/software are necessary - to bring these phones back and help us all. I bought 2 of those 3 phones as "for parts" on eBay, and it turned out that both of those phones appeared to have exactly this same issue (though one also had a cracked glass). I even verified the issue by swapping in my good phone's eMMC (at least on the NS4G, it's a swappable card module), and the boards booted up. I only needed the one for the good screen (as I had a good board but completely destroyed display panel) - and that's how I got my one working again.
Then, in the end, I accidentally stumbled upon the method by which the previous two phones were bricked - and now there are three. It seems like a fairly common problem. :/

Rooted Pixel 1 won't turn on, isn't responding

I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?
alienjon said:
I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?
Click to expand...
Click to collapse
See if you still can get your phone into download, fastboot or recovery mode. Here you can see the button combos: https://m.youtube.com/watch?v=YFaq4g-oa2Q
If you can get to recovery mode, click on wipe cache and reboot. If your phone still is stuck afterwards, go to recovery again. There is an option to wipe and reset the phone. Note that your data will be lost!!! Do it at your own risk. But a reset often is the last working choice when your phone behaves strangely.
If you get none of the three mentioned modes to work, I think your Pixel has a hardware fault.
Hope this helps.
check the charging port first....whether it is charging or not......try to connect to PC
i guess the phone is not charging
So the bottom line is this is still somewhat ongoing, though I’ve confirmed the phone is definitely bricked. I brought it into UBreakIFix and after taking it apart (noting that the device seemed physically in great shape) that there wasn’t anything obviously wrong with any of the particular hardware (they mentioned that replacing the motherboard would likely do it, but it would be about as expensive and effective as buying a new phone anyway...).
I ended up writing back to Google and am in back and forth talks with them now. I’m not sure what they can or will do, but my final answer will have to be getting a new phone one way or the other.

Categories

Resources