Advertisement
nihalnoor

3DS Console Banwave - 26/5/17

May 26th, 2017
144
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.46 KB | None | 0 0
  1. Important Information
  2. HOW TO (likely) AVOID THE BAN: (See attached image)
  3. 1. TURN OFF WIFI
  4. 2. Go to Friend List, click Settings in the corner of the screen, go to settings, and DISABLE Share Currently Playing Game.
  5. 3. Go to System Settings -> Internet Settings -> SpotPass -> Sending of System Information; turn it OFF.
  6. Optionally, avoid running homebrew from, or installing it to, the Home Menu, as a CIA.
  7.  
  8. This does NOT GUARANTEE THAT YOU WILL NOT BE BANNED. IT IS A SAFETY NET.
  9. NOBODY IS SAFE.
  10.  
  11.  
  12. What we know so far about the bans:
  13. People are getting banned. and it is by the use of data, sent from your console to Nintendo.
  14. We do not presently know how Nintendo determines which consoles to ban.
  15. They can look at any data sent from your 3DS, to or through their servers.
  16.  
  17. What we think the cause may be:
  18. Friend services sends Nintendo your currently playing title, if you don't disable this in the Friend List settings. If this includes a custom, homebrew or invalid title (not officially released by Nintendo) it triggers a ban.
  19. SpotPass also periodically sends Nintendo "system information", including all installed titles, including homebrew, and the other shop, unless you opt out of system information sending, in the Spotpass settings in Internet Settings.
  20. eShop, the home menu theme shop, and embedded/DLC eShop applet (collectively, eCommerce Services), may be reporting title information to Nintendo servers.
  21.  
  22. What we think aren't related at all:
  23. Fire Emblem Echoes; Pokemon; in-game cheating; save editing; pokemon genning; any specific game in general.
  24.  
  25. What we're certain shouldn't be triggering bans:
  26. sighax, boot9strap, arm9loaderhax; upgrading to boot9strap; running homebrew from an entrypoint in an official app, applet or game (e.g., browserhax, menuhax, ninjhax); .3dsx homebrew applications themselves, running from a homebrew entrypoint.
  27.  
  28. What could be risky to do, and may trigger bans:
  29. - Running any game ROM backups, including your own game backups
  30. - Installing and running any kind of CIA's
  31. - making a ROM backup from a game cartridge and installing it to NAND
  32. - installing homebrew to the home menu
  33. - running homebrew from the home menu
  34. - using the other shop or any ticket/titlekey managers
  35. - going on the eShop with homebrew installed to your home menu
  36. - leaving SpotPass on, or leaving Friend List "show friends what you're playing" on
  37. - using unofficial or pirated themes in CIA format (themes installed "raw" through Themely or similar should be fine)
  38.  
  39. What data is being transferred?
  40. - Friends list data, presence information, Favorite Title information, Now Playing information, game/battle join information. This includes your currently running title.
  41. - Matchmaking data for all games. This includes your current playing game, ranking and player information, DLC owned, and so forth.
  42. - SpotPass (BOSS) service subscription data. This includes all titles you have installed, which have SpotPass enabled.
  43. - StreetPass service beacon and user data. This includes all titles you have installed, which have StreetPass enabled.
  44. - eShop, DLC/eShop Applet, and Theme Shop, when launched, may send a list of installed titles and themes to Nintendo.
  45. - When the system checks for an update, it retrieves a list of title versions. This request should not have user-sensitive data.
  46. F.A.Q's!
  47. Please don't ask these questions again.
  48.  
  49. Q: Am I at risk for getting banned?
  50. A: Yes!
  51.  
  52. Q: What regions are affected by the banwave?
  53. A: All.
  54. Q: What firmwares are affected by the banwave?
  55. A: All. Only the latest one will allow you to connect online, though, so that's moot.
  56. Q: What CFW/Luma versions/bootstraps are affected by the banwave?
  57. A: All.
  58. Q: What 3DS models are affected by the banwave?
  59. A: All.
  60. Q: What homebrew methods are affected by the banwave?
  61. A: All.
  62.  
  63. Q: I got banned after upgrading to b9s, is it causing the bans?
  64. A: A9LH and B9S alone are not the reasons you are being banned. Both those and other CFW are susceptible to banning.
  65.  
  66. Q: Is the ban wave over? Will it end? WHEN WILL IT END?!?!?!?!?!?
  67. A: "Never."
  68.  
  69. Q: Will there be a solution for consoles that are already banned?
  70. A: No. It is a permanent ban.
  71.  
  72. Q: How do I know if I'm banned?
  73. A: Go online, open Friends List. If you get an Error 002-0102, you are banned.
  74. Q: Will doing this ban me?
  75. A: It shouldn't, if you only open Friends List and nothing else, and be sure to have read the information on How To Avoid The Ban.
  76.  
  77. Q: Can I still play online with my SpotPass or Friend List info sharing disabled?
  78. A: Yes.
  79.  
  80. Q: Is my NNID banned or affected on other consoles?
  81. A: No. Your NNID will continue to work, and Miiverse and eShop will work as expected.
  82.  
  83. Q: What can I still do online while I'm banned?
  84. A: Use the Internet Browser, buy things on the eShop, access Miiverse (not post?), use homebrew with internet connectivity, and use local multiplayer.
  85. Q: Ban "waves"? How many ban waves have there been, or will there be? Will there be more?
  86. A: The concept of a ban wave is misleading.
  87. Nintendo is likely logging information sent from your 3DS system to their servers, which is invalid (for instance, currently playing a homebrew title in Friends List.)
  88. When they see your information is invalid, it will flag your account for review.
  89. At an irregular interval, these flags will become bans permanently.
  90.  
  91. Q: My 3DS was in sleep mode. Can I still be banned?
  92. A: YES. It seems to be banning with SpotPass data, which is sent while your 3DS is asleep. Read the other pins for information on how to avoid bans.
  93.  
  94. Q: Is this a server/NNID ban or a console ban?
  95. A: Console ban. It affects your console-specific data. This data is not spoofable, and must come from a legitimate 3DS.
  96. FAQ's about BAN CIRCUMVENTION
  97.  
  98. Q: How do I circumvent the ban?
  99. A: We won't go in depth here. It requires another 3DS that's not banned, to extract "console-specific data" from and copy to your 3DS.
  100.  
  101. Q: What is console-specific data/information?
  102. A: Generally, anything specific to your console, including OTP and NAND CID.
  103. However, in this case, we're referring to nandrw:/sys/LocalFriendCodeSeed_B, aka LFCS, and possibly other files.
  104.  
  105. Q: Will a system transfer remove my ban status?
  106. A: No. You are banned. You wouldn't be able to system transfer, either.
  107.  
  108. Q: Will NNID injection or NNID bypassing/ban circumvention work?
  109. A: No, for 99% of cases. This is a console ban, triggered on connection with your valid, banned console-specific information.
  110.  
  111. Q: If the system that a copied LocalFriendCodeSeed_B came from is banned, does the dumped one get banned too?
  112. A: Yes. Do not steal LocalFriendCodeSeed_B's, do not use public LFCS's, and do not use one on more than one console at once, as they will be banned.
  113.  
  114. Q: Why can't an LFCS_B just be edited or generated?
  115. A: It's console-specific information signed at the provisioning step, at the factory, by processes which register and confirm your console's identity. It's RSA signed. The provisioning private key is sacrosanct, so as to keep malicious people
  116.  
  117. from making "genuine" clones of 3DS systems.
  118.  
  119. Q: Will the bootrom keys/boot9strap help us to generate/modify and re-sign the LFCS?
  120. A: Absolutely not. The LFCS is signed with an RSA signature at the factory, by Nintendo; and is verified serverside, by Nintendo. At no point is the key outside of the factory, ever.
  121. Q: Will this signature ever be cracked or brute-forced? Is it vulnerable to sighax?
  122. A: Not before the 3DS online services have ceased. You cannot count on a vulnerability in their signature checking system, because it is server-side.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement