Sponsored Links

Sponsored Links

PS2Classics - PS2 Classics Decryption and Encryption GUI Arrives

Sponsored Links
79w ago - Following up on the PS2 Classics Algorithm and PS2 Classics Keys, today PlayStation 3 homebrew developer IngPereira released PS2 Classics source code followed by aldostools making a PS2Classics GUI application followed by v1.1, v1.2, v1.3, v1.3.1, v1.3.2 through v2.0 available for decrypting and encrypting PS2 Classics with details below.

Download: [Register or Login to view links] / [Register or Login to view links] / [Register or Login to view links] / [Register or Login to view links] / [Register or Login to view links] (Copy to cygwin bin dir. Command: rap2klicensee rap out_klicensee) / [Register or Login to view links] / [Register or Login to view links] (30.5 MB) / [Register or Login to view links] and [Register or Login to view links] by geokhentix (with the graphics, sound, modified PARAM.SFO for remoteplay and the title alongside Klicensee and .rap included) / [Register or Login to view links] / [Register or Login to view links] / Noob Tutorial to Convert PS2 Games by kristijan1001 / [Register or Login to view links] / [Register or Login to view links] by deank

To quote, roughly translated: PS2Classic first version of the source code uploaded by USER PS3DEV Git on net.

The last script Flatz now ported to C and with the option to decrypt and encrypt! Ps2 Classics. So now you can also decrypt and encrypt ps2classics.

From flatz: Use this script ([Register or Login to view links]) to update a hash table inside decrypted virtual memory card: pastie.org/private/eukpgr74ydi7w9cmhgtmw

[Register or Login to view code]

I think it will allow to use original PS2 saves on PS3. Just use the script on your VMC file and encrypt the file with Aldo's tools to the VME format.

