• PS3HEN is now supporting 4.93 Firmware

    View Official Release Post for additional information HERE
PS3HEN

PS3HEN PS3HEN - Official Release Thread (Homebrew Enabler for the PS3) v3.5.0 (4.93 support)

I'm trying to play a PS1 game with webman, but it simply soft locks the console as soon as I try and mount the disc.
I try the same bin files from multiman and it mounts and launches and play nicely.

With multiman the game gets mounted and shows up on Xmb as "PlayStation game", no need to use any launcher or anything else.
Is there a special procedure to webman?
 
I've honestly created an account to ask this one question, as googling isn't turning up much relevant results.

What exactly is Dump Disc Hash Key? I spent a few hours last night trying to see what HEN can and can't do as well as see if http://wiki.redump.org/index.php?title=PlayStation_3_Dumping_Guide was a viable option on PS3 Hen, I've come to the conclusion it isn't viable at the moment but the Dump Disc Hash Key seen in the Hybrid firmware toolbox did catch my eye, so I was wonder if you could elaborate more on exactly what it is?

Guess No one can provide any input about my Disc Hash Key Question on page 80?

DHK is used to properly sign save file and is involved in executables encryption on disc. For average user, it is nothing important as in case of saves DHK can be "skipped" using debug fallback equivalent or using Fake SaveData owner in CEX2DEX/DEX CFW/OFW); as in case of decrypting, ODD doing it on the fly transparently so i.e multiMAN in normal mode can read already decrypted contents.

BTW Most of the keys are important only for advanced users, devs, software preservation enthusiasts etc. For You, probably the most important key is ERK as allow You to read HDD on PC in case of console death (possible to obtain only on CFW and maybe HEN consoles with old boot loader).
 
Last edited:
DHK is used to properly sign save file and is involved in executables encryption on disc. For average user, it is nothing important (as in case of saves DHK can be "skipped" using debug fallback equivalent or using Fake SaveData owner in CEX2DEX/DEX CFW/OFW).

Hmm, thanks for answering, when you say "involved in executables encryption on disc" what exactly do you mean? Do you means it's used in the decryption process or..?
 
@DuckTruck Executables (EBOOT.BIN + all *.sprx) are encrypted on disc by key in area which i.e PC ODD/ODDW cannot read. So when You dump PlayStation 3 disc game on PC (or on PS3 by multiMAN with DDA enabled), some contents are encrypted and useless in such form (but as I believe, in future, emulators will read file/db with keys to do it because disc images created in "normal mode" by backup managers on PS3 are not proper (decrypted, messed LBA etc.)). I'm not sure if we talking here about Disc Hash Key precisely, but for sure there is a key which is used by PS3 ODD fw or CellOS to decrypting stuff mentioned before. And this is why ReDump guys needs them for the database as they are part of the disc.

