Brick Solutions - Try These First!
Posted by tona
|
Brick Solutions - Try These First! October 04, 2008 05:41PM | Admin Registered: 15 years ago Posts: 180 |
This topic contains solutions to Wii Bricks that people have previously found useful along with general troubleshooting steps.
Read the Troubleshooting Steps from Savemii.net
http://savemii.net/troubleshooting.html
A semi-brick occurs when a System Menu update from the wrong region is installed on a Wii or some resources have been otherwise damaged, breaking some (but not all) of the functionality of the System Menu.
To fix a semi-brick you must install the correct System Menu for your region. One way to do this is using Dop-Mii.
A banner brick occurs when the user installs a channel with an invalid banner (wrong image size). With this type of brick the system will freeze after the Health and Safety screen and may display a "System Files are Corrupted" error message. This can be fixed if the Wii has BootMii (as Boot2) or Preloader (Priiloader) installed. If not then you've got a full brick.
A theme brick occurs when the user installs a broken System Menu theme. This type of brick can cause the System Menu to freeze either before or after the Health and Safety screen. his can be fixed if the Wii has BootMii (as Boot2) or Preloader (Priiloader) installed. If not then you've got a full brick.
A full brick of the System Menu occurs when the System Menu itself refuses to boot for any reason. There are two typical symptoms of a full brick:
1. The Wii displays an Opera error message instead of the Health and Safety screen when the Wii boots and does not check the disc drive for a disc before displaying the error. Because of this, it's impossible to fix using software unless you have BootMii installed (as boot2), or you use a Savemii Dongle with an autoboot disc.
2. The Wii displays nothing and you are presented with a black screen. Because of this, it's impossible to fix using software, UNLESS you have BootMii installed (as boot2), or you use a Savemii Dongle with an autoboot disc. In some cases even the latter will be unable to fix this brick.
A broken Bluetooth Module will present the same symptoms [as 2], but can only be fixed by physically replacing the module.
If the Wii NAND filesystem is corrupt, the System Menu's IOS is missing or invalid, or the System Menu is missing or broken, then the system will refuse to boot and nothing will be displayed on the screen. Depending on the exact cause of failure, Preloader or BootMii/boot2 are the only things that can fix this sort of brick, assuming they are installed and the system boots far enough to run them.
A broken Wifi Module will present the same symptoms, but can only be fixed by replacing the module.
A Low Level Brick (LLB) occurs when part of the boot process is corrupt -- boot1 is corrupt, or boot2 is corrupt. Since boot2 is required to be working and able load an IOS before the system can run, any errors in this process will render the system inoperable. It cannot be fixed with software and requires hardware modification (i.e. a hardware NAND programmer) to be repaired.
An Error 003 brick occurs when a System Menu, 4.2 or higher, from a different region gets installed onto a Korean Wii. There is currently no way known to fix this error. Once there is a game with a 4.3K update on it, one could install that via the SaveMii rescue menu.
See also: Brick/Brick Recovery
Edited 1 time(s). Last edit at 09/26/2010 08:19AM by bg4545.
Read the Troubleshooting Steps from Savemii.net
http://savemii.net/troubleshooting.html
A semi-brick occurs when a System Menu update from the wrong region is installed on a Wii or some resources have been otherwise damaged, breaking some (but not all) of the functionality of the System Menu.
To fix a semi-brick you must install the correct System Menu for your region. One way to do this is using Dop-Mii.
A banner brick occurs when the user installs a channel with an invalid banner (wrong image size). With this type of brick the system will freeze after the Health and Safety screen and may display a "System Files are Corrupted" error message. This can be fixed if the Wii has BootMii (as Boot2) or Preloader (Priiloader) installed. If not then you've got a full brick.
A theme brick occurs when the user installs a broken System Menu theme. This type of brick can cause the System Menu to freeze either before or after the Health and Safety screen. his can be fixed if the Wii has BootMii (as Boot2) or Preloader (Priiloader) installed. If not then you've got a full brick.
A full brick of the System Menu occurs when the System Menu itself refuses to boot for any reason. There are two typical symptoms of a full brick:
1. The Wii displays an Opera error message instead of the Health and Safety screen when the Wii boots and does not check the disc drive for a disc before displaying the error. Because of this, it's impossible to fix using software unless you have BootMii installed (as boot2), or you use a Savemii Dongle with an autoboot disc.
2. The Wii displays nothing and you are presented with a black screen. Because of this, it's impossible to fix using software, UNLESS you have BootMii installed (as boot2), or you use a Savemii Dongle with an autoboot disc. In some cases even the latter will be unable to fix this brick.
A broken Bluetooth Module will present the same symptoms [as 2], but can only be fixed by physically replacing the module.
If the Wii NAND filesystem is corrupt, the System Menu's IOS is missing or invalid, or the System Menu is missing or broken, then the system will refuse to boot and nothing will be displayed on the screen. Depending on the exact cause of failure, Preloader or BootMii/boot2 are the only things that can fix this sort of brick, assuming they are installed and the system boots far enough to run them.
A broken Wifi Module will present the same symptoms, but can only be fixed by replacing the module.
A Low Level Brick (LLB) occurs when part of the boot process is corrupt -- boot1 is corrupt, or boot2 is corrupt. Since boot2 is required to be working and able load an IOS before the system can run, any errors in this process will render the system inoperable. It cannot be fixed with software and requires hardware modification (i.e. a hardware NAND programmer) to be repaired.
An Error 003 brick occurs when a System Menu, 4.2 or higher, from a different region gets installed onto a Korean Wii. There is currently no way known to fix this error. Once there is a game with a 4.3K update on it, one could install that via the SaveMii rescue menu.
See also: Brick/Brick Recovery
Edited 1 time(s). Last edit at 09/26/2010 08:19AM by bg4545.
|
Re: Brick Solutions - Try These First! October 18, 2008 06:19PM | Admin Registered: 15 years ago Posts: 180 |
System Menu 2.x Users:
SaveMii acts somewhat differently on System Menu 2.x, but fortunately, it still works.
The main difference for 2.x is that updates are only installed from autoboot discs. You can not just insert a normal game disc to install updates with SaveMii on 2.x. A drivechip is essentially required to use SaveMii to fix 2.x bricks.
If you have a Wii that is still on System Menu 2.x, it is recommended that you update to the immediately with an online update, through homebrew (like DOP-Mii: WiiBrew Edition), or through a game disc update.
Edited 1 time(s). Last edit at 09/26/2010 08:21AM by bg4545.
SaveMii acts somewhat differently on System Menu 2.x, but fortunately, it still works.
The main difference for 2.x is that updates are only installed from autoboot discs. You can not just insert a normal game disc to install updates with SaveMii on 2.x. A drivechip is essentially required to use SaveMii to fix 2.x bricks.
If you have a Wii that is still on System Menu 2.x, it is recommended that you update to the immediately with an online update, through homebrew (like DOP-Mii: WiiBrew Edition), or through a game disc update.
Edited 1 time(s). Last edit at 09/26/2010 08:21AM by bg4545.
Sorry, you can't reply to this topic. It has been closed.