Deploying to gh-pages from @ ee117c1 🚀

bricks.html

@@ -434,7 +434,10 @@ <h1 id="brick-prevention">Brick Prevention</h1>
 <ul>
   <li><strong>Do NOT follow old Wii modding tutorials, use old homebrew, or use video guides on the Internet unless it is EXPLICITLY RECOMMENDED by the homebrew developer.</strong></li>
   <li><strong>Do NOT, under ANY CIRCUMSTANCES, USE THE HOMEBREW APP <code class="language-plaintext highlighter-rouge">Pimp My Wii</code>. It is DANGEROUS and does things that have the ability to BRICK YOUR WII!</strong></li>
-  <li><strong>Do NOT restore NAND backups from other consoles!</strong></li>
+  <li><strong>Do NOT install IOS packs such as DARKCORP that overwrite most of your IOS with cIOS. It is DANGEROUS and heavily outdated.</strong></li>
+  <li>
+    <p><strong>Do NOT restore NAND backups from other consoles!</strong></p>
+  </li>
   <li><strong>Do NOT use a Nintendo Wi-Fi Connection service unless it is known to be RCE patched (such as <a href="wiimmfi">Wiimmfi</a>). Doing otherwise could allow a malicious actor to BRICK your Wii!</strong></li>
   <li><strong>Only install updates for your own region!</strong>.
     <ul>
@@ -453,8 +456,7 @@ <h1 id="brick-prevention">Brick Prevention</h1>
       <li>Corrupted or unstable forwarders for homebrew could cause a <a href="#banner-brick">banner brick</a>, so try to stick with loading homebrew from the Homebrew Channel unless you really want a forwarder.</li>
     </ul>
   </li>
-  <li><strong>Ensure that you know what you are doing when running homebrew apps - especially those with the ability to modify system files.</strong></li>
-  <li><strong>Be ESPECIALLY careful when using applications such as:</strong>
+  <li><strong>Ensure that you know what you are doing when running homebrew apps - especially those with the ability to modify system files. Be ESPECIALLY careful when using applications such as:</strong>
     <ul>
       <li>AnyTitle Deleter</li>
       <li>AnyRegion Changer</li>
@@ -480,30 +482,29 @@ <h1 id="brick-prevention">Brick Prevention</h1>
 
 <h1 id="diagnosis">Diagnosis</h1>
 
-<p>Here is a small section that lists out steps similar to the Wii boot process, and links to the likely corresponding brick if something fails.</p>
+<p>This is a section intended to help you diagnose a potential brick, in order by least to most brick severity. If you seem to have a brick that isn’t covered in this section or in the guide, please join the Nintendo Homebrew discord server for support.</p>
 
 <ul>
-  <li>Turn on your Wii.</li>
-  <li>Nothing happens, black screen. Wii cannot be turned on with a Wiimote, Recovery Mode cannot be started, and BootMii as boot2 is not accessible. See <a href="bricks#low-level-brick">low-level brick</a>.</li>
-  <li>Nothing happens, black screen, BUT Wii can be turned on with a Wiimote/Recovery Mode can be accessed. See <a href="bricks#wi-fi-brick">Wi-Fi brick</a>.</li>
-  <li>Nothing happens, black screen, BUT BootMii as boot2 is accessible. See <a href="bricks#ios-brick">IOS brick</a>.</li>
-  <li>Error 003. See <a href="bricks#error-003-brick">Korean Kii/Error 003 brick</a>.</li>
-  <li>Wii starts, BUT you INSTANTLY see an error that resembles the Opera web browser. See <a href="bricks#wii-menuopera-brick">Wii Menu/Opera brick</a>.</li>
-  <li>Wii starts, you see the health/warning screen, but upon pressing A to start, the screen goes black and/or freezes and does not continue. Maintenance mode is accessible. See <a href="bricks#mail-brick">mail brick</a>.</li>
+  <li>Wii starts, and progresses to the Wii Menu. No app is malfunctioning, Wii settings is error free, everything is seemingly fine. No brick.</li>
+  <li>Wii starts, and progresses to the Wii Menu.
+    <ul>
+      <li>If after acccessing a specific channel, you get <code class="language-plaintext highlighter-rouge">The system files are corrupted.</code>, see <a href="bricks#banner-brick">banner brick</a>.</li>
+      <li>If after accessing the Wii settings, you see an error that resembles the Opera web browser, see <a href="bricks#semibrick">semibrick</a>.</li>
+    </ul>
+  </li>
   <li>Wii starts, you see the health/warning screen, but upon pressing A to start, you see a black screen.
     <ul>
       <li>If this happened after installing a theme, see <a href="bricks#theme-brick">theme brick</a>.</li>
       <li>If this happened after installing a WAD, see <a href="bricks#banner-brick">banner brick</a>.</li>
       <li>If this randomly started happening, and you can access Maintenance Mode by holding +/- on the health/warning screen, see <a href="bricks#mail-brick">mail brick</a>.</li>
     </ul>
   </li>
