A “Brick” usually means your Wii has reached a state where, it’s only use is that of a literal brick.
Bricks can occur for a variety of reasons, usually caused by improper system modifications via homebrew.

Here, we will discuss the different types of bricks, as well as some potential solutions.


Banner bricks occur when a corrupted WAD file is installed on the system menu.


If you have Priiloader installed, enter it by holding RESET while turning your Wii on. Select Homebrew Channel, then use your WAD manager to uninstall the faulty WAD.

If you do not have Priiloader, Maintenance mode may be worth a try. Hold down + and - on the Health and Safety screen. (do not press A!)

If you are fortunate enough to get to the Wii menu, enter the Homebrew Channel and uninstall the faulty WAD.

Theme brick


A theme brick occurs when a wrongly formatted theme is installed.


To resolve this issue, open HBC through Priiloader and access MyMenuifyMOD to install a default theme.



A semibrick occurs when a different region System Menu or a different region custom theme is installed. This causes the Wii to fail to find the Wii settings page files. Semibrick


If this was caused by a theme you installed, use MyMenuifyMod to re-download the original theme file.

If this was caused by a System menu WAD you installed, use NUS Downloader to re-obtain your original system menu.

Be cautious when downloading the System menu WAD. Make sure to pick the same version with the corrected region.

If you are actually in the process of a region change, use ARC-ME to automatically fix all your region settings to match your System menu.

System Menu brick


This brick is a more fatal version of a Semibrick. If your SYSCONF gets corrupt or damaged, the Wii will regenerate it and start the setup phase.

However, the setup pages are in a similar location to the Wii settings pages. If you have an incorrect region System menu or theme, the Wii cannot find them. System menu brick


If you still have Priiloader, use it to enter the Homebrew Channel and re-install the original theme file/original System menu.

In case you do not have Priiloader, you can try BlueBomb.

Mail brick


A mail brick happens when your Wii has a lot of mail. This will make the Wii crash.


To fix a mail brick, enter Maintenance mode by holding + and - on the Health and Safety screen. (do not press A!)
Enter the Homebrew Channel, and use cdbackup to delete your message board data.

Wi-Fi brick


This brick arises when your Wii’s Wi-Fi (or Bluetooth) module is damaged or not inserted properly. In such cases, the Wii gets stuck on a black screen while awaiting a response from IOS.

You can try and differentiate by checking if your Wii remote still powers on your Wii.

This will also happen on the Wii mini if you install a normal Wii IOS, because the Wii Mini does not have a Wi-Fi module.


To resolve this problem, you can try reseat or replace the Wi-Fi/Bluetooth module.

If you are on a Wii Mini, you must install a Wi-Fi module.

Error 003 Brick


This brick happens when a non-Korean System Menu on 4.2 or 4.3 detects that the Korean key is present.

This is usually an immediate follow-up to a Wii System Update on an unsuspecting region-changed Korean Wii. Error 003


Since this brick most often occurs after the System menu updates, Priiloader will not be present.

Korean Wiis also released with System menu 3.3, around the time that Nintendo fixed the Trucha bug in boot1, so BootMii as Boot2 cannot be installed to any Korean Wii.

The only way to fix this brick is a way to launch homebrew by launching a game through the Recovery menu.

IOS brick


This brick happens when the System menu’s IOS is a stub. This is usually the consequence of attempting to downgrade your Wii menu.


You must have BootMii as boot2 to fix this brick. Priiloader will not load.

You can either restore a NAND backup, or do this:

  1. Use NUS Downloader to pack a WAD of your original System menu.
  2. Use BootMii to enter the Homebrew Channel, and use a WAD manager to install the System menu WAD.

Low-level brick


This brick occurs when boot1/boot2 is corrupt.


You can only recover by using a NAND programmer.