Hacks Guide Wiki - User contributions [en]

3DS:History of 3DS Hacking

2025-03-29T01:03:16Z

StarlitSkies: remove approver magic word and shift zoogie credits to bottom of page

<references />
== 2011 ==

=== March ===
The official release of the Nintendo 3DS in the west, and the creation of the wiki [[3dbrew:Main_Page|3dbrew]].

=== June ===
The first 3DS roms are dumped.

=== September ===
Crown3DS gives a teaser implying the creation of a flashcart, but instead released a website written in broken English promising the community that they are progressing.

=== December ===
The first release of tools that convert video to the type of stereographic 3D video compatible with the Nintendo 3DS Camera.

== 2012 ==

=== Unknown Month ===
It is believed that Neimod's hardware RAM dumps and internal research led to the first userland and a9 exploits.<ref>https://gbatemp.net/threads/3ds-hacking-scene-history.443396/</ref>

=== March ===
The first (?) homebrew app is written in .cxi format, "Hello World", is written by Xcution (author of CiTRUS, a tool that allows BaNneR and ICoN files to be made using the .xbsf format)

== 2013 ==

=== August ===
The flashcart [[Gateway-3DS]] is first released, and serves as the sole option for homebrew in the 3DS' early years. At this time, there was basic arm9 homebrew possible via an [https://www.3dbrew.org/wiki/System_Settings MSET] exploit combined with [https://github.com/naehrwert/p3ds/tree/df8f52a8c22b7f4758e1a47b2ca712d12be60bc6 p3ds] (python tools for the 3DS).

=== December ===
Users in the community figure out how to reverse engineer [[Gateway-3DS]]' payload to create their own NAND emulation (or redirection). This leads to the users Smealum and Yellows8 creating a private payload called RedNAND.

== 2014 ==

=== January ===
brickgate/brickway - A scandal where Gateway released a FIRM that intentionally bricks consoles using Gateway3DS flashcart clones (such as R4 and Orange3DS). On top of this, its code was written badly enough that it triggered on many legitimate Gateway3DS cartridges, bricking completely 'innocent' users in the crossfire.

