Mirror/Luma3DS
1
0
Fork 0
mirror of https://github.com/LumaTeam/Luma3DS.git synced 2026-02-26 20:04:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated FAQ and Troubleshooting (markdown)

Aurora 2016-04-29 23:21:46 +02:00
parent 5bfe7e5bc6
commit b83ebf051c
1 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
FAQ-and-Troubleshooting.md

@ -6,6 +6,20 @@ You haven't configured Luma3DS to work with your boot manager, please refer to [
Your payload is out of date. You can get the latest version for Decrypt9/EmuNAND9/GodMode9 from their respective GitHub release pages, an updated Uncart from [here](https://github.com/AuroraWright/uncart/releases) and an updated CTRBootManager9 from [here](https://gbatemp.net/threads/release-ctrbootmanager9.417159/page-23#post-6271681). Your payload is out of date. You can get the latest version for Decrypt9/EmuNAND9/GodMode9 from their respective GitHub release pages, an updated Uncart from [here](https://github.com/AuroraWright/uncart/releases) and an updated CTRBootManager9 from [here](https://gbatemp.net/threads/release-ctrbootmanager9.417159/page-23#post-6271681).
## I get a black screen on boot with an Old3DS which was downgraded from the Gateway menu in the past
If your Old3DS/Old3DS XL was downgraded to 4.5 from the Gateway menu in the past, your CTRNAND has leftovers from one or more previous FIRMs, and this causes issues with the CTRNAND code. This is not an issue with Luma itself, but rather with the GW downgrade process which doesn't do any cleanup when downgrading.
Thankfully there's a method for cleaning your CTRNAND (at least the parts required by Luma3DS to operate normally):
1. Get the NTR FIRMs package from [here](http://www70.zippyshare.com/v/Fbj6n1vB/file.html) and the NAND FIRMs package from [here](http://www56.zippyshare.com/v/TagKBxrI/file.html)
2. Copy the `firmware.bin` file for your console from the NTR FIRMs package to the `luma` folder
3. From the NAND FIRMs package, copy `O3DS NATIVE90.cia` (if your NAND is 9.0/9.2) or `O3DS NATIVE104.cia` (if your NAND is updated to the latest version) to the SD card, plus `O3DS AGB.cia` and `O3DS TWL.cia` to the SD card
4. Hold the **SELECT** button to open the Luma3DS configuration menu and make sure the **SysNAND is updated** option is turned on if you are fixing SysNAND and viceversa, and press START to reboot; if **not** booting from A9LH boot Luma3DS again
5. Open your favorite cia installer (the guide has been tested successfully with **FBI 2.1**). If you don't have one, it's outside the scope of this guide, look on GBATemp to check how to get your first cia installed
6. Install the .cia files you copied in step 3
7. If you have other NANDs to fix, repeat the process from step 3 to step 6
7. Luma3DS should now be functioning normally, you can remove the `firmware.bin` from the `luma` folder and configure the **SysNAND is updated** option as needed
## I have a different issue ## I have a different issue
- If coming from a previous version of Luma3DS and you have an issue, try to delete the `config.bin` in `luma` and try again. - If coming from a previous version of Luma3DS and you have an issue, try to delete the `config.bin` in `luma` and try again.