Whoops, I forgot CAL0 was PRODINFO...
No, you have it right; it really is as simple as copying & pasting the files from one card to another. And the biggest size the Switch accepts is 2 TB which doesn't exist as of yet.
You can copy the saves but its not entirely safe to do so since the dates & such won't match so it might flag a ban. Also if you want to transfer DLC from your sysMMC to emuMMC, that would involve using homebrew which would then put your sysMMC at risk for a ban. Alternatively, you can remake the emuMMC after downloading the DLC on sysMMC but that would be a cumbersome process especially if you have to do it every time new DLC comes out.
There is a guide for retrieving games from emuMMC although I don't know how much luck you will have if its corrupted since if that's the case, the saves would be corrupted as well but its worth a shot.
Ah ok. I have a sneaking suspicion tho, that it's only hekate not working well regarding CAL0.
Based on my data, Hekate's Stock option is safer than SX' OFW option although that may be due to the fact that piracy was more easily accessible with SX OS than Hekate so it may have skewed the numbers but since Hekate not only predates SX OS but has received constant support, its not that far-fetched of a belief.
I updated it successfully several times before bumping into this error. It worked after the update, but then it got stuck on the boot screen one day. I assumed it was me doing something wrong (such as mixing up payloads, etc), as it happened a month prior, but this is not the case...
What versions are you on (FW, Atmo, Hekate) and what does your hekate_ipl.ini look like?
FW: 13.2.1, hekate: 5.7.0, atmo: 1.2.6
[config]
autoboot=0
autoboot_list=0
bootwait=0
verification=1
backlight=100
autohosoff=0
autonogc=0
updater2p=0
[Atmosphere - sysMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp
[CFW - emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummcforce=1
icon=bootloader/res/icon_payload.bmp
[Original - sysMMC]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp
i need to get this right because my fuses are ok for my 7.0 backup and I hear that in the future it may lead to getting the best features.
Launching with the stock Switch bootloader is what causes fuses to be burnt. In laymen's terms, booting the console normally will burn fuses. Hekate is a custom bootloader so it will not burn fuses unless either the developer accidentally reverts that or someone else creates a Hekate lookalike that burns fuses.
so auto rcm protects my fuses at all times. Just keep it on and hekate can boot OFW than do NSO FW updates eshop and game updates right.
My second paragraph explains the issue; your emuMMC has a blank Nintendo folder by default. The Nintendo folder used by sysMMC isn't copied over when emuMMC is created. I listed the potential fixes. And the reason cartridge games work is because those are not installed to the system.
before I set up emunand I had system memory and sd card memory. I understand what your saying applies to the games on SD card in the Nintendo folder. But isn’t it different for the games that were in system memory? When I migrated to emunand shouldn’t the games that were in system memory still work even with out the Nintendo folder? The cartidge games that work are ones that were dumped to system memory.
| atmosphere=1 | Enables Atmosphère patching. Not needed when fss0 is used. |
The Real Jdbye
@
Psionic Roshambo:
@
Psionic Roshambo:
@
BigOnYa:
@
Psionic Roshambo:
@
Psionic Roshambo:
@
Psionic Roshambo:
