07-22-2012 01:30 PM
Solved! Go to Solution.
07-22-2012 01:47 PM
Hi and Welcome to the Community!
Wow...that is a sad statement on the capabilities of the service center! If you want to try and remedy this yourself, then you would want to do an OS reload...
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.
If you are on MAC, you are limited to only your carriers sanctioned OS packages...but can still use any levels that they currently sanction. See this procedure:
Good luck and let us know!
07-22-2012 07:36 PM