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

November 14, 2011 // 3:37 pm - 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.

Download: JFW DH MA-1 3.56 PS3 Custom Firmware / JFW DH MA-1 3.56 PS3 Custom Firmware (Full) by Maara

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 B.E
  • 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.

FUNCTIONS

  • 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
should be.

LV2

  • 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.

LV1

  • 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.

LV0 APPLDR

  • 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
    valid.
  • 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.

NOTES

  • 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.

1.xdelta 356MA-MD5: d6ead544a81564331851b4e8b8d96c6d
DeltaPatcherLite.exe MD5: 05f144ebff7043c09107352315278ada
xdelta.exe MD5: 1c6b3a6e1e9df2c8313bcf98aabfc8e1
ProductModeXMB MD5: 6a4d8a189a202a988bc1f5425446b190
RepoMaster.exe MD5: 741e08ed4dd51d0cefa8faa1d043e766

ORIGINAL VERSION 2 3.56 MD5 CEX (for reference): 2a52196399a4b96ea568aafa65d1a27e
MA-1 3.56 PUP MD5 (for reference): efe066e4836393c8bf60a5cc6804ddc3





JFW DH MA-1 3.56 PS3 Custom Firmware is Now Available

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.



#905 - StanSmith - January 17, 2013 // 7:58 am
StanSmith's Avatar
Nice update. Now all my games have covers. BTW, That update is now Iris Manager v1.49.2 followed by v1.49.3 as outlined above.

Thats what it installed as for me.

#904 - PS4 News - January 16, 2013 // 1:15 pm
PS4 News's Avatar
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.

More PlayStation 3 News...

#903 - R34P3R - January 9, 2013 // 2:03 pm
R34P3R's Avatar
Glad to see an update from these guys. Been using Iris Manager for a while now. Not too shabby How's MultiMan different? Sorry for asking, I'm new to all of this

Been using Game Backup System to backup my games, proven to be quite a killer combination with Iris Manager

#902 - sly1986 - January 4, 2013 // 4:16 pm
sly1986's Avatar
Don't work on CFW Dex 4.21 PS3ITA, freeze all games and PS3 dont turn off.

#901 - BluRay - January 4, 2013 // 3:38 pm
BluRay's Avatar
MultiMan works perfectly on all of Rebug's CFWs. I don't know how you guys are having perfomance issues with it, the latest upgrades were there to improve that, it's faster than ever.

#900 - PS4 News - January 4, 2013 // 11:21 am
PS4 News's Avatar
Except for DEX stuff, this is the ongoing Iris Manager thread we use... however, in an upcoming release I will start a new dedicated thread for it per your suggestion. It appears they are kicking Iris Manager development into high gear lately so it probably won't be too long.

#899 - Anger007 - January 4, 2013 // 11:19 am
Anger007's Avatar
don't know if i should point this out but as this thread should be dead by now, and the convo is most certainly off topic, can't we move the convo to a new thread?

erm just ignore this post i just went through it and realised the iris creator is to do with dh so... i'm a dumbass today.

#898 - Azrial - January 4, 2013 // 11:03 am
Azrial's Avatar
I've updated my MM yesterday to latest version, still as nippy as ever for me, did go a bit clunky at around v4.14, but all that seems to have sorted itself out.

#897 - fantopoulos - January 4, 2013 // 10:39 am
fantopoulos's Avatar
Quote Originally Posted by StanSmith View Post
As MultiMan is becoming bloatware I'll give this a go.

Just tried it on 4.21REX and it says "Unsupported firmware" and quits.

i totally agree deank put so much uneeded crap into mm it slowed it down i haven't updated since 14.04 myself it is slow and only get slower folks iris is the new manager go Estwald, i consider both friends and talented but i got to give this one to iris you cant even hook up 2 usb on mm iris you can

#896 - PS4 News - January 4, 2013 // 8:12 am
PS4 News's Avatar
Following up on the previous revision, today Spanish PlayStation 3 developer Estwald has updated the Iris Manager PS3 game backup manager to version 1.45 followed by v1.46, v1.46.2 and v1.46.3 with the changes outlined below.

Download: Iris Manager v1.45 for v4.XX PS3 CFW / Iris Manager v1.46 for v4.XX PS3 CFW / Iris Manager v1.46.2 for v4.XX PS3 CFW / Iris Manager v1.46.3 for v4.XX PS3 CFW / Iris Manager v1.46.3 for v4.XX PS3 CFW (Source Code)

To quote, roughly translated: Well, Version 1.45 at this rate, we will update the rhythm of Multiman [+ laughs]. No, really: unless it is something of God, I have no intention to update more

In firmware version 3.41 is added: all works, as I have above and arranged the 3.55, which brought us to head for a stupid mistake [+ laughs], but also had a problem with one of the "pokes" I had to solve. And those of us in 4.30, what?.

Then I thought about the whiners: D_Skywalk is who has control of the versions after all and I have no guilt if you do not like the "flicker" that put the icon or the colors I choose [qmparto]. So the best we can do is "fool" and minimally modify the GUI to accomplish the following:

Now there are 8 colors to choose, the first four, as always, with the fading light of the selected icon appears D_Skywalk likes, but others we mola Unless, that is "not seen" so fast.

The next four activate the "flicker" that got me, you fat and shrinks the icon. The first is the "Beautiful Blue" that some claims in a while [qmparto] [plasma], the second is the same as the default (gray-beige) and the third a blue-violet and the fourth new rosita for girls D_Skywalk including [haha].

The reason for two-color copy of the original, is that I know: some will want to use those colors but with the "blink" again (or worse: want the new colors but how D_Skywalk) [Toctoc]. So this time we win and I think we keep D_Skywalk happy to, because the changes I had to do to all that are minimal and respect both.

By the way, Mr. D_Skywalk: this time if I left a brief note. Some changes you may seem trivial, but I assure you that in the absence of 3.55 parenthesis in a function petaba poke me the entire application. There are things that are done in a certain way, that's how it seems to work and not on a whim. Take this into consideration [+ laughs]

Regards

1.45 Changelog:

  • Support for firmware 3.41, 3.55 fixed, 21.4 adds DEX
  • Fixes installer PKG
  • Added new background colors with automatic selection of "flicker" or not. These changes are minor and I hope that you accept as is. Basically, if you use the first four colors is selected icon as you let him, but if you select the 4 new (2 are the same as those you use your) changes to flashing mode so clever

Salgo minor bug or market, this is the last change I have thought to do that is not related with the ISOS.

v1.46 Changelog:

  • Added the patch for 4.30 Rebug LV1 CEX to prevent the "panic shutdown" bug from occurring
  • Improved recognition of PSX discs

v1.46.2 Changelog:

  • PSX / PS1 disc games bug fix

Rough translation (via elotrolado.net/hilo_3-55-4-30-iris-manager-v1-38_1842936_s280#p1731280734): Good Estwald, Since I'm "tester" because I'm indicating hehe . Following the same tests as I said in another post, it seems that still does not work and the original directly, or the backup (unless another hard target if recognized earlier and then force the restart of play) [buuuaaaa].

Well, as always follow your progress and encouragement. Regards and happy hehe kings. I just uploaded a new version that fixes that. The modification basically consists of adding this, for which you are interested.
[code]
if(find_device==11) sprintf(filename, "/dev_bdvd");
else if(find_device==0) sprintf(filename, "/dev_hdd0");
else sprintf(filename, "/dev_usb00%c", 47+find_device);

DIR *dir;
dir = opendir (filename);

if (dir) {
closedir (dir);

if(find_device >= 0 && find_device < 11) move_bdemubackup_to_origin(1