• PS3HEN is now supporting 4.93 Firmware

    View Official Release Post for additional information HERE

[UNOFFICIAL] PS3HEN Alternate Builds

@bucanero can you update the cobra?
there are some 8.3 builds on Evilnat's github for older firmwares (rex included but i have not heard of new rex pup).

(if you mean adding what was added to hen above, it is not needed. the change was to work around act.dat being deleted on booting HFW.)
 
there are some 8.3 builds on Evilnat's github for older firmwares (rex included but i have not heard of new rex pup).

(if you mean adding what was added to hen above, it is not needed. the change was to work around act.dat being deleted on booting HFW.)

I meant, if @bucanero could update the current HEN cobra v8.1 to v8.3 :P
 
@bucanero

I'm having a issue with your code, i use it with a modification to reload all the categories as seen below:

ClUXiDN.png


It works good in the original source but when adding your code it does not work.

I tried downloading your main.c and just adding the code changes you made, both of them break it.

Any ideia?
 
@bucanero

I found where it broke

If i add the

// restore act.dat from act.bak backup
restore_act_dat();

it stops to reload all categories, but somehow the game and network still reload, even though I remove them to reload in code.


YEfQnAt.png





EDIT

I moved it down a bit after reload_xmb(); and now everything is working, but i wonder if it can interrupt other processes

SBgHy3J.png
 
Last edited:
For those who want to test, I have built the PS3HEN.BIN for all the HFW currently supported (4.84, 85, 86, 87, 88), with the improved plugin that restores act.dat (and the option to disable update check):
https://www.mediafire.com/file/2em2mto1ywar69x/PS3HEN_BIN-act.zip/file

Just download the zip, and replace your PS3HEN.BIN with the right file (e.g. PS3HEN.BIN_CEX_486 -> PS3HEN.BIN)

Note: to disable the online update check, you need to create an empty file: /dev_hdd0/hen_updater.off
@bucanero

J'ai installé votre version du "PS3HEN.BIN" sur mes consoles Slim et SuperSlim (CECH-3004, CECH-4004 et CECH-4204C) toutes sous le HEN-3.0.3 et le lancement des jeux PS2 ne se fait plus, il y a blocage sur un écran noir après le lancement du PS2 Classic PlaceHolder. Aucune touche de la manette n'est efficace, seul un arrêt forcé par la touche idoine de la PS3 stoppe la PS3 au bout d'un certain temps de laisser appuyé le doigt dessus. La console peut être re-démarrée sans contrôle des données au préalable.

Je ne possède plus l'original du fichier "PS3HEN.BIN" pour mon installation du HFW-4.88.1, pouvez-vous me le faire passer par un DL avant que vous ne corrigiez ce problème ???

Merci par avance.


In English via G-Trad :

I installed your version of "PS3HEN.BIN" on my Slim and SuperSlim consoles (CECH-3004, CECH-4004 and CECH-4204C) all under HEN-3.0.3 and the launch of PS2 games is no longer done, there is a crash on a black screen after launching the PS2 Classic PlaceHolder. No button on the controller is effective, only a forced stop by the appropriate button of the PS3 stops the PS3 after a certain time of leaving the finger pressed on it. The console can be restarted without checking the data first.

I no longer have the original "PS3HEN.BIN" file for my HFW-4.88.1 installation, can you pass it to me through a DL before you correct this problem ???

Thanks in advance.
 
@bucanero

J'ai installé votre version du "PS3HEN.BIN" sur mes consoles Slim et SuperSlim (CECH-3004, CECH-4004 et CECH-4204C) toutes sous le HEN-3.0.3 et le lancement des jeux PS2 ne se fait plus, il y a blocage sur un écran noir après le lancement du PS2 Classic PlaceHolder. Aucune touche de la manette n'est efficace, seul un arrêt forcé par la touche idoine de la PS3 stoppe la PS3 au bout d'un certain temps de laisser appuyé le doigt dessus. La console peut être re-démarrée sans contrôle des données au préalable.

Je ne possède plus l'original du fichier "PS3HEN.BIN" pour mon installation du HFW-4.88.1, pouvez-vous me le faire passer par un DL avant que vous ne corrigiez ce problème ???

Merci par avance.


In English via G-Trad :

I installed your version of "PS3HEN.BIN" on my Slim and SuperSlim consoles (CECH-3004, CECH-4004 and CECH-4204C) all under HEN-3.0.3 and the launch of PS2 games is no longer done, there is a crash on a black screen after launching the PS2 Classic PlaceHolder. No button on the controller is effective, only a forced stop by the appropriate button of the PS3 stops the PS3 after a certain time of leaving the finger pressed on it. The console can be restarted without checking the data first.

