PS3HEN (4.91 UPDATE) Auto HEN Installer by lmn7

esc0rtd3w said:
we were discussing the issue last night. That commit is just on github. We can't just apply that update to 3.2.0 release.

I think for now I will upload to the server a p3t bin that does not check the boot plugins text files at all. This way the release files are not touched, but just the installer bin will not check them anymore, but once installed it will behave as normal.

I can test and upload tonight when I get home.
Click to expand...
i was using R2 last night because i forgot to update webman first. is there a button that skips boot_plugins.txt but still runs henplugin.sprx?
 
esc0rtd3w said:
we were discussing the issue last night. That commit is just on github. We can't just apply that update to 3.2.0 release.

I think for now I will upload to the server a p3t bin that does not check the boot plugins text files at all. This way the release files are not touched, but just the installer bin will not check them anymore, but once installed it will behave as normal.

I can test and upload tonight when I get home.
Click to expand...

Most of the people including newbies will still get stuck when enabling hen, i really think this time it needs to include a empty boot_plugins.txt in the installation process

Edit: I think the hen installer script must delete the boot_plugin.txt as webMAN MOD installer will not create the boot_plugins.txt if it exists, so it will not enable after installed. (if a empty boot_plugins.txt is provided)

I'm wondering about this because casual users don't know about boot_plugins.txt, the ones that follows @Mello_1993 (A BR PS3 youtuber and a friend of mine) instructions in his video about 3.2.0 that used the boot_plugins.txt complains about webMAN not working even after re-installing it.

So the best solution is the boot_plugins.txt deletion in the first install.
 
@esc0rtd3w How about implementing the PSN protection on HEN (the rco mod by @DeViL303 )? Now it's only available on Nat's CFW

Can i make a PR?

A syscall restoration would be nice too (system_software_update.sprx), i can make a PR too, @nikolaevich23 implemented it)
 
Last edited:
esc0rtd3w said:
I am unfamiliar with that. You can submit a PR if you want and I can test it out.
Click to expand...


Disabling the boot_plugins.txt in the HEN for the installer only and a simple cellFsUnlink("/dev_hdd0/boot_plugins.txt"); should be enough

About the PRs i'll need to check the 3.2.0 source with 4.90 support, you can check the code here ( PS3HEN 3.3.0 · PS3-4K-Pro/HEN@7698e92 (github.com)) it's working good, the syscalls can be restored by entering in System Update options and the PSN protection is working as it should too, but i'm using the old 3.2.0 source with no 4.90 support.

Maybe tonight or tomorrow i'll make the PRs, i'll need to test with the new source.

Credits to nikolaevich23 for the implementation of my requests
 
LuanTeles said:
Disabling the boot_plugins.txt in the HEN for the installer only and a simple cellFsUnlink("/dev_hdd0/boot_plugins.txt"); should be enough

About the PRs i'll need to check the 3.2.0 source with 4.90 support, you can check the code here ( PS3HEN 3.3.0 · PS3-4K-Pro/HEN@7698e92 (github.com)) it's working good, the syscalls can be restored by entering in System Update options and the PSN protection is working as it should too, but i'm using the old 3.2.0 source with no 4.90 support.

Maybe tonight or tomorrow i'll make the PRs, i'll need to test with the new source.

Credits to nikolaevich23 for the implementation of my requests
Click to expand...
We shouldn't need to unlink the boot plugins text. Just the installer ignoring it should be enough. We start creating other problems when we touch the text files or even not load them under certain conditions under normal operation once installed. I still think just making the installer bin not look at them is the best way forward, unless something else is thought of.

Edit: well maybe it would still be a problem. Perhaps removing it would be best, but I can't think of a better option off hand right now. We discussed checking webman and even updating the sprx or installer, but that may bring on more unexpected issues in the future. Idk...its tricky lol

Edit2: Once hen is installed we would still have the same problem if boot plugins exists. The problem with checking for hen installed and skipping boot plugins comes when users try updating or the auto update kicks in. It will then see hen as installed and load text files again. That method seems good for clean installs though.
 
Last edited:
LuanTeles said:
Most of the people including newbies will still get stuck when enabling hen, i really think this time it needs to include a empty boot_plugins.txt in the installation process

Edit: I think the hen installer script must delete the boot_plugin.txt as webMAN MOD installer will not create the boot_plugins.txt if it exists, so it will not enable after installed. (if a empty boot_plugins.txt is provided)

I'm wondering about this because casual users don't know about boot_plugins.txt, the ones that follows @Mello_1993 (A BR PS3 youtuber and a friend of mine) instructions in his video about 3.2.0 that used the boot_plugins.txt complains about webMAN not working even after re-installing it.

So the best solution is the boot_plugins.txt deletion in the first install.
Click to expand...
I already instructed the most laymen to take a picture of the wall and rename the picture to boot_plugins.txt

It's complicated for people not to know how to create a text document.

I think it's a good idea for the HEN installer to create an empty boot_plugins.txt file, just like @LuanTeles said, this way it will force people to update the webman mod to the latest version.
 
