Hacking Sigpatches for Atmosphere (Hekate, fss0, fusee & package3)
- Thread starter ShadowOne333
- Start date
- Views 2,333,714
- Replies 3,678
- Likes 249
Or you can read the OP.
The Hekate_ipl.ini file has been included since day 1 as a template for the ones needing it.
Curious around the latest business with Atmosphere 1.7.1 and FW 18.1.0.
I got it running with no problems in the end and updated everything the same way as a I always do, but used the modified fusee.bin because I ran into corruption and NCA-errors (I admit I tried the modified fusee as a last resort and had no clue as to why I would need it).
I'm not nearly as technical as alot of you guys.. can someone explain in simpler terms what changed lately? Aren't signature patches a thing anymore? And what's sys-patches?
I got it running with no problems in the end and updated everything the same way as a I always do, but used the modified fusee.bin because I ran into corruption and NCA-errors (I admit I tried the modified fusee as a last resort and had no clue as to why I would need it).
I'm not nearly as technical as alot of you guys.. can someone explain in simpler terms what changed lately? Aren't signature patches a thing anymore? And what's sys-patches?
By looking at the code it was a clever way to add the fs-patches by replacing the no-gc patch great work!
I took the liberty to create a patch describing the modifications you've made to easily modify it in future updates
Edit: you would of course need to change the sha commit hash when needed in the lbraires/config/common.mk and thermosphere/Makfile files
What «NO Game Cartdrige» have to do with FS sigpatches. Removing the NoGC patches will upgrade the cartridge firmware making it unusable on lower HOS firmware
If you look at the code they changed they just did that for simplicity. But you can change the code so you can keep them both.
by the way, the only reason I manually set the commit hash is so it keeps the same build id as official atmosphere releases, so it'll appear as a normal official release instead of an unofficial commit id on crash dumps and error reports. it's not super necessary (though I guess manually setting it here helps when all the git repo files aren't included, so it doesnt try to use git commands to get them dynamically)
when was the last time you've needed to run a game card on 11.0.0 fw and under?
Hold on. If I'm understanding that correctly, you make a modified version to re-add patching functionality... and then mask it to appear in logs as the official release? Am I getting that right?
If so, why do that? Wouldn't that result in the official dev eventually getting error reports and crash dumps for unofficial builds, and unable to easily tell them apart? That sounds like trouble for everyone involved.
because the modifications here aren't going to actually break anything, and actual atmosphere bugs are still present. so it will be useful if people can report bugs without having to fuss about the whole unofficial builds and anti-signature patch stuff
Even if there was a way to be 100% sure the modifications will not cause any trouble, that functionality is no longer in the official release for good reason. And knowing the dev keeps (understandably) a healthy distance from the fuss... Making and sharing an unofficial build that re-adds it, for ease of use, that's good and helpful, kudos for that. Really. But having it pose as an actual, official release... I don't know, that doesn't feel right.
ok, I took it down. if anyone wants the functionality, dogtygr has a patch up and you can make do with that
hi all. I updated my switch firmware to 18.0.0 and using AMS 1.7.1 with modified fusee.bin.
however now I'm experiencing some games sometimes run, but sometimes it will says the game is corrupted (Unable to start software).
it happens on two nintendo switch that I owned. some examples of the games are super mario 3d world, super mario 3d all stars, princess peach.
Does anybody else experience this? does anyone have advice on how to solve this issue?
This never happened before atmosphere remove support for the patches.
any help is appreciated. thank you!
however now I'm experiencing some games sometimes run, but sometimes it will says the game is corrupted (Unable to start software).
it happens on two nintendo switch that I owned. some examples of the games are super mario 3d world, super mario 3d all stars, princess peach.
Does anybody else experience this? does anyone have advice on how to solve this issue?
This never happened before atmosphere remove support for the patches.
any help is appreciated. thank you!
Use SYS-Patch Sysmodule. https://gbatemp.net/threads/sys-patch-sysmod-that-patches-on-boot.633517
thank you! I'll try it.
I assume using the modified fusee.bin is quite straightforward, but apparently it has some issues.
Post automatically merged:
btw, If I use sys-patch, I assume I'll simply use the original fusee.bin and I don't need to use the sigpatches anymore? should I still keep the bootloader directory?
Post automatically merged:
thank you @impeeza !.
after reading a bit, what I did was:
use sys-patch found here https://gbatemp.net/download/sys-patch-1-5-2-binary-fw-18-1-0-atmosphere-1-7-1.38686/
which works for atmosphere 1.7.1 and firmware 18.0.0 (should work for 18.1.0 too)
the one found in the guide https://www.gamebrew.org/wiki/Sys-patch_Switch in the 1st post of this thread, is the old sys patch version 1.5.0, which doesn't work for newer games. this confuse me for a bit, because the guide page doesn't contain the latest sys patch compiled by @impeeza . My suggestion is to link the sys patch 1.5.2 in the 1st post of this thread to avoid confusion.
2. to avoid redundancy, I remove the sigpatches from the atmosphere directory, and I also remove the bootloader directory from root, since I don't use hekate. I simply boot atmosphere to sysnand.
so far, the games seems to be working fine. if I found any other issues, I'll report back here.
thank you!
Last edited by arabtm,
Similar threads
- No one is chatting at the moment.
-
-
-
-
-
-
-
-
@
SylverReZ:
The pcTattletale situation was really damning. Nobody was arsed to do any strong security for their monitoring app. -
-
-
@
SylverReZ:
@Xdqwerty, It was a monitoring application designed to monitor the activity of phones and computers (also known as "stalkware"). Somebody managed to hack into the company's Amazon web server and leaked the personal data of people using the program, they went out of business after this.
-
-
@
SylverReZ:
There was a HUGE vulnerability allowing somebody to grab raw unencrypted screenshots without them enforcing any form of security added using a simple Python script. The passwords for the accounts were MD5 hashed, so fairly easy to crack.
-
-
-
-
@
SylverReZ:
@Xdqwerty, Yeah, its wild especially for a company who aren't aware. You know what they say, you fuck around and find out.+1
-
-
-
-
-
-
-
-
