Hacking Discussion Where is SX OS and 7.0-1 Support?

[wurstpistole]

If its factually incorrect then kindly tell us who was first to exploit the switch.

Pegaswitch, probably. By SciresM and ReSwitched. May have heard that first name in connection with a certain cfw

 

[Goffrier]

i have reboot to payload working on reinx :smug:

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

it doesnt work for some people but for me it works™

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

just use secmon from ams

 

[Essasetic]

If its factually incorrect then kindly tell us who was first to exploit the switch.

Tell me what features atmos has that sx has included within its os.

Ohh wait.... rest my case.

Atmosphere has been in development and open source since May. So technically ScriesM and Reswitched was the first to release a proper CFW for the switch. (They were probably developing it way before May though).

For the first people to exploit it. Depends how you look at it. For the TSEC hexkyz has been attacking it since January. But for the Fusee exploit. Failoverflow were the first to report on it. And a few short months later it started being exploited.

Either way you look at it. TX weren't the first at anything that significant.

 

[ZachyCatGames]

If its factually incorrect then kindly tell us who was first to exploit the switch.

Tell me what features atmos has that sx has included within its os.

Ohh wait.... rest my case.

ReSwitched/SciresM exploited the Switch within a few months of it releasing (way before SX was even announced)

SXOS doesn’t have any debugging features, is missing multiple ams sysmodules, is missing exosphere, has no custom sysmodule loading, alot of their implementations of stuff are super buggy, they’re very late at adding features, it’s closed source, and has DRM. Also calling it an OS would be incorrect

 

[Goffrier]

yet sxos rocks!

 

[radicalwookie]

Reason 1) Not supporting Team X

Lol or actually being able to use cfw xD

 

[m4xw]

yet sxos rocks!

Rocking the Landfill in 2019 and beyond!

 

[Goffrier]

:shrek:

 

[thaikhoa]

Atmosphere has been in development and open source since May. So technically ScriesM and Reswitched was the first to release a proper CFW for the switch. (They were probably developing it way before May though).

For the first people to exploit it. Depends how you look at it. For the TSEC hexkyz has been attacking it since January. But for the Fusee exploit. Failoverflow were the first to report on it. And a few short months later it started being exploited.

Either way you look at it. TX weren't the first at anything that significant.

2nd Jan 2018
TX used to have their very first way to mount XCI on the first place (L R to switch between .xcis IIRC) then integrated the homebrew channel by using atmosphere sources.

 

[ZachyCatGames]

2nd Jan 2018
TX used to have their very first way to mount XCI on the first place (L R to switch between .xcis IIRC) then integrated the homebrew channel by using atmosphere sources.

The video you linked literally just shows a splashscreen then the regular qlaunch lock screen :thonk:

 

[thaikhoa]

The video you linked literally just shows a splashscreen :thonk:

I couldn't find out the video when they showed off the first way to mount XCI using L R buttons. Anyway, never mind... They won't have the wanted update anytime soon.

 

[ZachyCatGames]

Atmosphere has been in development and open source since May. So technically ScriesM and Reswitched was the first to release a proper CFW for the switch. (They were probably developing it way before May though).

The github repo was publicly put up in January 2018 and development started in January/february 2018

 

[Ita54_2]

SX OS with Atmosphere splash is no Problem i need only a working SX OS

 

[ScarletDreamz]

"Adopt"

 

[huma_dawii]

"Adopt"

OMG finally, its been FOREVER. I hope they bring some new features, otherwise I wont be able to understand the delay.

 

[ScarletDreamz]

OMG finally, its been FOREVER. I hope they bring some new features, otherwise I wont be able to understand the delay.

That was posted 2 weeks ago lolz.

 

[huma_dawii]

That was posted 2 weeks ago lolz.

Then that's a huge block... xD because we never reach the corner :v

 

[linuxares]

Why don't they release it as another beta if it now works? Just warn some features might not work?

 

[xabier]

I've cleaned up your post and struck through your incorrect text.


SX OS:

Pros:

XCI files - can mount and PLAY XCI files direct from USB (no need to copy to SD card).
- No need to install each game, just mount and they run - just like inserting a cartridge.
- XCI files do not install tickets so *POTENTIALLY* are not as detectable as NSP files.

USB storage - NSP files can be installed to SD card direct from USB storage, no need for PC. Useful on long journeys or selection from a large collection on the go.

EmuEMMC / emuNAND - makes it potentially possible to dodge a banned console due to no records kept in system NAND (online play under emuNAND not recommended however).
- different official firmware versions can be installed in system and emuNAND (no fuses are burned)
but difficult and the setup is a bit janky. not my experience with emuNAND creation in SX OS 2.5.3 was a few button presses and it was done.

Cons:

No official firmware 7.0 support as yet. Without this you can only use any of the existing 2000 or so titles available currently. NOTE that you CAN install titles and updates requiring firmware 7.x, as long as they are not encrypted with 7.x (as of 3/3/19 no titles are).

Costs money - about the same price as a 200GB SD card for the jig, the dongle and the SX OS licence.
- about the same price as a 128GB SD card for just the SX OS licence.

Cannot use KIPs advanced features - like custom kernel modules (Overclocking module, etc)

MUST use the jig and payload injector on every cold boot (personally, if you're powering off completely regularly then why?).



Free CFW:

Pros:

Official firmware 7.0 support and most likely ongoing support for the future.

No cost - just the included cost of your SD card for it to be installed on.

Can use KIPs advanced features - like custom kernel modules (Overclocking module, etc).

Can boot into CFW from Auto RCM - please note that auto-RCM has been extensively discussed as being potentially detectable by Nintendo and thus a bannable 'offence'.


Cons:

No XCI mounting.

No USB storage.

No emuEMMC / emuNAND.


Keep in mind that BOTH options allow installing of NSP titles to SD card and systemNAND (or emuNAND if using SX OS) via USB cable and NUT or SX server.

Both systems allow use of homebrew and backing up save games to alternate computers / storage for safe keeping.



If I've missed anything please let me know.


The age old question - which CFW should I use?

Look at the pros and con feature lists and see which features are must have items for you.


So *IS* SX OS worth purchasing RIGHT NOW?

Without official firmware support for 7.x it is a risky investment.

There is nothing stopping you to boot 7.0 ofw with sx dongle+hekate and autorcm

 

[Draxzelex]

Why don't they release it as another beta if it now works? Just warn some features might not work?

Probably because the most important feature, which is booting CFW, doesn't work. Assuming they (somehow) have that part down, the only other feature that would be broken is .NSP installation from the SD card as 7.0 broke that for both Tinfoil (not DZ) and Goldleaf but strangely not for DevMenu. Maybe they could tell people to use DevMenu like in the early days