Hacking EmuMMC stuck at switch logo

[BiggieBeans]

Hey so I setup emuMMC through the new Hekate release and everything seemed to be working so I booted into my sysnand (through Hekate) and set it downloading all the games and updates I (accidentally) deleted when reformatting my SD. But when that finished up all fine and well I went to boot into my emuMMC and it just hung at the Nintendo Switch logo and continues to do so every time I try and I have no clue why. I can still boot sysnand though. Can anyone help me out?

 

[Galactiiix]

do you have the latest version of atmosphere?

 

[BiggieBeans]

do you have the latest version of atmosphere?

Yup, 0.9.2. For reference I'm using the latest Kosmos.

 

[Galactiiix]

I had yesterday the same problem with the 0.9.2, I had to take the 0.9.1, update my emummc in 8.1.0 with choidujourNX and resume the version of atmosphere in 0.9.2. And now all works well

 

[crazy_p]

Edit your emummc.ini in your emummc Folder.

Delete all emummc_ prefixes.

Make sure it looks like this:

[emummc]
enabled = 1
sector = 0X03CBB000 (Put your own Sector here)
nintendo_path = Emutendo (Put your own Path here)

 

[BiggieBeans]

I had yesterday the same problem with the 0.9.2, I had to take the 0.9.1, update my emummc in 8.1.0 with choidujourNX and resume the version of atmosphere in 0.9.2. And now all works well

Hmm, my emummc firmware is already at 8.1.0 though. Will reinstalling the firmware fix my issue? And did you choose exfat when you installed it?

Edit your emummc.ini in your emummc Folder.

Delete all emummc_ prefixes.

Make sure it looks like this:

[emummc]
enabled = 1
sector = 0X03CBB000 (Put your own Sector here)
nintendo_path = Emutendo

I checked but there are no emummc_ prefixes in my ini. This is what mine looks like (remembering I let Hekate do all the setup):

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

 

[Galactiiix]

yes, i chose exfat

 

[crazy_p]

Hmm, my emummc firmware is already at 8.1.0 though. Will reinstalling the firmware fix my issue? And did you choose exfat when you installed it?


I checked but there are no emummc_ prefixes in my ini. This is what mine looks like (remembering I let Hekate do all the setup):

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

Hm strange maybe try 0.9.1 before creating a new emummc.

Btw do you have any custom Theme on your SD?
Try to delete them temporary.

Also when updating emummc with ChoiduJourNX don't install autoRCM and also do a Factory Reset
in ChoiduJour while updating!

 

[altorn]

Hmm, my emummc firmware is already at 8.1.0 though. Will reinstalling the firmware fix my issue? And did you choose exfat when you installed it?


I checked but there are no emummc_ prefixes in my ini. This is what mine looks like (remembering I let Hekate do all the setup):

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

nvm

 

[crazy_p]

nvm

His .ini File is abolutely fine!

 

[BiggieBeans]

nvm

Was gonna say, quite the contrary advice to have, thanks anyway though

yes, i chose exfat

Hm strange maybe try 0.9.1 before creating a new emummc.

Btw do you have any custom Theme on your SD?
Try to delete them temporary.

Also when updating emummc with ChoiduJour don't install autoRCM and also do a Factory Reset
in ChoiduJour while updating!

Nah no custom theme. I'll switch to 0.9.1 and see what I can do, will get back to you afterwards, cheers!

 

[crazy_p]

Was gonna say, quite the contrary advice to have, thanks anyway though



Nah no custom theme. I'll switch to 0.9.1 and see what I can do, will get back to you afterwards, cheers!

How do you Boot Atmosphere? Do you inject fusee-primary.bin direct or via Hekate?

If via Hekate, whats in your hekate_ipl.ini?

Try:

[config]
autoboot=0
autoboot_list=0
bootwait=1
verification=1
backlight=100
autohosoff=0
autonogc=0

[Atmosphere EMU]
payload=bootloader/payloads/fusee-primary.bin

[Atmosphere SYS]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1


(copy fusee-primary.bin to bootloader/payloads/ or define your own Path)

 

[BiggieBeans]

How do you Boot Atmosphere? Do you inject fusee-primary.bin direct or via Hekate?

If via Hekate, whats in your hekate_ipl.ini?

Try:

[config]
autoboot=0
autoboot_list=0
bootwait=1
verification=1
backlight=100
autohosoff=0
autonogc=0

[Atmosphere EMU]
payload=bootloader/payloads/fusee-primary.bin

[Atmosphere SYS]
emummc_force_disable=1
payload=bootloader/payloads/fusee-primary.bin


(copy fusee-primary.bin to bootloader/payloads/ or define your own Path)

Via Hekate. Heres my ini before making any changes:

[config]
autoboot=1
autoboot_list=0
bootwait=1
verification=1
backlight=100
autohosoff=0
autonogc=1

{AtlasNX/Kosmos v13}
{}
{Discord: link (not allowed to post links yet)}
{Github: link}
{Patreon: link}
{Pegascape DNS: link}
{This bundle provided by SDSetup}
{}

