Nintendo Handheld Console - New Nintendo 2DS XL - Black and Lime Green - Pre-installed with Mario Kart 7 (Nintendo 3DS)

Product Information

You'll want to basically remove anything not in that picture. You should only have either auto.3dsx or less.3dsx, depending on if you went ahead and setup lesshax. Both are shown in the image for reference only. I'm doing this right now, since the ropbin was replaced (and i think this is the menuhax configuration entry) how do i know what buttons to press in case i want to drop in sysnand? ihaveamac's version should just be a ninjhax 2.7 payload edited to remove the debug//colors, don't think it actually improves bootrate. HBL.cia will rely on the NAND version of where it's launched. So from Emu 11.0 on an o3DS USA console, it'll use "hblauncherloader_otherapp_payload_OLD-11-0-0-33-USA.bin" - It'll also rely on boot.3dsx. Because of this, it's not really recommended you rename your CFW file to boot.3dsx, as launching HBL.cia will just cause it to load the CFW boot.3dsx file. Copy the Decrypt9WIP folder from the Decrypt9WIP zip to the /3ds/ folder on your SD card. (Should have already been done previously, but just in case)

How do I update Decrypt9WIP in my 2DS? I have the previous version 20160607 installed in my system. We are now done with this part. Press Start to reboot. Read the next short part, to get an idea of how to install your GBA//DSiWare .CIA games. Since our Type2 menuhax config is set to not trigger when L is held and when launching Luma3DS, while holding L, tells Luma3DS to boot into SysNAND. What this results in is allowing us to boot into a patched SysNAND, from where we can launch the injected FBI.cia, to install our GBA//DSiWare .cias. Optional) Customize CtrBootManager to however you want using the wiki for an explanation of what every option does: https://github.com/OperationNT414C/CtrBootManager/wiki/CtrBootManager-setupCopy and merge the 3DS folder from the EmuNAND9 zip to the root of your SD card. (Should have already been done previously, but just in case) Go through initial setup without linking your Nintendo Network ID, you want it to remain linked only to RedNAND to prevent issues.

If you have followed this guide completely (apart from the optional parts) to this point, then you should have a short 3 second window at boot time, to load the Homebrew Menu. Do that now. With the ropbinpayload replaced with the one from the lesshax, it'll now boot less.3dsx at boot time. Or find custom ones here: https://gbatemp.net/threads/menuhax-2-0-custom-main-screen-images.401528/ The patched sysNAND is only really useful for people who want to play GBA//DSiWare games. The part titled "~[Optional] Injecting FBI into SysNAND (For GBA//DSiWare Games)~" covers all the steps in regards to that and goes a bit more into detail on this.Boot into the Homebrew Launcher. (If you have followed this guide, you should be autobooting into the Homebrew Launcher via menuhax) If you have followed this guide completely to this point, then you should have a short 3 second window at boot time, to load Decrypt9WIP. Do that now. Simplest? Probably using the lesshax payloads and renaming luma.3dsx to less.3dsx. Without using lesshax, you'd have to use HxD to change the robinpayload to suit your needs.

For this guide, we will be using Type 2, on the Left Trigger (change this to whatever you prefer, but there is a reason for this which I'll explain now).So far, we have autoboot menuhax setup, as well as our Luma3DS configured correctly, and our RedNAND updated to the latest system version. But we don't have CIA Manager. So for this part, we'll be properly injecting FBI into our RedNAND for use as our initial .CIA manager. If you have followed this guide as well as the previous half of this optional part, with all my recommendations to the letter, then you should have a short 3 second window at boot time, where you see the CtrBootManager menu. Very good guide Good job on writing this all out, even if most of the stuff was adapted from plailects, I can tell you put a lot of effort into it <3 From here, you'll have to decide how you want menuhax to activate. I recommend Type 2 autoboot. Where menuhax will basically trigger so long as it doesn't match the button value you designate. You'll need to actually boot into SysNAND to see the theme. Either boot into SysNAND by holding L at boot time, or by launching Luma3DS from CtrBootManager while holding L. (This is assuming you followed my recommendations)