Assigned
Status Update
Comments
ks...@gmail.com <ks...@gmail.com> #2
The Bootloop will eventually kill the nexus player. One of mine won't even turn on after this.
dc...@gmail.com <dc...@gmail.com> #3
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.
de...@gmail.com <de...@gmail.com> #4
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.
ya...@gmail.com <ya...@gmail.com> #5
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.
he...@gmail.com <he...@gmail.com> #6
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:
On Fri, Sep 7, 2018 at 9:21 AM <buganizer-system@google.com> wrote:
an...@gmail.com <an...@gmail.com> #7
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..
an...@gmail.com <an...@gmail.com> #8
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.
ry...@gmail.com <ry...@gmail.com> #9
Mine too! Not happy!
ad...@gmail.com <ad...@gmail.com> #10
One of mine died last week. Unplugged the other until I have tile to block your updates so it doesn't get bricked also.
kc...@gmail.com <kc...@gmail.com> #11
Mine is 100% hard bricked and nothing but a paperweight now. No OS, Bootloader or Recovery. Very disappointing.
an...@gmail.com <an...@gmail.com> #12
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.
ma...@gmail.com <ma...@gmail.com> #13
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.
Even if this issue is fixed I don't know how currently bricked systems will recover.
om...@gmail.com <om...@gmail.com> #14
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.
[Deleted User] <[Deleted User]> #15
My nexus player died early August from this same issue.
gr...@gmail.com <gr...@gmail.com> #16
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 withinhttps://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?
I have sideloaded Ver.8 multiple times only to have it fail. I've downgraded to 7.1.2 and with instructions within
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?
ju...@gmail.com <ju...@gmail.com> #17
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)
jg...@gmail.com <jg...@gmail.com> #18
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.
ga...@gmail.com <ga...@gmail.com> #19
Add me to the list. They need to fix this...
al...@gmail.com <al...@gmail.com> #20
da...@google.com <da...@google.com> #21
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?
ks...@gmail.com <ks...@gmail.com> #22
Flash this as a factory image or through Custom Recovery?
da...@google.com <da...@google.com> #23
Flash as factory image and data wipe.
da...@gmail.com <da...@gmail.com> #24
Mine also constant Google then black screen!
On Fri, Sep 7, 2018, 8:53 PM <buganizer-system@google.com> wrote:
On Fri, Sep 7, 2018, 8:53 PM <buganizer-system@google.com> wrote:
el...@gmail.com <el...@gmail.com> #25
Same issue here
ke...@gmail.com <ke...@gmail.com> #26
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.
da...@gmail.com <da...@gmail.com> #27
2 nexus players stuck in boot loop here too.
to...@gmail.com <to...@gmail.com> #28
Same here, it's dead,
when trying to go into recovery I see the google logo and then reboots.
when trying to go into recovery I see the google logo and then reboots.
ks...@gmail.com <ks...@gmail.com> #29
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
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
ks...@gmail.com <ks...@gmail.com> #30
There was no Flash all script . Flash each img individually?
mo...@gmail.com <mo...@gmail.com> #31
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.
mo...@gmail.com <mo...@gmail.com> #32
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…
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…
ed...@gmail.com <ed...@gmail.com> #33
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 really enjoyed this little guy but I can't take the bootloop! With no explanation in sight?!
js...@vt.edu <js...@vt.edu> #34
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.
[Deleted User] <[Deleted User]> #35
<purged>
ri...@gmail.com <ri...@gmail.com> #36
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?
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?
kl...@gmail.com <kl...@gmail.com> #37
Add me to the list
re...@gmail.com <re...@gmail.com> #38
Just checking, still nothing I see. Glad to have a paper weight with zero response from Google.
an...@gmail.com <an...@gmail.com> #39
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.
he...@gmail.com <he...@gmail.com> #40
Mine too. Black screen with occasional Google logo but nothing else.
gh...@gmail.com <gh...@gmail.com> #41
This happened to me as well
cc...@gmail.com <cc...@gmail.com> #42
Same issue here
za...@gmail.com <za...@gmail.com> #43
I have 7 tv boxes same problems
im...@gmail.com <im...@gmail.com> #44
2 nexus player same with same issue
na...@gmail.com <na...@gmail.com> #45
Mine died and now, I have to actually hang out with my wife.
ga...@gmail.com <ga...@gmail.com> #46
Any movement from Google on this?
cr...@gmail.com <cr...@gmail.com> #47
Yes, they posted a possible fix a few posts up.
jh...@gmail.com <jh...@gmail.com> #48
I also have a google Nexus Player dead, won't turn on, no light, nothing. Not even a boot screen. Please fix google!
ve...@gmail.com <ve...@gmail.com> #49
Having the same issue out of mine. No issues before Oreo.
ke...@gmail.com <ke...@gmail.com> #50
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.
vi...@google.com <vi...@google.com>
vi...@google.com <vi...@google.com> #51
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
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:
- Full OTA:
vi...@gmail.com <vi...@gmail.com> #52
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.
om...@gmail.com <om...@gmail.com> #53
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.
vi...@google.com <vi...@google.com> #54
Apologies, please ignore comment #51 , was meant for another bug.
vi...@google.com <vi...@google.com> #55
We have passed this to the development team and will update this issue with more information as it becomes available.
ty...@gmail.com <ty...@gmail.com> #56
Based on Google's own prioritization standards, shouldn't this be escalated to P0?
Perhttps://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."
Per
"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."
jd...@gmail.com <jd...@gmail.com> #57
Same boat -- Stuck on Google screen. Pretty unhappy this issue has been widespread and going on for more than a month with no resolution.
mu...@gmail.com <mu...@gmail.com> #58
2 dead Nexus players... UGH......
te...@gmail.com <te...@gmail.com> #59
Passing the buck to the development team.
om...@gmail.com <om...@gmail.com> #60
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.
ab...@gmail.com <ab...@gmail.com> #61
ab...@gmail.com <ab...@gmail.com> #62
ab...@gmail.com <ab...@gmail.com> #63
Abuhena031097cgc@gmail.com
On Tue, Sep 11, 2018, 12:12 AM Fowziah Hena Tamanna <
abuhena031097cgc@gmail.com> wrote:
On Tue, Sep 11, 2018, 12:12 AM Fowziah Hena Tamanna <
abuhena031097cgc@gmail.com> wrote:
ri...@gmail.com <ri...@gmail.com> #64
My Nexus player has died also because of this issue.
br...@gmail.com <br...@gmail.com> #65
me too
ke...@gmail.com <ke...@gmail.com> #66
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.
ra...@gmail.com <ra...@gmail.com> #67
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.
E3004: This package is for "fugu" devices; this is a "".
No fastboot on that device at all. just goes straight to recovery.
ra...@gmail.com <ra...@gmail.com> #68
Forgot to attach image of error.
ka...@gmail.com <ka...@gmail.com> #69
I have one that recently bricked and one that still working. Cross my fingers.
cr...@gmail.com <cr...@gmail.com> #70
Come on Google! Escalate this outage to P0.!
an...@gmail.com <an...@gmail.com> #71
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?
om...@gmail.com <om...@gmail.com> #72
This ticket isn't about those that flashed some non-stock image on their Nexus Player. You should try XDA.
an...@gmail.com <an...@gmail.com> #73
The problem affects stock and non-stock. I was going to try the proposed fix since my unit is still semi functional.
om...@gmail.com <om...@gmail.com> #74
Read the original post in this ticket to see where this is about stock.
si...@gmail.com <si...@gmail.com> #75
4 players all in loop , come on Google work the problem!
ro...@gmail.com <ro...@gmail.com> #76
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?
rm...@gmail.com <rm...@gmail.com> #77
2 players in boot loop, goons switch to shield
ga...@gmail.com <ga...@gmail.com> #78
Post #21 work consistently for anyone?
Al...@yahoo.com <Al...@yahoo.com> #79
3 players dead. Are you even working on a solution Google?
om...@gmail.com <om...@gmail.com> #80
Why isn't this a P0 right now?
mu...@gmail.com <mu...@gmail.com> #81
Because then they'd have to do something about it.
On Fri, Sep 14, 2018 at 5:56 PM <buganizer-system@google.com> wrote:
On Fri, Sep 14, 2018 at 5:56 PM <buganizer-system@google.com> wrote:
le...@gmail.com <le...@gmail.com> #82
another bricked np. stuck on google loading screen, unplugged it and now its dead
an...@gmail.com <an...@gmail.com> #83
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..
ch...@gmail.com <ch...@gmail.com> #84
Completely dead, mid August.
tr...@casaroberts.com <tr...@casaroberts.com> #85
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
ma...@gmail.com <ma...@gmail.com> #86
1 of my two Nexus Players is dead - no light when I plug it in.
jg...@gmail.com <jg...@gmail.com> #87
add me to the list with 2 none working nexus player :(
di...@gmail.com <di...@gmail.com> #88
Same here 1of my 2 Nexus Players is stuck in a boot loop. Get to the Google screen and then restarts back to it.
de...@gmail.com <de...@gmail.com> #89
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.
am...@gmail.com <am...@gmail.com> #90
Fix it Google
ke...@gmail.com <ke...@gmail.com> #91
I have 2 of 3 that have bit the dust.
da...@gmail.com <da...@gmail.com> #92
My Nexus player also recently died. This isn't a coincidence, please fix!
cl...@gmail.com <cl...@gmail.com> #93
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!
er...@gmail.com <er...@gmail.com> #94
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.
ul...@gmail.com <ul...@gmail.com> #95
Noticed a few weeks ago that my nexus player had also become stuck in bootloop. Posting to add another confirmed failure of device.
ow...@gmail.com <ow...@gmail.com> #96
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......
ba...@gmail.com <ba...@gmail.com> #97
And crickets from Google, sad...you have turned into Microsoft.
an...@gmail.com <an...@gmail.com> #98
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.
te...@gmail.com <te...@gmail.com> #99
Nearly two weeks later no response from the dev team. I wonder if the current fire stick has better performance than the nexus player?
ga...@gmail.com <ga...@gmail.com> #100
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.
de...@gmail.com <de...@gmail.com> #101
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).
st...@gmail.com <st...@gmail.com> #102
Add me to the list of folks having an issue.
vi...@gmail.com <vi...@gmail.com> #103
Died today.. Will not boot. Cannot get to bootloader.
na...@gmail.com <na...@gmail.com> #104
Mine as will , this is sick.... what's the next step ?
ze...@zebproctor.com <ze...@zebproctor.com> #105
I have now had 2 out of 3 I own die in the last month. This is crazy.
ry...@gmail.com <ry...@gmail.com> #106
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.
yk...@gmail.com <yk...@gmail.com> #107
I had two of mine died as well. Would really love this to be resolved... I still have one working. Please.
na...@gmail.com <na...@gmail.com> #108
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.
ge...@gmail.com <ge...@gmail.com> #109
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.
ko...@gmail.com <ko...@gmail.com> #110
Add me to the list of folks having an issue. my nexus player is die
do...@gmail.com <do...@gmail.com> #111
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!
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!
ja...@gmail.com <ja...@gmail.com> #112
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.
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.
ab...@gmail.com <ab...@gmail.com> #113
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.....
ga...@gmail.com <ga...@gmail.com> #114
won't turn on at all
dm...@gmail.com <dm...@gmail.com> #115
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.
na...@gmail.com <na...@gmail.com> #116
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:
Google and their support are this low.
On Sun, Sep 30, 2018 at 3:39 PM <buganizer-system@google.com> wrote:
--
*Thanks Natheer Becker*
an...@gmail.com <an...@gmail.com> #117
+1 for bricked after software update
re...@gmail.com <re...@gmail.com> #118
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.
fi...@gmail.com <fi...@gmail.com> #119
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.
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:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
re...@gmail.com added
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 <
hotlist: [AOSP] assigned <
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
sh...@gmail.com <sh...@gmail.com> #120
Bricked by software update 1+
to...@gmail.com <to...@gmail.com> #121
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?
when plugged in to my pc/Mac (tried both) it won't even show up in "adb devices" list
any news about a fix?
ba...@gmail.com <ba...@gmail.com> #122
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.
de...@gmail.com <de...@gmail.com> #123
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!
li...@gmail.com <li...@gmail.com> #124
I already emailed ASUS, they said to send it in as it's out of warranty it would cost me. They blamed Google.
sp...@rocketmail.com <sp...@rocketmail.com> #125
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>
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>
ro...@gmail.com <ro...@gmail.com> #126
Same issue here. Reboots/resets don't work.
sh...@gmail.com <sh...@gmail.com> #127
Same issue here with 2 devices. Hope to get some kind of fix or even acknowledgement soon because this is just disturbing.
al...@gmail.com <al...@gmail.com> #128
Same issue here. Annoying and losing trust in Google.
da...@gmail.com <da...@gmail.com> #129
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!!!!
This time, I can't even get to a point where I can reflash!!!
PLEASE FIX THIS!!!!
ke...@gmail.com <ke...@gmail.com> #130
om...@gmail.com <om...@gmail.com> #131
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....
ch...@gmail.com <ch...@gmail.com> #132
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
ra...@gmail.com <ra...@gmail.com> #133
2 out of 3 are dead. Keeping the third one unplugged in case there is a fix of some sort.
ga...@gmail.com <ga...@gmail.com> #134
Just curious, has anybody on here contacted a lawyer yet?
la...@gmail.com <la...@gmail.com> #135
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...
ch...@gmail.com <ch...@gmail.com> #136
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.
br...@gmail.com <br...@gmail.com> #137
Mine died as well.
no...@gmail.com <no...@gmail.com> #138
Another dead one here.. Died in Aug, I think, but I just discovered all of hte forum, reddit, etc, threads about the bricked devices.
ma...@gmail.com <ma...@gmail.com> #139
Mine stopped booting at all.
No way to even enter recovery.
No way to even enter recovery.
ri...@gmail.com <ri...@gmail.com> #140
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:
shame. WAS a wonderful device.
On Sat, Oct 13, 2018 at 12:26 PM <buganizer-system@google.com> wrote:
sc...@gmail.com <sc...@gmail.com> #141
Got one stuck on bootloop. Google send me the new mi box and we'll call it even!
b....@gmail.com <b....@gmail.com> #142
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.
ja...@gmail.com <ja...@gmail.com> #143
Add me to the list for a bricked Nexus Player.
da...@gmail.com <da...@gmail.com> #144
Add me to the list too. Currently functioning as a paperweight.
jm...@gmail.com <jm...@gmail.com> #145
Bricked device +1
je...@gmail.com <je...@gmail.com> #146
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?
fi...@gmail.com <fi...@gmail.com> #147
I've got 2 bricked devices.
ma...@gmail.com <ma...@gmail.com> #148
Bricked device +1 starting around August.
at...@gmail.com <at...@gmail.com> #149
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.
dr...@gmail.com <dr...@gmail.com> #150
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!!!!!
ma...@gmail.com <ma...@gmail.com> #151
2 units dead. One is still alive running version 8. But for how long.
da...@gmail.com <da...@gmail.com> #152
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.
mi...@gmail.com <mi...@gmail.com> #153
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.
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.
na...@gmail.com <na...@gmail.com> #154
Do you guys think we should draft a letter and everyone here send it via certified mail to Google HQ?.
mu...@gmail.com <mu...@gmail.com> #155
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?
je...@gmail.com <je...@gmail.com> #157
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:
I had to laugh when I saw this today.
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.
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.
ma...@gmail.com <ma...@gmail.com> #158
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
-Matt
na...@gmail.com <na...@gmail.com> #159
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
Link to the thread.
co...@gmail.com <co...@gmail.com> #160
Mine died last week. Will not power on. Draws 0.2Watts when plugged in but nothing happens. No lights no boot.
pa...@ipl.cl <pa...@ipl.cl> #161
Hello...
El mío también murió
Soy de Chile
Saludos...
El mío también murió
Soy de Chile
Saludos...
pa...@gmail.com <pa...@gmail.com> #162
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
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
mr...@gmail.com <mr...@gmail.com> #163
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.
ry...@gmail.com <ry...@gmail.com> #164
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!
kk...@gmail.com <kk...@gmail.com> #165
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.
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.
ba...@gmail.com <ba...@gmail.com> #166
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.
er...@gmail.com <er...@gmail.com> #167
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.
Chromecast Ultra with the option to boot into Android TV would have been an ideal Nexus Player replacement.
pu...@gmail.com <pu...@gmail.com> #168
My Nexus Player is not working properly with recent update, remote control and voice is not functioning properly.
ge...@gmail.com <ge...@gmail.com> #169
Mine won't boot at all. Can't do the bootloader method, completely stuck.
ju...@gmail.com <ju...@gmail.com> #170
@Assignee it's been almost 2 months without a feedback or even a comment: can we please get something ?
ja...@gmail.com <ja...@gmail.com> #171
What do we have to do to get a damn response?
ju...@gmail.com <ju...@gmail.com> #172
Some devices are getting killed because of some killer release being pushed: how is it P3 & S3 ???
ks...@gmail.com <ks...@gmail.com> #173
This needs to be p0 like NOW.
jo...@hotmail.com <jo...@hotmail.com> #174
It have also bricked my Nexus Player. All I see is Google logo , endless loop trying to boot.
Please help us resolve this.
Please help us resolve this.
ma...@gmail.com <ma...@gmail.com> #175
Google please communicate with us and at least let us know we are being heard. I will also offer my two dead units if it helps.
di...@gmail.com <di...@gmail.com> #176
The same problem, black screen.
jo...@gmail.com <jo...@gmail.com> #177
My nexus google player died too.
ar...@gmail.com <ar...@gmail.com> #178
Mine died too -- after plugging it in, the light never blinks an no signal is output over HDMI. I tried booting into fastboot/recovery by holding the button while plugging it in, but the light still didn't blink and my computer didn't find any fastboot devices.
ro...@gmail.com <ro...@gmail.com> #179
I just found this. Exact same symptoms. Stopped working in July. Black screen. This seems like an issue that was caused by a software update. Would like a solution.
ke...@gmail.com <ke...@gmail.com> #180
This needs to be dealt with now.... Forced EOL through an update is bull$hit. This isn't a rare case. This is every single Nexus players that connects to the internet takes an update of death. There is no way to fix it either since we have no access to fastboot or recovery, so pony up Google. Make this right.
wi...@gmail.com <wi...@gmail.com> #181
Black screen. Factory reset doesn't work. Count mine as bricked too!
ks...@gmail.com <ks...@gmail.com> #182
So -
I had a few back and forth's with Store Support. Got a case Number and everything. They seemed helpful. But now for a month they have been ignoring me. No response to repeated emails.
Enough is enough google........
I had a few back and forth's with Store Support. Got a case Number and everything. They seemed helpful. But now for a month they have been ignoring me. No response to repeated emails.
Enough is enough google........
ru...@gmail.com <ru...@gmail.com> #183
mine is bricked as well!
el...@gmail.com <el...@gmail.com> #184
Don't bother, Google isn't going to make this right nor will Asus. Don't waste your time like most of us here have
ve...@outlook.com.au <ve...@outlook.com.au> #185
I have been speaking with a friend of mine, a lawyer, he laughed, saying that if it can be proven that google has been pushing updates that aren't just soft-locking, but eventually destroying devices, and that this happens to every single device that's updated, well, just take the number of nexus players sold, multiply it by $99, and there's what both google and asus could be liable to receive as fines.
He's said this would hold up in the EU, as well as Australia, as simple open-and-shut cases; as for the US, well, he suggested anyone in the US seek the professional opinion of a woman named Nasim Aghdam.
Just for fun, I've saved this thread, and are ordering a number of brand new, still sealed nexus players to see if google's update will kill them.
Google, I'd suggest you work out an official stance on this real quick, if it's determined that your updates are destroying (not bricking) the devices (I'm guessing no CPU governor running while booting, and the devices burning themselves out), then you would be liable for destruction of property (among many, many other things).
He's said this would hold up in the EU, as well as Australia, as simple open-and-shut cases; as for the US, well, he suggested anyone in the US seek the professional opinion of a woman named Nasim Aghdam.
Just for fun, I've saved this thread, and are ordering a number of brand new, still sealed nexus players to see if google's update will kill them.
Google, I'd suggest you work out an official stance on this real quick, if it's determined that your updates are destroying (not bricking) the devices (I'm guessing no CPU governor running while booting, and the devices burning themselves out), then you would be liable for destruction of property (among many, many other things).
ba...@gmail.com <ba...@gmail.com> #186
People could try email bombing ASUS to move on the issue with Google...I'm sure they have better direct contacts then everyone here trying to reach someone via phone/email. This page contains email addresses contact info for ASUS.
https://www.elliott.org/company-contacts/asus/
th...@gmail.com <th...@gmail.com> #187
Another sad Nexus Player owner. No display/audio, and holding down the reset button does nothing on screen. I have a light on the bottom, and I've tested other devices and know that my HDMI cable and port is working, so....... I still have my Nexus 7 OG, and Nexus 7 (2013) working with no issues other than the OG Nexus 7 showing slowness. The 2013 Nexus 7 is still smooth as can be. Love using every once in a while to read books and light browsing. Can you please fix my Nexus Player? I ordered it from the Google Store and would love to see the longevity that my tabs have continue with my Nexus Player. Could you contact me about a replacement, or give a status update for the many who are having similar issues? I have 2 4th Gen Apple TVs that work great for everyone else in my family, but I'm the only Android user here. May Google be With You.
ko...@gmail.com <ko...@gmail.com> #188
I won 2 asus nexus players. Now both won't do shit. WTF Goggle
ko...@gmail.com <ko...@gmail.com> #189
*own
mg...@gmail.com <mg...@gmail.com> #190
I have one that lost Bluetooth and WiFi, The other glitches all the time and drops the WiFi every 15-30 mins (nothing else in the house does). Seems like since I updated to Oreo they have been programmed to die.
sg...@gmail.com <sg...@gmail.com> #191
Add me to the list. Black screen, can't reset, bricked.
vt...@gmail.com <vt...@gmail.com> #192
Black creek after update +1, unit bricked!!
ib...@gmail.com <ib...@gmail.com> #193
Fixed
ib...@gmail.com <ib...@gmail.com> #194
Fix issues
in...@gmail.com <in...@gmail.com> #195
How did you fix it?
cb...@gmail.com <cb...@gmail.com> #196
troll comment
ks...@gmail.com <ks...@gmail.com> #197
I bought mine from the google store and been going back and forth for MONTHS with the Help Desk folks.
They have stated there is nothing they can do and to contact ASUS. After informing them...again..and again...and again, that asus only refers it back to google. They said Sorry. I have repeatedly asked for it to be elevated to p-0. they are winning the war on me...I am tired of this fight. Google is going to make me go....apple...yuck
They have stated there is nothing they can do and to contact ASUS. After informing them...again..and again...and again, that asus only refers it back to google. They said Sorry. I have repeatedly asked for it to be elevated to p-0. they are winning the war on me...I am tired of this fight. Google is going to make me go....apple...yuck
kk...@gmail.com <kk...@gmail.com> #198
I have two Nexus Players bricked after software updates in October. Hadn't realized there was a problem or I would have stuck with the first 8.0 update. Now both are bricked. One can light the LED, one not, neither has any output via HDMI nor can I access either via adb. These are still better players than most other streamers on the market. Would really like some kind of solution. I left them stock so I could avoid potential problems like this. I wish now I had rooted and loaded with LineageOS. First my Nexus 6P and now this...
sg...@gmail.com <sg...@gmail.com> #199
Add me to the Pucked list. Found mine stuck in a bootloop back in Sept. I unplugged it, then plugged it back in and got nothing.
I tried to re flash it but it won't connect adb. LED doesn't light up. Verified the power supply is working. It's bricked. Really sucks.
Only found out a month ago this was a worldwide issue from a Reddit thread. $60 to ship back to ASUS? Ha ha, yeah right. Can get a Mi box for less than that.
Hoping Google/ASUS can make this right. Leaving a bad taste in my mouth for AndroidTV. This thing should have went legacy/obsolete before bricking itself.
I tried to re flash it but it won't connect adb. LED doesn't light up. Verified the power supply is working. It's bricked. Really sucks.
Only found out a month ago this was a worldwide issue from a Reddit thread. $60 to ship back to ASUS? Ha ha, yeah right. Can get a Mi box for less than that.
Hoping Google/ASUS can make this right. Leaving a bad taste in my mouth for AndroidTV. This thing should have went legacy/obsolete before bricking itself.
st...@gmail.com <st...@gmail.com> #200
Mines done also
sa...@gmail.com <sa...@gmail.com> #201
Done and bricked. Clearly intentional by Asus.
Will be the last Asus product I ever buy.
Will be the last Asus product I ever buy.
[Deleted User] <[Deleted User]> #202
delete
st...@gmail.com <st...@gmail.com> #203
So I'm thinking of filling small claims. Just to see what happens..
Seems they should be responsible..
Seems they should be responsible..
ve...@outlook.com.au <ve...@outlook.com.au> #204
I have purchased three brand new nexus players and am currently testing them to see if I can find specifically what is causing the devices to bootloop and eventually burn out.
I'd say hold off your claims and lawsuits for a while, if I can generate some evidence from this, the process should be much simpler.
I'd say hold off your claims and lawsuits for a while, if I can generate some evidence from this, the process should be much simpler.
sg...@gmail.com <sg...@gmail.com> #205
I bought a Nexus 6 phone right before I purchased the Nexus player. The phone doesn't get updates anymore, not even security patches, for over a year now.
So why did the Nexus players get OTA updates when they weren't supported anymore? Personally, I'm glad they were still being updated, but not like this!
#204 I hope you figure it out. Thanks!
So why did the Nexus players get OTA updates when they weren't supported anymore? Personally, I'm glad they were still being updated, but not like this!
#204 I hope you figure it out. Thanks!
so...@gmail.com <so...@gmail.com> #206
My Nexus Player is stuck in bootloop as well. I cannot get to recovery.
ja...@gmail.com <ja...@gmail.com> #207
I found my Nexus Player wasn't working in first week of August 2018, so I rebooted it to a bootloop, then stopped responding (bricked) shortly thereafter while attempting to boot to recovery. Now, the power LED comes on but no HDMI signal and can't ADB to it.
dl...@gmail.com <dl...@gmail.com> #208
Mine is dead too
rk...@gmail.com <rk...@gmail.com> #209
Weeks after the update it turned my nexus player into a paperweight also. This has definitely been a caused problem by googles update.
bl...@gmail.com <bl...@gmail.com> #210
My player turns on, but nothing comes out on the screen. Computer doesn't even recognize an input. tried to leave the bottom button press to go into commands, but it doesn't show anything on the screen. This happens randomly. had stock firmware.
om...@gmail.com <om...@gmail.com> #211
Google's lack of response has shown they don't care one single bit about it's users.
ep...@gmail.com <ep...@gmail.com> #212
Would be nice if Google would ever speak out for all of us stuck with completely dead players. It was entirely their fault and they are clearly hoping that by ignoring the issue completely we'll just eventually go away. >:(
he...@gmail.com <he...@gmail.com> #213
3 bricked within weeks of each other last year.
ac...@gmail.com <ac...@gmail.com> #214
RIP another stock Nexus Player here die, so this is it?
I wondering what would happen with my Sony 1000$ tv would they die too? Google this is robbery!!!!
Similar situation with my pixels 2 phones tons of hardware malfunction
I wondering what would happen with my Sony 1000$ tv would they die too? Google this is robbery!!!!
Similar situation with my pixels 2 phones tons of hardware malfunction
ro...@gmail.com <ro...@gmail.com> #215
Has google provided a fix or offered anything for this issue?
ma...@gmail.com <ma...@gmail.com> #216
Yes, would be nice to hear from Google itself.
I really like my Nexus player while it worked. And it is clearly the system update that killed the device, and no word from Google.
Very upsetting
I really like my Nexus player while it worked. And it is clearly the system update that killed the device, and no word from Google.
Very upsetting
sn...@gmail.com <sn...@gmail.com> #217
HEY! I have successfully connected my bricked player to the Intel xFSTK Flashing tool. The device is detected as an Intel Moorefield SoC. I am pretty confident we can flash firmware on this assuming we can get it to boot into the bootloader. (unless the bootloop has actually corrupted the hardware) I believe the only thing I am missing is the FW DNX file for the Fugu/Nexus Player (usually called dnx_fwr.bin) and I think this file is specific to the platform. I tried a file from the Asus Zenfone which is also Moorefield platform.
ga...@gmail.com <ga...@gmail.com> #218
If you get it working please post a guide!
sn...@gmail.com <sn...@gmail.com> #219
So hopefully someone from Google will check this and see if they can get the proper dnx_fwr.bin file. The Intel flash tool requires this file plus an ifwi.bin file that I have seen inside of some of the OTAs along with the bootloader. I think if you provide these files, it will boot the nexus player into fastboot and then you can flash one of the factory images. I am going to reach out to ASUS as well and see if they can provide the file. The ASUS Zenfone dnx_fwr.bin seems to partially kick off and then gives an error indicating perhaps something is not signed properly.
da...@gmail.com <da...@gmail.com> #220
Is this something we can pull from someone with a working device?
________________________________
From: buganizer-system@google.com
Sent: Wednesday, March 27, 2019 13:39
To: b-system+-398792221@google.com
Cc: danjng@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
sn...@gmail.com added comment #219 <https://issuetracker.google.com/issues/114276277#comment219 >:
So hopefully someone from Google will check this and see if they can get the proper dnx_fwr.bin file. The Intel flash tool requires this file plus an ifwi.bin file that I have seen inside of some of the OTAs along with the bootloader. I think if you provide these files, it will boot the nexus player into fastboot and then you can flash one of the factory images. I am going to reach out to ASUS as well and see if they can provide the file. The ASUS Zenfone dnx_fwr.bin seems to partially kick off and then gives an error indicating perhaps something is not signed properly.
_______________________________
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 >
duplicate issue: 118204383<https://issuetracker.google.com/issues/118204383 >
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.
________________________________
From: buganizer-system@google.com
Sent: Wednesday, March 27, 2019 13:39
To: b-system+-398792221@google.com
Cc: danjng@gmail.com
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
sn...@gmail.com added
So hopefully someone from Google will check this and see if they can get the proper dnx_fwr.bin file. The Intel flash tool requires this file plus an ifwi.bin file that I have seen inside of some of the OTAs along with the bootloader. I think if you provide these files, it will boot the nexus player into fastboot and then you can flash one of the factory images. I am going to reach out to ASUS as well and see if they can provide the file. The ASUS Zenfone dnx_fwr.bin seems to partially kick off and then gives an error indicating perhaps something is not signed properly.
_______________________________
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<
duplicate issue: 118204383<
hotlist: [AOSP] assigned<
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
sn...@gmail.com <sn...@gmail.com> #221
I don't think the dnx_fwr.bin is something you can pull from the device. As near as I can tell, it's the Download And Execute firmware file. It's something to do with the Intel SoC that the Nexus Player uses. There's a bunch of threads on people reviving the Asus Zenfone using this. The Asus Zenfone actually uses the same Intel SoC I believe. I think we just need the right one for the Nexus Player hardware. I could be totally off there. I am pretty sure the right combination of files and the Intel XFSTK Downloader will revive our players assuming the continuous bootlooping doesn't somehow damage the hardware permanently. That would be pretty shocking to me though.
ks...@gmail.com <ks...@gmail.com> #223
Yup -
I will get $10 as they replaced mine with a pixel xl (shot craps after a year)
HEY GOOGLE - Another one coming for the nexus player.
I will get $10 as they replaced mine with a pixel xl (shot craps after a year)
HEY GOOGLE - Another one coming for the nexus player.
sn...@gmail.com <sn...@gmail.com> #224
What's stupid is, they can most likely fix this if we can get a copy of the firmware in a format that allows us to load it with the Intel flash tool.
ks...@gmail.com <ks...@gmail.com> #225
One of mine would be Fixable -
The other Boot looped itself to death . The Software update came through when i was on vacation .
The other Boot looped itself to death . The Software update came through when i was on vacation .
sn...@gmail.com <sn...@gmail.com> #226
I honestly wonder if both would be fixable. I have one that doesn't boot into anything at all, but I can still flash it with the Intel Flash Tool. It shows up and I can talk to it and I can flash it with firmware but since I don't have the right firmware the Nexus Player returns an error when it sends over the firmware.
al...@gmail.com <al...@gmail.com> #227
Add me to the list.
ks...@gmail.com <ks...@gmail.com> #228
vi...@google.com - Is anything being done? This was assigned you on September 9th 2019.
You have done NOTHING (that we can see)
You have done NOTHING (that we can see)
om...@gmail.com <om...@gmail.com> #229
Google doesn't care. I've had a support ticket open on this for months, and after a dozen calls and emails they sent me a very short email simply said it's no longer under warranty. I've sent daily emails since then asking for a phone call, and they won't even respond.
st...@gmail.com <st...@gmail.com> #230
@ https://issuetracker.google.com/issues/114276277#comment221
Extended boot looping can damage the hardware. Thermal throttling on this device does not start until later in the boot process when the OS is loaded which can lead to thermal damage. At that point the device will be a complete brick.
Extended boot looping can damage the hardware. Thermal throttling on this device does not start until later in the boot process when the OS is loaded which can lead to thermal damage. At that point the device will be a complete brick.
sn...@gmail.com <sn...@gmail.com> #231
It's just sad really. Someone has/had these files. Asus closed the ticket on it too.
ni...@gmail.com <ni...@gmail.com> #232
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
ma...@gmail.com <ma...@gmail.com> #233
This is really disappointing that google has not responded. I started off with 3 units and two of them have died. They currently have no display at all. I have a few more new in box units sitting in storage waiting on a solution. I do not want them to become bricks. I would really like to use these devices. Has anyone come up with reliable brick prevention?
cr...@gmail.com <cr...@gmail.com> #234
According to an earlier tech support statement, the crippling update has been discontinued, so your new Nexus Players are safe to go online now,
co...@gmail.com <co...@gmail.com> #235
Well, that's nice for those whose player has not been killed off already.
jo...@xybrcode.com <jo...@xybrcode.com> #236
So if we can get to ADB can we flash with one of these images?
https://developers.google.com/android/images#fugu
Which ones are safe?
Which ones are safe?
ma...@gmail.com <ma...@gmail.com> #237
Can someone provide a link to the information about the bad update being pulled. Does anyone know what the update was?
de...@gmail.com <de...@gmail.com> #238
I believe it was one of the Google service updates on Play Store.
cr...@gmail.com <cr...@gmail.com> #239
This is the link to the Reddit thread where the top comment indicates the offending update had been discontinued.
https://www.reddit.com/r/nexusplayer/comments/a761pt/quick_update/
ro...@gmail.com <ro...@gmail.com> #240
I was affected by this issue, and my device will not power on. Is Google replacing units because their faulty software update caused an overheat failure?
ju...@gmail.com <ju...@gmail.com> #241
Nope, they are ignoring it in hopes that we just go away.
dj...@gmail.com <dj...@gmail.com> #242
Same issue here, dead Nexus Player, now I don't have a streaming player in my bedroom.
de...@gmail.com <de...@gmail.com> #243
One cool thing discovered with the Nexus Player remote- paired with a Chromebook you can not only navigate slides but play and pause embedded videos! Paired with my pixel phone, the mic button activates the assistant. So at least the remote is still useful!
ed...@gmail.com <ed...@gmail.com> #244
I've had 2 Nexus Players fail within a week of each other. The white led turns on but the HDMI never turns on. Hard reset doesn't work.
dl...@gmail.com <dl...@gmail.com> #245
Mine died last September. Same issue described above. Still waiting for someone to come up with a fix
st...@gmail.com <st...@gmail.com> #246
Been almost a year since this was opened.. last hardware device I'll be buying from Google.
ty...@gmail.com <ty...@gmail.com> #247
Same. I ended up switching to Roku and despite the Google homes plummeting in price I will not trust another piece of Google hardware ever again.
ke...@gmail.com <ke...@gmail.com> #248
Priority changed from p3 to p1.
I'd really like to see some movement here.
I'd really like to see some movement here.
na...@gmail.com <na...@gmail.com> #249
My Nexus player was working around 7/2019.
It was running Android 8.0, IIRC.
It has been turned off since then (I have a Roku and Amazon fireTV).
Is it safe to turn on my Google Nexus Player now (10/2019), or do I risk bricking it?
I had auto app updates turned off.
It was running Android 8.0, IIRC.
It has been turned off since then (I have a Roku and Amazon fireTV).
Is it safe to turn on my Google Nexus Player now (10/2019), or do I risk bricking it?
I had auto app updates turned off.
da...@gmail.com <da...@gmail.com> #250
@#249 I would say no. Mine had been off for a number of months, hooked it back up today, it was working fine for a while but then then rebooted to the recovery screen, factory reset is no help.
To add insult to injury, when I first turned it on I had to re-login. That generated a "Welcome to your new Nexus Player" email from Google. The email declined to mention the device would be bricked within 30 minutes, apparently due to a bad update that Google knows about but has not fixed (or stopped/blocked) in over a year!?
I ordered a FireTV stick the last Prime Day that I had not opened yet, doing that and hooking up now.
Adios AndroidTV!
To add insult to injury, when I first turned it on I had to re-login. That generated a "Welcome to your new Nexus Player" email from Google. The email declined to mention the device would be bricked within 30 minutes, apparently due to a bad update that Google knows about but has not fixed (or stopped/blocked) in over a year!?
I ordered a FireTV stick the last Prime Day that I had not opened yet, doing that and hooking up now.
Adios AndroidTV!
vi...@google.com <vi...@google.com> #251
Our Engineering team is still working on this issue. We will provide more updates as they become available.
sg...@gmail.com <sg...@gmail.com> #252
Thank you for the update. Glad to see it's still being looked at. Mine has been DOA for over a year now, but I still have it in the box.
co...@gmail.com <co...@gmail.com> #253
That's all fine and dandy, but what about those of us whose players were completely killed by the OS update?" No Power, No USB connection. Nothing.
so...@gmail.com <so...@gmail.com> #254
Google is replacing bricked Home Minis quickly. We are sitting here over a year later with no answers or replacements.
sa...@gmail.com <sa...@gmail.com> #255
#251 It's 14 months later. There's no one looking at this issue. We're not idiots.
ja...@gmail.com <ja...@gmail.com> #256
Who cares what your Engineering team is doing...Your Sales team needs to be refunding people their money. This is highway robbery. There needs to be some action here. Don't be evil!
ke...@gmail.com <ke...@gmail.com> #257
Here it is December 1st, and we are all still ghosted on this issue. If our hardware just died of old age, that'd be one thing, but the fact that an update killed em all, it feels like an organized hit job, that you guys feel you can ignore and people will just move on. I assure you, I'm still watching.
vi...@google.com <vi...@google.com>
ga...@gmail.com <ga...@gmail.com> #258
Sweet, hope the new engineer is an intern!
ke...@gmail.com <ke...@gmail.com> #259
And we wait....
st...@gmail.com <st...@gmail.com> #260
This issue alone has pushed me to moving onto another competitors eco system.. yeah it's a pain in moving, but if a company can release software that destroys a purchase and then ignore the issue for over a year, why even be in bed with them.
I don't envy you new engineer guy / baton holder / whoever.. but....
I don't envy you new engineer guy / baton holder / whoever.. but....
co...@gmail.com <co...@gmail.com> #261
Not expecting resolution. They've cleared out a balance of $260 from my Google play store gift cards. Claims they were Google rewards credits and won't do anything. They were from 2013 so of course I don't have a receipt.
sa...@gmail.com <sa...@gmail.com> #262
Anyone expecting resolution is seriously deluded.
They're doing exactly what they wanted which is to wait and let it die.
They're doing exactly what they wanted which is to wait and let it die.
co...@gmail.com <co...@gmail.com> #263
Yeah I don't know why anyone even cares at this point this device is completely obsolete. 1gb ram is not enough to run virtually any modern media streaming apps ontop of the OS and whatever other background processes are going on. It was showing its age back when this issue tracker was made by now its literally a paper weight regardless of its actual functional status.
ke...@gmail.com <ke...@gmail.com> #264
We care because these devices didn't die of old age. The hardware didn't fail. They took an update and were killed. Without the update they were working for what we used em for just fine. If it was a cellphone, a laptop, or hell, an mp3 player, we'd have just as much of a right to be angry. Hardware failure is one thing. A botched update (forcefully pushed out to our devices) is another.
ke...@gmail.com <ke...@gmail.com> #265
It didn't die, and any kind of beta testing before pushing the update would've seen that there was an issue. They killed the devices. It wasn't EOL or it wouldn't have gotten an update in the first place. That's how it works.
sn...@gmail.com <sn...@gmail.com> #266
Since Google literally killed our hardware, it would be nice to have it replaced. I would be more than happy with an adt-2 or adt-3.
bi...@gmail.com <bi...@gmail.com> #267
b....@gmail.com <b....@gmail.com> #268
Or even just a voucher for a Chromecast. Anything other than a dead piece
of hardware in a drawer.
On Tue, Dec 10, 2019, 7:08 PM <buganizer-system@google.com> wrote:
of hardware in a drawer.
On Tue, Dec 10, 2019, 7:08 PM <buganizer-system@google.com> wrote:
ga...@gmail.com <ga...@gmail.com> #269
Is it sad we still haven't tossed the hardware in hope Google will actually own up to their mistake?
ze...@zebproctor.com <ze...@zebproctor.com> #270
I know a huge group of ppl who won't be buying this:
The Verge: Google built its own tiny HDMI 2.1 box to jump-start ‘the next generation of Android TV’.
https://www.theverge.com/2019/12/10/21004376/google-adt-3-android-tv-10-update-set-top-hdmi-2-1
The Verge: Google built its own tiny HDMI 2.1 box to jump-start ‘the next generation of Android TV’.
om...@gmail.com <om...@gmail.com> #271
Yep, I can't won't purchase any Android TV product, unless Google does what
is right. Still got my puck in a drawer, along with the game controller for
it.
On Wed, Dec 11, 2019, 3:17 PM <buganizer-system@google.com> wrote:
is right. Still got my puck in a drawer, along with the game controller for
it.
On Wed, Dec 11, 2019, 3:17 PM <buganizer-system@google.com> wrote:
an...@gmail.com <an...@gmail.com> #272
People, give it up. This thread is hopeless. Google doesn't care and has
moved on.
--
Andrew
On Wed, Dec 11, 2019, 4:34 PM <buganizer-system@google.com> wrote:
moved on.
--
Andrew
On Wed, Dec 11, 2019, 4:34 PM <buganizer-system@google.com> wrote:
yk...@gmail.com <yk...@gmail.com> #273
Yup, I had 4 of these players and a bunch of controllers. Two at least were bricked. I have since moved on to Nvidia Shields (bought most of them second hand) and never looked back. It's not right that Google is not making it right... but honestly it was getting slow and once you use shield you can't use Nexus player anymore, it gets annoying. By the way, the game controllers can be used with any Android system - phones, tablets, or Nvidia Shield so those work just fine. I wish Google would offer some kind of closure in this case, but I don't see it happening.
ma...@gmail.com <ma...@gmail.com> #274
Please google give us some update. I have multiple units with this condition sitting in storage. At least give us some play store credit for our inconvenience.
-Matt
-Matt
ja...@gmail.com <ja...@gmail.com> #275
+1. Haven't used my Nexus Player in well over a year. Discovered a couple days ago that it had become unplugged at some point, so tried to start it up and... stuck at white Google screen and unable to get into bootloader. Reflashing back to 7.x is way more trouble than it's worth. Feel completely ripped off of the $100 purchase price; no way have we gotten that much value out of it yet (main use is on other devices).
st...@gmail.com <st...@gmail.com> #276
Another month of radio silence. Is anyone looking at this? Why is this being ignored?
ks...@gmail.com <ks...@gmail.com> #277
I think its best we all move on - Google yet again has screwed its early adapter - aka beta testers.
ks...@gmail.com <ks...@gmail.com> #279
Would Take
ke...@gmail.com <ke...@gmail.com> #280
I'm in.
om...@gmail.com <om...@gmail.com> #281
Yep, Google could do the right thing here, but we know they won't.
On Thu, Jan 30, 2020, 4:06 PM <buganizer-system@google.com> wrote:
On Thu, Jan 30, 2020, 4:06 PM <buganizer-system@google.com> wrote:
da...@gmail.com <da...@gmail.com> #282
Now if we could only get Google to read this thread and accommodate...
On Thu, Jan 30, 2020 at 5:09 PM <buganizer-system@google.com> wrote:
On Thu, Jan 30, 2020 at 5:09 PM <buganizer-system@google.com> wrote:
kk...@gmail.com <kk...@gmail.com> #283
Actually this article regarding the ADT-3 Android TV streaming box (https://9to5google.com/2020/01/30/buy-android-10-tv-adt-3 ) was updated yesterday to include "Update 1/31: It’s important to note that Netflix and Amazon Prime Video will not be available on ADT-3. This was reliably confirmed on Twitter today and borne out by past ADT units. Developer devices usually don’t receive the proper certifications from streaming providers to permit access." Thus, even if we were to get ADT-3 development units swapped one to one for every Nexus Player we own (and I have two, one bricked and bootlooping, one completely unresponsive with no LED) it would not be an equivalent since the dominant two streaming platforms wouldn't be available. I'd rather have a discount on an Nvidia Shield or even a Mi Box, which are at least available in the regular channel of US commerce (Wal-Mart), nominally quality controlled, and cheap. I can't imagine that Google couldn't negotiate with Xiaomi and get us an exclusive discount price in exchange for something. Alternatively, I own a Shield and it's by far the best Android TV experience I've used but Nvidia probably doesn't have anything to gain in particular from Google. Seems to me Asus bears a good amount of responsibility for this mistake as well, but they don't have any equivalent offerings to my knowledge -- though if they had a stockpile of Nexus 7s somewhere, I'd gladly take a 2013 LTE version since they'll run Android Q.
The only other thing that might get this moving is (and this is not a threat but a theoretical discussion) is to organize a class action suit. That's what finally caused Google to acknowledge problems with the Nexus 6P (which I also own)https://phandroid.com/2020/01/24/nexus-6p-settlement-payments-of-up-to-400-will-be-made-by-march-11th/ Here's the attendant Reddit discussion about the settlement https://www.reddit.com/r/Nexus6P/comments/etlelb/nexus_6p_settlement_payments_of_up_to_400_will_be/
The only other thing that might get this moving is (and this is not a threat but a theoretical discussion) is to organize a class action suit. That's what finally caused Google to acknowledge problems with the Nexus 6P (which I also own)
om...@gmail.com <om...@gmail.com> #284
Maybe we should go ahead with a class action lawsuit at this point. That'll
be the only way to get Google to step up after all of this time. There's
plenty of evidence out there. I'll start looking into how to get that
started if everyone else would be interested.
On Sat, Feb 1, 2020, 2:20 PM <buganizer-system@google.com> wrote:
be the only way to get Google to step up after all of this time. There's
plenty of evidence out there. I'll start looking into how to get that
started if everyone else would be interested.
On Sat, Feb 1, 2020, 2:20 PM <buganizer-system@google.com> wrote:
ok...@gmail.com <ok...@gmail.com> #285
It's been over a year since my Nexus Player suddenly went dead. I only see the LED lights up every time I plug in the power adapter. I waited patiently for a fix from Google. So disappointed. Asus and/or Google needs to fix this!
sa...@gmail.com <sa...@gmail.com> #286
There are no plans to fix this now or at any point in the future.
The bricking was likely intentional.
The bricking was likely intentional.
tb...@gmail.com <tb...@gmail.com> #287
Assuming the last comment is opinion and not fact... I hardly believe that a company with that level of profit would disregard so many people.
ks...@gmail.com <ks...@gmail.com> #288
They Did assign it as a priority 1 - So there is some hope..... Not sure how severity is only a 3 though - Couldn't much more severe short of the units bursting into flames.
ty...@gmail.com <ty...@gmail.com> #289
wish they would fix this.
de...@gmail.com <de...@gmail.com> #290
It's pretty clear from the lack of response that Google or ASUS isn't wanting or caring to fix this issue.
ga...@gmail.com <ga...@gmail.com> #291
Yup, pretty obvious the user base was not large enough so they dgaf.
he...@gmail.com <he...@gmail.com> #292
Hi, Google: It's Thursday, June 4, 2020 and you bricked our Nexus Players two years ago and did nothing about it. Thanks.
sg...@gmail.com <sg...@gmail.com> #293
At this point in time, I'd accept a Play store credit. Then I can take it out by the lake and see how many "skips" I can get out of it.
C'mon Google & ASUS, close the book on this.
C'mon Google & ASUS, close the book on this.
na...@gmail.com <na...@gmail.com> #294
the funny part this is a P1 issue and no response from them.
ma...@gmail.com <ma...@gmail.com> #295
I still have multiple broken units sitting and waiting a response.
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Thursday, June 4, 2020 11:20 AM
To: b-system+1894702662@google.com
Cc: maddigor@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
<mailto:na...@gmail.com> na...@gmail.com added comment #294 <https://issuetracker.google.com/issues/114276277#comment294 > :
the funny part this is a P1 issue and no response from them.
_______________________________
Reference Info: 114276277 Android TV update is bricking ASUS Nexus Players worldwide
component: Android Public Tracker <https://issuetracker.google.com/components/190923 >
status: Assigned
reporter: ge...@gmail.com <mailto:ge...@gmail.com>
assignee: cc...@google.com <mailto:cc...@google.com>
cc: ge...@gmail.com <mailto:ge...@gmail.com>
type: Bug
priority: P1
severity: S3
blocked by: 112286429 <https://issuetracker.google.com/issues/112286429 >
duplicate issue: 118204383 <https://issuetracker.google.com/issues/118204383 >
hotlist: [AOSP] assigned <https://issuetracker.google.com/hotlists/468531 >
retention: Component default
ReportedBy: User
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.
Unsubscribe from this issue. <https://issuetracker.google.com/issues/114276277?unsubscribe=true >
--
This email has been checked for viruses by AVG.
https://www.avg.com
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Thursday, June 4, 2020 11:20 AM
To: b-system+1894702662@google.com
Cc: maddigor@gmail.com
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
<mailto:na...@gmail.com> na...@gmail.com added
the funny part this is a P1 issue and no response from them.
_______________________________
Reference Info: 114276277 Android TV update is bricking ASUS Nexus Players worldwide
component: Android Public Tracker <
status: Assigned
reporter: ge...@gmail.com <mailto:ge...@gmail.com>
assignee: cc...@google.com <mailto:cc...@google.com>
cc: ge...@gmail.com <mailto:ge...@gmail.com>
type: Bug
priority: P1
severity: S3
blocked by: 112286429 <
duplicate issue: 118204383 <
hotlist: [AOSP] assigned <
retention: Component default
ReportedBy: User
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue. <
--
This email has been checked for viruses by AVG.
ma...@gmail.com <ma...@gmail.com> #296
Another thought is everyone respond to this thread and see if we can get some attention.
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Thursday, June 4, 2020 11:20 AM
To: b-system+1894702662@google.com
Cc: maddigor@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
<mailto:na...@gmail.com> na...@gmail.com added comment #294 <https://issuetracker.google.com/issues/114276277#comment294 > :
the funny part this is a P1 issue and no response from them.
_______________________________
Reference Info: 114276277 Android TV update is bricking ASUS Nexus Players worldwide
component: Android Public Tracker <https://issuetracker.google.com/components/190923 >
status: Assigned
reporter: ge...@gmail.com <mailto:ge...@gmail.com>
assignee: cc...@google.com <mailto:cc...@google.com>
cc: ge...@gmail.com <mailto:ge...@gmail.com>
type: Bug
priority: P1
severity: S3
blocked by: 112286429 <https://issuetracker.google.com/issues/112286429 >
duplicate issue: 118204383 <https://issuetracker.google.com/issues/118204383 >
hotlist: [AOSP] assigned <https://issuetracker.google.com/hotlists/468531 >
retention: Component default
ReportedBy: User
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.
Unsubscribe from this issue. <https://issuetracker.google.com/issues/114276277?unsubscribe=true >
--
This email has been checked for viruses by AVG.
https://www.avg.com
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Thursday, June 4, 2020 11:20 AM
To: b-system+1894702662@google.com
Cc: maddigor@gmail.com
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
<mailto:na...@gmail.com> na...@gmail.com added
the funny part this is a P1 issue and no response from them.
_______________________________
Reference Info: 114276277 Android TV update is bricking ASUS Nexus Players worldwide
component: Android Public Tracker <
status: Assigned
reporter: ge...@gmail.com <mailto:ge...@gmail.com>
assignee: cc...@google.com <mailto:cc...@google.com>
cc: ge...@gmail.com <mailto:ge...@gmail.com>
type: Bug
priority: P1
severity: S3
blocked by: 112286429 <
duplicate issue: 118204383 <
hotlist: [AOSP] assigned <
retention: Component default
ReportedBy: User
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue. <
--
This email has been checked for viruses by AVG.
ke...@gmail.com <ke...@gmail.com> #297
This ain't going anywhere. My 2 have been toast this issue first started showing up. Been commenting regularly to try to keep some focus on this issue, but no one cares. Shameful.
om...@gmail.com <om...@gmail.com> #298
Google simply doesn't care. They would have done something, anything, by
now if they were gonna do so.
On Thu, Jun 4, 2020, 10:26 AM <buganizer-system@google.com> wrote:
now if they were gonna do so.
On Thu, Jun 4, 2020, 10:26 AM <buganizer-system@google.com> wrote:
co...@gmail.com <co...@gmail.com> #299
Mine is still sitting in a drawer. Google either needs to tell use what they are going to do to remediate this (play store credit or credit toward their upcoming chromecast device or something) or they need to tell us they are not doing anything and we need to suck it up. Either one is better than telling us nothing and leaving this issue open to pretend like it is being worked on.
re...@gmail.com <re...@gmail.com> #300
Let us trade in for the new google "Sabrina" Android TV dongle!
On Thu, Jun 4, 2020, 10:28 AM <buganizer-system@google.com> wrote:
On Thu, Jun 4, 2020, 10:28 AM <buganizer-system@google.com> wrote:
sa...@gmail.com <sa...@gmail.com> #301
Time to move on folks. It's been two years.Their inaction IS the decision. They don't have to come out and say it. File their actions away when you ponder whether to buy another Google product and make your own decisions.
pa...@gmail.com <pa...@gmail.com> #302
I think google has moved on, and just don't care. I have 2 that died and moved on to firetv and a Shield.
om...@gmail.com <om...@gmail.com> #303
Hey Google - this has been P1 for awhile now. What ya gonna do to replace our bricked devices?
cr...@gmail.com <cr...@gmail.com> #304
They ain't going to do anything about this issue.
Google couldn't care less about these dead-in-the-water Nexus Players.
Just don't buy another Google product for the rest of your life.
Seriously...asking Google to make amends for their negligence will result in nothing.
Absolutely nothing.
Move on with your lives!
ve...@outlook.com.au <ve...@outlook.com.au> #305
Well, I'm having trouble reliably killing my nexus players, at least in a consistently repeatable manner.
It seems google cares enough to have killed the update server, to stop further devices from bricking, this may not be a big enough issue for google to bother fixing, as it may just be cheaper for them to send everyone who sooks a Sabrina once it's released.
I don't doubt that if they had another consumer Android TV device, they would have sorted this out ages back, but alas, they've been dragging the chain.
It seems google cares enough to have killed the update server, to stop further devices from bricking, this may not be a big enough issue for google to bother fixing, as it may just be cheaper for them to send everyone who sooks a Sabrina once it's released.
I don't doubt that if they had another consumer Android TV device, they would have sorted this out ages back, but alas, they've been dragging the chain.
ad...@google.com <ad...@google.com> #306
This is a product feature issue; not a developer issue. Our Android Support team will be in contact with you shortly.
In the meantime, here are helpful resources:
ad...@google.com <ad...@google.com>
zm...@google.com <zm...@google.com> #307
We appreciate your help! In most cases, we won't be able to send you an individualized response, but we'll investigate your report and use the information you provide to improve Android.
mo...@gmail.com <mo...@gmail.com> #308
TWO YEARS LATER.
We're still without any actual answers as to WHY.
I've only ever seen Apple Corporation kill off devices with their corporate branding. Until 2018, when Google of all, did just that.
So, I opened mine up.
There's signs of burn marks on the PCB.
From the "CON3001", down to "WCON4301", and the "ITE IT8566E 1432-AXA SC229A" area. (In a circle around where the thermal pad would be situated.)
The thermal pad over the CON3001, which adheres to the dual purpose passive heatsink/mount bracket, something is definitely off about it.
Now, thermal pads, I'm not too familiar with, but the one's I've handled, aren't spongy marshmallows with holes in them.
All the other thermal pads in the unit seem to be fine, but just not this one specifically.
What we know;
The bad 'update' triggered a bootloop that for many of us, went on to continue over a period of time, an overnight scenario is likely; something definitely started cooking in the units that no longer power on. A small handful of others were able to somehow halt this condition, revert the update and go back to a previous version, only to be forced back onto the bad update shortly after. The bad update was eventually pulled with no other news or details.
These units were forcibly given a bad 'update' that forced the oversized hockey pucks to begin to burn themselves out. Literally.
Most of us were smart enough to unplug them when we did.
Who knows how much longer until a fire would've resulted from this.
And Google just keeps playing stupid.
Imagine if all of these were to have caught fire back during the Nexus Player Mass Extinction Event?
We're still without any actual answers as to WHY.
I've only ever seen Apple Corporation kill off devices with their corporate branding. Until 2018, when Google of all, did just that.
So, I opened mine up.
There's signs of burn marks on the PCB.
From the "CON3001", down to "WCON4301", and the "ITE IT8566E 1432-AXA SC229A" area. (In a circle around where the thermal pad would be situated.)
The thermal pad over the CON3001, which adheres to the dual purpose passive heatsink/mount bracket, something is definitely off about it.
Now, thermal pads, I'm not too familiar with, but the one's I've handled, aren't spongy marshmallows with holes in them.
All the other thermal pads in the unit seem to be fine, but just not this one specifically.
What we know;
The bad 'update' triggered a bootloop that for many of us, went on to continue over a period of time, an overnight scenario is likely; something definitely started cooking in the units that no longer power on. A small handful of others were able to somehow halt this condition, revert the update and go back to a previous version, only to be forced back onto the bad update shortly after. The bad update was eventually pulled with no other news or details.
These units were forcibly given a bad 'update' that forced the oversized hockey pucks to begin to burn themselves out. Literally.
Most of us were smart enough to unplug them when we did.
Who knows how much longer until a fire would've resulted from this.
And Google just keeps playing stupid.
Imagine if all of these were to have caught fire back during the Nexus Player Mass Extinction Event?
om...@gmail.com <om...@gmail.com> #309
The thermal damage due to the boot loop is what got most of everyone.
Google's lack of concern on this one is frustrating. I had called Google
Support multiple times and eventually they flagged my account to where the
reps were told to not discuss anything concerning this with me.
Google needs to replace everyone's NP that they killed. Just because the
device was older, doesn't mean they should be allowed to kill it.
On Wed, Sep 23, 2020, 6:35 AM <buganizer-system@google.com> wrote:
Google's lack of concern on this one is frustrating. I had called Google
Support multiple times and eventually they flagged my account to where the
reps were told to not discuss anything concerning this with me.
Google needs to replace everyone's NP that they killed. Just because the
device was older, doesn't mean they should be allowed to kill it.
On Wed, Sep 23, 2020, 6:35 AM <buganizer-system@google.com> wrote:
ks...@gmail.com <ks...@gmail.com> #310
I love that this got bumped to Priority 1 - and then NOTHING......ass clowns
ma...@gmail.com <ma...@gmail.com> #311
It would be nice if they would give us the new chrome cast they are about
to release. I have at least 2 dead units sitting in a box. I am still
hoping they will do something for us.
On Thu, Sep 24, 2020 at 9:42 PM <buganizer-system@google.com> wrote:
to release. I have at least 2 dead units sitting in a box. I am still
hoping they will do something for us.
On Thu, Sep 24, 2020 at 9:42 PM <buganizer-system@google.com> wrote:
co...@gmail.com <co...@gmail.com> #312
Frankly, I would take a "Sorry, tough luck" and them closing this issue than them continuing to ignore the issue and us.
But a replacement device or a good discount toward a replacement would be prefered.
But a replacement device or a good discount toward a replacement would be prefered.
ja...@gmail.com <ja...@gmail.com> #313
There is a new chromecast coming out soon. What if we collectively purchase them from the Google store, and "return" them with the Nexus player in it's place? One could go as far as printing this entire thread and putting it in the box. Maybe, just maybe someone at Google will give a shit.
bi...@gmail.com <bi...@gmail.com> #314
I've already replaced my 2 bricked Nexus Players with 3 Nvidia Shield TV
Pro's. After the Android 11 update hard bricked my Pixel 3 XL (won't turn
on at all), I'm not interested in anything else Made by Google puts out in
the future, including the new Chromecast with Android TV. No more Pixel
phones, no more Pixelbooks, no more Chromecasts, no more Nest cameras, no
more Nest Homes, etc. I've even cancelled Youtube TV, YouTube Music and
Stadia, and will be cancelling Google One, Google Cloud and Nest Aware once
I migrate everything.
There isn't enough time in life to worry about a crap software update
bricking your perfectly good working hardware well before it's useful end
of life and Google's total lack of support.
On Mon, Sep 28, 2020, 7:45 PM <buganizer-system@google.com> wrote:
Pro's. After the Android 11 update hard bricked my Pixel 3 XL (won't turn
on at all), I'm not interested in anything else Made by Google puts out in
the future, including the new Chromecast with Android TV. No more Pixel
phones, no more Pixelbooks, no more Chromecasts, no more Nest cameras, no
more Nest Homes, etc. I've even cancelled Youtube TV, YouTube Music and
Stadia, and will be cancelling Google One, Google Cloud and Nest Aware once
I migrate everything.
There isn't enough time in life to worry about a crap software update
bricking your perfectly good working hardware well before it's useful end
of life and Google's total lack of support.
On Mon, Sep 28, 2020, 7:45 PM <buganizer-system@google.com> wrote:
ve...@outlook.com.au <ve...@outlook.com.au> #315
Google admin, you can sensor my message, but that won't stop us from doing it.
Could be fun, but I'd rather return the box of my nexus player instead, or order a pixel phone or something that costs more than my nexus player did and return the nexus player box for that.
Then file a bank chargeback if google refuses the refund.
Google, the hardest part here is that everyone feels like they've been left in the dark, silence is deafening, and we're desperate for something that'd force you to respond.
Respond before we get any ideas.
A simple "Yeah free chromecast with Google TV for everyone who's sooking" would be enough to shut us up.
If it weren't for nexus player owners Android TV would have been DOA, and this is how we end up getting treated.
What, your lawyers have said not to bother unless someone files a class action?
Or some tech youtuber makes a video on this stuff that gets a few million views?
Could be fun, but I'd rather return the box of my nexus player instead, or order a pixel phone or something that costs more than my nexus player did and return the nexus player box for that.
Then file a bank chargeback if google refuses the refund.
Google, the hardest part here is that everyone feels like they've been left in the dark, silence is deafening, and we're desperate for something that'd force you to respond.
Respond before we get any ideas.
A simple "Yeah free chromecast with Google TV for everyone who's sooking" would be enough to shut us up.
If it weren't for nexus player owners Android TV would have been DOA, and this is how we end up getting treated.
What, your lawyers have said not to bother unless someone files a class action?
Or some tech youtuber makes a video on this stuff that gets a few million views?
de...@gmail.com <de...@gmail.com> #316
It sucks that this bricking issue happened. Thankfully I only had one of my three Nexus Players bricked which ASUS replaced after I contacted them and made a strong case that what happened is not my fault and all I wanted was an working unit. ASUS understood and made an exception for me. This was several years ago so I doubt ASUS would still do that. But I also get why Google removed the post with the suggestion of committing fraudulent actions. Google is in their rights to do that. Likewise Google isn't going to suddenly out of goodwill replace bricked Nexus Players with the new Chromecast (Sabrina). Class action lawsuit? Over an device that is far long discontinued and even Lineage support is dropped from it? Yeah okay I doubt it'll get anywhere in court but good luck with that.
ry...@gmail.com <ry...@gmail.com> #317
I'm sure a class action lawsuit on this imminent. I also had a perfectly
working Nexus player that was bricked by this update. I think it'll be much
cheaper just to give everybody affected by this a Chromecast with Google TV
than to go to court.
On Tue, Sep 29, 2020, 1:17 PM <buganizer-system@google.com> wrote:
working Nexus player that was bricked by this update. I think it'll be much
cheaper just to give everybody affected by this a Chromecast with Google TV
than to go to court.
On Tue, Sep 29, 2020, 1:17 PM <buganizer-system@google.com> wrote:
he...@gmail.com <he...@gmail.com> #318
I've given my three bricked Nexus Players little outfits and a backstory so
they can actually serve some earthly function by keeping me entertained.
They're a nice Nexus Player family with hopes and dreams. Coronavirus has
strained them a bit but who among us can't relate to that?
On Wed, Sep 30, 2020 at 11:46 AM <buganizer-system@google.com> wrote:
they can actually serve some earthly function by keeping me entertained.
They're a nice Nexus Player family with hopes and dreams. Coronavirus has
strained them a bit but who among us can't relate to that?
On Wed, Sep 30, 2020 at 11:46 AM <buganizer-system@google.com> wrote:
st...@gmail.com <st...@gmail.com> #319
At this point I'm so frustrated with the response to this I'm actively telling anyone who will listen to avoid Google Devices. As the "tech" resource for my family and friends I can at least take pleasure in knowing I haven't driven others into this rotten eco system, and have diverted a few sales over to Roku. It's not much but it's honest work.
Over two years.. two years this issue has been open and ignored.
I recommend others do the same, share you experience and help friends and family steer clear of future offerings.
Over two years.. two years this issue has been open and ignored.
I recommend others do the same, share you experience and help friends and family steer clear of future offerings.
zm...@google.com <zm...@google.com>
mg...@gmail.com <mg...@gmail.com> #320
Wow great someone new that will do nothing with this ticket. Thanks I guess.
ks...@gmail.com <ks...@gmail.com> #321
But but its P1 now......and has been for ages.....But severity 3 -
How is this severity 3 - I am sitting on Not one but TWO bricked nexus players?
How is this severity 3 - I am sitting on Not one but TWO bricked nexus players?
om...@gmail.com <om...@gmail.com> #322
Google needs to replace everyone's NP that got bricked due to their faulty
update.
On Fri, Nov 6, 2020, 12:40 PM <buganizer-system@google.com> wrote:
update.
On Fri, Nov 6, 2020, 12:40 PM <buganizer-system@google.com> wrote:
ud...@gmail.com <ud...@gmail.com> #323
Word on the street is the NP got updated to the new Google TV interface.
de...@gmail.com <de...@gmail.com> #324
Com'on now. Wouldn't it be easy enough for them to give us an apology and a
store credit?
On Sat, Feb 13, 2021, 5:58 PM <buganizer-system@google.com> wrote:
store credit?
On Sat, Feb 13, 2021, 5:58 PM <buganizer-system@google.com> wrote:
ks...@gmail.com <ks...@gmail.com> #325
Thats great...But my two are bricked....
he...@gmail.com <he...@gmail.com> #326
Still have my three bricked NPs in their boxes. I'd take a Play Store
credit being that I have absolutely no interest in Google hardware anymore.
On Sat, Feb 13, 2021, 5:03 PM <buganizer-system@google.com> wrote:
credit being that I have absolutely no interest in Google hardware anymore.
On Sat, Feb 13, 2021, 5:03 PM <buganizer-system@google.com> wrote:
ke...@gmail.com <ke...@gmail.com> #327
As I sit here with 2 pucks that are bricked... No update will help of I can't even get to bootloader/recovery.. laughing but not laughing..
st...@gmail.com <st...@gmail.com> #328
Going on three years with no updates or progress.. since I've been happy to give business to Roku and others who support their products. This is shameful Google.
te...@gmail.com <te...@gmail.com> #329
Any update Google? I want a working replacement for my Nexus Player.
It appears to be a trend now that Google ignores hardware problems when they break a device. Unfortunately, my Pixel 3 was bricked by Google recently. First my Nexus Player and now my Pixel 3. I'm done with Google hardware and I recommend all my friends to avoid Google products due to their lack of customer support when they kill devices.
The Pixel 3 bricking issue.
https://issuetracker.google.com/issues/192008282
It appears to be a trend now that Google ignores hardware problems when they break a device. Unfortunately, my Pixel 3 was bricked by Google recently. First my Nexus Player and now my Pixel 3. I'm done with Google hardware and I recommend all my friends to avoid Google products due to their lack of customer support when they kill devices.
The Pixel 3 bricking issue.
st...@gmail.com <st...@gmail.com> #330
Comment has been deleted.
st...@gmail.com <st...@gmail.com> #331
Found this item up on a shelf and was suprised to see this still sitting here with no updates (I wasn't really surprised)
So any movement on this at all?
So any movement on this at all?
an...@gmail.com <an...@gmail.com> #332
Wow I forgot about this thread.
Due to Google's inaction, I'm on new hardware...
--
Andrew Kahn
On Tue, Feb 21, 2023, 1:44 PM <buganizer-system@google.com> wrote:
Due to Google's inaction, I'm on new hardware...
--
Andrew Kahn
On Tue, Feb 21, 2023, 1:44 PM <buganizer-system@google.com> wrote:
he...@gmail.com <he...@gmail.com> #333
I use my three bricked NPs as coasters.
On Tue, Feb 21, 2023, 11:45 AM <buganizer-system+917997+114276277@google.com>
wrote:
On Tue, Feb 21, 2023, 11:45 AM <buganizer-system+917997+114276277@google.com>
wrote:
tc...@gmail.com <tc...@gmail.com> #334
No one currently working at Google would even know what this device is at this point.
ko...@gmail.com <ko...@gmail.com> #335
Bye, google! I changed my NP brick to amazon stick 4k MAX
wi...@gmail.com <wi...@gmail.com> #336
2 NP deads here too ... 6 years and counting -
Will spam this tracker for life.
do a blog about it share it on FB and maybe a movie script.-
Will spam this tracker for life.
do a blog about it share it on FB and maybe a movie script.-
ks...@gmail.com <ks...@gmail.com> #337
pa...@gmail.com <pa...@gmail.com> #338
I've only got one dead NP but I think a voucher for a new streamer might
ease my emotional distress about it.
On Thu, Nov 7, 2024, 9:32 PM <buganizer-system@google.com> wrote:
ease my emotional distress about it.
On Thu, Nov 7, 2024, 9:32 PM <buganizer-system@google.com> wrote:
om...@gmail.com <om...@gmail.com> #339
Yep, one dead one here with the Nexus gamepad. Used to play NBA Jam on it
on a daily basis. Sucks Google killed them and didn't offer anything as a
result.
On Thu, Nov 7, 2024, 8:33 PM <buganizer-system@google.com> wrote:
on a daily basis. Sucks Google killed them and didn't offer anything as a
result.
On Thu, Nov 7, 2024, 8:33 PM <buganizer-system@google.com> wrote:
st...@gmail.com <st...@gmail.com> #340
Six years later I still have two of these things laying in my closet from the great brickage.
Google killed my Nexus Players, but also my recommending and purchasing anything in their ecosystem.. win win?
Google killed my Nexus Players, but also my recommending and purchasing anything in their ecosystem.. win win?
ra...@gmail.com <ra...@gmail.com> #341
Wow, y'all, it's been 6 years... They're not gonna send you free stuff or
fix the thing that's been EOL for all this time. Just give it up.
On Thu, Nov 7, 2024, 9:47 PM <buganizer-system@google.com> wrote:
fix the thing that's been EOL for all this time. Just give it up.
On Thu, Nov 7, 2024, 9:47 PM <buganizer-system@google.com> wrote:
ba...@gmail.com <ba...@gmail.com> #342
Still like the occasional reminder that Google produces a lot of buggy flawed products that they don't like to take responsibility for within the warranty period.
ra...@gmail.com <ra...@gmail.com> #343
When this bug was reported, the nexus player had been discontinued for 2 years, and was 4 years old. Well outside of any warranty period, so I don't know wtf you're talking about. If you don't like their products, don't buy them.
ba...@gmail.com <ba...@gmail.com> #344
Sorry I don't conform to your low expectations for the lifespan of a
mainstream consumer electronics product. I have electronic products I
bought in the 80s that still work like the day they were bought and those
that don't are reasonably easy to repair with a little soldering, plastic
grease, or gear bands. A product that dies in 6 years of purchase is a
product made by a company that doesn't care about quality or quality
control.
Everytime someone wakes up this thread I come back here to say, Google
makes crap products. It isn't a great burden on my time.
On Fri, Nov 8, 2024, 5:38 PM <buganizer-system@google.com> wrote:
mainstream consumer electronics product. I have electronic products I
bought in the 80s that still work like the day they were bought and those
that don't are reasonably easy to repair with a little soldering, plastic
grease, or gear bands. A product that dies in 6 years of purchase is a
product made by a company that doesn't care about quality or quality
control.
Everytime someone wakes up this thread I come back here to say, Google
makes crap products. It isn't a great burden on my time.
On Fri, Nov 8, 2024, 5:38 PM <buganizer-system@google.com> wrote:
ga...@gmail.com <ga...@gmail.com> #345
Guessing no class action every materialized?
Outside of that, this issue is dead. Google f*d us with a bad software update.
Outside of that, this issue is dead. Google f*d us with a bad software update.
an...@gmail.com <an...@gmail.com> #346
My Nvidia shield still goes hard in the paint.
I'm hesitant to upgrade to the new streaming device. It looks nice but I'm
still peppery for Google's poor handling of the Nexus Player.
If they sent me a free google streaming device, I'd feel better about
things but so much time has passed. #teampixel if that helps...
--
Andrew Kahn
On Fri, Nov 8, 2024, 8:59 AM <buganizer-system@google.com> wrote:
I'm hesitant to upgrade to the new streaming device. It looks nice but I'm
still peppery for Google's poor handling of the Nexus Player.
If they sent me a free google streaming device, I'd feel better about
things but so much time has passed. #teampixel if that helps...
--
Andrew Kahn
On Fri, Nov 8, 2024, 8:59 AM <buganizer-system@google.com> wrote:
de...@gmail.com <de...@gmail.com> #347
Comment has been deleted.
an...@gmail.com <an...@gmail.com> #348
Absolutely, there is a critical defect and they all kinda died around the
same time.
I can't even flash a third party rom onto the hardware... I paid for it, I
should *still be able to use it*.
--
Andrew Kahn
On Fri, Nov 8, 2024, 9:58 AM <buganizer-system@google.com> wrote:
same time.
I can't even flash a third party rom onto the hardware... I paid for it, I
should *still be able to use it*.
--
Andrew Kahn
On Fri, Nov 8, 2024, 9:58 AM <buganizer-system@google.com> wrote:
mg...@gmail.com <mg...@gmail.com> #349
They remotely bricked them and they don't want to answer to it.
I want to speak to the manager!
I want to speak to the manager!
ba...@gmail.com <ba...@gmail.com> #350
I moved on from the Nexus Player a long time ago. You should be more
bothered that you are expending energy telling us to move on. What is in it
for you? Pride in helping a billion dollar company stiff customers out of
their hard-earned money?
I expect products not to brick after product updates. I don't care if the
product is five minutes old or five years old. There is too much plastic
and electronic waste in the world.
Do I expect them to reply? No. Do I expect my money back? No. Did I expect
them to reply when the initial problems began rather than having Asus and
Google pass the buck on each other? Yeah. Will I reply every once in a
while when this opens again? Sure, why not.
Google stinks.
On Fri, Nov 8, 2024, 11:58 PM <buganizer-system@google.com> wrote:
bothered that you are expending energy telling us to move on. What is in it
for you? Pride in helping a billion dollar company stiff customers out of
their hard-earned money?
I expect products not to brick after product updates. I don't care if the
product is five minutes old or five years old. There is too much plastic
and electronic waste in the world.
Do I expect them to reply? No. Do I expect my money back? No. Did I expect
them to reply when the initial problems began rather than having Asus and
Google pass the buck on each other? Yeah. Will I reply every once in a
while when this opens again? Sure, why not.
Google stinks.
On Fri, Nov 8, 2024, 11:58 PM <buganizer-system@google.com> wrote:
Description
- Reboots are not possible
- Users report attempts to downgrade to Nougat are eventually overtaken with a subsequent update and bootlooped.
These systems have been going offline since early August. User forum here: