09-15-14 07:02 AM
656 ... 2021222324 ...
tools
  1. nileee's Avatar
    i done all this **** got no white screen
    03-13-11 01:21 PM
  2. tracy-1988's Avatar
    after mine connects it goes back to the mail screen???
    03-15-11 03:10 AM
  3. tracy-1988's Avatar
    after mine connects it goes back to the main screen? did i do it right?
    03-15-11 03:11 AM
  4. BigBadWulf's Avatar
    The screen would be white, with a tiny 507 error in the center. Do you have Desktop Manager installed and working?
    03-15-11 05:26 AM
  5. michaeljf79's Avatar
    it keeps telling me that loader.exe/nojvm is not recognisable. any suggestions?
    03-20-11 02:10 AM
  6. yogi's Avatar
    Ok, I've seen alot of people lately using JL_Cmder to wipe the device, but some are having problems. So, heres a How-To on how to use JL_Cmder. I hope this helps a few people out.

    1) DownloadJL_Cmder from the attached file below, unzip & install to the computer.

    2) Now, go ahead and sync all of your info or back it up. If you DO NOT, you will lose it ALL, obviously because we are wiping the device.

    3) If you do not have the latest version of the Desktop Manager, download it fromHERE
    Also, make sure, that you have the OS you are wanting to install to the device, installed to your computer as well.

    4)Make sure the Vendor XML file is deleted if you are going to install a OS that is not from your carrier. The vendor XML file can be located by going toC:\ProgramFiles\CommonFiles\ResearchInMotion\Applo ader

    5) Make sure the DM is closed and plug in BB to computer via USB

    6) Go to theJL_Cmderon your computer and double click it to start. Now, this may take a few tries to connect, so keep trying until it does.

    7) On the first screen, Press any key to continue.


    8) Now, if your device uses a password, enter it now. If not, press "N"

    9) Press 4 to initiate the WIPE

    10) Press "Y" to continue

    11) Now type "blackberry" to continue

    12) Now you will see a white screen with a'507' Error Don't worry, this is what you want! You are now ready to install the OS.

    13) Open the DM

    14) Select Apploader and step your way to the finish. After the OS is installed, it will take anywhere from 15 to 30 minutes to reboot the device. DO NOT UNPLUG THE DEVICE UNTIL THE APPLOADER SCREEN SAYS "THE LOADING OPERATION WAS SUCCESSFUL!!

    15) Almost done. Now, with the DM still open go to the Main page and Select "Backup & Restore" and restore from the backup that was made before wiping.

    That's it! You have now wiped your device withJL_Cmder
    Make sure you follow the instructions, and you shouldn't have a problem. I hope this helps.

    EDIT: How to use JL_Cmder with Vistax64:

    Download and install this version HERE
    1. Download JL_Cmder from HERE NON-INSTALLER
    2. Extract contents
    3. Download MY version
    4. Replace CHOICE.COM with the my version of the file.
    5. Rename my version extension to CHOICE.COM (thanks minigts for the catch!)
    6. Right click JL_Cmder.cmd and choose properties
    7. Click compatibility tab and check Run this program in compatibility mode for: Windows XP (Service Pack 2)
    8. Click OK
    9. Run JL_Cmder.cmd
    10. Continue as stated in the directions above.




    This tutorial was made by Crucial_Xtreme. Please do not copy and paste this outside this forum without my consent. Thank you. And Thanks to D_Fisher for making this Wonderful Application.

    Below is a list of App Errors:

    * 101 Internal JVM error.
    * 102 Invalid code in file system. The .cod files in the handheld have been checked for modification and it has been determined that there is a problem with one or more .cod files.
    * 103 The starting address for the boot .cod file cannot be found. This might mean that a boot .cod file has not been installed on the handheld, or that its format is invalid or corrupt.
    * 104 An uncaught Java exception was thrown in the Java code and diagnosed by the JVM. Execution can be continued or the handheld can be attached to a debugger on a desktop through a serial or USB cable. The event log should contain the traceback of the thrown exception.
    * 105 An OS file system API returned an error status for a certain operation. This can indicate a corrupt file system or an error in the JVM.
    * 106 An error has been detected in the graphics system of the handheld.
    * 107 Internal JVM error.
    * 108 Internal JVM error.
    * 109 Internal OS error.
    * 110 Non-idle event downtime error. A problem has been detected in the accumulation of JVM down time that represents how long the JVM has been idle. This indicates an error in either the OS code or the JVM code.
    * 200 Application manager threw an uncaught exception. The application manager event thread threw an uncaught exception and so cannot continue running.
    * 201 Initialization of the cryptographic system failed and the handheld cannot continue to operate.
    * 202 An attack on the key store has been detected, and the handheld cannot continue to operate.
    * 203 The application manager console process, usually the Home screen ribbon, has failed, like due to an uncaught exception.
    * 501 Internal error.
    * 502 All processes exited. The last Java process has terminated, and there is nothing left to execute.
    * 503 Internal error.
    * 504 Internal error.
    * 505 Internal error.
    * 506 An uncaught Java exception was thrown in the initial VM Java thread thus killing the only live thread in the system. The event log contains the traceback for the exception.
    * 507 A dependency on a .cod file could not be satisfied due to a missing .cod file. Load the missing .cod file onto the handheld.
    * 508 Invalid object. A problem has been detected with a debugger command to the VM.
    * 516 Error occurred during garbage collection, which might indicate a corrupted file system.
    * 510 All threads are waiting on objects, which results in a deadlock. The system cannot recover from this state since no thread can release a lock.
    * 511 A problem has occurred during debugging.
    * 515 The reachable objects form a group that cannot be represented properly by the VM because there are too many objects or the total size of the objects is too large.
    * 516 When committing a persistent object, the VM found that the persistent store id counter has reached its limit. The object was not committed.
    * 517 An inconsistency has been detected in the VM persistent object store.
    * 518 Internal error.
    * 519 Internal error.
    * 520 Internal error.
    * 521 Indicates that Object.wait() has been executed by a thread that holds a lock on another object; occurs only in simulator if the JvmDebugWaits application switch.
    * 522 A thread has acquired two locks on objects in an order that doesnít match the order that previous locks for the two types were acquired, which indicates a future potential deadlock situation; reported only in the simulator when the JvmDebugLocks application switch is set.
    * 523 A critical Java process has died and the device cannot continue to operate normally.
    * 524 An object has been marked as recovered by the Low Memory Manager but it was not freed during a garbage collection. This is only checked in the simulator under the control of the JvmDebugLMM application switch.
    * 525 Bad persistent object. An auto-commit operation during a garbage collection has detected a non-persistent object reachable from the persistent store root. The type of the object has been output into the event log.
    * 526 The class definition for java.lang.Object cannot be found.
    * 527 The class definition for java.lang.String cannot be found.
    * 528 The file system is corrupted. Data on the handheld is unrecoverable.
    * 529 The file system is corrupted. An attempt is going to be made to recover data, but some data might be lost.
    * 530 Internal JVM error.
    * 531 Flash memory has been exhausted.
    * 532 A JVM assertion has been violated. This error can occur only in the simulator, not on an actual handheld.

    Wow. Nice woek. Awesome. Thanks for that informations.
    04-17-11 11:36 PM
  7. mohi2011's Avatar
    You guys are absolutely brilliant! Thank you so much! Saved my blackberry!
    04-30-11 11:31 PM
  8. dboluarte's Avatar
    I need help!!! following the steps but my problem start in the step #11.
    I type "blackberry and then press Enter and the new screen say:

    RIM WIRELESS HANDHELD JAVA LOADER
    COPYRIGHT 2001-2007 RESEARCH IN MOTION LIMITED
    CONNECTING TO DEVICE...._


    Then change the screen to the steP #9.
    I did it again and no results . What im doing wrong??

    The cellphone just has the red light in the top on and the screen has a battery in the middle. I dont think that the battery is being charged.

    Thanks in advance!!!
    05-07-11 06:41 PM
  9. BigBadWulf's Avatar
    I need help!!! following the steps but my problem start in the step #11.
    I type "blackberry and then press Enter and the new screen say:

    RIM WIRELESS HANDHELD JAVA LOADER
    COPYRIGHT 2001-2007 RESEARCH IN MOTION LIMITED
    CONNECTING TO DEVICE...._


    Then change the screen to the steP #9.
    I did it again and no results . What im doing wrong??

    The cellphone just has the red light in the top on and the screen has a battery in the middle. I dont think that the battery is being charged.

    Thanks in advance!!!
    [color=#000066][Nothing is going to happen, till that battery is charged up. Right now there's nothing booted to wipe, and baring certain reasons, there's probably no need to either. Is it charging at all, via wall charger or USB?/color]
    05-07-11 07:15 PM
  10. dboluarte's Avatar
    i dont think is charging because it shows a battery with a dash in the midle. There is light in all the screen but just the battery with the dash. Do i always need to have a battery charged to do these steps?

    Thanks
    05-07-11 10:24 PM
  11. BigBadWulf's Avatar
    Yes, enough juice for the phone to power up is required. Try a different battery.
    05-07-11 10:29 PM
  12. dboluarte's Avatar
    it's good to know that. I already bought an adapter to charge the battery maybe i have to wait a week to get it. I'll post news after get it charged. Thanks again
    05-08-11 10:22 AM
  13. dboluarte's Avatar
    Nothing, battery is charged and happen the same thing. What else can i try?
    05-13-11 07:27 PM
  14. BigBadWulf's Avatar
    Nothing, battery is charged and happen the same thing. What else can i try?
    If you're sure the battery is good, and fully charged, then my best suggestion at this point is to remover the battery, SIM card and SD. Leave it like that at least 24 hours, then reinsert the battery only and see what it does.

    What happened to it prior to this state, what model, and how old is it?
    05-13-11 09:02 PM
  15. dboluarte's Avatar
    yes, battery was charged. It was chargind about 4 hours.
    I dont know its history because i bought this phone from another owner. It has cracked screen. When i insert the battery, there is not red light in the top and black screen. When i connect it to the computer, the red light in the top turns on , after 10 seconds the screen turns on and there is a battery in the middle with a red line crossing the battery. It always stay turn on if it is connected to my PC.
    05-15-11 09:33 AM
  16. BigBadWulf's Avatar
    yes, battery was charged. It was chargind about 4 hours.
    I dont know its history because i bought this phone from another owner. It has cracked screen. When i insert the battery, there is not red light in the top and black screen. When i connect it to the computer, the red light in the top turns on , after 10 seconds the screen turns on and there is a battery in the middle with a red line crossing the battery. It always stay turn on if it is connected to my PC.
    If it's still showing the dead battery sign, it's probably a bad battery, but could be a bigger problem. What condition did the seller say it was in, and did you check it before purchase?
    05-15-11 10:48 AM
  17. dboluarte's Avatar
    It's a new battery, i already bought for it.
    He just told me, it fell in the ground and broke the screen. he tried to turn it on but nothing. No more dataills about it. I always knew the working condition and I thought to fix the problem wouldn't be so hard.
    05-16-11 06:09 PM
  18. dj ned's Avatar
    Hi, thanks for your guide, it was a big help, I just upgraded my phone software and am currently restoring my data.. hopefully it will all work well, thanks!
    05-20-11 08:33 AM
  19. evelcaterpillar's Avatar
    I wish i had permission to post a totally new thread but cant i guess bc i am new....i just used this thread and its instructions to reset my 9670 to factory default in an attempt to remove an IT policy that was put on by a previous owner ( phone was bought on a site similar to ebay)....i tried multiple approaches to no avail...crackutil conflicted with vista...i dont have access to a bes and multiple other issues arose stopping me from removing the IT policy....this did work, i am running OS6 on my 9670 and the only thing i didnt see mentioned here is that every other place i looked said make sure desktop manager is not running, if desktop manager isnt running your device from what i can tell isnt connected so i ran desktop manager followed the instructions for resettofactory and bang phone reset and IT policy gone!
    05-20-11 08:57 AM
  20. adnan.jsr's Avatar
    Oh man i wiped my bb with it but was not able to install vodafone UK OS on verizon phone???? help!!!!
    05-26-11 07:34 AM
  21. BigBadWulf's Avatar
    Oh man i wiped my bb with it but was not able to install vodafone UK OS on verizon phone???? help!!!!
    It's a different carriers OS. You need to go to Program Files->Common Files->Research in Motion->AppLoader and delete vendor.xml, then click loader.exe to install.
    05-26-11 12:57 PM
  22. hausinformasi's Avatar
    Guys I need your help

    I tried to wipe my 8310 using the JL_Cmder provided here in page one
    But after I download the program & extract it I can't run the program (when I click the icon the program just wont start)

    what happen here? I need your advice on these

    Thanks for your help mastah
    05-30-11 10:45 PM
  23. BigBadWulf's Avatar
    Guys I need your help

    I tried to wipe my 8310 using the JL_Cmder provided here in page one
    But after I download the program & extract it I can't run the program (when I click the icon the program just wont start)

    what happen here? I need your advice on these

    Thanks for your help mastah
    What OS is your PC running, and did you follow the instructions for it on the first post?
    05-31-11 11:53 AM
  24. nikon7734's Avatar
    Does this work for a blackberry torch. i think it is bricked -- well the tech said the word. my phone turned off after an update and will not come back on. it keeps giving me a picture of a battery with a red x through it. does that mean its bricked. it has a new battery and everything
    06-01-11 10:18 AM
  25. hausinformasi's Avatar
    Guys I need your help

    I tried to wipe my 8310 using the JL_Cmder provided here in page one
    But after I download the program & extract it I can't run the program (when I click the icon the program just wont start)

    what happen here? I need your advice on these

    Thanks for your help mastah
    What OS is your PC running, and did you follow the instructions for it on the first post?
    I run on Windows 7
    yes i follow the instruction on the 1st post

    HELP
    06-02-11 07:16 PM
656 ... 2021222324 ...
LINK TO POST COPIED TO CLIPBOARD