Toggle search
Toggle menu
412
310
489
11.9K
Hacks Guide Wiki
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

3DS:Bannerbomb3/Installing boot9strap (Fredtool) and 3DS:Error screens/Luma3DS ErrDisp: Difference between pages

From Hacks Guide Wiki
More actions
(Difference between pages)
VisualWikitext
No edit summary
 
Ajl721 (talk | contribs)
Approver
75 edits
Corrupt or faulty update data can cause error code 0xc960454?, also made some spelling/grammar corrections.
 
Line 1: Line 1:
{{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]].


== What you need ==
This page lists various causes and solutions of Luma3DS ErrDisp errors.


* Your <code>movable.sed</code> file completing Seedminer or nimhax
==Reading a Luma3DS ErrDisp==
* The latest release of [https://github.com/zoogie/b9sTool/releases/download/v6.0.1/release_6.0.1.zip Luma3DS] (the Luma3DS <code>.zip</code> file)
* The latest release of [https://github.com/zoogie/Frogminer/releases/download/v1.0/Frogminer_save.zip Frogminer_save] (direct download)
* One of the following:
** System version 11.15.0: The 6.0.1 release of [https://github.com/zoogie/b9sTool/releases/download/v6.0.1/release_6.0.1.zip b9stool] (direct download)
** System version 11.16.0: The 6.1.1 release of [https://github.com/zoogie/b9sTool/releases/download/v6.1.1/release_6.1.1.zip b9stool] (direct download)


=== Section I - CFW Check ===
A Luma3DS ErrDisp error has several parts, but only two of them help in finding its cause. They are as follows:
As an additional safety measure, we will perform an additional check for custom firmware. This is because using this method when custom firmware is already installed has a risk of bricking the console (rendering it unusable without recovery methods like ntrboot).
[[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.


# Power off your device
==Known errors==
# Hold the (Select) button
# Power on your device while still holding the (Select) button
# If the check was successful, you will boot to the HOME Menu and you may proceed with this guide
# Power off your device
{{Warning
| text = If you see a configuration menu or the console immediately powers off, you already have CFW, and continuing with these instructions may BRICK your device! Follow Checking for CFW to upgrade your existing CFW.
}}


=== Section II - BannerBomb3 ===
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.


In this section, you will trigger the BannerBomb3 exploit using the DSiWare Management menu and copy the resulting file dump to your computer so that you can use it on the next section.
----


# Reinsert your SD card into your device
{| class="wikitable" style="margin: auto"
# Power on your device
! style="font-size:125%;" | Process Name
# Launch System Settings on your device
! style="font-size:125%;" | Problem & Solution
# Navigate to <code>Data Management</code> -> <code>DSiWare</code>-> <code>SD Card</code>
|-
#* Your device should show the BB3 multihax menu
| process: '''cam'''<br>process: '''qtm'''
#* If this step causes your device to crash, [3dsguide:troubleshooting#installing-boot9strap-fredtool|follow this troubleshooting guide]
| Your camera's hardware is damaged or dead.
# Use the D-Pad to navigate and press the (A) button to select "Dump DSiWare"
: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.
#* Your device will automatically reboot
: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.
# Power off your device
|-
| 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: '''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.
|-
| 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.
|}


=== Section III - Prep Work ===
{{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]].
|-
|0xC8A11BEF
|Occurs when attempting to use DLP services with an out-of-region game. This issue is not fixable currently.
|-
| 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.
|-
| 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.
|-
| 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.<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.
|-
| 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.


# Insert your SD card into your computer
|-
# Open the [https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec DSIHaxInjector_new] website on your computer
| 0xC92044EB<br>0xC92044FA<br>0xC960454?
# Under the “Username” field, enter any alphanumeric name (no spaces or special characters)
| Your SD card is set to read-only or is faulty.
#* You might want to put in a different name to differentiate it from BannerBomb3’s output
: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.
# Under the “DSiBin” field, upload your <code>42383841.bin</code> file using the first “Browse…” option
: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.
# Under the “MovableSed” field, upload your <code>movable.sed</code> file using the second “Browse…” option
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.
# Under the “InjectionTarget” field, set the injection target to <code>DSinternet</code>(NOT memorypit)
|-
# Click “Build”
| 0xD8E0806A
#* Wait a few seconds for the build process to complete
| You have developer UNITINFO enabled and are trying to install a retail game.
# In the Build History section on the left, type the Username into the “Filter Builds” field
:To fix, go into the file <code>sd:/luma/config.ini</code> and set the variable <code>use_dev_unitinfo</code> to 0.
# Click on the first search result
|-
#* This result should have the latest timestamp
| 0xD860446?
# Click the “output_(name).zip” link
| You are attempting to use more processing power than the console currently has available.
# Navigate to <code>Nintendo 3DS</code> -> <code><ID0></code> -> <code><ID1></code> -> <code>Nintendo DSiWare</code> on your SD card
: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.
# Delete <code>F00D43D5.bin</code> from your Nintendo DSiWare folder
|-
# Copy the <code>42383841.bin</code> file from the <code>hax</code> folder of the downloaded DSiWare archive (output_(name).zip) to the <code>Nintendo DSiWare</code> folder
| 0xD900458?
# Copy `boot.firm` and `boot.3dsx` from the Luma3DS `.zip` to the root of your SD card
| The app you tried to open, its savedata, or an update file for it is corrupted.
#* 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
: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.
# Copy `boot.nds` (B9STool) from the release `.zip` to the root of your SD card
|-
# Copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card
| {{anchor|0xF9605002}}0xF9605002
# Reinsert your SD card into your device
| If attempting to use any camera features, your camera hardware is damaged or dead.
# Power on your device
|}


=== Section IV - Overwriting DS Connection Settings ===
[[Category:Unbricking]]
 
In this section, you will copy the hacked DS Connection Settings DSiWare to internal memory, which will temporarily replace it with Flipnote Studio.
 
# Launch System Settings on your device
# Navigate to <code>Data Management</code> -> <code>DSiWare</code>
# Under the “SD Card” section, select the “Haxxxxxxxxx!” title
# Select “Copy”, then select “OK”
# Exit System Settings
# Return to main menu of the System Settings
# Navigate to <code>Internet Settings</code> -> <code>Nintendo DS Connections</code>, then select “OK” (image)
# If the exploit was successful, your 3DS will have loaded into the JPN version of Flipnote Studio
 
=== Section V - Flipnote Exploit ===
If you would prefer a visual guide to this section, one is available [https://zoogie.github.io/web/flipnote_directions/ here].
 
In this section, you will perform a series of very specific steps within Flipnote Studio that, when performed correctly, will launch the boot9strap (custom firmware) installer.
 
# Complete the initial setup process for the launched game until you reach the main menu
#* Select the left option whenever prompted during the setup process
# Using the touch-screen, select the large left box, then select the box with an SD card icon
# Once the menu loads, select the face icon, then the bottom right icon to continue
# Press (X) or (UP) on the D-Pad depending on which is shown on the top screen
# Select the second button along the top with a film-reel icon
# Scroll right until reel “3/3” is selected
# Tap the third box with the letter “A” in it
# Scroll left until reel “1/3” is selected
# Tap the fourth box with the letter “A” in it
# If the exploit was successful, your device will have loaded b9sTool
# Using the D-Pad, move to “Install boot9strap”
#* If you miss this step, the system will exit to HOME Menu instead of installing boot9strap and you will need to open Nintendo DS Connections and start over from the beginning of this section
# Press (A), then press START and SELECT at the same time to begin the process
# Once completed and the bottom screen says “done.”, exit b9sTool, then power off your device
#* You may have to force power off by holding the power button
#* If your device shuts down when you try to power it on, ensure that you have copied <code>boot.firm</code> from the Luma3DS <code>.zip</code> to the root of your SD card
#* If you see the Luma Configuration screen, power off your device and continue to the next section
 
=== Section VI - Luma3DS Configuration ===
 
# Press and hold (Select), and while holding (Select), power on your device. This will launch Luma3DS configuration
#* Luma3DS configuration menu are settings for the Luma3DS custom firmware. Many of these settings may be useful for customization or debugging
#* For the purpose of this guide, these settings will be left on default settings
#* If you boot to HOME Menu, follow this troubleshooting guide
# Press (Start) to save and reboot
# Power off your device
 
{{ Luma3DS is default }}
 
=== Section VII - Restoring DS Internet ===
 
# Insert your SD card into your computer
# Navigate to <code>Nintendo 3DS</code> -> <code><ID0></code> -> <code><ID1></code> -> <code>Nintendo DSiWare</code> on your SD card
# Copy the <code>484E4441.bin</code>  file from the <code>clean</code> folder of the downloaded DSiWare archive (output_(name).zip) to the <code>Nintendo DSiWare</code> folder
# 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>
# Under the “SD Card” section, select the “Haxxxxxxxxx!” title
# Select “Copy”, then select “OK”
# Exit System Settings
# Power off your device
 
<span style="font-size:200%;">Continue to [[3dsguide:finalizing-setup|Finalizing Setup]]</span>
Retrieved from "https://wiki.hacks.guide/wiki/3DS:Bannerbomb3/Installing_boot9strap_(Fredtool)"