yashsingh1/xdaforums huggingface dataset:
[Nexus Player Q&A, Help & Troubleshooting] brymaster5000:
Do you have a link to their contact page with an email address? Trying to find it but running into only phone numbers...

Thanks,

Bryan
[Nexus Player Q&A, Help & Troubleshooting] Eyedoctor2:
Yet another apparently bricked device.

Mine was unlocked but otherwise completely stock.

Was on loading bootloop. When I plugged/unplugged now stuck on Google screen.

Will subscribe to thread in hope of a resolution.
[Nexus Player Q&A, Help & Troubleshooting] gleonard3:
Broken for me too. Lame.
[Nexus Player Q&A, Help & Troubleshooting] omrebel:
Add me to the list of Nexus Players suddenly bootlooping.......
[Nexus Player Q&A, Help & Troubleshooting] tweaq:
Mine started bootlooping a few days ago. Finally got around to trying to fix it... and i'm here.
[Nexus Player Q&A, Help & Troubleshooting] DCDD85:
Here is a link from the ASUS site that I used to contact them.

https://www.asus.com/support/Product/ContactUs/Services/questionform/?lang=en-us&_ga=2.134540977.1146686866.1533938306-24237590.1533938306

I created an account before submitting anything, Just FYI.
[Nexus Player Q&A, Help & Troubleshooting] jnmacd:
factory reset did not work, but manually flashing to older version worked

i flashed 8.0.0 (OPR6.170623.021, Sep 2017) from here https://developers.google.com/android/images#fugu

and it booted up

I may need to block this device from downloading an update somehow.
[Nexus Player Q&A, Help & Troubleshooting] OneAn9ryN00b:
Count mine in.... Completely Stock.... tried factory reset but nothing. Will try loading an older imsge later when I get time.
[Nexus Player Q&A, Help & Troubleshooting] erehwon6811:
I wish you guys luck in finding a solution. I gave up and traded mine in at Best Buy to get a $30 off coupon for an nvidia shield. I could have kept it longer, but I was never able to get it into any form of a recovery. I didn't feel like fighting with it anymore. At least this way I got something out of it. It was a good device while it lasted.
[Nexus Player Q&A, Help & Troubleshooting] MrsLish:
I just had 2 die. The 1st one was about 2 weeks ago, I bought a new one online because I figured the old one had just died, but tonight the one in my bedroom died too. The new one I just got is still working but Im afraid the same is going to happen to it now too. I called Asus Customer Service and was told the warranty has expired on my devices and if I wanted to pay $60 then i could send it into them to look at. Im not doing that. They have obviously done something to these players. If anyone finds out what is going on please post. I love my Nexus players and this is such crap!
[Nexus Player Q&A, Help & Troubleshooting] growsonwalls:
I have unplugged my 3 units before they get killed with this virus-like killer update.

One of you are going to have to bite the bullet and send your bootlooped units to Asus to find and fix the problem.

How do you expect a fix when they don't have a broken unit to autopsy?
[Nexus Player Q&A, Help & Troubleshooting] tweaq:
I've been emailing with Asus. They want the same $60 fee for out of warranty repair. At this point, I feel like if you guys can't fix it, Asus has no hope.
[Nexus Player Q&A, Help & Troubleshooting] kornklown69:
same problem here ... spash screen loop.. worked great yesterday...
[Nexus Player Q&A, Help & Troubleshooting] PlaneCrazyy:
Something's fishy about the Nexus players....

Mines dead too. Google screen boot loop.
[Nexus Player Q&A, Help & Troubleshooting] Grushteniak:
Mine still working, I'm running 7.1.2 August Patch Level (build N2G48C) - I hated the YouTube new UI and then I found a way to prevent automatic update using Kernel Adiutor and a script.

Maybe this enforces the killer update, right? This is some serious thing, they have no right to do such thing
[Nexus Player Q&A, Help & Troubleshooting] El Daddy:
Throw my Nexus Player on the pile. I switched to the input and it was bootlooping. Power cycled it and it won't turn on. No status light, nothing.
[Nexus Player Q&A, Help & Troubleshooting] PlaneCrazyy:
I just can't believe they would push an update, brick all the Nexus players, and expect we're going to be ok with that. How does this work for all those devices that are out of warranty? Are we just out of luck at this point?

