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

[ber71]

Which message? I can not find it

maybe this
https://github.com/Atmosphere-NX/Atmosphere/issues/2388

 

[JamesDeans]

hey my keep tryin making forwarders but they dont work.
I also tried updating sigpatches and syspatch but it still shows me unpached
I dont understand how i should the ips patcher tool
It seems for me that from what i read here in the thread it is now possible but i dont understand how to install it correct.
Please help

 

[lsp199308]

Hello, everyone.
In HOS 17.0.0 and after, blanking your PRODINFO using any method (exosphere/blanking PRODINFO on NAND) will cause a User Abort in the nim service
nimID:0100000000000025
nim_patch_data:0xE2031FAA
[TABLE=full]
[TR]
[TD]constexpr auto adr_cond(u32 inst) -> bool {
return ((inst >> 24) & 0xFF) == 0x10[/TD]
[/TR]
[TR]
[TD]Can be found by wildcard: .0F00351F2003D5，
Can someone add sys-patch , thanks![/TD]
[/TR]
[/TABLE]

 

[impeeza]

maybe this
https://github.com/Atmosphere-NX/Atmosphere/issues/2388

https://github.com/Atmosphere-NX/Atmosphere/issues/2388#issuecomment-2402838435

Humm this is huge

 

[truemaster]

hello i have updated to fw 19 and im using atmosphere 1.8.0 with official (not patched) fusse.bin i have install syspatch 153 and have issues running tinfoil, the switch is acting like as if no sigpatches are installed but since im using syspatch i think sig patches are usless. but even if i use the patched fusee.bin and latest sigpatches same error any solutions. the tinfoil is the latest nro self installer

 

[Pseudo5417]

Hi! not so savy here but I updated firmware to 19.0 and downloaded and copied to root both hekaate 6.2.2 and atmosphere 1.8.0 when trying to inject fusee.bin an error pops, any idea on what should I do?

 

[petspeed]

hello i have updated to fw 19 and im using atmosphere 1.8.0 with official (not patched) fusse.bin i have install syspatch 153 and have issues running tinfoil, the switch is acting like as if no sigpatches are installed but since im using syspatch i think sig patches are usless. but even if i use the patched fusee.bin and latest sigpatches same error any solutions. the tinfoil is the latest nro self installer

Tinfoil selfinstaller doesn't work on fw19. Use the Applet version and start Tinfoil from Homebrew Menu or waint for new version

Post automatically merged: Oct 21, 2024

Hi! not so savy here but I updated firmware to 19.0 and downloaded and copied to root both hekaate 6.2.2 and atmosphere 1.8.0 when trying to inject fusee.bin an error pops, any idea on what should I do?

Did you also update the fusee.bin that you inject?
If yes then more details are needed. Show the error that pops up. That will make it much easier to help you

 

[truemaster]

ok thanks for the help

 

[thangga123]

Dear
After I upgraded to new atmosphere, hekate and sigpatch, some software reported errors
Has anyone encountered a similar situation?
Thank

 

[Konzolista]

Dear
After I upgraded to new atmosphere, hekate and sigpatch, some software reported errors
Has anyone encountered a similar situation?
Thank
View attachment 466241

Laziness kills people, go through the thread, it's been discussed here many times already
...and wipe your screen before taking pictures...

 

[Pseudo5417]

Tinfoil selfinstaller doesn't work on fw19. Use the Applet version and start Tinfoil from Homebrew Menu or waint for new version

Post automatically merged: Oct 21, 2024

Did you also update the fusee.bin that you inject?
If yes then more details are needed. Show the error that pops up. That will make it much easier to help you

I did updated fusee.bin from the same atmosphere version, this is the error that is giving me, not sure what I´m doing wrong.

 

[kidkat210]

I did updated fusee.bin from the same atmosphere version, this is the error that is giving me, not sure what I´m doing wrong.

That pic indicates your either using an older atmosphere with a new fusee.bin or a newer atmosphere and an older fusee.bin

 

[Hayato213]

I did updated fusee.bin from the same atmosphere version, this is the error that is giving me, not sure what I´m doing wrong.

Sound like your atmosphere build and fusee doesn't match.

 

[impeeza]

I did updated fusee.bin from the same atmosphere version, this is the error that is giving me, not sure what I´m doing wrong.

Which method are you using to start your console?

if you are using a chipmod, be sure the file PAYLOAD.BIN on the root of your console is updated.

If you are using a injector update the payload on it.

you boot your console with hekate? then the PAYLOAD.BIN must be hekate_ctcaer_6.2.2.bin renamed

if you boot you console directly to Atmosphère, then PAYLOAD.BIN must be fusee.bin from the same atmosphère version you have ,renamed.

 

[Pseudo5417]

Yes i understand it says incorrect fusee version, but as mentioned I am using latest hekate (6.2.2) and latest atmosphere (1.8.0) with the fusee.bin that is in that version, is in not updated there? what else could I be doing wrong? I am booting with hekate (using tegra rcm) and then injecting with fusee.

 

[impeeza]

Yes i understand it says incorrect fusee version, but as mentioned I am using latest hekate (6.2.2) and latest atmosphere (1.8.0) with the fusee.bin that is in that version, is in not updated there? what else could I be doing wrong? I am booting with hekate (using tegra rcm) and then injecting with fusee.

Are you trying to boot your console using Hekate bootloader or Atmosphère one?

how do you start your console? (modchip or payload injector)

 

[Pseudo5417]

Are you trying to boot your console using Hekate bootloader or Atmosphère one?

how do you start your console? (modchip or payload injector)

This is the process I usually do, connect switch with the jig to pc and inject with tegra, open hekate on swith and use payload-fusee.bin.

 

[impeeza]

This is the process I usually do, connect switch with the jig to pc and inject with tegra, open hekate on swith and use payload-fusee.bin.

Ok, please share with us your SDMC:/bootloader/Hekate_ipl.ini

on your console you inject Hekate payload, that is ok. thenk you manually select the next step? that is no so normal, most of people setup an autorun config on Hekate, so once you inject the bootloader hekate loads Atmosphère automatically.

share your Hekate_ipl.ini and we will try to help you.

 

[Pseudo5417]

Ok, please share with us your SDMC:/bootloader/Hekate_ipl.ini

on your console you inject Hekate payload, that is ok. thenk you manually select the next step? that is no so normal, most of people setup an autorun config on Hekate, so once you inject the bootloader hekate loads Atmosphère automatically.

share your Hekate_ipl.ini and we will try to help you.

These are the two that appear on my sd, I think autorun never worked for me for some rease, or i didn´t set it i dont remember. I really appreciate any help.

 

[impeeza]

These are the two that appear on my sd, I think autorun never worked for me for some rease, or i didn´t set it i dont remember. I really appreciate any help.

I see your problem. you are selecting the file SDMC:/bootloader/payloads/fusee.bin as a manual chainload of another payload, so you need:

update the file SDMC:/bootloader/payloads/fusee.bin to latest fusee.bin

OR

copy this on your SDMC:/bootloader/hekate_ipl.ini and try lo lad your console with hekate (I really recommend you to do this)

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

{--- BOOT ATMOSPHERE'S FUSEE.BIN ---}
[CFW - AtmosphereNX (V1)]
id=FUSEE
atmosphere=1
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/sys_cfw_boot.bmp

{--- BOOT PACKAGE3 FROM HEKATE ---}
[CFW - AtmosphereNX (V2)]
id=PACKAGE
emummcforce=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp
kip1patch=nosigchk
atmosphere=1
usb3force=1