Hacking Atmosphere crashing after updating sysnand to 9.0.0

[Mike_77712]

I updated my sysnand to 9.0.0 then tried to go to rcm(since autorcm was enabled) but i'm guessing the update broke autorcm. Then got into rcm using a jig but when i launch atmosphere on my emunand it crashes after the switch logo with error 2002-2634 on the usual atmosphere crash screen. Emunand is 8.1.0 (Atmosphere 0.9.3). Any ideas for fixing this? Sysnand works fine

 

[Lacius]

Downgrade your sysNAND or wait for 9.0.0 support (likely coming soon).

 

[Mike_77712]

Downgrade your sysNAND or wait for 9.0.0 support (likely coming soon).

i think i'll just stick it out and wait for 9.0.0 support, i probably might go and break something with downgrading

 

[Lacius]

i think i'll just stick it out and wait for 9.0.0 support, i probably might go and break something with downgrading

That's your best option. SciresM already has Atmosphere tentatively running on 9.0.0, so the wait likely won't be long.

In the future, you should not update until Atmosphere has been updated to support the new system version.

 

[TheCyberQuake]

I updated my sysnand to 9.0.0 then tried to go to rcm(since autorcm was enabled) but i'm guessing the update broke autorcm. Then got into rcm using a jig but when i launch atmosphere on my emunand it crashes after the switch logo with error 2002-2634 on the usual atmosphere crash screen. Emunand is 8.1.0 (Atmosphere 0.9.3). Any ideas for fixing this? Sysnand works fine

Take the game card out of the slot. If you updated sysNAND to 9.0.0, gamecard slot firmware was updated, and launching emuNAND with a game inserted causes it to crash.
Basically until CFW supports 9.0.0 and you can update your emuNAND, you won't be able to have gamecards inserted in emuNAND

 

[Mike_77712]

Take the game card out of the slot. If you updated sysNAND to 9.0.0, gamecard slot firmware was updated, and launching emuNAND with a game inserted causes it to crash.

Thanks. emunand works again. Looking back i did read something about game card slot issues with 9.0

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

That's your best option. SciresM already has Atmosphere tentatively running on 9.0.0, so the wait likely won't be long.

In the future, you should not update until Atmosphere has been updated to support the new system version.

You're right, I just had to jump the gun to play smash and immediately regretted it. Actually when i try and boot stock (sysnand) through hekate I get sent right back to hekate

 

[Lacius]

You're right, I just had to jump the gun to play smash and immediately regretted it. Actually when i try and boot stock (sysnand) through hekate I get sent right back to hekate

You cannot use Hekate with 9.0.0 until it gets 9.0.0 support. The only way to boot 9.0.0 right now is without a custom bootloader, which means you should not install AutoRCM for the time being unless you want to be temporarily locked out of your sysNAND.

 

[Mike_77712]

You cannot use Hekate with 9.0.0 until it gets 9.0.0 support. The only way to boot 9.0.0 right now is without a custom bootloader, which means you should not install AutoRCM for the time being unless you want to be temporarily locked out of your sysNAND.

Gotcha, so the only way to use sysnand again without waiting for hekate 9.0.0 support would be to disable auto rcm and boot normally

 

[Lacius]

Gotcha, so the only way to use sysnand again without waiting for hekate 9.0.0 support would be to disable auto rcm and boot normally

That is correct. You need Hekate or fusee-primary to become compatible with 9.0.0 before they can boot a 9.0.0 sysNAND.

 

[Joaoaug]

Take the game card out of the slot. If you updated sysNAND to 9.0.0, gamecard slot firmware was updated, and launching emuNAND with a game inserted causes it to crash.
Basically until CFW supports 9.0.0 and you can update your emuNAND, you won't be able to have gamecards inserted in emuNAND

Tks mate, i just got acess to my emunand again.