wiki.redump.info Wiki - User contributions [en]

Nintendo Wii U Dumping Guide

2026-07-10T18:07:40Z

Darksabre76:

This guide is an early work in progress.
==Retail Discs==
===Tools===
* Wii U console with a network connection
** Networking only required for soft-modding

* 32GB+ SD Card formatted to FAT32.
** (Optional) Additional 32GB+ USB storage device formatted to FAT32 or NTFS.
** Higher sizes are recommended as all WUDs are 25GB. Please note that some external devices require a Y-Cable or external power, as the Wii U's USB ports don't supply much power.

* [https://github.com/FIX94/wudump/releases/latest WUDump] or [https://github.com/wiiu-env/wudd/releases/latest WUDD] (Wii U Disc Dumper), to dump the actual game.
** If you use WUDD, you will need a tool that can calculate hashes such as [http://www.slavasoft.com/hashcalc/ Hashcalc] or [https://github.com/namazso/OpenHashTab/releases OpenHashTab].

===First Time Setup===
* Install the homebrew channel by following this [https://wiiu.hacks.guide/#/ guide] (or alternatively you can just download the [https://github.com/dimok789/homebrew_launcher/releases homebrew channel], place the wiiu folder on your SD Root and run it one-off using the browser exploit)
'''Option 1 - Setting up WUDump'''
* Download WUDump from above, and place it in SD:/wiiu/apps/wudump/ (you will need to make the folder 'wudump')
'''Option 2 - Setting up WUDD'''
* Download WUDD from above. If you installed Tiramisu on your Wii U, download the .rpx release. The .wuhb release can only be used with Aroma.
* Copy the wiiu folder to the root of your SD Card

===Dumping===
'''Option 1 - Dumping with WUDump'''
* Run the Homebrew Launcher.
* Once in the Homebrew launcher, select wudump, then hit Load.
* Press the appropriate button for what device you are dumping to (FAT32 USB, NTFS USB, or FAT32 SD)
* Once ready, the program will inform you to insert the disc; if you already have the disc inserted, simply eject and re-insert.

* This process takes a long time (1-2 hours!), so go get lunch and wait.

'''Option 2 - Dumping with WUDD'''
* Load WUDD through the Homebrew Launcher (Tiramisu) or the Wii U Menu (Aroma)
* Insert the disc and select which device you would like to dump to (FAT32 SD or NTFS USB) and then select Dump as WUD.
* If you dumped to a FAT32 device, the WUD will be split into 12 .part files that you need to combine. To do this:
** Copy the folder containing the part files to a file system with large file support (eg NTFS)
** Open a command prompt there and then copy and run the following command
(wudump) copy /b game_part1.wud + game_part2.wud + game_part3.wud + game_part4.wud + game_part5.wud + game_part6.wud + game_part7.wud + game_part8.wud + game_part9.wud + game_part10.wud + game_part11.wud + game_part12.wud game.wud
(WUDD) copy /b game.wud.part1 + game.wud.part2 + game.wud.part3 + game.wud.part4 + game.wud.part5 + game.wud.part6 + game.wud.part7 + game.wud.part8 + game.wud.part9 + game.wud.part10 + game.wud.part11 + game.wud.part12 game.wud

* You should now have two files, game.key and the full game.wud (the .part files are not needed anymore and can be deleted)
* Run Hashcalc, press the '...' button and select the game.wud file.
* Tick the MD5, SHA-1 and CRC32 boxes then click 'calculate'
* Open notepad, copy the template below and replace the data in <Angled Brackets> with the version of WUDD used and the data from Hashcalc.
* (If a new disc) Using a hex editor, open game.wud and copy the Internal Serial into "Comments".
Dumped with WUDD - Wii U Disc Dumper <Version of WUDD used>
MD5: <Paste the MD5 from Hashcalc here>
SHA1: <Paste the SHA1 from Hashcalc here>
CRC32: <Paste the CRC32 from Hashcalc here>
Internal Serial: <Paste the Internal Serial from your disc image here>
* Save the file as game.txt
* Keep your game.key file for personal use

==Development Discs (CAT-R)==
CAT-Rs can be dumped two ways:
*[[Disc Dumping Guide (MPF)]] with a Blu-Ray drive. MediaTek-based and Pioneer-based PC bluray drives have been confirmed as able to dump CAT-R discs. It's highly likely other drive models work as well (but have not been confirmed).
*Using the regular homebrew dumping methods, but on CAT-I/CAT-R/CAT-DEV hardware.

==Submitting Info to Redump==
Copy the CRC32 from your game.txt file, open the [https://redump.info/ Redump homepage] and paste the hash into the Quick search field in the upper right.
* If the search returns an existing entry on Redump, your dump is a verification and should be submitted on the [https://forum.redump.info/forum/16/verifications/ "Verifications" forum].
* If there is no existing entry for this hash, submit your dump on the [https://forum.redump.info/forum/11/dumps/ "New Dumps" forum]. '''Discs dumped with WUDD are currently only accepted for verifications.'''
* If you have dumper rights you should submit the dumpinfo using the [https://redump.info/newdisc/ New Disc form].
Please review the important guidelines outlined in this forum thread regarding submission of both new discs and verifications: [https://forum.redump.info/topic/27377/read-this-how-to-submit-new-dumps-verifications/ Redump Submissions]

'''Notes using the New Disc form''':
*In the New Disc form, put all ring information in the 'Ring' field like you would using the template below (a moderator will format them properly).
*Language Select and Case Serial information can go into the 'Comments' field.

[quote]
Note: paste the contents of the WUDump / WUDD game.txt or here.
[/quote]

[b]Game Information:[/b]

[b]Game Title:[/b]
[b]Region:[/b] Europe / USA / Japan / UK / Scandinavia / Australia
[b]Languages:[/b] English, German, French, Spanish, Italian, Dutch, Swedish, Norwegian, Danish, etc...
[b]Language Select:[/b] Language select via BIOS system settings / Language select screen at startup
[b]Disc Serial:[/b]
[b]Edition:[/b] Original / Demo / Starter Pack / Nintendo Selects
[b]Case Barcode:[/b]
[b]Case Serial:[/b]
[b]Size:[/b] 25.025.314.816

[b]Ring Information:[/b]

[b]Mastering Code (back):[/b]
[b]Mastering SID Code (back):[/b]
[b]Mould SID Code (back):[/b] IFPI XXXX
[b]Additional Mould Text (back):[/b]
[b]Toolstamp (back):[/b]
[b]Mould SID Code (front):[/b] IFPI XXXX
[b]Additional Mould Text (front):[/b]

[b]Game Key:[/b] Attached

'''Note:''' Don't forget to attach the game.key file to the post!

* '''Ring code info:''' [https://web.archive.org/web/20240514073908/https://media.discordapp.net/attachments/418896391092437000/965186288280023120/ringcodes-wiiu-back.jpg?ex=6643db87&is=66428a07&hm=ebcbfcf5876c3171e5f1f4a41418922a8cdf7fb8d74415e709e3b854afb2338b&=&format=webp&width=610&height=616 useful reference image]

[[Category:Dumping Guides]]

Sony PlayStation 3 Dumping Guide

2026-07-10T18:06:28Z

Darksabre76: Update mentions of PS3 keys

'''PlayStation 3''' dumping can be done in a few different ways which are detailed below.

Notes about dumping '''PS3 preproduction BD-R / DVD-R''' and '''PS3 kiosk discs''':
* Dump these with the [[Disc Dumping Guide (MPF)]] method.
* Preproduction builds can be BD-R or DVD-R, and all have a common disc key of 67C0758CF4996FEF7E88F90CC6959D66.
* Kiosk demos can be CD-ROM, DVD-ROM, or BD-ROM.
* Preproduction discs that are pressed BD-ROMs ([https://redump.info/disc/55522/ such as from some press kits]) should be dumped the same way as retail PS3 discs.

==Dumping with a PC Blu-ray drive==
If you do not have a compatible PS3 console or you are submitting a verification, you can skip the key extraction step and dump PS3 discs on a computer like normal Blu-ray discs.

# Use a [[Optical_Disc_Drive_Compatibility:_PlayStation_3_%26_4|compatible Blu-ray drive]].
# Follow the [[Disc Dumping Guide (MPF)]] (Windows) or the [[Dumping Guide (redumper_CLI)|CLI Dumping Guide]] (Windows, macOS, Linux).
# Submit the PS3 dump via the forum as usual (we recommend using MPF.Check on the redumper output files if you did not use MPF to dump).

This will dump the ISO and is acceptable for Redump, but will not be able to dump the key or create an IRD. See the below sections for dumping methods that also get the key.

'''Note''': PS3 keys are not stored in Redump, but it is recommended to back them up for personal use.

==Dumping with a PS3 Console + Custom Firmware (CFW)==
Buy a compatible PS3 Console model[https://www.psx-place.com/threads/4-85-flash-writer-released-cfw-ps3-models-only-now-go-from-4-85-ofw-to-4-85-hfw-to-a-4-85-cfw.26209/]. Early PS3 Slims and all PS3 Fats are compatible, newer PS3 slims and PS3 Super Slims are incompatible:
* Fat (all Fat models manufactured are compatible):
** CECH A01 NAND
** CECH B NAND
** CECH C NAND
** CECH E NAND
** CECH G NAND
** CECH H NOR
** CECH J NOR
** CECH K NOR
** CECH L NOR
** CECH M NOR
** CECH P NOR
** CECH Q NOR
* Slim:
** CECH-20XX
** CECH-21XX
** CECH-25XX (less compatible, best to avoid)

===Method 1: ManaGunZ===
This is the simplest method, but if you have any issues/bugs, you might want to try Method 2 (MultiMAN).

'''Setup:'''
* Install Evilnat CFW [https://www.youtube.com/watch?v=suM4dUAYUPE instructions here] (use 3.56-4.89 CFW if possible). CFW is a strict requirement, HEN hacks don't provide enough access to dump metadata.
* If you have 4.90 (or newer) CFW, you an install Rebug Toolbox ([https://store.brewology.com/ahomebrew.php?brewid=308 download]) and enable the QA toggle to be able to downgrade to 4.89 ([https://youtu.be/WoMsVT_ewW4?t=377 instructions here]). This is because the official ManaGunZ releases only support up to 4.89
* [https://github.com/Zarh/ManaGunZ/releases Download] and install ManaGunZ nightly (installation process is a straightforward launch of a .pkg file off a USB thumbstick)
* This fork supports PS3 Firmware 4.90/4.91: [https://github.com/RobbedColek/ManaGunZ/releases]
* This fork supports PS3 Firmware 4.92: [https://github.com/SashaPrawn/ManaGunZ/releases]

'''Dumping .iso and metadata:'''
* Boot your PS3 and once you get to the CFW menu, then insert the disc you wish to dump
* Launch ManaGunZ
* Select the game to dump under PS3 section
* Press Triangle to open the Game Menu
* Press '''Dump encrypted Blu-Ray disc'''
* Press '''Generate GetKey dump''' to dump metadata ('disc.pic' and 'getkey.log' files will be created)
* Transfer generated ISO and metadata files to PC with a method of your liking (FTP or USB stick)

'''Notes:'''
* Be sure to enable logging (at the main ManaGunZ screen press Start button to enter '''Settings''' menu; under '''Global settings''' enable '''Show logs''' option). This way you will be able to see a detailed live report on read errors if the application encounters any.
* It's not necessary to exit ManaGunZ after each dumping instance. The application will automatically update its state to accommodate for a new inserted disc.
* If you want to create an IRD file, then dump the disc via '''Dump decrypted Blu-Ray disc'''. The IRD file will be created at the last stage of the dumping process.
* [https://youtu.be/TfS53WfEqr0 Video showcase of a dumping process using ManaGunZ]

===Method 2: MultiMAN===
'''Setup:'''
* Install the latest Rebug CFW [https://www.youtube.com/watch?v=Eckd06nFReY instructions here] (use 3.56 CFW or higher).
* [https://github.com/Joonie86/Rebug-Toolbox/releases Download Rebug Toolbox].
* [https://store.brewology.com/ahomebrew.php?brewid=24 Download MultiMAN] (4.85.01).
* [https://archive.org/download/GetKeyR2GameOS.7z/GetKey-r2-GameOS.7z GetKey r2].
* If the PS3 is running a Cobra CFW and up-to-date multiMAN, you have to select from the XMMB menu mmCM → 'Switch to multiMAN mode' to make the the option 'Enable Direct Disc Access' appear in the start menu. Otherwise, the ISO that you create will be incorrect (decrypted).

'''Dumping .iso:'''
* In XMMB display mode, go to multiMAN → File Manager / mmOS.
* In the Start Menu icon (look at the MultiMAN icon in the bottom-left of the screen and click it), and select 'Enable Direct Disc Access'.
** If this option doesn't show up, go back to the XMMB display mode, and go to multiMAN → Switch to multiMan Mode.
** You will have to select 'Enable Direct Disc Access' for each dump. The system will not remember this option.
* Double-click the Games icon to switch back to XMMB display mode. In the multiMAN column, select 'Refresh'.
* Now go to the Video column. It should now show a BD/DVD entry. Go to it, and select the 'Create ISO' option.
* You can now copy the ISO to your preferred destination. For the best speeds, select the internal HDD.
* Once it is dumped, you can use File Manager to copy/paste the ISO from the PS3ISO folder to your USB drive.
* If your destination is FAT, >4GB ISOs that are split into segments have to be joined using PS3 ISO Tools[https://www.psx-place.com/threads/ps3-iso-tools-has-been-updated-to-v2-2-by-rudi-rastelli.3255/][https://archive.org/details/ps3-iso-tools-v2.2] or by using the 'copy /b' command on CMD.

'''Metadata dumping:'''
* Launch the Toolbox PKG app from the PS3 XMB. Once you are inside, move to the right over the options until the "Utilities" icon options displays. Then go down till you spot the following options:

1. "'''Dump eid root key''' (dump eid root key at dev_hdd0/game/RBGTLBOX2/USRDIR/eid_root_key)". Once you push it, the console will create a file called "eid_root_key" on the mentioned route. NOTE: the eid_root_key is console specific so can be reused.

Next, get a copy of the eid_root_key file:
:* Transfer to your computer via FTP: You can FTP into your console to copy the eid_root_key to your computer.
:* Transfer to your thumb drive via the console: Use MultiMAN File Manager or any tool to browse the PS3 file system to get inside the RBGTLBOX2 folder. Make sure you have a USB drive connected to the PS3. Copy the Eid Root Key and paste it to the USB drive (should be something like /dev_usb000).

2. "'''Export Flash to File''' (Backup your current NOR/NAND flash to /dev_usb000)". As soon as you enter the option, the system will ask you to "Please insert a USB drive (/dev_usb000) with at least 256mb free and try again!". Make sure you have a USB drive (format to Fat32 format - if your flash drive is bigger than 32gb you'll need to partition it) connected to the correct USB port (the right-most USB port). Try till you hit the correct port and the dumping process will start. NOTE: the NOR/NAND flash backup is console specific so can be reused.

* If everything was done correctly, once you pop the USB into a computer you should have two files: "''eid_root_key''" and something like this "''20181219-130200-FLASH-NOR-FW.81''" (The FW numbers depends on your firmware, in my case, i did it with FW 4.81).
* Fire up a hex editor app. We will use [https://mh-nexus.de/en/hxd/ HxD] for example.
* Once HxD is launched, go to "Open" and search for your NOR/NAND dump file. Open it.
* Once is loaded, hit CTRL+G and type in "303A0" if you're on NOR or "81BA0" if on NAND. (Note: If you didnt understand this, just write and search "303A0", when you start hex-editing the file, you are on NOR)
*At the left column, you should see the Offsets are displayed and the one we were looking, 0x00303A0 (for NOR in this case), will be there. Copy the 0x30 bytes from that offset and paste them into a new file AKA mark the 0x00303A0, 0x00303B0 and 0x00303C0 lines from "00" to "0F" values and copy them (CTRL+C). Go to File → New and a clean sheet will open. Paste (CTRL+V) the content and keep it opened.

''' This would be a visual example of what are you looking for. Mind you only need to search and copy the NOR bytes or the NAND bytes, not both:'''
{| class="wikitable"
|-
! NOR: 0x00303A0 - 0x00303CF
|-
|
<pre>Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

000303A0 8B D7 1B A0 C3 DA 4B BE B3 72 AE 61 78 90 31 1F ‹×. ÃÚK¾³r®ax.1.
000303B0 2E CD F1 92 28 8E 17 AD 6A 9C D5 8A 8E 17 86 39 .Íñ’(Ž..jœÕŠŽ.†9
000303C0 C8 0A F7 9B 92 D8 3A A8 92 60 73 6A 5E 12 2A 94 È.÷›’Ø:¨’`sj^.*”</pre>
|-
|}

{| class="wikitable"
|-
! NAND: 0x0081BA0 - 0x0081BCF
|-
|
<pre>Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00081BA0 40 9F 75 39 22 96 C2 12 A2 9C BC CF 53 99 73 40 @Ÿu9"–Â.¢œ¼ÏS™s@
00081BB0 5D AD A7 F6 26 6E 50 35 55 A8 8A B9 24 A1 F5 35 ].§ö&nP5U¨Š¹$¡õ5
00081BC0 BC 3B 7A 88 17 75 9C 44 A9 2D 4B E0 8B 80 92 E7 ¼;zˆ.uœD©-Kà‹€’ç</pre>
|-
|}

* Now, go to "File" → "Open" and open the EID root key file. Once it is open, do CTRL+A to select all the content and copy it (CTRL+C). Go to the previous sheet we created (the one where we pasted NOR/NAND bytes) and just paste (CTRL+V), making the bytes from the eid root key appear under the NOR/NAND ones. Go to "File" → "Save" and rename this file as "3Dump.bin".
* Take your "3Dump.bin" file and place it the USB drive.

'''Metadata Dumping: Using GetKey to get the Disc Key, Disc ID, and PIC'''
* Plug your USB drive (FAT32, with your 3Dump.bin on the root) into the right-most USB port (/dev_usb000/).
* From the PS3 XMB → Game → GetKey (with the game disc inserted): it'll run and exit back to XMB.
* It creates two files on the root of the USB drive: 'disc.pic' and 'getkey.log'.
* The 'getkey.log' text file will contain the disc_key, disc_id, and PIC. If anything went wrong when you originally created your '3Dump.bin' or extracting the data, the "getkey.log" will contain a WARNING message saying the process failed.
* Make sure to include the 'disc.pic' and 'getkey.log' when submitting your dumps.

==Dumping with a PC and an external PS3 Blu-ray drive==
===Tools===
'''Hardware'''
* 3k3y Ripper Device [https://www.modchipcentral.com/store/product.php?productid=17982].
* Sony PS3 Blu-ray drive with sector 2 zeroing[https://www.ebay.com/itm/252061696576].
* Sony PS3 OEM Power Cable[https://www.ebay.com/itm/324188388358] (these sometimes come with PS3 OEM drives, but not always).
* Power adapter. Search "UGREEN USB to IDE Converter, USB 3.0 to IDE" on Amazon - even though you don't need to convert IDE to anything, it's still a great power adapter for feeding power to your Blu-ray drive.
'''Software'''
* [https://archive.org/download/IsoToolsV1.34.9.7z/IsoTools-v1.34.9.7z IsoTools]
* [https://archive.org/download/GetkeyFrom3k3yR1.7z/GetkeyFrom3k3y-r1.7z GetKeyFrom3k3y]
* [https://archive.org/download/dvdtoimg_v1_01.7z/dvdtoimg_v1_01.7z DVDToImg]

===First-time setup===
* Hardware: Your Blu-ray drive should come with a ribbon. Attach this to the 3k3y Ripper. The 3k3y Ripper should come with a USB cable, plug this in to the 3k3y Ripper and the other end into your computer. Feed your Blu-ray drive power with the UGREEN power adapter AND plug the adapter's USB cable to the computer for additional power. Your computer should detect the drive.
* Software: Install IsoTools app linked above. Unzip GetKeyFrom3k3y and DVDToImg - these two are command line apps.
* Power on your drive and hook up the USB to your computer.
* Make sure your Blu-ray drive is empty. You can eject any disc with the tiny black button on top of the 3k3y Ripper.
* Open IsoTools. You should get a warning telling you that if you press "Yes" you will no longer be able to use the drive with a PS3 console ("You've enabled the use of default keys..."). Chose "Yes". [NOTE: if you don't get this pop-up, go to Tools → Settings and uncheck and recheck "Use Default Keys", at this point you should get the pop-up.]
* See also, 3K3Y setup video here[https://www.youtube.com/watch?v=DTi73XAfbkY].

===Dumping===
* Open IsoTools app.
* Put your PS3 disc into the drive. IsoTools should recognize the disc and say something like "PS3 Game Disc: BLUS-12345, Ready". (Note 1: When you insert your PS3 disc, don't be surprised if Windows doesn't recognize it under "My Computer". Note 2: You might have to eject and reinsert the disc before IsoTools will recognize it.)
* Close IsoTools app.
* Now open up the command line and cd (change directory) to the location of the dvdtoimg.exe that you downloaded earlier, and run a command: '''dvdtoimg f gamename.iso''' (where "f" is the drive letter). Eventually, the percentage will reach "100%" and then "Process finished".
* Eject the disc.
* Reopen IsoTools app, insert the disc again, and choose "Rip". Now IsoTools will ask you where you want to save the files (an .ird and a .dec.iso). Once you click Save, IsoTools will start dumping. You can immediately "Cancel" the dump and close IsoTools.
* Move the gamename.dec.iso file to the location of GetKeyFrom3k3y.exe
* Now in the command line, cd (change directory) to the location of GetKeyFrom3k3y.exe, and run a command: '''GetKeyFrom3k3y "gamename.dec.iso" >info.txt'''
* Now you can delete the .ird and gamename.dec.iso files.

==Submit your dump==

Please review the important guidelines outlined in this forum thread regarding submission of both new discs and verifications: [https://forum.redump.info/topic/27377/read-this-how-to-submit-new-dumps-verifications/ Redump Submissions]

'''Note:''' [https://github.com/SabreTools/MPF/ MPF.Check] (UI or CLI) supports CFW PS3 dumps with getkey logs. This greatly speeds up gathering submission info and is highly recommended over the below manual steps.

The below steps are only required if you are submitting a ManaGunZ/MultiMAN/3k3y dump (and do not want to use MPF.Check).

The required information for a submission is:
* Title of the game
* Category (usually 'Game').
* Media type: either BD-25 or BD-50
* Serial on the disc and, if it's different, serial on the cover (spine)
* Version of the game. This can be found by mounting the iso file and opening the PARAM.SFO file in the PS3_Game folder in a hex editor (for example http://www.hexed.it). Look for the VERSION and '''not''' the APP_VER.
* Ringcode information (see below for more information)
* Checksums for gamename.iso
* Contents of info.txt if dumped with PC method or getkey.log if dumped on console
* Barcode(s)
* PVD

Furthermore, it's optional (but highly appreciated) to check which languages the game has. Some games either show a language selection screen at startup or in the game options. Many games will boot with different languages depending on the active language selected in the System Settings. Booting the game with each system language is necessary to identify the supported languages for these games.

===Ring information===
The ring information can be found on the 'bottom' of the disc at printed/moulded on or near the inner plastic part of the disc.

'''Mastering code'''

For European discs, this is usually in the following format:

A0101XXXXXX-A511 X000

American discs have a code in the format:
BPSS-XXXXXXXX XX

Asian discs have a code in the format:
[Serial] X

''Don't forget the tab!''

'''Mastering SID'''

Mastering SID is printed on the disc (don't confuse it with the Mould SID which is pressed/moulded into the plastic). It is always in the format:

IFPI LXXX

'''Toolstamp'''

The toolstamp is a very small piece of text usually at the end of the Mastering Code. It's a few characters long. Note that the text is often mirrored, so make sure you don't copy the code backwards.

'''Mould SID'''

The Mould SID not printed on the back of the disc, but moulded/pressed in the plastic at the absolute center of the disc. The Mould SID is really small and can be read from the front/labelside (instead of the back) of the disc. It's always in the format:

IFPI XXXX

===Retrieving PVD===
Depending on the media and/or your version of IsoBuster (free version usually), you may not be able to view sectors and obtain the PVD with IsoBuster. The PVD is not absolutely required for your submission. Alternatively, you can locate it using a hex editor / hex viewer program such as Hex Workshop or HxD.

* IsoBuster option
** Open IsoBuster app.
** File → Open Image File. Select the .iso you created to open it.
** In the left hand side of the app, right click on "Session 1" → Sector View.
** In the box at the top input "16".
** Scoll down and highlight lines 0320 - 0370 → click on the notepad-looking icon (when your mouse hovers over it, it says "Copy").
** Paste this info into your submission, it's the "PVD" info. Here's an example of how it should look:
0320 : 20 20 20 20 20 20 20 20 20 20 20 20 20 32 30 31 201
0330 : 30 30 35 31 32 31 32 31 39 33 35 30 30 00 30 30 0051212193500.00
0340 : 30 30 30 30 30 30 30 30 30 30 30 30 30 30 00 30 00000000000000.0
0350 : 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 00 000000000000000.
0360 : 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 0000000000000000
0370 : 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

* Hex editor option
** Open up the .iso file with your hex editor of choice.
** Locate the sections 00008320 through 00008370 and copy this information.
** Past the info into your submission file.

===Template===
You can copy/paste the below template to submit a dump on the forum:

[b]Media:[/b]
[b]Category:[/b] Games
[b]Title:[/b]
[b]Region:[/b]
[b]Languages:[/b]

[b]Serial:[/b]

Ring:
[b]Mastering Code:[/b]
[b]Mastering SID Code:[/b]
[b]Toolstamp:[/b]
[b]Mould SID Code:[/b]

[b]Barcode:[/b]

[b]Comments:[/b]

[b]Version:[/b]
[b]Edition:[/b]

[b]PVD:[/b]

[b]Disc Key:[/b]
[b]Disc ID:[/b]
[b]PIC:[/b]

[b]Size:[/b]
[b]CRC-32:[/b]
[b]MD5:[/b]
[b]SHA1:[/b]

[[Category:Dumping Guides]]

Nintendo Wii U Dumping Guide

2026-07-10T18:04:07Z

Darksabre76: Remove mention of game.key for submission

This guide is an early work in progress.
==Retail Discs==
===Tools===
* Wii U console with a network connection
** Networking only required for soft-modding

* 32GB+ SD Card formatted to FAT32.
** (Optional) Additional 32GB+ USB storage device formatted to FAT32 or NTFS.
** Higher sizes are recommended as all WUDs are 25GB. Please note that some external devices require a Y-Cable or external power, as the Wii U's USB ports don't supply much power.

* [https://github.com/FIX94/wudump/releases/latest WUDump] or [https://github.com/wiiu-env/wudd/releases/latest WUDD] (Wii U Disc Dumper), to dump the actual game.
** If you use WUDD, you will need a tool that can calculate hashes such as [http://www.slavasoft.com/hashcalc/ Hashcalc] or [https://github.com/namazso/OpenHashTab/releases OpenHashTab].

===First Time Setup===
* Install the homebrew channel by following this [https://wiiu.hacks.guide/#/ guide] (or alternatively you can just download the [https://github.com/dimok789/homebrew_launcher/releases homebrew channel], place the wiiu folder on your SD Root and run it one-off using the browser exploit)
'''Option 1 - Setting up WUDump'''
* Download WUDump from above, and place it in SD:/wiiu/apps/wudump/ (you will need to make the folder 'wudump')
'''Option 2 - Setting up WUDD'''
* Download WUDD from above. If you installed Tiramisu on your Wii U, download the .rpx release. The .wuhb release can only be used with Aroma.
* Copy the wiiu folder to the root of your SD Card

===Dumping===
'''Option 1 - Dumping with WUDump'''
* Run the Homebrew Launcher.
* Once in the Homebrew launcher, select wudump, then hit Load.
* Press the appropriate button for what device you are dumping to (FAT32 USB, NTFS USB, or FAT32 SD)
* Once ready, the program will inform you to insert the disc; if you already have the disc inserted, simply eject and re-insert.

* This process takes a long time (1-2 hours!), so go get lunch and wait.

'''Option 2 - Dumping with WUDD'''
* Load WUDD through the Homebrew Launcher (Tiramisu) or the Wii U Menu (Aroma)
* Insert the disc and select which device you would like to dump to (FAT32 SD or NTFS USB) and then select Dump as WUD.
* If you dumped to a FAT32 device, the WUD will be split into 12 .part files that you need to combine. To do this:
** Copy the folder containing the part files to a file system with large file support (eg NTFS)
** Open a command prompt there and then copy and run the following command
(wudump) copy /b game_part1.wud + game_part2.wud + game_part3.wud + game_part4.wud + game_part5.wud + game_part6.wud + game_part7.wud + game_part8.wud + game_part9.wud + game_part10.wud + game_part11.wud + game_part12.wud game.wud
(WUDD) copy /b game.wud.part1 + game.wud.part2 + game.wud.part3 + game.wud.part4 + game.wud.part5 + game.wud.part6 + game.wud.part7 + game.wud.part8 + game.wud.part9 + game.wud.part10 + game.wud.part11 + game.wud.part12 game.wud

* You should now have two files, game.key and the full game.wud (the .part files are not needed anymore and can be deleted)
* Run Hashcalc, press the '...' button and select the game.wud file.
* Tick the MD5, SHA-1 and CRC32 boxes then click 'calculate'
* Open notepad, copy the template below and replace the data in <Angled Brackets> with the version of WUDD used and the data from Hashcalc.
* (If a new disc) Using a hex editor, open game.wud and copy the Internal Serial into "Comments".
Dumped with WUDD - Wii U Disc Dumper <Version of WUDD used>
MD5: <Paste the MD5 from Hashcalc here>
SHA1: <Paste the SHA1 from Hashcalc here>
CRC32: <Paste the CRC32 from Hashcalc here>
Internal Serial: <Paste the Internal Serial from your disc image here>
* Save the file as game.txt

==Development Discs (CAT-R)==
CAT-Rs can be dumped two ways:
*[[Disc Dumping Guide (MPF)]] with a Blu-Ray drive. MediaTek-based and Pioneer-based PC bluray drives have been confirmed as able to dump CAT-R discs. It's highly likely other drive models work as well (but have not been confirmed).
*Using the regular homebrew dumping methods, but on CAT-I/CAT-R/CAT-DEV hardware.

==Submitting Info to Redump==
Copy the CRC32 from your game.txt file, open the [https://redump.info/ Redump homepage] and paste the hash into the Quick search field in the upper right.
* If the search returns an existing entry on Redump, your dump is a verification and should be submitted on the [https://forum.redump.info/forum/16/verifications/ "Verifications" forum].
* If there is no existing entry for this hash, submit your dump on the [https://forum.redump.info/forum/11/dumps/ "New Dumps" forum]. '''Discs dumped with WUDD are currently only accepted for verifications.'''
* If you have dumper rights you should submit the dumpinfo using the [https://redump.info/newdisc/ New Disc form].
Please review the important guidelines outlined in this forum thread regarding submission of both new discs and verifications: [https://forum.redump.info/topic/27377/read-this-how-to-submit-new-dumps-verifications/ Redump Submissions]

'''Notes using the New Disc form''':
*In the New Disc form, put all ring information in the 'Ring' field like you would using the template below (a moderator will format them properly).
*Language Select and Case Serial information can go into the 'Comments' field.

[quote]
Note: paste the contents of the WUDump / WUDD game.txt or here.
[/quote]

[b]Game Information:[/b]

[b]Game Title:[/b]
[b]Region:[/b] Europe / USA / Japan / UK / Scandinavia / Australia
[b]Languages:[/b] English, German, French, Spanish, Italian, Dutch, Swedish, Norwegian, Danish, etc...
[b]Language Select:[/b] Language select via BIOS system settings / Language select screen at startup
[b]Disc Serial:[/b]
[b]Edition:[/b] Original / Demo / Starter Pack / Nintendo Selects
[b]Case Barcode:[/b]
[b]Case Serial:[/b]
[b]Size:[/b] 25.025.314.816

[b]Ring Information:[/b]

[b]Mastering Code (back):[/b]
[b]Mastering SID Code (back):[/b]
[b]Mould SID Code (back):[/b] IFPI XXXX
[b]Additional Mould Text (back):[/b]
[b]Toolstamp (back):[/b]
[b]Mould SID Code (front):[/b] IFPI XXXX
[b]Additional Mould Text (front):[/b]

[b]Game Key:[/b] Attached

'''Note:''' Don't forget to attach the game.key file to the post!

* '''Ring code info:''' [https://web.archive.org/web/20240514073908/https://media.discordapp.net/attachments/418896391092437000/965186288280023120/ringcodes-wiiu-back.jpg?ex=6643db87&is=66428a07&hm=ebcbfcf5876c3171e5f1f4a41418922a8cdf7fb8d74415e709e3b854afb2338b&=&format=webp&width=610&height=616 useful reference image]

[[Category:Dumping Guides]]

CodeLok / CopyLok

2026-07-10T15:35:28Z

Darksabre76: Update ZZ00 link

CopyLok and CodeLok was names used interchangeably during the life of the DRM. Its sometimes also known as CopyLock but this more commonly refers to [https://en.wikipedia.org/wiki/Rob_Northen_copylock a different DRM].

Comes both with or without rings. A bug in the Plextor firmware means any dump of either version made using a Plextor and any tool is likely to be bad. Incorrectly reporting the total number of errors.

For example, when dumping https://redump.info/disc/53929/ with ringless Copylok using either DIC or redumper and a Plextor drive, the error count is incorrectly reported as 1516, exactly double the correct 758 errors.

An incorrect _c2Error log looks as follows:
<code> 
LBA[002312, 0x00908] Detected C2 error 380 bit 
LBA[002313, 0x00909] Detected C2 error 20 bit</code>

A correct _c2Error log looks as follows:
<code> 
LBA[002312, 0x00908] Detected C2 error 300 bit 
LBA[002322, 0x00912] Detected C2 error 300 bit</code>

These discs can be correctly dumped using a non-Plextor drive and any of the following tools:
* DIC (using an ASUS or compatible firmware drive)
* redumper (Same as above)

Ringed Copylok meanwhile is supposed to have double errors (for example https://redump.info/disc/107930/). A correct Redumper dump of these will look like this.
<code> 
[LBA: 2316] C2 error (bits: 1354) 
[LBA: 2317] C2 error (bits: 1022)</code>

Only a handfull of drives are known to be able of handling this variation of the DRM. Most, including Plextor and Redump compatible Asus drives will instead have these kind of errors in their logs.
<code> 
LBA: 2315] subcode desync (shift: -1) 
[LBA: 2316] C2 error (bits: 440) 
[LBA: 2317] C2 error (bits: 2088) 
[LBA: 2326] C2 error (bits: 15 
[LBA: 2327] C2 error (bits: 1481 
[LBA: 2328] C2 error (bits: 1956 
[LBA: 2342] C2 error (bits: 1022 
[LBA: 2329] C2 error (bits: 308 
[LBA: 2331] subcode desync (shift: -2) 
[LBA: 2342] C2 error (bits: 608)</code>

Currently, These discs have to be dumped using:
* Redumper using the <code>--force-split</code> parameter and a TS-H353C/SH-D163C drive running [[Optical_Disc_Drive_Compatibility:_CD|custom ZZ00 firmware]]

[[Category:Copy Protection Guides| ]]