'Walshied' Windows Phone 7 that won't update? There's a fix for that

'Walshied' Windows Phone 7 that won't update? There's a fix for that

Summary: If you're among the "Walshied" Windows Phone 7 users who are having problems downloading the May WP7 security fix, help may be on the way.

SHARE:

Over the past couple of months, developer Chris Walsh's name has morphed into an adjective (and occasionally, a verb).

Some Windows Phone 7 users, frustrated by the slow pace at which Microsoft and its carrier partners were rolling out updates for Windows Phones, used an updater tool created by Walsh, one of the merry ChevronWP7 band. Suddenly, users were "Walshying" their phones and getting the February and "NoDo" copy-and-paste updates without having to wait for the onerous carrier testing and Microsoft notification process.

There was some debate as to whether, once a Windows Phone 7 was "Walshied," it would be able to get any updates that followed NoDo. When Microsoft began pushing out a security update (the "7392" OS update) to the phones this week, it was the moment of truth.

According to Microsoft -- via a May 4 blog post by Director of Developer Experience for Windows Phone, Brandon Watson -- those with Walshied phones were out of luck. From Watson's post:

"With Windows Phone update build 7392 going out to phones via the official update mechanism, those people who have used the unsupported method of forcing 7390 onto their phones will find that their phones will not update to 7392. With the official update process there is a requirement that the package on the phone also be official in order to update itself."

I've heard from some Walshied phone users that they were able to get the latest update But some were not.

Watson said the team didn't have time to spend "undoing this specific problem." Watson blogged that Walshied users who couldn't get the latest 7392 update would "most likely have to return to a store and submit your phone for a manufacturing return." He added, "However, because of this known error code, it is up to the mobile operators as to what they want to do with your phone."

Watson added, though, (without naming them directly) that the Chevron team is working on a fix for those Walshied phones that will, the Chevron team believes, solve the problem. Microsoft plans to "validate" this fix once it's done before officially letting users know about it.

No one's saying when Walsh's fix may be done, but it sounds from folks with whom I've spoken that it most likely will be completed either later this week or early next. No word on how long Microsoft will take to vet it once it's complete. The bottom line: Walshied phone users who are hitting the 7392 roadblock -- don't despair. Help sounds like it's on its way.

Topics: Microsoft, Mobility, Telcos, Windows

About

Mary Jo has covered the tech industry for 30 years for a variety of publications and Web sites, and is a frequent guest on radio, TV and podcasts, speaking about all things Microsoft-related. She is the author of Microsoft 2.0: How Microsoft plans to stay relevant in the post-Gates era (John Wiley & Sons, 2008).

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