-  <li>Wii starts, and progresses to the Wii Menu.
-    <ul>
-      <li>If after acccessing a specific channel, you get <code class="language-plaintext highlighter-rouge">The system files are corrupted.</code>, see <a href="bricks#banner-brick">banner brick</a></li>
-      <li>If after accessing the Wii settings, you see an error that resembles the Opera web browser, see <a href="bricks#semibrick">semibrick</a>.</li>
-    </ul>
-  </li>
-  <li>Wii starts, and progresses to the Wii Menu. No app is malfunctioning, Wii settings is error free, everything is seemingly fine. Unless you have some other kind of error or brick that does not fall under this umbrella (which if you do, you should come to support about), you’re good!</li>
+  <li>Wii starts, and you see the health/warning screen, but upon pressing A to start, the screen goes black and/or freezes and does not continue. Maintenance mode is accessible. See <a href="bricks#mail-brick">mail brick</a>.</li>
+  <li>Wii starts, BUT you INSTANTLY see an error that resembles the Opera web browser. See <a href="bricks#wii-menuopera-brick">Wii Menu/Opera brick</a>.</li>
+  <li>Error 003. See <a href="bricks#error-003-brick">Korean Kii/Error 003 brick</a>.</li>
+  <li>Nothing happens, black screen, BUT BootMii as boot2 is accessible. See <a href="bricks#ios-brick">IOS brick</a>.</li>
+  <li>Nothing happens, black screen, BUT Wii can be turned on with a Wiimote/Recovery Mode can be accessed. See <a href="bricks#wi-fi-brick">Wi-Fi brick</a>.</li>
+  <li>Nothing happens, black screen. Wii cannot be turned on with a Wiimote, Recovery Mode cannot be started, and BootMii as boot2 is not accessible. See <a href="bricks#low-level-brick">low-level brick</a>.</li>
 </ul>
 
 <h1 id="brick-types">Brick Types</h1>
@@ -604,16 +605,16 @@ <h4 id="symptoms-5">Symptoms</h4>
 <p><img src="/images/bricks/error-003.png" alt="" /></p>
 
 <h4 id="cause-5">Cause</h4>
-<p>When releasing the Korean Wiis, Nintendo changed the encryption key for these units specifically as a last ditch attempt at preventing homebrew. While obviously this failed, they also left a check in the System Menu versions 4.2/4.3 to determine whether or not the Korean Key is present on a system software region that is <strong>not</strong> Korean. If this check succeeds, the error triggers and the Wii is effectively bricked.</p>
+<p>When releasing the Korean Wiis, Nintendo changed the encryption key for these units specifically as a last ditch attempt at preventing homebrew. While this failed at its intended goal, Nintendo also left a check in the System Menu versions 4.2/4.3 to determine whether or not the Korean Key is present on a system software region that is <strong>not</strong> Korean. If this check succeeds, the error triggers and the Wii is effectively bricked.</p>
 
 <p>This is usually an immediate follow-up to a Wii System Update on an unsuspecting region-changed Korean Wii.</p>
 
 <h4 id="solutions-4">Solutions</h4>
-<p>Since this brick most often occurs after the Wii Menu updates, Priiloader will not be present.</p>
+<p>Since this brick most often occurs after the Wii Menu updates, Priiloader will not be present. In the case that Priiloader is present, you can simply fix it by either installing the previous Wii System Menu or removing the key with the KoreanKii homebrew app.</p>
 
 <p>Korean Wiis also released with Wii Menu 3.3, around the time that Nintendo <a href="https://wiibrew.org/wiki/3.3#Changes">fixed the Trucha bug in boot1</a>, so BootMii as Boot2 cannot be installed to or used on any Korean Wii.</p>
 
