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

 

[jdmntvrd]

You were most likely on SX OS 2.9 using Choidujour 1.0.1 and it froze on Flashing Firmware 0/6 like a bunch of other people which is why you were not given the option to click on the "reboot" button on the lower right. If you needed to hard reset the switch that means the firmware installation failed. You will need to do a nand restore unless someone comes up with another solution. Once you restore your nand you can do the 9.0.0 firmware update using sx os 2.8 and choidujour 1.0.2 instead and then update the boot.bin to the latest sx os to 2.9 beta.

i do have a nand backup but i dont have a boot0 and boot1 backed up. can i just use that? or do i have to get the boot0 and boot1? if so, is there a way to get it? im assuming the boot0 and boot1 in my "bricked" switch wont work since its not even booting up.

 

[Ericthegreat]

No. You likely won't see anything for ipatched units on higher firmwares

Don't be silly, once someone on the atmosphere team figures it out, they'll update a few days later.

 

[dekuleon]

For anyone that has a bricked EMUNAND--

1. Update SYSNAND to 9.0 through Nintendo's regular method (if you have the option to/want to)
2. In SX bootloader, dump just the BOOT0 and BOOT1 (these will match your system and be good for 9.0 firmware)
3. Copy from SX\Backup to SX\emunand (rename the old boot0 and boot1 first!)
** Your EMUNAND should boot again but be kinda janky (no games work/xci mount) Homebrew is fine, back up your saves **
4. Boot into 9.0 with SXOS 2.9b and install Choi 1.01 and DOWNGRADE to 8.1 firmware
5. Reboot, system should be good now back on 8.1. Stay here or continue at your own risk!

6. Put SXOS 2.8b back on your SD card along with Choi 1.02 and boot it.
7. Update to 9.0 firmware while in EMUNAND and power down after the update
8. Put SXOS 2.9b on your SD and boot... pray!

Im locked in step 4... 2.9 booting my Emunand 9.0, Choi 1.01 and Downgrade do 8.1, same error, 0/6 Flashing and nothing.

 

[Jayro]

Always make a backup before doing anything to the NAND. Especially given SX OS usually doesn't play nicely with homebrew as it's not really designed with homebrew in mind.

More like people need to design their homebrew with SX OS in mind...

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

Then you haven't updated atmosphere. It's booted fine for many people, and hasn't caused the sheer amount of bricks when updating that SX OS has

What kind of idiot would update their OS within CFW? That's just asking for trouble!

 

[dsrules]

@garyopa , this happens when try to mount xci files converted from nsp

 

[TheCyberQuake]

More like people need to design their homebrew with SX OS in mind...

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


What kind of idiot would update their OS within CFW? That's just asking for trouble!

Actually, in atmosphere it's fairly safe if you don't pirate. And if you do, choi is statistically far less likely to brick in atmosphere.
Also, atmosphere is designed with homebrew in mind, thus homebrew almost always works on it. SX OS is designed with piracy in mind, not homebrew, thus homebrew is not the first thing they ensure is working. It's not the homebrew's fault that it's not working, it's SX OS for not properly working with current homebrew libraries.

 

[MasterJ360]

Fucking immature atmosshill cunts. Stop trolling and being childish. Let sx users enjoy what they want. You're the problem with this community. Idiots.

Sadly that wont ever stop. They have been shitpost these update threads since the very 1st sxos update. Reminding us yet again they stolen code and they waited after Atmosphere. They are just upset b/c the support is ongoing even if its a buggy beta.

 

[rmorris003]

I restored to 6.1 using this method https://switch.homebrew.guide/usingcfw/manualchoiupgrade#step-0-before-starting
Also found a 6.1 extfat firmware that someone posted on the dark site in my thread.

 

[Essasetic]

More like people need to design their homebrew with SX OS in mind...

I'm sorry I couldn't hold it back any longer.

 

[jackieleex3]

