Tutorial
Updated
Unban 102-2452 (Console Ban)!
If you do this, please note that I am not responsible for any rebanning.
If you do this, do not hack again on Splatoon or any game's public battles; let the public play without hacks ruling their place. Use private battles.
This will be patched by Nintendo, it's only a matter of time.
Do not share your otp.bin or device certs. That's stupid.
Were you silly enough to get banned on Splatoon or another game? Sure, change your serial and then you're unbann- oh wait you're now console banned. RIP.If you do this, do not hack again on Splatoon or any game's public battles; let the public play without hacks ruling their place. Use private battles.
This will be patched by Nintendo, it's only a matter of time.
Do not share your otp.bin or device certs. That's stupid.
There is a way around this: You're going to need to be able to redirect OTP to SD (Mocha does this
) for this to work correctly.I suggest changing your serial too as more things that are different means Big N will not see you as quickly. But they'll probably still see you eventually.
Requirements:
- A hex editor. (I suggest Hex Fiend for Mac, HxD for Windows)
- Your OTP.bin
- A Wii U
- A brain.
- An internet connection to view this page.
- A new NNID to use
Steps:
- Go to this page, and open your otp.bin in the hex editor.
- Find the offsets for your Wii "NG ID", "NG private key", and "NSS device certificate", and copy them.
- Paste the id, key, and certificate over the Wii U ones - for the NG private key, add NULLs onto the end until it's the same size as the Wii U one.
Credits to "SplatSamu" for being my Wii U guinea pig since the fool got himself banned.
Last edited by ,
