* 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.
* 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.
The timebomb was pushed back from September 3, 2019 to September 3, 2024 in the most recent updates to the relevant flashcarts. These changes fix issue #1715 .
More detail:
The "R4iSDHC 20XX" carts were updated from 3.9b to 4.0b, and I figured out the new timebomb date by testing it on my own r4isdhc.com flashcart.
I don't own any r4i-sdhc.com carts, so I can't test it. However, I found a [store page](https://www.r4wood.com/home/16-r4i-sdhc-3ds-rts-card-for-3ds-all-systems.html) for this flashcart explaining that the "Latest time bomb for 1.85b kernel is Sept 3rd, 2024." The latest kernel version before 1.85b was 1.84b, but for some reason the current guide references kernel version 1.87. I think this must be a typo because I couldn't actually find any evidence that there ever was a 1.87, so I believe 1.85b is now the latest.
I hope my changes are received well.
Currently, the guide instructs users to format SD cards with 32K
allocation size in all cases. However, users with SD cards 128GB
or larger should use 64K to prevent issues with some applications,
including GBA VC.
change ds internet settings test to dsiware management test, revamp legacy methods, change pichaxx to link to frogtool
Co-authored-by: lily <lily@uwuu.ca>
