79w 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!
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 First of all, I would like to put three conditions:
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.
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.
where are the last game files located? i would like to make xmb mount pkgs for my games..so i can start them from xmb... thats the only reason i still have multiman on my ps3... pls tell me! somebody pls tell the creator of this wonderful app too
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...
Following up on his previous revisions, this weekend Spanish PlayStation 3 developer Estwald has updated the Iris Manager PS3 game backup manager to version 1.54 with the changes detailed below alongside some additional languages, PS1_EMU PKG files and themes.
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
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)
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:
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.
You can use the same multiMAN “covers” on Iris Manager! Just copy the “covers” folder into the Iris Manager directory
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!