TX is back with a major update to your favorite SX Installer app.
And with the release of v2.0.0 that means a lot of very nice new features.

It has been a while since SX Installer was updated, but earlier today TX released v2.0.0 which brings with it a number of nice improvements as you can see in their changelog below, and one of the amazing new features is that you can now upgrade and downgrade your Switch firmware with ease and safety, as simple as installing a NSP game on your Switch!

• Added XCI installation
• Added on-the-fly standard crypto install
• Standard crypto conversion hard drops minimum firmware requirement
• Added socket.json for fine tuning socket settings
• Added system firmware version check before installing
• Added google drive directory and file support
• Plugging in USB cable without SX Server no longer hangs SX Installer
• Added ability to reset minimum version nag in the application record.
• Fixed an out of memory crash.
• Added stability for 8.1.0 firmware.
• Improved Korean Translations.
• Added firmware installation.
• Added dropbox support. url syntax: dropbox:/token:here@/
• Miscellaneous bug fixes..
• Enabled compression on database files.
• Added hosts for custom host entries.
• Fixed game launching.
• Improved stability.
• Added ability to install save game at time of install.
  (unzips titleid.zip in the NSP to the games save)
• Added ability to install save games from zip files.
  (title id must be in brackets i.e. "doom fix [010018900DD00000].zip)"
• Fixed error installing certain titles over USB.

That's all for today. Stay tuned!

Source: MaxConsole

 

[NoNAND]

Some people don't want to enable AutoRCM though...
Maybe they replaced the switch bootloader

Highly unlikely but feasible
However that would require some exceptional skill and knowledge to pull that off.
Not even the big dev guys haven't achieved something as a permamant bootloader

 

[Deleted User]

Highly unlikely but feasible
However that would require some exceptional skill and knowledge to pull that off.
Not even the big dev guys haven't achieved something as a permamant bootloader

Probably would brick the switch if they did though.

 

[bodefuceta]

Probably would brick the switch if they did though.

This brick wouldn't be different than autoRCM. I'm fairly sure wasn't done because the bootloader is signature verified.

 

[Deleted User]

This brick wouldn't be different than autoRCM. I'm fairly sure wasn't done because the bootloader is signature verified.

AutoRCM needs a payload to launch into Horizon, we are talking about the SX payload replacing the switch one.

 

[bodefuceta]

AutoRCM needs a payload to launch into Horizon, we are talking about the SX payload replacing the switch one.

autoRCM is, itself, a brick.

 

[Deleted User]

Also, people stop getting salty about SX OS, 'they stole code' well, they don't care. Most people don't, even SciresM doesn't care about his code stolen. Everyone one can choose their own CFW, Atmosphere or ReiNX for general homebrew, SX OS for piracy and messing around.

 

[wiewiec]

So waiting for someone to test this upgrade/downgrade feature

 

[Deleted User]

autoRCM is, itself, a brick.

No, AutoRCM modifies the system so that the bootloader panics. And throws you into RCM, RCM isn't a brick. (Only half-a-brick in iPatched systems)

 

[Josshy0125]

So waiting for someone to test this upgrade/downgrade feature

Me too! Haha! It'd be nice to be able to coldboot!

 

[bodefuceta]

No, AutoRCM modifies the system so that the bootloader panics. And throws you into RCM, RCM isn't a brick. (Only half-a-brick in iPatched systems)

No, this thread explains why autoRCM can definitely be called a brick.

 

[jaysea]

I think the upgrade and downgrade function is only really usable if you are on emunand. On sysnand it would be too dangerous. Also if you boot in ofw after upgrading or downgrading, it will give problems. Downgrade would result in not being able to boot and upgrade would result in fuses getting burned.

 

[Deleted User]

No, this thread explains why autoRCM can definitely be called a brick.

The thread literally says the same thing i said.

 

[garyopa]

Some things to clear up.

There seems to be some confusion in this thread about the fuses and stuff.

The special firmware install feature on SX Installer automatically enables AutoRCM, and it will not install on iPatched switches.

You can downgrade even if your fuses are burnt, but you will only be able to boot using your SX Dongle or other payload system.

You can not boot OFW without RCM on a FW lower than your fuse count.

And for safely reasons we don't recommend going below v5.1.0

This feature is mainly aimed to make it easier to upgrade your firmware for those with banned Switch'es and for those running emunand not wisher to go online.

And the process is simple with one single nsp file instead of zip with bunch of firmware files, and it installs your firmware similar to how nintendo does it officially.

Downgrading is nice touch but does not get around any of the previous pitfalls that other downgrade methods allow, just makes it a bit simpler to operate and use.

 

[Essasetic]

Some things to clear up.

There seems to be some confusion in this thread about the fuses and stuff.

The special firmware install feature on SX Installer automatically enables AutoRCM, and it will not install on iPatched switches.

You can downgrade even if your fuses are burnt, but you will only be able to boot using your SX Dongle or other payload system.

You can not boot OFW without RCM on a FW lower than your fuse count.

And for safely reasons we don't recommend going below v5.1.0

This feature is mainly aimed to make it easier to upgrade your firmware for those with banned Switch'es and for those running emunand not wisher to go online.

And the process is simple with one single nsp file instead of zip with bunch of firmware files, and it installs your firmware similar to how nintendo does it officially.

Downgrading is nice touch but does not get around any of the previous pitfalls that other downgrade methods allow, just makes it a bit simpler to operate and use.

Agree with everything you've said. But why not downgrade below 5.1.0? If your fuses aren't burnt then you can access some cool warmboot exploits on 4.1.0 and below.

 

[Smellysocks84]

What i am waiting for is any progress on the patched switches out there. They have multiple times claimed to have done some progress, and a solution will Come.. But first time thay Said so was over a year now.. So i start to think thay loose that battle

 

[Deleted User]

Agree with everything you've said. But why not downgrade below 5.1.0? If your fuses aren't burnt then you can access some cool warmboot exploits on 4.1.0 and below.

The more the better!

 

[bodefuceta]

The thread literally says the same thing i said.

From that thread: "About the term "brick": There are two kinds of brick, a semi-brick and a full brick." autoRCM is the first.
From you: "RCM isn't a brick"

Are you illiterate?

 

[Deleted User]

What i am waiting for is any progress on the patched switches out there. They have multiple times claimed to have done some progress, and a solution will Come.. But first time thay Said so was over a year now.. So i start to think thay loose that battle

There is dejâ vu for 1.0.0-4.1.0

SciresM said that after 7.0.1 the console may never be hackable.

 

[Smellysocks84]

What i am waiting for is any progress on the patched switches out there. They have multiple times claimed to have done some progress, and a solution will Come.. But first time thay Said so was over a year now.. So i start to think thay loose that battle

But tjen thay should Just say so. "sorry, we have lost. Dont know what to do with it"

 

[hippy dave]

• Added ability to install save game at time of install.
  (unzips titleid.zip in the NSP to the games save)

Did you actually mean in the NSP? Or was it meant to say in the NSP folder or something? While it would be perfectly possible to add a zip file to a rebuilt NSP it sounds like a weird thing to do to me.