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

 

[Lacius]

OK so i manages to go threw the booting screen with the sx logo and the options boot custom firmware boot official firmware but whatever i choose it just goes back to black screen

Do you have a NAND backup you can restore?

Hello guys,

If I am running Emunand and I would want to upgrade my firmware (currently on 7.1.0) using this tool, did I understand it correctly that autoRCM is going to get activated? I heard that its strongly adviced not to use AutoRCM in combination with Emunand. Would love to hear back from someone who upgraded from a lower firmware to a newer one and is running Emunand. Big thanks in advance everyone

Whatever you do on your emuNAND should not affect your sysNAND. In other words, it won't install AutoRCM if you're using your emuNAND.

 

[Deleted User]

Ok, im sorry. My intention was to help. Dont wont any drama.. Hehe. Trie to charge your dongle. But flashes green, dont that idikate that it injected the payload?

I have the same happen to me after firmware update, that its Black and i had some problem inject payload. But then i Just hold down power button for some time, and tried again, and it booted after some tries and errors if you mange to make it boot again, make a nand backup, so you can fix problems and dont brick your switch

Did you use this tool? If so which version were you and which version you up/down graded to?

Using hekate check your fuses?

I honestly don't know

 

[MITSMOUTS]

Do you have a NAND backup you can restore?


Whatever you do on your emuNAND should not affect your sysNAND. In other words, it won't install AutoRCM if you're using your emuNAND.

I dont have a nand backup neither do i have an emunand

 

[BATMAN-]

Do you have a NAND backup you can restore?


Whatever you do on your emuNAND should not affect your sysNAND. In other words, it won't install AutoRCM if you're using your emuNAND.

Awesome, thanks for the clarification!

 

[Lacius]

I dont have a nand backup neither do i have an emunand

Are you using the latest version of SX OS?

 

[Deleted User]

I dont have a nand backup neither do i have an emunand

Next time make a NAND backup.

 

[MITSMOUTS]

Are you using the latest version of SX OS?

yes the latest official not the beta

 

[Lacius]

yes the latest official not the beta

Use the latest version and try again.

 

[Smellysocks84]

OK so i manages to go threw the booting screen with the sx logo and the options boot custom firmware boot official firmware but whatever i choose it just goes back to black screen

Hmmm

Did you use this tool? If so which version were you and which version you up/down graded to?

Using hekate check your fuses?

I honestly don't know

No i used what it caled again.
ChoiDujourNX
somting.... And i update from 6.0 to 7.1 and then downgraded to 6.0 has some issues with 7.1 at the time. I did not burned my fuses, i was asure of that. But it had som issues after downgraded, but after som trives and errors it booted again.

 

[Deleted User]

Hmmm

No i used what it caled again.
ChoiDujourNX
somting.... And i update from 6.0 to 7.1 and then downgraded to 6.0 has some issues with 7.1 at the time. I did not burned my fuses, i was asure of that. But it had som issues after downgraded, but after som trives and errors it booted again.

To be sure boot into hekate and check your fuses.

 

[smf]

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

I gave up reading that thread when it says: It should go without saying but I’ll say it anyway: This method is very dangerous. It could brick your Switch even beyond recovery and RCM if something goes wrong.

I'd like to see some proof that you can do anything in RCM that would prevent RCM from launching.

It's not a brick, its an intentional recovery mode boot loop. I'd accept an argument that ipatched units are semi bricked. I'm not going to join an anti autorcm cult.

 

[MITSMOUTS]

Use the latest version and try again.

OMFG YOU ARE A GOD IT WORKED.
Thank you so much could i donate some money to your paypal to say ty i thought i was done.

 

[Deleted User]

I gave up reading that thread when it says: It should go without saying but I’ll say it anyway: This method is very dangerous. It could brick your Switch even beyond recovery and RCM if something goes wrong.

I'd like to see some proof that you can do anything in RCM that would prevent RCM from launching.

