[krazy8]

I've had this happen once before... my storm got the "Reload Software: 552" on reboot. Last time I installed a new app and when I tried to run the app it had an uncaught exception. After reboot it gave me the reload software error. I was able to go into application loader on desktop manager (even though it didn't recognize my phone as connected) and remove the application. But this time desktop manager has a fatal error when it gets to the "searching for software updates" part of the connection process. Tried all sorts of things. Booting in safe mode doesn't work either, since it won't boot past the error screen. Any suggestions?

[Ronindan]

Sounds that you might have to do a full wipe of your storm

Have a looks at my sig to see if it helps.

Good luck

[krazy8]

any way to back up my data? it's been just over a month since i did a backup...

[Ronindan]

If I read it correctly your storm is bricked?


Here is the info to un-bricked it.

However so save your date it is probably too late.
Sorry Bud.

BlackBerry 101: How to Reload the Operating System on a Nuked BlackBerry | CrackBerry.com

[Ronindan]

any way to back up my data? it's been just over a month since i did a backup...

At least you data is only a month behind.

[krazy8]

I tried connecting my phone to desktop manager w/ the battery out and it connected... it shows me the list of everything currently on it but they're all shown as uninstalled. If I select them to install and hit next, can i let it reinstall everything and pop the battery back in before it reboots?

[krazy8]

i guess it would still lose my phone data...

[Ronindan]

I tried connecting my phone to desktop manager w/ the battery out and it connected... it shows me the list of everything currently on it but they're all shown as uninstalled. If I select them to install and hit next, can i let it reinstall everything and pop the battery back in before it reboots?

Actually before you do anything back app your stuff now!!

[krazy8]

it doesn't show me as connected, so i can't run backup or device software switch, it just shows the list in apploader

[Ronindan]

it doesn't show me as connected, so i can't run backup or device software switch, it just shows the list in apploader

Oh well. Load your os and apps and let it do its magic and after that pop the battery back in.

It does take some time, so be ready for it. Longer that when you are loading a new os.

Just a heads up.

[krazy8]

any idea how to use the jl_cmder in command line mode? I see an option in the javaloaderusage.txt file to wipe applications only:
Usage: JavaLoader [-u] [-p<port>|<pin>] [-b<baud>] [-d0|-d1] [-w<password>] [-q] <command>

-u Connect to USB handheld (default is serial)
-p<port> Specifies the serial port (serial handhelds only)
-p<pin> Specifies the handheld PIN (USB handhelds only)
-b<baud> Specifies the baud rate (serial handhelds only)
-d0 Disables VM debug mode
-d1 Enables VM debug mode
-w<password> Connects using the specified password
-q Quiet mode

<command> is of

dir [-d] [-s]
Lists modules on the handheld
-d Display dependency information
-s Display siblings

deviceinfo
Provides information on the handheld

load <.cod file> ...
Loads modules onto the handheld

load <.jad file>
Load modules described by JAD onto the handheld

load @<manifest> ...
Loads all modules named in <manifest> onto the handheld

save { <module> ... | -g <group> }
Retrieves modules from the handheld
-g Retrieves all modules in a specified group

info [-d] [-v] <.cod file> ...
Provides information on the specified modules
-d Display dependency information
-v Display verbose module information

wipe [-a|-f] Wipes the handheld
-a Wipe applications only
-f Wipe filesystem only

erase [-f] { <module> ... | -g <group> }
Erases modules on the handheld
-f Force erase of in-use modules
-g Erases all modules in a specified group

debugmode
Enables VM debug mode

eventlog
Retrives the handheld event log

cleareventlog
Clears the handheld event log

settime
Sets the time on the handheld to the current time

radio on|off
Turns the handheld's radio on or off

enum
Enumerates all USB handhelds

siblinginfo <.cod file> ...
Provides sibling information on the specified modules

screenshot <.bmp file>
Retreives the current screen contents and saves it as a BMP file

logstacktraces
Dumps the stack traces for all threads to the event log

resettofactory
Reset IT policy to factory settings

recoverflash <size in bytes>
Attempts to recover the specified amount of flash

otasl load <type> file
load an OTASL patch file
type is os, dspos, osext, installer, cod or patchlist

otasl purge <type>
purge OTASL patch files
type is os, dspos, osext, installer, cod or patchlist

otasl state <state>
set the OTASL state and reset
state is APPLY_PATCH, BACKUP_DATA, etc

[Ronindan]

any idea how to use the jl_cmder in command line mode? I see an option in the javaloaderusage.txt file to wipe applications only:
Usage: JavaLoader [-u] [-p<port>|<pin>] [-b<baud>] [-d0|-d1] [-w<password>] [-q] <command>

-u Connect to USB handheld (default is serial)
-p<port> Specifies the serial port (serial handhelds only)
-p<pin> Specifies the handheld PIN (USB handhelds only)
-b<baud> Specifies the baud rate (serial handhelds only)
-d0 Disables VM debug mode
-d1 Enables VM debug mode
-w<password> Connects using the specified password
-q Quiet mode

<command> is of

dir [-d] [-s]
Lists modules on the handheld
-d Display dependency information
-s Display siblings

deviceinfo
Provides information on the handheld

load <.cod file> ...
Loads modules onto the handheld

load <.jad file>
Load modules described by JAD onto the handheld

load @<manifest> ...
Loads all modules named in <manifest> onto the handheld

save { <module> ... | -g <group> }
Retrieves modules from the handheld
-g Retrieves all modules in a specified group

info [-d] [-v] <.cod file> ...
Provides information on the specified modules
-d Display dependency information
-v Display verbose module information

wipe [-a|-f] Wipes the handheld
-a Wipe applications only
-f Wipe filesystem only

erase [-f] { <module> ... | -g <group> }
Erases modules on the handheld
-f Force erase of in-use modules
-g Erases all modules in a specified group

debugmode
Enables VM debug mode

eventlog
Retrives the handheld event log

cleareventlog
Clears the handheld event log

settime
Sets the time on the handheld to the current time

radio on|off
Turns the handheld's radio on or off

enum
Enumerates all USB handhelds

siblinginfo <.cod file> ...
Provides sibling information on the specified modules

screenshot <.bmp file>
Retreives the current screen contents and saves it as a BMP file

logstacktraces
Dumps the stack traces for all threads to the event log

resettofactory
Reset IT policy to factory settings

recoverflash <size in bytes>
Attempts to recover the specified amount of flash

otasl load <type> file
load an OTASL patch file
type is os, dspos, osext, installer, cod or patchlist

otasl purge <type>
purge OTASL patch files
type is os, dspos, osext, installer, cod or patchlist

otasl state <state>
set the OTASL state and reset
state is APPLY_PATCH, BACKUP_DATA, etc

Sorry man I never used that command line. I just wipe the whole phone since there might be some issues with the actual os.