From 887870bed6dc94e2c8f3ba9a39069e6438a50017 Mon Sep 17 00:00:00 2001 From: Aurora Date: Wed, 28 Sep 2016 17:06:07 +0200 Subject: [PATCH] Updated FAQ and troubleshooting (markdown) --- FAQ-and-troubleshooting.md | 14 -------------- 1 file changed, 14 deletions(-) diff --git a/FAQ-and-troubleshooting.md b/FAQ-and-troubleshooting.md index 82ef23e..e625b62 100644 --- a/FAQ-and-troubleshooting.md +++ b/FAQ-and-troubleshooting.md @@ -6,20 +6,6 @@ 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 and an updated CtrBootManager9 from [here](https://gbatemp.net/threads/release-ctrbootmanager9.417159/page-23#post-6271681). -## I get an "unsupported FIRM" error on boot with an Old 3DS which has been downgraded from the Gateway menu in the past - -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): - -1. Get the FIRM .bins package from [here](http://www42.zippyshare.com/v/aqbG6Hlj/file.html) and the NAND FIRMs package from [here](http://www64.zippyshare.com/v/deaIdQMn/file.html) -2. Copy the O3DS `firmware.bin` file from the FIRM .bins package to the `luma` folder -3. From the NAND FIRMs package, copy `O3DS NATIVE.cia`, `O3DS AGB.cia` and `O3DS TWL.cia` to the SD card -4. Boot the NAND you need to fix -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, check how to get your first cia installed on [Plailect's guide](https://github.com/Plailect/Guide/wiki/Part-3-(arm9loaderhax)#section-v---injecting-fbi) -6. Install the .cia files you copied in step 3 -7. If you have other NANDs to fix, repeat the process from step 4 to step 6 -8. Luma3DS should now be functioning normally, you can remove the `firmware.bin` from the `luma` folder and delete the .cia files you used - ## I have issues with GBA/DS/DSiWare games and I have installed a patched AGB/TWL FIRM cia in the past There have been some reports of pre-patched AGB/TWL FIRMs interfering with Luma3DS' built-in patching.