PS3 PSXclassic's working with decompressed ISOs (w/ Tutorial)

Additional Research from PS3 developer zecoxao as the dev shares some information & findings from ZeroTolerance pertaining to PSXclassics working with decompressed ISOs. Great news coming for the PlayStation 1 gamer on CFW enabled PS3 consoles. See full details and the tutorial in the various quotes from the source (PlayStationHAX) link provided:​

​

It's simple to do.

• forge edat, use psx2psp to forge eboot and pack everything up.

Credits to ZeroTolerance for the information and findings.

Here are the tools (Windows only) :https://mega.nz/#F!lhdmgKxS!xOWydW41HkkK8TiqoP6ZIw


package.conf (example) :

Content-ID = UP9000-NPUJ00594_00-0000000000000001 
k_licensee = 0x00000000000000000000000000000000
TitleID = SLUS00594 
DRM_Type = Free
Content_Type = PS1emu 
PackageVersion = 01.00

make_npdata command to sign ISO.BIN.DAT (example):

make_npdata -e ISO.BIN.DAT ISO.BIN.EDAT 1 1 1 0 16 3 00 UP9000-NPUJ00594_00-0000000000000001 5

Apparently (and this is something Sony LOVES doing) they decided to use the code of a tool called PSX2PSP as their own and made psxclassics. the compression algo is there (although modified) and the isos come out uncompressed or compressed if we choose to.
The only 2 differences i've found so far (by using psxtract from Hykem) were that the crypto they use and PSX2PSP's (aparent lack of) crypto and the compression algo.

Sorry for the clarification

Tutorial:

1.) create pbp file using ps1topsp tool without using any compression methods.
2.) extraxt the data.psar from it (this file is required for creating ISO.BIN.EDAT)
3.) extract iso headers and isos from data.psar
4.) extract the sector table from iso header.
5.) use hasher util with each iso and sector table to create the the table with proper sha1 hashes.
6.) insert the hash tables to their iso headers
7.) fix the iso offsets into iso headers.
8.) create ISO.BIN.DAT using modified iso headers.
9.) create ECDSA signature at the tail og the ISO.BIN.DAT
10.) encrypt ISO.BIN.DAT to ISO.BIN.EDAT
11.) make pkg
12.) Profit!
​

Download: Tools (Windows)

Source: PlayStationHAX.it
​

 

What's the advantage of this? Faster loading? Does the compression effect visuals? I know PS1 games look worse loading via webMAN over IRIS

 

What's the advantage of this? Faster loading? Does the compression effect visuals? I know PS1 games look worse loading via webMAN over IRIS

it's not a matter of advantage. the initial issue we had was actually compressing the isos, because sony uses a custom tlzrc algorithm that we don't know about. however, ZeroTolerance found out that it's possible to just put a decompressed inside and it'd work
i assume however, that what you're saying IS true. using decompressed isos should allow for a faster loading .
ah, and i have no idea if this method works with OFW, since the tools to add ecdsa signature and the keys are still from 3.55 downwards, so it's possible that sony hasn't added protection measures yet. we could theoretically use a bought ps1 classic from the store as template and use it to copy activation settings to another eboot/iso.bin.edat combination we'd forge. the only issue would be passing the data (either with data transfer or with an ODDE)

 

it's not a matter of advantage. the initial issue we had was actually compressing the isos, because sony uses a custom tlzrc algorithm that we don't know about. however, ZeroTolerance found out that it's possible to just put a decompressed inside and it'd work
i assume however, that what you're saying IS true. using decompressed isos should allow for a faster loading .
ah, and i have no idea if this method works with OFW, since the tools to add ecdsa signature and the keys are still from 3.55 downwards, so it's possible that sony hasn't added protection measures yet. we could theoretically use a bought ps1 classic from the store as template and use it to copy activation settings to another eboot/iso.bin.edat combination we'd forge. the only issue would be passing the data (either with data transfer or with an ODDE)

Makes sense and neat to know that the 3.55 keys are still used in any area on the PS3. Thanks for the info and I guess PeXploit could be used for those below 4.75 for install as well as you said using it as a template.

 

Makes sense and neat to know that the 3.55 keys are still used in any area on the PS3. Thanks for the info and I guess PeXploit could be used for those below 4.75 for install as well as you said using it as a template.

yeah, it should be possible. then again i don't know how much did sony patch on ps1 classics

 

it's not a matter of advantage. the initial issue we had was actually compressing the isos, because sony uses a custom tlzrc algorithm that we don't know about. however, ZeroTolerance found out that it's possible to just put a decompressed inside and it'd work
i assume however, that what you're saying IS true. using decompressed isos should allow for a faster loading .
ah, and i have no idea if this method works with OFW, since the tools to add ecdsa signature and the keys are still from 3.55 downwards, so it's possible that sony hasn't added protection measures yet. we could theoretically use a bought ps1 classic from the store as template and use it to copy activation settings to another eboot/iso.bin.edat combination we'd forge. the only issue would be passing the data (either with data transfer or with an ODDE)

