Rearranged vWii related files
This commit is contained in:
parent
ee64260ac5
commit
34668a9268
4 changed files with 11 additions and 11 deletions
|
@ -1,6 +1,6 @@
|
||||||
# IOS Folders and Paths
|
# IOS Folders and Paths
|
||||||
|
---
|
||||||
?> This page is primarily meant to be used with [Recover a Corrupted IOS](vwii/recover-ios)
|
?> This page is primarily meant to be used with [Recover a Corrupted IOS](troubleshooting/recover-ios)
|
||||||
|
|
||||||
?> IOS folders are located in /slccmpt01/title/00000001
|
?> IOS folders are located in /slccmpt01/title/00000001
|
||||||
|
|
||||||
|
@ -41,7 +41,7 @@ IOS |IOS Folder |.tik File |Title ID
|
||||||
<script src="https://cdn.jsdelivr.net/npm/docsify-pagination@2/dist/docsify-pagination.min.js"></script>
|
<script src="https://cdn.jsdelivr.net/npm/docsify-pagination@2/dist/docsify-pagination.min.js"></script>
|
||||||
<div class="docsify-pagination-container">
|
<div class="docsify-pagination-container">
|
||||||
<div class="pagination-item pagination-item--previous">
|
<div class="pagination-item pagination-item--previous">
|
||||||
<a href="#/vwii/recover-ios">
|
<a href="#/troubleshooting/recover-ios">
|
||||||
<div class="pagination-item-label">
|
<div class="pagination-item-label">
|
||||||
<svg class="icon" width="10" height="16" viewBox="0 0 10 16" xmlns="http://www.w3.org/2000/svg">
|
<svg class="icon" width="10" height="16" viewBox="0 0 10 16" xmlns="http://www.w3.org/2000/svg">
|
||||||
<polyline fill="none" vector-effect="non-scaling-stroke" points="8,2 2,8 8,14"></polyline>
|
<polyline fill="none" vector-effect="non-scaling-stroke" points="8,2 2,8 8,14"></polyline>
|
|
@ -1,8 +1,8 @@
|
||||||
# Recover a Corrupted IOS
|
# Recover a Corrupted IOS
|
||||||
|
---
|
||||||
This page will guide you through the process of recovering a corrupted IOS on your vWii.
|
This page will guide you through the process of recovering a corrupted IOS on your vWii.
|
||||||
|
|
||||||
!> Do not use this method for anything else than [Recovering your Mii Channel](vwii/recover-mii-channel) or the following page.
|
!> Do not use this method for anything else than [Recovering your Mii Channel](troubleshooting/recover-mii-channel) or the following page.
|
||||||
|
|
||||||
### What You Need
|
### What You Need
|
||||||
|
|
||||||
|
@ -58,7 +58,7 @@ This page will guide you through the process of recovering a corrupted IOS on yo
|
||||||
1. Launch FileZilla
|
1. Launch FileZilla
|
||||||
1. Type in the IP address displayed by your Wii U in the `Host` field at the top of the window and click on `Quickconnect`
|
1. Type in the IP address displayed by your Wii U in the `Host` field at the top of the window and click on `Quickconnect`
|
||||||
1. In FileZilla, navigate to `/slccmpt01/title/00000001`
|
1. In FileZilla, navigate to `/slccmpt01/title/00000001`
|
||||||
1. Go to [this page](vwii/ios-folders) to see which folder/ticket you need to delete
|
1. Go to [this page](troubleshooting/ios-folders) to see which folder/ticket you need to delete
|
||||||
1. Delete the corresponding folder of the IOS you want to recover
|
1. Delete the corresponding folder of the IOS you want to recover
|
||||||
1. Navigate to `/slccmpt01/ticket/00000001`
|
1. Navigate to `/slccmpt01/ticket/00000001`
|
||||||
1. Delete the corresponding `.tik` file of the IOS you want to recover
|
1. Delete the corresponding `.tik` file of the IOS you want to recover
|
|
@ -1,8 +1,8 @@
|
||||||
# Recover Your Lost or Corrupted Mii Channel
|
# Recover Your Lost or Corrupted Mii Channel
|
||||||
|
---
|
||||||
This page will guide you through the process of restoring your Mii Channel to a working state.
|
This page will guide you through the process of restoring your Mii Channel to a working state.
|
||||||
|
|
||||||
!> Do not use this method for anything else than [Recovering a Corrupted IOS](vwii/recover-ios) or the following page.
|
!> Do not use this method for anything else than [Recovering a Corrupted IOS](troubleshooting/recover-ios) or the following page.
|
||||||
|
|
||||||
### What You Need
|
### What You Need
|
||||||
|
|
|
@ -1,5 +1,5 @@
|
||||||
# vWii Modding Guide
|
# vWii Modding Guide
|
||||||
|
---
|
||||||
This page will guide you through the process of modding your vWii.
|
This page will guide you through the process of modding your vWii.
|
||||||
|
|
||||||
We will now place the required Homebrew files on the SD Card.
|
We will now place the required Homebrew files on the SD Card.
|
||||||
|
@ -42,7 +42,7 @@ We will now place the required Homebrew files on the SD Card.
|
||||||
1. Launch the [Homebrew Launcher](user-guide/vwii/browser-exploit)
|
1. Launch the [Homebrew Launcher](user-guide/vwii/browser-exploit)
|
||||||
1. Launch Wuphax
|
1. Launch Wuphax
|
||||||
1. Press `B` to restore the Mii Channel
|
1. Press `B` to restore the Mii Channel
|
||||||
- If for some reason, you cannot restore your backup, you will need to [reinstall your Mii Channel](vwii/recover-mii-channel)
|
- If for some reason, you cannot restore your backup, you will need to [reinstall your Mii Channel](troubleshooting/recover-mii-channel)
|
||||||
|
|
||||||
### NAND Backup
|
### NAND Backup
|
||||||
|
|
||||||
|
@ -86,7 +86,7 @@ In case anything goes wrong in the later process and your vWii ends up bricked,
|
||||||
|
|
||||||
### Patching IOS 80
|
### Patching IOS 80
|
||||||
|
|
||||||
!> If for any reason, the Wii U is turned off while patching IOS 80, your vWii will be bricked. This can be fixed by either extracting the IOS 80 from your previously made NAND backup and then replacing it over FTP or by [reinstalling IOS 80](vwii/recover-ios)
|
!> If for any reason, the Wii U is turned off while patching IOS 80, your vWii will be bricked. This can be fixed by either extracting the IOS 80 from your previously made NAND backup and then replacing it over FTP or by [reinstalling IOS 80](troubleshooting/recover-ios)
|
||||||
|
|
||||||
1. Launch Patched IOS 80 Installer for vWii
|
1. Launch Patched IOS 80 Installer for vWii
|
||||||
1. Read the warning screen and wait 30 seconds
|
1. Read the warning screen and wait 30 seconds
|
||||||
|
|
Loading…
Reference in a new issue