This page covers diagnostic information and troubleshooting for issues that can occur on a Wii that render it inoperable, or impedes a major function of the console.
Error 001, unauthorized device has been detected.
This error appears after attempting to play a backup that was burned incorrectly. You can try to re-burn the disc, use a different burner, or try to load the ISO with something like USB Loader GX. Playing games without cIOS may also cause this issue. Early PIC-based modchips can also trigger this message.
Error 002, an error has occurred...
This error is caused by commercial titles released since late 2008 when they detect being forced to run on a different IOS than specified:
The 002 error is a check if 2 memory areas are the same. The 1st is filled by the apploader with some info from the disc(don't know where it is), which states which IOS to use, and the 2nd is filled by the IOS itself on Reload and tells which IOS is loaded.
The new/better 002fix just writes the 1st information at the postion of the 2nd one. The old 002 fix patched the main.dol and does not work anymore, since this patch causes a freeze on 002b games.
-- WiiPower, 2008
At various points in history, different approaches, alternatively performed by CIOS and backup loaders, have attempted to work around this ― though it should be a solved problem with modern CIOS and loader, while the "Force disc titles to use IOS249" Priiloader patch had traditionally been recognized as problematic.
Error 002-generating code can also be bypassed on backups using the "Generic Wii Patcher" utility.
Error 003, an unauthorized device has been detected
This error appears when System Menu => 4.2 is installed on a region-changed Korean Wii. The System Menu IOS for version 4.2 checks for the existence of an encryption key only present on Korean Wiis (known as the Korean Key), and if the Korean Key is not removed via homebrew prior to updating, then Error 003 will appear and the system will not be able to boot. This error is fixable if Priiloader or BootMii as boot2 was installed prior to the error appearing. You can load either one and then load into the homebrew channel and use KoreanKii to remove the Korean key. In theory, BlueBomb can be used to fix this, but it's unknown whether that works yet. If all else fails, you can try an autoboot disc with the Wii's recovery menu, provided you have a drivechip installed. If you have a BootMii backup or the NAND keys, you can use a flash programmer as a true last resort.
Usually, this error occurs on Wiis from [South] Korea that are updated to => 4.2 without removal of the Korean key. Because of the update, Priiloader is overwritten and Korean Wiis are unable to have Bootmii installed as Boot2. Therefore, installing a drivechip and using Recovery Mode are the only ways to repair this brick other than NAND flashing for Korean wiis.
Error 004 ... The system files are corrupted
This appears when you have BannerBomb v2 installed on System Menu 4.3. Remove it from your SD card using a PC.
This crash can also occur if a channel's banner animation is corrupted or malformed in a way that fails the BannerBomb v2 checks. If you encounter this, enable the "Re-enable Bannerbomb V2" patch in Priiloader.
"The system files are corrupted." or the System Menu otherwise fails to load.
 | Do not randomly edit files used by the System Menu, IOS, or any other component required in the Wii's boot process, unless you are absolutely sure of what you are doing. |
This error occurs when the System Menu chokes on it's own contents or the contents of the filesystem. This usually appears after installing a corrupted theme, or a WAD with a corrupted banner. Note that corrupted doesn't necessarily mean actual data corruption, it could also mean anything the System Menu doesn't like to the point of crashing.
If this error appeared after you performed a modification, simply undo said mod(s) and the error should resolve. You will likely need Priiloader or Bootmii/Boot2 in order to access homebrew that can revert changes or modifications to the System Menu. If neither Priiloader or Bootmii is accessible, then Recovery Mode with a drivechip can also be used to recover from this brick.
For repairing theme bricks, csm-installer is the only homebrew you should use for changing themes as it prevents the installation of themes that are broken or otherwise malformed/corrupt. You should install the default menu theme anytime you have issues with theming the system menu, as it ensures a clean slate to work off once you repair the brick.
For Banner Bricks, AnyTitle Deleter or a WAD manager (such as Multi-Mod Manager) can be used to uninstall WADs with bad banners.
If the symptoms presented are resolved when launching Maintenance Mode (by holding + and - on the H&S screen and not pressing A), then the System Menu could be choking on the contents of the mailbox. This could be caused by having too much mail, or having mail that is corrupted or malformed in a way that causes the Wii to crash when loading it. Because Maintenance Mode disables the Mail function of the System Menu, you should be able to launch the HBC and use Homebrew designed to delete mail, such as cdbackup.
For bricks caused by any other modifications to the System Menu's files, reinstalling the System Menu is the best way to reverse those.
This error is unlikely to appear randomly, but in the event it does, you should inspect the NANDs filesystem and check for bad blocks. A NAND backup should always be taken regularly, or before performing major modifications.
Note: It is also possible for bricks that cause this error to show different symptoms such as a black screen on boot, black screen after Health & Safety, or crashing after booting. Not every brick will show the same symptoms and troubleshooting will be required in most cases.
Opera Error in the system settings (Semi-Brick)
This error occurs when the System Menu is region changed incorrectly, and the Wii is unable to locate the System Setting's HTML document.
This error can also occur when installing out-of-region System Menu WADs or themes. To fix this, reinstall the WAD for your original System Menu or use csm-installer to reinstall the default theme.
Alternatively, AnyRegion Changer: Modmii Edition could be used to fix your region settings to match the System Menu installed.
This error manifests on Korean Wiis as a white page with 3 black dots.
Opera Error on boot instead of Health & Safety (Opera Full Brick)
This is caused when your SYSCONF file is damaged or corrupt and an out-of-region System Menu is installed. Normally, the SYSCONF file being damaged simply just causes the System Menu to restart initial setup, but if a System Menu from a different region is installed, the Wii is unable to correctly generate the file path for the Setup's HTML document, causing a 404 error inside the Opera browser.
If Priiloader or BootMii/Boot2 is installed and functional, then you can simply boot to the HBC and reinstall the original System Menu. You can also try BlueBomb to launch the Hackmii Installer, which will then take you to the HBC.
Should those fail, Recovery Mode with a drivechip can be used to load Smash Stack and launch the Hackmii Installer.
This error manifests on Korean Wiis as a white page with 3 black dots.
Video signal comes from Wii, but nothing is output. Screen is blank, cables and TV have been ruled out
First, try to confirm what works and what doesn't. Try to sync a Wiimote; this will inform you if the Wii is booted and the issue is video related, A/V filtering caps or something else is preventing an output from the Wii. Audio coming from the Wii will also be a good indicator the Wii is booted and functioning on a CPU/OS level.
If that fails, attempt to boot into Priiloader. If Priiloader boots, then launch the HBC and run SysCheck. You can also attempt to boot into Bootmii and restore a NAND backup, but if Priiloader is working, the issue can likely be fixed with homebrew. Proceed as if the Wii is showing "The System Files are Corrupted".
If Priiloader is unable to boot, see if the Wii has a vulnerable Boot1. If it does, check if Bootmii is able to boot off the SD card. If it does, then swap the Wifi module and confirm the Wii is able to boot to H&S. If not, then the System Menu IOS is corrupt. You can restore a NAND backup to repair this brick, or from BootMii launch the HBC and use a WAD Manager to reinstall the System Menu.
If the Wii does not have a vulnerable Boot1, attempt to boot Recovery Mode. If the Wii boots, try swapping the Wifi/Bluetooth module and the DVD drive. If not, then install a modchip and attempt to boot a Smash Stack disc. From there, try to load the HBC and reinstall the System Menu for your Wii's region. Bluebomb can theoretically be used in Recovery Mode, but it is unknown how to do this yet. If you have done this, please reach out to us on Discord so we can update this page with instructions.
If Recovery Mode fails to boot, then the System Menu IOS is corrupt or the Wii is suffering from a Low-level brick. If you have the expertise, you can attempt a low-level repair such as NAND flashing or motherboard repair.
If you have a Wii Mini, ensure you did not install a normal IOS80. If you did, good job. You now have to install a Wifi module. Otherwise, the steps here are similar but with the restrictions on the Wii mini.
A generic hardware failure (Bad CPU/RAM, GPU, NAND, etc..) can also cause symptoms of a Low-Level Brick.