User:Botman/3ds Assistance Regular Guide

Welcome to the 3DS assistance guide! If you're reading this, you most likely want to be better at helping in the Nintendo Homebrew Discord, but don't know where to start. This guide should serve as a helpful glossary and FAQ for those purposes.

General Advice

 * Don't try to solve an issue if you have no idea how to fix it.
 * Having only enough info to make educated guesses is fine, you're not expected to instantly find a solution. That's sometimes how it works even for the helpers.
 * You don't have to keep helping if someone's getting on your nerves. There will always be other people to find that person's issue.
 * Do NOT assist in dm. It is against the server rules, as we cannot monitor it.

Difference between software, firmware and hardware

 * Hardware is the console's physical parts, such as the RAM and CPU. This also includes things like the n3DS' NFC touchpoint.
 * Software is the 'encoded instructions' that cause the hardware to do specific things. This includes games, homebrew apps, system apps, etc.
 * Firmware is any software that runs directly on top of the hardware, such as its operating system. Despite its name, 'custom firmware' usually only patches the existing firmware rather than being an entirely new one.

Basic info on SOAP transfers
When a console connects to anything that uses the eShop servers, the eShop gets a full list of the titles available in that console's "eShop region" (including system apps) and compares this list against what is installed on the console. (Note that the eShop region is distinct from the region of the console's firmware.) After a console is region changed, the eShop gets a list of system apps that do not exist in the console's eShop region. This causes the error that blocks access to various online services.

To fix this, cleaninty is used along with the console's unique files to create a new eShop account in the correct region.

This usually requires donor files from an unusable console, so don't try to do it yourself. Ask on the Discord, and someone who already regularly does SOAPs will be able to help.

Useful Commands and Keywords
Here are some commands that are useful to know, as well as terms that are in common usage.













and : Display their respective rules' text, i.e.   shows rule 4,   shows rule 11, etc. .tag piracy adds to .r11 and sends this instead.















emuNAND: Short for emulated NAND. Used to be the way CFW was separated from the "stock" NAND, but this is no longer required. emuNANDs' only practical use now are for Korean games' fonts.
 * redNAND: An improved type of emuNAND that doesn't take up as much space on the SD. Otherwise identical.

sysNAND: The console's internal file storage. CFW can be safely installed to this without any notable risks.

Useful Programs
The following are apps or scripts that are commonly used or have extremely useful functionality for damaged consoles. Apps that are packaged with Finalizing Setup will be listed first.

Anemone3DS: A theme and splash screen manager.

Checkpoint: A save backup tool and cheat manager.

FBI: A file explorer and title manager.

GodMode9: A heavily multi-use tool, mainly used as a file explorer, game dumper, title manager, and to create NAND backups.

Luma3DS: The sole remaining CFW for the 3DS. Has several useful features and a built-in menu.

Universal-Updater: Homebrew browser and updater.

faketik: Creates new tickets for installed apps that lost theirs. Doesn't work if the apps themselves were deleted.

rverse: A third-party revival of Miiverse.

rehid: Allows remapping of the buttons and touchscreen based on specific inputs or what game is being played.

TWiLightMenu++: A DSi Menu upgrade/replacement, mainly used on the 3DS to play dumps of NDS games directly from the SD card.

TWPatch: Expands TWiLightMenu++'s visual capabilities, most notably by allowing for widescreen support.

Common troubleshooting situations
Some of the problems here are not actually "common" per se, but are instead included because they have a common cause and well-known solution.


 * If an error is occurring on boot and there is no known cause, see whether it keeps happening (including whether the error changes) if the SD is taken out. If it does, the issue is with the NAND.
 * If an error with the code  is happening within a game, use the tag with the same name. it will lead to  here.
 * If someone has Parental Controls enabled and wants to remove it, direct them to (not salthax, as that site isn't updated for the latest sys version).
 * If an  error happens when opening any DS mode software (a fast way to test is by opening Download Play -> Nintendo DS), link the   command (which is itself a redirect to 3DS:TWLFix).
 * If any one of the following things is happening to a console, link the hardware test and have the helpee send the contents of   after it finishes. This will test the RAM for errors.
 * The console repeatedly fails to boot and the notification LED is either red or magenta when it fails.
 * The console randomly and inconsistently crashes, regardless of whether the SD is inserted or not.
 * GodMode9 crashes.

Info on Older Setups
Before B9s, there were many other setups. below is a list of them and how to effectively move from that setup to B9s.

Gateway: Using the ds profile exploit to make a 3ds flashcart (note: this doesnt meant NTRboot)

Upgrade to B9s: WIP, sorry

Userland: Homebrew Launcher access, before cfw.

Upgrade to B9s: Follow Installing boot9strap (uloader) on 11.15.0 and below and Installing boot9strap (nimdsphax) on 11.16.0 and above.

Menuhax: (description WIP) Upgrade to B9s: Follow migrate from menuhax