I get this error when running it

HLVDD - Hardlock Virtual Device

cannont find ///FAST Hardlock Driver

any ideas my 7130 is stuck on data abort after loading a theme

That is a new error to me. Not sure what you need to do. I searched the BlackBerry Knowledgebase but didn't find anything there either.

This is a superb utility! I used it a lot with the 8700g and earlier Blackberries, but am unfortunately unable to get JL_Commander v1.8.3 to take a screengrab from my Curve OS v4.2.2.67 (Platform 2.4.0.29).

When I type in a filename for the screengrab and press enter, an Windows Explorer error message pops up saying "The path 'c:\docume~1\username\locals~1\temp\test.bmp' does not exist or is not a directory."

I've checked that my Curve is running the latest OS & it is. There currently isn't a later OS update available from O2 at the moment

Do you have any ideas why JLCommander v1.8.3 does not work with the Curve OS v4.2.2.67 (Platform 2.4.0.29)?

BBscreenshooter & bbscreenstream don't work either with the Curve OS v4.2.2.67 (Platform 2.4.0.29)

Thanks!

There is a known issue with the OS.
http://www.blackberryforums.com/gene...tml#post538226

Well done, thanks a lot.

Well done, thanks a lot.

Hello-First let me start by thanking all of you for contributing to this site. The content is very useful!

Second-I have a BB 8800 that started doing the reset loop a couple of days ago. Today I connected it to the desktop Manager and it would not detect it. I selected the apploader and it detected the device and identified the PIN. I followed the wizard up until the point where it asked for the device password. I wasn't sure if I would be able to recover the data so I purposely entered the incorrect password 10 times. The apploader advised me that it was wiping the device. When it finished, the LED would blink twice every so many seconds. I disconnected it from my PC, removed the battery, re-instered it and tested it. Now the device does not turn on, the LED remains red for almost a minute and then it starts to blink twice every so many seconds. I tried walking through the solutions provided using the Java app, and the App Loader via cmd but I can't get the device to be detected no matter what I do. I don't think it's a harsware failure and feel like I"m very close to bringing it back to life. Am I missing something? I appreciate any assistance and/or guidance. Thank you!

Hi all. Well this is a very useful forum, however I still cannot solve my problem hope you can help! I have a new T-Mobile Pearl, latest desktop manager, trying to install 4.2.1.96. The first install failed during the "trying to reconnect to JVM" step. So now I'm out here trying the JL_Cmder. Here's where I'm up to:

1. Desktop Manager not running
2. Blackberry restarted without the battery
3. Deleted vendor.xml
4. Connected via USB
5. Device Manager running, and it sees the BB as USB:PIN-FFFFFFFF
6. JL_Cmder never seems to find the BB, even with the -u command and a simple "dir" to see if its working
7. Application Loader Wizard starts, finds the BB at USB:PIN-FFFFFFFF
8. Application Loader presents the panel of software, I choose just the defaults for now
9. Updating Your Device panel appears
10. under "Load JVM and System Software", "Erasing Applications" appears to complete
11. under "Load JVM and System Software", "Loading System Software" appears to complete (ie. green bar crawls across to the end, then repeats rapidly)
12. under "Load JVM and System Software", "Waiting For Device initialization" appears to complete. During this process I hear a Windows USB device disconnected noise, followed by a connection noise, then a pause, then two connection noises in rapid succession
13. under "Load JVM and System Software", "Reconnecting to JVM" progress bar crawls across the screen, and then ends with an error panel
14. The error panel is titled "Unable to Complete the Loading Operation" and has this message: "Unable to reconnect to the device during a multi-stage load operation."

Woe is me ... please help ... thanks!

Tony

Must have tool if you have a blackberry. Awesome..

Every time I have seen the PIN listed as FFFFFFFF the device has been replaced. I have never recovered a device from this situation.

Unfortunatly, I agree with d_fisher. Pin=FFFFFFFF means you need a new device.

I cant seem to run the application on my laptop. I have copied the files on a folder on my desktop named bberry.
Help please

I've been trying to use your brilliant application, jl_cmdr v1.8.3 on a WinXP pc. I was using option 4, but kept getting this error:



Ps: I just saw another post with the same issue, and it appears this is a common thing, and there is no resolution...

Hmm...I've never tried using JL_Cmder for anything but wiping the device. It's worth it's weight, just for that.

Need more information please. Are you getting an error?

first off thanks mate , this is great utility

i am using a 6710 very old device, serial device
using desktop manager 4.2 SP1
device is detected and accesible using desktop manager
JL_Cmder cannot connect to port, tried using javaloader -p com1 but it just spit out help for javaloader and does nothing, pls help

