Purpose
  This tutorial will teach you how to install the Independence Exploit to your memory card to load programs from your memory card through the use of a PS2 backup CD.  One of those programs, HD Advance, will enable you to play your PS2 games directly from your HDD without the use of the individual discs, therefore lengthening the lifespan of you PS2's laser and your games.
 
 What is the memory card exploit?
  There is a flaw in the way that the PS2 handles the booting of PS1 discs.  The Memory Card Independence Exploit allows anyone with a memory card and a legal, pressed PS1 disc to hijack the boot process and run any piece of code.  Absolutely no modification to the system is necessary to use the exploit.  The files that you can load, with the exception of a few, are legal homebrew applications, meaning some regular person out there has created that program for free to share with the rest of the world.  The homebrew applications have an extension of .elf and will hereby be referred to as elf files.
 
 "My PS2 is unmodified.  Do I need a modchip or something to be able to do this?"
  You do not need a modified PS2 to use the exploit.  You will, however, need a way to get the exploit onto your memory card.  This guide will cover how to get the exploit onto your memory card using a modified PS2, so if you don't have a modified PS2, or know someone who does, this tutorial will not get you any further.  There are a few methods I am aware of in which you can transfer the exploit using an unmodified PS2.  The first, and possibly the easiest if you have a USB pen drive, can be found here (I would suggest reading my entire tutorial first so you get an idea of what you're doing.  The tutorial that is linked to assumes you know all about the exploit).  Another involves getting the disc image on a HDD (that will reside in your PS2) and boot it using HD Advance or HD Loader.  How you get that image transferred to your HDD is beyond my knowledge at this time.  Yet another method is by using the Sharkport, which is a game save transfer device.  The last method is by using a slide card and some sort of boot disc to boot a backup (this method will technically leave your PS2 unmodified).  For now, you will have to do a search to perform any of these methods.  I have never tried any of them.  This tutorial will assume from here on that you have a modified PS2 that is capable of at least booting PS2 CD backups.

Remember, if you have a friend who has a modified PS2, you can transfer the exploit to your memory card on their PS2 in a matter of seconds.  Bring that memory card home and you won't ever need to use that modified PS2 again.
 

Disclaimer
  Nobody is forcing you to follow this tutorial.  It is highly unlikely, but if you manage to break something, whether it be your PS2, a disc, your computer, or a body part, it is not my fault.  If you are clumsy or stupid, don't bother attempting this.  While you don't need to be a genius to do this, you must have a working brain.  If you decide to "mod" your PS2 at any point, be well aware that your warranty, if you still have one left, is completely voided once you open your PS2.  This tutorial will not teach you how to mod your PS2.

