38w ago - While everyone is awaiting further details on PlayStation 3 Custom Firmware 4.21 from the Red Power Team, today multiMAN was updated to version 04.06.00 followed by v04.06.01 adding PS3 4.21 CFW support among the changes outlined below.
Added support for 4.21CFW (CEX) (syscall 6-10 required):
"Standard" BD-Emulator option (sc36) (Hermes not supported yet)
Direct Disc Access (LV1&LV2 patched for Storage Manager access)
Raw access to optical media (PS1 backups & Showtime access to BD/DVD/CDs)
BD-Movie Region Changer
BD-Mirror for INT/EXT games
! Not fully tested with Red Power's 4.21CFW (Hermes payload used and syscall 1021 required)
What's new in multiMAN 04.06.01:
Added support for 4.21CFW (DEX) (syscalls 6-7 required):
"Standard" BD-Emulator option (sc36)
BD-Mirror for external / USB games
Finally, below are some related comments on the multiMAN v04.06.00 update as follows:
From Lightyear: multiMAN has supported 4.21 for a LONG time. now it's just CEX 4.21 support... it's really not that different. and deank releasing mm that supports 4.21 does NOT mean a completely 3rd party scene group is working on a new 4.21 CFW! they are not even working with dean... they have their own backup manager, according to their posts. *facepalm*
FWIW, multiman automatically worked on 4.21... dean didn't change anything to make that happen. someone just tested it out and realized it worked. just like PSX support. that was just a native thing that someone just "discovered" was working one day.
From deank: I see no mentions of DEX in the "What's new"/change log, quite the contrary. And - no - the mM update server is not hacked.
I just woke up and read some posts about some chinese shtty dongle for 4.21... Just to make it clear - the mM update has nothing to do with it and doesn't need a dongle if used with 4.21cfw. It is a pure speculation I guess, because there are a lot of people around who won't allow another dongle to surface anyway. I don't believe that their dongle (which I doubt it exists at all) will see the light of any day!
Why do you ask me about their stuff? I don't know any of them nor do I know what they're going to do. Someone leaked a file from their 'promo system' (the eboot.bin they use to launch that old multiMAN version), I took a look at it, I saw what patches they use for 4.21 and implemented some of them in mM and added syscall36. As simple as that - that way nothing is hidden in 'their system/manager' and is available in the regular public mM version. I know for sure that their firmware uses hermes because I saw how the payload and stuff is loaded in that leaked eboot.bin, hence I mentioned it in mM's changelog.
I already posted what I think few pages back. In addition to that - I think it will be a huge mistake if they decide to sell dongles.
I added some additional checks to make mM recognize when it is running on peek/poke-enabled 4.21CFW. Then it adds syscall36 just like it does on 3.55, which means that games should work without patching.
When asked why update MM to a hypothetical 4.21 his reply was quite arrogantly: Because I can, no other reason.
Also from deank when asked why 4.21 CFW support was listed if not fully tested yet: Ah, just don't tell me what and where I should put.
Finally a few weeks later he partially comes clean, revealing what used to be open source code and making the following statement for those interested.
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!
Hmm, I tried the Multiman method, installed both the PS2 Classics Placeholder package (17MB, shows PS2 placeholder app on XMB and installs game\PSU10000 folder) and the PS2 Classics Placeholder R2 package (153kb). Then I created a folder for one of my working rips (PS2ISO\[SLUS-20069] The Bouncer), and ftped the ISO.BIN.ENC over to here.
The Bouncer shows up in Multiman, downloads the cover, but when I run it it just goes to XMB. I ftped it to the PS2 Placeholder XMB's folder (game\PSU10000), and it runs fine from XMB. Why not Multiman? Anyone else get this to work? It would be so convenient to load up my rips and play them alongside everything else.
Okay, I've figured it out. The one rip I can't get to work is FF12 International Zodiac Job, because it's already patched with the fan translation pack which must alter something.
Anyway, you only need the PS2 Classics Placeholder R2 package (153kb) and mM 4.30.
1. Install PS2 CPR2 package and update mM to 430.
2. Whichever method you prefer (via ftp client or mM file manager), on the PS3 create subfolders for each PS2 ISO. Name them [gameid] gamename, ie. PS2ISO\[SLUS-20069] The Bouncer.
3. Using PS2ClassicsGUI (I used 1.4), place your 2P0001-PS2U10000_00-0000111122223333.rap (or whicever RAP you use to encrypt ISO) file into ..tools\scetool\raps.
4. In PS2ClassicsGUI, hit the Encrypt tab, open your iso rip with the black folder icon, and copy/paste or type the name of the RAP into the Content ID field (ie. 2P0001-PS2U10000_00-0000111122223333). The Klicensee field should automatically populate with the hex code pulled from the RAP you copied in the aforementioned raps folder. In this example, for the generic PS2 placeholder example, the klicensee code is E4E54FD67C16C316F47829A30484D843.
5. Click the Add LIMG Sector button (if available), say yes, then the bottom Encrypt button, say yes.
6. The newly generated ISO.BIN.ENC will be in the ..tools\ folder. Take that and copy/FTP it over to your PS3 into the PS2ISO folder you created (example PS2ISO\[SLUS-20069] The Bouncer\ISO.BIN.ENC).
7. In mM, under the Retro column, hit Refresh. If you named your folder's game id correctly, mM will pull the cover automatically. The title will be exactly waht you named the folder, minus the game id part.
8. Hit x to run the game. mM will exit to XMB. (This is the part that confused me initially until I recognized the behavior)
9. Go to the PS2 Classics Placeholder icon, and hit x to start. Your game should load after a bit and a couple of resolution changes.
10. Play! No package creation required.
So basically, it's as easy as create your ISO.BIN.ENC and the corresponding game folder on the PS3, then copy the file over appropriately and enjoy. Hope this helps anyone else having issues. mM will pull the artwork and create the SAVEDATA files for you. Big thanks to CaptainCPS-X and of course DeanK for mM, and no thanks to Sony for removing PS2 emulation!
Playing Final Fantasy X International (JP) for the first time as I type this. Thanks again guys!