Hacking [How To] Remove the 022-2812 ban error with a CFW

[KytuzuEX]

I just use modified arm9.bin from this tread once and unlink NNID.
then i switch to use original arm9loaderhax.bin and it still able to access e-shop with no error.

What way did you used to unlink the NNID?

 

[Polarise]

What way did you used to unlink the NNID?

You inject a blank NNIDsave.bin file using decrypt 9.

 

[KytuzuEX]

Ok, I tested the modified arm9loaderhax.bin

What I would like to do is to "re-link" my NNID back to be "unbanned"
I actually don't want to create a new one.

I injected a blank nnidsave and along the modified arm9loaderhax. I tried to log in my NNID and it said: "This NNID is already linked in another 3DS"

So I injected back my NNID along modified arm9loaderhax and it said: "This NNID cannot be used on this console" without an error code number.

So I wondered, what if .... I format? Formatting would be unlinking the NNID in order to "link" it on the blank nnidsave along with the modified arm9loaderhax.bin. Of course, using an modified SecureInfo_A.
(Note: I have A9LH and what if I format? I will lose the sysemunand?)

It can be possible? Or the NNID is just for System Transfer to another console?

 

[Cuphat]

Ok, I tested the modified arm9loaderhax.bin

What I would like to do is to "re-link" my NNID back to be "unbanned"
I actually don't want to create a new one.

I injected a blank nnidsave and along the modified arm9loaderhax. I tried to log in my NNID and it said: "This NNID is already linked in another 3DS"

So I injected back my NNID along modified arm9loaderhax and it said: "This NNID cannot be used on this console" without an error code number.

So I wondered, what if .... I format? Formatting would be unlinking the NNID in order to "link" it on the blank nnidsave along with the modified arm9loaderhax.bin. Of course, using an modified SecureInfo_A.
(Note: I have A9LH and what if I format? I will lose the sysemunand?)

It can be possible? Or the NNID is just for System Transfer to another console?

You'd need to get Nintendo to release your NNID from your console so you can link it to the "new" console. Changing the device ID like this makes Nintendo see it as a different console (which is why people are saying that it's probably not a good thing for it to change everyone to the same ID).

The only way to move your NNID to a new console ID like that is a system transfer (might be possible if you have a spare console that doesn't have any important NNID associations on it, transfer to it with a blank NNID save and normal CFW and transfer back to the modified CFW) or to contact Nintendo and feed them the right bullshit to get them to release the NNID.

 

[KytuzuEX]

You'd need to get Nintendo to release your NNID from your console so you can link it to the "new" console. Changing the device ID like this makes Nintendo see it as a different console (which is why people are saying that it's probably not a good thing for it to change everyone to the same ID).

