This does not bypass the online ban, and apparently you still cant effectively use the new nnid as it gives another error saying it cannot be linked to this console (got this error on eshop.
You can use ntr with o3ds
You can use ntr with o3ds
I got my first ban when using sky3ds to play final fantasy explorers, i dont know if i used my other NNID but im sure it was the other NNID because i saw one of my miiverse screenshots of FF explorers. But will the poeple who played pokemon too early get perma ban?
I played it while online but I was disconnected from the servers because I hadn't updated my system.
I removed the game and the ticket now, updated my 3DS and I tried to play some Kid Icarus online and it worked fine. Maybe I'm safe?
I removed the game and the ticket now, updated my 3DS and I tried to play some Kid Icarus online and it worked fine. Maybe I'm safe?
If I understand it correctly, no, because you don't need to launch NTR in game, so you boot the old 3ds, change the ram, and you're good to go until next reboot.
Correct me if I'm wrong.
A guy that "make" a pre-loaded version and upload it told me that it should be fine and its even safer than a .cia because is actually the game from the Estore.
Last edited by alexj9626,
Because playing early is a minor fault and a temporary ban probably suits it. It acts as a warning so people won't do that again in the future.
On other hand, pirating the game (equal to stealing stuff) is a serious offense and deserves to be permanently banned.
Uninstall the ticket with the ID 0004000000175e00 (Moon) or 0004000000164800 (Sun) using FBI.
If i do this method, and make a new NNID. Does system transferring from hacked o3ds to n3dsxl not hacked will fix the problem? Id want to do a system transfer to downgrade firmware on the n3dsxl but since nnid sticks to from the banned ds, i was wondering if it will work
D
Deleted User
Guest
This is what I did. Totally not complete yet though. We still need something for doing this automatically. I'm a big believer that Luma will be how we do it automatically.
I DID THIS ON AN O3DS. I ASSUME IT WORKS EVEN BETTER WITH AN N3DS SINCE IT DOESN'T REBOOT FOR High Memory Games!
1)Install/Setup NTR Launcher.
2)Download Process Dumper (http://gbatemp.net/attachments/processdumper2-zip.57034/) & Process Explorer (http://gbatemp.net/attachments/plugin-ntr-ram-explorer-1-2-5-beta-zip.44553/). Extract both plugins into Root/plugins/Home.
3)Turn on the 3ds, start NTR launcher. It'll dump back to the menu. if you get an error, turn off the system, turn it back on, start ntr launcher, but don't let it autoselect a mode. Manually pick any of them.
4)At the home menu, press X+Y. A menu will appear. Click A on "Process Explorer".
5)Click on PID:21. IT WILL MOMENTARRILY FREEZE. if it lasts more than a minute, its crashed. Start over from Step 3.
6)Underneath the tet RAM EXPLORER on the topleft of the bottom screen, there is a Hex area. We gotta get that as close to 0x00117636 as we can. Tap the left bar to get as close as you can, then use Up and Down or the circle pad to get even closer.
7)Once it's in range, you'll see on the far right, X-Nintendo-Device-ID.... What you want to do is click on the red EDITOR button. Now, using the dpad, make your way over to the word Device. Mess up a letter or two. Shift the numbers and letter up and down with X and Y. Example: CHange "Device" to "Devisu".
8)once thats done, click the Green WRITE button.
9)Now, scroll down a little, until you see: "Nintendo-FPD-Version". At the end of it, you see there are only 2 dots. Click the Red EDITOR button and change that to say "Nintendo-Device-ID" in teh same way you destroyed Device earlier.
10)Once it's changed, click the Green Write button. Immedietely, click the red Editor button once again. JUST before it says "Nintendo-Device-ID" which we created, we see exactly "Nintendo-API-Version..0000..."
11)Change the zeroes to any random numbers. IT MUST USE NUMBERS. Once changed, click WRITE.
Done.
_____
A few notes that are needed though:
1) Random crashes when playing with the memory can happen. Its annoying.
2) It's also temporary. Try to remember what device id you were using for next time your doing it.
3) I'm sure we can make longer, quite abit longer, device id's for even more stealth-y-ness. Unfortunetely with this simple editor, i'm not sure how to add to the code rather than just changing it.
4) If you get an Error 022-2501, then your NNID is banned. Use Decrypt9 to inject a blank NNID from here: https://www.dropbox.com/s/5g96tls1krt31n5/nnidsave.bin?dl=1
If you'd like, backup your old NNID before injecting the blank one. But if your banned, maybe you don't need to anyway.
And the biggest thing people need to know: If the system is turned off, or is rebooted, the ram change is lost. This includes Big Memory Mode such as Sun & Moon. This is why we need a way to make it happen automatically.
This is just from what i've been doing so far. I accept no responsibility for damages to your system, yadadadada legaliez.
--------------------- MERGED ---------------------------
I DID THIS ON AN O3DS. I ASSUME IT WORKS EVEN BETTER WITH AN N3DS SINCE IT DOESN'T REBOOT FOR High Memory Games!
1)Install/Setup NTR Launcher.
2)Download Process Dumper (http://gbatemp.net/attachments/processdumper2-zip.57034/) & Process Explorer (http://gbatemp.net/attachments/plugin-ntr-ram-explorer-1-2-5-beta-zip.44553/). Extract both plugins into Root/plugins/Home.
3)Turn on the 3ds, start NTR launcher. It'll dump back to the menu. if you get an error, turn off the system, turn it back on, start ntr launcher, but don't let it autoselect a mode. Manually pick any of them.
4)At the home menu, press X+Y. A menu will appear. Click A on "Process Explorer".
5)Click on PID:21. IT WILL MOMENTARRILY FREEZE. if it lasts more than a minute, its crashed. Start over from Step 3.
6)Underneath the tet RAM EXPLORER on the topleft of the bottom screen, there is a Hex area. We gotta get that as close to 0x00117636 as we can. Tap the left bar to get as close as you can, then use Up and Down or the circle pad to get even closer.
7)Once it's in range, you'll see on the far right, X-Nintendo-Device-ID.... What you want to do is click on the red EDITOR button. Now, using the dpad, make your way over to the word Device. Mess up a letter or two. Shift the numbers and letter up and down with X and Y. Example: CHange "Device" to "Devisu".
8)once thats done, click the Green WRITE button.
9)Now, scroll down a little, until you see: "Nintendo-FPD-Version". At the end of it, you see there are only 2 dots. Click the Red EDITOR button and change that to say "Nintendo-Device-ID" in teh same way you destroyed Device earlier.
10)Once it's changed, click the Green Write button. Immedietely, click the red Editor button once again. JUST before it says "Nintendo-Device-ID" which we created, we see exactly "Nintendo-API-Version..0000..."
11)Change the zeroes to any random numbers. IT MUST USE NUMBERS. Once changed, click WRITE.
Done.
_____
A few notes that are needed though:
1) Random crashes when playing with the memory can happen. Its annoying.
2) It's also temporary. Try to remember what device id you were using for next time your doing it.
3) I'm sure we can make longer, quite abit longer, device id's for even more stealth-y-ness. Unfortunetely with this simple editor, i'm not sure how to add to the code rather than just changing it.
4) If you get an Error 022-2501, then your NNID is banned. Use Decrypt9 to inject a blank NNID from here: https://www.dropbox.com/s/5g96tls1krt31n5/nnidsave.bin?dl=1
If you'd like, backup your old NNID before injecting the blank one. But if your banned, maybe you don't need to anyway.
And the biggest thing people need to know: If the system is turned off, or is rebooted, the ram change is lost. This includes Big Memory Mode such as Sun & Moon. This is why we need a way to make it happen automatically.
This is just from what i've been doing so far. I accept no responsibility for damages to your system, yadadadada legaliez.
--------------------- MERGED ---------------------------
It does, just not High Memory Mode, so Sun and Moon/Smash/MH4 are out of reach for a while until we can see if it can be done with Luma Code.NTR doesn't work on o3ds right?
Last edited by ,
Can someone confirm to me that movable.sed won't fuck you over and bring the bad seed over from a banned hacked 3DS to a good one during sys transfer?
I don't find those in process 21 though, they are in process 22 for me. I wonder if that matters....
It was in process 22 for me as well, whatever the ACT service is on your 3ds
Nice work. I think it could work under Luma, but I'm nowhere near as smart as Aurora.
D
Deleted-19228
Guest
was able to enter eshop and all.
Went to settings to try to create new NNID,
prompted 022-2402
(it apppears that 2812 -> banned from accessing eshop/miiverse
2501 -> NNID account itself banned)
Similar threads
