[JonahUK]

@CaptainCPS-X

That's what I thought, thanks for the confirmation.

@YlodedKing
Seems you may not have copied over everything needed which is why the game didn't boot. The param.sfo had nothing to do with it.

[sandungas]

Originally Posted by CaptainCPS-X What I been doing is: - download the "official" PKG using for example ( http://yifan.lu/psn/ ) or AldosTools Updater - extract its content into a new directory - replace the original EBOOT.BIN + PARAM.SFO <---- and all the .self files of the game - repack using AldosTools Shell Extension - Install new PKG - Play!...no need to rebuild PS3 database

The problem with this method is what i explained before... when the original update.pkg is too big (e.g: patches from saints row the third)... the file you are creating has the same size (there are patches bigger than 500mb)
I think is not good enought to be an "standard" method to make fixes because this problem with the size

[baargle]

Originally Posted by Ada Love Lace So consider it as not news but as tutorial/ highlight for users to make better fix (and testing them) More people can get their way to SFO, better it will be. Also, it s not necessary to have everyday astonish news, You can also create one new about cross buy feature (it s different than psp remastered) recently announced and give your theory on it (if it will have specific category on SFO...) If you want for technical infos, go to the wiki (don t check too much my edits they are only for history) and check Glevand latest edits (and make a new about it can be nice also)

That's a great idea, but how about saying as such in the news.

Even more ridiculous than this news.

You make a very good point though, a news front page thing should be done so the lesser able can make their own fixes as it is very easy. Obviously with the correct heading

[sandungas]

Originally Posted by baargle That's a great idea, but how about saying as such in the news. Even more ridiculous than this news. You make a very good point though, a news front page thing should be done so the lesser able can make their own fixes as it is very easy. Obviously with the correct heading

Well, right, the title of the thread "Pwning theory"... i see no pwning possible at all from SFO's (not even messing with the XMB database), but i like to see people playing with them
Patches is one of the things i never gave enought time to test, but there are some interesting "undocumented" features that are related with this

I added some notes in this section, take a look CaptainCPS-X, it seems you are very used with patches and motived enought to test new things
http://www.ps3devwiki.com/wiki/PARAM...eating_Patches

I think the most interesting is TARGET_APP_VER can be used to define a target patch (only is installed if the target matches)
In combination with the same APP_VER this can make "cummulative installations" (or the opposite of cummulatives, my english sucks)
http://www.ps3devwiki.com/wiki/PARAM.SFO#TARGET_APP_VER

[CaptainCPS-X]

Originally Posted by sandungas The problem with this method is what i explained before... when the original update.pkg is too big (e.g: patches from saints row the third)... the file you are creating has the same size (there are patches bigger than 500mb) I think is not good enought to be an "standard" method to make fixes because this problem with the size

I am currently testing a solution for this

SeeYa!



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

Originally Posted by sandungas Well, right, the title of the thread "Pwning theory"... i see no pwning possible at all from SFO's (not even messing with the XMB database), but i like to see people playing with them Patches is one of the things i never gave enought time to test, but there are some interesting "undocumented" features that are related with this I added some notes in this section, take a look CaptainCPS-X, it seems you are very used with patches and motived enought to test new things http://www.ps3devwiki.com/wiki/PARAM...eating_Patches I think the most interesting is TARGET_APP_VER can be used to define a target patch (only is installed if the target matches) In combination with the same APP_VER this can make "cummulative installations" (or the opposite of cummulatives, my english sucks) http://www.ps3devwiki.com/wiki/PARAM.SFO#TARGET_APP_VER

Nice information! thanks for the tips! I appreciate it!

SeeYa!

[rocknard]

Originally Posted by sandungas The problem with this method is what i explained before... when the original update.pkg is too big (e.g: patches from saints row the third)... the file you are creating has the same size (there are patches bigger than 500mb) I think is not good enought to be an "standard" method to make fixes because this problem with the size

and is it for what?? for play games +3.60; 4.10 etc?? very simple

[CaptainCPS-X]

Originally Posted by rocknard and is it for what?? for play games +3.60; 4.10 etc?? very simple

What @sandungas said is not FW specific is in general.

SeeYa!

[rocknard]

Originally Posted by CaptainCPS-X What @sandungas said is not FW specific is in general. SeeYa!

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

[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!

[rocknard]

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!

yes.. but the problem is the "eboot". we can't resing eboots above 3.60+ for now. or the eboot is signed for 4.10???