What locks and protection will Sony do in PS5? Trophies and Game saves tied to Biometrics of console owner/user?
A DNA sample (peripheral not included in the bundle)
The PARAM.PFD is like the "police officer" of the folder, it contains a list of hashes of the other files in the folder
Is like an anti-tampering protection, if you modify the other files the PARAM.PFD detects it and the whole folder becomes invalid
The list of the files supervised by PARAM.PFD is optional... you could have a savegame composed by 20 files but only 5 of them are protected by the PARAM.PFD
But the PARAM.SFO is always protected by the PARAM.PFD
To transfer savegames and trophies we need to change the user id's in the PARAM.SFO and this is when we are hitting with PARAM.PFD
The "pfdtool" made by flatz have an option that simply does an "update" of the PARAM.PFD. The way how is intended to be used is in this order
1) modify the other files as much you want
2) update the PARAM.PFD
3) profit
Is as simple as that, to decrypt/encrypt the PARAM.PFD is needed the EID root key of the PS3
The bruteforce savedata tool does this internally (and more things)
For the trophies is the same principle, you need to change the user identifyers of the PARAM.SFO... then do an "update" of the PARAM.PFD
-------------
And btw, the golden rule to remember when is needed to rebuild the database is...
If you are adding some file using non-official functions + and that file needs to be displayed in XMB = then is needed to rebuild the database
But if you use official functions, then is not needed to rebuild database, as example, the savegames can be exported/imported from USB by using the official functions, this "indexes" them well in the database
There are some exceptions to this rule though, is better to avoid them but could be handy sometimes, as example, if you have X content already indexed in the database you can replace his files by non-official functions... and then when you try to boot/load it in XMB is going to display an error because there is a mistmatch in between the database info about that content and the real files
But inmediatly after that error (no need to rebuild database) the conntent is fixed, the XMB displays it fine and everything fine with it
This happens because the dabatase have been updated at the same time that appeared the error on screen
So.. you are forcing a single entry in the database to be updated

Yeah, in a dirty way, it works, but should be avoided just incase the database cummulated some garbage caused by the error