Toggle sidebar

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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,191,811
  • Replies Replies 7,280
  • Likes Likes 266
fangamer said:
why i updated,the switch shows black screen
sys 22.1 use sys-patch now
Click to expand...
there is no way for me to know why your console shows a black screen.

update atmosphere, update hekate, update whichever payload you are booting with, remove custom theme, undo nogc patches, exit cartridge from slot of console, etc, etc. not enough information to work with
 
  • Like
Reactions: Blythe93
bth said:
there is no way for me to know why your console shows a black screen.

update atmosphere, update hekate, update whichever payload you are booting with, remove custom theme, undo nogc patches, exit cartridge from slot of console, etc, etc. not enough information to work with
Click to expand...
i have updated atmosphere, emu system version and Hekate to the last.the i copy the sys-patch to my sd card .
During the process, I encountered the error "Failed to apply ‘nosigchk’", but after deleting `kip1patch=nosigchk`, the error message disappeared. Finally, after entering the EMU system, the screen remained black.
and this is my hekate_ipl.ini setting
Code: 
[config]
autoboot=0
autoboot_list=0
bootwait=0
autohosoff=0
autonogc=1
updater2p=1
backlight=100

[CFW - sysMMC]
fss0=atmosphere/package3
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp

[CFW - emuMMC]
fss0=atmosphere/package3
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp

[Stock - sysMMC]
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_switch.bmp
 
fangamer said:
i have updated atmosphere, emu system version and Hekate to the last.the i copy the sys-patch to my sd card .
During the process, I encountered the error "Failed to apply ‘nosigchk’", but after deleting `kip1patch=nosigchk`, the error message disappeared. Finally, after entering the EMU system, the screen remained black.
Click to expand...
nosighchk lines have nothing to do with sys-patch, and this thread also isn't related to sys-patch. sys-patch thread that way -> https://gbatemp.net/threads/sys-patch-sysmod-that-patches-on-boot.633517
sys-patch doesn't make the screen go black, most probably other sysmodules inside of /atmosphere/contents/

delete anything not 420000000000000B
 
bth said:
nosighchk lines have nothing to do with sys-patch, and this thread also isn't related to sys-patch. sys-patch thread that way -> https://gbatemp.net/threads/sys-patch-sysmod-that-patches-on-boot.633517
sys-patch doesn't make the screen go black, most probably other sysmodules inside of /atmosphere/contents/

delete anything not 420000000000000B
Click to expand...
bth said:
nosighchk lines have nothing to do with sys-patch, and this thread also isn't related to sys-patch. sys-patch thread that way -> https://gbatemp.net/threads/sys-patch-sysmod-that-patches-on-boot.633517
sys-patch doesn't make the screen go black, most probably other sysmodules inside of /atmosphere/contents/

delete anything not 420000000000000B
Click to expand...
still shows black screen no switch logo. only in the EMU system
 
bth said:
not problem of sys-patch, provide /config/sys-patch/log.ini
Click to expand...
Code: 
[fs]
noacidsigchk1=Unpatched
noacidsigchk2=Unpatched
noncasigchk_old=Unpatched
noncasigchk_new=Unpatched
nocntchk_old=Unpatched
nocntchk_new=Unpatched
 
fangamer said:
Code: 
[fs]
noacidsigchk1=Unpatched
noacidsigchk2=Unpatched
noncasigchk_old=Unpatched
noncasigchk_new=Unpatched
nocntchk_old=Unpatched
nocntchk_new=Unpatched
Click to expand...
you do not have sys-patch that is up to date.

https://github.com/impeeza/sys-patch/blob/master/sysmod/src/main.cpp#L247-L253

the names are not like that.

i ignore your problem now.

