The only difference between these two configs is the one on the right has an additional config for Emunand (emuMMC). You would not have increased your risk any higher.So, I screwed up a little bit. I had on old emummc install that I couldn't get working quite right even after updating atmosphere, hekate, sigpatches etc. So I made a fresh install and offline updated it from 2.30 to 15.0.1. And THEN I realized that I had updated FSS0 SYS instead of emummc (I'm almost sure that the hekate.ini I downloaded from the NH Switch Guide was the culprit - when I went to download it again for a reinstall, it was back to its usual - see attached image for a comparison of the two files downloaded less than half an hour apart).
I've since redone the install and everything is working perfectly. But now I want to understand what I did. I don't get what FSS0 SYS is compared to stock SYS. Since I've apparently updated my Switch nand, now I just want to make sure, that It is clean to go online so I can buy and use online games on the stock nand (which has never been dirtied before) and keep emummc for everything else. Thanks.View attachment 354831
The only difference between Stock SYS and FSS0 SYS is the kip1 line.
https://github.com/CTCaer/hekate#boot-entry-keyvalue-combinations
kip1={FILE path} | Replaces/Adds kernel initial process. Multiple can be set. |
kip1={FOLDER path}/* | Loads every .kip/.kip1 inside a folder. Compatible with single kip1 keys. |
Unless you’ve added nefarious kips to your kernel you will be fine.