5,579
edits
Changes
Jump to navigation
Jump to search
Line 20:
Line 20: − − = Types of Bricks = − − == Semi/Partial Brick == − A Semi/Partial 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. Typically, games will still boot but the Settings menu will not work -- this prevents the system from healing itself with an online update. These cases can be fixed by installing a newer version of the System Menu from a disc of the correct region, or with any other tool that can modify the System Menu. − − === Fixing this brick === − An semi brick can be fixed by opening the [[Homebrew channel]] and booting recovery software to install the correct region or [[IOS]] set. − − If HBC is not installed for whatever reason, then [[Bannerbomb]] or [[Letterbomb]] can be used on any Wii on 4.0-4.3. On other versions, [[Bluebomb]] is generally the exploit to use. These exploits should be used to load the [[HackMii Installer]], which can be used to access HBC. − − Once HBC is loaded, [[NUS Downloader]] can be used to download the correct system files, and installed over the current system menu. − − '''CAUTION: Installing the wrong file can make the brick worse! Be very careful!''' − − === Cause of this brick === − Each region has its own version of the System Menu. For example, 3.2 of the [[System Menu]] available is v288 (NTSC/J), v289 (NTSC/U), v290 (PAL). The only difference between those three versions is two different files — the main executable for the menu (a .DOL file, more or less) and an ARC archive that stores compressed versions of the HTML/image resources. − − All of this is fine and good, but why put them in separately named directories? (E.g. EU/EU/GER/Setup/ScreenSave.html above)? The path name could always be the same because there are different files for each version. − − If there’s a specific path that the graphics need to sit at, it would make sense to simply hardcode this path. However, they seem to be trying to determine the system region from the [[:/title/00000001/00000002/data/setting.txt]] file, and then building up a pathname to load like so: sprintf(filename, "html/%s2/iplsetting.ash/%s/%s/ENG/Setup/ScreenSave.html", region, region, region). If they had hard-coded the path then the settings page would have loaded just fine. − − == Mail Brick == − A Mail Brick is caused when a user has too much mail in their Message Board for the Wii to handle. The Wii will crash upon booting through normal means. However, the System Menu can still be used through [[Maintenance Mode]]. − − === Fixing this brick === − This brick can be fixed by entering Maintanence Mode, which is done by holding + and - on the health screen when pressing A. From here, the mail can be deleted using homebrew launched from the [[Homebrew channel]]. If the Homebrew channel is not installed, then [[str2hax]] can be used for versions 2.0-4.3, or [[Bluebomb]] for other versions. Once the [[HackMii Installer]] is launched this way, HBC can be installed, and a mail deletion tool can be loaded. − − === Cause of this brick === − Mail bricks occur when malformed mail appears. Because the [[Message Board]] is always drawn under the channels, this causes functionality to fail, even before opening the message board. However, this is disabled entirely in maintanence mode, which allows the [[System Menu]] to launch. − − == Banner Brick == − 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. − − === Fixing this brick === − Since boot2 is intact during a Banner Brick, any user who owns a pre Q4 2008 Wii with BootMii installed (as boot2) can access BootMii regardless of any corrupt WAD installed. From here they can access the HBC to uninstall the broken channel using [[AnyTitle Deleter]]. − − If [[Preloader]] or [[Priiloader]] is installed, holding reset while powering on the Wii and launching HBC will enable recovery by uninstalling the broken channel. − − Users Without [[BootMii]] installed as [[boot2]] and [[Priiloader]]/[[Preloader]] may use the [[BlueBomb]] exploit to launch the [[HackMii Installer]], which will enable access to the HBC, so a similar recovery procedure can be used as described above. − − '''NOTE: Uninstalling the incorrect channel may lead to further damage, so users should be careful.''' − − === Cause of this brick === − A banner brick is caused when a channel with a malformed banner (icon), is installed. Due to the poor error checking of the System Menu, the system menu cant handle the corrupted banner, so it crashes and thinks that it is a file corruption. − − == Full Brick (System Menu) == − Generally speaking, a "full brick" occurs when the System Menu 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 “WARNING 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) In some cases the latter will be unable to fix this brick. − − Similar bricks occur when there is a broken Bluetooth Module, or non-Korean System Menu on a Korean Wii. The former can only be fixed by replacing the module. − − === Fixing this brick === − To fix this brick, [[BootMii]] must be installed as [[boot2]]. To boot recovery software, navigate to HBC and perform a system update. − − In some cases, it may also be possible to fix this brick using [[Priiloader]], by booting to HBC. This method is not as reliable as the BootMii method. − − If the Priiloader method does not work, and your Wii has GameCube ports in it, a [[SaveMii Dongle]] can be used. These dongles are inserted into the GameCube memory port, and are capable of performing disc updates. On a [[Wii Family Edition]], the GameCube ports can be soldered back in, allowing this method to work there as well. − − Once HBC is booted, [[NUS Downloader]] can be used to download an uncorrupted [[System Menu]], and another tool can install it. − − If none of these are options, [[Infectus]] must be used to restore a NAND backup. − − === Cause of this brick === − A full brick is caused when [[:/shared2/sys/SYSCONF]] is missing, damaged, or has the "reconfiguration" flag set, and the /title/00000001/00000002/data/setting.txt has the wrong region in it. When the system boots, it attempts to load the initial setup menu due to the damaged SYSCONF, but for the same reasons as the [[#Semi/Partial Brick|semi-brick]], it fails to find the page for setup and instead shows the Opera error. − − == Full Brick (IOS) == − If the [[System Menu]]'s [[IOS]] is corrupted, then the Wii will not show anything on the screen. This will appear identical to a System Menu brick, however, [[Priiloader]] cannot be used to fix this brick. − − A broken Wifi Module will present the same symptoms, but can only be fixed by replacing the module. This extends to installing a normal [[System Menu]] [[IOS]] on a [[Wii Mini]] without a WiFi module installed. − − === Fixing this brick === − To recover from an IOS brick, [[BootMii]] must be installed as [[boot2]]. Normal homebrew will likely not work to recover from this brick, because they depend on IOS's that are now corrupted. Instead, special tools using [[mini]] (such as [[RestoreMii]]) must be used to fix this brick. − − If BootMii cannot be installed as boot2 on this Wii, then [[Infectus]] must be used to restore a NAND backup. − − === Cause of this brick === − This brick occurs when the System Menu IOS is missing or corrupted. When this happens, boot2 cannot locate the IOS that should be launched, so it fails to boot, or boots garbage code. − − == Low Level Brick (LLB) == − − A 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. A LLB cannot be fixed with software and requires hardware modification to be repaired. − − === Fixing this brick === − LLBs cannot be fixed with [[BootMii]], even if it is installed as boot2. Instead, [[Infectus]] must be installed into the Wii hardware to install proper boot contents. A NAND backup is not required for this, because boot1 and boot2 are not encrypted with the NAND key. − − === Cause of this brick === − This is one of the most dangerous bricks, because not even BootMii can fix it. While [[boot0]] is in ROM, [[boot1]] is on the [[NAND]] and is SHA1 hashed in [[Hardware/OTP|OTP]]. This means if boot1 is modified at all, the signature check will fail, and boot0 will refuse to boot. [[boot2]] suffers in the same way, although its signature is checked via RSA signature verification instead of ROM, so this brick could also be caused by a corrupt boot2 signature, resulting in boot1 refusing to boot the system. No part of the official [[boot process]] allows recovery software to be booted, leaving the Wii in a bad state. − − Many low level bricks were caused by the [[4.2]] update incorrectly overriding boot2.
→Types of Bricks: removed section, as they now have their own pages
Finally, if an existing BootMii-boot2 installation fails to boot, then this is a [[#Low Level Brick (LLB)|low-level brick]].
Finally, if an existing BootMii-boot2 installation fails to boot, then this is a [[#Low Level Brick (LLB)|low-level brick]].
= Prevention =
= Prevention =