Sxos 3.0.0.0 not working with emunad??

Animefighters88

Full Member
Jun 7, 2020
37
8
Usa
Hi to everyone right now I'm on system FW 5.1 with an emunad rocking on 10.0.3 when I run sxos 3.0.0 with my emunad it will not boot into the emunad it will go into my sys nad it will never boot into the emunad. My system is a non chipped switch. Emunad working great on sxos 2.9.5 NOT 3.0.0 I see some people that have chipped the system and have an emunad working in 3.0.0 what I think is 3.0.0 will not work with an emunad unless it is chipped. When 3.0.0 boots up it brings me into my sys nad then I click on the gallery icon and it show sxos 3.0.0 any info would be awesome
 

safcalibur

Senior Member
May 1, 2020
116
18
Cambs
sorry what do you mean by 'chipped'?

I'm running emunand 10.0.1 with sxos 3.0 and am able to boot into emunand no problem. I'm pretty sure I havent chipped my switch in any way, have just used sx pro dongle, jig and sxos software.
 

Animefighters88

Full Member
Jun 7, 2020
37
8
Usa
Chipped slashed on modded
sorry what do you mean by 'chipped'?

I'm running emunand 10.0.1 with sxos 3.0 and am able to boot into emunand no problem. I'm pretty sure I havent chipped my switch in any way, have just used sx pro dongle, jig and sxos software.
3.00 will only boot into sys fw
 

Animefighters88

Full Member
Jun 7, 2020
37
8
Usa
Should I delete my emunad and try again what do you think also my switch is running sys nad 5.1 and emunad 10.0.3 any info would help
 

safcalibur

Senior Member
May 1, 2020
116
18
Cambs
how did you create your emunand? Is it hidden partition, on your sd card or on internal memory?

Mine is created on sd card but not as hidden partition.
 

Animefighters88

Full Member
Jun 7, 2020
37
8
Usa
Yes exfat.
would this work? ok
1. delete my emunand
2. update my switch sys nad from ver 5.1 to 10.0.0 then update it to 10.0.3 or 0.4 useing sxos 3.0.0 or should i use an older SXOS when updating??
3 make a new emunad as of right now i think my emundad is installed on the internal sys HD NOT on the SDCARD becuase i can take a brand new sd card loade up with games and i can boot into my EMU or SYS nad. BTW im banned i really dont see a point of haveing an EMUNAD someone please help any info is awsome.
how did you create your emunand? Is it hidden partition, on your sd card or on internal memory?

Mine is created on sd card but not as hidden partition.
yes i think so i can use any new sdcard on the sys and it will boot into emu NP
 
Last edited:

safcalibur

Senior Member
May 1, 2020
116
18
Cambs
Yes exfat.
would this work? ok
1. delete my emunand
2. update my switch sys nad from ver 5.1 to 10.0.0 then update it to 10.0.3 or 0.4 useing sxos 3.0.0 or should i use an older SXOS when updating??
3 make a new emunad as of right now i think my emundad is installed on the internal sys HD NOT on the SDCARD becuase i can take a brand new sd card loade up with games and i can boot into my EMU or SYS nad. BTW im banned i really dont see a point of haveing an EMUNAD someone please help any info is awsome.


yes i think so i can use any new sdcard on the sys and it will boot into emu NP
If you want to continue using emunand you dont need to update your sysnand, you can leave it on 5.1 that shouldnt be a problem.

I would delete the emunand then create a new one onto a micro SD card and have it as files on the card. I read somewhere (will try and dig out source) that if you create an emunand any other way then sxos 3.0 wont boot into it. The advantage of running an emunand besides the ban thing is that you can upgrade/downgrade firmware. I find this particularly useful in the modding scene as on newer versions of software people tend to find bugs etc

I upgraded my emunand to 10.0.1 and sxos 2.9.5b, this caused a lot of crashes with my games so I was able to go back to 9.2.0 with sxos 2.9.4 which worked perfectly and waited until sxos 3.0 came out. I then the other day upgraded f/w again and now using sxos 3.0 no issues, if there was any bugs I could just downgrade again. Thats a good feature of using choi to upgrade/downgrade.

Technically speaking you are right, you dont need an emunand as can do the same with your sysnand if you use choi as well. The problem comes if you use nintendo servers to upgrade, then you can go back as you burn fuses.

If you use choi to upgrade your sysnand then yeah, I dont see the point of having an emunand.

When upgrading f/w I would first of all put the newer boot.dat version of sxos onto your sd card, reboot into that to make sure all is good (all newer versions of sxos should work with all previous f/w versions). once that is confirmed as working I would upgrade the f/w via choi.
 
  • Like
Reactions: Animefighters88

Zuluuk

Noob Account
Jun 13, 2019
3
3
Here
The most common issue you will have is a plugin was installed, before you do anything drastic just rename the folder tittles to tittles_old and try. I had this issue when updating.

The other issue is themes, you should be on default before upgrading.
 
  • Like
Reactions: Animefighters88

Animefighters88

Full Member
Jun 7, 2020
37
8
Usa
If you want to continue using emunand you dont need to update your sysnand, you can leave it on 5.1 that shouldnt be a problem.

I would delete the emunand then create a new one onto a micro SD card and have it as files on the card. I read somewhere (will try and dig out source) that if you create an emunand any other way then sxos 3.0 wont boot into it. The advantage of running an emunand besides the ban thing is that you can upgrade/downgrade firmware. I find this particularly useful in the modding scene as on newer versions of software people tend to find bugs etc

I upgraded my emunand to 10.0.1 and sxos 2.9.5b, this caused a lot of crashes with my games so I was able to go back to 9.2.0 with sxos 2.9.4 which worked perfectly and waited until sxos 3.0 came out. I then the other day upgraded f/w again and now using sxos 3.0 no issues, if there was any bugs I could just downgrade again. Thats a good feature of using choi to upgrade/downgrade.

