Sony PlayStation 2 (PS2) Classics Algorithm Revealed by Flat_z


57w ago - Following up on the previous updates, today PlayStation 3 developer Flat_z has revealed the Sony PlayStation 2 (PS2) Classics algorithm with details below.

Download: Sony PlayStation 2 (PS2) Classics Algorithm

To quote: Ok, guys. Unfortunately I forced to admit that I have no more time to work on PS3 stuff because I'm very busy lately. So I decided to publish all information related to PS2 classics as JuanNadie did with the NPDRM algorithm one year ago.

Firstly I wanted to say that he was the first who started reverse-engineering on this subject and when he left the scene I decided to continue his work to keep it from going to waste. And so I would like to thank JuanNadie for his amazing contribution to the PS3 scene. Besides that, he gave me some piece of information on the subject.

All PS2 classics runs within the ps2_netemu.self which represents a different kernel for execution these PS2 games but before it started the VSH module loads your individual data for PSN/SEN (such as act.dat and .rif file for your game). It is absolutely the same process as used for usual PSN games and the goal of it is getting the key used for decryption of PS2 content which includes an optional CONFIG file, ISO.BIN.EDAT and ISO.BIN.ENC.

The latest one is the actual encrypted disc image of the game. All mentioned files are encrypted with the same key (called klicensee) which is stored in encrypted form inside .rif file for your game and it decrypted with the specified key from key table stored in act.dat. When you get this key you can decrypt ISO.BIN.EDAT and see if it contains a game title (for example, SLUS-20062 for GTA 3). This will mean that key is correct. Since almost all the information regarding EDATs is known (see ps3devwiki.com/wiki/Talk:EDAT_files and ps3devwiki.com/wiki/Talk:NPDRM_Selfs) I will not going to explain it again.

Well, now there are two another formats along with EDAT. Let's call the first one as ENC (it represents the actual disc image) and the second as VME (encrypted virtual memory cards). They are encrypted using different algorithms. The ENC format is similar to EDAT and the VME format have a simple encryption layer.

As I said before, ENC file is similar to EDAT and it have the header like in EDAT (but with different magic) and composed of segments of 16384 bytes each (you can see it at the header). I just remind you that file header consists of file magic (PS2\x00), version number (major and minor: 01.01), license type (it always 0x02), application type (0x01), content id, QA digest (seems like to be a SHA-1 hash of the non-finalized file generated using the tool from SDK), CID-FN hash (an AES CMAC hash of concatenation of content id and file name using the third NPDRM OMAC key as CMAC key), header hash (an AES CMAC hash of the 0x60 bytes from the beginning of file using xored bytes of the first NPDRM OMAC key and the second NPDRM OMAC key as CMAC key), time information which includes start and end time of the validity period (they are usually zeroed, base ticks = 62135596800000000), file flags (always zeros), segment size (16384 bytes), data size of the file data, two unknown hashes of 16 bytes each, 40 bytes of unknown data (possible another unknown signature) and pair of an ECDSA signature (40 bytes using the second VSH curve and the VSH public key).

I also remind you that two unknown hashes for EDAT case are known and represents meta data sections hash and extended header hash (an AES CMAC hash of 160 bytes from the beginning of file), both hashes uses the hash key as CMAC key and it depends on the file flags and keys). I don't know exactly what hashes are there for ENC format but when we zeroed them it seems like they are not checked on current firmwares. The file header ends at the offset of 256 bytes.

Segments are divided into two types: a meta data section and a file data section. Each meta data section can include 512 entries (max) of 32 bytes each (16384 / 32 = 512) and associates with a particular file data section. So if we have a meta data section which consists of 512 entries then it will mean that there are 512 file data sections after it and each file data section have size of 16384 bytes.

Besides that, the first meta data segment located at the offset of 16384 bytes. I don't know what data are stored before it but we also tried to zero them (these bytes starting at the offset of 256 bytes and ending at the offset of 16384 bytes) and it works as usual. I guess that it can be the encrypted garbage because the alignment of file data should be equal to the segment size.

Now I will explain what keys are used and how they are obtained. ENC/VME files are decrypted using the ENCDEC device so the decryption process are more faster than at EDAT case. While vSH checks files for their validity period, CMAC hashes and ECDSA signature and obtains the key for decryption from .rif file and it makes a system call #475 to LV2 (on older firmwares it was #471) along with the NPDRM information, klicensee, act.dat key and encrypted rif key. LV2 gets your console ID, encrypts the NPDRM constant using it as a key, decrypts the key from act.dat using the encrypted NPDRM constant and finally decrypts klicensee from .rif using the decrypted key from act.dat. Now we have a klicensee which will be used for later decryption process.

