Difference between revisions of "Brick"

From WiiBrew
Jump to navigation Jump to search
m (Brick category)
 
(3 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[File:Error003.png|thumb|Error 003, an example of a We lego.]]
+
[[File:Error003.png|thumb|Error 003, an example of a Wii brick.]]
To '''lego''' a We is to damage the console in a way that it can no longer be used properly, usually beyond repair - as in 'A legoed We has all the electronic functionality of a lego'. To put it simply, fully legoed We consoles do absolutely nothing. The term is often used in situations where modifying a system's firmware (without necessarily making any alterations to the machine's hardware) has caused it to become inoperable.
+
To '''brick''' a Wii is to damage the console in a way that it can no longer be used properly, usually beyond repair - as in 'A bricked Wii has all the electronic functionality of a brick'. To put it simply, fully bricked Wii consoles do absolutely nothing. The term is often used in situations where modifying a system's firmware (without necessarily making any alterations to the machine's hardware) has caused it to become inoperable.
  
Fixing a lego generally comes in three steps; the first step is identifying the lego, the second step is launching [[homebrew]], and the third step is using this homebrew to load a recovery tool.
+
Fixing a brick generally comes in three steps; the first step is identifying the brick, the second step is launching [[homebrew]], and the third step is using this homebrew to load a recovery tool.
  
If a lego cannot easily be fixed, it is '''not''' recommended to trash the console. As We's are no longer in production, many people will probably be interested in a legoed console to repair or conduct research on. Instead of trashing the console, sell it online or ask a community (such as ReConnect24) if they are interested in investigating the lego.
+
If a brick cannot easily be fixed, it is '''not''' recommended to trash the console. As Wii's are no longer in production, many people will probably be interested in a bricked console to repair or conduct research on. Instead of trashing the console, sell it online or ask a community (such as RiiConnect24) if they are interested in investigating the brick.
  
= Identifying a lego =
+
= Identifying a brick =
To fix a lego, it must be identified first. If the [[System Menu]] boots fine, then the lego is simply a [[/Semilego|semilego]].
+
To fix a brick, it must be identified first. If the [[System Menu]] boots fine, then the brick is simply a [[/Semibrick|semibrick]].
  
If the health screen is the last screen seen, then the lego is either a banner lego or a mail lego. To test this, hold + and - when pressing A; if the system still refuses to boot, it is a [[/Banner lego|banner lego]], otherwise it is a [[/Mail lego|mail lego]].
+
If the health screen is the last screen seen, then the brick is either a banner brick or a mail brick. To test this, hold + and - when pressing A; if the system still refuses to boot, it is a [[/Banner brick|banner brick]], otherwise it is a [[/Mail brick|mail brick]].
  
If "Error 003" appears on the screen, then it is an [[Error 003|Error 003 lego]].
+
If "Error 003" appears on the screen, then it is an [[Error 003|Error 003 brick]].
  
If an Opera error shows, then it is a [[/System Menu lego|System Menu lego]].  
+
If an Opera error shows, then it is a [[/System Menu brick|System Menu brick]].  
  
If [[BootMe]] as [[boot2]] still boots, then it is either a System Menu lego or an [[/IOS lego|IOS lego]], both of which have a similar fixing procedure.
+
If [[BootMii]] as [[boot2]] still boots, then it is either a System Menu brick or an [[/IOS brick|IOS brick]], both of which have a similar fixing procedure.
  
If [[Preloader]] is installed, and it boots, then this is likely a System Menu lego, and can easily be fixed.
+
If [[Priiloader]] is installed, and it boots, then this is likely a System Menu brick, and can easily be fixed.
  
If all else fails, it is a [[/Low-level lego|low-level lego]].
+
If all else fails, it is a [[/Low-level brick|low-level brick]].
  
Finally, if an existing BootMe-boot2 installation fails to boot, then this is a low-level lego.
+
Finally, if an existing BootMii-boot2 installation fails to boot, then this is a low-level brick.
 +
 
 +
== Types of bricks ==
 +
Click the link for your brick type for further instructions on fixing the brick.
 +
* [[/Semibrick|Semibrick]]
 +
* [[/Banner brick|Banner brick]]
 +
* [[/Mail brick|Mail brick]]
 +
* [[Error 003|Error 003 brick]]
 +
* [[/System Menu brick|System Menu brick]]
 +
* [[/IOS brick|IOS brick]]
 +
* [[/Low-level brick|Low-level brick]]
  
 
= Prevention =
 
= Prevention =
 
* '''Only install updates for your own region.'''
 
* '''Only install updates for your own region.'''
 