Technically speaking you are right, you dont need an emunand as can do the same with your sysnand if you use choi as well. The problem comes if you use nintendo servers to upgrade, then you can go back as you burn fuses.

If you use choi to upgrade your sysnand then yeah, I dont see the point of having an emunand.

When upgrading f/w I would first of all put the newer boot.dat version of sxos onto your sd card, reboot into that to make sure all is good (all newer versions of sxos should work with all previous f/w versions). once that is confirmed as working I would upgrade the f/w via choi.
Great info thanks :)
Thanks. I have no themes installed
 

Alanrey00

Noob Account
Feb 21, 2020
3
3
Mexico
Hi, I seem to have the same problem, tried deleting some folders and other things but nothing seems to work, went back to sx os 9.5 and everything works as normal

Sys ver: 10.0.1
Emunand ver 9.2.0

Maybe the new sx os just works with versions 10.0.x?
 

Animefighters88

Full Member
Jun 7, 2020
37
8
Usa
Hi, I seem to have the same problem, tried deleting some folders and other things but nothing seems to work, went back to sx os 9.5 and everything works as normal

Sys ver: 10.0.1
Emunand ver 9.2.0

Maybe the new sx os just works with versions 10.0.x?
You can update to 10.0.3 it works great besides the emunand . Definitely update so u can play the new games . If u dont update to 10.0.3 u have to use the save games files to boot the game . Emunad is working great with 10.0.3 and sxos 2.9.5 I'm thinking sxos with update soon.
 

Alanrey00

Noob Account
Feb 21, 2020
3
3
Mexico
You can update to 10.0.3 it works great besides the emunand . Definitely update so u can play the new games . If u dont update to 10.0.3 u have to use the save games files to boot the game . Emunad is working great with 10.0.3 and sxos 2.9.5 I'm thinking sxos with update soon.
I haven't update because I just update when I want a new game or want to play smash bros on the sys nand but lately I don't got that much time :/ but thanks anyway
 
  • Like
Reactions: Animefighters88

Blackice018

Noob Account
Oct 17, 2018
1
1
Same problem here, was running emunand 9.1.0 with sxos 2.9.5. Updated sxos to 3.0.0 and emunand boots to sysnand. I was not aware until i ran Choi to update to 10.0.3 and it said i was already on 10.0.4 (my sysnand). Might even cause a ban since my sysnand was not in flight mode.

Anyway, i downgraded sxos back to 2.9.5 and was able to boot into emunand again. Updated emunand to 10.0.3 exfat with Choi and tried again with sxos 3.0.0. i'm back on sxos 2.9.5 because 3.0.0 also boots into sysnand with emunand 10.0.3. I believe i have emunand on SD card without hidden partition (i have the Switch/sx folder). Using emutendo folder and no titles or themes in sxos folder.

I'm thinking maybe the folder structure is the problem or SXOS assumes it's installed in the wrong folder/partition. SX is in SD:/switch/sx, boot.dat on root, but i also have the SD:/sxos folder which has an empty titles and backup folder.
 
Last edited:

Animefighters88

Full Member
Jun 7, 2020
37
8
Usa
Same problem here, was running emunand 9.1.0 with sxos 2.9.5. Updated sxos to 3.0.0 and emunand boots to sysnand. I was not aware until i ran Choi to update to 10.0.3 and it said i was already on 10.0.4 (my sysnand). Might even cause a ban since my sysnand was not in flight mode.

Anyway, i downgraded sxos back to 2.9.5 and was able to boot into emunand again. Updated emunand to 10.0.3 exfat with Choi and tried again with sxos 3.0.0. i'm back on sxos 2.9.5 because 3.0.0 also boots into sysnand with emunand 10.0.3. I believe i have emunand on SD card without hidden partition (i have the Switch/sx folder). Using emutendo folder and no titles or themes in sxos folder.

I'm thinking maybe the folder structure is the problem or SXOS assumes it's installed in the wrong folder/partition. SX is in SD:/switch/sx, boot.dat on root, but i also have the SD:/sxos folder which has an empty titles and backup folder.

I hope it gets fixed asap for the time being I'm just staying on sxos 2.9.5 with 10.0.3.
 

Animefighters88

Full Member
Jun 7, 2020
37
8
Usa
Same problem here, was running emunand 9.1.0 with sxos 2.9.5. Updated sxos to 3.0.0 and emunand boots to sysnand. I was not aware until i ran Choi to update to 10.0.3 and it said i was already on 10.0.4 (my sysnand). Might even cause a ban since my sysnand was not in flight mode.

Anyway, i downgraded sxos back to 2.9.5 and was able to boot into emunand again. Updated emunand to 10.0.3 exfat with Choi and tried again with sxos 3.0.0. i'm back on sxos 2.9.5 because 3.0.0 also boots into sysnand with emunand 10.0.3. I believe i have emunand on SD card without hidden partition (i have the Switch/sx folder). Using emutendo folder and no titles or themes in sxos folder.

I'm thinking maybe the folder structure is the problem or SXOS assumes it's installed in the wrong folder/partition. SX is in SD:/switch/sx, boot.dat on root, but i also have the SD:/sxos folder which has an empty titles and backup folder.
Sxos 3.0.0 unfortunately seems like it doesn't support an internal emunad. I'm seeing all over the forum this is happening to a lot of ppl. The only way around it . Is to have an emunad on an sd card I'm just waiting to see if the next sxos update fixes this.
 

necora01

Junior Member
Apr 17, 2019
10
1
spain
Same problem with firmware 10.0.4 exfat and sx v3.0.0 error code 2168-0002 on start emunand.
Works fine with 2.9.5 version