Toggle sidebar

Hacking Sigpatches for Atmosphere (Hekate, fss0, fusee & package3)

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,313,959
  • Replies Replies 7,368
  • Likes Likes 266
Borsalino said:
Top homebrews personally you use? And some top recommendation of sys-modules. I remember I was using tesla before and it got complicated on my brain so I removed it. But I'm willing to try it again.

What I currently have:

Homebrew:
JKSV, Switch_90DNS_tester, Edizon

Sysmodules:
sys-ftpd-light, sys-clk, MissionControl
Click to expand...
For me personally, my main Homebrew is Sphaira a replacement for HomeBrew Menu, Homebrew Store GUI, Filebrowser, Theme downloader and installer, FTP, MTP navigator/installer, titles installer, HOS forwarder creator and more.

TESLA, Now UltraHand & Overlays for overlay management (GBATemp Thread)
JKSV for gamesaves backup/restore (GBATemp Thread)
NSO-Icon-Tool for change my profile photo (GBATemp Thread)
Solarus Engine for Zelda like games (GBATemp Thread)
Super Mario 64 for Nintendo Switch Port (GBATemp Thread)

and some others Homebrew so niche.

on the homebrew store you can find lots of Homebrew. Sphaira mentioned before have a GUI to this store directly on the console.
 
Last edited by impeeza,
  • Like
  • Love
Reactions: aarstar, fabianon, Tyvar1 and 3 others
impeeza said:
I personally my main Homebrew is Sphaira a replacement for HomeBrew Menu, Homebrew Store GUI, Filebrowser, Theme downloader and installer, FTP, MTP navigator/installer, titles installer, HOS forwarder creator and more.

TESLA, Now UltraHand & Overlays for overlay management (GBATemp Thread)
JKSV for gamesaves backup/restore (GBATemp Thread)
NSO-Icon-Tool for change my profile photo (GBATemp Thread)
Solarus Engine for Zelda like games (GBATemp Thread)
Super Mario 64 for Nintendo Switch Port (GBATemp Thread)

and some others Homebrew so niche.

on the homebrew store you can find lots of Homebrew. Sphaira mentioned before have a GUI to this store directly on the console.
Click to expand...
Now I’m extra excited to start from scratch. Thank you for the recommendations!

Small update: I finished doing h2testw although not every part of the micro sd card was tested. No errors were found

Code: 
Warning: Only 309686 of 458172 MByte tested.
Test finished without errors.
You can now delete the test files *.h2w or verify them again.
Writing speed: 25.5 MByte/s
Reading speed: 85.0 MByte/s
H2testw v1.4
 
Last edited by Borsalino,
  • Like
  • Love
Reactions: Tyvar1, Blythe93 and impeeza
I updated my switch from 17. something to 20.2.0. Got the kip and exefs patches you sent and also downloaded a fresh copy of syspatch and put it contents. When I boot and check my ovl, sys-patch log says that noncasigchk_new was Unpatched and then noacidsigchk, es3 and nim were patched by something else (orange colour). As a result none of my games launch.

Is there something I can delete from the atmosphere folder or change in my config?

Also I noticed the ipl example you uploaded in that zip says for the emmc boot option:

fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/emu_boot.bmp

