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

[esc0rtd3w]

Thanks a lot the team but any news for the auto installer by @lmn7 ?

Which installer are you referring to? It's different than the 2 installers available?

 

[bguerville]

Thanks a lot the team but any news for the auto installer by @lmn7 ?

Afaik Coro is meant to update the auto hen files once the HEN updates dust settles, you just need to wait.

 

[sandungas]

@esc0rtd3w im still thinking in what i said and there are a couple of details that worths to be mentioned, better soon that later if we are trying to standarize this system to install package managers

And additionally... you need to delete all the code related to the package manager sections inside the current category_game.xml
The only thing related with the package manager that you need to keep in category_game.xml is the link to the external xml file, and you can use the alias "%flash" to short it

src="xmb://localhost/%flash/xmb/install_package_files.xml#seg_package_files

The point is that you need to minimize the amount of code related to the package manager inside category_game.xml
And instead of it we are going to use an static path to a external xml file... so the installation of a new package manager doesnt requires to modify category_game.xml... and the external xml file needs to have the same name in the default HEN instalaltion and in the "PKG addons"

So... you need to decide the 2 names in the link, the names in my example above are what i used in the "rebug package manager standalone" release
The name "seg_package_files" is an official codename, i kept it because the "final user" is not supposed to see it, and eventually for the people that reads the xml it could be handy because is used in other places of the official files

When i decided to use the other name "install_package_files.xml" i was applying the same rules... is also mentioned somewhere in the official files, but right now im changing my mind a bit
The point is this file is going to be visible to "final users" (if they takes a look at dev_flash contents with a filemanager or FTP)... and im a living proof that the most straightforward way to talk about them (in general) is just to say "package manager". I think i wrote "package manager" tenths of times in the forum in the last few days, lol
I think is better this way:

src="xmb://localhost/%flash/xmb/package_manager.xml#seg_package_files

1) Official package manager
2) Rebug package manager classic (english only)
3) Rebug package manager classic (translated, requires a custom explore_plugin_full.rco)
4) Any other you want, the only requirement is that it needs to be written in a dedicated xml file, and optionally you can include a custom explore_plugin_full.rco with custom texts and icons for it

In the default HEN installer i would use option 2)... or 1) if you want to take the minimalistic approach

The point is that 1) and 2) are not dependant of the custom explore_plugin_full.rco so are compatible with al firmware versions since 1.00 up to 9.99
And the options 3) and 4) should be distributed in PKG format... and his compatibility depends of the custom explore_plugin_full.rco version inside them

If at some point this becomes popular and there is some people creating this "addon PKG" for different flavours of package managers you could decide to include one of the first group as default (not dependant of a custom explore_plugin.rco), but in the meantime there are only 2 easy ways to do it as far i know, the official or the rebug standalone

I would keep the rebug standalone, mostly because if you use the official most people is going to go directly into intalling the "addon PKG" for the rebug package manager... so is pretty much like forcing 90% of the HEN users to install an additional PKG... so doesnt looks like a good idea to use the official package manager as default

In the long term probably it will be better to use a different package manager in the default HEN installer, no offense intended but the rebug package manager is not the summit of evolution of PS3 package managers... there is room for improvements as usually with everything

 

[Serdar]

@sandungas
Thanks to those who contributed to the production of HEN and I agree with you, I wish there was a simple HEN option with no additional features. I imagine a plain HEN with no additional lines and no menus.

I would translate all HEN content for myself but our work was in vain as no other languages are officially supported and I had to deal with retranslation each time.
Then when I got an error I got bored and quit.

The main issue here is not the language, in fact some people can be obsessed with order, which is annoying when the system is half English and half another language.

 

[DeViL303]

The point is that you need to minimize the amount of code related to the package manager inside category_game.xml
And instead of it we are going to use an static path to a external xml file...

Just want to point out that if you use that path, and the package_manager.xml is missing or not read for any reason, then the console will soft brick during start up. Fairly easy to imagine scenarios where someone might end up with the modified category_game.xml but no package_manager.xml.

I recommend use this fixed path, with the "localhost//" which adds protection against this pointless system file check.

src="xmb://localhost//dev_flash/vsh/resource/explore/xmb/package_manager.xml#seg_package_files"/>

This would probably work too but I have not tested it

src="xmb://localhost//%flash/xmb/package_manager.xml#seg_package_files

 

[SteveGW]

