[hellsing9]

Added links to ps3devwiki. About .SFO even if the method is far fetched, old, lunatic.
It's better to anyone who has any type of curiosity to go and check the wiki to get more info.

P.s: my typos are getting worse..sorry xD

[sandungas]

Originally Posted by 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..

100% true... when the content is installed, a copy of the PARAM.SFO is stored in a "XMB database"... this database is updated when you install a patch for this game, when you boot the game, or when you "rebuild the database" (from recovery menu)

Originally Posted by 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??

Hmmm, never thought in it, but also true in some cases (there are different variations of the problem)

[CrashSerious]

Originally Posted by TizzyT Huh??? I don't get it... I think I'm missing something as well. To me this doesn't sound right, or maybe I miss-read it or misunderstood it.

It doesn't sound right, because it's not.

[baargle]

News is Ridiculous.

[YlodedKing]

<Anon> Something to mention is that those pkgs when downloaded from $0ny either need modification of the PARAM.SFO inside, or the HD db needs to be rebuilt once the PARAM.SFO is updated. <Anon> not much can be done about that without releasing the full pkgs <Anon> which is not for me to do. <Anon> there are tools for that already <Hellsing9> hdd encryption? <Anon> nah any tool that allows modifying a pkg, just need to replace the PARAM.SFO inside the pkg <Anon> or use spoofing. <Anon> when the pkg is installed the PARAM.SFO is used to create the db entry for the title <Anon> so if you install the sony pkg with the normal PARAM.SFO it will insist you need 4.xx firmware to run the title <Anon> modifying the PARAM.SFO after installation will not be reflected until the HD db is rebuilt from the service menu <Anon> spoofing gets around that. <Hellsing9> cool <Anon> they need to backup files <Anon> preferable that person has spoofing.

hellsing9 are those words from IRC ? I thought that IRC and forums don't mix hehehehheh just kidding
To me this article sounds more like a "normal ps3 troll article" you remember my TB theories hehehehhe
Anyway to the subject , it's funny that TB used a spoofing of their param.sfo
In their TB releases they used 50.00 or even 99.9 version in param.sfo .
It was an early knowledge that TB only masked it's releases so even if a person cracked it , it would not work because of the param.sfo masking and other things ...

[Ada Love Lace]

Originally Posted by baargle News is Ridiculous.

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)

[samdrlvt]

Ok, newbie question: even if the "method" is incorrectly explained, has 4.1+ PSN content (Max Payne update 1.05 and Walking Dead Demo) been patched to work on 3.4+ firmwares, or not?
If so, that is breaktrough progress, right?!

[DEFAULTDNB]

Yes a breakthrough has been made, it clearly works! but how it works seems to be the foggy part

[CaptainCPS-X]

Hiyas everyone! just wanted to contribute with my understanding of what is the Anon saying on that quote. It is basically what I have been doing with his patches releases as simple files.

When you "manually" install those "patched" files (EBOOT.BIN, PARAM.SFO) you will need to rebuild the PS3 Database via Recovery Menu for example, for the changes to take effect (I never had to rebuild DB because of what I will explain later).

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
- repack using AldosTools Shell Extension
- Install new PKG
- Play!...no need to rebuild PS3 database

That is what he is saying on that chat quote, we still need the patched files, he didn't say how he patched the EBOOT.BIN and PARAM.SFO. The system will not magically patch them just by replacing the PARAM.SFO.

PS: Sorry for my English I just woke up xD

SeeYa!

[JonahUK]

Originally Posted by YlodedKing hellsing9 are those words from IRC ? I thought that IRC and forums don't mix hehehehheh just kidding To me this article sounds more like a "normal ps3 troll article" you remember my TB theories hehehehhe Anyway to the subject , it's funny that TB used a spoofing of their param.sfo In their TB releases they used 50.00 or even 99.9 version in param.sfo . It was an early knowledge that TB only masked it's releases so even if a person cracked it , it would not work because of the param.sfo masking and other things ...

TB used spoofing in the SFO so the game wouldn't update. Nothing to do with "masking" or trying to hide anything. The param.sfo has no effect in relation to cracking their releases.