I no longer have the original "PS3HEN.BIN" file for my HFW-4.88.1 installation, can you pass it to me through a DL before you correct this problem ???

Thanks in advance.
you can download from github HERE and rename to PS3HEN.BIN. or you can reinstall HEN.
 
you can download from github HERE and rename to PS3HEN.BIN. or you can reinstall HEN.
Est-ce l'original installé par l'installateur du HEN ou est-ce votre modification que je télécharge via ce lien ???

Is this the original installed by the installer of the HEN or is it your modification which I download through this link ???
 
Est-ce l'original installé par l'installateur du HEN ou est-ce votre modification que je télécharge via ce lien ???

Is this the original installed by the installer of the HEN or is it your modification which I download through this link ???
original
 
@esc0rtd3w @bguerville

I saw a pull request in the PS3XPLOIT git hub (see here) to clear the browser auth_cache/history/cookies on everyboot, is it worth? does it impacts the HEN activation?
What is this for exactly?
The PR information is unclear to me.
"Cleaning browser junk files on boot" is not exactly an accurate description either, cookies/history isn't junk..

If it's to help with exploit initialization, HEN uses no cookies, clearing them or not changes nothing, same thing for authentication data & for history.
In conclusion, the code proposed in PR is absolutely pointless when it comes to helping with exploit init issues.

And if it's to remove traces of HEN in the browser files then you should only need to delete the history file however I assume you would lose the entire browser history for that user profile, not exactly ideal.. It may be better in that case to edit the xml & remove only the exploit page entries...

I don't maintain HEN but if I did I would not approve this PR, at least not as-is & not without further clarifications regarding its purpose.
 
Last edited:
What is this for exactly?
The PR information is unclear to me.
"Cleaning browser junk files on boot" is not exactly an accurate description either, cookies/history isn't junk..

If it's to help with exploit initialization, HEN uses no cookies, clearing them or not changes nothing, same thing for authentication data & for history.
In conclusion, the code proposed in PR is absolutely pointless when it comes to helping with exploit init issues.

And if it's to remove traces of HEN in the browser files then you should only need to delete the history file however I assume you would lose the entire browser history for that user profile, not exactly ideal.. It may be better in that case to edit the xml & remove only the exploit page entries...

I don't maintain HEN but if I did I would not approve this PR, at least not as-is & not without further clarifications regarding its purpose.

Most of the people thinks that cleaning the web browser cookies/cache solves HEN Failures and make it more stable, so probably is what the PR is for.
 
Most of the people thinks that cleaning the web browser cookies/cache solves HEN Failures and make it more stable, so probably is what the PR is for.
I know, that's why I mentioned it.

Those myths were built upon the steps we asked people to follow when the very first ps3xploit dump tool was being tested years ago.

At the time we were already experiencing exploit init issues & we were not sure whether certain browser features could impact the exploitation init process.
We had noticed that browsing other pages before starting the exploit would guarantee exploit init failures, so in order to get the best results we recommended to everyone to use a clean browser ie a freshly opened browser on blank homepage with clean cookies & clean cache.
By the time the second ps3xploit tool came out, we had already confirmed that cookies & cache were irrelevant, the only thing that was important was not to browse a single web page before loading the exploit.
But it was too late, those first instructions went viral from the moment the first test files got leaked, YT vids were made detailing those steps so when the first release came out, people experiencing exploit init issues & looking for ways to avoid them stumbled upon the first testing instructions which then spread to become this widespread myth it is today, believed by thousands & thousands of people.

Amazing how humans are so easily misled, isn't it?
 
@Coro

Je te confirme que c'est bien ta version du HEN qui empêchait le bon fonctionnement du lancement des jeux PS2 dans toutes mes PS3 sous le "HEN-3.0.3+". Si tu peux corriger cette erreur, cela serait excellent.
Un énorme MERCI pour ce que tu réalises pour toute la communauté PS3 (et autres ...).

English:
I confirm that it is indeed your version of the HEN which prevented the proper functioning of the launch of the PS2 games in all my PS3 under the "HEN-3.0.3 +". If you can correct this error, that would be great. A huge THANK YOU for what you do for the entire PS3 community (and others ...).
 
Last edited by a moderator:
  • Like
Reactions: Zar
@bucanero
I installed your version of "PS3HEN.BIN" on my Slim and SuperSlim consoles (CECH-3004, CECH-4004 and CECH-4204C) all under HEN-3.0.3 and the launch of PS2 games is no longer done, there is a crash on a black screen after launching the PS2 Classic PlaceHolder. No button on the controller is effective, only a forced stop by the appropriate button of the PS3 stops the PS3 after a certain time of leaving the finger pressed on it. The console can be restarted without checking the data first.

