This morning, we started rolling out the ‘Mango’ updates to around the world; at the same time, developers can all update their devices to Windows Phone 7.5 without having to fall back to the backup taken at the beginning of the provisioning process. This update is being made available to those running build 7712 on a retail device that was updated to ‘Mango’ using the provisioning tool we published to Connect a couple months ago.

 

To receive the update, connect your retail device to your faithful Zune client. The path to RTM will be applied in two parts:

• First, your device will receive the update that takes your phone from build 7712 to 7720
• Next, the update will clean-up the pre-production provisioning and repoint your device to the production update servers

 

Once provisioned back to the production servers, your device is then ready and capable to receive updates specific to your device/carrier combination, making it possible for you to receive such updates as drivers and firmware. If your device had drivers made available over the summer, you should see them immediately; and in the coming weeks, you should see the Windows Phone 7.5 device updates from your carrier as they are available for your device. Check out the ‘Where’s My Phone Update?’ page for the latest global status info.

 

This is great news!

 

At this point, you’re back in a happy place and able to be supported once more by your carrier. And even better, thanks to some extra work by our engineering teams, this means that most of you will not need to restore back to 739x, and that your data and settings will remain intact – meaning no saved games.

 

There are a few caveats to this process that it is worth noting:

• Download Zune 4.8: For best results, you should be running version 4.8.2345.0 of the Zune client. To update your Zune client, click on ‘Settings’ -> ‘Software’ -> ‘General’, and click the ‘Check for Updates’ button.
• Support scoped to 7712: This de-provisioning process has only been tested on devices updated (a) using the provided provisioning tool and (b) running the pre-release build (7712) released via the pre-release servers. Folks still running on build 7661 should be provided the 7712 update as part of this update process. All other pre-release configurations are untested and unsupported.
• Phone Backup and Disk Space: The first step of the update to 7720 is for Zune to perform another backup of your phone. As such, make a copy of your 7390 backup before you start on the update process (you may still yet need it) and be sure you have enough free disk space on your computer to support the backup.
• Driver updates may trail: The dev de-provisioning process occurs separately from the Windows Phone 7.5 update process for the general customer base on the production servers. Once provisioned back to the production servers, you may still have to wait to be eligible for your device-specific updates. As such, you may still experience some quirks with your device until you receive device and carrier-specific updates tuned for your specific device. We will try to provide additional data here to allow you to know when you’re retail device is finally ‘done’, but I don’t have that information to share at this point.

But wait! Protect that backup!

Lastly, in the known issues category, it has been observed that a small number of users may not receive device-specific updates released in the July timeframe. As such, you should absolutely be sure to hold onto that copy of your 739x backup before you begin the update process and continue to keep it in a safe place.

 

Windows Phone updates are cumulative in nature, and assume the presence of those that came before them. As such, getting a later update without the earlier one can put you in a less than ideal place. For folks who fail to receive a prior update, they may need to resort to using the 7390 backup in order to receive these updates. While there will be a few folks that this won’t help move forward to a supported state, it’s best to be prepared in case it happens to you.

Closing out the OS Beta

With this post, we’re officially declaring this program closed down. J I am no longer processing Connect invitation requests, and I will also be removing the provisioning binary files from the Connect server.

And, on behalf of the Windows Phone Division, I would like to take a moment to extend a heart-felt thanks to everyone that collectively participated in the ‘Mango’ OS Pre-Release. We updated over 75,000 devices over the past three months. Thank you for your patience in getting the invites and working through a process that was quite manual this go around. I’d also like to thank our App Hub support team that helped troubleshoot issues with updates and missing invites; and thanks to the engineering team (John Menter and Andrew Brown, specifically) for monitoring the boards and troubleshooting your issues; and a warm thanks to our active App Hub users for supporting your peers.

 

Thank you to all for helping to test the update process, yielding a better experience for our customers; and thank you for getting your apps built and tested in time for our Mango roll-out. It’s been great having you on board for the road to Windows Phone 7.5!

 

Most of all – thank you for being a Windows Phone developer, and collectively supporting our platform.

Great news Cliff. Thank you for all the hard work MSFT WP7 teams have put into this.  You all did a great job! I happened to be one of the ones who rolled back to 7390.  It seems the update is going to dev beta phones first.  Any hope for myself and other people for getting the update quickly or are we on the same time table as the rest of the world?

Thanks Cliff and thanks to all the folks on the Windows Phone Dev team! :)

Just installed the final bits at beta 2 refresh device (LG-E900).
Very smooth update - no problems.

Thanks for the great job!

It's great that we don't have to go back to NoDo to update. I know dev devices are not meant for normal use, but... I know you know that people can't just not use these devices, especially with Mango stuff!

My LG E900 update is going on the third update cycle, don't expect anything to go wrong and soon I'll be happily Mangoing on. Thanks to the whole team!

What is the final OS version for mango RTM?

Kieran Kelly:

What is the final OS version for mango RTM?

7.10.7720.68

Cool very painless on my Test Phone, now I have 7.10.7720.68.  Not sure what I am waiting for next, as I don't have a Carrier.

I Guess I Just need the Visual Studio Phone RTM(Mango) Tools  now

Just updated my HTC Trophy on Verizon to 7720.68  and  I have NO DATA service at all.   I have tried toggling data in the cellular settings and done a *228 etc..

