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

[LloydChristmas1]

how do i recreate your error?

Run a game and then press the power button once, screen turns off, press power button again and nothing happens. Have to then hold power button for 12 seconds to turn the switch off and reboot

 

[Mars04]

As a noob got everything to work (games start and tinfoil works) thanks guys, only problem is when a game is running, if i lock the switch the screen wont turn back on when pressing the power button, i have to turn it off and reboot with fusee

Wasn't this issue mentioned in release files of atmosphere? I think so and it wasn't an atmosphere issue but with the outdated sysmodules or so.

 

[LloydChristmas1]

Wasn't this issue mentioned in release files of atmosphere? I think so and it wasn't an atmosphere issue but with the outdated sysmodules or so.

Yeah i have just read over them and seems to be an issue when using sys-clk, which i do have.

 

[josete2k]

Yeah i have just read over them and seems to be an issue when using sys-clk, which i do have.

Sys-clk has a fix

https://github.com/retronx-team/sys-clk/issues/85

Post automatically merged: Oct 13, 2024

the pre pre release 19.0 + new hekate + syspatch seems to be fine for me so far. thanks to all the contributors.

What version of sys-patch??

 

[LloydChristmas1]

Sys-clk has a fix

https://github.com/retronx-team/sys-clk/issues/85

This works, thank you.

 

[nitrozz]

perfect. thanks

 

[laz305]

18.1 sigpatches work on 19.0?

 

[josete2k]

Nope

Post automatically merged: Oct 13, 2024

Modded fusee.bin - FS/ES/NFIM/Loader IPS patches.

NOTE: These will only run NSP/XCI - NRO forwarders are not working, these will need recompiled with new software to work. So will some homebrew.

This is ONLY for FW19 and the pre release - atmosphere-1.8.0-preprerelease-5717ea6c0, Once Atmosphere gets updated you will need to update the loader patch. Also these patches might be subject to change so only download if you really need to test FW 19, I recommend you stay on 18.1.0 for now.

Post automatically merged: Oct 13, 2024

EDIT:
Finaly I got NRO forwarders to work. You need to update hacbrewpack - I changed 2 files, although I probably only needed to edit 1. In HBMenu.json you need to change this:

"type": "debug_flags",
            "value": {
                "allow_debug": false,
                "force_debug_prod": false,
                "force_debug": true
            }

Also I added this key to extkeys.c - but I probably didn't need to:

else if (strcmp(key, "xci_t1_titlekey_kek_00") == 0)
            {
                matched_key = 1;
            }

When I rebuilt the NRO forwarders it worked, So that means that the patches are good :-)...

I've built my own hacbrewpack and same results... spinning in grey...

:'(


EDIT: working if I install it launching system with fusee, not with fss0 (I forgot the kip1patch=nosigchk add hehehe)

EDIT2: It always ask for a user and it autoreloads if I exit from app with the key designed for, but works.

EDIT3: added forwarders

Post automatically merged: Oct 13, 2024

you need new tool and set flag. npdmtool.exe has a pull request for the needed change. Or you can wait for @impeeza who is coming back soon.
"allow_debug": false,
"force_debug_prod": false, <= add this line
"force_debug": true

Done.

Compiled AMS working.

Thanks

 

[svoc]

Could you make a forwarder for 19 for this one please I don't have a windows PC

 

[miniminx]

Updated Sys-Patch.

Modded to work on FW19, I changed a couple of patches -ES patch is new for FW18 + 19. Added new FS patches for FW19. Other patches remain the same.

For Noobs (like me), this will save you needing to use a modded fusee.bin or patches.ini.

NOTE:
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?

 

[svoc]

Used the new sys patches it says failed to apply nosigpatch press power to continue so I do and it works perfectly any way to get rid of that message on boot so I don't have to get up to press power button

 

[miniminx]

Could you make a forwarder for 19 for this one please I don't have a windows PC

NRO path: /switch/off_switch.nro

 

[svoc]

NRO path: /switch/off_switch.nro

Thank you

 

[miniminx]

Used the new sys patches it says failed to apply nosigpatch press power to continue so I do and it works perfectly any way to get rid of that message on boot so I don't have to get up to press power button

I've no idea on what you are talking about, everything is working fine on my end.

 

[svoc]

I had to reinstall it all with out patches.ini and the other files from earlier and it is now working

 

[TomSwitch]

Updated Sys-Patch.

Modded to work on FW19, I changed a couple of patches -ES patch is new for FW18 + 19. Added new FS patches for FW19. Other patches remain the same.

For Noobs (like me), this will save you needing to use a modded fusee.bin or patches.ini.

NOTE:
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?

What did you change in sys-patch?
Seems to me only the flag and this change is needed, don't know why the upper limit was there in the first place
{ "es6", "0x.6300...0094A0..D1..FF97", 16, 0, mov2_cond, mov0_patch, mov0_applied, true, MAKEHOSVERSION(14,0,0), MAKEHOSVERSION(17,0,1) },
to
{ "es6", "0x.6300...0094A0..D1..FF97", 16, 0, mov2_cond, mov0_patch, mov0_applied, true, MAKEHOSVERSION(14,0,0)},

 

[miniminx]

I had to reinstall it all with out patches.ini and the other files from earlier and it is now working

No worries, also I reuploaded the nro forwarder with an Icon I just made in photoshop.

 

[svoc]

No worries, also I reuploaded the nro forwarder with an Icon I just made in photoshop.

Thanks I like the logo on the nsp

 

[duckbill007]

@miniminx, I have a 2 questions about this:
.nosigchk=0:0x074524:0x4:C0030054,10000014
1) Why 10000014, and not 07000014?
2) Why only case 8 and not others? Why it so special?

Patch works even without this. Also, on older fw this was not needed.

Post automatically merged: Oct 14, 2024

I think you made mistake: jump should be to 0x7459c, not to 0x74564, so it should be 1E000014

 

[miniminx]

@miniminx, I have a 2 questions about this:
.nosigchk=0:0x074524:0x4:C0030054,10000014
1) Why 10000014, and not 07000014?
2) Why only case 8 and not others? Why it so special?

Patch works even without this. Also, on older fw this was not needed.

This new patch was written by BorntoHonk, here's a quote from him to why it was added:

Ensures we hit that TBNZ condition with a zero NOP'ing the chain and do not go down to the 0x200 test.

At the end of the day, the patches do seem to work without it being added, it's been put in as a preemptive measure to make sure that when that function is called we always get the desired result.

It's subject to change, but for now it's being used for FW 19+