Update finalizing settup page (and add troubleshooting section) to avoid unnecessary CTR transfers on section II (#1850)

* Update finalizing-setup.txt

* Update finalizing-setup.txt

* Update finalizing-setup.txt

* Update troubleshooting.txt

* Update troubleshooting.txt

* Update troubleshooting.txt

* Update finalizing-setup.txt

* Update troubleshooting.txt

* Update troubleshooting.txt

* Update finalizing-setup.txt

* Update troubleshooting.txt

* Update troubleshooting.txt

* Create troubleshooting.txt

* Update troubleshooting.txt

* Update troubleshooting.txt

* Update troubleshooting.txt

* Update troubleshooting.txt

Work in progress save

* Update finalizing-setup.txt

* Update finalizing-setup.txt

* Update troubleshooting.txt

* Update troubleshooting.txt

* Update troubleshooting.txt

* Update troubleshooting.txt

* Update troubleshooting.txt

* Update troubleshooting.txt

* Update troubleshooting.txt

* Update troubleshooting.txt

* Update troubleshooting.txt

change how the buttons are said to open safe mode to more match the rest of the guide 

and reword the phrasing of "and following the prompts" to -----> "and following the on screen prompts". some people might get caught up on that so i changed it to be more clear

* Update troubleshooting.txt

* Update troubleshooting.txt
This commit is contained in:
TheGoofBall64 2021-03-14 18:21:44 -04:00 committed by GitHub
parent 48510fd087
commit 1e9c04c179
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 15 additions and 1 deletions

View file

@ -67,7 +67,7 @@ If, before following this guide, you already had an EmuNAND setup and would like
+ Updates while using B9S + Luma (what you have) are safe + Updates while using B9S + Luma (what you have) are safe
+ The updater may display a message saying "Your system is up to date" instead of updating. This is normal if you are already up to date; continue with the next section + The updater may display a message saying "Your system is up to date" instead of updating. This is normal if you are already up to date; continue with the next section
+ If this gives you an error, set your DNS settings to "auto" + If this gives you an error, set your DNS settings to "auto"
+ If this still gives you an error, [follow CTRTransfer](ctrtransfer), then try updating again + If this still gives you an error, [follow this troubleshooting guide](troubleshooting#system-update-error-after-installing-cfw)
#### Section III - Homebrew Launcher #### Section III - Homebrew Launcher

View file

@ -156,3 +156,17 @@ Browser based exploits (such as browserhax or 2xrsa) are often unstable and cras
1. Your device is bricked 1. Your device is bricked
1. You will need to get an ntrboot-comptible flashcart (one of the ones on [this list](ntrboot) or a [hardmod](https://gbatemp.net/threads/414498/), or repair / replace your device 1. You will need to get an ntrboot-comptible flashcart (one of the ones on [this list](ntrboot) or a [hardmod](https://gbatemp.net/threads/414498/), or repair / replace your device
1. For support (in English), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) 1. For support (in English), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)
## System update error after installing CFW
Occasionally, updates may fail to install after installing CFW. To fix this, reboot your device after each step of this section, then try updating again.
1. Set your DNS settings to "Auto"
1. Move closer to your WiFi router
1. Update from Safe Mode by turning off the console, holding (Left Shoulder) + (Right Shoulder) + (D-Pad Up) + (A) on boot, and following the on-screen prompts
1. Delete your WiFi connection, then reconnect to your WiFi again
1. Reboot your WiFi router
1. Connect to a different WiFi connection, like a mobile hotspot
1. Nintendo servers may be down; Try again later
1. If you still get an error, [follow CTRTransfer](ctrtransfer), then try again
1. For support (in English), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)