Over the weekend, Microsoft released its Windows Phone Support Tool and it seems the support tool was good for more than just getting a failed Windows Phone 7 update working again. Chris Walsh, one of the developers of the later removed ChevronWP7 tool, has just released a project called "ChevronWP7.Updater". According to Walsh, inside the Windows Phone Support Tool, Microsoft created a managed wrapper which takes care about the whole update process. ChevronWP.Updater takes benefit of this wrapper and now allows to flash every Windows Phone 7 to pre-NoDo (7008), NoDo (7355), NoDo update 1 (7389) and NoDo update 2 (7390) - all in a single process and with the proper firmware - accordingly to the phone!
Chris Walsh's ChevronWP7.Updater is a command line console app which prompts the user to follow the steps but it requires that the device language is supported by ChevronWP7.Update (at the moment the tool supports English US, English UK, French, Italian, Spanish and German) and it's strongly recommended not trying out any other language combinations!
Anyway, while this seems to be an interesting option to shorten the time for getting the Windows Phone 7 NoDo update, you better know what you are doing since such a workaround can seriously damage your Windows Phone 7! I would suggest to better wait until your carrier releases its Windows Phone 7 NoDo update but just in case you want it now, I've told you that there's a workaround.
UPDATE: Looks like Chris Walsh has taken down ChevronWP7.Updater, the download isn't available anymore. He has not yet given the reason for the take-down and therefore it's unclear if he has taken it down on Microsoft's request or because it caused more problems than it helped! Again, use it on your own risk and better know what you are doing if you plan to use it!
UPDATE 2: In an info, Microsoft seriously warns to use ChevronWP7.Updater. According to Microsoft, "the use of ChevronWP7.Updater could possibly put the updated Windows Phone 7 device into a state where it cannot receive future regular updates to the OS anymore", which means the only fix will be re-flashing the device with an original stock ROM. At the end of the day if could mean that such Windows Phone 7 devices have to be send to the manufacturers or carriers service centers because unlike for Windows Mobile, stock ROMs are officially not available as a public download for end-users.
UPDATE 3: As mentioned in Update 2, Microsoft's Eric Hautala has published a blog posting on the Windows Phone Blog where Hautala explains the situation: "We're working hard to get this job done as quickly as possible. But I've noticed that some of you are turning to homebrew solutions to update your phone immediately. As an engineer and a gadget lover, I totally understand the impulse to tinker. You want the latest technology and you're tired of waiting. [...] But 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. It's even possible your phone might stop working properly."
UPDATE 4: Chris Walsh has written a new blog post where he confirms that ChevronWP7.Updater can indeed break updated Windows Phones: "I was later informed by Microsoft that there were several problems with my tool and the manner in which it changes phones. [...] 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. Because the tool is, in Microsoft's words, "breaking phones", I have taken it offline at their request.
While the number of users impacted by this utility is small, 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."
Cheers ~ Arne