esc0rtd3w said:
We shouldn't need to unlink the boot plugins text. Just the installer ignoring it should be enough. We start creating other problems when we touch the text files or even not load them under certain conditions under normal operation once installed. I still think just making the installer bin not look at them is the best way forward, unless something else is thought of.

Edit: well maybe it would still be a problem. Perhaps removing it would be best, but I can't think of a better option off hand right now. We discussed checking webman and even updating the sprx or installer, but that may bring on more unexpected issues in the future. Idk...its tricky lol

Edit2: Once hen is installed we would still have the same problem if boot plugins exists. The problem with checking for hen installed and skipping boot plugins comes when users try updating or the auto update kicks in. It will then see hen as installed and load text files again. That method seems good for clean installs though.
Click to expand...


Yeap , that's why i thought of deleting the txt in the hen install, i can't find a best solution than that. I also thought about including an updated webMAN in the installer but it will roll back version if installed in the future as webMAN mod is always getting updates and the user will need to update it anyway, so deleting the txt and the user having to install the latest update is always the best option IMO.
 
Mello_1993 said:
I already instructed the most laymen to take a picture of the wall and rename the picture to boot_plugins.txt

It's complicated for people not to know how to create a text document.

I think it's a good idea for the HEN installer to create an empty boot_plugins.txt file, just like @LuanTeles said, this way it will force people to update the webman mod to the latest version.
Click to expand...
I agree with the idea of maybe having to force a wmm update, but creating the blank file seems like not the best way to do that. But maybe it is lol. Joonie and I were going back and forth about that last night. What's the best way? To force users to update webman manually or provide a way to reinstall it and update it for them, if hen detects that it exists. But then we only need that for the installation and when hen is installed, it will have to ignore that. Its kind of a catch 22 in a way.
 
esc0rtd3w said:
So they will know what is enabled? Hen? Isn't that what hiding the enable egg icon basically does as a visual?
Click to expand...

I just see a video of a guy explaining the new 3.2.0 and he is messing with the toggles of the webbrowser (cookie, history and ect), so i thought how the user will know if the feauture are enabled or not? So the icon swap can be used for tht.

The implementation is different of what we use in HEN egg logo, in this case i use and on/off.png a placeholder for the current icon and the commands to copy the on or off.png to the placeholder icon and

close_list;close_list;close_list;open_list explorer commands (it will need to be add to xai)

I implemented it using webMAN MOD

eg:

/copy.ps3/dev_hdd0/game/PS34KPROX/USRDIR/toolbox/icons/on.png&to=/dev_hdd0/game/PS34KPROX/USRDIR/toolbox/icons/plugins_icons/plugin_0.png;/xmb.ps3$close_list;/xmb.ps3$close_list;/xmb.ps3$close_list;/xmb.ps3$open_list


it will roll back the XMB levels and opens it again so the icon gets refreshed and returns to the same position without the user notice
 
Last edited:
Mello_1993 said:
I already instructed the most laymen to take a picture of the wall and rename the picture to boot_plugins.txt

It's complicated for people not to know how to create a text document.

I think it's a good idea for the HEN installer to create an empty boot_plugins.txt file, just like @LuanTeles said, this way it will force people to update the webman mod to the latest version.
Click to expand...

Nah the empty boot_plugins.txt in the installer will avoid webMAN to get installed, webMAN MOD AFAIK only creates the .txt if it is not found, it doesn't include the path to the file. So you'll have a lot of people " i installed hen, just fine but now i can't install webMAN"

Deleting the boot_plugins.txt in the first install IMO is the best solution.
 
LuanTeles said:
I just see a video of a guy explaining the new 3.2.0 and he is messing with the toggles of the webbrowser (cookie, history and ect), so i thought how the user will know if the feauture are enabled or not? So the icon swap can be used for tht.

The implementation is different of what we use in HEN egg logo, in this case i use and on/off.png a placeholder for the current icon and the commands to copy the on or off.png to the placeholder icon and

close_list;close_list;close_list;open_list explorer commands

it will roll back the XMB levels and opens it again so the icon gets refreshed and returns to the same position.
Click to expand...
OK. I see what you mean. That's not a bad idea. It does show on hen enable if you selected those clear cache options, in its own popup message, but changing the icon is also a good visual. We need new icons for some of the stuff still anyways @xp3riments :)
 
esc0rtd3w said:
OK. I see what you mean. That's not a bad idea. It does show on hen enable if you selected those clear cache options, in its own popup message, but changing the icon is also a good visual. We need new icons for some of the stuff still anyways @xp3riments :)
Click to expand...

Yeap, if the commads are executed quickly as webMAN does, it seems that the icon is just refreshed.

The popup is good, but visually is better.
 
Louay said:
why 4.88 P3T file is 21mb and 4.87 is 19mb while pkg is 11/12mb ?
Click to expand...
the pkg is to install it. the P3T holds most of the jailbreak. the pkg installs both P3T and the pkg. all combind creates a full jailbroken ver. if it was all in the same one the install will fail. also the P3T also helps keep the ps3 hen to boot and the ps3 to boot
 
You must log in or register to reply here.

Similar threads

Back
Top