If I never booted sysNAND after hacking my Switch, wouldn't I be able to make another unmodified NAND backup with hekate now? I mean I am just trying to understand the reason behind everything, consider me a bare noob regarding this matter.
Sorry, I may have misread your initial post. Based on your wording, I thought you were implying your sysMMC was tainted. If you never ran any sort of CFW or homebrew on it, then you don't have anything to worry about.
That's correct sir, I never touched my sysNAND again after making the backup first and then making an emuNAND since then, either with SX or hekate.
Well if you mean safely in terms of a ban, you already answered that by stating you never ran CFW or homebrew on your sysMMC. But if you meant safely in terms of a potential brick, you could just update online since Nintendo's official update method couldn't possibly have brick code in it.
Unfortunately this is where my lack of knowledge shows as I am not incredibly familiar with the SX modchip. All I do know is that the chip modifies some files in your console that can only be removed with the cleanup option. I don't know of the technical process to boot sysMMC cleanly from a chipped Switch after performing the cleanup step. I even have a sneaking suspicion that the OFW option from the SX menu is not as clean as it appears since there have been people banned after using it.
And what would be my alternative? I mean that's pretty rhetorical, it would be hekate then, but how exactly would I boot to sysNAND from hekate? Or would you say I am generally potentially f-ed because I had to chip my Switch?
That is also hard for me to answer because most of my banning information comes from consoles hacked via Fusee Gelee. Banning statistics dropped after the release of emuMMC and by the time the SX Core/Lite came out, I was lucky to receive a ban report at all. Theoretically speaking, the cleanup option from the SX menu combined with the trusted Hekate Stock mode should be safe.
Sorry that I reply so often but as I said before I rather am safe than sorry.
How is it a pain? USB installs are arguably better than installing stuff from the SD card and exFAT can corrupt your SD card so FAT32 is superior with that fact alone.
Cleaning the SD card is irrelevant. Scanning for files on the SD card is known to be pointless because not only can it lead to false positives but it is also potentially illegal. But can you not boot into Hekate without powering down the console after using the cleanup function from the SX menu?
Even though the chip takes a lot longer to boot (due to the clean up) I would be able. Now mentioning it a second question even arises:
As I've stated previously, I have evidence to believe it is not as clean as TX may have made it. People getting banned for using it is sufficient proof for me to not recommend anyone to use the SX OFW option. As for Hekate, if you have a Stock launch profile already, then you're set. Otherwise, you will either have to manually make one yourself or download a pre-configured hekate_ipl.ini fil with that launch profile. You can obtain pre-configured hekate_ipl.ini files from SDSetup or DeepSea.
Do not worry about asking me questions. I am more than happy to answer as many questions as you have.
Splitting files is only relevant for mounting .XCI files which you can only do with SX OS and that hasn't received support in over 3 months now with no chances of future support. .NSP files can also be split but the superior method of installation is via USB. You can also install .NSP files larger than 4 GB on FAT32 with network installation although this one isn't as fast as USB install.
Was not worried about the space, still hyper-cautious to whereas they might scan files anyway haha.
emuMMC is like owning a second Switch except they share the same hardware. This translates into emuMMC operating as a brick shield if you use it exclusively for CFW/homebrew or as a way to be on higher firmware versions without actually updating the firmware of your console. Its purpose is NOT to be used offline; that is simply what everyone does. In fact, emuMMC is designed for going online because there is an exploit that works on 4.1 and below. In order to ensure you have access to the exploit, you cannot update the console's firmware but you cannot go online without updating the firmware. This is where emuMMC proves useful because the firmware of the emuMMC does not affect the firmware of the sysMMC. That being said, if you do not want to get banned, you can only ever go online with sysMMC or emuMMC and not both.
@
Psionic Roshambo:
@
Julie_Pilgrim:
@
Sonic Angel Knight:
