New Instructions in the Stickies for Upgrading OS's
Please Login to Remove!
Many of you will notice that I have updated the instructions in all the "Latest OS" sticky threads. Instructions for downloading and using Desktop Manager to update the OS have been removed.
Every OS installation file installs with a copy of "Loader.exe" which will run Application Loader all by itself without Desktop Manager. This Loader.exe will do the backup, install the OS and restore the backup, just as Desktop Manager would. You can use it to "add" 3rd party software and doesn't change the procedure used for removing .cod's that I have listed in my Memory Optimization thread.
The main reason for this change is due to the Automatic BlackBerry Update feature new in Desktop Manager 4.7. This feature looks to the internet for new device software (carrier specific) and actually loads another hidden vendor.xml file in some cases and will prevent installed OS's from loading to the BlackBerry even though the user deleted the normal vendor.xml. There have been a LOT of "My BB won't update" complaints in the forum recently and this should eliminate many of those. Also, using Loader.exe makes the process simpler by requiring only one download, thus eliminating the confusion of the two downloads for DM and the OS.
It's been there forever and I've used it to load OS's for quite some time. Desktop Manager is great to have and there is a need for it but for a simple OS upgrade, it's beginning to be a thorn in the side.
I read on another forum that this will not work if you're on a BES. (it won't activate). I'm about to update from .81 to the latest version from AT&T tonight and want to make sure before I do. Has anyone on BES used this method to upgrade?
Just connect to DM after you're done with the upgrade to start EA. When you do the upgrade you can also run Loader.exe from a command prompt and add the switch /provision and it will EA (if you're connected to the mail server properly.)
Personally, I just do the OS upgrade, then I check out a few things then plug in to DM to start EA when I'm satisfied the OS is working ok. I hate to EA only to find an issue with the OS and then downgrade and have to EA again.
Now that I think of it I don't think I was plugged in to DM when I started the Enterprise Activation last time. I also checked things out before I added more things on to it. Why would you be plugged in to start EA?
My only comment is that for those of us on BES, you need DM running while Outlook/Lotus is up with connectivity to the server; if you want EA to go through w/o having to wait for normal business hours to have your IT group give you an OTA activation code. (For those of us who get entirely too much email everday and upgrade on the weekends in the middle of the night, you can see how this would be an issue...)
Other than that, using only loader is much simpler and sometimes needed when dealing with 523 or 507 errors.