So I goofed tonight. LOL. I was wanting to mess around with Amiibo stuff and decided to see if Tinfoil had any of them. I am using Hekate to launch Atmosphere. I know Tinfoil doesn't play nice with it, but I used Cling Wrap the other day to successfully grab an update I couldn't get elsewhere so I tried using Tinfoil again. Tinfoil wouldn't launch so I decided to reboot my Switch, but stupid me didn't think about the fact I'd used Cling Wrap to rename folders, so my SD card tried to launch with the renamed folders (bootloader) and (atmosphere/kips) (it didn't work).
I tried renaming the files using my PC, but I think I messed something up with Hekate when I did that. RCM still works so I launched into fusee primary to try and resolve the naming issue. I was able to get into Atmosphere to delete the folders Cling Wrap renamed (using Goldleaf) and deleted the hekate file in the renamed b00tloader file that Cling Wrap created. I then tried to relaunch using Hekate.
The Hekate payload successfully launches, but when I click the "Launch" option from the Hekate menu, it says there are no configurations there (I don't remember the exact wording, but I can try and update this once my SD card is finished backing up). I'm currently backing up my entire SD card so I hopefully don't mess anything else up any worse than I have.
I think what is happening is that when I launch Hekate it's not able to see the emummc I have been using, even though it's on the SD card. I compared the original Hekate folder I got from this forum's homebrew setup link and the config file is different than what I currently have on my SD card. The config for hekate_ipl from the software package I got from the guide is as follows:
[config]
autoboot=0
autoboot_list=0
autohosoff=1
autonogc=1
backlight=100
bootwait=3
updater2p=0
[CFW (sysMMC)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
icon=bootloader/res/icon_payload.bmp
[CFW (emuMMC)]
emummcforce=1
fss0=atmosphere/fusee-secondary.bin
icon=bootloader/res/icon_payload.bmp
[Stock]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
icon=bootloader/res/icon_switch.bmp
stock=1
[Fusee]
icon=bootloader/res/icon_payload.bmp
payload=bootloader/payloads/fusee-primary.bin
The config for the hekate_ipl currently on my card is as follows:
[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0
I'm not too tech savvy, but the main differences I see are that the config on my SD card right now has bootprotect=0 listed and the config on my SD card is also missing the text at the bottom that seems to point to the boot options (CFW sysMMC, CFW emuMMC, etc.)
I can browse my SD card and see the emuMMC folder, so I guess that's a positive sign, but I have no idea how to get Hekate to launch into it from the Hekate menu. When I load fusee primary from the Hekate payloads option I can get into atmosphere but none of my backups are working. I do know that Cling Wrap also renames the atmopshere/kips folder, so maybe it has something to do with that?
UPDATE 1: I just moved the hekate ini file from the sigpatch update to my SD card and it's now displaying emuMMC in the launch spot, but I'm getting a corrupt data error. Should I just reinstall all my backups that have the error message? There's a little exclamation point above several games. I used the updated sig patch data, so I guess the best solution is just to reinstall?
UPDATE 2: I ran the check for corrupted data and a couple game said "corrupted data found" and prompted me to redownload. When I tried launching the games after that, they worked.
Looks like my issue is resolved, except for Amiibo stuff. Just wanted to leave this post up in case anyone wants to explain what likely happened in so I don't make the same mistake again. MODS: if you want to delete the post, please feel free to do so.
I'd be eternally grateful for some help with this. I hope the solution is as simple as clicking a restore emuMMC button in Hekate, but I'm not too sure. Thanks in advance for your help and patience!