[DEFAULTDNB]

Originally Posted by n0der Weird! The testing we did must have been done on a different version then. With BLUS30732 all 22 (not 21) .sprx elfs decrypt without any complain from scetool. Do you remember which specific .sprx failed on your try? Do you have a link to Ifcaro explanation? Thanks for the answer.

it was materials_ps3.sprx/client_ps3.sprx and server_ps3.sprx

Ifcaros statement:

I used scetool for decryption and makeself for encryption. I just did that.

I'm 99% sure it was 21 sprx's I ripped my own disc like 3 times while testing, and 3 times it failed to fix 3 of them...

[Viral Doom]

Originally Posted by Esportes Thanks alot Azure and Longhorn. Finally i can fix the updates of my games which nobody cares. Like: Little Big Planet 2 (1.07) Monopoly (1.02) Motorstorm Apocalypse (1.05) But this self and sprx is ****ing all. Socom 4 (1.05) s4_g.self(24,2 MB) and libspace_g.sprx(337,36 KB) Battlefield 3 (1.05) Engine.BuildInfo_Ps3_Retail.sprx(5.77 KB) ************* [ - Post Merged - ] ************* And i don´t understand something. Call of Duty Black Ops (1.13) Have 2 self. t5_ps3.self and t5mp_ps3.self. Is there any difference between this files and the older versions?

SOCOM 4 - U.S. Navy SEALs [BCUS98135]

Hi dude, I've been doing the same as you, updating my games to 3.60 and making the proper fixes, and SOCOM its a paint in the ass:

The self key is: 08727df80102030431c855b900000101

Like the EBOOT.BIN, the s4_g.self also have to be edited by hexa, I mean:

00 33 00 00 00 35

to

00 33 00 00 00 34

Yes', I'm doing it for 3.41

the libspace_g.sprx dosesn't have to be edited, or I didn't find the same rutine

I encrypt the 3 files to 3.41, for EBOOT.BIN is not a problem, but I wanna make sure if I'm doing well with the .self and .sprx files, I'm basically doing this:

scetool.exe --sce-type=SELF --compress-data=TRUE --skip-sections=TRUE --key-revision=0A --self-auth-id=1010000001000003 --self-add-shdrs=TRUE --self-vendor-id=01000002 --self-type=NPDRM --self-fw-version=0003004100000000 --np-license-type=FREE --np-content-id=%CID% --np-app-type=EXEC --np-real-fname=self_out.self --encrypt self_out.elf self_out.self
scetool -i self_out.self

I'ts the same that I use for EBOOT.BIN

When i create the .pkg, the game boots and promp a message saying the version is no correct and I have to update again by PSN.

I read about this problem with OFW as well

BTW, do u have the original EBOOT.BIN, s4_g.self and libspace_g.sprx. BCUS98135

[opoisso893]

Originally Posted by Viral Doom SOCOM 4 - U.S. Navy SEALs [BCUS98135] Hi dude, I've been doing the same as you, updating my games to 3.60 and making the proper fixes, and SOCOM its a paint in the ass: The self key is: 08727df80102030431c855b900000101 Like the EBOOT.BIN, the s4_g.self also have to be edited by hexa, I mean: 00 33 00 00 00 35 to 00 33 00 00 00 34 Yes', I'm doing it for 3.41 the libspace_g.sprx dosesn't have to be edited, or I didn't find the same rutine I encrypt the 3 files to 3.41, for EBOOT.BIN is not a problem, but I wanna make sure if I'm doing well with the .self and .sprx files, I'm basically doing this: scetool.exe --sce-type=SELF --compress-data=TRUE --skip-sections=TRUE --key-revision=0A --self-auth-id=1010000001000003 --self-add-shdrs=TRUE --self-vendor-id=01000002 --self-type=NPDRM --self-fw-version=0003004100000000 --np-license-type=FREE --np-content-id=%CID% --np-app-type=EXEC --np-real-fname=self_out.self --encrypt self_out.elf self_out.self scetool -i self_out.self I'ts the same that I use for EBOOT.BIN When i create the .pkg, the game boots and promp a message saying the version is no correct and I have to update again by PSN. I read about this problem with OFW as well BTW, do u have the original EBOOT.BIN, s4_g.self and libspace_g.sprx. BCUS98135

Change --np-app-type=EXEC by --np-app-type=SPRX for sprx files.

[Viral Doom]

Originally Posted by opoisso893 Change --np-app-type=EXEC by --np-app-type=SPRX for sprx files.

Hi, thanks for answer, I'll try it.

I have a question, what is the diference between:

--key-revision=0010 >>>> --key-revision=000A
--np-content-id=%CID% >>>> --np-content-id=%~1

I know that 0010 is for 3.55 and 000A for 3.60, but is any diference at the time to encrypt?

[opoisso893]

Originally Posted by Viral Doom Hi, thanks for answer, I'll try it. I have a question, what is the diference between: --key-revision=0010 >>>> --key-revision=000A --np-content-id=%CID% >>>> --np-content-id=%~1 I know that 0010 is for 3.55 and 000A for 3.60, but is any diference at the time to encrypt?

