error code 2051-0006

[snam11]

hi, i own a switch with 1.0 fw and if i try to load sx os 2.5 i get this error.
with 2.4.1 it works fine.
could you fix this issue?
Lan play would be great, thanx!

 

[snam11]

i just discovered 2.5 works only if emunand is updated to 6.2

 

[Darck]

i just discovered 2.5 works only if emunand is updated to 6.2

This was exactly my problem. I had 2.1 FW and tried using sx os 2.5 beta, but it did not work. I had to find the old version sx os 2.4.1.

 

[imprezgc8]

Emunand is for sure recommended if you are trying to keep your sysnand on a lower firmware. You will start running into games that won't load without the newest firmware.

 

[Darck]

Emunand is for sure recommended if you are trying to keep your sysnand on a lower firmware. You will start running into games that won't load without the newest firmware.

I should have been more clear. I had 2.1 FW. I created emunand on 2.1 FW. When booting into SX OS 2.5, it would crash. I even tried loading into sysnand with SX OS 2.5 and it would crash. It gave the error code as this title thread. It was usually on the "Nintendo" load screen whenever it would crash. Strangely, sometimes I would get to the Lock Screen where you press a button 3 times to unlock, but it would always crash before unlocking. The crash would lead to a black screen where I had to hold the power button for 15 seconds. I thought I had bricked my NSW.

I stumbled upon this thread and tested the theory. I found and tried using 2.4.1 and was able to use it. I then used choidujourNX using SX OS 2.0.1 to upgrade sysnand to 6.2. I tried using SX OS 2.5 and was able to finally use it.

I did not have a clean sysnand and wanted a hidden partition on microsd so I could dual boot for online play on sysnand. So I restored sysnand, blew my fuses for 6.2, and created a new emunand.

I can confirm that loading into SX OS 2.5 on 2.1 FW is not possible for me.

 

[Hellzapoppin]

