Hacking Fatal Error after updating Atmosphere, Hekate and OFW

[Tatsuna]

Hi guys.

Today I had the unfortunate idea of updating my Switch through AIO Switch Update (disclaimer: I'm absolutely not blaming it) and now I can't seem to boot into Atmosphere anymore.

First of all, I use an R4s Dongle to inject Hekate and subsequently fusee-primary.bin. Through a personal hekate_ipl.ini I made so that when I inject my Switch, it goes straight to Atmosphere.
Now, after I had updated everything through AIO Switch Updater (as in Atmosphere, then sigpatches, then the OFW), Atmosphere crashed because of a fatal error and now my Switch is stuck at this:

I tried reverting to the previous versions of both Hekate and Atmosphere, but none seemed to work. Just in case, even if I knew it was useless, I overwrote the newest sigpatches with the ones I was using before. No luck.

Is there anything I can do about it? Thank you in advance.

 

[Hayato213]

If you can't boot using a clean build of Atmosphere you probably have to restore your NAND probably, SciresM doesn't recommend using these AIO updater, that why the Atmosphere Updater stop operation.

https://gbatemp.net/threads/atmosphere-updater-an-atmosphere-updater-for-your-switch.548450/page-6

 

[Tatsuna]

If you can't boot using a clean build of Atmosphere you probably have to restore your NAND probably, SciresM doesn't recommend using these AIO updater, that why the Atmosphere Updater stop operation.

https://gbatemp.net/threads/atmosphere-updater-an-atmosphere-updater-for-your-switch.548450/page-6

Clean installing Atmosphere worked, after a bit I managed to recompile the hekate_ipl.ini too. Thank you and sorry, it was easier than I thought.