Toggle sidebar

Homebrew [Release] Miiverse Custom Image Tool

  • Thread starter Thread starter PF2M
  • Start date Start date
  • Views Views 237,360
  • Replies Replies 1,563
  • Likes Likes 36
Status
Not open for further replies.
mozziedoo said:
I only posted one Leafy No Chin image to the MK7 community.
MY NNID IS NOW BLOCKED.
So I got banned. Do you know what this error code means?
022-2501: You cannot use this Nintendo Network ID on this system.
Click to expand...
The admins now have your DeviceID and it could be banned at any time. You are at a huge risk of a hyperban right now if your NNID just got suspended.

Just be on alert. If you're going to use Miiverse, use it through a proxy now.
Same thing for NNIDs.
 
mozziedoo said:
I only posted one Leafy No Chin image to the MK7 community.
MY NNID IS NOW BLOCKED.

--------------------- MERGED ---------------------------



So I got banned. Do you know what this error code means?

022-2501: You cannot use this Nintendo Network ID on this system.
Click to expand...

Lmao, I've only posted about 4 custom images and I have only been 2 week'd
 
PF2M said:
Alright, so I should admit that I didn't really find a way to fully bypass a hyperban. Well, I did... but it's very temporary, and you'd have to do it every time you reboot. This will also only work for Nintendo Network ID-related services, no online stuff until some other day. It's otherwise pretty simple though, so here's how I did it, I guess.
  1. Download the latest NTR CFW, and get this plugin.
  2. Start up your 3DS, and launch NTR CFW.
  3. Hit X+Y on the home menu, go down to 'Process explorer', and get to PID 21.
  4. Use the touch screen scrollbar (or anything else) to get to 0x00117636.
    Here, you should see "X-Nintendo-Device-ID". Use the editor to change that to literally anything else, like "X-Nintendo-Dedede-ID". (X/Y is up/down when changing bytes)
  5. Scroll down a bit more to find "X-Nintendo-FPD-Version", it was at 0x0011776E for me. Change that to "X-Nintendo-Device-ID; this is how you're going to actually make a difference. (Nintendo's servers don't actually care about your FPD version or Dedede ID; they track bans by the Device ID, and this is how we're changing it, since the actual device ID is nowhere to be found in the RAM.)
  6. There's four ASCII zeroes right before X-Nintendo-FPD-Version; this is where it comes from. Change this to whatever you want, it really doesn't matter as long as everyone isn't using "0000" as a deviceID.
  7. Do whatever until you reboot or close System Settings.
This isn't really the best method, and is only a proof-of-concept really. But hey, I had a Sunday deadline, and I had to show something. Maybe this could be made easier using an NTR plugin that does this directly, or maybe even something that could spoof the deviceID itself? Who knows?

I'm sorry if this isn't what you wanted. I'll go back into hibernation now.
Click to expand...

Does this still work?
 
PF2M said:
Alright, so I should admit that I didn't really find a way to fully bypass a hyperban. Well, I did... but it's very temporary, and you'd have to do it every time you reboot. This will also only work for Nintendo Network ID-related services, no online stuff until some other day. It's otherwise pretty simple though, so here's how I did it, I guess.
  1. Download the latest NTR CFW, and get this plugin.
  2. Start up your 3DS, and launch NTR CFW.
  3. Hit X+Y on the home menu, go down to 'Process explorer', and get to PID 21.
  4. Use the touch screen scrollbar (or anything else) to get to 0x00117636.
    Here, you should see "X-Nintendo-Device-ID". Use the editor to change that to literally anything else, like "X-Nintendo-Dedede-ID". (X/Y is up/down when changing bytes)
  5. Scroll down a bit more to find "X-Nintendo-FPD-Version", it was at 0x0011776E for me. Change that to "X-Nintendo-Device-ID; this is how you're going to actually make a difference. (Nintendo's servers don't actually care about your FPD version or Dedede ID; they track bans by the Device ID, and this is how we're changing it, since the actual device ID is nowhere to be found in the RAM.)
  6. There's four ASCII zeroes right before X-Nintendo-FPD-Version; this is where it comes from. Change this to whatever you want, it really doesn't matter as long as everyone isn't using "0000" as a deviceID.
  7. Do whatever until you reboot or close System Settings.
This isn't really the best method, and is only a proof-of-concept really. But hey, I had a Sunday deadline, and I had to show something. Maybe this could be made easier using an NTR plugin that does this directly, or maybe even something that could spoof the deviceID itself? Who knows?

I'm sorry if this isn't what you wanted. I'll go back into hibernation now.
Click to expand...
Why would you make this public? Nintendo is going to patch it, you know.
 
