Hacking Question what is the best scenario for brand new unpatched switch with firmware 4.1.0?

[Goldenman66]

Actually, I seem to remember running into the same issue. Make sure that you're running it from an "elevated" command prompt with administrative privileges. I seem to remember my error having something to do with the way I was typing the command in. I could be wrong, but I "think" what I did to work around it was mount the emuMMC partition with a drive letter, and then pass that drive letter to dd rather than \\?\Device\HarddiskVolumeXX.

I did mine slightly differently because just as a matter of preference I like having my emuMMC partition at the beginning of the card instead of the end, but that requires deleting the partition afterwards and is a little advanced.

If I can find a spare microSD card laying around, I might try playing with that dd command some more just to verify what I did to get around that error message.

You're really close to having Atmosphere + emuMMC, don't give up yet!

yes i run it with administrative privilege from CMD and powershell and both didn't work

 

[Goldenman66]

finally i did dd command, i don't know how i got it worked after several trials formatting and re-partition ...etc it's work and copied emummc.bin file to sd card second partition. now i copied ams and hekate files to sd card but i'm confused should i create emunand from hekate menu or only launch it from hekate?

 

[RHOPKINS13]

finally i did dd command, i don't know how i got it worked after several trials formatting and re-partition ...etc it's work and copied emummc.bin file to sd card second partition. now i copied ams and hekate files to sd card but i'm confused should i create emunand from hekate menu or only launch it from hekate?

That's great! You've already created the emunand by running the dd command, you don't have to do anything special from Hekate. If you followed the instructions correctly, you should have a sector position, make sure your emummc config is set up correctly!

 

[Goldenman66]

what is the required configuration exactly? i copied hekate and atmosphere files to SD card and create folder emummc and inside it i created emummc.ini file and write the hexadecimal value for sector number of second partition

 

[RHOPKINS13]

what is the required configuration exactly? i copied hekate and atmosphere files to SD card and create folder emummc and inside it i created emummc.ini file and write the hexadecimal value for sector number of second partition

You should be good to go now, what happens if you launch CFW from Hekate?

 

[Goldenman66]

You should be good to go now, what happens if you launch CFW from Hekate?

Now when i press to launch emunand from hekate it reboot and show atmosphere logo, also at system info version is 4.1.0 (ams 0.9.2) but when I change switch name at emunand it changed also at ofw I think it should be different, right? Another thing is at hekate emunand is disabled. I’m afraid that it may be running on a cfw instead of emunand, please advise?

 

[RHOPKINS13]

You're right, it's running CFW on your SysNAND and not your emuNAND then. For some reason Atmosphere isn't picking up your emummc config.

Windows often hides extensions for known file types, can you try using command prompt and "DIR" to verify that your emummc.ini file is actually named emummc.ini and not emummc.ini.ini? I've seen that mistake made here more than once.

You're sure you've got the right hexadecimal number for your partition, and didn't just copy one off an example?

 

[tabzer]

You should be able to go into Hekate/Nyx and select the partition you want emummc to be enabled. So select the partition and enable it.

 

[Goldenman66]

You're right, it's running CFW on your SysNAND and not your emuNAND then. For some reason Atmosphere isn't picking up your emummc config.

Windows often hides extensions for known file types, can you try using command prompt and "DIR" to verify that your emummc.ini file is actually named emummc.ini and not emummc.ini.ini? I've seen that mistake made here more than once.

You're sure you've got the right hexadecimal number for your partition, and didn't just copy one off an example?

file extension is right and hexadecimal number also

--------------------- MERGED ---------------------------

You should be able to go into Hekate/Nyx and select the partition you want emummc to be enabled. So select the partition and enable it.

i can't enable it, it is dimmed should i create emunand from hekate to enable it?, also the hexadecimal value is the same as SD RAW 1 sector start, ini file configuration is
"
[emummc]
emummc_enabled = 1
emummc_sector = 0xB980800
emummc_nintendo_path = EmuNAND
"

 

[tabzer]

Assuming you have emummc.ini inside /emuMMC/ it is wrong. In Atmosphere 0.9.3 the format should be like this:


[emummc]
enabled=1
sector=0xB980800
path=emuMMC/RAW1
id=0x0000
nintendo_path=emuMMC/RAW1/Nintendo

 

[Goldenman66]

Assuming you have emummc.ini inside /emuMMC/ it is wrong. In Atmosphere 0.9.3 the format should be like this:


[emummc]
enabled=1
sector=0xB980800
path=emuMMC/RAW1
id=0x0000
nintendo_path=emuMMC/RAW1/Nintendo

after i edit ini file as your configuration under emuMMC info it shows enabled but when i tried to launch it it reboots again to hekate. also RAW1 folder is not exists on the SD card should i create it?

 

[tabzer]

Try making that directory. If it doesn't work, then something about how the Emummc data was written is probably messed up.

 

[Goldenman66]

Try making that directory. If it doesn't work, then something about how the Emummc data was written is probably messed up.

even after i created this folder same issue

 

[tabzer]

try deleting Ox in front of B980800. Otherwise definitely rewrite the boot0+1+nand.bins to the sector. Using DD app works.

--------------------- MERGED ---------------------------

Actually. You should be able to delete and recreate the emummc partition using a partitioning software, then use hekate/nyx to create+enable emummc. That tends to be the most fool-proof way.

 

[Goldenman66]

try deleting Ox in front of B980800. Otherwise definitely rewrite the boot0+1+nand.bins to the sector. Using DD app works.

--------------------- MERGED ---------------------------

Actually. You should be able to delete and recreate the emummc partition using a partitioning software, then use hekate/nyx to create+enable emummc. That tends to be the most fool-proof way.

I tried to use hekate/nyx to create+enable emummc earlier before using dd method with same results, this is the main issue i have when using hekate to create emummc it’s created successfully but when trying to launch it reboot into hekate again also after using dd command and update ini file as your advise it reboots to hekate again, I don’t know what is the problem? is it the firmware version or something wrong i do?

 

[comput3rus3r]

I tried to use hekate/nyx to create+enable emummc earlier before using dd method with same results, this is the main issue i have when using hekate to create emummc it’s created successfully but when trying to launch it reboot into hekate again also after using dd command and update ini file as your advise it reboots to hekate again, I don’t know what is the problem? is it the firmware version or something wrong i do?

wow that sounds complicated. That's why noobs like me use sxos.

 

[xabier]

Do you care about playing online? If not, then there's probably no real reason to use an emuNAND.

Security. Broken emunand is easy to fix. Sysnand is easy but involves extra work

 

[Lacius]

Security. Broken emunand is easy to fix. Sysnand is easy but involves extra work

No. Making a sysNAND backup and restoring it if there's a problem is less cumbersome than setting up an emuNAND.

 

[xabier]

No. Making a sysNAND backup and restoring it if there's a problem is less cumbersome than setting up an emuNAND.

There is always a small risk for bad media or data corruption while restoring a backup. Emunand/emummc is safer.

 

[Lacius]

There is always a small risk for bad media or data corruption while restoring a backup. Emunand/emummc is safer.

You have the same risks with an emuNAND, and using an emuNAND increases the risk of an SD card going bad.