Wad Files For Wii



Wii wad manager free download. Clementine Clementine is a multi-platform music player and library organizer inspired by Amarok 1.4.

This article is about Wii software packaging. For the data files used by Doom, see WiiDoom.
  • 1General info
  • 3WAD format

General info

  • Nintendo Wii WAD files are like a zip or cab file on PC that contain a full set of files for installing an.app (application, program, game). The main purpouse of Wii WAD files is to install custom made channels and cIOS, but they are also considered to be an equivalent of the ROM and ISO files majority of which are warez.
  • To create your wad file, you can use the big button on the bottom that says 'Create WAD'. You will be asked where to store the wad. Just browse to the place where you want to save it, give it a.

The WAD file-format is a package that contains title information for the Wii, such as System Menus, IOS versions, and channels.

Piracy

For

Unfortunately, WAD files are often used to distribute pirated channels (both Virtual Console and WiiWare), due to the fact that they are also used by Nintendo and therefore easy to rip from the Wii and, for some WAD files, Nintendo's servers, and easy to create installers for. Wiibrew does not in any way endorse piracy, and as such these uses of WAD files should not be discussed.

If you wish to discuss legitimate WAD files, please ensure you make clear which file you are talking about and what you will use it for, to prevent people jumping to conclusions about your intentions.

System Menu

WAD files are often installed in the Wii System Menu to appear as channels, making launching easier. If a WiiBrew app isn't installed as a channel, it can usually only be launched from the Homebrew Channel itself. WAD file creation seems to be an intricate process and tools are difficult to locate, and most are based on the .NET framework. Associated with WAD file generation are forwarders, which when loaded simply load another arbitrary application. A common technique is to use a somewhat generalized WAD that can be easily customized to then forward to another WiiBrew application stored on the SD card.

Wii System Channel WAD files exist for WiiMC, ftpii, and numerous others.

Forwarders are somewhat easier to locate, a common one being the Narolez-NForwarder, for which source exists and is easily modifiable. One WAD generation system that still appears to be active is the CRAP system that appears to be .NET based. The Wadder system also seemed to be .NET based but it appears abandoned. Although these tools are often associated with piracy, there are clearly legitimate uses for them as well.

Where To Download Wad Files For Wii

The WAD files themselves contain either still images or a collection of images to be animated, as well as sound data. In addition there is a .DOL file for the program to be run when launched.

Wad Game Files For Wii

WAD format

Installable WADs

Common format used for WAD files distributed in update partitions from Wii discs. Thanks to Segher for his source.

StartEndLengthDescription
0x000x030x04Header size. Always set to 0x20.
0x040x050x02WAD Type. 'ib' is used for boot2 WADs, 'Is' for everything else.
0x060x070x02WAD Version. Always set to zero.
0x080x0B0x04Certificate chain size.
0x0C0x0F0x04Reserved. Always set to zero.
0x100x130x04Ticket size.
0x140x170x04TMD size.
0x180x1B0x04Encrypted content data size.
0x1C0x1F0x04Footer size.
0x200x3F0x20Alignment to 0x40 bytes (padding).

Sections are stored in installable WAD files in the same order from their headers (certificate chain, ticket, TMD, content data). Each section is aligned to a 0x40-byte boundary.

The encrypted content data section is composed of content files, which are stored following the same order from the TMD content records. These are encrypted using the decrypted titlekey from the Ticket and the content index as the IV (first two bytes, followed by 14 zeroes). The SHA-1 checksum of the decrypted content must match the hash from its corresponding TMD content record. Each content is individually aligned to a 0x40-byte boundary.

The footer is an optional, unencrypted timestamp / buildstamp. It's usually the first decrypted 0x40 bytes from the first content file.

In a hex editor, the beginning of any installable WAD will be 00 00 00 20 49 73 00 00. This can be useful to extract an embedded installable WAD from an ELF binary.

Backup WADs

Format used by content.bin files to store content data from a channel copied or transferred to the SD card, which get saved to /private/wii/title/<low_tid_ascii>/content.bin.

Also used by downloadable content data stored in the SD card, which gets saved to /private/wii/data/<low_tid_ascii>/<index>.bin - in this context, <index> represents a specific content index value from a TMD content record, expressed as a 3-digit number in base 10 notation (e.g. 000.bin).

Savegames use the same exact header, albeit with different fields filled and with an entirely different structure for the rest of the file.

