Windows Phone 7 ChevronUpdater issue being fixed. Microsoft explains the situation

If you have previously used the ChevronUpdater to update you Windows Phone 7 handset to NoDo then there’s a chance that you won’t be able to update your handset anymore. This was previously announced by Microsoft and was the reason why the hack was taken down a few hours after it went public. Now that the 7392 update is being rolled out some of the users who previously used the hack are unable to successfully in tall the update on their handsets. Fortunately a fix is being worked on by the man behind the original hack, and Microsoft is in the process of validating it.


Microsoft’s Brandon Watson posted a lengthy explanation of the issue and why it’s not Microsoft’s business to fix this:

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. Unfortunately for those customers out there who acted on information from sources outside of Microsoft, the rubber meets the road today.
[...]
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. The mobile operators purchase Windows Phones from the manufacturers, and they are the ones who are authorized to flash phones for the mobile operator. The mobile operator store locations are not capable of flashing phones on-site with an original OS image, which means that you will most likely have to return to a store and submit your phone for a manufacturing return. However, because of this known error code, it is up to the mobile operators as to what they want to do with your phone.

We understand that this isn’t ideal. Unfortunately, our engineering priorities are focused on improving the process by which updates get to Windows Phone, issuing the security update you just got and working to getting Mango to market. Undoing this specific problem was not in our schedule.

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.

Just to be clear here; devices updated via the VPN method are not affected by this issue. Only some devices updated using the ChevronUpdater are affected.

source: Microsoft

  • Pete

    Is there a way you can tell if your phone was updated to 7390 via the unofficial tool?

  • http://www.mobiletechworld.com MobileTechWorld

    Not that I’m aware of. But if someone did update his phone using this tool then I sure hope that he remembers doing it :-s

  • Pete

    Bought the phone 2nd hand (only a month old and in pristine condition). An Omnia 7. Very pleased with it. But just not sure as to how it got 7390 especially since its not an ‘offical’ phone. It running on network that currently does not offer any WP7 phones.

  • http://www.mobiletechworld.com MobileTechWorld

    The original owner may have used the VPN trick to get NoDo so there’s noway to really know unless you ask him. In either cases there’s isn’t much you can do right now given that all Omnia 7 updates have been halted. Microsoft is working on fixing some issues related to this model before resuming the roll out.