A couple of days ago I tried to switch on my Nexus Player after not using it for some time but there was not picture. I rebooted it but still nothing on the TV, so I thought maybe it had received an OTA update and got bricked, so I have tried to flash the latest factory image and have found that, although the process seems to finish OK, there's still no picture on the TV.
Has somebody faced this issue?. Could it be a hardware failure (maybe the HDMI output)?.
Thanks.
I have the same issue
Mine had a similar issue. It only showed the google logo for a few seconds after power on and then the screen turned black. It turned out that a pin of the HDMI connector was bent back and made contact with the connector housing.
Related
Hi, a friend of mine got an N7 a few days ago, and he has been using it fine, no problems at all, however, not 10 minutes ago, when he tried to use it, he said the entire touchscreen went dead, and doesn't respond to any touches. He is bringing it round tomorrow for me to have a look at, but I was wondering if anyone else had had this problem (couldn't find anything in the forums with search), or had any suggestions?
He has tried multiple reboots and wake/lock cycles, but no luck so far, and I don't remember it feeling creaky or badly constructed when I played with it on the first day he got it.
Thanks
Edit: Just something I missed out, the N7 hasn't be modified at all, so no rooting etc, AFAIK, meaning the problem isn't because of that..
Same problem on mine! Had my Nexus 7 CCO less than 1 month. The screen suddenly stopped responding to touch. I can still access the device using a OTG cable and mouse. No visible screen lift, screen colours / clarity all ok, even all my apps work. I factory reset the device but still the touchscreen is not working. Not sure what happened. I was so careful when using it
Note: Its a stock device.
Hello,
I have a Moto X Play which is in great condition, I use a case and a screen protector.
Today I went for a walk and grabbed my phone which I hadn't touched in awhile. Once I got outside I realized it wouldn't turn on no matter what I did. Strange, maybe I left an app on.
I get home, plug it in, and it's at 75%. I play with it a bit and put it back in my pocket.
A few minutes later, I can't get the screen on again. I figure, I'll plug it in, reboot it to clear the glitch, it's all good.
It just won't light up.
I can locate it, it's updating its location, I can call it, it vibrates, it responds to buttons (but not the screen) Nothing seems to be wrong with it other than the screen.
I've tried everything to do a reboot, I've plugged in the short circuit usb dongle thing that usually puts an android device right into debug mode. I think it is rebooting but no screen action.
I have the latest OS for the device (whatever the not-so-new one is) and I am unrooted, locked, whatever I haven't messed with anything like that.
What can or should I do? I am just recently out of the 1 year warrantee.
Thank you,
-Phil
Hold down your power and volume down buttons until it turns back up(night take some time) into the bootloader screen and try to factory reset it.
Sent from my Moto X Play using XDA Labs
I've tried this, so far no luck. A bit of an update:
I brought it to a shop, they gave it a light twist and the screen came back fine and was in the setup wizard (as I had remotely reset it). They said the display port may have plugged back in, gave it back free of charge. By the time i got back home it was off again. I brought it back in to have them open it and reattach it for real. This didn't help. They tried attaching a brand new screen, same issue. The screen doesn't light up for reboots, not for factory reset, nothing. I am guessing this is an issue on the motherboard but the fact that a light twist "fixes" the issue suggests to me a light soldering could solve the issue. The repair shop gave it back to me as unfixable but I don't want to give up on it yet. I did have an opportunity to get a Nexus 5 in good shape for 140$ so I did that for now. This gives me time to mess with the Moto X Play. Any ideas?
pcaston2 said:
I've tried this, so far no luck. A bit of an update:
I brought it to a shop, they gave it a light twist and the screen came back fine and was in the setup wizard (as I had remotely reset it). They said the display port may have plugged back in, gave it back free of charge. By the time i got back home it was off again. I brought it back in to have them open it and reattach it for real. This didn't help. They tried attaching a brand new screen, same issue. The screen doesn't light up for reboots, not for factory reset, nothing. I am guessing this is an issue on the motherboard but the fact that a light twist "fixes" the issue suggests to me a light soldering could solve the issue. The repair shop gave it back to me as unfixable but I don't want to give up on it yet. I did have an opportunity to get a Nexus 5 in good shape for 140$ so I did that for now. This gives me time to mess with the Moto X Play. Any ideas?
Click to expand...
Click to collapse
Make a video on attempt to remove a non removable battery
Sent from my Moto X Play using XDA Labs
Ive been having the same issue with my x play, so try this out. turn it on, and have a look at the screen under a bright light, see if you can make out anyting. The backlight might not be coming on, but the screen will still 'turn on' so to speak, you can still make out whats on the display, touch input works etc. I have an issue with the display connector, with a bit of pressure it will work then not work, almost as if the backlight shorts out. it took me awhile to find out that that was the problem. as for a fix, if its the same problem I'm having, then you'd probably need a new mainboard. I've tried everything, new screen, new battery, swapping covers etc.. I have 2 x plays to tinker with and swap out parts.
I've tried using my new phone's flashlight to illuminate the screen with no success (though I will try again tonight, I'm not 100% sure it's on). Looks like mainboard run somewhere around 120$ before the repair cost, seems like it's not worth it. I'll post back after I double-check to see if the screen is there or not.
If it's shorting, I would think it could be fixed with some careful soldering? I do know that when I turn my phone on (remember it's been hard reset and has no SIM card) it vibrates every few minutes, I have no idea why. That's the only odd behavior it's been experiencing aside from the display not showing up.
I tried to look for any sign of the screen showing up by using string light and I didn't see anything that might suggest anything is showing up.
Woke up this morning and started using my phone, noticed that the screen became unresponsive for a few seconds at a time and then I saw some gray horizontal lines.
Did a battery pull and restarted the phone, however, the screen is completely black and I can still hear the boot sound.
It requires a pin to start completely and I can feel the vibration when I touch the location of the back button (the only navigation key available on the pin screen).
Since this started happening I have tried restarting several times and I have seen the "LG splash screen" once, it freezes, the boot sound plays and the screen goes black once again.
The phone is unrooted and has never been modified any at all. It is the US996 variant.
Has anyone ever faced this issue? Could it be the display itself and maybe a replacement LCD will fix the issuse?
UPDATE
Got past the pin screen and think the phone has fully booted, fingerprint scanner works, I can touch the navigation keys and get feedback and I am still getting notifications.
However, the main screen is still blank and the second screen shows the time surrounded by static surrounded. I have attached a photo.
Sounds like a hardware issue.
mausam233 said:
Got past the pin screen and think the phone has fully booted, fingerprint scanner works, I can touch the navigation keys and get feedback and I am still getting notifications.
However, the main screen is still blank and the second screen shows the time surrounded by static surrounded. I have attached a photo.
Click to expand...
Click to collapse
Hi Have you fixed the issue?
Hi
it looks like a corrupt bootloader,
Was it rooted? try to press with the phone off volume + and plug in the usb to enter in download mode, if you enter download mode go back to factory
gilbertlucas46 said:
Hi Have you fixed the issue?
Click to expand...
Click to collapse
Had to send it in to LG to have it repaired
Oddly enough once it was returned the problem reoccured a few weeks later after using an aukey quick charge3.0 charger that I had. Which was when it happened the first time but I didn't make the connection until the second time around
I got rid of the phone though
No more LGs for me, I haven't had much luck with them
Throw that charger seems like or the cable or the charger itself gone bad ,one charger killed 2 of my phones not diferent brands
Hello,
Yesterday my rooted LG v20 h990ds got a kernel crash (green screen). I pulled the battery and after that I noticed no difference.
Today I woke up and noticed that the phone was really slow. Somehow the touchscreen was not always responsive so I had to lock and unlock it again.
I couldn't figure out what it was and I thought that maybe it was caused by the root. So I did a factory reset and went back to stock (LGUP). Unfortunately the problem is still there. Does anybody know what it is? Could it be a hardware defective?
Thanks in advance!
edit:
After a few tests it seems to be the digitizer. I've installed an app to test the digitizer.
Sometimes the screen sees a short touch as a long touch. That's why it opens extra options when I try to type a letter.
I've opened up the phone to see if there was any moisture damage visible, fortunately that was not the case.
Is it still possible that this is a software problem? Or do I have to buy a new screen?
edit 2:
The phone is functioning normally again. I disconnected the screen cable and plugged it back in again. Probably it was a loose contact.
This thread can be closed
Hi All
I have had my shield since last July hooked up to my Yamaha RX-V1075 receiver which feeds my Panasonic AE8000U projector.
Two weeks ago, I turned on as normal and I had an issue with a black screen, rebooted, logo appears for about 5 seconds and then black screen. Booted into safe mode, updated to 7.2.3 and the same issue.
One thing I did try and do at around the same time was connect an old harmony elite remote, I have since disconnected this and gone back to my old 4 remote world :laugh:
I can hook the shield up to my TV and it works fine, I have factory reset it. Still no joy and tried multiple HDMI cables.
Any ideas why it would stop working after 9 months, could this be the update or HDCP which is causing this problem. Any settings I can change in the shield to troubleshoot or check.
Thanks for your help.
Sean
kissofthegypsy said:
Hi All
I have had my shield since last July hooked up to my Yamaha RX-V1075 receiver which feeds my Panasonic AE8000U projector.
Two weeks ago, I turned on as normal and I had an issue with a black screen, rebooted, logo appears for about 5 seconds and then black screen. Booted into safe mode, updated to 7.2.3 and the same issue.
One thing I did try and do at around the same time was connect an old harmony elite remote, I have since disconnected this and gone back to my old 4 remote world [emoji23]
I can hook the shield up to my TV and it works fine, I have factory reset it. Still no joy and tried multiple HDMI cables.
Any ideas why it would stop working after 9 months, could this be the update or HDCP which is causing this problem. Any settings I can change in the shield to troubleshoot or check.
Thanks for your help.
Sean
Click to expand...
Click to collapse
Had a friend of mine experience a very similar situation after only 4 months. He ended up contacting nVidia and they RMA'd the unit.
Sent from my SM-G965U using Tapatalk
Johnny14o said:
Had a friend of mine experience a very similar situation after only 4 months. He ended up contacting nVidia and they RMA'd the unit.
Sent from my SM-G965U using Tapatalk
Click to expand...
Click to collapse
Thanks Johnny, I am RMAing it