mirror of
https://github.com/hacks-guide/Guide_3DS.git
synced 2024-11-23 09:29:51 +00:00
treewide: s/device/console
This commit is contained in:
parent
5617e9de97
commit
8c2613d88b
@ -6,7 +6,7 @@ title: "A9LH to B9S"
|
||||
|
||||
### Required Reading
|
||||
|
||||
This page is for existing arm9loaderhax users to update their devices to boot9strap.
|
||||
This page is for existing arm9loaderhax users to update their consoles to boot9strap.
|
||||
|
||||
All future releases of Luma3DS will only be made in the `.firm` format, which will only be compatible with boot9strap and sighax. This means that to continue receiving the latest updates of Luma3DS, you should use this page to update your installation.
|
||||
|
||||
@ -35,7 +35,7 @@ Note that, only on New 3DS, `secret_sector.bin` is needed to revert the arm9load
|
||||
For all steps in this section, overwrite any existing files on your SD card.
|
||||
{: .notice--info}
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy `boot.firm` and `boot.3dsx` from the latest version Luma3DS `.zip` to the root of your SD card
|
||||
+ The root of the SD card refers to the initial directory on your SD card where you can see the Nintendo 3DS folder, but are not inside of it
|
||||
@ -50,20 +50,20 @@ For all steps in this section, overwrite any existing files on your SD card.
|
||||
![]({{ "/images/screenshots/a9lh-to-b9s-root-layout.png" | absolute_url }})
|
||||
{: .notice--info}
|
||||
|
||||
1. Reinsert your SD card into your device
|
||||
1. Reinsert your SD card into your console
|
||||
|
||||
#### Section II - Installing boot9strap
|
||||
|
||||
1. Boot your device while holding (Start) to launch SafeB9SInstaller
|
||||
1. Boot your console while holding (Start) to launch SafeB9SInstaller
|
||||
+ If you see the luma configuration screen instead of SafeB9SInstaller, simply press (Start), then shut down your 3DS and try again
|
||||
+ If this gives you an error, try either using a new SD card or formatting your current SD card (backup existing files first)
|
||||
1. Wait for all safety checks to complete
|
||||
+ If you get an "OTP Crypto Fail" error, download <i class="fa fa-magnet" aria-hidden="true" title="This is a magnet link. Use a torrent client to download the file."></i> - [aeskeydb.bin](magnet:?xt=urn:btih:d25dab06a7e127922d70ddaa4fe896709dc99a1e&dn=aeskeydb.bin&tr=udp%3a%2f%2ftracker.tiny-vps.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.lelux.fi%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.loadbt.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.moeking.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.monitorit4.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.ololosh.space%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.pomf.se%3a80%2fannounce&tr=udp%3a%2f%2ftracker.srv00.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.theoks.net%3a6969%2fannounce&tr=udp%3a%2f%2fopen.tracker.cl%3a1337%2fannounce&tr=udp%3a%2f%2ftracker.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.zerobytes.xyz%3a1337%2fannounce&tr=udp%3a%2f%2ftracker1.bt.moack.co.kr%3a80%2fannounce&tr=udp%3a%2f%2fvibe.sleepyinternetfun.xyz%3a1738%2fannounce&tr=udp%3a%2f%2fwww.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a6969%2fannounce&tr=udp%3a%2f%2f9.rarbg.com%3a2810%2fannounce&tr=udp%3a%2f%2ftracker.opentrackr.org%3a1337%2fannounce&tr=http%3a%2f%2fopenbittorrent.com%3a80%2fannounce&tr=udp%3a%2f%2fexodus.desync.com%3a6969%2fannounce), then put it in the `/boot9strap/` folder on your SD card and try again
|
||||
{%- include_relative include/install-boot9strap-safeb9sinstaller.txt inline="true" -%}
|
||||
1. Your device should have rebooted into the Luma3DS configuration menu
|
||||
1. Your console should have rebooted into the Luma3DS configuration menu
|
||||
+ Luma3DS configuration menu are settings for the Luma3DS custom firmware. Many of these settings may be useful for customization or debugging
|
||||
+ For the purpose of this guide, these settings will be left on default settings
|
||||
+ If you get a black screen, [follow this troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware)
|
||||
+ If you get a black screen, [follow this troubleshooting guide](troubleshooting#boot-issues-on-consoles-with-custom-firmware)
|
||||
1. Press (Start) to save and reboot
|
||||
|
||||
___
|
||||
|
@ -4,7 +4,7 @@ title: "Alternate Exploits"
|
||||
|
||||
{% include toc title="Table of Contents" %}
|
||||
|
||||
3DS / 3DS XL / 2DS devices on firmware 11.17.0 do not currently have any free, software-only methods. Therefore, all of the methods here have some sort of prerequisite.
|
||||
3DS / 3DS XL / 2DS consoles on firmware 11.17.0 do not currently have any free, software-only methods. Therefore, all of the methods here have some sort of prerequisite.
|
||||
|
||||
### Installed eShop titles
|
||||
|
||||
|
@ -31,7 +31,7 @@ These instructions work on USA, Europe, Japan, and Korea region consoles as indi
|
||||
|
||||
#### Section II - Hardware Button Check
|
||||
|
||||
In this section, you will see whether you can access Safe Mode on your device. This will determine which method you will follow on the next page.
|
||||
In this section, you will see whether you can access Safe Mode on your console. This will determine which method you will follow on the next page.
|
||||
|
||||
Your SD card should remain in your computer while you perform this check.
|
||||
|
||||
@ -41,7 +41,7 @@ ___
|
||||
|
||||
### Next steps: Choose an exploit
|
||||
|
||||
If the camera appeared in the previous section, Safe Mode is likely to be working on your device.
|
||||
If the camera appeared in the previous section, Safe Mode is likely to be working on your console.
|
||||
|
||||
If the camera appeared, continue to [Installing boot9strap (USM)](installing-boot9strap-(usm))
|
||||
{: .notice--primary}
|
||||
|
@ -28,7 +28,7 @@ These instructions are for Taiwanese consoles ONLY (as indicated by a T at the e
|
||||
|
||||
#### Section II - Prep Work
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy `boot.firm` and `boot.3dsx` from the Luma3DS `.zip` to the root of your SD card
|
||||
+ The root of the SD card refers to the initial directory on your SD card where you can see the Nintendo 3DS folder, but are not inside of it
|
||||
@ -58,21 +58,21 @@ These instructions are for Taiwanese consoles ONLY (as indicated by a T at the e
|
||||
+ If you already had the folder *and* there are any existing DSiWare backup files (`<8-character-id>.bin`) inside, copy them to your PC and remove them from your SD card
|
||||
1. Open the output_(name) `.zip` file and navigate to `China_Taiwan` -> `output_setup`
|
||||
1. Copy all six `.bin` files to the `Nintendo DSiWare` folder
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Launch System Settings on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
1. Launch System Settings on your console
|
||||
1. Navigate to `Data Management` -> `DSiWare` -> `SD Card` -> (page 2)
|
||||
1. Take note of what number is on the DSiWare title on the second page (it will be a number between 1 and 6)
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card
|
||||
1. Open the output_(name) `.zip` file and navigate to `China_Taiwan` -> `output_hax`
|
||||
1. Copy the `.bin` file that is the same number as the one that was on the second page of the DSiWare Management menu to the `Nintendo DSiWare` folder, and overwrite when prompted
|
||||
1. Power on your device
|
||||
1. Launch System Settings on your device
|
||||
1. Power on your console
|
||||
1. Launch System Settings on your console
|
||||
1. Navigate to `Data Management` -> `DSiWare` -> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
1. Wait a while
|
||||
+ The following should happen, in this order: A progress swirl, a short freeze, the bottom screen turning purple, the music stopping, then the device showing an error message and rebooting
|
||||
+ The following should happen, in this order: A progress swirl, a short freeze, the bottom screen turning purple, the music stopping, then the console showing an error message and rebooting
|
||||
+ If you did not see the purple screen, then something went wrong
|
||||
1. You should now have the file `42383821.bin` on the root of your SD card
|
||||
1. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card
|
||||
@ -94,14 +94,14 @@ These instructions are for Taiwanese consoles ONLY (as indicated by a T at the e
|
||||
1. Click the "output_(name).zip" link
|
||||
1. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card
|
||||
1. Copy the `484E4441.bin` file from the `hax` folder of the downloaded DSiWare archive (output_(name).zip) to the `Nintendo DSiWare` folder
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Launch System Settings on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
1. Launch System Settings on your console
|
||||
1. Navigate to `Data Management` -> `DSiWare`
|
||||
1. Under the “SD Card” section, select the “Haxxxxxxxxx!” title
|
||||
1. Select “Copy”, then select “OK”
|
||||
1. Exit System Settings
|
||||
1. Launch Download Play on your device (the orange icon with a 3DS on it)
|
||||
1. Launch Download Play on your console (the orange icon with a 3DS on it)
|
||||
1. Select "Nintendo DS"
|
||||
1. If the exploit was successful, your 3DS will have loaded into the JPN version of Flipnote Studio
|
||||
|
||||
@ -111,21 +111,21 @@ These instructions are for Taiwanese consoles ONLY (as indicated by a T at the e
|
||||
|
||||
#### Section VI - Luma3DS Configuration
|
||||
|
||||
1. Press and hold (Select), and while holding (Select), power on your device
|
||||
1. Press and hold (Select), and while holding (Select), power on your console
|
||||
{% include_relative include/configure-luma3ds.txt %}
|
||||
|
||||
#### Section VII - Restoring DS Download Play
|
||||
|
||||
1. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card
|
||||
1. Copy the `484E4441.bin` file from the `clean` folder of the downloaded DSiWare archive (output_(name).zip) to the `Nintendo DSiWare` folder
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Launch System Settings on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
1. Launch System Settings on your console
|
||||
1. Navigate to `Data Management` -> `DSiWare`
|
||||
1. Under the “SD Card” section, select the “Haxxxxxxxxx!” title
|
||||
1. Select “Copy”, then select “OK”
|
||||
1. Exit System Settings
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
|
||||
___
|
||||
|
||||
|
@ -40,7 +40,7 @@ ___
|
||||
|
||||
### Next steps: Choose an exploit
|
||||
|
||||
If the camera appeared in the previous section, Safe Mode is likely to be working on your device.
|
||||
If the camera appeared in the previous section, Safe Mode is likely to be working on your console.
|
||||
|
||||
If the camera appeared, continue to [Installing boot9strap (USM)](installing-boot9strap-(usm))
|
||||
{: .notice--primary}
|
||||
|
@ -6,7 +6,7 @@ title: "CTRTransfer"
|
||||
|
||||
### Required Reading
|
||||
|
||||
This is an add-on section for installing an 11.15.0 CTRTransfer image to your device.
|
||||
This is an add-on section for installing an 11.15.0 CTRTransfer image to your console.
|
||||
|
||||
This page assumes that you have already installed Luma3DS and boot9strap. If you followed this website to the end (Finalizing Setup), you have Luma3DS and boot9strap.
|
||||
{: .notice--info}
|
||||
@ -21,8 +21,8 @@ To download the CTRTransfer images on this page, you will need a torrent client
|
||||
|
||||
* The latest release of [GodMode9](https://github.com/d0k3/GodMode9/releases/latest) (the GodMode9 `.zip` file)
|
||||
* The latest release of [FBI](https://github.com/Steveice10/FBI/releases/latest) *(the`.3dsx` file)*
|
||||
* The 11.15.0 CTRTransfer image for your device and region
|
||||
*(if your device is not from one of these regions, just pick one that matches your device type)*:
|
||||
* The 11.15.0 CTRTransfer image for your console and region
|
||||
*(if your console is not from one of these regions, just pick one that matches your console type)*:
|
||||
{% include_relative include/ctrtransfer-images.txt %}
|
||||
|
||||
### Instructions
|
||||
|
@ -6,13 +6,13 @@ On this page, you will dump an installed DSiWare title from the eShop to your SD
|
||||
|
||||
## Instructions
|
||||
|
||||
1. Power on your device
|
||||
1. Power on your console
|
||||
1. If you haven't already, re-download your DSiWare title from the Nintendo eShop (instructions [here](https://en-americas-support.nintendo.com/app/answers/detail/a_id/607/~/how-to-download-or-redownload-content-in-nintendo-3ds-eshop))
|
||||
+ A DSiWare title's banner will be a white box with an icon inside of it that is likely animated
|
||||
1. Launch System Settings on your device
|
||||
1. Launch System Settings on your console
|
||||
1. Navigate to `Data Management` -> `DSiWare`
|
||||
1. Select your DSiWare title, then tap "Copy", then "OK"
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card
|
||||
+ `<ID0>` is the 32-letter folder name that you copied in Seedminer
|
||||
|
@ -7,7 +7,7 @@ title: "Dumping Movable (nimhax)"
|
||||
{% capture technical_info %}
|
||||
<summary><em>Technical Details (optional)</em></summary>
|
||||
|
||||
To install boot9strap on your device, we derive your device's unique encryption key. To accomplish this, we use the Homebrew Launcher to launch nimhax and dump the data encryption key (movable.sed) from your device.
|
||||
To install boot9strap on your console, we derive your console's unique encryption key. To accomplish this, we use the Homebrew Launcher to launch nimhax and dump the data encryption key (movable.sed) from your console.
|
||||
|
||||
For a more technical explanation, see [here](https://github.com/luigoalma/nimhax/) for information about the nimhax exploit.
|
||||
|
||||
@ -23,11 +23,11 @@ For a more technical explanation, see [here](https://github.com/luigoalma/nimhax
|
||||
|
||||
#### Section I - Prep Work
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy the `nimhax` folder from the nimhax `.zip` to the `/3ds/` folder on your SD card
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
|
||||
![]({{ "/images/screenshots/nimhax-location.png" | absolute_url }})
|
||||
{: .notice--info}
|
||||
@ -40,7 +40,7 @@ For a more technical explanation, see [here](https://github.com/luigoalma/nimhax
|
||||
|
||||
### Next step: Frogtool
|
||||
|
||||
Once you have your device's encryption key (`movable.sed`), you can use it in conjunction with Frogtool, which uses your `movable.sed` file to inject and take advantage of JPN Flipnote Studio. \
|
||||
Once you have your console's encryption key (`movable.sed`), you can use it in conjunction with Frogtool, which uses your `movable.sed` file to inject and take advantage of JPN Flipnote Studio. \
|
||||
While this method is faster, it requires downloading a file with a torrent client. Do not follow this method if you're unable to use a torrent client.
|
||||
|
||||
Continue to [Installing boot9strap (Frogtool)](installing-boot9strap-(frogtool))
|
||||
|
@ -22,23 +22,23 @@ These instructions are written for use with GodMode9 v2.0.0 or later. If you hav
|
||||
|
||||
### Instructions
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy `GodMode9.firm` from the GodMode9 `.zip` to the `/luma/payloads/` folder on your SD card
|
||||
1. Copy the `gm9` folder from the GodMode9 `.zip` to the root of your SD card
|
||||
1. Reinsert your SD card into your device
|
||||
1. Reinsert your SD card into your console
|
||||
|
||||
## Dumping a Game Cartridge
|
||||
|
||||
{% capture notice %}
|
||||
Insert the game cartridge you intend to dump into your device
|
||||
Insert the game cartridge you intend to dump into your console
|
||||
+ 3DS game cartridges will be dumped to a `.3ds` format
|
||||
+ NDS game cartridges will be dumped to a `.nds` format
|
||||
{% endcapture %}
|
||||
|
||||
<div class="notice--info">{{ notice | markdownify }}</div>
|
||||
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
1. Navigate to `[C:] GAMECART`
|
||||
1. Follow the steps applicable to your game cartridge:
|
||||
+ **3DS Game Cartridge:** Press (A) on `[TitleID].trim.3ds` to select it
|
||||
@ -52,7 +52,7 @@ Insert the game cartridge you intend to dump into your device
|
||||
This will only work for 3DS games; it is not possible to install an NDS game cartridge to the system as a title.
|
||||
{: .notice--info}
|
||||
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
1. Navigate to `[C:] GAMECART`
|
||||
1. Press (A) on `[TitleID].trim.3ds` to select it, then select "NCSD image options...", then select "Install game image"
|
||||
1. Press (A) to unlock SysNAND (lvl1) writing, then input the key combo given
|
||||
@ -63,7 +63,7 @@ This will only work for 3DS games; it is not possible to install an NDS game car
|
||||
This should only be used if [Installing a Game Cartridge Directly to the System](#installing-a-game-cartridge-directly-to-the-system) does not work.
|
||||
{: .notice--info}
|
||||
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
1. Navigate to `[C:] GAMECART`
|
||||
1. Press (A) on `[TitleID].trim.3ds` to select it, then select "NCSD image options...", then select "Build CIA from file"
|
||||
1. Your installable `.cia` formatted file will be outputted to the `/gm9/out/` folder on your SD card
|
||||
@ -73,7 +73,7 @@ This should only be used if [Installing a Game Cartridge Directly to the System]
|
||||
This allows dumping of both System- and User-installed digital titles, such as ones downloaded from the eShop.
|
||||
{: .notice--info}
|
||||
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
1. Press (Home) to bring up the action menu
|
||||
1. Select "Title manager"
|
||||
1. Select one of the following depending on the type of title you wish to dump
|
||||
@ -95,14 +95,14 @@ To identify a `<TitleID>.gbavc.sav` file's Title ID, you can get a listing of al
|
||||
1. Do the following process for each GBA VC game that you want to back up the save for:
|
||||
+ Launch the GBA VC game
|
||||
+ Exit the GBA VC game
|
||||
+ Power off your device
|
||||
+ Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
+ Power off your console
|
||||
+ Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
+ Navigate to `[S:] SYSNAND VIRTUAL`
|
||||
+ Press (A) on `agbsave.bin` to select it
|
||||
+ Select "AGBSAVE options..."
|
||||
+ Select "Dump GBA VC save"
|
||||
+ Press (A) to continue
|
||||
+ Press (Start) to reboot your device
|
||||
+ Press (Start) to reboot your console
|
||||
|
||||
## Restore GBA VC Saves
|
||||
|
||||
@ -112,8 +112,8 @@ To identify a `<TitleID>.gbavc.sav` file's Title ID, you can get a listing of al
|
||||
1. Do the following process for each GBA VC game that you want to restore the save for:
|
||||
+ Launch the GBA VC game
|
||||
+ Exit the GBA VC game
|
||||
+ Power off your device
|
||||
+ Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
+ Power off your console
|
||||
+ Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
+ Navigate to `[0:] SDCARD` -> `gm9`
|
||||
+ Press (Y) on the `<TitleID>.gbavc.sav` file you wish to restore to copy it
|
||||
+ Press (B) to return to the main menu
|
||||
@ -122,7 +122,7 @@ To identify a `<TitleID>.gbavc.sav` file's Title ID, you can get a listing of al
|
||||
+ Select "AGBSAVE options..."
|
||||
+ Select "Inject GBA VC save"
|
||||
+ Press (A) to continue
|
||||
+ Press (Start) to reboot your device
|
||||
+ Press (Start) to reboot your console
|
||||
+ Launch the GBA VC game
|
||||
+ Exit the GBA VC game
|
||||
|
||||
@ -131,7 +131,7 @@ To identify a `<TitleID>.gbavc.sav` file's Title ID, you can get a listing of al
|
||||
For organizational purposes, copy each `.cia` file you wish to encrypt / decrypt to the `/cias/` folder on your SD card
|
||||
{: .notice--info}
|
||||
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
1. Navigate to `[0:] SDCARD` -> `cias`
|
||||
1. Press (A) on the `.cia` file to select it, then select "CIA image options..."
|
||||
1. Select the option to perform the desired function:
|
||||
|
@ -14,7 +14,7 @@ title: "FAQ"
|
||||
## Pre-Installation FAQ
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>I am on the latest system version. Is my device hackable without any external hardware/prerequisites?</u></summary>
|
||||
<summary><u>I am on the latest system version. Is my console hackable without any external hardware/prerequisites?</u></summary>
|
||||
|
||||
It depends on your console model. At the moment, New 3DS / New 3DS XL / New 2DS XL is able to be modded on 11.17.0 without any prerequisites (e.g. eShop titles, physical items), while 3DS / 3DS XL / 2DS is not.
|
||||
|
||||
@ -22,16 +22,16 @@ It depends on your console model. At the moment, New 3DS / New 3DS XL / New 2DS
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What devices is this guide compatible with?</u></summary>
|
||||
<summary><u>What consoles is this guide compatible with?</u></summary>
|
||||
|
||||
The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. If your system version string displays as "0.0.0-0", then you may have a developer unit.
|
||||
The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL consoles. If your system version string displays as "0.0.0-0", then you may have a developer unit.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How risky is hacking my console?</u></summary>
|
||||
|
||||
Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
Bricks are now effectively impossible unless you are purposely trying to brick your console.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
@ -45,21 +45,21 @@ Yes! This guide will install a few useful homebrew applications, including [Univ
|
||||
{% capture compat %}
|
||||
<summary><u>Can I use this to play games from other regions?</u></summary>
|
||||
|
||||
Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Some games may need to make use of Luma's [locale emulation feature](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) in order to work properly on out-of-region devices.
|
||||
Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Some games may need to make use of Luma's [locale emulation feature](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) in order to work properly on out-of-region consoles.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose any features if I install CFW?</u></summary>
|
||||
|
||||
No. Devices with custom firmware can still play online and run physical cartridges as any other 3DS can.
|
||||
No. Consoles with custom firmware can still play online and run physical cartridges as any other 3DS can.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I keep my NNID?</u></summary>
|
||||
|
||||
Your NNID (if you have one) will not be affected by this guide. Devices with a region of KOR, CHN, or TWN do not have NNID functionality to begin with and are thus unaffected.
|
||||
Your NNID (if you have one) will not be affected by this guide. Consoles with a region of KOR, CHN, or TWN do not have NNID functionality to begin with and are thus unaffected.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
@ -106,7 +106,7 @@ Historically, the 3DS used to have userland homebrew access through older exploi
|
||||
{% capture compat %}
|
||||
<summary><u>Is it safe to update my 3DS to the latest version with CFW?</u></summary>
|
||||
|
||||
If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. There have been updates in the past that have resulted in Luma3DS crashing on boot, so it is a good idea to wait a couple of hours to ensure that the latest update will not temporarily render the device unusable until Luma3DS is updated. System updates can be performed the same way as they are on an unmodified 3DS: through System Settings, Safe Mode, or the update prompt when the update is automatically downloaded.
|
||||
If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. There have been updates in the past that have resulted in Luma3DS crashing on boot, so it is a good idea to wait a couple of hours to ensure that the latest update will not temporarily render the console unusable until Luma3DS is updated. System updates can be performed the same way as they are on an unmodified 3DS: through System Settings, Safe Mode, or the update prompt when the update is automatically downloaded.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
@ -127,7 +127,7 @@ Yes, system transfers can be performed through the official System Transfer func
|
||||
{% capture compat %}
|
||||
<summary><u>How do I change the system language of a Japanese 3DS?</u></summary>
|
||||
|
||||
The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Note that this is very likely to break the Nintendo eShop on your device, which means you will be unable to update your games whether they are in-region or out-of-region.
|
||||
The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Note that this is very likely to break the Nintendo eShop on your console, which means you will be unable to update your games whether they are in-region or out-of-region.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
@ -154,14 +154,14 @@ If the game is not from the same region as the console, you will need to [dump t
|
||||
{% capture compat %}
|
||||
<summary><u>Help! Something bad happened and my 3DS won't boot to HOME Menu...</u></summary>
|
||||
|
||||
Please look at the [troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware). **Uninstalling CFW when your device is in an unbootable state is not recommended, as it is very likely to lead to a brick**.
|
||||
Please look at the [troubleshooting guide](troubleshooting#boot-issues-on-consoles-with-custom-firmware). **Uninstalling CFW when your console is in an unbootable state is not recommended, as it is very likely to lead to a brick**.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## menuhax / A9LH / Gateway FAQ
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>I modded my device (x) years ago, so it already has some sort of homebrew. What should I do?</u></summary>
|
||||
<summary><u>I modded my console (x) years ago, so it already has some sort of homebrew. What should I do?</u></summary>
|
||||
|
||||
It is recommended that you upgrade your setup to a modern, boot9strap-based one. Follow the [Checking for CFW](checking-for-cfw) guide to see how to upgrade your setup.
|
||||
{% endcapture %}
|
||||
|
@ -6,7 +6,7 @@ title: "Finalizing Setup"
|
||||
|
||||
### Required Reading
|
||||
|
||||
The file `boot.firm` is what is launched by boot9strap itself after it finishes loading off of NAND. In this case, we are using Luma3DS by [LumaTeam](https://github.com/LumaTeam/) to patch the device, allowing it to run homebrew software.
|
||||
The file `boot.firm` is what is launched by boot9strap itself after it finishes loading off of NAND. In this case, we are using Luma3DS by [LumaTeam](https://github.com/LumaTeam/) to patch the console, allowing it to run homebrew software.
|
||||
|
||||
On this page, we will make critical system file backups and install the following homebrew programs:
|
||||
|
||||
@ -43,18 +43,18 @@ If your previous CFW setup was EmuNAND-based and you wish to move the contents o
|
||||
|
||||
In this section, you will copy the files necessary to follow the rest of the instructions on this page.
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Create a folder named `cias` on the root of your SD card if it does not already exist
|
||||
1. Copy all of the CIA files (`Anemone3DS.cia`, `Checkpoint.cia`, `FBI.cia`, `Homebrew_Launcher.cia`, and `Universal-Updater.cia`) to the `/cias/` folder on your SD card
|
||||
1. Create a folder named `3ds` on the root of your SD card if it does not already exist
|
||||
+ This folder stores homebrew applications and data; it is different from the `Nintendo 3DS` folder that the device automatically generates
|
||||
+ This folder stores homebrew applications and data; it is different from the `Nintendo 3DS` folder that the console automatically generates
|
||||
1. Copy `FBI.3dsx` to the `/3ds/` folder on your SD card
|
||||
1. Create a folder named `payloads` in the `luma` folder on your SD card if it does not already exist
|
||||
1. Copy `GodMode9.firm` from the GodMode9 `.zip` to the `/luma/payloads/` folder on your SD card
|
||||
1. Copy the `gm9` folder from the GodMode9 `.zip` to the root of your SD card
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
|
||||
The screenshots below indicate the minimum SD card layout that is required to follow this page. You may have extra files or folders on your SD card, depending on your previous setup or the method that you followed.
|
||||
|
||||
@ -69,14 +69,14 @@ The screenshots below indicate the minimum SD card layout that is required to fo
|
||||
|
||||
As an additional safety measure, we will perform an additional check for custom firmware. If custom firmware is not installed by this point for any reason, the next section may render your console unable to be hacked without external hardware.
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Hold the (Select) button
|
||||
1. Power on your device while still holding the (Select) button
|
||||
1. If the check was successful, your device should have booted into the Luma3DS configuration menu
|
||||
1. Power on your console while still holding the (Select) button
|
||||
1. If the check was successful, your console should have booted into the Luma3DS configuration menu
|
||||
1. Press (Start) to save and reboot
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
|
||||
If you do NOT boot into the Luma3DS configuration menu, custom firmware was not installed on your device. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
If you do NOT boot into the Luma3DS configuration menu, custom firmware was not installed on your console. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
{: .notice--danger}
|
||||
|
||||
|
||||
@ -88,7 +88,7 @@ In this section, you will update your system to the latest version, which is saf
|
||||
|
||||
#### Section IV - Homebrew Launcher
|
||||
|
||||
In this section, you will temporarily replace Download Play with Homebrew Launcher (which we need to launch FBI). Download Play will automatically go back to normal once you reboot your device.
|
||||
In this section, you will temporarily replace Download Play with Homebrew Launcher (which we need to launch FBI). Download Play will automatically go back to normal once you reboot your console.
|
||||
|
||||
{% include_relative include/launch-hbl-dlp.txt %}
|
||||
|
||||
@ -119,8 +119,8 @@ In this section, you will install several useful homebrew applications to HOME M
|
||||
|
||||
In this section, you will use a script to copy some of Luma3DS's files to internal memory so that they can be accessed, even without an SD card inserted.
|
||||
|
||||
1. Power off your device
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Power off your console
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
+ If you do not boot into GodMode9, ensure that `GodMode9.firm` is in `/luma/payloads/` and that `payloads` is correctly spelled
|
||||
1. If you are prompted to create an essential files backup, press (A) to do so, then press (A) to continue once it has completed
|
||||
1. If you are prompted to fix the RTC date&time, press (A) to do so, then set the date and time, then press (A) to continue
|
||||
@ -161,7 +161,7 @@ In this section, you will make backups of files that can be used to recover from
|
||||
+ If you see "Destination already exists", press (A) on "Overwrite file(s)"
|
||||
1. Press (A) to continue
|
||||
1. Press (Home) to bring up the action menu
|
||||
1. Select "Poweroff system" to power off your device
|
||||
1. Select "Poweroff system" to power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy `<date>_<serialnumber>_sysnand_##.bin`, `<date>_<serialnumber>_sysnand_##.bin.sha`, and `essential.exefs` from the `/gm9/out/` folder on your SD card to a safe location on your computer
|
||||
+ Copy these backups to multiple locations (such as online file storage, an external hard drive, etc.)
|
||||
@ -169,12 +169,12 @@ In this section, you will make backups of files that can be used to recover from
|
||||
1. Delete `<date>_<serialnumber>_sysnand_##.bin` and `<date>_<serialnumber>_sysnand_##.bin.sha` from the `/gm9/out/` folder on your SD card after copying it
|
||||
+ The other backup files are negligible in size and may be kept on your SD card for ease of access
|
||||
1. If you have it, copy the `/luma/backups/` folder on your SD card to a safe location on your computer
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
|
||||
___
|
||||
|
||||
You're done! Custom firmware is now fully configured on your device.
|
||||
You're done! Custom firmware is now fully configured on your console.
|
||||
{: .notice--success}
|
||||
|
||||
### Information and Notes
|
||||
|
@ -8,7 +8,7 @@ title: "Flashing ntrboot (3DS Multi System)"
|
||||
|
||||
Before proceeding, ensure you have read all of the information on [ntrboot](ntrboot).
|
||||
|
||||
This method requires temporary access to a second 3DS family device that is already running boot9strap. This does not require your flashcart to support either 3DS's version.
|
||||
This method requires temporary access to a second 3DS family console that is already running boot9strap. This does not require your flashcart to support either 3DS's version.
|
||||
|
||||
Note that in some rare circumstances, it may be possible for the flashing process to **brick** a counterfeit flashcart and render it permanently unusable. This is unlikely, but nevertheless, only original listed flashcarts are supported. To reduce the chance of receiving a counterfeit card, it is recommended that you use a reputable site to buy your flashcart (such as [NDS Card](http://www.nds-card.net/))
|
||||
{: .notice--danger}
|
||||
@ -16,9 +16,9 @@ Note that in some rare circumstances, it may be possible for the flashing proces
|
||||
### What You Need
|
||||
|
||||
* Your ntrboot compatible flashcart
|
||||
* Two 3DS family devices
|
||||
+ **The source 3DS**: the 3DS family device that is already running boot9strap
|
||||
+ **The target 3DS**: the device on stock firmware
|
||||
* Two 3DS family consoles
|
||||
+ **The source 3DS**: the 3DS family console that is already running boot9strap
|
||||
+ **The target 3DS**: the console on stock firmware
|
||||
* The v1.3 release of [boot9strap-ntr](https://github.com/SciresM/boot9strap/releases/download/1.3/boot9strap-1.3-ntr.zip) (direct download)
|
||||
* The latest release of [ntrboot_flasher](https://github.com/ntrteam/ntrboot_flasher/releases/latest) (`ntrboot_flasher.firm`)
|
||||
|
||||
|
@ -23,17 +23,17 @@ Note that in some rare circumstances, it may be possible for the flashing proces
|
||||
|
||||
#### Section I - Prep Work
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your flashcart's SD card into your computer
|
||||
1. Create a folder named `ntrboot` on the root of your flashcart's SD card
|
||||
1. Copy `boot9strap_ntr.firm` from the boot9strap ntr `.zip` to the `/ntrboot/` folder on your flashcart's SD card
|
||||
1. Copy `ntrboot_flasher_nds.nds` to your flashcart's SD card
|
||||
1. Reinsert your flashcart's SD card back into your flashcart
|
||||
1. Insert your ntrboot compatible DS / DSi flashcart into your device
|
||||
1. Insert your ntrboot compatible DS / DSi flashcart into your console
|
||||
|
||||
#### Section II - Flashing ntrboot
|
||||
|
||||
1. Launch `ntrboot_flasher_nds.nds` on your device using your flashcart
|
||||
1. Launch `ntrboot_flasher_nds.nds` on your console using your flashcart
|
||||
1. Press (A) to continue
|
||||
1. Use (Up) and (Down) to select your flashcart
|
||||
1. Press (A) to continue
|
||||
@ -45,7 +45,7 @@ Note that in some rare circumstances, it may be possible for the flashing proces
|
||||
1. Select "Inject FIRM" to install boot9strap to your flashcart
|
||||
1. Input the key combo given to confirm
|
||||
1. Press (A) to continue
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
|
||||
___
|
||||
|
||||
|
@ -16,9 +16,9 @@ Note that in some rare circumstances, it may be possible for the flashing proces
|
||||
### What You Need
|
||||
|
||||
* Your ntrboot compatible flashcart
|
||||
* Two devices
|
||||
* Two consoles
|
||||
+ **The source DSi**: the Nintendo DSi which is compatible with your flashcart
|
||||
+ **The target 3DS**: the 3DS family device on stock firmware
|
||||
+ **The target 3DS**: the 3DS family console on stock firmware
|
||||
* The latest release of [ds_ntrboot_flasher](https://github.com/ntrteam/ds_ntrboot_flasher/releases/latest) (`ds_ntrboot_flasher_dsi.nds`)
|
||||
|
||||
### Instructions
|
||||
|
@ -16,9 +16,9 @@ Note that in some rare circumstances, it may be possible for the flashing proces
|
||||
### What You Need
|
||||
|
||||
* Your ntrboot compatible flashcart
|
||||
* Two devices
|
||||
* Two consoles
|
||||
+ **The source NDS / NDSL**: the Nintendo DS or Nintendo DS Lite which is compatible with your flashcart
|
||||
+ **The target 3DS**: the 3DS family device on stock firmware
|
||||
+ **The target 3DS**: the 3DS family console on stock firmware
|
||||
* The v1.3 release of [boot9strap-ntr](https://github.com/SciresM/boot9strap/releases/download/1.3/boot9strap-1.3-ntr.zip) (direct download)
|
||||
* The latest release of [ntrboot_flasher_nds](https://github.com/jason0597/ntrboot_flasher_nds/releases/latest) (`ntrboot_flasher_nds.nds`)
|
||||
|
||||
|
@ -4,13 +4,13 @@ title: "Get Started"
|
||||
|
||||
{% include toc title="Table of Contents" %}
|
||||
|
||||
Before starting this guide, we will see if custom firmware is already installed and check the current system version of your device.
|
||||
Before starting this guide, we will see if custom firmware is already installed and check the current system version of your console.
|
||||
|
||||
#### Section I - CFW Check
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Hold the (Select) button
|
||||
1. Power on your device while still holding the (Select) button
|
||||
1. Power on your console while still holding the (Select) button
|
||||
1. If you do not see an unusual menu (e.g. "Luma3DS Configuration"), you may proceed to the next section
|
||||
|
||||
If you see an unusual menu, STOP - you already have custom firmware! Continue from [here](checking-for-cfw#what-to-do-next).
|
||||
@ -18,12 +18,12 @@ If you see an unusual menu, STOP - you already have custom firmware! Continue fr
|
||||
|
||||
#### Section II - System Version Check
|
||||
|
||||
1. Launch System Settings on your device
|
||||
1. Launch System Settings on your console
|
||||
1. Your system version will be displayed on the bottom right of the top screen (e.g. "Ver. 11.17.0-50U")
|
||||
|
||||
#### Section III - Select a Method
|
||||
|
||||
To find the correct method for your device, please enter the system version you found in Section II.
|
||||
To find the correct method for your console, please enter the system version you found in Section II.
|
||||
|
||||
{% capture noneSelected %}
|
||||
System model is required.
|
||||
|
@ -29,24 +29,24 @@ Some of the instructions below are only applicable to the latest version of GodM
|
||||
|
||||
### Instructions
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy `GodMode9.firm` from the GodMode9 `.zip` to the `/luma/payloads/` folder on your SD card
|
||||
1. Copy the `gm9` folder from the GodMode9 `.zip` to the root of your SD card
|
||||
1. Reinsert your SD card into your device
|
||||
1. Reinsert your SD card into your console
|
||||
|
||||
## Creating a NAND Backup
|
||||
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
{% include_relative include/nand-backup.txt %}
|
||||
|
||||
## Restoring a NAND Backup
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy `<date>_<serialnumber>_sysnand_##.bin` from your computer to the `/gm9/out/` folder on your SD card
|
||||
1. Reinsert your SD card into your device
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Reinsert your SD card into your console
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
1. Press (Home) to bring up the action menu
|
||||
1. Select "Scripts..."
|
||||
1. Select "GM9Megascript"
|
||||
@ -69,7 +69,7 @@ For organizational purposes, copy the `.cia` file you wish to inject to the `/ci
|
||||
Note that it is not possible to inject files into Health & Safety that are larger than it (including games and other large applications)
|
||||
{: .notice--info}
|
||||
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
1. Navigate to `[0:] SDCARD` -> `cias`
|
||||
1. Press (A) on your `.cia` to select it, then select "CIA image options...", then select "Mount image to drive"
|
||||
1. Press (A) on the `.app` file, then select "NCCH image options", then select "Inject to H&S"
|
||||
@ -82,7 +82,7 @@ Note that it is not possible to inject files into Health & Safety that are large
|
||||
This will only work if the Health & Safety injection was performed by GodMode9 (not Decrypt9 or Hourglass9).
|
||||
{: .notice--info}
|
||||
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
1. Press (Home) to bring up the action menu
|
||||
1. Select "More..."
|
||||
1. Select "Restore H&S"
|
||||
@ -94,12 +94,12 @@ This will only work if the Health & Safety injection was performed by GodMode9 (
|
||||
**Note that this will erase the contents of your SD card!**
|
||||
{: .notice--danger}
|
||||
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
{% include_relative include/format-sd-gm9.txt %}
|
||||
|
||||
## Removing an NNID without formatting your device
|
||||
## Removing an NNID without formatting your console
|
||||
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
1. Press (Home) to bring up the action menu
|
||||
1. Select "Scripts..."
|
||||
1. Select "GM9Megascript"
|
||||
@ -111,4 +111,4 @@ This will only work if the Health & Safety injection was performed by GodMode9 (
|
||||
1. Press (B) to return to the main menu
|
||||
1. Select "Exit"
|
||||
1. Press (A) to relock write permissions if prompted
|
||||
1. Press (Start) to reboot your device
|
||||
1. Press (Start) to reboot your console
|
||||
|
@ -36,7 +36,7 @@ Popular uses for custom firmware include:
|
||||
## What does this guide install?
|
||||
|
||||
This guide will:
|
||||
+ Install **boot9strap** and **Luma3DS custom firmware** on unmodified retail 3DS/2DS devices
|
||||
+ Install **boot9strap** and **Luma3DS custom firmware** on unmodified retail 3DS/2DS consoles
|
||||
+ Luma3DS will automatically remove the region lock and allow you to run unsigned software
|
||||
+ Install various pieces of homebrew software, such as a package installer, save file manager, and a homebrew app store
|
||||
+ Make critical system file backups that can help avoid bricks (and recover data in the event of one)
|
||||
|
@ -6,7 +6,7 @@ title: "Homebrew Launcher (freakyhax)"
|
||||
|
||||
{% capture technical_info %}
|
||||
<summary><em>Technical Details (optional)</em></summary>
|
||||
[freakyhax](https://plutooo.github.io/freakyhax/) is an exploit for the game Freakyforms Deluxe discovered and released by [plutooo](https://github.com/plutooo). It works on versions 9.0.0 through 11.17.0 on EUR, USA and JPN region devices.
|
||||
[freakyhax](https://plutooo.github.io/freakyhax/) is an exploit for the game Freakyforms Deluxe discovered and released by [plutooo](https://github.com/plutooo). It works on versions 9.0.0 through 11.17.0 on EUR, USA and JPN region consoles.
|
||||
|
||||
{% endcapture %}
|
||||
<details>{{ technical_info | markdownify }}</details>
|
||||
@ -26,24 +26,24 @@ This method requires a working 3DS camera.
|
||||
|
||||
#### Section I - Prep Work
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy all files and folders inside the `/build/<your console and region>/exploit/` folder from the freakyhax `.zip` to the root of your SD card
|
||||
+ The root of the SD card refers to the initial directory on your SD card where you can see the Nintendo 3DS folder, but are not inside of it
|
||||
1. Copy the otherapp payload for your model/region/version from `otherapps.zip` to the root of your SD card, then rename the payload to `otherapp.bin`
|
||||
+ Do not add the `.bin` extension if you do not already see it
|
||||
1. Copy `boot.firm` and `boot.3dsx` from the Luma3DS `.zip` to the root of your SD card
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
|
||||
#### Section II - freakyhax
|
||||
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
1. Launch Freakyforms Deluxe
|
||||
1. In the game menu, select `Play -> Camera -> Load a QR code`
|
||||
1. Select the QR code
|
||||
1. If the exploit was successful, your device will have booted into the Homebrew Launcher
|
||||
1. If the exploit was successful, your console will have booted into the Homebrew Launcher
|
||||
|
||||
#### Section III - Hardware Button Check
|
||||
|
||||
|
@ -26,25 +26,25 @@ This process will overwrite your Cubic Ninja save file, if you have one.
|
||||
|
||||
#### Section I - Prep Work
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy `Launcher.dat` from the folder appropriate for your console from the ninjhax2-dx `.zip` file to the root of your SD card
|
||||
+ The root of the SD card refers to the initial directory on your SD card where you can see the Nintendo 3DS folder, but are not inside of it
|
||||
1. Copy `boot.firm` and `boot.3dsx` from the Luma3DS `.zip` to the root of your SD card
|
||||
|
||||
#### Section II - ninjhax2-dx
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
1. Launch "Cubic Ninja" once and select "Create"
|
||||
+ If prompted, delete all data
|
||||
1. Select "QR Code"
|
||||
1. Select "Scan QR Code"
|
||||
1. On your PC, open the browser and go to [ninjhax2-dx website](https://zoogie.github.io/web/nh2dx/)
|
||||
1. Select your console's region and hardware
|
||||
1. On your device, scan the QR code
|
||||
1. On your console, scan the QR code
|
||||
+ If the game exits to the HOME Menu, then the exploit has installed correctly
|
||||
1. Launch "Cubic Ninja" again
|
||||
1. If the exploit was successful, your device will have booted into the Homebrew Launcher
|
||||
1. If the exploit was successful, your console will have booted into the Homebrew Launcher
|
||||
|
||||
#### Section III - Hardware Button Check
|
||||
|
||||
|
@ -18,9 +18,9 @@ This process will overwrite your Pokémon Picross save file, if you have one. If
|
||||
|
||||
### What You Need
|
||||
|
||||
+ The game "Pokémon Picross" installed on your device
|
||||
+ The game "Pokémon Picross" installed on your console
|
||||
+ If you have downloaded it before, you can [redownload it](https://en-americas-support.nintendo.com/app/answers/detail/a_id/607/~/how-to-download-or-redownload-content-in-nintendo-3ds-eshop)
|
||||
+ Your SD card must be inserted in your device to install Pokémon Picross
|
||||
+ Your SD card must be inserted in your console to install Pokémon Picross
|
||||
+ Your `movable.sed` file from completing [Seedminer](seedminer)
|
||||
+ The latest release of [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) (the Luma3DS `.zip` file)
|
||||
+ [otherapps.zip]({{ base_path }}/assets/otherapps.zip) (direct download)
|
||||
@ -32,7 +32,7 @@ This process will overwrite your Pokémon Picross save file, if you have one. If
|
||||
|
||||
In this section, you will copy some of the files that will be used to launch the Homebrew Launcher.
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy `boot.firm` and `boot.3dsx` from the Luma3DS `.zip` to the root of your SD card
|
||||
+ The root of the SD card refers to the initial directory on your SD card where you can see the Nintendo 3DS folder, but are not inside of it
|
||||
@ -49,7 +49,7 @@ In this section, you will copy some of the files that will be used to launch the
|
||||
|
||||
#### Section II - PicHaxx
|
||||
|
||||
In this section, you will create a hacked Pokémon Picross save file that, when loaded, will run the Homebrew Launcher on your device.
|
||||
In this section, you will create a hacked Pokémon Picross save file that, when loaded, will run the Homebrew Launcher on your console.
|
||||
|
||||
1. Open [the PicHaxx Injector website](https://3dstools.nhnarwhal.com/#/pichaxx) on your computer
|
||||
1. Select your `movable.sed` file
|
||||
@ -64,10 +64,10 @@ In this section, you will create a hacked Pokémon Picross save file that, when
|
||||
![]({{ "/images/screenshots/pichaxx-save-location.png" | absolute_url }})
|
||||
{: .notice--info}
|
||||
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
1. Launch "Pokémon Picross"
|
||||
1. If the exploit was successful, your device will have booted into the Homebrew Launcher
|
||||
1. If the exploit was successful, your console will have booted into the Homebrew Launcher
|
||||
+ If you get an error message, [follow this troubleshooting guide](troubleshooting#homebrew-launcher-pichaxx)
|
||||
|
||||
#### Section III - Hardware Button Check
|
||||
|
@ -15,9 +15,9 @@ This set of instructions does not support the Japanese version of SmileBASIC.
|
||||
{: .notice--info}
|
||||
|
||||
### What You Need
|
||||
+ The game "SmileBASIC" installed on your device
|
||||
+ The game "SmileBASIC" installed on your console
|
||||
+ If you have downloaded it before, you can [redownload it](https://en-americas-support.nintendo.com/app/answers/detail/a_id/607/~/how-to-download-or-redownload-content-in-nintendo-3ds-eshop)
|
||||
+ Your SD card must be inserted in your device to install SmileBASIC
|
||||
+ Your SD card must be inserted in your console to install SmileBASIC
|
||||
+ The latest release of [smilehax-IIe](https://github.com/zoogie/smilehax-IIe/releases/download/v1.0/Release_sh2e_v1.0.zip) (direct download)
|
||||
+ The latest release of [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) (the Luma3DS `.zip` file)
|
||||
+ [otherapps.zip]({{ base_path }}/assets/otherapps.zip) (direct download)
|
||||
@ -27,13 +27,13 @@ This set of instructions does not support the Japanese version of SmileBASIC.
|
||||
|
||||
#### Section I - Prep Work
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy `boot.firm` and `boot.3dsx` from the Luma3DS `.zip` to the root of your SD card
|
||||
+ The root of the SD card refers to the initial directory on your SD card where you can see the Nintendo 3DS folder, but are not inside of it
|
||||
1. Copy the otherapp payload for your model/region/version from `otherapps.zip` to the root of your SD card, then rename the payload to `otherapp.bin`
|
||||
+ Do not add the `.bin` extension if you do not already see it
|
||||
1. Transfer the `.wav` for your region from the Release_sh2e `.zip` to a device that can play `.wav` files, for example a phone
|
||||
1. Transfer the `.wav` for your region from the Release_sh2e `.zip` to a console that can play `.wav` files, for example a phone
|
||||
1. Copy the petitcom `.icn` for your region to the root of your SD card
|
||||
|
||||
#### Section II - smilehax
|
||||
@ -49,14 +49,14 @@ This set of instructions does not support the Japanese version of SmileBASIC.
|
||||
1. Select PMODEM141, then press "Select File"
|
||||
1. Select PMODEM141.PRG, then Press "OK", then "Yes" to execute it
|
||||
1. Select RECEIVE FILE SIMPLEX
|
||||
1. Prepare the device you use to play the `.wav` file
|
||||
1. Keep your console about a foot from the `.wav` file playing devices' speaker and use a reasonable (not loud) volume to play the`.wav`
|
||||
1. Prepare the console you use to play the `.wav` file
|
||||
1. Keep your console about a foot from the `.wav` file playing consoles' speaker and use a reasonable (not loud) volume to play the`.wav`
|
||||
1. Now select 300BPS, then play the `.wav` file
|
||||
1. When it finishes, Press "Yes", then press "OK"
|
||||
1. Press the START button
|
||||
1. Select the SH2E-xxx.TXT file, then press OK, then "Yes" to execute it
|
||||
+ If you get kicked back into menu, make sure you're using the latest version of SmileBASIC
|
||||
1. If the exploit was successful, your device will have booted into the Homebrew Launcher
|
||||
1. If the exploit was successful, your console will have booted into the Homebrew Launcher
|
||||
|
||||
#### Section III - Hardware Button Check
|
||||
|
||||
|
@ -16,9 +16,9 @@ This process will overwrite your Steel Diver: Sub Wars save file, if you have on
|
||||
|
||||
### What You Need
|
||||
|
||||
+ The game "Steel Diver: Sub Wars" installed on your device
|
||||
+ The game "Steel Diver: Sub Wars" installed on your console
|
||||
+ If you have downloaded it before, you can [redownload it](https://en-americas-support.nintendo.com/app/answers/detail/a_id/607/~/how-to-download-or-redownload-content-in-nintendo-3ds-eshop)
|
||||
+ Your SD card must be inserted in your device to install Steel Diver: Sub Wars
|
||||
+ Your SD card must be inserted in your console to install Steel Diver: Sub Wars
|
||||
+ Your `movable.sed` file from completing [Seedminer](seedminer)
|
||||
+ The latest release of [Steelhax](https://github.com/MechanicalDragon0687/vegaroxas.github.io/releases/download/1.0/steelhax-release.zip) (direct download)
|
||||
+ The latest release of [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) (the Luma3DS `.zip` file)
|
||||
@ -30,7 +30,7 @@ This process will overwrite your Steel Diver: Sub Wars save file, if you have on
|
||||
|
||||
In this section, you will copy some of the files that will be used to launch the Homebrew Launcher.
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy `boot.firm` and `boot.3dsx` from the Luma3DS `.zip` to the root of your SD card
|
||||
+ The root of the SD card refers to the initial directory on your SD card where you can see the Nintendo 3DS folder, but are not inside of it
|
||||
@ -38,18 +38,18 @@ In this section, you will copy some of the files that will be used to launch the
|
||||
1. Copy the otherapp payload for your model/region/version from `otherapps.zip` to `steelhax` folder on your SD card, then rename the payload to `payload.bin`
|
||||
+ Do not add the `.bin` extension if you do not already see it
|
||||
1. Copy `movable.sed` from your computer to the root of your SD card
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
|
||||
#### Section II - Steelminer
|
||||
|
||||
In this section, you will create a hacked Steel Diver: Sub Wars save file that, when used, will load the Homebrew Launcher on your device.
|
||||
In this section, you will create a hacked Steel Diver: Sub Wars save file that, when used, will load the Homebrew Launcher on your console.
|
||||
|
||||
1. Launch "Steel Diver: Sub Wars" once and select a Mii to initialize your save file
|
||||
+ Decline the game update when prompted
|
||||
+ If you have already updated the game, use the Data Management menu of the System Settings to delete the update
|
||||
1. Exit "Steel Diver: Sub Wars"
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Open [the SteelHax Save Tool website](https://3dstools.nhnarwhal.com/#/steelhax) on your computer
|
||||
1. Select your `movable.sed` file
|
||||
@ -62,10 +62,10 @@ In this section, you will create a hacked Steel Diver: Sub Wars save file that,
|
||||
+ **USA Region**: `000d7d00`
|
||||
1. Copy the newly downloaded `00000001.sav` file to the `data` folder on your SD card
|
||||
+ Overwrite the old save file when prompted
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
1. Launch "Steel Diver: Sub Wars"
|
||||
1. If the exploit was successful, your device will have booted into the Homebrew Launcher
|
||||
1. If the exploit was successful, your console will have booted into the Homebrew Launcher
|
||||
|
||||
#### Section III - Hardware Button Check
|
||||
|
||||
|
@ -16,7 +16,7 @@ For technical details on the exploits that you will be using on this page, see [
|
||||
|
||||
Super-skaterhax (when used to launch the Homebrew Launcher) is compatible with New models on version 11.16.0 in all regions, and 11.17.0 in the EUR, JPN and USA regions.
|
||||
|
||||
The instructions provided only apply to the New 3DS, New 3DS XL, and New 2DS XL. Please ensure that the device you are modding is a New 3DS, New 3DS XL, or New 2DS XL before continuing.
|
||||
The instructions provided only apply to the New 3DS, New 3DS XL, and New 2DS XL. Please ensure that the console you are modding is a New 3DS, New 3DS XL, or New 2DS XL before continuing.
|
||||
{: .notice--warning}
|
||||
|
||||
### What You Need
|
||||
@ -28,13 +28,13 @@ The instructions provided only apply to the New 3DS, New 3DS XL, and New 2DS XL.
|
||||
|
||||
In this section, you will copy the files needed to trigger both super-skaterhax and the Homebrew Launcher.
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy `boot.firm` and `boot.3dsx` from the Luma3DS `.zip` to the root of your SD card
|
||||
+ The root of the SD card refers to the initial directory on your SD card where you can see the Nintendo 3DS folder, but are not inside of it
|
||||
1. Copy everything inside the folder for your device's region (and also system version if the region is USA) in the super-skaterhax `.zip` to the root of your SD card
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Copy everything inside the folder for your console's region (and also system version if the region is USA) in the super-skaterhax `.zip` to the root of your SD card
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
|
||||
![]({{ "/images/screenshots/skater-root-layout.png" | absolute_url }})
|
||||
{: .notice--info}
|
||||
@ -44,12 +44,12 @@ In this section, you will copy the files needed to trigger both super-skaterhax
|
||||
|
||||
In this section, you will visit the browser exploit webpage, which will launch the Homebrew Launcher.
|
||||
|
||||
If you haven't already, make sure you have a working Internet connection set up on your device.
|
||||
If you haven't already, make sure you have a working Internet connection set up on your console.
|
||||
{: .notice--info}
|
||||
|
||||
1. On the HOME Menu, press the Left and Right shoulder buttons at the same time to open the camera
|
||||
+ If you are unable to open the camera, open the Internet Browser and manually type the URL instead (`https://zoogie.github.io/web/super/` for EUR/USA/JPN, `https://zoogie.github.io/web/korea` for KOR)
|
||||
1. Tap the QR code button and scan one of the following QR codes for your device's region [here](https://user-images.githubusercontent.com/28328903/226086338-585bfdac-0aac-44c0-b413-89206d2815d8.png)
|
||||
1. Tap the QR code button and scan one of the following QR codes for your console's region [here](https://user-images.githubusercontent.com/28328903/226086338-585bfdac-0aac-44c0-b413-89206d2815d8.png)
|
||||
+ If you get a security certificate warning, press (A) to allow the connection
|
||||
1. Press the (Select) button to open the bookmark tab
|
||||
+ If your (Select) button does not respond, tap the star icon on the bottom-left corner of the screen
|
||||
@ -63,11 +63,11 @@ If you haven't already, make sure you have a working Internet connection set up
|
||||
1. Press (Home) to return to the HOME Menu, then immediately press (A) to launch the browser again
|
||||
1. Select the "GO GO!" button on the top screen
|
||||
+ If any prompts appear, approve all of them
|
||||
+ If your device freezes on a yellow screen, hold the POWER button until it turns off, then retry this section
|
||||
+ If your device freezes on a red screen, hold the POWER button until it turns off, redo step 3 of Section II, then retry this section
|
||||
+ If your console freezes on a yellow screen, hold the POWER button until it turns off, then retry this section
|
||||
+ If your console freezes on a red screen, hold the POWER button until it turns off, redo step 3 of Section II, then retry this section
|
||||
+ If you get another error, try again up to 5 times, and if it still doesn't work, [follow this troubleshooting guide](troubleshooting#homebrew-launcher-super-skaterhax)
|
||||
1. If the exploit was successful, your device will have booted into the Homebrew Launcher
|
||||
1. Power off your device
|
||||
1. If the exploit was successful, your console will have booted into the Homebrew Launcher
|
||||
1. Power off your console
|
||||
|
||||
#### Section III - Hardware Button Check
|
||||
|
||||
|
@ -1,6 +1,6 @@
|
||||
**3DS firmware 11.17.0 was recently released**. Here's what you should know:
|
||||
|
||||
- If your device is running *Luma 10.2.1 or higher*, it is *100% safe* to update. You can check your Luma version by holding (Select) while booting your device.
|
||||
- If your device is on an older Luma version, you should [update Luma](checking-for-cfw) before you update your device to 11.17.0.
|
||||
- If your device does not yet have custom firmware, **do NOT update to the latest version**, as installation methods may be more difficult.
|
||||
- If your unmodified device is ALREADY on 11.17.0, this guide has been updated accordingly. Specifically, New3DS-family devices have a [free software method](homebrew-launcher-(super-skaterhax)), while Old3DS-family devices will need to use [alternate exploits](alternate-exploits) that rely on external hardware or software.
|
||||
- If your console is running *Luma 10.2.1 or higher*, it is *100% safe* to update. You can check your Luma version by holding (Select) while booting your console.
|
||||
- If your console is on an older Luma version, you should [update Luma](checking-for-cfw) before you update your console to 11.17.0.
|
||||
- If your console does not yet have custom firmware, **do NOT update to the latest version**, as installation methods may be more difficult.
|
||||
- If your unmodified console is ALREADY on 11.17.0, this guide has been updated accordingly. Specifically, New3DS-family consoles have a [free software method](homebrew-launcher-(super-skaterhax)), while Old3DS-family consoles will need to use [alternate exploits](alternate-exploits) that rely on external hardware or software.
|
||||
|
@ -1,6 +1,6 @@
|
||||
In this section, you will copy the files needed to trigger the BannerBomb3 exploit onto your device's SD card.
|
||||
In this section, you will copy the files needed to trigger the BannerBomb3 exploit onto your console's SD card.
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Open [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen) on your computer
|
||||
1. Upload your movable.sed using the “Choose File” option
|
||||
|
@ -1,10 +1,10 @@
|
||||
As an additional safety measure, we will perform an additional check for custom firmware. This is because using this method when custom firmware is already installed has a risk of bricking the console (rendering it unusable without recovery methods like [ntrboot](ntrboot)).
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Hold the (Select) button
|
||||
1. Power on your device while still holding the (Select) button
|
||||
1. Power on your console while still holding the (Select) button
|
||||
1. If the check was successful, you will boot to the HOME Menu and you may proceed with this guide
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
|
||||
If you see a configuration menu or the console immediately powers off, you already have CFW, and continuing with these instructions may BRICK your device! Follow [Checking for CFW](checking-for-cfw) to upgrade your existing CFW.
|
||||
If you see a configuration menu or the console immediately powers off, you already have CFW, and continuing with these instructions may BRICK your console! Follow [Checking for CFW](checking-for-cfw) to upgrade your existing CFW.
|
||||
{: .notice--danger}
|
||||
|
@ -1,5 +1,5 @@
|
||||
1. Your device should have booted into the Luma3DS configuration menu
|
||||
1. Your console should have booted into the Luma3DS configuration menu
|
||||
+ Luma3DS configuration menu are settings for the Luma3DS custom firmware. Many of these settings may be useful for customization or debugging
|
||||
+ For the purpose of this guide, **leave these options on the default settings** (do not check or uncheck anything)
|
||||
+ If your device shuts down when you try to power it on, ensure that you have copied `boot.firm` from the Luma3DS `.zip` to the root of your SD card
|
||||
+ If your console shuts down when you try to power it on, ensure that you have copied `boot.firm` from the Luma3DS `.zip` to the root of your SD card
|
||||
1. Press (Start) to save and reboot
|
||||
|
@ -1,7 +1,7 @@
|
||||
This section will reset your system configuration to its defaults. Installed games and their save data will not be affected. This is necessary to prevent known issues relating to extended memory mode and applets on some devices.
|
||||
This section will reset your system configuration to its defaults. Installed games and their save data will not be affected. This is necessary to prevent known issues relating to extended memory mode and applets on some consoles.
|
||||
|
||||
1. Power off your device
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Power off your console
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
1. Navigate to `[0:] SDCARD` -> `gm9`
|
||||
1. Press (X) on the CTRTransfer image `.bin` to delete it
|
||||
1. Press (A) to confirm
|
||||
@ -17,7 +17,7 @@ This section will reset your system configuration to its defaults. Installed gam
|
||||
1. Press (A) to unlock SysNAND (lvl2) writing, then input the key combo given
|
||||
1. Once the file has been deleted, press (A) to continue
|
||||
1. Press (A) to relock write permissions if prompted
|
||||
1. Press (Start) to reboot your device
|
||||
1. Your device will load into the initial setup menu
|
||||
1. Press (Start) to reboot your console
|
||||
1. Your console will load into the initial setup menu
|
||||
+ This is expected behaviour. You have not lost any of your game data
|
||||
1. Complete the initial setup menu by following the prompts on your device's screen
|
||||
1. Complete the initial setup menu by following the prompts on your console's screen
|
||||
|
@ -1,4 +1,4 @@
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
1. If you are prompted to create an essential files backup, press (A) to do so, then press (A) to continue once it is completed
|
||||
1. If you are prompted to fix the RTC date&time, press (A) to do so, then set the date and time, then press (A) to continue
|
||||
+ Note that, if you had to fix the RTC date and time, you will have to fix the time in the System Settings as well after this guide
|
||||
@ -23,7 +23,7 @@
|
||||
1. Press (B) to return to the main menu
|
||||
1. Select "Exit"
|
||||
1. Press (A) to relock write permissions if prompted
|
||||
1. Press (Start) to reboot your device
|
||||
1. Update your device by going to System Settings, then "Other Settings", then going all the way to the right and using "System Update"
|
||||
1. Press (Start) to reboot your console
|
||||
1. Update your console by going to System Settings, then "Other Settings", then going all the way to the right and using "System Update"
|
||||
+ Updates while using B9S + Luma (what you have) are safe
|
||||
+ If this gives you an error, set your DNS settings to "auto"
|
||||
|
@ -1,8 +1,8 @@
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Create a folder named `3ds` on the root of your SD card if it does not already exist
|
||||
1. Copy `GodMode9.firm` from the GodMode9 `.zip` to the `/luma/payloads/` folder on your SD card
|
||||
1. Copy the `gm9` folder from the GodMode9 `.zip` to the root of your SD card
|
||||
1. Copy the 11.15.0 CTRTransfer image `.bin` from the CTRTransfer `.zip` to the `/gm9/` folder on your SD card
|
||||
1. Copy `FBI.3dsx` to the `/3ds/` folder on your SD card
|
||||
1. Reinsert your SD card into your device
|
||||
1. Reinsert your SD card into your console
|
||||
|
@ -1,14 +1,14 @@
|
||||
In this section, you will enter Safe Mode (a feature available on all 3DS family devices) and navigate to a menu where unSAFE_MODE will be triggered, which will launch you into the boot9strap (custom firmware) installer.
|
||||
In this section, you will enter Safe Mode (a feature available on all 3DS family consoles) and navigate to a menu where unSAFE_MODE will be triggered, which will launch you into the boot9strap (custom firmware) installer.
|
||||
|
||||
1. With your device still powered off, hold the following buttons: (Left Shoulder) + (Right Shoulder) + (D-Pad Up) + (A), and while holding these buttons together, power on your device
|
||||
+ Keep holding the buttons until the device boots into Safe Mode (a "system update" menu)
|
||||
1. With your console still powered off, hold the following buttons: (Left Shoulder) + (Right Shoulder) + (D-Pad Up) + (A), and while holding these buttons together, power on your console
|
||||
+ Keep holding the buttons until the console boots into Safe Mode (a "system update" menu)
|
||||
1. Press "OK" to accept the update
|
||||
+ There is no update. This is part of the exploit
|
||||
1. Press "I accept" to accept the terms and conditions
|
||||
1. The update will eventually fail, with the error code `003-1099`. This is intended behaviour
|
||||
1. When asked "Would you like to configure Internet settings?", select "Yes"
|
||||
1. On the following menu, navigate to `Connection 1` -> `Change Settings` -> `Next Page (right arrow)` -> `Proxy Settings` -> `Detailed Setup` ([image](/images/screenshots/usm/safemode_highlighted.png))
|
||||
1. If the exploit was successful, your device will have booted into SafeB9SInstaller
|
||||
+ If your device instead freezes on a white screen, hold the POWER button until it turns off, then retry this section
|
||||
+ If your device instead freezes on a red screen, you are missing `usm.bin` from the root of your SD card
|
||||
1. If the exploit was successful, your console will have booted into SafeB9SInstaller
|
||||
+ If your console instead freezes on a white screen, hold the POWER button until it turns off, then retry this section
|
||||
+ If your console instead freezes on a red screen, you are missing `usm.bin` from the root of your SD card
|
||||
+ If you get a different error, [follow this troubleshooting guide](troubleshooting#installing-boot9strap-usm)
|
@ -22,8 +22,8 @@ In this section, you will copy the files necessary to temporarily replace DS Con
|
||||
+ The root of the SD card refers to the initial directory on your SD card where you can see the Nintendo 3DS folder, but are not inside of it
|
||||
1. Copy `boot.nds` (B9STool) from the release `.zip` to the root of your SD card
|
||||
1. Copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
|
||||
![]({{ "/images/screenshots/fredtool/fredtool-root-layout.png" | absolute_url }})
|
||||
{: .notice--info}
|
@ -2,9 +2,9 @@ In this section, you will restore DS Connection Settings to the way it was befor
|
||||
|
||||
1. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card
|
||||
1. Copy the `42383841.bin` file from the `clean` folder of the downloaded DSiWare archive (output_(name).zip) to the `Nintendo DSiWare` folder, replacing the existing one
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Launch System Settings on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
1. Launch System Settings on your console
|
||||
1. Navigate to `Data Management` -> `DSiWare` -> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
1. Select the "Nintendo DSi™" title
|
||||
1. Select "Copy", then select "OK"
|
||||
|
@ -1,11 +1,11 @@
|
||||
In this section, you will copy the hacked DS Connection Settings DSiWare to internal memory, which will temporarily replace it with Flipnote Studio.
|
||||
|
||||
1. Launch System Settings on your device
|
||||
1. Launch System Settings on your console
|
||||
1. Navigate to `Data Management` -> `DSiWare` -> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
1. Select the "Haxxxxxxxxx!" title
|
||||
+ If you are unable to select the "Haxxxxxxxxx" title, [follow this troubleshooting guide](troubleshooting#installing-boot9strap-fredtool)
|
||||
1. Select "Copy", then select "OK"
|
||||
1. Return to main menu of the System Settings
|
||||
1. Navigate to `Internet Settings` -> `Nintendo DS Connections`, then select "OK" ([image](/images/screenshots/fredtool/dsconnection.png))
|
||||
1. If the exploit was successful, your device will have loaded the JPN version of Flipnote Studio
|
||||
+ If your device does not load the JPN version of Flipnote Studio, [follow this troubleshooting guide](troubleshooting#installing-boot9strap-fredtool)
|
||||
1. If the exploit was successful, your console will have loaded the JPN version of Flipnote Studio
|
||||
+ If your console does not load the JPN version of Flipnote Studio, [follow this troubleshooting guide](troubleshooting#installing-boot9strap-fredtool)
|
@ -1,6 +1,6 @@
|
||||
### Next step: Choose an exploit
|
||||
|
||||
If the camera appeared in the previous section, Safe Mode is likely to be working on your device.
|
||||
If the camera appeared in the previous section, Safe Mode is likely to be working on your console.
|
||||
|
||||
If the camera appeared, continue to [Installing boot9strap (HBL-USM)](installing-boot9strap-(hbl-usm))
|
||||
{: .notice--primary}
|
||||
|
@ -1,6 +1,6 @@
|
||||
### Next step: Choose an exploit
|
||||
|
||||
If the camera appeared in the previous section, Safe Mode is likely to be working on your device.
|
||||
If the camera appeared in the previous section, Safe Mode is likely to be working on your console.
|
||||
|
||||
If the camera appeared, continue to [Installing boot9strap (HBL-USM)](installing-boot9strap-(hbl-usm))
|
||||
{: .notice--primary}
|
||||
|
@ -14,7 +14,7 @@ In this section, you will perform a series of very specific steps within Flipnot
|
||||
1. Tap the third box with the letter "A" in it
|
||||
1. Scroll left until reel "1/3" is selected
|
||||
1. Tap the fourth box with the letter "A" in it
|
||||
1. If the exploit was successful, your device will have loaded b9sTool
|
||||
1. If the exploit was successful, your console will have loaded b9sTool
|
||||
1. Using the D-Pad, move to "Install boot9strap"
|
||||
{%- if include.method == "dsinternet" %}
|
||||
+ If you miss this step, the system will exit to HOME Menu instead of installing boot9strap and you will need to open Nintendo DS Connections and start over from the beginning of this section
|
||||
@ -22,7 +22,7 @@ In this section, you will perform a series of very specific steps within Flipnot
|
||||
+ If you miss this step, the system will exit to HOME Menu instead of installing boot9strap and you will need to open DS Download Play and start over from the beginning of this section
|
||||
{%- endif %}
|
||||
1. Press (A), then press START and SELECT at the same time to begin the process
|
||||
1. Once completed and the bottom screen says "done.", exit b9sTool, then power off your device
|
||||
1. Once completed and the bottom screen says "done.", exit b9sTool, then power off your console
|
||||
+ You may have to force power off by holding the power button
|
||||
+ If your device shuts down when you try to power it on, ensure that you have copied `boot.firm` from the Luma3DS `.zip` to the root of your SD card
|
||||
+ If you see the Luma Configuration screen, power off your device and continue to the next section
|
||||
+ If your console shuts down when you try to power it on, ensure that you have copied `boot.firm` from the Luma3DS `.zip` to the root of your SD card
|
||||
+ If you see the Luma Configuration screen, power off your console and continue to the next section
|
||||
|
@ -1,12 +1,12 @@
|
||||
{%- if include.inline != "true" %}
|
||||
In this section, you will install custom firmware onto your device.
|
||||
In this section, you will install custom firmware onto your console.
|
||||
{%- endif %}
|
||||
|
||||
1. When prompted, input the key combo given on the top screen to install boot9strap
|
||||
+ If a step on the lower screen has red-colored text, and you are not prompted to input a key combo, [follow this troubleshooting guide](troubleshooting#issues-with-safeb9sinstaller)
|
||||
{%- if include.isbootfirm == "true" %}
|
||||
1. Once it is completed, force your device to power off by holding down the power button
|
||||
+ Your device will only boot to the SafeB9SInstaller screen until the next section is completed
|
||||
1. Once it is completed, force your console to power off by holding down the power button
|
||||
+ Your console will only boot to the SafeB9SInstaller screen until the next section is completed
|
||||
{%- else %}
|
||||
1. Once it is complete, press (A) to reboot your device
|
||||
1. Once it is complete, press (A) to reboot your console
|
||||
{%- endif %}
|
||||
|
@ -9,5 +9,5 @@
|
||||
1. Press (Home) to suspend Download Play
|
||||
1. Press the "Close" button on the bottom screen to close Download Play
|
||||
1. Re-launch the Download Play application
|
||||
1. Your device should load the Homebrew Launcher
|
||||
+ If your device is stuck on the loading splash screen, you are missing `boot.3dsx` from the root of your SD card
|
||||
1. Your console should load the Homebrew Launcher
|
||||
+ If your console is stuck on the loading splash screen, you are missing `boot.3dsx` from the root of your SD card
|
||||
|
@ -10,10 +10,10 @@
|
||||
1. Press (B) to return to the main menu
|
||||
1. Select "Exit"
|
||||
1. Press (A) to relock write permissions if prompted
|
||||
1. Hold (R) and press (Start) at the same time to power off your device
|
||||
1. Hold (R) and press (Start) at the same time to power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy `<date>_<serialnumber>_sysnand_##.bin` and `essential.exefs` from the `/gm9/out/` folder on your SD card to a safe location on your computer
|
||||
+ Make backups in multiple locations (such as online file storage)
|
||||
+ These backups will save you from a brick and/or help you recover files from the NAND image if anything goes wrong in the future
|
||||
1. Delete `<date>_<serialnumber>_sysnand_##.bin` and `<date>_<serialnumber>_sysnand_##.bin.sha` from the `/gm9/out/` folder on your SD card after copying it
|
||||
1. Reinsert your SD card into your device
|
||||
1. Reinsert your SD card into your console
|
||||
|
@ -11,7 +11,7 @@ In this section, you will enter the Homebrew Launcher (using custom firmware) so
|
||||
1. Press (B) to exit the Rosalina menu
|
||||
1. Press (Home), then close Download Play
|
||||
1. Relaunch the Download Play application
|
||||
1. Your device should load the Homebrew Launcher
|
||||
1. Your console should load the Homebrew Launcher
|
||||
1. Launch slotTool from the list of homebrew
|
||||
1. Select "RESTORE original wifi slots 1,2,3"
|
||||
1. Your device will then reboot
|
||||
1. Your console will then reboot
|
||||
|
@ -7,4 +7,4 @@ In this section, you will restore the Internet settings back to normal.
|
||||
1. Click OK, then click Save
|
||||
1. When prompted, click "Test" to perform the connection test
|
||||
+ The test should succeed
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
|
@ -1,6 +1,6 @@
|
||||
In this section, you will see whether your shoulder buttons are working on your device. This will determine which method you will follow on the next page.
|
||||
In this section, you will see whether your shoulder buttons are working on your console. This will determine which method you will follow on the next page.
|
||||
|
||||
1. Power on your device
|
||||
1. Power on your console
|
||||
1. Once you see the HOME Menu, press the (Left Shoulder) and (Right Shoulder) buttons at the same time
|
||||
+ The camera applet should appear
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
|
@ -1,7 +1,7 @@
|
||||
{% capture technical_info %}
|
||||
<summary><em>Technical Details (optional)</em></summary>
|
||||
|
||||
To install boot9strap on your device, we derive your device's unique encryption key. To accomplish this, we use a tool called Seedminer to calculate the data encryption key (movable.sed) for your device.
|
||||
To install boot9strap on your console, we derive your console's unique encryption key. To accomplish this, we use a tool called Seedminer to calculate the data encryption key (movable.sed) for your console.
|
||||
|
||||
For information on how Seedminer works, see [this presentation](https://zoogie.github.io/web/34⅕c3).
|
||||
|
||||
@ -13,7 +13,7 @@ This method uses a powerful graphics card to perform the calculations needed. A
|
||||
|
||||
### Section I - Prep Work
|
||||
|
||||
In this section, you will get the necessary details from your 3DS that are required to figure out your device's encryption key.
|
||||
In this section, you will get the necessary details from your 3DS that are required to figure out your console's encryption key.
|
||||
|
||||
{% capture console_state_info %}
|
||||
Before following this section:
|
||||
@ -22,7 +22,7 @@ Before following this section:
|
||||
{% endcapture %}
|
||||
<div class="notice--info">{{ console_state_info | markdownify }}</div>
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Navigate to the `Nintendo 3DS` folder on your SD card
|
||||
1. Copy the name of the 32-letter folder you see directly inside Nintendo 3DS
|
||||
@ -34,24 +34,24 @@ Before following this section:
|
||||
{: .notice--info}
|
||||
1. Paste your 32-letter folder name into [a document](/images/screenshots/seedminer/text-document.png) you can reference later
|
||||
+ This folder is known as your "ID0". Take note of this as this guide will refer to it as such later
|
||||
1. Power on your device
|
||||
1. Power on your console
|
||||
+ Your SD card does not need to be inserted at this point
|
||||
1. Go to your Friend List (the [orange Face Icon]({{ "/images/friend-list-icon.png" | absolute_url }}) in the top row of your HOME Menu)
|
||||
+ If you receive an error and are kicked out of the menu, you either must create a new Mii or your device cannot connect to Nintendo's servers (due to a ban or connection issues)
|
||||
+ If you receive an error and are kicked out of the menu, you either must create a new Mii or your console cannot connect to Nintendo's servers (due to a ban or connection issues)
|
||||
1. Find your Mii profile, then find the "Friend Code" field on the top screen
|
||||
|
||||
### Section II - Seedminer
|
||||
|
||||
In this section, you will use the Bruteforce Movable website to retrieve your device's encryption key in the form of `movable.sed`.
|
||||
In this section, you will use the Bruteforce Movable website to retrieve your console's encryption key in the form of `movable.sed`.
|
||||
|
||||
1. Open [Bruteforce Movable](https://seedminer.hacks.guide/) on your computer
|
||||
+ If the site isn't working, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask (in English) for someone there to assist you
|
||||
1. Enter your device's Friend Code (with no spaces or dashes) into the "Your friend code" field
|
||||
1. Paste your device's 32 character long folder name into the "Your ID0" field
|
||||
1. Enter your console's Friend Code (with no spaces or dashes) into the "Your friend code" field
|
||||
1. Paste your console's 32 character long folder name into the "Your ID0" field
|
||||
+ Do not attempt to enter the ID0 manually, as it is easy to make a mistake. Ensure the ID0 is entered correctly by copying and pasting it from where you saved it in the previous section
|
||||
1. Select "Go"
|
||||
+ If the site immediately goes to step 4, the website has already correctly processed your bruteforce request. You can download your `movable.sed` file and continue to the next section. You do not need to (re-)add the bot
|
||||
1. Use the ["Register Friend" button](/images/screenshots/seedminer/register-friend.png) on your device to add the bot's friend code as given by the website
|
||||
1. Use the ["Register Friend" button](/images/screenshots/seedminer/register-friend.png) on your console to add the bot's friend code as given by the website
|
||||
+ If prompted, the name that you give to the friend does not matter
|
||||
1. Wait for the site to update
|
||||
+ If it does not, wait a few minutes before refreshing the page once
|
||||
@ -62,4 +62,4 @@ In this section, you will use the Bruteforce Movable website to retrieve your de
|
||||
+ If you are still waiting after half an hour, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask (in English) for someone there to assist you
|
||||
+ If you get "We were unable to successfully complete your bruteforce request. :`(", follow the [respective troubleshooting on this page](troubleshooting#seedminer)
|
||||
+ Keep this file as you will need it in the upcoming page
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
|
@ -1,4 +1,4 @@
|
||||
1. Update your device by going to System Settings, then "Other Settings", then going all the way to the right and using "System Update"
|
||||
1. Update your console by going to System Settings, then "Other Settings", then going all the way to the right and using "System Update"
|
||||
{%- if include.cfw == "true" %}
|
||||
+ Updates while using B9S + Luma (what you have) are safe
|
||||
{%- endif %}
|
||||
|
@ -33,15 +33,15 @@ You should only be able to get to this page if you are running version 11.16.0.
|
||||
|
||||
In this section, you will trigger the BannerBomb3 exploit using the DSiWare Management menu and copy the resulting file dump to your computer so that you can use it on the next section.
|
||||
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Launch System Settings on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
1. Launch System Settings on your console
|
||||
1. Navigate to `Data Management` -> `DSiWare` -> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#installing-boot9strap-fredtool)
|
||||
+ Your console should show the BB3 multihax menu
|
||||
+ If this step causes your console to crash, [follow this troubleshooting guide](troubleshooting#installing-boot9strap-fredtool)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Dump DSiWare"
|
||||
+ Your device will automatically reboot
|
||||
1. Power off your device
|
||||
+ Your console will automatically reboot
|
||||
1. Power off your console
|
||||
|
||||
#### Section III - Prep Work
|
||||
|
||||
@ -57,7 +57,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
||||
|
||||
#### Section VI - Luma3DS Configuration
|
||||
|
||||
1. Press and hold (Select), and while holding (Select), power on your device
|
||||
1. 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 %}
|
||||
|
@ -45,7 +45,7 @@ You should only be able to get to this page if you are running version 11.17.0.
|
||||
|
||||
#### Section V - Luma3DS Configuration
|
||||
|
||||
1. Press and hold (Select), and while holding (Select), power on your device
|
||||
1. 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 %}
|
||||
|
@ -37,15 +37,15 @@ You should only be able to get to this page if you are running version 11.15.0 o
|
||||
|
||||
In this section, you will trigger the BannerBomb3 exploit using the DSiWare Management menu and copy the resulting file dump to your computer so that you can use it on the next section.
|
||||
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Launch System Settings on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
1. Launch System Settings on your console
|
||||
1. Navigate to `Data Management` -> `DSiWare` -> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#installing-boot9strap-fredtool)
|
||||
+ Your console should show the BB3 multihax menu
|
||||
+ If this step causes your console to crash, [follow this troubleshooting guide](troubleshooting#installing-boot9strap-fredtool)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Dump DSiWare"
|
||||
+ Your device will automatically reboot
|
||||
1. Power off your device
|
||||
+ Your console will automatically reboot
|
||||
1. Power off your console
|
||||
|
||||
#### Section III - Prep Work
|
||||
|
||||
@ -61,7 +61,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
||||
|
||||
#### Section VI - Luma3DS Configuration
|
||||
|
||||
1. Press and hold (Select), and while holding (Select), power on your device
|
||||
1. 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 %}
|
||||
|
@ -30,14 +30,14 @@ If you are unable to install one, follow [Bannerbomb3](bannerbomb3) instead.
|
||||
|
||||
#### Section II - Prep Work
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy `boot.firm` and `boot.3dsx` from the Luma3DS `.zip` to the root of your SD card
|
||||
1. Copy `boot.nds` (b9sTool) from the b9sTool release `.zip` to the root of your SD card
|
||||
1. Copy `Frogtool.3dsx` to the `/3ds/` folder on your SD card
|
||||
1. Copy `frogcert.bin` to the root of your SD card
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
|
||||
#### Section III - Patching DS Download Play
|
||||
|
||||
@ -47,7 +47,7 @@ If you are unable to install one, follow [Bannerbomb3](bannerbomb3) instead.
|
||||
1. Frogtool will automatically run and inject the JPN version of Flipnote Studio into your DS Download Play
|
||||
1. Once this operation has finished, read the screens and check if the process was successful
|
||||
1. Tap the touch screen, then select "BOOT patched DS Download Play"
|
||||
1. If the exploit was successful, your device will have loaded the JPN version of Flipnote Studio
|
||||
1. If the exploit was successful, your console will have loaded the JPN version of Flipnote Studio
|
||||
+ If you get stuck on a black screen, follow [this](https://wiki.hacks.guide/wiki/3DS:TWLFix#Homebrew_Launcher-0) page, then try again
|
||||
|
||||
#### Section IV - Flipnote Exploit
|
||||
@ -56,7 +56,7 @@ If you are unable to install one, follow [Bannerbomb3](bannerbomb3) instead.
|
||||
|
||||
#### Section VI - Luma3DS Configuration
|
||||
|
||||
1. Press and hold (Select), and while holding (Select), power on your device
|
||||
1. 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 %}
|
||||
@ -74,13 +74,13 @@ If you are unable to install one, follow [Bannerbomb3](bannerbomb3) instead.
|
||||
1. Press (B) to exit the Rosalina menu
|
||||
1. Press (Home), then close Download Play
|
||||
1. Relaunch the Download Play application
|
||||
1. Your device should load the Homebrew Launcher
|
||||
1. Your console should load the Homebrew Launcher
|
||||
1. Launch Frogtool from the list of homebrew
|
||||
1. Select the "RESTORE patched DS Download Play" option
|
||||
1. Once this operation has finished, read the screens and check if the process was successful
|
||||
+ If there are any errors or missing files, correct the problem and try again
|
||||
1. If the process was successful, tap the touch screen, then press START to exit
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
|
||||
___
|
||||
|
||||
|
@ -32,7 +32,7 @@ This will work on New 3DS, New 2DS, Old 3DS, and Old 2DS on *all* versions that
|
||||
* The latest version of [hardmod-b9s-installer](https://github.com/ihaveamac/hardmod-b9s-installer/releases/latest)
|
||||
+ Windows users can use the compiled `.exe`, while Mac and Linux users will need to have [Python 3](https://www.python.org/downloads/) installed to run the `.py`
|
||||
* The latest release of [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) (the Luma3DS `.zip` file that isn't source code)
|
||||
* The `.firm` corresponding to your device and version:
|
||||
* The `.firm` corresponding to your console and version:
|
||||
|
||||
| Version(s) | Kernel | Old 3DS or Old 2DS | New 3DS or New 2DS |
|
||||
|-|-|:-:|:-:|
|
||||
@ -74,28 +74,28 @@ This will work on New 3DS, New 2DS, Old 3DS, and Old 2DS on *all* versions that
|
||||
|
||||
In this section, you will download the necessary files for the hardmod and dump the NAND image in preparation to install custom firmware.
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy `boot.firm` and `boot.3dsx` from the Luma3DS `.zip` to the root of your SD card
|
||||
1. Copy the hardmod-b9s-installer folder from the hardmod-b9s-installer `.zip` to your computer
|
||||
1. Copy your downloaded `.firm` to the hardmod-b9s-installer folder on your computer
|
||||
1. Rename your downloaded `.firm` in the hardmod-b9s-installer folder on your computer to `current.firm`
|
||||
1. Copy `boot9strap.firm` and `boot9strap.firm.sha` from the boot9strap `.zip` to the hardmod-b9s-installer folder on your computer
|
||||
1. Reinsert your SD card into your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Use your hardmod to create a NAND backup
|
||||
1. 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 device to install custom firmware on it.
|
||||
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.
|
||||
|
||||
1. Run hardmod-b9s-installer
|
||||
+ Windows Users: Run `install-b9s.exe`
|
||||
+ Mac and Linux Users: Run `install-b9s.py`
|
||||
1. Flash your outputted `NAND-patched.bin` to your device with your hardmod
|
||||
1. Power off your device
|
||||
1. Flash your outputted `NAND-patched.bin` to your console with your hardmod
|
||||
1. Power off your console
|
||||
1. Disconnect your hardmod
|
||||
1. Press and hold (Select), and while holding (Select), power on your device
|
||||
1. 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 %}
|
||||
|
@ -31,18 +31,18 @@ If your (Right/Left Shoulder), (D-Pad Up) or (A) buttons do not work, join [Nint
|
||||
|
||||
#### Section I - Prep Work
|
||||
|
||||
In this section, you will copy the files needed to trigger the unSAFE_MODE exploit onto your device's SD card. Then, you will use Homebrew Launcher to launch slotTool, which will overwrite your Wi-Fi slots with hacked data. Your Wi-Fi connection settings will be temporarily overwritten while the exploit is active.
|
||||
In this section, you will copy the files needed to trigger the unSAFE_MODE exploit onto your console's SD card. Then, you will use Homebrew Launcher to launch slotTool, which will overwrite your Wi-Fi slots with hacked data. Your Wi-Fi connection settings will be temporarily overwritten while the exploit is active.
|
||||
|
||||
1. Insert your SD card into your computer
|
||||
1. Create a folder named `boot9strap` on the root of your SD card
|
||||
1. Copy `boot9strap.firm` and `boot9strap.firm.sha` from the RELEASE `.zip` to the `/boot9strap/` folder on your SD card
|
||||
1. Create a folder named `3ds` on the root of your SD card if it does not already exist
|
||||
+ This folder stores homebrew applications and data; it is different from the `Nintendo 3DS` folder that the device automatically generates
|
||||
+ This folder stores homebrew applications and data; it is different from the `Nintendo 3DS` folder that the console automatically generates
|
||||
1. Copy the `slotTool` folder from the RELEASE `.zip` to the `/3ds/` folder on your SD card
|
||||
1. Copy `usm.bin` from the RELEASE `.zip` to the root folder on your SD card
|
||||
1. Copy `SafeB9SInstaller.bin` from the SafeB9SInstaller `.zip` to the root of your SD card
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
1. Open the Homebrew Launcher through your method of choice (likely the Internet Browser)
|
||||
1. Launch slotTool from the list of homebrew
|
||||
+ If you get stuck on a red screen, forcefully power off the console by holding the power button for fifteen seconds, then retry this section
|
||||
|
@ -28,7 +28,7 @@ In order to follow these instructions, you will need the following:
|
||||
- A second 3DS with custom firmware (the **source 3DS**) that is the same region as the 3DS you are trying to modify (the **target 3DS**)
|
||||
- The consoles must be USA, JPN, or EUR region consoles
|
||||
- A physical or digital copy of Mario Kart 7 that is the same region as both consoles
|
||||
- An SD card for both devices
|
||||
- An SD card for both consoles
|
||||
|
||||
### What You Need
|
||||
|
||||
@ -91,9 +91,9 @@ In this section, you will use Download Play to transfer the exploit data from th
|
||||
1. Launch Mario Kart 7
|
||||
- Ensure that wireless connectivity is enabled
|
||||
1. Navigate to `Local Multiplayer`. A menu should pop up
|
||||
- If the screen freezes, hold the power button for fifteen seconds to force power off your device, then try again
|
||||
- If the screen freezes, hold the power button for fifteen seconds to force power off your console, then try again
|
||||
- If you have launched kartdlphax previously, the last selected settings will be loaded. If they are correct, select `Use settings` and skip the next 3 steps. If they are incorrect, select `Change settings` and proceed.
|
||||
1. Select your **target 3DS** device type (Old 3DS family or New 3DS family)
|
||||
1. Select your **target 3DS** console type (Old 3DS family or New 3DS family)
|
||||
1. Select the following exploit type depending on your system version:
|
||||
- 11.16.0: select `xPloitInjector (11.16)`
|
||||
- 11.17.0: select `xPloitInjector (11.17)`
|
||||
|
@ -10,7 +10,7 @@ To use the [magnet](https://wikipedia.org/wiki/Magnet_URI_scheme) links on this
|
||||
|
||||
### What You Need
|
||||
|
||||
* A magnet that triggers the sleep mode of your device (if using a folding style device)
|
||||
* A magnet that triggers the sleep mode of your console (if using a folding style console)
|
||||
* Your ntrboot flashed flashcart
|
||||
* The latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip) (direct download)
|
||||
* The latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip) (direct download)
|
||||
@ -20,7 +20,7 @@ To use the [magnet](https://wikipedia.org/wiki/Magnet_URI_scheme) links on this
|
||||
|
||||
#### Section I - Prep Work
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your console's SD card into your computer
|
||||
+ This is the SD card from your 3DS, *not* the SD card from your flashcart
|
||||
1. Copy `SafeB9SInstaller.firm` from the SafeB9SInstaller `.zip` to the root of your SD card and rename it to `boot.firm`
|
||||
@ -33,20 +33,20 @@ To use the [magnet](https://wikipedia.org/wiki/Magnet_URI_scheme) links on this
|
||||
{: .notice--info}
|
||||
|
||||
1. Reinsert your SD card into your 3DS
|
||||
1. Power on your device
|
||||
1. Power on your console
|
||||
|
||||
#### Section II - ntrboot
|
||||
|
||||
1. Use the magnet to find the spot on your device where the sleep sensor is triggered
|
||||
1. Use the magnet to find the spot on your console where the sleep sensor is triggered
|
||||
+ This step is not needed on the old 2DS (which has a sleep mode switch)
|
||||
1. Power off your device
|
||||
1. Insert your flashcart into your device
|
||||
1. Place the magnet on your device to trigger the sleep sensor
|
||||
1. Power off your console
|
||||
1. Insert your flashcart into your console
|
||||
1. Place the magnet on your console to trigger the sleep sensor
|
||||
+ On old 2DS, you should instead enable the sleep mode switch
|
||||
1. Hold (Start) + (Select) + (X) + (Power) for several seconds, then release the buttons
|
||||
+ It may take a few attempts to get this to work because the positioning is awkward
|
||||
1. If the exploit was successful, you will have booted into SafeB9SInstaller
|
||||
1. Remove the magnet from your device
|
||||
1. Remove the magnet from your console
|
||||
+ On old 2DS, you should instead disable the sleep mode switch
|
||||
|
||||
#### Section III - Installing boot9strap
|
||||
@ -58,8 +58,8 @@ To use the [magnet](https://wikipedia.org/wiki/Magnet_URI_scheme) links on this
|
||||
1. Insert your SD card into your computer
|
||||
1. Delete `boot.firm` from the root of your SD card
|
||||
1. Copy `boot.firm` from the Luma3DS `.zip` to the root of your SD card
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
{%- include_relative include/configure-luma3ds.txt %}
|
||||
|
||||
{% include_relative include/luma3ds-installed-note.txt %}
|
||||
@ -116,15 +116,15 @@ Do not follow this section until you have completed the rest of the instructions
|
||||
|
||||
##### Instructions
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
+ This is the SD card from your 3DS, *not* the SD card from your flashcart
|
||||
1. Create a folder named `ntrboot` on the root of your SD card
|
||||
1. Copy the `.bin` file from your flashrom backup `.zip` to the `/ntrboot/` folder on the root of your SD card
|
||||
1. Create a folder named `payloads` in the `luma` folder on your SD card
|
||||
1. Copy `ntrboot_flasher.firm` to the `/luma/payloads/` folder on your SD card
|
||||
1. Reinsert your SD card into your device
|
||||
1. Insert your ntrboot compatible DS / DSi flashcart into your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Insert your ntrboot compatible DS / DSi flashcart into your console
|
||||
1. Launch ntrboot_flasher by holding (Start) during boot
|
||||
1. Read the red screen warning
|
||||
1. Press (A) to continue
|
||||
@ -134,4 +134,4 @@ Do not follow this section until you have completed the rest of the instructions
|
||||
1. Press (A) to proceed
|
||||
1. Wait until the process is completed
|
||||
1. Press (A) to return to the main menu
|
||||
1. Press (B) to power off your device
|
||||
1. Press (B) to power off your console
|
||||
|
@ -14,9 +14,9 @@ For technical details on the exploit that you will be using on this page, see [h
|
||||
|
||||
### Compatibility Notes
|
||||
|
||||
safecerthax is compatible with all Old 3DS and Old 2DS devices in all regions on system versions 1.0.0 through 11.14.0.
|
||||
safecerthax is compatible with all Old 3DS and Old 2DS consoles in all regions on system versions 1.0.0 through 11.14.0.
|
||||
|
||||
This exploit will not work on the New 3DS, New 3DS XL, or New 2DS XL. Please ensure that the device you are modding is an Old 3DS, Old 3DS XL, or Old 2DS before continuing.
|
||||
This exploit will not work on the New 3DS, New 3DS XL, or New 2DS XL. Please ensure that the console you are modding is an Old 3DS, Old 3DS XL, or Old 2DS before continuing.
|
||||
{: .notice--info}
|
||||
|
||||
### What You Need
|
||||
@ -44,29 +44,29 @@ In this section, you will copy the files needed to trigger the safecerthax explo
|
||||
1. Create a folder named `boot9strap` on the root of your SD card
|
||||
1. Copy `boot9strap.firm` and `boot9strap.firm.sha` from the boot9strap `.zip` to the `/boot9strap/` folder on your SD card
|
||||
1. Copy `SafeB9SInstaller.bin` from the SafeB9SInstaller `.zip` to the root of your SD card
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
|
||||
#### Section III - safecerthax proxy
|
||||
|
||||
In this section, you will change your Internet connection settings to use a proxy network designed to exploit the System Update feature of your device.
|
||||
In this section, you will change your Internet connection settings to use a proxy network designed to exploit the System Update feature of your console.
|
||||
|
||||
{% include_relative include/addproxy.txt %}
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
|
||||
#### Section IV - safecerthax
|
||||
|
||||
In this section, you will enter Safe Mode (a feature available on all 3DS family devices) where safecerthax will be triggered, which will launch you into the boot9strap (custom firmware) installer.
|
||||
In this section, you will enter Safe Mode (a feature available on all 3DS family consoles) where safecerthax will be triggered, which will launch you into the boot9strap (custom firmware) installer.
|
||||
|
||||
1. With your device still powered off, hold the following buttons: (Left Shoulder) + (Right Shoulder) + (D-Pad Up) + (A), and while holding these buttons together, power on your device
|
||||
+ Keep holding the buttons until the device boots into Safe Mode (a "system update" menu)
|
||||
1. With your console still powered off, hold the following buttons: (Left Shoulder) + (Right Shoulder) + (D-Pad Up) + (A), and while holding these buttons together, power on your console
|
||||
+ Keep holding the buttons until the console boots into Safe Mode (a "system update" menu)
|
||||
1. Press "OK" to accept the update
|
||||
+ There is no update. This is part of the exploit
|
||||
1. Press "I accept" to accept the terms and conditions
|
||||
1. The update will eventually fail, with the error code `003-1099`. This is intended behaviour
|
||||
1. Press "OK" to close the error message
|
||||
1. If the exploit was successful, you will have booted into SafeB9SInstaller
|
||||
+ If the device freezes or crashes, force power off the device, then retry this section
|
||||
+ If the console freezes or crashes, force power off the console, then retry this section
|
||||
|
||||
#### Section V - Installing boot9strap
|
||||
|
||||
|
@ -18,7 +18,7 @@ For technical details on the exploits that you will be using on this page, see [
|
||||
Soundhax (when combined with universal-otherapp) is compatible with versions 1.0.0 through 11.3.0 in all regions.
|
||||
|
||||
### What You Need
|
||||
* The latest release of [Soundhax](http://soundhax.com) *(for your region, device, and version)*
|
||||
* The latest release of [Soundhax](http://soundhax.com) *(for your region, console, and version)*
|
||||
+ If Soundhax appears in your browser as an unplayable video, press Ctrl+S or Cmd+S to save it to your computer
|
||||
* The latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip) (direct download)
|
||||
* The latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip) (direct download)
|
||||
@ -31,7 +31,7 @@ Soundhax (when combined with universal-otherapp) is compatible with versions 1.0
|
||||
|
||||
In this section, you will copy the files needed to trigger both Soundhax and universal-otherapp.
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy the Soundhax `.m4a` to the root of your SD card
|
||||
+ The root of the SD card refers to the initial directory on your SD card where you can see the Nintendo 3DS folder, but are not inside of it
|
||||
@ -40,8 +40,8 @@ In this section, you will copy the files needed to trigger both Soundhax and uni
|
||||
1. Create a folder named `boot9strap` on the root of your SD card
|
||||
1. Copy `boot9strap.firm` and `boot9strap.firm.sha` from the boot9strap `.zip` to the `/boot9strap/` folder on your SD card
|
||||
1. Copy `SafeB9SInstaller.bin` from the SafeB9SInstaller `.zip` to the root of your SD card
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
|
||||
![]({{ "/images/screenshots/uosoundhax-root-layout.png" | absolute_url }})
|
||||
{: .notice--info}
|
||||
@ -53,8 +53,8 @@ In this section, you will copy the files needed to trigger both Soundhax and uni
|
||||
|
||||
In this section, you will launch Soundhax through the Nintendo 3DS Sound app, which will use universal-otherapp to launch the boot9strap (custom firmware) installer.
|
||||
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
1. Launch Nintendo 3DS Sound
|
||||
|
||||
![]({{ "/images/screenshots/soundhax-welcome.png" | absolute_url }})
|
||||
|
@ -23,7 +23,7 @@ For technical details on the exploits that you will be using on this page, see [
|
||||
|
||||
SSLoth allows users on version 11.13.0 and below to bypass the browser version check, allowing the use of new-browserhax or old-browserhax (compatible with versions 11.4.0 through 11.13.0 in all regions), which can then be used in conjunction with universal-otherapp.
|
||||
|
||||
If you have updated your device to your current version using a cartridge, you will not be able to bypass the browser version check. If this is the case, stay on your current firmware and ask [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for help.
|
||||
If you have updated your console to your current version using a cartridge, you will not be able to bypass the browser version check. If this is the case, stay on your current firmware and ask [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for help.
|
||||
{: .notice--warning}
|
||||
|
||||
### What You Need
|
||||
@ -37,7 +37,7 @@ If you have updated your device to your current version using a cartridge, you w
|
||||
|
||||
In this section, you will copy the files needed to trigger both browserhax and universal-otherapp.
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy `otherapp.bin` to the root of your SD card and rename it to `arm11code.bin`
|
||||
+ The root of the SD card refers to the initial directory on your SD card where you can see the Nintendo 3DS folder, but are not inside of it
|
||||
@ -46,8 +46,8 @@ In this section, you will copy the files needed to trigger both browserhax and u
|
||||
1. Create a folder named `boot9strap` on the root of your SD card
|
||||
1. Copy `boot9strap.firm` and `boot9strap.firm.sha` from the boot9strap `.zip` to the `/boot9strap/` folder on your SD card
|
||||
1. Copy `SafeB9SInstaller.bin` from the SafeB9SInstaller `.zip` to the root of your SD card
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
|
||||
#### Section II - SSLoth
|
||||
|
||||
|
@ -38,7 +38,7 @@ If your (Right/Left Shoulder), (D-Pad Up), or (A) buttons do not work, you will
|
||||
|
||||
#### Section I - Prep Work
|
||||
|
||||
In this section, you will copy the files needed to trigger the unSAFE_MODE exploit onto your device's SD card.
|
||||
In this section, you will copy the files needed to trigger the unSAFE_MODE exploit onto your console's SD card.
|
||||
|
||||
1. Your SD card should be inserted in your computer
|
||||
1. Copy `usm.bin` to the root of your SD card
|
||||
@ -58,22 +58,22 @@ In this section, you will copy the files needed to trigger the unSAFE_MODE explo
|
||||
|
||||
In this section, you will trigger the BannerBomb3 exploit using the DSiWare Management menu, which can be used to overwrite your Wi-Fi slots with hacked data. Your Wi-Fi connection settings will be temporarily overwritten while the exploit is active.
|
||||
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Launch System Settings on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
1. Launch System Settings on your console
|
||||
1. Navigate to `Data Management` -> `DSiWare` -> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ Your console should show the BB3 multihax menu
|
||||
+ If the BB3 multihax menu doesn't open, [follow this troubleshooting guide](troubleshooting#bannerbomb3)
|
||||
+ If the BB3 multihax menu says "cfw installed already", you already have custom firmware and should continue from [here](checking-for-cfw)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Install unSAFE_MODE"
|
||||
+ Your device will automatically power off
|
||||
1. Power on your device
|
||||
1. Launch System Settings on your device
|
||||
+ Your console will automatically power off
|
||||
1. Power on your console
|
||||
1. Launch System Settings on your console
|
||||
1. Navigate to `Internet Settings` -> `Connection Settings`
|
||||
1. Ensure that all three connections are named "Haaaaaaaxxxxxxxxx..."
|
||||
+ Do NOT change these settings!
|
||||
+ If all three connections are NOT all named "Haaaaaaaxxxxxxxxx...", STOP! Something went wrong in this section and MUST be fixed before you can continue
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
|
||||
#### Section III - unSAFE_MODE
|
||||
|
||||
@ -90,11 +90,11 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
||||
|
||||
In this section, you will trigger the BannerBomb3 exploit a second time so that you can restore the Wi-Fi connection slots that were overwritten in Section II.
|
||||
|
||||
1. Launch System Settings on your device
|
||||
1. Launch System Settings on your console
|
||||
1. Navigate to `Data Management` -> `DSiWare` -> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Uninstall unSAFE_MODE"
|
||||
+ Your device will automatically reboot
|
||||
1. Power off your device
|
||||
+ Your console will automatically reboot
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card
|
||||
1. Delete `F00D43D5.bin` from your Nintendo DSiWare folder and from your computer. This file will not be needed anymore
|
||||
|
@ -23,7 +23,7 @@ Each section is collapsed by default. Click or tap on the name of the section to
|
||||
![]({{ "/images/screenshots/onboarding/compatible.png" | absolute_url }})
|
||||
{: .notice--info}
|
||||
|
||||
This guide works with every retail device in the Nintendo 3DS family of consoles (including the 3DS, 3DS XL/LL, 2DS, New 3DS, New 3DS XL/LL, and New 2DS XL/LL, regardless of region or firmware.
|
||||
This guide works with every retail console in the Nintendo 3DS family of consoles (including the 3DS, 3DS XL/LL, 2DS, New 3DS, New 3DS XL/LL, and New 2DS XL/LL, regardless of region or firmware.
|
||||
{% endcapture %}
|
||||
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
@ -59,9 +59,9 @@ If you want, you can check your SD card for errors before following this guide u
|
||||
{% capture compat %}
|
||||
<summary><strong>Potential risks</strong></summary>
|
||||
|
||||
By modding your device, you subject it to the remote (but non-zero) possibility of the device being banned from online play or bricked (rendered non-functional). ___Incorrect file placement will NOT brick your device___, but purposely skipping instructions might. Similarly, the last ban wave occurred over five years ago, but there is no guarantee that another one will not occur in the future.
|
||||
By modding your console, you subject it to the remote (but non-zero) possibility of the console being banned from online play or bricked (rendered non-functional). ___Incorrect file placement will NOT brick your console___, but purposely skipping instructions might. Similarly, the last ban wave occurred over five years ago, but there is no guarantee that another one will not occur in the future.
|
||||
|
||||
In short: Modding your device is safe, but it's ___your responsibility___ if something goes wrong.
|
||||
In short: Modding your console is safe, but it's ___your responsibility___ if something goes wrong.
|
||||
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
@ -23,18 +23,18 @@ You MUST have already installed Luma3DS and boot9strap to use this.
|
||||
|
||||
#### Section I - Prep Work
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy `GodMode9.firm` from the GodMode9 `.zip` to the `/luma/payloads/` folder on your SD card
|
||||
1. Copy the `gm9` folder from the GodMode9 `.zip` to the root of your SD card
|
||||
1. Reinsert your SD card into your device
|
||||
1. Reinsert your SD card into your console
|
||||
|
||||
#### Section II - Backup SysNAND DSiWare Saves
|
||||
|
||||
If you do not have any DSiWare games or saves that you care about, skip this section.
|
||||
{: .notice--info}
|
||||
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
1. If you are prompted to create an essential files backup, press (A) to do so, then press (A) to continue once it is completed
|
||||
1. If you are prompted to fix the RTC date&time, press (A) to do so, then set the date and time, then press (A) to continue
|
||||
+ Note that, if you had to fix the RTC date and time, you will have to fix the time in the System Settings as well after this guide
|
||||
@ -60,18 +60,18 @@ To identify a `<TitleID>.gbavc.sav` file's Title ID, you can get a listing of al
|
||||
1. Do the following process for each GBA VC game that you want to back up the save for:
|
||||
+ Launch the GBA VC game
|
||||
+ Exit the GBA VC game
|
||||
+ Boot your device while holding (Start) to launch the Luma3DS chainloader menu
|
||||
+ Boot your console while holding (Start) to launch the Luma3DS chainloader menu
|
||||
+ Launch GodMode9 by pressing (A)
|
||||
+ Navigate to `[S:] SYSNAND VIRTUAL`
|
||||
+ Press (A) on `agbsave.bin` to select it
|
||||
+ Select "AGBSAVE options..."
|
||||
+ Select "Dump GBA VC save"
|
||||
+ Press (A) to continue
|
||||
+ Press (Start) to reboot your device
|
||||
+ Press (Start) to reboot your console
|
||||
|
||||
#### Section IV - Copy EmuNAND to SysNAND
|
||||
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
1. Navigate to `[E:] EMUNAND VIRTUAL`
|
||||
1. Press (A) on `nand.bin` to select it, then select "NAND image options...", then select "Restore SysNAND (safe)"
|
||||
1. Press (A) to unlock SysNAND overwriting, then input the key combo given
|
||||
@ -107,12 +107,12 @@ If you did not backup GBA VC Saves earlier, skip this section.
|
||||
To identify a `<TitleID>.gbavc.sav` file's Title ID, you can get a listing of all games on the system and their corresponding Title IDs by holding (R) and pressing (A) on the GodeMode9 main menu, then selecting "Search for titles".
|
||||
{: .notice--info}
|
||||
|
||||
1. Hold (R) and press (Start) at the same time to power off your device
|
||||
1. Power on your device into SysNAND
|
||||
1. Hold (R) and press (Start) at the same time to power off your console
|
||||
1. Power on your console into SysNAND
|
||||
1. Do the following process for each GBA VC game that you want to restore the save for:
|
||||
+ Launch the GBA VC game
|
||||
+ Exit the GBA VC game
|
||||
+ Boot your device while holding (Start) to launch the Luma3DS chainloader menu
|
||||
+ Boot your console while holding (Start) to launch the Luma3DS chainloader menu
|
||||
+ Launch GodMode9 by pressing (A)
|
||||
+ Navigate to `[0:] SDCARD` -> `gm9`
|
||||
+ Press (Y) on the `<TitleID>.gbavc.sav` file you wish to restore to copy it
|
||||
@ -122,25 +122,25 @@ To identify a `<TitleID>.gbavc.sav` file's Title ID, you can get a listing of al
|
||||
+ Select "AGBSAVE options..."
|
||||
+ Select "Inject GBA VC save"
|
||||
+ Press (A) to continue
|
||||
+ Press (Start) to reboot your device
|
||||
+ Press (Start) to reboot your console
|
||||
+ Launch the GBA VC game
|
||||
+ Exit the GBA VC game
|
||||
|
||||
#### Section VII - Backup SysNAND
|
||||
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
{% include_relative include/nand-backup.txt -%}
|
||||
1. **Backup every file on your SD card to a folder on your computer; all files will be deleted in the following steps**
|
||||
|
||||
#### Section VIII - Format SD card
|
||||
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
{% include_relative include/format-sd-gm9.txt -%}
|
||||
1. Hold (R) and press (B) at the same time to eject your SD card
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy all your files back to your SD card
|
||||
+ Ensure you replace the `boot.firm` file on your SD card with the one from your backup
|
||||
1. Reinsert your SD card into your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Press (A) to remount your SD card
|
||||
1. Press (Start) to reboot
|
||||
|
||||
|
@ -11,7 +11,7 @@ If your flashcart comes pre-flashed with ntrboot (or you have already flashed nt
|
||||
|
||||
Installing boot9strap with ntrboot requires a compatible NDS / DSi flashcart to flash ntrboot to. Note that some of these flashcarts are sold pre-flashed with ntrboot.
|
||||
|
||||
While the ntrboot exploit works independently of the system version, the ntrboot flasher (which installs the exploit to the cart) is not. This means that, depending on the versions and devices supported by your flashcart, only certain methods may be available to you.
|
||||
While the ntrboot exploit works independently of the system version, the ntrboot flasher (which installs the exploit to the cart) is not. This means that, depending on the versions and consoles supported by your flashcart, only certain methods may be available to you.
|
||||
|
||||
Note that carts with a "Time Bomb" will no longer be able to launch `.nds` files when they detect that the system clock has passed a date determined by the flashcart firmware. One method to bypass this is to set the system clock to an earlier date.
|
||||
|
||||
@ -37,13 +37,13 @@ Note that carts with a "Time Bomb" will no longer be able to launch `.nds` files
|
||||
![]({{ "/images/screenshots/ntrboot-flashcarts.png" | absolute_url }})
|
||||
{: .notice--info}
|
||||
|
||||
Ensure your flashcart is able to launch `.nds` files on your device before beginning. Some flashcarts may require firmware or "kernel" files to be copied to the flashcart SD card. Consult your specific flashcart's instructions for more information.
|
||||
Ensure your flashcart is able to launch `.nds` files on your console before beginning. Some flashcarts may require firmware or "kernel" files to be copied to the flashcart SD card. Consult your specific flashcart's instructions for more information.
|
||||
|
||||
Note that specific methods may have additional compatibility information.
|
||||
|
||||
The usage of this exploit, regardless of the flashing method, requires access to a small magnet if the target device is of a folding style (any 3DS family system that is not the old 2DS with a sleep switch). This is because the exploit requires your device to enter sleep mode while still having access to the buttons.
|
||||
The usage of this exploit, regardless of the flashing method, requires access to a small magnet if the target console is of a folding style (any 3DS family system that is not the old 2DS with a sleep switch). This is because the exploit requires your console to enter sleep mode while still having access to the buttons.
|
||||
|
||||
To test if a magnet will work, hold it on or around the (A)(B)(X)(Y) buttons while the device is powered on to see if it triggers sleep mode. If it does, both displays will go black as long as the magnet is held in that spot.
|
||||
To test if a magnet will work, hold it on or around the (A)(B)(X)(Y) buttons while the console is powered on to see if it triggers sleep mode. If it does, both displays will go black as long as the magnet is held in that spot.
|
||||
{: .notice--info}
|
||||
|
||||
Note that the flashcart will not be able to be used for its standard functions while the ntrboot exploit is installed on it (except for in the case of the Acekard 2i, which remains functional *on NDS and custom firmware 3DS systems only*). This means that, for most flashcarts, it will not even display on the HOME Menu. There are optional steps at the end of the ntrboot flashing instructions to remove it from your flashcart when you are done.
|
||||
@ -67,7 +67,7 @@ ___
|
||||
|
||||
#### Flashing ntrboot (3DS Multi System)
|
||||
|
||||
This method requires temporary access to a second 3DS family device that is already running boot9strap. This does not require your flashcart to support either 3DS's version.
|
||||
This method requires temporary access to a second 3DS family console that is already running boot9strap. This does not require your flashcart to support either 3DS's version.
|
||||
|
||||
Continue to [Flashing ntrboot (3DS Multi System)](flashing-ntrboot-(3ds-multi-system))
|
||||
{: .notice--primary}
|
||||
|
@ -6,7 +6,7 @@ title: "Region Changing"
|
||||
|
||||
### Required Reading
|
||||
|
||||
This is an add-on section for region changing your device. This is done by installing the 11.15.0 CTRTransfer image for the region you want to switch to. After installing the image, you can update your device normally to the latest firmware (11.17.0).
|
||||
This is an add-on section for region changing your console. This is done by installing the 11.15.0 CTRTransfer image for the region you want to switch to. After installing the image, you can update your console normally to the latest firmware (11.17.0).
|
||||
|
||||
Note that region changing is almost completely unnecessary since Luma3DS supports out-of-region games and individual title [Locale Emulation](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features). Additionally, running NDS games with alternative out-of-region languages is supported by [TWiLight Menu++](https://github.com/DS-Homebrew/TWiLightMenu/releases). You should only perform a region change if you wish to have your system UI is in a language that is not available on your console's current region.
|
||||
|
||||
@ -17,14 +17,14 @@ As a part of this process, your system configuration will be reset to its defaul
|
||||
{: .notice--warning}
|
||||
|
||||
{% capture notice-6 %}
|
||||
If you change the region of your device:
|
||||
If you change the region of your console:
|
||||
|
||||
+ You will not be able to use your NNID (if you have one). NNIDs are locked to the region that they were created in.
|
||||
+ You may not be able to access the eShop, even if you [delete your eShop account](https://en-americas-support.nintendo.com/app/answers/detail/a_id/74/~/how-to-delete-a-nintendo-eshop-account) beforehand. This is because certain titles tend to remain linked to the 3DS, even after account deletion (especially on New 3DS).
|
||||
+ While purchases can no longer be made on eShop, game updates can still be downloaded. Updates are usually required for online play.
|
||||
+ This logic extends to system transfers, meaning you would not be able to perform a system transfer from a USA 3DS to a region-changed JPN-to-USA 3DS.
|
||||
+ That being said, system transfer and game updates are region locked anyway (e.g. Japanese eShop only has Japanese game updates).
|
||||
+ **You will not be able to uninstall custom firmware without bricking the device!** If you intend to uninstall custom firmware in the future, you **MUST** restore your NAND backup that was created before the region change.
|
||||
+ **You will not be able to uninstall custom firmware without bricking the console!** If you intend to uninstall custom firmware in the future, you **MUST** restore your NAND backup that was created before the region change.
|
||||
{% endcapture %}
|
||||
|
||||
<div class="notice--danger">{{ notice-6 | markdownify }}</div>
|
||||
@ -36,7 +36,7 @@ To download the CTRTransfer images on this page, you will need a torrent client
|
||||
|
||||
* The latest release of [GodMode9](https://github.com/d0k3/GodMode9/releases/latest) (the GodMode9 `.zip` file)
|
||||
* The latest release of [FBI](https://github.com/Steveice10/FBI/releases/latest) *(the`.3dsx` file)*
|
||||
* The 11.15.0 CTRTransfer image for your device type of the region that you want to change to (e.g. Download "New 3DS or 2DS - USA" if you have a New 3DS and want to change your region to USA)
|
||||
* The 11.15.0 CTRTransfer image for your console type of the region that you want to change to (e.g. Download "New 3DS or 2DS - USA" if you have a New 3DS and want to change your region to USA)
|
||||
{% include_relative include/ctrtransfer-images.txt %}
|
||||
|
||||
### Instructions
|
||||
@ -47,7 +47,7 @@ To download the CTRTransfer images on this page, you will need a torrent client
|
||||
|
||||
#### Section II - NAND Backup
|
||||
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
{% include_relative include/nand-backup.txt %}
|
||||
|
||||
#### Section III - CTRTransfer
|
||||
|
@ -20,8 +20,8 @@ Your SD card must be formatted as FAT32 to follow this guide, or else the 3DS wi
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy `boot.3dsx` and `boot.firm` from the Luma3DS `.zip` to the root of your SD card, replacing any existing files
|
||||
+ The root of the SD card refers to the initial directory on your SD card where you can see the Nintendo 3DS folder, but are not inside of it
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
+ If you see the Luma3DS configuration menu, press (Start) to save and reboot
|
||||
|
||||
The latest version of Luma3DS has now been installed on your SD card and on internal memory.
|
||||
|
@ -16,7 +16,7 @@ This method requires a reasonably powerful GPU (any dedicated graphics card made
|
||||
{% capture technical_info %}
|
||||
<summary><em>Technical Details (optional)</em></summary>
|
||||
|
||||
To install boot9strap on your device, we derive your device's unique encryption key. To accomplish this, we use a tool called Seedminer to calculate the data encryption key (movable.sed) for your device.
|
||||
To install boot9strap on your console, we derive your console's unique encryption key. To accomplish this, we use a tool called Seedminer to calculate the data encryption key (movable.sed) for your console.
|
||||
|
||||
Because we do not have access to the Friends List, we are deriving the first part of `movable.sed` using a Mii QR code instead of by performing a two-way friend exchange.
|
||||
|
||||
|
@ -10,7 +10,7 @@ ___
|
||||
|
||||
### Next step: BannerBomb3
|
||||
|
||||
Once you have your device's encryption key (`movable.sed`), you can use it in conjunction with BannerBomb3, which uses your `movable.sed` file to take advantage of exploits in the System Settings application.
|
||||
Once you have your console's encryption key (`movable.sed`), you can use it in conjunction with BannerBomb3, which uses your `movable.sed` file to take advantage of exploits in the System Settings application.
|
||||
|
||||
Continue to [BannerBomb3 + Fredtool (TWN)](bannerbomb3-fredtool-(twn))
|
||||
{: .notice--primary}
|
||||
|
@ -10,7 +10,7 @@ ___
|
||||
|
||||
### Next step: BannerBomb3
|
||||
|
||||
Once you have your device's encryption key (`movable.sed`), you can use it in conjunction with BannerBomb3, which uses your `movable.sed` file to take advantage of exploits in the System Settings application.
|
||||
Once you have your console's encryption key (`movable.sed`), you can use it in conjunction with BannerBomb3, which uses your `movable.sed` file to take advantage of exploits in the System Settings application.
|
||||
|
||||
Continue to [BannerBomb3](bannerbomb3)
|
||||
{: .notice--primary}
|
||||
|
@ -23,8 +23,8 @@ Guide pages:
|
||||
* [Finalizing Setup](#finalizing-setup)
|
||||
|
||||
Issues after installation:
|
||||
* [Boot issues](#boot-issues-on-devices-with-custom-firmware)
|
||||
* [Software issues](#software-issues-on-devices-with-custom-firmware)
|
||||
* [Boot issues](#boot-issues-on-consoles-with-custom-firmware)
|
||||
* [Software issues](#software-issues-on-consoles-with-custom-firmware)
|
||||
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
@ -70,13 +70,13 @@ Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance,
|
||||
![]({{ "/images/screenshots/multiple-id0.png" | absolute_url }})
|
||||
{: .notice--info}
|
||||
|
||||
This occurs when you use your SD card in multiple 3DS devices and is intended to prevent inadvertently merging data that would not be valid on other devices. To figure out which long folder name is correct for your 3DS, follow these instructions:
|
||||
This occurs when you use your SD card in multiple 3DS consoles and is intended to prevent inadvertently merging data that would not be valid on other consoles. To figure out which long folder name is correct for your 3DS, follow these instructions:
|
||||
|
||||
1. Rename the `Nintendo 3DS` folder to `BACKUP_Nintendo 3DS`
|
||||
1. Reinsert your SD card into your device and power on your device
|
||||
1. Wait for the device to generate the SD card data
|
||||
1. Reinsert your SD card into your console and power on your console
|
||||
1. Wait for the console to generate the SD card data
|
||||
+ Your applications will have disappeared. This is normal and will be resolved shortly
|
||||
1. Power off your device and reinsert your SD card into your computer
|
||||
1. Power off your console and reinsert your SD card into your computer
|
||||
1. Navigate to the `Nintendo 3DS` folder on your SD card
|
||||
1. Copy the 32 character long name of the folder you see
|
||||
+ This is your true ID0 that you will use in [Section II of Seedminer](seedminer#section-ii---seedminer)
|
||||
@ -129,7 +129,7 @@ Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID
|
||||
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this console in a way that makes this method impossible to perform. If this is the case, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
@ -274,7 +274,7 @@ If your files are in the correct locations, re-create the save using the [PicHax
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" or Errdisp when opening Picross</u></summary>
|
||||
|
||||
Your device already has custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
Your console already has custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
@ -297,9 +297,9 @@ Your modified `00000001.sav` file may be misplaced, or you may have used the wro
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Soundhax</u></summary>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
If your console is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
If your device is not on those firmwares, it likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
If your console is not on those firmwares, it likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
@ -313,7 +313,7 @@ There is an issue with your `otherapp.bin` file (it is missing, misplaced, or co
|
||||
{% capture compat %}
|
||||
<summary><u>"Could not play"</u></summary>
|
||||
|
||||
You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow [Seedminer](seedminer).
|
||||
You have the wrong Soundhax file for your console and region, or your console is incompatible with Soundhax. In the latter case, you should update your console to the latest version and follow [Seedminer](seedminer).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
@ -379,7 +379,7 @@ The SSLoth proxy was incorrectly configured. Re-do the SSLoth section on the pag
|
||||
|
||||
Follow these steps in order:
|
||||
|
||||
1. Launch System Settings on your device
|
||||
1. Launch System Settings on your console
|
||||
1. Navigate to `Internet Settings` -> `Connection Settings`
|
||||
1. Click on your network connection slot and navigate to `Change Settings` -> `Next Page (right arrow)` -> `Proxy Settings`
|
||||
1. Set "Proxy Settings" to "No"
|
||||
@ -398,7 +398,7 @@ Follow these steps in order:
|
||||
{% capture compat %}
|
||||
<summary><u>"To use the Internet Browser, please update your system using the System Update option in the System Settings."</u></summary>
|
||||
|
||||
First, make sure you entered the correct proxy for the connection you're using. If not, go back to [Section II](installing-boot9strap-(ssloth-browser).html#section-ii---ssloth). If the proxy is correct, then your device has been cart-updated, which means an alternate exploit will need to be used.
|
||||
First, make sure you entered the correct proxy for the connection you're using. If not, go back to [Section II](installing-boot9strap-(ssloth-browser).html#section-ii---ssloth). If the proxy is correct, then your console has been cart-updated, which means an alternate exploit will need to be used.
|
||||
|
||||
<u>Method 1</u><br>
|
||||
If the two numbers before the region in the system version string is equal to or less than 36 (e.g. Ver. 11.14.0-**36**U), you can follow [Soundhax](installing-boot9strap-(soundhax)). When prompted to select a firmware to generate the sound file, use:
|
||||
@ -412,14 +412,14 @@ If the two numbers before the region in the system version string is equal to or
|
||||
If you have an Old 3DS / Old 3DS XL / 2DS, you can try a Safe Mode update, which will trigger an alternate exploit:
|
||||
|
||||
1. Ensure that the proxy that you used for SSLoth is still actively applied to your internet connection
|
||||
1. With your device powered off, hold the following buttons: (Left Shoulder) + (Right Shoulder) + (D-Pad Up) + (A), and while holding these buttons together, power on your device
|
||||
+ Keep holding the buttons until the device boots into Safe Mode (a "system update" menu)
|
||||
1. With your console powered off, hold the following buttons: (Left Shoulder) + (Right Shoulder) + (D-Pad Up) + (A), and while holding these buttons together, power on your console
|
||||
+ Keep holding the buttons until the console boots into Safe Mode (a "system update" menu)
|
||||
1. Press "OK" to accept the update
|
||||
1. If everything worked correctly, the update will fail and the 3DS will boot into SafeB9SInstaller. If it did, then continue from [Section IV](installing-boot9strap-(ssloth-browser)#section-iv---installing-boot9strap).
|
||||
|
||||
---
|
||||
|
||||
If these methods didn't work (or do not apply to you), update your device to the latest version and follow [Seedminer](seedminer).
|
||||
If these methods didn't work (or do not apply to you), update your console to the latest version and follow [Seedminer](seedminer).
|
||||
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
@ -486,7 +486,7 @@ This likely indicates that you already have custom firmware. You should [check f
|
||||
## Finalizing Setup
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to update device</u></summary>
|
||||
<summary><u>Unable to update console</u></summary>
|
||||
|
||||
The steps below can be attempted in any order, but are listed from easiest to hardest to perform.
|
||||
|
||||
@ -544,17 +544,17 @@ If you have enough space on your SD card, your SD might be corrupted or faulty.
|
||||
|
||||
---
|
||||
|
||||
## Boot issues on devices with custom firmware
|
||||
## Boot issues on consoles with custom firmware
|
||||
|
||||
The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
|
||||
The steps detailed here generally assume that your console has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
|
||||
{: .notice--info}
|
||||
|
||||
### Power/notification light indicators
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>My device powers off when I try to turn it on, and/or the notification LED shows a color on boot</u></summary>
|
||||
<summary><u>My console powers off when I try to turn it on, and/or the notification LED shows a color on boot</u></summary>
|
||||
|
||||
There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
|
||||
There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the console.
|
||||
|
||||
If the notification LED flashes:
|
||||
|
||||
@ -564,18 +564,18 @@ If the notification LED flashes:
|
||||
|
||||
You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
|
||||
|
||||
If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
|
||||
If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your console (such as a disconnected backlight cable). You may be able to get your console to boot by holding it at certain angles.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>My device gets stuck on a black screen with blue power light staying on</u></summary>
|
||||
<summary><u>My console gets stuck on a black screen with blue power light staying on</u></summary>
|
||||
|
||||
The steps below can be attempted in any order, but are listed from least to most time-consuming.
|
||||
|
||||
1. Power off your device, remove the SD card, re-insert it, then power on your device.
|
||||
1. Power off your device, eject the game cartridge if inserted, power on your device, then wait up to ten minutes. If your device boots within ten minutes, the issue has been fixed and is unlikely to reoccur
|
||||
1. Rename the `Nintendo 3DS` folder on your SD card to `Nintendo 3DS_BACKUP`, then attempt to boot. If your device successfully boots, there is some issue within your `Nintendo 3DS` folder. Try clearing HOME Menu extdata:
|
||||
1. Power off your console, remove the SD card, re-insert it, then power on your console.
|
||||
1. Power off your console, eject the game cartridge if inserted, power on your console, then wait up to ten minutes. If your console boots within ten minutes, the issue has been fixed and is unlikely to reoccur
|
||||
1. Rename the `Nintendo 3DS` folder on your SD card to `Nintendo 3DS_BACKUP`, then attempt to boot. If your console successfully boots, there is some issue within your `Nintendo 3DS` folder. Try clearing HOME Menu extdata:
|
||||
+ Navigate to `/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/`
|
||||
+ Delete the corresponding folder for your 3DS region:
|
||||
+ **EUR Region**: `00000098`
|
||||
@ -585,10 +585,10 @@ The steps below can be attempted in any order, but are listed from least to most
|
||||
+ **KOR Region**: `000000A9`
|
||||
+ **TWN Region**: `000000B1`
|
||||
1. Try booting into recovery mode and updating your system:
|
||||
+ Power off your device
|
||||
+ Power off your console
|
||||
+ Hold (Left Shoulder) + (Right Shoulder) + (D-Pad Up) + (A)
|
||||
+ Power on your device
|
||||
+ If you were successful, the device will boot to an "update your system" screen
|
||||
+ Power on your console
|
||||
+ If you were successful, the console will boot to an "update your system" screen
|
||||
1. Follow the [CTRTransfer](ctrtransfer) guide
|
||||
1. For further support, ask for help at [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
@ -613,9 +613,9 @@ There are a number of reasons as to why this could be happening. In any case, th
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..."</u></summary>
|
||||
|
||||
ARM11 exception handlers are disabled, or custom firmware is not installed. Try enabling ARM11 exception handlers:
|
||||
+ Power off your device
|
||||
+ Power off your console
|
||||
+ Hold (Select)
|
||||
+ Power on your device, while still holding (Select)
|
||||
+ Power on your console, while still holding (Select)
|
||||
+ If the "Disable ARM11 exception handlers" box is checked, uncheck it
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
@ -624,11 +624,11 @@ ARM11 exception handlers are disabled, or custom firmware is not installed. Try
|
||||
<summary><u>HOME Menu is missing installed applications</u></summary>
|
||||
|
||||
This could be caused by various reasons, but most likely because your SD card is not being read by the system.
|
||||
You can check if your SD is being read by holding SELECT on boot and checking the yellow text on the bottom screen; if it says "Booted from CTRNAND via B9S", then your device is booting from the internal memory and not from the SD card.
|
||||
You can check if your SD is being read by holding SELECT on boot and checking the yellow text on the bottom screen; if it says "Booted from CTRNAND via B9S", then your console is booting from the internal memory and not from the SD card.
|
||||
If this is the case, attempt the steps below, which are listed from easiest to hardest:
|
||||
1. Power off your device, remove the SD card, re-insert it, then power on your device
|
||||
1. Power off your device, remove the SD card, insert it on your PC, download the latest release of [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extract `boot.firm` from the `Luma3DS.zip` and place it on the root of your SD card (replacing any existing file)
|
||||
1. Power off your device, remove the SD card, insert it on your PC and reformat your SD card according to your computer's operating system: [Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux)) *(this will wipe your SD card data)*
|
||||
1. Power off your console, remove the SD card, re-insert it, then power on your console
|
||||
1. Power off your console, remove the SD card, insert it on your PC, download the latest release of [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extract `boot.firm` from the `Luma3DS.zip` and place it on the root of your SD card (replacing any existing file)
|
||||
1. Power off your console, remove the SD card, insert it on your PC and reformat your SD card according to your computer's operating system: [Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux)) *(this will wipe your SD card data)*
|
||||
1. Test your SD card for errors by following the guide according to your computer's operating system: [Windows](h2testw-(windows)), [Linux](f3-(linux)), [macOS](f3xswift-(mac)). If your SD card is marked as faulty, then you will have to replace your SD card
|
||||
1. Your SD card slot may be broken. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for further assistance
|
||||
{% endcapture %}
|
||||
@ -637,8 +637,8 @@ If this is the case, attempt the steps below, which are listed from easiest to h
|
||||
{% capture compat %}
|
||||
<summary><u>Blue "BOOTROM ERROR" screen</u></summary>
|
||||
|
||||
Your device is likely hard-bricked. You will need to buy an ntrboot flashcart to reinstall boot9strap in order to attempt to fix your device. This may also indicate a hardware issue that cannot be fixed. In any case, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
+ It is also possible that someone has set a boot-time splash screen that just looks like a brick. Try leaving your device powered on, waiting on the blue screen, for five minutes.
|
||||
Your console is likely hard-bricked. You will need to buy an ntrboot flashcart to reinstall boot9strap in order to attempt to fix your console. This may also indicate a hardware issue that cannot be fixed. In any case, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
+ It is also possible that someone has set a boot-time splash screen that just looks like a brick. Try leaving your console powered on, waiting on the blue screen, for five minutes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
@ -649,37 +649,37 @@ Please take a photo of the error and join [Nintendo Homebrew on Discord](https:/
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Software issues on devices with custom firmware
|
||||
## Software issues on consoles with custom firmware
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DSi / DS functionality is broken or has been replaced with Flipnote Studio</u></summary>
|
||||
|
||||
1. Download the latest release of [TWLFix-CFW](https://github.com/MechanicalDragon0687/TWLFix-CFW/releases/latest) (the `.3dsx` file)
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Create a folder named `3ds` on the root of your SD card if it does not already exist
|
||||
1. Copy `TWLFix-CFW.3dsx` to the `/3ds/` folder on your SD card
|
||||
1. Reinsert your SD card into your device
|
||||
1. Reinsert your SD card into your console
|
||||
1. Open the Homebrew Launcher
|
||||
1. Launch TWLFix-CFW from the list of homebrew
|
||||
1. Press (A) to uninstall the broken TWL titles
|
||||
1. Press (Start) to reboot the device
|
||||
1. Press (Start) to reboot the console
|
||||
1. Perform a System Update by going to System Settings, then "Other Settings", then going all the way to the right and using "System Update"
|
||||
+ The update will see that the essential TWL titles have been uninstalled, and will redownload and reinstall them
|
||||
1. Once the update is complete, tap "OK" to reboot the device
|
||||
1. Once the update is complete, tap "OK" to reboot the console
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>GBA Virtual Console and/or Safe Mode functionality is broken</u></summary>
|
||||
|
||||
Your device is running Luma3DS 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your device to a modern custom firmware environment.
|
||||
Your console is running Luma3DS 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your console to a modern custom firmware environment.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Extended memory mode games (Pokemon Sun/Moon, Smash, etc.) don't work</u></summary>
|
||||
|
||||
This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will need to system format your device to fix this issue.
|
||||
This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will need to system format your console to fix this issue.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
@ -698,7 +698,7 @@ If you weren't able to find your error or the instructions didn't work, join [Ni
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu extdata</u></summary>
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Navigate to the `/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/` folder on your SD card
|
||||
1. Delete the corresponding folder for your 3DS region:
|
||||
@ -708,21 +708,21 @@ If you weren't able to find your error or the instructions didn't work, join [Ni
|
||||
+ **CHN Region**: `000000A1`
|
||||
+ **KOR Region**: `000000A9`
|
||||
+ **TWN Region**: `000000B1`
|
||||
1. Reinsert your SD card into your device
|
||||
1. Reinsert your SD card into your console
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu theme data</u></summary>
|
||||
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Navigate to the `/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/` folder on your SD card
|
||||
1. Delete the corresponding folder for your 3DS region:
|
||||
+ **EUR Region**: `000002ce`
|
||||
+ **JPN Region**: `000002cc`
|
||||
+ **USA Region**: `000002cd`
|
||||
1. Reinsert your SD card into your device
|
||||
1. Reinsert your SD card into your console
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
@ -730,10 +730,10 @@ If you weren't able to find your error or the instructions didn't work, join [Ni
|
||||
<summary><u>Turning off Parental Controls</u></summary>
|
||||
|
||||
You can disable the Parental Controls feature by going to System Settings -> Parental Controls and inserting the PIN, then pressing "Clear Settings", then "Delete" to remove it.
|
||||
However, if you do not know the PIN and therefore cannot access the device's settings, you will need to disable it. In order to do this, you need to obtain your device's master key (mkey):
|
||||
However, if you do not know the PIN and therefore cannot access the console's settings, you will need to disable it. In order to do this, you need to obtain your console's master key (mkey):
|
||||
1. Go to [this website](https://mkey.eiphax.tech/)
|
||||
1. Fill the following boxes with the information:
|
||||
+ Device Type: Select "3DS" (the same applies if you are using a 2DS, New 3DS (XL/LL) or New 2DS (XL/LL))
|
||||
+ Console Type: Select "3DS" (the same applies if you are using a 2DS, New 3DS (XL/LL) or New 2DS (XL/LL))
|
||||
+ System Date: The day and month your console's clock is set to
|
||||
+ Inquiry Number: Can be obtained by pressing "Forgot PIN" then "I Forgot" in the Parental Controls screen
|
||||
1. After you have obtained your mkey, press OK on the screen you have obtained your Inquiry Number, then input the master key
|
||||
|
@ -6,7 +6,7 @@ title: "Uninstall CFW"
|
||||
|
||||
### Required Reading
|
||||
|
||||
This will completely remove CFW from your device, including boot9strap and Luma3DS, for the purpose of restoring the device to stock.
|
||||
This will completely remove CFW from your console, including boot9strap and Luma3DS, for the purpose of restoring the console to stock.
|
||||
|
||||
Any unsigned (illegitimate) games will be rendered unusable and will be removed during this process. Use a [save manager](https://github.com/FlagBrew/Checkpoint/releases/latest) to back up any saves that you care about.
|
||||
|
||||
@ -34,7 +34,7 @@ then uninstalling CFW <u><strong>WILL BRICK YOUR CONSOLE</strong></u>. If this a
|
||||
{% endcapture %}
|
||||
<div class="notice--danger">{{ notice-6 | markdownify }}</div>
|
||||
|
||||
These instructions will only work on devices with a Luma3DS version of 8.0 or higher. If you have an older version of Luma, you must upgrade your setup before following these instructions. Follow [this page](checking-for-cfw) to find your upgrade instructions.
|
||||
These instructions will only work on consoles with a Luma3DS version of 8.0 or higher. If you have an older version of Luma, you must upgrade your setup before following these instructions. Follow [this page](checking-for-cfw) to find your upgrade instructions.
|
||||
{: .notice--warning}
|
||||
|
||||
### What You Need
|
||||
@ -47,41 +47,41 @@ These instructions will only work on devices with a Luma3DS version of 8.0 or hi
|
||||
### Instructions
|
||||
|
||||
#### Section I - Prep Work
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy `boot.firm` and `boot.3dsx` from the Luma3DS `.zip` to the root of your SD card
|
||||
1. Copy `GodMode9.firm` from the GodMode9 `.zip` to the `/luma/payloads/` folder on your SD card
|
||||
1. Copy the `gm9` folder from the GodMode9 `.zip` to the root of your SD card
|
||||
1. Copy `DSiWareUninstaller.3dsx` to the `/3ds/` folder on your SD card
|
||||
1. Copy `safety_test.gm9` to the `/gm9/scripts/` folder on your SD card
|
||||
1. Reinsert your SD card into your device
|
||||
1. Reinsert your SD card into your console
|
||||
|
||||
#### Section II - DS Mode Tests
|
||||
The purpose of this section is to check whether built-in DS mode applications will continue to work once CFW is uninstalled. If you skip this section, DS mode or its functions may be inaccessible until CFW is reinstalled.
|
||||
|
||||
##### DS Connection Settings Test
|
||||
1. Power on your device
|
||||
1. Launch System Settings on your device
|
||||
1. Power on your console
|
||||
1. Launch System Settings on your console
|
||||
1. Navigate to `Internet Settings` -> `Nintendo DS Connection Settings`, then click OK
|
||||
1. You should boot into the Nintendo DS Connection Setup menu
|
||||
+ If your console displays the Japanese version of Flipnote Studio, a black screen, or an error message, the test has failed
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
|
||||
##### DS Download Play Test
|
||||
1. Power on your device
|
||||
1. Power on your console
|
||||
1. Launch the Download Play application (![]({{ "/images/download-play-icon.png" | absolute_url }}){: height="24px" width="24px"})
|
||||
1. Select "Nintendo DS"
|
||||
1. If your device loads into a "Download software via DS Download Play" menu, the test was successful
|
||||
1. If your console loads into a "Download software via DS Download Play" menu, the test was successful
|
||||
+ If your console displays the Japanese version of Flipnote Studio, a black screen, or an error message, the test has failed
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
|
||||
If either of these tests has failed, DS mode, DS Download Play, and/or DS Connection Settings may be inaccessible once CFW is uninstalled! You should [fix DS mode](troubleshooting#software-issues-on-devices-with-custom-firmware) before continuing.
|
||||
If either of these tests has failed, DS mode, DS Download Play, and/or DS Connection Settings may be inaccessible once CFW is uninstalled! You should [fix DS mode](troubleshooting#software-issues-on-consoles-with-custom-firmware) before continuing.
|
||||
{: .notice--warning}
|
||||
|
||||
#### Section III - Safety Test
|
||||
The purpose of this section is to verify that the console will boot and that critical system functions, like System Settings and the keyboard, will work once CFW is uninstalled. **If you skip this section, you may BRICK your device!**
|
||||
The purpose of this section is to verify that the console will boot and that critical system functions, like System Settings and the keyboard, will work once CFW is uninstalled. **If you skip this section, you may BRICK your console!**
|
||||
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
1. If you are prompted to create an essential files backup, press (A) to do so, then press (A) to continue once it is complete
|
||||
1. If you are prompted to fix the RTC date&time, press (A) to do so, then set the date and time, then press (A) to continue
|
||||
+ Note that, if you had to fix the RTC date and time, you will have to fix the time in the System Settings as well after following this guide
|
||||
@ -90,22 +90,22 @@ The purpose of this section is to verify that the console will boot and that cri
|
||||
1. Select "safety_test"
|
||||
1. Read the text on-screen and press (A) to continue
|
||||
1. You should boot into the regular 3DS HOME Menu (any custom theme is irrelevant). If you do, continue these instructions
|
||||
+ If you do not boot into the regular 3DS HOME Menu (black screen, error screen, etc.), uninstalling CFW **WILL BRICK YOUR DEVICE!**
|
||||
1. Launch System Settings on your device
|
||||
+ If you do not boot into the regular 3DS HOME Menu (black screen, error screen, etc.), uninstalling CFW **WILL BRICK YOUR CONSOLE!**
|
||||
1. Launch System Settings on your console
|
||||
+ If the console crashes at this point, the test has failed
|
||||
1. Select "Other Settings"
|
||||
1. Select "Profile"
|
||||
1. Select "User Name"
|
||||
1. If you are able to enter a new user name, the test was successful
|
||||
+ If the keyboard does not appear, the screen freezes, or the console crashes, the test has failed
|
||||
1. Power off your device
|
||||
1. Power off your console
|
||||
|
||||
If you do NOT boot into the regular 3DS HOME Menu, or System Settings / your keyboard is inaccessible, **DO NOT continue with these instructions**! Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask (in English) for someone there to assist you.
|
||||
{: .notice--danger}
|
||||
|
||||
#### Section IV - NAND Backup
|
||||
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
1. Press (Home) to bring up the action menu
|
||||
1. Select "Scripts..."
|
||||
1. Select "GM9Megascript"
|
||||
@ -117,14 +117,14 @@ If you do NOT boot into the regular 3DS HOME Menu, or System Settings / your key
|
||||
1. Press (B) to return to the main menu
|
||||
1. Select “Exit”
|
||||
1. Press (Home) to bring up the action menu
|
||||
1. Select “Poweroff system” to power off your device
|
||||
1. Select “Poweroff system” to power off your console
|
||||
|
||||
#### Section V - Removing illegitimate content
|
||||
This section will remove illegitimate content, like homebrew and dumped cartridges. If you have save data that you care about, back it up with a save manager before continuing!
|
||||
{: .notice--warning}
|
||||
|
||||
1. Power on your device
|
||||
1. Launch System Settings on your device
|
||||
1. Power on your console
|
||||
1. Launch System Settings on your console
|
||||
1. Navigate to Data Management > Nintendo 3DS > Software
|
||||
1. In this list of software, delete any non-Nintendo content you installed while using CFW
|
||||
+ This includes common system software such as FBI, Anemone3DS, Luma Updater, Homebrew Launcher, Checkpoint, and others, along with any games and titles that you did *not* install from the eShop
|
||||
@ -143,16 +143,16 @@ This section will remove illegitimate content, like homebrew and dumped cartridg
|
||||
1. Press (B) to exit the Rosalina menu
|
||||
1. Press (Home), then close Download Play
|
||||
1. Launch the Download Play application
|
||||
1. Your device should load the Homebrew Launcher
|
||||
1. Your console should load the Homebrew Launcher
|
||||
1. Launch DSiWare Uninstaller from the list of homebrew
|
||||
1. Follow the prompts and allow the program to uninstall
|
||||
1. Once the process has succeeded, exit the Homebrew Launcher and power off your device
|
||||
1. Once the process has succeeded, exit the Homebrew Launcher and power off your console
|
||||
|
||||
#### Section VI - System Format
|
||||
This section will ensure that all illegitimate tickets are removed, allowing eShop to work normally. This will remove all content from the 3DS and log you out of your NNID. Keep in mind that your console's encryption key will be shuffled, meaning that any old data will be rendered inaccessible, even if you have a backup of your SD contents.
|
||||
|
||||
1. Power on your device
|
||||
1. Launch System Settings on your device
|
||||
1. Power on your console
|
||||
1. Launch System Settings on your console
|
||||
1. Navigate to Other Settings -> Next Page (until the final page) -> Format System Memory
|
||||
1. Follow the prompts to format your 3DS
|
||||
|
||||
@ -161,7 +161,7 @@ This section will ensure that all illegitimate tickets are removed, allowing eSh
|
||||
This is your final opportunity to verify that all safety steps above have been followed! Please ensure that you have followed all sections on this page, **especially** `Section III - Safety Test`, before continuing.
|
||||
{: .notice--warning}
|
||||
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
|
||||
+ If you instead see the Luma3DS chainloader, use the D-Pad and the (A) button to select GodMode9
|
||||
1. Press (Home) to bring up the action menu
|
||||
1. Select "Scripts..."
|
||||
@ -174,11 +174,11 @@ This is your final opportunity to verify that all safety steps above have been f
|
||||
1. Press (B) to return to the main menu
|
||||
1. Select "Exit"
|
||||
1. Press (A) to relock write permissions if prompted
|
||||
1. Press (Start) to reboot your device
|
||||
1. Press (Start) to reboot your console
|
||||
|
||||
___
|
||||
|
||||
All custom firmware has been removed from your device.
|
||||
All custom firmware has been removed from your console.
|
||||
{: .notice--success}
|
||||
|
||||
You can now remove any extra files and folders from the root of your SD card that are *not* the `Nintendo 3DS`, `DCIM`, or `private` folders.
|
||||
|
@ -29,7 +29,7 @@ For all steps in this section, overwrite any existing files on your SD card.
|
||||
1. Copy `boot9strap.firm` and `boot9strap.firm.sha` from the boot9strap `.zip` to the `/boot9strap/` folder on your SD card
|
||||
1. Copy `SafeB9SInstaller.firm` from the SafeB9SInstaller `.zip` to the root of your SD card and rename it to `boot.firm`
|
||||
+ If a `boot.firm` already exists, replace it
|
||||
1. Reinsert your SD card into your device
|
||||
1. Reinsert your SD card into your console
|
||||
|
||||
![]({{ "/images/screenshots/updateb9s-root-layout.png" | absolute_url }})
|
||||
{: .notice--info}
|
||||
@ -37,7 +37,7 @@ For all steps in this section, overwrite any existing files on your SD card.
|
||||
|
||||
#### Section II - Installing boot9strap
|
||||
|
||||
1. Power on your device
|
||||
1. Power on your console
|
||||
+ This should automatically launch SafeB9SInstaller
|
||||
{%- include_relative include/install-boot9strap-safeb9sinstaller.txt isbootfirm="true" inline="true" %}
|
||||
|
||||
@ -45,9 +45,9 @@ For all steps in this section, overwrite any existing files on your SD card.
|
||||
|
||||
1. Insert your SD card into your computer
|
||||
1. Copy `boot.firm` and `boot.3dsx` from the Luma3DS `.zip` to the root of your SD card, replacing the existing file
|
||||
1. Reinsert your SD card into your device
|
||||
1. Power on your device
|
||||
1. If your device has booted into the Luma3DS configuration menu, press (Start) to save and reboot
|
||||
1. Reinsert your SD card into your console
|
||||
1. Power on your console
|
||||
1. If your console has booted into the Luma3DS configuration menu, press (Start) to save and reboot
|
||||
+ Luma3DS configuration menu are settings for the Luma3DS custom firmware. Many of these settings may be useful for customization or debugging
|
||||
+ For the purpose of this guide, these settings will be left on default settings
|
||||
|
||||
|
@ -4,11 +4,11 @@ title: "Updating Firmware (KOR)"
|
||||
|
||||
### Required Reading
|
||||
|
||||
To use the Seedminer exploit, you must update your device to the latest system version.
|
||||
To use the Seedminer exploit, you must update your console to the latest system version.
|
||||
|
||||
### What you need
|
||||
|
||||
* An internet connection on your device
|
||||
* An internet connection on your console
|
||||
|
||||
#### Section I - Updating the System
|
||||
|
||||
|
@ -4,11 +4,11 @@ title: "Updating Firmware (New 3DS)"
|
||||
|
||||
### Required Reading
|
||||
|
||||
To use the super-skaterhax exploit, you must update your device to the latest system version.
|
||||
To use the super-skaterhax exploit, you must update your console to the latest system version.
|
||||
|
||||
### What you need
|
||||
|
||||
* An internet connection on your device
|
||||
* An internet connection on your console
|
||||
|
||||
#### Section I - Updating the System
|
||||
|
||||
|
@ -4,11 +4,11 @@ title: "Updating Firmware (TWN)"
|
||||
|
||||
### Required Reading
|
||||
|
||||
To use the Seedminer exploit, you must update your device to the latest system version.
|
||||
To use the Seedminer exploit, you must update your console to the latest system version.
|
||||
|
||||
### What you need
|
||||
|
||||
* An internet connection on your device
|
||||
* An internet connection on your console
|
||||
|
||||
#### Section I - Updating the System
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user