IssueTracker

The Bootloop will eventually kill the nexus player.  One of mine won't even turn on after this.

I have two Nexus Players effected by this. I have had limited luch reflashing the stock OS but it only lasts a few days then boom it dies again.

Mine went out as well, and I can't even get to the bootloader by holding the button on the bottom while starting. It's completely bricked since the last update.

Mine is in a bootloop as of early August. I am currently using a Chromecast Ultra but is very restrictive in it's capabilities and not a viable replacement. No remote and I have a TV tuner which the chromecast can not directly use.

Same problem bootloop.  Can't get into recovery to reset.  Please fix!
On Fri, Sep 7, 2018 at 9:21 AM <buganizer-system@google.com> wrote:

I have the same problem with 2 of my nexus player went into bootloop last month, within days of each other.  happened after OTA to the latest OREO code..   Google, please remove the bad code from OTA, even as I was able to reflash it to 7.1.2, right away it downloaded the bad code after connected to WIFI..

I suggest to google that at a minimum, the bad 8.0 firmware should be removed until this issue resolve so that no more nexus player getting the code via OTA and killed with bootloop issue.

Mine too! Not happy!

One of mine died last week. Unplugged the other until I have tile to block your updates so it doesn't get bricked also.

Mine is 100% hard bricked and nothing but a paperweight now. No OS, Bootloader or Recovery. Very disappointing.

I have 4 Nexus Player bricks from this update.  Two of them are not used frequently and I imagine bootlooped to death as they no longer power on at all.  The other two are used daily and those were caught when they started bootlooping to the recovery screen and may be recoverable if a fix is issued.  None of them will boot up to the home screen though.   Would love to see a fix as the Nexus Players are still better than most boxes on the market.

One of my two Nexus Players have died. Can't get into bootloader. "Reboot to bootloader" in recovery just resets the device, sometimes showing a "no command" screen. In recovery all adb commands results in "error: closed". Only adb command that works is "adb sideload" but all files immediately or at around 50% give a "footer is wrong" "Signature verification failed" error.
Even if this issue is fixed I don't know how currently bricked systems will recover.

Same problem as everyone else. Neither Asus nor Google seem to want to take ownership of this. I cannot fix it from the bootloop at this point and had to go out and purchase a new device because of this.

My nexus player died early August from this same issue.

I have tried multiple "fixes" that are listed as possibilities in the XDA forum for Nexus Players. So far, they have all worked for only 2 days and then it is back to a boot loop.

I have sideloaded Ver.8  multiple times only to have it fail. I've downgraded to 7.1.2 and with instructions within https://forum.xda-developers.com/nexus-player/help/best-nexusplayer-rom-7-1-2-scratch-root-t3820607 , negated the upgrade to Ver 8 and yet it still 2 days later goes into a boot loop.

Using TWRP, it makes a backup but then won't restore it. I wipe everything that TWRP lets me then through it's file manager I see that there are still folders in /system, yet when I ask TWRP to reboot, it warns me that there is no O/S. Fastboot still comes up though and I am able to flash from there. Good for another 2 days....?  

Is there a way to wipe/format everything and still have fastboot? Would need to redefine partitions? If it were a hard disk I would think that I had a head crash that was taking things down, but I don't think that there is anything spinning in there?

Mine soft bricked 3 times after reloading it 7.1.1 and after the third try it stopped working all together. (Problem started beginning of August)

Mine restarted itself about a week or so ago, and after having to hardboot it, now stuck in a bootloop at the black and white Google logo.

Add me to the list. They need to fix this...

Please fix this!

On Fri, Sep 7, 2018, 9:07 PM <buganizer-system@google.com> wrote:

For those that have a non functioning device, are able to flash and know how to flash, can you try the attached image and let us know if it helps?

Flash this as a factory image or through Custom Recovery?

Flash as factory image and data wipe.

Mine also constant Google then black screen!

On Fri, Sep 7, 2018, 8:53 PM <buganizer-system@google.com> wrote:

Same issue here

