AnyTitle Deleter is an application which allows you to completely delete (almost) any title on your Wii. This is useful as a space-freeing application, an informative application, and a paranoia tool. I also hope the source code will be helpful to others making tools for the Wii.

NOTE: DELETING DISC-BASED TITLES FROM YOUR SYSTEM WILL DELETE ITS SAVE DATA!

The following are some notable features:

Deletes previously "Non-Removable" titles, such as IOS, MIOS, some system channels, etc.
Contains extensive brick protection--You cannot delete your System Menu, it's IOS, or some other necessary titles.
Lists all titles installed on the system in both hex and ASCII format in a series of nice (but console-based) menus.
Attempts un-installation of titles the "safe" way, and if it fails, will do a more manual "delete" upon request.
Although I'm far from a "good coder," I put some work into making my code fairly simple and useful for others. For programmers looking to learn something about the Wii, this code contains:

Lots of examples of various ES and ISFS calls
A fairly reliable, though unorthodox System Menu region detection method (not based on console settings, so it applies to even semi-bricked systems)
A console-based menu that should be fairly easy to adapt into other other applications (Just write your own UpdatePage() function)
Lots of comments

Load using any method. This does not rely on SD or any other hardware, so it can be loaded with any current method.

Navigating the menu is self explanatory. Just select a title you want to delete and hit A.

Titles currently only display Title ID (I may add full name listings later).

The ability of this program to delete system titles has caused a bit of worry. As mentioned in the feature description, however, it contains extensive anti-brick precautions. It has been tested on consoles from multiple regions and system versions, and contains fallback protection when some settings cannot be detected.



To the right is a video exposing just how much you can delete without any issues booting the system menu or the homebrew channel. It also demonstrates the brick blocking functionality.

The brick protection prevents the following titles from being deleted:

The System Menu (1-2)
The IOS used by your system menu (1-30 on 3.x). This is detected automatically and completely accurately.
boot2 (1-1, Although boot2 is not a standard listed title anyway)
Region Select and EULA for your region. (0x10008-HALx and 0x10008-HAKx)
In the event that either the System Menu's region or IOS version cannot be detected, it will not allow you to delete any titles in its respective category, and suggests you report the issue to the author.

The brick protection will also provide warnings when you try to uninstall the following titles:

The current IOS (Although its deletion will not affect usage, it may be worth noting)
The IOS used by the Homebrew Channel (Detected automatically, but based on the Homebrew Channel being 0x10001-HAXX)
Neither of these titles will cause bricks, but they could possibly cause unwanted behavior.

I have personally tested all the brick-blocking features with this application, and can say that a 3.x system will successfully boot with only System Menu and IOS30 in the system titles section.

Okay, people wanted it, people get it.

Ocarina is a very simple Wii application for your homebrew channel. What it does? Start a game.. but there's a twist of course.

Ocarina checks the GAME ID.. like RZDP01 for Zelda Twilight Princess (PAL). Then it checks the inserted SD card whether it can find a cheat code file for that game: in this case it would have to be name [sd]:\codes\rzdp01.gct .

To create GCT files.. a PC application is bundled in the package. This application is coming with 2 example files. rsbe.txt and rsbp.txt (Smash Brothers NTSC-U and PAL respectively). Using the File menu you can open, them and select the cheats you want.
Note that unlike an Action Replay you can modify codes with XXXXXXXX inside them.. it will always ask you to store modifications to its application memory I added this question so that people do not cry if a code is messed up - the actual cheat code file will not be modified until you save it in the app.

Once you're done selecting codes: click on "Export to GCT"... and the rest should be pretty straight forward! Insert your SD card.

The package is seperated in a PC folder (PC client) and HBC (Homebrew channel)... put the stuff in its folders.. and they're happy!