No DATA at all.  No 3G indicator ..  Phone service works fine just no data.

I'm restoring to the backup since I need this phone.

So..  I guess point is.. its not all painless.  YMMV.

Thanks for the post Cliff, I think a lot of people were hoping for a post like this.

Just updated, nice surprise in not having to restore back.
Great work Windows Phone team!

Great news and no problems with my update but i would like to ask a one question. When I got to the pandora website to play music it is really really quiet when i have my phone set for mobil browsing and when i switched it to desktop it got a whole lot louder for 1 song then it went back to its quiet self. And both volumes are set to the max. Is this a problem with the phone or pandora?

OK now it is loud again after playing through half a song... And the next song is loud ya!

Cliff,

You assisted me in getting the Dev beta when my email address was somehow wrong on the hub, and I thank you for that.

Now I have to throw in a great big thank you for this bit of work.   It was unexpected, like when my Wife buys me ice cream when she goes to the grocery store (and nearly as sweet).

The entire WP7 team deserves a big round of thank yous from all Developers.   They said they would do their best for developers, and I'm not sure what else they could have done.   @Joebelfiore said he would fix the update process after NoDo, and he and his team did that.   Users will be very happy with Mango, and that will drive more people to the platform.

Guaranteed.

-thanks again
-e

My experience updating LG Quantum on AT&T to the RTM:

I first went to Zune and told it to delete all the synced media.  I always do that before an update, since it is SO easy to put back on.  It speeds the update process by quite a bit.

Updated the 7712 to 7720 with no problems, although the "Syncing" step took a while.

In provisioning out the Beta bits, a bit of hitch in the update process when Zune seemed to hang at determining the amount of disk space for the update.

I read a few posts suggesting other users had had this problem in updating to 7712.  Things seemed pretty safe.

After taking a deep breath and praying to the software gods, I cancelled the update.  I didn't reboot the phone or the computer or even exit Zune.

Zune said I had an update ready, I told Zune to install it.

After that, the phone went to the next step "Installing LG Update for Windows Phone", after creating "another" backup.

Seamless after that small hitch.

Kudos to the team!
-e

I've just updated to 7.5 however im not seeing the add hidden network feature or the bing music feature! I have a LG Optimus 7.

THANK YOU!

My LG C900 worked flawlessly during the upgrade. Even the LG updates were downloaded (I was a little apprehensive about getting the LG update in due course because LG had been totally silent. Of course, AT&T confirmed a few weeks ago that GA would be "this fall" and wouldn't you - fall has arrived!!

Once again a very big thank you for helping us avoid the roll-back for the upgrade. Yeah, it would have worked but the fewer hurdles we have the faster we can meet our deadlines.

Regards.

Well done guys, thanks for going the extra mile.

ok guys i have an Omnia7 currently running Mango Beta 2

The update process went on , first i had driver problems for which i had to download the fix it tool.

and now i have the 80180048 error.

What do i do now ??

ive never used the chevron unlock or any other methods to date. and theres no info on what the error is either
so what do i do now ?

This is amazing thank you so much, I was not looking forward to losing everthing on my phone.

I'm having the same problem on a Samsung Focus :(

When I connect my Win Phone which is running 7712, I connect with Zune Client  version 4.8.2345.0, I get the update notification, but when I click the install button, the update process just hangs (while attempting to compute required disk space to install the update.)  I attempted the update twice with the same results.  Each time I waited about 10 to 15 minutes.

Is anyone else experiencing this problem?

Thanks

My HTC HD7 updated to 7.10.7720.68 without issues.   Then the firmware was updated.   Everything seems the same, just faster after the update.   Probably the firmware update helped.

I was worried that it would take hours and involve a roll-back.   Instead the two updates took about 20 minutes.

Disclaimer: I'm a product manager; I'm not in engineering nor in support -- that said, just trying to help...

From conversations I've seen/heard:

- For the hanging on backup, I've been told that some folks take a loooong time on the computing disk space...you can either wait for that process to complete (which can be particularly long if you have an SD card or lots of music/videos/data on the device), or you can elect to cancel the backup (Zune allows this as of the 4.8 client). If you cancel the backup, you better damn well know you have your NoDo backup somewhere. :o

- For the 80180048 error, that is almost always a result of the Walsh update tool or using the support tool. The 7403 update was supposed to have fixed that issue, and if you updated to Mango before 7403 was put out there (first 2-3 weeks of the program), you may still have some residual confusion in your device. I've been told that a hard reset may fix the problem; otherwise, I would say roll back to NoDo and update again (which should fix the issue). Other folks here on the forums may have other/more useful suggestions.

Hope this helps; glad it's working for most, and sorry to hear some are having pain.

My dev phone is still at NoDo. I need to test Mango readiness of my apps. My phone is not scheduled to be updated yet.
So how do I install the pre-RTM version so that I can test? I really shouldn't wait weeks, as I'm behind now.

I had the same hanging problem just before the clean-up update.  Cancelling out and starting again [after clearing the (previous) 'Update Successful' and 'an update is available' messages from my phone] cured the problem.  Then I got the HTC updates and now - I can use all the 7.5 goodies, including the augmented reality stuff that hooks into the Motion API.  Virtually pain free.  Now I don't have any excuse to put off finishing that killer App any longer.