Hacking RELEASE Sigpatches for Atmosphere (fusee-primary only!)

[Ibcap]

I've already partially addressed that with the faster boot times as well as with the emuMMC options. Additionally, booting with fusee as opposed to fss0 means you have to configure BCT.ini as opposed to hekate_ipl.ini which is not as easy since you can modify hekate_ipl.ini from within Hekate but you have to edit BCT.ini manually. This is why so many users had nogc issues despite disabling it in Hekate.

Which is partially hekates fault. Hekate has a generic option for disabling nogc without prefacing that it only works for certain configs and does not support the official atmosphere payload. I will agree though it would be nice if atmosphere added a payload or homebrew program to configure settings such as nogc or if hekate added the option. Wouldnt be too hard to do since youre just modifying an ini.

 

[MichelRT24]

Pokemon Sword is working fine here as well using these patches + AMS 0.13.0 on FW 10.0.4. I tested a dozen of other games and all of them are booting just fine.

finally it was ldn_mitm "fault", i deleted and the game works fine

 

[adimah]

Thank you for this, just bought a new switch and was looking for the latest Sigpatches. Took some time to set the switch up with Atmosphere but well worth the effort.

 

[Cheesycod]

Theres a few reasons I recommend primary over fss0, none of them make it objectively better but just my recommendation.
Firstly, anecdotally is has fewer issues. Usually from my experience when people have problems related to games not working switch to fusee primary and its sigpatches fixes the issue.
Secondly its much simpler for support. By this what i mean is users generally dont know if they are using primary or fss0 and trying to get them to figure it out for giving support is a nightmare. Because of this on the discord servers I mod we tend to just recommend fusee primary, because it will cut down on support time and confusion by just having everyone use the same method.
Thirdly, it tends to have faster and better support. The sigpatches always come out for it before fss0 and a certain homebrew app tends to really not like fss0.
If you know what youre doing feel free to use fss0, this is just a personal recommendation not me saying fss0 is bad.

As for booting, usually I would recommend people swapping from sysnand and emunand use the hekate stock sysnand function and chainload emunand through fusee primary. If you want to use both sysnand and emunand with cfw you can keep one as fss0 or just keep using what works for you.

Also, important note: you can solve this in TegraRCMGUI by just having different payloads to load.

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

Also, good work on your sigpatches!

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

@lbcap Can I have an invite link to your discord server

 

[Ibcap]

@lbcap Can I have an invite link to your discord server

Not sure Im allowed to share links to the servers I mod here. The names are Jackintheshop (JITS), Reloaded (rebirth) and Wareznx for reference.

 

[poptool]

Thanks for sharing

 

[BaffledBatsandSlother]

Getting an NCA error when trying to install mario64 v6 homebrew NSP with these patches, the exact same nsp worked fine installing on older patches yesterday. "Error 2002-4518, Description: Invalid NCA, might mean missing sigpatches or too low firmware". I'm on 10.0.0.4

 

[Ichigo1990]

support emummc
how
please tell me

 

[Ibcap]

support emummc
how
please tell me

The same as usual? They're just sigpatches not a cfw.

 

[homaru]

Hello guys
I don't know what to do to make everything work as it should. I have had a problem with my Switch for 2 days ... I can't deal with this problem.
CFW: Hetake
Current system version: 10.0.4 | AMS 0.13.0 | E
After installing the Tinfoil and Goldbricks applications, I get the information:
Could not start software
Please try again from the HOME Menu
When I try to run Lithium, everything looks good at first (of course I can only run from Album) but when I try to install NSZ, I get the information:
error
Allocation error: not enough memory.
I have no idea what I have to do honestly, can anyone tell me what to do so that I can install games without problems?
Greetings!

 

[Ibcap]

Hello guys
I don't know what to do to make everything work as it should. I have had a problem with my Switch for 2 days ... I can't deal with this problem.
CFW: Hetake
Current system version: 10.0.4 | AMS 0.13.0 | E
After installing the Tinfoil and Goldbricks applications, I get the information:
Could not start software
Please try again from the HOME Menu
When I try to run Lithium, everything looks good at first (of course I can only run from Album) but when I try to install NSZ, I get the information:
error
Allocation error: not enough memory.
I have no idea what I have to do honestly, can anyone tell me what to do so that I can install games without problems?
Greetings!

First issue, hekate is not a cfw. Second issue, the reason tinfoil is failing to run is probably that you're using kosmos/fss0 and these sigpatches only work for atmosphere. The memory issue sounds like you're out of space on your sd or nand.

 