Make sure Desktop Manager is NOT running when using JL_Cmder.

yes , desktop manager is not running

I believe it did that because you didn't tell JavaLoader what to do. All you did was tell it to use COM1. Test it out with something simple like I am not even sure if you need to specify -pCOM1 or not. The default is the serial port. Never had a serial device to test against.

still port cannot be connected, device is at OS ver 3.7, could this be a problem?

nvm

Not sure I can help out anymore. I don't have a serial BlackBerry so I can't test. Anything else would be merely a guess. Sorry.

this is a great app. Now let me get this users device so I can ask yall a question.

I can't find a website to download the JI Cmder. Can you help me find a site?
I have been on google for 2 hours trying to find a site to download it.

Check my signature....

Also, it's in the first post of this thread.

I've had my Pearl since January and I've downloaded several cool tools! By far, this may be one of the coolest! I had no idea it would be so simple!!! Love It!

I'm new to this (BB 8700g), so don't scream, BUT how long does it take for the 'wipe' command to work. Originally I had a JUM Error 523. So I downloaded the nifty JL_CMDER and then told it to wipe my handheld. Now the hourglass is just turning like a whirling dirvish? How long is this suppose to take to wipe the handheld? The red light is flashing like crazy too. Will this work like this (yes, I plugged it up to my laptop and installed the JL_CMDER). And I simply used the wipe command...am I on the right track?

Welcome to the forums,
It can take anywhere from 2 minutes to 2 or 3 hours. If content protection was on then it will take a couple of hours. If content protection was off then it will take a couple minutes.

Fantastic bit of work, thanks buddy.

RIM - why create a device that requires another device and another OS to wipe it? The reset button behind the battery door doesn't wipe the device, so why not build in a button on the system board itself to wipe the device and hide it under the case so average users can't accidentally wipe their devices but technicians can? Why do I need to connect my Blackberry to a Windows based PC to wipe it out? Where's the "easy button" on the device itself?

Nevertheless, AT&T and RIM couldn't help me wipe my device. My 8700c is stuck in a continuous power cycle and I can't get it to wipe... all because I lost my network connection while downloading InfoSpace to my device. I followed these 2 instructions for JL_Cmder precisely on 2 different computers with no success (the 2nd computer had USB 2.0 ports): How do I wipe the BlackBerry using Jl Cmder? - BlackBerryFAQ & What to do next if Jl Cmder will not connect and wipe - BlackBerryFAQ. When JL_Cmder actually wipes the device, what indication will I get? Will the 507 code on the device be my first indication that it wiped successfully or will JL_Cmder give me an indication that it wiped my device successfully?

Sorry in advance for my tone. I'm just frustrated with RIM - not JL_Cmder nor its creator nor the fine folks helping here on blackberryforums.com. Because of this forum, I have enjoyed my 3+ years of Blackberry use much more than I ever would have without it.

The 507 screen is the indication of a "wiped" device.

The actual wipe program is called javaloader. JL_Cmder is just a small app built around the javaloader program from RIM.

J have problem with JL_Cmder.
When J start it everything is ok and when J press to wipe device or anything else hi open blank notepad and on progam say conneting to device... can open port.

Please help me...

I can't get it to run with Vista... Any clues to get it running?

I'm glad I found these forums. My blackberry locked up when trying to pair with a bluetooth CAC reader. It wouldn't respond to anything. This utility was able to wipe the device and allow me to start from scratch. Thanks!

Whenever I click on JL-CMder, it says: wanna install
I click yes, and then nothing......
BB 8800 with 4.2 Software on Win XP.

Help???????

Wirelessly posted (8100: BlackBerry8100/4.2.1 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/100)

Are you using Vista? If so, you need to right click and select ran as admin.

How do you install this thing on vista?

Hey guys I have heard the same problem.
This helped me I hope it helps u too.

BlackBerry Search Results

sorry, downloaded this software, but i can't install it on my PC!!!

Great app

My 7130 has "device error 348" right out of the box - tried jlc & pressed 5 for wipe - it tried to connect, nothing happens, goes back to the main screen w/ options. javaloader has the same error "Connecting To Device...Error: unable to open port"

Anyone know anything about 348? When I try to reinstall the OS, it starts correctly and goes half way then gives this "Unable to reconnect to the device during a multi-stage load operation." error on the PC.

Update - tried a working bb and it's getting "unable to open port" on jlc also. They're connected to my desktop directly to the front usbs - is that the problem?