The only way to move your NNID to a new console ID like that is a system transfer (might be possible if you have a spare console that doesn't have any important NNID associations on it, transfer to it with a blank NNID save and normal CFW and transfer back to the modified CFW) or to contact Nintendo and feed them the right bullshit to get them to release the NNID.

I have a spare A9LH 2DS without any NNID. So, that can work!?

I heard that system transfering a NNID from a banned 3DS to a unbanned 3DS can leave you also banned. I doubt that.

I need more details about that transfer! :0

SecureInfo_A can be sufficient to replace the Device ID?

 

[Garro]

Ok, I tested the modified arm9loaderhax.bin

What I would like to do is to "re-link" my NNID back to be "unbanned"
I actually don't want to create a new one.

I injected a blank nnidsave and along the modified arm9loaderhax. I tried to log in my NNID and it said: "This NNID is already linked in another 3DS"

So I injected back my NNID along modified arm9loaderhax and it said: "This NNID cannot be used on this console" without an error code number.

So I wondered, what if .... I format? Formatting would be unlinking the NNID in order to "link" it on the blank nnidsave along with the modified arm9loaderhax.bin. Of course, using an modified SecureInfo_A.
(Note: I have A9LH and what if I format? I will lose the sysemunand?)

It can be possible? Or the NNID is just for System Transfer to another console?

I know you can "unlink" a NNID by pressing X+Y and then A while the error message that the NNID cant be used on this console is on the screen. But I don't know if it really unlink the NNID server-side.

 

[KytuzuEX]

I know you can "unlink" a NNID by pressing X+Y and then A while the error message that the NNID cant be used on this console is on the screen. But I don't know if it really unlink the NNID server-side.

I did it!

I don't know if it will say the same thing.

 

[Cuphat]

I have a spare A9LH 2DS without any NNID. So, that can work!?

I heard that system transfering a NNID from a banned 3DS to a unbanned 3DS can leave you also banned. I doubt that.

I need more details about that transfer! :0

SecureInfo_A can be sufficient to replace the Device ID?

SecureInfo_A has the serial number, not the device ID. The device ID is changed by using the modified CFW in the OP of this thread (or something similar). I'd wait to see if someone makes something better before doing the transfer back, no idea if anyone is working on it though.

I have no idea what the actual repercussions of transferring from a banned to an unbanned console is. I'm not sure if anyone does.

But since transferring should also transfer the console's NNIDs (even when they aren't currently signed-in) it should work in theory to move the NNID to the new device ID.

I guess, worst case, you'll learn something interesting one way or another.

 

[KytuzuEX]

SecureInfo_A has the serial number, not the device ID. The device ID is changed by using the modified CFW in the OP of this thread (or something similar). I'd wait to see if someone makes something better before doing the transfer back, no idea if anyone is working on it though.

I have no idea what the actual repercussions of transferring from a banned to an unbanned console is. I'm not sure if anyone does.

But since transferring should also transfer the console's NNIDs (even when they aren't currently signed-in) it should work in theory to move the NNID to the new device ID.

I guess, worst case, you'll learn something interesting one way or another.

Thanks for the explanation! I'm going to mess a little bit with arm9loaderhax hex editing to see where it is. lol

 

[wsquan171]

SecureInfo_A has the serial number, not the device ID. The device ID is changed by using the modified CFW in the OP of this thread (or something similar). I'd wait to see if someone makes something better before doing the transfer back, no idea if anyone is working on it though.

I have no idea what the actual repercussions of transferring from a banned to an unbanned console is. I'm not sure if anyone does.

But since transferring should also transfer the console's NNIDs (even when they aren't currently signed-in) it should work in theory to move the NNID to the new device ID.

I guess, worst case, you'll learn something interesting one way or another.

Is it possible to transfer from a banned system to another system? Shouldn't all server related services rendered unavailable if you get a console ban? It seems true to me that if we can transfer to another console, edit device id on the first one, then transfer back, we indeed can have NNID usable on the previously banned console.

 

[Cuphat]

Is it possible to transfer from a banned system to another system? Shouldn't all server related services rendered unavailable if you get a console ban? It seems true to me that if we can transfer to another console, edit device id on the first one, then transfer back, we indeed can have NNID usable on the previously banned console.

If you still have your NNID linked, you won't be able to transfer (it wants you to log in to that NNID before transferring, which errors out of course). If you inject a blank nnidsave using Decrypt9, it skips the NNID login part and should let you transfer, as far as I can tell.

 

[KytuzuEX]

Is it possible to transfer from a banned system to another system? Shouldn't all server related services rendered unavailable if you get a console ban? It seems true to me that if we can transfer to another console, edit device id on the first one, then transfer back, we indeed can have NNID usable on the previously banned console.

