May 5, 2011 12:34 GMT  ·  By

Redmond-based software giant Microsoft has just confirmed that Windows Phone 7 device owners who forced the NoDo update on their devices won't be able to enjoy a new update past it, at least not for the time being. The company says that those people who used the unofficial update mechanism to bring their devices up to the March update, aka NoDo, aka build 7390 would have their devices stuck to this software version, and that the latest software for their devices, 7392, won't arrive.

In a recent post on the company's blog, Microsoft's Brandon Watson sheds some light on the matter, explaining why users won't be able to update to newer software and how they brought this upon themselves.

“Despite the fact that many people have claimed that an unofficial update mechanism worked fine for them, we cautioned that phones which were updated via this method were not going to be able to update past build 7390,” he notes.

Long story short, the unofficial process performed an incomplete update of the phones, which resulted in an altered state machine, not an updated one, with the handset being considered at state machine here.

The official update mechanism won't be able to bring the machine up from this unknown state, especially with the device looking like running under pre-7390 software rather than a proper 7390 release.

“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,” the blog post continues.

“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,” Watson explains.

However, there's still hope. Users forced the update on their devices via an unofficial tool, and those behind this tool are currently working on finding a solution for the issue, they believe that a fix is near, and Microsoft says they would provide the necessary help in this direction.

“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,” Brandon Watson continues.

According to Microsoft, chances are that future updates would modify the aforementioned mechanism, so that users who perform unofficial updates of their devices won't face similar problems, but nothing is available from the company at the moment.