Related
Hi all, I've found that when I leave my Player on sleep for a while, I am unable to wake it back up. I've tried pressing the hardware button, the remote buttons, etc. The led is on, but there's no output or sound response from my TV. I have to unplug the NP and plug it back in. Probably a user error, but what's the process to wake the system?
Thanks in advance!
Sent from my SM-N910V using XDA Free mobile app
Action123 said:
Hi all, I've found that when I leave my Player on sleep for a while, I am unable to wake it back up. I've tried pressing the hardware button, the remote buttons, etc. The led is on, but there's no output or sound response from my TV. I have to unplug the NP and plug it back in. Probably a user error, but what's the process to wake the system?
Thanks in advance!
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
I am experiencing something similar, it started with restarts, then it would not boot without the button on the bottom and now it says no signal. Tried connecting it to the pc, pc installed drivers, and if you unplug a cable it says cable unplugged.
Action123 said:
Hi all, I've found that when I leave my Player on sleep for a while, I am unable to wake it back up. I've tried pressing the hardware button, the remote buttons, etc. The led is on, but there's no output or sound response from my TV. I have to unplug the NP and plug it back in. Probably a user error, but what's the process to wake the system?
Thanks in advance!
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
Bumping as I still haven't found a solution.
yep, mine does the same thing, every day i have to reboot it as the screen is black and the device is unresponsive
MIne I have to unplug the HDMI and plug it back in then magically there is a signal. I tried setting never go to sleep and that did not hep. Did anyone upgrade to 5.1.1? does that fix anything?
Bump. Got mine a few days ago and the same thing happens.
It's still on and running. It's still a little warm under the button. But no matter what I do with the remote or button or TV, nothing happens. The only way to get it back up is to unplug/plug the hdmi or power cable.
I've got the same problem, but I've unplugged everything and still nothing, tried different TVs, Different HDMi leads still nothing. Going to contact Ausu or go back to where I purchased it tomorrow. was loving catching up with Game of Throne haha
malctron said:
I've got the same problem, but I've unplugged everything and still nothing, tried different TVs, Different HDMi leads still nothing. Going to contact Ausu or go back to where I purchased it tomorrow. was loving catching up with Game of Throne haha
Click to expand...
Click to collapse
You think it's just a defective device?
Maybe I should return mine as well.
I'm taking mine back tomorrow hopefully. If I can find the receipt
malctron said:
I'm taking mine back tomorrow hopefully. If I can find the receipt
Click to expand...
Click to collapse
Did you get a replacement? Did it work?
Action123 said:
Hi all, I've found that when I leave my Player on sleep for a while, I am unable to wake it back up. I've tried pressing the hardware button, the remote buttons, etc. The led is on, but there's no output or sound response from my TV. I have to unplug the NP and plug it back in. Probably a user error, but what's the process to wake the system?
Thanks in advance!
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
Quoting you so you get a notification
Did you find a solution? Was it your TV, HDMI cable, or the unit itself?
DonDizzurp said:
Quoting you so you get a notification
Did you find a solution? Was it your TV, HDMI cable, or the unit itself?
Click to expand...
Click to collapse
Still no solution. Tried 3 different ROMs and it's the same thing with each one. Could it be a firmware problem? I mean I shouldn't have to reboot it every time it goes to sleep. The hardware button on the bottom has no effect. I'm slowly giving up.
DonDizzurp said:
Did you get a replacement? Did it work?
Click to expand...
Click to collapse
Hey, sorry for the delay, been busy.
But yeah I got my new nexus. Rang Asus with some struggle as the serial on the product wasn't matching up on the system. Useful haha
Then they said it would take 29 days to get a fix or replacement.... I then said I'll take it back to where I got it which in my case was Argos.
Took it back told them the problem, girl looked at me completely confused. Think I lost her at bootloader haha. But I might as well tell them how to explain to do a factory reset which I couldn't do anyway. Then got my replacement. Which I'm leaving in the box as I want to be a geeky guy and do a unboxing video this time haha.
I found if you turn the TV on and off again it will work.. no need to get up and pull the HDMI cable
I noticed this issue didn't happen with 5.0 but happened with 5.1.1 so I'm hoping a new update will fix it.
Random question but on 5.1.1 how do we get sideloader? As I can't find it on the store
Doesn't matter was being an idiot.
malctron said:
Random question but on 5.1.1 how do we get sideloader? As I can't find it on the store
Doesn't matter was being an idiot.
Click to expand...
Click to collapse
A sideloader? If you are asking how to sideload, you boot into the recovery and then choose install from sideload, then use the "adb sideload" command.
malctron said:
Random question but on 5.1.1 how do we get sideloader? As I can't find it on the store
Doesn't matter was being an idiot.
Click to expand...
Click to collapse
That has absolutely nothing to do with this thread
LOL
Also, you sideload using ADB
Turn on USB debugging, install the ADB driver on your PC, then use the adb command "adb install apkname.apk"
No need for root or recovery.
DonDizzurp said:
I found if you turn the TV on and off again it will work.. no need to get up and pull the HDMI cable
I noticed this issue didn't happen with 5.0 but happened with 5.1.1 so I'm hoping a new update will fix it.
Click to expand...
Click to collapse
This doesn't work on my setup. But pulling the HDMI cable works.
This problem appeared on my Nexus player about a month ago, it was working perfectly until that time.
It looks like a problem with the HDMI CEC. Even if I put my NP in "Never sleep mode" as soon as I turn off the TV it will not then wake when I turn the TV back on.
Well, in my case at least, that is not accurate. When I turn the TV on, nothing appears on the screen nor is there any audio, but the NP is still responding to commands and working. I can blindly start a YouTube video from the highlights section while the TV is still "blanked" and when I toggle the HDMI cable connection the I can see that the NP was functioning "correctly" other than it wasn't outputting anything to the HDMI port.
I would say that the "fault" is just likely to be on the TV not implementing HDMI CEC correctly, but everything WAS working correctly until recently and the only changes are on the Nexus Player side of the equation.
DonDizzurp said:
That has absolutely nothing to do with this thread
LOL
Also, you sideload using ADB
Turn on USB debugging, install the ADB driver on your PC, then use the adb command "adb install apkname.apk"
No need for root or recovery.
Click to expand...
Click to collapse
Haha I know told you it was random yeah I did that after I sent it. Couldn't delete the message sorry haha
Problem solved?
Before you take the device back to the store, I believe the problem is the TV; even those of you who tried multiple ones. I did the same thing; tried a different TV. However, in my case, it works. When I hooked mine to a newer TV, the device wakes up fine. I read in other forums (searched "HDMI won't wake up device") and to my surprise, there are other forum where people complained about the same with other devices. Apparently, something related to the HDMI port (maybe the version of HDMI?).
I'm usually good at recovering my devices since I've had various Android devices since 2010. I'm stuck with how to recover my Shield since it doesn't have a physical buttons. How can I boot directly into the bootloader or recovery? I've done it a few times by accident by rubbing my finger across the power button but can't figure out how to do now. ADB or Fastboot won't detect it at all, I just get a black screen and my TV says "no output".
I had rooted my Shield but kept the stock OS and had TWRP installed but saw no use for root. The 1.4 OS update had been sitting on my homescreen for weeks so I finally decided to revert back to stock and upgrade. I flashed the stock bootloader via fastboot and then flashed the system image but didn't touch userdata. After booting up some things would be goofy (Netflix would get to either 25% or 99% and the audio would play but the video would be stuck on the loading screen, Grid streaming would load the game but would display a green screen but the audio would play in the background) but I didn't want to wipe it yet because I didn't backup Kodi yet.
I saw that there was a 2.0 OS update available and I knew it should work now since I had the stock recovery so I downloaded it and applied it, it verified the image and then rebooted to the stock recovery and proceeded to flash the image. It got about 99% (or maybe 100% done, I wasn't paying attention) and then next thing I notice I just saw a black screen. I thought maybe it was upgrading something or reinitializing something so I waited about 5 minutes and still nothing. Rebooted and got the same thing.
Anyone know if this is recoverable or should I just RMA it?
I'm in the same boat. I was running pure stock from day one (only bought this thing two weeks ago).
After installing 2.0 update last night, the device powers on (green light) but no signal from HDMI. Tried another TV and bypassed receiver (as per forum suggestion).
Computer does not detect when connected with USB. Tried to do HW boot into recovery, does not seem to work.
I have started the RMA process but I'm still trying to get this thing to boot into recovery.
Seems like this has happened to a few other users also over at the geforce forums.
try to reflash it with nvidia images.
if you cant boot to fastboot try this.
HW method:
- Disconnect power cable
- Insert USB OTG cable and make sure to connect other end to a host PC
- Connect power cable to SHIELD
- Quickly start pressing power button for ~3 seconds
- Do not hold the button and connect power supply afterwards
- HDMI TV should be always connected to SHIELD
Alternative method:
- Perform software shutdown on SHIELD by holding Power button for 10 seconds
- Connect USB OTG cable to SHIELD
- Start pressing power button for 3 seconds
- HDMI TV should be always connected to SHIELD
brando56894 said:
Seems like this has happened to a few other users also over at the geforce forums.
Click to expand...
Click to collapse
I did the RMA, only took a few days. The new unit came and auto-updated to 2.0. It worked fine.
I spoke with support today regarding the update, they had this to say;
[12:51:41 PM] : Only few devices, which already had some issues, got bricked with 2.0 update. This was already predicted by NVIDIA, just to get those devices replaced for the customers.
[12:52:45 PM] : Few devices had some hardware issues, but they were working fine. To make that issue prominent and get them detected and to replace them, NVIDIA has released 2.0 update.
[12:53:34 PM] : For other devices, 2.0 update will add many new features and will boost the performance. But for those lot, it will brick them
[12:55:38 PM] : It was a strategy from NVIDIA to provide perfect devices to our customers
Click to expand...
Click to collapse
Take that with a grain of salt of course.
Defective is defective I guess... the RMA was fast at least.
So they bricked the defective ones on purpose just to get them out of use?
I'm in the process of RMAing mine now, they want a lot of information hahaha
God this from support since mine have black screen, it did not help me and my are sent for rma but i might help other.
As part of troubleshooting steps, please try the below mentioned steps and see if that fixes the issue.
-> Unplug all the cables and keep the device off for good 2-3 minutes.
-> Plug the Power cable, controller through USB (Wired) and Ethernet cable to the ATV. Do not connect HDMI cable.
-> The device will power on. Keep it idle for about 5 minutes and keep tapping A button on the controller. Continue tapping for about a few seconds.
-> Now leave the device is this state without the HDMI cable for good 15 to 20 minutes and plug the HDMI cable.
-> See if the ATV displays any output.
I just got my replacement unit, so I'm good. I have two shield controllers now
brando56894 said:
I just got my replacement unit, so I'm good. I have two shield controllers now
Click to expand...
Click to collapse
Sent from my SM-G925K using XDA Free mobile app
bunny0007 said:
God this from support since mine have black screen, it did not help me and my are sent for rma but i might help other.
As part of troubleshooting steps, please try the below mentioned steps and see if that fixes the issue.
-> Unplug all the cables and keep the device off for good 2-3 minutes.
-> Plug the Power cable, controller through USB (Wired) and Ethernet cable to the ATV. Do not connect HDMI cable.
-> The device will power on. Keep it idle for about 5 minutes and keep tapping A button on the controller. Continue tapping for about a few seconds.
-> Now leave the device is this state without the HDMI cable for good 15 to 20 minutes and plug the HDMI cable.
-> See if the ATV displays any output.
Click to expand...
Click to collapse
Where or from which sources you get this tutorial information?
Sent from my SM-G925K using XDA Free mobile app
visitor29 said:
Where or from which sources you get this tutorial information?
Sent from my SM-G925K using XDA Free mobile app
Click to expand...
Click to collapse
Nvidia tech chat support, before they made a rma on my box.
But just got my replacement box today
How hard was it to get a replacement? I am afraid to do anything to mine. Asked nvidia if unlocking the bootloader or rooting the device voids the warranty since they show you how on their website. Their response was that doing either allows them to reject your return under warranty. Just looking for anyones input on their encounter with doing a rma if something should happen.
You may have screwed yourself over by telling them that you did that. I had mine rooted and unlocked also, except mine was unrooted when it bricked itself but the bootloader was still unlocked. I made not mention of rooting/unlocking and it was extremely simple to get a replacement.
No mine is still stock. Just received a replacement from amazon since it bricked itself doing the 2.1 update. Was just wondering what they had to say about the situation. Was consindering flashing the 2.1 full rom, but was worried what would happen if it bricked and had to do a rma. Would not say anything to them about unlocking the bootloader or flashing it. Was wondering if they could detect if anything was modified on it since I see everyone gets a black screen and can't access the console with fastboot. Do they have some way of accessing the system or are they also locked out like we are? Just want to be sure I can get a rma if something happens. A $300 Pro model is a lot to screw up. Support was great to work with, but didnt get as far as a rma since it was still in amazon's 30 day return window. Got a new one in 2 days since I have prime. I just asked what there policy was and not mentioned anything about a bad console.
---------- Post added at 06:13 PM ---------- Previous post was at 06:07 PM ----------
Its just a shame that they offer the tools for developers, but turn around and say that it voids the consoles warranty.
I'm sure they are able to use a UART bridge (serial console) to get into it but I doubt they care enough, like I said mine had an unlocked bootloader but I haven't heard anything back from them yet regarding it.
OMG I fell to their trick to brick my device.... I just did my RMA today, they asked me to do alot things; speed test, model number, turn off, unplug power and hdmi, hold power for 30 sec, plug in power for 2-3 mins, plug in hdmi, then found out no signal on my screen...I assumed it's brick now. i attempted to revive the unit but it doesn't seem to work... Then they had me filled out form, provide snapshot of p/n and s/n numbers... and send them my invoice of purchase.
every time it gets new firmware it loses netflix 4k and this is the fix for it
bunny0007 said:
God this from support since mine have black screen, it did not help me and my are sent for rma but i might help other.
As part of troubleshooting steps, please try the below mentioned steps and see if that fixes the issue.
-> Unplug all the cables and keep the device off for good 2-3 minutes.
-> Plug the Power cable, controller through USB (Wired) and Ethernet cable to the ATV. Do not connect HDMI cable.
-> The device will power on. Keep it idle for about 5 minutes and keep tapping A button on the controller. Continue tapping for about a few seconds.
-> Now leave the device is this state without the HDMI cable for good 15 to 20 minutes and plug the HDMI cable.
-> See if the ATV displays any output.
Click to expand...
Click to collapse
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.
Finally decided to try out the Gear VR that came with my S8 tonight. It said there was a firmware update for the controller, the update failed and now I can't get the controller to turn on or connect. Any have a solution?
Varekai said:
Finally decided to try out the Gear VR that came with my S8 tonight. It said there was a firmware update for the controller, the update failed and now I can't get the controller to turn on or connect. Any have a solution?
Click to expand...
Click to collapse
Same thing happened to me. After ab 5 min, holding the home button on controller restarted and I could pair again.
Bored.Fish said:
Same thing happened to me. After ab 5 min, holding the home button on controller restarted and I could pair again.
Click to expand...
Click to collapse
I replaced the batteries and held the button for well over a minute, nothing.
Hi, what solved this issue?
It never got resolved for me. Samsung wanted remote access to my phone which I didn't want to give. Gamestop sells the controller for $40 so I bought a new one.
woke up one morning and i cannot get any signal over hdmi. i unplugged it and waited a while and plugged it back in, and i still get nothing from it. no audio or video. the white led in the front does light up. The youtube app on my phone detects a random chromecast singnal, but i cannot connect to it (it could be a neighbor but i doubt it). its completely stock. windows didnt detect anything when i plugged it into the usb port on my laptop. any ideas?
Mine has died as well. It will boot up to a white Google logo on a black background. The logo stays up for a while, disappears, and comes back a few minutes later. It never advances further. Tried holding the bottom button as I powered it up, but that didn't do anything.
Mine randomly died too. Went to turn it over to that source and nothing. Led light was on but no image. Pulled the plug and repowered it and still nothing and now the led won't light. Rather pissed. Loved that thing! And there is no true successor for it!
Mine started random reboots a week or 2 ago. Did a factory reset in settings and that worked for about 2 days then reboots again, also lost Wifi.
Did a reset via TWRP and nothing. Going to try a downgrade to android 7.
I followed this post and downgraded to 7.1.2 and it's found Wifi again. Working well so far.
i cant even get anything on the screen at all. guess I'm buying a shield.
i just had two nexus players randomly die as well, after google screen its just blank.
3 in 3 weeks
I have 3 Nexus players and they all died a week apart from each other. They would just stay in the Android boot screen. Factory resets didn't work. Was this a timed death of the product line?
*Update:
I was able to use the Nexus Root Tool to unlock the bootloader on one of my players and flash the stock Android from the Google developers site. It worked, but the same issue had happen 2 more times since! My other 2 players won't load the bootloader, so I haven't been able to do anything with those.
Yes, something seems to be up, mine died earlier today, too many people to just be coincidence. I was casting to it and it just rebooted and is stuck on the google startup animation. Stock, never unlocked or rooted, been rock solid up until now. I use it as a DVR so I figured maybe my external hard drive had crapped out and was causing a hangup since the light isn't on anymore, but same symptoms when unplugging it and trying to reboot.
Same thing here, with 3 devices. Hit the home button on our main TV earlier, and it went to a black screen. Rebooted, and it'll show the boot animation, then goes to a black screen where it normally would have went to the 10' interface. Tried our bedroom player, no signal at all. Haven't tried my spare in the basement yet, but I bet it'd work since it's not been powered on in about 6 months, since I replaced it with a cheap chinese player..
skunkfifty said:
I followed this post and downgraded to 7.1.2 and it's found Wifi again. Working well so far.
Click to expand...
Click to collapse
Update to my last post:
Add mine to the pile. 7.1.2 ran great for about a week. Now it just sits on the black google loading screen.
erehwon6811 said:
Mine has died as well. It will boot up to a white Google logo on a black background. The logo stays up for a while, disappears, and comes back a few minutes later. It never advances further. Tried holding the bottom button as I powered it up, but that didn't do anything.
Click to expand...
Click to collapse
I just experienced this as well. Came home from work, plopped on the couch thinking I was going to catch up on some news and to my surprise my remote app on my phone wasn't finding the player in the network. Come to find out I have this black screen with the "Google" loop occurring.
Pressing the button the bottom didn't work - nothing. I never rooted, flashed a different OS, unlocked it - nothing. I really like this guy - I loved the design.
---------- Post added at 04:28 PM ---------- Previous post was at 04:24 PM ----------
Agamemnon2002 said:
I have 3 Nexus players and they all died a week apart from each other. They would just stay in the Android boot screen. Factory resets didn't work. Was this a timed death of the product line?
Click to expand...
Click to collapse
Exactly the same thing for me yesterday! WTH?!? I never flashed, unlocked the bootloader - nothing. I have to admit I do find this interesting that so many are having these issues withing the last few weeks - days.
Same here as well, just noticed this morning. Very interesting that all are experiencing the same issue around the same time.
wayneshades said:
I just experienced this as well. Came home from work, plopped on the couch thinking I was going to catch up on some news and to my surprise my remote app on my phone wasn't finding the player in the network. Come to find out I have this black screen with the "Google" loop occurring.
Pressing the button the bottom didn't work - nothing. I never rooted, flashed a different OS, unlocked it - nothing. I really like this guy - I loved the design.
---------- Post added at 04:28 PM ---------- Previous post was at 04:24 PM ----------
Exactly the same thing for me yesterday! WTH?!? I never flashed, unlocked the bootloader - nothing. I have to admit I do find this interesting that so many are having these issues withing the last few weeks - days.
Click to expand...
Click to collapse
Same issue here. Asus support wanted me to send it in for out of warranty repair with an upfront $60 charge before even getting repair estimates. I asked them to escalate it since this seems to have been a software update causing widespread issues. Also wrote them on twitter about it.
I've contacted ASUS support as well about my 2 stuck devices. They asked that everyone with the problem go to their support page and submit an email using the "Complaint" category.
Same problem here, yesterday I came home and it is stuck on the black screen that says Google.
Add mine to the pile.
mine doesn't boot up anymore either. i just sent a complaint email to Asus support as mentioned above.
stevedeezy said:
mine doesn't boot up anymore either. i just sent a complaint email to Asus support as mentioned above.
Click to expand...
Click to collapse
I did the same thing and I got a response back that I should contact Google. When contacting Google, they told me I should contact Asus.
Add me to the list... working perfectly yesterday then suddenly this morning wont stop hanging on the splash screen.. just loops... tried factory reset and nothing..