- Thread starter Mythrandir
- Start date
- Views 13,575
- Replies 29
I figured it out. Don't use dd. Partition the end of the sd card and create emummc on that. Then partiton again closer to the start of the sd, and create another emummc. It selects the first partition of matching size.
Now I need to know how to boot emummc without cfw for stock emummc.
Now I need to know how to boot emummc without cfw for stock emummc.
Why not use dd?
I don't understand exactly what you mean by "stock emummc", but I believe that my configuration is what you want:
- Make a backup of your NAND using Hekate or use an old backup, and then join the files as I explained in the previous post
- Create three partitions on your SD card. The first will be your SD card data, wich should be in FAT 32. The other two can be anything BUT UNALLOCATED.
- First dd your emummc.bin to the last partition (THE THIRD ONE), using Gparted Live or you software of choice. Once finished, insert the SD card into the Switch, start Hekate and choose the "Migrate emummc" option. So you will have RAW2 available. If you dd'ed your clean NAND backup this will be your "stock emuMMC".
- Now click on "Create emummc". Hekate will find the first available partition (THE SECOND ONE), and will create RAW1, a direct copy of your real sysnand.
In my case (stock firmware = 1.0.0) I turn on the Switch, then use the "Reswitched" link in the News (installed by Fake News) to start PegaScape, and finally select Nereba to take me to Hekate.
Then I can choose among the emummc:
RAW1: "dirty", updated by ChoiDujourNX
RAW2: "clean", updated by official servers
Got it?
Last edited by kassio69,
i have missed one step ... we need to change foldername raw1 to raw2 after migrate and before install raw 1
now i have 2 raw emmunands
3 partitions first fat32 second let it unlocated and the last one unformated now dd to the last unformated one
migrate emmunand via hekate make sure you have raw 2 now change the folder name from raw 1 to raw 2 Change the Name in the emunandconfig to RAW 2 now change unlocated partition 2 to unformated after that launch hekate install emunand as partition and you are should see raw 1 and 2 now
Last edited by loler55,
Why further complicate something that is already complicated?
Let's call "SD card data" partition 1, "emummc1" partition 2 and "emummc2" partition 3.
It is recommended to format partition 1 in FAT 32.
If you leave partition 2 unallocated and partition 3 unformatted + dd your emummc.bin to partition 3: Hekate will recognize it as RAW1 when you select "Migrate emummc", and then you will have to do all this renaming juggling.
If you leave partition 2 and 3 unformatted + dd your emummc.bin to partition 3: Hekate will recognize it as RAW2 when you select "Migrate emummc"
RAW1 then doesn't even have to be dd'ed, you can create directly from Hekate ("Create emummc").
Edit: I edited my previous posts, because I was saying to create two partitions, but I think that was confusing because there are three partitions in total (SD card data and two emummc)
Last edited by kassio69,
Hey @kassio69 ; it sounds like your setup is exactly what I’ve been looking for but I thought Hekate couldn’t boot a ‘stock’ emuMMC (as an official firmware for online, eShop etc.)
That must not be the case because it sounds like that’s exactly what you’re doing.
I’m currently running a ‘dirty’ SysMMC at 7.0.1 with a single EmuMMC (at 9.2.0) that I use for homebrew, etc.
Do you know how I could partition my card to keep my existing EmuMMC plus create another one (from my clean backup of 7.0.1) to use for online, etc.?
Hey!
I believe all you have to do is follow the steps I provided.
I edited my first post in this thread, now it's easier to understand.
1. Format your SD card and create three partitions, as previously indicated
2. dd your clean 7.0.1 nand to the third partition
3. "Migrate emuMMC": Hekate will recognize your now emulated clean 7.0.1 nand as RAW2.
If it is really clean you will be able to update using official Nintendo servers, and after that you should make a new backup and delete the old one.
4. "Create emuMMC": Hekate will create an emulated copy of your current sysnand (dirty 7.0.1) as RAW1, wich you should update using ChoidujourNX.
With your current real sysnand (if I understand correctly = 7.0.1 with burnt fuses) the best thing to do is to use a dongle to start Hekate, and then choose the desired emuMMC.
Don't update your real sysnand (only update your emulated sysnand), and hope for a DejaVu exploit for 7.0.1, which is theoretically possible.
In my case (1.0.0) I use Nereba, so I can turn on/off my console and don't need any dongle.
Last edited by kassio69,
OK @kassio69 , I followed your advice to get a 'stock' emuMMC in RAW2. I'm stubborn and trying really hard to keep my 'old' emuMMC for homebrew instead of creating a new one from my sysMMC. 2 questions for you:
1) In order to get Hekate to boot the 'stock' emuMMC in RAW2, it has to run it via Atmosphere. Does this not invalidate its status as a 'stock' MMC and make it detectable by Nintendo? For example when you go in settings to show the version, it includes an Atmosphere string.
2) Can you provide your (or an example) Hekate boot configuration and emuMMC configuration file to show how it handles 2 RAW partitions? Currently I have 2 working partitions and Nintendo folders but I don't know how to edit the 'SD\emuMMC\emummc.ini' file to work with 2 partitions. For example, here's my current file that points to RAW2 only:
[emummc]
enabled=1
sector=0x1a09e800
path=emuMMC/RAW1
id=0x0000
nintendo_path=emuMMC/RAW1/Nintendo
1) In order to get Hekate to boot the 'stock' emuMMC in RAW2, it has to run it via Atmosphere. Does this not invalidate its status as a 'stock' MMC and make it detectable by Nintendo? For example when you go in settings to show the version, it includes an Atmosphere string.
2) Can you provide your (or an example) Hekate boot configuration and emuMMC configuration file to show how it handles 2 RAW partitions? Currently I have 2 working partitions and Nintendo folders but I don't know how to edit the 'SD\emuMMC\emummc.ini' file to work with 2 partitions. For example, here's my current file that points to RAW2 only:
[emummc]
enabled=1
sector=0x1a09e800
path=emuMMC/RAW1
id=0x0000
nintendo_path=emuMMC/RAW1/Nintendo
First of all, I believe that you will not be able to create RAW2 without following my steps (that is, without deleting your current emuMMC).
Believe me when I say that I tried VARIOUS methods to get Hekate to recognize two emuMMC.
Stop being stubborn, you will simply have to copy the contents of your SD card to another location and then put it back. Use Checkpoint or something similar for saved games.
I'll copy/paste what I wrote in this post: https://gbatemp.net/threads/multipl...restoring-a-clean-nand-for-online-use.562188/
"In fact, even in the clean emunand Atmosphere is running in the background.
E.g. : If you check the version of your system the version of Atmosphere will appear next to it, you can access Hbmenu by holding R, and in my case even the BootSoundNX sound (sysmodule) plays at startup.
Simply running Atmosphere is no problem and does not generate a ban."
Now i don't understand .. do you have two partitions working or not?
If yes: Hekate > emuMMC > change emuMMC > select the one you want to use (no need to edit emummc.ini manually)
Anyway, here are my settings:
hekate_ipl.ini
[config]
autoboot=0
autoboot_list=0
bootwait=3
verification=1
backlight=100
autohosoff=0
autonogc=0
updater2p=0
[CFW (EMUMMC)]
fss0=atmosphere/fusee-secondary.bin
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
kip1patch=nosigchk
kip1=atmosphere/kips/ams_mitm.kip
{}
emummc.ini (it's directing to RAW2 because that's the last one I used)
[emummc]
enabled=2
sector=0x37f1d000
path=emuMMC/RAW2
id=0x0000
nintendo_path=emuMMC/RAW2/Nintendo
Last edited by kassio69,
Similar threads
