Having spent the weekend researching the reasons for my Pearl's crash I have come to the conclusion that Error 523 is generated when a Java module crashes and remains active instead of terminating. In my case it was Mobipocket Reader that was the guilty party though it seems that other apps are capable of producing the same problem.

First the good news - YOU MAY NOT HAVE TO RE-INSTALL THE OS.

Now the bad news, you need to use the command prompt and a piece of software called JavaLoader. First download jl_cmdr (posted below). Un-zip it and open the folder. Identify the file JavaLoader and copy it to the directory that comes up when you type 'command' into the 'run' utility available via the Start menu.

In the Dos-Prompt window (black screen that appeared when you typed 'command') type the following exactly as it appears below:

JavaLoader -USB DIR > DIR.TXT

Follow the screen prompts re passwords etc and, when finished, you will have a text file in the same directory as the JavaLoader app that lists all the modules on your BB.

Look through the list and the dates will identify the most likely culprit (probably the last module that was installed). Next type the following in the Dos-Prompt window:

JavaLoader -USB ERASE -F NAME-OF-MODULE-TO-BE-ERASED

If you are as fortuate as me then your little pal will spring back into life and you can reload the offending app.

Many thanks to all the other members of the forum whose posts got me working again - I hope that the summary above will provide a one-stop-shop for other suffers.

Last edited by d_fisher : 05-14-2007 at 08:12 AM.
Reason: Removed attachment. JL_Cmder is available from another thread.

I have been going through the same pain with my Pearl with every now and then getting an Error 523 "reset" .. Having pulled down the logs from the device, I can see that it appears an MMS was causing this. Reading some threads on forums etc, it appears that some cross carrier MMS's have been know to cause some problems, as such... Once connected, I ran;

C:\Program Files\JL_Cmder>javaloader -u -w erase -f net_rim_bb_mms

The device rebooted itself and is all good again, now I *could* install it again, but seeing as this particular module has done this to me a lot of times now. I will wait till there is new software and try again I expect....

Hi,
Iam using 7100v series handheld,iam gettimg the blankscreen,
I tried the following C:\Program Files\JL_Cmder>JavaLoader -USB ERASE -F 7100
but it gives error Connecting to device...Error: unable to open port

Helpful hint on this one, as I seem to be getting these more often than I would like.
If the problem is caused by something connectivity related (I get to the security screen and then it pops the app errror 523) add these steps...

I seem to get the java error 532 when I leave jivetalk on over night and the machine (set to turn off at 11pm and on at 6am). And when I check it in the morning it has that error displayed and asks me to reset the device. So I'm guessing it's jivetalk, anyone else experienced this? I'm willing to put up with it as I love <3 jive talk, im+ is so slow to boot and consumes my battery like no tomorrow!..

I have been going through the same pain with my Pearl with every now and then getting an Error 523 "reset" .. Having pulled down the logs from the device, I can see that it appears an MMS was causing this. Reading some threads on forums etc, it appears that some cross carrier MMS's have been know to cause some problems, as such... Once connected, I ran;

C:\Program Files\JL_Cmder>javaloader -u -w erase -f net_rim_bb_mms

The device rebooted itself and is all good again, now I *could* install it again, but seeing as this particular module has done this to me a lot of times now. I will wait till there is new software and try again I expect....

Hope this helps someone as well...

Thank you very much for your help!

This is the exact issue that I had today with my 8310.

I am actually quite surprised that RIM has done nothing to fix what appears to be a very serious error.

Anyways, I deleted the MMS module and my Curve restarted with no problems (after having repeated app error 523 messages since Christmas eve).

I have been going through the same pain with my Pearl with every now and then getting an Error 523 "reset" .. Having pulled down the logs from the device, I can see that it appears an MMS was causing this. Reading some threads on forums etc, it appears that some cross carrier MMS's have been know to cause some problems, as such... Once connected, I ran;

C:\Program Files\JL_Cmder>javaloader -u -w erase -f net_rim_bb_mms

The device rebooted itself and is all good again, now I *could* install it again, but seeing as this particular module has done this to me a lot of times now. I will wait till there is new software and try again I expect....

Hope this helps someone as well...

Worked like a charm for me!! I was sending MMS pix to a buddy on Verizon Wireless earlier, and about 2 hours later, I got the App Error 523. Did what you said, and works perfect!

nevermind... I was not using Javaloader, but instead JL_Cmdr. Anyway it still comes back with the "error to open port" problem.

I don't want to lose my PIM data. All I want to do one more time is sync cause I have a lot of info unsynced yet. Is there anyway to do that at all?
I have tried with and without battery as well as SIM. Nothing connects.

While at work today, my personal 8100 Pearl decided to take [another] crap on me.
I was incredibly upset b/c I hadn't backed up my data in over a month!
Once I got home, I decided to hit up the wonder WWW to search for a solution - other than "reloading the OS".
THANK YOU SO MUCH!!
I was able to delete the "net_rim_bb_mms" module and BOOM!
It booted right back up with no problem!!!!
Woot!!
It's all backed up now, but I honestly think I'm going to look into switch over to AT&T and buy the Tilt.

need help. i just bought 8320 this week. after reading some of the post i remembered i sent MMS then aftr few hours i got the error. i tried the application loader, tried looking for the javaloader but i cant find it. plus my desktop manager does not recognize my device when i plug it.

i was getting the Error 523 whenever i receive a MMS. Connected my BB to USB cable during the bootup process typed JavaLoader -USB DIR > DIR.TXT as adviced by Adam9999 and got the installed modules list.. then used

Helpful hint on this one, as I seem to be getting these more often than I would like.
If the problem is caused by something connectivity related (I get to the security screen and then it pops the app errror 523) add these steps...

Remove battery - leave cover off for now

Remove the SIM

Boot up

Disable the "radio"

Remove battery

Re-insert SIM

Replace battery

Boot up

Put battery cover back on

Wait until everything looks finished

Enable Radio

Works like a charm for me...

thanks JHoetzl. this appears to work great. I would try this before the Javaloader. This has happened a few times after installing new apps from the DM. It appears to only happen when I leave the phone connected when it reboots.

Having spent the weekend researching the reasons for my Pearl's crash I have come to the conclusion that Error 523 is generated when a Java module crashes and remains active instead of terminating. In my case it was Mobipocket Reader that was the guilty party though it seems that other apps are capable of producing the same problem.

First the good news - YOU MAY NOT HAVE TO RE-INSTALL THE OS.

Now the bad news, you need to use the command prompt and a piece of software called JavaLoader. First download jl_cmdr (posted below). Un-zip it and open the folder. Identify the file JavaLoader and copy it to the directory that comes up when you type 'command' into the 'run' utility available via the Start menu.

In the Dos-Prompt window (black screen that appeared when you typed 'command') type the following exactly as it appears below:

JavaLoader -USB DIR > DIR.TXT

Follow the screen prompts re passwords etc and, when finished, you will have a text file in the same directory as the JavaLoader app that lists all the modules on your BB.

Look through the list and the dates will identify the most likely culprit (probably the last module that was installed). Next type the following in the Dos-Prompt window:

JavaLoader -USB ERASE -F NAME-OF-MODULE-TO-BE-ERASED

If you are as fortuate as me then your little pal will spring back into life and you can reload the offending app.

Many thanks to all the other members of the forum whose posts got me working again - I hope that the summary above will provide a one-stop-shop for other suffers.