Exploit Install via Cheat Device using a USB Thumb Drive


This tutorial will cover exploit install using the most popular method, using a cheat device, a USB thumb drive, and a custom made game save.


The memory card exploit will work on old school fat PS2's, not any version of the slimline ones.  Also please note, that due to the USB driver that most cheat devices use, there is a limitation of which USB thumb drives that will work with the chosen cheat device.  My suggestion is to try one, and if it doesn't work, try a different brand.  Some have said that Lexar brand thumb drives have the best compatibility with said driver.


Required Files

Titleman Frontend - This program is a Windows GUI that allows you to create your TITLE.DB.

PS2 Savebuilder - This program allows you to build your cusom game save into the appropriate format for your cheat device.

uLaunchELF - PS2 homebrew program - Used to launch, manage, and transfer PS2 format homebrew.  It also has a built in FTP server, and HDD manager.

Game Save Preparation

Since the method of creating the exploit game save is the same for all cheat devices, this will be in one section.

Step 1 - Creating your custom TITLE.DB

Open Titleman Frontend.  You will see this screen.


First thing you need to do is click on the "Create TITLE.DB" button.  This will obviously create a new TITLE.DB for you to add your PS1 disc ID('s)

Before we go any further, I need to explain a major detail.  There are 3 major regions of PS2 systems with the exception of using a demo with the disc ID of PSX.EXE

NTSC U/C often use disc ID's starting with SCUS or SLUS

NTSC Jap uses disc ID's of SLIP and another one I can't seem to remember or find at the moment.


It is important that you choose the correct region for your system and game(s) you would like to use as your trigger disc.  Also the correct format for a disc ID is like this (case sensative) SCUS_000.00

There are no exceptions, you MUST use your correct region and format for the exploit to trigger properly.

Once you have entered you disc ID porperly, click on "Add Exec".  When you have finished entering your disc ID('s), click on "List current contents of TITLE.DB".  You should see the ID's you entered in the information screen, and like I have done.


Step 2 - Building the Exploit Game Save

The exploit resides in a game save on your memroy card called "Your System Configuration".  This save actually has one of three logical names on your MC depnding on your PS2's region.  This is important that you use the correct one.





Extract the BOOT.ELF from the uLaunchELF zip file and place it in the same folder where you stored your TITLE.DB

Now, go ahead and open PS2 Savebuilder, and click on button that looks like a page to create a new file.

Then you should see this:

Now, you need to drag two files into the window.  These files being "BOOT.ELF" and "TITLE.DB".  You also need to rename the box next to "Root/ID" to the appropriate region as describe above.  For example mine is a NTSC U/C so I used BADATA-SYSTEM.

The final step of this is to save your exploit game save into the appropraite format for your cheat device.  the picture below is pretty self explanatory.

Now, just copy the exploit game save to your USB thumb drive.

End of game save preparation

Now, go ahead and start up your PS2 and delete the "Your System Configuration" save.  If you don't, it could cause a conflict.

Now the only thing really to do is to boot  your cheat device, plug in your USB thumb drive into your PS2 and transfer the game save using the Save Manager in the cheat device.

Don't be alarmed when the save shows up with the name "NEW_FILE" its normal.  Once the PS2 is rebooted, that folder will become "Your System Configuration" again, only with the exploit files in there with it. (notice that the file size is now over 300KB instead of 5KB)

Place your PS1 "trigger disc" in the tray and select it.  You should now see a white flash, and then uLaunchELF screen appear.

If you now see uLE, congrats, you have successfully installed the memory card exploit.  If you don't see uLE, or see the system frozen on a colored screen, you will need to redo the save.