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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,337,001
  • Replies Replies 7,371
  • Likes Likes 266
KISS principle. Fusee is stage 1 loader that does all the system initialization before you can load into the os. Hekate is an alternative stage 1 loader, if you chain load fusee through hekate you're running two bootloader back to back for no reason when hekate is already capable of doing everything fusee does on its own
Yet, hekate bypasses some atmosphere settings and doesn't allow to boot games above your FW which is a feature since SX OS days...

Fusee payload I can play games much above my FW...
 
  • Like
Reactions: impeeza
Yet, hekate bypasses some atmosphere settings and doesn't allow to boot games above your FW which is a feature since SX OS days...

Fusee payload I can play games much above my FW...
Fusee does nothing to allow or prevent that. Some installers lower the fw requirements when installing the games (if you tell them to), and proper sigpatches are required to run them. And exactly what fusee settings does hekate "bypass"? Have you actually read the entire front page of the repo and studied all of the keys and options available? Just because "standard" ipl.ini that gets pushed with the sigpatch bundle or AIO packs doesn't have those other things configured, doesn't mean it's not an option.
 
Fusee does nothing to allow or prevent that. Some installers lower the fw requirements when installing the games (if you tell them to), and proper sigpatches are required to run them. And exactly what fusee settings does hekate "bypass"? Have you actually read the entire front page of the repo and studied all of the keys and options available? Just because "standard" ipl.ini that gets pushed with the sigpatch bundle or AIO packs doesn't have those other things configured, doesn't mean it's not an option.
What kind of patches would do that? Just curious...
 
Fusee does nothing to allow or prevent that. Some installers lower the fw requirements when installing the games (if you tell them to), and proper sigpatches are required to run them. And exactly what fusee settings does hekate "bypass"? Have you actually read the entire front page of the repo and studied all of the keys and options available? Just because "standard" ipl.ini that gets pushed with the sigpatch bundle or AIO packs doesn't have those other things configured, doesn't mean it's not an option.
Hekate has many atmosphere serttings bypass that use hekate own settings for example one of them is updater2p among many, that one as example bypass the reboot_to_payload from atmosphere...

And Fusee does bypass FW requirement, I have tested many times, hekate + hekate latest sigpatches and could only run games upto my FW, all other installed games above my FW gets corrupt and can't also install anything above my FW...

With fusee even on FW 15.0.0 I could run most FW 17.0.1 games which never worked with FSS0.

I also tried syspatch with everything patched with Hekate FSS0 and same result so something in it is bypassing something that have always been there since even SX OS days...

And to install games I just use tinfoil which bypasses FW requirement same way I tried on hekate which never works...

It's likely that games have to be modded to run on hekate on a lower FW...

ps: It's more than clear reading hekate that it uses it's own settings though some can still be used from atmosphere if they are present but I never found a way to bypass the FW requirement with FSS0.
You think scires would have piracy-specific functionality like this in his software?
It's nothing to do with piracy...
 
Last edited by guily6669,
oh? in what non-piracy scenarios would that be relevant?
well any app that is installed that is made for last FW can be used on a lower FW for example kinda like how tinfoil is installed except it's made to require very low FW... but like if they made GTA V with latest SDK would require latest FW to test even if it was on a FW that was still unhackeable at the moment in time, it can be bypassed without having to modify the installer...

Anyway I don't think it's intentional but have always been present and simply doesn't work with hekate so any new latest FW game you have to go run update it even if atmos still doesn't support it unless is a compatible FW likely 18 and 18.0.1 are probably compatible, no idea as I'm on FW 17.0.1 and can install any FW 18+ required game and play well and likely will still work for FW 19...
 
well any app that is installed that is made for last FW can be used on a lower FW for example kinda like how tinfoil is installed except it's made to require very low FW... but like if they made GTA V with latest SDK would require latest FW to test even if it was on a FW that was still unhackeable at the moment in time, it can be bypassed without having to modify the installer...

Anyway I don't think it's intentional but have always been present and simply doesn't work with hekate so any new latest FW game you have to go run update it even if atmos still doesn't support it unless is a compatible FW likely 18 and 18.0.1 are probably compatible, no idea as I'm on FW 17.0.1 and can install any FW 18+ required game and play well and likely will still work for FW 19...
in which non-piracy situation are you going to be trying to run games in a lower firmware version than they ask for?
 
  • Like
Reactions: HenryBaby
Isn't tinfoil still refusing to work on systems with hekate installed? Get rid of that pos software. There are better installers now that get the job done faster.
 
I think you are mixing terms and concepts...
well you can try for example downgrade firmware to 16 and try a FW 17+ game with hekate FSS0 with latest hekate sigpatches or sys-patch and just installing a normal backup with tinfoil nothing modified and you will see it will never boot, throw a error and then corrupt...

