N-archive/Guide_Wii
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

New translations bricks.md (Norwegian)

Browse source
This commit is contained in:
ihaveahax 2024-03-02 00:52:51 -06:00
parent 74107ef358
commit 78ec669674
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
_pages/no_NO/bricks.md
View file

@ -13,7 +13,7 @@ Preventing a brick involves many rules that range between common sense and fail-
+ **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!**
+ **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!**
@ -42,7 +42,7 @@ In any case, you should absolutely:
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 Wii.
+ Turn on your 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).
@ -132,7 +132,7 @@ This is usually an immediate follow-up to a Wii System Update on an unsuspecting
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.
#### 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.
This brick is a more fatal version of a [Semibrick](#semibrick). If your SYSCONF (system configuration file) gets corrupt or damaged, the Wii will regenerate it and start the setup phase.
However, the setup pages are in a similar location to the Wii settings pages. If you have an incorrect region Wii Menu or theme, the Wii cannot find them.
@ -146,7 +146,7 @@ If you still have [Priiloader](priiloader), use it to enter the Homebrew Channel
Alternatively, [Recovery Mode](recovery-mode) can be used to attempt a fix.
## Korean Kii/Error 003 Brick
## KoreanKii/Error 003 Brick
#### Symptoms
This brick occurs when boot1/boot2 is corrupt.