This payload is for the ps3 on firmware 3.41. It uses the ps3 to decrypt the selfs (using the 3.41 or below alogirthms) for us like it would do for any game to read the code and run it. After the game is decrypted by the ps3 the data is ran through the hypervisor to check if it is "legit". When it is in the hypervisor the payload "pulls it out" or "dumps the hypervisor" and then you have the decrypted data and that data is placed in a file.

Now here is why we can't do this with the black ops retail selfs.

The black ops eboot is signed with 3.50 keys which use the 3.50 algorithm. So that means that we would have to have this on the 3.50 firmware or above because that is what the algorithm for 3.5 self decryption is on. Which is not possible with just a payload. So, sorry to tell you this, this will not help us, yet.

The only way this would work is if you ported over the 3.50 or 3.55 self decryption algorithm in a cfw. Which if we did find this algorithm, we wouldnt even need the payload, as we could just use it to decrypt them.


NOOB SUMMARY: No mods online yet.

why did Graf even release the tools in the first place if they wont work on 3.55

For every npdrm before 3.50... It still can be kinda usefull for some older games.

true but still if he has the ability to create tools for NPDRM's for 3.41 then he should sooner or later be able to get the tools up for 3.50 and up... do you know anyone aside from him and geohotz that would know how to program anything like that??? :pedo:

Well title says it all but here is why:

i have a guy on my msn. who made his own CFW 3.55 with payloads.
and he had to port over the 3.55 to get the self decryption algorithm. he reckons it only took him a few hours..
and this guy bricked 2 ps3's as he didnt know how to make CFW in the first place.
but with his CFW he can decrypt any retail .self/.bin and he encrypts with geohots....

really i would like to see a little proof did he even show you proof or did he just say that?