Search options

To create an IRD file using Redump2IRD program you would need:

1. PS3 disc image (ISO) in encrypted state;
2. Corresponding Disc Key from Metadata section of a redump entry for the disc;
3. Corresponding Disc ID from Metadata section of a redump entry for the disc;
4. Corresponding Permanent Information & Control (PIC) from Metadata section of a redump entry for the disc;

What to do:

1. Launch Redump2IRD program;
2. Make sure Redump Mode is ticked (at the bottom);
3. Put Disc Key into Encrypted D1 (Key) field;
4. Put Disc ID into Decrypted D2 (ID) field;
5. Put Permanent Information & Control (PIC) into Permanent Information & Control (PIC) Data (in Hex) field;
6. Press Create IRD button;
7. Select encrypted image (ISO file);
8. After 10-20 seconds pause, input filename for IRD file.

The result is an IRD file for >decrypted< image of the game.

No Mastering SID Code?

No Toolstamp?

Hello.

Have you tried reading remaining ring codes in some way?
You can try using CIS scanner if you have one: https://youtu.be/HfOSmGjvs8w

I've tried using the 1.41 test build with the same scratched LittleBigPlanet disc.

https://youtu.be/Pc-yYqFAI7w

1. At 05:30 you can see that the log stating read errors appears which is nice.

2. At 06:33 you can see that 30/30 re-tries are reached on the first bad sector, no termination of dumping process or any prompt appearing happens. The log itself is already a pretty nice development but I would like to see a setting (that could be switched on and off in the global settings of the program, for example) that would make dumping process actually be terminated upon any bad sector reaching 30/30 re-tries. My reasoning is that, with multiMAN after I start dumping process, I go and do something else. I don't need to constantly monitor the screen since multiMAN will outright terminate the dumping process by itself. With ManaGunZ in its current state I need to monitor screen in order to know if read errors happened or not.

Also, I'm not sure why multiMAN and ManaGunZ make optical drive behave differently when read errors are encountered. Again, as I've described in my previous post multiMAN would stop and spin the disc again which is very audible while ManaGunZ doesn't do this, even in the 1.41 test version. It wouldn't matter much if the output dumps are correct, I guess. Just a thought.

3. At 07:43 you can see that Cancelled notification pops-up at the upper right corner. That's me trying to terminate the dumping process by pressing Circle button. For some reason, termination doesn't happen if the log is actively shown on screen. When I pressed Hide logs button at 08:14, the dumping process was allowed to be terminated.

I also tried using the newly implemented "Get files for redump.org" function seen at 0:23 in the above video. Works perfectly. And more than that, it outputs files with the custom filenames which include timestamps like this:

BCES01663_20210722_071038.getkey.log
BCES01663_20210722_071038.disc.pic

This is a nice improvement in comparison to GetKey since when keys are dumped via GetKey the output files' filenames would remain the same, meaning that GetKey would overwrite them. This forces dumpers to transfer the files to PC after each dump which wastes time. ManaGunZ improves on this, especially since it uses timestamps a dumper can dump multiple copies of the same game in one session and the files won't be overwritten.

So, ManaGunZ is approaching to be the dumping tool for me. Allow for automatic dumping process termination upon encountering read errors and I'll switch to it. And if FTP connection is added at some point, then I'll drop multiMAN entirely (haven't tried webMAN-MOD yet).

Hello.

From what I understand HEN doesn't provide enough access to the system's inner workings. In particular it's not possible to dump eid_root_key and without it you wouldn't be able to use Getkey.

You need to have a proper CFW installed.