NEW UPDATE FIXES UPGRADE ISSUES! ​

​

PLEASE USE V2.9.1b INSTEAD OF 2.9​

​

YOU CAN NOW USE CHOIDUJOURNX 1.0.2 WITH 2.9.1b

**********************************************


Good day, fans and believers! We hope you are all having a good weekend.

Team-Xecuter has done it again, they have updated their world-famous SX OS to now support the latest v9.0 Switch firmware from Nintendo.

Today, we bring you a much needed update of SX OS. Full compatibility with the latest Switch firmware 9.0! Sorry that we kept you waiting, we wanted to make sure all our unique features still properly work.

Additionally, we also introduced support for the "Horizon split format". This means that people who use FAT32 can have folders named 'game.xci' with split parts contained therein (named 00, 01, 02, etc.). Make sure the folder has the 'archive' bit set.

We know you are waiting for some other big features in SX OS, they are coming.. We wanted to get this compatibility update out first though.

So what are you waiting for? SX OS 2.9 beta is available for download on our website now! (and also through the builtin online updater part of SX OS.)

—< Team-Xecuter - Rocking the Switch in 2019 and beyond! >—​

Source: MaxConsole

 

[gizmomelb]

Also where is garry in the last 19 pages huh. Hiding like tx are. Sxos is a shitstorm atm. I hope for the tx fans tx sort there shit out quick smart. Not fair for anyone to have bricked consoles.

It's the weekend, not everyone works 24/7 - though why some companies release major patches / updates for any product on a Friday is beyond me.. It means if there are problems their support and devs aren't around to quickly address issues until 2 days later.

 

[hippy dave]

Hey does anyone have any of the old "Brickway" memes from the 3DS days?

 

[Khar00f]

Wait what? You are going online with your Emunand? Have you disabled stealth mode?

Yes, I disable stealth to update my games.

 

[hippy dave]

Yes, I disable stealth to update my games.

Then there's no point you using stealth mode at all. All the logs & telemetry that isn't sent when stealth mode is on, is saved up and sent the moment there's a connection available (ie stealth mode turned off).

 

[TheCyberQuake]

Yes, I disable stealth to update my games.

There's literally no point in using stealth mode if you ever go online without it, because all of the logs and telemetry stuff is basically saved and then sent once you go online without it. AFAIK it isn't cleared or anything.

 

[Khar00f]

Then there's no point you using stealth mode at all. All the logs & telemetry that isn't sent when stealth mode is on, is saved up and sent the moment there's a connection available (ie stealth mode turned off).

That's fine, I was doing it long before stealth was an option, so far I'm still not banned (it seems) since I can still download the updates.

I don't use this switch for dual boot, I use only with SX, I have another switch for my online play.

 

[hippy dave]

Hey does anyone have any of the old "Brickway" memes from the 3DS days?

I could only find this one old one from back in the day:

Spoiler

and this somewhat prophetic more recent one:

Spoiler

 

[Essasetic]

IF TX have blindly copied code from Atmosphere, then ChoiDuJourNX should be working with no issues, since the 1.02 revision of CJNX apparently has atmos only compatible code calls in it (from discussions on Discord - currently trying to catch up on facts, rather than opinions). Since CJNX is also closed source it's not something *I* can easily look into.

You missed one key word "blindly". Since they "blindly" copied code and didn't test for any conflicts that may happen with their own code. You got the situation with ChoiDujourNX where people's switches got bricked. I can't think of another reason for this.

Still checking, but that semi has to be expected - it was like an earlier GC firmware update - was it 3.x or 4.x where there was a forced GC update in the firmware update. It seems that with 9.0.0 the forced GC update process also burns a fuse - I'll need to verify in the atmos sections, though possibly that might be related to the atmos specific code in ChoiDuJourNX so it skips burning a fuse? Further research will hopefully uncover the truth rather than opinion.

You really didn't need to check? Hexkyz already has confirmed that this update burnt a GC fuse. It shouldn't really "be expected". What I did expect however was TX to inform users of this issue and they should've gave the users two options. To either enable nogc and not be able to use it on 9.0.0 (but still have the ability to use it on earlier firmwares) or don't enable nogc and be able to use it on 9.0.0 (but not on earlier firmwares). ChoiDujourNX also has literally nothing to do with GC fuses and it can't be worked for it not to burn GC fuses.

The GC code has changed and still boots single title XCIs with no issues - it is only the bundled XCIs with DLC and updates integrated which are having issues and guess what? That's probably because of the updated GC firmware from Nintendo. I'm guessing Nintendo now check to see if there is only a single titleID / licence / ticket in the XCI for it to run, if there are more (which should never occur in real cartridges) then it's not passing the security test.

But since XCI is an SX OS specifc thing and loads of atmos users have said they never see the point, I guess it won't effect anyone other than SX OS users, right?

Grasping for thin straws, I never said it couldn't boot normal xci files. That could be possible but then riddle me this. Why didn't TX test and resolve this? They were already two weeks behind Atmosphere in getting 9.0.0 support is that not enough time to check that every feature is at least functional on 9.0.0? We'll have to wait and see what Nintendo has done behind the scenes.

Yes, you are correct. But how is atmosphere relevant to this? I hadn't even mentioned atmosphere in the points that I made.

