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

burhansalih · Aug 2, 2020

Wait for the patches I’m sure they’ll be out soon.

mathew77 · Aug 2, 2020

burhansalih said:
they’ll be out soon.

Soon..™®©

Sylphia · Aug 2, 2020

Oh, after search a bit I think I'll go back to fss0, patches worked.

threads/latest-fs-and-acid-patches-for-kosmos.562915/page-23#post-9154168

sorry I can't post full url because I'm new to here

mathew77 · Aug 2, 2020

Sylphia said:
patches worked.

They don't work with fusee-primary, I guess.

Sylphia · Aug 2, 2020

mathew77 said:
They don't work with fusee-primary, I guess.

Yeah, they are for fss0.
Why should I use fusee-primary if fss0 worked, boot faster?

Freizuegig · Aug 2, 2020

Just to get things straight. I had to redo the whole process for my switch and i am now on Atmo 0.14.0. Iam booting via Atmosphere FSS0 EmuMMC.

Do i have to wait for the new sigpatches to install and use the newest "things" on my cfw ?
Sorry for this question but i didnt understand the differences between fuse-primary and so on
Many thanks in advance

mathew77 · Aug 2, 2020

Sylphia said:
Why should I use

You don't «need to», it's just a matter of choice.
I prefer fusee-primary booting, without messing up with the hekate's fss0.

Sylphia · Aug 2, 2020

Freizuegig said:
Just to get things straight. I had to redo the whole process for my switch and i am now on Atmo 0.14.0. Iam booting via Atmosphere FSS0 EmuMMC.

Do i have to wait for the new sigpatches to install and use the newest "things" on my cfw ?
Sorry for this question but i didnt understand the differences between fuse-primary and so on
Many thanks in advance

see #303

Hoowahman · Aug 2, 2020

You probably should delete that patch as everyone is getting black screen with it...

peteruk · Aug 2, 2020

For such an important topic you would think we could get this Stickied in this sub forum

Tokiwa · Aug 2, 2020

Patches in general seems to be broken with 0.14, i have another Switch without sigpatches and enabling the nogc patch gives me a black screen.

mathew77 · Aug 2, 2020

Tokiwa said:
Patches in general seems to be broken with 0.14

So-o-o, chances that we will have working sigpatches are going low?..

Tokiwa · Aug 2, 2020

mathew77 said:
So-o-o, chances that we will have working sigpatches are going low?..

I could be wrong but it seems to be a bug with Atmosphere, we'll probably need to wait for a fix on atmosphere side.

For now i recommend everyone to stick with 0.13, which is what i'll be doing with my main switch.

Ibcap · Aug 2, 2020

Sylphia said:
Yeah, they are for fss0.
Why should I use fusee-primary if fss0 worked, boot faster?

Well for one thing a specific app thats very popular only works on fusee primary but if you dont use that app then go ahead.

Lacius · Aug 2, 2020

Tokiwa said:
I could be wrong but it seems to be a bug with Atmosphere, we'll probably need to wait for a fix on atmosphere side.

For now i recommend everyone to stick with 0.13, which is what i'll be doing with my main switch.

You are probably correct. Adding an empty patch for loader causes a black screen.

Ibcap · Aug 2, 2020

Ive seen claims now that at least one person has managed to get the patches to work without black screening and actually launch unsigned apps with them but I cannot replicate it. Maybe theres some setting causing it?

mathew77 · Aug 2, 2020

Lacius said:
Adding an empty patch for loader causes a black screen.

It didn't do intentionally as a custom sigpatches-protection, isn't it?

Lacius · Aug 2, 2020

mathew77 said:
It didn't do intentionally as a custom sigpatches-protection, isn't it?

No. The issue also allegedly occurs enabling/disabling nogc. It's being looked at. Assuming it's an Atmosphere bug, a fix will likely be released within the next few days.

In the meantime, there is no reason for most users not to use 0.13, unless you want to use Daybreak. After using Daybreak to update, one can also switch back to 0.13 for the time being.

Ibcap · Aug 2, 2020

Lacius said:
No. The issue also allegedly occurs enabling/disabling nogc. It's being looked at. Assuming it's an Atmosphere bug, a fix will likely be released within the next few days.

In the meantime, there is no reason for most users not to use 0.13, unless you want to use Daybreak. After using Daybreak to update, one can also switch back to 0.13 for the time being.

Can confirm I got the patches working by using a new sd with a fresh atmosphere copy

Since these do work, do people want me to update the thread with a disclaimer to toggle nogc to make them work or should I leave it for now

Lacius · Aug 2, 2020

Ibcap said:
Can confirm I got the patches working by using a new sd with a fresh atmosphere copy

Since these do work, do people want me to update the thread with a disclaimer to toggle nogc to make them work or should I leave it for now

What happens if you manually enable or disable nogc?

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

Well-Known Member

Lovin' life.

Member

Lovin' life.

Member

New Member

Lovin' life.

Member

Member

Well-Known Member

Well-Known Member

Lovin' life.

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Lovin' life.

Well-Known Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum