For those keeping track, Operation Flashpoint: Red River's TITLE_ID is BLES-01171 with the patch version 01.01.
MultiMAN PS3 back-up users can download the latest game update patch from within the application, then simply put it on a USB drive and select install via 'Install Packages' and the .SFO file will automatically be changed as outlined below:
1. Insert Disc in PS3
2. Start Multiman
3. Highlight Operation Flashpoint: Red River and press Triangle
4. Select UPDATE
5. Save the file [48MBish]
6. Exit to XMB
7. Install update via PACKAGE INSTALLER
8. Boot Game via MM allowing MM to change PARAM.SFO
Quick Reminder: The more games that get added to [Register or Login to view links], the more games I can search for updates and can report have 3.5000 patches.
Games with a 3.6000 signed eboot cannot be launched on current CFW solutions (as FW 3.5500 doesn't have the 3.6000 keys).
Game updates effectively replace the eboot that comes on the disk, with an updated version.
If the game update pushed out is not signed with the 3.6000 key and instead the 3.5000 key - the requirment to play the game is reduced from 3.6000 to 3.5000.
This is how you can play 3.6000 games such as Duke Nukem Forever and Operation Flashpoint: Red River on 3.55 CFW.
It also works the other way Gran Turismo 5 (a 03.5000 game) recently had a patch (v1.10) containing a 03.6000 eboot - if you were to update to this patch the requirment to play the game is increased from 3.5000 to 3.6000 - meaning you would not be able to play this game anymore on current CFW solutions (you can always just stay on older updates, or not update at all)
Games such as Portal 2 do not have any updates released and is therefor impossible to change the requirement of 3.6000 to anything usable for current CFW solutions.
yep it does.. so I download the update through Multiman - and then install as a Package, then re-run game through multiman? or is there something else involved? Also do I need to 100% check the update is able to be patched before even attempting to update to prevent a 3.60 signed update being written over game?