This brings the NAND backup steps up to speed with the more up-to-date
Finalizing Setup prior to adding an automated script, which fixes
a few issues such as:
- missing step to copy `.bin.sha` from the SD card
- inconsistency where guide tells to copy `essential.exefs` without
extracting it first
There *is* no next page. This is just to check whether the console can
actually run safecerthax.
This was also an issue in kartdlphax as well, as it used the same
include previously.
- use latest luma for non-soundhax/ntrboot/hardmod/updating-b9s/a9lh-to-b9s pages, to ensure more people end up on latest luma (ie. user error from copying files to sd)
- explicitly delete then copy boot.firm and boot.3dsx to lessen chance of error there
Change recommended for standardization purposes (currently soundhax and ntrboot use 12.0.1 and don't prompt people to update which is inconsistent)
At the moment, 13.x is unable to boot on at least 10.6 and below. So, to ensure that guide pages are (at least mostly) consistent, using 12.0.1 on all* pages and then prompting user to update luma in finalizing setup. This involves reorganizing finalizing setup a bit so that the cfw check and system update come before we modify the sd card.
Note: Change currently not copied to kartdlphax as this would involve reverting to an older commit and would cause complications with 3gx 12.0.1.
Digital game and save data loss is a common fear, so I believe it should be added to the pre-installation FAQ.
This commit adds back a sentence that used to be on the home page that I believe was first written by lilyuwuu in pull #1888, then removed by the same person in commit 93b4f3b "basic information rework".
- explicitly name the three folders in the zip to make it easier for people to tell what goes where
- add note about merging folders in macos
- retool inline troubleshooting about not booting into godmode9 to reflect the script
luma 13.x does not currently work on older firmwares (confirmed up to 10.5.0-30). This change will result in inconsistent luma versions depending on method followed but should not otherwise impact cfw installation / guide routing
- Add the text "Disclaimer" to potential risks to illustrate that it's more us resigning liability rather than a likely risk
- Add new section "File placement terminology" that explains what root of SD is, how /directories/ are illustrated and how <identifiers> work
- Change GitHub and file-extension images to better illustrate the point
- Reword GitHub text to better illustrate the point
- get-started: add "select the model of your console" because that is what you need to do
