Hacking Setup emuNAND with SX OS, Unable to use cartridge clot in OFW

[Aagrajag]

I tried to set up my Switch such that it could run a lower firmware in sysNAND and a higher one in emuNAND, but I seem to have somehow made it impossible to use the cartridge slot in OFW running in sysNAND. Although I can boot into OFW without any problem, the moment any cartridge is inserted into the slot, the system throws this error code “2002-2634” and requires a reboot.

Here’s my setup:

With the console offline (and remaining so since) I was running OFC 3.0.1 and used an SX Pro jig and dongle (with SX OS 2.5) to setup an emuNAND based on that firmware. I entered the emuNAND and used the latest Choidujour to successfully update the emuNAND to 6.1.0. No problems so far; OFW is still 3.0.1, just as I left it, and CFW is reporting 6.1.0. Also, autoRCM is *not* enabled.

I can now use the cartridge slot in the 6.1.0 CFW without a problem to dump games and such, but when I boot back into the 3.0.1 OFW the cartridge slot becomes unusable, throwing that 2002-2634 error code and forcing a reboot whenever a game is inserted.

Does anyone know how to get the slot working again in OFW? Choidujour supposedly kept my fuses intact when I upgraded the emuNAND’s firmware from 3.0.1 to 6.1.0, but it sounds like some kind of mismatch due to the firmware versions being different between the OFW and the CFW. No one else in the referenced thread reported any such problems, though.

I simply wanted a good way to backup all my legit games to a memory card, but at this point I’m looking for any solution that will fix the cartridge slot in the OFW. I’ve thought of possibly:

1. Doing a factory reset on the emuNAND, the sysNAND, or both.
2. Booting into SX OS on the sysNAND and using Choidujour to bring the sysNAND’s firmware up to 6.1.0 so the OFW and CFW versions match
3. Failing all else, going completely legit, updating the sysNAND to the latest 6.2.0 firmware through the regular update and then throwing the SX dongle and bullshit out the window as money well-wasted.

I haven’t done anything yet, since I don’t want to lose any options in case someone has a solution, and I *can* still use the slot and backups successfully in the 6.0.1 emuNAND. If I can’t fix the slot sysNAND *and* lose the working emuNAND, then I’ll really be hosed.

Infinite thanks to anyone who can help me with this. Cheers.

 

[OrGoN3]

I tried to set up my Switch such that it could run a lower firmware in sysNAND and a higher one in emuNAND, but I seem to have somehow made it impossible to use the cartridge slot in OFW running in sysNAND. Although I can boot into OFW without any problem, the moment any cartridge is inserted into the slot, the system throws this error code “2002-2634” and requires a reboot.

Here’s my setup:

With the console offline (and remaining so since) I was running OFC 3.0.1 and used an SX Pro jig and dongle (with SX OS 2.5) to setup an emuNAND based on that firmware. I entered the emuNAND and used the latest Choidujour to successfully update the emuNAND to 6.1.0. No problems so far; OFW is still 3.0.1, just as I left it, and CFW is reporting 6.1.0. Also, autoRCM is *not* enabled.

I can now use the cartridge slot in the 6.1.0 CFW without a problem to dump games and such, but when I boot back into the 3.0.1 OFW the cartridge slot becomes unusable, throwing that 2002-2634 error code and forcing a reboot whenever a game is inserted.

Does anyone know how to get the slot working again in OFW? Choidujour supposedly kept my fuses intact when I upgraded the emuNAND’s firmware from 3.0.1 to 6.1.0, but it sounds like some kind of mismatch due to the firmware versions being different between the OFW and the CFW. No one else in the referenced thread reported any such problems, though.

I simply wanted a good way to backup all my legit games to a memory card, but at this point I’m looking for any solution that will fix the cartridge slot in the OFW. I’ve thought of possibly:

