Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,112,048
  • Replies Replies 47,954
  • Likes Likes 66
In what order did you did it though, did you set it up though, setup exosphere / dns mitm then update the firmware?
Just earlier? DNS MITM has been set up before first emuMMC boot some time back, so it's already active. With it active, the firmware was updated.

90DNS Checker confirms this, all domains are blocked.
 
Just earlier? DNS MITM has been set up before first emuMMC boot some time back, so it's already active. With it active, the firmware was updated.

90DNS Checker confirms this, all domains are blocked.

So do you have a exosphere.ini config in the root of your SD? Also check your serial number it should like XAW0000000000000 if done correctly.
 
In what order did you did it though, did you set it up though, setup exosphere / dns mitm then update the firmware?
  1. DNS MITM before emuMMC first boot
  2. Prodinfo blanking done some time after first boot
  3. Used Daybreak to update to 20.4.0
Is that what you're asking?
Post automatically merged:

So do you have a exosphere.ini config in the root of your SD? Also check your serial number it should like XAW0000000000000 if done correctly.
Yes, it's in SD root, and yes. That's what I meant by all zeroes.

Just so we're on the same page, I'm referring to this nag when trying to open the web browser via homebrew:

1770406970187.png
 
  1. DNS MITM before emuMMC first boot
  2. Prodinfo blanking done some time after first boot
  3. Used Daybreak to update to 20.4.0
Is that what you're asking?
Post automatically merged:


Yes, it's in SD root, and yes. That's what I meant by all zeroes.

Just so we're on the same page, I'm referring to this nag when trying to open the web browser via homebrew:

View attachment 555249

If done correctly it might just be that the game update it is trying to nag you about is higher than your current firmware, I mean you can update to 21.2.0 fine,

In Impezza guide it does explain how to setup exosphere and DNS MiTM but it seem like you done it correctly.

1770407402254.png

 
If done correctly it might just be that the game update it is trying to nag you about is higher than your current firmware, I mean you can update to 21.2.0 fine,
Are you implying that (in this case) the last time Switch was online on sysMMC prior to creating emuMMC, it saved the latest update version ID, and the nag isn't going to disappear until that update is installed? That would mean it isn't enough to update to any firmware version...

To be clear, I avoid 21.x due to less memory availability to system modules.

Now to enable DNSMiTM, you need to restore your SDMC:/atmosphere/config/system_settings.ini file from backup, or copy the one from SDMC:/atmosphere/config_template/system_settings.ini and be sure the parameter enable_dns_mitm , enable_dns_mitm_debug_log and add_defaults_to_dns_hosts have the value u8!0x1 Also be sure you remove the «;» at start of the line.
After doing this in addition to relying on the defaults (DNS MITM is enabled without having to explicitly enable it), there was no difference, it works as usual:
DNS Mitm:
Adding defaults to redirection list.
Selecting hosts file...
Skipping /hosts/emummc_32574152.txt because it does not exist...
Selected /hosts/emummc.txt
Redirections:
`*ctest.cdn.nintendo.net` -> 95.216.149.205
`*conntest.nintendowifi.net` -> 95.216.149.205
`*nintendoswitch.cn` -> 127.0.0.1
`*nintendoswitch.com.cn` -> 127.0.0.1
`*nintendoswitch.com` -> 127.0.0.1
`*nintendo.pl` -> 127.0.0.1
`*nintendo.ch` -> 127.0.0.1
`*nintendo.se` -> 127.0.0.1
`*nintendo.co.za` -> 127.0.0.1
`*nintendo.ru` -> 127.0.0.1
`*nintendo.pt` -> 127.0.0.1
`*nintendo.no` -> 127.0.0.1
`*nintendo.nl` -> 127.0.0.1
`*nintendo.it` -> 127.0.0.1
`*nintendo.hu` -> 127.0.0.1
`*nintendo.gr` -> 127.0.0.1
`*nintendo.fr` -> 127.0.0.1
`*nintendo.fi` -> 127.0.0.1
`*nintendo.de` -> 127.0.0.1
`*nintendo.dk` -> 127.0.0.1
`*nintendods.cz` -> 127.0.0.1
`*nintendo.be` -> 127.0.0.1
`*nintendo.at` -> 127.0.0.1
`*nintendo.co.nz` -> 127.0.0.1
`*nintendo.com.au` -> 127.0.0.1
`*nintendo.com.hk` -> 127.0.0.1
`*nintendo.tw` -> 127.0.0.1
`*nintendo.co.kr` -> 127.0.0.1
`*nintendo.es` -> 127.0.0.1
`*nintendowifi.net` -> 127.0.0.1
`*nintendo-europe.com` -> 127.0.0.1
`*nintendo.co.uk` -> 127.0.0.1
`*nintendo.co.jp` -> 127.0.0.1
`*nintendo.jp` -> 127.0.0.1
`*nintendo.net` -> 127.0.0.1
`*nintendo.com` -> 127.0.0.1
`receive-lp1.er.srv.nintendo.net` -> 127.0.0.1
`receive-lp1.dg.srv.nintendo.net` -> 127.0.0.1
 
