* troubleshooting: complete overhaul
* Add "Failed to launch SB9SI" warning; fix typo
* Add new troubleshooting; reword red+white screen
- Change red/white to red/purple/pink and white
- Clarify the difference between the two stock An error has occurred messages
- Add troubleshooting for being stuck on "doing agbhax" and "preparearm9fortwl"
- make join NH message more consistent
* Remove browser TS, add pichaxx/BB3/Fred TS, change headings
Much of these troubleshooting instructions are taken from https://3ds.eiphax.tech/issues and adapted for this page.
* Pichaxx troubleshooting update
Both an exception occurred and errdisp can appear on modded consoles
Split black screen with text and game starts normally because black screen with text can appear even if just otherapp.bin is missing
* add funny frii bricc splash warning
Co-authored-by: eip <36315290+eip618@users.noreply.github.com>, lily, hansol
After some complains from a dyslexic user, I decided to make 2 pretty minor changes
Section 3, step 1 - changed "all safety checks" to "all checks" - safeb9sinstaller just calls them "checks", so the word safety there was unneeded
Section 3, step 2 - changed "key combo given to install..." to "key combo given on the top screen to install..." - this specifically calls out where the combo will be given, to prevent users from looking at the bottom screen when the combo is on the top.
These QOL changes:
- Add information about DNS issues to safecerthax and SSLoth-Browser.
- Change instaces of "ntr boot9strap" and "standard boot9strap" to their actual filenames, to lessen confusion.
- Instructs users to click the QR code button in the camera before scanning it.
I have changed my mind about sacrificing flexibility for convenience. OCS was too much of a black box which, while well intentioned, just didn't work very well in the environment we have available to us.
