Brandon Watson today posted about a specific issue: Windows phones “updated” using any unofficial mechanisms.
Watson noted that “with Windows Phone update build 7392 going out to phones via the official update mechanism, those people who’ve used the unsupported method of forcing 7390 onto their phones will find that their phones willn’t update to 7392. With the official update process there’s a requirement that the package on the phone also be official in order to update itself.”
“When we test our update process, we test against a known state machine. Further, as a health protection mechanism, the phone will always try to recover from an error state (as in an incomplete update), and will begin doing things to solve for the fact that it’s in an unknown state. This’s the reason why phones started downloading OEM updates after forcing the update via this unofficial tool. It’s also the reason why people who used the unofficial tool to get to 7390 reported that their phones later updated to 7390 via the Zune PC software. The state machine looked more like pre-7390 than it did 7390. However, because of the existence of some of the 7390 bits on the phone, and the fact that the 7390 update process was not intended to run against this a priori unknown state machine, the result was an incomplete 7390 update,” Watson explained.
“If you’ve a phone that was updated using this unofficial tool, and you attempt to update to 7392 from the Zune software, you’ll get the error code 80180048. Zune is the only official way to update the operating system on the phones. The mobile operators purchase Windows Phones from the manufacturers, and they’re the ones who’re authorized to flash phones for the mobile operator. The mobile operator store locations aren’t capable of flashing phones on-site with an original OS image, which means that you’ll most likely have to return to a store and submit your phone for a manufacturing return. However, because of this known error code, it’s up to the mobile operators as to what they want to do with your phone,” Watson added.
“However, the creators of the unsupported tool are a clever bunch, and wanted to get a timely fix created for customers who have put their phones into this state. They believe they’ve created a way to get these phones back on the officially supported path. We’ll work with them to validate their solution and applaud the team for taking responsibility to do this.”
[Source: Windows team blog]