but I used to also have a line saying
kip1=atmosphere/kips/*
Do I need that removed ot should I keep it?
 
20.3.0 still same:


Code: 
a "MOV" arm instruction with ending of 0x2A was found within the pattern

Sys-patch for ES string still valid for: 20.3.0

Sys-patch ES pattern found at: 076B18

The ghidra-equivalent pattern used was: .. .. 00 .. .. .. 00 94 a0 .. .. d1 .. .. ff 97 .. .. .. .. .. .. .. a9

An arm "MOV" condition is what is supposed to be patched at this offset

an "STP" arm instruction with ending of 0xA9 was found proceding the pattern

Sys-patch for NIFM string still valid for: 20.3.0

Sys-patch NIFM pattern found at: 087BC0

The ghidra-equivalent pattern used was: 14 .. .. .. .. .. .. .. .. .. .. .. 91 .. .. .. .. .. .. .. .. .. .. .. 97 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 14

An arm "STP" condition is what is supposed to be patched at the offset right after the branch arm condition tested ("B")

a "ADR" arm instruction with ending of 0x10 was found within the pattern

Sys-patch for NIM string still valid for: 20.3.0

Sys-patch NIM pattern found at: 190EF8

The ghidra-equivalent pattern used was: .. 0F 00 35 1F 20 03 D5 .. .. .. ..

An arm "ADR" condition is what is supposed to be patched at the offset right after the "CBNZ and "NOP" conditions the pattern finds

a "TBZ" arm instruction with ending of 0x36 was found within the pattern, first pattern verified

a "BL" arm instruction with ending of 0x94 was found within the pattern, second pattern verified

both sys-patch strings are valid for FS-FAT32 for: 20.3.0

20.3.0 First Sys-patch FS-FAT32 pattern found at: 023C88

The ghidra-equivalent pattern used was (11.0.0+) : .. 94 .. .. 00 36 .. 25 80 52

An arm "TBZ" condition is what is supposed to be patched, it is found within the pattern.

20.3.0 Second Sys-patch FS-FAT32 pattern found at: 07A880

The ghidra-equivalent pattern used was (19.0.0+) : 40 f9 .. .. .. 94 .. .. 40 b9 .. .. 00 12

An arm "BL" condition is what is supposed to be patched, it is found within the pattern.

20.3.0 FS-FAT32 SHA256 hash: ED34B450584A5B43150CFF94D6A7C49F6B7F4C649B7CC6A0D8A0BB316EB52B76


FS-exFAT was skipped for: 20.3.0, due to missing NCA file for exfat in the provided firmware files.
 
  • Like
  • Love
Reactions: Tokiwa, impeeza, Blythe93 and 4 others
Yes, just added version to AMS and Mission Control code and all working
 

Attachments

  • IMG_20250729_124142_927.jpg
    IMG_20250729_124142_927.jpg
    266 KB · Views: 43
  • Like
  • Love
Reactions: mauroalexand, Tokiwa, impeeza and 2 others
Hi @impeeza !

I managed to do a fresh start on my switch and did a file based Emunand this time around. Also installed the newer tesla overlay and some overlays. Included Sphaira as well.

I'm a little bit outdated in terms of network. How do I make sure that when I connect my Emunand to my wifi, I don't get detected by Nintendo?

EDIT/UPDATE:
The setup I was following instructed me to add an emummc.txt on SD:/atmosphere/hosts folder. These are the logs I get from my dns_mitm_startup.log.

Code: 
DNS Mitm:
Adding defaults to redirection list.
Selecting hosts file...
Skipping /hosts/emummc_xxxxxxx.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

I think it's safe to assume that I should be fine connecting to my wifi?
 
Last edited by Borsalino,
  • Like
Reactions: Blythe93
Borsalino said:
Hi @impeeza !

I managed to do a fresh start on my switch and did a file based Emunand this time around. Also installed the newer tesla overlay and some overlays. Included Sphaira as well.

I'm a little bit outdated in terms of network. How do I make sure that when I connect my Emunand to my wifi, I don't get detected by Nintendo?

EDIT/UPDATE:
The setup I was following instructed me to add an emummc.txt on SD:/atmosphere/hosts folder. These are the logs I get from my dns_mitm_startup.log.

Code: 
DNS Mitm:
Adding defaults to redirection list.
Selecting hosts file...
Skipping /hosts/emummc_xxxxxxx.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

I think it's safe to assume that I should be fine connecting to my wifi?
Click to expand...
yes, Atmosphère's DNS MiTM is the current protection layer, you can go to https://gbatemp.net/threads/switch-noob-paradise-ask-questions-here.488277 and more people can help you with your questions that thread is constantly monitored by several tempers.
 
  • Like
Reactions: grimson, Tyvar1, Blythe93 and 1 other person
Sorry, I accidentaly updated to 20.3.0 firmware and I used an unnoficial atmosphere version that the owner posted

"cant start program, try again in home menu"

It works, but when I install a nsp for example homebrew app and I enter it, I get a error


Do you know why? Thanks for your help !!
 

Attachments

  • photo_2025-07-30_00-16-40.jpg
    photo_2025-07-30_00-16-40.jpg
    64.8 KB · Views: 47
  • Like
Reactions: NeoGranzon
angelus kun said:
Thanks brooo as always patches are working great but idk why noacidchk_new is always unpatched? Am I doing something wrong?
Click to expand...
nothing wrong that patch is only for a specific firmware version, for others firmware version there are others Noacid ones.
 
  • Like
Reactions: Blythe93 and angelus kun
Okay, what gives? I just updated from OFW 19.0.1 to 20.3.0 after also updating Atmosphere to 1.9.3.

Everything worked upfront, and loads correctly. But when I go to navigate through my games, the icons load VERY slowly, and selecting any game results in a generic "Failed to open Software" message. These were games that already worked on 19.0.1.

These are the steps I followed. Can someone please tell me what I missed? Please note that I do not use Hekate, and I keep my Switch on Airplane mode, so I didn't mess with any ini files.

(I did notice that there's no longer a dedicated sigpatches folder in the sigpacthes update zip, which I found on the a few posts above in this thread.)

- Plug SD card into PC.
- Delete the following atmosphere folders:
- contents (or titles)
- crash_reports
- erpt_reports
- fatal_reports

- Extract new atmosphere folder contents to SD card root.
- Copy sigpatches folder contents to root of SD, overwrite all duplicates.
- Create folder for firmware, copy over the extracted files.

- Plug in USB Dongle.
- Replace the "fusee.bin" file both on SD and USB Dongle.
- On the Dongle, you may need to rename the file to match the file name in the other folders.
- Eject SD and Dongle.

- Insert SD and Dongle onto Switch, power on.
- If everything looks ok, launch the Homebrew Loader and run Daybreak.
- Choose "FAT32 + exFAT, "Preserve Settings".
- After installation and reboot, check System Settings for updated FW.
 
  • Like
Reactions: Willsito_GG
Eye-V-Sore said:
Okay, what gives? I just updated from OFW 19.0.1 to 20.3.0 after also updating Atmosphere to 1.9.3.

Everything worked upfront, and loads correctly. But when I go to navigate through my games, the icons load VERY slowly, and selecting any game results in a generic "Failed to open Software" message. These were games that already worked on 19.0.1.

These are the steps I followed. Can someone please tell me what I missed? Please note that I do not use Hekate, and I keep my Switch on Airplane mode, so I didn't mess with any ini files.

(I did notice that there's no longer a dedicated sigpatches folder in the sigpacthes update zip, which I found on the a few posts above in this thread.)

- Plug SD card into PC.
- Delete the following atmosphere folders:
- contents (or titles)
- crash_reports
- erpt_reports
- fatal_reports

- Extract new atmosphere folder contents to SD card root.
- Copy sigpatches folder contents to root of SD, overwrite all duplicates.
- Create folder for firmware, copy over the extracted files.

- Plug in USB Dongle.
- Replace the "fusee.bin" file both on SD and USB Dongle.
- On the Dongle, you may need to rename the file to match the file name in the other folders.
- Eject SD and Dongle.

- Insert SD and Dongle onto Switch, power on.
- If everything looks ok, launch the Homebrew Loader and run Daybreak.
- Choose "FAT32 + exFAT, "Preserve Settings".
- After installation and reboot, check System Settings for updated FW.
Click to expand...
Install latest SYS-Patch Sysmodule.
 
  • Like
Reactions: Blythe93
impeeza said:
Install latest SYS-Patch Sysmodule.
Click to expand...
Thank you for the help - that worked!! The pre-boot period for each game has a 2-3 second blank screen now, but it always ends up working and proceeds fine from there. And navigating the Ui has sped up again too.

So, next time, do I still need to "update my sigpatches" using zips from this thread, or can I skip that step entirely?
 
Last edited by Eye-V-Sore,
Eye-V-Sore said:
Thank you for the help!

So, is that required now? I thought it was merely supplementary. How does it work exactly, relative to the old sigpatches method?

And by "install", can you please provide exact instructions?
Click to expand...
They are easy for people which have hard time following instructions.

installation is download them from https://gbatemp.net/download/sys-patch-sysmodule.39124/ and extract the ZIP file to the root of your SD Card, replace all files.
 
  • Like
Reactions: mauroalexand, Krazyeye, Blythe93 and 1 other person
Eye-V-Sore said:
Thank you for the help - that worked!! The pre-boot period for each game has a 2-3 second blank screen now, but it always ends up working and proceeds fine from there. And navigating the Ui has sped up again too.

So, next time, do I still need to "update my sigpatches" using zips from this thread, or can I skip that step entirely?
Click to expand...
its a preference but myself i use both syspatch and the sig patches by downloading the package 3 in this thread
 
  • Like
  • Love
Reactions: Krazyeye, Blythe93 and impeeza
firmware V20.3.0 + atmosphere v1.9.3 + sigpatch v0 for firmware v20.3.0 make youtube and tinfoil v20 alive again.
 
Last edited by johnliu,

Site & Scene News

Go to forum More news

Popular threads in this forum

Emulation Emulator  NetherSX2 - Switch Port

Dekopon - (Mostly) Fullspeed 3DS Emulation on Nintendo Switch

Emulation Emulator  Cemu - Wii U Emulator - Switch Port

Homebrew Homebrew game  Ultimate Switch Port Thread

Emulation Emulator  DrasticDS Emulator - Switch Port

Homebrew Homebrew game  Castlevania Symphony of the Night - Switch port

Homebrew Homebrew game  Angry Birds Classic - Switch Port

Homebrew Homebrew game  Castle of Illusion - Switch port