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
- 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
- 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
- `SDMC` folder is gone
- another file to cleanup from root of SD
- new SD root image
- more clarification on version support
- BetaV3 (upcoming at time of commit) allows MSET9 to be used between
11.4 and 11.7 on o3ds and between 11.4 and 11.17 on new3ds, but it
requires modifying a value in the script. Since we're only using
this page on 11.17 o3ds for now, there's no need to directly point
this out, but this commit slightly changes the wording a bit to
account for this.
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>
Replaces the root layout image for petit-compwner with an image that
looks more in line with the guide (it's still Windows 10 instead of
Windows 11, however)
- 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
readd screenshots that were lost when switching bb3
remove screenshots not used in years
add inline troubleshooting for red screen usm
fix language in troubleshooting
add screenshot for boot9strap folder
add screenshot for 3ds folder
add file layout screenshots for hbl-pichaxx and hbl-usm
fix typo that breaks screenshot link in usm and hbl-usm
remove some unnecessary indenting
firwmare -> firmware
id1 folder consistency based on what people should have at that point of the guide
- 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
file-ext: add win11 screenshot
file-ext: return -> continue as file extension warning is no longer on get started
homepage: add note about file extensions; move ban notice
