The Nintendo Switch itself is USB-C, but the SX Pro is Micro-USB. You can even charge the SX Pro without it being inserted into the Nintendo Switch.
thanks, man. I'm pretty ignorant about switch hacking, so I'm trying to take in what I can for when the day comes that I do hack my switch. I'll most likely buy a banned switch for that and just use it test games before actually buying them.
It lacks user customization meaning you will have to use the same settings for the CFW each and every time you boot it up while all other CFW allow you to freely customize what you load in their own various ways. For example, LayeredFS has problems with certain games so you can manually disable that with other CFW such as ReiNX (by moving fs_mitm.kip, which enables LayeredFS, from /sysmodules to /sysmodules/dis) or Atmosphere (through launching a launch configuration that doesn't enable LayeredFS via Hekate).What does SXOS lack that other CFW have? Anything worth having a separate sd card for?
For example, LayeredFS
Seems like more work to me but that was just one example. There are plenty of other patches that you can customize with other CFW such as nogc, fs.kip, autoboot, boot time, custom splash screens, etc.Yeh but technically I can just rename (using NX Shell) the “titles” folder in sd:/sxos/ and that will disable mods? Not disable, but the path will be wrong, making it not work...
YesIs it possible store more than one payload on a microSD card from the SX Pro, and load one from it?
Sent from my SM-T280 using Tapatalk
you want to connect you notebook to the switch to use the games on the notebook hardisk to play troogh the switch ?Quick question . . . . Can SX Installer be connected to a PC through a USB connection? I haven't been able to find an answer for that anywhere. I'm assuming it is for external storage on the dock.
EmuNAND being on the SD card means a copy of your eMMC raw GPP exists on your SD card. And your eMMC raw GPP is comprised of 2 partitions, one of which is only empty space reserved for installed content aka the USER partition. This is what the installation is referring to when it asks internal memory/console. Installing it to the SD card would refer to the space not taken up by the EmuNAND partition. If installing content while in EmuNAND, they go into the Emutendo folder.I have installed Emunand Image on SD card, but when installing games on EMUNAND it still asks where i wanted to install the game, MicroSD or Console, since the emunand is emulated on micro sd why it asks me if a want to install pirated games on console , it is safe if a choose to install on console by mistake ?
EmuNAND being on the SD card means a copy of your eMMC raw GPP exists on your SD card. And your eMMC raw GPP is comprised of 2 partitions, one of which is only empty space reserved for installed content aka the USER partition. This is what the installation is referring to when it asks internal memory/console. Installing it to the SD card would refer to the space not taken up by the EmuNAND partition. If installing content while in EmuNAND, they go into the Emutendo folder.
Its your choice of whether you want to install to your SD card which the space is shared between SysNAND and EmuNAND or to internal memory where it will use up the empty space within your EmuNAND partition. The location doesn't matter outside of that.So, for properly use of Emunand image, i should select to install directly on console or it doesnt matter
you want to connect you notebook to the switch to use the games on the notebook hardisk to play troogh the switch ?