Emunand broken after updating Sysnand, please help

[Audino]

Hello,

I have an Oled switch with mod chip. Today my Sysnand was prompted to update and still works, but my Emunand isn’t booting anymore. It says a fatal error occurred when booting fusee, can not locate warm boot firmware. I've searched everywhere but can't find answers. The warmboot error fix doesn't work and I've updated atmosphere and hekate. What can I do to fix this?

 

[Hayato213]

There is a pre-release of Atmosphere 1.6 on Atmosphere github you can use.

https://github.com/Atmosphere-NX/Atmosphere/releases

 

[Audino]

There is a pre-release of Atmosphere 1.6 on Atmosphere github you can use.

https://github.com/Atmosphere-NX/Atmosphere/releases

I already used it, it doesn’t fix this problem

 

[Hayato213]

I already used it, it doesn’t fix this problem

Did you inject fusee.bin?

 

[Audino]

Did you inject fusee.bin?

Yeah I updated it

 

[Waip]

I am having the exact same issue. Switch OLED with instinct NX V6 chip, 16.10 emunand and updated sysnand to 17.0
Tried updating hekate to 6.0.7 and atmo to 16.0 with new fusee, it still gives the same error message :/

 

[josete2k]

You need to launch cfw on sysnand in order to autodump warmboot.

 

[Waip]

You need to launch cfw on sysnand in order to autodump warmboot.

Thanks for the advice, I got it to work again indeed. Here's what I did:

1) Launched atmo 1.6.0 on sysnand 17.0, it worked and created "wb_13.bin"
2) Then changed atmosphere to previous working install with sigpatches for 16.10 emunand, and it booted like a charm

 

[josete2k]

You can/should use the new atmosphere too

 

[Waip]

You can/should use the new atmosphere too

Unless I am mistaken, no sigpatches yet ?

 

[josete2k]

Unless I am mistaken, no sigpatches yet ?

Yep... But only for the 17.0.0

You can use 16.1.0 with latest atmos without any issue. Only Loader patches are needed and sys-patch can do that.

 

[Audino]

Oh my god I'm so happy it works again. Thank you very much!!! I was so sad that it didn't work anymore and it felt like I was the only one with this issue.

 

[CapitolLimited]

If anyone else has this problem, I fixed it by booting to OFW at least once using the Warmboot Error Fix from Hekate -> Launch. It might be named differently based on your own installation method, but whatever Hekate Launch option that lets you boot into OFW works (as long as it's NOT through Hekate->Reboot->OFW). No renaming files or creating any files needed.