North East Bytes - a Microsoft technology usergroup in North East England.

Powered by Squarespace

« NEBytes March: Bytecast out now, Automation event next week | Main | Windows Server User Group returns with April 6th event in London »

Pre-NoDo WinPho Update Woe

After complaints about the lack of updates to Windows Phone 7, the first feature update, codenamed NoDo is practially upon us (after being delayed, obviously). NoDo brings performance improvements and everyone's favourite smartphone feature - copy and paste. It seems that Windows Phone 7 made it out of the door with some deficiencies in the updating procedure, so we've been provided with a pre-upate update to update the updating.

Sadly for many owners of Samsung handsets, the pre-NoDo update didn't work, and a small number of phones were even "bricked" by the update (the "fix" being to go back to the shop and swap it for a working handset). Fortunately I didn't get stung by this - I'd actually attempted the update before reading that it may kill my phone, but having attempted it on my netbook, I didn't have enough disk space available to do it.

Good news though - Microsoft pulled the update before it caused too much damage and released a new, better version making the Samsung-specific problems a thing of the past.

Except it didn't.

I am one of a number of Samsung owners (I have an Omnia 7, but the Focus is also affected), who is experiencing a problem installing the updated pre-update update that updates the updating. Specifically, the process times out and offers up error code 800705B4. Microsoft has [sarcasm]provided a solution[/sarcasm] to this issue on the Microsoft Answers site - "temporarily delete media items from your phone and try the update again".

This fits in with advice on the Windows Phone Help and how-to pages about updating, which is linked from the Zune client when the error appears where it says that "Windows Phone Update requires that there is some extra space on your phone while it's being updated." Sadly neither that page, nor the "answer" on Microsoft Answers says how much space this specific update needs. You'd think they'd be able to know that fairly easily.

When I first received error 800705B4 I only had about 400Mb free on the phone, so I followed the advice and first removed all of my music from the phone. This left a whole gigabyte free, but the update failed again. I then removed some videos, taking the free space up to 1.3Gb. Failure again. Removal of pictures and podcasts took me up to 1.7Gb free - still no joy. Next I'm going to have to start on app removal.

Looking at some of the posts on Microsoft Answers, people have started out with as much as 3Gb free and removed content to free up over 5Gb in total, but they're still getting 800705B4! I would love to see Microsoft telling us how much space it needs, or some evidence that 1.7Gb or even 5Gb is not enough! As it stands, their "answer" - that the update needs more free space is at best a fluke.

I can understand that the phone needs some space free to be able to complete the update, but surely it doesn't need several gigabytes. If that was the case, then this problem certainly wouldn't be specific to Samsung phones! Clearly something is still very broken with this update on certain Samsung firmware versions.

I'm starting to think that I may need to do a factory reset on my phone in order to get the update on. It wouldn't take me long to get back up and running with most apps (although reinstalling them all will be a pain), and I can re-sync my media. The main problem is that Windows Phone 7 has been positioned as the Xbox Live phone and anyone who has to reset the device will lose any progress that they've made in any games because there's no way to backup or restore application data.

As an early adopter, I expect some pain with a new technology, but this is getting a bit pathetic. I'm nearly mad enough about it to create a Facebook group!

PrintView Printer Friendly Version

EmailEmail Article to Friend

References (3)

References allow you to track sources for this article, as well as articles that were written in response to this article.
  • Response
    Attention ! I just found a glitch in your post! Check if css is placed right!
  • Response
    Hi there can I quote some of the insight from this blog if I link back to you?
  • Response
    Response: XardfFsU
    Pre-NoDo WinPho Update Woe - Blog -

Reader Comments (4)

I am really nervous about this as I have added a microSD card to my Samsung Focus and we all know what a debacle and never resolved question that was. I am on AT&T and neither my Samsung Focus or LG WindowsPhone devices have received notification of the update availability. That is my bigger concern as it reminds me of the Droid platform I left.

March 9, 2011 | Unregistered CommenterJKav

I don't like the idea of carriers having control over update releases either. In fact I normally buy unlocked phones for that exact reason.

One thing that I didn't say in the post was that I'm a bit concerned that we might have this kind of fiasco every time an update is released. If I'm going to have to factory reset my phone to add new functionality each time, then I'll be changing my phone!

Hopefully this update to the updating mechanism will make life easier in the future.

March 9, 2011 | Registered Commenterjonoble

This is why I am sticking with my Droid. MS has a history of releasing software that is "swiss cheese" and then releasing updates to fill the holes. I really don't like the "scorched earth" approach that MS recommends, removing everything from your mobile to complete an update is to say the least, ridiculous.

April 21, 2011 | Unregistered Commenterbestandroid

In fairness, I should have updated this to say that Microsoft did release a tool that would enable the update to complete without wiping everything out. I wasn't patient enough to hang around and wait for that to appear, but at least they should have some credit for solving the problem.

May 9, 2011 | Registered Commenterjonoble

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>