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

 

[ganons]

it would seem this new SX breaks custom XCI files as a clean rip of lets go works but a custom one does not same with my smash bros

What did you do on your custom xci? Game + update?

 

[rmorris003]

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??

Yes I followed the guide and I am up and running after using 2.8 to flash the 9.0 and links awakening xci loads fine.
I didnt lose any data and just didnt copy the user/safe folder that doesnt exist in the firmware backup that was supplied to me.

 

[Budsixz]

I dont even know why people want to update to 9.0 for now
Yea sx is having probs for now but i think it would work fine with 8.0.1 (I use atmos BTW)
Just stay low till everything is fixed. No games need 9.0 anyways

 

[TheCyberQuake]

I dont even know why people want to update to 9.0 for now
Yea sx is having probs for now but i think it would work fine with 8.0.1 (I use atmos BTW)
Just stay low till everything is fixed. No games need 9.0 anyways

Honestly, this. Even for atmosphere people were just dying to update. Unless you are using online services, there's kinda no reason currently to update to 9.0.0. The keys are only required by one game DLC right now afaik, and nothing else. And typically it will take a bit for both games and homebrew/cfw to update anyway, so no real point in doing so.

 

[gizmomelb]

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.

I'll have to re-read then.. as the posts I've seen all indicated they had issues updating their emuNAND with choidujoir 1.01 and it freezing. Not updating their sysNAND.

SonyUSA presented a nice step by step guide to repairs and it worked for the person who first posted they had problems updating (kudos SonyUSA).


The animosity between homebrew developers is escalating to BOTH sides actively implementing DRM so their homebrew will not work on the other CFW and that type of tribalism is pitiful. This is supposed to be a community, instead there have been specific individuals who have actively and consistently decided to shitpost and divide the users since the release of an alternative - specifically taking offence that it is a paid product. I've been around computers since the 1970s and there have been pay for pirating solutions for every single PC, handheld or console.. so while the technically knowledgable people can whine about it there have been solutions specifically for the non-technical which cost. Hell even for the technically knowledgable I'm sure there have been users who have paid OTHERS to program and instal modchips, assist them with the soft hacking etc. just because they weren't 100% certain they were doing the right thing. Just like I'm sure loads of older users on here would also admit to charging other people money to hack their systems for them over various consoles, over the years.

 

[Essasetic]

The animosity between homebrew developers is escalating to BOTH sides actively implementing DRM so their homebrew will not work on the other CFW and that type of tribalism is pitiful.

I have not seen one piece of homebrew that has been specifically made to not work with SX OS

 

[gizmomelb]

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.

that was good foresight on the atmos devs, kudos to them. Hopefully there are maintainers / devs of general homebrew who update their software so then we can all enjoy their work on the console we enjoy.

 

[TheCyberQuake]

I'll have to re-read then.. as the posts I've seen all indicated they had issues updating their emuNAND with choidujoir 1.01 and it freezing. Not updating their sysNAND.

SonyUSA presented a nice step by step guide to repairs and it worked for the person who first posted they had problems updating (kudos SonyUSA).


The animosity between homebrew developers is escalating to BOTH sides actively implementing DRM so their homebrew will not work on the other CFW and that type of tribalism is pitiful. This is supposed to be a community, instead there have been specific individuals who have actively and consistently decided to shitpost and divide the users since the release of an alternative - specifically taking offence that it is a paid product. I've been around computers since the 1970s and there have been pay for pirating solutions for every single PC, handheld or console.. so while the technically knowledgable people can whine about it there have been solutions specifically for the non-technical which cost. Hell even for the technically knowledgable I'm sure there have been users who have paid OTHERS to program and instal modchips, assist them with the soft hacking etc. just because they weren't 100% certain they were doing the right thing. Just like I'm sure loads of older users on here would also admit to charging other people money to hack their systems for them over various consoles, over the years.

I honestly don't know anything about homebrew DRM. Afaik as long as a cfw is designed to work properly with libnx and it's libraries, none of the mainstream homebrew options have DRM. I could be wrong, so I would love an explanation for that.

 

[Essasetic]

This is supposed to be a community, instead there have been specific individuals who have actively and consistently decided to shitpost and divide the users since the release of an alternative - specifically taking offence that it is a paid product.

Let me just state the irony that you're posting this in a thread. To a company that has done little to nothing for the homebrew community.

 

[Foxi4]

You people do realize this time around it took them longer to update for a newer firmware because atmosphere basically kept the fixes for 9.0.0 private until they were ready to release. There's plenty of evidence showing they've been stealing atmosphere code.
And not only that, this update is buggy af, causing more bricks than I've ever seen in a public release of anything. Wow. Good job TX, and the staff here that get paid to white-knight for them.