-<p>While these caveats leave the Wii in a particularly dangerous situation, <strong>it is still fixable</strong>. This involves going into <a href="recovery-mode">Recovery Mode</a>, where an exploit can be triggered in order to gain access to the Homebrew Channel and revert the conditions that caused the brick.</p>
+<p>While this leaves the Wii in a particularly dangerous situation, <strong>it is still fixable</strong>. This involves going into <a href="recovery-mode">Recovery Mode</a>, where an exploit can be triggered in order to gain access to the Homebrew Channel and revert the conditions that caused the brick. Note that you must have a drivechip in order for this method to work.</p>
 
 <h2 id="ios-brick">IOS brick</h2>
 
@@ -662,9 +663,9 @@ <h4 id="solutions-7">Solutions</h4>
 <p>First, troubleshooting must be done to determine if hardware is at fault. In the order listed, do the following:</p>
 
 <ul>
-  <li>Test to make sure that your Wii actually still functions (it accepts discs as normal, spins up correctly, Wiimotes connect) before attempting the following steps. If this is the case and only video is not being displayed, you may have an exceptionally rare failure of the video port or the GPU.</li>
-  <li>If on a Wii mini, and if a normal IOS80 was installed, see <a href="wi-fi-brick">Wi-Fi brick</a>. If steps to resolve the Wi-Fi brick failed, proceed.</li>
-  <li>Attempt to boot into <a href="recovery-mode">Recovery Mode</a> (normal Wiis only). If the Wii boots into Recovery Mode, see <a href="wi-fi-brick">Wi-Fi brick</a>. If steps to resolve the Wi-Fi brick failed, proceed.</li>
+  <li>Test to make sure that your Wii actually still functions (it accepts discs as normal, spins up correctly, Wiimotes connect) before attempting the following steps. If this is the case and only video is not being displayed, you may have a bad video cable, or an exceptionally rare failure of the video port or the GPU.</li>
+  <li>If on a Wii mini, and if a normal IOS80 was installed, see <a href="bricks#wi-fi-brick">Wi-Fi brick</a>. If steps to resolve the Wi-Fi brick failed, proceed.</li>
+  <li>Attempt to boot into <a href="recovery-mode">Recovery Mode</a> (normal Wiis only). If the Wii boots into Recovery Mode, see <a href="bricks#wi-fi-brick">Wi-Fi brick</a> or <a href="bricks#ios-brick">IOS brick</a>. If steps to resolve the Wi-Fi brick or IOS brick failed, proceed.</li>
   <li>Reseat the disc drive and attempt to boot normally. If still unsuccessful, replace the disc drive. If still unsuccessful, proceed.</li>
   <li>At this point, either there is a low level boot0/boot1 corruption, a NAND chip failure, or there is a wider unknown hardware failure. Consider consulting online help or buying another Wii.</li>
 </ul>

feed.xml

@@ -1 +1 @@
-<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.3.3">Jekyll</generator><link href="https://wii.hacks.guide/feed.xml" rel="self" type="application/atom+xml" /><link href="https://wii.hacks.guide/" rel="alternate" type="text/html" /><updated>2024-03-02T05:55:20+00:00</updated><id>https://wii.hacks.guide/feed.xml</id><title type="html">Wii Hacks Guide</title><subtitle>The complete guide to modding your Wii (and Wii mini)</subtitle><author><name>Nintendo Homebrew</name></author></feed>
+<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.3.3">Jekyll</generator><link href="https://wii.hacks.guide/feed.xml" rel="self" type="application/atom+xml" /><link href="https://wii.hacks.guide/" rel="alternate" type="text/html" /><updated>2024-03-06T15:47:27+00:00</updated><id>https://wii.hacks.guide/feed.xml</id><title type="html">Wii Hacks Guide</title><subtitle>The complete guide to modding your Wii (and Wii mini)</subtitle><author><name>Nintendo Homebrew</name></author></feed>

recovery-mode.html

@@ -360,17 +360,34 @@ <h1 id="page-title" class="page__title" itemprop="headline">Recovery Mode
 <nav class="toc">
     <header><h4 class="nav__title"><i class="fas fa-file-alt"></i> Table of Contents</h4></header>
 <ul class="toc__menu" id="markdown-toc">
