Tutorial
Updated
Unlinking EmuNAND and fix 002-2634
I started to decorate my O3DS 10.3 EmuNAND home menu with badges but every time I reboot into emuNAND, all icons, that weren't present in the sysNAND before setting EmuNAND up, pops out of the folders, replace badges and the known unwrapping bug. Besides that, sysNAND will reset your home menu theme if the sysNAND doesn't know this theme. All this can be solved by unlinking the NAND's.
BUT the big other isssue by unlinking them is that your NNID will be not linked to you 3DS anymore, your 3DS kinda „logs out“ your NNID at the formating process. This process information is remebered in your NNID account, say, Nintendo servers. That's why you need internet connection for formatting the device.
I spent an hour of solving this problem, so that's why I'm writting down my steps for correct unlinking:
1. Remove SD-Card and backup all data (or at least the "Nintendo 3DS folder), EmuNAND too! Use https://gbatemp.net/threads/emunand-tool-release-and-support-thread.359239/
2. Boot sysNAND without SD-Card and go to Settings → Formating.
3. Format! (It will ask for an internet connection (for logging off NNID from this device), but don't worry, it WILL NOT update!) - Your NAND's are after formating unlinked!
Don't forget to remove Smealum's DNS!
4. Setup you device again, but spare your try for logging in your NNID, you have to update FW for logging in, which no one of us wants.
5. Put SD-Card back in
At this point, you can't even use your NNID in the emuNAND, because Nintendo servers remebered your logging off process while formating, that's why you get the error 002-2634.
We need our 3DS on newest FW, not logged in, to log into our NNID
6. Boot into EmuNAND (rxTools, CakeFW, ReiNAND etc.)
7.Format your EmuNAND! (You made a backup of your SD-Card and emuNAND on it, so don't worry.
Don't forget to remove Smealum's DNS!
8. Boot into EmuNAND after formating, set up and log into your NNID – that should work know.
Note: I suggest to use Smealum's DNS 107.211.140.065, do it while you are setting up your device. This DNS blocks Nintendo's update server.
9. Restore SD-Cards data and EmuNAND.
10.Done!
Now you have an unlinked EmuNAND, fully NNID/eshop access on it and no homemenu interference by your sysNAND.
Contra: You can't log in SysNAND into you NNID account (which is not important either, because you are on a old FW that can't use ehop) and you will lost all data on your SysNAND, but if you want to keep your saves and cia's, do a backup with SDF and a cia manager and restore after unlinking
Tested on 9.2.0-20E O3DS / EmuNAND 10.3-x
BUT the big other isssue by unlinking them is that your NNID will be not linked to you 3DS anymore, your 3DS kinda „logs out“ your NNID at the formating process. This process information is remebered in your NNID account, say, Nintendo servers. That's why you need internet connection for formatting the device.
I spent an hour of solving this problem, so that's why I'm writting down my steps for correct unlinking:
1. Remove SD-Card and backup all data (or at least the "Nintendo 3DS folder), EmuNAND too! Use https://gbatemp.net/threads/emunand-tool-release-and-support-thread.359239/
2. Boot sysNAND without SD-Card and go to Settings → Formating.
3. Format! (It will ask for an internet connection (for logging off NNID from this device), but don't worry, it WILL NOT update!) - Your NAND's are after formating unlinked!
Don't forget to remove Smealum's DNS!
4. Setup you device again, but spare your try for logging in your NNID, you have to update FW for logging in, which no one of us wants.
5. Put SD-Card back in
At this point, you can't even use your NNID in the emuNAND, because Nintendo servers remebered your logging off process while formating, that's why you get the error 002-2634.
We need our 3DS on newest FW, not logged in, to log into our NNID
6. Boot into EmuNAND (rxTools, CakeFW, ReiNAND etc.)
7.Format your EmuNAND! (You made a backup of your SD-Card and emuNAND on it, so don't worry.
Don't forget to remove Smealum's DNS!
8. Boot into EmuNAND after formating, set up and log into your NNID – that should work know.
Note: I suggest to use Smealum's DNS 107.211.140.065, do it while you are setting up your device. This DNS blocks Nintendo's update server.
9. Restore SD-Cards data and EmuNAND.
10.Done!
Now you have an unlinked EmuNAND, fully NNID/eshop access on it and no homemenu interference by your sysNAND.
Contra: You can't log in SysNAND into you NNID account (which is not important either, because you are on a old FW that can't use ehop) and you will lost all data on your SysNAND, but if you want to keep your saves and cia's, do a backup with SDF and a cia manager and restore after unlinking
Tested on 9.2.0-20E O3DS / EmuNAND 10.3-x
Last edited by artur3004,