OFFICIAL SX OS v2.6 BETA Discussion

Status
Not open for further replies.

Plaidstallion

Noob Account
Jan 13, 2019
9
1
World
I haven't tested this personally. I know there is a bug that relates to emunand.... I will find out.

edit:
All I have heard is the boot up is "iffy" and may take a few attempts?

I am not sure as the emunand bug isn't confirmed. Any info from users on this is welcome.
OK I guess I will hold off for now as still even today the games being released can be patched to 6.2.0.

Side question: ChoiDuJourNX 1.0.1 released last year (02.08.2018) is the latest version? Seems weird that a new version isn't needed to apply newer firmware revisions.
Edit: I guess it is still the most up to date version to use. I will leave the question in case anyone stumbles across this wondering the same about Choi.
 
Last edited:

Palinkat

Full Member
Apr 5, 2018
34
8
I can confirm that the jit patches (Patch for svcControlCodeMemory ) now work in sx os and on emunand !!!
So, retroarch with n64 core works perfectly on emunand !!!
Time to forget about atmosphere :cool:
Thanks for the post, which version of the core are you using? I don't see anything different on my console so might have the wrong version of muppen64.

TA
 

lordplops

Senior Member
Feb 8, 2019
135
28
France
OK I guess I will hold off for now as still even today the games being released can be patched to 6.2.0.

Side question: ChoiDuJourNX 1.0.1 released last year (02.08.2018) is the latest version? Seems weird that a new version isn't needed to apply newer firmware revisions.
Edit: I guess it is still the most up to date version to use. I will leave the question in case anyone stumbles across this wondering the same about Choi.
you don't need new hands to turn a new key in a new lock do you? Same principle.
 

killer2239

Noob Account
Mar 14, 2019
3
1
USA
I updated my emunand with choixdujour without any problem, just keep in mind HDD support doesn't work in CFW 7.0.x
So just to be sure I understand this correctly as I have not been through a firmware upgrade since I got SX OS Pro when my switch on was 6.2. So the correct upgrade path for both System and EMU nand would be to do the following:

-Boot to SX dongle screen, switch to System Nand (turn off emu nand).
-Boot CFW 6.2 Sys Nand and Upgrade with Chio to 7.0.1 select to not burn fuse
-Reboot and test booting up with OFW on sys nand.
-Reboot and go back into dongle sx screen, turn on emu nand
-Boot into CFW 6.2 Emu Nand and upgrade with Chio to 7.0.1 and again select not to burn fuse
-Reboot and load CFW 7.0.1 with Emu Nand on

I assume it would be a good idea to do a new Nand dump (not where you create the Emu, but just a dump as a backup) before the stop of booting back into the emu nand to upgrade it to 7.0.1?

Edit: If I was not worried about fuses, would the only difference be to boot into OFW and let it do the system update like normal? I assume best to turn off AutoRCM first if its on. If I did it this way, when updating the EMU Nand with Chio, would it matter if I left option on or off to not burn fuse?
 
Last edited:

Leena12

Junior Member
Mar 11, 2019
22
3
Florida, USA
I saw it mentioned in this thread a few times as an issue but since this is my exact situation, can we get some confirmation one way or another:

Does 2.6 Beta work when upgrading a hidden partition emuNAND from 6.2.0 to 7.0.1 with ChoiDuJourNX?
I was wondering the same thing, because I read somewhere that when they loaded EMUnand (hidden partition 6.2 to 7.0.1) it crashed. I also read a few people were having problems, but I'm not sure what it might be, it may be what gameover mentioned as well.
Hopefully they can get this fixed. I"m not that brave to try it as of yet.
 

Hudson88

Junior Member
Mar 17, 2019
22
3
England
The emunand should automatically initiate when you boot in to sx there will be a little yellow box above boot cfw to say it's on
 

vipera1212

Full Member
Dec 13, 2018
36
8
Hi, today I used FTP to move some files to my Switch, next I went to work. When I came back home I was unable to transfer other files. I would like to know if there's anything I can do to fix this or is a problem of 2.6?
 

JJTapia19

Full Member
Feb 11, 2019
45
8
Puerto Rico
Many users have confirmed that atmos reboot to payload feature is now implemented using the reboot to payload.nro. My request is, can that feature be also implemented to de fatal error screen like atmos does. That way we would we would not need to inject the sx payload to get back to sx if a crash comes. Those crashes are really common with installers and homebrew.
 

vipera1212

Full Member
Dec 13, 2018
36
8
We will need more info than that.

It worked, then it didn't work is just not enough.

Do you have free space on your sd card? What ftp program are you using? Do you get any errors?
I have 58 GB on my microSD and I was trying to move an update of 34 MB. I was using Filezilla and while it was moving the file it failed due to an internet issue, after that I was unable to transfer other files.
 

vipera1212

Full Member
Dec 13, 2018
36
8
Sounds like you have a network issue there. Or possibly your switch entered sleep mode?

