- Joined
- May 17, 2014
- Messages
- 535
- Trophies
- 0
- Age
- 31
- Location
- Warrnambool, Victoria, Australia
- XP
- 499
- Country
Error messages have actually changed over time through system updates, but only once though. But you are right about what it does and all that.So even though this is common knowledge now, I thought the the legit descriptions of these bans were interesting and are as follows:
002-0121 -
Cannot access the online service.
For help, visit support.nintendo.com. Authentication error on authentication server.
Local friend code SEED has invalid certificate. Causes include system malfunction, use of an illegal tool, connecting to a live-environment authentication server from development hardware, connecting to a development-environment authentication server from production hardware, etc.
This error can be reproduced on the error simulation server.
022-2812 -
You cannot access Nintendo Network
services using this system.
Please make a note of the error code
and visit support.nintendo.com.
The use of all network services has been suspended at the device level.
I've also decided to make a list of error codes, relating to bans. Please note that if anything in this post that says 'certificate', we mean the LocalFriendCodeSeed_A or LocalFriendCodeSeed_B file.
002-0102
Error message used on NATIVE_FIRM versions 1.0.0 to 10.4.0:
Error message used on NATIVE_FIRM versions 10.5.0 and later:Cannot access the online service.
For help, visit support.nintendo.com.
Authentication error on authentication server.
What does this error mean?This device's access to online services
has been restricted by Nintendo.
For help, visit support.nintendo.com.
It means that the authentication server has verified the certificate (under the name LocalFriendCodeSeed_A or LocalFriendCodeSeed_B), used for accessing the Friend Service of the server. But the server has denied the certificate from allowing access to the service. In other words, the certificate has been blocked (aka banned).
Current solution:
As of this post, it is currently possible to bypass this by using a loophole in the Friend Service server by changing the certificate to that of a different console to trick the server into thinking that it's the same console, but not matching the certificate that's been banned. However, this loophole won't last forever, Nintendo is bound to patch their server at some point in the future to make it impossible to get past it without sacrificing all of your eShop purchases and Friend List.
002-0121
Error message used on NATIVE_FIRM versions 1.0.0 to 10.4.0:
Error message used on NATIVE_FIRM versions 10.5.0 and later:Cannot access the online service.
For help, visit support.nintendo.com.
Authentication error on authentication server.
What does this error mean?This device's access to online services
has been restricted by Nintendo.
For help, visit support.nintendo.com.
The authentication server cannot find a certificate on its server that matches the certificate on the console, usually because the certificate has been automatically removed from the server, along with the eShop account and Friend Service account. This is exactly why custom certificates cannot be made, even if we knew the RSA key for it. And that's why some people decide to sacrifice their own console's LocalFriendCodeSeed_A or LocalFriendCodeSeed_B file by sharing it. This error code only appears while using the Friend List app.
Current solution:
Same solution as error code 002-0102. However, this error code will only happen if you've got error code 022-2812 while attempting to connect to Nintendo Network services. You will also have to use the solution for error code 022-2812 as well.
022-2812
Error message used on all NATIVE_FIRM versions:
What does this error mean?You cannot access Nintendo Network
services using this system.
Please make a note of the error code
and visit support.nintendo.com.
The console has been denied access from the Nintendo Network servers. In the past, it was possible to bypass this by simply changing the serial number in SecureInfo_A to match that of a different console. But now this is no longer possible since the authentication on the Nintendo Network servers also check for deviceID that matches the serial number stored in their database.
Current solution:
The only way to get around this, is by spoofing the deviceID to match that of a different console, along with the serial number matching that of the same console as the deviceID. It's not possible to use the same eShop account ID, as that account as been automatically deleted from the server after this ban is placed on the console. So you have to start over from scratch. This solution would be pretty useless to do anyways, unless you don't feel like spending around $100 on a new console.
Last edited by Platinum Lucario,