NEED HELP HEX strings in updates

[pinky]

hmm...not sure. gengp4 seems to ignore what the PARAM.SFO says, at least I think. it has a generic base for every game. to create an update, you need the game pkg. if it doesn't find the correct A0100-V0100 , it will error saying that the file can't be found. oh, this is with orbis, which uses the content id of the gengp4. dumping both game and app together as one seems to replace the game files with the updates when needed. I'm not sure where it gets the app and master version from in this case.

 

[sandungas]

Thats why I noted that there were already two patches the first one got nuked as there was a master version of the game with that patch already included.

I now can confirm this as I went online to update the original psn game and it told me it needed v1.02. That actually is my 1.01 version update for my master version 1.01.

For detailed release info i use to search in gamefaqs, they have a good database
https://gamefaqs.gamespot.com/ps3/991066-lara-croft-and-the-guardian-of-light/data

I was trying to see if the game was released first as bluray, or to see if there was some difference in the release dates that could justify why the main game is 1.01 but i dont find any explain for it

Sometimes it happens, i guess is because the first version was sent to sony for approval, then they stepped back and repeated it, and after that was published. In other words, the first version with APP_VER 1.00 never was public
This is the only explain i can imagine

So in this case this means the last patch the A0101V0101 is in fact update 4 right Sandungas?

Is hard to know, i cant tell

 

[Mjfdms]

For detailed release info i use to search in gamefaqs, they have a good database
https://gamefaqs.gamespot.com/ps3/991066-lara-croft-and-the-guardian-of-light/data

I was trying to see if the game was released first as bluray, or to see if there was some difference in the release dates that could justify why the main game is 1.01 but i dont find any explain for it

Sometimes it happens, i guess is because the first version was sent to sony for approval, then they stepped back and repeated it, and after that was published. In other words, the first version with APP_VER 1.00 never was public
This is the only explain i can imagine

Is hard to know, i cant tell

I think I know what happened to that game in particular... first realese was for Xbox 360 in August then came ps3 release. I think the Xbox realese is thr main game version 1.00 and the other that came out a month or so later is in fact the republished game from Xbox to ps3 with already an update inside making it v1.01 master.


Equation:
A0100-V0100=APP 1.00, Main 1.00
A0101-V0100=APP 1.01, Main 1.00
A0100-V0101=APP 1.01, Main 1.01
A0101-V0101=APP 1.02, Main 1.01=
APP 1.01, Main 1.00

 

[Mjfdms]

that's interesting, 'cause I have shovel knight on the ps4 that says A0100V0102 with a patch A0101V0101 . orbis or gengp4, one of them, seems to merge both of them if you do this as a whole dump (both game and update). I'm not entirely sure how that works, but this seems to be the case when it comes to updates expecting A0100V0100.

I dont think thats the right update. It should be at least named A0101-V0102

Editig i was wrong lets see again the last part of my equation:

A0101-V0101=APP 1.02, Main 1.01=
APP 1.01, Main 1.00

So

A0100-V0102=APP1.02, Main 1.02=
APP 1.01, Main 1.01

Therefore the update you ve got is rhe right one A0101-V0101

 

[pinky]

I dont think thats the right update. It should be at least named A0101-V0102

that's something that doesn't make sense. I've never bothered to check what a dumped (game+patch) param.sfo looks like. doing both together isn't recommended either. I've never personally tried one of those pkgs. I just backed up what games I had. the patch won't go through since it assumes all games are A0100V0100, so you either have to dump both together or rename the pkg.. I'm not sure if this has any bearing on the pkg, since you can freely rename a pkg, but when it comes to the update itself, I'm not sure. I have a third version that's repacked with duxa's repacker. it doesn't throw up any errors. however, you still need the game and the patch with the game pkg renamed.

 

[pinky]

oh, I just had a thought, at least pertaining to games and patches that are separate. the system seems to use the PARAM.SFO when creating a game pkg, but then it uses that same game pkg to create an update (just like orbis, and possibly the way sony does it to prevent confusion). what if it has these weird app/master versions due to changing the original pkg name? though, you can rename the pkg anything you want, I believe, but the gengp4 will still be connected to the original game pkg name with its assumed A0100-V0100. . I'm not sure about pkgs together. this is just a theory.

 

[Mjfdms]

I see now that updates i get from psn directly are instaled to a diferent directory inside the ps3 that way the original param.sfo its not changed and maintains the master version intact only the app version is changed inside the created directory.

 

[pinky]

app version (possibly master version as well) is located in the metadata indexer as installed by the PARAM.SFO. I know the app version is in there as I've seen it, but I'm not sure about the master version. iirc, the file in question is named metadata_db_hdd with no extension. it's located in the mms/db folder on the root of dev_hdd0.