A complete guide to 3DS custom firmware, from stock to boot9strap.
7c3af39e12
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
|
||
|---|---|---|
| .github | ||
| _data/navigation | ||
| _includes | ||
| _pages | ||
| _sass | ||
| _theme@13df935df5 | ||
| assets | ||
| gm9_scripts | ||
| images | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| _config.yml | ||
| banner.js | ||
| clean_translations.py | ||
| CNAME | ||
| crowdin.yaml | ||
| Gemfile | ||
| LICENSE | ||
| package.json | ||
| README.md | ||
| rss.py | ||
| rss.xml | ||
3ds.hacks.guide
A complete guide to 3DS (and 2DS) custom firmware, from stock to boot9strap.
Running the site locally
This requires the following installed on your system:
- ruby(-dev)
- bundler
To test the website locally, clone the source code:
git clone https://github.com/hacks-guide/Guide_3DS --recurse-submodules
cd Guide_3DS
Then simply run the following commands:
bundle config set --local path vendor/bundle
bundle install
bundle exec jekyll serve
The website should now be running on http://127.0.0.1:4000/.