[sandungas]

By now the only (dirty) trick that works is to create a savegame in the "destiny" ps3 and keept both files .SFO & .PFD
The rest of files of the savegame folder can be replaced (by overwriting them)

*This .SFO contains the "destiny" ACCOUNT_ID and doesnt need to be edited
*This .PFD contains the hash of the .SFO ...so is validating it

This trick works fine for internall HDD savegames (usually, but not allways for severall reasons as...)
------------------------------------------------------

The problem is when the .PFD contains a long list hashes of other files of the folder
This depends of the developers of the game, there are savegames where the .PFD contains hashes of other important files (i.e. PARAM.SFO, SAVE1.DAT, SAVE2.DAT, PROFILE.WTF, etc...)

In this games there is no solution, because what you are trying to replace is PROFILE.WFT and the rest, and you cant use none "origin" nor the "destiny" .PFD (you are using a mix of files from both, so the hashes lists inside both .PFD's are not corect)

The only way is to rebuild (or patch) one .PFD with the new hashes of the files you are replacing, but this is not possible (yet)
--------------------------------------------------------

I suggested to doing it by patching (brutally) the .PFD by copy-pasting the hashes next to the text "PARAM.SFO --this--> 1489361784617624786"
1.- You need a .SFO created in the "destiny" ps3 (and his hash copied from his .PFD)
2.- Overwrite this .SFO in the downloaded savegame folder
3.- Brutal-patch his hash by editing the downloaded .PFD


This way you are only replacing 1 file, and you need to edit other 1 file (mandatory to validate the replaced one)
Its a bit simpler, rude, and noob, and a guy said in this thread that if you try to edit the .PFD it gets corrupted itself, so probably doesnt works
But if the method works it will have more "compatibility" with rare savegames, and i think is a better approach to understand the real problem, that are this hashes inside the .PFD