WARNING ChevronWP7 May Have Consequences
After Microsoft warned against using ChevronWP7 Updater earlier this week, then begged for patience until you receive an official update, Chris Walsh, creator of ChevronWP7 Update, has now warned everyone not to use his application. Chris has posted over on his blog that Microsoft communicated with him directly that the method in which his program unlocks the phones is not safe, and will place devices in a “non-serviceable state.” All that means is you lose your warranty, everyone should’ve known that before even using the program, we get that. Following that Chris explains he was also told by Microsoft that those using the ChevronWP7 Updater method “‘may’ no longer receive updates.” Of course, your immediate reaction might be ‘big deal they are just trying to scare us out of not hacking our phones’, but you never really know that for a fact.
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.
Chris continues his blog post by apologizing to the over 25,000 Windows Phone 7 users that have used his application to receive the NoDo update earlier. He hopes (along with all the users) that the update method doesn’t have any real consequences to those who used it. You can read the full blog post at the source link.
Have you noticed any problems with your “early update” NoDo? Will you be restoring your phone or keeping your early update NoDo version?
My Coding Adventures (Chris Walsh’s Blog)
Been running it on my Samsung Focus since the the updater came out, and I haven’t had any issues at all. I actually used the copy/paste for the first time yesterday… nice feature! What was all the fuss about, it seems pretty simple.
Also I can finally browse the marketplace with it locking up, and it allows me to scroll the list without stopping to wait for the pictures to load.
One major thing that was not fixed is the bluetooth call quality. Still terrible.
Blah blah blah, there always was and there always will be someone who will “fix” the problem and most likely someone else not Microsoft which is why this happened in the first place. People are sick of waiting too long for things which keep getting dragged on.
There should have been a set time allocated to every tel-co provider to test the phones on their networks and it should be rolled out at the same time irrespective of where you live or what type of phone you have. How much testing is need for 1 small OS update??? You cant tell me that these small updates need over 3 months of testing.
If Mango is due at the end of the year then we should see it rolled out by 2013 at AT&T.