Hacking Do there exist any conditions where the DSiWare exploit doesn't take 7 days?

Quantumcat · Sep 29, 2016

Reaga said:
So it sounds like my best option is to make a dummy account

Sadly this won't work, all NNIDs associated with a console get moved when system transferring, not just the active one at the time. You can still restore your wife's backup, she'll have all her games and saves only she won't be able to use the eShop or anything that logs onto the NNID like Badge Arcade (if she does, all games she bought that are now on your console will not be useable anymore).

Reaga · Sep 29, 2016

Quantumcat said:
Sadly this won't work, all NNIDs associated with a console get moved when system transferring, not just the active one at the time. You can still restore your wife's backup, she'll have all her games and saves only she won't be able to use the eShop or anything that logs onto the NNID like Badge Arcade (if she does, all games she bought that are now on your console will not be useable anymore).

Wow, I had meant to cancel that message for exactly that reason. Didn't realize I'd posted it.

Anyway, what would be your suggestion here?

DocKlokMan · Sep 29, 2016

Quantumcat said:
That will not work, that NNID is now linked to the target console. Only way to get it back onto the wife's console is ringing up Nintendo or waiting 7 days to do a system transfer.

It will be unlinked when he formats the newly hacked 3DS. No worries, been through this before, know the drill.

Quantumcat · Sep 29, 2016

AnalogMan said:
It will be unlinked when he formats the newly hacked 3DS. No worries, been through this before, know the drill.

I thought it was confirmed that every NNID belonging to a console is moved over to the target after a system transfer?

If you can log into an NNID on one console you cannot log into it on another. To be able to format and then log into it on another console would require that the non-logged-in NNIDs NOT transfer (because if they do, then you can log into them on the target, which would mean you cannot log into them on the source).

Reaga · Sep 29, 2016

