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
Some time ago there was a buzz about unbanning methods, but I didnt care. Now I do, but I have no idea what current situation is and its hard to figur...
Well hell, after the triumphant return of DemonHades (Triumphal say something
If if as you read, the CFW who had to leave for a long time and stubbornness of your dear master demon DH did not go. So without further ado I leave you with the link to download the CFW and its Tolos (Manager, usaveme and others) just say that a certain person once told me that a cfw had to be free, well that's something I do not agree.
But if they wanted their work free jaicrab since all that thought it was demon JFW were wrong and the only themes I jaicrab little more but I think the pup, blipi, the manager, the openpstore mario, is that this is something that would need to see cast long ago that if this was not released at the time were by the manipulations of a certain person.. Links ..
• Usaveme: http://www.putlocker.com/file/B234F8AC37E42573
• Blipi TheGrid Manager: http://www.putlocker.com/file/A8E48E2F05036440
• OpenPStore: http://www.putlocker.com/file/082D657078F7A2DD
• JFW-DH 3.41 V2: http://www.mediafire.com/?j7mude3rd16dtju
• JFW-DH 3.41 V3: http://www.mediafire.com/?7jvvcv6b3tnr9k5
A greeting and farewell dh.org Rest in peace.
PS The v2 is the best work, thanks to jaicrab, blipi, FLIPI. mario, and other people who worked alongside this be for nothing then remained in. CAREFULLY: BOATS AND TEAM I was the most controversial developer in the DH team
To quote, roughly translated: eEID0 Dumper by BlackDeath to JBM 3.55, MA 3.56 and CFW 3.55
Hello friends, after the method of filtration CEX2DEX the team decided to investigate this new field (for some) and not so much for others, that is why we are working to bring you the easiest method to move to Linux without requiring DEX.
Today I present created by the dumper EID0 blackdeath with which we can dump all EID0 or directly CEX first section with only launch a pkg and have connected a USB port on dev_usb000, the instructions are on screen and are easy:
• START: To dump all EID0.
• SQUARE: To dump the first section of EID0 directly (eid0_1st_Section_CEX.bin).
• X (EQUIS): To dump metldr (Encryption) to USB and be prepared to exploit and get the dump of the decrypted metldr in subsequent steps.
If you are in Normal 3.55 cfw release the pkg from video.
BlackDeath says: This latest version now allows you to dump the metldr (encryption) on your console if usais the X button and you will have your ready to dump metldr encryption decryption keys used together with her exploit later.
Tell them to keep working this issue need not linux as the next step is to dump the metldr without having to make so many things in linux but a quick and easy dump.
The eEID0 is necessary for the process dump metldr As you know, and only the first section of eEID0 (That we get directly to this tool) is required for Conversion to a unit DEX / TEST.
No more here I leave the download link, works both on any CFW 3.55 (PEEK | POKE LV2) as in MA:
• http://www.mediafire.com/?eblfgmmwrmjl8sw (Old Version)
• http://www.mediafire.com/?32dca82c31470qa (New Version)
Thanks BlackDeath, Checko, Tito01 and DemonHades
From checko: WIP: A method to dump metldr and eEID root keys without linux, more easy with some little steps .. maybe naehrwert can help you. To quote from his Twitter (via twitter.com/naehrwert/status/226682478373531648 and twitter.com/naehrwert/status/226686257005203456):
Isn't installing linux to get your eid root key a bit of an overkill when you could just use netrpc?!
Or you could compile this pastie.org/4295312, sign it with metldr keys and grab the key/iv from shared LS...
ldr.ld
ENTRY(_start)
SECTIONS
{
. = 0x25800;
.text :
{
*(.text)
}
.data :
{
*(.data)
*(.rodata)
}
.bss :
{
bss = .;
*(.bss)
}
}
#ifndef _TYPES_H_
#define _TYPES_H_
typedef char s8;
typedef unsigned char u8;
typedef short s16;
typedef unsigned short u16;
typedef int s32;
typedef unsigned int u32;
typedef long long int s64;
typedef unsigned long long int u64;
#endif
.text
/* Loader entry. */
.global _start
_start:
/* Setup stack pointer. */
ila sp, 0x3DFA0
/* Well... */
brsl lr, main
_hang:
br _hang
#include "types.h"
void *_memcpy(void *dst, void *src, u32 len);
void main()
{
//Copy eid root key/iv to shared LS.
_memcpy((u8 *)0x3E000, (u8 *)0x00000, 0x30);
//Hang (the PPU should copy the key/iv from shared LS now).
while(1);
}
void *_memcpy(void *dst, void *src, u32 len)
{
u8 *d = (u8 *)dst;
u8 *s = (u8 *)src;
u32 i;
for(i = 0; i < len; i++)
d[i] = s[i];
return dst;
}
Our partner and developer RacingLocura07 (UsaveME) leaves us on this occasion the conf editor ps3, this application allows you to enable or disable patches, plugins or create flags without using a PC, all from the PS3 itself in a simple and fast
Download: http://www.sendspace.com/file/99llgd
Options:
• Displays a list of flags
• Displays list of patch-dynamic
• Displays a list of plugins
• Allows you to export to the root of the usb, the. Cfg file to test it before storing.
List of flags:
• Matheros (direct or normal)
• dumper-ram
• debug
• dev_flash (dumper / restore)
• sc35/36 +8 (more compatible)
• 100% Fan speed (fan at 100%)
Any questions you have you can reply in this thread, thanks to RacingLocura07, tito1, adriansfc92 as Cheko. Conf editor and this works both as the 3.56 MA JBM 3.55
Finally, in related PS3 homebrew news today PsyOil has made available a http://www.psyoil.info/pup/Pup%20down.zip for those interested stating:
On a click of a button a command prompt window will start downloading (from the PS3 Dev Wiki) the PUP to the same directory as the program. Do not delete wget.exe or else the pups will not download!
Its pretty simple, list of firmwares (OFW) on click they download to the directory your placed the two files in.
Now, you're probably wonder why someone would ever need this. I download and delete pups very often, so I made this program to make it a bit easy to find a PUP right away.. Making a CEX/DEX downloader soon.
Update: he has now released the http://www.psyoil.info/pup/cex-sex%20downloader.zip followed by a http://psyoil.info/pup/sexdexcex.zip stating the following:
Once again, I suck at GUI programs. I've made a command prompt version of the same program, where you just enter the name of the firmware version exmp “4.10″ and it starts downloading the firmware on command (4.10p for patch pups) Should I just release that or stick to the ghetto lookin’ GUI?
Shortly following he also made available a http://psyoil.info/pup/Pup%20extractor.zip stating, to quote:
Very simple and straight forward, place pup within the same folder as the extractor! Credit to HSReina for df.exe
Also, I've included a simple command prompt app:
Enter "pu.exe PS3UPDAT.PUP PS3UPDAT" to extract the pup.
Enter "df" to extract Dev_flash from the pup
Enjoy
Here is http://psyoil.info/pup/shop%20converter%20PUP.zip as well by PsyOil with the details below, as follows:
Sony shop PUP, just patched promo_flags/update_flags. anyways, this is just a basic pup that will convert your PS3 into a SHOP Ps3. (not advertising as a jailbreak or a CFW) its just a basic MFW.
Remember after unlocking through security settings, the package installer is NOT for homebrews but only for installing demos. The second PUP is a file that'll convert your SHOP PS3 into a retail PS3. Remember, these still apply! (scei.co.jp/ps3-eula/ps3_eula_en.html)
More PlayStation 3 News...