Code: 
    { "noacidsigchk_1.0.0-9.2.0", "0xC8FE4739", -24, 0, bl_cond, ret0_patch, ret0_applied, true, FW_VER_ANY, MAKEHOSVERSION(9,2,0) }, // moved to loader 10.0.0
    { "noacidsigchk_1.0.0-9.2.0", "0x0210911F000072", -5, 0, bl_cond, ret0_patch, ret0_applied, true, FW_VER_ANY, MAKEHOSVERSION(9,2,0) }, // moved to loader 10.0.0
    { "noncasigchk_1.0.0-3.0.2", "0x88..42..58", -4, 0, tbz_cond, nop_patch, nop_applied, true, MAKEHOSVERSION(1,0,0), MAKEHOSVERSION(3,0,2) },
    { "noncasigchk_4.0.0-16.1.0", "0x1E4839....00......0054", -17, 0, tbz_cond, nop_patch, nop_applied, true, MAKEHOSVERSION(4,0,0), MAKEHOSVERSION(16,1,0) },
    { "noncasigchk_17.0.0+", "0x0694....00..42..0091", -18, 0, tbz_cond, nop_patch, nop_applied, true, MAKEHOSVERSION(17,0,0), FW_VER_ANY },
    { "nocntchk_1.0.0-18.1.0", "0x40F9........081C00121F05", 2, 0, bl_cond, ret0_patch, ret0_applied, true, MAKEHOSVERSION(1,0,0), MAKEHOSVERSION(18,1,0) },
    { "nocntchk_19.0.0+", "0x40F9............40B9091C", 2, 0, bl_cond, ret0_patch, ret0_applied, true, MAKEHOSVERSION(19,0,0), FW_VER_ANY },
 
bth said:
no. 1.6.0 works fine with 22.1.0, my patterns did not break for ES 22.1.0 (the only thing that changed in 22.1.0)

also here's full bundle with atmosphere 1.11.1 loader patch included (kip .ips patches/ patches.ini)
Click to expand...
sys-patch 1.6.0 does work fine by itself, but when I install the patches listed here, atmosphere crashes when trying to boot from hekate. i'll upload the crash just on the off chance it isn't user error.
 

Attachments

bth said:
you do not have sys-patch that is up to date.

https://github.com/impeeza/sys-patch/blob/master/sysmod/src/main.cpp#L247-L253

the names are not like that.

i ignore your problem now.

Code: 
    { "noacidsigchk_1.0.0-9.2.0", "0xC8FE4739", -24, 0, bl_cond, ret0_patch, ret0_applied, true, FW_VER_ANY, MAKEHOSVERSION(9,2,0) }, // moved to loader 10.0.0
    { "noacidsigchk_1.0.0-9.2.0", "0x0210911F000072", -5, 0, bl_cond, ret0_patch, ret0_applied, true, FW_VER_ANY, MAKEHOSVERSION(9,2,0) }, // moved to loader 10.0.0
    { "noncasigchk_1.0.0-3.0.2", "0x88..42..58", -4, 0, tbz_cond, nop_patch, nop_applied, true, MAKEHOSVERSION(1,0,0), MAKEHOSVERSION(3,0,2) },
    { "noncasigchk_4.0.0-16.1.0", "0x1E4839....00......0054", -17, 0, tbz_cond, nop_patch, nop_applied, true, MAKEHOSVERSION(4,0,0), MAKEHOSVERSION(16,1,0) },
    { "noncasigchk_17.0.0+", "0x0694....00..42..0091", -18, 0, tbz_cond, nop_patch, nop_applied, true, MAKEHOSVERSION(17,0,0), FW_VER_ANY },
    { "nocntchk_1.0.0-18.1.0", "0x40F9........081C00121F05", 2, 0, bl_cond, ret0_patch, ret0_applied, true, MAKEHOSVERSION(1,0,0), MAKEHOSVERSION(18,1,0) },
    { "nocntchk_19.0.0+", "0x40F9............40B9091C", 2, 0, bl_cond, ret0_patch, ret0_applied, true, MAKEHOSVERSION(19,0,0), FW_VER_ANY },
Click to expand...
oh,how could i update the sys-patch? i download sys-patch-v1.6.1.zip and copy all folder to the sd root folder
 
