[CaptainCPS-X]

Originally Posted by rocknard Sorry but it seems very simply. Do you say i can create one pkg signed for 3.70 (unpack and repack with new sfo) and only modifying the param.sfo for 3.55 or 3.41 can i play this??? Amazingly simply, no? And the eboot? not important? I always recompile pkg's fix changing ebootfix+param.sfo but if this is 3.70 will this work?? Sorry for my bad english

PKG files use a global key, therefore, they can be decrypted / extracted no matter if the content inside of them is designed for any specific Firmware.

For example, if I wanted, I could download the PKG file for Metal Gear Solid 4 update from Sony servers (content is designed for 4.0+ FW) , and I will be able to extract its contents because of what I said previously .

Do not be confused though, this doesn't mean that the content will be decrypted when extracted from the PKG. The content will still be encrypted and signed for 4.0+ FW. The files must be individually patched by unknown means, like for example "Anonymous" unreleased method.

SeeYa!

[rocknard]

Originally Posted by CaptainCPS-X PKG files use a global key, therefore, they can be decrypted / extracted no matter if the content inside of them is designed for any specific Firmware. For example, if I wanted, I could download the PKG file for Metal Gear Solid 4 update from Sony servers (content is designed for 4.0+ FW) , and I will be able to extract its contents because of what I said previously . Do not be confused though, this doesn't mean that the content will be decrypted when extracted from the PKG. The content will still be encrypted and signed for 4.0+ FW. The files must be individually patched by unknown means, like for example "Anonymous" unreleased method. SeeYa!

Can i try this with one pkg update 1.05 from AC revelations signed for 3.70 and it will work??? ignore the eboot and only change the fw version from . param.sfo.?'

what is this method from "anonymous", sorry but i don't understand how can you fix the demo from 4.10 if you don't know the metod?? do you change anything in eboot???

[CaptainCPS-X]

Originally Posted by rocknard Can i try this with one pkg update 1.05 from AC revelations signed for 3.70 and it will work??? ignore the eboot and only change the fw version from . param.sfo.?'

If you make a re-pack of the original update, and just change the PARAM.SFO, the game will try to boot, but will give you an error code 8XXXX... and throw you back to XMB.

You need to decrypt + resign the EBOOT.BIN / *.SELF / *.SPRX files for lower FW, for example 3.40 - 3.55 to make it work.

SeeYa!

[rocknard]

Originally Posted by CaptainCPS-X If you make a re-pack of the original update, and just change the PARAM.SFO, the game will try to boot, but will give you an error code 8XXXX... and throw you back to XMB. You need to decrypt + resign the EBOOT.BIN / *.SELF / *.SPRX files for lower FW, for example 3.40 - 3.55 to make it work. SeeYa!

Hehehe. i always do it, but my "confusion" is how do you do with updates above 3.60+.

Don't lie me!!

thx for attention me

[CaptainCPS-X]

Originally Posted by rocknard Hehehe. i always do it, but my "confusion" is how do you do with updates above 3.60+. Don't lie me!! thx for attention me

LOL, if you're asking me how to "decrypt" or "sign" 3.61+ content, I am sorry but that information is only know by the "Anonymous" person who is releasing these latest patches.

I just do the easy-to-install PKGs so people don't have to rebuild their PS3 Database.

SeeYa!

[rocknard]

Originally Posted by CaptainCPS-X LOL, if you're asking me how to "decrypt" or "sign" 3.61+ content, I am sorry but that information is only know by the "Anonymous" person who is releasing these latest patches. I just do the easy-to-install PKGs so people don't have to rebuild their PS3 Database. SeeYa!

hehe ok ok. Tell him "Anonymous" if he can create one fix for update 1.05 (3.70) ac revelations (the fix from duplex is bugged on memories desmond). Thxx master

[sandungas]

Originally Posted by CaptainCPS-X Here is an example of a simple patch @sandungas , so we can basically avoid having to re-package the whole game / demo with all files. Just some moments ago I posted this (tested) Dyad Demo (FW 4.10) - Patched for CFW 3.40+ http://www.ps3hax.net/showthread.php...496#post415496 This is basically what I did: 1- Downloaded the Demo 2- Unpacked the original files 3- Copied the only the "necessary" files to make a PKG (ICON0.PNG, PIC1.PNG, PARAM.SFO, USRDIR/EBOOT.BIN) 4- Replaced PARAM.SFO and EBOOT.BIN with patched ones. 5- Repacked into a new PKG Then I just installed the Demo first and then the Patch EDIT: There was no need to Rebuild PS3 DB for this, as you stated on the wiki, every time a PKG is installed it automatically updates the DB with the new info. SeeYa!

