PS3 3.60 Keys Leaked

Published on 08-01-2012 05:18 AM

343 Comments

First it seemed as if it was just a rumor or perhaps fake. But euss has confirmed that they are indeed real. The day I'm sure all of you have been waiting for. The release of some PlayStation 3 keys (lv1ldr, lv2ldr, isoldr, appldr) have been leaked to the masses allowing you to patch 65 additional games. You will need a few tools in order to patch the SFO of your games. Or not. Word is Rogero says a new custom firmware will be made available. So those of you who don't want to decrypt and encrypt files should just wait a little longer.

eussNL Comments:

If you post keys in a random topic, you will fast enough be
marked as a troll. When posting keys, please do it in proper
format, so it can be easily debunked/proven

greetz, eussNL

KaKaRoTo Comments:

3.60 keys Update:

Q: recently 3.60 keys surfaced (lv1ldr, lv2ldr, isoldr, appldr), what does this mean for this release and the future?
A: That is actually a multiparted answer:

Now that several binairies (Iso module + CoreOS minus the loaders that are inside lv0) can be decrypted, more investigation can be done in them, which give a new boost in (unrelated to the HeN) other targets, like:

Hardwareless downgrades : Downgrading with PSgrade Dongle (lv1.self)
QA Flagging / systemtokens (spu_token_processor.self) and usertokens (spu_utoken_processor.self)
PS2 compatibility (mc_iso_spu_module.self , me_iso_for_ps2emu.self , sv_iso_for_ps2emu.self)
Getting per_console_root_key_1 / EID_root_key on 3.56+/slim3K (lv1.self , aim_spu_module.self)
Backsigning applications for <=3.55 and patch sys_proc_param_version (appldr.self , lv2_kernel.self)

Q: So does this mean a future release would be sooner?
A: Only God knows

But it can also be that because of the above, it would become meaningless/surpassed by better progress. So lets all hope for the best

I will be adding to this article as I learn more. Just wanted to rush this news to you asap.

UPDATE: Use Deank's EBOOT Fix Tool 0.5 to convert the EBOOTS for you. Just download the keys add them to EBOOT Fix Tool's ps3 folder. (Download below includes the keys, so no need to download them unless using other methods)

Originally Posted by deank

They also posted my ebootFIX/ebootMOD tools prepackaged with the keys in .ps3 folder, so it is ready to be used like in the old 3.41/3.55 days.

Have in mind that some games (like Sniper Ghost Warrior) have additional .self/.sprx files and it is better to use ebootFIX by dragging the PS3_GAME folder to it - it will find and fix all necessary files. If you use ebootMOD you'll have to search for these files yourself and 'fix' them one by one.

UPDATE 2: Another Method

Use SCETool to Decrypt a PS3 3.60 EBOOT.BIN File:
For those of you who want to decrypt a 3.60 EBOOT.BIN use scetool. Download scetool_0.2.7.zip unzip it to C:\scetool. Create a new folder inside scetool and name it data and download these files here:

keys: ps3devwiki.com/files/devtools/scetool/data/keys
ldr_curves: ps3devwiki.com/files/devtools/scetool/data/ldr_curves
vsh_curves: ps3devwiki.com/files/devtools/scetool/data/vsh_curves

Put them inside data folder. Put your EBOOT.BIN file in scetool folder. Go to start - run - cmd and cd to the folder were scetool is. For example "cd C:\scetool". Then type this command to decrypt the EBOOT.BIN: "scetool -d EBOOT.BIN EBOOT.ELF" and use this one to encrypt it to 3.41: C:\scetool>scetool -0=SELF -5=APP -6=0003004100000000 -e EBOOT.elf EBOOT.BIN

Download: Deank's EBOOT Fix Tool 0.5 - UPDATED LINK

Source: elotrolado via ps3crunch via ps3devwiki via ps3news

Thanks to deeptrap for the awesome news tip!

PSX-SCENE: The Pinnacle Scene Xenocracy

● Latest News ● Report News ● Search Forums ● Hall of Fame ●
● Facebook.com/PSXScene ● RSS ● Twitter.com/psx_scene ●

Share
- Share this post on
- Digg
- Del.icio.us
- Technorati
- Twitter

RUT Dark Ronin, SkyNet, bourat and 5 others like this.

Categories:

_{Tags :

euss,

kakaroto,

ps3,

ps3 3.60 keys,

ps3 custom firmware,

ps3 hacks,

ps3 keays,

ps3 keys leaked,

rogero}

343 Comments

Matsumot0 - 08-15-2012, 08:22 AM
- Reply
i use PS3/PSP PKG Decryper & Extrator by Mathieulh for retail
or PkgView for debug

dewitman - 08-15-2012, 08:51 AM
- Reply
I used pkgViewer an then clicked Associate .pkg files with this application, now I can extract the pkg files. I tried fixing the update for GoldenEye reloaded and everything went fine. I patched the EBOOT and got this when I doubleclicked it:

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 [3.55]

But then to repackage it, do I have to rightclick the BLES01292 folder or the EP0002-BLES01292_00-GOLDENEYEPATCH02-A0102-V0100-PE_fw36000,00 folder and select "Make pkg"?
I have tried it on the BLES01292 folder and when I opened it with pkgView it had the same structure as the original pkg so I assume this is the correct folder to create a pkg from.

I also tried to fix the 1.13 update for COD Black Ops but on both the self files (t5_ps3f self and t5mp_ps3f self) I get[*] Error: Could not decrypt header., but it continued after the error. When I check them afterwards, they are signe for 3.55. The EBOOT doesnt have this error when I CTRL + ENTER it.
Can I ignore this error or is this something serious and should I avoid installing my fixed package?

Both are the European region patches for the games, just so you know.

BlyackScorpio - 08-15-2012, 03:59 PM
- Reply
Originally Posted by 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

Where can I get the tools you're speaking of. I visited your page but I'm not sure which tool you're talking about. Also, is there an installable cygwin or do I just need to get the files and move them to system32? I have the 3.60keys folder from deank and it has some cy****.dll files in there. Are those the ones you're speaking of?