Hacking [Tutorial] How to access NNID and eShop on 9.5.0-23 Emunand

[Juiss]

I installed the (U) NVer CIA with the version in the OP, but I am getting error code 022-2634 (An error has occurred.) when running eShop or other app that requires the NNID.

You have to format your emuNAND and link your NNID
Follow these steps:

Didn't you format your EmuNAND and link your NNID already?
If you didn't, this is what you have to do (you wont lose anything at all):
1. Backup your EmuNAND using Emunand9 or the Emunand Tool
2. Copy your Nintendo 3DS directory from the SD card to your PC
3. Boot into EmuNAND, open System Settings and choose Format
4. Boot back into EmuNAND and go through setup
5. Go to System Settings and sign into your NNID (now it will be properly linked to the system ID)
6. Inject the previously back upped EmuNAND to your SD card
7. Move the Nintendo 3DS directory back

And there. Your NNID is now active on your system and you should no longer receive the error.

 

[gudenau]

To bad I updated my eShop a while ago. :-/

 

[infinete]

Installed Title ID: 000400DB20016102 Version: 448 on my N3ds 9.5 emunand, ran the Hans spoofer, and it worked! Thanks! Now if only retail cartridges could be spoofed like this :/, the dream .

 

[Wire]

I still get Error Code: 022-2634 after setting up my NNID from formatting emunand and reinjecting it and all that.
Edit: Off to bed. Will see this probably tomorrow afternoon since that's when I have free time.

 

[Shadowfied]

