PS3 dumping instructions

[SpaceAgeHero]

Thanks for clarifying that.

Would it be possible then, theoretically, to extract metadata, disc_key etc. using classical PS3 homebrew applications?
Or is this not even possible technically without linux?
I don't really wanna mess with linux on 3.55. Would like to stay on 4.41 CFW.

[V.]

Well, the plan still is to make such an app someday, but interest in that has been lost a bit.
Technically it should be possible.

[NvrBst]

I ported the "GetKey-r2" application by JamJam to GameOS so people should be able to run from XMB now if they wish. Install the getkey.pkg, from the attachment "GetKey-r2-GameOS.7z" file, as you would any homebrew.

Instructions:
-) Put your 3Dump.bin on the root of a usb.
     GetKey will look for it at "/dev_usb000/3Dump.bin"
a) Put a disc in your PS3.
b) Put the USB in your right-most usb slot (/dev_usb000/).
c) Launch getkey from XMB: it'll run and exit back to XMB.

You should then notice 2 new files on the root of your USB:
/dev_usb000/getkey.log
/dev_usb000/disc.pic

The log/pic should be exactly what you got before. Transfer them off via ftp/usb/etc, and then repeat.

Example "getkey.log" from GameOS/XMB

Code: Select all

GetKey r2
Load keys
Test unit ready: return value of ioctl indicates success
Read pic: return value of ioctl indicates success
get dec key
  establish session keys:
    do send key: return value of ioctl indicates success
    do report key: return value of ioctl indicates success
    calculate session keys
    do send key: return value of ioctl indicates success
  get data
    do unknown e1:
    unknown e1 cdb: e100.....a0bf
    return value of ioctl indicates success
    do unknown e0:
    unknown e0 cdb: e0003....0b1c
    return value of ioctl indicates success
get_dec_key succeeded!


disc_key = cb66d33016a7d89308ebad7eb2379e64

disc_id = 00000000000000ff00020003XXXXXXXX
PIC:
10020000444901080000200042444f01
1101010000000000006f817f00100000
006f817e000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000

SUCCESS: Everything was correctly dumped.

Source is with the program, I tried to keep source as close to original program as possible, just do_cdb(...) has been modified for GameOS, and compiled with PSL1GHTv2.

I'll see what I can do to maybe rewrite the code so it's more simple / has the ability to dump information to screen maybe (or give some visual indications). Also ideally give you options to save pic/log files to alternate locations like net_host, and grab disc title for log filenames. Maybe edit so EID can be grabbed dynamically instead of 3Dump.bin. But for now I thought something is better than nothing for those who rather dump disc keys from XMB/GameOS instead of dual boot.

It has been tested with REBUG 4.46.1 LITE EDITION, but, it should work on any CFW fine. If someone else wish's to add any of the above features, etc, feel free to do so.



One question to JamJam/Someone. I notice the "disc.pic" is 4100 bytes (which seems corret based on the source code). I have done a few verifies, and the begining/log dumped PIC matches exsisting database items, so I'm sure it's fine, however, I always notice some data in the disc.pic at the next page boundary (800h). Example:

Code: Select all

000h: 10 02 00 00 44 49 01 08 00 00 20 00 42 44 4F 01 11 01 01 00 00 00 00 00 00 6F 81 7F 00 10 00 00 00 6F 81 7E 00 00 00 ...AllZeros...
800h: 00 00 00 00 45 42 01 00 00 00 00 00 FF FF FF FF FF FF FF FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...AllZeros...

Is this 800h information to be ignored? Does it exist for the original program (I don't have a dual boot to test with)?


EDIT: The attachment system doesn't seem to work, so uploaded to external: http://www.mediafire.com/download/g9pvt … -GameOS.7z

[V.]

Very nice! Thanks!

About the PIC, it is still  a bit unclear what is needed/wanted.
The original 3k3y stuff only dumped 0x73 bytes of the PIC.

[jamjam]

Well done modifying the source and making a pkg, I didn't expect anyone to modify it otherwise I might have made it a little cleaner

The PIC is a bit of a question mark. 3k3y gets 0x73 bytes, redump gets 0x84, and things can always change. The full PIC is dumped just in case we want more of it in the future.

[gamecaptor]

The Game OS version is exactly what I needed!! Thank you NvrBst! YOU ROCK!

[SpaceAgeHero]

Hey guys,

recently this has come to my attention: http://www.3k3y.com/ripp3r/.

The provider claims "It is the only software capable of creating accurate PS3 ISO images".

Even though I do not own any 3k3y-Hardware I checked out the Ripp3r-Software.
Since the application includes ISO encryption/decryption features, I wanted to know what it can do with my (Redump) PS3-ISOs, dumped following the guide in this very thread.

Well ... I wasn't too surprised to find that my ISO files were being rejected as "invalid ISO" when trying to use the built in ISO crypto feature, for instance.

So I am wondering, are my ISOs really accurate dumps?

I believe that I have read somewhere that 3k3y ISOs have the disc_key included, even though it doesn't really belong in the disc image. Could this be the reason why redump ISOs do not match, thus 3k3y ISOs being not accurate after all?

3k3y Ripp3r Software can be found here for your investigation: http://www.3k3y.com/ripp3r/Setup.msi

Also here is the documentation including some interesting PS3-Disc crypto-information: http://www.3k3y.com/index.php/download_ … ew/41/128/

Cheers.

[pablogm123]

While the dumps got using certain BD drives for PC (mainly Mediatek based ones) are completely OK, they aren't usable without the encryption key. To extract the key you can use the 3k3y Ripper PCB combined with a sacrificed (not reusable in any PS3 console anymore) BD-ROM drive ripped from a PS3 console.

More info:

/viewtopic.php?p=31206#p31206
/viewtopic.php?p=31209#p31209

[gamecaptor]

Hi gents,

I got a new PS3 (CECH-2001A). It's setup with Rebug 4.65.1. I installed NvrBst GetKey, but I need to get a dump of the drive. My question is what is the easiest way to get a 3dump.bin file? And can I use the 3Dump.bin file that I had in the PS3 FAT that I had previously (it had to go back to it's rightful owner)?

I have Little Big Planet 3 in hand at the moment and I would like to post it.

[usurper]

No, you need to get the drive key (3Dump.bin) from that ne PS3.
Be aware, that the dumping programm for the 3Dump.bin will just work under 3.55. For getting it, you need to downgrade your current CFW once. Afterwards you can upgrade back to whatever CFW you like.