Note: Some users have reported that updated the emuNAND created in this guide causes the sysNAND to be updated. Others have reported success with the same process. Tread carefully, and know that neither I nor any developer of the tools used in this guide are responsible for what happens. Requirements SD Card (preferably blank, if not make sure to take a full backup) A PC with an SD card reader A 4.5 or lower 3DS with mset already installed using Gateway's Installer file. Software Download Links: Dev Menu CIA (Look for either BigBlueBox CIA or GovanifY’s CFW. Google is your friend, the file name will be either BigBlueBox.cia or DevMenu_2x.cia) Palantine CFW PBT CFW Network Scanner Gateway Launcher.dat rxTools + firmware.bin (cdn_firm.exe in the folder) + slot0x25KeyX.bin (Google) First off, make sure the CIAs you have planned to install using this method are clean. Clean means that the CIA has been ripped from a 3DS bundle. These CIAs are clearly marked on the sites that you download them on. If you have doubts if a CIA is clean, it is likely not. Format your SD card. It should be completely blank. Make sure to take a backup if you were using it for something else. In the "SD Card" folder from Palantine's CFW, you will find files such as Launcher.dat. Copy all of these onto the SD Card. Now, copy the boot.bin from PBT-CFW. There should already be a boot.bin from Palantine's CFW - delete this one and make sure you are running PBT CFW. Put the SD into the 3DS. Start the system, and let it create software management information. Now power down the system, and put the SD back into your computer. Now, in your SD card, there should be a Nintendo 3DS folder. Open it, and open the folder inside that. There should be another, so open that too. You should see a exdata folder. Make a new folder (not inside the exdata folder, but in the same directory as it) called “dbs”. Go into the folder and make a blank text file, named “title.db” or “import.db”. Doesn’t matter which. Put the SD back into the 3DS. Now, navigate to Settings --> Other --> Profile. WHILE HOLDING THE L BUTTON, tap DS Profile. The screen should be a DARK blue on the top. As with regular CFW, the bottom screen should ideally flash white for a moment and then load the CFW. If it doesn't, hold power to reboot the system and repeat step 9. Make sure to hold L. Now, once you’ve gotten into PBT-CFW, you’ll need your 3DS’ IP Address. You can use the tool you downloaded earlier (the network scanner) to find the devices from Nintendo. Note the IP. (usually looks like 192.168.1.1xx). Copy the DevMenu CIA you downloaded earlier into the Palantine CFW folder with run.bat. Edit the run.bat file in the Palantine CFW folder. Replace the DevMenu_2x.cia part with the name of your CIA, and the IPTOMODIFY with your IP. Code: installcia IPTOMODIFY 1 DevMenu_2x.cia Code: installcia 192.168.1.155 1 DevMenu_2x.cia Now execute the run.bat by double clicking it. It should return a result code of 0. If it doesn't, repeat steps 5-14. If it fails to connect, make sure the IP is correct and the 3DS is connected to the internet. You should now have DevMenu installed onto the 3DS. Without powering off the system, remove the SD and put it into your computer. Copy the clean CIAs you wish to install. Insert the SD back into the system, and go into Dev Menu. Install CIAs as normal. Once the CIAs have been installed, power off the system. Remove the SD, and insert it into your computer. Backup the Nintendo 3DS folder. Now, delete the Launcher.dat. Copy over the Gateway Launcher.dat. Insert the SD into the system. Use the DS Profile exploit like earlier to boot into Gateway. Use the "Format EmuNAND function". Your SD will be wiped. Once that is done, power off the system. Remove the SD and delete Launcher.dat from your computer. Copy the rxTools.dat file, plus firmware.bin, plus the KeyX file. Also copy back the Nintendo 3DS folder. Navigate to the rxTools thread linked above on your computer, and place the SD back into the system. Power on, and press L or R to be taken to the camera. Tap the QR button and scan the code in the thread. Let it take you to the site. rxTools will load. Boot into rxMode. Go into Settings. Ensure it says RX-E 4.x. If it says something else, power off and try steps 23 onward again. This is the dangerous part. Update the emuNAND in System Settings. Some users have reported success and others have updated their sysNAND. Personally, I have found that if you had the update nag on your 4.5 sysNAND, you will end up updating sysNAND. In that case, power off the system, remove the SD, and follow the steps in this thread. Note that this may not solve the issue, and you might end up with an updated sysNAND. At this point, you should have a 4.5 sysNAND and an emuNAND bootable at version 9.6, with the CIAs installed. Boot into it, and launch every game once. Open the eShop and check downloaded software just for good measure. I personally did not do this step, but it is recommended. Now, get another SD Card. This could be the SD you used to make another emuNAND. However, it won't work if this SD has the emuNAND unlinked from your sysNAND. If they're unlinked, you cannot merge these two emuNANDs. You will have to stick with 1 SD for the emuNAND we just made, and one with the one you already had. If your NANDs were linked, you can redownload the legit CIAs from the eShop on your emuNAND. Or, you can format emuNAND again like before and redownload them. If there are any issues with the guide, please inform me. However, these steps should be relatively safe except for the update part, which is a mixed bag. Check the rxTools thread to see the reports on updating sysNAND accidentally.