[haxxxen]

wuzzaa. thanks for mentioning on your page. though hexxxen i wanted to choose first on here as username, as i love playing with hexeditors, but haxxxen was chosen because of this site

[aldostools]

sorry it was typo... it now says @haxxxen

[haxxxen]

ok, thanks. but it would have been no problem to me the other way

[SkillerCMP]

Originally Posted by aldostools I have addressed these bugs in build 2.6.0. The program also identifies the Master Codes and show the TITLEID in the code. Code types currently unsupported for EBOOT patching are: 0000 <- master code type 3X00 (pointer codes) C0nn (conditional/joker codes) 10000 (are currently supported as 2000 but disabled by default) <- I still wonder what are these code types (????)

can u show me some 10000 codes I think this is a typo .. EDIT <--- should have kept reading :P I see u noticed its a typo :P
also Aldo are u using SCEtools to decrypt/Encrypt the eboot .. u could set that to return back the data area ..

or u can use offset 0x1C (EBOOT.BIN) that tells u the Decrypted size of the elf

[aldostools]

Originally Posted by SkillerCMP can u show me some 10000 codes I think this is a typo .. EDIT <--- should have kept reading :P I see u noticed its a typo :P also Aldo are u using SCEtools to decrypt/Encrypt the eboot .. u could set that to return back the data area .. or u can use offset 0x1C (EBOOT.BIN) that tells u the Decrypted size of the elf

yes, I'm using SCETools... do you mean use scetool -i to get the size Data Length ?

Yes I could do it or read the offset at 0x1C... the real problem is that the editor loads the list of games on startup and the eboot (bin or elf) is not necessarily available when a game is selected, so it is not always possible to calculate the elf size to display a proper red/blue icon. So I assume that any address (after substract 0x100000) if it's larger than 0x260000 (38 MB), it is a memory address and show the red icon.

However, the routine that patches the ELF validates the offsets based on the real size of the ELF file. So I don't need to check the EBOOT.BIN headers or use scetool to the ELF size, because the ELF is required and it's easy to get the size from the file.

[SkillerCMP]

Originally Posted by aldostools yes, I'm using SCETools... do you mean use scetool -i to get the size Data Length ? Yes I could do it or read the offset at 0x1C... the real problem is that the editor loads the list of games on startup and the eboot (bin or elf) is not necessarily available when a game is selected, so it is not always possible to calculate the elf size to display a proper red/blue icon. So I assume that any address (after substract 0x100000) if it's larger than 0x260000 (38 MB), it is a memory address and show the red icon. However, the routine that patches the ELF validates the offsets based on the real size of the ELF file. So I don't need to check the EBOOT.BIN headers or use scetool to the ELF size, because the ELF is required and it's easy to get the size from the file.

True true
:P just good to see this is still moving forword

[aldostools]

It is important to receive feedback about bugs from the users. I cannot test all the features on each revision, and sometimes things get broken when new features are implemented.

@butnut has pointed me another important bug in the patch ELF module, that didn't decrypt the EBOOT.BIN and about ELFs were not getting the patches applied.

Here is the fixed build 2.6.2. Pleeeeeese, test and report back the issues.
http://ps3tools.aldostools.org/PS3_C..._installer.rar

FYI @gingerbread

[gingerbread]

@aldostools Thanks for the update.

Will it be possible to add a tick mark left side of the "Set Game Status" and "Set Cheat Status" menu. Users will know what status that they are in.

Thanks!

[aldostools]

Originally Posted by gingerbread @aldostools Thanks for the update. Will it be possible to add a tick mark left side of the "Set Game Status" and "Set Cheat Status" menu. Users will know what status that they are in. Thanks!

The build "2.6.2" that is currently online has these changes implemented.
It also includes the database version 0.96 (Feb 13, 2013).

[butnut]

Originally Posted by aldostools It is important to receive feedback about bugs from the users. I cannot test all the features on each revision, and sometimes things get broken when new features are implemented. @butnut has pointed me another important bug in the patch ELF module, that didn't decrypt the EBOOT.BIN and about ELFs were not getting the patches applied. Here is the fixed build 2.6.2. Pleeeeeese, test and report back the issues. http://ps3tools.aldostools.org/PS3_C..._installer.rar FYI @gingerbread

2.6.2 eboot patching is working great!

One thing I noticed is pressing ctrl+E then selecting an eboot/elf and after selecting cheats then pressing ctrl+p, well that part works but when I press ctrl+J nothing happens. So I click on patch elf then make self and it creates the patched eboot.

If I then restart the program and this time go straight to the patch elf button and select open elf then apply patch to elf, well at this point if I press ctrl+J then the new window pops up.

It's not really a big deal and other than that the program is working 100%.