Help migrating from SXOS to Atmosphere

[nokaktsawa]

Hi everybody,

I was on SX OS (partition based EmuNAND) on an old Erista switch and I followed this guide to migrate to Atmosphere:

hxxps://rentry.org/mys8q

(place "t" 's instead of "x" 's in the URL)

I also restored my original boot0 and boot1 even if my switch is not a Mariko via NxNandManager

Once I inserted my SD into my switch, I managed to boot it into Hekate, I selected emuMMC in the main menu, selected Migrate emuMMC and finally selected emunand, which is now enabled.
Then I finally launched Atmosphere CFW but it doesn't boot, and says the following:

A fatal error occurred when running Fusée.
Failed to find INI1!

Press POWER to reboot.

If I press POWER, it still gives me the same error message.

What did I do wrong? How can I fix that?
TYIA

 

[urherenow]

First and foremost, you did NOT have to "migrate" your emummc. I've been switching between the two at random, since emummc became available. Hekate runs perfectly well on an SX-created emummc. I'm not going to look at the guide you used, but I'll assume it's old. Do you have a hekate_ipl.ini in there in the boot loader folder? Does it have the following entry in it somewhere?

[CFW - emuMMC]
fss0=atmosphere/package3
emummcforce=1
kip1patch=nosigchk
atmosphere=1
icon=bootloader/res/icon_payload.bmp

Note the fss0 line ends in "package3". An old guide likely doesn't mention that, but you should read the darn manual (for hekate and/or Atmosphere) yourself, instead of following a stupid guide. Guides don't get updated.

You would also need /emummc/emummc.ini with the following entry:

[emummc]
enabled=1
sector=0x2
path=emuMMC/RAW1
id=0x0000
nintendo_path=Emutendo

but if your "migrate emummc" physically moved or renamed anything, the above entry may no longer be valid for your SD (it's for an SX partition-based emummc). Give it a try though, I guess.

 

[nokaktsawa]

First and foremost, you did NOT have to "migrate" your emummc. I've been switching between the two at random, since emummc became available. Hekate runs perfectly well on an SX-created emummc. I'm not going to look at the guide you used, but I'll assume it's old. Do you have a hekate_ipl.ini in there in the boot loader folder? Does it have the following entry in it somewhere?

[CFW - emuMMC]
fss0=atmosphere/package3
emummcforce=1
kip1patch=nosigchk
atmosphere=1
icon=bootloader/res/icon_payload.bmp

Note the fss0 line ends in "package3". An old guide likely doesn't mention that, but you should read the darn manual (for hekate and/or Atmosphere) yourself, instead of following a stupid guide. Guides don't get updated.

You would also need /emummc/emummc.ini with the following entry:

[emummc]
enabled=1
sector=0x2
path=emuMMC/RAW1
id=0x0000
nintendo_path=Emutendo

but if your "migrate emummc" physically moved or renamed anything, the above entry may no longer be valid for your SD (it's for an SX partition-based emummc). Give it a try though, I guess.

First and foremost, thank you for your reply.
Actually I just fixed my issue by replacing the boot0 and boot1 I stupidly restored even if I was not on Mariko.
BTW yes, the guide I followed should be quite updated since it contains the entry "fss0=atmosphere/package3"

 

[urherenow]

First and foremost, thank you for your reply.
Actually I just fixed my issue by replacing the boot0 and boot1 I stupidly restored even if I was not on Mariko.
BTW yes, the guide I followed should be quite updated since it contains the entry "fss0=atmosphere/package3"

Good to hear. Was about to tell you about the /emuMMC/RAW1/raw_based file, but realised I hadn't installed HxD on my new laptop yet and was looking at what the 4 bytes in that file were. Pretty sure it's the same for everyone, but not sure what they're for or where they come from.

00 60 F9 37 are the 4 bytes, in case anybody is curious.