Scetool Header Error

Of course all the tools use scetool anyway.
It's just about the arguments used by the tools... That's why I suggested cutting the middle man out & using scetool directly...

Which reminds me...
Anybody knows the story behind oscetool?
I am curious, I got the source for it ages ago & I finally compiled it before the holidays intending to use it..
How different is it? Is it exactly the same thing?
@kozarovv? @pinky?

Sent with Tapatalk
 
Last edited:
If you really want to "learn", the best imo is to read the scetool Readme, the threads about it, psdevwiki page & most important use trial & error. There's no substitute for practicing! [emoji6]
Once you know the syntax, it's half the battle. The rest you will learn quickly by using the tool...

Sent with Tapatalk
 
bguerville said:
If you really want to "learn", the best imo is to read the scetool Readme, the threads about it, psdevwiki page & most important use trial & error. There's no substitute for practicing! [emoji6]

Sent with Tapatalk
Click to expand...
yeah i have but am not gettin it :/
 
There are plenty of examples if you look for them. Start with easy stuff, just decrypt a simple self to begin with.
A simple scetool -d <self-file> <elf-file> then try encrypting it...

Sent with Tapatalk
 
add
Code: 
-2 05
or
Code: 
-2 06
to your command line.

Btw. I'm not 100% sure this resolve it. I don't messed with npdrm too much. klicense edit can be needed.
 
if u use ps3tools eboot bruteforce tool to find the klicense in the eboot, it will automatically decrypt the elf. u could see if that works on ur end. speaking of which, I need the latest version of ps3tools if anyone has a link. ever since my computer crashed, I haven't gotten around to reinstalling that.
 
bguerville said:
There are plenty of examples if you look for them. Start with easy stuff, just decrypt a simple self to begin with.
A simple scetool -d <self-file> <elf-file> then try encrypting it...

Sent with Tapatalk
Click to expand...
yeah i know this already, ive used it alot
kozarovv said:
add
Code: 
-2 05
or
Code: 
-2 06
to your command line.

Btw. I'm not 100% sure this resolve it. I don't messed with npdrm too much. klicense edit can be needed.
Click to expand...
yeah i was tryin similar commands but with = added though. still not workin though. ill see what @aldostools says
 
I couldn't get scetool to extract the file either but somehow PS3tools could. So I looked though some of the PS3tools files and found this "scetool.exe -l B8498B3492E822F7D2390862568B03C7 -v -d "EBOOT.BIN" "EBOOT.elf" which is what worked.
 
bigjokker said:
I couldn't get scetool to extract the file either but somehow PS3tools could. So I looked though some of the PS3tools files and found this "scetool.exe -l B8498B3492E822F7D2390862568B03C7 -v -d "EBOOT.BIN" "EBOOT.elf" which is what worked.
Click to expand...
yep it works. what is that klicense i wonder?

anyways, thanks alot for the help
 
Last edited:
Checking logs obtained with tools & such allows to get clues at to cli usage.
That's what bigjokker did... [emoji6]

Sent with Tapatalk
 
psydefx said:
yep it works. what is that klicense i wonder?

anyways, thanks alot for the help
Click to expand...

u can find the klicense with ps3 tools eboot bruteforcing tool which is what I mentioned. however, the rap has to be able to decrypt the self into elf in order for it to work. r u sure the content id (rap name) was correct? u can find that in the PARAM.SFO .
 
pinky said:
u can find the klicense with ps3 tools eboot bruteforcing tool which is what I mentioned. however, the rap has to be able to decrypt the self into elf in order for it to work. r u sure the content id (rap name) was correct? u can find that in the PARAM.SFO .
Click to expand...
according to aldo, ps3tools uses dklic_validator
 
there's a portion of lv 2 that contains all of the klicenses (I think there's around 1,000). I know his app uses that portion of lv2, written as a bin file, to determine the klicense of a game. the klicense is actually a bunch of random bytes to obfuscate hacking I believe.
 
psydefx said:
according to aldo, ps3tools uses dklic_validator
Click to expand...

Sorry I did a mistake, dklic_validator is for edats.

I rechecked the source code and PKG ContentID uses: klicencebruteforce.exe and the set of keys stored in klics.txt, dev_klics.txt to verify the klicense, before try to decrypt an EBOOT, SELF or SPRX.
 
aldostools said:
Sorry I did a mistake, dklic_validator is for edats.

I rechecked the source code and PKG ContentID uses: klicencebruteforce.exe and the set of keys stored in klics.txt, dev_klics.txt to verify the klicense, before try to decrypt an EBOOT, SELF or SPRX.
Click to expand...
what command do i use for eboot.bin in klicencebruteforce? (klicencebruteforce [options] <self-file> <keydata-file> <ps3keys-file>)
 
the bruteforce tool has a gui, so u don't have to worry about commands. sometimes it finds the klicense quickly, other times not. there's a text file that contains the content id and klicense for various games/content, so it'll find the klicense instantly if the klicense has been recorded in there. I think @aldostools keeps an updated klicense text file with each new version of his tools. it's a way of keeping records of them, so u don't have to bruteforce it each time. though, the better way is using the system to get the klicense. aldostools web man mod, I believe, can record the klicense of a game once u've booted the game up. I think there's a command to save it to a text file. it should be much easier than bruteforcing it since it will be immediate.
 
If you can install the game then definitely use
webMAN-MOD klic command
OR
XMB CFW Settings.

Either way the klicense gets dumped to a log file & can be viewed on screen.

Sent with Tapatalk
 
You must log in or register to reply here.

Similar threads

Back
Top