Still waiting for an option to fix this device. It was your update that broke it. Stuck at splash with blinking.led till it reboots. No fastboot, recovery, nothing. This wasn't caused by any fault of mine, and isn't right that so many people are just out of the devices due to your bad update.

2 nexus players stuck in boot loop here too.

Same here, it's dead,
when trying to go into recovery I see the google logo and then reboots.

Received the following:

error: cannot load 'bootloader-fugu-fugu-02.13.img'
rebooting into bootloader...
OKAY [  0.594s]
finished. total time: 1.199s
< waiting for any device >
W/        ( 4702): Unable to open 'image-fugu-opr2.170623.027.zip': No such file or directory
error: failed to open zip file 'image-fugu-opr2.170623.027.zip': I/O Error

There was no Flash all script . Flash each img individually?

My Nexus player completely died, no lights, no boot, nothing. Power supply is good. Replaced it with my backup that is working fine. Disappointing that after I threw it away that I see others having this issue.

I had noticed mine was behaving oddly for a few days in early August, prior to it dying outright with nearly everyone else's:

When I would switch to the input it was on, it was already in the middle of a reboot for some reason, figured it got a tiny update or something and thought nothing of it.

The day it outright died, it was doing something that looked like a bootloop, it didn't respond to the holding of the button on the underside, so I unplugged the power for ten minutes to see if that would help it get over itself.
I plug it back in, and no status light or anything from the unit. It doesn't appear to have power despite being plugged in.

It's just not the same with a Chromecast; the lack of the remote, the tiny phone screen trying to cast but wireless interference degrades the signal and causes stuttering or lag.

Was hoping that a new model would have come out by now, but…

Same situation with me as well.  Bootloop began sometime in early August and have brought it up in an XDA forum where I was shocked to find I wasn't alone. I never reconfigured anything on my NP, no flashing other operation systems outside of vanilla, and kept it quite grneric.

I really enjoyed this little guy but I can't take the bootloop!  With no explanation in sight?!

I have three nexus players with two already dead.  The devices will not even boot now.  This all started at the beginning of August.  Really hope google figures this out.  Until then I am leaving my third one unplugged.

Please add me to the list of affected customers, my Nexus Player went into a bootloop and doing a factory reset won't fix it.

This is going to affect many Google ecosystem users, forcing me to move to another device may open the door to walking away from Google Services.... Roku? Apple TV?

Add me to the list

Just checking, still nothing I see. Glad to have a paper weight with zero response from Google.

Mine died too. I threw it out and bought a shield. Didn't think anything of it until I started seeing posts pop up everywhere.

Mine too. Black screen with occasional Google logo but nothing else.

This happened to me as well

Same issue here

I have 7 tv boxes same problems

2 nexus player same with same issue

Mine died and now, I have to actually hang out with my wife.

Any movement from Google on this?

Yes, they posted a possible fix a few posts up.

I also have a google Nexus Player dead, won't turn on, no light, nothing. Not even a boot screen. Please fix google!

Having the same issue out of mine. No issues before Oreo.

No flash is gonna fix most of us. Most can't get to bootloader or recovery, so this isn't gonna be as easy as "just flash this zip". This is the dumbest shit.

Is it possible to capture recovery logs. If yes, please follow below steps to retrieve recovery logs:

1) If your phone is ON, turn it OFF.
2) Press and hold these two buttons at the same time until the device turns ON: Volume Down button and Power button.
3) Select “Recovery mode” by using the Volume buttons to navigate and the Power button to select it.
4) In the next screen, while holding down the Power button, press and release the Volume Up button once
5) Select “View Recovery logs”.
6) There might be multiple log files. Start with "/cache/recovery/last_log” to view the log contents.
7) Look for lines like "Finding update package", "Opening update package" etc.
8) If it doesn't contain such lines, continue to the next log file (last_log.1, last_log.2, etc.).
9) Take pictures of the screen to record the logs.
 
Please upload the files to Google Drive: share the folder with android-bugreport@google.com and share the link here.
 
Afterwards, you can recover your device’s system image by following the instructions at:
 