I would never have bought the thing if I knew they would push an update to kill it after a few years, I don't think anybody would!

At first I suspected my hardware had some failure because mine is stock out of the box and I've never flashed anything else on it. Based on the timing of everyone else's going down, most all within the last few weeks... It seems unlikely.

ASUS/GOOGLE, WHAT ARE YOU DOING?!
[Nexus Player Q&A, Help & Troubleshooting] jimshep:
After escalating the issue, Google support responded that even though it was purchased from them, Asus is responsible for support now since it is out of warranty. Looks like it's time to get a different device :(.
[Nexus Player Q&A, Help & Troubleshooting] jimshep:
Bummer, looks like the $30 Best Buy streaming device trade-in credit has expired.
[Nexus Player Q&A, Help & Troubleshooting] PJnetv5:
Heard back from Asus support. Sounds like they do not have the equipment to reset the Nexus Players anymore. Additionally, the level 2 guy told me it would be $60 per device if they had the equipment. I only paid $50 for it.... Pretty disappointing! Here is the email:

________________________

Thank you for contacting ASUS Corporate Customer Care. Allow me to apologize on behalf of ASUS for the issues you are having.

My name is Dwight G. and I am with the Corporate Customer Care team here at ASUS. Our service center has stated that due to the age of the unit there is no part in stock to repair the unit. Please accept my apologies for any inconvenience this may cause.

We do value your business, thank you for being a part of the ASUS family. If you have any further questions, comments, or concerns please do not hesitate to let us know, we will be more than happy to assist you.

_________________________

Has anyone gotten a response from Google? It was actually Google that sent me to Asus, but I believe Google pushes the images though.
[Nexus Player Q&A, Help & Troubleshooting] jimshep:
Seems like Google gave the same response to me
[Nexus Player Q&A, Help & Troubleshooting] billteeth:
Care to elaborate on using Kernel Adiutor and a script to prevent updates? I've got a NP that's been in a box for 6 months, I was planning on using to record football games in September...
[Nexus Player Q&A, Help & Troubleshooting] Grushteniak:
I followed this thread: https://xdaforums.com/nexus-player/help/how-to-stop-ota-update-nougat-t3588731

You have to be rooted, keep that in mind. Good luck!
[Nexus Player Q&A, Help & Troubleshooting] billteeth:
Cool, thanks! Looks like I'll be dusting off my OTG cable and NRT for some root action.
[Nexus Player Q&A, Help & Troubleshooting] bugginout711:
Asus has now redirected me back to Google after Google first directed me to the hardware manufacturer.

"Thank you for contacting ASUS Corporate Customer Care.

Allow me to apologize on behalf of ASUS for the issues you are having.

Please see reply from the Team:

The whole SW system is totally controlled by Google. We can not do anything on this.

End users should submit the SW issues to Google directly.

Best Regards,"
[Nexus Player Q&A, Help & Troubleshooting] jimshep:
One of the primary reasons I have purchased Nexus and Pixel devices in the past was to avoid the hardware vendor / software vendor finger pointing. Guess this assumption is invalid. :(
[Nexus Player Q&A, Help & Troubleshooting] Dejavou42:
Experiencing same issue

I just experienced the same issue with my nexus player. (google bootloop/ factory reset doesn't work). I tried wiping the cache partition. This froze for about 30 minutes after which I gave up and rebooted the nexus player. At this point I was completely stuck on the "no command" screen with the icon of the android laying on its back. The image and text would flash about every 5 seconds. I found adb would still connect, and fired up wugfresh nrt. I tried flashing 7.0.0 firmware and 8.0 firmware, and nothing would work. Then I noticed that I was getting an error when trying to flash the latest OPR2.170623.027, Nov 2017) firmware: Remote: flash cmds error. Thanks to a reddit article, I found that 7.1.2 (N2G48C, Aug 2017) will work fine. I applied this firmware with NRT, and boom, I am back in business. The 8.0 update went through again automatically once I set up the nexus player, and so far, no boot loop again yet. As I side, this device had never been rooted or unlocked until after the bootloop issue.

To me, it definitely looks like there is an issue with the latest firmware. I hope Google will release a fix for this.
[Nexus Player Q&A, Help & Troubleshooting] killerjay13:
I had the same issues and had to use Nexus root tool to try and fix it. Never knew how to do this until now and that tool was a life saver.

I think one of these 2 Google play store updates maybe the problem

1)

Abdroid TV Home

= Version- 1.5.4-100-4935149f; Update Aug. 8, 2018

2)

