Why the Chevron.Updater was withdrawn
When I posted about the Chevron.Updater application, that developer Chris Walsh launched earlier in the week, I was surprised to see the updater there in the early morning, Monday, and then the download link was dead in the afternoon. The Windows team blog, later posted an update about it’s state of affairs concerning the update rolling out conventionally, and made mention of Chris’s utility.
my strong advice is: wait. If you attempt one of these workarounds, we can’t say for sure what might happen to your phone because we haven’t fully tested these homebrew techniques. You might not be getting the important device-specific software we would typically deliver in the official update. Or your phone might get misconfigured and not receive future updates
Chris Walsh, the developer has posted on his blog why the Updater was withdrawn from the public domain, for the moment.
Despite the fact that all outward signs indicate the phone has been updated to build 7390, Microsoft tells me otherwise. Part of the problem, the company says, is that I incorrectly used an undocumented API to deliver updates.
Most problematic, Microsoft tells me that updating in this manner will place devices in a “non-serviceable state”. In its blog post describing the situation, Microsoft instead says devices updated in this manner “may” no longer receive updates
Chris also apologises profusely, and promises to let us know how to rectify the problem [if any] in time.
I would at least like to communicate that I”m sorry if this tool causes any issues down the road. In a follow-up post, I’ll detail what your next steps should be as official support isn’t an option at this time
Also reading the comments on the blog, there is no animosity towards Chris in any way. and a couple of mentions of waiting for a fix. I think though, the apostrophised “MAY” shows their lack of knowledge, and an attempt to create fear from Microsoft. I have not had any ill affects from using the updater, and in fact, running NoDo on my Mozart has enhanced what I already thought was a brilliant user experience. The updater may break the updating process?, but no conclusive proof has been offered at this point.
The thing now is everyone is looking for a fix. even though that may be premature at this point, downgrade your rom. You can downgrade and install any rom compatible with your phone, developer unbranded, carrier branded, unbranded using the boot loader flash method. The post from XDA has download links for all of the major carriers, for the HTC Mozart, but you will find similar posts in your specific device category. Downgrade your ROM to flash back to, what would be perceived as normal by Microsoft, if they can even tell at this point. One point, this involves a hard reset, factory restore of your phone, so you will have to set up, and download your apps again. Of course you also go back to pre NoDo depending where your carrier is at.
This will probably be the simplest solution you can apply if you are worried about your phone being in an unserviceable state.If you have a developer unlocked phone, there may be a better way to fix this via the registry, if in fact it is a problem at all.
The real downside to using the Chevron Updater, is that it bypasses the Zune backup, giving you no default previous state to revert to, but as many users are reporting, after using the utility, they are receiving further OEM updates. For now, it remains a very complicated story, with the major factor presented, that it breaks the phone for further updates. If it does, I’m sure Microsoft will use it for leverage to promote their platform approach, if it doesn’t, will Microsoft embrace the homebrew community a little less cautiously?
However it goes, Microsoft have not been able to provide a flawless updating solution for their new OS, and it’s been well noted, even if it is just in the enthusiast community.