not only "fusee-primary.bin", but also replace "fusee-secondary.bin" with "package3" (no file extension) in hekate_ipl.ini if using fss0 boot method.
This is the issue users in this thread are having : their Hekate IPL is still pointing to an old file.
When updating from older than 1.0.0 AMS to newer version:
- delete sd:/sept/ folder (not used anymore)
- delete sd:/atmosphere/fusee-secondary.bin (not used anymore)
- delete sd:/atmosphere/config/BCT.ini (not used anymore). Note: If you changed the setting for noGC, be sure to copy stratosphere.ini from the template folder into /atmosphere/config/stratosphere.ini and edit it accordingly.
- Edit hekate_ipl.ini, if present, rename fusee-primary.bin to fusee.bin
- Edit hekate_ipl.ini, if present, rename fusee-secondary.bin to package3
- delete sd:/bootloader/payloads/fusee-primary.bin (if present for you. Some guides put it here, some don't. This is how I like to launch AMS)
- if your version of AMS is older than 0.10.x, it still used "sd:/atmosphere/titles/" folder for Game mods with LayeredFS, rename the folder to "contents"
- and do the following steps too
and on every new update:
0) pre-update step, for security
- remove any theme you have installed
- Exit from your current firmware (either full shutdown the console and remove SD, or go to hekate UMS to transfer files to SD from USB), you can't update AMS files while AMS is running.
1) new files
- overwrite old Atmosphere content at SD root with new release (all the zip content : atmosphere, switch, and hbmenu.nro). This ensure you to keep previous configs, instead of deleting and reinstalling.
- overwrite old Hekate's "bootloader" folder at SD root with new release
2) patches
- overwrite Atmosphere and/or Hekate's bootloader at SD root with the corresponding
sigpatches's fusee.zip, based on the way you launch AMS (fusée or fss0). if you don't know, overwrite both. Attention, each new version of Atmosphere requires specific updated version of the patches. compare the "build hash" on the patch version against AMS zip package filename. If the patches are not available online (anymore), you can generate them yourself now, either with a computer (python if you are on linux, windows with MrDude's sigpatch creator) or homebrew directly on your Switch (with Dogty's sigpatch creator homebrew).
3) For convenience:
- copy Atmosphere's latest "fusee.bin" into sd:/bootloader/payloads/ folder. This will let you launch AMS from Hekate's payload menu : Hekate > payload > fusée.bin.
- copy sd:/bootloader/update.bin to a new file. Rename the copied file to "reboot_payload.bin", and move+overwrite it into Atmosphere folder. This will ensure you can reboot to Hekate from HB menu with "reboot to payload" app instead of rebooting AMS.
4) Additional updates
- optional : verify if there's a new lockpick_RCM.bin released, and replace it in sd:/bootloader/payloads/ too. (And if there's a new version, don't forget to launch that RCM binary from Hekate to dump your new keys to SD, and keep a save/back to your computer!)
- mandatory : Update ALL the sys-module you have on your SD : Tesla, Mission Control, emuiibo, etc.
final step) payload sender/injector for Fusée gelée
- Replace hekate_ctcaer_x.x.x.bin payload binary on your RCM booter/dongle/phone/chipset/computer/whatever you use to send payloads to RCM. But, this is unnecessary if your previous hekate is not too old, because it now always check if "update.bin" is newer and launch it instead. But I prefer having the correct one on my RCM device/dongle/app.
When I want to boot Atmosphere, I don't go into "launch" menu, but instead go to Payloads and select Fusée. it's a little faster, one less splash screen from hekate.
This method uses "fusée" (primary), not the FSS0 boot method.
If you prefer using "hekate" fss0 boot method, you need to use the "Launch" menu you setup using hekate_ipl.ini
Hekate:
https://github.com/CTCaer/hekate/releases
Atmosphère:
https://github.com/Atmosphere-NX/Atmosphere/releases
Lockpick_RCM:
https://github.com/shchmue/Lockpick_RCM/releases
sigpatches: no direct link, but it's very easy to find the patches from itotaljustice on a web search engine. take "fusee.zip".
make the patches yourself :
- windows tool from MrDude :
https://github.com/mrdude2478/IPS_Patch_Creator
- Homebrew tool from dogty (dogcsty) : (removed link until official release)
all information about the patches are here :
https://gbatemp.net/threads/info-on-sha-256-hashes-on-fs-patches.581550/
If you haven't done it yet, you can also update your console's firmware.
https://gbatemp.net/posts/9564701
