A Q for the more knowledeable members

Hi Guys,

I've been reading about the issues with updating games etc.

Obviously, the eboot contained in the update is not being patched or decrypted by the current managers (as it is not accessed by them) whereas the original eboot is patched somehow when doing a backup.

So, what exactly is getting changed on the eboot when performing a backup?
Is it patching the eboot (changing a byte or address etc)?
How exactly does it decrypt a retail eboot to be usable by the BM?

I know it is not changing the media flag used (DG/HG etc) because all the eboots I've looked at still retain the original flag of DG

If we know what gets changed to make this a valid eboot (bootable by BM) then couldn't we patch the update eboot to become a valid eboot (again bootable by BM) and repackage the pkg to install the update?

Just an idea, waiting for the more knowledgeable of you to explain if this is feasible or whether I should get my coat and leave!

Cheers,
Jonah.

Quote:

---

Originally Posted by JonahUK

Is it patching the eboot (changing a byte or address etc)?
How exactly does it decrypt a retail eboot to be usable by the BM?

---

It doesn't.

From what I read and understood, the Backup Manager doesn't decrypt any file. It just mounts the game to the right path in order to make it run. Think of Backup Manager as Daemon Tools when mounting an ISO... Except that BM can't load isos.. :P

Ok, so the eboot isn't being patched or changed. Good. That means I don't have to do any editing or patching etc.

TBH, I haven't actually tested any updates to my games, I am going off what has been said previously.

I'll do some testing with updates.

Cheers.

Quote:

---

Originally Posted by JonahUK

Ok, so the eboot isn't being patched or changed. Good. That means I don't have to do any editing or patching etc.

TBH, I haven't actually tested any updates to my games, I am going off what has been said previously.

I'll do some testing with updates.

Cheers.

---

Well, people have yet to figure out how does the updates work, as there are some games that update, and some that doesn't.

Good luck with your tests. I'll start with mine as soon as my board gets here, as I don't feel like soldering stuff to use my Arduino. :yawn:

What I'm thinking here is that when the new update is applied, the original disc checks the system, sees an update and runs that instead (obviously).

So (again in theory) the updated eboot will probably be looking for where the game SHOULD be instead of where the game actually is (dependant on BM used but default is dev_hdd0/game/LAUN12345/GAMEZ/ID/PS3_GAME/USRDIR etc.

If that's the case, then we could simply patch the eboot to look for the actual path. But this is where I would stumble as I don't know if I can patch a retail eboot....... I don't have the SDK so I don't know.

I have some updates currently d/ling so will test as soon as I can.

Cheers.