{-- Custom Firmware --}
[CFW]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

{---- Miscellaneous ---}
[Stock]
fss0=atmosphere/fusee-secondary.bin
stock=1
icon=bootloader/res/icon_switch.bmp
{}

{--- FORCED SYSNAND ---}
[CFW (EMUMMC Disabled)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
[Stock (EMUMMC Disabled)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
stock=1
icon=bootloader/res/icon_switch.bmp
{}

Not seeing any mention of fusee-primary in there, not sure if that's an issue. Will try what you suggested.

 

[KTroopA]

slighty OT but what is the difference between fusee-secondary.bin and
fusee-primary.bin?

 

[crazy_p]

Iirc fusee-primary is like Hekate a Bootloader (a way to boot Atmosphere)


Fusée-Primary
Fusée-primary is the payload file (fusee-primary.bin) sent to the Switch from an external device. Once sent, fusée-primary makes initial preparations before loading fusée-secondary from the Switch’s SD Card.

Fusée-primary can be configured via the BCT.ini file located on the Switch’s SD card.


BTW Atmosphere 0.9.2 somehow fails to load SYSNand via Heakate 0.9.1 works fine tho...!

 

[Akira]

Try the newly released hotfix

 

[BiggieBeans]

How do you Boot Atmosphere? Do you inject fusee-primary.bin direct or via Hekate?

If via Hekate, whats in your hekate_ipl.ini?

Try:

[config]
autoboot=0
autoboot_list=0
bootwait=1
verification=1
backlight=100
autohosoff=0
autonogc=0

[Atmosphere EMU]
payload=bootloader/payloads/fusee-primary.bin

[Atmosphere SYS]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1


(copy fusee-primary.bin to bootloader/payloads/ or define your own Path)

I launched both presets and neither booted properly. EmuMMC gave me the hanging switch logo with autonogc turned on but in all other scenarios each of them gave me a black screen.

Try the newly released hotfix

Okey doke I'll give it a go. I take it's one of these two on the Github release?:
atmosphere-0.9.2-master-6f85b11f+hbl-2.1+hbmenu-3.0.1.zip
atmosphere-0.9.2-master-b0a66a63+hbl-2.1+hbmenu-3.0.1.zip

 

[crazy_p]

I launched both presets and neither booted properly. EmuMMC gave me the hanging switch logo with autonogc turned on but in all other scenarios each of them gave me a black screen.

Only thing i could think of, is try to delete the two lines in emummc.ini and make spaces.

Edit from:
[emummc]
enabled=1
sector=0xafcc000
path=emuMMC/RAW1
id=0x0000
nintendo_path=emuMMC/RAW1/Nintendo

To:
[emummc]
enabled = 1
sector = 0xafcc000
nintendo_path = emuMMC/RAW1/Nintendo

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

On which Firmware was your Emummc when you created it? Did you uncheck autoRCM and Factory reseted the Emummc in ChoiduJourNX? If not, best would be to start from scratch. I had the same problem before, in my case autoRCM was the culprit...

 

[BiggieBeans]

Try the newly released hotfix

Only thing i could think of, is try to delete the two lines in emummc.ini and make spaces.

Edit from:
[emummc]
enabled=1
sector=0xafcc000
path=emuMMC/RAW1
id=0x0000
nintendo_path=emuMMC/RAW1/Nintendo

To:
[emummc]
enabled = 1
sector = 0xafcc000
nintendo_path = emuMMC/RAW1/Nintendo

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

On which Firmware was your Emummc when you created it? Did you uncheck autoRCM and Factory reseted the Emummc? If not, best would be to start from scratch. I had the same problem before, in my case autoRCM was the culprit...

Neither the hotfix or the emummc.ini changes gave me any results, and my emuMMC was created on and still is on 8.1.0. Turning off autoRCM hasn't given any immediate results but I'll go do the whole factory reset thing (assuming AMS 9.0.1 boots).

 

[crazy_p]

Try the newly released hotfix

Thanks that fixed my Problem! (i was on SYS 4.1.0)
[Fix for 4.X units (new strato rework broke a method in spl) (#616)]

Neither the hotfix or the emummc.ini changes gave me any results, and my emuMMC was created on and still is on 8.1.0. Turning off autoRCM hasn't given any immediate results but I'll go do the whole factory reset thing (assuming AMS 9.0.1 boots).

Strange, with this Build (copy hbl.nsp from a previous Release to /atmosphere/) and these Settings both my SYS and EMU Nand just boot fine!

emummc.ini

[emummc]
enabled = 1
sector = 0X03CBB000
nintendo_path = Emutendo


hekate_ipl.ini

[config]
autoboot=0
autoboot_list=0
bootwait=1
verification=1
backlight=100
autohosoff=0
autonogc=0

[Atmosphere EMU]
payload=bootloader/payloads/fusee-primary.bin
logopath=bootloader/Atmosphere.bmp
icon=bootloader/res/Atmosphere.bmp

[Atmosphere SYS]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1
logopath=bootloader/Atmosphere.bmp
icon=bootloader/res/Atmosphere.bmp