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

Go to download
Overview Extra info Updates (8) Reviews (1) History Discussion
i want to install hen on my second ps3 superslim im on 4.86 i see the hen alternative installer option has been removed i tried the first method numerous times now it show welcome to hen but theres no hen installed HFW i installed twice from the safemode other methods do not work i have been usin alternative installer for a long time now
 
KevinF said:
could someone explain to me why the hen needs hfw to be installed pls?
Click to expand...
The firmware has many "parts" inside, the most important wasn't changed, but the smaller simpler part was.

This part has the Hen exploit, Sony patched it, these amazing people just change this small part so that we can keep using the same old exploit.

Of course it's very complicated, I wouldn't even know where to start if I wanted to do something similar.
 
The HFW story is not very difficult to grasp.
On the one hand, Joonie realised it was possible to repack different /dev_flash files into an OFW PUP & the system would not notice the difference on installation.
Of course, any executable file has to be officially signed & not revoked, you can only repack official executable files from earlier ofw versions otherwise depending on the files swapped you would get a brick at worst or a dysfunctional OS at best.

On the other hand, in 4.83, Sony patched the parseFloat vulnerability exploited by the first wave of ps3xploit releases.
Using the trick described above, Joonie thought to repack post 4.82 pup files with the official 4.82 silk_webkit.sprx file which contained the vulnerability that sony eventually patched after 4.82.

That's the extent of the changes in HFW releases. The firmware is identical to OFW, it does not allow anything else than let people use the parseFloat vulnerability based ps3xploit tools in post 4.82 OFW.

HEN relies on HFW because it still uses the old parseFloat vulnerability to take control of userland execution & execute a ROP chain that in turn triggers the HEN kernel exploit that allows HEN to install & run its mini Cobra payload. If it used another userland exploit, HEN would no longer need HFW.
 
Last edited:
bguerville said:
The HFW story is not very difficult to grasp.
On the one hand, Joonie realised it was possible to repack different /dev_flash files into an OFW PUP & the system would not notice the difference on installation.
Of course, any executable file has to be officially signed & not revoked, you can only repack official executable files from earlier ofw versions otherwise depending on the files swapped you would get a brick at worst or a dysfunctional OS at best.

On the other hand, in 4.83, Sony patched the parseFloat vulnerability exploited by the first wave of ps3xploit releases.
Using the trick described above, Joonie thought to repack post 4.82 pup files with the official 4.82 silk_webkit.sprx file which contained the vulnerability that sony eventually patched after 4.82.

That's the extent of the changes in HFW releases. The firmware is identical to OFW, it does not allow anything else than let people use the parseFloat vulnerability based ps3xploit tools in post 4.82 OFW.

HEN relies on HFW because it still uses the old parseFloat vulnerability to take control of userland execution & execute a ROP chain that in turn triggers the HEN kernel exploit that allows HEN to install & run its mini Cobra payload. If it used another userland exploit, HEN would no longer need HFW.
Click to expand...
can you explain briefly, how to create a 4.86 Hybrid FirmWare, from a 4.86 ofw? we will need the puad gui am I right?

edit: I've been watching how to make cfw from Bobby Downgrades, but I can't find any tutorial about Hybrid FirmWare, could you help me pls?
 
I don't know any tutorial to make HFW, it's probably because there isn't much of a use for one. HFWs have already been released for each firmware version > 4.82 and being only a mean to an end, there is no need for variants.

Anyway, you can use PUADGUI to extract PUP contents, there are also various CLI tools to do it. The same tools can be used to repack extracted contents into a PUP file.

Inside a PUP package, the /dev_flash files are packed in a series of numbered tar files found inside update_files.tar. PUADGUI can unpack them all for you. In one of them, you will find silk_webkit.sprx.
In post 4.82 OFW, that's the tar file that needs to be repacked with the 4.82 silk_webkit.sprx to make a HFW. Then you need to repack the PUP correctly & you have your HFW.
In theory, you can repack a number of other files including xml files related to XMB but without custom sprx files to call there is little point, you can always experiment though however I recommend to
1. stick to /dev_flash files.
2. leave vsh.self alone
3. experiment on NOR consoles only, if something goes wrong you can always reformat the hdd to wipe /dev_flash in case of soft brick.