-  <li><a href="#requirements" id="markdown-toc-requirements">Requirements</a></li>
-  <li><a href="#preparation" id="markdown-toc-preparation">Preparation</a></li>
-  <li><a href="#method-i---recovery-menu-to-smash-stack" id="markdown-toc-method-i---recovery-menu-to-smash-stack">Method I - Recovery Menu to Smash Stack</a></li>
-  <li><a href="#method-ii---recovery-menu-to-save-game-exploit" id="markdown-toc-method-ii---recovery-menu-to-save-game-exploit">Method II - Recovery Menu to Save Game Exploit</a></li>
-  <li><a href="#method-iii---recovery-menu-to-bluebomb" id="markdown-toc-method-iii---recovery-menu-to-bluebomb">Method III - Recovery Menu to Bluebomb</a></li>
+  <li><a href="#how-recovery-mode-works" id="markdown-toc-how-recovery-mode-works">How Recovery Mode Works</a></li>
+  <li><a href="#accessing-and-using-recovery-mode" id="markdown-toc-accessing-and-using-recovery-mode">Accessing and Using Recovery Mode</a>    <ul>
+      <li><a href="#requirements" id="markdown-toc-requirements">Requirements</a></li>
+      <li><a href="#preparation" id="markdown-toc-preparation">Preparation</a></li>
+      <li><a href="#method-i---recovery-menu-to-smash-stack" id="markdown-toc-method-i---recovery-menu-to-smash-stack">Method I - Recovery Menu to Smash Stack</a></li>
+      <li><a href="#method-ii---recovery-menu-to-save-game-exploit" id="markdown-toc-method-ii---recovery-menu-to-save-game-exploit">Method II - Recovery Menu to Save Game Exploit</a></li>
+      <li><a href="#method-iii---recovery-menu-to-bluebomb" id="markdown-toc-method-iii---recovery-menu-to-bluebomb">Method III - Recovery Menu to Bluebomb</a></li>
+    </ul>
+  </li>
 </ul>
 
   </nav>
 </aside>
 
-<p>Recovery Mode is a last resort method for recovering your Wii console from a brick before resorting to hard-modding and manual NAND programming. This mode was accessed by Nintendo employees in the factory by the usage of a special dongle, but the input needed to access it can easily be replicated in the present with a GameCube controller. Essentially, Recovery Mode puts a Wii Menu in a state where programs can be executed from a disc, including some retail games. This guide will instruct you on how to recover from bricks (especially Korean Kii/Error 003) with it.</p>
+<p>Recovery Mode is a last resort method for recovering your Wii console from a brick before resorting to hard-modding and manual NAND programming. This mode was accessed by Nintendo employees in the factory by the usage of a special dongle, but the input needed to access it can easily be replicated with a GameCube controller. Essentially, Recovery Mode puts a Wii Menu in a state where programs can be executed from a disc.</p>
+
+<h3 id="how-recovery-mode-works">How Recovery Mode Works</h3>
+
+<p>On System Menu versions 2.1 and upwards, booting into Recovery Mode will yield a verison number display on the bottom right of the screen, and will idle on the screen while waiting for a disc to be inserted. By default, Recovery Mode only boots two types of discs:</p>
+
+<ul>
+  <li>A disc whose title ID starts with a number like 0 or 1 - an autoboot disc. All retail game discs are <strong>not</strong> an autoboot disc and instead start with a letter.</li>
+  <li>A retail game disc that has a valid update partition whose version is higher than the one on the NAND.</li>
+</ul>
+
+<p>This check can be bypassed using Priiloader, which allows Recovery Mode to boot any disc that is inserted into the Wii. Unfortunately, if you can already access Priiloader, then there is no need to use Recovery Mode in the first place as you can fix your brick by booting homebrew apps in it. With this said, if you are in a situation where the only accessible option is using Recovery Mode, you must have a drivechip on hand to bypass the disc check. If are able to bypass this check one way or another, you may follow the instructions below to start from Recovery Mode and get to the HackMii installer.</p>
+
+<h3 id="accessing-and-using-recovery-mode">Accessing and Using Recovery Mode</h3>
 
 <h4 id="requirements">Requirements</h4>
 
