50w ago - 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.
1 ;/ dev_usb000/dumper.self;
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 ..
* / / Content plugin NoBD to launch backups from the external hd without having to managers
USB00:
boot.cfg (we can also have it in flash)
NoBD.self
GAME_USB (the flag of activation)
PS3_GAME (is the backup folder you want to launch, we have to do is grab our PS3_GAME backup folder and put it in the root of our pen / external HDD)
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.
1 ;/ dev_usb000/plugin.self;
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).
PatchUser.bin Structure (By JaiCraB Originally in JFW 3.41)
/ / -------------------------------------
/ / FILE STRUCTURE PATCHUSER.BIN
/ / -------------------------------------
/ / 1. - 8 Bytes = Hash Module
/ / 2. - Each 8 bytes = PATCH (4byte Offset. ELF (Obviously you will have to locate it before in the pc), 4byte Opcode (This is the patch itself, which you have patched the fw (Payloads, etc.) before you shall know which is an opcode)
/ / 3. - End of block when you find the information 8 bytes 0x5448454752494421 (MagicEnd) (in ASCII says, "THEGRID!") And signifies the end of the block patch
/ / 4. - Next Module and so on ...
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
Doesn't sounds like the sort of game I would find fun. Who wants to clean piss for a game? People don't want to do it for a job so why would a game of...
Download: http://mods.elotrolado.net/~hermes/ps3/irismanager-4-x.rar / http://www.sendspace.com/file/ip7vyn (Mirror) / http://www.putlocker.com/file/5E261DC08AF5A48D (Password: IRIS) / http://www.mediafire.com/?gqxu5xbiic7aw51 by pinoytechno
To quote, roughly translated: Well, given that D_Skywalk is "low" paternity and asked me to open a new thread, to update it, that I do, taking advantage we have new version
1) I do not carry version control, because in github I canceled, I have no desire to go back to those bastards and git all problems are often under Windows, as not handle http addresses. So I'll post a RAR and point and if someone wants to take control of versions, back on, but for now, I'm not.
2) The official version is that we D_Skywalk and me. Your contributions are welcome, within a limit, it has been said that the GUI should be the same, basically, and not be breaking the application schema. That does not mean that you may not go it alone and break it in your own way, you will have to call but then otherwise your application, by request of D_Skywalk. Obviously, if the changes are minor, no need to change the application name, but it is not in competition, if not collaboration. If that is respected, I have no objection to lend you aid, etc.
3) The third condition is rather a request that anyone who drives the Wiki, should be an entry "Iris Manager" to link it in this post and facilitaros the task if you or any morning for example, I abandoned the project.
What's new:
Changelog 1.55
• Support CFW 4.31 from Miralastijeras (Thanks to the author for help to make the port easier)
• New Homelaunc1 for CFW 4.31
• NEW PATCH FOR PS1 EMULATOR: it fixes the issues when some games were calling the ps1_netemu. The fix is done faking the disc ID in the sector 16. That was the reason of the black screen of games like Chrono Cross, but inserting another PSX disc THAT game worked.
• New patch to simulate the extended info for the TOC, in case it is needed.
• IMPORTANT: the ps1_emu from 4.31 can be used. Please, use one from 4.30 or previous. Estwald has to check if it is feasible the emulation via syscall. The big issue is to find where to store the code, that is large to support all versions.
• Fixed some minor bugs from the previous version.
Regards
More PlayStation 3 News...
add a filemanager..
add the ability to create xmb mount files for each game..(like load last game from mm)
and add dev_blind access...
btw: do anybody know how to edit app home from the newest rogero... the standard app is the pkg installer displayed ass toolbox... is there a way to change the apps??? i want to delete pkg installer.... i want to replace it with irismanager if the upper functions are added...so at the moment im still using both... pls give me a reason to delete mm for ever.... nothing against dean but i just like it simple... 220 mb space for a loader is too much...
Download: http://mods.elotrolado.net/~hermes/ps3/irismanager-4-x.rar / http://www.mediafire.com/?6d1wls6zc6tjf1k / http://www.mediafire.com/?xi80w7427gc5wt8 / http://www.mediafire.com/?39kn2jcwk7m6957 / http://www.mediafire.com/?aofz3efu5m83gv6 / http://www.mediafire.com/?ssxu9mkz9g4zzc9 / http://www.mediafire.com/?zo4ndtzt94gl8ea (based on this PT-PT) / http://www.mediafire.com/?89r14pkoyawmak8 / http://www.mediafire.com/?e8l4mb0ekb2icss by brunolee / http://www.mediafire.com/?oaz1df5bk3cxvcu / http://www.mediafire.com/?c7osjfayi2s4khw by Markus95 / http://www.mediafire.com/?9ylhnpp2z8k2v88 (http://www.mediafire.com/?7av637v4zhx2ika) / http://www.mediafire.com/?zrmwocq7i1jk7qd / http://www.mediafire.com/?kb28cf1jbva8gc1 / http://www.mediafire.com/?7g5zwmzfii5ld1o / http://www.mediafire.com/?lp7ckkveawy3map / http://www.mediafire.com/?ost6cw7bcwiku78 / http://www.mediafire.com/?u2llka4lplai6ww / http://www.mediafire.com/?ef7cdlt3l007grc / http://www.mediafire.com/?62bhqts272pydgt / http://www.mediafire.com/?h1m0aaih2xk511p / http://www.mediafire.com/?3xdw67cau4qqj74 / http://www.mediafire.com/?epd2yj5pnibdne7 / http://www.mediafire.com/?fg9am4t86unf9f9 / http://www.mediafire.com/?fi3oj4jorgk16e8 by brunolee / https://docs.google.com/spreadsheet/ccc?key=0As9ZdsrJoSp1dFpiRG1lZDV5d1RUamxBOHhFT1EtNFE#gid=0
To quote, roughly translated: What's new:
• Added possibility to extract ISO PSX (Game Copy option, press Select on PSX disc) from multiple disks.
• Added possibility to use tricks disk: ISO hits the / PSXGAMES / CHEATS. The iso should be 2352 bytes per sector that can then be used to adapt to other sizes, creating replicas. For example, the Xploder 4 is not even 10 MB, so it's no big deal to have multiple versions. When asked if you want to start using it and mount it as a first album. See notes for details (the name is the same, I just need an extension and a sector size correct, internally, is list what is in that directory looking for a valid ISO)
• Changed BD Emu options: there are now separate options for internal or external disk: In internal: libfs always takes patched, can not mount or play as hard. In external: if you mount the disk, not taken libfs patched and is the recommended option. With libfs only recommend it for games that have cached data in the internal HDD.
• Enabled L2 to show games. At first, the first option to show only R2 PS3 games, while if you press L2 would PSX
And now about other things:
• I see that you are using my Deank ps1_emu patches. That's no problem, since precisely, if I do things is public for anyone to be able to use, obviously. The problem is that it does not usually release the source code in compliance with applicable licenses and thereby not allowing others we can benefit from their contributions as he takes advantage of ours.
• BD-Emu Theme internally mounted: roll both not flushed the Grid and it works perfectly [+ laughs]. How not work was if you used the game on installing external internal data (a waste, since most of the game is in that file).
• PS2-PSP Topic: I'm not going to put up with it.
• Theme D_Skywalk: I know nothing of the boy and has me worried. Other than that, with the whole thing, I'm getting a lot of changes in the sources and I hope there is no problem then ...
• Move Topic: besides I have not Move, I can not use v2 PSL1GHT even compile, among other things, because compilers do not support my IF Mode Pointer and is already a pain without having to play more, and to have to settle a new library on the old woman ends up not being consistent. Perhaps we should look at that bear Iris V2, but first would have to have compilers and toolchain oopo as we know it (you throw two hours compiling something to the end, leave a mistake that you do not know where it comes. That at least since Windows [+ laughs])
• Thread Dump PSX disc: in psx.c is a very nice routine called read_raw_sector () to read entire sectors. Maybe someone interested as used
Regards
Iris Manager Tutorial by LoboGuara
Things you need:
• The latest Iris Manager release (Actually, 1.54): http://mods.elotrolado.net/~hermes/ps3/irismanager-4-x.rar
• TrueAncestor SELF resigner (only for the required files): http://www.mediafire.com/?4ojs79teb4486x4
• A file manager (i.e. multiMAN , Comgenie Awesome FileManager) OR a working PC-PS3 ftp connection
Install the Iris PKG on your PS3 (The pkg is inside the rar file: irismanager-4-x.pkg)
1. Extract the Iris Manager rar file on your PC
2. Inside the Iris uncompressed folder, you will see a file named patch_ps1emu.rar. Extract this file
3. Extract TrueAncestor SELF resigner and copy the contents of the DATA folder (ldr_curves, vsh_curves, keys) to the patch_ps1emu DATA folder.
4. Copy the file /dev_flash/ps1emu/ps1_emu.self (using FTP or a file Manager) and put this file into the patch_ps1emu extracted folder
5. Run patch_ps1emu.bat with Administrator privileges
6. Copy the generated ps1_emu_patched2.self to the IRIS MANAGER folder on PS3 (usually /dev_hdd0/game/IMANAGER4)
Example: /dev_hdd0/game/IMANAGER4/ ps1_emu_patched2.self
Preparing your PSX ISOS:
On your EXTERNAL USB device, create a folder called “PSXISOS”
/dev_usb000/PSXGAMES/
Inside the PSXGAMES folder, create a foder with the game name
Example: /dev_usb000/PSXGAMES/CrashBandicoot/
Inside the game folder, put your ISO/BIN/IMG and Optionally, a JPG image named “Cover.jpg” (to get the cover showing on Iris Manager game list),
The Directory structure should be like this: /dev_usb000/PSXGAMES/CrashBandicoot/CrashBandicoot.iso
If the game has multiple disks, put the other disk images in the same folder respecting the filename of the first disc. Example
/dev_usb000/PSXGAMES/FinalFantasy9/ FF9_disc1.ISO
/dev_usb000/PSXGAMES/FinalFantasy9/ FF9_disc2.ISO
/dev_usb000/PSXGAMES/FinalFantasy9/ FF9_disc3.ISO
/dev_usb000/PSXGAMES/FinalFantasy9/ FF9_disc4.ISO
The Cover image must not exceed 1024×1024 in size. Done. Your PSX games will now apperar on Iris Game list
Note: there is a pkg containing the patched ps1_emu_patched2.self , you can download it HERE if you are having problems patching your own file. Im not recommending using it, since i have not tested this pkg myself.
Example of the correct folder structure using Iris Manager:
PS3 GAMES:
Iris Manager will search for your PS3 games on /dev_usb000/GAMEZ instead of GAMES. If you are a multiMAN user, you can just rename your GAMES folder to GAMEZ. Since multiMAN search for games in both GAMES and GAMEZ folder, you will have no problems.
GAME COVERS:
You can use the same multiMAN “covers” on Iris Manager! Just copy the “covers” folder into the Iris Manager directory
Ex: /dev_hdd0/game/IMANAGER4/covers
Tips: To load the last played game: Hold L1 at Iris Manager startup. Sorting the games by system: Press L2 (PSX) or R2 (PS3). Game config: Select your PSX/PS3 game and press SELECT. General config: Press START
Iris Manager Translations: brunolee provide a nice language pkgs, you can get these translations linked above. Just install the respective .pkg and you are done! Have fun! If you have any doubts/questions, dont hesitate to ask!
More PlayStation 3 News...