Android System Webview

= Version 68.0.3440.91; Updated Aug. 6, 2018

And maybe this one as well, but this one is a big maybe

3)

Android TV Core Services

= Version 1.4.5-100-4860530f; Updated Jun. 25,2018

I̶ ̶h̶a̶d̶ ̶t̶o̶ ̶u̶s̶e̶ ̶n̶e̶x̶u̶s̶ ̶r̶o̶o̶t̶ ̶t̶o̶o̶l̶ ̶3̶ ̶t̶i̶m̶e̶s̶;̶ ̶ ̶

[̶B̶]̶[̶U̶]̶1̶s̶t̶ ̶t̶i̶m̶e̶[̶/̶U̶]̶[̶/̶B̶]̶ ̶I̶ ̶j̶u̶s̶t̶ ̶l̶e̶t̶ ̶t̶h̶e̶ ̶n̶e̶x̶u̶s̶ ̶d̶o̶ ̶i̶t̶s̶ ̶t̶h̶i̶n̶g̶ ̶h̶o̶p̶i̶n̶g̶ ̶t̶h̶a̶t̶ ̶a̶ ̶c̶l̶e̶a̶n̶ ̶i̶n̶s̶t̶a̶l̶l̶ ̶w̶o̶u̶l̶d̶ ̶f̶i̶x̶ ̶t̶h̶e̶ ̶p̶r̶o̶b̶l̶e̶m̶ ̶(̶2̶ ̶d̶a̶y̶s̶ ̶l̶a̶t̶e̶r̶ ̶b̶o̶o̶t̶l̶o̶o̶p̶)̶,̶ ̶

[̶B̶]̶[̶U̶]̶2̶n̶d̶ ̶t̶i̶m̶e̶[̶/̶U̶]̶[̶/̶B̶]̶ ̶I̶ ̶s̶t̶o̶p̶p̶e̶d̶ ̶a̶l̶l̶ ̶a̶u̶t̶o̶ ̶u̶p̶d̶a̶t̶e̶s̶ ̶f̶r̶o̶m̶ ̶t̶h̶e̶ ̶G̶o̶o̶g̶l̶e̶ ̶P̶l̶a̶y̶ ̶A̶p̶p̶ ̶S̶t̶o̶r̶e̶ ̶(̶b̶u̶t̶ ̶s̶t̶i̶l̶l̶ ̶r̶u̶n̶n̶i̶n̶g̶ ̶O̶r̶e̶o̶)̶ ̶a̶n̶d̶ ̶o̶n̶l̶y̶ ̶i̶n̶s̶t̶a̶l̶l̶e̶d̶ ̶N̶O̶N̶-̶G̶o̶o̶g̶l̶e̶ ̶L̶L̶C̶ ̶r̶e̶l̶a̶t̶e̶d̶ ̶u̶p̶d̶a̶t̶e̶s̶ ̶a̶n̶d̶ ̶o̶n̶l̶y̶ ̶u̶p̶d̶a̶t̶e̶d̶ ̶m̶y̶ ̶a̶p̶p̶s̶.̶ ̶T̶h̶i̶s̶ ̶w̶o̶r̶k̶e̶d̶ ̶f̶i̶n̶e̶ ̶u̶n̶t̶i̶l̶ ̶I̶ ̶d̶e̶c̶i̶d̶e̶d̶ ̶t̶o̶ ̶b̶e̶ ̶b̶r̶a̶v̶e̶ ̶a̶n̶d̶ ̶s̶t̶a̶r̶t̶e̶d̶ ̶u̶p̶d̶a̶t̶i̶n̶g̶ ̶G̶o̶o̶g̶l̶e̶ ̶L̶L̶C̶ ̶r̶e̶l̶a̶t̶e̶d̶ ̶u̶p̶d̶a̶t̶e̶s̶ ̶1̶ ̶o̶r̶ ̶2̶ ̶a̶t̶ ̶a̶ ̶t̶i̶m̶e̶,̶ ̶i̶t̶ ̶c̶r̶a̶s̶h̶e̶d̶ ̶i̶n̶t̶o̶ ̶t̶o̶ ̶b̶o̶o̶t̶l̶o̶o̶p̶ ̶a̶f̶t̶e̶r̶ ̶I̶ ̶u̶p̶d̶a̶t̶e̶d̶ ̶t̶h̶e̶ ̶l̶a̶s̶t̶ ̶2̶ ̶G̶o̶o̶g̶l̶e̶ ̶L̶L̶C̶ ̶(̶u̶p̶d̶a̶t̶e̶s̶ ̶1̶ ̶&̶ ̶2̶ ̶l̶i̶s̶t̶e̶d̶ ̶a̶b̶o̶v̶e̶)̶.̶ ̶T̶h̶i̶s̶ ̶b̶o̶o̶t̶l̶o̶o̶p̶e̶d̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶d̶a̶y̶ ̶a̶s̶ ̶r̶e̶b̶o̶o̶t̶ ̶1̶ ̶f̶a̶i̶l̶e̶d̶ ̶

