Clarification on the 5.5.6 update
This commit is contained in:
parent
160def5d09
commit
d696c54a90
2 changed files with 2 additions and 2 deletions
|
@ -1,6 +1,6 @@
|
|||
# Blocking Updates
|
||||
---
|
||||
All currently known Wii U exploits can, unlike e.g. the Nintendo Switch RCM exploit, be patched by a system update. Although the Wii U is no longer officially supported, Nintendo may still release updates for it. Namely, the updates 5.5.3, 5.5.4 and 5.5.5 were all released after the Wii U was discontinued, so blocking updates is still a recommended action.
|
||||
All currently known Wii U exploits can, unlike e.g. the Nintendo Switch RCM exploit, be patched by a system update. Although the Wii U is no longer officially supported, Nintendo may still release updates for it. Namely, the updates 5.5.3 up to 5.5.6 were all released after the Wii U was discontinued, so blocking updates is still a recommended action.
|
||||
|
||||
### Instructions {docsify-ignore}
|
||||
|
||||
|
|
|
@ -40,7 +40,7 @@ This guide has the end goal of taking a completely unmodified Wii U from stock t
|
|||
!> Before beginning the guide, you must know the risks of Wii U hacking: **EVERY** time you modify your system, there is always the potential for an **UNRECOVERABLE** brick. They’re rare but still a possibility so make sure you follow **ALL** directions **EXACTLY!**
|
||||
|
||||
>
|
||||
> This guide will work on all Wii U consoles in all regions on firmware 5.5.6 or below.
|
||||
> This guide will work on all Wii U consoles in all regions on the latest firmware (5.5.6 for North American consoles, 5.5.5 for all other regions) or below.
|
||||
>
|
||||
> You will need the following in order to successfully follow this guide:
|
||||
>
|
||||
|
|
Loading…
Reference in a new issue