1. Doing a factory reset on the emuNAND, the sysNAND, or both.
2. Booting into SX OS on the sysNAND and using Choidujour to bring the sysNAND’s firmware up to 6.1.0 so the OFW and CFW versions match
3. Failing all else, going completely legit, updating the sysNAND to the latest 6.2.0 firmware through the regular update and then throwing the SX dongle and bullshit out the window as money well-wasted.

I haven’t done anything yet, since I don’t want to lose any options in case someone has a solution, and I *can* still use the slot and backups successfully in the 6.0.1 emuNAND. If I can’t fix the slot sysNAND *and* lose the working emuNAND, then I’ll really be hosed.

Infinite thanks to anyone who can help me with this. Cheers.

When updating your emuNAND, did you make sure to use the nogc option? You might've upgraded the firmware of your card slot by accident, which would render it unusable on lower firms.

 

[Aagrajag]

When updating your emuNAND, did you make sure to use the nogc option? You might've upgraded the firmware of your card slot by accident, which would render it unusable on lower firms.

Thanks for the fast reply.

Crap, I didn't know about any such option. I just restarted Choidujour, but I could not find that option anywhere. If it isn't enabled by default, then that's what may have happened.

If that is the case, what is the best way to proceed from here? Can it be reversed or ignored somehow? Should I find some way of updating the sysNAND to 6.0.1 as well?

 

[k3rizz3k]

Thanks for the fast reply.

Crap, I didn't know about any such option. I just restarted Choidujour, but I could not find that option anywhere. If it isn't enabled by default, then that's what may have happened.

If that is the case, what is the best way to proceed from here? Can it be reversed or ignored somehow? Should I find some way of updating the sysNAND to 6.0.1 as well?

As far as I know it is irreversible.

 

[Aagrajag]

As far as I know it is irreversible.

Meaning the game card reader has its own fuses... Wonderful...

So, theoretically, updating the sysNAND firmware to match the 6.1.0 emuNAND firmware should fix it, right? My terror now is that because the card reader update should not be able to exist in a 3.0.1 firmware, running Choidujour in sysNAND to update the system firmware to 6.1.0 might do something unpredictable when it tries to update the card reader's firmware which has already been (but should not have been) updated.

 

[k3rizz3k]

Meaning the game card reader has its own fuses... Wonderful...

So, theoretically, updating the sysNAND firmware to match the 6.1.0 emuNAND firmware should fix it, right? My terror now is that because the card reader update should not be able to exist in a 3.0.1 firmware, running Choidujour in sysNAND to update the system firmware to 6.1.0 might do something unpredictable when it tries to update the card reader's firmware which has already been (but should not have been) updated.

Updating your sysnand should fix it.

 

[Aagrajag]

Updating your sysnand should fix it.

That sounds like my only option, but is it safe to do so using Choidujour again to bring it to 6.1.0? I don't want to update the sysNAND officially, because that would force me onto the latest 6.2, with which I've heard their are problems. Choidujour already kind of burned me by not warning about this irreversible card reader update, so I'm very wary about what will happen when the upgrade process on sysNAND encounters an already-updated card reader that shouldn't technically exist in that state.

 

[shanefromoz]

6.2 has no problems that i know of

 

[Aagrajag]

Oh, and I should probably mention a very minor but possibly related issue in the 6.1.0 emuNAND:

Whenever I first insert a cartridge, nothing happens for about three seconds, then I get a message stating that a game card is *not* inserted, but, if I pop it out and then in again, it works. This strange first-insertion-fails-second-insertion-succeeds happens always now, and with all cartridges.

--------------------- MERGED ---------------------------

6.2 has no problems that i know of

Unfortunately, that is not what I'm reading here:

http://3ds-flashcard.com/blog/dose-sx-os-pro-works-on-new-switch-firmware-6-2-0/

so I'm extremely reluctant to go beyond 6.1.

 

[shanefromoz]

Works fine here with 6.2 and sxos

 

[AmandaRose]

Oh, and I should probably mention a very minor but possibly related issue in the 6.1.0 emuNAND:

