A partial write in the directory makes it 99.9% certain of file corruption, as fdsk is ran on boot, if it finds anything wrong, it panics. Be sure you never pull the power or turn it off, before files have been synced/disk cache written. Send the eject command, to be gentle with your Didj or start firmware update.ĭidj is by far the easiest to mess up while updating, or transferring any files for that matter.
But if you would like to run an update of the firmware or bootloader, OpenLFConnect can make it rather painless. For general purpose looking around, its far easier to use the OS's file browser. You should see a new window pop up with the contents, or it show up in your file browser, depending on the OS used. This will obtain the location the Didj is mounted on. Once Didj is plugged in and turned on, start the client and connect. If you just pull the plug, it can cause data corruption. Always make sure to safely eject the device, to allow the host OS to commit the changes. It will be needed if your Didj ever says it "needs repair."Ī word of caution to prevent "needs repair" issues.
The first thing you should do with your Didj, is back up the entire drive that gets mounted, archive it, and keep it somewhere safe. The Didj client has a few specific commands, all prefixed with didj_. Once you mount the Didj, you will be given a remote prompt, in reality you are still on the local filesystem, you can still use all the same commands if you like however. The Didj is different than the LeapPad or Explorer in that it is not a networking enabled device. You've been warned, cwdl and cwdr are you're friends, they will tell you where each path is pointed to and pay attention to the prompt prefix. Also always make sure you are where you think you are, its easy to forget you switched to local or remote, and run a command thinking you are somewhere else. Uploading will over write a directory or file, deleting a directory will remove it regardless if there is anything in it, etc, etc. Either packaging, or opening up the stock firmware for modification.Ĭaution, there are no prompts to ask if you are sure. Utility commands, package_download, cbf_unwrap, jffs2_create_eroots, these commands are there to help facilitate creating updates. OpenLFConnect commands, debug on, set_host_ip, get_mount_point, these are some basic configuration settings used by the base application.Ĭlient commands, dftp_connect, didj_mount, boot_surgeon didj_update, dftp_reboot, these are commands specific to the client that is running, and are checked to make sure their respective client is the currently running client.įilesystem commands, ls, cd, cat, upload, download, these are your basic filesystem commands, for navigation or basic maintenance. There is basically four types of commands. Make sure you understand what you're doing, and use fresh batteries or an A/C adapter during updating. WARNING: This program can flash new firmware, has the ability to make and delete, upload and download, files could be destroyed, firmware flashing could go wrong. Especially if you want those things to run as they should, since there is online functionality that is required for certain features. You'll need to use the LFConnect program. The update functions deal with those exclusively, for updating the offical LeapFrog user interfaces, games, movies, etc. The program deals with firmware/bootloader items. There are also extra functions for wrapping and unwrapping CBF files and extracting lf2/lfp packages. For Didj it can mount the USB drive, copy firmware over, and send the eject command that will attempt to start flashing the firmware. It also manages uploading the surgeon.cbf file for USB boot recovery mode and is capable of enabling ftp/telnet on both devices. For Explorer and LeapPad it can use their dftpdevice to upload firmware. OpenLFConnect is a Python and sg3_utils command line based replacement application for the LeapFrog LFConnect program and more.