Hacking How would I go about linking my NNID to my sysNAND?

[ultramario1998]

Spoiler

My system specs

n3ds xl - sysnand 9.2.0-20U, reinand 10.5.0

When attempting to connect to any Nintendo Network services, I'm getting error 022-2634. Did some research, and found out that this is caused by having one's NNID linked to the emunand but not the sysnand. Problem is, Nintendo wants me to update to do that nowadays.

What can I do to fix this? I know that I can upgrade my NATIVE_FIRM to get around the onlinelock, but that would also result in a frankenfirmware. (and, as I understand it, limit my ability to access the HBL and thus my emunand) Does anybody have any suggestions of what I can do to fix it?

 

[lpchaim]

There's a guide around here that worked beautifully for me when that happened, I think it was this one but it has been a while. For future reference use tinyformat if you ever need to format a linked system again, since it skips the NNID unlinking part (alongside formatting, folder deletion and pretty much everything else haha) and as a result you don't have to go through all this trickery to relink. Unless you want all that to happen, of course.

 

[Xenosaiga]

@ultramario1998, if your NNID is linked to emunand you could use Decrypt9wip NNID dump to copy NNID.

First launch Derypt9 and then go to emunand settings and select dump NNID.
Then back to Decrypt9 main menu and select system and then inject NNID that you just backed up into the system.

Hope it works for you!

 

[lpchaim]

@ultramario1998, if your NNID is linked to emunand you could use Decrypt9wip NNID dump to copy NNID.

First launch Derypt9 and then go to emunand settings and select dump NNID.
Then back to Decrypt9 main menu and select system and then inject NNID that you just backed up into the system.

Hope it works for you!

Wow, that sounds mighty convenient and easy. Had no idea this was possible.
EDIT: Also,did I misunderstand the OP? I assumed OP's emunand was borked, but reading Xenosaiga's answer it could be that you wanted to connect with sysnand instead of emunand?

 

[Xenosaiga]

Wow, that sounds mighty convenient and easy. Had no idea this was possible.
EDIT: Also,did I misunderstand the OP? I assumed OP's emunand was borked, but reading Xenosaiga's answer it could be that you wanted to connect with sysnand instead of emunand?

No. For some reason they want to re-link NNID to sysnand.

Honestly if @ultramario1998 is trying to connect to eshop on emunand then they need to do it completely different. Steps are similar but noticeable different.

1. Backup emunand with Decrypt9.
2. Install tinyformat.cia to emunand.
3. Run tinyformat in emunand.
4. Setup emunand as if new and link NNID.
5. Backup emunand NNID using decrypt9.
6. Restore emunand from your earlier backup.
7. Restore your backed up NNID to your emunand.
8. Profit!

I hope this helps. Also I take no liability if you mess up somehow.

And if you must know this is how I fixed my own error. So these steps are from what I did and I have been spreading the word on how to fix.


Further info found here: https://gbatemp.net/threads/solution-for-people-with-the-022-2634-error.413546/#post-6088178

Original fix below:

Spoiler

What you will need:
Tiny Format
https://gbatemp.net/threads/release-tinyformat.391635/
Decrypt9WIP
https://gbatemp.net/threads/download-decrypt9-open-source-decryption-tools-wip.388831/
Emunand9
https://gbatemp.net/threads/release-emunand9tool-open-source-emunand-formatter-manager.405921/

1. Backup emunand with Emunand9
2. Format emunand using tiny format
3. Setup nnid after format finishes
4. In Decrypt9 under emunand options, dump nnid
5. Restore emunand from backup
6. Inject nnid backup into restored emunand

This is how I fixed my issue. Hope it helped.