Screen won't stay on - Nexus 5 Q&A, Help & Troubleshooting

Nexus 5, stock firmware not rooted and otherwise untouched. When trying to screen unlock the phone, it immediately returned to the lock screen almost as if it didn't unlock.
I found that if I power cycled the phone, I had around 20 seconds of usage before the same behaviour started again and I could keep doing this process.
I tried factory reset, and found that the screen worked perfectly for bootup and would work continually until any button was pressed - then the same 'screen switching off issue'. I could get a flicker of what was on the screen, by pressing the power button - but then it quickly gracefully went off.
The screen itself appears to be functional, and no odd pixels. Booting (and using) the bootloader / recovery works exactly as expected, without the screen turning off - for an unlimited amount of time.
I then tried flashing Cyanogenmod, but gave the identical result. Now reverted back to stock.
Any ideas?
Thanks

Related

broken fuze. powers on as soon as battery is popped in

So I've had my fuze a little over a year now, no major issues. Used mostly energyroms, but about December time I switched back to a simple non-bloated stock rom for the stability.
Anyway today at work I was texting, and I press the power button to put the phone in standby. And the screen remains on and usable. I tried again and it would not go into standby (power button physically feels normal, it does not feel loose or abnormal.) So i let it sit for a few minutes, then i look at it and a message poped up asking if i wanted to turn the phone off (like as if i was holding the power button)so i press no, then it comes up again a few seconds later and aagain and again. So I soft reset the phone.
The phone resets but takes a LOT longer at the att/htc splashscreen, then it hangs at the htc screen and does not make it to the wimo screen, but instead an error screen saying:
"The device is unable to boot because you have either turned off the device incorrectly or tried to install an applicationa from an untrusted source, press SEND to reset your device or press any other button to cancel..."
I think it went through the hard reset this time because when it restarted it asked to calibrate the screen and install stuff. it resets again sometime after that, still takes forever at the splash screen and comes back up to the error, only this time no matter what button i press it wont go away and boot into wimo. It seems like none of my buttons work (they wont light up now) when i slide out the keyboard, it is not lit up like normally.
And heres the kicker, my only way to turn on/off the phone is to take out/put in the battery. As soon as I pop the battery back in the fuze turns on. Is my phone toast? Ive tried to hard reset and the phone does not reach the bootloader, it goes straight to the splash screen. Same with trying to reflash it from my comp, raphealwrapper cannot find my phone.
I've only recently encountered the exact same problem on my Touch Pro, but stock ROM and everything. As far as I can tell, our power buttons are busted and probably need to be serviced. One of the contacts must be stuck in the 'on' position somewhere inside :\ As a temporary fix, I've been using AEButton Plus and remapped double tap end call key to turn the screen off, and removing the stylus to turn it on.

[Q] HTC Desire not exactly bricked.......but.....read on

Hi
Strange occurrence today. Turned on phone--nothing. Reset battery and it booted fine, but after awhile (when the screen timed out) it went back to black. When I turn it on it goes to dark blue (BSOD?) but nothing else happens, however as soon as I reset the battery, it will boot successfully and as long as the screen is on, the apps seem to work etc. As soon as I lose the screen, I lose the phone again. Volume down followed by power switch brings up the same BSOD.
The lcd is on and the phone is apparently charging regardless.
Can anyone help get me back in business?
Thanks

Black Screen of Death Recovery

I just got the Black Screen of Death for the first time after owning the phone for 2 weeks - pretty alarming when the phone is unresponsive, you can't reboot with the power button, and you can't pull the battery. (Coming from an S5, this is my first phone with a non-removable battery). Even though I knew my phone was fully charged, I tried plugging it in, and didn't even get the red LED. Not good.
After a little Googling, the solution I found that worked for me was: Press and hold Down Volume + Power at the same time for 7 seconds.
This brings you to a screen with some options, the first being to reboot like normal.
Volume toggles up and down between the options, but be sure not to choose option 2, which is a factory reset!
The Bixby button selects, so I just clicked on option 1, and I was back in business.
This apparently does a "simulated battery disconnect". Assuming it was some sort of firmware crash, this should bring you back to life. It did for me. There are other suggestions on the page if it doesn't work, but I was good to go after step 1. Hope it helps...
http://thedroidguy.com/2017/05/sams...ck-screen-death-troubleshooting-guide-1072353
I had the same problem. Well mine showed the AID display but was completely unresponsive for like 30 minutes. That thing you did helped. Shortly after I did a full factory reset and been fine since
Sent from my SM-G955U using Tapatalk
Not working
I followed rooting instructions on https://forum.xda-developers.com/galaxy-s8+/development/root-t4128321
and now my phone wont even turn on at all, not even a sign of life after bootloader was flashed