thanks agin for your aswome releases team, my super slim is today a happy hen!

 

[Coro]

Thanks a lot the team but any news for the auto installer by @lmn7 ?

4.89 update done!

 

[jolek]

Updated the resource.

 

[LATIF]

hi have you category_game.xml and other files explore_category_game.rco .......for 4.89 han_supportfiles

 

[bguerville]

hi have you category_game.xml and other files explore_category_game.rco .......for 4.89 han_supportfiles

The HAN legacy project has not been updated by esc0 yet.
If/when he updates it, updated support files will be available at **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) as usual and in the ps3xploit/ethanol GitHub repository.

 

[LATIF]

The HAN legacy project has not been updated by esc0 yet.
If/when he updates it, updated support files will be available at **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) as usual and in the ps3xploit/ethanol GitHub repository.

thx

 

[Px34Life]

I have installed the HFW 3 or 4 times and 1 from the recovery I install HEN enable but every time i lunch it freeze up my PS3.
Any Help

 

[chronoss]

4.89 update done!

There is offline version please...

 

[Coro]

There is offline version please...

yes. goto the release thread HERE. click on "HFW 4.89" near the end of the first post.

 

[Md Hesam]

Ultimat toolbox avaliale for HFW 4.89?

 

[chronoss]

yes. goto the release thread HERE. click on "HFW 4.89" near the end of the first post.

There is not the alternative (manuel by @lmn7 ) methode on the pack

 

[chronoss]

yes. goto the release thread HERE. click on "HFW 4.89" near the end of the first post.

haven't see the link, sorry and Thanks a lot, thanks @lmn7

 

[esc0rtd3w]

i just remembered why we had all of those extra rco files in the HEN install pkg lol . It was to overwrite the rco modified by the themes, to make them ofw again on an install. This is a huge PITA, and the themes can be updated (currently broken), but would need 4.89 versions separate, and if we keep them, the ofw rcos will have to be put back into the package, or theme colors will not be overwritten on HEN installation.

@sandungas

btw, this is the current query for package manager, and the xml was moved into, as it is now hidden on boot (until refresh issue is resolved) and loads from dev_flash/hen/xml/hen_pkg_manager_full.xml on HEN enable.

<Query
                class="type:x-xmb/folder-pixmap"
                key="seg_package_files"
                attr="seg_package_files"
                src="xmb://localhost/dev_hdd0/hen/xml/hen_pkg_manager_full.xml#seg_package_files"
                />

@sandungas @DeViL303

 

[sandungas]

i just remembered why we had all of those extra rco files in the HEN install pkg lol . It was to overwrite the rco modified by the themes, to make them ofw again on an install. This is a huge PITA, and the themes can be updated (currently broken), but would need 4.89 versions separate, and if we keep them, the ofw rcos will have to be put back into the package, or theme colors will not be overwritten on HEN installation.

In my oppinion.. is better to add a theme named "Original HEN" with the files that could be damaged by the installation of an incompatible theme
This way you dont need to include that files (only intended to repair the damage created by incompatible themes) in the default HEN installer PKG
In other words, without them the HEN PKG will be more simple, smaller in size, easyer to mantain, etc...

Btw, to find the RCO files from that themes broken in 4.89 (without need to try them) is needed to compare the filenames in everyone of them with the list of RCO files updated in 4.89 https://www.psdevwiki.com/ps3/4.89_CEX#dev_flash
The golden rule is... any custom RCO that was working fine in 4.88 but was updated in OFW 4.89 is broken... so the theme containing that RCO is broken
Else... if the theme is composed only by RCO files that was working fine in 4.88 and was not updated in OFW 4.89 then the theme is fine, there is no need to worry about it

 

[esc0rtd3w]

In my oppinion.. is better to add a theme named "Original HEN" with the files that could be damaged by the installation of an incompatible theme
This way you dont need to include that files (only intended to repair the damage created by incompatible themes) in the default HEN installer PKG
In other words, without them the HEN PKG will be more simple, smaller in size, easyer to mantain, etc...

yeah thats probably the best way. We do have a stock blue theme, which is the HEN default, so this could be used, and we can leave the extra rcos out of main installer pkg.

i am working on updating the themes for 4.89, and i also noticed that a few icons are not correct for some colors, and some themes have extra icons that have been colorized. I am extracting everything and comparing whats what from each one, then i can update them all with fixed rcos.