Article: PS3 3.60 Keys Leaked

[cerebr_al]

Thanks @mossopinc but the site says it's free downloads are currently exhausted. I am too will try again in the morning!

Just went through and downloading. Thank you!!!

[sketchdesigner]

if there is anywhere that I can upload the files to and link without getting into trouble then let me know and I'll provide the working fix(s) that I used that dont work from scenefiles

[Elissa]

Snip

I can look up how to repackage the eboot. Thanks for all the information I'll try it tonight and post back if it works or not.

[Ultron]

Still hoping to one day play Disgaea 4

That's exactly what I was hoping to do with this. I thought Disgaea 4 WAS 3.6, but i guess not T_T

[whitedove]

anyone having trouble with mm ebootfix this might work for you rename .ps3 folder to ps3keys or make a ps3keys folder and copy keys in to it it worked for me and anyone know how to rencrypt with scetool this does not work freezes scetool -0=SELF -5=APP -6=0003004100000000 -e EBOOT.elf EBOOT.BIN

[bonbon1477]

anybody here got ACE COMBAT ASSAULT HORIZON (BLES01392) fix working? the game is in 3.70 but it has an 3.60 update/patch. i tried to encrypt the update's eboot using multiMAN Eboot Fix Tool 0.5 but it doesn't seem to work. if anyone have an idea how to do it correctly, please do tell. it will be greatly appreciated. thanks.

[mojamoja]

hi oakhead,

did you repacked the EBOOT ?

I followed instructions exactly as described (GT5 euro BCES00569) 113, as well as patching PARAM located in home BCES00569
It didn't work, got a message at XMB I have to upgrade to 360 (i'm still at 341 HERMES)

Some information must be recorded during PKG information.
I did cleanup. Install update 105. Manually deleted the home BCES00569 directory, so there were virtually no EBOOT or PARAM files anymore.
Again, when I start to launch it, i still have that message asking for upgrading ?!
any ideas ?

bye.

[oakhead69]

hi oakhead,

did you repacked the EBOOT ?

I followed instructions exactly as described (GT5 euro BCES00569) 113, as well as patching PARAM located in home BCES00569
It didn't work, got a message at XMB I have to upgrade to 360 (i'm still at 341 HERMES)

Some information must be recorded during PKG information.
I did cleanup. Install update 105. Manually deleted the home BCES00569 directory, so there were virtually no EBOOT or PARAM files anymore.
Again, when I start to launch it, i still have that message asking for upgrading ?!
any ideas ?

bye.

I am on 3.55, but I guess it should be OK on 3.41.

For GT5 I 'fixed the EBOOT, that I extract from update 1.12 EP9001-BCES00569_00-0000000000000000-A0112-V0100-PE.pkg (as 1.13 does not have an EBOOT).
I then 'fixed' this eboot using the steps I described.
I then extracted update 1.13 EP9001-BCES00569_00-0000000000000000-A0113-V0100-PE.pkg
Added the 'fixed' EBOOT to the USRDIR, edited the PARAM.SFO to 3.41 from 3.6.
I then repackaged the update using psn_package_npdrm.exe.

If you do not want to repackage it, then use MultiMan to replace the EBOOT.BIN and PARAM.SFO in hdd0/game/BCES00569. After you have installed all updates from 1.05 - 1.13. Just remember you to install ALL the updates in order.

This worked fine for me GT5 now working on 1.13 update.

As for update 1.05 that is only 3.5 and you could already do this ages ago. This is only needed for update 1.10 onwards and you only need to 'fix' the EBOOT from the latest version (or in this case the one before)

It also worked for BLES01214 Earth Defense Force®: Insect Armageddon™.

[ceast21]

Seems alot of people are having trouble getting certain games to work correctly doing eboots themselves.

Im sure this will be frowned upon but those of you who want already made eboots
just google "3.60 keys leaked eboots" it will be the first link.
than you click "new decrypted PlayStation 3 EBOOT fixes" at the top of post & it will take you to a post which is being updated freq that has the eboots.

hope i dont get in trouble im just trying to help the page also has good info on the doit yourself eboot fix process.

[mojamoja]

Thanks for your reply.

It looks like it HAS to be packaged.
What i did, 105-113 updates installation (order ok)
Get from ftp (multiman) eboot and param files, patched them, and again ftp.
Looks good ... but I had that message about 360 upgrade.

As you did, I rebuild a 113 package with 112 patched files.
Looks better now, I have still an issue 8001003C, but I can see it's loading, so that's far better...