PS4 News on Facebook! PS4 News on Twitter! PS4 News on YouTube! PS4 News RSS Feed!

Home PS4 News - Latest PlayStation 4 and PS3 News

January 16, 2013 // 1:58 pm - Following up on the previous updates, today Spanish PlayStation 3 developer Estwald has updated the Iris Manager PS3 game backup manager to version 1.49.1 followed by 1.49.2 and v1.49.3 with the changes detailed below.

Download: Iris Manager v1.49.1 / v1.49.2 / v1.49.3 for v4.XX PS3 CFW / Iris Manager 1.49.1 PKG (Animated Icon) by faxtron / Portuguese (BR) Language.ini Translation 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.


Iris Manager v1.49.1 PS3 Backup Game Manager Update is Released

Follow us on Twitter, Facebook and drop by the PS3 Hacks and PS3 CFW forums for the latest PlayStation 3 scene and PS4 Hacks & JailBreak updates with PlayStation 4 homebrew PS4 Downloads.



#875 - technodon - June 9, 2012 // 10:25 am
technodon's Avatar
could someone explain in english how to run the plugin that dumps 256MB of ram on DemonHades 3.56 to USB please. been trying to get this to work all day! lol.

#874 - Adriansfc92 - June 8, 2012 // 8:17 am
Adriansfc92's Avatar
Following up on their previous updates, today the Spanish PlayStation 3 developers at DemonHades have made available the first plugins for TheGrid dubbed Dumper RAM and NoBD for PS3 JFW DH 3.56 MA Custom Firmware.

To quote, roughly translated:

First TheGrid plugins - Dumper RAM and NoBD

Hello again demons, as we all know when it was announced the JFW one of the first features was the ability to run plugins in the background, options such as having music while playing games, ftp in the background, and so endless possibilities in which only limits us one thing, the imagination of the devs to create plugins...

I come today to present the first 2 plugins for our revered JFW3.56MA functional, we begin with the dumper.ram
a plugin ideal for researchers and curious, originally created by JaiCraB for JFW 3.41 and worn by our great friend blackdeath for JFW3.56 MA.

Dumper.RAM

This is a plugin that allows us to dump the 256MB of ram at any time, the instructions are simple prior to everything, the first is to install 2.0.

The plugin support makes use of the following: When starting the look the boot.cfg in / dev_flash / TheGrid or / dev_usb000 (Bone in the root of the usb port closest to the reader) this boot.cfg consists of the following a simple text file that tell the path to the plugin to load.

[Register or Login to view code]

As you see first is the 1 that could also be a zero (1 - active | 0 - off) always go after the separator, a semicolon to go to the route after the plugin to load and then close the line with a point semicolon, then the line is successfully completed the plugin. Always be called boot.cfg will be recognized this is how ...

I give you an example as shown in the top line of boot.cfg, active with 1 plugin and take the root of the usb as a route to connect the pen to read the USB00 (if on the right) and turn on my PS3, well when we are in the JMB / XMB TheGrid is ready for the implementation of dumper.self (our plugin) plugin that is activated by a flag in this case his name is activated dumper.ram putting the pen in the flag dumper USB00.ram at the root, when you connect the led on our PS3 started blinking green when finished dump that we realize when we see that our PS3 hdd stops read / write so intensely open a filemanager or FTP and we will have our dumpeo in dev_hdd00 ready for review.

The most important of all, no matter when we activate the plugin, you can be in full play in full BD movie using the browser etc etc ... as I said before, great to learn more about assemblies such minis games, ps2, psx ... plugin download link boot.cfg dumper.ram + activation + flag http://www.multiupload.nl/JT4YIW7GQ2

NOTE: boot.cfg open with notepad for configuration
NOTE-2: If we leave the dev_flash boot.cfg create the folder on the pendrive GRID_UPDATER we put in and start the ps3 (USB00)
NOTE-3: Remember to activate the ninth TheGrid.cfg patch is to enable the use plugins

Plugin NoBD

Plugin NoBD, another plugin created by JaiCraB, and carried by blackdeath, in NoBD we can set aside for loading backups managers in our PS3, currently only able to launch games on the PS3 JFW3.56MA, but could launch PSX games movies BD, and PS2 games (retro consoles) for retro would not find a way the game PS2 PS3 detected as when we are in service mode... instructions: start the PS3 with the pen drive plugged into the USB00, and at the root we have the following ..

[Register or Login to view code]

Turn on the PS3 with everything prepared and inserted an original game PS3, go to XMB and see that the title of the game is not the original if not the backup, we launched and we will give an error, this error is due to refresh BD ignore it, take us back to jmb / xmb and launch the game again, now you can play it 100% without the use of any manager... plugin download link boot.cfg NoBD + activation + flag http://www.multiupload.nl/AG9JNWIJ2A

NOTE: currently only have 1 backup can be mounted but we could have till about 16 in future revisions
NOTE-2: If we leave the dev_flash boot.cfg create the folder on the pendrive GRID_UPDATER we put in and start the PS3 (USB00)
NOTE-3: Remember to activate the ninth TheGrid.cfg patch is to enable the use plugins