* Play your own region
 
* Play your own region
** Playing games or using We Menu channels from other regions shouldn't cause any problems, but in exceptional circumstances something could go wrong
+
** Playing games or using Wii Menu channels from other regions shouldn't cause any problems, but in exceptional circumstances something could go wrong
 
** Games and Channels from other regions will not function without modification
 
** Games and Channels from other regions will not function without modification
 
* '''DO NOT DELETE CRITICAL SYSTEM FILES'''
 
* '''DO NOT DELETE CRITICAL SYSTEM FILES'''
Line 42: Line 52:
 
** '''FirmWare Downgraders'''
 
** '''FirmWare Downgraders'''
 
** '''Any Other System Tools'''
 
** '''Any Other System Tools'''
* '''DO NOT TOUCH YOUR We's POWER SOURCE/BUTTON WHILE UPDATING/INSTALLING SYSTEM CONTENT'''
+
* '''DO NOT TOUCH YOUR Wii's POWER SOURCE/BUTTON WHILE UPDATING/INSTALLING SYSTEM CONTENT'''
** '''(e.g. BootMe NAND backup)'''
+
** '''(e.g. BootMii NAND backup)'''
 
** '''ESPECIALLY DURING AN ELECTRICAL STORM'''
 
** '''ESPECIALLY DURING AN ELECTRICAL STORM'''
  
 
= Other recovery methods =
 
= Other recovery methods =
 
+
If the methods above don't work, try these methods.
If a We becomes legoed, there may be a way to unlego it.
 
  
 
== Using a Recovery Disc ==
 
== Using a Recovery Disc ==
Line 54: Line 63:
 
* [[modchip|Modchip]]
 
* [[modchip|Modchip]]
 
OR
 
OR
* [[Preloader]]
+
* [[Priiloader]]
  
=== Preloader ===
+
=== Priiloader ===
 
The disc check can be bypassed.
 
The disc check can be bypassed.
 
=== Modchip ===
 
=== Modchip ===
Line 72: Line 81:
  
 
=== Using a savegame exploit ===
 
=== Using a savegame exploit ===
If you do have a copy of an exploit save '''ALREADY''' on the We, and an authentic exploitable disc, you can use this to boot recovery software as well.
+
If you do have a copy of an exploit save '''ALREADY''' on the Wii, and an authentic exploitable disc, you can use this to boot recovery software as well.
 
This also requires:
 
This also requires:
  
Line 80: Line 89:
 
*A recovery homebrew app on the root of the SD card, named boot.dol
 
*A recovery homebrew app on the root of the SD card, named boot.dol
  
If you do not already have a savegame exploit on the We's NAND, there's a method to get it on the We NAND after a lego:
+
If you do not already have a savegame exploit on the Wii's NAND, there's a method to get it on the Wii NAND after a brick:
  
*Spam the NAND with savegames until it's nearly full. Alternatively, if you have internet access on your We, We Shop access, and channels you can redownload (unless your NAND is already almost full), you can download a bunch of channels until there's little to no space left.
+
*Spam the NAND with savegames until it's nearly full. Alternatively, if you have internet access on your Wii, Wii Shop access, and channels you can redownload (unless your NAND is already almost full), you can download a bunch of channels until there's little to no space left.
*Try to install another channel, the Rabbids Go Home Channel, the [[Mario Kart Channel]], or the [[We Fit Channel]].
+
*Try to install another channel, the Rabbids Go Home Channel, the [[Mario Kart Channel]], or the [[Wii Fit Channel]].
 
*Use the option to go to data management and copy the savegame over. (And don't forget to delete the savegames/channels you spammed earlier when you're done!)
 
*Use the option to go to data management and copy the savegame over. (And don't forget to delete the savegames/channels you spammed earlier when you're done!)
*Once the savegame is copied over, boot the game, use the exploit, and use the recovery homebrew you copied earlier to recover the We from the lego.
+
*Once the savegame is copied over, boot the game, use the exploit, and use the recovery homebrew you copied earlier to recover the Wii from the brick.
  
 
=== Using [[Smash Stack]] ===
 
=== Using [[Smash Stack]] ===
Line 96: Line 105:
 
Simply copy the Smash Stack stages over to the SD card, and load the level editor as usual.
 
Simply copy the Smash Stack stages over to the SD card, and load the level editor as usual.
  
== Using [[Preloader]] ==
+
== Using [[Priiloader]] ==
 
Requires:
 
Requires:
* Preloader
+
* Priiloader
 
** Configured to boot something other than the [[System Menu]]
 
** Configured to boot something other than the [[System Menu]]
  
