1

(5 replies, posted in General discussion)

I agree a new guide should be made for v4.82 CFW (now that hopefully many new dumpers will be able to join with newly CFWed units due to the new ability no longer needing <3.55). It should possible using only latest version Rebug with no 3.55 downgrade or OtherOS. Credits go to NvrBst for this info!!

http://forum.redump.org/topic/12699/ps3 … tructions/

STEP 1
Convert to CFW, newer consoles up to 4.82 OFW can use "PS3Xploit" visit the official website and forums

STEP 2
Install an EID root key dumper and dump the EID root key to a flash drive and put on computer
* EID Root Key Dumper Link: http://store.brewology.com/ahomebrew.php?brewid=228

STEP 3
Use Rebug Toolbox or equivalent to make a NAND (fat PS3)/NOR (newer slim PS3) backup to flash drive (should be a one click button in the menu)
This should come pre-installed with Rebug CFW or downloadable as a standalone pkg from their website to install on other CFW

STEP 4
Extract the EID4 from the NOR or NAND using NvrBst's instructions
Use your hex editor of choice to extract the correct 48 byte string from your NOR or NAND dump. You can find the coordinates (offset) for this at the below wiki link.
* EID4 offsets inside your NOR or NAND dump: http://www.psdevwiki.com/ps3/Flash:Encr … _eEID#EID4
NOR: 0x00303A0 - 0x00303CF
NAND: 0x0081BA0 - 0x0081BCF

STEP 5
Use a hex editor software to concatenate the contents of your extracted EID4 (48 bytes extracted from the relevant location of the NAND or NOR) + EID Root Key to make a 96 bytes file and save this as "3Dump.bin" using NvrBst's instructions

STEP 6
Download the attachment on NvrBst's post in the linked thread called "Getkey-r2-GameOS" and install the contained .pkg on your PS3. This is the linux key dumper recompiled for the PS3's gameOS system. This was the key ingredient we needed.

STEP 7
Put the 3Dump.bin file on a flash drive (Fat32) root directory, insert the disc whose key must be dumped, and run the GetKey program on PS3. This should flash for a few seconds and create some .log files on the flash drive containing the necessary information to be submitted.

STEP 8
Dump the encrypted contents of the PS3 disc using for example IsoBuster on PC with a compatible BD drive, or find another clean way to dump encrypted

STEP 9
Submit, post on forums or PM me if you have any troubles

I'm not a wiki editor but if anyone wants to clean this up and pop it on there or if I should it might help the would-be dumpers smile
*I also think BD-Video (including hybrid PS3/BD-Video) needs a guide which I can do if I refresh myself, and also I believe I might have posed my successful steps somewhere in the forums.

NvrBst wrote:

Also keep in mind you can generate the 3Dump.bin yourself from almost any CFW version (including 4.65) if you really want to (just the official 3k3y app only works on 3.55). However downgrading and re-upgrading is fine too.

### Generating it Yourself Brief Summary ###
3Dump.bin is just the "EID4(48 bytes)+EID Root Key(48bytes)". EID4 you can get by making a NOR or NAND dump (typically via multiMan), and EID Root Key you need an app.

* EID Root Key Dumper Link: http://store.brewology.com/ahomebrew.php?brewid=228
* EID4 offsets inside your NOR or NAND dump: http://www.psdevwiki.com/ps3/Flash:Encr … _eEID#EID4

I've generated the 3Dump.bin manually on 4.46, and it matched my 3.55 3Dump.bin. If you havn't already downgraded, and need more detailed instructions I can try to help, just let me know.


