[longhornx]

Originally Posted by nattes ebootfix.bat xxxxxx-xxxxxxxxx_xx-xxxxxxxxxxxxxxxx example EP0006-BLES01298_00-NFSPATCH00000001

if you use the one of a previous post mine, you only need to drag an eboot.bin to it (no need to add the content id)

[Asure]

Originally Posted by concretecork I am having trouble with creating Rage BLUS eboot. I am guessing the link in your tutorial was for scetool, and since the link for the new one is still not working i found v0.2.7. The rage update package is called "UP1003-BLUS30485_00-RAGEDAYONEPATCH1-A0101-V0100-PE_fw3.60" i cut the eboot and pasted in the scetool folder and opened command window and type "ebootfix UP1003-BLUS30485_00-RAGEDAYONEPATCH1" and hit enter and i get error "ebootfix is not recognized as a command" Can somebody please explain what i am doing wrong? Thanks

Rage not only has 'EBOOT.BIN' but also 'patch.self' binaries in the update.
At the moment, the trick to unpack SELF files like patch.self is unknown.
Same applies to SPRX files like the ones used on the portal patch.

Currently the bat file can only work on updates that have only EBOOT.BIN as binaries. This excludes rage, portal 2 , MW3 and so on. I've been looking how to unpack these new SPRX files since day one 3.60 keys leaked.. but nobody is sharing the info.

[MHMProSoft]

i got this *warning in this line :
???

[Asure]

Go back to scetool 0.2.7, i've skipped 0.2.8 because it gives a lot of these errors..

[nattes]

*************** ELF builder - V1.2 - Heden/DeLiGhT'11 ***************

Usage: ELF_builder [-debug | -dump]

ie.#1: graf_chokolo's dump to ELF
ELF_builder -dump <in: SELF> <in: DUMP.0> <in: DUMP.1> <out: ELF>

ie.#2: debug SELF to ELF
ELF_builder -debug <in: SELF> <out: ELF>
************* [ - Post Merged - ] *************
makeself eboot.elf
ELF header size @ 40
8 program headers @ 40
35 section headers @ 1897eb8
processing segment 0 with rlen 17a5768 len 17a5768 offset 0...encrypted...
processing segment 1 with rlen e4c74 len e4c74 offset 17b0000...encrypted...
processing segment 2 with rlen 0 len 0 offset 1894c74...encrypted...
processing segment 3 with rlen 0 len 0 offset 1894c74...encrypted...
processing segment 4 with rlen 0 len 0 offset 1894c74...encrypted...
processing segment 5 with rlen 24c len 24c offset 1843178...
processing segment 6 with rlen 28 len 28 offset 17a5700...
processing segment 7 with rlen 40 len 40 offset 17a5728...
segments enumerated
built crypt data
file built
self written in memory
0 [main] make_self 10600 exception::handle: Exception: STATUS_ACCESS_VIOLA
TION
946 [main] make_self 10600 open_stackdumpfile: Dumping stack trace to make_s
elf.exe.stackdump
************* [ - Post Merged - ] *************
selfrebuilder --eboot.elf
SELF Rebuilder by Anonymous developers on EFNET
SELF and SPRX packer and signer
Based on the fail0verflow Tools
! use with caution !

Usage: self_rebuilder <input.elf> <output.self> <original.self>
input.elf: The input ELF to sign
output.self: The output SELF/SPRX to generate
original.self: The reference original SELF/SPRX

[haxxxen]

btw, you can even fix sprx with ebootmod. i have tried it myself for stranglehold where i had to mod a sprx file. but i prefer magicpkg with drag and drop

[a$h x]

Any ideas what's gone wrong here:



I think the patch maybe encrypted with 3.60+ keys any easy way to find out?

[longhornx]

Originally Posted by a$h x Any ideas what's gone wrong here: I think the patch maybe encrypted with 3.60+ keys any easy way to find out?

your eboot could be a TB eboot, corrupted, etc...

you can see with which keys are a self encrypted using scetool -i EBOOT.BIN

here's a example (FW version/keys in red):

scetool 0.2.8 <public build> (C) 2011-2012 by naehrwert NP local license handling (C) 2012 by flatz [*] SCE Header: Magic 0x53434500 [OK] Version 0x00000002 Key Revision [0.92 - 3.30] Header Type [SELF]

[Asure]

Originally Posted by haxxxen btw, you can even fix sprx with ebootmod. i have tried it myself for stranglehold where i had to mod a sprx file. but i prefer magicpkg with drag and drop

The newer 3.60 SELF/SPRX files do not decrypt for me with scetool (or even with ebootmod which uses unself). If there's some command line magic involved, why not share it with us?

Take RAGE (BLES01426) for example. It's got a SELF inside.

[*] Warning: Could not decrypt header.[*] SCE Header:
 Magic           0x53434500 [OK]
 Version         0x00000002
 Key Revision    [3.60 - 3.61]
 Header Type     [SELF]

but, funny thing is, HOTY or Exe.trim.all released a decrypted & patched version, which also does not decrypt with scetool, but is for 3.4x:

[*] Warning: Could not decrypt header.[*] SCE Header:
 Magic           0x53434500 [OK]
 Version         0x00000002
 Key Revision    [0.92 - 3.30]
 Header Type     [SELF]

So well.. we know it's possible, but we don't know how to do it.

[pSydeFX]

@a$h x that update is 3.70 signed. it wont work