Whenever I first insert a cartridge, nothing happens for about three seconds, then I get a message stating that a game card is *not* inserted, but, if I pop it out and then in again, it works. This strange first-insertion-fails-second-insertion-succeeds happens always now, and with all cartridges.

--------------------- MERGED ---------------------------



Unfortunately, that is not what I'm reading here:

http://3ds-flashcard.com/blog/dose-sx-os-pro-works-on-new-switch-firmware-6-2-0/

so I'm extremely reluctant to go beyond 6.1.

That is old news sx-os has been updated to work on latest firmware.

https://team-xecuter.com/forums/threads/155006-SX-OS-BETA-REPOSITORY-Downloads-all-beta-versions

 

[Aagrajag]

That is old news sx-os has been updated to work on latest firmware.

https://team-xecuter.com/forums/threads/155006-SX-OS-BETA-REPOSITORY-Downloads-all-beta-versions

Ah. Well, at least that leaves another option for me.

 

[DocKlokMan]

Ah. Well, at least that leaves another option for me.

PS, the cartridge firmware was only ever updated once, in FW 4.0.0. So you only really need to update sysNAND to 4.0.0 using ChoiNX if you want to try and keep it low.

 

[Aagrajag]

PS, the cartridge firmware was only ever updated once, in FW 4.0.0. So you only really need to update sysNAND to 4.0.0 using ChoiNX if you want to try and keep it low.

Thanks, I'm trying to keep it low, but my major concern now is that when I use Choidujour to update to *any* newer firmware on the sysNAND, something might go sideways when it tries to update the already-updated card reader. That should be impossible, right?

 

[Andalitez]

Thanks, I'm trying to keep it low, but my major concern now is that when I use Choidujour to update to *any* newer firmware on the sysNAND, something might go sideways when it tries to update the already-updated card reader. That should be impossible, right?

Nothing is impossible, but yeah people have done it. It does a fuse check when it loads the first time,so nothing bad should happen

 

[DocKlokMan]

Thanks, I'm trying to keep it low, but my major concern now is that when I use Choidujour to update to *any* newer firmware on the sysNAND, something might go sideways when it tries to update the already-updated card reader. That should be impossible, right?

No reports of such an incident have surfaced.

 

[ILLPLEASA]

Oh, and I should probably mention a very minor but possibly related issue in the 6.1.0 emuNAND:

Whenever I first insert a cartridge, nothing happens for about three seconds, then I get a message stating that a game card is *not* inserted, but, if I pop it out and then in again, it works. This strange first-insertion-fails-second-insertion-succeeds happens always now, and with all cartridges.

This is happening to one of my friend’s Switch as well running SX OS 2.5 Beta...

They did a fresh wipe on Sys 6.2 then created EmuNAND right after so I don’t think it’s related to 6.1 nor your particular cartridge slot upgrade..

It also ONLY happens to my friend within EmuNAND as their card slot works perfectly fine in their SysNAND

I honestly think it could be a bug related to SXOS... What version of SX OS are you running?

My friend assumed it happened because they might have left a cartridge in the slot while they were creating the EmuNAND...

not sure the validity of that claim nor if a fresh wipe and EmuNAND install might clear the problem as they don’t want to go through the whole setup again unfortunately...

 

[metaphz]

This is happening to one of my friend’s Switch as well running SX OS 2.5 Beta...


It also ONLY happens to my friend within EmuNAND as their card slot works perfectly fine in their SysNAND

This happens to me on 6.2.0 with 2.5 also. However I'm affected on SysNAND, have never used emuNAND.

 

[Aagrajag]

I honestly think it could be a bug related to SXOS... What version of SX OS are you running?

I think there is a good chance the bug has something to do with SX OS 2.5. It *is* a beta release, after all.

 

[Aagrajag]

Thanks for all your advice, guys. Just to report in:

I successfully used Choidujournx to update the sysNAND form 3.0.1 to 4.1.0 and no problems were caused by the card reader, so to do so is safe for anyone else who finds himself in my situation.