Its finaly working but i am getting some weird symbols in the menus and stuff. Any idea?
Yes, when I right clicked the folder, I got the bruteforce command in my folder menu in windows. When I ran it, it scans the entire directory for all available self/sprx files. Once it finds one or all of them, it starts doing it's magic. It only found one sprx. And that's the one that got fixed by the tool.
I really like when bruteforce finds one self or sprx, since then it creates the param.sfo, eboot.bin, and sprx files automatically. Param.sfo for 3.40 fw and etc. But when it doesn't find a sprx/elf, it doesn't do anything, just tells me it didn't find anything. So then I have right click on the eboot.bin and choose Resign Eboot (3.56+) in the file menu of windows.
What I do find puzzling is that scetool commands makes the eboots quite smaller in size compared to the original. But also smaller than other eboot fixes that I've come across. I wonder if scetool has a bug? Or other people are using another method, such as: TrueAncestor EBOOT Resigner
I've also noticed that scetool makes an eboot.bin file compatible to key revision: 0.92 - 2.36, while other eboots done by others, are focuses on either 3.40 or 3.55. I'd like to learn how they can target a certain FW? I think there are some game that may be more compatible with 3.55 than with 2.36 or lower. What do you think?
I'm going to ask aldostools to take a look at this thread. He might have all the answers? :)
I think it only checks the root not every subfolder. You might have something buried deep in the structure
@thumbkin - be more specific
Maybe, but the folder I started the bruteforce was BLES01296 and it found the sprx inside BLES01296/PS3_GAME/USRDIR/sprx/. So that was pretty deep. But I don't know if it can go any deeper. I did check all the folders to see if I could find any other files, but I could not spot any.
Originally Posted by BahumatLord
Working with which eboot fix? The original one on the first post of this thread, or the one I just recently did using Bahumatlord's .bat code?
Originally Posted by Thumbkin
And can you take a picture of the symbols you are seeing!???
Bahumatlord, can you check the code you gave me? I think I did a good job cleaning up the highlighted part (which adds bbcode to it). (see below).
if exist EBOOT.BIN goto fix
echo EBOOT.BIN not found...
FOR /F "tokens=1,2 delims= " %%A IN ('scetool.exe -i EBOOT.BIN') DO (
if [%%A]==[ContentID] set CID=%%B
scetool.exe --decrypt EBOOT.BIN EBOOT.elf
if not exist EBOOT.elf unself.exe EBOOT.BIN EBOOT.elf
FixELF.exe EBOOT.elf "24 13 BC C5 F6 00 33 00 00 00 36" "24 13 BC C5 F6 00 33 00 00 00 34"
ren EBOOT.BIN EBOOT.BIN_ORIGINAL > NUL
if [%CID%]== (
scetool.exe -v --sce-type=SELF --compress-data=TRUE --skip-sections=TRUE --key-revision=01 --self-auth-id=1010000001000003 --self-app-version=0001000000000000 --self-vendor-id=01000002 --self-type=APP --self-fw-version=0003004000000000 --encrypt EBOOT.elf EBOOT.BIN
) else (
scetool.exe -v --sce-type=SELF --compress-data=TRUE --skip-sections=TRUE --key-revision=01 --self-auth-id=1010000001000003 --self-app-version=0001000000000000 --self-add-shdrs=TRUE --self-vendor-id=01000002 --self-type=NPDRM --self-fw-version=0003004000000000 --np-license-type=FREE --np-content-id=%CID% --np-app-type=EXEC --np-real-fname=EBOOT.BIN --encrypt EBOOT.elf EBOOT.BIN
del /Q EBOOT.elf > NUL
if not exist EBOOT.BIN ren EBOOT.BIN_ORIGINAL EBOOT.BIN
Disregard my post about the irredable text.
It was caused by the fact that the first time I ran the game only throphies got installed and it didnt install any game data.
The second time i launched the game it did start the game installer data. When it completed the game started and all text was normaly readible.
Thx alot ALL for this fix!
at JayJay: I used your fix posted on the previous page posted as attachment
Be sure to thank Bahumatlord. He was the hero in this campaign! :)
Originally Posted by Thumbkin
I also updated the first post of this topic, to let people know that if they get an error, there is another eboot to try. :)
--key-revision=01 -> uses keys for fw 0.92 - 2.36 and higher (all versions)
Originally Posted by Jay-Jay
--key-revision=04 -> uses keys for fw 3.40 - 3.41 and higher (from 3.40 and higher)
--key-revision=07 -> uses keys for fw 3.50 and higher
--key-revision=0A -> uses keys for fw 3.55 and higher
BTW BruteForce is intended to do that :) to resign files I think it is better to use the Resign (3.56+) from PKG ContentID.
I recommend to use one of the latest versions, like "ps3tools 2.0.43"
it now includes a new file "scetool_parameters.txt" where you can customize the parameteres used by the tool.
it includes the latest bruteforce
Now, regaring the "question"... the thread is 3 page long... could you make a summary in 2 lines?
The smaller size of the EBOOT is due the --compress-data=TRUE parameter.
Thanks aldostools for the reply in this topic. I really appreciate it. I think you gave me a lot to go on now with this reply.
I apologize for that. My issue is that I don't really understand a whole lot about this, so this is why my questions are not yet organized. I think once I get a better understanding about how to use these tools properly, my questions will improve. Can I get a rain check for now? But do you know if there are guides or tutorials to get the most out of the scetool? And also a guide for the "right click" on a file menu options in windows? (see screenshot below):
I don't know of any tutorial for scetool. For basic info use: scetool.exe --help
Originally Posted by Jay-Jay
Most of the commands were learned/implemented on my tools via my own trials/errors and with the help/feedback from users like Asure, deank, andreus, PatrickBatman, catalinnc, Omnomnom, MAGiC333X, BLKDTH, JLM, opoisso893, Matsumot0 on the ps3crunch forums.
The PKG_ContentID generates some batch files in the folder: ps3tool/scetool
you can check them to learn more how the scetool is used.