I saw a video of a guy moving certification files (2 files) and getting access again. Maybe if I grab those from another 3ds that will make it for the ban? Even if I "sacrifice" the unbanned 3ds ahahah
Last edited by GoldenGallade,
Hacking Ban 022-2812, solution after 2 years?
- Thread starter GoldenGallade
- Start date
- Views 5,528
- Replies 30
While this is true, you can use that new console to spoof the device ID of the banned one. I never posted the code that achieves this because it isn't mine, but I may do so now since the 3DS is essentially EOL.
He's probably referring to the above video where I use the device ID and certificate from another console to bypass the ban. This works by injecting them into the ARM9 RAM before the console fully boots, so you need a custom loader.
Last edited by Joom,
Yes, this is the video I watched. So are you the author? Could you explain what should I do in order to achieve this? And by custom loader you mean stuff like godmode9?
No, I'm not the one that created the code if that's what you're asking. I was just the beta tester. For this to work, you need a secondary, same model console that isn't banned. You also have to make a brand new NNID. By custom loader, I mean code included in the boot.firm that injects the necessary files into the ITCM (ARM9 RAM). So, you have to have devkitPro and a build environment set up as well since anything that serves as a main boot FIRM can be used. It doesn't specifically have to be Luma so long as it mounts and reads the SD.
The devkitPro part looks complicated do you think you can help me explaining step by step what I have to do? If it is not too much to ask, would be really appreciated.
Do you understand what devkitPro is? It just provides the toolchain necessary to compile stuff for the 3DS. It's only going to be useful if you have the code to add to whatever you plan to use, which isn't available publicly. I'm also assuming that you're on Windows, but you're gonna want a Linux setup (virtual or not) to make compilation as easy as possible. Not to mention you need the tool dd to extract the certificate and device ID from a RAM dump, which comes with Linux.
That's definitely something I'm not able to do without a tutorial, since I have no clues about devkitPro or Linux environment.
There's really no easy way to do this. If I knew more, I would just make a chainloader that acts as the boot FIRM that injects these files, then loads the custom firmware FIRM file.
Similar threads
