Hacking Fixing error 022-2634

[thedude28]

So following this quote right here:

Nor do you have to completely delete your NNID.

You just have to make an emunand backup and a backup of your nand's folder in sdmc:/Nintendo 3DS/, then format emunand in system settings, re-link your NNID in your newly formatted emunand, then restore emunand backup and restore your folder in Nintendo 3DS so you don't lose your games and your saves.

Voilà, should work now.

What would actually happen if I formatted Emunand in System Settings? Is it possible to unlink/re-link it from here?

 

[izy]

no because your emunand crashes if you remove SD.

 

[thedude28]

no because your emunand crashes if you remove SD.

It actually turns out, if you format Emunand through system settings, it just formats the mini Partition it creates or whatever and also deletes the emunand folder located in Nintendo 3DS. It does not affect anything else at all.

In my case, running a Jap New3DS that was firmware spoofed, I had to downgrade a few titles. This is because the first time I formatted system memory in Emunand, I forgot that I had spoofed my firmware and thus had bricked it.

 

[izy]

It actually turns out, if you format Emunand through system settings, it just formats the mini Partition it creates or whatever and also deletes the emunand folder located in Nintendo 3DS. It does not affect anything else at all.

In my case, running a Jap New3DS that was firmware spoofed, I had to downgrade a few titles. This is because the first time I formatted system memory in Emunand, I forgot that I had spoofed my firmware and thus had bricked it.

Well the folder is located on the 3DS SD card, if you remove you SD before you format system menu like you are meant to for unlinking nands you wouldnt get that.

But like i said if you try and remove sd before formatting emunand in settings it would crash

 

[Deleted-236924]

I'm actually not sure what happens if you format emunand in system settings.

I've done it a fair few times on my XL and it just formats emunand. Everything sysnand remained untouched.

But then yesterday I did it on my regular 3DS, formatted sysnand so I could unlink them, then I went to format emunand in system settings and for some reason they were back to being linked. I had to re-format sysnand again to unlink them.

The only difference I see is that on my XL, sysnand was 9.2 while emunand was 10.3, every time I did this. On the regular 3DS they were both on 9.2, could that have confused the 3DS somehow?

 

[Searinox]

But then yesterday I did it on my regular 3DS, formatted sysnand so I could unlink them, then I went to format emunand in system settings and for some reason they were back to being linked. I had to re-format sysnand again to unlink them.

The only difference I see is that on my XL, sysnand was 9.2 while emunand was 10.3, every time I did this. On the regular 3DS they were both on 9.2, could that have confused the 3DS somehow?

Sysnand and emunand unique IDs are generated deterministically. They will become linked again if they have each been formatted the same number of times. Format emunand once, they become unlinked. Format sysnand once, they get to the same UID again. Format emunand 5 times, they're unlinked, format sysnand 5 times, they're back linked again.

 

[anonymoose]

, so is this method right?