Linked by Thom Holwerda on Wed 23rd Feb 2011 23:56 UTC, submitted by gogothebee
Windows Ah, something Microsoft really couldn't use right now: problems with the very first update to its Windows Phone 7 operating system. In this very competitive marketplace, in which WP7 is a late newcomer, it can't use major problems like this. The thing is though - how big of a problem is this, really? And, is it even Microsoft's fault at all?
Permalink for comment 463796
To read all comments associated with this story, please click here.
RE: The phones
by atsureki on Thu 24th Feb 2011 04:40 UTC in reply to "The phones"
atsureki
Member since:
2006-03-12

were not hardware bricked. They had a soft brick, which only requires you to hit the button combination which reflashes the firmware onto the device.


No.

http://arstechnica.com/microsoft/news/2011/02/everything-that-can-g...

"For lucky individuals, the process merely hangs on step seven (out of ten); rebooting the phone resurrects it, albeit without the upgrade. For a minority of unlucky users, the process fails at step six, and corrupts the phone's firmware. What's worse is that for some of them it appears to be bricking the phone completely, rendering it useless."

Next paragraph goes into detail about the button combination, and how it sometimes doesn't work.

I remember Eugenia's recent article about older iOS products being "bricks" because two features have ceased to work after an update. Meanwhile the first WP7 update has made actual, real, for serious bricks, and that word is conspicuously absent. To be fair, the iOS issue is systemic, and this is relatively isolated. But to be actually really fair, these are actually really bricks, and the iOS devices actually really aren't. Just sayin'.

Reply Parent Score: 3