Microsoft's latest mobile OS update has locked up some Samsung Omnia 7 handsets and reportedly bricked others. The problem seems to be with specific firmware versions of the Omnia 7, but there's speculation that developer builds or the 64-bit version of the Zune software is to blame. So some users are installing the upgrade …
Considering you have the facts completely wrong, is it the Omnia 7 (from Samsung) or the HTC HD7 (from HTC) that is having the problem?
I have the Samsung and will not be updating it...
It's a Samsung Omnia 7 isn't it?
HTC's is the HD7.
How can an update brick a phone that was already a brick?
This is just incompetence from Microsoft.
Microsoft has had 6 months preparation since Windows Phone 7 was released to the phone manufacturers.
Now that the update has arrived, it performs no useful function, except to brick the phone. It's a phantom update that is purely so Microsoft can practice the art of issuing updates. You could call it a placebo update... the update you think you get when you don't really get an update.
Obviously it has failed. Microsoft must try harder before it can bring the miraculous features of Copy/Paste and full multitasking to Windows Phone 7.
*here we go*
Just to correct you, the update DOES perform useful functions. It makes the update mechanism faster and more reliable, and it seems, from what users are saying, to fix some bugs and speed up the phone a bit.
There, corrected your post for you. Pleasure.
"Microsoft must try harder before it can bring the miraculous features of Copy/Paste and full multitasking to Windows Phone 7."
Personally I'd have thought that microsoft shouldnt really be working on copy / paste for their 'new' operating system. They still havent got it working on Vista. Yes microsoft, you still have customers who were saddled with that vista abomination through the microsoft tax on laptops.
When can we have an OS that works please?
Anyone who buys a Phone 7 phone should really know that simple OS functionality is way, way out of microsofts league.
I am staggered that anyone bought one. People only buy the desktop OS as its a compulsory tax, but with phones there is real choice out there, and yet still people buy toy tat from redmond.
Hmmm, I must not be people, I buy Microsoft products because they work well for me. Not like that crap Linux, I like spending time with my family not debugging code because I something to work. I also don't buy Apple because I don't like paying 4x the reasonable cost of the hardware because it looks pretty and to be honest, shiny isn't really that nice looking once it's got very visible usage marks all over it (form over function as ever).
You cannot cut and paste in Vista? Is your keyboard broken or something?
What is your issue with Vista? I know it is trendy to slag it off and I know there were major issues with dirvers when it first came out, but for day to day use, what is the issue with it that you encounter? Obviously not being able to cut and paste would be annoying...
The fanboys have really downvoted you... Is MSFT now ordering all its employees to flood the Reg's forums, as they do in Endgadget?
Type your bile here - plain text only, no HTML
I'm staggered anyone buys anything else. I mean, Android.....come on, choopy, laggy fragmented bollocks made by an advertising company. iOS....locked-down piece of overblown marketing bollocks made by a marketing company. Blackberry....oh, please. Do I even need to -
Look, before you diss WP7 at least be in possession of a sense of irony.
Re: How can an update brick a phone that was already a brick?
"Obviously it has failed. Microsoft must try harder before it can bring the miraculous features of Copy/Paste and full multitasking to Windows Phone 7"
You say that, but I notice that my HTC Desire HD has Copy/Paste functionality that could hardly be called "miraculous". It's not only woefully inconsistent (some apps support it, some don't and some have different implementations) but also a bit buggy.
For example, trying copying something out of a mail message you've received in Gmail.
Tap and hold does nothing (unlike other apps), you have to hit "Menu" then "Select Text". You don't get little bars to move nor a magnifying glass, you have to tap at the beginning of the text and then drag your finger until the end of the text and let go. When you let go, it goes into the clipboard and the selection clears. Made a mistake? Oh tough, sorry, try again.
Then when you try and paste it into the description field of a new calendar entry all the newlines are lost. Really helpful.
Rag on Microsoft all you want about how they should have supported CopyPaste from the beginning but don't kid yourself that the Android* implementation is any good.
(* could be HTC's fault too, I don't know)
"The fanboys have really downvoted you... Is MSFT now ordering all its employees to flood the Reg's forums, as they do in Endgadget?"
I had to laugh at the two (at the time) MS monkeys who down voted this one.... that did make me chuckle...
WP7 uses a pair of ULDRs (Update Loaders) to prevent real bricking.
One ULDR is flashed during the update process, and during the first boot, if it fails, the other is used to boot in to and flash the rest of the firmware. When the device successfully boots, it overwrites the non-updated ULDR with the updated one.
Unless a user has deliberately circumvented this, there will always be enough code to boot the device in to a state in which it can be recovered rather than being properly bricked.
And your point is?
Are you saying that the update cannot fail or that it must be the users fault?
Obviously this isn't happening, or there wouldn't be reports of bricked phones. You assume that if one fails, the other is miraculously guaranteed to work. There's a good chance Microsoft $%^&ed *both* of them up.
Using two update loaders
Ah, so all I have to do is two update loaders, and it makes it impossible to brick something?
It doesn't matter if the update loader is a complete pile of %%%%, the mere fact that there are TWO of them prevents it doing anything wrong?
RE:And your point is?
"Are you saying that the update cannot fail or that it must be the users fault?"
It does sound just like that doesn't it...?
Not a brick, just stuck
There's a significant difference between a brick, and a device stuck in ULDR.
I'm going with a device stuck in ULDR is far more likely, and is probably what happened.
Zune doesn't have access to the images required to get a device out of ULDR, so recovery is more complicated than just plugging a device in, but the device isn't a brick.
The device boots
Well, clearly the devices are capable of booting, and most are capable of being updated without issues. That to me would imply the ULDR is functional (and that samsung have bollocksed it up)
The fact that only one ULDR gets altered during a flash procedure makes it pretty difficult to break, and from all the reports I've seen, it's a lack of the firmware image required being available that makes the devices useless, and not the update mechanism itself.
If anyone happens to see a *.ffu for the Omnia7, that's what's needed to recover it.
Maybe the update
is to prevent the phone from being bricked during updates...
The update turns
your expensive phone
to a simple brick
(yes I modified a well known haiku)
You made it into a haikan't.
Your update through Zune
has magically transformed
Windows into walls
The recent update
looked out of the windows
and closed the curtains
The author of this article should actually research an issue before writing an article based off forum posts. Had the author read the rest of the posts then maybe we'd have a legitimate article to read instead of this trash piece intended to pander to the anti-MS crowd with nothing more than hearsay.
You know you've got a microsoft phone when...
(The post is required, and must contain letters.)
You look at it and think...
Thank f**k I'm not giving Jobs any more money, this phone is awesome...
No Problems Here!
I have an Omnia 7 and I connected it to my Windows 7 x64 PC last night, started up the Zune software and ran the update.
Not only did the update slide by easily in 20 minutes, but the software also now gives me the option of reverting back to the previous version if I so choose.
Since the update my phone is definitely slightly snappier and smoother, and I'm sure the application menu bounces less distance but the icons spring together more..
I'm not saying it can't happen to others, but I don't believe this story. I don't see an error in updating the OS on the device bricking the device. I could see a firmware update doing it, but not a software update.
Twenty f**king minutes to update the updater. With the phone processor and a modern 64 bit as well you should be able to solve world poverty in twenty minutes not just add a small update to a bl**dy phone.
20 mins isn't bad
Bear in mind WP7 does a full backup (of the internal flash and SD card), so 8-16GB, and this is sent over the simplest interface it's possible to get driving USB for reliability.
20mins really isn't that bad.
Good luck Nokia!
You're going to need it with this lot as your "partners".
Funny that Nokia s40 "dumb" phones have over the air self update capability which does work fine. Yes they can update their own firmware.
wass with all the ms supporters?
really wp7 isn't anything special, then again nor is ios or android. I always run into niggles or something isn't quite right. Right now the main issue is the ability to use it at work. Going to get my grubby mitts on a webos palm pre and see how that pans out.
Nearly got it right
Well, it seems MS nearly got it right. Not too bad for a first attempt. Apple can't get updates right everytime and they make the hardware their updates are installing on.
Given that MS's entire strategy rests on being able to reliably update handsets they had better find out why this one didn't go perfectly. I suppose they can take comfort from the fact that only one of the handset types seems to have been affected. But the next update had better go just right otherwise it will start looking like a bad idea...