Listening to the latest WP Radio Podcast (episode 22 HERE ), Brandon Watson from MS reports ~12:00 minutes into the podcast;

The Chris Walsh Chevron.Updater tool definately does not update your handset to 7390 Nodo properly.  He states “It didn’t quite work as they thought it did……and they didn’t have the ability to test it completely“  His analogy was “It’s got tyres, it’s got doors, it’s got an engine – it looks like a car, BUT it’s not a car!“.

It sounds like with over 25K downloads of the tool as reported by Chris before he took the file down at MS’s requests – MS are said by Brandon to be working on how phones that have been forced may be fixed or have the change reversed (ROM flashing as the last resort).

Every Wednesday we can expect Eric Hautala (MS General Manager, Customer Experience Engineering) will be updating his Windows Blog post here: http://windowsteamblog.com/windows_phone/b/windowsphone/

Let’s hope (as myself one that has used this tool) that MS and Chris together come up with a solution to help what must be at least 10,000 (thats less than 1 in 2 downloaders) forced updates in the wild get their fixes prior to Mango – or interim MS WP7 updates post NoDo.