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.
I confirmed it from r4isdhc's official sale.
Since they replaced the mainboard used by the flashcard, the newer than 2020 model are no longer support ntrboot.
* Added F3
* Added guide
* Delete f3x-(mac).txt
* whoop
* Update _main.js
* Fixing mistakes part1
* Removed "The Latest Release of" text
* Reworded cd command
* Update f3-(mac).txt
* Make user move f3 folder to desktop
suggested by lilyuwuu so that way all users can be on the same page when doing the command line instructions.
* Made one line not sound as run on
* Changed “Run” to type
Decided to change it based off the command typing sections in the linux sd formatting guide
* Changed “F3X” to F3
How did i miss this
* Changed F3 again
I missed it again like how
* Add files via upload
* Not needed due to F3XSwift
* Rewritten for F3XSwift
* Update _main.js
* changed to F3XSwift
How did I miss this when I originally started it
* changed to F3XSwift
* corrected issues pointed out
* Changed to resolve conflict&readd sd notice
* fixed again
* Update get-started.txt
* made it appear once
accidentally cp'd it during editing
* readied for version issues
* Update get-started.txt
* Update f3x-(mac).txt
* F3XSwift-Mac: Add macOS compatibility warning; clarify instructions
* get-started: Switch link from F3X to F3XSwift
* site-nav: Add F3X to list
Co-authored-by: Lily <lily@uwuu.ca>
* 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.