To everyone who handles the issue and the skimming want (I think that's there too Andara and a GUI to facilitate the decryption and encryption PS2 isos) now you can see in a more crystal clear the PS2 Emulator Sony did possible on your machine with 256mbs of ram.

It speaks of a very good compatibility not clear at the moment but I think it gets a little better when using the emulator on fw 4.31 also if you change the DISC ID (SL? S-?????) The game will not work in question by one who is already confirmed in the Store operation.

Here the list of ps2 games (en.wikipedia.org/wiki/List_of_downloadable_PlayStation_3_games#PlayStation_2_classics) and uploaded to the sony store: List of PS2 games on PSN published. The issue seems to be like the retro 360 hacked with a game changing IDs nonfunctional by other active functional emulator then this game customized configurations that run some others.

Also before signing their own ps2 isos needed and would be ideal you to do a test with this encryption find it out easily if you do it a ps2 classic refirmais proven again and so you could see if it still works which would mean that no apparently problems with encryption and you can safely test any ps2 iso.

In such case you can also try to sign the Open PS2 Loader it should work on the emulator because it was already functioning in 3.55. Here I upload the first version already compiled (above) for the devs or advanced who want to eat it right now but have some error or problem.

Is a new version of py script of flatz ported to C and now including encryption stuff, so now we can decrypt and encrypt any ps2 classic, ps2 backwards compatibility for every PS3!

So ps2 modding of any ps2 classic is possible like modding gta san andreas ps2 classic like on ps2 times and obviously too encrypting any ps2 iso but we don't know all about compatibility but it looks like a good amount of games should work. We need to test Open PS2 loader and ps2 homebrew and see if they work too on last emulator from sony.

Thanks to flatz and user for the source code. Here gtasa eur / usa klicensee already in binary files.

Download: [Register or Login to view links]

Decrypt: ps2classic d cex GTASA_NPUD_KLIC.KEY ISO.BIN.ENC ISO.BIN meta_out

Make any modifications on the game by extracting game data folder of ISO.BIN (Can be a simple CD-ROM ISO9660 image or UDF DVD image like gtasa) you can use Ultraiso or any other iso tool and now.

Encrypt: ps2classic e cex GTASA_NPUD_KLIC.KEY ISO.BIN ISO.BIN_mod.ENC ISO.BIN.ENC UP9000-NPUD20946_00-0000000000000000

UP9000-NPUD20946_00-0000000000000000 = Content ID

Again this example can be done too when you want to load other game so you use other iso from any game and you can change DISC ID on PARAM.SFO, ISO.BIN.EDAT by following flatz instructions above. Or you can even use savedata from original PS2 by modifying vmc. Thanks to flatz now we can do many things to explore the new ps2 emulator.

From aldostools on the PS2Classics GUI: Usage:


[Register or Login to view code]


[Register or Login to view code]


[Register or Login to view code]

PS2Classics_GUI – (c) 2013 by Aldo Vargas


1. Copy your idps and act.dat to scetool/data
2. Copy your rap files in scetool/raps

The GUI requires to have installed the following VB5 Runtime: [Register or Login to view links]

Note: The following step is not necessary, it is done automatically by my ps3tools (if installed running as Administrator):

2- Just to make sure, go to where you installed it and run "PkgView.exe" once, click on "Tools" menu and associate with PKG files, then close it.

Other notes, the PS2 Classics GUI creates the .key from the value entered in the klicensee field. If the PS2 raps are copied into the RAPS folder (located inside the .\scetool folder included with the PS2 Classics GUI), the tool will fill automatically the klicensee field when you select the ISO.BIN.ENC

PS2 Classics GUI 1.1 Changes:

  • Added support for drag & drop and command line interface (CLI) -> pass the full path of the image as parameter.
  • Added support for auto decryption if a PKG is selected or passed as parameter.
  • RAP files are auto copied to the RAPS folder if they are present in the same folder of the PKG or in a "exdata" folder
  • Pad verification (for multiple of 0x4000) now asks if you want to add the required padding when needed.
  • Image type (CD or DVD) is now detected and displayed on the GUI
  • Added option to patch the image with the file size and image type (CD or DVD)
  • The program looks for the LIMG header in the offset (File Size - 0x4000), and changes the 4 bytes size (in big endian format) to: (Image Size - 0x4000) \ 0x800 for DVD and sets 8th byte to 1. Bytes 15-16 are set to 08 00 (Image Size - 0x4000) \ 0x930 for CD and sets 8th byte to 2. Bytes 15-16 are set to 09 30
  • PkgView by ifcaro is now included with the tool.

Note: Please consider this version a "beta". Backup your ISOS before apply any of the aforementioned patches, just in case a bug is found.

PS2 Classics GUI 1.2 Changes:

  • Fixed the patch that writes the new image size and image type in the LIMG header.
  • Now displays the 16 bytes of the LIMG header when the image is opened.
  • Now allows to add the LIMG sector to the end of image.
  • Changed the GUI to a "tabbed look".

PS2 Classics GUI 1.3 Changes:

  • Added support for the VMC/VME commands.
  • Added /? to display the command line syntax.

PS2 Classics GUI 1.3.1 Changes:

I just updated the PS2 Classics GUI 1.3.1 to support the decryption/encryption of the CONFIG. Now I see that one of the major issues now is that multiple games now have the same Content ID and should replace the ISO.BIN.ENC in the /game/NPxD00000/ folder. The steps are:

1- Copy the rap of your base game (PS2) as a new random content id. eg. EP0000-NPED12345_00-AAAABBBBCCCCDDDD.rap
2. Copy the new rap to the RAPS folder of PS2 Classic GUI
3. Extract the files of the PKG of your base game (except CONFIG and ISO.BIN.ENC, they will be deleted/replaced anyway)
4. Launch PS2 Classic GUI, select the ISO and enter the new content id. eg EP0000-NPED12345_00-AAAABBBBCCCCDDDD
(it should display the same KLIC of your base game)
5. Add the LIMG header and encrypt the ISO as ISO.BIN.ENC
6. Edit the PARAM.SFO on the extracted with the title of the PS2 title.
7. Copy the ISO.BIN.ENC to the base game
8. Rename the extracted folder with the new content id (EP0000-NPED12345_00-AAAABBBBCCCCDDDD), right click and select Make PKG
9. Install both raps (the original and the new created) using reActPSN
10. Install the PKG
11. Test if it works.

PS2 Classics GUI 1.3.2 Changes:

PS2 Classics 1.3.2 now has a ISO9660 check (it looks if offset 0x8000 has the CD001 magic)... just to warn about any potential problem.

PS2 Classics GUI 1.4 Changes:

I have updated the tool to version 1.4. The CD001 is now checked at 0x8000 for DVD and 0x9318 for CD. This version now uses the Volume Sectors located at offset 0x8050 for DVD and 0x939C for CD. If the LSD value is 0, tries to use the MSD value. If both values are 0, then it uses the former method using fixed sector sizes 0x800/0x930.

The sector size and number of sectors is now displayed, like in ImgBurn, so now it can be easily compared with the ones in the LIMG. Other minor changes were made... I hope that this build help to improve the creation of the images (specially the CD ones).

PS2 Classics GUI 1.5.1 / 1.5.2 Changes:

  • Graphical progress bar
  • Display of ICON0 on top right corner
  • Display of title id & game title when an iso or encrypted iso is selected
  • Support to open/edit PARAM.SFO
  • Patch the PARAM.SFO with title id & game title
  • Uses the default Klicensee and Content ID from CaptainCPS-X 's PS2 Classics Placeholder
  • Includes the RAP for PS2 Classics Placeholder (also reActPSN in included in the rar)
  • New ps2classic.exe from IngPereira & flat_z
  • Rehash of saves
  • New heuristics verification to know if hash table must be updated or appended to the save file
  • The conversion now asks where to save the result file (ISO.BIN, ISO.BIN.ENC, CONFIG, CONFIG.DEC, SCEVMC0.VME, SCEVMC0.VMC)
  • Many other improvements

PS2 Classics GUI 1.6 Changes:

  • New options to set default output mode and default path
  • Auto creation of PS2ISO folders (output mode PS2ISO)
  • Auto creation of Package files (output mode Package File)
  • Auto-detected game title now can be selected/copied

PS2 Classics GUI 1.6.1 Changes:

[*]Added shell integration to .BIN and .ISO file extensions
  • New options to set default output mode and default path
  • Auto creation of PS2ISO folders (output mode PS2ISO)
  • Auto creation of Package files (output mode Package File)
  • Auto-detected game title now can be selected/copied

PS2 Classics GUI 1.7 Changes:

  • Solves some issues with the file associations.
  • Verifies if the file system accepts the file size (>4GB) and if there is enough free space.
  • Improved the LIMG segment detection/patching before the encryption.
  • Added option to auto rename the PKG to title name + [title id], instead of the content id as name.

PS2 Classics GUI 2.0 Changes:

The new version now allows to create the PKG with custom images and text.Drag & drop the images (jpg, bmp, gif, tif or even a PARAM.SFO) or paste an image from the clipboard or select the images using the open dialog, and the program will create the images with the proper dimensions when the "Make PKG" button is pressed.

From zecoxao: vmc key: 64 E3 0D 19 A1 69 41 D6 77 E3 2E EB E0 7F 45 D2

Let's begin then:

Football Generation NPED00028: 4C 49 4D 47 00 00 00 02 00 03 C7 43 00 00 09 30

Psychonauts NPUD21120: 4C 49 4D 47 00 00 00 01 00 1A 2F 00 00 00 08 00

Disgaea 2 NPUD21397: 4C 49 4D 47 00 00 00 01 00 0A A4 E0 00 00 08 00

NPED00032 Dirt Track Devils: 4C 49 4D 47 00 00 00 02 00 01 59 11 00 00 09 30

Baroque NPED00099: 4C 49 4D 47 00 00 00 01 00 11 66 50 00 00 08 00

Dreams coming true guys... for those who wish to document the LIMG: ps3devwiki.com/wiki/Talk:Emulation#LIMG_Table_.28PS2_Classics.2C_help_to_fill_please.29

From mind: LIMG for NFS Underground2 NTSC US: 4C 49 4D 47 00 00 00 01 00 15 6B 80 00 00 08 00

From Agrippa90: LIMG for GTA SAN ANDREAS version "SUB-ITALIAN" (different to general Europe version): 4C 49 4D 47 00 00 00 01 00 21 AD A0 00 00 08 00

From DaBlackDeath: LIMG of NPED00151 - ROOM ZOOM: 4C 49 4D 47 00 00 00 01 00 09 CC 10 00 00 08 00

Below is a Guide to Obtain, unpack, decrypt, encrypt and repackage a PS2 Classic from CaptainCPS-X as follows:

OK let me try to put it simple. The decryption is not really needed, I added it to the guide so people would know how to achieve the whole process.

The games I have reported working are not PS2 Classic, they are PS2 ISOs not obtained from PSN that have been patched with the recently discovered LIMG data segment. After patching and encrypting they will be playable on any PS3, just as any PS2 Classic would.

The process to play PS2 games at this moment would be:

  • Obtain just one PS2 Classic from PSN to use as placeholder
  • Unpack the PS2 Classic PKG
  • Encrypt any PS2 ISO patched with the LIMG data segment as "ISO.BIN.ENC"
  • Replace the original "ISO.BIN.ENC" with the one you just patched + encrypted

You can then repackage the PS2 Classic and install it on your PS3, the only step you would need to do is the activation process using reActPSN just once.

After you have just one PS2 Classic installed and activated on your PS3, you can just replace the "ISO.BIN.ENC" with any other patched + encrypted ISO you like. There is no need to be installing + activating every individual ISO with a different PS2 Classic placeholder, unless you really want to do so.

Guide to Obtain, Unpack, Decrypt, Encrypt and Repackage a PS2 Classic by CaptainCPS-X


  • The main goal of this guide is to explain how to decrypt and encrypt back a PS2 Classic PKG for use with the PS3.
  • This guide will be updated from time to time, and some images / screenshots will be eventually included to illustrate some steps in a clearer way.
  • A sub-guide will be included later to explain how to install PS2 Classics using reActPSN, it is very easy and just require the use of RAP files.
  • Included are a collection of tools you will need before proceeding. This guide assumes that you, the user, knows how to extract a compressed file, edit a text based file and follow instructions.
  • In this guide we will be using "Capcom Vs SNK 2 Millionaire Fighting 2001" as example.
  • Modification of ISO or replacement with alternate ones has not been tested, as a result I decided not to add experimental procedures to this guide. As soon as I confirm a working method for this, I will add it.


Thanks to flatz , IngPereira , LoOzers, aldostools , baargle , fail0verfl0w, Graf _chokolo, and everybody else involved in the ps2classic dev stuff.


Here you have a collection of all tools used in this guide. Some of them have custom and easy to modify scripts made by me.

Download: [Register or Login to view links] (15.7 MB)

It includes the following tools:

  • aldostools 's ps3tools v2.2.1
  • aldostools 's ps2classic GUI
  • ps2classic v1 (thanks to IngPereira )
  • rap2klicensee (thanks to IngPereira )
  • PSNStuff v1.8 (thanks to LoOzers)
  • reActPSN

NOTE: In the guide I mentioned the extraction of each tool to its own directory, but when I made the final RAR package I decided to include them all already extracted so, when following the guide just image you extracted them .


1- Extract "PSNStuff_ver1.8.zip" somewhere you like.
2- Run "PSNStuff" and wait for it to update the database.
3- On the main screen, click on the filter drop-down menu and select "PS2".
4- Look for "Capcom Vs SNK 2 Millionaire Fighting 2001" and download both PKG / RAP.
5- Close PSNStuff, you should have 2 new files now:

  • pkg/NPJD00015 Capcom Vs SNK 2 Millionaire Fighting 2001.pkg
  • exdata/JP0102-NPJD00015_00-0000000000000000.rap


1- Install aldostools's ps3tools v2.2.2 ([Register or Login to view links])
2- Go to PSNStuff "exdata" directory and right-click "JP0102-NPJD00015_00-0000000000000000.rap", then click on "Convert RAP to RIF KEY".
3- You will now have a 2 new files called "JP0102-NPJD00015_00-0000000000000000.key" (binary) and "JP0102-NPJD00015_00-0000000000000000.key.txt" (plain txt, not used in this guide)

Note: The obtained key is equivalent to the "NPJD00015.KEY.BIN" so I recommend to rename it to match the guide to avoid confusion.


1- Extract "rap2klicensee_capcpsx.zip" somewhere you like.
2- Go to PSNStuff "exdata" directory and copy "JP0102-NPJD00015_00-0000000000000000.rap" to where you extracted "rap2klicensee_capcpsx".
3- Run the included batch / script file "GET_KLICENSEE.cmd" (as Administrator).
4- You will now have a file named "NPJD00015.KEY.BIN"

NOTE: If you want to get the klicensee for other RAP, just edit the script / batch file with a TXT editor (ex. Notepad).


NOTE: If you have ps3tools by aldostools already setup and you have the shell integrated features then you can skip step 1 and 2.

1- Install ps3tools v2.2.1 (ps3tools_2.2.1.zip) (by aldostools).
2- Just to make sure, go to where you installed it and run "PkgView.exe" once, click on "Tools" menu and associate with PKG files, then close it.
3- Go to PSNStuff "pkg" directory and right-click "NPJD00015 Capcom Vs SNK 2 Millionaire Fighting 2001.pkg", on the pop-up menu click "Extract to current path...".
4- You will now have the extracted PS2 Classic game files.


1- Extract "ps2classic_v1_capcpsx.zip" somewhere you like.
2- Go to the directory where you extracted the PS2 Classic game files and copy "ISO.BIN.ENC" to where you extracted "ps2classic_v1_capcpsx".
3- Go to the directory where you extracted the "rap2klicensee_capcpsx" and copy "NPJD00015.KEY.BIN" to where you extracted "ps2classic_v1_capcpsx".
4- Run the included script / batch file "DECRYPT.cmd" and wait for the finish message to appear, do not close it before. Depending on the size of the file it might take longer, just be patient.
5- You will now have 2 new files: "ISO.BIN" and "meta_out"

NOTE: Do not modify the decrypted ISO, when I confirm how to do this, I will include it in my guide, for now just continue.


1- While still at "ps2classic_v1_capcpsx" directory, run the included script / batch file "ENCRYPT.cmd" and wait for the finish message to appear, do not close it before. Depending on the size of the file it might take longer, just be patient.
2- You will now have a new file: "ISO.BIN_mod.ENC"


* coming soon...


* coming soon...


1- While still at "ps2classic_v1_capcpsx" directory, copy or move "ISO.BIN_mod.ENC" to where the original was extracted / located (refer to "UNPACKING THE PS2 CLASSIC" up)
2- Make a backup if needed of the original "ISO.BIN.ENC" then delete it from this location.
3- Rename the new "ISO.BIN_mod.ENC" to "ISO.BIN.ENC"
4- Navigate 2 directories up to where "ISO.BIN.ENC" was located.
5- Right click the directory and select "Make PKG..." (You must have ps3tools (by aldostools ) installed, refer to "UNPACKING THE PS2 CLASSIC" up).
6- You will now have a file called: "PP0001-SLPM65047_00-0000111122223333.pkg" (rename as you like).


1- Install "reActPSN_v2.23_CFW_340_4XX.pkg" on your PS3.
2- Install the PS2 Classic "PP0001-SLPM65047_00-0000111122223333.pkg" on your PS3.
3- Create a user account called "aa" on your PS3.
4- Create a directory called "exdata" on a external USB Storage Device (FAT32)
5- Copy the "JP0102-NPJD00015_00-0000000000000000.rap" from the PSN Stuff directory (refer to "OBTAINING THE PS2 CLASSIC" up) to the new "exdata" directory created on the external USB Storage Device (FAT32).
6- Connect the USB Storage Device (FAT32) to your PS3.
7- Switch to user "aa" on your PS3
8- Run "reActPSN" and wait until the PS3 restarts, you can now enter your regular account and access the PS2 Classic.

PS: I am currently preparing more content for the guide to make it even more complete so please be patient if what you are looking for is not here. SeeYa!

Update: OK guys here you have something to play with, I just called it LIMGpatcher, it is a quick application for testing purposes.

It is a tool that will automatically patch any supported ISO with the LIMG segment and the proper volume size / total sectors data.

Source code will be published later, right now it is a mess . Usage is very simple, you just double click on the application to run it, and a window will pop-up that will let you explore your computer for any ISO / BIN image. It is a console application but doesn't process any command line arguments.

It have a simple check to see if it can find the CD001 standard ISO9660 identifier at sector 16 (2048 per sector). And it will check if the ISO / BIN image has been already patched to avoid re-patching or appending any more data. I haven't run this on other PCs but it should work fine, I tested it on Windows 7 x64 Ultimate. Enjoy!

Download: [Register or Login to view links] (30 kb)

After using this on any specified ISO / BIN, you can then rename it to "ISO.BIN" then follow my guide to encrypt it as "ISO.BIN.ENC" and finally repackage it.

Or if you already have the PS2 Classic installed + activated, just replace the ISO.BIN.ENC on your PS3 with the new one (you can use multiMAN for example to transfer the file via USB / FTP).

PS: I am currently doing tests, so that is why it has been difficult to write more stuff to the guide or update it, but eventually I will keep posting more information so everyone can get to play their favorite PS2 games on their PS3. Sorry if my explanations are not very good, I haven't sleep at all since like 20 hours, been at university, doing rl stuff and my body is just a mess , need sleep soon haha!

Just made a backup of my original Metal Gear Solid 3 [US] disc using ImgBurn, saved it as .ISO and then patched it using my application. After that I encrypted it following the procedures mentioned on my guide and uploaded the "ISO.BIN.ENC" via FTP to my PS3. Started playing it and it looks pretty good so far

Convert any PS2 ISO to PS2 Classic Guide by CaptainCPS-X

Note: This guide will have technical details to a minimum, to avoid confusion. But, assumes that the user knows how to install PKG files on the PS3, and how to transfer files to the internal hard disk drive of the PS3 console.

In this guide you will learn how to convert PS2 games in ISO format to PS2 Classic, making any game playable on your PS3 console.

Users on Rebug 4.21.1 must update to latest release, or you will not be able to play PS2 Classics (Thanks to ploggy and others for reporting)

I have made a custom PS2 Classic PKG based on 'Maximo (US / Capcom)', and edited PARAM.SFO, Images with custom ones (I think you guys will like them ) and removed the original ISO.BIN.ENC, CONTENT directory and CONFIG file. You don't have to go to PSN Stuff anymore with this placeholder PKG, I will provide the needed .RAP / KLICENSEE too.

It is just 17MB approx (2x 8MB Virtual Memory Cards + Images) I hope you all don't mind, but I will be restructuring the guide to be even easier. In a couple of hours I will have everything done and will let you all know (Placeholder PKG will be available for download then as well)

PS: And yeah I have an idea for a PS3 homebrew that allows the user to view a list of ISOs located on the HDD, then let them "switch" the one on the placeholder, by just moving / renaming the ISOs from one directory to another (copying it would be tedious for big files) and it could even change the PARAM.SFO title to display what ISO is selected at the moment. I can't promise anything to be done today or Friday, but maybe in the weekend when I have more free time to code, probably I can do something about that. SeeYa!

Note: This guide will have technical details to a minimum, to avoid confusion. But, assumes that the user knows how to install PKG files on the PS3, and how to transfer files to the internal hard disk drive of the PS3 console.

In this guide you will learn how to convert PS2 games in ISO format to PS2 Classic, making any game playable on your PS3 console.


flatz, IngPereira, LoOzers, aldostools, baargle, fail0verfl0w, Graf _chokolo, and everybody else involved in the ps2classic dev stuff. Thanks to all the users who have shown their support and given me nice comments, I appreciate it.


  • PS2 Classic Placeholder PKG
  • RAP file to activate the PS2 Classic Placeholder PKG
  • ReActPSN (used only once, to activate the PS2 Placeholder PKG)
  • aldostools's ps3tools v2.2.2
  • aldostools's ps2classic GUI v1.3
  • Any PS2 game ISO

All of the requirements can be downloaded here (except the PS2 ISO LOL!)

Download: [Register or Login to view links] (30.5 MB) / [Register or Login to view links] (Mirror) / [Register or Login to view links] (15 MB)


1- Copy the provided "exdata" directory to a external USB Storage Device (FAT32).
2- Install the provided "PS2 Classic Placeholder PKG" to your PS3.
3- You will now have a new icon on the XMB, but it is not activated, and of course doesn't have the PS2 game ISO yet.
4- Install the provided "reActPSN PKG" to your PS3.
5- Create a new user on your PS3 called "aa".
6- Log in to the new user account and run "reActPSN"
7- It will restart you PS3 and you can now log back in to your regular user account.

Note: After this step, the placeholder will be ready and you will not have to mess with reActPSN anymore. It still does not have any PS2 ISO that will be done later, keep reading.


1- Install aldostools 's ps3tools v2.2.2
2- Go to where you just installed ps3tools and run "PKG_ContentID.exe" (as Administrator to allow Registry write privileges) then close it (this will add the "Make PKG..." available on the windows context menu).
3- Install / extract aldo stool's ps2classic GUI v1.3 to anywhere you like


1- Run "ps2classic GUI v1.3" and switch to "Encrypt" tab.
2- Browse your PC for any PS2 game ISO and select it.
3- Copy and Paste this on the Content ID field: 2P0001-PS2U10000_00-0000111122223333
4- On the klicensee field Copy and Paste this: E4E54FD67C16C316F47829A30484D843
5- Click on "Add LIMG Sector" button and on the next pop-up click "Yes".
6- Click "Encrypt" and on the next pop-up click "Yes".
7- Wait for it to finish, a pop-up will come saying its completed.
8- You will now have a new file called "ISO.BIN.ENC" (this is the converted PS2 game to PS2 Classic)

Note: When selecting the desired ISO on step 2, make sure to use ISOs that were built as ISO9660 with sectors of 2048 bytes. You can verify this with ImgBurn.

Then you should open the ISO with a hex editor and check the offset 0x8000 (sector 16), the standard ISO9660 Identifier (CD001) should be located exactly there, if there is other data at that point of the ISO, then probably you have an ISO that was built as binary, as a result it will have a different sector structure.


There are various method you can transfer the new "ISO.BIN.ENC" to your PS3, where you installed the "PS2 Classics Placeholder PKG", I will mention them here to give you an idea:

Method 1:

Use the "PS2U10000" directory structure provided to make a game update package. You just have to put the "ISO.BIN.ENC" on the "USRDIR" and use "ps3tools" to make a package of the whole directory structure.

If the size of the PKG is more than 4GB then you will have to split it using any of the tools available for that (they must have extension of .66600, .66601, etc... to be installed via multiMAN).

Method 2:

Just copy the "ISO.BIN.ENC" to your external USB Storage Device and paste it on your PS3 at "/dev_hdd0/game/PS2U10000/USRDIR/"

If the "ISO.BIN.ENC" size is more than 4GB then you must use other method.

Method 3:

Upload the "ISO.BIN.ENC" via FTP / multiMAN to your PS3 at "/dev_hdd0/game/PS2U10000/USRDIR/"


Thanks to aldostools for this information, I will eventually incorporate it in my guide, for now here you have it. Mistawes has confirmed here that the following steps WORK. They avoid the issue of reusing the same ContentID and rap for all the games converted:

1. Copy the rap of your base game (PS2) as a new random content id. eg. EP0000-NPED12345_00-AAAABBBBCCCCDDDD.rap
2. Copy the new rap to the RAPS folder of PS2 Classic GUI
3. Extract the files of the PKG of your base game (except CONFIG and ISO.BIN.ENC, they will be deleted/replaced anyway)
4. Launch PS2 Classic GUI, select the ISO and enter the new content id. eg EP0000-NPED12345_00-AAAABBBBCCCCDDDD (it should display the same KLIC of your base game)
5. Add the LIMG header and encrypt the ISO as ISO.BIN.ENC
6. Edit the PARAM.SFO on the extracted with the title of the PS2 title.
7. Copy the ISO.BIN.ENC to the base game
8. Rename the extracted folder with the new content id (EP0000-NPED12345_00-AAAABBBBCCCCDDDD), right click and select Make PKG
9. Install both raps (the original and the new created) using reActPSN
10. Install the PKG

In short: you copy the rap of your base game, rename it with a new (invented) content id/title id and encrypt the ISO and create the PKG using that new content id.


Since I understand that even when things have been simplifying in the recent days, it can be tedious to be moving, replacing, copying ISO files over the USRDIR of the PS2 Classics Placeholder. So, I have a proposed a PS3 homebrew application that when finished will allow the users to browse a list of PS2 ISOs located on your Internal / External hard disk drive and from there with a simple press of a button automatically do the moving / renaming process, so you can go back to XMB and play the game selected.

The good thing about doing this kind of application, is that it can be made to display game covers, information, etc as well. So at the end we would have a very organized list of our PS2 backups. The development of this application will be done mostly on weekends when I have the most free time. On week days I have university so I will not be able to work a lot on it, maybe add small modules and pieces of code. So keep using PS2 Classics Placeholder for a while, and most of all, enjoy playing PS2 on your PS3!!!


Update 2: PS2 Classics Manager v1.0 (Coming Soon)


I am currently doing kind of a flowchart for an upcoming application that will be called "PS2 Classics Manager", this application will handle PS2 ISOs easily and even display front / back cover, I will work on a custom game database file that will hold some information about each game (ex. Title, Year, Company, Genre, etc).

The planned application will work in conjunction with my PS2 Classics Placeholder.

Game list will be generated by scanning the PS2ISO directory located as in: "dev_hdd0/PS2ISO/[SLUS-20915] METAL_GEAR_SOLID_3_SNAKE_EATER/"

And the structure of each PS2 game would be as follows:


Now, the good thing about having the ISOs on the internal HDD is that my application would only have to "move" the file accordingly and keep record of it on a simple CONFIG.CFG (remember where it was located originally), in other hand, if we have the PS2 ISOs at external we would have to copy them and wait while it completes, split files would be easily supported as well.

I will start working on the application today, since I don't have university anymore for this week. Soon I will be posting Work in Progress information and probably some screenshots.

The core of this application will be my other homebrew "FBAlpha Retro Loader" one, so I don't have to start coding the application from scratch.

When finished it will be signed to run on CFW 3.40+ but of course some of you will have to re-sign it if it doesn't launch (I have tried to sign for all CFW, but I got tired of messing with signing stuff and ppl reporting issues , LOL)


Make the handling of PS2 game ISOs as simple as possible, this will avoid having a bunch of entries on the XMB.

Just having the PS2 Classics Placeholder + PS2 Classics Manager will be enough to start enjoying your favorite PS2 games.


I started working on this today, but since I am using one of my previous homebrew as base, I don't have to do as much code writing as if I started from scratch. So the most time consuming will be modifying / removing all the unneeded modules / functions and write the new ones.

A simple functional build will probably be available around Saturday, or maybe even tomorrow, depending on how I handle my free time.

Progress Update: I just compiled and ran the first test build of PS2 Classics Manager, at this moment the core is almost ready, I still have to write the modules to process internal / external PS2 games.

Someone said something about virtual memory cards, I considered this and now users will have the option to put them as in:


They will be moved / copied as needed when you select a PS2 game as active. Before I go to sleep here you have some of the stuff I've done...

  • Module to swap the Placeholder PS2 ISO is ready (Internal only for now). It will move the ISO.BIN.ENC to the Placeholder "USRDIR" directory and when you run the manager again it will be moved back to where it was (This is specific to the internal PS2 ISOS, in case of external ones they will be handled differently, but I will give details later).
  • Virtual Memory Cards are automatically copied from the game directory to the SAVEDATA directory, then when the game is switched back, they will be copied as well (I need to test and see if by doing this every game keep their data).
  • A copy of "COVER_FULL.PNG" (this is the cover displayed in the Game List screen) will be made as "PIC0.PNG" to the PS2 Classics Placeholder directory, so when the user select it on the XMB they can see what game is active (I will eventually improve this feature so users can customize this better).

Note: I am trying my best to bring this application to all of you as soon as possible but even when I said I would have it probably by this weekend, it will probably take me more time depending on the free time I have here. I have to study for some university tests and I have a few homework to do, but please be patient, I will eventually deliver what I have promised. Thanks everyone for understanding and your support.

  • Rewrote the module to move / copy files, now it will work on a separate thread and a progress dialog will be displayed to the user. In case of a unexpected error, it will be displayed as well. When this module is finished I will be ready to make a initial beta release of PS2 Classics Manager.
  • I confirmed that the memory cards included initially in every PS2 Classics PKG are eventually copied automatically by the PS3, and in case of the PS2 Classics Placeholder they get copied to "/dev_hdd0/home/*USER_ID_NUM*/ps2emu2_savedata/PS2U10000/". This means that no matter if you modify memory cards located at "/dev_hdd0/game/PS2U10000/USRDIR/SAVEDATA/" the PS3 will always use the ones at "/dev_hdd0/home/*USER_ID_NUM*/ps2emu2_savedata/PS2U10000/".

I will now make a final test to confirm this, and if I am correct, then VME files will be handled appropriately by PS2 Classics Manager. Will report soon with more updates! SeeYa!

From svenmullet comes a different approach to PS2 Classics alongside a video below, as follows:

I'm assuming you know how to encrypt ISOs to work with this, and you've already got a collection of ISO.BIN.ENCs floating around.

If you encrypt any ISO with the same key, the PS3 sees it as activated and runs it. PS2 ISOs need to be loaded from internal HDD, and I personally hate waiting for things to transfer over. Plus, I have a large amount of games/etc installed and appearing on the XMB, so naturally I organize things into albums or just let the XMB do it automatically with the square button. PS2 Classics will auto-organize into "PlayStation2" album.

So if you wanna be cool like me, make a template folder on your PC then either a) FTP into your "base" game installation on the PS3, or b) use aldostools and simply right-click "extract" on the pkg, and copy over:


These are the same files you will use with every PS2 Classics installation you make.

Now make some ISO.BIN.ENCs. (you know how to do this, remember?) Put each of them into a separate folder using this naming convention: NP[U=US, E=Eur, J=Jap]D[TitleID# of disc] so for instance Final Fantasy X is "NPUD20312". You really can call the folder whatever you want (within reason) because all the work is done by the PARAM.SFO, but for the sake of order, stick to proper naming conventions. Copy all files from "Template" into this folder, edit the SFO to reflect the correct title id and title, and make or download some cover art, specifically you need ICON0.PNG (320X176) and PIC1.PNG (1920X1080)

They must be uncompressed PNG at the stated resolutions or they will not show up. I go to google image search and use search terms "[game name/title id] 1920x1080" for the background (PIC1.PNG) and "[game name/title id] cover" for the cover art, then pixlr.com/editor/ for a free in-browser photoshop-like app to edit anything you need.

So, the final folder structure should be:


And that's it! You can either package this folder up and install it (You'll have to figure out how to do that, I don't bother making a package) or FTP transfer it directly into dev_hdd0/games/ I would suggest making all the folders first then transferring everything at once, because you need to do a Recovery Mode -> Rebuild Database for these to show up in XMB, and that removes any "album" customization, playlists, etc that you've done. A minor pain, but it is what it is...

Okay, I finally caved in a waited (like 10 minutes) for the package builder to do it's thing, made a package out of my handmade Need for Speed: Most Wanted folder. It installed fine, appeared on XMB and booted perfect! This is even easier than I thought.[/edit]

Anyway, after all the hard work, you boot to XMB and... voila! Home-made PS2 Classics:

PS2 Classics and Codebreaker Cheats Method

Allows you to use codebreaker with your ps2 classics, though there are some limitations- ie Final Fantasy games seem to have "hidden files" so they won't work. From arj1231:

To use codebreaker cheats open your game iso with ultraiso.

Download this ([Register or Login to view links] and [Register or Login to view links] and [Register or Login to view links]) and extract. now add the extracted files (boot.elf, codebreaker.elf, and system.cnf) to your iso, can just drag&drop into ultraiso. It will ask to overwrite SYSTEM.CNF/YES.

Your iso should have a file name SCUS_xxx.xx or something to that effect, extract it to desktop and add .elf extension and repaste it into iso.

So now your iso should have all original files + BOOT.elf, CB10.elf and your new SCUSxxx.elf, save and resign as you would ps2 classic

Now once you start your new game, it will automatically start uLe, so you scroll down to cdfs directory. hit O. now find the Codebreaker elf and hit O. Codebreaker starts.

Scroll over to Cheats and find your game and select your cheats you want to use. Press start and it should bring back to the main screen with the disc icon highlighted. press X to load disk, it will start ULauncher again.

Scroll down to cdfs directory and start you SCUSxxx elf file you created. Your game should load with the cheats enabled. I have tested this with SocomII, and Socom3.

Custom Made PS2 Classics for PS3 by Lo gi

Looks nice, I think, much better than Sony's offering, and also I demonstrate how to get the best performance (not nec. the best quality, but hey) by turning "off" screen mode It drops down to 480P native and runs faster.

Here's some samples you can drop your ISO.BIN.ENCs into: [Register or Login to view links] / [Register or Login to view links]

Finally, from crump comes a PS2 Classic CLI v1.0 Batch renaming, encrypting, decrypting, pkg-ing tool.

Download: [Register or Login to view links] (2 MB)

From the ReadMe file: This is a tool to utilize ps2classic, which converts PS2ISOs to PS2 Classic games. You are able to encrypt, decrypt, rename, and pack pkg (windows only. seriously, someone please release modified pkg tools? maybe?), and in bulk. say you have 100 ps2 ISO files in a folder and some subfolders, this tool will help you.

NOTE: Python 2.7.3 required. can't do pkg other than windows because can't find the modified source for package_make_npdrm...or pkg.py...

Usage: to see options: ps2ctool.py -h

all to process all ISO files in current folder.
rename To rename a file to and move it to the "Renamed" folder.
encrypt To encrypt a file to a specific target
decrypt To decrypt a file to a specific target

and for example, you want to know how to encrypt a file, type:

ps2ctool.py encrypt -h

Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!

Comments 716 Comments - Go to Forum Thread »

• Please Register at PS3News.com or Login to make comments on Site News articles. Thanks!

PS3 News's Avatar
#676 - PS3 News - 28w ago
Today PlayStation 3 developer Samson has ported the PS2 homebrew game Geotron and the PS2 utility MCMAN to PS3 (Cobra CFW) with details below.

Download: [Register or Login to view links] (25.1 MB) / [Register or Login to view links] (24.6 MB)

Geotron ISO For Cobra CFW

Another cobra autobooting blast from the ps2 scene Geotron.

GEOTRON version 0.5 for PS2. This is a beta version of a clone of XBox "Geometry Wars" for PS2. New features include 2-player mode, hiscore save, and major bugs fixed.


Another little tool from the ps2 days in autobooting iso format that cobra users might find handy..

Mount your ps2 mc's in the xmb and boot mcman to delete or backup saves to another mc, highlight a save and press start for options.

OdeFixUpdate v1.0 Beta from BiteYourConsole

Download: [Register or Login to view links] / [Register or Login to view links] (Mirror)

Rough translation: Many users of the Ode on Firmware console Superslim 4.55 and found quite a few problems to update their games, waiting for the user Pal0x releases a solution that ultimately we put on a pair of instructions to try to make it easier to prepare updates.

The application is simple to use, just enter the PKG update file in the program folder and launch the file OdeFixUpdate.bat.

The package will be extracted to a folder where the application will fetch the file EBOOT.BIN and PARAM.SFO elaborating, at the end of the two files will be stored in the folder extracted earlier.

Following re-create the file E3boot.ISO or in the case of Cobra Ode performed a series of applications in order to bring the right file for the start of our games, finally burn the image onto a Blu-ray single layer.

From magneto: Cobra team release of IRD parsing library

Note that this release is only for application developers. ODE users will not find any use of these files.

The Cobra Team has decided to release its IRD parsing library under a GPLv3 open source license. We hope that it helps other developers integrate IRD support into their application. On top of parsing v6, v7, v8 and v9 IRD file formats, a helper function was included that parses the ISO file structure to populate the list of all files in the ISO. It can be useful for listing iso files from an IRD and checking their MD5 hashes.

The IRD library can be downloaded from here: libird.rar

PS3 News's Avatar
#675 - PS3 News - 29w ago
Cobra ODE 2.0 Update FAQ by magneto and Cobra.cfg Config Tool by SDeath are now available, as follows:

ODE 2.0 Update FAQ

With the recent release of the Cobra ODE version 2.0, there has been a lot of questions asked here in the forums, and many of them were asked multiple times. This thread is to help everyone update properly to 2.0 and fix any issues they might encounter, without having to read through pages of threads to find the answer to their question.

Before asking any question on the forum, please make sure to read this thread carefully. We will keep this thread updated with all the frequently asked questions, so make sure to check it again for updates.

How can I update to the 2.0 release

You first need to update to the bootloader 1.3 which can be downloaded here: Cobra_ODE_BootLoader_v1.3.rar

If you do not update the bootloader first, then you cannot flash the 2.0 release. Once you have updated the bootloader, you can flash the MCU, FPGA1 and FPGA2 files in any order, as long as you do it one at a time and delete the fpga files after it has been updated.

Please refer to the appropriate section on the user manual to know how to flash them. Do not interrupt the process while it is flashing the bootloader or the FPGA to avoid a risk of bricking your device.

How can I see which Cobra ODE board revision I have?

You can open your console and you will see the version of the ODE written on the main Cobra PCB. If you do not wish to open the console, then you can try flashing the fpga1 images until you find the one for your device. You must of course first update the bootloader to 1.3, then you can flash the fpga1.dat file from the v3 board folder, if it fails immediately (shuts down immediately, and does not blink for 2 minutes like it's supposed to be).

Then you have a v4.20 or v4.30 board. Flashing the wrong fpga image will not damage your ODE in any way. The v4.20 and v4.30 boards will accept both the v4.20 and v4.30 fpga1 update, so if you try to update with the v4.20 fpga1.dat image and it works, you can then boot the PS3 with the switch set to PT mode.

If the PS3 does not detect the disc, then you probably have a v4.30 board. The fpga3.dat file is the same for all boards and will work regardless of your board revision.

After I updated the FPGA images, the LED does not turn on anymore when I power the PS3

If you update the FPGA images without updating the MCU image, then the light will not turn on. You can still update the MCU just put the file on your USB drive and try it.

I can't update anything, the LED never becomes purple when I power the PS3

Remove the power from the PS3 completely and wait a minute or two to make sure the PS3's power supply completely drains of power. Format your HDD with [Register or Login to view links] and copy the files again then try again.

After I updated, the PS3 freezes before it reaches the XMB

This is probably because you updated FPGA1, but not the FPGA3 file. Try to update it again.

When I put the fpga3.dat file on my USB stick, the LED flashes purple quickly but it doesn't blink for 2 minutes

This is probably because the fpga3 file has already been updated.

Cobra ODE used to allow us to downgrade to previous versions, can I downgrade to 1.9 ?

Yes you can, you will need to keep the bootloader on version 1.3 in order to downgrade the MCU and FPGA images. If you do not downgrade the FPGA1 and FPGA3 to their initial version, it will not work. It is not necessarily to downgrade the bootloader. You can find all the files you need here: Downgrade.rar

Can I update my ODE even if I'm not on a superslim console?

Yes, the 2.0 release is for everyone.

I'm on a superslim console, but on 4.50 or 4.53 firmware, do I need to update my PS3 firmware to use the 2.0 release?

No, you can use the 2.0 release on any PS3 firmware, on any PS3 console.

What is that Cobra ODE Bypass 455 v1.0 download on the website? Do I need it?

Those files and tools are only used for bypassing the new Anti-ODE security measures in the 4.55 PS3 firmware for superslim consoles. If you do not have a superslim, or if you have not updated to 4.55 firmware, then you do not need to download or use those files.

I'm on a superslim console, but on 4.55 firmware, how can I make my games work again ?

You need to download and read very carefully the anti-bypass manual: Anti-ODE_Security_Bypass_Manual_(English)_v1.0.pdf

You will also need to download the Bypass tools: cobra-ode.com/downloads/Cobra_ODE_Bypass_455_v1.0.rar

Do not forget to add the bypass.4.55=1 option to the cobra.cfg.

How can I configure the ODE? How can I edit the cobra.cfg file ?

To configure the ODE, you can change options in the cobra.cfg file. To edit the file, you can simply open it with NotePad or any other text editor. To "uncomment a line" means to remove the # in front of it.

Since I updated, my ps3 and ODE are freezing, what should I do ?

You should enable the mcu.underclock=1 option in the cobra.cfg

I copied the browser.iso file to the COBRA directory but i only see the manager, not the browser

You must enable the manager.type=browser in the cobra.cfg file. It is highly recommended to also enable the eject.on_selection=1 option at the same time.

I am using the browser but when I select a game, it will only show a video of the cobra logo, it doesn't load my games, what should I do?

You must enable the eject.on_selection=1 option in the cobra.cfg file, if you don't, the ODE waits for you to manually eject the disc in order to load your game selection.

Ever since I updated, I keep getting the 80010017 error, or the "Insert original disc" 8001003E error, or the bypass is not working for me on 4.55

If you are not on a superslim console on 4.55 firmware and you get those errors, or if you are and you used the bypass and are 100% sure that you have read and followed the bypass manual correctly but you still are getting those errors, then you need to use a different update for your ODE.

This issue is caused by a bug that we discovered shortly after the release. Only a small portion of ODE users are affected by it, but for those who are, they cannot run games anymore. The cause is a bug in the new FPGA image which is responsible for encrypting iso files on the fly. So far, only 4.30 board users seem to be affected, but it is not yet certain.

If you have this issue, you can try flashing the 4.20 FPGA1 image to your 4.30A board, and hopefully, it will fix the problem. The 4.20 FPGA image will work on 4.30 boards but it will have the side effect that PT mode will not work. You can however still use the software Passthrough-Mode from the manager or the browser.

If that doesn't work for you, or you are not on 4.30A board or you do not want to lose PT support. You can use this 2.0b release that we are making available to you in the link below, and flash your device with the FPGA image provided.

If you use the 2.0b version, your games should run again as they did before. This update will revert back to the original FPGA image and will use the old, non-optimized method for encryption. This means that you will not have the 220% performance increase in playback of IRD games.

MCU 2.0b release: [Register or Login to view links]

Can I use a BD-RE disc for the SWAP disc instead of a BD-R ?

While we are currently testing a variety of BD-RE brands to make sure compatibility is optimal, early reports indicate that the use of BD-RE discs will work with the bypass method. You can try and we are confident it will work. This can cut down costs as you can reuse the same disc when you need to generate a new SWAP iso image.

I updated to 2.0 but cutscenes from some IRD games are still lagging a little

The performance for IRD games has increased to 220% from MCU 1.9, but it is not yet as fast as using an original disc. Most IRD games will run smoothly now, but some games which use very high definition cutscene videos will still lag a little. It is however barely noticeable and much better than before.

Ever since I updated to 4.55 on my superslim, I can't use PT mode using the switch on the back. Why is that?

This is a bug in the 4.30A board revisions. You can use software passthrough mode however and that will work.

Cobra.cfg Config Tool

Download: [Register or Login to view links] / [Register or Login to view links] / [Register or Login to view links]

I have made a new program for you guys so you can create the cobra.cfg in a few easy steps.
It is setup with default settings and you can just click the options you want.

I have 2 sections, Basic Settings and Advanced Settings, only use the Advanced settings if you where told to do so by a member with more experience or if you know what you are doing.

All options have tooltips if you want to know more about what they do. By default the following is set:

  • COBRA Browser
  • Eject Disc On selection in Browser/Manager
  • Add "Return to Manager" in XMB
  • MCU Underclock

For users on a 4k and on OFW 4.55 enable that option too in the basic settings. If you want to use the Manager just enable that.

After setting the right settings press Generate and select the destination of the cobra.cfg so the COBRA folder on the external HDD, if it already exist it will be overwritten.



  • Initial Release


  • Bugfix - Small typo in the code, it's fixed in v1.1


  • ARMITAGEIII Limited Edition


  • Last save location is now saved

Update: 8 - 3 - 2014: Cobra ODE News - Update

We are pleased to announce the release of the 2.0 fw for 5.10B QSV pcb's. This brings the new version of the v5 QSV functionality on par with the v3 and v4 / v4 QSV pcb's. We have included a brief txt explaining the upgrade process for the v5 QSV board. The user manual will be updated shortly with this information.

For users on 4.55 using the 4000 series PS3 and the 5.10B, please ensure that you also install the JTAG adapter pcb and applicable FFC cables to controle the drive cover switch. The 4.55 bypass software and documentation in the downloads section is also relevent to your pcb version.

Download: Cobra ODE (V5.10B) FW V2.0 * For PCB v5.10B only *

Finally, from Samson comes a PADTEST.ISO for Cobra CFW with details below:

Download: [Register or Login to view links]

I made a simple iso that autoboots into an old ps2 padtest elf..


README: PS2 ELF for testing Playstation 1 Original/Dual Analog/Dualshock 1 and Playstation 2 Dualshock 2 controllers.

Tests the digital and analog functions with a 0-255 scale.

To test vibration, hold 'triangle', then move the left joystick down for the strong motor (that seems to have 96 positions), or press up and down on the directional pad for the weak motor (that has 2 positions).

PS3 News's Avatar
#674 - PS3 News - 30w ago
28 - 2 - 2014: Cobra ODE News - Update

COBRA ODE 2.0 fw Release for V3 and V4/V4 QSV Cobra PCB's including OFW 4.55 Bypass

We are pleased to present for release the Cobra fw 2.0 which has many new features and also initial support for OFW 4.55. Whilst the support for OFW 4.55 is not as convenient as on previous OFW's, it provides a solution for those who accidentally updated or wish to use 4.55 directly on SEN.

We suggest that users remain on 4.53 or lower if they wish to benefit from the full convenience of an ODE solution. That being said we are researching other possible methods for compatibility with the 4.55+ firmwares and will keep our users posted through the news on this site and various other forums.

Before using the Cobra ODE kindly refer to the 4.55 Bypass manual carefully. Please be sure to follow the prerequisite steps and ensure that you have updated the firmware on the ODE hardware properly first. Kindly note that 1 wire must be soldered to the drive door, which is detailed in the updated installation manual. The newly launched V5 QSV Cobra does not require a wire to be soldered for controlling the 4k series drive door, since it is bundled with a special adapter which takes care of this functionality via the included ribbon cables.

In addition to the 4.55 OFW support, we have included many new features which are sure to excite users and demonstrate the power of the Cobra ODE.

New features in 2.0 fw:

  • On the fly generation of browser menu system (no pc app required)
  • LED configuration
  • Full 4k auto eject system added
  • XMB enabled passthrough system added, use of hardware switch not required
  • Configuration of eject delay added
  • AES performamce increased by 100%
  • Disc dumping via manager added
  • + Many other tweaks and performance benefits added

We have also freshened up our user manauls to make installation and detailing of the full functionality of the Cobra ODE easier to understand.

As you can see the 2.0 fw release is a massive leap forward. You can be sure to expect more from Team Cobra in the months to come.

2.0fw for V5 QSV users will be released in the following week... Read "User Manual v2.0" and follow Bootloader update procedure prior to use FPGA update from MCU v2.0. Thanks for your continued support.


Finally, from SDeath comes an updated Easy Batch Generate/Merge COBRA ISO's Tool (Including OFW 4.55 ISO's + Swap Disc) with direct download links below.

To quote: And a whole new update of my tool came together with the 2.0 COBRA ODE update. To make sure you can convert all those games for the 4.55 bypass more easily. And also supports the merging of the games dumped by the new Manager.

Download: [Register or Login to view links] / [Register or Login to view links]

Changelog: 28-02-2014 (dd-mm-yyyy):

  • Updated to latest version support files released today by the COBRA Team.
  • Added support for OFW 4.55 Bypass batch ISO creation.
  • Added support to generate the OFW 4.55 Bypass SwapDisc.
  • Added support to batch merge game ISO's either dumped using the new 1.6 COBRA Manager, or split with genps3iso.
  • Added Check to see if source folders are empty.
  • Generated a exe from the script.

Only people with a 4k PS3 and are on OFW 4.55 need to use the swap disc and will need to rebuild their games!!

All others don't need to do this, they can still update to COBRA ODE 2.0 firmware to enjoy the new features.

Tutorial: How to Dump a Game with Cobra Manager 1.6

  • Connect a FAT32 USB drive to the front ports of the PS3.
  • Uncomment this line in the cobra.cfg: disc.unsupported=ignore
  • Start the Manager (this won't work on the Browser).
  • Switch to the disc you want to dump (also unsupported discs can be dumped when switched when the manager is running).
  • Press triangle.

After it's done you can use the Easy Batch Generate/Merge COBRA ISO's Tool (Including OFW 4.55 ISO's + Swap Disc) to merge them again into one ISO file.

Known Issues:

I've seen crashes after it's done dumping, you need to hard reboot the PS3 to get it to work again.

Tutorial: How to Prepare the HDD (with Preconfigured Packages)

This will replace the Tutorial: How to Create the Cobra Browser, with the 2.0 update of the Cobra ODE, things have changed how the Browser behaves and how it's created, it all does it on the fly.

So therefore a Browser Tutorial is not needed anymore, but to make things easy for you I have setup 3 pre-configured HDD packages to prepare your HDD, this way you are sure all the needed files are there on the HDD.

The Packages:

*Stealth will show the Cobra Browser in the Games and Video section of the XMB, SuperStealth will only show the Cobra Browser in the Video section.

All 3 packages include the Browser and the Manager, from update 2.0 onward it's very easy to switch between the two, just a small edit in the cobra.cfg. The differences between the packages is just how the cobra.cfg is setup. The Manager now also supports disc dumping so that's why I think it should also be included in the Browser packages.


01 - Download one of the above packages.
02 - Extract the contents to the root of the HDD.
03 - Copy the games to the folder PS3_GAMES.
04 - Adjust the cobra.cfg to your needs, on default it will show the Return to Manager option in the XMB, the other options like 4.55 or LED disable you need to adjust yourself.
05 - Safe eject the HDD and connect to the external PCB USB port. Done!


If you downloaded one of my Browser packages you can switch easily to the manager by changing this line:

[Register or Login to view code]

To this:

[Register or Login to view code]

And if you used my Manager package you have to do the revers to switch to the Browser so change this line:

[Register or Login to view code]

To this:

[Register or Login to view code]

  • File versions used: Browser/Manager 1.6, cobra.db 28-02-2014.

PS3 News's Avatar
#673 - PS3 News - 30w ago
26 - 2 - 2014: Cobra ODE News - Information

We are now close to release of the 2.0 firmware for the V3, V4 and V4 QSV versions of Cobra. We expect to release the 2.0 firmware this weekend. The release includes support for 4.55 OFW on 4k consoles and all functionality previously announced for fw 2.0

Furthermore, we are now shipping the 5.10B QSV Cobra which is more compact and runs on accelerated hardware giving faster performance. The Cobra 2.0 firmware will be released for 5.10B next week.

All future firmware updates will be released in parallel on V3, V4 / V4 QSV and V5 / V5 QSV hardware.

Photos of the new V5.10B hardware pack, will be published tomorrow.

Update: Cobra ODE MCU v2.0 Released

The Cobra Team as promised has released a new update for users with Cobra ODE version MCU 2.0. The new update is for users with problems with the console and 4k with ofw 4.55. In waiting for an official guide below is the changelog and downloading:

Changelog: COBRA ODE 2.0

  • FPGA 1: Increase AES encryption module performance to 220% faster than previous release
  • FPGA 3: Fix disc dumping corruption and increase disc dumping performance by 100%
  • Added support for manager.type=browser configuration option to autogenerate browser
  • Added support for software-emulation Pass-Through mode
  • Added support for bypass.4.55=1 configuration option to bypass the 4.55 superslim security
  • Added support for game.pt=1 configuration option to force software-emulation Pass-Through
  • Added support for updating PS3 firmware without needing to switch to PT mode
  • Added support for eject.add_menu=1 configuration option to add a menu to return to manager when game iso is loaded
  • Added support for eject.delay option to specify delay in milliseconds before reinsertion of disc after it has been ejected on QSB systems
  • Added support for manager.on_eject=0 configuration option
  • Added support for mcu.underclock configuration option
  • Added support for leds.disable configuration option to disable specific LED colors
  • Various stability fixes


  • Fix support for flashing FPGA images
  • Add support for flashing 2.0 firmware


  • Add disc dumping capabilities
  • Add support for Passthrough Mode

Download: Cobra ODE Manager v 1.6 / Cobra ODE Bootloader 1.3 / Cobra ODE Database (28-02-2014) / Cobra ODE MCU 2.0

Warning: Downloading and use is at your own risk without an official guide. Only users with console 2k and 3k users can update while the console 4k users must wait.

redvaleyard's Avatar
#672 - redvaleyard - 30w ago
I got a Cobra Usb dongle last week on the strength of it being apparently plug in and play and non-invasive procedure for the console. I've found it isn't easy.

As a total novice I need a step by step idiot proof guide how to hack the ps3 so I can actually use it. I've so far installed all the drivers and latest 6.0 firmware on the dongle and come to a grinding halt.

I've downloaded all the files and followed the user manual but am stuck. In various forums I've read about installing flashing devices but I thought using the Cobra you don't.

I need to open the console. I need massive and simple help on what to do. I'm on a PS3 original 60gb uk pal with latest OFW 4.55 installed. Any help gratefully received.

Remember I'm a complete novice and need simple untechnical "do this", "do that" instructions. Thanks in advance.

Sponsored Links

Sponsored Links
Sponsored Links

Sponsored Links

Advertising - Affiliates - Contact Us - PS3 Downloads - Privacy Statement - Site Rules - Top - © 2014 PlayStation 3 News