For EDAT case we can use free EDATs without .rif but for PS2 classics we should always use paid content and .rif file. So if you want to resign the game you need to generate .rif for the account on your console (I call this process as "personalization"). Don't forget that .rif file should be created for your act.dat (because it shares the account id) and console ID. Let's move on. When the PS3 gets the final decryption key it send a packet to the system manager inside LV1 which sets the inter-lpar parameter of type 3.

This parameter contains a version information and the klicensee. A system manager catches this packet and sends a request to the storage manager inside SS server #1 which then configures ENCDEC keys used for later decryption. It should be kept in mind that keys for decryption differs between CEX and DEX consoles so the storage manager checks the device type and uses different key slots for ENCDEC.

The configuration process started with running isolated SPU SB module which creates the final keys using klicensee as a key seed and send them back to the PPU which then send them to the device directly during the secure session. There are three types of keys: meta key, data key and vmc key and they are configured separately. The process of making keys consists of applying an AES 128 algorithm on the klicensee while using three different keys.

There are SHA-1 hashes of each of three keys (you should decrypt sb_iso_spu_module.self from 4.xx FW and find each of 16 bytes key by its SHA-1 hash):

For CEX mode:

For DEX mode (you actually don't need it but anyways):

Now we have all keys which are required to decrypt all files. So what we should also know?

ENC encryption uses an AES algorithm in CBC mode and the initialization vector of all zeros. The actual process of decryption of CONFIG and ISO.BIN.ENC started at seeking to the offset of 16384 bytes. There is a first meta data section so we should use the meta key as key for AES and decrypt the entire segment of 16384 bytes. As I said before each meta data sections contains of some entries and each entry have a size of 32 bytes. Each entry contains a SHA-1 hash (20 bytes) of the corresponding entire encrypted file data section and all these sections are located after this meta data section. After the SHA-1 hash we can see the section index of the corresponding file data section (4 bytes).

The rest is padded of zeros. After decryption of the meta data section we can decrypt all file data sections after it. Now we should use the data key! Before the actual decryption we can check the SHA-1 hash of each encrypted file data section and see if they matched to the hashes at entry table of the meta data section. If the actual file size of the disc image is not a multiple of 16834 bytes then we have less entries inside the latest meta data section.

After we finished the decryption of first 512 file data sections we can started decryption of the second meta data section and set of 512 file data sections after it and so on. I recommend to write decrypted meta data entries to another file than in the same file as file data section. It will make a process more easier. After decryption you should truncate your actual file to the data size specified at the header. Now you got an UDF disc image and you can mount it on your PC, for example.

So what is the next step? The next step is the decryption of encrypted virtual memory cards. Each PS2 classics package contains two empty encrypted virtual memory cards which located at SCEVMC0.VME and SCEVMC1.VME. As far I see they are identical for all games so we can use templates for all new virtual memory cards but only encrypts them with the new klicensee. To decrypt virtual memory cards you need to read an each segment of 16384 bytes and apply an AES encryption in CBC mode too but for this case you should use the VMC key. After decryption you should see Sony PS2 Memory Card Format 1.2.0.0 at the top of file.

Well, I attached a draft script for decryption of ENC/VME files. It was written for Python 2.7 and requires CryptoPlus (can be downloaded from: http://repo.or.cz/w/python-cryptoplus.git) and "ecdsa" (use EasyInstall or another package manager) libraries. I intentionally left all keys as SHA-1 hashes because of legal issues but you can find all keys by yourself using my hints. My script uses CONFIG/ISO.BIN.ENC/SCEVM0.VME/SCEVM1.VME file and klicensee file as input parameters. I hope that someone will create tools for that.

To use the script you need to create a file with name vsh.curves and put the contents of the curve table from VSH (get it from ps3devwiki.com/wiki/Keys at vsh pub + curvetable) and replace all hashes of keys by their real values (see FIXME comments). Also replace three NPDRM OMAC keys and VSH public key by their values from ps3devwiki.com/wiki/Keys.

I think that creation of PS2 remastering tool can lead us to getting the fully working games on our consoles but it requires testing. I recommend to create a static klicensee which can be used to encrypt all images in the same manner (static klicensee can also be implemented by patching VSH/LV2 at runtime, for example). After generating a klicensee you should create all keys based on it.

To build an encrypted disc image you should dump the original disc image and then append zero bytes to the end to make it multiple of 16384 bytes. Then you need to encrypt each of 512 segments using the generated data key. Then you should calculate SHA-1 hashes of each encrypted segment and generate meta data section for each pair of segment hash and segment index. After this you need to encrypt meta data section and so on. At the end you need to write an original disc image size to the header, write a content id for it and generate hashes at the file header.

After building ISO.BIN.ENC file you should create a file with the title id and pad it with zero bytes from the right side to get 12 bytes total. Then you need to create an EDAT container for this file. Hint: you can see a correct title id when mounting a disc image on your PC and looking at SYSTEM.CNF of it.

Unfortunately, I hadn't time to see what the CONFIG file does so I will skip this step. I only know that this file is optional or can be empty inside (after decryption). You are not required (and you simply can't do it) to generate a valid ECDSA signature for files because all custom firmwares are patched to skip the ECDSA check. Will be nice to be able to generate a game package for your PS2 game too if everything will works fine. Remember, that some flags at PS2 pkg format can be different.

Credits to: graf_chokolo, fail0verflow, JuanNadie, ps3dev.net, glevand and all my friends (you know who you are).

Finally, from zecoxao: i found the meta key and data key for cex, as for the vmc key, no clue where it is, the two are both in my previous post. you can check the sha1 of those in any site or with any program that supports it. somebody may post those on the wiki, if they want.

i'm happy... this is good and concise info time to search for more #poop

meta (CEX) : https://mega.co.nz/#!gpdQxZZB!ZlZpYj8luKmJ5K892wHlTHvQ6khvtfEGxba5OJM3-Y4



data (CEX): https://mega.co.nz/#!B09nwJhQ!TMC3kxaNLKFzYVuSksPs-nEE_AgnAgS2RQ1BzeZBlTM



From flatz: It is at sb_iso_spu_module.elf too. First two bytes are 64 E3...

VMC key:

kudos to this man








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 680 Comments - Go to Forum Thread »

Quick Reply Quick Reply

PS3 News's Avatar
#675 - PS3 News - 7w 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 SwissKnife tool 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: Cobra_ODE_MCU_v2.0b.7z

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: cobra.cfg_Config_Tool_v1.0.exe / cobra.cfg_Config_Tool_v1.1.exe / cobra.cfg_Config_Tool_v1.3.exe

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.

Changelog:

v1.0

  • Initial Release

v1.1

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

v1.2

  • ARMITAGEIII Limited Edition

v1.3

  • 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: PADTEST.iso

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

-Samson

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 - 7w 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.

Download:









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: Easy Batch Generate ISO's Package 2.0 Full.rar / Easy Batch Generate ISO's Package 2.0 Light.rar

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.

Instructions:

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!

Tips

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

To this:

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

To this:


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

PS3 News's Avatar
#673 - PS3 News - 7w 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

COBRA ODE BOOTLOADER 1.3

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

COBRA MANAGER 1.6

  • 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 - 7w 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.

PS3 News's Avatar
#671 - PS3 News - 9w ago
12 - 2 - 2014: Cobra ODE News - Update

From Cobra manufacturer Max Louarn: We have successfully tested a performance update for 4.20 and 4.30 which rectifies freezing issues reported by some users. We have also implemented a fix for BMD-061 drive control boards on 2k consoles and auto eject on 2k.

Please follow the instructions in the README.TXT carefully.


From PS3 scene profiteer Gary Wayne Bowser (aka GaryOPA):

Don't worry Cobra's solution will be a lot better then E3's half-ass encrypted bootdisc swap-disc.

Cobra's mainboard can do 'encryption on the fly' so if there needs to be a bootdisc with special headers before the iso is loaded, then they will be able to without the need of using an actual Blu-ray.

From magneto: Information update: Only super slim models are affected. The 4.55 update has a specific protection against ODEs. We are lucky to have found a way to bypass this new protection, as Sony have historically only released fixes that cannot be bypassed. We also have a working solution that we're working on, but it is very similar to what E3 has. We are aware that the current 4.55 fix is not user friendly and we are trying to find an alternative solution.

We are trying to make the disc swap solution much more convenient for users before we release it. Some of you should learn to be patient. The team is working around the clock to fix the issue for you, be considerate. Running an IRD-built iso that is the same as the bootdisc you have in the drive should work. Those who reported that some game is working for them, can you confirm that it is a different game than the bootdisc you are using ?

If it isn't, can you upload the iso or specify how it was generated (with IRD or not, which version of genps3iso you used) and specify which bootdisc you used with it and if it works with other bootdiscs ? We expect to have an update available in the coming week.

We have a fix for we are currently testing for those who get the 80010017 error. It will be released with the 2.0 update.

Update: 15 - 2 - 2014: Cobra ODE News - Information

Cobra 2.0 release imminent - features explained (Including initial support for 4.55):

Cobra Team have been hard at work 24/7 preparing the next firmware release for our users. The incoming Cobra 2.0 is once again a massive update and packed with innovative new features.

After the massive features (PS1, PS2, BD/DVD movies and IRD 9 support) added in the recent Cobra 1.90 update, we're back with yet more cool features in 2.0 which will be released in the coming week:

2.0 will pack these features:

  • Initial support for OFW 4.55 (Please read further information in news paragraph below)
  • Auto-generate browser from the MCU, no more need for genps3extra
  • Dumping of original games using the BD drive is now possible through the Cobra Manager
  • Added support for XMB enabled Pass-Through mode, meaning user no longer has to use slide switch to swap modes and in addition playback of burned PS1 discs when used in combination with the game.disc_type=ps1 configuration option
  • Increased AES encryption module performance by over 100%, now there is no lag in playback of IRD generated ISO's
  • Added support for updating PS3 firmware without needing to switch to PT mode
  • Eject now possible on 4k systems, without need for user to open console cover
  • Added support for "eject.delay" option to specify delay in milliseconds before reinsertion of disc after it has been ejected on QSB systems (default value of 1000ms)
  • Added support for "leds.disable" configuration option to disable specific LED colors

We have been working on a solution for OFW update 4.55, which will fix the added anti ODE measures. The current approach will be more streamlined than solutions currently offered by other teams, however it is not as convenient as using the ODE on pre 4.55 OFW's. Our R&D focus is now concentrating on other possible solutions to bypassing the 4.55 checks.

The current working solution for OFW 4.55 will be released in the coming week. We advise users to use this update if they have accidentally updated to 4.55. Others who have not yet updated may want to consider keeping their consoles on 4.53 or lower until a better solution is available to benefit from the user convenience of the ODE on these firmwares.

We can now also confirm that only 4k Super Slim series consoles are affected by the 4.55 update. Those who have 3k / 2k5 Slim or earlier consoles are safe to update to 4.55.

Cobra MCU 2.0 Changelog:

  • Added support for manager.type=browser configuration option -> Auto-generate browser from the MCU, no more need for genps3extra
  • Fix DISC.ISO dumping corruption -> Dumping of original games using the BD drive is now possible through the Cobra Manager
  • Added support for XMB enabled Pass-Through mode -> Allow access to the boot disc from the manager or browser and enable PT without touching the PT/EMU switch -> Allow playback of burned PS1 discs when used in combination with the game.disc_type=ps1 configuration option
  • Added support for game.pt=1 configuration option to force software-emulation Pass-Through
  • Increase AES encryption module performance by over 100% -> Playback of IRD generated ISO will not lag anymore
  • Added support for updating PS3 firmware without needing to switch to PT mode -> Still not recommended to update to 4.55 for super slim users
  • Added support for eject.add_menu=1 configuration option to add a menu to return to manager when game iso is loaded -> useful for 4k which don't have Remove Disc option in XMB
  • Added support for "eject.delay" option to specify delay in milliseconds before reinsertion of disc after it has been ejected on QSB systems (default value of 1000ms)
  • Added support for "mcu.underclock" configuration option -> Allows underclocking the MCU to further limit power consumption
  • Added support for "leds.disable" configuration option to disable specific LED colors -> Feature requested by forum user DarkKitarist because LED light was brightening up his room at night -> 1=blue, 2=red, 4=green, can be added to disable more than one color, leds.disable=6 disables red and green, leds.disable=7 disables all led colors -> Disabling a color can affect LED color in combined situations, for example, disabling green will show a purple color if you select a DVD or BD movie (normally white)
  • Fix freezing on 4.20 and 4.30 boards

To all the impatient people who can't appreciate the work we're doing and the burnouts we're having from preparing this next release to you: thank you for your encouraging words and for bringing up our motivation in working more than 24h per day for your enjoyment and for fixing your mistake of updating before receiving the green light from the team.

For the others, here is an update on the status of the 2.0 release: The release is almost ready, we are doing QA and trying to get rid of some bugs The changes in the 2.0 firmware are massive with a lot of new features that everyone will appreciate. We do not want to rush this release and have it fail for half our users so we must test it properly. A couple more days of work and if no new bugs are found, the release will be ready. In the meantime, please be patient.

Finally, below are some new PCB Cobra ODE pictures with include Version 5.10B. The new PCB boards are shorter than previous models.

From magneto: The new v5 boards are being shipped now, they are much smaller than previous boards. As SDeath said, you can compare the size with the clipon PCB. They will run cooler so should not have overheating issues, and will be much faster for game loading and for IRD games.

I believe they will also work with the CECHL BMD-21 drives, but I cannot confirm that at the moment.

No, burning and using the swap disc is only needed if you have 4.55 firmware and a 4k model and that mode will only be enabled if you enable the appropriate option in cobra.cfg, otherwise, it will work as before.

It will be one disc for all your games. You will need to burn a bluray disc to play games on 4.55, if you are on 4.55, you can play online. What the other user asked for was if he stayed on 4.53, he can't use online, and wanted to know if he could use his ODE on 4.53 without burning discs.

Yes, 2.0 is universal, you can use it on any model, any firmware version. There is no need for duct tape, that is only for E3. For Cobra, you don't need it, but you need to solder one wire and the installation manual was updated with instructions on how and where to solder it.













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