Hacking EmuMMC not showing SD card space in full

  • Thread starter Thread starter evertonstz
  • Start date Start date
  • Views Views 5,704
  • Replies Replies 8

evertonstz

Well-Known Member
Member
Joined
Jan 5, 2019
Messages
209
Reaction score
133
Trophies
0
Age
32
XP
589
Country
Brazil
EDIT AGAIN: problem not solved actually, I'm open to sugestions

-----------------------------
SOLVED (NOT ACTUALLY): be aware, the guide has wrong information in the dd part:

sudo dd if=/dev/zero of=/dev/sd-# seek=29854 bs=1M count=1 status=progress
the seek part should only be 29854 if your SD card is 32GiBs, for any other SD size you have to insert the last sector, you can see the last sector in your last partition.
--------------------------------------------
original post:

I've followed this guide for linux: https://switch.homebrew.guide/emummc/linux

Basically: created two partitions, one fat32 that's about 512MiB and the rest of the cart was also fat32 and zeroed the zones as explained in the link. The problem: the SD space in the console shows 425MiB (I suppose this is the partition I've created), and the internal memory shows only 25GiB, my SD is 128GiB, so it should be around that. Any ideas?

On my PC the partition's space is shown 118,68 GiB, so I know it was formated correctly.
 
Last edited by evertonstz,
I've followed this guide for linux: https://switch.homebrew.guide/emummc/linux

Basically: created two partitions, one fat32 that's about 512MiB and the rest of the cart was also fat32 and zeroed the zones as explained in the link. The problem: the SD space in the console shows 425MiB (I suppose this is the partition I've created), and the internal memory shows only 25GiB, my SD is 128GiB, so it should be around that. Any ideas?

On my PC the partition's space is shown 118,68 GiB, so I know it was formated correctly.
Why do you want to partition the entire card as emuNAND? There is no point to doing this. 512MB is very little space and you may want to put some emulators and ROMs on there or something, which can only load from the SD.
Hekate AFAIK just flashes the NAND raw data to the partition, if the partition is bigger it won't automatically resize the NAND, you have to do that manually.
 
Last edited by The Real Jdbye,
Why do you want to partition the entire card as emuNAND? There is no point to doing this. 512MB is very little space and you may want to put some emulators and ROMs on there or something, which can only load from the SD.
Hekate AFAIK just flashes the NAND raw data to the partition, if the partition is bigger it won't automatically resize the NAND, you have to do that manually.
I'm just following the guide, tbh. Btw, tought I had solved the problem, but it's not solved, do you have any other guide for emuNAND? I literally got the console today and this is tbh quite confusing.
Where I can resize the NAND?
 
Last edited by evertonstz,
I'm just following the guide, tbh. Btw, tought I had solved the problem, but it's not solved, do you have any other guide for emuNAND? I literally got the console today and this is tbh quite confusing.
Where I can resize the NAND?
The guide is a bit poorly explained. You should set "Free space following" to 29856 on the first partition. Don't change the size, let it fill up the rest of the card. And the second partition should be size 29856.
 
The guide is a bit poorly explained. You should set "Free space following" to 29856 on the first partition. Don't change the size, let it fill up the rest of the card. And the second partition should be size 29856.
Now I'm more confused. What you told me gave me two partitios: sdb1 with 90 GiB and sdb2 with 29,16GiB. I suppose sdb2 will be the emuNAND and shown in the system as Internal Memory and sdb1 will be shown by the system as SD, right?
 
Now I'm more confused. What you told me gave me two partitios: sdb1 with 90 GiB and sdb2 with 29,16GiB. I suppose sdb2 will be the emuNAND and shown in the system as Internal Memory and sdb1 will be shown by the system as SD, right?
That's exactly how it's supposed to be.
 
  • Like
Reactions: evertonstz
You followed the guide wrong. In GParted you were supposed to put 29856 in "Free Space Following."

Following that guide puts the EmuMMC at the END of the SD card. Alternatively, you can put it at the beginning instead. I prefer it that way, to me it's easier to work with if you later decide to upgrade your SD card.

For more info, you could check out this post: https://gbatemp.net/threads/emummc-setup-win-linux-quadboot.541152/page-4#post-8682981

Basically, I create my ~30gb partition at the beginning of the SD card, and then a second partition covering the rest of the sd card. In this case, you'd take a NAND backup made by Hekate, and DD it over your sdb1. Afterwards, to prevent the Switch from trying to mount sdb1 as a FAT32 partition, potentially corrupting your emuMMC, simply delete the partition. The data will stay there.
 
You followed the guide wrong. In GParted you were supposed to put 29856 in "Free Space Following."

Following that guide puts the EmuMMC at the END of the SD card. Alternatively, you can put it at the beginning instead. I prefer it that way, to me it's easier to work with if you later decide to upgrade your SD card.

For more info, you could check out this post: https://gbatemp.net/threads/emummc-setup-win-linux-quadboot.541152/page-4#post-8682981

Basically, I create my ~30gb partition at the beginning of the SD card, and then a second partition covering the rest of the sd card. In this case, you'd take a NAND backup made by Hekate, and DD it over your sdb1. Afterwards, to prevent the Switch from trying to mount sdb1 as a FAT32 partition, potentially corrupting your emuMMC, simply delete the partition. The data will stay there.
A possibly better (at least easier) way to do it if you want to have the partition at the beginning is to just use SX OS to format the emuNAND, then the emuNAND will be at the beginning and in SX OS compatible format (but still detected by Hekate and usable just fine with Atmosphere)
 

Site & Scene News

Popular threads in this forum