So that is what I did, and I was able to boot to atmosphere, however, I would like to understand the ongoing issue with hekate if possible and why it wont allow me to boot from "launch" in its menu
--------------------- MERGED ---------------------------
So you are recommending I just redo my micro SD card and start over again?
I def see the potential and usefulness of hekate and I use it as my primary payload, but I didn't for a very long time because of stuff like OP is experiencing. In fact that's why I told him to use the payload as a boot entry cause I've never successfully launched atmos with sigpatch from hekate without just booting to fusee-primary. I end up with errors about nosigpatch failing etc, so I just use hekate to boot android or fusee.
SYSNand is on your switch itself, EMUNand will be created on the sd card....easiest way is to just create another Emunand once you get back up and running...but if you had games saves while playing on EMUNand then they will be saved to sd card EMUNand...
--------------------- MERGED ---------------------------
If you value your EMUNand and games saved to it then don't format it, just replace atmos /sigpatch files...
--------------------- MERGED ---------------------------
And put "hekate_ctcaer_5.5.4.bin" on your injector.
--------------------- MERGED ---------------------------
https://switch.homebrew.guide/index.html
i have replaced the atmos folders, I will try to play around with the sig patches and see if that changes anything. I really would like to not lose my game saves. anyway I can just copy them off the micro sd card and drop them back in once I have my games reinstalled?
Thanks for all your help guys, I somewhat got hekate working now, to start atmosphere I have to click on "payload" instead of "launch" what is the difference in me not having an emummc now?
If you want to go online with it and help prevent a ban, you should setup EMUNand, if you keep it in "Airplane" mode and dont go online at all, can just use Sysnand. And yes in hekate - Payloads - Fusee-primary to start, or change the hekate_ini file like user earlier was trying to explain to you.
Last edited by BigOnYa,
Here are the correct Boot Entries for you hekate_ipl.ini:
Copy fusee-primary.bin to bootloader/payloads whenever you Update Atmosphère.
Also make sure your hekate_ipl.ini is not named hekate_ipl.ini.txt
Code:
[Atmosphere SYS]
emummc_force_disable=1
payload=bootloader/payloads/fusee-primary.bin
[Atmosphere Hekate SYS]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
[Atmosphere EMU]
payload=bootloader/payloads/fusee-primary.bin
[Atmosphere Hekate EMU]
fss0=atmosphere/fusee-secondary.binCopy fusee-primary.bin to bootloader/payloads whenever you Update Atmosphère.
Also make sure your hekate_ipl.ini is not named hekate_ipl.ini.txt
Last edited by crazy_p,
Ok, do you mean if I want to go online and connect to the eshop or just go online even if I have configured my dns, I was thinking of configuring my dns in order to use aio updater. but as of now I have always kept my switch in airplane mode.
He wants you to use Hekate to load fusee_primary but not only is this inefficient, its also incorrectly done. Fss0 can only read fusee_secondary and not fusee_primary.
Similar threads
