Gaming Has anyone gotten banned from playing Pokemon Moon online?

  • Thread starter Thread starter AquaX101
  • Start date Start date
  • Views Views 1,298,777
  • Replies Replies 9,528
  • Likes Likes 2

Yeah sorry for getting your hopes up, i got all excited too when I had 2 different Movable, but when I checked the LFC, the values were the same. as the new movable.

So generally speaking, generating a new movable is a bust.

Likely this fix can only be done by

1. Injecting unbanned LFC
2. Unbanned Movable values to LFC.
3. System Transfer to generate new Movable as the values must have to come from Nintendo and signed
 
What did you do with the previous boot.3dsx?
I opened the newly created payload on my SD card in a hex editor, searched for "boot.3dsx" in text, replaced it with "luma.3dsx" and save, moved the Luma3DS .3dsx to the root of my SD, and rename it to "luma.3dsx"
 
Yeah sorry for getting your hopes up, i got all excited too when I had 2 different Movable, but when I checked the LFC, the values were the same. as the new movable.

So generally speaking, generating a new movable is a bust.

Likely this fix can only be done by

1. Injecting unbanned LFC
2. Unbanned Movable values to LFC.
3. System Transfer to generate new Movable as the values must have to come from Nintendo and signed
It's fine. Just need a way to clear the movables and LFC permanently to inject clean ones from my unbanned 3ds.
 
I opened the newly created payload on my SD card in a hex editor, searched for "boot.3dsx" in text, replaced it with "luma.3dsx" and save, moved the Luma3DS .3dsx to the root of my SD, and rename it to "luma.3dsx"
If luma boot , you don't have replace the boot.3dsx
 
Yeah sorry for getting your hopes up, i got all excited too when I had 2 different Movable, but when I checked the LFC, the values were the same. as the new movable.

So generally speaking, generating a new movable is a bust.

Likely this fix can only be done by

1. Injecting unbanned LFC
2. Unbanned Movable values to LFC.
3. System Transfer to generate new Movable as the values must have to come from Nintendo and signed

Or changing region using dev firmwares
 
Ok, so I assume you can't do a system transfer to a banned 3ds?
My son's got banned... it had no Nintendo Id linked... so no eshop ban... don't think that helps though.
I never installed or played sumo so my 3ds is in the clear and still has my NNID.
 
don't know if this was mentioned before or not,there is 350 page

yah,if you are from Europe,DO NOT USE THE DIGITAL GAME

pokemon-sun-moon-email-ban.png


http://nintendoeverything.com/ninte...pirated-pokemon-sunmoon-copies-are-permanent/
 
Last edited by aos10,
Ok, so I assume you can't do a system transfer to a banned 3ds?
My son's got banned... it had no Nintendo Id linked... so no eshop ban... don't think that helps though.
I never installed or played sumo so my 3ds is in the clear and still has my NNID.
Why system transfert to a banned is impossible ?
 
Oh dear god it worked, it worked!

Acraeus, I could pay you a beer right now.

I just unbanned myself from 002 using nothing but my own 3DS! This is incredible. And I suck at writing tutorials of any kind, so please don't count on me when it comes to that!
But basically

1. Inject an old NAND backup from when you were still installing a9lh (I did one before)
2. Use Decrypt9 to extract movable.sed from it

3. Use Decrypt 9 to extract movable.sed and LocalFriendCodeSeed_B from your current NAND that is banned
4. Use HxD (hex editor) to compare your old movable.sed with your LocalFriendCodeSeed_B, see how offsets 00000000/08 through 00000110/07 is the SAME!
5. Open up your NEW movable.sed with HxD and copy offsets 00000000/08 through 00000110/07
6. Open up LocalFriendCodeSeed_B with HxD and CTRL+A and then paste what you just copied
7. Save, inject to sysnand

This is how I did it, don't blame me if something goes wrong because I'm even worse at giving instructions than following them.

EDIT: Ignore strikethrough text, that is no needed and was just a part of me finding out HOW to do it, you don't need to do that.
do i paste what i copied and repla
Basic jist of what to copy over is as follows (sorry for bad handwriting lolol, ignore first 8 bytes (SEED...) and last 40 bytes.
Last 3 bytes of the seed should be 00

View attachment 69297
when you copy it over do you replace it too?
 
My movable.sed and localfriendcodeseed_B are the same so I am doing a NANDmin backup and restoring my 9.2 one before I did a system format while installing arm9
 
Ok, so I assume you can't do a system transfer to a banned 3ds?
My son's got banned... it had no Nintendo Id linked... so no eshop ban... don't think that helps though.
I never installed or played sumo so my 3ds is in the clear and still has my NNID.
uhhhh if you're willing to do a bit of guided science you can definitely unban your sons 3ds, back up the movable.sed and localfriendcodeseed on both consoles and attempt to transfer from your clean one to his banned one, if it goes will both of you should have unique seeds,if it doesn't you can still use your own seed to have both unbanned
 
its the luma patch, I think is pretty buggy atm and probably wont be in final luma
Especially since it doesn't have random number generation (RNG) built into it to change the device-id. If you use that your device-id will be the same as everyone else's who uses it.
 
So like, i have my brother's 3DS which isn't banned. I dumped its LocalFriendSeed_B and injected it on mine (after properly keeping a backup of mine of course), however i still get 002-0102 upon checking my friends list. Do i have to do anything else, like replacing my movable.sed for example? I dumped mine again and compared it on hxd to make sure it was my brother's and it is, but he's definitely not banned right now.
 

Site & Scene News

Popular threads in this forum