[no0byme]

I was curious if I could run the game with a modded or resigned game update.
So, I've decrypted the latest game update (eboot).
And then encrypted/resigned it by using the latest scetool tool.

Here's what I did:
scetool.exe --sce-type=SELF --compress-data=FALSE --skip-sections=TRUE --key-revision=01 --self-auth-id=1010000001000003 --self-vendor-id=01000002 --self-type=NPDRM --self-app-version=0001000000000000 --self-fw-version=0002005000000000 --np-license-type=FREE --np-content-id=*I --np-app-type=EXEC --np-real-fname=EBOOT.BIN --encrypt EBOOT.ELF EBOOT.BIN

Scetool signed/encrypted it without any problem. I replaced it with the orginal game update eboot and ran the game, but got a 80010017 error.

The game and its updates are very old (FW 2.50). I installed the game patches and they load just fine on 4.30 Rogero, but they fail to load when I decrypt/reencrypt and replaced the game update.

I've noticed that the filesize between original game update and encrypted game update is a bit different.
Original: 15,377kb
Resigned/Encrypted: 15,355kb

Any help will be appreciated, thanks!

[baargle]

I'm confused, why are you decrypting/encrypting with different keys if the game/updates is from so long ago.

It should work as it is with no decrypting/encrypting.

If it's just an experiment, then there's no reason why it won't work if done correctly.

Have you patched param.sfo correctly?
The difference in file size you describe is quite normal. It's only when it's a sizeable change in size that you should wonder if somethings wrong on that front.

[no0byme]

But say if I want to mod the game update, I'd need to decrypt it first and then encrypt it back? That's what I did except that I didn't mod it (I was curious if it could work) but got the error when I load the game. Ahh... different keys? If this is 2.50, what keys do I use? I couldn't find 2.50 keys.

I didn't do anything to param.sfo or something else, just the EBOOT itself.

I don't know what I'm doing wrong.