I am running 4.2.0 on a O3DS that was downgraded with gateway. I was following the guide for fixing black screens when booting Luma3DS and now I can no longer boot NinjHax, it just crashes.
I installed the NATIVE104.cia on my 4.2.0 sysNand. Any idea how to fix this?
I get a black screen 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):
- Get the NTR FIRMs package from here and the NAND FIRMs package from here
- Copy the O3DS firmware.bin file from the NTR FIRMs package to the luma folder
- 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
- Hold the SELECT button to open the Luma3DS configuration menu and make sure theSysNAND 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
- 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
- Install the .cia files you copied in step 3
- If you have other NANDs to fix, repeat the process from step 3 to step 6
- Luma3DS should now be functioning normally, you can remove the firmware.bin from theluma folder and configure the SysNAND is updated option as needed
I installed the NATIVE104.cia on my 4.2.0 sysNand. Any idea how to fix this?