I want to backup an Atmosphere partition emuMMC and restore it to another SD card. First I saved the emuMMC as Atmosphere file variant on the PC. This also worked so far. Afterwards I prepared the new SD card with Mini Tool PW and then restored the previously saved emuMMC on the unformatted partition intended for the emuMMC data and reactivated it via Hekate. But it doesn't boot. What could be the reason?
In addition, I think the structure of the stored Atmosphere nand Image files is that of the SX OS (10 files). Wouldn't it have to be 17 files?
View attachment 187163
EDIT:
I have a guess why the emuMMC doesn't boot! The emuMMC partition is created on the back of my SD card. An emuMMC created by Hekate can read a partition that was created on the SD card at the back as well as at the front. The SX OS on the other hand can only read a front created partition.
But since the backup created with EmuTools v0.2.7 is an SX OS file variant, although it should be the Atmosphere file variant by selection, it is also restored as an SX OS partition. But since SX OS can only recognize the partition if it is on the front of the SD card, the emuMMC does not boot either.
But even if a SX OS File Backup was created (although it should have been an Atmposphere File Backup), this shouldn't really matter, because
Atmosphere hidden Partiton was chosen as the target for the recovery, which doesn't seem to be the case either. Possibly v0.2.7 contains a bug that only performs SX OS based operations.
View attachment 187202
There are no difference between Emunand, emuMMC and hekate backup, they are all a byte copy of your nand, splitted in various ways.
You can boot an SX partition with Atmosphere simply using 0x2 as starting sector in emummc.ini file.
EmuTool didn't apply any trasformation to the data.
About your question of the 17 files, Atmosphere can read a file emu splitted in quite every way, but I used the same size that hekate use when it create a file Emu from emummc menu.
My last test before releasing 0.2.7 was from SX emu on file restored to an SX emu on partition, than dumped to Atmo files and at the end restored to Atmo partition and all 4 of them booted succesfully (all directly on SD card without passing from Hard Disks or other support)
Does your dumped files boot as emu on file with Atmosphere? (very slow compared to partition emu in Atmosphere)
I think the problem was generated when you tried to reactivate the new Emu via Hekate, two consideration about that:
1- there is no need to activate the emu, the generated emummc.ini file is ready to boot
2- even if EmuTool replicate exactly the folder structure, the file raw_based is ok and Atmosphere boot the emu correctly, sometime hekate is not able to recognize the emu in emuMMC selection menu, so you are not able to activate it from the menu if you deactivate it.
If you use the emummc migration feature of the hekate menu, most of the time it resolves.
I'm currently working on it.
Now, to not do the whole procedure again, first try with the migration tool in hekate menu, remember to copy your original emummc Nintendo folder.
If this not solve please check on Minitool the properties of the partition you created and write me the starting block and SD total size.
Please write me also the content of you current emummc.ini file you can find in sdcard, inside emummc folder.
Ciao!