Are you implying that (in this case) the last time Switch was online on sysMMC prior to creating emuMMC, it saved the latest update version ID, and the nag isn't going to disappear until that update is installed? That would mean it isn't enough to update to any firmware version...

To be clear, I avoid 21.x due to less memory availability to system modules.


After doing this in addition to relying on the defaults (DNS MITM is enabled without having to explicitly enable it), there was no difference, it works as usual:
DNS Mitm:
Adding defaults to redirection list.
Selecting hosts file...
Skipping /hosts/emummc_32574152.txt because it does not exist...
Selected /hosts/emummc.txt
Redirections:
`*ctest.cdn.nintendo.net` -> 95.216.149.205
`*conntest.nintendowifi.net` -> 95.216.149.205
`*nintendoswitch.cn` -> 127.0.0.1
`*nintendoswitch.com.cn` -> 127.0.0.1
`*nintendoswitch.com` -> 127.0.0.1
`*nintendo.pl` -> 127.0.0.1
`*nintendo.ch` -> 127.0.0.1
`*nintendo.se` -> 127.0.0.1
`*nintendo.co.za` -> 127.0.0.1
`*nintendo.ru` -> 127.0.0.1
`*nintendo.pt` -> 127.0.0.1
`*nintendo.no` -> 127.0.0.1
`*nintendo.nl` -> 127.0.0.1
`*nintendo.it` -> 127.0.0.1
`*nintendo.hu` -> 127.0.0.1
`*nintendo.gr` -> 127.0.0.1
`*nintendo.fr` -> 127.0.0.1
`*nintendo.fi` -> 127.0.0.1
`*nintendo.de` -> 127.0.0.1
`*nintendo.dk` -> 127.0.0.1
`*nintendods.cz` -> 127.0.0.1
`*nintendo.be` -> 127.0.0.1
`*nintendo.at` -> 127.0.0.1
`*nintendo.co.nz` -> 127.0.0.1
`*nintendo.com.au` -> 127.0.0.1
`*nintendo.com.hk` -> 127.0.0.1
`*nintendo.tw` -> 127.0.0.1
`*nintendo.co.kr` -> 127.0.0.1
`*nintendo.es` -> 127.0.0.1
`*nintendowifi.net` -> 127.0.0.1
`*nintendo-europe.com` -> 127.0.0.1
`*nintendo.co.uk` -> 127.0.0.1
`*nintendo.co.jp` -> 127.0.0.1
`*nintendo.jp` -> 127.0.0.1
`*nintendo.net` -> 127.0.0.1
`*nintendo.com` -> 127.0.0.1
`receive-lp1.er.srv.nintendo.net` -> 127.0.0.1
`receive-lp1.dg.srv.nintendo.net` -> 127.0.0.1

Once the system know about there is an update it is kinda too late, it will continue nag you until you update, If 20.5.0 doesn't work for you you might have to go higher firmware I guess.
 
Once the system know about there is an update it is kinda too late, it will continue nag you until you update, If 20.5.0 doesn't work for you you might have to go higher firmware I guess.
I assume there's no harm in trying what I linked earlier?

 
I assume there's no harm in trying what I linked earlier?


If you know how to hex edit then sure, but probably easier if you just update firmware, I mean everything run fine on 21.2.0, if you are already on 20.x.x doesn't matter a lot.
 
  • Like
Reactions: lightwo
Hey all! Long time lurker, love the community and resources here! First post ever. I'm not TOTALLY new, but been out of all the updates for the past few years.

V1 unpatched switch 1, been using rcm to hekate & atmosphere for a loing time with various updates to sig patches when new games came out.

I tried the new Super Mario Galaxy 1+2 from the cart, which forced an update that I stupidly proceeded with. My emummc is now operating at 20.1.5. OFW still remains at 13.x.x

I updated Atmosphere, hekate and all sigpatches, so all my previously installed games work and everything runs fine. So does the Galaxy cartridge, but Tinfoil and other homebrew apps are now having issues.

