03-22-2010 03:24 PM
I hear this term from time to time...
What would happen if you set a module to autostartup and systemmodule and it went into a CPU loop right from the "getgo"?
Question - is there such thing as "safe boot" OR a way thru Desktop Manager to remove the culprit code?
I don't have this situation - but considering an app to be autostartup and I'd like to know if it did have issues like that - what is the solution?
Thanks in advance...
03-22-2010 04:39 PM - edited 03-22-2010 04:41 PM
You can use javaloader -erase to erase the offending module, if you know the module name.
Otherwise, worst case scenario, you can always use javaloader -wipe (which will wipe everything, including the OS) and then install a new OS on the phone.
In the 2 years I've been at my development company, we've never killed one of our phones so completely it couldn't be brought back with a -wipe / reinstall, so don't worry about bricking your device.
03-22-2010 06:39 PM
On most BlackBerrys nowadays you can boot in "safe mode" where no third-party applications are supposed to start on system startup. To boot in "safe mode", cold-reboot, wait until the red LED dims (this happens relatively quickly), then press and hold the ESC key until the handheld boots up. The top center part of the home screen should say "safe mode" and there will also be a popup telling that you've booted in safe mode.
03-22-2010 07:27 PM
Interesting, does this work on the Storm as well? If so I have yet to get it to work and probably did something wrong.
03-22-2010 07:43 PM - edited 03-22-2010 07:46 PM
@klyubin - That is a very useful bit of knowledge. Thanks for sharing.
@rcmaniac25 - Apologies, the kudos was intended for klyubin - enjoy it!
03-22-2010 10:42 PM
@Peter: It's OK I'll return the favor.