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

Mars04

Active Member
Newcomer
Joined
Apr 22, 2024
Messages
25
Trophies
0
XP
105
Country
South Africa
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.
 
  • Like
Reactions: BigOnYa

josete2k

Well-Known Member
Member
Joined
Apr 24, 2009
Messages
860
Trophies
1
Age
44
Location
Spain
XP
2,062
Country
Spain

josete2k

Well-Known Member
Member
Joined
Apr 24, 2009
Messages
860
Trophies
1
Age
44
Location
Spain
XP
2,062
Country
Spain
Nope
Post automatically merged:

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:


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:

Code:
"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:
Code:
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:

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
 

Attachments

  • hacbrewpack.zip
    178.5 KB · Views: 3
  • HBMenu-0197bb45716e0000.zip
    353.2 KB · Views: 7
  • chiaki-01b603927cb89000.zip
    350.5 KB · Views: 8
Last edited by josete2k,

svoc

Active Member
Newcomer
Joined
Oct 12, 2024
Messages
40
Trophies
0
Age
29
XP
37
Country
United States
Could you make a forwarder for 19 for this one please I don't have a windows PC
 

Attachments

  • off_switch.nro.zip
    113.3 KB · Views: 6

miniminx

Well-Known Member
Member
Joined
Jun 27, 2024
Messages
236
Trophies
0
Age
25
XP
492
Country
United States
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?
 

Attachments

  • Sys-Patch(fw19).zip
    171.5 KB · Views: 5

svoc

Active Member
Newcomer
Joined
Oct 12, 2024
Messages
40
Trophies
0
Age
29
XP
37
Country
United States
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

Well-Known Member
Member
Joined
Jun 27, 2024
Messages
236
Trophies
0
Age
25
XP
492
Country
United States
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.
2024101405452400-57B4628D2267231D57E0FC1078C0596D.jpg
 
  • Like
Reactions: nitrozz

svoc

Active Member
Newcomer
Joined
Oct 12, 2024
Messages
40
Trophies
0
Age
29
XP
37
Country
United States
I had to reinstall it all with out patches.ini and the other files from earlier and it is now working
 

TomSwitch

Well-Known Member
Member
GBAtemp Patron
Joined
Jan 10, 2019
Messages
5,255
Trophies
3
Age
44
XP
17,134
Country
United States
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)},
 

duckbill007

Well-Known Member
Member
Joined
May 5, 2011
Messages
845
Trophies
1
XP
3,014
Country
Russia
@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:

I think you made mistake: jump should be to 0x7459c, not to 0x74564, so it should be 1E000014
 
Last edited by duckbill007,
  • Wow
Reactions: impeeza

miniminx

Well-Known Member
Member
Joined
Jun 27, 2024
Messages
236
Trophies
0
Age
25
XP
492
Country
United States
@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:

Code:
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+
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • realtimesave @ realtimesave:
    I used to play 007 and cod4 a lot
  • realtimesave @ realtimesave:
    and test drive unlimited
  • BigOnYa @ BigOnYa:
    Pretty much all the games that come out buggy get patched soon after anyways. Not to many that I've noticed are game breaking bugs. Of course I mostly only game on Xbox seriesx.
  • kijetesantakalu042 @ kijetesantakalu042:
    @BigOnYa It's still unacceptable
  • realtimesave @ realtimesave:
    I wonder if anyone actually uses a PS5 these days
  • BigOnYa @ BigOnYa:
    Game updates are a norm today, deal with it. They only make games better. GTAV gets weekly updates still today.
  • realtimesave @ realtimesave:
    mine just sits
  • kijetesantakalu042 @ kijetesantakalu042:
    @BigOnYa Game updates are a good thing. But shouldn
  • kijetesantakalu042 @ kijetesantakalu042:
    be a crutch for releasing a working game
  • BigOnYa @ BigOnYa:
    I have not played a game in years that had a game breaking bug on launch, so I wouldn't say a crutch.
  • kijetesantakalu042 @ kijetesantakalu042:
    Scarlet and voilet
  • BigOnYa @ BigOnYa:
    Maybe different on PC, who knows, since I'm in the Xbox ecosystem.
  • kijetesantakalu042 @ kijetesantakalu042:
    Fallout 76
  • kijetesantakalu042 @ kijetesantakalu042:
    No mans sky
  • BigOnYa @ BigOnYa:
    Yep, been playing fallout76 for years, since launch, I never had any game breaking bugs, or corrupted saves. Don't play No Mans Sky, its boring.
  • kijetesantakalu042 @ kijetesantakalu042:
    At launch there were some issues
  • BigOnYa @ BigOnYa:
    Issues? All games have issues, but not game breaking.
  • BigOnYa @ BigOnYa:
    Again don't play on PC, nor would play that. And who knows, some those "issues" could just be your PC.
  • realtimesave @ realtimesave:
    usually issues are a shitty PC
    +1
  • realtimesave @ realtimesave:
    I haven't had a crappy pc in years and when I did, I promptly got rid of it
  • kijetesantakalu042 @ kijetesantakalu042:
    KSP 2 did suck and the entire staff team got laid off
  • BigOnYa @ BigOnYa:
    When I used to game on PC, I'd pirate PC games all the time, and some yes would crash often, maybe they were bad rips or something. I've had my SeriesX for over 2 years now and never have had a game crash yet, or any game breaking bugs. I have seen weird bugs like NPC walking thru floors or walls, but not often.
    BigOnYa @ BigOnYa: When I used to game on PC, I'd pirate PC games all the time, and some yes would crash often...