EDIT: Also, more so for your own information, if you run the official 3k3y app on a non 3.55, the 3Dump.bin file that is generated is typically just 48bytes (EID4). However, it is probably best to only run the official 3k3y app on 3.55 CFW, especially since you can just get the EID4 from your NAND/NOR dump and who knows what the root key logic does if not run on 3.55 (very unlikely to brick your system, but, isn't the cleanest thing to do).

2

(24 replies, posted in Dumps)

for PVD, try the "PVD dumper" script attached by hiker13526, it makes it very easy for me to just drag the .bin or iso onto the bat
http://forum.redump.org/topic/15711/pri … in-python/

3

(1,629 replies, posted in General discussion)

So I am dumping a new disc with SecuROM 4.85.07 trying to get proper subchannel information but the subIntention.txt from a dump with the May 11 2017 version differs by one line (one less entry) from the dump I got using the March 23 2017 version

During this time the /se changed to /ns, so maybe my input is different? If I should be using more new /n* options related to protection maybe I missed something.

input commands are
DiscImageCreator.exe cd G rt3d2sec510 4 /c2 /d8 /ns [new]
DiscImageCreator.exe cd G rt3d2upse 4 /c2 /d8 /se [old]

the .sub files hash identically and psxt001z output is identical, and seems to include reference to the sector that is missing in the latest version (MSF: 01:41:62)

NEW SUBINTENTION

MSF: 00:01:74 Q-Data: 410100 00:40:01 00 00:03:74 2ef1
MSF: 01:08:50 Q-Data: 410101 21:06:50 00 05:08:50 0a8f
MSF: 01:21:70 Q-Data: 410101 01:19:74 00 01:21:50 45a0
MSF: 02:05:50 Q-Data: 410101 00:03:50 00 42:05:50 be00
MSF: 02:17:28 Q-Data: 410101 02:15:2c 00 02:17:08 ac40
MSF: 03:05:48 Q-Data: 410101 43:03:48 00 01:05:48 a41f
MSF: 03:13:38 Q-Data: 410101 03:51:38 00 03:11:38 ff1f
MSF: 03:14:56 Q-Data: 410101 03:12:5e 00 03:14:46 f374
MSF: 03:21:59 Q-Data: 410101 03:1d:59 00 03:01:59 5ea0
MSF: 03:36:49 Q-Data: 410101 03:36:49 00 03:76:49 a964
MSF: 03:38:47 Q-Data: 410101 03:36:45 00 03:38:07 2f4d

OLD SUBINTENTION

MSF: 00:01:74 Q-Data: 410100 00:40:01 00 00:03:74 2ef1
MSF: 01:08:50 Q-Data: 410101 21:06:50 00 05:08:50 0a8f
MSF: 01:21:70 Q-Data: 410101 01:19:74 00 01:21:50 45a0
MSF: 01:41:62 Q-Data: 410101 01:39:62 00 01:41:62 89a9
MSF: 02:05:50 Q-Data: 410101 00:03:50 00 42:05:50 be00
MSF: 02:17:28 Q-Data: 410101 02:15:2c 00 02:17:08 ac40
MSF: 03:05:48 Q-Data: 410101 43:03:48 00 01:05:48 a41f
MSF: 03:13:38 Q-Data: 410101 03:51:38 00 03:11:38 ff1f
MSF: 03:14:56 Q-Data: 410101 03:12:5e 00 03:14:46 f374
MSF: 03:21:59 Q-Data: 410101 03:1d:59 00 03:01:59 5ea0
MSF: 03:36:49 Q-Data: 410101 03:36:49 00 03:76:49 a964
MSF: 03:38:47 Q-Data: 410101 03:36:45 00 03:38:07 2f4d

psxt001z output

psxt001z by Dremora, v0.21 beta 1

MSF: 01:08:50 Q-Data: 410101 21:06:50 00 05:08:50 0a8f  xor 8001 3237 P1 xor 20 04
MSF: 01:21:70 Q-Data: 410101 01:19:74 00 01:21:50 45a0  xor 8001 2d65 P3 xor 04 20
MSF: 01:41:62 Q-Data: 410101 01:39:62 00 01:41:62 89a9  xor 0080 0080 ?
MSF: 01:56:40 Q-Data: 410101 01:54:40 00 01:56:40 4881  xor 0200 0200 ?
MSF: 02:05:50 Q-Data: 410101 00:03:50 00 42:05:50 be00  xor 8001 fd4f P1 xor 02 40
MSF: 02:17:28 Q-Data: 410101 02:15:2c 00 02:17:08 ac40  xor 8001 2d65 P3 xor 04 20
MSF: 02:31:68 Q-Data: 410101 02:29:68 00 02:31:68 bdc2  xor 4000 4000 ?
MSF: 03:05:48 Q-Data: 410101 43:03:48 00 01:05:48 a41f  xor 8001 338d P1 xor 40 02
MSF: 03:13:38 Q-Data: 410101 03:51:38 00 03:11:38 ff1f  xor 8001 8c73 P2 xor 40 02
MSF: 03:14:56 Q-Data: 410101 03:12:5e 00 03:14:46 f374  xor 8001 901d P3 xor 08 10
MSF: 03:21:59 Q-Data: 410101 03:1d:59 00 03:01:59 5ea0  xor 8001 8046 P2 xor 04 20
MSF: 03:24:09 Q-Data: 410101 03:22:09 00 03:24:09 02bd  xor 8000 8000 ?
MSF: 03:36:49 Q-Data: 410101 03:36:49 00 03:76:49 a964  xor 8001 068d P2 xor 02 40
MSF: 03:38:47 Q-Data: 410101 03:36:45 00 03:38:07 2f4d  xor 8001 8c46 P3 xor 02 40
MSF: 04:06:23 Q-Data: 410101 04:04:23 00 04:06:23 0936  xor 0400 0400 ?
Number of modified sectors: 15

Maybe the "?" means that the line at 01:41:62 should not be created and this is a fixed error in the newest version?
Just wanted to check so I don't submit something wrong to the db!
Thanks for this great tool smile

4

(1,629 replies, posted in General discussion)

More info on my issue:

In github 20170303, in _mainError.txt I get the following error when dumping a CD (IBM PC):
"This sector is data, but the header doesn't exist"
on Every Single LBA

It creates a .bin file with the same exact size as the Redump verified IsoBuster file, but different CRC. Also, when loading the new image into IsoBuster, it comes up as audio instead of data/file system

In github release 20161119, it dumps normally and matches Redump and IsoBuster output, and is data, using the same command as above

5

(1,629 replies, posted in General discussion)

Hi, thank you for this great and sophisticated tool!

I may be doing something wrong but for me the 2017-03-03 version gives me a different CRC than an older version I was using (August 26, 2015 or some date in that month according to the log).

The Old CRC matches Redump, IsoBuster, and ImgBurn, while the new one doesn't match any
I am using a non-plextor BDRW drive to rip IBM-PC CDs (so far just single track data discs). I noticed this difference in multiple discs

I will get back if you need more data, I know that testing more versions to see where the break happens would help probably.
The command I am using is "DiscImageCreator cd <letter> <name> # /c2" where the speed number I have tried variations 0, 8, or 24. /d8 is not supported on my drive.

Hope to get this sorted so I can submit good PC dumps.
PS once I get this working, I was looking for a good way to find the PVD