[Wouldy]

Hi flatz, thanks alot for the cool program. I was wondering if you could help me with this issue that I'm having, this is from an original unmodified save file from my console. Shouldn't all the hashes be ok.

I have attached a log of the problem, since the code wrap on this forum is messy and buggy.

[sakibsultan_308]

I presume gamegenie and xploder is useless now. Am i correct?

[SkillerCMP]

Originally Posted by sakibsultan_308 I presume gamegenie and xploder is useless now. Am i correct?

The game genie will never be useless do to the true amount of work need to add codes to alot of the saves believe me been hacking saves/games for sometime and a commercial device gets way more support then devices like this since one not alot of the ppl that will us this or try to use it will fully understand what it takes. And the user aspect of it is not geared to ofw were GG is.. U have to remember GG takes out all the extra layers not just the Sony layer. So that the end user can do simple things as well. With out trying to jump threw hopes... this tool is very hacker orientated out side of the resigning process. So good for dev/game hackers bad for an end user.. believe me I'm not downing the program and don't think flatz will take it that way.. but in the end end users want everything just simple and already done

[flatz]

Originally Posted by rayan2 but will the trophies work ??

No, it will not work with the current public version. I will release a new version soon but without trophy keys. See my posts about it because I already explained why I think so.

Originally Posted by Wouldy Shouldn't all the hashes be ok. I have attached a log of the problem, since the code wrap on this forum is messy and buggy.

I think it is an issue with 4 version. Can you check the byte at offset 0x0F at PARAM.PFD? If it is 4 then it seems that they have different keys or maybe algorithm for this version. I will try to investigate it soon.

Originally Posted by aldostools Well I use a slightly different method in my work in progress of the GUI

Wow Your tool is great.

Originally Posted by aldostools I still don't get the "update" PFD to work properly... maybe master @flatz could give a hand

What are your problem, aldostools? I can help you.

Let me say a few words about the process of signing. There are two types of files - system file object (PARAM.SFO) and game files (which are encrypted by the secure file ID). The first one contains 3 or 4 hashes (depending on whether it is a trophy file database or not). So for game saves they are a static key embedded in the prx module, your unique console ID, disc hash key and authentication ID (it is static too). So if you take a foreign save game you probably don't have its console ID and the disc hash key (you can only take a disc hash key if you have an original game disc for it). Also if you don't have a secure file ID and you are lazy to get it (by bruteforcing it/reversing the game executable/dumping from the memory) then you can't calculate hashes for game files too. That's why I created two different modes of signing/checking - one for these people who want only to resign a foreign save game and nothing more and the second one is for people who have all data to update all hashes for their save game. The first mode called partial update/check (see the corresponding option at pfdtool), and for full update you don't need to specify this option. The partial update only updates hashes which are easy to calculate (based on static data such as authentication ID and console ID). So if you have a filled global.conf (all keys and your console ID) and run a partial update on the foreign save game to resign it for your console then you got a fully working resigned save game. But if you want to modify save game files which are encrypted then you need to get all data and specify them in configuration files and then use a full update to resign it. By the way the PS3 itself doesn't check some hashes such as a hash which was calculated using a disc hash key. So you can omit some of them (I only omitted the hash which I said and it works fine). But I don't know what situation will be in the future, maybe S0ny will add a check for them.

[z-paul]

Where or how can I find console_id?

schould I use "IDPS Viewer"?

[aldostools]

Originally Posted by flatz What are your problem, aldostools? I can help you.

Ok I think I managed to get it working after your kind description THANKS!
(I added it to the readme )

I updated the tool, so now the buttons are in a more logical order:
patch sfo -> decrypt pfd -> update pfd (full or partial) -> encrypt pfd -> verify

Here is the link to the version 1.1.3:
http://aldostools.org/temp/BruteforceSaveData.rar

Originally Posted by z-paul Where or how can I find console_id?

Try using multiMAN's system information.
The console_id is 16 bytes long (32 hex digits)
and it looks like: 000000010085000X1001XXXXXXXXXXXX
(if you have a US/CA console, you will see a 000000010084000)

[Wouldy]

Originally Posted by flatz I think it is an issue with 4 version. Can you check the byte at offset 0x0F at PARAM.PFD? If it is 4 then it seems that they have different keys or maybe algorithm for this version. I will try to investigate it soon.

Yeah the PFD is version 4 at offset 0x0F, so maybe need to find new syscon key in newer firmwares.

[diesel701]

Originally Posted by aldostools I updated the tool, so now the buttons are in a more logical order: patch sfo -> decrypt pfd -> update pfd (full or partial) -> encrypt pfd -> verify

Aldo, how can I decrypt other files in savegame folder with your tool? Not only the pfd file..

[gingerbread]

@aldostools Amazing work!!

[aldostools]

Originally Posted by diesel701 Aldo, how can I decrypt other files in savegame folder with your tool? Not only the pfd file..

Are the other files encrypted too???? Currently the file list includes only the ones found in the pfd