Has anyone try to use checkpoint on 2.9? I get an software error when I click it in homebrew

 

[evilone]

Currently is there any need for 9.0 ? Didnt saw any game which was needed. =)
But still thanks that the development continues, im really happy with SXOS.

 

[lamende]

I tried to update with ChoiDujourNX 1.01 and it froze at flashing firmware 0/6 now I can't get past the Nintendo logo it just goes black and no other cfw loads, I think I am corrupt. I had updated SX-OS first then rebooted/flashed. I also did not do a nand backup.

Edit- just read the previous pages and I should have read here first.

Did you fix your switch? I did the same thing as you... 8.1 w/ SX 2.9 tried to use Choi 1.0.1 to update to 9.0 and got stuck on 0/6 flashing firmware. Now I can't get past the Nintendo logo. Is there any way to fix this without restoring or updating sysnand? What is the fix for this??

 

[zahimi]

Correct way:
Sx 2.8
Choi 1.0.2
Update to 9.0.0
Shut down
Put 2.9 beta on sd card
Boot successfully with no problem.

follow this and you will be fine

thanks! works fine.

 

[SonyUSA]

Has anyone try to use checkpoint on 2.9? I get an software error when I click it in homebrew

All homebrew needs to be updated to work on 9.0 properly, and Checkpoint author got lazy so you must run it in app mode (highlight a game, hold R, launch it) to be able to even run it anymore

 

[SonyUSA]

I restored to 6.1 using this method https://switch.homebrew.guide/usingcfw/manualchoiupgrade#step-0-before-starting
Also found a 6.1 extfat firmware that someone posted on the dark site in my thread.

This looks good for a manual downgrade back to 6.1 and should save people but is much more complex. This is for SYSNAND and would be different for manually restoring EMUNAND so don't try it on EMUNAND because it will write to your SYSNAND ! Also if you have burned fuses past 6.1 you won't be able to boot SYSNAND without using CFW and then updating to 9.0 (or whatever fuse is set to).

 

[Hayro]

I'm on Sysnand (9.0) and EmuNAND (8.1.0 exfat)
I get error 2168-0002 (something like the cartridge error) when I try to access 9.0 on EmuNAND. My cartridge is empty.
I have an EmuNAND backup (8.1.0 exfat), so I'm fine but I really can't update to 9.0.

9.0 installation is always completed but I noticed this message like 4 times : error 0xe02 deleting unused.
8.1.0 EmuNAND + 2.8 boot + Choi (tried both 1.0.1 and 1.0.2) -> after 9.0 setup, I changed from 2.8 boot to 2.9 boot -> still getting error 2168-0002.

Is it possible that my NAND is corrupted even tho my 8.1.0 EmuNAND backup runs fine?
Also if you restore NAND while on EmuNAND, does it affect SysNAND (like downgrade)?

I'll stay on 8.1.0 for now.

Edit : Nevermind it works, make sure to delete your theme folder in titles if you have the same problem as me.

 

[jackieleex3]

Looks like xci is not working in 2.9.

 

[Bladexdsl]

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

who gives a fuck about homebrew we want to pirate!

 

[gizmomelb]

I haven't said anything mean, while you and other sx os users have thrown insults. I just call out bad things when I see them. I don't autmomatically support everything a company does just because I like them and use their product.
I know you don't like it, but frankly it's not good that people are bricking their switches literally following the instructions of TX. I don't know why you are defending that, because it genuinely is a bad thing that people are bricking their switches. That's not even me slandering, literally it's happening here on the forums.
You want to call out a company when they do something bad with the hopes they will improve, and until that happens they won't have any real reason to do so.

looking in the CFW forums and specifically at the atmos release thread there are a large number of posts from potential atmos users also experiencing a large number of issues upgrading to 9.0.0 and /or upgrading their installation of atmosphere CFW - please have a good look and let us know if there are any SX OS users in there throwing shade at those users or their choice of CFW or the CFW itself?

