- 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>
This commit splits the rather large Flipnote exploit section into the
following includes:
- exploit-flipnote
- install-boot9strap-b9stool
This also rewords portions of the Fredtool steps in individual pages so
that the steps to launch Flipnote Studio are now in the Flipnote
Exploit section, so as to make the b9stool section flow through easily.
This also allows to remove more arguments within the `include_relative`
directive.
After having this page in production for some time, it is clear that
the year numbers simply do not matter. For instance, the original 2DS
*also* shows 2011 on the backplate, yet it was only released in 2013.
Instead, add estimated manufacture dates for each model. These years
and guesses are *not* proven; however, it gets us relatively close to
what is expected based on the release date and how long it was being
manufactured.
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.
---
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.
While theoretically users should only end up here on O3DS 11.4 and
above, we may still need this page for users where Soundhax is broken
due to an incompatible CVer:NVer combination, which may lead to a user
running safecerthax on 11.3 and below only for Luma3DS to black screen.
This brings the NAND backup steps up to speed with the more up-to-date
Finalizing Setup prior to adding an automated script, which fixes
a few issues such as:
- missing step to copy `.bin.sha` from the SD card
- inconsistency where guide tells to copy `essential.exefs` without
extracting it first
There *is* no next page. This is just to check whether the console can
actually run safecerthax.
This was also an issue in kartdlphax as well, as it used the same
include previously.
- 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.
Digital game and save data loss is a common fear, so I believe it should be added to the pre-installation FAQ.
This commit adds back a sentence that used to be on the home page that I believe was first written by lilyuwuu in pull #1888, then removed by the same person in commit 93b4f3b "basic information rework".
- 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
luma 13.x does not currently work on older firmwares (confirmed up to 10.5.0-30). This change will result in inconsistent luma versions depending on method followed but should not otherwise impact cfw installation / guide routing
- 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
