Article: PS3 3.60 Keys Leaked

[Matsumot0]

The only idea I have is, did you re-encrypt the self files with the klicence?

I have looked at the elf file of the selfs in the original update pkg and the SDK is already 3.4 so no change required there.

If you PM the pkg file/ link I will look at it, but I am going on holiday early tomorrow so it will have to be today.


On an aside, do you live in Matsumoto or is it your name? Nice city been there quite a few times in the past visiting Seiko Epson.

Thanks for your answer

I'm sure, i re-encrypt the self file with the klicense, as defined in your explanations.
But I noticed if i want re-decrypt my new self, i don't need the klicense! as an eboot :O
maybe the problem is here, i don't see -> "[*] Warning: Could not decrypt header" as before.

And no i don't live in Matsumoto regrettably, it's just my nickname, but i trust you, if you tell me is a wonderful city, like this country where her is :P

Edit: it's ok i've solved my problem for: maybe the problem is here, i don't see -> "[*] Warning: Could not decrypt header" as before.
bad batch >_< i remove just a little synthax > "scetool -l AF0A8F0A8909F09234091AFADF909AF0 -v --sce-type=SELF" wtf xD
and the warning appears again! I don't know where does this -v lol

[aldostools]

It seems that some here have missed this:
Asure/Aldo's KLicense Tool Discussion - Page 18

It is a scetool-brute force tool, with heuristic algorythms to help to reduce the time finding the klicensee.
Just copy the EBOOT.BIN, self/sprx and PARAM.SFO to the folder and let the program fix them.
If the klicense is already known (currently 16 known klicensees), it will take only 3 seconds to resign/fix your game using 3.40 or 3.55 keys.
If the klicense is unknown, it could take some minutes or hours to find it. eg. WWE 12's took 1 hour 7 mins 37 secs to find it.

The tool is based on Asure's brute force batch script, but improved a lot with the help and ideas of several devs/users @ crunch (see the credits).

[Matsumot0]

Thank for updated your tool aldo

NBA 2K12 update 1.05 BLES01418-BLUS30830-BLJS10136: 6F46772AC2C84BA59484A73BB13B26BB
Metal Gear Solid HD 1.01 BLES01419-BLUS30847-BLJM61001: B608E78018A335E494B972A6B717A166


Can you make an autoupdate db? when you add new data in klics txt at launch of tool?

[mojamoja]

Same as me. I'm at HERMES 341
NPDRM signed patched eboot returns to xmb (8001003C)
if using SELF (not NPDRM) from ebootfix/mod, endless GT logo
if using NPDRM from ebootfix/mod output eboot, endless GT logo

an update to say that it finally worked fine with HERMES firmware

