465294c481
* New translations troubleshooting.txt (French) * New translations troubleshooting.txt (Greek) * New translations troubleshooting.txt (Romanian) * New translations troubleshooting.txt (Spanish) * New translations troubleshooting.txt (Arabic) * New translations troubleshooting.txt (Bulgarian) * New translations troubleshooting.txt (Catalan) * New translations troubleshooting.txt (Czech) * New translations troubleshooting.txt (German) * New translations troubleshooting.txt (Finnish) * New translations troubleshooting.txt (Hebrew) * New translations troubleshooting.txt (Hungarian) * New translations troubleshooting.txt (Italian) * New translations troubleshooting.txt (Japanese) * New translations troubleshooting.txt (Korean) * New translations troubleshooting.txt (Dutch) * New translations troubleshooting.txt (Norwegian) * New translations troubleshooting.txt (Polish) * New translations troubleshooting.txt (Portuguese) * New translations troubleshooting.txt (Russian) * New translations troubleshooting.txt (Swedish) * New translations troubleshooting.txt (Turkish) * New translations troubleshooting.txt (Ukrainian) * New translations troubleshooting.txt (Chinese Simplified) * New translations troubleshooting.txt (Chinese Traditional) * New translations troubleshooting.txt (Vietnamese) * New translations troubleshooting.txt (Portuguese, Brazilian) * New translations troubleshooting.txt (Indonesian) * New translations troubleshooting.txt (Thai) * New translations troubleshooting.txt (Croatian) * New translations troubleshooting.txt (Malay) * New translations troubleshooting.txt (Pirate English)
611 lines
34 KiB
Text
611 lines
34 KiB
Text
---
|
|
title: "Проблемы и их решения"
|
|
---
|
|
|
|
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.
|
|
|
|
{% 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>
|
|
|
|
{% 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>
|
|
|
|
{% 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>
|
|
|
|
{% 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
|
|
|
|
{% capture compat %}
|
|
<summary><u>Multiple long folder names in Nintendo 3DS folder</u></summary>
|
|
|
|
![]({{ "/images/screenshots/multiple-id0.png" | absolute_url }})
|
|
{: .notice--info}
|
|
|
|
This occurs when you use your SD card in multiple 3DS devices and is intended to prevent inadvertently merging data that would not be valid on other devices. To figure out which long folder name is correct for your 3DS, follow these instructions:
|
|
|
|
1. Rename the `Nintendo 3DS` folder to `BACKUP_Nintendo 3DS`
|
|
1. Reinsert your SD card into your device and power on your device
|
|
1. Wait for the device to generate the SD card data
|
|
+ Your applications will have disappeared. This is normal and will be resolved shortly
|
|
1. Power off your device and reinsert your SD card into your computer
|
|
1. Перейдите в папку `Nintendo 3DS` на SD-карте
|
|
1. Copy the 32 character long name of the folder you see
|
|
+ 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>
|
|
|
|
{% 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>
|
|
|
|
{% 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>
|
|
|
|
{% 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
|
|
|
|
{% 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).
|
|
|
|
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.
|
|
{% endcapture %}
|
|
<details>{{ compat | markdownify }}</details>
|
|
|
|
{% capture compat %}
|
|
<summary><u>DSiWare Management menu does not crash</u></summary>
|
|
|
|
`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>
|
|
|
|
{% capture compat %}
|
|
<summary><u>DSiWare Management shows a question mark</u></summary>
|
|
|
|
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>
|
|
|
|
## Installing boot9strap (USM)
|
|
|
|
{% capture compat %}
|
|
<summary><u>Safe Mode system update succeeds instead of giving error 003-1099</u></summary>
|
|
|
|
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>
|
|
|
|
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.
|
|
{% 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 (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)
|
|
|
|
{% 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>
|
|
|
|
{% 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>
|
|
|
|
|
|
{% 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>
|
|
|
|
{% 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>
|
|
|
|
{% 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>
|
|
|
|
{% capture compat %}
|
|
<summary><u>Error 032-0420 when opening browser</u></summary>
|
|
|
|
Follow these steps in order:
|
|
|
|
1. Launch the System Settings application
|
|
1. Navigate to `Internet Settings` -> `Connection Settings`
|
|
1. Click on your network connection slot and navigate to `Change Settings` -> `Next Page (right arrow)` -> `Proxy Settings`
|
|
1. Set "Proxy Settings" to "No"
|
|
1. Click OK, then click Save
|
|
1. When prompted, click "Test" to perform the connection test
|
|
+ The test should succeed
|
|
1. Click "OK" to continue
|
|
1. Press "Back" twice, then "Close" to go back to the HOME Menu
|
|
1. Open the Internet Browser once
|
|
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>
|
|
|
|
{% 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>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>
|
|
|
|
{% capture compat %}
|
|
<summary><u>"PrepareArm9ForTwl returned error c8804631!"</u></summary>
|
|
|
|
Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
|
{% 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>
|
|
|
|
|
|
## Finalizing Setup
|
|
|
|
{% 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.
|
|
|
|
1. Set your DNS settings to "Auto"
|
|
1. Move closer to your WiFi router
|
|
1. Update from Safe Mode by turning off the console, holding (Left Shoulder) + (Right Shoulder) + (D-Pad Up) + (A) on boot, and following the on-screen prompts
|
|
1. Delete your WiFi connection, then reconnect to your WiFi again
|
|
1. Reboot your WiFi router
|
|
1. Connect to a different WiFi connection, like a mobile hotspot
|
|
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>
|
|
|
|
{% 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>
|
|
|
|
{% capture compat %}
|
|
<summary><u>Infinite loading screen 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>
|
|
|
|
{% 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 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}
|
|
|
|
### 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.
|
|
|
|
If the notification LED flashes:
|
|
|
|
- **White**: Your 3DS was not able to find `boot.firm` on your SD card or on internal memory.
|
|
- **Magenta**: Your 3DS was not able to find `boot.firm` on your SD card. It was able to find `boot.firm` on internal memory, but the file is corrupted.
|
|
- **Red**: Your 3DS was able to find `boot.firm` on both your SD card and on internal memory, but both files are corrupted.
|
|
|
|
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>
|
|
|
|
{% 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/`
|
|
+ Delete the corresponding folder for your 3DS region:
|
|
+ **EUR регион**: `00000098`
|
|
+ **JPN регион**: `00000082`
|
|
+ **USA регион**: `0000008f`
|
|
+ **CHN регион**: `000000A1`
|
|
+ **KOR регион**: `000000A9`
|
|
+ **TWN регион**: `000000B1`
|
|
1. Try booting into recovery mode and updating your system:
|
|
+ Power off your device
|
|
+ Hold (Left Shoulder) + (Right Shoulder) + (D-Pad Up) + (A)
|
|
+ Power on your device
|
|
+ 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>
|
|
|
|
### Error message on boot
|
|
|
|
{% 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>
|
|
|
|
{% 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>
|
|
|
|
{% 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>
|
|
|
|
Please take a photo of the error and join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for assistance.
|
|
{% endcapture %}
|
|
<details>{{ compat | markdownify }}</details>
|
|
|
|
## 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. Выключите консоль
|
|
1. Создайте папку `3ds` в корне SD-карты, если таковой нет
|
|
1. Скопируйте `TWLFix-CFW.3dsx` в папку `/3ds/` на SD-карте
|
|
1. Вставьте SD-карту обратно в консоль
|
|
1. Запустите Homebrew Launcher
|
|
1. Выберите TWLFix-CFW в списке homebrew
|
|
1. Нажмите (A), чтобы удалить поврежденные тайтлы TWL
|
|
1. Нажмите (Start) для перезагрузки
|
|
1. Выполните обновление системы, зайдя в Системные настройки, затем "Прочие настройки", затем листайте вправо до конца и выберите пункт "Обновление"
|
|
+ Обновление увидит, что системные тайтлы TWL были удалены, и заново скачает и установит их
|
|
1. После завершения обновления нажмите "OK" для перезагрузки
|
|
{% endcapture %}
|
|
<details>{{ compat | markdownify }}</details>
|
|
|
|
{% capture compat %}
|
|
<summary><u>GBA Virtual Console and/or Safe Mode functionality is broken</u></summary>
|
|
|
|
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>
|
|
|
|
{% 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
|
|
|
|
{% capture compat %}
|
|
<summary><u>Clear HOME Menu extdata</u></summary>
|
|
|
|
1. Выключите консоль
|
|
1. Вставьте SD-карту в компьютер
|
|
1. Navigate to the `/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/` folder on your SD card
|
|
1. Delete the corresponding folder for your 3DS region:
|
|
+ **EUR регион**: `00000098`
|
|
+ **JPN регион**: `00000082`
|
|
+ **USA регион**: `0000008f`
|
|
+ **CHN регион**: `000000A1`
|
|
+ **KOR регион**: `000000A9`
|
|
+ **TWN регион**: `000000B1`
|
|
1. Вставьте SD-карту обратно в консоль
|
|
{% endcapture %}
|
|
<details>{{ compat | markdownify }}</details>
|
|
|
|
{% capture compat %}
|
|
<summary><u>Clear HOME Menu theme data</u></summary>
|
|
|
|
1. Выключите консоль
|
|
1. Вставьте SD-карту в компьютер
|
|
1. Navigate to the `/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/` folder on your SD card
|
|
1. Delete the corresponding folder for your 3DS region:
|
|
+ **EUR Region**: `000002ce`
|
|
+ **JPN Region**: `000002cc`
|
|
+ **USA Region**: `000002cd`
|
|
1. Вставьте SD-карту обратно в консоль
|
|
{% endcapture %}
|
|
<details>{{ compat | markdownify }}</details>
|
|
|