N̶o̶w̶ ̶I̶'̶m̶ ̶o̶n̶ ̶m̶y̶ ̶[̶B̶]̶[̶U̶]̶3̶r̶d̶ ̶r̶e̶i̶n̶s̶t̶a̶l̶l̶[̶/̶U̶]̶[̶/̶B̶]̶ ̶a̶n̶d̶ ̶i̶t̶ ̶s̶e̶e̶m̶s̶ ̶t̶o̶ ̶b̶e̶ ̶d̶o̶i̶n̶g̶ ̶o̶k̶,̶ ̶b̶u̶t̶ ̶t̶h̶i̶s̶ ̶t̶i̶m̶e̶ ̶I̶ ̶s̶t̶i̶l̶l̶ ̶p̶u̶t̶ ̶i̶t̶ ̶o̶n̶ ̶n̶o̶ ̶a̶u̶t̶o̶ ̶u̶p̶d̶a̶t̶e̶s̶ ̶f̶r̶o̶m̶ ̶t̶h̶e̶ ̶G̶o̶o̶g̶l̶e̶ ̶p̶l̶a̶y̶ ̶s̶t̶o̶r̶e̶ ̶a̶n̶d̶ ̶o̶n̶l̶y̶ ̶u̶p̶d̶a̶t̶e̶d̶ ̶G̶o̶o̶g̶l̶e̶ ̶L̶L̶C̶ ̶t̶h̶i̶n̶g̶s̶ ̶t̶h̶a̶t̶ ̶w̶e̶r̶e̶ ̶l̶a̶s̶t̶ ̶u̶p̶d̶a̶t̶e̶d̶ ̶b̶e̶f̶o̶r̶e̶ ̶J̶u̶n̶e̶ ̶2̶5̶ ̶o̶r̶ ̶l̶o̶o̶k̶e̶d̶ ̶n̶o̶n̶-̶e̶s̶s̶e̶n̶t̶i̶a̶l̶.̶ ̶ ̶T̶h̶a̶t̶ ̶l̶e̶f̶t̶ ̶m̶e̶ ̶w̶i̶t̶h̶ ̶t̶h̶e̶ ̶3̶ ̶a̶p̶p̶ ̶a̶b̶o̶v̶e̶ ̶l̶i̶s̶t̶e̶d̶ ̶a̶n̶d̶ ̶I̶'̶m̶ ̶o̶n̶ ̶d̶a̶y̶ ̶2̶ ̶o̶f̶ ̶n̶o̶ ̶p̶r̶o̶b̶l̶e̶m̶s̶ ̶a̶n̶d̶ ̶h̶a̶v̶e̶ ̶r̶e̶b̶o̶o̶t̶e̶d̶ ̶i̶t̶ ̶a̶ ̶b̶u̶n̶c̶h̶ ̶o̶f̶ ̶t̶i̶m̶e̶s̶ ̶t̶o̶ ̶s̶e̶e̶ ̶i̶f̶ ̶i̶t̶ ̶w̶i̶l̶l̶ ̶s̶t̶i̶l̶l̶ ̶r̶e̶s̶t̶a̶r̶t̶.̶

