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

[Olmectron]

I got 17.0.0 installed in SysMMC. And 16.1.0 in EmuMMC.

Maybe it's a stupid question, but could I keep Atmosphere 1.6.1 in the console for keep booting Stock in SysMMC already in 17, and use these patches for use in EmuMMC without having to change atmosphere every time I want to change between Sys and Emu?

 

[Crung]

Im on 17.0 . I have 16.1 sigpatches (from sigmapatch) . I get "nosigchk" but then im able to install games and play them just fine. I thought the sigpatches did not work on 17.0

 

[impeeza]

the sigpatches in the first post will work in ams 1.6.0 with fw 16.0.3?

Syspatches on OP works for all firmware versions up to 16.1.0. and Atmosphère Up to 1.5.1.


For Firmwares Up to 16.1.0 and Atmosphère 1.6.1 prerelease you could use this package:

 

[sj33]

Syspatches on OP works for all firmware versions up to 16.1.0. and Atmosphère Up to 1.5.1.


For Firmwares Up to 16.1.0 and Atmosphère 1.6.1 prerelease you could use this package:

Oh excellent - with this I can have my sysmmc on 17.0.0 and emummc on 16.1.0 - best of both worlds!

 

[duckbill007]

Just a question: did you checked nn::fssrv::sf::IFileSystemProxyForLoader:penCodeFileSystem call for sigcheck?

 

[Yannick_SG]

I just installed the new update, but after a few moments of booting (for example when I go to the settings for example) I get the error 2123-0011 (0x167b). Does anyone have the same? Here a image of the full error:

EDIT: I had some issues with the update, as the SD Card was exFAT and after I installed the new FW I pressed only FAT32, so I had to change the SD Card (256GB) to FAT32 as well - maybe that also plays a role?

 

[The-Ran-Dom-One]

I need ES sigpatches after using this zip

 

[taxco]

I just installed the new update, but after a few moments of booting (for example when I go to the settings for example) I get the error 2123-0011 (0x167b). Does anyone have the same? Here a image of the full error:

EDIT: I had some issues with the update, as the SD Card was exFAT and after I installed the new FW I pressed only FAT32, so I had to change the SD Card (256GB) to FAT32 as well - maybe that also plays a role?

It tels you becouse of program 0100xxxx
delete the folder 0100xxxxxxxxxxx25 on your sd card.

Downgrade to firm 16 becouse games anit working on firm 17 until patches are released.

 

[impeeza]

Edit, it seems to be a Theme related folder, just backup it and remove from SD Card.

 

[impy101]

I hope the sigpatches update comes soon. Can't play any games since they all ask for an internet connection. Regret updating to 17.0.0

 

[Tokiwa]

I hope the sigpatches update comes soon. Can't play any games since they all ask for an internet connection. Regret updating to 17.0.0

Yup, next time you should check if atmosphere and sigpatches are available before updating.

 

[Jandresquiroga]

I just installed the new update, but after a few moments of booting (for example when I go to the settings for example) I get the error 2123-0011 (0x167b). Does anyone have the same? Here a image of the full error:

EDIT: I had some issues with the update, as the SD Card was exFAT and after I installed the new FW I pressed only FAT32, so I had to change the SD Card (256GB) to FAT32 as well - maybe that also plays a role?

If you have the console connected to Wi-Fi internet, put it in airplane mode

 

[impeeza]

I hope the sigpatches update comes soon. Can't play any games since they all ask for an internet connection. Regret updating to 17.0.0

downgrade to FW 16.1.0.

 

[realg123]

downgrade to FW 16.1.0.

Stupid question, but how would you downgrade would you need a nand backup of your FW on 16.1.0?

 

[Stidwack]

Stupid question, but how would you downgrade would you need a nand backup of your FW on 16.1.0?

use AIO updater to download the 16.1.0 firmware, then Daybreak to install.

 

[realg123]

use AIO updater to download the 16.1.0 firmware, then Daybreak to install.

Thank you, just to confirm it can be OFW 16.1.0 firmware? I remembered reading sometime each time you upgrade it burns a fuse and after a certain point you can't downgrade is this still true? Is there a risk of bricking?

 

[impeeza]

Stupid question, but how would you downgrade would you need a nand backup of your FW on 16.1.0?

never use AIO, just get a copy of the FW 16 and use Daybreak homebrew to install it, then reinstall the sigpatches and that is all.

remember update your atmosphère to 1.6.1

 

[realg123]

never use AIO, just get a copy of the FW 16 and use Daybreak homebrew to install it, then reinstall the sigpatches and that is all.

remember update your atmosphère to 1.6.1

Thank you, does fuse count matter? I've updated manually before, but I'm wondering if there is anything special that needs to be done before downgrading, I thought it could cause a brick if you went over the fuse count, do I need to check anything else before doing so?

 

[impeeza]

Thank you, does fuse count matter? I've updated manually before, but I'm wondering if there is anything special that needs to be done before downgrading, I thought it could cause a brick if you went over the fuse count, do I need to check anything else before doing so?

fuses do not count if you use CFW (Atmosphère). and try to always use Atmosphère so you avoid burn the fuses.

 

[realg123]

fuses do not count if you use CFW (Atmosphère). and try to always use Atmosphère so you avoid burn the fuses.

Thank you, sorry last question, would it still work on CFW I don't have to be using emunand to downgrade correct?