With scetool v0.2.8 :
--key-revision=000A => SDK 3.55
--key-revision=0004 => SDK 3.40
http://www.ps3devwiki.com/wiki/Revision_versus_Version

%CID% or %~1 depend of your script.

[Asure]

If some of you can share back klic's that you find (pm is fine, or post them in the topic) it might be possible to improve the bat file so we can search for them faster, and simplify the process.

[Viral Doom]

Originally Posted by opoisso893 With scetool v0.2.8 : --key-revision=000A => SDK 3.55 --key-revision=0004 => SDK 3.40 http://www.ps3devwiki.com/wiki/Revision_versus_Version %CID% or %~1 depend of your script.

Thats right, I already read that, but my question is at the momento to encrpyt the .bin what issues presents.

In other words, I should use --key-revision=0004 if I'm making fixes for 3.41? or does'nt matter?

About my script, I'm using this one:

@Echo
 off
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
rename EBOOT.BIN EBOOT_ORIGINAL.BIN
pause
scetool.exe --sce-type=SELF --compress-data=TRUE --skip-sections=TRUE --key-revision=0010 --self-auth-id=1010000001000003 --self-add-shdrs=TRUE --self-vendor-id=01000002 --self-type=NPDRM --self-fw-version=0003004100000000 --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
scetool -i EBOOT.BIN
pause

and I also use this one:

scetool.exe --decrypt EBOOT.BIN EBOOT.ELF
rename EBOOT.BIN EBOOT_ORIGINAL.BIN
pause
scetool.exe --sce-type=SELF --compress-data=TRUE --skip-sections=TRUE --key-revision=0010 --self-auth-id=1010000001000003 --self-add-shdrs=TRUE --self-vendor-id=01000002 --self-type=NPDRM --self-fw-version=0003004100000000 --np-license-type=FREE --np-content-id=%~1 --np-app-type=EXEC --np-real-fname=EBOOT.BIN --encrypt EBOOT.ELF EBOOT.BIN
pause
del /Q EBOOT.ELF
scetool -i EBOOT.BIN
pause

the only diference is the header and the %CID% / %~1 value:

@Echo
 off
FOR /F "tokens=1,2 delims= " %%A IN ('scetool.exe -i EBOOT.BIN') DO (
if [%%A]==[ContentID] set CID=%%B
)

CID is the ContentID, in this case this script set the right ContentID?

[Asure]

Well, 3.55 also can decrypt 3.4x so i don't see any issues using lower versions.
You should use the contentID from the orignal eboot.bin.

[Viral Doom]

Originally Posted by opoisso893 Change --np-app-type=EXEC by --np-app-type=SPRX for sprx files.

Nothing bro, the same results

Originally Posted by Asure Well, 3.55 also can decrypt 3.4x so i don't see any issues using lower versions. You should use the contentID from the orignal eboot.bin.

But if I make a fix to 3.41, I NEED to use 0004?

About ContentID, should I use, for example SOCOM 4:

ContentID: UP9000-BCUS98135_00-S4PATCH000000001

So, in the script I use:

--np-content-id=UP9000-BCUS98135_00-S4PATCH000000001

is that what u mean?

What is the diferences to use the right ContentID?, I have made more than 10 Fixes with %CID% / %~1, and the result its the same: works ^^

[longhornx]

Originally Posted by Viral Doom Nothing bro, the same results But if I make a fix to 3.41, I NEED to use 0004? About ContentID, should I use, for example SOCOM 4: ContentID: UP9000-BCUS98135_00-S4PATCH000000001 So, in the script I use: --np-content-id=UP9000-BCUS98135_00-S4PATCH000000001 is that what u mean? What is the diferences to use the right ContentID?, I have made more than 10 Fixes with %CID% / %~1, and the result its the same: works ^^

you have to use the content id inside of original eboot.bin, just read it with scetool -i eboot.bin

%CID% -<is returned from scetool -i blabal.self(bin) = content id
%~1 is the value inputed in from batch, eg:

mybatch.bat value2input
value2input will be a var called %1 (%~1=without quotes)

EDIT: can someone try to decrypt 2 self files inside of this MW2 (BLES00683) patch?

eboot.elf has only 69.6KB i used this batch without success

@Echo off for %%S in (eboot.elf) do SET /a LAST_OFFSET=%%~zS-16 for %%S in (eboot.elf) do SET /a MAX_OFFSET=%%~zS-16 :START set CUT=8 if %LAST_OFFSET% gtr 1000000 ( set /a CUT+=1 ) rem echo Cut val: %CUT% FOR /F "tokens=*" %%i in ('"od -j%LAST_OFFSET% -N16 -w16 -t x1 eboot.elf | cut -c %CUT%- |sed 's/ //g'"') do SET KEY=%%i if %KEY% == 00000000000000000000000000000000 ( echo Skipped 10 bytes of blank/useless key at %LAST_OFFSET% set /a LAST_OFFSET-=10 ) else ( ECHO Trying Key: %KEY% from decimal offset: %LAST_OFFSET% / %MAX_OFFSET% scetool.exe -d patch.self selfout.elf -l %KEY% >nul set /a LAST_OFFSET-=1 ) IF EXIST selfout.elf GOTO END goto START :end echo Done! Key used was: %KEY% pause

Download patch v1.13