Pixel 2 screen unresponsive after 60 minutes of providing power

Pixel 2, unrooted, stock, locked bootloader.
I was providing power to another pixel 2 far from a power outlet. After ~15 minutes, the phones were behaving fine. After I ate (about 45 minutes later), I unplugged the phones and my phone (the one providing power) had a black screen that would not turn on (there is no screen cover; i've heard of those causing issues with the head sensor and turning the screen off)
At first I thought the device had been drained, but the fingerprint sensor responds with the normal haptic blip. If I press the power button right afterward, the fingerprint sensor used to also flash the screen veeeeery slightly, as though it were off and being turned back on, but it no longer does that.
Troubleshooting steps so far performed:
held power button for >30 seconds: causes a long haptic blip that repeats itself every 30 seconds. No other response, and the phone acts like it's off; it no longer does the short blip on fingerprint sensor use (how I get it "on" again is a bit of a mystery, as there's no haptic feedback to represent turning on; probably something I do "boots" it silently and it starts haptic blipping once that's done)
held power button and vol.down at the same time: results vary based on whether it's "off" (after 30 sec power press). If off, nothing happens. If on, after 30 seconds I get the long and the short haptic blips in sequence.
tried to connect pixel buds to it to see if assistant would talk to me. pixel buds wouldn't connect.
charged for 20 minutes and then performed the steps above.
did NOT try calling it before I switched my sim to an older back-up device and now I can't re-activate it on the dead phone to try that.
Still no dice. Dead-seeming phone. One thing I was wondering about... I've noticed when these 2 phones are touching (stacked), they prompt some kind of linking or sharing (well, they don't NOW but they did when they were both alive). Is it possible that my phone offered to cast to the other phone and my leg confirmed while it was in my pocket? Surely it wouldn't continue to cast after being restarted? (this is a reach but it's all I can think of)
Recently discovered the alarm is still set. It went off at 7:15 this morning (correct time), but NOT with the alarm ringtone I have set. So either some settings are wonky or... maybe it's unable to mount the storage filesystem? I can either turn it off by holding the power for 30 seconds or by turning the volume down (volume keys still work)
I'm traveling with a mac right now but when I get back to a PC, is there any chance I could get somewhere with something like ADB (without wiping the device)? I might need some specific steps as I usually only tinker with scripts like wugfresh's.
Google wants to send me a refurb but the device is only 19 days old and I'd rather have a new device when I paid for a new device.
Thanks!
Don't want to quote all of that, so I'll just say that you can download the Mac version of the tools, download the latest factory image, edit the flash-all.sh to remove the -w, so you don't wipe userdata, and then just run the newly saved script. But, you do have to unlock the bootloader first.
DuckRuckus said:
you do have to unlock the bootloader first.
Click to expand...
Click to collapse
Thanks for the reply. I'm back home so I can use my PC now... but I haven't unlocked the bootloader, so I gather I'll lose all my data if I unlock it? Is there any way to extract data without being able to enable data transfer mode on the device?
Also, if I can't get a screen, I can't boot to fastboot or recovery... Will I be able to actually do anything at all?

HTC U11 128GB screen won't turn off.

I've had the U11 for several months and everything is and has been great with it. Today, however, several things just stopped working. I first noticed the fingerprint scanner not working, then I noticed that the power button doesn't turn the screen off. The power button works, I can hold it down and the power menu appears.
I adjusted the screen timeout to 15 seconds and rather than the screen shutting off, it merely dims as though I've turned the brightness all the way down.
The phone is completely stock, but I did unlock OEM Bootloader in developer options.
I went into recovery and wiped the cache to no change. The screen won't shut off and the fingerprint scanner does not register anything. Everything else on the phone appears to work fine. Has anyone else had this issue?
The same night, I ran the battery all the way down and let it sit depleted all night. Charged it to 100% and everything started working again.

Categories

Resources