This tutorial also briefly shows you how to play your legal backups from your HDD.  If you choose to use this method for copying games you do not own to your HDD, that is up to you.  I will not offer any advice for doing so and I will not be held responsible for any trouble you may get into by breaking copyright laws.

  
 
 What you will need exactly:
  • A Sony Playstation 2 (I really hope you knew that.)
  • A PS2 memory card with at least 2MB space free (I use an unofficial one; it's up to you if you feel you need a Sony one or not.)
  • A way to boot a backup PS2 CD (Only to get the exploit to the memory card the one time.)
  • A PS1 disc (This will be your trigger disc.  Hopefully, it will be on this list)

   - these are optional, but highly recommended -

  • An FTP program on your computer.  I prefer FlashFXP.  (Once the exploit is on your memory card, you can transfer new or updated elf files through ftp within a small network.  This tutorial is not going to cover networking, but if you have a router (or even a hub) you should be fine.  If not you will need to look into a crossover cable, of which I know nothing about.)
  • An official Sony network Adapter (This is required if you want to use a HDD.)
  • A HDD  (It does not need be the official Sony HDD.  Maxtor's are usually recommended, but check with this compatibility list for the status of any particular drives.)
  • *Note - while you technically don't need one to run the exploit, there really are a limited number of things you can do without a HDD.
 
 Step 1 - Let's Get Started!
  The first thing you need to do is download this zip file.  Make a folder in C:\ and call it mc.  This is the folder where you will unpack the zip file to.  It should look like this: 

For this guide, we are going to install the exploit, KeyLauncher (this is the program that will launch when the exploit is triggered), and execFTPs (this is a program that you will boot from within KeyLauncher to turn your PS2 into an active server; when the server is initialized, you will be able to transfer files back and forth from your PS2 to your computer), and HD Advance (this is the program that you can use to play games from a HDD in your PS2).  Read more about it here. (Note: The version included in the zip file has been patched for use on HDD's up to 2TB.  The retail version is advertised as only supporting up to 200GB drives.)
 
 Grab a PS1 game to be your trigger disc
  Here is where your PS1 disc comes into play.  In most tutorials, this step is the hardest part.  Because I'm a nice guy, I've decided to greatly simplify it for you.  The file called TITLE.DB is what tells the PS2 to boot the exploit instead of the game.  Normally, you would have to get the game signature from the PS1 disc you want to use and patch it into the file.  I have included a TITLE.DB file that has over 800 PS1 game titles.  IF you have a PS1 game, odds are it's in this file.  Take a look at the file here just to make sure you have at least one of these games.  If you do, any game you have on that list will be your trigger disc and we can move on.  If not, you will have to complete this extra step to make a TITLE.DB file for your PS1 game.
 
 Step 2 - Setting up KeyLauncher
  KeyLauncher is a nice little program that boots up when the exploit is triggered.  It is basically your start screen, where you are able to choose to boot all of your other programs.  There are a few other "boot" programs, as they're called, you could use instead, but KeyLauncher has the nicest layout right now and is the easiest to use.  Here is a screenshot:

As you can see, each program you want to boot will be linked to a button on your PS2 controller.  For now, you will just have the 2 other programs to load, but I will show you how to easily add more later. 

I've already set KeyLauncher up for you, but if you want to make any changes - and you will eventually, so pay attention -  this is what you're going to need to do.  Using Notepad, open the file called KL.DAT.  It should look like this:

This file is what you'll use to link your elf files to their buttons.  What do all the lines mean?  Well, the first line "AUTO=0" tells KeyLauncher to boot one of your elf files within a certain period of time.  If you want a program to boot 5 seconds after KeyLauncher starts, the line should read "AUTO=5" and there should be a "@" at the end of the line for the program you want to boot.  For example, if I wanted HD Advance to automatically boot 5 seconds after KeyLauncher starts, my KL.DAT would look like this:

 Let's say you didn't want to mess with KeyLauncher.  Let's say you wanted to automatically boot into a program (HD Advance, for example) instead of being able to boot anything else.  The "@" will still be at the end of the line for the program you want to automatically start with, but the top line will read "AUTO=0."

The other lines - which start with []=, /\=, O=, X=, R1=, R2=, R3=, L1=, L2=, and L3= - are the button assignments.  The correct way assign a button to an elf is with a line like
"mc0:/BADATA-SYSTEM/AAAAA.ELF;Xxxxx"

  • mc0:/ points to the memory card in slot 1. (mc0 means memory card 1, while mc1 means memory card 2 - remember that.  Right now, I believe KeyLauncher only boots elf files from the mc or your HDD)
  • BADATA-SYSTEM is the folder where your exploit, along with all of your other elf files will live.  If you don't have a North American PS2, it might be called BEDATA-SYSTEM or BIDATA-SYSTEM.
  • AAAAA.ELF is the exact name of the elf file as it sits on your memory card.  Capitalization is super important here.  Every elf title will be capitalized, including the ELF extension at the end.  The A's will obviously be substituted for the name of the elf file you want.
  • Xxxxx is the name that you want to call it.  This is the only part that will be shown when KeyLauncher boots.

KeyLauncher has already been renamed for you, but understand that the "boot" program you want use - if it's not KeyLauncher - must be renamed to BOOT.ELF.  Without a BOOT.ELF file, the exploit will not boot to anything.  You will most likely just get a black screen.

Now you know how to use and set up KeyLauncher.
 
 Step 3 - HDL Dumb
  HDL Dumb is an easy to use version of a program titled "HDL Dump."  It's a program that let's you install PS2 games (either by disc or by image file) right to your PS2's HDD through networking.  There are 2 parts that work in conjunction.  The file titled HDLD_SVR.ELF is the program that runs on the PS2 side and HDL Dumb is the program that will be run from your PC.  HDLD_SVR.ELF should be in your "files" folder.

Download HDL Dumb right here.
 
 Step 4 - execFTPs
  execFTPs is the PS2 server.  Basically, you run this small  program on your PS2, and you can use an ftp client to connect to your PS2.  From there, you'll be able to add new elf files, delete files from the card, or edit certain files (such as KL.DAT).  Open CONFIG.DAT with Notepad and you will see only a single line with 3 sets of numbers, each separated by a single space,  The line will look like this:

192.168.0.10 255.255.255.0 192.168.0.1

If you don't know your computer's default values (IP, subnet mask, and starting IP), go to Start > Run > type cmd and press enter.  Then type ipconfig and press enter.  This will give you the values you'll need.

  • The green field is your PS2's IP address.  You make this up and make it only a few numbers different than your PC's IP.  If your PC's IP is 192.168.0.10, then make your PS2's IP 192.168.0.12.
  • The red field is your subnet mask.  Use the same as what command prompt tells you it is.
  • The yellow field is your starting IP.  Use the same as what command prompt tells you it is.

Make sure to save the file once you've set it up.
 
 Step 5 - Creating your CD image
  Now that all your files are setup, it's time to create your CD image.  Once the image is made, you'll be able to burn it with your favorite CD creating software.  Open up CDGenPS2.exe, which will look like this:

Go to your C:\mc\ folder and drag and drop the following files , in this order into the right side of CDGenPS2:

  • CDVD.IRX
  • EXPINST.ELF
  • SYSTEM.CNF
  • TITLE.DB

Next, drag and drop the entire FILES folder in C:\mc\ to the same spot in CDGenPS2.

The last file to drag and drop will be the dummy file - DUMMY.DAT.  Put this in the same way you've done all the other files.  Once all your files are there, it will look like this:

Note that "Files" folder will go right to the top, so don't think that you placed it in the wrong order.  Now you must fix the LBA of the SYSTEM.CNF.  To do so, right click on SYSTEM.CNF and click "edit."  When the pop up appears, check the box that says "fix LBA" and type "12231" in the field.  It will look like this:

Then click ok.  CDGenPS2 will now look like this:

Now we can hit the hit the button on the left side.  It will ask you where you want to save it and you can also give it a new name if you want.

Using your favorite CD burning software (I prefer Nero), create your CD.  You now have a PS2 backup. 

 
 Step 6 - Installing the exploit
  This step is pretty simple.  Boot the disc the way you normally boot backups.  The disc will automatically install the Exploit, KeyLauncher, ExecFTPs, HD Advance and HDL_Dumb onto your memory card, along with any other elf files you decided to use with your exploit.  Installation will be done when your screen says "Installation Complete!"   If you get an error that says source file cannot be copied or something, it means you don't have enough free space on your memory card.

Take that disc out, put in your PS1 disc that you decided to go with earlier, and boot it regularly.  If all goes well, your screen will turn white for a second and it will boot into KeyLauncher.  If you actually want to play that PS1 game, just take out your memory card and then turn on your PS2.  Once the game is loaded, you can put the memory card back in if you need.

Congratulate yourself, because everything from here on in is cake compared to what you've done.
 
 Step 7 - Installing more elf files
  Now that you have the exploit and you've been playing around with it, you decide that you want to install more elf files, but you don't want to have to make a whole new CD.  No problem.  Start up execFTPs from KeyLauncher.  Once it says “FTP Server initialed at port 21,” go to your computer and start up your ftp program (I recommend FlashFXP).  Type in the address you gave your PS2 earlier, turn passive mode off, and connect.  It will have 3 folders - hdd, mc, and pfs. 

Go into the "mc" folder and then go into the "0" folder.  You should see a list of folders, with BADATA-SYSTEM at the top.  This is the folder where your exploit is. (One important note - just so you don't get worried - there is a bug with execFTPs where if there are 20 or 21 files in any directory, they will not show up.  It's not a bad thing and it doesn't mean anything on your memory card is missing, but if you run into that, you might want to make a few small files and transfer them to the affected directory so you can properly view all of your files.)  Before you enter the folder, make a new folder called SYS-CONF for later. (When you see this folder on your memory card using the PS2 browser, it will appear as corrupted data because it has no icon.  In an advanced tutorial, I will show you how to create your own PS2 icon so it appears as a valid game save.)  Now you can enter the BADATA-SYSTEM folder.  Any new elf files you have and want to install, you can just transfer right to this folder.  Remember to edit you KL.DAT file so your new elf files can be on your KeyLauncher menu.
 
 Step 8 - Installing PS2 games to your HDD through your network
  Once you have your HDD working in your PS2, there are a couple ways to transfer your games.  This portion will show you how to transfer games over your network.  First, using execFTPs and your ftp program, you should have made a folder called SYS-CONF.  In it you need a file called IPCONFIG.DAT.  This file is exactly the same as the CONFIG.DAT file you used earlier - it just has a different name.  Transfer IPCONFIG.DAT to the SYS-CONF folder.  This file is necessary to use HDL Dumb.

Launch the HDL Dumb Server from your PS2.  Now launch the HDL Dumb program you downloaded earlier for your PC. 

It should be pretty easy to figure out.  If you can't network, you can take the HDD out of your PS2 and stick it in your PC.  Windows will not recognize it, but this program will.  The transfer rate while it's in your PC is much faster, by the way, than doing this network method.

Anyway, hit the ... box to pick an image file or check the the circle for Optical drive if your game is in one of your drive's.  Name your game as you want it to appear in your HD Advance screen.  The Startup (your disc signature) should already be filled in for you.  If not type it in here. (The one time I had to type it in manually, the game wouldn't work from HD Advance.)  On the bottom, you will see a list for compatibility flags (modes).  Many games will work without any modes, but there are many that require one or more modes turned on to work.  You don't really need to worry about having the right one checked at this point, as you can change them from within HD Advance at any time.  Here is a simple breakdown of what the each mode means, since everybody is always curious:

  • Mode 1: Enables slower HDD access. Passes data from the HDD slower for games that rely on the speed the data is coming from the CDVD.
  • Mode 2: Enables DVD9 support.
  • Mode 3: Removes the Loader from the memory after the game is patched. Some games flush the location where the loader is (because some cheat programs use the same location), and if after that the game resets the IOP (when the loader kicks in to patch stuff) and the system is still patched to enter the loader it crashes.

I've found that mode 3 is usually the mode that needs to be enabled when a game won't boot.  For a complete list of games and whether or not they are compatible with the HDD, go here.  If your game is not on that list for some reason, you will need to play around with the modes to figure out what works for you.

Once you have everything set, hit the "Install" button and sit back as your game installs to the HDD.
 
 You are now done!
  Show off your new knowledge to your friends and they will think you're some sort of genius.  You will automatically be the coolest person of the group until, of course, it gets old and they get tired of playing video games.