SilverGoku said:
sys-patch 1.6.0 does work fine by itself, but when I install the patches listed here, atmosphere crashes when trying to boot from hekate. i'll upload the crash just on the off chance it isn't user error.
Click to expand...
i'd rather you provide the crash_log output not marked .bin (you renamed to .txt, it is a binary file, not log file for reading)
(it's saying 0100000000000001 / loader is crashing)

fangamer said:
oh,how could i update the sys-patch? i download sys-patch-v1.6.1.zip and copy all folder to the sd root folder
Click to expand...
this not sys-patch thread. you copy wrong.
 
Last edited by bth,
SilverGoku said:
sys-patch 1.6.0 does work fine by itself, but when I install the patches listed here, atmosphere crashes when trying to boot from hekate. i'll upload the crash just on the off chance it isn't user error.
Click to expand...
anyway more on this;

this is my debug log for the loader patch (which that error report claims is crashing, though i don't know how to read these properly, only the actual error log files)

which should be the same as sys-patch - the only difference is sys-patch only patches 00 on the 01 of the cmp


Code: 
(LOADER) Using compressed hash from package3_and_stratosphere_extracted/loader.kip1
(LOADER) SHA256 of package3_and_stratosphere_extracted/loader.kip1 is:
(LOADER) 03EC72DB053F34CA138D0381BBEFAD9A7D4BC442BEECF0AA4637DF229E1DB87A
(LOADER) Found 1 patch location(s) for 22.1.0

(LOADER) Pattern matched: noacidsigchk_10.0.0+ for 22.1.0
(LOADER) sys-patch pattern: 009401C0BE121F00
(LOADER) ghidra pattern: 00 94 01 C0 BE 12 1F 00
(LOADER) Offset: 0x006078
(LOADER) Instruction: cmp
(LOADER) Existing bytes: 1F00016B
(LOADER) Patch applied: 1F00006B
(LOADER) Pattern diff (context):
F35341A9F76343A9F96B44A9FB7345A9FD7BC8A8C0035FD64C53009401C0BE121F00016B69FAFF54C022403900010035C00240F9E1FF9F92E1DFFFF20000018BE19F70B21F0001EB42F9FF54E14340F922008052E00315AA882A009400F0FF35

Patch data:
from: 0x006078: (1F00016B) cmp w0, w1
to:   0x006078: (1F00006B) cmp w0, w0

Instruction order, the offset being patched is 0x6078:

0x006058:     (F3 53 41 A9)    ldp    x19, x20, [sp, #0x10]
0x00605C:     (F7 63 43 A9)    ldp    x23, x24, [sp, #0x30]
0x006060:     (F9 6B 44 A9)    ldp    x25, x26, [sp, #0x40]
0x006064:     (FB 73 45 A9)    ldp    x27, x28, [sp, #0x50]
0x006068:     (FD 7B C8 A8)    ldp    x29, x30, [sp], #0x80
0x00606C:     (C0 03 5F D6)    ret 
0x006070:     (4C 53 00 94)    bl    #0x1ada0
0x006074:     (01 C0 BE 12)    mov    w1, #0x9ffffff

0x006078:     (1F 00 01 6B)    cmp    w0, w1

0x00607C:     (69 FA FF 54)    b.ls    #0x5fc8
0x006080:     (C0 22 40 39)    ldrb    w0, [x22, #8]
0x006084:     (00 01 00 35)    cbnz    w0, #0x60a4
0x006088:     (C0 02 40 F9)    ldr    x0, [x22]
0x00608C:     (E1 FF 9F 92)    mov    x1, #-0x10000
0x006090:     (E1 DF FF F2)    movk    x1, #0xfeff, lsl #48
0x006094:     (00 00 01 8B)    add    x0, x0, x1
0x006098:     (E1 9F 70 B2)    mov    x1, #0xffffffffff0000
0x00609C:     (1F 00 01 EB)    cmp    x0, x1
0x0060A0:     (42 F9 FF 54)    b.hs    #0x5fc8
0x0060A4:     (E1 43 40 F9)    ldr    x1, [sp, #0x80]
0x0060A8:     (22 00 80 52)    mov    w2, #1
0x0060AC:     (E0 03 15 AA)    mov    x0, x21
0x0060B0:     (88 2A 00 94)    bl    #0x10ad0
0x0060B4:     (00 F0 FF 35)    cbnz    w0, #0x5eb4

instruction order:
ldp ldp ldp ldp ldp ret bl mov cmp b.ls ldrb cbnz ldr mov movk add mov cmp b.hs ldr mov mov bl cbnz


(LOADER-) Generated hekate-style patch block for 22.1.0
   [LOADER:03EC72DB053F34CA]
     .nosigchk=0:0x005F78:0x4:1F00016B,1F00006B
 
bth said:
anyway more on this;

this is my debug log for the loader patch (which that error report claims is crashing, though i don't know how to read these properly, only the actual error log files)

which should be the same as sys-patch


Code: 
(LOADER) Using compressed hash from package3_and_stratosphere_extracted/loader.kip1
(LOADER) SHA256 of package3_and_stratosphere_extracted/loader.kip1 is:
(LOADER) 03EC72DB053F34CA138D0381BBEFAD9A7D4BC442BEECF0AA4637DF229E1DB87A
(LOADER) Found 1 patch location(s) for 22.1.0

(LOADER) Pattern matched: noacidsigchk_10.0.0+ for 22.1.0
(LOADER) sys-patch pattern: 009401C0BE121F00
(LOADER) ghidra pattern: 00 94 01 C0 BE 12 1F 00
(LOADER) Offset: 0x006078
(LOADER) Instruction: cmp
(LOADER) Existing bytes: 1F00016B
(LOADER) Patch applied: 1F00006B
(LOADER) Pattern diff (context):
F35341A9F76343A9F96B44A9FB7345A9FD7BC8A8C0035FD64C53009401C0BE121F00016B69FAFF54C022403900010035C00240F9E1FF9F92E1DFFFF20000018BE19F70B21F0001EB42F9FF54E14340F922008052E00315AA882A009400F0FF35

Patch data:
from: 0x006078: (1F00016B) cmp w0, w1
to:   0x006078: (1F00006B) cmp w0, w0

Instruction order, the offset being patched is 0x6078:

0x006058:     (F3 53 41 A9)    ldp    x19, x20, [sp, #0x10]
0x00605C:     (F7 63 43 A9)    ldp    x23, x24, [sp, #0x30]
0x006060:     (F9 6B 44 A9)    ldp    x25, x26, [sp, #0x40]
0x006064:     (FB 73 45 A9)    ldp    x27, x28, [sp, #0x50]
0x006068:     (FD 7B C8 A8)    ldp    x29, x30, [sp], #0x80
0x00606C:     (C0 03 5F D6)    ret 
0x006070:     (4C 53 00 94)    bl    #0x1ada0
0x006074:     (01 C0 BE 12)    mov    w1, #0x9ffffff

0x006078:     (1F 00 01 6B)    cmp    w0, w1

0x00607C:     (69 FA FF 54)    b.ls    #0x5fc8
0x006080:     (C0 22 40 39)    ldrb    w0, [x22, #8]
0x006084:     (00 01 00 35)    cbnz    w0, #0x60a4
0x006088:     (C0 02 40 F9)    ldr    x0, [x22]
0x00608C:     (E1 FF 9F 92)    mov    x1, #-0x10000
0x006090:     (E1 DF FF F2)    movk    x1, #0xfeff, lsl #48
0x006094:     (00 00 01 8B)    add    x0, x0, x1
0x006098:     (E1 9F 70 B2)    mov    x1, #0xffffffffff0000
0x00609C:     (1F 00 01 EB)    cmp    x0, x1
0x0060A0:     (42 F9 FF 54)    b.hs    #0x5fc8
0x0060A4:     (E1 43 40 F9)    ldr    x1, [sp, #0x80]
0x0060A8:     (22 00 80 52)    mov    w2, #1
0x0060AC:     (E0 03 15 AA)    mov    x0, x21
0x0060B0:     (88 2A 00 94)    bl    #0x10ad0
0x0060B4:     (00 F0 FF 35)    cbnz    w0, #0x5eb4

instruction order:
ldp ldp ldp ldp ldp ret bl mov cmp b.ls ldrb cbnz ldr mov movk add mov cmp b.hs ldr mov mov bl cbnz


(LOADER-) Generated hekate-style patch block for 22.1.0
   [LOADER:03EC72DB053F34CA]
     .nosigchk=0:0x005F78:0x4:1F00016B,1F00006B
Click to expand...
ah i see. i tried disabling user exception handlers, and it is still not generating a crash report for me or i would provide it. :(
 

Site & Scene News

Go to forum More news

Popular threads in this forum

Dusk for switch (TLoZ Twilight Princess port)

Homebrew  New Homebrew "Foil Server"?

Homebrew  Full List of N64 Recompilation Switch ports

Hacking  WiFi chip failing and can't boot. is it possible to enable Airplane Mode by editing system save files directly?

Homebrew Tutorial Translation Project  CS2SX — Write Nintendo Switch Homebrew in C#

Homebrew  Sonic Unleashed Recompiled (Homebrew Port)

Is it fixable

Hacking Emulation  Switch Prod Keys downloading from sites okay?