Anybody else having trouble booting their system after upgrading to Atmosphere 0.13.0?
So, I just recently upgraded to the latest version of Hekate (5.3.0) where it works just fine when the console was still on Atmosphere 0.12.0. But after using the files for Atmosphere 0.13.0, it no longer boots beyond the Hekate part of the chainload booting process.
System firmware: 10.0.2
Are you using the latest sigpatches?I had this problem, It didn't matter what I tried I didn't get it to boot, I tried what @Lacius suggested and still nothing. I reverted back to 0.12.0 now some of my games don't work.
I had this problem, It didn't matter what I tried I didn't get it to boot, I tried what @Lacius suggested and still nothing. I reverted back to 0.12.0 now some of my games don't work.
Are you using the latest sigpatches?
What happens?
- Make sure the SD card is FAT32.
- Remove all CFW files/folders from your SD card (that would be folders like /sept/ and /atmosphere/)
- Download the latest Atmosphere
- Download the latest fusee-primary (next to Atmosphere)
- Download these signature patches if you're using Atmosphere 0.13
- Put Atmosphere and the signature patches onto your SD card
- Put the SD into your Switch
- Enter RCM
- Launch Atmosphere using fusee-primary (not Hekate)
If you want to continue using Hekate, make sure you chainload fusee-primary properly. Otherwise, those patches won't work. Hekate requires separate patches, and it's not recommended.I was when I tried 0.13.0, then I reverted back to 0.12.0 and some games didn't work, so I used the previous sig patches and still, some games work some don't
Ok, I did this and it works now, only before when I restarted the switch I would go straight to Hekate now it just restarts EmuMMC.
If you want to continue using Hekate, make sure you chainload fusee-primary properly. Otherwise, those patches won't work. Hekate requires separate patches, and it's not recommended.
How do you Launch fusee-primary without Hekate?
Are you using an RCM loader?How do you Launch fusee-primary without Hekate?
You can also replace reboot_payload.bin in the atmosphere folder with the hekate payload (rename it to reboot_payload.bin). The restart option simply loads that payload.Excuse my ignorance but how do I do that? Everything is working now either if I load just with Hekate or the way you suggested (Fusee-Primary) I would like to have the option to restart into Hekate menu since I have 2 EmuMMC's (one for backups and one for online) how do I do that?
Edit: I got it to restart into Hekate by turning "Update Reboot 2 Payload" On
So, I just tried this method. While it managed to get past the Hekate part, it got stuck after the Atmosphere logo.
- Put fusee-primary into the ‘/bootloader/payloads’ folder on your SD card.
- Enter Hekate
- Select ‘Payloads’
- Select fusee-primary
The sigpatches aren't compatible with 0.13.0 yeti have a issue but with just with pokemon sword, the game crashes just after past the titile screen is so weird because other people can run the game properly, and is not my nsp because in Atmosphere 12 works i have the sigpatches and all for Atmos 13 but i couldn't make it work (i made a clean install and all) i think i´m gonna stay at 12 for now because i play a lot Pokemon recently-
The sigpatches aren't compatible with 0.13.0 yet
Are you using the latest version of fusee-primary?So, I just tried this method. While it managed to get past the Hekate part, it got stuck after the Atmosphere logo.
Meantime, I will be reverting back to Atmosphere 0.12.0 again to temporarily offset the issue.
Are you booting with fusee-primary, or are you booting with Hekate?i have a issue but with just with pokemon sword, the game crashes just after past the titile screen is so weird because other people can run the game properly, and is not my nsp because in Atmosphere 12 works i have the sigpatches and all for Atmos 13 but i couldn't make it work (i made a clean install and all) i think i´m gonna stay at 12 for now because i play a lot Pokemon recently-
What happens when you boot with fusee-primary without Hekate?got an error after sept logo "0100000000000003" (chain load from hekate) any idea?
Took the chance and no sys-module was broken after updating to 0.13.0.Does 0.13.0 break compatibility with any sys module?