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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,304,989
  • Replies Replies 7,368
  • Likes Likes 266
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?
Thanks, SYS-TWEAK wasn't working with ips patches and/or patches.ini (FW 18.1.0).

FS patching (translations) weren't working too.

Now with sys-patch all are ok.

Should I remove the ips and patches.ini??? I'll test
 
  • Like
Reactions: impeeza
Thanks, SYS-TWEAK wasn't working with ips patches and/or patches.ini (FW 18.1.0).

FS patching (translations) weren't working too.

Now with sys-patch all are ok.

Should I remove the ips and patches.ini??? I'll test
Probably the patches and patches.ini files you were using are for FW 19. if you are now using sys-patch, you can remove them but it doesn't really matter as your switch will still get patched one way or the other.
 
@miniminx : Do you have modified the ""nocntchk_new"" in your Sys-patch code and if yes what have you modified?
No, I removed that one and made new patterns.

Code:
        //new good patch tested on fw 19
    { "nocntchk_FW19_1", "0xC003005401", 0, 0, bne_cond, ret1_patch, ret1_applied, true, MAKEHOSVERSION(19,0,0) },
    { "nocntchk_FW19_2", "0x1C0012.050071..0054..00.60", -9, 0, bl_cond, ret0_patch, ret0_applied, true, MAKEHOSVERSION(19,0,0) },
    //
    { "noacidsigchk1", "0xC8FE4739", -24, 0, bl_cond, ret0_patch, ret0_applied, true, FW_VER_ANY, MAKEHOSVERSION(9,2,0) },
    { "noacidsigchk2", "0x0210911F000072", -5, 0, bl_cond, ret0_patch, ret0_applied, true, FW_VER_ANY, MAKEHOSVERSION(9,2,0) },
    { "noncasigchk_old", "0x1E42B9", -5, 0, tbz_cond, nop_patch, nop_applied, true, MAKEHOSVERSION(10,0,0), MAKEHOSVERSION(14,2,1) },
    { "noncasigchk_new", "0x3E4479", -5, 0, tbz_cond, nop_patch, nop_applied, true, MAKEHOSVERSION(15,0,0), MAKEHOSVERSION(16,1,0) },
    { "noncasigchk_new2", "0x258052", -5, 0, tbz_cond, nop_patch, nop_applied, true, MAKEHOSVERSION(17,0,0) },
    { "nocntchk", "0x081C00121F050071..0054", -4, 0, bl_cond, ret0_patch, ret0_applied, true, MAKEHOSVERSION(10,0,0), MAKEHOSVERSION(15,0,0) },
};

constinit Patterns ldr_patterns[] = {
    { "noacidsigchk", "0xFD7B.A8C0035FD6", 16, 2, subs_cond, subs_patch, subs_applied, true },
};

constinit Patterns es_patterns[] = {
    { "es1", "0x1F90013128928052", -4, 0, cbz_cond, b_patch, b_applied, true, FW_VER_ANY, MAKEHOSVERSION(13,2,1) },
    { "es2", "0xC07240F9E1930091", -4, 0, tbz_cond, nop_patch, nop_applied, true, FW_VER_ANY, MAKEHOSVERSION(10,2,0) },
    { "es3", "0xF3031FAA02000014", -4, 0, bne_cond, nop_patch, nop_applied, true, FW_VER_ANY, MAKEHOSVERSION(10,2,0) },
    { "es4", "0xC0FDFF35A8C35838", -4, 0, mov_cond, nop_patch, nop_applied, true, MAKEHOSVERSION(11,0,0), MAKEHOSVERSION(13,2,1) },
    { "es5", "0xE023009145EEFF97", -4, 0, cbz_cond, b_patch, b_applied, true, MAKEHOSVERSION(11,0,0), MAKEHOSVERSION(13,2,1) },
    { "es6", "0x.6300...0094A0..D1..FF97", 16, 0, mov2_cond, mov0_patch, mov0_applied, true, MAKEHOSVERSION(14,0,0), MAKEHOSVERSION(17,0,1) },
    //new good patch tested on fw 18-19
    { "es7_FW18-19", "0xFF97..132A...A9........FF.0491C0035FD6", 2, 0, mov2_cond, mov0_patch, mov0_applied, true, MAKEHOSVERSION(18,0,0), MAKEHOSVERSION(19,0,0) },
 
Hello guys, I did the update but I encounter a yellow screen after rebooting after starting emummc or sysnand on hekate, is there something I can cook ?
 
Is it just me or after updating to 18.1 does it stay on the boot logo way longer than usual? Mine just goes from boot logo to black screen, it doesn’t even show the lock screen before going to sleep.
 
No, I removed that one and made new patterns.

Code:
        //new good patch tested on fw 19
    { "nocntchk_FW19_1", "0xC003005401", 0, 0, bne_cond, ret1_patch, ret1_applied, true, MAKEHOSVERSION(19,0,0) },
    { "nocntchk_FW19_2", "0x1C0012.050071..0054..00.60", -9, 0, bl_cond, ret0_patch, ret0_applied, true, MAKEHOSVERSION(19,0,0) },
    //
    { "noacidsigchk1", "0xC8FE4739", -24, 0, bl_cond, ret0_patch, ret0_applied, true, FW_VER_ANY, MAKEHOSVERSION(9,2,0) },
    { "noacidsigchk2", "0x0210911F000072", -5, 0, bl_cond, ret0_patch, ret0_applied, true, FW_VER_ANY, MAKEHOSVERSION(9,2,0) },
    { "noncasigchk_old", "0x1E42B9", -5, 0, tbz_cond, nop_patch, nop_applied, true, MAKEHOSVERSION(10,0,0), MAKEHOSVERSION(14,2,1) },
    { "noncasigchk_new", "0x3E4479", -5, 0, tbz_cond, nop_patch, nop_applied, true, MAKEHOSVERSION(15,0,0), MAKEHOSVERSION(16,1,0) },
    { "noncasigchk_new2", "0x258052", -5, 0, tbz_cond, nop_patch, nop_applied, true, MAKEHOSVERSION(17,0,0) },
    { "nocntchk", "0x081C00121F050071..0054", -4, 0, bl_cond, ret0_patch, ret0_applied, true, MAKEHOSVERSION(10,0,0), MAKEHOSVERSION(15,0,0) },
};

constinit Patterns ldr_patterns[] = {
    { "noacidsigchk", "0xFD7B.A8C0035FD6", 16, 2, subs_cond, subs_patch, subs_applied, true },
};

constinit Patterns es_patterns[] = {
    { "es1", "0x1F90013128928052", -4, 0, cbz_cond, b_patch, b_applied, true, FW_VER_ANY, MAKEHOSVERSION(13,2,1) },
    { "es2", "0xC07240F9E1930091", -4, 0, tbz_cond, nop_patch, nop_applied, true, FW_VER_ANY, MAKEHOSVERSION(10,2,0) },
    { "es3", "0xF3031FAA02000014", -4, 0, bne_cond, nop_patch, nop_applied, true, FW_VER_ANY, MAKEHOSVERSION(10,2,0) },
    { "es4", "0xC0FDFF35A8C35838", -4, 0, mov_cond, nop_patch, nop_applied, true, MAKEHOSVERSION(11,0,0), MAKEHOSVERSION(13,2,1) },
    { "es5", "0xE023009145EEFF97", -4, 0, cbz_cond, b_patch, b_applied, true, MAKEHOSVERSION(11,0,0), MAKEHOSVERSION(13,2,1) },
    { "es6", "0x.6300...0094A0..D1..FF97", 16, 0, mov2_cond, mov0_patch, mov0_applied, true, MAKEHOSVERSION(14,0,0), MAKEHOSVERSION(17,0,1) },
    //new good patch tested on fw 18-19
    { "es7_FW18-19", "0xFF97..132A...A9........FF.0491C0035FD6", 2, 0, mov2_cond, mov0_patch, mov0_applied, true, MAKEHOSVERSION(18,0,0), MAKEHOSVERSION(19,0,0) },
Thanks for all but you've also added "ret1_patch" and "ret1_applied" witch are not in the original code before, what is the code for these or more simpler could you share your "main.cpp" file to see what you have done? I'm not realy good to understand how all this work, sory if I ennoy you with my questions.
 
Thanks for all but you've also added "ret1_patch" and "ret1_applied" witch are not in the original code before, what is the code for these or more simpler could you share your "main.cpp" file to see what you have done? I'm not realy good to understand how all this work, sory if I ennoy you with my questions.
I'm not uploading any code for now as I am still editing some stuff, also the version I am modding is for private use.

Code:
constexpr PatchData ret1_patch_data{ "0x10000014" };

Looking at the original code, it should be fairly obvious what else you need to add.
 
Last edited by miniminx,
I'm not uploading any code for now as I am still editing some stuff, also the version I am modding is for private use.

Code:
constexpr PatchData ret1_patch_data{ "0x10000014" };

Looking at the original code, it should be fairly obvious what else you need to add.
Thanks again, it seems to work.
 
  • Like
Reactions: miniminx
Nope
Post automatically merged:


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:


Done.

Compiled AMS working.

Thanks
Hello there the hacbrewpack.zip have inside a hacbrewpack.exe which only runs on MSYS DO NOT RUN on Windows command line because have MSYS DLLs dependency, do you have the source repo?
 
Hi I successfully updated everything, I've gotten to the point where I can open games and such however when I try to install from Awoo I get an error: failed to open file system with id
error code: 0x001fb402

I tried to install via dbi instead butwhen the download finished I got a blank icon with a spinning circle.

What do I do to fix this?
 
  • Love
Reactions: impeeza
Hi I successfully updated everything, I've gotten to the point where I can open games and such however when I try to install from Awoo I get an error: failed to open file system with id
error code: 0x001fb402

I tried to install via dbi instead butwhen the download finished I got a blank icon with a spinning circle.

What do I do to fix this?
Try using TinWoo Installer instead.
 
  • Love
  • Like
Reactions: BigOnYa and impeeza

Site & Scene News

Popular threads in this forum