Did you use a homebrew solution to force the Windows Phone 7 "NoDo" cut and paste update? You might be out of luck when it comes to security upgrades.
Microsoft announced Wednesday that people who used an "unofficial update mechanism" to upgrade to "NoDo" will not get a security upgrade that started rolling out yesterday. In a blog post explaining the situation, Microsoft basically said we told you so.
"We cautioned that phones which were updated via this method were not going to be able to update past build 7390," Microsoft's Brandon Watson wrote. "Unfortunately for those customers out there who acted on information from sources outside of Microsoft, the rubber meets the road today."
Updates for the Windows Phone 7 platform have had a bit of a rough road, prompting delays. For those who didn't want to wait, the developer behind the short-lived ChevronWP7 jailbreak for Windows Phone 7 posted a new hack that let users bypass Microsoft and carriers to update their mobile operating system.
In early April, Microsoft cautioned against using this method. "Bottom line: unsupported workarounds put you in uncharted territory that may void your phone warranty," Microsoft said at the time.
As a result, the recent "7392" security update, which fixes nine fradulent third-party digital certificates, will not be available for phones that used the Chevron workaround.
"With the official update process there is a requirement that the package on the phone also be official in order to update itself," Watson wrote. "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."
Microsoft is not completely ruling out a future update, but "for now there is no fix." The Windows Phone 7 team is now focused on the current security update and the next major platform update, codenamed Mango. "Undoing this specific problem was not in our schedule," Watson said.
That being said, the team that developed the workaround might have a solution.
They "wanted to get a timely fix created for customers who have put their phones into this state," Watson continued. "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."