People are NOT bricking their switches - there are some users who have jumped the gun early and may have used incorrect versions of software and temporarily lost use of their emuNAND - not their sysNAND - so their systems are NOT bricked. It seems the SX OS community is working out ways to recover the emuNAND (particialarly if they were in hidden partitions) so they upgrade can proceed smoothly.

Should we be calling out atmosphere CFW for being bad and not easy to use, based on the number of help posts that are on here with users experiencing issues?

As for SX OS users throwing insults, frankly I cannot blame them - we are sick and fucking tired of arseholes continually throwing shit at us when the SX OS community generally do not do it to atmos users - as I've posted in other threads there was a period just after the 8.0.0 release where SX OS users had had enough and they did retaliate and posted shit to the atmos users in their threads and gave back what had been given to them.. If you want to start a shit fight then keep on throwing poop little monkey, but expect it to explode across every forum across GBAtemp.

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

View attachment 180814 @garyopa , this happens when try to mount xci files converted from nsp

will wait to see what NSC updates.. it might be an NSP to XCI conversion issue.

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

More like people need to design their homebrew with SX OS in mind...

there has already been discussion that libnx needs to be updated as Nintendo changed stuff in 9.0.0 - so unless the homebrew is recompiled with the newer libnx with 9.0.0 support it won't work correctly across any CFW.

 

[TheCyberQuake]

looking in the CFW forums and specifically at the atmos release thread there are a large number of posts from potential atmos users also experiencing a large number of issues upgrading to 9.0.0 and /or upgrading their installation of atmosphere CFW - please have a good look and let us know if there are any SX OS users in there throwing shade at those users or their choice of CFW or the CFW itself?

People are NOT bricking their switches - there are some users who have jumped the gun early and may have used incorrect versions of software and temporarily lost use of their emuNAND - not their sysNAND - so their systems are NOT bricked. It seems the SX OS community is working out ways to recover the emuNAND (particialarly if they were in hidden partitions) so they upgrade can proceed smoothly.

Should we be calling out atmosphere CFW for being bad and not easy to use, based on the number of help posts that are on here with users experiencing issues?

As for SX OS users throwing insults, frankly I cannot blame them - we are sick and fucking tired of arseholes continually throwing shit at us when the SX OS community generally do not do it to atmos users - as I've posted in other threads there was a period just after the 8.0.0 release where SX OS users had had enough and they did retaliate and posted shit to the atmos users in their threads and gave back what had been given to them.. If you want to start a shit fight then keep on throwing poop little monkey.

First off, the difference here is slight problems with atmosphere vs actual bricks. And you seem to have not read through this thread, because many of the bricks in here are on sysNAND, not "just in emuNAND". Recoverable yes, but annoying and difficult to work with. So while yes atmosphere does have problems (or rather, the software being used in conjunction with atmosphere, not atmosphere itself), it's usually fixed by updating other homebrew, or disabling a simple setting in hekate/fusee-primary. These problems exist because the fact that atmosphere is opensource means that there is a bunch of developers working on various projects and software to work with atmosphere. Which means greater customization with how it functions. This does unfortunately mean that sometimes these pieces don't work properly together when one is updated without updating another. But as stated before, the fixes are almost always as simple as deleting a file or folder, or changing a setting within the bootloader. So while it does have it's problems that I totally agree with you about, it's not the same degree as bricking your emuNAND, or what some people on here have, bricking your sysNAND. You can't treat these two problems the same because they are radically different in the complexity of fixing the problem.

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

there has already been discussion that libnx needs to be updated as Nintendo changed stuff in 9.0.0 - so unless the homebrew is recompiled with the newer libnx with 9.0.0 support it won't work correctly across any CFW.

Actually, atmosphere took that into account BEFORE release, and added a stop-gap interpreter that would allow all homebrew to still work without updates in 9.0.0. So actually that is wrong, they still work in 9.0.0 because of that, at least for the no input problem you are referring to.