PUADGUI does the extraction/packing work behind the scenes but if you are interested in the details, here is kakaroto's code related to PUP files creation/extraction:
https://github.com/omgneeq/ps3utils
In it, among other things, you will find a fix_tar app to ensure the validity of tar files header being used by the PUP.

Here is some info about the PUP structure:
https://www.psdevwiki.com/ps3/Playstation_Update_Package_(PUP)#PS3

For PUADGUI (and most PC tools for ps3 system file handling), I recommend updating the keys, otherwise certain features won't work correctly when handling the latest firmware files.
Overall there are 2 systems that apps may use to handle ps3 keys (typically keys are located in a folder named "data" but some apps use a different name).

1. All keys are in one big "keys" file
2. Each key has its own file

Depending on the app, you need to either update the keys file or add the files corresponding to new keys in the folder.

Here is info about the keys:
https://www.psdevwiki.com/ps3/Keys

Here is the updated keys file in a zip (you need to unzip the archive of course). If you need the other format (each key its own file), you will need to either create them yourself or try to find a git repo with updated key files. Keys from 4.82 to 4.86 are all identical so if you have key files up to 4.82 you can just copy them & rename them appropriately.

View attachment keys.zip
 
Last edited:
bguerville said:
I don't know any tutorial to make HFW, it's probably because there isn't much of a use for one. HFWs have already been released for each firmware version > 4.82 and being only a mean to an end, there is no need for variants.

Anyway, you can use PUADGUI to extract PUP contents, there are also various CLI tools to do it. The same tools can be used to repack extracted contents into a PUP file.

Inside a PUP package, the /dev_flash files are packed in a series of numbered tar files found inside update_files.tar. PUADGUI can unpack them all for you. In one of them, you will find silk_webkit.sprx.
In post 4.82 OFW, that's the tar file that needs to be repacked with the 4.82 silk_webkit.sprx to make a HFW. Then you need to repack the PUP correctly & you have your HFW.
In theory, you can repack a number of other files including xml files related to XMB but without custom sprx files to call there is little point, you can always experiment though however I recommend to
1. stick to /dev_flash files.
2. leave vsh.self alone
3. experiment on NOR consoles only, if something goes wrong you can always reformat the hdd to wipe /dev_flash in case of soft brick.

PUADGUI does the extraction/packing work behind the scenes but if you are interested in the details, here is kakaroto's code related to PUP files creation/extraction:
https://github.com/omgneeq/ps3utils
In it, among other things, you will find a fix_tar app to ensure the validity of tar files header being used by the PUP.

Here is some info about the PUP structure:
https://www.psdevwiki.com/ps3/Playstation_Update_Package_(PUP)#PS3

For PUADGUI (and most PC tools for ps3 system file handling), I recommend updating the keys, otherwise certain features won't work correctly when handling the latest firmware files.
Overall there are 2 systems that apps may use to handle ps3 keys (typically keys are located in a folder named "data" but some apps use a different name).

1. All keys are in one big "keys" file
2. Each key has its own file

Depending on the app, you need to either update the keys file or add the files corresponding to new keys in the folder.

Here is info about the keys:
https://www.psdevwiki.com/ps3/Keys

Here is the updated keys file in a zip (you need to unzip the archive of course). If you need the other format (each key its own file), you will need to either create them yourself or try to find a git repo with updated key files. Keys from 4.82 to 4.86 are all identical so if you have key files up to 4.82 you can just copy them & rename them appropriately.

View attachment 27520
Click to expand...
thank you
 
welcome friends

I would like to ask you for help with this problem, probably related to HEN 4.86. I have a problem with running multiman and/or irisman.

The installation of HEN runs smoothly, but when I try to run multiman or irisman the console crashes. You can see that applications start to run because the HDD diode flashes but ends up with a black screen. Pressing the power button causes the green diode to blink and after a few seconds the console will beep several times and the diode will continue blinking. Only holding the power button for more than 10 seconds will turn off the console. Of course, it is also the case that both applications start normally and I can then start games etc.

