'Walsh Fix' Being Approved by Microsoft, Brandon Explains the Problem
Chevron have posted on their Twitter account that a fix from Chris Walsh is being validated by Microsoft to see to the problems that have arisen from unofficially updating handsets to NoDo.
We recently looked at how the Chevronwp7.updater has caused issues for many users attempting to receive the May security update, hopefully once this fix is approved by the Windows Phone team, we should see some positive results without having to re-flash devices.
In addition, there has been a new article posted on the Windows Phone developer blog. Brandon Watson explains why the unofficial tool may have a negative impact on Windows Phones by putting them in a changed state, as opposed to an updated state (if looking at the devices as state machines).
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 is in an unknown state. This is 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.
If you have a phone that was updated using this unofficial tool, and you attempt to update to 7392 from the Zune software, you will get the error code 80180048. Zune is the only official way to update the operating system on the phones.
So, good news for you guys who are experiencing the 80180048 error when attempting to receive the May security update. It should be noted that the Chevron team are working on this fix and are taking responsibility off their own backs, which deserves much appraisal. The Windows Phone team are busy working on Mango among other workings which the unsupported tool is not apart of.