Hacks Guide Wiki - User contributions [en]

3DS:Cleaninty

2026-02-22T13:55:52Z

ManiacOfHomebrew: Remove broken link to autosoap

{{lowercase title}}{{Infobox homebrew
| title = cleaninty
| developers = luigoalma
| version = 0.1.3
| releasedate = 2023-03-18
| github = luigoalma/cleaninty
| githubtag = v0.1.3
| forwindows = 1
| formac = 1
| forlinux = 1
}}
{{imbox
| type = delete
| text = Nintendo Homebrew no longer offers SOAP transfer services. This page is about the tools used, and can be used by anyone with their own console data. Users must provide their own donor console data. Use at your own risk.
}}
'''cleaninty''' is a PC tool used to communicate with Nintendo eShop servers, using the [[wikipedia:SOAP|SOAP]] protocol. For a 3DS, these servers deal with managing eShop accounts, downloading eShop titles, and system transfers. It is also the tool used for what is informally known as a "SOAP transfer".

==Overview==
SOAP transfers involve complex functionality. As a result, the following explanation has been divided into two versions: a simplified user-end version, and the technical version.
 If you do not care about the technical side of things, you may skip that part, and will still be able to understand how to use cleaninty itself.

<tabber>
|-|Simplified Explanation=
There are two pieces of data in a 3DS that let it talk to Nintendo's eShop servers with a unique ID: its serial number and its [[3DS:System files|<code>otp.bin</code>]]. If these are copied out of the console and used somewhere else, they can be used to imitate the console - meaning Nintendo's servers can act on commands without the console doing anything on its end. 
However, the files cannot communicate on their own, and a connection to Nintendo's servers that acts identically to a console is still needed. This is the part cleaninty handles.

The reason this allows for changing eShop regions easily, and at infinite range, are as follows:
* '''Ease of Use''': 'Records' of all purchased apps are stored on Nintendo's servers, and some of these records are tied to a separate account that existed before the concept of NNIDs was added - these tickets cannot be removed by normal means, and their presence blocks the console from registering to any other eShop region. (The most common of these tickets is the [[3dbrew:StreetPass Mii Plaza|Mii Plaza 3.x]] update.) The only way to remove these tickets is to transfer them to another console, and cleaninty is able to move ''only'' the legacy account's records by being extremely precise with what commands are and aren't used in the process.
* '''Infinite Range:''' System transfers are effectively divided into three parts: the local content transfer, the NNID transfer, and the legacy account transfer. The local content transfer is the important part here, as on an actual console, these three must be done at the same time - but if cleaninty sends the commands for a legacy account transfer, it doesn't start the content transfer, and thus the consoles do not have to be next to each other. (Technically, this also means a [[3DS:MM|Movable Moveover]] is the exact opposite of a SOAP transfer.)

|-|Technical Explanation=
First, some background info: there are two accounts for the eShop.

<ol>
<li>Legacy DeviceID-based accounts, which were in use starting from the first system version but are mostly unused now.
<li>NNID-based accounts, which were introduced by system firmware v7.0 and remain as the main account type.
</ol>

