- Joined
- Aug 6, 2017
- Messages
- 19,244
- Solutions
- 7
- Reaction score
- 10,211
- Trophies
- 2
- Age
- 32
- Location
- New York City
- XP
- 14,111
- Country

Today I tried updating Atmosphere and now I can't boot into CFW. First I downloaded the latest Atmosphere release dropped it in the root of my SD card. I then removed the sept folder and fusee-secondary.bin from the atmosphere folder. After that I replaced the hekate_ipl.ini with one the referenced package3. Now I can't seem to boot into CFW, as fusee-primary.bin no longer works and the new fusee.bin just shows two Atmopshere splash screens then locks on a black screen until you hard reset. I've tried chainloading fusee.bin through Hekate as well but to no avail. Anybody have any ideas how to fix this? Also my SD is formatted as FAT32 if that matters.
Rename the latest hekate payload to reboot_to_payload.bin and replace the one inside the /atmosphere folder with that. Then whenever you perform the Restart function from the Power menu while in CFW, it will launch the reboot_to_payload.bin fileso I dual booted my Switch and now have Linux and Atosphere but can I get some help, how do I make my Atmosphere swap back to Hekate payload so I can swap without shutting down the system? Does it have to do with my Hakate file in the bootloader/ini ? Heres mine. Can someone help me change it so it can work right (that is if its the reason it doesn't work)
It shouldn't as your CFW supports firmware 13.X but if you're so worried about updating, then you don't need to update. No games require firmware 13.X and the only feature added is Bluetooth support.If I update my Atmosphere cfw partition to be on 13 will it mess with my carts format/ would I need to redo the entire dual booting process again? I'm asking because I don't want to lose anymore gigs on my card, I already lost almost 90 gigs and can't get them back (right now).
No, Atmosphere updated the names of some of their components. Fusee-secondary.bin was renamed to package3 which is what your error is about. Rename fusee-secondary.bin to package3 in your hekate_ipl.ini fileRead somwhere don't remember where
that this error
Error while loading fss0:
atmosphere/fusee-secondary.bin
Wrong ini cfg or missing/corrupt files!
Failed to launch HOS!
and the Failed to run tsec_keygen firmware error
is because AMS from 1.1.0 not is compatible with devices running with SX core.
Is this right and if so will there be a fix soon?
Well emuMMC and sysMMC share the same certificate for going online so any information that emuMMC transmits online is information that would also be tied to sysMMC's certificate.Hey, this is such a noob question, but: i‘ve been playing an nsp game on my emummc(has a linked nintendo account), always using 90DNS, but it shows 20hours played on the game on the profile information. If I were to connect accidentally my emummc to Nintendo servers, could those informations be registered on the sysmmc ? Thx











