[b-suns]

At home I have latest version installed Multilanguage 190. At work I have 167, yesterday I've installed trial version of program (at work), like usual BB rebooted, and WHAT ARE HELL now my version is 167 again! And Manager killed LoaderBackup!!! So be carefully with this

And next more, 60% of battery DIED during the night, the phone was TURNED OFF

[mmuras]

Originally Posted by b-suns

At home I have latest version installed Multilanguage 190. At work I have 167, yesterday I've installed trial version of program (at work), like usual BB rebooted, and WHAT ARE HELL now my version is 167 again! And Manager killed LoaderBackup!!! So be carefully with this

And next more, 60% of battery DIED during the night, the phone was TURNED OFF

On the PC which caused the problem...(the one at your work) did you verify you did the following:

Originally Posted by TroyDBrown

1. Download the above OS file to the PC then install it to the PC by running (double clicking) the file you downloaded.
2. Go to c:\program files\common files\research in motion\apploader and delete the file named "vendor.xml."
3. Plug in BB and double click on "Loader.exe." It's located in the same place as the above vendor.xml file.

Per LINK: http://www.blackberryforums.com/general-9000-series-discussion-bold/160810-latest-os-9000-4-6-0-331-4-6-0-190-multilanguage.html


Basically if the vendor.xml file was not removed on the work PC, then you may have caused your device to revert back to old system......and yes that would suck...

Thoughts?



Link:

[b-suns]

Vendor.xml was deleted for sure, loader.exe wasn't applied, what for it?

[PapiPabs]

If you still have .167 installed at work, either uninstall through add/remove programs, or just click cancel when the update window pops up. Your automatic update may have downgraded your OS automatically when you hooked up to DM at work with .167 installed.

[b-suns]

Originally Posted by PapiPabs

If you still have .167 installed at work, either uninstall through add/remove programs, or just click cancel when the update window pops up. Your automatic update may have downgraded your OS automatically when you hooked up to DM at work with .167 installed.

I always doing it, but this time DM loads 167 system to BB with new software Now switching to 190 again, tiered to enter all the login/pass data in 3rd party application ))

[Klotar]

If you run multiple PC's, you must have the same version of the handheld OS installed on each. I know you know that now, and if you step back and think about it, it makes perfect sense that DM downgraded your handheld OS. It does not "know" that downgrading wasn't what you intended.

There is also an additional wrinkle that you should be aware of, even if you do have the same handheld OS installed on multiple systems: if you remove certain components from one PC (e.g. extra languages, unused themes, sample videos, etc.) but do not do so on the other PC's, when you hook your BB up to DM, you may find that you have your unused languages/themes/videos back. It depends on how you removed those modules (e.g. by renaming the .cod files).

A tip which may help in the future and in case of emergencies: on my SD storage card, I created a directory in which I keep a copy of Desktop Manager, stand-alone Device Manager, the two latest handheld OS's, several backup .ipd files, JavaLoader / JL_Commander, PKZIP, some of my more critical applications in .jad/.cod format (so that I can reinstall from the SD card using the Media Explore function), plus an exported contact list (from Outlook) in .csv format. If disaster strikes, I should be able to recover most functionality, even on someone else's PC as long as I have a USB cord.