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

In cmd its a command not found but in mingw it is installed i believe since it gives me options and commands

And im ot sure how big the sprx is getting but when i build the henplugin folder with mingw it builds, and its only 6kb and the prx is 12kb

Make a new test batch file with this code in the HenPlugin folder and run it.
Code:
@echo off

cls

set PS3SDK=/c/PSDK3v2

set WIN_PS3SDK=C:/PSDK3v2

set PS3DEV=%PS3SDK%/ps3dev2

set PATH=%WIN_PS3SDK%/mingw/msys/1.0/bin;%WIN_PS3SDK%/mingw/bin;%PS3DEV%/ppu/bin;

set CYGWIN=C:\PSDK3v2\MinGW\msys\1.0\bin

 

rm *.prx *.sprx

%CYGWIN%\bash -i -c 'make release'

pause
When done, check whether you have a sprx file in the folder and post the entire command prompt output here.
 
Make a new test batch file with this code in the HenPlugin folder and run it.
Code:
@echo off

cls

set PS3SDK=/c/PSDK3v2

set WIN_PS3SDK=C:/PSDK3v2

set PS3DEV=%PS3SDK%/ps3dev2

set PATH=%WIN_PS3SDK%/mingw/msys/1.0/bin;%WIN_PS3SDK%/mingw/bin;%PS3DEV%/ppu/bin;

set CYGWIN=C:\PSDK3v2\MinGW\msys\1.0\bin

rm *.prx *.sprx

%CYGWIN%\bash -i -c 'make release'

pause
When done, check whether you have a sprx file in the folder and post the entire command prompt output here.
okay great this simples it down so when i ran it it created 2 *prx files first is a sprx, 70kb and second is the prx at 12kb but at the end it said scetool command not found with errors like [all] errors 127 and error 2

but i realise if you put the scetool in C:/windows and type scetool in cmd it reads the exe so as of why it still dont work is really annoying and fun

error bellow (managed to copy and paste in cmd)

make -f Makefile_release --no-print-directory
/bin/cp HENplugin.sym HENplugin.prx
/C/usr/local/cell/host-win32/bin/make_fself HENplugin.prx HENplugin.sprx
make objs/main.ppu.o objs/printf.ppu.o objs/asmcode.ppu.o
make[2]: Nothing to be done for `objs/main.ppu.o'.
make[2]: Nothing to be done for `objs/printf.ppu.o'.
make[2]: Nothing to be done for `objs/asmcode.ppu.o'.
/C/usr/local/cell/host-win32/bin/ppu-lv2-prx-strip --strip-debug --strip-section
-header HENplugin.prx
scetool -0 SELF -1 TRUE -s FALSE -2 0A -3 1070000052000001 -4 01000002 -5 APP -6
0003004000000000 -A 0001000000000000 -8 400000000000000000000000000000000000000
0000000000000000000000000 -9 00000000000000000000000000000000000000000000007B000
0000100020000 -e HENplugin.prx HENplugin.sprx
make[1]: scetool: Command not found
make[1]: *** [all] Error 127
make: *** [release] Error 2
Press any key to continue . . .
 
okay i moved the scetool to the henplugin folder and ran the bat file with the code you provided and it build successful, here

rm: cannot lstat `*.prx': No such file or directory
rm: cannot lstat `*.sprx': No such file or directory
make -f Makefile_release --no-print-directory
/bin/cp HENplugin.sym HENplugin.prx
/C/usr/local/cell/host-win32/bin/make_fself HENplugin.prx HENplugin.sprx
make objs/main.ppu.o objs/printf.ppu.o objs/asmcode.ppu.o
make[2]: Nothing to be done for `objs/main.ppu.o'.
make[2]: Nothing to be done for `objs/printf.ppu.o'.
make[2]: Nothing to be done for `objs/asmcode.ppu.o'.
/C/usr/local/cell/host-win32/bin/ppu-lv2-prx-strip --strip-debug --strip-section
-header HENplugin.prx
scetool -0 SELF -1 TRUE -s FALSE -2 0A -3 1070000052000001 -4 01000002 -5 APP -6
0003004000000000 -A 0001000000000000 -8 400000000000000000000000000000000000000
0000000000000000000000000 -9 00000000000000000000000000000000000000000000007B000
0000100020000 -e HENplugin.prx HENplugin.sprx
scetool 0.4.0 <public build> (C) 2011-2013 by naehrwert
NP local license handling (C) 2012 by flatz
*** Zlib Compression Level:-1 ***
[*] SELF built.
[*] Data compressed.
[*] Data encrypted.
[*] HENplugin.sprx written.
Press any key to continue . . .
 
