Hacking Error while trying to boot into sysnand

[LeyendaV]

Yesterday I updated my sysnand to 15.0.1, then returned to emunand normally and without any issues.
Today, while trying to boot into sys once more (from Hekate 5.9.0), I get this message.

First time I see this kind of error tbh.

Disabling autorcm and turning on the console works as a temporary fix.

 

[binkinator]

Yesterday I updated my sysnand to 15.0.1, then returned to emunand normally and without any issues.
Today, while trying to boot into sys once more (from Hekate 5.9.0), I get this message.

View attachment 338529

First time I see this kind of error tbh.

Disabling autorcm and turning on the console works as a temporary fix.

Updating to Atmosphere 1.4.0 worked over here (identical symptoms):



https://gbatemp.net/threads/switch-noob-paradise-ask-questions-here.488277/page-1757#post-9967953

 

[LeyendaV]

Updating to Atmosphere 1.4.0 worked over here (identical symptoms):

View attachment 338567

https://gbatemp.net/threads/switch-noob-paradise-ask-questions-here.488277/page-1757#post-9967953

For what I can see, his problem was with Atmosphere on emunand. My emunand boots without any kind of issue, is the sysnand what's not launching.

 

[binkinator]

For what I can see, his problem was with Atmosphere on emunand. My emunand boots without any kind of issue, is the sysnand what's not launching.

Are you booting Sysnand via Hekate? If so, please share the stanza from /bootloader/hekate_ipl.ini for Sysnand that you are clicking to boot up.

 

[LeyendaV]

Are you booting Sysnand via Hekate? If so, please share the stanza from /bootloader/hekate_ipl.ini for Sysnand that you are clicking to boot up.

[Stock - sysMMC]
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_switch.bmp

 

[binkinator]

[Stock - sysMMC]
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_switch.bmp

Right, so check the first line where it’s using package3 under the /atmosphere directory. If your Atmosphere isn’t up to date with your FW it will not be able to boot properly. Please update your Atmosphere.

E: your emunand is likely down-rev and thus not impacted. You should always update in this order, Atmosphere/Hekate and then FW