Your IP address will be publicly visible if you make any edits.
Wii:Cheats
From Hacks Guide Wiki
More actions
This is the latest revision of this page; it has no approved revision.
Cheat Codes, also sometimes known as Gecko Codes, are strings of hexidecimal that will modify parts of a Wii or Gamecube game, either for the purpose of gaining an advantage in the game, using a private server, or adjusting video and other functions. Cheats that gain an advantage in online gameplay may be subject to a ban, so use them at your own discretion.
Make sure you install cIOS before continuing with this tutorial!
Extract the usbloader_gx.zip and copy the apps folder to the root of your SD card or USB drive.
Select the cheats you want to download from Gamehacking.org. If you have your own code, see the example cheat file for proper formatting.
In the format dropdown menu, select .txt.
Then, under the filename dropdown menu, select the game ID. It should be the last option.
On the root your SD or USB drive, make a folder called txtcodes, then place the file there.
Eject the SD card or USB drive and insert it into your Wii.
Launch USB Loader GX in the Homebrew Channel.
Click on the game you want to launch. If you want to launch a Disc, you can press the Disc icon in the top right corner.
Select Settings, then select Game Load, and scroll down until you see Ocarina, then enable it.
Navigate back one menu and select the Ocarina option. You should be greeted with a list of your codes.
Choose which codes you would like to enable, then select create.
Launch the game and the codes will be applied. The .gct file that was created is stored in the codes folder on the root of your SD or USB drive.
Make sure you install cIOS before continuing with this tutorial!
Extract the wiiflow.zip and copy the apps folder to the root of your SD card or USB drive.
Select the cheats you want to download from Gamehacking.org. If you have your own code, see the example cheat file for proper formatting.
In the format dropdown menu, select .txt.
Then, under the filename dropdown menu, select the game ID. It should be the last option.
Save the .txt file to /wiiflow/codes/ on your SD or USB drive
Launch WIiFlow WFL in the Homebrew Channel.
Click on the game you want to launch. If you want to launch a Disc, you can press the Disc icon in the bottom right corner.
Select Settings, go to page 2 and enable Ocarina.
Select the Cheat Codes option. You should be greeted with a list of your codes.
Choose which codes you would like to enable, then select apply.
Launch the game and the codes will be applied. The .gct file that was created is stored in /wiiflow/codes/gct on your SD or USB drive.
This tutorial does NOT work with disc backups or channels installed to an emuNAND, use USB Loader GX or WiiFlow if you wish to use cheats with them.
Extract the WiiLauncher.zip and copy the apps folder to the root of your SD card or USB drive.
Extract the Cheat_manager_v0_3.rar using 7-Zip (Keka on Mac) and copy the apps folder to the root of your SD card or USB drive.
Select the cheats you want to download from Gamehacking.org. If you have your own code, see the example cheat file for proper formatting.
In the format dropdown menu, select .txt.
Then, under the filename dropdown menu, select the game ID. It should be the last option.
On the root your SD or USB drive, make a folder called txtcodes, then place the text file there.
Eject the SD card or USB drive and insert it into your Wii.
Launch Cheat Manager in the Homebrew Channel.
Select the corresponding text file that goes to the game ID of your game.
Press + on your Wii remote for every code you would like to enable.
Press 1 on the Wii remote to create the .gct file. The .gct file that was created is stored in the codes folder on the root of your SD or USB drive.
Press the home button to exit back to the Homebrew Channel.
Launch WiiLauncher in the Homebrew Channel.
If you are launching a disc game, insert your disc into the Wii's disc drive, then select Launch Game. Otherwise, select Launch Channel.
This tutorial does NOT work with disc backups or channels installed to an emuNAND, use USB Loader GX or WiiFlow if you wish to use cheats with them.
On Windows Devices, you may need to enable file name extentions to see the complete name of the file.
Extract the WiiLauncher.zip and copy the apps folder to the root of your SD card or USB drive.
Extract the codemanager.zip to a preferred location on your PC.
Select the cheats you want to download from Gamehacking.org. If you have your own code, see the example cheat file for proper formatting.
In the format dropdown menu, select .txt.
Then, under the filename dropdown menu, select the game ID. It should be the last option.
Launch the codemanager1.2.exe in the codemanager folder on your PC.
In the top right corner, click on File, then click on Open TXT file.
Locate your .txt file you saved and select Open.
Select the check box for every code you want to enable, then select Export to GCT, and select Store to file
Locate your SD or USB drive, ceate a folder called codes, and save it there.
Eject the SD card or USB drive and insert it into your Wii.
Launch WiiLauncher in the Homebrew Channel.
If you are launching a disc game, insert your disc into the Wii's disc drive, then select Launch Game. Otherwise, select Launch Channel. The game should launch with your codes applied.
Example Cheat File
On Windows Devices, you may need to enable file name extentions to see the complete name of the file.
Below is an example of a cheat file for the USA version of Mario Kart Wii. Create a new text file using your preferred text editor. Make sure the encoding is set to UTF-8. The filename for the text file will be renamed to the game ID that your game is for. In this example, it will be named RMCE01.txt Game IDs can be found on GameTDB. Make sure the Game ID for your region is correct. Inside of the text file, the game ID will be on line 1, and on line 2 will be the game name. Copy your first code two lines below the game name, making sure the name of the code is displayed first then the strings of hexidecimal below that. Seperate each code with 2 lines of space. Code author is not required, but crediting is always a good idea.