2 Comments »

A lot has happened since I posted last:

- Last Saturday, when we (Jared, Jadon, Dad, and I) were playing soccer, Jared and Dad ran into each other and we thought he might have fractured/broken his collar (clavicle) bone, but thankfully he only badly bruised it…

Yesterday was Dad’s birthday and his Blackberry decided to surprise him with an error message “JVM Error 517″, requiring a reset, which upon reboot, would have the same error message (continuous cycle). He called Cingular they said it was either the phone or the SIM card, then he stopped by the store and the SIM card was fine, so they said it was his phone (Like his phone had “gone bad” or something)… He had emailed me earlier to tell me that his phone was inoperable, and gave me the error message, so I did a little looking online (but didn’t have much time at the time :) ). When he got home he said something to the effect of “Jordan I need your phone for now because we still have some stuff going on at work and I need to be reachable”, so I took my SIM card out of my phone and he took his SIM card out of his Blackberry, and we swapped phones. Realizing that I probably wouldn’t get my phone back until he got a working phone, I decided that it was a good time to see if I could get his Blackberry working. I proceeded to google the error message, and all I seemed to be able to find was the error code and its meaning, not how to resolve it (JVM 517: Filesystem corrupt… An inconsistency was detected in the JVM persistent object store.) I wandered over to Cingular.com and went to their support area, and did a search for the error number, and it listed a bunch of other error messages and then at the bottom of the page it said “…most of these errors can be fixed by doing one of the following:…” and they listed a few steps and then alternate steps if the device wasn’t being recognized by the desktop software. I tried the first, and ended up having to follow the alternate instructions and unplug it from the computer and then plug it back in right after I did a hard-reset on it, while getting through the various dialog boxes before the Blackberry finished rebooting. I just click “next, next, next, next” and it said “connecting….” then it said “reading device configuration” and then I knew it was going to work… So I left it alone to do its thing and went to go play Pente with the family. <an hour passes>
Dad walks up to his laptop
“Jordan, It works!”
Jordan:
“Great!”
Dad:
“Thank you for getting it working!”
Jordan:
“You are welcome!”

Then Dad jokingly says
I wonder if they put a little something in the software that after a certain amount of time, it displays an error message and locks up, so that people think they have to get a new phone”…
We walk back into the great room and he tells me (and the rest of the family that is listening) about how Cingular told him that it was either the SIM or the Phone that was bad, neither ended up being “bad”.
BTW – Dad has owned his Blackberry a little over two years…

I had one more thing I was going to write about, but I can’t remember what it was….

-Jordan

2 Responses to “Recent Happenings…”
 

Hi,

So I googled this error (JVM error 517) and found your blog. I am desperately trying to fix my blackberry with this exact problem. Do you remember what you did? I can’t find information anywhere (at AT&T, Google, etc) and they won’t help because it’s just over a year old… any information you could give would be very much appreciated!

Thanks!

Leslie wrote on May 31st, 2009 at 11:04 pm

 

AT&T support page listing JVM error codes

At the bottom of the above page, it says:

The majority of JVM errors can be resolved by performing the following
Perform a hard reset on the device.
Upgrade the RIM BlackBerry device to the latest Handheld Software.
If the error persists, attempt to run Application Loader when the device does not connect.
If further assistance is needed, please contact Customer Care.

I ran the application loader and followed the instructions on that page. Excerpts below.

IMPORTANT: Timing is critical in this process. Read through the following steps before beginning this procedure.

Procedure
Disconnect the device from the computer.
Access BlackBerry Desktop Manager, then select Application Loader.
Click Next.

Perform a hard reset on the device.
IMPORTANT: Reconnect the device before it completes the reset, then perform the following:
NOTE: If these steps are not completed before the device finishes resetting, the Application Loader will not detect the device.
If using a USB connection, wait until the drop-down list on the Communication Port Selection window changes to USB-PIN, then click Next…

See the rest.

As I said in my blog post, I had to quickly hit the next button a few times. Timing is important.

Let me know how it turns out!

Jordan wrote on June 1st, 2009 at 12:03 pm

Leave a Reply