For large file transfers it is MUCH more practical to take the SD card out and copy the files to it from PC. So much faster.
The only strange thing is that Filezilla says that transfer is completed... But it doesn't copy anything on the Switch
 

JJTapia19

Full Member
Feb 11, 2019
45
8
Puerto Rico
I have 58 GB on my microSD and I was trying to move an update of 34 MB. I was using Filezilla and while it was moving the file it failed due to an internet issue, after that I was unable to transfer other files.
Also if the file you need to transfer smaller than 4gb you can mount your switch as an mtp device using this homebrew app and copy and paste the files to the sd card without ftp or removing the sd card if you have a usb c cable. https://github.com/liuervehc/nxmtp/releases
 

vipera1212

Full Member
Dec 13, 2018
36
8
Also if the file you need to transfer smaller than 4gb you can mount your switch as an mtp device using this homebrew app and copy and paste the files to the sd card without ftp or removing the sd card if you have a usb c cable. https://github.com/liuervehc/nxmtp/releases
Thanks man I'll try
And I also noticed that delete after install in Sx Installer doesn't work properly
 
Last edited:
  • Like
Reactions: JJTapia19

SenshiV

Noob Account
Mar 12, 2019
2
1
US
HI, I just want to share my situation.

I downloaded the update and it's working well until now. I don;t use much of advance features so I can;t vouch for them thou'

I just ran into a problem that fortunately was easily fixed.

After updating to 7 before this update, my switch was unable to boot at all, even with Tegra, The SX logo appeared, then the Switch went blank again so I couldn't try anything else or play physicals in the meantime.

Today, I downloaded the update, copied to my SD card, tried to boot with the dongle and didn't work, so I connected the switch to the PC, ran Tegra, and loaded the SX_Loader.bin. The switch started then went blank (as before), but after that it restarted and it was working again.

Just mentioning it in case it's helpful to anybody.

Thanks for the update TX.
 

Spike_916

Noob Account
Jun 10, 2009
4
1
Sacramento, CA
Here are my finding and input on the new 2.6 Beta SX OS.

Steps I took for install:
  • Backed up License Key, SX Installer, SX Dumper, Checkpoint, etc.
  • Fresh Format on MicroSD (ExFAT w/ Default Allocation)
  • Put in MicroSD and Booted Original FW to Initialize the MicroSD
  • Shutdown System
  • Loaded Boot.dat, License Key, SX Installer, SX Dumper, Checkpoint, etc. to MicroSD
  • Placed Jumper and SX Pro on Switch and Booted in Recovery
  • Installed EmuNAND to MicroSD and Installed AutoRCM
  • Booted into Custom FW
Keep in mind before I did this process I updated all game software also since I was getting dual software update message.

First one is as follows:

Ready to Start System Update. Update Now?
Once the update is complete, the console will restart.”

Options: Start Software, Cancel, or Update

Second one is as follows:

“A System Update is Required Before you Can Proceed.”
Options: Cancel or Update

Prior to the 2.6 install, in the Original FW, this wasn’t an issue since after I updated and the messages went away. Once I Installed EmuNAND and booted into the SX OS the messages reappeared which is an issue. If I attempt to update, due to Stealth mode, it blocks communication to Nintendo so I can’t update to bypass the second message. Only option is to Cancel which makes Pokemon Let’s Go Eevee unplayable in SX OS. All my other games just prompt the first Software message which I can hit “Start Software” and it works fine.

One attempt to fix this issue was to use SX Installer 1.5 on all my games but with no success. Curious how in SX OS can I update these offline (if possible) and somehow remove these messages like it is for my Original FW.

Here are my gripes two gripes so far on my experience with 2.6 BETA
  • I can’t boot into Original FW without Hooking it up and doing a Payload dump. It just is a black screen not until I plug in the SX Pro, then it automatically starts.
  • Software Update Messages
Tonight, I am going to attempt a clean install of everything. Uninstall AutoRCM, Uninstall EmuNAND, Restore the Switch, Turn Off Auto Update, ensure all update messages are gone, then start the process from scratch.

Still somewhat new to this, so let me know if you see a mistake on my part or if something doesn’t make sense. All help is much appreciated. Also if you are experiencing the same issues, let me know so I don't feel like I am the only one lol.

Random Issues after the first boot into SX OS 2.6 BETA that Somehow Fixed Themselves with a Restart:
  • My actual legit games would not load immediately, took 4-5 attempts each time.
  • Saved Game File Corruption message for LEGO Ninjago
  • Skyrim Failed Repeatedly in SX Installed 1.5 (Might have been MicroSD Space Issue)
Nintendo Switch Info
System Version: 7.0.1
SX Installer 1.5
SX OS 2.6 BETA

Edited: Forgot to shout out to the Team Xecuter staff for all their hard work and future efforts.
 
Status
Not open for further replies.