Microsoft Yanks Windows Phone 7 Patch

HardOCP News

[H] News
Joined
Dec 31, 1969
Messages
0
You gotta love a "patch" that bricks your new phone. I'm not sure what is being done about the bricked phones but Microsoft says they will re-release the patch once it has been patched...with a patch.

An initial patch intended to pave the groundwork for a pair of forthcoming Windows Phone 7 updates ended up "bricking" a number of Samsung smartphones this week, forcing Microsoft to pull the update and giving Redmond a black eye in the process. Microsoft has "temporarily" pulled the patch.
 
Ouch, that's gotta suck. At least they're big enough to take care of any potential problems that may come up as a result.
 
Personally, I think this is why they rolled out this "update for the update". When they released the update, they did it very slowly, only releasing it to select phones at a time. I believe this was their test of the upcoming update. Definitely a Samsung issue, not Microsoft. Me and my wife still haven't gotten a notification on our phones for the update.
 
Personally, I think this is why they rolled out this "update for the update". When they released the update, they did it very slowly, only releasing it to select phones at a time. I believe this was their test of the upcoming update. Definitely a Samsung issue, not Microsoft. Me and my wife still haven't gotten a notification on our phones for the update.

Same here, no update yet for my Focus. Thankfully, in this case :)
Posted via Mobile Device
 
Edit: looks like just the Samsung Omnia 7s were affected.
Posted via Mobile Device
 
Yep, I'm on AT&T with the Focus and nothing. My wife has the LG Quantum.
Posted via Windows Phone
 
Personally, I think this is why they rolled out this "update for the update". When they released the update, they did it very slowly, only releasing it to select phones at a time. I believe this was their test of the upcoming update. Definitely a Samsung issue, not Microsoft. Me and my wife still haven't gotten a notification on our phones for the update.

SparkedFire from the old CPU forums?! Small e-world :).

Ars has a much better article about it, and this was their take on the blame which I generally agree with:
Testing all the different variants was certainly something Microsoft could have done, but apparently has not. I'm sure that Samsung has some blame here too—the problems thus far appear to be limited to its handsets—but if Samsung has screwed something up, Microsoft should have noticed this and forced them to fix it before shipping the phones to end users.
 
SparkedFire from the old CPU forums?! Small e-world :).

Yep it's me. I wonder if Samsung was shipping multiple firmwares which caused the problem. Maybe Microsoft was only aware of one firmware, which is the one they tested on.
 
I gotta feel sorry for samsung, in december they went through the same thing with the Galaxy S in Canada and the droid 2.2 update cooking phones.
 
Back
Top