Acknowledgments:

  • MA Rokiski to create and enable TheGrid is compatible with
  • JaiCraB by TheGrid for plugins, and all their hard work
  • Blackdeath to make bigger every day this cfw
  • DemonHades of testings at night till the thousand...
  • And even server, I hope you enjoy greetings...

TheGrid Update 2.0, Plugins activation and other improvements (via demonhades.org/foro/viewtopic.php?t=6639&f=297#p50112)

Good hello, here we bring you another update from TheGrid, this time you have already activated the plugin system in the background, ready for the shift that they said it was not possible to have multitasking PPU "This is going to turn mathieuth the learned "

Among the supported plugins you have for the time and Full NOdisk DUMPER RAM. These plugins are loaded in the background and are activated only by setting the activation flag in correct path (root usb).

ExterMAl dev_flash

Also you have flags as ExterMAl dev_flash, where you only have to remove a pup of the FW that you please lower or similar to 356 (do not care debug or retail) and place the 7 folders dev_flash forming at the root of the pendrive

  • VSH
  • SYS
  • bdplayer
  • ps1emu
  • ps2emu
  • pspemu
  • data

And flash.external flag (if this flag is to start the console with the PEN, I always start the external dev_flash) The rest of the boot flags are:

  • factory.mode: Lets put the console in service mode without a dongle just to insert a usb with that flag.
  • hv.debug: Enables debugging of all services of the HV, with a ram dump you can see all debug messages.

TheGrid details:

  • Improved dynamic patching (Fully functional).
  • On the plugin support (Multitasking) in the background.
  • Various optimizations.


  • First patch (first number in the 64): this corresponds to MatherOS Patch to disable or enable the use of Linux on the console.
  • Second patch (second number in the 64): Corresponds to load the syscall PL3 Payload 35 in the console.
  • Third patch (third number in the 64): Corresponds to load Payload Supports sc MAS 36 and 8 on the console.
  • Fourth patch (fourth number in the 64): Corresponds to load BD region Free bone patch overrides the restriction on the region bds ignoring methods such as changing the console region (Annoyed if you have to do all the time) .
  • Fifth patch (fifth in number 64): Corresponds to the patch that disables the PS1 disk check on the console.
  • Sixth patch (sixth in number 64): Enables or disables dynamic patch the FW by loading a patch that makes bone PatchUser.bin the same user or future updates that we will be taking to thegrid will come in the form of a file "PatchUser.bin" that will contain the updates.
  • Seventh patch (Seventh in the number 64): Enables or disables support for LV2 Dynarec in order to use dynamic recompilation of the emulators and performance improvements in them (For use with emulators suits the users and devs who want the best performance).
  • Eighth patch (eighth number in the 64): Enables or disables the SET FAN 100% to revolutionize cooler fan speed to the limit.
  • Ninth patch (Nine in number 64): Enables or disables support plugins (*) ...

Confeditor prepared for this version with the changes in TheGrid: http://www.mediafire.com/?x8qiy4x1y1e9l6w

If you have questions visit the wikiMA: jfwdh356ma.wikispaces.com/TheGrid%2CPlugins+y+Parches+Dinamicos

The plugin support makes use of the following: When starting the look the boot.cfg in / dev_flash / TheGrid or / dev_usb000 (Bone in the root of the usb port closest to the reader) this boot.cfg consists of the following a simple text file that tell the path to the plugin to load.

[Register or Login to view code]

As you see first is the 1 that could also be a zero (1 - active | 0 - off) always go after the separator, a semicolon to go to the route after the plugin to load and then close the line with a point semicolon, then the line is successfully completed the plugin. Always be called boot.cfg will be recognized this is how ...

Here you can download TheGrid (http://www.mediafire.com/?ca5pp6qgjccob8n) 2.0 update, remember that this is not the SP1.4 and the plugins will be published in the next few days

TUTORIAL PATCHUSER.BIN by blackdeath (via demonhades.org/foro/viewtopic.php?t=6639&f=297#p50125):

With this new version of TheGrid you can avail of dynamic patching capacity at its maximum splendor, as you do this is more dedicated to developers who want to learn new things and new ways of working that is why I teach that is the dynamic patch for user.

The dynamic patching is patching or modification of any file of fw (modules selves - sprx) in memory is something that is dynamic in the time it is loaded will be patched is a new way to modify the firmware without having to touch the dev_flash modules and obtaining the best results since being tested is no longer needed for any damage fw test.

To enable you ought to select the config "PatchUser.bin Support (User Patches)" on TheGrid.cfg.

The PatchUser.bin (You must write so as I write!) Should be placed in "/ dev_usb000/GRID_UPDATER/PatchUser.bin" (This is not to count him to keep the dev_flash and so will not need to change your patch provided automatically by if you play a bad thing not to be always starting tengais wrong) you can clear this also put in "/ dev_flash / TheGrid / PatchUser.bin" but I recommend that you leave this path when coding sure your patch is safe and you are aware of wanting to load times.

See it like this:

  • Dev_flash (East end where to stay and work completed and improved)
  • Dev_usb (test medium only load it when you find the USB so if you have not placed the usb (usb000) not obviously you will carry
  • Your patches since they are in the usb is why I see it more secure when we have something we test and end and that failure is not
  • Simply insert the USB or simply delete or correct PatchUser.bin usb in pc).

[Register or Login to view code]

As you can see is the same as I explained in the structure... Well I hope that many developers and interested in learning can prove it ...

Regards

Thanks to Rokiski, JaiCraB, blackdeath, Cheko Vakaloka and all that happened , and we recommend that all users install the MA to provide support to everything that is posted

Update: From haxxxen: Appldr research: unsigned apps patch (based on JFW DH 3.56)

Finally i have found a remedy for this (stupid) vsh.self unsigned app patch (pl3 based on kakaroto) for cex cfw/target.

due to disadvantages to this pl3 patch on dex i had removed it long time ago now, but never realized that there is a reason why this patch was there and found. @Joonie now has told me the problems that occur if you remove this patch, or you don't apply it. the symptoms are shutdowns on almost all apps when exiting or blackscreens.

well, even cobra does not work without this patch and will softbrick your ps3 on cex cfw (which was btw never mentioned by its cobra developer in readme)

now that i am a dex user, i have found this patch making problems with dex cfws, which is a nogo to me. it will break npdrm_fself signed apps and you cannot run them.

i then tried porting those appldr patches made by demonhades and guess what, the result is that i can run apps on cex again without any shutdowns or blackscreen. so this will make that vsh.self patch finally obsolete, at least to me and i am very happy

these are the patches i have found, but i need a helping hand there to determine which are needed and which not. fyi habib and Joonie, 4.21 appldr unsigned apps patches:

[Register or Login to view code]

Finally, from Joonie: this is off topic but I just wanted to let you know.

I found the working pattern that can be hard-coded in to lv1.elf for lv2 memory protection patch though not really needed on these days but wanted to let you know this patch worked on 4.46 and 4.75 at least.

I've been testing lv1 patches all day long and noticed the difference between 3.55, 4.21 , 4.30+ from cyber's toolbox.

for 4.21 he used:

[Register or Login to view code]

this pattern, and I was able to confirm this patch did work with prx loader 1.04, [without this, prx loader shutsdown]
however, I didn't test if this could be hard-coded since you said you had a brick before.

and for 4.30, 4.41, 4.46 cyber started using this pattern

[Register or Login to view code]

I also tested this patch with prxloader 1.03 [the one without lv2 mem protection patch, user included the patch since 1.04 for 4.46]

and I tried this patch hard-coded with lv1.self from 4,46 and 4.75, and it turned out worked without any problem.

Maybe you could try this one with your 4.21 and it could be good to add one of your tcl task collections.

I'll try to work on that appldr patch as soon as I'm done with my own stuff.. keep up with your good work.

ah also another thing, currently there isn't any working toggle recovery tool for NAND ps3s. [Condor updater 3.xx , REBUG TOOLBOX, vshmenu, glevend's recovery toggle, and yours]

I think that the offset of "FF" flag to enable recovery mode on eeprom doesn't seem to do anything on NAND PS3.

[Register or Login to view code]


I was able to get eeprom dump from ps3 dev wiki, the ones dumped by HW method, but I don't seem to find any clue about how to enable Recovery mode on NAND ps3s.

the original source code is available via zecoxao 's github.

More PlayStation 3 News...

#873 - HeyManHRU - May 16, 2012 // 4:18 pm
HeyManHRU's Avatar
Thanks for the posts Adriansfc92.

#872 - NTA - May 16, 2012 // 1:44 pm
NTA's Avatar
Oh I see. That's a bit unfortunate lol.

#871 - Adriansfc92 - May 16, 2012 // 1:32 pm
Adriansfc92's Avatar
Because in 3.55 no haven't dynarec and our team is focused on only JFW 3.56.

#870 - NTA - May 16, 2012 // 1:24 pm
NTA's Avatar
Why only support for 3.56? The other firmwares might feel a bit lonely without a decent psx emulator

#869 - Adriansfc92 - May 16, 2012 // 1:15 pm
Adriansfc92's Avatar
This only work in JFW 3.56.

#868 - NTA - May 16, 2012 // 12:44 pm
NTA's Avatar
What firmwares are supported by this PSX emulator? Only 3.56? What about 3.41/3.55?

#867 - Adriansfc92 - May 16, 2012 // 11:31 am
Adriansfc92's Avatar
The compatibility is not very high keep in mind this is a beta will be improved.

Try games and comment thanks!

Sorry for my bad english

#866 - NTA - May 16, 2012 // 11:18 am
NTA's Avatar
Seems legit. How's the compatibility?