Select a language to translate this page!
Powered by Microsoft® Translator
Hi everyone. I know some of you are eager for Samsung Omnia 7 and Focus news.
Today we restarted updating Omnia 7 phones. The restart is happening in phases. Go to the Zune software and manually check for an update. If you don’t see one today, look again next Tuesday when we plan to deliver updates to additional Omnia 7 customers. Operators being targeted in later phases include Deutsche Telekom, Orange, and SFR.
What will be in the update? If you haven’t already received the March “copy and paste” update, you’ll receive one update that includes both “copy and paste” and 7392. If you installed copy and paste before we halted updates to Omnia 7s, you’ll just get 7392. You can learn more about our updates and how to install them from Update Central.
We don’t yet have an update readied for the Focus variant, but we are making solid progress. Mike or I will jump online when we have it definitively scheduled for you.
One final important note. A small number of people who’ve already installed the March “copy and paste” update on their Omnia 7 might have trouble installing 7392, but Samsung today published a new tool designed to fix this. If you get stuck during installation, please see this support article, which contains troubleshooting steps and a link to the new Samsung tool.
Eric Hautala, GM, Customer Experience Engineering
Thank you very much!
So to be clear, we use the new Samsung tool ONLY IF we encounter a problem yes?
I don't know what to say.....What about are you kidding us?! Next phase after another week?! We waiting for Pre-Nodo & Nodo from 22.3.2011. When I bought my Omnia MS said that updates will be availeble for all at the same time...this is laughable :)
@Imperial Dynamics: Yes. According to Samsung, this should impact a fairly small number of folks. According to the support article, you'll know if it impacts you because you're phone will get hung up during step 6 of the install and keep rebooting. If that doesn't happen, you're probably fine and don't need it.
Ok, so I have already installed the samsung patch today as not heard much about uk based install.
Bought phone as soon as came out at t-mobile, uk.
Still on 7004. No nodo, or pre nodo update, or that security patch.
Where does that leave me? I continue to wait patiently.
There are currently 2 problems for Users with the Samsung-Patch:
There is a version of the Bootloader (18.104.22.168) which does not allow to acces the Download Mode unless you use some USB Jig to force it, which makes it impossible for them to install this Update.
The other Problem is with the MacOS Users as Samsung only provides a Windows Version of it's update.
What is Microsoft's idea on how to solve this problem? The later can be kind of averted by using a friends pc but still this isn't looking too good.
@Pault: Your device has most likely a T-Mobile branding and therefore will be part of the second wave starting next week on tuesday (May 24th). At least that's how I understand the article.
@Pault. Thank you for your patience. T-Mobile UK isn't being targeted in this week's wave.
@StevieBallz: Thanks. My boot loader is sitting on 22.214.171.124 so maybe all is shortly to be good.
Happy for all this to just get sorted, so this blog does not continue to grow with more angry comments from other users in my position.
Thanks Michael for the info. Hope the samsung headaches go away from now on.
Great news - a very long time coming but great news all the same. Many thanks :-)
I quote "Operators being targeted in later phases include Deutsche Telekom, Orange, and SFR."
I'm on Orange in the UK, anybody know when these "Later Phases" with commence?
The situation is just crazy. Still waiting and waiting. Are you sure i get update next week?
Help! I have an Omnia 7 and after the update, it hangs. The Samsung tool doesn't work, it just says "wait the device" and my fingers are sore from holding the buttons. My phone is dead! What do I do?
My unlocked Omnia 7 has been updated (NoDo and 7392) THANK YOU, WINDOWS PHONE TEAM.
Now we are waiting for Mango update :-)
Just plugged my Omnia 7 into Zune and the update is showing up.
I am on Orange using an unbranded & unlocked Omnia 7.
Will re-post if all goes well.
@rcbapb: Please call the Samsung Support Center. Not sure where you're located, but there's a number listed in the support article linked above in Eric's post.
@Simon Blackburn: Awesome! Since your phone is unbranded, that makes sense. "Open market" phones were targeted today. Branded Orange phones won't see an update just yet, per Eric' post. Just to set expectations for anybody else reading and wondering.
It took quite some time to FINALLY get the update but still I'm convinced there could have been better ways of keeping the customers informed...
But still, finally it's on my Omnia :)
Hi Eric, my Omnia 7 is still stuck on 7004 and tells me its up to date, will this update it?
Omnia 7 - T-Mobile UK (aka Deutsche Telekom). Thanks for outlining that it will be next week. I'll just be glad to get the update. I sincerely hope Mango is smoother than this (as i'm sure you are). Your proposed update process was the precise reason why I didn't go for an Android device. At the moment though, you guys are doing the right things and keeping my faith.
@Alansonit: Thanks for the comment. Everyone here is acutely aware of what you guys are expecting from us for the Mango update. It's top of mind for everyone.
@danielfarah: Have you plugged into Zune and checked for an update? Who's your operator? If you're not seeing one today, your phone probably isn't being targeted in this week's wave.
Yaaaay. Finally got the update. Now hurry up with Mango! Thanks @Michael Stroh for ur updates on this update.
Got the update aswell, proof MS is and can control the update release/process.
To bad that the Zune client doesn't do an autolookup for the errorcode which i encountered at first: 801812DD
Was able to find the solution via the Help and Support part with clear instructions. Shouldn't be hard to implement, since in this case it was up for grabs. Did provide this suggestion as feedback and confirmed that the provided solution works. Hopefully it's used to provide better service in future.
@OrhanA: Great to hear--and great suggestion. It's on our radar.
@Michael Stroh, wow fast response, positively surprised. Glad to read it's appreciated, i'm full of good ideas :)
well this sounds great... but I am unable to enter the download mode on my Omnia 7 as described in the KB article - the Samsung tool is USELESS! This is so sad :( please give us a Nokia with WP7 - these Samsung devices suck badly when they should be updated!
Can someone explain why there is stll a holdup on the Focus? A different brand of memory really creates that big of a problem?
@myan strange, never heard of an Omnia7 not being able to enter download mode. You sure about the procedure ?
Check if the phone is capable of getting into the ‘download mode’. To do this: Turn off the phone (or remove > replace battery), then turn it back on by pressing the power/camera/VolumeUP buttons simultaneously. When the phone turns on, release the power button. If the phone shows the yellow triangle with exclamation and a “download mode” message, your phone is capable of getting into the ‘download mode’.
Btw, you do have that error for which you need the Samsung tool ? If not, you don't, or better yet shouldn't install it.
@OrhanA thanks for the help - nevertheless I am not able to enter the download mode... your description is the exact same as shown on the Samsung tool.... and that is what I am trying to do.... without success
When I start the phone with this method above to enter the download mode my phone hangs in the "samsung omnia 7" boot screen - I then have to remove the battery to start the phone again
Woo! Update successful on my Omnia7 with Optus. Thanks guys for taking the time to get this update right. Time for some Copy/Paste madness!
@myan: I'm sorry to hear about your troubles. Call the Samsung Support Center per the support article above.
@:jburch: I understand what you're saying. Although subtle, the difference was enough to require the creation and testing of a new update for that population of phones. Hence the delay. I'm sorry you're having to wait, but the team is working hard to get those back on track.
updated my Omnia 7 on Optus, Thanks to all WP7 Team, Great work Guys!!
I have had an issue that has been on again off again. When I try to send a text message , after I type what I want, I am unable to hit the send button at the bottom of the screen if the keyboard is up still. It does not detect any touch at the bottom of the screen. If I hide the keyboard I am unable to hit send. This issue is in email as weel as some other programs I believe. Also It says I have one update for an app, but when I go to marketplace I am unable to click on the "1 update" at bottom of the screen. I had this issues months ago and it went away. It is back now, has anyone else heard of this and is there any remedy for it?
As for the above I have a Samsung phone, I have updated twice to get copy and paste
To all the Omnia 7 users with Download Mode problem:
If you have Boot loader version (126.96.36.199) or a BRICKED PHONE, you need a USB jig. It is about $7.99 on EBAY, just search for “USB JIG Omnia 7” I had the same problem and USB JIG saved my bricked phone. TRY IT, IT WORKS.
Good to see! I'm not too worried about the 7392 update, I would just like everyone out there to have the 7390 update. Enjoying my phone a lot more since that update, and appreciate you all working with Chris Walsh to resolve that update issue as well. Even with all the missing features, NoDo is much more useable.
I'm also enjoying the articles providing some insight about the keyboard, and copy and paste. Good Stuff! Keep heading in that direction, you aren't there yet, but at least you've begun turning the train around, many of us can see that.
POST MY ATTENTION TO ENGLISH TRANSLATE (IS A SOLUTION FOR THOSE WHO DO NOT WANT TO WAIT)
1.- Ocupar ChevronWp7.updater para actualizar a NODO... (el teléfono quedara en un estado "walshed" y no recibirá futuras actualizaciones)
2.- ir a blog.walshie.me/walshed-phone-support-tool-official-fix-to-get-you-back-on-track (allí encontraran la solución para sacar el estado "walshed" del teléfono)
sigan las instrucciones y su teléfono quedara con nodo y recibirá actualizaciones
yo hice esto con mi teléfono Samsung Omnia7 y eh recibido la ultima actualización mediante Zune y esta todo OK
recuerden tener instalado.
x86 Operating System (32 bit) x64 Operating System (64 bit)
Windows Phone Support Tools Windows Phone Support Tools
Thank you, looking forward to Mango and beyond!
Flawless update process for my Omnia, thank you! Already looking forward to Mango...
" Operators being targeted in later phases include Deutsche Telekom, Orange, and SFR." this means...not in wave 2 next week, are you serious?
How many waves do you plan?
Have you any plans when the update will deliver to EVERYONE (will this happen ever?)?
Thank you sooooo much !!! MS you are awesome for not leaving us omnia and focus owners behind !!!! Very cool, thanks to everybody who helped fixing this issue !
Will ever Telefonica from Spain release any update?? It is the only mobile operator in the world which hasn't yet released any update for it's WP7 devices. Will this one arrive before WP7 gets fully obsolete?? Please MS press this mobile operator !!!
Thank you for the updatepost and being clear about the two phases of Omnia 7 update releases.
I'll look forward to Tues 24th May for Feb pre-update (7008) and then a combined March NoDo + May Security (7392) set of updates on my T-Mobile UK Samsung Omnia 7.
One thing you could have done clearer in this post and on the 'Where's my Update' international page is that 'Deutsche Telekom' is the parent company, whereas the consumer branding and mobile company is only known to the majority of people in most of Europe outside Germany as 'T-Mobile'. Took me a while to find that out when T-Mobile was 'missing' from your international page and you can see from the comments even here on this blog post it's still causing confusion for people.
If you check Wikipedia you'll clearly see that it is a 'T-Mobile [Country]' brand that people are aware of by default in Europe - en.wikipedia.org/.../T-Mobile
I suggest therefore that from now on it would be clearer and simpler if you just said 'T-Mobile (non-US)' when you want to specify all the non-US European operators.
Thank you guys, hope next updates will be there in time, anyway Good Job
But why so much time for these update... now I have to wait another week for my Omnia 7 T-Mobile...
Thank you Michael for being here for all of us, now Awesomely (If thats a word) i got the notification for a new update directly to my phone but at the end of the update (Through Zune), it doesnt have the problem that the samsung support tool suggests but i get the error code 80180048. Now I'll be honest, i did "walsh" my phone, but used the official tool to get it back on track, but nonetheless i'll try the samsung tool anyway and report back
Thanks Michael, Eric And Microsoft!
yipeee!!! It was a wonderful surprise when i checked my Omnia 7 today morning wherein there was a notification for an update and i immediately connected my phone & successfully updated...Everything works smoothly...I really appreciate the effort you guys at MS have put in sorting the update issue for Omnia 7 & now the wait is over..Thanks guys and special thanks to @Eric Hautala for regularly updating on this...Cheers
Thanks all for your works, and special thanks to Michael Stroh to be the first to tell us that the update was stopped.
hmm. ok, it didnt update the phone at all, just kept it at 7390
Well NoDo, sure, but I still haven't received the February update either. Will I get that too?
wow. Atlast a definite date. I'd have to wait for another week, but that's ok. Thanks for the update, Eric Hautala
All went smooth. Patience is a virtue. Thanks from a happy customer :)
I have an unlocked unbranded Omnia 7 (Developer phone) on the three network in the UK, I had the NoDo update a while ago but checking after this it says my phone is up to date on (7390) is the 7392 update not yet available to UK Omnia 7's?
I'm stuck with an Omnia 7 having bootloader version 188.8.131.52, unable to install the Samung patch and the 7392 update. Can somebody tell me if samsung is working on a fix, as it seems ridiculous I'd need to buy a USB jig to get my device into download mode.
Awesome, Thanks guys - deployed to my partner and soon to my sister's Omnia 7.
Cheers. Roll on Mango!!
@ andreabarbera I am wondering the same.. but can't see how a fix can be applied without using download mode to update the bootloader. Just a tip if you don't have a usb jig and are handy with a soldering iron I believe you can make one with a simple 301k resisitor and a micro USB plug for next to nothing. Although whether you should have to go to this trouble on a new phone is open to opinion.
@sirrusty @andreabarbera damn this is soooo ridiculoius.... I have done nothing bad or unofficial to this phone... and now I have to order a jig to repair it wow... what has caused the damage that even a factory reset does not help.... sirrusty can you provide some further information for such a self made jig? I think I will try to build one by my own...
I wont go into too much detail myself as I don't want the blame if anyone does it wrong.... but type 301k resistor trick into bing or google . other samsung phones have had the same problem not just the omnia 7. people will have to judge their DIY ability and access to the components.. some will find it easier to order a ready built jig, some people may find it easier to get the components to build one depending on location.
Eric, I'm having a problem with updating my Omnia 7. After using the Samsung Tool and then trying to update to 7392. Zune gets stuck on step 6 and the phone keeps getting stuck at the "Samsung Omnia 7" boot screen and it keeps restarting and restarting but still stuck at "Samsung Omnia 7" bootscreen.
If I pull out the cable, sometimes the phone gets bricked but when I try to update using the Samsung tool again to fix the phone, I can boot up fine but the phone is stuck at 7390.
My samsung omnia 7 just updated to 7392 and is Oputs branded so that's good news for others who want to know. My question is though, why when Nodo was first updated it took 2 months for Optus and other telcos to test and update and release but now the day MS re-release it we get it straight away?? Surely the new update that works on Samsung would had have to go through the same "rigorous" testing it did before so make sure all is ok? Or is this a sign that from now telcos won't need to be involved in the update process??
Still on 7390 (bootloader 184.108.40.206). Stuck in reboot, download-modus not starting.
Like @ andreabarbera says; it seems ridiculous I'd need to buy a USB jig to get my device into download mode.
Any ideas (other then buying a non samsung wp7)
@ SaaMocin unfortunetly the only other options seem to be as Michael says above contact a samsung service centre who will do the jig trick for you (they may also update the phone so you dont have the same problem in the future, thats pure speculation). The Jig seems to be the only fix that does not involve sending your phone away or getting a new one if you have insurance.
I'd love to know the story about the problem: what caused it, how it was found, what was needed to solve it.
Okay, maybe I'm just dense and didn't see this elsewhere, but did all updates to the Focus stop because of the issue with 1.4 versions of the phone? Mine is a 1.3 version and it's already updated to NoDo, but I've seen no activity on the 7392 update yet. I guess I just don't understand enough about exactly how the "phasing" works with update deployment (e.g., what is the control mechanism).
Why has the "Where's my phone update" page NOT been updated this 5-3-2011? It does not reflect the 7392 update (I am an AT&T customer with a Samsung Focus)
another week, I am ok with that, at least we know when we will get the update
Just to be clear: If get myself the USB jig and install the Samsung patch and the 7392 update, will my phone then still require the USB jig each time I have to install an update, or will the Samsung patch resolve the download mode impossibility? I'm not sending my phone away for servicing, that could take three to four weeks probably. For the record: I did not do anything to the phone besides installing the official updates through the Zune client.
To go to download mode: press Volume Up and Camera
just two buttons. Make sure you press Volume Up not "Somewhere there" button.
I updated mine yesterday - was the first one on "Dude WIMU"
The problem is the version of the bootloader (220.127.116.11), can you check if, after the Samsung fix, the version is still the same?
Anyway you can try to go in download mode without JIG...
I have applied Samsung fix (and 7.0.7392) - Bootloader version is 18.104.22.168
Just to add, I'm still stuck at rebooting cycle. Bootloader version is 22.214.171.124
I'm having BootLoader v 126.96.36.199, I'm about to send back my phone in the hopes that Samsung will update the phone.
I'm wondering if buying a jig would really fix it, AND if it would allow to update the phone afterwards like any other "normal" Omnia 7... above that, I wonder that if I buy the jig, and update the USB Driver (which is what the Samsung update tool does), that I will still have that crappy BootLoader version which makes my phone hang when the battery is dead and I recharge it (this alway happens now).
to Zulhardy: sure you restarted Zune and reconnected phone after Samsung fix, didn't you?
Please repost your problem here with your bootloader version at this link.
@Oleg Yes tried more than 6 times already. Still stuck at rebooting.
@ Michael Stroh, thank you for the add'l info on Focus variant 1.4. It's encouraging to see the Omnia 7 back up and running - just hope the efforts on the Focus were running in parallel with the Omnia efforts. Will keep checking back, but again would like to throw out the request that some news be delivered in a week's time - even if the fix isn't fully prepared - just to keep us informed.
I'm a big fan of WP7 thus far - so much so that I got you guys two new converts over the weekend, so keep it up.
Right, so when i have been asking on this blog for weeks and weeks "am i going to have problems with my phone after officialy updating to NoDo when prompted by my carrier" and you completely ignorned me and others. The answer was in fact, yes you are going to have problems and we are then going to tell you to call a number for support from samsung that isn't even freephone.
I have the 188.8.131.52 bootloader. To be told this makes me pretty angry, i have been such a strong supporter of MS over the years. I've bought pretty much every release of windows, i've had both XBox consoles and windows mobile now windows phone devices. Way to reward loyalty... call this number.
What are they going to tell me to do? Some info would be nice.
@ andreabarbera I believe from what I can work out you would need the jig in the future if you require to get back into download mode as I dont think the patch does anything with the bootloader... don't quote me on that yet though...
using it in the future shouldnt cause any issues appart from remembering where you store it, the loader itself is just missing the 3 key combination to access download mode and the USB jig thing is just replicating what samsung use.
Well, I managed to update my phone with bootloader 184.108.40.206, but nog before spending € 1 to buy three resistors at my local electronics store and follow the instructions in this video: www.youtube.com/watch . I managed to get the phone in download mode, install the Samsung patch, and the 7392 update without problems after that. The bootloader version after that is still 220.127.116.11, but I suspect the Samsung patch fixed the download mode problem as the phone rebooted without a problem during installation of the 7392 update and managed to install the error without error.
There are lots of problems reported so far.
My: Bootloader ver. 18.104.22.168
1. If using Samsung update tool – Cant get the phone in DL mode.
- On the phone: rebooting process stack on “Samsung Omnia 7” white color msg.
2. Via Zune - reported that update is available .
- I started the update but process stack on “rebooting the phone” page. ( page 6 of 10 )
- The update zune error code is because I have to disconnect the USB cable – reboot and connect again.
More info here at XDA :
I just tested my phone, still running bootloader 22.214.171.124 but updated with the Samsung patch and 7392, and now it seems to react when powering up holding the camera button + volume up buttons. The phone now displays the "connect to computer" picture, whereas before it would just show the Samsung Omnia 7 logo. It doesn't show the "Download mode" message with the yellow triangle though.
"Operators being targeted in later phases include Deutsche Telekom, Orange, and SFR". Hey, don't rush guys. I'm sure there are lots of other phones that need updating as well. Oh wait, no there isn't. Oh well, what's another week on top of the 13 or so I've waited so far.
Failed! I had not problem until now. Samsung Omnia 7 unbranded. Update hangs at step 6 - reboot.
Got the device update support tool. It won't connect. Samsung don't want to know Where do I go...
@andreabarbera 3 resistors? I take it you used 300K (3 X 100k) with them wired in series instead of 301k. If so thats good news.. will be even easier for people to get hold of the right values.
So what's the USB jig? Samsung (called the UK as there is no contact number for Switzerland) say all problems are Microsofts.They suggest a factory reset. But I don't want to loose all the stuff I cna't backup...
@Michael Stroh: you've been posting a lot of replies on this thread (thanks for that), but still no answer regarding the mysterious 7392 update. Is it being distributed for AT&T Focus users (who already have NoDo -- I'm not referring to those unlucky 1.4 users who haven't even gotten NoDo yet), or not?
When it was first released, there seemed to be a flurry of people getting it, but nothing since.
So have you stopped distributing 7392 to AT&T Focus users? Please, tell us what's going on. It doesn't seem like that's too much to ask.
A USB Jig is just a really simple device to get your phone into download mode if it wont in the usual way.. it works on several samsung phones that have certin issues... if you can get into download mode you dont need it...
@andreabarbera I love the sticky tape solution in that video link you posted... forget what I said about soldering!! unless you want a permanant one for next time.
Well I keep on reading but think I'm at a dead end : bootloader 126.96.36.199 ! Perhaps MS needs to manage the firmware as well as the software...
This sucks big time. I have a Samsung Omnia with boot loader 188.8.131.52 and I am not able to update. MS say call Samsung support. Samsung say this is MS fault. Nice to know they care about their customers
I've got the same issue also located in Switzerland. Do you have any news about this issue?
I've got an unbranded Samsung Omnia 7 bought from brack mägenwil with booloader 184.108.40.206 which is not upgradeable to 7392 because of the missing download mode.
Where did you bought your phone?
Wow, how on earth can Samsung say the bootloader issue is a Microsoft problem? SAMSUNG deviated from the approved spec, not Microsoft! Man, I hate companies that try to pull that garbage.
@ Carol Chisholm I will try and help you decide if you need a Jig... There are very few dead ends.. just pesky little problems that stop one thing working.. lets see if i can help you through them..
you have the bootloader that cant boot to download mode (some lucky ones can.. but most with that number cant).. without access to the download mode you cant apply the samsung fix and it wont connect to the device.. A USB Jig (either homemade for about £1/$1/1Euro, or purchased from ebay or somewhere if you dont want to do it your self (trust me its easy)) should solve your problem as you will then be able to connect to install the samsung patch after plugging the jig in. hope thathelps... or am I reading your issue wrong?
I think the support issue does need sorting though.. for people who do not feel comfortable with such fixes someone should take responsibilty and sort them.
@ Michael Stroh - Would you be able to confirm or deny (or find out) if carriers determine what keyboard language package is installed on our WP7? I have an HTC Arrive and it ONLY shows the US English package. I read that some owners with different phones and carriers have multiple keyboard language packages AND if Sprint is the one limiting me to only US English (I am multilingual) THEN I will have to deal with them (or them with me) directly.
@ Everyone else with an HTC Arrive – Have any of you already received the 7392 update?
Hi. I have bought a Samsung Omnia 7 from Germany. I bought it for its wonderful display. It is a T-mobile device, that is officially unlocked. My bootloader is 220.127.116.11. When I first bought it it came with 7004. I debranded (my phone is developer unlocked) it and I managed this way to get the February update to 7008. After that and at least till Monday Zune did n't gave me a newer update. Since I wanted to test Nodo -regardless the risk of bricking my device - I followed the following guide.
1. Start Zune
2. Turn off Data connection and Wifi on the Phone
3. Connect the Phone with the PC (USB)
4. Start the update search in Zune
5. About 3 seconds later, disconnect your PC from the internet (Turn WLAN off or just unplug your Ethernet cable).
6. Zune finds NoDo-Update. Press OK.
7. Connect to the internet again and install the update.
Everything worked as described except step 6, which gave an immediate update to 7392. The installation was flawless but I am not sure if this was luck or the way it should be. I don't know if any pf these helps but you should be aware that anything beside the official method is at your own risk and that you should n't blame anyone if you came out with a bricked phone.
@pergrill: I'm sorry that you're getting the runaround--that's always frustrating. I mentioned your case to our support team and they've reached out to their counterparts at Samsung. Anyone on this thread encountering a problem after trying the Samsung tool or with their Omnia's bootloader should contact the Samsung Support Center. It's possible that a few of their support staffers might not have gotten the memo. That can happen despite good intentions or preparation.
This is sooooo sad.... it feels harder and harder to defend win phones from day to day - I know guys that told white lies to others that asked about the update procedure.... just to keep a good impression for the phone!!!
Tomorrow I will try to force my omnia into download mode with a self-made jig...
I will then post some results here... hope this helps
i'm scared to get my phone swapped out (ive got insurance so i dont have to wait for repair) so i'll stick to my already replaced one that the bluetooth actually works perfectly on but has a dodgy but Jigable bootloader thanks! best of two evils. my Samsung TV works great, my Samsung camera is amazing, my Samsung TFT monitor is brilliant... so why so many issues with the phones?
Hi, First of all; many thanks for all the updated information!
Secondly; I have a T-Mobile Uk, UNLOCKED Omnia 7 and i live in Malta .. Im on bootloader 18.104.22.168 and version 7004.. Zune is telling me that my phone is up to date when obviously this is not the case. When will i be receiving my update as i live in malta, have a fully unlocked phone yet its branded to t-mobile... ??? .. many thanks in advance!
I think it is important to say thanks where thanks is due.
Thanks to all the MS team. I imagine it is very diffciult to deal with all of us pressuring you to get it right.
With some resevations which i am getting used to not having, (considering i loved Win Mo first) I do love the WP7 concept. Well done from the begining and for your ongoing work.