(cleanup syntax) |
(initial conversion from 3ds.hacks.guide, converted using pandoc) |
||
| Line 1: | Line 1: | ||
{{ | {% include toc title="Table of Contents" %} | ||
{% capture technical_info %} | |||
<summary><em>Technical Details (optional)</em></summary> | |||
An excellent guide to getting a hardmod can be found [https://gbatemp.net/threads/414498/ here]. | An excellent guide to getting a hardmod can be found [https://gbatemp.net/threads/414498/ here]. | ||
| Line 6: | Line 9: | ||
This is a currently working implementation of the "FIRM partitions known-plaintext" exploit detailed [https://www.3dbrew.org/wiki/3DS_System_Flaws here]. | This is a currently working implementation of the "FIRM partitions known-plaintext" exploit detailed [https://www.3dbrew.org/wiki/3DS_System_Flaws here]. | ||
Using a hardmod, we can dump the NAND image, install custom firmware to the NAND image, then re-install the hacked NAND image to the console. | Using a hardmod, we can dump the NAND image, install custom firmware to the NAND image, then re-install the hacked NAND image to the console. | ||
{% endcapture %} | |||
<details>{{ technical_info | markdownify }}</details> | |||
{: .notice--info} | |||
<span id="compatibility-notes"></span> | |||
=== Compatibility Notes === | === Compatibility Notes === | ||
| Line 16: | Line 25: | ||
This will work on New 3DS, New 2DS, Old 3DS, and Old 2DS on ''all'' versions that you have a corresponding <code>.firm</code> for. | This will work on New 3DS, New 2DS, Old 3DS, and Old 2DS on ''all'' versions that you have a corresponding <code>.firm</code> for. | ||
<span id="what-you-need"></span> | |||
=== What You Need === | === What You Need === | ||
| Line 188: | Line 198: | ||
|} | |} | ||
<span id="instructions"></span> | |||
=== Instructions === | === Instructions === | ||
<span id="section-i---prep-work"></span> | |||
==== Section I - Prep Work ==== | ==== Section I - Prep Work ==== | ||
| Line 205: | Line 217: | ||
# Move your NAND backup to the hardmod-b9s-installer folder on your computer and rename it to <code>NAND.bin</code> | # Move your NAND backup to the hardmod-b9s-installer folder on your computer and rename it to <code>NAND.bin</code> | ||
<span id="section-ii---installing-boot9strap"></span> | |||
==== Section II - Installing boot9strap ==== | ==== Section II - Installing boot9strap ==== | ||
| Line 215: | Line 228: | ||
# Power off your console | # Power off your console | ||
# Disconnect your hardmod | # Disconnect your hardmod | ||
# Press and hold (Select), and while holding (Select), power on your console | # Press and hold (Select), and while holding (Select), power on your console {% include_relative include/configure-luma3ds.txt %} | ||
{% include_relative include/luma3ds-installed-note.txt %} | |||
----- | ----- | ||
<span | <span id="continue-to-finalizing-setup"></span> | ||
=== Continue to [[finalizing-setup|Finalizing Setup]] === | |||
{: .notice--primary} | |||
{{hg imported}} | {{hg imported}} | ||
Revision as of 00:05, 25 January 2024
{% include toc title="Table of Contents" %}
{% capture technical_info %}
<summary>Technical Details (optional)</summary>
An excellent guide to getting a hardmod can be found here.
This is a currently working implementation of the "FIRM partitions known-plaintext" exploit detailed here.
Using a hardmod, we can dump the NAND image, install custom firmware to the NAND image, then re-install the hacked NAND image to the console.
{% endcapture %}
<details>Template:Technical info</details> {: .notice--info}
Compatibility Notes
To use the magnet links on this page, you will need a torrent client like qBittorrent or Deluge.
To extract the .7z files linked on this page, you will need a file archiver like 7-Zip or The Unarchiver.
This will work on New 3DS, New 2DS, Old 3DS, and Old 2DS on all versions that you have a corresponding .firm for.
What You Need
- Your NAND image extracted using your hardmod
- The latest release of boot9strap (direct download)
- The latest version of hardmod-b9s-installer
- Windows users can use the compiled
.exe, while Mac and Linux users will need to have Python 3 installed to run the.py
- Windows users can use the compiled
- The latest release of Luma3DS (the Luma3DS
.zipfile) - The
.firmcorresponding to your console and version:
Instructions
Section I - Prep Work
In this section, you will download the necessary files for the hardmod and dump the NAND image in preparation to install custom firmware.
- Power off your console
- Insert your SD card into your computer
- Copy
boot.firmandboot.3dsxfrom the Luma3DS.zipto the root of your SD card - Copy the hardmod-b9s-installer folder from the hardmod-b9s-installer
.zipto your computer - Copy your downloaded
.firmto the hardmod-b9s-installer folder on your computer - Rename your downloaded
.firmin the hardmod-b9s-installer folder on your computer tocurrent.firm - Copy
boot9strap.firmandboot9strap.firm.shafrom the boot9strap.zipto the hardmod-b9s-installer folder on your computer - Reinsert your SD card into your console
- Use your hardmod to create a NAND backup
- Move your NAND backup to the hardmod-b9s-installer folder on your computer and rename it to
NAND.bin
Section II - Installing boot9strap
In this section, you will install custom firmware to the dumped NAND image, and then install this NAND image back onto the console to install custom firmware on it.
- Run hardmod-b9s-installer
- Windows Users: Run
install-b9s.exe - Mac and Linux Users: Run
install-b9s.py
- Windows Users: Run
- Flash your outputted
NAND-patched.binto your console with your hardmod - Power off your console
- Disconnect your hardmod
- Press and hold (Select), and while holding (Select), power on your console {% include_relative include/configure-luma3ds.txt %}
{% include_relative include/luma3ds-installed-note.txt %}
Continue to Finalizing Setup
{: .notice--primary}