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
All themes are moved to `_theme` submodule, which will be shared with
other websites on hacks.guide.
Repository-specific files can be overlayed after the fact, such as
additional languages, custom JavaScript, progress table paths and the
like.
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
- `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.
- Clean up MSET9-specific files
- Update message for Error #14: CIA install fail (most likely happens
when file is corrupted)
- Update NAND backup link (darn you, dying link shorteners)
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>
All downstream changes from the theme (i.e. here) will be denoted with:
/* hacks-guide change start */
and
/* hacks-guide change end */
One-line changes are marked with
/* hacks-guide change */
next to it.
Since our theme does not have linear history with upstream, this allows
quicker identification of what exactly has differentiated downstream,
as we do have a few out-of-tree patches for extra functionality.
Manually create dbs folder to fix edge case where cp would not automatically create folder
Ask user to re-import DB if mount fail (this seems to most often occur if a dummy title database is lingering, but consent is asked for just to prevent potential data loss even though that should not even be a possibility)
Poweroff if Error #16 (title.db mount fail) is denied, to prevent proceeding script (which will not work)
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.
super-skaterhax is now a much more functional exploit alongside
nimdsphax, so ditch Seedminer for this device.
Only redirect to updating-firmware-(new-3ds) if the version is
11.16 or later, as opposed to 11.17 only previously.
Since we don't redirect 11.16, simplify code accordingly.
Closes#2323.
Fix logical error relating to NOSPACE (3DS would continue to have insufficient space if Nintendo 3DS folder is moved back, so SDFREE section now checks for BACKUPFLAG and if present skips that section)
Automatically skip NAND backup if BACKUPFLAG is detected (this flag cannot be tripped erroneously)
force nand backup if no nintendo 3ds folder (prevent user error)
use more forceful language for dummy title database creation
tell people to delete nand backup if nospace
- 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)
- All KOR models on 11.16 do seedminer, fredtool is still better than
frogtool
- Note the KOR O3DS browser quirk
- Mii mining on 11.15 O3DS only
- super-skaterhax has code for KOR N3DS, but unused for now as
seedminer gets there first
Well, I'll say never mix integer with bool
This new version literally inverted new/old for kor
I originally wrote it as !old, it's literally now !(new=1=true)