with Fusee payload it just works.
in which non-piracy situation are you going to be trying to run games in a lower firmware version than they ask for?
Again for homebrew devs doing installing kind of projects even though it's unlikely.

But like I said the feature is likely from other thing but simply works and with hekate it overrides something and doesn't work.

ps: I don't need to go run updating crap FW when they come out and before everything is updated and broken on it to run whatever newer game that require newer FW with fusee so whatever...
 
well you can try for example downgrade firmware to 16 and try a FW 17 game with hekate FSS0 with latest hekate sigpatches or sys-patch and just installing a normal backup with tinfoil nothing modified and you will see it will never boot, throw a error and then corrupt...

with Fusee payload it just works.
Let me try in a moment.
 
Let me try in a moment.
I already tried many times even with your older hekate sigpatches and with latest sys-patch and never worked, all the games I had only the ones upto my FW were working and all the others were turning corrupt, as soon as I booted with fusee, I could check the games again and checked OK and played again, tried booting again with FSS0 same thing... I was on FW 16 something back then and FW 17+ wouldn't work while with fusee even some FW 18 games would work...

It's likely that with hekate we have to mod the game install to change the FW required version or maybe with DBI or some crap, no idea, with fusee just need to install with any installer that has the option to install regardless of FW needed with nothing modded.

EDIT: Also you have to pay attention to the game's update cause like some games with FSS0 I could play on my FW but after updating couldn't because the FW requirement changed and some games this happens, like the original game requires lower FW than the updated version...
 
Last edited by guily6669,
@guily6669 you are completely talking out of your ass. Fusee, and Atmosphere in general will not run ANYTHING without sigpatches, besides legit dumps with private tickets that belong to you. Daybreak works, because firmware files don’t need private tickets. (NROs run from hbl excepted, of course).

R2p is still something you can configure, so thanks for answering my question without answering my question. You haven’t so much as read through the front page of the hekate repo.
 
I already tried many times even with your older hekate sigpatches and with latest sys-patch and never worked, all the games I had only the ones upto my FW were working and all the others were turning corrupt, as soon as I booted with fusee, I could check the games again and checked OK and played again, tried booting again with FSS0 same thing... I was on FW 16 something back then and FW 17+ wouldn't work while with fusee even some FW 18 games would work...

It's likely that with hekate we have to mod the game install to change the FW required version or maybe with DBI or some crap, no idea, with fusee just need to install with any installer that has the option to install regardless of FW needed with nothing modded.

EDIT: Also you have to pay attention to the game's update cause like some games with FSS0 I could play on my FW but after updating couldn't because the FW requirement changed and some games this happens, like the original game requires lower FW than the updated version...


Well I just made this test:

Console V1 unpatched, FW 18.1.0, SYS-Patch 1.5.2, Hekate 6.2.0 booting via FSS0: Everything working fine.

Removed themes and downgraded to FW 15.0.0


Starting using official Fusee commit-e85bc4d directly: Everything works fine

Starting using official Fusee commit-e85bc4d modded to re enable FS patching directly: Everything works fine

Starting Atmosphère commit e85bc4d vía Hekate 6.2.0 using FSS0 package3 loading: Error reading the game, corrupted files

Starting Atmosphère commit e85bc4d vía Hekate 6.2.0 using FSS0 package3 loading AND REMOVING kip1patch=nosigchk from Hekate_ipl.ini: Error reading the game, corrupted files

Trying to reinstall the game:

1718419138321.png


Sadly I don't think CTCaer will Help us about this because he is very strong to be against Piracy and that is only needed on piracy.

reupgrading to FW18 everything works fine, even the installation:
1718419244879.png
 
Well I just made this test:

Console V1 unpatched, FW 18.1.0, SYS-Patch 1.5.2, Hekate 6.2.0 booting via FSS0: Everything working fine.

Removed themes and downgraded to FW 15.0.0


Starting using official Fusee commit-e85bc4d directly: Everything works fine

Starting using official Fusee commit-e85bc4d modded to re enable FS patching directly: Everything works fine

Starting Atmosphère commit e85bc4d vía Hekate 6.2.0 using FSS0 package3 loading: Error reading the game, corrupted files

Starting Atmosphère commit e85bc4d vía Hekate 6.2.0 using FSS0 package3 loading AND REMOVING kip1patch=nosigchk from Hekate_ipl.ini: Error reading the game, corrupted files

Trying to reinstall the game:


Sadly I don't think CTCaer will Help us about this because he is very strong to be against Piracy and that is only needed on piracy.

reupgrading to FW18 everything works fine, even the installation:
Just like I told you, but thanks for diving deeper.

Anyway I would really like if someone could talk with him and ask if there's some kind of atmosphere setting or hekate setting to bypass the FW...

That's why I keep using fusee and only need to upgrade FW in like years usually.
 

Site & Scene News

Popular threads in this forum