I no longer have the original "PS3HEN.BIN" file for my HFW-4.88.1 installation, can you pass it to me through a DL before you correct this problem ???

Thanks in advance.

mmm... that's weird because the change was only on the plugin (and the plugin unloads shortly after showing the HEN notification pop up). It shouldn't have an impact on the ps2 classics, but anyways, you can get the original binary file from ps3xploit here:
https://github.com/PS3Xploit/PS3HEN/raw/master/PS3HEN.BIN_CEX_488

maybe the act.dat link to act.bak has some effect on the ps2classic launcher? do you have any offline account activated with Apollo (act.bak) on your PS3s?
as I said, my change was at the hen plugin level, not at the payload/cobra that should be handling launching other stuff... but I'm not an expert here so I might have missed something.
 
@bucanero

EDIT

I moved it down a bit after reload_xmb(); and now everything is working, but i wonder if it can interrupt other processes

wow, nice weird finding, I wonder if the link syscall could have such effect??

from my understanding, the restore_act_dat() method shouldn't impact reload_xmb(), but from your tests it actually made a difference. I wasn't sure myself of the best place to call restore_act_dat(), so when I have a chance I'll update my PR and move it down after reload_xmb() just like you did.

thanks for testing
 
@Coro

Je te confirme que c'est bien ta version du HEN qui empêchait le bon fonctionnement du lancement des jeux PS2 dans toutes mes PS3 sous le "HEN-3.0.3+". Si tu peux corriger cette erreur, cela serait excellent.
Un énorme MERCI pour ce que tu réalises pour toute la communauté PS3 (et autres ...).

English:
I confirm that it is indeed your version of the HEN which prevented the proper functioning of the launch of the PS2 games in all my PS3 under the "HEN-3.0.3 +". If you can correct this error, that would be great. A huge THANK YOU for what you do for the entire PS3 community (and others ...).
if it says "3.0.3 +" when HEN starts, then it is not mine.

the bt mod will say "HEN 3.0.3 (BTGA)". the mod with disabled automatic updates will say "HEN 3.0.3 (NOAU)" . the act.dat test build will say "HEN 3.0.3 (actdat)". i have not made any others for 3.0.3

@Valk has a 3.0.2 + on github but he never made 3.0.3 that i am aware of. his repository and at least one more has my name on it but it is not mine. they cloned my repository then made changes but did not change the name.

can you send me the BIN file?
 
mmm... that's weird because the change was only on the plugin (and the plugin unloads shortly after showing the HEN notification pop up). It shouldn't have an impact on the ps2 classics, but anyways, you can get the original binary file from ps3xploit here:
https://github.com/PS3Xploit/PS3HEN/raw/master/PS3HEN.BIN_CEX_488

maybe the act.dat link to act.bak has some effect on the ps2classic launcher? do you have any offline account activated with Apollo (act.bak) on your PS3s?
as I said, my change was at the hen plugin level, not at the payload/cobra that should be handling launching other stuff... but I'm not an expert here so I might have missed something.
En effet, j'ai des comptes PSN activés (donc des act.dat/act.bak) mais non-connectés sur les deux principales PS3 (les deux SuperSlim), le souci est différent sur la Slim (CECH-3004B). Se peut-il que le souci soit lié aussi à une interférence avec le webMAN-Mod (v1.47.36) actuel ??? Dans ce cas, il va falloir vérifier cela avec @aldostools !!!

Indeed, I have activated PSN accounts (therefore act.dat / act.bak) but not connected on the two main PS3s (both SuperSlim), the problem is different on the Slim (CECH-3004B). Could it be that the problem is also related to an interference with the current webMAN-Mod (v1.47.36) ??? In this case, we will have to verify this with @aldostools !!!
 
if it says "3.0.3 +" when HEN starts, then it is not mine.

the bt mod will say "HEN 3.0.3 (BTGA)". the mod with disabled automatic updates will say "HEN 3.0.3 (NOAU)" . the act.dat test build will say "HEN 3.0.3 (actdat)". i have not made any others for 3.0.3

@Valk has a 3.0.2 + on github but he never made 3.0.3 that i am aware of. his repository and at least one more has my name on it but it is not mine. they cloned my repository then made changes but did not change the name.

can you send me the BIN file?
En effet, ce n'est pas le tien mais celui de @bucanero que j'ai téléchargé via le lien de la page #79, donc c'est celui de Buk qui n'est pas bon. J'attend qu'il réagisse aux soucis créés via sa modification. Je suis désolé de t'avoir dérangé @Coro ...

Indeed, it's not yours but the one from @bucanero that I downloaded via the link on page #79, so it's Buk's that is not good. I am waiting for him to react to the concerns created by his modification. I'm sorry I bothered you @Coro ...
 
Back
Top