What are these sigpatches for ?

I have everything working perfectly with and without these so just wondering what they do ...
I am running Atmosphere 0.17.1 without exosphere, Hekate CTCaer mod v5.5.2, fusee-secondary.bin with emuNAND.

The following patches are not found in ITotalJustice release:
0f3850b7ce489f6a8faee9ad301013f66c74e7c8f8d1b7038ab7fe8ba9d5ac24.ips
4D9C6D6993BF5BF058843BE072C9819598865C79BF87674C63B6D248FA7A0BA4.ips

I also have these alternate patches, which are smaller than in ITotalJustice release:
29CA1C792CF3AB6357929DF0627170FF8EA1CC057DBE2E5C58ADD8A442BD0CA8.ips (26 bytes)
57F03DC120EE515C58482959AB4F76F2B5E56467A377D9576A8BDBE22E3CA2EA.ips (24 bytes)
987521753F9B8CE98718E3C70FFEA1FDDFF58511A482F5387DE25FAD822C27C0.ips (26 bytes)

Anyone know especially the first two extra patches, what they would be for ?

Also, is there an advantage to running emuNAND if I'm entirely offline anyways?
I'm assuming firmware updates can be installed using daybreak ?

 

The 3 that have different sizes, not sure where I found them, they're not in ITotalJustice or eXhumer repos.

The 2 extra ones, are both in loader_patches as well, but the 0F38 is also contained in eXhumer repo:
github: eXhumer/patches/releases

I don't know where I got the 4D9C one, but when I search I see them mentioned here:
gbatemp: /threads/sigpatches-for-atmosphere-fusee-primary-only.567542/page-17

Sorry can't post URL's yet as I'm new

— Posts automatically merged - Please don't double post! —

loader_patches are not needed anyways for fss0 I think?
So when I boot hekate -> fss0 -> atmosphere I shouldn't even need them ...


EDIT... I found the source of the smaller patches as well as the EXTRA ones :

gbatemp: /threads/sigpatches-for-atmosphere-hekate-fss0-fusee-secondary-only.571543/
I wonder if the smaller sized ones are better / worse ...

 

Makes sense, I removed fs_patches and loader_patches completely and everything seems to work

I have a weird issue booting Hekate, fss0 to atmosphere, where after the Nintendo logo the screen goes black
and stays black, until I hold the power button. Then I will boot again in the same way and it boots fine ...
After it's working, I'll hold the power button then Power Off, and the next boot Hekate, fss0 to atmosphere
will make it hang after Nintendo logo, but repeat the process and it boots just fine ...

It's really weird!

 

I might have to try that, is there any advantages to running emuNAND
if I'm not even connecting the switch to the internet at all ? Just wondering

 

If you're in Airplane mode, how did you upgrade to new firmware, with ChoiDujourNX ?
I would imagine then on reboot you blew fuses, however I guess that doesn't matter as long as everything works

But if you already have a NAND backup and run on sysNAND, I suppose every time you upgrade firmware
you'd have to create a new NAND backup but other than that I don't suppose there would be any downsides?

I wonder if there's any other advantages to emuNAND ...

 

Yeah I did a similar thing, however when I backed up my NAND even RAR'd it came to basically 30 gigs,
meaning my NAND was full of junk, and that was even after resetting the switch ... So after using atmos
for a while I restored my NAND but not before I edited the NAND backup and cleared the USER partition,
and then did another factory reset and backed it up again, now it's about 2.5 gigs RAR'd ...

I bet there's a better way of making a clean NAND backup but this was the best I could do

 

Exactly, however the rawnand.bin will be 29 gigs before you compress with RAR, unless you don't get a valid backup ...
Now mine would not compress at all, so I had to mount and edit it, and clear out the USER partition on the backup,
then I re-flashed it back to the switch, and then did a factory reset, which at this point I should be fine as after
restoring I didn't run CFW on it, and after that I finally did my 2nd backup that would compress ...

 

Glad you found the 30GB one, that's the one that matters

But if you were to compress it with RAR you might find it would be much smaller,
but mine would not compress and I found out the switch never erases stuff from NAND
and just changes the partition table to say the files are not there, but after a backup since
it's raw there's encrypted old data there instead of 00's, so erasing USER partition on the
raw nand backup itself fixes that

 

Haha, yeah, that alone would seem suspicious to them, but they can't ban on suspicion

I suppose you don't have to make an EmuNAND, as long as you backup your saved games,
afterwards you can try restoring and checking to make sure it's not banned and then go back,
to either EmuNAND or SysNAND again ...

 

Mine is mostly on or sleeping so I rarely have to payload it to hekate, only when loading new games on SD,
however it's just a weird issue that it seems every 2nd boot fails after the nintendo logo, sort of annoying