Hacking How do I remove NNID without system format?

[AtlanticBit]

My emuNAND was system transferred and then restored. I need to get rid of NNID without system format(am on CFW and have billions of my (un)tested hb on it).

 

[Shadowtrance]

Had this in my notepad from a while go, does the trick.


NNID is listed in: \data\<your unique id>\sysdata\00010038 > 00000000

It was pretty simple to do it and here it is how i did it:

1. I extracted my fat16 xorpad using launcher.dat from 3DS_Multi_Decryptor
2. Dumped emuNAND.bin using emuNANDTool
3. Extracted emunand.fat16.bin
4. xor'ed emunand.fat16.bin
5. Mounted emunand.fat16.bin.out with WinImage
6. Browsed to \data\<your unique id>\sysdata\00010038
7. Deleted 00000000
8. Renamed emunand.fat16.bin.out to test.bin
9. xor'ed test.bin
10. Injected test.bin.out into emunand.fat16.bin with HxD
11. Injected emunand.fat16.bin @ offset B930000 with HxD
12. Injected my new emunand.fat16.bin into my SD Card using emuNANDTool

Eh, voila, after booting into emuNAND NNID was gone

 

[Deleted-355425]

Had this in my notepad from a while go, does the trick.


NNID is listed in: \data\<your unique id>\sysdata\00010038 > 00000000

It was pretty simple to do it and here it is how i did it:

1. I extracted my fat16 xorpad using launcher.dat from 3DS_Multi_Decryptor
2. Dumped emuNAND.bin using emuNANDTool
3. Extracted emunand.fat16.bin
4. xor'ed emunand.fat16.bin
5. Mounted emunand.fat16.bin.out with WinImage
6. Browsed to \data\<your unique id>\sysdata\00010038
7. Deleted 00000000
8. Renamed emunand.fat16.bin.out to test.bin
9. xor'ed test.bin
10. Injected test.bin.out into emunand.fat16.bin with HxD
11. Injected emunand.fat16.bin @ offset B930000 with HxD
12. Injected my new emunand.fat16.bin into my SD Card using emuNANDTool

Eh, voila, after booting into emuNAND NNID was gone

Saving this one for myself, thanks.

 

[Intronaut]

My emuNAND was system transferred and then restored. I need to get rid of NNID without system format(am on CFW and have billions of my (un)tested hb on it).

I had the same problem, but I solved it downgrading the 3DS to 4.2 and then updating it again to 9.2.

 

[Sliter]

Actually I'm with a NNID problem , I have a formated emunand that I can't relink it , my acutuall emunand ans sysnand wich is "linked" but I can't sue any service that use NNID :v I don't know what to do lol

 

[RepeatingDigits]

Actually I'm with a NNID problem , I have a formated emunand that I can't relink it , my acutuall emunand ans sysnand wich is "linked" but I can't sue any service that use NNID :v I don't know what to do lol

Format Sysnand, I think it's your only option. Make a NAND backup first, though.
You could even try to deauthorize the console by formatting sysnand, relinking, and then restoring your old NAND. Wonder if that'll do the trick.

 

[Sliter]

Format Sysnand, I think it's your only option. Make a NAND backup first, though.
You could even try to deauthorize the console by formatting sysnand, relinking, and then restoring your old NAND. Wonder if that'll do the trick.

ok I will try! thanks
but why I can't link on the unlinked emunand?

 

[RepeatingDigits]

ok I will try! thanks
but why I can't link on the unlinked emunand?

If you're trying to link your SysNAND NNID on your unlinked EmuNAND it won't work, because upon login Nintendo servers check that the ID you're trying to link is already on your SysNAND.

 

[Sliter]

If you're trying to link your SysNAND NNID on your unlinked EmuNAND it won't work, because upon login Nintendo servers check that the ID you're trying to link is already on your SysNAND.

oh this makes sense now o-o

 

[Apache Thunder]

Nintendo servers won't let you link your NNID twice if it's still linked

Though there are some ways around that. In my case, I have both sysnand and emunand linked to my NNID, but both are not linked to each other. That's because I had a previous 3DS that got bricked and I called Nintendo to move the account over to my 3DS XL. So I had emunand linked to NNID that way. Then after I got some one to unbrick the original 3DS and provide the decrypted fat16 file. I was able to move over the movable.sed and data folders (you can't move over ticket.db, as that is encrypted to console unique keys and will brick if moved to another console manually). Note that you can't just move movable.sed to another console without editing it first.

In most instances if you have a 320 byte long file, it has 2 lines of code at the end you have to remove with a hex editor. Then set the first 4 header bytes after the "SEED" text to zero. Then that file can be moved to another console. I was able to use all the original save games and such that the bricked 3DS had. I just had to reinstall any that didn't have tickets. (which wasn't many since alot of what my emunand had already had titles my original 3DS had so the tickets were valid)

Thus I was able to move the data/movable.sed to my emunand and just moved my emunand's original movable.sed/data folder to sysnand since I backed that up before doing this process. They both used the same NNID and password originally, so they both connect to my NNID just fine since the account still has my XL connected to it.

