01-28-2013 01:39 PM
01-28-2013 08:16 PM
Hi and Welcome to the Community!
Here is a KB that discusses that error:
Hopefully it contains something useful! There also are multiple existing threads on this site that discuss that exact error...your review of those might prove useful, and a search of this site, using the error message, error code, or symptom, should reveal all applicable existing threads to you.
At the top of each device forum, there should be some "sticky" threads that discuss the OS levels available for many models. If they include your model, then please use those as reference as you proceed. Otherwise, you will have to dig through the official download portal for OS packages for your model:
From a PC, you can install any compatible (e.g., for your exact BB Model Number) OS package to a BB via this procedure:
Note that while written for "reload" and the Storm, it can be used to upgrade, downgrade, or reload any BB device model -- it all depends on the OS package you download and install to your PC. If that OS package is from a carrier other than the carrier for which your BB was originally manufactured, then delete, on your PC, all copies of VENDOR.XML...there will be at least one, and perhaps 2, and they will be located in or similarly to (it changes based on your Windows version) these folders:
Be sure that you remove, from your PC, any other BB device OS packages as having more than one installed to the PC can cause conflicts with this procedure.
You may also want to investigate the use of BBSAK (bbsak.org) to perform the wipe it is capable of.
You may also want to try this procedure to perhaps narrow down the precise causal item:
When the behavior presents, you know the culprit...the last thing you loaded.
If the behavior does not re-present, then you know that either step 1 or 2 cured it.
If the behavior presents no matter what, then you likely have a hardware level issue for which no amount of OS or software can cure.
Good luck and let us know!