I was in the midst of upgrading my BB 7730 to OS4, and the installer failed. (some general error about having a problem backing up files). Got an hourglass on the BB, then an error: JVM ERROR 523 and an option to reset. I reset, and it starts the entire process over. Sometimes, more often now than not, I click the reset option, and it takes me to another page saying JVM ERROR 523, and that has a different, larger reset button, but clicking that does nothing.

I've tried the javaloader -u wipe on it, but it cannot open the port. I've tried to use the application loader, but it cannot detect the blackberry on the USB port. Am I looking at a dead BB?

Did you remove and reinsert the battery?
Does that cause the USB to work again?

I tried using the remove/reinsert battery--no dice.

To be absolutely specific--I remove the battery, run the javaloader -u wipe, and in the time it takes to think, I put the battery back in, and it still fails.

I'm beginning to really get worried.

To add some MORE specifics: With the battery in, Windows gives me an error about how it doesnt recognize the device. I removed the battery once, and it detected a RIM device on the USB bus, but javaloader would not connect, and I couldnt reproduce that particular situation...

the fun continues. when I use the desktop manager, and look at connection settings, I select USB. For the first 5 minutes of the JVM error 523 crash, I watch as it recognizes my BB's PIN, and then, doesnt, and does again. When it recognizes the PIN, if I use the javaloader, it tries to connect on average 30 seconds loger than normal, but still fails out in the end. When I doubleclick on application manager during this period, the app manager hangs for about 20 seconds, then defaults to its welcome screen.

waiiit. Its all dependent on how I wiggle the cable connecting the PC to the BB....what?!

Ok, now that ive firmly connected the cable, the Javaloader is hanging on connect...just sitting there...

I really can't believe that it crashed during the OS update--it figures, though. When I update PalmOS stuff, Im always biting my nails, but during this one, I was laid back and optimistic. Now I have a paperweight.

HAH! Ok, connected, disconnected....

no os on it, now I have an error, 507 with some icon with a circle and slash.

any idea what to do next?

Error 507 is the one you want. (That's the one that you SHOULD be able to get USB connection on. I've always seen most people successfully recover from a 507, anyways ....)

You should now be able to "javaloader -usb wipe"

If USB is having problems, skip the hub, and directly connect. Try different USB ports. Try a different computer.

Your USB problems may be related to your original OS install problem; I wouldn't reinstall the OS on the same USB port.

Everything worked out marvelously. Installed 4, and its purring like a kitten again.

Thanks Mark. You're tops!!!