Booting up on emummc CFW but console reading the internal console System Memory instead

[mickael28]

Hiya, I had a Switch without a microSD card and installed a bunch of games onto its default internal System Memory.

After that, I put a microSD card, created a partition for emummc and booted up from that as the CFW.

By reading other posts, I was expecting to have an almost empty "System Memory" of ~30GB (which was the space I choose for this emummc partition), however I've currently got only 6GB left which is what I had in the console internal system memory instead.

I was not expecting any of the games I installed in the console originally to be visible when booting up on the emummc CFW, however, this seems to be the partition that's visible to me and I can even launch and play those games.

I've launched the other Hekate option with sysMMC CFW option for a comparison and I cannot see any difference when compared to emuMMC. Other than the S or E, they both can see the games installed in the stock internal memory.

Any idea why this could be and how could I see the real emummc partition with its 30GB instead?

Post automatically merged: Jul 3, 2024

Another couple of comments:

1- when I boot on the stock FW, I can see all the games I installed whilst I was on the emuMMC CFW on the microSD card too.

2- while on the emuMMC CFW, I deleted one of the games that was appearing on the 'System Memory' and it deleted it from both, the emuMMC CFW and from the stock FW's System Memory as well

 

[Deleted member 702243]

because emummc is a copy of real emmc, including all games and updates/dlc that were on it

just go in data management and uninstall everything you dont need, from the emummc side

 

[Hayato213]

Check your system string, if it says E then you are on emunand.

 

[mickael28]

Thanks, understood the par that emuMMC was a copy of real emmc. But it seems to be somehow misbehaving and mixing both up.

1- I'm on the E system, but if I delete a game from this emuNand, it gets deleted in the real stock system as well (which I don't think it should be happening)

2- All games I've installed in EmuNand, get listed as well on the Stock (eg, Tinfoil itself) which I don't think should be listed there at all?

Not sure where the mix up is coming from or how to solve it because I've redone the setup a few times and double checked all config and in theory it all looks ok, although then it misbehaves with those 2 issues

 

[Hayato213]

Thanks, understood the par that emuMMC was a copy of real emmc. But it seems to be somehow misbehaving and mixing both up.

1- I'm on the E system, but if I delete a game from this emuNand, it gets deleted in the real stock system as well (which I don't think it should be happening)

2- All games I've installed in EmuNand, get listed as well on the Stock (eg, Tinfoil itself) which I don't think should be listed there at all?

Not sure where the mix up is coming from or how to solve it because I've redone the setup a few times and double checked all config and in theory it all looks ok, although then it misbehaves with those 2 issues

You probably don't have an emunand, you probably confusing sysnand CFW with stock Sysnand, if you separated them correctly Sysnand and Emunand doesn't touch each other.

 

[mickael28]

You probably don't have an emunand, you probably confusing sysnand CFW with stock Sysnand, if you separated them correctly Sysnand and Emunand doesn't touch each other.

I created one on a partition and then I enabled it and it seems to be working fine. It was displaying the E string under system settings too after booting it.

That seemed ok, other than the games were then all mixed up.

I'm redoing the whole setup again, deleting all partitions, etc and will retry in the coming days.

I'll put an update when done to either say it worked on another attempt or to ask for any other ideas, thnks guys

 

[impeeza]

Hiya, I had a Switch without a microSD card and installed a bunch of games onto its default internal System Memory.

After that, I put a microSD card, created a partition for emummc and booted up from that as the CFW.

By reading other posts, I was expecting to have an almost empty "System Memory" of ~30GB (which was the space I choose for this emummc partition), however I've currently got only 6GB left which is what I had in the console internal system memory instead.

I was not expecting any of the games I installed in the console originally to be visible when booting up on the emummc CFW, however, this seems to be the partition that's visible to me and I can even launch and play those games.

I've launched the other Hekate option with sysMMC CFW option for a comparison and I cannot see any difference when compared to emuMMC. Other than the S or E, they both can see the games installed in the stock internal memory.

Any idea why this could be and how could I see the real emummc partition with its 30GB instead?

Post automatically merged: Jul 3, 2024

Another couple of comments:

1- when I boot on the stock FW, I can see all the games I installed whilst I was on the emuMMC CFW on the microSD card too.

2- while on the emuMMC CFW, I deleted one of the games that was appearing on the 'System Memory' and it deleted it from both, the emuMMC CFW and from the stock FW's System Memory as well

you are not booting on the emuMMC, you are booting on SysNAND using CFW.

 

[mickael28]

Having a further look into everything, reinstalling apps and changing configs.

I was on Hekate 6.1.1 and my console had updated to the latest official FW 18.1.0

The issue kept on happening until I upgraded to hekate v6.2.1 & Nyx v1.6.3, I've not used it much yet but now it seems both sysNand and emuNand are different. With 6.1.1 the content was still appearing like shared across all CFWs/Stock.

So if anyone has a similar issue.

My FIX: upgrade to latest hekate/nyx