Page 49 of 128 FirstFirst ... 394849505999 ... LastLast
Results 481 to 490 of 1278

Thread: Cobra USB - PS3 Dongle Runs Blu-ray & PS1 iSOs and PSP Minis

  1. #481
    Join Date
    Apr 2005

    PS2 Classics Keys & Cobra 6.0 4.30 PS3 CFW Payload by MiralaTijera Out

    Following up on his previous update and Flat_z's release earlier today, Spanish PlayStation 3 developer MiralaTijera has now made available the PS2 Classics keys and Cobra 6.0 4.30 PS3 CFW payload from the DRM-infected USB dongle by the notorious scene profiteers.

    Download: PS2 Classics Keys / Cobra 6.0 4.30 PS3 CFW Payload (via / Cobra 6.0 4.30 PS3 CFW Payload (Mirror)

    For those naive, it's no coincidence these PS2 keys and Cobra payload are just now mysteriously being released as the PS3 capitalistic pigs Max Louarn, Paul Owen and Gary Wayne Bowser (aka GaryOpa) ready their next ripoff product for market this month and (once again) their True Blue cycle repeats on even more unsuspecting victims unfortunately.

    To quote, roughly translated: payload 4.30 cobra 6.0 xDDDDDDDD

    base = 0x8000000000540000

    MiraElCobra what next?

    Of the keys to what Flatz
    VMC 64 E3 0D 19 A1 69 41 D6 77 E3 2E EB E0 7F 45 D2
    ATA SEED D9 2D 65 DB 05 7D 49 E1 A6 6F 22 74 B8 BA C5 08 83 84 4E D7 56 CA 79 51 63 62 EA 8A DA C6 03 26
    ECDSA PUBLIC 62 27 B0 0A 02 85 6F B0 41 08 87 67 19 E0 A0 18 32 91 EE B9 6E 73 6A BF 81 F7 0E E9 16 1B 0D DE B0 26 76 1A FF 7B C8 5B
    DataKey 10 17 82 34 63 F4 68 C1 AA 41 D7 00 B1 40 F2 57
    MetaKey 38 9D CB A5 20 3C 81 59 EC F9 4C 93 93 16 4C C9
    Mira Miraaaaaa Miraaaalaaaaaaa
    Here the dongle detects the payload who send the instruction from the lv2 (0xAAAA 0xC0BA) and them one loop with a send cmd to the dongle...
        seg010:80000000007F0830 ld r0, 0(r9)
        seg010:80000000007F0834 ld r11, 0x10(r9)
        seg010:80000000007F0838 mtctr r0
        seg010:80000000007F083C ld r2, 8(r9)
        seg010:80000000007F0840 bctrl
        seg010:80000000007F0844 ld r2, 0x90+var_68(r1)
        seg010:80000000007F0848 li r11, -1
        seg010:80000000007F084C mr. r4, r3
        seg010:80000000007F0850 beq loc_0_80000000007F0A58
        seg010:80000000007F0854 lis r0, -0x5556 # 0xAAAABAC0
        seg010:80000000007F0858 lwz r9, 8(r4)
        seg010:80000000007F085C mr r30, r4
        seg010:80000000007F0860 ori r0, r0, 0xBAC0 # 0xAAAABAC0 --> USB PID ?
        seg010:80000000007F0864 cmpw cr7, r9, r0
        seg010:80000000007F0868 bne cr7, loc_0_80000000007F0880
        seg010:80000000007F086C ld r9, off_0_8000000000340228 # unk_0_80000000002CF940
        seg010:80000000007F0870 li r0, 1
        seg010:80000000007F0874 li r11, 0
        seg010:80000000007F0878 stw r0, 0(r9)
        seg010:80000000007F087C b loc_0_80000000007F0A58
    From haz367: Just for testing this payload..loaded the "payload.bin" using his 4.31CFW and Core 2.6.5 /update4 and it seems to inject payload into kernel, comparing lv1/lv2 dumps is a mess cuse it's always different.. log of payload loaded into kernel.. then what.. lol.. back to my psu.
    Core: Mount dev-rewrite Result (0x00000000)
    Core: Payloader Called!!! Init subsystem
    Core: Payloader copy and place on kernel the payload
    Core: Payloader now place the hook on kernel
    Core: syscall 36 is UP and all is OK, continue
    Finally, from ing_pereira (via

    Here I leave the source published by Flatz (Proof of concept of ps2 classics decryption, the. ENC, the encrypted virtual memory cards. VME and CONFIG file tweaks) with notes in English and the script. Py python already prepared with keys of miralatijera again who does or leaves much of the work.

    Use: <ISO.BIN.ENC or CONFIG or SCEVMC*.VME> <klicensee_del_juego.bin>
    The binary klicensee no texts as always, I remind you need python and well maybe the code has errors at some point but this desconosco it since I am still in the process of testing a classic ps2.

    This advanced for devs and theme they want to take a look at the issue of ps2 classics and encryption and decryption. Flatz With its analysis and work on the subject, miralatijera by keys.

    [imglink=|PS2 Classics Keys, Cobra 6.0 4.30 PS3 CFW Payload by MiralaTijera Out][/imglink]
    [imglink=|PS2 Classics Keys, Cobra 6.0 4.30 PS3 CFW Payload by MiralaTijera Out][/imglink]
    More PlayStation 3 News...

  2. #482
    Xplic1T Guest
    Nice so hopefully, Dean can now back this feature into the next MM so that we can finally get Ps2 support out of your 60gb consoles.

  3. #483
    azoreseuropa Guest
    Wait.. it did say PS3 systems!!! Including PS3 slim too? I hope so.

  4. #484
    pedro800 Guest
    another job for deank

  5. #485
    Xplic1T Guest
    Nope no slim support only 60gb (which is what the cobra payload was designed to exploit)

  6. #486
    beradd Guest

    MultiMan holding select not working Help

    I have searched for awhile and i cannot figure out how to launch stealth Mm 4.20.04 on Rogero 4.30 v 2.05 after loading a game by holding select. I have to restart the unit then i may go back to the toolbox and open it then press select for stealth or start to update and load Mm stealth. Holding select does nothing for me did i go wrong somewhere or just misunderstanding.

    I used multiMAN ver 04.20.00 BASE CEX. Then multiMAN ver 04.20.04 UPD CEX and last I Used multiMAN ver 04.20.04 UPD STEALTH.

    Installed under MultiMans method #1 Using DeanK installPKG noREBOOT pkg from Rogero 4.30 v 2.05 and report_data from multiMAN version 04.20.04 Update Stealth. I have also tried Method #2 and renaming the report data nothing changes.

  7. #487
    Liongooder Guest
    I have the same problem,the only solution is to install the standalone [* Install Package Files] & enter srealth multiman by pressing SELECT, at least its much better than restarting every time.. you wanna change the game,whenever you wanna go online delete the [* Install Package Files] its the only way to go around it, maybe Deank will release a new update to fix this problem.

  8. #488
    DEUSC2D Guest
    Hiya, you need to install stealth mM base first then the UPD stealth mM. It works on every CFW I tried.

  9. #489
    Join Date
    Apr 2005

    PS2Classics - PS2 Classics Decryption and Encryption GUI Arrives

    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: ps2classicv1.rar / PS2 Classics GUI (Latest Version) / PS2 Classics GUI (Test Version) / PS3Tools Collection v2.2.2 / rap2klicensee.rar (Copy to cygwin bin dir. Command: rap2klicensee rap out_klicensee) / Xpert v2.rar / ps2_to_ps2classic_tools.rar (30.5 MB) / Premade .PKG for FFX and Premade .PKG for FFX II by geokhentix (with the graphics, sound, modified PARAM.SFO for remoteplay and the title alongside Klicensee and .rap included) / PS2 Classic to PS3 Conversion Compatibility List / GIT / Noob Tutorial to Convert PS2 Games by kristijan1001 / PS2Classics GUI v2.0 / ps2classics.rar 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 (update_vmc_hashes.exe (Compiled Version)) to update a hash table inside decrypted virtual memory card:
    import sys, os, struct, hashlib
    if len(sys.argv) < 2:
    	print 'usage: <VMC file>'
    def calculate_sha1(data):
    	return hashlib.sha1(data).digest()
    file_magic = 'Sony PS2 Memory Card Format'
    segment_size = 16384
    segment_count = 528 # don't count the last segment for PS3
    file_name = sys.argv[1]
    with open(file_name, 'rb') as in_file:
    	data_size = segment_count * segment_size
    	data =
    	if data is None or not data.startswith(file_magic):
    		print 'Error! Invalid .VMC file.'
    with open(file_name, 'wb') as out_file:
    	segment_hashes = ''
    	for i in xrange(segment_count):
    		segment_data = data[i * segment_size:(i + 1) * segment_size]
    		segment_hashes += calculate_sha1(segment_data)
    	segment_hashes = segment_hashes.ljust(segment_size, '\x00')
    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 ( on_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: GTASA_ps2classic-klics.rar

    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:

    ps2classic d [cex/dex] [klicensee] [encrypted image] [out data] [out meta]
    ps2classic e [cex/dex] [klicensee] [iso] [out data] [real out name] [CID]
    ps2classic vd [cex/dex] [vme file] [out vmc] [(eid root key)]
    ps2classic ve [cex/dex] [vmc file] [out vme] [(eid root key)]
    ./ps2classic e cex gta_vc.key ISO.BIN ISO.BIN.ENC_mod ISO.BIN.ENC UP9000-NPUD20552_00-0000000000000000
    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:

    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: 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: how_to_dec_enc_ps2classics_capcpsx.rar (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 "" 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 (
    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 "" 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 ( (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 "" 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"

    DECRYPTING THE PS2 CLASSIC (GUI by aldostools)

    * coming soon...

    ENCRYPTING THE PS2 CLASSIC (GUI by aldostools)

    * 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: LIMGpatcher_v1_capcpsx_[beta].zip (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: ps2_to_ps2classic_tools.rar (30.5 MB) / ps2_to_ps2classic_tools.rar (Mirror) / ps2_to_ps2classic_tools_v2.rar (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 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 (uLe-CB10.rar and PS2 Tools and CBv92_GH_DAY1_ELFLDR.7z) 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: / PS2 CD-Ripping for Dummies.pdf

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

    Download: (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

    Usage: to see options: -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: encrypt -h

    [imglink=|PS2Classics - PS2 Classics Decryption and Encryption GUI Arrives][/imglink]
    [imglink=|PS2Classics - PS2 Classics Decryption and Encryption GUI Arrives][/imglink]
    [imglink=|PS2Classics - PS2 Classics Decryption and Encryption GUI Arrives][/imglink]
    More PlayStation 3 News...

  10. #490
    beradd Guest
    I have installed mm base first and i can get it to load a back up its just after i quit back to xmb I cannot get mm stealth to load to choose another backup only after restart can i choose a new back up to load.

    Am i mistaken or was there a fix in the newest update for a no reboot?

Page 49 of 128 FirstFirst ... 394849505999 ... LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts