Sponsored Links

Sponsored Links

PS2Classic Final with Source Code Arrives for PS2 Classic Games on PS3

Sponsored Links
92w ago - Following up on his previous release, this weekend PlayStation 3 developer IngPereira has made available PS2Classic Final with source code for playing PS2 Classic games on the PS3 entertainment system.

Download: [Register or Login to view links] / [Register or Login to view links] / [Register or Login to view links] (3.1 Expert with PS2 CDVD plugin) / [Register or Login to view links] / [Register or Login to view links] / [Register or Login to view links] by CrUmp / [Register or Login to view links] by u$er / [Register or Login to view links] by DEREKTROTTER

Now it doesn't need root key to vmc stuff and now vmc decryption and encryption is working great, added ISO9660 checks and LIMG check and creation. Thanks to flatz, aldo and many others.



[Register or Login to view code]


[Register or Login to view code]

To quote, roughly translated: Good friends here I leave the last revision PS2Classic with the new changes and additions by me with the help of Flatz and aldo.

PS2Classic Final Changelog:

  • ISO9660 Check
  • LIMG Support (Check / Creation)
  • VMC Decryption / Encryption fixed with the help of flatz by making new py script to rehash stuff so i can port it and now without. the need to use a root key to encrypt or decrypt your vmc's, thanks to aldo too by helping me in the process.
  • Now you see the progress being maded by decryption or encryption, so is more easy to wait.

Deciphering virtual memory card

[Register or Login to view code]

Encrypting virtual memory card

[Register or Login to view code]

It will rehash every change in the blocks and now it should work. About encrypting and decrypting ISO.BIN.ENC or CONFIG nothing changes about user commands because all the change was internal, so is the same.

If you don't want to use this cmd version is better to wait to the new version of Aldo Gui tool because it will have this added and some better gui improvements. Thanks to flatz, aldo and many others helping in the process.

Here also included something for those who want to modify or ripearlas isos more easily and are functional in the PS3. The process is very easy and simple using Expert 1.3 since the 2.0 version tends to have flaws with these images ISO9660 corrupting and ends.

Ripping or modification of any PS2 game

1. Crack the ps2classic ISO.BIN.ENC with great command line or GUI aldo.
2. Expert Runs 1.03 and continues to work the following order:

  • Extract LBA
  • Extract files (It will extract every file from the game in a folder with the iso name)

Now you can make your changes to the game(But obviusly you cannot just delete stuff because the LBA has an order you need to make some dummy file and rename it to the file you want to delete for example), you can mod everything too if the game have some modding tools for sure like gta sa, vc, etc.

  • Rebuild files (Now it will make a ISO with the game folder extracted previusly modified)
  • Rebuild LBA

3. Just encrypt that Game ISO modified with new tools like this new ps2classic command line tool or with new Aldo gui Ps2classic tool with new changes (Because this tools will now remake the LIMG section too). Now use the new ISO.BIN.ENC on the PS3 and check your changes.


From CrUmp comes a PS2 ISO Renaming Tool called PS3CTool v1 (linked above) for PS2Classic v 1.0 with details below, as follows:

I only test with my mac. if you install python 2.7 on windows this should work too. i don't know if it's ok to put key file in this, so I didn't include it. put your ps2.key file in the same location, and include this folder in your $PATH like:

[Register or Login to view code]

PS2 ISO Renaming Tool for PS2classic v 1.0 - PS3Classic: To encrypt PS2 ISO to PS2Classic image.

The best way to play your PS2 games on your PS3 console is to convert them into PS2 Classic Games. With Multiman and PS2Classic container, you can have unlimited PS2ISOs loaded into your PS3. With [gameID] Game Title naming convention, Multiman will download the game cover if avaliable.

This tool finds gameID from within PS2ISO, and compare with online database to rename the ISO file names

This script works with ps2classic command line tool to make it more convenience to convert mass ISOs.


[Register or Login to view code]


[Register or Login to view code]


[Register or Login to view code]


To rename ISO file with sonyindex.com database entry, in '[DISCID] FILENAME' format

ALL: in a folder to process every ISO under that folder, including subfolders. It will move ISO files to current folder, and re-name iso filenames against the database entries.

Finally, from u$er comes some proper PS2Classic Tool binaries (linked above) who states the following:

Hey there, i've compiled a set of PS2Classic binaries for you based on the latest changes. if you don't like using cmd-line apps, you can replace the one in PS2Classic GUI with this one.

[Register or Login to view code]

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

Comments 1212 Comments - Go to Forum Thread »

• Please Register at PS3News.com or Login to make comments on Site News articles.
#617 - PS3 News - 64w ago
PS3 News's Avatar
Following up on their previous announcement, today Gary Wayne Bowser (aka GaryOPA) and Max Louarn's new Cobra pitchman magneto released the official Cobra USB source code and updated Cobra.db database with the same old song and dance below, as follows:

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

A few days ago, STLcardsWS sent us a request, asking if we could release the source code of the Cobra USB dongle.

Today, we are fulfilling this request with a release of the full source code. We are releasing the entire source code under the GPL license.

You will find an overview.txt file which explains the content of each directory, and a readme.txt file in the cobralib subdirectory which explains its API and how to use it.

The source code is massive, and represents countless hours of work, containing 33,346 lines of C code, 5,981 lines of C++ code, 2,728 lines of assembly code and 35,530 lines in header files. We are sure that you can make good use of it, in part or in whole, within the community.

We hope that this release will be useful to the PS3 scene as a whole and that some of our exclusive features can be ported to the new and free custom firmwares.

As for all those haters out there who found the announcement of this effort as a new pretext to show your hate towards us, let it be known that this is not a PR stunt as you seem to think, this idea came from STLcardsWS, writer for psx-scene and dashhacks, who sent his request to us, and we accepted it.

We have no obligation to release the source, and if you don't want or like it, then simply don't download it. We are saddened to see people still finding ways to complain no matter what we decide to do. Even if it is for the scene that we do it. It is truly sad to see some people unable to show any other emotions than hate and ungratefulness.

Here is an update to the cobra.db database. It (cobra.db and supported games in CSV format) will be made available on the Web site shortly.

#616 - vnguyen972 - 64w ago
vnguyen972's Avatar
I cannot seem to be able to install 4.50 Base... I mean it installed but when I run it, it says the installation was incomplete... install the BASE or FULL, what did i miss? I thought I installed the Base from the link above. Please help!

#615 - PS3 News - 64w ago
PS3 News's Avatar
Today PlayStation 3 developer deank updated multiMAN to version 04.50.00 BASE (20131003) with the changes below, as follows:

Download: [Register or Login to view links] (110.36 MB) / [Register or Login to view links] (31.7 MB) / [Register or Login to view links] (132 MB - Mirror) / [Register or Login to view links] (31.65 MB)

  • multiMAN ver 04.50.00 BASE CEX (20131003).pkg
  • multiMAN ver 04.50.00 BASE DEX (20131003).pkg
  • multiMAN ver 04.50.00 STEALTH (20131003).zip
  • Showtime 04.03.536 [CEX].pkg
  • Showtime 04.03.536 [DEX].pkg
  • Added support for 4.50CFW
  • Disc-less mode: Icon changed from BD disc to "folder icon"

Update is available online within multiMAN and in web column. Tested on FAT 80GB PAL PS3... all good.

Here are all mmTOOLS updated to support 4.46DEX and 4.50CFW (CEX):

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

  • lastGAME 8.0
  • lastGAME 8.0 [SINGSTAR replacement]
  • gameDATA 8.0
  • bdRESET 8.0
  • stDISC 6.0
  • installPKG 2.0

All tools are also compatible with (Cex/Dex) CFWs 3.55C/D, 4.21C/D, 4.30C/D, 4.31C, 4.40C, 4.41C, 4.46C/D and 4.50C.

Available also in mM's WEB column.


  • lastGAME now support BD-MIRROR option (internal/external).
  • lastGAME 8.0 [SINGSTAR replacement] requires updated multiMAN. mM will look for lastGAME-SS and if found it will use it. I find it very convenient, because the "Load Last Title" icon is always on top, next to the BD disc icon.

