Fellow gbatemp users,
It has been reported by many SX OS users that the latest SX OS 2.9 BETA is causing several different types of issues, some of which are quite major. This thread is to help warn others who may see the post created by "GaryOPA" titled: "TX Presents SX OS v2.9 BETA - With Full v9.0 Firmware Support!" and quickly jump to the latest BETA 2.9 release without realizing the potential issues at hand.
The main issue of concern is:
1) When a user downloads the latest SX OS 2.9 BETA, copies the new boot.bin to their microSD card, boots into the new 2.9 BETA CFW and initiates a firmware update to 9.0.0 (and possibly other firmware versions) using ChoiDujourNX version 1.0.1, it may cause the update to stop partially through on the "flashing firmware packages 0/6" screen. When this happens the user is forced to hard reboot the console which results in a black screen. At this point many users chose to restore their NAND backups in order to get access back into SX OS again. Others mention that they are able to load into atmosphere cfw and downgrade their firmware back to 8.1.0 and use SX OS 2.8 again. For those who ran into this issue while using emunand are able to re-create emunand which also seems to correct the issue.
**There is a work around that I and others were able to do to avoid the above issue: it required you to load into SX OS 2.8 and install firmware 9.0.0 using ChoiDujourNX version 1.0.2, once this is completed you are able to change boot.bin to the latest 2.9 version. Other methods for updating firmware successfully include using TXInstaller, Tinfoil, official Nintendo servers, etc.**
This leads us to another issue:
2) Users have also been reporting that the latest SX OS 2.9 BETA when loading into 9.0.0 firmware causes a GCFuse to burn (Game Cart Fuse) that prevents you from using game carts on firmware versions lower then 9.0.0.
3) Using the latest SX OS 2.9 BETA on firmware 9.0.0: This seems to break custom XCI loading. We are unsure if this is related to the GCFuse burn. Waiting to see if this can be corrected with a new SX OS revision.
Minor Issues:
4) Using the latest SX OS 2.9 BETA on firmware 9.0.0 in docked mode: When exiting the album using the "B" button, it causes an error.
5) Using the latest SX OS 2.9 BETA on firmware 8.1.0: When attempting to initiate a firmware update to 9.0.0 using ChoiDujourNX version 1.0.2 it stops on the "Testing for BIS Protection" screen, user is forced to do a hard reboot but is able to get back into SX OS 2.9 still on firmware 8.1.0.
6) Using the latest SX OS 2.9 BETA on firmware 9.0.0: No longer allows you to install incognito.
I realize that there may be more issues I am unaware of. Some of the mentioned issues may only affect certain users. There may be more workarounds for some of these issues and many of these issues may be resolved by an update by TX. We are noticing that GBAtemp mods have not changed the title to GaryOPA's thread to include a "Warning" as many people have repeatedly asked within that thread. We have also not heard from GaryOPA or TX on these issues recently. TX did make a post on their discord warning the following, quote:
"
@everyone There have been enough reports of people having trouble upgrading to 9.0 with choidujourNX... Please just stay on 8.1.0 until further notice while we look into what is going on. If you insist on upgrading it seems the 2.8 boot.dat file is not showing the same problems.
Remember
1: ALWAYS BACK UP YOUR NAND BEFORE CHANGING FIRMWARE VERSIONS. ALWAYS - NO EXCEPTIONS!
2: Disable any themes before upgrading firmware.
3: Always enable the exFAT driver when upgrading.
4: Pay attention to the AutoRCM option if you are using ChoidujourNX. Choose wisely."
Now we have to wait to see what response we get from TX, whether it be a new SX OS revision that includes many fixes to these issues or a statement/post addressing these problems. Personally I would recommend that TX temporarily removes the new 2.9 BETA download until these issues are looked into in more detail and a proper revision released that does not negatively impact their user base.
I made this post simply to warn others that may update without knowing this information. Hope I was able to help some.