Because calling Nintendo to move over the account doesn't copy the movable.sed or data folders, the friend code seed and encryption seed are not moved over either. So the emunand had a different encryption seed and folder then the original 3DS that got bricked. Hence how I got emunand's movable.sed/data encryption seeds moved to sysnand then having the original 3DS movable.sed/data seeds copied to emunand from the bricked 3DS. They both use the same NNID and I can use them both at the same time without them being linked to each other.

For users with just one console, you can link emunand to NNID, back that up to pc using emunand tool. Then format to unlink and then simply link it again. Then decrypt the backup you made earlier and copy the movable.sed (found in the private folder) and the contents of the data folder to a prepared already decrypted 9.2 sysnand image that has been decrypted. Of coarse I'd recommend testing that resulting 9.2 image as emunand first if you don't have a NAND mod since doing blind edits to sysnand image without testing it first carries a brick risk.

I suggest you search the forums on this subject as what I posted above is a generalized summery. You have to be careful with how you edit the movable.sed file and I probably wasn't specific enough with exactly how much data you have to chop off the end of the file. Search around for more details on that as I've forgotten exactly the amount.

Just note that if you are moving the movable.sed file from emunand to sysnand on the same console, you do NOT need to edit it! Editing it is only required if you are moving a movable.sed from one console to another!

 

[Sliter]

Format Sysnand, I think it's your only option. Make a NAND backup first, though.
You could even try to deauthorize the console by formatting sysnand, relinking, and then restoring your old NAND. Wonder if that'll do the trick.

well I trie dit but also don't worked like on the emunand :B says the information I entered isn't correct , but is the same I used to log in on web miiverse

 

[MelonGx]

System Format never unlinks your NNID on the console.
After the System Format, your data vanished, but you still cannot create any new NNID (or NNID-less logging in e-shop) unless you delete your old NNID.
So, see #2 for the best solution.

10. Injected test.bin.out into emunand.fat16.bin with HxD
11. Injected emunand.fat16.bin @ offset B930000 with HxD

What does this mean?
Does it mean injecting test.bin.out on emunand.fat16.bin's B930000 for the start?

 

[Sliter]

System Format never unlinks your NNID on the console.
After the System Format, your data vanished, but you still cannot create any new NNID (or NNID-less logging in e-shop) unless you delete your old NNID.
So, see #2 for the best solution.


What does this mean?
Does it mean injecting test.bin.out on emunand.fat16.bin's B930000 for the start?

I have no ieda how to do half of the steps D:

 

[jagerstaffel]

Say, we can delete NNID's, right? I know it's a little extreme, but it is an option to unlink an NNID from a console, correct?

 

[MelonGx]

I have no ieda how to do half of the steps D:

For 1, you need either 3DS_Multi_Decryptor or RX-TOOLS.
For 3, you need a dragNandDumpForFat16.BAT file.
For 4, you need Padxorer.exe.
You can find the tool names on other steps themselves.

 

[Hammyface]

Say, we can delete NNID's, right? I know it's a little extreme, but it is an option to unlink an NNID from a console, correct?

According to the people (rightfully) pissed off at Nintendo's forums, the only way to "unlink" an NNID from a 3DS is to literally delete the username. There is no option on the 3ds other than "delete account".

I am not sure what happens if you were also using that NNID on a Wii U.

 

[Shadowtrance]

Yep the only way to remove it from the 3ds is either system transfer to another 3ds or totally delete it using the delete option in NNID settings, it's tied to the system SERVER side on nintendo side, so if you use the delete option it's gone fullstop.

About time nintendo got with the times and made a proper account system rather than tying it to the bloody console like they do now.

 

[Sliter]

For 1, you need either 3DS_Multi_Decryptor or RX-TOOLS.
For 3, you need a dragNandDumpForFat16.BAT file.
For 4, you need Padxorer.exe.
You can find the tool names on other steps themselves.

ok I will give another try with more care when I get time ..
but I'm confused why I can't link this on the "clean" emunand õ3o say that some of my info are wrong , but I can log in on web miiverse with the same info ...

 

[TimX24968B]

Had this in my notepad from a while go, does the trick.


NNID is listed in: \data\<your unique id>\sysdata\00010038 > 00000000

It was pretty simple to do it and here it is how i did it:

1. I extracted my fat16 xorpad using launcher.dat from 3DS_Multi_Decryptor
2. Dumped emuNAND.bin using emuNANDTool
3. Extracted emunand.fat16.bin
4. xor'ed emunand.fat16.bin
5. Mounted emunand.fat16.bin.out with WinImage
6. Browsed to \data\<your unique id>\sysdata\00010038
7. Deleted 00000000
8. Renamed emunand.fat16.bin.out to test.bin
9. xor'ed test.bin
10. Injected test.bin.out into emunand.fat16.bin with HxD
11. Injected emunand.fat16.bin @ offset B930000 with HxD
12. Injected my new emunand.fat16.bin into my SD Card using emuNANDTool

Eh, voila, after booting into emuNAND NNID was gone

this got very confusing for me, and when I tried to drag in the emunand.fat16.bin.out into winimage, there were no files, and the file itself was 0 bytes. I got annoyed with them taking my DLC and just went back to emunand9 and redid the entire emunand setup process from there. thankfully, I didn't need to reinstall all my apps, and the saves were kept too! and i no longer have a linked NNID in emunand.