HTC 8x Bricked after Win10 Preview install, how can I fix this?

  • Thread starter Windows Central Question
  • Start date
W

Windows Central Question

HTC 8x Bricked after Win10 Preview install

Received a notification yesterday that a "critical update" was ready. Upon checking it was the long awaited Windows 10 Technical Preview, which I proceeded to install. The update went in into a reboot cycle -- Power On -> HTC Logo -> T Mobile Logo -> Spinning Gears for 20 sec -> black screen for ~3 sec -> reboot.
The Windows Phone Recovery Tool shows Firmware Version as Unknown and does not find any recovery packages on the server.

First reaction - not polite to put on the interwebs
Second reaction - why release an update for which there is no tested recovery method? Another fine example of Microsoft ineptitude in the mobile space.

Now a perfectly functioning hardware phone is effectively bricked, and thanks to the UEFI secure boot won't even be able to install an alternate OS.
Received a notification yesterday that a "critical update" was ready. Upon checking it was the long awaited Windows 10 Technical Preview, which I proceeded to install. The update went in into a reboot cycle -- Power On -> HTC Logo -> T Mobile Logo -> Spinning Gears for 20 sec -> black screen for ~3 sec -> reboot.
The Windows Phone Recovery Tool shows Firmware Version as Unknown and does not find any recovery packages on the server.

First reaction - not polite to put on the interwebs
Second reaction - why release an update for which there is no tested recovery method? Another fine example of Microsoft ineptitude in the mobile space.

Now a perfectly functioning hardware phone is effectively bricked, and thanks to the UEFI secure boot won't even be able to install an alternate OS.

Val
 

realwarder

New member
Dec 31, 2012
3,689
0
0
Visit site
Re: HTC 8x Bricked after Win10 Preview install

Suggest you ask for help from Microsoft. Windows Phone twitter page is one path. Community forums on Microsoft site another. You'll just need the right tool to update back to default firmware. Sending a tweet to @GabeAul may also help, although they are aware users have experienced this. But ask for help anyway.

Last time this happened it took Microsoft about 2-3 days to fix the issue and release an update to the recovery tool.
 

Members online

Forum statistics

Threads
323,160
Messages
2,243,365
Members
428,034
Latest member
shelton786