- Factory Image: https://developers.google.com/android/images
- Full OTA: https://developers.google.com/android/ota

This is about the Nexus player, not a phone.....even more funny that the above comment is from Google's employee. You would think they would know their product.

Hold on....the Google employee assigned to this doesn't even know what the Nexus Player is? Whenever this issue first started, and everyone's Nexus Players started dying all at once, I spoke with Google support, and noone seemed to even know what Android TV was. This is sad.

Apologies, please ignore comment #51, was meant for another bug.

We have passed this to the development team and will update this issue with more information as it becomes available.

Based on Google's own prioritization standards, shouldn't this be escalated to P0?

Per https://developers.google.com/issue-tracker/concepts/issues:

"P0:    An issue that needs to be addressed immediately and with as many resources as is required. Such an issue causes a full outage or makes a critical function of the product to be unavailable for everyone, without any known workaround."

Same boat -- Stuck on Google screen. Pretty unhappy this issue has been widespread and going on for more than a month with no resolution.

2 dead Nexus players... UGH......

Passing the buck to the development team.

Since these devices have been bricked (can't even flash them) by whatever update killed them, I'm curious to see how they plan on "fixing" this mess.

On Tue, Sep 11, 2018, 12:10 AM <buganizer-system@google.com> wrote:

On Mon, Sep 10, 2018, 5:59 AM <buganizer-system@google.com> wrote:

Abuhena031097cgc@gmail.com

On Tue, Sep 11, 2018, 12:12 AM Fowziah Hena Tamanna <
abuhena031097cgc@gmail.com> wrote:

My Nexus player has died also because of this issue.

me too

How do you plan on fixing something you can't flash? Tell me a good story, I'm in the mood to need a laugh.

2 Dead Nexus Players here as well. One refuses to enter fastboot or recovery, one will get into recovery, but attempting to sideload image results in:
E3004: This package is for "fugu" devices; this is a "".

No fastboot on that device at all. just goes straight to recovery.

Forgot to attach image of error.

I have one that recently bricked and one that still working. Cross my fingers.

Come on Google! Escalate this outage to P0.!

I switched to Lineage when this first started and it ran fine for a month or so, then turned up in the bootloop...I can flash lineage again through TWRP, but I can not for the life of me get it to boot to fastboot.  adb works fine, but when I give the adb reboot bootloader command it just reboots a couple of times and comes back to TWRP recovery.  Can you make a TWRP compatible zip file of this image?

This ticket isn't about those that flashed some non-stock image on their Nexus Player. You should try XDA.

The problem affects stock and non-stock. I was going to try the proposed fix since my unit is still semi functional.

Read the original post in this ticket to see where this is about stock.

4 players all in loop , come on Google work the problem!

The test image ZIP from Google above states that it requires bootloader FUGU-02.19 in android-info.txt. The bootloader from the most recent factory image is only bootloader-fugu-fugu-02.13.img. Where do we get 2.19 from to even be able to flash the ZIP?

2 players in boot loop, goons switch to shield

Post #21 work consistently for anyone?

3 players dead. Are you even working on a solution Google?

Why isn't this a P0 right now?

Because then they'd have to do something about it.

On Fri, Sep 14, 2018 at 5:56 PM <buganizer-system@google.com> wrote:

another bricked np.  stuck on google loading screen, unplugged it and now its dead

I reflashed mine about 9 days ago, rooted and followed some instruction on the net to prevent auto-update, and it was working working since then until today, it goes on bootloop again.. this is ridiculous..

Completely dead, mid August.

2 out of 3 dead units here :(  i came back from vacation to 1 dead unit and 1 in the boot loop, but during the time that I was looking for answers the 2nd unit died.  Total bricks as far as I can tell, cannot connect to them via adb.  Happy to try anything to get them going again

1 of my two Nexus Players is dead - no light when I plug it in.

add me to the list with 2 none working nexus player :(

Same here 1of my 2 Nexus Players is stuck in a boot loop. Get to the Google screen and then restarts back to it.

My first Nexus Player of the three I own just went into the bootloop mode today. Running stock Oreo 8.0. This needs to be fixed as I did nothing to cause this. You broke it Google. Now fix your mess up.

Fix it Google

I have 2 of 3 that have bit the dust.

My Nexus player also recently died.  This isn't a coincidence, please fix!

Both of my Nexus players died the same day. I used these to monitor my security cameras with tinycam pro..now i have to use a Samsung tablet instead of a monitor. Please fix this!

1 of my 2 Nexus Players also got stuck in the bootloop last month where it can't load the Android system.  Was running the latest Oreo.  Factory reset does not fix it.  It will not boot into bootloader so ADB does not see it to flash an older stock image.

Noticed a few weeks ago that my nexus player had also become stuck in bootloop. Posting to add another confirmed failure of device.

Don't use my device a ton so never noticed it in a boot loop.. just went to use it and found device with light on but unresponsive black screen and blinking remote. Love having my devices nuked from the google mothership......

And crickets from Google, sad...you have turned into Microsoft.

If anyone at Google would like one of these bricked units sent in for testing get in touch.  I'm happy send a couple of mine in.  Since self destructing I've replaced all of them with other hardware and their primary purpose has shifted to duct collecting.

Nearly two weeks later no response from the dev team.  I wonder if the current fire stick has better performance than the nexus player?

I can't tell the difference. Just have to sideload a few apps like Kodi and YouTubeTV. After this wonderful response I think I'm done investing in the google ecosphere.

Great news is I somehow managed to get mine to boot again. Bad news is trying to get into both bootloader and recovery sends it back to bootlooping until I unplug it then replug it in (which in turn sends it back to the main OS).

Add me to the list of folks having an issue.

Died today.. Will not boot.  Cannot get to bootloader.

Mine as will , this is sick.... what's the next step ?

I have now had 2 out of 3 I own die in the last month. This is crazy.

This happened to me at the end of August. It seems like Google is intentionally bricking our devices. My device worked perfectly fine for what I used it for. I'm very disappointed.

I had two of mine died as well. Would really love this to be resolved... I still have one working. Please.

I think we need to escalate this ASAP , whoever opened the case can ask for escalation. I see the Severity is S3 which is the lowest while this is affecting a lot of people.

I am the originator of this case.  I am not able to alter the priority or severity of the issue.  I do get the sense that this issue is being ignored at this point.  I will be watching closely for any statements made at Google's hardware event on October 9th regarding Android TV going forward.  I'd love some public acknowledgement of this debacle in some form or another, but I guess my expectations are pretty low at this point.  I really thought Google was better than this.

Add me to the list of folks having an issue.  my nexus player is die

I have spent a lot of time on the phone and emailing Google and Asus on this issue. When I have called Google they have told me that "Google does not support the Nexus Player". To which I respond , then why do you have a support site for it and why have you released software for it? But honestly the rep on the phone really is not going to help. I have twice tried to escalate my call and each time I was told that there is no manager to take my call and they schedule a call back. However I have never been called back which is quite frustrating. When I email them I get nothing back as well. I'm very surprised at this kind of response by Google, it is not the kind of reaction I expect. However I have made some slight progress with Asus. I have gotten all the way to level 3 support and while the help they are currently giving are things I have already tried at least I'm getting something! My last contact with them was where they asked me to flash the latest OS. I told them that I have tried that and it is not a permanent fix. I'm currently waiting to hear back from that feedback.

I know it might be a pain but all I can say is patience and persistence. Keep calling, keep emailing. Posting on this issue or the other one on the product forums site is not helping from what can tell. So we need to bring it to the front lines. I hope this fuels some of you to not lose faith and to keep trying to get the attention of Google and Asus. Thanks!

Mine is 100% hard bricked. I tried plugging it in and holding the button down and nothing.
No response. No OS, Bootloader or Recovery. Very disappointing.
I never put it in an unlocked Bootloader or anything so I am not sure there is anything I can do.

i got 2 now doing it. i just bought the  2nd one new  and it's only 1 month old and just did it.. not a hardware issue.....

won't turn on at all

I had one go out so I found a brand new one on eBay about a month ago. Working great till last week and the second one took a dump. Was able to flash Nougat back on to it but with the automatic update it only lasted a day and a half before it corrupted again. I gave up and bought a Amazon Fire TV stick which was difficult because I am all in on the Google ecosystem. Both Nexus Players are now paperweights. This is 100% a software issue caused by Google.

I think this is a good call for a class action lawsuit.., Never thought
Google and their support are this low.

On Sun, Sep 30, 2018 at 3:39 PM <buganizer-system@google.com> wrote:

--



*Thanks Natheer Becker*

+1 for bricked after software update

2 bricks. Google, I'll trade them in for a new Chromecast or Android TV box. I know of about 10 other bricks from friends. We need a fix or someway to recoup the value of these systems.

I have 3 as well…I would prefer a software fix personally as I love my NP. Perhaps a website that will allow us to download software to bring them back to life.

 

 

From: buganizer-system@google.com [mailto:buganizer-system@google.com]
Sent: Sunday, September 30, 2018 8:19 PM
To: b-system+-446522008@google.com
Cc: fidel4loans@gmail.com
Subject: Re: Issue 114276277: Android TV update is bricking ASUS Nexus Players worldwide

 

Replying to this email means your email address will be shared with the team that works on this product.


https://issuetracker.google.com/issues/114276277

Changed

re...@gmail.com added comment #118 <https://issuetracker.google.com/issues/114276277#comment118> :
2 bricks. Google, I'll trade them in for a new Chromecast or Android TV box. I know of about 10 other bricks from friends. We need a fix or someway to recoup the value of these systems.

_______________________________


Reference Info: 114276277 Android TV update is bricking ASUS Nexus Players worldwide

component:  Android Public Tracker
status:  Assigned
reporter:  ge...@gmail.com
assignee:  vi...@google.com
cc:  ge...@gmail.com
type:  Bug P3 S3
blocked by:  112286429 <https://issuetracker.google.com/issues/112286429>
hotlist:  [AOSP] assigned <https://issuetracker.google.com/hotlists/468531> , Google Domain <https://issuetracker.google.com/hotlists/710308>



Generated by Google IssueTracker notification system

You're receiving this email because you are subscribed to updates on Google IssueTracker issue 114276277 <https://issuetracker.google.com/issues/114276277>  where you have the role: starred.

Bricked by software update 1+

same here, can't get into recovery anymore, and no output on hdmi
when plugged in to my pc/Mac (tried both) it won't even show up in "adb devices" list

any news about a fix?

Considering how many people are reporting the problem, but Google remains silent, probably time to start reaching out to the media about the issue, maybe that will get Google's attention. While I don't believe this is being done on purpose it is baffling why Google hasn't stopped the update from occurring with NP's that are still working.

I just sent an email to Asus as well https://www.asus.com/us/support/FAQ/1010030/#. Next step is social media campaigning if we don't get adequate responses. I am holding out for the Oct 9 product release from Google, hoping the new Chromecast has full Android TV capability and Google Assistant integration- wait, I already purchased that product, and Google bricked it!

I already emailed ASUS, they said to send it in as it's out of warranty it would cost me. They blamed Google.

Ours died Sunday, 30-Sept. I didn't have time to deal with it until today. It's disappointing to see the extent of the impact this update has caused.
Last night, it was still stuck on the Google logo/screen. I tried holding the button for the boot screen, but no luck.

Please, help Google! If you wanna do a Nexus Player gen 2, that'd be great too.

Since this has been going on since July, I'm not convinced this will ever get attention. <sad>

Same issue here. Reboots/resets don't work.

Same issue here with 2 devices. Hope to get some kind of fix or even acknowledgement soon because this is just disturbing.

Same issue here. Annoying and losing trust in Google.

Running into this issue... I was able to stave it off for a few weeks, but I have to reflash every month!!!!!!!!

This time, I can't even get to a point where I can reflash!!!

PLEASE FIX THIS!!!!

Enough is enough. Shared to several Android tech sites, blogs, and news outlets.

https://plus.google.com/+KenGreenwood/posts/BvG5hg1Hre3

Imagine that - a new Mi Box is being announced after Google killed everyone's NP. And still not a word from Google about this mess. It really might be time to discuss a class action....

Seriously. Strange how I've had 3 Google devices have a compromising issue surface right before new devices are released. New chromecast was leaked recently

2 out of 3 are dead.  Keeping the third one unplugged in case there is a fix of some sort.

Just curious, has anybody on here contacted a lawyer yet?

I do hope Google sucks it up and does something about this. Electronics do have short shelf life these days but killing off a 4-year-old working product is probably not the best for its long-term image...

Maybe google should fucking call Asus and they just redirect each other into a black hole. Shitties support ever. I can't wait till the Nexus 6p class action lawsuits and the future lawsuit for Nexus player. Can't use the battery as an excuse this time.

Mine died as well.

Another dead one here.. Died in Aug, I think, but I just discovered all of hte forum, reddit, etc, threads about the bricked devices.

Mine stopped booting at all.
No way to even enter recovery.

My daughter's and nephew's both crapped out around the same time. What a
shame. WAS a wonderful device.

On Sat, Oct 13, 2018 at 12:26 PM <buganizer-system@google.com> wrote:

Got one stuck on bootloop. Google send me the new mi box and we'll call it even!

Mine just died. I was literally just using it earlier today. Came in and turned the TV on, Nexus Player was unresponsive. Tried unplugging it and plugging it back in and it won't even turn on now.

Add me to the list for a bricked Nexus Player.

Add me to the list too. Currently functioning as a paperweight.

Bricked device +1

Just lost my 2nd nexus player.  Can't believe they're still pushing this update that bricks these devices.  Any word from Google on this yet?

I've got 2 bricked devices.

Bricked device +1 starting around August.

Went on vacation and came back to a bricked device, tried to recover by instructions and it made it worse. Google is a shit company with poor employees, they have no idea what they are doing. Amazon is much better my device still works with them.

Super disappointed in google on this one as I too have a bricked nexus player as well thanks to the horrible oreo update they tried to push!!  PLEASE fix this GOOGLE!!!!!

2 units dead.  One is still alive running version 8.  But for how long.

Also dead. It happened some two or three months ago but I haven't had the time to look into it until this weekend when I was reading about flashing it or possible options to restore and I stumbled upon this. Seems I'm not the only one that got into the fatal bootloop. No fastboot is available.

I also had two die within a week.  I tried everything to revive them but neither would respond.  I finally gave up, threw both in the trash and reluctantly bought a Shield and a Mi box.

I could understand if an update caused an operational issue and we had an option to downgrade.  For at least my two, there was no downgrade, no access to bootloader, no anything.  This isn't random nor a coincidence for all these devices to die within a month of each other.

Do you guys think we should draft a letter and everyone here send it via certified mail to Google HQ?.

Do it up and I'll send one in. Also, is there a specific news outlet that we could get to bring this to national attention?

Created Nexus product help forum, I think will hear more on the other side.

link
https://productforums.google.com/forum/#!topic/nexus/rcQeY6EuoVU;context-place=forum/nexus

Mine went down end of August after the update as well.


I had to laugh when I saw this today.
https://electronics.woot.com/offers/asus-nexus-player-8gb-black

On Mon, Oct 22, 2018 at 10:31 AM <buganizer-system@google.com> wrote:

--
Jeff Simmons, OD, MBA
Optometrist

Taylor Optical / Healthy Eyes for Life
m: 801.662.9466
e: jeffsimmonsod@gmail.com

The content of this email is confidential and intended for the recipient
specified in message only. It is strictly forbidden to share any part of
this message with any third party, without a written consent of the sender.
If you received this message by mistake, please reply to this message and
follow with its deletion, so that we can ensure such a mistake does not
occur in the future.

I bought replacements for my two dead units.  But I will not be using them until google commits to a fix for the issue.

-Matt

Hey Guys, Looks like there is a thread with Nexus Hardware support is going on for a while and Google employee is replying in the thread. Let's participate in that case.

Link to the thread.

https://productforums.google.com/forum/#!topic/nexus/Ski0fFZ0pZM;context-place=forum/nexus

Mine died last week. Will not power on. Draws 0.2Watts when plugged in but nothing happens. No lights no boot.

Hello...
El mío también murió
Soy de Chile
Saludos...

Add me to the list, my nexus player died today.
Black Screen and the white led on, strangely it's listed as a device I can cast to on my phone. If I cast to it I can hear audio but the screen stays black.

-Payton

My second one just went bootlooping. This one was New in Box at the beginning of August so it doesn't seem to be related to the flash wearing out.

I've been tempted to buy a 'new' one, but for that very reason I have not. Apparently the problem is still not fixed, even almost 3 months later from when mine bit the dust. Unbelievable, makes me wonder if it's deliberate!

I have two Nexus Players on Android 8.0 that I depend upon as a cordcutter with two small children. I used microSD to ethernet devices to connect to my router so I never had the intermittent WiFi drops experienced by others.  Now, both appear to have a similar bootloop issue that others have described and though I am not getting any display whatsoever. I have tried resetting to factory defaults but the device will not even respond to a reset with the button on the underside held and power plugged in.  I have tried using software tools (the Nexus Root Toolkit by Wugsoft) to re-flash the device on which I had unlocked the bootloader (the other had never been unlocked) but it will not go into fastboot mode to be recognized by the computer nor will it show any video or audio.  I have contacted Asus "support" and they want more than the value of the device to look at it and refer me back to Google support channels for any software issues, which is how they view this situation.

This is the second set of Google/Android TV devices that has burned me after the Sony model NSZ-GS8 was discontinued in a single year on Android Honeycomb.  I'm am shocked and appalled at the level of support that Google has given to the Google TV and now the Android TV platform.  Can't Google commit to something as technologically inclined as entertainment?  This is the kind of support we all grew to expect and resent from Microsoft for 25 years...   After the device was end-of-lifed in March I thought I'd see sales channels die out for this device, but there are still multiple channels on Ebay as well as overseas stores that still have stock on this product.   That is not an end-of-life product if the channels are still marketing it and making money on its sale.  I have felt strongly about supporting the idea of Google TV/ Android TV, but I'm getting tired of having the company who sold me the product decide when it dies.  If I wanted to be manipulated like that, I'd give up any self respect and buy an iPhone.

Not sure how to star this.  But my nexus player has been killed as well. Hopefully google makes this right, glad I didn't pull the trigger on the pixel 3.

As reported earlier, my first Nexus player died in August with the corrupt Android system error and the factory reset option does nothing to fix the problem.  I can't get it to fastboot to re-flash a factory image.  My second Nexus player lasted until yesterday where it locked up on the screensaver.  It started bootlooping on the Google logo after restart.  After the problem with the first one, and finding this thread, I had enabled USB debugging on the second one in anticipation of it getting bricked also.  I was able to use the Nexus Root Toolkit to flash it back to stock Nougat this morning but it updated to Oreo before I could lookup how to stop the updates.  So far it is operating normally again, but I don't have any confidence that it will last.  I now have to use the Samsung TV apps to cover for the loss of the first one and Chromecasts aren't family friendly enough to replace the second.  I bought these and peripherals to get away from Apple TV, but may have to go back.

Chromecast Ultra with the option to boot into Android TV would have been an ideal Nexus Player replacement.

My Nexus Player is not working properly with recent update, remote control and voice is not functioning properly.

Mine won't boot at all. Can't do the bootloader method, completely stuck.

@Assignee it's been almost 2 months without a feedback or even a comment: can we please get something ?

What do we have to do to get a damn response?

Some devices are getting killed because of some killer release being pushed: how is it P3 & S3 ???

This needs to be p0 like NOW.