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

[impeeza]

I think you missed som patches in patches.ini

#FS 19.0.0-fat32
[FS:D94C6815F8F50A20]
.nosigchk=0:0x021478:0x4:60090036,1F2003D5
.nosigchk=0:0x0745A0:0x4:89740394,E0031F2A
.nosigchk=0:0x074524:0x4:C0030054,10000014

#FS 19.0.0-exfat
[FS:EDA87868A4490750]
.nosigchk=0:0x021478:0x4:60090036,1F2003D5
.nosigchk=0:0x0745A0:0x4:95A20394,E0031F2A
.nosigchk=0:0x074524:0x4:C0030054,10000014

#loader Atmosphere-1.8.0 pre
[Loader:D3FD950603AECC4D]
.nosigchk=0:0x602A:0x1:01,00

YES, YOU ARE RIGHT I LEAVE THE V1 FW19 PATCHES ON PATCHES.INI

CORRECTING NOW.

Thanks a lot buddy.

Post automatically merged: Oct 15, 2024

I think that's the opposite. If Version Skip is disabled, the sysmodule will try to search all patterns, not only the present CFW

ha ha ha, yes you are right.

 

[Nephiel]

Just noticed that 9 of the .ips files in kip_patches/loader_patches have lowercase names, the rest are all uppercase.
I guess it doesn't really matter with FAT32, but... shouldn't they be all uppercase?

 

[impeeza]

Just noticed that 9 of the .ips files in kip_patches/loader_patches have lowercase names, the rest are all uppercase.
I guess it doesn't really matter with FAT32, but... shouldn't they be all uppercase?

The case do not matters.

 

[justinkb]

#FS 19.0.0-fat32
[FS:D94C6815F8F50A20]
.nosigchk=0:0x021478:0x4:60090036,1F2003D5
.nosigchk=0:0x0745A0:0x4:89740394,E0031F2A
.nosigchk=0:0x074524:0x4:C0030054,10000014

#FS 19.0.0-exfat
[FS:EDA87868A4490750]
.nosigchk=0:0x021478:0x4:60090036,1F2003D5
.nosigchk=0:0x0745A0:0x4:95A20394,E0031F2A
.nosigchk=0:0x074524:0x4:C0030054,10000014

Those FS patches are definitely right, I came to the exact same patches.ini entries and everything working fine here on 19.0.0. (I don't use loader patches, I just build Atmosphere myself with the relevant changes that avoid the need to patch it)

 

[Quincy]

The case do not matters.

It is, however, good practice to pick a naming scheme and sticking with it (i.e. ALL uppercase, none uppercase or every case random(why? :'( ) ) though. Keeps your filetree looking tidy and avoids confusion for the end-user (the very same confusion you were answering ).

But that's for the developers to decide and update

Sorry for the programmer inside me being programming-P.C. (no pun intended)

 

[mathew77]

Hi dear all!
Please, need new sigpatches for a new build of the atmosphere-1.8.0-prerelease-c6014b533: https://github.com/Atmosphere-NX/Atmosphere/releases

Thanks in advance. ^___^

 

[w350922439]

Hi dear all!
Please, need new sigpatches for a new build of the atmosphere-1.8.0-prerelease-c6014b533: https://github.com/Atmosphere-NX/Atmosphere/releases

Thanks in advance. ^___^

add loader to patches.ini, its same as 1.8.0 test version.
#Loader Atmosphere-1.8.0 pre
[Loader:A73B75768096EA90]
.nosigchk=0:0x602A:0x1:01,00

 

[svoc]

add loader to patches.ini, its same as 1.8.0 test version.
#Loader Atmosphere-1.8.0 pre
[Loader:A73B75768096EA90]
.nosigchk=0:0x602A:0x1:01,00

https://gbatemp.net/attachments/hekate-ams-package3-sigpatches-1-7-1-cfw-19-0-0-zip.463520/

Would this not work it is the same build as the previous test version that he put out a few days ago just published to the release page vs a issue is my understanding

 

[OLineGuy]

The reason Tinfoil is not working for some is because Tinfoil creates an nro forwarder to run it from your main menu. You can probably run Tinfoil by launching another app while pressing the right trigger to launch the hbmenu (so you don't enter applet mode), then you should be able to run Tinfoil from the hbmenu.

To fix tinfoil, just make a new NRO Forwarder for it - or use this one.
NRO path: /switch/tinfoil/tinfoil.nro

thanks, the forwarder now works on 19 but when u back out with B to exit, it just restarts the app so you need to press home to quit.

 

[shadow256]

Can you check whether some are not needed? I disabled some and seems nothing breaks. What does nocntchk do?
[fs]
noacidsigchk1=Skipped
noacidsigchk2=Skipped
noncasigchk_old=Skipped
noncasigchk_new=Skipped
noncasigchk_new2=Patched (sys-patch)
nocntchk_old=Skipped
nocntchk_new=Unpatched
nocntchk_FW19_1=Disabled
nocntchk_FW19_2=Disabled
[ldr]
noacidsigchk=Patched (sys-patch)
debug_flag=Patched (sys-patch)
[erpt]
no_erpt=Patched (sys-patch)
[es]
es1=Skipped
es2=Skipped
es3=Skipped
es4=Skipped
es5=Skipped
es6=Skipped
es6a=Patched (sys-patch)
es7=Skipped
es7_FW18-19=Disabled
[nifm]
ctest=Patched (sys-patch)

Do yyou have the code for "no_erpt" and "debug_flag" patches for Sys-patch, theses could be interesting?

 

[nitrozz]

why i get es7_FW18-19 unpatched

 

[Blythe93]

why i get es7_FW18-19 unpatched

If you have IPS/Patches.ini installed and use this at the same time - on FW19 - nocntchk_FW19_1 will say it's unpatched,even though it is. I couldn't find in the code how to fix this as it works OK and shows patched if not using ips/patches.ini to patch that address?

Sourced from here, might be related to ES patches as well?

 

[TomSwitch]

Do yyou have the code for "no_erpt" and "debug_flag" patches for Sys-patch, theses could be interesting?

Erpt can fill up when you avoid nintendo server. Debug flag is mostly useless cause you can always recompile with the flag set correctly. It's a pity two version would be needed for 1.7 and 1.8

constexpr PatchData erpt_patch_data{ "0xE0031F2AC0035FD6" };
{ "no_erpt", "0xFD7B02A9FD830091F76305A9", -4, 0, no_cond, erpt_patch, erpt_applied, true },

 

[burhansalih]

Hi All,

Just want a bit of advice really I have been using the following Hekate config below for a while and its never given me any agro just wanted to know if it was good and should I be using it...someone did mention I should add the following for warm boot fix but I have never had any errors with warm boot.

[Warmboot Error Fix]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

And below is my current configuration.

[config]
autoboot=0
autoboot_list=0
bootwait=1
backlight=84
noticker=0
autohosoff=1
autonogc=0
updater2p=1
bootprotect=0

{--- Custom Firmware ---}
[CFW (SYSNAND)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummc_force_disable=1
icon=bootloader/res/icon_atmosphere.bmp
{}

[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/icon_hekate-atmosphere.bmp
{}

{-------- Stock ---------}
[Stock SYS]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_stock.bmp

 

[Bigdrago]

For those that insist on using Tinfoil: at least stay away from the "self installer". If you must, keep to the NRO "Applet version" and use title override instead.

Why is that?

 

[LuigiGad]

The reason Tinfoil is not working for some is because Tinfoil creates an nro forwarder to run it from your main menu. You can probably run Tinfoil by launching another app while pressing the right trigger to launch the hbmenu (so you don't enter applet mode), then you should be able to run Tinfoil from the hbmenu.

To fix tinfoil, just make a new NRO Forwarder for it - or use this one.
NRO path: /switch/tinfoil/tinfoil.nro

Thanks so much for the file, this works. Now the question is why what I created online was not good? What tools should I use to create forwarders? I have to create one for PFBNEO.

 

[josete2k]

Thanks so much for the file, this works. Now the question is why what I created online was not good? What tools should I use to create forwarders? I have to create one for PFBNEO.

https://gbatemp.net/threads/gui-for-nsp-forwarder-tool-for-12.588018/post-10516248

 

[PotionMaster21]

add loader to patches.ini, its same as 1.8.0 test version.
#Loader Atmosphere-1.8.0 pre
[Loader:A73B75768096EA90]
.nosigchk=0:0x602A:0x1:01,00

i did this but software still doesn't seem to launch, unless that's being caused by another issue then apologies.

 

[alcab]

Sorry for asking, if this is not allowed please let me know. But it is possible to get a patched fusee.bin so that it is compatible with sigpatches? Do I have to compile the file by myself? How?

Thanks in advance for your help.

 

[OrGoN3]

add loader to patches.ini, its same as 1.8.0 test version.
#Loader Atmosphere-1.8.0 pre
[Loader:A73B75768096EA90]
.nosigchk=0:0x602A:0x1:01,00

Is it that or is it

#loader Atmosphere-1.8.0-prerelease [Loader3FD950603AECC4D] .nosigchk=0:0x602A:0x1:01,00

This was the one for the preprerelease, or maybe it was the first preprerelease. Anybody know?

Post automatically merged: Oct 16, 2024

Hi All,

Just want a bit of advice really I have been using the following Hekate config below for a while and its never given me any agro just wanted to know if it was good and should I be using it...someone did mention I should add the following for warm boot fix but I have never had any errors with warm boot.

[Warmboot Error Fix]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

And below is my current configuration.

[config]
autoboot=0
autoboot_list=0
bootwait=1
backlight=84
noticker=0
autohosoff=1
autonogc=0
updater2p=1
bootprotect=0

{--- Custom Firmware ---}
[CFW (SYSNAND)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummc_force_disable=1
icon=bootloader/res/icon_atmosphere.bmp
{}

[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/icon_hekate-atmosphere.bmp
{}

{-------- Stock ---------}
[Stock SYS]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_stock.bmp

No need to add it. It's identical to your stock sys block. Basically, if you ever get the warmboot error, launch stock once (with or without hekate) then reboot to hekate. Fixed.