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
As MSET9 has mostly matured, we will no longer need several other
exploits.
The following are removed:
- alternate-exploits (and all linked by it)
- All seedminer-related paths
- firmware update pages
- MSET9 now has extensive error-checking, which is almost fully accounted for in the troubleshooting (save for errors that shouldn't happen)
- Enhanced troubleshooting for ID1, pulled from the visual troubleshooter. Commonized and used for Seedminer multiple ID1 scenarios
- Update MSET9 page to account for mset9 v1.1
- Finalizing script v1.5.1 to remove errors.txt
- Reword uninstalling mset9 to removing mset9 for consistency and so that people hopefully don't skip it
- Add an additional message right before the finalizing setup link to make even fewer people skip it, hopefully
- Move Assert id0 troubleshooting to the top of mset9 (it's the first error people are likely to encounter)
- Add MSET9 detected to troubleshooting
- Update to script v1.5.0, which adds proper(ish) MSET9 detection
- instructions now work on more than o3ds 11.7-11.17
- clarify python needs to be installed
- add instruction to select console and model
- add informational blurb to the top of each section
- reword do not skip warning
- new troubleshooting (infinite loading)
- have troubleshooting account for model selector
- small troubleshooting grammar edits
Adapted from 3DS:Alternate Exploits/Installing boot9strap (MSET9) on
the wiki, a page written primarily by @Gruetzig.
Also modifies FAQ accordingly.
Co-authored-by: Gruetzig <florianavilov@gmail.com>
Script now uses and imports a donor title database to prevent confusing rebooting / database resetting - no more "Dummy title database found"!
Explicitly check for A:/dbs/title.db to determine existence of title database (likely inconsequential)
Check if A:/dbs/title.db is valid
Check if any dependency files are missing and/or fail to install
Clean up SD card files for Alternate Exploits, menuhax67, nimdsphax
Catch double-backups (i.e. user tries to re-run script without Nintendo 3DS folder after already having made a NAND backup)
Troubleshooting also updated accordingly.
- 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.
* exchange fredtool-legacy for menuhax-uloader
* troubleshooting: add troubleshooting for menuhax67 leftover
* menuhax-uloader->menuhax
* fix wording of stuff
* make bb3 and uloader direct downloads
* add image for the home menu icon
* add commas
* wipe wipe and do do(usm -> menuhax)
- Wrong soundhax file should not recommend updating to latest fw
- agbhax TWN/CHN edgecase troubleshooting should no longer be necessary with JS routing
lily
ManiacOfGitHub
Botman
Gruetzig
Blueness
TophattedWasTaken
lifehackerhansol
Lily
Florian