I also wish to keep my OFW on 2,2 (I'm a waiter):
I intend to use Emunand and update it, but would still like to have the option of booting to CFW with SX OS versions later than 2.41.

(SX OS 2.5.2) - Boot loader menu, OK - select CFW, error 2254-0006
(SX OS 2.5) - Boot loader menu, OK - select CFW, error 2051-0006
(SX OS 2.4.1) - Boot loader menu, OK - select CFW, sucess
(SX OS 2.1) - Boot loader menu, OK - select CFW, sucess

Does TX intend to not support all versions of OFW going forward?
If TX has to implement fixes in the future due to countermeasures, where does that leave us 'waiters'

Can I even install Emunand with SX OS 2.4.1 and update emunand to 6.2 and have it launch later with 2.5.2 ?

Also See:
https://team-xecuter.com/community/threads/error-2254-0006.129451/post-997473

Thanks,

 

[imprezgc8]

I also wish to keep my OFW on 2,2 (I'm a waiter):
I intend to use Emunand and update it, but would still like to have the option of booting to CFW with SX OS versions later than 2.41.

(SX OS 2.5.2) - Boot loader menu, OK - select CFW, error 2254-0006
(SX OS 2.5) - Boot loader menu, OK - select CFW, error 2051-0006
(SX OS 2.4.1) - Boot loader menu, OK - select CFW, sucess
(SX OS 2.1) - Boot loader menu, OK - select CFW, sucess

Does TX intend to not support all versions of OFW going forward?
If TX has to implement fixes in the future due to countermeasures, where does that leave us 'waiters'

Can I even install Emunand with SX OS 2.4.1 and update emunand to 6.2 and have it launch later with 2.5.2 ?

Also See:
https://team-xecuter.com/community/threads/error-2254-0006.129451/post-997473

Thanks,

So first, SX does support all current OFWs. If you are running 6.2 OFW you need to use at least SX 2.4. Any OFW lower than that can use previous versions of SX, but it is always recommended to use the latest ver.

To answer your second question, I am currently running OFW 5.1 SX 2.5.2 with emunand on 6.2.

We can try to troubleshoot the issue you are facing and try to get SX 2.5.2 working. Once that is working you can then try to setup emunand.

First thing to do is make sure you have a current OFW 2.2. Once you make a backup to your computer and a few other places if you can. Once you have that, back up your license file and any other files you want from your SD. Then format your SD with your switch, copy the license file back and I would honestly re-download the SX 2.5.2 file and copy to the SD card. See if you are able to boot then.

Start with that and let me know what happens.

I should have been more clear. I had 2.1 FW. I created emunand on 2.1 FW. When booting into SX OS 2.5, it would crash. I even tried loading into sysnand with SX OS 2.5 and it would crash. It gave the error code as this title thread. It was usually on the "Nintendo" load screen whenever it would crash. Strangely, sometimes I would get to the Lock Screen where you press a button 3 times to unlock, but it would always crash before unlocking. The crash would lead to a black screen where I had to hold the power button for 15 seconds. I thought I had bricked my NSW.

I stumbled upon this thread and tested the theory. I found and tried using 2.4.1 and was able to use it. I then used choidujourNX using SX OS 2.0.1 to upgrade sysnand to 6.2. I tried using SX OS 2.5 and was able to finally use it.

I did not have a clean sysnand and wanted a hidden partition on microsd so I could dual boot for online play on sysnand. So I restored sysnand, blew my fuses for 6.2, and created a new emunand.

I can confirm that loading into SX OS 2.5 on 2.1 FW is not possible for me.

Very weird. Wish I could test myself, but I do not have a switch running OFW 2.1.

 

[Hellzapoppin]

I think we are saying the same thing (and the link I posted) .
2.5 and 2.5.2 on earlier sysnand (1.0 2.1 2.2 ) or emunand crashes with an error code.

My aim is first to be able to boot CFW 2.5.2 (or later) on a virgin 2.2 OFW , and eventually emunand at 6.2 and later. SX 2.41 (and SX 2.0) are the latest I can. I tried multiple sd cards (formatted the 8gb with Switch) and downloaded 2.5 and 2.52 several times then tested. Same results.

Thanks.

 

[imprezgc8]

Very weird. If you use an older ver of SX, does it work without crashing? Say like Ver 2.0 or even like 1.8?

 

[Hellzapoppin]

(SX OS 2.5.2) - Boot loader menu, OK - select CFW, error 2254-0006
(SX OS 2.5) - Boot loader menu, OK - select CFW, error 2051-0006
(SX OS 2.4.1) - Boot loader menu, OK - select CFW, success
(SX OS 2.1) - Boot loader menu, OK - select CFW, success

I can try earlier.

 

[imprezgc8]

Sorry, Lot of stuff going on. Didn't remember you posted that already. It does seem like something changed between 2.4.1 and 2.5. I will see what I can find and let you know.

 

[laboden]

Any update on this discussion? I am having same error when using v2.5 and v2.5.2. My sysnand is on even lower 1.0.0

 

[imprezgc8]

There are a lot of people posting about problems in this thread. Some of you are not even running the sam OFW. Please start your own thread if you are having an issue with all your information. It is hard to keep track of everyones info if they are all in the same thread.

 

[Hellzapoppin]

Tokyo, Some people don't want to update their OFW (Sysnand), there are reasons. This is precisely the point we are trying to make. We want to be able to run current SX-OS on firmware as shipped.
imprezgc8, nothing really has changed - 2.5 and 2.5.2 on earlier firmware (1.0 2.1 2.2 ) crashes with an error code - 2.41 and earlier works.
I didn't start my own thread because I believe this is an SX-OS issue introduced after 2.41 - not user error. If you still think separate threads would help, I'd be glad to do what you ask. Thanks again

 

[imprezgc8]

Tokyo, Some people don't want to update their OFW (Sysnand), there are reasons. This is precisely the point we are trying to make. We want to be able to run current SX-OS on firmware as shipped.
imprezgc8, nothing really has changed - 2.5 and 2.5.2 on earlier firmware (1.0 2.1 2.2 ) crashes with an error code - 2.41 and earlier works.
I didn't start my own thread because I believe this is an SX-OS issue introduced after 2.41 - not user error. If you still think separate threads would help, I'd be glad to do what you ask. Thanks again

Unfortunately it is going to be hard to troubleshoot this since most people do not have such low FW Switches to test. I can confirm that all versions of SX have worked as intended. Now I have been on OFW 5.1 for a while and more recently created an emunand and updated that to 6.2. I have used just about every version of SX without issues though. So this is either something with FW 1.0 or something the user setups. Not trying to be an ass here. It's just like I said above, will be hard to troubleshoot without having a Switch on a low firmware.

Only suggestion I can make personally if you don't want to update your sysnand, is to use a version of SX that works that supports emunand (hopefully SD Files version), create an emunand, update that to 6.2 and then update SX. Leaving your sysnand on a low FW still, but being able to use a new SX ver.