And the updated multiMAN (you need it only if you plan to use lastGAME [SingStar replacement]):

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

MultiMAN 04.50.00 FULL repacked by StevenTJ


  • Added support for 4.50CFW
  • Disc-less mode: Icon changed from BD disc to "folder icon"

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

#614 - sesjse - 64w ago
sesjse's Avatar
03 - 10 - 2013: Cobra ODE News - Update

COBRA ODE v1.4 firmware is now available in the downloads section (attached below). In the 1.4 update, the maximum number of files per drive has been increased from 128 to 500 files.

Due to popular demand, we have also added support for a new cobra.cfg configuration file which allows you to set the ODE to disable the use of the manager, or to return to manager mode after each reboot. Please refer to the user manual for more information on the cobra.cfg configuration file.

The update also fixes a small bug with some HDD drives, introduced in the previous 1.3 firmware. The bootloader has also been updated to v1.2 to fix HDD support. Please refer to the user manual for information on how to update your device.

The COBRA manager has been updated to fix a freezing issue and to increase the limit of games to 500 in order to match the new MCU limits.

The third-party library has being updated to reflect that iso limit increase as well. A small API change has been made, please refer to the Changelog.txt for more information.

Thanks for your continued support.

  • Cobra ODE BootLoader v1.2
  • Cobra ODE MCU v1.4
  • Cobra ODE Manage v1.3
  • Cobra ODE Library v1.4
  • Cobra ODE User Manual (English) v1.4

We forgot to mention that BootLoader v1.2 give you the option to downgrade MCU firmware to previous version.

03 - 10 - 2013: Cobra ODE News - Update

We forgot to mention that BootLoader v1.2 give you the option to downgrade MCU firmware to previous version.

And here is a list of change log for every download item.

Cobra ODE Bootloader v1.2 Update.

[Register or Login to view code]

Cobra ODE MCU v1.4

[Register or Login to view code]

Cobra ODE Manager v1.3 Update:

[Register or Login to view code]

