SX OS v2.3 BETA was released by TX, is it possible to use SX Pro /SX OS to play free games on Nintendo Switch? What is the news of SX OS v2.3 BETA? Should we update SX OS to v2.3 BETA?
What is the news of SX OS v2.3
SD emuNAND support
Since the introduction of our emuNAND feature we got a lot of comments about our initial decision to make the emuNAND data live on the actual system NAND. After lots of hard work we are happy to say we now have a workable solution for storing your emuNAND partition data on your microSD card. This has the upside of not using up any space on your Switch. In order to use the new microSD emuNAND system you will *not* have to format your microSD card. Simply enter the TX boot menu by holding Volume-+ while powering on your switch. Head into the options menu and select emuNAND on the left. Users of our existing emuNAND solution will see an option to migrate their existing emuNAND data. The migration process also cleans up the old emuNAND from the system NAND. Painless! We’re interested in hearing your feedback about this exciting new functionality.
The ‘Emutendo’ folder
In addition to the new microSD emuNAND system we also introduce the ‘Emutendo’ folder on your microSD card. As you’ve probably noticed, the Switch saves various data to a ‘Nintendo’ folder on your microSD card. To completely decouple this data between your Original Firmware and your EmuNAND enabled firmware we have made EmuNAND enabled systems use this differently named folder. If you want keep using your old SD card data with your emuNAND, simply copy/rename the ‘Nintendo’ folder to ‘Emutendo’.
Added more directories to scan for content
By popular demand we have added yet another list of subdirectories that will be scanned on your microSD card (or USB harddisk) for XCI/NSP/homebrew. The directories that have been added are:
– /sxos/updates
– /sxos/dlc
– /switch/updates
– /switch/dlc
Homebrew menu takeover of any title by holding R
Homebrew is usually launched from either the TX menu or the Homebrew Launcher menu. Both of these applications run as an ‘applet’ on the Switch. Applets do not have access to all of the system’s memory, and thus any homebrew apps or games launched from here are affected by this as well. The only way to allow full use of the system’s memory was to build and install homebrew NSP files. But now we have added another way to give homebrew applications full memory access! You can now hold the (R) button while launching any regular title, and this will launch the Homebrew Launcher Menu. Any homebrew launched from here will run with the same capabilities as a regular Switch game/app. Enjoy!
Loading homebrew from USB
More good news for homebrew lovers. You can now copy homebrew NRO files to your USB harddisk as well, and launch them directly from our SX OS menu.
Stability improvements
Overall stability of many components has been improved. This includes LayeredFS and USB incompatibilities. We have also fixed a bug which would prevent people from launching more than 32 titles.
libusbfs update
Last but not least a small update for developers. We’ve squashed a small bug in libusbfs pertaining the stat() function. If you had issues with this, grab an updated copy of libusbfs from our website!
Should we update SX OS to v2.3 BETA?
After the test on SX OS 2.3. There’s a critical bug in SX OS 2.3. After moving Emunand from NAND to mSD it’ll restore the whole BOOT1 to its original form and backup a copy to sx\emunand\boot1.bin which won’t have EMUNAND recognition inside of it (thanks to restoring to the origin). That causes a black screen when booting to Emunand. There’s a slight difference in sx\emunand\boot0.bin compares to original BOOT0 as well.
The good news here: We won’t touch BOOT0/1 anymore.
Solution: Before moving Emunand to mSD, backup BOOT0, and BOOT1.
After moving EMunand to mSD, rename backup BOOT1 to boot1.bin and copy and paste it to sxos\emunand\ (overwrite when asked）
UPDATE: Backup BOOT0 and BOOT1 (from the Emunand on NAND) then rename to boot0.bin and boot1.bin then copy to sxos\emunand\ > Works Perfectly.
After updating to newer firmware. We should manually adjust BOOT1 to fit the purpose if there is any BOOT1 update available. and manually backup BOOT0 to sx\emunand\boot0.bin as well.
3dslatestinformation 