I have already tried different things. I reloaded the original soft, then HEN again, formatted the HDD, restored the factory settings. No success. Still sneaking in on the randomness of multiman and irisman startup.

I tried it on two SUPERSLIM 4004 and 4200. The same effect on both.
 
zaodrze244 said:
welcome friends

I would like to ask you for help with this problem, probably related to HEN 4.86. I have a problem with running multiman and/or irisman.

The installation of HEN runs smoothly, but when I try to run multiman or irisman the console crashes. You can see that applications start to run because the HDD diode flashes but ends up with a black screen. Pressing the power button causes the green diode to blink and after a few seconds the console will beep several times and the diode will continue blinking. Only holding the power button for more than 10 seconds will turn off the console. Of course, it is also the case that both applications start normally and I can then start games etc.

I have already tried different things. I reloaded the original soft, then HEN again, formatted the HDD, restored the factory settings. No success. Still sneaking in on the randomness of multiman and irisman startup.

I tried it on two SUPERSLIM 4004 and 4200. The same effect on both.
Click to expand...
The blackscreen issue could also be caused by other applications interfering with the homebrews. What else do you have installed on your console?
 
zaodrze244 said:
Nothing else I have installed. Only multiman and irisman. If I installed only one of them the effect was the same black screen. So they do not interfere with each other.

After writing this post I found this thread https://www.psx-place.com/threads/when-is-the-official-multiman-for-4-86-1-hfw.30372/ . I will be home in about 6 hours and I will try to control the fan maybe it will help something.
Click to expand...
Sometimes, Webman Mod does cause blackscreen issues when launching other homebrews if fan mode is set to Dynamic auto. Since, you do no have it installed, i believe that is not what's causing it. You can still try it anyway and see if it works.

If it doesn't, i suggest you reinstall HFW and HEN. Also try the HEN Edition of Multiman and Irisman.
 
zaodrze244 said:
Nothing else I have installed. Only multiman and irisman. If I installed only one of them the effect was the same black screen. So they do not interfere with each other.

After writing this post I found this thread https://www.psx-place.com/threads/when-is-the-official-multiman-for-4-86-1-hfw.30372/ . I will be home in about 6 hours and I will try to control the fan maybe it will help something.
Click to expand...

Try downloading & installing the latest build of webMAN MOD 1.47.30. In a recent commit I improved the compatibility of the fan control in HEN delaying the fan control when a game/homebrew start.
 
Thanks for your suggestions. I tried what you suggested earlier but without success.

However, surprisingly the installation of the webman helped. With the webman running I could run mutliman and irisman without black screens.

Moreover I uninstalled the mutliman because I liked the webman more. I left Irisman for the sake of file manager looking like a good old norton commander.

I set the webman's fan control to SYSCOM and with this setting irisman works.

I'm new to HEN and other applications so I'm just discovering their capabilities and learning everything.

Great that there are people who take their time to create such applications, I am very grateful to them. Great job.

I mounted in my PS3 SuperSlim 4200, 1TB SSD :) and copied 60 game titles that I haven't managed to play yet. With SSD and HEN on board, playing on PS3 is pure pleasure. The console works very quietly without a noisy disc in the drive.
 
aldostools said:
Try downloading & installing the latest build of webMAN MOD 1.47.30. In a recent commit I improved the compatibility of the fan control in HEN delaying the fan control when a game/homebrew start.
Click to expand...
I have tried the 1.47.30 version, but the black screen still appears
 
psdavx said:
I have tried the 1.47.30 version, but the black screen still appears
Click to expand...
I think we shouldn't blame wMM, as a PS3 mechanic I have faced various PS3s, some have installed wMM with Auto Dynamic Fan Control + multiMAN HEN MOD by Joonie working normally, some are not.

Even without installing wMM, sometimes multiMAN/mmCM blanks.
 
You must log in or register to reply here.

Similar threads

Back
Top