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).
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
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).
Format Sysnand, I think it's your only option. Make a NAND backup first, though.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
ok I will try! thanksFormat 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.
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.ok I will try! thanks
but why I can't link on the unlinked emunand?
oh this makes sense now o-oIf 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.
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 miiverseFormat 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.
What does this mean?10. Injected test.bin.out into emunand.fat16.bin with HxD
11. Injected emunand.fat16.bin @ offset B930000 with HxD
I have no ieda how to do half of the steps D: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:
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?
ok I will give another try with more care when I get time ..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.
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.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