(adsbygoogle = window.adsbygoogle || []).push({});Games Confirmed Working with Rogero 4.21 Firmware
Games confirmed by members of PS3ISO, some require you to load with SELECT+ X withink multiman. Very tempted to update to play some of these but im waiting on a safer option.
Working
Sleeping dogs
NFL 13
Resident evil 6
Resident evil: Raccoon City
NBA 2k13
Dishonoured
Lollipop chainsaw
Sorcery
Journey
Darksiders 2
F1 2012
Borderlands 2
Madden 13
Doom 3
Persona 4
Disgaea 4
Ratchet and Clank Collection
Angry birds
Dead or Alive 5
Tekken Hybrid
Tekken Tag Tournament 2
Assassins Creed 3
Damage Inc WW2
WWF13
UFC 3
007 Legends
Of Orcs And Men
Gran Turismo 5 Academy Edition
Street fighter X Tekken
Fifa13
Medal of Honor: warfighter
Assassins Creed 3
yes borderlands 2 was confirmed working internal/external (any game in drive)
medal of honor also works fine
games from now will likely require 4.25 tho
You know they are in the process of changing all of the keys again, such a pain in the ass lol. Just glad the guys that know the ins and outs of the hardware are constantly probing looking for ways in.
You know they are in the process of changing all of the keys again, such a pain in the ass lol. Just glad the guys that know the ins and outs of the hardware are constantly probing looking for ways in.
read this a ps3 dev wrote
Breaking it down into simple and easy to understand words
Since Marcan’s answers can be a bit difficult to digest, I’ve broken them up into the form of questions and answers with the special help of ViRGE on this. This will clear alot of it up for those less technical.
Q: What exactly has been recovered?
A: The keys used by bootldr to decrypt/verify lv0, and by reversing the process the private keys used by Sony to sign lv0. If we consult our handy 3.60+ chain of trust diagram, we can see that bootldr is at the very root of the chain of trust, with lv0 being the first module it loads.
Q: So what can we do with the lv0 signing key?
A: In short, we can use it to decrypt lv0, modify it to patch out any lv0 security checks, and resign it with a legitimate key that bootldr will accept. With the chain of trust broken and lv0 no longer enforcing the security of the modules that it controls, we can then start modifying lv1ldr, lv2ldr, appldr, isoldr, etc to patch out their security checks and add CFW functionality.
Q: Can Sony “fix” this like they did for the 3.55 exploit?
A: No. With 3.55 the keys metldr used to verify its dependent modules were recovered. So Sony simply stopped using the now-insecure metldr and started using bootldr (which was still secure) to load.. Sony doesn’t have any more secure modules like bootldr left so like I said in my original post they have no options and cant fix anything; without getting too technical, we now have the keys to every “common” hardware module that is able to decrypt Sony-signed modules. The only thing left are the modules that use per-console keys, which are useless for booting common firmware (which must be decryptable by every PS3)
Q: So bootldr is fixed in hardware?
A: Correct. Like metldr, bootldr cannot be software updated by Sony. It’s hard-coded in hardware. As a reminder, bootldr/metldr themselves can’t be exploited, but because of the keys we have recovered we can make them load anything we want, nullifying whatever security they provide.
Q: What about future firmwares?
A: Good news! We can decrypt those too. Sony can use various coding tricks to make the process more difficult (this is called obfuscation), but they can’t stop us by using keys. We will always be able to decrypt lv0, and as long as we can figure out how to navigate lv0 we can figure out how to decrypt and modify its dependent modules. For those of you that follow Sony hardware this is much like how the earlier PSPs were hacked. So we can always decrypt the firmware and will be able to create newer CFWs as long as we can get past any obfuscation by Sony.
Q: So the PS3 is utterly and completely broken?
A: To an extant yes, debatable but unlike the 3.55 hack we have mostly everything needed. Sony will never be able to re-secure existing consoles.
Q: What about consoles running firmware newer than 3.55?
A: Because all “old” consoles use the same keys to verify modules like lv0, at a minimum we can decrypt, patch, and resign the firmware. The problem is that we need a way to convince the PS3 to flash our modified firmware. With 3.55 and below that was easy enough to do because of the keys recovered, but 3.56 and later change that so that flashing is more complex than just using the recovered keys. This isn’t an insurmountable problem – hardware flashers will always work – but for easy software flashing we need to find new exploits in the PS3 software stack to convince OFW consoles to flash CFW.
Q: What about newer consoles?
A: So there’s the real problem. Remember how we said bootldr and metldr are fixed in hardware? Sony can create new hardware, and update those modules in the process. By using new hardware in conjunction with new firmware for that hardware, Sony could completely change the keys used to secure the system. Without getting too technical, all of this progress comes from the fact that Sony was sloppy and did a poor job of implementing their security on earlier consoles, which is what lead to the first keys being leaked. Sony could always issue new hardware with new keys and a fixed security system at which point we’d be completely locked out of that new hardware. It’s entirely possible they’ll do this (if they haven’t done so already), so much like the PSP we’re going to end up with a limited number of consoles that have hardware-based flaws that can be exploited. Of course we then found new ways of exploiting the PSP anyhow, and ultimately were able to exploit every PSP made in one way or another.
If you are on anything higher than 3.55 it doesn’t mean you are out, there are ways to downgrade if your model is one thats able, otherwise you are just not able to do anything right now until more dev work is done. So sit tight and hold on. Again stay tuned, more info and news will be definitely coming.
The following user thanked DEREKTROTTER for this useful post:
Breaking it down into simple and easy to understand words
Yeah, I was reading on psxhax and tortuga about the LV0 keys. Nice break down though, sometimes it is hard to convert engineer speak to standard english. Sometimes its worse than trying to determine how to make sense of the legaleze crap that lawyers come up with.
---------- Post added at 11:26 AM ---------- Previous post was at 11:24 AM ----------
what version of multiman you have?
make sure you have a disc in the drive, load with multiman SELECT+X if needed
i have the latest version (4.0 and i have tried with cd but i get the error 80010009 and 80010017!
i have a question, i have check firmware version and is not spoofed to 4.25 why?
anyay i need to install the update befor run the game?
i have the latest version (4.0 and i have tried with cd but i get the error 80010009 and 80010017!
i have a question, i have check firmware version and is not spoofed to 4.25 why?
anyay i need to install the update befor run the game?
i will let u know as im downloading MOH now, some people have reported the older version of multiman is better