I linked a new NNID to sysnand and now my (different) NNID in emunand won't work because the 3ds is registered to the sysnand NNID. I can't 'unlink' the NNID from the sysnand without using system transfer (will not work on fw 9.0) or deleting it which will remove all the content. Is formatting sysnand the only way to fix it and will it damage my emunand?
- Joined
- Nov 23, 2014
- Messages
- 15,144
- Trophies
- 0
- Location
- Canberra, Australia
- Website
- boot9strap.com
- XP
- 11,119
- Country
Formatting your SysNAND won't damage your emuNAND, and if you are worried about losing your stuff you can back up your sysNAND using the Gateway launcher or format emuNAND on a different SD card (so you can access all the sysNAND stuff by putting in that other SD card)
That happened to me once and I even called nintendo (without telling them I was on emunand of course). And their fix and only option was to format it the system (emunand in my case). Now I have the same NNID on both sysnand and emunand and it works.
I ended up deleting the NNID on sysnand but that still hasn't fixed it. The NNID on emunand still doesn't work. I need to somehow "relink" it but I can't figure out how to do it without losing all my content/saves on the emunand
How would I restore sysnand from a backup? how would I even have a sysnand backup?
--------------------- MERGED ---------------------------
Now I'm thinking I should log into my emunand's NNID on my sysnand BUT the nands aren't linked and if it doesn't work I'd be completely screwed because the only way to unlink it would be to delete my whole NNID.
Well since you have a hacked 3ds, I assumed you made a nand.bin backup of your sysnand. You would restore it with the gateway menu (holding dpad UP when selecting the "downgrade" option)
oh i get you. that might have worked, i've fixed that bit now. now i just need to get my emunand nnid linked again
Best plan I have right now is, image my SD card with win32diskimager, format from the settings menu of the emunand, relink the NNID then re-write the whole SD card with my image. Would this work? what else could go wrong?
Last edited by apoptygma,
- Joined
- Nov 23, 2014
- Messages
- 15,144
- Trophies
- 0
- Location
- Canberra, Australia
- Website
- boot9strap.com
- XP
- 11,119
- Country
Of course you can format the system! What does it tell you when you try to do it? If it asks you to connect to the net, don't wprry, it won't update or anything.
The way I understood it, your original NNID is on your emunand? then you unlinked your nands, and made a new NNID on your sysnand?
In that case, I would simply:
-restore sysnand backup to a state before I unlinked my nands, so now my nands are linked again, and the new NNID will be as if it never was linked to sysnand.
-unlink nands
-sign into the same NNID on sysnand (it may work based on what I've read and understood)
In that case, I would simply:
-restore sysnand backup to a state before I unlinked my nands, so now my nands are linked again, and the new NNID will be as if it never was linked to sysnand.
-unlink nands
-sign into the same NNID on sysnand (it may work based on what I've read and understood)
I unlinked my nands, signed into NNID "A" on emunand, then later on signed into NNID "B" on sysnand, this broke the NNID on emunand. I've now deleted "B" from sysnand so there's no linked NNID there, but the emunand with NNID "A" still doesn't work.
I've got a 64gb microSD in this unit and it's taking *forever* to image it, Is there any faster way to get NNID "A" which is linked with emunand working again? I'm scared to link NNID "A" on sysnand as the two nands aren't linked (the have different SDCARD:\Nintendo 3DS\#### IDs) and I'm not sure if the 'linking' on Nintendo's servers for the NNID is based off that value or the ID of the hardware itself which doesn't vary between emunand instances.
I don't have a NAND backup of sysnand in a state where the emunand I want to keep using was linked to sysnand btw.
I've got a 64gb microSD in this unit and it's taking *forever* to image it, Is there any faster way to get NNID "A" which is linked with emunand working again? I'm scared to link NNID "A" on sysnand as the two nands aren't linked (the have different SDCARD:\Nintendo 3DS\#### IDs) and I'm not sure if the 'linking' on Nintendo's servers for the NNID is based off that value or the ID of the hardware itself which doesn't vary between emunand instances.
I don't have a NAND backup of sysnand in a state where the emunand I want to keep using was linked to sysnand btw.
Yeah, I don't know that that'll work.
The only sure way of doing it would be to restore a copy of sysNAND from before you unlinked as suggested above.
If you could restore a sysNAND backup from before you unlinked, all you'd have to do would be to link your existing NNID to your sysNAND to be able to use it on both. In addition to that, when you connected to the eShop from sysNAND, all of the titles you installed on emuNAND would appear on the sysNAND homescreen.
Oh well, more fool you for not keeping a backup of your sysNAND before creating your emuNAND. At this stage though, your options are few; you can either create emuNAND from scratch and lose all your data, or you can install everything from .cia files from here on out.
Nope, what I did worked. I deleted the sysnand NNID, imaged the sd, formatted the emunand, linked the NNID to emunand, restored the SD and it's fixed. Fuck what a headache! Hope this is helpful to someone one day.
Similar threads
- No one is chatting at the moment.
