Hacking Question File Based EmuMMC

[Dave_Chad]

Just wondering if anyone has it working correctly yet? Not seen confirmation, only of the partition based one.

I have emummc.kip in the atmosphere folder. I have emummc folder with my nand files in. (boot0, boot1 and 00) I have emummc.ini with,

[emummc]
emummc!emummc_enabled = 1
emummc!emummc_path = atmosphere/emummc
emummc!emummc_id = 30

I have booted Hekate and done the fix archive bit part too.

I just boot into standard nand.

EDIT: I am aware they said wait so i don't need telling that...this is a hobby i find it fun.

 

[Shadow#1]

Just wondering if anyone has it working correctly yet? Not seen confirmation, only of the partition based one.

I have emummc.kip in the atmosphere folder. I have emummc folder with my nand files in. (boot0, boot1 and 00) I have emummc.ini with,

[emummc]
emummc!emummc_enabled = 1
emummc!emummc_path = atmosphere/emummc
emummc!emummc_id = 30

I have booted Hekate and done the fix archive bit part too.

I just boot into standard nand.

EDIT: I am aware they said wait so i don't need telling that...this is a hobby i find it fun.

Just wait

 

[Dave_Chad]

Just wait

Thank you for your well thought out and informative reply. My simple question was answered.

 

[Jayro]

I'd be on board with doing emummc using a "files and folders" method instead of one huge partition/one huge file. The DSi and Wii useds files and folders, so I'm sure the Switch can too.

 

[Muxi]

I hope it's ok that I put my request here, since it's about the file based emuMMC.

It should be possible by now to create a file based emuMMC via Hekate, which is nearly as fast as the partition variant. I already use a partition emuMMC, but I wanted to test it anyway. Are there any requirements for booting this emuMMC? Because when I tried to boot it via fusee-primay (AMS 0.13.0) it ends up in a black screen with strange characters. I had experienced something similar with AMS 0.12.0 before, but here the emuMMC up to FW 8.1.0 was still booted (very slowly) and with higher FW versions it came to a black screen. Or can this emuMMC only be booted via Hekate?

Short summary:

file based emuMMC FW 10.0.4 created via Hekate v5.2.1 --> cannot be booted via fusee-primary (AMS 0.12.0) ---> black screen

file based emuMMC FW 10.0.4 created via Hekate v5.3.0 --> cannot be booted via fusee-primary (AMS 0.13.0) ---> black screen witch strange characters

partition emuMMC FW 10.0.4 created via Hekate v5.2.1 / v5.3.0 --> can be booted without problems via fusee-primary (AMS 0.12.0 / 0.13.0)

 

[tataniko]

@annson24 & @Muxi

This works well for fast file based emuMMC.
Check it yourself.

 

[Muxi]

This works well for fast file based emuMMC

Thanks, but isn't that the data of the official AMS release of v0.12.0? If I go by the version number, this is the same one I used (before v0.13.0).

 

[tataniko]

Thanks, but isn't that the data of the official AMS release of v0.12.0? If I go by the version number, this is the same one I used (before v0.13.0).

The officials don't work yet. This is a fork of AMS 0.12.0, fusee-secondary by Kronos2308, which is working. I use it on firmware 10.0.2 for fast file based emuMMC. At least, this works on 10.0.2.

 

[annson24]

@annson24 & @Muxi

This works well for fast file based emuMMC.
Check it yourself.

Thanks, but isn't that the data of the official AMS release of v0.12.0? If I go by the version number, this is the same one I used (before v0.13.0).

@tataniko I believe this build is prior to the v0.13.0 but after the commit on the new emummc driver, correct? If so, this would be good for the time being until a fix has been made on the official build.

@Muxi replying to your post about ams v0.12.0 not booting file-based emummc; I believe it does boot the emummc, it's just super slow that it will take a few minutes before showing the nintendo logo.

 

[Muxi]

it's just super slow that it will take a few minutes before showing the nintendo logo.

This was the case with ams up to and including v0.12.0 and only up to a file based emuMMC on FW 8.1.0. Everything beyond that I could not boot. A retry of the setup under Hekate 5.3.0 and subsequent booting via fusee-primary (ams 0.13.0) resulted in a black screen with strange characters on the right side of the screen. This emuMMC was created from a sysMMC on FW 10.0.4.

However, this emuMMC can be booted via Hekate and is also nearly as fast as the partition variant, but it does not work via fusee-primary. The composition of my CFW still requires booting via fusee-primary, otherwise I could just boot via Hekate.

 

[tataniko]

@tataniko I believe this build is prior to the v0.13.0 but after the commit on the new emummc driver, correct? If so, this would be good for the time being until a fix has been made on the official build.

Yes, that build has the new fast FS for file based emuMMC, I use it for a month via fusee-primary. I created a reduced size (4gb user partition) file based emuMMC from NAND backup with NxNandManager by eliboa. It works very well.