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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,360,824
  • Replies Replies 7,392
  • Likes Likes 266
you must read before tap, but well, first be sure you are on Atmosphère 1.6.1 prerelease, update Hekate to 6.0.7 and backup and delete sd:/atmosphere/contents folder, because some sysmodules and themes are no compatible with FW17

REINSTALL SIGPATCHES and then start your console and now you can backup your savegames.
Will the current Sig patches work with 17.0 because that's what my CFW sysnand is my emummc works fine as well as ofw it's only the CFW sysnand that crashes after it boots up my emunsnd is still 16.1.0 it was only the system I accidentally updated
 
  • Haha
Reactions: kerelenko
Current latest sigpatches won't work with 17.0.0.
There's sys-patch module that allows games to work, but homebrew forwarders and XCI installs still do not work.
XCI now works as do NSZ - it's just forwarders and modded xci files that need to be done now. Be patient as always and once the files patches are complete and tested for issues, there's no doubt they will be released. Just stay on 16.1.0 for now unless you are told otherwise, there's no need to update just yet as no games require you too. If you want to play online with 17.0.0 - you should not be using CFW to do this so patches are irrelevant for that scenario.
 
They haven't been released yet, check this thread every now and then for more updates.
For the time being it's suggested that you downgrade to 16.1.0 via Daybreak and use either these (for firmware 16.1.0 and Atmosphere 1.5.5) or these (for firmware 16.1.0 and Atmosphere 1.6.1).
I'm still at 16.1, it's just annoying to keep getting the nag on OFW.
 
  • Like
Reactions: impeeza
XCI now works as do NSZ - it's just forwarders and modded xci files that need to be done now. Be patient as always and once the files patches are complete and tested for issues, there's no doubt they will be released. Just stay on 16.1.0 for now unless you are told otherwise, there's no need to update just yet as no games require you too. If you want to play online with 17.0.0 - you should not be using CFW to do this so patches are irrelevant for that scenario.
Did "borntohonk" manage to find the new FS locations? Looks like it on Github.
 
Did "borntohonk" manage to find the new FS locations? Looks like it on Github.
Several people are working on that, including MrDude and iTotalJustice.
Bug Nin changed a lot the FS functions so a lot of testing is currently being made to ensure no errors get introduced on new set of patches.

XCI now works as do NSZ - it's just forwarders and modded xci files that need to be done now. Be patient as always and once the files patches are complete and tested for issues, there's no doubt they will be released. Just stay on 16.1.0 for now unless you are told otherwise, there's no need to update just yet as no games require you too. If you want to play online with 17.0.0 - you should not be using CFW to do this so patches are irrelevant for that scenario.


Advanced are being tracked on Sys-Patch and IPSCreator GitHubs
 
Several people are working on that, including MrDude and iTotalJustice.
Bug Nin changed a lot the FS functions so a lot of testing is currently being made to ensure no errors get introduced on new set of patches.




Advanced are being tracked on Sys-Patch and IPSCreator GitHubs
Yepp I'm following it. It seems that bonrtohonk seem to have manage to decrypt the method the longest. So I generally just got curious.
 
  • Love
Reactions: impeeza
Ok. Wrong wording. Not nsp and nsz, but nca and ncz. Padding issue applies only to nsp<->nsz conversion. Internal files are identical.
You know how to handle nsp files in deep like no other i know, i just catch your wrong wording to point to an old issue i had with nsp indexer and reported to nsz author.
You know how much respect i have for your talent.
 
  • Like
Reactions: impeeza
Not sure, that ncm needs to be patched. There are no checks related to signatures. And not working xci old installs means that header signature check not removed.
 
@duckbill007

Please read here about distrubution bit setting breaking the NCA signatures,

https://github.com/ITotalJustice/sys-patch/issues/5

I've already modded tinwoo so you can skip modding that bit, but all current installers should probably be modded to at least add an option to skip modding the header. It's not an issue on older firmwares but for 17.xx it seems to cause issues when installing nca's that have had that bit modded.

Actually that post I linked describes the issue, so it's worth a read.
 
How long do sigpatch releases usually take after each update?
The time it takes, Is a lot of people working on that, giving for free their time and knowledge, Of course you can get an IDE an start coding and make them as soon as you wish.

Of course as you are paying so much for the sigpaches you can demand them by released now.
 
The time it takes, Is a lot of people working on that, giving for free their time and knowledge, Of course you can get an IDE an start coding and make them as soon as you wish.

Of course as you are paying so much for the sigpaches you can demand them by released now.
Relax, I was merely asking how long it takes on average for new sigpatches to be releases after an update. I wasn't asking with the intention of having these people hurry up or anything like that.

Usually really quick unless there are issues.
Good to know. I guess there are issues this time then. Wasn't aware this was such a big update. Goes to show that not everyone reads changelogs, I guess... :P
 

Site & Scene News

Popular threads in this forum