@@ -383,11 +400,6 @@ <h4 id="requirements">Requirements</h4>
       <li>Any retail game, and access to the <a href="bluebomb">Bluebomb</a> exploit</li>
     </ul>
   </li>
-  <li>If the Diagnostic Disc Check was not previously removed with Priiloader, and no drive chip is on hand:
-    <ul>
-      <li>Super Smash Bros. Brawl (<a href="legacy-exploits#smash-stack">Smash Stack</a>)</li>
-    </ul>
-  </li>
   <li>An original revision Wii (Family Edition Wiis will not work due to the lack of GameCube ports - otherwise you must solder some on)</li>
   <li>A Windows/macOS/Linux PC with an Internet connection</li>
   <li>An SD Card formatted to FAT32</li>
@@ -397,16 +409,29 @@ <h4 id="preparation">Preparation</h4>
 
 <p class="notice--warning">In order to hold down all 4 individual D-Pad buttons on a GameCube controller, you may be required to take the casing apart.</p>
 
-<p>First of all, verify that your Wii can boot into Recovery Mode <em>at all</em>. This involves taking a GameCube controller, plugging it into the fourth controller port on a Wii, and simultaneously holding down the 4 individual D-Pad buttons on boot. If everything goes right, you should see a screen similar to the above. Bear in mind that if you are on a System Menu version on 2.0 or prior, you will not see a version number display at all, and you will not be able to boot from discs.</p>
+<p>First of all, verify that your Wii can boot into Recovery Mode <em>at all</em>. This involves taking a GameCube controller, plugging it into the fourth controller port on a Wii, and simultaneously holding down the 4 individual D-Pad buttons on boot. If everything goes right, you should see a screen similar to the above. As stated above, if you are on a System Menu version on 2.0 or prior, you will not see a version number display at all and you will not be able to boot from discs.</p>
 
 <h4 id="method-i---recovery-menu-to-smash-stack">Method I - Recovery Menu to Smash Stack</h4>
 
+<ol>
+  <li>If you have a Super Smash Bros. Brawl game disc, you can use <a href="legacy-exploits#smash-stack">Smash Stack</a> to load the HackMii installer off of your SD card.</li>
+  <li>Boot into Recovery Mode, and insert the Super Smash Bros. Brawl game disc. It should boot at this point.</li>
+  <li>Follow the instructions for the exploit on Wiibrew.</li>
+</ol>
+
 <h4 id="method-ii---recovery-menu-to-save-game-exploit">Method II - Recovery Menu to Save Game Exploit</h4>
 
+<ol>
+  <li>If you already have a save game on your Wii for a save game exploit listed in <a href="legacy-exploits">Legacy Exploits</a>, you may use a respective exploit in order to load the HackMii installer.</li>
+  <li>Boot into Recovery Mode, and insert your respective game disc. It should boot at this point.</li>
+  <li>Follow the instructions for the exploit on Wiibrew.</li>
+</ol>
+
 <h4 id="method-iii---recovery-menu-to-bluebomb">Method III - Recovery Menu to Bluebomb</h4>
 
-<hr />
-<p>Under Construction</p>
+<p>You can also use Bluebomb as a means of recovery. At this time, we are still drawing up instructions for this section.</p>
+
+<p class="notice--info">At this point, you should be able to install the Homebrew Channel and access homebrew on your SD card that can be used to revert your brick.</p>
 
 <p class="notice--info"><a href="bricks">Return to Bricks</a></p>
 

site-navigation.html

@@ -402,7 +402,8 @@ <h1 id="page-title" class="page__title" itemprop="headline">Site Navigation
   <li><a href="priiloader">Priiloader</a></li>
   <li><a href="hackmii">Relaunching the HackMii Installer</a></li>
   <li><a href="update">Updating Wii Menu to v4.3</a></li>
-  <li><a href="wii-factory-reset">Restoring the Wii NAND to Stock</a></li>
+  <li><a href="recovery-mode">Recovery Mode</a></li>
+  <li><a href="wii-factory-reset">Restoring The Wii NAND to Stock</a></li>
   <li><a href="wnd-mini">Wii mini NAND Dumper</a></li>
   <li><a href="yawmme">YAWM ModMii Edition</a></li>
 </ul>