Microsoft Approves Fix for "Walshed" Windows Phones (Update)

Official word coming from the ChevronWP7 Twitter page confirms that Microsoft has just approved a possible solution to phones that used the team's Updater to force the NoDo update. No details yet, but they are forthcoming and we officially have a confirmation.

Update: Brandon Watson just took to the Windows Phone Developer Blog to divulge the details of the supposed fix. Watson confirms that the Updater tool has prevented phones from receiving future updates, specifically yesterday's 7392 update, saying the tool "performed an incomplete update" when forcing NoDo:

With Windows Phone update build 7392 going out to phones via the official update mechanism, those people who have used the unsupported method of forcing 7390 onto their phones will find that their phones will not update to 7392. With the official update process there is a requirement that the package on the phone also be official in order to update itself. 

Phones updated via the unsupported method do not contain an official image and cannot be updated further at this time. Due to scheduling of engineering resources, we did not anticipate having to undue the changes made to phones by these unsupported methods. While we are not ruling out having a fix in the future, for now there is no fix. 

However, Watson goes on to say that the ChevronWP7 team has taken up the responsibility in order to provide a fix:

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 have created a way to get these phones back on the officially supported path. We will work with them to validate their solution and applaud the team for taking responsibility to do this.

So as of today, any "Walshed" phones will not be receiving the 7392 or any future Windows Phone updates. Fortunately for those who did use the tool, it's clear ChevronWP7 is admitting their mistake and will be providing a fix sometime soon. In the meantime, just be extra careful while browsing suspicious websites or opening unknown emails on your Windows Phone in order to avoid that security hole yesterday's update patched.

Source: Twitter, Windows Phone Developer Blog