just be sure to:
- patch PKG's PARAM SFO to 341
- patch manually EBOOT ELF as described earlier in the thread "24 13 bc c5 f6 00 33 00 00 00 36"
(don't use ebootmod)
- sign it as NPDRM also as described using scetool (oakhead's messages)
(make_self_npdrm will produce an EBOOT ELF able to start, but will hang at GT logo)
- make the pkg

i updated successfully to 113

[Quakes69]

@ aldostools, Nice tool set thanks! TDU2 works great. hehehe

I have a side Question. Does it matter if you make a pkg of the fixed files with the same KLicense?

[aldostools]

@Quakes69

The release of pkgs with the fixed files is irrelevant. You can make the package yourself with few clicks:

1. Install my PS3 Tools
If you don't have cygwin installed in System32, you may need to copy the cygwin dlls and the ps3 keys to the ".\tools" folder
These files are required by the psn_package_npdrm.exe

2. Start PS3 Game Updates and download the game update for the game (if the 3.60 version is not available, try using Google)
3. Go to the downloaded folder and right click on the PKG, select "Extract to current folder..." (or press Shift+ENTER on the PKG)
4. Go to the extracted USRDIR and press Ctrl+ENTER on the EBOOT.BIN. Double click (or press ENTER) on the EBOOT.BIN to confirm it was signed with 3.55 key.
5. Press Ctrl+Enter on the self/sprx files. Double click (or press ENTER) on the self/sprx files to confirm they are signed with 3.55 key.
6. Delete the _ORIGINAL backup files.
7. Return to the extracted folder (the one that looks like a Content ID), right click on it and select Make PKG...
8. Install the new PKG on your PS3 and play!!

I think that it cannot be easier...

Other tips:
- to convert a retail PKG into a debug (DEX) PKG, just press Ctrl+Shift+ENTER on a PKG.
- to view the content id of a PKG, press Ctrl+ENTER on a PKG
- other files associated are to viewer a are: PUP, PKG, BIN, edat, self, sprx, thm, md5, sfo, sfx

[Quakes69]

@ aldostools;

So can I with my Make Package NPDRM GUI. Or have you forgot

I was just wondering if one had actually repack the pkg with the same KLicense is all. BTW, I run my GUI with out the cygwin' with psn_package_npdrm

To understand how to setup the GUI for Repackage is

Open the GUI.
Select the path that the PKG's are.
Click on the File you want. IE: TDU2 1.06 update pkg
Click the Second button. Drops down Settings
Tick --check
Click the Third button. Drops down Config
Make sure Package.conf is NOT Ticked/Checked at this time.
Click the Forth button. Drops down File/Target
Tick File
Hit Execute
Results:

"I:\******\psn_package_npdrm.exe" --check "I:*******\TDU2\UP0182-BLUS*****_00-TDU2000000000106-A0106-V0100-PE.pkg"

checking package validity:    %  100

Checker Revision : 1732
Package Filename : I:\PS3-DLC-PATCHES-PACKS\TDU2\UP0182-BLUS*****_00-TDU2000000000106-A0106-V0100-PE.pkg
ContentID        = UP0182-BLUS*****_00-TDU2000000000106
DRMType          = Free
ContentType      = GameData
PackageType      = DiscGamePatch
PackageFlag      = RenameDirectory (during install for consistency)
PackageVersion   = 01.00
# APP_VER        : 01.06
# TARGET_APP_VER : 01.05
# PS3_SYSTEM_VER : 03.6000
# PackageSize    : 19,934,512 bytes
# QA_Digest      : 0x********************************
#                : This is a digest of packaged files and attributes.
# PackageDigest  : 0x********************************
#                : This is sha1 digest of package without last 32 bytes.
# Packaged by    : MODDED V1.0 - Original Rev. 1732
Notice: Patch package should be same ID and types with the original package.
    please double check it because it can violate DRM protection.
This file was finalized: "I:\********\TDU2\UP0182-BLUS*****_00-TDU2000000000106-A0106-V0100-PE.pkg"

Take a mental note of the BOLD settings used for the Previous pkg. Or just leave the Output window open

Repack:
Click on first button - Collapses File viewer
Untick --check / Tick -output - Click the right most button to select the output directory you wanna save your New PKG
Tick Package.conf
With the Original file selected it would have put it in the ContentID. Remove the last "-A0106-V0100-PE" Click OK
Example:
ContentID = UP0182-BLUS*****_00-TDU2000000000106
DRMType = Free
ContentType = GameData
PackageType = DiscGamePatch

Untick File and Tick Target-Dir change the Target-Dir to the folder with the fixed Files.
Example:
I:\DLC-PATCHES\TDU2\BLUS*****

Click Execute. Install on PS3 all seems long but it's all just clicks and done.

All I wanted to know if it was Necessary to repack with the same KLicense...

Thanks,

Quake

[aldostools]

@ aldostools;

All I wanted to know if it was Necessary to repack with the same KLicense...

Sorry I misread your question...

I always repack all my PKGs using the free klic 72F990788F9CFF745725F08E4C128387 and I haven't had any issue.

[Quakes69]

Sorry I misread your question...

I always repack all my PKGs using the free klic 72F990788F9CFF745725F08E4C128387 and I haven't had any issue.

OK, That's all I wanted to know. I was using that one too for a while.

I think I should put in a Menu option or a Drop down for KLicenses. Or maybe load up your klics.txt to a Menu/Drop down select.



Quake

Edit: Then again, What's the sense. If it doesn't matter for the PKG itself then there would no sense on doing that. Oh well...

[Matsumot0]

Finally i've solved my problem... for black ops patch 1.13 it's just a f*cking... --skip-sections=TRUE to FALSE... omg

Scetool docs: -s, --skip-sections TRUE(default)/FALSE Whether to skip sections or not.