Old nyx gui found please help

[DozeBeatS]

Only had my modded Switch for a month, had it modded by someone else. All was working fine until today when got the "old nyx gui found! there will be dragons!' nessage. Attempting to load emummc does nothing and goes to a black screen. I see there are solutions online but that's if you know your way around the software which I don't. Can anyone explain exactly what need to do please?

 

[jkyoho]

update your hekate bootloader files to match with the payload.bin you using

 

[JustSomeDudeWithAQuestion]

update your hekate bootloader files to match with the payload.bin you using

hey Im new to this and im also getting this error along with a "a fatal error occured when running fusee, unable to identify package 1".
I have found several other threads but all the solutions are more or less outdated, I was wondering if you knew how to fix any of these problems
my bootloader files are updated, but I if they match the payload bin, they way they are supposed to.
Also to note I am upgrading to fimware 21.0.0, I belive I correctly instsalled all the correct updated material, but apparently its not the case.
I would love some help with this.

 

[AmeliaFox]

hey Im new to this and im also getting this error along with a "a fatal error occured when running fusee, unable to identify package 1".
I have found several other threads but all the solutions are more or less outdated, I was wondering if you knew how to fix any of these problems
my bootloader files are updated, but I if they match the payload bin, they way they are supposed to.
Also to note I am upgrading to fimware 21.0.0, I belive I correctly instsalled all the correct updated material, but apparently its not the case.
I would love some help with this.

It's literally telling you what's wrong. You are using the wrong fusee.bin and Atmosphere for the firmware you are trying to load.

What version is your CURRENT sysnand/emunand you are trying to boot?

 

[JustSomeDudeWithAQuestion]

It's literally telling you what's wrong. You are using the wrong fusee.bin and Atmosphere for the firmware you are trying to load.

What version is your CURRENT sysnand/emunand you are trying to boot?

where can I check the versions?
I want to give you the right info because I havent done this in almost 2 years

Post automatically merged: Feb 17, 2026

It's literally telling you what's wrong. You are using the wrong fusee.bin and Atmosphere for the firmware you are trying to load.

What version is your CURRENT sysnand/emunand you are trying to boot?

I believe my sysnand is unchaged since the last time I brought my switch back to date, which was mid 2024. While emunand previously was at 18.smth and now should've been updated to 21.0.0

I got atmosphere 1.10.2

 

[AmeliaFox]

If your emunand is on 21.0.0 you need the latest CLEAN version of Atmosphere, so remove/rename your old Atmosphere folder and use the latest versions of Atmosphere and fusee.bin from here: https://github.com/Atmosphere-NX/Atmosphere/releases

If you also use hekate, get the latest version from here: https://github.com/CTCaer/hekate/releases

Finally get sys-patch from here: https://github.com/impeeza/sys-patch/releases

Make sure to clean or remove the bootloader and Atmosphere folders before unpacking and writing these new files to your microsd card.

That's all you need to do, don't add anything else as there's no need.

 

[JustSomeDudeWithAQuestion]

If your emunand is on 21.0.0 you need the latest CLEAN version of Atmosphere, so remove/rename your old Atmosphere folder and use the latest versions of Atmosphere and fusee.bin from here: https://github.com/Atmosphere-NX/Atmosphere/releases

If you also use hekate, get the latest version from here: https://github.com/CTCaer/hekate/releases

Finally get sys-patch from here: https://github.com/impeeza/sys-patch/releases

Make sure to clean or remove the bootloader and Atmosphere folders before unpacking and writing these new files to your microsd card.

That's all you need to do, don't add anything else as there's no need

Thank you very much

 

[JustSomeDudeWithAQuestion]

Thank you very much

Hey I just followed all the instructions you gave me, and I still ran into the "unable to identify package1!" Message when I tried booting it, do you know what else could cause this issue?

Sorry for pestering you this much

 

[AmeliaFox]

Hey I just followed all the instructions you gave me, and I still ran into the "unable to identify package1!" Message when I tried booting it, do you know what else could cause this issue?

Sorry for pestering you this much

Maybe your emunand is corrupt then, because if Atmosphere/fusee.bin can't read the information from it then it won't be able to identify it. You should re-dump your sysnand using hekate to a new emunand. It could also be your micro sd is dying. Most likely your emunand is corrupted though.

 

[JustSomeDudeWithAQuestion]

Maybe your emunand is corrupt then, because if Atmosphere/fusee.bin can't read the information from it then it won't be able to identify it. You should re-dump your sysnand using hekate to a new emunand. It could also be your micro sd is dying. Most likely your emunand is corrupted though.

Before I did the changes you suggested I tried to boot it one more time, and after the error popped up I held the power button to reboot and the switch for the first time booted up correctly, its all updated and functioning.

You mentioned the error could be caused by my micro sd dying, which based on what happened I believe to be the case, since it seems to not have been properly read by the system the first few times it was booted. I am going to make sure the switch is fully functional so it can last me until I get a new card, lol.

Nontheless I appreciate your help.

update: I can load up games fine, but there seem to be some issues when I tried to boot up tinfoil, and when I pressed the system update button.

 

[AmeliaFox]

Before I did the changes you suggested I tried to boot it one more time, and after the error popped up I held the power button to reboot and the switch for the first time booted up correctly, its all updated and functioning.

You mentioned the error could be caused by my micro sd dying, which based on what happened I believe to be the case, since it seems to not have been properly read by the system the first few times it was booted. I am going to make sure the switch is fully functional so it can last me until I get a new card, lol.

Nontheless I appreciate your help.

update: I can load up games fine, but there seem to be some issues when I tried to boot up tinfoil, and when I pressed the system update button.

Tinfoil is broken on new firmware and latest Atmosphere and needs to be updated by the developer (needs to be compiled with the new libnx). You should use an alternative nsp/xci installer program. DBI/Tinwoo etc.

 

[JustSomeDudeWithAQuestion]

Tinfoil is broken on new firmware and latest Atmosphere and needs to be updated by the developer (needs to be compiled with the new libnx). You should use an alternative nsp/xci installer program. DBI/Tinwoo etc.

Is it really? Damn.. good to know.
Ill give the alternatives a shot then

Preciate it again