Anyway, this philosophy is similar to ADF lovers VS IPF lovers. In my opinion better way is having encrypted 1:1 disc images + keys instead of decrypted but not the same as original disc images. Currently on PS3, You cannot mount encrypted *.iso because none of the modules or backup managers support it. :(
 
@DuckTruck Executables (EBOOT.BIN + all *.sprx) are encrypted on disc by key in area which i.e PC ODD/ODDW cannot read. So when You dump PlayStation 3 disc game on PC (or on PS3 by multiMAN with DDA enabled), some contents are encrypted and useless in such form (but as I believe, in future, emulators will read file/db with keys to do it because disc images created in "normal mode" by backup managers on PS3 are not proper (decrypted, messed LBA etc.)). I'm not sure if we talking here about Disc Hash Key precisely, but for sure there is a key which is used by PS3 ODD fw or CellOS to decrypting stuff mentioned before. And this is why ReDump guys needs them for the database as they are part of the disc.

Anyway, this philosophy is similar to ADF lovers VS IPF lovers. In my opinion better way is having encrypted 1:1 disc images + keys instead of decrypted but not the same as original disc images. Currently on PS3, You cannot mount encrypted *.iso because none of the modules or backup managers support it. :(

Yep your talking about exactly what I was thinking, and thus why I asked for clarification. The other day I ran the Disc Hash key from the Hybrid Firmware folder, and the resulting output did not match what was on redump. So my current thought process is, Disc Hash Key is the hash of the actual decryption key? (I could be talking out of my ass but that was the first idea that popped into my mind).

I'm with you on the part about having encrypted 1:1 disc images + keys.

Either way this has only got me more intrigued about what exactly the Disc Hash Key function does and what exactly it is useful for.
 
There is another way to think in it...
The original PS3 game discs are encrypted, divided in regions, and other shits we dont need in cfw
In a backup manager is needed to use code to "remove" all this useless layers of the onion, and this could reduce performance because is made by software (not by hardware)

So what you prefer, to have the games in plain files (more simple to deal with them, and smaller size), or to have the games fully protected (in bigger size and with the performace hit) ?

The decission was taken years ago and became legacy, and the details of the PS3 ISO format was decided by cobra team (the hardware manufacturers), and estwald for iris manager

When that happened i had my doubts if the decission taken by estwald was the correct, in some way i like the iea of having 1:1 perfect copies of the original
But after thinking in it and after experience that there was no problem i fully agree with what estwald did... the concept was to remove all the sony protections and simplify the ISO format to the max
 
There is another way to think in it...
The original PS3 game discs are encrypted, divided in regions, and other shits we dont need in cfw
In a backup manager is needed to use code to "remove" all this useless layers of the onion, and this could reduce performance because is made by software (not by hardware)

So what you prefer, to have the games in plain files (more simple to deal with them, and smaller size), or to have the games fully protected (in bigger size and with the performace hit) ?

The decission was taken years ago and became legacy, and the details of the PS3 ISO format was decided by cobra team (the hardware manufacturers), and estwald for iris manager

When that happened i had my doubts if the decission taken by estwald was the correct, in some way i like the iea of having 1:1 perfect copies of the original
But after thinking in it and after experience that there was no problem i fully agree with what estwald did... the concept was to remove all the sony protections and simplify the ISO format to the max
Yeah I get that you wouldn't want to take the speed hit.

Personally my approach is to archive games in its original format (or as close to possible) with the relevant information and tools along side it to get it into a more useful state (if needed) for use
 
@sandungas It is the best for PS3 users (especially when we can't have larger internal memory than as I remember 1,5GiB) but from software preservation point of view it is catastrophic because pirate sites are flooded by broken backups which have impact also on this goal.

@umart666 Writing homebrew for PS3 is not an easy task and, I could be wrong, whole executable must fit into free RAM which we don't have much. So maybe it is just unnecessary time spend and resources waste? From user point of view. ;)

The other day I ran the Disc Hash key from the Hybrid Firmware folder, and the resulting output did not match what was on redump. So my current thought process is, Disc Hash Key is the hash of the actual decryption key?

I don't know. I checked my Mirror's Edge dumps and both keys are not match to each other (neither any simple hash from it but could be salted by something of course), so definitely they are two different things:

disc_hash_key=845D434A390342117E5DB9066BDEFF0F
disc_key=A3C6F188B96592651169C2939606F638
 
Last edited:
Multiman keeps freezing after launching it. It freezes on Multiman welcome logo. Anyone experiencing it also? Do you know if there's a fix to this? I am using multiMAN_04.84.00_BASE_(20190528)_[PS3HEN]
 
hello, I just wanted to comment a couple of things
1)2.02 worked perfectly on a super slim, 4.84 hybrid firmware, everyhing was fine, but I updated to 2.1.1 and hybrid tools disappeared. I tried reinstalling 2.1.1 several times, enabling han and mounting that blind thing both in the browser and in the off line tools, but I can't get hybrid tools back. enable hen is there and it seems to be working.

2)the ps3hen.bin and stackframe.bin are NOT in the 2.1.1 release zip file. maybe that's the problem?. where can I get the files?. I guess I'll go back to 2.02 meanwhile.
 
Say fellas...
We need a Update hen 3.0....
To see if ill be able to rip Dvd-R
...because my super slim cant for some reason and my dvd-R are not protected
 
Guys a need help from you.
Y have a PS3 slim 3004a model OFW 4.82 with ps3 han installed (20x games instaled)
Now y can offline activate han and play the games, y dont go online with the PS3 because y dont wont do update my firmware 4.82 OFW.

When y install the new hen for 4.82 OFW PS3HEN_2.1.1_4.82_FW.zip

will y have all my 20x games installed on the PS3 and will y able to play it?
Can the new PS3 Hen play every ISO PS3 game?
 
hello, I just wanted to comment a couple of things
1)2.02 worked perfectly on a super slim, 4.84 hybrid firmware, everyhing was fine, but I updated to 2.1.1 and hybrid tools disappeared. I tried reinstalling 2.1.1 several times, enabling han and mounting that blind thing both in the browser and in the off line tools, but I can't get hybrid tools back. enable hen is there and it seems to be working.

2)the ps3hen.bin and stackframe.bin are NOT in the 2.1.1 release zip file. maybe that's the problem?. where can I get the files?. I guess I'll go back to 2.02 meanwhile.
HFW Tools only shown on HEN Enable now!

the files are NOT missing, they are in pkg

why the hell do you think we would not include needed files?
 
Guys a need help from you.
Y have a PS3 slim 3004a model OFW 4.82 with ps3 han installed (20x games instaled)
Now y can offline activate han and play the games, y dont go online with the PS3 because y dont wont do update my firmware 4.82 OFW.

When y install the new hen for 4.82 OFW PS3HEN_2.1.1_4.82_FW.zip

will y have all my 20x games installed on the PS3 and will y able to play it?
Can the new PS3 Hen play every ISO PS3 game?

if you wish to remain 4.82 then that's fine you will be able to play all your installed games unless your activation is deleted or disabled if this is the case you would either need to re-activate via proxy while remaining on 4.82 or update to 4.84 and fresh install HFW & HEN.

PS3ISO will work 100% if you rip your own games.
 
I don't know. I checked my Mirror's Edge dumps and both keys are not match to each other (neither any simple hash from it but could be salted by something of course), so definitely they are two different things:

disc_hash_key=845D434A390342117E5DB9066BDEFF0F
disc_key=A3C6F188B96592651169C2939606F638

From what I recall, either Data 1 or Data 2 key is per disc, and this did not really matter as far as online safety was concerned.
 
Last edited:
@sandungas It is the best for PS3 users (especially when we can't have larger internal memory than as I remember 1,5GiB) but from software preservation point of view it is catastrophic because pirate sites are flooded by broken backups which have impact also on this goal.
But we have the IRD format for integrity checks :)

Sadly... at some point in the past the IRD databases was invaded by false info and fakers, and nowadays there are some IRD files in the databases that are false, but most of them can be identifyed and taken down
Ive seen some IRD files that contained the hash of the files generated by multiman, like the ones we was talking about here:
https://www.psx-place.com/threads/multiman-copy-game-to-internal-hdd-bug-or-not.24507/#post-184326
You know the files: PS3GAME.BG0, PS3GAME.BG1, PS3GAME.CHK, PS3GAME.INI, etc...

I cant imagine which kind of idiot made that, but they was about to ruin the plan completly, lucky there are not much of those false IRD files made by retarded people
 
Back
Top