Logically, HAS TO BE possible... like that. (I haven't tested yet)
What we have to do is to edit somehow the deviceID.

 

[wsquan171]

If you still have your NNID linked, you won't be able to transfer (it wants you to log in to that NNID before transferring, which errors out of course). If you inject a blank nnidsave using Decrypt9, it skips the NNID login part and should let you transfer, as far as I can tell.

Now I get it. Good idea and worth a try.

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

Logically, HAS TO BE possible... like that.
What we have to do is to edit somehow the arm9loaderhax.bin if I'm correct, that's where is the deviceID.

We have to wait for an RNG lol, I prefer to edit it manually by myself. But I don't know.

True. Don't want to share the same device id with hundreds of people.

 

[KytuzuEX]

Hmm, many things come up in my mind lol.

Another speculation, what if I inject my NNID from the banned 3DS to the unbanned 3DS? (In my case, having no NNID in my 2nd 3DS)
Backstory:
Previously, "unlinking" your NNID by pressing X+Y and A in the settings with the modified arm9loaderhax.bin in the Console-banned 3DS

That in mind, technically, you will be having a blank nnidsave.bin in your banned 3DS. In other words, System Transfer from second 3DS injected NNID from banned 3DS to the banned 3DS with a "different" DeviceID.

 

[Cuphat]

Hmm, many things come up in my mind lol.

Another speculation, what if I inject my NNID from the banned 3DS to the unbanned 3DS? (In my case, having no NNID in my 2nd 3DS)
Backstory:
Previously, "unlinking" your NNID by pressing X+Y and A in the settings with the modified arm9loaderhax.bin in the Console-banned 3DS

That in mind, technically, you will be having a blank nnidsave.bin in your banned 3DS. In other words, System Transfer from second 3DS injected NNID from banned 3DS to the banned 3DS with a "different" DeviceID.

No, that wouldn't work. Your unbanned 3DS would have the same issue as your modified device ID on the banned 3DS, it won't let you log in and thus you couldn't transfer it. The transfer is needed to move the NNID on the server side to the right console. Without moving it on their end, it won't work.

I haven't tried it, but if you were able to inject your nnidsave to your unbanned console, trying to System Transfer would ask you to login and then error out telling you that you can't use that NNID on that console. I don't see any way around the first transfer.

 

[wsquan171]

Hmm, many things come up in my mind lol.

Another speculation, what if I inject my NNID from the banned 3DS to the unbanned 3DS? (In my case, having no NNID in my 2nd 3DS)
Backstory:
Previously, "unlinking" your NNID by pressing X+Y and A in the settings with the modified arm9loaderhax.bin in the Console-banned 3DS

That in mind, technically, you will be having a blank nnidsave.bin in your banned 3DS. In other words, System Transfer from second 3DS injected NNID from banned 3DS to the banned 3DS with a "different" DeviceID.

Well, you can do that and it will show as if you logged nnid in your 2nd console. But I guess you won't be able to do anything on eshop since on the server side your nnid is still linked to the banned console. The only way to swich nnid linkage is to do system transfer, or call nintendo.

The fact is that, you can link multiple nnids to one console. When doing system transfer all of them will be transferred to the target console despite that only one is active.

 

[KytuzuEX]

No, that wouldn't work. Your unbanned 3DS would have the same issue as your modified device ID on the banned 3DS, it won't let you log in and thus you couldn't transfer it. The transfer is needed to move the NNID on the server side to the right console. Without moving it on their end, it won't work.

I haven't tried it, but if you were able to inject your nnidsave to your unbanned console, trying to System Transfer would ask you to login and then error out telling you that you can't use that NNID on that console. I don't see any way around the first transfer.

Well, you can do that and it will show as if you logged nnid in your 2nd console. But I guess you won't be able to do anything on eshop since on the server side your nnid is still linked to the banned console. The only way to swich nnid linkage is to do system transfer, or call nintendo.

The fact is that, you can link multiple nnids to one console. When doing system transfer all of them will be transferred to the target console despite that only one is active.

I see!
Since I can't transfer because I need to log on at least once on the E-Shop and I can't, the last option is to call Ninty.
They... wouldn't dare to neglect my request? What I have to say is that I need to unlink my NNID from that console right?

 

[Cuphat]

You can system transfer, or should be able to anyhow. You inject an empty nnidsave.bin to your banned 3DS. It no longer will require you to login to an NNID when transferring. Logging into an NNID is what you were banned from, so long as you avoid that, it should be fine.

And, despite not being logged in to the NNID, as @wsquan171 said, doing a system transfer will transfer all NNID associations regardless of it they were logged in during the transfer. Therefore, it should then be possible to login to that NNID on the second console. In theory.

After that, you'd want to use a modified CFW to spoof your device ID. In theory, you could then transfer back (while running said CFW) to move your NNIDs to the new device ID.

Assumptions made in this is that you are indeed able to transfer without an NNID attached, even on a banned console, that doing the transfer will transfer your NNID even though it isn't logged in, that transferring from a banned console won't cause the destination console to be adversely effected, and that spoofing the device ID like this works to bypass the ban without any weird side effects. I think all that is solid assumptions, but they are assumptions none-the-less.

 

[Krunch]

Well, you can do that and it will show as if you logged nnid in your 2nd console. But I guess you won't be able to do anything on eshop since on the server side your nnid is still linked to the banned console. The only way to swich nnid linkage is to do system transfer, or call nintendo.

The fact is that, you can link multiple nnids to one console. When doing system transfer all of them will be transferred to the target console despite that only one is active.

I think you will be unable to do a system transfer even with you NNID erased from your device. What is guess is that, on server side, a device with XXXXX ID have linked ZZZ NNID, and there are just two ways to unlink it server side:

First one, being done manually by nintendo,
Second one, the device with XXXX ID sends a petition to link the ZZZ NNID to a second device with a different ID, which can't be done because when XXXX device tries to connect to the server to send the petition, its connection is refused by a blacklist. As far I know, that petition is mandatory.

The only way to bypass the 022 for now is faking another device ID, and although you could send a petition to the server, that wouldn't come from the XXXXX device, so the ZZZ NNID would still remain linked to it on server side.

Edit:

Assumptions made in this is that you are indeed able to transfer without an NNID attached, even on a banned console, that doing the transfer will transfer your NNID even though it isn't logged in, that transferring from a banned console won't cause the destination console to be adversely effected, and that spoofing the device ID like this works to bypass the ban without any weird side effects. I think all that is solid assumptions, but they are assumptions none-the-less.

Well, all depends on what you said, if a banned console without a linked NNID is able to do a system transfer, which I think it wouldn't.

 

[Cuphat]

I think you will be unable to do a system transfer even with you NNID erased from your device. What is guess is that, on server side, a device with XXXXX ID have linked ZZZ NNID, and there are just two ways to unlink it server side:

First one, being done manually by nintendo,

Second one, the device with XXXX ID sends a petition to link the ZZZ NNID to a second device with a different ID, which can't be done because when XXXX device tries to connect to the server to send the petition, its connection is refused by a blacklist. As far I know, that petition is mandatory.


The only way to bypass the 022 for now is faking another device ID, and although you could send a petition to the server, that wouldn't come from the XXXXX device, so the ZZZ NNID would still remain linked to it on server side.

But we already know that System Transferring will move all NNIDs from the source console to the destination console, which means it doesn't have to ask for a specific NNID to be moved. You should be able to initiate a system transfer without issue (I got to the point where I needed to connect a second 3DS just fine after blanking out my nnidsave.bin) which seems to imply to me that any system transfer done will cause Nintendo to move all NNIDs associated to the new console automatically.

Again, I can't test it all the way right now, but I do know for sure that it moved my main NNID when I transferred to someone else's console for DSiWare, even though I specifically created a new NNID to transfer. It made no difference, both NNIDs were moved and I had to contact Nintendo to get them to release it.

Failing all of this, contacting Nintendo is still on the table, though who knows if they will see that the NNID is associated with a banned console and refuse.