And features from SX OS have been integrated into Atmos (cheat engine) - who really cares (only the SX OS haters, that's who!)? I'm certain earlier version of Tinfoil and other third party installers had support for split NSP and XCI files many, many months previously.

It's almost like complaining if Windows added something like EXT4 support and all the *NIX and Apple users were boo hooing and throwing tantrums.

Again, grasping for thin straws. First point I can entirely dismiss as Atmosphere isn't the target here. Also tinfoil has no relevance here either.

Except, they'd require actual effort to port the codebase of Windows. Since SX OS is based off Horizon. It's an easy copy and paste session.

That's ok, no one ever for an instant thought you would keep quiet about a new release from TX. We could sense the pressure building up from the other side of the planet.

lmao ok. I didn't start shit talking until bad stuff actually started to happen and even then it was mild comments until my summary.

 

[Espen84]

I did the same with mine. Tried to update mi emunand 8.1 (sysnand also 8.1) with Choi on sxos 2.9. It just got stuck on flashing.. so I shut it down. When I tried to boot, I just got black screen. Then I booted with holding the up volume, in to sxos menu.. from there I deleted the emunand.. rebooted in to sxos tried first sysnand just to make sure, seemed ok.. so I made a new emunand ( on so card, not hidden) some prosess and still failed.. did this all over but not on sxos 2.8 beta. Now it upgraded firmware as it should.. it rebooted to black screen. (Got a bit scared then) but then I remember I am on sxos 2.8 that don't support fw 9.0.. so I added the boot.bin 2.9 and all seems good at last. I see people had som issues with xci and gamecard. But I don't know, seems ok here... at least what I can see.. did trie a gamecard, it worked, I did tried a xci, worked. So don't know seems okey.

 

[ian2009]

Is the team xecuter site down for anybody else?

 

[JoeBloggs777]

Is the team xecuter site down for anybody else?

working ok for me, but i'm using a vpn

 

[Espen84]

I did the same with mine. Tried to update mi emunand 8.1 (sysnand also 8.1) with Choi on sxos 2.9. It just got stuck on flashing.. so I shut it down. When I tried to boot, I just got black screen. Then I booted with holding the up volume, in to sxos menu.. from there I deleted the emunand.. rebooted in to sxos tried first sysnand just to make sure, seemed ok.. so I made a new emunand ( on so card, not hidden) some prosess and still failed.. did this all over but not on sxos 2.8 beta. Now it upgraded firmware as it should.. it rebooted to black screen. (Got a bit scared then) but then I remember I am on sxos 2.8 that don't support fw 9.0.. so I added the boot.bin 2.9 and all seems good at last. I see people had som issues with xci and gamecard. But I don't know, seems ok here... at least what I can see.. did trie a gamecard, it worked, I did tried a xci, worked. So don't know seems okey.

I did see something about burning GC fuses, if you trie a gamecard in sx 2.9.and that it GC will not work on lower firmware. So basically I'm F*** couse I did not read that before after.. but i don't get all crazy about it either, as long as it at least work on 9.0 and later.. don't use GC anyway, did not even know GC had fuses to burn before today so

 

[ian2009]

Thanks, just used my vpn add-on and it worked, i guess my ISP has blocked it.

 

[Essasetic]

Is the team xecuter site down for anybody else?

TX blockade got applied to the UK. It'll permanently be down unless you use a VPN.

 

[Badder]

I was stuck at the Nintendo logo black screen loop after updating my switch sx is 2.9 to firmware 9.0.0 with ChoidojourNX 1.01 fortunately i could still boot into rcm so I booted up atmosphere like the other post said and updated my firmware through choidojourNX 1.02 and it works fine now.

 

[tpax]

I'm on 8.1 (not using emunand) and 2.8 now. What's the definitive way to update to 9.0 and 2.9?
Use 2.8 and CDJ 1.0.1 to update the fw, and then boot with 2.9?

 

[SpiderPig2810]

I can not boot to atmosphere. But why? I used a tutorial from this forum to use both atmosphere and SX OS side by side. I followed the instructions and got to the point where atmosphere tries to load, i also got the logo screen and so on. But then i get a grey screen with a lot of messages (from atmosphere) that i can push the power button to restart or hold with vol + button and so on.....

How can i get atmosphere running? I have no idea what's SysNAND oder EmuNAND or so.

There was no problem in the past for upgrading. How can i downgrade to 8.1 without the opportunity to boot up OFW, Sx OS or atmosphere? Is my Switch bricked?

 

[Badder]

Was stuck on black screen after Nintendo logo when I tried to upgrade firmware to 9.0.0 with sx os 2.9 choidujourNX 1.01 so like another post mentioned I booted atmosphere and installed firm 9.0.0 again with choidujourNX 1.02 and it works fine again.

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

I can not boot to atmosphere. But why? I used a tutorial from this forum to use both atmosphere and SX OS side by side. I followed the instructions and got to the point where atmosphere tries to load, i also got the logo screen and so on. But then i get a grey screen with a lot of messages (from atmosphere) that i can push the power button to restart or hold with vol + button and so on.....

How can i get atmosphere running? I have no idea what's SysNAND oder EmuNAND or so.

There was no problem in the past for upgrading. How can i downgrade to 8.1 without the opportunity to boot up OFW, Sx OS or atmosphere? Is my Switch bricked?

I don't know much so I probly won't be much help lol but I did have some error when trying to boot atmosphere whole a game cartridge was in my switch so I removed the game and rebooted my switch and it worked fine.

 

[NeroAngelo]

That's because SX OS isn't really designed with homebrew in mind

I usually do the update and homebrew stuff with Atmo linked to my SXOS emuNAND, then switch back to SXOS for the gaming

 

[roamin]

It's the weekend, not everyone works 24/7 - though why some companies release major patches / updates for any product on a Friday is beyond me.. It means if there are problems their support and devs aren't around to quickly address issues until 2 days later.

When your software is killing people's switches you better start working 24/7.