i still persist in using exfat not fat32, sometimes use another fat32 sdcard for cheat data searching. but i don't think nintendo will add ntfs support maybe they consider sdcard is flashdisk not HDD。
just a sample that i used. from deepsea 3.2.0 (atmosphere 1.1.1 + hekate 5.6.2)
the "logopath=xxxxxx" is not necessary , don't forget add sigpatch bootloader/patches.ini
[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
{}
{www.91wii.com}
{}
[DS-CFW...
i update sysnand in stock booting and use tegraexplorer to dump the latest firmware. then update emunand via daybreak. But first we have to wait for the new atmosphere version released that supports latest HOS
hope the imitation modchip's price would be less than 200 RMB in this year.
auto
yes, some people have been prosecuted for soldering modchip in switch,
for example, a gaming store was imposed a fine by local court around 200,000 RMB a couple of months ago.
cut emunand's size with nxnandmanager software on ur desktop. after resize your emunand and save as a clean trimmed emunand. It is very convenient to restore it when you need.
no one can trigger the soft exploit above firmware 4.1, means still based on RCM exploit or SX core/lite exploit.
if you console has RCM exploit. you can take a modchip in it , the name is RCM x86 or named SAMD21 on market.
auto
you must trigger the exploit on your switch before using cfw...
yes, that's exactly right what i always recommend others to backup a clean nand before jailbreak.
still someguys didn't and they don't know how to use memloader and hacdiskmount. even they forgot backup console's biskey.
so the haku33 is a better way to clean nand compare those a little bit...
i saw maybe you are using windows in mac. check usb driver compatible problem. or you can choose to payload with android phone. need a otg adapter in addition.
holding power button above 15 seconds to shutdown and try it again.
don't forget charging full battery before working.
i am not sure wether there is a hardware problem in your switch.
auto
if you restored boot0/1 not paired Hos version with current system , it could be brick.
for example...
did you made emunand before? if not. you can choose to restore clean nand (only your switch's nand backup) or runs haku33 to elimination was pulluted data in current switch's nand.
use choidujournx to upgrade or downgrade for emunand are both safe. but don't use it in sysnand because patched switch and mariko's can't ingore efuse which it means look like a brick.
i thought you should go visit www.91wii.com can slove the simple problem.
unpatched switch can use the RCM exploit with any appropriate payloads except you did something wrong.
check bootloader/hekate_ipl.ini and maybe autoboot=1 so could entry hekate's recovery mode menu.
is it right in patch.ini?
#Loader Atmosphere-0.16.0-p2
[Loader:81530982b7d79dbc]
.nosigchk=0:0x6D9A:0x1:01,00
#Loader Atmosphere-0.16.1
[Loader:eac30efb8b99ad10]
.nosigchk=0:0x6DEA:0x1:01,00