Sponsored Links

Sponsored Links

Sony PlayStation 2 (PS2) Classics Algorithm Revealed by Flat_z


Sponsored Links
71w 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: [Register or Login to view links]

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: [Register or Login to view links]) 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) : [Register or Login to view links]



data (CEX): [Register or Login to view links]



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

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

PS3 News's Avatar
#679 - PS3 News - 18w ago
Today magneto has made available the Cobra ODE 2.1 Public Beta with changelog below, as follows:

Download: v2.1_beta.rar

We are releasing a public beta for the 2.1 firmware which is soon to be released. This beta is for v4.20, v4.30 and v5.10 boards only. Unfortunately, we are still finalizing the FPGA images for v3.x boards. You can download the beta from here: v2.1_beta.rar

For v4 board users, make sure you flash both FPGA images correctly. For v5 board users, you MUST update to the 2.0 firmware before using this beta. If you did not update to 2.0 already, then the 2.0 firmware file is included in the beta archive.

Here is the changelog:

  • FPGA1: Fix timing issues in AES core
  • FPGA3: Improve stability
  • Fix encryption issues causing 80010017 errors for v3, v4 and v5 boards
  • Fix bypass method for MPX001 motherboards
  • Fix crash when disc dumping finishes
  • Fix issue when BD-RE disc is detected in drive
  • Added support for bypass.delay option (default is 10000 in milliseconds)
  • Enable mcu.underclock by default
  • Set default manager type to browser
  • Enable eject.on_selection by default
  • Enable eject.add_menu by default

Small changes are required, the browser, eject on selection, eject add menu and underclock are enabled by default, so in order to disable them you would need to use : mcu.underclock=0 or eject.add_menu=0 for example in cobra.cfg

EBOOT/SELF/SPRX Resigner for ODE by Joonie86

Hi everyone, this is Joonie. I would like to introduce this useful tool for ODE users.

I've seen some EBOOT resigners for ODE that resolves the issue with 80010017 error due to the non-original eboot, but it seems that no resigners could resign self and sprx files for ODE users unless the files are renamed to EBOOT.BIN instead.

Lots of games like Cod, God of War, FFX 10/10-2 HD, has tones of files including EBOOT.BIN, *.SELFs and *.SPRXs needed to be resigned for lower FW to work with.

This tool can be useful for people who use lower FW version, but the game requires higher FW,
I think this is very helpful for 4k users who use OFW 4.53 but willing to play future release game that requires 4.55+ FW.

Some of games can't work without properly resigning all of those files if the game has been touched for CFW, or you're trying to convert PSN games to DISC type.

Games like Lost in the rain [PSN] does not work without resigning sprx files [it has about 26 files to be resigned as NO-DRM]



How to use:

1. unpack the zip file
2. choose the desired folder to resign each file
3. put the file you want to resign, if it's EBOOT.BIN put that inside EBOOT Resigner folder, if it's Self file then inside the self.

*it does not support multiple self / sprx files, so please do it one file at a time

4. run the batch file [EBOOT Resigner] [SELF Resigner] [SPRX Resigner]
5. it'll be automatically delete the original file and create new file that's resigned with 3.55's key in order for ODE to work.



*This tool originally had Chinese translated gui interface, but I removed it, if that's needed I can add it upon request.

Usage of EBOOT/SELF/SPRX Resigner for ODE

1. Resolves the issue with the game due to the missing original EBOOT.BIN/*.SELF/*.SPRX [80010017 error fix]
2. Modded EBOOT.BIN to enable some cheat codes.
3. Homebrew/PSN pkg conversion to Disc type ISO file.
4. Lowering PS3 System software requirement from 4.XX to 3.55 [It can be very useful for 4k users who wish to stay on 4.53 but willing to play future release games]

*Regarding resigning npdrm psn pkg eboot/self/sprx. In order for those npdrm files to be resigned, first it has to be NO-DRM type, you can make those file "RAP" free by using True Anscestor Eboot Resigner 1.91. As long as it's NO-DRM EBOOT/SELF/SPRX, It should work with this resigner for ODE. Because this resigner does not support NPDRM files [requires RIF KEY]

Non-supported feature:

1. Batch resign for multiple files. This resigner can only resign one file at a time.

Download: [Register or Login to view links] (COBRA_ODE.zip)

I originally found this from Chinese forum called Duowan. This tool is kinda similar to JjKkYu's older version of True Anscestor Eboot Resigner. Unfortunately I couldn't figure out who originally made this tool.

All I did was adding "SPRX" resigner to support more files. Please remind me if anyone knows who built this tool originally, I'd like to give him many many thanks.

Special Thanks

naehrwert [scetool], Team Cobra, The person who originally built this tool.

P.S. SDeath, Can you make batch script for this tool to support multiple self / sprx files? games like FFX HD has about over 1000 sprx files.. ;; I really enjoy your batch tool for ISO. Please consider this if that's possible.

How to Install and Play PSP Remaster PKG on the Cobra ODE by Joonie86

Hi this is Joonie, today I want to introduce this tutorial to show you how to play PSP games on PS3.



About a year ago, this method was discovered by the well known developer zecoxao and since then all the scenes got hyped and as a result, lots of great tools were developed, but sadly, due to the its compatibility issue with games, lot of people have lost interested in doing this. I personally confirmed this PSP remaster work on OFW by data transfer from CFW to OFW.

But at that time, I did not have ODE and Cobra ODE was still in developing stage, so probably because of that, people have forgotten about this PSP Remaster conversion. So today, I'd like to bring it back here so hopefully it helps some people who really want to play PSP games on PS3.

First of all I would like to send my thanks to everyone that contributed to this forum as it has taught a lot on the topic and I doubt I could have done this without them!

Requirements:

1. Sonicman ODE v1.01
2. PSP to PS3 Conversion tool
I use Aldostools' [Register or Login to view links] updated on 2013-05-09! Based on the awesome scripts created by szczuru, and the tools created by Pink1, arnold (swapperneger), zecoxao, tpu, doobz, sandungas among others devs. This "mod" tries to streamline the process of conversion of PKG/ISO/CSO/PBP to PSP package for PS3. Latest versions include a GUI and improved compatibility.

3. Compatible PSP Game ISO files for PS3

PSP to PS3 conversion's compatibility is not really good, probably as much as PSN Game to ISO, which means I'd say 50% of the chance you may get it to work. Before you begin, you could look at compatibility list:

4. FAT32 Formatted USB Stick or HDD [Big enough to contain PSP PKG Games minimum 2GB
5. Cobra ODE

How to:

Step 1: PSP iso to PS3's remaster PKG Conversion

For this example i will use the following:

GAME ISO: Parasite Eve: The 3rd birthday
Disc ID: ULES-01513
Unpacked size: 1.36GB
Image Format: .ISO



Drag the ISO file to the file Path and it will automatically process and fix ISO file properly for Conversion, In the middle of the process it will ask if you want to fix EBOOT, MINIS2,EDAT and such, Just click "YES" so it will continue.

Soon you will see this screen below:



Then click "MAKE PKG" and it will start process. As soon as you're done, you'll see the message saying "Process finished" and then find the where the result is by clicking black folder icon and open the results folder:



Copy the pkg file to External USB FAT32 HDD or STICK, and plug it to PS3's front USB ports.

Then launch the SonicMAN ODE. You DO NOT have to change your Cobra.cfg setting to make it as default setting, you can just put that manager.iso file inside PS3_GAMES folder on your NTFS HDD for ODE.

Step 2:

Launching SonicMAN ODE and Install the pkg.

This multiMAN fork called SonicMAN ODE has pkg install feature, and it does not matter if the PKG file is repacked or not. It can unpack the PKG file without going thru PS3's signature check, and gets registered inside the system so you do not have to put your system on Recovery mode and data rebuild like old way, it's really easy to install pkg just click and go.

*A little tip for DLC install. I know it's off topic, but it is very useful tip for people who want to install DLC pkgs as well other than PSP pkgs.

With the same method, you can install DLC pkgs too, but since it unpacks everything from the package including PARAM.SFO, you may eventually face the issue with the particular game you want to play, so the best way to do is, if it is possible, after the installation of DLC pkg, manually install game update at the very last, so that way you can overwrite the PARAM.SFO over DLC's:



Select the SonicMAN ODE from the browser and mount, then launch it!



Open the File Manager:



Click the dev_usb00X [the number depends on which port you use from [S3]



Fine the package and double click:



Click Ok to unpack the package.





As soon as you're done exit to XMB. If the game doesn't appear right away, try to eject the disk and mount any PS3 games on ODE Browser.

As soon as the game is mounted, it will refresh the system and PSP game will appear. Once it's appeared, you don't need to use SonicMAN ODE anymore, it's permanent like homebrew, you don't need bootdisc or SonicMAN to launch it.

If you use Superslim PS3 and enabled 4.55 bypass, whenever you launch PSP game, your Clipboard's LED will blink as if it was doing bypass process, do not worry, you don't need to swap any disc, you can just leave the bootdisc.

It will launch no matter what. Again, you will see lots of games will have issue, eventually freeze, or blackscreen, so please check the compatibility list first and then try, if you try many times and fail, you will feel so frustrated.

Games that are confirmed by me:

  • Final Fantasy 0
  • Final Fantasy 7 Crisis Core
  • Parasite Eve The 3rd birthday
  • CPGX





*How to make your PSP games run in full screen:



Go to the game setting from XMB.





Video: Examples of three different bypassing behaviors on OFW 4.55 (Only 4k models)

















Since OFW 4.55, Sony made changes on PS3's Official Firmware to block ODE, but for some reason, only the 4K/4.2K models are affected and as a result, Team Cobra successfully managed to bypass the anti-ode check on OFW 4.55.

Unfortunately, To be honest with you all, running back up games on 4K/4.2K models is not as easy as before, but, ODE still does its job and allows you to play back up games no matter what.

Bypassing procedure is a little bit different depending on the game title, so in this video, it will show you how it is different.

Basically there are three different behaviors.

1. A game with no update [1.00 version] : Only requires one swap [Boot disc -> Swap disc]
2. A game with update [1.0x version] : Requires two swaps [Boot disc -> Swap disc -> Boot disc]
3. A game with update but does not check LIC.DAT [license data] [Boot disc ->Boot disc]

In this video, there are three games that show each case of bypass procedue.

1. Dynasty Warrior 8 Extreme Legend US release [1.00 version with no update]
2. Dai-3-Ji Super Robot Taisen Z JP release [1.01 version with game update patch]
3. Metal Gear Solid 4 Guns of Patriots US release [2.00 version with game update patch but no LIC.DAT]

Tested system setup:

PS3 CECH-4001C
Cobra ODE 4.30a
MCU 2.1 Public Beta
Bypass Enabled
Cobra ODE Browser 1.6
OFW 4.55
WD Elements 1.5TB
Bootdisc : BLUS30111 PES 2008 US
Swapdisc : SONY BD-RE 25GB SL
BD Disc's MID : RITEK-BW1-001

Finally, from Joonie86 comes a Cobra Manager 1.6 [Stealth version] with details below:

Download: [Register or Login to view links]



This is as the same as Cobra Manager v1.6 that's on the official Cobra-ODE's Web site, but properly spoofed. I saw the ban report recently and decided to make proper spoofed version of Cobra Manager.

I can not guarantee if this will prevent ban from PSN, but one thing I can tell is this won't be flagged as Cobra Manager, but Kung fu rider instead.

I extracted PS3_DISC.SFB / LIC.DAT / PARAM.SFO from the original game. so it's almost as close as the original game.. but I didn't put the original ICON,PIC files because I don't think that's necessary.

I haven't tried this with my system yet since it's more work for me because I have to re burn new SWAP disc.

If someone wants to try this out please replace the manager with this one and report back.

SDeath mention that whatever file that you put inside the COBRA folder as manager.iso, on XMB it would be shown as "Cobra Manager", but I believe it won't be flagged as "Cobra Manager" because I saw how Sonic-man-ODE was flagged as Sonicman ODE instead of PS MOVE Starter Edition unlike Multiman for ODE.

Again, this is NOT Cobra ODE "Browser" but Manager which is useful for people who want to dump their own game discs.

PS3 News's Avatar
#678 - PS3 News - 18w ago
Today PlayStation 3 developer deank released MultiMAN v04.55.01 which features a USB bus scanning fix for 4.53-4.55 CFW alongside the latest Showtime for MultiMAN with the changes outlined below.

Download: [Register or Login to view links] (44.66 MB) / [Register or Login to view links] (140.65 MB) / [Register or Login to view links] (41.18 MB)

multiMAN 04.55.01 Changelog:

  • Fixed USB bus scanning and reset for CFW 4.53 and 4.55
  • Updated Showtime for mM to version 04.05.302
  • Fixed few other things

All updates are also available online within mM and in the WEB column.

Showtime v4.5.308 Changelog:

4.5.308 (by Andreas Oman)

skin/osk.view: Get rid of a trace() message
view: Support backslash escaped characters
Move deescape_cstyle() to misc/str.c
misc/str: Use av_url_split() instead of a copy
glw: Make sure sinewave() always output a different number than last time
osk: Make captions on some buttons translatable
Put on screen keyboards in a category of its own
Add support for On screen keyboard plugins
glw/deck: Add missing cases for GLW_SIGNAL_RESELECT_CHANGED
Fix double free()
glw: Optimize evaluation of dynamic statements
glw: Do dynamic statement evals without signal handlers
glw: Remove priorities from signal handling
glw: Remove remaining signals that needed to return values from generic signal dispatcher
glw: Move pointer events out of generic signal handling
glw: Remove GLW_SIGNAL_EVENT from generic signal dispatch
glw: Rework padding/border/margin attribute implementations
glw: Increase math precision in sinewave()
skin: If log is not visible, don't even load the views
glw: Add scheduled forced redraw of UI for various glw view functions
glw: Rename gr_schedule_refresh() -> glw_need_refresh()
glw: Fix more issues related to missing screen refreshes when in conditional rendering mode
ass: Leave some debug printf() in which is ifdef'ed out
Fix some minor sub/ass parser issues
Fix various bugs related to font loading and improve glyph caching
text: Fix problem with right aligned text spanning multiple lines
Fix broken JPEG file detection
Remove the index.html parser that will parse HTML as directory scan: It was buggy and the use case is somewhat limited / doubtful
subtitles: Add support for absolute positioning and fontsize changes in ass/ssa
glw: Fix recent regression causing empty label/text not to be cleared correctly
glw: Trig UI refresh when scrollbar moves
Rework image loader / decoding pipeline to be more flexible: Prepares for HW accelerated image manipulation
Add some more keymappings:
. Shift-F7: Seek backwards
. Shift-F8: Play/Pause
. Shift-F9: Seek forwards
Add some ugly hacks for decoding RGBA lossy jpegs
Add missing file: metadata.h
xmp: Trig end-of-track after first loop
metadata: Remove locking during I/O: This should make the metadata UI stuff feel a lot more snappy.
metadata: Don't use metadata_source_t for temp storage during queries
backend/image: Fix broken locking around image loader
metadata: Split metadata.c into multiple files
httpclient: Correctly deal with HEAD req. returning 404
Set page in loading state during video demuxer init
videodecoder: Make sure to clear "too slow decoder" if we switch decoder
Fix audio settings page a bit
Various fixes to some race conditions in image loader
glw: Reinitialize frame queues when switching video engine
glw/video: Improve AVDIFF trace message
ps3: Parse extradata in annexb mode if it's formated that way
ps3: Show notification to user if h264 level parameters is violated: In particular number of reference frames
Fix focus bug on upgrade page
Convert decoded video frames to YUV420 if video render driver can't display it
Fix regression in opengl video renderer
Add audio speaker tests (found in settings->audio)
Set good defaults for cache and persistent path when running in STOS

oscarsu2003's Avatar
#677 - oscarsu2003 - 20w ago
Please help, error unusable PS3 update 4.55 OFW. First apologizes for my English, It is not my language.

I have a PS3 Slim 2501A - 160GB HDD - Cobra ODE 1.9 (4.20A motherboard), OFW 4.53

I changed Cobra_ODE to PT mode and It has had this mode during all the tests I've done. I did not think the PT test mode before upgrading, but it worked some weeks ago, then I went to EMU mode until PT mode again for the update.

I had installed OFW 4.53 and tried to pass OFW 4.55, first through WIFI, an error occurred, not pointed, and then I spent updating via USB. Everything seemed fine, but during the update process stopped at 58% presenting UPDATE ERROR MESSAGE 8002F14E.

The machine got into a loop It could not leave, beginning the upgrade, as high as 58% and give the error again.

From here I performed the following processes:

A) I get out the HDD, I gave FAT32 format on the PC with "HDD Low Level Format Tool" and put in the ps3.

A.1.) I turned on the PS3 NORMALLY, indicated I should format the disk and connect a storage device to update data 4.53 or later.

I connected a USB with OFW 4.55, the process began, presented the message "Checking please wait" for the end, after about 20 minutes, end up giving the message "NO WERE FOUND DATA APPLICABLE UPDATE, connect a storage device contains update data version 4.53 or later, and press both START and SELECT. ".

I have repeated this several times all with the same result.

A.2.) I turned on the PS3 in RECOVERY mode and using the option 3.-RESTORE FILE SYSTEM-. I pointed message "connect a storage device to update data 4.53 or higher and press SELECT + START"

I performed the operation with both the OFW 4.53 as the 4.55, pressing Select + Start, presents the message "Checking ... Please wait" at least for 20 minutes, and finally presents message "ERROR HAS OCCURRED . contact technical support for assistance (8002F281)"

A.3.) I turned on the PS3 in RECOVERY mode and using option 6 -. SYSTEM UPDATE-I indicated message "connect a storage device to update data 4.53 or higher and press Select + Start"

Exactly the same procedure and same result as indicated under "A.1." ("NO WERE FOUND DATA APPLICABLE UPDATE")

B.) I take out the HDD, format it to NTFS, and return to introduce in the ps3.

B.1.) I turned on the PS3 NORMALLY, indicated I should format the disk and connect a storage device to update data 4.53 or later.
Exactly the same procedure and same result as indicated under "A.1." ("NO WERE FOUND DATA APPLICABLE UPDATE")

B.2.) 'll be back once again to take out the HDD of the PS3, I connect it to PC and see that the PS3 HAS NOT GIVEN ANY FORMAT the HDD, the disc appears to me empty and NTFS format.
Is this normal?

B.3.) Use the "HDD Regenerator" program on the HDD brand and I do not have bad sectors, I understand that the HDD is fine.

Do you find normal that the PS3 has not formatted the HDD?
So what this message "not found applicable update data"?

I do not know what else to do, please, can anyone help?

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

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

Geotron ISO For Cobra CFW

Another cobra autobooting blast from the ps2 scene Geotron.

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

PS2 MCMAN For Cobra CFW

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

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

OdeFixUpdate v1.0 Beta from BiteYourConsole

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

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

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

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

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

From magneto: Cobra team release of IRD parsing library

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

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

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

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

ODE 2.0 Update FAQ

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

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

How can I update to the 2.0 release

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Yes, the 2.0 release is for everyone.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Cobra.cfg Config Tool

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

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

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

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

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

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

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

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: [Register or Login to view links]

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




Sponsored Links

Sponsored Links
Sponsored Links

Sponsored Links







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