Okay so I did manage to get it working on rx as well. As stated in the first post, TIGER should not be installed for CFW, so I used FBI and removed the new TIGER installed (if you're gonna do this, have a backup of your emunand to be safe) which I only realized after the fact, is the entire eShop title, so I grabbed the original 9.5 TIGER from the 9.5 update archive, installed that back, then only installed the NVER, and now I can access and download from the eShop from both rx and GW, although I have to use HANS even for GW mode. Sleep mode still does not work.

 

[Aroth]

All of you that keep getting 022-2634 after unlinking/updating, when you format the system to unlink are you formatting sysnand or emunand?

--------------------- MERGED ---------------------------

Okay so I did manage to get it working on rx as well. As stated in the first post, TIGER should not be installed for CFW, so I used FBI and removed the new TIGER installed (if you're gonna do this, have a backup of your emunand to be safe) which I only realized after the fact, is the entire eShop title, so I grabbed the original 9.5 TIGER from the 9.5 update archive, installed that back, then only installed the NVER, and now I can access and download from the eShop from both rx and GW, although I have to use HANS even for GW mode. Sleep mode still does not work.

Yeah sleep mode will only work for GW users who installed the updated eshop. It has to do with how HANS launches titles, you can't exit back to the home menu once you do, and if you reboot the system and return to the home menu then the system doesnt know the url to connect to anymore.

 

[Shadowfied]

All of you that keep getting 022-2634 after unlinking/updating, when you format the system to unlink are you formatting sysnand or emunand?

--------------------- MERGED ---------------------------


Yeah sleep mode will only work for GW users who installed the updated eshop. It has to do with how HANS launches titles, you can't exit back to the home menu once you do, and if you reboot the system and return to the home menu then the system doesnt know the url to connect to anymore.

First, regarding the unlinking. Just to be clear, what we're unlinking is the NNID, not the NANDS, just to avoid confusion. Your NANDS should already be unlinked at this point. When you set up EmuNAND for the first time, it cloned your then current SysNAND, and as I said, at this point, SysNAND should had been formatted again so that the NANDS are not linked. Now, the EmuNAND holds your NNID but in an unuseable state. Therefore you must unlink the NNID from your EmuNAND, which is done by formatting it through the SYSTEM SETTINGS. First of course, extract your EmuNAND and Nintendo 3DS folder, then once you've formatted and re-linked the NNID just inject it back and your Nintendo 3DS folder. Sory if I went overboard with the explanation.

Regarding the eShop, sleep mode doesn't work in Gateway mode either (even without HANS, just using the Multi patcher then opening eShop) for me.

 

[Aroth]

First, regarding the unlinking. Just to be clear, what we're unlinking is the NNID, not the NANDS, just to avoid confusion. Your NANDS should already be unlinked at this point. When you set up EmuNAND for the first time, it cloned your then current SysNAND, and as I said, at this point, SysNAND should had been formatted again so that the NANDS are not linked. Now, the EmuNAND holds your NNID but in an unuseable state. Therefore you must unlink the NNID from your EmuNAND, which is done by formatting it through the SYSTEM SETTINGS. First of course, extract your EmuNAND and Nintendo 3DS folder, then once you've formatted and re-linked the NNID just inject it back and your Nintendo 3DS folder. Sory if I went overboard with the explanation.

Regarding the eShop, sleep mode doesn't work in Gateway mode either (even without HANS, just using the Multi patcher then opening eShop) for me.

You are half right.

"When you set up EmuNAND for the first time, it cloned your then current SysNAND, and as I said, at this point, SysNAND should had been formatted again so that the NANDS are not linked." This part is correct and what people should be doing.

"Now, the EmuNAND holds your NNID but in an unuseable state." If this is happening to people that unlinked their nands by formating sysnand, something else is going wrong.

"Therefore you must unlink the NNID from your EmuNAND, which is done by formatting it through the SYSTEM SETTINGS." I suspect what is happening is people are doing this and then when they try to relink their NNID, they get the error.

edit:

I am speaking from personal experience here.

I originally transferred my O3DS XL to my N3DS XL (with my nnid), then I set up emunand, then i formatted my sysnand to unlink the nands. At this point my emunand worked perfectly fine with no issues what so ever. This is how I know if people do it in that order they should not get the nnid error.

 

[Shadowfied]

"Now, the EmuNAND holds your NNID but in an unuseable state." If this is happening to people that unlinked their nands by formating sysnand, something else is going wrong.

"Therefore you must unlink the NNID from your EmuNAND, which is done by formatting it through the SYSTEM SETTINGS." I suspect what is happening is people are doing this and then when they try to relink their NNID, they get the error.

The unusable NNID happened on both my O3DS and N3DSXL even after formatting SysNAND.

If people try to relink their NNID after formatting EmuNAND, it will always work, unless the NNID is somehow linked somewhere else.

 

[Aroth]

The unusable NNID happened on both my O3DS and N3DSXL even after formatting SysNAND.

If people try to relink their NNID after formatting EmuNAND, it will always work, unless the NNID is somehow linked somewhere else.

You do realize that the nnid link consists of two parts right? the system and the server. Formatting the system allows another NNID to be linked to it, but the original NNID is still treated as linked by the server which is why it throws 022-2634 when you try and use it on a new system.

 

[Shadowfied]

You do realize that the nnid link consists of two parts right? the system and the server. Formatting the system allows another NNID to be linked to it, but the original NNID is still treated as linked by the server which is why it throws 022-2634 when you try and use it on a new system.

Yes...have I said elsewise?

 

[Aroth]

Yes...have I said elsewise?

You are strongly implying it by stating that if you have a system linked to a NNID and format it, then you can immediately relink the same NNID to the same system. It does not work that way 99% of the time.

I remember the original emunand/cfw tutorials told users that if they wanted to unlink their nands they should enter system settings on their emunand and format it. This always seemed weird to me because of the NNID situation which is why i did the format on my sysnand instead. I strongly suspect 90% or more of the users in these threads reporting 022-2634 did just that. They formatted their emunand via system settings to unlink the nands.

 

[Shadowfied]

You are strongly implying it by stating that if you have a system linked to a NNID and format it, then you can immediately relink the same NNID to the same system. It does not work that way 99% of the time.

I remember the original emunand/cfw tutorials told users that if they wanted to unlink their nands they should enter system settings on their emunand and format it. This always seemed weird to me because of the NNID situation which is why i did the format on my sysnand instead. I strongly suspect 90% or more of the users in these threads reporting 022-2634 did just that. They formatted their emunand via system settings to unlink the nands.

As I said, I formatted SysNAND after setting up my EmuNAND, which unlinks it from SysNAND, then format EmuNAND which unlinks it from EmuNAND. No more links. That's what I did and what worked on both my systems.

 

[Aroth]

As I said, I formatted SysNAND after setting up my EmuNAND, which unlinks it from SysNAND, then format EmuNAND which unlinks it from EmuNAND. No more links. That's what I did and what worked on both my systems.

Except thats wrong. Idk why it worked for you but it doesnt work for 99% of people.

Let me try explaining it with examples.

You have O3DS with your NNID linked to it. You decide to buy a N3DS and you want to sell your old one to pay for it. So you sell it to me for $100 and use that towards your N3DS. I get home and go about setting it up and link my own NNID to the freshly formatted system. Now, according to you, since you just formatted the O3DS (and I just linked my own to it) your NNID should unlinked and available for use in another system. And for most people this would seem like common sense.

But that's wrong.

You get home and unpack your N3DS and go to link your NNID. Suddenly a wild 022-2634 appears. That format you did wasn't very effective. You now have to contact Nintendo and tell them you sold your O3DS and went to link your NNID to your N3DS but got an error. They get some info from you and say they will take care of it and you will get an email in 72 hours informing you the transfer was completed. Three days later you get the email and try to link your NNID again. Your call to Nintendo was super effective. The wild 022-2634 has been defeated.

That is how it works just for trying to transfer to a new system. Nintendo themselves have said that a NNID can only ever be linked to a single 3DS system at a time and the only way to transfer it is via a system transfer. What Nintendo does when you call them is essentially a system transfer without the game/save data, which you complete by logging into your NNID again on the new system after they email you.

Now tell me, why would this be ANY different for dealing with emuands and sysnands which when unlinked are treated as two different 3ds systems by the software?

 

[Shadowfied]

I'm talking about the same system though. Then it WILL work. It's not linked to the ID of the Sys or Emu NAND, it's linked to the actual consoles ID. Yes, if you're gonna be linking it to another system it's not gonna work, you're gonna have to use System Transfer. I guess we are on the same page then. My bad.

 

[Aroth]

I'm talking about the same system though. Then it WILL work. It's not linked to the ID of the Sys or Emu NAND, it's linked to the actual consoles ID. Yes, if you're gonna be linking it to another system it's not gonna work, you're gonna have to use System Transfer. I guess we are on the same page then. My bad.

If what you are saying was true, then no one would be getting that error, because that error ONLY happens when you try to link a NNID that is already linked to a system in nintendo's servers.

 

[Shadowfied]

If what you are saying was true, then no one would be getting that error, because that error ONLY happens when you try to link a NNID that is already linked to a system in nintendo's servers.

Well, in that case I guess I was just lucky and have no idea what I'm talking about, seems odd that it worked twice for me though and apparently for other people that were having the error.

 

[Audioboxer]

I tried to install the NVER version 448 on emunand 9.5 running rtxtools through FBI and I get install failed. Possible corrupt download or something else? I used 000400DB20016102 as I have a EU/UK N3DS.

Thanks

 

[Shadowfied]

I tried to install the NVER version 448 on emunand 9.5 running rtxtools through FBI and I get install failed. Possible corrupt download or something else? I used 000400DB20016102 as I have a EU/UK N3DS.

Thanks

Did you install to SD or NAND?

 

[RocketRobz]

eShop now works, but when I try to click on a game to view, I get error code 007-2404 (An error has occurred.). The error doesn't happen when I use HANS to run eShop. Is this normal?