This doesnt works when the update adds important features (like the patch 2.00 for heavy rain that adds "move controller" support")
The EBOOT.BIN is like the main menu you see when the game boots + all the funtions of the game
So in this example the move patch needs the specific files used by "move" feature that are contained in the patch... if you remove them the game will crash

Same can happen with other patches

[CaptainCPS-X]

Originally Posted by sandungas This doesnt works when the update adds important features (like the patch 2.00 for heavy rain that adds "move controller" support") The EBOOT.BIN is like the main menu you see when the game boots + all the funtions of the game So in this example the move patch needs the specific files used by "move" feature that are contained in the patch... if you remove them the game will crash Same can happen with other patches

Yeah, but it is ok, because of this:

1- User install original update / game PKG (full install)
2- User install a PKG file with resigned self(s) / eboot / sprx(s)
3- PS3 will 'not' remove the essential files installed in step (1) when installing the PKG from step (2), the system will just update / overwrite all files included in the new patched PKG.

EDIT: The system will update the PS3 Database as well with the new PARAM.SFO information from step (2).

SeeYa!

[sandungas]

Originally Posted by CaptainCPS-X Yeah, but it is ok, because of this: 1- User install original update / game PKG (full install) 2- User install a PKG file with resigned self(s) / eboot / sprx(s) 3- PS3 will 'not' remove the essential files installed in step (1) when installing the PKG from step (2), the system will just update / overwrite all files included in the new patched PKG. SeeYa!

Yeah, this is the idea, the two important things that needs to be considered are APP_VER and PS3_SYSTEM_VER e.g with gran turismo would be something like this:

disc -----------> APP_VER = 01.00, PS3_SYSTEM_VER = 3.50
patch 01.01 ---> APP_VER = 01.01, PS3_SYSTEM_VER = 3.55 (200mb)
patch 01.02 ---> APP_VER = 01.02, PS3_SYSTEM_VER = 3.60 (400mb)

fix ------------> APP_VER = 01.03, PS3_SYSTEM_VER = 3.40 (5mb)

This is a correct way to do it, the problem is the APP_VER in the fix has increased and the real 01.03 patch cant be installed.... but later a 01.04 patch can be installed and ruin all (it depends if are cummulative)

In this example the better way to keep the "standard" is by making a fix with APP_VER 01.02 intented to be installed over the real patch with the same APP_VER 01.02 (so after installation his APP_VER is the same)
Maybe this can be done by using TARGET_APP_VER but never tested myself

Edit:
The other way is by making the fix APP_VER = 09.99... this blocks all the next patches

[CaptainCPS-X]

Originally Posted by sandungas Yeah, this is the idea, the two important things that needs to be considered are APP_VER and PS3_SYSTEM_VER e.g with gran turismo would be something like this: disc -----------> APP_VER = 01.00, PS3_SYSTEM_VER = 3.50 patch 01.01 ---> APP_VER = 01.01, PS3_SYSTEM_VER = 3.55 (200mb) patch 01.02 ---> APP_VER = 01.01, PS3_SYSTEM_VER = 3.60 (400mb) fix ------------> APP_VER = 01.02, PS3_SYSTEM_VER = 3.40 (5mb) This is a correct way to do it, the problem is the APP_VER in the fix has increased and the real 01.02 patch cant be installed.... but later a 01.03 patch can be installed and ruin all (it depends if are cummulative) In this example the better way to keep the "standard" is by making a patch with APP_VER 01.01 (so after installed... the patch version is the same) Maybe this can be done b using TARGET_APP_VER but never tested myself

Indeed, that is how I am actually packing my fixes, I never change the APP_VER, I leave it as it was in the original update, I just change the Minimum FW Version (in PARAM.SFO).

I have Gran Turismo so I will make some tests and let you know .

Thanks for the feedback and information.

SeeYa!



************* [ - Post Merged - ] *************


I believe the right approach if there was going to be a "Standard" made for update patches, is like you said @sandungas , just put APP_VER - 09.99

So the user will never update unless a new patch is released, then he can manually update with the new patch fix safely.

I will re-patch all my released PKGs and re-upload them soon, maybe I will make a thread with them soon, so at least on my end I'm following the right approach . We will just have to exhort other patch makers to do it the same way.

SeeYa!