I don't care what people do. I just think it's dumb to pay for software that's stealing most of it's codebase from free open source software. Which has been proven in multiple ways. And then people acting like because it's a beta it's okay for the crapton of bricks currently happening because people are listening to advice given by them. Yeah, that's beyond being in "beta", that's just being bad software.

Speaking of the staff shilling, let's do some of that. As some users explained to you, SX OS offers certain features that they consider to be valuable and worth paying for. These are features that Atmo doesn't have, not necessarily because it can't, but because it won't, for legal and ethical reasons, which is understandable. SX OS does share a significant portion of its code (or at the very least its general solutions) with Atmo, regardless of whether TX is willing to admit that or not, but I'm not particularly shocked by that considering the primary purpose of the software - let's just say that it surprises noone. It's a matter of preference, people are entitled to spend their money however they want, even in ways that you'd personally consider wasteful. Is this something worth arguing about? Probably not. Hearing about the installation issues and the various bugs is worrisome, and it's valuable information - arguing with other users about their preferences isn't.



Now, where's my check?

 

[gizmomelb]

I have not seen one piece of homebrew that has been specifically made to not work with SX OS

I can't recall if it was checkpoint or edizon, I'll need to look back to confirm.

 

[Essasetic]

I can't recall if it was checkpoint or edizon, I'll need to look back to confirm.

I'll let you check but I'm almost certain that neither of those put DRM so it purposely wouldn't work with SX OS. If it doesn't, there's likely a good reason behind it (probably like Checkpoint).

 

[OuahOuah]

I'm always reading at those new SXOS release threads just to read nolife trolls like @TheCyberQuake
So thanks for not deceiving me

 

[gizmomelb]

Let me just state the irony that you're posting this in a thread. To a company that has done little to nothing for the homebrew community.

you mean like how most I.T businesses have done nothing for homebrew communities? So should Nintendo be supporting the homebrew community? Should Sony? Should Microsoft? Granted there aren't many paid for piracy apps around, I'd have to go hunting most likely in the satellite TV area to find if any of the companies who make and sell sat tv decoders (without you needing to pay for subscription access) have ever done anything to benefit their community.. and I'm guessing it would be a "no".

 

[Essasetic]

you mean like how most I.T businesses have done nothing for homebrew communities? So should Nintendo be supporting the homebrew community? Should Sony? Should Microsoft? Granted there aren't many paid for piracy apps around, I'd have to go hunting most likely in the satellite TV area to find if any of the companies who make and sell sat tv decoders (without you needing to pay for subscription access) have ever done anything to benefit their community.. and I'm guessing it would be a "no".

Except, unlike Microsoft, Sony and Nintendo. They're a hacking company. Just the ethically wrong kind. They've had multiple opportunities to help out the homebrew community (and to be fair they did contribute to the bounty). But, what else have they done apart from that?

 

[TheCyberQuake]

I'm always reading at those new SXOS release threads just to read nolife trolls like @TheCyberQuake
So thanks for not deceiving me

Don't know how I've been trolling when I've just been using reasoning. Especially given just above I also state that an atmosphere setup is also not perfect.
I just don't think it's acceptable for a company to release software, even in beta, which includes advice that causes a massive bricking event. I would be giving crap to atmosphere or whatever other software if a similar event happened to this scale.

 

[gizmomelb]

I'll let you check but I'm almost certain that neither of those put DRM so it purposely wouldn't work with SX OS. If it doesn't, there's likely a good reason behind it (probably like Checkpoint).

ok, it is Edizon - from their wiki - https://github.com/WerWolv/EdiZon/wiki

"Q - FEATURE XYZ DOESN'T WORK ON MY SWITCH WITH SX OS! PLZ FIX!
A - No. We're not going to fix any issues related to SX OS. There are multiple reasons for this: First, SX OS is bad. If you want to pirate games, go ahead and use it but don't expect EdiZon or ANY other homebrew app to work on it. SX OS uses a lot of code from Atmosphere and other Open Source projects but the way they use it breaks a lot of homebrew apps. Secondly, neither do I have SX OS nor am I willing to get it so we can't test it on there anyways. TLDR; SX OS -> Shit -> I don't care about it."


So not direct DRM (my mistake with wording) but lack of compatibility with the nebulous "SX OS uses a lot of code from Atmosphere and other Open Source projects but the way they use it breaks a lot of homebrew apps."

Please, I would really like to know a solid definition or explanation from any developer - please what does SX OS do wrong so homebrew does not work? This is a serious question, the same as to why apparently the dreamcast emulator will not work under SX OS? Are there missing libs? Are functions not implemented in SX OS?

 

[TheCyberQuake]