I used Tinfoil only to install games from their cartridges. What's the best alternative now?

I'm reading into DBI, but it sounds like there's malware or a bricking possibility if using the non-english version. Thanks!
Bumping this. Best way to resurrect tinfoil or is there another better way to dump carts to my switch? DBI? Russian or English version?
 
got these messages after installing Deep Sea CFW from github. anyone familiar and know what to do? please point me in the right direction...
 

Attachments

  • 628564435_3892316227743145_511793496005952059_n.jpg
    628564435_3892316227743145_511793496005952059_n.jpg
    381.5 KB · Views: 16
  • 628181271_3892316184409816_7418078883472263739_n.jpg
    628181271_3892316184409816_7418078883472263739_n.jpg
    367.6 KB · Views: 15
got these messages after installing Deep Sea CFW from github. anyone familiar and know what to do? please point me in the right direction...

Like it says update your hekate, plus deep sea is outdated, it haven't got any update for one year.
 
If you know how to hex edit then sure, but probably easier if you just update firmware, I mean everything run fine on 21.2.0, if you are already on 20.x.x doesn't matter a lot.
Status update: it looks like what I linked is strictly a procedure for bypassing game updates. I was able to extract the save and hex edit it with this method, but whether or not I then make a system update, there is no difference.

Welp, it looks like I hit a brick wall. No browser for me. No big loss, but unfortunate.
 
Looking for some noob help. I have a working switch that needs to be updated.

Previously I was able to update my switch with relative ease in about ten steps or so using the rentry guide. https://web.archive.org/web/20240207052548/https://rentry.org/CaptainsInfo. Where I'm stuck is that the Captains Prepack isn't available any longer. I used to use signpatches, but those are gone now(?) and I don't think that syspatches are the same thing, I'm definitely a noob!

Current Version: 18.0.1 | AMS 1.7.1|E & Hekate 6.2.1

Because I simply followed these steps over the years without issue, I never learned the ins and outs of the process.

Again, the current switch is working fine on 18.0.1, but there are a few games that just won't work. So sorry if this has been asked, this thread is thousands of pages longs! Any help would be appreciated! Thank you
 
Looking for some noob help. I have a working switch that needs to be updated.

Previously I was able to update my switch with relative ease in about ten steps or so using the rentry guide. https://web.archive.org/web/20240207052548/https://rentry.org/CaptainsInfo. Where I'm stuck is that the Captains Prepack isn't available any longer. I used to use signpatches, but those are gone now(?) and I don't think that syspatches are the same thing, I'm definitely a noob!

Current Version: 18.0.1 | AMS 1.7.1|E & Hekate 6.2.1

Because I simply followed these steps over the years without issue, I never learned the ins and outs of the process.

Again, the current switch is working fine on 18.0.1, but there are a few games that just won't work. So sorry if this has been asked, this thread is thousands of pages longs! Any help would be appreciated! Thank you


You can follow this, but there is few things to keep in mind going higher firmware there are less memory for homebrew. For firmware 20.x.x/and 21.x.x it has less memory compare to firmware 18.x.x down from 40MB to 14MB, so it might cause some problem if the person use a lot of sysmodules. As for 20.x.x and beyond there is also slowdown in the all software list when you load the icons, in addition there is a battery draining problem that can be fixed.
 
Last edited by Hayato213,
  • Like
Reactions: nytech9
So I recently updated to 20.5.0. All went well.

But now I have a young doughter where I would like to play Kirby with. So I want to use Edizon cheats.

Are Nx overlay and Edizon still suported on 20.5.0? Because it seems they haven't been updated in a while when checking github?

Also I keep my switch strictly offline, so no internet connection. Is there like a place where I can download the most recent cheat database and just drag it on the SD card?

Thanks in advance for any help.
 
Hi, looking to some advices :) as I get a bit confused just hanging around
My Erista V1 patched has a sx core (1.3fw) running sx os 3.0.5 and 10.2.0 ofw,
I'd like to update all system but looks like debug usb doesn't work as windows didn't dect the core at all.
What's best option?
Is it possible to replace core with any other newer board, keeping actual flat?
Thanks
 
Hi, looking to some advices :) as I get a bit confused just hanging around
My Erista V1 patched has a sx core (1.3fw) running sx os 3.0.5 and 10.2.0 ofw,
I'd like to update all system but looks like debug usb doesn't work as windows didn't dect the core at all.
What's best option?
Is it possible to replace core with any other newer board, keeping actual flat?
Thanks

What is your goal? to use Atmosphere?
 

Site & Scene News

Popular threads in this forum