Is there a tool to separate a merged pkg?

[kilwa]

If a dump contains the base/update merged into one file, is there a tool that can separate that back to the original two files (base and update)?

 

[godreborn]

If a dump contains the base/update merged into one file, is there a tool that can separate that back to the original two files (base and update)?

no, it's impossible once they're combined.

 

[KiiWii]

No.

It’s a one way operation, as it overwrites old files (base) with new (update), to form one pkg.

You may be able to extract the update, but never the base afaik.

 

[godreborn]

heard from alazif that she's thinking about how to separate base and update from remastered games, since they're merged no matter what, but it's low priority iirc.

 

[kilwa]

No.

It’s a one way operation, as it overwrites old files (base) with new (update), to form one pkg.

You may be able to extract the update, but never the base afaik.

This is the reason for the post tbh. I'd like to extract the update, if possible.
Or is there a method to 100% check if an update is indeed merged with the base?

 

[godreborn]

This is the reason for the post tbh. I'd like to extract the update, if possible.
Or is there a method to 100% check if an update is indeed merged with the base?

Possibly, but not always, the master version will be higher.

 

[kilwa]

Honestly surprised there's not a method or tool, etc to determine if an update is 100% merged.

I'm assuming simply installing the dump wouldn't help 100% of the time either. I've seen base games with an update merged (I think) that show nothing on update history or the info screen. But at the same time, most seem to show at least the update history to determine that update being there.

 

[godreborn]

Honestly surprised there's not a method or tool, etc to determine if an update is 100% merged.

I'm assuming simply installing the dump wouldn't help 100% of the time either. I've seen base games with an update merged (I think) that show nothing on update history or the info screen. But at the same time, most seem to show at least the update history to determine that update being there.

Check the param.sfo. the master version will be higher than 1.00.

 

[kilwa]

Check the param.sfo. the master version will be higher than 1.00.

Interesting! Is there a preferred tool or program for this?

 

[godreborn]

Interesting! Is there a preferred tool or program for this?

You can do it with orbis sfo app from fake pkg tools.

 

[kilwa]

You can do it with orbis sfo app from fake pkg tools.

Now that's the part that confuses me. That's what I *was* looking at to determine whether or not an update was merged.

But there's some games that display a master version number higher than v1.00. Then Orbis Patches claims there's no update for the game or Orbis Patches claims that the latest update is lower than what's being displayed as the master version.

It's super, super confusing.

 

[godreborn]

Now that's the part that confuses me. That's what I *was* looking at to determine whether or not an update was merged.

But there's some games that display a master version number higher than v1.00. Then Orbis Patches claims there's no update for the game or Orbis Patches claims that the latest update is lower than what's being displayed as the master version.

It's super, super confusing.

That's the problem. Some psn games have updates as part of the base game. There's no way to tell 100%.

 

[kilwa]

That's the problem. Some psn games have updates as part of the base game. There's no way to tell 100%.

Ahhh, okay. So, perhaps, Orbis Patches isn't entirely accurate to some extent?

 

[godreborn]

Ahhh, okay. So, perhaps, Orbis Patches isn't entirely accurate to some extent?

It's up to Sony how it's done

 

[Hayato213]

Now that's the part that confuses me. That's what I *was* looking at to determine whether or not an update was merged.

But there's some games that display a master version number higher than v1.00. Then Orbis Patches claims there's no update for the game or Orbis Patches claims that the latest update is lower than what's being displayed as the master version.

It's super, super confusing.

EP9000-CUSA08809_00-SOTC0000000000EU-A0100-V0100.pkg

EP9000 Meaning Europe Region and 9000 is for PSN I think, US/Canada has UP instead of EP, not really sure for different # after EP/UP, maybe for different video games development company such as Square Enix, Santa Monica Studio that released the game via physical version.

CUSA08809_00 is the Title ID

SOTC0000000000EU is the 16 Characters for the Game Title, usually initial of each word in the game title, SOTC for Shadow Of The Colossus, usually filled with 0 after coming up with name for games, such as HORIZONCE0000000 and FARCRY5GAME00000.

A0100 meaning application version 1.00, game dumped without updated merged would be A0100.

V0100 meaning update files version 1.00, so no update. For game that has update combined , it would be something like EP9000-CUSA08809_00-SOTC0000000000EU-A0100-V0106.pkg for update version 1.06

For an update that wasn't merged together with the game, it would have naming convention of EP9000-CUSA08809_00-SOTC0000000000EU-A0106-V0100.pkg 1.06 would be the application version.

Hopefully this help.