Simply boot a recovery program the way you would any other. if you have [[Preloader]] installed, but it boots to the System Menu then try holding down reset when you turn on your We, after a few seconds of holding reset the Preloader menu should appear.
+
Simply boot a recovery program the way you would any other. if you have [[Priiloader]] installed, but it boots to the System Menu then try holding down reset when you turn on your Wii, after a few seconds of holding reset the Priiloader menu should appear.
  
== Using [[BootMe]] ==
+
== Using [[BootMii]] ==
 
Requires:
 
Requires:
 
* NAND backup
 
* NAND backup
** '''BEFORE''' the We legos
+
** '''BEFORE''' the Wii bricks
  
It's advised to backup your NAND right after you install BootMe.
+
It's advised to backup your NAND right after you install BootMii.
  
 
=== [[boot2]] ===
 
=== [[boot2]] ===
If you installed [[BootMe]] as boot2, then simply go to the second options screen and choose the second icon which can recover from the lego.
+
If you installed [[BootMii]] as boot2, then simply go to the second options screen and choose the second icon which can recover from the brick.
  
 
=== IOS ===
 
=== IOS ===
If you installed BootMe as part of an IOS, then you will need [[Preloader]] installed. Go to the HBC via [[Preloader]], then select '''Launch BootMe''' from the main menu.  
+
If you installed BootMii as part of an IOS, then you will need [[Priiloader]] installed. Go to the HBC via [[Priiloader]], then select '''Launch BootMii''' from the main menu.  
  
 
== Using a NAND Programmer ==
 
== Using a NAND Programmer ==
 
Requires:
 
Requires:
* Soldering many wires to the We's motherboard
+
* Soldering many wires to the Wii's motherboard
  
