221 lines
15 KiB
Markdown
221 lines
15 KiB
Markdown
---
|
||
title: "变砖"
|
||
---
|
||
|
||
{% include toc title="Table of Contents" %}
|
||
|
||
“变砖” 通常意味着您的 Wii 已经到了只能作为[砖块](https://wikipedia.org/wiki/Brick)使用的地步。 <br> 变砖的原因很多,通常是由于通过自制对系统进行的不当修改所致。
|
||
|
||
# Brick Prevention
|
||
|
||
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:
|
||
|
||
+ **Do NOT follow old Wii modding tutorials, use old homebrew, or use video guides on the Internet unless it is EXPLICITLY RECOMMENDED by the homebrew developer.**
|
||
+ **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 restore NAND backups from other consoles!**
|
||
+ **Do NOT use a Nintendo Wi-Fi Connection service unless it is known to be RCE patched (such as [Wiimmfi](wiimmfi)). Doing otherwise could allow a malicious actor to BRICK your Wii!**
|
||
+ **Only install updates for your own region!**.
|
||
+ 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 applying system updates to your console, and consider seeking support for further assistance.
|
||
+ **Do NOT delete or modify system files, and do NOT install any system file mods unless you know what you are doing!**
|
||
+ An example of modifying files going wrong is replacing IOS80 on Wii mini, which may result in a [Wi-Fi Brick](bricks#wi-fi-brick).
|
||
+ **Do NOT install homebrew from untrustworthy sources or if the source code is not available.**
|
||
+ Software on the [Open Shop Channel](osc) is safe.
|
||
+ 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), so 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 ESPECIALLY careful when using applications 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 your electricity is unstable (e.g. storm, power outage), postpone what you are doing until you have a stable power source.
|
||
+ This applies to dangerous processes such as BootMii NAND restoration, which could lead to a [full brick](#low-level-brick) if anything goes wrong.
|
||
|
||
In any case, you should absolutely:
|
||
+ Have BootMii installed as boot2 if available, but otherwise as IOS.
|
||
+ Have Priiloader installed regardless of BootMii installation method.
|
||
+ Backup your NAND with BootMii and always have a valid spare copy on hand, but especially before attempting anything risky. Note that in some brick scenarios, BootMii is not accessible, so plan ahead.
|
||
|
||
# Diagnosis
|
||
|
||
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.
|
||
|
||
+ Turn on your Wii.
|
||
+ Nothing happens, black screen. 解决这个问题的唯一办法是通过恢复菜单启动游戏来启动自制。 只有当您拆开 GameCube 手柄,按住所有 4 个十字键,同时将 GameCube 手柄插入 Wii 的第 4 个插槽,打开 Wii 后才能使用它。 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. Maintenance 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 Maintenance Mode by holding +/- on the health/warning screen, see [mail brick](bricks#mail-brick).
|
||
+ Wii Menu brick(Wii 菜单砖)
|
||
+ 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 Menu brick(Wii 菜单砖) 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!
|
||
|
||
# Brick Types
|
||
|
||
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).
|
||
|
||
#### 原因
|
||
Semibrick(半砖)在安装了不同区域的 Wii 菜单或不同区域的自定义主题时发生。 这会导致 Wii 找不到 Wii 设置页面文件。
|
||
|
||
![](/images/bricks/semibrick.png)
|
||
|
||
#### 解决方案
|
||
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 csm-installer to reinstall the original theme.
|
||
|
||
如果这是由您安装的 Wii 菜单 WAD 引起的,使用 [NUS Downloader](https://wiibrew.org/wiki/NUSD) 重新获取原始 Wii 菜单。
|
||
|
||
下载 Wii 菜单 WAD 时要小心。 确保选择与更正后的区域相同的版本。
|
||
{: .notice--danger}
|
||
|
||
如果您确实正在更改区域,请使用 [ARC-ME](https://github.com/modmii/Any-Region-Changer-ModMii-Edition/releases) 自动修复所有区域设置,以便与您的 Wii 菜单相匹配。
|
||
|
||
## 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.
|
||
|
||
![](/images/bricks/sysfiles-corrupted.jpg)
|
||
|
||
#### 原因
|
||
Banner bricks(横幅砖)会在安装了含无效的 Wii 菜单横幅或图标的 WAD 文件时出现。
|
||
|
||
#### 解决方案
|
||
如果有幸进入 Wii 菜单,请进入 Homebrew Channel 并卸载有问题的 WAD。
|
||
|
||
如果安装了 [Priiloader](priiloader),请在打开 Wii 时按住 RESET 进入。 选择 Homebrew Channel,然后使用 WAD 管理器卸载有问题的 WAD。
|
||
|
||
如果没有 Priiloader,维护模式也许值得一试。 在健康与安全屏幕上按住 `+` 和 `-`。 (不要按 `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.
|
||
|
||
#### 原因
|
||
Theme brick(主题砖)在安装了格式错误的主题时发生。
|
||
|
||
#### 解决方案
|
||
To resolve this issue, open HBC through Priiloader or BootMii as boot2 and access csm-installer to install a default theme such as the base Wii Menu theme. Alternatively, go into [YAWM ModMii Edition](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. Maintenance mode is still accessible.
|
||
|
||
#### 原因
|
||
当 Wii 收到大量邮件时,就会出现 "mail brick(邮件砖)"。 这会导致 Wii 崩溃。
|
||
|
||
#### 解决方案
|
||
By entering holding + and - on the warning screen, maintenance 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).
|
||
|
||
(不要按 `A`!) <br> 进入 Homebrew Channel,使用 [cdbackup](https://oscwii.org/library/app/cdbackup) 删除 Wii 留言板数据。
|
||
|
||
## Wii 菜单砖
|
||
|
||
#### 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 by any other means.
|
||
|
||
#### 原因
|
||
此砖与 [Semibrick(半砖)](#semibrick)相比更为致命。 If your SYSCONF (system configuration file) gets corrupt or damaged, the Wii will regenerate it and start the setup phase.
|
||
|
||
然而,设置页面的位置与 Wii 设置页面类似。 如果Wii 菜单或主题的区域不正确,Wii 将无法找到它们。
|
||
|
||
![](/images/bricks/sysmenu-brick.png)
|
||
|
||
#### 解决方案
|
||
|
||
如果您还有 [Priiloader](priiloader),请使用它进入 Homebrew Channel 并重新安装原始主题文件/原始 Wii 菜单。
|
||
|
||
如果您没有 Priiloader,可以试试 [BlueBomb](bluebomb)。
|
||
|
||
Alternatively, [Recovery Mode](recovery-mode) can be used to attempt a fix.
|
||
|
||
## KoreanKii/Error 003 Brick
|
||
|
||
#### Symptoms
|
||
Screen shows up as listed below on normal boot.
|
||
|
||
`Error:003`<br> `unauthorized device has been detected.`<br>
|
||
|
||
![](/images/bricks/error-003.png)
|
||
|
||
#### 原因
|
||
When releasing the Korean Wiis, Nintendo changed the encryption key for these units specifically as a last ditch attempt at preventing homebrew. While obviously this failed, they also left a check in the System Menu versions 4.2/4.3 to determine whether or not the Korean Key is present on a system software region that is **not** Korean. If this check succeeds, the error triggers and the Wii is effectively bricked.
|
||
|
||
这通常是在不知情的更改区域的韩版 Wii 进行 Wii 系统更新后立即发生的情况。
|
||
|
||
#### 解决方案
|
||
由于此砖最常在 Wii 菜单更新后发生,因此 Priiloader 将不会存在。
|
||
|
||
韩版 Wii 在 Wii 菜单 3.3 发布时推出,当时任天堂 [修复了 boot1 中的 Trucha 漏洞](https://wiibrew.org/wiki/3.3#Changes), 因此任何韩版 Wii 都无法将 BootMii 安装为 Boot2。
|
||
|
||
While these caveats leave the Wii in a particularly dangerous situation, **it is still fixable**. This involves going into [Recovery Mode](recovery-mode), where an exploit can be triggered in order to gain access to the Homebrew Channel and revert the conditions that caused the brick.
|
||
|
||
## IOS brick(IOS 砖)
|
||
|
||
#### 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.
|
||
|
||
#### 原因
|
||
当 Wii 菜单 IOS 是一个[存根(stub)](http://wiibrew.org/wiki/Stub_IOS)时发生。 这通常是尝试降级 Wii 菜单的结果。 If this error began happening after installing a normal IOS80 to a Wii mini, see [Wi-Fi brick](bricks#wi-fi-brick).
|
||
|
||
#### 解决方案
|
||
[Recovery mode](recovery-mode) may or may not be accessible due to the nature of the brick, but Priiloader will almost always not work. 必须将 BootMii 安装为 boot2 才能解决这个问题。 If these conditions are not met, see [low-level brick](bricks#low-level-brick).
|
||
|
||
您可以还原 NAND 备份,或执行以下步骤:
|
||
|
||
1. 使用 [NUS Downloader](https://wiibrew.org/wiki/NUSD) 打包原始 Wii 菜单的 WAD。
|
||
1. 使用 BootMii 进入 Homebrew Channel,并使用 WAD 管理器安装 Wii 菜单 WAD。
|
||
|
||
## Wi-Fi brick(Wi-Fi 砖)
|
||
|
||
#### 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.
|
||
|
||
#### 原因
|
||
当 Wii 的 Wi-Fi(或蓝牙)模块损坏或未正确插入时,就会出现这种状况。 在这种情况下,Wii 会在等待 IOS 响应时卡在黑屏上。
|
||
|
||
这也会在 Wii Mini 上安装了普通的 Wii IOS 时发生,因为 Wii Mini 没有 Wi-Fi 模块。
|
||
|
||
#### 解决方案
|
||
要解决这个问题,可尝试重新安装或更换 Wi-Fi/蓝牙模块。
|
||
|
||
如果使用 Wii Mini,则必须安装 Wi-Fi 模块。
|
||
|
||
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, neither can BootMii as boot2 (or it never existed in the first place), for all intents and purposes the console appears dead.
|
||
|
||
#### 原因
|
||
当 boot1/boot2 损坏时会出现此故障。
|
||
|
||
#### 解决方案
|
||
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. Consider consulting online help or buying another Wii.
|
||
|
||
[Click here to go back to the site index.](site-navigation)
|
||
{: .notice--info}
|