• 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 can install my fix (unsigned), HEN installer (signed), wMM and prepISO pkgs while having original 4.89 file installed just fine. It was done from usb000/packages.

The only broken thing that's I'm aware is this (infinite loading until you run the HEN):
l5VuNPy.png

I think the package manager should only be loaded when Hen is started, just like the hfw tools
 
Thanks for all the input guys :) Apparently we have an issue with explore_plugin.sprx, which i never looked into switching them from the current DEX one to test Package Manager. I assumed this was needed and its always worked before. I still have not replicated the bugs yet, but I see the trophies, and other XMB items are not correct from peoples screenshots.

I guess we just figure out another way to fix this problem. Starting with replacing the original 4.89 explore_plugin seems like a good start, i suppose.

I can make a new thread for HEN problems so we can keep them all organized and in some kind of order.

This will require plenty of testing and feedback, but since 3.1.0 is already released, we can have some kind of open beta test lol :)

I think this is only a problem on 4.89, unless others see issues on older firmware.
 
I can make a new thread for HEN problems so we can keep them all organized and in some kind of order.
I know about this problem till beta HEN, but can't say about that because I don't have access to the dev section and was banned for posting screenshots from beta HEN. So, public thread will be great idea.
 
Thanks for all the input guys :) Apparently we have an issue with explore_plugin.sprx, which i never looked into switching them from the current DEX one to test Package Manager. I assumed this was needed and its always worked before. I still have not replicated the bugs yet, but I see the trophies, and other XMB items are not correct from peoples screenshots.

I guess we just figure out another way to fix this problem. Starting with replacing the original 4.89 explore_plugin seems like a good start, i suppose.

I can make a new thread for HEN problems so we can keep them all organized and in some kind of order.

This will require plenty of testing and feedback, but since 3.1.0 is already released, we can have some kind of open beta test lol :)

I think this is only a problem on 4.89, unless others see issues on older firmware.

Apparently, using the 4.89 explorer_plugin fixed every issue.

It's only on 4,89 due to the internal "xml" overrides in the new sprx
 
I know about this problem till beta HEN, but can't say about that because I don't have access to the dev section and was banned for posting screenshots from beta HEN. So, public thread will be great idea.
bug reports are okay in public threads. i won't delete them...unless they are about my own releases. :)

the dev section is not really used very much. many normal users here are happy to beta test. sometimes it is better to post there first (like if the homebrew could cause brick).
 
I can install my fix (unsigned), HEN installer (signed), wMM and prepISO pkgs while having original 4.89 file installed just fine. It was done from usb000/packages.

The only broken thing that's I'm aware is this (infinite loading until you run the HEN):
l5VuNPy.png
You say you can install PKG files, we are happy for you but...
Why don't you explain things properly?
Do you mean using the original CEX files?
And you don't have any other problems with the Package Manager items when HEN is not enabled? Because afair using CEX files for this has been tried long ago and found problematic because some stuff wasn't working right.
Or using some other trick?

At the end of the day, if you're so clever and so skilled, why don't you take that open source project over in the first place?
Release both HFWs and PRs for HEN updates in the future?
Do the jobs that we always end up having to do because nobody else is willing to do them, although they're more than willing to comment on the job done.
We would welcome such a move, it would free our time and we could focus on other things like new exploits.

Personally I am not interested in HEN maintenance, it's not my project, if it were, it would never have been released in that state from the very start, there would be no HFW and no DEX files deployed and this conversation wouldn't have happened.
 
Last edited:
Btw I just installed the original explorer_plugin.srpx and my package manager/installer is still working as it should.

I didn't understand the point of using dex, from what i read i thought it was necessary for pkgs installation.

@sandungas @bguerville @esc0rtdew
Those things were chosen and implemented at the time by people who are no longer active, we took them at their words, if they reused this DEX file, they will have had their reasons.
Is all this still necessary now with HEN?
Maybe not, I dunno. Testing is required.
 
Those things were chosen and implemented at the time by people who are no longer active, we took them at their words, if they reused this DEX file, they will have had their reasons.
Is all this still necessary now with HEN?
Maybe not, I dunno. Testing is required.

I found the issue, using the official sprx intead of the DEX one the "STANDARD" folder is missing with the spinning icon and the system stutters a little while on it, but only when hen is disabled.

The solution i found is to hide the package manager (there is no point having it while hen is disabled) when hen is disabled and only shows when enabled.

All the issues are now gone.
 
Last edited:
I found the issue, using the official sprx intead of the DEX one the "STANDARD" folder is missing with the spinning icon and the system stutters a little while on it, but only when hen is disabled.

The solution i found is to hide the package manager (there is no point having it while hen is disabled) when hen is disabled and only shows when enabled.

All the issues is now gone.
Ok but have you tested all the features?
Not just local PKG installation from USB but the other package manager features including the downloaded PKG stuff?
We need to be thorough about this.
If we can remove the DEX stuff without any impact whatsoever, we shall do that.
 
Ok but have you tested all the features?
Not just local PKG installation from USB but the other package manager features including the downloaded PKG stuff?
We need to be thorough about this.
If we can remove the DEX stuff without any impact whatsoever, we shall do that.

I tested my custom pkGs and official ones.

Edit: I just tested downloading from XMB entries, all working fine
 
Ok but have you tested all the features?
Not just local PKG installation from USB but the other package manager features including the downloaded PKG stuff?
We need to be thorough about this.
If we can remove the DEX stuff without any impact whatsoever, we shall do that.

BTW, I've released some unofficial builds of Hen and made a thread for it, just to make sure there are no issues
 
I tested my custom pkGs and official ones.

Edit: I just tested downloading from XMB entries, all working fine
What about the downloaded stuff that goes into a temporary folder waiting for deployment and which gets deleted after PKG deployment? Is all this stuff still working as expected?
 
What about the downloaded stuff that goes into a temporary folder waiting for deployment and which gets deleted after PKG deployment? Is all this stuff still working as expected?

Yeap, game bubbles are working (downloaded with pkgi)

They install and automatically gets deleted just fine
 
Yeap, game bubbles are working (downloaded with pkgi)

They install and automatically gets deleted just fine
That's good news.
But it's like I said, it requires more testing, there could be other issues including some that may arise only in specific situations.
If it works out though, we should integrate those changes and get rid of the DEX files, I have ALWAYS said that using DEX files in HEN was not a good idea and that problems would eventually arise with that practice at some point since we cannot get updated versions.
 
At the end of the day, if you're so clever and so skilled, why don't you take that open source project over in the first place?
Release both HFWs and PRs for HEN updates in the future?
I need some time to try to understand how HEN works. Both HFW and sprx fix was done from PC without touching source code of the HEN. I will share new HFW if/when new OFW is released for sure. Already checked all OFWs for the silk_webkit file. It appears in the 4.10 and was updated in 4.50 and 4.83 for a second time.
 
Back
Top