(Will let you know in a few days how its going)

Failed
[Nexus Player Q&A, Help & Troubleshooting] jsgraphicart:
This is some good info for those able to get their Nexus Player back up and running. When/If I ever do, I'll be sure to do the same. Crazy how an app could possibly brick your device.
[Nexus Player Q&A, Help & Troubleshooting] killerjay13:
Sad to Report but this failed today. :( Going to try and not let it update anything from stock Oreo to see if that works.
[Nexus Player Q&A, Help & Troubleshooting] DCDD85:
I have a total of three Nexus Players. The other week two of them died with in a few days of each other. I searched the internet and really did not find out a lot. Like most I found this thread and one on Reddit that I'm currently following. In the week since this all started I have flashed stock Android 7.0 to both devices. They in turn start to work and get the latest update to Android 8.0. Just about a day after they get the update to 8.0 they die again. I have repeated this process twice for each of my effected Nexus Players. I have also reached out to ASUS with the same result as many here. I hope there is some solution soon.
[Nexus Player Q&A, Help & Troubleshooting] jsgraphicart:
So I'm going to try and get my Nexus Player working again this weekend. Just had a question. Am I able to flash stuff in the bootloader if I never enabled USB Debugging in the settings when it was working? When I tried to flash stuff last weekend, it would always fail.
[Nexus Player Q&A, Help & Troubleshooting] bigworm50:
I had never enabled usb debugging before mine died and I was able to flash TWRP and use the command line commands for it over adb to flash lineage 15..
[Nexus Player Q&A, Help & Troubleshooting] jsgraphicart:
Thanks. Just want to be prepared for when I work on it. The hardest part is getting the thing into recovery in the first place. Mine seems to be so bad I can only get into it with some luck.
[Nexus Player Q&A, Help & Troubleshooting] DCDD85:
Yes you can. My suggestion is to use the Nexus Root Toolkit and follow the instructions. It's pretty straightforward. I know because I don't flash very often either and I was able to get going pretty quickly.

Here is a link to the tool:

https://www.google.com/amp/www.wugfresh.com/nrt/amp/
[Nexus Player Q&A, Help & Troubleshooting] jimshep:
After contacting Google support and being redirected to Asus who then redirected me back to Google, Google is pushing it back again to Asus. As this problem is most likely a software issue being pushed by Google, I have little confidence that this is every going to be resolved.

Should I replace the Nexus player with Roku or Shield? Was leaning toward the Shield, but not sure after this fiasco especially with the relatively old hardware in the Shield.
[Nexus Player Q&A, Help & Troubleshooting] jnmacd:
well, reflashing worked for awhile.... about a week later, same thing, won't boot.

I reflashed again, and its working, but probably only for a small amount of time.
[Nexus Player Q&A, Help & Troubleshooting] jsgraphicart:
I can't even get the thing into recovery. I plug it in holding the button, the light comes on but it takes a good minute before the Google logo even pops up. Keeping the button held, it eventually turns off and repeats. Tried letting go of the button when the logo comes on as well but same results.

Sometimes the light pulses slowly. I don't even know what that means. Anyone know the light indicator meanings? Solid light should just mean it's powered on. Then there's a slow pulse. And I've also seem a fast pulse. The fast pulse seemed to happen when I got into recovery once last week.

I think it may just be time to lay this device to rest and get something new
[Nexus Player Q&A, Help & Troubleshooting] DCDD85:
I'm not sure what the lights mean, by the sounds of there must be a meaning. However to get the device into fastboot is a bit tricky. Based on what you stated above it sounds like you are holding the center button after the google logo appears. If so, what you want to do is as soon as you see the Google logo let go of the button and just wait. The fastbook menu should appear. At least this is my experience. In fact I have to flash stock 8.0 this morning on one of mine that keeps boot looping. Its a pain to keep flashing but at least I'm able to use the device for a day or two.

I hope this helps!

Also here is a thread on the Google Product Forums about this issue, it appears to be getting some notice. I suggest everyone who has not post here as well. The more we post the the better chance I think of a fix coming to fruition.

https://support.google.com/nexus/forum/AAAANseOu18Ski0fFZ0pZM/?hl=en
[Nexus Player Q&A, Help & Troubleshooting] jsgraphicart:
I've gotten into fastboot with ease in the past. It's just acting different now. It doesn't want to do it no matter what I've tried. And I've tried everything imaginable with that single button. Pressing and releasing it at different times. It just shuts down and repeats the same thing. Oh well. Hopefully the issue gets more attention from Google if it's their fault.
[Nexus Player Q&A, Help & Troubleshooting] DCDD85:
Apologies, I'm not sure I have much more to offer. I'm by no means and expert. Possibly someone on here has an alternative method of booting into fastboot? I did a quick Google search and I did not see anything that jumped out at me. I'm sorry I know how frustrating this must be. If I come across anything I'll post back here.
[Nexus Player Q&A, Help & Troubleshooting] Dejavou42:
Recovery

Hopefully this helps. I don't even use a tv to time the button press. I use this method:

1. Make sure male to male usb cable is plugged in to Nexus Player and computer first.

2. Leave the power cord unplugged.

3. press and hold the bottom button

4. plug in the power.

5. as soon as the light changes from slow pulsing to fast pulsing, release the button.

Your computer should recognize the adb device at that point. Also try to ignore the usb device connected sounds from your computer. It will connect and disconnect a few times before finally booting into adb recovery mode. If I remember correctly, the white google logo will remain on the screen for a few seconds after initiating recovery mode, and that might be throwing you off. If you continue holding the button too long, it will reboot.

-EDIT: NRT will flash the device from the screen where you select between normal boot, recovery, and restart bootloader. If you are trying to flash after you actually select the recovery option, it may never get to that point. I have never been able to get the "recovery menu" to load at all when the nexus player goes into the bootloop. Also, you may want to check the power supply voltage, if it is on the low side, it may slow things down...

Last edit- If while flashing with NRT, your device reboots after downloading the bootloader, and doesn't reconnect (give it a good 5 minutes first):

1. unplug the power cable.

2. hold down the bottom button and replug the power cable

3. as soon as the light starts rapidly flashing again, release the button.

4. NRT will pick up where it left off.

5. if doing the firmware flash without a tv connected, be ready to unplug the power cable as soon as it says "rebooting" again, just after writing cache. (you're probably going to have to reflash a second time, but in my case, the second time it has completed every time.)

6. connect to a tv, and if you get the "no command" screen, do the reflash process again. This time it should go through 100% without having to trick it after downloading the bootloader.

consider following this guide to permanently stay in 7.1.2. (that's what I'm going to do, and report back with results. *fingers crossed):

https://xdaforums.com/nexus-player/help/best-nexusplayer-rom-7-1-2-scratch-root-t3820607

I've read reports that anyone locked down to 7.1.2 hasn't experienced these issues.

Also, my nexus player is bricked again. I'm gonna re-flash it again, and maybe try to install twrp, and back it up that way for easy reflashing in the future.
[Nexus Player Q&A, Help & Troubleshooting] gleonard3:
I know some people are against Oreo, but it does buy you some functionality over Nougat. With Oreo, you can connect a USB 3.0 HD using an OTG cable and get DVR functionality with the Live Channels app. Was really a great cord-cutting solution using OTA reception. Used it everyday. I may try to get mine back to some locked down state of Oreo for this purpose.

Ideally though, I think Google owes us a goddamn explanation here. I'm thinking a class action suit is in order. Pretty unreal. This situation is inexcusable. I've been a loud proponent of Google for a long time. Tired of being made to look like an idiot. This isn't the only time.
[Nexus Player Q&A, Help & Troubleshooting] PlaneCrazyy:
So, I can see in device manager when I plug in my nexus player, the device named 'MOOREFIELD' pops up. I can't see it with ADB, but I can't even get into fastboot on the device. I'm trying to add my hardware ID's for it in the INF file for the usb drivers to install it, but it's failing to find the driver.

Does somebody have a working one that I could cross reference my hardware ID's with to see if something else weird is going on? I get:

USB\VID_8086&PID_0A2C&REV_00:0

USB\VID_8086&PID_0A2C

with a device description of :

MOOREFIELD

So I added this to my INF file:

;MOOREFIELD

%SingleAdbInterface%	= USB_Install, USB\VID_8086&PID_0A2C

%CompositeAdbInterface% = USB_Install, USB\VID_8086&PID_0A2C&REV_00:0

Also tried:

;Google Nexus Player

%SingleAdbInterface%	= USB_Install, USB\VID_8086&PID_0A2C

%CompositeAdbInterface% = USB_Install, USB\VID_8086&PID_0A2C&REV_00:0

Any idea if this could work even if I can't access fastboot?
[Nexus Player Q&A, Help & Troubleshooting] Dejavou42:
moorefield device

Moorefield is how the device is recognized on initial boot, and will continue to be recognized as this if stuck on the "white google logo screen." I believe this is a direct access to the intel atom processor. I show the same info for that device:

USB\VID_8086&PID_0A2C&REV_00:0

USB\VID_8086&PID_0A2C

Pay attention to the light on the bottom of the nexus player. Start holding it in before you plug in the power cord, and as soon as the light starts blinking fast, release the button. You may not be holding the button long enough.

When fastboot loads, the device will be recognized as "Android bootloader interface" with the following ids:

USB\VID_18D1&PID_4EE0&REV_????

USB\VID_18D1&PID_4EE0

The only application that I know of that can access the moorefield device is XFSTK, and can be found on sourceforge. I can't post external links yet, so you'll just have to search for it. I have never tried that program with the nexus player in this state, so be careful, you may permanently brick the device.
[Nexus Player Q&A, Help & Troubleshooting] PlaneCrazyy:
I think it's already toast. The first time it was boot looping at the first of August, I was able to bring it back by going to the bootloader and flashing back to stock. Now it's behaving completely different this time around. When I plug it in, It takes almost 30sec to even show the Google screen. Holding the button until this point doesn't work anymore. The led never flashes quickly, but goes to a slow pulse for about 15 sec shortly after the Google logo appears, then loops around again. Unless I can try XFSTK to somehow force it to the bootloader...
[Nexus Player Q&A, Help & Troubleshooting] jsgraphicart:
That's exactly where I am at the moment. I've given up on fixing it for now. But it would be nice if someone could find a way out of this state. Let us know if you have success with anything.
[Nexus Player Q&A, Help & Troubleshooting] Dejavou42:
fastboot troubleshooting

If I'm not mistaken, the slow pulsing light indicates normal boot. I'm wondering if the bottom button has failed on some of these devices. If you're good at disassembling things, you could try checking continuity of the button and/or manually make the connection with a piece of scrap wire/ paper clip.
[Nexus Player Q&A, Help & Troubleshooting] Dejavou42:
Hardware failure

I'm starting to believe those that are saying this is caused by hardware failure. My device is boot looping again with 7.1.2 installed, rooted with magisk, and ota updates blocked. The fist thing that started happening is google play services started crashing. I couldn't even open the play store to update anything. I then uninstalled updates to google play services and google play store, and they were still crashing. Essentially, nothing could update on the device at all. I was watching something on netflix, and the box crashed, rebooted, and got stuck in the bootloop.

I may try to install lineage OS at some point just to play around some more with the box, but I'm fairly convinced that I just need to trash this thing and move on.