Additionally, it should be mentioned that there are four main parts of the 3DS eShop's servers that are related to SOAP operations. Connecting to most of them requires the use of two cerificates from the console(s) to verify it's a real console, those certificates being [[3dbrew:ClCertA|ClCertA]] and [[3dbrew:CTCert|CTCert]]. (The needed data from CTCert is stored inside the console's <code>otp.bin</code> [[3dbrew:OTP Registers|from offsets 0x20 to 0x80]].)

<ol>
<li>ECS: Handles management of NNID accounts and tickets. Requires certificates.
<li>IAS: Handles management of legacy accounts, and has IVS as a sub-service for identity verification (including a stored copy of movable.sed).
<li>CAS: Outputs lists of title metadata, country-related info, and valid currency management options. Requires certificates.
<li>NUS: Downloads of games, updates and system titles. Does '''not''' require certificates for system titles, but does require them for games and updates.
</ol>

NUS and CAS are not relevant to this specifically, but it is worth knowing about them in general.

More detailed information on this subject can be found on [https://yifan.lu/2015/04/22/opening-up-cardboard-crafting-an-american-new-3ds-non-xl/ this page.]

----

The issue that makes system transfers required at all is that legacy accounts are still used in some specific edge cases, when they shouldn't be.

Specifically, certain titles are not linked to the NNID when purchased/downloaded (the exact cause is still unknown, but a leading theory is that it's because they were delisted from the eShop), and as such, those titles' tickets will instead attach to the legacy account and stay there. The titles that do this will be called '''legacy titles''' for the remainder of this explanation.

Since the legacy account is meant to be entirely out of use, legacy titles are far harder to remove than 'normal' ones - an NNID can be moved anywhere with relative ease because ECS just throws ownership over and lets the console do proper region checks later, but IAS has significantly more checks with the legacy account.

Specifically, if there are still titles on the legacy account, then a specific call to IVS to create a new eShop account will fail because it will refuse to mismatch the legacy account's region with its titles.
 In this scenario, trying to do a normal system transfer to fix eShop works if done before region changing. But attempting to system transfer after the region change will also fail, because the console(s) detect that they're region changed at the firmware level before it even starts.
 And on top of that, the average user does not have a second console to system transfer to in the first place. This is where cleaninty comes in.

Specifically, cleaninty's role is to create a PC-based connection to Nintendo's servers using the same certificates that validate a normal connection, and then give the user extremely fine precision over which commands they do or don't want to use. Additionally, since it only uses the consoles' files and only talks to the servers, the physical consoles do not have to be present for any part of the process.

Using this PC-based connection, it is entirely possible to pick and choose in a very specific way that bypasses normal requirements, using two consoles (the "donor" and "recipient"):

First, the donor must already have a blank legacy account (either through luck or through its own SOAP transfer). This allows it to perform <code>EShopRegionChange</code> freely without restrictions, as there are no legacy titles holding it back.
Once the donor has a blank account, it can <code>EShopRegionChange</code> to match the recipient's eShop account region, and then proceed to take the recipient's account through a <code>SysTransfer</code>.
 The reason this works is because when cleaninty does the <code>SysTransfer</code>, the command is run in isolation - so it will not check the consoles' firmware regions, make no requests to ECS, and immediately move the account only after checking they're the same region '''without touching anything else'''.

Once the legacy account is moved, the recipient will create a new blank account when it next opens the eShop - and in turn, because the new account is made entirely from scratch, this new account's region will match the console's firmware even if it's region-changed. This gives the 'recipient' working eShop access and the ability to change its own region freely - and as the eShop has closed all new purchases and delisted titles cannot be redownloaded from the eShop, it should not be possible for it to receive legacy titles a second time, meaning this fix is effectively permanent.

Also note that the donor also remains 'free' when this happens, as the transferred legacy titles vanish at some point along the way instead of being properly moved to its account. This means that a donor can be used infinite times, the only limit being the seven-day cooldown between each individual <code>SysTransfer</code>.

</tabber>

==Features==

When the required constants have been supplied through <code>SetupConstants</code> and you have the unique data (<code>otp.bin</code> and either <code>SecureInfo_A</code> or the serial number) of a console, cleaninty can act as that console and do the following:

*<code>GenJson</code>: Compiles the console's data into a single JSON file. This JSON is required for all other commands except <code>RecoverIVS</code>.
*<code>CheckReg</code>: Obtains the console's eShop status, eShop region, and any titles attached to its eShop account, then updates the JSON file with the new data.
*<code>SysTransfer</code>: Moves the eShop titles of the source console to the target console. This is the only needed command for a SOAP transfer if the console has legacy tickets.
**A successful use of this command triggers a 7-day cooldown on system transfers for both consoles, the same as a full system transfer.
*<code>NNIDTransfer</code>: (Still experimental. Use with caution.) Moves only the NNIDs of the source console to the target console. This is not affected by system transfer cooldowns and does not trigger a cooldown.
*<code>LastTransfer</code>: Provides the date&time of the given console's last system transfer, the number of transfers it has ever done, and the time at which the current transfer cooldown will expire if there is one active.
*<code>GetIVS</code>: Downloads the console's stored copy of <code>movable.sed</code> from the SOAP servers, if they have one.
*<code>SetIVS</code>: Uploads the chosen JSON's stored <code>movable.sed</code> to the SOAP servers. This will overwrite the current stored movable.
*<code>RecoverIVS</code>: Tries to recover a console's <code>movable.sed</code> using only its raw <code>otp.bin</code> and eShop region data.
*<code>EShopDelete</code>: Deletes the target console's eShop account. This is the secondary part of a SOAP transfer if the console has no legacy tickets, as the console will then automatically register an account in the correct region when it next accesses the eShop.
*<code>EShopRegionChange</code>: Attempts to delete and then recreate the target console's eShop account for the entered region. This is the main part of a SOAP transfer if the console has no legacy tickets, but an <code>EShopDelete</code> should still be done afterward.
*<code>ETickets</code>/<code>ETicketDownload</code>/<code>ETikTitleDownload</code>: Lists all owned eShop tickets / downloads all tickets / downloads the titles attached to all tickets, respectively, from the given console's eShop account.

==Installation==

Instructions for installation & setup are {{GitHub|luigoalma/cleaninty#Installing|on the GitHub page}}, but the installation instructions may need to be interpreted for your OS.

Regardless of your OS, you will need a 3DS with both custom firmware and [[3DS:GodMode9|GodMode9]] installed to dump all of the files required to do <code>SetupConstants</code>. The vast majority of them are dumped using [https://raw.githubusercontent.com/luigoalma/cleaninty/master/gm9scripts/ExtractSystemElements.gm9 ExtractSystemElements.gm9], but the [[wikipedia:Advanced_Encryption_Standard|AES]] Constant "C" is found using the full set of instructions [https://3ds.goombi.fr/convertMii/0x31.html on this page].

{{critical|The AES Constant, along with all other constants used by cleaninty, are copyrighted data. Obtaining them from your own console(s) is fine, but '''do not''' share the constants with anyone else.}}
{{info|These constants are the same on all consoles. Once one set is dumped, you will not need to redump in the future unless you lose access to them.}}
===Windows===

Don't bother trying to install cleaninty on Windows directly. Windows has OpenSSL disabled in its <code>curl.exe</code>, but cleaninty requires OpenSSL to function. Working around this issue manually is obnoxious and not worth the time spent.

Instead, there are two options:
#Install a Linux distro through [https://learn.microsoft.com/en-us/windows/wsl/install WSL] and then install cleaninty inside the WSL instance using the macOS/Linux instructions. (This is the simpler path, and WSL is useful for many other things. If you choose this instead of msys2, it is recommended that you also install the {{GitHub|microsoft/terminal|Windows Terminal}}.)
#Install [https://www.msys2.org/ msys2] and then install cleaninty inside the msys2 instance using the below instructions.

To install cleaninty inside msys2, open the terminal <code>mingw64.exe</code> that is inside the msys2 installation folder, then run the following two commands one at a time:
*<code>pacman -Syu mingw-w64-x86_64-python mingw-w64-x86_64-python-defusedxml mingw-w64-x86_64-python-cryptography mingw-w64-x86_64-python-pycurl</code>
*<code>python -m pip install cleaninty</code>

Once this is completed, from here on out you will need to open the msys2 <code>mingw64.exe</code> terminal to use cleaninty.

{{info|Be aware that when using cleaninty through msys2, the place it will look in to find <code>boot9.bin</code>, <code>SSLCertificates</code>, and <code>ctr_constants.json</code> is a folder named <code>3ds</code> inside your msys2 <code>home</code> folder.}}

===macOS and Linux===

First, ensure you have Python 3.7 or newer. You can check if your Python version is new enough by opening a terminal and running the command <code>python3 --version</code>. If you do not, install a compatible version from either your package manager or [https://www.python.org/downloads/ the Python website].

Then, either install cleaninty directly from <code>pip</code> or clone its repo via the command <code>git clone https://github.com/luigoalma/cleaninty.git</code> and then run the <code>setup.py</code> script. Installing directly from <code>pip</code> will install an outdated but functional version of cleaninty.

By default, the latest version of cryptography will be installed, which does not work with cleaninty. You should install the latest compatible version, 43.0.3, with <code>pip</code>.

==Usage==
{{critical|Make sure the files for all consoles you compile into a json are accurate before using them in cleaninty, or else the commands may affect a different console than they "should be" affecting (or simply fail outright).

The easiest way to do this is by checking the serial sticker(s) on the console against the copy of the serial in [[3dbrew:Nandrw/sys/SecureInfo_A|SecureInfo_A]]. 
If none of the stickers agree with the SecureInfo, also check against the copy in [[3dbrew:Twln/sys/log/inspect.log|inspect.log]] and make sure its listed MAC Address matches the one within firmware by booting the console normally and going into '''System Settings -> Internet Settings -> Other Information -> Confirm MAC Address'''.}}

There is no graphical interface for cleaninty. All commands are ran through the command line.

===Manual command line===

The commands are the same on all operating systems. Run <code>cleaninty ctr (command) --help</code> for information on an individual command's syntax.

As an example, the minimum list of commands needed to set up two consoles' data and perform a SOAP transfer between them would be as follows:
#<code>cleaninty ctr GenJson --otp otp.bin --secureinfo secinfo.bin --out soap_donor.json</code>
#<code>cleaninty ctr GenJson --otp otp1.bin --secureinfo secinfo1.bin --out soap_target.json</code>
#<code>cleaninty ctr CheckReg -C soap_donor.json</code>
#<code>cleaninty ctr CheckReg -C soap_target.json</code>
#*The CheckReg commands are not necessary if you are already certain the donor and target have the same region.
#<code>cleaninty ctr EShopRegionChange -C soap_target.json -r (eShop region) -c (eShop country - not required if region is JPN/KOR/CHN)</code>
#*You can use any region/country for this command other than the one listed in the <code>soap_target.json</code>'s <code>CheckReg</code>.
#Depending on whether the EShopRegionChange was successful or not, only do '''one''' of the following commands.
<tabber>
|-|Succeeded=
<ol>
<li value="7"><code>cleaninty ctr EShopDelete -C soap_target.json</code></li>
</ol>

|-|Failed=
<ol>
<li value="7"><code>cleaninty ctr SysTransfer -s soap_target.json -t soap_donor.json</code></li>
</ol>
</tabber>

===Autosoap script===

{{warning|Although this script is far simpler to use than manually inputting commands, errors may still occur during edge cases. Knowledge of the command line will still likely be required to debug if this occurs.}}

If you are inexperienced with the command line or just don't want to type the commands manually every time, there is a SOAP bash script made by StarlitSkies that heavily simplifies the process.

Read the instructions on its page for setup and usage.

[[Category:Nintendo 3DS guides]]

User:ManiacOfHomebrew

2026-02-04T02:24:29Z

ManiacOfHomebrew:

Hello. I like cubes with derpy faces and stuff. Here's some of that stuff:

[[User:ManiacOfHomebrew/3DS 12-hour Clock|3DS 12-hour clock]] - In case you're 'murican! (Or any other country that has a 12-hour clock I guess)

[[3DS:Alternate Exploits/Installing boot9strap (MSET9-ChromeOS)|Installing boot9strap (MSET9-ChromeOS)]] - Pretty much only for Chromebooks that can't use Android for some reason.

[[User:ManiacOfHomebrew/Installing boot9strap (MSET9-GM9)|Installing boot9strap (MSET9-GM9)]] - I really have no idea why you would ever use this.

[https://skater.nintendohomebrew.com super-skaterhax AIO generator] - Used on the [[3ds-guide:installing-boot9strap-(super-skaterhax)|guide]]! ([https://maniacofgithub.github.io/super-skaterhax-site/ Mirror because ISPs hate this site for some reason])

User:ManiacOfHomebrew/Installing boot9strap (MSET9-ChromeOS)

2026-02-04T02:19:40Z

ManiacOfHomebrew: Changed redirect target from 3DS:Installing boot9strap (MSET9-ChromeOS) to 3DS:Alternate Exploits/Installing boot9strap (MSET9-ChromeOS)

#REDIRECT [[3DS:Alternate Exploits/Installing boot9strap (MSET9-ChromeOS)]]

3DS:Alternate Exploits/Installing boot9strap (MSET9-ChromeOS)

2026-02-04T02:18:02Z

ManiacOfHomebrew: ManiacOfHomebrew moved page 3DS:Installing boot9strap (MSET9-ChromeOS) to 3DS:Alternate Exploits/Installing boot9strap (MSET9-ChromeOS)

==Required Reading==
This is an alternative to the normal MSET9 Play Store guide that ChromeOS and Android devices would normally use. This version ports over the new features of MSET9 v2.0 and features a script that looks far more similar to the one used in the MSET9 CLI guide.

==Compatibility Notes==
{{Warning|text=This script is only compatible with Chromebooks and other devices running ChromeOS. If you are on a Windows, Mac, or Linux device, you should follow the [https://3ds.hacks.guide/installing-boot9strap-(mset9-cli).html MSET9 CLI guide] instead. If you are on an Android device, you should follow the [https://3ds.hacks.guide/installing-boot9strap-(mset9-play-store).html MSET9 Play Store guide] instead. If you do not have access to any of these devices, you will need to use an [[3DS:Alternate Exploits|alternate exploit]].}}

==What You Need==

*The latest version of [https://github.com/hacks-guide/MSET9/releases/latest MSET9]

==Instructions==
{{Info|text=On this page, you will use the MSET9-ChromeOS script, which is used to trigger MSET9. While the script is in progress, user data will temporarily disappear but will return upon the completion of this page. If you get an error when running the script, please join {{ml|Get support|Nintendo Homebrew on Discord}} and ping <code>@_themaniac</code> for assistance.}}

===Section I - Prep Work===
In this section, you will prepare the MSET9 exploit by temporarily creating a new HOME Menu profile with no user data, and then setting up that profile with only the minimum data required for MSET9 to trigger. Your existing user data will disappear, but will come back when you are finished with this page.

#Insert your SD card into your Chromebook
#Open the MSET9 <code>.zip</code> file from your Downloads folder, and copy everything inside to the root of your SD card
#*Before copying, ensure that none of the files inside the ZIP are already on the SD card. If they are, delete them
#Go to [https://maniacofgithub.github.io/mset9-chromeos/ this website] and click "Copy!" to copy the script to your clipboard
# Open the ChromeOS Files application by pressing {{B|Alt|Shift|M}} on your keyboard
#Select your SD card on the sidebar on the left in the Files application
#Open the DevTools Console for the Files application by pressing {{B|Ctrl|Shift|J}} on your keyboard
#*You may want to maximize this window to make it easier to read
#*Do not close this window or the Files application until you are told to do so
#Click to the right of the right arrow on the left side of this menu. Your cursor should start blinking
#Press {{B|Ctrl|V}} to paste the code then push Enter to run the MSET9-ChromeOS script
#*If you see a warning about not pasting code into the console that you do not understand, type <code>allow pasting</code> and then push Enter. Then, retry this step
#*This script does not contain malware, sends no data to any server, and does not even require an internet connection. If you wish, you can read the code on the site where you copied it from to verify this
#Type the characters corresponding to your console model and version, then press Enter
#*Ensure that the correct console model and version is displayed
#Type <code>a</code>, then press Enter to begin the process of creating the MSET9 ID1
#After reading the disclaimer, type <code>a</code> again and press Enter to accept it
#*If you see the message "Created hacked ID1.", you are ready to continue the guide
#*Your 3DS will appear to have no data / no user-installed apps on HOME Menu. '''This is expected.''' Your data will come back at a later step
#Eject the SD card from the Chromebook, either by typing <code>eject</code> into the DevTools Console or by selecting the eject icon in the Files app
#Reinsert your SD card into the console
#Power on your console
#Open Mii Maker
#Wait for your console to reach the [[3ds-guide:images/screenshots/mset9/mii-welcome.png|Welcome to Mii Maker]] screen, then exit Mii Maker and return to the HOME Menu
#*You may see [[3ds-guide:images/screenshots/mset9/mii-extdata.png|this screen]], which indicates the necessary data has been created
#*If you just reach the [[3ds-guide:images/screenshots/mset9/mii-existing.png|normal]] Mii Maker screen, then the data already exists. Exit Mii Maker and return to the HOME Menu
#Launch System Settings and navigate to <code>Data Management</code> -> <code>Nintendo 3DS</code> -> <code>Software</code> -> <code>Reset</code> ([[3ds-guide:images/screenshots/database-reset.jpg|image]])
#*This will not wipe any of your data
#Power off your console by pressing the power button then tapping Power Off on the lower screen
#Insert your SD card into your Chromebook
#Select your SD card on the sidebar on the left in the Files application
#In the DevTools Console window, type <code>restart</code> and press Enter to run the MSET9-ChromeOS script
#*If you closed the Files window or the DevTools Console window, this will not work
#*Instead, you should redo Section I Steps 3 through 8
#Type the characters corresponding to your console model and version, then press Enter
#*The window should change to this and display <code>Ready</code>
#**(Image coming soon)
#*If the window says <code>Not ready - check MSET9 status for more details</code>:
#**Type <code>b</code>, then press Enter to check the MSET9 status and follow the directions indicated
#**Once you have resolved the issue, return to Section I Step 19
#Type <code>z</code>, then press Enter to close the script
#*Do not close the window
#Eject the SD card from the Chromebook, either by typing <code>eject</code> into the DevTools Console or by selecting the eject icon in the Files app
#Reinsert your SD card into your console

===Section II - MSET9===
In this section, you will trigger MSET9 to launch SafeB9SInstaller (the custom firmware installer).
{{Warning|text=These instructions must be followed '''EXACTLY''', so double-check EVERYTHING you are doing to avoid errors!}}
#Power on your console, ensuring System Settings is selected
#*If System Settings is not selected, [[3ds-guide:images/screenshots/mset9/hover-settings.png|hover over]] the System Settings icon using the D-Pad, power your console off, then back on
#Press {{B|A}} to launch System Settings
#Navigate to <code>Data Management</code> -> <code>Nintendo 3DS</code> -> <code>Extra Data</code> ([[3ds-guide:images/screenshots/mset9/settings-extdata.png|image]])
#'''Do not press any buttons or touch the screen'''
#'''With the console STILL ON, and without pressing any buttons or touching the screen,''' remove your SD card from your console
#*The menu will refresh and say that no SD card is inserted
#Insert your SD card into your Chromebook
#Select your SD card on the sidebar on the left in the Files application
#In the DevTools Console window, type <code>restart</code> and press Enter to run the MSET9-ChromeOS script
#*If you closed the Files window or the DevTools Console window, this will not work
#*Instead, you should redo Section I Steps 3 through 8
#Type the characters corresponding to your console model and version, then press Enter
#In the DevTools Console window, type <code>c</code>, then press Enter to inject MSET9
#*You should see "MSET9 successfully injected!"
#Eject the SD card from the Chromebook, either by typing <code>eject</code> into the DevTools Console or by selecting the eject icon in the Files app
#Reinsert your SD card into your console '''without pressing any buttons or touching the screen'''
#If the exploit was successful, you will have booted into SafeB9SInstaller

===Section III - Installing boot9strap===
In this section, you will install custom firmware onto your console.
#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, [[3ds-guide:troubleshooting-mset9.html|follow this troubleshooting guide]]
#Once it is complete, press {{B|A}} to reboot your console
#Your device 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 your device shuts down when you try to power it on, ensure that you have copied <code>boot.firm</code> from the MSET9 <code>.zip</code> to the root of your SD card
#Press (Start) to save and reboot

===Section IV - Removing MSET9===
In this section, you will remove MSET9 to prevent further issues and to restore your user data (games, themes, etc). (This will not remove the custom firmware that you have just installed.)
{{Warning|text=Do NOT skip this section! If you skip it, applications may crash unexpectedly and you will encounter errors on the next page!}}
#Power off your console
#Insert your SD card into your Chromebook
#Select your SD card on the sidebar on the left in the Files application
#In the DevTools Console window, type <code>restart</code> and press Enter to run the MSET9-ChromeOS script
#*If you closed the Files window or the DevTools Console window, this will not work
#*Instead, you should redo Section I Steps 3 through 8
#Type the characters corresponding to your console model and version, then press Enter
#*The current state should display <code>Injected</code>
#*If you have already removed the trigger file (or never injected in the first place), the current state will show <code>Ready</code>, skip to Step 7
#Type <code>d</code>, then press Enter to remove the trigger file
#*You should see "Removed trigger file."
#Type <code>e</code>, then press Enter to remove MSET9
#*You should see "Successfully removed MSET9!"
{{Info|text=You can '''now''' close the DevTools Console window and the Files application.}}
At this point, your console will boot to Luma3DS by default.

*Luma3DS does not look any different from the normal HOME Menu. If your console has booted into the HOME Menu, it is running custom firmware.
*On the next page, you will install useful homebrew applications to complete your setup.
-----

{{Warning|text=Did you follow Section IV (Removing MSET9)? That section is MANDATORY!}}
Continue to [[3dsguide:finalizing-setup|Finalizing Setup]]

User:ManiacOfHomebrew/Installing boot9strap (MSET9-ChromeOS)

2026-02-04T02:16:50Z

ManiacOfHomebrew: ManiacOfHomebrew moved page User:ManiacOfHomebrew/Installing boot9strap (MSET9-ChromeOS) to 3DS:Installing boot9strap (MSET9-ChromeOS): Upgraded to 3DS namespace by popular demand

#REDIRECT [[3DS:Installing boot9strap (MSET9-ChromeOS)]]

3DS:Alternate Exploits/Installing boot9strap (MSET9-ChromeOS)

2026-02-04T02:16:49Z

ManiacOfHomebrew: ManiacOfHomebrew moved page User:ManiacOfHomebrew/Installing boot9strap (MSET9-ChromeOS) to 3DS:Installing boot9strap (MSET9-ChromeOS): Upgraded to 3DS namespace by popular demand

3DS:Missing Titles

2025-12-10T20:54:56Z

ManiacOfHomebrew: fix typo

3DS titles can appear to vanish from the HOME Menu for several different reasons. This page provides recommended solutions based on what appears in System Settings → Data Management → Nintendo 3DS → Software.

{{info|text=This issue does not affect anything
installed as DSiWare, including TWiLightMenu++ and games forwarded via nds-forwarder.}}

== On the 3DS, Going to System Settings → Data Management → Nintendo 3DS → Software results in...==

==='''Titles with gray X's on them:'''===
Install and run [[3DS:Faketik|Faketik]].

==='''A Popup Reading "The microSD/SD card software management information is corrupted. Reset it now?":'''===
If you have any games or saves you'd like to keep, [[3DS:Rebuild title database|rebuild your Title Database]]. If you do not care about your current data, you can hit "Reset", which will erase the contents of your SD Card, rendering your current games and saves unusable and you can reinstall your apps afterwards.

==='''A Popup Reading "No microSD/SD card Found" and/or your installed custom theme is gone:'''===
Your SD Card is not being read by your console. Ensure it is properly inserted into the console. If it is, backup the contents of your SD Card to a computer or phone, [[Formatting an SD card|reformat the SD Card]], then [[Checking SD card integrity|test its integrity]].

=== '''A Popup Reading "Could not access microSD/SD card":''' ===
Your SD Card is not formatted to FAT32. Ensure to [[Formatting an SD card|properly format it]].

=== '''A Popup Reading "There is no available software data":''' ===
Your console is able to read your SD card but it could not find any software data.

# Insert your SD card into your computer
# Open the <code>Nintendo 3DS folder</code>, if you see multiple <code>id0</code> (32 characters long folder), [[3DS:Troubleshooting/multiple ID0|figure out what's the correct id0]]
# Open the correct <code>id0</code>, if you see multiple <code>id1</code> (32 characters long folder), [[3DS:Troubleshooting/multiple ID1|figure out what's the correct id1]]

If that did not fix your issue, your data could have been deleted or there is an issue with one or more database files, join the {{ml|Get support|Nintendo Homebrew Discord}} for further assistance.

==='''Question marks or black boxes where game icons should be:'''===
Your SD Card is likely corrupted. Backup the contents of your SD Card to a computer or phone, [[3ds-guide:formatting-sd-(windows)|reformat the SD Card]], then [[3ds-guide:h2testw-(windows).html|test its integrity]].

==='''Titles Appear Listed Normally, But are Still Missing from Home Menu''':===
==== If this occurred after installing 300+ 3DS titles:====
Delete some games from the <code>Data Management</code> screen until you’re under 300 titles.
====If this occurred and you have less than 300 titles installed:====
Install and run [[3DS:Gm9-title-fixer|Chalenged's gm9 title fixer]].

*If you run into any issues with the above option, join the {{ml|Get support|Nintendo Homebrew Discord}} and mention that you've tried to use the title fixer script.

*Alternatively, you can manually generate a file that describes the contents of your SD, join the {{ml|Get support|Nintendo Homebrew Discord}}, and send it in the <code>#bot-cmds</code> channel for further instructions. To generate this file, you will need a Windows computer and a way to access your SD on said computer. Follow the instructions below:

#Insert your 3DS's SD card into your computer
#Navigate to the <code>Nintendo 3DS/<ID0>/<ID1>/title</code> folder on your SD
#*The ID0 and ID1 are long 32-character folders inside your <code>Nintendo 3DS</code> folder. For more help navigating your SD Card's contents, consult the [https://3ds.hacks.guide/key-information.html Key Information] Section of the 3DS Guide.
#Hold Shift and right-click on the empty space of the folder
#Click on Open Command Prompt/Terminal/Powershell, depending on which ones appear
#Type <code>tree /a /f > title.txt</code> into the terminal and then press Enter
#Close the terminal
# Upload <code>title.txt</code> to the <code>#bot-cmds</code> channel of the {{ml|Get support|Nintendo Homebrew Discord}} and follow its recommendations

[[Category:Unbricking]]
[[Category:Nintendo 3DS troubleshooting]]

3DS:Ctrcheck

2025-11-18T01:57:39Z

ManiacOfHomebrew: GM9 updated

{{Lowercase title}}{{Infobox homebrew
| title = ctrcheck
| for3ds = 1
| developers = StarlitSkies, FrozenFire
| version = 4.0
| releasedate = 2024-10-04
| github = nh-server/scripts
| releaseurl = https://raw.githubusercontent.com/nh-server/scripts/main/3DS/ctrcheck.gm9
}}

'''ctrcheck''' is a custom GodMode9 script that does a large number of [[wikipedia:Sanity check|sanity checks]] and [[wikipedia:Checksum|checksums]] on a 3DS' firmware and SD card to make troubleshooting easier through [[wikipedia:Fault isolation|fault isolation]], though it can also automatically fix certain issues.

== Required Reading ==

ctrcheck does not fix the majority of issues by itself, and instead only informs the user that they exist. Some of the issues it checks for may still require large amounts of knowledge to fix - this script is not a 'miracle cure' and should not be treated as such.

Additionally, ctrcheck cannot check whether the SD is damaged, only certain specific issues with reading its data. If you have an issue that might be caused by an SD being corrupted or formatted badly, the pages [[Formatting an SD card]] and/or [[Checking SD card integrity]] will be far more useful.

== Instructions ==

=== What You Need ===

* The latest version of [https://raw.githubusercontent.com/nh-server/scripts/main/3DS/ctrcheck.gm9 ctrcheck.gm9]
** To download, right-click/long-press the link and select <code>Save link as...</code> or similar, then rename the downloaded file to <code>ctrcheck.gm9</code> if it is not named exactly that
* A device that you can use to transfer files to your 3DS, either via an SD slot or via [[3DS:FTP|FTP]]

=== Section I - Prep Work ===

# Power off your console and insert the SD card into your device
# Copy the downloaded <code>ctrcheck.gm9</code> into <code>sd:/gm9/scripts</code> on the SD card
# If GodMode9 either is not installed or is outdated (the latest version is v2.2.1), [[3DS:GodMode9#Installation|install the latest version now]]
# Reinsert the SD card into your console

=== Section II - ctrcheck ===

# Hold {{B|START}}, and while holding {{B|START}}, power on your console. This will launch GodMode9
# Press the {{B|HOME}} button, then go into '''Scripts...''' -> '''ctrcheck'''
#* If ctrcheck does not appear here, go into the folder <code>0:/gm9/scripts</code> and manually rename it to <code>ctrcheck.gm9</code> by highlighting it and pressing {{B|R|X}}, then reopen the scripts menu
# Based on the type of issue you're having, select one of the top three options
#* If you are even slightly unsure about what type of issue it is, pick '''All'''
# Accept any prompts to fix issues and unlock sysNAND write permissions that appear, perform data recovery and rerun the script if instructed to, and then read the results on the top screen once the script is entirely finished
# If you are following this guide at someone else's request, send a copy of the results to that person. Otherwise, if the results include any of the following, do the matching instructions:
#* <code>______ installed to firm0/firm1</code>: If the result type is <code>Information</code>, you may ignore this line. If the type is <code>Warning</code> or <code>Critical</code>, follow either [[3dsguide:updating-b9s|Updating B9S]] (if using boot9strap) or [[3DS:Fastboot3DS/Usage#Updating_fastboot3DS|Updating fastboot3DS]] (if using fastboot3DS) to get the latest version of a known good bootloader. If the type is <code>Error</code> and both FIRM0 and FIRM1 are affected, ask for help in the {{ml|Get support|Nintendo Homebrew Discord}}
#* <code>Critical: NVRAM is inaccessible</code>: If your console is an old model (no ZL/ZR shoulder buttons and no C-Stick), try reseating the Wi-Fi module on the motherboard. If this does not fix it or you have a new model, download this [[Special:DownloadWithFilename/File:Luma ignore cfgnor.firm/boot.firm| special build of Luma]] and put it on the root of your SD card, replacing <code>boot.firm</code> if it already exists
#** This build does not fix the issue, only stop it from causing system crashes. You will still be unable to play DS games, and if you were unable to use Wi-Fi it will also stay broken - fixing these entirely requires a hardware replacement
#* <code>Warning: The SD title database needs to be reset</code>: Using [[3dsguide:images/screenshots/database-reset.jpg|this picture]] as a guide, reset the title database. After you reset, follow [[3dsguide:finalizing-setup|Finalizing Setup]] to reacquire the homebrew apps
#* <code>Warning: There is no boot.firm/boot.3dsx in the SD card root</code>: Follow [[3dsguide:restoring-updating-cfw|Restoring / Updating CFW]] to reacquire the file(s)
#* <code>Critical: NAND is unreadable at _______...?</code>: Your console's internal storage is damaged in a way that may require advanced troubleshooting to fix. Ask for help in the {{ml|Get support|Nintendo Homebrew Discord}}
#* One or more of movable.sed, LFCS, SecureInfo, and/or HWCAL is marked as either <code>invalid</code> or <code>still invalid after a recovery attempt</code>: If you have a NAND backup from before this happened, [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|restore it]]. If you do not, then ask for help in the {{ml|Get support|Nintendo Homebrew Discord}}
#* <code>Critical: n3DS has an o3DS NAND header</code>: If you have a NAND backup from before this happened, [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|restore it]]. If you do not, then ask for help in the {{ml|Get support|Nintendo Homebrew Discord}}
# If any other result(s) of the type <code>Warning</code>, <code>Critical</code>, or <code>Error</code> appear, you may want to ask for help in the {{ml|Get support|Nintendo Homebrew Discord}} and provide the full output of ctrcheck there
{{info|text=The results found on the top screen are also stored on the SD card in the file <code>sd:/gm9/ctrcheck_latest.txt</code> - however, if you run ctrcheck again, that file will be overwritten with the new results. To avoid this, enabling permanent logging will also append the results to the file <code>sd:/gm9/ctrcheck_log.txt</code>.}}

[[Category:Unbricking]]
[[Category:Nintendo 3DS troubleshooting]]

3DS:Export saves

2025-09-10T03:04:59Z

ManiacOfHomebrew: update this page a little bit

{{Page WIP}}
This page details how to backup and restore save data on the 3DS.

The Nintendo 3DS stores save data in the following ways:
*'''Cartridges''' ''usually'' have a place on the cartridge itself to save their data. This means that a cartridge's save data will remain when the cartridge is used on another 3DS.
**There are a few exceptions to this. Such games will save as "extdata" (extra data) and will follow the same rules as digital games.
*'''Digital games''' save their data into a packed, encrypted format within the <code>Nintendo 3DS</code> folder. This means that in order to use your save data on another 3DS, you would need to unpack and decrypt it.
*'''Cartridges and digital games''' save ''less important'' data (for example, Pokémon battle videos and Super Smash Bros. replays) as "extdata" in a packed, encrypted format within the <code>Nintendo 3DS</code> folder. Like the save data for digital games, you would need to unpack and decrypt it in order to import it to another 3DS.

With this in mind, there are many ways to export your save files into a format that:
*Can be copied to many locations (e.g. computer, online storage, external hard drive)
*Can be used for save file editing (e.g. PKHeX, Marc Robledo's ACNL Save Editor)
*Can be used on another 3DS, or in emulators

{{warning|text=The instructions here assume that you have custom firmware. If your console is unmodified or only has homebrew access through a game like Steel Diver: Sub Wars, you should [[3dsguide:index|install custom firmware]] first.}}

=Cartridges=

Since your cartridge save data is (generally) on the cartridge, you can make your save data backups on ''any'' 3DS using homebrew applications.

There are two save managers commonly used on the 3DS: JKSM and Checkpoint. If you followed [[3dsguide:index|our guide]] to install custom firmware, you will probably already have Checkpoint installed. If not, you can get it by following the instructions [[Checkpoint#Installation|here]]. Once you have it:

#Open Checkpoint (the flag icon) through your preferred method
#Select the game you want to make a save file backup of
#*Cartridges will generally be the first title displayed on the list and will be labelled as "Media Type: Cartridge" on the bottom screen
#*The game will not show up in Checkpoint if a save file has not been created in the game
#*If you are having issues getting the game to show up, try holding {{B|B}} to refresh Checkpoint
#Press the {{B|L}} button to back up the save file for the game
#*The save file name can be anything, but setting it as the date makes it easy to identify when the save file was created

{{success|text=You're done! The save file will be output to <code>/3ds/Checkpoint/saves/<game name>/<folder name from earlier></code>.}}

=Digital games and extdata=

==If your 3DS is working==

If your 3DS is currently reasonably functional (as in, you can reasonably navigate through all the menus), you can make your save data backups on the 3DS itself using homebrew applications.

There are two save managers commonly used on the 3DS: JKSM and Checkpoint. If you followed [[3dsguide:index|our guide]] to install custom firmware, you will probably already have Checkpoint installed. If not, you can get it by following the instructions [[Checkpoint#Installation|here]]. Once you have it:

#Open Checkpoint (the flag icon) through your preferred method
#Select the game you want to make a save file or extdata backup of
#*The game will not show up in Checkpoint if a save file has not been created in the game
#*If you are having issues getting the game to show up, try holding {{B|B}} to refresh Checkpoint
#*You can press {{B|X}} to switch to backing up extdata
#Press the {{B|L}} button to back up the save file or extdata for the game
#*The save file name can be anything, but setting it as the date makes it easy to identify when the save file was created

{{success|text=You're done! The save file will be output to one of the following locations:
* <code>/3ds/Checkpoint/saves/<game name>/<folder name from earlier></code> if it is a save file
* <code>/3ds/Checkpoint/extdata/<game name>/<folder name from earlier></code> if it is extdata}}

==If your 3DS isn't working==

If your 3DS is currently nonfunctional (as in, you can't boot to home menu and the issue cannot be fixed), you may be able to make your save data backups depending on the files you have. You'll need any of the following:
*Your NAND backup (e.g. <code>220101_AA000000000_sysnand_000.bin</code>)
*<code>essentials.exefs</code>
*<code>movable.sed</code>

If you don't have any of these files on hand, you may still be able to get your encryption key if:
*It is [https://seedminer.hacks.guide/ cached on Bruteforce Movable] (enter your Friend Code and ID0 combination to check; if it skips to Step 4 then you're good to go)
*You have (physical or non-physical) access to a 3DS that has done a two-way friend exchange to your broken console at some point [[3DS:Seedminer/Manual mining|(see here for instructions)]]
*You have a Mii QR code created with your broken console at some point [[3DS:Seedminer/Mii mining|(see here for instructions)]]
*Your broken console can still access GodMode9, whether through a [[3DS:Boot9strap|boot9strap]] installation or an [[3DS:Ntrboot|ntrboot-compatible flashcard]], such as the Ace3DS X.

Once you have your encryption key on hand, you can either:
*Import the encryption key to a working console (from which you can use Checkpoint, as above), or
*Create unpacked, decrypted save data with the help of some computer programs

===Import all SD card data to a working console===
{{warning|1=With this method, you lose access to all games/savedata/themes/DSiWare that was installed on the working console beforehand. If you have a large amount of preexisting data you would like to keep, choose another method.}}
If you would like to import all SD card data to another console, follow [[3DS:Movable Moveover|3DS:Movable Moveover]].

===Use a computer to unpack and decrypt save files (easy)===
([[ninfs]] + 3ds-save-tool)

===Use a computer to unpack and decrypt save files (hard)===
(3ds-save-tool + secrets.py)

==Things you can't or shouldn't do==

===3DS Flashcart stuff===
3DS flashcarts are not advised for [[3DS:Flashcarts#3DS Flashcarts|several reasons]], and as such will not be recommended here either.

If you use such a flashcart, the save files can likely be imported into Checkpoint and used through there.

===Powersaves stuff===

===Official Save Data Backup feature===
Save data backed up with this feature remains encrypted and in a packed file format, so it cannot be used on another 3DS nor can it be recovered without the encryption key. Therefore, using Checkpoint is preferred.

[[Category:Nintendo 3DS guides]]

3DS:Luma3DS/Configuration

2025-08-08T16:01:23Z

ManiacOfHomebrew: Fix caps

{{hatnote|1=This article is about the Luma3DS configuration menu, accessible on boot. For information about Rosalina (the menu that is accessible when booted into HOME Menu), see [[3DS:Luma3DS/Rosalina|Luma3DS/Rosalina]].}}

The Luma3DS configuration menu is a menu that can be accessed by holding {{B|Select}} while turning on your 3DS. In the menu, you can:
* See what version of Luma3DS is currently installed
* Modify some of Luma3DS's 'optional' settings (settings that will, in general, not affect the overall functionality of your 3DS)
* See where Luma3DS is booting from

By default, [[3dsguide:index|our custom firmware installation guide]] uses the default configuration that is generated when Luma3DS is first run. This page will contain explanations for the various options contained in Luma3DS configuration so that you can make an informed decision on what options (if any) to change.

Luma3DS configuration will often be reset to default settings if:
* You change to a different version of Luma3DS
* You are switching between Luma3DS forks

Luma3DS also keeps separate configuration files for the SD card and CTRNAND (internal memory). The files' locations are <code>SD:/luma/config.ini</code> and <code>CTRNAND:/rw/luma/config.ini</code>, respectively.

==Navigating Luma3DS configuration==
{{info|If your {{B|Select}}, {{Key press|Up}}, {{Key press|Down}}, or {{B|A}} buttons are broken, you will be unable to use the Luma3DS configuration. As an alternative, you can manually modify all options that are in the Luma3DS configuration by modifying the <code>config.ini</code> file in the <code>luma</code> folder (as of Luma3DS v12.0).}}
You can access Luma3DS configuration by holding {{B|Select}} while powering on your device. 
When in the Luma3DS configuration menu, you can use the {{Key press|Up}} and {{Key press|Down}} buttons to highlight different options. Press {{B|A}} to enable, disable, or cycle through the options. The currently highlighted option will be coloured differently from the rest of the configuration menu, and an option that is currently enabled will be indicated with <code>(x)</code>. For example, <code>(x) Show NAND or user string in System Settings</code> indicates that the "Show NAND or user string in System Settings" option is enabled. 
Once you are done configuring Luma3DS, either select the '''Save and exit''' option or press the {{B|Start}} button to save your configuration. If the PIN setting is enabled, you will be told to set it; otherwise, the 3DS will immediately reboot.

==Luma3DS configuration options==

===Default===

====Screen brightness====
Changes the brightness of the Luma3DS configuration screen. Takes effect instantly.

====Splash====
Determines whether Luma3DS will attempt to display a splash screen (a custom boot image) while booting your 3DS. This option will not do anything unless you have splash images in the <code>luma</code> folder, and will not affect whether a PIN splash shows up. For more information, see [[3DS:Splash screens]].

====PIN lock====
Determines whether Luma3DS will require a PIN to be entered when powering on your device. You will be prompted to set the PIN after saving the configuration. For more information, see [[3DS:Luma3DS/PIN lock]].

====New 3DS CPU====
{{info|This option can only be used on a New 3DS/2DS.}}
When enabled, allows the New 3DS's enhanced clock speed and L2 cache to be used in all titles, not just New 3DS-exclusives. This may improve performance for some games, but it may also reveal hidden bugs in games when the Clock+L2 setting is enabled - this can result in anything up to a crash. This option is the same as the one found in the [[3DS:Luma3DS/Rosalina|Rosalina menu]].

====Hbmenu autoboot====
When enabled, automatically boots to the selected homebrew launcher instead of the HOME Menu. 
If 3DS is chosen, this will always be the normal Homebrew Launcher. 
if DSi is chosen, by default this will attempt to boot to the {{GitHub|devkitPro/nds-hb-menu/releases/latest|nds-hb-menu}} - if this is not installed, it will boot to an exception instead.

The title IDs used for each of these options can be configured in the <code>config.ini</code> file.

====Enable loading external FIRMs and modules====
When enabled, Luma3DS will load customized FIRMs and system modules (basically, for modifying non-game elements on the 3DS). This option will not do anything unless you have the necessary files in <code>luma</code> or <code>/luma/sysmodules</code>.

This option is most commonly used for the Nintendo Network replacement [[Pretendo]], or sysmodule rewrites such as [[3DS:rehid|rehid]] or [[3DS:Wumiibo|Wumiibo]].

====Enable game patching====
When enabled, Luma3DS will load modded game files. This option will not do anything unless you have any files to load, which should be placed in <code>/luma/titles/(title ID of game)</code>. 
You will often enable this option if you are planning to use game mods via LayeredFS, such as translation patches or ROM hacks. 
You will also need this option if you need to manually specify the locale for games that fail to work despite Luma3DS's region-free patch. For more information, see [[3DS:Setting game locales]].

==== Redirect app. syscore threads to core2 ====
{{info|This option can only be used on a New 3DS/2DS.}}
When enabled, Luma3DS will move some application threads to core2, which usually goes unused despite being intended for applications. This will boost performance on resource-intensive games (like Pokemon US/UM) by around 10%, but may also break some games and applications.

==== Show NAND or user string in System Settings ====
When enabled, Luma3DS will show its own (or a user-specified) version string in System Settings. For example, the default version string of an unmodded 3DS on 11.16.0-49U would be <code>Ver. 11.16.0-49U</code>. With this option enabled, the version string would instead show <code>Sys. 11.16.0-49U</code>. This serves as a decent custom firmware check, but it is not comprehensive since the option can be disabled at will.

A custom version string of up to '''19 characters''' can also be manually specified by creating a file with the custom string called <code>customversion_sys.txt</code> and putting it inside the <code>luma</code> folder.

==== Show GBA boot screen in patched AGB_FIRM ====
When enabled, Luma3DS will show the [https://www.youtube.com/watch?v=6_ZD3FxMcvQ GBA boot screen] when loading a GBA game through the built-in GBA firmware of the 3DS (such as through virtual console).

=== EmuNAND/RedNAND only ===
{{info|These options will only appear if your currently inserted SD card has an [[3DS:EmuNAND and RedNAND|EmuNAND/RedNAND]] set up. These are almost entirely unneeded by now, however, and should instead be [[3dsguide:move-emunand|moved into the SysNAND]] unless you are using them to deal with Chinese/Korean fonts.}}

==== Default EmuNAND ====
It is possible to have multiple EmuNANDs on one SD card. This option changes which one to boot into by default. If you only have one EmuNAND, this option will not do anything. 
You can also manually specify which EmuNAND to boot into by holding a certain direction on the D-Pad while powering on: {{Key press|Up}} for 1, {{Key press|Right}} for 2, {{Key press|Down}} for 3, {{Key press|Left}} for 4.

==== Autoboot EmuNAND ====
Determines whether the emuNAND will automatically boot when you turn on your 3DS without holding any buttons. If this option is disabled, you will boot into the sysNAND by default. Holding {{B|L}} when powering on will invert this logic, meaning the 3DS will boot into sysNAND even when this option is enabled (or into emuNAND if it's disabled).

== Configuration options in config.ini ==
As of Luma3DS v11.0, certain options have been moved and can only be edited in the <code>config.ini</code> file, located in both <code>SD:/luma/config.ini</code> and <code>[1]:/rw/luma/config.ini</code>. This section documents those options.

==== config_version_major, config_version_minor ====
{{warning|There is no reason to touch this option, and doing so may reset your Luma3DS configuration.}}
Luma3DS uses these lines to determine what revision of <code>config.ini</code> is being used to prevent inconsistencies between Luma3DS updates. '''Do not touch these options'''.

==== splash_duration_ms ====
Determines for how many milliseconds the splash screen should be displayed, up to 2,147,483,647 milliseconds. For more information, see [[3DS:Splash screens]].

==== autoboot_dsi_titleid ====
Determines the DSi title to boot into when <code>autoboot_3ds_homebrew</code> is set to 2. The selected title must be installed on the NAND, or it will instead crash on boot - the default app used is {{GitHub|devkitPro/nds-hb-menu|nds-hb-menu}}.

==== force_audio_output ====
Forces all audio output except for the camera shutter to go to the headphones. Because Luma3DS only directly affects NATIVE_FIRM, this will not work in DS games, GBA games, payloads such as GodMode9, or [[3DS:Safe Mode|Safe Mode]].

Due to software limitations, this will stop working temporarily if you unplug and then replug headphones. Close and reopen the screen when this happens to fix it.

=== Rosalina menu options ===
The following options can be altered in some way via the [[3DS:Luma3DS/Rosalina|Rosalina menu]].

==== hbldr_3dsx_titleid ====
The title ID that is input here will launch the Homebrew Launcher instead of whatever application is actually run. In most cases, this will be set to the Homebrew Launcher Wrapper that is installed in the guide (000400000d921e00).

==== rosalina_menu_combo ====
Determines what keys you need to press to open the Rosalina menu. By default, this is set to {{Key press|L|Down|SELECT}}. 
For example, if one of the default keys is broken, you can set it to <code>X+Y</code> to change the menu combination to {{Key press|X|Y}}.

==== plugin_loader_enabled ====
Determines if [[3DS:Game plugins/3GX|3GX plugins]] placed in <code>SD:/luma/plugins/</code> are enabled. Having this option disabled does not stop you from using [[3DS:Game plugins/PLG|PLG plugins]] with bootNTR.

==== ntp_tz_offset_min ====
Determines your timezone to set the time correctly. The value is the number of minutes your timezone is from UTC. 
For example, Eastern Standard Time (EST) is UTC-5, so the offset would be 60 * -5 = -300.

==== volume_slider_override ====
Determines the volume to set the console to, overriding the physical volume slider of the console. Because Luma3DS only directly affects NATIVE_FIRM, this will not work in DS games, GBA games, payloads such as GodMode9, or [[3DS:Safe Mode|Safe Mode]].

The value should be a number from 0 to 100, while a value of -1 will disable the volume override.

==== Screen filter options ====
All of the following options can be configured for each screen, and thus have two variables.

===== screen_filters_cct =====
Determines the Correlated Color Temperature (cct). Can be set to any integer between 1000 and 25100.

===== screen_filters_gamma =====
Adjusts the gamma of the screen. Can be set to any integer between 0 and 1411. Increasing this above 1 will make colors look more saturated.

===== screen_filters_contrast =====
Adjusts the contrast of the screen. Can be set to any integer between 0 and 255.

===== screen_filters_brightness =====
Adjusts the brightness of the screen. Can be set to any number between -1 and 1.

===== screen_filters_invert =====
If set to 1, inverts the colors of the screen.

=== Options you shouldn't touch ===
You shouldn't touch these options unless you know what you're doing.

==== autoboot_3ds_app_mem_type ====
{{warning|This option is only of interest for developers. Changing it without knowing what you are doing may result in frequent crashes.}}
When set to anything but 0, uses an alternate memory layout when <code>autoboot_3ds_homebrew</code> is set to 1.

==== use_dev_unitinfo ====
{{warning|This option will break most retail features while enabled - this includes online play, eShop, amiibo, and all retail games.}}
When set to 1, this option changes a flag in the 3DS firmware so that it thinks it is a development unit, allowing you to run development applications.

==== disable_arm11_exception_handlers ====
{{warning|This option usually does not stop errors from happening - it only makes them harder to troubleshoot.}}
When set to 1, this option disables the [[3DS:EXCEPTION|An exception occurred]] message that occurs when an application crashes, normally replacing it with a black screen or a generic error message.

==== enable_safe_firm_rosalina ====
{{info|Luma3DS should not be active in SAFE_FIRM since SAFE_FIRM is meant as a 'rescue mode' - it's relatively unlikely anything bad will happen, but don't enable this option without a specific good reason.}}
When set to 1, this option does two things:
* Allows Rosalina to function when using [[3DS:Safe Mode|Safe Mode]] (for example, if you need to take screenshots of Safe Mode or perform whatever other functions Rosalina allows)
* Suppresses the <code>0xF96183FE</code> QTM error, which notably allows the New 2DS XL to work on firmwares below 11.3.0

== Troubleshooting with Luma3DS configuration ==
The Luma3DS configuration menu contains two pieces of information that can be used for troubleshooting: the currently installed Luma3DS version and the location from which Luma3DS is booting. 
If you are starting on a new SD card or upgrading from an old (2017 or older) custom firmware setup, you can follow the instructions [[3dsguide:checking-for-cfw|here]] to find out the correct course of action. 
As of Luma3DS v9.0, the location from which Luma3DS is booting will be displayed in yellow on the bottom screen. The following lines are known to be possible:
* Booted from SD via B9S
** Indicates that Luma3DS is being booted from the <code>boot.firm</code> file on the root of your SD card (or wherever else on the SD you may have it configured if you are using fastboot3DS).
* Booted from CTRNAND via B9S
** Indicates that Luma3DS is being booted from the <code>boot.firm</code> file on the root of SYSNAND CTRNAND (or wherever else on SYSNAND CTRNAND you may have it configured if you are using fastboot3DS). If an SD card is inserted and you still see this message, one of three things is possible: 1. you are missing <code>boot.firm</code> from the root of your SD card, 2. your SD card isn't being read, or 3. you have configured fastboot3DS to try to boot from Luma on the CTRNAND before trying the SD.
* Booted from SD via B9S (ntrboot)
** Indicates that Luma3DS is being booted from the <code>boot.firm</code> file on the root of your SD card, but that you are running B9S via ntrboot. If you're trying to install CFW, you should instead use SafeB9SInstaller as your <code>boot.firm</code> file.
* Booted from SD via FIRM0 or FIRM1
** Indicates that Luma3DS has been installed to your FIRM partitions (where boot9strap or fastboot3DS would normally go). This is known to break some custom firmware functions, so unless you intended to do this, you should [[3DS:Luma3DS to boot9strap|follow these instructions]] to install boot9strap to your FIRM partitions.
* Booted from CTRNAND via FIRM0 or FIRM1
** Indicates that Luma3DS has been installed to your FIRM partitions and that the SD is not being read. You will need a usable SD card if you wish to install boot9strap to your FIRM partitions as above, so [[Formatting_an_SD_card|try to fix that first by reformatting]] - if this does not work, your SD may be corrupted and should [[Checking_SD_card_integrity|be tested for errors.]]

[[Category:Nintendo 3DS guides]]
[[Category:Nintendo 3DS information]]

3DS:Installing software

2025-08-05T03:38:29Z

ManiacOfHomebrew: Remove Citra and correct formatting

{{shortcut|3DS:IS}}

This page details how installing software/homebrew works on the 3DS.

==3DS software formats==
Software on the 3DS comes in two main formats: '''CIA''' and '''3DSX'''.

*'''CIA''' <code>.cia</code> format software is usually installed with [[3DS:FBI|FBI]]/[[3DS:GodMode9|GodMode9]] and will end up on HOME Menu as a launchable title. Both homebrew and retail game dumps are available in the '''CIA''' format.
*'''3DSX''' <code>.3dsx</code> format software is installed by placing the 3DSX file in the <code>3ds</code> folder (NOT <code>Nintendo 3DS</code>) and can only be launched from Homebrew Launcher. All '''3DSX''' format software is homebrew.

No format is inherently better than the other; it just depends on how you want to launch your software. If you'd prefer your application on HOME Menu, '''CIA''' format is the way to go. Otherwise, '''3DSX''' is probably better.

There is also '''NDS''' <code>.nds</code> format software, which can only be used with [https://wiki.ds-homebrew.com/twilightmenu/installing-3ds TWiLightMenu++]/nds-bootstrap and can be launched by placing the <code>.nds</code> file anywhere on the SD card visible to TWiLightMenu++. This format of homebrew is also compatible with the DSi and with DS flashcarts. Alternatively, you can create a forwarder that points to the <code>.nds</code> file on your SD card, which will show up on your HOME Menu. For instructions, see [https://wiki.ds-homebrew.com/ds-index/forwarders here].

{{Warning|text=The 3DS HOME Menu has a limit of 300 3DS titles and 40 DSiWare titles. The '''3DS''' title limit can be bypassed with [[3DS:3DSBank|3DSBank]]. The '''DSiWare''' limit itself cannot be bypassed, but if you are primarily installing <code>.nds</code> forwarders, you can use [https://github.com/YANBForwarder/YANBF YANBF] to make use of the 3DS title limit.|}}

Some other file formats you might encounter (but not as often):

*'''3DS''' <code>.3ds</code> is used for cartridge dumps, which you can make/install using [[3DS:Dump titles and game cartridges|GodMode9]]. This file format is also often used by emulators.
*'''CXI''' <code>.cxi</code> is a generic executable format sometimes used for digital file dumps / preservation.
*'''APP''' <code>.app</code> is the packed application format that you will see in the <code>Nintendo 3DS</code> folder. You won't be able to directly manipulate these very easily.

In summary, if you want to install software on your 3DS, you should be looking for '''CIA''' or '''3DSX''' format applications — and sometimes '''NDS''' files.

==Installing .cia files==

There are 3 applications that are typically used to install 3DS software and homebrew:
<tabber>

|-|FBI=


[[3DS:FBI|FBI]] is an application that can install '''CIA''' files. To use it:

<ol>
<li>Place your <code>.cia</code> file anywhere on your SD card. (You may want to create a <code>cias</code> folder for organizational purposes.)</li>
<li>Open the FBI application (if you followed 3ds.hacks.guide, it will be on your HOME Menu)</li>
<li>Navigate to SD Card -> (wherever you put the <code>.cia</code> file)</li>
<li>Navigate to <code>Install and delete CIA</code>
<ul><li>The '''CIA''' file itself does not need to be kept after it is installed, hence "Install and delete"</li></ul>
</li>
<li>Wait for the '''CIA''' to install</li>
</ol>

Once the install has finished, close FBI and the application should appear as a gift box to open on your HOME Menu. If it doesn't immediately appear, you may have to power your console off and on to get it to appear.


|-|GodMode9=


[[3DS:GodMode9|GodMode9]] is an application that can install '''CIA''' files. To use it:

<ol>
<li>Place your <code>.cia</code> file anywhere on your SD card. (You may want to create a <code>cias</code> folder for organizational purposes.)</li>
<li>Power on your 3DS while holding {{B|Start}}</li>
<li>Navigate to <code>[0:] SDCARD</code> and press {{B|A}}</li>
<li>Navigate to the location of the <code>.cia</code> file you want to install, then press {{B|A}}</li>
<li>Navigate to <code>CIA Image Options...</code> and press {{B|A}}</li>
<li>Navigate to <code>Install game image</code> and press {{B|A}}</li>
<li>Unlock write permissions if prompted</li>
<li>Wait for the CIA to install</li>
<li>Press {{B|A}} when <code>Install success</code> appears</li>
<li>Relock write permissions if prompted</li>
</ol>

Once the install has finished, reboot your console by pressing {{B|Start}}


|-|Universal-Updater=


If you followed 3ds.hacks.guide to install custom firmware on your 3DS, you probably also have [[3DS:Universal-Updater|Universal-Updater]], which can be used as a homebrew app store. To use it:

<ol>
<li>Open the Universal-Updater application (the blue down arrow icon)</li>
<li>Use the <code>D-Pad</code> to navigate between applications and the {{B|A}} button to select an application</li>
<li>Use the <code>Search</code> or <code>Filter</code> function (the magnifying glass) to look for a specific application</li>
<li>Under <code>Available Downloads</code>, select either the <code>.cia</code>, <code>.3dsx</code>, or <code>.nds</code> file, then press {{B|A}} again to install the application</li>
<li>Check the queue (the button with the number in it) to see download progress
<ul>
<li>'''CIA''' files will appear on your HOME Menu in a gift box after you exit Universal-Updater</li>
<li>'''3DSX''' files will become available in the Homebrew Launcher application</li>
<li>'''NDS''' files will need to be launched from [https://wiki.ds-homebrew.com/twilightmenu/installing-3ds.html TWiLightMenu++]</li>
</ul></li>
</ol>

Once the install has finished, press {{B|Start}} to exit the application, if you installed a '''CIA''' file and it doesn't immediately appear, you may have to power your console off and on to get it to appear.


</tabber>

==Running .3dsx files==
To run a piece of homebrew in <code>.3dsx</code> format:

# Place your <code>.3dsx</code> file in the <code>3ds</code> folder (NOT <code>Nintendo 3DS</code>) on your SD card
#*Some pieces of homebrew may require additional support files. You may have to consult the README / documentation of that software if this is the case
#The homebrew should now appear in the list of homebrew that appears when you open the Homebrew Launcher (the blue "h" icon) on your HOME Menu
#*Navigate between homebrew applications / folders using the D-Pad and press the {{B|A}} button to launch it

==Reinstalling software from the eShop==
See [https://en-americas-support.nintendo.com/app/answers/detail/a_id/607/~/how-to-download-or-redownload-content-in-nintendo-3ds-eshop this] page to redownload content from the 3DS eShop.

==Uninstalling software==

See [[3DS:Uninstalling software]].

[[Category:Nintendo 3DS guides]]

User:ManiacOfHomebrew/Manual System Transfer

2025-07-08T23:13:37Z

ManiacOfHomebrew: Start work on this guide

== Required Reading ==
This guide allows you to perform a system transfer without the need for the official System Transfer tool in System Settings. This guide is separated into 3 parts, with each subsequent part transferring (arguably) less important information while being increasingly more difficult. You should typically only use this guide in these scenarios:

* The source console ("old console") is damaged in a way that it cannot access System Transfer.
* You need to transfer from a New 3DS to an Old 3DS (For Old 3DS to New 3DS, you should use the official method)
* One of the consoles is a different region than the other, and [https://en-americas-support.nintendo.com/app/answers/detail/a_id/74/~/how-to-delete-a-nintendo-eshop-account deleting the eShop account] before region changing (or running [https://github.com/luigoalma/nimregion/releases nimregion] in the Homebrew Launcher after region changing) did not fix access to the eShop.

User:ManiacOfHomebrew/3DS 12-hour Clock

2025-05-04T03:39:52Z

ManiacOfHomebrew: typo

{{#approvable_by: users = ManiacOfHomebrew}}
{{Page WIP|notes=*I want to expand this to include AM/PM indicators, but I'm not sure if it'll be possible.
*In addition, I would like this to work across all applets, but that will take some time to flesh out.}}

==Required Reading==
The 3DS uses the 24-hour time format to display the time on the HOME Menu among other applets. This guide shows you how to convert the 3DS system's clock on the HUD of the HOME Menu to a 12-hour format.

{{Info|text=This will not affect other applets such as System Settings or the Nintendo eShop at the moment, meaning you will only see a 12-hour clock on the HOME Menu.}}{{Info|text=The clock will display in Japanese 12-hour time, which means that 12:00 (both midnight and noon) will be displayed as 0:00. All other hours of the day function as expected.}}
{{Warning|text=There have been reports that using custom HOME menu modifications via LayeredFS in Luma can randomly cause the system to crash when returning to the HOME menu from a game. Until this issue is fixed, a patched CIA is the recommended way to use this modification.}}

==What You Need==

*The latest version of [https://github.com/schrmh/HMRT Home Menu Rebuilding Tool]
** To download, click the green code button, and then Download ZIP.
*The latest version of [https://github.com/IcySon55/3DLandMSBTeditor/releases MSBT Editor Reloaded]
*The latest version of [[3DS:GodMode9/Usage#Updating GodMode9|GodMode9]] installed
*A computer running Windows, or Wine for Mac/Linux (Required to run MSBT Editor)

==Instructions==
{{info|text=In this guide, <code><Your language></code> is to be substituted with your consoles language selection. For example, <code>US_English</code>.}}
===Section I: Prep Work===

#Extract Home Menu Rebuilding Tool as well as MSBT Editor Reloaded to a new folder on your computer
#Press and hold {{Key press|Start}}, and while holding {{Key press|Start}}, power on your console. This will launch GodMode9
#Press {{Key press|HOME}} to bring up the action menu
#Select "Title manager"
#Select "[1:] NAND / TWL"
#Scroll down through the list and select a title labeled <code>(CTR-N-HMME)</code>. This is the HOME Menu application
#Select "Manage Title..."
#Select "Build CIA (standard)"
#Push {{Key press|A}} once it is finished
#Push {{Key press|R|Start}} to power off the console
#Insert the SD Card into your computer
#Backup the <code>.cia</code> file in the <code>gm9/out</code> folder to a safe place on your computer. It ends with <code>(CTR-N-HMME).standard.cia</code>
#Make another copy of this <code>.cia</code> file in the folder created in step 1
#Rename it to <code>HomeMenu.cia</code>
#Copy <code>HomeMenu.cia</code> to the Home Menu Rebuilding Tool folder

===Section II - Modifying===

*Open <code>HMRT.bat</code>
*Push {{Key press|1}} on your keyboard to extract the components of the Home Menu
*Push {{Key press|5}} on your keyboard to decompress the components
*Keep the window open and open <code>MsbtEditor.exe</code>
*Drag the file named <code>hud_msbt.LZ</code> from <code>ExtractedRomFS/message_hud/<Your language></code> into MsbtEditor
*Scroll down and select <code>lau_hours</code> in the list on the left
*Change <code>%H</code> to <code>%h</code> in the first text box labeled "Edit:"
*Push {{B|Ctrl|S}} to save, then close MsbtEditor

===Section III - Installing===
<tabber>
|-|Patched CIA (Recommended)=

{{Warning|text=Read this box closely!
*This method makes direct edits to your system HOME Menu.
*Create/update your NAND backup! When making changes to your device, there is always the chance you will brick.
*Having a custom HOME Menu installed breaks system updates. If you want to update your system, you will have to restore your HOME Menu with a blank <code>HomeMenu.cia</code> first.}}

# In the Home Menu Rebuilding Tool window, push {{Key press|6}} on your keyboard to recompress the components
# In the Home Menu Rebuilding Tool window, push {{Key press|2}} on your keyboard to rebuild the HomeMenu CIA.
# Copy the outputted <code>HomeMenu_edited.cia</code> file to the root of the SD card
# Press and hold {{Key press|Start}}, and while holding {{Key press|Start}}, power on your console. This will launch GodMode9
# Navigate to the <code>[0:] SDCARD</code> drive, then select the <code>HomeMenu_edited.cia</code> file
# Select "CIA Image options..."
# Select "Encrypt file (...)"
# Select "Encrypt inplace"
# After it is finished, push {{Key press|A}} to continue
# Select the <code>HomeMenu_edited.cia</code> file again
# Select "CIA Image options..."
# Select "Install game image"
# Press {{Key press|A}} to unlock SysNAND (lvl1) writing, then input the key combo given
# Push {{Key press|A}} twice then {{Key press|Start}} to reboot

{{success|text=The HOME Menu's clock should now be displaying 12-hour time.}}

|-|Luma LayeredFS=

[[File:USEnglish12HourTime.png|thumb|The file structure for a US_English 12-hour time patch file.]]
#In the Home Menu Rebuilding Tool window, push {{Key press|6}} on your keyboard to recompress the components
#Close the Home Menu Rebuilding Tool window.
#On your 3ds SD Card, create the following folder corresponding to your region:
*JPN: <code>luma/titles/0004003000008202/romfs</code>
*USA: <code>luma/titles/0004003000008F02/romfs</code>
*EUR: <code>luma/titles/0004003000009802/romfs</code>
*CHN: <code>luma/titles/000400300000A102/romfs</code>
*KOR: <code>luma/titles/000400300000A902/romfs</code>
*TWN: <code>luma/titles/000400300000B102/romfs</code>
<ol start="4">
<li>Create the <code>message_hud/<Your language></code> folder inside the <code>romfs</code> folder.</li>
<li>Copy <code>hud_msbt_LZ.bin</code> from <code>ExtractedRomFS/message_hud/<Your language></code> to the new folder.</li>
<li>Eject your SD Card and put it back in the console.</li>
<li>Start your device and hold SELECT to enter the Luma3DS configuration screen</li>
<li>Press (A) on <code>( ) Enable game patching</code> to tick it (if it is not already ticked) <code>(x)</code></li>
<li>Press <code>START</code> to boot the the HOME Menu</li>
</ol>
{{success|text=The HOME Menu's clock should now be displaying 12-hour time.}}
</tabber>

{{info|text=If the HOME menu does not boot or you encounter any other problem, it is recommended that you ask for help on the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord server] in one of the 3DS assistance channels, mentioning that you were following this guide.}}

User:ManiacOfHomebrew/3DS 12-hour Clock

2025-05-04T03:39:02Z

ManiacOfHomebrew: make patched cia default method until the issue is fixed

{{#approvable_by: users = ManiacOfHomebrew}}
{{Page WIP|notes=*I want to expand this to include AM/PM indicators, but I'm not sure if it'll be possible.
*In addition, I would like this to work across all applets, but that will take some time to flesh out.}}

==Required Reading==
The 3DS uses the 24-hour time format to display the time on the HOME Menu among other applets. This guide shows you how to convert the 3DS system's clock on the HUD of the HOME Menu to a 12-hour format.

{{Info|text=This will not affect other applets such as System Settings or the Nintendo eShop at the moment, meaning you will only see a 12-hour clock on the HOME Menu.}}{{Info|text=The clock will display in Japanese 12-hour time, which means that 12:00 (both midnight and noon) will be displayed as 0:00. All other hours of the day function as expected.}}
{{Warning|text=There have been reports that using custom HOME menu modifications via LayeredFS in Luma can randomly cause the system to crash when returning to the HOME menu from a game. Until this issue is fixed, a patched CIA is the recommended way to use this modification.}}

==What You Need==

*The latest version of [https://github.com/schrmh/HMRT Home Menu Rebuilding Tool]
** To download, click the green code button, and then Download ZIP.
*The latest version of [https://github.com/IcySon55/3DLandMSBTeditor/releases MSBT Editor Reloaded]
*The latest version of [[3DS:GodMode9/Usage#Updating GodMode9|GodMode9]] installed
*A computer running Windows, or Wine for Mac/Linux (Required to run MSBT Editor)

==Instructions==
{{info|text=In this guide, <code><Your language></code> is to be substituted with your consoles language selection. For example, <code>US_English</code>.}}
===Section I: Prep Work===

#Extract Home Menu Rebuilding Tool as well as MSBT Editor Reloaded to a new folder on your computer
#Press and hold {{Key press|Start}}, and while holding {{Key press|Start}}, power on your console. This will launch GodMode9
#Press {{Key press|HOME}} to bring up the action menu
#Select "Title manager"
#Select "[1:] NAND / TWL"
#Scroll down through the list and select a title labeled <code>(CTR-N-HMME)</code>. This is the HOME Menu application
#Select "Manage Title..."
#Select "Build CIA (standard)"
#Push {{Key press|A}} once it is finished
#Push {{Key press|R|Start}} to power off the console
#Insert the SD Card into your computer
#Backup the <code>.cia</code> file in the <code>gm9/out</code> folder to a safe place on your computer. It ends with <code>(CTR-N-HMME).standard.cia</code>
#Make another copy of this <code>.cia</code> file in the folder created in step 1
#Rename it to <code>HomeMenu.cia</code>
#Copy <code>HomeMenu.cia</code> to the Home Menu Rebuilding Tool folder

===Section II - Modifying===

*Open <code>HMRT.bat</code>
*Push {{Key press|1}} on your keyboard to extract the components of the Home Menu
*Push {{Key press|5}} on your keyboard to decompress the components
*Keep the window open and open <code>MsbtEditor.exe</code>
*Drag the file named <code>hud_msbt.LZ</code> from <code>ExtractedRomFS/message_hud/<Your language></code> into MsbtEditor
*Scroll down and select <code>lau_hours</code> in the list on the left
*Change <code>%H</code> to <code>%h</code> in the first text box labeled "Edit:"
*Push {{B|Ctrl|S}} to save, then close MsbtEditor

===Section III - Installing===
<tabber>
|-|Patched CIA (Recommended)=

{{Warning|text=Read this box closely!
*This method is makes direct edits to your system HOME Menu.
*Create/update your NAND backup! When making changes to your device, there is always the chance you will brick.
*Having a custom HOME Menu installed breaks system updates. If you want to update your system, you will have to restore your HOME Menu with a blank <code>HomeMenu.cia</code> first.}}

# In the Home Menu Rebuilding Tool window, push {{Key press|6}} on your keyboard to recompress the components
# In the Home Menu Rebuilding Tool window, push {{Key press|2}} on your keyboard to rebuild the HomeMenu CIA.
# Copy the outputted <code>HomeMenu_edited.cia</code> file to the root of the SD card
# Press and hold {{Key press|Start}}, and while holding {{Key press|Start}}, power on your console. This will launch GodMode9
# Navigate to the <code>[0:] SDCARD</code> drive, then select the <code>HomeMenu_edited.cia</code> file
# Select "CIA Image options..."
# Select "Encrypt file (...)"
# Select "Encrypt inplace"
# After it is finished, push {{Key press|A}} to continue
# Select the <code>HomeMenu_edited.cia</code> file again
# Select "CIA Image options..."
# Select "Install game image"
# Press {{Key press|A}} to unlock SysNAND (lvl1) writing, then input the key combo given
# Push {{Key press|A}} twice then {{Key press|Start}} to reboot

{{success|text=The HOME Menu's clock should now be displaying 12-hour time.}}

|-|Luma LayeredFS=

[[File:USEnglish12HourTime.png|thumb|The file structure for a US_English 12-hour time patch file.]]
#In the Home Menu Rebuilding Tool window, push {{Key press|6}} on your keyboard to recompress the components
#Close the Home Menu Rebuilding Tool window.
#On your 3ds SD Card, create the following folder corresponding to your region:
*JPN: <code>luma/titles/0004003000008202/romfs</code>
*USA: <code>luma/titles/0004003000008F02/romfs</code>
*EUR: <code>luma/titles/0004003000009802/romfs</code>
*CHN: <code>luma/titles/000400300000A102/romfs</code>
*KOR: <code>luma/titles/000400300000A902/romfs</code>
*TWN: <code>luma/titles/000400300000B102/romfs</code>
<ol start="4">
<li>Create the <code>message_hud/<Your language></code> folder inside the <code>romfs</code> folder.</li>
<li>Copy <code>hud_msbt_LZ.bin</code> from <code>ExtractedRomFS/message_hud/<Your language></code> to the new folder.</li>
<li>Eject your SD Card and put it back in the console.</li>
<li>Start your device and hold SELECT to enter the Luma3DS configuration screen</li>
<li>Press (A) on <code>( ) Enable game patching</code> to tick it (if it is not already ticked) <code>(x)</code></li>
<li>Press <code>START</code> to boot the the HOME Menu</li>
</ol>
{{success|text=The HOME Menu's clock should now be displaying 12-hour time.}}
</tabber>

{{info|text=If the HOME menu does not boot or you encounter any other problem, it is recommended that you ask for help on the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord server] in one of the 3DS assistance channels, mentioning that you were following this guide.}}

User:ManiacOfHomebrew

2025-04-24T03:37:29Z

ManiacOfHomebrew:

Hello. I like cubes with derpy faces and stuff. Here's some of that stuff:

[[User:ManiacOfHomebrew/3DS 12-hour Clock|3DS 12-hour clock]] - In case you're 'murican! (Or any other country that has a 12-hour clock I guess)

[[User:ManiacOfHomebrew/Installing boot9strap (MSET9-ChromeOS)|Installing boot9strap (MSET9-ChromeOS)]] - Pretty much only for Chromebooks that can't use Android for some reason.

[[User:ManiacOfHomebrew/Installing boot9strap (MSET9-GM9)|Installing boot9strap (MSET9-GM9)]] - I really have no idea why you would ever use this.

[https://skater.nintendohomebrew.com super-skaterhax AIO generator] - Used on the [[3ds-guide:installing-boot9strap-(super-skaterhax)|guide]]! ([https://maniacofgithub.github.io/super-skaterhax-site/ Mirror because ISPs hate this site for some reason])

User:ManiacOfHomebrew/Installing boot9strap (MSET9-GM9)

2025-04-24T03:33:38Z

ManiacOfHomebrew: Finish the guide

== Required Reading ==
This is an alternative to the normal MSET9 guide that allows you to use another already modded console to install boot9strap to an unmodded console. There's very little good reason to follow this guide considering the compatibility of MSET9 on different OS nowadays. If you do not know why you are following this guide, you should instead [https://3ds.hacks.guide return to the main guide].

==What You Need==

*Two 3DS family consoles
**The source 3DS: the 3DS family console that is already running boot9strap
**The target 3DS: the 3DS family console on stock firmware
*Any adapters needed to insert the SD card from the target 3DS into the source 3DS
*The latest version of [https://github.com/hacks-guide/MSET9/releases/latest MSET9]
*The latest version of [https://github.com/ManiacOfGitHub/MSET9-GM9/releases MSET9-GM9] (the MSET9-GM9 <code>.zip</code> file)
*The latest version of [[3DS:GodMode9/Usage#Updating GodMode9|GodMode9]] installed onto the target SD card

==Instructions==
{{Info|text=The SD card referred to throughout this guide is the SD card from the target console.}}
{{Info|text=On this page, you will use the MSET9-GM9 script, which is used to trigger MSET9. While the script is in progress, user data will temporarily disappear but will return upon the completion of this page. If you get an error when running the script, please join [https://discord.gg/MWxPgEp Nintendo Homebrew on Discord] and ping <code>@_themaniac</code> for assistance.}}
===Section I - Prep Work===
In this section, you will prepare the MSET9 exploit by temporarily creating a new HOME Menu profile with no user data, and then setting up that profile with only the minimum data required for MSET9 to trigger. Your existing user data will disappear, but will come back when you are finished with this page.

#Insert your SD card into your computer
#Copy everything from the MSET9 <code>.zip</code> to the root of your SD card, overwriting any existing files
#Copy everything from the MSET9-GM9 <code>.zip</code> to the root of your SD card, overwriting any existing files
#Insert your SD card into your '''source console'''
#Press and hold {{B|Start}}, and while holding {{B|Start}}, power on the '''source console'''. This will launch GodMode9
#Press {{B|Home}} to bring up the action menu
#Select "Lua scripts..."
#Select "MSET9-GM9"
#Press {{B|A}} to continue when you see "Welcome to MSET9-GM9."
#Read the information on the bottom screen, then press {{B|A}} to continue
#Press {{B|A}} to unlock <code>0:/Nintendo 3DS</code> writing, then input the key combo given
#*You can ignore the warning that says "!THIS IS NOT RECOMMENDED!"
#Select the option corresponding to your console model and version
#Select "1. Create MSET9 ID1" to begin the process of creating the MSET9 ID1
#After reviewing the disclaimer, press {{B|A}} to accept it
#If you see the message "Created hacked ID1.", press {{B|A}} to exit the script
#Press {{B|A}} to power off your console
#Eject the SD card from the '''source console'''
#Reinsert your SD card into the '''target console'''
#Power on the '''target console'''
#Open Mii Maker
#Wait for your console to reach the [[3ds-guide:images/screenshots/mset9/mii-welcome.png|Welcome to Mii Maker]] screen, then exit Mii Maker and return to the HOME Menu
#*You may see [[3ds-guide:images/screenshots/mset9/mii-extdata.png|this screen]], which indicates the necessary data has been created
#*If you just reach the [[3ds-guide:images/screenshots/mset9/mii-existing.png|normal]] Mii Maker screen, then the data already exists. Exit Mii Maker and return to the HOME Menu
#Launch System Settings and navigate to <code>Data Management</code> -> <code>Nintendo 3DS</code> -> <code>Software</code> -> <code>Reset</code> ([[3ds-guide:images/screenshots/database-reset.jpg|image]])
#*This will not wipe any of your data
#Power off the '''target console''' by pressing the power button then tapping Power Off on the lower screen
#Eject the SD card from the '''target console'''
#Reinsert your SD card into the '''source console'''
#Press and hold {{B|Start}}, and while holding {{B|Start}}, power on the '''source console'''. This will launch GodMode9
#Press {{B|Home}} to bring up the action menu
#Select "Lua scripts..."
#Select "MSET9-GM9"
#Press {{B|A}} to continue when you see "Welcome to MSET9-GM9."
#Read the information on the bottom screen, then press {{B|A}} to continue
#Press {{B|A}} to unlock <code>0:/Nintendo 3DS</code> writing, then input the key combo given
#*You can ignore the warning that says "!THIS IS NOT RECOMMENDED!"
#Select the option corresponding to your console model and version
#The top screen should change to [https://raw.githubusercontent.com/ManiacOfGitHub/MSET9-GM9/refs/heads/master/resources/mset9-gm9/ready.png this] and display <code>Ready!</code>
#*If the window says <code>Not Ready - Check MSET9 status for more details.</code>:
#**Select "2. Check MSET9 status" to check the MSET9 status and follow the directions indicated
#**Once you have resolved the issue, return to Section I Step 24
#Press {{B|B}} to exit the script
#Press {{B|A}} to power off your console
#Eject the SD card from the '''source console'''
#Reinsert your SD card into the '''target console'''
===Section II - MSET9===
In this section, you will trigger MSET9 to launch SafeB9SInstaller (the custom firmware installer).
{{Warning|text=These instructions must be followed '''EXACTLY''', so double-check EVERYTHING you are doing to avoid errors!}}
#Power on the '''target console''', ensuring System Settings is selected
#*If System Settings is not selected, [[3ds-guide:images/screenshots/mset9/hover-settings.png|hover over]] the System Settings icon using the D-Pad, power your console off, then back on
#Press {{B|A}} to launch System Settings
#Navigate to <code>Data Management</code> -> <code>Nintendo 3DS</code> -> <code>Extra Data</code> ([[3ds-guide:images/screenshots/mset9/settings-extdata.png|image]])
#'''Do not press any buttons or touch the screen'''
#'''With the target console STILL ON, and without pressing any buttons or touching the screen,''' remove your SD card from the '''target console'''
#Insert your SD card into your '''source console'''
#Press and hold {{B|Start}}, and while holding {{B|Start}}, power on the '''source console'''. This will launch GodMode9
#Press {{B|Home}} to bring up the action menu
#Select "Lua scripts..."
#Select "MSET9-GM9"
#Press {{B|A}} to continue when you see "Welcome to MSET9-GM9."
#Read the information on the bottom screen, then press {{B|A}} to continue
#Press {{B|A}} to unlock <code>0:/Nintendo 3DS</code> writing, then input the key combo given
#*You can ignore the warning that says "!THIS IS NOT RECOMMENDED!"
#Select the option corresponding to your console model and version
#Select "3. Inject trigger file" to inject MSET9
#*You should see "MSET9 successfully injected!"
#Press {{B|A}} to exit the script
#Press {{B|A}} to power off the '''source console'''
#Reinsert your SD card into the '''target console''' without pressing any buttons or touching the screen
#If the exploit was successful, you will have booted into SafeB9SInstaller
===Section III - Installing boot9strap===
In this section, you will install custom firmware onto your console.
#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, [[3ds-guide:troubleshooting-mset9.html|follow this troubleshooting guide]]
#Once it is complete, press {{B|A}} to reboot your console
#Your device 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 your device shuts down when you try to power it on, ensure that you have copied <code>boot.firm</code> from the MSET9 <code>.zip</code> to the root of your SD card
#Press (Start) to save and reboot
===Section IV - Removing MSET9===
In this section, you will remove MSET9 to prevent further issues and to restore your user data (games, themes, etc). (This will not remove the custom firmware that you have just installed.)
{{Warning|text=Do NOT skip this section! If you skip it, applications may crash unexpectedly and you will encounter errors on the next page!}}
#Power off your '''target console'''
#Eject the SD card from the '''target console'''
#Reinsert your SD card into the '''source console'''
#Press and hold {{B|Start}}, and while holding {{B|Start}}, power on the '''source console'''. This will launch GodMode9
#Press {{B|Home}} to bring up the action menu
#Select "Lua scripts..."
#Select "MSET9-GM9"
#Press {{B|A}} to continue when you see "Welcome to MSET9-GM9."
#Read the information on the bottom screen, then press {{B|A}} to continue
#Press {{B|A}} to unlock <code>0:/Nintendo 3DS</code> writing, then input the key combo given
#*You can ignore the warning that says "!THIS IS NOT RECOMMENDED!"
#Select the option corresponding to your console model and version
#Select "4. Remove trigger file"
#*You should see "Removed trigger file."
#Press {{B|A}} to return to the main menu.
#Select "5. Remove MSET9"
#*You should see "Successfully removed MSET9!"
#Press {{B|A}} to power off.
#Eject the SD card from the '''source console'''
#Reinsert your SD card into the '''target console'''
{{Info|text=You can '''now''' delete the <code>mset9-gm9</code> folder on the root of your SD card if you wish.}}
At this point, your console will boot to Luma3DS by default.

*Luma3DS does not look any different from the normal HOME Menu. If your console has booted into the HOME Menu, it is running custom firmware.
*On the next page, you will install useful homebrew applications to complete your setup.
-----

{{Warning|text=Did you follow Section IV (Removing MSET9)? That section is MANDATORY!}}
Continue to [[3dsguide:finalizing-setup|Finalizing Setup]]

User:ManiacOfHomebrew/Installing boot9strap (MSET9-GM9)

2025-04-24T02:48:35Z

ManiacOfHomebrew: begin writing guide for mset9-gm9. biggest waste of time in my life, but it's fun

3DS:Dump titles and game cartridges

2025-04-21T15:03:39Z

ManiacOfHomebrew: Make angle brackets more consistent

{{hatnote|1="3DS:DUMP" redirects here. For dumping system files, see [[3DS:Dump system files]].}}
{{TOC right}}{{info|text=For support (in English) with GodMode9, as well as help with scripting and to get updates and info, join [https://discord.gg/BRcbvtFxX4 GodMode9 on Discord].}}

Aside from creating and restoring NAND backups, GodMode9 has the functionality to dump installed titles to an installable <code>.cia</code> file, to dump game cartridge data to a <code>.3ds</code> ROM file, and to directly install a game cartridge to the system.

== Updating GodMode9 ==

{{info|text=These instructions are written for use with GodMode9 v2.0.0 or later. If you have an older version of GodMode9, follow these instructions to update it.}}

=== What You Need ===

* The latest release of [https://github.com/d0k3/GodMode9/releases/latest GodMode9]

=== Instructions ===

# Power off your device
# Insert your SD card into your computer
# Copy <code>GodMode9.firm</code> from the GodMode9 <code>.zip</code> to the <code>/luma/payloads/</code> folder on your SD card
# Copy the <code>gm9</code> folder from the GodMode9 <code>.zip</code> to the root of your SD card
# Reinsert your SD card into your device

== Installing a game cartridge directly to the system ==

{{info|text=This will only work for 3DS games; it is not possible to install an NDS game cartridge to the system as a title.}}

# Press and hold {{B|Start}}, and while holding {{B|Start}}, power on your device. This will launch GodMode9
# Navigate to <code>[C:] GAMECART</code>
# Press {{B|A}} on <code><TitleID>.trim.3ds</code> to select it, then select NCSD image options…, then select Install game image
# Press {{B|A}} to unlock SysNAND (lvl1) writing, then input the key combo given
# Once the process is complete, your game will show up in the HOME Menu as an installed title.

{{info|text=Save data is not automatically copied, you must do it yourself with a save manager such as [[Checkpoint]].}}

== Dumping a game cartridge ==

{{info|text=Insert the game cartridge you intend to dump into your device
* 3DS game cartridges will be dumped to a <code>.3ds</code> format
* NDS game cartridges will be dumped to a <code>.nds</code> format}}

# Press and hold {{B|Start}}, and while holding {{B|Start}}, power on your device. This will launch GodMode9
# Navigate to <code>[C:] GAMECART</code>
# Follow the steps applicable to your game cartridge:
#* '''3DS Game Cartridge:''' Press {{B|A}} on <code><TitleID>.trim.3ds</code> to select it, then select <code>NCSD image options...</code>, then select <code>Decrypt file (0:/gm9/out)</code>.
#* '''NDS Game Cartridge:''' Press {{B|A}} on <code><TitleID>.nds</code> to select it, then select <code>Copy to 0:/gm9/out</code>
#** Trimmed dumps are not recommended for NDS games in general, as they can cause various playback issues
# Your non-installable <code>.3ds</code> or <code>.nds</code> formatted file will be outputted to the <code>/gm9/out/</code> folder on your SD card

== Dumping a 3DS game cartridge to CIA ==

{{info|text=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.}}

# Press and hold {{B|Start}}, and while holding {{B|Start}}, power on your device. This will launch GodMode9
# Navigate to <code>[C:] GAMECART</code>
# Press {{B|A}} on <code><TitleID>.trim.3ds</code> to select it, then select NCSD image options…, then select Build CIA from file
# Your installable <code>.cia</code> formatted file will be outputted to the <code>/gm9/out/</code> folder on your SD card

== Dumping an installed title ==

{{info|text=This allows dumping of both System- and User-installed digital titles, such as ones downloaded from the eShop.}}

# Press and hold {{B|Start}}, and while holding {{B|Start}}, power on your device. This will launch GodMode9
# Press {{B|Home}} to bring up the action menu
# Select Title manager
# Select one of the following depending on the type of title you wish to dump
#* '''User Installed Title''': <code>[A:] SD CARD</code>
#* '''System Title / DSiWare''': <code>[1:] NAND / TWL</code>
# Select the title you wish to dump
# Select Manage Title…
# Select Build CIA (standard)
# Your installable <code>.cia</code> formatted file will be outputted to the <code>/gm9/out/</code> folder on your SD card

== Backup GBA VC saves ==

{{info|text=The game will be outputted to the <code>/gm9/out/</code> folder on your SD card with the name <code><TitleID>.gbavc.sav</code>.}}

{{info|text=To identify a <code><TitleID>.gbavc.sav</code> file’s Title ID, you can get a listing of all games on the system and their corresponding Title IDs by pressing {{B|Home}} to bring up the action menu, selecting <code>Title manager</code>, and selecting <code>[A:] SD CARD</code>.}}

# 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 {{B|Start}}, and while holding {{B|Start}}, power on your device. This will launch GodMode9
## Navigate to <code>[S:] SYSNAND VIRTUAL</code>
## Press {{B|A}} on <code>agbsave.bin</code> to select it
## Select AGBSAVE options…
## Select Dump GBA VC save
## Press {{B|A}} to continue
## Press {{B|Start}} to reboot your device

== Restore GBA VC saves ==

{{info|text=To identify a <code><TitleID>.gbavc.sav</code> file’s Title ID, you can get a listing of all games on the system and their corresponding Title IDs by pressing {{B|Home}} to bring up the action menu, selecting <code>Title manager</code>, and selecting <code>[A:] SD CARD</code>.}}

# 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 {{B|Start}}, and while holding {{B|Start}}, power on your device. This will launch GodMode9
## Navigate to <code>[0:] SDCARD</code> -> <code>gm9</code> -> <code>out</code>
## Press {{B|Y}} on the <code><TitleID>.gbavc.sav</code> file you wish to restore to copy it
## Press {{B|B}} to return to the main menu
## Navigate to <code>[S:] SYSNAND VIRTUAL</code>
## Press {{B|A}} on <code>agbsave.bin</code> to select it
## Select AGBSAVE options…
## Select Inject GBA VC save
## Press {{B|A}} to continue
## Press {{B|Start}} to reboot your device
## Launch the GBA VC game
## Exit the GBA VC game

== Encrypting / Decrypting a CIA file ==

{{info|text=For organizational purposes, copy each <code>.cia</code> file you wish to encrypt / decrypt to the <code>/cias/</code> folder on your SD card}}

# Press and hold {{B|Start}}, and while holding {{B|Start}}, power on your device. This will launch GodMode9
# Navigate to <code>[0:] SDCARD</code> -> <code>cias</code>
# Press {{B|A}} on the <code>.cia</code> file to select it, then select CIA image options…
# Select the option to perform the desired function:
#* '''Encrypt to 0:/gm9/out:''' Create an encrypted copy of the selected <code>.cia</code> file in the <code>/gm9/out/</code> folder on your SD card
#* '''Decrypt to 0:/gm9/out:''' Create a decrypted copy of the selected <code>.cia</code> file in the <code>/gm9/out/</code> folder on your SD card
#* '''Encrypt inplace:''' Replace the selected <code>.cia</code> file with an encrypted version
#* '''Decrypt inplace:''' Replace the selected <code>.cia</code> file with a decrypted version
# Your encrypted / decrypted <code>.cia</code> will be outputted to the desired location

{{hg imported|Guide_3DS}}

[[Category:Nintendo 3DS guides]]

3DS:Fastboot3DS to boot9strap

2025-04-13T21:37:33Z

ManiacOfHomebrew: Caps

{{lowercase title}}
==Required Reading==
[[3DS:fastboot3DS|fastboot3DS]] is a firmware loader alternative to [[3DS:boot9strap|boot9strap]]. It offers some enhanced features compared to boot9strap such as the ability to chainload payloads, display splashes, backup/restore your NAND, and more. Although there is no issues with running fastboot3DS with modern CFW, most homebrew guides will assume you are running boot9strap which could make troubleshooting difficult if you are unsure of how fastboot3DS functions. If you would like to learn about fastboot3DS you can read more on its [[3DS:fastboot3DS|wiki page]], otherwise continue with this guide to move your setup to boot9strap.

==Instructions==
===What you need===

*the latest release of [https://github.com/LumaTeam/Luma3DS/releases/latest Luma3DS] (the Luma3DS <code>.zip</code> file)
*the latest release of [https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip SafeB9SInstaller] (direct download)
*the latest release of [https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip boot9strap] (direct download)

===Section I - Prep Work===

# Power off your console
# Insert the SD card into your computer
# Copy <code>boot.firm</code>, <code>boot.3dsx</code>, and <code>config</code> from the Luma3DS <code>.zip</code> to the root of your SD card
# Create a folder named <code>boot9strap</code> on the root of your SD card
# Copy <code>boot9strap.firm</code> and <code>boot9strap.firm.sha</code> from the boot9strap <code>.zip</code> to the <code>/boot9strap/</code> folder on your SD card
#Copy <code>SafeB9SInstaller.firm</code> from the SafeB9SInstaller <code>.zip</code> to the root of your SD card
# Reinsert your SD card into your console

===Section II - Installing boot9strap===

# Press and hold {{B|HOME}}, and while holding {{B|HOME}}, power on your console. This will launch the fastboot3DS menu
# Select <code>[+] Boot from file...</code> -> <code>sdmc:</code> -> <code>SafeB9SInstaller.firm</code>
# You will have booted into SafeB9SInstaller
# When prompted, input the key combo given on the top screen to install boot9strap
#* If the top screen is blank, power off your device and re-do Section II
# Once it is complete, press (A) to reboot your device
#* Your console may 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, '''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 <code>boot.firm</code> from the Luma3DS <code>.zip</code> to the root of your SD card
#* press {{B|START}} to save and reboot
{{Luma3DS is default}}

-----

Continue to [[3dsguide:finalizing-setup|Finalizing Setup]]

[[Category:Nintendo 3DS guides]]

3DS:3ds essential dumper

2025-01-04T13:24:21Z

ManiacOfHomebrew: Fix typo

{{DISPLAYTITLE:3DS:3ds_essential_dumper}}{{Infobox homebrew
| title = 3ds_essential_dumper
| for3ds = 1
| developers = danny8376
| version = alpha-b67d544
| releasedate = 2023-9-10
| github = danny8376/3ds_essential_dumper
| githubtag = alpha-b67d544
}}
{{info|text=This guide is intended for consoles that are suffering from hardware failure and can no longer function normally. If your 3DS can still run [[GodMode9]], see [[3DS:GodMode9/Usage#Creating_a_NAND_backup|GodMode9 Usage]] instead.}}

== What You Need==

*The latest release of [https://github.com/danny8376/3ds_essential_dumper/releases 3ds_essential_dumper] (the <code>3ds_essential_dumper.firm</code> file)

==Section 1 Prep Work ==

#Power off your console
#Insert your SD card into your computer
#Rename <code>boot.firm</code> to <code>luma.firm</code>, if it exists
#Copy <code>3ds_essential_dumper.firm</code> to the root of your SD card
#Rename <code>3ds_essential_dumper.firm</code> to <code>boot.firm</code>
#Reinsert your SD card into your console

==Section II: 3ds_essential_dumper ==
{{info|Ensure your SD card has at least 1.3GB of free space if you plan on doing a NAND backup, and that it is formatted to FAT32 using [[Formatting an SD card|our guide]]}}

#Power on your console
# When the Power and Notification LEDs flash red, press {{Key press|A}} to dump the NAND
#*If you do not need a NAND dump from the console, press {{Key press|B}} instead
#Wait for your console to turn off. If dumping the NAND, this can take over 30 minutes to an hour
#Insert your SD card into your computer
#Your dumped files will be in the <code>/edump/</code> folder on the SD card

File:Super-skaterhax-usa-v11.17.zip

2024-12-30T15:06:40Z

ManiacOfHomebrew: ManiacOfHomebrew uploaded a new version of File:Super-skaterhax-usa-v11.17.zip

Super Skater Hax Files, 11.17, USA

File:Super-skaterhax-usa-pre17.zip

2024-12-30T15:06:12Z

ManiacOfHomebrew: ManiacOfHomebrew uploaded a new version of File:Super-skaterhax-usa-pre17.zip

Super Skater Hax Files, 11.15-11.16, USA

File:Super-skaterhax-kor-pre17.zip

2024-12-30T15:05:32Z

ManiacOfHomebrew: ManiacOfHomebrew uploaded a new version of File:Super-skaterhax-kor-pre17.zip

Super Skater Hax Files, Pre 11.17, KOR

File:Super-skaterhax-jpn-all.zip

2024-12-30T15:05:07Z

ManiacOfHomebrew: ManiacOfHomebrew uploaded a new version of File:Super-skaterhax-jpn-all.zip

Super Skater Hax Files, 11.15-11.17, JPN

File:Super-skaterhax-eur-all.zip

2024-12-30T15:04:45Z

ManiacOfHomebrew: ManiacOfHomebrew uploaded a new version of File:Super-skaterhax-eur-all.zip

Super Skater Hax Files, 11.15-11.17, EUR

Pretendo Network

2024-11-24T18:38:17Z

ManiacOfHomebrew: Change supported game list to unofficial, but more up-to-date, source

{{Infobox homebrew
| title = Nimbus(Nintendo 3DS)
| image = Pretendo-banner.png
| for3ds = 1
| forwiiu = 0
| developers = jonbarrow, ashquarky, and others.
| website = https://pretendo.network/ Pretendo.Network
| github = PretendoNetwork/nimbus
| universaldb = 3ds/nimbus
| version = 1.6.1
| releasedate = 2024-07-02
| githubtag = latest
}}
{{Infobox homebrew
| title = Inkay(Nintendo Wii U)
| image = Pretendo-banner.png
| for3ds = 0
| forwiiu = 1
| forswitch = 0
| forwii = 0
| developers = jonbarrow, ashquarky, and others.
| website = https://pretendo.network/ Pretendo.Network
| github = PretendoNetwork/inkay
| releaseurl = https://hb-app.store/wiiu/inkay hb-app.store
| version = 2.6.0
| releasedate = 2024-07-26
| githubtag = latest
| forwindows = 0
| formac = 0
| forlinux = 0
| forjava = 0
}}

Pretendo is an open-source project that aims to recreate [[w:Nintendo Network|Nintendo Network]] for the 3DS and Wii U. This includes but is not limited to, game servers, [[w:Miiverse|Miiverse]], friends-lists, and more.

==Installation==
For 3DS, [[udb:3ds/nimbus|Nimbus]] is available on Universal-Updater. For Wii U, [[hbappstore:wiiu/inkay|Inkay]] is available on the Homebrew App Store. Manual installation instructions for 3DS, Wii U, and Cemu can be found on the Pretendo website [https://pretendo.network/docs/install/ here].

==Usage==
<tabber>
|-|Nintendo 3DS=
Nimbus allows for switching between Pretendo and Nintendo Networks. To use Nimbus, launch it from the HOME Menu or the Homebrew Launcher, and select either '''Pretendo''' or '''Nintendo''' to switch between the two networks. While on the Pretendo Network, launch a [https://games.pretendo.zip supported game] to play online with other Pretendo users.
Some features, notably Pretendo's Miiverse replacement Juxtaposition, will require a PNID to function. A PNID is a unique identifier, functioning the same as Nintendo's NNIDs. To create a PNID open '''System Settings''' -> '''Nintendo Network ID Settings'''. Alternatively, [https://pretendo.network/account/register register for an account] using the Pretendo website, and then link an existing PNID instead.
|-|Nintendo Wii U=
Inkay allows for switching between Pretendo and Nintendo Networks. To use Inkay press {{B|L + DOWN + SELECT}} on the Wii U Gamepad to open the Plugin Menu, then press {{B|A}} on '''Inkay'''
* To connect to Nintendo Network, set '''Connect to the Pretendo Network''' to <code>false</code>
* To connect to Pretendo Network, set '''Connect to the Pretendo Network''' to <code>true</code>

While on the Pretendo Network, launch a [https://games.pretendo.zip supported game] to play online with other Pretendo users.
Some features, notably Pretendo's Miiverse replacement Juxtaposition, will require a PNID to function. A PNID is a unique identifier, functioning the same as Nintendo's NNIDs. To create a PNID, tap on your profile icon in the Wii U Menu -> '''Create/Link Nintendo Network ID'''. Alternatively, [https://pretendo.network/account/register register for an account] using the Pretendo website, and then link an existing PNID instead.
</tabber>

=== SD file layout ===
<tabber>

|-|Nintendo 3DS=

{{Tree list}}
* {{Tree icon|sd}} (root)
** {{Tree icon|d}} 3ds
*** {{Tree icon|f}} nimbus.3dsx
*** {{Tree icon|f}} juxt-prod.pem
** {{Tree icon|d}} luma
*** {{Tree icon|d}} sysmodules
**** {{Tree icon|f}}0004013000002902.ips
**** {{Tree icon|f}}0004013000002E02.ips
**** {{Tree icon|f}}0004013000002F02.ips
**** {{Tree icon|f}}0004013000003202.ips
**** {{Tree icon|f}}0004013000003802.ips
*** {{Tree icon|d}} titles
**** {{Tree icon|d}}000400300000BC02
**** {{Tree icon|d}}000400300000BD02
**** {{Tree icon|d}}000400300000BE02
{{Tree list/end}}


|-|Nintendo Wii U=

{{Tree list}}
* {{Tree icon|sd}} (root)
** {{Tree icon|d}} wiiu
*** {{Tree icon|d}} environments
**** {{Tree icon|d}} aroma
***** {{Tree icon|d}} modules
****** {{Tree icon|d}} setup
******* {{Tree icon|f}} 30_nimble.rpx
***** {{Tree icon|d}} plugins
****** {{Tree icon|f}} Inkay-pretendo.wps
{{Tree list/end}}

</tabber>

User:ManiacOfHomebrew

2024-11-19T22:56:04Z

ManiacOfHomebrew: this has been a long time coming

Hello. I like cubes with derpy faces and stuff. Here's some of that stuff:

[[User:ManiacOfHomebrew/3DS 12-hour Clock|3DS 12-hour clock]] - In case you're 'murican! (Or any other country that has a 12-hour clock I guess)

[[User:ManiacOfHomebrew/Installing boot9strap (MSET9-ChromeOS)|Installing boot9strap (MSET9-ChromeOS)]] - I have no idea why you would do this.

[https://skater.nintendohomebrew.com super-skaterhax AIO generator] - Used on the [[3ds-guide:installing-boot9strap-(super-skaterhax)|guide]]! ([https://maniacofgithub.github.io/super-skaterhax-site/ Mirror because ISPs hate this site for some reason])

3DS:System Transfer/Target has CFW

2024-11-05T21:02:27Z

ManiacOfHomebrew: source console, cuz it's getting copied over and the target sd card is gonna be emptied

The system transfer process is mostly the same as it would be done without CFW on either device, but you will need to use faketik at the end to restore any applications and games that did not come from the eShop.

== What You Need ==

* The latest release of {{GitHub|/d0k3/GodMode9/releases/latest|GodMode9}} (the GodMode9 <code>.zip</code> file)
* The latest release of {{GitHub|ihaveamac/faketik/releases/latest|faketik}} (the <code>.3dsx</code> file)

== Instructions ==

=== Section I - Prep Work ===

* For '''both consoles''', perform the following steps:
*# Power off your device
*# Insert your SD card into your computer
*# Copy <code>GodMode9.firm</code> from the GodMode9 <code>.zip</code> to the <code>/luma/payloads/</code> folder on your SD card
*# Copy the <code>gm9</code> folder from the GodMode9 <code>.zip</code> to the root of your SD card
* For the '''source console''', perform the following steps:
*# Create a folder named <code>3ds</code> on the root of your SD card if it does not already exist
*# Copy <code>faketik.3dsx</code> to the <code>/3ds/</code> folder on your SD card
* Reinsert both SD cards into their respective consoles

=== Section II - NAND Backup ===

Creating a NAND backup of both consoles is a good idea in case something goes wrong. It ensures you can recover your data in the event of an error.

* For '''both consoles''', perform the following steps:
*# Press and hold {{B|START}}, and while holding {{B|START}}, power on your device. This will launch GodMode9
*# Press {{B|HOME}} to bring up the action menu
*# Select "Scripts..."
*# Select "GM9Megascript"
*# Select "Backup Options"
*# Select "SysNAND Backup"
*# Press {{B|A}} to confirm
*#* This process will take some time
*#* If you get an error, make sure that you have at least 1.3GB of free space on your SD card
*# Press {{B|A}} to continue
*# Press {{B|B}} to return to the main menu
*# Select "Exit"
*# Press {{B|A}} to relock write permissions if prompted
*# Press {{B|R|START}} to power off your console
*# Insert the console's SD card into your computer
*# Copy <code><date>_<serialnumber>_sysnand_00.bin</code> and <code><date>_<serialnumber>_sysnand_00.bin.sha</code> from <code>/gm9/out</code> to a safe place on your computer, then delete both files from the SD card
*# Reinsert the SD card into its console

=== Section III - System Transfer ===

# [https://en-americas-support.nintendo.com/app/answers/detail/a_id/14169 Perform the system transfer as usual]. If you are transferring from a Old 3DS to a New 3DS, choose the option '''PC-Based Transfer''' when asked, not '''Wireless Transfer''' or '''Low-Capacity microSD Card Transfer'''
#* The prompt mentioning this is not given when transferring between two Old 3DS consoles or two New 3DS consoles. These transfers are almost the same as PC-Based Transfers, but ask you to move the '''source console''''s physical SD card to the '''target console''' rather than just copy the data over. This part can be ignored without consequence, and you can copy the data between the SD cards anyway
#* If you have the option to pick a PC-Based Transfer but do not have access to a PC, be aware that during a Wireless Transfer, homebrew software, cartridge dumps, and any other data only obtainable through CFW will not be transferred over. You will need to take extra steps to reobtain the lost data.

=== Next Steps - Branching of the Way ===

Were you able to perform a '''PC-Based Transfer''' in Section III?
----
<tabber>

|-|Yes=

{{info|text='''The source console is finished.''' The following steps should only be performed on '''the target console'''.}}

=== Section IV - Homebrew Launcher ===

# Launch the Download Play application
# Wait until you see the Nintendo 3DS and Nintendo DS buttons
# Press {{B|L}} + {{B|D-PAD DOWN}} + {{B|SELECT}} at the same time to open the Rosalina menu
# Select "Miscellaneous options"
# Select "Switch the hb. title to the current app."
# Press {{B|B}} to continue
# Press {{B|B}} to return to the Rosalina main menu
# Press {{B|B}} to exit the Rosalina menu
# Press {{B|HOME}}, then close Download Play
# Launch the Download Play application
# Your device should load the Homebrew Launcher

=== Section V - faketik ===

# Launch faketik from the list of homebrew
#* If you receive the error "The External Title Database is not available.", ensure that the correct SD card is inserted into the console
# Press {{B|HOME}}, then close Download Play

{{success|text=The transfer is complete! Note that you may have to unwrap all the icons that were restored by faketik.}}

|-|No, but a Wireless Transfer succeeded=

=== Section IV - Homebrew File Recovery ===

This section will have you manually copy all homebrew files onto the '''target console''', as wireless transfers actively refuse them.

# On the '''target console''', note all apps that should have appeared but are missing
# Insert the '''source console's''' SD card into your PC, and copy the homebrew data off of it and onto your PC
#*Everything except the <code>Nintendo 3DS</code> and <code>DCIM</code> folders is considered homebrew data
# Take out the '''source console's''' SD card but leave it out of its console, and insert the '''target console's''' SD card into your PC
# Move all of the files you copied off of the '''source console's''' SD card onto the '''target console's''' SD card
# Reinsert the '''target console's''' SD card into its console
# Redo [[3dsguide:finalizing-setup|Finalizing Setup]] on the '''target console'''. This will ensure you have backups available in case the next section does not work as intended

=== Section V - Homebrew App Recovery ===
{{Section WIP|notes=Provide more detailed instructions on how to use ninfs.}}

This section will restore all games/savedata that the Wireless Transfer refused to copy over.

# Insert the '''source console's''' SD card into your PC and mount its <code>Nintendo 3DS</code> folder using [[ninfs]]
# Copy all games/savedata that were not transferred onto the '''target console''' onto somewhere on your PC
# Unmount the '''source console's''' <code>Nintendo 3DS</code> folder and reinsert its SD card into its console
# Insert the '''target console's''' SD card into your PC
# Mount the '''target console's''' <code>Nintendo 3DS</code> folder in ninfs, and add all copied games/savedata from your PC into the existing contents
# Unmount the <code>Nintendo 3DS</code> folder from ninfs, but keep the '''target console's''' SD card inserted
# [[3DS:Rebuild Title Database|Rebuild title.db]] on the '''target console''' to force all the new apps to appear
# Reinsert the '''target console's''' SD card into its console

{{success|text=The transfer is complete! Note that you may have to unwrap all the icons that were restored.}}

|-|No, the transfer failed=

Attempt to redo the transfer. If it continues to give errors, join the [[Get support|Nintendo Homebrew Discord]] and ask, in English, for help.

</tabber>

[[Category:Nintendo 3DS guides]]

3DS:System Transfer/Target has CFW

2024-11-05T20:58:09Z

ManiacOfHomebrew: faketik not copied lol

The system transfer process is mostly the same as it would be done without CFW on either device, but you will need to use faketik at the end to restore any applications and games that did not come from the eShop.

== What You Need ==

* The latest release of {{GitHub|/d0k3/GodMode9/releases/latest|GodMode9}} (the GodMode9 <code>.zip</code> file)
* The latest release of {{GitHub|ihaveamac/faketik/releases/latest|faketik}} (the <code>.3dsx</code> file)

== Instructions ==

=== Section I - Prep Work ===

* For '''both consoles''', perform the following steps:
*# Power off your device
*# Insert your SD card into your computer
*# Copy <code>GodMode9.firm</code> from the GodMode9 <code>.zip</code> to the <code>/luma/payloads/</code> folder on your SD card
*# Copy the <code>gm9</code> folder from the GodMode9 <code>.zip</code> to the root of your SD card
* For the '''target console''', perform the following steps:
*# Create a folder named <code>3ds</code> on the root of your SD card if it does not already exist
*# Copy <code>faketik.3dsx</code> to the <code>/3ds/</code> folder on your SD card
* Reinsert both SD cards into their respective consoles

=== Section II - NAND Backup ===

Creating a NAND backup of both consoles is a good idea in case something goes wrong. It ensures you can recover your data in the event of an error.

* For '''both consoles''', perform the following steps:
*# Press and hold {{B|START}}, and while holding {{B|START}}, power on your device. This will launch GodMode9
*# Press {{B|HOME}} to bring up the action menu
*# Select "Scripts..."
*# Select "GM9Megascript"
*# Select "Backup Options"
*# Select "SysNAND Backup"
*# Press {{B|A}} to confirm
*#* This process will take some time
*#* If you get an error, make sure that you have at least 1.3GB of free space on your SD card
*# Press {{B|A}} to continue
*# Press {{B|B}} to return to the main menu
*# Select "Exit"
*# Press {{B|A}} to relock write permissions if prompted
*# Press {{B|R|START}} to power off your console
*# Insert the console's SD card into your computer
*# Copy <code><date>_<serialnumber>_sysnand_00.bin</code> and <code><date>_<serialnumber>_sysnand_00.bin.sha</code> from <code>/gm9/out</code> to a safe place on your computer, then delete both files from the SD card
*# Reinsert the SD card into its console

=== Section III - System Transfer ===

# [https://en-americas-support.nintendo.com/app/answers/detail/a_id/14169 Perform the system transfer as usual]. If you are transferring from a Old 3DS to a New 3DS, choose the option '''PC-Based Transfer''' when asked, not '''Wireless Transfer''' or '''Low-Capacity microSD Card Transfer'''
#* The prompt mentioning this is not given when transferring between two Old 3DS consoles or two New 3DS consoles. These transfers are almost the same as PC-Based Transfers, but ask you to move the '''source console''''s physical SD card to the '''target console''' rather than just copy the data over. This part can be ignored without consequence, and you can copy the data between the SD cards anyway
#* If you have the option to pick a PC-Based Transfer but do not have access to a PC, be aware that during a Wireless Transfer, homebrew software, cartridge dumps, and any other data only obtainable through CFW will not be transferred over. You will need to take extra steps to reobtain the lost data.

=== Next Steps - Branching of the Way ===

Were you able to perform a '''PC-Based Transfer''' in Section III?
----
<tabber>

|-|Yes=

{{info|text='''The source console is finished.''' The following steps should only be performed on '''the target console'''.}}

=== Section IV - Homebrew Launcher ===

# Launch the Download Play application
# Wait until you see the Nintendo 3DS and Nintendo DS buttons
# Press {{B|L}} + {{B|D-PAD DOWN}} + {{B|SELECT}} at the same time to open the Rosalina menu
# Select "Miscellaneous options"
# Select "Switch the hb. title to the current app."
# Press {{B|B}} to continue
# Press {{B|B}} to return to the Rosalina main menu
# Press {{B|B}} to exit the Rosalina menu
# Press {{B|HOME}}, then close Download Play
# Launch the Download Play application
# Your device should load the Homebrew Launcher

=== Section V - faketik ===

# Launch faketik from the list of homebrew
#* If you receive the error "The External Title Database is not available.", ensure that the correct SD card is inserted into the console
# Press {{B|HOME}}, then close Download Play

{{success|text=The transfer is complete! Note that you may have to unwrap all the icons that were restored by faketik.}}

|-|No, but a Wireless Transfer succeeded=

=== Section IV - Homebrew File Recovery ===

This section will have you manually copy all homebrew files onto the '''target console''', as wireless transfers actively refuse them.

# On the '''target console''', note all apps that should have appeared but are missing
# Insert the '''source console's''' SD card into your PC, and copy the homebrew data off of it and onto your PC
#*Everything except the <code>Nintendo 3DS</code> and <code>DCIM</code> folders is considered homebrew data
# Take out the '''source console's''' SD card but leave it out of its console, and insert the '''target console's''' SD card into your PC
# Move all of the files you copied off of the '''source console's''' SD card onto the '''target console's''' SD card
# Reinsert the '''target console's''' SD card into its console
# Redo [[3dsguide:finalizing-setup|Finalizing Setup]] on the '''target console'''. This will ensure you have backups available in case the next section does not work as intended

=== Section V - Homebrew App Recovery ===
{{Section WIP|notes=Provide more detailed instructions on how to use ninfs.}}

This section will restore all games/savedata that the Wireless Transfer refused to copy over.

# Insert the '''source console's''' SD card into your PC and mount its <code>Nintendo 3DS</code> folder using [[ninfs]]
# Copy all games/savedata that were not transferred onto the '''target console''' onto somewhere on your PC
# Unmount the '''source console's''' <code>Nintendo 3DS</code> folder and reinsert its SD card into its console
# Insert the '''target console's''' SD card into your PC
# Mount the '''target console's''' <code>Nintendo 3DS</code> folder in ninfs, and add all copied games/savedata from your PC into the existing contents
# Unmount the <code>Nintendo 3DS</code> folder from ninfs, but keep the '''target console's''' SD card inserted
# [[3DS:Rebuild Title Database|Rebuild title.db]] on the '''target console''' to force all the new apps to appear
# Reinsert the '''target console's''' SD card into its console

{{success|text=The transfer is complete! Note that you may have to unwrap all the icons that were restored.}}

|-|No, the transfer failed=

Attempt to redo the transfer. If it continues to give errors, join the [[Get support|Nintendo Homebrew Discord]] and ask, in English, for help.

</tabber>

[[Category:Nintendo 3DS guides]]

User:ManiacOfHomebrew/sandbox

2024-11-05T00:17:44Z

ManiacOfHomebrew: ManiacOfHomebrew moved page User:ManiacOfHomebrew/sandbox to User:ManiacOfHomebrew/Installing boot9strap (MSET9-ChromeOS)

#REDIRECT [[User:ManiacOfHomebrew/Installing boot9strap (MSET9-ChromeOS)]]

3DS:Alternate Exploits/Installing boot9strap (MSET9-ChromeOS)

2024-11-05T00:17:44Z

ManiacOfHomebrew: ManiacOfHomebrew moved page User:ManiacOfHomebrew/sandbox to User:ManiacOfHomebrew/Installing boot9strap (MSET9-ChromeOS)

==Required Reading==
This is an alternative to the normal MSET9 Play Store guide that ChromeOS and Android devices would normally use. This version ports over the new features of MSET9 v2.0 and features a script that looks far more similar to the one used in the MSET9 CLI guide.

==Compatibility Notes==
{{Warning|text=This script is only compatible with Chromebooks and other devices running ChromeOS. If you are on a Windows, Mac, or Linux device, you should follow the [https://3ds.hacks.guide/installing-boot9strap-(mset9-cli).html MSET9 CLI guide] instead. If you are on an Android device, you should follow the [https://3ds.hacks.guide/installing-boot9strap-(mset9-play-store).html MSET9 Play Store guide] instead. If you do not have access to any of these devices, you will need to use an [[3DS:Alternate Exploits|alternate exploit]].}}

==What You Need==

*The latest version of [https://github.com/hacks-guide/MSET9/releases/latest MSET9]

==Instructions==
{{Info|text=On this page, you will use the MSET9-ChromeOS script, which is used to trigger MSET9. While the script is in progress, user data will temporarily disappear but will return upon the completion of this page. If you get an error when running the script, please join [https://discord.gg/MWxPgEp Nintendo Homebrew on Discord] and ping <code>@_themaniac</code> for assistance.}}

===Section I - Prep Work===
In this section, you will prepare the MSET9 exploit by temporarily creating a new HOME Menu profile with no user data, and then setting up that profile with only the minimum data required for MSET9 to trigger. Your existing user data will disappear, but will come back when you are finished with this page.

#Insert your SD card into your Chromebook
#Open the MSET9 <code>.zip</code> file from your Downloads folder, and copy everything inside to the root of your SD card
#*Before copying, ensure that none of the files inside the ZIP are already on the SD card. If they are, delete them
#Go to [https://maniacofgithub.github.io/mset9-chromeos/ this website] and click "Copy!" to copy the script to your clipboard
# Open the ChromeOS Files application by pressing {{B|Alt|Shift|M}} on your keyboard
#Select your SD card on the sidebar on the left in the Files application
#Open the DevTools Console for the Files application by pressing {{B|Ctrl|Shift|J}} on your keyboard
#*You may want to maximize this window to make it easier to read
#*Do not close this window or the Files application until you are told to do so
#Click to the right of the right arrow on the left side of this menu. Your cursor should start blinking
#Press {{B|Ctrl|V}} to paste the code then push Enter to run the MSET9-ChromeOS script
#*If you see a warning about not pasting code into the console that you do not understand, type <code>allow pasting</code> and then push Enter. Then, retry this step
#*This script does not contain malware, sends no data to any server, and does not even require an internet connection. If you wish, you can read the code on the site where you copied it from to verify this
#Type the characters corresponding to your console model and version, then press Enter
#*Ensure that the correct console model and version is displayed
#Type <code>a</code>, then press Enter to begin the process of creating the MSET9 ID1
#After reading the disclaimer, type <code>a</code> again and press Enter to accept it
#*If you see the message "Created hacked ID1.", you are ready to continue the guide
#*Your 3DS will appear to have no data / no user-installed apps on HOME Menu. '''This is expected.''' Your data will come back at a later step
#Eject the SD card from the Chromebook, either by typing <code>eject</code> into the DevTools Console or by selecting the eject icon in the Files app
#Reinsert your SD card into the console
#Power on your console
#Open Mii Maker
#Wait for your console to reach the [[3ds-guide:images/screenshots/mset9/mii-welcome.png|Welcome to Mii Maker]] screen, then exit Mii Maker and return to the HOME Menu
#*You may see [[3ds-guide:images/screenshots/mset9/mii-extdata.png|this screen]], which indicates the necessary data has been created
#*If you just reach the [[3ds-guide:images/screenshots/mset9/mii-existing.png|normal]] Mii Maker screen, then the data already exists. Exit Mii Maker and return to the HOME Menu
#Launch System Settings and navigate to <code>Data Management</code> -> <code>Nintendo 3DS</code> -> <code>Software</code> -> <code>Reset</code> ([[3ds-guide:images/screenshots/database-reset.jpg|image]])
#*This will not wipe any of your data
#Power off your console by pressing the power button then tapping Power Off on the lower screen
#Insert your SD card into your Chromebook
#Select your SD card on the sidebar on the left in the Files application
#In the DevTools Console window, type <code>restart</code> and press Enter to run the MSET9-ChromeOS script
#*If you closed the Files window or the DevTools Console window, this will not work
#*Instead, you should redo Section I Steps 3 through 8
#Type the characters corresponding to your console model and version, then press Enter
#*The window should change to this and display <code>Ready</code>
#**(Image coming soon)
#*If the window says <code>Not ready - check MSET9 status for more details</code>:
#**Type <code>b</code>, then press Enter to check the MSET9 status and follow the directions indicated
#**Once you have resolved the issue, return to Section I Step 19
#Type <code>z</code>, then press Enter to close the script
#*Do not close the window
#Eject the SD card from the Chromebook, either by typing <code>eject</code> into the DevTools Console or by selecting the eject icon in the Files app
#Reinsert your SD card into your console

===Section II - MSET9===
In this section, you will trigger MSET9 to launch SafeB9SInstaller (the custom firmware installer).
{{Warning|text=These instructions must be followed '''EXACTLY''', so double-check EVERYTHING you are doing to avoid errors!}}
#Power on your console, ensuring System Settings is selected
#*If System Settings is not selected, [[3ds-guide:images/screenshots/mset9/hover-settings.png|hover over]] the System Settings icon using the D-Pad, power your console off, then back on
#Press {{B|A}} to launch System Settings
#Navigate to <code>Data Management</code> -> <code>Nintendo 3DS</code> -> <code>Extra Data</code> ([[3ds-guide:images/screenshots/mset9/settings-extdata.png|image]])
#'''Do not press any buttons or touch the screen'''
#'''With the console STILL ON, and without pressing any buttons or touching the screen,''' remove your SD card from your console
#*The menu will refresh and say that no SD card is inserted
#Insert your SD card into your Chromebook
#Select your SD card on the sidebar on the left in the Files application
#In the DevTools Console window, type <code>restart</code> and press Enter to run the MSET9-ChromeOS script
#*If you closed the Files window or the DevTools Console window, this will not work
#*Instead, you should redo Section I Steps 3 through 8
#Type the characters corresponding to your console model and version, then press Enter
#In the DevTools Console window, type <code>c</code>, then press Enter to inject MSET9
#*You should see "MSET9 successfully injected!"
#Eject the SD card from the Chromebook, either by typing <code>eject</code> into the DevTools Console or by selecting the eject icon in the Files app
#Reinsert your SD card into your console '''without pressing any buttons or touching the screen'''
#If the exploit was successful, you will have booted into SafeB9SInstaller

===Section III - Installing boot9strap===
In this section, you will install custom firmware onto your console.
#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, [[3ds-guide:troubleshooting-mset9.html|follow this troubleshooting guide]]
#Once it is complete, press {{B|A}} to reboot your console
#Your device 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 your device shuts down when you try to power it on, ensure that you have copied <code>boot.firm</code> from the MSET9 <code>.zip</code> to the root of your SD card
#Press (Start) to save and reboot

===Section IV - Removing MSET9===
In this section, you will remove MSET9 to prevent further issues and to restore your user data (games, themes, etc). (This will not remove the custom firmware that you have just installed.)
{{Warning|text=Do NOT skip this section! If you skip it, applications may crash unexpectedly and you will encounter errors on the next page!}}
#Power off your console
#Insert your SD card into your Chromebook
#Select your SD card on the sidebar on the left in the Files application
#In the DevTools Console window, type <code>restart</code> and press Enter to run the MSET9-ChromeOS script
#*If you closed the Files window or the DevTools Console window, this will not work
#*Instead, you should redo Section I Steps 3 through 8
#Type the characters corresponding to your console model and version, then press Enter
#*The current state should display <code>Injected</code>
#*If you have already removed the trigger file (or never injected in the first place), the current state will show <code>Ready</code>, skip to Step 7
#Type <code>d</code>, then press Enter to remove the trigger file
#*You should see "Removed trigger file."
#Type <code>e</code>, then press Enter to remove MSET9
#*You should see "Successfully removed MSET9!"
{{Info|text=You can '''now''' close the DevTools Console window and the Files application.}}
At this point, your console will boot to Luma3DS by default.

*Luma3DS does not look any different from the normal HOME Menu. If your console has booted into the HOME Menu, it is running custom firmware.
*On the next page, you will install useful homebrew applications to complete your setup.
-----

{{Warning|text=Did you follow Section IV (Removing MSET9)? That section is MANDATORY!}}
Continue to [[3dsguide:finalizing-setup|Finalizing Setup]]

3DS:Alternate Exploits/Installing boot9strap (MSET9-ChromeOS)

2024-11-04T22:59:47Z

ManiacOfHomebrew: whoops 2.0

==Required Reading==
This is an alternative to the normal MSET9 Play Store guide that ChromeOS and Android devices would normally use. This version ports over the new features of MSET9 v2.0 and features a script that looks far more similar to the one used in the MSET9 CLI guide.

==Compatibility Notes==
{{Warning|text=This script is only compatible with Chromebooks and other devices running ChromeOS. If you are on a Windows, Mac, or Linux device, you should follow the [https://3ds.hacks.guide/installing-boot9strap-(mset9-cli).html MSET9 CLI guide] instead. If you are on an Android device, you should follow the [https://3ds.hacks.guide/installing-boot9strap-(mset9-play-store).html MSET9 Play Store guide] instead. If you do not have access to any of these devices, you will need to use an [[3DS:Alternate Exploits|alternate exploit]].}}

==What You Need==

*The latest version of [https://github.com/hacks-guide/MSET9/releases/latest MSET9]

==Instructions==
{{Info|text=On this page, you will use the MSET9-ChromeOS script, which is used to trigger MSET9. While the script is in progress, user data will temporarily disappear but will return upon the completion of this page. If you get an error when running the script, please join [https://discord.gg/MWxPgEp Nintendo Homebrew on Discord] and ping <code>@_themaniac</code> for assistance.}}

===Section I - Prep Work===
In this section, you will prepare the MSET9 exploit by temporarily creating a new HOME Menu profile with no user data, and then setting up that profile with only the minimum data required for MSET9 to trigger. Your existing user data will disappear, but will come back when you are finished with this page.

#Insert your SD card into your Chromebook
#Open the MSET9 <code>.zip</code> file from your Downloads folder, and copy everything inside to the root of your SD card
#*Before copying, ensure that none of the files inside the ZIP are already on the SD card. If they are, delete them
#Go to [https://maniacofgithub.github.io/mset9-chromeos/ this website] and click "Copy!" to copy the script to your clipboard
# Open the ChromeOS Files application by pressing {{B|Alt|Shift|M}} on your keyboard
#Select your SD card on the sidebar on the left in the Files application
#Open the DevTools Console for the Files application by pressing {{B|Ctrl|Shift|J}} on your keyboard
#*You may want to maximize this window to make it easier to read
#*Do not close this window or the Files application until you are told to do so
#Click to the right of the right arrow on the left side of this menu. Your cursor should start blinking
#Press {{B|Ctrl|V}} to paste the code then push Enter to run the MSET9-ChromeOS script
#*If you see a warning about not pasting code into the console that you do not understand, type <code>allow pasting</code> and then push Enter. Then, retry this step
#*This script does not contain malware, sends no data to any server, and does not even require an internet connection. If you wish, you can read the code on the site where you copied it from to verify this
#Type the characters corresponding to your console model and version, then press Enter
#*Ensure that the correct console model and version is displayed
#Type <code>a</code>, then press Enter to begin the process of creating the MSET9 ID1
#After reading the disclaimer, type <code>a</code> again and press Enter to accept it
#*If you see the message "Created hacked ID1.", you are ready to continue the guide
#*Your 3DS will appear to have no data / no user-installed apps on HOME Menu. '''This is expected.''' Your data will come back at a later step
#Eject the SD card from the Chromebook, either by typing <code>eject</code> into the DevTools Console or by selecting the eject icon in the Files app
#Reinsert your SD card into the console
#Power on your console
#Open Mii Maker
#Wait for your console to reach the [[3ds-guide:images/screenshots/mset9/mii-welcome.png|Welcome to Mii Maker]] screen, then exit Mii Maker and return to the HOME Menu
#*You may see [[3ds-guide:images/screenshots/mset9/mii-extdata.png|this screen]], which indicates the necessary data has been created
#*If you just reach the [[3ds-guide:images/screenshots/mset9/mii-existing.png|normal]] Mii Maker screen, then the data already exists. Exit Mii Maker and return to the HOME Menu
#Launch System Settings and navigate to <code>Data Management</code> -> <code>Nintendo 3DS</code> -> <code>Software</code> -> <code>Reset</code> ([[3ds-guide:images/screenshots/database-reset.jpg|image]])
#*This will not wipe any of your data
#Power off your console by pressing the power button then tapping Power Off on the lower screen
#Insert your SD card into your Chromebook
#Select your SD card on the sidebar on the left in the Files application
#In the DevTools Console window, type <code>restart</code> and press Enter to run the MSET9-ChromeOS script
#*If you closed the Files window or the DevTools Console window, this will not work
#*Instead, you should redo Section I Steps 3 through 8
#Type the characters corresponding to your console model and version, then press Enter
#*The window should change to this and display <code>Ready</code>
#**(Image coming soon)
#*If the window says <code>Not ready - check MSET9 status for more details</code>:
#**Type <code>b</code>, then press Enter to check the MSET9 status and follow the directions indicated
#**Once you have resolved the issue, return to Section I Step 19
#Type <code>z</code>, then press Enter to close the script
#*Do not close the window
#Eject the SD card from the Chromebook, either by typing <code>eject</code> into the DevTools Console or by selecting the eject icon in the Files app
#Reinsert your SD card into your console

===Section II - MSET9===
In this section, you will trigger MSET9 to launch SafeB9SInstaller (the custom firmware installer).
{{Warning|text=These instructions must be followed '''EXACTLY''', so double-check EVERYTHING you are doing to avoid errors!}}
#Power on your console, ensuring System Settings is selected
#*If System Settings is not selected, [[3ds-guide:images/screenshots/mset9/hover-settings.png|hover over]] the System Settings icon using the D-Pad, power your console off, then back on
#Press {{B|A}} to launch System Settings
#Navigate to <code>Data Management</code> -> <code>Nintendo 3DS</code> -> <code>Extra Data</code> ([[3ds-guide:images/screenshots/mset9/settings-extdata.png|image]])
#'''Do not press any buttons or touch the screen'''
#'''With the console STILL ON, and without pressing any buttons or touching the screen,''' remove your SD card from your console
#*The menu will refresh and say that no SD card is inserted
#Insert your SD card into your Chromebook
#Select your SD card on the sidebar on the left in the Files application
#In the DevTools Console window, type <code>restart</code> and press Enter to run the MSET9-ChromeOS script
#*If you closed the Files window or the DevTools Console window, this will not work
#*Instead, you should redo Section I Steps 3 through 8
#Type the characters corresponding to your console model and version, then press Enter
#In the DevTools Console window, type <code>c</code>, then press Enter to inject MSET9
#*You should see "MSET9 successfully injected!"
#Eject the SD card from the Chromebook, either by typing <code>eject</code> into the DevTools Console or by selecting the eject icon in the Files app
#Reinsert your SD card into your console '''without pressing any buttons or touching the screen'''
#If the exploit was successful, you will have booted into SafeB9SInstaller

===Section III - Installing boot9strap===
In this section, you will install custom firmware onto your console.
#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, [[3ds-guide:troubleshooting-mset9.html|follow this troubleshooting guide]]
#Once it is complete, press {{B|A}} to reboot your console
#Your device 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 your device shuts down when you try to power it on, ensure that you have copied <code>boot.firm</code> from the MSET9 <code>.zip</code> to the root of your SD card
#Press (Start) to save and reboot

===Section IV - Removing MSET9===
In this section, you will remove MSET9 to prevent further issues and to restore your user data (games, themes, etc). (This will not remove the custom firmware that you have just installed.)
{{Warning|text=Do NOT skip this section! If you skip it, applications may crash unexpectedly and you will encounter errors on the next page!}}
#Power off your console
#Insert your SD card into your Chromebook
#Select your SD card on the sidebar on the left in the Files application
#In the DevTools Console window, type <code>restart</code> and press Enter to run the MSET9-ChromeOS script
#*If you closed the Files window or the DevTools Console window, this will not work
#*Instead, you should redo Section I Steps 3 through 8
#Type the characters corresponding to your console model and version, then press Enter
#*The current state should display <code>Injected</code>
#*If you have already removed the trigger file (or never injected in the first place), the current state will show <code>Ready</code>, skip to Step 7
#Type <code>d</code>, then press Enter to remove the trigger file
#*You should see "Removed trigger file."
#Type <code>e</code>, then press Enter to remove MSET9
#*You should see "Successfully removed MSET9!"
{{Info|text=You can '''now''' close the DevTools Console window and the Files application.}}
At this point, your console will boot to Luma3DS by default.

*Luma3DS does not look any different from the normal HOME Menu. If your console has booted into the HOME Menu, it is running custom firmware.
*On the next page, you will install useful homebrew applications to complete your setup.
-----

{{Warning|text=Did you follow Section IV (Removing MSET9)? That section is MANDATORY!}}
Continue to [[3dsguide:finalizing-setup|Finalizing Setup]]

3DS:Alternate Exploits/Installing boot9strap (MSET9-ChromeOS)

2024-11-04T22:58:14Z

ManiacOfHomebrew: Whoops

==Required Reading==
This is an alternative to the normal MSET9 Play Store guide that ChromeOS and Android devices would normally use. This version ports over the new features of MSET9 v2.0 and features a script that looks far more similar to the one used in the MSET9 CLI guide.

==Compatibility Notes==
{{Warning|text=This script is only compatible with Chromebooks and other devices running ChromeOS. If you are on a Windows, Mac, or Linux device, you should follow the [https://3ds.hacks.guide/installing-boot9strap-(mset9-cli).html MSET9 CLI guide] instead. If you are on an Android device, you should follow the [https://3ds.hacks.guide/installing-boot9strap-(mset9-play-store).html MSET9 Play Store guide] instead. If you do not have access to any of these devices, you will need to use an [[3DS:Alternate Exploits|alternate exploit]].}}

==What You Need==

*The latest version of [https://github.com/hacks-guide/MSET9/releases/latest MSET9]

==Instructions==
{{Info|text=On this page, you will use the MSET9-ChromeOS script, which is used to trigger MSET9. While the script is in progress, user data will temporarily disappear but will return upon the completion of this page. If you get an error when running the script, please join [https://discord.gg/MWxPgEp Nintendo Homebrew on Discord] and ping <code>@_themaniac</code> for assistance.}}

===Section I - Prep Work===
In this section, you will prepare the MSET9 exploit by temporarily creating a new HOME Menu profile with no user data, and then setting up that profile with only the minimum data required for MSET9 to trigger. Your existing user data will disappear, but will come back when you are finished with this page.

#Insert your SD card into your Chromebook
#Open the MSET9 <code>.zip</code> file from your Downloads folder, and copy everything inside to the root of your SD card
#*Before copying, ensure that none of the files inside the ZIP are already on the SD card. If they are, delete them
#Go to [https://maniacofgithub.github.io/mset9-chromeos/ this website] and click "Copy!" to copy the script to your clipboard
# Open the ChromeOS Files application by pressing {{B|Alt|Shift|M}} on your keyboard
#Select your SD card on the sidebar on the left in the Files application
#Open the DevTools Console for the Files application by pressing {{B|Ctrl|Shift|J}} on your keyboard
#*You may want to maximize this window to make it easier to read
#*Do not close this window or the Files application until you are told to do so
#Click to the right of the right arrow on the left side of this menu. Your cursor should start blinking
#Press {{B|Ctrl|V}} to paste the code then push Enter to run the MSET9-ChromeOS script
#*If you see a warning about not pasting code into the console that you do not understand, type <code>allow pasting</code> and then push Enter. Then, retry this step
#*This script does not contain malware, sends no data to any server, and does not even require an internet connection. If you wish, you can read the code on the site where you copied it from to verify this
#Type the characters corresponding to your console model and version, then press Enter
#*Ensure that the correct console model and version is displayed
#Type <code>a</code>, then press Enter to begin the process of creating the MSET9 ID1
#After reading the disclaimer, type <code>a</code> again and press Enter to accept it
#*If you see the message "Created hacked ID1.", you are ready to continue the guide
#*Your 3DS will appear to have no data / no user-installed apps on HOME Menu. '''This is expected.''' Your data will come back at a later step
#Eject the SD card from the Chromebook, either by typing <code>eject</code> into the DevTools Console or by selecting the eject icon in the Files app
#Reinsert your SD card into the console
#Power on your console
#Open Mii Maker
#Wait for your console to reach the [[3ds-guide:images/screenshots/mset9/mii-welcome.png|Welcome to Mii Maker]] screen, then exit Mii Maker and return to the HOME Menu
#*You may see [[3ds-guide:images/screenshots/mset9/mii-extdata.png|this screen]], which indicates the necessary data has been created
#*If you just reach the [[3ds-guide:images/screenshots/mset9/mii-existing.png|normal]] Mii Maker screen, then the data already exists. Exit Mii Maker and return to the HOME Menu
#Launch System Settings and navigate to <code>Data Management</code> -> <code>Nintendo 3DS</code> -> <code>Software</code> -> <code>Reset</code> ([[3ds-guide:images/screenshots/database-reset.jpg|image]])
#*This will not wipe any of your data
#Power off your console by pressing the power button then tapping Power Off on the lower screen
#Insert your SD card into your Chromebook
#Select your SD card on the sidebar on the left in the Files application
#In the DevTools Console window, type <code>restart</code> and press Enter to run the MSET9-ChromeOS script
#*If you closed the Files window or the DevTools Console window, this will not work
#*Instead, you should redo Section I Steps 3 through 8
#Type the characters corresponding to your console model and version, then press Enter
#*The window should change to this and display <code>Ready</code>
#**(Image coming soon)
#*If the window says <code>Not ready - check MSET9 status for more details</code>:
#**Type <code>b</code>, then press Enter to check the MSET9 status and follow the directions indicated
#**Once you have resolved the issue, return to Section I Step 19
#Type <code>z</code>, then press Enter to close the script
#*Do not close the window
#Eject the SD card from the Chromebook, either by typing <code>eject</code> into the DevTools Console or by selecting the eject icon in the Files app
#Reinsert your SD card into your console

===Section II - MSET9===
In this section, you will trigger MSET9 to launch SafeB9SInstaller (the custom firmware installer).
{{Warning|text=These instructions must be followed '''EXACTLY''', so double-check EVERYTHING you are doing to avoid errors!}}
#Power on your console, ensuring System Settings is selected
#*If System Settings is not selected, [[3ds-guide:images/screenshots/mset9/hover-settings.png|hover over]] the System Settings icon using the D-Pad, power your console off, then back on
#Press {{B|A}} to launch System Settings
#Navigate to <code>Data Management</code> -> <code>Nintendo 3DS</code> -> <code>Extra Data</code> ([[3ds-guide:images/screenshots/mset9/settings-extdata.png|image]])
#'''Do not press any buttons or touch the screen'''
#'''With the console STILL ON, and without pressing any buttons or touching the screen,''' remove your SD card from your console
#*The menu will refresh and say that no SD card is inserted
#Insert your SD card into your Chromebook
#Select your SD card on the sidebar on the left in the Files application
#In the DevTools Console window, type <code>restart</code> and press Enter to run the MSET9-ChromeOS script
#*If you closed the Files window or the DevTools Console window, this will not work
#*Instead, you should redo Section I Steps 3 through 8
#Type the characters corresponding to your console model and version, then press Enter
#In the DevTools Console window, type <code>c</code>, then press Enter to inject MSET9
#*You should see "MSET9 successfully injected!"
#Eject the SD card from the Chromebook, either by typing <code>eject</code> into the DevTools Console or by selecting the eject icon in the Files app
#Reinsert your SD card into your console '''without pressing any buttons or touching the screen'''
#If the exploit was successful, you will have booted into SafeB9SInstaller

===Section III - Installing boot9strap===
In this section, you will install custom firmware onto your console.
#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, [[3ds-guide:troubleshooting-mset9.html|follow this troubleshooting guide]]
#Once it is complete, press {{B|A}} to reboot your console
#Your device 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 your device shuts down when you try to power it on, ensure that you have copied <code>boot.firm</code> from the MSET9 <code>.zip</code> to the root of your SD card
#Press (Start) to save and reboot

===Section IV - Removing MSET9===
In this section, you will remove MSET9 to prevent further issues and to restore your user data (games, themes, etc). (This will not remove the custom firmware that you have just installed.)
{{Warning|text=Do NOT skip this section! If you skip it, applications may crash unexpectedly and you will encounter errors on the next page!}}
#Power off your console
#Insert your SD card into your Chromebook
#Select your SD card on the sidebar on the left in the Files application
#In the DevTools Console window, type <code>restart</code> and press Enter to run the MSET9-ChromeOS script
#*If you closed the Files window or the DevTools Console window, this will not work
#*Instead, you should redo Section I Steps 3 through 8
#Type the characters corresponding to your console model and version, then press Enter
#*The current state should display <code>Injected</code>
#*If you have already removed the trigger file (or never injected in the first place), the current state will show <code>Ready</code>, skip to Step 6
#Type <code>d</code>, then press Enter to remove the trigger file
#*You should see "Removed trigger file."
#Type <code>e</code>, then press Enter to remove MSET9
#*You should see "Successfully removed MSET9!"
{{Info|text=You can '''now''' close the DevTools Console window and the Files application.}}
At this point, your console will boot to Luma3DS by default.

*Luma3DS does not look any different from the normal HOME Menu. If your console has booted into the HOME Menu, it is running custom firmware.
*On the next page, you will install useful homebrew applications to complete your setup.
-----

{{Warning|text=Did you follow Section IV (Removing MSET9)? That section is MANDATORY!}}
Continue to [[3dsguide:finalizing-setup|Finalizing Setup]]

3DS:Alternate Exploits/Installing boot9strap (MSET9-ChromeOS)

2024-11-04T22:57:38Z

ManiacOfHomebrew: Complete MSET9-ChromeOS guide

==Required Reading==
This is an alternative to the normal MSET9 Play Store guide that ChromeOS and Android devices would normally use. This version ports over the new features of MSET9 v2.0 and features a script that looks far more similar to the one used in the MSET9 CLI guide.

==Compatibility Notes==
{{Warning|text=This script is only compatible with Chromebooks and other devices running ChromeOS. If you are on a Windows, Mac, or Linux device, you should follow the [https://3ds.hacks.guide/installing-boot9strap-(mset9-cli).html MSET9 CLI guide] instead. If you are on an Android device, you should follow the [https://3ds.hacks.guide/installing-boot9strap-(mset9-play-store).html MSET9 Play Store guide] instead. If you do not have access to any of these devices, you will need to use an [[3DS:Alternate Exploits|alternate exploit]].}}

==What You Need==

*The latest version of [https://github.com/hacks-guide/MSET9/releases/latest MSET9]

==Instructions==
{{Info|text=On this page, you will use the MSET9-ChromeOS script, which is used to trigger MSET9. While the script is in progress, user data will temporarily disappear but will return upon the completion of this page. If you get an error when running the script, please join [https://discord.gg/MWxPgEp Nintendo Homebrew on Discord] and ping <code>@_themaniac</code> for assistance.}}

===Section I - Prep Work===
In this section, you will prepare the MSET9 exploit by temporarily creating a new HOME Menu profile with no user data, and then setting up that profile with only the minimum data required for MSET9 to trigger. Your existing user data will disappear, but will come back when you are finished with this page.

#Insert your SD card into your Chromebook
#Open the MSET9 <code>.zip</code> file from your Downloads folder, and copy everything inside to the root of your SD card
#*Before copying, ensure that none of the files inside the ZIP are already on the SD card. If they are, delete them
#Go to [https://maniacofgithub.github.io/mset9-chromeos/ this website] and click "Copy!" to copy the script to your clipboard
# Open the ChromeOS Files application by pressing {{B|Alt|Shift|M}} on your keyboard
#Select your SD card on the sidebar on the left in the Files application
#Open the DevTools Console for the Files application by pressing {{B|Ctrl|Shift|J}} on your keyboard
#*You may want to maximize this window to make it easier to read
#*Do not close this window or the Files application until you are told to do so
#Click to the right of the right arrow on the left side of this menu. Your cursor should start blinking
#Press {{B|Ctrl|V}} to paste the code then push Enter to run the MSET9-ChromeOS script
#*If you see a warning about not pasting code into the console that you do not understand, type <code>allow pasting</code> and then push Enter. Then, retry this step
#*This script does not contain malware, sends no data to any server, and does not even require an internet connection. If you wish, you can read the code on the site where you copied it from to verify this
#Type the characters corresponding to your console model and version, then press Enter
#*Ensure that the correct console model and version is displayed
#Type <code>a</code>, then press Enter to begin the process of creating the MSET9 ID1
#After reading the disclaimer, type <code>a</code> again and press Enter to accept it
#*If you see the message "Created hacked ID1.", you are ready to continue the guide
#*Your 3DS will appear to have no data / no user-installed apps on HOME Menu. '''This is expected.''' Your data will come back at a later step
#Eject the SD card from the Chromebook, either by typing <code>eject</code> into the DevTools Console or by selecting the eject icon in the Files app
#Reinsert your SD card into the console
#Power on your console
#Open Mii Maker
#Wait for your console to reach the [[3ds-guide:images/screenshots/mset9/mii-welcome.png|Welcome to Mii Maker]] screen, then exit Mii Maker and return to the HOME Menu
#*You may see [[3ds-guide:images/screenshots/mset9/mii-extdata.png|this screen]], which indicates the necessary data has been created
#*If you just reach the [[3ds-guide:images/screenshots/mset9/mii-existing.png|normal]] Mii Maker screen, then the data already exists. Exit Mii Maker and return to the HOME Menu
#Launch System Settings and navigate to <code>Data Management</code> -> <code>Nintendo 3DS</code> -> <code>Software</code> -> <code>Reset</code> ([[3ds-guide:images/screenshots/database-reset.jpg|image]])
#*This will not wipe any of your data
#Power off your console by pressing the power button then tapping Power Off on the lower screen
#Insert your SD card into your Chromebook
#Select your SD card on the sidebar on the left in the Files application
#In the DevTools Console window, type <code>restart</code> and press Enter to run the MSET9-ChromeOS script
#*If you closed the Files window or the DevTools Console window, this will not work
#*Instead, you should redo Section I Steps 3 through 8
#Type the characters corresponding to your console model and version, then press Enter
#*The window should change to this and display <code>Ready</code>
#**(Image coming soon)
#*If the window says <code>Not ready - check MSET9 status for more details</code>:
#**Type <code>b</code>, then press Enter to check the MSET9 status and follow the directions indicated
#**Once you have resolved the issue, return to Section I Step 19
#Type <code>z</code>, then press Enter to close the script
#*Do not close the window
#Eject the SD card from the Chromebook, either by typing <code>eject</code> into the DevTools Console or by selecting the eject icon in the Files app
#Reinsert your SD card into your console

===Section II - MSET9===
In this section, you will trigger MSET9 to launch SafeB9SInstaller (the custom firmware installer).
{{Warning|Text=These instructions must be followed '''EXACTLY''', so double-check EVERYTHING you are doing to avoid errors!}}
#Power on your console, ensuring System Settings is selected
#*If System Settings is not selected, [[3ds-guide:images/screenshots/mset9/hover-settings.png|hover over]] the System Settings icon using the D-Pad, power your console off, then back on
#Press {{B|A}} to launch System Settings
#Navigate to <code>Data Management</code> -> <code>Nintendo 3DS</code> -> <code>Extra Data</code> ([[3ds-guide:images/screenshots/mset9/settings-extdata.png|image]])
#'''Do not press any buttons or touch the screen'''
#'''With the console STILL ON, and without pressing any buttons or touching the screen,''' remove your SD card from your console
#*The menu will refresh and say that no SD card is inserted
#Insert your SD card into your Chromebook
#Select your SD card on the sidebar on the left in the Files application
#In the DevTools Console window, type <code>restart</code> and press Enter to run the MSET9-ChromeOS script
#*If you closed the Files window or the DevTools Console window, this will not work
#*Instead, you should redo Section I Steps 3 through 8
#Type the characters corresponding to your console model and version, then press Enter
#In the DevTools Console window, type <code>c</code>, then press Enter to inject MSET9
#*You should see "MSET9 successfully injected!"
#Eject the SD card from the Chromebook, either by typing <code>eject</code> into the DevTools Console or by selecting the eject icon in the Files app
#Reinsert your SD card into your console '''without pressing any buttons or touching the screen'''
#If the exploit was successful, you will have booted into SafeB9SInstaller

===Section III - Installing boot9strap===
In this section, you will install custom firmware onto your console.
#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, [[3ds-guide:troubleshooting-mset9.html|follow this troubleshooting guide]]
#Once it is complete, press {{B|A}} to reboot your console
#Your device 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 your device shuts down when you try to power it on, ensure that you have copied <code>boot.firm</code> from the MSET9 <code>.zip</code> to the root of your SD card
#Press (Start) to save and reboot

===Section IV - Removing MSET9===
In this section, you will remove MSET9 to prevent further issues and to restore your user data (games, themes, etc). (This will not remove the custom firmware that you have just installed.)
{{Warning|text=Do NOT skip this section! If you skip it, applications may crash unexpectedly and you will encounter errors on the next page!}}
#Power off your console
#Insert your SD card into your Chromebook
#Select your SD card on the sidebar on the left in the Files application
#In the DevTools Console window, type <code>restart</code> and press Enter to run the MSET9-ChromeOS script
#*If you closed the Files window or the DevTools Console window, this will not work
#*Instead, you should redo Section I Steps 3 through 8
#Type the characters corresponding to your console model and version, then press Enter
#*The current state should display <code>Injected</code>
#*If you have already removed the trigger file (or never injected in the first place), the current state will show <code>Ready</code>, skip to Step 6
#Type <code>d</code>, then press Enter to remove the trigger file
#*You should see "Removed trigger file."
#Type <code>e</code>, then press Enter to remove MSET9
#*You should see "Successfully removed MSET9!"
{{Info|text=You can '''now''' close the DevTools Console window and the Files application.}}
At this point, your console will boot to Luma3DS by default.

*Luma3DS does not look any different from the normal HOME Menu. If your console has booted into the HOME Menu, it is running custom firmware.
*On the next page, you will install useful homebrew applications to complete your setup.
-----

{{Warning|text=Did you follow Section IV (Removing MSET9)? That section is MANDATORY!}}
Continue to [[3dsguide:finalizing-setup|Finalizing Setup]]

3DS:Alternate Exploits/Installing boot9strap (MSET9-ChromeOS)

2024-11-04T15:38:35Z

ManiacOfHomebrew: Start making the MSET9-ChromeOS guide

3DS:Remove Parental Controls

2024-08-16T13:05:56Z

ManiacOfHomebrew: Change mkey link

{{shortcut|3DS:RMPC}}
This page is about how to remove Parental Controls, assuming you do not know the PIN or the answer to the secret question.

{{warning|text='''Disclaimer:''' You should only do this on consoles that you fully own or where you have been granted permission. We are not liable for any consequences that may come from removing Parental Controls on someone else's console.}}

== With homebrew (CFW required) ==

[[udb:3ds/3ds-parentalunlock|3DS-ParentalUnlock]] can remove Parental Controls.

{{info|text=If you cannot enter Homebrew Launcher due to Parental Controls, try using a different target title to load homebrew: [[3DS:Troubleshooting/manually entering homebrew launcher]]}}

== Using mkey generator (CFW not required) ==

This method does not require custom firmware to be installed on your device, as it uses a website to generate a master key for your device.

{{info|text=If there is a Nintendo Network ID for a child linked to the console, Parental Controls cannot be disabled with System Settings. Instead you will need to use the homebrew program [[#With homebrew (CFW required)|3DS-ParentalUnlock]]. Note that you can still set up homebrew and custom firmware even if Parental Controls are enabled.}}

#Launch System Settings on your console
#Navigate to the Parental Controls menu
#When asked if you would like to change your Parental Control settings, select "Forgot PIN"
#When asked for the answer to your secret question, select "I Forgot"
#If asked if you would like to send a master key to the e-mail address registered with the account, select "Cancel"
#*If you do not see this prompt, you should skip this step
#You should now see a screen with the title "Obtaining a master key." Open the mkey generator at [https://mkey.nintendohomebrew.com Nintendo Homebrew] and input the following information:
#*Set the "Device type" to "3DS"
#*Set the "System date" to your console's current date, displayed at the top right of the top screen
#*Leave the "Additional data" field blank
#*Set the "Inquiry number" to the number in the middle of the bottom screen
#Select the "Go" button on the website
#Select the "OK" button on the console
#Input the master key outputted at the top of the webpage.
#When asked to choose a new PIN, select "Cancel"
#Select "Clear Settings" then "Delete" to delete Parental Controls
#*If settings cannot be deleted due to a child Nintendo Network ID being linked, instead change the PIN to one that you can remember and remove it later [[#With homebrew (CFW required)|with homebrew]].

[[Category:Nintendo 3DS guides]]

Wii U:Hardmod unbrick

2024-08-15T21:01:10Z

ManiacOfHomebrew:

{{ombox|type=speedy|text=This guide is now outdated since there is a software exploit that allows unbricking without soldering! There is a guide for it [https://gbatemp.net/threads/cbhc-unbrick-guide-without-soldering.613371/ here]. UDPIH will not work if you somehow deleted OSv10 (00050010-1000400A), so you ''must'' hardmod the system.}}

__TOC__

== Start ==

Hello and welcome to the new and improved <s>freddy fazbears pizza</s> Wii U Unbrick Guide. This Guide only covers the SLC (Wii U).

Usually if you need to restore vWii NAND, there is [https://gbatemp.net/threads/release-vwii-nand-restorer.560948/ vWii NAND Restorer] (Needs backup) or [https://gbatemp.net/threads/vwii-decaffeinator-restore-vwii-without-a-nand-backup.566252/ vWii Decaffenator] (Doesn’t need backup)

Wii U doesnt have something like that yet though. so we have to open up the console and solder some wires to the NAND.

To unbrick the Wii U we will use an Rasberry Pi. I have only ever used an RPi0 but the pinouts should be the same on every RPi. If you want to use a Teensy to unbrick, refer to [https://gbatemp.net/threads/guide-kaflukes-hardmod-cbhc-unbrick-guide.476725/ this guide]

== What you need ==

* An slc.bin dump from ''before'' the brick, or an otp.bin dump.
* A Raspberry Pi and MicroSD for the Raspberry Pi.
* Decent soldering equipment.
* Decent soldering skills.
* Ability to follow instructions.
* A Lot of time.
* A Decent understanding of Linux.
* Last but not least, A Brain.


=== Setting up the software ===

# Set up RPIOS on a MicroSD. (Guide: https://www.raspberrypi.com/documentation/computers/getting-started.html)
# Power on your RPI and connect it to the internet.
# Open up a terminal (<code>CTRL ALT T</code>) and run <code>wget https://raw.githubusercontent.com/Lazr1026/unbrick/main/pinand.sh && chmod +x pinand.sh</code>
# Now run <code>./pinand.sh</code>.


=== Solder the RPI to Wii U board ===

Take apart the Wii U, look up a teardown.

Make sure you are VERY CAREFUL when soldering to these points. one mess up and your console may be dead for good.

Solder Points:

RPI:

[[File:WiiU-hardmod-RPI-pinout.png|600px]]

[[File:WiiU-hardmod-RPI-back.png|600px]]

Wii U Board:

[[File:WiiU-hardmod-RPI-solder.jpg|600px]]

It should look like this when finished.

[[File:WiiU-hardmod-done.png|600px]]


== Fixing the NAND ==

Note: Now depending on what the hell you did, you could be doing something WAY different (ie. only restoring certain pages). We will be flashing back an entire SLC image here.


=== FIXING THE NAND WITH ONLY OTP.BIN ===

Download [https://github.com/koolkdev/wiiuqt/releases/tag/v0.2 Eyekeys NAND Tools] and extract the zip somewhere on your PC.

# Put the Wii U back together enough to get everything plugged in (Disc Drive, Power Button, Fan, Heatsink.)
# Power on the Wii U.
# Turn on the RPI.
# Open up a terminal and run <code>sudo ./pinand 50 read_id</code>, you should get something like this. [[File:WiiU-hardmod-readid.png|600px]]
# Run <code>sudo ./pinand 50 read_full 0 262144 slc.bin</code>.
# Wait for it to finish reading. (DO NOT UNPLUG THE WII U OR RPI.)
# Turn off the Wii U and RPI, insert the RPI’ MicroSD in your PC.
# Copy the <code>slc.bin</code> from <code>sd:/home/[USER]</code> to the NAND Tools folder on your PC. (Hint: Now would be a REALLY good time to copy otp.bin to the folder as well.)
# Open a Command Prompt and run <code>nandCbhcRemover.exe slc.bin</code>. See the next section for flashing the NAND back to the Wii U.

=== FIXING THE NAND WITH ONLY SLC.BIN ===

# Insert the RPI’ MicroSD in your PC.
# Copy <code>slc.bin</code> to <code>sd:/home/[USER]</code>. (OTP Only Users: Click <code>Replace</code> when asked.)
# Insert the RPI’ MicroSD into the RPI.
# Turn on the Wii U.
# Turn on the RPI.
# Open a terminal and type in <code>sudo ./pinand 50 read_id</code>. You should get something like this. [[File:WiiU-hardmod-readid.png|600px]]
# Run <code>sudo ./pinand 50 erase_blocks 0 4096 && sudo ./pinand 50 write_full 0 262144 slc.bin</code>.
# Wait for it to finish, this will take a LONG time (around 2 days for an RPi0). (DO NOT UNPLUG THE WIIU OR THE RPI.)

== After Flashing ==

# Turn off the Wii U.
# Turn off the RPI.
# Put the Wii U back together enough to test if it boots, plug in Disc Drive, Power Button, Fan, Heatsink.
# Turn on the Wii U, connect an HDMI or AV (or if your Gamepad is still paired, that works too).
* If it loads to Wii U Menu, congrats, desolder the wires on the Wii U Board and put the system back together. You have successfully done the RPI Hardmod Method.
* If it does not load to Wii U Menu and Errors, then you did something wrong, or you used the wrong backup. Try Flashing again, or join [https://discord.gg/HNDcTEkcR3 Ivy’s Stuff] and ask for help in <code>#help</code>

== Credits: ==

*[https://github.com/Lazr1026/unbrick] - Created this guide.
*[https://github.com/rw-r-r-0664 rw-r-r-0644] - sending me an edited pinand and fixing it.
*[https://github.com/GaryOderNichts GaryOderNichts], [https://github.com/Nightkingale Nightkingale], and agilly1989 - Emotional support while doing this.
*[https://discord.com/invite/F2PKpEj The 4TU Discord server] - Letting me clog up their wiiu channel over this.
*[https://forums.raspberrypi.com/ RPi Forums] - Having a thread on [https://forums.raspberrypi.com/viewtopic.php?t=16775 Bit-Banging a TSOP NAND.]

[[Category:Wii U guides]]

3DS:Alternate Exploits/Homebrew Launcher (PicHaxx)

2024-07-17T16:38:00Z

ManiacOfHomebrew: /* Required Reading */

{{3DS unavailable eShop|Pokémon Picross}}{{System version outdated article|console=ctr|sysversion=11.17.0-50|reason=The otherapp payload may have been broken in the latest update.}}

==Required Reading==

[https://github.com/zoogie/pichaxx Pichaxx] is an exploit for the game Pokémon Picross released by [https://github.com/zoogie zoogie], originally discovered and [https://twitter.com/mrnbayoh/status/744899681663258624?lang=en demonstrated] by [https://github.com/MrNbaYoh MrNbaYoh]. This method of using Seedminer for further exploitation uses your <code>movable.sed</code> file to write a custom save file for Pokémon Picross, which can then be used to launch the Homebrew Launcher.

{{warning|text=This process requires your console-specific <code>movable.sed</code> file. If you don't have it yet, you can get it by following [[3DS:Seedminer|Seedminer]].}}

{{warning|text=This process will overwrite your Pokémon Picross save file, if you have one. If you wish to preserve your Pokémon Picross game data, you should make a backup of your <code>00000001.sav</code> file before overwriting it.}}

__TOC__

==What You Need==
*The game "Pokémon Picross" (free on eShop) installed on your device
**You can scan [http://api.qrserver.com/v1/create-qr-code/?color=000000&bgcolor=FFFFFF&data=ESHOP://50010000037815&margin=0&qzone=1&size=400x400&ecc=L this QR code] using the Nintendo 3DS Camera for a direct link to the eShop app
**Your SD card must be inserted in your device to install Pokémon Picross
*Your <code>movable.sed</code> file from completing Seedminer
* The latest release of [https://github.com/LumaTeam/Luma3DS/releases/latest Luma3DS] (the Luma3DS <code>.zip</code> file)
*[[Media:Otherapps.zip|otherapps.zip]]

==Instructions==

===Section I - Prep Work ===

# Power off your device
#Insert your SD card into your computer
# Copy <code>boot.firm</code> and <code>boot.3dsx</code> from the Luma3DS <code>.zip</code> 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
#Copy the otherapp payload for your region/version/model from the otherapps <code>.zip</code> file to the root of your SD card and rename it to <code>otherapp.bin</code>

===Section II - PicHaxx===
#Open [https://3dstools.nhnarwhal.com/#/pichaxx the PicHaxx Injector website] on your computer
#Select your <code>movable.sed</code> file
#Select "Build and Download"
#Wait for the process to complete
#Navigate to <code>Nintendo 3DS</code> -> <code><ID0></code> -> <code><ID1></code> -> <code>title</code> -> <code>00040000</code> -> <code>0017c100</code> -> <code>data</code> on your SD card
#*The <code><ID0></code> will be the same one that you used in [[3dsguide:seedminer|Seedminer]]
#*The <code><ID1></code> is a 32 character long folder inside of the <code><ID0></code>
#Copy the newly downloaded <code>00000001.sav</code> file to the <code>data</code> folder on your SD card
#*Overwrite the old save file when prompted
# Reinsert your SD card into your device
#Power on your device
#Launch "Pokémon Picross"
#If the exploit was successful, your device will have loaded the Homebrew Launcher
#*If you get an error message, [[3dsguide:troubleshooting#installing-boot9strap-pichaxx|follow this troubleshooting guide]]

-----

Continue to [[3DS:Alternate Exploits/Installing boot9strap (nimdsphax)|Installing boot9strap (nimdsphax)]]

[[Category:Nintendo 3DS guides]]

User:ManiacOfHomebrew/3DS 12-hour Clock

2024-07-11T00:21:48Z

ManiacOfHomebrew: add clarifications about 12-hour time, fix grammar, and "HOME Menu"

{{#approvable_by: users = ManiacOfHomebrew}}
{{Page WIP|notes=*I want to expand this to include AM/PM indicators, but I'm not sure if it'll be possible.
*In addition, I would like this to work across all applets, but that will take some time to flesh out.}}

==Required Reading==
The 3DS uses the 24-hour time format to display the time on the HOME Menu among other applets. This guide shows you how to convert the 3DS system's clock on the HUD of the HOME Menu to a 12-hour format.

{{Info|text=This will not affect other applets such as System Settings or the Nintendo eShop at the moment, meaning you will only see a 12-hour clock on the HOME Menu.}}{{Info|text=The clock will display in Japanese 12-hour time, which means that 12:00 (both midnight and noon) will be displayed as 0:00. All other hours of the day function as expected.}}

==What You Need==

*The latest version of [https://github.com/schrmh/HMRT Home Menu Rebuilding Tool]
** To download, click the green code button, and then Download ZIP.
*The latest version of [https://github.com/IcySon55/3DLandMSBTeditor/releases MSBT Editor Reloaded]
*The latest version of [[3DS:GodMode9/Usage#Updating GodMode9|GodMode9]] installed
*A computer running Windows, or Wine for Mac/Linux (Required to run MSBT Editor)

==Instructions==
{{info|text=In this guide, <code><Your language></code> is to be substituted with your consoles language selection. For example, <code>US_English</code>.}}
===Section I: Prep Work===

#Extract Home Menu Rebuilding Tool as well as MSBT Editor Reloaded to a new folder on your computer
#Press and hold {{Key press|Start}}, and while holding {{Key press|Start}}, power on your console. This will launch GodMode9
#Press {{Key press|HOME}} to bring up the action menu
#Select "Title manager"
#Select "[1:] NAND / TWL"
#Scroll down through the list and select a title labeled <code>(CTR-N-HMME)</code>. This is the HOME Menu application
#Select "Manage Title..."
#Select "Build CIA (standard)"
#Push {{Key press|A}} once it is finished
#Push {{Key press|R|Start}} to power off the console
#Insert the SD Card into your computer
#Backup the <code>.cia</code> file in the <code>gm9/out</code> folder to a safe place on your computer. It ends with <code>(CTR-N-HMME).standard.cia</code>
#Make another copy of this <code>.cia</code> file in the folder created in step 1
#Rename it to <code>HomeMenu.cia</code>
#Copy <code>HomeMenu.cia</code> to the Home Menu Rebuilding Tool folder

===Section II - Modifying===

*Open <code>HMRT.bat</code>
*Push {{Key press|1}} on your keyboard to extract the components of the Home Menu
*Push {{Key press|5}} on your keyboard to decompress the components
*Keep the window open and open <code>MsbtEditor.exe</code>
*Drag the file named <code>hud_msbt.LZ</code> from <code>ExtractedRomFS/message_hud/<Your language></code> into MsbtEditor
*Scroll down and select <code>lau_hours</code> in the list on the left
*Change <code>%H</code> to <code>%h</code> in the first text box labeled "Edit:"
*Push {{B|Ctrl|S}} to save, then close MsbtEditor

===Section III - Installing===
<tabber>
|-|Luma LayeredFS (Recommended)=

[[File:USEnglish12HourTime.png|thumb|The file structure for a US_English 12-hour time patch file.]]
#In the Home Menu Rebuilding Tool window, push {{Key press|6}} on your keyboard to recompress the components
#Close the Home Menu Rebuilding Tool window.
#On your 3ds SD Card, create the following folder corresponding to your region:
*JPN: <code>luma/titles/0004003000008202/romfs</code>
*USA: <code>luma/titles/0004003000008F02/romfs</code>
*EUR: <code>luma/titles/0004003000009802/romfs</code>
*CHN: <code>luma/titles/000400300000A102/romfs</code>
*KOR: <code>luma/titles/000400300000A902/romfs</code>
*TWN: <code>luma/titles/000400300000B102/romfs</code>
<ol start="4">
<li>Create the <code>message_hud/<Your language></code> folder inside the <code>romfs</code> folder.</li>
<li>Copy <code>hud_msbt_LZ.bin</code> from <code>ExtractedRomFS/message_hud/<Your language></code> to the new folder.</li>
<li>Eject your SD Card and put it back in the console.</li>
<li>Start your device and hold SELECT to enter the Luma3DS configuration screen</li>
<li>Press (A) on <code>( ) Enable game patching</code> to tick it (if it is not already ticked) <code>(x)</code></li>
<li>Press <code>START</code> to boot the the HOME Menu</li>
</ol>
{{success|text=The HOME Menu's clock should now be displaying 12-hour time.}}

|-|Patched CIA=

{{Warning|text=Read this box closely!
*This method is much less preferred than LayeredFS, as it makes direct edits to your system HOME Menu. Only use this as a last resort and if troubleshooting LayeredFS was not successful!
*Create/update your NAND backup! When making changes to your device, there is always the chance you will brick.
*Having a custom HOME Menu installed breaks system updates. If you want to update your system, you will have to restore your HOME Menu with a blank <code>HomeMenu.cia</code> first.}}

# In the Home Menu Rebuilding Tool window, push {{Key press|6}} on your keyboard to recompress the components
# In the Home Menu Rebuilding Tool window, push {{Key press|2}} on your keyboard to rebuild the HomeMenu CIA.
# Copy the outputted <code>HomeMenu_edited.cia</code> file to the root of the SD card
# Press and hold {{Key press|Start}}, and while holding {{Key press|Start}}, power on your console. This will launch GodMode9
# Navigate to the <code>[0:] SDCARD</code> drive, then select the <code>HomeMenu_edited.cia</code> file
# Select "CIA Image options..."
# Select "Encrypt file (...)"
# Select "Encrypt inplace"
# After it is finished, push {{Key press|A}} to continue
# Select the <code>HomeMenu_edited.cia</code> file again
# Select "CIA Image options..."
# Select "Install game image"
# Press {{Key press|A}} to unlock SysNAND (lvl1) writing, then input the key combo given
# Push {{Key press|A}} twice then {{Key press|Start}} to reboot

{{success|text=The HOME Menu's clock should now be displaying 12-hour time.}}
</tabber>

{{info|text=If the HOME menu does not boot or you encounter any other problem, it is recommended that you ask for help on the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord server] in one of the 3DS assistance channels, mentioning that you were following this guide.}}

3DS:Universal-Updater

2024-05-17T00:48:11Z

ManiacOfHomebrew: extra info i guess

{{Page WIP}}{{Infobox homebrew
| image = Universal-Updater-Banner.png
| imagealt = Universal-Updater banner on the Home Menu
| developers = Universal-Team
| for3ds = 1
| version = 3.2.6
| releasedate = 2022-11-21
| github = Universal-Team/Universal-Updater
| universaldb = 3ds/universal-updater
| githubtag = v3.2.6
}}
'''Universal-Updater''' is a homebrew browser that supports installing and updating homebrew software. It connects to [[udb:|Universal-DB]] by default.

== Features ==
* Browse homebrew applications and view information such as version number, release notes, screenshots and more.
* Universal-Updater will automatically download, extract, rename, and place files for simple one click installation of apps.
* Continue browsing while apps install and queue multiple downloads for batch installs.
* Download directories can be customized for various file types to fit your setup.
* Displays an indicator when a newer version of an application is available.
* Sort and search for homebrew, or add markers to easily find your favorite homebrew apps.
* Change UniStores to view different repositories such as TWiLight Menu++ skins or create your own.
* Universal-Updater has support for over twenty languages.

== Installation ==

{{info|Universal-Updater is installed as part of [[3dsguide:finalizing-setup|Finalizing Setup]] on 3DS Hacks Guide. It is also on [[udb:3ds/universal-updater|Universal-DB]] and automatically updates itself.}}

<tabber>
|-|FBI QR code=

=== What You Need ===

* [[3DS:FBI|FBI]] installed on your console

=== Instructions ===

{{FBI QR code
| name1 = CIA
| url1 = https://github.com/Universal-Team/Universal-Updater/releases/latest/download/Universal-Updater.cia
| name2 = 3DSX
| url2 = https://github.com/Universal-Team/Universal-Updater/releases/latest/download/Universal-Updater.3dsx
}}

|-|Manually (CIA)=

=== What You Need ===

* The latest release of {{GitHub|Universal-Team/Universal-Updater/releases/latest|Universal-Updater}} (the <code>.cia</code> file)

=== Instructions ===

#Insert your SD card into your computer
#Copy <code>Universal-Updater.cia</code> to the <code>cias</code> folder on your SD card
#*Create the folder if it does not exist; it is for organization purposes
#Insert your SD card into your console
#Power on your console
#Launch FBI
#Navigate to <code>SD</code> -> <code>cias</code>
#Press {{B|A}} while <code>Universal-Updater.cia</code> is selected, then select <code>Install and delete CIA(s)</code>
#Wait for the process to complete
#Exit FBI

|-|Manually (3DSX)=

=== What You Need ===

* The latest release of {{GitHub|Universal-Team/Universal-Updater/releases/latest|Universal-Updater}} (the <code>.3dsx</code> file)

=== Instructions ===

#Insert your SD card into your computer
#Copy <code>Universal-Updater.3dsx</code> to the <code>3ds</code> folder on your SD card
#Insert your SD card into your console
#Power on your console

</tabber>

== Usage ==
===Main menu===
* '''Information icon''': Browse homebrew apps using the directional controls and view screenshots or release notes by tapping the icons on the lower screen. Tap on the star icon to add markers to apps that can be used as a filter in search.
* '''Download icon''': View available downloads for the currently selected app. This menu is automatically displayed upon selecting an entry with the A button. An SD card icon indicates that the entry has been downloaded before. Tapping the SD card icon will tell Universal-Updater that that entry is no longer installed. (It will no longer show an update indicator.)
* '''Queue icon''': View the status of the current downloads. Some download entries will also need to be interacted with for optional installs, indicated by "Action Required!" in the progress bar. Tapping the progress bar will switch it from displaying the progress of the entire installation to the progress of the current step of the installation.
* '''Search icon''': Search for apps by title, author, category, or console. Apply filters to your search from user added markers, or filter by apps that have new updates. You can add your search selection to the download queue to easily install many apps at once.
* '''Sort icon''': Sort entries by title, author, or last updated. You can also switch the sort order from ascending or descending, and change between a grid or list of apps.
* '''Gear icon''': Change various settings, view credits, or exit Universal-Updater

===Settings===
* '''Language''': Change the language of Universal-Updater's menus from over twenty languages. There may even be a silly one, Bruh!
* '''Select UniStore''': Change the repository that Universal-Updater downloads from. Press start to manually update the currently highlighted UniStore. Tap the (+) to add more Unistores; select from the list, scan a QR code, or enter the URL of a UniStore to add your own.
* '''Auto-update settings''': Change whether Universal-Updater automatically updates itself and its UniStores. You can also have Universal-Updater use a nightly version for updates instead of stable releases.
* '''GUI settings''': Select if you want to use custom backgrounds of UniStores, or if you want to use a custom font, instead of the default system font. Select custom themes to use, more information [https://github.com/Universal-Team/Universal-Updater/wiki/custom-themes here].
* '''Directory settings''': Change what directories certain files are placed in. You can also choose if 3dsx file are placed in a folder with their own name.
* '''Credits''': View the credits for the people who worked on the app. The current version of the app can be found in this screen.
* '''Exit Universal-Updater''': Closes Universal-Updater. This can also be done by pressing start in the main menu.

== See also ==
[https://github.com/Universal-Team/Universal-Updater/wiki Universal-Updater wiki on GitHub]

{{Short description|Homebrew browser and updater}}

3DS:Custom themes

2024-05-15T01:35:17Z

ManiacOfHomebrew: dont have to install anemone3ds if you already have it, other minor changes

{{hatnote|1=This article only details how to apply custom themes. If you wish to create one of your own instead, see [[3DS:Custom themes/creation|the theme creation page]] instead.}}

'''Custom themes''' are a set of graphics and sounds that can be applied to your HOME Menu to give it a bit more personality. They are built on the same framework as the official themes that can be found on Nintendo's theme shop.

Custom themes are available on USA, EUR, and JPN firmwares. They are partially implemented but inaccessible on KOR firmwares, and entirely unimplemented in CHN and TWN firmwares.

== Installation ==
Custom themes can be managed with a homebrew software called [[3DS:Anemone3DS|Anemone3DS]].

=== What you need ===
* The latest release of {{GitHub|astronautlevel2/Anemone3DS/releases/latest|Anemone3DS}}
*A 3DS on USA/EUR/JPN firmware (if your 3DS UI isn't in Korean or Chinese, you're good to go)

=== Section I: Prep Work===
{{Info|text=If you already have Anemone3DS installed (from Finalizing Setup or elsewhere), then you may skip this section.}}
#Insert your SD card into your computer
#Copy <code>Anemone3DS.cia</code> to the <code>cias</code> folder on your SD card
#*Create the folder if it does not exist; it is for organization purposes
#*Alternatively, if you want to run Anemone3DS from the Homebrew launcher, copy <code>Anemone3DS.3dsx</code> to the <code>3ds</code> folder.
#Insert your SD card into your 3DS
#Open FBI
#Navigate to <code>SD</code> -> <code>cias</code>
#Press {{B|A}} while <code>Anemone3DS.cia</code> is selected, then select <code>Install and delete CIA(s)</code>
#Allow FBI to install the CIA
#Exit FBI

===Section II: extdata setup===
For Anemone3DS themes to work properly, you must create theme extdata. You can do this from the HOME Menu.

#From the HOME Menu, tap the top-left HOME Menu settings button
#Tap "Change Theme"
#Set your theme to anything other than the default
#Allow the 3DS to create the theme extdata
#Exit the theme menu

===Section III: Anemone3DS===

#Open Anemone3DS
#If you don't already have a theme, press {{B|Right Shoulder}} to enter the QR code scanner, then scan a QR code from [https://themeplaza.art/themes Theme Plaza] to download a theme
#*Alternatively, you can place themes downloaded from the website (in <code>.zip</code> format) into <code>sd:/Themes/</code>. Create the folder if it does not already exist
# See the top screen for instructions on what to do. Here are some examples of what Anemone3DS is capable of:
#*If you want to just install one theme with its background music, hover over the theme, hold {{B|A}}, hold {{B|D-Pad Up}}, then release {{B|A}}
#* If you want to install one theme ''without'' its background music, hover over the theme, hold {{B|A}}, hold {{B|D-Pad Right}}, then release {{B|A}}
#*If you want to shuffle multiple themes, press {{B|B}} to select the themes you would like to shuffle (up to ten), hold {{B|A}}, hold {{B|D-Pad Down}}, then release {{B|A}}
#Once you've made your selections, press {{B|Start}} to exit Anemone3DS
#*You will be booted to the Sleep Mode screen
#Press {{B|Home}} to return to the HOME Menu

{{success|Your custom theme has been applied!}}
[[Category:Nintendo 3DS guides]]

3DS:Dump titles and game cartridges

2024-05-14T23:06:36Z

ManiacOfHomebrew: Correct GBA VC save path

{{TOC right}}{{info|text=For support (in English) with GodMode9, as well as help with scripting and to get updates and info, join [https://discord.gg/BRcbvtFxX4 GodMode9 on Discord].}}

Aside from creating and restoring NAND backups, GodMode9 has the functionality to dump installed titles to an installable <code>.cia</code> file, to dump game cartridge data to a <code>.3ds</code> ROM file, and to directly install a game cartridge to the system.

== Updating GodMode9 ==

{{info|text=These instructions are written for use with GodMode9 v2.0.0 or later. If you have an older version of GodMode9, follow these instructions to update it.}}

=== What You Need ===

* The latest release of [https://github.com/d0k3/GodMode9/releases/latest GodMode9]

=== Instructions ===

# Power off your device
# Insert your SD card into your computer
# Copy <code>GodMode9.firm</code> from the GodMode9 <code>.zip</code> to the <code>/luma/payloads/</code> folder on your SD card
# Copy the <code>gm9</code> folder from the GodMode9 <code>.zip</code> to the root of your SD card
# Reinsert your SD card into your device

== Installing a game cartridge directly to the system ==

{{info|text=This will only work for 3DS games; it is not possible to install an NDS game cartridge to the system as a title.}}

# Press and hold {{B|Start}}, and while holding {{B|Start}}, power on your device. This will launch GodMode9
# Navigate to <code>[C:] GAMECART</code>
# Press {{B|A}} on <code>[TitleID].trim.3ds</code> to select it, then select NCSD image options…, then select Install game image
# Press {{B|A}} to unlock SysNAND (lvl1) writing, then input the key combo given
# Once the process is complete, your game will show up in the HOME Menu as an installed title.

== Dumping a game cartridge ==

{{info|text=Insert the game cartridge you intend to dump into your device
* 3DS game cartridges will be dumped to a <code>.3ds</code> format
* NDS game cartridges will be dumped to a <code>.nds</code> format}}

# Press and hold {{B|Start}}, and while holding {{B|Start}}, power on your device. This will launch GodMode9
# Navigate to <code>[C:] GAMECART</code>
# Follow the steps applicable to your game cartridge:
#* '''3DS Game Cartridge:''' Press {{B|A}} on <code>[TitleID].trim.3ds</code> to select it, then select <code>NCSD image options...</code>, then select <code>Decrypt file (0:/gm9/out)</code>.
#* '''NDS Game Cartridge:''' Press {{B|A}} on <code>[TitleID].nds</code> to select it, then select <code>Copy to 0:/gm9/out</code>
#** Trimmed dumps are not recommended for NDS games in general, as they can cause various playback issues
# Your non-installable <code>.3ds</code> or <code>.nds</code> formatted file will be outputted to the <code>/gm9/out/</code> folder on your SD card

== Dumping a 3DS game cartridge to CIA ==

{{info|text=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.}}

# Press and hold {{B|Start}}, and while holding {{B|Start}}, power on your device. This will launch GodMode9
# Navigate to <code>[C:] GAMECART</code>
# Press {{B|A}} on <code>[TitleID].trim.3ds</code> to select it, then select NCSD image options…, then select Build CIA from file
# Your installable <code>.cia</code> formatted file will be outputted to the <code>/gm9/out/</code> folder on your SD card

== Dumping an installed title ==

{{info|text=This allows dumping of both System- and User-installed digital titles, such as ones downloaded from the eShop.}}

# Press and hold {{B|Start}}, and while holding {{B|Start}}, power on your device. This will launch GodMode9
# Press {{B|Home}} to bring up the action menu
# Select Title manager
# Select one of the following depending on the type of title you wish to dump
#* '''User Installed Title''': <code>[A:] SD CARD</code>
#* '''System Title / DSiWare''': <code>[1:] NAND / TWL</code>
# Select the title you wish to dump
# Select Manage Title…
# Select Build CIA (standard)
# Your installable <code>.cia</code> formatted file will be outputted to the <code>/gm9/out/</code> folder on your SD card

== Backup GBA VC saves ==

{{info|text=The game will be outputted to the <code>/gm9/out/</code> folder on your SD card with the name <code><TitleID>.gbavc.sav</code>.}}

{{info|text=To identify a <code><TitleID>.gbavc.sav</code> file’s Title ID, you can get a listing of all games on the system and their corresponding Title IDs by pressing {{B|Home}} to bring up the action menu, selecting <code>Title manager</code>, and selecting <code>[A:] SD CARD</code>.}}

# 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 {{B|Start}}, and while holding {{B|Start}}, power on your device. This will launch GodMode9
## Navigate to <code>[S:] SYSNAND VIRTUAL</code>
## Press {{B|A}} on <code>agbsave.bin</code> to select it
## Select AGBSAVE options…
## Select Dump GBA VC save
## Press {{B|A}} to continue
## Press {{B|Start}} to reboot your device

== Restore GBA VC saves ==

{{info|text=To identify a <code><TitleID>.gbavc.sav</code> file’s Title ID, you can get a listing of all games on the system and their corresponding Title IDs by pressing {{B|Home}} to bring up the action menu, selecting <code>Title manager</code>, and selecting <code>[A:] SD CARD</code>.}}

# 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 {{B|Start}}, and while holding {{B|Start}}, power on your device. This will launch GodMode9
## Navigate to <code>[0:] SDCARD</code> -> <code>gm9</code> -> <code>out</code>
## Press {{B|Y}} on the <code><TitleID>.gbavc.sav</code> file you wish to restore to copy it
## Press {{B|B}} to return to the main menu
## Navigate to <code>[S:] SYSNAND VIRTUAL</code>
## Press {{B|A}} on <code>agbsave.bin</code> to select it
## Select AGBSAVE options…
## Select Inject GBA VC save
## Press {{B|A}} to continue
## Press {{B|Start}} to reboot your device
## Launch the GBA VC game
## Exit the GBA VC game

== Encrypting / Decrypting a CIA file ==

{{info|text=For organizational purposes, copy each <code>.cia</code> file you wish to encrypt / decrypt to the <code>/cias/</code> folder on your SD card}}

# Press and hold {{B|Start}}, and while holding {{B|Start}}, power on your device. This will launch GodMode9
# Navigate to <code>[0:] SDCARD</code> -> <code>cias</code>
# Press {{B|A}} on the <code>.cia</code> file to select it, then select CIA image options…
# Select the option to perform the desired function:
#* '''Encrypt to 0:/gm9/out:''' Create an encrypted copy of the selected <code>.cia</code> file in the <code>/gm9/out/</code> folder on your SD card
#* '''Decrypt to 0:/gm9/out:''' Create a decrypted copy of the selected <code>.cia</code> file in the <code>/gm9/out/</code> folder on your SD card
#* '''Encrypt inplace:''' Replace the selected <code>.cia</code> file with an encrypted version
#* '''Decrypt inplace:''' Replace the selected <code>.cia</code> file with a decrypted version
# Your encrypted / decrypted <code>.cia</code> will be outputted to the desired location

{{hg imported|Guide_3DS}}

[[Category:Nintendo 3DS guides]]

3DS:Custom Themes

2024-04-19T03:03:56Z

ManiacOfHomebrew: redirect

#REDIRECT [[3DS:Custom themes]]

Formatting an SD card/Mac

2024-04-11T18:16:42Z

ManiacOfHomebrew: Undo MSET9 Fresh mention - Mac

This is an add-on section for formatting an SD card to FAT32.

If the console already recognizes the SD card, this guide is not required.

This page is for Mac users only. If you are not on Mac, check out the [[Special:MyLanguage/Formatting an SD card/Windows|Windows]] or [[Special:MyLanguage/Formatting an SD card/Linux|Linux]] pages.

== Instructions ==

<tabber>
|-|OS X El Capitan (10.11) and later=

<ol>
<li>Insert your SD card into your computer</li>
<li>If the SD card has any files and folders on it, copy everything to a folder on your computer</li>
<li>Run the Disk Utility app</li>
<li>In the top-left "View" menu, choose "Show All Devices"</li>
<li>Select your SD card in the left panel {{warning|1=Make sure you choose the correct device, otherwise you might accidentally erase the wrong drive!}}</li>
<li>Click "Erase" at the top</li>
<li>Enter anything for "Name"</li>
<li>Ensure that "Format" is set to "MS-DOS (FAT)"</li>
<li>Ensure that "Scheme" is set to "Master Boot Record"
<ul>
<li>If "Scheme" does not appear, click "Cancel" and make sure to choose the device instead of a volume</li>
</ul></li>
<li>Click "Erase"</li>
<li>Wait for the format to finish</li>
<li>Click "Close"</li>
<li>If the SD card had any files and folders on it before the format, copy everything back from your computer</li>
</ol>

|-|OS X Yosemite (10.10) and earlier=

<ol>
<li>Insert your SD card into your computer</li>
<li>If the SD card has any files and folders on it, copy everything to a folder on your computer</li>
<li>Run the Disk Utility app</li>
<li>Select your SD card in the left panel {{warning|1=Make sure you choose the correct device, otherwise you might accidentally erase the wrong drive!}}</li>
<li>Click "Partition" at the top
<ul>
<li>If "Partition" does not appear, make sure to choose the device instead of a volume</li>
</ul></li>
<li>Ensure that "Partition Layout" is set to "1 Partition"</li>
<li>Enter anything for "Name"</li>
<li>Ensure that "Format" is set to "MS-DOS (FAT)"</li>
<li>Click "Options" below the partition table</li>
<li>Choose "Master Boot Record"</li>
<li>Click "OK"</li>
<li>Click "Apply"</li>
<li>Click "Partition"</li>
<li>Wait for the format to finish</li>
<li>Close Disk Utility</li>
<li>If the SD card had any files and folders on it before the format, copy everything back from your computer</li>
</ol>

</tabber>

{{hg imported|Guide_3DS}}

[[Category:General guides]]

Formatting an SD card/Linux

2024-04-11T18:16:39Z

ManiacOfHomebrew: Undo MSET9 Fresh mention - Linux

This is an add-on section for formatting an SD card to FAT32.

This page is for Linux users only. If you are not on Linux, check out the [[Special:MyLanguage/Formatting an SD card/Windows|Windows]] or [[Special:MyLanguage/Formatting an SD card/Mac|Mac]] pages.

== Instructions ==
{{warning|Before beginning these steps, copy all of your SD card's contents to a folder on your computer.}}

{{warning|The commands in this guide are case-sensitive. Enter them exactly as written, or there may be unintended consequences.}}
<tabber>
|-|fdisk=


# Make sure your SD card is '''not''' inserted
# Open a terminal window and type <code>watch lsblk</code>
# Insert the SD card and watch for a new device appearing in lsblk
# Observe the output for the new device. It should match something like this: {{#tag:syntaxhighlight|
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 3,8G 0 disk
└─mmcblk0p1 179:1 0 3,7G 0 part /run/media/user/FFFF-FFFF
|lang=text}}
# Take note of the name of the device that now appears. In our example above, it was <code>mmcblk0p1</code>, but it could show up as <code>sda</code> or <code>sdb</code>, if you use a USB adapter
#* If <code>RO</code> is set to 1, make sure the lock switch is not slid down
# Hit CTRL + C to exit the menu
# Install the <code>fdisk</code> and <code>dosfstools</code> packages using your package manager of choice
# Type <code>sudo fdisk /dev/<device name></code>
# Enter <code>t</code> and then enter <code>0c</code>
# Enter <code>a</code> and then <code>p</code> - observe the output, and make sure the device is now formatted correctly
# If there are no issues, enter <code>w</code> - this will save changes and exit the fdisk prompt
# Type <code>sudo mkfs.vfat /dev/<device name>1 -s 64</code> to reformat the new partition
#* If the SD card is over 32GB in size, change <code>64</code> to <code>128</code>
# Type <code>sudo eject /dev/<device name></code>, then remove and reinsert the SD card
# Copy your data back onto the SD card


|-|cfdisk=


# Make sure your SD card is '''not''' inserted
# Open a terminal window and type <code>watch lsblk</code>
# Insert the SD card and watch for a new device appearing in lsblk
# Observe the output for the new device. It should match something like this: {{#tag:syntaxhighlight|
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 3,8G 0 disk
└─mmcblk0p1 179:1 0 3,7G 0 part /run/media/user/FFFF-FFFF
|lang=text}}
# Take note of the name of the device that now appears. In our example above, it was <code>mmcblk0p1</code>, but it could show up as <code>sda</code> or <code>sdb</code>, if you use a USB adapter
#* If <code>RO</code> is set to 1, make sure the lock switch is not slid down
# Hit CTRL + C to exit the menu
# Install the <code>cfdisk</code> and <code>dosfstools</code> packages using your package manager of choice
# Type <code>sudo cfdisk /dev/<device name></code>
# Choose the <code>Delete</code> option and delete any existing partitions
# Choose the <code>New</code> option, keep partition size at the recommended size, and choose primary partition type
# Choose the <code>Type</code> option, scroll up until you see <code>b W95 FAT32</code> and select it
# Finally, choose the <code>Write</code> option.
# Choose the <code>Quit</code> option
# Type <code>sudo eject /dev/<device name></code>, then remove and reinsert the SD card
# Copy your data back onto the SD card


|-|parted=


# Make sure your SD card is '''not''' inserted
# Open a terminal window and type <code>watch lsblk</code>
# Insert the SD card and watch for a new device appearing in lsblk
# Observe the output for the new device. It should match something like this: {{#tag:syntaxhighlight|
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 3,8G 0 disk
└─mmcblk0p1 179:1 0 3,7G 0 part /run/media/user/FFFF-FFFF
|lang=text}}
# Take note of the name of the device that now appears. In our example above, it was <code>mmcblk0p1</code>, but it could show up as <code>sda</code> or <code>sdb</code>, if you use a USB adapter
#* If <code>RO</code> is set to 1, make sure the lock switch is not slid down
# Hit CTRL + C to exit the menu
# Install the <code>parted</code> and <code>dosfstools</code> packages using your package manager of choice
# Type <code>sudo parted /dev/<device name> mklabel msdos</code>
# Type <code>sudo parted -a opt /dev/<device name> mkpart primary fat32 0% 100%</code>
# Type <code>sudo eject /dev/<device name></code>, then remove and reinsert the SD card.
# Copy your data back onto the SD card.

</tabber>
{{hg imported|Guide_3DS}}

[[Category:General guides]]

Formatting an SD card/Windows

2024-04-11T18:16:35Z

ManiacOfHomebrew: Undo MSET9 Fresh mention - Windows

<languages/>
<translate>

This is an add-on section for formatting an SD card to FAT32.


This page is for Windows users only. If you are not on Windows, check out the [[Special:MyLanguage/Formatting an SD card/Linux|Linux]] or [[Special:MyLanguage/Formatting an SD card/Mac|Mac]] pages.
</translate>

== Choose your SD card size ==
<tabber>
|-|<translate> 64GB or larger</translate>=

=== What You Need ===
*<translate> The latest version of <tvar name="sdformatter">[https://www.sdcard.org/downloads/formatter/sd-memory-card-formatter-for-windows-download/ SD Memory Card Formatter]</tvar></translate>
*<translate> The latest version of <tvar name="guiformat">[http://ridgecrop.co.uk/index.htm?guiformat.htm guiformat]</tvar></translate>

<translate>
=== Instructions === 
</translate>

<ol>
<li><translate> Insert your SD card into your computer</translate></li>
<li><translate> If the SD card has any files and folders on it, copy everything to a folder on your computer</translate></li>
<li><translate> Run <code>SD Card Formatter Setup</code> (the <code>.exe</code> file) in the downloaded .zip file with Administrator privileges, then install the program</translate></li>
<li><translate> Run <code>SD Card Formatter</code> from the Start Menu</translate></li>
<li><translate> Select your SD card’s drive letter for "Select card"</translate>{{warning|<translate nowrap> Make sure you choose the correct drive letter, otherwise you might accidentally erase the wrong drive!</translate>}}</li>
<li><translate> Ensure that "Quick Format" is selected</translate></li>
<li><translate> Click "Format"</translate></li>
<li><translate> Click "OK"</translate></li>
<li><translate> Wait for the format to finish</translate></li>
<li><translate> Click "OK"</translate></li>{{info|<translate nowrap> '''You're not done yet!''' Your SD card will be formatted to exFAT at this point. The following steps will format it to FAT32.</translate>}}
<li><translate> Close SD Card Formatter</translate></li>
<li><translate> Run <code>guiformat.exe</code></translate></li>
<li><translate> Select your SD card’s drive letter for "Drive"</translate>{{warning|<translate nowrap> Make sure you choose the correct drive letter, otherwise you might accidentally erase the wrong drive!</translate>}}</li>
<li><translate> Select a size for "Allocation unit size"</translate>
<ul>
<li><translate> If the SD card is 64GB, choose 32768</translate></li>
<li><translate> If the SD card is larger than 64GB, choose 65536</translate></li>
</ul></li>
<li><translate> Ensure that "Quick Format" is selected</translate></li>
<li><translate> Click "Start"</translate></li>
<li><translate> Click "OK"</translate></li>
<li><translate> Wait for the format to finish</translate></li>
<li><translate> Click "Close"</translate></li>
<li><translate> If the SD card had any files and folders on it before the format, copy everything back from your computer</translate></li>
</ol>

<translate>
=== Common errors with guiformat ===  </translate>
==== Failed to open device: GetLastError()=32 ====
<translate>

Close everything that may be using the SD card, such as any File Explorer windows. If it does not resolve the issue, try formatting the card to NTFS, then run GUIFormat again.
</translate>

==== GetLastError()=1117 ====
<translate>

Your SD card write-protection switch may be [https://3ds.hacks.guide/images/sdlock.png enabled]. The lock must be flipped upwards to allow writing to the SD card (including formatting).
</translate>

|-|<translate> 32GB or smaller</translate>=

=== What You Need ===
*<translate> The latest version of <tvar name="sdformatter">[https://www.sdcard.org/downloads/formatter/sd-memory-card-formatter-for-windows-download/ SD Memory Card Formatter]</tvar></translate>

<translate>
=== Instructions === 
</translate>

<ol>
<li><translate> Insert your SD card into your computer</translate></li>
<li><translate> If the SD card has any files and folders on it, copy everything to a folder on your computer</translate></li>
<li><translate> Run <code>SD Card Formatter Setup</code> (the <code>.exe</code> file) in the downloaded .zip file with Administrator privileges, then install the program</translate></li>
<li><translate> Run <code>SD Card Formatter</code> from the Start Menu</translate></li>
<li><translate> Select your SD card’s drive letter for "Select card"</translate>{{warning|<translate nowrap> Make sure you choose the correct drive letter, otherwise you might accidentally erase the wrong drive!</translate>}}</li>
<li><translate> Ensure that "Quick Format" is selected</translate></li>
<li><translate> Click "Format"</translate></li>
<li><translate> Click "OK"</translate></li>
<li><translate> Wait for the format to finish</translate></li>
<li><translate> Click "OK"</translate></li>
<li><translate> Close SD Card Formatter</translate></li>
<li><translate> If the SD card had any files and folders on it before the format, copy everything back from your computer</translate></li>
</ol>
</tabber>

==SD Card not formatting or has some other issue.==
Refer to the [[SD Clean/Windows|SD Clean]] guide.

{{hg imported|Guide_3DS}}

[[Category:General guides]]

Formatting an SD card/Mac

2024-04-11T18:03:09Z

ManiacOfHomebrew: Don't copy during MSET9 Fresh - Mac

This is an add-on section for formatting an SD card to FAT32.

If the console already recognizes the SD card, this guide is not required.

This page is for Mac users only. If you are not on Mac, check out the [[Special:MyLanguage/Formatting an SD card/Windows|Windows]] or [[Special:MyLanguage/Formatting an SD card/Linux|Linux]] pages.

== Instructions ==

<tabber>
|-|OS X El Capitan (10.11) and later=

<ol>
<li>Insert your SD card into your computer</li>
<li>If the SD card has any files and folders on it, copy everything to a folder on your computer</li>
<li>Run the Disk Utility app</li>
<li>In the top-left "View" menu, choose "Show All Devices"</li>
<li>Select your SD card in the left panel {{warning|1=Make sure you choose the correct device, otherwise you might accidentally erase the wrong drive!}}</li>
<li>Click "Erase" at the top</li>
<li>Enter anything for "Name"</li>
<li>Ensure that "Format" is set to "MS-DOS (FAT)"</li>
<li>Ensure that "Scheme" is set to "Master Boot Record"
<ul>
<li>If "Scheme" does not appear, click "Cancel" and make sure to choose the device instead of a volume</li>
</ul></li>
<li>Click "Erase"</li>
<li>Wait for the format to finish</li>
<li>Click "Close"</li>
<li>If the SD card had any files and folders on it before the format, copy everything back from your computer
<ul>
<li>If you are in the process of following the [[3DS:MSET9_fresh|MSET9 fresh troubleshooting guide]], skip this step, or else the error is likely to keep happening.</li>
</ul></li>
</ol>

|-|OS X Yosemite (10.10) and earlier=

<ol>
<li>Insert your SD card into your computer</li>
<li>If the SD card has any files and folders on it, copy everything to a folder on your computer</li>
<li>Run the Disk Utility app</li>
<li>Select your SD card in the left panel {{warning|1=Make sure you choose the correct device, otherwise you might accidentally erase the wrong drive!}}</li>
<li>Click "Partition" at the top
<ul>
<li>If "Partition" does not appear, make sure to choose the device instead of a volume</li>
</ul></li>
<li>Ensure that "Partition Layout" is set to "1 Partition"</li>
<li>Enter anything for "Name"</li>
<li>Ensure that "Format" is set to "MS-DOS (FAT)"</li>
<li>Click "Options" below the partition table</li>
<li>Choose "Master Boot Record"</li>
<li>Click "OK"</li>
<li>Click "Apply"</li>
<li>Click "Partition"</li>
<li>Wait for the format to finish</li>
<li>Close Disk Utility</li>
<li>If the SD card had any files and folders on it before the format, copy everything back from your computer
<ul>
<li>If you are in the process of following the [[3DS:MSET9_fresh|MSET9 fresh troubleshooting guide]], skip this step, or else the error is likely to keep happening.</li>
</ul></li>
</ol>

</tabber>

{{hg imported|Guide_3DS}}

[[Category:General guides]]

Formatting an SD card/Linux

2024-04-11T18:03:04Z

ManiacOfHomebrew: Don't copy during MSET9 Fresh - Linux

This is an add-on section for formatting an SD card to FAT32.

This page is for Linux users only. If you are not on Linux, check out the [[Special:MyLanguage/Formatting an SD card/Windows|Windows]] or [[Special:MyLanguage/Formatting an SD card/Mac|Mac]] pages.

== Instructions ==
{{warning|Before beginning these steps, copy all of your SD card's contents to a folder on your computer.}}

{{warning|The commands in this guide are case-sensitive. Enter them exactly as written, or there may be unintended consequences.}}
<tabber>
|-|fdisk=


# Make sure your SD card is '''not''' inserted
# Open a terminal window and type <code>watch lsblk</code>
# Insert the SD card and watch for a new device appearing in lsblk
# Observe the output for the new device. It should match something like this: {{#tag:syntaxhighlight|
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 3,8G 0 disk
└─mmcblk0p1 179:1 0 3,7G 0 part /run/media/user/FFFF-FFFF
|lang=text}}
# Take note of the name of the device that now appears. In our example above, it was <code>mmcblk0p1</code>, but it could show up as <code>sda</code> or <code>sdb</code>, if you use a USB adapter
#* If <code>RO</code> is set to 1, make sure the lock switch is not slid down
# Hit CTRL + C to exit the menu
# Install the <code>fdisk</code> and <code>dosfstools</code> packages using your package manager of choice
# Type <code>sudo fdisk /dev/<device name></code>
# Enter <code>t</code> and then enter <code>0c</code>
# Enter <code>a</code> and then <code>p</code> - observe the output, and make sure the device is now formatted correctly
# If there are no issues, enter <code>w</code> - this will save changes and exit the fdisk prompt
# Type <code>sudo mkfs.vfat /dev/<device name>1 -s 64</code> to reformat the new partition
#* If the SD card is over 32GB in size, change <code>64</code> to <code>128</code>
# Type <code>sudo eject /dev/<device name></code>, then remove and reinsert the SD card
# If the SD card had any files and folders on it before the format, copy everything back from your computer
#* If you are in the process of following the [[3DS:MSET9_fresh|MSET9 fresh troubleshooting guide]], skip this step, or else the error is likely to keep happening.


|-|cfdisk=


# Make sure your SD card is '''not''' inserted
# Open a terminal window and type <code>watch lsblk</code>
# Insert the SD card and watch for a new device appearing in lsblk
# Observe the output for the new device. It should match something like this: {{#tag:syntaxhighlight|
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 3,8G 0 disk
└─mmcblk0p1 179:1 0 3,7G 0 part /run/media/user/FFFF-FFFF
|lang=text}}
# Take note of the name of the device that now appears. In our example above, it was <code>mmcblk0p1</code>, but it could show up as <code>sda</code> or <code>sdb</code>, if you use a USB adapter
#* If <code>RO</code> is set to 1, make sure the lock switch is not slid down
# Hit CTRL + C to exit the menu
# Install the <code>cfdisk</code> and <code>dosfstools</code> packages using your package manager of choice
# Type <code>sudo cfdisk /dev/<device name></code>
# Choose the <code>Delete</code> option and delete any existing partitions
# Choose the <code>New</code> option, keep partition size at the recommended size, and choose primary partition type
# Choose the <code>Type</code> option, scroll up until you see <code>b W95 FAT32</code> and select it
# Finally, choose the <code>Write</code> option.
# Choose the <code>Quit</code> option
# Type <code>sudo eject /dev/<device name></code>, then remove and reinsert the SD card
# If the SD card had any files and folders on it before the format, copy everything back from your computer
#* If you are in the process of following the [[3DS:MSET9_fresh|MSET9 fresh troubleshooting guide]], skip this step, or else the error is likely to keep happening.


|-|parted=


# Make sure your SD card is '''not''' inserted
# Open a terminal window and type <code>watch lsblk</code>
# Insert the SD card and watch for a new device appearing in lsblk
# Observe the output for the new device. It should match something like this: {{#tag:syntaxhighlight|
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 3,8G 0 disk
└─mmcblk0p1 179:1 0 3,7G 0 part /run/media/user/FFFF-FFFF
|lang=text}}
# Take note of the name of the device that now appears. In our example above, it was <code>mmcblk0p1</code>, but it could show up as <code>sda</code> or <code>sdb</code>, if you use a USB adapter
#* If <code>RO</code> is set to 1, make sure the lock switch is not slid down
# Hit CTRL + C to exit the menu
# Install the <code>parted</code> and <code>dosfstools</code> packages using your package manager of choice
# Type <code>sudo parted /dev/<device name> mklabel msdos</code>
# Type <code>sudo parted -a opt /dev/<device name> mkpart primary fat32 0% 100%</code>
# Type <code>sudo eject /dev/<device name></code>, then remove and reinsert the SD card.
# If the SD card had any files and folders on it before the format, copy everything back from your computer
#* If you are in the process of following the [[3DS:MSET9_fresh|MSET9 fresh troubleshooting guide]], skip this step, or else the error is likely to keep happening.

</tabber>
{{hg imported|Guide_3DS}}

[[Category:General guides]]

Formatting an SD card/Windows

2024-04-11T18:02:58Z

ManiacOfHomebrew: Don't copy during MSET9 Fresh - Windows

<languages/>
<translate>

This is an add-on section for formatting an SD card to FAT32.


This page is for Windows users only. If you are not on Windows, check out the [[Special:MyLanguage/Formatting an SD card/Linux|Linux]] or [[Special:MyLanguage/Formatting an SD card/Mac|Mac]] pages.
</translate>

== Choose your SD card size ==
<tabber>
|-|<translate> 64GB or larger</translate>=

=== What You Need ===
*<translate> The latest version of <tvar name="sdformatter">[https://www.sdcard.org/downloads/formatter/sd-memory-card-formatter-for-windows-download/ SD Memory Card Formatter]</tvar></translate>
*<translate> The latest version of <tvar name="guiformat">[http://ridgecrop.co.uk/index.htm?guiformat.htm guiformat]</tvar></translate>

<translate>
=== Instructions === 
</translate>

<ol>
<li><translate> Insert your SD card into your computer</translate></li>
<li><translate> If the SD card has any files and folders on it, copy everything to a folder on your computer</translate></li>
<li><translate> Run <code>SD Card Formatter Setup</code> (the <code>.exe</code> file) in the downloaded .zip file with Administrator privileges, then install the program</translate></li>
<li><translate> Run <code>SD Card Formatter</code> from the Start Menu</translate></li>
<li><translate> Select your SD card’s drive letter for "Select card"</translate>{{warning|<translate nowrap> Make sure you choose the correct drive letter, otherwise you might accidentally erase the wrong drive!</translate>}}</li>
<li><translate> Ensure that "Quick Format" is selected</translate></li>
<li><translate> Click "Format"</translate></li>
<li><translate> Click "OK"</translate></li>
<li><translate> Wait for the format to finish</translate></li>
<li><translate> Click "OK"</translate></li>{{info|<translate nowrap> '''You're not done yet!''' Your SD card will be formatted to exFAT at this point. The following steps will format it to FAT32.</translate>}}
<li><translate> Close SD Card Formatter</translate></li>
<li><translate> Run <code>guiformat.exe</code></translate></li>
<li><translate> Select your SD card’s drive letter for "Drive"</translate>{{warning|<translate nowrap> Make sure you choose the correct drive letter, otherwise you might accidentally erase the wrong drive!</translate>}}</li>
<li><translate> Select a size for "Allocation unit size"</translate>
<ul>
<li><translate> If the SD card is 64GB, choose 32768</translate></li>
<li><translate> If the SD card is larger than 64GB, choose 65536</translate></li>
</ul></li>
<li><translate> Ensure that "Quick Format" is selected</translate></li>
<li><translate> Click "Start"</translate></li>
<li><translate> Click "OK"</translate></li>
<li><translate> Wait for the format to finish</translate></li>
<li><translate> Click "Close"</translate></li>
<li><translate> If the SD card had any files and folders on it before the format, copy everything back from your computer</translate>
<ul>
<li><translate>If you are in the process of following the [[3DS:MSET9_fresh|MSET9 fresh troubleshooting guide]], skip this step, or else the error is likely to keep happening.</translate></li>
</ul></li>
</ol>

<translate>
=== Common errors with guiformat ===  </translate>
==== Failed to open device: GetLastError()=32 ====
<translate>

Close everything that may be using the SD card, such as any File Explorer windows. If it does not resolve the issue, try formatting the card to NTFS, then run GUIFormat again.
</translate>

==== GetLastError()=1117 ====
<translate>

Your SD card write-protection switch may be [https://3ds.hacks.guide/images/sdlock.png enabled]. The lock must be flipped upwards to allow writing to the SD card (including formatting).
</translate>

|-|<translate> 32GB or smaller</translate>=

=== What You Need ===
*<translate> The latest version of <tvar name="sdformatter">[https://www.sdcard.org/downloads/formatter/sd-memory-card-formatter-for-windows-download/ SD Memory Card Formatter]</tvar></translate>

<translate>
=== Instructions === 
</translate>

<ol>
<li><translate> Insert your SD card into your computer</translate></li>
<li><translate> If the SD card has any files and folders on it, copy everything to a folder on your computer</translate></li>
<li><translate> Run <code>SD Card Formatter Setup</code> (the <code>.exe</code> file) in the downloaded .zip file with Administrator privileges, then install the program</translate></li>
<li><translate> Run <code>SD Card Formatter</code> from the Start Menu</translate></li>
<li><translate> Select your SD card’s drive letter for "Select card"</translate>{{warning|<translate nowrap> Make sure you choose the correct drive letter, otherwise you might accidentally erase the wrong drive!</translate>}}</li>
<li><translate> Ensure that "Quick Format" is selected</translate></li>
<li><translate> Click "Format"</translate></li>
<li><translate> Click "OK"</translate></li>
<li><translate> Wait for the format to finish</translate></li>
<li><translate> Click "OK"</translate></li>
<li><translate> Close SD Card Formatter</translate></li>
<li><translate> If the SD card had any files and folders on it before the format, copy everything back from your computer</translate>
<ul>
<li><translate>If you are in the process of following the [[3DS:MSET9_fresh|MSET9 fresh troubleshooting guide]], skip this step, or else the error is likely to keep happening.</translate></li>
</ul></li>
</ol>
</tabber>

==SD Card not formatting or has some other issue.==
Refer to the [[SD Clean/Windows|SD Clean]] guide.

{{hg imported|Guide_3DS}}

[[Category:General guides]]

3DS:Error codes

2024-04-02T22:51:09Z

ManiacOfHomebrew: fix link

{{hatnote|1=This page only lists error codes that are always handled by stock parts of firmware. If the error in question is handled by custom firmware, the pages on [[3DS:Error screens/Luma3DS exception screen|"An exception occurred" screens]] and [[3DS:Error screens/Luma3DS ErrDisp|Luma3DS ErrDisps]] will be relevant instead.}}

{{info|Not all 3DS error codes are known or understood, and it is unlikely all codes will ever be documented in full due to Nintendo failing to document many of them. As such, this page can be considered a living document - any information written here will likely be subject to frequent changes.}}
On both stock and custom firmware, apps can cause errors if they run into a non-fatal issue.

This page lists various causes of stock error codes.

== Reading an error code ==
An error code has two parts - the code itself, and its official description.
[[File:3DS error code.jpg|center]]
For this page, only the code matters.

== Known errors ==
In the below tables, error codes are separated into sets by their section (e.g. 007-XXXX) and then sorted within their sets in ascending order by their result code (e.g. XXX-2001).

__TOC__

{| class="wikitable" style="margin:auto;"
|-
! colspan="3" |<h3>001 - Online Services</h3>
|-
|0102
|Unexpected disconnection from network services.
|[https://en-americas-support.nintendo.com/app/answers/detail/a%20id/17043 Nintendo Support Page]
|-
|0112
|Unable to connect to the server.
|
|-
|0302
|Unable to connect to the server.
|
|-
|0502
|Cannot connect to online services, or unexpectedly disconnected from them.
|
|-
|0718
|The Friends List is already full.
|
|-
|0720
|Generic error code.
|
|-
|0721
|Online access is restricted by Parental Controls.
|
|-
|0724
|Your Personal Mii is missing.
|
|-
|0725
|Your ability to register friends is restricted by Parental Controls.
|
|-
|0726
|Your notification settings for the Friends List are not yet configured.
|
|-
|0803
|Cannot connect to authentication servers.
|[https://www.nintendo.co.jp/netinfo/en_US/index.html Server Status and Maintenance]
|-
|0811
|Online play servers under maintenance.
|[https://www.nintendo.co.jp/netinfo/en_US/index.html Server Status and Maintenance]
|-
! colspan="3" |<h3> 002 - Account Related Errors</h3>
|-
| 0100
|The online service is unavailable.
|
|-
|0101
|Network has high traffic or is down.
|
|-
|0102
|Account permanently banned.
|
|-
|0107
|Account temporarily banned.
|
|-
|0109
|Possible corrupted data.
|
|-
|0110
|YouTube for the 3DS has been discontinued.
|
|-
|0111
|The online service is unavailable.
|
|-
|0119
|Friend module outdated, system update required.
|
|-
|0120
|This game/title is outdated, and must be updated before use.
|
|-
|0121
|Invalid LocalFriendCodeSeed SEED signature - the file is possibly modified.
|
|-
| 0123
|Account is permanently banned.
|
|-
|3503
|Service under maintenance.
|
|-
|34xx
|Server returned a 4xx HTTP error.
|[https://www.nintendo.co.jp/netinfo/en_US/index.html Server Status and Maintenance]
|-
|35xx
|Server returned a 5xx HTTP error.
|[https://www.nintendo.co.jp/netinfo/en_US/index.html Server Status and Maintenance]
|-
! colspan="3" |<h3>003 - Network Connection Errors</h3>
|-
|0200
|Wireless connections are disabled.
|
|-
|0299
|Wireless connections are disabled.
|
|-
|0300
|The EULA for your region has not been accepted.
|
|-
|0399
|The accepted EULA version is too low.
|
|-
|0400
|Your ability to do this is restricted by Parental Controls.
|
|-
|1000
|No Access Point found.
|
|-
|1004
|No Access Point found with USB Connector.
|
|-
|1099
|Could not find an Access Point with the entered SSID.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4249/kw/003-1099 Nintendo Support Page]
|-
|1100
|The encryption key is incorrect.
|
|-
|1101
|Access Point password incorrect or it has a incompatible configuration.
|
|-
|1102
|Unable to connect to Access Point due to incorrect Security Setting.
|
|-
|1104
|Unable to connect to Access Point with USB Connector.
|
|-
|1200
|Connection refused, as it would give this device the same IP address as another device in the network.
|
|-
|1300
|Incorrect Access Point configuration.
|
|-
|1400
|Incorrect security key.
|
|-
|1402
|Unable to connect to the internet with this Access Point.
|
|-
|2000
|Incorrect security key or DNS.
|
|-
|2001
|DNS resolution error. If you are using a custom DNS server, recheck its settings.
|
|-
|2100
|Network may be busy or have other connection problems.
|
|-
|2200
|Unable to connect to the Proxy Server.
|
|-
|3000
|There was an issue with authentication.
|
|-
|3305
|This service is not available in your location.
|
|-
|3405
|Generic communication error.
|
|-
|4000
|Generic communication error.
|
|-
|4100
|Generic communication error.
|
|-
! colspan="3" | <h3>005 - Network Installation Management</h3>
|-
|2008
|eShop download failed or the title's ticket is invalid. Delete the ticket in FBI and install it from a legitimate source like the eShop or (if it's a cart dump) from the game's cartridge.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/41692 Nintendo Support Page]
|
|-
|2037
|The server is undergoing maintenance.
|
|
|-
|2038
|A system update is required to use this service.
|
|
|-
|2043
|A system update is required to use this service.
|
|
|-
|2056
|Not enough space on the SD Card.
|
|
|-
|2061
|Unable to access the SD Card.
|
|
|-
|2062
|Not enough space in the System Memory.
|
|
|-
|2068
|The server is undergoing maintenance.
|
|
|-
|2069
|The software is corrupted.
|
|
|-
|4017
|This activation code is not recognized.
|
|
|-
|4040
|eShop connection timeout.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4429 Nintendo Support Page]
|-
|4069
|eShop is unavailable. If the issue persists, the SD might need to be replaced.
| [https://en-americas-support.nintendo.com/app/answers/detail/a_id/14413 Nintendo Support Page]
|-
|4240
|Cannot connect to eShop servers.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/28399 Nintendo Support Page]
|-
|4305
|Generic connection timeout error, could also mean that you are unable to download software from the eShop.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4346 Nintendo Support Page]
|-
|4320
|Generic error, only displays when formatting the console or performing a system transfer.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/48382 Nintendo Support Page]
|-
|5403
|Transfers are currently prohibited.
|
|-
|5404
|The transfer limit has been reached.
|
|-
|5542
|Maximum Funds reached.
|
|-
|5546
|Unable to purchase more items.
|
|-
|5568
|This activation code cannot be used with your account.
|
|-
|5593
|Unable to transfer specific software.
|
|-
|5602
|eShop title(s) from another region are linked to this console. This is caused by a region change.
|
|-
|5644
|Unable to use this credit card with this specific system.
|
|-
|5670
|You are unable to view your account's activity at this time.
|
|-
|5687
|Generic eShop connection issue error.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/26251/ Nintendo Support Page]
|-
|5704
| Generic eShop connection issue error.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/26252 Nintendo Support Page]
|-
|5804
|This number has expired.
|
|-
|5811
|This activation code has expired.
|
|-
|5815
|This activation code has already been used.
|
|-
|5941
|The entered login details are incorrect.
|
|-
|5942
|Name was not registered due to a connection error.
|
|-
|5948
|Your eShop funds are already over the maximum value.
|
|-
|5958
|Unknown eShop error, usually seen on region-changed consoles.
|
|-
|5964
|Your NNID is banned from accessing the eShop. Contact Nintendo Support if this is a mistake.
|
|-
|5989
|You cannot link your Club Nintendo account to more than eight Nintendo 3DS systems.
|
|-
|6402
|The entered login details are incorrect.
|
|-
|6403
|Unable to register the entered username.
|
|-
|6499
|The Club Nintendo servers are undergoing maintenance, so your name couldn't be registered.
|
|-
|6501
|This credit card cannot be used.
|
|-
|6503
|The entered credit card number is incorrect.
|
|-
|6504
|You must enter the three-digit security code.
|
|-
|6507
|The entered credit card details are incorrect.
|
|-
|6511
|This credit card cannot be used.
|
|-
|6514
|The entered expiry date for this credit card is incorrect.
|
|-
|6519
|The entered address does not match the credit card's billing address.
|
|-
|7545
|eShop is unavailable. If the issue persists, the SD might need to be replaced.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/14413 Nintendo Support Page]
|-
|7550
|eShop is unavailable. If the issue persists, the SD might need to be replaced.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/14413 Nintendo Support Page]
|-
|8025
|eShop is unavailable. If the issue persists, the SD might need to be replaced.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/14413 Nintendo Support Page]
|-
|8026
|eShop is unavailable. If the issue persists, the SD might need to be replaced.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/14413 Nintendo Support Page]
|-
|8029
|eShop is unavailable. If the issue persists, the SD might need to be replaced.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/14413 Nintendo Support Page]
|-
! colspan="3" |<h3>006 - Matchmaking Errors</h3>
|-
|0112
|Issue connecting with Pokémon Bank.
|[https://en-americas-support.nintendo.com/app/answers/detail/a%20id/4203/ Nintendo Support Page]
|-
|0302
|Unable to connect to the server.
|
|-
|0311
|Unable to connect to the server.
|
|-
|0329
|The server is undergoing maintenance.
|
|-
|0332
|Closed ports while attempting matchmaking.
|
|-
|0347
|This online service is discontinued.
|
|-
|0501
|May indicate that the network is blocking traffic necessary for Online Play.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4204 Nintendo Support Page]
|-
|0502
|May indicate that the network is blocking traffic necessary for Online Play.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4204 Nintendo Support Page]
|-
|0520
|Unable to connect to the Internet.
|
|-
|0612
| Network is not optimal for peer-to-peer connections, possibly due to your network's NAT type.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/25881 Nintendo Support Page]
|-
|0617
|Generic error message.
|
|-
|0620
|Generic communication error.
|
|-
|0623
|Unable to connect due to outdated software.
|
|-
|0721
|Your ability to do online interactions is restricted by Parental Controls.
|
|-
|0800
|Unable to connect to authentication servers during the matchmaking process.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4328/ Nintendo Support Page]
|-
|0811
|Service unavailable due to maintenance.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/25910/ Nintendo Support Page]
|-
|0817
|This online service is discontinued.
|
|-
|0899
|Unable to connect to authentication servers during the matchmaking process.
| [https://en-americas-support.nintendo.com/app/answers/detail/a_id/4328/ Nintendo Support Page]
|-
! colspan="3" |<h3>007 - eShop API Errors</h3>
|-
|0200
|Could not access the SD Card.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4234 Nintendo Support Page]
|-
|1221
|The used download code is only redeemable in its relevant software, not in the eShop.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/14600 Nintendo Support Page]
|-
|2001
|Error when attempting to access the eShop with a region-changed console. Change back to the original region or restore a NAND backup made before the change to fix.
|
|-
|2100
|Connection to eShop timed out, often caused by slow download times.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4432 Nintendo Support Page]or [https://support.nintendo.com/networkstatus Server Status and Maintenance]
|-
|2640
|Cannot connect to eShop/CDN servers.
|[https://support.nintendo.com/networkstatus Server Status and Maintenance]
|-
| 2670
|Error while attempting to connect.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4383 Nintendo Support Page]
|-
|2705
|Cannot connect to Nintendo servers.
|[https://support.nintendo.com/networkstatus Server Status and Maintenance]
|-
|2720
|eShop SSL error.
|
|-
|2913
| The server is probably down. Try again later.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/10425 Nintendo Support Page]
|-
|2916
|Unknown cause, typically displayed when attempting to download a title from the eShop.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/6557 Nintendo Support Page]
|-
|2920
|eShop download failed or invalid title ticket. Delete the ticket in FBI and install it from a legitimate source like the eShop or (if it's a cart dump) from the game's cartridge.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/41692 Nintendo Support Page]
|-
|2924
|The language or region setting in your profile (not the same as the console's region) is not supported by the eShop.
|
|-
|3049
|The eShop is currently under maintenance.
|[https://support.nintendo.com/networkstatus/ Server Status and Maintenance]
|-
|6106
|Occurs when attempting to re-download software from the eShop with an invalid or fake ticket active.
|
|-
! colspan="3" |<h3>009 - eShop Application</h3>
|-
|1000
|A system update required. Check [[3DS:Is it safe to update?]]
|
|-
|1001
|The eShop is currently under maintenance.
|[https://support.nintendo.com/networkstatus/ Server Status and Maintenance]
|-
|1002
|This service cannot be used in your region.
|
|-
|1003
|The system's country setting and the eShop's country setting do not match.
|
|-
|1004
|The content of this code has already been acquired.
|
|-
|1006
|The selected downloadable items cannot be purchased together.
|
|-
|1100
|The Add Funds function is not available in your selected region.
|
|-
|1200
|This Activation Code has already been used.
|
|-
|1201
|The entered code is not recognized.
|
|-
|1202
|The entered activation code is not recognized.
|
|-
|1203
|This card is not valid on 3DS Systems.
|
|-
|1205
|This activation code is not valid in your region.
|
|-
|1206
|This code cannot be used here.
|
|-
|1299
|The entered number is invalid.
|
|-
|1302
|Failed to enter the correct PIN.
|
|-
|1303
|Failed to authenticate the stored credit card's information. The information has been deleted.
|
|-
|1304
|The entered credit card cannot be used.
|
|-
|1305
|Credit card payments cannot be accepted at this time.
|
|-
|1313
|The entered address is incorrect.
|
|-
|1350
|The entered value exceeds your balance limit.
|
|-
|1351
|The balance limit has been reached.
|
|-
|2001
|Error when attempting to access the eShop with a region-changed console. Change back to the original region or restore a NAND backup made before the change to fix.
|
|-
|2410
|This service has been discontinued.
|
|-
|2705
|Often caused by network timing out or losing connection with the eShop.
|[https://en-americas-support.nintendo.com/app/answers/detail/a%20id/17014 Nintendo Support Page]
|-
|2913
|eShop or in-game DLC failed to download (or the server is down).
|[https://en-americas-support.nintendo.com/app/answers/detail/a%20id/7243 Nintendo Support Page]
|-
|2916
|Unknown cause, typically displayed when attempting to download a title from the eShop.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/6557 Nintendo Support Page]
|-
|2920
|eShop download failed or invalid title ticket. Delete the ticket in FBI and install it from a legitimate source like the eShop or (if it's a cart dump) from the game's cartridge.
| [https://en-americas-support.nintendo.com/app/answers/detail/a_id/41692 Nintendo Support Page]
|-
|2923
|Unable to use a function that requires Internet Services.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/17014 Nintendo Support Site]
|-
|2924
|Your language or region setting (not console region) is not supported by the eShop.
|
|-
|2995
|The used download code is incorrect, not yet activated, expired, entered in the wrong place, or only usable in a different region.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/13515 Nintendo Support Site]
|-
|2996
|The item from the entered code is not currently being distributed.
|
|-
|4100
|The SD Card's data limit has been reached.
|
|-
|4072
|The SD Card may not be inserted.
|
|-
|4074
|Could not access the SD Card.
|
|-
|4075
|The SD Card's software management data is corrupted.
|
|-
|4077
|Download refused due to insufficient space on the SD Card.
|
|-
|4079
|Unable to access the SD Card.
|
|-
|4998
|The local version of this content is newer than the version you are trying to download. Unknown what causes this.
|
|-
|6106
|An AM error occurred in NIM. Likely a bad ticket.
|
|-
|8001
|Authentication failed.
|
|-
|8002
|The service has expired.
|
|-
|8101
|The save data is unusable, as DLC required for it is missing.
|
|-
|8102
|Not enough free space to complete this process.
|
|-
|8111
|The DLC is corrupted.
|
|-
|8201
|Your access to the eShop is restricted by Parental Controls.
|
|-
|8301
|The 3DS User Agreement has to be accepted.
|
|-
|8401
|Corrupted update data. Delete it and reinstall.
|
|-
|9001
|The download was stopped due to low battery.
|
|-
|9002
|The entered number is invalid.
|
|-
|9003
|The entered Password is invalid.
|
|-
! colspan="3" |<h3>011 - eShop Site</h3>
|-
|24xx
|Server returned a 4xx HTTP error.
|[https://www.nintendo.co.jp/netinfo/en_US/index.html Server Status and Maintenance]
|-
|25xx
|Server returned a 5xx HTTP error.
|[https://www.nintendo.co.jp/netinfo/en_US/index.html Server Status and Maintenance]
|-
|3010
|The server timed out due to inactivity.
|
|-
|3021
|eShop title not found (wrong region or non-existent).
|
|-
| 3136
|eShop currently unavailable. Try again later.
|
|-
|5998
|eShop is currently under maintenance.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/24326/ Nintendo Support Page]
|-
|6901
|Console permanently banned (this is always displayed in Japanese).
|
|-
! colspan="3" |<h3>012 - Browser Errors</h3>
|-
|1004
|The SSL connection Failed.
|
|-
|1511
|SSL certificate warning.
|
|-
! colspan="3" |<h3> 014 - Data Transfer Errors</h3>
|-
|0013
|The System Transfer failed due to an invalid language setting.
|
|-
|0016
|The consoles have the same movable.sed. Format the target console and try again.
|
|-
|0062
|An error occurred during the System Transfer. Move closer to the router and try again.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/15664 Nintendo Support Page]
|-
! colspan="3" |<h3>022 - More Account Errors</h3>
|-
|1021
|There is no NNID linked to this system.
|
|-
|1022
|The entered NNID is already linked to the system.
|
|-
|2452
|Tried to access the eShop with UNITINFO patch enabled. Turn this off in Luma's configuration file, <code>sd:/luma/config.ini</code>.
|
|-
|2501
|The entered NNID is already linked to another system. Could be caused by a System Transfer (which transfers all associated NNID's, whether linked or not), restoring the Source System's NAND, and then attempting to use applications that require an NNID.
|
|-
|2502
|The NNID can't be used because it does not match the region setting of the system.
|
|-
|2503
|The network Service Agreement is not yet accepted.
|
|-
|2511
|A System Update is required (displayed by Miiverse).
|
|-
|2512
|A software update is required to use this title's online services.
|
|-
|2571
|This NNID is already in use.
|-
|2572
|NNID contains text that can't be used.
|-
|2573
|The entered password can't be used.
|-
|2574
|The entered nickname can't be used.
|-
|2575
|The entered email address is incorrect.
|-
|2576
|The entered NNID can't be used.
|-
|2577
|Your password cannot be identical to your NNID.
|-
|2578
|The entry contains characters that can't be used.
|-
|2579
|You can't use more than one punctuation character in your NNID.
|-
|2580
|You can't use punctuation as the first or last character of your NNID.
|-
|2581
|You can't use more than six numbers in your NNID.
|-
|2582
|Your entry contains characters that cannot be used.
|-
|2583
|Your password must contain characters from at least two of the following categories: letters, numbers and punctuation.
|-
|2584
|You can't use the same character three or more times in a row.
|-
|2585
|The email address you entered can't be used.
|-
|2586
|The domain name of the e-mail address you entered may be incorrect.
|-
|2587
|The NNID you entered already exists.
|-
|2591
|NNID is already linked to another system. Could be caused by a System Transfer (which transfers all associated NNID's, whether linked or not), restoring the Source System's NAND, and then attempting to use applications that require an NNID.
|-
|2592
|The limit for linking this NNID has been reached.
|-
|2593
|The entered NNID cannot be used because it has not yet been confirmed by a parent/guardian.
|-
|2594
|Parental Controls restrictions must be set up first.
|-
|2595
|You have not registered a Mii.
|-
|2611
|The entered password is incorrect.
|-
|2612
|The entered email address is incorrect.
|-
|2613
|The entered information is incorrect.
|-
|2613
|Incorrect email or password when attempting to link an existing NNID. Can also happen if the NNID is already linked to a system, or when attempting to download a title from the eShop without having a linked NNID on the console.
|
|-
| 2631
|The NNID you are trying to use has been deleted or can't be used for a system transfer. A transferable NNID will only work on the target system.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4285/kw/022-2631 Nintendo Support Page]
|-
|2632
|The NNID has been changed.
|
|-
|2633
|This NNID has been temporarily locked due to too many password attempts. Try again later.
|
|-
|2634
|The NNID is not correctly linked to the system. To fix this, follow these steps, reboot the console, and try to sign into the NNID again.
|[[3DS:GodMode9/Usage#Removing_an_NNID_without_formatting_your_device|Said Steps]]
|-
|2643
|The session has expired.
|
|-
|2662
|You can't perform this operation several times in a row.
|
|-
|2672
|Use of credit card has been stopped.
|
|-
|2673
|The entered credit card cannot be used.
|
|-
|2674
|Check the credit card's number and enter it again.
|
|-
|2675
|Check the credit card's expiration date and enter it again.
|
|-
|2676
|Check the credit card's PIN and enter it again.
|
|-
|2677
|The entered information is not correct.
|
|-
|2679
|The entered credit card is expired.
|
|-
|2801
|Online Services cannot be used.
|
|-
|2802
|The entered NNID cannot be used.
|
|-
|2803
|Online Services cannot be used.
|
|-
|2812
|Console has been permanently banned by Nintendo for playing Pokémon Sun & Moon online before the release date.
|
|-
|2815
|Console has been permanently banned from accessing Miiverse by Nintendo.
|
|-
|2881
|The server is undergoing maintenance.
|
|-
|2882
|This online service has been discontinued.
|
|-
|2884
|This online service is not available in your country of residence.
|
|-
|2911
|Your ability to do online interactions has been restricted by Parental Controls.
|
|-
|5363
|The NNID settings failed to load due to an invalid language setting.
|
|-
|5515
|The network timed out.
|
|-
|5531
|Cannot connect to account servers.
|[https://support.nintendo.com/networkstatus Server Status and Maintenance]
|-
! colspan="3" |<h3> 026 - Account/eShop?</h3>
|-
|24xx
|Server returned a 4xx HTTP error.
|[https://www.nintendo.co.jp/netinfo/en_US/index.html Server Status and Maintenance]
|-
| 25xx
|Server returned a 5xx HTTP error.
|[https://www.nintendo.co.jp/netinfo/en_US/index.html Server Status and Maintenance]
|-
|3221
|Failed to unlink the NNID during formatting. Try again.
|-
|3278
|eShop gift cards cannot be used on the 3DS eShop. Add funds through the website or Nintendo Switch.
|
|-
! colspan="3" |<h3>032 - More Browser Errors </h3>
|-
|1035
|Unable to display the page.
|
|-
|1208
|Address not supported.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/43018/~/error-code%3A-032-1208 Nintendo Support Page]
|-
|1820
|The Internet Browser cannot confirm the security of the website. Note that the 3DS Internet Browser is fairly old and does not contain certificates for certain issuers, namely Let's Encrypt, so it may show this issue for some websites that work fine on a modern device.
|
|-
! colspan="3" |<h3>090 - In-Game Specific Errors </h3>
|-
|0212
|The game is permanently banned from Pokémon Global Link for using altered or illegal save data.
|
|}

[[Category:Nintendo 3DS information]]