ok, it is Edizon - from their wiki - https://github.com/WerWolv/EdiZon/wiki

"Q - FEATURE XYZ DOESN'T WORK ON MY SWITCH WITH SX OS! PLZ FIX!
A - No. We're not going to fix any issues related to SX OS. There are multiple reasons for this: First, SX OS is bad. If you want to pirate games, go ahead and use it but don't expect EdiZon or ANY other homebrew app to work on it. SX OS uses a lot of code from Atmosphere and other Open Source projects but the way they use it breaks a lot of homebrew apps. Secondly, neither do I have SX OS nor am I willing to get it so we can't test it on there anyways. TLDR; SX OS -> Shit -> I don't care about it."


So not direct DRM (my mistake with wording) but lack of compatibility with the nebulous "SX OS uses a lot of code from Atmosphere and other Open Source projects but the way they use it breaks a lot of homebrew apps."

Please, I would really like to know a solid definition or explanation from any developer - please what does SX OS do wrong so homebrew does not work? This is a serious question, the same as to why apparently the dreamcast emulator will not work under SX OS? Are there missing libs? Are functions not implemented in SX OS?

Honestly, imo, it's broken because SX OS doesn't do a good job of implementing homebrew. And unfortunately, I'm lead to believe that it's because their cfw is piracy first, homebrew second. Let's be real. A majority of people buy SX OS for the piracy, not the homebrew. Which is a shame, but it's the developers first priority over homebrew support. Multiple other cfw support homebrew perfectly fine, it's mostly SX OS that seems to have problems. I wouldn't be able to say why as I don't fully understand the atmosphere code and the SX OS code is closed source. But in theory anything that properly uses libnx and it's output NRO files would be able to run homebrew. Maybe I'm wrong, but that's the way I see it right now.

 

[gizmomelb]

Except, unlike Microsoft, Sony and Nintendo. They're a hacking company. Just the ethically wrong kind. They've had multiple opportunities to help out the homebrew community (and to be fair they did contribute to the bounty). But, what else have they done apart from that?

they released their USB libs so any homebrew could have USB accessibility under SX OS (which may or may not be locked to other functions only in SX -ie XCI loading, I don't know).

The main things people across both CFWs wanted was cheat modes, USB loading, XCI support and backing up save games etc. Now pretty much both CFW have those features, so again it all comes down to choosing what you want and whether you choose to spend time (atmos) or money (SX OS) to do it the easiest way that suits the end user.

It's hard to find a direct simile but hopefully this is close - you can choose to pay for netflix yourself, pay a bit to a friend to share their legit account, or download all shows via torrents. Whichever way suits you best for time vs money vs ease of use.

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

Honestly, imo, it's broken because SX OS doesn't do a good job of implementing homebrew. And unfortunately, I'm lead to believe that it's because their cfw is piracy first, homebrew second. Let's be real. A majority of people buy SX OS for the piracy, not the homebrew.

I agree totally with the reasons people buy SX OS. While it may be a fun diversion to play Quake or some old emulated game on the Switch, frankly we've either all seen and or done it before a hundred times across tablets, watches, PC, refridgerators etc. There aren't any killed homebrew apps, if there were - they'd be commerically sold.

But as for your first sentence - "it's broken because SX OS doesn't do a good job of implementing homebrew" - we see that repeated on these forums from time to time, but what does it actually mean? In a previous reply I've posted I'd love a dev to actually explain why it doesn't do a good job of homebrew - is it missing libraries or functions, un-implemented system handlers or permissions? I'd like to know the why and not just opinions - I'm like that with general news as well. Opinion pieces mean nothing to me, give me the source and I'll research and make my own decision.

 

[TheCyberQuake]

I agree totally with the reasons people buy SX OS. While it may be a fun diversion to play Quake or some old emulated game on the Switch, frankly we've either all seen and or done it before a hundred times across tablets, watches, PC, refridgerators etc. There aren't any killed homebrew apps, if there were - they'd be commerically sold.

But as for your first sentence - "it's broken because SX OS doesn't do a good job of implementing homebrew" - we see that repeated on these forums from time to time, but what does it actually mean? In a previous reply I've posted I'd love a dev to actually explain why it doesn't do a good job of homebrew - is it missing libraries or functions, un-implemented system handlers or permissions? I'd like to know the why and not just opinions - I'm like that with general news as well. Opinion pieces mean nothing to me, give me the source and I'll research and make my own decision.

Unfortunately there's really no good way for us to know why it isn't working because SX OS is closed source. So it's up to SX OS devs to figure it out as we have no real way to look at how they are implementing it and in turn why it is broken. The atmosphere code and libnx is public, so you could see what works, but no good way to figure out why SX OS isn't working because you can't compare the two.