okay i moved the scetool to the henplugin folder and ran the bat file with the code you provided and it build successful, here

rm: cannot lstat `*.prx': No such file or directory
rm: cannot lstat `*.sprx': No such file or directory
make -f Makefile_release --no-print-directory
/bin/cp HENplugin.sym HENplugin.prx
/C/usr/local/cell/host-win32/bin/make_fself HENplugin.prx HENplugin.sprx
make objs/main.ppu.o objs/printf.ppu.o objs/asmcode.ppu.o
make[2]: Nothing to be done for `objs/main.ppu.o'.
make[2]: Nothing to be done for `objs/printf.ppu.o'.
make[2]: Nothing to be done for `objs/asmcode.ppu.o'.
/C/usr/local/cell/host-win32/bin/ppu-lv2-prx-strip --strip-debug --strip-section
-header HENplugin.prx
scetool -0 SELF -1 TRUE -s FALSE -2 0A -3 1070000052000001 -4 01000002 -5 APP -6
0003004000000000 -A 0001000000000000 -8 400000000000000000000000000000000000000
0000000000000000000000000 -9 00000000000000000000000000000000000000000000007B000
0000100020000 -e HENplugin.prx HENplugin.sprx
scetool 0.4.0 <public build> (C) 2011-2013 by naehrwert
NP local license handling (C) 2012 by flatz
*** Zlib Compression Level:-1 ***
[*] SELF built.
[*] Data compressed.
[*] Data encrypted.
[*] HENplugin.sprx written.
Press any key to continue . . .

okay great this simples it down so when i ran it it created 2 *prx files first is a sprx, 70kb and second is the prx at 12kb but at the end it said scetool command not found with errors like [all] errors 127 and error 2

but i realise if you put the scetool in C:/windows and type scetool in cmd it reads the exe so as of why it still dont work is really annoying and fun
Here you are, if scetool fails in the command prompt, that's a problem for HenPlugin compilation because you are executing the batch file commands in the command prompt, not in the mingw terminal, you see what I mean?

You can fix this in different ways actually

1. You can add a line in the batch file to add the scetool executable folder to the PATH variable using the export command.

2. You can copy the scetool executable in the HenPlugin folder which is what you did.

3. You can add the scetool executable folder to the PATH variable directly in Windows System Environment Variables section so that scetool will always be usable from the command prompt.

Important:
Remember that scetool requires the data folder with all the keys in it to do its job.
Depending on which of the 3 setups you decide to use you may need to copy the data folder where the scetool executable is located.
"scetool -k" displays the list of keys, if the data folder cannot be found that command will error out.
 
okay sorry for the many relipes but i managed to get it to say done and i think it built correctly what i did was move the scetool to the henplugin folder and it never said anything about the scetool again so i think that error is fixed but i noticed when it built it where are the files it builds i cant see or find a PS3HEN.BIN or sprx anywhere
 
Here you are, if scetool fails in the command prompt, that's a problem for HenPlugin compilation because you are executing the batch file commands in the command prompt, not in the mingw terminal, you see what I mean?

You can fix this in different ways actually

1. You can add a line in the batch file to add the scetool executable folder to the PATH variable using the export command.

2. You can copy the scetool executable in the HenPlugin folder which is what you did.

3. You can add the scetool executable folder to the PATH variable directly in Windows System Environment Variables section so that scetool will always be usable from the command prompt.

Important:
Remember that scetool requires the data folder with all the keys in it to do its job.
Depending on which of the 3 setups you decide to use you may need to copy the data folder where the scetool executable is located.
"scetool -k" displays the list of keys, if the data folder cannot be found that command will error out.
oh okay right ill go with the 3rd on then thanks also what are the files that get made or modified is it the PS3HEN.BIN_CEX_488 files and then just rename them to PS3HEN.BIN or not
 
oh okay right ill go with the 3rd on then thanks also what are the files that get made or modified is it the PS3HEN.BIN_CEX_488 files and then just rename them to PS3HEN.BIN or not
Yep, that's the HEN package for 4.88, the batch file combines all the different parts of the project into this one package.

Note that you can compile the debug version too which can be helpful to get debug logs over UDP with socat whenever you need to investigate a problem..
 
Yep, that's the HEN package for 4.88, the batch file combines all the different parts of the project into this one package.

Note that you can compile the debug version too which can be helpful to get debug logs over UDP with socat whenever you need to investigate a problem..
oh great thank you for all your help really, i really do appreciate it
 
oh great thank you for all your help really, i really do appreciate it
You are welcome. [emoji6]

Now you are set to compile any open source homebrew, you can start tweaking code, make small modifications here and there, you can test many of the samples that come with the SDK too.
There are tools in the SDKs to create param.sfo and PKG files for deployment, alternatively you can also use the nice PKG tools from Aldo.
If you need further help with that stuff, just ask...
 
You are welcome. [emoji6]

Now you are set to compile any open source homebrew, you can start tweaking code, make small modifications here and there, you can test many of the samples that come with the SDK too.
If you need further help with that stuff, just ask...
sure will do, i know i can do anything now (so excited) again thank you for your time in helping me
 
i just rose from the dead :eek:

Ben and I are working on getting things back up to speed for 4.89.

Need to contact some old friends to see if they can help with HFW!

EDIT:
HFW is in progress. HEN is in progress.
Hello, just a stupid question. Will the updated HEN be numbered 3.1.0 just like that, or will some new functionality be added? I expected it to be 3.0.4 i.e. with a higher last number, which shows that hyung has been updated to work with the newer HFW as it was before
 
Hello, just a stupid question. Will the updated HEN be numbered 3.1.0 just like that, or will some new functionality be added? I expected it to be 3.0.4 i.e. with a higher last number, which shows that hyung has been updated to work with the newer HFW as it was before
There are a few reasons the version number will be 3.1.0. This is not just a version number change for HFW support, and does have a couple new features added, including act.dat restore, and small HFW Tools updates.

Another reason is because there are beta testing pkgs that are in the wild that have the 3.0.4 versioning, and this will be less confusing moving forward.

The final reason is that 4.89 brought some unexpected changes, so i anticipate there will be a couple minor revisions to the 3.1.0 base, i.e. RemotePlay mainly.

There are also many HFW builds now floating around, so the official one will distinguish itself from others as well.

Both are in testing right now, and i expect releases this week.
 
There are a few reasons the version number will be 3.1.0. This is not just a version number change for HFW support, and does have a couple new features added, including act.dat restore, and small HFW Tools updates.

Another reason is because there are beta testing pkgs that are in the wild that have the 3.0.4 versioning, and this will be less confusing moving forward.

The final reason is that 4.89 brought some unexpected changes, so i anticipate there will be a couple minor revisions to the 3.1.0 base, i.e. RemotePlay mainly.

There are also many HFW builds now floating around, so the official one will distinguish itself from others as well.

Both are in testing right now, and i expect releases this week.
What about the find from zecoxao? Can your hyun help with research to find vulnerabilities and the theoretical possibility of creating cfw on 3000/4000 ps3?
 
What about the find from zecoxao? Can your hyun help with research to find vulnerabilities and the theoretical possibility of creating cfw on 3000/4000 ps3?
What find would that be exactly?

You know, if the problem was that simple, CFWs would already exist for those models.

Finding a vulnerability to exploit at a lower level than lv2 requires research, reverse engineering and testing, you need skills and also a good working knowledge of lv0 and lv1 which extremely few active PS3 devs and hackers actually possess btw.

I believe it's feasible, after all that's the ultimate objective of my PS3 Toolset project, or the targeted end game if you prefer, but it won't be done overnight, the problem is time and dedication.
esc0 and I have already invested a lot of both to get where we are, what you are asking esc0 to do amounts to asking him to invest hundreds more hours of his free time into it to acquire the skills and apply them in the hope he succeeds while still maintaining existing releases, managing the hosting, the repos, the tech support, the finances etc..
Maybe other people could start helping out too, we are nothing special, anyone can learn the needed skills and do their part for the community rather than count on others to sort everything out.
 
Last edited:
PS3HEN 3.1.0 Released

OP Updated

Website will be updated soon. All files are live on server.

CHANGELOG

HEN Plugin Changes
- Updated To Support 4.89 HFW
- Added act.dat Backup/Restore feature (thanks @bucanero )
Payload Changes

- Updated To Support 4.89 HFW
- COBRA PS3MAPI Changes
- Updated To Identify 4.89 Firmware
Resource Changes

- Added Dump PSID option to HFW Tools
- Added Toggle Automatic Update option to HFW Tools
- Updated text on Theme Selector in HFW Tools
- Added new icons for updated HFW Tools options (thanks @xps3riments )
- Updated RCO files to fix display issues with 4.89 only (thanks @sandungas )
- explore_plugin_full.rco: 44292838814555627FC8F9F9CB632CD8
- software_update_plugin.rco: D1FAF469796E6894AA1CECCFAC7895EF
- Updated layout_grid_table files for 480p and 272p to fix display issues in Remote Play with 4.89 only (thanks @sandungas )
 
Last edited:
@bguerville bro do you have an update forecast for bgtoolset for those who have a CFW compatible model and are stuck on OFW 4.89 and want to go back to cfw?, sorry for the question and thanks for everything you do for the ps3 community!
 
Back
Top