Guide Overhaul
This commit is contained in:
grunt22fox
lifehackerhansol
parent
82e9f355c1
commit
85c89c6011
223 changed files with 621 additions and 348 deletions
|
|
@ -103,7 +103,7 @@ analytics:
|
|||
# Site Author
|
||||
author:
|
||||
name : "Nintendo Homebrew"
|
||||
avatar : # path of avatar image, e.g. "/assets/images/bio-photo.jpg"
|
||||
avatar : # path of avatar image, e.g. "/assets/images/site-config/bio-photo.jpg"
|
||||
bio : "Nintendo Homebrew Community"
|
||||
location : "Nullsec"
|
||||
email :
|
||||
|
|
|
|||
|
|
@ -1,22 +1,21 @@
|
|||
<!-- start custom head snippets -->
|
||||
<!-- insert favicons. use http://realfavicongenerator.net/ -->
|
||||
|
||||
<link rel="apple-touch-icon" sizes="180x180" href="{{ base_path }}/images/apple-touch-icon.png?v=PYEmwKvQAx">
|
||||
<link rel="icon" type="image/png" href="{{ base_path }}/images/favicon-32x32.png?v=PYEmwKvQAx" sizes="32x32">
|
||||
<link rel="icon" type="image/png" href="{{ base_path }}/images/favicon-194x194.png?v=PYEmwKvQAx" sizes="194x194">
|
||||
<link rel="icon" type="image/png" href="{{ base_path }}/images/android-chrome-192x192.png?v=PYEmwKvQAx" sizes="192x192">
|
||||
<link rel="icon" type="image/png" href="{{ base_path }}/images/favicon-16x16.png?v=PYEmwKvQAx" sizes="16x16">
|
||||
<link rel="manifest" href="{{ base_path }}/images/manifest.json?v=PYEmwKvQAx">
|
||||
<link rel="mask-icon" href="{{ base_path }}/images/safari-pinned-tab.svg?v=PYEmwKvQAx" color="#2E3440">
|
||||
<link rel="shortcut icon" href="{{ base_path }}/images/favicon.ico?v=PYEmwKvQAx">
|
||||
<link rel="apple-touch-icon" sizes="180x180" href="{{ base_path }}/images/site-config/apple-touch-icon.png?v=PYEmwKvQAx">
|
||||
<link rel="icon" type="image/png" href="{{ base_path }}/images/site-config/favicon-16x16.png?v=PYEmwKvQAx" sizes="16x16">
|
||||
<link rel="icon" type="image/png" href="{{ base_path }}/images/site-config/favicon-32x32.png?v=PYEmwKvQAx" sizes="32x32">
|
||||
<link rel="icon" type="image/png" href="{{ base_path }}/images/site-config/favicon-194x194.png?v=PYEmwKvQAx" sizes="194x194">
|
||||
<link rel="icon" type="image/png" href="{{ base_path }}/images/site-config/android-chrome-192x192.png?v=PYEmwKvQAx" sizes="192x192">
|
||||
<link rel="manifest" href="{{ base_path }}/assets/js/manifest.json?v=PYEmwKvQAx">
|
||||
<link rel="mask-icon" href="{{ base_path }}/images/site-config/safari-pinned-tab.svg?v=PYEmwKvQAx" color="#2E3440">
|
||||
<link rel="shortcut icon" href="{{ base_path }}/images/site-config/favicon.ico?v=PYEmwKvQAx">
|
||||
<meta name="apple-mobile-web-app-title" content="Guide">
|
||||
<meta name="application-name" content="Guide">
|
||||
<meta name="msapplication-TileColor" content="#2E3440">
|
||||
<meta name="msapplication-TileImage" content="{{ base_path }}/images/mstile-144x144.png?v=PYEmwKvQAx">
|
||||
<meta name="msapplication-config" content="{{ base_path }}/images/browserconfig.xml?v=PYEmwKvQAx">
|
||||
<meta name="msapplication-TileImage" content="{{ base_path }}/images/site-config/mstile-144x144.png?v=PYEmwKvQAx">
|
||||
<meta name="msapplication-config" content="{{ base_path }}/assets/xml/browserconfig.xml?v=PYEmwKvQAx">
|
||||
<meta name="theme-color" content="#2E3440">
|
||||
|
||||
|
||||
{% assign split_path = page.path | split: "/" %}
|
||||
{% assign locale = split_path[1] %}
|
||||
{% if locale == 'en_US' %}
|
||||
|
|
|
|||
20
_includes/identify-console.html
Normal file
20
_includes/identify-console.html
Normal file
|
|
@ -0,0 +1,20 @@
|
|||
<div class="revisiontable auto-grid-width">
|
||||
<div align="center" class="r1 c1 console-model">
|
||||
Wii
|
||||
</div>
|
||||
<div align="center" class="r1 c2 console-model">
|
||||
Wii Mini
|
||||
</div>
|
||||
<div align="center" class="r1 c3 console-model">
|
||||
Wii U
|
||||
</div>
|
||||
<div class="r2 c1 console-img auto-grid-height">
|
||||
<img src="../images/get-started/wii.png" alt="Wii Console">
|
||||
</div>
|
||||
<div class="r2 c2 console-img auto-grid-height">
|
||||
<img src="../images/get-started/wii-mini.png" alt="Wii Mini Console">
|
||||
</div>
|
||||
<div class="r2 c3 console-img auto-grid-height">
|
||||
<img src="../images/get-started/wii-u.png" alt="Wii U Console">
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -5,7 +5,7 @@ excerpt: "Page not found. Your pixels are in another canvas." #
|
|||
sitemap: false
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
Sorry, but the page you were trying to view does not exist.
|
||||
{: .notice--warning}
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ It is **strongly** advised against using **any** video guide for hacking your Wi
|
|||
If you need help with anything regarding this tutorial, please join [the Wii mini Hacking Discord server](https://discord.gg/6ryxnkS) (recommended)
|
||||
{: .notice--info}
|
||||
|
||||
|
||||
|
||||
|
||||
BlueBomb is an exploit that takes advantage of a flaw in the Wii and Wii mini's Bluetooth libraries. Although it is the only exploit that works for the Wii mini, BlueBomb can run on the original Wii as well. This exploit also enables recovery from certain bricks, such as a banner brick.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,20 +4,28 @@ title: "BootMii Backup"
|
|||
|
||||
{% include toc title="Table of Contents" %}
|
||||
|
||||
|
||||
|
||||
You need an **SD card** to create a NAND backup using BootMii.
|
||||
If you do not have one, you can skip this page, although it is highly recommended to make a NAND backup if you can.
|
||||
{: .notice--warning}
|
||||
|
||||
BootMii installed as boot2 is only available on Wii's shipped before mid-late-2008. If you don't have one of these Wii's, you will need to install as an IOS.
|
||||
{: .notice--info}
|
||||
|
||||
|
||||
BootMii allows for backing up and restoring your Wii's NAND storage. This page will guide you in backing up your Wii's NAND to an SD Card, which you can then use however you like.
|
||||
|
||||
Family edition Wiis (Wiis without GameCube ports) CANNOT restore NAND backups. This is because of the lack of GameCube ports which are required on non-boot2 Wiis to enter the restoration confirmation code. Please bear this in mind before you make one, even though it is recommended to do so anyway.
|
||||
{: .notice--danger}
|
||||
|
||||
You need an **SD card** to use BootMii at all, but especially to create a NAND backup. If you do not have an SD card on hand right now, you can skip this page, but you are highly recommended to return to this page later to back up your NAND.
|
||||
{: .notice--warning}
|
||||
|
||||
Navigating BootMii is not possible using a Wii Remote. You must use the POWER and RESET buttons on your console, or a GameCube controller plugged into port 1. To navigate between options, press POWER on your Wii (or left/right on the +Control Pad on a GameCube controller). To select an option, press RESET on your Wii or A on your GameCube controller. You will NEED to use a GameCube controller to restore a NAND backup in the future if BootMii is installed as IOS.
|
||||
{: .notice--info}
|
||||
|
||||
If the `Launch BootMii` button does not appear in the Homebrew Channel, please [re-launch the HackMii Installer](hackmii) and install BootMii.
|
||||
{: .notice--warning}
|
||||
|
||||
If the screen stays black and the blue disc drive light is blinking upon launching BootMii, you are missing the BootMii files on your SD card. Download [this zip file](https://static.hackmii.com/bootmii_sd_files.zip) and extract it to the root of your SD card, then try again.
|
||||
{: .notice--warning}
|
||||
|
||||
#### Requirements
|
||||
|
||||
* An SD card with at least 512MB of free space
|
||||
* An SD card with a minimum 512MB of free space, 1GB or more recommended
|
||||
|
||||
#### Instructions
|
||||
|
||||
|
|
@ -26,30 +34,17 @@ If you have BootMii installed as boot2 you will need to launch BootMii by restar
|
|||
|
||||
1. Launch the Homebrew Channel.
|
||||
1. Press the HOME Button, then select "Launch BootMii".
|
||||
|
||||
|
||||
If the `Launch BootMii` button does not appear, please [re-launch the HackMii Installer](hackmii) and install BootMii.
|
||||
{: .notice--info}
|
||||
|
||||
Navigating BootMii is not possible using a Wii Remote. You must use the POWER and RESET buttons on your console, or a GameCube controller plugged into port 1. To navigate between options, press POWER on your Wii (or left/right on the +Control Pad
|
||||
on a GameCube controller). To select an option, press RESET on your Wii or A on your GameCube controller.
|
||||
{: .notice--info}
|
||||
|
||||
If the screen stays black and the blue disc drive light is blinking, you are missing the BootMii files on your SD card.
|
||||
Download [this zip file](https://static.hackmii.com/bootmii_sd_files.zip) and extract it to the root of your SD card, then try again.
|
||||
{: .notice--warning}
|
||||
|
||||
|
||||
1. Select the Options button (the icon with the gears).
|
||||
|
||||
1. Select the first button to the left.
|
||||
|
||||
+ A NAND backup will start. You can watch the progress on the screen.
|
||||
+ "Bad Blocks" are normal. Don't worry when you see some on a NAND backup.
|
||||
|
||||
1. Select the first button to the left. A NAND backup will start. You can watch the progress on the screen.
|
||||
|
||||
+ "Bad Blocks" are normal, and mostly originate from the factory due to NAND binning. Don't worry when you see some on a NAND backup.
|
||||
+ After this step, it will verify the backup. Ideally, all the blocks should be green after the verification process.
|
||||
1. When the backup is complete, exit the NAND backup screen by pressing any button.
|
||||
|
||||
1. To exit BootMii, press the Back button (the one with the arrow) and then you can press either the Wii Menu button or the Homebrew Channel button to exit where you want to.
|
||||
|
||||
|
||||
1. To exit BootMii, press the Back button (the one with an arrow) and then you can press either the Wii Menu button or the Homebrew Channel button to exit BootMii.
|
||||
|
||||
|
||||
<div id="restore-notice" class="notice" markdown="1">
|
||||
To restore from a NAND backup on your SD card, you can follow the instructions for [RestoreMii](bootmiirecover).
|
||||
|
|
@ -65,5 +60,5 @@ Two files will have been created on the root of your SD Card; `nand.bin` and `ke
|
|||
{: .notice--info}
|
||||
|
||||
[Continue to Priiloader Installation](priiloader)<br>
|
||||
Priiloader adds a level of brick protection, and is highly recommended, especially if you were only able to install BootMii as IOS.
|
||||
Priiloader adds a secondary level of brick protection, and is highly recommended even if BootMii was installed as boot2. For BootMii on IOS, it is effectively required to boot in the case of a more severe brick.
|
||||
{: .notice--info}
|
||||
|
|
|
|||
|
|
@ -2,54 +2,52 @@
|
|||
title: "BootMii Recovery"
|
||||
---
|
||||
|
||||
#### Requirements
|
||||
* An earlier NAND Backup made by [BootMii](https://wii.guide/bootmii)
|
||||
* **A GameCube Controller**
|
||||
{% include toc title="Table of Contents" %}
|
||||
|
||||
#### Important notes
|
||||
This guide will provide instructions on how to restore a backup of your NAND with BootMii. Please bear in mind that this is usually the <strong>last resort</strong> method of repairing a brick if you have one, and if it does not fix your issue, you may have to seek support. If you are still able to enter BootMii, make an attempt to enter the Homebrew Channel instead so that you may attempt to [identify and repair the brick](bricks) using other methods.
|
||||
|
||||
**Restoring a NAND backup is usually a last resort.**
|
||||
|
||||
If you are even able to enter BootMii, enter the Homebrew Channel instead, and try your best to [identify what caused the brick](bricks) and reverse it.
|
||||
|
||||
If you have not done anything to cause a brick (or you're starting up your Wii after a long time), then it is probably a [Wi-Fi Brick](bricks#wi-fi-brick).
|
||||
If you have BootMii installed as boot2, you will need to launch BootMii by restarting the console. Skip steps 1 and 2 if this is the case.
|
||||
{: .notice--info}
|
||||
|
||||
**Family edition Wiis (Wiis without GameCube ports) CANNOT restore NAND backups.**
|
||||
If the screen stays black and the blue disc drive light is blinking upon launching BootMii, you are missing the BootMii files on your SD card. Download [this zip file](https://static.hackmii.com/bootmii_sd_files.zip) and extract it to the root of your SD card, then try again.
|
||||
{: .notice--warning}
|
||||
|
||||
Family edition Wiis released very well after [boot1 was patched](https://wiibrew.org/wiki/Wii_Family_Edition#Changes_carried_over_from_previous_revisions), which means you will not have BootMii as boot2.
|
||||
|
||||
If you do not have BootMii as boot2, RestoreMii will prompt you for the Konami code via a GameCube Controller.
|
||||
Family edition Wiis (Wiis without GameCube ports) CANNOT restore NAND backups. This is because of the lack of GameCube ports which are required on non-boot2 Wiis to enter the restoration confirmation code. For additional help, please seek support.
|
||||
{: .notice--danger}
|
||||
|
||||
Family edition Wiis do not have ports for GameCube controllers.
|
||||
DO NOT restore an unverified NAND backup, or one that is not from your Wii: this may lead to a WORSE BRICK. The same goes for using faulty SD cards.
|
||||
{: .notice--danger}
|
||||
|
||||
**Restoring an unverified NAND backup may lead to a WORSE BRICK.**
|
||||
#### Requirements
|
||||
* An earlier NAND Backup made by [BootMii](bootmii)
|
||||
|
||||
The same also goes for faulty SD cards.
|
||||
#### Restoring individual data from a NAND backup
|
||||
|
||||
**Want to restore individual data from your NAND backup?**
|
||||
There is likely a much safer and faster way to bring individual data back to your Wii, likely involving the use of Dolphin Emulator.
|
||||
|
||||
There is likely a much safer and faster way to bring it back to your Wii, likely involving the use of Dolphin Emulator.
|
||||
|
||||
For example, if you want to restore your Wii Message Board data, use Dolphin to import your NAND backup, find `Wii/title/00000001/00000002/data/cdb.vff`, copy it to your SD card as `cdbackup.vff`, and use [cdbackup](https://oscwii.org/library/app/cdbackup) to restore it.
|
||||
For example, if you want to restore your Wii Message Board data, use Dolphin to import your NAND backup. In Dolphin, go to `File -> Open User Folder`, and find `Wii/title/00000001/00000002/data/cdb.vff`, copy it to your SD card, and use [WiiXplorer](https://oscwii.org/library/app/wiixplorer) to restore it in the corresponding location.
|
||||
|
||||
If you want to restore a game's save data, use Dolphin to import your NAND backup, use `Tools > Export All Wii Saves` to export all your saves to your SD card, and use Data Management to move it to your Wii.
|
||||
|
||||
#### Instructions
|
||||
#### Important preliminary notes
|
||||
|
||||
If you have BootMii installed as boot2, you will need to launch BootMii by restarting the console. Skip steps 1 and 2 if this is the case.
|
||||
{: .notice}
|
||||
+ If you have not done anything to cause a brick (or you're starting up your Wii after a long time), then it is probably a [Wi-Fi Brick](bricks#wi-fi-brick).
|
||||
|
||||
+ If you have BootMii as IOS installed, RestoreMii will prompt you for the Konami code via a GameCube Controller.
|
||||
|
||||
+ You must use the POWER (right) and RESET (select) buttons on your console, or a GameCube controller plugged into port 1 to navigate BootMii. To navigate with a GameCube controller, click left/right on the +Control Pad on a GameCube controller. To select, press A.
|
||||
|
||||
#### Instructions
|
||||
|
||||
1. Launch the Homebrew Channel.
|
||||
1. Press the HOME Button, then select "Launch BootMii".
|
||||
|
||||
You must use the POWER (right) and RESET (select) buttons on your console, or a GameCube controller plugged into port 1. To navigate with a GameCube controller, click left/right on the +Control Pad
|
||||
on a GameCube controller. To select, press A.
|
||||
{: .notice--info}
|
||||
|
||||
1. Select the Options button (the icon with the gears).
|
||||
|
||||
1. Select the RestoreMii button.
|
||||
|
||||
1. On your GameCube controller, input the Konami code: ↑, ↑, ↓, ↓, ←, →, ←, →, B, A, START
|
||||
1. If BootMii is installed as IOS, input the Konami code on your GameCube controller: ↑, ↑, ↓, ↓, ←, →, ←, →, B, A, START
|
||||
1. After the recovery ended, you should see a text say `I HAZ SUCCESS!`, otherwise `I HAZ FAIL`. Hit any button on your Wii console or GCN controller.
|
||||
|
||||
If you were restoring a NAND backup in order to repair a brick and this did not fix your issue, please consult [the bricks portion](bricks) of this guide.
|
||||
{: .notice--info}
|
||||
|
|
|
|||
|
|
@ -4,42 +4,78 @@ title: "Bricks"
|
|||
|
||||
{% include toc title="Table of Contents" %}
|
||||
|
||||
A "Brick" usually means your Wii has reached a state where, its only use is that of a literal [brick](https://wikipedia.org/wiki/Brick). <br>
|
||||
Bricks can occur for a variety of reasons, usually caused by improper system modifications via homebrew.
|
||||
A "Brick" usually means your Wii has reached a state where its next purpose in existing is likely that of a doorstop, or a display figure. <br>
|
||||
Bricks can occur for a variety of reasons, however usually it results through corrupted software, or from improper modifications made through homebrew.
|
||||
|
||||
Here, we will discuss the different types of bricks, as well as some potential solutions.
|
||||
# Brick Prevention
|
||||
|
||||
## Banner brick
|
||||
Preventing a brick involves many rules that range between common sense and fail-safe backups. Here are the general recommendations of what not to do:
|
||||
|
||||
#### Cause
|
||||
Banner bricks occur if you install a WAD file that has an invalid Wii Menu banner or icon.
|
||||
+ **DO NOT FOLLOW OLD WII MODDING TUTORIALS, USE OLD HOMEBREW, OR USE OLD VIDEO GUIDES ON THE INTERNET UNLESS EXPLICITLY RECOMMENDED BY THE DEVELOPER**.
|
||||
+ **DO NOT, UNDER ANY CIRCUMSTANCES, USE THE HOMEBREW APP `Pimp My Wii`. IT IS DANGEROUS, AND DOES THINGS THAT HAVE THE ABILITY TO BRICK YOUR WII!**
|
||||
+ **DO NOT USE NAND BACKUPS FROM OTHER CONSOLES ON BOOTMII**.
|
||||
+ **DO NOT USE A NINTENDO WI-FI CONNECTION SERVICE UNLESS IT IS RCE PATCHED, SUCH AS `Wiimmfi`. DOING OTHERWISE COULD PLACE YOUR WII AT RISK OF BEING BRICKED!**
|
||||
+ **ONLY INSTALL UPDATES FOR YOUR OWN REGION AND PLAY GAMES ONLY FROM YOUR OWN REGION**.
|
||||
+ In most cases, playing a game from another region should simply cause the game to just not boot, unless you have sufficiently modified the console to do otherwise. With that said, extraordinary events have the potential to cause a brick, so the risk is better left untouched.
|
||||
+ Installing updates from another region could have no effect at best, but result in a [Korean Kii/Error 003](bricks#korean-kiierror-003-brick) brick at worst. To prevent this from happening if you bought a pre-owned Wii, run [SysCheck](syscheck) to verify the original region of your console. If it is Korean, be EXTREMELY careful with making system updates to your console, and consider seeking support for help.
|
||||
+ **DO NOT DELETE OR MODIFY SYSTEM FILES, AND DO NOT INSTALL SYSTEM FILE MODS UNLESS YOU KNOW ABSOLUTELY WHAT YOU ARE DOING**.
|
||||
+ An example of this going wrong is replacing IOS80 on Wii Mini - this can easily result in a [Wi-Fi Brick](bricks#wi-fi-brick).
|
||||
+ **DO NOT INSTALL HOMEBREW THAT WAS NOT OBTAINED FROM A TRUSTED SOURCE SUCH AS OSC, IF IT WAS NOT LISTED ON THIS GUIDE, OR IF THE SOURCE CODE IS NOT AVAILABLE**.
|
||||
+ There have been incidents of malicious software being developed for the Wii in the past, while other apps are just badly developed. Make sure that you know what you are installing, and only install what you need.
|
||||
+ Corrupted or unstable forwarders for homebrew could cause a [banner brick](#banner-brick), try to stick with loading homebrew from the Homebrew Channel unless you really want a forwarder.
|
||||
+ **ENSURE THAT YOU KNOW WHAT YOU ARE DOING WHEN RUNNING HOMEBREW APPS, ESPECIALLY THOSE WITH THE ABILITY TO MODIFY SYSTEM FILES**.
|
||||
+ **BE EXCEPTIONALLY CAREFUL WHEN USING APPS SUCH AS:**
|
||||
+ AnyTitle Deleter
|
||||
+ AnyRegion Changer
|
||||
+ KoreanKii (secondary cause of [Korean Kii/Error 003](bricks#korean-kiierror-003-brick) brick)
|
||||
+ Firmware Downgraders
|
||||
+ Any other app that modifies critical NAND files
|
||||
+ **DO NOT TOUCH THE WII'S POWER SOURCE OR POWER BUTTONS WHEN INSTALLING OR MODIFYING CRITICAL SYSTEM CONTENT**.
|
||||
+ If you are in the middle of an electrical storm, maybe it's better to just do it afterwards.
|
||||
+ This applies to dangerous processes such as BootMii NAND restoration, which could lead to a [full brick](#low-level-brick) if anything goes wrong.
|
||||
|
||||
#### Solutions
|
||||
If you have [Priiloader](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.
|
||||
In any case, you should absolutely:
|
||||
+ Have BootMii installed as boot2 if available, but otherwise as IOS.
|
||||
+ Have Priiloader installed regardless of the above.
|
||||
+ Back your NAND up with BootMii and always have a valid spare copy on hand, but especially before attempting anything risky. Note that on some bricks, BootMii is not accessible, so plan ahead.
|
||||
|
||||
If you don't have Priiloader, Maintenance mode may be worth a try.
|
||||
Hold down `+` and `-` on the Health and Safety screen. (do not press `A`!)
|
||||
# Diagnosis
|
||||
|
||||
If you are fortunate enough to get to the Wii Menu, enter the Homebrew Channel and uninstall the faulty WAD.
|
||||
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.
|
||||
|
||||
## Theme brick
|
||||
+ Turn on Wii.
|
||||
+ 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 [low-level brick](bricks#low-level-brick).
|
||||
+ Nothing happens, black screen, BUT Wii can be turned on with a Wiimote/Recovery Mode can be accessed. See [Wi-Fi brick](bricks#wi-fi-brick).
|
||||
+ Nothing happens, black screen, BUT BootMii as boot2 is accessible. See [IOS brick](bricks#ios-brick).
|
||||
+ Error 003. See [Korean Kii/Error 003 brick](bricks#error-003-brick).
|
||||
+ Wii starts, BUT you INSTANTLY see an error that resembles the Opera web browser. See [Wii Menu/Opera brick](bricks#wii-menuopera-brick).
|
||||
+ 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. Maintenence mode is accessible. See [mail brick](bricks#mail-brick).
|
||||
+ Wii starts, you see the health/warning screen, but upon pressing A to start, you see a black screen.
|
||||
+ If this happened after installing a theme, see [theme brick](bricks#theme-brick).
|
||||
+ If this happened after installing a WAD, see [banner brick](bricks#banner-brick).
|
||||
+ If this randomly started happening, and you can access Maintenence Mode by holding +/- on the health/warning screen, see [mail brick](bricks#mail-brick).
|
||||
+ Wii starts, and progresses to the Wii Menu.
|
||||
+ If after acccessing a specific channel, you get `The system files are corrupted.`, see [banner brick](bricks#banner-brick)
|
||||
+ If after accessing the Wii settings, you see an error that resembles the Opera web browser, see [semibrick](bricks#semibrick).
|
||||
+ 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!
|
||||
|
||||
#### Cause
|
||||
A theme brick occurs when a wrongly formatted theme is installed.
|
||||
# Brick Types
|
||||
|
||||
#### Solutions
|
||||
To resolve this issue, open HBC through Priiloader and access MyMenuifyMod to install a default theme.
|
||||
Here, the different Wii bricks will be discussed in order of severity, with symptoms, causes, and solutions.
|
||||
|
||||
## Semibrick
|
||||
|
||||
#### Symptoms
|
||||
When navigating to Wii Settings, you instead get an error from the Opera web browser along the lines of `You tried to access the address (URL), which is currently unavailable.` In some cases, some parts of the Wii Settings menu may still be accessible, but other parts may not (such as the Country menu).
|
||||
|
||||
#### Cause
|
||||
A semibrick occurs when a different region Wii Menu or a different region custom theme is installed.
|
||||
This causes the Wii to fail to find the Wii settings page files.
|
||||
A semibrick occurs when a different region Wii Menu or a different region custom theme is installed. As the Wii Settings menu is rendered using HTML pages with Opera, themes often replace these pages and put them in different directories; essentially leading to a `404 Not Found` error but in the form of a console brick.
|
||||
|
||||
|
||||
#### Solutions
|
||||
If this was caused by a theme you installed, use MyMenuifyMod to re-download the original theme file.
|
||||
Verify in AnyRegion Changer that your console region is the same as the theme or Wii Menu that you have installed.
|
||||
|
||||
If this was caused by a theme you installed, use MyMenuifyMod to reinstall the original theme file.
|
||||
|
||||
If this was caused by a Wii Menu WAD you installed, use [NUS Downloader](https://wiibrew.org/wiki/NUSD) to re-obtain your original Wii Menu.
|
||||
|
||||
|
|
@ -48,7 +84,51 @@ Be cautious when downloading the Wii Menu WAD. Make sure to pick the same versio
|
|||
|
||||
If you are actually in the process of a region change, use [ARC-ME](https://github.com/modmii/Any-Region-Changer-ModMii-Edition/releases) to automatically fix all your region settings to match your Wii Menu.
|
||||
|
||||
## Wii Menu brick
|
||||
## Banner brick
|
||||
|
||||
#### Symptoms
|
||||
Attempt to start the Wii - warning/press A screen shows up, and when A is pressed, the screen passes normally; however, beyond this point, nothing happens and the Wii remains on a black screen. This happened after installing a WAD and rebooting, or returning to the Wii Menu. Alternatively, the Wii Menu can still be accessed, but opening the corrupt channel results in the console freezing. In some cases, you may see the "System files are corrupted" screen.
|
||||
|
||||
|
||||
#### Cause
|
||||
Banner bricks occur if you install a WAD file that has an invalid Wii Menu banner or icon.
|
||||
|
||||
#### Solutions
|
||||
If you are somehow able to still access the Wii Menu, go into the Homebrew Channel and use [YAWMME](yawmme) or your current WAD manager to uninstall the corrupt channel.
|
||||
|
||||
If you cannot access the Wii Menu, and have [Priiloader](priiloader) installed, enter it by holding RESET while turning your Wii on. Select Homebrew Channel, then uninstall the corrupt channel.
|
||||
|
||||
If you don't have or can't access Priiloader, Maintenance mode may be worth a try. Hold down `+` and `-` on the Health and Safety screen (do not press `A`!).
|
||||
|
||||
## Theme brick
|
||||
|
||||
#### Symptoms
|
||||
|
||||
Attempt to start the Wii - warning/press A screen shows up, and when A is pressed, the screen passes normally; however, beyond this point, nothing happens and the Wii remains on a black screen. This happened after installing a theme.
|
||||
|
||||
#### Cause
|
||||
A theme brick occurs when a wrongly formatted theme is installed.
|
||||
|
||||
#### Solutions
|
||||
To resolve this issue, open HBC through Priiloader or BootMii as boot2 and access MyMenuifyMod to install a default theme such as the base Wii Menu theme. Alternatively, go into [YAWMME](yawmme) and install the CORRECT default Wii Menu WAD for your region and version.
|
||||
|
||||
## Mail brick
|
||||
|
||||
#### Symptoms
|
||||
Attempt to start the Wii - warning/press A screen shows up, and when A is pressed, the screen passes normally; however, beyond this point, nothing happens and the Wii remains on a black screen. Maintenence mode is still accessible.
|
||||
|
||||
#### Cause
|
||||
A mail brick occurs when a Wii has too much mail to handle, or when malformed mail is in the Wii Message Board, causing a crash upon booting through normal means. Because the Wii Message Board is always drawn below Wii channels, this causes the Wii Menu to fail as it is always open.
|
||||
|
||||
#### Solution
|
||||
By entering holding + and - on the warning screen, Maintenence mode can be entered, where the Wii Message Board is not loaded at all. If the Homebrew Channel is not installed and the system menu is at Wii menu version 2.0 or later, follow [str2hax](str2hax). Otherwise, see [Bluebomb](bluebomb).
|
||||
|
||||
From here, the Homebrew Browser can be loaded and mail can be deleted by using WiiXplorer and navigating to `TO BE COMPLETED, INSERT INFORMATION ON HOW TO SOLVE MAIL BRICK`
|
||||
|
||||
## Wii Menu/Opera brick
|
||||
|
||||
#### Symptoms
|
||||
When starting the Wii, you instead get an error from the Opera web browser along the lines of `You tried to access the address (URL), which is currently unavailable.` This will happen every time you start the Wii, and cannot be bypassed in any other means.
|
||||
|
||||
#### Cause
|
||||
This brick is a more fatal version of a [Semibrick](#semibrick). If your SYSCONF gets corrupt or damaged, the Wii will regenerate it and start the setup phase.
|
||||
|
|
@ -60,25 +140,65 @@ However, the setup pages are in a similar location to the Wii settings pages. If
|
|||
|
||||
If you still have [Priiloader](priiloader), use it to enter the Homebrew Channel and re-install the original theme file/original Wii Menu.
|
||||
|
||||
In case you do not have Priiloader, you can try [BlueBomb](bluebomb).
|
||||
In case you do not have Priiloader or your Wii is not modded, you can try [BlueBomb](bluebomb).
|
||||
|
||||
## Mail brick
|
||||
Alternatively, Recovery Mode can be used by holding all 4 buttons on the D-Pad of a GameCube controller that is plugged into the fourth controller port of the Wii.
|
||||
|
||||
## Korean Kii/Error 003 Brick
|
||||
|
||||
#### Symptoms
|
||||
Screen shows up as listed below on normal boot.
|
||||
|
||||
`Error:003`<br>
|
||||
`unauthorized device has been detected.`<br>
|
||||
|
||||
|
||||
#### Cause
|
||||
A mail brick happens when your Wii has a lot of mail. This will make the Wii crash.
|
||||
|
||||
This brick happens when a non-Korean Wii Menu on 4.2 or 4.3 detects that the Korean common key is present.
|
||||
|
||||
This is usually an immediate follow-up to a Wii System Update on an unsuspecting region-changed Korean Wii.
|
||||
#### Solutions
|
||||
|
||||
Since this brick most often occurs after the Wii Menu updates, Priiloader will not be present.
|
||||
|
||||
Korean Wiis also released with Wii Menu 3.3, around the time that Nintendo [fixed the Trucha bug in boot1](https://wiibrew.org/wiki/3.3#Changes), so BootMii as Boot2 cannot be installed to or used on any Korean Wii.
|
||||
|
||||
While this brick is infamous and hard to fix, **it is still fixable**. This involves one of two solutions.
|
||||
|
||||
##### Recovery Mode
|
||||
|
||||
See [recovery mode](recovery-mode.md).
|
||||
|
||||
##### BlueBomb
|
||||
|
||||
If you have a drive chip on hand, [BlueBomb](bluebomb) is accessible. It is not known exactly why one is needed to use it, but without one, BlueBomb cannot progress past stage 0.
|
||||
|
||||
## IOS brick
|
||||
|
||||
#### Symptoms
|
||||
This brick will appear identical to a low-level brick due to a Wii Menu failure via IOS; however there is not a full low-level NAND corruption, or a low-level hardware failure. Due to this, BootMii as boot2 is still bootable.
|
||||
|
||||
#### Cause
|
||||
This brick happens when the Wii Menu's IOS is a [stub](http://wiibrew.org/wiki/Stub_IOS). This is usually the consequence of attempting to downgrade your Wii menu. If this error began happening after installing a normal IOS80 to a Wii Mini, see [Wi-Fi brick](wi-fi-brick).
|
||||
|
||||
#### Solutions
|
||||
To fix a mail brick, enter Maintenance mode by holding `+` and `-` on the Health and Safety screen. (do not press `A`!) <br>
|
||||
Enter the Homebrew Channel, and use [cdbackup](https://oscwii.org/library/app/cdbackup) to delete your Wii Message Board data.
|
||||
You must have BootMii as boot2 to fix this. Recovery mode is not accessible due to a broken IOS, and Priiloader will not work. If these conditions are not met, see [low-level brick](bricks#low-level-brick).
|
||||
|
||||
You can either restore a NAND backup, or do this:
|
||||
|
||||
1. Use [NUS Downloader](https://wiibrew.org/wiki/NUSD) to pack a WAD of your original Wii Menu.
|
||||
1. Use BootMii to enter the Homebrew Channel, and use a WAD manager to install the Wii Menu WAD.
|
||||
|
||||
## Wi-Fi brick
|
||||
|
||||
#### Symptoms
|
||||
This brick appears identical to a low-level brick, however you can still power on the Wii with a Wiimote, and you can still boot into Recovery Mode on an original revision Wii.
|
||||
|
||||
#### Cause
|
||||
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 doesn't have a Wi-Fi module.
|
||||
|
||||
#### Solutions
|
||||
|
|
@ -86,41 +206,21 @@ To resolve this problem, you can try to reseat or replace the Wi-Fi/Bluetooth mo
|
|||
|
||||
If you are on a Wii Mini, you must install a Wi-Fi module.
|
||||
|
||||
## Error 003 Brick
|
||||
|
||||
#### Cause
|
||||
|
||||
This brick happens when a non-Korean Wii Menu on 4.2 or 4.3 detects that the Korean common key is present.
|
||||
|
||||
This is usually an immediate follow-up to a Wii System Update on an unsuspecting region-changed Korean Wii.
|
||||
|
||||
|
||||
#### Solutions
|
||||
|
||||
Since this brick most often occurs after the Wii Menu updates, Priiloader will not be present.
|
||||
|
||||
Korean Wiis also released with Wii Menu 3.3, around the time that Nintendo [fixed the Trucha bug in boot1](https://wiibrew.org/wiki/3.3#Changes), 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. It's only accessible if you take apart a GameCube controller to hold all 4 +Control Pad buttons down while the GameCube controller's plugged into the 4th slot on your Wii as it's turned on. Taking apart the controller is necessary since you cannot hold down all the buttons without taking the controller apart.
|
||||
|
||||
## IOS brick
|
||||
|
||||
#### Cause
|
||||
This brick happens when the Wii Menu's IOS is a [stub](http://wiibrew.org/wiki/Stub_IOS). This is usually the consequence of attempting to downgrade your Wii menu.
|
||||
|
||||
#### Solutions
|
||||
You must have BootMii as boot2 to fix this brick. Priiloader will not load.
|
||||
{: .notice}
|
||||
|
||||
You can either restore a NAND backup, or do this:
|
||||
|
||||
1. Use [NUS Downloader](https://wiibrew.org/wiki/NUSD) to pack a WAD of your original Wii Menu.
|
||||
1. Use BootMii to enter the Homebrew Channel, and use a WAD manager to install the Wii Menu WAD.
|
||||
If both fail, see [low-level brick](bricks#low-level-brick).
|
||||
|
||||
## Low-level brick
|
||||
|
||||
#### Symptoms
|
||||
Completely black screen, no response to user input. Recovery Mode cannot be booted.
|
||||
|
||||
#### Cause
|
||||
This brick occurs when boot1/boot2 is corrupt.
|
||||
This brick occurs when boot1/boot2 is corrupt, or if there is a hardware failure.
|
||||
|
||||
#### Solutions
|
||||
You can only recover by using a NAND programmer.
|
||||
First, troubleshooting must be done to determine if hardware is at fault. In the order listed, do the following:
|
||||
|
||||
+ 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.
|
||||
+ If on a Wii Mini, and if a normal IOS80 was installed, see [Wi-Fi brick](wi-fi-brick). If steps to resolve the Wi-Fi brick failed, proceed.
|
||||
+ Attempt to boot into [Recovery Mode](recovery-mode) (normal Wiis only). If the Wii boots into Recovery Mode, see [Wi-Fi brick](wi-fi-brick). If steps to resolve the Wi-Fi brick failed, proceed.
|
||||
+ Reseat the disc drive and attempt to boot normally. If still unsuccessful, replace the disc drive. If still unsuccessful, proceed.
|
||||
+ At this point, either there is a low level boot0/boot1 corruption, a NAND chip failure, or there is a wider unknown hardware failure. Good luck.
|
||||
|
|
@ -2,12 +2,12 @@
|
|||
title: "Donations"
|
||||
---
|
||||
|
||||
[![Paypal]({{ "/images/paypal_white.png" | absolute_url }}){:height="72px" width="256px"}{: style="padding-bottom: .35em"}](https://paypal.me/NintendoHomebrew){: .align-center}
|
||||
[{:height="72px" width="256px"}{: style="padding-bottom: .35em"}](https://paypal.me/NintendoHomebrew){: .align-center}
|
||||
[https://paypal.me/NintendoHomebrew](https://paypal.me/NintendoHomebrew)
|
||||
{: .text-center}
|
||||
{: .notice--info}
|
||||
|
||||
[{:height="72px" width="256px"}{: style="padding-bottom: .35em"}](https://www.patreon.com/WiiLink24){: .align-center}
|
||||
[{:height="72px" width="256px"}{: style="padding-bottom: .35em"}](https://www.patreon.com/WiiLink24){: .align-center}
|
||||
[https://www.patreon.com/WiiLink24](https://www.patreon.com/WiiLink24)
|
||||
{: .text-center}
|
||||
{: .notice--info}
|
||||
|
|
|
|||
|
|
@ -26,21 +26,21 @@ Want to dump a GameCube or a Wii disk? There are two ways of doing so, depending
|
|||
##### Section II - Ripping
|
||||
|
||||
1. Select your device that you will be dumping the game to - your USB drive or SD card.
|
||||
|
||||
|
||||
1. On this screen, it asks you if you want to download a file with game checksums so you can verify the dump created is a 1:1 copy of the disc. It's your choice whether to say `Yes` or `No` to download this file.
|
||||
|
||||
|
||||
1. Now insert the game you want to dump.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Set it as shown on the screen below.
|
||||
|
||||
If you are dumping one of the 13 games on [this list](https://wiki.dolphin-emu.org/index.php?title=Category:Dual_Layer_Disc_games), set `Dual Layer` to `Yes`.
|
||||
{: .notice--info}
|
||||
|
||||
|
||||
|
||||
|
||||
1. CleanRip will now dump your game. It can take a while, since it will dump the full 4.7 GB disc contents (8.5 GB for dual layer discs).
|
||||
|
||||
|
||||
</div>
|
||||
|
||||
<div id="dump-smb" class="blanktabcontent" markdown="1">
|
||||
|
|
@ -64,23 +64,23 @@ Your Wii and your computer must be connected to one local network.
|
|||
##### Section II - Ripping
|
||||
|
||||
1. Press the right on the D-pad and press A.
|
||||
|
||||
|
||||
1. Choose the disc that you want to copy (The options are: `GameCube Disc`, `Wii Single-Layer Disc`, `Wii Dual-Layer Disc` and press "A"
|
||||
|
||||
|
||||
1. Now put your game to your Wii. (If it's already in your Wii, eject it and put it back.)
|
||||
|
||||
|
||||
|
||||
|
||||
1. Remember your Wii URL (IP address)
|
||||
|
||||
|
||||
1. On your computer's web browser, go to your address bar and enter the Wii URL.
|
||||
|
||||
|
||||
1. Click on `Click here to download XXXX.iso`.
|
||||
|
||||
|
||||
|
||||
The transfer speed is not the fastest, but if you can't use anything else, it's better than nothing.
|
||||
{: .notice--info}
|
||||
|
||||
|
||||
|
||||
|
||||
</div>
|
||||
|
||||
|
|
|
|||
|
|
@ -19,13 +19,13 @@ This tutorial will explain you how to dump WADs from your Wii System Memory.
|
|||
##### Section II - Dumping
|
||||
|
||||
1. Press the A Button.
|
||||
|
||||
|
||||
|
||||
1. Choose `Installed Channel Titles`.
|
||||
|
||||
|
||||
|
||||
1. Find the content you want to dump and press the 1 Button.
|
||||
|
||||
|
||||
|
||||
1. Choose `Backup to WAD`.
|
||||
1. At the prompt to `Fakesign the ticket`, choose `Yes`.
|
||||
|
|
@ -33,4 +33,4 @@ This tutorial will explain you how to dump WADs from your Wii System Memory.
|
|||
1. At the prompt to `Change the output WAD region`, choose `No`.
|
||||
|
||||
You have now dumped that WAD. It should appear on your SD card.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: "FAQ"
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
### How risky is hacking my console?
|
||||
Bricks (a state where either some parts of your Wii software are not working, or your Wii is not working at all) are extremely rare unless you ignore/circumvent all safety checks, or do something risky or naive like installing an older version of the Wii Menu. Make sure you install [BootMii](bootmii) and [Priiloader](priiloader) to protect yourself from bricks!
|
||||
|
|
@ -26,4 +26,4 @@ The following is a list of things that can potentially **BRICK** your vWii (don'
|
|||
* Modifying the vWii NAND without knowing what you are doing.
|
||||
|
||||
### How can I remove parental controls?
|
||||
The [mkey generator](https://mkey.salthax.org) can generate the code required to remove parental controls.
|
||||
The [mkey generator](https://mkey.salthax.org) can generate the code required to remove parental controls.
|
||||
|
|
@ -12,12 +12,20 @@ FlashHax is an exploit for the Wii that is triggered by using the Internet Chann
|
|||
#### Instructions
|
||||
|
||||
1. Open up the Internet Channel on your Wii.
|
||||
1. Go to flashhax.com in the browser and bookmark the page.
|
||||
|
||||
1. Go to flashhax.com in the browser and select the correct region for your console.
|
||||
|
||||
1. Bookmark the web page, by clicking the star button and pressing `Add Favorite`.
|
||||
|
||||
1. Open the site from the bookmark. It'll then proceed to download and load the HackMii Installer. It may take some time as it is downloading the installer over the Internet.
|
||||
|
||||
|
||||
If the HackMii Installer doesn't load and it instead freezes (you can't move your cursor), please restart your Wii and repeat step 3 until it works. It might take multiple tries, be persistent!
|
||||
If the HackMii Installer doesn't load and it instead freezes (you can't move your cursor), please restart your Wii and repeat step 4 until it works. It might take multiple tries, so be persistent!
|
||||
|
||||
If you still can't get it to load, try deleting your cookies or save data for the Internet Channel.
|
||||
|
||||
If after several tries Flashhax still does not work, you should try a [different exploit](get-started) instead.
|
||||
|
||||
|
||||
[Continue to Homebrew Channel and BootMii Installation](hbc)
|
||||
{: .notice--info}
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ title: "GameCube Saves"
|
|||
|
||||
This is a full guide on how to manage your GameCube saves.
|
||||
|
||||
|
||||
|
||||
|
||||
Use of any GameCube peripheral with a Family Edition Wii or Wii Mini require soldering on GameCube ports and/or memory card slots.
|
||||
{: .notice--info}
|
||||
|
|
@ -37,13 +37,13 @@ If you are looking for save game exploits for booting into [Swiss](https://githu
|
|||
|
||||
1. Insert your physical memory card into Slot A or Slot B.
|
||||
1. Select the device you want to restore from.
|
||||
|
||||
|
||||
1. In GCMM, Press X on a GameCube controller or + on a Wii remote.
|
||||
|
||||
|
||||
1. Select the slot your memory card is in.
|
||||
|
||||
|
||||
1. Select the save you want to restore. If you have multiple saves to restore, you can press R on the GameCube controller or 1 on the Wii remote to restore all of your saves.
|
||||
|
||||
|
||||
1. When restoration is complete, press any button to continue.
|
||||
|
||||
## Backing Up A Save (.gci File) to an SD or USB From a Physical Memory Card
|
||||
|
|
@ -66,13 +66,13 @@ If you are looking for save game exploits for booting into [Swiss](https://githu
|
|||
|
||||
1. Insert your physical memory card into slot A or slot B.
|
||||
1. Select the device you want to backup to.
|
||||
|
||||
|
||||
1. In GCMM, Press Y on a GameCube controller or - on a Wii remote.
|
||||
|
||||
|
||||
1. Select the slot your memory card is in.
|
||||
|
||||
|
||||
1. Select the save you want to backup. If you have multiple saves to backup, you can press R on the GameCube controller or 1 on the Wii remote to backup all of your saves.
|
||||
|
||||
|
||||
1. When backing up is complete, press any button to continue.
|
||||
|
||||
## Backing Up Your Physical Memory Card Into an Emulated Memory Card (.raw file)
|
||||
|
|
@ -94,9 +94,9 @@ If you are looking for save game exploits for booting into [Swiss](https://githu
|
|||
|
||||
1. Insert your memory card into Slot A or Slot B.
|
||||
1. Select the device you want to dump to.
|
||||
|
||||
|
||||
1. Press L and Y at the same time on GameCube Controller or B and - at the same time on the Wii remote to backup your to a .raw file and select the slot your memory card is in.
|
||||
|
||||
|
||||
1. When the dump is complete, press any button to continue. It should be saved in a folder on the root of your SD or USB called `MCBACKUP`.
|
||||
|
||||
## Restoring an Emulated Memory Save to a Physical Memory Card
|
||||
|
|
@ -113,10 +113,10 @@ If you are looking for save game exploits for booting into [Swiss](https://githu
|
|||
1. If you are restoring a Nintendont emulated memory card save, navigate to the `saves` folder on the root of your SD card or USB.
|
||||
1. Insert your memory card into Slot A or Slot B.
|
||||
1. Select the device you want to restore from.
|
||||
|
||||
|
||||
1. Press L and X at the same time on GameCube controller or B and + at the same time on the Wii remote.
|
||||
1. Select the slot your memory card is in.
|
||||
|
||||
|
||||
1. It should restore the .raw file to your memory card. When restoration is complete, press any button to continue.
|
||||
|
||||
## Transferring Saves Between 2 Physical Memory Cards
|
||||
|
|
@ -130,13 +130,13 @@ If you are looking for save game exploits for booting into [Swiss](https://githu
|
|||
|
||||
1. Insert both memory cards into the Wii.
|
||||
1. From the System menu, navigate into `Wii Options`, `Data Management`, `Save Data`, `Nintendo GameCube`.
|
||||
 <br>
|
||||
 <br>
|
||||
|
||||
 <br>
|
||||
 <br>
|
||||
|
||||
 <br>
|
||||
 <br>
|
||||
|
||||
|
||||
|
||||
|
||||
1. Find the save you want, select it and select `Move or Copy`.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,36 +4,25 @@ title: "Get Started"
|
|||
|
||||
{% include toc title="Table of Contents" %}
|
||||
|
||||
Even if your Wii has already been softmodded in the past, following these steps can still ensure that your softmod is up to date.
|
||||
It is recommended to at least have an SD card on hand after the initial hack process, as this will enable you to make a NAND backup using BootMii and install many types of homebrew.
|
||||
{: .notice--info}
|
||||
|
||||
All of the exploits run the HackMii Installer, and have the same end result.
|
||||
All listed exploits are different methods of achieving the same end-result, getting to the HackMii installer.
|
||||
{: .notice--info}
|
||||
|
||||
Although you can follow this guide without an SD card, you will not be able to create or restore a NAND backup using BootMii, and you won't be able to use some homebrew.
|
||||
{: .notice--info}
|
||||
These steps will help you softmod your Wii, from stock to BootMii. Before starting this guide, please ensure that your console is on the latest version of the Wii firmware (4.3). If your Wii is already softmodded but is on an older version, follow [this](update) guide to update to latest.
|
||||
|
||||
If your Wii Menu is not on version 4.3, use str2hax, Wilbrand or FlashHax to install the Homebrew Channel, and then follow the [update guide](update) to update to 4.3.
|
||||
{: .notice--info}
|
||||
### Identify your console revision:
|
||||
|
||||
This guide is for the original Wii and Wii mini only (including the Wii Family Edition). Do not use this on a Wii U (vWii)!
|
||||
If you want to install homebrew on a Wii U, [follow this guide](https://wiiu.hacks.guide).
|
||||
{: .notice--warning}
|
||||
{% include identify-console.html %}<br>
|
||||
|
||||
### Choose an exploit to use
|
||||
### Select your exploit
|
||||
|
||||
These exploits are sorted by easiest to hardest difficulty of use.
|
||||
Select the exploit that corresponds to your console and situation the best. If the recommended option does not work for you, or if you are curious about other exploits, check out [Legacy Exploits](legacy-exploits).
|
||||
|
||||
+ [str2hax](str2hax) - Exploit that uses the Wii EULA
|
||||
* Requires an Internet connection and changing the DNS server
|
||||
+ [LetterBomb](letterbomb) - Exploit that uses the Wii Message Board
|
||||
* Requires an SD card
|
||||
* Must be on version 4.3
|
||||
+ [Wilbrand](wilbrand) - Exploit that also uses the Wii Message Board
|
||||
* Requires only an SD card with the Web UI, otherwise requires a PC in addition to the SD card
|
||||
* Works on versions 3.0 - 4.3
|
||||
+ [FlashHax](flashhax) - Exploit that uses the Internet Channel
|
||||
* Requires the Internet Channel installed, and an Internet connection
|
||||
+ [BlueBomb](bluebomb) - Exploit that uses Bluetooth
|
||||
* Requires a computer with Bluetooth and GNU/Linux, as well as a USB storage device
|
||||
* This is the only exploit that works on the **Wii mini**
|
||||
| Console Revision | Recommended Exploit |
|
||||
| ----------------- | ------------------- |
|
||||
| Wii/Wii Family Edition | If you can use an SD card: Proceed to [Letterbomb](letterbomb)<br> If you cannot use an SD card: Proceed to [str2hax](str2hax) |
|
||||
| Wii Mini | Proceed to [Bluebomb](bluebomb) |
|
||||
| Wii U (vWii) | If you have not modded your Wii U yet:<br> Proceed to [Introduction (wiiu.hacks.guide)](https://wiiu.hacks.guide/#/)<br> If your Wii U is already modded:<br> Proceed to [vWii Modding (wiiu.hacks.guide)](https://wiiu.hacks.guide/#/vwii-modding) |
|
||||
| Dolphin Emulator | Proceed to [Homebrew Channel on Dolphin](homebrew-dolphin) |
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ title: "Homebrew Channel - for Wii mini only"
|
|||
|
||||
{% include toc title="Table of Contents" %}
|
||||
|
||||
|
||||
|
||||
|
||||
The Homebrew Channel is where you will go to launch homebrew applications.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,57 +4,51 @@ title: "Homebrew Channel and BootMii Installation"
|
|||
|
||||
{% include toc title="Table of Contents" %}
|
||||
|
||||
|
||||
|
||||
|
||||
The Homebrew Channel is where you will go to launch homebrew applications.
|
||||
BootMii is a piece of software that can backup and restore your Wii's NAND storage, and if installed in boot2, provides brick protection.
|
||||
|
||||
Regarding BootMii, there are two ways that it can be installed: directly to a part of the Wii bootloader called boot2, and via an IOS. Preferably you would want to install BootMii under boot2 as it provides extended brick protection, however Wiis with a vulnerable boot2 are considerably rare and made mostly before 2009. In most cases, installing BootMii as IOS should be fine, as long as you also install Priiloader.
|
||||
{: .notice--info}
|
||||
|
||||
If you do not have an SD card, you cannot install nor use BootMii; regardless of whether or not you install it as IOS or boot2.
|
||||
You can always [install it at a later date](hackmii).
|
||||
{: .notice--warning}
|
||||
|
||||
#### Instructions
|
||||
|
||||
1. You will see a scam warning screen. Wait 30 seconds for the text "Press 1 to continue" to appear, then press 1.
|
||||
|
||||
1. You will be presented with a test results screen. Select `Continue`.
|
||||
|
||||
|
||||
If BootMii says that it `can only be installed as an IOS`, that's normal.
|
||||
{: .notice--info}
|
||||
|
||||
1. Select `Install the Homebrew Channel`.
|
||||
|
||||
|
||||
1. Select `Continue` when finished.
|
||||
|
||||
1. Once installed, select `Back`, then select `BootMii`.
|
||||
|
||||
1. Select `Install BootMii as IOS`.
|
||||
|
||||
If you do not have an SD card, you cannot install nor use BootMii, and therefore will not be able to utilize any of the mentioned benefits. <br>
|
||||
You can always [install it at a later date](hackmii).
|
||||
{: .notice--warning}
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
1. Once done, select `Continue`.
|
||||
1. If you have the option to `Install BootMii as boot2`, please do so as well. This offers the best possible brick protection you can have. Otherwise, skip this step.
|
||||
1. Once done, select `Continue`. If you have the option to `Install BootMii as boot2`, please do so as well.
|
||||
|
||||
1. Select `Exit` to finally open the Homebrew Channel.
|
||||
|
||||
|
||||
#### Required Reading
|
||||
|
||||
You can now use the Homebrew Channel to launch homebrew apps. Open Shop Channel is a one-stop shop for downloading homebrew, which you will learn how to install further in this guide.
|
||||
You can now use the Homebrew Channel to launch homebrew apps, as well as BootMii for backing up and restoring your NAND if you were able to install it.
|
||||
|
||||
Here's a tip - when installing homebrew applications on your SD Card or USB drive, your folder structure should look like this:
|
||||
|
||||
|
||||
|
||||
|
||||
`AppName1` and `AppName2` are placeholder names. Do not nest multiple `apps` folders inside the `apps` folder itself.
|
||||
|
||||
[Continue to making a NAND Backup using BootMii](bootmii)<br>
|
||||
Making a NAND backup with BootMii at this point is highly recommended.
|
||||
{: .notice--info}
|
||||
|
||||
If you couldn't install BootMii, continue to [installing Priiloader](priiloader).
|
||||
Making a NAND backup at this point is highly recommended, and is one of the only ways to save your Wii from a brick in some cases.
|
||||
{: .notice--info}
|
||||
|
||||
Tip: You can tell if a Wii has BootMii installed as boot2 if your disc drive flashes very briefly, only after the immediate flash that happens when you press the POWER Button.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ layout: splash
|
|||
title: "Wii Hacks Guide"
|
||||
header:
|
||||
overlay_color: "#5e616c"
|
||||
overlay_image: /images/home-page-feature.jpg
|
||||
overlay_image: /images/main-pages/home-page-feature.jpg
|
||||
overlay_filter: 0.5
|
||||
caption:
|
||||
excerpt: "The complete guide to modding your Nintendo Wii."
|
||||
|
|
|
|||
35
_pages/en_US/homebrew-dolphin.md
Normal file
35
_pages/en_US/homebrew-dolphin.md
Normal file
|
|
@ -0,0 +1,35 @@
|
|||
---
|
||||
title: "Installing Homebrew Channel on Dolphin Emulator"
|
||||
---
|
||||
|
||||
{% include toc title="Table of Contents" %}
|
||||
|
||||
On Dolphin Emulator version `5.0-4588` or later, the Wii Menu can be easily installed through Dolphin itself. Once this is done, the Homebrew Channel can be installed, although not in the same manner as a physical Wii.
|
||||
|
||||
#### What you need
|
||||
|
||||
* A Windows/MacOS/Linux computer with an Internet connection
|
||||
* [Dolphin Emulator](https://dolphin-emu.org/download/) version `5.0-4588` or later
|
||||
* The latest version of [Open Homebrew Channel](https://github.com/Wii-Mini-Hacking/hbc/releases)
|
||||
|
||||
### Instructions
|
||||
|
||||
1. If you have not already done so, install the Wii Menu on Dolphin Emulator by going to `Tools > Perform System Update`.
|
||||
|
||||
1. Download `Open_HBC_(version)_LULZ.wad` from the page linked above.
|
||||
1. Open Dolphin Emulator.
|
||||
1. Select `Tools > Install WAD` and select the `Open_HBC_(version)_LULZ.wad` file that was downloaded.
|
||||
|
||||
1. Select `Tools > Load Wii System Menu`. The channel should now appear.
|
||||
|
||||
|
||||
### Post-Installation, installing Homebrew Apps through Open Shop Channel
|
||||
|
||||
1. Download the Open Shop Channel [here](https://oscwii.org/library/app/homebrew_browser) for usage in Dolphin. Alternatively, you can get OSCDL and do this process manually.
|
||||
1. Stop the emulation (if running), and open the `Config > Wii` window in Dolphin Emulator.
|
||||
1. Enable `Automatically Sync with Folder`. Optionally, you may also want to adjust the `SD Card File Size` to a larger parameter - however in most cases `Auto` should be fine.
|
||||
1. Open the `SD Sync Folder`. On Windows, this can easily be done by pasting the folder path into the Start Menu, Windows Explorer, or Run.
|
||||
1. Extract any homebrew apps to the `WiiSDSync` folder. The end result should look something like this:
|
||||
|
||||
1. Load the Wii Menu and open the Homebrew Channel. Your newly installed apps should appear!
|
||||
|
||||
67
_pages/en_US/legacy-exploits.md
Normal file
67
_pages/en_US/legacy-exploits.md
Normal file
|
|
@ -0,0 +1,67 @@
|
|||
---
|
||||
title: "Legacy Exploits"
|
||||
---
|
||||
|
||||
This page lays out different exploits that were used, or can still be used on the Nintendo Wii to hack the console - but for one reason or another, are not recommended today.
|
||||
|
||||
### Game Exploits
|
||||
|
||||
#### Smash Stack
|
||||
|
||||
+ Loads directly from files on the SD card through Super Smash Bros. Melee
|
||||
+ Requires an SD card under the original SD specification, 2GB or less
|
||||
+ Works on all system menu versions, even 4.3, as well as on Korean Wiis
|
||||
+ Can be used as a means of recovering an Error 003 console in Recovery Mode
|
||||
+ Superceded mostly by Letterbomb and Bluebomb
|
||||
+ [Wiibrew Page](https://wiibrew.org/wiki/Smash_Stack)
|
||||
|
||||
#### Twilight Hack
|
||||
|
||||
+ Loads a hacked game save on the Wii System Memory through The Legend of Zelda: Twilight Princess
|
||||
+ Works only on system menu versions up to 3.4
|
||||
+ Superceded by Wilbrand, or by updating to 4.3 and using Letterbomb and Bluebomb
|
||||
+ [Wiibrew Page](https://wiibrew.org/wiki/Twilight_Hack)
|
||||
|
||||
#### Indiana Pwns
|
||||
|
||||
+ Loads a hacked game save on the Wii System Memory through LEGO Indiana Jones
|
||||
+ Works on all system menu versions, even 4.3
|
||||
+ Superceded mostly by Letterbomb and Bluebomb
|
||||
+ [Wiibrew Page](https://wiibrew.org/wiki/Indiana_Pwns)
|
||||
|
||||
#### Bathaxx
|
||||
|
||||
+ Loads a hacked game save on the Wii System Memory through LEGO Batman
|
||||
+ Works on all system menu versions, even 4.3
|
||||
+ Superceded mostly by Letterbomb and Bluebomb
|
||||
+ [Wiibrew Page](https://wiibrew.org/wiki/Bathaxx)
|
||||
|
||||
#### Return of the Jodi
|
||||
|
||||
+ Loads a hacked game save on the Wii System Memory through LEGO Star Wars: The Complete Saga
|
||||
+ Works on all system menu versions, even 4.3
|
||||
+ Superceded mostly by Letterbomb and Bluebomb
|
||||
+ [Wiibrew Page](https://wiibrew.org/wiki/Return_of_the_Jodi)
|
||||
|
||||
#### Eri HaKawai
|
||||
|
||||
+ Loads a hacked game save on the Wii System Memory through Tales of Symphonia: Dawn of the New World
|
||||
+ Works on all system menu versions, even 4.3
|
||||
+ Superceded mostly by Letterbomb and Bluebomb
|
||||
+ [Wiibrew Page](https://wiibrew.org/wiki/Eri_HaKawai)
|
||||
|
||||
#### Yu-Gi-OWNED!
|
||||
|
||||
+ Loads a hacked game save on the Wii System Memory through Yu-Gi-Oh 5D's Wheelie Breakers
|
||||
+ Works on all system menu versions, even 4.3
|
||||
+ Superceded mostly by Letterbomb and Bluebomb
|
||||
+ [Wiibrew Page](https://wiibrew.org/wiki/Yu-Gi-OWNED!)
|
||||
|
||||
### Other Exploits
|
||||
|
||||
#### Bannerbomb
|
||||
|
||||
+ Crashes the Wii Menu by exploiting an oversight in Wii banner loading
|
||||
+ Works on system menu versions 3.0-4.1 on v1, and 4.2 on v2 (attempting to load Bannerbomb on 4.3 will result in an `Error#004 The system files are corrupted`)
|
||||
+ Superceded by Wilbrand, or by updating to 4.3 and using Letterbomb and Bluebomb
|
||||
+ [Wiibrew Page](https://wiibrew.org/wiki/Bannerbomb)
|
||||
|
|
@ -2,31 +2,40 @@
|
|||
title: "LetterBomb"
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
For instructions on how to format your SD card correctly, please see [this guide](https://wiki.hacks.guide/wiki/Formatting_an_SD_card). It is highly recommended to check it due to problems with formatting as FAT32.
|
||||
{: .notice--info}
|
||||
|
||||
Do NOT use any of the MAC address examples given in this guide, as they will simply cause an error on the HackMii website. Use your own!
|
||||
{: .notice--warning}
|
||||
|
||||
LetterBomb is an exploit for the Wii that is triggered using the Wii Message Board.
|
||||
|
||||
#### What you need
|
||||
* An SD card formatted to FAT32/MS-DOS
|
||||
* A Wii on System Menu version 4.3
|
||||
* An SD card formatted as FAT32
|
||||
* A Nintendo Wii on System Menu version 4.3
|
||||
* A Windows/MacOS/Linux computer with an Internet connection
|
||||
|
||||
#### Instructions
|
||||
|
||||
1. On your Wii, go to `Wii Settings` -> `Internet` -> `Console Information` and make note of your MAC address.
|
||||
1. Visit [please.hackmii.com](https://please.hackmii.com/), input your Wii MAC and region, ensure `Bundle the HackMii Installer for me!` is checked, and cut either wire.
|
||||
|
||||
|
||||
1. On your Wii, go to `Wii Settings`. At this point, take note in the top right corner of the letter next to the system version. This letter corresponds to your system menu region, which you will need to know for the corresponding steps. Also, ensure that you are on System Menu version 4.3.
|
||||
|
||||
1. Next, go to `Internet` > `Console Information`, and take note of your FULL MAC address.
|
||||
|
||||
1. Visit [the HackMii website](https://please.hackmii.com/) and input your Wii MAC address and region. Ensure `Bundle the HackMii Installer for me!` is checked, and cut either wire.
|
||||
|
||||
1. Take your SD card, and make sure that it is formatted as FAT32.
|
||||
1. Extract the contents of the downloaded ZIP to the root of your SD card.
|
||||
1. Take out your SD card and insert it in your Wii.
|
||||
+ The SD card must be inserted in the SD card slot located in the front of the Wii. Using a USB adapter plugged into the Wii's USB port will not work.
|
||||
1. On your Wii, return to the Wii Menu and then open the Wii Message Board.
|
||||
1. Load the red letter with a bomb icon.
|
||||
+ The SD card must be inserted in the SD card slot located in the front of the Wii. Using a USB to SD adapter plugged into the Wii's USB port will not work.
|
||||
1. On your Wii, return to the Wii Menu and then open the Wii Message Board. Then, open the red letter with a bomb.
|
||||
+ Ensure the date on your Wii is correct, otherwise you might be unable to find the letter.
|
||||
+ In various scenarios, you may need to look at the previous or next day to find it.
|
||||
+ If you don't see the red letter, check if any errors appear in the SD card sections in `Data Management`. If any do, there may be an issue with the SD card format or the Wii’s SD card reader.
|
||||
+ If your Wii freezes after clicking on the letter, you probably chose the wrong region when downloading the exploit. Redo Step 2 and select the correct region.
|
||||
+ In some cases, you may need to check the messages for tommorow or yesterday for the letter to show up.
|
||||
+ If you don't see the red letter, check if any errors appear in the SD card section of `Data Management`. If any do, there may be an issue with the SD card format or the Wii’s SD card reader.
|
||||
+ If your Wii freezes after clicking on the letter, you most likely chose the wrong system menu region for LetterBomb. Go back to Step 2 and verify that you chose the right region.
|
||||
|
||||
|
||||
|
||||
|
||||
[Continue to Homebrew Channel and BootMii Installation](hbc)
|
||||
{: .notice--info}
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ This Program does NOT come with a warranty, so you are responsible for any poten
|
|||
This program is NOT intended to be used for the vWii or the Wii mini. Some tools may or may not work for these platforms.
|
||||
{: .notice--warning}
|
||||
|
||||
|
||||
|
||||
|
||||
ModMii is a PC program for windows created by XFlak that has various helpful tools for modding, including some tutorials that may not be currently available here on the [wii.guide](site-navigation) website. <br>
|
||||
You can choose to launch in ModMii skin, which has a more user friendly approach, or launch in ModMii Classic, which interacts like a PC terminal or command prompt.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ Priiloader adds a level of brick protection to your Wii. It loads before the Wii
|
|||
|
||||
### Installing Priiloader
|
||||
|
||||
|
||||
|
||||
|
||||
{% capture notice-vwii-priiloader %}
|
||||
Priiloader 0.10.0 introduces vWii support! <br>
|
||||
|
|
@ -134,17 +134,17 @@ You will be installing `uneoboot.dol` in step 3.
|
|||
|
||||
1. Launch the Homebrew channel, then launch the Load Priiloader app.
|
||||
1. Scroll down to `Load/Install file` and press A.
|
||||
|
||||
|
||||
1. Scroll through the menu until your desired homebrew app is highlighted, and press A to install it.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Press B to go back to the main menu.
|
||||
1. Scroll down to `Settings` and press A.
|
||||
|
||||
|
||||
1. Press Right to cycle through the Autoboot options until `Installed file` is selected.
|
||||
|
||||
|
||||
1. Scroll down to `save settings` and press A.
|
||||
|
||||
|
||||
1. Press B to return to the main menu.
|
||||
1. Scroll back up to `System Menu` and press A.
|
||||
|
||||
|
|
@ -154,15 +154,15 @@ Your Wii should now automatically boot to whichever homebrew app you installed.
|
|||
|
||||
1. Launch the Homebrew Channel, then launch the Load Priiloader app.
|
||||
1. Scroll down to `Settings` and press A.
|
||||
|
||||
|
||||
1. Press Right to cycle through the Autoboot options until your desired option is selected. <br>
|
||||
`Disabled` will autoboot to the Priiloader menu.
|
||||
|
||||
Please don't set Autoboot to `BootMii IOS`. You will get stuck in a loop until you continuously hold the RESET button to enter the Priiloader menu.
|
||||
{: .notice--warning}
|
||||
|
||||
|
||||
|
||||
1. Scroll down to `save settings` and press A.
|
||||
|
||||
|
||||
1. Press B to return to the main menu.
|
||||
1. Scroll back up to `System Menu` and press A.
|
||||
|
|
|
|||
29
_pages/en_US/recovery-mode.md
Normal file
29
_pages/en_US/recovery-mode.md
Normal file
|
|
@ -0,0 +1,29 @@
|
|||
---
|
||||
title: "Recovery Mode"
|
||||
---
|
||||
|
||||
{% include toc title="Table of Contents" %}
|
||||
|
||||
|
||||
|
||||
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 some bricks using it.
|
||||
|
||||
#### What you need:
|
||||
|
||||
+ A GameCube controller
|
||||
+ If the Diagnostic Disc Check was previously removed with Priiloader, or if a drive chip is on hand:
|
||||
+ Super Smash Bros. Melee (Smash Stack)
|
||||
+ Any other exploited Wii game, with the current exploit game save on the console (see [Legacy Exploits](legacy-exploits))
|
||||
+ If the Diagnostic Disc Check was not previously removed with Priiloader, and no drive chip is on hand:
|
||||
+ Super Smash Bros. Melee (Smash Stack)
|
||||
+ An original revision Nintendo Wii (Family Edition Wiis will not work)
|
||||
+ A Windows/Mac OS/Linux PC with an Internet connection
|
||||
+ An SD Card formatted to Fat32
|
||||
|
||||
#### Preparation
|
||||
|
||||
#### Method I - Recovery Menu to Smash Stack
|
||||
|
||||
#### Method II - Recovery Menu to Bluebomb
|
||||
|
||||
#### Method III - Recovery Menu to Save Game Exploit
|
||||
|
|
@ -7,7 +7,7 @@ title: "RiiConnect24 FORE000006"
|
|||
For support (in English) with RiiConnect24, as well as RiiTag, join [RiiConnect24 on Discord](https://discord.gg/rc24).
|
||||
{: .notice--primary}
|
||||
|
||||
|
||||
|
||||
|
||||
If you get error FORE000006, your Wii's clock is probably set incorrectly. Set it to the correct date and time, then wait no more than an hour and the Forecast Channel should start working.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ title: "RiiConnect24 for Dolphin"
|
|||
|
||||
{% include toc title="Table of Contents" %}
|
||||
|
||||
|
||||
|
||||
|
||||
For support (in English) with RiiConnect24, as well as RiiTag, join [RiiConnect24 on Discord](https://discord.gg/rc24).
|
||||
{: .notice--primary}
|
||||
|
|
@ -40,7 +40,7 @@ If you have Dolphin already installed, skip to [Section II](#section-ii---instal
|
|||
1. Extract the .7z file using a program like 7-Zip or WinRAR.
|
||||
1. Start Dolphin.
|
||||
1. In Dolphin, go to `Tools` -> `Perform Online System Update` -> Choose your region.
|
||||
|
||||
|
||||
|
||||
If you have a homebrewed Wii console, you can use a [BootMii NAND dump](bootmii) instead of installing the system files with the System Update option. See [this page](https://wiki.dolphin-emu.org/index.php?title=NAND_Usage_Guide) for more information.
|
||||
{: .notice--info}
|
||||
|
|
@ -54,20 +54,21 @@ If you use a Windows version before Windows 10, you unfortunately cannot use Wii
|
|||
1. Download `RiiConnect24Patcher.bat` if you are on Windows, and `RiiConnect24Patcher.sh` if you are on a Unix system
|
||||
1. On Windows run `RiiConnect24Patcher.bat`. On Unix systems, open Terminal and type `bash`, then drag `RiiConnect24Patcher.sh` into the terminal then press enter. It should look like this: `bash RiiConnect24Patcher.sh`.
|
||||
1. Press 1 to choose "`Start`" and confirm your selection by pressing `ENTER`. (NOTE: These screenshots are from the Windows version of the patcher.)
|
||||
|
||||
1. For this guide, choose "`Install RiiConnect24 on your Dolphin Emulator`"
|
||||
|
||||
|
||||
1. Choose "`Express (Recommended)`". It will give you everything you need.
|
||||
|
||||
|
||||
1. Select your region.
|
||||
|
||||
|
||||
1. While you're at it, RiiConnect24 Patcher can additionally download some other optional channels that do not use RiiConnect24. `[X]` represents the options that selected. Just press 5 and `ENTER` if you're not interested.
|
||||
|
||||
|
||||
1. Press `1` then `ENTER` to start patching.
|
||||
1. Be patient...
|
||||
|
||||
|
||||
1. After it's done, we would appreciate if you take a minute to send anonymous feedback to us. If you don't want to, close the patcher. All the files should already be on your SD Card.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In Dolphin, go to `Tools` and then `Install WAD`. Install all the WAD files one by one.
|
||||
|
||||
##### Section III - Setting your Region
|
||||
|
|
@ -80,9 +81,9 @@ If you have imported your Wii's NAND backup, the default Region Select will prob
|
|||
1. Download and unzip [AnyGlobe Changer v1.0](https://github.com/fishguy6564/AnyGlobe-Changer/releases/download/1.0/AnyGlobe.Changer.zip).
|
||||
1. Drag the `boot.dol` file on to the Dolphin window.
|
||||
1. Wait a few seconds, then press 1 to continue.
|
||||
|
||||
|
||||
1. Select your region and sub-region, then select `Save`, then `Return`.
|
||||
|
||||
|
||||
|
||||
When you go back to the Everybody Votes Channel, the country & region names will appear blank. This is normal.
|
||||
{: .notice--info}
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ title: RiiConnect24 vWii Guide
|
|||
|
||||
{% include toc title="Table of Contents" %}
|
||||
|
||||
|
||||
|
||||
|
||||
For support (in English) with RiiConnect24, as well as RiiTag, join [RiiConnect24 on Discord](https://discord.gg/rc24).
|
||||
{: .notice--primary}
|
||||
|
|
@ -40,7 +40,7 @@ We are **NOT** responsible if you brick, or damage your console in any way whats
|
|||
* A Wii U with [the vWii modded](https://wiiu.hacks.guide/#/vwii-modding). **This guide requires the latest CFW on your Wii U.**
|
||||
* A Nintendo Network ID (NNID) linked to your Wii U
|
||||
* [Priiloader](priiloader) installed on your vWii
|
||||
* [RiiConnect24 Patcher (Windows, Mac and Linux)](https://github.com/RiiConnect24/RiiConnect24-Patcher/releases)
|
||||
* [RiiConnect24 Patcher (Windows, Mac and Linux)](https://github.com/riiconnect24/RiiConnect24-Patcher/releases)
|
||||
* [RiiConnect24 Mail Patcher](https://oscwii.org/library/app/Mail-Patcher)
|
||||
* [YAWM ModMii Edition](https://oscwii.org/library/app/yawmme)
|
||||
|
||||
|
|
@ -62,26 +62,26 @@ After following the vWii modding guide linked above, you should have:
|
|||
1. Download `RiiConnect24Patcher.bat` if you are on Windows, and `RiiConnect24Patcher.sh` if you are on a Unix system
|
||||
1. On Windows run `RiiConnect24Patcher.bat`. On Unix systems, open Terminal and type `bash`, then drag `RiiConnect24Patcher.sh` into the terminal then press enter. It should look like this: `bash RiiConnect24Patcher.sh`.
|
||||
1. Press 1 to choose "`Start`" and confirm your selection by pressing `ENTER`. (NOTE: These screenshots are from the Windows version of the patcher.)
|
||||
|
||||
|
||||
1. Select "`2. Wii U (vWii, Wii Mode)`".
|
||||
|
||||
|
||||
1. For this guide, choose "`Install RiiConnect24 on your Wii`"
|
||||
|
||||
|
||||
1. Choose "`Express (Recommended)`". It will give you everything you need.
|
||||
|
||||
|
||||
1. Select your region.
|
||||
|
||||
|
||||
1. While you're at it, RiiConnect24 Patcher can additionally download some other optional channels that do not use RiiConnect24. `[X]` represents the options that selected. Just press 5 and `ENTER` if you're not interested.
|
||||
|
||||
|
||||
1. Connect your SD Card or USB Drive to your computer and select "`1`".
|
||||
|
||||
|
||||
1. If your device was detected successfully, select "`1`". If not, make sure there's a folder called `apps` on your SD Card or USB Drive and try again.
|
||||
|
||||
|
||||
1. Be patient...
|
||||
|
||||
|
||||
1. After it's done, we would appreciate if you take a minute to send anonymous feedback to us. If you don't want to, close the patcher. All the files should already be on your SD Card.
|
||||
|
||||
|
||||
|
||||
|
||||
1. If it did not copy everything automatically to your SD Card or USB Device, copy the `WAD` and `apps` folder next to `RiiConnect24Patcher.bat` to your SD Card or USB Device.
|
||||
|
||||
##### Section II - Installing WADs
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ title: "RiiConnect24"
|
|||
|
||||
{% include toc title="Table of Contents" %}
|
||||
|
||||
|
||||
|
||||
|
||||
For support (in English) with RiiConnect24, as well as RiiTag, join [RiiConnect24 on Discord](https://discord.gg/rc24).
|
||||
{: .notice--primary}
|
||||
|
|
@ -31,7 +31,7 @@ DO NOT INSTALL RIICONNECT24 ON A WII MINI! It will not work and it will brick th
|
|||
* An SD card or USB drive
|
||||
* A Wii with an Internet connection
|
||||
* A computer
|
||||
* [RiiConnect24 Patcher (Windows, Mac and Linux)](https://github.com/RiiConnect24/RiiConnect24-Patcher/releases)
|
||||
* [RiiConnect24 Patcher (Windows, Mac and Linux)](https://github.com/riiconnect24/RiiConnect24-Patcher/releases)
|
||||
* [YAWM ModMii Edition](https://oscwii.org/library/app/yawmme)
|
||||
|
||||
#### Instructions
|
||||
|
|
@ -42,26 +42,26 @@ DO NOT INSTALL RIICONNECT24 ON A WII MINI! It will not work and it will brick th
|
|||
1. Download `RiiConnect24Patcher.bat` if you are on Windows, and `RiiConnect24Patcher.sh` if you are on a Unix system
|
||||
1. On Windows run `RiiConnect24Patcher.bat`. On Unix systems, open Terminal and type `bash`, then drag `RiiConnect24Patcher.sh` into the terminal then press enter. It should look like this: `bash RiiConnect24Patcher.sh`.
|
||||
1. Press 1 to choose "`Start`" and confirm your selection by pressing `ENTER`. (NOTE: These screenshots are from the Windows version of the patcher.)
|
||||
|
||||
|
||||
1. Select the device you're patching for.
|
||||
|
||||
|
||||
1. For this guide, choose "`Install RiiConnect24 on your Wii`"
|
||||
|
||||
|
||||
1. Choose "`Express (Recommended)`". It will give you everything you need.
|
||||
|
||||
|
||||
1. Select your region.
|
||||
|
||||
|
||||
1. While you're at it, RiiConnect24 Patcher can additionally download some other optional channels that do not use RiiConnect24. `[X]` represents the options that selected. Just press 5 and `ENTER` if you're not interested.
|
||||
|
||||
|
||||
1. Connect your SD Card or USB Drive to your computer and select "`1`".
|
||||
|
||||
|
||||
1. If your device was detected successfully, select "`1`". If not, make sure there's a folder called `apps` on your SD Card or USB Drive and try again.
|
||||
|
||||
|
||||
1. Be patient...
|
||||
|
||||
1. After it's done, close the patcher. All the files should already be on your SD Card.
|
||||
|
||||
|
||||
|
||||
1. After it's done, we would appreciate if you take a minute to send anonymous feedback to us. If you don't want to, close the patcher. All the files should already be on your SD Card.
|
||||
|
||||
|
||||
1. If it did not copy everything automatically to your SD Card or USB Device, copy the `WAD` and `apps` folder next to `RiiConnect24Patcher.bat` to your SD Card or USB Device.
|
||||
|
||||
##### Section II - Installing WADs
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ If you want to use Riivolution on a Wii mini, a WiFi card must be soldered and W
|
|||
Riivolution requires a working disk drive and a clean physical copy of the disk the desired mod is for. Scratched disks may or may not work very well or at all.
|
||||
{: .notice--info}
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
#### What you need
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ title: "Removing RSSMii"
|
|||
|
||||
If you no longer wish to use RSSMii (maybe because it gives you too much Wii Mail), here's how to remove it.
|
||||
|
||||
|
||||
|
||||
|
||||
#### What you need
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ title: "Installing RSSMii"
|
|||
|
||||
Do you want to get RSS feed updates on your Wii Message Board? This tutorial will tell you how to set RSSMii up.
|
||||
|
||||
|
||||
|
||||
|
||||
#### What you need
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ layout: single
|
|||
sitemap: false
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
{% capture notice-1 %}
|
||||
**Featured**
|
||||
|
|
@ -48,7 +48,6 @@ sitemap: false
|
|||
+ [Relaunching the HackMii Installer](hackmii)
|
||||
+ [str2hax](str2hax)
|
||||
+ [Types of Bricks](bricks)
|
||||
+ [Wii Mod Lite](wiimodlite)
|
||||
+ [Wilbrand](wilbrand)
|
||||
+ [YAWM ModMii Edition](yawmme)
|
||||
|
||||
|
|
|
|||
|
|
@ -20,39 +20,39 @@ str2hax is an exploit for the Wii that is triggered by loading the Wii's End Use
|
|||
This exploit requires you to set your DNS in order to connect to a server that contains the exploit.
|
||||
|
||||
1. Go to `Wii Options`.
|
||||
|
||||
|
||||
1. Go to `Wii Settings`.
|
||||
|
||||
|
||||
1. Go to `Page 2`, then click on `Internet`.
|
||||
|
||||
|
||||
1. Go to `Connection Settings`.
|
||||
|
||||
|
||||
1. Select your current connection.
|
||||
|
||||
|
||||
1. Go to `Change Settings`.
|
||||
|
||||
|
||||
1. Go to `Auto-Obtain DNS` (Not IP Address), then select `No`, then `Advanced Settings`.
|
||||
|
||||
|
||||
1. Type in `18.188.135.9` as the Primary DNS.
|
||||
|
||||
|
||||
|
||||
If there are 3 fields instead of 2 (like above), go back and make sure you are on the `Auto-Obtain DNS` page.
|
||||
{: .notice--warning}
|
||||
|
||||
1. Select `Confirm`, then select `Save`.
|
||||
|
||||
|
||||
1. Select `OK` to perform a connection test.
|
||||
|
||||
|
||||
+ If the connection test was successful, select `No` to skip the Wii System Update.
|
||||
+ If it fails with error code `521xx`, please verify that you have entered the DNS correctly.
|
||||
+ If it is still unsuccessful, please [use another exploit](get-started).
|
||||
|
||||
|
||||
+ If the connection test was successful, select `No` to skip the Wii System Update.
|
||||
+ If it fails with error code `521xx`, please verify that you have entered the DNS correctly.
|
||||
+ If it is still unsuccessful, please [use another exploit](get-started).
|
||||
|
||||
##### Section II - Triggering the Exploit
|
||||
|
||||
1. Go to the `Internet` section, then `User Agreements` or `Agreement/Contact`, then `Yes`.
|
||||
1. Click on `Next`. You should be greeted with the following screen:
|
||||
|
||||
|
||||
1. Give the exploit 1-2 minutes to download (and don't press `I ACCEPT`/`I DO NOT ACCEPT`).
|
||||
1. Once the exploit downloads, you will see a few text screens, then a mess of colors, then finally, the HackMii Installer.
|
||||
|
||||
|
|
|
|||
|
|
@ -21,8 +21,8 @@ A SysCheck lists all the IOS and cIOS that are on your Wii, along with some info
|
|||
|
||||
1. Wait for the program to get some information about your Wii.
|
||||
1. When "This IOS will be tested (Please select)" is shown on the screen, press A.
|
||||
|
||||
|
||||
1. Wait for the program to get some information about your IOS.
|
||||
1. After it finishes, press the `A` Button if you want to view the log.
|
||||
|
||||
|
||||
1. If you want to share the SysCheck, you can press the `A` Button, which will upload it to [syscheck.rc24.xyz](http://syscheck.rc24.xyz/) and give you a link. You can also share the `sysCheck.csv` saved to the root of your SD Card or USB Drive. The `IOSsysCheck.log` file (saved to the root as well) contains additional information about your IOS.
|
||||
|
|
|
|||
|
|
@ -76,9 +76,9 @@ There are a couple of ways to get the .app files for your vWii System Menu, in t
|
|||
|
||||
After selecting the correct version to download, check the box for `Create Decrypted Contents (*.app)`. Then, press the `Start NUS Download` Button on the top of the window.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
After the download has finished, search for the .app file corresponding to your region in the folder where NUS Downloader is.
|
||||
|
||||
|
|
@ -100,7 +100,7 @@ After you find the .app file, copy it to the main directory of the folder contai
|
|||
1. Click on `Create CSM` and select the .app file that you copied to the ThemeMii folder.
|
||||
1. Now navigate to the `theme` folder on your SD card and save your theme with the .csm extension.
|
||||
|
||||
|
||||
|
||||
|
||||
##### Section IV - Installing the Theme
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ This is a quick start guide on how to use USB Loader GX, a popular USB loader fo
|
|||
Despite its name, USB Loader GX is also capable of loading games from an SD Card.
|
||||
{: .notice--info}
|
||||
|
||||
|
||||
|
||||
|
||||
#### What you need
|
||||
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ title: "Wii Backup Manager"
|
|||
{% include toc title="Table of Contents" %}
|
||||
|
||||
Wii Backup Manager is a program to copy Wii games from your computer to a USB drive so you can play the games on your Wii. It also can download game covers from [GameTDB](https://gametdb.com/) and can be used to list what games you have. This tutorial will tell you how to copy over games from your computer to your USB drive. The other features are able to be used in the easy-to-use interface.
|
||||
|
||||
#### What you need
|
||||
|
||||
* A PC running Windows
|
||||
|
|
@ -36,14 +37,14 @@ You may format it as NTFS, but it won't work with a majority of apps (eg. The Ho
|
|||
##### Section II - Copying Games Over
|
||||
|
||||
1. Go to the `Drive 1` tab, then select the drive that you're putting the Wii games on.
|
||||
|
||||
|
||||
1. Go to the `Files` tab, then select `Add`. <br>
|
||||
Select `Files` to add multiple games to the program, or select `Folder` to add a whole folder of games.
|
||||
|
||||
|
||||
1. Go to `Select`, then click `Games not on drive 1`.
|
||||
|
||||
|
||||
1. Select `Transfer`, then select `Drive 1` to transfer the games over. It might take a while for the games to copy over.
|
||||
|
||||
|
||||
|
||||
##### Options once complete
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ title: "WiiFlow"
|
|||
|
||||
{% include toc title="Table of Contents" %}
|
||||
|
||||
|
||||
|
||||
|
||||
This is a quick start guide on how to use WiiFlow, a USB loader for the Wii that's used to play games from a USB drive or SD card.
|
||||
|
||||
|
|
@ -70,7 +70,7 @@ When you bring the cursor to the bottom of the screen while in flow view, there
|
|||
+ Disc - Loads game that is in disc drive.
|
||||
+ House - Will open this menu. This menu can also be launched by pressing the home button.
|
||||
|
||||
|
||||
|
||||
|
||||
+ Help Guide - Shows all the controls you can use in WiiFlow.
|
||||
+ Reload Cache - Press this when WiiFlow is not detecting a new game on the USB drive or SD card.
|
||||
|
|
|
|||
|
|
@ -23,9 +23,9 @@ Do NOT make a shortcut for the games "Mario Party 9" or "A Boy and His Blob". It
|
|||
#### Instructions
|
||||
|
||||
1. Install WiiGSC, then right click on it and choose **Run as administrator**. If you do not do this, WiiGSC will throw an error when you open it.
|
||||
|
||||
|
||||
1. Select the path to the ISO or WBFS file on your USB drive, and select the USB Loader you use. The other options should be fine the way they are.
|
||||
|
||||
|
||||
1. Install the generated WAD with your WAD manager.
|
||||
|
||||
<div class="notice--info">
|
||||
|
|
|
|||
|
|
@ -34,11 +34,11 @@ You cannot use the default Dolphin NAND with this service. You must use your own
|
|||
1. Make sure to download the version in the README that corresponds to your operating system.
|
||||
1. Launch the patcher and begin the setup process.
|
||||
1. When you see the setup screen, select `1. English Translation` in order to gain access to the Food Delivery Channel (Domino's) channel.<br><br>
|
||||
|
||||
|
||||
1. Next, you’ll see this screen, asking which version of Food Delivery Channel you want, so you’ll want to pick `2. Domino's (US and Canada only)`<br><br>
|
||||
|
||||
|
||||
1. After that, you can go through the rest of the process, but once you reach this step, be sure to pick the correct console platform you’re installing this on, as it will matter when using the app.<br><br>
|
||||
|
||||
|
||||
|
||||
##### Section II - Registering your Console ID
|
||||
|
||||
|
|
@ -75,8 +75,8 @@ In this section you will be setting your address information. This is required f
|
|||
1. Launch the Food Delivery Channel from the Wii Menu.
|
||||
1. If you have not previously set your address information, a prompt telling you to set it will appear. Press the `Address Info` button. Otherwise, click the `Change Address Information` button in the main menu.
|
||||
1. Now you are in the Address Information menu. Press the arrows to traverse screens. Here you will enter your data. When you are finished, click the `Done` button and then `Demae`.<br><br>
|
||||
<br><br>
|
||||
|
||||
<br><br>
|
||||
|
||||
|
||||
##### Section V - Placing an order
|
||||
|
||||
|
|
@ -91,14 +91,14 @@ If you have previously placed an order, skip to step 4.
|
|||
|
||||
1. Launch the Food Delivery Channel (aka. Food Channel) from the Wii Menu
|
||||
1. Follow the on-screen instructions, then click `Order` in the main menu.<br><br>
|
||||
<br><br>
|
||||
<br><br>
|
||||
1. You will now be prompted to select your region. Be sure to select your residing country correctly. Failure to do so will result in restaurants failing to load. You will then be prompted to select your state/province, then city. If your city is not on the list, you can select any one as it does not matter.<br><br>
|
||||
<br><br>
|
||||
<br><br>
|
||||
1. Click the `Pizza` button. This will load all the restaurants in your area. The first restaurant in the list is the one closest to you.
|
||||
1. Click `See Menu` to list the different menu categories. Click the category you would like, then select a food item. In the item screen, you can add toppings and adjust quantity.
|
||||
1. After adding a food item, you will be brought to the basket. To add a food item, scroll to the bottom and select `Add Order`. To proceed to checkout, click `Next`.
|
||||
1. Review your order thoroughly before placing the order. When you are ready, click the big green `Order` button.<br><br>
|
||||
<br><br>
|
||||
<br><br>
|
||||
1. If no error appeared, your order was placed successfully! To track your order, simply visit the Domino's Tracker for your region and enter the phone number you entered in the Address Information menu.
|
||||
|
||||
**_Happy ordering!_**
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ title: "Wiimmfi"
|
|||
|
||||
{% include toc title="Table of Contents" %}
|
||||
|
||||
|
||||
|
||||
|
||||
[Wiimmfi](https://wiimmfi.de) is a replacement service for the now-defunct Nintendo Wi-Fi Connection. It has been developed by Wiimm and Leseratte.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ title: "WiiWare Patcher"
|
|||
|
||||
Want to patch WAD games (WiiWare) to work with Wiimmfi and you don't know how? This tutorial will explain you how WiiWare Patcher works. (This tutorial is only suitable for Windows operating system)
|
||||
|
||||
|
||||
|
||||
|
||||
This tutorial is only for Windows version of WiiWare Patcher.
|
||||
{: .notice--info}
|
||||
|
|
@ -24,13 +24,14 @@ This tutorial is only for Windows version of WiiWare Patcher.
|
|||
##### Section II - Patching WiiWare games
|
||||
|
||||
1. On Windows, run `WiiWarePatcher.bat`.
|
||||
|
||||
|
||||
1. Press any key to start the patcher.
|
||||
1. Select if you want to patch your games or if you want to download and patch `Wii Speak Channel`.
|
||||
|
||||
|
||||
1. If you're patching your own games, copy them (.WAD files) to the folder where `WiiWarePatcher.bat` is, press `1` and hit ENTER.
|
||||
1. The patching process will start. Be patient.
|
||||
|
||||
|
||||
1. It's done! Patched WAD's are in the `wiimmfi-wads` folder. Install them using YAWM ModMii Edition or other WAD Manager.
|
||||
|
||||
|
||||
[Return to Wiimmfi installation page](wiimmfi)
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: "Wilbrand"
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
Wilbrand, like LetterBomb, is an exploit for the Wii that is triggered using the Wii Message Board.
|
||||
|
||||
|
|
@ -27,7 +27,7 @@ SD cards larger than 2GB will not work on Wii menu versions before 4.0.
|
|||
|
||||
1. On your Wii, go to `Wii Settings`, and make note of the version at the top right. Proceed to `Internet` -> `Console Information` and also make note of your MAC address.
|
||||
1. Visit [wilbrand.donut.eu.org](https://wilbrand.donut.eu.org/), input your Wii MAC, version, region, ensure `Bundle the HackMii Installer for me!` is checked, and cut either wire.
|
||||
|
||||
|
||||
1. Click on "Download your .zip".
|
||||
1. Extract the contents of the downloaded ZIP to the root of your SD card.
|
||||
1. Take out your SD card and insert it in your Wii.
|
||||
|
|
@ -37,7 +37,7 @@ SD cards larger than 2GB will not work on Wii menu versions before 4.0.
|
|||
+ Ensure the date on your Wii is correct, otherwise you might be unable to find the letter.
|
||||
+ The mail may have appeared on the previous or next day.
|
||||
+ If you don't see the green letter, check if any errors appear in the SD card sections in `Data Management`. If any do, there may be an issue with the SD card format or the Wii's SD card reader.
|
||||
|
||||
|
||||
|
||||
If this didn't work for you, [try another exploit](get-started) or try [Wilbrand CLI](#wilbrand-cli).
|
||||
|
||||
|
|
@ -67,12 +67,12 @@ SD cards larger than 2GB will not work on Wii menu versions before 4.0.
|
|||
|
||||
+ Windows: `.\Wilbrand.exe AA-BB-CC-DD-EE-FF MM/DD/YYYY VERSION X:`
|
||||
+ `X:` is the drive letter of your SD card.
|
||||
|
||||
|
||||
|
||||
+ Linux/MacOS: `./Wilbrand AA-BB-CC-DD-EE-FF MM/DD/YYYY VERSION /media/mount_dir`
|
||||
+ If you have not opened your terminal directly in the folder Wilbrand was extracted to, use `cd` to enter it first, eg. `cd ~/Desktop/Wilbrand`
|
||||
+ `/media/mount_dir` is the folder your SD card is mounted in. This may vary depending on your Linux distro.
|
||||
|
||||
|
||||
|
||||
1. Extract the HackMii Installer v1.2 to a folder on your PC.
|
||||
+ You may also simply open the zip file in your archive manager.
|
||||
|
|
@ -84,7 +84,7 @@ SD cards larger than 2GB will not work on Wii menu versions before 4.0.
|
|||
+ Ensure the date on your Wii is correct, otherwise you might be unable to find the letter.
|
||||
+ The mail may have appeared on the previous or next day.
|
||||
+ If you don't see the green letter, check if any errors appear in the SD card sections in `Data Management`. If any do, there may be an issue with the SD card format or the Wii's SD card reader.
|
||||
|
||||
|
||||
|
||||
[Continue to Homebrew Channel and BootMii Installation](hbc)
|
||||
{: .notice--info}
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ title: "YAWM ModMii Edition"
|
|||
|
||||
{% include toc title="Table of Contents" %}
|
||||
|
||||
|
||||
|
||||
|
||||
YAWM ModMii Edition is an application that can install WADs and launch homebrew applications.
|
||||
This tutorial will show you how to install WADs.
|
||||
|
|
@ -23,13 +23,13 @@ This tutorial will show you how to install WADs.
|
|||
#### Section II - Installing WADs
|
||||
|
||||
1. Select the source device that has the WAD file(s) you would like to install.
|
||||
|
||||
|
||||
1. Navigate to the folder that has the WAD files.
|
||||
+ If you have a folder named `wad`, it will be opened automatically.
|
||||
|
||||
|
||||
1. Navigate to the WAD file you would like to install and press `A`.
|
||||
+ If you would like to install multiple WAD files at once, press `+` on each of them, then press `A`.
|
||||
|
||||
|
||||
1. Press A again to install the WAD(s).
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -5,13 +5,13 @@ title: "RiiConnect24 DNS Update"
|
|||
If you need help with anything regarding this tutorial, please join [the RiiConnect24 Discord server](https://discord.gg/rc24) (recommended) or [e-mail us at support@riiconnect24.net](mailto:support@riiconnect24.net).
|
||||
{: .notice--info}
|
||||
|
||||
|
||||
|
||||
|
||||
Our official DNS Address has been updated. We require all users to change it. Failure in doing so will result in losing access to most or every RiiConnect24 service.
|
||||
|
||||
The old address will be supported until it's `DEPRECATION` date. We will remind you using Wii Mail or our [Discord server](https://discord.gg/rc24) about the need to change the DNS Address in the next few months.
|
||||
|
||||
We've restricted access to Forecast Channel and News Channel for users still using the old DNS Address. Users will also see a new EULA when trying to enable WiiConnect24 reminding them about the change.   
|
||||
We've restricted access to Forecast Channel and News Channel for users still using the old DNS Address. Users will also see a new EULA when trying to enable WiiConnect24 reminding them about the change.   
|
||||
|
||||
To update your entered DNS Address please follow these steps:
|
||||
|
||||
|
|
|
|||
|
|
@ -6,3 +6,31 @@
|
|||
|
||||
@import "minimal-mistakes/skins/{{ site.minimal_mistakes_skin | default: 'default' }}"; // skin
|
||||
@import "minimal-mistakes"; // main partials
|
||||
|
||||
.revisiontable {
|
||||
display: grid;
|
||||
}
|
||||
|
||||
.auto-grid-width {
|
||||
grid-auto-columns: minmax(0, 1fr);
|
||||
}
|
||||
|
||||
.auto-grid-height {
|
||||
grid-template-rows: 0fr;
|
||||
}
|
||||
|
||||
.revisiontable div {
|
||||
border: 1px solid;
|
||||
}
|
||||
|
||||
.console-img {
|
||||
margin-top: auto;
|
||||
margin-bottom: auto;
|
||||
}
|
||||
|
||||
.r1 { grid-row: 1; }
|
||||
.r2 { grid-row: 2; }
|
||||
.c1 { grid-column: 1; }
|
||||
.c2 { grid-column: 2; }
|
||||
.c3 { grid-column: 3; }
|
||||
.c4 { grid-column: 4; }
|
||||
|
|
|
|||
|
|
@ -5,13 +5,13 @@
|
|||
"start_url": "/",
|
||||
"icons": [
|
||||
{
|
||||
"src": "./android-chrome-192x192.png",
|
||||
"src": "/images/site-config/android-chrome-192x192.png",
|
||||
"sizes": "192x192",
|
||||
"type": "image/png",
|
||||
"purpose": "maskable"
|
||||
},
|
||||
{
|
||||
"src": "./android-chrome-512x512.png",
|
||||
"src": "/images/site-config/android-chrome-512x512.png",
|
||||
"sizes": "512x512",
|
||||
"type": "image/png",
|
||||
"purpose": "any"
|
||||
0
images/IOS-Patcher/iospatcher_1.jpg → images/#unused#/IOS-Patcher/iospatcher_1.jpg
Executable file → Normal file
0
images/IOS-Patcher/iospatcher_1.jpg → images/#unused#/IOS-Patcher/iospatcher_1.jpg
Executable file → Normal file
|
Before Width: | Height: | Size: 19 KiB After Width: | Height: | Size: 19 KiB |
0
images/IOS-Patcher/iospatcher_2.jpg → images/#unused#/IOS-Patcher/iospatcher_2.jpg
Executable file → Normal file
0
images/IOS-Patcher/iospatcher_2.jpg → images/#unused#/IOS-Patcher/iospatcher_2.jpg
Executable file → Normal file
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 14 KiB |
0
images/IOS-Patcher/iospatcher_3.jpg → images/#unused#/IOS-Patcher/iospatcher_3.jpg
Executable file → Normal file
0
images/IOS-Patcher/iospatcher_3.jpg → images/#unused#/IOS-Patcher/iospatcher_3.jpg
Executable file → Normal file
|
Before Width: | Height: | Size: 20 KiB After Width: | Height: | Size: 20 KiB |
0
images/IOS-Patcher/iospatcher_4.jpg → images/#unused#/IOS-Patcher/iospatcher_4.jpg
Executable file → Normal file
0
images/IOS-Patcher/iospatcher_4.jpg → images/#unused#/IOS-Patcher/iospatcher_4.jpg
Executable file → Normal file
|
Before Width: | Height: | Size: 19 KiB After Width: | Height: | Size: 19 KiB |
0
images/IOS-Patcher/iospatcher_mainscreen.jpg → images/#unused#/IOS-Patcher/iospatcher_mainscreen.jpg
Executable file → Normal file
0
images/IOS-Patcher/iospatcher_mainscreen.jpg → images/#unused#/IOS-Patcher/iospatcher_mainscreen.jpg
Executable file → Normal file
|
Before Width: | Height: | Size: 28 KiB After Width: | Height: | Size: 28 KiB |
0
images/IOS-Patcher/netinstall.jpg → images/#unused#/IOS-Patcher/netinstall.jpg
Executable file → Normal file
0
images/IOS-Patcher/netinstall.jpg → images/#unused#/IOS-Patcher/netinstall.jpg
Executable file → Normal file
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 14 KiB |
0
images/IOS-Patcher/netinstall_downloading.jpg → images/#unused#/IOS-Patcher/netinstall_downloading.jpg
Executable file → Normal file
0
images/IOS-Patcher/netinstall_downloading.jpg → images/#unused#/IOS-Patcher/netinstall_downloading.jpg
Executable file → Normal file
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 41 KiB After Width: | Height: | Size: 41 KiB |
0
images/RiiConnect24/WiiXplorer_1.png → images/#unused#/RiiConnect24/WiiXplorer_1.png
Executable file → Normal file
0
images/RiiConnect24/WiiXplorer_1.png → images/#unused#/RiiConnect24/WiiXplorer_1.png
Executable file → Normal file
|
Before Width: | Height: | Size: 36 KiB After Width: | Height: | Size: 36 KiB |
0
images/RiiConnect24/WiiXplorer_2.png → images/#unused#/RiiConnect24/WiiXplorer_2.png
Executable file → Normal file
0
images/RiiConnect24/WiiXplorer_2.png → images/#unused#/RiiConnect24/WiiXplorer_2.png
Executable file → Normal file
|
Before Width: | Height: | Size: 36 KiB After Width: | Height: | Size: 36 KiB |
0
images/RiiConnect24/WiiXplorer_3.png → images/#unused#/RiiConnect24/WiiXplorer_3.png
Executable file → Normal file
0
images/RiiConnect24/WiiXplorer_3.png → images/#unused#/RiiConnect24/WiiXplorer_3.png
Executable file → Normal file
|
Before Width: | Height: | Size: 31 KiB After Width: | Height: | Size: 31 KiB |
0
images/RiiConnect24/WiiXplorer_4.png → images/#unused#/RiiConnect24/WiiXplorer_4.png
Executable file → Normal file
0
images/RiiConnect24/WiiXplorer_4.png → images/#unused#/RiiConnect24/WiiXplorer_4.png
Executable file → Normal file
|
Before Width: | Height: | Size: 23 KiB After Width: | Height: | Size: 23 KiB |
0
images/RiiConnect24/WiiXplorer_5.png → images/#unused#/RiiConnect24/WiiXplorer_5.png
Executable file → Normal file
0
images/RiiConnect24/WiiXplorer_5.png → images/#unused#/RiiConnect24/WiiXplorer_5.png
Executable file → Normal file
|
Before Width: | Height: | Size: 26 KiB After Width: | Height: | Size: 26 KiB |
0
images/RiiConnect24/WiiXplorer_6.png → images/#unused#/RiiConnect24/WiiXplorer_6.png
Executable file → Normal file
0
images/RiiConnect24/WiiXplorer_6.png → images/#unused#/RiiConnect24/WiiXplorer_6.png
Executable file → Normal file
|
Before Width: | Height: | Size: 28 KiB After Width: | Height: | Size: 28 KiB |
0
images/RiiConnect24/WiiXplorer_7.png → images/#unused#/RiiConnect24/WiiXplorer_7.png
Executable file → Normal file
0
images/RiiConnect24/WiiXplorer_7.png → images/#unused#/RiiConnect24/WiiXplorer_7.png
Executable file → Normal file
|
Before Width: | Height: | Size: 41 KiB After Width: | Height: | Size: 41 KiB |
0
images/RiiConnect24/WiiXplorer_8.png → images/#unused#/RiiConnect24/WiiXplorer_8.png
Executable file → Normal file
0
images/RiiConnect24/WiiXplorer_8.png → images/#unused#/RiiConnect24/WiiXplorer_8.png
Executable file → Normal file
|
Before Width: | Height: | Size: 22 KiB After Width: | Height: | Size: 22 KiB |
0
images/RiiConnect24/WiiXplorer_9.png → images/#unused#/RiiConnect24/WiiXplorer_9.png
Executable file → Normal file
0
images/RiiConnect24/WiiXplorer_9.png → images/#unused#/RiiConnect24/WiiXplorer_9.png
Executable file → Normal file
|
Before Width: | Height: | Size: 28 KiB After Width: | Height: | Size: 28 KiB |
0
images/RiiConnect24/clock/battery.jpg → images/#unused#/RiiConnect24/clock/battery.jpg
Executable file → Normal file
0
images/RiiConnect24/clock/battery.jpg → images/#unused#/RiiConnect24/clock/battery.jpg
Executable file → Normal file
|
Before Width: | Height: | Size: 36 KiB After Width: | Height: | Size: 36 KiB |
0
images/RiiConnect24/clock/batterycover.jpg → images/#unused#/RiiConnect24/clock/batterycover.jpg
Executable file → Normal file
0
images/RiiConnect24/clock/batterycover.jpg → images/#unused#/RiiConnect24/clock/batterycover.jpg
Executable file → Normal file
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 14 KiB |
0
images/RiiConnect24/clock/plug.jpg → images/#unused#/RiiConnect24/clock/plug.jpg
Executable file → Normal file
0
images/RiiConnect24/clock/plug.jpg → images/#unused#/RiiConnect24/clock/plug.jpg
Executable file → Normal file
|
Before Width: | Height: | Size: 19 KiB After Width: | Height: | Size: 19 KiB |
0
images/RiiConnect24/clock/screwdriver.jpg → images/#unused#/RiiConnect24/clock/screwdriver.jpg
Executable file → Normal file
0
images/RiiConnect24/clock/screwdriver.jpg → images/#unused#/RiiConnect24/clock/screwdriver.jpg
Executable file → Normal file
|
Before Width: | Height: | Size: 20 KiB After Width: | Height: | Size: 20 KiB |
0
images/RiiConnect24/clock/unplug.jpg → images/#unused#/RiiConnect24/clock/unplug.jpg
Executable file → Normal file
0
images/RiiConnect24/clock/unplug.jpg → images/#unused#/RiiConnect24/clock/unplug.jpg
Executable file → Normal file
|
Before Width: | Height: | Size: 26 KiB After Width: | Height: | Size: 26 KiB |
|
Before Width: | Height: | Size: 135 KiB After Width: | Height: | Size: 135 KiB |
0
images/Theme/common-key.png → images/#unused#/Theme/common-key.png
Executable file → Normal file
0
images/Theme/common-key.png → images/#unused#/Theme/common-key.png
Executable file → Normal file
|
Before Width: | Height: | Size: 1.4 KiB After Width: | Height: | Size: 1.4 KiB |
0
images/WiiModLite/1.gif → images/#unused#/WiiModLite/1.gif
Executable file → Normal file
0
images/WiiModLite/1.gif → images/#unused#/WiiModLite/1.gif
Executable file → Normal file
|
Before Width: | Height: | Size: 658 KiB After Width: | Height: | Size: 658 KiB |
0
images/WiiModLite/2.png → images/#unused#/WiiModLite/2.png
Executable file → Normal file
0
images/WiiModLite/2.png → images/#unused#/WiiModLite/2.png
Executable file → Normal file
|
Before Width: | Height: | Size: 21 KiB After Width: | Height: | Size: 21 KiB |
0
images/WiiModLite/3.png → images/#unused#/WiiModLite/3.png
Executable file → Normal file
0
images/WiiModLite/3.png → images/#unused#/WiiModLite/3.png
Executable file → Normal file
|
Before Width: | Height: | Size: 11 KiB After Width: | Height: | Size: 11 KiB |
0
images/WiiModLite/4.gif → images/#unused#/WiiModLite/4.gif
Executable file → Normal file
0
images/WiiModLite/4.gif → images/#unused#/WiiModLite/4.gif
Executable file → Normal file
|
Before Width: | Height: | Size: 18 KiB After Width: | Height: | Size: 18 KiB |
0
images/WiiModLite/5.png → images/#unused#/WiiModLite/5.png
Executable file → Normal file
0
images/WiiModLite/5.png → images/#unused#/WiiModLite/5.png
Executable file → Normal file
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 13 KiB |
0
images/WiiModLite/6.png → images/#unused#/WiiModLite/6.png
Executable file → Normal file
0
images/WiiModLite/6.png → images/#unused#/WiiModLite/6.png
Executable file → Normal file
|
Before Width: | Height: | Size: 79 KiB After Width: | Height: | Size: 79 KiB |
0
images/WiiModLite/7.png → images/#unused#/WiiModLite/7.png
Executable file → Normal file
0
images/WiiModLite/7.png → images/#unused#/WiiModLite/7.png
Executable file → Normal file
|
Before Width: | Height: | Size: 131 KiB After Width: | Height: | Size: 131 KiB |
|
|
@ -1,7 +1,7 @@
|
|||
document.addEventListener('DOMContentLoaded', init, false);
|
||||
function init() {
|
||||
if ('serviceWorker' in navigator) {
|
||||
navigator.serviceWorker.register('/images/service-worker.js')
|
||||
navigator.serviceWorker.register('/assets/js/service-worker.js')
|
||||
.then((reg) => {
|
||||
// Service worker registration confirmed
|
||||
}, (err) => {
|
||||
0
images/vWii/Install249.png → images/#unused#/vwii/Install249.png
Executable file → Normal file
0
images/vWii/Install249.png → images/#unused#/vwii/Install249.png
Executable file → Normal file
|
Before Width: | Height: | Size: 79 KiB After Width: | Height: | Size: 79 KiB |
0
images/vWii/Install250.png → images/#unused#/vwii/Install250.png
Executable file → Normal file
0
images/vWii/Install250.png → images/#unused#/vwii/Install250.png
Executable file → Normal file
|
Before Width: | Height: | Size: 78 KiB After Width: | Height: | Size: 78 KiB |
0
images/vWii/Results.jpg → images/#unused#/vwii/Results.jpg
Executable file → Normal file
0
images/vWii/Results.jpg → images/#unused#/vwii/Results.jpg
Executable file → Normal file
|
Before Width: | Height: | Size: 10 KiB After Width: | Height: | Size: 10 KiB |
0
images/vWii/ScamScreen.png → images/#unused#/vwii/ScamScreen.png
Executable file → Normal file
0
images/vWii/ScamScreen.png → images/#unused#/vwii/ScamScreen.png
Executable file → Normal file
|
Before Width: | Height: | Size: 56 KiB After Width: | Height: | Size: 56 KiB |
0
images/vWii/StartWuphax.png → images/#unused#/vwii/StartWuphax.png
Executable file → Normal file
0
images/vWii/StartWuphax.png → images/#unused#/vwii/StartWuphax.png
Executable file → Normal file
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 13 KiB |
0
images/vWii/SuccessHBC.png → images/#unused#/vwii/SuccessHBC.png
Executable file → Normal file
0
images/vWii/SuccessHBC.png → images/#unused#/vwii/SuccessHBC.png
Executable file → Normal file
|
Before Width: | Height: | Size: 49 KiB After Width: | Height: | Size: 49 KiB |
0
images/vWii/d2x.png → images/#unused#/vwii/d2x.png
Executable file → Normal file
0
images/vWii/d2x.png → images/#unused#/vwii/d2x.png
Executable file → Normal file
|
Before Width: | Height: | Size: 4.9 KiB After Width: | Height: | Size: 4.9 KiB |
|
Before Width: | Height: | Size: 28 KiB After Width: | Height: | Size: 28 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 42 KiB |
BIN
images/Wii/MacAddress.png
Normal file
BIN
images/Wii/MacAddress.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 239 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 53 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 112 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 72 KiB After Width: | Height: | Size: 221 KiB |
|
Before Width: | Height: | Size: 4.1 KiB After Width: | Height: | Size: 4.1 KiB |
BIN
images/bricks/sysfiles-corrupted.jpg
Normal file
BIN
images/bricks/sysfiles-corrupted.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 24 KiB |
|
Before Width: | Height: | Size: 116 KiB After Width: | Height: | Size: 116 KiB |
|
Before Width: | Height: | Size: 50 KiB After Width: | Height: | Size: 50 KiB |
|
Before Width: | Height: | Size: 47 KiB After Width: | Height: | Size: 47 KiB |
|
Before Width: | Height: | Size: 52 KiB After Width: | Height: | Size: 52 KiB |
Some files were not shown because too many files have changed in this diff Show more
Loading…
Reference in a new issue