yashsingh1/xdaforums huggingface dataset:
[Nexus Player Q&A, Help & Troubleshooting] Ad1982:
Agreed, I've reached out to Google and after a few days they got back to me and just pointed me to Asus. From what others have said, Asus wants $60 to look at it/fix it, which is more than what it costs to just pick one up off of ebay. What a shame, outside of the Nvidia Shield, there's not much that can do the things I was able to do with the Nexus Player (Cast & usb tv tuner/dvr are my 2 main requirements...even the Mi Box doesn't work with the tv tuner I picked up for compatibility with the Nexus Player, or with any other usb tv tuner for that matter).
[Nexus Player Q&A, Help & Troubleshooting] Wipeout:
This happened to me, too on or about the 1st of August. Noticed it would start the bouncing "balls" boot animation, then freeze. Booted into bootloader, reflashed last system image, worked great. Then it was competely dead a few days later--no white light on the bottom, nothing. Picked up a shield and have been loving it, but was very frustrating to have it happen out of the blue.
[Nexus Player Q&A, Help & Troubleshooting] professorpasta:
This also happened to me, glad I am not alone. Currently trying to get to the bootloader in an attempt to reflash /system, but fastboot is not detecting it for some reason.
[Nexus Player Q&A, Help & Troubleshooting] sprockkets:
Mine was able to be reflashed and it worked, but now it went back to this behavior in a day. Now I tried to turn it on and it won't even show anything, no hdmi signal. I already bought a Mecool M8S L to replace it but I'm really at a loss as to what would have killed it. A GPS update? Can't see that messing up the system partition. Someone needs to see if an update is being pushed.

I would have gone Roku but my lady doesn't like the UI.
[Nexus Player Q&A, Help & Troubleshooting] ilgadets:
Mine has also died. After a few times crashing out of youtube, I had the perpetual boot animation, now just a blank screen and no led light.
[Nexus Player Q&A, Help & Troubleshooting] stevedeezy:
Asus replied to me with instructions to boot into recovery or to send the unit in for repair with a $60 charge. My unit no longer powers on after keeping it unplugged for a day.
[Nexus Player Q&A, Help & Troubleshooting] bryanus:
I'd love to try this, but like many others here, our players are completely dead. No LED, power up, boot logo, or anything. Can't adb/fastboot at all.
[Nexus Player Q&A, Help & Troubleshooting] ggregor:
Implemented but what's next?
[Nexus Player Q&A, Help & Troubleshooting] trevd:
Yes the logs are extremely verbose. What I would Suggest you do is. After about 60 secs of the bootloop I would issue the follow commands

adb shell stop
adb shell stop bootanim
adb shell dmesg > dmesg.txt
adb logcat -b all > logcat

So to break this down.

Assuming you're accessing this from a linux box ( although windows should work just as we;

[I]adb shell stop [/I]will stop the android framework and *most* of the native services.

This command used to stop them all but for some reason the bootanim service was still running hence the additional adb shell stop bootanim

The screen on the nexus should go black. the next 2 command grab the kernel log using the dmesg command and a full logcat.

Things have changed over the years so -b all is the only argument required and there is no need to specify each log buffer individually.

You'll have to Ctrl+C the logcat command but you'll know when to do that as the logcat.txt file *should* stop growing ( if it doesn't, just give it 30 second and the Ctrl+C it )

After that if you can upload the files to pastebin, google drive or whereever you can make the files available for viewing. I will take a look and also explain what folks need to look for to diagnose whatever is the matter with these devices.

As far as blocking OTA's. After a quick investigation, things appear to have changed between 7.x and 8 as it appears the system update has now been integrated into the GMS framwork - This is what activity manager launches when check system update button is pressed

[B] com.google.android.gms/.update.SystemUpdatePanoActivity][/B]

.

I did try and disable the update checking the "proper" way by revoking update permissions from the GMS package. Unfortunately I was met with the following errors

adb shell pm revoke com.google.android.gms com.google.android.gms.permission.PHENOTYPE_UPDATE_BROADCAST
Operation not allowed: java.lang.SecurityException: Permission com.google.android.gms.permission.PHENOTYPE_UPDATE_BROADCAST is not a changeable permission type

adb shell pm revoke com.google.android.gms android.permission.NOTIFY_PENDING_SYSTEM_UPDATE
Operation not allowed: java.lang.SecurityException: Permission android.permission.NOTIFY_PENDING_SYSTEM_UPDATE is not a changeable permission type

There's probably something inside of the /data/data/com.google.android.gms/ directory that can be jigged to prevent any ota from downloading

I can also think of a ton of dirty hacks that will break the update process.

However I think it's all abiit of a moot point tbh as the chances of receiving and further updates is slim/none.

This is because the opr2.170623.027 november 2017 release is the final update/relase issued to the nexus player.

I've been running it since it dropped and i've not had any issues with OTA's at all.

Hopefully this helps a little without muddy the waters too much.

Trevd
[Nexus Player Q&A, Help & Troubleshooting] ggregor:
Logs uploaded

I had rebooted which no longer gives me the animation balls rolling. Now I just get a Google with an unlocked image at the bottom. So I shelled in at the # prompt redirected to the two files. Also, it seems that now I don't get the "Recovery" screen to come up with the option to restore using ADB from a sideloaded OTA.zip ? Was this due to the overwrite of "boot" with boot.img?

adb shell stop
adb shell stop bootanim
adb shell dmesg > dmesg.txt
adb logcat -b all > logcat

<snip>

You'll have to Ctrl+C the logcat command but you'll know when to do that as the logcat.txt file *should* stop growing ( if it doesn't, just give it 30 second and the Ctrl+C it )

</snip>

Had to truncate the logcat file as my account with pastebin only allows 512k pastes. Look here: https://pastebin.com/u/ggregor
[Nexus Player Q&A, Help & Troubleshooting] ggregor:
Downgraded to 7.1.2 to see what happens

Referencing this post:

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

(partially anyway as I still don't have a mouse hook-up), I was able to get 7.1.2 loaded and had it working enough to prove that a reboot was possible without it going back into a loop or stuck at bouncing balls.

Overnight though it updated itself to Ver. 8 and this morning it was back to the bouncing balls.

The author of the post above talks of loading TWRK and then a script to disable OTA upgrades. I've got an adapter on order to allow mouse input to mini-usb and will follow this to hopefully a working device again.
[Nexus Player Q&A, Help & Troubleshooting] mirrin:
Mine died too same symptoms
[Nexus Player Q&A, Help & Troubleshooting] ajtorres14:
We might have something in common, we just need to find it. I have 4 Nexus Players, 2 of them died suddenly, those two had the Amazon Firestick remote, the other two still have the stock remote. All of them have the latest build of Kodi, but the ones that died were used more often, also the ones that died were updated manually with images from the Android API website.

By dead I mean stuck in a bootloop, they won't go past the Google splash screen. Fastboot mode lets me select Recovery mode, but it won't take me to recovery screen. Restart bootloader option seems to work just fine.
[Nexus Player Q&A, Help & Troubleshooting] Xzyl:
Mine went late last night. Kodi went a day or two earlier before everything else followed. can get by with streaming with the Blu Ray player (still losing 3 apps plus the media browser) until I cam afford to replace it. On the up side it looks like there is another option coming out.

Ematic Getting Ready to Release Android TV Streaming Box

Already filed with the FCC.

"According to the filing, the Jetstream device will run Google’s Android TV operating system, with access to the Google Assistant via an included Bluetooth voice remote. The streamer features 2 USB ports, an SD card slot, an Ethernet port, HDMI out as well as AV out to connect to TVs, and also digital audio out."

From Variety also on Cord Cutter News
[Nexus Player Q&A, Help & Troubleshooting] ski522:
Wow, glad I had turned off auto-updates on both my players. Google is really turning into Microsoft!
[Nexus Player Q&A, Help & Troubleshooting] ajtorres14:
I don't want to sound pessimist, but turning off auto updates won't help, it will eventually force the update.
[Nexus Player Q&A, Help & Troubleshooting] killerjay13:
We Need to figure out which Tech Media Companies are going to Googles October 9th event so when Q&A comes up they all start asking about "Why google pushed a kill switch update to the Nexus player in August?" Maybe that would get their attention.
[Nexus Player Q&A, Help & Troubleshooting] kornklown69:
I agree with you on this.. this needs to be pushed further, this seems deliberate which I hope is not the case.. hopefully this isn't a way for them to push a new product on us.
[Nexus Player Q&A, Help & Troubleshooting] ski522:
I'm blocking access to updates at my firewall as well.
[Nexus Player Q&A, Help & Troubleshooting] Andrew H:
"Bootloop of Death"

My Nexus Player died about the same time as everyone else on here. I figured maybe it was a hardware issue and today I took it apart to re-flow it with a torch.

No avail there, so I searched and found this article, and yep, just about the same time as everyone else, it had the bootloop of death. I didn't really notice it at first, so I just let it go overnight. The next day I was going to start it up in recovery mode so I can try to roll it back, but it was too late. Unit was dead.

If the thing wasn't so cheap on Ebay to get a new one, I'd be complaining, but I think I'll just find another streaming solution. Chromecast is something I used the most on it anyway.
[Nexus Player Q&A, Help & Troubleshooting] justmart:
Add one more. Mine died today after reboot.
[Nexus Player Q&A, Help & Troubleshooting] talon_dgnr8:
Mine is boot looping as we speak. It got to be so sluggish while in use so I restarted it from the menu...then this. I tried unplugging the OTG cable..no joy. I tried unplugging / plugging back in...no joy. I tried wiping data and still boot loop. I came to try a new ROM and hope to reflash it...but I'll try to read through this forum first to see others attempting the same and results. My Nexus Player was stock, no root or unlocked boot loader.
[Nexus Player Q&A, Help & Troubleshooting] Amadeo1759:
Soo....., anyone gonna start a lawsuit of some sort? I don't want to believe this is coincidence. I mean, can it be any more obvious? I think we have all been swindled for our hard earned money. If only there was a way for us to prove that an update from Google or Asus purposely crashed our systems and the company is trying to empty pockets rather than fix the matter
[Nexus Player Q&A, Help & Troubleshooting] a8ksh4:
Hi All, please file a complaint with the Better Business Bureau:

https://www.bbb.org/us/ca/fremont/profile/wholesale-computers/asus-computer-international-1116-16870

When you click to file a complaint, you'll have to search for the business. Use "Fremont, CA", and "Asus" for the search.

This is the text I'm using:
[Nexus Player Q&A, Help & Troubleshooting] a8ksh4:
Probably reiterating the same thing as others already in this thread, but I got an email back from Asus this morning saying:

In other news, I went ahead and opened a BBB complaint with google, as well since Asus is saying it's their responsibility to fix this.
[Nexus Player Q&A, Help & Troubleshooting] BluPhant:
Mine had a few issues (unable to launch apps, like Pluto TV, etc) recently. I had been putting off trying to figure it out, but had gone through basic steps (clear data, try again, uninstall/reinstall apps) with no luck.

This morning it failed to launch an app completely, and rebooted itself. I got bootloop. I was able to eventually use the hardware button to get it into fastboot & flashed the stock Oreo image back to it (wiping in the process). Everything is working now. I wonder if there is some data corruption going on? It's very strange that this is happening all of a sudden. Mine has an unlocked bootloader, but it is otherwise stock.

Since it's working, I'm not downgrading for now, will if it becomes an issue. As a side note here, this NP has only been in use for about a month or so (was NIB in Sept).

-Blu
[Nexus Player Q&A, Help & Troubleshooting] linkboy:
I just turned mine on and the remote was wigging out. Restarted it and it's now bootlooping. First time I've turned it on in a few months (I've got a ShieldTV that I use in my living room), my Nexus Player is in my son's room.

I'm fuming right now.
[Nexus Player Q&A, Help & Troubleshooting] BluPhant:
Is there any consensus here about the root cause? Anecdotally, it seems that people on a previous version of Android appear to be immune, so there appears to be a correlation between Oreo and these issues? I'm not sure what to do about mine, I'm still covered by a seller warranty, so I could theoretically send it back and get it replaced but I'm not sure if a replacement would help the situation. Just looking for some opinion here.

-Blu
[Nexus Player Q&A, Help & Troubleshooting] Takakoma:
Reviví mi Nexus Player...

Hello a Todos...

Les comento que el día de ayer reviví mi Nexus Player.

Utilicé estos tres enlaces:

https://www.androidcentral.com/how-manually-upgrade-pixel-nexus

https://www.xda-developers.com/install-adb-windows-macos-linux/

https://developers.google.com/android/ota

Lean estas instrucciones primero y luego descarguen el programa ADB (https://www.xda-developers.com/install-adb-windows-macos-linux/) y el archivo imagen del Sistema Operativo Android (https://dl.google.com/dl/android/aosp/fugu-ota-opr2.170623.027-401d182e.zip) una vez descargados procedan con las instrucciones.

Deben entrar en el modo de arranque que permite ingresar a una lista de comandos del Nexus Player, esto se logra manteniendo el botón negro pulsado con el Nexus Player desenergizado, luego sin soltar el botón se debe energizar el Nexus Player y aparecerán las opciones, (luego soltar el botón) si no aparecen, deben mantener presionando nuevamente y realizar el mismo procedimiento. Si el Robot aparece, deben presionar el botón negro por unos 4 segundos y volver a soltarlo y aparecerán las funciones.

Seleccionar la opción:

Apply update from ADB

Ahora deben utilizar el programa ADB y mandar un par de comandos vía cable USB al Nexus Player.

Este programa se instala en Windows, MAC o LINUX.

https://www.xda-developers.com/install-adb-windows-macos-linux/

Después este programa se debe abrir en CMD, en el caso de Windows.

Yo lo alojé en C:\adb

Uno de los comandos para saber que el PC se conecta al Nexus Player (en mi caso utilicé Windows 10) es:

C:\adb\adb devices

Este comando entrega un código del Nexus Player.

Si el código alfanumérico aparece en pantalla, es porque el Nexus Player respondió.

Desde este otro enlace se debe bajar el último link perteneciente a Nexus Player Fugu.

https://developers.google.com/android/ota

(https://dl.google.com/dl/android/aosp/fugu-ota-opr2.170623.027-401d182e.zip) este es el archivo a descargar, después yo le cambié el nombre dentro de mi PC a fugu.zip y lo cargué en la carpeta C:\adb

El otro comando es:

C:\adb\adb sideload fugu.zip

Con este comando comenzará la carga del sistema operativo Android en el Nexus Player, desde 0% hasta 100%.

Con estos procedimientos mi Nexus Player revivió...

Saludos a todos, menos a Google...

Paulo
[Nexus Player Q&A, Help & Troubleshooting] sankyou:
Add me to the list. It's too bad no one bought these things or we could do a class-action lawsuit. WAAAAAAY too many instances for this to be a coincidence. After Oreo - my Nexus Player was so slow that it was almost unusable. That was until the point where it really is unusable.
[Nexus Player Q&A, Help & Troubleshooting] MGA2009:
Today I received a refurbished Nexus Player running Android 5.0

Before it got the O update, I runned thru the guide to update it to Android 7.1.2 and avoid Android 8.0 inhope to avoid the sudden death.

I will keep updates to see if my Nexus Player dies or not.
[Nexus Player Q&A, Help & Troubleshooting] BluPhant:
Down(up)graded to Nougat. I couldn't find an OTG dongle, so I found and documented TWRP commands in the downgrade thread. Everything looks good! Hopefully this fixes the issues. Everything seems way quicker in this version as well - didn't think it was slow before, but this just feels better.

-Blu
[Nexus Player Q&A, Help & Troubleshooting] bemoo:
I’m in Europe (Netherlands) with two NP’s. Waiting for things to go sour but so far, everythings still ok.

Am I waiting for something that’s not gonna happen? I even bought a Mi-box just in case.

Anybody know if this is maybe a regional problem?
[Nexus Player Q&A, Help & Troubleshooting] gregfrankenstein:
I guess I'm the only one whose Player hasn't self-destructed. Maybe it's because I've tried LineageOS and then switched back to stock when Kodi didn't work, so perhaps in re-flashing the factory image I've averted whatever OTA update borked everyone. Really though, it's a device from 2014 that stopped receiving support like a year ago. Neither Google nor Asus have any obligation to care. That's just how tech works these days. My laptop has a major security vulnerability in its CPU and Intel won't fix it. Can I file a class action over it? No.
[Nexus Player Q&A, Help & Troubleshooting] macdaddie87:
Your laptop still works so your situation is different. How ever if your personal data with vital info was hacked do to this security flaw then yes you can sue for damages because Intel knows about and refuses to fix the vulnerability. You must be able to prove such a claim but you can sue and win in such case.

Since Asus and Google both refuse to fix do to a update then they should at least replace it with ADT2 since it's no longer in production. We are early adopters of ATV and have supported it every since. There is no other official Google replacement available for sale. They do however have the ADT2.
[Nexus Player Q&A, Help & Troubleshooting] koww:
Guys, my Nexus Player died a couple of months ago. When I plug it in, the white led is solid continuously and can't get it to blink or connect it to my laptops. Any way to make my laptop detect it to downgrade OS on it?
[Nexus Player Q&A, Help & Troubleshooting] x86fanboy:
Hi all,

I'm interested in recreating this problem in a controlled environment, and recording the process as it may be used as evidence.

I have ordered three brand new devices and am awaiting their delivery.

As I don't have any players on me right now, I can't grab the current OTA image (possibly not, read on).

I was under the impression that the devices stopped receiving updates some time back, and the latest images (both factory and OTA) listed on the google developer site are from November 2017.

Given it appears the devices started bricking in August, I'd assume an OTA image was pushed in August of 2018. Does anyone know if this is true?

If not, if the latest image pushed was from November 2017, then we can assume there was something in the Nov 17 image that didn't activate until Aug 2018. I'm thinking something along the lines of the Unix 2038 problem, however instead relevant to August 2018.

It's too much of a coincidence for it to be a mass NAND failure, so I suspect it has something to do with the updates.

Additionally, I suspect this is a two-stage problem. Stage 1: The initial soft-brick, and bootloop.

Eventually, after a device has sat in bootloop for days, if not weeks (Like mine in my old untouched apartment, I suspect), with the governor disabled, Stage 2: I suspect the CPU literally burns itself out.

There's not much I can do until my devices arrive, and there's a chance google will have pulled the OTA by that time (If they haven't already (I've downloaded all the 8.0 images currently on the google dev site)) but if anyone has any totally dead (Stage 2) devices that they've given up all hope for, and wouldn't mind parting with for the sake of investigation, I would be willing to pay shipping if you pulled the motherboard and sent it to me (google "Asus Nexus Player Motherboard Replacement"), as I wish to determine exactly which components are burning out.

I'm as curious as anyone as to what's happening, and if there are any permanent fixes for it, I love my nexus players, I just haven't had a chance to move them to my new apartment and greatly fear one has since died (Used to be listed on android device manager, but alas, no more).

Luckily one was unplugged and has remained off since this all seemed to have started (It may still have the Nov 17 image on it, however), and I have no intention on plugging it back in until we have an absolute, permeant fix.
[Nexus Player Q&A, Help & Troubleshooting] ski522:
I blocked all outbound request for my players, other then https & http and since I only use my player as Kodi and Youtube that has worked fine. I use a Mikrotik router as my Internet connection so I have quite a bit of flexibility with creating necessary FW rules. Outside of ports 80 & 443 I believe updates require and additional port Whether the latter is true or not, both my NP's continue to work.

There are still complaints via this thread https://issuetracker.google.com/issues/114276277 and it sound's like the update creates a brick unit with no ability to recover. I don't think google intentionally meant to update the NP...my guess is google updated androidTV and the NP's accidentally got caught in a bad update.

I think what is really troublesome is that Google has been silent on the issue...Google has turned into what Microsoft was in the 90's & 2000's.
[Nexus Player Q&A, Help & Troubleshooting] kmcd7:
Mine is dead too. Tried factory reset sever times, using slight variations to the process at times, just to be certain. Nothing works. It's fully dead. I think Google may have put something into these units so they would die out at some point. No way for me to verify that.
[Nexus Player Q&A, Help & Troubleshooting] Nate2:
Asus won't let me register my Nexus Player with its serial number with my other registered Asus devices on their site unless I can find a purchase receipt for my Nexus Player (which I can't find).

Great way to disclaim all liability/responsibility for their products.
[Nexus Player Q&A, Help & Troubleshooting] nick25255:
It is because memory leak. Cpu begins work hard and it became warm. So I took my 230 v timer from IKEA and reboot Nexus every day. It works. If you will not reboot it, app will start 30 seconds after weak. So, CPU works hard
[Nexus Player Q&A, Help & Troubleshooting] TheLoonyRebel:
Play Store update that caused the bricking has been pulled months ago. So it's safe to use Oreo again on the Nexus Player. I've been using Oreo on one of mine for the last few days with no issues.
[Nexus Player Q&A, Help & Troubleshooting] mirrin:
Mine died randomly too it was stock running Oreo...
[Nexus Player Q&A, Help & Troubleshooting] elw4chi:
my nexus player, disable wifi and bluetooth, is there any way to revive them?

I appreciate any information you can provide me

i buy with android 8.1, anf setting freeze menu, not working bluetooth and wifi, i unlock bootloader, and restore 7.1 and my nexus player is fast, and buy ugreen usb-UTP but I still do not arrive
[Nexus Player Q&A, Help & Troubleshooting] txtmikhail:
i flashed my dead nexus player back to 6.0 and rooted it and its been working great for me
[Nexus Player Q&A, Help & Troubleshooting] koww:
How did you do it? Can you share instructions?
[Nexus Player Q&A, Help & Troubleshooting] YoshiFan501:
My nexus player is extra dead. When i plug it into my computer, it shows up as the MOOREFIELD bootloader, and i dont know how to get into android from this. Any ideas on how to fix this?