108w ago - Today Spanish PlayStation 3 developer DemonHades has released the first version of their JFW DH MA-1 3.56 PS3 Custom Firmware alongside a video of it in action below.
Note: Before installing, barrybarryk warns users who install JFW DH MA-1 3.56 PS3 CFW they will not be able to downgrade without a hardware flasher... so be aware it's primarily intended for those stuck on a 3.56 base.
To quote, roughly translated: PS3 MA-1 3.56 is the first PS3 Custom Firmware version 3.56. This custom (its most basic) was ready for about 7 or 8 months, but it was not until now when I decided to publish it.
It has nothing to do with the recently published exploit the metldr, although the appearance is imminent futures higher firmwares, for which he wants to try, here it is.
First of all thanks:
Graf_Chokolo, for their great work.
A Demonhades, for its testing, its great strength.
A JaiCrab, for their help.
A Lara, for making me laugh a day.
People who have tested this 3.56 MA-1, thank you very much.
To all that s @ s who donated for a flasher, no firmware ell @ s this far along would not exist as such.
A Varicella by their selfless help.
A M.E.M, do not forget and forgive.
Tod @ s @ s that I forget that by mistake, apologize.
As the first version, it only takes the most basic functions of a custom firmware, now I'll explain. Also explain the changes performed in the 3.56 Sony, and as in its release notes, which argued as a simple patch was not just a patch.
Support PEEK / POKE lv2, using the typical SYSCALL 6 and 7 for compatibility with existing homebrew.
Support PEEK / POKE lv1 native SYSCALL using 10 and 11 respectively. These are used as SYSCALL
than the lv2, the devs just have to use them as you would those of lv1 lv2 but affecting.
Load unsigned applications, FSELF format natively. That is, a normal application or npdrm
FSELF valid format worked directly. (No touch-memory copy in the lv2).
Load logically signed applications, both official and unofficial signature valid.
Support for applications up to version 3.56.
Use of all SYSCALL system, provided that the product no later verify mode, QA, etc.
No need to modify the PARAM.SFO in the event that hypothetically would use a application that requests
a version higher than 3.56 in either npdrm / normal application / or application running from the bdemu.
Installation of Retail and Debug PKG since the PKG Install option.
System settings in the XMB QA hacked. Now you can open the options using the normal combo without
QA flag is active or a valid token or existing on your machine. Any options changed is maintained
in the system registry settings.
This QA system hack allows any SPRX to call the XMB to check this information hacked receive information, such as the nas_plugin.sprx, which in the case of DEX would permit installed without any patch of PKG Retail. As always be careful you do with those options, this is the safest way to have the QA without be QA, and not have to modify the EEPROM in any recalculated appearance or tokens of any kind. Here I have to thank Sony for making the security of your token only be in one byte and not in those
FIX: Patch to allow loading of applications for (avoids errors 0x80010009)
FIX: Patch to avoid checking the firmware version of the application against the version of firmware stored in the memory of lv2 (avoid the error 0x80010019)
FIX: Patch to avoid the error 0x8001003C (allows loading of applications that request more internally than the current version)
FIX: Patch to avoid the error 0x8001003D
FIX: Patch to avoid the error 0x8001003E (using hdd patch and have no disc inserted)
FIX: Enables the use of all SYSCALL, avoiding generic error 0x80010003.
CHANGES IN THE LV2 3.56:
FIX: Patching a new security check that prevents updater mode, it could launch an application unsigned with the minimum key 0xD (3.56), avoiding the error 0x80010009. NOTE: See NOTE AT THE END OF THIS README
FIX: otherwise is used to integrate the new SYSCALL 6, 7, 10, 11 at lv2.
Added support for PEEK / POKE NATIVE at lv1. The method used to integrate these new hypercalls not use hypercall existing one, but really any hypercall not used in the system is a peek or poke depending on the case. To interact with PEEK / POKE, lv2 use SYSCALL of 10 and 11 respectively.
Changes in the hypercall mmap (114). In the 3.56 Sony made significant changes in this hypercall to avoid the use that was being given to the lv1 to lv2 mapping. Now this hypercall checks that the key argument has not been modified, are checked mapping ranges
(Someone who understands this will realize how dangerous it is that you map the critical thing, and do not speak of lv1) the hypercall code is divided into sub-functions into chunks for rolling the analysis. 3.56 In this version of this hypercall MA has not been touched, but having the support of PEEK / POKE in lv1 mapping is no longer necessary. In a later version is not ruled out such a check hypercall it's not complicated really, just it was not necessary for this version.
Changes in the hypercall unmap (115), similar to mmap, its code shared between subfunctions.
FIX: Added some patches to avoid integrity checks lv1 / LV0.
FIX: Added patches in the SPM and the DM to enable the use of any service. The patch is different, smaller, the SS patch exists (this is no longer compatible with 3.56), in my testings my patch does not produce any kind of problem with trophies, or saved games, etc..
TODO: Delete the problem of not being able to downgrade to a version lower than 3.56. Currently not possible down from 3.56 after upgrading to the.
FIX: Patch to override the check ECDSA digital signature. Now an application with an invalid signature signed will be considered valid.
For example, "sign" an application without having the proper private key to generate a proper signature.
FIX: Patch that removes the hash check of the application segments. A hash will be considered invalid
FIX: Patch to override that you can not use FSELF retail consoles. This patch is different from that in ps3devwiki, the patch is on that page about this subject brickea machines has a problem metadata to decrypt the encrypted executables retail.
FIX: Patch to override the protection added in 3.55 (in the case of applications npdrm / normal, previously only was in charge of the RVK) which prevents applications can be used above the indicated version in the firmware today. That is, in a hypothetical case, a game trying to throw in a 3.60 3.56.
FIX: Patch to override the protection auth check the applications (added in 3.56), this check detects programs created public tools as they always put the same auth, auth superior one.
FIX: Patch to remove the protection from the white list of authorized programs, added in 3.56. Now you can use all applications as 3.55 and below.
The lv2 is protected by a hash in lv1, in case you want to play an offset that encompassed in the range of protection, this would produce a panic check off the system. To avoid this problem, use the tool that is attached to this package before using poke modify lv2. Why not to implement this patch directly is because not everyone is dev, and that can not be touched lv2 is safe for the user.
Of course the source code of this program is included, so a dev can see how using the POKE lv1 patched the problem.
You can now enter service mode, and use the lv2diag as before, but this has a potential danger. The 3.56 now makes it impossible to make a downgrade to less than 3.56, meaning that if you are in the 3.56 in him are, if you have time you tried to cancel out a version that checks the update manager. The problem is a programming error that allows updating Lv2Diag.self, the failure is that No checks that the update is in the usb or to verify that this is valid, the program formats the flash 1.2 and 3. That is, if then fails, your system would not have died partially flashes, still work ROS can use a lv2diag active again, but who Forewarned is forearmed. Lv2diag Beware!
Attached to this package is an updated application to extract the nodes of a dump of lv1 is an update of the application made by Graf Chokolo, now has support for versions 3.15, 3.41, 3.55 and 3.56 in one program. Useful to display the nodes extracted from your dump.
The firmware finished graphic will be added when finished JFW 3.41 itself.
In the package adds an application, I do not think there publicly, to put the product model directly from the XMB, acts as a toggle, in the event that you can use the product as simply so I removed the product.
As a final note to remember that this is the first version of the firmware, so constructive criticism are welcome. As I suppose that due to this publication where patches are appldr, many variants will come out of it, just remember that the first publication was this.
Do not bite the hand that feeds you, today is like tomorrow is a 3.56 higher, or maybe not.
3.56 MA-1 Installation Instructions
Assuming you want to upgrade to this version from 3.55 and below, the following steps.
1. Download the CEX 3.56 VERSION 2 from somewhere.
2. Apply the patch with included xdelta to patch on the official PUP VERSION 3.56 2.
3. Install the product using PUP by lv2diag mode, or through the XMB.
In the future, take a version for people stuck in the 3.56 flasher.
ORIGINAL VERSION 2 3.56 MD5 CEX (for reference): 2a52196399a4b96ea568aafa65d1a27e
MA-1 3.56 PUP MD5 (for reference): efe066e4836393c8bf60a5cc6804ddc3
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
very very nice... really thinking about changing to irismanager.... i think deank could do this a long time ago in multiman... but hes with teamcobra... so he want to make money... NOW he have to do it...
mm is great... it can do alot of stuff... but i really only use it for ftp, filemanager and to create xmb mount pkgs via last game...
i think its no problem to find a alternative ftp and filemanager... there are homebrew stuff for this... so the only important reason for me to use mm is to create xmb mount pkgs via load last game pkg...
if iris manager would have a function like last game... i would change really quick!!!! because i like it simple! and most of futures in mm are useless for me!!
next big thing i hope will be psp backups via irismanager... i really like this dude!!
btw is load last game working with irismanager??? i didnt tested yet!?
Following up on his revisions, today Spanish PlayStation 3 developer Estwald has updated the Iris Manager PS3 game backup manager to version 1.50 followed by v1.50.1, v1.50.2, v1.50.5, v1.50.6, v1.51, v1.52, v1.52.1, and v1.53 with the changes detailed below.
To quote, roughly translated: Well, if you do not mind, I go up and this and that people will test: your upload yours and let me know when (that can be downloaded without using git!) And I add anything new at no cost to you (if you want to take an eye for entertainment, do it ).
I've gotten notes, anyway (I played the payloads also, by the way, to add code if LV2 patches fail because the instruction cache, as seems to be happening at 3.55 in the case of black screen)
Ability to run PSX ISO
IMPORTANT extract psx iso.txt:
As added PSX isos for Iris Manager 1.50 +
Create a folder in root PSXGAMES or USB HDD
Put the PSX game folder inside. The folder name is used as the name of the game in Iris Manager.
The PSX games should be files. Bin or. Img (or. BIN,. IMG) contend sectors of 2352 bytes. You can get from 1-8 files "iso"
Iris Manager takes the isos in alphanumeric order. When you throw a game with multiple isos you can rotate the screen in order
the last moment.
You can put a cover.jpg file (maximum size 1024 x 1024 pixels)
PSX config is saved in the game folder.
Iris Manager mounts USB / BDVD and HDD0 in that order of preference to change the hard disk virtually. If a device can be mounted
It is used to simulate EJECT / PUT.
If a game has two or more discs when the game asks for a disk change, unplug and plug the USB device or disc ejects and hits CD / DVD / BR to change the "iso" (to be ax when your "ejecta" LED flashes green when you put a "new" medium green LED does not blink). The method is rotating so when using the latest iso it will change to the first iso)
NOTE: You can use a BR disc without problems PSX Emu patched. It is not necessary to eject the disc to play.
The configuration of each game is saved in your contacts, while the PSX game disc, is taken as reference for the games you have not saved the configuraracion there.
As I discuss the order they are taken multiple ISOS is alphanumeric (will 1.bin 2.bin Disc 1 and Disc 2 as)
When demos to run, if there are several, are presented with a screen that shows the order of the iso, but that makes pressing CIRCLE rotate upwards (so for example, if we are playing disc 2, you can select Start)
As I comment if you can mount a USB device is taken as "eject" first, otherwise a possible CD / DVD / BR that can be mounted and ultimately the HDD (so you can not eject). This makes it possible that if we have a game on the internal PSX with a pendrive connected and we disconnect and connect back to be changed from "ISO"
Changing ISO can only be done if the game is awaiting it and calling the appropriate function. This is because if "eject" (although no pendrive see activity in the eye) the green led flashes console. To get him back update the counter rotating.
Internally the emulator supports 8 virtual files are rotated. Iris Manager assigns all consecutively. If a game had 3 albums would be allocated as follows: 1,2,3,1,2,3,1,2 by what we see in the following sequence instead of the three would go to 1.
Although you can change discs should not tinker needlessly with that: a game may hang, so Use it only when necessary
Note that the first version of the emulator: if a game does not work but you have the assurance that if it works from ps1_emu CDROM (not the net), you tell me if I can watch it.
Indeed, in PSX options, choosing emulator is unnecessary for ISOS: ya know that you need to run (another thing that is not )
Estwald updated Iris Manager to version 1.50.1 to solve a permission issue in the FTP Server.
Estwald updated again to version 1.50.2 to fix a problem with the settings for PSX ISO
Ability to run PSX ISO (since 1.50.0)
Merged with code from D_Skywalk
Fixed small bugs (the FTP bug was fixed in 1.50.1)
Added option to copy PSX games from USB to HDD and viceversa.
MC now is cached on internal HDD and updated on the original folder returning to Iris Manager
Added option to list games per category using R2 (first all, then each category)
Fixed issue where BR drive was disappearing.
Fixed problem with a poke that could affect 3.55.
v1.51 (232014 via elotrolado.net/hilo_3-55-4-30-iris-manager-v1-38_1842936_s520#p1731460966):
Added support for 4.21 DEX
Removed "PSX unsupported" message when a PSX "ISO" is launched (syscall 8 is required to make it work; LV1 patches are not needed)
New version of the PSX emulator V2 (ps1_emu_patched2.self, do not rename it)
Added support for .ISO and .MDF (alcohol) formats for PSX images.
Images in MODE1/2048, MODE2/2336 and MODE2/2448 (CD-XA) are also supported.
All the images of the same game must be in the same format.
Added check of free space on HDD, when copying games
If size of game is larger than free space on internal HDD + 1GB, the copy is aborted
If size of game is larger than free space on external USB + 1MB, the copy is aborted
BD-EMU does not mount the HDD by default (now there are 2 options: old behavior and the default)
Some parts of the code have been touched (if some hangs occurs on start up)
The patcher tools have been unified in the same rar file
Restored the missing "mkdir" function that caused the error accessing language.ini