For some haters, this might be the usual case. “What do you expect from Microsoft?” Well, making a mobile OS is not something very new to Microsoft. Their Windows Mobile actually has been around for quite some time, earlier than iOS and Android. However, simple things such as updating the phone OS still causes problems for their Windows Phone 7 handsets, and the latest is as serious as bricking the phone.

Monday, Microsoft started rolling out the first update to Windows Phone 7. The company was non-specific about the purpose of the update; it’s not the copy-and-paste update that will be shipped next month, but rather an update to somehow improve the update process. Presumably to ensure that the company can keep on top of any issues that may arise. But somehow, there’s already issue on the first update to Windows Phone 7.

Most Windows Phone 7 devices update with no problem, but a few particular Samsung handsets get troubles. The two Samsung handsets on the market, the Omnia 7 and the Focus, are both having troubles installing the update. The updates fail to install in two ways: 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.

Those unfortunates with apparent firmware corruption can try forcing the phone into download mode (turn off the handset, then turn it on while holding the camera button and the volume down button, and keep all three buttons pressed for 10-15 seconds; then choose the “format” option). If this is successful, it should allow the handset to recover its original firmware and resume operation. But not everyone can get this to work, indicating that the devices are truly bricked, with the only option being to return them to the network operator and have them replaced under warranty.

Investigation of the issue shows that Samsung has a range of different firmware versions in-use. Devices with older firmwares—JI9, JID (which my Omnia 7 is using) and JJ4—are failing to update. The newer JK1 firmware updates properly (at least most of the time). Figuring out which firmware version you have is a somewhat awkward procedure. From the phone’s dialer, type ##634#, then press the call button. This will start up Samsung’s Diagnosis application (it will also create an icon for it in the phone’s programs list, so that you can go back to it in future without using the dialer).

In the ‘Diagnosis application’, type in *#1234#. This will show a screen of detailed version information. It’s the first three version numbers (for “PDA”, “Phone”, and “CSC”) that are relevant here. If the firmware versions are older (JIx, JJx) then the update probably won’t work; if they’re newer (JKx) it probably will. But there are no guarantees.

Thus far, Microsoft has already provided an official statement regarding this issue: “We are investigating reports related to the Windows Phone update process and will provide additional information and guidance as it becomes available.”

Microsoft says that it hopes to produce an update that resolves the Samsung incompatibility within three days or so. In the meantime, owners of Samsung handsets are advised not to install the update. You won’t want your phone to be bricked by Microsoft right?

SOURCE via Ars Technica