- Status
Sorry being ignorant, but what should I do with these? Extract in the root folder of my SD card? I facing issues when trying to run games and I'm pretty sure it's because of signature patches and I found these, just don't know what to do with them.
these patches work like a charm.
- delete your old CFW from your FAT32 micro sd ( i hope )
- on PC ... extract a package like Deepsea into a folder
- in this folder extract these patches and replace files if required
- copy the contents of this folder to the microsd
- injects hekate via tegraRCMgui
- on hekate go to :
a ) / Launch / ... choose to launch cfw on sysnand or emummc
b ) / options / Autoboot / ... choose to launch cfw on sysnand or emummc .. and save this config ( Save Options )
come back / Launch / ... choose to launch cfw on sysnand or emummc
* don't launch Atmosphere fusee primary via hekate / more config.
*install backups with Awoo Installer + NS-USBloader ...only.
* if you install backups with Tinfoil/HBG-shit ... may not work properly on these patches.
Last edited by mikifantastik98,
Is there a reason as to why not launch Atmosphere via fusee primary? Kinda out of the loop here.
As this thread title implies, these patches are for booting with Hekate/Kosmos or more accurately with fss0. If you boot with fusee-primary whether primarily or via chainloading, you would need another set of patches.
What is the fss0? (Sorry really don't understand any of these, I only come here for the ES patches.)
To give a bit of context, Kosmos initially was known as SD Files. As the name implied, they distributed a package of CFW files that came with some useful homebrew applications for easy setup of CFW. This package existed before the first official release of Atmosphere. The only way this was possible was by using an alternative bootloader known as Hekate. Now since Hekate is not primarily meant to load Atmosphere, it requires a bit of setup in order to work. This involved compiling all of Atmosphere's individual parts and having Hekate point to them in order to boot CFW. Unfortunately this was rather inefficient so instead an easier method was developed in the form of fss0 where Hekate can grab all of those files from one individual file: fusee-secondary.
fuse primary chainloads fuse secondary to load HOS
hekate is a replacement for fuse primary and "takes content" out of fuse secondary to load HOS
it not a hack, not wonky, doesnt harm your switch and the only person that thinks its bad is spreading this rumor because he cant get the users to use tinfoil.
Edit (this should make it clear):
Send Payload “Fusee-primary.bin” > boot Atmosphere (fusée-secondary)
Send Payload “Hekate” > chain-boot fusee-primary.bin > boot Atmosphere (payload=)
Send Payload “Hekate” > Hekate uses fusee-secondary to boot Atmosphere (fss0=)
Hekate (and Nyx interface of Hekate) set by DeepSea ready-to-use package lets you choose how you want to boot your console (Stock, SysMMC or emuMMC) directly from its menu. But this choice can only be applied if you launch Atmosphère with fusée-secondary (“fss0=”).
If you have an emuMMC folder or partition and use fusée-primary (“payload=”) method to boot your console, Atmosphère will always follow its own setting to determine whether to use sysMMC or emuMMC regardless of the user choice in Hekate.
While an alternative may be to edit Atmosphere config files to force disable emuMMC and reboot the console, the typical method is to edit “emummc/emummc.ini” and set emummc!enabled=0 or 1. 0 means disabled. 1 Means enabled. You can edit the file yourself, or use existing homebrew directly from your Homebrew Launcher menu, such as emuMMC Toggler or EmuMmcConfig and reboot the payload (fusée-primary).If you use Hekate, you could name your boot choice “Atmosphere” only.
This loss of flexibility and user unfriendliness from Hekate boot menu when using fusee-primary.bin to launch AMS is why DeepSea uses the “fss0=” booting style for syntax. This increased flexibility, all in one menu would not be possible if booting using fusée-primary.bin
Last edited by Slluxx,
there is nothing wrong with neither of those methods.
if you prefer atmospheres way of booting and losing the flexibility that hekate gives you with emummc, thats completly fine.
but those booting methods need different kind of patches. the patches in here are for the hekate fss0 method and not for the fusee primary method
What is the flexibility that is given when booting with the emummc?
Might stop using fusee primary and just boot through that instead.
Hope he never comes back here. He intentionally derailed the thread, really making it a mess.
What flexibility do you lose? Just chainload fusee-primary through hekate, and you will have most, if not, all of hekate's features.
For sigpatches, people will usually need them for either emuMMC or sysMMC, never both. That way, using fusee-primary with its sigpatches is good enough for using it on either emuMMC or sysMMC (fusee-primary relies on emummc.ini to see if emuMMC is selected), and people can use fss0 to boot the other with homebrew (here, they won't care about sigpatches).
Last edited by pofehof,
Hekate lets you launch CFW with either sysMMC or emuMMC but only when using the fss0 method. When you use fusee, you can only launch whatever it is configured to launch which is sysMMC by default. Fusee has to be manually configured to launch emuMMC which isn't as easy as setting it up with fss0.
God damn, the different opinions and all this info is making me understand less, should I just simply use the launch options (sysMMC/emuMMC)?, btw what's the difference between these two?
sysMMC launches sysMMC and emuMMC launches emuMMC. emuMMC is self-explanatory if you know what it is and sysMMC is your normal console.
- Status
Similar threads
