82w ago - Following up on their
initial release and
IrisManager application, this weekend Spanish PlayStation 3 developer
DemonHades has made available a JFW DH 3.56 MA PS3 Custom Firmware (CFW) Installation Tutorial.
To quote, roughly translated:
Installation Tutorial for JFW DH 3.56 MA
This tutorial is designed so that the user makes a comfortable and easy installation "DH JFW 3.56 MA" without risk of incorrect installation either. Before starting the installation we will clear some things:
What is the DH JFW 356 MA?
It is the first CFW 3.56 for the system, thanks to DH 356 JFW MA, locked in 3.56 users who are unable to downgrade have a chance to scene, so if you'll need a flasher. For users who are at 3.55 or 3.41 will not need the flasher for installation.
How is unlike the rest of the current CFW?
3.56 The DH JFW is made by sceners MA Spanish and we thought both users who are locked up like that scene today have at 3.41/3.55.
The DH JFW 3.56 MA has features that no other CFW has, such as preloader, Thegra, etc...
It also has a number of tools and addons that are still developing, these are:
- JMAB (XMB design and organization of the new categories JFW)
- IrisMAnager356
- OpenPStore
- UsaveME
- MARNE
- EGEA
- MAD
- MABLDTR2
- PS3control
- CallGate
- Thegra
- BOMA
- MALSE_BLUE
- VDFMA
Detailed below and each one is to be used.
If I upgrade to 3.56 MA DH JFW get trapped forever?
No, you can do downgrade / update, thanks to MAD.
What is MAD?
A virtual flasher that does not require welding in 356MA.
What I can run the risk having it installed?
None if you follow exactly the installation.
Will support the DH JFW 3.56 MA?
If both errors and retrofit.
If I find errors in the DH JFW 3.56 MA, whom I must communicate in order to make the correction?
Mainly DemonHades.org must communicate in explaining what happened.
Installation Process JFW 3.56 DH MA
Files needed for this process:
Installation process:
1. Download the JFW 3.56 DH MA.
2. Check with the MD5 Software is correct when published in this tutorial.
3. Watch the PS3 version you have installed the JFW Before Dh 3.56 MA, must have 3.55 or 3.41.
4. Downloaded the update has to go in the following path of pendrive: PS3/UPDATE/PS3UPDAT.PUP
5. Insert the stick into the PS3 XMB I install it from the PUP as if an ordinary question.
6. Once installed restart PS3 and go.
Important notice: The DH JFW 3.56 MA includes live via PKG service mode, you should not use it unless you know the subject and even fewer use the flashing Lv2Diag.self... will have a total brick.
Also if you mistakenly enter service mode, you can go put in the root of the pendrive Lv2Diag.self of 220kb on usb0 to exit the service mode you will find in the thread of DH 3.56 JFW MA.
Tutorial made to DemonHades.org by
DeathHades,
Psjuan and
DemonHades.
im new to this site iv just started to look into doing a jailbreak on my ps3 so if any one can piont me in the rite direction
it would be very helpfu...
Thats what it installed as for me.
Download: http://mods.elotrolado.net/~hermes/ps3/irismanager-4-x-irismanager-4-x.rar / http://www.mediafire.com/?m3r96w4302e3k68 by faxtron / http://rapidshare.com/files/2072545998/language.ini by LoboGuara
To quote, roughly translated: Well, then here goes: I have included notes (many) so you have any idea what I've played and that: basically control power off by temperature (90 seconds above 79 degrees) and idle time (60 minutes without touching the pad and provided they are not doing file transfers that we can touch morality) is in routine pad.c reading pad
I think it basically means operation: for not being overloaded reading, I do that every 16 tics read the timer and temperature using syscall, do the necessary checks and if the old timer is not zero and go overtime, catapum Chimpun ( without a word))
I've grouped all that well is not lost [+ laughs]. And now the explanation for users:
• Now to have an hour of downtime in Iris console off
• As I said, in Iris temperature alarm: 90 seconds without the temperature drops below 80 � C in either CPU or RSX and the console is turned off.
• The addition of the callback Disc allows're not constantly checking whether there is a disc in and it allows the reader to rest.
• Added support for redirection libfs.sprx: copy by ftp or via usb (usb :/ gets into iris) libfs_patched.sprx, which is generated by patch_libfs.bat (do not forget to put keys in the data folder!) And games like COD4: MW to operate from internal BD-Emu mount
• In Tools (press START) the "Copy from / dev_usb / Iris to Iris folder" will make life easier to move things to the installation directory of Iris Manager. For example, if you put "covers" of Multiman within the USB folder, you copy your own content or libfs_parched.sprx we talked about. The option uses asynchronous copying to gain speed.
IMPORTANT: This new option may damage the Iris Manager installation if not used with head, for logical reasons.
NOTE: Obviously, there is no option to delete anything that is copied, except by FTP or pulling or uninstalling other programs (which will render the games settings, etc.) Enjoy it!
v1.49.1 Changelog (translation by aldostools):
• After one hour of inactivity in Iris the console is turned off
• Temperature alarm in Iris: if temperature remains above 80 � C for 90 seconds in either CPU or RSX, the console is turned off.
• Added support for redirection of libfs.sprx: copy by ftp or via usb (to usb:/iris) the libfs_patched.sprx generated using patch_libfs.bat (don't forget to put the keys file in the data folder!) and games like COD4: MW will play from internal HDD with the BD-Emu mounted.
• Added a callback for Disc check, that prevents constant polling if the disc is inserted or not, giving a rest to the BR drive reader.
• In Tools (press START) the option "Copy from / dev_usb / Iris to Iris folder" will make life easier letting to move things to the installation directory of Iris Manager. For example, if you put "covers" of multiMAN or the libfs_parched.sprx we talked about within the USB folder, Iris will copy the content its folder. The option uses asynchronous copying to gain speed.
IMPORTANT: This new option may damage the Iris Manager installation if not used with head, for logical reasons.
v1.49.2 Chagelog (translation by aldostools):
• Fixed a bug mounting the BD-Emu when certain disk changes occur (for example, inserting certain PSX games, eject then put a BR disc).
• Removed patched libfs load when BD-Emu is used from external disc (COD black screen 4: MW similar to that which occurred from internal)
• Added warning messages in shutdown functions (in one case can be cancelled, in the other is non-cancelable for obvious reasons: if there is overheating, we must be forced to turn off the PS3)
v1.49.3 Changelog (via elotrolado.net/hilo_3-55-4-30-iris-manager-v1-38_1842936_s340#p1731400119):
• If you load a game for PS3 (not PSN, a disc game), some data are stored in a file (lastgame). Holding down L1 on startup, when Iris Manager is loading again, it will load automatically the last game, unless their presence is not detected or error.
• If in the root directory of the game (where usually the PS3_DISC_SFB is found), you put a file name containing ps2disc.txt with the destination path (eg. /dev_usb000/dataps2 or /dev_hdd/GAME/dataps2), that folder is mounted as /dev_ps2disc.
This feature can be useful for games like Sing Star, that can read tracks from PS2 discs.
More PlayStation 3 News...
Been using Game Backup System to backup my games, proven to be quite a killer combination with Iris Manager