=== March ===
The first commit of [https://citra-emulator.com/ Citra], the first major 3DS emulator, is released.

=== August ===
The secondary userland exploit {{GitHub|yellows8/oot3dhax|oot3dhax}} is first released by yellows8.

=== November ===
[https://www.gamebrew.org/wiki/Palantine_CFW_3DS Palantine] (a CFW made by Yellows8 and other) is leaked, bringing a closed-source custom firmware to the public. However, it had limitations such as the EmuNAND not being updateable, having a low boot rate, and being difficult to install, among others. The thing it did best, running CIAs, would be taken and added to Gateway3DS shortly after.

The flashcart [[Sky3DS]] is first released. It could play pirated roms on entirely stock consoles, but couldn't run homebrew and had a very high ban risk due to the way it worked. This ban risk was unfixable until full custom firmware was released, and by that point it became obsolete anyway.

The primary userland exploit{{GitHub|smealum/ninjhax|ninjhax}} is first released by smealum.

== 2015 ==

=== January ===
Gateway cracks firmware version 9.2 and updates their flashcarts to OMEGA. The user yifanlu makes a blog post about reverse engineering the memchunkhax/firmlaunchhax combo used by Gateway, and teams such SALT, roxas75, and patois implement their own versions of it shortly after.

=== February ===
The custom firmware {{GitHub|roxas75/rxTools|rxTools}} is first released by roxas75, notable for being purely focused on utilitarian homebrew and trying to avoid piracy entirely to avoid all potential legal issues.

=== May ===
The custom firmware PastaCFW is first released. It is named after a leak of sigpatches on pastebin, which was combined with patois' Brahma (an open source memchunkhax/firmlaunchhax) to make the first open source custom firmware. Its only major caveat was that it had no emuNAND support.

A fork of rxTools with PastaCFW's sigpatches is released by ahp_person (appletinivi), causing roxas75 to openly dispute him in an attempt to stop piracy from becoming a legal issue for the wider homebrew community.

=== June ===
Once popular demand turns against him, roxas75 eventually gives in, releasing the rxTools source and officially adding sigpatches. He then, understandably, quits the homebrew scene immediately afterward and does not ever return.

=== July ===
The primary userland exploit Ninjhax2x is first released.

=== August ===
The exploits Tubehax and Ironhax are first released.
* Tubehax is a primary userland exploit that took advantage of the 3DS YouTube app, but was unfortunately patched only a couple months later on all versions.
* Ironhax is the first secondary (userland) exploit, meaning it requires extra leverage to work (usually from a primary exploit such as Tubehax).

ReiNand, the first fully-featured custom firmware to support the New 3DS, is released.

=== September ===
The exploits Menuhax and Browserhax are first released.
* Menuhax is a secondary userland exploit targeting the Home Menu. After the one use of a primary exploit needed to install it, it gives fully untethered coldboot userland access by exploiting the Home Menu automatically as it loads.
* Browserhax is a term for a series of primary userland exploits using the internet browsers for the n3DS and o3DS, which would become mainstays of the scene for a few more years before Nintendo finally killed off the potential for any new Browserhax.

=== December ===
An upgrade to Sky3DS, Sky3DS+, is released. Among others, its new features included bypassing cart-based AP in recent games and having a second button for more ease of selecting games.

The CCC hosts [https://gbatemp.net/threads/32c3-console-hacking-3ds-talk-dec-27-smea-derrek-plutoo.405640/ 32c3] in Hamburg, Germany. During 32c3, [https://smealum.github.io/3ds/32c3/ smealum gives a talk] where snshax, [[arm9loaderhax]], memchunkhax2, and ntrcardhax are revealed, & menuhax and ironhax receive updates to continue functioning.
* snshax and ntrcardhax would ultimately be of little interest, thanks to snshax being n3DS-only and ntrcardhax requiring an extremely specific type of modified flashcart that effectively didn't exist.
* memchunkhax2 is a privilege escalation k11 exploit that, although not immediately useful, would quickly become the foundation of downgrading as part of other exploit chains.
* Arm9loaderhax is an untethered coldboot custom firmware loader that is installed directly to the FIRM partitions. Although it was somewhat unsafe and risky to install through its entire lifetime, it was still a massive step forward for the homebrew community by allowing homebrew tools even larger amounts of control over the system.

== 2016 ==

=== January ===
An exploit chain using memchunkhax2 is introduced, the first implementation of downgrading from 10.x firmwares to 9.2 for certain other exploits.

Downgrading would soon after be patched by version 10.4.

=== February ===
[[arm9loaderhax]] is fully released, and becomes a mainstay of the scene.

The primary userland exploit ctr-httpwn is first released by yellows8.

A complex dispute between the original author of ReiNand (Reisyukaku) and the rest of its developer team hits its first overt boiling point, causing them to cut ties as much as possible and officially fork the project into AuReiNand.

=== March ===
The privilege escalation k11 exploit memchunkhax2.1 is first released by Aliaspider, which allowed 9.2 downgrades to resume until version 10.7 patched it a second time.

=== April ===
AuReiNand is renamed to Luma3DS, and work begins towards rewriting every line of code. Once this is done, they detach it from ReiNand's fork network on GitHub, which marks the point where it is converted into an entirely original project.

The tool {{GitHub|dazjo/salt_sploit_installer|salt_sploit_installer}} is first released, being unique because it sets the stage for three secondary userland exploits very shortly afterward.
Just a few days later, two of those three - {{GitHub|shinyquagsire23/v_hax|(v*)hax}} and {{GitHub|shinyquagsire23/supermysterychunkhax|supermysterychunkhax}} - are both first released by shinyquagsire23.

=== May ===
The third secondary userland exploit to use salt_sploit_installer, {{GitHub|dazjo/humblehax|humblehax}}, is first released by dazjo. This one is especially notable because it required purchasing a limited-time game from Humble Bundle, a quirk not seen in any exploit before or since.

=== June ===
The secondary userland exploit {{GitHub|MrNbaYoh/basehaxx|basehaxx}} is first released by MrNbaYoh.

=== July ===
A user reveals a DSiWare-based firm downgrade method after several months' worth of teasers. The release of this allowed 9.2 downgrades to continue on versions 11.0 - 11.2, before being patched a third time.

=== September ===
Arm9loaderhax gains two new tools that make its installation even easier: CTRNand Transfer (shortening the install time of both new and old 3DS) and OTPless (an instant N3DS install method). CTRNand Transfer would be kept and see far more use later, but OTPless was later removed from use due to having a small but completely random chance to brick.

=== December ===
The CCC hosts [https://gbatemp.net/threads/33c3-console-hacking-2016-3ds-wiiu-talk-dec-27-30-smea-derrek-nedwill-naehrwert.450043/ 33c3] in Hamburg, Germany. During 33c3, [https://derrekr.github.io/3ds/33c3/ derrekr gives a talk] where soundhax, fasthax, and sighax are revealed.
* Soundhax is a primary userland exploit targeting Nintendo 3DS Sound that was made by nedwill. Because it was free (unlike ninjhax, which required Cubic Ninja, a paid game), almost all consoles at the time were vulnerable to this exploit.
* Fasthax is another privilege escalation k11 exploit, also made by nedwill.
* [https://zoogie.github.io/sh/ Sighax] is a complex exploit of a vulnerability in the bootrom revealed by derrekr; when used properly, it allows anyone to sign arbitrary firmware code without restrictions. derrekr also revealed vague details about how he dumped the 3DS ARM9/ARM11 bootroms, though gave no detail about the exact code.<ref>https://wololo.net/2016/12/28/33c3-3ds-bootrom-cracked-sign-firmwares/</ref>

Nintendo launches a bug bounty program for the 3DS on HackerOne, with bounties from $100 - $20,000 per exploit. This caused exploit developers to start moving away from public releases.
== 2017 ==

=== January ===
The privilege escalation k9 exploit chain safehax is first released by the user appleTinivi, after an anonymous user posted the method on 3dbrew. Through the use of this exploit chain (usable on all versions up to 11.2), the process for installing a9lh was significantly streamlined: specifically, it shortens the list of needed steps to directly downgrading to 2.1, using exploits on 2.1 to get a copy of otp.bin, restoring the original NAND, and installing a9lh using the otp.

=== February ===
safehax and fasthax are patched by the release of version 11.3, also temporarily patching firm downgrading via DSiWare and hardmodding again in the process.

=== April ===
A previously-unknown privilege escalation k11 exploit, udsploit is first released by Smealum just as it's patched by the release of version 11.4. However, it remains useful for those who stayed on version 11.3.

Safehax is updated to work on 11.3 by AppleTinivi due to an oversight in Nintendo's previous patch for safehax.

=== May ===
SciresM creates and gives an unofficial sequel to 33c3, 33.5c3. [https://sciresm.github.io/33-and-a-half-c3/ During this talk], [[boot9strap]] and the concepts that would later allow [[ntrboot]] are revealed.
* Boot9strap is effectively the successor to arm9loaderhax, being another coldboot firmware loader that works in a much cleaner way by implementing a FIRM sighax signature. Because of how it works, it carries near-zero brick risk and gains control early enough to keep access to the bootroms and decrypted OTP, allowing it to dump them in software.
* Ntrboot allows for any correctly signed firm to be booted from a DS cartridge when the correct keycombo is held down, which also skips the entire normal boot process. This allows it to serve both as an instant custom firmware installation method and an extremely potent unbricking tool.

Since legitimate firms can now be created with nothing more than NAND access, DSiWare and hardmod-based downgrades resume on the latest firmware by using the known plaintext attack.

=== June ===
The n2DSXL is released in Australia, and it is quickly discovered that it happens to have the same vulnerable bootroms as the old 3DS models did.

=== August ===
The first practical implementation of [[Ntrboot]] is released, starting only with support for ak2i and R4 flashcards but quickly growing to others.

=== September ===
The Gateway team reveals they have been working on a new flashcard called [[Stargate]], a 3-in-1 hybrid of an ntrboot card, DS flashcart, and [[Sky3DS]]. It was abandoned after a few months due to people seeking out cheaper options for ntrboot cards.

== 2018 ==

=== January ===
A user reveals a method to brute-force the movable.sed using only the LocalFriendCodeSeed (which is obtainable in userland). This entrypoint, called [[3DS:Seedminer|Seedminer]], allowed users to inject hacked DSiWare and install [[boot9strap]] with only one 3DS.

=== July ===
Nintendo releases version 11.8.

=== August ===
Smealum reveals an arm9 exploit chain that he had been teasing at defcon, but it had already been patched in version 11.8 because he disclosed it to the HackerOne bug bounty program earlier on. As part of the reveal, he posted the incomplete repos on Github, but nobody to date has been able to make the exploit work.

=== September ===
The primary *miner exploit Frogminer is first released. This variant of the *miner exploit path utilizes an old version of the Japanese Flipnote Studio injected into DS Download Play instead of using Sudoku, meaning unlike its predecessor, it is a completely free *miner exploit.

=== December ===
Nintendo releases version 11.9, patching an unreleased browser exploit for both the O3DS and N3DS thanks to another HackerOne bounty submission by the userland exploit developer MrNbaYoh.

== 2019 ==

=== July ===
The primary userland exploit BannerBomb3, which targeted System Settings and mostly used the *miner series to complete the exploit chain, is first released.

=== December ===
The CCC hosts [https://gbatemp.net/threads/36c3-hacker-conference-underway-27th-to-30th-of-december-2019.555023/ 36c3] in Leipzig, Germany. During 36c3, [https://mrnbayoh.github.io/36c3/ MrNbaYoh gives a talk] that demonstrates a new primary exploit chain: using StreetPass tags, someone could remotely takeover a 3DS in userland and install custom firmware, with zero user interaction required. This would set up further exploits developed by TuxSH and Lazypixie which would take over the ARM11 kernel, and later on Safehax 2.x to also take over ARM9. However, due to its potential for malicious use (i.e. remotely bricking consoles), this exploit chain was submitted to HackerOne sometime earlier and patched in version 11.12, two months before 36c3 started.

== 2020 ==

=== April ===
The privilege escalation k9 exploit chain unSAFE_MODE, a revised version of safehax for version 11.13, is first released. Notably, this exploit chain would never be directly patched, but would be made unusuable when universal_otherapp is patched.

=== July ===
Nintendo's HackerOne bounty program [https://hackerone.com/nintendo/updates?type=team is closed on July 15th.]

=== August ===
The primary userland exploit new-browserhax, which is the simplest and most potent browserhax yet, is first released for both the n3DS and o3DS by zoogie. This begins a temporary 'golden age' where installing CFW is the easiest it ever has been, or will be (as of 2025-03-13).

=== September ===
Nintendo shuts down retail production of all 3DS models.

=== October ===
The secondary exploit menuhax67, the successor to Yellows8's menuhax, is first released by zoogie. This version of the exploit still requires initial userland access, but has even more privileges and is simpler to activate than the original. (And it's a great meme)

=== November ===
Nintendo releases version 11.14.0-46, patching a few last-minute submissions of exploits from the HackerOne bounty. This includes zoogie's new-browserhax, which ends the 'golden age' temporarily and changes the main userland entry point to back to Seedminer.

=== December ===
After the one month cooldown between each submission of bugs to HackerOne, MrNbaYoh and TuxSH disclose the entrypoint SSLoth and an exploit for it, safecerthax. Together, they create a full chain to boot9strap on o3DS models (and this chain still works on certain older versions, though it requires access to [[3DS:Safe Mode|Safe Mode]]).

TuxSH updates universal-otherapp to include a new exploit chain (based on smpwn, spipwn, khax and agbhax) that works on NATIVE_FIRM.

The primary userland exploit new-browserhax-xl is released by zoogie, resuming the 'golden age' of easy CFW installs.

== 2021 ==

=== January ===
Nintendo ends Unity3DS and many debugging/dev hardware items in one fell swoop.

=== April ===
The privilege escalation userland exploit chain nimhax, an expansion of ctr-httpwn that simultaneously takes over the nim sysmodule, is first released by luigoalma.

The primary userland exploit old-browserhax-xl is first released by zoogie, complementing new-browserhax-xl so that all consoles have a browser exploit available again.

The semi-primary userland exploit [[3DS:Kartdlphax|kartdlphax]], an exploit for Mario Kart 7 that requires a second modded console, is first released by PabloMK7 (creator of CTGP-7).

=== July ===
Nintendo releases version 11.15, which patches both browserhax-xl exploits, ending the 'golden age' for good in the process. It also patches SSLoth (which leaves safecerthax unpatched but unusuable), and as such Seedminer becomes the main exploit again.

== 2022 ==

=== August ===
Nintendo releases version 11.16, breaking TuxSH's universal-otherapp combo by patching smpwn.

Nintendo also lays the foundation for the eShop closure by updating MINT/ESHOP to handle shutting down eShop payments. Just two weeks later, they would update the NVER on this title due to a typo in the web data module.

=== December ===
The entrypoint ENLBufferPwn, an online RCE for Mario Kart 7, is disclosed by PabloMK7 after it was already patched in version 1.2 of the game. Although it had potential for custom firmware, PabloMK7 disclosed it because it could be used to remotely load universal-otherapp over the network; doing so would create a k9 exploit chain that also had potential for mass bricks, online cheats, remote installation of malware, or practically anything else (though with size constraints). By the time of disclosure, it was already being used in the wild to reset VR scores and interfere with races, making this claim of threat even more credible.

== 2023 ==

=== March ===
The primary userland exploit super-skaterhax, another n3DS-only browser exploit, is first released.

Nintendo closes the eShop on the 27th, restricting all exploits that relied on free games and DSiWare to people who had bought them before its close. These exploits were removed from the guide's main paths shortly after.

=== May ===
Nintendo releases version 11.17, patching BannerBomb3 and leaving the o3DS with no free softmod method for the first time in a while.

=== July ===
The privilege escalation "k11" exploit chain nimdsphax, an expansion of nimhax that also takes over the dsp sysmodule, is first released by TuxSH and luigoalma. It is notable in that it does not directly exploit k11, but instead disables GPU_PROT and then uses the GPU to directly overwrite k11 code.

The secondary exploit Kartminer7, a secondary *miner exploit also requiring a copy of Mario Kart 7 (can be either physical or digital), is first released by zoogie.

=== October ===
The primary k9 exploit MSET9, which targets System Settings and has no extra requirements, is first released by zoogie. This restores free softmod access for the o3DS, but also works consistently on the n3DS as well and is generally an extremely stable exploit.

=== December ===
Zoogie(?) calls it quits and is looking forward to future challenges whilst appreciating the time "he had helping people unlock their 3DSs!" -zoogie
<references />

(Credit to zoogie for writing "A Pretty Brief History of the 3ds Hacking/Homebrew Scene", the GBAtemp page that this page was heavily adapted from.)

User:StarlitSkies/signature

2025-03-26T00:20:43Z

StarlitSkies: version 2, done correctly this time

[[User:StarlitSkies|<span style="font-family: Cambria; font-weight: bold;color: indigo">Starlit</span><span style="font-family: Cambria; font-weight: bold;color: mediumblue">Skies</span>]] ([[User talk:StarlitSkies|<span style="font-family: Cambria; font-weight: bold;color: gold">talk</span>]])

User:StarlitSkies/signature

2025-03-26T00:09:00Z

StarlitSkies: my signature sucked anyway, this is a nice time for a revamp

<span style="font-family: Cambria;color: indigo; font-weight: bold">[[User:StarlitSkies|Starlit<span style="color: mediumblue">Skies</span>]] ([[User talk:StarlitSkies|<span style="color: gold">talk</span>]])</span>

User:StarlitSkies/test/subtest

2025-03-25T23:56:06Z

StarlitSkies: this concludes the FitnessGram™ Pacer Test

User:StarlitSkies/test/subtest

2025-03-25T23:51:58Z

StarlitSkies: funni signature nonsense go brrr

test 1: <span style="font-family: Cambria;color: cornflowerblue">[[User:StarlitSkies|Starlit<span style="color: cyan">Skies</span>]] ([[User talk:StarlitSkies|talk]])</span>
this should be the same as this: <span style="font-family: Cambria;color: cornflowerblue">[[User:StarlitSkies|Starlit<span style="color: cyan">Skies</span>]] ([[User talk:StarlitSkies|talk]])</span>

test 2: <span style="font-family: Cambria;color: goldenrod">[[User:StarlitSkies|Starlit<span style="color: cyan">Skies</span>]] ([[User talk:StarlitSkies|talk]])</span>
test 3: <span style="font-weight: bold;color: gold">[[User:StarlitSkies|Wario<span style="color: purple">hax</span>]] ([[User talk:StarlitSkies|talk]])</span>
test 4: <span style="font-weight: bold;color: gold">[[User:Wariohax|Wario<span style="color: purple">hax</span>]] ([[User talk:Wariohax|talk]])</span>

3DS:Error screens/Luma3DS exception screen

2025-03-21T17:45:57Z

StarlitSkies: reassort and condense the multi-error headers in Arm11 for better readability, plus minor info fixes (mostly to loader and app/ctrapp/etc.)

{{shortcut|3DS:EXCEPTION}}
This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues.

== Reading a Luma3DS exception screen ==

A Luma3DS exception has four (or five, in a few cases) different parts to it that help in finding its cause, as follows:
[[File:Luma3DS_exception.png|center]]
* '''Processor:''' What part of the system is causing the exception. The two processors are:
** '''Arm9:''' The 'security processor' of the system. These exceptions are usually raised because of errors in NAND data or hardware faults in either the 3DS or its SD card.
** '''Arm11:''' The 'userland' of the system. These exceptions have numerous causes but are more often related to broken software or user data.
* '''Exception type:''' The type of fault that caused the exception. These categories correspond to the ARM exceptions for the [https://developer.arm.com/documentation/ddi0201/d ARM9] and [https://developer.arm.com/documentation/ddi0360/f ARM11] CPUs, as follows:
** '''data abort''': Caused by a read or write to an invalid part of memory. Usually related to game mods/cheats/plugins, broken HOME Menu data, and/or broken CFW applications.
** '''prefetch abort''': Caused by an attempt to execute a CPU instruction that was marked as invalid. Often related to conflicts between CFW and other software.
** '''prefetch abort (svcBreak)''': Caused by either Process9 or homebrew software manually halting because it tripped a pre-defined error condition. Often related to damage to NAND data, even when raised by Arm11. Can also happen when launching an out-of-region game that isn't [[3DS:SGL|locale emulated.]]
** '''prefetch abort (kernel panic)''': Caused by Kernel9 detecting an unrecoverable error and forcibly halting to avoid causing damage. Can be related to any of several things, but hardware issues are the most likely.
** '''undefined instruction''': Caused by an attempt to execute a CPU instruction that was unimplemented, disallowed, or unusable. Often related to software missing its required files (if not on boot) or an outdated <code>boot.firm</code> (if on boot).
* '''Fault status:''' The specific type of ARM exception that was raised. Helpful for developers, but not so much for the end user.
* '''Current process:''' Where the error is coming from in the system. Often the most helpful part of the exception. Some examples of processes are as follows:
** '''fs''': The filesystem, i.e. either the SD card or the NAND.
** '''menu''': Data that is opened either as a part of the HOME Menu or at the same time as it.
** '''loader''': The service that opens apps, meaning the app most recently opened has an issue.
** '''nwm''': Networking services, almost always Wi-Fi.
** '''ns''': The <u>N</u>intendo User Interface <u>S</u>hell, which handles all apps/processes/services in 3DS mode.
* '''Registers (R0-R12/SP/LR/PC/CPSR/FPEXC)''': Usually just internal data that's not worth reading, though R0 is the most likely of them to contain useful data. There are certain notable exceptions that aren't mentioned in the list of known errors, however:
** If the value <code>000400??</code> (the ? marks can be any number) appears in any of the registers, it likely refers to the first half of a title ID - check the value of the register after it to ensure this. If it is a title ID, it can be used to narrow down the original cause of an error.
** If the value of any register starts with the letter C, D, E, or F (even if it isn't in R0) and doesn't look completely random, it may be an error code - this is more likely if the value starts with C or D. You may want to check it manually, as if it is an error code, it can likely help in troubleshooting.

== Known Errors ==

In the following list, the file prefixes on file paths refer to the starting location. <code>sd:/</code> refers to the SD card, and numbers in the format of <code>[X:]</code> refer to GodMode9's drive numbers.
{{info|If the below fixes do not solve your issue or you are unsure of what to do, join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] for further assistance.}}
----

=== <big>Arm9</big> ===

Arm9 errors are sorted by their '''exception type'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>Any Type</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that the SD card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try booting again.
* A system save located on the NAND in <code>[1:]/data</code> has a problem.
* System-unique files are missing from the NAND in <code>[1:]/rw/sys</code>.

<h5>data abort</h5>
* The <code>shared2</code> folder in <code>[2:] SYSNAND TWLN</code> is missing.
** To fix, create this folder.
* System titles have been deleted.
** To fix, perform a [[3DS:Safe Mode|Safe Mode update]]. If this does not work, perform a [[3DS:CTRTransfer|CTRTransfer]].

<h5>prefetch abort (svcBreak)</h5>
* The system movable, <code>[1:]/private/movable.sed</code>, is 288 bytes but a flag is enabled that expects a size of 320 bytes.
** To fix, boot into GodMode9 and select <code>SYSNAND CTRNAND</code>, then go into the <code>private</code> folder.<br>Inside this folder, you will see a file named <code>movable.sed</code>. Select it, and under the options menu, select '''Show in Hexeditor'''.<br>Green-colored numbers will appear in the middle of the screen - press {{B|A}} and then unlock '''writing to sysNAND (lvl2)'''.<br>At the beginning of the file, look for the set of numbers <code>53 45 45 44 00 01</code>. Once you find these numbers, hold {{B|A}} and press {{B|D-PAD DOWN}} while the <code>01</code> value is highlighted to change it to <code>00</code>. Press {{B|B}}, then {{B|A}}, then {{B|B}} to save changes and exit from the hexeditor, then press {{B|START}} to reboot your console.
* <code>SYSNAND CTRNAND</code> has bad CMACs.
** To fix, press R+A on the <code>SYSNAND CTRNAND</code> drive and <code>Fix CMACs for drive</code>. The console will act like it has been formatted after this, and this is intended.
*If none of the above have worked, perform a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]].

<h5>prefetch abort (kernel panic)</h5>
* The console likely has a hardware issue.

<h5>undefined instruction</h5>
* The console likely has a hardware issue, or corrupted sysmodules. Try performing a [[3DS:CTRTransfer|CTRTransfer]] to see if it resolves the issue.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>data abort</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that your card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try again.

=== <big>Arm11</big> ===

All Arm11 errors are sorted by their '''current process''', except for entries that can apply to multiple processes; these always appear first in the list for simplicity.
<br>If an error appears in the <code>Error At Any Time</code> section, do not look for it in the other two sections.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>gsp/i2c/mcu/pxi/spi</h5>
* The console has a serious hardware issue that is likely not easily fixable.
** Run [[3DS:Hardware test|3ds_hw_test]]. If the test returns zero errors detected, join [https://discord.gg/C29hYvh the Nintendo Homebrew Discord] and ask, in English, for help.

<h5>act</h5>
* Your NNID(s)' stored data is misconfigured or being interfered with.
** To fix, if [https://pretendo.network Pretendo] is installed, turn it off by disabling <code>Enable loading external FIRMs and modules</code> on [[3DS:Luma3DS/Configuration|the Luma configuration menu]].
*** If this does not help or Pretendo is not installed, then [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|restore a NAND backup]] - especially if you recently tried to [[3DS:GodMode9/Usage#Removing_an_NNID_without_formatting_your_device|log out an NNID]].

<h5>boss</h5>
* <h6>Outdated firmware (11.16 or older):</h6>
** The current firmware version may be too old for SpotPass to work. Perform a [[3DS:Safe Mode|Safe Mode update]].
*** If this does not work, you may require [[3DS:CTRTransfer|a CTRTransfer.]]
* <h6>Latest firmware (11.17):</h6>
** An installation of NetPass is likely interfering with your console. To check this, do the following steps:
**# Hold {{B|SELECT}} while powering on the console
**# Within the [[3DS:Luma3DS/Configuration|Luma config menu]], disable <code>Enable loading external FIRMs and modules</code>
**# Either press {{B|START}} or press {{B|A}} on the <code>Save and exit</code> option to save changes and exit the config menu
**# If the issue stops after this, go into the folder <code>sd:/luma/sysmodules</code> and delete the files <code>0004013000003402.ips</code> and <code>0004013000002602.ips</code> to remove NetPass entirely.

<h5>camera</h5>
* Potential hardware issues, or an instance of ShutTheCamUp is crashing.
** Look for and delete <code>/luma/sysmodules/0004013000001602.ips</code> and <code>/luma/titles/0004013000001602/code.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the correct Old or New 3DS patch for [[udb:3ds/shut-the-cam-up|ShutTheCamUp]] if you wish to continue using it.
*** If these don't exist, or the error occurs when booting without an SD card, it's likely hardware issues. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.

<h5>cfg</h5>
* Either the NAND [[3dbrew:Config Savegame|config savegame]] or part of your console-unique file(s) is damaged.
** To fix, first boot into GodMode9, press R+A while the cursor is on the folder <code>[1:]/data/<ID0>/sysdata/00010017</code>, choose to <code>Copy to 0:/gm9/out</code>, then delete the folder. After rebooting, the console will enter initial setup again; this is intended and not an issue.
*** If this does not help, delete the newly created <code>00010017</code> and copy the backup into its place, run [[3DS:ctrcheck|ctrcheck]], and replace any console-unique files marked as invalid or missing with the copies from the <code>essentials.exefs</code> backup inside <code>[S:] SYSNAND VIRTUAL</code> in GodMode9.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|Fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]] and trying to trigger the error with the SD card removed from the console.<br>If the error stops when the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>hid</h5>
* Either an instance of rehid is crashing, or your console may have hardware damage.
** First look for and delete <code>/luma/titles/0004013000001D02</code>, <code>/luma/titles/0004013000003302</code>, <code>/luma/sysmodules/0004013000001D02.cxi</code> and <code>/luma/sysmodules/0004013000003302.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the latest release of [[3DS:Rehid|rehid]] to continue using it.
*** If these don't exist, or rehid has never been installed on this console, it's likely hardware issues. [[3DS:Hardware test|3ds_hw_test]] or [[3DS:ctrcheck|ctrcheck]] may help with fault isolation.

<h5>loader</h5>
* <h6>prefetch abort (svcBreak)</h6>
**The code or sysmodule patch Luma3DS tried to load is invalid or corrupt.
***To fix: Redownload any recently installed patches (eg. Nimbus (Pretendo), Wumiibo, or anything else that goes in <code>/luma/titles</code> or <code>/luma/sysmodules</code>.) Alternatively, you may disable <code>loading external FIRMs and modules</code> as well as <code>Enable game patching</code> in the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]].

<h5>mset</h5>
* System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] and ask, in English, for help.

<h5>menu</h5>
* <h6>data abort</h6>
** The installed [[3DS:Custom themes|theme]] is corrupted or otherwise broken.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>000002cd</code><br>EUR: <code>000002ce</code><br>JPN: <code>000002cc</code>
** The HOME Menu's extra data is corrupted.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>0000008f</code><br>EUR: <code>00000098</code><br>JPN: <code>00000082</code><br>KOR: <code>000000A9</code>
** An installed application is corrupted or otherwise broken.
*** To fix, either perform a [[3DS:Safe Mode|Safe Mode update]], attempt to enter System Settings before the crash occurs and delete the application in Data Management, or [[Formatting an SD card|reformat the SD card]].
* <h6>prefetch abort</h6>
** An installation of Menuhax is conflicting with the custom firmware.
*** To fix, follow the directions [[3DS:Troubleshooting/removing_menuhax67|on this page]].
**If this occurs on boot, set '''Hbmenu autoboot''' in the [[3DS:Luma3DS/Configuration|Luma configuration menu]] to 3DS, then follow the above instructions and turn '''Hbmenu autoboot''' back off once it has been removed.
***Ensure in <code>sd:/luma/config.ini</code> that hbldr_3dsx_titleid is set to 000400000d921e00 and <code>boot.3dsx</code> is in the root.
* <h6>prefetch abort (svcBreak)</h6>
** If <code>R5</code> contains <code>D900458B</code>: The <code>f000000b</code> folder in <code>SYSNAND CTRNAND</code> is broken, its exact location being at <code>[1:]/data/<ID0>/extdata/00048000/f000000b</code>.
*** To fix, backup <code>f000000b</code> by pressing R+A while highlighting it, then selecting <code>Copy to 0:/gm9/out</code>. Once it is backed up, delete the folder. If this does not fix the issue, copy the folder back where it was.
**System titles are missing. Perform a [[3DS:Safe Mode|Safe Mode update]].
**If you have a recent NAND backup, try restoring it with [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|this guide]]

<h5>ns</h5>
* The [[3DS:Luma3DS/Configuration|Luma configuration]] setting '''Hbmenu autoboot''' is set to boot to a title that does not exist.
** To fix, disable the option, install an application with the title ID in <code>sd:/luma/config.ini</code>, or change the set title ID to match an application that does exist.

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi using an external switch. New models do not have this switch disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pm</h5>
* The installed version of Luma3DS likely does not support the current firmware version. This is guaranteed to be true if the contents of R0 are <code>E0E01BF5</code>.
** To fix, [[3dsguide:restoring-updating-cfw|update CFW.]]

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>app/CtrApp/IbizaCit/Joker/Kirby3DS/Kujira/niji_loc/etc.</h5>
* The app you most recently opened is attempting to load corrupt code, instructions, or patches. As this type of error can happen to nearly anything on the console, if your listed '''current process''' does not show up anywhere else under Arm11, it may help to follow these instructions anyway.
** First, turn off all game mods, cheat codes, plugins, and [[3DS:Luma3DS/Configuration|both the settings <code>Game patching</code> and <code>loading external FIRMs and modules</code> in the Luma config menu]] to stop all external interference.<br>If this fixes the issue, redownload all of those types of patches that you had enabled for the game(s) before turning them back on. If it does not fix the issue, check whether the game is the same region as the console and [[3DS:SGL|activate locale emulation]] if it is not.
*** If the error continues after trying all of the above, then the game itself is likely faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it. If it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it. If it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.

<h5>3dsx_app</h5>
* The <code>.3dsx</code> file that was most recently opened is corrupted.
** To fix, download a new copy of the <code>.3dsx</code> file. If this error happens when opening the Homebrew Launcher, download a new copy of <code>boot.3dsx</code>.
**: If the error still happens, [[Checking SD card integrity|test the SD card for errors.]]

<h5>GARDEN</h5>
* Animal Crossing's game data or savedata is having issues.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, then the game itself may be faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
*** If the error yet still happens, ensure that you have not used a save editor before the error started happening. If you have used a save editor, the edits are broken and you will need to restore a backed-up save, or wipe the save and start over if you have no backup.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]] and trying to recreate the error without the SD card inserted.<br>If the error stops after the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>loader</h5>

* <h6>undefined instruction</h6>
** The app most recently opened is trying to load invalid, missing, or corrupt data. If the value of R0 starts with C or D, it is an error code, and has a chance of being an error code if the value starts with E or F. A large number of such error codes can be found at [[3DS:ERRDISP|this page]], but here are the most common values seen in this error:
*** <code>D9004587</code>: When trying to open a game: The game is corrupted, or its seed is not imported.
**** To fix: Follow [[3DS:FCG|the corrupted games guide]]
*** <code>C8804478</code>: If trying to open the Homebrew Launcher: <code>boot.3dsx</code> is missing from the root of your SD card.
**** To fix: Download the latest Homebrew Launcher from [https://github.com/devkitPro/3ds-hbmenu/releases/latest here]
*** <code>C88044AB</code>: If trying to open the Homebrew Launcher: Your SD card either is not properly inserted, or cannot be read by the console.
**** To fix: Try to reinsert the SD more firmly, and check whether its data can be read on boot. If it can't, then [[Formatting an SD card|reformat the SD]].
*** <code>D96077FA</code>/<code>FFFFFFFF</code>: The <code>.3dsx</code> that Luma3DS tried to load is corrupted.
**** To fix, redownload the app you are trying to launch. If this happens when you try to open the Homebrew Launcher itself, see the error above.
*** Most of the other possible error codes that can appear here are listed on [[3DS:Error_screens/Luma3DS_ErrDisp|the ErrDisp page]].
* <h6>prefetch abort (svcBreak)</h6>
**The code or sysmodule patch Luma3DS tried to load is invalid or corrupt.
***To fix: Redownload any recently installed patches (eg. Nimbus (Pretendo), Wumiibo, or anything else that goes in <code>/luma/titles</code> or <code>/luma/sysmodules</code>.) Alternatively, you may disable <code>loading external FIRMs and modules</code> as well as <code>Enable game patching</code> in the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]].

<h5>mset</h5>
* '''If not occurring in Nintendo DS Profile:''' System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.
* '''If occurring in Nintendo DS Profile:''' Your NVRAM either is corrupted or is suffering from hardware damage. Run [[3DS:ctrcheck|ctrcheck]] - if its results do not include <code>Critical: NVRAM is inaccessible</code>, then follow [[3DS:NVRAM|the Fix NVRAM guide]].

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi with an external switch. New models must instead disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pxi</h5>
* Could be anything from a faulty cartridge to damaged internal components, but will almost always be some type of hardware issue.

<h5>pm</h5>
* The software you have launched may be missing required files. If the value in R0 is <code>E0E01BF5</code>, this is extremely likely to be the cause.

<h5>qtm/cam</h5>
* The camera's hardware is damaged or dead.
** To fix, replace the camera with a new one. To avoid the error until then, disconnect the camera or avoid using anything that activates the camera.

<h5>swkbd</h5>
* The software keyboard is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.

[[Category:Unbricking]]
[[Category:Nintendo 3DS troubleshooting]]
{{Short description|Guide to the CFW error handler}}

3DS:Error screens/Luma3DS exception screen

2025-03-21T17:13:42Z

StarlitSkies: expand game-specific processes fixes under Arm11 Error During Use and move it to the top of that section

{{shortcut|3DS:EXCEPTION}}
This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues.

== Reading a Luma3DS exception screen ==

A Luma3DS exception has four (or five, in a few cases) different parts to it that help in finding its cause, as follows:
[[File:Luma3DS_exception.png|center]]
* '''Processor:''' What part of the system is causing the exception. The two processors are:
** '''Arm9:''' The 'security processor' of the system. These exceptions are usually raised because of errors in NAND data or hardware faults in either the 3DS or its SD card.
** '''Arm11:''' The 'userland' of the system. These exceptions have numerous causes but are more often related to broken software or user data.
* '''Exception type:''' The type of fault that caused the exception. These categories correspond to the ARM exceptions for the [https://developer.arm.com/documentation/ddi0201/d ARM9] and [https://developer.arm.com/documentation/ddi0360/f ARM11] CPUs, as follows:
** '''data abort''': Caused by a read or write to an invalid part of memory. Usually related to game mods/cheats/plugins, broken HOME Menu data, and/or broken CFW applications.
** '''prefetch abort''': Caused by an attempt to execute a CPU instruction that was marked as invalid. Often related to conflicts between CFW and other software.
** '''prefetch abort (svcBreak)''': Caused by either Process9 or homebrew software manually halting because it tripped a pre-defined error condition. Often related to damage to NAND data, even when raised by Arm11. Can also happen when launching an out-of-region game that isn't [[3DS:SGL|locale emulated.]]
** '''prefetch abort (kernel panic)''': Caused by Kernel9 detecting an unrecoverable error and forcibly halting to avoid causing damage. Can be related to any of several things, but hardware issues are the most likely.
** '''undefined instruction''': Caused by an attempt to execute a CPU instruction that was unimplemented, disallowed, or unusable. Often related to software missing its required files (if not on boot) or an outdated <code>boot.firm</code> (if on boot).
* '''Fault status:''' The specific type of ARM exception that was raised. Helpful for developers, but not so much for the end user.
* '''Current process:''' Where the error is coming from in the system. Often the most helpful part of the exception. Some examples of processes are as follows:
** '''fs''': The filesystem, i.e. either the SD card or the NAND.
** '''menu''': Data that is opened either as a part of the HOME Menu or at the same time as it.
** '''loader''': The service that opens apps, meaning the app most recently opened has an issue.
** '''nwm''': Networking services, almost always Wi-Fi.
** '''ns''': The <u>N</u>intendo User Interface <u>S</u>hell, which handles all apps/processes/services in 3DS mode.
* '''Registers (R0-R12/SP/LR/PC/CPSR/FPEXC)''': Usually just internal data that's not worth reading, though R0 is the most likely of them to contain useful data. There are certain notable exceptions that aren't mentioned in the list of known errors, however:
** If the value <code>000400??</code> (the ? marks can be any number) appears in any of the registers, it likely refers to the first half of a title ID - check the value of the register after it to ensure this. If it is a title ID, it can be used to narrow down the original cause of an error.
** If the value of any register starts with the letter C, D, E, or F (even if it isn't in R0) and doesn't look completely random, it may be an error code - this is more likely if the value starts with C or D. You may want to check it manually, as if it is an error code, it can likely help in troubleshooting.

== Known Errors ==

In the following list, the file prefixes on file paths refer to the starting location. <code>sd:/</code> refers to the SD card, and numbers in the format of <code>[X:]</code> refer to GodMode9's drive numbers.
{{info|If the below fixes do not solve your issue or you are unsure of what to do, join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] for further assistance.}}
----

=== <big>Arm9</big> ===

Arm9 errors are sorted by their '''exception type'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>Any Type</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that the SD card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try booting again.
* A system save located on the NAND in <code>[1:]/data</code> has a problem.
* System-unique files are missing from the NAND in <code>[1:]/rw/sys</code>.

<h5>data abort</h5>
* The <code>shared2</code> folder in <code>[2:] SYSNAND TWLN</code> is missing.
** To fix, create this folder.
* System titles have been deleted.
** To fix, perform a [[3DS:Safe Mode|Safe Mode update]]. If this does not work, perform a [[3DS:CTRTransfer|CTRTransfer]].

<h5>prefetch abort (svcBreak)</h5>
* The system movable, <code>[1:]/private/movable.sed</code>, is 288 bytes but a flag is enabled that expects a size of 320 bytes.
** To fix, boot into GodMode9 and select <code>SYSNAND CTRNAND</code>, then go into the <code>private</code> folder.<br>Inside this folder, you will see a file named <code>movable.sed</code>. Select it, and under the options menu, select '''Show in Hexeditor'''.<br>Green-colored numbers will appear in the middle of the screen - press {{B|A}} and then unlock '''writing to sysNAND (lvl2)'''.<br>At the beginning of the file, look for the set of numbers <code>53 45 45 44 00 01</code>. Once you find these numbers, hold {{B|A}} and press {{B|D-PAD DOWN}} while the <code>01</code> value is highlighted to change it to <code>00</code>. Press {{B|B}}, then {{B|A}}, then {{B|B}} to save changes and exit from the hexeditor, then press {{B|START}} to reboot your console.
* <code>SYSNAND CTRNAND</code> has bad CMACs.
** To fix, press R+A on the <code>SYSNAND CTRNAND</code> drive and <code>Fix CMACs for drive</code>. The console will act like it has been formatted after this, and this is intended.
*If none of the above have worked, perform a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]].

<h5>prefetch abort (kernel panic)</h5>
* The console likely has a hardware issue.

<h5>undefined instruction</h5>
* The console likely has a hardware issue, or corrupted sysmodules. Try performing a [[3DS:CTRTransfer|CTRTransfer]] to see if it resolves the issue.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>data abort</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that your card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try again.

=== <big>Arm11</big> ===

All Arm11 errors are sorted by their '''current process'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>Kujira/Joker/niji_loc/IbizaCit/Kirby3DS/etc.</h5>
* These processes are game-specific ones, meaning the game you most recently opened is attempting to load corrupt code, instructions, or patches. If your listed '''current process''' does not show up anywhere in the Arm11 section, it may help to follow these instructions anyway.
** First, disable all game mods, cheat codes, plugins, and [[3DS:Luma3DS/Configuration|turn off both <code>Game patching</code> and <code>loading external FIRMs and modules</code> in the Luma config menu]] to stop all external interference.
If this fixes the issue, redownload all of the patches you had enabled for the game(s) before turning these settings back on. If it does not fix the issue, check whether the game is the same region as the console and [[3DS:SGL|activate locale emulation]] if it is not.
*** If the error continues after trying all of the above, then the game itself is likely faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it. If it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it. If it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.

<h5>act</h5>
* Your NNID(s)' stored data is misconfigured or being interfered with.
** To fix, if [https://pretendo.network Pretendo] is installed, turn it off by disabling <code>Enable loading external FIRMs and modules</code> on [[3DS:Luma3DS/Configuration|the Luma configuration menu]].
*** If this does not help or Pretendo is not installed, then [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|restore a NAND backup]] - especially if you recently tried to [[3DS:GodMode9/Usage#Removing_an_NNID_without_formatting_your_device|log out an NNID]].

<h5>boss</h5>
* <h6>Outdated firmware (11.16 or older):</h6>
** The current firmware version may be too old for SpotPass to work. Perform a [[3DS:Safe Mode|Safe Mode update]].
*** If this does not work, you may require [[3DS:CTRTransfer|a CTRTransfer.]]
* <h6>Latest firmware (11.17):</h6>
** An installation of NetPass is likely interfering with your console. To check this, do the following steps:
**# Hold {{B|SELECT}} while powering on the console
**# Within the [[3DS:Luma3DS/Configuration|Luma config menu]], disable <code>Enable loading external FIRMs and modules</code>
**# Either press {{B|START}} or press {{B|A}} on the <code>Save and exit</code> option to save changes and exit the config menu
**# If the issue stops after this, go into the folder <code>sd:/luma/sysmodules</code> and delete the files <code>0004013000003402.ips</code> and <code>0004013000002602.ips</code> to remove NetPass entirely

<h5>camera</h5>
* Potential hardware issues, or an instance of ShutTheCamUp is crashing.
** Look for and delete <code>/luma/sysmodules/0004013000001602.ips</code> and <code>/luma/titles/0004013000001602/code.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the correct Old or New 3DS patch for [[udb:3ds/shut-the-cam-up|ShutTheCamUp]] if you wish to continue using it.
*** If these don't exist, or the error occurs when booting without an SD card, it's likely hardware issues. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.

<h5>cfg</h5>
* Either the NAND [[3dbrew:Config Savegame|config savegame]] or part of your console-unique file(s) is damaged.
** To fix, first boot into GodMode9, press R+A while the cursor is on the folder <code>[1:]/data/<ID0>/sysdata/00010017</code>, choose to <code>Copy to 0:/gm9/out</code>, then delete the folder. After rebooting, the console will enter initial setup again; this is intended and not an issue.
*** If this does not help, delete the newly created <code>00010017</code> and copy the backup into its place, run [[3DS:ctrcheck|ctrcheck]], and replace any console-unique files marked as invalid or missing with the copies from the <code>essentials.exefs</code> backup inside <code>[S:] SYSNAND VIRTUAL</code> in GodMode9.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|Fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]] and trying to trigger the error with the SD card removed from the console.<br>If the error stops when the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>hid</h5>
* Potential hardware problems, or an instance of rehid is crashing.
** First look for and delete <code>/luma/titles/0004013000001D02</code>, <code>/luma/titles/0004013000003302</code>, <code>/luma/sysmodules/0004013000001D02.cxi</code> and <code>/luma/sysmodules/0004013000003302.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the latest release of [[3DS:Rehid|rehid]] to continue using it.
*** If these don't exist, or rehid has never been installed on this console, it's likely hardware issues. [[3DS:Hardware test|3ds_hw_test]] or [[3DS:ctrcheck|ctrcheck]] may help with fault isolation.

<h5>i2c/gsp/mcu/pxi/spi/</h5>
* The console has a serious hardware issue that is likely not easily fixable.
** Run [[3DS:Hardware test|3ds_hw_test]]. If the test returns zero errors detected, join [https://discord.gg/C29hYvh the Nintendo Homebrew Discord] and ask, in English, for help.

<h5>loader</h5>
* <h6>prefetch abort (svcBreak)</h6>
**The code or sysmodule patch Luma3DS tried to load is invalid or corrupt.
***To fix: Redownload any recently installed patches (eg. Nimbus (Pretendo), Wumiibo, or anything else that goes in <code>/luma/titles</code> or <code>/luma/sysmodules</code>.) Alternatively, you may disable <code>loading external FIRMs and modules</code> as well as <code>Enable game patching</code> in the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]].

<h5>mset</h5>
* System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] and ask, in English, for help.

<h5>menu</h5>
* <h6>data abort</h6>
** The installed [[3DS:Custom themes|theme]] is corrupted or otherwise broken.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>000002cd</code><br>EUR: <code>000002ce</code><br>JPN: <code>000002cc</code>
** The HOME Menu's extra data is corrupted.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>0000008f</code><br>EUR: <code>00000098</code><br>JPN: <code>00000082</code><br>KOR: <code>000000A9</code>
** An installed application is corrupted or otherwise broken.
*** To fix, either perform a [[3DS:Safe Mode|Safe Mode update]], attempt to enter System Settings before the crash occurs and delete the application in Data Management, or [[Formatting an SD card|reformat the SD card]].
* <h6>prefetch abort</h6>
** An installation of Menuhax is conflicting with the custom firmware.
*** To fix, follow the directions [[3DS:Troubleshooting/removing_menuhax67|on this page]].
**If this occurs on boot, set '''Hbmenu autoboot''' in the [[3DS:Luma3DS/Configuration|Luma configuration menu]] to 3DS, then follow the above instructions and turn '''Hbmenu autoboot''' back off once it has been removed.
***Ensure in <code>sd:/luma/config.ini</code> that hbldr_3dsx_titleid is set to 000400000d921e00 and <code>boot.3dsx</code> is in the root.
* <h6>prefetch abort (svcBreak)</h6>
** If <code>R5</code> contains <code>D900458B</code>: The <code>f000000b</code> folder in <code>SYSNAND CTRNAND</code> is broken, its exact location being at <code>[1:]/data/<ID0>/extdata/00048000/f000000b</code>.
*** To fix, backup <code>f000000b</code> by pressing R+A while highlighting it, then selecting <code>Copy to 0:/gm9/out</code>. Once it is backed up, delete the folder. If this does not fix the issue, copy the folder back where it was.
**System titles are missing. Perform a [[3DS:Safe Mode|Safe Mode update]].
**If you have a recent NAND backup, try restoring it with [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|this guide]]

<h5>ns</h5>
* The [[3DS:Luma3DS/Configuration|Luma configuration]] setting '''Hbmenu autoboot''' is set to boot to a title that does not exist.
** To fix, disable the option, install an application with the title ID in <code>sd:/luma/config.ini</code>, or change the set title ID to match an application that does exist.

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi using an external switch. New models do not have this switch disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pm</h5>
* The installed version of Luma3DS likely does not support the current firmware version. This is guaranteed to be true if the contents of R0 are <code>E0E01BF5</code>.
** To fix, [[3dsguide:restoring-updating-cfw|update CFW.]]

<span style="font-size:140%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>3dsx_app</h5>
* The <code>.3dsx</code> file that was most recently opened is corrupted.
** To fix, download a new copy of the <code>.3dsx</code> file. If this error happens when opening the Homebrew Launcher, download a new copy of <code>boot.3dsx</code>.
**: If the error still happens, [[Checking SD card integrity|test the SD card for errors.]]

<h5>app/CtrApp</h5>
* If not <code>prefetch abort (svcBreak)</code>: The app most recently opened is trying to use broken software.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause.
**: If the error still happens, then the game itself is likely faulty. If it is a system app, [[3DS:CTRTransfer|perform a CTRTransfer]]. Otherwise, if it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
* If <code>prefetch abort (svcBreak)</code>: The app most recently opened is out-of-region and relies on locale-specific data. Activate [[3DS:SGL|locale emulation]] for it.

<h5>GARDEN</h5>
* Animal Crossing's game data or savedata is having issues.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, then the game itself may be faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
*** If the error yet still happens, ensure that you have not used a save editor before the error started happening. If you have used a save editor, the edits are broken and you will need to restore a backed-up save, or wipe the save and start over if you have no backup.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]] and trying to recreate the error without the SD card inserted.<br>If the error stops after the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>loader</h5>

* <h6>undefined instruction</h6>
** The app most recently opened has an issue. If the value of R0 starts with C or D, it is an error code, and has a chance of being an error code if the value starts with E or F. Here are some common values for R0:
*** <code>D9004587</code>: When trying to open a game: The game is corrupted, or its seed is not imported.
**** See: [[3DS:Fixing corrupted games]]
*** <code>C8804478</code>: If trying to open the Homebrew Launcher: <code>boot.3dsx</code> is missing from the root of your SD card.
**** To fix: Download the latest Homebrew Launcher from [https://github.com/devkitPro/3ds-hbmenu/releases/latest here]
*** <code>D96077FA</code>/<code>FFFFFFFF</code>: The <code>.3dsx</code> that Luma3DS tried to load is corrupted.
**** To fix, redownload the app you are trying to launch. If this happens when you try to open the Homebrew Launcher itself, see the error above.
*** Most of the other possible error codes that can appear here are listed on [[3DS:Error_screens/Luma3DS_ErrDisp|the ErrDisp page]].
* <h6>prefetch abort (svcBreak)</h6>
**The code or sysmodule patch Luma3DS tried to load is invalid or corrupt.
***To fix: Redownload any recently installed patches (eg. Nimbus (Pretendo), Wumiibo, or anything else that goes in <code>/luma/titles</code> or <code>/luma/sysmodules</code>.) Alternatively, you may disable <code>loading external FIRMs and modules</code> as well as <code>Enable game patching</code> in the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]].

<h5>mset</h5>
* '''If not caused in Nintendo DS Profile:''' System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.
* '''If caused in Nintendo DS Profile:''' Your NVRAM is either corrupted or damaged in hardware. Run [[3DS:ctrcheck|ctrcheck]] - if its results do not include <code>Critical: NVRAM is inaccessible</code>, then follow [[3DS:NVRAM|the Fix NVRAM guide]].

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi with an external switch. New models must instead disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pxi</h5>
* Could be anything from a faulty cartridge to damaged internal components, but will almost always be some type of hardware issue.

<h5>pm</h5>
* The software you have launched may be missing required files. If the value in R0 is <code>E0E01BF5</code>, this is extremely likely to be the cause.

<h5>qtm/cam</h5>
* The camera's hardware is damaged or dead.
** To fix, replace the camera with a new one. To avoid the error until then, disconnect the camera or avoid using anything that activates the camera.

<h5>swkbd</h5>
* The software keyboard is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.
[[Category:Unbricking]]
[[Category:Nintendo 3DS troubleshooting]]
{{Short description|Guide to the CFW error handler}}

Formatting an SD card/Mac

2025-03-17T02:32:17Z

StarlitSkies: note not to restore SD contents if this is in the middle of another guide

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<br>{{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)" (or "MS-DOS (FAT32)" if it appears)</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<br>{{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 unless you were linked to this by another guide that needs the SD to be formatted and blank</li>
</ol>

</tabber>

{{hg imported|Guide_3DS}}

[[Category:General guides]]

Formatting an SD card/Linux

2025-03-17T02:32:16Z

StarlitSkies: note not to restore SD contents if this is in the middle of another guide, and standardize wording for that step

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=

<span>
# 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 29.7G 0 disk
└─mmcblk0p1 179:1 0 29.5G 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>mmcblk0</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
# Type <code>sudo umount /dev/<device name>*</code> (do not replace the <code>*</code>)
# 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>o</code>, this will create a new MBR partition scheme
# Enter <code>n</code>, then press enter until you're returned to the prompt
#* The default values will work fine for all consoles
# Enter <code>t</code>, 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: {{#tag:syntaxhighlight|
Disk /dev/mmcblk0: 29.72 GiB, 31914983424 bytes, 62333952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x########

Device Boot Start End Sectors Size Id Type
/dev/<partition name> 8192 62333951 62325760 29.7G c W95 FAT32 (LBA)
|lang=text}}
# If there are no issues, enter <code>w</code> - this will save changes and exit the fdisk prompt
# Type <code>sudo mkfs.vfat /dev/<partition name> -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, unless you were linked to this by another guide that needs the SD to be formatted and blank
</span>

|-|parted=

<span>
# 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 29.7G 0 disk
└─mmcblk0p1 179:1 0 29.5G 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>mmcblk0</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 mkfs.vfat /dev/<partition name> -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, unless you were linked to this by another guide that needs the SD to be formatted and blank
</span>

|-|KDE Partition Manager=

<span>
# Make sure your SD card is '''not''' inserted
# Open KDE Partition Manager, inputting your password as needed
# Insert your SD card and click <code>Refresh Devices</code>. The new device that shows up in the left pane is your SD card
# Click your SD card, then click the <code>New Partition Table</code> button at the top of the window
# When asked, choose <code>Ms-Dos</code>. Do '''NOT''' use <code>GPT</code>
#* [[File:KDE Partition Manager - MBR.png]]
# Right click the <code>unallocated</code> space in the right pane and select <code>New</code>
# When selecting your filesystem, choose <code>FAT32</code> from the drop-down menu. The window should look like this:
#* [[File:KDE Partition Manager - New Partition.png]]
# Click <code>OK</code>, then click <code>Apply</code>, then <code>Apply Pending Operations</code>
# Eject and reinsert your SD card
# If the SD card had any files and folders on it before the format, copy everything back from your computer, unless you were linked to this by another guide that needs the SD to be formatted and blank
</tabber>
{{hg imported|Guide_3DS}}

[[Category:General guides]]

Formatting an SD card/Windows

2025-03-17T02:32:14Z

StarlitSkies: note not to restore SD contents if this is in the middle of another guide

<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 (note that if GUIFormat reverts to 32768, this does not mean it selected the wrong cluster size!)</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, unless you were linked to this by another guide that needs the SD to be formatted and blank</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]]

Checking SD card integrity/Mac/legacy

2025-03-15T17:43:20Z

StarlitSkies: move backup and format of the SD card to the actual instructions

This is an add-on section for checking your SD card for errors using F3X.

Depending on the size of your SD card and the speed of your computer, this process can take up to several hours!

This page is for Mac users who are using '''macOS Sierra (10.12) and earlier'''. If you are not on macOS, check out the [[Checking SD card integrity/Windows|Windows]] or [[Checking SD card integrity/Linux|Linux]].

{{info|text=If you're using a Mac on macOS 10.13 (High Sierra) and above, follow [[Checking SD card integrity/Mac|this page]] instead.}}

== What You Need ==
* The latest version of {{GitHub|insidegui/F3X/releases/latest|F3X}} (the <code>.zip</code> file)

== Instructions ==
# Insert your SD card into your computer
# Create a new folder on your desktop, which will be referred to as the backup folder from now on
# Copy everything from your SD card to the backup folder
# [[Formatting_an_SD_card/Mac|Format the SD card]]
# Unzip the F3X <code>.zip</code> file
# Insert your SD card into your computer
# Run the F3X app
# Select your SD card
# Press "Start Test"
# Wait until the process is complete

{{success|text=If the test shows the result <code>Success! Your card is ok!</code>, your SD card is likely good. You can delete all <code>.h2w</code> files on your SD card and then copy the contents of the backup folder back to it.}}

{{critical|text=If the test shows any other results, your SD card is failing. You will have to replace it!}}

[[Category:General guides]]

Checking SD card integrity/Mac

2025-03-15T17:43:19Z

StarlitSkies: move backup and format of the SD card to the actual instructions

This is an add-on section for checking your SD card for errors using F3XSwift.

Depending on the size of your SD card and the speed of your computer, this process can take up to several hours!

This page is for Mac users only. If you are not on macOS, check out the [[Checking SD card integrity/Windows|Windows]] or [[Checking SD card integrity/Linux|Linux]] pages.

{{info|text=F3XSwift is only compatible with macOS 10.13 (High Sierra) and above. If you have an older version of macOS, follow [[Checking SD card integrity/Mac/legacy|this page]] instead.}}

== What You Need ==
* The latest version of {{GitHub|vrunkel/F3XSwift/releases/latest|F3XSwift}} (the <code>.app.zip</code> file)

== Instructions ==
# Insert your SD card into your computer
# Create a new folder on your desktop, which will be referred to as the backup folder from now on
# Copy everything from your SD card to the backup folder
# [[Formatting_an_SD_card/Mac|Format the SD card]]
# Run the F3XSwift app
# Select your SD card from the list of volumes
# Click "Test"
# Click "Open" to confirm writing to your SD card
# Wait until the process is complete

{{success|text=If the test shows the result <code>Success! Your card is ok!</code>, your SD card is likely good. You can delete all <code>.h2w</code> files on your SD card and then copy the contents of the backup folder back to it.}

{{critical|text=If the test shows any other results, your SD card is failing. You will have to replace it!}}

[[Category:General guides]]

Checking SD card integrity/Linux

2025-03-15T17:43:19Z

StarlitSkies: move backup and format of the SD card to the actual instructions

This is an add-on section for checking your SD card for errors using F3.

Depending on the size of your SD card and the speed of your computer, this process can take up to several hours!

This page is for Linux users only. If you are not on Linux, check out the [[Checking SD card integrity/Windows|Windows]] or [[Checking SD card integrity/Mac|Mac]] pages.

== What You Need ==
* The latest version of {{GitHub|AltraMayor/f3/releases/tag/v8.0|F3}} (the <code>.zip</code> file)

== Instructions ==
# Insert your SD card into your computer
# Mount your SD card
# Create a new folder on your desktop, which will be referred to as the backup folder from now on
# Copy everything from your SD card to the backup folder
# [[Formatting_an_SD_card/Linux|Format the SD card]]
# Extract the F3 <code>.zip</code> file
# Open a terminal window and <code>cd</code> into the F3 directory
# Run <code>make</code> to compile F3
# Run <code>./f3write <your SD card mount point></code>
# Wait until the process is complete. See below for an example output.
$ ./f3write /media/michel/6135-3363/
Free space: 29.71 GB
Creating file 1.h2w ... OK!
...
Creating file 30.h2w ... OK!
Free space: 0.00 Byte
Average Writing speed: 4.90 MB/s
# Run <code>./f3read <your SD card mount point></code>
# Wait until the process is complete. See below for an example output.
$ ./f3read /media/michel/6135-3363/
SECTORS ok/corrupted/changed/overwritten
Validating file 1.h2w ... 2097152/ 0/ 0/ 0
...
Validating file 30.h2w ... 1491904/ 0/ 0/ 0
...
Data OK: 29.71 GB (62309312 sectors)
Data LOST: 0.00 Byte (0 sectors)
Corrupted: 0.00 Byte (0 sectors)
Slightly changed: 0.00 Byte (0 sectors)
Overwritten: 0.00 Byte (0 sectors)
Average Reading speed: 9.42 MB/s

{{success|text=If the test shows the result <code>Data LOST: 0.00 Byte (0 sectors)</code>, your SD card is likely good. You can delete all <code>.h2w</code> files on your SD card and then copy the contents of the backup folder back to it.}}

{{critical|text=If the test shows any other results, your SD card is failing. You will have to replace it!}}

[[Category:General guides]]

Checking SD card integrity/Windows

2025-03-15T17:43:18Z

StarlitSkies: move backup and format of the SD card to the actual instructions

This is an add-on section for checking your SD card for errors using h2testw.

Depending on the size of your SD card and the speed of your computer, this process can take up to several hours!

This page is for Windows users only. If you are not on Windows, check out the [[Checking SD card integrity/Linux|Linux]] or [[Checking SD card integrity/Mac|Mac]] pages.

== What You Need ==
* The latest version of [https://www.heise.de/ct/Redaktion/bo/downloads/h2testw_1.4.zip h2testw] (direct download)

== Instructions ==
# Insert your SD card into your computer
# Create a new folder on your desktop, which will be referred to as the backup folder from now on
# Copy everything from your SD card to the backup folder
# [[Formatting_an_SD_card/Windows|Format the SD card]]
# Copy <code>h2testw.exe</code> from the h2testw <code>.zip</code> to your desktop
# Run <code>h2testw.exe</code>
# Select "English"
# Click "Select target"
# Select your SD card's drive letter
# Ensure "all available space" is selected
# Click "Write + Verify"
# Wait until the process is completed

{{success|text=If the test shows the result <code>Test finished without errors</code>, your SD card is likely good. You can delete all <code>.h2w</code> files on your SD card and then copy the contents of the backup folder back to it.}}

{{critical|text=If the test shows any other results, your SD card is failing. You will have to replace it!}}

[[Category:General guides]]

3DS:History of 3DS Hacking

2025-03-14T20:07:36Z

StarlitSkies: give far more specific (and more correct) details on exploits mentioned, portray the rxTools dispute correctly, and add several more exploits to the timeline

{{#approvable_by: users = Wariohax}}
<references />Heavy adaption of zoogie's "A Pretty Brief History of the 3ds Hacking/Homebrew Scene" from the "3DS hacking scene history" section on GBAtemp.
== 2011 ==

=== March ===
The official release of the Nintendo 3DS in the west, and the creation of the wiki [[3dbrew:Main_Page|3dbrew]].

=== June ===
The first 3DS roms are dumped.

=== September ===
Crown3DS gives a teaser implying the creation of a flashcart, but instead released a website written in broken English promising the community that they are progressing.

=== December ===
The first release of tools that convert video to the type of stereographic 3D video compatible with the Nintendo 3DS Camera.

== 2012 ==

=== Unknown Month ===
It is believed that Neimod's hardware RAM dumps and internal research led to the first userland and a9 exploits.<ref>https://gbatemp.net/threads/3ds-hacking-scene-history.443396/</ref>

=== March ===
The first (?) homebrew app is written in .cxi format, "Hello World", is written by Xcution (author of CiTRUS, a tool that allows BaNneR and ICoN files to be made using the .xbsf format)

== 2013 ==

=== August ===
The flashcart [[Gateway-3DS]] is first released, and serves as the sole option for homebrew in the 3DS' early years. At this time, there was basic arm9 homebrew possible via an [https://www.3dbrew.org/wiki/System_Settings MSET] exploit combined with [https://github.com/naehrwert/p3ds/tree/df8f52a8c22b7f4758e1a47b2ca712d12be60bc6 p3ds] (python tools for the 3DS).

=== December ===
Users in the community figure out how to reverse engineer [[Gateway-3DS]]' payload to create their own NAND emulation (or redirection). This leads to the users Smealum and Yellows8 creating a private payload called RedNAND.

== 2014 ==

=== January ===
brickgate/brickway - A scandal where Gateway released a FIRM that intentionally bricks consoles using Gateway3DS flashcart clones (such as R4 and Orange3DS). On top of this, its code was written badly enough that it triggered on many legitimate Gateway3DS cartridges, bricking completely 'innocent' users in the crossfire.

=== March ===
The first commit of [https://citra-emulator.com/ Citra], the first major 3DS emulator, is released.

=== August ===
The secondary userland exploit {{GitHub|yellows8/oot3dhax|oot3dhax}} is first released by yellows8.

=== November ===
[https://www.gamebrew.org/wiki/Palantine_CFW_3DS Palantine] (a CFW made by Yellows8 and other) is leaked, bringing a closed-source custom firmware to the public. However, it had limitations such as the EmuNAND not being updateable, having a low boot rate, and being difficult to install, among others. The thing it did best, running CIAs, would be taken and added to Gateway3DS shortly after.

The flashcart [[Sky3DS]] is first released. It could play pirated roms on entirely stock consoles, but couldn't run homebrew and had a very high ban risk due to the way it worked. This ban risk was unfixable until full custom firmware was released, and by that point it became obsolete anyway.

The primary userland exploit{{GitHub|smealum/ninjhax|ninjhax}} is first released by smealum.

== 2015 ==

=== January ===
Gateway cracks firmware version 9.2 and updates their flashcarts to OMEGA. The user yifanlu makes a blog post about reverse engineering the memchunkhax/firmlaunchhax combo used by Gateway, and teams such SALT, roxas75, and patois implement their own versions of it shortly after.

=== February ===
The custom firmware {{GitHub|roxas75/rxTools|rxTools}} is first released by roxas75, notable for being purely focused on utilitarian homebrew and trying to avoid piracy entirely to avoid all potential legal issues.

=== May ===
The custom firmware PastaCFW is first released. It is named after a leak of sigpatches on pastebin, which was combined with patois' Brahma (an open source memchunkhax/firmlaunchhax) to make the first open source custom firmware. Its only major caveat was that it had no emuNAND support.

A fork of rxTools with PastaCFW's sigpatches is released by ahp_person (appletinivi), causing roxas75 to openly dispute him in an attempt to stop piracy from becoming a legal issue for the wider homebrew community.

=== June ===
Once popular demand turns against him, roxas75 eventually gives in, releasing the rxTools source and officially adding sigpatches. He then, understandably, quits the homebrew scene immediately afterward and does not ever return.

=== July ===
The primary userland exploit Ninjhax2x is first released.

=== August ===
The exploits Tubehax and Ironhax are first released.
* Tubehax is a primary userland exploit that took advantage of the 3DS YouTube app, but was unfortunately patched only a couple months later on all versions.
* Ironhax is the first secondary (userland) exploit, meaning it requires extra leverage to work (usually from a primary exploit such as Tubehax).

ReiNand, the first fully-featured custom firmware to support the New 3DS, is released.

=== September ===
The exploits Menuhax and Browserhax are first released.
* Menuhax is a secondary userland exploit targeting the Home Menu. After the one use of a primary exploit needed to install it, it gives fully untethered coldboot userland access by exploiting the Home Menu automatically as it loads.
* Browserhax is a term for a series of primary userland exploits using the internet browsers for the n3DS and o3DS, which would become mainstays of the scene for a few more years before Nintendo finally killed off the potential for any new Browserhax.

=== December ===
An upgrade to Sky3DS, Sky3DS+, is released. Among others, its new features included bypassing cart-based AP in recent games and having a second button for more ease of selecting games.

The CCC hosts [https://gbatemp.net/threads/32c3-console-hacking-3ds-talk-dec-27-smea-derrek-plutoo.405640/ 32c3] in Hamburg, Germany. During 32c3, [https://smealum.github.io/3ds/32c3/ smealum gives a talk] where snshax, [[arm9loaderhax]], memchunkhax2, and ntrcardhax are revealed, & menuhax and ironhax receive updates to continue functioning.
* snshax and ntrcardhax would ultimately be of little interest, thanks to snshax being n3DS-only and ntrcardhax requiring an extremely specific type of modified flashcart that effectively didn't exist.
* memchunkhax2 is a privilege escalation k11 exploit that, although not immediately useful, would quickly become the foundation of downgrading as part of other exploit chains.
* Arm9loaderhax is an untethered coldboot custom firmware loader that is installed directly to the FIRM partitions. Although it was somewhat unsafe and risky to install through its entire lifetime, it was still a massive step forward for the homebrew community by allowing homebrew tools even larger amounts of control over the system.

== 2016 ==

=== January ===
An exploit chain using memchunkhax2 is introduced, the first implementation of downgrading from 10.x firmwares to 9.2 for certain other exploits.

Downgrading would soon after be patched by version 10.4.

=== February ===
[[arm9loaderhax]] is fully released, and becomes a mainstay of the scene.

The primary userland exploit ctr-httpwn is first released by yellows8.

A complex dispute between the original author of ReiNand (Reisyukaku) and the rest of its developer team hits its first overt boiling point, causing them to cut ties as much as possible and officially fork the project into AuReiNand.

=== March ===
The privilege escalation k11 exploit memchunkhax2.1 is first released by Aliaspider, which allowed 9.2 downgrades to resume until version 10.7 patched it a second time.

=== April ===
AuReiNand is renamed to Luma3DS, and work begins towards rewriting every line of code. Once this is done, they detach it from ReiNand's fork network on GitHub, which marks the point where it is converted into an entirely original project.

The tool {{GitHub|dazjo/salt_sploit_installer|salt_sploit_installer}} is first released, being unique because it sets the stage for three secondary userland exploits very shortly afterward.
Just a few days later, two of those three - {{GitHub|shinyquagsire23/v_hax|(v*)hax}} and {{GitHub|shinyquagsire23/supermysterychunkhax|supermysterychunkhax}} - are both first released by shinyquagsire23.

=== May ===
The third secondary userland exploit to use salt_sploit_installer, {{GitHub|dazjo/humblehax|humblehax}}, is first released by dazjo. This one is especially notable because it required purchasing a limited-time game from Humble Bundle, a quirk not seen in any exploit before or since.

=== June ===
The secondary userland exploit {{GitHub|MrNbaYoh/basehaxx|basehaxx}} is first released by MrNbaYoh.

=== July ===
A user reveals a DSiWare-based firm downgrade method after several months' worth of teasers. The release of this allowed 9.2 downgrades to continue on versions 11.0 - 11.2, before being patched a third time.

=== September ===
Arm9loaderhax gains two new tools that make its installation even easier: CTRNand Transfer (shortening the install time of both new and old 3DS) and OTPless (an instant N3DS install method). CTRNand Transfer would be kept and see far more use later, but OTPless was later removed from use due to having a small but completely random chance to brick.

=== December ===
The CCC hosts [https://gbatemp.net/threads/33c3-console-hacking-2016-3ds-wiiu-talk-dec-27-30-smea-derrek-nedwill-naehrwert.450043/ 33c3] in Hamburg, Germany. During 33c3, [https://derrekr.github.io/3ds/33c3/ derrekr gives a talk] where soundhax, fasthax, and sighax are revealed.
* Soundhax is a primary userland exploit targeting Nintendo 3DS Sound that was made by nedwill. Because it was free (unlike ninjhax, which required Cubic Ninja, a paid game), almost all consoles at the time were vulnerable to this exploit.
* Fasthax is another privilege escalation k11 exploit, also made by nedwill.
* [https://zoogie.github.io/sh/ Sighax] is a complex exploit of a vulnerability in the bootrom revealed by derrekr; when used properly, it allows anyone to sign arbitrary firmware code without restrictions. derrekr also revealed vague details about how he dumped the 3DS ARM9/ARM11 bootroms, though gave no detail about the exact code.<ref>https://wololo.net/2016/12/28/33c3-3ds-bootrom-cracked-sign-firmwares/</ref>

Nintendo launches a bug bounty program for the 3DS on HackerOne, with bounties from $100 - $20,000 per exploit. This caused exploit developers to start moving away from public releases.
== 2017 ==

=== January ===
The privilege escalation k9 exploit chain safehax is first released by the user appleTinivi, after an anonymous user posted the method on 3dbrew. Through the use of this exploit chain (usable on all versions up to 11.2), the process for installing a9lh was significantly streamlined: specifically, it shortens the list of needed steps to directly downgrading to 2.1, using exploits on 2.1 to get a copy of otp.bin, restoring the original NAND, and installing a9lh using the otp.

=== February ===
safehax and fasthax are patched by the release of version 11.3, also temporarily patching firm downgrading via DSiWare and hardmodding again in the process.

=== April ===
A previously-unknown privilege escalation k11 exploit, udsploit is first released by Smealum just as it's patched by the release of version 11.4. However, it remains useful for those who stayed on version 11.3.

Safehax is updated to work on 11.3 by AppleTinivi due to an oversight in Nintendo's previous patch for safehax.

=== May ===
SciresM creates and gives an unofficial sequel to 33c3, 33.5c3. [https://sciresm.github.io/33-and-a-half-c3/ During this talk], [[boot9strap]] and the concepts that would later allow [[ntrboot]] are revealed.
* Boot9strap is effectively the successor to arm9loaderhax, being another coldboot firmware loader that works in a much cleaner way by implementing a FIRM sighax signature. Because of how it works, it carries near-zero brick risk and gains control early enough to keep access to the bootroms and decrypted OTP, allowing it to dump them in software.
* Ntrboot allows for any correctly signed firm to be booted from a DS cartridge when the correct keycombo is held down, which also skips the entire normal boot process. This allows it to serve both as an instant custom firmware installation method and an extremely potent unbricking tool.

Since legitimate firms can now be created with nothing more than NAND access, DSiWare and hardmod-based downgrades resume on the latest firmware by using the known plaintext attack.

=== June ===
The n2DSXL is released in Australia, and it is quickly discovered that it happens to have the same vulnerable bootroms as the old 3DS models did.

=== August ===
The first practical implementation of [[Ntrboot]] is released, starting only with support for ak2i and R4 flashcards but quickly growing to others.

=== September ===
The Gateway team reveals they have been working on a new flashcard called [[Stargate]], a 3-in-1 hybrid of an ntrboot card, DS flashcart, and [[Sky3DS]]. It was abandoned after a few months due to people seeking out cheaper options for ntrboot cards.

== 2018 ==

=== January ===
A user reveals a method to brute-force the movable.sed using only the LocalFriendCodeSeed (which is obtainable in userland). This entrypoint, called [[3DS:Seedminer|Seedminer]], allowed users to inject hacked DSiWare and install [[boot9strap]] with only one 3DS.

=== July ===
Nintendo releases version 11.8.

=== August ===
Smealum reveals an arm9 exploit chain that he had been teasing at defcon, but it had already been patched in version 11.8 because he disclosed it to the HackerOne bug bounty program earlier on. As part of the reveal, he posted the incomplete repos on Github, but nobody to date has been able to make the exploit work.

=== September ===
The primary *miner exploit Frogminer is first released. This variant of the *miner exploit path utilizes an old version of the Japanese Flipnote Studio injected into DS Download Play instead of using Sudoku, meaning unlike its predecessor, it is a completely free *miner exploit.

=== December ===
Nintendo releases version 11.9, patching an unreleased browser exploit for both the O3DS and N3DS thanks to another HackerOne bounty submission by the userland exploit developer MrNbaYoh.

== 2019 ==

=== July ===
The primary userland exploit BannerBomb3, which targeted System Settings and mostly used the *miner series to complete the exploit chain, is first released.

=== December ===
The CCC hosts [https://gbatemp.net/threads/36c3-hacker-conference-underway-27th-to-30th-of-december-2019.555023/ 36c3] in Leipzig, Germany. During 36c3, [https://mrnbayoh.github.io/36c3/ MrNbaYoh gives a talk] that demonstrates a new primary exploit chain: using StreetPass tags, someone could remotely takeover a 3DS in userland and install custom firmware, with zero user interaction required. This would set up further exploits developed by TuxSH and Lazypixie which would take over the ARM11 kernel, and later on Safehax 2.x to also take over ARM9. However, due to its potential for malicious use (i.e. remotely bricking consoles), this exploit chain was submitted to HackerOne sometime earlier and patched in version 11.12, two months before 36c3 started.

== 2020 ==

=== April ===
The privilege escalation k9 exploit chain unSAFE_MODE, a revised version of safehax for version 11.13, is first released. Notably, this exploit chain would never be directly patched, but would be made unusuable when universal_otherapp is patched.

=== July ===
Nintendo's HackerOne bounty program [https://hackerone.com/nintendo/updates?type=team is closed on July 15th.]

=== August ===
The primary userland exploit new-browserhax, which is the simplest and most potent browserhax yet, is first released for both the n3DS and o3DS by zoogie. This begins a temporary 'golden age' where installing CFW is the easiest it ever has been, or will be (as of 2025-03-13).

=== September ===
Nintendo shuts down retail production of all 3DS models.

=== October ===
The secondary exploit menuhax67, the successor to Yellows8's menuhax, is first released by zoogie. This version of the exploit still requires initial userland access, but has even more privileges and is simpler to activate than the original. (And it's a great meme)

=== November ===
Nintendo releases version 11.14.0-46, patching a few last-minute submissions of exploits from the HackerOne bounty. This includes zoogie's new-browserhax, which ends the 'golden age' temporarily and changes the main userland entry point to back to Seedminer.

=== December ===
After the one month cooldown between each submission of bugs to HackerOne, MrNbaYoh and TuxSH disclose the entrypoint SSLoth and an exploit for it, safecerthax. Together, they create a full chain to boot9strap on o3DS models (and this chain still works on certain older versions, though it requires access to [[3DS:Safe Mode|Safe Mode]]).

TuxSH updates universal-otherapp to include a new exploit chain (based on smpwn, spipwn, khax and agbhax) that works on NATIVE_FIRM.

The primary userland exploit new-browserhax-xl is released by zoogie, resuming the 'golden age' of easy CFW installs.

== 2021 ==

=== January ===
Nintendo ends Unity3DS and many debugging/dev hardware items in one fell swoop.

=== April ===
The privilege escalation userland exploit chain nimhax, an expansion of ctr-httpwn that simultaneously takes over the nim sysmodule, is first released by luigoalma.

The primary userland exploit old-browserhax-xl is first released by zoogie, complementing new-browserhax-xl so that all consoles have a browser exploit available again.

The semi-primary userland exploit [[3DS:Kartdlphax|kartdlphax]], an exploit for Mario Kart 7 that requires a second modded console, is first released by PabloMK7 (creator of CTGP-7).

=== July ===
Nintendo releases version 11.15, which patches both browserhax-xl exploits, ending the 'golden age' for good in the process. It also patches SSLoth (which leaves safecerthax unpatched but unusuable), and as such Seedminer becomes the main exploit again.

== 2022 ==

=== August ===
Nintendo releases version 11.16, breaking TuxSH's universal-otherapp combo by patching smpwn.

Nintendo also lays the foundation for the eShop closure by updating MINT/ESHOP to handle shutting down eShop payments. Just two weeks later, they would update the NVER on this title due to a typo in the web data module.

=== December ===
The entrypoint ENLBufferPwn, an online RCE for Mario Kart 7, is disclosed by PabloMK7 after it was already patched in version 1.2 of the game. Although it had potential for custom firmware, PabloMK7 disclosed it because it could be used to remotely load universal-otherapp over the network; doing so would create a k9 exploit chain that also had potential for mass bricks, online cheats, remote installation of malware, or practically anything else (though with size constraints). By the time of disclosure, it was already being used in the wild to reset VR scores and interfere with races, making this claim of threat even more credible.

== 2023 ==

=== March ===
The primary userland exploit super-skaterhax, another n3DS-only browser exploit, is first released.

Nintendo closes the eShop on the 27th, restricting all exploits that relied on free games and DSiWare to people who had bought them before its close. These exploits were removed from the guide's main paths shortly after.

=== May ===
Nintendo releases version 11.17, patching BannerBomb3 and leaving the o3DS with no free softmod method for the first time in a while.

=== July ===
The privilege escalation "k11" exploit chain nimdsphax, an expansion of nimhax that also takes over the dsp sysmodule, is first released by TuxSH and luigoalma. It is notable in that it does not directly exploit k11, but instead disables GPU_PROT and then uses the GPU to directly overwrite k11 code.

The secondary exploit Kartminer7, a secondary *miner exploit also requiring a copy of Mario Kart 7 (can be either physical or digital), is first released by zoogie.

=== October ===
The primary k9 exploit MSET9, which targets System Settings and has no extra requirements, is first released by zoogie. This restores free softmod access for the o3DS, but also works consistently on the n3DS as well and is generally an extremely stable exploit.

=== December ===
Zoogie(?) calls it quits and is looking forward to future challenges whilst appreciating the time "he had helping people unlock their 3DSs!" -zoogie

3DS:History of 3DS Hacking

2025-03-14T00:55:02Z

StarlitSkies: deduplicate the first couple lines

{{#approvable_by: users = Wariohax}}
<references />Heavy adaption of zoogie's "A Pretty Brief History of the 3ds Hacking/Homebrew Scene" from the "3DS hacking scene history" section on GBAtemp.
== 2011 ==

=== March ===
The official release of the Nintendo 3DS in the west, and the creation of the wiki [[3dbrew:Main_Page|3dbrew]].

=== June ===
The first 3DS roms are dumped.

=== September ===
Crown3DS gives a teaser implying the creation of a flashcart, but instead released an Engrish website promising the community that they are progressing.

=== December ===
The first release of tools that convert video to the type of stereographic 3D video compatible with the Nintendo 3DS Camera.

== 2012 ==

=== Unknown Month ===
It is believed that Neimod's hardware RAM dumps and internal research led to the first userland and a9 exploits.<ref>https://gbatemp.net/threads/3ds-hacking-scene-history.443396/</ref>

=== March ===
The first (?) homebrew app is written in .cxi format, "Hello World", is written by Xcution (author of CiTRUS, a tool that allows BaNneR and ICoN files to be made using the .xbsf format)

== 2013 ==

=== August ===
[[Gateway-3DS]] is first released, and serves as the sole option for homebrew in the 3DS' early years. At this time, there was basic arm9 homebrew possible via an [https://www.3dbrew.org/wiki/System_Settings MSET] exploit combined with [https://github.com/naehrwert/p3ds/tree/df8f52a8c22b7f4758e1a47b2ca712d12be60bc6 p3ds] (python tools for the 3DS).

=== December ===
Users in the community figure out how to reverse engineer [[Gateway-3DS]]' payload to create their own NAND emulation (or redirection). This leads to the users Smealum and Yellows8 creating a private payload called RedNAND.

== 2014 ==

=== January ===
brickgate/brickway - A scandal where Gateway released a FIRM that intentionally bricks consoles using Gateway3DS flashcart clones (such as R4 and Orange3DS). On top of this, its code was written badly enough that it triggered on many legitimate Gateway3DS cartridges, bricking completely 'innocent' users in the crossfire.

=== March ===
The first commit of [https://citra-emulator.com/ Citra], the first major 3DS emulator, is released.

=== November ===
[https://www.gamebrew.org/wiki/Palantine_CFW_3DS Palantine] (a CFW made by Yellows8 and other) is leaked, bringing a closed-source custom firmware to the public. However, it had limitations such as the EmuNAND not being updateable, having a low boot rate, and being difficult to install, among others. The thing it did best, running CIAs, would be taken and added to Gateway3DS shortly after.

The flashcart [[Sky3DS]] is released. It could play pirated roms on entirely stock consoles, but couldn't run homebrew and had a very high ban risk due to the way it worked.

The userland exploit [https://gbatemp.net/threads/introducing-ninjhax-a-nintendo-3ds-homebrew-exploit.374233/ ninjhax] is officially released.

== 2015 ==

=== January ===
Gateway cracks 9.2 and updates their flashcards to OMEGA. The user yifanlu makes a blog post about reverse engineering the memchunkhax/firmlaunchhax combo used by Gateway, and teams such SALT, roxas75, and patois implement their own versions of it shortly after.

=== February ===
[https://gbatemp.net/threads/release-rxtools-roxas75-3ds-toolkit-fw-2-0-9-2.382782/ rxTools] is first released by roxas75.

=== May ===
PastaCFW (named after a leak of sigpatches on pastebin) is first released. It combined the works of patois' Brahma (an open source memchunkhax/firmlaunchhax) to make the first open source custom firmware, though with no emuNAND support.

A fork of rxTools with sigpatches is released by ahp_person (appletinivi), and roxas75 attempts to stop the patches from becoming widespread out of concerns over piracy.

=== June ===
roxas75 eventually gives in due to popular demand, releasing the rxTools source and adding sigpatches in officially, then quits the homebrew scene immediately afterward.

=== July ===
The exploit Ninjhax2x is first released.

=== August ===
The exploits Tubehax and Ironhax are first released.
* Tubehax was a primary userland exploit that took advantage of the 3DS YouTube app, but was unfortunately patched only a couple months later on all firmware.
* Ironhax was the first secondary userland exploit, meaning it requires extra leverage to work (usually from a primary exploit such as Tubehax).

ReiNand, the first fully-featured custom firmware to support the New 3DS, is released.

=== September ===
The exploits Menuhax and Browserhax are first released.
* Menuhax is a secondary exploit of the Home Menu that allows userland control to be gained immediately on boot.
* Browserhax is a term for a series of primary exploits using the internet browsers for the n3DS and o3DS, which would become mainstays of the scene for a few more years before Nintendo finally killed off the potential for any new Browserhax.

=== December ===
An upgrade to Sky3DS, Sky3DS+, is released. Among others, its new features included bypassing cart-based AP in recent games and adding a filesystem-based game loading feature.

The CCC hosts [https://gbatemp.net/threads/32c3-console-hacking-3ds-talk-dec-27-smea-derrek-plutoo.405640/ 32c3] in Hamburg, Germany. During 32c3, [https://smealum.github.io/3ds/32c3/ smealum gives a talk] where snshax, [[arm9loaderhax]], memchunkhax2, and ntrcardhax are revealed, & menuhax and ironhax receive updates to continue functioning.
* snshax, menuchunkhax2, and ntrcardhax would ultimately be of little interest.
* Arm9loaderhax was the first custom bootloader (and thus also the first coldboot custom firmware) for the 3DS, and although it was somewhat unsafe and risky to install, it was still a massive step forward for the homebrew community.

== 2016 ==

=== January ===
Downgrading is first introduced, allowing 10.x firmwares to revert to 9.2 for certain exploits.

Downgrading would soon after be patched by version 10.4.

=== February ===
[[arm9loaderhax]] is fully released, and becomes a mainstay of the scene.

AuReiNand, a fork of ReiNAND, is released after a disagreement with ReiNand's original author (Reisukaku) caused the rest of the developer team to cut ties. Soon after, it would be renamed to Luma3DS and lose its official status as a fork to help distance itself even further.

=== March ===
The exploit memchunkhax2.1 is released by Aliaspider, which allowed 9.2 downgrades to resume until version 10.7 patched it a second time.

=== May ===
R11

=== July ===
A user reveals a DSiWare-based firm downgrade method after several months' worth of teasers. The release of this allowed 9.2 downgrades to continue on versions 11.0 - 11.2, before being patched a third time.

=== September ===
Arm9loaderhax gains two new tools that make its installation even easier: CTRNand Transfer (shortening the install time of both new and old 3DS) and OTPless (instant N3DS install). CTRNand Transfer would survive to see far more use, but OTPless was later removed from use due to having a small but completely random chance to brick.

=== December ===
The CCC hosts [https://gbatemp.net/threads/33c3-console-hacking-2016-3ds-wiiu-talk-dec-27-30-smea-derrek-nedwill-naehrwert.450043/ 33c3] in Hamburg, Germany. During 33c3, [https://derrekr.github.io/3ds/33c3/ derrekr gives a talk] where soundhax, fasthax, and sighax are revealed.
* Soundhax is a free (as opposed to ninjhax, which required Cubic Ninja, a paid game) userland primary exploit for Nintendo 3DS Sound made by nedwill. Almost all consoles at the time were vulnerable to this exploit.
* Fasthax is another k11 (arm11 kernel) exploit, also made by nedwill.
* [https://zoogie.github.io/sh/ Sighax] is a complex exploit of a vulnerability in the bootrom revealed by derrekr; when used properly, it allows anyone to sign arbitrary firmware code without restrictions. derrekr also revealed vague details about how he dumped the 3DS ARM9/ARM11 bootroms, though gave no detail about the exact code.<ref>https://wololo.net/2016/12/28/33c3-3ds-bootrom-cracked-sign-firmwares/</ref>

Nintendo launches a bug bounty program for the 3DS, the bounties being $100 - $20,000 per exploit, this would have an affect of exploit developers moving away from public releases.

== 2017 ==

=== January ===
The arm9 exploit Safehax is released by the user appleTinivi after an anonymous user posted the method on 3dbrew. This exploit allows for full system control up to version 11.2, which significantly streamlined the process for installing a9lh; from this point on, it is reduced to directly downgrading to 2.1, using exploits on 2.1 to get a copy of otp.bin, and then restoring the original NAND and installing a9lh using their otp.

=== February ===
safehax and fasthax are patched by the release of version 11.3, also permanently patching firm downgrading with DSiWare and hardmodding in the process.

=== April ===
A previously-unknown k11 exploit, udsploit is first released by Smealum just as it's patched by the release of version 11.4.

Safehax is updated to work on 11.3 by AppleTinivi due to an oversight in Nintendo's previous patch for safehax.

=== May ===
SciresM creates and gives an unofficial sequel to 33c3, 33.5c3. [https://sciresm.github.io/33-and-a-half-c3/ During this talk], [[boot9strap]] and the concepts that would later allow [[ntrboot]] are revealed.
* Boot9strap is effectively the sequel to arm9loaderhax, being a much cleaner custom bootloader that implements a FIRM sighax signature. Because of how it works, it carries near-zero brick risk and gains control early enough to keep access to the bootroms and decrypted OTP, allowing it to dump them in software.
* Ntrboot allows for any correctly signed firm to be booted from a DS cartridge when the correct keycombo is held down, which also skips the entire normal boot process. This allows it to serve both as an instant custom firmware installation method and an extremely potent unbricking tool.

Since legitimate firms can now be created with nothing more than NAND access, DSiWare and hardmod-based downgrades resume on the latest firmware by using the known plaintext attack.

=== June ===
The n2DSXL is released in Australia, and it is quickly discovered that it happens to have the same vulnerable bootroms as the old 3DS models did.

=== August ===
[[Ntrboot]] is first released, starting only with support for ak2i and R4 flashcards but quickly growing to others.

=== September ===
The Gateway team reveals they have been working on a new flashcard called [[Stargate]], a supposed 3-in-1 hybrid of an ntrboot card, DS flashcart, and [[Sky3DS]]. It was abandoned after a few months due to people seeking out cheaper options for ntrboot cards.

== 2018 ==

=== January ===
A user reveals a method that brute-forces the movable.sed using only the LocalFriendCodeSeed (which is obtainable in userland). This method, called [[3DS:Seedminer|Seedminer]], allowed users to inject hacked DSiWare and install [[boot9strap]] with only one 3DS.

=== July ===
Nintendo releases version 11.8.

=== August ===
Smealum reveals an arm9 exploit chain that he had been teasing at defcon, but it had already been patched in version 11.8 because he disclosed it to the HackerOne bug bounty program earlier on. As part of the reveal, he posted the incomplete repos on Github, but nobody to date has been able to make the exploit work.

=== September ===
A new version of Seedminer called Frogminer is released. This variant of the exploit utilizes an old version of the Japanese Flipnote Studio injected into DS Download Play instead of using Sudoku, meaning unlike the original, it was a completely free miner exploit.

=== December ===
Nintendo releases version 11.9, patching an unreleased browser exploit for both the O3DS and N3DS thanks to another HackerOne bounty submission by the userland exploit developer MrNbaYoh.

== 2019 ==

=== July ===
The exploit BannerBomb3, a userland primary exploit for System Settings that mostly uses the miner series as its secondary exploits, is first released.

=== December ===
The CCC hosts [https://gbatemp.net/threads/36c3-hacker-conference-underway-27th-to-30th-of-december-2019.555023/ 36c3] in Leipzig, Germany. During 36c3, [https://mrnbayoh.github.io/36c3/ MrNbaYoh gives a talk] that demonstrates a new primary exploit chain: using StreetPass tags, someone could remotely takeover a 3DS in userland and install custom firmware, with zero user interaction required. This would set up further exploits developed by TuxSH and Lazypixie which would take over the ARM11 kernel, and later on Safehax 2.x to also take over ARM9. However, due to its potential for malicious use (i.e. remotely bricking consoles), this exploit chain was submitted to HackerOne sometime earlier and patched in version 11.12, two months before 36c3 started.

== 2020 ==

=== April ===
The exploit unSAFE_MODE, a new version of safehax for version 11.13, is first released.

=== July ===
Nintendo's HackerOne bounty program is closed on July 15th. [https://hackerone.com/nintendo/updates?type=team]

=== August ===
The exploit new-browserhax, the simplest and most potent browserhax yet, is released for both the n3DS and o3DS by zoogie. This begins a temporary 'golden age' where installing CFW is the easiest it ever has been, or will be (as of 2025-03-13).

=== September ===
Nintendo shuts down retail production of all 3DS models.

=== October ===
The exploit menuhax67, the successor to Yellows8's menuhax, is first released by zoogie. This version of the exploit is even simpler to activate than the original. (And it's a great meme)

=== November ===
Nintendo releases version 11.14.0-46, fixing a few last-minute submissions of exploits from the HackerOne bounty. This also fixes zoogie's new-browserhax, which ends the 'golden age' temporarily and changes the main userland entry point to back to Seedminer.

=== December ===
After the one month cooldown between each submission of bugs to HackerOne, MrNbaYoh and TuxSH disclose the exploits SSLoth and safecerthax. These two exploits, combined, created a full chain to boot9strap on o3DS models (and still do, when triggered through [[3DS:Safe Mode|Safe Mode]]).

TuxSH updates universal-otherapp to include a new exploit chain (based on smpwn, spipwn, khax and agbhax) that works on NATIVE_FIRM.

The exploit new-browserhax-xl is released by zoogie, resuming the 'golden age' of easy CFW installs.

== 2021 ==

=== January ===
Nintendo ends Unity3DS and many debugging/dev hardware items in one fell swoop.

=== April ===
The exploit old-browserhax-xl is first released by zoogie, complementing new-browserhax-xl so that all consoles have a browser exploit available again.

The exploit [[3DS:Kartdlphax|kartdlphax]], a semi-primary exploit for Mario Kart 7, is released by PabloMK7 (creator of CTGP-7).

=== July ===
Nintendo releases version 11.15, which patches SSLoth in Safe Mode and both browserhax-xl exploits, ending the 'golden age' for good. Seedminer takes its place again.

== 2022 ==

=== August ===
Nintendo releases version 11.16, breaking TuxSH's universal-otherapp combo by patching smpwn.

Nintendo also lays the foundation for the eShop closure by updating MINT/ESHOP to handle shutting down eShop payments. Just two weeks later, they would update the NVER on this title due to a typo in the web data module.

=== December ===
The exploit ENLBufferPwn, an online RCE exploit for Mario Kart 7, is disclosed by PabloMK7 after it was already patched in version 1.2 of the game. Although it had potential for custom firmware, PabloMK7 disclosed it because it also had potential for mass bricks and/or online cheats.

== 2023 ==

=== March ===
The exploit super-skaterhax, another n3DS-only primary browser exploit, is first released.

Nintendo closes the eShop on the 27th, restricting all exploits that relied on free games and DSiWare to people who had bought them before its close. These exploits were removed from the guide's main paths shortly after.

=== May ===
Nintendo releases version 11.17, patching BannerBomb3 and leaving the o3DS with no free softmod method for the first time in a while.

=== July ===
The exploit nimdsphax, a secondary exploit requiring userland access, is first released by TuxSH and luigoalma.

The exploit Kartminer7, a secondary exploit requiring Seedminer and a copy of Mario Kart 7 (can be either physical or digital), is first released by zoogie.

=== October ===
The exploit MSET9, a full exploit of System Settings with no extra requirements, is first released by zoogie. This restores free softmod access for the o3DS, but also works consistently on the n3DS as well and is generally an extremely stable exploit.

=== December ===
Zoogie(?) calls it quits and is looking forward to future challenges whilst appreciating the time "he had helping people unlock their 3DSs!" -zoogie

3DS:History of 3DS Hacking

2025-03-14T00:50:38Z

StarlitSkies: overhaul conventions, create a (mostly) consistent style and tone, and patch the gaps where some bits of info that should be mentioned aren't

{{#approvable_by: users = Wariohax}}
<references />Heavy adaption of zoogie's "A Pretty Brief History of the 3ds Hacking/Homebrew Scene" from the "3DS hacking scene history" section on GBAtemp.
{{#approvable_by: users = Wariohax}}
<references />Heavy adaption of zoogie's "A Pretty Brief History of the 3ds Hacking/Homebrew Scene" from the "3DS hacking scene history" section on GBAtemp.
== 2011 ==

=== March ===
The official release of the Nintendo 3DS in the west, and the creation of the wiki [[3dbrew:Main_Page|3dbrew]].

=== June ===
The first 3DS roms are dumped.

=== September ===
Crown3DS gives a teaser implying the creation of a flashcart, but instead released an Engrish website promising the community that they are progressing.

=== December ===
The first release of tools that convert video to the type of stereographic 3D video compatible with the Nintendo 3DS Camera.

== 2012 ==

=== Unknown Month ===
It is believed that Neimod's hardware RAM dumps and internal research led to the first userland and a9 exploits.<ref>https://gbatemp.net/threads/3ds-hacking-scene-history.443396/</ref>

=== March ===
The first (?) homebrew app is written in .cxi format, "Hello World", is written by Xcution (author of CiTRUS, a tool that allows BaNneR and ICoN files to be made using the .xbsf format)

== 2013 ==

=== August ===
[[Gateway-3DS]] is first released, and serves as the sole option for homebrew in the 3DS' early years. At this time, there was basic arm9 homebrew possible via an [https://www.3dbrew.org/wiki/System_Settings MSET] exploit combined with [https://github.com/naehrwert/p3ds/tree/df8f52a8c22b7f4758e1a47b2ca712d12be60bc6 p3ds] (python tools for the 3DS).

=== December ===
Users in the community figure out how to reverse engineer [[Gateway-3DS]]' payload to create their own NAND emulation (or redirection). This leads to the users Smealum and Yellows8 creating a private payload called RedNAND.

== 2014 ==

=== January ===
brickgate/brickway - A scandal where Gateway released a FIRM that intentionally bricks consoles using Gateway3DS flashcart clones (such as R4 and Orange3DS). On top of this, its code was written badly enough that it triggered on many legitimate Gateway3DS cartridges, bricking completely 'innocent' users in the crossfire.

=== March ===
The first commit of [https://citra-emulator.com/ Citra], the first major 3DS emulator, is released.

=== November ===
[https://www.gamebrew.org/wiki/Palantine_CFW_3DS Palantine] (a CFW made by Yellows8 and other) is leaked, bringing a closed-source custom firmware to the public. However, it had limitations such as the EmuNAND not being updateable, having a low boot rate, and being difficult to install, among others. The thing it did best, running CIAs, would be taken and added to Gateway3DS shortly after.

The flashcart [[Sky3DS]] is released. It could play pirated roms on entirely stock consoles, but couldn't run homebrew and had a very high ban risk due to the way it worked.

The userland exploit [https://gbatemp.net/threads/introducing-ninjhax-a-nintendo-3ds-homebrew-exploit.374233/ ninjhax] is officially released.

== 2015 ==

=== January ===
Gateway cracks 9.2 and updates their flashcards to OMEGA. The user yifanlu makes a blog post about reverse engineering the memchunkhax/firmlaunchhax combo used by Gateway, and teams such SALT, roxas75, and patois implement their own versions of it shortly after.

=== February ===
[https://gbatemp.net/threads/release-rxtools-roxas75-3ds-toolkit-fw-2-0-9-2.382782/ rxTools] is first released by roxas75.

=== May ===
PastaCFW (named after a leak of sigpatches on pastebin) is first released. It combined the works of patois' Brahma (an open source memchunkhax/firmlaunchhax) to make the first open source custom firmware, though with no emuNAND support.

A fork of rxTools with sigpatches is released by ahp_person (appletinivi), and roxas75 attempts to stop the patches from becoming widespread out of concerns over piracy.

=== June ===
roxas75 eventually gives in due to popular demand, releasing the rxTools source and adding sigpatches in officially, then quits the homebrew scene immediately afterward.

=== July ===
The exploit Ninjhax2x is first released.

=== August ===
The exploits Tubehax and Ironhax are first released.
* Tubehax was a primary userland exploit that took advantage of the 3DS YouTube app, but was unfortunately patched only a couple months later on all firmware.
* Ironhax was the first secondary userland exploit, meaning it requires extra leverage to work (usually from a primary exploit such as Tubehax).

ReiNand, the first fully-featured custom firmware to support the New 3DS, is released.

=== September ===
The exploits Menuhax and Browserhax are first released.
* Menuhax is a secondary exploit of the Home Menu that allows userland control to be gained immediately on boot.
* Browserhax is a term for a series of primary exploits using the internet browsers for the n3DS and o3DS, which would become mainstays of the scene for a few more years before Nintendo finally killed off the potential for any new Browserhax.

=== December ===
An upgrade to Sky3DS, Sky3DS+, is released. Among others, its new features included bypassing cart-based AP in recent games and adding a filesystem-based game loading feature.

The CCC hosts [https://gbatemp.net/threads/32c3-console-hacking-3ds-talk-dec-27-smea-derrek-plutoo.405640/ 32c3] in Hamburg, Germany. During 32c3, [https://smealum.github.io/3ds/32c3/ smealum gives a talk] where snshax, [[arm9loaderhax]], memchunkhax2, and ntrcardhax are revealed, & menuhax and ironhax receive updates to continue functioning.
* snshax, menuchunkhax2, and ntrcardhax would ultimately be of little interest.
* Arm9loaderhax was the first custom bootloader (and thus also the first coldboot custom firmware) for the 3DS, and although it was somewhat unsafe and risky to install, it was still a massive step forward for the homebrew community.

== 2016 ==

=== January ===
Downgrading is first introduced, allowing 10.x firmwares to revert to 9.2 for certain exploits.

Downgrading would soon after be patched by version 10.4.

=== February ===
[[arm9loaderhax]] is fully released, and becomes a mainstay of the scene.

AuReiNand, a fork of ReiNAND, is released after a disagreement with ReiNand's original author (Reisukaku) caused the rest of the developer team to cut ties. Soon after, it would be renamed to Luma3DS and lose its official status as a fork to help distance itself even further.

=== March ===
The exploit memchunkhax2.1 is released by Aliaspider, which allowed 9.2 downgrades to resume until version 10.7 patched it a second time.

=== May ===
R11

=== July ===
A user reveals a DSiWare-based firm downgrade method after several months' worth of teasers. The release of this allowed 9.2 downgrades to continue on versions 11.0 - 11.2, before being patched a third time.

=== September ===
Arm9loaderhax gains two new tools that make its installation even easier: CTRNand Transfer (shortening the install time of both new and old 3DS) and OTPless (instant N3DS install). CTRNand Transfer would survive to see far more use, but OTPless was later removed from use due to having a small but completely random chance to brick.

=== December ===
The CCC hosts [https://gbatemp.net/threads/33c3-console-hacking-2016-3ds-wiiu-talk-dec-27-30-smea-derrek-nedwill-naehrwert.450043/ 33c3] in Hamburg, Germany. During 33c3, [https://derrekr.github.io/3ds/33c3/ derrekr gives a talk] where soundhax, fasthax, and sighax are revealed.
* Soundhax is a free (as opposed to ninjhax, which required Cubic Ninja, a paid game) userland primary exploit for Nintendo 3DS Sound made by nedwill. Almost all consoles at the time were vulnerable to this exploit.
* Fasthax is another k11 (arm11 kernel) exploit, also made by nedwill.
* [https://zoogie.github.io/sh/ Sighax] is a complex exploit of a vulnerability in the bootrom revealed by derrekr; when used properly, it allows anyone to sign arbitrary firmware code without restrictions. derrekr also revealed vague details about how he dumped the 3DS ARM9/ARM11 bootroms, though gave no detail about the exact code.<ref>https://wololo.net/2016/12/28/33c3-3ds-bootrom-cracked-sign-firmwares/</ref>

Nintendo launches a bug bounty program for the 3DS, the bounties being $100 - $20,000 per exploit, this would have an affect of exploit developers moving away from public releases.

== 2017 ==

=== January ===
The arm9 exploit Safehax is released by the user appleTinivi after an anonymous user posted the method on 3dbrew. This exploit allows for full system control up to version 11.2, which significantly streamlined the process for installing a9lh; from this point on, it is reduced to directly downgrading to 2.1, using exploits on 2.1 to get a copy of otp.bin, and then restoring the original NAND and installing a9lh using their otp.

=== February ===
safehax and fasthax are patched by the release of version 11.3, also permanently patching firm downgrading with DSiWare and hardmodding in the process.

=== April ===
A previously-unknown k11 exploit, udsploit is first released by Smealum just as it's patched by the release of version 11.4.

Safehax is updated to work on 11.3 by AppleTinivi due to an oversight in Nintendo's previous patch for safehax.

=== May ===
SciresM creates and gives an unofficial sequel to 33c3, 33.5c3. [https://sciresm.github.io/33-and-a-half-c3/ During this talk], [[boot9strap]] and the concepts that would later allow [[ntrboot]] are revealed.
* Boot9strap is effectively the sequel to arm9loaderhax, being a much cleaner custom bootloader that implements a FIRM sighax signature. Because of how it works, it carries near-zero brick risk and gains control early enough to keep access to the bootroms and decrypted OTP, allowing it to dump them in software.
* Ntrboot allows for any correctly signed firm to be booted from a DS cartridge when the correct keycombo is held down, which also skips the entire normal boot process. This allows it to serve both as an instant custom firmware installation method and an extremely potent unbricking tool.

Since legitimate firms can now be created with nothing more than NAND access, DSiWare and hardmod-based downgrades resume on the latest firmware by using the known plaintext attack.

=== June ===
The n2DSXL is released in Australia, and it is quickly discovered that it happens to have the same vulnerable bootroms as the old 3DS models did.

=== August ===
[[Ntrboot]] is first released, starting only with support for ak2i and R4 flashcards but quickly growing to others.

=== September ===
The Gateway team reveals they have been working on a new flashcard called [[Stargate]], a supposed 3-in-1 hybrid of an ntrboot card, DS flashcart, and [[Sky3DS]]. It was abandoned after a few months due to people seeking out cheaper options for ntrboot cards.

== 2018 ==

=== January ===
A user reveals a method that brute-forces the movable.sed using only the LocalFriendCodeSeed (which is obtainable in userland). This method, called [[3DS:Seedminer|Seedminer]], allowed users to inject hacked DSiWare and install [[boot9strap]] with only one 3DS.

=== July ===
Nintendo releases version 11.8.

=== August ===
Smealum reveals an arm9 exploit chain that he had been teasing at defcon, but it had already been patched in version 11.8 because he disclosed it to the HackerOne bug bounty program earlier on. As part of the reveal, he posted the incomplete repos on Github, but nobody to date has been able to make the exploit work.

=== September ===
A new version of Seedminer called Frogminer is released. This variant of the exploit utilizes an old version of the Japanese Flipnote Studio injected into DS Download Play instead of using Sudoku, meaning unlike the original, it was a completely free miner exploit.

=== December ===
Nintendo releases version 11.9, patching an unreleased browser exploit for both the O3DS and N3DS thanks to another HackerOne bounty submission by the userland exploit developer MrNbaYoh.

== 2019 ==

=== July ===
The exploit BannerBomb3, a userland primary exploit for System Settings that mostly uses the miner series as its secondary exploits, is first released.

=== December ===
The CCC hosts [https://gbatemp.net/threads/36c3-hacker-conference-underway-27th-to-30th-of-december-2019.555023/ 36c3] in Leipzig, Germany. During 36c3, [https://mrnbayoh.github.io/36c3/ MrNbaYoh gives a talk] that demonstrates a new primary exploit chain: using StreetPass tags, someone could remotely takeover a 3DS in userland and install custom firmware, with zero user interaction required. This would set up further exploits developed by TuxSH and Lazypixie which would take over the ARM11 kernel, and later on Safehax 2.x to also take over ARM9. However, due to its potential for malicious use (i.e. remotely bricking consoles), this exploit chain was submitted to HackerOne sometime earlier and patched in version 11.12, two months before 36c3 started.

== 2020 ==

=== April ===
The exploit unSAFE_MODE, a new version of safehax for version 11.13, is first released.

=== July ===
Nintendo's HackerOne bounty program is closed on July 15th. [https://hackerone.com/nintendo/updates?type=team]

=== August ===
The exploit new-browserhax, the simplest and most potent browserhax yet, is released for both the n3DS and o3DS by zoogie. This begins a temporary 'golden age' where installing CFW is the easiest it ever has been, or will be (as of 2025-03-13).

=== September ===
Nintendo shuts down retail production of all 3DS models.

=== October ===
The exploit menuhax67, the successor to Yellows8's menuhax, is first released by zoogie. This version of the exploit is even simpler to activate than the original. (And it's a great meme)

=== November ===
Nintendo releases version 11.14.0-46, fixing a few last-minute submissions of exploits from the HackerOne bounty. This also fixes zoogie's new-browserhax, which ends the 'golden age' temporarily and changes the main userland entry point to back to Seedminer.

=== December ===
After the one month cooldown between each submission of bugs to HackerOne, MrNbaYoh and TuxSH disclose the exploits SSLoth and safecerthax. These two exploits, combined, created a full chain to boot9strap on o3DS models (and still do, when triggered through [[3DS:Safe Mode|Safe Mode]]).

TuxSH updates universal-otherapp to include a new exploit chain (based on smpwn, spipwn, khax and agbhax) that works on NATIVE_FIRM.

The exploit new-browserhax-xl is released by zoogie, resuming the 'golden age' of easy CFW installs.

== 2021 ==

=== January ===
Nintendo ends Unity3DS and many debugging/dev hardware items in one fell swoop.

=== April ===
The exploit old-browserhax-xl is first released by zoogie, complementing new-browserhax-xl so that all consoles have a browser exploit available again.

The exploit [[3DS:Kartdlphax|kartdlphax]], a semi-primary exploit for Mario Kart 7, is released by PabloMK7 (creator of CTGP-7).

=== July ===
Nintendo releases version 11.15, which patches SSLoth in Safe Mode and both browserhax-xl exploits, ending the 'golden age' for good. Seedminer takes its place again.

== 2022 ==

=== August ===
Nintendo releases version 11.16, breaking TuxSH's universal-otherapp combo by patching smpwn.

Nintendo also lays the foundation for the eShop closure by updating MINT/ESHOP to handle shutting down eShop payments. Just two weeks later, they would update the NVER on this title due to a typo in the web data module.

=== December ===
The exploit ENLBufferPwn, an online RCE exploit for Mario Kart 7, is disclosed by PabloMK7 after it was already patched in version 1.2 of the game. Although it had potential for custom firmware, PabloMK7 disclosed it because it also had potential for mass bricks and/or online cheats.

== 2023 ==

=== March ===
The exploit super-skaterhax, another n3DS-only primary browser exploit, is first released.

Nintendo closes the eShop on the 27th, restricting all exploits that relied on free games and DSiWare to people who had bought them before its close. These exploits were removed from the guide's main paths shortly after.

=== May ===
Nintendo releases version 11.17, patching BannerBomb3 and leaving the o3DS with no free softmod method for the first time in a while.

=== July ===
The exploit nimdsphax, a secondary exploit requiring userland access, is first released by TuxSH and luigoalma.

The exploit Kartminer7, a secondary exploit requiring Seedminer and a copy of Mario Kart 7 (can be either physical or digital), is first released by zoogie.

=== October ===
The exploit MSET9, a full exploit of System Settings with no extra requirements, is first released by zoogie. This restores free softmod access for the o3DS, but also works consistently on the n3DS as well and is generally an extremely stable exploit.

=== December ===
Zoogie(?) calls it quits and is looking forward to future challenges whilst appreciating the time "he had helping people unlock their 3DSs!" -zoogie

3DS:Error screens/Luma3DS ErrDisp

2025-02-02T11:01:54Z

StarlitSkies: hmm. actually, i can word that far better than i just did. lemme try again

{{shortcut|3DS:ERRDISP}}
With Luma3DS installed, the 3DS error handler is modified to give significantly more information compared to [[3DS:Error screens/Nintendo error screen|the default error screens]]. These errors are also displayed by certain other applications such as [[3DS:FBI|FBI]].

This page lists various causes and solutions of Luma3DS ErrDisp errors.

==Reading a Luma3DS ErrDisp==

A Luma3DS ErrDisp error has several parts, but only two of them help in finding its cause. They are as follows:
[[File:Luma3DS ErrDisp.jpg|center]]
* '''Process name:''' The part of the system that is triggering the error. Can be helpful if the error code is generic.
* '''Error code:''' The specific reason the error occurred. This is almost always the most helpful part of the error.

==Known errors==

If your ErrDisp displays one of the processes in the first table, you do not need to look up its error code in the second one. The solutions for these processes are almost always the same.

----

{| class="wikitable" style="margin: auto"
! style="font-size:125%;" | Process Name
! style="font-size:125%;" | Problem & Solution
|-
| process: '''cam'''<br>process: '''qtm'''
| Your camera's hardware is damaged or dead.
:If the error code is <code>0xF96183FE</code>, you can open <code>sd:/luma/config.ini</code> and set the variable <code>enable_safe_firm_rosalina</code> to 1 to bypass this error.
:Otherwise, to fix, replace the camera with a new one. To avoid the error until then, or if you cannot get a new camera, disconnect the camera.
|-
| process: '''kernel'''
| Your system software is having a strange issue.
:To fix, diagnose further by reading the contents of the file <code>sd:/luma/errdisp.txt</code>. If you do not understand this file, join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and explain your issue there.
|-
| process: '''mcu'''
| Some piece(s) of hardware related to power or the battery is damaged.
:First, check if your console's charging LED (the orange one) repeatedly turns on and off on its own while a cable is inserted. If it does, this is a sign of a faulty charger port, which may be contributing to the errors and should be fixed before any other troubleshooting.
:Once the charger port is verified intact, any other causes are likely deeper within the motherboard. Dissassembling and carefully analyzing the console will likely be necessary to find these issues, and even then, they may not be practical to fix.
| process: '''nwm'''
| Your WiFi chipset's hardware is damaged or dead.
:To fix, replace the WiFi chipset with a new one. To avoid this error until then or if you cannot get a new chipset, disable WiFi on the 3DS and do not turn it back on.
:If your 3DS is an old model, you can disable WiFi with an external switch. New models must instead disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on may allow you to access Rosalina before it can crash.
|}

{{info|In the following table, when <code>?</code> is in an error code, it is a wildcard.<br>This means any character can be in its position and the error code will remain the same.}}
{| class="wikitable" style="margin: auto"
! style="font-size:125%;" | Error Code
! style="font-size:125%;" | Problem & Solution
|-
| card removed
| Your SD card is faulty, or debris is interfering with its connection to the 3DS.
:To fix, clean the SD card and the SD reader in the 3DS with isopropyl alcohol. If this does not work, [[Checking SD card integrity|test the SD card for errors]].
|-
| 0xC86044D2
| Your NAND does not have enough free space available.
:To fix, join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and explain your issue in detail. Deleting files from the NAND without guidance is likely to cause additional issues.
|-
| 0xC8804464<br>0xC8804471<br>0xC8804497<br>0xC88044A?
| Some dependency of the app you are trying to open does not exist.
:Ensure your SD is inserted, especially if the code is C88044AB specifically. If it is, ensure you have all of the necessary files for what you are trying to do.
:If you are specifically getting 0xc8804471 when opening an out-of-region game, it means it needs [[3DS:Setting Game Locales|locale emulation]] to function properly.<br>If you do have the files and it is happening to a digital title, [[3DS:Safe Mode|do a Safe Mode update.]]<br>If you do have the files and it is happening to a cartridge, either your 3DS or the cartridge likely has a hardware issue.
|-
| 0xC8804478
| The app you tried to open or system software it relies on is missing.
:If this occurs when you open any DS game or DS Download Play, follow [[3DS:TWLFix|TWLFix]].
:If this occurs after doing a manual CTRTransfer, Lazarus3DS, or the nim module errors, check in GodMode9 whether the file path <code>1:/private/movable.sed</code> exists. If it does not, you will need to manually restore <code>movable.sed</code> from a backup. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask for help with this.
|-
| 0xC8A04573
| Your SD card is formatted strangely.
:To fix, [[Formatting an SD card|reformat the SD card.]] If this does not work, [[Checking SD card integrity|test the SD card for errors.]]
|-
| 0xC8A0802B
| If this happened while installing an application, your <code>title.db</code> does not exist or is corrupted.
:To fix, follow one of the two following sets of instructions. The second one will delete all installed games/apps as a side effect, but is significantly faster and simpler.
:#[[3DS:Rebuild Title Database|rebuild <code>title.db</code>]] and then try again.
:#Open GodMode9, go into the file path <code>[A:] SYSNAND SD/dbs/</code> and delete any existing <code>title.db</code>, then press {{B|R}}+{{B|Y}}, choose '''Create a dummy file''', and name this file <code>title.db</code> - leave the file size at 0. Once the file is created, press {{B|START}} to reboot, go into System Settings -> Data Management -> Nintendo 3DS -> Software, and choose '''Yes''' if a prompt about management information appears.
|-
|0xC8A11BEF
|Occurs when attempting to use DLP services with an out-of-region game. This issue is not fixable currently.
|-
| 0xC92044EB<br>0xC92044FA<br>0xC960454?
| Your SD card is set to read-only or is faulty.
:To fix, make sure the slider on the left side of the SD card is pushed up, use a different SD adapter if you are currently using one, and [[Checking SD card integrity|test the SD for errors]] if it is not read-only.
:If the error still happens, the SD card is likely faulty. If it is also read-only, it has permanently protected itself to prevent data corruption. Either way, back up its contents and get a new SD.
If the error is happening when launching a cartridge, especially if the error code is 0xC960454?, delete any updates or DLC to see if the cartridge works as they could be corrupt or faulty. If this succeeds, reinstall them from eShop and ensure the cartridge still works.
|-
| 0xD860446?
| You are attempting to use more processing power than the console currently has available.
:To fix, ensure you are not using a mod that is designed for an emulator rather than native hardware. If you are using such a mod, either toggle off any "Extra RAM" setting or use a different mod.
|-
| 0xD8E0806A
| You have developer UNITINFO enabled and are trying to install a retail game.
:To fix, go into the file <code>sd:/luma/config.ini</code> and set the variable <code>use_dev_unitinfo</code> to 0.
|-
| 0xD900458?
| The app you tried to open, its savedata, or an update file for it is corrupted.
:To fix, if it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it. If it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it. If it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
|-
| {{anchor|0xF9605002}}0xF9605002
| If attempting to use any camera features, your camera hardware is damaged or dead.
|}

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

3DS:Error screens/Luma3DS ErrDisp

2025-02-02T10:52:44Z

StarlitSkies: reword mcu error section to de-emphasize charger port, as causation is not entirely proven (also no, i wasn't thinking about the Rosalina error when i initially wrote this bit)

{{shortcut|3DS:ERRDISP}}
With Luma3DS installed, the 3DS error handler is modified to give significantly more information compared to [[3DS:Error screens/Nintendo error screen|the default error screens]]. These errors are also displayed by certain other applications such as [[3DS:FBI|FBI]].

This page lists various causes and solutions of Luma3DS ErrDisp errors.

==Reading a Luma3DS ErrDisp==

A Luma3DS ErrDisp error has several parts, but only two of them help in finding its cause. They are as follows:
[[File:Luma3DS ErrDisp.jpg|center]]
* '''Process name:''' The part of the system that is triggering the error. Can be helpful if the error code is generic.
* '''Error code:''' The specific reason the error occurred. This is almost always the most helpful part of the error.

==Known errors==

If your ErrDisp displays one of the processes in the first table, you do not need to look up its error code in the second one. The solutions for these processes are almost always the same.

----

{| class="wikitable" style="margin: auto"
! style="font-size:125%;" | Process Name
! style="font-size:125%;" | Problem & Solution
|-
| process: '''cam'''<br>process: '''qtm'''
| Your camera's hardware is damaged or dead.
:If the error code is <code>0xF96183FE</code>, you can open <code>sd:/luma/config.ini</code> and set the variable <code>enable_safe_firm_rosalina</code> to 1 to bypass this error.
:Otherwise, to fix, replace the camera with a new one. To avoid the error until then, or if you cannot get a new camera, disconnect the camera.
|-
| process: '''kernel'''
| Your system software is having a strange issue.
:To fix, diagnose further by reading the contents of the file <code>sd:/luma/errdisp.txt</code>. If you do not understand this file, join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and explain your issue there.
|-
| process: '''mcu'''
| Something related to power or the battery is having issues.
:First, check if your console's charging LED (the orange one) repeatedly turns on and off on its own while a cable is inserted. If it does, this is a sign of a faulty charger port, which may be contributing to the errors and should be fixed before any other troubleshooting.
:If the charger port is intact, there is a deeper hardware issue within the motherboard's power management that may not be fixable.
|-
| process: '''nwm'''
| Your WiFi chipset's hardware is damaged or dead.
:To fix, replace the WiFi chipset with a new one. To avoid this error until then or if you cannot get a new chipset, disable WiFi on the 3DS and do not turn it back on.
:If your 3DS is an old model, you can disable WiFi with an external switch. New models must instead disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on may allow you to access Rosalina before it can crash.
|}

{{info|In the following table, when <code>?</code> is in an error code, it is a wildcard.<br>This means any character can be in its position and the error code will remain the same.}}
{| class="wikitable" style="margin: auto"
! style="font-size:125%;" | Error Code
! style="font-size:125%;" | Problem & Solution
|-
| card removed
| Your SD card is faulty, or debris is interfering with its connection to the 3DS.
:To fix, clean the SD card and the SD reader in the 3DS with isopropyl alcohol. If this does not work, [[Checking SD card integrity|test the SD card for errors]].
|-
| 0xC86044D2
| Your NAND does not have enough free space available.
:To fix, join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and explain your issue in detail. Deleting files from the NAND without guidance is likely to cause additional issues.
|-
| 0xC8804464<br>0xC8804471<br>0xC8804497<br>0xC88044A?
| Some dependency of the app you are trying to open does not exist.
:Ensure your SD is inserted, especially if the code is C88044AB specifically. If it is, ensure you have all of the necessary files for what you are trying to do.
:If you are specifically getting 0xc8804471 when opening an out-of-region game, it means it needs [[3DS:Setting Game Locales|locale emulation]] to function properly.<br>If you do have the files and it is happening to a digital title, [[3DS:Safe Mode|do a Safe Mode update.]]<br>If you do have the files and it is happening to a cartridge, either your 3DS or the cartridge likely has a hardware issue.
|-
| 0xC8804478
| The app you tried to open or system software it relies on is missing.
:If this occurs when you open any DS game or DS Download Play, follow [[3DS:TWLFix|TWLFix]].
:If this occurs after doing a manual CTRTransfer, Lazarus3DS, or the nim module errors, check in GodMode9 whether the file path <code>1:/private/movable.sed</code> exists. If it does not, you will need to manually restore <code>movable.sed</code> from a backup. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask for help with this.
|-
| 0xC8A04573
| Your SD card is formatted strangely.
:To fix, [[Formatting an SD card|reformat the SD card.]] If this does not work, [[Checking SD card integrity|test the SD card for errors.]]
|-
| 0xC8A0802B
| If this happened while installing an application, your <code>title.db</code> does not exist or is corrupted.
:To fix, follow one of the two following sets of instructions. The second one will delete all installed games/apps as a side effect, but is significantly faster and simpler.
:#[[3DS:Rebuild Title Database|rebuild <code>title.db</code>]] and then try again.
:#Open GodMode9, go into the file path <code>[A:] SYSNAND SD/dbs/</code> and delete any existing <code>title.db</code>, then press {{B|R}}+{{B|Y}}, choose '''Create a dummy file''', and name this file <code>title.db</code> - leave the file size at 0. Once the file is created, press {{B|START}} to reboot, go into System Settings -> Data Management -> Nintendo 3DS -> Software, and choose '''Yes''' if a prompt about management information appears.
|-
|0xC8A11BEF
|Occurs when attempting to use DLP services with an out-of-region game. This issue is not fixable currently.
|-
| 0xC92044EB<br>0xC92044FA<br>0xC960454?
| Your SD card is set to read-only or is faulty.
:To fix, make sure the slider on the left side of the SD card is pushed up, use a different SD adapter if you are currently using one, and [[Checking SD card integrity|test the SD for errors]] if it is not read-only.
:If the error still happens, the SD card is likely faulty. If it is also read-only, it has permanently protected itself to prevent data corruption. Either way, back up its contents and get a new SD.
If the error is happening when launching a cartridge, especially if the error code is 0xC960454?, delete any updates or DLC to see if the cartridge works as they could be corrupt or faulty. If this succeeds, reinstall them from eShop and ensure the cartridge still works.
|-
| 0xD860446?
| You are attempting to use more processing power than the console currently has available.
:To fix, ensure you are not using a mod that is designed for an emulator rather than native hardware. If you are using such a mod, either toggle off any "Extra RAM" setting or use a different mod.
|-
| 0xD8E0806A
| You have developer UNITINFO enabled and are trying to install a retail game.
:To fix, go into the file <code>sd:/luma/config.ini</code> and set the variable <code>use_dev_unitinfo</code> to 0.
|-
| 0xD900458?
| The app you tried to open, its savedata, or an update file for it is corrupted.
:To fix, if it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it. If it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it. If it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
|-
| {{anchor|0xF9605002}}0xF9605002
| If attempting to use any camera features, your camera hardware is damaged or dead.
|}

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

3DS:Error screens/Luma3DS exception screen

2025-02-02T10:43:35Z

StarlitSkies: add variant of arm11 boss exception caused by NetPass

{{shortcut|3DS:EXCEPTION}}
This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues.

== Reading a Luma3DS exception screen ==

A Luma3DS exception has four (or five, in a few cases) different parts to it that help in finding its cause, as follows:
[[File:Luma3DS_exception.png|center]]
* '''Processor:''' What part of the system is causing the exception. The two processors are:
** '''Arm9:''' The 'security processor' of the system. These exceptions are usually raised because of errors in NAND data or hardware faults in either the 3DS or its SD card.
** '''Arm11:''' The 'userland' of the system. These exceptions have numerous causes but are more often related to broken software or user data.
* '''Exception type:''' The type of fault that caused the exception. These categories correspond to the ARM exceptions for the [https://developer.arm.com/documentation/ddi0201/d ARM9] and [https://developer.arm.com/documentation/ddi0360/f ARM11] CPUs, as follows:
** '''data abort''': Caused by a read or write to an invalid part of memory. Usually related to game mods/cheats/plugins, broken HOME Menu data, and/or broken CFW applications.
** '''prefetch abort''': Caused by an attempt to execute a CPU instruction that was marked as invalid. Often related to conflicts between CFW and other software.
** '''prefetch abort (svcBreak)''': Caused by either Process9 or homebrew software manually halting because it tripped a pre-defined error condition. Often related to damage to NAND data, even when raised by Arm11. Can also happen when launching an out-of-region game that isn't [[3DS:SGL|locale emulated.]]
** '''prefetch abort (kernel panic)''': Caused by Kernel9 detecting an unrecoverable error and forcibly halting to avoid causing damage. Can be related to any of several things, but hardware issues are the most likely.
** '''undefined instruction''': Caused by an attempt to execute a CPU instruction that was unimplemented, disallowed, or unusable. Often related to software missing its required files (if not on boot) or an outdated <code>boot.firm</code> (if on boot).
* '''Fault status:''' The specific type of ARM exception that was raised. Helpful for developers, but not so much for the end user.
* '''Current process:''' Where the error is coming from in the system. Often the most helpful part of the exception. Some examples of processes are as follows:
** '''fs''': The filesystem, i.e. either the SD card or the NAND.
** '''menu''': Data that is opened either as a part of the HOME Menu or at the same time as it.
** '''loader''': The service that opens apps, meaning the app most recently opened has an issue.
** '''nwm''': Networking services, almost always Wi-Fi.
** '''ns''': The <u>N</u>intendo User Interface <u>S</u>hell, which handles all apps/processes/services in 3DS mode.
* '''Registers (R0-R12/SP/LR/PC/CPSR/FPEXC)''': Usually just internal data that's not worth reading, though R0 is the most likely of them to contain useful data. There are certain notable exceptions that aren't mentioned in the list of known errors, however:
** If the value <code>000400??</code> (the ? marks can be any number) appears in any of the registers, it likely refers to the first half of a title ID - check the value of the register after it to ensure this. If it is a title ID, it can be used to narrow down the original cause of an error.
** If the value of any register starts with the letter C, D, E, or F (even if it isn't in R0) and doesn't look completely random, it may be an error code - this is more likely if the value starts with C or D. You may want to check it manually, as if it is an error code, it can likely help in troubleshooting.

== Known Errors ==

In the following list, the file prefixes on file paths refer to the starting location. <code>sd:/</code> refers to the SD card, and numbers in the format of <code>[X:]</code> refer to GodMode9's drive numbers.
{{info|If the below fixes do not solve your issue or you are unsure of what to do, join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] for further assistance.}}
----

=== <big>Arm9</big> ===

Arm9 errors are sorted by their '''exception type'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>Any Type</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that the SD card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try booting again.
* A system save located on the NAND in <code>[1:]/data</code> has a problem.
* System-unique files are missing from the NAND in <code>[1:]/rw/sys</code>.

<h5>data abort</h5>
* The <code>shared2</code> folder in <code>[2:] SYSNAND TWLN</code> is missing.
** To fix, create this folder.
* System titles have been deleted.
** To fix, perform a [[3DS:Safe Mode|Safe Mode update]]. If this does not work, perform a [[3DS:CTRTransfer|CTRTransfer]].

<h5>prefetch abort (svcBreak)</h5>
* The system movable, <code>[1:]/private/movable.sed</code>, is 288 bytes but a flag is enabled that expects a size of 320 bytes.
** To fix, boot into GodMode9 and select <code>SYSNAND CTRNAND</code>, then go into the <code>private</code> folder.<br>Inside this folder, you will see a file named <code>movable.sed</code>. Select it, and under the options menu, select '''Show in Hexeditor'''.<br>Green-colored numbers will appear in the middle of the screen - press {{B|A}} and then unlock '''writing to sysNAND (lvl2)'''.<br>At the beginning of the file, look for the set of numbers <code>53 45 45 44 00 01</code>. Once you find these numbers, hold {{B|A}} and press {{B|D-PAD DOWN}} while the <code>01</code> value is highlighted to change it to <code>00</code>. Press {{B|B}}, then {{B|A}}, then {{B|B}} to save changes and exit from the hexeditor, then press {{B|START}} to reboot your console.
* <code>SYSNAND CTRNAND</code> has bad CMACs.
** To fix, press R+A on the <code>SYSNAND CTRNAND</code> drive and <code>Fix CMACs for drive</code>. The console will act like it has been formatted after this, and this is intended.
*If none of the above have worked, perform a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]].

<h5>prefetch abort (kernel panic)</h5>
* The console likely has a hardware issue.

<h5>undefined instruction</h5>
* The console likely has a hardware issue, or corrupted sysmodules. Try performing a [[3DS:CTRTransfer|CTRTransfer]] to see if it resolves the issue.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>data abort</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that your card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try again.

=== <big>Arm11</big> ===

All Arm11 errors are sorted by their '''current process'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>act</h5>
* Your NNID(s)' stored data is misconfigured or being interfered with.
** To fix, if [https://pretendo.network Pretendo] is installed, turn it off by disabling <code>Enable loading external FIRMs and modules</code> on [[3DS:Luma3DS/Configuration|the Luma configuration menu]].
*** If this does not help or Pretendo is not installed, then [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|restore a NAND backup]] - especially if you recently tried to [[3DS:GodMode9/Usage#Removing_an_NNID_without_formatting_your_device|log out an NNID]].

<h5>boss</h5>
* <h6>Outdated firmware (11.16 or older):</h6>
** The current firmware version may be too old for SpotPass to work. Perform a [[3DS:Safe Mode|Safe Mode update]].
*** If this does not work, you may require [[3DS:CTRTransfer|a CTRTransfer.]]
* <h6>Latest firmware (11.17):</h6>
** An installation of NetPass is likely interfering with your console. To check this, do the following steps:
**# Hold {{B|SELECT}} while powering on the console
**# Within the [[3DS:Luma3DS/Configuration|Luma config menu]], disable <code>Enable loading external FIRMs and modules</code>
**# Either press {{B|START}} or press {{B|A}} on the <code>Save and exit</code> option to save changes and exit the config menu
**# If the issue stops after this, go into the folder <code>sd:/luma/sysmodules</code> and delete the files <code>0004013000003402.ips</code> and <code>0004013000002602.ips</code> to remove NetPass entirely

<h5>camera</h5>
* Potential hardware issues, or an instance of ShutTheCamUp is crashing.
** Look for and delete <code>/luma/sysmodules/0004013000001602.ips</code> and <code>/luma/titles/0004013000001602/code.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the correct Old or New 3DS patch for [[udb:3ds/shut-the-cam-up|ShutTheCamUp]] if you wish to continue using it.
*** If these don't exist, or the error occurs when booting without an SD card, it's likely hardware issues. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.

<h5>cfg</h5>
* Either the NAND [[3dbrew:Config Savegame|config savegame]] or part of your console-unique file(s) is damaged.
** To fix, first boot into GodMode9, press R+A while the cursor is on the folder <code>[1:]/data/<ID0>/sysdata/00010017</code>, choose to <code>Copy to 0:/gm9/out</code>, then delete the folder. After rebooting, the console will enter initial setup again; this is intended and not an issue.
*** If this does not help, delete the newly created <code>00010017</code> and copy the backup into its place, run [[3DS:ctrcheck|ctrcheck]], and replace any console-unique files marked as invalid or missing with the copies from the <code>essentials.exefs</code> backup inside <code>[S:] SYSNAND VIRTUAL</code> in GodMode9.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|Fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]] and trying to trigger the error with the SD card removed from the console.<br>If the error stops when the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>hid</h5>
* Potential hardware problems, or an instance of rehid is crashing.
** First look for and delete <code>/luma/titles/0004013000001D02</code>, <code>/luma/titles/0004013000003302</code>, <code>/luma/sysmodules/0004013000001D02.cxi</code> and <code>/luma/sysmodules/0004013000003302.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the latest release of [[3DS:Rehid|rehid]] to continue using it.
*** If these don't exist, or rehid has never been installed on this console, it's likely hardware issues. [[3DS:Hardware test|3ds_hw_test]] or [[3DS:ctrcheck|ctrcheck]] may help with fault isolation.

<h5>i2c/gsp/mcu/pxi/spi/</h5>
* The console has a serious hardware issue that is likely not easily fixable.
** Run [[3DS:Hardware test|3ds_hw_test]]. If the test returns zero errors detected, join [https://discord.gg/C29hYvh the Nintendo Homebrew Discord] and ask, in English, for help.

<h5>loader</h5>
* <h6>prefetch abort (svcBreak)</h6>
**The code or sysmodule patch Luma3DS tried to load is invalid or corrupt.
***To fix: Redownload any recently installed patches (eg. Nimbus (Pretendo), Wumiibo, or anything else that goes in <code>/luma/titles</code> or <code>/luma/sysmodules</code>.) Alternatively, you may disable <code>loading external FIRMs and modules</code> as well as <code>Enable game patching</code> in the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]].

<h5>mset</h5>
* System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] and ask, in English, for help.

<h5>menu</h5>
* <h6>data abort</h6>
** The installed [[3DS:Custom themes|theme]] is corrupted or otherwise broken.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>000002cd</code><br>EUR: <code>000002ce</code><br>JPN: <code>000002cc</code>
** The HOME Menu's extra data is corrupted.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>0000008f</code><br>EUR: <code>00000098</code><br>JPN: <code>00000082</code><br>KOR: <code>000000A9</code>
** An installed application is corrupted or otherwise broken.
*** To fix, either perform a [[3DS:Safe Mode|Safe Mode update]], attempt to enter System Settings before the crash occurs and delete the application in Data Management, or [[Formatting an SD card|reformat the SD card]].
* <h6>prefetch abort</h6>
** An installation of Menuhax is conflicting with the custom firmware.
*** To fix, follow the directions [[3DS:Troubleshooting/removing_menuhax67|on this page]].
**If this occurs on boot, set '''Hbmenu autoboot''' in the [[3DS:Luma3DS/Configuration|Luma configuration menu]] to 3DS, then follow the above instructions and turn '''Hbmenu autoboot''' back off once it has been removed.
***Ensure in <code>sd:/luma/config.ini</code> that hbldr_3dsx_titleid is set to 000400000d921e00 and <code>boot.3dsx</code> is in the root.
* <h6>prefetch abort (svcBreak)</h6>
** If <code>R5</code> contains <code>D900458B</code>: The <code>f000000b</code> folder in <code>SYSNAND CTRNAND</code> is broken, its exact location being at <code>[1:]/data/<ID0>/extdata/00048000/f000000b</code>.
*** To fix, backup <code>f000000b</code> by pressing R+A while highlighting it, then selecting <code>Copy to 0:/gm9/out</code>. Once it is backed up, delete the folder. If this does not fix the issue, copy the folder back where it was.
**System titles are missing. Perform a [[3DS:Safe Mode|Safe Mode update]].
**If you have a recent NAND backup, try restoring it with [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|this guide]]

<h5>ns</h5>
* The [[3DS:Luma3DS/Configuration|Luma configuration]] setting '''Hbmenu autoboot''' is set to boot to a title that does not exist.
** To fix, disable the option, install an application with the title ID in <code>sd:/luma/config.ini</code>, or change the set title ID to match an application that does exist.

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi using an external switch. New models do not have this switch disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pm</h5>
* The installed version of Luma3DS likely does not support the current firmware version. This is guaranteed to be true if the contents of R0 are <code>E0E01BF5</code>.
** To fix, [[3dsguide:restoring-updating-cfw|update CFW.]]

<span style="font-size:140%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>3dsx_app</h5>
* The <code>.3dsx</code> file that was most recently opened is corrupted.
** To fix, download a new copy of the <code>.3dsx</code> file. If this error happens when opening the Homebrew Launcher, download a new copy of <code>boot.3dsx</code>.
**: If the error still happens, [[Checking SD card integrity|test the SD card for errors.]]

<h5>app/CtrApp</h5>
* If not <code>prefetch abort (svcBreak)</code>: The app most recently opened is trying to use broken software.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause.
**: If the error still happens, then the game itself is likely faulty. If it is a system app, [[3DS:CTRTransfer|perform a CTRTransfer]]. Otherwise, if it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
* If <code>prefetch abort (svcBreak)</code>: The app most recently opened is out-of-region and relies on locale-specific data. Activate [[3DS:SGL|locale emulation]] for it.

<h5>GARDEN</h5>
* Animal Crossing's game data or savedata is having issues.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, then the game itself may be faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
*** If the error yet still happens, ensure that you have not used a save editor before the error started happening. If you have used a save editor, the edits are broken and you will need to restore a backed-up save, or wipe the save and start over if you have no backup.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]] and trying to recreate the error without the SD card inserted.<br>If the error stops after the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>Kujira/Joker/niji_loc</h5>
* The app most recently opened has an issue of some kind.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, ensure the game is the same region as the console - if it is not, [[3DS:SGL|activate locale emulation for the game.]]
*** If the error yet still happens, then the game itself is likely faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it. If it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it. If it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.

<h5>loader</h5>

* <h6>undefined instruction</h6>
** The app most recently opened has an issue. If the value of R0 starts with C or D, it is an error code, and has a chance of being an error code if the value starts with E or F. Here are some common values for R0:
*** <code>D9004587</code>: When trying to open a game: The game is corrupted, or its seed is not imported.
**** See: [[3DS:Fixing corrupted games]]
*** <code>C8804478</code>: If trying to open the Homebrew Launcher: <code>boot.3dsx</code> is missing from the root of your SD card.
**** To fix: Download the latest Homebrew Launcher from [https://github.com/devkitPro/3ds-hbmenu/releases/latest here]
*** <code>D96077FA</code>/<code>FFFFFFFF</code>: The <code>.3dsx</code> that Luma3DS tried to load is corrupted.
**** To fix, redownload the app you are trying to launch. If this happens when you try to open the Homebrew Launcher itself, see the error above.
*** Most of the other possible error codes that can appear here are listed on [[3DS:Error_screens/Luma3DS_ErrDisp|the ErrDisp page]].
* <h6>prefetch abort (svcBreak)</h6>
**The code or sysmodule patch Luma3DS tried to load is invalid or corrupt.
***To fix: Redownload any recently installed patches (eg. Nimbus (Pretendo), Wumiibo, or anything else that goes in <code>/luma/titles</code> or <code>/luma/sysmodules</code>.) Alternatively, you may disable <code>loading external FIRMs and modules</code> as well as <code>Enable game patching</code> in the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]].

<h5>mset</h5>
* '''If not caused in Nintendo DS Profile:''' System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.
* '''If caused in Nintendo DS Profile:''' Your NVRAM is either corrupted or damaged in hardware. Run [[3DS:ctrcheck|ctrcheck]] - if its results do not include <code>Critical: NVRAM is inaccessible</code>, then follow [[3DS:NVRAM|the Fix NVRAM guide]].

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi with an external switch. New models must instead disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pxi</h5>
* Could be anything from a faulty cartridge to damaged internal components, but will almost always be some type of hardware issue.

<h5>pm</h5>
* The software you have launched may be missing required files. If the value in R0 is <code>E0E01BF5</code>, this is extremely likely to be the cause.

<h5>qtm/cam</h5>
* The camera's hardware is damaged or dead.
** To fix, replace the camera with a new one. To avoid the error until then, disconnect the camera or avoid using anything that activates the camera.

<h5>swkbd</h5>
* The software keyboard is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.
[[Category:Unbricking]]
[[Category:Nintendo 3DS troubleshooting]]
{{Short description|Guide to the CFW error handler}}

3DS:Error screens/Luma3DS exception screen

2024-12-13T04:10:51Z

StarlitSkies: added Category:Nintendo 3DS troubleshooting using HotCat

{{shortcut|3DS:EXCEPTION}}
This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues.

== Reading a Luma3DS exception screen ==

A Luma3DS exception has four (or five, in a few cases) different parts to it that help in finding its cause, as follows:
[[File:Luma3DS_exception.png|center]]
* '''Processor:''' What part of the system is causing the exception. The two processors are:
** '''Arm9:''' The 'security processor' of the system. These exceptions are usually raised because of errors in NAND data or hardware faults in either the 3DS or its SD card.
** '''Arm11:''' The 'userland' of the system. These exceptions have numerous causes but are more often related to broken software or user data.
* '''Exception type:''' The type of fault that caused the exception. These categories correspond to the ARM exceptions for the [https://developer.arm.com/documentation/ddi0201/d ARM9] and [https://developer.arm.com/documentation/ddi0360/f ARM11] CPUs, as follows:
** '''data abort''': Caused by a read or write to an invalid part of memory. Usually related to game mods/cheats/plugins, broken HOME Menu data, and/or broken CFW applications.
** '''prefetch abort''': Caused by an attempt to execute a CPU instruction that was marked as invalid. Often related to conflicts between CFW and other software.
** '''prefetch abort (svcBreak)''': Caused by either Process9 or homebrew software manually halting because it tripped a pre-defined error condition. Often related to damage to NAND data, even when raised by Arm11. Can also happen when launching an out-of-region game that isn't [[3DS:SGL|locale emulated.]]
** '''prefetch abort (kernel panic)''': Caused by Kernel9 detecting an unrecoverable error and forcibly halting to avoid causing damage. Can be related to any of several things, but hardware issues are the most likely.
** '''undefined instruction''': Caused by an attempt to execute a CPU instruction that was unimplemented, disallowed, or unusable. Often related to software missing its required files (if not on boot) or an outdated <code>boot.firm</code> (if on boot).
* '''Fault status:''' The specific type of ARM exception that was raised. Helpful for developers, but not so much for the end user.
* '''Current process:''' Where the error is coming from in the system. Often the most helpful part of the exception. Some examples of processes are as follows:
** '''fs''': The filesystem, i.e. either the SD card or the NAND.
** '''menu''': Data that is opened either as a part of the HOME Menu or at the same time as it.
** '''loader''': The service that opens apps, meaning the app most recently opened has an issue.
** '''nwm''': Networking services, almost always Wi-Fi.
** '''ns''': The <u>N</u>intendo User Interface <u>S</u>hell, which handles all apps/processes/services in 3DS mode.
* '''Registers (R0-R12/SP/LR/PC/CPSR/FPEXC)''': Usually just internal data that's not worth reading, though R0 is the most likely of them to contain useful data. There are certain notable exceptions that aren't mentioned in the list of known errors, however:
** If the value <code>000400??</code> (the ? marks can be any number) appears in any of the registers, it likely refers to the first half of a title ID - check the value of the register after it to ensure this. If it is a title ID, it can be used to narrow down the original cause of an error.
** If the value of any register starts with the letter C, D, E, or F (even if it isn't in R0) and doesn't look completely random, it may be an error code - this is more likely if the value starts with C or D. You may want to check it manually, as if it is an error code, it can likely help in troubleshooting.

== Known Errors ==

In the following list, the file prefixes on file paths refer to the starting location. <code>sd:/</code> refers to the SD card, and numbers in the format of <code>[X:]</code> refer to GodMode9's drive numbers.
{{info|If the below fixes do not solve your issue or you are unsure of what to do, join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] for further assistance.}}
----

=== <big>Arm9</big> ===

Arm9 errors are sorted by their '''exception type'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>Any Type</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that the SD card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try booting again.
* A system save located on the NAND in <code>[1:]/data</code> has a problem.
* System-unique files are missing from the NAND in <code>[1:]/rw/sys</code>.

<h5>data abort</h5>
* The <code>shared2</code> folder in <code>[2:] SYSNAND TWLN</code> is missing.
** To fix, create this folder.
* System titles have been deleted.
** To fix, perform a [[3DS:Safe Mode|Safe Mode update]]. If this does not work, perform a [[3DS:CTRTransfer|CTRTransfer]].

<h5>prefetch abort (svcBreak)</h5>
* The system movable, <code>[1:]/private/movable.sed</code>, is 288 bytes but a flag is enabled that expects a size of 320 bytes.
** To fix, boot into GodMode9 and select <code>SYSNAND CTRNAND</code>, then go into the <code>private</code> folder.<br>Inside this folder, you will see a file named <code>movable.sed</code>. Select it, and under the options menu, select '''Show in Hexeditor'''.<br>Green-colored numbers will appear in the middle of the screen - press {{B|A}} and then unlock '''writing to sysNAND (lvl2)'''.<br>At the beginning of the file, look for the set of numbers <code>53 45 45 44 00 01</code>. Once you find these numbers, hold {{B|A}} and press {{B|D-PAD DOWN}} while the <code>01</code> value is highlighted to change it to <code>00</code>. Press {{B|B}}, then {{B|A}}, then {{B|B}} to save changes and exit from the hexeditor, then press {{B|START}} to reboot your console.
* <code>SYSNAND CTRNAND</code> has bad CMACs.
** To fix, press R+A on the <code>SYSNAND CTRNAND</code> drive and <code>Fix CMACs for drive</code>. The console will act like it has been formatted after this, and this is intended.
*If none of the above have worked, perform a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]].

<h5>prefetch abort (kernel panic)</h5>
* The console likely has a hardware issue.

<h5>undefined instruction</h5>
* The console likely has a hardware issue, or corrupted sysmodules. Try performing a [[3DS:CTRTransfer|CTRTransfer]] to see if it resolves the issue.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>data abort</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that your card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try again.

=== <big>Arm11</big> ===

All Arm11 errors are sorted by their '''current process'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>act</h5>
* Your NNID(s)' stored data is misconfigured or being interfered with.
** To fix, if [https://pretendo.network Pretendo] is installed, turn it off by disabling <code>Enable loading external FIRMs and modules</code> on [[3DS:Luma3DS/Configuration|the Luma configuration menu]].
*** If this does not help or Pretendo is not installed, then [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|restore a NAND backup]] - especially if you recently tried to [[3DS:GodMode9/Usage#Removing_an_NNID_without_formatting_your_device|log out an NNID]].

<h5>boss</h5>
* The current firmware version is too old for SpotPass to work. Perform a [[3DS:Safe Mode|Safe Mode update]].
** If this does not work, you may require [[3DS:CTRTransfer|a CTRTransfer.]]

<h5>camera</h5>
* Potential hardware issues, or an instance of ShutTheCamUp is crashing.
** Look for and delete <code>/luma/sysmodules/0004013000001602.ips</code> and <code>/luma/titles/0004013000001602/code.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the correct Old or New 3DS patch for [[udb:3ds/shut-the-cam-up|ShutTheCamUp]] if you wish to continue using it.
*** If these don't exist, or the error occurs when booting without an SD card, it's likely hardware issues. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.

<h5>cfg</h5>
* Either the NAND [[3dbrew:Config Savegame|config savegame]] or part of your console-unique file(s) is damaged.
** To fix, first boot into GodMode9, press R+A while the cursor is on the folder <code>[1:]/data/<ID0>/sysdata/00010017</code>, choose to <code>Copy to 0:/gm9/out</code>, then delete the folder. After rebooting, the console will enter initial setup again; this is intended and not an issue.
*** If this does not help, delete the newly created <code>00010017</code> and copy the backup into its place, run [[3DS:ctrcheck|ctrcheck]], and replace any console-unique files marked as invalid or missing with the copies from the <code>essentials.exefs</code> backup inside <code>[S:] SYSNAND VIRTUAL</code> in GodMode9.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|Fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]] and trying to trigger the error with the SD card removed from the console.<br>If the error stops when the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>hid</h5>
* Potential hardware problems, or an instance of rehid is crashing.
** First look for and delete <code>/luma/titles/0004013000001D02</code>, <code>/luma/titles/0004013000003302</code>, <code>/luma/sysmodules/0004013000001D02.cxi</code> and <code>/luma/sysmodules/0004013000003302.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the latest release of [[3DS:Rehid|rehid]] to continue using it.
*** If these don't exist, or rehid has never been installed on this console, it's likely hardware issues. [[3DS:Hardware test|3ds_hw_test]] or [[3DS:ctrcheck|ctrcheck]] may help with fault isolation.

<h5>i2c/gsp/mcu/pxi/spi/</h5>
* The console has a serious hardware issue that is likely not easily fixable.
** Run [[3DS:Hardware test|3ds_hw_test]]. If the test returns zero errors detected, join [https://discord.gg/C29hYvh the Nintendo Homebrew Discord] and ask, in English, for help.

<h5>loader</h5>
* <h6>prefetch abort (svcBreak)</h6>
**The code or sysmodule patch Luma3DS tried to load is invalid or corrupt.
***To fix: Redownload any recently installed patches (eg. Nimbus (Pretendo), Wumiibo, or anything else that goes in <code>/luma/titles</code> or <code>/luma/sysmodules</code>.) Alternatively, you may disable <code>loading external FIRMs and modules</code> as well as <code>Enable game patching</code> in the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]].

<h5>mset</h5>
* System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] and ask, in English, for help.

<h5>menu</h5>
* <h6>data abort</h6>
** The installed [[3DS:Custom themes|theme]] is corrupted or otherwise broken.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>000002cd</code><br>EUR: <code>000002ce</code><br>JPN: <code>000002cc</code>
** The HOME Menu's extra data is corrupted.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>0000008f</code><br>EUR: <code>00000098</code><br>JPN: <code>00000082</code><br>KOR: <code>000000A9</code>
** An installed application is corrupted or otherwise broken.
*** To fix, either perform a [[3DS:Safe Mode|Safe Mode update]], attempt to enter System Settings before the crash occurs and delete the application in Data Management, or [[Formatting an SD card|reformat the SD card]].
* <h6>prefetch abort</h6>
** An installation of Menuhax is conflicting with the custom firmware.
*** To fix, follow the directions [[3DS:Troubleshooting/removing_menuhax67|on this page]].
**If this occurs on boot, set '''Hbmenu autoboot''' in the [[3DS:Luma3DS/Configuration|Luma configuration menu]] to 3DS, then follow the above instructions and turn '''Hbmenu autoboot''' back off once it has been removed.
***Ensure in <code>sd:/luma/config.ini</code> that hbldr_3dsx_titleid is set to 000400000d921e00 and <code>boot.3dsx</code> is in the root.
* <h6>prefetch abort (svcBreak)</h6>
** If <code>R5</code> contains <code>D900458B</code>: The <code>f000000b</code> folder in <code>SYSNAND CTRNAND</code> is broken, its exact location being at <code>[1:]/data/<ID0>/extdata/00048000/f000000b</code>.
*** To fix, backup <code>f000000b</code> by pressing R+A while highlighting it, then selecting <code>Copy to 0:/gm9/out</code>. Once it is backed up, delete the folder. If this does not fix the issue, copy the folder back where it was.
**System titles are missing. Perform a [[3DS:Safe Mode|Safe Mode update]].
**If you have a recent NAND backup, try restoring it with [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|this guide]]

<h5>ns</h5>
* The [[3DS:Luma3DS/Configuration|Luma configuration]] setting '''Hbmenu autoboot''' is set to boot to a title that does not exist.
** To fix, disable the option, install an application with the title ID in <code>sd:/luma/config.ini</code>, or change the set title ID to match an application that does exist.

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi using an external switch. New models do not have this switch disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pm</h5>
* The installed version of Luma3DS likely does not support the current firmware version. This is guaranteed to be true if the contents of R0 are <code>E0E01BF5</code>.
** To fix, [[3dsguide:restoring-updating-cfw|update CFW.]]

<span style="font-size:140%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>3dsx_app</h5>
* The <code>.3dsx</code> file that was most recently opened is corrupted.
** To fix, download a new copy of the <code>.3dsx</code> file. If this error happens when opening the Homebrew Launcher, download a new copy of <code>boot.3dsx</code>.
**: If the error still happens, [[Checking SD card integrity|test the SD card for errors.]]

<h5>app/CtrApp</h5>
* If not <code>prefetch abort (svcBreak)</code>: The app most recently opened is trying to use broken software.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause.
**: If the error still happens, then the game itself is likely faulty. If it is a system app, [[3DS:CTRTransfer|perform a CTRTransfer]]. Otherwise, if it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
* If <code>prefetch abort (svcBreak)</code>: The app most recently opened is out-of-region and relies on locale-specific data. Activate [[3DS:SGL|locale emulation]] for it.

<h5>GARDEN</h5>
* Animal Crossing's game data or savedata is having issues.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, then the game itself may be faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
*** If the error yet still happens, ensure that you have not used a save editor before the error started happening. If you have used a save editor, the edits are broken and you will need to restore a backed-up save, or wipe the save and start over if you have no backup.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]] and trying to recreate the error without the SD card inserted.<br>If the error stops after the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>Kujira/Joker/niji_loc</h5>
* The app most recently opened has an issue of some kind.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, ensure the game is the same region as the console - if it is not, [[3DS:SGL|activate locale emulation for the game.]]
*** If the error yet still happens, then the game itself is likely faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it. If it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it. If it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.

<h5>loader</h5>

* <h6>undefined instruction</h6>
** The app most recently opened has an issue. If the value of R0 starts with C or D, it is an error code, and has a chance of being an error code if the value starts with E or F. Here are some common values for R0:
*** <code>D9004587</code>: When trying to open a game: The game is corrupted, or it's seed is not imported.
**** See: [[3DS:Fixing corrupted games]]
*** <code>C8804478</code>: If trying to open the Homebrew Launcher: <code>boot.3dsx</code> is missing from the root of your SD card.
**** To fix: Download the latest Homebrew Launcher from [https://github.com/devkitPro/3ds-hbmenu/releases/latest here]
*** <code>D96077FA</code>/<code>FFFFFFFF</code>: The <code>.3dsx</code> that Luma3DS tried to load is corrupted.
**** To fix, redownload the app you are trying to launch. If this happens when you try to open the Homebrew Launcher itself, see the error above.
*** Most of the other possible error codes that can appear here are listed on [[3DS:Error_screens/Luma3DS_ErrDisp|the ErrDisp page]].
* <h6>prefetch abort (svcBreak)</h6>
**The code or sysmodule patch Luma3DS tried to load is invalid or corrupt.
***To fix: Redownload any recently installed patches (eg. Nimbus (Pretendo), Wumiibo, or anything else that goes in <code>/luma/titles</code> or <code>/luma/sysmodules</code>.) Alternatively, you may disable <code>loading external FIRMs and modules</code> as well as <code>Enable game patching</code> in the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]].

<h5>mset</h5>
* '''If not caused in Nintendo DS Profile:''' System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.
* '''If caused in Nintendo DS Profile:''' Your NVRAM is either corrupted or damaged in hardware. Run [[3DS:ctrcheck|ctrcheck]] - if its results do not include <code>Critical: NVRAM is inaccessible</code>, then follow [[3DS:NVRAM|the Fix NVRAM guide]].

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi with an external switch. New models must instead disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pxi</h5>
* Could be anything from a faulty cartridge to damaged internal components, but will almost always be some type of hardware issue.

<h5>pm</h5>
* The software you have launched may be missing required files. If the value in R0 is <code>E0E01BF5</code>, this is extremely likely to be the cause.

<h5>qtm/cam</h5>
* The camera's hardware is damaged or dead.
** To fix, replace the camera with a new one. To avoid the error until then, disconnect the camera or avoid using anything that activates the camera.

<h5>swkbd</h5>
* The software keyboard is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.
[[Category:Unbricking]]
[[Category:Nintendo 3DS troubleshooting]]
{{Short description|Guide to the CFW error handler}}

3DS:Error screens/Luma3DS ErrDisp

2024-12-13T04:10:43Z

StarlitSkies: added Category:Nintendo 3DS troubleshooting using HotCat

{{shortcut|3DS:ERRDISP}}
With Luma3DS installed, the 3DS error handler is modified to give significantly more information compared to [[3DS:Error screens/Nintendo error screen|the default error screens]]. These errors are also displayed by certain other applications such as [[3DS:FBI|FBI]].

This page lists various causes and solutions of Luma3DS ErrDisp errors.

==Reading a Luma3DS ErrDisp==

A Luma3DS ErrDisp error has several parts, but only two of them help in finding its cause. They are as follows:
[[File:Luma3DS ErrDisp.jpg|center]]
* '''Process name:''' The part of the system that is triggering the error. Can be helpful if the error code is generic.
* '''Error code:''' The specific reason the error occurred. This is almost always the most helpful part of the error.

==Known errors==

If your ErrDisp displays one of the processes in the first table, you do not need to look up its error code in the second one. The solutions for these processes are almost always the same.

----

{| class="wikitable" style="margin: auto"
! style="font-size:125%;" | Process Name
! style="font-size:125%;" | Problem & Solution
|-
| process: '''cam'''<br>process: '''qtm'''
| Your camera's hardware is damaged or dead.
:If the error code is <code>0xF96183FE</code>, you can open <code>sd:/luma/config.ini</code> and set the variable <code>enable_safe_firm_rosalina</code> to 1 to bypass this error.
:Otherwise, to fix, replace the camera with a new one. To avoid the error until then, or if you cannot get a new camera, disconnect the camera.
|-
| process: '''kernel'''
| Your system software is having a strange issue.
:To fix, diagnose further by reading the contents of the file <code>sd:/luma/errdisp.txt</code>. If you do not understand this file, join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and explain your issue there.
|-
| process: '''mcu'''
| Something related to power or the battery is having issues.
:To fix, check if your charger repeatedly disconnects and reconnects while it is inserted. If this is the case, you have a faulty charger port and need to replace it.
:If this is not the case, you have a deeper hardware issue that may not be fixable.
|-
| process: '''nwm'''
| Your WiFi chipset's hardware is damaged or dead.
:To fix, replace the WiFi chipset with a new one. To avoid this error until then or if you cannot get a new chipset, disable WiFi on the 3DS and do not turn it back on.
:If your 3DS is an old model, you can disable WiFi with an external switch. New models must instead disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on may allow you to access Rosalina before it can crash.
|}

{{info|In the following table, when <code>?</code> is in an error code, it is a wildcard.<br>This means any character can be in its position and the error code will remain the same.}}
{| class="wikitable" style="margin: auto"
! style="font-size:125%;" | Error Code
! style="font-size:125%;" | Problem & Solution
|-
| card removed
| Your SD card is faulty, or debris is interfering with its connection to the 3DS.
:To fix, clean the SD card and the SD reader in the 3DS with isopropyl alcohol. If this does not work, [[Checking SD card integrity|test the SD card for errors]].
|-
| 0xC86044D2
| Your NAND does not have enough free space available.
:To fix, join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and explain your issue in detail. Deleting files from the NAND without guidance is likely to cause additional issues.
|-
| 0xC8804464<br>0xC8804471<br>0xC8804497<br>0xC88044A?
| Some dependency of the app you are trying to open does not exist.
:Ensure your SD is inserted, especially if the code is C88044AB specifically. If it is, ensure you have all of the necessary files for what you are trying to do.
:If you are specifically getting 0xc8804471 when opening an out-of-region game, it means it needs [[3DS:Setting Game Locales|locale emulation]] to function properly.<br>If you do have the files and it is happening to a digital title, [[3DS:Safe Mode|do a Safe Mode update.]]<br>If you do have the files and it is happening to a cartridge, either your 3DS or the cartridge likely has a hardware issue.
|-
| 0xC8804478
| The app you tried to open or system software it relies on is missing.
:If this occurs when you open any DS game or DS Download Play, follow [[3DS:TWLFix|TWLFix]].
:If this occurs after doing a manual CTRTransfer, Lazarus3DS, or the nim module errors, check in GodMode9 whether the file path <code>1:/private/movable.sed</code> exists. If it does not, you will need to manually restore <code>movable.sed</code> from a backup. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask for help with this.
|-
| 0xC8A04573
| Your SD card is formatted strangely.
:To fix, [[Formatting an SD card|reformat the SD card.]] If this does not work, [[Checking SD card integrity|test the SD card for errors.]]
|-
| 0xC8A0802B
| If this happened while installing an application, your <code>title.db</code> does not exist or is corrupted.
:To fix, follow one of the two following sets of instructions. The second one will delete all installed games/apps as a side effect, but is significantly faster and simpler.
:#[[3DS:Rebuild Title Database|rebuild <code>title.db</code>]] and then try again.
:#Open GodMode9, go into the file path <code>1:/dbs/</code> and delete any existing <code>title.db</code>, then press {{B|R}}+{{B|Y}}, choose '''Create a dummy file''', and name this file <code>title.db</code> - leave the file size at 0. Once the file is created, press {{B|START}} to reboot, go into System Settings -> Data Management -> Nintendo 3DS -> Software, and choose '''Yes''' if a prompt about management information appears.
|-
|0xC8A11BEF
|Occurs when attempting to use DLP services with an out-of-region game. This issue is not fixable currently.
|-
| 0xC92044EB<br>0xC92044FA<br>0xC960454?
| Your SD card is set to read-only or is faulty.
:To fix, make sure the slider on the left side of the SD card is pushed up, use a different SD adapter if you are currently using one, and [[Checking SD card integrity|test the SD for errors]] if it is not read-only.
:If the error still happens, the SD card is likely faulty. If it is also read-only, it has permanently protected itself to prevent data corruption. Either way, back up its contents and get a new SD.
If the error is happening when launching a cartridge, especially if the error code is 0xC960454?, delete any updates or DLC to see if the cartridge works as they could be corrupt or faulty. If this succeeds, reinstall them from eShop and ensure the cartridge still works.
|-
| 0xD860446?
| You are attempting to use more processing power than the console currently has available.
:To fix, ensure you are not using a mod that is designed for an emulator rather than native hardware. If you are using such a mod, either toggle off any "Extra RAM" setting or use a different mod.
|-
| 0xD8E0806A
| You have developer UNITINFO enabled and are trying to install a retail game.
:To fix, go into the file <code>sd:/luma/config.ini</code> and set the variable <code>use_dev_unitinfo</code> to 0.
|-
| 0xD900458?
| The app you tried to open, its savedata, or an update file for it is corrupted.
:To fix, if it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it. If it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it. If it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
|-
| {{anchor|0xF9605002}}0xF9605002
| If attempting to use any camera features, your camera hardware is damaged or dead.
|}

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

3DS:Error codes

2024-12-13T04:10:28Z

StarlitSkies: added Category:Nintendo 3DS troubleshooting using HotCat

{{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" |<span id="001"><h3>001 - Online Services</h3></span>
|-
|0102
|Unexpected disconnection from network services.
|[https://en-americas-support.nintendo.com/app/answers/detail/a%20id/17043 Nintendo Support Page]
|-
|0112
|Friends server connection timed out.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/14458/ Nintendo Support Page]
|-
|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" |<span id="002"><h3> 002 - Account Related Errors</h3></span>
|-
| 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
|The online service is no longer available.
|
|-
|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
|This specific game cartridge is banned from online play.
|
|-
|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" |<span id="003"><h3>003 - Network Connection Errors</h3></span>
|-
|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" | <span id="005"><h3>005 - Network Installation Management</h3></span>
|-
|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" |<span id="006"><h3>006 - Matchmaking Errors</h3></span>
|-
|0102
-
0111
|Application errors.
|[https://github.com/PretendoNetwork/error-codes/tree/master/data/006 Pretendo Documentation]
|-
|0112
|Connection timed out.
|[https://github.com/PretendoNetwork/error-codes/blob/master/data/006/0112/en_US.json Pretendo Documentation]
|-
|0113
-
0116
|Application errors.
|[https://github.com/PretendoNetwork/error-codes/tree/master/data/006 Pretendo Documentation]
|-
|0301
|Connection could not be established.
|[https://github.com/PretendoNetwork/error-codes/blob/master/data/006/0301/en_US.json Pretendo Documentation]
|-
|0302
|Authentication failed.
|[https://github.com/PretendoNetwork/error-codes/blob/master/data/006/0302/en_US.json Pretendo Documentation]
|-
|0303
-
0311
|Application/Server Communication Errors.
|[https://github.com/PretendoNetwork/error-codes/tree/master/data/006 Pretendo Documentation]
|-
|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]
|-
|0503
-
0511
|Communication Errors.
|[https://github.com/PretendoNetwork/error-codes/tree/master/data/006 Pretendo Documentation]
|-
|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" |<span id="007"><h3>007 - eShop API Errors</h3></span>
|-
|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" |<span id="009"><h3>009 - eShop Application</h3></span>
|-
|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" |<span id="011"><h3>011 - eShop Site</h3></span>
|-
|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" |<span id="012"><h3>012 - Old 3DS Browser Errors</h3></span>
|-
|1004
|The SSL connection failed.
|
|-
|1032
|The file cannot be loaded.
|
|-
|1506,
1509
-
1511
|Certificate Errors.
|[https://github.com/PretendoNetwork/error-codes/tree/master/data/012 Pretendo Documentation]
|-
! colspan="3" |<span id="014"><h3> 014 - Data Transfer Errors</h3></span>
|-
|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" |<span id="022"><h3>022 - More Account Errors</h3></span>
|-
|1001
|Unable to find the specified user.
|
|-
|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>.
|
|-
|2458
|The HTTP client was not authorized to make the request.
|
|-
|2482
|The game server requested could not be found.
|
|-
|2484
|The game server ID and title ID were not linked, or the request did not send a game server ID.
|
|-
|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" |<span id="026"><h3> 026 - Account/eShop?</h3></span>
|-
|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" |<span id="032"><h3>032 - New 3DS Browser Errors </h3></span>
|-
|1006,
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" |<span id="090"><h3>090 - In-Game Specific Errors </h3></span>
|-
|0212
|The game is permanently banned from Pokémon Global Link for using altered or illegal save data.
|
|}

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

3DS:Error screens

2024-12-13T04:09:52Z

StarlitSkies: added Category:Nintendo 3DS troubleshooting using HotCat

{{shortcut|3DS:ERR}}
There are several kinds of errors that can appear on the 3DS. To get to a more relevant page, click on the image or on the link that matches your error.

== Nintendo ErrDisp ==
The stock crash screens. These only occur on stock firmware or on old Luma3DS versions that don't have the custom ErrDisp.

Because these screens are also completely unhelpful for debugging/fault isolation on retail consoles, there is (and will be) no page about them.

If you have a developer console, then these ErrDisps are most similar to Luma3DS ErrDisps and you should check that page instead.

== Nintendo error code ==
[[File:3DS error code.jpg|320px|thumb|link=3DS:Error codes|Nintendo error code]]

The stock error codes. These occur both on stock and custom firmware, and Luma3DS does not replace or edit them.

See [[3DS:Error codes|this page]] for known causes to many of these.
{{clear}}
== Luma3DS ErrDisp ==
[[File:Luma3DS ErrDisp.jpg|320px|thumb|text-top|link=3DS:ERRDISP|Luma3DS ErrDisp]]
{| class="wikitable" style="float-right;"
|+Shortcut:
| [[3DS:ERRDISP]]
|}
Luma3DS replaces the stock ErrDisp to show more information about an error.

See [[/Luma3DS ErrDisp|this page]] for known fixes to many of these.
{{clear}}
== Luma3DS exception screen ==
[[FIle:Luma3DS exception.png|320px|thumb|link=3DS:EXCEPTION|Luma3DS exception screen]]
{| class="wikitable" style="float-right;"
|+ Shortcut:
| [[3DS:EXCEPTION]]
|}
Luma3DS adds a new crash handler for everything its version of ErrDisp does not handle.

See [[/Luma3DS exception screen|this page]] for known fixes to many of these.

{{disambig}}
[[Category:Unbricking]]
[[Category:Nintendo 3DS troubleshooting]]

3DS:Cleaninty

2024-12-05T06:06:10Z

StarlitSkies: fix interwiki link

{{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
}}
'''cleaninty''' is a PC tool used to communicate with Nintendo's [[wikipedia:SOAP|SOAP]] servers. 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.
<br>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.<br>
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.<br>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.
<br>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.
<br> 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>.
<br>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>: <u>(Still experimental. Use with caution.)</u> 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 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.

== 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]].<br>
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 {{GitHub|StarlitSkies/autosoap|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]]

3DS:Cleaninty

2024-12-05T02:12:50Z

StarlitSkies: overhaul to information, split overview into user-friendly and technical versions, revise descriptions of commands, & add {{warning}} to autosoap script

{{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
}}
'''cleaninty''' is a PC tool used to communicate with Nintendo's [[wikipedia:SOAP|SOAP]] servers. 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.
<br>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.<br>
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.<br>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.
<br>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.
<br> 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>.
<br>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>: <u>(Still experimental. Use with caution.)</u> 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 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.

== 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]].<br>
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 {{GitHub|StarlitSkies/autosoap|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]]

Glossary

2024-11-15T23:25:42Z

StarlitSkies: add the codenames that CTR/TWL/NTR refer to

{{Page WIP}}{{TOC right}}
This is a list of terms commonly used within the Nintendo hacking scenes.

== General ==

=== C ===

;custom firmware, CFW
:Software that patches the official firmware to do more things. See also: [[custom firmware]]

=== D ===

;dump
:Copying a game's contents to a format easily accessible by a PC or other device.

=== E ===

;exploit
:Code that is used to take advantage of a vulnerability. In a hacking sense, it can be used as a method to run custom software on the device.

=== H ===

;homebrew
:Software for a device that is not authorized by its manufacturer.

;homebrew launcher
:Software that is used to start other homebrew.

=== N ===

;NAND
:Name for the internal storage or system memory. Often used even if the storage is not using [[wikipedia:Flash memory|NAND technology]].

;NTR
:Short for Nitro, the codename for the Nintendo DS.

=== R ===

;region change, region changing
:Changing the system firmware from its source region.

=== V ===

;vulnerability
:A flaw in software that could be exploited. In a hacking sense, it can be used as a vector to run custom code.

== Nintendo 3DS ==

=== # ===

;.3ds
:The file format for raw Nintendo 3DS cartridge dumps.

;.3dsx
:A custom homebrew application format. Usually used with the Homebrew Launcher.

=== A ===

;AGB_FIRM
:Name for the firmware that runs Game Boy Advance games on the 3DS. See also: [[3DS:GBA games]]

=== C ===

;cardboard
:The System Transfer application.

;CIA
:An installable package. Short for "CTR Importable Archive".

;CTR
:Short for both Citrus and Centrair, the codenames for both the Nintendo 3DS series as a whole and the original 2011 model.

;CTRNAND
:A partition on the Nintendo 3DS NAND. Contains system titles, system saves, tickets, and more.

=== E ===

;EmuNAND
:A redirected NAND that is instead read from the SD card. Also known as a RedNAND.

;essential.exefs
:A file generated using GodMode9 containing various per-console files.

=== I ===

;ID0
:Part of the "Nintendo 3DS" SD card directory tree. The name of this folder is generated from a hash based on the <code>movable.sed</code>.

;ID1
:Part of the "Nintendo 3DS" SD card directory tree. The name of this folder is generated from the CID of the SD card used at the time.

=== L ===

;Luma3DS
:The primary [[custom firmware]] for the 3DS. See also: [[3DS:Luma3DS]]

=== M ===

;movable.sed
:A file intended to be transferred through system transfers (hence its name) that contains the console-specific encryption key for system data (including SD card data). In the Seedminer process, only the encryption key portion of <code>movable.sed</code> (keyY) is derived.

=== N ===

;NATIVE_FIRM
:The normal firmware that is used to run 3DS games and applications.

=== R ===

;Rosalina
:The in-game menu feature of [[3DS:Luma3DS|Luma3DS]].

=== S ===

;seedminer
:The process of bruteforcing the key of a <code>movable.sed</code> file.

=== T ===

;TWL
:Short for Twilight, the codename for the Nintendo DSi.

;TWLNAND
:A partition on the Nintendo 3DS NAND. Contains DSiWare titles and saves, and some system titles.

;TWL_FIRM
:Name for the firmware that runs Nintendo DS and DSi games on the 3DS.

== Wii U ==

== Nintendo Switch ==

=== # ===
; 90DNS
: DNS that blocks system updates on the Nintendo Switch. This can be enabled by following the guide here.

=== A ===
; Atmosphère
: The CFW developed by the Atmosphère-NX organization on GitHub and the one used in this guide.

; Applet mode
: Refers to when the homebrew launcher is running as an applet (typically the album applet). In this state there are fewer resources available and some homebrew apps will either break or have reduced functionality.

; AutoRCM
: A method that corrupts parts of your boot0 and boot1, causing the Switch to boot into RCM automatically. Using this requires an additional peripheral (such as a computer, phone, dongle or trinket) to be able to boot your Switch.

=== B ===
; BOOT0 and BOOT1
: Two partitions of the Switch NAND.

; BIS keys
: Specific keys used to decrypt the NAND.

=== D ===
; Deja Vu
: An unreleased exploit chain for the Nintendo Switch. The completely unpatched version of this chain will grant access to TrustZone, which effectively means being able to enter CFW. The TrustZone part of this exploit was patched in firmware version 5.0.0 and up, but normal homebrew access can still be gained up to firmware version 6.0.1.

; DNS
: Domain Name System. Basically, it's the internet's addressbook. If you visit a website, the DNS is what tells you what server the site is hosted on.

; dns.mitm
: Atmosphère module that enables DNS redirection on a system-wide level. It can be used in place of 90DNS and has the advantage of not needing to be set up for every connection individually.

; Dongle
: Device you can plug in the charging port of your Switch to automatically send a payload if your Switch is in RCM.

=== E ===
; Encryption keys
: Keys used to encrypt files from the Nintendo Switch. These can be dumped by following the guide [[switchguide:extras/dumping_title_keys|here]].

=== F ===
; fusée-gelée/ShofEL2
: Two names for two different implementations of the same exploit. This is an exploit that grants full bootrom access to the Nintendo Switch from the Tegra X1s RCM and permits us to run CFW. This exploit requires an external device and a tiny hardware modification. fusée-gelée is developed by an ex-ReSwitched developer, while ShofEL2 is developed by the failoverfl0w team. This guide uses fusée-gelée.

=== H ===
; hactool
: Software used to decrypt Nintendo Switch files like .XCI and .NSP files.

; Hekate
: A bootloader for the Nintendo Switch. The current guide uses this in combination with essential files from Atmosphère to boot CFW.

; Homebrew launcher
: Software developed by the Switchbrew team that lets you run other Homebrew.

=== J ===
; Jig
: Refers to a piece of hardware that you can put in the Joycon rail to enter RCM.

=== K ===
; KIP
: Short for Kernel Initial Process. These files can be loaded in when the Switch boots in CFW and provide additional functionality.

=== M ===
; MMC
: Refers to the type of NAND the Switch's internal storage uses. Sometimes used interchangeably with NAND (e.g. emuMMC/emuNAND).

=== N ===
; NSP
: File format for installable titles.

; nx-hbloader
: Intermediary program used to load the Homebrew Launcher from CFW developed by Switchbrew. Comes bundled with Atmosphère.

=== P ===
; Patched
: Refers to any Switch not vulnerable to the fusée-gelée exploit.

; PRODINFO
: A partition on the NAND of your Switch. This along with BOOT0 and BOOT1 is the only part of your Switch that contain data that is unrecoverable without a backup. Atmosphère backs up this partition on booting and it is included in your NAND backup.

=== R ===
; ReSwitched
: A hacking team that is one of the main developers for Atmosphère.

; RCM
: A shorthand for "Recovery Mode". When talking about hacking the Switch, this commonly refers to the Recovery Mode in the Tegra X1 chip that is included in the Nintendo Switch. Can be entered by holding down the Tegra X1 home button. This button is not the same as the home button on the joycons. Ways of pressing this button can be found [[switchguide:user_guide/emummc/entering_rcm|here]].

=== T ===
; TegraRCMGUI/fusee-interface-tk
: Software used to run the fusée-gelée exploit on the Switch.

; Tegra X1
: A chip made by Nvidia that is used in the Nintendo Switch.

; Trinket
: A tiny chip that is soldered on the Switch motherboard to automatically send a payload if it is in RCM.

; TrustZone
: The highest security level on the Switch.

=== U ===
; Unpatched
: Opposite of [[#P|patched]].

=== X ===
; XCI
: File format for raw gamecard images.

3DS:DS mode unbrick

2024-11-15T23:12:29Z

StarlitSkies: shift around sections to account for twlfix being more common than everything else

{{shortcut|3DS:DSU}}
The DS mode firmware used for backwards compatibility in a 3DS console can be made unusuable by several different things. This page lists the full usual set of troubleshooting steps to fix this issue.

The troubleshooting below should always be started at the first section. The troubleshooting will direct you to other sections as necessary.

__TOC__

== CFW Check ==
First, we will make sure your console has working CFW. This will help as it allows access to several useful homebrew tools, including [[3DS:GodMode9|GodMode9]].

# Power on your console while holding the {{B|SELECT}} button
#* If your console boots to the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]], press {{B|START}} to save, then continue
#* If your console doesn't boot to the Luma3DS configuration menu, do the same without the SD card inserted
#** If your console does boot to the Luma3DS configuration menu, your SD card wasn't inserted correctly, re-insert it and try again
#** If your console doesn't boot to the Luma3DS configuration menu, you likely do not have Luma installed, and should [[3dsguide:index|install CFW before continuing]] as all but one of the fixes on this page require it
#*** To make sure of this, hold {{Key press|SELECT|START|X|POWER}} for seven seconds while the console is powered off, then power off again, hold {{B|HOME}}, and then press {{B|POWER}} - if the notification LED [[3DS:boot9strap#LED_Status_Codes|lit up a color]] or the [[3DS:fastboot3DS|fastboot3DS]] menu appears, then you have working CFW but something is interfering with Luma. Join the Nintendo Homebrew Discord for more advanced help
#*** If you do not have CFW and do not want to install it, then this guide cannot help you. You should still install CFW through [[3dsguide:index|a method on the guide]].

== Troubleshooting ==

=== Section I - Prep Work ===

# Follow [[3dsguide:restoring-updating-cfw.html|Restoring / Updating CFW]], then the "Updating GodMode9" and "Creating a NAND backup" sections on [[3DS:GodMode9/Usage]]
#* Keep the NAND backup in your <code>gm9/out</code> folder if you have room, as it will be used if you need to do Section V

=== Section II - TWLFix Triad ===

==== Section II, Part I - Regular TWLFix ====

# Download {{GitHub|MechanicalDragon0687/TWLFix-CFW/releases/download/1.3.1/TWLFix-CFW.3dsx|TWLFix-CFW.3dsx}} (direct download)
# Power off your console and insert your SD card into your computer
# Copy <code>TWLFix-CFW.3dsx</code> into <code>sd:/3ds/</code>
# Reinsert your SD card into your console
# Power on your console
# Launch the '''Homebrew Launcher'''
# Launch ''TWLFix CFW Edition'' from the list of homebrew
# Press {{B|A}} to begin
# When the process is completed, press {{B|START}} to reboot
# '''''REQUIRED:''''' Update your console by opening '''System Settings''' -> '''Other Settings''', then going to the last page and selecting '''System Update'''
#* '''This step MUST be completed even if your console is already on the latest version'''
#* Updates while using B9S + Luma3DS (what you have) are safe
#* If the update gives you an error, go through [[3DS:Troubleshooting#Unable to update console|Unable to update console]]
# After the System Update, attempt to open something that uses DS mode
#* If DS mode still crashes, continue to Part II of this section

==== Section II, Part II - Semi-Manual TWLFix ====

{{warning|If you have installed any DSiWare games/apps, be aware that these will also be removed by CompleteDSiWareUninstaller. If you do not want to have to reinstall them afterward,use a tool such as [[3DS:GodMode9|GodMode9]] or [[3DS:FBI|FBI]] to make individual <code>.cia</code> backups of the apps before starting the below instructions.}}

# Download {{GitHub|fox8091/Complete-DSiWare-Uninstaller/releases/download/1.0.2/CompleteDSiWareUninstaller.3dsx|CompleteDSIWareUninstaller.3dsx}} (direct download)
# Power off your console and insert your SD card into your computer
# Copy <code>CompleteDSiWareUninstaller.3dsx</code> into <code>sd:/3ds/</code>
# Reinsert your SD card into your console
# Power on your console
# Launch the '''Homebrew Launcher'''
# Launch ''Complete DSiWare Uninstaller'' from the list of homebrew
# Press {{B|A}} to begin
# When the process is completed, press {{B|START}} to reboot
# '''''REQUIRED:''''' Update your console by opening '''System Settings''' -> '''Other Settings''', then going to the last page and selecting '''System Update'''
#* '''This step MUST be completed even if your console is already on the latest version'''
#* Updates while using B9S + Luma3DS (what you have) are safe
#* If the update gives you an error, go through [[3DS:Troubleshooting#Unable to update console|Unable to update console]]
# After the System Update, attempt to open something that uses DS mode
#* If DS mode still crashes, continue to Part III of this section
#* If it does ''not'' crash and the issue is fixed, you may reinstall any <code>.cia</code> backups of user apps you made earlier now
#** If reinstalling these backups causes DS mode to start crashing again, the apps in question are corrupt. Redo this section and delete the <code>.cia</code>s

==== Section II, Part III - Manual TWLFix ====

# Power off your console and insert your SD card into your computer
# Install a torrent client such as [https://www.qbittorrent.org/download qBitTorrent] or [https://deluge-torrent.org/download/ Deluge] if you do not already have one
# Using your torrent client, download the four following <code>.cia</code> files from their magnet links:
#* {{Magnet|link=magnet:?xt=urn:btih:4A106681407FEDE5DE95CC8BDA635432481F6B5D|text=TWL Version Data}}
#* {{Magnet|link=magnet:?xt=urn:btih:2B9DF8496922F2546DFB0B01220068CE53C19D3D|text=DS Internet}}
#* {{Magnet|link=magnet:?xt=urn:btih:B581D3C5D98F5E621FDDFC1CE5704BB45BF05A8C|text=DS Download Play}}
#* {{Magnet|link=magnet:?xt=urn:btih:7B90D506AD032A581A00035616EAA17A68C48EFF|text=Nintendo DS Cart Whitelist}}
# Depending on whether your 3DS is a new model or an old, download '''one''' of these two <code>.cia</code> files from its magnet link:
#* {{Magnet|link=magnet:?xt=urn:btih:EAB8558C97B18B1F329A2BFCC3C899B84C082A27|text=New 3DS TWL_FIRM}}
#* {{Magnet|link=magnet:?xt=urn:btih:17511EADB6E6F3FF22D04F90644E37BD2D96CA43|text=Old 3DS TWL_FIRM}}
#* If you are not sure of your console's model, check how many shoulder buttons it has - a new model has four of them ({{B|L|ZL|ZR|R}}), and an old model only has two {{B|L|R}}
# Move any files currently inside the folder <code>sd:/cias</code> onto your PC (make it if it doesn't exist), then copy the five downloaded <code>.cia</code>s into that folder
# Reinsert your SD card into your console
# Power on your console
# Open FBI and go into the '''Titles''' section
# Wait for all titles to load, and then go to the bottom where titles colored in purple text appear
# Press {{B|A}} and select <code>Delete title and ticket</code> on the following titles:
#* <code>0004800F484E4C41</code> (TWL Version Data)
#* <code>0004800F484E4841</code> (Nintendo DS Cart Whitelist)
#* <code>DS Download Play</code>
#* <code>Nintendo DSi™</code>
#* New 3DS only: <code>0004013820000102</code> (New3DS TWL_FIRM)
#* Old 3DS only: <code>0004013800000102</code> (TWL_FIRM)
# Go back out of '''Titles''', go into '''SDCARD''', and navigate into the <code>cias</code> folder
# Choose the <code><nowiki><current directory></nowiki></code> option and then <code>Install all cias</code> (do '''not''' select <code>Install and delete all cias</code>)
#* If any of the titles give an error during installation, skip them and attempt to install them individually. If they still give an error, ask for help and state the error code
# Go back out of '''SDCARD''' and go into '''Titles''' again
# Wait for all titles to load, and then go to the bottom. Ensure all of the titles you deleted in Step 10 are now present. If they are not, restart again from Step 10
# Exit FBI, then power off your console and power on again
# Attempt to open something that uses DS mode
# If DS mode still crashes, continue to Section III

=== Section III - Bizarre Edge Cases ===

# Power off your console and insert the SD card into your computer
# Open the file <code>sd:/luma/config.ini</code> in a text editor
# Scroll down until you find the variables <code>disable_arm11_exception_handlers</code> and <code>enable_dsi_external_filter</code>
#* These variables should both be set to 0; if either of them are not, set them to 0 now
# Exit the text editor, remove the SD card, and reinsert the SD card into your console
# Power on your console
# Open [[3DS:FBI|'''FBI''']], then go into '''Remote Install''' -> '''Scan QR code'''
# Check whether the camera works, then press {{B|X}} and similarly check the other camera
#* If either camera causes an error or does not produce any output, your camera is likely bricked - this is known to cause DS mode issues. Disconnect the camera's cable ribbon and/or replace the camera entirely to fix this
# Power off the console, then power on again while holding {{B|SELECT}} to access the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]]
# If either of the following settings are enabled, disable them:
#* <code>Enable loading external FIRMs and modules</code>
#* <code>Enable game patching</code>
# Either press {{B|START}} or select <code>Save and exit</code>, then attempt to open something that uses DS mode
#* If this works, look for and delete faulty patches in <code>sd:/luma/sysmodules</code>, <code>sd:/luma/titles</code>, and <code>sd:/luma/twl_upscaling_filter.bin</code> before turning any of their respective settings back on
# If DS mode still crashes and the camera works, continue to Section IV
#* If the camera does not work, then this is a hardware issue, and this guide will not fix broken hardware.<br>Instead, try disconnecting the camera from the motherboard, then obtain a replacement camera if that does not help

=== Section IV - NVRAM Analysis ===

==== Section IV, Part I - Corruption Check ====

# Open '''System Settings''' -> '''Other Settings''' -> '''Profile''' -> '''Nintendo DS Profile'''
#* If this crashes, continue to Part II of this section
#* If this does not crash, skip to Section V

==== Section IV, Part II - ctrcheck ====

# Follow the instructions on [[3DS:ctrcheck|the ctrcheck page]]
# If you did not get <code>Critical: NVRAM is inaccessible</code>, then reboot after trying all other applicable fixes and continue to Part III of this section

==== Section III, Part III - Restoration ====

# Follow the instructions on [[3DS:NVRAM|the Fix NVRAM page]]
#* If the DS Profile does not crash after this, attempt to open something that uses DS mode (the DS Profile only uses NVRAM, not DS mode)
#** If DS mode still crashes, continue to Section V

=== Section V - TinyFormat ===

# Power off your console and insert the SD card into your computer
# If your NAND backup from Section I is not already on your SD card, copy it to <code>gm9/out</code> now
# Download {{GitHub|javimadgit/TinyFormat/releases/latest|TinyFormat}} (the <code>.zip</code> that is '''not''' the source code) and extract it
# Copy <code>TinyFormat.3dsx</code> from <code>3ds/TinyFormat</code> inside the zip, and paste it into <code>sd:/3ds</code>
# Reinsert the SD card into your console
# Power on your console
# Go into the '''Homebrew Launcher''', then open <code>TinyFormat.3dsx</code>
# Press {{B|Y}} to start the format
# Your console will eventually load to initial setup - this is intended, and does not mean data has been lost
# Go through initial setup until you reach the HOME Menu
#* If you cannot complete initial setup for some reason, you may be able to bypass it using {{GitHub|zoogie/2DSaver|2DSaver}}
# Attempt to open something that uses DS mode
#* If this still crashes, [[3DS:GodMode9/Usage#Restoring a NAND backup|restore your NAND backup]] and then continue to Section VI

=== Section VI - 3ds_hw_test ===

# Power off your console and insert the SD card into your computer
# Download {{GitHub|aspargas2/3ds_hw_test/releases|3ds_hw_test}} (the <code>3ds_hw_test.firm</code> file)
# Place this file in <code>sd:/luma/payloads</code> on the SD card
# Reinsert the SD card into your console
# Hold {{B|START}}, and while holding {{B|START}} power on the console
# Select <code>3ds_hw_test</code>
# Press any button to start the test
# The test will take up to 45 minutes - when it's done, press any button to turn it off
# The file <code>HWTEST.LOG</code> will have been created on the SD root - open this file in a text editor
#* '''GodMode9''' will work for this, if you do not have a PC with an SD slot available
# Scroll down to the end and look at the number of errors
#* If this number is more than 0, your console's RAM is dying and you need to replace the motherboard

If the above number of errors is zero, you have now exhausted all of the conventional fixes. Go to [https://discord.gg/C29hYvh the Nintendo Homebrew Discord], ask for help, and mention that you've tried this page already.

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

User:StarlitSkies/Sidebar

2024-11-11T08:02:48Z

StarlitSkies: Special:ConfirmAccounts

* Current Page
** Special:Purge/{{FULLPAGENAME}}|Purge cache
** Special:PageInfo/{{FULLPAGENAME}}|View page info
** Special:Diff/prev/{{REVISIONID:{{FULLPAGENAME}}}}|View last change
** Special:PrefixIndex/{{NAMESPACE}}:{{ROOTPAGENAME}}|View subpage tree
** Special:Contributions/{{REVISIONUSER:{{FULLPAGENAME}}}}|View editor's activity

* Maintenance
** https://wiki.hacks.guide/w/index.php?title=Special:ApprovedRevs|Unapproved revisions
** https://wiki.hacks.guide/w/index.php?title=Special:ApprovedRevs&show=unapproved|Unapproved pages
** https://wiki.hacks.guide/w/index.php?title=Special:ApprovedRevs&show=notlatestfiles|Unapproved file revisions
** https://wiki.hacks.guide/w/index.php?title=Special:ApprovedRevs&show=unapprovedfiles|Unapproved files
** Special:ConfirmAccounts|Pending account requests

3DS:System Transfer/Target has CFW

2024-10-29T09:40:35Z

StarlitSkies: perplexing.

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
* 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-10-29T09:18:40Z

StarlitSkies: i normally don't read nintendo's official docs on anything. that was a mistake this time

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
* 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 move over the lost data.<br>If you pick a Wireless Transfer in this case anyway, select "Do Not Delete" when prompted on the '''target console''' to preserve all data on the '''source console''''s SD card, or else you will have to manually reobtain all lost homebrew/dumps/etc. by hand

=== 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-10-29T09:07:23Z

StarlitSkies: be more precise about what a PC-based transfer is, make it clear a transfer of some kind has to work, clean up internal wikitext and wording, and use {{GitHub}} templates

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
* 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, and these transfers will always be Wireless Transfers
#* If you cannot do a PC-Based Transfer, 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 move over the lost data.<br>If this is the case, select "Do Not Delete" when prompted on the '''target console''' to preserve all data on the '''source console''''s SD card, or else you will have to manually reobtain all lost homebrew/dumps/etc. by hand

=== 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:StarlitSkies

2024-10-29T08:37:09Z

StarlitSkies: this was old, lacking in style, and vaguely cringe. it is no longer old or lacking in style

{{#babel:en-N|es-1}}
one of the [[Get support|Nintendo Homebrew Discord]]'s 3DS helpers, and a person generally interested in tech of all kinds.
<br>i'm lazy (and depressed), but i also try to be efficient - so if you ask me to do something, it'll still generally get done.

here's all the 3DS-related things i currently maintain or heavily contribute to:
{| class="wikitable"
! Name !! Link
|-
| wiki.hacks.guide || a lot of pages here, but mainly troubleshooting stuff<br>[[3DS:DSU|3DS:DSU]], [[3DS:EXCEPTION]], and [[3DS:ERRDISP]] are my best work
|-
| nintendo homebrew's scripts || https://github.com/nh-server/scripts
|}

----

<span style="font-size:175%; display:flex; font-family:cursive;">my testing grounds</span>
(feel free to pitch in on any WIP articles i start making in the sandbox pages, if it's stuff i want to put on the mainspace eventually then i won't mind.)
{{Special:PrefixIndex/{{FULLPAGENAME}}/sandbox}}
{{Special:PrefixIndex/{{FULLPAGENAME}}/test}}

<span style="font-size:175%; display:flex; font-family:cursive;">user management</span>
* [[/common.css/]]
* [[/common.js/]]
* [[/Sidebar/]]

----

<br><span style="font-size:75%; font-family:cursive;">do these headers show up in comic sans for you? i hope so. they do for me</span>

3DS:Wireless streaming/HzMod

2024-10-23T23:16:10Z

StarlitSkies: get rid of disputed info in the warning at the start, use github and button templates, make internal wikitext not look terrible, and mention what to do with hzloader

{{warning|text=This is not the preferred streaming method on a New 3DS, as [[3DS:STREAM|ntr-hr]] has notably higher performance. If you have a New 3DS, you will likely want to follow the base page instead.}}

== Installing HzMod ==

=== What You Need ===
* Your console's IP from the first section
* The latest release of {{GitHub|RattletraPM/Snickerstream/releases/latest|Snickerstream}}
* [https://puu.sh/zgjTU/3acfc28fa5.zip HzMod]
* {{GitHub|lifehackerhansol/FBI/releases/latest|FBI}} installed on your console

=== Section I: Prep Work ===
# Ensure that your console and your computer are on the same network
# Download and extract the latest Snickerstream <code>.zip</code> file
# Download and extract the HzMod <code>.zip</code> file
# Take the SD card out of your console and put it into your computer
# Copy the <code>HorizonM.cia</code> and <code>HzLoad.cia</code> files from where you extracted the HzMod <code>.zip</code> file to your SD card
#* You may put these files anywhere where you can easily access them
#* If you plan on streaming extended memory games, copy the <code>HzLoad_HIMEM.cia</code> file to your SD card as well
# Put your SD card back into your console

=== Section II: Installing CIAs ===
# Power on your console if it is not already on
# Open FBI
# Press {{B|A}} on <code>SD</code> at the top of your bottom screen
#Find the <code>.cia</code> files that you copied, press {{B|A}} on each one and select <code>Install and delete CIA</code>
#*Once you are done, press {{B|START}} to exit FBI

=== Section III: Streaming ===
# Open the Snickerstream <code>.exe</code> file from where you extracted it
# Change the Streaming app on the right side of the Snickerstream window to <code>HzMod</code> in the dropdown
# On your console, open all the gifts that appeared on your HOME menu and open HorizonM Loader
#* If you plan on streaming extended memory games, open HorizonM HIMEM Loader instead
#* Your notification LED should now turn cyan, meaning it's ready for streaming
# Input your console's IP from the first section into the IP box in the Snickerstream window
#* You may also {{GitHub|RattletraPM/Snickerstream/wiki/Settings-101|adjust your settings}} to your liking if you wish
# Click <code>Connect!</code> in the Snickerstream window
#* Your console's notification LED should turn green, and its top screen should now be streamed to your computer
#* You will likely experience an average of 3 FPS with this method if you have an Old 3DS. This low framerate is normal and cannot be improved, as Old 3DS models have weak hardware
# To open a game correctly, '''do not immediately close HorizonM Loader''' - instead, press the HOME button, select a game to open, and only then press {{B|A}} when asked to close the loader
{{success|HzMod has now been installed and activated.}}

[[Category:Nintendo 3DS guides]]

3DS:Wireless streaming

2024-10-23T23:16:08Z

StarlitSkies: remove {{Page WIP}}, use github and button templates, make internal wikitext not look terrible, emphasize ntr-hr even more, and a dash of extra clarity for the warnings at the start

{{shortcut|3DS:STREAM}}
{{warning|text=This guide cannot be used to stream DS games, DSiWare, and GBA games. You will need a hardware capture card to do that.}}
{{critical|text='''This guide only works on New 3DS models.'''
<br>If you have a Old 3DS model, you can use [[/HzMod|HzMod]] instead; however, keep in mind that Old 3DS models have very weak hardware, and extremely low framerates are unavoidable. It is generally not practical to stream with an Old 3DS.}}

This page will show you how to stream your New 3DS console's screens to your computer over WiFi. However, note the following things:

* Your console and your computer need to be on the same network.
* Streaming audio over WiFi currently isn't possible - you will need to use an AUX cable and a device with Line In at the same time to receive audio.
* If you have a poor connection, you may not get the best results. The receiving computer should be connected to the network via Ethernet or a 5GHz WiFi connection.

{{info|text=Significantly improved performance is available through [https://gbatemp.net/threads/rel-improved-hopefully-ntr-streamer-for-n3ds-xl-ll.644726/ ntr-hr], a fork of the original NTR. However, it is slightly more unstable and still actively being developed.<br>
If you do not consider that a problem, then to use ntr-hr, download <code>BootNTRSelector-PabloMK7-Banner.cia</code> from the {{GitHub|xzn/ntr-hr/releases|ntr-hr releases page}} and use it in place of the BootNTR Selector <code>.cia</code> that would have been downloaded below.}}

== Finding your Console's IP ==
You'll need to know the local IP address of your 3DS later, so it's a good idea to find it now.
{{3DS:Check local IP address}}

== Streaming with NTR ==
<tabber>
|-|Windows - Snickerstream=
=== What You Need ===
* Your console's IP from the first section
* The latest release of {{GitHub|RattletraPM/Snickerstream/releases/latest|Snickerstream}}
* The latest release of {{GitHub|LumaTeam/Luma3DS/releases/latest|Luma3DS}}
* The latest release of {{GitHub|Nanquitas/BootNTR/releases/latest|BootNTR Selector}}
* {{GitHub|lifehackerhansol/FBI/releases/latest|FBI}} installed on your console

=== Section I: Prep Work ===
#Ensure that your console and your computer are on the same network
# Download and extract the latest Snickerstream <code>.zip</code> file
# Download the latest Luma3DS <code>boot.firm</code> file
# Download the latest BootNTR Selector <code>.cia</code> file
# Power off your console
# Take the SD card out of your console and put it into your computer
# Replace the <code>boot.firm</code> file on the root of your SD card with the one you just downloaded
# Copy the BootNTR selector <code>.cia</code> file to your SD card
#* You may put this file where you can easily access it
# Put your SD card back into your console

=== Section II: Installing CIAs ===
# Power on your console
#* If you are prompted with a Luma3DS configuration screen, just press {{B|START}}
# Open FBI
# Press {{B|A}} on <code>SD</code> at the top of your bottom screen
# Find the BootNTR Selector <code>.cia</code> file that you copied, press A on it and select <code>Install and delete CIA</code>
# Press {{B|START}} to exit FBI

===Section III: Streaming===
# Open the Snickerstream <code>.exe</code> file from where you extracted it
# On your console, open the gift that appeared on your home menu and launch BootNTR Selector
#* If you're prompted with 3 buttons on your bottom screen, tap "Use default"
#* If you're prompted to choose an NTR version, choose 3.6
#* Your console's screen should flash some colors, meaning that it's ready for streaming
# Input your console's IP from the first section into the IP box in the Snickerstream window
#* You may also {{GitHub|RattletraPM/Snickerstream/wiki/Settings-101|adjust your settings}} to your liking if you wish
# Click <code>Connect!</code> in the Snickerstream window
#* Your console's screens should now be streamed to your computer

|-|macOS - cuteNTR-OSX=
=== What You Need ===
* Your console's IP from the first section
* The latest release of {{GitHub|EBLeifEricson/cuteNTR-OSX/releases/tag/0.3.2|cuteNTR-OSX}}
* The latest release of {{GitHub|LumaTeam/Luma3DS/releases/latest|Luma3DS}}
* The latest release of {{GitHub|Nanquitas/BootNTR/releases/latest|BootNTR Selector}}
* {{GitHub|lifehackerhansol/FBI/releases/latest|FBI}} installed on your console

=== Section I: Prep Work ===
#Ensure that your console and your computer are on the same network
# Download <code>cuteNTR-0.3.2.dmg</code>
# Download the latest Luma3DS <code>boot.firm</code> file
# Download the latest BootNTR Selector <code>.cia</code> file
# Power off your console
# Take the SD card out of your console and put it into your computer
# Replace the <code>boot.firm</code> file on the root of your SD card with the one you just downloaded
# Copy the BootNTR selector <code>.cia</code> file to your SD card
#* You may put this file where you can easily access it
# Put your SD card back into your console

=== Section II: Installing CIAs ===
# Power on your console
#* If you are prompted with a Luma3DS configuration screen, just press {{B|START}}
# Open FBI
# Press {{B|A}} on <code>SD</code> at the top of your bottom screen
# Find the BootNTR Selector <code>.cia</code> file that you copied, press A on it and select <code>Install and delete CIA</code>
# Press {{B|START}} to exit FBI

=== Section III: Streaming ===
# On your console, open the gift that appeared on your home menu and launch BootNTR Selector
#* If you're prompted with 3 buttons on your bottom screen, tap "Use default"
#* If you're prompted to choose an NTR version, choose 3.6
#* Your console's screen should flash some colors, meaning that it's ready for streaming
# Open the cuteNTR <code>.dmg</code>, and copy the app to the Applications folder
#* You may be prompted to enter the admin password
# Right click on the app and click 'open'
#* You may be prompted to enter the admin password
# Input your console's IP from the first section into the IP box in the cuteNTR window
# Click <code>Connect!</code> in the cuteNTR window
#* Your console's screens should now be streamed to your computer. The top and bottom screens will be 2 different windows. If you cannot find them, on the bottom of the screen where the dock is located, right click the cuteNTR icon and select "Show All Windows"

|-|Debian Linux - cuteNTR=
=== What You Need ===
* Your console's IP from the first section
* sudo
* The latest release of {{GitHub|LumaTeam/Luma3DS/releases/latest|Luma3DS}}
* The latest release of {{GitHub|Nanquitas/BootNTR/releases/latest|BootNTR Selector}}
* {{GitHub|lifehackerhansol/FBI/releases/latest|FBI}} installed on your console

=== Section I: Prep Work ===
# Ensure that your console and your computer are on the same network
# Download the latest Luma3DS <code>boot.firm</code> file
# Download the latest BootNTR Selector <code>.cia</code> file
# Power off your console
# Take the SD card out of your console and put it into your computer
# Replace the <code>boot.firm</code> file on the root of your SD card with the one you just downloaded
# Copy the BootNTR selector <code>.cia</code> file to your SD card
#* You may put this file where you can easily access it
# Put your SD card back into your console

=== Section II: installing cuteNTR ===
This section will add a [https://askubuntu.com/a/4990 PPA] to your sources in order to install cuteNTR. Proceed on your own risk.
# Open the terminal
# Run <code>sudo add-apt-repository ppa:joenosie/3ds</code> to add the PPA to your sources
# Run <code>sudo apt update && sudo apt upgrade</code> to update your setup
# Run <code>sudo apt install cutentr</code> to install cuteNTR

===Section III: Installing CIAs ===
# Power on your console
#* If you are prompted with a Luma3DS configuration screen, just press {{B|START}}
# Open FBI
# Press {{B|A}} on <code>SD</code> at the top of your bottom screen
# Find the BootNTR Selector <code>.cia</code> file that you copied, press A on it and select <code>Install and delete CIA</code>
# Press {{B|START}} to exit FBI

=== Section IV: Streaming ===
# Launch cuteNTR, either from your window manager or with <code>cutentr</code> in the terminal
# On your console, open the gift that appeared on your home menu and launch BootNTR Selector
#* If you're prompted with 3 buttons on your bottom screen, tap "Use default"
#* If you're prompted to choose an NTR version, choose 3.6
#* Your console's screen should flash some colors, meaning that it's ready for streaming
# Input your console's IP from the first section into the IP box next to the <code>Stream</code> button
# Click <code>Stream</code> in the cuteNTR window
#* Your console's screens should now be streamed to your computer

|-|Arch Linux - cuteNTR=
=== What You Need ===
* Your console's IP from the first section
* sudo
* The latest release of {{GitHub|LumaTeam/Luma3DS/releases/latest|Luma3DS}}
* The latest release of {{GitHub|Nanquitas/BootNTR/releases/latest|BootNTR Selector}}
* {{GitHub|lifehackerhansol/FBI/releases/latest|FBI}} installed on your console

=== Section I: Prep Work===
# Ensure that your console and your computer are on the same network
# Download the latest Luma3DS <code>boot.firm</code> file
# Download the latest BootNTR Selector <code>.cia</code> file
# Power off your console
# Take the SD card out of your console and put it into your computer
# Replace the <code>boot.firm</code> file on the root of your SD card with the one you just downloaded
# Copy the BootNTR selector <code>.cia</code> file to your SD card
#* You may put this file where you can easily access it
# Put your SD card back into your console

=== Section II: Installing cuteNTR===
This is a small tutorial for installing the popular AUR helper {{GitHub|Jguer/yay|yay}} and installing cuteNTR with it. If you already have a working AUR helper, or know how to install AUR packages in general, you can download and make <code>cutentr-git</code> yourself, then continue with the next section.

# Open the terminal
# Run <code>sudo pacman -S --needed git base-devel</code> to make sure that you have the base-devel package group and git installed
#* Confirm your password if prompted
# Run <code>git clone https://aur.archlinux.org/yay.git</code>
# Run <code>cd yay</code>
# Run <code>makepkg -si</code> to install yay
#* Confirm your password if prompted
# Run <code>yay -S cutentr-git</code> to install cuteNTR
#* Confirm your password if prompted

=== Section III: Installing CIAs ===
# Power on your console
#* If you are prompted with a Luma3DS configuration screen, just press {{B|START}}
# Open FBI
# Press {{B|A}} on <code>SD</code> at the top of your bottom screen
# Find the BootNTR Selector <code>.cia</code> file that you copied, press A on it and select <code>Install and delete CIA</code>
# Press {{B|START}} to exit FBI

=== Section IV: Streaming ===
# Launch cuteNTR, either from your window manager or with <code>cutentr</code> in the terminal
# On your console, open the gift that appeared on your home menu and launch BootNTR Selector
#* If you're prompted with 3 buttons on your bottom screen, tap "Use default"
#* If you're prompted to choose an NTR version, choose 3.6
#* Your console's screen should flash some colors, meaning that it's ready for streaming
# Input your console's IP from the first section into the IP box next to the <code>Stream</code> button
# Click <code>Stream</code> in the cuteNTR window
#* Your console's screens should now be streamed to your computer

|-|Other Linux - cuteNTR=
=== What You Need ===
* Your console's IP from the first section
* The latest release of [https://flatpak.org/setup/ flatpak] installed on your computer for your operating system
* The latest release of {{GitHub|LumaTeam/Luma3DS/releases/latest|Luma3DS}}
* The latest release of {{GitHub|Nanquitas/BootNTR/releases/latest|BootNTR Selector}}
* {{GitHub|lifehackerhansol/FBI/releases/latest|FBI}} installed on your console

=== Section I: Prep Work ===
# Ensure that your console and your computer are on the same network
# Download the latest Luma3DS <code>boot.firm</code> file
# Download the latest BootNTR Selector <code>.cia</code> file
# Power off your console
# Take the SD card out of your console and put it into your computer
# Replace the <code>boot.firm</code> file on the root of your SD card with the one you just downloaded
# Copy the BootNTR selector <code>.cia</code> file to your SD card
#* You may put this file where you can easily access it
# Put your SD card back into your console

=== Section II: Installing cuteNTR ===
# Open the terminal
# Run <code>mkdir cuteNTR && cd cuteNTR</code> to make a new directory and go into it
# Run <code>wget https://gitlab.com/BoltsJ/cuteNTR/uploads/da6b5bafbab68b45cc9bee0ae590a3ca/com.gitlab.BoltsJ.cuteNTR.flatpak</code>
# Run <code>flatpak install com.gitlab.BoltsJ.cuteNTR.flatpak</code> to install cuteNTR
# Confirm your password and all other prompts with yes
# Run <code>cd .. && rm -r cuteNTR</code> to delete the directory

=== Section III: Installing CIAs ===
# Power on your console
#* If you are prompted with a Luma3DS configuration screen, just press {{B|START}}
# Open FBI
# Press {{B|A}} on <code>SD</code> at the top of your bottom screen
# Find the BootNTR Selector <code>.cia</code> file that you copied, press A on it and select <code>Install and delete CIA</code>
# Press {{B|START}} to exit FBI

=== Section IV: Streaming ===
# Launch cuteNTR by running <code>flatpak run com.gitlab.BoltsJ.cuteNTR</code>
# On your console, open the gift that appeared on your home menu and launch BootNTR Selector
#* If you're prompted with 3 buttons on your bottom screen, tap "Use default"
#* If you're prompted to choose an NTR version, choose 3.6
#* Your console's screen should flash some colors, meaning that it's ready for streaming
# Input your console's IP from the first section into the IP box next to the <code>Stream</code> button
# Click <code>Stream</code> in the cuteNTR window
#* Your console's screens should now be streamed to your computer

</tabber>

== Using Line In to Receive Audio ==

=== What You Need ===

* A 3.5mm to 3.5mm audio cable
* An audio in (line in or microphone in) port on your computer
** Some computers have a single "headphone" port that can be used for both audio output and input. To use one of these, you will need a Y splitter cable

=== How to use ===

# Connect your 3DS to your computer's audio input port with a 3.5mm to 3.5mm audio cable
# Pipe the audio from your audio input port into the software you intend to use
#* The exact steps will depend on the software you're using
#* If you are recording or streaming your game using [https://obsproject.com/ OBS], add a new Audio Input Capture
#* If you are streaming your game via a service such as Discord, you will need to use software such as [https://vb-audio.com/Voicemeeter/ Voicemeeter] to mix your microphone and 3DS audio inputs together
#** If you do not wish to speak while streaming, simply point the app at the 3DS's audio device
#** If you do not wish to mix your microphone and 3DS audio inputs together, you can set up a scene using [https://obsproject.com/ OBS], create a Windowed Projector Preview and share on Discord that window. Then, in [https://obsproject.com/kb/audio-mixer-guide#setting-audio-levels Advanced Audio Properties], turn on the Audio Monitoring for the 3DS Audio Input Capture so that viewers on Discord can hear the 3DS audio. Note that this last step will direct the 3DS audio also to your audio output device (headphones/speakers).
#* To simply listen to the audio, you can [https://www.tenforums.com/tutorials/126383-listen-microphone-through-playback-device-windows.html listen to the audio input device in Windows]

== Troubleshooting ==

* Games such as those in the Pokemon series, Smash Bros 3DS and many more may crash when trying to load or after a loading screen. To avoid this issue, ensure that the debugger is enabled. To do this see [[3DS:Check local IP address|this]] page.
* Similarly, such of the above games may disable Wi-Fi connection while using Snickerstream when trying to play online. To counter this, make sure to enable NFC Patch in Snickerstream.

[[Category:Nintendo 3DS guides]]

3DS:Ctrcheck

2024-10-05T05:16:16Z

StarlitSkies: v4.0, plus matching revisions to in-line troubleshooting

{{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.1.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 [[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 [[Media:Luma ignore cfgnor.firm|the]] special build of Luma linked in the fourteenth word of this sentence, rename it to <code>boot.firm</code>, and put it on the root of your SD card
#** 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 [[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 [[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 [[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 [[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:CTRTransfer/Manual

2024-10-05T05:14:54Z

StarlitSkies: script was updated to use gm9/in instead of gm9/out, so reflecting change here

{{hatnote|This is not the same as a CTRTransfer - it is harder to perform and not needed in most cases.<br>For instructions on a regular CTRTransfer, see [[3DS:CTRTransfer|the main CTRTransfer page.]]}}

A '''manual CTRTransfer''' is an advanced version of a CTRTransfer, used to restore more parts of the system software. It uses the same CTRTransfer images as the regular version, but overwrites the entire CTRNAND instead of just replacing the files that are most prone to damage.

{{critical|This is an advanced process that should only be used when all other options are exhausted.<br>It can be destructive if done incorrectly, so use caution.<br>If you run into any issues or do not understand something, join the [https://discord.gg/C29hYvh Nintendo Homebrew] Discord server and ask, in English, for help.}}

== Instructions ==

=== What You Need ===

* A 3DS console that can access [[3DS:GodMode9|GodMode9]]
* If console-unique files are missing but you have an external backup: The <code>essential.exefs</code> from this console
* A CTRTransfer image from [[3DS:CTRTransfer#What_You_Need|here]] that matches your model and region. This requires a torrent client such as [https://www.qbittorrent.org/download.php qBittorrent] or [https://dev.deluge-torrent.org/wiki/Download Deluge].
* The latest version of [https://raw.githubusercontent.com/nh-server/scripts/main/3DS/manual_transfer.gm9 manual_transfer.gm9]
** To download, right-click/long-press the link and select the <code>Save link as...</code> or similar, then rename the downloaded file to <code>manual_transfer.gm9</code> if it is not named exactly that)

=== Section I - Manual CTRTransfer ===

# Power off the console, remove the SD card, and connect it to your computer
# If you do not already have [[3DS:GodMode9|GodMode9]] on your SD card, take the time to get it now
# Once the CTRTransfer image is downloaded, place the CTRTransfer's <code>.bin</code> and <code>.bin.sha</code> files in <code>sd:/gm9/in</code>
# Copy the <code>manual_transfer.gm9</code> file you downloaded into <code>sd:/gm9/scripts</code>
# Put your SD card back into your console
# Hold {{B|START}}, and while holding {{B|START}}, power on your console. This will launch GodMode9
# Navigate into the drive <code>[S:] SYSNAND VIRTUAL</code>
# Move the cursor onto <code>essential.exefs</code> and press {{B|Y}} to copy it
# Go back out to the drive list, then go into <code>[0:] SDCARD</code>/<code>gm9/in</code>
# Press {{B|Y}}, and choose to <code>Copy path(s)</code>
# Press the {{B|HOME}} button, then go into <code>Scripts...</code> and select <code>manual_transfer</code>
#* You may choose yourself whether to restore optional data or not, unless you were linked to this by another page that says what to pick
# Wait for the script to complete, and then press {{B|A}} when it asks to reboot
# You should reach the HOME Menu without issues

{{success|The manual CTRTransfer has been completed.}}

{{info|If this did not fix your issue, you may have a hardware issue or serious software issue that will require further attention. Need some help? Ask us on Discord: [https://discord.gg/C29hYvh Nintendo Homebrew]}}

{{Short description|Advanced system restoration process}}

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

3DS:Black screen unbrick

2024-10-05T04:00:47Z

StarlitSkies: make datayeet mandatory in manual ctrtransfer section

{{shortcut|3DS:BSU}}
When a 3DS boots to a black screen instead of the HOME Menu, it is usually a bad sign. This page lists common troubleshooting steps to fix this issue.

The troubleshooting below should always be started at the first section. The troubleshooting will direct you to the next sections if necessary.

__TOC__

== CFW Check ==
First, we will check if the console has CFW. This will help as it allows access to [[3DS:GodMode9|GodMode9]], a helpful tool for troubleshooting and fixing issues.

# Power on your console while holding the {{B|SELECT}} button
#* If your console boots to the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]], press {{B|START}} to save, then continue to the CFW troubleshooting section below
#* If your console doesn't boot to the Luma3DS configuration menu, do the same without the SD card inserted
#** If your console does boot to the Luma3DS configuration menu, your SD card wasn't inserted correctly, re-insert it and try again
#** If your console turns off right away, you have CFW and can continue to the CFW troubleshooting section below
#** If your console doesn't boot to the Luma3DS configuration menu but black-screens, your console is likely bricked without CFW, and you should continue to the stock troubleshooting section at the bottom of this page
#*** To make sure of this, hold {{Key press|SELECT|START|X|POWER}} for seven seconds while the console is powered off, then power off again, hold {{B|HOME}}, and then press {{B|POWER}} - if the notification LED [[3DS:boot9strap#LED_Status_Codes|lit up a color]] or the [[3DS:fastboot3DS|fastboot3DS]] menu appears, then you have working CFW but something is interfering with Luma. Join the Nintendo Homebrew Discord for more advanced help

== CFW troubleshooting ==

=== Section I - Prep Work ===

# Follow [[3dsguide:restoring-updating-cfw.html|Restoring / Updating CFW]], then "Updating GodMode9" and "Creating a NAND backup" section on [[3DS:GodMode9/Usage]]
# Take out any inserted game cartridge
# Continue to the next section

=== Section II - RTCBug ===

# Power on your console
# Wait ten seconds, then press {{Key press|L|Down|SELECT}} at the same time
#* If the [[3DS:Luma3DS/Rosalina|Rosalina menu]] opens, you're likely experiencing [[3DS:Lumabug|RTCBug]] - return by pressing B, wait 15 minutes, remove any existing cartridge inserted, and the HOME Menu should load on its own. If this doesn't work, continue to the next section
#* If Rosalina doesn't open, continue to the next section

=== Section III - Luma3DS configuration reset ===

# Insert the SD card into your computer
# Navigate to the folder <code>sd:/luma</code>
# Delete <code>config.ini</code>
# Reinsert the SD card into your console
# Power on your console
#* If your console doesn't boot to the Luma3DS config, follow [[SD Clean]], then return to section 2
# Do not enable anything, just press {{B|START}} to save the default configuration
#* If your console boots to the HOME Menu, you should look for and delete faulty patches in <code>/luma/sysmodules</code> and <code>/luma/titles</code> on the SD card before turning <code>Enable game patching</code> or <code>Loading external FIRMs and modules</code> back on
#* If your console doesn't boot to the HOME Menu, continue to the next section
#* If your console boots to an error, check [[3DS:EXCEPTION|the Luma exceptions page]] for how to fix your error, or ask for help in the Nintendo Homebrew Discord if your error isn't listed there

=== Section IV - SD HOME Menu extdata ===

#Power on your console without the SD card inserted
#* If it boots to the Luma3DS configuration screen, press {{B|START}} to save
#* If it doesn't boot to the HOME menu, continue to the next section
#* If it boots to the HOME Menu, do the following steps:
#*# Insert your SD card into your computer
#*# Navigate to <code>Nintendo 3DS</code> -> <code>ID0</code> -> <code>ID1</code> -> <code>extdata</code>
#*#* <code>ID0</code> and <code>ID1</code> are 32-character long folders
#*#* If you have multiple ID0/ID1 folders, do the following for all of them
#*# Delete the corresponding folder for your region:
#*#* USA: <code>0000008f</code>
#*#* EUR: <code>00000098</code>
#*#* JPN: <code>00000082</code>
#*#* KOR: <code>000000A9</code>
#*# Reinsert your SD card into your console
#*# Power on your console
#*#* If it still doesn't boot to the HOME Menu, but does without the SD card, you're experiencing a very weird issue and should ask in the Nintendo Homebrew discord for more advanced help

=== Section V - Safe Mode ===

# Power on your console while holding {{Key press|L|R|Up|A}}
#* If your console boots to the Safe Mode menu, perform the update and see if it boots to the HOME Menu
#* If it doesn't boot to Safe Mode, or doesn't boot to the HOME Menu after a Safe Mode update, continue to the next section

=== Section VI - ctrcheck ===

# Follow the instructions on [[3DS:Ctrcheck|the ctrcheck page]]
# If the console doesn't boot to the HOME Menu after all applicable fixes have been tried, continue to the next section

=== Section VII - New 3DS camera brick{{anchor|Section VIII - New 3DS camera brick}} ===

{{info|If you are currently troubleshooting an old model console, ignore this and skip to the next section.
<br>If you are unsure whether your console is new or old, look at its shoulder buttons. A new model has four ({{Key press|ZL|L|R|ZR}}), and an old model has two ({{Key press|L|R}}).}}

# Insert your SD card into your computer
# Navigate to the <code>/luma/</code> folder
# Look for <code>errdisp.txt</code>
## If this file already exists, rename it to <code>_errdisp.txt</code>
## If this file doesn't exist, skip to the next section
# Reinsert your SD card into the console
# Power on the console
# Wait 30 seconds without pressing any buttons
# Power off the console
# Navigate to the <code>/luma/</code> folder
# Look for <code>errdisp.txt</code>
#* If this file exists, open it in a text editor, and check if the process name is <code>qtm</code>
#** If the process name is <code>qtm</code>, you need to disconnect your inner camera or replace it
#** If the process name is something else, your console has a very unusual issue and you should ask in the Nintendo Homebrew Discord for more advanced help
#* If this file doesn't exist, continue to the next section

=== Section VIII - CTRTransfer{{anchor|Section VII - CTRTransfer}} ===

# Follow the [[3dsguide:ctrtransfer.html|CTRTransfer guide on 3DS Hacks Guide]]
#* If the console doesn't boot to the HOME Menu at the end of Section III, continue to the next section of this guide

=== Section IX - 3ds_hw_test ===

# Follow the instructions on [[3DS:Hardware test|the hardware test page]]
#* If the number of errors from this is zero, continue to the next section

===Section X - Manual CTRTransfer===

# Follow [[3DS:CTRTransfer/Manual]]
#* When asked whether to restore optional data, press {{B|B}} to deny it

----
By this point, you have exhausted all conventional fixes. If your console has not booted to the HOME Menu by now, go to the Nintendo Homebrew Discord and mention that you've tried this page already.

==Stock troubleshooting==

===Section I - Safe Mode ===

# Power on your console while holding {{Key press|L|R|Up|A}}
#* If your console boots to the Safe Mode menu, perform the update and see if it boots to the HOME Menu
#* If it doesn't boot to Safe Mode, or doesn't boot to the HOME Menu after a Safe Mode update, continue to the next section

===Section II - Shutdown menu ===

# Power on the console
# Wait 30 seconds without touching any buttons
# Press the POWER button
#* If the shutdown menu opens (a grey screen with text), you're experiencing <code>f000000b</code> corruption and must install boot9strap with a [[3DS:ntrboot|ntrboot]] compatible flashcart in order to fix the issue
#* If the screen stays black and the console only powers off if you hold the button for 15 seconds, this may be potentially fixable with ntrboot if it is not a hardware issue

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

3DS:Cleaninty

2024-09-30T02:20:46Z

StarlitSkies: /* Installation */: the AES constant very clearly needs godmode9 too. also mention that the constants are not console-unique

3DS:Ctrcheck

2024-09-30T01:27:36Z

StarlitSkies: change cfgnor luma link to the updated ver of the file

{{Lowercase title}}{{Infobox homebrew
| title = ctrcheck
| for3ds = 1
| developers = StarlitSkies, FrozenFire
| version = 3.1.1
| releasedate = 2024-09-28
| 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.1.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, then read the results on the top screen once the script finishes
# If you are following this guide at someone else's request, send a picture 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 [[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 [[Media:Luma ignore cfgnor.firm|the]] special build of Luma linked in the fourteenth word of this sentence, rename it to <code>boot.firm</code>, and put it on the root of your SD card
#** 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 [[Get support|Nintendo Homebrew Discord]]
#* One or more of movable.sed, LFCS, SecureInfo, and/or HWCAL is marked as <code>not found</code>, <code>is an invalid size</code>, or <code>data is invalid</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 [[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 [[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 [[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]]

File:Luma ignore cfgnor.firm

2024-09-30T01:22:57Z

StarlitSkies: set {{real filename}}

{{real filename|boot.firm}}
== Summary ==
broken NVRAM mitigation, now updated to v13.2!
built from https://github.com/lifehackerhansol/Luma3DS/tree/ignore-cfgnor
[[Category:Nintendo 3DS homebrew]]
[[Category:Unbricking]]

File:Luma ignore cfgnor.firm

2024-09-30T01:22:39Z

StarlitSkies: broken NVRAM mitigation, now updated to v13.2! built from https://github.com/lifehackerhansol/Luma3DS/tree/ignore-cfgnor Category:Nintendo 3DS homebrew Category:Unbricking

== Summary ==
broken NVRAM mitigation, now updated to v13.2!
built from https://github.com/lifehackerhansol/Luma3DS/tree/ignore-cfgnor
[[Category:Nintendo 3DS homebrew]]
[[Category:Unbricking]]

3DS:Movable Moveover

2024-09-29T01:28:21Z

StarlitSkies: change link to nh-server/scripts github instead of gist, and make instructions on downloading clearer

{{hatnote|This page is a guide to transferring data between systems without doing a System Transfer, and usually should only be done if the '''source console''' you are transferring from is nonfunctional or you only have its SD.
<br>If you do not have a specific reason to follow this guide (i.e. both consoles are usable), do [[3DS:System Transfer|a System Transfer]] instead.}}
{{shortcut|3DS:MMM}}

= Required Reading (Do NOT ignore) =

This guide can potentially cause unexpected results if done wrong. Please ensure you read the steps carefully to prevent these unexpected results from happening.
<br>Additionally, ensure you have read the following three warnings to have a full understanding of the potential risks of this guide.

{{critical|text=Do '''NOT''' use a <code>movable.sed</code> from Bruteforce Movable as your system movable (in general, but especially not for this guide). Doing so may cause other issues with the system, and '''WILL''' result in a guaranteed brick if you uninstall CFW while using that movable. Always keep a backup of your original <code>movable.sed</code> if you do so.}}

{{warning|text=If you have already done this guide at any time before the date 2024-08-11, then uninstalling CFW will brick your console, as FixupMovable (which is done by the script) is required to avoid crashing on stock firmware.
<br>If this applies to you, you can fix stock firmware by booting into [[3DS:GodMode9|GodMode9]], copying your <code>movable.sed</code> from <code>1:/private</code> to the '''destination console''''s SD root, copying <code>MovableMoveover.gm9</code> to the <code>/gm9/scripts/</code> folder on the SD card, and then doing the instructions from Section II onward on the '''destination console''' only.}}

{{warning|text=Any games/savedata/themes/DSiWare that was already on the destination console's SD card will become inaccessible once the guide is completed - you will only be able to use the data transferred over from the source console. To access the destination console's data again, you must undo the moveover.
<br>The script extracts the original versions of those files so you are able to undo it if you need to - ''do not lose those files.''}}

{{info|If the above warning will cause issues for you and you are willing to take extra steps to avoid it, you can instead use [[ninfs]] to merge the source console's encrypted files onto the destination console, then [[3DS:Rebuild Title Database|rebuild title.db]] to make any merged games/apps appear.<br>
However, note that even this method will '''not''' bypass the issues of using a Bruteforce Movable <code>movable.sed</code>.}}

If you are confused in any way, join [https://discord.gg/C29hYvh the Nintendo Homebrew Discord] and ask for help in the 3ds-assistance channels.

== What You Need ==

* Two 3DS consoles, both modded with [[3DS:Luma3DS|Luma3DS]]
** These will be referred to as the '''source console''' and '''destination console''' for this guide's purposes
** If either console is not currently modded, stop and mod it with [[3dsguide:|our custom firmware installation guide]] first
* The '''source console's''' <code>essential.exefs</code>, such as the one created in [[3dsguide:finalizing-setup|our guide's Finalizing Setup]]
** If you already have the '''source console's''' <code>movable.sed</code> outside of a <code>.exefs</code> file, you can use that directly
* The '''source console's''' <code>Nintendo 3DS</code> folder
**this should contain the data you are trying to transfer
* The latest version of {{GitHub|/ihaveamac/faketik/releases/latest|faketik}} (the <code>.3dsx</code> file)
* The latest version of {{GitHub|d0k3/GodMode9/releases/latest|GodMode9}} (the GodMode9 <code>.zip</code> file)
* The latest version of [https://raw.githubusercontent.com/nh-server/scripts/main/3DS/MovableMoveover.gm9 MovableMoveover.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>MovableMoveover.gm9</code> if it is not named exactly that

== Instructions ==

=== Section I - Prep Work ===

{{info|Follow these instructions on the '''destination console''' only.}}

# Power off your console and 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
# Copy <code>MovableMoveover.gm9</code> to the <code>/gm9/scripts/</code> folder on your SD card
# Create a folder named <code>3ds</code> on the root of your SD card if it does not already exist
#* This folder stores homebrew applications and data; it is different from the <code>Nintendo 3DS</code> folder that the console automatically generates
# Copy <code>faketik.3dsx</code> to the <code>3ds</code> folder on the root of your SD card
# Copy the '''source console's''' <code>essential.exefs</code> to the root of your SD card and rename it to <code>old-essential.exefs</code>
#* If you have the '''source console''''s <code>movable.sed</code> already in raw form, you can copy that file to the root of the SD card instead
# Copy the '''source console's''' <code>Nintendo 3DS</code> folder the the root of your SD card
# Reinsert your SD card into your console

=== Section II - Setup Script ===
# Hold {{B|Start}}, and while holding {{B|Start}}, power on your console
# Your console will have booted into GodMode9
# If you are prompted to create an essential files backup, press {{B|A}} to do so, then press {{B|A}} to continue once it has completed
# If you are prompted to fix the RTC date&time, press {{B|A}} to do so, then set the date and time, then press {{B|A}} to continue
# Press {{B|Home}} to bring up the action menu
# Select “Scripts…”
# Select “MovableMoveover”
# Follow the prompts in the script, answering any questions that you are asked
# Once the script completes your console will have rebooted
# Your console may act like it has just been formatted - this does not mean your data has been lost. If it does this, proceed normally through initial setup and get to the HOME Menu

{{info|text=The destination console's original <code>essential.exefs</code> and <code>movable.sed</code> files will be in <code>sd:/gm9/out/MMM_Backup</code> on its SD card. It is highly recommended to back up these files to a safe location.}}

=== Section III - Reinstating Apps ===

# Launch the '''Download Play''' application
# Wait until you see the two buttons
#* Do not press either of the buttons
# Press {{B|L|DOWN|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'''
# Relaunch the '''Download Play''' application
# Your console should load the '''Homebrew Launcher'''
# Launch '''faketik''' from the list of homebrew
# Wait until the process is completed
# Press {{B|START}} to exit
# Reboot your console

{{success|text=The moveover is complete. Congratulations for performing a complex procedure.}}

[[Category:Nintendo 3DS guides]]

3DS:CTRTransfer/Manual

2024-09-29T01:28:20Z

StarlitSkies: change link to nh-server/scripts github instead of eiphax, and make instructions on downloading clearer

{{hatnote|This is not the same as a CTRTransfer - it is harder to perform and not needed in most cases.<br>For instructions on a regular CTRTransfer, see [[3DS:CTRTransfer|the main CTRTransfer page.]]}}

A '''manual CTRTransfer''' is an advanced version of a CTRTransfer, used to restore more parts of the system software. It uses the same CTRTransfer images as the regular version, but overwrites the entire CTRNAND instead of just replacing the files that are most prone to damage.

{{critical|This is an advanced process that should only be used when all other options are exhausted.<br>It can be destructive if done incorrectly, so use caution.<br>If you run into any issues or do not understand something, join the [https://discord.gg/C29hYvh Nintendo Homebrew] Discord server and ask, in English, for help.}}

== Instructions ==

=== What You Need ===

* A CTRTransfer image from [[3DS:CTRTransfer#What_You_Need|here]] that matches your model and region. This requires a torrent client such as [https://www.qbittorrent.org/download.php qBittorrent] or [https://dev.deluge-torrent.org/wiki/Download Deluge].
* The latest version of [https://raw.githubusercontent.com/nh-server/scripts/main/3DS/manual_transfer.gm9 manual_transfer.gm9]
** To download, right-click/long-press the link and select the <code>Save link as...</code> or similar, then rename the downloaded file to <code>manual_transfer.gm9</code> if it is not named exactly that)

=== Section I - Manual CTRTransfer ===

# Power off the console, remove the SD card, and connect it to your computer
# If you do not already have [[3DS:GodMode9|GodMode9]] on your SD card, take the time to get it now
# Once the CTRTransfer image is downloaded, place the CTRTransfer's <code>.bin</code> and <code>.bin.sha</code> files in <code>sd:/gm9/out</code>
# Copy the <code>manual_transfer.gm9</code> file you downloaded into <code>sd:/gm9/scripts</code>
# Put your SD card back into your console
# Hold {{B|START}}, and while holding {{B|START}}, power on your console. This will launch GodMode9
# Navigate into the drive <code>[S:] SYSNAND VIRTUAL</code>
# Press {{B|A}} on <code>essential.exefs</code> and select '''Copy to 0:/gm9/out'''
# Press {{B|A}} to continue
# Press the {{B|HOME}} button, then go into <code>Scripts...</code> and select <code>manual_transfer</code>
# Wait for the script to complete, and then press {{B|A}} when it asks to reboot
# You should reach the HOME Menu without issues

{{success|The manual CTRTransfer has been completed.}}

{{info|If this did not fix your issue, you may have a hardware issue or serious software issue that will require further attention. Need some help? Ask us on Discord: [https://discord.gg/C29hYvh Nintendo Homebrew]}}

{{Short description|Advanced system restoration process}}

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

3DS:Ctrcheck

2024-09-29T01:28:18Z

StarlitSkies: change link to nh-server/scripts github instead of gist, change {{Infobox homebrew}} to match, and make instructions on downloading clearer

{{Lowercase title}}{{Infobox homebrew
| title = ctrcheck
| for3ds = 1
| developers = StarlitSkies, FrozenFire
| version = 3.1.1
| releasedate = 2024-09-28
| 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.1.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, then read the results on the top screen once the script finishes
# If you are following this guide at someone else's request, send a picture 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 [[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 [[Media:Luma_v13.0.2_ignore-cfgnor.firm|the]] special build of Luma linked in the fourteenth word of this sentence, rename it to <code>boot.firm</code>, and put it on the root of your SD card
#** 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 [[Get support|Nintendo Homebrew Discord]]
#* One or more of movable.sed, LFCS, SecureInfo, and/or HWCAL is marked as <code>not found</code>, <code>is an invalid size</code>, or <code>data is invalid</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 [[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 [[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 [[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]]

File:Gc-data-management.png

2024-09-24T00:03:54Z

StarlitSkies: StarlitSkies uploaded a new version of File:Gc-data-management.png

File:Wii-options.png

2024-09-24T00:03:50Z

StarlitSkies: StarlitSkies uploaded a new version of File:Wii-options.png

3DS:Error screens/Luma3DS exception screen

2024-09-23T09:08:20Z

StarlitSkies: ctrcheck doesn't have to be ran on Full to check NVRAM anymore

{{shortcut|3DS:EXCEPTION}}
This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues.

== Reading a Luma3DS exception screen ==

A Luma3DS exception has four (or five, in a few cases) different parts to it that help in finding its cause, as follows:
[[File:Luma3DS_exception.png|center]]
* '''Processor:''' What part of the system is causing the exception. The two processors are:
** '''Arm9:''' The 'security processor' of the system. These exceptions are usually raised because of errors in NAND data or hardware faults in either the 3DS or its SD card.
** '''Arm11:''' The 'userland' of the system. These exceptions have numerous causes but are more often related to broken software or user data.
* '''Exception type:''' The type of fault that caused the exception. These categories correspond to the ARM exceptions for the [https://developer.arm.com/documentation/ddi0201/d ARM9] and [https://developer.arm.com/documentation/ddi0360/f ARM11] CPUs, as follows:
** '''data abort''': Caused by a read or write to an invalid part of memory. Usually related to game mods/cheats/plugins, broken HOME Menu data, and/or broken CFW applications.
** '''prefetch abort''': Caused by an attempt to execute a CPU instruction that was marked as invalid. Often related to conflicts between CFW and other software.
** '''prefetch abort (svcBreak)''': Caused by either Process9 or homebrew software manually halting because it tripped a pre-defined error condition. Often related to damage to NAND data, even when raised by Arm11. Can also happen when launching an out-of-region game that isn't [[3DS:SGL|locale emulated.]]
** '''prefetch abort (kernel panic)''': Caused by Kernel9 detecting an unrecoverable error and forcibly halting to avoid causing damage. Can be related to any of several things, but hardware issues are the most likely.
** '''undefined instruction''': Caused by an attempt to execute a CPU instruction that was unimplemented, disallowed, or unusable. Often related to software missing its required files (if not on boot) or an outdated <code>boot.firm</code> (if on boot).
* '''Fault status:''' The specific type of ARM exception that was raised. Helpful for developers, but not so much for the end user.
* '''Current process:''' Where the error is coming from in the system. Often the most helpful part of the exception. Some examples of processes are as follows:
** '''fs''': The filesystem, i.e. either the SD card or the NAND.
** '''menu''': Data that is opened either as a part of the HOME Menu or at the same time as it.
** '''loader''': The service that opens apps, meaning the app most recently opened has an issue.
** '''nwm''': Networking services, almost always Wi-Fi.
** '''ns''': The <u>N</u>intendo User Interface <u>S</u>hell, which handles all apps/processes/services in 3DS mode.
* '''Registers (R0-R12/SP/LR/PC/CPSR/FPEXC)''': Usually just internal data that's not worth reading, though R0 is the most likely of them to contain useful data. There are certain notable exceptions that aren't mentioned in the list of known errors, however:
** If the value <code>000400??</code> (the ? marks can be any number) appears in any of the registers, it likely refers to the first half of a title ID - check the value of the register after it to ensure this. If it is a title ID, it can be used to narrow down the original cause of an error.
** If the value of any register starts with the letter C, D, E, or F (even if it isn't in R0) and doesn't look completely random, it may be an error code - this is more likely if the value starts with C or D. You may want to check it manually, as if it is an error code, it can likely help in troubleshooting.

== Known Errors ==

In the following list, the file prefixes on file paths refer to the starting location. <code>sd:/</code> refers to the SD card, and numbers in the format of <code>[X:]</code> refer to GodMode9's drive numbers.
{{info|If the below fixes do not solve your issue or you are unsure of what to do, join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] for further assistance.}}
----

=== <big>Arm9</big> ===

Arm9 errors are sorted by their '''exception type'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>Any Type</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that the SD card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try booting again.
* A system save located on the NAND in <code>[1:]/data</code> has a problem.
* System-unique files are missing from the NAND in <code>[1:]/rw/sys</code>.

<h5>data abort</h5>
* The <code>shared2</code> folder in <code>[2:] SYSNAND TWLN</code> is missing.
** To fix, create this folder.
* System titles have been deleted.
** To fix, perform a [[3DS:Safe Mode|Safe Mode update]]. If this does not work, perform a [[3DS:CTRTransfer|CTRTransfer]].

<h5>prefetch abort (svcBreak)</h5>
* The system movable, <code>[1:]/private/movable.sed</code>, is 288 bytes but a flag is enabled that expects a size of 320 bytes.
** To fix, boot into GodMode9 and select <code>SYSNAND CTRNAND</code>, then go into the <code>private</code> folder.<br>Inside this folder, you will see a file named <code>movable.sed</code>. Select it, and under the options menu, select '''Show in Hexeditor'''.<br>Green-colored numbers will appear in the middle of the screen - press {{B|A}} and then unlock '''writing to sysNAND (lvl2)'''.<br>At the beginning of the file, look for the set of numbers <code>53 45 45 44 00 01</code>. Once you find these numbers, hold {{B|A}} and press {{B|D-PAD DOWN}} while the <code>01</code> value is highlighted to change it to <code>00</code>. Press {{B|B}}, then {{B|A}}, then {{B|B}} to save changes and exit from the hexeditor, then press {{B|START}} to reboot your console.
* <code>SYSNAND CTRNAND</code> has bad CMACs.
** To fix, press R+A on the <code>SYSNAND CTRNAND</code> drive and <code>Fix CMACs for drive</code>. The console will act like it has been formatted after this, and this is intended.
*If none of the above have worked, perform a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]].

<h5>prefetch abort (kernel panic)</h5>
* The console likely has a hardware issue.

<h5>undefined instruction</h5>
* The console likely has a hardware issue, or corrupted sysmodules. Try performing a [[3DS:CTRTransfer|CTRTransfer]] to see if it resolves the issue.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>data abort</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that your card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try again.

=== <big>Arm11</big> ===

All Arm11 errors are sorted by their '''current process'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>act</h5>
* Your NNID(s)' stored data is misconfigured or being interfered with.
** To fix, if [https://pretendo.network Pretendo] is installed, turn it off by disabling <code>Enable loading external FIRMs and modules</code> on [[3DS:Luma3DS/Configuration|the Luma configuration menu]].
*** If this does not help or Pretendo is not installed, then [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|restore a NAND backup]] - especially if you recently tried to [[3DS:GodMode9/Usage#Removing_an_NNID_without_formatting_your_device|log out an NNID]].

<h5>boss</h5>
* The current firmware version is too old for SpotPass to work. Perform a [[3DS:Safe Mode|Safe Mode update]].
** If this does not work, you may require [[3DS:CTRTransfer|a CTRTransfer.]]

<h5>camera</h5>
* Potential hardware issues, or an instance of ShutTheCamUp is crashing.
** Look for and delete <code>/luma/sysmodules/0004013000001602.ips</code> and <code>/luma/titles/0004013000001602/code.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the correct Old or New 3DS patch for [[udb:3ds/shut-the-cam-up|ShutTheCamUp]] if you wish to continue using it.
*** If these don't exist, or the error occurs when booting without an SD card, it's likely hardware issues. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.

<h5>cfg</h5>
* Either the NAND [[3dbrew:Config Savegame|config savegame]] or part of your console-unique file(s) is damaged.
** To fix, first boot into GodMode9, press R+A while the cursor is on the folder <code>[1:]/data/<ID0>/sysdata/00010017</code>, choose to <code>Copy to 0:/gm9/out</code>, then delete the folder. After rebooting, the console will enter initial setup again; this is intended and not an issue.
*** If this does not help, delete the newly created <code>00010017</code> and copy the backup into its place, run [[3DS:ctrcheck|ctrcheck]], and replace any console-unique files marked as invalid or missing with the copies from the <code>essentials.exefs</code> backup inside <code>[S:] SYSNAND VIRTUAL</code> in GodMode9.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|Fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]] and trying to trigger the error with the SD card removed from the console.<br>If the error stops when the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>hid</h5>
* Potential hardware problems, or an instance of rehid is crashing.
** First look for and delete <code>/luma/titles/0004013000001D02</code>, <code>/luma/titles/0004013000003302</code>, <code>/luma/sysmodules/0004013000001D02.cxi</code> and <code>/luma/sysmodules/0004013000003302.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the latest release of [[3DS:Rehid|rehid]] to continue using it.
*** If these don't exist, or rehid has never been installed on this console, it's likely hardware issues. [[3DS:Hardware test|3ds_hw_test]] or [[3DS:ctrcheck|ctrcheck]] may help with fault isolation.

<h5>i2c/gsp/mcu/pxi/spi/</h5>
* The console has a serious hardware issue that is likely not easily fixable.
** Run [[3DS:Hardware test|3ds_hw_test]]. If the test returns zero errors detected, join [https://discord.gg/C29hYvh the Nintendo Homebrew Discord] and ask, in English, for help.

<h5>mset</h5>
* System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] and ask, in English, for help.

<h5>menu</h5>
* <h6>data abort</h6>
** The installed [[3DS:Custom themes|theme]] is corrupted or otherwise broken.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>000002cd</code><br>EUR: <code>000002ce</code><br>JPN: <code>000002cc</code>
** The HOME Menu's extra data is corrupted.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>0000008f</code><br>EUR: <code>00000098</code><br>JPN: <code>00000082</code><br>KOR: <code>000000A9</code>
** An installed application is corrupted or otherwise broken.
*** To fix, either perform a [[3DS:Safe Mode|Safe Mode update]], attempt to enter System Settings before the crash occurs and delete the application in Data Management, or [[Formatting an SD card|reformat the SD card]].
* <h6>prefetch abort</h6>
** An installation of Menuhax is conflicting with the custom firmware.
*** To fix, follow the directions [[3DS:Troubleshooting/removing_menuhax67|on this page]].
**If this occurs on boot, set '''Hbmenu autoboot''' in the [[3DS:Luma3DS/Configuration|Luma configuration menu]] to 3DS, then follow the above instructions and turn '''Hbmenu autoboot''' back off once it has been removed.
***Ensure in <code>sd:/luma/config.ini</code> that hbldr_3dsx_titleid is set to 000400000d921e00 and <code>boot.3dsx</code> is in the root.
* <h6>prefetch abort (svcBreak)</h6>
** If <code>R5</code> contains <code>D900458B</code>: The <code>f000000b</code> folder in <code>SYSNAND CTRNAND</code> is broken, its exact location being at <code>[1:]/data/<ID0>/extdata/00048000/f000000b</code>.
*** To fix, backup <code>f000000b</code> by pressing R+A while highlighting it, then selecting <code>Copy to 0:/gm9/out</code>. Once it is backed up, delete the folder. If this does not fix the issue, copy the folder back where it was.
**System titles are missing. Perform a [[3DS:Safe Mode|Safe Mode update]].
**If you have a recent NAND backup, try restoring it with [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|this guide]]

<h5>ns</h5>
* The [[3DS:Luma3DS/Configuration|Luma configuration]] setting '''Hbmenu autoboot''' is set to boot to a title that does not exist.
** To fix, disable the option, install an application with the title ID in <code>sd:/luma/config.ini</code>, or change the set title ID to match an application that does exist.

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi using an external switch. New models do not have this switch disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pm</h5>
* The installed version of Luma3DS likely does not support the current firmware version. This is guaranteed to be true if the contents of R0 are <code>E0E01BF5</code>.
** To fix, [[3dsguide:restoring-updating-cfw|update CFW.]]

<span style="font-size:140%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>3dsx_app</h5>
* The <code>.3dsx</code> file that was most recently opened is corrupted.
** To fix, download a new copy of the <code>.3dsx</code> file. If this error happens when opening the Homebrew Launcher, download a new copy of <code>boot.3dsx</code>.
**: If the error still happens, [[Checking SD card integrity|test the SD card for errors.]]

<h5>app/CtrApp</h5>
* If not <code>prefetch abort (svcBreak)</code>: The app most recently opened is trying to use broken software.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause.
**: If the error still happens, then the game itself is likely faulty. If it is a system app, [[3DS:CTRTransfer|perform a CTRTransfer]]. Otherwise, if it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
* If <code>prefetch abort (svcBreak)</code>: The app most recently opened is out-of-region and relies on locale-specific data. Activate [[3DS:SGL|locale emulation]] for it.

<h5>GARDEN</h5>
* Animal Crossing's game data or savedata is having issues.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, then the game itself may be faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
*** If the error yet still happens, ensure that you have not used a save editor before the error started happening. If you have used a save editor, the edits are broken and you will need to restore a backed-up save, or wipe the save and start over if you have no backup.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]] and trying to recreate the error without the SD card inserted.<br>If the error stops after the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>Kujira/Joker/niji_loc</h5>
* The app most recently opened has an issue of some kind.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, ensure the game is the same region as the console - if it is not, [[3DS:SGL|activate locale emulation for the game.]]
*** If the error yet still happens, then the game itself is likely faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it. If it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it. If it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.

<h5>loader</h5>

* <h6>undefined instruction</h6>
** The app most recently opened has an issue. If the value of R0 starts with C or D, it is an error code, and has a chance of being an error code if the value starts with E or F. Here are some common values for R0:
*** <code>D9004587</code>: When trying to open a game: The game is corrupted, or it's seed is not imported.
**** See: [[3DS:Fixing corrupted games]]
*** <code>C8804478</code>: If trying to open the Homebrew Launcher: <code>boot.3dsx</code> is missing from the root of your SD card.
**** To fix: Download the latest Homebrew Launcher from [https://github.com/devkitPro/3ds-hbmenu/releases/latest here]
*** <code>D96077FA</code>/<code>FFFFFFFF</code>: The <code>.3dsx</code> that Luma3DS tried to load is corrupted.
**** To fix, redownload the app you are trying to launch. If this happens when you try to open the Homebrew Launcher itself, see the error above.
*** Most of the other possible error codes that can appear here are listed on [[3DS:Error_screens/Luma3DS_ErrDisp|the ErrDisp page]].
* <h6>prefetch abort (svcBreak)</h6>
**The LayeredFS or sysmodule patch Luma3DS tried to load is invalid or corrupt.
***To fix: Redownload any recently installed patches (eg. Nimbus (Pretendo), Wumiibo, or anything else that goes in <code>/luma/titles</code> or <code>/luma/sysmodules</code>.) Alternatively, you may disable <code>loading external FIRMs and modules</code> as well as <code>Enable game patching</code> in the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]].

<h5>mset</h5>
* '''If not caused in Nintendo DS Profile:''' System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.
* '''If caused in Nintendo DS Profile:''' Your NVRAM is either corrupted or damaged in hardware. Run [[3DS:ctrcheck|ctrcheck]] - if its results do not include <code>Critical: NVRAM is inaccessible</code>, then follow [[3DS:NVRAM|the Fix NVRAM guide]].

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi with an external switch. New models must instead disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pxi</h5>
* Could be anything from a faulty cartridge to damaged internal components, but will almost always be some type of hardware issue.

<h5>pm</h5>
* The software you have launched may be missing required files. If the value in R0 is <code>E0E01BF5</code>, this is extremely likely to be the cause.

<h5>qtm/cam</h5>
* The camera's hardware is damaged or dead.
** To fix, replace the camera with a new one. To avoid the error until then, disconnect the camera or avoid using anything that activates the camera.

<h5>swkbd</h5>
* The software keyboard is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.
[[Category:Unbricking]]
{{Short description|Guide to the CFW error handler}}

3DS:Ctrcheck

2024-09-23T09:08:16Z

StarlitSkies: 3.1.0, plus revised in-line troubleshooting to match the update

{{Lowercase title}}{{Infobox homebrew
| title = ctrcheck
| for3ds = 1
| developers = StarlitSkies, FrozenFire
| version = 3.1.0
| releasedate = 2024-09-23
| website = https://gist.github.com/StarlitSkies/f417c1ded9de8fceffdb532f92823377/ gist.github.com
}}

'''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 release of [https://gist.github.com/StarlitSkies/f417c1ded9de8fceffdb532f92823377/raw/ctrcheck.gm9 ctrcheck.gm9]
** To download, right-click/long-press the page and select <code>Save page as...</code> or similar, then rename the downloaded file to <code>ctrcheck.gm9</code> if it is not already named 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.1.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, then read the results on the top screen once the script finishes
# If you are following this guide at someone else's request, send a picture 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 [[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 [[Media:Luma_v13.0.2_ignore-cfgnor.firm|the]] special build of Luma linked in the fourteenth word of this sentence, rename it to <code>boot.firm</code>, and put it on the root of your SD card
#** 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 [[Get support|Nintendo Homebrew Discord]]
#* One or more of movable.sed, LFCS, SecureInfo, and/or HWCAL is marked as <code>not found</code>, <code>is an invalid size</code>, or <code>data is invalid</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 [[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 [[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 [[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:TWLFix/Manual

2024-09-18T03:52:25Z

StarlitSkies: all TWLFixes are now included in 3DS:DSU, so these pages are redundant - they now redirect to it

#REDIRECT [[3DS:DSU]]