23 comments
Log in or register to join the discussion
  • what a mess

    being Microsoft, it will take around 10 years to get sorted all the issues they are facing. Remember, it took them around 20 years to have an half decent working OS, so the 10 years for WP7 span may be optimistic.
    theo_durcan
    • RE: 'Walshied' Windows Phone 7 that won't update? There's a fix for that

      @theo_durcan <br>What WP7 issue?
      illegaloperation
      • Windows Phone 7 is one big bag of problems

        @day2die
        Windows Phone 7 is riddled with issues that to this day are not fixed.

        Why does multitasking not work for 3rd party apps?
        Why is a Windows Phone unable to log onto a Wi-Fi hotspot that uses a static IP or hidden SSID?
        Why are Windows Phone 7 users forbidden from using a custom ringtone?

        There is a long list of Windows Phone 7 problems that need to be fixed. But Microsoft has not yet done it.

        It is this frustration that caused many Windows Phone 7 users to try to break free of Microsoft's walled-garden, and use Walsh's updater. Microsoft has deliberately blocked jail-break Windows Phones from ever being updated again.

        These are not broken phones. This is Microsoft deliberately blocking those phones from future updates. People should realize that this is the situation that you find yourself in, if you buy a Windows Phone. Either slow, painful updates (eg the NoDo fiasco), or getting blocked by Microsoft if you try to update it yourself.
        Vbitrate
      • RE: 'Walshied' Windows Phone 7 that won't update? There's a fix for that

        @zndac
        1. Those are limitations that are being fix in Mango. How much stuff do you want in a software that was developed in 18 months?

        2. Those are unofficial updater as is not supported by Microsoft. It is the same reason updates doesn't work on other jailbroken or rooted phone. Oh, and Microsoft is not deliberately blocking people from updating and is corroborating with Chris Walsh on fixing the issue. Has Apple and Google ever done that? NO.
        illegaloperation
      • RE: 'Walshied' Windows Phone 7 that won't update? There's a fix for that

        @zndac

        The phones just work and are significantly better than anything else. Your particula issues appear to be yours. I don't need 3rd party multi-tasking, it works fine on my static IP hotspot and I thank GOD it doesn't have custom ringtones (just around 200 to choose from). In any case, we get all that later in the year.

        There was no need to jailbreak the phone besides personality problems or an inablitity to wait for anything.

        It works great now, it will have even more features in the future. Perhaps you could actually use one for a while before ranting ;-)
        tonymcs@...
      • RE: 'Walshied' Windows Phone 7 that won't update? There's a fix for that

        @zndac

        There is a difference between "problems" which are by design, and those that aren't.
        "Why does multitasking not work for 3rd party apps?" because they decided not to implement it in the original release (presumably time constraints). They are implementing it in Mango.

        Other questions: by design (many of these decisions I presume are due to time constraints or other). But since when is the lack of a feature a "problem"? It still functions the way the designed it to.

        This is not a WP7 issue created by Microsoft. It came as a result of using unsupported updating tools. Yes, they may have deliberatly blocked it... or they may have not. According to them, Chevron didn't fully update it, and they couldn't be bothered making the updater work with unsupported update methods (time constraints or so that people get the message that they shouldn't be following unsupported methods)
        xnederlandx
      • RE: 'Walshied' Windows Phone 7 that won't update? There's a fix for that

        @zndac
        I see what you mean. Please understand, MS can't fix what isn't there yet. WP7 was designed, developed and launched within a tight, ambitious schedule. Without certain features that power users and even average consumers have come to rely on from Windows Mobile, Android and iOS.

        A lot of these features come with Mango, the next update, while the features that have made it in WP7 so far, offer a unique, smooth experience. The level of frustration is probably more related to how long WP7 users had/have to wait for NoDo and their patience.

        Anyone interested in the WP7 design and market goals could have known about what you consider a walled garden, before getting frustrated with WP7 about the features, Marketplace and automatic updating.

        Anyway, MS and their partners should have learned a lot from the NoDo update. So people can expect better, without anything slow, painful or DIY.
        Forrestall
    • RE: 'Walshied' Windows Phone 7 that won't update? There's a fix for that

      @theo_durcan

      Windows 95, Windows 2000, Windows 2003, Windows 2008 and Windows 7. Hmmm...I just rattled off 5 Operating systems in the last 16 years. Time to hit the books man.
      Rob.sharp
    • RE: 'Walshied' Windows Phone 7 that won't update? There's a fix for that

      @theo_durcan

      Maybe just a WP7 674 000 units sold at retail!!

      Wake up Nokia.

      http://www.bgr.com/2011/05/03/674000-windows-phone-devices-sold-to-date-analyst-suggests/
      Sultansulan
      • RE: 'Walshied' Windows Phone 7 that won't update? There's a fix for that

        @Sultansulan
        Who knows, maybe Eldar's estimate of 674.000 is correct.

        However, it seems to me Canalys estimated phone manufacturers shipped about 2.400.000 WP7 phones, just in Q1 2011 alone. December 2010 MS stated phone manufacturers shipped 1.500.000 phones in the first six weeks after launch. January 2011 MS stated that number had risen to 2.000.000.

        http://canalys.com/pr/2011/r2011051.html

        So I find it hard to imagine that the relatively few carriers and retailers worldwide, that actually sell WP7 to consumers, ordered 2.400.000 more WP7 phones in Q1 2011, if they couldn't sell most of the first stock of 1.500.000 to 2.000.000 they ordered in Q4 2010.

        Anyway, I think Nokia was already wide awake a few months ago. The WP7 deal is sealed, Nokia and MS are working hard together to ship the first Nokia WP7 in 2011.
        Forrestall
  • RE: 'Walshied' Windows Phone 7 that won't update? There's a fix for that

    I unbranded my Focus to get NoDo and I had no problem getting the new security update. Tg I didn't do it the Chevron way, though they will probably have the fix out soon.
    briggins
  • RE: 'Walshied' Windows Phone 7 that won't update? There's a fix for that

    they so did this on purpose to prove a point
    koolin_
    • No they warned people when this buggy updater was released that it would do

      this. If you run something thats leaves your phone in a bad state you shouldnt expect MS to put in special code and test resources to handle it.
      Johnny Vegas
  • RE: 'Walshied' Windows Phone 7 that won't update? There's a fix for that

    What is the reason to validate that there is a 'legitimate' version/package on the phone in order to update? That is just asinine and stupid on the part of Microsoft, as well as an attempt to punish people for daring to update their phone in a way Microsoft doesn't like.
    Lerianis10
    • RE: 'Walshied' Windows Phone 7 that won't update? There's a fix for that

      @Lerianis10
      Perhaps they decised to do this because of issues they have been having with updates?
      It makes sense that you want to check everything on the target phone is OK before you update... otherwise something unexpected could happen to the phone which may damage something.
      xnederlandx
    • RE: 'Walshied' Windows Phone 7 that won't update? There's a fix for that

      @Lerianis10
      I think it is just to help ensure a troublefree automatic update as part of the smooth consumer centric experience MS has designed for WP7.

      The average WP7 users probably prefer this over the kind of control and manual update some Android power users prefer.
      Forrestall
    • RE: 'Walshied' Windows Phone 7 that won't update? There's a fix for that

      @Lerianis10 <br><br>I'm sorry but you should validate any package before installing it on a device which contains personal information. MS does this to protect the consumer! Imagine that...a company doing something to protect the consumer! Apple and Google might learn a thing or two from MS. <br><br>You have to give some love to MS for providing a Walshied fix. They don't have to do this but they also want people to be able to use their phones. I'm sure they're also aware that carriers won't accept exchanges for these phones.
      Rob.sharp
  • RE: 'Walshied' Windows Phone 7 that won't update? There's a fix for that

    Trying to figure out the logic of hacking an expensive phone to get an update that one was going to get anyway ? I am not aware of any local that not pushed the nodo update, so why the fuss? Try hacking your ps3 game console or your iPhone and see how fast of a mess that makes. BTW posting this on my fab wp7 - LG optomis and this thing is sweet!
    kallal@...
  • RE: 'Walshied' Windows Phone 7 that won't update? There's a fix for that

    This is nonsense. I have the Focus. First off I have never had an update issue. 2nd, I used the Chevron team updater for prenodo and then nodo. Then finally about 3 weeks later when at&t got off their lazy pompies (I.E. As*es), I recieved the over the air update notice. Then I plugged into Zune and installed the "official" bits, both prenodo and nodo. So my phone is fine and I will recieve the security update guess when? When AT&T decides I can finally have it!<br>Most of these supposed update problems are non-sense. Everyone I talk to agrees.<br><br>Anyway, I can't wait for Mango to get released to finally shut all of the doubters up (I.E. iNaives)<br>Mango will stomp a new hole in iOS, that I can promise!<br>Mango is a HUGE update, and I do mean HUGE.
    mikroland
  • Send Back to Manufacturer?

    <i>Watson said the team didn?t have time to spend ?undoing this specific problem.? Watson blogged that Walshied users who couldn?t get the latest 7392 update would ?most likely have to return to a store and submit your phone for a manufacturing return.? He added, ?However, because of this known error code, it is up to the mobile operators as to what they want to do with your phone.?</i>

    I find it hard to believe that WP7 phones do not have a restore feature. Please tell me it does.
    WarhavenSC