Cobra ODE Library 1.4 Update (This is for Homebrew Developer's only - not for end user)

[Register or Login to view code]

#613 - PS3 News - 64w ago
PS3 News's Avatar
Today magneto states that the Cobra USB DRM dongle produced by Max Louarn and marketed by Gary Wayne Bowser (aka GaryOPA) is going open source now that they have their new ODE cash cow, just as they did with the True Blue DRM-infected dongle and countless other projects they profited on from the PS3 scene that should have been free and open-source to begin with.

Download: [Register or Login to view links]

Below are the details, to quote from the overview.txt document:

Compilers needed:

- The toolchain at bsc.es/computer-sciences/programming-models/linux-cell is needed.
Cobra is compiled with ppu-gcc version 4.1.1. It is unknown if other versions will work.

- Other toolchains are known not to work. Mainly, due to incompatibilities with cryptcode, and with the macros at lv2/include/patch.h,
as well as with some asm code. Porting cobra to other toolchain would be a matter of transalitng those files to the new toolchain.

- sdcc, to comopile the i8051 binaries. Version 2.8.0 is used. It is unknown if a different version will cause any problem.

- sony sdk, to compile netiso and cobralib. Any version is supossed to work.

- gcc: (linux, mingw32, cygwin, etc), to compile the pc tools. these tools usually assume a little endian system like x86/x86_64

Overview of directories.

+ cryptcode
----+ include: include files with macros to encrypt functions
----+ src: the source code to decrypt functions (ps3)
----+ tool: the tool to encrypt the functions (pc)

cryptcode is a tool to encrypt functions with the purpose of obfuscate things a bit.
Additionally, it has the "suicidal" feature, which makes a function code to be destroyed after returning,
which is intended to be used on initialization functions that are not further used.

+ debug
----+ include
----+ src

Debug files to printf over lan. It also has patches to redirect kernel printf and the ttyWrite syscall to the library.
Debug library also works in ps2 emulator mode.
The files here are intended for debug phase only, and they are not linked when DEBUG is not defined.

+ lv1
----+ include
----+ src

Files for hypercalls and lv1 related functionality.

+ lv2
----+ include
----+ src

The lv2 kernel cobra "sdk".
It contains the defintions of a bunch of lv2 kernel functions for all kind of functionality (io, memory, processes, threads, modules, synchronization, etc).
The file symbols.h has the addresses of the functions. Some symbols have only been resolved for 3.55.

+ lv2gen

Tool to merge stage0 and stage1 with lv2 kernel.
To compile stage1, original encrypted lv2_kernel.self of 3.55 must be placed in this directory.
This tool requires failoverflow tools to be installed and be on the path.

+ stage0_file

Stage 0 of cobra, merged along with stage1 inside lv2_kernel.self.
It just changes the protection of lv2 kernel memory and then jump to stage1 (0x7f0000).

+ stage1_file

Stage 1 of cobra, it loads and decrypts stage 1.5 from cobra.
The current code is a bit difficult to understand, but it is basically a very simple virtual machine
with 4 opcodes and some obfuscation, that receives the opcodes from cobra usb. Operations end in a xor with a table.
The small vm code does stage 1 integrity via the md5 functions of lv2 kernel, and it also checks that some functions of the kernel are untouched.
It is intended as a first barrier against attackers, more protections are in stage 1.5.

Because of its "exotic" way of working, any code change or compiler change will break the code, it was not intended to be modified.

+ stage1.5
---+ gen: pc tool to generate the modified i8051 rom.
It modifies the opcodes of the given i8051 program. In addition, each data of each opcode is also xored with different values.
Furthermore, the full ROM is xored again with keys that are residual data from stage 1.

----+ loader: the i8051 program, must be compiled with sdcc. It checks that lv2 kernel, stage0 and stage1 haven't been modified, it does some handshake with the device to
check cobra usb authenticity, and it decrypts stage2, which is inside stage 1.5. It also self-checks stage 1.5 against modification.

----+ vm: the vm that implements a simple i8051 emulator. The opcodes and obfuscation xor values are autogenerated by the gen tool in opcodes.c file.
Currently, generation of stage 1.5 requires to modify some vars in the Makefile, this was intended to be automatic in the future by the stage1.5_gen tool.

----+ stage1.5_gen: it generates the encrypted stage1.5 file, that can be directly flashed on the device.

Stage 1.5 protection mechanism includes some additional operations ("side effects") done in the md5 functions (vm) to complicate reverse engeneering,
emulation and debugging techniques such as hooks.

Most attackers would assume that it is just a md5 function after seeing some constants, and they would stop the reverse of the function.
This protects against both: emulation where the attacker blindly implemented the md5 function, and some hooks where the attacker would hook the function:
calling original function, returning to his code and giving the proper value of the md5 without realizing that the state of the vm (instrCount) has been
modified with the data passed.

+ stage1.5_lan

An unprotected implementation of stage1.5 that loads decrypted stage2 from lan. Useful for debugging: flash stage1.5_lan to the device and you can send
stage2.bin with graf chokolo "sendfile" tool upon ps3 boot.

+ stage2

Cobra core itself. It implements almost all functionality of cobra (except ps2 and network isos). Its functionality is made available to the gui program (manager)
via syscall8 with subopcodes. (see syscall8.h). Every pointer in these syscalls is reduced to 32 bits (get_secure_user_ptr function) for security purposes.

----+ storage_ext.c: it implements the disc emulation system, providing functions to mount/umount disc files, and to send insert/eject events to devices.
In 5.0, a "proxy system" was added, so that the actual read could happen in user mode via ports/queues.
This is currently only used for the network iso features, where the network code is done by an user mode sprx loaded at the vsh process by the gui program.

----+ modules_patch.c: it contains the patches to user modules. It also implements some syscalls, so that the gui program can load a sprx in the vsh process to have resident code.
This is currently used only for network iso, but it could be used in the future to implemented "plugin" features, like resident ftp or something.
Due to security concerns, all modules of the firmware are currently hashed, this is to avoid the gui program and the netiso sprx to be easily dumped,
although that wouldn't be critical anyways.

----+ psp.c: it implements the reading of psp isos. See modulespatch.c for patches. Currently 3.55 and 4.00 psp emulator are supported. The gui program is able to mount
an encrypted fat32 image with the sys_storage_ext_mount_encrypted_image (storage_ext.c)
This is currently used to hide the 4.00 ofw emulator (which is further encrypted with our own sprx encryption), which is located in the "lambda.db" file in the
psp launcher package. Other than that and having a way of starting the psp emulator, the psp launcher doesn't have any function, the rest of the content is
filled with random fake data and black png images.
Currently mode 1 = 3.55 emulator, mode 2 = 4.00 emulator. The gui program determines which emulator to use by either user selection of mode,
or by a fixed list if mode is auto. (see cobralib).

+ stage2_cipher

PC tool to cipher stage2.

+ ps2emu
---- + include
---- + src

The ps2emu cobra "sdk".
It contains the defintions of some ps2emu functions.
The functionality is quite limited compared to the lv2 one, but there are still functions for file access (internal hdd only), libc, etc

The symbols.h contains the addresses of the functions.
Either PS2HWEMU, PS2GXEMU or PS2SOFTEMU must be defined to select between the "almost full hardware" emulator (CECHA, CECHB),
the gx emulator (CECHC, CECHE) and the software emulator.

+ ps2emu_gen

Tool to merge ps2emu stage1 with a ps2emu. Original 3.55 ps2_emu.self, ps2_gxemu.self and ps2_softemu.self must be placed in this directory to compile ps2emu stage1.

+ ps2emu_stage1_file

Stage1 for ps2emu, which is merged with emulators .self. It loads an encrypted ps2emu stage 1.5 from internal hdd, that previously cobra core wrote to a temporary file.
Compile with "make -f Makefile.hwemu", "make -f Makefile.softemu" and "make -f Makefile.gxemu" to select each emulator.

For the encryption, modification date of the file is used the key as well as very minor obfuscation to hide file name, further protection is done in ps2emu stage 1.5.
A different key is used for each emulator.

+ ps2emu_stage1_file_debug

Same as above but without protection, intended for debuggin purposes. It loads directly a decrypted ps2emu stage 2 skipping stage 1.5.
PS2EMU_DEBUG must be set in cobra core (lv2 stage2).

+ ps2emu_stage1.5
----+ gen: pc tool to generate the rom of i8051 program with modified opcodes, encryption, etc. Pretty much like its lv2 counterpart, except that it takes two i8051 programs
as arguments.

----+ preloader: first i8051 program. It sets the keys of the second i8051 program using predictable rand function from sdcc, and reboots the virtual machine at the addresses
of the second program.
----+ loader: second and main i8051 program. Decrypts and loads stage2. Some protection to avoid modification of ps2emu as well as self-modification is done.
Some protection is done using unused part of the ps2 emu arguments that were set by lv2. See lv2 stage2.
----+ xtea: small ppc program with xtea algorithm. It is to be used by loader.
----+ xtea_cipher: pc progra, it encrypts the xtea binary with lightweight encryption that can be handled by virtual program, and converts it into an array suitable for sdcc.
----+ vm: the vm that emulates a modified i8051 machine. Pretty much like its lv2 counterpart, with some slight differences.
----+ stage1.5_cipher: it ciphers the ps2emu stage 1.5, making it ready to flash to cobra usb.

+ ps2emu_stage2

The core of the ps2emu code. It handles the disc emulation in the ps2 lpar.

----+ common: the part of the implementation that is common to the 3 emulators. Disc emulation itself is really here. Also, code to read non original ps2 dvd is here.
PS2 emulator tipically read most dvd sectors by using a 2064 bytes raw read using an unofficial/undocumented/propietary scsi command.
However, this command only works for original discs, and there doesn't seem to be any way to bypass this from the ps3 software side.
The workaround to make DVD+-R to work is implementing the 2064 command by reading 2048 bytes from disc and faking the rest of data,
just like it is done for isos anyways.

----+ hwemu: the part of the implementation that is specific of ps2_emu.self
----+ gxemu: the part of the implementation that is specific to ps2_gxemu.self
----+ softemu: the part of the implementation thati s specific to ps2_softemu.self. Very similar to the gxemu one.
----+ stage2_cipher: pc tool to cipher ps2emu stage2.

+ netiso: user sprx with the implementation of network isos. This sprx uses the sys_storage_ext_mount_discfile_proxy function to get the disc read requests from kernel.
This sprx is loaded by the gui program in the vsh process space. Because of the special way in which is loaded, the start and stop routines must follow some rules:
start routine can't use some functions and it must end with a thread exit using directly the lv2 syscall and not the library function.
Same goes the stop function, but additionally, the stop function must finalize the module by itself.

+ ps3netsrv: pc application with the server code for network isos.

+ sprx_cipher2: tool to encrypt self/sprx for cobra usage only. Keys for gui (manager), vsh plugins (netiso) and 4.00+ psp emulator are different.

+ encrypt_image: it encrypts a fat32 image. Used currently to hide 4.00 psp emulator.

+ cobralib

The library given to the gui programmer. It encapsulates the syscalls to make things a bit easier to understand. It also does some processing, like psp keys setting,
and discless jailberak game setting.
For example, discless games in jailbreak format are implemented like this: an empty dummy ps3 iso is created by cobralib and mounted. After that, the jailbreak
game is mounted with the standard path redirection method. This approach allows to have disc command emulation at the same time that the standard path redirection, allowing
a near 100% discless compatibility.

+ usb
----+ cobramakefirm5.0: tool to create a cba file. The 5.0 directory includes the files that were used to generate cobra 5.0 firmware.
To generate a new firmware, replace the content of that folder with new stages 1.5, leave mcu.bin and other files, and use "cobramakefirm 1 5.0 newfirm.cba"
----+ cobraflash: the flasher that is distributed to users.

+ cobrausbupdater: the ps3 version of cobraflash. Why are there idiots that try to reverse this when they have a pc version easier to reverse is unknown, but this application is unprotected because there is anything too useful for attackers there.

Finally, from deank: Without recompiling you can't port it to a different firmware. The latest cobrausb FW6.0 was for 4.30, so you'll need to change a lot of stuff to make it work on 4.50.

From CaptainCPS-X: So, yeah deank is right, we indeed need the source to be able to compile the CFW elements that need to be changed, payloads alone wont do the job.

vronz , payloads alone won't do the job. The article is not talking about USB dongle, or specific micro-controller source code and neither am I, if you research more you will notice it is talking about CFW modules and other needed tools.

So to give you an idea, lets say you get the magical payload, you will need to have the CFW with needed changes so it is able to interface with it, or else it will not work.

Lets say a Windows application to play mp3 and wav media, use functions from a Dynamic Library (DLL) but when compiled it didn't include a module to load mp3.

You load the application and try to play an mp3, what will happen? a message will pop-up about windows not being able to find the module required to play mp3, then to fix it you would have to recompile the Dynamic Library, this time including the new module to handle mp3s.

If you still believe we don't need any source code, then well, I tried to explain it . SeeYa!

Finally, from an0nym0us: You are mostly right, the majority of the code that they will be releasing is useless DRM protection they used to detect change, and brick the dongle. Much of which had been reversed already anyway. They probably are not selling many if any units anymore either, so that for sure was a factor. And of course it is to drive public sentiment of their profiteering in the ODE market.

But the "good for the scene" part has some truth to it. The patches used for bdemu for instance will be quite useful to replace the method that has been in use since 2010. Some of the other patches that remained unique to the Cobra USB will also be valuable to the scene.

At the end of the day though, for me personally, the choice to open-source now is a too little too late scenario. This company created its own reputation of being slimy snakes, and shedding skin now will not change that.


Sponsored Links

Sponsored Links
Sponsored Links

Sponsored Links

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