★★★DO NOT FOLLOW THIS METHOD IF YOU HAVE BEEN BANNED IN THE MOST RECENT BANWAVE (MAY 2017) - YOU WILL LIKELY GET BANNED AGAIN ON YOUR NEW LFCS_B WASTING THE CONSOLE THAT IT CAME FROM AND DOING NOTHING FOR YOUR BANNED ONE★★★ --- Scroll down a bit to skip straight to the tutorial. --- It's for general discussion regarding this current error code bypass method. I want this to be organized. Not sure if this type of thread exists, I didn't see one, just general chaos with working methods thrown into the mix in various other threads. If a thread like this already exists, sorry for making this one, and please delete this thread. --------------------- Basic info: So, as some of you may know, Nintendo has graced a lot of us with the ban hammer. The vast majority of people have received error code 002-0102, which essentially is a ban from all game related online services. Historically, this ban has been 15 days, but it appears that this time, it's permanent. With this being said, the only way it looks like we're getting out of this, is by injecting a valid, unbanned LocalFriendCodeSeed_B. --------------------- NOTE: THE REPERCUSSIONS FROM NINTENDO FOR DOING THIS ARE UNKNOWN. IT MAY BE NOTHING, YOU MAY GET BANNED AGAIN, AND IN A WORSE WAY, WE DON'T KNOW YET. THE RISK IS ALL ON YOU. Solution (so far): The solution to this error code/ban, is to simply inject a valid "unbanned" LocalFriendCodeSeed_* (* can be A or B, B seems most common, and appears to be the primary option in Decrypt9, so is most likely the general default. A seems to appear when B is deleted, and A also appears to be all 0's when it is generated after B is deleted). As of right now, the only way to obtain a valid "unbanned" LocalFriendCodeSeed_* is from another 3DS or 2DS system that hasn't been banned from online play with your tool of choice (Decrypt9 is the easiest and safest way). As far as I know, the type of system you obtain the file from is irrelevant, and the worst that will happen when using a fake/garbage/dummy file is you get a different error when going online (I got 002-0121). It is unknown if there truly is a way to generate this file, or spoof it in some way, as attempting to simply inject a 272 byte file with random data will not work for the reason stated above, which leads some to believe that the file is either encrypted, or protected in some other way. Additionally, trying to edit the last 8 bytes of a LocalFriendCodeSeed appears to result in the same error. 002-0121 is an invalid certificate error. --------------------- NOTE: THE REPERCUSSIONS FROM NINTENDO FOR DOING THIS ARE UNKNOWN. IT MAY BE NOTHING, YOU MAY GET BANNED AGAIN, AND IN A WORSE WAY, WE DON'T KNOW YET. THE RISK IS ALL ON YOU. Tutorial: Always backup your NAND before modifying it! ONLY do this with A9LH! There have been numerous bricks reported from people not using A9LH who have tried this method! Part 1 (mandatory for most, do this step): This step removes the NNID from your system, and changes the serial in SecureInfo_A. Follow this guide (they're both the same guide, just a different format, if you like videos, watch the video, if you'd rather read, choose the gbatemp post) Download for blank nnidsave.bin: https://www.dropbox.com/s/5g96tls1krt31n5/nnidsave.bin?dl=1 Video Guide: Text Guide: https://gbatemp.net/threads/tutorial-how-to-bypass-nnid-bans-miiverse-online-eshop-etc.417999/ Part 2 or 4 (optional) This step resets your friend code and removes everyone on your friends list. You can do this either before, or after you do Part 3, I did it after. https://gbatemp.net/threads/error-002-0102-help.449019/page-12 - Apache Thunder's post a bit down regarding folder locations. I deleted the contents of the folders (the contents should just be one file with a bunch of 0's as the name, be careful) with Godmode9. I'm sure there's a safer way, but I don't know what that would be. Be careful. Part 3 (main part, manditory). Video Tutorial (they're both the same guide, just a different format, if you like videos, watch the video, if you'd rather read, read directly below the video): Text tutorial: If you have a valid unbanned LocalFriendCodeSeed_B from a different source, you can omit the steps to dump a seed from an unbanned system. All you need to follow are the steps to inject the seed into the banned system. Have two 3DS systems with access to Decrypt9 (the banned system, and a clean system, the banned system should already have access to this, if not, figure out a way to install it). On the 3DS that has not been banned, load into Decrypt9. Once in Decrypt9, move down and press A on "SysNAND Options". When in SysNAND options, move down and press A on "System File Dump". Head on down to "Dump LocalFriendCodeSeed_B" and choose a name. The default name is best. Once dumped, access your SD card though your computer, via. SD card adapter, FTP, whatever you choose. Head to the files9 folder (that's where it was for me, might be on root for you, or somewhere else, but the point is there's only one copy on the SD card, which is the one you just dumped), and move LocalFriendCodeSeed_B to somewhere safe. Once you have LocalFriendCodeSeed_B saved somewhere safe, you can put the SD card back into your 3DS or close FTP. Do the same process for the banned 3DS just to be safe. It might not seem necessary to back up a banned LocalFriendCodeSeed, but we don't know yet. Better safe than sorry. Make sure not to confuse the unbanned one with the banned one, to save yourself some time and trouble. Injection: Prior to injecting a different LocalFriendCodeSeed, make sure you've backed up the original LocalFriendCodeSeed on the system you'll be injecting to. As mentioned above, you can do so through the "System File Dump" menu in Decrypt9. After backing up the banned LocalFriendCodeSeed, move the unbanned seed from your unbanned 3DS to the root of your banned system's SD card (I also put in the files9 folder to be safe, but I don't think you need to). Once you've moved the unbanned LocalFriendCodeSeed to the banned system's SD card, put the SD card back into your banned system (or close out of FTP), and reboot into Decypt9. Now, instead of clicking "System File Dump", you're going to click "System File Inject". Select LocalFriendCodeSeed_B, and verify you want to inject by following the on screen instructions. Select the file name, should be the default one, and inject it. Granted you dumped the file and copied it over correctly, the file should inject successfully. Press B to go back, and start to reboot. You should be able to go online. --------------------- Goal: The goal (in my opinion) is to figure out exactly how LocalFriendCodeSeed is made/works, so we can potentially generate or modify existing ones and have them turn out valid. --------------------- Random "info" (probably just speculation): Doing a system transfer from a system with 002-0102 to a system that does not have 002-0102 is safe. LocalFriendCodeSeed_B is not carried over during the system transfer process, and therefor will not ban the target (unbanned) system. For more info regarding this file (LocalFriendCodeSeed) & how it works: https://www.3dbrew.org/wiki/Nandrw/sys/LocalFriendCodeSeed_B https://www.3dbrew.org/wiki/PSPXI:GetLocalFriendCodeSeed https://www.3dbrew.org/wiki/CfgS:GetLocalFriendCodeSeed http://3dbrew.org/wiki/Process_Services_PXI https://www.3dbrew.org/wiki/Process_Services https://www.3dbrew.org/wiki/Memory_layout WARNINGS & DISCLAIMER: I am not responsible in any way for any damage done to your system. This guide is assuming the person following is both using A9LH (Arm9LoaderHax) and Luma3DS custom firmware. It is NOT safe to modify SecureInfo_A on systems not using A9LH with Emunand, as having a different SecureInfo_A between EmuNAND/RedNAND and SysNAND WILL RESULT IN A BRICK. The only way to recover from said brick is to flash a NAND backup via. hard mod!