|
|
| Line 1: |
Line 1: |
| {{shortcut|3DS:EXCEPTION}}
| | ==Required Reading== |
| 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 usually result from 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 often related to broken software or user data.
| |
| * '''Exception type:''' How the system is causing the exception. These categories are often too broad to be helpful, but three of them are more precise:
| |
| **'''data abort''': Oftentimes related to a broken mod or broken HOME Menu data. Occasionally related to custom firmware data being broken.
| |
| **'''prefetch abort (svcBreak)''': Oftentimes an issue with data on the NAND, even when Arm11. Can also happen when launching an out-of-region game.
| |
| **'''undefined instruction''': Usually either a broken piece of software (if not on boot) or outdated <code>boot.firm</code> (if on boot).
| |
| *'''Fault status:''' Why the system is causing the exception. Normally not helpful except for developers.
| |
| *'''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 you last tried to open has an issue.
| |
| **'''nwm''': Networking services, almost always WiFi.
| |
| **'''ns''': The <u>N</u>intendo User Interface <u>S</u>hell, which handles all apps/processes in 3DS mode.
| |
| *'''R0''': Usually just internal data that's not worth reading. There are two notable exceptions, however:
| |
| **'''Arm11 loader exception''': If R0's contents start with a C or D, R0 is an error code. This code usually gives the exact cause of the issue.
| |
| **'''Arm11 pm exception''': If R0's contents are <code>E0E01BF5</code>, <code>boot.firm</code> is guaranteed to be too outdated to work.
| |
|
| |
|
| ==Known Errors==
| | [https://github.com/zoogie/Bannerbomb3 Bannerbomb3] is an exploit for the DSiWare Management Menu, compatible with system versions 11.16 and lower for all regions excluding the iQue 3DS since it doesn't have that menu. The main developer is [https://github.com/zoogie zoogie]. |
| 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/nintendohomebrew Nintendo Homebrew Discord]] for further assistance.}}
| |
| ----
| |
|
| |
|
| === <big>Arm9</big> ===
| | It's the main primary exploit used on the [https://3ds.hacks.guide/ main guide], unSAFE_MODE and BB3('''B'''anner'''b'''omb'''3''')+Fredtool both use it. It can be used to prepare the secondary exploits [https://github.com/zoogie/unSAFE_MODE unSAFE_MODE] or [https://github.com/zoogie/menuhax67 menuhax67], both made by the legend [https://github.com/zoogie zoogie]. This page covers preparing menuhax67 to access the Homebrew Launcher since accessing the Homebrew Launcher from Bannerbomb3 directly is not possible. On the next page you will find out how to access the Homebrew Launcher with menuhax67. Note that with a crashing DSiWare Management Menu, this method won't work. |
| Arm9 errors are sorted by their '''exception type'''.
| |
|
| |
|
| <span style="font-size:175%; display:flex; justify-content:center "><h4>Error On Boot</h4></span>
| | The instructions described here only work with EUR/USA/JPN/KOR, if you want to use Taiwan for some odd reason, no you don't want that, use the normal guide instead to install custom firmware. |
| {| class="wikitable" style="margin: auto"
| |
| ! style="font-size:95%;" | Exception Type
| |
| ! style="font-size:95%;" | Problem & Solution
| |
| |-
| |
| | rowspan="3" | <h5>Any Type</h5>
| |
| | Files on the SD are corrupted.
| |
| :To fix, [[Checking_SD_card_integrity|verify that your 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>.
| |
| |-
| |
| | rowspan="2" | <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]].<br>If this does not work, perform a [[3DS:CTRTransfer|CTRTransfer]].
| |
| |-
| |
| | rowspan="2" | <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.
| |
| |-
| |
| | <h5>prefetch abort (kernel panic)</h5>
| |
| | The console likely has a hardware issue.
| |
| |-
| |
| | <h5>undefined instruction</h5>
| |
| | The console likely has a hardware issue.
| |
| |}
| |
|
| |
|
| <span style="font-size:175%; display:flex; justify-content:center"><h4>Error During Use</h4></span>
| | ==What you need== |
| {| class="wikitable" style="margin: auto"
| |
| ! style="font-size:95%;" | Exception Type
| |
| ! style="font-size:95%;" | Problem & Solution
| |
| |-
| |
| | <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> ===
| | *The latest version of [https://github.com/LumaTeam/Luma3DS/releases/latest Luma3DS] (the Luma3DS <code>.zip</code> file) |
| All Arm11 errors are sorted by their '''current process'''.
| | *The latest version of [https://github.com/zoogie/Bannerbomb3/releases/latest Bannerbomb3] (the Release <code>.zip</code> file) |
| | *Your <code>movable.sed</code> file from completing [[3dsguide:seedminer|Seedminer]] |
| | *The latest version of [https://github.com/zoogie/menuhax67/releases/latest menuhax67] (the menuhax67 <code>.zip</code> file) |
|
| |
|
| <span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>
| | ==Instructions== |
| {| class="wikitable" style="margin: auto"
| |
| ! style="font-size:95%;" | Current Process
| |
| ! style="font-size:95%;" | Exception Type
| |
| ! style="font-size:95%;" | Problem & Solution
| |
| |-
| |
| | <h5>boss</h5> || data abort
| |
| | 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>fs</h5> || any
| |
| | Can be anything from SD card problems to hardware issues.
| |
| |-
| |
| | <h5>hid</h5> || any
| |
| | Potential hardware problems.
| |
| |-
| |
| | <h5>ic2/spi</h5> || any
| |
| | The console has a serious hardware issue that likely is not easily fixable.
| |
| :Join [https://discord.gg/C29hYvh the Nintendo Homebrew Discord] and ask, in English, for help.
| |
| |-
| |
| |-
| |
| | <h5>mset</h5> || any
| |
| | 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>
| |
| | data abort
| |
| | Your HOME Menu has an Albanian virus and is trying to delete itself.
| |
| :Help it by opening SafeMode9 on your 3DS and then throwing a brick at the console.
| |
| |-
| |
| | <h5>ns</h5> || prefetch abort (svcBreak)
| |
| | The [[3DS:Luma3DS/Configuration|Luma configuration]] setting <code>Autoboot Homebrew</code> is set to boot to a title that does not exist.
| |
| :To fix, disable the option or install an application that matches the title ID set in <code>sd:/luma/config.ini</code>.
| |
| |-
| |
| | <h5>nwm</h5> || any
| |
| | 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>pm</h5> || undefined instruction
| |
| | 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>
| | ===Section I - Prep Work=== |
| {| class="wikitable" style="margin: auto"
| |
| ! style="font-size:95%;" | Current Process
| |
| ! style="font-size:95%;" | Exception Type
| |
| ! style="font-size:95%;" | Problem & Solution
| |
| |-
| |
| | <h5>3dsx_app</h5> || any
| |
| | The <code>.3dsx</code> file you opened is corrupted.
| |
| :To fix, download a new copy of the <code>.3dsx</code> file. If this error happens when you open the Homebrew Launcher, download a new copy of <code>boot.3dsx</code>.
| |
| ::If the error still happens, [[Checking SD card integrity|test your SD for errors.]]
| |
| |-
| |
| | <h5>app/CtrApp</h5> || any
| |
| | The app you last 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.
| |
| |-
| |
| | <h5>GARDEN</h5> || any
| |
| | 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> || any
| |
| | Can be anything from SD card problems to hardware issues.
| |
| |-
| |
| | <h5>Kujira/Joker/niji_loc</h5> || any
| |
| | The app you last 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|force the game to use the correct region.]]
| |
| ::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> || undefined instruction
| |
| | The app you last opened has an issue. If the contents of R0 start with C or D, R0 is an error code.<br>
| |
| :Most of the possible error codes for this are also listed on [[3DS:Error_screens/Luma3DS_ErrDisp|this page]].
| |
| |-
| |
| | <h5>mset</h5> || any
| |
| | 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.
| |
| |-
| |
| | <h5>nwm</h5> || any
| |
| | 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>qtm/cam</h5> || any
| |
| | 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.
| |
| |-
| |
| |}
| |
|
| |
|
| | #Insert the SD card of your '''target 3DS''' in your computer |
| | #Copy <code>boot.firm</code> and <code>boot.3dsx</code> from the Luma3DS <code>.zip</code> to the root of your SD card |
| | #*The root of the SD card refers to the initial directory on your SD card where you can see the Nintendo 3DS folder, but are not inside of it |
| | #Copy the <code>Launcher.dat</code> for your region/version from the Release <code>.zip</code> to the root of your SD card |
| | #Copy the bb3.bin from the Release <code>.zip</code> to the root of your SD card |
|
| |
|
| [[Category:Unbricking]] | | ===Section II - Bannerbomb3 Prep=== |
| {{Short description|Guide to the CFW error handler}}
| | |
| | ====Section II, Part I - F00D43D5.bin generation==== |
| | |
| | # Open the [http://3dstools.nhnarwhal.com/#/bb3gen BannerBomb3 multitool Injector website] on your computer |
| | # Upload your movable.sed using the “Choose File” option |
| | # Click “Build and Download” |
| | |
| | ====Section II, Part II - F00D43D5.bin placement==== |
| | |
| | #Navigate to <code>Nintendo 3DS</code> -> <code><ID0></code> -> <code><ID1></code> on your SD card |
| | #*The <code><ID0></code> will be the same one that you used in Seedminer |
| | #*The <code><ID1></code> is a 32 character long folder inside of the <code><ID0></code> |
| | #Create a folder named <code>Nintendo DSiWare</code> inside of the <code><ID1></code> |
| | #*If you already had the folder ''and'' there are any existing DSiWare backup files (<code><8-character-id>.bin</code>) inside, copy them to your PC and then remove them from your SD card |
| | #Copy the <code>F00D43D5.bin</code> file from <code>DSIWARE_EXPLOIT.zip</code> to the <code>Nintendo DSiWare</code> |
| | |
| | ===Section III - Bannerbomb3=== |
| | |
| | #Reinsert your SD card into your device |
| | #Power on your device |
| | #Launch System Settings on your device |
| | #Navigate to <code>Data Management</code> -> <code>DSiWare</code> -> <code>SD Card</code> |
| | #Select <code>Install *HAX</code> |
| | |
| | ----- |
| | |
| | <span style="font-size:200%;">Continue to [[3DS:Alternate_Exploits/menuhax67#Using_menuhax67 | menuhax67]]</span> |
| | |
| | [[Category:Nintendo 3DS guides]] |
