Put your 'wad' programs in there ( a wad-program always ends with '.wad' note: WAD-installer ain't a '.wad' file!!! You have to put wad-installer. Elf or.dol in the root of your sd card It depends on what firmware you have on your WII!!! - use wad-installer.elf if you have firmware 3.3 - use wad-installer.dol if you have firmware 3.4. Hey Guys Get Ready To Blow Your Wad Again To Get The Wads You Want To Email At renegade763@gmail.com or gamemodder666@gmail.com Or Leave A Comment With What.
Backup Launchers > cIOS InstallationThe cIOS (custom IOS) is a custom piece of software that is used by some applications that work with unofficial content. By installing it, you can for example use Backup Loaders and install unofficial channels to your Wii menu. Every cIOS uses an official IOS by Nintendo as its base.
While a cIOS is installed by most people for Backup Loaders, it is also needed by a handful of other applications to work. There are many applications however that don't need a cIOS. Most of the Homebrew Applications on Wiibrew only need the Homebrew Channel.
See below Required - An SD Card (preferably non-SDHC) or USB device
- Homebrew Channel installed (must be up to date!)
- 2 cIOSs will be installed, which can be used by backup loaders and some other apps as well.
If you have no WiFi access on your Wii, follow these additional steps first. Else skip to the guide below. The WiiU uses another method to get these WADs, so if you are softmodding a WiiU (vWii), you should skip these steps regardless. Computer ---------------------- |
1. Start up NUS Downloader. If you don't have it, you can grab it on its page (or direct download link) 2. Make sure that 'Pack WAD' is enabled. 3. Using the database, navigate to the following files and press start NUS Download for each one: - IOS -> IOS56 -> v5661
- IOS -> IOS57 -> v5918
4. Open the NUS Downloader directory (the folder where you placed NUS Downloader, you can use extras -> open NUSD directory to open it easily). You will see a folder named titles. You will find two new folders in this directory: - 0000000100000038
- 0000000100000039
In each folder, there is another folder for the version you just downloaded. Open this version folder and find a WAD file: - 0000000100000038 -> 5661 -> IOS56-64-v5661.wad
- 0000000100000039 -> 5918 -> IOS57-64-v5918.wad
Copy both WAD files to the root of the SD card (or your USB device if you don't have an SD card). Optionally, if you wish to verify that the downloaded WADs are correct, use a checksum tool (like fciv) to verify: - IOS56
- MD5 = 5cdee6593cf0dacc18cf300b12166fde
- SHA1 = 597c360e521ccd3062fd9c38c5369e691344d5e2
- IOS57
- MD5 = ac8bbbea38f29e8d8959badb3badf18e
- SHA1 = b8fd4efbb6d7ae2f4e9328b3082901f5981701b1
Guide Computer ---------------------- |
1. Start off by downloading the cIOS Installer (make sure to download the correct one):
Inside the zip will be an apps folder. Extract this folder to your SD card (merge with existing apps folder if needed). Your SD card (or USB) should look like this: SD
|- IOS56-64-v5661.wad (optionally, for Wii offline guide)
|- IOS57-64-v5918.wad (optionally, for Wii offline guide)
|- /apps
|- /d2x-cios-installer
Wii ---------------------- |
2. Insert you SD card (or USB) into the Wii. Now locate the d2x cIOS installer and run it.
3. Wait for the app to load. Read the text on the welcome screen (if it interests you) and press A to continue.
4. You will now see the main configuration screen. There are many different configurations you can make when installing cIOSs. This guide merely shows our own recommendations, based on the experience of the general community. They should work fine for 99% of all cases. - cIOS 249 base 56 v10 beta52
- cIOS 250 base 57 v10 beta52
- Your cursor ( > ) will be on the cIOS d2x Version. Change the version to v10 beta52 using the D-PAD (left/right).
- Move down, and change the IOS Base to 56.
- Move down again, and change the IOS slot to 249.
- In some cases it may warn you that the current (c)IOS or IOS STUB will be overwritten. You can ignore this warning.
- Move down, and change the cIOS revision to 65535.
- This revision is only used by the Wii when checking updates. It is set to the highest version to prevent a system update from overriding it with a non-functional official IOS.
- This option does not appear on the WiiU installer.
(note: in the screenshot below; the version is set to beta53-alt; we recommend using beta52 instead)
You are now ready to install, so press A to continue. You will land on an overview with the available cIOS slots. The slot you just selected should be blinking. Several other slots may be highlighted in red or purple, depending on your console and possible previous softmods.
Wait for the progress to complete. It may take a while, especially for the online installation. Once it finishes, you will land on another IOS overview screen. Your freshly installed cIOS should be highlighted in a green color. On the WiiU version, you will get a simple confirmation message instead. Press the A button to go back to the configuration screen. Next, you want to configure the second cIOS. This time, use the following settings: - d2x version: v10 beta52
- cIOS base: 57
- cIOS slot: 250.
- cIOS revision: 65535
Again, press A to install it and wait for the process to finish. Once everything is installed, press B to exit the application.
You are now able to run any backup loader you want! Enjoy! We recommend you to use a USB loader. USB loaders do not require DVD burning and have much better speeds and interfaces.
You just need an up-to-date Homebrew Channel installed, nothing else.
But what about the Trucha Bug Restorer / Dop-Mii / IOS236? Those are outdated hacks, and using/installing them serves no purpose.
When should I follow the steps under 'Offline NUS Downloads'? Those steps are for people who are softmodding a regular Wii and don't have WiFi on that console. The steps essentially pre-download some required files which are otherwise downloaded by the console itself. These files can not be included with the installer for legal reasons.
People softmodding a WiiU (vWii) can skip these steps regardless, since the installer will extract them from the console itself.
Can I use other cIOS configurations as the one in this guide? Yes! As stated above, the configurations of this guide are recommendations based on various tests by the community. They should work for the majority of cases. But you are free to install different cIOSs in different slots. We only recommend to do this if our configurations don't work, though. If you do install your own cIOSs, make sure to select a slot above 200. Also don't use slot 254 (which is BootMii IOS).
What is the IOS base for? Since building an IOS from scratch is not very easy; the cIOSs that we install merely apply some patches to the existing IOSs provided by Nintendo for the Wii. The IOS base determines what IOS the patches are applied to.
What is the IOS slot for? The Wii is able to store multiple IOSs on its internal memory, with each IOS occupying its own slot. The slot is merely a number that tells the system where to load the IOS from. For example, IOS56 will be found in IOS slot 56. In order to avoid overriding the default IOSs that are installed on the system, cIOSs (which are custom IOS and thus occupy the same slots), are installed in slots above 200, which are empty or stubs by default.
What is the IOS revision for? Each IOS has an internal version number. When an update needs to be done to an IOS, the version number is increased. The system, when it detects a newer version for an IOS, will prompt the user to start a system update. The revision of an installed cIOS is thus usually maxed out to prevent the system from overriding it with a non-functional official version.
What is NAND Emulation? NAND emulation is an optional feature. It allows you to load things like virtual console games from a fake NAND (the internal memory of the console). This fake NAND (often called EmuNAND, Emulated NAND) is stored on the SD card rather than the console itself.
USB Loaders such as USB Loader GX and Wiiflow can create an EmuNAND and use it to launch titles.
What is the 'Current IOS' listed on the bottom of the installer? This IOS is the one used to run the installer itself (all applications need an IOS to run). It has nothing to do with the cIOSs that are installed. Do I need to install a cIOS to use Nintendont (GameCube Backup Loader)?Nope. The cIOS is not used for GameCube backups. It is needed for Wii backups, though, and some USB loaders may need it to run.
|
|
- This article is about Wii software packaging. For the data files used by Doom, see WiiDoom.
General info
The WAD file-format is a package that contains title information for the Wii, such as System Menus, IOS versions, and channels.
Piracy
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.
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 format
Installable WADs
Common format used for WAD files distributed in update partitions from Wii discs. Thanks to Segher for his source.
Start | End | Length | Description |
---|
0x00 | 0x03 | 0x04 | Header size. Always set to 0x20. |
0x04 | 0x05 | 0x02 | WAD Type. 'ib' is used for boot2 WADs, 'Is' for everything else. |
0x06 | 0x07 | 0x02 | WAD Version. Always set to zero. |
0x08 | 0x0B | 0x04 | Certificate chain size. |
0x0C | 0x0F | 0x04 | Reserved. Always set to zero. |
0x10 | 0x13 | 0x04 | Ticket size. |
0x14 | 0x17 | 0x04 | TMD size. |
0x18 | 0x1B | 0x04 | Encrypted content data size. |
0x1C | 0x1F | 0x04 | Footer size. |
0x20 | 0x3F | 0x20 | Alignment 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.
Wad Files For Wii
Backup WADs
Nintendo Wii Wads Download
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.
Start | End | Length | Description |
---|
0x00 | 0x03 | 0x04 | Header size. Always set to 0x70. |
0x04 | 0x05 | 0x02 | WAD Type. Always set to 'Bk'. |
0x06 | 0x07 | 0x02 | WAD Version. Always set to 0x01. |
0x08 | 0x0B | 0x04 | Console ID. |
0x0C | 0x0F | 0x04 | Savegame file count. Always set to zero (only used in savegames). |
0x10 | 0x13 | 0x04 | Savegame file data size. Always set to zero (only used in savegames). |
0x14 | 0x17 | 0x04 | TMD size. |
0x18 | 0x1B | 0x04 | Encrypted content data size. |
0x1C | 0x1F | 0x04 | Backup area size (total size from the start of this header to the end of the encrypted content data). |
0x20 | 0x5F | 0x40 | Included contents bitfield. |
0x60 | 0x67 | 0x08 | Title 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. |
0x68 | 0x6D | 0x06 | MAC address. Always set to zero (only used in savegames). |
0x6E | 0x6F | 0x02 | Reserved. Always set to zero. |
0x70 | 0x7F | 0x10 | Alignment 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'