Why Won't My OS Update?? I Deleted The Vendor Xml file!! - Page 2

DonNguyen · #16 12-21-2008, 05:41 PM

great write up CX

ben-kelley · #17 12-21-2008, 05:53 PM

I have downloaded .83. seemed to work great at first but then i noticed that app cntr and browser were missing. i removed the battery a few times and everything came back, but then I have noticed while phone was sitting idle it came up with a "523 error" on a white screen and was locked up. Can anyone shed some light on this.

Crucial_Xtreme · Thread Author #18 12-21-2008, 06:01 PM

Go to Options>Advanced Options>Host Routing Table>Menu>Register Now. After you receive the activation email, if the Browser doesn't come back pull the battery and replace it, or resend service books.

Posted from my CrackBerry at wapforums.crackberry.com

ben-kelley · #19 12-21-2008, 06:09 PM

i pulled the battery, the icons came back. the problem is that when the phone is idle and on the charger i am getting a "523 error reset" and a white screen.

Crucial_Xtreme · Thread Author #20 12-21-2008, 06:17 PM

you can try pulling the battery a couple more times, although I doubt it will work. I hope you have backed up your device recently! If the pulls do not work, check my guide in the How-To forum on how to wipe with JL_Cmder. After you wipe the device>plug in device>Open DM>Apploader>Add/Remove>and install the Core Applications. After it is done, return to the main menu>Backup/Restore>and restore from a previous backup.

Posted from my CrackBerry at wapforums.crackberry.com

xxfire · #21 12-21-2008, 06:20 PM

so why am I doing this update? I just got my Storm 4 days ago and it seems to work great... What are the "gains" seems nothing but hassle to me..

Crucial_Xtreme · Thread Author #22 12-21-2008, 06:22 PM

If you feel that your Storm is working fine, then do not update. Only those who's devices aren't working so well, are updating, or those who just want to install the newest. By no means do you have to install this OS.

Posted from my CrackBerry at wapforums.crackberry.com

enilm · #23 12-21-2008, 07:24 PM

Quote:

Originally Posted by xxfire

so why am I doing this update? I just got my Storm 4 days ago and it seems to work great... What are the "gains" seems nothing but hassle to me..

Here at Crackberry, we don't believe in "if it ain't broken, why fix it." We upgrade no matter what, lol.

sciddl · #24 12-21-2008, 07:41 PM

Quote:

Originally Posted by Crucial_Xtreme

@sciddi: you need to follow the directions in this guide. Then download .83 and double click to install to your computer. Then delete the Vendor Xml file. After that, plug in device>open DM>and it should prompt you to update.

Posted from my CrackBerry at wapforums.crackberry.com

Roger, followed instructions 3 times. I got the prompt to update. The update looked clean until it reset the device. Then I got an endless loop of "app error 200". I have redownloaded the update for fear it wasnt a good d'load. No dice. I believe I will wait for an official verizon update. They are more stable anyway.

Thanks for the assistance.

Crucial_Xtreme · Thread Author #25 12-21-2008, 07:50 PM

NP. It is a 3rd party application that is more than likely causing the problem. I would suggest going back to .76. But I do want to tell you that there is no difference between the beta and the Official version.

Posted from my CrackBerry at wapforums.crackberry.com

sciddl · #26 12-21-2008, 07:53 PM

Ok. thanks for the info. I may try again if I have a few hours to burn. Look forward to seeing more about the storm!

Crucial_Xtreme · Thread Author #27 12-21-2008, 08:13 PM

Quote:

Originally Posted by sciddl

Ok. thanks for the info. I may try again if I have a few hours to burn. Look forward to seeing more about the storm!

Alright cool. I have a guide posted in the How-To forum on wiping with JL_Cmder. Check it out, it's good help.

Smuuth · #28 12-21-2008, 09:48 PM

Great post, C_X and I am sure it will help quite a few people.

Only one issue some may run into if they have used the self-extracting install package (470_b050_multilanguage*.exe) originally to install Desktop Manager. When they used that self-extracting .exe to install, it does not leave the .msi files on the disk, but puts them on there temporarily then deletes them after install.

This means that when they try to modify the Desktop Manager installation as you suggest, there will be one or more files the installer looks for that it will not be able to find.

The solution is to first highlight the installer self-extracting .exe file and extract those files into a folder on the desktop. When the installer cannot find those install files it needs, just browse to that folder (it should have the same name as the self-extracting .exe file and will contain the Blackberry Desktop Manager .msi file as well as all the component files.)

The modification will then proceed as it should.

Of course, if this is too complicated, they can always just remove the Desktop Manager and then re-install it as you also pointed out. Of course, removing the Desktop Manager will remove the device OS software as well which will have to be re-installed.

Crucial_Xtreme · Thread Author #29 12-21-2008, 09:51 PM

Quote:

Originally Posted by Smuuth

Great post, C_X and I am sure it will help quite a few people.

Only one issue some may run into if they have used the self-extracting install package (470_b050_multilanguage*.exe) originally to install Desktop Manager. When they used that self-extracting .exe to install, it does not leave the .msi files on the disk, but puts them on there temporarily then deletes them after install.

This means that when they try to modify the Desktop Manager installation as you suggest, there will be one or more files the installer looks for that it will not be able to find.

The solution is to first highlight the installer self-extracting .exe file and extract those files into a folder on the desktop. When the installer cannot find those install files it needs, just browse to that folder (it should have the same name as the self-extracting .exe file and will contain the Blackberry Desktop Manager .msi file as well as all the component files.)

The modification will then proceed as it should.

Of course, if this is too complicated, they can always just remove the Desktop Manager and then re-install it as you also pointed out. Of course, removing the Desktop Manager will remove the device OS software as well which will have to be re-installed.

Thanks. I appreciate your input.