[zedrex98]

hi i need help i am running system 10.0.4 AMS 0.13.0 and Tinfoil is not working with it, i added these patches and it still isnt working with it, it keeps saying that it is corrupt.

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

hi i need help im running softwear 10.0.4 AMS 0.13.0 and tinfoil is apparently corrupt so i added the patches and i am still getting the same issue.

 

[kasboy]

I have been having problems with my switch. 9.1.0, I had atmosphere 0.11.1 and decided to upgrade to 0.13.0 and I got error of 04000001 (or something like that) and then 0100000010D or something of the sort.
I have been wandering here and there on the web to seek answers but seems no one has.
It works fine when clean upgrade, meaning deleting switch, atmosphere, config, etc.
but as soon as I get Idm_mitm, hb app store, tinfoil, goldleaf, etc ( my usual apps), keeps crashing.


I deleted the folders. since I read somewhere that that might solve it but... well, doesn't seem to be a permanent solution. I don't now what 040000001 was. I think maybe Idm_mitm_ or maybe even tinfoil (if tinfoil, I won't be able to play xci)
have not turned on and obviously, not placed the Sd inside, yet...

 

[kasboy]

I tried. now It ran. I could load the mario odyssey. but when I got out of it and tried to enter hbmenu, it shows a 010000000000100D error

 

[BaffledBatsandSlother]

Any idea why these patches don't work with Mario 64 switch port v6 but the patches I got from sdsetup.com work?

 

[Tokiwa]

Any idea why these patches don't work with Mario 64 switch port v6 but the patches I got from sdsetup.com work?

Are you booting with fusee-primary.bin?

 

[Ibcap]

Any idea why these patches don't work with Mario 64 switch port v6 but the patches I got from sdsetup.com work?

Because as Tokiwa is alluding to you arent using the atmosphere payload. These patches definitely work with the mario 64 switch port, my group has been releasing the updates for it starting v3 and on.

 

[pofehof]

For example, you cannot tell if you booted emuMMC or not with Fusee unless you use different themes and even then, fusee will not hesitate to kick you into sysMMC.

That is pretty misleading. Even if you simply launch through fusee, going to system settings will tell you whether you are in sysMMC or emuMMC.

Additionally, booting with fusee as opposed to fss0 means you have to configure BCT.ini as opposed to hekate_ipl.ini which is not as easy since you can modify hekate_ipl.ini from within Hekate but you have to edit BCT.ini manually.

Usually, a majority of people will either use CFW only on sysMMC or emuMMC, not both. Because of that, people do not really need to worry about editing that file since it defaults to emuMMC (if detected). Boot times also are a non-issue since you could simply put your Switch to sleep after turning it on.

In the end, chainloading fusee-primary through hekate is likely the best thing to do since atmosphere patches will likely be updated more often instead of fss0 patches.

 

[Draxzelex]

That is pretty misleading. Even if you simply launch through fusee, going to system settings will tell you whether you are in sysMMC or emuMMC.

Its not misleading from the point of view from someone who wants to avoid launching sysMMC by accident and to incur a ban. It also doesn't make sense to check what you booted after the fact when only one tool will check what you boot beforehand.

Usually, a majority of people will either use CFW only on sysMMC or emuMMC, not both. Because of that, people do not really need to worry about editing that file since it defaults to emuMMC (if detected). Boot times also are a non-issue since you could simply put your Switch to sleep after turning it on.

In the end, chainloading fusee-primary through hekate is likely the best thing to do since atmosphere patches will likely be updated more often instead of fss0 patches.

However because of that, it makes it impossible to launch both sysMMC or emuMMC at your will if you have AutoRCM enabled which there is no reason to use nowadays. And regardless of sleep mode, the slower boot time is still a con. Lastly, there has never been a time when fss0 patches have not been updated. Even when they came out after the fusee patches, those patches were never required for CFW, the latest firmware, or any games unless you were the type to be on the bleeding edge which is rare.

In the end, fusee is inferior and useless compared to Hekate. If you want to use it, that is your perogative but it holds no value.

 

[Mister_X]

Im in 10.0.4 with emummc and i have problems with the burnout game.... always installs fine, but when i go to check corrupt data... There´s some corrupt data... i try diferents sd´s, installers, sigpatches... i make a nsp from the dump of my cartdrige, i make xci and convert to nsp... and always the same result... Any idea?