I haven't tested this yet... it looks to me like a lot of steps to do something that backup managers (including multiMAN, Iris, webMAN and RetroXMB) already can do without any effort from the users...

My question is, would it be possible to create a psx placeholder like the one for ps2?

 

That would be neat but I prefer this over a manager as I love the quick access from the XMB. I even use Cobra though admittedly looks worse then loading from IRISMAN

 

That would be neat but I prefer this over a manager as I love the quick access from the XMB. I even use Cobra though admittedly looks worse then loading from IRISMAN

RetroXMB uses IRISMAN to load the isos quickly from XMB. Anyway it would be interesting to see a PSX Classics Placeholder...

BTW have you tested the bad looking games switching between psxemu or psxnetemu in /setup.ps3 ?

 

I haven't tested this yet... it looks to me like a lot of steps to do something that backup managers (including multiMAN, Iris, webMAN and RetroXMB) already can do without any effort from the users...

My question is, would it be possible to create a psx placeholder like the one for ps2?

yes, it should be possible. however you'd need to reverse engineer the code used in psx2psp in order to fast-forward the process...

 

this is so cool ,seams a bit like the PSP days of getting your PSX games to run on your PSP there was a program/app that pretty much did it all for you used it all the time back then , something like that for the PS3 would be great

 

I've added the Instructions and some scripts to make your life easier on the mega link. Please consult them, if you want to make a template for psx classics. Thanks

 

Where is fix_isobindat.py?

 

Where is fix_isobindat.py?

thanks for reminding me. i added it now (inside a zip) because mega said it already exists. added.

 

Run ps1iso.exe not find iso.dat
iso.dat is ISO.BIN.DAT this file? I rename it

Run sign.py get R / S value is not the same every time?

 

Run ps1iso.exe not find iso.dat
iso.dat is ISO.BIN.DAT this file? I rename it

Run sign.py get R / S value is not the same every time?

iso.dat is the ISO
R and S are always random

 

Successful
But need to edit fix_iso-bin-dat.py 'r +' change 'rb +'


But more CD ALL IN ONE How to make?

 

Successful
But need to edit fix_iso-bin-dat.py 'r +' change 'rb +'


But more CD ALL IN ONE How to make?

same method but append isos

example:
iso.dat: <-(iso1(eof)iso2(eof)iso3(eof)iso4)->

 

Successful
But need to edit fix_iso-bin-dat.py 'r +' change 'rb +'


But more CD ALL IN ONE How to make?

edit which 'r +' to 'rb +' in fix_iso-bin-dat.py ??

----------

Appending R: & S: to iso.bin.dat at the end will look like this?
Should the last line be 16 bytes?

00 77 9C F0 10 C7 55 42 75 42 AC 40 95 C9 3C 91
01 69 E9 07 34 00 53 07 BA BD B8 CF 59 7C A8 50 
63 AA 46 8E E2 D9 29 F2 68 0E

I really want to figure this out but my finished game errors on xmb..
It be nice to get the NTSC Fear Effect 1 & 2 multi-disc working since they have disc switching problems,
but I can't get a single disc game working..

Maybe a script could be written for the hex patching stuff?

-----------

Also appending multdisc to iso.dat, shouldn't the iso.bin.dat become 4mb instead of 1mb ?

 

I really can't help here (i never tested this), my only advice for you [MENTION=20220]MOST Hated[/MENTION] is to use mentions. [MENTION=502]zecoxao[/MENTION] in this case, then you have more chance that he will answer.

Edit: I realized is your first post. Welcome on site.

 

I really can't help here (i never tested this), my only advice for you [MENTION=20220]MOST Hated[/MENTION] is to use mentions. [MENTION=502]zecoxao[/MENTION] in this case, then you have more chance that he will answer.

Edit: I realized is your first post. Welcome on site.

Thanks for the warm welcome

Yeah. I caught onto this late because it should of been bigger news playing psx games the official psn xmb way.. Imo

I followed every step. Step for step and I get an error when running the game on ps3.

I built two ps1iso.exe 32 / 64 since I'm on windows 10 pro.. Just in case.

I'm not sure where I'm failing at.. I'm usually good with this stuff.
I had no problem making PS2 Classics the manual way before the GUI by [MENTION=89]aldostools[/MENTION] was released.
For some reason I can't get this working.. I'm not gonna pull hair out over it though.

Some help from [MENTION=502]zecoxao[/MENTION] and [MENTION=1840]Omage[/MENTION] would be appreciated.