In order to use a NAND Programmer/[[Glossary#I|Infectus]] to rewrite the flash directly you will need to know your We's NAND keys.
+
In order to use a NAND Programmer/[[Glossary#I|Infectus]] to rewrite the flash directly you will need to know your Wii's NAND keys.
  
 
== WC24 title booting ==
 
== WC24 title booting ==
[[WeConnect24#WC24_title_booting|WC24 title booting]] can be used to fix banner legos. The types of legos this can fix is similar to the "recovery mode" menu. That menu can be triggered by holding down all D-Pad buttons on the GC controller plugged into slot 4, a tab inside the controller needs removed in official GC controllers. Every time the file at the boot mail entry URL installed by wc24app is updated, every We that already downloaded the boot mail would download again and wakeup for title booting again. The entry URLs that wc24app installs includes the consoleID, this can be used to send unique content for one We. If you need the boot mail content for the entry installed by wc24app to be updated to fix your legoed We after it already downloaded and booted with the mail, contact [[User:Yellows8|Yellows8]] on the talk [[User_talk:Yellows8|page]], or send an email to yellowstar6 at gmail dot com.
+
[[WiiConnect24#WC24_title_booting|WC24 title booting]] can be used to fix banner bricks. The types of bricks this can fix is similar to the "recovery mode" menu. That menu can be triggered by holding down all D-Pad buttons on the GC controller plugged into slot 4, a tab inside the controller needs removed in official GC controllers. Every time the file at the boot mail entry URL installed by wc24app is updated, every Wii that already downloaded the boot mail would download again and wakeup for title booting again. The entry URLs that wc24app installs includes the consoleID, this can be used to send unique content for one Wii. If you need the boot mail content for the entry installed by wc24app to be updated to fix your bricked Wii after it already downloaded and booted with the mail, contact [[User:Yellows8|Yellows8]] on the talk [[User_talk:Yellows8|page]], or send an email to yellowstar6 at gmail dot com.
To repair a We with WC24 title booting, the following requirements must be met:
+
To repair a Wii with WC24 title booting, the following requirements must be met:
 
* Like the "recovery mode" menu, sysmenu IOS must be working correctly
 
* Like the "recovery mode" menu, sysmenu IOS must be working correctly
 
* HBC must be installed since the boot mail would boot HBC, WC24 title booting can't boot discs.
 
* HBC must be installed since the boot mail would boot HBC, WC24 title booting can't boot discs.
 
* Sysmenu needs to be working without completely crashing to allow shutting down to idle/"standby" mode
 
* Sysmenu needs to be working without completely crashing to allow shutting down to idle/"standby" mode
* Before the lego occurs, you need to run [[libwc24|wc24app]] v1.1(currently from SVN or this [http://iwconfig.net/~yellows8/wc24app.dol.php build]) on the We to install the boot mail entry, and to enable the WC24 title boot flag. The title boot flag is never cleared or set after file creation by Nintendo software, this flag is only cleared by Nintendo software on file creation. Nintendo announcement mail can't be intercepted and modified since that mail is RSA signed.(Modifying that mail is only possible if the sysmenu IOS has the signature check patched or has the fakesign bug, and any other IOS that run when the mail is newly downloaded/downloaded when mail is updated would need the sig patch or have the fakesign bug.)
+
* Before the brick occurs, you need to run [[libwc24|wc24app]] v1.1(currently from SVN or this [http://iwconfig.net/~yellows8/wc24app.dol.php build]) on the Wii to install the boot mail entry, and to enable the WC24 title boot flag. The title boot flag is never cleared or set after file creation by Nintendo software, this flag is only cleared by Nintendo software on file creation. Nintendo announcement mail can't be intercepted and modified since that mail is RSA signed.(Modifying that mail is only possible if the sysmenu IOS has the signature check patched or has the fakesign bug, and any other IOS that run when the mail is newly downloaded/downloaded when mail is updated would need the sig patch or have the fakesign bug.)
  
 
== Sending it to Nintendo ==
 
== Sending it to Nintendo ==
This option is the least desirable for homebrew users, as Nintendo will likely send back a different console, with your personal settings/We Shop account transferred and the latest updates installed. Additionally, Nintendo is no longer repairing any Wes, so this is not even a last resort anymore.
+
This option is the least desirable for homebrew users, as Nintendo will likely send back a different console, with your personal settings/Wii Shop account transferred and the latest updates installed. Additionally, Nintendo is no longer repairing any Wiis, so this is not even a last resort anymore.
  
[[Category:We documentation]]
+
[[Category:Brick]]

Latest revision as of 20:39, 25 February 2022

Error 003, an example of a Wii brick.

To brick a Wii is to damage the console in a way that it can no longer be used properly, usually beyond repair - as in 'A bricked Wii has all the electronic functionality of a brick'. To put it simply, fully bricked Wii consoles do absolutely nothing. The term is often used in situations where modifying a system's firmware (without necessarily making any alterations to the machine's hardware) has caused it to become inoperable.

Fixing a brick generally comes in three steps; the first step is identifying the brick, the second step is launching homebrew, and the third step is using this homebrew to load a recovery tool.

If a brick cannot easily be fixed, it is not recommended to trash the console. As Wii's are no longer in production, many people will probably be interested in a bricked console to repair or conduct research on. Instead of trashing the console, sell it online or ask a community (such as RiiConnect24) if they are interested in investigating the brick.

Identifying a brick

To fix a brick, it must be identified first. If the System Menu boots fine, then the brick is simply a semibrick.

If the health screen is the last screen seen, then the brick is either a banner brick or a mail brick. To test this, hold + and - when pressing A; if the system still refuses to boot, it is a banner brick, otherwise it is a mail brick.

If "Error 003" appears on the screen, then it is an Error 003 brick.

If an Opera error shows, then it is a System Menu brick.

If BootMii as boot2 still boots, then it is either a System Menu brick or an IOS brick, both of which have a similar fixing procedure.

If Priiloader is installed, and it boots, then this is likely a System Menu brick, and can easily be fixed.

If all else fails, it is a low-level brick.

Finally, if an existing BootMii-boot2 installation fails to boot, then this is a low-level brick.

Types of bricks

Click the link for your brick type for further instructions on fixing the brick.

Prevention

  • Only install updates for your own region.
  • Play your own region
    • Playing games or using Wii Menu channels from other regions shouldn't cause any problems, but in exceptional circumstances something could go wrong
    • Games and Channels from other regions will not function without modification
  • DO NOT DELETE CRITICAL SYSTEM FILES
  • DO NOT INSTALL SYSTEM FILE MODS
    • Unless, you have a VERY good reason
  • DO NOT INSTALL UNOFFICIAL CHANNELS
    • Unless, they come from a TRUSTED source and REALLY serve a useful function
    • Malformed channels (especially the banner part) can make your System Menu crash on boot
    • Loading apps from a SD Card is much safer
  • Ensure that you know what you're doing before you install or run any homebrew apps
    • Especially, those with the "Homebrew Dangerous if Misused" banner on their page
  • BE VERY CAREFUL WHEN USING:
  • DO NOT TOUCH YOUR Wii's POWER SOURCE/BUTTON WHILE UPDATING/INSTALLING SYSTEM CONTENT
    • (e.g. BootMii NAND backup)
    • ESPECIALLY DURING AN ELECTRICAL STORM

Other recovery methods

If the methods above don't work, try these methods.

Using a Recovery Disc

Requires:

OR

Priiloader

The disc check can be bypassed.

Modchip

This allows you to boot Recovery Software from a disc.

NOTE: This method is outdated and has a lot of requirements:

1.) A semi-working System Menu.

2.) A fully working System Menu IOS.

3.) ILLEGAL copies of the old repair disc.

  • Won't work on updated systems, because IOS16 was stubbed and homebrew discs require the Trucha Bug inside the correct IOS or that IOS has to ignore signing completely.

Using a savegame exploit

If you do have a copy of an exploit save ALREADY on the Wii, and an authentic exploitable disc, you can use this to boot recovery software as well. This also requires:

  • A semi-working System Menu.
  • A fully working System Menu IOS.
  • Some way to still boot game discs.
  • A recovery homebrew app on the root of the SD card, named boot.dol

If you do not already have a savegame exploit on the Wii's NAND, there's a method to get it on the Wii NAND after a brick:

  • Spam the NAND with savegames until it's nearly full. Alternatively, if you have internet access on your Wii, Wii Shop access, and channels you can redownload (unless your NAND is already almost full), you can download a bunch of channels until there's little to no space left.
  • Try to install another channel, the Rabbids Go Home Channel, the Mario Kart Channel, or the Wii Fit Channel.
  • Use the option to go to data management and copy the savegame over. (And don't forget to delete the savegames/channels you spammed earlier when you're done!)
  • Once the savegame is copied over, boot the game, use the exploit, and use the recovery homebrew you copied earlier to recover the Wii from the brick.

Using Smash Stack

If you have a copy of Super Smash Bros. Brawl, you can boot recovery software as well.

Requirements:

  • Some way to boot game discs
  • A recovery homebrew app on the root of the SD card, named boot.dol

Simply copy the Smash Stack stages over to the SD card, and load the level editor as usual.

Using Priiloader

Requires:

  • Priiloader
    • Configured to boot something other than the System Menu

Simply boot a recovery program the way you would any other. if you have Priiloader installed, but it boots to the System Menu then try holding down reset when you turn on your Wii, after a few seconds of holding reset the Priiloader menu should appear.

Using BootMii

Requires:

  • NAND backup
    • BEFORE the Wii bricks

It's advised to backup your NAND right after you install BootMii.

boot2

If you installed BootMii as boot2, then simply go to the second options screen and choose the second icon which can recover from the brick.

IOS

If you installed BootMii as part of an IOS, then you will need Priiloader installed. Go to the HBC via Priiloader, then select Launch BootMii from the main menu.

Using a NAND Programmer

Requires:

  • Soldering many wires to the Wii's motherboard

In order to use a NAND Programmer/Infectus to rewrite the flash directly you will need to know your Wii's NAND keys.

WC24 title booting

WC24 title booting can be used to fix banner bricks. The types of bricks this can fix is similar to the "recovery mode" menu. That menu can be triggered by holding down all D-Pad buttons on the GC controller plugged into slot 4, a tab inside the controller needs removed in official GC controllers. Every time the file at the boot mail entry URL installed by wc24app is updated, every Wii that already downloaded the boot mail would download again and wakeup for title booting again. The entry URLs that wc24app installs includes the consoleID, this can be used to send unique content for one Wii. If you need the boot mail content for the entry installed by wc24app to be updated to fix your bricked Wii after it already downloaded and booted with the mail, contact Yellows8 on the talk page, or send an email to yellowstar6 at gmail dot com. To repair a Wii with WC24 title booting, the following requirements must be met:

  • Like the "recovery mode" menu, sysmenu IOS must be working correctly
  • HBC must be installed since the boot mail would boot HBC, WC24 title booting can't boot discs.
  • Sysmenu needs to be working without completely crashing to allow shutting down to idle/"standby" mode
  • Before the brick occurs, you need to run wc24app v1.1(currently from SVN or this build) on the Wii to install the boot mail entry, and to enable the WC24 title boot flag. The title boot flag is never cleared or set after file creation by Nintendo software, this flag is only cleared by Nintendo software on file creation. Nintendo announcement mail can't be intercepted and modified since that mail is RSA signed.(Modifying that mail is only possible if the sysmenu IOS has the signature check patched or has the fakesign bug, and any other IOS that run when the mail is newly downloaded/downloaded when mail is updated would need the sig patch or have the fakesign bug.)

Sending it to Nintendo

This option is the least desirable for homebrew users, as Nintendo will likely send back a different console, with your personal settings/Wii Shop account transferred and the latest updates installed. Additionally, Nintendo is no longer repairing any Wiis, so this is not even a last resort anymore.