New Crowdin updates (#2162)
* New translations a9lh-to-b9s.txt (Arabic) * New translations uninstall-cfw.txt (Arabic) * New translations installing-boot9strap-(fredtool).txt (Arabic) * New translations seedminer.txt (Arabic) * New translations installing-boot9strap-(usm).txt (Arabic) * New translations checking-for-cfw.txt (Arabic) * New translations faq.txt (Bulgarian) * New translations move-emunand.txt (Bulgarian) * New translations troubleshooting.txt (Bulgarian) * New translations finalizing-setup.txt (Bulgarian) * New translations a9lh-to-b9s.txt (Bulgarian) * New translations uninstall-cfw.txt (Bulgarian) * New translations installing-boot9strap-(fredtool).txt (Bulgarian) * New translations seedminer.txt (Bulgarian) * New translations installing-boot9strap-(usm).txt (Bulgarian) * New translations checking-for-cfw.txt (Bulgarian) * New translations faq.txt (Catalan) * New translations move-emunand.txt (Catalan) * New translations troubleshooting.txt (Catalan) * New translations finalizing-setup.txt (Catalan) * New translations a9lh-to-b9s.txt (Catalan) * New translations uninstall-cfw.txt (Catalan) * New translations installing-boot9strap-(fredtool).txt (Catalan) * New translations seedminer.txt (Catalan) * New translations installing-boot9strap-(usm).txt (Catalan) * New translations checking-for-cfw.txt (Catalan) * New translations faq.txt (Czech) * New translations move-emunand.txt (Czech) * New translations troubleshooting.txt (Czech) * New translations finalizing-setup.txt (Czech) * New translations a9lh-to-b9s.txt (Czech) * New translations uninstall-cfw.txt (Czech) * New translations installing-boot9strap-(fredtool).txt (Czech) * New translations seedminer.txt (Czech) * New translations installing-boot9strap-(usm).txt (Czech) * New translations checking-for-cfw.txt (Czech) * New translations faq.txt (Greek) * New translations move-emunand.txt (Greek) * New translations troubleshooting.txt (Greek) * New translations finalizing-setup.txt (Greek) * New translations a9lh-to-b9s.txt (Greek) * New translations uninstall-cfw.txt (Greek) * New translations installing-boot9strap-(fredtool).txt (Greek) * New translations seedminer.txt (Greek) * New translations installing-boot9strap-(usm).txt (Greek) * New translations checking-for-cfw.txt (Greek) * New translations faq.txt (Finnish) * New translations move-emunand.txt (Finnish) * New translations troubleshooting.txt (Finnish) * New translations finalizing-setup.txt (Finnish) * New translations a9lh-to-b9s.txt (Finnish) * New translations uninstall-cfw.txt (Finnish) * New translations installing-boot9strap-(fredtool).txt (Finnish) * New translations seedminer.txt (Finnish) * New translations installing-boot9strap-(usm).txt (Finnish) * New translations checking-for-cfw.txt (Finnish) * New translations faq.txt (Hebrew) * New translations move-emunand.txt (Hebrew) * New translations troubleshooting.txt (Hebrew) * New translations finalizing-setup.txt (Hebrew) * New translations a9lh-to-b9s.txt (Hebrew) * New translations uninstall-cfw.txt (Hebrew) * New translations installing-boot9strap-(fredtool).txt (Hebrew) * New translations seedminer.txt (Hebrew) * New translations installing-boot9strap-(usm).txt (Hebrew) * New translations checking-for-cfw.txt (Hebrew) * New translations faq.txt (Hungarian) * New translations move-emunand.txt (Hungarian) * New translations troubleshooting.txt (Hungarian) * New translations finalizing-setup.txt (Hungarian) * New translations a9lh-to-b9s.txt (Hungarian) * New translations uninstall-cfw.txt (Hungarian) * New translations installing-boot9strap-(fredtool).txt (Hungarian) * New translations seedminer.txt (Hungarian) * New translations installing-boot9strap-(usm).txt (Hungarian) * New translations checking-for-cfw.txt (Hungarian) * New translations troubleshooting.txt (Italian) * New translations finalizing-setup.txt (Italian) * New translations installing-boot9strap-(fredtool).txt (Italian) * New translations seedminer.txt (Italian) * New translations faq.txt (Japanese) * New translations move-emunand.txt (Japanese) * New translations troubleshooting.txt (Japanese) * New translations finalizing-setup.txt (Japanese) * New translations a9lh-to-b9s.txt (Japanese) * New translations uninstall-cfw.txt (Japanese) * New translations installing-boot9strap-(fredtool).txt (Japanese) * New translations seedminer.txt (Japanese) * New translations installing-boot9strap-(usm).txt (Japanese) * New translations checking-for-cfw.txt (Japanese) * New translations faq.txt (Korean) * New translations move-emunand.txt (Korean) * New translations troubleshooting.txt (Korean) * New translations finalizing-setup.txt (Korean) * New translations a9lh-to-b9s.txt (Korean) * New translations uninstall-cfw.txt (Korean) * New translations installing-boot9strap-(fredtool).txt (Korean) * New translations seedminer.txt (Korean) * New translations installing-boot9strap-(usm).txt (Korean) * New translations checking-for-cfw.txt (Korean) * New translations move-emunand.txt (Dutch) * New translations finalizing-setup.txt (Dutch) * New translations a9lh-to-b9s.txt (Dutch) * New translations uninstall-cfw.txt (Dutch) * New translations installing-boot9strap-(fredtool).txt (Dutch) * New translations seedminer.txt (Dutch) * New translations installing-boot9strap-(usm).txt (Dutch) * New translations checking-for-cfw.txt (Dutch) * New translations faq.txt (Norwegian) * New translations move-emunand.txt (Norwegian) * New translations troubleshooting.txt (Norwegian) * New translations finalizing-setup.txt (Norwegian) * New translations a9lh-to-b9s.txt (Norwegian) * New translations uninstall-cfw.txt (Norwegian) * New translations installing-boot9strap-(fredtool).txt (Norwegian) * New translations seedminer.txt (Norwegian) * New translations installing-boot9strap-(usm).txt (Norwegian) * New translations checking-for-cfw.txt (Norwegian) * New translations faq.txt (Polish) * New translations move-emunand.txt (Polish) * New translations troubleshooting.txt (Polish) * New translations finalizing-setup.txt (Polish) * New translations a9lh-to-b9s.txt (Polish) * New translations uninstall-cfw.txt (Polish) * New translations installing-boot9strap-(fredtool).txt (Polish) * New translations seedminer.txt (Polish) * New translations installing-boot9strap-(usm).txt (Polish) * New translations checking-for-cfw.txt (Polish) * New translations faq.txt (Portuguese) * New translations move-emunand.txt (Portuguese) * New translations troubleshooting.txt (Portuguese) * New translations finalizing-setup.txt (Portuguese) * New translations a9lh-to-b9s.txt (Portuguese) * New translations uninstall-cfw.txt (Portuguese) * New translations installing-boot9strap-(fredtool).txt (Portuguese) * New translations seedminer.txt (Portuguese) * New translations installing-boot9strap-(usm).txt (Portuguese) * New translations checking-for-cfw.txt (Portuguese) * New translations faq.txt (Russian) * New translations move-emunand.txt (Russian) * New translations troubleshooting.txt (Russian) * New translations finalizing-setup.txt (Russian) * New translations a9lh-to-b9s.txt (Russian) * New translations uninstall-cfw.txt (Russian) * New translations installing-boot9strap-(fredtool).txt (Russian) * New translations seedminer.txt (Russian) * New translations installing-boot9strap-(usm).txt (Russian) * New translations checking-for-cfw.txt (Russian) * New translations faq.txt (Swedish) * New translations move-emunand.txt (Swedish) * New translations troubleshooting.txt (Swedish) * New translations finalizing-setup.txt (Swedish) * New translations a9lh-to-b9s.txt (Swedish) * New translations uninstall-cfw.txt (Swedish) * New translations installing-boot9strap-(fredtool).txt (Swedish) * New translations seedminer.txt (Swedish) * New translations installing-boot9strap-(usm).txt (Swedish) * New translations checking-for-cfw.txt (Swedish) * New translations faq.txt (Turkish) * New translations move-emunand.txt (Turkish) * New translations troubleshooting.txt (Turkish) * New translations finalizing-setup.txt (Turkish) * New translations a9lh-to-b9s.txt (Turkish) * New translations uninstall-cfw.txt (Turkish) * New translations installing-boot9strap-(fredtool).txt (Turkish) * New translations seedminer.txt (Turkish) * New translations installing-boot9strap-(usm).txt (Turkish) * New translations checking-for-cfw.txt (Turkish) * New translations faq.txt (Ukrainian) * New translations move-emunand.txt (Ukrainian) * New translations troubleshooting.txt (Ukrainian) * New translations finalizing-setup.txt (Ukrainian) * New translations a9lh-to-b9s.txt (Ukrainian) * New translations uninstall-cfw.txt (Ukrainian) * New translations installing-boot9strap-(fredtool).txt (Ukrainian) * New translations seedminer.txt (Ukrainian) * New translations installing-boot9strap-(usm).txt (Ukrainian) * New translations checking-for-cfw.txt (Ukrainian) * New translations faq.txt (Chinese Traditional) * New translations move-emunand.txt (Chinese Traditional) * New translations troubleshooting.txt (Chinese Traditional) * New translations finalizing-setup.txt (Chinese Traditional) * New translations a9lh-to-b9s.txt (Chinese Traditional) * New translations uninstall-cfw.txt (Chinese Traditional) * New translations installing-boot9strap-(fredtool).txt (Chinese Traditional) * New translations seedminer.txt (Chinese Traditional) * New translations installing-boot9strap-(usm).txt (Chinese Traditional) * New translations checking-for-cfw.txt (Chinese Traditional) * New translations faq.txt (Vietnamese) * New translations move-emunand.txt (Vietnamese) * New translations troubleshooting.txt (Vietnamese) * New translations finalizing-setup.txt (Vietnamese) * New translations a9lh-to-b9s.txt (Vietnamese) * New translations uninstall-cfw.txt (Vietnamese) * New translations installing-boot9strap-(fredtool).txt (Vietnamese) * New translations seedminer.txt (Vietnamese) * New translations installing-boot9strap-(usm).txt (Vietnamese) * New translations checking-for-cfw.txt (Vietnamese) * New translations faq.txt (Portuguese, Brazilian) * New translations move-emunand.txt (Portuguese, Brazilian) * New translations troubleshooting.txt (Portuguese, Brazilian) * New translations finalizing-setup.txt (Portuguese, Brazilian) * New translations a9lh-to-b9s.txt (Portuguese, Brazilian) * New translations uninstall-cfw.txt (Portuguese, Brazilian) * New translations installing-boot9strap-(fredtool).txt (Portuguese, Brazilian) * New translations seedminer.txt (Portuguese, Brazilian) * New translations installing-boot9strap-(usm).txt (Portuguese, Brazilian) * New translations checking-for-cfw.txt (Portuguese, Brazilian) * New translations seedminer.txt (Indonesian) * New translations checking-for-cfw.txt (Indonesian) * New translations faq.txt (Thai) * New translations move-emunand.txt (Thai) * New translations troubleshooting.txt (Thai) * New translations finalizing-setup.txt (Thai) * New translations a9lh-to-b9s.txt (Thai) * New translations uninstall-cfw.txt (Thai) * New translations installing-boot9strap-(fredtool).txt (Thai) * New translations seedminer.txt (Thai) * New translations installing-boot9strap-(usm).txt (Thai) * New translations checking-for-cfw.txt (Thai) * New translations faq.txt (Croatian) * New translations move-emunand.txt (Croatian) * New translations troubleshooting.txt (Croatian) * New translations finalizing-setup.txt (Croatian) * New translations a9lh-to-b9s.txt (Croatian) * New translations uninstall-cfw.txt (Croatian) * New translations installing-boot9strap-(fredtool).txt (Croatian) * New translations seedminer.txt (Croatian) * New translations installing-boot9strap-(usm).txt (Croatian) * New translations checking-for-cfw.txt (Croatian) * New translations faq.txt (Malay) * New translations move-emunand.txt (Malay) * New translations troubleshooting.txt (Malay) * New translations finalizing-setup.txt (Malay) * New translations a9lh-to-b9s.txt (Malay) * New translations uninstall-cfw.txt (Malay) * New translations installing-boot9strap-(fredtool).txt (Malay) * New translations seedminer.txt (Malay) * New translations installing-boot9strap-(usm).txt (Malay) * New translations checking-for-cfw.txt (Malay) * New translations faq.txt (Pirate English) * New translations move-emunand.txt (Pirate English) * New translations troubleshooting.txt (Pirate English) * New translations finalizing-setup.txt (Pirate English) * New translations a9lh-to-b9s.txt (Pirate English) * New translations uninstall-cfw.txt (Pirate English) * New translations installing-boot9strap-(fredtool).txt (Pirate English) * New translations seedminer.txt (Pirate English) * New translations installing-boot9strap-(usm).txt (Pirate English) * New translations checking-for-cfw.txt (Pirate English)
This commit is contained in:
ihaveahax
GitHub
parent
ca6c5f5dfe
commit
93d0639f30
320 changed files with 16096 additions and 7388 deletions
|
|
@ -64,7 +64,7 @@ For all steps in this section, overwrite any existing files on your SD card.
|
|||
1. Your device should have rebooted into the Luma3DS configuration menu
|
||||
+ Luma3DS configuration menu are settings for the Luma3DS custom firmware. Many of these settings may be useful for customization or debugging
|
||||
+ For the purpose of this guide, these settings will be left on default settings
|
||||
+ If you get a black screen, [follow this troubleshooting guide](troubleshooting#boot-related-issues-on-modded-devices)
|
||||
+ If you get a black screen, [follow this troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware)
|
||||
1. Press (Start) to save and reboot
|
||||
|
||||
___
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ This is an add-on section to check if your console already has a modern custom f
|
|||
|
||||
If your console already has an arm9loaderhax or boot9strap based custom firmware, you will need to follow the instructions indicated to upgrade your setup to a modern one.
|
||||
|
||||
If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#clear-home-menu-extdata), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
|
||||
If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#other-troubleshooting), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
|
||||
{: .notice--info}
|
||||
|
||||
### Instructions
|
||||
|
|
|
|||
|
|
@ -14,79 +14,173 @@ title: "FAQ"
|
|||
|
||||
## Pre-Installation FAQ
|
||||
|
||||
#### **Q:** *I am on the latest system version. Is my device hackable without any external hardware?*
|
||||
**A:** Yes! The latest firmware (11.16.0) has a free method for getting CFW named [Seedminer](seedminer).
|
||||
{% capture compat %}
|
||||
<summary><u>I am on the latest system version. Is my device hackable without any external hardware?</u></summary>
|
||||
|
||||
#### **Q:** *What devices is this guide compatible with?*
|
||||
**A:** The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. If your system version string displays as "0.0.0-0", then you may have a developer unit.
|
||||
Yes! The latest firmware (11.16.0) has a free method for getting CFW named [Seedminer](seedminer).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How risky is hacking my console?*
|
||||
**A:** Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
{% capture compat %}
|
||||
<summary><u>What devices is this guide compatible with?</u></summary>
|
||||
|
||||
#### **Q:** *Can I run awesome homebrew and emulators with this?*
|
||||
**A:** Yes! This guide will install a few useful homebrew applications, including [Universal-Updater](https://github.com/Universal-Team/Universal-Updater/releases/latest), which acts as a homebrew app store.
|
||||
The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. If your system version string displays as "0.0.0-0", then you may have a developer unit.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I use this to play games from other regions?*
|
||||
**A:** Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Some games may need to make use of Luma's [locale emulation feature](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) in order to work properly on out-of-region devices.
|
||||
{% capture compat %}
|
||||
<summary><u>How risky is hacking my console?</u></summary>
|
||||
|
||||
#### **Q:** *Will I lose any features if I install CFW?*
|
||||
**A:** No. Devices with custom firmware can still use the eShop and run physical cartridges as any other 3DS can.
|
||||
Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I keep my NNID?*
|
||||
**A:** Your NNID (if you have one) will not be affected by this guide. Devices with a region of KOR, CHN, or TWN do not have NNID functionality to begin with and are thus unaffected.
|
||||
{% capture compat %}
|
||||
<summary><u>Can I run awesome homebrew and emulators with this?</u></summary>
|
||||
|
||||
#### **Q:** *Will my 3DS be banned for having CFW?*
|
||||
**A:** There was a ban wave in May 2017 that banned CFW users from online play (eShop access, NNIDs, and Nintendo Accounts were unaffected), seemingly at random. A ban wave at such a scale has not been seen since. That being said, we don't know what Nintendo may have in store in the future. At this time, we don't think that bans are something that you need to worry about.
|
||||
Yes! This guide will install a few useful homebrew applications, including [Universal-Updater](https://github.com/Universal-Team/Universal-Updater/releases/latest), which acts as a homebrew app store.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I do this without a computer (e.g. an Android phone)?*
|
||||
**A:** All you need is the ability to put files on a compatible SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Can I use this to play games from other regions?</u></summary>
|
||||
|
||||
#### **Q:** *What size SD card can I use?*
|
||||
**A:** You will need at least 1.5GB of free SD card space to follow this guide in its entirety. While the 3DS is officially compatible with SD cards up to 32GB, larger SD cards can be used if they are manually re-formatted as FAT32. It is not recommended to use SD cards greater than 128GB due to known issues with GBA graphics and custom themes.
|
||||
Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Some games may need to make use of Luma's [locale emulation feature](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) in order to work properly on out-of-region devices.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *I heard about this thing I have to pay for (Gateway, Sky3DS, ntrboot, R4, etc). Is that something I need?*
|
||||
**A:** No. Custom firmware can be installed for free on the latest firmware without any hardware devices. In fact, 3DS-mode flashcarts like Gateway and Sky3DS are not recommended because they are obsolete and may carry ban or brick risk.
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose any features if I install CFW?</u></summary>
|
||||
|
||||
#### **Q:** *What's the difference between custom firmware and homebrew access?*
|
||||
**A:** Historically, the 3DS used to have userland homebrew access through older exploits like ninjhax. The level of system access granted with userland allowed you to run basic homebrew and emulators but did not allow you to (easily) modify games or dump cartridges. It was also a lot less stable, with homebrew often ungracefully crashing and requiring a full reboot. Custom firmware grants a far greater level of system access while also being more stable than homebrew-only entrypoints.
|
||||
No. Devices with custom firmware can still use the eShop and run physical cartridges as any other 3DS can.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I keep my NNID?</u></summary>
|
||||
|
||||
Your NNID (if you have one) will not be affected by this guide. Devices with a region of KOR, CHN, or TWN do not have NNID functionality to begin with and are thus unaffected.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will my 3DS be banned for having CFW?</u></summary>
|
||||
|
||||
There was a ban wave in May 2017 that banned CFW users from online play (eShop access, NNIDs, and Nintendo Accounts were unaffected), seemingly at random. A ban wave at such a scale has not been seen since. That being said, we don't know what Nintendo may have in store in the future. At this time, we don't think that bans are something that you need to worry about.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I do this without a computer (e.g. an Android phone)?</u></summary>
|
||||
|
||||
Yes! All you need is the ability to put files on a compatible SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What size SD card can I use?</u></summary>
|
||||
|
||||
You will need at least 1.5GB of free SD card space to follow this guide in its entirety. While the 3DS is officially compatible with SD cards up to 32GB, larger SD cards can be used if they are manually re-formatted as FAT32. It is not recommended to use SD cards greater than 128GB due to known issues with GBA graphics and custom themes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>I heard about this thing I have to pay for (Gateway, Sky3DS, ntrboot, R4, etc). Is that something I need?</u></summary>
|
||||
|
||||
No. Custom firmware can be installed for free on the latest firmware without any hardware devices. In fact, 3DS-mode flashcarts like Gateway and Sky3DS are not recommended because they are obsolete and may carry ban or brick risk.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What's the difference between custom firmware and homebrew?</u></summary>
|
||||
|
||||
Historically, the 3DS used to have userland homebrew access through older exploits like ninjhax. The level of system access granted with userland allowed you to run basic homebrew and emulators but did not allow you to (easily) modify games or dump cartridges. It was also a lot less stable, with homebrew often ungracefully crashing and requiring a full reboot. Custom firmware grants a far greater level of system access while also being more stable than homebrew-only entrypoints.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Post-Installation FAQ
|
||||
|
||||
#### **Q:** *Is it safe to update my 3DS to the latest version with CFW?*
|
||||
**A:** If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. There have been updates in the past that have resulted in Luma3DS crashing on boot, so it is a good idea to wait a couple of hours to ensure that the latest update will not temporarily render the device unusable until Luma3DS is updated. System updates can be performed the same way as they are on a stock 3DS: through System Settings, Safe Mode, or the update prompt when the update is automatically downloaded.
|
||||
{% capture compat %}
|
||||
<summary><u>Is it safe to update my 3DS to the latest version with CFW?</u></summary>
|
||||
|
||||
#### **Q:** *How do I upgrade my SD card?*
|
||||
**A:** Copy and paste your SD card contents to a new SD card formatted as FAT32. For 128GB cards, an allocation size of 65536 is recommended. SD cards larger than 128GB are not recommended due to known issues with GBA graphics and custom themes.
|
||||
If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. There have been updates in the past that have resulted in Luma3DS crashing on boot, so it is a good idea to wait a couple of hours to ensure that the latest update will not temporarily render the device unusable until Luma3DS is updated. System updates can be performed the same way as they are on a stock 3DS: through System Settings, Safe Mode, or the update prompt when the update is automatically downloaded.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I system transfer with CFW?*
|
||||
**A:** Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets for illegitimate titles (homebrew) will not transfer, but the titles can be made to reappear with [faketik](https://github.com/ihaveamac/faketik/releases/latest). Make sure that you do not perform a wireless transfer, as this will delete illegitimate titles. CFW will remain on both consoles.
|
||||
{% capture compat %}
|
||||
<summary><u>How do I upgrade my SD card?</u></summary>
|
||||
|
||||
#### **Q:** *How do I change the system language of a Japanese 3DS?*
|
||||
**A:** The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Note that this is very likely to break the Nintendo eShop on your device, which means you will be unable to update your games whether they are in-region or out-of-region.
|
||||
Copy and paste your SD card contents to a new SD card formatted as FAT32. For 128GB cards, an allocation size of 65536 is recommended. SD cards larger than 128GB are not recommended due to known issues with GBA graphics and custom themes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How do I update homebrew applications?*
|
||||
**A:** It depends on the format of the homebrew application. Generally speaking:
|
||||
{% capture compat %}
|
||||
<summary><u>Can I system transfer with CFW?</u></summary>
|
||||
|
||||
Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets for illegitimate titles (homebrew) will not transfer, but the titles can be made to reappear with [faketik](https://github.com/ihaveamac/faketik/releases/latest). Make sure that you do not perform a wireless transfer, as this will delete illegitimate titles. CFW will remain on both consoles.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I change the system language of a Japanese 3DS?</u></summary>
|
||||
|
||||
The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Note that this is very likely to break the Nintendo eShop on your device, which means you will be unable to update your games whether they are in-region or out-of-region.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I update homebrew applications?</u></summary>
|
||||
|
||||
It depends on the format of the homebrew application. Generally speaking:
|
||||
|
||||
* Homebrew in **CIA format** can be updated by installing the new CIA, which will usually overwrite the old one. If the old CIA is not overwritten, you can delete the old one from Data Management as you would any other 3DS title.
|
||||
* Homebrew in **3DSX format** can be updated by replacing the 3DSX file in `/3ds/` with a fresh copy. If the homebrew application includes additional assets, you may need to place that folder somewhere else. Refer to the documentation of the homebrew application.
|
||||
* For updating Luma3DS, see [this page](restoring-updating-cfw). For updating GodMode9, see [this page](godmode9-usage#updating-godmode9).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How do I update games from outside of my 3DS region?*
|
||||
**A:** You will need to [dump the updates](dumping-titles-and-game-cartridges) from a 3DS that has the updates installed. The Nintendo eShop only contains updates for the console's region (a Japanese 3DS will only have updates for Japanese games).
|
||||
{% capture compat %}
|
||||
<summary><u>How do I update my games?</u></summary>
|
||||
|
||||
#### **Q:** *Help! Something bad happened and now I cannot boot...*
|
||||
**A:** Please look at the [troubleshooting guide](troubleshooting). **Uninstalling CFW when your device is in an unbootable state is not recommended, as it is very likely to lead to a brick**.
|
||||
You can continue to download game updates from the Nintendo eShop, even after the 2023 shutdown.
|
||||
|
||||
If the game is not from the same region as the console, you will need to [dump the updates](dumping-titles-and-game-cartridges) from a 3DS that has the updates installed. The Nintendo eShop only contains updates for the console's region (a Japanese 3DS will only have updates for Japanese games).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Help! Something bad happened and my 3DS won't boot to HOME Menu...</u></summary>
|
||||
|
||||
Please look at the [troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware). **Uninstalling CFW when your device is in an unbootable state is not recommended, as it is very likely to lead to a brick**.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## menuhax / A9LH / Gateway FAQ
|
||||
|
||||
#### **Q:** *I modded my device x years ago. What should I do?*
|
||||
**A:** It is recommended that you upgrade your setup to a modern, boot9strap-based one. Follow the [Checking for CFW](checking-for-cfw) guide to see how to upgrade your setup.
|
||||
{% capture compat %}
|
||||
<summary><u>I modded my device (x) years ago, so it already has some sort of homebrew. What should I do?</u></summary>
|
||||
|
||||
#### **Q:** *My setup works for me. Why should I upgrade it?*
|
||||
**A:** The vast majority of modern homebrew (such as Checkpoint and BootNTR Selector) have only been tested on modern, boot9strap-based setups and may not work entirely (or at all) on older setups based on menuhax, A9LH, or Gateway. In addition, depending on your setup, you may be unable to safely update to the latest firmware. Modern, boot9strap-based setups allow for a greater level of system access than previous hacks, including the ability to dump your console's bootrom.
|
||||
It is recommended that you upgrade your setup to a modern, boot9strap-based one. Follow the [Checking for CFW](checking-for-cfw) guide to see how to upgrade your setup.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Will I lose anything if I upgrade my setup?*
|
||||
**A:** Your old setup (including your EmuNAND, if you have one) can usually be directly migrated to boot9strap with no data loss. If you have data that is particularly important to you, it would be a good idea to make a decrypted backup of your save data before upgrading your setup with a tool like [JKSM](https://github.com/J-D-K/JKSM/releases/tag/12%2F20%2F2018).
|
||||
{% capture compat %}
|
||||
<summary><u>My setup works for me. Why should I upgrade it?</u></summary>
|
||||
|
||||
The vast majority of modern homebrew (such as Checkpoint and BootNTR Selector) have only been tested on modern, boot9strap-based setups and may not work entirely (or at all) on older setups based on menuhax, A9LH, or Gateway. In addition, depending on your setup, you may be unable to safely update to the latest firmware. Modern, boot9strap-based setups allow for a greater level of system access than previous hacks, including the ability to dump your console's bootrom.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose anything if I upgrade my setup?</u></summary>
|
||||
|
||||
Your old setup (including your EmuNAND, if you have one) can usually be directly migrated to boot9strap with no data loss. If you have data that is particularly important to you, it would be a good idea to make a decrypted backup of your save data before upgrading your setup with a tool like [JKSM](https://github.com/J-D-K/JKSM/releases/tag/12%2F20%2F2018).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I move saves from an existing Gateway setup to a more modern setup?</u></summary>
|
||||
|
||||
#### **Q:** *How do I move saves from an existing Gateway setup to a more modern setup?*
|
||||
**A:** See [this thread](https://gbatemp.net/threads/425743/).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@ In this section, you will update your system to the latest version, which is saf
|
|||
+ Updates while using B9S + Luma (what you have) are safe
|
||||
+ The updater may display a message saying "Your system is up to date" instead of updating. This is normal if you are already up to date; continue with the next section
|
||||
+ If this gives you an error, set both your DNS settings and Proxy settings to "auto"
|
||||
+ If this still gives you an error, [follow this troubleshooting guide](troubleshooting#unable-to-update-device)
|
||||
+ If this still gives you an error, [follow this troubleshooting guide](troubleshooting#finalizing-setup)
|
||||
|
||||
#### Section III - Homebrew Launcher
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
|||
1. Launch System Settings on your device
|
||||
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#dsiware-management-menu-crashes-without-showing-bb3-multihax-menu)
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#installing-boot9strap-fredtool)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Dump DSiWare"
|
||||
+ Your device will automatically reboot
|
||||
1. Power off your device
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
|||
1. Launch System Settings on your device
|
||||
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#dsiware-management-menu-crashes-without-showing-bb3-multihax-menu)
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#bannerbomb3)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Install unSAFE_MODE"
|
||||
+ Your device will automatically power off
|
||||
|
||||
|
|
|
|||
|
|
@ -168,7 +168,6 @@ To identify a `<TitleID>.gbavc.sav` file's Title ID, you can get a listing of al
|
|||
1. Reinsert your SD card into your device
|
||||
1. Press (A) to remount your SD card
|
||||
1. Press (Start) to reboot
|
||||
1. If you get a black screen, [follow this troubleshooting guide](troubleshooting#ts_sys_down)
|
||||
|
||||
___
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ In this section, you will get the necessary details from your 3DS that are requi
|
|||
+ If you don't have a `Nintendo 3DS` folder, put your SD card into your 3DS and power it on so that the folder can be created
|
||||
1. Copy the name of the 32-letter folder you see directly inside Nintendo 3DS
|
||||
+ This 32-letter name is system-specific and will be different for each console
|
||||
+ If you see multiple 32-letter folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
|
||||
+ If you see multiple 32-letter folders, follow [these instructions](troubleshooting#seedminer)
|
||||
+ You can ignore the `private` folder if you have it
|
||||
|
||||
![]({{ "/images/screenshots/seedminer/id0-example.png" | absolute_url }})
|
||||
|
|
|
|||
|
|
@ -2,37 +2,69 @@
|
|||
title: "Troubleshooting"
|
||||
---
|
||||
|
||||
{% include toc title="Table of Contents"%}
|
||||
|
||||
This page offers troubleshooting advice for commonly encountered issues. If you are unable to solve your issue with the advice on this page, please join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and describe your issue, including what you have already tried.
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary>Table of Contents</summary>
|
||||
|
||||
Used on multiple pages:
|
||||
* [SafeB9SInstaller](#issues-with-safeb9sinstaller)
|
||||
|
||||
Guide pages:
|
||||
* [Seedminer](#seedminer)
|
||||
* [BannerBomb3](#bannerbomb3)
|
||||
* [Installing boot9strap (USM)](#installing-boot9strap-usm)
|
||||
* [Installing boot9strap (Fredtool)](#installing-boot9strap-fredtool)
|
||||
* [Homebrew Launcher (PicHaxx)](#homebrew-launcher-pichaxx)
|
||||
* [Installing boot9strap (Soundhax)](#installing-boot9strap-soundhax)
|
||||
* [Installing boot9strap (SSLoth-Browser)](#installing-boot9strap-ssloth-browser)
|
||||
|
||||
* [Finalizing Setup](#finalizing-setup)
|
||||
|
||||
Issues after installation:
|
||||
* [Boot issues](#boot-issues-on-devices-with-custom-firmware)
|
||||
* [Software issues](#software-issues-on-devices-with-custom-firmware)
|
||||
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
{: .notice--info}
|
||||
|
||||
## Issues with SafeB9SInstaller
|
||||
|
||||
### SigHaxed FIRM was not installed! Check lower screen for more info.
|
||||
|
||||
#### SigHaxed FIRM - File not found
|
||||
{% capture compat %}
|
||||
<summary><u>SigHaxed FIRM - File not found</u></summary>
|
||||
|
||||
You are missing `boot9strap.firm` and `boot9strap.firm.sha` from the `boot9strap` folder, or the `boot9strap` folder is misnamed. Download the latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip), and place `boot9strap.firm` and `boot9strap.firm.sha` in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### SigHaxed FIRM - invalid FIRM
|
||||
{% capture compat %}
|
||||
<summary><u>SigHaxed FIRM - invalid FIRM</u></summary>
|
||||
|
||||
There is an issue with your `boot9strap.firm` and `boot9strap.firm.sha` files. Re-download the latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip), and place `boot9strap.firm` and `boot9strap.firm.sha` in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Secret Sector - File not found
|
||||
{% capture compat %}
|
||||
<summary><u>Secret Sector - File not found</u></summary>
|
||||
|
||||
You are missing `secret_sector.bin` from the `boot9strap` folder, or the `boot9strap` folder is misnamed. Download [secret_sector.bin](magnet:?xt=urn:btih:15a3c97acf17d67af98ae8657cc66820cc58f655&dn=secret_sector.bin&tr=udp%3a%2f%2ftracker.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.lelux.fi%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.loadbt.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.moeking.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.monitorit4.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.ololosh.space%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.pomf.se%3a80%2fannounce&tr=udp%3a%2f%2ftracker.srv00.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.theoks.net%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.tiny-vps.com%3a6969%2fannounce&tr=udp%3a%2f%2fopen.tracker.cl%3a1337%2fannounce&tr=udp%3a%2f%2ftracker.zerobytes.xyz%3a1337%2fannounce&tr=udp%3a%2f%2ftracker1.bt.moack.co.kr%3a80%2fannounce&tr=udp%3a%2f%2fvibe.sleepyinternetfun.xyz%3a1738%2fannounce&tr=udp%3a%2f%2fwww.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a6969%2fannounce&tr=udp%3a%2f%2f9.rarbg.com%3a2810%2fannounce&tr=udp%3a%2f%2ftracker.opentrackr.org%3a1337%2fannounce&tr=udp%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fopenbittorrent.com%3a80%2fannounce) using a torrent client, and place it in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Something else
|
||||
{% capture compat %}
|
||||
<summary><u>Something else</u></summary>
|
||||
|
||||
Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance, and describe the message that you see.
|
||||
|
||||
---
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Seedminer
|
||||
|
||||
### Multiple long folder names in Nintendo 3DS folder
|
||||
{% capture compat %}
|
||||
<summary><u>Multiple long folder names in Nintendo 3DS folder</u></summary>
|
||||
|
||||
![]({{ "/images/screenshots/multiple-id0.png" | absolute_url }})
|
||||
{: .notice--info}
|
||||
|
|
@ -49,98 +81,285 @@ This occurs when you use your SD card in multiple 3DS devices and is intended to
|
|||
+ This is your true ID0 that you will use in [Section II of Seedminer](seedminer#section-ii---seedminer)
|
||||
1. Delete the `Nintendo 3DS` folder
|
||||
1. Rename the `BACKUP_Nintendo 3DS` folder to `Nintendo 3DS`
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Bruteforce Movable skips to step 4
|
||||
{% capture compat %}
|
||||
<summary><u>Bruteforce Movable skips to step 4</u></summary>
|
||||
|
||||
The website has already mined your `movable.sed` using your friend code and ID0 combination. You can use the `movable.sed` that it provides you.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Important! You have been locked out of the automated part1 dumper system...
|
||||
{% capture compat %}
|
||||
<summary><u>Important! You have been locked out of the automated part1 dumper system...</u></summary>
|
||||
|
||||
Your friend code was blocked from using the friend code bot because your 3DS did not successfully friend the bot. Ensure your 3DS is properly connected to the Internet, then join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask to be unlocked.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### We were unable to successfully complete your bruteforce request. :`(
|
||||
{% capture compat %}
|
||||
<summary><u>We were unable to successfully complete your bruteforce request. :`(</u></summary>
|
||||
|
||||
The website has determined that your `movable.sed` cannot be brute-forced. Ensure that you gave the correct ID0 to the website. If your ID0 is correct, then you will be unable to use Seedminer and you will have to use an alternate method that will require additional games or hardware.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
## BannerBomb3
|
||||
|
||||
## Homebrew Launcher (PicHaxx)
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management menu crashes without showing BB3 multihax menu</u></summary>
|
||||
Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. If it is, then re-create it with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen).
|
||||
|
||||
### "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
Your `00000001.sav` and/or `otherapp.bin` files may be misplaced. Ensure that `00000001.sav` is in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data` and that `otherapp.bin` is on the root of your SD card.
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow [an alternate branch of Seedminer](homebrew-launcher-(pichaxx)). If Safe Mode doesn't work or you need assistance with this matter, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
If your files are in the correct locations, re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx), then place it in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`. Ensure that the file is named exactly `00000001.sav` and that you used your console's `movable.sed` to create it. Re-download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management menu does not crash</u></summary>
|
||||
|
||||
### "An exception occurred" or Errdisp when opening Picross
|
||||
`F00D43D5.bin` is missing from `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. Make sure that `Nintendo DSiWare` is correctly spelled and spaced. Uppercase/lowercase does not matter.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
Your device already has custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management shows a question mark</u></summary>
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
There may be an issue with your `F00D43D5.bin` file (it may be corrupted or intended for the wrong 3DS). Re-create your `F00D43D5.bin` file with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen), ensuring that you use the `movable.sed` file for your console.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
There is an issue with your `otherapp.bin` file. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
## Installing boot9strap (USM)
|
||||
|
||||
### Game starts normally
|
||||
{% capture compat %}
|
||||
<summary><u>Safe Mode system update succeeds instead of giving error 003-1099</u></summary>
|
||||
|
||||
Your modified `00000001.sav` file may be misplaced, or you may have used the wrong `movable.sed` when creating it. Re-generate your `movable.sed` from [Bruteforce Movable](https://seedminer.hacks.guide), then re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx) and place the resulting file (`00000001.sav`) in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`.
|
||||
unSAFE_MODE is not installed. [Follow the instructions](installing-boot9strap-(usm)] to install it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary><u>Red screen after selecting "Detailed Setup"</u></summary>
|
||||
|
||||
## Installing boot9strap (Soundhax)
|
||||
The file `usm.bin` is missing or misplaced. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/download/v1.3/usm.bin) and place `usm.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
### Red/purple/pink and white screen after running Soundhax
|
||||
There is also a possibility that the console isn't reading your SD card. Make sure it is inserted and formatted correctly.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
If your device is not on those firmwares, it likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
|
||||
There is an issue with your `otherapp.bin` file (it is missing, misplaced, or corrupted). Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) and place it on the root of your SD card.
|
||||
|
||||
### "Could not play"
|
||||
|
||||
You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow [Seedminer](seedminer).
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to mount the SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
## Installing boot9strap (Fredtool)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Error on Fredtool Injector page</u></summary>
|
||||
|
||||
Ensure that your `movable.sed` and DSiWare backup come from the same console. A mismatch will result in an error.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to select "Haxxxxxxxxx!" because the BB3 multihax menu appears</u></summary>
|
||||
|
||||
You forgot to delete `F00D43D5.bin` from the SD card. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card and delete the `F00D43D5.bin` file.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"Haxxxxxxxxx!" does not appear</u></summary>
|
||||
|
||||
There is an issue with your `42383821.bin` file (it is incorrect, missing, misplaced, or corrupted). Re-create your files with the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website and ensure that you place the `42383821.bin` file from `output.zip` -> `hax` in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DS Connection Settings launches normally</u></summary>
|
||||
|
||||
`Haxxxxxxxxx!` was not copied from your SD card to your system memory.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Black screen when launching DS Connection Settings</u></summary>
|
||||
|
||||
Your DS Connection Settings application is broken, and you will need Homebrew Launcher access to fix this issue. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>SD card is grayed out in Flipnote</u></summary>
|
||||
|
||||
Flipnote may take a long time to index your card if you have a large SD card. Let it sit for a few minutes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Lenny face does not appear in SD card section</u></summary>
|
||||
|
||||
You did not copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Flipnote freezes</u></summary>
|
||||
|
||||
You may have accidentally touched the touch screen while in the modified Flipnote. Re-enter DS Connection Settings and try again, ensuring that you don't accidentally use the touchscreen.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Green screen after pasting</u></summary>
|
||||
|
||||
The file `boot.nds` is missing or misplaced. Download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>White screen after pasting</u></summary>
|
||||
There is an issue with your `boot.nds` file. Re-download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to open Luma3DS configuration menu after running B9STool</u></summary>
|
||||
|
||||
It is possible that boot9strap was not successfully installed. Follow section B of [this page](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Homebrew Launcher (PicHaxx)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
|
||||
|
||||
Your `00000001.sav` and/or `otherapp.bin` files may be misplaced. Ensure that `00000001.sav` is in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data` and that `otherapp.bin` is on the root of your SD card.
|
||||
|
||||
If your files are in the correct locations, re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx), then place it in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`. Ensure that the file is named exactly `00000001.sav` and that you used your console's `movable.sed` to create it. Re-download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" or Errdisp when opening Picross</u></summary>
|
||||
|
||||
Your device already has custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `otherapp.bin` file. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Game starts normally</u></summary>
|
||||
|
||||
Your modified `00000001.sav` file may be misplaced, or you may have used the wrong `movable.sed` when creating it. Re-generate your `movable.sed` from [Bruteforce Movable](https://seedminer.hacks.guide), then re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx) and place the resulting file (`00000001.sav`) in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Installing boot9strap (Soundhax)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Soundhax</u></summary>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
If your device is not on those firmwares, it likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `otherapp.bin` file (it is missing, misplaced, or corrupted). Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) and place it on the root of your SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"Could not play"</u></summary>
|
||||
|
||||
You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow [Seedminer](seedminer).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Installing boot9strap (SSLoth-Browser)
|
||||
|
||||
### Red/purple/pink and white screen after running browserhax
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Browserhax</u></summary>
|
||||
|
||||
This likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
|
||||
|
||||
The file `arm11code.bin` is missing or misplaced. Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place `otherapp.bin` on the root of your SD card and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `arm11code.bin` file. Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place `otherapp.bin` on the root of your SD card and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Opening the browserhax QR code or URL crashes
|
||||
{% capture compat %}
|
||||
<summary><u>Opening the browserhax QR code or URL crashes</u></summary>
|
||||
|
||||
Browser based exploits (such as this one) are often unstable and crash frequently, but they can sometimes be fixed by doing the following steps.
|
||||
|
||||
1. Launch the browser, then launch the browser settings
|
||||
1. Scroll to the bottom and Initialize Savedata (it also may be called Clear All Save Data)
|
||||
1. Try the exploit again
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Opening the browser prompts for a system update instead
|
||||
{% capture compat %}
|
||||
<summary><u>System Update prompt when opening browser</u></summary>
|
||||
|
||||
The SSLoth proxy was incorrectly configured. Re-do the SSLoth section on the page.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Error 032-0420 when trying to open the browser
|
||||
{% capture compat %}
|
||||
<summary><u>Error 032-0420 when opening browser</u></summary>
|
||||
|
||||
Follow these steps in order:
|
||||
|
||||
|
|
@ -157,126 +376,47 @@ Follow these steps in order:
|
|||
1. If prompted about a system update, press OK
|
||||
+ This won't actually update the system
|
||||
1. Start again from [Section II](installing-boot9strap-(ssloth-browser).html#section-ii---ssloth)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Frozen on "Doing agbhax..."
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Frozen on "Doing agbhax..."</u></summary>
|
||||
There may be an issue with your `arm11code.bin` file. Re-download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place it on the root of your SD card, and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
If you have a Taiwanese unit (with a T in the version string, ie. 11.3.0-##T), you will not be able to follow these instructions, and you will need to update your console and follow [Seedminer](seedminer) instead.
|
||||
|
||||
If you have a Mainland Chinese unit (with a C in the version string, ie. 11.3.0-##C), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "PrepareArm9ForTwl returned error c8804631!"
|
||||
{% capture compat %}
|
||||
<summary><u>"PrepareArm9ForTwl returned error c8804631!"</u></summary>
|
||||
|
||||
You will need to follow an alternate method. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to mount the SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## BannerBomb3
|
||||
|
||||
### DSiWare Management menu crashes without showing BB3 multihax menu
|
||||
|
||||
Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. If it is, then re-create it with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen).
|
||||
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow [an alternate branch of Seedminer](homebrew-launcher-(pichaxx)). If Safe Mode doesn't work or you need assistance with this matter, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
|
||||
### DSiWare Management menu does not crash
|
||||
|
||||
`F00D43D5.bin` is missing from `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. Make sure that `Nintendo DSiWare` is correctly spelled and spaced. Uppercase/lowercase does not matter.
|
||||
|
||||
### DSiWare Management shows a question mark
|
||||
|
||||
There may be an issue with your `F00D43D5.bin` file (it may be corrupted or intended for the wrong 3DS). Re-create your `F00D43D5.bin` file with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen), ensuring that you use the `movable.sed` file for your console.
|
||||
|
||||
---
|
||||
|
||||
## Installing boot9strap (USM)
|
||||
|
||||
### Update doesn't fail with error code `003-1099`
|
||||
|
||||
unSAFE_MODE is not installed. Follow the instructions on your page to install unSAFE_MODE again.
|
||||
|
||||
### Red screen when selecting detailed setup
|
||||
|
||||
The file `usm.bin` is missing or misplaced. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/download/v1.3/usm.bin) and place `usm.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
There is also a possibility that the console isn't reading your SD card. Make sure it is inserted and formatted correctly.
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
### Failed to mount the SD card!
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
|
||||
---
|
||||
|
||||
## Installing boot9strap (Fredtool)
|
||||
|
||||
### Error on Fredtool Injector page
|
||||
|
||||
Ensure that your `movable.sed` and DSiWare backup come from the same console. A mismatch will result in an error.
|
||||
|
||||
### Unable to select the "Haxxxxxxxxx!" title because of the BB3 multihax menu
|
||||
|
||||
You forgot to delete `F00D43D5.bin` from the SD card. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card and delete the `F00D43D5.bin` file.
|
||||
|
||||
### "Haxxxxxxxxx!" does not appear
|
||||
|
||||
There is an issue with your `42383821.bin` file (it is incorrect, missing, misplaced, or corrupted). Re-create your files with the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website and ensure that you place the `42383821.bin` file from `output.zip` -> `hax` in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`.
|
||||
|
||||
### DS Connection Settings launches normally
|
||||
|
||||
`Haxxxxxxxxx!` was not copied from your SD card to your system memory.
|
||||
|
||||
### Black screen when launching DS Connection Settings
|
||||
|
||||
Your DS Connection Settings application is broken, and you will need Homebrew Launcher access to fix this issue. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
|
||||
### SD card is grayed out
|
||||
|
||||
Flipnote may take a long time to index your card if you have a large SD card. Let it sit for a few minutes.
|
||||
|
||||
### Lenny face does not appear
|
||||
|
||||
You did not copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card.
|
||||
|
||||
### Flipnote is frozen
|
||||
|
||||
You may have accidentally touched the touch screen while in the modified Flipnote. Re-enter DS Connection Settings and try again, ensuring that you don't accidentally use the touchscreen.
|
||||
|
||||
### Green screen after pasting
|
||||
|
||||
The file `boot.nds` is missing or misplaced. Download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
|
||||
### White screen after pasting
|
||||
|
||||
There is an issue with your `boot.nds` file. Re-download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
|
||||
### Unable to open Luma3DS configuration menu after running b9stool
|
||||
|
||||
It is possible that boot9strap was not successfully installed. Follow section B of [this page](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md).
|
||||
|
||||
---
|
||||
|
||||
## Finalizing Setup
|
||||
|
||||
### Unable to update device
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to update device</u></summary>
|
||||
|
||||
The steps below can be attempted in any order, but are listed from easiest to hardest to perform.
|
||||
|
||||
|
|
@ -289,27 +429,41 @@ The steps below can be attempted in any order, but are listed from easiest to ha
|
|||
1. Nintendo servers may be down; Try again later
|
||||
1. If you still get an error, [follow CTRTransfer](ctrtransfer), then try again
|
||||
1. For further support (in English), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Unable to enter Rosalina due to broken button(s)
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to enter Rosalina menu due to broken Left Shoulder / Down D-Pad / Select button(s)</u></summary>
|
||||
|
||||
Download this [alternate config.ini](https://cdn.discordapp.com/attachments/196635695958196224/982798396265988186/config.ini) and place it in `/luma/`. This will change the Rosalina key combination to (X) + (Y).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An exception occurred" after trying to launch Homebrew Launcher via Download Play
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" after trying to launch Homebrew Launcher from Download Play</u></summary>
|
||||
|
||||
There is an issue with your `boot.3dsx` file (it is missing, misplaced, or corrupted). Download the latest release of [the Homebrew Launcher](https://github.com/devkitPro/3ds-hbmenu/releases/latest) and place `boot.3dsx` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "Scripts directory not found" in GodMode9
|
||||
{% capture compat %}
|
||||
<summary><u>"Scripts directory not found" in GodMode9</u></summary>
|
||||
|
||||
You did not copy the `gm9` folder from the GodMode9 `.zip` to the root of your SD card. Download the latest release of [GodMode9](https://github.com/d0k3/GodMode9/releases/latest) and place the `gm9` folder on the root of your SD card, merging it with the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## Boot-related issues on modded devices
|
||||
## Boot issues on devices with custom firmware
|
||||
|
||||
The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
|
||||
{: .notice--info}
|
||||
|
||||
### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
|
||||
### Power/notification light indicators
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>My device powers off when I try to turn it on, and/or the notification LED shows a color on boot</u></summary>
|
||||
|
||||
There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
|
||||
|
||||
|
|
@ -322,11 +476,15 @@ If the notification LED flashes:
|
|||
You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
|
||||
|
||||
If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### My device gets stuck on a black screen, with a static blue light
|
||||
{% capture compat %}
|
||||
<summary><u>My device gets stuck on a black screen with blue power light staying on</u></summary>
|
||||
|
||||
The steps below can be attempted in any order, but are listed from least to most time-consuming.
|
||||
|
||||
1. Power off your device, remove the SD card, re-insert it, then power on your device.
|
||||
1. Power off your device, eject the game cartridge if inserted, power on your device, then wait up to ten minutes. If your device boots within ten minutes, the issue has been fixed and is unlikely to reoccur
|
||||
1. Rename the `Nintendo 3DS` folder on your SD card to `Nintendo 3DS_BACKUP`, then attempt to boot. If your device successfully boots, there is some issue within your `Nintendo 3DS` folder. Try clearing HOME Menu extdata:
|
||||
+ Navigate to `/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/`
|
||||
|
|
@ -344,35 +502,48 @@ The steps below can be attempted in any order, but are listed from least to most
|
|||
+ If you were successful, the device will boot to an "update your system" screen
|
||||
1. Follow the [CTRTransfer](ctrtransfer) guide
|
||||
1. For further support, ask for help at [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### My device boots to an error screen
|
||||
### Error message on boot
|
||||
|
||||
#### "An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"</u></summary>
|
||||
|
||||
Your Luma3DS version is outdated. Download the latest release of [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### "An error has occurred. Hold down the POWER button to turn off the power..."
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..."</u></summary>
|
||||
|
||||
ARM11 exception handlers are disabled, or custom firmware is not installed. Try enabling ARM11 exception handlers:
|
||||
+ Power off your device
|
||||
+ Hold (Select)
|
||||
+ Power on your device, while still holding (Select)
|
||||
+ If the "Disable ARM11 exception handlers" box is checked, uncheck it
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Some other error
|
||||
|
||||
Please take a photo of the error and join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
|
||||
### Blue "Bootrom Error" screen
|
||||
{% capture compat %}
|
||||
<summary><u>Blue "BOOTROM ERROR" screen</u></summary>
|
||||
|
||||
Your device is likely hard-bricked. You will need to buy an ntrboot flashcart to reinstall boot9strap in order to attempt to fix your device. This may also indicate a hardware issue that cannot be fixed. In any case, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
+ It is also possible that someone has set a boot-time splash screen that just looks like a brick. Try leaving your device powered on, waiting on the blue screen, for five minutes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary><u>Some other error</u></summary>
|
||||
|
||||
## Functionality-related issues on modded devices
|
||||
Please take a photo of the error and join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### DSi / DS functionality is broken or has been replaced with Flipnote Studio
|
||||
## Software issues on devices with custom firmware
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DSi / DS functionality is broken or has been replaced with Flipnote Studio</u></summary>
|
||||
|
||||
1. Download the latest release of [TWLFix-CFW](https://github.com/MechanicalDragon0687/TWLFix-CFW/releases/latest) (the `.3dsx` file)
|
||||
1. Power off your device
|
||||
|
|
@ -386,20 +557,29 @@ Your device is likely hard-bricked. You will need to buy an ntrboot flashcart to
|
|||
1. Perform a System Update by going to System Settings, then "Other Settings", then going all the way to the right and using "System Update"
|
||||
+ The update will see that the essential TWL titles have been uninstalled, and will redownload and reinstall them
|
||||
1. Once the update is complete, tap "OK" to reboot the device
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### GBA Virtual Console and/or Safe Mode functionality is broken
|
||||
{% capture compat %}
|
||||
<summary><u>GBA Virtual Console and/or Safe Mode functionality is broken</u></summary>
|
||||
|
||||
Your device is running Luma3DS/AuReiNand 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your device to a modern custom firmware environment.
|
||||
Your device is running Luma3DS 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your device to a modern custom firmware environment.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Extended memory mode games are broken
|
||||
{% capture compat %}
|
||||
<summary><u>Extended memory mode games (Pokemon Sun/Moon, Smash, etc.) don't work</u></summary>
|
||||
|
||||
This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will need to system format your device to fix this issue.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## Other troubleshooting
|
||||
|
||||
### Clear HOME Menu extdata
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu extdata</u></summary>
|
||||
|
||||
1. Power off your device
|
||||
1. Insert your SD card into your computer
|
||||
|
|
@ -412,8 +592,11 @@ This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will n
|
|||
+ **KOR Region**: `000000A9`
|
||||
+ **TWN Region**: `000000B1`
|
||||
1. Reinsert your SD card into your device
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Clear HOME Menu theme data
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu theme data</u></summary>
|
||||
|
||||
1. Power off your device
|
||||
1. Insert your SD card into your computer
|
||||
|
|
@ -423,3 +606,6 @@ This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will n
|
|||
+ **JPN Region**: `000002cc`
|
||||
+ **USA Region**: `000002cd`
|
||||
1. Reinsert your SD card into your device
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@ The purpose of this section is to check whether built-in DS mode applications wi
|
|||
+ If your console displays the Japanese version of Flipnote Studio, a black screen, or an error message, the test has failed
|
||||
1. Power off your device
|
||||
|
||||
If either of these tests has failed, DS mode, DS Download Play, and/or DS Connection Settings may be inaccessible once CFW is uninstalled! You should [fix DS mode](troubleshooting#dsi--ds-functionality-is-broken-or-has-been-replaced-with-flipnote-studio) before continuing.
|
||||
If either of these tests has failed, DS mode, DS Download Play, and/or DS Connection Settings may be inaccessible once CFW is uninstalled! You should [fix DS mode](troubleshooting#software-issues-on-devices-with-custom-firmware) before continuing.
|
||||
{: .notice--warning}
|
||||
|
||||
#### Section III - Safety Test
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ For all steps in this section, overwrite any existing files on your SD card.
|
|||
1. Your device should have rebooted into the Luma3DS configuration menu
|
||||
+ Luma3DS configuration menu are settings for the Luma3DS custom firmware. Many of these settings may be useful for customization or debugging
|
||||
+ For the purpose of this guide, these settings will be left on default settings
|
||||
+ If you get a black screen, [follow this troubleshooting guide](troubleshooting#boot-related-issues-on-modded-devices)
|
||||
+ If you get a black screen, [follow this troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware)
|
||||
1. Press (Start) to save and reboot
|
||||
|
||||
___
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ This is an add-on section to check if your console already has a modern custom f
|
|||
|
||||
If your console already has an arm9loaderhax or boot9strap based custom firmware, you will need to follow the instructions indicated to upgrade your setup to a modern one.
|
||||
|
||||
If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#clear-home-menu-extdata), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
|
||||
If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#other-troubleshooting), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
|
||||
{: .notice--info}
|
||||
|
||||
### Instructions
|
||||
|
|
|
|||
|
|
@ -14,79 +14,173 @@ title: "FAQ"
|
|||
|
||||
## Pre-Installation FAQ
|
||||
|
||||
#### **Q:** *I am on the latest system version. Is my device hackable without any external hardware?*
|
||||
**A:** Yes! The latest firmware (11.16.0) has a free method for getting CFW named [Seedminer](seedminer).
|
||||
{% capture compat %}
|
||||
<summary><u>I am on the latest system version. Is my device hackable without any external hardware?</u></summary>
|
||||
|
||||
#### **Q:** *What devices is this guide compatible with?*
|
||||
**A:** The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. If your system version string displays as "0.0.0-0", then you may have a developer unit.
|
||||
Yes! The latest firmware (11.16.0) has a free method for getting CFW named [Seedminer](seedminer).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How risky is hacking my console?*
|
||||
**A:** Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
{% capture compat %}
|
||||
<summary><u>What devices is this guide compatible with?</u></summary>
|
||||
|
||||
#### **Q:** *Can I run awesome homebrew and emulators with this?*
|
||||
**A:** Yes! This guide will install a few useful homebrew applications, including [Universal-Updater](https://github.com/Universal-Team/Universal-Updater/releases/latest), which acts as a homebrew app store.
|
||||
The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. If your system version string displays as "0.0.0-0", then you may have a developer unit.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I use this to play games from other regions?*
|
||||
**A:** Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Some games may need to make use of Luma's [locale emulation feature](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) in order to work properly on out-of-region devices.
|
||||
{% capture compat %}
|
||||
<summary><u>How risky is hacking my console?</u></summary>
|
||||
|
||||
#### **Q:** *Will I lose any features if I install CFW?*
|
||||
**A:** No. Devices with custom firmware can still use the eShop and run physical cartridges as any other 3DS can.
|
||||
Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I keep my NNID?*
|
||||
**A:** Your NNID (if you have one) will not be affected by this guide. Devices with a region of KOR, CHN, or TWN do not have NNID functionality to begin with and are thus unaffected.
|
||||
{% capture compat %}
|
||||
<summary><u>Can I run awesome homebrew and emulators with this?</u></summary>
|
||||
|
||||
#### **Q:** *Will my 3DS be banned for having CFW?*
|
||||
**A:** There was a ban wave in May 2017 that banned CFW users from online play (eShop access, NNIDs, and Nintendo Accounts were unaffected), seemingly at random. A ban wave at such a scale has not been seen since. That being said, we don't know what Nintendo may have in store in the future. At this time, we don't think that bans are something that you need to worry about.
|
||||
Yes! This guide will install a few useful homebrew applications, including [Universal-Updater](https://github.com/Universal-Team/Universal-Updater/releases/latest), which acts as a homebrew app store.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I do this without a computer (e.g. an Android phone)?*
|
||||
**A:** All you need is the ability to put files on a compatible SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Can I use this to play games from other regions?</u></summary>
|
||||
|
||||
#### **Q:** *What size SD card can I use?*
|
||||
**A:** You will need at least 1.5GB of free SD card space to follow this guide in its entirety. While the 3DS is officially compatible with SD cards up to 32GB, larger SD cards can be used if they are manually re-formatted as FAT32. It is not recommended to use SD cards greater than 128GB due to known issues with GBA graphics and custom themes.
|
||||
Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Some games may need to make use of Luma's [locale emulation feature](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) in order to work properly on out-of-region devices.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *I heard about this thing I have to pay for (Gateway, Sky3DS, ntrboot, R4, etc). Is that something I need?*
|
||||
**A:** No. Custom firmware can be installed for free on the latest firmware without any hardware devices. In fact, 3DS-mode flashcarts like Gateway and Sky3DS are not recommended because they are obsolete and may carry ban or brick risk.
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose any features if I install CFW?</u></summary>
|
||||
|
||||
#### **Q:** *What's the difference between custom firmware and homebrew access?*
|
||||
**A:** Historically, the 3DS used to have userland homebrew access through older exploits like ninjhax. The level of system access granted with userland allowed you to run basic homebrew and emulators but did not allow you to (easily) modify games or dump cartridges. It was also a lot less stable, with homebrew often ungracefully crashing and requiring a full reboot. Custom firmware grants a far greater level of system access while also being more stable than homebrew-only entrypoints.
|
||||
No. Devices with custom firmware can still use the eShop and run physical cartridges as any other 3DS can.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I keep my NNID?</u></summary>
|
||||
|
||||
Your NNID (if you have one) will not be affected by this guide. Devices with a region of KOR, CHN, or TWN do not have NNID functionality to begin with and are thus unaffected.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will my 3DS be banned for having CFW?</u></summary>
|
||||
|
||||
There was a ban wave in May 2017 that banned CFW users from online play (eShop access, NNIDs, and Nintendo Accounts were unaffected), seemingly at random. A ban wave at such a scale has not been seen since. That being said, we don't know what Nintendo may have in store in the future. At this time, we don't think that bans are something that you need to worry about.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I do this without a computer (e.g. an Android phone)?</u></summary>
|
||||
|
||||
Yes! All you need is the ability to put files on a compatible SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What size SD card can I use?</u></summary>
|
||||
|
||||
You will need at least 1.5GB of free SD card space to follow this guide in its entirety. While the 3DS is officially compatible with SD cards up to 32GB, larger SD cards can be used if they are manually re-formatted as FAT32. It is not recommended to use SD cards greater than 128GB due to known issues with GBA graphics and custom themes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>I heard about this thing I have to pay for (Gateway, Sky3DS, ntrboot, R4, etc). Is that something I need?</u></summary>
|
||||
|
||||
No. Custom firmware can be installed for free on the latest firmware without any hardware devices. In fact, 3DS-mode flashcarts like Gateway and Sky3DS are not recommended because they are obsolete and may carry ban or brick risk.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What's the difference between custom firmware and homebrew?</u></summary>
|
||||
|
||||
Historically, the 3DS used to have userland homebrew access through older exploits like ninjhax. The level of system access granted with userland allowed you to run basic homebrew and emulators but did not allow you to (easily) modify games or dump cartridges. It was also a lot less stable, with homebrew often ungracefully crashing and requiring a full reboot. Custom firmware grants a far greater level of system access while also being more stable than homebrew-only entrypoints.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Post-Installation FAQ
|
||||
|
||||
#### **Q:** *Is it safe to update my 3DS to the latest version with CFW?*
|
||||
**A:** If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. There have been updates in the past that have resulted in Luma3DS crashing on boot, so it is a good idea to wait a couple of hours to ensure that the latest update will not temporarily render the device unusable until Luma3DS is updated. System updates can be performed the same way as they are on a stock 3DS: through System Settings, Safe Mode, or the update prompt when the update is automatically downloaded.
|
||||
{% capture compat %}
|
||||
<summary><u>Is it safe to update my 3DS to the latest version with CFW?</u></summary>
|
||||
|
||||
#### **Q:** *How do I upgrade my SD card?*
|
||||
**A:** Copy and paste your SD card contents to a new SD card formatted as FAT32. For 128GB cards, an allocation size of 65536 is recommended. SD cards larger than 128GB are not recommended due to known issues with GBA graphics and custom themes.
|
||||
If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. There have been updates in the past that have resulted in Luma3DS crashing on boot, so it is a good idea to wait a couple of hours to ensure that the latest update will not temporarily render the device unusable until Luma3DS is updated. System updates can be performed the same way as they are on a stock 3DS: through System Settings, Safe Mode, or the update prompt when the update is automatically downloaded.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I system transfer with CFW?*
|
||||
**A:** Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets for illegitimate titles (homebrew) will not transfer, but the titles can be made to reappear with [faketik](https://github.com/ihaveamac/faketik/releases/latest). Make sure that you do not perform a wireless transfer, as this will delete illegitimate titles. CFW will remain on both consoles.
|
||||
{% capture compat %}
|
||||
<summary><u>How do I upgrade my SD card?</u></summary>
|
||||
|
||||
#### **Q:** *How do I change the system language of a Japanese 3DS?*
|
||||
**A:** The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Note that this is very likely to break the Nintendo eShop on your device, which means you will be unable to update your games whether they are in-region or out-of-region.
|
||||
Copy and paste your SD card contents to a new SD card formatted as FAT32. For 128GB cards, an allocation size of 65536 is recommended. SD cards larger than 128GB are not recommended due to known issues with GBA graphics and custom themes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How do I update homebrew applications?*
|
||||
**A:** It depends on the format of the homebrew application. Generally speaking:
|
||||
{% capture compat %}
|
||||
<summary><u>Can I system transfer with CFW?</u></summary>
|
||||
|
||||
Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets for illegitimate titles (homebrew) will not transfer, but the titles can be made to reappear with [faketik](https://github.com/ihaveamac/faketik/releases/latest). Make sure that you do not perform a wireless transfer, as this will delete illegitimate titles. CFW will remain on both consoles.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I change the system language of a Japanese 3DS?</u></summary>
|
||||
|
||||
The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Note that this is very likely to break the Nintendo eShop on your device, which means you will be unable to update your games whether they are in-region or out-of-region.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I update homebrew applications?</u></summary>
|
||||
|
||||
It depends on the format of the homebrew application. Generally speaking:
|
||||
|
||||
* Homebrew in **CIA format** can be updated by installing the new CIA, which will usually overwrite the old one. If the old CIA is not overwritten, you can delete the old one from Data Management as you would any other 3DS title.
|
||||
* Homebrew in **3DSX format** can be updated by replacing the 3DSX file in `/3ds/` with a fresh copy. If the homebrew application includes additional assets, you may need to place that folder somewhere else. Refer to the documentation of the homebrew application.
|
||||
* For updating Luma3DS, see [this page](restoring-updating-cfw). For updating GodMode9, see [this page](godmode9-usage#updating-godmode9).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How do I update games from outside of my 3DS region?*
|
||||
**A:** You will need to [dump the updates](dumping-titles-and-game-cartridges) from a 3DS that has the updates installed. The Nintendo eShop only contains updates for the console's region (a Japanese 3DS will only have updates for Japanese games).
|
||||
{% capture compat %}
|
||||
<summary><u>How do I update my games?</u></summary>
|
||||
|
||||
#### **Q:** *Help! Something bad happened and now I cannot boot...*
|
||||
**A:** Please look at the [troubleshooting guide](troubleshooting). **Uninstalling CFW when your device is in an unbootable state is not recommended, as it is very likely to lead to a brick**.
|
||||
You can continue to download game updates from the Nintendo eShop, even after the 2023 shutdown.
|
||||
|
||||
If the game is not from the same region as the console, you will need to [dump the updates](dumping-titles-and-game-cartridges) from a 3DS that has the updates installed. The Nintendo eShop only contains updates for the console's region (a Japanese 3DS will only have updates for Japanese games).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Help! Something bad happened and my 3DS won't boot to HOME Menu...</u></summary>
|
||||
|
||||
Please look at the [troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware). **Uninstalling CFW when your device is in an unbootable state is not recommended, as it is very likely to lead to a brick**.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## menuhax / A9LH / Gateway FAQ
|
||||
|
||||
#### **Q:** *I modded my device x years ago. What should I do?*
|
||||
**A:** It is recommended that you upgrade your setup to a modern, boot9strap-based one. Follow the [Checking for CFW](checking-for-cfw) guide to see how to upgrade your setup.
|
||||
{% capture compat %}
|
||||
<summary><u>I modded my device (x) years ago, so it already has some sort of homebrew. What should I do?</u></summary>
|
||||
|
||||
#### **Q:** *My setup works for me. Why should I upgrade it?*
|
||||
**A:** The vast majority of modern homebrew (such as Checkpoint and BootNTR Selector) have only been tested on modern, boot9strap-based setups and may not work entirely (or at all) on older setups based on menuhax, A9LH, or Gateway. In addition, depending on your setup, you may be unable to safely update to the latest firmware. Modern, boot9strap-based setups allow for a greater level of system access than previous hacks, including the ability to dump your console's bootrom.
|
||||
It is recommended that you upgrade your setup to a modern, boot9strap-based one. Follow the [Checking for CFW](checking-for-cfw) guide to see how to upgrade your setup.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Will I lose anything if I upgrade my setup?*
|
||||
**A:** Your old setup (including your EmuNAND, if you have one) can usually be directly migrated to boot9strap with no data loss. If you have data that is particularly important to you, it would be a good idea to make a decrypted backup of your save data before upgrading your setup with a tool like [JKSM](https://github.com/J-D-K/JKSM/releases/tag/12%2F20%2F2018).
|
||||
{% capture compat %}
|
||||
<summary><u>My setup works for me. Why should I upgrade it?</u></summary>
|
||||
|
||||
The vast majority of modern homebrew (such as Checkpoint and BootNTR Selector) have only been tested on modern, boot9strap-based setups and may not work entirely (or at all) on older setups based on menuhax, A9LH, or Gateway. In addition, depending on your setup, you may be unable to safely update to the latest firmware. Modern, boot9strap-based setups allow for a greater level of system access than previous hacks, including the ability to dump your console's bootrom.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose anything if I upgrade my setup?</u></summary>
|
||||
|
||||
Your old setup (including your EmuNAND, if you have one) can usually be directly migrated to boot9strap with no data loss. If you have data that is particularly important to you, it would be a good idea to make a decrypted backup of your save data before upgrading your setup with a tool like [JKSM](https://github.com/J-D-K/JKSM/releases/tag/12%2F20%2F2018).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I move saves from an existing Gateway setup to a more modern setup?</u></summary>
|
||||
|
||||
#### **Q:** *How do I move saves from an existing Gateway setup to a more modern setup?*
|
||||
**A:** See [this thread](https://gbatemp.net/threads/425743/).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@ In this section, you will update your system to the latest version, which is saf
|
|||
+ Updates while using B9S + Luma (what you have) are safe
|
||||
+ The updater may display a message saying "Your system is up to date" instead of updating. This is normal if you are already up to date; continue with the next section
|
||||
+ If this gives you an error, set both your DNS settings and Proxy settings to "auto"
|
||||
+ If this still gives you an error, [follow this troubleshooting guide](troubleshooting#unable-to-update-device)
|
||||
+ If this still gives you an error, [follow this troubleshooting guide](troubleshooting#finalizing-setup)
|
||||
|
||||
#### Section III - Homebrew Launcher
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
|||
1. Launch System Settings on your device
|
||||
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#dsiware-management-menu-crashes-without-showing-bb3-multihax-menu)
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#installing-boot9strap-fredtool)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Dump DSiWare"
|
||||
+ Your device will automatically reboot
|
||||
1. Power off your device
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
|||
1. Launch System Settings on your device
|
||||
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#dsiware-management-menu-crashes-without-showing-bb3-multihax-menu)
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#bannerbomb3)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Install unSAFE_MODE"
|
||||
+ Your device will automatically power off
|
||||
|
||||
|
|
|
|||
|
|
@ -168,7 +168,6 @@ To identify a `<TitleID>.gbavc.sav` file's Title ID, you can get a listing of al
|
|||
1. Reinsert your SD card into your device
|
||||
1. Press (A) to remount your SD card
|
||||
1. Press (Start) to reboot
|
||||
1. If you get a black screen, [follow this troubleshooting guide](troubleshooting#ts_sys_down)
|
||||
|
||||
___
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ In this section, you will get the necessary details from your 3DS that are requi
|
|||
+ If you don't have a `Nintendo 3DS` folder, put your SD card into your 3DS and power it on so that the folder can be created
|
||||
1. Copy the name of the 32-letter folder you see directly inside Nintendo 3DS
|
||||
+ This 32-letter name is system-specific and will be different for each console
|
||||
+ If you see multiple 32-letter folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
|
||||
+ If you see multiple 32-letter folders, follow [these instructions](troubleshooting#seedminer)
|
||||
+ You can ignore the `private` folder if you have it
|
||||
|
||||
![]({{ "/images/screenshots/seedminer/id0-example.png" | absolute_url }})
|
||||
|
|
|
|||
|
|
@ -2,37 +2,69 @@
|
|||
title: "Troubleshooting"
|
||||
---
|
||||
|
||||
{% include toc title="Table of Contents"%}
|
||||
|
||||
This page offers troubleshooting advice for commonly encountered issues. If you are unable to solve your issue with the advice on this page, please join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and describe your issue, including what you have already tried.
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary>Table of Contents</summary>
|
||||
|
||||
Used on multiple pages:
|
||||
* [SafeB9SInstaller](#issues-with-safeb9sinstaller)
|
||||
|
||||
Guide pages:
|
||||
* [Seedminer](#seedminer)
|
||||
* [BannerBomb3](#bannerbomb3)
|
||||
* [Installing boot9strap (USM)](#installing-boot9strap-usm)
|
||||
* [Installing boot9strap (Fredtool)](#installing-boot9strap-fredtool)
|
||||
* [Homebrew Launcher (PicHaxx)](#homebrew-launcher-pichaxx)
|
||||
* [Installing boot9strap (Soundhax)](#installing-boot9strap-soundhax)
|
||||
* [Installing boot9strap (SSLoth-Browser)](#installing-boot9strap-ssloth-browser)
|
||||
|
||||
* [Finalizing Setup](#finalizing-setup)
|
||||
|
||||
Issues after installation:
|
||||
* [Boot issues](#boot-issues-on-devices-with-custom-firmware)
|
||||
* [Software issues](#software-issues-on-devices-with-custom-firmware)
|
||||
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
{: .notice--info}
|
||||
|
||||
## Issues with SafeB9SInstaller
|
||||
|
||||
### SigHaxed FIRM was not installed! Check lower screen for more info.
|
||||
|
||||
#### SigHaxed FIRM - File not found
|
||||
{% capture compat %}
|
||||
<summary><u>SigHaxed FIRM - File not found</u></summary>
|
||||
|
||||
You are missing `boot9strap.firm` and `boot9strap.firm.sha` from the `boot9strap` folder, or the `boot9strap` folder is misnamed. Download the latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip), and place `boot9strap.firm` and `boot9strap.firm.sha` in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### SigHaxed FIRM - invalid FIRM
|
||||
{% capture compat %}
|
||||
<summary><u>SigHaxed FIRM - invalid FIRM</u></summary>
|
||||
|
||||
There is an issue with your `boot9strap.firm` and `boot9strap.firm.sha` files. Re-download the latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip), and place `boot9strap.firm` and `boot9strap.firm.sha` in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Secret Sector - File not found
|
||||
{% capture compat %}
|
||||
<summary><u>Secret Sector - File not found</u></summary>
|
||||
|
||||
You are missing `secret_sector.bin` from the `boot9strap` folder, or the `boot9strap` folder is misnamed. Download [secret_sector.bin](magnet:?xt=urn:btih:15a3c97acf17d67af98ae8657cc66820cc58f655&dn=secret_sector.bin&tr=udp%3a%2f%2ftracker.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.lelux.fi%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.loadbt.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.moeking.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.monitorit4.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.ololosh.space%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.pomf.se%3a80%2fannounce&tr=udp%3a%2f%2ftracker.srv00.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.theoks.net%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.tiny-vps.com%3a6969%2fannounce&tr=udp%3a%2f%2fopen.tracker.cl%3a1337%2fannounce&tr=udp%3a%2f%2ftracker.zerobytes.xyz%3a1337%2fannounce&tr=udp%3a%2f%2ftracker1.bt.moack.co.kr%3a80%2fannounce&tr=udp%3a%2f%2fvibe.sleepyinternetfun.xyz%3a1738%2fannounce&tr=udp%3a%2f%2fwww.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a6969%2fannounce&tr=udp%3a%2f%2f9.rarbg.com%3a2810%2fannounce&tr=udp%3a%2f%2ftracker.opentrackr.org%3a1337%2fannounce&tr=udp%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fopenbittorrent.com%3a80%2fannounce) using a torrent client, and place it in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Something else
|
||||
{% capture compat %}
|
||||
<summary><u>Something else</u></summary>
|
||||
|
||||
Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance, and describe the message that you see.
|
||||
|
||||
---
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Seedminer
|
||||
|
||||
### Multiple long folder names in Nintendo 3DS folder
|
||||
{% capture compat %}
|
||||
<summary><u>Multiple long folder names in Nintendo 3DS folder</u></summary>
|
||||
|
||||
![]({{ "/images/screenshots/multiple-id0.png" | absolute_url }})
|
||||
{: .notice--info}
|
||||
|
|
@ -49,98 +81,285 @@ This occurs when you use your SD card in multiple 3DS devices and is intended to
|
|||
+ This is your true ID0 that you will use in [Section II of Seedminer](seedminer#section-ii---seedminer)
|
||||
1. Delete the `Nintendo 3DS` folder
|
||||
1. Rename the `BACKUP_Nintendo 3DS` folder to `Nintendo 3DS`
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Bruteforce Movable skips to step 4
|
||||
{% capture compat %}
|
||||
<summary><u>Bruteforce Movable skips to step 4</u></summary>
|
||||
|
||||
The website has already mined your `movable.sed` using your friend code and ID0 combination. You can use the `movable.sed` that it provides you.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Important! You have been locked out of the automated part1 dumper system...
|
||||
{% capture compat %}
|
||||
<summary><u>Important! You have been locked out of the automated part1 dumper system...</u></summary>
|
||||
|
||||
Your friend code was blocked from using the friend code bot because your 3DS did not successfully friend the bot. Ensure your 3DS is properly connected to the Internet, then join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask to be unlocked.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### We were unable to successfully complete your bruteforce request. :`(
|
||||
{% capture compat %}
|
||||
<summary><u>We were unable to successfully complete your bruteforce request. :`(</u></summary>
|
||||
|
||||
The website has determined that your `movable.sed` cannot be brute-forced. Ensure that you gave the correct ID0 to the website. If your ID0 is correct, then you will be unable to use Seedminer and you will have to use an alternate method that will require additional games or hardware.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
## BannerBomb3
|
||||
|
||||
## Homebrew Launcher (PicHaxx)
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management menu crashes without showing BB3 multihax menu</u></summary>
|
||||
Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. If it is, then re-create it with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen).
|
||||
|
||||
### "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
Your `00000001.sav` and/or `otherapp.bin` files may be misplaced. Ensure that `00000001.sav` is in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data` and that `otherapp.bin` is on the root of your SD card.
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow [an alternate branch of Seedminer](homebrew-launcher-(pichaxx)). If Safe Mode doesn't work or you need assistance with this matter, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
If your files are in the correct locations, re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx), then place it in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`. Ensure that the file is named exactly `00000001.sav` and that you used your console's `movable.sed` to create it. Re-download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management menu does not crash</u></summary>
|
||||
|
||||
### "An exception occurred" or Errdisp when opening Picross
|
||||
`F00D43D5.bin` is missing from `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. Make sure that `Nintendo DSiWare` is correctly spelled and spaced. Uppercase/lowercase does not matter.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
Your device already has custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management shows a question mark</u></summary>
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
There may be an issue with your `F00D43D5.bin` file (it may be corrupted or intended for the wrong 3DS). Re-create your `F00D43D5.bin` file with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen), ensuring that you use the `movable.sed` file for your console.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
There is an issue with your `otherapp.bin` file. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
## Installing boot9strap (USM)
|
||||
|
||||
### Game starts normally
|
||||
{% capture compat %}
|
||||
<summary><u>Safe Mode system update succeeds instead of giving error 003-1099</u></summary>
|
||||
|
||||
Your modified `00000001.sav` file may be misplaced, or you may have used the wrong `movable.sed` when creating it. Re-generate your `movable.sed` from [Bruteforce Movable](https://seedminer.hacks.guide), then re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx) and place the resulting file (`00000001.sav`) in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`.
|
||||
unSAFE_MODE is not installed. [Follow the instructions](installing-boot9strap-(usm)] to install it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary><u>Red screen after selecting "Detailed Setup"</u></summary>
|
||||
|
||||
## Installing boot9strap (Soundhax)
|
||||
The file `usm.bin` is missing or misplaced. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/download/v1.3/usm.bin) and place `usm.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
### Red/purple/pink and white screen after running Soundhax
|
||||
There is also a possibility that the console isn't reading your SD card. Make sure it is inserted and formatted correctly.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
If your device is not on those firmwares, it likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
|
||||
There is an issue with your `otherapp.bin` file (it is missing, misplaced, or corrupted). Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) and place it on the root of your SD card.
|
||||
|
||||
### "Could not play"
|
||||
|
||||
You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow [Seedminer](seedminer).
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to mount the SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
## Installing boot9strap (Fredtool)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Error on Fredtool Injector page</u></summary>
|
||||
|
||||
Ensure that your `movable.sed` and DSiWare backup come from the same console. A mismatch will result in an error.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to select "Haxxxxxxxxx!" because the BB3 multihax menu appears</u></summary>
|
||||
|
||||
You forgot to delete `F00D43D5.bin` from the SD card. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card and delete the `F00D43D5.bin` file.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"Haxxxxxxxxx!" does not appear</u></summary>
|
||||
|
||||
There is an issue with your `42383821.bin` file (it is incorrect, missing, misplaced, or corrupted). Re-create your files with the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website and ensure that you place the `42383821.bin` file from `output.zip` -> `hax` in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DS Connection Settings launches normally</u></summary>
|
||||
|
||||
`Haxxxxxxxxx!` was not copied from your SD card to your system memory.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Black screen when launching DS Connection Settings</u></summary>
|
||||
|
||||
Your DS Connection Settings application is broken, and you will need Homebrew Launcher access to fix this issue. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>SD card is grayed out in Flipnote</u></summary>
|
||||
|
||||
Flipnote may take a long time to index your card if you have a large SD card. Let it sit for a few minutes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Lenny face does not appear in SD card section</u></summary>
|
||||
|
||||
You did not copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Flipnote freezes</u></summary>
|
||||
|
||||
You may have accidentally touched the touch screen while in the modified Flipnote. Re-enter DS Connection Settings and try again, ensuring that you don't accidentally use the touchscreen.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Green screen after pasting</u></summary>
|
||||
|
||||
The file `boot.nds` is missing or misplaced. Download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>White screen after pasting</u></summary>
|
||||
There is an issue with your `boot.nds` file. Re-download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to open Luma3DS configuration menu after running B9STool</u></summary>
|
||||
|
||||
It is possible that boot9strap was not successfully installed. Follow section B of [this page](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Homebrew Launcher (PicHaxx)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
|
||||
|
||||
Your `00000001.sav` and/or `otherapp.bin` files may be misplaced. Ensure that `00000001.sav` is in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data` and that `otherapp.bin` is on the root of your SD card.
|
||||
|
||||
If your files are in the correct locations, re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx), then place it in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`. Ensure that the file is named exactly `00000001.sav` and that you used your console's `movable.sed` to create it. Re-download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" or Errdisp when opening Picross</u></summary>
|
||||
|
||||
Your device already has custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `otherapp.bin` file. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Game starts normally</u></summary>
|
||||
|
||||
Your modified `00000001.sav` file may be misplaced, or you may have used the wrong `movable.sed` when creating it. Re-generate your `movable.sed` from [Bruteforce Movable](https://seedminer.hacks.guide), then re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx) and place the resulting file (`00000001.sav`) in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Installing boot9strap (Soundhax)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Soundhax</u></summary>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
If your device is not on those firmwares, it likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `otherapp.bin` file (it is missing, misplaced, or corrupted). Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) and place it on the root of your SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"Could not play"</u></summary>
|
||||
|
||||
You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow [Seedminer](seedminer).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Installing boot9strap (SSLoth-Browser)
|
||||
|
||||
### Red/purple/pink and white screen after running browserhax
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Browserhax</u></summary>
|
||||
|
||||
This likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
|
||||
|
||||
The file `arm11code.bin` is missing or misplaced. Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place `otherapp.bin` on the root of your SD card and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `arm11code.bin` file. Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place `otherapp.bin` on the root of your SD card and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Opening the browserhax QR code or URL crashes
|
||||
{% capture compat %}
|
||||
<summary><u>Opening the browserhax QR code or URL crashes</u></summary>
|
||||
|
||||
Browser based exploits (such as this one) are often unstable and crash frequently, but they can sometimes be fixed by doing the following steps.
|
||||
|
||||
1. Launch the browser, then launch the browser settings
|
||||
1. Scroll to the bottom and Initialize Savedata (it also may be called Clear All Save Data)
|
||||
1. Try the exploit again
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Opening the browser prompts for a system update instead
|
||||
{% capture compat %}
|
||||
<summary><u>System Update prompt when opening browser</u></summary>
|
||||
|
||||
The SSLoth proxy was incorrectly configured. Re-do the SSLoth section on the page.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Error 032-0420 when trying to open the browser
|
||||
{% capture compat %}
|
||||
<summary><u>Error 032-0420 when opening browser</u></summary>
|
||||
|
||||
Follow these steps in order:
|
||||
|
||||
|
|
@ -157,126 +376,47 @@ Follow these steps in order:
|
|||
1. If prompted about a system update, press OK
|
||||
+ This won't actually update the system
|
||||
1. Start again from [Section II](installing-boot9strap-(ssloth-browser).html#section-ii---ssloth)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Frozen on "Doing agbhax..."
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Frozen on "Doing agbhax..."</u></summary>
|
||||
There may be an issue with your `arm11code.bin` file. Re-download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place it on the root of your SD card, and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
If you have a Taiwanese unit (with a T in the version string, ie. 11.3.0-##T), you will not be able to follow these instructions, and you will need to update your console and follow [Seedminer](seedminer) instead.
|
||||
|
||||
If you have a Mainland Chinese unit (with a C in the version string, ie. 11.3.0-##C), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "PrepareArm9ForTwl returned error c8804631!"
|
||||
{% capture compat %}
|
||||
<summary><u>"PrepareArm9ForTwl returned error c8804631!"</u></summary>
|
||||
|
||||
You will need to follow an alternate method. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to mount the SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## BannerBomb3
|
||||
|
||||
### DSiWare Management menu crashes without showing BB3 multihax menu
|
||||
|
||||
Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. If it is, then re-create it with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen).
|
||||
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow [an alternate branch of Seedminer](homebrew-launcher-(pichaxx)). If Safe Mode doesn't work or you need assistance with this matter, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
|
||||
### DSiWare Management menu does not crash
|
||||
|
||||
`F00D43D5.bin` is missing from `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. Make sure that `Nintendo DSiWare` is correctly spelled and spaced. Uppercase/lowercase does not matter.
|
||||
|
||||
### DSiWare Management shows a question mark
|
||||
|
||||
There may be an issue with your `F00D43D5.bin` file (it may be corrupted or intended for the wrong 3DS). Re-create your `F00D43D5.bin` file with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen), ensuring that you use the `movable.sed` file for your console.
|
||||
|
||||
---
|
||||
|
||||
## Installing boot9strap (USM)
|
||||
|
||||
### Update doesn't fail with error code `003-1099`
|
||||
|
||||
unSAFE_MODE is not installed. Follow the instructions on your page to install unSAFE_MODE again.
|
||||
|
||||
### Red screen when selecting detailed setup
|
||||
|
||||
The file `usm.bin` is missing or misplaced. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/download/v1.3/usm.bin) and place `usm.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
There is also a possibility that the console isn't reading your SD card. Make sure it is inserted and formatted correctly.
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
### Failed to mount the SD card!
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
|
||||
---
|
||||
|
||||
## Installing boot9strap (Fredtool)
|
||||
|
||||
### Error on Fredtool Injector page
|
||||
|
||||
Ensure that your `movable.sed` and DSiWare backup come from the same console. A mismatch will result in an error.
|
||||
|
||||
### Unable to select the "Haxxxxxxxxx!" title because of the BB3 multihax menu
|
||||
|
||||
You forgot to delete `F00D43D5.bin` from the SD card. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card and delete the `F00D43D5.bin` file.
|
||||
|
||||
### "Haxxxxxxxxx!" does not appear
|
||||
|
||||
There is an issue with your `42383821.bin` file (it is incorrect, missing, misplaced, or corrupted). Re-create your files with the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website and ensure that you place the `42383821.bin` file from `output.zip` -> `hax` in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`.
|
||||
|
||||
### DS Connection Settings launches normally
|
||||
|
||||
`Haxxxxxxxxx!` was not copied from your SD card to your system memory.
|
||||
|
||||
### Black screen when launching DS Connection Settings
|
||||
|
||||
Your DS Connection Settings application is broken, and you will need Homebrew Launcher access to fix this issue. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
|
||||
### SD card is grayed out
|
||||
|
||||
Flipnote may take a long time to index your card if you have a large SD card. Let it sit for a few minutes.
|
||||
|
||||
### Lenny face does not appear
|
||||
|
||||
You did not copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card.
|
||||
|
||||
### Flipnote is frozen
|
||||
|
||||
You may have accidentally touched the touch screen while in the modified Flipnote. Re-enter DS Connection Settings and try again, ensuring that you don't accidentally use the touchscreen.
|
||||
|
||||
### Green screen after pasting
|
||||
|
||||
The file `boot.nds` is missing or misplaced. Download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
|
||||
### White screen after pasting
|
||||
|
||||
There is an issue with your `boot.nds` file. Re-download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
|
||||
### Unable to open Luma3DS configuration menu after running b9stool
|
||||
|
||||
It is possible that boot9strap was not successfully installed. Follow section B of [this page](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md).
|
||||
|
||||
---
|
||||
|
||||
## Finalizing Setup
|
||||
|
||||
### Unable to update device
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to update device</u></summary>
|
||||
|
||||
The steps below can be attempted in any order, but are listed from easiest to hardest to perform.
|
||||
|
||||
|
|
@ -289,27 +429,41 @@ The steps below can be attempted in any order, but are listed from easiest to ha
|
|||
1. Nintendo servers may be down; Try again later
|
||||
1. If you still get an error, [follow CTRTransfer](ctrtransfer), then try again
|
||||
1. For further support (in English), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Unable to enter Rosalina due to broken button(s)
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to enter Rosalina menu due to broken Left Shoulder / Down D-Pad / Select button(s)</u></summary>
|
||||
|
||||
Download this [alternate config.ini](https://cdn.discordapp.com/attachments/196635695958196224/982798396265988186/config.ini) and place it in `/luma/`. This will change the Rosalina key combination to (X) + (Y).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An exception occurred" after trying to launch Homebrew Launcher via Download Play
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" after trying to launch Homebrew Launcher from Download Play</u></summary>
|
||||
|
||||
There is an issue with your `boot.3dsx` file (it is missing, misplaced, or corrupted). Download the latest release of [the Homebrew Launcher](https://github.com/devkitPro/3ds-hbmenu/releases/latest) and place `boot.3dsx` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "Scripts directory not found" in GodMode9
|
||||
{% capture compat %}
|
||||
<summary><u>"Scripts directory not found" in GodMode9</u></summary>
|
||||
|
||||
You did not copy the `gm9` folder from the GodMode9 `.zip` to the root of your SD card. Download the latest release of [GodMode9](https://github.com/d0k3/GodMode9/releases/latest) and place the `gm9` folder on the root of your SD card, merging it with the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## Boot-related issues on modded devices
|
||||
## Boot issues on devices with custom firmware
|
||||
|
||||
The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
|
||||
{: .notice--info}
|
||||
|
||||
### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
|
||||
### Power/notification light indicators
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>My device powers off when I try to turn it on, and/or the notification LED shows a color on boot</u></summary>
|
||||
|
||||
There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
|
||||
|
||||
|
|
@ -322,11 +476,15 @@ If the notification LED flashes:
|
|||
You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
|
||||
|
||||
If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### My device gets stuck on a black screen, with a static blue light
|
||||
{% capture compat %}
|
||||
<summary><u>My device gets stuck on a black screen with blue power light staying on</u></summary>
|
||||
|
||||
The steps below can be attempted in any order, but are listed from least to most time-consuming.
|
||||
|
||||
1. Power off your device, remove the SD card, re-insert it, then power on your device.
|
||||
1. Power off your device, eject the game cartridge if inserted, power on your device, then wait up to ten minutes. If your device boots within ten minutes, the issue has been fixed and is unlikely to reoccur
|
||||
1. Rename the `Nintendo 3DS` folder on your SD card to `Nintendo 3DS_BACKUP`, then attempt to boot. If your device successfully boots, there is some issue within your `Nintendo 3DS` folder. Try clearing HOME Menu extdata:
|
||||
+ Navigate to `/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/`
|
||||
|
|
@ -344,35 +502,48 @@ The steps below can be attempted in any order, but are listed from least to most
|
|||
+ If you were successful, the device will boot to an "update your system" screen
|
||||
1. Follow the [CTRTransfer](ctrtransfer) guide
|
||||
1. For further support, ask for help at [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### My device boots to an error screen
|
||||
### Error message on boot
|
||||
|
||||
#### "An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"</u></summary>
|
||||
|
||||
Your Luma3DS version is outdated. Download the latest release of [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### "An error has occurred. Hold down the POWER button to turn off the power..."
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..."</u></summary>
|
||||
|
||||
ARM11 exception handlers are disabled, or custom firmware is not installed. Try enabling ARM11 exception handlers:
|
||||
+ Power off your device
|
||||
+ Hold (Select)
|
||||
+ Power on your device, while still holding (Select)
|
||||
+ If the "Disable ARM11 exception handlers" box is checked, uncheck it
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Some other error
|
||||
|
||||
Please take a photo of the error and join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
|
||||
### Blue "Bootrom Error" screen
|
||||
{% capture compat %}
|
||||
<summary><u>Blue "BOOTROM ERROR" screen</u></summary>
|
||||
|
||||
Your device is likely hard-bricked. You will need to buy an ntrboot flashcart to reinstall boot9strap in order to attempt to fix your device. This may also indicate a hardware issue that cannot be fixed. In any case, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
+ It is also possible that someone has set a boot-time splash screen that just looks like a brick. Try leaving your device powered on, waiting on the blue screen, for five minutes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary><u>Some other error</u></summary>
|
||||
|
||||
## Functionality-related issues on modded devices
|
||||
Please take a photo of the error and join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### DSi / DS functionality is broken or has been replaced with Flipnote Studio
|
||||
## Software issues on devices with custom firmware
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DSi / DS functionality is broken or has been replaced with Flipnote Studio</u></summary>
|
||||
|
||||
1. Download the latest release of [TWLFix-CFW](https://github.com/MechanicalDragon0687/TWLFix-CFW/releases/latest) (the `.3dsx` file)
|
||||
1. Power off your device
|
||||
|
|
@ -386,20 +557,29 @@ Your device is likely hard-bricked. You will need to buy an ntrboot flashcart to
|
|||
1. Perform a System Update by going to System Settings, then "Other Settings", then going all the way to the right and using "System Update"
|
||||
+ The update will see that the essential TWL titles have been uninstalled, and will redownload and reinstall them
|
||||
1. Once the update is complete, tap "OK" to reboot the device
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### GBA Virtual Console and/or Safe Mode functionality is broken
|
||||
{% capture compat %}
|
||||
<summary><u>GBA Virtual Console and/or Safe Mode functionality is broken</u></summary>
|
||||
|
||||
Your device is running Luma3DS/AuReiNand 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your device to a modern custom firmware environment.
|
||||
Your device is running Luma3DS 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your device to a modern custom firmware environment.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Extended memory mode games are broken
|
||||
{% capture compat %}
|
||||
<summary><u>Extended memory mode games (Pokemon Sun/Moon, Smash, etc.) don't work</u></summary>
|
||||
|
||||
This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will need to system format your device to fix this issue.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## Other troubleshooting
|
||||
|
||||
### Clear HOME Menu extdata
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu extdata</u></summary>
|
||||
|
||||
1. Power off your device
|
||||
1. Insert your SD card into your computer
|
||||
|
|
@ -412,8 +592,11 @@ This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will n
|
|||
+ **KOR Region**: `000000A9`
|
||||
+ **TWN Region**: `000000B1`
|
||||
1. Reinsert your SD card into your device
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Clear HOME Menu theme data
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu theme data</u></summary>
|
||||
|
||||
1. Power off your device
|
||||
1. Insert your SD card into your computer
|
||||
|
|
@ -423,3 +606,6 @@ This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will n
|
|||
+ **JPN Region**: `000002cc`
|
||||
+ **USA Region**: `000002cd`
|
||||
1. Reinsert your SD card into your device
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@ The purpose of this section is to check whether built-in DS mode applications wi
|
|||
+ If your console displays the Japanese version of Flipnote Studio, a black screen, or an error message, the test has failed
|
||||
1. Power off your device
|
||||
|
||||
If either of these tests has failed, DS mode, DS Download Play, and/or DS Connection Settings may be inaccessible once CFW is uninstalled! You should [fix DS mode](troubleshooting#dsi--ds-functionality-is-broken-or-has-been-replaced-with-flipnote-studio) before continuing.
|
||||
If either of these tests has failed, DS mode, DS Download Play, and/or DS Connection Settings may be inaccessible once CFW is uninstalled! You should [fix DS mode](troubleshooting#software-issues-on-devices-with-custom-firmware) before continuing.
|
||||
{: .notice--warning}
|
||||
|
||||
#### Section III - Safety Test
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ For all steps in this section, overwrite any existing files on your SD card.
|
|||
1. Your device should have rebooted into the Luma3DS configuration menu
|
||||
+ Luma3DS configuration menu are settings for the Luma3DS custom firmware. Many of these settings may be useful for customization or debugging
|
||||
+ For the purpose of this guide, these settings will be left on default settings
|
||||
+ If you get a black screen, [follow this troubleshooting guide](troubleshooting#boot-related-issues-on-modded-devices)
|
||||
+ If you get a black screen, [follow this troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware)
|
||||
1. Press (Start) to save and reboot
|
||||
|
||||
___
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ This is an add-on section to check if your console already has a modern custom f
|
|||
|
||||
If your console already has an arm9loaderhax or boot9strap based custom firmware, you will need to follow the instructions indicated to upgrade your setup to a modern one.
|
||||
|
||||
If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#clear-home-menu-extdata), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
|
||||
If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#other-troubleshooting), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
|
||||
{: .notice--info}
|
||||
|
||||
### Instructions
|
||||
|
|
|
|||
|
|
@ -14,79 +14,173 @@ title: "FAQ"
|
|||
|
||||
## Pre-Installation FAQ
|
||||
|
||||
#### **Q:** *I am on the latest system version. Is my device hackable without any external hardware?*
|
||||
**A:** Yes! The latest firmware (11.16.0) has a free method for getting CFW named [Seedminer](seedminer).
|
||||
{% capture compat %}
|
||||
<summary><u>I am on the latest system version. Is my device hackable without any external hardware?</u></summary>
|
||||
|
||||
#### **Q:** *What devices is this guide compatible with?*
|
||||
**A:** The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. If your system version string displays as "0.0.0-0", then you may have a developer unit.
|
||||
Yes! The latest firmware (11.16.0) has a free method for getting CFW named [Seedminer](seedminer).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How risky is hacking my console?*
|
||||
**A:** Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
{% capture compat %}
|
||||
<summary><u>What devices is this guide compatible with?</u></summary>
|
||||
|
||||
#### **Q:** *Can I run awesome homebrew and emulators with this?*
|
||||
**A:** Yes! This guide will install a few useful homebrew applications, including [Universal-Updater](https://github.com/Universal-Team/Universal-Updater/releases/latest), which acts as a homebrew app store.
|
||||
The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. If your system version string displays as "0.0.0-0", then you may have a developer unit.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I use this to play games from other regions?*
|
||||
**A:** Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Some games may need to make use of Luma's [locale emulation feature](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) in order to work properly on out-of-region devices.
|
||||
{% capture compat %}
|
||||
<summary><u>How risky is hacking my console?</u></summary>
|
||||
|
||||
#### **Q:** *Will I lose any features if I install CFW?*
|
||||
**A:** No. Devices with custom firmware can still use the eShop and run physical cartridges as any other 3DS can.
|
||||
Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I keep my NNID?*
|
||||
**A:** Your NNID (if you have one) will not be affected by this guide. Devices with a region of KOR, CHN, or TWN do not have NNID functionality to begin with and are thus unaffected.
|
||||
{% capture compat %}
|
||||
<summary><u>Can I run awesome homebrew and emulators with this?</u></summary>
|
||||
|
||||
#### **Q:** *Will my 3DS be banned for having CFW?*
|
||||
**A:** There was a ban wave in May 2017 that banned CFW users from online play (eShop access, NNIDs, and Nintendo Accounts were unaffected), seemingly at random. A ban wave at such a scale has not been seen since. That being said, we don't know what Nintendo may have in store in the future. At this time, we don't think that bans are something that you need to worry about.
|
||||
Yes! This guide will install a few useful homebrew applications, including [Universal-Updater](https://github.com/Universal-Team/Universal-Updater/releases/latest), which acts as a homebrew app store.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I do this without a computer (e.g. an Android phone)?*
|
||||
**A:** All you need is the ability to put files on a compatible SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Can I use this to play games from other regions?</u></summary>
|
||||
|
||||
#### **Q:** *What size SD card can I use?*
|
||||
**A:** You will need at least 1.5GB of free SD card space to follow this guide in its entirety. While the 3DS is officially compatible with SD cards up to 32GB, larger SD cards can be used if they are manually re-formatted as FAT32. It is not recommended to use SD cards greater than 128GB due to known issues with GBA graphics and custom themes.
|
||||
Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Some games may need to make use of Luma's [locale emulation feature](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) in order to work properly on out-of-region devices.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *I heard about this thing I have to pay for (Gateway, Sky3DS, ntrboot, R4, etc). Is that something I need?*
|
||||
**A:** No. Custom firmware can be installed for free on the latest firmware without any hardware devices. In fact, 3DS-mode flashcarts like Gateway and Sky3DS are not recommended because they are obsolete and may carry ban or brick risk.
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose any features if I install CFW?</u></summary>
|
||||
|
||||
#### **Q:** *What's the difference between custom firmware and homebrew access?*
|
||||
**A:** Historically, the 3DS used to have userland homebrew access through older exploits like ninjhax. The level of system access granted with userland allowed you to run basic homebrew and emulators but did not allow you to (easily) modify games or dump cartridges. It was also a lot less stable, with homebrew often ungracefully crashing and requiring a full reboot. Custom firmware grants a far greater level of system access while also being more stable than homebrew-only entrypoints.
|
||||
No. Devices with custom firmware can still use the eShop and run physical cartridges as any other 3DS can.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I keep my NNID?</u></summary>
|
||||
|
||||
Your NNID (if you have one) will not be affected by this guide. Devices with a region of KOR, CHN, or TWN do not have NNID functionality to begin with and are thus unaffected.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will my 3DS be banned for having CFW?</u></summary>
|
||||
|
||||
There was a ban wave in May 2017 that banned CFW users from online play (eShop access, NNIDs, and Nintendo Accounts were unaffected), seemingly at random. A ban wave at such a scale has not been seen since. That being said, we don't know what Nintendo may have in store in the future. At this time, we don't think that bans are something that you need to worry about.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I do this without a computer (e.g. an Android phone)?</u></summary>
|
||||
|
||||
Yes! All you need is the ability to put files on a compatible SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What size SD card can I use?</u></summary>
|
||||
|
||||
You will need at least 1.5GB of free SD card space to follow this guide in its entirety. While the 3DS is officially compatible with SD cards up to 32GB, larger SD cards can be used if they are manually re-formatted as FAT32. It is not recommended to use SD cards greater than 128GB due to known issues with GBA graphics and custom themes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>I heard about this thing I have to pay for (Gateway, Sky3DS, ntrboot, R4, etc). Is that something I need?</u></summary>
|
||||
|
||||
No. Custom firmware can be installed for free on the latest firmware without any hardware devices. In fact, 3DS-mode flashcarts like Gateway and Sky3DS are not recommended because they are obsolete and may carry ban or brick risk.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What's the difference between custom firmware and homebrew?</u></summary>
|
||||
|
||||
Historically, the 3DS used to have userland homebrew access through older exploits like ninjhax. The level of system access granted with userland allowed you to run basic homebrew and emulators but did not allow you to (easily) modify games or dump cartridges. It was also a lot less stable, with homebrew often ungracefully crashing and requiring a full reboot. Custom firmware grants a far greater level of system access while also being more stable than homebrew-only entrypoints.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Post-Installation FAQ
|
||||
|
||||
#### **Q:** *Is it safe to update my 3DS to the latest version with CFW?*
|
||||
**A:** If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. There have been updates in the past that have resulted in Luma3DS crashing on boot, so it is a good idea to wait a couple of hours to ensure that the latest update will not temporarily render the device unusable until Luma3DS is updated. System updates can be performed the same way as they are on a stock 3DS: through System Settings, Safe Mode, or the update prompt when the update is automatically downloaded.
|
||||
{% capture compat %}
|
||||
<summary><u>Is it safe to update my 3DS to the latest version with CFW?</u></summary>
|
||||
|
||||
#### **Q:** *How do I upgrade my SD card?*
|
||||
**A:** Copy and paste your SD card contents to a new SD card formatted as FAT32. For 128GB cards, an allocation size of 65536 is recommended. SD cards larger than 128GB are not recommended due to known issues with GBA graphics and custom themes.
|
||||
If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. There have been updates in the past that have resulted in Luma3DS crashing on boot, so it is a good idea to wait a couple of hours to ensure that the latest update will not temporarily render the device unusable until Luma3DS is updated. System updates can be performed the same way as they are on a stock 3DS: through System Settings, Safe Mode, or the update prompt when the update is automatically downloaded.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I system transfer with CFW?*
|
||||
**A:** Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets for illegitimate titles (homebrew) will not transfer, but the titles can be made to reappear with [faketik](https://github.com/ihaveamac/faketik/releases/latest). Make sure that you do not perform a wireless transfer, as this will delete illegitimate titles. CFW will remain on both consoles.
|
||||
{% capture compat %}
|
||||
<summary><u>How do I upgrade my SD card?</u></summary>
|
||||
|
||||
#### **Q:** *How do I change the system language of a Japanese 3DS?*
|
||||
**A:** The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Note that this is very likely to break the Nintendo eShop on your device, which means you will be unable to update your games whether they are in-region or out-of-region.
|
||||
Copy and paste your SD card contents to a new SD card formatted as FAT32. For 128GB cards, an allocation size of 65536 is recommended. SD cards larger than 128GB are not recommended due to known issues with GBA graphics and custom themes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How do I update homebrew applications?*
|
||||
**A:** It depends on the format of the homebrew application. Generally speaking:
|
||||
{% capture compat %}
|
||||
<summary><u>Can I system transfer with CFW?</u></summary>
|
||||
|
||||
Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets for illegitimate titles (homebrew) will not transfer, but the titles can be made to reappear with [faketik](https://github.com/ihaveamac/faketik/releases/latest). Make sure that you do not perform a wireless transfer, as this will delete illegitimate titles. CFW will remain on both consoles.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I change the system language of a Japanese 3DS?</u></summary>
|
||||
|
||||
The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Note that this is very likely to break the Nintendo eShop on your device, which means you will be unable to update your games whether they are in-region or out-of-region.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I update homebrew applications?</u></summary>
|
||||
|
||||
It depends on the format of the homebrew application. Generally speaking:
|
||||
|
||||
* Homebrew in **CIA format** can be updated by installing the new CIA, which will usually overwrite the old one. If the old CIA is not overwritten, you can delete the old one from Data Management as you would any other 3DS title.
|
||||
* Homebrew in **3DSX format** can be updated by replacing the 3DSX file in `/3ds/` with a fresh copy. If the homebrew application includes additional assets, you may need to place that folder somewhere else. Refer to the documentation of the homebrew application.
|
||||
* For updating Luma3DS, see [this page](restoring-updating-cfw). For updating GodMode9, see [this page](godmode9-usage#updating-godmode9).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How do I update games from outside of my 3DS region?*
|
||||
**A:** You will need to [dump the updates](dumping-titles-and-game-cartridges) from a 3DS that has the updates installed. The Nintendo eShop only contains updates for the console's region (a Japanese 3DS will only have updates for Japanese games).
|
||||
{% capture compat %}
|
||||
<summary><u>How do I update my games?</u></summary>
|
||||
|
||||
#### **Q:** *Help! Something bad happened and now I cannot boot...*
|
||||
**A:** Please look at the [troubleshooting guide](troubleshooting). **Uninstalling CFW when your device is in an unbootable state is not recommended, as it is very likely to lead to a brick**.
|
||||
You can continue to download game updates from the Nintendo eShop, even after the 2023 shutdown.
|
||||
|
||||
If the game is not from the same region as the console, you will need to [dump the updates](dumping-titles-and-game-cartridges) from a 3DS that has the updates installed. The Nintendo eShop only contains updates for the console's region (a Japanese 3DS will only have updates for Japanese games).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Help! Something bad happened and my 3DS won't boot to HOME Menu...</u></summary>
|
||||
|
||||
Please look at the [troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware). **Uninstalling CFW when your device is in an unbootable state is not recommended, as it is very likely to lead to a brick**.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## menuhax / A9LH / Gateway FAQ
|
||||
|
||||
#### **Q:** *I modded my device x years ago. What should I do?*
|
||||
**A:** It is recommended that you upgrade your setup to a modern, boot9strap-based one. Follow the [Checking for CFW](checking-for-cfw) guide to see how to upgrade your setup.
|
||||
{% capture compat %}
|
||||
<summary><u>I modded my device (x) years ago, so it already has some sort of homebrew. What should I do?</u></summary>
|
||||
|
||||
#### **Q:** *My setup works for me. Why should I upgrade it?*
|
||||
**A:** The vast majority of modern homebrew (such as Checkpoint and BootNTR Selector) have only been tested on modern, boot9strap-based setups and may not work entirely (or at all) on older setups based on menuhax, A9LH, or Gateway. In addition, depending on your setup, you may be unable to safely update to the latest firmware. Modern, boot9strap-based setups allow for a greater level of system access than previous hacks, including the ability to dump your console's bootrom.
|
||||
It is recommended that you upgrade your setup to a modern, boot9strap-based one. Follow the [Checking for CFW](checking-for-cfw) guide to see how to upgrade your setup.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Will I lose anything if I upgrade my setup?*
|
||||
**A:** Your old setup (including your EmuNAND, if you have one) can usually be directly migrated to boot9strap with no data loss. If you have data that is particularly important to you, it would be a good idea to make a decrypted backup of your save data before upgrading your setup with a tool like [JKSM](https://github.com/J-D-K/JKSM/releases/tag/12%2F20%2F2018).
|
||||
{% capture compat %}
|
||||
<summary><u>My setup works for me. Why should I upgrade it?</u></summary>
|
||||
|
||||
The vast majority of modern homebrew (such as Checkpoint and BootNTR Selector) have only been tested on modern, boot9strap-based setups and may not work entirely (or at all) on older setups based on menuhax, A9LH, or Gateway. In addition, depending on your setup, you may be unable to safely update to the latest firmware. Modern, boot9strap-based setups allow for a greater level of system access than previous hacks, including the ability to dump your console's bootrom.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose anything if I upgrade my setup?</u></summary>
|
||||
|
||||
Your old setup (including your EmuNAND, if you have one) can usually be directly migrated to boot9strap with no data loss. If you have data that is particularly important to you, it would be a good idea to make a decrypted backup of your save data before upgrading your setup with a tool like [JKSM](https://github.com/J-D-K/JKSM/releases/tag/12%2F20%2F2018).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I move saves from an existing Gateway setup to a more modern setup?</u></summary>
|
||||
|
||||
#### **Q:** *How do I move saves from an existing Gateway setup to a more modern setup?*
|
||||
**A:** See [this thread](https://gbatemp.net/threads/425743/).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@ In this section, you will update your system to the latest version, which is saf
|
|||
+ Updates while using B9S + Luma (what you have) are safe
|
||||
+ The updater may display a message saying "Your system is up to date" instead of updating. This is normal if you are already up to date; continue with the next section
|
||||
+ If this gives you an error, set both your DNS settings and Proxy settings to "auto"
|
||||
+ If this still gives you an error, [follow this troubleshooting guide](troubleshooting#unable-to-update-device)
|
||||
+ If this still gives you an error, [follow this troubleshooting guide](troubleshooting#finalizing-setup)
|
||||
|
||||
#### Section III - Homebrew Launcher
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
|||
1. Launch System Settings on your device
|
||||
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#dsiware-management-menu-crashes-without-showing-bb3-multihax-menu)
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#installing-boot9strap-fredtool)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Dump DSiWare"
|
||||
+ Your device will automatically reboot
|
||||
1. Power off your device
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
|||
1. Launch System Settings on your device
|
||||
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#dsiware-management-menu-crashes-without-showing-bb3-multihax-menu)
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#bannerbomb3)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Install unSAFE_MODE"
|
||||
+ Your device will automatically power off
|
||||
|
||||
|
|
|
|||
|
|
@ -168,7 +168,6 @@ To identify a `<TitleID>.gbavc.sav` file's Title ID, you can get a listing of al
|
|||
1. Reinsert your SD card into your device
|
||||
1. Press (A) to remount your SD card
|
||||
1. Press (Start) to reboot
|
||||
1. If you get a black screen, [follow this troubleshooting guide](troubleshooting#ts_sys_down)
|
||||
|
||||
___
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ In this section, you will get the necessary details from your 3DS that are requi
|
|||
+ If you don't have a `Nintendo 3DS` folder, put your SD card into your 3DS and power it on so that the folder can be created
|
||||
1. Copy the name of the 32-letter folder you see directly inside Nintendo 3DS
|
||||
+ This 32-letter name is system-specific and will be different for each console
|
||||
+ If you see multiple 32-letter folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
|
||||
+ If you see multiple 32-letter folders, follow [these instructions](troubleshooting#seedminer)
|
||||
+ You can ignore the `private` folder if you have it
|
||||
|
||||
![]({{ "/images/screenshots/seedminer/id0-example.png" | absolute_url }})
|
||||
|
|
|
|||
|
|
@ -2,37 +2,69 @@
|
|||
title: "Troubleshooting"
|
||||
---
|
||||
|
||||
{% include toc title="Table of Contents"%}
|
||||
|
||||
This page offers troubleshooting advice for commonly encountered issues. If you are unable to solve your issue with the advice on this page, please join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and describe your issue, including what you have already tried.
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary>Table of Contents</summary>
|
||||
|
||||
Used on multiple pages:
|
||||
* [SafeB9SInstaller](#issues-with-safeb9sinstaller)
|
||||
|
||||
Guide pages:
|
||||
* [Seedminer](#seedminer)
|
||||
* [BannerBomb3](#bannerbomb3)
|
||||
* [Installing boot9strap (USM)](#installing-boot9strap-usm)
|
||||
* [Installing boot9strap (Fredtool)](#installing-boot9strap-fredtool)
|
||||
* [Homebrew Launcher (PicHaxx)](#homebrew-launcher-pichaxx)
|
||||
* [Installing boot9strap (Soundhax)](#installing-boot9strap-soundhax)
|
||||
* [Installing boot9strap (SSLoth-Browser)](#installing-boot9strap-ssloth-browser)
|
||||
|
||||
* [Finalizing Setup](#finalizing-setup)
|
||||
|
||||
Issues after installation:
|
||||
* [Boot issues](#boot-issues-on-devices-with-custom-firmware)
|
||||
* [Software issues](#software-issues-on-devices-with-custom-firmware)
|
||||
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
{: .notice--info}
|
||||
|
||||
## Issues with SafeB9SInstaller
|
||||
|
||||
### SigHaxed FIRM was not installed! Check lower screen for more info.
|
||||
|
||||
#### SigHaxed FIRM - File not found
|
||||
{% capture compat %}
|
||||
<summary><u>SigHaxed FIRM - File not found</u></summary>
|
||||
|
||||
You are missing `boot9strap.firm` and `boot9strap.firm.sha` from the `boot9strap` folder, or the `boot9strap` folder is misnamed. Download the latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip), and place `boot9strap.firm` and `boot9strap.firm.sha` in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### SigHaxed FIRM - invalid FIRM
|
||||
{% capture compat %}
|
||||
<summary><u>SigHaxed FIRM - invalid FIRM</u></summary>
|
||||
|
||||
There is an issue with your `boot9strap.firm` and `boot9strap.firm.sha` files. Re-download the latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip), and place `boot9strap.firm` and `boot9strap.firm.sha` in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Secret Sector - File not found
|
||||
{% capture compat %}
|
||||
<summary><u>Secret Sector - File not found</u></summary>
|
||||
|
||||
You are missing `secret_sector.bin` from the `boot9strap` folder, or the `boot9strap` folder is misnamed. Download [secret_sector.bin](magnet:?xt=urn:btih:15a3c97acf17d67af98ae8657cc66820cc58f655&dn=secret_sector.bin&tr=udp%3a%2f%2ftracker.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.lelux.fi%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.loadbt.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.moeking.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.monitorit4.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.ololosh.space%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.pomf.se%3a80%2fannounce&tr=udp%3a%2f%2ftracker.srv00.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.theoks.net%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.tiny-vps.com%3a6969%2fannounce&tr=udp%3a%2f%2fopen.tracker.cl%3a1337%2fannounce&tr=udp%3a%2f%2ftracker.zerobytes.xyz%3a1337%2fannounce&tr=udp%3a%2f%2ftracker1.bt.moack.co.kr%3a80%2fannounce&tr=udp%3a%2f%2fvibe.sleepyinternetfun.xyz%3a1738%2fannounce&tr=udp%3a%2f%2fwww.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a6969%2fannounce&tr=udp%3a%2f%2f9.rarbg.com%3a2810%2fannounce&tr=udp%3a%2f%2ftracker.opentrackr.org%3a1337%2fannounce&tr=udp%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fopenbittorrent.com%3a80%2fannounce) using a torrent client, and place it in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Something else
|
||||
{% capture compat %}
|
||||
<summary><u>Something else</u></summary>
|
||||
|
||||
Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance, and describe the message that you see.
|
||||
|
||||
---
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Seedminer
|
||||
|
||||
### Multiple long folder names in Nintendo 3DS folder
|
||||
{% capture compat %}
|
||||
<summary><u>Multiple long folder names in Nintendo 3DS folder</u></summary>
|
||||
|
||||
![]({{ "/images/screenshots/multiple-id0.png" | absolute_url }})
|
||||
{: .notice--info}
|
||||
|
|
@ -49,98 +81,285 @@ This occurs when you use your SD card in multiple 3DS devices and is intended to
|
|||
+ This is your true ID0 that you will use in [Section II of Seedminer](seedminer#section-ii---seedminer)
|
||||
1. Delete the `Nintendo 3DS` folder
|
||||
1. Rename the `BACKUP_Nintendo 3DS` folder to `Nintendo 3DS`
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Bruteforce Movable skips to step 4
|
||||
{% capture compat %}
|
||||
<summary><u>Bruteforce Movable skips to step 4</u></summary>
|
||||
|
||||
The website has already mined your `movable.sed` using your friend code and ID0 combination. You can use the `movable.sed` that it provides you.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Important! You have been locked out of the automated part1 dumper system...
|
||||
{% capture compat %}
|
||||
<summary><u>Important! You have been locked out of the automated part1 dumper system...</u></summary>
|
||||
|
||||
Your friend code was blocked from using the friend code bot because your 3DS did not successfully friend the bot. Ensure your 3DS is properly connected to the Internet, then join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask to be unlocked.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### We were unable to successfully complete your bruteforce request. :`(
|
||||
{% capture compat %}
|
||||
<summary><u>We were unable to successfully complete your bruteforce request. :`(</u></summary>
|
||||
|
||||
The website has determined that your `movable.sed` cannot be brute-forced. Ensure that you gave the correct ID0 to the website. If your ID0 is correct, then you will be unable to use Seedminer and you will have to use an alternate method that will require additional games or hardware.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
## BannerBomb3
|
||||
|
||||
## Homebrew Launcher (PicHaxx)
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management menu crashes without showing BB3 multihax menu</u></summary>
|
||||
Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. If it is, then re-create it with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen).
|
||||
|
||||
### "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
Your `00000001.sav` and/or `otherapp.bin` files may be misplaced. Ensure that `00000001.sav` is in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data` and that `otherapp.bin` is on the root of your SD card.
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow [an alternate branch of Seedminer](homebrew-launcher-(pichaxx)). If Safe Mode doesn't work or you need assistance with this matter, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
If your files are in the correct locations, re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx), then place it in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`. Ensure that the file is named exactly `00000001.sav` and that you used your console's `movable.sed` to create it. Re-download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management menu does not crash</u></summary>
|
||||
|
||||
### "An exception occurred" or Errdisp when opening Picross
|
||||
`F00D43D5.bin` is missing from `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. Make sure that `Nintendo DSiWare` is correctly spelled and spaced. Uppercase/lowercase does not matter.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
Your device already has custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management shows a question mark</u></summary>
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
There may be an issue with your `F00D43D5.bin` file (it may be corrupted or intended for the wrong 3DS). Re-create your `F00D43D5.bin` file with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen), ensuring that you use the `movable.sed` file for your console.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
There is an issue with your `otherapp.bin` file. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
## Installing boot9strap (USM)
|
||||
|
||||
### Game starts normally
|
||||
{% capture compat %}
|
||||
<summary><u>Safe Mode system update succeeds instead of giving error 003-1099</u></summary>
|
||||
|
||||
Your modified `00000001.sav` file may be misplaced, or you may have used the wrong `movable.sed` when creating it. Re-generate your `movable.sed` from [Bruteforce Movable](https://seedminer.hacks.guide), then re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx) and place the resulting file (`00000001.sav`) in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`.
|
||||
unSAFE_MODE is not installed. [Follow the instructions](installing-boot9strap-(usm)] to install it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary><u>Red screen after selecting "Detailed Setup"</u></summary>
|
||||
|
||||
## Installing boot9strap (Soundhax)
|
||||
The file `usm.bin` is missing or misplaced. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/download/v1.3/usm.bin) and place `usm.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
### Red/purple/pink and white screen after running Soundhax
|
||||
There is also a possibility that the console isn't reading your SD card. Make sure it is inserted and formatted correctly.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
If your device is not on those firmwares, it likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
|
||||
There is an issue with your `otherapp.bin` file (it is missing, misplaced, or corrupted). Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) and place it on the root of your SD card.
|
||||
|
||||
### "Could not play"
|
||||
|
||||
You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow [Seedminer](seedminer).
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to mount the SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
## Installing boot9strap (Fredtool)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Error on Fredtool Injector page</u></summary>
|
||||
|
||||
Ensure that your `movable.sed` and DSiWare backup come from the same console. A mismatch will result in an error.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to select "Haxxxxxxxxx!" because the BB3 multihax menu appears</u></summary>
|
||||
|
||||
You forgot to delete `F00D43D5.bin` from the SD card. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card and delete the `F00D43D5.bin` file.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"Haxxxxxxxxx!" does not appear</u></summary>
|
||||
|
||||
There is an issue with your `42383821.bin` file (it is incorrect, missing, misplaced, or corrupted). Re-create your files with the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website and ensure that you place the `42383821.bin` file from `output.zip` -> `hax` in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DS Connection Settings launches normally</u></summary>
|
||||
|
||||
`Haxxxxxxxxx!` was not copied from your SD card to your system memory.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Black screen when launching DS Connection Settings</u></summary>
|
||||
|
||||
Your DS Connection Settings application is broken, and you will need Homebrew Launcher access to fix this issue. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>SD card is grayed out in Flipnote</u></summary>
|
||||
|
||||
Flipnote may take a long time to index your card if you have a large SD card. Let it sit for a few minutes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Lenny face does not appear in SD card section</u></summary>
|
||||
|
||||
You did not copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Flipnote freezes</u></summary>
|
||||
|
||||
You may have accidentally touched the touch screen while in the modified Flipnote. Re-enter DS Connection Settings and try again, ensuring that you don't accidentally use the touchscreen.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Green screen after pasting</u></summary>
|
||||
|
||||
The file `boot.nds` is missing or misplaced. Download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>White screen after pasting</u></summary>
|
||||
There is an issue with your `boot.nds` file. Re-download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to open Luma3DS configuration menu after running B9STool</u></summary>
|
||||
|
||||
It is possible that boot9strap was not successfully installed. Follow section B of [this page](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Homebrew Launcher (PicHaxx)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
|
||||
|
||||
Your `00000001.sav` and/or `otherapp.bin` files may be misplaced. Ensure that `00000001.sav` is in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data` and that `otherapp.bin` is on the root of your SD card.
|
||||
|
||||
If your files are in the correct locations, re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx), then place it in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`. Ensure that the file is named exactly `00000001.sav` and that you used your console's `movable.sed` to create it. Re-download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" or Errdisp when opening Picross</u></summary>
|
||||
|
||||
Your device already has custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `otherapp.bin` file. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Game starts normally</u></summary>
|
||||
|
||||
Your modified `00000001.sav` file may be misplaced, or you may have used the wrong `movable.sed` when creating it. Re-generate your `movable.sed` from [Bruteforce Movable](https://seedminer.hacks.guide), then re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx) and place the resulting file (`00000001.sav`) in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Installing boot9strap (Soundhax)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Soundhax</u></summary>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
If your device is not on those firmwares, it likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `otherapp.bin` file (it is missing, misplaced, or corrupted). Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) and place it on the root of your SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"Could not play"</u></summary>
|
||||
|
||||
You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow [Seedminer](seedminer).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Installing boot9strap (SSLoth-Browser)
|
||||
|
||||
### Red/purple/pink and white screen after running browserhax
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Browserhax</u></summary>
|
||||
|
||||
This likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
|
||||
|
||||
The file `arm11code.bin` is missing or misplaced. Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place `otherapp.bin` on the root of your SD card and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `arm11code.bin` file. Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place `otherapp.bin` on the root of your SD card and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Opening the browserhax QR code or URL crashes
|
||||
{% capture compat %}
|
||||
<summary><u>Opening the browserhax QR code or URL crashes</u></summary>
|
||||
|
||||
Browser based exploits (such as this one) are often unstable and crash frequently, but they can sometimes be fixed by doing the following steps.
|
||||
|
||||
1. Launch the browser, then launch the browser settings
|
||||
1. Scroll to the bottom and Initialize Savedata (it also may be called Clear All Save Data)
|
||||
1. Try the exploit again
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Opening the browser prompts for a system update instead
|
||||
{% capture compat %}
|
||||
<summary><u>System Update prompt when opening browser</u></summary>
|
||||
|
||||
The SSLoth proxy was incorrectly configured. Re-do the SSLoth section on the page.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Error 032-0420 when trying to open the browser
|
||||
{% capture compat %}
|
||||
<summary><u>Error 032-0420 when opening browser</u></summary>
|
||||
|
||||
Follow these steps in order:
|
||||
|
||||
|
|
@ -157,126 +376,47 @@ Follow these steps in order:
|
|||
1. If prompted about a system update, press OK
|
||||
+ This won't actually update the system
|
||||
1. Start again from [Section II](installing-boot9strap-(ssloth-browser).html#section-ii---ssloth)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Frozen on "Doing agbhax..."
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Frozen on "Doing agbhax..."</u></summary>
|
||||
There may be an issue with your `arm11code.bin` file. Re-download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place it on the root of your SD card, and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
If you have a Taiwanese unit (with a T in the version string, ie. 11.3.0-##T), you will not be able to follow these instructions, and you will need to update your console and follow [Seedminer](seedminer) instead.
|
||||
|
||||
If you have a Mainland Chinese unit (with a C in the version string, ie. 11.3.0-##C), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "PrepareArm9ForTwl returned error c8804631!"
|
||||
{% capture compat %}
|
||||
<summary><u>"PrepareArm9ForTwl returned error c8804631!"</u></summary>
|
||||
|
||||
You will need to follow an alternate method. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to mount the SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## BannerBomb3
|
||||
|
||||
### DSiWare Management menu crashes without showing BB3 multihax menu
|
||||
|
||||
Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. If it is, then re-create it with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen).
|
||||
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow [an alternate branch of Seedminer](homebrew-launcher-(pichaxx)). If Safe Mode doesn't work or you need assistance with this matter, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
|
||||
### DSiWare Management menu does not crash
|
||||
|
||||
`F00D43D5.bin` is missing from `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. Make sure that `Nintendo DSiWare` is correctly spelled and spaced. Uppercase/lowercase does not matter.
|
||||
|
||||
### DSiWare Management shows a question mark
|
||||
|
||||
There may be an issue with your `F00D43D5.bin` file (it may be corrupted or intended for the wrong 3DS). Re-create your `F00D43D5.bin` file with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen), ensuring that you use the `movable.sed` file for your console.
|
||||
|
||||
---
|
||||
|
||||
## Installing boot9strap (USM)
|
||||
|
||||
### Update doesn't fail with error code `003-1099`
|
||||
|
||||
unSAFE_MODE is not installed. Follow the instructions on your page to install unSAFE_MODE again.
|
||||
|
||||
### Red screen when selecting detailed setup
|
||||
|
||||
The file `usm.bin` is missing or misplaced. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/download/v1.3/usm.bin) and place `usm.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
There is also a possibility that the console isn't reading your SD card. Make sure it is inserted and formatted correctly.
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
### Failed to mount the SD card!
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
|
||||
---
|
||||
|
||||
## Installing boot9strap (Fredtool)
|
||||
|
||||
### Error on Fredtool Injector page
|
||||
|
||||
Ensure that your `movable.sed` and DSiWare backup come from the same console. A mismatch will result in an error.
|
||||
|
||||
### Unable to select the "Haxxxxxxxxx!" title because of the BB3 multihax menu
|
||||
|
||||
You forgot to delete `F00D43D5.bin` from the SD card. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card and delete the `F00D43D5.bin` file.
|
||||
|
||||
### "Haxxxxxxxxx!" does not appear
|
||||
|
||||
There is an issue with your `42383821.bin` file (it is incorrect, missing, misplaced, or corrupted). Re-create your files with the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website and ensure that you place the `42383821.bin` file from `output.zip` -> `hax` in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`.
|
||||
|
||||
### DS Connection Settings launches normally
|
||||
|
||||
`Haxxxxxxxxx!` was not copied from your SD card to your system memory.
|
||||
|
||||
### Black screen when launching DS Connection Settings
|
||||
|
||||
Your DS Connection Settings application is broken, and you will need Homebrew Launcher access to fix this issue. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
|
||||
### SD card is grayed out
|
||||
|
||||
Flipnote may take a long time to index your card if you have a large SD card. Let it sit for a few minutes.
|
||||
|
||||
### Lenny face does not appear
|
||||
|
||||
You did not copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card.
|
||||
|
||||
### Flipnote is frozen
|
||||
|
||||
You may have accidentally touched the touch screen while in the modified Flipnote. Re-enter DS Connection Settings and try again, ensuring that you don't accidentally use the touchscreen.
|
||||
|
||||
### Green screen after pasting
|
||||
|
||||
The file `boot.nds` is missing or misplaced. Download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
|
||||
### White screen after pasting
|
||||
|
||||
There is an issue with your `boot.nds` file. Re-download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
|
||||
### Unable to open Luma3DS configuration menu after running b9stool
|
||||
|
||||
It is possible that boot9strap was not successfully installed. Follow section B of [this page](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md).
|
||||
|
||||
---
|
||||
|
||||
## Finalizing Setup
|
||||
|
||||
### Unable to update device
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to update device</u></summary>
|
||||
|
||||
The steps below can be attempted in any order, but are listed from easiest to hardest to perform.
|
||||
|
||||
|
|
@ -289,27 +429,41 @@ The steps below can be attempted in any order, but are listed from easiest to ha
|
|||
1. Nintendo servers may be down; Try again later
|
||||
1. If you still get an error, [follow CTRTransfer](ctrtransfer), then try again
|
||||
1. For further support (in English), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Unable to enter Rosalina due to broken button(s)
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to enter Rosalina menu due to broken Left Shoulder / Down D-Pad / Select button(s)</u></summary>
|
||||
|
||||
Download this [alternate config.ini](https://cdn.discordapp.com/attachments/196635695958196224/982798396265988186/config.ini) and place it in `/luma/`. This will change the Rosalina key combination to (X) + (Y).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An exception occurred" after trying to launch Homebrew Launcher via Download Play
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" after trying to launch Homebrew Launcher from Download Play</u></summary>
|
||||
|
||||
There is an issue with your `boot.3dsx` file (it is missing, misplaced, or corrupted). Download the latest release of [the Homebrew Launcher](https://github.com/devkitPro/3ds-hbmenu/releases/latest) and place `boot.3dsx` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "Scripts directory not found" in GodMode9
|
||||
{% capture compat %}
|
||||
<summary><u>"Scripts directory not found" in GodMode9</u></summary>
|
||||
|
||||
You did not copy the `gm9` folder from the GodMode9 `.zip` to the root of your SD card. Download the latest release of [GodMode9](https://github.com/d0k3/GodMode9/releases/latest) and place the `gm9` folder on the root of your SD card, merging it with the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## Boot-related issues on modded devices
|
||||
## Boot issues on devices with custom firmware
|
||||
|
||||
The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
|
||||
{: .notice--info}
|
||||
|
||||
### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
|
||||
### Power/notification light indicators
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>My device powers off when I try to turn it on, and/or the notification LED shows a color on boot</u></summary>
|
||||
|
||||
There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
|
||||
|
||||
|
|
@ -322,11 +476,15 @@ If the notification LED flashes:
|
|||
You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
|
||||
|
||||
If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### My device gets stuck on a black screen, with a static blue light
|
||||
{% capture compat %}
|
||||
<summary><u>My device gets stuck on a black screen with blue power light staying on</u></summary>
|
||||
|
||||
The steps below can be attempted in any order, but are listed from least to most time-consuming.
|
||||
|
||||
1. Power off your device, remove the SD card, re-insert it, then power on your device.
|
||||
1. Power off your device, eject the game cartridge if inserted, power on your device, then wait up to ten minutes. If your device boots within ten minutes, the issue has been fixed and is unlikely to reoccur
|
||||
1. Rename the `Nintendo 3DS` folder on your SD card to `Nintendo 3DS_BACKUP`, then attempt to boot. If your device successfully boots, there is some issue within your `Nintendo 3DS` folder. Try clearing HOME Menu extdata:
|
||||
+ Navigate to `/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/`
|
||||
|
|
@ -344,35 +502,48 @@ The steps below can be attempted in any order, but are listed from least to most
|
|||
+ If you were successful, the device will boot to an "update your system" screen
|
||||
1. Follow the [CTRTransfer](ctrtransfer) guide
|
||||
1. For further support, ask for help at [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### My device boots to an error screen
|
||||
### Error message on boot
|
||||
|
||||
#### "An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"</u></summary>
|
||||
|
||||
Your Luma3DS version is outdated. Download the latest release of [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### "An error has occurred. Hold down the POWER button to turn off the power..."
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..."</u></summary>
|
||||
|
||||
ARM11 exception handlers are disabled, or custom firmware is not installed. Try enabling ARM11 exception handlers:
|
||||
+ Power off your device
|
||||
+ Hold (Select)
|
||||
+ Power on your device, while still holding (Select)
|
||||
+ If the "Disable ARM11 exception handlers" box is checked, uncheck it
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Some other error
|
||||
|
||||
Please take a photo of the error and join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
|
||||
### Blue "Bootrom Error" screen
|
||||
{% capture compat %}
|
||||
<summary><u>Blue "BOOTROM ERROR" screen</u></summary>
|
||||
|
||||
Your device is likely hard-bricked. You will need to buy an ntrboot flashcart to reinstall boot9strap in order to attempt to fix your device. This may also indicate a hardware issue that cannot be fixed. In any case, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
+ It is also possible that someone has set a boot-time splash screen that just looks like a brick. Try leaving your device powered on, waiting on the blue screen, for five minutes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary><u>Some other error</u></summary>
|
||||
|
||||
## Functionality-related issues on modded devices
|
||||
Please take a photo of the error and join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### DSi / DS functionality is broken or has been replaced with Flipnote Studio
|
||||
## Software issues on devices with custom firmware
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DSi / DS functionality is broken or has been replaced with Flipnote Studio</u></summary>
|
||||
|
||||
1. Download the latest release of [TWLFix-CFW](https://github.com/MechanicalDragon0687/TWLFix-CFW/releases/latest) (the `.3dsx` file)
|
||||
1. Power off your device
|
||||
|
|
@ -386,20 +557,29 @@ Your device is likely hard-bricked. You will need to buy an ntrboot flashcart to
|
|||
1. Perform a System Update by going to System Settings, then "Other Settings", then going all the way to the right and using "System Update"
|
||||
+ The update will see that the essential TWL titles have been uninstalled, and will redownload and reinstall them
|
||||
1. Once the update is complete, tap "OK" to reboot the device
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### GBA Virtual Console and/or Safe Mode functionality is broken
|
||||
{% capture compat %}
|
||||
<summary><u>GBA Virtual Console and/or Safe Mode functionality is broken</u></summary>
|
||||
|
||||
Your device is running Luma3DS/AuReiNand 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your device to a modern custom firmware environment.
|
||||
Your device is running Luma3DS 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your device to a modern custom firmware environment.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Extended memory mode games are broken
|
||||
{% capture compat %}
|
||||
<summary><u>Extended memory mode games (Pokemon Sun/Moon, Smash, etc.) don't work</u></summary>
|
||||
|
||||
This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will need to system format your device to fix this issue.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## Other troubleshooting
|
||||
|
||||
### Clear HOME Menu extdata
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu extdata</u></summary>
|
||||
|
||||
1. Power off your device
|
||||
1. Insert your SD card into your computer
|
||||
|
|
@ -412,8 +592,11 @@ This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will n
|
|||
+ **KOR Region**: `000000A9`
|
||||
+ **TWN Region**: `000000B1`
|
||||
1. Reinsert your SD card into your device
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Clear HOME Menu theme data
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu theme data</u></summary>
|
||||
|
||||
1. Power off your device
|
||||
1. Insert your SD card into your computer
|
||||
|
|
@ -423,3 +606,6 @@ This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will n
|
|||
+ **JPN Region**: `000002cc`
|
||||
+ **USA Region**: `000002cd`
|
||||
1. Reinsert your SD card into your device
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@ The purpose of this section is to check whether built-in DS mode applications wi
|
|||
+ If your console displays the Japanese version of Flipnote Studio, a black screen, or an error message, the test has failed
|
||||
1. Power off your device
|
||||
|
||||
If either of these tests has failed, DS mode, DS Download Play, and/or DS Connection Settings may be inaccessible once CFW is uninstalled! You should [fix DS mode](troubleshooting#dsi--ds-functionality-is-broken-or-has-been-replaced-with-flipnote-studio) before continuing.
|
||||
If either of these tests has failed, DS mode, DS Download Play, and/or DS Connection Settings may be inaccessible once CFW is uninstalled! You should [fix DS mode](troubleshooting#software-issues-on-devices-with-custom-firmware) before continuing.
|
||||
{: .notice--warning}
|
||||
|
||||
#### Section III - Safety Test
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ For all steps in this section, overwrite any existing files on your SD card.
|
|||
1. Your device should have rebooted into the Luma3DS configuration menu
|
||||
+ Luma3DS configuration menu are settings for the Luma3DS custom firmware. Many of these settings may be useful for customization or debugging
|
||||
+ For the purpose of this guide, these settings will be left on default settings
|
||||
+ If you get a black screen, [follow this troubleshooting guide](troubleshooting#boot-related-issues-on-modded-devices)
|
||||
+ If you get a black screen, [follow this troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware)
|
||||
1. Press (Start) to save and reboot
|
||||
|
||||
___
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ This is an add-on section to check if your console already has a modern custom f
|
|||
|
||||
If your console already has an arm9loaderhax or boot9strap based custom firmware, you will need to follow the instructions indicated to upgrade your setup to a modern one.
|
||||
|
||||
If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#clear-home-menu-extdata), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
|
||||
If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#other-troubleshooting), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
|
||||
{: .notice--info}
|
||||
|
||||
### Instructions
|
||||
|
|
|
|||
|
|
@ -14,79 +14,173 @@ title: "FAQ"
|
|||
|
||||
## Pre-Installation FAQ
|
||||
|
||||
#### **Q:** *I am on the latest system version. Is my device hackable without any external hardware?*
|
||||
**A:** Yes! The latest firmware (11.16.0) has a free method for getting CFW named [Seedminer](seedminer).
|
||||
{% capture compat %}
|
||||
<summary><u>I am on the latest system version. Is my device hackable without any external hardware?</u></summary>
|
||||
|
||||
#### **Q:** *What devices is this guide compatible with?*
|
||||
**A:** The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. If your system version string displays as "0.0.0-0", then you may have a developer unit.
|
||||
Yes! The latest firmware (11.16.0) has a free method for getting CFW named [Seedminer](seedminer).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How risky is hacking my console?*
|
||||
**A:** Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
{% capture compat %}
|
||||
<summary><u>What devices is this guide compatible with?</u></summary>
|
||||
|
||||
#### **Q:** *Can I run awesome homebrew and emulators with this?*
|
||||
**A:** Yes! This guide will install a few useful homebrew applications, including [Universal-Updater](https://github.com/Universal-Team/Universal-Updater/releases/latest), which acts as a homebrew app store.
|
||||
The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. If your system version string displays as "0.0.0-0", then you may have a developer unit.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I use this to play games from other regions?*
|
||||
**A:** Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Some games may need to make use of Luma's [locale emulation feature](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) in order to work properly on out-of-region devices.
|
||||
{% capture compat %}
|
||||
<summary><u>How risky is hacking my console?</u></summary>
|
||||
|
||||
#### **Q:** *Will I lose any features if I install CFW?*
|
||||
**A:** No. Devices with custom firmware can still use the eShop and run physical cartridges as any other 3DS can.
|
||||
Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I keep my NNID?*
|
||||
**A:** Your NNID (if you have one) will not be affected by this guide. Devices with a region of KOR, CHN, or TWN do not have NNID functionality to begin with and are thus unaffected.
|
||||
{% capture compat %}
|
||||
<summary><u>Can I run awesome homebrew and emulators with this?</u></summary>
|
||||
|
||||
#### **Q:** *Will my 3DS be banned for having CFW?*
|
||||
**A:** There was a ban wave in May 2017 that banned CFW users from online play (eShop access, NNIDs, and Nintendo Accounts were unaffected), seemingly at random. A ban wave at such a scale has not been seen since. That being said, we don't know what Nintendo may have in store in the future. At this time, we don't think that bans are something that you need to worry about.
|
||||
Yes! This guide will install a few useful homebrew applications, including [Universal-Updater](https://github.com/Universal-Team/Universal-Updater/releases/latest), which acts as a homebrew app store.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I do this without a computer (e.g. an Android phone)?*
|
||||
**A:** All you need is the ability to put files on a compatible SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Can I use this to play games from other regions?</u></summary>
|
||||
|
||||
#### **Q:** *What size SD card can I use?*
|
||||
**A:** You will need at least 1.5GB of free SD card space to follow this guide in its entirety. While the 3DS is officially compatible with SD cards up to 32GB, larger SD cards can be used if they are manually re-formatted as FAT32. It is not recommended to use SD cards greater than 128GB due to known issues with GBA graphics and custom themes.
|
||||
Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Some games may need to make use of Luma's [locale emulation feature](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) in order to work properly on out-of-region devices.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *I heard about this thing I have to pay for (Gateway, Sky3DS, ntrboot, R4, etc). Is that something I need?*
|
||||
**A:** No. Custom firmware can be installed for free on the latest firmware without any hardware devices. In fact, 3DS-mode flashcarts like Gateway and Sky3DS are not recommended because they are obsolete and may carry ban or brick risk.
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose any features if I install CFW?</u></summary>
|
||||
|
||||
#### **Q:** *What's the difference between custom firmware and homebrew access?*
|
||||
**A:** Historically, the 3DS used to have userland homebrew access through older exploits like ninjhax. The level of system access granted with userland allowed you to run basic homebrew and emulators but did not allow you to (easily) modify games or dump cartridges. It was also a lot less stable, with homebrew often ungracefully crashing and requiring a full reboot. Custom firmware grants a far greater level of system access while also being more stable than homebrew-only entrypoints.
|
||||
No. Devices with custom firmware can still use the eShop and run physical cartridges as any other 3DS can.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I keep my NNID?</u></summary>
|
||||
|
||||
Your NNID (if you have one) will not be affected by this guide. Devices with a region of KOR, CHN, or TWN do not have NNID functionality to begin with and are thus unaffected.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will my 3DS be banned for having CFW?</u></summary>
|
||||
|
||||
There was a ban wave in May 2017 that banned CFW users from online play (eShop access, NNIDs, and Nintendo Accounts were unaffected), seemingly at random. A ban wave at such a scale has not been seen since. That being said, we don't know what Nintendo may have in store in the future. At this time, we don't think that bans are something that you need to worry about.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I do this without a computer (e.g. an Android phone)?</u></summary>
|
||||
|
||||
Yes! All you need is the ability to put files on a compatible SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What size SD card can I use?</u></summary>
|
||||
|
||||
You will need at least 1.5GB of free SD card space to follow this guide in its entirety. While the 3DS is officially compatible with SD cards up to 32GB, larger SD cards can be used if they are manually re-formatted as FAT32. It is not recommended to use SD cards greater than 128GB due to known issues with GBA graphics and custom themes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>I heard about this thing I have to pay for (Gateway, Sky3DS, ntrboot, R4, etc). Is that something I need?</u></summary>
|
||||
|
||||
No. Custom firmware can be installed for free on the latest firmware without any hardware devices. In fact, 3DS-mode flashcarts like Gateway and Sky3DS are not recommended because they are obsolete and may carry ban or brick risk.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What's the difference between custom firmware and homebrew?</u></summary>
|
||||
|
||||
Historically, the 3DS used to have userland homebrew access through older exploits like ninjhax. The level of system access granted with userland allowed you to run basic homebrew and emulators but did not allow you to (easily) modify games or dump cartridges. It was also a lot less stable, with homebrew often ungracefully crashing and requiring a full reboot. Custom firmware grants a far greater level of system access while also being more stable than homebrew-only entrypoints.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Post-Installation FAQ
|
||||
|
||||
#### **Q:** *Is it safe to update my 3DS to the latest version with CFW?*
|
||||
**A:** If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. There have been updates in the past that have resulted in Luma3DS crashing on boot, so it is a good idea to wait a couple of hours to ensure that the latest update will not temporarily render the device unusable until Luma3DS is updated. System updates can be performed the same way as they are on a stock 3DS: through System Settings, Safe Mode, or the update prompt when the update is automatically downloaded.
|
||||
{% capture compat %}
|
||||
<summary><u>Is it safe to update my 3DS to the latest version with CFW?</u></summary>
|
||||
|
||||
#### **Q:** *How do I upgrade my SD card?*
|
||||
**A:** Copy and paste your SD card contents to a new SD card formatted as FAT32. For 128GB cards, an allocation size of 65536 is recommended. SD cards larger than 128GB are not recommended due to known issues with GBA graphics and custom themes.
|
||||
If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. There have been updates in the past that have resulted in Luma3DS crashing on boot, so it is a good idea to wait a couple of hours to ensure that the latest update will not temporarily render the device unusable until Luma3DS is updated. System updates can be performed the same way as they are on a stock 3DS: through System Settings, Safe Mode, or the update prompt when the update is automatically downloaded.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I system transfer with CFW?*
|
||||
**A:** Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets for illegitimate titles (homebrew) will not transfer, but the titles can be made to reappear with [faketik](https://github.com/ihaveamac/faketik/releases/latest). Make sure that you do not perform a wireless transfer, as this will delete illegitimate titles. CFW will remain on both consoles.
|
||||
{% capture compat %}
|
||||
<summary><u>How do I upgrade my SD card?</u></summary>
|
||||
|
||||
#### **Q:** *How do I change the system language of a Japanese 3DS?*
|
||||
**A:** The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Note that this is very likely to break the Nintendo eShop on your device, which means you will be unable to update your games whether they are in-region or out-of-region.
|
||||
Copy and paste your SD card contents to a new SD card formatted as FAT32. For 128GB cards, an allocation size of 65536 is recommended. SD cards larger than 128GB are not recommended due to known issues with GBA graphics and custom themes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How do I update homebrew applications?*
|
||||
**A:** It depends on the format of the homebrew application. Generally speaking:
|
||||
{% capture compat %}
|
||||
<summary><u>Can I system transfer with CFW?</u></summary>
|
||||
|
||||
Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets for illegitimate titles (homebrew) will not transfer, but the titles can be made to reappear with [faketik](https://github.com/ihaveamac/faketik/releases/latest). Make sure that you do not perform a wireless transfer, as this will delete illegitimate titles. CFW will remain on both consoles.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I change the system language of a Japanese 3DS?</u></summary>
|
||||
|
||||
The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Note that this is very likely to break the Nintendo eShop on your device, which means you will be unable to update your games whether they are in-region or out-of-region.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I update homebrew applications?</u></summary>
|
||||
|
||||
It depends on the format of the homebrew application. Generally speaking:
|
||||
|
||||
* Homebrew in **CIA format** can be updated by installing the new CIA, which will usually overwrite the old one. If the old CIA is not overwritten, you can delete the old one from Data Management as you would any other 3DS title.
|
||||
* Homebrew in **3DSX format** can be updated by replacing the 3DSX file in `/3ds/` with a fresh copy. If the homebrew application includes additional assets, you may need to place that folder somewhere else. Refer to the documentation of the homebrew application.
|
||||
* For updating Luma3DS, see [this page](restoring-updating-cfw). For updating GodMode9, see [this page](godmode9-usage#updating-godmode9).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How do I update games from outside of my 3DS region?*
|
||||
**A:** You will need to [dump the updates](dumping-titles-and-game-cartridges) from a 3DS that has the updates installed. The Nintendo eShop only contains updates for the console's region (a Japanese 3DS will only have updates for Japanese games).
|
||||
{% capture compat %}
|
||||
<summary><u>How do I update my games?</u></summary>
|
||||
|
||||
#### **Q:** *Help! Something bad happened and now I cannot boot...*
|
||||
**A:** Please look at the [troubleshooting guide](troubleshooting). **Uninstalling CFW when your device is in an unbootable state is not recommended, as it is very likely to lead to a brick**.
|
||||
You can continue to download game updates from the Nintendo eShop, even after the 2023 shutdown.
|
||||
|
||||
If the game is not from the same region as the console, you will need to [dump the updates](dumping-titles-and-game-cartridges) from a 3DS that has the updates installed. The Nintendo eShop only contains updates for the console's region (a Japanese 3DS will only have updates for Japanese games).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Help! Something bad happened and my 3DS won't boot to HOME Menu...</u></summary>
|
||||
|
||||
Please look at the [troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware). **Uninstalling CFW when your device is in an unbootable state is not recommended, as it is very likely to lead to a brick**.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## menuhax / A9LH / Gateway FAQ
|
||||
|
||||
#### **Q:** *I modded my device x years ago. What should I do?*
|
||||
**A:** It is recommended that you upgrade your setup to a modern, boot9strap-based one. Follow the [Checking for CFW](checking-for-cfw) guide to see how to upgrade your setup.
|
||||
{% capture compat %}
|
||||
<summary><u>I modded my device (x) years ago, so it already has some sort of homebrew. What should I do?</u></summary>
|
||||
|
||||
#### **Q:** *My setup works for me. Why should I upgrade it?*
|
||||
**A:** The vast majority of modern homebrew (such as Checkpoint and BootNTR Selector) have only been tested on modern, boot9strap-based setups and may not work entirely (or at all) on older setups based on menuhax, A9LH, or Gateway. In addition, depending on your setup, you may be unable to safely update to the latest firmware. Modern, boot9strap-based setups allow for a greater level of system access than previous hacks, including the ability to dump your console's bootrom.
|
||||
It is recommended that you upgrade your setup to a modern, boot9strap-based one. Follow the [Checking for CFW](checking-for-cfw) guide to see how to upgrade your setup.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Will I lose anything if I upgrade my setup?*
|
||||
**A:** Your old setup (including your EmuNAND, if you have one) can usually be directly migrated to boot9strap with no data loss. If you have data that is particularly important to you, it would be a good idea to make a decrypted backup of your save data before upgrading your setup with a tool like [JKSM](https://github.com/J-D-K/JKSM/releases/tag/12%2F20%2F2018).
|
||||
{% capture compat %}
|
||||
<summary><u>My setup works for me. Why should I upgrade it?</u></summary>
|
||||
|
||||
The vast majority of modern homebrew (such as Checkpoint and BootNTR Selector) have only been tested on modern, boot9strap-based setups and may not work entirely (or at all) on older setups based on menuhax, A9LH, or Gateway. In addition, depending on your setup, you may be unable to safely update to the latest firmware. Modern, boot9strap-based setups allow for a greater level of system access than previous hacks, including the ability to dump your console's bootrom.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose anything if I upgrade my setup?</u></summary>
|
||||
|
||||
Your old setup (including your EmuNAND, if you have one) can usually be directly migrated to boot9strap with no data loss. If you have data that is particularly important to you, it would be a good idea to make a decrypted backup of your save data before upgrading your setup with a tool like [JKSM](https://github.com/J-D-K/JKSM/releases/tag/12%2F20%2F2018).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I move saves from an existing Gateway setup to a more modern setup?</u></summary>
|
||||
|
||||
#### **Q:** *How do I move saves from an existing Gateway setup to a more modern setup?*
|
||||
**A:** See [this thread](https://gbatemp.net/threads/425743/).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@ In this section, you will update your system to the latest version, which is saf
|
|||
+ Updates while using B9S + Luma (what you have) are safe
|
||||
+ The updater may display a message saying "Your system is up to date" instead of updating. This is normal if you are already up to date; continue with the next section
|
||||
+ If this gives you an error, set both your DNS settings and Proxy settings to "auto"
|
||||
+ If this still gives you an error, [follow this troubleshooting guide](troubleshooting#unable-to-update-device)
|
||||
+ If this still gives you an error, [follow this troubleshooting guide](troubleshooting#finalizing-setup)
|
||||
|
||||
#### Section III - Homebrew Launcher
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
|||
1. Launch System Settings on your device
|
||||
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#dsiware-management-menu-crashes-without-showing-bb3-multihax-menu)
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#installing-boot9strap-fredtool)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Dump DSiWare"
|
||||
+ Your device will automatically reboot
|
||||
1. Power off your device
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
|||
1. Launch System Settings on your device
|
||||
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#dsiware-management-menu-crashes-without-showing-bb3-multihax-menu)
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#bannerbomb3)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Install unSAFE_MODE"
|
||||
+ Your device will automatically power off
|
||||
|
||||
|
|
|
|||
|
|
@ -168,7 +168,6 @@ To identify a `<TitleID>.gbavc.sav` file's Title ID, you can get a listing of al
|
|||
1. Reinsert your SD card into your device
|
||||
1. Press (A) to remount your SD card
|
||||
1. Press (Start) to reboot
|
||||
1. If you get a black screen, [follow this troubleshooting guide](troubleshooting#ts_sys_down)
|
||||
|
||||
___
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ In this section, you will get the necessary details from your 3DS that are requi
|
|||
+ If you don't have a `Nintendo 3DS` folder, put your SD card into your 3DS and power it on so that the folder can be created
|
||||
1. Copy the name of the 32-letter folder you see directly inside Nintendo 3DS
|
||||
+ This 32-letter name is system-specific and will be different for each console
|
||||
+ If you see multiple 32-letter folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
|
||||
+ If you see multiple 32-letter folders, follow [these instructions](troubleshooting#seedminer)
|
||||
+ You can ignore the `private` folder if you have it
|
||||
|
||||
![]({{ "/images/screenshots/seedminer/id0-example.png" | absolute_url }})
|
||||
|
|
|
|||
|
|
@ -2,37 +2,69 @@
|
|||
title: "Troubleshooting"
|
||||
---
|
||||
|
||||
{% include toc title="Table of Contents"%}
|
||||
|
||||
This page offers troubleshooting advice for commonly encountered issues. If you are unable to solve your issue with the advice on this page, please join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and describe your issue, including what you have already tried.
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary>Table of Contents</summary>
|
||||
|
||||
Used on multiple pages:
|
||||
* [SafeB9SInstaller](#issues-with-safeb9sinstaller)
|
||||
|
||||
Guide pages:
|
||||
* [Seedminer](#seedminer)
|
||||
* [BannerBomb3](#bannerbomb3)
|
||||
* [Installing boot9strap (USM)](#installing-boot9strap-usm)
|
||||
* [Installing boot9strap (Fredtool)](#installing-boot9strap-fredtool)
|
||||
* [Homebrew Launcher (PicHaxx)](#homebrew-launcher-pichaxx)
|
||||
* [Installing boot9strap (Soundhax)](#installing-boot9strap-soundhax)
|
||||
* [Installing boot9strap (SSLoth-Browser)](#installing-boot9strap-ssloth-browser)
|
||||
|
||||
* [Finalizing Setup](#finalizing-setup)
|
||||
|
||||
Issues after installation:
|
||||
* [Boot issues](#boot-issues-on-devices-with-custom-firmware)
|
||||
* [Software issues](#software-issues-on-devices-with-custom-firmware)
|
||||
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
{: .notice--info}
|
||||
|
||||
## Issues with SafeB9SInstaller
|
||||
|
||||
### SigHaxed FIRM was not installed! Check lower screen for more info.
|
||||
|
||||
#### SigHaxed FIRM - File not found
|
||||
{% capture compat %}
|
||||
<summary><u>SigHaxed FIRM - File not found</u></summary>
|
||||
|
||||
You are missing `boot9strap.firm` and `boot9strap.firm.sha` from the `boot9strap` folder, or the `boot9strap` folder is misnamed. Download the latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip), and place `boot9strap.firm` and `boot9strap.firm.sha` in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### SigHaxed FIRM - invalid FIRM
|
||||
{% capture compat %}
|
||||
<summary><u>SigHaxed FIRM - invalid FIRM</u></summary>
|
||||
|
||||
There is an issue with your `boot9strap.firm` and `boot9strap.firm.sha` files. Re-download the latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip), and place `boot9strap.firm` and `boot9strap.firm.sha` in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Secret Sector - File not found
|
||||
{% capture compat %}
|
||||
<summary><u>Secret Sector - File not found</u></summary>
|
||||
|
||||
You are missing `secret_sector.bin` from the `boot9strap` folder, or the `boot9strap` folder is misnamed. Download [secret_sector.bin](magnet:?xt=urn:btih:15a3c97acf17d67af98ae8657cc66820cc58f655&dn=secret_sector.bin&tr=udp%3a%2f%2ftracker.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.lelux.fi%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.loadbt.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.moeking.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.monitorit4.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.ololosh.space%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.pomf.se%3a80%2fannounce&tr=udp%3a%2f%2ftracker.srv00.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.theoks.net%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.tiny-vps.com%3a6969%2fannounce&tr=udp%3a%2f%2fopen.tracker.cl%3a1337%2fannounce&tr=udp%3a%2f%2ftracker.zerobytes.xyz%3a1337%2fannounce&tr=udp%3a%2f%2ftracker1.bt.moack.co.kr%3a80%2fannounce&tr=udp%3a%2f%2fvibe.sleepyinternetfun.xyz%3a1738%2fannounce&tr=udp%3a%2f%2fwww.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a6969%2fannounce&tr=udp%3a%2f%2f9.rarbg.com%3a2810%2fannounce&tr=udp%3a%2f%2ftracker.opentrackr.org%3a1337%2fannounce&tr=udp%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fopenbittorrent.com%3a80%2fannounce) using a torrent client, and place it in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Something else
|
||||
{% capture compat %}
|
||||
<summary><u>Something else</u></summary>
|
||||
|
||||
Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance, and describe the message that you see.
|
||||
|
||||
---
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Seedminer
|
||||
|
||||
### Multiple long folder names in Nintendo 3DS folder
|
||||
{% capture compat %}
|
||||
<summary><u>Multiple long folder names in Nintendo 3DS folder</u></summary>
|
||||
|
||||
![]({{ "/images/screenshots/multiple-id0.png" | absolute_url }})
|
||||
{: .notice--info}
|
||||
|
|
@ -49,98 +81,285 @@ This occurs when you use your SD card in multiple 3DS devices and is intended to
|
|||
+ This is your true ID0 that you will use in [Section II of Seedminer](seedminer#section-ii---seedminer)
|
||||
1. Delete the `Nintendo 3DS` folder
|
||||
1. Rename the `BACKUP_Nintendo 3DS` folder to `Nintendo 3DS`
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Bruteforce Movable skips to step 4
|
||||
{% capture compat %}
|
||||
<summary><u>Bruteforce Movable skips to step 4</u></summary>
|
||||
|
||||
The website has already mined your `movable.sed` using your friend code and ID0 combination. You can use the `movable.sed` that it provides you.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Important! You have been locked out of the automated part1 dumper system...
|
||||
{% capture compat %}
|
||||
<summary><u>Important! You have been locked out of the automated part1 dumper system...</u></summary>
|
||||
|
||||
Your friend code was blocked from using the friend code bot because your 3DS did not successfully friend the bot. Ensure your 3DS is properly connected to the Internet, then join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask to be unlocked.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### We were unable to successfully complete your bruteforce request. :`(
|
||||
{% capture compat %}
|
||||
<summary><u>We were unable to successfully complete your bruteforce request. :`(</u></summary>
|
||||
|
||||
The website has determined that your `movable.sed` cannot be brute-forced. Ensure that you gave the correct ID0 to the website. If your ID0 is correct, then you will be unable to use Seedminer and you will have to use an alternate method that will require additional games or hardware.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
## BannerBomb3
|
||||
|
||||
## Homebrew Launcher (PicHaxx)
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management menu crashes without showing BB3 multihax menu</u></summary>
|
||||
Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. If it is, then re-create it with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen).
|
||||
|
||||
### "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
Your `00000001.sav` and/or `otherapp.bin` files may be misplaced. Ensure that `00000001.sav` is in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data` and that `otherapp.bin` is on the root of your SD card.
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow [an alternate branch of Seedminer](homebrew-launcher-(pichaxx)). If Safe Mode doesn't work or you need assistance with this matter, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
If your files are in the correct locations, re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx), then place it in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`. Ensure that the file is named exactly `00000001.sav` and that you used your console's `movable.sed` to create it. Re-download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management menu does not crash</u></summary>
|
||||
|
||||
### "An exception occurred" or Errdisp when opening Picross
|
||||
`F00D43D5.bin` is missing from `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. Make sure that `Nintendo DSiWare` is correctly spelled and spaced. Uppercase/lowercase does not matter.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
Your device already has custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management shows a question mark</u></summary>
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
There may be an issue with your `F00D43D5.bin` file (it may be corrupted or intended for the wrong 3DS). Re-create your `F00D43D5.bin` file with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen), ensuring that you use the `movable.sed` file for your console.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
There is an issue with your `otherapp.bin` file. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
## Installing boot9strap (USM)
|
||||
|
||||
### Game starts normally
|
||||
{% capture compat %}
|
||||
<summary><u>Safe Mode system update succeeds instead of giving error 003-1099</u></summary>
|
||||
|
||||
Your modified `00000001.sav` file may be misplaced, or you may have used the wrong `movable.sed` when creating it. Re-generate your `movable.sed` from [Bruteforce Movable](https://seedminer.hacks.guide), then re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx) and place the resulting file (`00000001.sav`) in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`.
|
||||
unSAFE_MODE is not installed. [Follow the instructions](installing-boot9strap-(usm)] to install it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary><u>Red screen after selecting "Detailed Setup"</u></summary>
|
||||
|
||||
## Installing boot9strap (Soundhax)
|
||||
The file `usm.bin` is missing or misplaced. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/download/v1.3/usm.bin) and place `usm.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
### Red/purple/pink and white screen after running Soundhax
|
||||
There is also a possibility that the console isn't reading your SD card. Make sure it is inserted and formatted correctly.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
If your device is not on those firmwares, it likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
|
||||
There is an issue with your `otherapp.bin` file (it is missing, misplaced, or corrupted). Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) and place it on the root of your SD card.
|
||||
|
||||
### "Could not play"
|
||||
|
||||
You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow [Seedminer](seedminer).
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to mount the SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
## Installing boot9strap (Fredtool)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Error on Fredtool Injector page</u></summary>
|
||||
|
||||
Ensure that your `movable.sed` and DSiWare backup come from the same console. A mismatch will result in an error.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to select "Haxxxxxxxxx!" because the BB3 multihax menu appears</u></summary>
|
||||
|
||||
You forgot to delete `F00D43D5.bin` from the SD card. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card and delete the `F00D43D5.bin` file.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"Haxxxxxxxxx!" does not appear</u></summary>
|
||||
|
||||
There is an issue with your `42383821.bin` file (it is incorrect, missing, misplaced, or corrupted). Re-create your files with the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website and ensure that you place the `42383821.bin` file from `output.zip` -> `hax` in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DS Connection Settings launches normally</u></summary>
|
||||
|
||||
`Haxxxxxxxxx!` was not copied from your SD card to your system memory.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Black screen when launching DS Connection Settings</u></summary>
|
||||
|
||||
Your DS Connection Settings application is broken, and you will need Homebrew Launcher access to fix this issue. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>SD card is grayed out in Flipnote</u></summary>
|
||||
|
||||
Flipnote may take a long time to index your card if you have a large SD card. Let it sit for a few minutes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Lenny face does not appear in SD card section</u></summary>
|
||||
|
||||
You did not copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Flipnote freezes</u></summary>
|
||||
|
||||
You may have accidentally touched the touch screen while in the modified Flipnote. Re-enter DS Connection Settings and try again, ensuring that you don't accidentally use the touchscreen.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Green screen after pasting</u></summary>
|
||||
|
||||
The file `boot.nds` is missing or misplaced. Download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>White screen after pasting</u></summary>
|
||||
There is an issue with your `boot.nds` file. Re-download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to open Luma3DS configuration menu after running B9STool</u></summary>
|
||||
|
||||
It is possible that boot9strap was not successfully installed. Follow section B of [this page](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Homebrew Launcher (PicHaxx)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
|
||||
|
||||
Your `00000001.sav` and/or `otherapp.bin` files may be misplaced. Ensure that `00000001.sav` is in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data` and that `otherapp.bin` is on the root of your SD card.
|
||||
|
||||
If your files are in the correct locations, re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx), then place it in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`. Ensure that the file is named exactly `00000001.sav` and that you used your console's `movable.sed` to create it. Re-download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" or Errdisp when opening Picross</u></summary>
|
||||
|
||||
Your device already has custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `otherapp.bin` file. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Game starts normally</u></summary>
|
||||
|
||||
Your modified `00000001.sav` file may be misplaced, or you may have used the wrong `movable.sed` when creating it. Re-generate your `movable.sed` from [Bruteforce Movable](https://seedminer.hacks.guide), then re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx) and place the resulting file (`00000001.sav`) in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Installing boot9strap (Soundhax)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Soundhax</u></summary>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
If your device is not on those firmwares, it likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `otherapp.bin` file (it is missing, misplaced, or corrupted). Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) and place it on the root of your SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"Could not play"</u></summary>
|
||||
|
||||
You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow [Seedminer](seedminer).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Installing boot9strap (SSLoth-Browser)
|
||||
|
||||
### Red/purple/pink and white screen after running browserhax
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Browserhax</u></summary>
|
||||
|
||||
This likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
|
||||
|
||||
The file `arm11code.bin` is missing or misplaced. Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place `otherapp.bin` on the root of your SD card and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `arm11code.bin` file. Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place `otherapp.bin` on the root of your SD card and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Opening the browserhax QR code or URL crashes
|
||||
{% capture compat %}
|
||||
<summary><u>Opening the browserhax QR code or URL crashes</u></summary>
|
||||
|
||||
Browser based exploits (such as this one) are often unstable and crash frequently, but they can sometimes be fixed by doing the following steps.
|
||||
|
||||
1. Launch the browser, then launch the browser settings
|
||||
1. Scroll to the bottom and Initialize Savedata (it also may be called Clear All Save Data)
|
||||
1. Try the exploit again
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Opening the browser prompts for a system update instead
|
||||
{% capture compat %}
|
||||
<summary><u>System Update prompt when opening browser</u></summary>
|
||||
|
||||
The SSLoth proxy was incorrectly configured. Re-do the SSLoth section on the page.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Error 032-0420 when trying to open the browser
|
||||
{% capture compat %}
|
||||
<summary><u>Error 032-0420 when opening browser</u></summary>
|
||||
|
||||
Follow these steps in order:
|
||||
|
||||
|
|
@ -157,126 +376,47 @@ Follow these steps in order:
|
|||
1. If prompted about a system update, press OK
|
||||
+ This won't actually update the system
|
||||
1. Start again from [Section II](installing-boot9strap-(ssloth-browser).html#section-ii---ssloth)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Frozen on "Doing agbhax..."
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Frozen on "Doing agbhax..."</u></summary>
|
||||
There may be an issue with your `arm11code.bin` file. Re-download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place it on the root of your SD card, and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
If you have a Taiwanese unit (with a T in the version string, ie. 11.3.0-##T), you will not be able to follow these instructions, and you will need to update your console and follow [Seedminer](seedminer) instead.
|
||||
|
||||
If you have a Mainland Chinese unit (with a C in the version string, ie. 11.3.0-##C), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "PrepareArm9ForTwl returned error c8804631!"
|
||||
{% capture compat %}
|
||||
<summary><u>"PrepareArm9ForTwl returned error c8804631!"</u></summary>
|
||||
|
||||
You will need to follow an alternate method. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to mount the SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## BannerBomb3
|
||||
|
||||
### DSiWare Management menu crashes without showing BB3 multihax menu
|
||||
|
||||
Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. If it is, then re-create it with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen).
|
||||
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow [an alternate branch of Seedminer](homebrew-launcher-(pichaxx)). If Safe Mode doesn't work or you need assistance with this matter, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
|
||||
### DSiWare Management menu does not crash
|
||||
|
||||
`F00D43D5.bin` is missing from `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. Make sure that `Nintendo DSiWare` is correctly spelled and spaced. Uppercase/lowercase does not matter.
|
||||
|
||||
### DSiWare Management shows a question mark
|
||||
|
||||
There may be an issue with your `F00D43D5.bin` file (it may be corrupted or intended for the wrong 3DS). Re-create your `F00D43D5.bin` file with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen), ensuring that you use the `movable.sed` file for your console.
|
||||
|
||||
---
|
||||
|
||||
## Installing boot9strap (USM)
|
||||
|
||||
### Update doesn't fail with error code `003-1099`
|
||||
|
||||
unSAFE_MODE is not installed. Follow the instructions on your page to install unSAFE_MODE again.
|
||||
|
||||
### Red screen when selecting detailed setup
|
||||
|
||||
The file `usm.bin` is missing or misplaced. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/download/v1.3/usm.bin) and place `usm.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
There is also a possibility that the console isn't reading your SD card. Make sure it is inserted and formatted correctly.
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
### Failed to mount the SD card!
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
|
||||
---
|
||||
|
||||
## Installing boot9strap (Fredtool)
|
||||
|
||||
### Error on Fredtool Injector page
|
||||
|
||||
Ensure that your `movable.sed` and DSiWare backup come from the same console. A mismatch will result in an error.
|
||||
|
||||
### Unable to select the "Haxxxxxxxxx!" title because of the BB3 multihax menu
|
||||
|
||||
You forgot to delete `F00D43D5.bin` from the SD card. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card and delete the `F00D43D5.bin` file.
|
||||
|
||||
### "Haxxxxxxxxx!" does not appear
|
||||
|
||||
There is an issue with your `42383821.bin` file (it is incorrect, missing, misplaced, or corrupted). Re-create your files with the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website and ensure that you place the `42383821.bin` file from `output.zip` -> `hax` in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`.
|
||||
|
||||
### DS Connection Settings launches normally
|
||||
|
||||
`Haxxxxxxxxx!` was not copied from your SD card to your system memory.
|
||||
|
||||
### Black screen when launching DS Connection Settings
|
||||
|
||||
Your DS Connection Settings application is broken, and you will need Homebrew Launcher access to fix this issue. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
|
||||
### SD card is grayed out
|
||||
|
||||
Flipnote may take a long time to index your card if you have a large SD card. Let it sit for a few minutes.
|
||||
|
||||
### Lenny face does not appear
|
||||
|
||||
You did not copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card.
|
||||
|
||||
### Flipnote is frozen
|
||||
|
||||
You may have accidentally touched the touch screen while in the modified Flipnote. Re-enter DS Connection Settings and try again, ensuring that you don't accidentally use the touchscreen.
|
||||
|
||||
### Green screen after pasting
|
||||
|
||||
The file `boot.nds` is missing or misplaced. Download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
|
||||
### White screen after pasting
|
||||
|
||||
There is an issue with your `boot.nds` file. Re-download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
|
||||
### Unable to open Luma3DS configuration menu after running b9stool
|
||||
|
||||
It is possible that boot9strap was not successfully installed. Follow section B of [this page](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md).
|
||||
|
||||
---
|
||||
|
||||
## Finalizing Setup
|
||||
|
||||
### Unable to update device
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to update device</u></summary>
|
||||
|
||||
The steps below can be attempted in any order, but are listed from easiest to hardest to perform.
|
||||
|
||||
|
|
@ -289,37 +429,41 @@ The steps below can be attempted in any order, but are listed from easiest to ha
|
|||
1. Nintendo servers may be down; Try again later
|
||||
1. If you still get an error, [follow CTRTransfer](ctrtransfer), then try again
|
||||
1. For further support (in English), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Unable to enter Rosalina due to broken button(s)
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to enter Rosalina menu due to broken Left Shoulder / Down D-Pad / Select button(s)</u></summary>
|
||||
|
||||
Download this [alternate config.ini](https://cdn.discordapp.com/attachments/196635695958196224/982798396265988186/config.ini) and place it in `/luma/`. This will change the Rosalina key combination to (X) + (Y).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An exception occurred" after trying to launch Homebrew Launcher via Download Play
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" after trying to launch Homebrew Launcher from Download Play</u></summary>
|
||||
|
||||
There is an issue with your `boot.3dsx` file (it is missing, misplaced, or corrupted). Download the latest release of [the Homebrew Launcher](https://github.com/devkitPro/3ds-hbmenu/releases/latest) and place `boot.3dsx` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "Scripts directory not found" in GodMode9
|
||||
{% capture compat %}
|
||||
<summary><u>"Scripts directory not found" in GodMode9</u></summary>
|
||||
|
||||
You did not copy the `gm9` folder from the GodMode9 `.zip` to the root of your SD card. Download the latest release of [GodMode9](https://github.com/d0k3/GodMode9/releases/latest) and place the `gm9` folder on the root of your SD card, merging it with the existing one.
|
||||
|
||||
### `essentials.exefs` missing from `/gm9/out/`
|
||||
|
||||
Your device had custom firmware in the past, so you were not automatically prompted to make a backup. Make a backup manually:
|
||||
|
||||
1. Reinsert your SD card into your device
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Navigate to `[S:] SYSNAND VIRTUAL`
|
||||
1. Select `essentials.exefs`, then `Copy to 0:/gm9/out/`
|
||||
1. You should now have `essentials.exefs` in `/gm9/out/`
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## Boot-related issues on modded devices
|
||||
## Boot issues on devices with custom firmware
|
||||
|
||||
The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
|
||||
{: .notice--info}
|
||||
|
||||
### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
|
||||
### Power/notification light indicators
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>My device powers off when I try to turn it on, and/or the notification LED shows a color on boot</u></summary>
|
||||
|
||||
There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
|
||||
|
||||
|
|
@ -332,11 +476,15 @@ If the notification LED flashes:
|
|||
You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
|
||||
|
||||
If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### My device gets stuck on a black screen, with a static blue light
|
||||
{% capture compat %}
|
||||
<summary><u>My device gets stuck on a black screen with blue power light staying on</u></summary>
|
||||
|
||||
The steps below can be attempted in any order, but are listed from least to most time-consuming.
|
||||
|
||||
1. Power off your device, remove the SD card, re-insert it, then power on your device.
|
||||
1. Power off your device, eject the game cartridge if inserted, power on your device, then wait up to ten minutes. If your device boots within ten minutes, the issue has been fixed and is unlikely to reoccur
|
||||
1. Rename the `Nintendo 3DS` folder on your SD card to `Nintendo 3DS_BACKUP`, then attempt to boot. If your device successfully boots, there is some issue within your `Nintendo 3DS` folder. Try clearing HOME Menu extdata:
|
||||
+ Navigate to `/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/`
|
||||
|
|
@ -354,35 +502,48 @@ The steps below can be attempted in any order, but are listed from least to most
|
|||
+ If you were successful, the device will boot to an "update your system" screen
|
||||
1. Follow the [CTRTransfer](ctrtransfer) guide
|
||||
1. For further support, ask for help at [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### My device boots to an error screen
|
||||
### Error message on boot
|
||||
|
||||
#### "An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"</u></summary>
|
||||
|
||||
Your Luma3DS version is outdated. Download the latest release of [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### "An error has occurred. Hold down the POWER button to turn off the power..."
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..."</u></summary>
|
||||
|
||||
ARM11 exception handlers are disabled, or custom firmware is not installed. Try enabling ARM11 exception handlers:
|
||||
+ Power off your device
|
||||
+ Hold (Select)
|
||||
+ Power on your device, while still holding (Select)
|
||||
+ If the "Disable ARM11 exception handlers" box is checked, uncheck it
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Some other error
|
||||
|
||||
Please take a photo of the error and join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
|
||||
### Blue "Bootrom Error" screen
|
||||
{% capture compat %}
|
||||
<summary><u>Blue "BOOTROM ERROR" screen</u></summary>
|
||||
|
||||
Your device is likely hard-bricked. You will need to buy an ntrboot flashcart to reinstall boot9strap in order to attempt to fix your device. This may also indicate a hardware issue that cannot be fixed. In any case, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
+ It is also possible that someone has set a boot-time splash screen that just looks like a brick. Try leaving your device powered on, waiting on the blue screen, for five minutes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary><u>Some other error</u></summary>
|
||||
|
||||
## Functionality-related issues on modded devices
|
||||
Please take a photo of the error and join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### DSi / DS functionality is broken or has been replaced with Flipnote Studio
|
||||
## Software issues on devices with custom firmware
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DSi / DS functionality is broken or has been replaced with Flipnote Studio</u></summary>
|
||||
|
||||
1. Download the latest release of [TWLFix-CFW](https://github.com/MechanicalDragon0687/TWLFix-CFW/releases/latest) (the `.3dsx` file)
|
||||
1. Power off your device
|
||||
|
|
@ -396,20 +557,29 @@ Your device is likely hard-bricked. You will need to buy an ntrboot flashcart to
|
|||
1. Perform a System Update by going to System Settings, then "Other Settings", then going all the way to the right and using "System Update"
|
||||
+ The update will see that the essential TWL titles have been uninstalled, and will redownload and reinstall them
|
||||
1. Once the update is complete, tap "OK" to reboot the device
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### GBA Virtual Console and/or Safe Mode functionality is broken
|
||||
{% capture compat %}
|
||||
<summary><u>GBA Virtual Console and/or Safe Mode functionality is broken</u></summary>
|
||||
|
||||
Your device is running Luma3DS/AuReiNand 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your device to a modern custom firmware environment.
|
||||
Your device is running Luma3DS 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your device to a modern custom firmware environment.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Extended memory mode games are broken
|
||||
{% capture compat %}
|
||||
<summary><u>Extended memory mode games (Pokemon Sun/Moon, Smash, etc.) don't work</u></summary>
|
||||
|
||||
This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will need to system format your device to fix this issue.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## Other troubleshooting
|
||||
|
||||
### Clear HOME Menu extdata
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu extdata</u></summary>
|
||||
|
||||
1. Power off your device
|
||||
1. Insert your SD card into your computer
|
||||
|
|
@ -422,8 +592,11 @@ This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will n
|
|||
+ **KOR Region**: `000000A9`
|
||||
+ **TWN Region**: `000000B1`
|
||||
1. Reinsert your SD card into your device
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Clear HOME Menu theme data
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu theme data</u></summary>
|
||||
|
||||
1. Power off your device
|
||||
1. Insert your SD card into your computer
|
||||
|
|
@ -433,3 +606,6 @@ This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will n
|
|||
+ **JPN Region**: `000002cc`
|
||||
+ **USA Region**: `000002cd`
|
||||
1. Reinsert your SD card into your device
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@ The purpose of this section is to check whether built-in DS mode applications wi
|
|||
+ If your console displays the Japanese version of Flipnote Studio, a black screen, or an error message, the test has failed
|
||||
1. Power off your device
|
||||
|
||||
If either of these tests has failed, DS mode, DS Download Play, and/or DS Connection Settings may be inaccessible once CFW is uninstalled! You should [fix DS mode](troubleshooting#dsi--ds-functionality-is-broken-or-has-been-replaced-with-flipnote-studio) before continuing.
|
||||
If either of these tests has failed, DS mode, DS Download Play, and/or DS Connection Settings may be inaccessible once CFW is uninstalled! You should [fix DS mode](troubleshooting#software-issues-on-devices-with-custom-firmware) before continuing.
|
||||
{: .notice--warning}
|
||||
|
||||
#### Section III - Safety Test
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ Beachte, dass auf dem New 3DS die `secret_sector.bin` benötigt wird, um den arm
|
|||
1. Dein Gerät sollte neu starten und die Luma3DS Konfiguration anzeigen
|
||||
+ 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 get a black screen, [follow this troubleshooting guide](troubleshooting#boot-related-issues-on-modded-devices)
|
||||
+ If you get a black screen, [follow this troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware)
|
||||
1. Drücke (Start) zum Speichern und neustarten
|
||||
|
||||
___
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ This is an add-on section to check if your console already has a modern custom f
|
|||
|
||||
If your console already has an arm9loaderhax or boot9strap based custom firmware, you will need to follow the instructions indicated to upgrade your setup to a modern one.
|
||||
|
||||
If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#clear-home-menu-extdata), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
|
||||
If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#other-troubleshooting), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
|
||||
{: .notice--info}
|
||||
|
||||
### Anleitung
|
||||
|
|
|
|||
|
|
@ -14,79 +14,173 @@ Wenn auf deiner Konsole *Luma 11.0* läuft, ist es *100% sicher* zu updaten. Du
|
|||
|
||||
## FAQ vor der Installation
|
||||
|
||||
#### **Q:** *I am on the latest system version. Is my device hackable without any external hardware?*
|
||||
**A:** Yes! Die neuste Firmware (11.16.0) besitzt eine kostenlose Methode namens [Seedminer](seedminer), um CFW zu installieren.
|
||||
{% capture compat %}
|
||||
<summary><u>I am on the latest system version. Is my device hackable without any external hardware?</u></summary>
|
||||
|
||||
#### **Q:** *What devices is this guide compatible with?*
|
||||
**A:** The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. Wenn deine Systemversion als "0.0.0-0" angezeigt, hast du möglicherweise eine Entwicklereinheit.
|
||||
Yes! Die neuste Firmware (11.16.0) besitzt eine kostenlose Methode namens [Seedminer](seedminer), um CFW zu installieren.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How risky is hacking my console?*
|
||||
**A:** Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
{% capture compat %}
|
||||
<summary><u>What devices is this guide compatible with?</u></summary>
|
||||
|
||||
#### **Q:** *Can I run awesome homebrew and emulators with this?*
|
||||
**A:** Yes! Diese Anleitung wird nützliche Homebrew-Apps instalieren, darunter den Universal-Updater (siehe https://github.com/Universal-Team/Universal-Updater/releases/latest), eine Art Homebrew App Store.
|
||||
The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. Wenn deine Systemversion als "0.0.0-0" angezeigt, hast du möglicherweise eine Entwicklereinheit.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I use this to play games from other regions?*
|
||||
**A:** Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Some games may need to make use of Luma's [locale emulation feature](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) in order to work properly on out-of-region devices.
|
||||
{% capture compat %}
|
||||
<summary><u>How risky is hacking my console?</u></summary>
|
||||
|
||||
#### **Q:** *Will I lose any features if I install CFW?*
|
||||
**A:** No. Konsolen mit Custom Firmware können immer noch den eShop und Cartridges wie jeder andere 3DS benutzen.
|
||||
Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I keep my NNID?*
|
||||
**A:** Your NNID (if you have one) will not be affected by this guide. Konsolen mit KOR, CHN, oder TWN Region haben sowieso keine NNID Funktionalität und sind daher nicht betroffen.
|
||||
{% capture compat %}
|
||||
<summary><u>Can I run awesome homebrew and emulators with this?</u></summary>
|
||||
|
||||
#### **Q:** *Will my 3DS be banned for having CFW?*
|
||||
**A:** There was a ban wave in May 2017 that banned CFW users from online play (eShop access, NNIDs, and Nintendo Accounts were unaffected), seemingly at random. Seitdem hat man so eine Ban-Welle nicht gesehen. Trotzdem wissen wir nicht, was wir von Nintendo in Zukunft erwarten können. Im Moment denken wir nicht, dass Bans etwas sind, dass du beachten musst.
|
||||
Yes! Diese Anleitung wird nützliche Homebrew-Apps instalieren, darunter den Universal-Updater (siehe https://github.com/Universal-Team/Universal-Updater/releases/latest), eine Art Homebrew App Store.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I do this without a computer (e.g. an Android phone)?*
|
||||
**A:** All you need is the ability to put files on a compatible SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Can I use this to play games from other regions?</u></summary>
|
||||
|
||||
#### **Q:** *What size SD card can I use?*
|
||||
**A:** You will need at least 1.5GB of free SD card space to follow this guide in its entirety. Während der 3DS offiziell mit SD-Karten bis zu 32GB kompatibel ist, können größere SD-Karten verwendet werden, wenn sie manuell als FAT32 formatiert werden. Es wird nicht empfohlen, SD-Karten größer als 128GB zu verwenden, da bekannte Probleme mit GBA-Grafiken und benutzerdefinierten Designs auftreten.
|
||||
Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Some games may need to make use of Luma's [locale emulation feature](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) in order to work properly on out-of-region devices.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *I heard about this thing I have to pay for (Gateway, Sky3DS, ntrboot, R4, etc). Is that something I need?*
|
||||
**A:** No. Custom Firmware kann kostenlos auf der neusten Firmware ohne zusätzliche Hardware installiert werden. Darüber hinaus sind 3DS-mode Flashkarten wie Gateway und Sky3DS nicht empfohlen, da sie veraltet sind und Ban- und Brickrisiken mit sich bringen können.
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose any features if I install CFW?</u></summary>
|
||||
|
||||
#### **Q:** *What's the difference between custom firmware and homebrew access?*
|
||||
**A:** Historically, the 3DS used to have userland homebrew access through older exploits like ninjhax. Das mit Userland gewährte Niveau des Systemzugriffs erlaubt es dir, grundlegendes Homebrew und Emulatoren zu benutzen, hat dir aber nicht erlaubt, Spiele (einfach) zu modifizieren oder Cartridges zu dumpen. Es war auch viel instabiler, alles ist öfters gecrasht und brauchte einen vollen Neustart. Custom Firmware erlaubt ein viel besseres Niveau des Systemzugriffes und ist auch viel stabiler als Nur-Homebrew Entrypoints.
|
||||
No. Konsolen mit Custom Firmware können immer noch den eShop und Cartridges wie jeder andere 3DS benutzen.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I keep my NNID?</u></summary>
|
||||
|
||||
Your NNID (if you have one) will not be affected by this guide. Konsolen mit KOR, CHN, oder TWN Region haben sowieso keine NNID Funktionalität und sind daher nicht betroffen.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will my 3DS be banned for having CFW?</u></summary>
|
||||
|
||||
There was a ban wave in May 2017 that banned CFW users from online play (eShop access, NNIDs, and Nintendo Accounts were unaffected), seemingly at random. Seitdem hat man so eine Ban-Welle nicht gesehen. Trotzdem wissen wir nicht, was wir von Nintendo in Zukunft erwarten können. Im Moment denken wir nicht, dass Bans etwas sind, dass du beachten musst.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I do this without a computer (e.g. an Android phone)?</u></summary>
|
||||
|
||||
Yes! All you need is the ability to put files on a compatible SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What size SD card can I use?</u></summary>
|
||||
|
||||
You will need at least 1.5GB of free SD card space to follow this guide in its entirety. Während der 3DS offiziell mit SD-Karten bis zu 32GB kompatibel ist, können größere SD-Karten verwendet werden, wenn sie manuell als FAT32 formatiert werden. Es wird nicht empfohlen, SD-Karten größer als 128GB zu verwenden, da bekannte Probleme mit GBA-Grafiken und benutzerdefinierten Designs auftreten.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>I heard about this thing I have to pay for (Gateway, Sky3DS, ntrboot, R4, etc). Is that something I need?</u></summary>
|
||||
|
||||
No. Custom Firmware kann kostenlos auf der neusten Firmware ohne zusätzliche Hardware installiert werden. Darüber hinaus sind 3DS-mode Flashkarten wie Gateway und Sky3DS nicht empfohlen, da sie veraltet sind und Ban- und Brickrisiken mit sich bringen können.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What's the difference between custom firmware and homebrew?</u></summary>
|
||||
|
||||
Historically, the 3DS used to have userland homebrew access through older exploits like ninjhax. Das mit Userland gewährte Niveau des Systemzugriffs erlaubt es dir, grundlegendes Homebrew und Emulatoren zu benutzen, hat dir aber nicht erlaubt, Spiele (einfach) zu modifizieren oder Cartridges zu dumpen. Es war auch viel instabiler, alles ist öfters gecrasht und brauchte einen vollen Neustart. Custom Firmware erlaubt ein viel besseres Niveau des Systemzugriffes und ist auch viel stabiler als Nur-Homebrew Entrypoints.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Post-Installation FAQ
|
||||
|
||||
#### **Q:** *Is it safe to update my 3DS to the latest version with CFW?*
|
||||
**A:** If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. Es gab Updates in der Vergangenheit, die Luma3DS beim Hochfahren zum Crashen gebracht haben, also ist es eine gute Idee, ein paar Stunden zu warten, um sicherzustellen, dass das Update sicher ist, damit deine Konsole nicht temporär nicht mehr funktioniert bis Luma3DS geupdated ist. Ein System Update kann genau wie auf einer regulären Konsole durchgeführt werden: System Einstellungen, Recovery-Modus oder durch die Update-Notifikation wenn das Update schon heruntergeladen ist.
|
||||
{% capture compat %}
|
||||
<summary><u>Is it safe to update my 3DS to the latest version with CFW?</u></summary>
|
||||
|
||||
#### **Q:** *How do I upgrade my SD card?*
|
||||
**A:** Copy and paste your SD card contents to a new SD card formatted as FAT32. Für 128 GB Karten wird eine Allocation Unit Size von 65536 empfohlen. SD-Karten größer als 128GB werden aufgrund bekannter Probleme mit GBA-Grafiken und benutzerdefinierten Designs nicht empfohlen.
|
||||
If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. Es gab Updates in der Vergangenheit, die Luma3DS beim Hochfahren zum Crashen gebracht haben, also ist es eine gute Idee, ein paar Stunden zu warten, um sicherzustellen, dass das Update sicher ist, damit deine Konsole nicht temporär nicht mehr funktioniert bis Luma3DS geupdated ist. Ein System Update kann genau wie auf einer regulären Konsole durchgeführt werden: System Einstellungen, Recovery-Modus oder durch die Update-Notifikation wenn das Update schon heruntergeladen ist.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I system transfer with CFW?*
|
||||
**A:** Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets für unechte Titel (Homebrew) werden nicht übertragen, aber die Titel können mit [faketik](https://github.com/ihaveamac/faketik/releases/latest) wieder erscheinen. Überprüfe nochmals, dass du keinen drahtlosen Datentransfer machst, da dies unechte Titel löschen wird. CFW wird auf beiden Konsolen erhalten bleiben.
|
||||
{% capture compat %}
|
||||
<summary><u>How do I upgrade my SD card?</u></summary>
|
||||
|
||||
#### **Q:** *How do I change the system language of a Japanese 3DS?*
|
||||
**A:** The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Beachte, dass dies sehr wahrscheinlich die Funktionalität des Nintendo eShop auf deinem Gerät beschädigt. Dies bedeutet, dass du deine Spiele nicht mehr aktualisieren werden kannst, obgleich du dich innerhalb oder außerhalb der Region befindest.
|
||||
Copy and paste your SD card contents to a new SD card formatted as FAT32. Für 128 GB Karten wird eine Allocation Unit Size von 65536 empfohlen. SD-Karten größer als 128GB werden aufgrund bekannter Probleme mit GBA-Grafiken und benutzerdefinierten Designs nicht empfohlen.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How do I update homebrew applications?*
|
||||
**A:** It depends on the format of the homebrew application. Allgemein gesagt:
|
||||
{% capture compat %}
|
||||
<summary><u>Can I system transfer with CFW?</u></summary>
|
||||
|
||||
Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets für unechte Titel (Homebrew) werden nicht übertragen, aber die Titel können mit [faketik](https://github.com/ihaveamac/faketik/releases/latest) wieder erscheinen. Überprüfe nochmals, dass du keinen drahtlosen Datentransfer machst, da dies unechte Titel löschen wird. CFW wird auf beiden Konsolen erhalten bleiben.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I change the system language of a Japanese 3DS?</u></summary>
|
||||
|
||||
The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Beachte, dass dies sehr wahrscheinlich die Funktionalität des Nintendo eShop auf deinem Gerät beschädigt. Dies bedeutet, dass du deine Spiele nicht mehr aktualisieren werden kannst, obgleich du dich innerhalb oder außerhalb der Region befindest.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I update homebrew applications?</u></summary>
|
||||
|
||||
It depends on the format of the homebrew application. Allgemein gesagt:
|
||||
|
||||
* Homebrew im **CIA Format** kann durch Installieren einer neuen CIA aktualisiert werden, was normalerweise die alte Version überschreibt. Wenn die alte CIA nicht überschrieben wird, kannst du die Alte aus der Datenverwaltung löschen, wie du es auch bei jedem anderen 3DS-Titel tun würdest.
|
||||
* Homebrew im **3DSX Format** kann durch Ersetzen der 3DSX Datei in `/3ds/` mit einer neuen Kopie aktualisiert werden. Wenn die Anwendung zusätzliche Assets enthält, musst du diese vielleicht in einem anderen Ordner ersetzen. Lies dafür die Dokumentation der Homebrew Anwendung.
|
||||
* Zum Updaten von Luma3DS, gehe auf [diese Seite](restoring-updating-cfw). Zum Updaten von GodMode9, gehe auf [diese Seite](godmode9-usage#updating-godmode9).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How do I update games from outside of my 3DS region?*
|
||||
**A:** You will need to [dump the updates](dumping-titles-and-game-cartridges) from a 3DS that has the updates installed. Der Nintendo eShop enthält nur Updates für die Region der Konsole(ein Japanischer 3DS wird nur Updates für japanische Spiele haben).
|
||||
{% capture compat %}
|
||||
<summary><u>How do I update my games?</u></summary>
|
||||
|
||||
#### **Q:** *Help! Something bad happened and now I cannot boot...*
|
||||
**A:** Please look at the [troubleshooting guide](troubleshooting). **Das Deinstallieren von CFW wenn dein Gerät in einem unbootbaren Zustand ist, wird nicht empfohlen, da es sehr wahrscheinlich zu einem Brick führen wird**.
|
||||
You can continue to download game updates from the Nintendo eShop, even after the 2023 shutdown.
|
||||
|
||||
If the game is not from the same region as the console, you will need to [dump the updates](dumping-titles-and-game-cartridges) from a 3DS that has the updates installed. Der Nintendo eShop enthält nur Updates für die Region der Konsole(ein Japanischer 3DS wird nur Updates für japanische Spiele haben).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Help! Something bad happened and my 3DS won't boot to HOME Menu...</u></summary>
|
||||
|
||||
Please look at the [troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware). **Das Deinstallieren von CFW wenn dein Gerät in einem unbootbaren Zustand ist, wird nicht empfohlen, da es sehr wahrscheinlich zu einem Brick führen wird**.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## menuhax / A9LH / Gateway FAQ
|
||||
|
||||
#### **Q:** *I modded my device x years ago. What should I do?*
|
||||
**A:** It is recommended that you upgrade your setup to a modern, boot9strap-based one. Follow the [Checking for CFW](checking-for-cfw) guide to see how to upgrade your setup.
|
||||
{% capture compat %}
|
||||
<summary><u>I modded my device (x) years ago, so it already has some sort of homebrew. What should I do?</u></summary>
|
||||
|
||||
#### **Q:** *My setup works for me. Why should I upgrade it?*
|
||||
**A:** The vast majority of modern homebrew (such as Checkpoint and BootNTR Selector) have only been tested on modern, boot9strap-based setups and may not work entirely (or at all) on older setups based on menuhax, A9LH, or Gateway. In addition, depending on your setup, you may be unable to safely update to the latest firmware. Moderne, boot9strap-basierte Setups erlauben einen höheren Grad an Systemzugriff als frühere Hacks, einschließlich der Möglichkeit, die Bootrom deiner Konsole zu dumpen.
|
||||
It is recommended that you upgrade your setup to a modern, boot9strap-based one. Follow the [Checking for CFW](checking-for-cfw) guide to see how to upgrade your setup.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Will I lose anything if I upgrade my setup?*
|
||||
**A:** Your old setup (including your EmuNAND, if you have one) can usually be directly migrated to boot9strap with no data loss. Wenn du Daten hast, die dir sehr wichtig sind, ist es eine gute Idee eine entschlüsselte Kopie von deinen Speicherdaten mit einem Tool wie [JKSM](https://github.com/J-D-K/JKSM/releases/tag/12%2F20%2F2018) zu erstellen bevor du ein Setup upgradest.
|
||||
{% capture compat %}
|
||||
<summary><u>My setup works for me. Why should I upgrade it?</u></summary>
|
||||
|
||||
The vast majority of modern homebrew (such as Checkpoint and BootNTR Selector) have only been tested on modern, boot9strap-based setups and may not work entirely (or at all) on older setups based on menuhax, A9LH, or Gateway. In addition, depending on your setup, you may be unable to safely update to the latest firmware. Moderne, boot9strap-basierte Setups erlauben einen höheren Grad an Systemzugriff als frühere Hacks, einschließlich der Möglichkeit, die Bootrom deiner Konsole zu dumpen.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose anything if I upgrade my setup?</u></summary>
|
||||
|
||||
Your old setup (including your EmuNAND, if you have one) can usually be directly migrated to boot9strap with no data loss. Wenn du Daten hast, die dir sehr wichtig sind, ist es eine gute Idee eine entschlüsselte Kopie von deinen Speicherdaten mit einem Tool wie [JKSM](https://github.com/J-D-K/JKSM/releases/tag/12%2F20%2F2018) zu erstellen bevor du ein Setup upgradest.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I move saves from an existing Gateway setup to a more modern setup?</u></summary>
|
||||
|
||||
#### **Q:** *How do I move saves from an existing Gateway setup to a more modern setup?*
|
||||
**A:** Lies [diesen Thread](https://gbatemp.net/threads/425743/).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@ In this section, you will update your system to the latest version, which is saf
|
|||
+ Updates mit B9S + Luma (welches du hast) sind sicher
|
||||
+ The updater may display a message saying "Your system is up to date" instead of updating. This is normal if you are already up to date; continue with the next section
|
||||
+ If this gives you an error, set both your DNS settings and Proxy settings to "auto"
|
||||
+ If this still gives you an error, [follow this troubleshooting guide](troubleshooting#unable-to-update-device)
|
||||
+ If this still gives you an error, [follow this troubleshooting guide](troubleshooting#finalizing-setup)
|
||||
|
||||
#### Abschnitt III - Homebrew Launcher
|
||||
|
||||
|
|
@ -119,7 +119,7 @@ In this section, you will install several useful homebrew applications to HOME M
|
|||
|
||||
In this section, you will use a script to copy some of Luma3DS's files to internal memory so that they can be accessed, even without an SD card inserted.
|
||||
|
||||
1. Schalte deinen 3DS aus
|
||||
1. Schalte dein Gerät aus
|
||||
1. Drücke und halte (Start), und während du (Start) hältst, schalte deinen 3DS an. This will launch GodMode9
|
||||
+ If you do not boot into GodMode9, ensure that `GodMode9.firm` is in `/luma/payloads/` and that `payloads` is correctly spelled
|
||||
1. Wenn du aufgefordert wirst, ein "essential files backup" durchzuführen, drücke (A). Drücke erneut (A) nachdem es abgeschlossen ist
|
||||
|
|
@ -169,7 +169,7 @@ In this section, you will make backups of files that can be used to recover from
|
|||
1. Lösche `<date>_<serialnumber>_sysnand_###.bin` und `<date>_<serialnumber>_sysnand_###.bin.sha`aus dem `/gm9/out/` Ordner der SD-Karte nachdem du diese kopiert hast
|
||||
+ The other backup files are negligible in size and may be kept on your SD card for ease of access
|
||||
1. If you have it, copy the `/luma/backups/` folder on your SD card to a safe location on your computer
|
||||
1. Stecke deine SD-Karte nun wieder in deinen 3DS
|
||||
1. Stecke deine SD-Karte wieder in dein Gerät
|
||||
1. Schalte deine Konsole an
|
||||
|
||||
___
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
|||
1. Launch System Settings on your device
|
||||
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#dsiware-management-menu-crashes-without-showing-bb3-multihax-menu)
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#installing-boot9strap-fredtool)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Dump DSiWare"
|
||||
+ Your device will automatically reboot
|
||||
1. Schalte deinen 3DS aus
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
|||
1. Launch System Settings on your device
|
||||
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#dsiware-management-menu-crashes-without-showing-bb3-multihax-menu)
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#bannerbomb3)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Install unSAFE_MODE"
|
||||
+ Your device will automatically power off
|
||||
|
||||
|
|
|
|||
|
|
@ -157,7 +157,7 @@ Betätige dazu zeitgleich die Tasten (R) und (A) im GodMode9 Hauptmenü und wäh
|
|||
1. Drücke (HOME) um das Aktionsmenü aufzurufen
|
||||
1. Wähle "More..."
|
||||
1. Wähle "SD format menu"
|
||||
1. Drücke (A), um zu bestätigen
|
||||
1. Drücke (A) um zu bestätigen
|
||||
1. Wähle "No EmuNAND"
|
||||
1. Wähle "Auto"
|
||||
1. Drücke (A), um den Namen `GM9SD` zu akzeptieren
|
||||
|
|
@ -170,7 +170,6 @@ Betätige dazu zeitgleich die Tasten (R) und (A) im GodMode9 Hauptmenü und wäh
|
|||
1. Stecke deine SD-Karte nun wieder in deinen 3DS
|
||||
1. Drücke (A) um die SD-Karte einzuhängen
|
||||
1. Drücke (Start), um das System neu zu starten
|
||||
1. If you get a black screen, [follow this troubleshooting guide](troubleshooting#ts_sys_down)
|
||||
|
||||
___
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ In this section, you will get the necessary details from your 3DS that are requi
|
|||
+ If you don't have a `Nintendo 3DS` folder, put your SD card into your 3DS and power it on so that the folder can be created
|
||||
1. Copy the name of the 32-letter folder you see directly inside Nintendo 3DS
|
||||
+ This 32-letter name is system-specific and will be different for each console
|
||||
+ If you see multiple 32-letter folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
|
||||
+ If you see multiple 32-letter folders, follow [these instructions](troubleshooting#seedminer)
|
||||
+ You can ignore the `private` folder if you have it
|
||||
|
||||
![]({{ "/images/screenshots/seedminer/id0-example.png" | absolute_url }})
|
||||
|
|
|
|||
|
|
@ -2,37 +2,69 @@
|
|||
title: "Problembehandlung"
|
||||
---
|
||||
|
||||
{% include toc title="Inhalt"%}
|
||||
|
||||
This page offers troubleshooting advice for commonly encountered issues. If you are unable to solve your issue with the advice on this page, please join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and describe your issue, including what you have already tried.
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary>Table of Contents</summary>
|
||||
|
||||
Used on multiple pages:
|
||||
* [SafeB9SInstaller](#issues-with-safeb9sinstaller)
|
||||
|
||||
Guide pages:
|
||||
* [Seedminer](#seedminer)
|
||||
* [BannerBomb3](#bannerbomb3)
|
||||
* [Installing boot9strap (USM)](#installing-boot9strap-usm)
|
||||
* [Installing boot9strap (Fredtool)](#installing-boot9strap-fredtool)
|
||||
* [Homebrew Launcher (PicHaxx)](#homebrew-launcher-pichaxx)
|
||||
* [Installing boot9strap (Soundhax)](#installing-boot9strap-soundhax)
|
||||
* [Installing boot9strap (SSLoth-Browser)](#installing-boot9strap-ssloth-browser)
|
||||
|
||||
* [Finalizing Setup](#finalizing-setup)
|
||||
|
||||
Issues after installation:
|
||||
* [Boot issues](#boot-issues-on-devices-with-custom-firmware)
|
||||
* [Software issues](#software-issues-on-devices-with-custom-firmware)
|
||||
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
{: .notice--info}
|
||||
|
||||
## Issues with SafeB9SInstaller
|
||||
|
||||
### SigHaxed FIRM was not installed! Check lower screen for more info.
|
||||
|
||||
#### SigHaxed FIRM - File not found
|
||||
{% capture compat %}
|
||||
<summary><u>SigHaxed FIRM - File not found</u></summary>
|
||||
|
||||
You are missing `boot9strap.firm` and `boot9strap.firm.sha` from the `boot9strap` folder, or the `boot9strap` folder is misnamed. Download the latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip), and place `boot9strap.firm` and `boot9strap.firm.sha` in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### SigHaxed FIRM - invalid FIRM
|
||||
{% capture compat %}
|
||||
<summary><u>SigHaxed FIRM - invalid FIRM</u></summary>
|
||||
|
||||
There is an issue with your `boot9strap.firm` and `boot9strap.firm.sha` files. Re-download the latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip), and place `boot9strap.firm` and `boot9strap.firm.sha` in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Secret Sector - File not found
|
||||
{% capture compat %}
|
||||
<summary><u>Secret Sector - File not found</u></summary>
|
||||
|
||||
You are missing `secret_sector.bin` from the `boot9strap` folder, or the `boot9strap` folder is misnamed. Download [secret_sector.bin](magnet:?xt=urn:btih:15a3c97acf17d67af98ae8657cc66820cc58f655&dn=secret_sector.bin&tr=udp%3a%2f%2ftracker.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.lelux.fi%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.loadbt.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.moeking.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.monitorit4.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.ololosh.space%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.pomf.se%3a80%2fannounce&tr=udp%3a%2f%2ftracker.srv00.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.theoks.net%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.tiny-vps.com%3a6969%2fannounce&tr=udp%3a%2f%2fopen.tracker.cl%3a1337%2fannounce&tr=udp%3a%2f%2ftracker.zerobytes.xyz%3a1337%2fannounce&tr=udp%3a%2f%2ftracker1.bt.moack.co.kr%3a80%2fannounce&tr=udp%3a%2f%2fvibe.sleepyinternetfun.xyz%3a1738%2fannounce&tr=udp%3a%2f%2fwww.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a6969%2fannounce&tr=udp%3a%2f%2f9.rarbg.com%3a2810%2fannounce&tr=udp%3a%2f%2ftracker.opentrackr.org%3a1337%2fannounce&tr=udp%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fopenbittorrent.com%3a80%2fannounce) using a torrent client, and place it in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Something else
|
||||
{% capture compat %}
|
||||
<summary><u>Something else</u></summary>
|
||||
|
||||
Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance, and describe the message that you see.
|
||||
|
||||
---
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Seedminer
|
||||
|
||||
### Multiple long folder names in Nintendo 3DS folder
|
||||
{% capture compat %}
|
||||
<summary><u>Multiple long folder names in Nintendo 3DS folder</u></summary>
|
||||
|
||||
![]({{ "/images/screenshots/multiple-id0.png" | absolute_url }})
|
||||
{: .notice--info}
|
||||
|
|
@ -49,98 +81,285 @@ This occurs when you use your SD card in multiple 3DS devices and is intended to
|
|||
+ This is your true ID0 that you will use in [Section II of Seedminer](seedminer#section-ii---seedminer)
|
||||
1. Delete the `Nintendo 3DS` folder
|
||||
1. Rename the `BACKUP_Nintendo 3DS` folder to `Nintendo 3DS`
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Bruteforce Movable skips to step 4
|
||||
{% capture compat %}
|
||||
<summary><u>Bruteforce Movable skips to step 4</u></summary>
|
||||
|
||||
The website has already mined your `movable.sed` using your friend code and ID0 combination. You can use the `movable.sed` that it provides you.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Important! You have been locked out of the automated part1 dumper system...
|
||||
{% capture compat %}
|
||||
<summary><u>Important! You have been locked out of the automated part1 dumper system...</u></summary>
|
||||
|
||||
Your friend code was blocked from using the friend code bot because your 3DS did not successfully friend the bot. Ensure your 3DS is properly connected to the Internet, then join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask to be unlocked.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### We were unable to successfully complete your bruteforce request. :`(
|
||||
{% capture compat %}
|
||||
<summary><u>We were unable to successfully complete your bruteforce request. :`(</u></summary>
|
||||
|
||||
The website has determined that your `movable.sed` cannot be brute-forced. Ensure that you gave the correct ID0 to the website. If your ID0 is correct, then you will be unable to use Seedminer and you will have to use an alternate method that will require additional games or hardware.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
## BannerBomb3
|
||||
|
||||
## Homebrew Launcher (PicHaxx)
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management menu crashes without showing BB3 multihax menu</u></summary>
|
||||
Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. If it is, then re-create it with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen).
|
||||
|
||||
### "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
Your `00000001.sav` and/or `otherapp.bin` files may be misplaced. Ensure that `00000001.sav` is in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data` and that `otherapp.bin` is on the root of your SD card.
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow [an alternate branch of Seedminer](homebrew-launcher-(pichaxx)). If Safe Mode doesn't work or you need assistance with this matter, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
If your files are in the correct locations, re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx), then place it in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`. Ensure that the file is named exactly `00000001.sav` and that you used your console's `movable.sed` to create it. Re-download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Füge die `.bin` Erweiterung nicht hinzu, wenn du sie noch nicht siehst.
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management menu does not crash</u></summary>
|
||||
|
||||
### "An exception occurred" or Errdisp when opening Picross
|
||||
`F00D43D5.bin` is missing from `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. Make sure that `Nintendo DSiWare` is correctly spelled and spaced. Uppercase/lowercase does not matter.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
Your device already has custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management shows a question mark</u></summary>
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
There may be an issue with your `F00D43D5.bin` file (it may be corrupted or intended for the wrong 3DS). Re-create your `F00D43D5.bin` file with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen), ensuring that you use the `movable.sed` file for your console.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
There is an issue with your `otherapp.bin` file. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Füge die `.bin` Erweiterung nicht hinzu, wenn du sie noch nicht siehst.
|
||||
## Installing boot9strap (USM)
|
||||
|
||||
### Game starts normally
|
||||
{% capture compat %}
|
||||
<summary><u>Safe Mode system update succeeds instead of giving error 003-1099</u></summary>
|
||||
|
||||
Your modified `00000001.sav` file may be misplaced, or you may have used the wrong `movable.sed` when creating it. Re-generate your `movable.sed` from [Bruteforce Movable](https://seedminer.hacks.guide), then re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx) and place the resulting file (`00000001.sav`) in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`.
|
||||
unSAFE_MODE is not installed. [Follow the instructions](installing-boot9strap-(usm)] to install it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary><u>Red screen after selecting "Detailed Setup"</u></summary>
|
||||
|
||||
## Installing boot9strap (Soundhax)
|
||||
The file `usm.bin` is missing or misplaced. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/download/v1.3/usm.bin) and place `usm.bin` on the root of your SD card. Füge die `.bin` Erweiterung nicht hinzu, wenn du sie noch nicht siehst.
|
||||
|
||||
### Red/purple/pink and white screen after running Soundhax
|
||||
There is also a possibility that the console isn't reading your SD card. Make sure it is inserted and formatted correctly.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
If your device is not on those firmwares, it likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
|
||||
There is an issue with your `otherapp.bin` file (it is missing, misplaced, or corrupted). Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) and place it on the root of your SD card.
|
||||
|
||||
### "Could not play"
|
||||
|
||||
You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow [Seedminer](seedminer).
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Füge die `.bin` Erweiterung nicht hinzu, wenn du sie noch nicht siehst.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to mount the SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
## Installing boot9strap (Fredtool)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Error on Fredtool Injector page</u></summary>
|
||||
|
||||
Ensure that your `movable.sed` and DSiWare backup come from the same console. A mismatch will result in an error.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to select "Haxxxxxxxxx!" because the BB3 multihax menu appears</u></summary>
|
||||
|
||||
You forgot to delete `F00D43D5.bin` from the SD card. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card and delete the `F00D43D5.bin` file.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"Haxxxxxxxxx!" does not appear</u></summary>
|
||||
|
||||
There is an issue with your `42383821.bin` file (it is incorrect, missing, misplaced, or corrupted). Re-create your files with the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website and ensure that you place the `42383821.bin` file from `output.zip` -> `hax` in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DS Connection Settings launches normally</u></summary>
|
||||
|
||||
`Haxxxxxxxxx!` was not copied from your SD card to your system memory.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Black screen when launching DS Connection Settings</u></summary>
|
||||
|
||||
Your DS Connection Settings application is broken, and you will need Homebrew Launcher access to fix this issue. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>SD card is grayed out in Flipnote</u></summary>
|
||||
|
||||
Flipnote may take a long time to index your card if you have a large SD card. Let it sit for a few minutes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Lenny face does not appear in SD card section</u></summary>
|
||||
|
||||
You did not copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Flipnote freezes</u></summary>
|
||||
|
||||
You may have accidentally touched the touch screen while in the modified Flipnote. Re-enter DS Connection Settings and try again, ensuring that you don't accidentally use the touchscreen.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Green screen after pasting</u></summary>
|
||||
|
||||
The file `boot.nds` is missing or misplaced. Download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>White screen after pasting</u></summary>
|
||||
Es gibt ein Problem mit deiner `boot.nds` Datei. Re-download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to open Luma3DS configuration menu after running B9STool</u></summary>
|
||||
|
||||
It is possible that boot9strap was not successfully installed. Follow section B of [this page](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Homebrew Launcher (PicHaxx)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
|
||||
|
||||
Your `00000001.sav` and/or `otherapp.bin` files may be misplaced. Ensure that `00000001.sav` is in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data` and that `otherapp.bin` is on the root of your SD card.
|
||||
|
||||
If your files are in the correct locations, re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx), then place it in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`. Ensure that the file is named exactly `00000001.sav` and that you used your console's `movable.sed` to create it. Re-download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Füge die `.bin` Erweiterung nicht hinzu, wenn du sie noch nicht siehst.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" or Errdisp when opening Picross</u></summary>
|
||||
|
||||
Your device already has custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `otherapp.bin` file. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Füge die `.bin` Erweiterung nicht hinzu, wenn du sie noch nicht siehst.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Game starts normally</u></summary>
|
||||
|
||||
Your modified `00000001.sav` file may be misplaced, or you may have used the wrong `movable.sed` when creating it. Re-generate your `movable.sed` from [Bruteforce Movable](https://seedminer.hacks.guide), then re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx) and place the resulting file (`00000001.sav`) in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Installing boot9strap (Soundhax)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Soundhax</u></summary>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
If your device is not on those firmwares, it likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `otherapp.bin` file (it is missing, misplaced, or corrupted). Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) and place it on the root of your SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"Could not play"</u></summary>
|
||||
|
||||
You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow [Seedminer](seedminer).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Füge die `.bin` Erweiterung nicht hinzu, wenn du sie noch nicht siehst.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Installing boot9strap (SSLoth-Browser)
|
||||
|
||||
### Red/purple/pink and white screen after running browserhax
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Browserhax</u></summary>
|
||||
|
||||
This likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
|
||||
|
||||
The file `arm11code.bin` is missing or misplaced. Lade die neuste Version von [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) herunter, platziere `otherapp.bin` im Stammverzeichnis deiner SD-Karte und benenne die Datei zu `arm11code.bin` um. Füge die `.bin` Erweiterung nicht hinzu, wenn du sie noch nicht siehst.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `arm11code.bin` file. Lade die neuste Version von [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) herunter, platziere `otherapp.bin` im Stammverzeichnis deiner SD-Karte und benenne die Datei zu `arm11code.bin` um. Füge die `.bin` Erweiterung nicht hinzu, wenn du sie noch nicht siehst.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Opening the browserhax QR code or URL crashes
|
||||
{% capture compat %}
|
||||
<summary><u>Opening the browserhax QR code or URL crashes</u></summary>
|
||||
|
||||
Browser based exploits (such as this one) are often unstable and crash frequently, but they can sometimes be fixed by doing the following steps.
|
||||
|
||||
1. Launch the browser, then launch the browser settings
|
||||
1. Scroll to the bottom and Initialize Savedata (it also may be called Clear All Save Data)
|
||||
1. Try the exploit again
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Opening the browser prompts for a system update instead
|
||||
{% capture compat %}
|
||||
<summary><u>System Update prompt when opening browser</u></summary>
|
||||
|
||||
The SSLoth proxy was incorrectly configured. Re-do the SSLoth section on the page.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Error 032-0420 when trying to open the browser
|
||||
{% capture compat %}
|
||||
<summary><u>Error 032-0420 when opening browser</u></summary>
|
||||
|
||||
Follow these steps in order:
|
||||
|
||||
|
|
@ -157,126 +376,47 @@ Follow these steps in order:
|
|||
1. If prompted about a system update, press OK
|
||||
+ This won't actually update the system
|
||||
1. Start again from [Section II](installing-boot9strap-(ssloth-browser).html#section-ii---ssloth)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Füge die `.bin` Erweiterung nicht hinzu, wenn du sie noch nicht siehst.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Frozen on "Doing agbhax..."
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Frozen on "Doing agbhax..."</u></summary>
|
||||
There may be an issue with your `arm11code.bin` file. Re-download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place it on the root of your SD card, and rename it to `arm11code.bin`. Füge die `.bin` Erweiterung nicht hinzu, wenn du sie noch nicht siehst.
|
||||
|
||||
If you have a Taiwanese unit (with a T in the version string, ie. 11.3.0-##T), you will not be able to follow these instructions, and you will need to update your console and follow [Seedminer](seedminer) instead.
|
||||
|
||||
If you have a Mainland Chinese unit (with a C in the version string, ie. 11.3.0-##C), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "PrepareArm9ForTwl returned error c8804631!"
|
||||
{% capture compat %}
|
||||
<summary><u>"PrepareArm9ForTwl returned error c8804631!"</u></summary>
|
||||
|
||||
You will need to follow an alternate method. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to mount the SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## BannerBomb3
|
||||
|
||||
### DSiWare Management menu crashes without showing BB3 multihax menu
|
||||
|
||||
Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. If it is, then re-create it with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen).
|
||||
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow [an alternate branch of Seedminer](homebrew-launcher-(pichaxx)). If Safe Mode doesn't work or you need assistance with this matter, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
|
||||
### DSiWare Management menu does not crash
|
||||
|
||||
`F00D43D5.bin` is missing from `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. Make sure that `Nintendo DSiWare` is correctly spelled and spaced. Uppercase/lowercase does not matter.
|
||||
|
||||
### DSiWare Management shows a question mark
|
||||
|
||||
There may be an issue with your `F00D43D5.bin` file (it may be corrupted or intended for the wrong 3DS). Re-create your `F00D43D5.bin` file with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen), ensuring that you use the `movable.sed` file for your console.
|
||||
|
||||
---
|
||||
|
||||
## Installing boot9strap (USM)
|
||||
|
||||
### Update doesn't fail with error code `003-1099`
|
||||
|
||||
unSAFE_MODE is not installed. Follow the instructions on your page to install unSAFE_MODE again.
|
||||
|
||||
### Red screen when selecting detailed setup
|
||||
|
||||
The file `usm.bin` is missing or misplaced. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/download/v1.3/usm.bin) and place `usm.bin` on the root of your SD card. Füge die `.bin` Erweiterung nicht hinzu, wenn du sie noch nicht siehst.
|
||||
|
||||
There is also a possibility that the console isn't reading your SD card. Make sure it is inserted and formatted correctly.
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Füge die `.bin` Erweiterung nicht hinzu, wenn du sie noch nicht siehst.
|
||||
|
||||
### Failed to mount the SD card!
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
|
||||
---
|
||||
|
||||
## Installing boot9strap (Fredtool)
|
||||
|
||||
### Error on Fredtool Injector page
|
||||
|
||||
Ensure that your `movable.sed` and DSiWare backup come from the same console. A mismatch will result in an error.
|
||||
|
||||
### Unable to select the "Haxxxxxxxxx!" title because of the BB3 multihax menu
|
||||
|
||||
You forgot to delete `F00D43D5.bin` from the SD card. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card and delete the `F00D43D5.bin` file.
|
||||
|
||||
### "Haxxxxxxxxx!" does not appear
|
||||
|
||||
There is an issue with your `42383821.bin` file (it is incorrect, missing, misplaced, or corrupted). Re-create your files with the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website and ensure that you place the `42383821.bin` file from `output.zip` -> `hax` in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`.
|
||||
|
||||
### DS Connection Settings launches normally
|
||||
|
||||
`Haxxxxxxxxx!` was not copied from your SD card to your system memory.
|
||||
|
||||
### Black screen when launching DS Connection Settings
|
||||
|
||||
Your DS Connection Settings application is broken, and you will need Homebrew Launcher access to fix this issue. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
|
||||
### SD card is grayed out
|
||||
|
||||
Flipnote may take a long time to index your card if you have a large SD card. Let it sit for a few minutes.
|
||||
|
||||
### Lenny face does not appear
|
||||
|
||||
You did not copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card.
|
||||
|
||||
### Flipnote is frozen
|
||||
|
||||
You may have accidentally touched the touch screen while in the modified Flipnote. Re-enter DS Connection Settings and try again, ensuring that you don't accidentally use the touchscreen.
|
||||
|
||||
### Green screen after pasting
|
||||
|
||||
The file `boot.nds` is missing or misplaced. Download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
|
||||
### White screen after pasting
|
||||
|
||||
Es gibt ein Problem mit deiner `boot.nds` Datei. Re-download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
|
||||
### Unable to open Luma3DS configuration menu after running b9stool
|
||||
|
||||
It is possible that boot9strap was not successfully installed. Follow section B of [this page](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md).
|
||||
|
||||
---
|
||||
|
||||
## Finalizing Setup
|
||||
|
||||
### Unable to update device
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to update device</u></summary>
|
||||
|
||||
The steps below can be attempted in any order, but are listed from easiest to hardest to perform.
|
||||
|
||||
|
|
@ -289,27 +429,41 @@ The steps below can be attempted in any order, but are listed from easiest to ha
|
|||
1. Nintendo servers may be down; Try again later
|
||||
1. If you still get an error, [follow CTRTransfer](ctrtransfer), then try again
|
||||
1. For further support (in English), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Unable to enter Rosalina due to broken button(s)
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to enter Rosalina menu due to broken Left Shoulder / Down D-Pad / Select button(s)</u></summary>
|
||||
|
||||
Download this [alternate config.ini](https://cdn.discordapp.com/attachments/196635695958196224/982798396265988186/config.ini) and place it in `/luma/`. This will change the Rosalina key combination to (X) + (Y).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An exception occurred" after trying to launch Homebrew Launcher via Download Play
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" after trying to launch Homebrew Launcher from Download Play</u></summary>
|
||||
|
||||
There is an issue with your `boot.3dsx` file (it is missing, misplaced, or corrupted). Download the latest release of [the Homebrew Launcher](https://github.com/devkitPro/3ds-hbmenu/releases/latest) and place `boot.3dsx` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "Scripts directory not found" in GodMode9
|
||||
{% capture compat %}
|
||||
<summary><u>"Scripts directory not found" in GodMode9</u></summary>
|
||||
|
||||
You did not copy the `gm9` folder from the GodMode9 `.zip` to the root of your SD card. Download the latest release of [GodMode9](https://github.com/d0k3/GodMode9/releases/latest) and place the `gm9` folder on the root of your SD card, merging it with the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## Boot-related issues on modded devices
|
||||
## Boot issues on devices with custom firmware
|
||||
|
||||
The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
|
||||
{: .notice--info}
|
||||
|
||||
### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
|
||||
### Power/notification light indicators
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>My device powers off when I try to turn it on, and/or the notification LED shows a color on boot</u></summary>
|
||||
|
||||
There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
|
||||
|
||||
|
|
@ -322,11 +476,15 @@ If the notification LED flashes:
|
|||
You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
|
||||
|
||||
If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### My device gets stuck on a black screen, with a static blue light
|
||||
{% capture compat %}
|
||||
<summary><u>My device gets stuck on a black screen with blue power light staying on</u></summary>
|
||||
|
||||
The steps below can be attempted in any order, but are listed from least to most time-consuming.
|
||||
|
||||
1. Power off your device, remove the SD card, re-insert it, then power on your device.
|
||||
1. Power off your device, eject the game cartridge if inserted, power on your device, then wait up to ten minutes. If your device boots within ten minutes, the issue has been fixed and is unlikely to reoccur
|
||||
1. Rename the `Nintendo 3DS` folder on your SD card to `Nintendo 3DS_BACKUP`, then attempt to boot. If your device successfully boots, there is some issue within your `Nintendo 3DS` folder. Try clearing HOME Menu extdata:
|
||||
+ Navigate to `/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/`
|
||||
|
|
@ -344,35 +502,48 @@ The steps below can be attempted in any order, but are listed from least to most
|
|||
+ If you were successful, the device will boot to an "update your system" screen
|
||||
1. Follow the [CTRTransfer](ctrtransfer) guide
|
||||
1. For further support, ask for help at [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### My device boots to an error screen
|
||||
### Error message on boot
|
||||
|
||||
#### "An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"</u></summary>
|
||||
|
||||
Your Luma3DS version is outdated. Download the latest release of [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### "An error has occurred. Hold down the POWER button to turn off the power..."
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..."</u></summary>
|
||||
|
||||
ARM11 exception handlers are disabled, or custom firmware is not installed. Try enabling ARM11 exception handlers:
|
||||
+ Power off your device
|
||||
+ Hold (Select)
|
||||
+ Power on your device, while still holding (Select)
|
||||
+ If the "Disable ARM11 exception handlers" box is checked, uncheck it
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Some other error
|
||||
|
||||
Please take a photo of the error and join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
|
||||
### Blue "Bootrom Error" screen
|
||||
{% capture compat %}
|
||||
<summary><u>Blue "BOOTROM ERROR" screen</u></summary>
|
||||
|
||||
Your device is likely hard-bricked. You will need to buy an ntrboot flashcart to reinstall boot9strap in order to attempt to fix your device. This may also indicate a hardware issue that cannot be fixed. In any case, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
+ It is also possible that someone has set a boot-time splash screen that just looks like a brick. Try leaving your device powered on, waiting on the blue screen, for five minutes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary><u>Some other error</u></summary>
|
||||
|
||||
## Functionality-related issues on modded devices
|
||||
Please take a photo of the error and join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### DSi / DS functionality is broken or has been replaced with Flipnote Studio
|
||||
## Software issues on devices with custom firmware
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DSi / DS functionality is broken or has been replaced with Flipnote Studio</u></summary>
|
||||
|
||||
1. Download the latest release of [TWLFix-CFW](https://github.com/MechanicalDragon0687/TWLFix-CFW/releases/latest) (the `.3dsx` file)
|
||||
1. Schalte deine Konsole aus
|
||||
|
|
@ -386,20 +557,29 @@ Your device is likely hard-bricked. You will need to buy an ntrboot flashcart to
|
|||
1. Perform a System Update by going to System Settings, then "Other Settings", then going all the way to the right and using "System Update"
|
||||
+ The update will see that the essential TWL titles have been uninstalled, and will redownload and reinstall them
|
||||
1. Once the update is complete, tap "OK" to reboot the device
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### GBA Virtual Console and/or Safe Mode functionality is broken
|
||||
{% capture compat %}
|
||||
<summary><u>GBA Virtual Console and/or Safe Mode functionality is broken</u></summary>
|
||||
|
||||
Your device is running Luma3DS/AuReiNand 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your device to a modern custom firmware environment.
|
||||
Your device is running Luma3DS 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your device to a modern custom firmware environment.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Extended memory mode games are broken
|
||||
{% capture compat %}
|
||||
<summary><u>Extended memory mode games (Pokemon Sun/Moon, Smash, etc.) don't work</u></summary>
|
||||
|
||||
This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will need to system format your device to fix this issue.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## Other troubleshooting
|
||||
|
||||
### Clear HOME Menu extdata
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu extdata</u></summary>
|
||||
|
||||
1. Schalte deinen 3DS aus
|
||||
1. Stecke deine SD-Karte in deinen Computer
|
||||
|
|
@ -412,8 +592,11 @@ This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will n
|
|||
+ **KOR-Region**: `000000A9`
|
||||
+ **TWN-Region**: `000000B1`
|
||||
1. Stecke deine SD-Karte nun wieder in deinen 3DS
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Clear HOME Menu theme data
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu theme data</u></summary>
|
||||
|
||||
1. Schalte deinen 3DS aus
|
||||
1. Stecke deine SD-Karte in deinen Computer
|
||||
|
|
@ -423,3 +606,6 @@ This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will n
|
|||
+ **JPN Region**: `000002cc`
|
||||
+ **USA Region**: `000002cd`
|
||||
1. Stecke deine SD-Karte nun wieder in deinen 3DS
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@ The purpose of this section is to check whether built-in DS mode applications wi
|
|||
+ If your console displays the Japanese version of Flipnote Studio, a black screen, or an error message, the test has failed
|
||||
1. Schalte deinen 3DS aus
|
||||
|
||||
If either of these tests has failed, DS mode, DS Download Play, and/or DS Connection Settings may be inaccessible once CFW is uninstalled! You should [fix DS mode](troubleshooting#dsi--ds-functionality-is-broken-or-has-been-replaced-with-flipnote-studio) before continuing.
|
||||
If either of these tests has failed, DS mode, DS Download Play, and/or DS Connection Settings may be inaccessible once CFW is uninstalled! You should [fix DS mode](troubleshooting#software-issues-on-devices-with-custom-firmware) before continuing.
|
||||
{: .notice--warning}
|
||||
|
||||
#### Section III - Safety Test
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ For all steps in this section, overwrite any existing files on your SD card.
|
|||
1. Your device should have rebooted into the Luma3DS configuration menu
|
||||
+ Luma3DS configuration menu are settings for the Luma3DS custom firmware. Many of these settings may be useful for customization or debugging
|
||||
+ For the purpose of this guide, these settings will be left on default settings
|
||||
+ If you get a black screen, [follow this troubleshooting guide](troubleshooting#boot-related-issues-on-modded-devices)
|
||||
+ If you get a black screen, [follow this troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware)
|
||||
1. Πατήστε (Start) για αποθήκευση των αλλαγών και επανεκκίνηση
|
||||
|
||||
___
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ This is an add-on section to check if your console already has a modern custom f
|
|||
|
||||
If your console already has an arm9loaderhax or boot9strap based custom firmware, you will need to follow the instructions indicated to upgrade your setup to a modern one.
|
||||
|
||||
If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#clear-home-menu-extdata), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
|
||||
If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#other-troubleshooting), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
|
||||
{: .notice--info}
|
||||
|
||||
### Instructions
|
||||
|
|
|
|||
|
|
@ -14,79 +14,173 @@ title: "FAQ"
|
|||
|
||||
## Pre-Installation FAQ
|
||||
|
||||
#### **Q:** *I am on the latest system version. Is my device hackable without any external hardware?*
|
||||
**A:** Yes! The latest firmware (11.16.0) has a free method for getting CFW named [Seedminer](seedminer).
|
||||
{% capture compat %}
|
||||
<summary><u>I am on the latest system version. Is my device hackable without any external hardware?</u></summary>
|
||||
|
||||
#### **Q:** *What devices is this guide compatible with?*
|
||||
**A:** The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. If your system version string displays as "0.0.0-0", then you may have a developer unit.
|
||||
Yes! The latest firmware (11.16.0) has a free method for getting CFW named [Seedminer](seedminer).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How risky is hacking my console?*
|
||||
**A:** Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
{% capture compat %}
|
||||
<summary><u>What devices is this guide compatible with?</u></summary>
|
||||
|
||||
#### **Q:** *Can I run awesome homebrew and emulators with this?*
|
||||
**A:** Yes! This guide will install a few useful homebrew applications, including [Universal-Updater](https://github.com/Universal-Team/Universal-Updater/releases/latest), which acts as a homebrew app store.
|
||||
The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. If your system version string displays as "0.0.0-0", then you may have a developer unit.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I use this to play games from other regions?*
|
||||
**A:** Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Some games may need to make use of Luma's [locale emulation feature](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) in order to work properly on out-of-region devices.
|
||||
{% capture compat %}
|
||||
<summary><u>How risky is hacking my console?</u></summary>
|
||||
|
||||
#### **Q:** *Will I lose any features if I install CFW?*
|
||||
**A:** No. Devices with custom firmware can still use the eShop and run physical cartridges as any other 3DS can.
|
||||
Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I keep my NNID?*
|
||||
**A:** Your NNID (if you have one) will not be affected by this guide. Devices with a region of KOR, CHN, or TWN do not have NNID functionality to begin with and are thus unaffected.
|
||||
{% capture compat %}
|
||||
<summary><u>Can I run awesome homebrew and emulators with this?</u></summary>
|
||||
|
||||
#### **Q:** *Will my 3DS be banned for having CFW?*
|
||||
**A:** There was a ban wave in May 2017 that banned CFW users from online play (eShop access, NNIDs, and Nintendo Accounts were unaffected), seemingly at random. A ban wave at such a scale has not been seen since. That being said, we don't know what Nintendo may have in store in the future. At this time, we don't think that bans are something that you need to worry about.
|
||||
Yes! This guide will install a few useful homebrew applications, including [Universal-Updater](https://github.com/Universal-Team/Universal-Updater/releases/latest), which acts as a homebrew app store.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I do this without a computer (e.g. an Android phone)?*
|
||||
**A:** All you need is the ability to put files on a compatible SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Can I use this to play games from other regions?</u></summary>
|
||||
|
||||
#### **Q:** *What size SD card can I use?*
|
||||
**A:** You will need at least 1.5GB of free SD card space to follow this guide in its entirety. While the 3DS is officially compatible with SD cards up to 32GB, larger SD cards can be used if they are manually re-formatted as FAT32. It is not recommended to use SD cards greater than 128GB due to known issues with GBA graphics and custom themes.
|
||||
Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Some games may need to make use of Luma's [locale emulation feature](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) in order to work properly on out-of-region devices.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *I heard about this thing I have to pay for (Gateway, Sky3DS, ntrboot, R4, etc). Is that something I need?*
|
||||
**A:** No. Custom firmware can be installed for free on the latest firmware without any hardware devices. In fact, 3DS-mode flashcarts like Gateway and Sky3DS are not recommended because they are obsolete and may carry ban or brick risk.
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose any features if I install CFW?</u></summary>
|
||||
|
||||
#### **Q:** *What's the difference between custom firmware and homebrew access?*
|
||||
**A:** Historically, the 3DS used to have userland homebrew access through older exploits like ninjhax. The level of system access granted with userland allowed you to run basic homebrew and emulators but did not allow you to (easily) modify games or dump cartridges. It was also a lot less stable, with homebrew often ungracefully crashing and requiring a full reboot. Custom firmware grants a far greater level of system access while also being more stable than homebrew-only entrypoints.
|
||||
No. Devices with custom firmware can still use the eShop and run physical cartridges as any other 3DS can.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I keep my NNID?</u></summary>
|
||||
|
||||
Your NNID (if you have one) will not be affected by this guide. Devices with a region of KOR, CHN, or TWN do not have NNID functionality to begin with and are thus unaffected.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will my 3DS be banned for having CFW?</u></summary>
|
||||
|
||||
There was a ban wave in May 2017 that banned CFW users from online play (eShop access, NNIDs, and Nintendo Accounts were unaffected), seemingly at random. A ban wave at such a scale has not been seen since. That being said, we don't know what Nintendo may have in store in the future. At this time, we don't think that bans are something that you need to worry about.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I do this without a computer (e.g. an Android phone)?</u></summary>
|
||||
|
||||
Yes! All you need is the ability to put files on a compatible SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What size SD card can I use?</u></summary>
|
||||
|
||||
You will need at least 1.5GB of free SD card space to follow this guide in its entirety. While the 3DS is officially compatible with SD cards up to 32GB, larger SD cards can be used if they are manually re-formatted as FAT32. It is not recommended to use SD cards greater than 128GB due to known issues with GBA graphics and custom themes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>I heard about this thing I have to pay for (Gateway, Sky3DS, ntrboot, R4, etc). Is that something I need?</u></summary>
|
||||
|
||||
No. Custom firmware can be installed for free on the latest firmware without any hardware devices. In fact, 3DS-mode flashcarts like Gateway and Sky3DS are not recommended because they are obsolete and may carry ban or brick risk.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What's the difference between custom firmware and homebrew?</u></summary>
|
||||
|
||||
Historically, the 3DS used to have userland homebrew access through older exploits like ninjhax. The level of system access granted with userland allowed you to run basic homebrew and emulators but did not allow you to (easily) modify games or dump cartridges. It was also a lot less stable, with homebrew often ungracefully crashing and requiring a full reboot. Custom firmware grants a far greater level of system access while also being more stable than homebrew-only entrypoints.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Post-Installation FAQ
|
||||
|
||||
#### **Q:** *Is it safe to update my 3DS to the latest version with CFW?*
|
||||
**A:** If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. There have been updates in the past that have resulted in Luma3DS crashing on boot, so it is a good idea to wait a couple of hours to ensure that the latest update will not temporarily render the device unusable until Luma3DS is updated. System updates can be performed the same way as they are on a stock 3DS: through System Settings, Safe Mode, or the update prompt when the update is automatically downloaded.
|
||||
{% capture compat %}
|
||||
<summary><u>Is it safe to update my 3DS to the latest version with CFW?</u></summary>
|
||||
|
||||
#### **Q:** *How do I upgrade my SD card?*
|
||||
**A:** Copy and paste your SD card contents to a new SD card formatted as FAT32. For 128GB cards, an allocation size of 65536 is recommended. SD cards larger than 128GB are not recommended due to known issues with GBA graphics and custom themes.
|
||||
If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. There have been updates in the past that have resulted in Luma3DS crashing on boot, so it is a good idea to wait a couple of hours to ensure that the latest update will not temporarily render the device unusable until Luma3DS is updated. System updates can be performed the same way as they are on a stock 3DS: through System Settings, Safe Mode, or the update prompt when the update is automatically downloaded.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I system transfer with CFW?*
|
||||
**A:** Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets for illegitimate titles (homebrew) will not transfer, but the titles can be made to reappear with [faketik](https://github.com/ihaveamac/faketik/releases/latest). Make sure that you do not perform a wireless transfer, as this will delete illegitimate titles. CFW will remain on both consoles.
|
||||
{% capture compat %}
|
||||
<summary><u>How do I upgrade my SD card?</u></summary>
|
||||
|
||||
#### **Q:** *How do I change the system language of a Japanese 3DS?*
|
||||
**A:** The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Note that this is very likely to break the Nintendo eShop on your device, which means you will be unable to update your games whether they are in-region or out-of-region.
|
||||
Copy and paste your SD card contents to a new SD card formatted as FAT32. For 128GB cards, an allocation size of 65536 is recommended. SD cards larger than 128GB are not recommended due to known issues with GBA graphics and custom themes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How do I update homebrew applications?*
|
||||
**A:** It depends on the format of the homebrew application. Generally speaking:
|
||||
{% capture compat %}
|
||||
<summary><u>Can I system transfer with CFW?</u></summary>
|
||||
|
||||
Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets for illegitimate titles (homebrew) will not transfer, but the titles can be made to reappear with [faketik](https://github.com/ihaveamac/faketik/releases/latest). Make sure that you do not perform a wireless transfer, as this will delete illegitimate titles. CFW will remain on both consoles.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I change the system language of a Japanese 3DS?</u></summary>
|
||||
|
||||
The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Note that this is very likely to break the Nintendo eShop on your device, which means you will be unable to update your games whether they are in-region or out-of-region.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I update homebrew applications?</u></summary>
|
||||
|
||||
It depends on the format of the homebrew application. Generally speaking:
|
||||
|
||||
* Homebrew in **CIA format** can be updated by installing the new CIA, which will usually overwrite the old one. If the old CIA is not overwritten, you can delete the old one from Data Management as you would any other 3DS title.
|
||||
* Homebrew in **3DSX format** can be updated by replacing the 3DSX file in `/3ds/` with a fresh copy. If the homebrew application includes additional assets, you may need to place that folder somewhere else. Refer to the documentation of the homebrew application.
|
||||
* For updating Luma3DS, see [this page](restoring-updating-cfw). For updating GodMode9, see [this page](godmode9-usage#updating-godmode9).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How do I update games from outside of my 3DS region?*
|
||||
**A:** You will need to [dump the updates](dumping-titles-and-game-cartridges) from a 3DS that has the updates installed. The Nintendo eShop only contains updates for the console's region (a Japanese 3DS will only have updates for Japanese games).
|
||||
{% capture compat %}
|
||||
<summary><u>How do I update my games?</u></summary>
|
||||
|
||||
#### **Q:** *Help! Something bad happened and now I cannot boot...*
|
||||
**A:** Please look at the [troubleshooting guide](troubleshooting). **Uninstalling CFW when your device is in an unbootable state is not recommended, as it is very likely to lead to a brick**.
|
||||
You can continue to download game updates from the Nintendo eShop, even after the 2023 shutdown.
|
||||
|
||||
If the game is not from the same region as the console, you will need to [dump the updates](dumping-titles-and-game-cartridges) from a 3DS that has the updates installed. The Nintendo eShop only contains updates for the console's region (a Japanese 3DS will only have updates for Japanese games).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Help! Something bad happened and my 3DS won't boot to HOME Menu...</u></summary>
|
||||
|
||||
Please look at the [troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware). **Uninstalling CFW when your device is in an unbootable state is not recommended, as it is very likely to lead to a brick**.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## menuhax / A9LH / Gateway FAQ
|
||||
|
||||
#### **Q:** *I modded my device x years ago. What should I do?*
|
||||
**A:** It is recommended that you upgrade your setup to a modern, boot9strap-based one. Follow the [Checking for CFW](checking-for-cfw) guide to see how to upgrade your setup.
|
||||
{% capture compat %}
|
||||
<summary><u>I modded my device (x) years ago, so it already has some sort of homebrew. What should I do?</u></summary>
|
||||
|
||||
#### **Q:** *My setup works for me. Why should I upgrade it?*
|
||||
**A:** The vast majority of modern homebrew (such as Checkpoint and BootNTR Selector) have only been tested on modern, boot9strap-based setups and may not work entirely (or at all) on older setups based on menuhax, A9LH, or Gateway. In addition, depending on your setup, you may be unable to safely update to the latest firmware. Modern, boot9strap-based setups allow for a greater level of system access than previous hacks, including the ability to dump your console's bootrom.
|
||||
It is recommended that you upgrade your setup to a modern, boot9strap-based one. Follow the [Checking for CFW](checking-for-cfw) guide to see how to upgrade your setup.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Will I lose anything if I upgrade my setup?*
|
||||
**A:** Your old setup (including your EmuNAND, if you have one) can usually be directly migrated to boot9strap with no data loss. If you have data that is particularly important to you, it would be a good idea to make a decrypted backup of your save data before upgrading your setup with a tool like [JKSM](https://github.com/J-D-K/JKSM/releases/tag/12%2F20%2F2018).
|
||||
{% capture compat %}
|
||||
<summary><u>My setup works for me. Why should I upgrade it?</u></summary>
|
||||
|
||||
The vast majority of modern homebrew (such as Checkpoint and BootNTR Selector) have only been tested on modern, boot9strap-based setups and may not work entirely (or at all) on older setups based on menuhax, A9LH, or Gateway. In addition, depending on your setup, you may be unable to safely update to the latest firmware. Modern, boot9strap-based setups allow for a greater level of system access than previous hacks, including the ability to dump your console's bootrom.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose anything if I upgrade my setup?</u></summary>
|
||||
|
||||
Your old setup (including your EmuNAND, if you have one) can usually be directly migrated to boot9strap with no data loss. If you have data that is particularly important to you, it would be a good idea to make a decrypted backup of your save data before upgrading your setup with a tool like [JKSM](https://github.com/J-D-K/JKSM/releases/tag/12%2F20%2F2018).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I move saves from an existing Gateway setup to a more modern setup?</u></summary>
|
||||
|
||||
#### **Q:** *How do I move saves from an existing Gateway setup to a more modern setup?*
|
||||
**A:** See [this thread](https://gbatemp.net/threads/425743/).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@ In this section, you will update your system to the latest version, which is saf
|
|||
+ Updates while using B9S + Luma (what you have) are safe
|
||||
+ The updater may display a message saying "Your system is up to date" instead of updating. This is normal if you are already up to date; continue with the next section
|
||||
+ If this gives you an error, set both your DNS settings and Proxy settings to "auto"
|
||||
+ If this still gives you an error, [follow this troubleshooting guide](troubleshooting#unable-to-update-device)
|
||||
+ If this still gives you an error, [follow this troubleshooting guide](troubleshooting#finalizing-setup)
|
||||
|
||||
#### Section III - Homebrew Launcher
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
|||
1. Launch System Settings on your device
|
||||
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#dsiware-management-menu-crashes-without-showing-bb3-multihax-menu)
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#installing-boot9strap-fredtool)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Dump DSiWare"
|
||||
+ Your device will automatically reboot
|
||||
1. Power off your device
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
|||
1. Launch System Settings on your device
|
||||
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#dsiware-management-menu-crashes-without-showing-bb3-multihax-menu)
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#bannerbomb3)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Install unSAFE_MODE"
|
||||
+ Your device will automatically power off
|
||||
|
||||
|
|
|
|||
|
|
@ -168,7 +168,6 @@ To identify a `<TitleID>.gbavc.sav` file's Title ID, you can get a listing of al
|
|||
1. Reinsert your SD card into your device
|
||||
1. Πατήστε (A) για να ξαναμοντάρετε την κάρτα SD
|
||||
1. Press (Start) to reboot
|
||||
1. If you get a black screen, [follow this troubleshooting guide](troubleshooting#ts_sys_down)
|
||||
|
||||
___
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ In this section, you will get the necessary details from your 3DS that are requi
|
|||
+ If you don't have a `Nintendo 3DS` folder, put your SD card into your 3DS and power it on so that the folder can be created
|
||||
1. Copy the name of the 32-letter folder you see directly inside Nintendo 3DS
|
||||
+ This 32-letter name is system-specific and will be different for each console
|
||||
+ If you see multiple 32-letter folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
|
||||
+ If you see multiple 32-letter folders, follow [these instructions](troubleshooting#seedminer)
|
||||
+ You can ignore the `private` folder if you have it
|
||||
|
||||
![]({{ "/images/screenshots/seedminer/id0-example.png" | absolute_url }})
|
||||
|
|
|
|||
|
|
@ -2,37 +2,69 @@
|
|||
title: "Troubleshooting"
|
||||
---
|
||||
|
||||
{% include toc title="Table of Contents"%}
|
||||
|
||||
This page offers troubleshooting advice for commonly encountered issues. If you are unable to solve your issue with the advice on this page, please join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and describe your issue, including what you have already tried.
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary>Table of Contents</summary>
|
||||
|
||||
Used on multiple pages:
|
||||
* [SafeB9SInstaller](#issues-with-safeb9sinstaller)
|
||||
|
||||
Guide pages:
|
||||
* [Seedminer](#seedminer)
|
||||
* [BannerBomb3](#bannerbomb3)
|
||||
* [Installing boot9strap (USM)](#installing-boot9strap-usm)
|
||||
* [Installing boot9strap (Fredtool)](#installing-boot9strap-fredtool)
|
||||
* [Homebrew Launcher (PicHaxx)](#homebrew-launcher-pichaxx)
|
||||
* [Installing boot9strap (Soundhax)](#installing-boot9strap-soundhax)
|
||||
* [Installing boot9strap (SSLoth-Browser)](#installing-boot9strap-ssloth-browser)
|
||||
|
||||
* [Finalizing Setup](#finalizing-setup)
|
||||
|
||||
Issues after installation:
|
||||
* [Boot issues](#boot-issues-on-devices-with-custom-firmware)
|
||||
* [Software issues](#software-issues-on-devices-with-custom-firmware)
|
||||
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
{: .notice--info}
|
||||
|
||||
## Issues with SafeB9SInstaller
|
||||
|
||||
### SigHaxed FIRM was not installed! Check lower screen for more info.
|
||||
|
||||
#### SigHaxed FIRM - File not found
|
||||
{% capture compat %}
|
||||
<summary><u>SigHaxed FIRM - File not found</u></summary>
|
||||
|
||||
You are missing `boot9strap.firm` and `boot9strap.firm.sha` from the `boot9strap` folder, or the `boot9strap` folder is misnamed. Download the latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip), and place `boot9strap.firm` and `boot9strap.firm.sha` in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### SigHaxed FIRM - invalid FIRM
|
||||
{% capture compat %}
|
||||
<summary><u>SigHaxed FIRM - invalid FIRM</u></summary>
|
||||
|
||||
There is an issue with your `boot9strap.firm` and `boot9strap.firm.sha` files. Re-download the latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip), and place `boot9strap.firm` and `boot9strap.firm.sha` in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Secret Sector - File not found
|
||||
{% capture compat %}
|
||||
<summary><u>Secret Sector - File not found</u></summary>
|
||||
|
||||
You are missing `secret_sector.bin` from the `boot9strap` folder, or the `boot9strap` folder is misnamed. Download [secret_sector.bin](magnet:?xt=urn:btih:15a3c97acf17d67af98ae8657cc66820cc58f655&dn=secret_sector.bin&tr=udp%3a%2f%2ftracker.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.lelux.fi%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.loadbt.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.moeking.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.monitorit4.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.ololosh.space%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.pomf.se%3a80%2fannounce&tr=udp%3a%2f%2ftracker.srv00.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.theoks.net%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.tiny-vps.com%3a6969%2fannounce&tr=udp%3a%2f%2fopen.tracker.cl%3a1337%2fannounce&tr=udp%3a%2f%2ftracker.zerobytes.xyz%3a1337%2fannounce&tr=udp%3a%2f%2ftracker1.bt.moack.co.kr%3a80%2fannounce&tr=udp%3a%2f%2fvibe.sleepyinternetfun.xyz%3a1738%2fannounce&tr=udp%3a%2f%2fwww.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a6969%2fannounce&tr=udp%3a%2f%2f9.rarbg.com%3a2810%2fannounce&tr=udp%3a%2f%2ftracker.opentrackr.org%3a1337%2fannounce&tr=udp%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fopenbittorrent.com%3a80%2fannounce) using a torrent client, and place it in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Something else
|
||||
{% capture compat %}
|
||||
<summary><u>Something else</u></summary>
|
||||
|
||||
Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance, and describe the message that you see.
|
||||
|
||||
---
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Seedminer
|
||||
|
||||
### Multiple long folder names in Nintendo 3DS folder
|
||||
{% capture compat %}
|
||||
<summary><u>Multiple long folder names in Nintendo 3DS folder</u></summary>
|
||||
|
||||
![]({{ "/images/screenshots/multiple-id0.png" | absolute_url }})
|
||||
{: .notice--info}
|
||||
|
|
@ -49,98 +81,285 @@ This occurs when you use your SD card in multiple 3DS devices and is intended to
|
|||
+ This is your true ID0 that you will use in [Section II of Seedminer](seedminer#section-ii---seedminer)
|
||||
1. Delete the `Nintendo 3DS` folder
|
||||
1. Rename the `BACKUP_Nintendo 3DS` folder to `Nintendo 3DS`
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Bruteforce Movable skips to step 4
|
||||
{% capture compat %}
|
||||
<summary><u>Bruteforce Movable skips to step 4</u></summary>
|
||||
|
||||
The website has already mined your `movable.sed` using your friend code and ID0 combination. You can use the `movable.sed` that it provides you.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Important! You have been locked out of the automated part1 dumper system...
|
||||
{% capture compat %}
|
||||
<summary><u>Important! You have been locked out of the automated part1 dumper system...</u></summary>
|
||||
|
||||
Your friend code was blocked from using the friend code bot because your 3DS did not successfully friend the bot. Ensure your 3DS is properly connected to the Internet, then join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask to be unlocked.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### We were unable to successfully complete your bruteforce request. :`(
|
||||
{% capture compat %}
|
||||
<summary><u>We were unable to successfully complete your bruteforce request. :`(</u></summary>
|
||||
|
||||
The website has determined that your `movable.sed` cannot be brute-forced. Ensure that you gave the correct ID0 to the website. If your ID0 is correct, then you will be unable to use Seedminer and you will have to use an alternate method that will require additional games or hardware.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
## BannerBomb3
|
||||
|
||||
## Homebrew Launcher (PicHaxx)
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management menu crashes without showing BB3 multihax menu</u></summary>
|
||||
Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. If it is, then re-create it with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen).
|
||||
|
||||
### "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
Your `00000001.sav` and/or `otherapp.bin` files may be misplaced. Ensure that `00000001.sav` is in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data` and that `otherapp.bin` is on the root of your SD card.
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow [an alternate branch of Seedminer](homebrew-launcher-(pichaxx)). If Safe Mode doesn't work or you need assistance with this matter, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
If your files are in the correct locations, re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx), then place it in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`. Ensure that the file is named exactly `00000001.sav` and that you used your console's `movable.sed` to create it. Re-download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management menu does not crash</u></summary>
|
||||
|
||||
### "An exception occurred" or Errdisp when opening Picross
|
||||
`F00D43D5.bin` is missing from `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. Make sure that `Nintendo DSiWare` is correctly spelled and spaced. Uppercase/lowercase does not matter.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
Your device already has custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management shows a question mark</u></summary>
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
There may be an issue with your `F00D43D5.bin` file (it may be corrupted or intended for the wrong 3DS). Re-create your `F00D43D5.bin` file with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen), ensuring that you use the `movable.sed` file for your console.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
There is an issue with your `otherapp.bin` file. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
## Installing boot9strap (USM)
|
||||
|
||||
### Game starts normally
|
||||
{% capture compat %}
|
||||
<summary><u>Safe Mode system update succeeds instead of giving error 003-1099</u></summary>
|
||||
|
||||
Your modified `00000001.sav` file may be misplaced, or you may have used the wrong `movable.sed` when creating it. Re-generate your `movable.sed` from [Bruteforce Movable](https://seedminer.hacks.guide), then re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx) and place the resulting file (`00000001.sav`) in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`.
|
||||
unSAFE_MODE is not installed. [Follow the instructions](installing-boot9strap-(usm)] to install it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary><u>Red screen after selecting "Detailed Setup"</u></summary>
|
||||
|
||||
## Installing boot9strap (Soundhax)
|
||||
The file `usm.bin` is missing or misplaced. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/download/v1.3/usm.bin) and place `usm.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
### Red/purple/pink and white screen after running Soundhax
|
||||
There is also a possibility that the console isn't reading your SD card. Make sure it is inserted and formatted correctly.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
If your device is not on those firmwares, it likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
|
||||
There is an issue with your `otherapp.bin` file (it is missing, misplaced, or corrupted). Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) and place it on the root of your SD card.
|
||||
|
||||
### "Could not play"
|
||||
|
||||
You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow [Seedminer](seedminer).
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to mount the SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
## Installing boot9strap (Fredtool)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Error on Fredtool Injector page</u></summary>
|
||||
|
||||
Ensure that your `movable.sed` and DSiWare backup come from the same console. A mismatch will result in an error.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to select "Haxxxxxxxxx!" because the BB3 multihax menu appears</u></summary>
|
||||
|
||||
You forgot to delete `F00D43D5.bin` from the SD card. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card and delete the `F00D43D5.bin` file.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"Haxxxxxxxxx!" does not appear</u></summary>
|
||||
|
||||
There is an issue with your `42383821.bin` file (it is incorrect, missing, misplaced, or corrupted). Re-create your files with the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website and ensure that you place the `42383821.bin` file from `output.zip` -> `hax` in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DS Connection Settings launches normally</u></summary>
|
||||
|
||||
`Haxxxxxxxxx!` was not copied from your SD card to your system memory.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Black screen when launching DS Connection Settings</u></summary>
|
||||
|
||||
Your DS Connection Settings application is broken, and you will need Homebrew Launcher access to fix this issue. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>SD card is grayed out in Flipnote</u></summary>
|
||||
|
||||
Flipnote may take a long time to index your card if you have a large SD card. Let it sit for a few minutes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Lenny face does not appear in SD card section</u></summary>
|
||||
|
||||
You did not copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Flipnote freezes</u></summary>
|
||||
|
||||
You may have accidentally touched the touch screen while in the modified Flipnote. Re-enter DS Connection Settings and try again, ensuring that you don't accidentally use the touchscreen.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Green screen after pasting</u></summary>
|
||||
|
||||
The file `boot.nds` is missing or misplaced. Download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>White screen after pasting</u></summary>
|
||||
There is an issue with your `boot.nds` file. Re-download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to open Luma3DS configuration menu after running B9STool</u></summary>
|
||||
|
||||
It is possible that boot9strap was not successfully installed. Follow section B of [this page](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Homebrew Launcher (PicHaxx)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
|
||||
|
||||
Your `00000001.sav` and/or `otherapp.bin` files may be misplaced. Ensure that `00000001.sav` is in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data` and that `otherapp.bin` is on the root of your SD card.
|
||||
|
||||
If your files are in the correct locations, re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx), then place it in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`. Ensure that the file is named exactly `00000001.sav` and that you used your console's `movable.sed` to create it. Re-download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" or Errdisp when opening Picross</u></summary>
|
||||
|
||||
Your device already has custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `otherapp.bin` file. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Game starts normally</u></summary>
|
||||
|
||||
Your modified `00000001.sav` file may be misplaced, or you may have used the wrong `movable.sed` when creating it. Re-generate your `movable.sed` from [Bruteforce Movable](https://seedminer.hacks.guide), then re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx) and place the resulting file (`00000001.sav`) in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Installing boot9strap (Soundhax)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Soundhax</u></summary>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
If your device is not on those firmwares, it likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `otherapp.bin` file (it is missing, misplaced, or corrupted). Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) and place it on the root of your SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"Could not play"</u></summary>
|
||||
|
||||
You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow [Seedminer](seedminer).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Installing boot9strap (SSLoth-Browser)
|
||||
|
||||
### Red/purple/pink and white screen after running browserhax
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Browserhax</u></summary>
|
||||
|
||||
This likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
|
||||
|
||||
The file `arm11code.bin` is missing or misplaced. Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place `otherapp.bin` on the root of your SD card and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `arm11code.bin` file. Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place `otherapp.bin` on the root of your SD card and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Opening the browserhax QR code or URL crashes
|
||||
{% capture compat %}
|
||||
<summary><u>Opening the browserhax QR code or URL crashes</u></summary>
|
||||
|
||||
Browser based exploits (such as this one) are often unstable and crash frequently, but they can sometimes be fixed by doing the following steps.
|
||||
|
||||
1. Launch the browser, then launch the browser settings
|
||||
1. Scroll to the bottom and Initialize Savedata (it also may be called Clear All Save Data)
|
||||
1. Try the exploit again
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Opening the browser prompts for a system update instead
|
||||
{% capture compat %}
|
||||
<summary><u>System Update prompt when opening browser</u></summary>
|
||||
|
||||
The SSLoth proxy was incorrectly configured. Re-do the SSLoth section on the page.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Error 032-0420 when trying to open the browser
|
||||
{% capture compat %}
|
||||
<summary><u>Error 032-0420 when opening browser</u></summary>
|
||||
|
||||
Follow these steps in order:
|
||||
|
||||
|
|
@ -157,126 +376,47 @@ Follow these steps in order:
|
|||
1. If prompted about a system update, press OK
|
||||
+ This won't actually update the system
|
||||
1. Start again from [Section II](installing-boot9strap-(ssloth-browser).html#section-ii---ssloth)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Frozen on "Doing agbhax..."
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Frozen on "Doing agbhax..."</u></summary>
|
||||
There may be an issue with your `arm11code.bin` file. Re-download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place it on the root of your SD card, and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
If you have a Taiwanese unit (with a T in the version string, ie. 11.3.0-##T), you will not be able to follow these instructions, and you will need to update your console and follow [Seedminer](seedminer) instead.
|
||||
|
||||
If you have a Mainland Chinese unit (with a C in the version string, ie. 11.3.0-##C), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "PrepareArm9ForTwl returned error c8804631!"
|
||||
{% capture compat %}
|
||||
<summary><u>"PrepareArm9ForTwl returned error c8804631!"</u></summary>
|
||||
|
||||
You will need to follow an alternate method. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to mount the SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## BannerBomb3
|
||||
|
||||
### DSiWare Management menu crashes without showing BB3 multihax menu
|
||||
|
||||
Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. If it is, then re-create it with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen).
|
||||
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow [an alternate branch of Seedminer](homebrew-launcher-(pichaxx)). If Safe Mode doesn't work or you need assistance with this matter, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
|
||||
### DSiWare Management menu does not crash
|
||||
|
||||
`F00D43D5.bin` is missing from `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. Make sure that `Nintendo DSiWare` is correctly spelled and spaced. Uppercase/lowercase does not matter.
|
||||
|
||||
### DSiWare Management shows a question mark
|
||||
|
||||
There may be an issue with your `F00D43D5.bin` file (it may be corrupted or intended for the wrong 3DS). Re-create your `F00D43D5.bin` file with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen), ensuring that you use the `movable.sed` file for your console.
|
||||
|
||||
---
|
||||
|
||||
## Installing boot9strap (USM)
|
||||
|
||||
### Update doesn't fail with error code `003-1099`
|
||||
|
||||
unSAFE_MODE is not installed. Follow the instructions on your page to install unSAFE_MODE again.
|
||||
|
||||
### Red screen when selecting detailed setup
|
||||
|
||||
The file `usm.bin` is missing or misplaced. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/download/v1.3/usm.bin) and place `usm.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
There is also a possibility that the console isn't reading your SD card. Make sure it is inserted and formatted correctly.
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
### Failed to mount the SD card!
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
|
||||
---
|
||||
|
||||
## Installing boot9strap (Fredtool)
|
||||
|
||||
### Error on Fredtool Injector page
|
||||
|
||||
Ensure that your `movable.sed` and DSiWare backup come from the same console. A mismatch will result in an error.
|
||||
|
||||
### Unable to select the "Haxxxxxxxxx!" title because of the BB3 multihax menu
|
||||
|
||||
You forgot to delete `F00D43D5.bin` from the SD card. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card and delete the `F00D43D5.bin` file.
|
||||
|
||||
### "Haxxxxxxxxx!" does not appear
|
||||
|
||||
There is an issue with your `42383821.bin` file (it is incorrect, missing, misplaced, or corrupted). Re-create your files with the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website and ensure that you place the `42383821.bin` file from `output.zip` -> `hax` in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`.
|
||||
|
||||
### DS Connection Settings launches normally
|
||||
|
||||
`Haxxxxxxxxx!` was not copied from your SD card to your system memory.
|
||||
|
||||
### Black screen when launching DS Connection Settings
|
||||
|
||||
Your DS Connection Settings application is broken, and you will need Homebrew Launcher access to fix this issue. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
|
||||
### SD card is grayed out
|
||||
|
||||
Flipnote may take a long time to index your card if you have a large SD card. Let it sit for a few minutes.
|
||||
|
||||
### Lenny face does not appear
|
||||
|
||||
You did not copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card.
|
||||
|
||||
### Flipnote is frozen
|
||||
|
||||
You may have accidentally touched the touch screen while in the modified Flipnote. Re-enter DS Connection Settings and try again, ensuring that you don't accidentally use the touchscreen.
|
||||
|
||||
### Green screen after pasting
|
||||
|
||||
The file `boot.nds` is missing or misplaced. Download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
|
||||
### White screen after pasting
|
||||
|
||||
There is an issue with your `boot.nds` file. Re-download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
|
||||
### Unable to open Luma3DS configuration menu after running b9stool
|
||||
|
||||
It is possible that boot9strap was not successfully installed. Follow section B of [this page](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md).
|
||||
|
||||
---
|
||||
|
||||
## Finalizing Setup
|
||||
|
||||
### Unable to update device
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to update device</u></summary>
|
||||
|
||||
The steps below can be attempted in any order, but are listed from easiest to hardest to perform.
|
||||
|
||||
|
|
@ -289,37 +429,41 @@ The steps below can be attempted in any order, but are listed from easiest to ha
|
|||
1. Nintendo servers may be down; Try again later
|
||||
1. If you still get an error, [follow CTRTransfer](ctrtransfer), then try again
|
||||
1. For further support (in English), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Unable to enter Rosalina due to broken button(s)
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to enter Rosalina menu due to broken Left Shoulder / Down D-Pad / Select button(s)</u></summary>
|
||||
|
||||
Download this [alternate config.ini](https://cdn.discordapp.com/attachments/196635695958196224/982798396265988186/config.ini) and place it in `/luma/`. This will change the Rosalina key combination to (X) + (Y).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An exception occurred" after trying to launch Homebrew Launcher via Download Play
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" after trying to launch Homebrew Launcher from Download Play</u></summary>
|
||||
|
||||
There is an issue with your `boot.3dsx` file (it is missing, misplaced, or corrupted). Download the latest release of [the Homebrew Launcher](https://github.com/devkitPro/3ds-hbmenu/releases/latest) and place `boot.3dsx` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "Scripts directory not found" in GodMode9
|
||||
{% capture compat %}
|
||||
<summary><u>"Scripts directory not found" in GodMode9</u></summary>
|
||||
|
||||
You did not copy the `gm9` folder from the GodMode9 `.zip` to the root of your SD card. Download the latest release of [GodMode9](https://github.com/d0k3/GodMode9/releases/latest) and place the `gm9` folder on the root of your SD card, merging it with the existing one.
|
||||
|
||||
### `essentials.exefs` missing from `/gm9/out/`
|
||||
|
||||
Your device had custom firmware in the past, so you were not automatically prompted to make a backup. Make a backup manually:
|
||||
|
||||
1. Reinsert your SD card into your device
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Navigate to `[S:] SYSNAND VIRTUAL`
|
||||
1. Select `essentials.exefs`, then `Copy to 0:/gm9/out/`
|
||||
1. You should now have `essentials.exefs` in `/gm9/out/`
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## Boot-related issues on modded devices
|
||||
## Boot issues on devices with custom firmware
|
||||
|
||||
The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
|
||||
{: .notice--info}
|
||||
|
||||
### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
|
||||
### Power/notification light indicators
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>My device powers off when I try to turn it on, and/or the notification LED shows a color on boot</u></summary>
|
||||
|
||||
There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
|
||||
|
||||
|
|
@ -332,11 +476,15 @@ If the notification LED flashes:
|
|||
You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
|
||||
|
||||
If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### My device gets stuck on a black screen, with a static blue light
|
||||
{% capture compat %}
|
||||
<summary><u>My device gets stuck on a black screen with blue power light staying on</u></summary>
|
||||
|
||||
The steps below can be attempted in any order, but are listed from least to most time-consuming.
|
||||
|
||||
1. Power off your device, remove the SD card, re-insert it, then power on your device.
|
||||
1. Power off your device, eject the game cartridge if inserted, power on your device, then wait up to ten minutes. If your device boots within ten minutes, the issue has been fixed and is unlikely to reoccur
|
||||
1. Rename the `Nintendo 3DS` folder on your SD card to `Nintendo 3DS_BACKUP`, then attempt to boot. If your device successfully boots, there is some issue within your `Nintendo 3DS` folder. Try clearing HOME Menu extdata:
|
||||
+ Navigate to `/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/`
|
||||
|
|
@ -354,35 +502,48 @@ The steps below can be attempted in any order, but are listed from least to most
|
|||
+ If you were successful, the device will boot to an "update your system" screen
|
||||
1. Follow the [CTRTransfer](ctrtransfer) guide
|
||||
1. For further support, ask for help at [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### My device boots to an error screen
|
||||
### Error message on boot
|
||||
|
||||
#### "An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"</u></summary>
|
||||
|
||||
Your Luma3DS version is outdated. Download the latest release of [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### "An error has occurred. Hold down the POWER button to turn off the power..."
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..."</u></summary>
|
||||
|
||||
ARM11 exception handlers are disabled, or custom firmware is not installed. Try enabling ARM11 exception handlers:
|
||||
+ Power off your device
|
||||
+ Hold (Select)
|
||||
+ Power on your device, while still holding (Select)
|
||||
+ If the "Disable ARM11 exception handlers" box is checked, uncheck it
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Some other error
|
||||
|
||||
Please take a photo of the error and join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
|
||||
### Blue "Bootrom Error" screen
|
||||
{% capture compat %}
|
||||
<summary><u>Blue "BOOTROM ERROR" screen</u></summary>
|
||||
|
||||
Your device is likely hard-bricked. You will need to buy an ntrboot flashcart to reinstall boot9strap in order to attempt to fix your device. This may also indicate a hardware issue that cannot be fixed. In any case, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
+ It is also possible that someone has set a boot-time splash screen that just looks like a brick. Try leaving your device powered on, waiting on the blue screen, for five minutes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary><u>Some other error</u></summary>
|
||||
|
||||
## Functionality-related issues on modded devices
|
||||
Please take a photo of the error and join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### DSi / DS functionality is broken or has been replaced with Flipnote Studio
|
||||
## Software issues on devices with custom firmware
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DSi / DS functionality is broken or has been replaced with Flipnote Studio</u></summary>
|
||||
|
||||
1. Download the latest release of [TWLFix-CFW](https://github.com/MechanicalDragon0687/TWLFix-CFW/releases/latest) (the `.3dsx` file)
|
||||
1. Power off your device
|
||||
|
|
@ -396,20 +557,29 @@ Your device is likely hard-bricked. You will need to buy an ntrboot flashcart to
|
|||
1. Perform a System Update by going to System Settings, then "Other Settings", then going all the way to the right and using "System Update"
|
||||
+ The update will see that the essential TWL titles have been uninstalled, and will redownload and reinstall them
|
||||
1. Once the update is complete, tap "OK" to reboot the device
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### GBA Virtual Console and/or Safe Mode functionality is broken
|
||||
{% capture compat %}
|
||||
<summary><u>GBA Virtual Console and/or Safe Mode functionality is broken</u></summary>
|
||||
|
||||
Your device is running Luma3DS/AuReiNand 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your device to a modern custom firmware environment.
|
||||
Your device is running Luma3DS 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your device to a modern custom firmware environment.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Extended memory mode games are broken
|
||||
{% capture compat %}
|
||||
<summary><u>Extended memory mode games (Pokemon Sun/Moon, Smash, etc.) don't work</u></summary>
|
||||
|
||||
This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will need to system format your device to fix this issue.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## Other troubleshooting
|
||||
|
||||
### Clear HOME Menu extdata
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu extdata</u></summary>
|
||||
|
||||
1. Power off your device
|
||||
1. Εισάγετε την κάρτα SD στον υπολογιστή σας
|
||||
|
|
@ -422,8 +592,11 @@ This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will n
|
|||
+ **KOR Region**: `000000A9`
|
||||
+ **TWN Region**: `000000B1`
|
||||
1. Reinsert your SD card into your device
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Clear HOME Menu theme data
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu theme data</u></summary>
|
||||
|
||||
1. Power off your device
|
||||
1. Εισάγετε την κάρτα SD στον υπολογιστή σας
|
||||
|
|
@ -433,3 +606,6 @@ This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will n
|
|||
+ **JPN Region**: `000002cc`
|
||||
+ **USA Region**: `000002cd`
|
||||
1. Reinsert your SD card into your device
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@ The purpose of this section is to check whether built-in DS mode applications wi
|
|||
+ If your console displays the Japanese version of Flipnote Studio, a black screen, or an error message, the test has failed
|
||||
1. Power off your device
|
||||
|
||||
If either of these tests has failed, DS mode, DS Download Play, and/or DS Connection Settings may be inaccessible once CFW is uninstalled! You should [fix DS mode](troubleshooting#dsi--ds-functionality-is-broken-or-has-been-replaced-with-flipnote-studio) before continuing.
|
||||
If either of these tests has failed, DS mode, DS Download Play, and/or DS Connection Settings may be inaccessible once CFW is uninstalled! You should [fix DS mode](troubleshooting#software-issues-on-devices-with-custom-firmware) before continuing.
|
||||
{: .notice--warning}
|
||||
|
||||
#### Section III - Safety Test
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ Fer all steps in 'tis section, overwrite any existin' files on ye SD card.
|
|||
1. Ye device should have rebooted into th' Luma3DS configuration menu
|
||||
+ Luma3DS configuration menu are settings for the Luma3DS custom firmware. Many of these settings may be useful for customization or debugging
|
||||
+ For the purpose of this guide, these settings will be left on default settings
|
||||
+ If you get a black screen, [follow this troubleshooting guide](troubleshooting#boot-related-issues-on-modded-devices)
|
||||
+ If you get a black screen, [follow this troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware)
|
||||
1. Press (Start) to save 'n reboot
|
||||
|
||||
___
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ This is an add-on section to check if your console already has a modern custom f
|
|||
|
||||
If your console already has an arm9loaderhax or boot9strap based custom firmware, you will need to follow the instructions indicated to upgrade your setup to a modern one.
|
||||
|
||||
If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#clear-home-menu-extdata), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
|
||||
If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#other-troubleshooting), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
|
||||
{: .notice--info}
|
||||
|
||||
### Instructions
|
||||
|
|
|
|||
|
|
@ -14,79 +14,173 @@ title: "FAQ"
|
|||
|
||||
## Pre-Installation FAQ
|
||||
|
||||
#### **Q:** *I am on the latest system version. Is my device hackable without any external hardware?*
|
||||
**A:** Yes! The latest firmware (11.16.0) has a free method for getting CFW named [Seedminer](seedminer).
|
||||
{% capture compat %}
|
||||
<summary><u>I am on the latest system version. Is my device hackable without any external hardware?</u></summary>
|
||||
|
||||
#### **Q:** *What devices is this guide compatible with?*
|
||||
**A:** The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. If your system version string displays as "0.0.0-0", then you may have a developer unit.
|
||||
Yes! The latest firmware (11.16.0) has a free method for getting CFW named [Seedminer](seedminer).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How risky is hacking my console?*
|
||||
**A:** Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
{% capture compat %}
|
||||
<summary><u>What devices is this guide compatible with?</u></summary>
|
||||
|
||||
#### **Q:** *Can I run awesome homebrew and emulators with this?*
|
||||
**A:** Yes! This guide will install a few useful homebrew applications, including [Universal-Updater](https://github.com/Universal-Team/Universal-Updater/releases/latest), which acts as a homebrew app store.
|
||||
The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. If your system version string displays as "0.0.0-0", then you may have a developer unit.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I use this to play games from other regions?*
|
||||
**A:** Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Some games may need to make use of Luma's [locale emulation feature](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) in order to work properly on out-of-region devices.
|
||||
{% capture compat %}
|
||||
<summary><u>How risky is hacking my console?</u></summary>
|
||||
|
||||
#### **Q:** *Will I lose any features if I install CFW?*
|
||||
**A:** No. Devices with custom firmware can still use the eShop and run physical cartridges as any other 3DS can.
|
||||
Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I keep my NNID?*
|
||||
**A:** Your NNID (if you have one) will not be affected by this guide. Devices with a region of KOR, CHN, or TWN do not have NNID functionality to begin with and are thus unaffected.
|
||||
{% capture compat %}
|
||||
<summary><u>Can I run awesome homebrew and emulators with this?</u></summary>
|
||||
|
||||
#### **Q:** *Will my 3DS be banned for having CFW?*
|
||||
**A:** There was a ban wave in May 2017 that banned CFW users from online play (eShop access, NNIDs, and Nintendo Accounts were unaffected), seemingly at random. A ban wave at such a scale has not been seen since. That being said, we don't know what Nintendo may have in store in the future. At this time, we don't think that bans are something that you need to worry about.
|
||||
Yes! This guide will install a few useful homebrew applications, including [Universal-Updater](https://github.com/Universal-Team/Universal-Updater/releases/latest), which acts as a homebrew app store.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I do this without a computer (e.g. an Android phone)?*
|
||||
**A:** All you need is the ability to put files on a compatible SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Can I use this to play games from other regions?</u></summary>
|
||||
|
||||
#### **Q:** *What size SD card can I use?*
|
||||
**A:** You will need at least 1.5GB of free SD card space to follow this guide in its entirety. While the 3DS is officially compatible with SD cards up to 32GB, larger SD cards can be used if they are manually re-formatted as FAT32. It is not recommended to use SD cards greater than 128GB due to known issues with GBA graphics and custom themes.
|
||||
Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Some games may need to make use of Luma's [locale emulation feature](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) in order to work properly on out-of-region devices.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *I heard about this thing I have to pay for (Gateway, Sky3DS, ntrboot, R4, etc). Is that something I need?*
|
||||
**A:** No. Custom firmware can be installed for free on the latest firmware without any hardware devices. In fact, 3DS-mode flashcarts like Gateway and Sky3DS are not recommended because they are obsolete and may carry ban or brick risk.
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose any features if I install CFW?</u></summary>
|
||||
|
||||
#### **Q:** *What's the difference between custom firmware and homebrew access?*
|
||||
**A:** Historically, the 3DS used to have userland homebrew access through older exploits like ninjhax. The level of system access granted with userland allowed you to run basic homebrew and emulators but did not allow you to (easily) modify games or dump cartridges. It was also a lot less stable, with homebrew often ungracefully crashing and requiring a full reboot. Custom firmware grants a far greater level of system access while also being more stable than homebrew-only entrypoints.
|
||||
No. Devices with custom firmware can still use the eShop and run physical cartridges as any other 3DS can.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I keep my NNID?</u></summary>
|
||||
|
||||
Your NNID (if you have one) will not be affected by this guide. Devices with a region of KOR, CHN, or TWN do not have NNID functionality to begin with and are thus unaffected.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will my 3DS be banned for having CFW?</u></summary>
|
||||
|
||||
There was a ban wave in May 2017 that banned CFW users from online play (eShop access, NNIDs, and Nintendo Accounts were unaffected), seemingly at random. A ban wave at such a scale has not been seen since. That being said, we don't know what Nintendo may have in store in the future. At this time, we don't think that bans are something that you need to worry about.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I do this without a computer (e.g. an Android phone)?</u></summary>
|
||||
|
||||
Yes! All you need is the ability to put files on a compatible SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What size SD card can I use?</u></summary>
|
||||
|
||||
You will need at least 1.5GB of free SD card space to follow this guide in its entirety. While the 3DS is officially compatible with SD cards up to 32GB, larger SD cards can be used if they are manually re-formatted as FAT32. It is not recommended to use SD cards greater than 128GB due to known issues with GBA graphics and custom themes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>I heard about this thing I have to pay for (Gateway, Sky3DS, ntrboot, R4, etc). Is that something I need?</u></summary>
|
||||
|
||||
No. Custom firmware can be installed for free on the latest firmware without any hardware devices. In fact, 3DS-mode flashcarts like Gateway and Sky3DS are not recommended because they are obsolete and may carry ban or brick risk.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What's the difference between custom firmware and homebrew?</u></summary>
|
||||
|
||||
Historically, the 3DS used to have userland homebrew access through older exploits like ninjhax. The level of system access granted with userland allowed you to run basic homebrew and emulators but did not allow you to (easily) modify games or dump cartridges. It was also a lot less stable, with homebrew often ungracefully crashing and requiring a full reboot. Custom firmware grants a far greater level of system access while also being more stable than homebrew-only entrypoints.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Post-Installation FAQ
|
||||
|
||||
#### **Q:** *Is it safe to update my 3DS to the latest version with CFW?*
|
||||
**A:** If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. There have been updates in the past that have resulted in Luma3DS crashing on boot, so it is a good idea to wait a couple of hours to ensure that the latest update will not temporarily render the device unusable until Luma3DS is updated. System updates can be performed the same way as they are on a stock 3DS: through System Settings, Safe Mode, or the update prompt when the update is automatically downloaded.
|
||||
{% capture compat %}
|
||||
<summary><u>Is it safe to update my 3DS to the latest version with CFW?</u></summary>
|
||||
|
||||
#### **Q:** *How do I upgrade my SD card?*
|
||||
**A:** Copy and paste your SD card contents to a new SD card formatted as FAT32. For 128GB cards, an allocation size of 65536 is recommended. SD cards larger than 128GB are not recommended due to known issues with GBA graphics and custom themes.
|
||||
If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. There have been updates in the past that have resulted in Luma3DS crashing on boot, so it is a good idea to wait a couple of hours to ensure that the latest update will not temporarily render the device unusable until Luma3DS is updated. System updates can be performed the same way as they are on a stock 3DS: through System Settings, Safe Mode, or the update prompt when the update is automatically downloaded.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I system transfer with CFW?*
|
||||
**A:** Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets for illegitimate titles (homebrew) will not transfer, but the titles can be made to reappear with [faketik](https://github.com/ihaveamac/faketik/releases/latest). Make sure that you do not perform a wireless transfer, as this will delete illegitimate titles. CFW will remain on both consoles.
|
||||
{% capture compat %}
|
||||
<summary><u>How do I upgrade my SD card?</u></summary>
|
||||
|
||||
#### **Q:** *How do I change the system language of a Japanese 3DS?*
|
||||
**A:** The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Note that this is very likely to break the Nintendo eShop on your device, which means you will be unable to update your games whether they are in-region or out-of-region.
|
||||
Copy and paste your SD card contents to a new SD card formatted as FAT32. For 128GB cards, an allocation size of 65536 is recommended. SD cards larger than 128GB are not recommended due to known issues with GBA graphics and custom themes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How do I update homebrew applications?*
|
||||
**A:** It depends on the format of the homebrew application. Generally speaking:
|
||||
{% capture compat %}
|
||||
<summary><u>Can I system transfer with CFW?</u></summary>
|
||||
|
||||
Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets for illegitimate titles (homebrew) will not transfer, but the titles can be made to reappear with [faketik](https://github.com/ihaveamac/faketik/releases/latest). Make sure that you do not perform a wireless transfer, as this will delete illegitimate titles. CFW will remain on both consoles.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I change the system language of a Japanese 3DS?</u></summary>
|
||||
|
||||
The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Note that this is very likely to break the Nintendo eShop on your device, which means you will be unable to update your games whether they are in-region or out-of-region.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I update homebrew applications?</u></summary>
|
||||
|
||||
It depends on the format of the homebrew application. Generally speaking:
|
||||
|
||||
* Homebrew in **CIA format** can be updated by installing the new CIA, which will usually overwrite the old one. If the old CIA is not overwritten, you can delete the old one from Data Management as you would any other 3DS title.
|
||||
* Homebrew in **3DSX format** can be updated by replacing the 3DSX file in `/3ds/` with a fresh copy. If the homebrew application includes additional assets, you may need to place that folder somewhere else. Refer to the documentation of the homebrew application.
|
||||
* For updating Luma3DS, see [this page](restoring-updating-cfw). For updating GodMode9, see [this page](godmode9-usage#updating-godmode9).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How do I update games from outside of my 3DS region?*
|
||||
**A:** You will need to [dump the updates](dumping-titles-and-game-cartridges) from a 3DS that has the updates installed. The Nintendo eShop only contains updates for the console's region (a Japanese 3DS will only have updates for Japanese games).
|
||||
{% capture compat %}
|
||||
<summary><u>How do I update my games?</u></summary>
|
||||
|
||||
#### **Q:** *Help! Something bad happened and now I cannot boot...*
|
||||
**A:** Please look at the [troubleshooting guide](troubleshooting). **Uninstalling CFW when your device is in an unbootable state is not recommended, as it is very likely to lead to a brick**.
|
||||
You can continue to download game updates from the Nintendo eShop, even after the 2023 shutdown.
|
||||
|
||||
If the game is not from the same region as the console, you will need to [dump the updates](dumping-titles-and-game-cartridges) from a 3DS that has the updates installed. The Nintendo eShop only contains updates for the console's region (a Japanese 3DS will only have updates for Japanese games).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Help! Something bad happened and my 3DS won't boot to HOME Menu...</u></summary>
|
||||
|
||||
Please look at the [troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware). **Uninstalling CFW when your device is in an unbootable state is not recommended, as it is very likely to lead to a brick**.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## menuhax / A9LH / Gateway FAQ
|
||||
|
||||
#### **Q:** *I modded my device x years ago. What should I do?*
|
||||
**A:** It is recommended that you upgrade your setup to a modern, boot9strap-based one. Follow the [Checking for CFW](checking-for-cfw) guide to see how to upgrade your setup.
|
||||
{% capture compat %}
|
||||
<summary><u>I modded my device (x) years ago, so it already has some sort of homebrew. What should I do?</u></summary>
|
||||
|
||||
#### **Q:** *My setup works for me. Why should I upgrade it?*
|
||||
**A:** The vast majority of modern homebrew (such as Checkpoint and BootNTR Selector) have only been tested on modern, boot9strap-based setups and may not work entirely (or at all) on older setups based on menuhax, A9LH, or Gateway. In addition, depending on your setup, you may be unable to safely update to the latest firmware. Modern, boot9strap-based setups allow for a greater level of system access than previous hacks, including the ability to dump your console's bootrom.
|
||||
It is recommended that you upgrade your setup to a modern, boot9strap-based one. Follow the [Checking for CFW](checking-for-cfw) guide to see how to upgrade your setup.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Will I lose anything if I upgrade my setup?*
|
||||
**A:** Your old setup (including your EmuNAND, if you have one) can usually be directly migrated to boot9strap with no data loss. If you have data that is particularly important to you, it would be a good idea to make a decrypted backup of your save data before upgrading your setup with a tool like [JKSM](https://github.com/J-D-K/JKSM/releases/tag/12%2F20%2F2018).
|
||||
{% capture compat %}
|
||||
<summary><u>My setup works for me. Why should I upgrade it?</u></summary>
|
||||
|
||||
The vast majority of modern homebrew (such as Checkpoint and BootNTR Selector) have only been tested on modern, boot9strap-based setups and may not work entirely (or at all) on older setups based on menuhax, A9LH, or Gateway. In addition, depending on your setup, you may be unable to safely update to the latest firmware. Modern, boot9strap-based setups allow for a greater level of system access than previous hacks, including the ability to dump your console's bootrom.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose anything if I upgrade my setup?</u></summary>
|
||||
|
||||
Your old setup (including your EmuNAND, if you have one) can usually be directly migrated to boot9strap with no data loss. If you have data that is particularly important to you, it would be a good idea to make a decrypted backup of your save data before upgrading your setup with a tool like [JKSM](https://github.com/J-D-K/JKSM/releases/tag/12%2F20%2F2018).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I move saves from an existing Gateway setup to a more modern setup?</u></summary>
|
||||
|
||||
#### **Q:** *How do I move saves from an existing Gateway setup to a more modern setup?*
|
||||
**A:** See [this thread](https://gbatemp.net/threads/425743/).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@ In this section, you will update your system to the latest version, which is saf
|
|||
+ Updates while usin' B9S + Luma (what ye have) be safe
|
||||
+ The updater may display a message saying "Your system is up to date" instead of updating. This is normal if you are already up to date; continue with the next section
|
||||
+ If this gives you an error, set both your DNS settings and Proxy settings to "auto"
|
||||
+ If this still gives you an error, [follow this troubleshooting guide](troubleshooting#unable-to-update-device)
|
||||
+ If this still gives you an error, [follow this troubleshooting guide](troubleshooting#finalizing-setup)
|
||||
|
||||
#### Section III - Homebrew Launcher
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
|||
1. Launch System Settings on your device
|
||||
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#dsiware-management-menu-crashes-without-showing-bb3-multihax-menu)
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#installing-boot9strap-fredtool)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Dump DSiWare"
|
||||
+ Your device will automatically reboot
|
||||
1. Power off ye device
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
|||
1. Launch System Settings on your device
|
||||
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#dsiware-management-menu-crashes-without-showing-bb3-multihax-menu)
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#bannerbomb3)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Install unSAFE_MODE"
|
||||
+ Your device will automatically power off
|
||||
|
||||
|
|
|
|||
|
|
@ -168,7 +168,6 @@ To identify a `<TitleID>.gbavc.sav` file's Title ID, you can get a listing of al
|
|||
1. Reinsert ye SD card into ye device
|
||||
1. Press (A) to remount your SD card
|
||||
1. Press (Start) to reboot
|
||||
1. If you get a black screen, [follow this troubleshooting guide](troubleshooting#ts_sys_down)
|
||||
|
||||
___
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ In this section, you will get the necessary details from your 3DS that are requi
|
|||
+ If you don't have a `Nintendo 3DS` folder, put your SD card into your 3DS and power it on so that the folder can be created
|
||||
1. Copy the name of the 32-letter folder you see directly inside Nintendo 3DS
|
||||
+ This 32-letter name is system-specific and will be different for each console
|
||||
+ If you see multiple 32-letter folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
|
||||
+ If you see multiple 32-letter folders, follow [these instructions](troubleshooting#seedminer)
|
||||
+ You can ignore the `private` folder if you have it
|
||||
|
||||
![]({{ "/images/screenshots/seedminer/id0-example.png" | absolute_url }})
|
||||
|
|
|
|||
|
|
@ -2,37 +2,69 @@
|
|||
title: "Troubleshootin'"
|
||||
---
|
||||
|
||||
{% include toc title="Table of Contents"%}
|
||||
|
||||
This page offers troubleshooting advice for commonly encountered issues. If you are unable to solve your issue with the advice on this page, please join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and describe your issue, including what you have already tried.
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary>Table of Contents</summary>
|
||||
|
||||
Used on multiple pages:
|
||||
* [SafeB9SInstaller](#issues-with-safeb9sinstaller)
|
||||
|
||||
Guide pages:
|
||||
* [Seedminer](#seedminer)
|
||||
* [BannerBomb3](#bannerbomb3)
|
||||
* [Installing boot9strap (USM)](#installing-boot9strap-usm)
|
||||
* [Installing boot9strap (Fredtool)](#installing-boot9strap-fredtool)
|
||||
* [Homebrew Launcher (PicHaxx)](#homebrew-launcher-pichaxx)
|
||||
* [Installing boot9strap (Soundhax)](#installing-boot9strap-soundhax)
|
||||
* [Installing boot9strap (SSLoth-Browser)](#installing-boot9strap-ssloth-browser)
|
||||
|
||||
* [Finalizing Setup](#finalizing-setup)
|
||||
|
||||
Issues after installation:
|
||||
* [Boot issues](#boot-issues-on-devices-with-custom-firmware)
|
||||
* [Software issues](#software-issues-on-devices-with-custom-firmware)
|
||||
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
{: .notice--info}
|
||||
|
||||
## Issues with SafeB9SInstaller
|
||||
|
||||
### SigHaxed FIRM was not installed! Check lower screen for more info.
|
||||
|
||||
#### SigHaxed FIRM - File not found
|
||||
{% capture compat %}
|
||||
<summary><u>SigHaxed FIRM - File not found</u></summary>
|
||||
|
||||
You are missing `boot9strap.firm` and `boot9strap.firm.sha` from the `boot9strap` folder, or the `boot9strap` folder is misnamed. Download the latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip), and place `boot9strap.firm` and `boot9strap.firm.sha` in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### SigHaxed FIRM - invalid FIRM
|
||||
{% capture compat %}
|
||||
<summary><u>SigHaxed FIRM - invalid FIRM</u></summary>
|
||||
|
||||
There is an issue with your `boot9strap.firm` and `boot9strap.firm.sha` files. Re-download the latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip), and place `boot9strap.firm` and `boot9strap.firm.sha` in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Secret Sector - File not found
|
||||
{% capture compat %}
|
||||
<summary><u>Secret Sector - File not found</u></summary>
|
||||
|
||||
You are missing `secret_sector.bin` from the `boot9strap` folder, or the `boot9strap` folder is misnamed. Download [secret_sector.bin](magnet:?xt=urn:btih:15a3c97acf17d67af98ae8657cc66820cc58f655&dn=secret_sector.bin&tr=udp%3a%2f%2ftracker.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.lelux.fi%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.loadbt.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.moeking.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.monitorit4.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.ololosh.space%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.pomf.se%3a80%2fannounce&tr=udp%3a%2f%2ftracker.srv00.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.theoks.net%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.tiny-vps.com%3a6969%2fannounce&tr=udp%3a%2f%2fopen.tracker.cl%3a1337%2fannounce&tr=udp%3a%2f%2ftracker.zerobytes.xyz%3a1337%2fannounce&tr=udp%3a%2f%2ftracker1.bt.moack.co.kr%3a80%2fannounce&tr=udp%3a%2f%2fvibe.sleepyinternetfun.xyz%3a1738%2fannounce&tr=udp%3a%2f%2fwww.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a6969%2fannounce&tr=udp%3a%2f%2f9.rarbg.com%3a2810%2fannounce&tr=udp%3a%2f%2ftracker.opentrackr.org%3a1337%2fannounce&tr=udp%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fopenbittorrent.com%3a80%2fannounce) using a torrent client, and place it in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Something else
|
||||
{% capture compat %}
|
||||
<summary><u>Something else</u></summary>
|
||||
|
||||
Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance, and describe the message that you see.
|
||||
|
||||
---
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Seedminer
|
||||
|
||||
### Multiple long folder names in Nintendo 3DS folder
|
||||
{% capture compat %}
|
||||
<summary><u>Multiple long folder names in Nintendo 3DS folder</u></summary>
|
||||
|
||||
![]({{ "/images/screenshots/multiple-id0.png" | absolute_url }})
|
||||
{: .notice--info}
|
||||
|
|
@ -49,98 +81,285 @@ This occurs when you use your SD card in multiple 3DS devices and is intended to
|
|||
+ This is your true ID0 that you will use in [Section II of Seedminer](seedminer#section-ii---seedminer)
|
||||
1. Delete the `Nintendo 3DS` folder
|
||||
1. Rename the `BACKUP_Nintendo 3DS` folder to `Nintendo 3DS`
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Bruteforce Movable skips to step 4
|
||||
{% capture compat %}
|
||||
<summary><u>Bruteforce Movable skips to step 4</u></summary>
|
||||
|
||||
The website has already mined your `movable.sed` using your friend code and ID0 combination. You can use the `movable.sed` that it provides you.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Important! You have been locked out of the automated part1 dumper system...
|
||||
{% capture compat %}
|
||||
<summary><u>Important! You have been locked out of the automated part1 dumper system...</u></summary>
|
||||
|
||||
Your friend code was blocked from using the friend code bot because your 3DS did not successfully friend the bot. Ensure your 3DS is properly connected to the Internet, then join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask to be unlocked.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### We were unable to successfully complete your bruteforce request. :`(
|
||||
{% capture compat %}
|
||||
<summary><u>We were unable to successfully complete your bruteforce request. :`(</u></summary>
|
||||
|
||||
The website has determined that your `movable.sed` cannot be brute-forced. Ensure that you gave the correct ID0 to the website. If your ID0 is correct, then you will be unable to use Seedminer and you will have to use an alternate method that will require additional games or hardware.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
## BannerBomb3
|
||||
|
||||
## Homebrew Launcher (PicHaxx)
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management menu crashes without showing BB3 multihax menu</u></summary>
|
||||
Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. If it is, then re-create it with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen).
|
||||
|
||||
### "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
Your `00000001.sav` and/or `otherapp.bin` files may be misplaced. Ensure that `00000001.sav` is in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data` and that `otherapp.bin` is on the root of your SD card.
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow [an alternate branch of Seedminer](homebrew-launcher-(pichaxx)). If Safe Mode doesn't work or you need assistance with this matter, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
If your files are in the correct locations, re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx), then place it in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`. Ensure that the file is named exactly `00000001.sav` and that you used your console's `movable.sed` to create it. Re-download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management menu does not crash</u></summary>
|
||||
|
||||
### "An exception occurred" or Errdisp when opening Picross
|
||||
`F00D43D5.bin` is missing from `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. Make sure that `Nintendo DSiWare` is correctly spelled and spaced. Uppercase/lowercase does not matter.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
Your device already has custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management shows a question mark</u></summary>
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
There may be an issue with your `F00D43D5.bin` file (it may be corrupted or intended for the wrong 3DS). Re-create your `F00D43D5.bin` file with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen), ensuring that you use the `movable.sed` file for your console.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
There is an issue with your `otherapp.bin` file. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
## Installing boot9strap (USM)
|
||||
|
||||
### Game starts normally
|
||||
{% capture compat %}
|
||||
<summary><u>Safe Mode system update succeeds instead of giving error 003-1099</u></summary>
|
||||
|
||||
Your modified `00000001.sav` file may be misplaced, or you may have used the wrong `movable.sed` when creating it. Re-generate your `movable.sed` from [Bruteforce Movable](https://seedminer.hacks.guide), then re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx) and place the resulting file (`00000001.sav`) in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`.
|
||||
unSAFE_MODE is not installed. [Follow the instructions](installing-boot9strap-(usm)] to install it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary><u>Red screen after selecting "Detailed Setup"</u></summary>
|
||||
|
||||
## Installing boot9strap (Soundhax)
|
||||
The file `usm.bin` is missing or misplaced. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/download/v1.3/usm.bin) and place `usm.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
### Red/purple/pink and white screen after running Soundhax
|
||||
There is also a possibility that the console isn't reading your SD card. Make sure it is inserted and formatted correctly.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
If your device is not on those firmwares, it likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
|
||||
There is an issue with your `otherapp.bin` file (it is missing, misplaced, or corrupted). Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) and place it on the root of your SD card.
|
||||
|
||||
### "Could not play"
|
||||
|
||||
You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow [Seedminer](seedminer).
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to mount the SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
## Installing boot9strap (Fredtool)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Error on Fredtool Injector page</u></summary>
|
||||
|
||||
Ensure that your `movable.sed` and DSiWare backup come from the same console. A mismatch will result in an error.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to select "Haxxxxxxxxx!" because the BB3 multihax menu appears</u></summary>
|
||||
|
||||
You forgot to delete `F00D43D5.bin` from the SD card. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card and delete the `F00D43D5.bin` file.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"Haxxxxxxxxx!" does not appear</u></summary>
|
||||
|
||||
There is an issue with your `42383821.bin` file (it is incorrect, missing, misplaced, or corrupted). Re-create your files with the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website and ensure that you place the `42383821.bin` file from `output.zip` -> `hax` in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DS Connection Settings launches normally</u></summary>
|
||||
|
||||
`Haxxxxxxxxx!` was not copied from your SD card to your system memory.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Black screen when launching DS Connection Settings</u></summary>
|
||||
|
||||
Your DS Connection Settings application is broken, and you will need Homebrew Launcher access to fix this issue. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>SD card is grayed out in Flipnote</u></summary>
|
||||
|
||||
Flipnote may take a long time to index your card if you have a large SD card. Let it sit for a few minutes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Lenny face does not appear in SD card section</u></summary>
|
||||
|
||||
You did not copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Flipnote freezes</u></summary>
|
||||
|
||||
You may have accidentally touched the touch screen while in the modified Flipnote. Re-enter DS Connection Settings and try again, ensuring that you don't accidentally use the touchscreen.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Green screen after pasting</u></summary>
|
||||
|
||||
The file `boot.nds` is missing or misplaced. Download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>White screen after pasting</u></summary>
|
||||
There is an issue with your `boot.nds` file. Re-download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to open Luma3DS configuration menu after running B9STool</u></summary>
|
||||
|
||||
It is possible that boot9strap was not successfully installed. Follow section B of [this page](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Homebrew Launcher (PicHaxx)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
|
||||
|
||||
Your `00000001.sav` and/or `otherapp.bin` files may be misplaced. Ensure that `00000001.sav` is in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data` and that `otherapp.bin` is on the root of your SD card.
|
||||
|
||||
If your files are in the correct locations, re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx), then place it in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`. Ensure that the file is named exactly `00000001.sav` and that you used your console's `movable.sed` to create it. Re-download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" or Errdisp when opening Picross</u></summary>
|
||||
|
||||
Your device already has custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `otherapp.bin` file. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Game starts normally</u></summary>
|
||||
|
||||
Your modified `00000001.sav` file may be misplaced, or you may have used the wrong `movable.sed` when creating it. Re-generate your `movable.sed` from [Bruteforce Movable](https://seedminer.hacks.guide), then re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx) and place the resulting file (`00000001.sav`) in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Installing boot9strap (Soundhax)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Soundhax</u></summary>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
If your device is not on those firmwares, it likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `otherapp.bin` file (it is missing, misplaced, or corrupted). Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) and place it on the root of your SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"Could not play"</u></summary>
|
||||
|
||||
You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow [Seedminer](seedminer).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Installing boot9strap (SSLoth-Browser)
|
||||
|
||||
### Red/purple/pink and white screen after running browserhax
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Browserhax</u></summary>
|
||||
|
||||
This likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
|
||||
|
||||
The file `arm11code.bin` is missing or misplaced. Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place `otherapp.bin` on the root of your SD card and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `arm11code.bin` file. Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place `otherapp.bin` on the root of your SD card and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Opening the browserhax QR code or URL crashes
|
||||
{% capture compat %}
|
||||
<summary><u>Opening the browserhax QR code or URL crashes</u></summary>
|
||||
|
||||
Browser based exploits (such as this one) are often unstable and crash frequently, but they can sometimes be fixed by doing the following steps.
|
||||
|
||||
1. Launch the browser, then launch the browser settings
|
||||
1. Scroll to the bottom and Initialize Savedata (it also may be called Clear All Save Data)
|
||||
1. Try the exploit again
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Opening the browser prompts for a system update instead
|
||||
{% capture compat %}
|
||||
<summary><u>System Update prompt when opening browser</u></summary>
|
||||
|
||||
The SSLoth proxy was incorrectly configured. Re-do the SSLoth section on the page.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Error 032-0420 when trying to open the browser
|
||||
{% capture compat %}
|
||||
<summary><u>Error 032-0420 when opening browser</u></summary>
|
||||
|
||||
Follow these steps in order:
|
||||
|
||||
|
|
@ -157,126 +376,47 @@ Follow these steps in order:
|
|||
1. If prompted about a system update, press OK
|
||||
+ This won't actually update the system
|
||||
1. Start again from [Section II](installing-boot9strap-(ssloth-browser).html#section-ii---ssloth)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Frozen on "Doing agbhax..."
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Frozen on "Doing agbhax..."</u></summary>
|
||||
There may be an issue with your `arm11code.bin` file. Re-download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place it on the root of your SD card, and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
If you have a Taiwanese unit (with a T in the version string, ie. 11.3.0-##T), you will not be able to follow these instructions, and you will need to update your console and follow [Seedminer](seedminer) instead.
|
||||
|
||||
If you have a Mainland Chinese unit (with a C in the version string, ie. 11.3.0-##C), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "PrepareArm9ForTwl returned error c8804631!"
|
||||
{% capture compat %}
|
||||
<summary><u>"PrepareArm9ForTwl returned error c8804631!"</u></summary>
|
||||
|
||||
You will need to follow an alternate method. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to mount the SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## BannerBomb3
|
||||
|
||||
### DSiWare Management menu crashes without showing BB3 multihax menu
|
||||
|
||||
Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. If it is, then re-create it with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen).
|
||||
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow [an alternate branch of Seedminer](homebrew-launcher-(pichaxx)). If Safe Mode doesn't work or you need assistance with this matter, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
|
||||
### DSiWare Management menu does not crash
|
||||
|
||||
`F00D43D5.bin` is missing from `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. Make sure that `Nintendo DSiWare` is correctly spelled and spaced. Uppercase/lowercase does not matter.
|
||||
|
||||
### DSiWare Management shows a question mark
|
||||
|
||||
There may be an issue with your `F00D43D5.bin` file (it may be corrupted or intended for the wrong 3DS). Re-create your `F00D43D5.bin` file with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen), ensuring that you use the `movable.sed` file for your console.
|
||||
|
||||
---
|
||||
|
||||
## Installing boot9strap (USM)
|
||||
|
||||
### Update doesn't fail with error code `003-1099`
|
||||
|
||||
unSAFE_MODE is not installed. Follow the instructions on your page to install unSAFE_MODE again.
|
||||
|
||||
### Red screen when selecting detailed setup
|
||||
|
||||
The file `usm.bin` is missing or misplaced. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/download/v1.3/usm.bin) and place `usm.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
There is also a possibility that the console isn't reading your SD card. Make sure it is inserted and formatted correctly.
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
### Failed to mount the SD card!
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
|
||||
---
|
||||
|
||||
## Installing boot9strap (Fredtool)
|
||||
|
||||
### Error on Fredtool Injector page
|
||||
|
||||
Ensure that your `movable.sed` and DSiWare backup come from the same console. A mismatch will result in an error.
|
||||
|
||||
### Unable to select the "Haxxxxxxxxx!" title because of the BB3 multihax menu
|
||||
|
||||
You forgot to delete `F00D43D5.bin` from the SD card. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card and delete the `F00D43D5.bin` file.
|
||||
|
||||
### "Haxxxxxxxxx!" does not appear
|
||||
|
||||
There is an issue with your `42383821.bin` file (it is incorrect, missing, misplaced, or corrupted). Re-create your files with the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website and ensure that you place the `42383821.bin` file from `output.zip` -> `hax` in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`.
|
||||
|
||||
### DS Connection Settings launches normally
|
||||
|
||||
`Haxxxxxxxxx!` was not copied from your SD card to your system memory.
|
||||
|
||||
### Black screen when launching DS Connection Settings
|
||||
|
||||
Your DS Connection Settings application is broken, and you will need Homebrew Launcher access to fix this issue. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
|
||||
### SD card is grayed out
|
||||
|
||||
Flipnote may take a long time to index your card if you have a large SD card. Let it sit for a few minutes.
|
||||
|
||||
### Lenny face does not appear
|
||||
|
||||
You did not copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card.
|
||||
|
||||
### Flipnote is frozen
|
||||
|
||||
You may have accidentally touched the touch screen while in the modified Flipnote. Re-enter DS Connection Settings and try again, ensuring that you don't accidentally use the touchscreen.
|
||||
|
||||
### Green screen after pasting
|
||||
|
||||
The file `boot.nds` is missing or misplaced. Download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
|
||||
### White screen after pasting
|
||||
|
||||
There is an issue with your `boot.nds` file. Re-download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
|
||||
### Unable to open Luma3DS configuration menu after running b9stool
|
||||
|
||||
It is possible that boot9strap was not successfully installed. Follow section B of [this page](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md).
|
||||
|
||||
---
|
||||
|
||||
## Finalizing Setup
|
||||
|
||||
### Unable to update device
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to update device</u></summary>
|
||||
|
||||
The steps below can be attempted in any order, but are listed from easiest to hardest to perform.
|
||||
|
||||
|
|
@ -289,37 +429,41 @@ The steps below can be attempted in any order, but are listed from easiest to ha
|
|||
1. Nintendo servers may be down; Try again later
|
||||
1. If you still get an error, [follow CTRTransfer](ctrtransfer), then try again
|
||||
1. For further support (in English), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Unable to enter Rosalina due to broken button(s)
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to enter Rosalina menu due to broken Left Shoulder / Down D-Pad / Select button(s)</u></summary>
|
||||
|
||||
Download this [alternate config.ini](https://cdn.discordapp.com/attachments/196635695958196224/982798396265988186/config.ini) and place it in `/luma/`. This will change the Rosalina key combination to (X) + (Y).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An exception occurred" after trying to launch Homebrew Launcher via Download Play
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" after trying to launch Homebrew Launcher from Download Play</u></summary>
|
||||
|
||||
There is an issue with your `boot.3dsx` file (it is missing, misplaced, or corrupted). Download the latest release of [the Homebrew Launcher](https://github.com/devkitPro/3ds-hbmenu/releases/latest) and place `boot.3dsx` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "Scripts directory not found" in GodMode9
|
||||
{% capture compat %}
|
||||
<summary><u>"Scripts directory not found" in GodMode9</u></summary>
|
||||
|
||||
You did not copy the `gm9` folder from the GodMode9 `.zip` to the root of your SD card. Download the latest release of [GodMode9](https://github.com/d0k3/GodMode9/releases/latest) and place the `gm9` folder on the root of your SD card, merging it with the existing one.
|
||||
|
||||
### `essentials.exefs` missing from `/gm9/out/`
|
||||
|
||||
Your device had custom firmware in the past, so you were not automatically prompted to make a backup. Make a backup manually:
|
||||
|
||||
1. Reinsert ye SD card into ye device
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Navigate to `[S:] SYSNAND VIRTUAL`
|
||||
1. Select `essentials.exefs`, then `Copy to 0:/gm9/out/`
|
||||
1. You should now have `essentials.exefs` in `/gm9/out/`
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## Boot-related issues on modded devices
|
||||
## Boot issues on devices with custom firmware
|
||||
|
||||
The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
|
||||
{: .notice--info}
|
||||
|
||||
### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
|
||||
### Power/notification light indicators
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>My device powers off when I try to turn it on, and/or the notification LED shows a color on boot</u></summary>
|
||||
|
||||
There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
|
||||
|
||||
|
|
@ -332,11 +476,15 @@ If the notification LED flashes:
|
|||
You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
|
||||
|
||||
If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### My device gets stuck on a black screen, with a static blue light
|
||||
{% capture compat %}
|
||||
<summary><u>My device gets stuck on a black screen with blue power light staying on</u></summary>
|
||||
|
||||
The steps below can be attempted in any order, but are listed from least to most time-consuming.
|
||||
|
||||
1. Power off your device, remove the SD card, re-insert it, then power on your device.
|
||||
1. Power off your device, eject the game cartridge if inserted, power on your device, then wait up to ten minutes. If your device boots within ten minutes, the issue has been fixed and is unlikely to reoccur
|
||||
1. Rename the `Nintendo 3DS` folder on your SD card to `Nintendo 3DS_BACKUP`, then attempt to boot. If your device successfully boots, there is some issue within your `Nintendo 3DS` folder. Try clearing HOME Menu extdata:
|
||||
+ Navigate to `/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/`
|
||||
|
|
@ -354,35 +502,48 @@ The steps below can be attempted in any order, but are listed from least to most
|
|||
+ If you were successful, the device will boot to an "update your system" screen
|
||||
1. Follow the [CTRTransfer](ctrtransfer) guide
|
||||
1. For further support, ask for help at [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### My device boots to an error screen
|
||||
### Error message on boot
|
||||
|
||||
#### "An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"</u></summary>
|
||||
|
||||
Your Luma3DS version is outdated. Download the latest release of [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### "An error has occurred. Hold down the POWER button to turn off the power..."
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..."</u></summary>
|
||||
|
||||
ARM11 exception handlers are disabled, or custom firmware is not installed. Try enabling ARM11 exception handlers:
|
||||
+ Power off your device
|
||||
+ Hold (Select)
|
||||
+ Power on your device, while still holding (Select)
|
||||
+ If the "Disable ARM11 exception handlers" box is checked, uncheck it
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Some other error
|
||||
|
||||
Please take a photo of the error and join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
|
||||
### Blue "Bootrom Error" screen
|
||||
{% capture compat %}
|
||||
<summary><u>Blue "BOOTROM ERROR" screen</u></summary>
|
||||
|
||||
Your device is likely hard-bricked. You will need to buy an ntrboot flashcart to reinstall boot9strap in order to attempt to fix your device. This may also indicate a hardware issue that cannot be fixed. In any case, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
+ It is also possible that someone has set a boot-time splash screen that just looks like a brick. Try leaving your device powered on, waiting on the blue screen, for five minutes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary><u>Some other error</u></summary>
|
||||
|
||||
## Functionality-related issues on modded devices
|
||||
Please take a photo of the error and join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### DSi / DS functionality is broken or has been replaced with Flipnote Studio
|
||||
## Software issues on devices with custom firmware
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DSi / DS functionality is broken or has been replaced with Flipnote Studio</u></summary>
|
||||
|
||||
1. Download the latest release of [TWLFix-CFW](https://github.com/MechanicalDragon0687/TWLFix-CFW/releases/latest) (the `.3dsx` file)
|
||||
1. Power off ye device
|
||||
|
|
@ -396,20 +557,29 @@ Your device is likely hard-bricked. You will need to buy an ntrboot flashcart to
|
|||
1. Perform a System Update by going to System Settings, then "Other Settings", then going all the way to the right and using "System Update"
|
||||
+ The update will see that the essential TWL titles have been uninstalled, and will redownload and reinstall them
|
||||
1. Once the update is complete, tap "OK" to reboot the device
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### GBA Virtual Console and/or Safe Mode functionality is broken
|
||||
{% capture compat %}
|
||||
<summary><u>GBA Virtual Console and/or Safe Mode functionality is broken</u></summary>
|
||||
|
||||
Your device is running Luma3DS/AuReiNand 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your device to a modern custom firmware environment.
|
||||
Your device is running Luma3DS 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your device to a modern custom firmware environment.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Extended memory mode games are broken
|
||||
{% capture compat %}
|
||||
<summary><u>Extended memory mode games (Pokemon Sun/Moon, Smash, etc.) don't work</u></summary>
|
||||
|
||||
This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will need to system format your device to fix this issue.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## Other troubleshooting
|
||||
|
||||
### Clear HOME Menu extdata
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu extdata</u></summary>
|
||||
|
||||
1. Power off ye device
|
||||
1. Insert ye SD card into ye computer
|
||||
|
|
@ -422,8 +592,11 @@ This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will n
|
|||
+ **KOR Region**: `000000A9`
|
||||
+ **TWN Region**: `000000B1`
|
||||
1. Reinsert ye SD card into ye device
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Clear HOME Menu theme data
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu theme data</u></summary>
|
||||
|
||||
1. Power off ye device
|
||||
1. Insert ye SD card into ye computer
|
||||
|
|
@ -433,3 +606,6 @@ This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will n
|
|||
+ **JPN Region**: `000002cc`
|
||||
+ **USA Region**: `000002cd`
|
||||
1. Reinsert ye SD card into ye device
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@ The purpose of this section is to check whether built-in DS mode applications wi
|
|||
+ If your console displays the Japanese version of Flipnote Studio, a black screen, or an error message, the test has failed
|
||||
1. Power off ye device
|
||||
|
||||
If either of these tests has failed, DS mode, DS Download Play, and/or DS Connection Settings may be inaccessible once CFW is uninstalled! You should [fix DS mode](troubleshooting#dsi--ds-functionality-is-broken-or-has-been-replaced-with-flipnote-studio) before continuing.
|
||||
If either of these tests has failed, DS mode, DS Download Play, and/or DS Connection Settings may be inaccessible once CFW is uninstalled! You should [fix DS mode](troubleshooting#software-issues-on-devices-with-custom-firmware) before continuing.
|
||||
{: .notice--warning}
|
||||
|
||||
#### Section III - Safety Test
|
||||
|
|
|
|||
|
|
@ -65,7 +65,7 @@ Para todos los pasos en esta sección, sobreescribe cualquier archivo repetido e
|
|||
1. Tu consola debería haber reiniciado en el menú de configuración de Luma3DS
|
||||
+ 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 get a black screen, [follow this troubleshooting guide](troubleshooting#boot-related-issues-on-modded-devices)
|
||||
+ If you get a black screen, [follow this troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware)
|
||||
1. Presiona (Start) para guardar y reiniciar
|
||||
|
||||
___
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ Esta es una sección complementaria para comprobar si tu consola ya tiene un cus
|
|||
|
||||
Si tu consola tiene un custom firmware basado en arm9loaderhax o boot9strap, tendrás que seguir las instrucciones indicadas para actualizar tu instalación a una más moderna.
|
||||
|
||||
If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#clear-home-menu-extdata), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
|
||||
If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#other-troubleshooting), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
|
||||
{: .notice--info}
|
||||
|
||||
### Instrucciones
|
||||
|
|
|
|||
|
|
@ -14,79 +14,173 @@ title: "Preguntas Frecuentes"
|
|||
|
||||
## Pre-Installation FAQ
|
||||
|
||||
#### **Q:** *I am on the latest system version. Is my device hackable without any external hardware?*
|
||||
**A:** Yes! The latest firmware (11.16.0) has a free method for getting CFW named [Seedminer](seedminer).
|
||||
{% capture compat %}
|
||||
<summary><u>I am on the latest system version. Is my device hackable without any external hardware?</u></summary>
|
||||
|
||||
#### **Q:** *What devices is this guide compatible with?*
|
||||
**A:** The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. Si la versión del sistema se muestra como "0.0.0-0", entonces podrías tener una unidad de desarrollador.
|
||||
Yes! The latest firmware (11.16.0) has a free method for getting CFW named [Seedminer](seedminer).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How risky is hacking my console?*
|
||||
**A:** Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
{% capture compat %}
|
||||
<summary><u>What devices is this guide compatible with?</u></summary>
|
||||
|
||||
#### **Q:** *Can I run awesome homebrew and emulators with this?*
|
||||
**A:** Yes! Esta guía instalará algunas aplicaciones homebrew incluyendo [Universal-Updater](https://github.com/Universal-Team/Universal-Updater/releases/latest), que actúa como una tienda de aplicaciones homebrew.
|
||||
The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. Si la versión del sistema se muestra como "0.0.0-0", entonces podrías tener una unidad de desarrollador.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I use this to play games from other regions?*
|
||||
**A:** Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Algunos juegos podrían necesitar hacer uso de la [función de emulación local (info en inglés)](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) de Luma para poder funcionar apropiadamente en consolas fuera de su región.
|
||||
{% capture compat %}
|
||||
<summary><u>How risky is hacking my console?</u></summary>
|
||||
|
||||
#### **Q:** *Will I lose any features if I install CFW?*
|
||||
**A:** No. Las consolas con custom firmware pueden seguir usando la eShop y usar cartuchos físicos como cualquier otra 3DS.
|
||||
Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I keep my NNID?*
|
||||
**A:** Your NNID (if you have one) will not be affected by this guide. Devices with a region of KOR, CHN, or TWN do not have NNID functionality to begin with and are thus unaffected.
|
||||
{% capture compat %}
|
||||
<summary><u>Can I run awesome homebrew and emulators with this?</u></summary>
|
||||
|
||||
#### **Q:** *Will my 3DS be banned for having CFW?*
|
||||
**A:** There was a ban wave in May 2017 that banned CFW users from online play (eShop access, NNIDs, and Nintendo Accounts were unaffected), seemingly at random. Desde ese entonces, no se ha visto una ola de baneos de tal magnitud. Dicho esto, no sabemos lo que Nintendo tenga preparado para nosotros en el futuro. En este momento, no creemos que los baneos sean algo de lo que tengas que preocuparte.
|
||||
Yes! Esta guía instalará algunas aplicaciones homebrew incluyendo [Universal-Updater](https://github.com/Universal-Team/Universal-Updater/releases/latest), que actúa como una tienda de aplicaciones homebrew.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I do this without a computer (e.g. an Android phone)?*
|
||||
**A:** All you need is the ability to put files on a compatible SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Can I use this to play games from other regions?</u></summary>
|
||||
|
||||
#### **Q:** *What size SD card can I use?*
|
||||
**A:** You will need at least 1.5GB of free SD card space to follow this guide in its entirety. Si bien la 3DS es oficialmente compatible con tarjetas SD de hasta 32 GB, se pueden usar tarjetas SD más grandes, siempre y cuando sean reformateadas manualmente en formato FAT-32. Se recomienda NO usar tarjetas SD de tamaño mayor a 128GB debido a problemas conocidos con gráficos en juegos de GBA y temas personalizados.
|
||||
Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Algunos juegos podrían necesitar hacer uso de la [función de emulación local (info en inglés)](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) de Luma para poder funcionar apropiadamente en consolas fuera de su región.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *I heard about this thing I have to pay for (Gateway, Sky3DS, ntrboot, R4, etc). Is that something I need?*
|
||||
**A:** No. El Custom Firmware se puede instalar de manera gratuita, en la versión del sistema más reciente y sin usar ningún hardware adicional. De hecho, los flashcarts de 3DS como Gateway y Sky3DS se desaconsejan debido a que son obsoletos y acarrean posibles riesgos de baneo o brickeo de la consola.
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose any features if I install CFW?</u></summary>
|
||||
|
||||
#### **Q:** *What's the difference between custom firmware and homebrew access?*
|
||||
**A:** Historically, the 3DS used to have userland homebrew access through older exploits like ninjhax. The level of system access granted with userland allowed you to run basic homebrew and emulators but did not allow you to (easily) modify games or dump cartridges. También era muy inestable, a menudo sucediendo que el homebrew se crasheaba y requería apagar y encender la consola. El Custom firmware otorga un nivel mucho mayor de acceso al sistema, al mismo tiempo que es más estable que lo que permite el homebrew de usuario.
|
||||
No. Las consolas con custom firmware pueden seguir usando la eShop y usar cartuchos físicos como cualquier otra 3DS.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I keep my NNID?</u></summary>
|
||||
|
||||
Your NNID (if you have one) will not be affected by this guide. Devices with a region of KOR, CHN, or TWN do not have NNID functionality to begin with and are thus unaffected.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will my 3DS be banned for having CFW?</u></summary>
|
||||
|
||||
There was a ban wave in May 2017 that banned CFW users from online play (eShop access, NNIDs, and Nintendo Accounts were unaffected), seemingly at random. Desde ese entonces, no se ha visto una ola de baneos de tal magnitud. Dicho esto, no sabemos lo que Nintendo tenga preparado para nosotros en el futuro. En este momento, no creemos que los baneos sean algo de lo que tengas que preocuparte.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I do this without a computer (e.g. an Android phone)?</u></summary>
|
||||
|
||||
Yes! All you need is the ability to put files on a compatible SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What size SD card can I use?</u></summary>
|
||||
|
||||
You will need at least 1.5GB of free SD card space to follow this guide in its entirety. Si bien la 3DS es oficialmente compatible con tarjetas SD de hasta 32 GB, se pueden usar tarjetas SD más grandes, siempre y cuando sean reformateadas manualmente en formato FAT-32. Se recomienda NO usar tarjetas SD de tamaño mayor a 128GB debido a problemas conocidos con gráficos en juegos de GBA y temas personalizados.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>I heard about this thing I have to pay for (Gateway, Sky3DS, ntrboot, R4, etc). Is that something I need?</u></summary>
|
||||
|
||||
No. El Custom Firmware se puede instalar de manera gratuita, en la versión del sistema más reciente y sin usar ningún hardware adicional. De hecho, los flashcarts de 3DS como Gateway y Sky3DS se desaconsejan debido a que son obsoletos y acarrean posibles riesgos de baneo o brickeo de la consola.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What's the difference between custom firmware and homebrew?</u></summary>
|
||||
|
||||
Historically, the 3DS used to have userland homebrew access through older exploits like ninjhax. The level of system access granted with userland allowed you to run basic homebrew and emulators but did not allow you to (easily) modify games or dump cartridges. También era muy inestable, a menudo sucediendo que el homebrew se crasheaba y requería apagar y encender la consola. El Custom firmware otorga un nivel mucho mayor de acceso al sistema, al mismo tiempo que es más estable que lo que permite el homebrew de usuario.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Post-Installation FAQ
|
||||
|
||||
#### **Q:** *Is it safe to update my 3DS to the latest version with CFW?*
|
||||
**A:** If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. Ha habido actualizaciones en el pasado que han causado que Luma3DS muestre un error al iniciar, por lo que es buena idea esperar un par de horas para asegurarse de que la última actualización no haga que la consola no se pueda utilizar temporalmente hasta que Luma3DS sea actualizado. Las actualizaciones del sistema se pueden realizar de la misma manera que en una 3DS normal: a través de Configuración de la consola, el Modo Seguro, o el aviso de actualización que aparece cuando esta se descarga automáticamente.
|
||||
{% capture compat %}
|
||||
<summary><u>Is it safe to update my 3DS to the latest version with CFW?</u></summary>
|
||||
|
||||
#### **Q:** *How do I upgrade my SD card?*
|
||||
**A:** Copy and paste your SD card contents to a new SD card formatted as FAT32. Para tarjetas de 128GB se recomienda un tamaño de asignación de 65536 bytes. Las tarjetas SD de tamaño mayor a 128GB no se recomiendan debido a problemas conocidos con gráficos en juegos de GBA y temas personalizados.
|
||||
If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. Ha habido actualizaciones en el pasado que han causado que Luma3DS muestre un error al iniciar, por lo que es buena idea esperar un par de horas para asegurarse de que la última actualización no haga que la consola no se pueda utilizar temporalmente hasta que Luma3DS sea actualizado. Las actualizaciones del sistema se pueden realizar de la misma manera que en una 3DS normal: a través de Configuración de la consola, el Modo Seguro, o el aviso de actualización que aparece cuando esta se descarga automáticamente.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I system transfer with CFW?*
|
||||
**A:** Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets for illegitimate titles (homebrew) will not transfer, but the titles can be made to reappear with [faketik](https://github.com/ihaveamac/faketik/releases/latest). Asegúrate de no realizar una transferencia inalámbrica, ya que esto también eliminará el software ilegítimo en sí. El CFW permanecerá en ambas consolas.
|
||||
{% capture compat %}
|
||||
<summary><u>How do I upgrade my SD card?</u></summary>
|
||||
|
||||
#### **Q:** *How do I change the system language of a Japanese 3DS?*
|
||||
**A:** The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Ten en cuenta que es muy probable que esto corrompa la Nintendo eShop en tu consola, lo que significa que no podrás actualizar tus juegos, ya sea los que son de región japonesa o los que no.
|
||||
Copy and paste your SD card contents to a new SD card formatted as FAT32. Para tarjetas de 128GB se recomienda un tamaño de asignación de 65536 bytes. Las tarjetas SD de tamaño mayor a 128GB no se recomiendan debido a problemas conocidos con gráficos en juegos de GBA y temas personalizados.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How do I update homebrew applications?*
|
||||
**A:** It depends on the format of the homebrew application. En general:
|
||||
{% capture compat %}
|
||||
<summary><u>Can I system transfer with CFW?</u></summary>
|
||||
|
||||
Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets for illegitimate titles (homebrew) will not transfer, but the titles can be made to reappear with [faketik](https://github.com/ihaveamac/faketik/releases/latest). Asegúrate de no realizar una transferencia inalámbrica, ya que esto también eliminará el software ilegítimo en sí. El CFW permanecerá en ambas consolas.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I change the system language of a Japanese 3DS?</u></summary>
|
||||
|
||||
The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Ten en cuenta que es muy probable que esto corrompa la Nintendo eShop en tu consola, lo que significa que no podrás actualizar tus juegos, ya sea los que son de región japonesa o los que no.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I update homebrew applications?</u></summary>
|
||||
|
||||
It depends on the format of the homebrew application. En general:
|
||||
|
||||
* El Homebrew en **formato CIA** se puede actualizar instalando el nuevo CIA, que usualmente sobrescribirá el antiguo. Si la aplicación antigua no es sobreescrita, puedes borrarla desde Gestión de Datos como harías con cualquier otro título de 3DS.
|
||||
* El Homebrew en **formato 3DSX** puede ser actualizado reemplazando el archivo 3DSX en `/3ds/` con la nueva versión. Si la aplicación homebrew incluye recursos adicionales, puede que necesites colocarlos en otro lugar. Ante la duda, consulta la documentación de la aplicación.
|
||||
* Para actualizar Luma3DS, consulta [esta página](restoring-updating-cfw). Para actualizar GodMode9, lee [esta página](godmode9-usage#updating-godmode9).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How do I update games from outside of my 3DS region?*
|
||||
**A:** You will need to [dump the updates](dumping-titles-and-game-cartridges) from a 3DS that has the updates installed. La Nintendo eShop sólo contiene actualizaciones para la región de la consola (una consola japonesa sólo tendrá actualizaciones para juegos japoneses).
|
||||
{% capture compat %}
|
||||
<summary><u>How do I update my games?</u></summary>
|
||||
|
||||
#### **Q:** *Help! Something bad happened and now I cannot boot...*
|
||||
**A:** Please look at the [troubleshooting guide](troubleshooting). **Se recomienda NO desinstalar CFW cuando la consola no enciende, ya que es muy probable que termine con un brickeo**.
|
||||
You can continue to download game updates from the Nintendo eShop, even after the 2023 shutdown.
|
||||
|
||||
If the game is not from the same region as the console, you will need to [dump the updates](dumping-titles-and-game-cartridges) from a 3DS that has the updates installed. La Nintendo eShop sólo contiene actualizaciones para la región de la consola (una consola japonesa sólo tendrá actualizaciones para juegos japoneses).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Help! Something bad happened and my 3DS won't boot to HOME Menu...</u></summary>
|
||||
|
||||
Please look at the [troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware). **Se recomienda NO desinstalar CFW cuando la consola no enciende, ya que es muy probable que termine con un brickeo**.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## menuhax / A9LH / Gateway FAQ
|
||||
|
||||
#### **Q:** *I modded my device x years ago. What should I do?*
|
||||
**A:** It is recommended that you upgrade your setup to a modern, boot9strap-based one. Sigue la guía de [Comprobación de CFW](checking-for-cfw) para ver cómo actualizar tu setup.
|
||||
{% capture compat %}
|
||||
<summary><u>I modded my device (x) years ago, so it already has some sort of homebrew. What should I do?</u></summary>
|
||||
|
||||
#### **Q:** *My setup works for me. Why should I upgrade it?*
|
||||
**A:** The vast majority of modern homebrew (such as Checkpoint and BootNTR Selector) have only been tested on modern, boot9strap-based setups and may not work entirely (or at all) on older setups based on menuhax, A9LH, or Gateway. Además, dependiendo del setup, es posible que no puedas actualizar con seguridad a la última versión del sistema. Modern, boot9strap-based setups allow for a greater level of system access than previous hacks, including the ability to dump your console's bootrom.
|
||||
It is recommended that you upgrade your setup to a modern, boot9strap-based one. Sigue la guía de [Comprobación de CFW](checking-for-cfw) para ver cómo actualizar tu setup.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Will I lose anything if I upgrade my setup?*
|
||||
**A:** Your old setup (including your EmuNAND, if you have one) can usually be directly migrated to boot9strap with no data loss. Si tienes datos que son especialmente importantes, sería una buena idea hacer una copia de seguridad de tus datos de guardado antes de actualizar tu setup, por medio de una herramienta como [JKSM](https://github. om/J-D-K/JKSM/releases/tag/12%2F20%2F2018).
|
||||
{% capture compat %}
|
||||
<summary><u>My setup works for me. Why should I upgrade it?</u></summary>
|
||||
|
||||
The vast majority of modern homebrew (such as Checkpoint and BootNTR Selector) have only been tested on modern, boot9strap-based setups and may not work entirely (or at all) on older setups based on menuhax, A9LH, or Gateway. Además, dependiendo del setup, es posible que no puedas actualizar con seguridad a la última versión del sistema. Modern, boot9strap-based setups allow for a greater level of system access than previous hacks, including the ability to dump your console's bootrom.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose anything if I upgrade my setup?</u></summary>
|
||||
|
||||
Your old setup (including your EmuNAND, if you have one) can usually be directly migrated to boot9strap with no data loss. Si tienes datos que son especialmente importantes, sería una buena idea hacer una copia de seguridad de tus datos de guardado antes de actualizar tu setup, por medio de una herramienta como [JKSM](https://github. om/J-D-K/JKSM/releases/tag/12%2F20%2F2018).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I move saves from an existing Gateway setup to a more modern setup?</u></summary>
|
||||
|
||||
#### **Q:** *How do I move saves from an existing Gateway setup to a more modern setup?*
|
||||
**R:** Echa un vistazo a [este hilo](https://gbatemp.net/threads/425743/) (*en inglés*).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@ In this section, you will update your system to the latest version, which is saf
|
|||
+ Actualizar la consola teniendo B9S y Luma (lo que acabas de instalar) es seguro
|
||||
+ El actualizador podría mostrar un mensaje diciendo "La consola ya está actualizada" en lugar de actualizar. Esto es normal si tu consola ya está actualizada; continúa con la siguiente sección
|
||||
+ If this gives you an error, set both your DNS settings and Proxy settings to "auto"
|
||||
+ If this still gives you an error, [follow this troubleshooting guide](troubleshooting#unable-to-update-device)
|
||||
+ If this still gives you an error, [follow this troubleshooting guide](troubleshooting#finalizing-setup)
|
||||
|
||||
#### Sección III - Homebrew Launcher
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
|||
1. Entra a Configuración de la consola
|
||||
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#dsiware-management-menu-crashes-without-showing-bb3-multihax-menu)
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#installing-boot9strap-fredtool)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Dump DSiWare"
|
||||
+ Your device will automatically reboot
|
||||
1. Apaga tu consola
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
|||
1. Entra a Configuración de la consola
|
||||
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#dsiware-management-menu-crashes-without-showing-bb3-multihax-menu)
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#bannerbomb3)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Install unSAFE_MODE"
|
||||
+ Tu consola se apagará automáticamente
|
||||
|
||||
|
|
|
|||
|
|
@ -135,7 +135,7 @@ Para identificar el Title ID de un archivo `<TitleID>.gbavc.sav`, tu podrías ob
|
|||
1. Selecciona "Backup Options"
|
||||
1. Selecciona "SysNAND Backup"
|
||||
1. Presiona (A) para confirmar
|
||||
+ Este proceso tomará algún tiempo
|
||||
+ Este proceso tomará un tiempo
|
||||
+ Si te aparece un error, asegúrate de que tienes al menos 1.3GB de espacio libre en tu tarjeta SD
|
||||
1. Presiona (A) para continuar
|
||||
1. Presiona (B) para volver al menú principal
|
||||
|
|
@ -165,10 +165,9 @@ Para identificar el Title ID de un archivo `<TitleID>.gbavc.sav`, tu podrías ob
|
|||
1. Inserta tu tarjeta SD en tu computadora
|
||||
1. Copia todos tus archivos de regreso a tu tarjeta SD
|
||||
+ Asegúrate de reemplazar el archivo `boot.firm` en tu tarjeta SD con el de tu respaldo
|
||||
1. Vuelve a insertar tu tarjeta SD en tu consola
|
||||
1. Reinserta tu tarjeta SD en tu consola
|
||||
1. Presiona (A) para montar la SD
|
||||
1. Presiona (Start) para reiniciar
|
||||
1. If you get a black screen, [follow this troubleshooting guide](troubleshooting#ts_sys_down)
|
||||
|
||||
___
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ In this section, you will get the necessary details from your 3DS that are requi
|
|||
+ If you don't have a `Nintendo 3DS` folder, put your SD card into your 3DS and power it on so that the folder can be created
|
||||
1. Copy the name of the 32-letter folder you see directly inside Nintendo 3DS
|
||||
+ This 32-letter name is system-specific and will be different for each console
|
||||
+ If you see multiple 32-letter folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
|
||||
+ If you see multiple 32-letter folders, follow [these instructions](troubleshooting#seedminer)
|
||||
+ You can ignore the `private` folder if you have it
|
||||
|
||||
![]({{ "/images/screenshots/seedminer/id0-example.png" | absolute_url }})
|
||||
|
|
|
|||
|
|
@ -2,37 +2,69 @@
|
|||
title: "Resolución de Problemas"
|
||||
---
|
||||
|
||||
{% include toc title="Tabla de Contenidos"%}
|
||||
|
||||
Esta página ofrece consejos de solución de problemas para problemas comunes que puedan surgir. Si no logras resolver tu problema con esta página, por favor únete al [Discord de Nintendo Homebrew](https://discord. g/MWxPgEp) (en inglés) y describe tu problema, incluyendo lo que ya has intentado hacer previamente.
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary>Table of Contents</summary>
|
||||
|
||||
Used on multiple pages:
|
||||
* [SafeB9SInstaller](#issues-with-safeb9sinstaller)
|
||||
|
||||
Guide pages:
|
||||
* [Seedminer](#seedminer)
|
||||
* [BannerBomb3](#bannerbomb3)
|
||||
* [Installing boot9strap (USM)](#installing-boot9strap-usm)
|
||||
* [Installing boot9strap (Fredtool)](#installing-boot9strap-fredtool)
|
||||
* [Homebrew Launcher (PicHaxx)](#homebrew-launcher-pichaxx)
|
||||
* [Installing boot9strap (Soundhax)](#installing-boot9strap-soundhax)
|
||||
* [Installing boot9strap (SSLoth-Browser)](#installing-boot9strap-ssloth-browser)
|
||||
|
||||
* [Finalizing Setup](#finalizing-setup)
|
||||
|
||||
Issues after installation:
|
||||
* [Boot issues](#boot-issues-on-devices-with-custom-firmware)
|
||||
* [Software issues](#software-issues-on-devices-with-custom-firmware)
|
||||
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
{: .notice--info}
|
||||
|
||||
## Problemas con SafeB9SInstaller
|
||||
|
||||
### SigHaxed FIRM was not installed! Revisa la pantalla inferior para más información.
|
||||
|
||||
#### SigHaxed FIRM - File not found
|
||||
{% capture compat %}
|
||||
<summary><u>SigHaxed FIRM - File not found</u></summary>
|
||||
|
||||
Los archivos `boot9strap.firm` y `boot9strap.firm.sha` no están en la carpeta `boot9strap`, o la carpeta `boot9strap` tiene un nombre equivocado. Download the latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip), and place `boot9strap.firm` and `boot9strap.firm.sha` in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### SigHaxed FIRM - invalid FIRM
|
||||
{% capture compat %}
|
||||
<summary><u>SigHaxed FIRM - invalid FIRM</u></summary>
|
||||
|
||||
Hay un problema con los archivos `boot9strap.firm` y `boot9strap.firm.sha`. Re-download the latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip), and place `boot9strap.firm` and `boot9strap.firm.sha` in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Secret Sector - File not found
|
||||
{% capture compat %}
|
||||
<summary><u>Secret Sector - File not found</u></summary>
|
||||
|
||||
You are missing `secret_sector.bin` from the `boot9strap` folder, or the `boot9strap` folder is misnamed. Download [secret_sector.bin](magnet:?xt=urn:btih:15a3c97acf17d67af98ae8657cc66820cc58f655&dn=secret_sector.bin&tr=udp%3a%2f%2ftracker.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.lelux.fi%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.loadbt.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.moeking.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.monitorit4.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.ololosh.space%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.pomf.se%3a80%2fannounce&tr=udp%3a%2f%2ftracker.srv00.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.theoks.net%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.tiny-vps.com%3a6969%2fannounce&tr=udp%3a%2f%2fopen.tracker.cl%3a1337%2fannounce&tr=udp%3a%2f%2ftracker.zerobytes.xyz%3a1337%2fannounce&tr=udp%3a%2f%2ftracker1.bt.moack.co.kr%3a80%2fannounce&tr=udp%3a%2f%2fvibe.sleepyinternetfun.xyz%3a1738%2fannounce&tr=udp%3a%2f%2fwww.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a6969%2fannounce&tr=udp%3a%2f%2f9.rarbg.com%3a2810%2fannounce&tr=udp%3a%2f%2ftracker.opentrackr.org%3a1337%2fannounce&tr=udp%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fopenbittorrent.com%3a80%2fannounce) using a torrent client, and place it in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Something else
|
||||
{% capture compat %}
|
||||
<summary><u>Something else</u></summary>
|
||||
|
||||
Únete al [Discord de Nintendo Homebrew](https://discord.gg/MWxPgEp) (en inglés) para obtener ayuda, y describe el mensaje que veas.
|
||||
|
||||
---
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Seedminer
|
||||
|
||||
### Multiple long folder names in Nintendo 3DS folder
|
||||
{% capture compat %}
|
||||
<summary><u>Multiple long folder names in Nintendo 3DS folder</u></summary>
|
||||
|
||||
![]({{ "/images/screenshots/multiple-id0.png" | absolute_url }})
|
||||
{: .notice--info}
|
||||
|
|
@ -49,98 +81,285 @@ This occurs when you use your SD card in multiple 3DS devices and is intended to
|
|||
+ This is your true ID0 that you will use in [Section II of Seedminer](seedminer#section-ii---seedminer)
|
||||
1. Delete the `Nintendo 3DS` folder
|
||||
1. Rename the `BACKUP_Nintendo 3DS` folder to `Nintendo 3DS`
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Bruteforce Movable skips to step 4
|
||||
{% capture compat %}
|
||||
<summary><u>Bruteforce Movable skips to step 4</u></summary>
|
||||
|
||||
El sitio web ya ha minado tu `movable.sed` usando tu código de amigo y el ID0. Puedes utilizar el `movable.sed` que te proporciona.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Important! You have been locked out of the automated part1 dumper system...
|
||||
{% capture compat %}
|
||||
<summary><u>Important! You have been locked out of the automated part1 dumper system...</u></summary>
|
||||
|
||||
Tu código de amigo fue bloqueado del bot de código de amigo porque tu consola no pudo agregar al bot como amigo. Asegúrate de que tu consola esté correctamente conectada a Internet, luego únete al [Discord de Nintendo Homebrew](https://discord.gg/MWxPgEp) y pide que se te desbloquee.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### We were unable to successfully complete your bruteforce request. :`(
|
||||
{% capture compat %}
|
||||
<summary><u>We were unable to successfully complete your bruteforce request. :`(</u></summary>
|
||||
|
||||
El sitio web ha determinado que tu `movable.sed` no puede ser minado. Asegúrate de haber escrito correctamente el ID0 en el sitio web. Si tu ID0 era correcto, entonces no podrás usar Seedminer y tendrás que utilizar un método alternativo que requerirá juegos o hardware adicionales.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
## BannerBomb3
|
||||
|
||||
## Homebrew Launcher (PicHaxx)
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management menu crashes without showing BB3 multihax menu</u></summary>
|
||||
Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. If it is, then re-create it with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen).
|
||||
|
||||
### "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
Los archivos `00000001.sav` y/o `otherapp.bin` pueden estar fuera de lugar. Asegúrate de que el archivo `00000001.sav` está en `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`, y que el archivo `otherapp.bin` está en la raíz de la tarjeta SD.
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow [an alternate branch of Seedminer](homebrew-launcher-(pichaxx)). If Safe Mode doesn't work or you need assistance with this matter, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
If your files are in the correct locations, re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx), then place it in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`. Asegúrate de que el archivo se llama exactamente `00000001.sav` y que utilizaste el `movable.sed` correspondiente a tu consola para crearlo. Re-download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. No añadas manualmente la extensión `.bin` al archivo si ves que no la tiene.
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management menu does not crash</u></summary>
|
||||
|
||||
### "An exception occurred" or Errdisp when opening Picross
|
||||
`F00D43D5.bin` is missing from `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. Asegúrate de que `Nintendo DSiWare` está correctamente escrito y espaciado. Las mayúsculas/minúsculas no importan.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
Tu consola ya tiene Custom Firmware instalado. Deberías ir a [Comprobación de CFW](checking-for-cfw) antes de continuar.
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management shows a question mark</u></summary>
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
Puede haber un problema con el archivo `F00D43D5.bin` (puede estar corrupto o preparado para otra consola 3DS). Re-create your `F00D43D5.bin` file with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen), ensuring that you use the `movable.sed` file for your console.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
Hay un problema con el archivo `otherapp.bin`. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. No añadas manualmente la extensión `.bin` al archivo si ves que no la tiene.
|
||||
## Instalar boot9strap (USM)
|
||||
|
||||
### Game starts normally
|
||||
{% capture compat %}
|
||||
<summary><u>Safe Mode system update succeeds instead of giving error 003-1099</u></summary>
|
||||
|
||||
El archivo `00000001.sav` modificado puede estar fuera de lugar, o puedes haber usado el `movable.sed` incorrecto al crearlo. Re-generate your `movable.sed` from [Bruteforce Movable](https://seedminer.hacks.guide), then re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx) and place the resulting file (`00000001.sav`) in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`.
|
||||
unSAFE_MODE is not installed. [Follow the instructions](installing-boot9strap-(usm)] to install it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary><u>Red screen after selecting "Detailed Setup"</u></summary>
|
||||
|
||||
## Instalar boot9strap (Soundhax)
|
||||
The file `usm.bin` is missing or misplaced. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/download/v1.3/usm.bin) and place `usm.bin` on the root of your SD card. No añadas manualmente la extensión `.bin` al archivo si ves que no la tiene.
|
||||
|
||||
### Red/purple/pink and white screen after running Soundhax
|
||||
There is also a possibility that the console isn't reading your SD card. Make sure it is inserted and formatted correctly.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
Si tu consola no está en esas versiones y ocurre esto, indica que posiblemente ya tengas custom firmware instalado. Deberías ir a [Comprobación de CFW](checking-for-cfw) antes de continuar.
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
|
||||
Hay un problema con el archivo `otherapp.bin` (falta, está mal colocado o está corrupto). Descarga la última versión de [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) y coloca el archivo en la raíz de tu tarjeta SD.
|
||||
|
||||
### "Could not play"
|
||||
|
||||
Tienes el archivo de Soundhax incorrecto para tu consola y región, o tu consola es incompatible con Soundhax. En este último caso, se recomienda actualizar la consola a la última versión y seguir [Seedminer](seedminer).
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
Falta el archivo `SafeB9SInstaller.bin` o está fuera de lugar. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. No añadas manualmente la extensión `.bin` al archivo si ves que no la tiene.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to mount the SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
## Instalar boot9strap (Fredtool)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Error on Fredtool Injector page</u></summary>
|
||||
|
||||
Asegúrate de que tu archivo `movable.sed` y la copia de seguridad de DSiWare provienen de la misma consola. El error aparece cuando los archivos no coinciden.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to select "Haxxxxxxxxx!" because the BB3 multihax menu appears</u></summary>
|
||||
|
||||
You forgot to delete `F00D43D5.bin` from the SD card. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card and delete the `F00D43D5.bin` file.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"Haxxxxxxxxx!" does not appear</u></summary>
|
||||
|
||||
Hay un problema con el archivo `42383821.bin` (es incorrecto, no está presente, está mal colocado o está corrupto). Re-create your files with the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website and ensure that you place the `42383821.bin` file from `output.zip` -> `hax` in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DS Connection Settings launches normally</u></summary>
|
||||
|
||||
`Haxxxxxxxxx!` no fue copiado de la tarjeta SD a la memoria de la consola.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Black screen when launching DS Connection Settings</u></summary>
|
||||
|
||||
El menú de Conexiones de Nintendo DS no funciona, y necesitarás acceso al Homebrew Launcher para solucionar este problema. Únete al [Discord de Nintendo Homebrew](https://discord.gg/MWxPgEp) para obtener ayuda.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>SD card is grayed out in Flipnote</u></summary>
|
||||
|
||||
Flipnote puede tomar mucho tiempo en construir un índice de la tarjeta SD si esta es muy grande. Espera unos minutos.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Lenny face does not appear in SD card section</u></summary>
|
||||
|
||||
No copiaste la carpeta `private` del archivo `.zip` de Frogminer_save a la raíz de la tarjeta SD.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Flipnote freezes</u></summary>
|
||||
|
||||
Es posible que hayas tocado la pantalla táctil dentro del Flipnote modificado. Vuelve a entrar al menú de Conexiones de Nintendo DS e intenta de nuevo, asegurándote de no tocar la pantalla táctil por accidente.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Green screen after pasting</u></summary>
|
||||
|
||||
Falta el archivo `boot.nds` o está fuera de lugar. Descarga la última versión de [b9stool](https://github.com/zoogie/b9sTool/releases/latest) y coloca el archivo `boot.nds` en la raíz de la tarjeta SD, sobreescribiendo el existente.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>White screen after pasting</u></summary>
|
||||
Hay un problema con el archivo `boot.nds`. Vuelve a descargar la última versión de [b9stool](https://github.com/zoogie/b9sTool/releases/latest) y coloca el archivo `boot.nds` en la raíz de la tarjeta SD, sobreescribiendo el existente.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to open Luma3DS configuration menu after running B9STool</u></summary>
|
||||
|
||||
Es posible que boot9strap no se haya instalado correctamente. Sigue la sección B de [esta página](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Homebrew Launcher (PicHaxx)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
|
||||
|
||||
Los archivos `00000001.sav` y/o `otherapp.bin` pueden estar fuera de lugar. Asegúrate de que el archivo `00000001.sav` está en `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`, y que el archivo `otherapp.bin` está en la raíz de la tarjeta SD.
|
||||
|
||||
If your files are in the correct locations, re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx), then place it in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`. Asegúrate de que el archivo se llama exactamente `00000001.sav` y que utilizaste el `movable.sed` correspondiente a tu consola para crearlo. Re-download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. No añadas manualmente la extensión `.bin` al archivo si ves que no la tiene.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" or Errdisp when opening Picross</u></summary>
|
||||
|
||||
Tu consola ya tiene Custom Firmware instalado. Deberías ir a [Comprobación de CFW](checking-for-cfw) antes de continuar.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
Hay un problema con el archivo `otherapp.bin`. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. No añadas manualmente la extensión `.bin` al archivo si ves que no la tiene.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Game starts normally</u></summary>
|
||||
|
||||
El archivo `00000001.sav` modificado puede estar fuera de lugar, o puedes haber usado el `movable.sed` incorrecto al crearlo. Re-generate your `movable.sed` from [Bruteforce Movable](https://seedminer.hacks.guide), then re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx) and place the resulting file (`00000001.sav`) in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Instalar boot9strap (Soundhax)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Soundhax</u></summary>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
Si tu consola no está en esas versiones y ocurre esto, indica que posiblemente ya tengas custom firmware instalado. Deberías ir a [Comprobación de CFW](checking-for-cfw) antes de continuar.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
Hay un problema con el archivo `otherapp.bin` (falta, está mal colocado o está corrupto). Descarga la última versión de [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) y coloca el archivo en la raíz de tu tarjeta SD.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"Could not play"</u></summary>
|
||||
|
||||
Tienes el archivo de Soundhax incorrecto para tu consola y región, o tu consola es incompatible con Soundhax. En este último caso, se recomienda actualizar la consola a la última versión y seguir [Seedminer](seedminer).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
Falta el archivo `SafeB9SInstaller.bin` o está fuera de lugar. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. No añadas manualmente la extensión `.bin` al archivo si ves que no la tiene.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Installing boot9strap (SSLoth-Browser)
|
||||
|
||||
### Red/purple/pink and white screen after running browserhax
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Browserhax</u></summary>
|
||||
|
||||
This likely indicates that you already have custom firmware. Deberías ir a [Comprobación de CFW](checking-for-cfw) antes de continuar.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
|
||||
|
||||
The file `arm11code.bin` is missing or misplaced. Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place `otherapp.bin` on the root of your SD card and rename it to `arm11code.bin`. No añadas manualmente la extensión `.bin` al archivo si ves que no la tiene.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `arm11code.bin` file. Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place `otherapp.bin` on the root of your SD card and rename it to `arm11code.bin`. No añadas manualmente la extensión `.bin` al archivo si ves que no la tiene.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Opening the browserhax QR code or URL crashes
|
||||
{% capture compat %}
|
||||
<summary><u>Opening the browserhax QR code or URL crashes</u></summary>
|
||||
|
||||
Browser based exploits (such as this one) are often unstable and crash frequently, but they can sometimes be fixed by doing the following steps.
|
||||
|
||||
1. Launch the browser, then launch the browser settings
|
||||
1. Scroll to the bottom and Initialize Savedata (it also may be called Clear All Save Data)
|
||||
1. Try the exploit again
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Opening the browser prompts for a system update instead
|
||||
{% capture compat %}
|
||||
<summary><u>System Update prompt when opening browser</u></summary>
|
||||
|
||||
The SSLoth proxy was incorrectly configured. Re-do the SSLoth section on the page.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Error 032-0420 when trying to open the browser
|
||||
{% capture compat %}
|
||||
<summary><u>Error 032-0420 when opening browser</u></summary>
|
||||
|
||||
Follow these steps in order:
|
||||
|
||||
|
|
@ -157,126 +376,47 @@ Follow these steps in order:
|
|||
1. If prompted about a system update, press OK
|
||||
+ This won't actually update the system
|
||||
1. Start again from [Section II](installing-boot9strap-(ssloth-browser).html#section-ii---ssloth)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
Falta el archivo `SafeB9SInstaller.bin` o está fuera de lugar. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. No añadas manualmente la extensión `.bin` al archivo si ves que no la tiene.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Frozen on "Doing agbhax..."
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Frozen on "Doing agbhax..."</u></summary>
|
||||
There may be an issue with your `arm11code.bin` file. Re-download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place it on the root of your SD card, and rename it to `arm11code.bin`. No añadas manualmente la extensión `.bin` al archivo si ves que no la tiene.
|
||||
|
||||
If you have a Taiwanese unit (with a T in the version string, ie. 11.3.0-##T), you will not be able to follow these instructions, and you will need to update your console and follow [Seedminer](seedminer) instead.
|
||||
|
||||
If you have a Mainland Chinese unit (with a C in the version string, ie. 11.3.0-##C), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "PrepareArm9ForTwl returned error c8804631!"
|
||||
{% capture compat %}
|
||||
<summary><u>"PrepareArm9ForTwl returned error c8804631!"</u></summary>
|
||||
|
||||
You will need to follow an alternate method. Únete al [Discord de Nintendo Homebrew](https://discord.gg/MWxPgEp) para obtener ayuda.
|
||||
Únete al [Discord de Nintendo Homebrew](https://discord.gg/MWxPgEp) para obtener ayuda.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to mount the SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## BannerBomb3
|
||||
|
||||
### DSiWare Management menu crashes without showing BB3 multihax menu
|
||||
|
||||
Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. If it is, then re-create it with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen).
|
||||
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow [an alternate branch of Seedminer](homebrew-launcher-(pichaxx)). If Safe Mode doesn't work or you need assistance with this matter, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
|
||||
### DSiWare Management menu does not crash
|
||||
|
||||
`F00D43D5.bin` is missing from `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. Asegúrate de que `Nintendo DSiWare` está correctamente escrito y espaciado. Las mayúsculas/minúsculas no importan.
|
||||
|
||||
### DSiWare Management shows a question mark
|
||||
|
||||
Puede haber un problema con el archivo `F00D43D5.bin` (puede estar corrupto o preparado para otra consola 3DS). Re-create your `F00D43D5.bin` file with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen), ensuring that you use the `movable.sed` file for your console.
|
||||
|
||||
---
|
||||
|
||||
## Instalar boot9strap (USM)
|
||||
|
||||
### Update doesn't fail with error code `003-1099`
|
||||
|
||||
unSAFE_MODE is not installed. Follow the instructions on your page to install unSAFE_MODE again.
|
||||
|
||||
### Red screen when selecting detailed setup
|
||||
|
||||
The file `usm.bin` is missing or misplaced. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/download/v1.3/usm.bin) and place `usm.bin` on the root of your SD card. No añadas manualmente la extensión `.bin` al archivo si ves que no la tiene.
|
||||
|
||||
There is also a possibility that the console isn't reading your SD card. Make sure it is inserted and formatted correctly.
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
|
||||
Falta el archivo `SafeB9SInstaller.bin` o está fuera de lugar. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. No añadas manualmente la extensión `.bin` al archivo si ves que no la tiene.
|
||||
|
||||
### Failed to mount the SD card!
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
|
||||
---
|
||||
|
||||
## Instalar boot9strap (Fredtool)
|
||||
|
||||
### Error on Fredtool Injector page
|
||||
|
||||
Asegúrate de que tu archivo `movable.sed` y la copia de seguridad de DSiWare provienen de la misma consola. El error aparece cuando los archivos no coinciden.
|
||||
|
||||
### Unable to select the "Haxxxxxxxxx!" title because of the BB3 multihax menu
|
||||
|
||||
You forgot to delete `F00D43D5.bin` from the SD card. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card and delete the `F00D43D5.bin` file.
|
||||
|
||||
### "Haxxxxxxxxx!" does not appear
|
||||
|
||||
Hay un problema con el archivo `42383821.bin` (es incorrecto, no está presente, está mal colocado o está corrupto). Re-create your files with the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website and ensure that you place the `42383821.bin` file from `output.zip` -> `hax` in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`.
|
||||
|
||||
### DS Connection Settings launches normally
|
||||
|
||||
`Haxxxxxxxxx!` no fue copiado de la tarjeta SD a la memoria de la consola.
|
||||
|
||||
### Black screen when launching DS Connection Settings
|
||||
|
||||
El menú de Conexiones de Nintendo DS no funciona, y necesitarás acceso al Homebrew Launcher para solucionar este problema. Únete al [Discord de Nintendo Homebrew](https://discord.gg/MWxPgEp) para obtener ayuda.
|
||||
|
||||
### SD card is grayed out
|
||||
|
||||
Flipnote puede tomar mucho tiempo en construir un índice de la tarjeta SD si esta es muy grande. Espera unos minutos.
|
||||
|
||||
### Lenny face does not appear
|
||||
|
||||
No copiaste la carpeta `private` del archivo `.zip` de Frogminer_save a la raíz de la tarjeta SD.
|
||||
|
||||
### Flipnote is frozen
|
||||
|
||||
Es posible que hayas tocado la pantalla táctil dentro del Flipnote modificado. Vuelve a entrar al menú de Conexiones de Nintendo DS e intenta de nuevo, asegurándote de no tocar la pantalla táctil por accidente.
|
||||
|
||||
### Green screen after pasting
|
||||
|
||||
Falta el archivo `boot.nds` o está fuera de lugar. Descarga la última versión de [b9stool](https://github.com/zoogie/b9sTool/releases/latest) y coloca el archivo `boot.nds` en la raíz de la tarjeta SD, sobreescribiendo el existente.
|
||||
|
||||
### White screen after pasting
|
||||
|
||||
Hay un problema con el archivo `boot.nds`. Vuelve a descargar la última versión de [b9stool](https://github.com/zoogie/b9sTool/releases/latest) y coloca el archivo `boot.nds` en la raíz de la tarjeta SD, sobreescribiendo el existente.
|
||||
|
||||
### Unable to open Luma3DS configuration menu after running b9stool
|
||||
|
||||
Es posible que boot9strap no se haya instalado correctamente. Sigue la sección B de [esta página](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md).
|
||||
|
||||
---
|
||||
|
||||
## Finalizar instalación
|
||||
|
||||
### Unable to update device
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to update device</u></summary>
|
||||
|
||||
Los pasos siguientes se pueden intentar en cualquier orden, pero están ordenados por orden de dificultad.
|
||||
|
||||
|
|
@ -289,27 +429,41 @@ Los pasos siguientes se pueden intentar en cualquier orden, pero están ordenado
|
|||
1. Puede que los servidores de Nintendo estén caídos. Intenta más tarde
|
||||
1. Si aún te sigue dando error, [sigue la sección de CTRTransfer](ctrtransfer) y luego intenta actualizar nuevamente
|
||||
1. Para más soporte (en inglés), entra al [Discord de Nintendo Homebrew](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Unable to enter Rosalina due to broken button(s)
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to enter Rosalina menu due to broken Left Shoulder / Down D-Pad / Select button(s)</u></summary>
|
||||
|
||||
Download this [alternate config.ini](https://cdn.discordapp.com/attachments/196635695958196224/982798396265988186/config.ini) and place it in `/luma/`. This will change the Rosalina key combination to (X) + (Y).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An exception occurred" after trying to launch Homebrew Launcher via Download Play
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" after trying to launch Homebrew Launcher from Download Play</u></summary>
|
||||
|
||||
Hay un problema con el archivo `boot.3dsx` (falta, está mal colocado o está corrupto). Download the latest release of [the Homebrew Launcher](https://github.com/devkitPro/3ds-hbmenu/releases/latest) and place `boot.3dsx` on the root of your SD card, replacing any existing file. Asegúrate de extraer el archivo ZIP con cualquier herramienta que no sea WinRAR, ya que se sabe que causa problemas con los archivos relacionados con 3DS.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "Scripts directory not found" in GodMode9
|
||||
{% capture compat %}
|
||||
<summary><u>"Scripts directory not found" in GodMode9</u></summary>
|
||||
|
||||
No copiaste la carpeta `gm9` del archivo `.zip` de GodMode9 a la raíz de la tarjeta SD. Descarga la última versión de [GodMode9](https://github.com/d0k3/GodMode9/releases/latest) y coloca la carpeta `gm9` en la raíz de la tarjeta SD, combinándola con la ya existente.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## Boot-related issues on modded devices
|
||||
## Boot issues on devices with custom firmware
|
||||
|
||||
Los pasos detallados a continuación asumen que tu consola tiene un setup moderno de custom firmware (boot9strap + Luma3DS 8.0 o superior). Si tu consola tiene una configuración antigua (por ejemplo, algo basado en arm9loaderhax o menuhax), deberías actualizar dicha configuración antes de seguir estas instrucciones.
|
||||
{: .notice--info}
|
||||
|
||||
### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
|
||||
### Power/notification light indicators
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>My device powers off when I try to turn it on, and/or the notification LED shows a color on boot</u></summary>
|
||||
|
||||
There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
|
||||
|
||||
|
|
@ -322,11 +476,15 @@ If the notification LED flashes:
|
|||
You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
|
||||
|
||||
Si escuchas un "pop", potencialmente acompañado de la luz de la pantalla parpadeando un segundo, hay un problema en el hardware de tu consola (cable de luz de fondo desconectado, por ejemplo). Es posible que tu consola encienda sosteniéndola en distintas orientaciones.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### My device gets stuck on a black screen, with a static blue light
|
||||
{% capture compat %}
|
||||
<summary><u>My device gets stuck on a black screen with blue power light staying on</u></summary>
|
||||
|
||||
Los pasos siguientes se pueden intentar en cualquier orden, pero están ordenados por cantidad de tiempo que toma realizar.
|
||||
|
||||
1. Power off your device, remove the SD card, re-insert it, then power on your device.
|
||||
1. Apaga tu consola, saca el cartucho si tiene uno puesto, enciende la consola y luego espera hasta diez minutos. Si la consola enciende en los siguientes diez minutos, el problema fue resuelto y es muy improbable que vuelva a ocurrir
|
||||
1. Cambia el nombre de la carpeta `Nintendo 3DS` de tu tarjeta SD a `Nintendo 3DS_BACKUP`, luego intenta encenderla. Si la consola enciende sin problemas, hay un problema con tu carpeta `Nintendo 3DS`. Try clearing HOME Menu extdata:
|
||||
+ Ve a `/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/`
|
||||
|
|
@ -344,35 +502,48 @@ Los pasos siguientes se pueden intentar en cualquier orden, pero están ordenado
|
|||
+ Si lo has hecho correctamente, la consola mostrará una pantalla para "actualizar tu sistema"
|
||||
1. Sigue la guía de [CTRTransfer](ctrtransfer)
|
||||
1. Para más ayuda, puedes pedir ayuda (*en inglés*) en el [Discord de Nintendo Homebrew](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### My device boots to an error screen
|
||||
### Error message on boot
|
||||
|
||||
#### "An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"</u></summary>
|
||||
|
||||
Tu versión de Luma3DS está desactualizada. Descarga la última versión de [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) y coloca `boot.firm` en la raíz de tu tarjeta SD, reemplazando cualquier archivo existente. Asegúrate de extraer el archivo ZIP con cualquier herramienta que no sea WinRAR, ya que se sabe que causa problemas con los archivos relacionados con 3DS.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### "An error has occurred. Hold down the POWER button to turn off the power..."
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..."</u></summary>
|
||||
|
||||
Tienes activada la opción "Disable ARM11 exception handlers", o directamente no tienes custom firmware instalado. Intenta activar las excepciones de ARM11:
|
||||
+ Apaga tu consola
|
||||
+ Mantén presionado (Select)
|
||||
+ Enciende la consola mientras mantienes presionado (Select)
|
||||
+ Si la opción "Disable ARM11 exception handlers" está marcada, desmárcala
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Some other error
|
||||
|
||||
Por favor saca una foto del error y entra al [Discord de Nintendo Homebrew](https://discord.gg/MWxPgEp) y pide ayuda (*en inglés*).
|
||||
|
||||
### Blue "Bootrom Error" screen
|
||||
{% capture compat %}
|
||||
<summary><u>Blue "BOOTROM ERROR" screen</u></summary>
|
||||
|
||||
Tu consola muy probablemente está brickeada a nivel de hardware. Tendrás que conseguir una flashcard compatible con ntrboot y reinstalar boot9strap para intentar reparar tu consola. This may also indicate a hardware issue that cannot be fixed. En este caso, entra al [Discord de Nintendo Homebrew](https://discord.gg/MWxPgEp) para obtener ayuda (*en inglés*).
|
||||
+ También es posible que alguien haya configurado una pantalla de inicio que luce tal y como un brickeo. Prueba a dejar tu consola encendida, esperando en la pantalla azul, durante cinco minutos.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary><u>Some other error</u></summary>
|
||||
|
||||
## Functionality-related issues on modded devices
|
||||
Por favor saca una foto del error y entra al [Discord de Nintendo Homebrew](https://discord.gg/MWxPgEp) y pide ayuda (*en inglés*).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### DSi / DS functionality is broken or has been replaced with Flipnote Studio
|
||||
## Software issues on devices with custom firmware
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DSi / DS functionality is broken or has been replaced with Flipnote Studio</u></summary>
|
||||
|
||||
1. Descarga la última versión de [TWLFix-CFW](https://github.com/MechanicalDragon0687/TWLFix-CFW/releases/latest) *(el archivo `.3dsx`)*
|
||||
1. Apaga tu consola
|
||||
|
|
@ -386,20 +557,29 @@ Tu consola muy probablemente está brickeada a nivel de hardware. Tendrás que c
|
|||
1. Realiza una Actualización de sistema dirigiéndote a la Configuración de la consola, después a "Otras opciones", luego ve al último menú de la derecha y pulsa en "Actualización"
|
||||
+ La actualización verá que los títulos TWL esenciales han sido desinstalados, y los volverá a descargar e instalar
|
||||
1. Una vez que la actualización se haya completado, pulsa "Aceptar" para reiniciar la consola
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### GBA Virtual Console and/or Safe Mode functionality is broken
|
||||
{% capture compat %}
|
||||
<summary><u>GBA Virtual Console and/or Safe Mode functionality is broken</u></summary>
|
||||
|
||||
Your device is running Luma3DS/AuReiNand 6.6 or older, likely via arm9loaderhax. Deberías seguir [A9LH a B9S](a9lh-to-b9s) para actualizar tu consola a un entorno de custom firmware más moderno.
|
||||
Your device is running Luma3DS 6.6 or older, likely via arm9loaderhax. Deberías seguir [A9LH a B9S](a9lh-to-b9s) para actualizar tu consola a un entorno de custom firmware más moderno.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Extended memory mode games are broken
|
||||
{% capture compat %}
|
||||
<summary><u>Extended memory mode games (Pokemon Sun/Moon, Smash, etc.) don't work</u></summary>
|
||||
|
||||
Esto puede ocurrir después de un CTRTransfer o al cambiar de región en Old 3DS / 2DS. Necesitarás formatear tu consola para solucionar este problema.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## Other troubleshooting
|
||||
|
||||
### Clear HOME Menu extdata
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu extdata</u></summary>
|
||||
|
||||
1. Apaga tu consola
|
||||
1. Inserta tu tarjeta SD en tu computadora
|
||||
|
|
@ -412,8 +592,11 @@ Esto puede ocurrir después de un CTRTransfer o al cambiar de región en Old 3DS
|
|||
+ **Región KOR**: `000000A9`
|
||||
+ **Región TWN**: `000000B1`
|
||||
1. Vuelve a insertar tu tarjeta SD en tu consola
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Clear HOME Menu theme data
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu theme data</u></summary>
|
||||
|
||||
1. Apaga tu consola
|
||||
1. Inserta tu tarjeta SD en tu computadora
|
||||
|
|
@ -423,3 +606,6 @@ Esto puede ocurrir después de un CTRTransfer o al cambiar de región en Old 3DS
|
|||
+ **JPN Region**: `000002cc`
|
||||
+ **USA Region**: `000002cd`
|
||||
1. Vuelve a insertar tu tarjeta SD en tu consola
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@ El propósito de esta sección es comprobar si las aplicaciones integradas del m
|
|||
+ Si tu consola muestra la versión japonesa de Flipnote Studio, una pantalla en negro, o un mensaje de error; significa que esta prueba ha fallado
|
||||
1. Apaga tu consola
|
||||
|
||||
Si cualquiera de estas pruebas falla, ¡el modo DS, el Modo Descarga DS y/o la Configuración de conexión de DS podrían ser inaccesibles una vez que el CFW sea desinstalado! You should [fix DS mode](troubleshooting#dsi--ds-functionality-is-broken-or-has-been-replaced-with-flipnote-studio) before continuing.
|
||||
Si cualquiera de estas pruebas falla, ¡el modo DS, el Modo Descarga DS y/o la Configuración de conexión de DS podrían ser inaccesibles una vez que el CFW sea desinstalado! You should [fix DS mode](troubleshooting#software-issues-on-devices-with-custom-firmware) before continuing.
|
||||
{: .notice--warning}
|
||||
|
||||
#### Sección III - Prueba de Seguridad
|
||||
|
|
@ -105,7 +105,7 @@ If you do NOT boot into the regular 3DS HOME Menu, or System Settings / your key
|
|||
|
||||
#### Sección IV - Copia de seguirdad de la NAND
|
||||
|
||||
1. Presiona y mantén el botón (Start), y mientras lo mantienes presionado, enciende tu consola. Esto abrirá GodMode9
|
||||
1. Mantén presionado el botón (Start), y enciende la consola sin soltarlo. Esto iniciará GodMode9
|
||||
1. Presiona el botón (Home) para abrir el menú de acción
|
||||
1. Selecciona "Scripts..."
|
||||
1. Selecciona "GM9Megascript"
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ Korvaa mahdolliset olemassa olevat tiedostot SD-kortillasi kaikissa tämän vaih
|
|||
1. Konsolisi pitäisi uudelleenkäynnistyä suoraan Luma3DS:n määritysvalikkoon
|
||||
+ 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 get a black screen, [follow this troubleshooting guide](troubleshooting#boot-related-issues-on-modded-devices)
|
||||
+ If you get a black screen, [follow this troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware)
|
||||
1. Paina (START)-painiketta tallentaaksesi ja käynnistääksesi uudelleen
|
||||
|
||||
___
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ This is an add-on section to check if your console already has a modern custom f
|
|||
|
||||
If your console already has an arm9loaderhax or boot9strap based custom firmware, you will need to follow the instructions indicated to upgrade your setup to a modern one.
|
||||
|
||||
If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#clear-home-menu-extdata), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
|
||||
If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#other-troubleshooting), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
|
||||
{: .notice--info}
|
||||
|
||||
### Ohjeet
|
||||
|
|
|
|||
|
|
@ -14,79 +14,173 @@ title: "UKK"
|
|||
|
||||
## Pre-Installation FAQ
|
||||
|
||||
#### **Q:** *I am on the latest system version. Is my device hackable without any external hardware?*
|
||||
**A:** Yes! The latest firmware (11.16.0) has a free method for getting CFW named [Seedminer](seedminer).
|
||||
{% capture compat %}
|
||||
<summary><u>I am on the latest system version. Is my device hackable without any external hardware?</u></summary>
|
||||
|
||||
#### **Q:** *What devices is this guide compatible with?*
|
||||
**A:** The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. If your system version string displays as "0.0.0-0", then you may have a developer unit.
|
||||
Yes! The latest firmware (11.16.0) has a free method for getting CFW named [Seedminer](seedminer).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How risky is hacking my console?*
|
||||
**A:** Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
{% capture compat %}
|
||||
<summary><u>What devices is this guide compatible with?</u></summary>
|
||||
|
||||
#### **Q:** *Can I run awesome homebrew and emulators with this?*
|
||||
**A:** Yes! This guide will install a few useful homebrew applications, including [Universal-Updater](https://github.com/Universal-Team/Universal-Updater/releases/latest), which acts as a homebrew app store.
|
||||
The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. If your system version string displays as "0.0.0-0", then you may have a developer unit.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I use this to play games from other regions?*
|
||||
**A:** Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Some games may need to make use of Luma's [locale emulation feature](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) in order to work properly on out-of-region devices.
|
||||
{% capture compat %}
|
||||
<summary><u>How risky is hacking my console?</u></summary>
|
||||
|
||||
#### **Q:** *Will I lose any features if I install CFW?*
|
||||
**A:** No. Devices with custom firmware can still use the eShop and run physical cartridges as any other 3DS can.
|
||||
Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I keep my NNID?*
|
||||
**A:** Your NNID (if you have one) will not be affected by this guide. Devices with a region of KOR, CHN, or TWN do not have NNID functionality to begin with and are thus unaffected.
|
||||
{% capture compat %}
|
||||
<summary><u>Can I run awesome homebrew and emulators with this?</u></summary>
|
||||
|
||||
#### **Q:** *Will my 3DS be banned for having CFW?*
|
||||
**A:** There was a ban wave in May 2017 that banned CFW users from online play (eShop access, NNIDs, and Nintendo Accounts were unaffected), seemingly at random. A ban wave at such a scale has not been seen since. That being said, we don't know what Nintendo may have in store in the future. At this time, we don't think that bans are something that you need to worry about.
|
||||
Yes! This guide will install a few useful homebrew applications, including [Universal-Updater](https://github.com/Universal-Team/Universal-Updater/releases/latest), which acts as a homebrew app store.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I do this without a computer (e.g. an Android phone)?*
|
||||
**A:** All you need is the ability to put files on a compatible SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Can I use this to play games from other regions?</u></summary>
|
||||
|
||||
#### **Q:** *What size SD card can I use?*
|
||||
**A:** You will need at least 1.5GB of free SD card space to follow this guide in its entirety. While the 3DS is officially compatible with SD cards up to 32GB, larger SD cards can be used if they are manually re-formatted as FAT32. It is not recommended to use SD cards greater than 128GB due to known issues with GBA graphics and custom themes.
|
||||
Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Some games may need to make use of Luma's [locale emulation feature](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) in order to work properly on out-of-region devices.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *I heard about this thing I have to pay for (Gateway, Sky3DS, ntrboot, R4, etc). Is that something I need?*
|
||||
**A:** No. Custom firmware can be installed for free on the latest firmware without any hardware devices. In fact, 3DS-mode flashcarts like Gateway and Sky3DS are not recommended because they are obsolete and may carry ban or brick risk.
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose any features if I install CFW?</u></summary>
|
||||
|
||||
#### **Q:** *What's the difference between custom firmware and homebrew access?*
|
||||
**A:** Historically, the 3DS used to have userland homebrew access through older exploits like ninjhax. The level of system access granted with userland allowed you to run basic homebrew and emulators but did not allow you to (easily) modify games or dump cartridges. It was also a lot less stable, with homebrew often ungracefully crashing and requiring a full reboot. Custom firmware grants a far greater level of system access while also being more stable than homebrew-only entrypoints.
|
||||
No. Devices with custom firmware can still use the eShop and run physical cartridges as any other 3DS can.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I keep my NNID?</u></summary>
|
||||
|
||||
Your NNID (if you have one) will not be affected by this guide. Devices with a region of KOR, CHN, or TWN do not have NNID functionality to begin with and are thus unaffected.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will my 3DS be banned for having CFW?</u></summary>
|
||||
|
||||
There was a ban wave in May 2017 that banned CFW users from online play (eShop access, NNIDs, and Nintendo Accounts were unaffected), seemingly at random. A ban wave at such a scale has not been seen since. That being said, we don't know what Nintendo may have in store in the future. At this time, we don't think that bans are something that you need to worry about.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I do this without a computer (e.g. an Android phone)?</u></summary>
|
||||
|
||||
Yes! All you need is the ability to put files on a compatible SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What size SD card can I use?</u></summary>
|
||||
|
||||
You will need at least 1.5GB of free SD card space to follow this guide in its entirety. While the 3DS is officially compatible with SD cards up to 32GB, larger SD cards can be used if they are manually re-formatted as FAT32. It is not recommended to use SD cards greater than 128GB due to known issues with GBA graphics and custom themes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>I heard about this thing I have to pay for (Gateway, Sky3DS, ntrboot, R4, etc). Is that something I need?</u></summary>
|
||||
|
||||
No. Custom firmware can be installed for free on the latest firmware without any hardware devices. In fact, 3DS-mode flashcarts like Gateway and Sky3DS are not recommended because they are obsolete and may carry ban or brick risk.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What's the difference between custom firmware and homebrew?</u></summary>
|
||||
|
||||
Historically, the 3DS used to have userland homebrew access through older exploits like ninjhax. The level of system access granted with userland allowed you to run basic homebrew and emulators but did not allow you to (easily) modify games or dump cartridges. It was also a lot less stable, with homebrew often ungracefully crashing and requiring a full reboot. Custom firmware grants a far greater level of system access while also being more stable than homebrew-only entrypoints.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Post-Installation FAQ
|
||||
|
||||
#### **Q:** *Is it safe to update my 3DS to the latest version with CFW?*
|
||||
**A:** If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. There have been updates in the past that have resulted in Luma3DS crashing on boot, so it is a good idea to wait a couple of hours to ensure that the latest update will not temporarily render the device unusable until Luma3DS is updated. System updates can be performed the same way as they are on a stock 3DS: through System Settings, Safe Mode, or the update prompt when the update is automatically downloaded.
|
||||
{% capture compat %}
|
||||
<summary><u>Is it safe to update my 3DS to the latest version with CFW?</u></summary>
|
||||
|
||||
#### **Q:** *How do I upgrade my SD card?*
|
||||
**A:** Copy and paste your SD card contents to a new SD card formatted as FAT32. For 128GB cards, an allocation size of 65536 is recommended. SD cards larger than 128GB are not recommended due to known issues with GBA graphics and custom themes.
|
||||
If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. There have been updates in the past that have resulted in Luma3DS crashing on boot, so it is a good idea to wait a couple of hours to ensure that the latest update will not temporarily render the device unusable until Luma3DS is updated. System updates can be performed the same way as they are on a stock 3DS: through System Settings, Safe Mode, or the update prompt when the update is automatically downloaded.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I system transfer with CFW?*
|
||||
**A:** Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets for illegitimate titles (homebrew) will not transfer, but the titles can be made to reappear with [faketik](https://github.com/ihaveamac/faketik/releases/latest). Make sure that you do not perform a wireless transfer, as this will delete illegitimate titles. CFW will remain on both consoles.
|
||||
{% capture compat %}
|
||||
<summary><u>How do I upgrade my SD card?</u></summary>
|
||||
|
||||
#### **Q:** *How do I change the system language of a Japanese 3DS?*
|
||||
**A:** The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Note that this is very likely to break the Nintendo eShop on your device, which means you will be unable to update your games whether they are in-region or out-of-region.
|
||||
Copy and paste your SD card contents to a new SD card formatted as FAT32. For 128GB cards, an allocation size of 65536 is recommended. SD cards larger than 128GB are not recommended due to known issues with GBA graphics and custom themes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How do I update homebrew applications?*
|
||||
**A:** It depends on the format of the homebrew application. Generally speaking:
|
||||
{% capture compat %}
|
||||
<summary><u>Can I system transfer with CFW?</u></summary>
|
||||
|
||||
Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets for illegitimate titles (homebrew) will not transfer, but the titles can be made to reappear with [faketik](https://github.com/ihaveamac/faketik/releases/latest). Make sure that you do not perform a wireless transfer, as this will delete illegitimate titles. CFW will remain on both consoles.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I change the system language of a Japanese 3DS?</u></summary>
|
||||
|
||||
The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Note that this is very likely to break the Nintendo eShop on your device, which means you will be unable to update your games whether they are in-region or out-of-region.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I update homebrew applications?</u></summary>
|
||||
|
||||
It depends on the format of the homebrew application. Generally speaking:
|
||||
|
||||
* Homebrew in **CIA format** can be updated by installing the new CIA, which will usually overwrite the old one. If the old CIA is not overwritten, you can delete the old one from Data Management as you would any other 3DS title.
|
||||
* Homebrew in **3DSX format** can be updated by replacing the 3DSX file in `/3ds/` with a fresh copy. If the homebrew application includes additional assets, you may need to place that folder somewhere else. Refer to the documentation of the homebrew application.
|
||||
* For updating Luma3DS, see [this page](restoring-updating-cfw). For updating GodMode9, see [this page](godmode9-usage#updating-godmode9).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How do I update games from outside of my 3DS region?*
|
||||
**A:** You will need to [dump the updates](dumping-titles-and-game-cartridges) from a 3DS that has the updates installed. The Nintendo eShop only contains updates for the console's region (a Japanese 3DS will only have updates for Japanese games).
|
||||
{% capture compat %}
|
||||
<summary><u>How do I update my games?</u></summary>
|
||||
|
||||
#### **Q:** *Help! Something bad happened and now I cannot boot...*
|
||||
**A:** Please look at the [troubleshooting guide](troubleshooting). **Uninstalling CFW when your device is in an unbootable state is not recommended, as it is very likely to lead to a brick**.
|
||||
You can continue to download game updates from the Nintendo eShop, even after the 2023 shutdown.
|
||||
|
||||
If the game is not from the same region as the console, you will need to [dump the updates](dumping-titles-and-game-cartridges) from a 3DS that has the updates installed. The Nintendo eShop only contains updates for the console's region (a Japanese 3DS will only have updates for Japanese games).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Help! Something bad happened and my 3DS won't boot to HOME Menu...</u></summary>
|
||||
|
||||
Please look at the [troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware). **Uninstalling CFW when your device is in an unbootable state is not recommended, as it is very likely to lead to a brick**.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## menuhax / A9LH / Gateway FAQ
|
||||
|
||||
#### **Q:** *I modded my device x years ago. What should I do?*
|
||||
**A:** It is recommended that you upgrade your setup to a modern, boot9strap-based one. Follow the [Checking for CFW](checking-for-cfw) guide to see how to upgrade your setup.
|
||||
{% capture compat %}
|
||||
<summary><u>I modded my device (x) years ago, so it already has some sort of homebrew. What should I do?</u></summary>
|
||||
|
||||
#### **Q:** *My setup works for me. Why should I upgrade it?*
|
||||
**A:** The vast majority of modern homebrew (such as Checkpoint and BootNTR Selector) have only been tested on modern, boot9strap-based setups and may not work entirely (or at all) on older setups based on menuhax, A9LH, or Gateway. In addition, depending on your setup, you may be unable to safely update to the latest firmware. Modern, boot9strap-based setups allow for a greater level of system access than previous hacks, including the ability to dump your console's bootrom.
|
||||
It is recommended that you upgrade your setup to a modern, boot9strap-based one. Follow the [Checking for CFW](checking-for-cfw) guide to see how to upgrade your setup.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Will I lose anything if I upgrade my setup?*
|
||||
**A:** Your old setup (including your EmuNAND, if you have one) can usually be directly migrated to boot9strap with no data loss. If you have data that is particularly important to you, it would be a good idea to make a decrypted backup of your save data before upgrading your setup with a tool like [JKSM](https://github.com/J-D-K/JKSM/releases/tag/12%2F20%2F2018).
|
||||
{% capture compat %}
|
||||
<summary><u>My setup works for me. Why should I upgrade it?</u></summary>
|
||||
|
||||
The vast majority of modern homebrew (such as Checkpoint and BootNTR Selector) have only been tested on modern, boot9strap-based setups and may not work entirely (or at all) on older setups based on menuhax, A9LH, or Gateway. In addition, depending on your setup, you may be unable to safely update to the latest firmware. Modern, boot9strap-based setups allow for a greater level of system access than previous hacks, including the ability to dump your console's bootrom.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose anything if I upgrade my setup?</u></summary>
|
||||
|
||||
Your old setup (including your EmuNAND, if you have one) can usually be directly migrated to boot9strap with no data loss. If you have data that is particularly important to you, it would be a good idea to make a decrypted backup of your save data before upgrading your setup with a tool like [JKSM](https://github.com/J-D-K/JKSM/releases/tag/12%2F20%2F2018).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I move saves from an existing Gateway setup to a more modern setup?</u></summary>
|
||||
|
||||
#### **Q:** *How do I move saves from an existing Gateway setup to a more modern setup?*
|
||||
**A:** See [this thread](https://gbatemp.net/threads/425743/).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@ In this section, you will update your system to the latest version, which is saf
|
|||
+ Päivitykset B9S + Luma -kokoonpanolla (joka sinulla on) ovat turvallisia
|
||||
+ The updater may display a message saying "Your system is up to date" instead of updating. This is normal if you are already up to date; continue with the next section
|
||||
+ If this gives you an error, set both your DNS settings and Proxy settings to "auto"
|
||||
+ If this still gives you an error, [follow this troubleshooting guide](troubleshooting#unable-to-update-device)
|
||||
+ If this still gives you an error, [follow this troubleshooting guide](troubleshooting#finalizing-setup)
|
||||
|
||||
#### Section III - Homebrew Launcher
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
|||
1. Launch System Settings on your device
|
||||
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#dsiware-management-menu-crashes-without-showing-bb3-multihax-menu)
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#installing-boot9strap-fredtool)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Dump DSiWare"
|
||||
+ Your device will automatically reboot
|
||||
1. Sammuta konsolisi
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
|||
1. Launch System Settings on your device
|
||||
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#dsiware-management-menu-crashes-without-showing-bb3-multihax-menu)
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#bannerbomb3)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Install unSAFE_MODE"
|
||||
+ Your device will automatically power off
|
||||
|
||||
|
|
|
|||
|
|
@ -168,7 +168,6 @@ Jotta voisit tunnistaa `<sovellustunnus>.gbavc.sav`-tiedoston pelin, voit näytt
|
|||
1. Aseta SD-korttisi takaisin konsoliisi
|
||||
1. Paina (A):ta liittääksesi SD-korttisi takaisin järjestelmään
|
||||
1. Paina (START)-painiketta käynnistääksesi uudelleen
|
||||
1. If you get a black screen, [follow this troubleshooting guide](troubleshooting#ts_sys_down)
|
||||
|
||||
___
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ In this section, you will get the necessary details from your 3DS that are requi
|
|||
+ If you don't have a `Nintendo 3DS` folder, put your SD card into your 3DS and power it on so that the folder can be created
|
||||
1. Copy the name of the 32-letter folder you see directly inside Nintendo 3DS
|
||||
+ This 32-letter name is system-specific and will be different for each console
|
||||
+ If you see multiple 32-letter folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
|
||||
+ If you see multiple 32-letter folders, follow [these instructions](troubleshooting#seedminer)
|
||||
+ You can ignore the `private` folder if you have it
|
||||
|
||||
![]({{ "/images/screenshots/seedminer/id0-example.png" | absolute_url }})
|
||||
|
|
|
|||
|
|
@ -2,37 +2,69 @@
|
|||
title: "Vianmääritys"
|
||||
---
|
||||
|
||||
{% include toc title="Table of Contents"%}
|
||||
|
||||
This page offers troubleshooting advice for commonly encountered issues. If you are unable to solve your issue with the advice on this page, please join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and describe your issue, including what you have already tried.
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary>Table of Contents</summary>
|
||||
|
||||
Used on multiple pages:
|
||||
* [SafeB9SInstaller](#issues-with-safeb9sinstaller)
|
||||
|
||||
Guide pages:
|
||||
* [Seedminer](#seedminer)
|
||||
* [BannerBomb3](#bannerbomb3)
|
||||
* [Installing boot9strap (USM)](#installing-boot9strap-usm)
|
||||
* [Installing boot9strap (Fredtool)](#installing-boot9strap-fredtool)
|
||||
* [Homebrew Launcher (PicHaxx)](#homebrew-launcher-pichaxx)
|
||||
* [Installing boot9strap (Soundhax)](#installing-boot9strap-soundhax)
|
||||
* [Installing boot9strap (SSLoth-Browser)](#installing-boot9strap-ssloth-browser)
|
||||
|
||||
* [Finalizing Setup](#finalizing-setup)
|
||||
|
||||
Issues after installation:
|
||||
* [Boot issues](#boot-issues-on-devices-with-custom-firmware)
|
||||
* [Software issues](#software-issues-on-devices-with-custom-firmware)
|
||||
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
{: .notice--info}
|
||||
|
||||
## Issues with SafeB9SInstaller
|
||||
|
||||
### SigHaxed FIRM was not installed! Check lower screen for more info.
|
||||
|
||||
#### SigHaxed FIRM - File not found
|
||||
{% capture compat %}
|
||||
<summary><u>SigHaxed FIRM - File not found</u></summary>
|
||||
|
||||
You are missing `boot9strap.firm` and `boot9strap.firm.sha` from the `boot9strap` folder, or the `boot9strap` folder is misnamed. Download the latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip), and place `boot9strap.firm` and `boot9strap.firm.sha` in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### SigHaxed FIRM - invalid FIRM
|
||||
{% capture compat %}
|
||||
<summary><u>SigHaxed FIRM - invalid FIRM</u></summary>
|
||||
|
||||
There is an issue with your `boot9strap.firm` and `boot9strap.firm.sha` files. Re-download the latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip), and place `boot9strap.firm` and `boot9strap.firm.sha` in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Secret Sector - File not found
|
||||
{% capture compat %}
|
||||
<summary><u>Secret Sector - File not found</u></summary>
|
||||
|
||||
You are missing `secret_sector.bin` from the `boot9strap` folder, or the `boot9strap` folder is misnamed. Download [secret_sector.bin](magnet:?xt=urn:btih:15a3c97acf17d67af98ae8657cc66820cc58f655&dn=secret_sector.bin&tr=udp%3a%2f%2ftracker.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.lelux.fi%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.loadbt.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.moeking.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.monitorit4.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.ololosh.space%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.pomf.se%3a80%2fannounce&tr=udp%3a%2f%2ftracker.srv00.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.theoks.net%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.tiny-vps.com%3a6969%2fannounce&tr=udp%3a%2f%2fopen.tracker.cl%3a1337%2fannounce&tr=udp%3a%2f%2ftracker.zerobytes.xyz%3a1337%2fannounce&tr=udp%3a%2f%2ftracker1.bt.moack.co.kr%3a80%2fannounce&tr=udp%3a%2f%2fvibe.sleepyinternetfun.xyz%3a1738%2fannounce&tr=udp%3a%2f%2fwww.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a6969%2fannounce&tr=udp%3a%2f%2f9.rarbg.com%3a2810%2fannounce&tr=udp%3a%2f%2ftracker.opentrackr.org%3a1337%2fannounce&tr=udp%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fopenbittorrent.com%3a80%2fannounce) using a torrent client, and place it in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Something else
|
||||
{% capture compat %}
|
||||
<summary><u>Something else</u></summary>
|
||||
|
||||
Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance, and describe the message that you see.
|
||||
|
||||
---
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Seedminer
|
||||
|
||||
### Multiple long folder names in Nintendo 3DS folder
|
||||
{% capture compat %}
|
||||
<summary><u>Multiple long folder names in Nintendo 3DS folder</u></summary>
|
||||
|
||||
![]({{ "/images/screenshots/multiple-id0.png" | absolute_url }})
|
||||
{: .notice--info}
|
||||
|
|
@ -49,98 +81,285 @@ This occurs when you use your SD card in multiple 3DS devices and is intended to
|
|||
+ This is your true ID0 that you will use in [Section II of Seedminer](seedminer#section-ii---seedminer)
|
||||
1. Delete the `Nintendo 3DS` folder
|
||||
1. Rename the `BACKUP_Nintendo 3DS` folder to `Nintendo 3DS`
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Bruteforce Movable skips to step 4
|
||||
{% capture compat %}
|
||||
<summary><u>Bruteforce Movable skips to step 4</u></summary>
|
||||
|
||||
The website has already mined your `movable.sed` using your friend code and ID0 combination. You can use the `movable.sed` that it provides you.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Important! You have been locked out of the automated part1 dumper system...
|
||||
{% capture compat %}
|
||||
<summary><u>Important! You have been locked out of the automated part1 dumper system...</u></summary>
|
||||
|
||||
Your friend code was blocked from using the friend code bot because your 3DS did not successfully friend the bot. Ensure your 3DS is properly connected to the Internet, then join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask to be unlocked.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### We were unable to successfully complete your bruteforce request. :`(
|
||||
{% capture compat %}
|
||||
<summary><u>We were unable to successfully complete your bruteforce request. :`(</u></summary>
|
||||
|
||||
The website has determined that your `movable.sed` cannot be brute-forced. Ensure that you gave the correct ID0 to the website. If your ID0 is correct, then you will be unable to use Seedminer and you will have to use an alternate method that will require additional games or hardware.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
## BannerBomb3
|
||||
|
||||
## Homebrew Launcher (PicHaxx)
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management menu crashes without showing BB3 multihax menu</u></summary>
|
||||
Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. If it is, then re-create it with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen).
|
||||
|
||||
### "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
Your `00000001.sav` and/or `otherapp.bin` files may be misplaced. Ensure that `00000001.sav` is in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data` and that `otherapp.bin` is on the root of your SD card.
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow [an alternate branch of Seedminer](homebrew-launcher-(pichaxx)). If Safe Mode doesn't work or you need assistance with this matter, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
If your files are in the correct locations, re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx), then place it in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`. Ensure that the file is named exactly `00000001.sav` and that you used your console's `movable.sed` to create it. Re-download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management menu does not crash</u></summary>
|
||||
|
||||
### "An exception occurred" or Errdisp when opening Picross
|
||||
`F00D43D5.bin` is missing from `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. Make sure that `Nintendo DSiWare` is correctly spelled and spaced. Uppercase/lowercase does not matter.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
Your device already has custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management shows a question mark</u></summary>
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
There may be an issue with your `F00D43D5.bin` file (it may be corrupted or intended for the wrong 3DS). Re-create your `F00D43D5.bin` file with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen), ensuring that you use the `movable.sed` file for your console.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
There is an issue with your `otherapp.bin` file. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
## Installing boot9strap (USM)
|
||||
|
||||
### Game starts normally
|
||||
{% capture compat %}
|
||||
<summary><u>Safe Mode system update succeeds instead of giving error 003-1099</u></summary>
|
||||
|
||||
Your modified `00000001.sav` file may be misplaced, or you may have used the wrong `movable.sed` when creating it. Re-generate your `movable.sed` from [Bruteforce Movable](https://seedminer.hacks.guide), then re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx) and place the resulting file (`00000001.sav`) in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`.
|
||||
unSAFE_MODE is not installed. [Follow the instructions](installing-boot9strap-(usm)] to install it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary><u>Red screen after selecting "Detailed Setup"</u></summary>
|
||||
|
||||
## Installing boot9strap (Soundhax)
|
||||
The file `usm.bin` is missing or misplaced. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/download/v1.3/usm.bin) and place `usm.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
### Red/purple/pink and white screen after running Soundhax
|
||||
There is also a possibility that the console isn't reading your SD card. Make sure it is inserted and formatted correctly.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
If your device is not on those firmwares, it likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
|
||||
There is an issue with your `otherapp.bin` file (it is missing, misplaced, or corrupted). Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) and place it on the root of your SD card.
|
||||
|
||||
### "Could not play"
|
||||
|
||||
You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow [Seedminer](seedminer).
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to mount the SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
## Installing boot9strap (Fredtool)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Error on Fredtool Injector page</u></summary>
|
||||
|
||||
Ensure that your `movable.sed` and DSiWare backup come from the same console. A mismatch will result in an error.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to select "Haxxxxxxxxx!" because the BB3 multihax menu appears</u></summary>
|
||||
|
||||
You forgot to delete `F00D43D5.bin` from the SD card. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card and delete the `F00D43D5.bin` file.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"Haxxxxxxxxx!" does not appear</u></summary>
|
||||
|
||||
There is an issue with your `42383821.bin` file (it is incorrect, missing, misplaced, or corrupted). Re-create your files with the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website and ensure that you place the `42383821.bin` file from `output.zip` -> `hax` in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DS Connection Settings launches normally</u></summary>
|
||||
|
||||
`Haxxxxxxxxx!` was not copied from your SD card to your system memory.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Black screen when launching DS Connection Settings</u></summary>
|
||||
|
||||
Your DS Connection Settings application is broken, and you will need Homebrew Launcher access to fix this issue. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>SD card is grayed out in Flipnote</u></summary>
|
||||
|
||||
Flipnote may take a long time to index your card if you have a large SD card. Let it sit for a few minutes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Lenny face does not appear in SD card section</u></summary>
|
||||
|
||||
You did not copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Flipnote freezes</u></summary>
|
||||
|
||||
You may have accidentally touched the touch screen while in the modified Flipnote. Re-enter DS Connection Settings and try again, ensuring that you don't accidentally use the touchscreen.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Green screen after pasting</u></summary>
|
||||
|
||||
The file `boot.nds` is missing or misplaced. Download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>White screen after pasting</u></summary>
|
||||
There is an issue with your `boot.nds` file. Re-download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to open Luma3DS configuration menu after running B9STool</u></summary>
|
||||
|
||||
It is possible that boot9strap was not successfully installed. Follow section B of [this page](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Homebrew Launcher (PicHaxx)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
|
||||
|
||||
Your `00000001.sav` and/or `otherapp.bin` files may be misplaced. Ensure that `00000001.sav` is in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data` and that `otherapp.bin` is on the root of your SD card.
|
||||
|
||||
If your files are in the correct locations, re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx), then place it in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`. Ensure that the file is named exactly `00000001.sav` and that you used your console's `movable.sed` to create it. Re-download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" or Errdisp when opening Picross</u></summary>
|
||||
|
||||
Your device already has custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `otherapp.bin` file. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Game starts normally</u></summary>
|
||||
|
||||
Your modified `00000001.sav` file may be misplaced, or you may have used the wrong `movable.sed` when creating it. Re-generate your `movable.sed` from [Bruteforce Movable](https://seedminer.hacks.guide), then re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx) and place the resulting file (`00000001.sav`) in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Installing boot9strap (Soundhax)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Soundhax</u></summary>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
If your device is not on those firmwares, it likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `otherapp.bin` file (it is missing, misplaced, or corrupted). Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) and place it on the root of your SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"Could not play"</u></summary>
|
||||
|
||||
You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow [Seedminer](seedminer).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Installing boot9strap (SSLoth-Browser)
|
||||
|
||||
### Red/purple/pink and white screen after running browserhax
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Browserhax</u></summary>
|
||||
|
||||
This likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
|
||||
|
||||
The file `arm11code.bin` is missing or misplaced. Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place `otherapp.bin` on the root of your SD card and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `arm11code.bin` file. Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place `otherapp.bin` on the root of your SD card and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Opening the browserhax QR code or URL crashes
|
||||
{% capture compat %}
|
||||
<summary><u>Opening the browserhax QR code or URL crashes</u></summary>
|
||||
|
||||
Browser based exploits (such as this one) are often unstable and crash frequently, but they can sometimes be fixed by doing the following steps.
|
||||
|
||||
1. Launch the browser, then launch the browser settings
|
||||
1. Scroll to the bottom and Initialize Savedata (it also may be called Clear All Save Data)
|
||||
1. Try the exploit again
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Opening the browser prompts for a system update instead
|
||||
{% capture compat %}
|
||||
<summary><u>System Update prompt when opening browser</u></summary>
|
||||
|
||||
The SSLoth proxy was incorrectly configured. Re-do the SSLoth section on the page.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Error 032-0420 when trying to open the browser
|
||||
{% capture compat %}
|
||||
<summary><u>Error 032-0420 when opening browser</u></summary>
|
||||
|
||||
Follow these steps in order:
|
||||
|
||||
|
|
@ -157,126 +376,47 @@ Follow these steps in order:
|
|||
1. If prompted about a system update, press OK
|
||||
+ This won't actually update the system
|
||||
1. Start again from [Section II](installing-boot9strap-(ssloth-browser).html#section-ii---ssloth)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Frozen on "Doing agbhax..."
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Frozen on "Doing agbhax..."</u></summary>
|
||||
There may be an issue with your `arm11code.bin` file. Re-download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place it on the root of your SD card, and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
If you have a Taiwanese unit (with a T in the version string, ie. 11.3.0-##T), you will not be able to follow these instructions, and you will need to update your console and follow [Seedminer](seedminer) instead.
|
||||
|
||||
If you have a Mainland Chinese unit (with a C in the version string, ie. 11.3.0-##C), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "PrepareArm9ForTwl returned error c8804631!"
|
||||
{% capture compat %}
|
||||
<summary><u>"PrepareArm9ForTwl returned error c8804631!"</u></summary>
|
||||
|
||||
You will need to follow an alternate method. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to mount the SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## BannerBomb3
|
||||
|
||||
### DSiWare Management menu crashes without showing BB3 multihax menu
|
||||
|
||||
Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. If it is, then re-create it with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen).
|
||||
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow [an alternate branch of Seedminer](homebrew-launcher-(pichaxx)). If Safe Mode doesn't work or you need assistance with this matter, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
|
||||
### DSiWare Management menu does not crash
|
||||
|
||||
`F00D43D5.bin` is missing from `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. Make sure that `Nintendo DSiWare` is correctly spelled and spaced. Uppercase/lowercase does not matter.
|
||||
|
||||
### DSiWare Management shows a question mark
|
||||
|
||||
There may be an issue with your `F00D43D5.bin` file (it may be corrupted or intended for the wrong 3DS). Re-create your `F00D43D5.bin` file with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen), ensuring that you use the `movable.sed` file for your console.
|
||||
|
||||
---
|
||||
|
||||
## Installing boot9strap (USM)
|
||||
|
||||
### Update doesn't fail with error code `003-1099`
|
||||
|
||||
unSAFE_MODE is not installed. Follow the instructions on your page to install unSAFE_MODE again.
|
||||
|
||||
### Red screen when selecting detailed setup
|
||||
|
||||
The file `usm.bin` is missing or misplaced. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/download/v1.3/usm.bin) and place `usm.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
There is also a possibility that the console isn't reading your SD card. Make sure it is inserted and formatted correctly.
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
### Failed to mount the SD card!
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
|
||||
---
|
||||
|
||||
## Installing boot9strap (Fredtool)
|
||||
|
||||
### Error on Fredtool Injector page
|
||||
|
||||
Ensure that your `movable.sed` and DSiWare backup come from the same console. A mismatch will result in an error.
|
||||
|
||||
### Unable to select the "Haxxxxxxxxx!" title because of the BB3 multihax menu
|
||||
|
||||
You forgot to delete `F00D43D5.bin` from the SD card. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card and delete the `F00D43D5.bin` file.
|
||||
|
||||
### "Haxxxxxxxxx!" does not appear
|
||||
|
||||
There is an issue with your `42383821.bin` file (it is incorrect, missing, misplaced, or corrupted). Re-create your files with the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website and ensure that you place the `42383821.bin` file from `output.zip` -> `hax` in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`.
|
||||
|
||||
### DS Connection Settings launches normally
|
||||
|
||||
`Haxxxxxxxxx!` was not copied from your SD card to your system memory.
|
||||
|
||||
### Black screen when launching DS Connection Settings
|
||||
|
||||
Your DS Connection Settings application is broken, and you will need Homebrew Launcher access to fix this issue. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
|
||||
### SD card is grayed out
|
||||
|
||||
Flipnote may take a long time to index your card if you have a large SD card. Let it sit for a few minutes.
|
||||
|
||||
### Lenny face does not appear
|
||||
|
||||
You did not copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card.
|
||||
|
||||
### Flipnote is frozen
|
||||
|
||||
You may have accidentally touched the touch screen while in the modified Flipnote. Re-enter DS Connection Settings and try again, ensuring that you don't accidentally use the touchscreen.
|
||||
|
||||
### Green screen after pasting
|
||||
|
||||
The file `boot.nds` is missing or misplaced. Download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
|
||||
### White screen after pasting
|
||||
|
||||
There is an issue with your `boot.nds` file. Re-download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
|
||||
### Unable to open Luma3DS configuration menu after running b9stool
|
||||
|
||||
It is possible that boot9strap was not successfully installed. Follow section B of [this page](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md).
|
||||
|
||||
---
|
||||
|
||||
## Finalizing Setup
|
||||
|
||||
### Unable to update device
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to update device</u></summary>
|
||||
|
||||
The steps below can be attempted in any order, but are listed from easiest to hardest to perform.
|
||||
|
||||
|
|
@ -289,37 +429,41 @@ The steps below can be attempted in any order, but are listed from easiest to ha
|
|||
1. Nintendo servers may be down; Try again later
|
||||
1. If you still get an error, [follow CTRTransfer](ctrtransfer), then try again
|
||||
1. For further support (in English), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Unable to enter Rosalina due to broken button(s)
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to enter Rosalina menu due to broken Left Shoulder / Down D-Pad / Select button(s)</u></summary>
|
||||
|
||||
Download this [alternate config.ini](https://cdn.discordapp.com/attachments/196635695958196224/982798396265988186/config.ini) and place it in `/luma/`. This will change the Rosalina key combination to (X) + (Y).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An exception occurred" after trying to launch Homebrew Launcher via Download Play
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" after trying to launch Homebrew Launcher from Download Play</u></summary>
|
||||
|
||||
There is an issue with your `boot.3dsx` file (it is missing, misplaced, or corrupted). Download the latest release of [the Homebrew Launcher](https://github.com/devkitPro/3ds-hbmenu/releases/latest) and place `boot.3dsx` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "Scripts directory not found" in GodMode9
|
||||
{% capture compat %}
|
||||
<summary><u>"Scripts directory not found" in GodMode9</u></summary>
|
||||
|
||||
You did not copy the `gm9` folder from the GodMode9 `.zip` to the root of your SD card. Download the latest release of [GodMode9](https://github.com/d0k3/GodMode9/releases/latest) and place the `gm9` folder on the root of your SD card, merging it with the existing one.
|
||||
|
||||
### `essentials.exefs` missing from `/gm9/out/`
|
||||
|
||||
Your device had custom firmware in the past, so you were not automatically prompted to make a backup. Make a backup manually:
|
||||
|
||||
1. Aseta SD-korttisi takaisin konsoliisi
|
||||
1. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
|
||||
1. Navigate to `[S:] SYSNAND VIRTUAL`
|
||||
1. Select `essentials.exefs`, then `Copy to 0:/gm9/out/`
|
||||
1. You should now have `essentials.exefs` in `/gm9/out/`
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## Boot-related issues on modded devices
|
||||
## Boot issues on devices with custom firmware
|
||||
|
||||
The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
|
||||
{: .notice--info}
|
||||
|
||||
### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
|
||||
### Power/notification light indicators
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>My device powers off when I try to turn it on, and/or the notification LED shows a color on boot</u></summary>
|
||||
|
||||
There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
|
||||
|
||||
|
|
@ -332,11 +476,15 @@ If the notification LED flashes:
|
|||
You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
|
||||
|
||||
If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### My device gets stuck on a black screen, with a static blue light
|
||||
{% capture compat %}
|
||||
<summary><u>My device gets stuck on a black screen with blue power light staying on</u></summary>
|
||||
|
||||
The steps below can be attempted in any order, but are listed from least to most time-consuming.
|
||||
|
||||
1. Power off your device, remove the SD card, re-insert it, then power on your device.
|
||||
1. Power off your device, eject the game cartridge if inserted, power on your device, then wait up to ten minutes. If your device boots within ten minutes, the issue has been fixed and is unlikely to reoccur
|
||||
1. Rename the `Nintendo 3DS` folder on your SD card to `Nintendo 3DS_BACKUP`, then attempt to boot. If your device successfully boots, there is some issue within your `Nintendo 3DS` folder. Try clearing HOME Menu extdata:
|
||||
+ Navigate to `/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/`
|
||||
|
|
@ -354,35 +502,48 @@ The steps below can be attempted in any order, but are listed from least to most
|
|||
+ If you were successful, the device will boot to an "update your system" screen
|
||||
1. Follow the [CTRTransfer](ctrtransfer) guide
|
||||
1. For further support, ask for help at [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### My device boots to an error screen
|
||||
### Error message on boot
|
||||
|
||||
#### "An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"</u></summary>
|
||||
|
||||
Your Luma3DS version is outdated. Download the latest release of [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### "An error has occurred. Hold down the POWER button to turn off the power..."
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..."</u></summary>
|
||||
|
||||
ARM11 exception handlers are disabled, or custom firmware is not installed. Try enabling ARM11 exception handlers:
|
||||
+ Power off your device
|
||||
+ Hold (Select)
|
||||
+ Power on your device, while still holding (Select)
|
||||
+ If the "Disable ARM11 exception handlers" box is checked, uncheck it
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Some other error
|
||||
|
||||
Please take a photo of the error and join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
|
||||
### Blue "Bootrom Error" screen
|
||||
{% capture compat %}
|
||||
<summary><u>Blue "BOOTROM ERROR" screen</u></summary>
|
||||
|
||||
Your device is likely hard-bricked. You will need to buy an ntrboot flashcart to reinstall boot9strap in order to attempt to fix your device. This may also indicate a hardware issue that cannot be fixed. In any case, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
+ It is also possible that someone has set a boot-time splash screen that just looks like a brick. Try leaving your device powered on, waiting on the blue screen, for five minutes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary><u>Some other error</u></summary>
|
||||
|
||||
## Functionality-related issues on modded devices
|
||||
Please take a photo of the error and join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### DSi / DS functionality is broken or has been replaced with Flipnote Studio
|
||||
## Software issues on devices with custom firmware
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DSi / DS functionality is broken or has been replaced with Flipnote Studio</u></summary>
|
||||
|
||||
1. Download the latest release of [TWLFix-CFW](https://github.com/MechanicalDragon0687/TWLFix-CFW/releases/latest) (the `.3dsx` file)
|
||||
1. Sammuta konsolisi
|
||||
|
|
@ -396,20 +557,29 @@ Your device is likely hard-bricked. You will need to buy an ntrboot flashcart to
|
|||
1. Perform a System Update by going to System Settings, then "Other Settings", then going all the way to the right and using "System Update"
|
||||
+ The update will see that the essential TWL titles have been uninstalled, and will redownload and reinstall them
|
||||
1. Once the update is complete, tap "OK" to reboot the device
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### GBA Virtual Console and/or Safe Mode functionality is broken
|
||||
{% capture compat %}
|
||||
<summary><u>GBA Virtual Console and/or Safe Mode functionality is broken</u></summary>
|
||||
|
||||
Your device is running Luma3DS/AuReiNand 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your device to a modern custom firmware environment.
|
||||
Your device is running Luma3DS 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your device to a modern custom firmware environment.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Extended memory mode games are broken
|
||||
{% capture compat %}
|
||||
<summary><u>Extended memory mode games (Pokemon Sun/Moon, Smash, etc.) don't work</u></summary>
|
||||
|
||||
This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will need to system format your device to fix this issue.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## Other troubleshooting
|
||||
|
||||
### Clear HOME Menu extdata
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu extdata</u></summary>
|
||||
|
||||
1. Sammuta konsolisi
|
||||
1. Aseta SD-korttisi tietokoneeseesi
|
||||
|
|
@ -422,8 +592,11 @@ This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will n
|
|||
+ **KOR Region**: `000000A9`
|
||||
+ **TWN Region**: `000000B1`
|
||||
1. Aseta SD-korttisi takaisin konsoliisi
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Clear HOME Menu theme data
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu theme data</u></summary>
|
||||
|
||||
1. Sammuta konsolisi
|
||||
1. Aseta SD-korttisi tietokoneeseesi
|
||||
|
|
@ -433,3 +606,6 @@ This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will n
|
|||
+ **JPN Region**: `000002cc`
|
||||
+ **USA Region**: `000002cd`
|
||||
1. Aseta SD-korttisi takaisin konsoliisi
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@ The purpose of this section is to check whether built-in DS mode applications wi
|
|||
+ If your console displays the Japanese version of Flipnote Studio, a black screen, or an error message, the test has failed
|
||||
1. Sammuta konsolisi
|
||||
|
||||
If either of these tests has failed, DS mode, DS Download Play, and/or DS Connection Settings may be inaccessible once CFW is uninstalled! You should [fix DS mode](troubleshooting#dsi--ds-functionality-is-broken-or-has-been-replaced-with-flipnote-studio) before continuing.
|
||||
If either of these tests has failed, DS mode, DS Download Play, and/or DS Connection Settings may be inaccessible once CFW is uninstalled! You should [fix DS mode](troubleshooting#software-issues-on-devices-with-custom-firmware) before continuing.
|
||||
{: .notice--warning}
|
||||
|
||||
#### Section III - Safety Test
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ Pour toutes les étapes de cette section, remplacez tous les fichiers existants
|
|||
1. Votre console va redémarrer dans la configuration de Luma3DS
|
||||
+ 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 get a black screen, [follow this troubleshooting guide](troubleshooting#boot-related-issues-on-modded-devices)
|
||||
+ If you get a black screen, [follow this troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware)
|
||||
1. Appuyez sur (Start) pour enregistrer les modifications et redémarrer
|
||||
|
||||
___
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ Il s'agit d'une section complémentaire pour vérifier si votre console possède
|
|||
|
||||
Si votre console possède déjà un custom firmware basé sur arm9loaderhax ou boot9strap, vous devrez suivre les instructions indiquées pour mettre à jour votre configuration vers une configuration moderne.
|
||||
|
||||
If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#clear-home-menu-extdata), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
|
||||
If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#other-troubleshooting), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
|
||||
{: .notice--info}
|
||||
|
||||
### Instructions
|
||||
|
|
|
|||
|
|
@ -14,79 +14,173 @@ title: "FAQ"
|
|||
|
||||
## Pre-Installation FAQ
|
||||
|
||||
#### **Q:** *I am on the latest system version. Is my device hackable without any external hardware?*
|
||||
**A:** Yes! The latest firmware (11.16.0) has a free method for getting CFW named [Seedminer](seedminer).
|
||||
{% capture compat %}
|
||||
<summary><u>I am on the latest system version. Is my device hackable without any external hardware?</u></summary>
|
||||
|
||||
#### **Q:** *What devices is this guide compatible with?*
|
||||
**A:** The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. If your system version string displays as "0.0.0-0", then you may have a developer unit.
|
||||
Yes! The latest firmware (11.16.0) has a free method for getting CFW named [Seedminer](seedminer).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How risky is hacking my console?*
|
||||
**A:** Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
{% capture compat %}
|
||||
<summary><u>What devices is this guide compatible with?</u></summary>
|
||||
|
||||
#### **Q:** *Can I run awesome homebrew and emulators with this?*
|
||||
**A:** Yes! This guide will install a few useful homebrew applications, including [Universal-Updater](https://github.com/Universal-Team/Universal-Updater/releases/latest), which acts as a homebrew app store.
|
||||
The instructions are the same for all retail 3DS, 3DS XL, 2DS, New 3DS, New 3DS XL, and New 2DS XL devices. If your system version string displays as "0.0.0-0", then you may have a developer unit.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I use this to play games from other regions?*
|
||||
**A:** Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Some games may need to make use of Luma's [locale emulation feature](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) in order to work properly on out-of-region devices.
|
||||
{% capture compat %}
|
||||
<summary><u>How risky is hacking my console?</u></summary>
|
||||
|
||||
#### **Q:** *Will I lose any features if I install CFW?*
|
||||
**A:** No. Devices with custom firmware can still use the eShop and run physical cartridges as any other 3DS can.
|
||||
Bricks are now effectively impossible unless you are purposely trying to brick your device.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I keep my NNID?*
|
||||
**A:** Your NNID (if you have one) will not be affected by this guide. Devices with a region of KOR, CHN, or TWN do not have NNID functionality to begin with and are thus unaffected.
|
||||
{% capture compat %}
|
||||
<summary><u>Can I run awesome homebrew and emulators with this?</u></summary>
|
||||
|
||||
#### **Q:** *Will my 3DS be banned for having CFW?*
|
||||
**A:** There was a ban wave in May 2017 that banned CFW users from online play (eShop access, NNIDs, and Nintendo Accounts were unaffected), seemingly at random. A ban wave at such a scale has not been seen since. That being said, we don't know what Nintendo may have in store in the future. At this time, we don't think that bans are something that you need to worry about.
|
||||
Yes! This guide will install a few useful homebrew applications, including [Universal-Updater](https://github.com/Universal-Team/Universal-Updater/releases/latest), which acts as a homebrew app store.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I do this without a computer (e.g. an Android phone)?*
|
||||
**A:** All you need is the ability to put files on a compatible SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Can I use this to play games from other regions?</u></summary>
|
||||
|
||||
#### **Q:** *What size SD card can I use?*
|
||||
**A:** You will need at least 1.5GB of free SD card space to follow this guide in its entirety. While the 3DS is officially compatible with SD cards up to 32GB, larger SD cards can be used if they are manually re-formatted as FAT32. It is not recommended to use SD cards greater than 128GB due to known issues with GBA graphics and custom themes.
|
||||
Yes; Luma3DS will automatically ignore the region check for cartridges and installed titles. Some games may need to make use of Luma's [locale emulation feature](https://github.com/LumaTeam/Luma3DS/wiki/Optional-features) in order to work properly on out-of-region devices.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *I heard about this thing I have to pay for (Gateway, Sky3DS, ntrboot, R4, etc). Is that something I need?*
|
||||
**A:** No. Custom firmware can be installed for free on the latest firmware without any hardware devices. In fact, 3DS-mode flashcarts like Gateway and Sky3DS are not recommended because they are obsolete and may carry ban or brick risk.
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose any features if I install CFW?</u></summary>
|
||||
|
||||
#### **Q:** *What's the difference between custom firmware and homebrew access?*
|
||||
**A:** Historically, the 3DS used to have userland homebrew access through older exploits like ninjhax. The level of system access granted with userland allowed you to run basic homebrew and emulators but did not allow you to (easily) modify games or dump cartridges. It was also a lot less stable, with homebrew often ungracefully crashing and requiring a full reboot. Custom firmware grants a far greater level of system access while also being more stable than homebrew-only entrypoints.
|
||||
No. Devices with custom firmware can still use the eShop and run physical cartridges as any other 3DS can.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I keep my NNID?</u></summary>
|
||||
|
||||
Your NNID (if you have one) will not be affected by this guide. Devices with a region of KOR, CHN, or TWN do not have NNID functionality to begin with and are thus unaffected.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will my 3DS be banned for having CFW?</u></summary>
|
||||
|
||||
There was a ban wave in May 2017 that banned CFW users from online play (eShop access, NNIDs, and Nintendo Accounts were unaffected), seemingly at random. A ban wave at such a scale has not been seen since. That being said, we don't know what Nintendo may have in store in the future. At this time, we don't think that bans are something that you need to worry about.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Can I do this without a computer (e.g. an Android phone)?</u></summary>
|
||||
|
||||
Yes! All you need is the ability to put files on a compatible SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What size SD card can I use?</u></summary>
|
||||
|
||||
You will need at least 1.5GB of free SD card space to follow this guide in its entirety. While the 3DS is officially compatible with SD cards up to 32GB, larger SD cards can be used if they are manually re-formatted as FAT32. It is not recommended to use SD cards greater than 128GB due to known issues with GBA graphics and custom themes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>I heard about this thing I have to pay for (Gateway, Sky3DS, ntrboot, R4, etc). Is that something I need?</u></summary>
|
||||
|
||||
No. Custom firmware can be installed for free on the latest firmware without any hardware devices. In fact, 3DS-mode flashcarts like Gateway and Sky3DS are not recommended because they are obsolete and may carry ban or brick risk.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>What's the difference between custom firmware and homebrew?</u></summary>
|
||||
|
||||
Historically, the 3DS used to have userland homebrew access through older exploits like ninjhax. The level of system access granted with userland allowed you to run basic homebrew and emulators but did not allow you to (easily) modify games or dump cartridges. It was also a lot less stable, with homebrew often ungracefully crashing and requiring a full reboot. Custom firmware grants a far greater level of system access while also being more stable than homebrew-only entrypoints.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Post-Installation FAQ
|
||||
|
||||
#### **Q:** *Is it safe to update my 3DS to the latest version with CFW?*
|
||||
**A:** If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. There have been updates in the past that have resulted in Luma3DS crashing on boot, so it is a good idea to wait a couple of hours to ensure that the latest update will not temporarily render the device unusable until Luma3DS is updated. System updates can be performed the same way as they are on a stock 3DS: through System Settings, Safe Mode, or the update prompt when the update is automatically downloaded.
|
||||
{% capture compat %}
|
||||
<summary><u>Is it safe to update my 3DS to the latest version with CFW?</u></summary>
|
||||
|
||||
#### **Q:** *How do I upgrade my SD card?*
|
||||
**A:** Copy and paste your SD card contents to a new SD card formatted as FAT32. For 128GB cards, an allocation size of 65536 is recommended. SD cards larger than 128GB are not recommended due to known issues with GBA graphics and custom themes.
|
||||
If you are using Luma3DS, your custom firmware loader (boot9strap) will *never* be removed when performing a system update. There have been updates in the past that have resulted in Luma3DS crashing on boot, so it is a good idea to wait a couple of hours to ensure that the latest update will not temporarily render the device unusable until Luma3DS is updated. System updates can be performed the same way as they are on a stock 3DS: through System Settings, Safe Mode, or the update prompt when the update is automatically downloaded.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Can I system transfer with CFW?*
|
||||
**A:** Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets for illegitimate titles (homebrew) will not transfer, but the titles can be made to reappear with [faketik](https://github.com/ihaveamac/faketik/releases/latest). Make sure that you do not perform a wireless transfer, as this will delete illegitimate titles. CFW will remain on both consoles.
|
||||
{% capture compat %}
|
||||
<summary><u>How do I upgrade my SD card?</u></summary>
|
||||
|
||||
#### **Q:** *How do I change the system language of a Japanese 3DS?*
|
||||
**A:** The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Note that this is very likely to break the Nintendo eShop on your device, which means you will be unable to update your games whether they are in-region or out-of-region.
|
||||
Copy and paste your SD card contents to a new SD card formatted as FAT32. For 128GB cards, an allocation size of 65536 is recommended. SD cards larger than 128GB are not recommended due to known issues with GBA graphics and custom themes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How do I update homebrew applications?*
|
||||
**A:** It depends on the format of the homebrew application. Generally speaking:
|
||||
{% capture compat %}
|
||||
<summary><u>Can I system transfer with CFW?</u></summary>
|
||||
|
||||
Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets for illegitimate titles (homebrew) will not transfer, but the titles can be made to reappear with [faketik](https://github.com/ihaveamac/faketik/releases/latest). Make sure that you do not perform a wireless transfer, as this will delete illegitimate titles. CFW will remain on both consoles.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I change the system language of a Japanese 3DS?</u></summary>
|
||||
|
||||
The only way to change the system language of a Japanese 3DS to a language other than Japanese is to perform a [region change](region-changing). Note that this is very likely to break the Nintendo eShop on your device, which means you will be unable to update your games whether they are in-region or out-of-region.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I update homebrew applications?</u></summary>
|
||||
|
||||
It depends on the format of the homebrew application. Generally speaking:
|
||||
|
||||
* Homebrew in **CIA format** can be updated by installing the new CIA, which will usually overwrite the old one. If the old CIA is not overwritten, you can delete the old one from Data Management as you would any other 3DS title.
|
||||
* Homebrew in **3DSX format** can be updated by replacing the 3DSX file in `/3ds/` with a fresh copy. If the homebrew application includes additional assets, you may need to place that folder somewhere else. Refer to the documentation of the homebrew application.
|
||||
* For updating Luma3DS, see [this page](restoring-updating-cfw). For updating GodMode9, see [this page](godmode9-usage#updating-godmode9).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *How do I update games from outside of my 3DS region?*
|
||||
**A:** You will need to [dump the updates](dumping-titles-and-game-cartridges) from a 3DS that has the updates installed. The Nintendo eShop only contains updates for the console's region (a Japanese 3DS will only have updates for Japanese games).
|
||||
{% capture compat %}
|
||||
<summary><u>How do I update my games?</u></summary>
|
||||
|
||||
#### **Q:** *Help! Something bad happened and now I cannot boot...*
|
||||
**A:** Please look at the [troubleshooting guide](troubleshooting). **Uninstalling CFW when your device is in an unbootable state is not recommended, as it is very likely to lead to a brick**.
|
||||
You can continue to download game updates from the Nintendo eShop, even after the 2023 shutdown.
|
||||
|
||||
If the game is not from the same region as the console, you will need to [dump the updates](dumping-titles-and-game-cartridges) from a 3DS that has the updates installed. The Nintendo eShop only contains updates for the console's region (a Japanese 3DS will only have updates for Japanese games).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Help! Something bad happened and my 3DS won't boot to HOME Menu...</u></summary>
|
||||
|
||||
Please look at the [troubleshooting guide](troubleshooting#boot-issues-on-devices-with-custom-firmware). **Uninstalling CFW when your device is in an unbootable state is not recommended, as it is very likely to lead to a brick**.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## menuhax / A9LH / Gateway FAQ
|
||||
|
||||
#### **Q:** *I modded my device x years ago. What should I do?*
|
||||
**A:** It is recommended that you upgrade your setup to a modern, boot9strap-based one. Follow the [Checking for CFW](checking-for-cfw) guide to see how to upgrade your setup.
|
||||
{% capture compat %}
|
||||
<summary><u>I modded my device (x) years ago, so it already has some sort of homebrew. What should I do?</u></summary>
|
||||
|
||||
#### **Q:** *My setup works for me. Why should I upgrade it?*
|
||||
**A:** The vast majority of modern homebrew (such as Checkpoint and BootNTR Selector) have only been tested on modern, boot9strap-based setups and may not work entirely (or at all) on older setups based on menuhax, A9LH, or Gateway. In addition, depending on your setup, you may be unable to safely update to the latest firmware. Modern, boot9strap-based setups allow for a greater level of system access than previous hacks, including the ability to dump your console's bootrom.
|
||||
It is recommended that you upgrade your setup to a modern, boot9strap-based one. Follow the [Checking for CFW](checking-for-cfw) guide to see how to upgrade your setup.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### **Q:** *Will I lose anything if I upgrade my setup?*
|
||||
**A:** Your old setup (including your EmuNAND, if you have one) can usually be directly migrated to boot9strap with no data loss. If you have data that is particularly important to you, it would be a good idea to make a decrypted backup of your save data before upgrading your setup with a tool like [JKSM](https://github.com/J-D-K/JKSM/releases/tag/12%2F20%2F2018).
|
||||
{% capture compat %}
|
||||
<summary><u>My setup works for me. Why should I upgrade it?</u></summary>
|
||||
|
||||
The vast majority of modern homebrew (such as Checkpoint and BootNTR Selector) have only been tested on modern, boot9strap-based setups and may not work entirely (or at all) on older setups based on menuhax, A9LH, or Gateway. In addition, depending on your setup, you may be unable to safely update to the latest firmware. Modern, boot9strap-based setups allow for a greater level of system access than previous hacks, including the ability to dump your console's bootrom.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Will I lose anything if I upgrade my setup?</u></summary>
|
||||
|
||||
Your old setup (including your EmuNAND, if you have one) can usually be directly migrated to boot9strap with no data loss. If you have data that is particularly important to you, it would be a good idea to make a decrypted backup of your save data before upgrading your setup with a tool like [JKSM](https://github.com/J-D-K/JKSM/releases/tag/12%2F20%2F2018).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>How do I move saves from an existing Gateway setup to a more modern setup?</u></summary>
|
||||
|
||||
#### **Q:** *How do I move saves from an existing Gateway setup to a more modern setup?*
|
||||
**A:** See [this thread](https://gbatemp.net/threads/425743/).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@ In this section, you will update your system to the latest version, which is saf
|
|||
+ Mettre à jour tout en ayant B9S + Luma (ce que vous avez) est sans danger
|
||||
+ La console peut afficher un message disant "Aucune mise à jour nécessaire" au lieu de faire une mise à jour. Ceci est normal si vous êtes déjà à jour ; continuez vers la section suivante
|
||||
+ If this gives you an error, set both your DNS settings and Proxy settings to "auto"
|
||||
+ If this still gives you an error, [follow this troubleshooting guide](troubleshooting#unable-to-update-device)
|
||||
+ If this still gives you an error, [follow this troubleshooting guide](troubleshooting#finalizing-setup)
|
||||
|
||||
#### Section III - Homebrew Launcher
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
|||
1. Lancez les Paramètres de la console
|
||||
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#dsiware-management-menu-crashes-without-showing-bb3-multihax-menu)
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#installing-boot9strap-fredtool)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Dump DSiWare"
|
||||
+ Your device will automatically reboot
|
||||
1. Éteignez votre 3DS
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ In this section, you will trigger the BannerBomb3 exploit using the DSiWare Mana
|
|||
1. Lancez les Paramètres de la console
|
||||
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
|
||||
+ Your device should show the BB3 multihax menu
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#dsiware-management-menu-crashes-without-showing-bb3-multihax-menu)
|
||||
+ If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#bannerbomb3)
|
||||
1. Use the D-Pad to navigate and press the (A) button to select "Install unSAFE_MODE"
|
||||
+ Votre console s'éteindra automatiquement
|
||||
|
||||
|
|
|
|||
|
|
@ -135,7 +135,7 @@ Pour identifier le Title ID d'un fichier `<TitleID>.gbavc.sav`, vous pouvez obte
|
|||
1. Sélectionnez "Backup Options"
|
||||
1. Sélectionnez "SysNAND Backup"
|
||||
1. Appuyez sur (A) pour confirmer
|
||||
+ Ce processus pendra du temps
|
||||
+ Ce processus prendra un certain temps
|
||||
+ Si une erreur apparaît, vérifiez que vous avez au moins 1,3 Go d'espace libre sur votre carte SD
|
||||
1. Appuyez sur (A) pour continuer
|
||||
1. Appuyez sur (B) pour revenir au menu principal
|
||||
|
|
@ -165,10 +165,9 @@ Pour identifier le Title ID d'un fichier `<TitleID>.gbavc.sav`, vous pouvez obte
|
|||
1. Insérez votre carte SD dans votre ordinateur
|
||||
1. Copier tous vos fichiers sur votre carte SD
|
||||
+ Assurez-vous de remplacer le fichier `boot.firm` sur votre carte SD avec le 'boot.firm' de votre sauvegarde
|
||||
1. Réinsérez votre carte SD dans votre 3DS
|
||||
1. Retirez la carte SD de votre ordinateur et réinsérez-là dans votre 3DS
|
||||
1. Appuyez sur (A) pour remonter votre carte SD
|
||||
1. Appuyez sur (Start) pour redémarrer
|
||||
1. If you get a black screen, [follow this troubleshooting guide](troubleshooting#ts_sys_down)
|
||||
|
||||
___
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ In this section, you will get the necessary details from your 3DS that are requi
|
|||
+ If you don't have a `Nintendo 3DS` folder, put your SD card into your 3DS and power it on so that the folder can be created
|
||||
1. Copy the name of the 32-letter folder you see directly inside Nintendo 3DS
|
||||
+ This 32-letter name is system-specific and will be different for each console
|
||||
+ If you see multiple 32-letter folders, follow [these instructions](troubleshooting#multiple-long-folder-names-in-nintendo-3ds-folder)
|
||||
+ If you see multiple 32-letter folders, follow [these instructions](troubleshooting#seedminer)
|
||||
+ Vous pouvez ignorer le dossier `private` si vous l'avez
|
||||
|
||||
![]({{ "/images/screenshots/seedminer/id0-example.png" | absolute_url }})
|
||||
|
|
|
|||
|
|
@ -2,37 +2,69 @@
|
|||
title: "Problèmes et Dépannage"
|
||||
---
|
||||
|
||||
{% include toc title="Table of Contents"%}
|
||||
|
||||
This page offers troubleshooting advice for commonly encountered issues. If you are unable to solve your issue with the advice on this page, please join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and describe your issue, including what you have already tried.
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary>Table of Contents</summary>
|
||||
|
||||
Used on multiple pages:
|
||||
* [SafeB9SInstaller](#issues-with-safeb9sinstaller)
|
||||
|
||||
Guide pages:
|
||||
* [Seedminer](#seedminer)
|
||||
* [BannerBomb3](#bannerbomb3)
|
||||
* [Installing boot9strap (USM)](#installing-boot9strap-usm)
|
||||
* [Installing boot9strap (Fredtool)](#installing-boot9strap-fredtool)
|
||||
* [Homebrew Launcher (PicHaxx)](#homebrew-launcher-pichaxx)
|
||||
* [Installing boot9strap (Soundhax)](#installing-boot9strap-soundhax)
|
||||
* [Installing boot9strap (SSLoth-Browser)](#installing-boot9strap-ssloth-browser)
|
||||
|
||||
* [Finalizing Setup](#finalizing-setup)
|
||||
|
||||
Issues after installation:
|
||||
* [Boot issues](#boot-issues-on-devices-with-custom-firmware)
|
||||
* [Software issues](#software-issues-on-devices-with-custom-firmware)
|
||||
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
{: .notice--info}
|
||||
|
||||
## Issues with SafeB9SInstaller
|
||||
|
||||
### SigHaxed FIRM was not installed! Check lower screen for more info.
|
||||
|
||||
#### SigHaxed FIRM - File not found
|
||||
{% capture compat %}
|
||||
<summary><u>SigHaxed FIRM - File not found</u></summary>
|
||||
|
||||
You are missing `boot9strap.firm` and `boot9strap.firm.sha` from the `boot9strap` folder, or the `boot9strap` folder is misnamed. Download the latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip), and place `boot9strap.firm` and `boot9strap.firm.sha` in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### SigHaxed FIRM - invalid FIRM
|
||||
{% capture compat %}
|
||||
<summary><u>SigHaxed FIRM - invalid FIRM</u></summary>
|
||||
|
||||
There is an issue with your `boot9strap.firm` and `boot9strap.firm.sha` files. Re-download the latest release of [boot9strap](https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip), and place `boot9strap.firm` and `boot9strap.firm.sha` in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Secret Sector - File not found
|
||||
{% capture compat %}
|
||||
<summary><u>Secret Sector - File not found</u></summary>
|
||||
|
||||
You are missing `secret_sector.bin` from the `boot9strap` folder, or the `boot9strap` folder is misnamed. Download [secret_sector.bin](magnet:?xt=urn:btih:15a3c97acf17d67af98ae8657cc66820cc58f655&dn=secret_sector.bin&tr=udp%3a%2f%2ftracker.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.lelux.fi%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.loadbt.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.moeking.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.monitorit4.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.ololosh.space%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.pomf.se%3a80%2fannounce&tr=udp%3a%2f%2ftracker.srv00.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.theoks.net%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.tiny-vps.com%3a6969%2fannounce&tr=udp%3a%2f%2fopen.tracker.cl%3a1337%2fannounce&tr=udp%3a%2f%2ftracker.zerobytes.xyz%3a1337%2fannounce&tr=udp%3a%2f%2ftracker1.bt.moack.co.kr%3a80%2fannounce&tr=udp%3a%2f%2fvibe.sleepyinternetfun.xyz%3a1738%2fannounce&tr=udp%3a%2f%2fwww.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a6969%2fannounce&tr=udp%3a%2f%2f9.rarbg.com%3a2810%2fannounce&tr=udp%3a%2f%2ftracker.opentrackr.org%3a1337%2fannounce&tr=udp%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fopenbittorrent.com%3a80%2fannounce) using a torrent client, and place it in the `boot9strap` folder.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Something else
|
||||
{% capture compat %}
|
||||
<summary><u>Something else</u></summary>
|
||||
|
||||
Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance, and describe the message that you see.
|
||||
|
||||
---
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Seedminer
|
||||
|
||||
### Multiple long folder names in Nintendo 3DS folder
|
||||
{% capture compat %}
|
||||
<summary><u>Multiple long folder names in Nintendo 3DS folder</u></summary>
|
||||
|
||||
![]({{ "/images/screenshots/multiple-id0.png" | absolute_url }})
|
||||
{: .notice--info}
|
||||
|
|
@ -49,98 +81,285 @@ This occurs when you use your SD card in multiple 3DS devices and is intended to
|
|||
+ This is your true ID0 that you will use in [Section II of Seedminer](seedminer#section-ii---seedminer)
|
||||
1. Delete the `Nintendo 3DS` folder
|
||||
1. Rename the `BACKUP_Nintendo 3DS` folder to `Nintendo 3DS`
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Bruteforce Movable skips to step 4
|
||||
{% capture compat %}
|
||||
<summary><u>Bruteforce Movable skips to step 4</u></summary>
|
||||
|
||||
The website has already mined your `movable.sed` using your friend code and ID0 combination. You can use the `movable.sed` that it provides you.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Important! You have been locked out of the automated part1 dumper system...
|
||||
{% capture compat %}
|
||||
<summary><u>Important! You have been locked out of the automated part1 dumper system...</u></summary>
|
||||
|
||||
Your friend code was blocked from using the friend code bot because your 3DS did not successfully friend the bot. Ensure your 3DS is properly connected to the Internet, then join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask to be unlocked.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### We were unable to successfully complete your bruteforce request. :`(
|
||||
{% capture compat %}
|
||||
<summary><u>We were unable to successfully complete your bruteforce request. :`(</u></summary>
|
||||
|
||||
The website has determined that your `movable.sed` cannot be brute-forced. Ensure that you gave the correct ID0 to the website. If your ID0 is correct, then you will be unable to use Seedminer and you will have to use an alternate method that will require additional games or hardware.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
## BannerBomb3
|
||||
|
||||
## Homebrew Launcher (PicHaxx)
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management menu crashes without showing BB3 multihax menu</u></summary>
|
||||
Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. If it is, then re-create it with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen).
|
||||
|
||||
### "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
Your `00000001.sav` and/or `otherapp.bin` files may be misplaced. Ensure that `00000001.sav` is in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data` and that `otherapp.bin` is on the root of your SD card.
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow [an alternate branch of Seedminer](homebrew-launcher-(pichaxx)). If Safe Mode doesn't work or you need assistance with this matter, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
If your files are in the correct locations, re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx), then place it in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`. Ensure that the file is named exactly `00000001.sav` and that you used your console's `movable.sed` to create it. Re-download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management menu does not crash</u></summary>
|
||||
|
||||
### "An exception occurred" or Errdisp when opening Picross
|
||||
`F00D43D5.bin` is missing from `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. Make sure that `Nintendo DSiWare` is correctly spelled and spaced. Uppercase/lowercase does not matter.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
Your device already has custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% capture compat %}
|
||||
<summary><u>DSiWare Management shows a question mark</u></summary>
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
There may be an issue with your `F00D43D5.bin` file (it may be corrupted or intended for the wrong 3DS). Re-create your `F00D43D5.bin` file with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen), ensuring that you use the `movable.sed` file for your console.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
There is an issue with your `otherapp.bin` file. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
## Installing boot9strap (USM)
|
||||
|
||||
### Game starts normally
|
||||
{% capture compat %}
|
||||
<summary><u>Safe Mode system update succeeds instead of giving error 003-1099</u></summary>
|
||||
|
||||
Your modified `00000001.sav` file may be misplaced, or you may have used the wrong `movable.sed` when creating it. Re-generate your `movable.sed` from [Bruteforce Movable](https://seedminer.hacks.guide), then re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx) and place the resulting file (`00000001.sav`) in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`.
|
||||
unSAFE_MODE is not installed. [Follow the instructions](installing-boot9strap-(usm)] to install it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary><u>Red screen after selecting "Detailed Setup"</u></summary>
|
||||
|
||||
## Installing boot9strap (Soundhax)
|
||||
The file `usm.bin` is missing or misplaced. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/download/v1.3/usm.bin) and place `usm.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
### Red/purple/pink and white screen after running Soundhax
|
||||
There is also a possibility that the console isn't reading your SD card. Make sure it is inserted and formatted correctly.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
If your device is not on those firmwares, it likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
|
||||
There is an issue with your `otherapp.bin` file (it is missing, misplaced, or corrupted). Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) and place it on the root of your SD card.
|
||||
|
||||
### "Could not play"
|
||||
|
||||
You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow [Seedminer](seedminer).
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to mount the SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
## Installing boot9strap (Fredtool)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Error on Fredtool Injector page</u></summary>
|
||||
|
||||
Ensure that your `movable.sed` and DSiWare backup come from the same console. A mismatch will result in an error.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to select "Haxxxxxxxxx!" because the BB3 multihax menu appears</u></summary>
|
||||
|
||||
You forgot to delete `F00D43D5.bin` from the SD card. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card and delete the `F00D43D5.bin` file.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"Haxxxxxxxxx!" does not appear</u></summary>
|
||||
|
||||
There is an issue with your `42383821.bin` file (it is incorrect, missing, misplaced, or corrupted). Re-create your files with the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website and ensure that you place the `42383821.bin` file from `output.zip` -> `hax` in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DS Connection Settings launches normally</u></summary>
|
||||
|
||||
`Haxxxxxxxxx!` was not copied from your SD card to your system memory.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Black screen when launching DS Connection Settings</u></summary>
|
||||
|
||||
Your DS Connection Settings application is broken, and you will need Homebrew Launcher access to fix this issue. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>SD card is grayed out in Flipnote</u></summary>
|
||||
|
||||
Flipnote may take a long time to index your card if you have a large SD card. Let it sit for a few minutes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Lenny face does not appear in SD card section</u></summary>
|
||||
|
||||
You did not copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Flipnote freezes</u></summary>
|
||||
|
||||
You may have accidentally touched the touch screen while in the modified Flipnote. Re-enter DS Connection Settings and try again, ensuring that you don't accidentally use the touchscreen.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Green screen after pasting</u></summary>
|
||||
|
||||
The file `boot.nds` is missing or misplaced. Download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>White screen after pasting</u></summary>
|
||||
There is an issue with your `boot.nds` file. Re-download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to open Luma3DS configuration menu after running B9STool</u></summary>
|
||||
|
||||
It is possible that boot9strap was not successfully installed. Follow section B of [this page](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Homebrew Launcher (PicHaxx)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
|
||||
|
||||
Your `00000001.sav` and/or `otherapp.bin` files may be misplaced. Ensure that `00000001.sav` is in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data` and that `otherapp.bin` is on the root of your SD card.
|
||||
|
||||
If your files are in the correct locations, re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx), then place it in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`. Ensure that the file is named exactly `00000001.sav` and that you used your console's `movable.sed` to create it. Re-download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" or Errdisp when opening Picross</u></summary>
|
||||
|
||||
Your device already has custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `otherapp.bin` file. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/latest), place the `.bin` file relevant to your console from the `otherapps_with_CfgS` folder to the root of your SD card, and rename it to `otherapp.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Game starts normally</u></summary>
|
||||
|
||||
Your modified `00000001.sav` file may be misplaced, or you may have used the wrong `movable.sed` when creating it. Re-generate your `movable.sed` from [Bruteforce Movable](https://seedminer.hacks.guide), then re-create the save using the [PicHaxx Save Tool](https://3dstools.nhnarwhal.com/#/pichaxx) and place the resulting file (`00000001.sav`) in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `title` -> `00040000` -> `0017c100` -> `data`.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Installing boot9strap (Soundhax)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Soundhax</u></summary>
|
||||
|
||||
If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from [here](https://github.com/TuxSH/universal-otherapp/releases/latest).
|
||||
|
||||
If your device is not on those firmwares, it likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `otherapp.bin` file (it is missing, misplaced, or corrupted). Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) and place it on the root of your SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"Could not play"</u></summary>
|
||||
|
||||
You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow [Seedminer](seedminer).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
## Installing boot9strap (SSLoth-Browser)
|
||||
|
||||
### Red/purple/pink and white screen after running browserhax
|
||||
{% capture compat %}
|
||||
<summary><u>Red/purple/pink and white screen after running Browserhax</u></summary>
|
||||
|
||||
This likely indicates that you already have custom firmware. You should [check for CFW](checking-for-cfw).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
|
||||
|
||||
The file `arm11code.bin` is missing or misplaced. Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place `otherapp.bin` on the root of your SD card and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An error has occurred, forcing the software to close..." (white message box)
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
|
||||
|
||||
There is an issue with your `arm11code.bin` file. Download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place `otherapp.bin` on the root of your SD card and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Opening the browserhax QR code or URL crashes
|
||||
{% capture compat %}
|
||||
<summary><u>Opening the browserhax QR code or URL crashes</u></summary>
|
||||
|
||||
Browser based exploits (such as this one) are often unstable and crash frequently, but they can sometimes be fixed by doing the following steps.
|
||||
|
||||
1. Launch the browser, then launch the browser settings
|
||||
1. Scroll to the bottom and Initialize Savedata (it also may be called Clear All Save Data)
|
||||
1. Try the exploit again
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Opening the browser prompts for a system update instead
|
||||
{% capture compat %}
|
||||
<summary><u>System Update prompt when opening browser</u></summary>
|
||||
|
||||
The SSLoth proxy was incorrectly configured. Re-do the SSLoth section on the page.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Error 032-0420 when trying to open the browser
|
||||
{% capture compat %}
|
||||
<summary><u>Error 032-0420 when opening browser</u></summary>
|
||||
|
||||
Follow these steps in order:
|
||||
|
||||
|
|
@ -157,126 +376,47 @@ Follow these steps in order:
|
|||
1. If prompted about a system update, press OK
|
||||
+ This won't actually update the system
|
||||
1. Start again from [Section II](installing-boot9strap-(ssloth-browser).html#section-ii---ssloth)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Frozen on "Doing agbhax..."
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>Frozen on "Doing agbhax..."</u></summary>
|
||||
There may be an issue with your `arm11code.bin` file. Re-download the latest release of [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest), place it on the root of your SD card, and rename it to `arm11code.bin`. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
If you have a Taiwanese unit (with a T in the version string, ie. 11.3.0-##T), you will not be able to follow these instructions, and you will need to update your console and follow [Seedminer](seedminer) instead.
|
||||
|
||||
If you have a Mainland Chinese unit (with a C in the version string, ie. 11.3.0-##C), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "PrepareArm9ForTwl returned error c8804631!"
|
||||
{% capture compat %}
|
||||
<summary><u>"PrepareArm9ForTwl returned error c8804631!"</u></summary>
|
||||
|
||||
You will need to follow an alternate method. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Failed to mount the SD card!
|
||||
{% capture compat %}
|
||||
<summary><u>Failed to mount the SD card!</u></summary>
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## BannerBomb3
|
||||
|
||||
### DSiWare Management menu crashes without showing BB3 multihax menu
|
||||
|
||||
Ensure that `F00D43D5.bin` is the only file in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. If it is, then re-create it with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen).
|
||||
|
||||
Also, ensure that `bb3.bin` is on the root of the SD card. If it is missing, then download the latest release of [Bannerbomb3](https://github.com/lifehackerhansol/Bannerbomb3/releases/download/v3.0-lhs1/bb3.bin) (direct download), and copy the `bb3.bin` file to the root of your SD card.
|
||||
|
||||
If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow [an alternate branch of Seedminer](homebrew-launcher-(pichaxx)). If Safe Mode doesn't work or you need assistance with this matter, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
|
||||
|
||||
### DSiWare Management menu does not crash
|
||||
|
||||
`F00D43D5.bin` is missing from `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`. Make sure that `Nintendo DSiWare` is correctly spelled and spaced. Uppercase/lowercase does not matter.
|
||||
|
||||
### DSiWare Management shows a question mark
|
||||
|
||||
There may be an issue with your `F00D43D5.bin` file (it may be corrupted or intended for the wrong 3DS). Re-create your `F00D43D5.bin` file with the [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen), ensuring that you use the `movable.sed` file for your console.
|
||||
|
||||
---
|
||||
|
||||
## Installing boot9strap (USM)
|
||||
|
||||
### Update doesn't fail with error code `003-1099`
|
||||
|
||||
unSAFE_MODE is not installed. Follow the instructions on your page to install unSAFE_MODE again.
|
||||
|
||||
### Red screen when selecting detailed setup
|
||||
|
||||
The file `usm.bin` is missing or misplaced. Download the latest release of [unSAFE_MODE](https://github.com/zoogie/unSAFE_MODE/releases/download/v1.3/usm.bin) and place `usm.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
There is also a possibility that the console isn't reading your SD card. Make sure it is inserted and formatted correctly.
|
||||
|
||||
### Failed to open SafeB9SInstaller.bin
|
||||
|
||||
The file `SafeB9SInstaller.bin` is missing or misplaced. Download the latest release of [SafeB9SInstaller](https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip), extract it, and place `SafeB9SInstaller.bin` on the root of your SD card. Do not add the `.bin` extension if you do not already see it.
|
||||
|
||||
### Failed to mount the SD card!
|
||||
|
||||
Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.
|
||||
|
||||
If this is unsuccessful, try using another SD card.
|
||||
|
||||
---
|
||||
|
||||
## Installing boot9strap (Fredtool)
|
||||
|
||||
### Error on Fredtool Injector page
|
||||
|
||||
Ensure that your `movable.sed` and DSiWare backup come from the same console. A mismatch will result in an error.
|
||||
|
||||
### Unable to select the "Haxxxxxxxxx!" title because of the BB3 multihax menu
|
||||
|
||||
You forgot to delete `F00D43D5.bin` from the SD card. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` on your SD card and delete the `F00D43D5.bin` file.
|
||||
|
||||
### "Haxxxxxxxxx!" does not appear
|
||||
|
||||
There is an issue with your `42383821.bin` file (it is incorrect, missing, misplaced, or corrupted). Re-create your files with the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website and ensure that you place the `42383821.bin` file from `output.zip` -> `hax` in `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`.
|
||||
|
||||
### DS Connection Settings launches normally
|
||||
|
||||
`Haxxxxxxxxx!` was not copied from your SD card to your system memory.
|
||||
|
||||
### Black screen when launching DS Connection Settings
|
||||
|
||||
Your DS Connection Settings application is broken, and you will need Homebrew Launcher access to fix this issue. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
|
||||
### SD card is grayed out
|
||||
|
||||
Flipnote may take a long time to index your card if you have a large SD card. Let it sit for a few minutes.
|
||||
|
||||
### Lenny face does not appear
|
||||
|
||||
You did not copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card.
|
||||
|
||||
### Flipnote is frozen
|
||||
|
||||
You may have accidentally touched the touch screen while in the modified Flipnote. Re-enter DS Connection Settings and try again, ensuring that you don't accidentally use the touchscreen.
|
||||
|
||||
### Green screen after pasting
|
||||
|
||||
The file `boot.nds` is missing or misplaced. Download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
|
||||
### White screen after pasting
|
||||
|
||||
There is an issue with your `boot.nds` file. Re-download the latest release of [b9stool](https://github.com/zoogie/b9sTool/releases/latest) and place `boot.nds` on the root of your SD card, replacing the existing one.
|
||||
|
||||
### Unable to open Luma3DS configuration menu after running b9stool
|
||||
|
||||
It is possible that boot9strap was not successfully installed. Follow section B of [this page](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md).
|
||||
|
||||
---
|
||||
|
||||
## Finalizing Setup
|
||||
|
||||
### Unable to update device
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to update device</u></summary>
|
||||
|
||||
The steps below can be attempted in any order, but are listed from easiest to hardest to perform.
|
||||
|
||||
|
|
@ -289,27 +429,41 @@ The steps below can be attempted in any order, but are listed from easiest to ha
|
|||
1. Les serveurs de Nintendo sont peut-être en panne ; Réessayez plus tard
|
||||
1. Si vous recevez toujours un message d'erreur, [suivez CTRTransfer](ctrtransfer), puis réessayez
|
||||
1. For further support (in English), join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Unable to enter Rosalina due to broken button(s)
|
||||
{% capture compat %}
|
||||
<summary><u>Unable to enter Rosalina menu due to broken Left Shoulder / Down D-Pad / Select button(s)</u></summary>
|
||||
|
||||
Download this [alternate config.ini](https://cdn.discordapp.com/attachments/196635695958196224/982798396265988186/config.ini) and place it in `/luma/`. This will change the Rosalina key combination to (X) + (Y).
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "An exception occurred" after trying to launch Homebrew Launcher via Download Play
|
||||
{% capture compat %}
|
||||
<summary><u>"An exception occurred" after trying to launch Homebrew Launcher from Download Play</u></summary>
|
||||
|
||||
There is an issue with your `boot.3dsx` file (it is missing, misplaced, or corrupted). Download the latest release of [the Homebrew Launcher](https://github.com/devkitPro/3ds-hbmenu/releases/latest) and place `boot.3dsx` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### "Scripts directory not found" in GodMode9
|
||||
{% capture compat %}
|
||||
<summary><u>"Scripts directory not found" in GodMode9</u></summary>
|
||||
|
||||
You did not copy the `gm9` folder from the GodMode9 `.zip` to the root of your SD card. Download the latest release of [GodMode9](https://github.com/d0k3/GodMode9/releases/latest) and place the `gm9` folder on the root of your SD card, merging it with the existing one.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## Boot-related issues on modded devices
|
||||
## Boot issues on devices with custom firmware
|
||||
|
||||
The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.
|
||||
{: .notice--info}
|
||||
|
||||
### My device powers off when I try to turn it on, and/or the notification LED shows a color on boot
|
||||
### Power/notification light indicators
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>My device powers off when I try to turn it on, and/or the notification LED shows a color on boot</u></summary>
|
||||
|
||||
There is an issue with your `boot.firm` file. If you're running [boot9strap 1.4](https://github.com/SciresM/boot9strap/releases/tag/1.4), your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your `boot.firm` file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.
|
||||
|
||||
|
|
@ -322,11 +476,15 @@ If the notification LED flashes:
|
|||
You can get a new `boot.firm` file by downloading the [latest release of Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extracting it, and placing `boot.firm` on the root of your SD card. If your `boot.firm` file is consistently being detected as corrupted, you may want to check your SD card for errors ([Windows](h2testw-(windows)), [Linux](f3-(linux)), or [macOS](f3xswift-(mac))). Also, note that the 3DS tends to have issues with files extracted using WinRAR.
|
||||
|
||||
If you hear a "popping sound", potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### My device gets stuck on a black screen, with a static blue light
|
||||
{% capture compat %}
|
||||
<summary><u>My device gets stuck on a black screen with blue power light staying on</u></summary>
|
||||
|
||||
The steps below can be attempted in any order, but are listed from least to most time-consuming.
|
||||
|
||||
1. Power off your device, remove the SD card, re-insert it, then power on your device.
|
||||
1. Power off your device, eject the game cartridge if inserted, power on your device, then wait up to ten minutes. If your device boots within ten minutes, the issue has been fixed and is unlikely to reoccur
|
||||
1. Rename the `Nintendo 3DS` folder on your SD card to `Nintendo 3DS_BACKUP`, then attempt to boot. If your device successfully boots, there is some issue within your `Nintendo 3DS` folder. Try clearing HOME Menu extdata:
|
||||
+ Navigate to `/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/`
|
||||
|
|
@ -344,35 +502,48 @@ The steps below can be attempted in any order, but are listed from least to most
|
|||
+ If you were successful, the device will boot to an "update your system" screen
|
||||
1. Follow the [CTRTransfer](ctrtransfer) guide
|
||||
1. For further support, ask for help at [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp)
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### My device boots to an error screen
|
||||
### Error message on boot
|
||||
|
||||
#### "An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"</u></summary>
|
||||
|
||||
Your Luma3DS version is outdated. Download the latest release of [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) and place `boot.firm` on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### "An error has occurred. Hold down the POWER button to turn off the power..."
|
||||
{% capture compat %}
|
||||
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..."</u></summary>
|
||||
|
||||
ARM11 exception handlers are disabled, or custom firmware is not installed. Try enabling ARM11 exception handlers:
|
||||
+ Éteignez votre console
|
||||
+ Hold (Select)
|
||||
+ Power on your device, while still holding (Select)
|
||||
+ If the "Disable ARM11 exception handlers" box is checked, uncheck it
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
#### Some other error
|
||||
|
||||
Please take a photo of the error and join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
|
||||
### Blue "Bootrom Error" screen
|
||||
{% capture compat %}
|
||||
<summary><u>Blue "BOOTROM ERROR" screen</u></summary>
|
||||
|
||||
Your device is likely hard-bricked. You will need to buy an ntrboot flashcart to reinstall boot9strap in order to attempt to fix your device. This may also indicate a hardware issue that cannot be fixed. In any case, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
+ It is also possible that someone has set a boot-time splash screen that just looks like a brick. Try leaving your device powered on, waiting on the blue screen, for five minutes.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
{% capture compat %}
|
||||
<summary><u>Some other error</u></summary>
|
||||
|
||||
## Functionality-related issues on modded devices
|
||||
Please take a photo of the error and join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### DSi / DS functionality is broken or has been replaced with Flipnote Studio
|
||||
## Software issues on devices with custom firmware
|
||||
|
||||
{% capture compat %}
|
||||
<summary><u>DSi / DS functionality is broken or has been replaced with Flipnote Studio</u></summary>
|
||||
|
||||
1. Download the latest release of [TWLFix-CFW](https://github.com/MechanicalDragon0687/TWLFix-CFW/releases/latest) (the `.3dsx` file)
|
||||
1. Éteignez votre 3DS
|
||||
|
|
@ -386,20 +557,29 @@ Your device is likely hard-bricked. You will need to buy an ntrboot flashcart to
|
|||
1. Effectuez une Mise à jour du Système en vous rendant dans les Paramètres de la console, puis "Autres paramètres", puis tout à droite sur l'option "Mise à jour du Système"
|
||||
+ Le processus de mise à jour verra que les titres TWL essentiels ont été désinstallés, et va les re-télécharger et les réinstaller
|
||||
1. Une fois la mise à jour terminée, appuyez sur "OK" pour redémarrer la console
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### GBA Virtual Console and/or Safe Mode functionality is broken
|
||||
{% capture compat %}
|
||||
<summary><u>GBA Virtual Console and/or Safe Mode functionality is broken</u></summary>
|
||||
|
||||
Your device is running Luma3DS/AuReiNand 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your device to a modern custom firmware environment.
|
||||
Your device is running Luma3DS 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your device to a modern custom firmware environment.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Extended memory mode games are broken
|
||||
{% capture compat %}
|
||||
<summary><u>Extended memory mode games (Pokemon Sun/Moon, Smash, etc.) don't work</u></summary>
|
||||
|
||||
This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will need to system format your device to fix this issue.
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
---
|
||||
|
||||
## Other troubleshooting
|
||||
|
||||
### Clear HOME Menu extdata
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu extdata</u></summary>
|
||||
|
||||
1. Éteignez votre 3DS
|
||||
1. Insérez votre carte SD dans votre ordinateur
|
||||
|
|
@ -412,8 +592,11 @@ This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will n
|
|||
+ **Région KOR** : `000000A9`
|
||||
+ **Région TWN** : `000000B1`
|
||||
1. Réinsérez votre carte SD dans votre 3DS
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
### Clear HOME Menu theme data
|
||||
{% capture compat %}
|
||||
<summary><u>Clear HOME Menu theme data</u></summary>
|
||||
|
||||
1. Éteignez votre 3DS
|
||||
1. Insérez votre carte SD dans votre ordinateur
|
||||
|
|
@ -423,3 +606,6 @@ This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will n
|
|||
+ **JPN Region**: `000002cc`
|
||||
+ **USA Region**: `000002cd`
|
||||
1. Réinsérez votre carte SD dans votre 3DS
|
||||
{% endcapture %}
|
||||
<details>{{ compat | markdownify }}</details>
|
||||
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@ Le but de cette section est de vérifier si les applications intégrées en mode
|
|||
+ Si votre console affiche la version japonaise de Flipnote Studio, un écran noir ou un message d'erreur, le test a échoué
|
||||
1. Éteignez votre 3DS
|
||||
|
||||
Si l'un de ces tests a échoué, le mode DS, le Mode téléchargement DS, et/ou les paramètres de Connexions Nintendo DS peuvent être inaccessibles une fois le CFW désinstallé ! You should [fix DS mode](troubleshooting#dsi--ds-functionality-is-broken-or-has-been-replaced-with-flipnote-studio) before continuing.
|
||||
Si l'un de ces tests a échoué, le mode DS, le Mode téléchargement DS, et/ou les paramètres de Connexions Nintendo DS peuvent être inaccessibles une fois le CFW désinstallé ! You should [fix DS mode](troubleshooting#software-issues-on-devices-with-custom-firmware) before continuing.
|
||||
{: .notice--warning}
|
||||
|
||||
#### Section III - Tests de sécurité
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show more
Loading…
Reference in a new issue