StartEndLengthDescription
0x000x030x04Header size. Always set to 0x70.
0x040x050x02WAD Type. Always set to 'Bk'.
0x060x070x02WAD Version. Always set to 0x01.
0x080x0B0x04Console ID.
0x0C0x0F0x04Savegame file count. Always set to zero (only used in savegames).
0x100x130x04Savegame file data size. Always set to zero (only used in savegames).
0x140x170x04TMD size.
0x180x1B0x04Encrypted content data size.
0x1C0x1F0x04Backup area size (total size from the start of this header to the end of the encrypted content data).
0x200x5F0x40Included contents bitfield.
0x600x670x08Title ID. Set to zero in backup WADs from content.bin files, set to parent title ID in DLCs (not the DLC title ID) and set to game title ID in savegames.
0x680x6D0x06MAC address. Always set to zero (only used in savegames).
0x6E0x6F0x02Reserved. Always set to zero.
0x700x7F0x10Alignment to 0x40 bytes (padding).

Sections are stored in backup WAD files in the same order from their headers (TMD, content data). Each section is aligned to a 0x40-byte boundary.

The included contents bitfield serves to determine which contents from the TMD are part of the backup WAD. Up to 512 different contents (bits) can be toggled, separated in groups of 8 contents (byte), where the LSB represents the first content from the group and the MSB represents the last content. Shared contents are usually not included. For example, the bitfield for a backup WAD that holds a TMD with 10 content records, where indexes 4 and 8 are both shared contents, would be EF 02 (11101111 00000010), followed by 62 zeroes.

The encrypted content data section is composed of content files, which are stored following the same order from the TMD content records. These are encrypted using the console-specific PRNG key and the content index as the IV (first two bytes, followed by 14 zeroes). The SHA-1 checksum of the decrypted content must match the hash from its corresponding TMD content record. Each content is individually aligned to a 0x40-byte boundary.

In a hex editor, the beginning of any backup WAD will be 00 00 00 70 42 6B 00 01. This can be useful to extract an embedded backup WAD from a bigger file (such as content.bin files).

Please note that, unlike content.bin files from channels, each <index>.bin file from transferred DLCs only holds a single encrypted content. This also means that a single bit from the entire included contents bitfield is enabled.

Retrieved from 'https://wiibrew.org/w/index.php?title=WAD_files&oldid=108739'

At some point you’ve heard of Wad Manager and probably used it to install channels. Well this tutorial is for helping you use wad manager to install .wad files on any version of the Wii. This will also help you not get the ERROR RET -2011 (or similar) messages. Here’s a rundown of what Wad Manager is and what it features.

What is wad manager? (basic rundown)

Wad files for wii

Wad manager is a homebrew application that lets you install .wad files on your hacked Wii. .Wad files are files that once installed on your wii are either in the form of channels or IOS, or cIOS titles. There are 4 types of channels that a .wad file could be:

  1. A Virtual Console game
  2. WiiWare
  3. Official Nintendo Channels (ex: Internet Channel, Wii Speak channel, etc.)
  4. A homebrew application or game

As for IOS and cIOS, those are mostly installed for a certain homebrew app/game
NOTE: I’ve made a tutorial on how to install vc games/WiiWare with Wad Manager here.

Now that you know what the Wad Manager is, i’ll explain how to set it up on your SD Card.

Setting up your SD Card

  1. First you need to download a Wad Manager (mirror)
  2. Once you download it make a folder on the root of your SD Card called: apps
  3. Go into that apps folder and make another folder called Wad Manager (or whatever you want)
  4. In that folder drag the meta.xml, icon.png, and boot.dol you got when you download the Wad Manager.
    ~At this point the homebrew channel should recognize the Wad Manager application~
  5. Now on the root of your SD Card* make a folder called: WAD
  6. In the WAD folder you will put your .wad files you want to install

*NOTE: If you downloaded version 1.4 of wad manager you can choose to put your WAD files on a USB.

Nes Wads For Wii

Installing .wad files correctly (no more errors!)

Wad Files For Wii Download

Now if you’ve tried to install your .wad files but always get the annoying error messages here is the tutorial on how to install them correctly:

  1. Put the contents on your SD Card as it is in the .rar just drag all to SD Card.
  2. Run CMDVDX34 using HBC (Downgrade IOS35 and exit the app)
  3. Install IOS35.wad using Wad Manager (any version) (if it fails, it’s already installed, don’t worry continue)
  4. Then run Wad Manager (IOS35 Version) and install the CIOS7.wad
  5. Your Done!
  6. Now you can run the CIOS rev installer update and start enjoying your installed .wad files.
  7. Download latest CIOS rev installer (mirror)