This homebrew lets you install the various D2X cIOSX without going through modmii and without having to do the various steps needed to install the betas. Image unavailable (removed by its host) Features
Lets you install d2x cIOS v4, v5 and v6.
Lets you install d2x beta cIOS or "hybrid" cIOS made up of different modules (ES, EHCI, DIPP...).
Available base IOS: IOS37 v5662, IOS38 v4123, IOS53 v5662, IOS55 v5662, IOS56 v5661, IOS57 v5918, IOS58 v6175.
Ability to choose the install slot. (from 200 to 255)
Ability to install Online and Offline.
Support for .wad files at the root of SD/USB devices.
Support for SD/USB devices.
Support for the HW_AHBPROT flag. (enabled by default)
Support for comments in ciosmaps.xml
Support for classic controllers, Wiimotes and GameCube controllers.
Support for the <arg>--ios=XXX</arg> argument in meta.xml to automatically configure which IOS to use (only active when AHBPROT is absent).
Support for the <arg>--remove-cache</arg> argument in meta.xml to delete the "nus" directory when exiting d2x cIOS Installer.
Ability to choose the cIOS revision from among relevant values.
Ability to install several cIOS at once.
Ability to save/load an installation's configuration.
Ability to generate a NUS script suited to the installation's configuration.
Ability to free up a slot >=200
Changelog
- better handling of the installation queue.
- better handling of warning messages.
- fixed the no_ios_reload and release_date tags in meta.xml.
- support for external cIOS working again.
- faster return to the homebrew channel.
Installer v3:
- Removed support for d2x cIOS v3
- Added the ES_Version patch for AHBPROT (Thx R2-D2199)
- Fixed the bug related to AHBPROT in offline mode (Thx Davebaol)
- New summary screen giving an overview of the installation's configuration
- New log screen giving the installation results
- Choice of cIOS revision from among the most relevant values
- Module for saving an installation's configuration
- Module for loading an installation's configuration via a ciosconf.cfg file to be placed in the d2x cIOS installer directory
- Module for saving the nus script needed to download the files required for offline mode
- Various fixes
- The <arg>--ios=XXX</arg> argument in meta.xml is now only active when AHBPROT is absent
Installer v2.2:
- Filtered the list of candidate "Working IOS" to exclude STUB(s) (including fake STUBs)
- Default cIOS install slot set to 249.
- Default d2x cIOS version set to the latest final version.
- Attempted fix for screen flickering.
- Minor display reorganization.
- Removed support for the checkbox (d2x=D2X and app=APP)
- Added support for comments in the ciosmaps.xml file.
- Added support for DevkitPro's Portlibs directory in the makefile. (Thx Rodries)
- post-build.bat script to update meta.xml after compilation.
- Support for the <arg>--remove-cache</arg> argument in meta.xml to delete the "nus" directory when exiting d2x cIOS Installer.
- Support for the HW_AHBPROT flag. (disabled by default)
--> you need to uncomment the <no_ios_reload /> tag in the meta.xml file to enable it, knowing that it can also be used automatically by using for example the argument --ios=0 or --ios=AHBPROT
--> to use AHBPROT, select IOS58+AHBPROT on the "Working IOS" screen
Installer v2.1:
- New icon (Thanks WiiD)
- Support for .wad files at the root of SD/USB devices for offline installation.
- Set up the GoogleCode project!
Installer v2.0:
- New GUI.
- Fixed minor bugs.
- Complete rewrite of the code.
- Added support for USB devices.
- Fixed the warning message reporting an occupied slot.
- Updated the list of occupied slots after a successful cIOS installation.
- Possible return to the IOS selection screen to use in case of a non-critical error.
- Support for the <arg>--ios=XXX</arg> argument in meta.xml to automatically configure which IOS to use.
- Ability to add cIOS to the list without updating d2x cIOS Installer. Just put the files (.app modules + ciosmaps.xml) next to d2x cIOS Installer's boot.dol for it to take new cIOS into account. This way, you can build "hybrid" cIOS with very specific module versions (DIPP, EHCI, ES, FAT, FFSP, MLOAD, SDHC, USB).
v1.3:
- Replaced the d2x cIOS v6 beta1 with the final d2x cIOS v6.
- Added support for the Korean Common Key on all bases (except IOS38) for v6. (Thx Damysteryman)
- Extended Korean Common Key support to cIOS versions 3, 4 and 5.
v1.2:
- Added d2x cIOS v5 final and v6 beta1.
- Implemented the identification method for the new cIOS (on V4, V5 and v6beta1)
V1.1
- replaced the d2x cIOS v4 beta 4 with the d2x cIOS v4
V.1
- Lets you install the D2X v3 (rev21003) and v4 (rev21004) cIOS.
- Available base IOS: IOS37 v5662, IOS38 v4123, IOS53 v5662, IOS55 v5662, IOS56 v5661, IOS57 v5918, IOS58 v6175.
- Ability to choose the install slot.
- Ability to install Online and Offline.
- Support for classic controllers (untested), Wiimotes and GameCube controllers.
Adding a cIOS to the installer:
Official websiteSince d2x cIOS Installer v2.0, it's possible to add cIOS without having to compile the sources!
This new feature can be very useful for installing beta versions of cIOS or even creating "hybrid" cIOS, such as for example d2x cIOS vX but with the EHCI module from vY for testing purposes.
For this, you won't really need programming knowledge, other than knowing how to read an .xml file and rename folders.
So to add a cIOS to the list, in addition to those already present, you need to grab the .app modules of the cIOS you want to build (found in the ModMii sources), place them in the right spot on the SD/USB device and edit the file CIOSMAPS.xml
You'll notice that a sampleCIOSMAPS.xml file is provided, which is actually the "map" of the d2x cIOS v6 (a sort of installation guide for d2x cIOS Installer).
Once opened with an xml editor, it looks scary but only a few lines matter to us:
- <ciosgroup name="D2X v6" version="21006" basescount="7">
Here the name tag shows the name that will appear on the cIOS Installer, and version the final revision of the cIOS (max = 65535). So you can edit these 2 tags as you see fit.
- Then go into the spoiler for the base you want to install, for example base 37, I open the spoiler <base ios="37" version="5662" contentscount="22" modulescount="7">
- Inside, the only lines that matter to us are the ones containing module tags such as for example: <content id="0x26" module="EHCI21006" tmdmoduleid="3"/>.
If I want to change the EHCI module, all I have to do is replace its name with the name of the one I want to put in.
If you put in several new cIOS, don't forget to change the line <ciosmaps ciosgroupscount="1">
- Once you've made the changes, save and rename the file sampleCIOSMAPS.xml to CIOSMAPS.xml
- Now let's get to the modules (.app files). The directory tree used to store the modules mainly depends on the name attribute of the relevant ciosgroup tag in the CIOSMAPS.xml.
For example, for a cIOS for whichyou'll need to store its modules (.app files) in the directoryCode: Select all
<ciosgroup name="D2X vX beta1" ...putting a space in the name attribute necessarily results in a new directoryCode: Select all
<répertoire de d2x cIOS installer>\D2X\vX\beta1\
If name="D2XvXbeta1" then the directory will be <d2x cIOS installer directory>\D2XvXbeta1\
- Check that the module names match those you put in the .xml file
- That's it, it's done. d2x cIOS Installer should see your new cIOS, and if the modules are misplaced, it will tell you.
Source
