Useless post. I know what an emunand and sysnand is. Question is what the user below you answered.
Post automatically merged:
So fusee.bin knows that when it is ran it has to check for emunand? If so that is absolutely amazing and whoever developed that payload is an intelligent individual. So I assume emummc_force_disable is what tells hekate to use the sysnand instead?
Is there any benefit to switching from what I have now:
[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp
to this?:
[CFW - emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp
{--- Custom Firmware ---}
[CFW (SYSNAND)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummc_force_disable=1
icon=bootloader/res/sysnand.bmp
{}
[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/emummc.bmp
{}
Based off this, if a user had a emunand, the top one allow the user to boot into CFW Sysnand, and the bottom one allow the user to boot into Emunand CFW,
If the person wanted to boot into stock OFW, no CFW
[Stock SYS]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock_boot.bmp
Really no major benefit, just the emummc_force and stock=1 tell hekate what to use.