choo choo, all aboard the train to OCS
* finalizing: switch to file-management scriptrunner
Switch to scriptrunner for file management (to lessen user error from incorrectly copying files).
Thus, users will need to copy just two files: finalize_helper.firm to SD:/luma/payloads/ (which will have to be created by the user) and finalize.romfs (which ends up on root of SD).
This change allows for better checking of file integrity and lessens the chance of user error from incorrectly copying files.
The scriptrunner's task is to load finalize.romfs from the SD card, unpack it, and to copy its contents to root of SD.
The intended location of finalize.romfs is root of SD, but the scriptrunner will attempt to move the file if it is found in SD:/Nintendo 3DS, SD:/DCIM, SD:/luma, or SD:/luma/payloads.
Remove errors relating to missing files (since that should no longer be possible).
Add visuals on the top screen for error resolution, with QR codes to the guide / NH where appropriate.
* finalizing: inline chainloader
in case people have more than one payload
---
Revert "safecerthax: use Luma3DS v12.0.1"
This reverts commit 643d765387.
---
Revert "installing-boot9strap-(ntrboot): sync v12.0.1 release string with other pages"
This reverts commit 96e5a8dde8.
---
Revert "bb3-twn: use latest luma"
This reverts commit 9eed676426.
---
Revert "treewide: use luma latest; change finalize"
This reverts commit 54fa51da39.
---
Revert "atob: specify 12.0.1 in instructions"
This reverts commit 73a9ddb3c4.
---
Revert "TEMP: use 12.0.1, update to 13.x in finalize"
This reverts commit a2e847c7ba.
---
Revert "TEMPORARY: use luma v12.0.1 for soundhax, ntrboot"
This reverts commit b47ab171d1.
- 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.
- 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
- Move script backups to /gm9/backups/.
- Remove redundant silent A:/backups/essential.exefs backup.
- Fix logical error relating to moving Nintendo 3DS folder off of SD card.
- If Nintendo 3DS folder is not detected, script will now propmt user to skip to making a NAND backup
- This will create a file in SD:/gm9/flags/ called BACKUPFLAG
- If this flag is present when the Nintendo 3DS folder is present (re-added), the script will tell the user that a NAND backup likely already exists and prompt the user to either create another backup or to skip creating the backup
- Move database dummyflag from A:/dbs/ to SD:/gm9/flags/
- Change errors to error levels, and adjust top screen accordingly
- "Information" indicates that the user didn't do anything wrong, but that the user must do something that deviates from the normal guide (e.g. create title database, NAND backup flag tripped) - indicated on top screen with `(i)`
- "Warning" indicates that the script will continue, but will not complete as intended (e.g. no Nintendo 3DS folder) - indicated on top screen with `/!\`
- "Error" indicates that the script cannot continue due to user error (incorrect GM9 version, missing files, etc) - indicated on top screen with `:(`
- "Fatal Error" indicates that the script has triggered an error that should not occur and requires debugging (CIA install fail, invalid SD size) - indicated on top screen with `wtf?`
Guide also adjusted accordingly.
I'm not even going to try to point people to the right direction from
here, if they literally couldn't even get CFW installed and got to this
page then they need help.
* Add includes for ctrtransfer steps
- Region changing and CTRTransfer uses this
- Also split HBL open options, it is also used by finalizing setup
* Commonize NAND backup steps
Finalizing Setup won't use this include for the time being. But we
should use it for GM9 usage as well as Region Changing.
* Commonize GM9 SD format steps
Pages using this include:
- godmode9-usage
- move-emunand
* remove usage of is-powered-off, just do that in the main page
* always power off after NAND backup, it's trivial to get back in
Trying to explain what "unmounting" is to a user is going to be
confusing anyway
* Unconditionally don't set up an emuNAND, also remove usage of is-powered-off
* Fix rendering
- Convert FAQ and Troubleshooting pages to clickable dropdowns to improve readability.
- Add separate table of contents to Troubleshooting (for mobile users)
- Remove a couple of irrelevant troubleshooting
- Update pages that link to troubleshooting to use new headers
* faq+troubleshooting: dropdowns
- Convert FAQ and Troubleshooting pages to clickable dropdowns to improve readability.
- Add separate table of contents to Troubleshooting (for mobile users)
- Remove a couple of irrelevant troubleshooting
- Update pages that link to troubleshooting to use new headers
* a9lh-to-b9s: fix typo
- Cropped screenshots so that they take up less space.
- Fix the notices in Finalizing Setup (they got broken)
- censor id0 in most places as an additional measure to prevent people from using example id0/id1
- clarify that id0 is system-specific in seedminer
