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

[ShadowOne333]

Sorry for the long delay.
I just updated the OP to include the sigpatches for Atmosphere 0.19.1.

Updated both the IPS patches (Loader) and the Hekate's INI with the latest Atmos release.
Afaik, the FS and ES patches remain the same, since FW version 12.0.0 patches were already addressed for the 0.19.0 release, and FW hasn't been updated since the Atmos 0.19.1 release.

 

[Pienkaito]

Hi, I´ve recently updated everything (FW 12.0.0+Atmosphère 0.19.1+Hekate v5.5.5) and I was nearly done with only sigpatches missing.
Launching any game only gives me the cursed "Could not start the software."

Homebrew Menu (Applet Mode) can launch the newest homebrew, so the install can´t be the issue.
I´ve deleted the folders "atmosphere" and "bootloader" on my root SD before updating and inserted the sigpatches at the very end.

Any ideas what I could be doing wrong?
Thanks in advance.

 

[petspeed]

Hi, I´ve recently updated everything (FW 12.0.0+Atmosphère 0.19.1+Hekate v5.5.5) and I was nearly done with only sigpatches missing.
Launching any game only gives me the cursed "Could not start the software."

Homebrew Menu (Applet Mode) can launch the newest homebrew, so the install can´t be the issue.
I´ve deleted the folders "atmosphere" and "bootloader" on my root SD before updating and inserted the sigpatches at the very end.

Any ideas what I could be doing wrong?
Thanks in advance.

What payload do you use?
Where did you download the sigpatches?

 

[mathew77]

Hmm, I guess we need a new es/fs sigpatches for the new OFW 12.0.1, right?

 

[burhansalih]

Hmm, I guess we need new es/fs sigpatches for new OFW 12.0.1, right?

I think we will yes

 

[Pienkaito]

What payload do you use?
Where did you download the sigpatches?

I use hekate and the sigpatches in OP.

 

[pofehof]

Hmm, I guess we need a new es/fs sigpatches for the new OFW 12.0.1, right?

Don't think so, since it wasn't a big update. I created ES and FS patches with 12.0.1, and they are exactly the same as the ones created from 12.0.0.

Didn't need to update my patches (for fusee-primary) when I updated to 12.0.1.

 

[burhansalih]

Don't think so, since it wasn't a big update. I created ES and FS patches with 12.0.1, and they are exactly the same as the ones created from 12.0.0.

Didn't need to update my patches (for fusee-primary) when I updated to 12.0.1.

I was under the impression that every update requires ES & FS patches or am I mistaken?

If you do not then happy days.

 

[pofehof]

I was under the impression that every update requires ES & FS patches or am I mistaken?

Only if there's a noticeable change. According to SciresM, they only updated Bluetooth and bsdsockets, which is why Atmosphere 0.19.1 still works and why ES and FS patches haven't changed.

 

[ShadowOne333]

So no need to update the sigpatches then?
The current ones for 0.19.1 and 12.0.0 work for 12.1 as well?

 

[burhansalih]

Only if there's a noticeable change. According to SciresM, they only updated Bluetooth and bsdsockets, which is why Atmosphere 0.19.1 still works and why ES and FS patches haven't changed.

fantastic thank you for confirming. Once I get my switch back I’ll give it a go.

Thank you

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

So no need to update the sigpatches then?
The current ones for 0.19.1 and 12.0.0 work for 12.1 as well?

sounds correct according to the above posts

 

[tNz]

Has anyone already got emummc to run with the latest version? With the sigpatches and the latest hekate and atmos version, I only get a black screen when starting emummc.

 

[impeeza]

Don't think so, since it wasn't a big update. I created ES and FS patches with 12.0.1, and they are exactly the same as the ones created from 12.0.0.

Didn't need to update my patches (for fusee-primary) when I updated to 12.0.1.

Hi, this is in part correct, if the checksum of the files needed to be patches doesn't change and the addresses of the patches still the same, the sigpatches will work fine, this was the case for firmwares 09.0.0 & 09.0.1 but not the case of 08.1.0 & 08.1.1.

 

[impeeza]

I Just download firmware 12.0.1 from Darthsternie and used AutoIPS to generate the patches on it and can confirm the addresses and checksums are the same so the sigpatches for 12.0.0 are the same for 12.0.1

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

Has anyone already got emummc to run with the latest version? With the sigpatches and the latest hekate and atmos version, I only get a black screen when starting emummc.

For me i have a EmuMMC in FW 12.0.0 and Atmosphère 0.19.1 and works fine on almost every homebrew, a few need to recompile but the work is in progress.

 

[JBizzle3rd]

Has anyone already got emummc to run with the latest version? With the sigpatches and the latest hekate and atmos version, I only get a black screen when starting emummc.

me too looks like we need an update patches.ini file

 

[Goku1992A]

Ive been using my Switch without any issues, im just asking if anyone besides Darthsternie uploads firmware cause I can't find it anywhere.

It isn't a good practice to use a dirty SYSNAND IMO. The banrisk is incredibly high and if you botch a firmware update your switch will be bricked but use at your own risk. The safe approach is emummc considering your SYSNAND will be intact for OFW use and you can use the emummc for CFW/Homebrew use.

All my friends gotten banned from dirty sysnand

 

[JBizzle3rd]

Has anyone already got emummc to run with the latest version? With the sigpatches and the latest hekate and atmos version, I only get a black screen when starting emummc.

me as well, we need an updated patches.ini file

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

Hi, I´ve recently updated everything (FW 12.0.0+Atmosphère 0.19.1+Hekate v5.5.5) and I was nearly done with only sigpatches missing.
Launching any game only gives me the cursed "Could not start the software."

Homebrew Menu (Applet Mode) can launch the newest homebrew, so the install can´t be the issue.
I´ve deleted the folders "atmosphere" and "bootloader" on my root SD before updating and inserted the sigpatches at the very end.

Any ideas what I could be doing wrong?
Thanks in advance.

any game that you tried to launch and received an error will have to be deleted and reinstalled. Can yo install a game?

 

[tNz]

me as well, we need an updated patches.ini file

Where can we get the updated patches.ini file?

 

[blindseer]

I don'

Where can we get the updated patches.ini file?

I don't understand, the sigpatches from the op work fine on ams 19.1, firmware 12.0.1 and hekate 5.5.5. Did you do a clean install?
I did get a black screen the first time I tried booting after updating my emummc but after a reboot it works fine.

 

[tNz]

I don'

I don't understand, the sigpatches from the op work fine on ams 19.1, firmware 12.0.1 and hekate 5.5.5. Did you do a clean install?
I did get a black screen the first time I tried booting after updating my emummc but after a reboot it works fine.

Yeah I did a clean install. I downloaded Atmosphere and Hekate directly from the Git Repos and the Sigpatches from here. Then I set up 2 emummcs on the SD card with the NAND firmware 3.0.1. However, I don't get the emummcs started. Only the hekate boot logo appears. With Atmosphere 0.18.1 and hekate 5.5.4 it works without any problems.

My hekate_ipl.ini:

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=0
updater2p=0
bootprotect=0


{--- Custom Firmware ---}
[CFW (Online)]
emummcforce=1
emupath=emuMMC/RAW1
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

[CFW (Offline)]
emummcforce=1
emupath=emuMMC/RAW2
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}