My blackberry is completely useless right now. The hourglass will not go away, locking my keypad. Eventually it shows "App Error 523." I have no way to wipe my blackberry clean because I can't get to the menu to do an handheld wipe and I have a mac computer so "JL_CmDr " is unable to be installed onto my computer. DM doesnt work either because it can't connect to my computer because the hourglass wont go away. Can someone please help me because my blackberry is 5 minutes away from being thrown against the wall.

Welcome to the forums.

What app have you installed? That usually indicates an issue with an app.

Your best bet would be to use DM and go into app loader to remove the application you installed.

If that isn't possible, your only other option would be to reinstall the OS. Any way you could get to a PC?

Try pulling the battery and see if it will come back.

JVM can mean you have an incompatible theme. What were you doing right before you got the error?

You may end up finding a friend with a Windows PC and reloading your OS from that machine. Or creating a Windows instance on your MAC using either Bootcamp, Parallels or VMWare.

I've pulled the battery at least a hundred times.

Here's a post I put on CrackBerry.com regarding this error (below). In your situation I think it would be best to find a Windows XP/Vista/7 system and use the JL_Cmdr utility to try and delete your Alarms in your phone. In my case deleting the Alarms worked. I've been in your situation with having to reload the OS. I've reloaded my entire OS after a JL_Cmdr wipe at least 8 times. Each time the problems kept occurring after heavy use of the Alarm feature on my Bold. Hopefully my ramblings below might help a bit. Good luck.

--------------------------------------------------------

I don't know if this will help your situation, but I have received this error the entire time I've had my Bold (9000).

You don't happen to add lots of Alarms to your Calendar do you? Well, I do. I need appointment reminders that are persistent and extremely annoying to get my attention. I use the normal reminders to just harass me about things I want to be doing, not need to be doing.

Anyhow, I noticed that after a while of using my Bold that I put in so many alarms, usually over 25 or so, into the calendar that problems start occurring. First thing that happens that is usually my warning of imminent catastrophe is that my morning alarm doesn't go off on the phone. After a reset, I would get the App Error 523 and then have to do a OS wipe (using forums' instruction to use JavaLoader to force a wipe on the phone) and I would lose everything. Now, I notice, the newer firmware doesn't crash the phone completely. I'll get the App Error 523 message now when I go to do any sort of data sync or backup. Luckily, I found a trick to wipe my calendars before the error occurs.

Startup Desktop Manager. When it goes to scan the phone for updates, hit Cancel. Go to Backup and Restore. Then click on Advanced. It will do a scan on the phone to see what databases are on it. This might trigger an App Error 523 crash. Reset your phone if this happens and wait until right after it comes up and the Desktop Manager tries to do another "Updates" scan. Cancel that scan. Now it should try and do another Database Scan again. let that occur, but as soon as it finishes, find the Alarms item (you'll see a number next to it, which is a count of alarm items) and click on it and delete it quickly.

This worked in my case, luckily. I have firmware v4.6.0.297 (Platform 4.0.0.247) provided through AT&T (my carrier). The previous version of the firmware, 4.0.0.2xx or something, would immediately come up with the App Error 523 on boot and stop me from doing this. Now at least I can recover my phone through this pain of a fix without doing a complete wipe. If you don't have this firmware and get the App Error 523 immediately on boot, you might try to use the JavaLoader utility and mess with the command line functions to delete just the Alarms data on the phone. See some other forums on how to do that in detail. I followed them myself months ago when this problem kept occuring on my original Bold before I swapped it for a refurb replacement.