So it's been mentioned and done before, but I've see no definitive guide on how to do a full sysNAND to sysNAND System Transfer by taking advantage of NTR CFW's firmware spoofing mechanisms. After asking questions and researching some threads that were pointed out to me, I wanted to post the full steps I took to get my Old 3DS sysNAND properly transferred to my New 3DS. Theres a Q/A section below the guide, and I can add to it if more people ask.
Also, now that Ninjhax 2.0 has been released, I'm sure it won't be long before we can do this kind of operation between systems that are on >9.6 - But I won't get ahead of myself.
This is my first go at a guide and made it as complete as I could - So here we go!
Requirements
1. Both systems sysNAND on version 9.0-9.2
2. Project Pokemon for O3DS
3. NTR CFW on N3DS
4. NTR Debugger
***DISCLAIMER***
I highly recommend taking sysNAND backups of both units before doing this. I'd also recommend restoring them over your current NAND with the backup to ensure you have a good copy. If you continue you are doing so on your own and I take no responsibility if something goes wrong in the transfer or your system(s) become bricked.
Procedure
1. If you had unlinked NAND's, you must restore your previous NAND to your system.
2. Run Project Pokemon firmware spoof on your O3DS
2. Run NTR Mode on your N3DS
3. Start the NTR Debugger on your N3DS
4.Verify both systems can log into the eShop and you do not get a system update prompt. If you get the update prompt, you are not running NTR or the Project Pokemon spoofs corrently on your units. Read above to fix.
I performed a local wireless transfer, transferring all of my SD card data over wireless (took forever), but can vouch it worked without issue. If you want a speedier transfer, you can do a local copy of your SD card data on your computer.
Question/Answer:
Q: "Why not just transfer your O3DS emuNAND to your N3DS emuNAND?"
A: You can, and there is a simpler method using the MultiPatcher CIA. I however wanted to have a sysNAND backup of my N3DS with my legitimate NNID and purchases. This way if my emuNAND for whatever reason gets royally F'd, I won't lose my NNID along with my purchases and can restore properly to start from square one.
If you're intersted in doing an emuNAND to emuNAND transfer, look here: http://www.maxconsole.com/maxcon_fo...m-Transfer-Old-3ds-to-New-3ds-Gateway-Emunand
Q: Can't I just use the MuliPatcher to do this on sysNAND?
A: No. MultiPatcher is an invalid (non-legitimate eShop purchased) CIA and could cause a bricked system during the transfer to sysNAND. In emuNAND however, this is okay.
Q: What if one of my systems is already on the latest sysNAND?
A: Start the sysTransfer like normal on that system from system settings. Follow the steps for NTR or Project Pokemon on the exploitable system.
Credits:
Ronhero - Helped with providing links and also creating the emuNAND transfer guide over on MaxConsole
The Real Jdbye - Also helped in providing links
motezazer - Project Pokemon guide
NTR CFW Team
tpu, enler, amuro, etc. NTR CFW will not be possible without them.
ChiChou(https://github.com/ChiChou). For designing the logo.
Myria, shinyquagsire23, Zidapi, etc. For testing on various consoles.
Smealum, for the amazing 'ninjhax' solution that runs unsigned code on 3DS consoles.
Also, now that Ninjhax 2.0 has been released, I'm sure it won't be long before we can do this kind of operation between systems that are on >9.6 - But I won't get ahead of myself.
This is my first go at a guide and made it as complete as I could - So here we go!
Requirements
1. Both systems sysNAND on version 9.0-9.2
2. Project Pokemon for O3DS
3. NTR CFW on N3DS
***DISCLAIMER***
I highly recommend taking sysNAND backups of both units before doing this. I'd also recommend restoring them over your current NAND with the backup to ensure you have a good copy. If you continue you are doing so on your own and I take no responsibility if something goes wrong in the transfer or your system(s) become bricked.
Procedure
1. If you had unlinked NAND's, you must restore your previous NAND to your system.
- You could transfer emuNAND to a target sysNAND, but I would recommend a clean NAND with no invalid/custom CIA's installed as they could brick the target system.
- Copy NAND backup to your SD card if it is not present - Name it NAND.bin if not currently
- Launch GW menu
- Navigate to the far right and highlight "Downgrade System"
- Hold "Up+A" and you will be prompted to restore using a NAND backup already present on the SD card.
- OLD 3DS METHOD
- Download the code.bin and code.c from step 2 above
- Copy them to the root of your SD card
- Launch the web browser
- Clear cookies and history
- Go to loadcode.projectpokemon.org
- Wait for the load bar and the message "failed to load" to disappear
- Press Home
- Done - Check connection to eShop
- Copy ntr.bin to your N3DS's microsd card from link in Step 3 above
- Start Cubic Ninja, Click Edit->QR Code and scan the QR file. (JAPAN.png for JP consoles, and EUROPE_USA.png for other consoles)
- (Hint: If you have installed other exploits already, hold L+R+X+Y at game's main menu to erase the savedata)
- Press A to install the BootNTR
- Turn off your console.
- How to boot into NTR Mode:
- Turn on you console, wait a few seconds before starting Cubic Ninja.
- Click Edit->QR Code, after booted up successfully, the screen will flashes blue and return to Home Menu.
- If it was failed, hold power button to turn off the N3DS and try again.
3. Start the NTR Debugger on your N3DS
- Once your N3DS is running NTR CFW, press "X+Y"
- Scroll to "Enable Debugger" and Press "A"
- If you had CN in the game slot, it may start - Exit to the home screen
- Launch NTR Debugger on your computer - It also requires IronPython to run if you're having trouble - http://ironpython.net/
- Connect the debugger with the command : connect('192.168.XXX.XXX', 8000)
- Replace 192.168.XXX.XXX with your 3DS IP address - If you can't find it, look in your home router's DHCP address table
- Once connected, type the following command (may not work on 8.1J) : write(0x10DD28, (0x00, 0x20, 0x08, 0x60, 0x70, 0x47), pid=0x25)
- Note: If you're having trouble with the NTR/Project Pokemon programs, please read through and use those threads in your troubleshooting. There's no need to fill this guide with questions that may have already been answered in their respective places.
I performed a local wireless transfer, transferring all of my SD card data over wireless (took forever), but can vouch it worked without issue. If you want a speedier transfer, you can do a local copy of your SD card data on your computer.
Question/Answer:
Q: "Why not just transfer your O3DS emuNAND to your N3DS emuNAND?"
A: You can, and there is a simpler method using the MultiPatcher CIA. I however wanted to have a sysNAND backup of my N3DS with my legitimate NNID and purchases. This way if my emuNAND for whatever reason gets royally F'd, I won't lose my NNID along with my purchases and can restore properly to start from square one.
If you're intersted in doing an emuNAND to emuNAND transfer, look here: http://www.maxconsole.com/maxcon_fo...m-Transfer-Old-3ds-to-New-3ds-Gateway-Emunand
Q: Can't I just use the MuliPatcher to do this on sysNAND?
A: No. MultiPatcher is an invalid (non-legitimate eShop purchased) CIA and could cause a bricked system during the transfer to sysNAND. In emuNAND however, this is okay.
Q: What if one of my systems is already on the latest sysNAND?
A: Start the sysTransfer like normal on that system from system settings. Follow the steps for NTR or Project Pokemon on the exploitable system.
Credits:
Ronhero - Helped with providing links and also creating the emuNAND transfer guide over on MaxConsole
The Real Jdbye - Also helped in providing links
motezazer - Project Pokemon guide
NTR CFW Team
tpu, enler, amuro, etc. NTR CFW will not be possible without them.
ChiChou(https://github.com/ChiChou). For designing the logo.
Myria, shinyquagsire23, Zidapi, etc. For testing on various consoles.
Smealum, for the amazing 'ninjhax' solution that runs unsigned code on 3DS consoles.
Last edited by Maximilious,