Ok, you guys can probably understand why I'm getting confused. Thankfully I haven't started anything yet (in fact, can't seem to find my powersaves so I can put OoThax on her 3DS), so in the meantime:

Analog, have you tested this theory? Because while I would like to believe that formatting the N3DS will not remove A9LH (I can see that) and that it would unlink such that my wife could safely relink her account to her system without waiting 7 days (I'm less likely to be sure on that), I cannot in good conscious mess with her 3DS until I can guarantee that (screw-ups on my part notwithstanding) she won't lose anything.

DocKlokMan · Sep 29, 2016

Lesson about NNIDs:

When you sign into a NNID on a console, the console checks Nintendo's servers to see if it's already associated with a console by it's serial number. If it's not, it submits the serial number to Nintendo and updates their records.

If it is already associated, you get the error that you cannot sign into another console. When you system transfer, it does two things. The target 3DS goes online and removes the serial on file for the NNID that's currently signed into it and then the serial for the original 3DS is updated on record to match that of the target 3DS.

You can also de-register your NNID yourself by using the built in system format. This requires internet access and goes online to de-register your serial from your NNID. This is also the only way to officially sign-out of a NNID.

In this exact scenario, here's what would happen:

o3DS starts system transfer to n3DS. n3DS goes online and removes the serial on file for your NNID. Then it updates the serial number on record for your wife's NNID and migrates the account over. Your wife's o3DS is left formatted and without a NNID associated with it. The n3DS has all your wife's files and her NNID. Once you install A9LH using Fieldrunners, you can format your 3DS safely which goes online and removes the serial from your wife's NNID. Now neither NNID is assigned to any console.

Now, if you were to restore your wife's backup right now, you'd get an error because it has a NNID signed in that has no serial on record. So you would first set your wife's o3DS up as a new device, sign into her NNID to re-register her serial number and then you can restore her backup.

Finally, you can sign into your NNID as well.

I have taken parts of these steps when I needed to system format to fix an issue and messed up the signing in bit before restoring my backup after a system transfer. I don't have two 3DS's I'm willing to do this with right this moment, but worst case scenario as QuantumCat has said is a phone call to Nintendo to free your wife's NNID so it can be signed in on her o3DS again.

Andim · Sep 29, 2016

Call Nintendo's support line. Complain about the error message you get when you try to use your NNID after transferring. Tell them that somehow, someone else transferred your account away, you don't have the 3DS it was transferred to. They will get it back for you within 2 days.

vb_encryption_vb · Sep 29, 2016

Nintendo won't transfer till 7 days haso surpassed. Many have tried and failed. Quite simply, you have to wait. I've seen some reports, that Nintendo will still make you wait even if you call them now.

Majickhat55 · Sep 29, 2016

Make a NAND back up of your source 3DS, then format the system, create a dummy NNID or use eShop without one then do the DSiWare thing, restore your sysNAND on your source 3DS and sign into your original NNID. That's exactly what I did and I didn't have to call Nintendo or do the system transfer twice. My target 3DS also still has it's original NNID, (but also has the dummy one tied to the console server-side).

If you don't have any funds/purchased games under your NNID then it doesn't really matter. Just make a new one.

Andim · Sep 29, 2016

vb_encryption_vb said:
Nintendo won't transfer till 7 days haso surpassed. Many have tried and failed. Quite simply, you have to wait. I've seen some reports, that Nintendo will still make you wait even if you call them now.

Sounds like you're just not convincing enough. I called them and got it done in 1 day. I have the email to prove it.

vb_encryption_vb · Sep 29, 2016

Andim said:
Sounds like you're just not convincing enough. I called them and got it done in 1 day. I have the email to prove it.

Depends on who answers possibly? Personally, I don't bother with the dishware method, I can install a hardmod and have arm9loaderhax running in an hours time...

Reaga · Sep 29, 2016

Majickhat55 said:
Make a NAND back up of your source 3DS, then format the system, create a dummy NNID or use eShop without one then do the DSiWare thing, restore your sysNAND on your source 3DS and sign into your original NNID. That's exactly what I did and I didn't have to call Nintendo or do the system transfer twice. My target 3DS also still has it's original NNID, (but also has the dummy one tied to the console server-side).

If you don't have any funds/purchased games under your NNID then it doesn't really matter. Just make a new one.

So you were able to perform the full DSiWare exploit and return both accounts within the same day?

Deleted-19228 · Sep 29, 2016

People are going through too much hassle. Just go buy a 2DS in store. System transfer. Return system...Or keep it to mod other systems.

Quantumcat · Sep 29, 2016

AnalogMan said:
removes the serial on file for your NNID

This part is wrong I'm pretty sure. The target retains all the same NNID associations that it started with. Otherwise you'd have NNIDs floating around with no console associated.

--------------------- MERGED ---------------------------

AnalogMan said:
you can format your 3DS safely which goes online and removes the serial from your wife's NNID

Not true - the NNID is still linked to the console on Nintendo's servers even after formatting. The N3DS is the only console that can sign into it.

--------------------- MERGED ---------------------------

AnalogMan said:
Now neither NNID is assigned to any console.

Not true - both NNIDs are associated with the N3DS now.

Halvorsen · Sep 29, 2016

AnalogMan said:
Lesson about NNIDs:

When you sign into a NNID on a console, the console checks Nintendo's servers to see if it's already associated with a console by it's serial number. If it's not, it submits the serial number to Nintendo and updates their records.

If it is already associated, you get the error that you cannot sign into another console. When you system transfer, it does two things. The target 3DS goes online and removes the serial on file for the NNID that's currently signed into it and then the serial for the original 3DS is updated on record to match that of the target 3DS.

You can also de-register your NNID yourself by using the built in system format. This requires internet access and goes online to de-register your serial from your NNID. This is also the only way to officially sign-out of a NNID.

In this exact scenario, here's what would happen:

o3DS starts system transfer to n3DS. n3DS goes online and removes the serial on file for your NNID. Then it updates the serial number on record for your wife's NNID and migrates the account over. Your wife's o3DS is left formatted and without a NNID associated with it. The n3DS has all your wife's files and her NNID. Once you install A9LH using Fieldrunners, you can format your 3DS safely which goes online and removes the serial from your wife's NNID. Now neither NNID is assigned to any console.

Signing out of an NNID isn't the same as unlinking the ID from the system. The ID will always be linked to one system until it is linked to the next.

Quantumcat · Sep 29, 2016

AnalogMan said:
set your wife's o3DS up as a new device, sign into her NNID

won't work, the system transfer linked the NNID to the N3DS. It's now the only console that can sign into it.

If it was possible to format to delink NNIDs with consoles then you could easily share games just by formatting, and having a friend sign into your NNID and redownload all your games.

DocKlokMan · Sep 29, 2016

If you say so. This is based on my own experience, my own calls to Nintendo and through many 3DS upgrades and downgrades. But if there's documentation and not speculation on how NNID registration works, then obviously I will defer anyone to that.

Quantumcat · Sep 29, 2016

AnalogMan said:
If you say so. This is based on my own experience, my own calls to Nintendo and through many 3DS upgrades and downgrades. But if there's documentation and not speculation on how NNID registration works, then obviously I will defer anyone to that.

Well, the guide used to advise making a dummy NNID until someone confirmed that every NNID belonging to the source console also moved. So whoever that was did confirm that.
Is also known that the only way to move an NNID is by system transfer or asking Nintendo to do it. Formatting isn't sufficient. I'll see if I can find an article on it.

--------------------- MERGED ---------------------------

Each Nintendo Network ID can be associated to one Wii U console and one Nintendo 3DS family system.

Once a Nintendo Network ID has been associated to a Nintendo 3DS family system, it can only be moved to a different Nintendo 3DS family system through the Data Transfer process. How to

From http://en-americas-support.nintendo...~/how-to-link-an-existing-nintendo-network-id

So with the first point, the NNID is either linked to the source or the target but not botg. The active one will definitely get linked to the target, and "someone" worked out that the non-active ones will get linked to the target also. If they are linked to the target, they can't be linked to the source also.

For the second point, the only way to change the link on an NNID is by system transfer. So if they are linked to the target, that means the only way to link them to the source is by system transfer. (Or calling Nintendo as we know)

Hacking Do there exist any conditions where the DSiWare exploit doesn't take 7 days?

Dead and alive

Well-Known Member

Plugin Dev

Dead and alive

Well-Known Member

Plugin Dev

Well-Known Member

That hardmod guy....

The Red Woman

Well-Known Member

That hardmod guy....

Well-Known Member

Deleted-19228

Guest

Dead and alive

Well-Known Member

Dead and alive

Plugin Dev

Dead and alive

Similar threads

Popular threads in this forum