PS3HaX developer Snowydew along with the help of software devloper KDSBest released some interesting Edat Encryption/Decryption tool’s on Sunday, here is what Snowydew said when i asked him about the tools:
Stupid question, what does your tools do ?
was wondering if i could add a bit to the post
extracts iso.bin.edats
post ?
when kds converted it over he found out that act.dat and rif can also be decrypted
as well as possibly re encrypted
errr the thread about it / news post, haven’t done this in ages
the reason the re encryption process is a POC, is because even though we can resign it, we’re unfamiliar with certain bytes in the header (What i wanted to ask if you could add)
I havent done one yet, but if you want to do it, i will front poage it, it would look more proffesional coming from someone that knows exactly what it does
well it’s full sources for all the versions, the java ones are the originals that i’ve had since december
looked aroudn for people to convert over to something usable since you need the java sdk and netbeans installed to even use it or compile it, so we got it to c# through kds
when converting it over he found out little aspects to rif and act.dats, i’m not sure if he included them 100% though
Snowydew> so the decryption as it stands right now, an do iso.bin.edat, requires idps, rif and act.dat for the games.
re encryption i believe it needs the “fake” signed ones, as well as an idps (not sure on the idps)
however the second method only requires the idps and the .rap file
this does not cover licenseing games i believe (It could, but we haven’t tested it)
the re encryption algo is in the encryption one, but again haven’t been able to test it completely (reason i was asking around on twitter awhile back)
Source PS3HaX IRC
and
Snowydews Twitter
05-22-2012
03:42 AM
all I have to say is
05-22-2012
03:44 AM
Releases, releases, and more releases. I love spring:P
05-22-2012
03:48 AM
Mirror: http://www.mediafire.com/?h2h7q9db4iai7j5
05-22-2012
05:02 AM
05-22-2012
05:10 AM
i read the frontpage post but i didnt understand for what is this tool exactly ?
05-22-2012
05:13 AM
05-22-2012
05:14 AM
[MENTION=45614]KDSBest[/MENTION] ok thx and for what is the EDAT for ?
thx....
05-22-2012
05:24 AM
i think its a license file from PSN games......
05-22-2012
06:15 AM
05-22-2012
07:53 AM
Shout out to [MENTION=190503]snowydew[/MENTION] and [MENTION=45614]KDSBest[/MENTION]!
05-22-2012
08:04 AM
Plz a little clarification for "Beginners" of what all this is about ;P ?!!!!!
05-22-2012
08:04 AM
Will this give us >4.0 cfw? Will sell my Ps3 if it doesnt happen this spring. Nvm just trolling..
It's nice to see ppl still contribute to this scene full of flamers and jerks.
Keep up the good work!
05-22-2012
08:12 AM
YUPII!
I like Snowy
05-22-2012
08:52 AM
Congrats [MENTION=190503]snowydew[/MENTION] and [MENTION=45614]KDSBest[/MENTION]. Good job (specially for providing source code).
I ran the app and there is no text field for klicensee so I assume that this release is only for PSX games.
For those asking this tool (once improved) will allow you to do what [MENTION=204584]EXE.trim.ALL[/MENTION] did months ago... freeing DLC, PSX, PS2 and some PSN game. However my favorite use is SDAT. A lot of developers encrypt resource files on SDAT... now we can do our own mods/translation
If you want to get a bit technical (on decryption) here is a disccussion on the topic (the first pages are on self and then changes to EDAT):
http://www.ps3hax.net/showthread.php?t=28303
BTW if you have a RAP you don't need the IDPS nor act.dat nor RIF...
PS: For devs, if any of you knows how an isolated SPU reads the config ring please contact me.
05-22-2012
09:39 AM
I'm just happy that something happens! I'm too uneducated and stupid myself to do anything like this, really appreciate people who keeps the scene alive!
LOVE YOU!
05-22-2012
09:51 AM
Snowy and KDSBest thank you for all your hard work!
05-22-2012
11:15 AM
Thanks so much guys, I have been waiting for this!
05-22-2012
11:33 AM
Hope this stuff does lead to something nice for us users soon
05-22-2012
11:50 AM
05-22-2012
12:53 PM
first, thanks a lot for this tool...when can we expect a release that can deal with ps3 psn edats (from psn ps3 games or dlcs)?..this one is ps1 only...
_
05-22-2012
01:21 PM
Very cool, thAnks
05-22-2012
01:25 PM
happy birthday GregoryRasputin
05-22-2012
02:05 PM
05-22-2012
02:29 PM
Good proof of concept, more pieces of the puzzle are out
The fact is there is an .iso inside all "ps1 classic" games and "psp minis" games... and probably "ps2 classic" games
There are firmware modules (the ones labeled 9660) that can read this .iso format that is an standard of the industry
So theorically, if you can provide an .iso in the correct format (with the extended track info)... and with the hability of recreating his header and the rest of his structure you have a way to boot any ps1 game in any ps3 model
*obiously there is no 100% compatibility in the emulators itself, so some games will not run, but expect a big number to work
------------
With "psp minis"... there is no use because there are no minis discs to make a backup in .iso format
------------
With "ps2 classics" probably has some things in common with PS1... but also some different things... can be a bit more complicated (and compatibility very low with ps3 slims)
05-22-2012
02:35 PM
PS. We're still looking for psp minis with all the requirements to see the file structure inside of the iso.bin.edat. They're apparently rare nowadays so
05-22-2012
03:08 PM
And the "psp minis" released for psp years ago ? (not for ps3)
The format is inherited from PSP, maybe changed a bit with the years, but im supposing not too much, this old games theorically can be "packed" to ps3 format
05-22-2012
04:14 PM
There is the need to know the compression algorithm on the Edat? Like juan said some months ago that the algorithm old in java performs the decryption and re-encryption on the .edat but i mean if we want to make custom psn psx pkgs we need to get that ISO.BIN in plain text uncompressed.
05-22-2012
05:12 PM
Thanks for this
05-22-2012
05:23 PM
I had thought this was to do psn games, but its still going in the right direction for what ive been trying to understand.Maybe someone can answer this for me here. I downloaded mini's from psn server and fixed them for psp then extracted the folders to look inside. I had the same game with the fix from ps3 extracted. I have been trying to figure out the difference with the fixes so that i could fix my other psp minis to play on ps3. The files were encrypted and i don't know enough about coding to understand it. Is this something different altogether?
05-22-2012
06:08 PM
free psn games, thanks Sony
05-22-2012
06:22 PM
05-23-2012
01:30 AM
Nice to see talented people still paying attention to PS1 games.
[MENTION=201930]JuanNadie[/MENTION] was speaking about EXE trim ALL release (and reactPSN after) and i noticed they weren t working when you export them to PSP because the KEYS.BIN is missing (NPUJ-12345/USRDIR/CONTENT/)
It s because the game is turn on free content or is it a part of the missing bytes in the process?
(can you "rewrite/restructuring in proper wiki " the infos you gave here on the ps3 dev wiki? thanks you for your thread and infos)
(the key.bin needed to make it working after export can be "replaced"/ is the same/ with the one you got in normal case when you bought from PSN PSP or from PSP scene release // meaning for people who never used export: export work fine in the release of PSN games for PS3 if you added the Key.bin into folder Content before exporting the game to your psp, otherwise th game is not working on your PSP)
[MENTION=190503]snowydew[/MENTION]dev, and [MENTION=45614]KDSBest[/MENTION] what is the use of the file: CONFIG? (PS1emu config file) it s just for ini the disc number (like starting directly to CD2) and what are the fews bytes "dancing" inside it (CRC to VM1 in case of PS3/ VMP in case of PSP?). Can we said it s similar than SYSTEM.CNF used in original PS1 game (this file, someone else from the PSX time can also answer to describe quickly)
Thanks you for the attention on such area and the release and sorry in advance for the questions.
05-23-2012
03:30 AM
exciting things are happening! i love seeing this stuff!
i can't wait to play thps2 with little load time; i mean, any psone game but that game mainly (for me).
i can almost see this leading to a way of forcing newer games to boot on 3.55 but there will be obvious compatibility errors but nothing anyone won't mind trying to figure out. then again, one step at a time because anything is possible
05-23-2012
03:31 AM
05-23-2012
06:26 AM
05-23-2012
11:51 AM
05-23-2012
07:16 PM
The file structure of a decrypted iso.bin is divided in "blocks" and "clusters"
Then the "disc 1" starts (1024 blocks, 64 clusters)
Then the "disc 2" starts (another 1024 blocks, 64 clusters)
etc...
Inside the first clusters of each disc (this cluster can be considered another header specific for this disc) you have the "magic" PSISOIMG0000 that is different for "psp minis" (i dont remember)..... and probably another for "ps2 classics" (speculation)
Also the "game_id"... "number of clusters"... some unknown counters... (probably blocks used or similar)
But the most important area of this cluster is the 32 bytes (seems to be a key) displaced 0x800 bytes from the start of the cluster
Then there is a block of padding
And in the second cluster it begins the "file_table"... this table last to the end of the "disc 1" (and not-used clusters contains a checksum of 16 bytes)
The file_table is composed of entries of 32 bytes each
In each entry you have...the displacement from start of table, file size ?, cluster number (inside the iso) ?... etc...
--------------------------------------
Well... this file_table is pointing to the disc in iso format, and probably to "sectors" of the disc... it can be a TOC
And here is where is important to take in account the track data mode of the old ps1 discs, because it had an special track (known as MODE2)
Edit:
The positions are always fixed, so for a game with 4 discs the important stuff is at this offsets:
discs_start -----------> 0x000400 (disc1), 0x100400 (disc2), 0x200400 (disc3), 0x300400 (disc4)
discs_keys -----------> 0x000C00 (disc1), 0x100C00 (disc2), 0x200C00 (disc3), 0x300C00 (disc4)
discs_file_tables ------> 0x004400 (disc1), 0x104400 (disc2), 0x204400 (disc3), 0x304400 (disc4)
05-24-2012
06:14 PM
I just created a new wiki page: http://www.ps3devwiki.com/wiki/Iso.bin.edat
All the iso.bin offsets are mapped, some of them are still unknown, but his positions are clear
With this tables can be done a program to "read" iso.bin files to give an output list of all the positions, information, etc... (in a semi-human-readable format)
Now its needed to identify the "unknown" areas by understanding the relationship with the real .iso structure
The next step is to be able to generate this iso.bin files
Feel free to help updating the page if you find something
05-24-2012
06:42 PM
05-24-2012
07:19 PM
But because i dont know exactly what they are... i found no better names
All that i added to the page is from a iso.bin.edat decrypted from a retail game... i just removed the extension .edat to difference it from an encrypted one
And well... in resume... this iso.bin is pointing to areas of another .iso file
This areas obviously are "sectors of a disc"... and probably related with the TOC of the disc (table of contents)
And for the decryption of each disc (or each disc header)... i think the key is the one i marked as "disc_key" (doesnt seems to be a checksum, and is the only one with 32 bytes)
At the end of the file there is an area of 40 bytes a bit strange that i have no idea if is related with encryption
05-24-2012
09:30 PM