(adsbygoogle = window.adsbygoogle || []).push({});

PS3 patch_mp.ff's COD4, COD5, MW2

You must login or register to view this content.[/CENTER]

Guys i've been working on this for such a long time and to be honest am a little bit fed up with working on it by myself so im going to release all the knowledge i've gained over the past 6 weeks with regard to modding the COD4, COD5 and MW2 PS3 patch and will try my best to answer your questions. This is not anything to do with decrypting the HDD, this is about the decompressing and recompressing of the actual patch itself.

Firstly these are all PS3 patches which belong to myself, they are generic meaning they will work on all PS3's, so if a modded patch was produced and shared with the community, it could be re-encrypted individually and replaced onto the original patch.

Each patch is compressed with ZLIB and providing the correct headers are found, each individual GSC can be decompressed and compressed. From what i understand the patches are compressed with a window bit value of 15 (maximum compression). The ZLIB headers on XBOX 360 patches start with the bytes '38 DA'

Offzip can be used to decompress PS3 patches which is what i have used on all of the patches to get them decompessed. This then allows me to view the patches in FF viewer (Providing the correct file convention is used) and can allow me to edit them. Unfortunately because FF viewer is designed to work with PC and XBOX 360 patches, it will not save PS3 fast files with the correct compression format as PS3 FF's headers change from each block.

So basically the problem i have is that i cannot get the patches compressed correctly which is what i understand a lot of members have a similar problem. Ideally what we need to find is the ZLIB headers for the PS3 patches, then if we find the correct header relating to the correct GSC (for example the _missions.gsc - the one which contains "onPlayerSpawned" used for entering dvars into) then edit that file with some dvars, get it recompressed with the correct compression ration (Pretty sure its a window bits value of 15) then we would have a working modded patch, which then leads us onto the next problem......

From what TheUnk0wn has said is that the PS3 HDD is checksummed, i have been unable to check this out as i have been really busy lately, anyway if this is the case we will need to find an alternate method of getting the patch onto the HDD through bypassing this checksum. For those who are unsure of what a checksum is, it is a digit which checks the integrity of a file to make sure any errors or changes havent occurred. Anyway, i have a couple of ideas on how to get around this checksum, firstly you could actually work out the checksum which was done on the XBOX 360 version of COD4 but to be honest, this isn't going to happen. My second method is a much more realistic idea which could actually work, anyway when you download a patch from PSN it is encrypted as a .PKG and actually contains the patch itself (obviously) along with several other files (such as the eboot.bin etc). If the locations of the patch could be found in the .PKG it will load onto the PS3 correctly and has the potential to bypass the checksum. I have tried this method myself and looked through the .PKG but cannot find any similar data to the patch_mp.ff, i have also tried decrypting the .pkg using the PS3's HDD decryption method but had no luck. I have however managed to add the patch_mp.ff to the .PKG and manage to get it to download and install half-way before giving an error so i think it is the right route to go down, also since having hunter as a friend (doubt for much longer though but understand my reasons for posting this) when he loads up games, he will go offline, then online when loading every single game up (which is what happens when you download a patch to your ps3, you will go offline, download the patch, then come back online again). Anyway i think thats just about everything, as mentioned this is not a 'OmG hOw D0 u DeCyPt DA HaRdDrIv3?' thread, this is for those who have already reached that stage and are stuck on the next part.

Here are the PS3 Patches:

1.10 Patch MW2: You must login or register to view this content.
COD5: You must login or register to view this content.
COD4: You must login or register to view this content.

Advice:The COD4 and MW2 patches CAN be opened in FF viewer providing you dont change the file names, but as explained earlier, they cannot be saved correctly.

Credits to:
Prasoc - From S7, Creator of the FF Viewer helped me understand the patches a lot more and how they worked.
Hunter - Helped me hugely but lost contact with him when i decrypted the patch. Fantastic guy and don't hate him for not releasing his hacks.

I would appreciate some +REP for all my hard work and time that i've put into this and thank Hunter as well for finding out this exploit, if it wasn't for him, i can guarantee we wouldn't be here now, we would still be talking about some packet injection crap.

DONT POST ASKING TO GET IN A LOBBY, I HAVENT EVEN GOT IT WORKING! I AM ASKING FOR ASSISTANCE

It is, the HDD method is checksummed with no current way to get to it (if it's even possible).

If you could upload the whole decrypted patch i could get it re-encrypted as a whole so you just have to use PS3 Proxy

I tried decrypting the gamesave but it didn't work..

I'm thinking patch blocker and proxy. They are a favourite of the unkn0wn after all....

Patch blocker is a MUST, but is imposible to get it working with the cheksum of the hdd! :S

For checksums could you just brutecrc32 the checksums?

how did you open the pkg??

They are decrypted patches, they are just compressed so it looks like they are 'encrypted'.

I need the other files that come from the .pkg
If you don't have them, could you upload your partlog?

These arnt from the .PKG, they are from my HDD. But i was just saying that within a .PKG it contains loads of other things such as the eboot.bin because when you decrypt your HDD these files will be present on your HDD. And the only place they could have come from would be the .PKG. I dont have the eboot.bin or the other files, only the patches.