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

[condector]

You really should stay away of all in one packages IF YOU DON'T KNOW REALLY WHAT EACH THING IS AND HOW WORKS. read the https://rentry.org/SwitchHackingIsEasy guide to understand the basics and then you can handle your console by yourself.

Mr impeeza, maybe you need to quote the original guy that post about the package.

I agree with you. It is better to read about and do it by yourself, but, considering his question, I imagine that maybe was clever to him to ask from whom he get the package at all.

 

[impeeza]

yep my bad, missed one quote, fixed!

 

[MightySashiman]

yep my bad, missed one quote, fixed!

for a new comer trying to understand things, the rentry guide is confusing within the first few lines... I still talks about fusee.bin although this is supposed to be obsolete in favour of atmosphere/package3, isn't it?

 

[impeeza]

for a new comer trying to understand things, the rentry guide is confusing within the first few lines... I still talks about fusee.bin although this is supposed to be obsolete in favour of atmosphere/package3, isn't it?

No is not, Fusee.bin is the payload, the fusee.bin code then loads Package3 file.

also you can use Hekate as payload, then instruct Hekate to Load Fusee.bin or directly Package3 (recommended)

 

[alcab]

Why is Package3 recommended over booting with the modded version of fusee.bin? I usually do the opposite...

Thanks for all your help!

 

[TomSwitch]

@impeeza any reason why not just have sys-patch alone? I am using your sys-patch-1.5.1_Updated-PR.zip should I change to your newer release?

 

[guily6669]

Why is Package3 recommended over booting with the modded version of fusee.bin? I usually do the opposite...

Thanks for all your help!

Snakes says to use Hekate FSSO, fishes say to use Fusee so yeah... Hekate is also faster to boot but I don't see much difference at least not using autoboot...

I like using fusee cause for some reason with Hekate FSS0 I can't play games above my FW while with with fusee I'm on FW 17.0.1 and can play FW18 games without needing to update.

But now that fusee doesnt support sigpatches, it's likely that a lot of people might prefer to use FSS0 with hekate sigpatches or have to use modded fusee payload or have to use sys-patch system module and I like the less modules the better for me.

I'm using modded fusee payload with old FW 18 sigpatches and it's working fine here.

 

[TomSwitch]

or have to use sys-patch system module and I like the less modules the better for me.

Without knowing much about sys-patch implementation detail I like to ask this question to those who knows, is there really any impact to the memory space since it looks like sys-patch get loaded, do the hack and exit so there should be no extra price to pay as with other methods?

 

[4d1xlaan]

Why is Package3 recommended over booting with the modded version of fusee.bin? I usually do the opposite...

Thanks for all your help!

KISS principle. Fusee is stage 1 loader that does all the system initialization before you can load into the os. Hekate is an alternative stage 1 loader, if you chain load fusee through hekate you're running two bootloader back to back for no reason when hekate is already capable of doing everything fusee does on its own

 

[petspeed]

KISS principle. Fusee is stage 1 loader that does all the system initialization before you can load into the os. Hekate is an alternative stage 1 loader, if you chain load fusee through hekate you're running two bootloader back to back for no reason when hekate is already capable of doing everything fusee does on its own

You could just run fusee directly without Hekate. That's what I do

 

[4d1xlaan]

You could just run fusee directly without Hekate. That's what I do

Yeah, you can. but since hekate has a lot of other useful functionality, people usually already have it and already boot to it anyway, and then it becomes a case of "do I put fss0 in my config or chain load fusee" and I have a hard time finding a use case for chain loading fusee from hekate

By that same principle if you dont need hekate functionality, then fusee is the better choice because it only does the bare minimum necessary

 

[TomSwitch]

Yeah, you can. but since hekate has a lot of other useful functionality, people usually already have it and already boot to it anyway, and then it becomes a case of "do I put fss0 in my config or chain load fusee" and I have a hard time finding a use case for chain loading fusee from hekate

By that same principle if you dont need hekate functionality, then fusee is the better choice because it only does the bare minimum necessary

using fusee has one less dependency, you can use hekate 5.5 for example and never need to update and that is what I have been using since 5.5 and is still 5.5 now for me and I don't have to update it. Not that I am those super early adopter that can't wait for hekate to get updated to support what ever is new from Nintendo, I just like less effort.

 

[4d1xlaan]

One more thing too is that you know fusee is going to work, while it's not necessarily guaranteed that hekate will always set things up correctly. It's one extra point of failure and you wont get support from atmosphere for issues caused by hekate

 

[impeeza]

@impeeza any reason why not just have sys-patch alone? I am using your sys-patch-1.5.1_Updated-PR.zip should I change to your newer release?

As I had told before they both are complementary use the one you like it both

Post automatically merged: Jun 14, 2024

Snakes says to use Hekate FSSO, fishes say to use Fusee so yeah... Hekate is also faster to boot but I don't see much difference at least not using autoboot...

I like using fusee cause for some reason with Hekate FSS0 I can't play games above my FW while with with fusee I'm on FW 17.0.1 and can play FW18 games without needing to update.

But now that fusee doesnt support sigpatches, it's likely that a lot of people might prefer to use FSS0 with hekate sigpatches or have to use modded fusee payload or have to use sys-patch system module and I like the less modules the better for me.

I'm using modded fusee payload with old FW 18 sigpatches and it's working fine here.

Because you need to build a modified fusee.Bin version

 

[kenshinsano]

Hello, since the update of Switch and Atmosphere, my hbmenu.nsp (on main screen EmuMMC) dosent work
Sigpatches updtaed too
Trieds to reinstall the nsp but same probleme
Do you know maybe please how to fix it ?

 

[Redverd]

Help please.
I can't start the game SMTV: Vengeance

My switch says:
"Unable to start software. Return to the HOME Menu and try again."

From my search I assume the problem to be sigpatches, so I download the latest I could find but it didn't work

My switch is on fw 18.0.0 and AMS 1.7.1

​

 

[impeeza]

install sys-patch sysmodule

https://gbatemp.net/download/sys-patch-1-5-2-binary-fw-18-1-0-atmosphere-1-7-1.38686/

 

[Redverd]

install sys-patch sysmodule

https://gbatemp.net/download/sys-patch-1-5-2-binary-fw-18-1-0-atmosphere-1-7-1.38686/

Thanks. It works.
Install, restart and open.
Does this mean in the future, every time fw and AMS is updated sys-patch update is needed too?

 

[impeeza]

Thanks. It works.
Install, restart and open.
Does this mean in the future, every time fw and AMS is updated sys-patch update is needed too?

We hope no need to upgrade SYS-Patch. is designated to search the patterns on the memory and patch them on the fly.

 

[petspeed]

Thanks. It works.
Install, restart and open.
Does this mean in the future, every time fw and AMS is updated sys-patch update is needed too?

No often it will still work without an update