Last night, I began the upgrade from 188.8.131.52 to 5.0.1. The device was near 100% charged, plugged into my Win10 desktop. The update downloaded, I clicked to restart and update. It began the update as normal, I looked after a few minutes and it was half way through the update. I look again a few minutes later and the screen is black. I tap the power button, nothing. I disconnect it from my computer, no beep / chime or anything. I push the power button again, holding it for a second or two thinking that it just shutdown, nothing. I push and hold the power button for about 20+ seconds, nothing. I push and hold volume up + power for about 20 seconds, nothing. Plug it into wall, no indicators or anything on the screen. I plug it into my computer and I get a chime that windows recognizes the device, then a few moments later the device disconnect chime, nothing on the tablet. Left it plugged in to an amazon power adapter all night, this morning, nothing. Its bricked. Amazon support won't help me, its out of warranty despite their software update likely corrupting the bootloader or partition.
You describe exactly what happened to me and two friends. We were OTA updated to OS 184.108.40.206, requested the developer preview and our Fire HDs were destroyed as soon as Amazon installed the developer preview. I hope someone here can offer some guidance because Amazon CS is not acknowledging that it has released an update that is incompatible with the developers preview.
There a whole bunch of people (including me) in a
slickdeals.net forum thread (people who purchased these recently cheaply through Amazon warehouse) who have had bricked devices when updating from 220.127.116.11 to 5.0.1 developer preview. Seems like people are having no problem updating from 4.5.5, but devices coming from 18.104.22.168 all get bricked. Hopefully, Amazon can pull 5.0.1 for anyone on 22.214.171.124 until they fix this.
Hi C.Mancini, Thanks for posting this, and we're extremely sorry to hear this has happened! If you could, please open a contact us case and call out what type of device you have that is not functioning after signing up for the Developer Preview. Additionally, please provide your preferred mailing address in the event that we are required to replace your defective device. We are investigating a root cause at this time, and will reply if a solution is determined. Thanks again for reaching out, and we appreciate everyone sharing these details for our investigation.
I just submitted a report through that some contact us link. Justin, C. Mancini obviously has an issue with getting his device replaced, but you need to get this reported to the development team as many people are winding up with bricked devices when updated from 126.96.36.199 to 5.0.1 developer preview. If you don't fix the core issue, you are going to get lets more complaints and more bricked devices. Is someone looking into this?
Thanks LexLuthor, This is absolutely a priority for investigation. We are investigating workarounds and having necessary discussions on outcomes. We have a backlog of potential devices affected and will use this information accordingly. Justin