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

[impeeza]

Does it replace sigpatches or is it used along side them?

SYS-Patches is a complementary to sigpatches, if one fails the other is there to the rescue.

 

[josete2k]

https://github.com/Atmosphere-NX/Atmosphere/commit/46a43578829163cd08b9ddcaaacc6febd1e71e0e

Hmmm...

 

[linuxares]

https://github.com/Atmosphere-NX/Atmosphere/commit/46a43578829163cd08b9ddcaaacc6febd1e71e0e

Hmmm...

https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10289904

 

[ShadowOne333]

That just flew by to me.
What does this mean for IPS sigpatches?
Are they simply ditching patch loading because muh loading time is 1 sec slower?

 

[ghjfdtg]

I won't affect hekate and/or sys-patch users.

 

[linuxares]

That just flew by to me.
What does this mean for IPS sigpatches?
Are they simply ditching patch loading because muh loading time is 1 sec slower?

No clue, but it means either use Hekate and load package3 so Hekate insert the patches. Or use Sys-patch, https://github.com/ITotalJustice/sys-patch

 

[duckbill007]

Are they simply ditching patch loading because muh loading time is 1 sec slower?

Yes

 

[impeeza]

That just flew by to me.
What does this mean for IPS sigpatches?
Are they simply ditching patch loading because muh loading time is 1 sec slower?

Less that 1 second for me

 

[Hassal]

Yes

Not really he would have done the same.

 

[impeeza]

Firmware 17.0.x reboot-less update is on the air, the sigpatches are the same, so no update of the package is needed.

 

[Blythe93]

Firmware 17.0.x reboot-less update is on the air, the sigpatches are the same, so no update of the package is needed.

I'm curious, other than obvious what's the difference between regular and rebootless update as far as firmware files are concerned?

 

[Ethelbert]

Rebootless updates are just some whatevers like updating the list of filtered swear words and such.

 

[impeeza]

I'm curious, other than obvious what's the difference between regular and rebootless update as far as firmware files are concerned?

Normally small changes not related with functional code, restricted words, aesthetic changes and so on. as no executing code is changed you don't need to reboot the console to apply.

 

[Lavaimp]

curiously, do the current sigpatches allow me to dump games like splatoon 3? I wanted to do a text edit, but i get an error about unable to find keys when trying to dump the game. I own it legitimately.

 

[crazypete]

Hello I updated and I added everything that is usually added for the update but now I have this error. Has anyone gotten this before???

 

[Stidwack]

Hello I updated and I added everything that is usually added for the update but now I have this error. Has anyone gotten this before???

on your SD card, delete "atmosphere\contents\0100000000001000". If you updated with a custom theme then that's the problem

 

[crazypete]

on your SD card, delete "atmosphere\contents\0100000000001000". If you updated with a custom theme then that's the problem

That did it!!! your awesome!!! thank you!!!!!

 

[impeeza]

That did it!!! your awesome!!! thank you!!!!!

before update you FW is better you remove your themes, that is that folder for.

 

[cmdwedge]

I apologise for the stupid questions!

So I have updated my Switch to 17.0.0 on the EmuMMC, updated Hekate, Atmosphere 1.6.2, fusee.bin etc. The Switch crashes with the error code for a blanked prodkey. I have backups of my prodkeys for both SysMMC and EmuMMC. If I boot my Switch into SysMMC, it's on an old firmware and the serial number shown in the settings is correct for the console, ie: I never blanked the SysMMC one.

However, booting my Switch into EmuMMC crashes. I have the backups of absolutely everything, including the prodkey bin files from Incognito_RCM. I understand to get my EmuMMC working again, I'll need to restore the prodkey to EmuMMC via Incognito_RCM. The problem I think is that there isn't a version (yet) that supports 17.0.0.

This repository supports 16.0 - https://github.com/mistervampi/Incognito_RCM - using this, I get 'unknown pkg1 version' when it's attempting to retrieve biskeys.

Are my options to wait for an Incognito_RCM to support 17.0, or to simply delete my EmuMMC and start over, with no blanked serial number? I have a lot of data inside the EmuMMC so it would be a pain to lose it all.

Thanks!

 

[urherenow]

But let's pretend no of fuses are burnt (or whatever the minimal amount is), should the entry look like this? kip1patch=nosigchk,nogc

If you've ever turned your machine on in OFW, before ever using CFW, while on a firmware higher than 4.1, then the nogc option is pointless, and in fact causes some people problems when booting with game cart inserted. Only people who are still convinced that a cold-boot CFW will come for 4.1 or lower, are worried about it. With that said, kip1patch=nogc is intended to be used when booting with stock=1 (for those concerned about this). Otherwise, it should be up in your global config in the form of

[config]
autonogc=1

There is a pretty detailed explanation of every one of these things on the front page of the repo. Not knowing this, is why I despise AIO packs.