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

Updated FAQ and Troubleshooting (markdown)

Aurora 2016-04-30 03:05:26 +02:00
parent 47b7f37d76
commit b449b8b632
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
FAQ-and-Troubleshooting.md

@ -6,13 +6,13 @@ 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 has been downgraded from the Gateway menu in the past ## I get a black screen on boot with an Old 3DS which has been downgraded from the Gateway menu in the past
If your Old3DS/Old3DS XL has been 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 and leaves CTRNAND in a messy state. If your Old 3DS/Old 3DS XL has been 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 and leaves CTRNAND in a messy state.
Thankfully there's a method for cleaning your CTRNAND (at least the parts required by Luma3DS to operate normally): 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) 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 O3DS from the NTR FIRMs package to the `luma` folder 2. Copy the O3DS `firmware.bin` file 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), plus `O3DS AGB.cia` and `O3DS TWL.cia` to the SD card 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), 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 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 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
@ -26,7 +26,7 @@ There have been some reports of pre-patched AGB/TWL FIRM interfering with Luma3D
Follow these steps to restore the unpatched Nintendo FIRMs: Follow these steps to restore the unpatched Nintendo FIRMs:
1. Get the NAND FIRMs package from [here](http://www56.zippyshare.com/v/TagKBxrI/file.html) 1. Get the NAND FIRMs package from [here](http://www56.zippyshare.com/v/TagKBxrI/file.html)
2. From the NAND FIRMs package, copy `O3DS AGB.cia` and `O3DS TWL.cia` (if you have an Old3DS), or `N3DS AGB.cia` and `N3DS TWL.cia` (if you have a New3DS) to the SD card 2. From the NAND FIRMs package, copy `O3DS AGB.cia` and `O3DS TWL.cia` (if you have an Old 3DS), or `N3DS AGB.cia` and `N3DS TWL.cia` (if you have a New3 DS) to the SD card
3. 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 3. 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
4. Install the .cia files you copied in step 2 4. Install the .cia files you copied in step 2
5. Luma3DS should now be functioning normally 5. Luma3DS should now be functioning normally