[Ada Love Lace]

Hellsing9, this article is not complete (about somes eboots / sfo type), not really right (speaking about rebuilt data base is the last resort) and the best you can got from editing your SFO is having your remote play control or music in game (and match your FW in this case)?
I m not saying it s wrong and it s nice to have it in high light so people will start to do better fix but it s not news.

Edit: Sandungas is the master SFO and thanks to that wiki page (and other SFO pioneer who came first with this int32 descriptions) was able to understand this file.

To make sure, i don t complain about that article because it s nice to see more people around SFO (especially about update) but it s not really new, it s more like to remember people to don t be lazy when they do theirs fix.

[DEFAULTDNB]

Thank you @Ada Love Lace for giving your thoughts. It just doesn't seem correct to me, and I am no expert at all.

[hellsing9]

Originally Posted by Ada Love Lace Hellsing9, this article is not complete (about somes eboots / sfo type), not really right (speaking about rebuilt data base is the last resort) and the best you can got from editing your SFO is having your remote play control or music in game (and match your FW in this case)? I m not saying it s wrong and it s nice to have it in high light so people will start to do better fix but it s not news.

That's the reason of the pic = Not complete, it's up to the community (unity) to get a better or another workaround or just depend on what Anon have to say.

*Don't shoot the messenger* they said...

We have you, @sandungas and more people that have field experience on this.
About if it not news, or if is news.
Many users if they are willing to learn how to patch things up, will be *forced* somehow to learn the basics.
The ones who want the download link posted on the frontpage and DEMANDS for a solution, well that's another story.

[sandungas]

We was discussing about this in the IRC, heheh
Is not correct that PARAM.SFO mods can be used to boot newer games

The conversation with this <anon> i think was focused to how to install "fixes" (there are some different ways... all are based in replacing files)
Basically, you need to replace (from the backup folder, or from one of his patches installation folder) the EBOOT.BIN and all the .self's of the game

If you do it manually... you dont need any more, but if you want to do it with a .pkg... then you need to use a PARAM.SFO
And this gives a few different ways to do it...


<+sandungas> <Anon>not much can be done about that without releasing the full pkgs
<+sandungas> <Anon>which is not for me to do.
<+sandungas> and this is not right btw... this is not the "only" solution
<+sandungas> you can make a patch.pkg that replaces it
<+sandungas> is easy, there is people doing it this way
<+sandungas> you must include in the patch.pkg the EBOOT.BIN + PARAM.SFO + all the needed .elf's
<+sandungas> and in the PARAM.SFO .... you need to decide what to do with the APP_VER (version of the patch)
<+sandungas> you can use some trick (there are) to keep the original number...
<+sandungas> or you can fake it as 9.99
<%Hellsing9> spoof
<+sandungas> spoof is not enought
<+sandungas> you need to make the patch.pkg to replace files
<+sandungas> but what this <anon> proposes....
<+sandungas> is to use the original patch.... replace eboot + .elf's in it... then repackage keeping the original PARAM.SFO values
<+sandungas> this is good... but.... there is a big problem
<+sandungas> what happens if the patch has a huge size ?... like the ones for gt5 or lot of games ?
<+sandungas> this means your "fix" will have a huge size
<+sandungas> this is why is not the best way to do it

[Asure]

I don't get what all this is about. We still can't decrypt the eboot(s) in the package, right?
Any package/update builder should know by now, the param.sfo must be hexedited (or search/replace) the fw version to say, 3.40. But they don't all know you must do it before you build the PKG..

If you install a pkg, with SFO inside of 4.0, it will be stored as 'requires 4.0' in the dbase.
If you then replace that SFO with a lower version by FTP, it will still be 4.0 in the database, and you can work around that by rebuilding.

Offcourse it's better to have your SFO say 3.41, before you make a pkg of your fix/update/crack etc. but not everybody knows this.

Anyway, i don't see how this gets eboots from higher versions working if they are signed with 3.72+ keys.. Unless they aren't really signed with higher keys, just 3.60..

[DEFAULTDNB]

Interesting, thank you @sandungas

[Ada Love Lace]

Originally Posted by hellsing9 That's the reason of the pic = Not complete, it's up to the community (unity) to get a better or another workaround or just depend on what Anon have to say. *Don't shoot the messenger* they said...

I edited my previous message and if it was just up to me, everyday can have one or two article about param.sfo, hip/his, disc.sfo and .pfd. I admit to be some specific feeling to theses files,
About param.sfo update: there are one flag or more still unknown and to document them in different case. I don t know if this unknown flag can do magic but i ll guess no.
About param.sfo on Disc Game, there are one old flag i strongly suspect , still not documented but if i m right, it s "useless" like the flag for chat voice or old xmb in game.

About category on SFO, there are fews unknown, most of them only have name on the wiki. I suspect one other but again it will be useless. The category we got only the name like X3, WT, BV VF ...it might be interesting but no magic on them.

One new possible category can be also for cross buy feature (game you play on ps3 and ps vita) and one possible new attribute can be PS VITA export (i doubt it will be from Attribute) so we can transfer our ps1 classic to the ps vita like it s already possible to do with PSP (you need to add the specific file keys.bin to make it working)

It s nice to see article on SFO and i hope lot of people will check the wiki page.

[p666]

I think he's just saying, if you install a 4.x pkg update while running 4.x DEX (for a legit game), if you go back to 3.55, then unless you rebuild your database, any CFW game fix you might have created for 3.55 will not work, even if you patch the SFO. This is because the DB still says requires 4.x

So if you are mucking around with trying to generate a fix for CFW 3.55, just make sure you don't have any old copy of the 4.xx SFO in your DB, as it will never work.



yes??

[Alvoca]

Are they able to crack any 4.+ PSN content like games,demos, updates...etc
If they are this is a big step for the scene. I'm looking forward to hear more from them.

[JonahUK]

No amount of SFO or DB editing will make games work if they are signed for higher FW.

This is useful ONLY if you get an incorrectly made fix where the releaser has forgot to edit the PARAM.SFO.

This method has been known since the 3.41 days and it was how Black Ops was fixed to work on 3.41 by MRDOCA (the original way before the fix packs were released, a debug pkg was used).