- Dec 14, 2011
- 25
- 3
I got SX core installed on a V1 patched switch originally was on 5.1.0. new firmware and OS was not yet released by that time and was on firmware 1.2 and SX OS 3.0.2
sysNAND, emuNAND, and OFW work fine, but I was on 5.1.0 so I need to update and so I stupidly updated emuNAND using ChoiDujourNX thinking it was safe its emuNAND and reads reports that works on emunand and 3.0.2.
Everything seems to work and I have successfully updated emuNAND to 10.0.4 and the next step for me is getting my keys so I could do some mods then I found out that I can no longer boot on sysNAND or emuNAND giving me these errors.

So my sysNAND is on 5.1.0 and my emuNAND is on 10.0.4. Tried updating to firmware 1.3 and SX OS 3.0.3 and problem still persist.
Question is... is this normal? that the sysNAND is brick while my emuNAND works without a problem.
sysNAND, emuNAND, and OFW work fine, but I was on 5.1.0 so I need to update and so I stupidly updated emuNAND using ChoiDujourNX thinking it was safe its emuNAND and reads reports that works on emunand and 3.0.2.
Everything seems to work and I have successfully updated emuNAND to 10.0.4 and the next step for me is getting my keys so I could do some mods then I found out that I can no longer boot on sysNAND or emuNAND giving me these errors.

So my sysNAND is on 5.1.0 and my emuNAND is on 10.0.4. Tried updating to firmware 1.3 and SX OS 3.0.3 and problem still persist.
Question is... is this normal? that the sysNAND is brick while my emuNAND works without a problem.
Last edited: