Yesterday we heard that using the ChevronWP7.updater tool might cause some issues with future Windows Phone updates and was pulled from Walsh’s blog shortly after.
Well, Eric Hautala has updated the Windows Phone Blog again today with a warning about using these workarounds:
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. Believe me, I get it.
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. Bottom line: unsupported workarounds put you in uncharted territory that may void your phone warranty. We’ve made a lot of progress in recent weeks, so I urge you to please be patient for just a bit longer and wait for your official update notification to arrive.
I definitely see where Microsoft is coming from. After all, I held off as long as I could before turning to use the updater. The problem is, and its even clearer, that At&t is happy playing games with their Windows Phone updates and while Eric and those at Microsoft “Get it”, they clearly don’t really “Get It” or they would do something to get these customers their official update in a timely fashion.
Overall, it sounds like Microsoft was simply “playing it safe” by claiming it might effect future Windows Phone updates, when they really just want to test homebrew methods before officially stating them OK to use. Either way, you are updating at your own risk if you use any methods other than the official Zune software update, but trust me, I “Get It” if you do.
Read the entire Windows Phone Blog post here.