* 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
A few people have been confused about how to load GodMode9 in Section VI, and have accidentally pressed the button too late or tried to time the START button, etc. The fool-proof explanation on how to load GodMode9 or the chainloader menu appears to be to press and hold START, and keep holding the START button when powering on the console.
Section VI, step 2 makes this clearer.
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.
This page currently links to the BannerBomb3 DSiWare generator, which is incorrect for this guide. I have changed the link to point to the correct page, which is the UnSAFE_MODE DSiWare generator.
I found someone who misspelled "payloads" as "playloads", causing
confusion for a while until I saw a directory listing. I don't know how
common exactly this is but I feel a note could be added here.
I'm not too happy about how this is worded though. Especially the path
which might need to be updated following #1829.
* add formatting-sd-(mac)
Unfinished, needs steps for Yosemite/10.10 and before.
* formatting-sd-(mac): steps for <=10.10
* formatting-sd-(mac): link to correct linux page
* formatting-sd-(mac): allow any volume label
* add formatting-sd-(windows)
Unfinished page, needs a few more updates.
* formatting-sd-(windows): volume label should be blank
* formatting-sd-(windows): add warning after choosing drive letter
* formatting-sd-(windows): allow any volume label
* update format link
* formatting-sd-(windows): use 32768 allocation unit size for 64GB
This commit aims to make guide wording on some pages more consistent to make it easier to understand.
A warning has been added above each Legacy Method page, and the links to their respective tools have been fixed.
HBL-Soundhax: Account for browsers trying to play Soundhax as a video
B9S-Soundhax: Switch to v1.2 release of pre9otherapp; use v2.0 in case of prolonged failure; add file extension clarification
HBL-Pichaxx: Changed DSiWare Dumper link to Frogtool, added note about 11.14, updated pichaxx injector link
HBL-Soundhax: changed 3.0.0 to 2.1.0 (the cart update section may need to be removed/reworded entirely as it is unclear...)
B9S-USM: Copied troubleshooting/QoL text fixes from HBL-USM; changed github link to LumaTeam
Legacy Methods: PicHaxx capitalization consistency
The "if you get an error" line works under the assumption that no user error is happening. It is not possible to in-line troubleshoot all potential user error cases without increasing confusion.
The "No applications found" line has been modified to be more consistent with the rest of the guide.
The site navigation link to BrowserHax 2020 has also been renamed to be consistent with the name of the page.
