I have noticed that a lot of people have been getting the 022-2634 error as of late, and it is partially due to the large number of people that are downgrading their 3ds systems. Just as a note, use this guide as a reference. You should be safe when following this tutorial, make sure to read through it.
In the case that something bad does happen, such as your 3DS resetting somehow, I am not responsible. By following this guide you understand these terms and will not hold me accountable for any damages caused.
The reason:
Basically, what happens is if you downgraded to 9.2 and had a NNID linked to your sysnand this would cause this error when you tried to enter eshop/any service that required you to have a NNID. When you created your emunand, both sysnand and emunand shared the same NNID. But when you formatted sysnand to unlink the two nands, you also unlinked the NNID from the console (this is what appears in Nintendo's servers). When you try to try to go into the eshop or similar services, you will get an error because the Nintendo servers still does not know that your NNID is linked to your system.
The solution:
(Big thanks to Ammako who originally posted the solution, but no thread was created specifically for it)
By following these setups, you will relink your NNID to your console (updating Nintendo's servers) and be able to use eshop and similar services again.
1. Put your sd/microsd card into your computer and use emunand tool to backup your emunand. Save this as .bin file (ex emunand.bin). Transfer this file to your computer, and make sure that it is safe. This is your backup of your emunand just in case something bad happens.
2. After this, navigate to your sd card and open up the "Nintendo 3DS" folder and either temporarly move the emunand folder to a different location, or add an underscore "_" to the end of the folder name. The folder name should be made up of various numbers and letters and should be the folder that has a larger size if you have installed cias on it. Optionally, you can make an entire backup of your sd card to be safe. Not required, but could be helpful. Put your sd card back into your 3ds.
3. Boot into emunand and go into system settings. Make sure that you are in emunand and NOT in sysnand. After making sure you are in emunand, format your emunand through system settings. Don't use Gateway or something else to format emunand, just system settings.
4. After your emunand has been formated, launch back into emunand and set it up. Link your NNID to your new emunand. After you have setup your emunand and NNID, turn off your 3ds and remove the sd card. Place the sd card back into your computer.
5. Use emunand tool to restore the backup of your emunand that your created. Also, make sure to move the emunand folder with the numbers and letters back into the "Nintendo 3DS" folder or to remove the "_" from the name.
6. Eject the sd card and boot back into emunand. If everything went right, your emunand should the same as it started. Try to launch eshop or a similar service.
Hopefully this is helpful, and if you have any questions/comments let me know!
In the case that something bad does happen, such as your 3DS resetting somehow, I am not responsible. By following this guide you understand these terms and will not hold me accountable for any damages caused.
The reason:
Basically, what happens is if you downgraded to 9.2 and had a NNID linked to your sysnand this would cause this error when you tried to enter eshop/any service that required you to have a NNID. When you created your emunand, both sysnand and emunand shared the same NNID. But when you formatted sysnand to unlink the two nands, you also unlinked the NNID from the console (this is what appears in Nintendo's servers). When you try to try to go into the eshop or similar services, you will get an error because the Nintendo servers still does not know that your NNID is linked to your system.
The solution:
(Big thanks to Ammako who originally posted the solution, but no thread was created specifically for it)
By following these setups, you will relink your NNID to your console (updating Nintendo's servers) and be able to use eshop and similar services again.
1. Put your sd/microsd card into your computer and use emunand tool to backup your emunand. Save this as .bin file (ex emunand.bin). Transfer this file to your computer, and make sure that it is safe. This is your backup of your emunand just in case something bad happens.
2. After this, navigate to your sd card and open up the "Nintendo 3DS" folder and either temporarly move the emunand folder to a different location, or add an underscore "_" to the end of the folder name. The folder name should be made up of various numbers and letters and should be the folder that has a larger size if you have installed cias on it. Optionally, you can make an entire backup of your sd card to be safe. Not required, but could be helpful. Put your sd card back into your 3ds.
3. Boot into emunand and go into system settings. Make sure that you are in emunand and NOT in sysnand. After making sure you are in emunand, format your emunand through system settings. Don't use Gateway or something else to format emunand, just system settings.
4. After your emunand has been formated, launch back into emunand and set it up. Link your NNID to your new emunand. After you have setup your emunand and NNID, turn off your 3ds and remove the sd card. Place the sd card back into your computer.
5. Use emunand tool to restore the backup of your emunand that your created. Also, make sure to move the emunand folder with the numbers and letters back into the "Nintendo 3DS" folder or to remove the "_" from the name.
6. Eject the sd card and boot back into emunand. If everything went right, your emunand should the same as it started. Try to launch eshop or a similar service.
Hopefully this is helpful, and if you have any questions/comments let me know!