It's not a brick, its an intentional recovery mode boot loop. I'd accept an argument that ipatched units are semi bricked. I'm not going to join an anti autorcm cult.

I'm pretty sure the guy that sent that was a troll.

 

[Lacius]

OMFG YOU ARE A GOD IT WORKED.
Thank you so much could i donate some money to your paypal to say ty i thought i was done.

I don't need your money. I'm glad everything is working now.

If you don't want your Switch to coldboot into RCM, remove AutoRCM.

 

[MITSMOUTS]

I don't need your money. I'm glad everything is working now.

If you don't want your Switch to coldboot into RCM, remove AutoRCM.

Again i have no words to say..I appreciate your help a lot!

 

[Smellysocks84]

To be sure boot into hekate and check your fuses.

I was able to fix it on mine, Just saying that i had simular issues. And was able to get it back after som tries. I hope MITSMOTS DO the same. Dont wish a bricked switch on anybody..

Sadly i dont have my Old switch anymore, i gave mine to my nephew fore his birthday. And i bought a new/ used switch. And i manages to buy a patched switch with firmware 7.1 on it... Stupid me

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

I was able to fix it on mine, Just saying that i had simular issues. And was able to get it back after som tries. I hope MITSMOTS DO the same. Dont wish a bricked switch on anybody..

Sadly i dont have my Old switch anymore, i gave mine to my nephew fore his birthday. And i bought a new/ used switch. And i manages to buy a patched switch with firmware 7.1 on it... Stupid me

At least the serial number say its patched on some sites. I have t tried to inject payload. But i guess i dont need to trie aither so.... Sad...

 

[Deleted User]

I was able to fix it on mine, Just saying that i had simular issues. And was able to get it back after som tries. I hope MITSMOTS DO the same. Dont wish a bricked switch on anybody..

Sadly i dont have my Old switch anymore, i gave mine to my nephew fore his birthday. And i bought a new/ used switch. And i manages to buy a patched switch with firmware 7.1 on it... Stupid me

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



At least the serial number say its patched on some sites. I have t tried to inject payload. But i guess i dont need to trie aither so.... Sad...

use this website if you want;
https://ismyswitchpatched.com

 

[Lacius]

I gave up reading that thread when it says: It should go without saying but I’ll say it anyway: This method is very dangerous. It could brick your Switch even beyond recovery and RCM if something goes wrong.

I'd like to see some proof that you can do anything in RCM that would prevent RCM from launching.

It's not a brick, its an intentional recovery mode boot loop. I'd accept an argument that ipatched units are semi bricked. I'm not going to join an anti autorcm cult.

AutoRCM is an intentional softbrick that allows for a convenient way to enter RCM. As you said, it's an intentional RCM bootloop, and that's a softbrick. AutoRCM itself should always be able to be removed, and it's is relatively safe. There used to be concerns regarding the ability to charge a dead battery in a system with AutoRCM installed, but those concerns ended up being unfounded.

If AutoRCM is somehow installed onto a patched system, I can't think of any way to recover from that kind of brick without a hardmod.

That all being said, in principle, a malicious RCM payload could potentially fry hardware components, but I'm unaware of this ever having happened.

 

[Smellysocks84]

Again i have no words to say..I appreciate your help a lot!

Make a nand backup and use emunand, then you shoul be quite safe in the future. And do a backup after every firmware update..

 

[Deleted User]

AutoRCM is an intentional softbrick that allows for a convenient way to enter RCM. As you said, it's an intentional RCM bootloop, and that's a softbrick. AutoRCM itself should always be able to be removed, and it's is relatively safe. There used to be concerns regarding the ability to charge a dead battery in a system with AutoRCM installed, but those concerns ended up being unfounded.

If AutoRCM is somehow installed onto a patched system, I can't think of any way to recover from that kind of brick without a hardmod.

That all being said, in principle, a malicious RCM payload could potentially fry hardware components, but I'm unaware of this ever having happened.

AutoRCM could be fixed if signed code was injected.