Hacking Problems unlinking nands

[termitavee]

I know there're hundreds of post like this but I couldn't solve it so I'll ask here.

first, I have a n3ds 9.2 whith 10.4 emunand+reinand

The steps (if I'm not wrong) are:

1. formating sysnand (taking the sd before)
2. (inserting the sd) setting up the formated sysnand
   
3. log in the nnid on sysnand

The problem is that the 3ds doesn't let me introduce the nnid because the console isn't update.

Another time (i have installed emunan a few times xD) I just left nands linked but when I tried to update a game I got the 022-2634 and all my games from emunand dissapeared from sysnand (but they weren't unlinked).

(I'll update this post whit the possible solutions and the one that helped me)

EDIT: SOLVED, there were two problems: the first, I was confusing a few things, (I don't know why I was trying to sign up in sisNand with no reason); the second one was the typical 022-2634

As KhaderWelaye said, it is solved formating emunand, upgrading it and signing up your nnid, then restore a backup of your previous emunand and everithing correct

I've ran into this as well after unlinking my NAND by formatting the SysNAND. Here is how I got around this problem primarily using the EmuNAND9 tool:

• Dump EmuNAND to EmuNAND.bin
• Clone SysNAND to EmuNAND (Referred to as EmuNAND2 henceforth)
• Boot EmuNAND2 using method of choice
• Update EmuNAND2 and login with NNID
• Clone EmuNAND.bin to EmuNAND
• Boot original EmuNAND, update if necessary, login with NNID and enjoy!

I started this process with 9.2 SysNAND / 9.2 EmuNAND and ended this process with 9.2 SysNAND and 10.4 EmuNAND. Loaded up the eShop no problem.

I did this using my existing MenuHax Coldboot Setup, I just held L after ReiNAND had launched. It's a little scary to update since it's a little hard to tell if you're in SysNAND or EmuNAND2 after you've cloned, but worst-case scenario you have a NAND backup on-hand!

Another solution is as Goomby said, to use TinyFormat (which prevents thw 022-2634 error)

 

[Robmead23]

Normally people log in on emunand and it works

 

[TeconMoon]

I've ran into this as well after unlinking my NAND by formatting the SysNAND. Here is how I got around this problem primarily using the EmuNAND9 tool:

• Dump EmuNAND to EmuNAND.bin
• Clone SysNAND to EmuNAND (Referred to as EmuNAND2 henceforth)
• Boot EmuNAND2 using method of choice
• Update EmuNAND2 and login with NNID
• Clone EmuNAND.bin to EmuNAND
• Boot original EmuNAND, update if necessary, login with NNID and enjoy!

I started this process with 9.2 SysNAND / 9.2 EmuNAND and ended this process with 9.2 SysNAND and 10.4 EmuNAND. Loaded up the eShop no problem.

I did this using my existing MenuHax Coldboot Setup, I just held L after ReiNAND had launched. It's a little scary to update since it's a little hard to tell if you're in SysNAND or EmuNAND2 after you've cloned, but worst-case scenario you have a NAND backup on-hand!

 

[termitavee]

I've ran into this as well after unlinking my NAND by formatting the SysNAND. Here is how I got around this problem primarily using the EmuNAND9 tool:

• Dump EmuNAND to EmuNAND.bin
• Clone SysNAND to EmuNAND (Referred to as EmuNAND2 henceforth)
• Boot EmuNAND2 using method of choice
• Update EmuNAND2 and login with NNID
• Clone EmuNAND.bin to EmuNAND
• Boot original EmuNAND, update if necessary, login with NNID and enjoy!

I started this process with 9.2 SysNAND / 9.2 EmuNAND and ended this process with 9.2 SysNAND and 10.4 EmuNAND. Loaded up the eShop no problem.

I did this using my existing MenuHax Coldboot Setup, I just held L after ReiNAND had launched. It's a little scary to update since it's a little hard to tell if you're in SysNAND or EmuNAND2 after you've cloned, but worst-case scenario you have a NAND backup on-hand!

A little confusing the first time but ok, I'll try (I have backup of boths nands xD).

 

[AceEvo55]

Whether or not it is "required" to log into emunand with your NNID, that's where I would encourage you to log in as that's where you'll want your games to download (that way you can update them, and also limits your reason for using sysnand, and by extension, potentially making a mistake within sysnand).

 

[TeconMoon]

Whether or not it is "required" to log into emunand with your NNID, that's where I would encourage you to log in as that's where you'll want your games to download (that way you can update them, and also limits your reason for using sysnand, and by extension, potentially making a mistake within sysnand).

Correct, logging into EmuNAND with your NNID is what we want to do.

When you format your system to unlink the Sys/EmuNAND, during the format process your system is disassociated from your NNID. If you unlink by formatting EmuNAND, there's no connection problems afterwards in EmuNAND but you lose anything you had. If you unlink by formatting SysNAND, EmuNAND thinks that the system is still linked with your NNID when Nintendo's Servers report differently, which results in the 022-2634 error code when you try to sign into anything with your NNID.

Getting around this requires you to sign in with your NNID using SysNAND, which knows that it's not linked to a NNID, so that Nintendo's Servers report that your NNID is linked to your console. After you perform this task, you can log in with your NNID on your EmuNAND.

The main problem here is you can't log in using your NNID on SysNAND unless you update, and updating breaks all your exploits. That's why it's necessary to go through all the silly trouble of copying SysNAND back to EmuNAND, updating, logging in, and then putting your original EmuNAND back.

 

[Goombi]

Simple question: doesn't TinyFormat avoid this exact trouble?
I used it on 2 of my 3 setup 3DS and that did the trick.

 

[termitavee]

Ok, officially this thread is for me a noob thread xD I have read it before but I didn't understood it correctly.

Thanks people.

 

[TeconMoon]

Simple question: doesn't TinyFormat avoid this exact trouble?
I used it on 2 of my 3 setup 3DS and that did the trick.

You're right, it probably would! Didn't even know that existed haha