81c2fae561
* New translations finalizing-setup.txt (Hungarian) * New translations finalizing-setup.txt (Italian) * New translations finalizing-setup.txt (Japanese) * New translations finalizing-setup.txt (Korean) * New translations finalizing-setup.txt (Dutch) * New translations finalizing-setup.txt (Norwegian) * New translations finalizing-setup.txt (Polish) * New translations finalizing-setup.txt (Portuguese) * New translations finalizing-setup.txt (Russian) * New translations finalizing-setup.txt (Swedish) * New translations finalizing-setup.txt (Turkish) * New translations finalizing-setup.txt (Ukrainian) * New translations finalizing-setup.txt (Chinese Simplified) * New translations finalizing-setup.txt (Chinese Traditional) * New translations finalizing-setup.txt (Vietnamese) * New translations finalizing-setup.txt (Portuguese, Brazilian) * New translations finalizing-setup.txt (Indonesian) * New translations finalizing-setup.txt (Thai) * New translations finalizing-setup.txt (Croatian) * New translations finalizing-setup.txt (Malay) * New translations finalizing-setup.txt (Pirate English) * New translations troubleshooting.txt (Italian) * New translations troubleshooting.txt (Italian) * New translations finalizing-setup.txt (Italian) * New translations troubleshooting.txt (Romanian) * New translations troubleshooting.txt (French) * 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 (Greek) * 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) * New translations finalizing-setup.txt (Romanian) * New translations finalizing-setup.txt (French) * New translations finalizing-setup.txt (Spanish) * New translations finalizing-setup.txt (Arabic) * New translations finalizing-setup.txt (Bulgarian) * New translations finalizing-setup.txt (Catalan) * New translations finalizing-setup.txt (Czech) * New translations finalizing-setup.txt (German) * New translations finalizing-setup.txt (Greek) * New translations finalizing-setup.txt (Finnish) * New translations finalizing-setup.txt (Hebrew) * New translations finalizing-setup.txt (Hungarian) * New translations finalizing-setup.txt (Italian) * New translations finalizing-setup.txt (Japanese) * New translations finalizing-setup.txt (Korean) * New translations finalizing-setup.txt (Dutch) * New translations finalizing-setup.txt (Norwegian) * New translations finalizing-setup.txt (Polish) * New translations finalizing-setup.txt (Portuguese) * New translations finalizing-setup.txt (Russian) * New translations finalizing-setup.txt (Swedish) * New translations finalizing-setup.txt (Turkish) * New translations finalizing-setup.txt (Ukrainian) * New translations finalizing-setup.txt (Chinese Simplified) * New translations finalizing-setup.txt (Chinese Traditional) * New translations finalizing-setup.txt (Vietnamese) * New translations finalizing-setup.txt (Portuguese, Brazilian) * New translations finalizing-setup.txt (Indonesian) * New translations finalizing-setup.txt (Thai) * New translations finalizing-setup.txt (Croatian) * New translations finalizing-setup.txt (Malay) * New translations finalizing-setup.txt (Pirate English) * New translations addproxy.txt (Romanian) * New translations addproxy.txt (French) * New translations addproxy.txt (Spanish) * New translations addproxy.txt (Arabic) * New translations addproxy.txt (Bulgarian) * New translations addproxy.txt (Catalan) * New translations addproxy.txt (Czech) * New translations addproxy.txt (German) * New translations addproxy.txt (Greek) * New translations addproxy.txt (Finnish) * New translations addproxy.txt (Hebrew) * New translations addproxy.txt (Hungarian) * New translations addproxy.txt (Italian) * New translations addproxy.txt (Japanese) * New translations addproxy.txt (Korean) * New translations addproxy.txt (Dutch) * New translations addproxy.txt (Norwegian) * New translations addproxy.txt (Polish) * New translations addproxy.txt (Portuguese) * New translations addproxy.txt (Russian) * New translations addproxy.txt (Swedish) * New translations addproxy.txt (Turkish) * New translations addproxy.txt (Ukrainian) * New translations addproxy.txt (Chinese Simplified) * New translations addproxy.txt (Chinese Traditional) * New translations addproxy.txt (Vietnamese) * New translations addproxy.txt (Portuguese, Brazilian) * New translations addproxy.txt (Indonesian) * New translations addproxy.txt (Thai) * New translations addproxy.txt (Croatian) * New translations addproxy.txt (Malay) * New translations addproxy.txt (Pirate English) * New translations finalizing-setup.txt (Romanian) * New translations finalizing-setup.txt (French) * New translations finalizing-setup.txt (Spanish) * New translations finalizing-setup.txt (Arabic) * New translations finalizing-setup.txt (Bulgarian) * New translations finalizing-setup.txt (Catalan) * New translations finalizing-setup.txt (Czech) * New translations finalizing-setup.txt (German) * New translations finalizing-setup.txt (Greek) * New translations finalizing-setup.txt (Finnish) * New translations finalizing-setup.txt (Hebrew) * New translations finalizing-setup.txt (Hungarian) * New translations finalizing-setup.txt (Italian) * New translations finalizing-setup.txt (Japanese) * New translations finalizing-setup.txt (Korean) * New translations finalizing-setup.txt (Dutch) * New translations finalizing-setup.txt (Norwegian) * New translations finalizing-setup.txt (Polish) * New translations finalizing-setup.txt (Portuguese) * New translations finalizing-setup.txt (Russian) * New translations finalizing-setup.txt (Swedish) * New translations finalizing-setup.txt (Turkish) * New translations finalizing-setup.txt (Ukrainian) * New translations finalizing-setup.txt (Chinese Simplified) * New translations finalizing-setup.txt (Chinese Traditional) * New translations finalizing-setup.txt (Vietnamese) * New translations finalizing-setup.txt (Portuguese, Brazilian) * New translations finalizing-setup.txt (Indonesian) * New translations finalizing-setup.txt (Thai) * New translations finalizing-setup.txt (Croatian) * New translations finalizing-setup.txt (Malay) * New translations finalizing-setup.txt (Pirate English) * New translations troubleshooting.txt (Romanian) * New translations troubleshooting.txt (French) * 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 (Greek) * 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) * New translations finalizing-setup.txt (Romanian) * New translations finalizing-setup.txt (French) * New translations finalizing-setup.txt (Spanish) * New translations finalizing-setup.txt (Arabic) * New translations finalizing-setup.txt (Bulgarian) * New translations finalizing-setup.txt (Catalan) * New translations finalizing-setup.txt (Czech) * New translations finalizing-setup.txt (German) * New translations finalizing-setup.txt (Greek) * New translations finalizing-setup.txt (Finnish) * New translations finalizing-setup.txt (Hebrew) * New translations finalizing-setup.txt (Hungarian) * New translations finalizing-setup.txt (Italian) * New translations finalizing-setup.txt (Japanese) * New translations finalizing-setup.txt (Korean) * New translations finalizing-setup.txt (Dutch) * New translations finalizing-setup.txt (Norwegian) * New translations finalizing-setup.txt (Polish) * New translations finalizing-setup.txt (Portuguese) * New translations finalizing-setup.txt (Russian) * New translations finalizing-setup.txt (Swedish) * New translations finalizing-setup.txt (Turkish) * New translations finalizing-setup.txt (Ukrainian) * New translations finalizing-setup.txt (Chinese Simplified) * New translations finalizing-setup.txt (Chinese Traditional) * New translations finalizing-setup.txt (Vietnamese) * New translations finalizing-setup.txt (Portuguese, Brazilian) * New translations finalizing-setup.txt (Indonesian) * New translations finalizing-setup.txt (Thai) * New translations finalizing-setup.txt (Croatian) * New translations finalizing-setup.txt (Malay) * New translations finalizing-setup.txt (Pirate English) * New translations troubleshooting.txt (Romanian) * New translations troubleshooting.txt (French) * 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 (Greek) * 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) * New translations finalizing-setup.txt (Italian) * New translations addproxy.txt (Italian)
809 lines
44 KiB
Text
809 lines
44 KiB
Text
---
|
||
title: "疑難排解"
|
||
---
|
||
|
||
本頁提供常見問題的疑難解答及建議。 如果您無法透過本頁解決你的問題,請加入 [Discord 上的 Nintendo Homebrew 伺服器](https://discord.gg/MWxPgEp),並以英文敘述你的問題,以及您已經嘗試過的步驟。
|
||
|
||
{% 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)
|
||
* [Homebrew Launcher (super-skaterhax)](#homebrew-launcher-super-skaterhax)
|
||
|
||
* [Finalizing Setup](#finalizing-setup)
|
||
|
||
Issues after installation:
|
||
* [Boot issues](#boot-issues-on-consoles-with-custom-firmware)
|
||
* [Software issues](#software-issues-on-consoles-with-custom-firmware)
|
||
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
{: .notice--info}
|
||
|
||
## 關於 SafeB9SInstaller 的問題
|
||
|
||
### 『SigHaxed FIRM was not installed!』 Check lower screen for more info.
|
||
|
||
{% capture compat %}
|
||
<summary><u>MicroSD Card - init failed</u></summary>
|
||
|
||
Your SD card is most likely acting weird. Try reformatting your SD card ([Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux))). If this doesn't work, try another SD card.
|
||
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>SigHaxed FIRM - File not found</u></summary>
|
||
|
||
你忘記把 `boot9strap.firm` 和 `boot9strap.firm.sha` 放進 SD 卡根目錄的 `boot9strap` 資料夾,或建立 `boot9strap` 資料夾的時候打錯了名字。 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>
|
||
|
||
你的 `boot9strap.firm` 和 `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>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Secret Sector - File not found</u></summary>
|
||
|
||
你忘記把 `secret_sector.bin` 放進 SD 卡根目錄的 `boot9strap` 資料夾了,或是建立 `boot9strap` 資料夾的時候打錯了名字。 用 BT 下載 [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),並將其放至 `boot9strap` 資料夾中。
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Something else</u></summary>
|
||
|
||
請在 [Discord 上的 Nintendo Homebrew 伺服器](https://discord.gg/MWxPgEp)以英文尋求協助,並敘述您所看到的錯誤訊息。
|
||
{% 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 consoles and is intended to prevent inadvertently merging data that would not be valid on other consoles. 若要確定哪個資料夾屬於您 3DS 的,請按照以下說明操作:
|
||
|
||
1. 將 `Nintendo 3DS` 資料夾重新命名為 `BACKUP_Nintendo 3DS`
|
||
1. Reinsert your SD card into your console
|
||
1. Power on your console
|
||
1. Wait for the console to generate the SD card data
|
||
+ 您先前所安裝的應用程式會暫時消失。 這是正常的,且待會就會恢復正常。
|
||
1. Power off your console
|
||
1. 將 SD 卡插入至電腦中
|
||
1. 移動至 SD 卡的 `Nintendo 3DS` 資料夾中
|
||
1. 複製含有 32 字元的資料夾的名稱
|
||
+ 這也就是您裝置的 ID0 序號,可適用於 [Seedminer 第二章節部分的步驟](seedminer#section-ii---seedminer)
|
||
1. 刪除 `Nintendo 3DS` 資料夾
|
||
1. 將 `BACKUP_Nintendo 3DS` 資料夾重新命名為 `Nintendo 3DS`
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Bruteforce Movable skips to step 4</u></summary>
|
||
|
||
這代表網站曾已經使用你的好友碼和 ID0 取得你的 `movable.sed` 了。 你可以直接使用它給的 `movable.sed` 檔案。
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Important! You have been locked out of the automated part1 dumper system...</u></summary>
|
||
|
||
你的好友代碼已被本服務封鎖,因為你沒有在服務的限定時間內將機器人好友碼加入到好友列表。 確保你的 3DS 已經連上網,然後加入 [Nintendo Homebrew Discord 伺服器](https://discord.gg/MWxPgEp)來要求解鎖。
|
||
{% 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.
|
||
|
||
If you have a New 3DS / New 3DS XL / New 2DS XL (as indicated by the four shoulder buttons on the back and the C-Stick on the right), you can follow [Homebrew Launcher (super-skaterhax)](homebrew-launcher-(super-skaterhax)). Otherwise, you will need to follow a method that requires additional games or hardware.
|
||
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
## BannerBomb3
|
||
|
||
{% capture compat %}
|
||
<summary><u>Multiple ID1 folders inside of ID0</u></summary>
|
||
|
||
![]({{ "/images/screenshots/multiple-id1.png" | absolute_url }})
|
||
|
||
This can occur if you've used multiple SD cards on a 3DS and then merged the contents of the SD cards together. This is done to prevent conflicting, valid data from being merged together.
|
||
|
||
To fix this, you will need to determine which folder contains your data. Usually, this will be the larger (or largest) of the folders. Backup and delete the smaller one(s), then create a `Nintendo DSiWare` folder in the one that remains and move `F00D43D5.bin` to that location.
|
||
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>DSiWare Management menu crashes without showing BB3 multihax menu</u></summary>
|
||
確保 `F00D43D5.bin` 是 `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 console in a way that makes this method impossible to perform. If this is the case, 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 displays "No accessible software data."</u></summary>
|
||
|
||
`F00D43D5.bin` 沒有放進 `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare`。 請確保 `Nintendo DSiWare` 拼寫和空格位置正確。 請注意大小寫是沒有關係的。
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>DSiWare Management shows a question mark</u></summary>
|
||
|
||
您所使用的 `F00D43D5.bin` 檔案可能有問題(損壞或用於錯誤的 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>
|
||
|
||
## 安裝 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. 如果您的電腦沒有顯示 `.bin` 的副檔名,請勿手動新增。
|
||
|
||
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>
|
||
|
||
`SafeB9SInstaller.bin` 檔案遺失或放在了錯誤的位置。 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. 如果您的電腦沒有顯示 `.bin` 的副檔名,請勿手動新增。
|
||
{% 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.
|
||
|
||
若仍無法正常使用,請試著使用另一張 SD 卡。
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
## 安裝 boot9strap (透過 Fredtool)
|
||
|
||
{% capture compat %}
|
||
<summary><u>Error on Fredtool Injector page</u></summary>
|
||
|
||
請確保您的 `movable.sed` 檔案和 DSiWare 備份是從同一台主機匯出的。 若兩者並不匹配則會跳出錯誤。
|
||
{% 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>
|
||
|
||
您所使用的 `42383821.bin` 檔案有問題(有問題、放錯位置或者損壞)。 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!` 沒有被從 SD 卡中複製到系統內存中。
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Black screen when launching DS Connection Settings</u></summary>
|
||
|
||
你主機的 DS『連線設定 (Connection Settings)』已損壞;您得需要想辦法獲得啟動 Homebrew Launcher 的權限才能正確將其修復。 請加入 [Discord 上的 Nintendo Homebrew](https://discord.gg/MWxPgEp) 頻道尋求幫助。
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>SD card is grayed out in Flipnote</u></summary>
|
||
|
||
如果您所使用的 SD 卡特別大的話,Flipnote 可能需要花很長時間來建立相對應的索引。 等待幾分鐘即可。
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Lenny face does not appear in SD card section</u></summary>
|
||
|
||
您尚未解壓 Frogminer_save `.zip` 中的 `private` 資料夾到 SD 卡的根目錄底下.
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Flipnote freezes</u></summary>
|
||
|
||
您在修改過的 Flipnote 中可能誤觸了觸控螢幕。 請重新開啟 DS 連線設定 (Connection Settings) 並再試一次-並特別注意不要誤觸螢幕。
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Green screen after pasting</u></summary>
|
||
|
||
`boot.nds` 檔案遺失或位置錯誤。 下載最新版本的 [b9stool](https://github.com/zoogie/b9sTool/releases/latest) 並將 `boot.nds` 放在你 SD 卡的根目錄中,如有存在相同檔案請替換。
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
|
||
{% capture compat %}
|
||
<summary><u>White screen after pasting</u></summary>
|
||
這代表您所使用的 `boot.nds` 檔案有問題。 重新下載最新版本的 [b9stool](https://github.com/zoogie/b9sTool/releases/latest) 並將 `boot.nds` 放在你 SD 卡的根目錄中,如有存在相同檔案請替換。
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Unable to open Luma3DS configuration menu after running B9STool</u></summary>
|
||
|
||
Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and explain what has happened.
|
||
{% 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 [otherapps.zip](/assets/otherapps.zip), place the `.bin` file relevant to your console to the root of your SD card, and rename it to `otherapp.bin`. 如果您的電腦沒有顯示 `.bin` 的副檔名,請勿手動新增。
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>"An exception occurred" or Errdisp when opening Picross</u></summary>
|
||
|
||
Your console already has custom firmware. 請先[檢查是否已安裝自製韌體](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 [otherapps.zip](/assets/otherapps.zip), place the `.bin` file relevant to your console to the root of your SD card, and rename it to `otherapp.bin`. 如果您的電腦沒有顯示 `.bin` 的副檔名,請勿手動新增。
|
||
{% 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>
|
||
|
||
## 安裝 boot9strap (透過 Soundhax)
|
||
|
||
{% capture compat %}
|
||
<summary><u>Red/purple/pink and white screen after running Soundhax</u></summary>
|
||
|
||
If your console 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 console is not on those firmwares, it likely indicates that you already have custom firmware. 請先[檢查是否已安裝自製韌體](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>
|
||
|
||
您所使用的 `otherapp.bin` 檔案有問題(如遺失、放錯位置或者損壞)。 下載最新版本的 [universal-otherapp](https://github.com/TuxSH/universal-otherapp/releases/latest) 並將其放在你 SD 卡的根目錄中。
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>"Could not play"</u></summary>
|
||
|
||
You have the wrong Soundhax file for your console and region, or your console is incompatible with Soundhax. In the latter case, your course of action will determine on what version your 3DS is currently on. 請加入 [Discord 上的 Nintendo Homebrew](https://discord.gg/MWxPgEp) 頻道尋求幫助。
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
|
||
|
||
`SafeB9SInstaller.bin` 檔案遺失或放在了錯誤的位置。 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. 如果您的電腦沒有顯示 `.bin` 的副檔名,請勿手動新增。
|
||
{% 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.
|
||
|
||
若仍無法正常使用,請試著使用另一張 SD 卡。
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
## 安裝 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. 請先[檢查是否已安裝自製韌體](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`. 如果您的電腦沒有顯示 `.bin` 的副檔名,請勿手動新增。
|
||
{% 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`. 如果您的電腦沒有顯示 `.bin` 的副檔名,請勿手動新增。
|
||
{% 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 select "Reset Save Data" (it may also be called "Initialize Save Data" or "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 System Settings on your console
|
||
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>
|
||
|
||
`SafeB9SInstaller.bin` 檔案遺失或放在了錯誤的位置。 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. 如果您的電腦沒有顯示 `.bin` 的副檔名,請勿手動新增。
|
||
{% 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`. 如果您的電腦沒有顯示 `.bin` 的副檔名,請勿手動新增。
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>"PrepareArm9ForTwl returned error c8804631!"</u></summary>
|
||
|
||
請加入 [Discord 上的 Nintendo Homebrew](https://discord.gg/MWxPgEp) 頻道尋求幫助。
|
||
{% 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.
|
||
|
||
若仍無法正常使用,請試著使用另一張 SD 卡。
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
## Homebrew Launcher (super-skaterhax)
|
||
|
||
{% capture compat %}
|
||
<summary><u>"An error has occurred. Please save your data in any software currently in use, then restart the system."</u></summary>
|
||
|
||
The date is set incorrectly. To set it correctly, follow these steps:
|
||
|
||
1. Select the System Settings icon on the HOME Menu, and tap Open.
|
||
1. Tap Other Settings.
|
||
1. Tap Date & Time.
|
||
1. Tap Today's date.
|
||
1. Tap Up/Down Arrows to set the correct Day, Month and Year.
|
||
1. Select OK to confirm.
|
||
|
||
If the problem persists:
|
||
|
||
- Ensure that `arm11code.bin`, `browserhax_hblauncher_ropbin_payload.bin`, and `boot.3dsx` are on the root of the SD card (not inside of any folder)
|
||
- Ensure that you selected the correct payload for your region AND system version
|
||
- Ensure that your region settings look [like this](/images/screenshots/skater_lang.png)
|
||
- Try resetting your browser data:
|
||
1. Launch the browser, then launch the browser settings
|
||
1. Scroll to the bottom and select "Reset Save Data" (it may also be called "Initilize Save Data" or "Clear All Save Data")
|
||
1. Try the exploit again
|
||
- Try changing the system language to something other than the current language
|
||
|
||
{% 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. Make sure to copy the files of the [latest version of super-skaterhax](https://github.com/zoogie/super-skaterhax/releases/latest) for your region and version to the root of your SD card (not inside of a folder).
|
||
|
||
![]({{ "/images/screenshots/skater-root-layout.png" | absolute_url }})
|
||
{: .notice--info}
|
||
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
|
||
{% capture compat %}
|
||
<summary><u>An exception occured or "DLL_HEAP_INFORMATION" when pressing GO! GO!</u></summary>
|
||
|
||
This likely indicates that you already have custom firmware. 請先[檢查是否已安裝自製韌體](checking-for-cfw) 。
|
||
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
## 完成安裝
|
||
|
||
{% capture compat %}
|
||
<summary><u>Unable to update console</u></summary>
|
||
|
||
以下是可以嘗試的解決方法,按從簡單到困難的順序排列。
|
||
|
||
1. 將網路設定中的 DNS 位址設定設為『自動 (Auto)』
|
||
1. 將主機靠近您的 WiFi 路由器
|
||
1. 開機時按住「L」鍵 +「R」鍵 +「上」鍵 +「A」鍵以開機至安全模式中,並遵循所示指示進行更新
|
||
1. 將主機中的 WiFi 連線設定清除,並再重新設定一次
|
||
1. 重新啟動您的 WiFi 路由器
|
||
1. 試著使用其他 WiFi 連線,比如手機的 WiFi 熱點
|
||
1. 任天堂伺服器目前可能臨時下線,請稍後再試
|
||
1. 如果錯誤持續,請進行 [CTRTransfer](ctrtransfer),並再試一次
|
||
1. 請至 [Discord 的 Nintendo Homebrew](https://discord.gg/MWxPgEp) 伺服器中尋求協助 (英文)。
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Error #01: No Nintendo 3DS folder</u></summary>
|
||
|
||
Your SD card does not have the `Nintendo 3DS` folder. Power on your device with your SD card inserted, then wait for the device to show a message box that says "Creating HOME Menu management information". Once the message box disappears, power off your device and try again.
|
||
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Error #02: Missing essential.exefs</u></summary>
|
||
|
||
You said 'No' to the "Make essential files backup?" prompt in GodMode9. Power off your device, power it on while holding (Start) to re-enter GodMode9, say 'Yes' to the prompt, then try again.
|
||
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
|
||
<summary><u>Unable to open GodMode9 or Error #03: Missing files</u></summary>
|
||
|
||
You did not copy everything from `finalize.zip` to the root of your SD card. Remember, your SD card should have at least these files:
|
||
|
||
![]({{ "/images/screenshots/finalizing-root-layout.png" | absolute_url }})
|
||
{: .notice--info}
|
||
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
|
||
<summary><u>Error #04: No space</u></summary>
|
||
|
||
You need at least 1.3GB of free space to perform the NAND backup, which is a part of the script. If you don't have enough space, follow these steps:
|
||
|
||
1. Power off your console
|
||
1. Remove the SD card and insert it into your computer
|
||
1. Copy the `Nintendo 3DS` folder from the root of your SD card to your computer
|
||
1. Delete the Nintendo 3DS folder from the SD card
|
||
1. Reinsert your SD card into your console
|
||
1. Power off your console, hold START and power on still holding START to boot on GodMode9
|
||
1. 選擇『Scripts...』
|
||
1. Select "finalize"
|
||
1. Follow the prompts in the script, answering each question that you are asked
|
||
1. Copy the files in `gm9/out` on your SD to a safe location on your computer
|
||
1. Delete the `<date>_<serialnumber>_sysnand_##.bin` and `<date>_<serialnumber>_sysnand_##.bin.sha` files from the SD card, keeping essential.exefs in `/gm9/out/`
|
||
1. Copy the `Nintendo 3DS` folder from your computer to the root of your SD card
|
||
1. Delete the `Nintendo 3DS` folder from your computer
|
||
|
||
Once done, re-run the script.
|
||
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Error #05: No title database</u></summary>
|
||
|
||
Press (A) to create a title database, unlock SysNAND writing by entering the buttons on-screen, follow the prompts [here](/images/screenshots/database-reset.jpg), then re-run the script.
|
||
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Error #06 or "Error: Could not open directory" when attempting a NAND backup</u></summary>
|
||
|
||
Make sure you have at least 1.3GB available in your SD card. If you don't have enough space, follow these steps:
|
||
1. Power off your console
|
||
1. Remove the SD card and insert it into your computer
|
||
1. Copy the `Nintendo 3DS` folder from the root of your SD card to your computer
|
||
1. Delete the Nintendo 3DS folder from the SD card
|
||
1. Reinsert your SD card into your console
|
||
1. Power off your console, hold START and power on still holding START to boot on GodMode9
|
||
1. Perform a [NAND Backup](godmode9-usage#creating-a-nand-backup)
|
||
1. Copy the files in `gm9/out` on your SD to a safe location on your computer
|
||
1. Delete the `<date>_<serialnumber>_sysnand_##.bin` and `<date>_<serialnumber>_sysnand_##.bin.sha` files from the SD card, keeping essential.exefs in `/gm9/out/`
|
||
1. Copy the `Nintendo 3DS` folder from your computer to the root of your SD card
|
||
1. Delete the `Nintendo 3DS` folder from your computer
|
||
|
||
If you have enough space on your SD card, your SD might be corrupted or faulty. Check your SD card for any errors by following the guide according to your computer's operating system: [Windows](h2testw-(windows)), [Linux](f3-(linux)), [macOS](f3xswift-(mac)).
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Error #08: Dummy title database</u></summary>
|
||
|
||
You didn't delete the dummy title database that was created by Error #05. Follow the prompts [here](/images/screenshots/database-reset.jpg), then re-run the script.
|
||
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
---
|
||
|
||
## Boot issues on consoles with custom firmware
|
||
|
||
The steps detailed here generally assume that your console has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). 如果你的主機還在用舊版的自製韌體(例如基於 arm9loaderhax 或 menuhax 的安裝),則你應該在繼續操作前先升級自製韌體。
|
||
{: .notice--info}
|
||
|
||
### Power/notification light indicators
|
||
|
||
{% capture compat %}
|
||
<summary><u>My console 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 console.
|
||
|
||
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 console (such as a disconnected backlight cable). You may be able to get your console to boot by holding it at certain angles.
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>My console gets stuck on a black screen with blue power light staying on</u></summary>
|
||
|
||
以下是可以嘗試的解決方法,按最省時到最耗時的順序排列。
|
||
|
||
1. Power off your console, remove the SD card, re-insert it, then power on your console.
|
||
1. Power off your console, eject the game cartridge if inserted, power on your console, then wait up to ten minutes. If your console boots within ten minutes, the issue has been fixed and is unlikely to reoccur
|
||
1. 將 SD 卡上的 `Nintendo 3DS` 資料夾重命名為 `Nintendo 3DS_BACKUP`,然後試著開機。 If your console successfully boots, there is some issue within your `Nintendo 3DS` folder. 試著刪除 HOME 主選單的外存 (extdata):
|
||
+ 移動至 `/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/`
|
||
+ Delete the corresponding folder for your 3DS region:
|
||
+ **歐版**: `00000098`
|
||
+ **日版**: `00000082`
|
||
+ **美版**: `0000008f`
|
||
+ **大陸版**: `000000A1`
|
||
+ **韓版**: `000000A9`
|
||
+ **台灣版**: `000000B1`
|
||
1. 試試看透過還原模式更新您的系統:
|
||
+ Power off your console
|
||
+ 按住「L」鍵 +「R」鍵 +「上」鍵 +「A」鍵
|
||
+ Power on your console
|
||
+ If you were successful, the console will boot to an "update your system" screen
|
||
1. 遵循[CTRTransfer](ctrtransfer)中的步驟
|
||
1. 請至 [Discord 的 Nintendo Homebrew](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>
|
||
|
||
你主機的 Luma3DS 版本已過時。 下載最新版本的[Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) 並將 `boot.firm` 放在你 SD 卡的根目錄中,如有存在相同檔案請直接覆蓋。 請不要用 WinRAR 解壓 ZIP 檔案;目前已知使用此軟體會導致與 3DS 有關的檔案的問題。
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>"Unable to mount CTRNAND or load the CTRNAND FIRM. Please use an external one."</u></summary>
|
||
There are a number of reasons as to why this could be happening. In any case, this error can usually be fixed by following the [CTRTransfer](ctrtransfer) guide.
|
||
{% 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 異常處理器已被關閉,或主機尚未安裝自製韌體。 試著啟用 ARM11 異常處理器:
|
||
+ Power off your console
|
||
+ 按住「Select」鍵
|
||
+ Power on your console, while still holding (Select)
|
||
+ 如果『ARM11 exception handlers disabled』已被勾選,請取消勾選
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>HOME Menu is missing installed applications</u></summary>
|
||
|
||
This could be caused by various reasons, but most likely because your SD card is not being read by the system.
|
||
You can check if your SD is being read by holding SELECT on boot and checking the yellow text on the bottom screen; if it says "Booted from CTRNAND via B9S", then your console is booting from the internal memory and not from the SD card.
|
||
If this is the case, attempt the steps below, which are listed from easiest to hardest:
|
||
1. Power off your console, remove the SD card, re-insert it, then power on your console
|
||
1. Power off your console, remove the SD card, insert it on your PC, download the latest release of [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest), extract `boot.firm` from the `Luma3DS.zip` and place it on the root of your SD card (replacing any existing file)
|
||
1. Power off your console, remove the SD card, insert it on your PC and reformat your SD card according to your computer's operating system: [Windows](formatting-sd-(windows)), [macOS](formatting-sd-(mac)), [Linux](formatting-sd-(linux)) *(this will wipe your SD card data)*
|
||
1. Test your SD card for errors by following the guide according to your computer's operating system: [Windows](h2testw-(windows)), [Linux](f3-(linux)), [macOS](f3xswift-(mac)). If your SD card is marked as faulty, then you will have to replace your SD card
|
||
1. Your SD card slot may be broken. Join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for further assistance
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Blue "BOOTROM ERROR" screen</u></summary>
|
||
|
||
Your console is likely hard-bricked. You will need to buy an ntrboot flashcart to reinstall boot9strap in order to attempt to fix your console. This may also indicate a hardware issue that cannot be fixed. 不論如何,請加入 [Discord 上的 Nintendo Homebrew 伺服器](https://discord.gg/MWxPgEp) 尋求幫助。
|
||
+ 也有可能是有人惡作劇,把您主機的開機畫面改成像是磚機的畫面。 Try leaving your console powered on, waiting on the blue screen, for five minutes.
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Some other error</u></summary>
|
||
|
||
請將錯誤訊息拍下,請加入 [Discord 上的 Nintendo Homebrew](https://discord.gg/MWxPgEp) 頻道尋求協助。
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
## Software issues on consoles with custom firmware
|
||
|
||
{% capture compat %}
|
||
<summary><u>DSi / DS functionality is broken or has been replaced with Flipnote Studio</u></summary>
|
||
|
||
1. * 下載最新版的 [TWLFix-CFW](https://github.com/MechanicalDragon0687/TWLFix-CFW/releases/latest) *(`.3dsx` 檔案)*
|
||
1. Power off your console
|
||
1. 在 SD 卡的根目錄底下建立一個新資料夾 `3ds`
|
||
1. 將 `TWLFix-CFW.3dsx` 複製到 SD 卡中的 `/3ds/` 資料夾底下
|
||
1. Reinsert your SD card into your console
|
||
1. 啟動 Homebrew Launcher
|
||
1. 於 Homebrew 清單內啟動 TWLFix-CFW 管理器
|
||
1. 按 『A』 移除損壞的 TWL 程式
|
||
1. Press (Start) to reboot the console
|
||
1. Update your console by going to System Settings, then "Other Settings", then going all the way to the right and using "System Update"
|
||
+ 更新程式將會偵測到裝置必要的 TWL 軟體已被移除,並重新下載和安裝它們
|
||
1. Once the update is complete, tap "OK" to reboot the console
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>GBA Virtual Console and/or Safe Mode functionality is broken</u></summary>
|
||
|
||
Your console is running Luma3DS 6.6 or older, likely via arm9loaderhax. You should follow [A9LH to B9S](a9lh-to-b9s) to update your console 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>
|
||
|
||
舊版 3DS / 2DS 在做完 CTRTransfer 或區碼變更之後可能會出現這個問題。 You will need to system format your console to fix this issue.
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Exception screen when booting/loading an application</u></summary>
|
||
|
||
Look for your exception screen in [this page](https://wiki.hacks.guide/wiki/3DS:Error_screens/Luma3DS_exception_screen).
|
||
If you weren't able to find your error or the instructions didn't work, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) for further assistance.
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Opening the HOME Menu settings crashes the console or loads the Homebrew Launcher</u></summary>
|
||
|
||
Your console likely still has menuhax67 installed. To uninstall menuhax67, download the latest release of [menuhax67](https://github.com/zoogie/menuhax67/releases/latest) (the menuhax `.zip`), then follow the ["Uninstall menuhax67" section](https://wiki.hacks.guide/wiki/3DS:Alternate_Exploits/menuhax67#Uninstall_menuhax67) here.
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
---
|
||
|
||
## 其他疑難排解
|
||
|
||
{% capture compat %}
|
||
<summary><u>Clear HOME Menu extdata</u></summary>
|
||
|
||
1. Power off your console
|
||
1. 將 SD 卡插入至電腦中
|
||
1. 移動至您 SD 卡的 `/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000` 資料夾中
|
||
1. 刪除對應您 3DS 區域的資料夾:
|
||
+ **歐版**: `00000098`
|
||
+ **日版**: `00000082`
|
||
+ **美版**: `0000008f`
|
||
+ **大陸版**: `000000A1`
|
||
+ **韓版**: `000000A9`
|
||
+ **台灣版**: `000000B1`
|
||
1. Reinsert your SD card into your console
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Clear HOME Menu theme data</u></summary>
|
||
|
||
1. Power off your console
|
||
1. 將 SD 卡插入至電腦中
|
||
1. 移動至您 SD 卡的 `/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000` 資料夾中
|
||
1. 刪除對應您 3DS 區域的資料夾:
|
||
+ **歐版**: `000002ce`
|
||
+ **日版**: `000002cc`
|
||
+ **美版**: `000002cd`
|
||
1. Reinsert your SD card into your console
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Manually entering Homebrew Launcher</u></summary>
|
||
|
||
If you are missing the Homebrew Launcher application from your HOME Menu, you can follow these instructions to manually enter the Homebrew Launcher. (You will need [boot.3dsx and boot.firm](https://github.com/LumaTeam/Luma3DS/releases/latest) on the root of your SD card.)
|
||
|
||
{% include_relative include/launch-hbl-dlp.txt %}
|
||
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|
||
{% capture compat %}
|
||
<summary><u>Turning off Parental Controls</u></summary>
|
||
|
||
You can disable the Parental Controls feature by going to System Settings -> Parental Controls and inserting the PIN, then pressing "Clear Settings", then "Delete" to remove it.
|
||
However, if you do not know the PIN and therefore cannot access the console's settings, you will need to disable it. In order to do this, you need to obtain your console's master key (mkey):
|
||
1. Go to [this website](https://mkey.eiphax.tech/)
|
||
1. Fill the following boxes with the information:
|
||
+ Device Type: Select "3DS" (the same applies if you are using a 2DS, New 3DS (XL/LL) or New 2DS (XL/LL))
|
||
+ System Date: The day and month your console's clock is set to
|
||
+ Inquiry Number: Can be obtained by pressing "Forgot PIN" then "I Forgot" in the Parental Controls screen
|
||
1. After you have obtained your mkey, press OK on the screen you have obtained your Inquiry Number, then input the master key
|
||
1. Press "Clear Settings", then "Delete" to remove all Parental Controls data
|
||
{% endcapture %}
|
||
<details>{{ compat | markdownify }}</details>
|
||
|