BlackBerry® Torch™

[rlaspinall]

I downloaded the Blackberry World update to my Torch 9800 and now have the error "Uncaught exception: java.lang.NullPointerException"

Can anyone advise on how to correct this?

[sdgardne]

Hi and Welcome to the Community!

I recommend that you attempt to boot into Safe Mode:

• KB17877 How to start a BlackBerry smartphone in Safe Mode

It may take you multiple attempts to get the ESC key sequence (press/release/hold) correct, so be patient. When successfully into Safe Mode, think carefully...what happened just before this behavior started? A new app? An update? A Theme? Something else? Think carefully as the smallest change could be causal...and attempt to undo whatever that was.

Good luck and let us know!

[rlaspinall]

I just ran it through safe mode and checked the settings of all the apps and it still had the error when I rebooted it. 

To provide more detail on when it happened - a phone call came in while it was updateing BB World and the system froze, requiring a reboot to start again. 

Hopeuflly that helps diagnose the problem.

[sdgardne]

Wait...so the problem did not present while in Safe Mode, but did again after returning to normal mode? If so, then it's one of your 3rd party apps that is the culprit.

From your description, it's likely AppWorld itself (odd, but that's what it looks like). To determine, try this process:

1) Remove AppWorld from your BB

• KB10040 How to view or remove installed applications on a BlackBerry smartphone
• You may have to use Safe Mode to remove it
• If it requests that you reboot the BB, do so

2) Do a Batt-Pull reboot (power on, remove battery, wait, insert battery, wait), even if redundant to the one you did in step 1.

3) Install (on your BB) a fresh copy of AppWorld

• http://blackberry.com/appworld/download
• Again, if it requests to reboot, do so.

4) Do another Batt-Pull reboot

5) See if it now works.

Cheers!

[rlaspinall]

It was a great idea, but the problem continues. I wonder about using the desktop manager and deleting and reinstalling all of the third party apps. Do you think that is worth the effort. 

[sdgardne]

Wait...I'm not clear on your situation. The behavior presents when AW is installed right? But does it also present when AW is not installed I just can't quite tell... If, for example, the behavior only happens when AW is installed, then I'd see no utility in what you suggest...

[rlaspinall]

The error came up when AW was uninstalled as well.

[sdgardne]

OK...thanks...I did not understand that from your prior posts. Given that, something else is the cause...which means your idea does have merit. You can try removing, one by one, each add-on app until the behavior ceases.

But, this is not guaranteed (well, nothing is really!!)...if, for instance, the core OS has been corrupted somehow, then removing apps won't cure it. Rather, reloading the OS cleanly, and perhaps even "bare bone" followed by slowly adding things, is the only way to cure that (if it is indeed curable).

Good luck and let us know!

[rlaspinall]

I uninstalled AW with Desktop Manager and reinstalled. It is now working.
Thanks for your help.