IRISMAN

PS3 IRISMAN {information] - A manager for CFW enabled PS3's (developed by Aldostools) 4.91.2

@aldostools
too bad, no pm...:(

do you mind if I would release a modified version of IRISMAN? not much of changings, but with big and useful impact, especially useful these days :)

No, I don't mind... however as the license says you should include the source code with the changes and use a different name to avoid confusion about which fork is being used.

IMHO It would be more practical if you submit a pull request to the github repository. That way future releases would include your improvements.
 
No, I don't mind... however as the license says you should include the source code with the changes and use a different name to avoid confusion about which fork is being used.

IMHO It would be more practical if you submit a pull request to the github repository. That way future releases would include your improvements.
ok, got it. doing sth like this of course only with src, but well, you will see it is not much of change and probably no demand for this. just want to put this out for some like me

edit
oh, and sorry that I have bothered you about the payloads. I should have checked your source on git before asking questions
 
Last edited:
IRISMAN v4.91.1 is out!

Changelog:
  • Support for CFW/HFW 4.91
  • Includes latest Mamba 8.4 (20230307) with support for 4.91 PEX
  • Updated exFAT Manager 0.10
  • Includes deank's Movian M7 7.0.2
 
@aldostools I may have posted about this before, but I think I found the solution to fix Movian/Showtime exiting to multiMAN/XMB. I decrypted SHOWTIME.SELF using TrueAncestor Self Resigner, and saw 3 cases of BLES80608, one of them in a string pointing to the multiMAN RELOAD.SELF. Should just be a case of replacing those 3 cases with IRISMAN00 the resigning -- that's the part I need help with. When trying to resign with Self Resigner, I get an output file that's 4MB smaller, and when trying to launch it on the PS3, it doesn't work.
 
@aldostools I may have posted about this before, but I think I found the solution to fix Movian/Showtime exiting to multiMAN/XMB. I decrypted SHOWTIME.SELF using TrueAncestor Self Resigner, and saw 3 cases of BLES80608, one of them in a string pointing to the multiMAN RELOAD.SELF. Should just be a case of replacing those 3 cases with IRISMAN00 the resigning -- that's the part I need help with. When trying to resign with Self Resigner, I get an output file that's 4MB smaller, and when trying to launch it on the PS3, it doesn't work.

Try using TrueAncestor SELF Resigner
https://www.psx-place.com/resources/trueancestor-self-resigner-by-jjkkyu.33/

I haven't verified it, but maybe these guides could help you
https://www.psx-place.com/threads/guide-properly-sign-sprx-and-eboot-for-hen.24449/
https://www.psx-place.com/resources/resign-eboot-and-sprx-files.831/
 

Thanks for your reply. I tried True Ancestor self resigner already. I even tried scetool, using the original SHOWTIME.SELF as a template. Can you look into it when/if you get chance, please. I imagine it's quite similar to how you made multiMAN MOD.
 
The easiest way to resign a SELF is using scetool with the option --template <original.self>

It will apply the settings from the original.self to the new self file.
 
The easiest way to resign a SELF is using scetool with the option --template <original.self>

It will apply the settings from the original.self to the new self file.

I appreciate your reply once again. Here's what I tried:

To decrypt the original SHOWTIME.SELF, I used "scetool --decrypt ORIGINAL.SELF SHOWTIME.ELF".

I then used HxD to replace the 3 occurrences of BLES80608 with IRISMAN00.

To generate a new SELF, I used "scetool --template ORIGINAL.SELF --sce-type SELF --compress-data TRUE --encrypt SHOWTIME.ELF SHOWTIME.SELF".

Finally, I replaced the SHOWTIME.SELF in IRISMAN with the one I edited, but unfortunately when using the Showtime option in IRISMAN, it just returns to the XMB without opening Movian.
 
I have used this command:
scetool.exe -v --sce-type=SELF --template="original.SELF" --encrypt "file.ELF" "file.SELF"

The "original.SELF" cannot be an EBOOT.BIN or a npDRM SELF. It must be encrypted as a SELF used in bluray games.

To force the return of SHOWTIME to IRISMAN, I used to remap /dev_hdd0/game/BLES80608 to /dev_hdd0/game/IRISMAN00 instead of replace the game ID in the SELF.
 
I have used this command:
scetool.exe -v --sce-type=SELF --template="original.SELF" --encrypt "file.ELF" "file.SELF"

The "original.SELF" cannot be an EBOOT.BIN or a npDRM SELF. It must be encrypted as a SELF used in bluray games.

To force the return of SHOWTIME to IRISMAN, I used to remap /dev_hdd0/game/BLES80608 to /dev_hdd0/game/IRISMAN00 instead of replace the game ID in the SELF.

Thank you. I guess remapping doesn't work? As Showtime/Movian returns to the XMB most of the time. It will very rarely return to IRISMAN, but it seems random.

EDIT: I now realise that you meant remapping with webMAN. I initially thought it was the method you were currently using in IRISMAN.
 
Last edited:
IRISMAN 4.91.2.

Changelog:
  • Support for CFW/HFW 4.91
  • Includes latest Mamba 8.4 (20230307) with support for 4.91 PEX
  • Updated exFAT Manager 0.12
  • Includes deank's Movian M7 7.0.2
 
@aldostools I just discovered that it's not possible to access NTFS drives through the built-in FTP server. I get error 125, or 150 normally when trying to access it. It's not a problem with the drive, as Movian's server can access it without issue.

I saw in the webMAN changelog "Fixed a regression accessing NTFS through FTP", so perhaps IRISMAN has the same issue.

To clarify, I don't have webMAN MOD installed, so it's not a conflict of having 2 servers running simultaneously.
 
webMAN and IRISMAN are 2 separated projects. Not all the fixes applied to webMAN MOD were applied to IRISMAN.

Also the FTP servers are slightly different too.
 
webMAN and IRISMAN are 2 separated projects. Not all the fixes applied to webMAN MOD were applied to IRISMAN.

Also the FTP servers are slightly different too.

I know they're separate projects. I was just reporting a bug in IRISMAN. But mentioned the similar bug that was in webMAN and has been fixed. I was indirectly saying that if you fixed it in one, it theoretically shouldn't take ages to fix in the other.
 
I know they're separate projects. I was just reporting a bug in IRISMAN. But mentioned the similar bug that was in webMAN and has been fixed. I was indirectly saying that if you fixed it in one, it theoretically shouldn't take ages to fix in the other.

The project is open source so others can take up the challenge when I'm busy...
 
Back
Top