PF2M said:
Alright, so I should admit that I didn't really find a way to fully bypass a hyperban. Well, I did... but it's very temporary, and you'd have to do it every time you reboot. This will also only work for Nintendo Network ID-related services, no online stuff until some other day. It's otherwise pretty simple though, so here's how I did it, I guess.
  1. Download the latest NTR CFW, and get this plugin.
  2. Start up your 3DS, and launch NTR CFW.
  3. Hit X+Y on the home menu, go down to 'Process explorer', and get to PID 21.
  4. Use the touch screen scrollbar (or anything else) to get to 0x00117636.
    Here, you should see "X-Nintendo-Device-ID". Use the editor to change that to literally anything else, like "X-Nintendo-Dedede-ID". (X/Y is up/down when changing bytes)
  5. Scroll down a bit more to find "X-Nintendo-FPD-Version", it was at 0x0011776E for me. Change that to "X-Nintendo-Device-ID; this is how you're going to actually make a difference. (Nintendo's servers don't actually care about your FPD version or Dedede ID; they track bans by the Device ID, and this is how we're changing it, since the actual device ID is nowhere to be found in the RAM.)
  6. There's four ASCII zeroes right before X-Nintendo-FPD-Version; this is where it comes from. Change this to whatever you want, it really doesn't matter as long as everyone isn't using "0000" as a deviceID.
  7. Do whatever until you reboot or close System Settings.
This isn't really the best method, and is only a proof-of-concept really. But hey, I had a Sunday deadline, and I had to show something. Maybe this could be made easier using an NTR plugin that does this directly, or maybe even something that could spoof the deviceID itself? Who knows?

I'm sorry if this isn't what you wanted. I'll go back into hibernation now.
Click to expand...
I cannot get to that id.
 
ariankordi said:
Hyperbans are only tracked via the DeviceID in this situation. He edited RAM in the ACT process (ACT is for network accounts) that could edit the DeviceID to something else, I'm not really exact on that.

--------------------- MERGED ---------------------------

I might as well mention that I've circumvented a hyperban on my 2DS as well. Yes, it is hyperbanned.
I redirected all account.nintendo.net requests to my PC so I could modify the requests and send them back to the server.
This is a more 'controllable' method as you can spoof everything in the request and response.
YVCww5I.png
xYylsJq.jpg

And proof, since I wasn't hyperbanned too long ago:
vicp0Gr.jpg

PF2M is louder than me in a lot of ways, so I didn't really release this info when I first achieved this a few days ago.
Click to expand...
How would you redirect and edit them?

Sent from my ONEPLUS A3000 using Tapatalk
 
PF2M said:
Alright, so I should admit that I didn't really find a way to fully bypass a hyperban. Well, I did... but it's very temporary, and you'd have to do it every time you reboot. This will also only work for Nintendo Network ID-related services, no online stuff until some other day. It's otherwise pretty simple though, so here's how I did it, I guess.
  1. Download the latest NTR CFW, and get this plugin.
  2. Start up your 3DS, and launch NTR CFW.
  3. Hit X+Y on the home menu, go down to 'Process explorer', and get to PID 21.
  4. Use the touch screen scrollbar (or anything else) to get to 0x00117636.
    Here, you should see "X-Nintendo-Device-ID". Use the editor to change that to literally anything else, like "X-Nintendo-Dedede-ID". (X/Y is up/down when changing bytes)
  5. Scroll down a bit more to find "X-Nintendo-FPD-Version", it was at 0x0011776E for me. Change that to "X-Nintendo-Device-ID; this is how you're going to actually make a difference. (Nintendo's servers don't actually care about your FPD version or Dedede ID; they track bans by the Device ID, and this is how we're changing it, since the actual device ID is nowhere to be found in the RAM.)
  6. There's four ASCII zeroes right before X-Nintendo-FPD-Version; this is where it comes from. Change this to whatever you want, it really doesn't matter as long as everyone isn't using "0000" as a deviceID.
  7. Do whatever until you reboot or close System Settings.
This isn't really the best method, and is only a proof-of-concept really. But hey, I had a Sunday deadline, and I had to show something. Maybe this could be made easier using an NTR plugin that does this directly, or maybe even something that could spoof the deviceID itself? Who knows?

I'm sorry if this isn't what you wanted. I'll go back into hibernation now.
Click to expand...
Trying this for a while now, but I don't get Process Explorer, I get process list, nor can I get to 0x00117636.

I literally start NTR, it reboots, I press XY and it appears..... then I continue?
 
I had to go get a different program to go with this it to get Process Explorer as an option.
 
zirogx2 said:
How would you redirect and edit them?
Click to expand...
Search for "https://account.nintendo.net" in RAM, replace it with your machine's IP and then use a proxy like Fiddler to take requests from your machine to another site, which is account.nintendo.net in this case. ClCertA is needed. That's the most basic way to explain it.
 
ariankordi said:
Search for "https://account.nintendo.net" in RAM, replace it with your machine's IP and then use a proxy like Fiddler to take requests from your machine to another site, which is account.nintendo.net in this case. ClCertA is needed. That's the most basic way to explain it.
Click to expand...
Can't find it anywhere in ram

Sent from my ONEPLUS A3000 using Tapatalk
 
Status
Not open for further replies.

Site & Scene News

Go to forum More news

Popular threads in this forum

Why did the price of 3ds shoot up ?

Hacking Homebrew Project  BlazerTube - a YouTube 3DS revival using the REAL app!

Problems getting Homebrew to appear outside of the Homebrew Launcher (homebrew won't appear on the HOME menu)

Homebrew app Emulator  [Release] 3DS-CLI - Run a real RISC-V Linux environment on the Nintendo 3DS

Website for finding alternative games for 3DS

Gaming  any good rpgs on 3ds?

Hardware  2 Broken 3DSes, need help

Hacking  Modding Reassurance