PS3MFW Builder 1.0.0 (Our MFW 1.0.0) is Officially Released
Following up on the previous updates and the recent PS3 MFW XMB InGame ScreenShot progress, PlayStation 3 developers RedDot-3ND7355 and B7U3 C50SS have now officially released PS3MFW (PS3 Modified Firmware) Builder 1.0.0 dubbed Our MFW 1.0.0 followed by PS3MFW v0.3.1 + 4.xx Tasks with the changes below.
To quote: Hey everyone! As you may know that the "official" (stated by our team) PS3MFW Builder 1.0.0 is now released! Here's a little word:
Thanks everyone who had been helping A LOT! And for making this possible! Thx for all your time that you used up to make this is STABLE as possible... Even tho it will still be under update because of new pup releases! Anyways heres the credits!
Finally we had fixed and got MFW Builder 0.3 to work and made 0.3.1
Enjoy this fix and u can add our tasks from our git
Or even your owns...
MFW Tasks (Custom)
Here are our own MFW Tasks hand made! took patterns from the 4.xx features in mfw builder v3 pre-release! If any tasks dosen't work plz report back! And if your a programer that is good in this lik Glevand then plz join us! Thanks and Enjoy!
From haxxxen: Just a small task (patch_game_plugin.zip linked above) to share.. it will remove the debug message "Quit Game: No Request Event" from DEX or REBUG firmwares (the info symbol won't be removed), still searching for fake save data owner message, but not very easy to find. It seems it is hardcoded somewhere else, but not in modules.
I have found now that fake save data owner message by browsing vsh strings... I have packed both tasks into one, so you can choose both options at same time and it seperates rebug and dex firmware. it is still in old format though, sorry RedDot the info symbols will remain on both patches for manual patching:
So lets be real... So many new fw's get released everytime Sony has an update... sure you get the added capability but at the risk of a brick... which I never want to find when I can just keep getting 3.55 patches for games I actually want to play..
Have and will always will be on KMEAW 3.55 until possibly a new FW comes out supporting PS2 iso execution (Leak)... or if it just gets ported onto Deanks project I might just stay indefinitely. I just have to ask whats the point when MFW programs exist and people just rip off a CFW generated from tools like these add a name and sites front page it.. ?
Also from toolboy2012: Ok All, So I have NOT yet actually attempted to install/flash a CFW from my build, but I know you guys have been testing for quite some time, as you were mentioning the 'corruption' issue when trying to install over an existing 4.xx CFW. But I plan on doing it soon, now that hopefully we have the worst mess out of the way... (or at least I hope so!!)
Here's what is all fixed up, and all checked into my PS3MFW repo (and the associated source repos as well)
NOTE: PKGTOOL and SCETOOL both NOW USE the "PS3_KEYS" environment variable (just like the PS3MFW sets the 'PS3_KEYS' build variable), so make sure you set this env. variable in your windows 'environment variable setup', or if NOT, the keys search will then look in the "./data" path for the "keys, curves, vsh_curves" files...
So you can look at my base.tcl to see how I'm calling the 'pkgtool', with the arguments (basically it was a drop-in where the old tools were, I didn't have to change any file paths/output paths, just add in the 'calling' parameters... I still have to add the "-help" option to the pkgtool with more info, I just haven't had a chance to add it yet!
The "-key" option for "pkgtool" is now just OPTIONAL, you do NOT need to specify any key names anymore, as they are
auto-loaded from the scetool 'keys' file. (although you can use this option to 'override' the auto search, and find
the exact key you want to use)
SO TWO TOTAL 'other' key types had to be put into the 'keys' file for the COS/PUP files, and for the SPKG output stuff, they are shown below for reference (especially if you want to just add to your own 'keys' file)
I DID put my keys files back (for now) into my PS3MFW repo, just so you won't be fighting with key issues for now... eventually I'll take them back out, as I hate having that stuff in with my source... here is the two keys you need to add to the latest 'keys' file: (they are ALREADY in my keys file in my repo) (I've re-upped my keys files for now, so you all can take them if you don't already have them)
So let me know how it all goes, I hope things start working now, if not, at least we are much much closer! But I really feel the spkg hdr issues should be fixed...
BTW, one thing I noticed, still need to add support for the "unspp/spp" into the base.tcl, to use SCETOOL, rather than the old spp keys, as scetool does have suppport for SPP files... so I'll work on that as well... (was going to add the SPP code into my pkgtool, but no need, as scetool already has it!)
From RedDot-3ND7355: Is that spkg private key even good? Take a look at the spkg after using this one 00542D46E7B3DAAC8AEB81E533873AABD6D74BB710. BTW, Thanks for the huge update! Cheers!
That link has also been added to the main article... I generally keep them updated myself until major revisions surface, then I simply create a new article and start all over. Thanks for the heads-up B7U3 C50SS and +Rep!