Brand new Switch, currently hackable. Update or not?

[Dudemeister]

Hi Guys, brand new here. I just bought a brand new Switch, and based on the serial number (XAW700150xxxxx), it should be hackable, so I'm about to order a SX Pro.

Meanwhile, I tried browsing through the console, and just about everything I do, says I need to upgrade, in fact it seems to have downloaded an update as soon as it connected to the internet. Using one of the tututorials I found here, I was able to delete the downloaded update.

The Switch currently has system 4.1.0, and I know the latets version of the software is 6.2.0. Would letting the switch update the software to 6.2.0 also update the firmware and prevent future hacking?

 

[Dudemeister]

SO basically wait until I get the SX OS Pro, then back up the existing firmware first. Do I update the firmware through the normal Nintendo OTA update, or do I have to do it off line using the SX OS.

I already downloaded the 6.2 firmware from the links here.

Also can you elaborate on the burnt fuses bit? Are you saying that the firmware update modifies the hardware ? to what end? prevent reverting back?

 

[imprezgc8]

If you are not worried about burning your fuses you can just update through nintendo, then make you nand back up on 6.2.

Alternatively you can follow this guide to update without burning your fuses. This makes it possible to downgrade if for some reason you need to, though it is not really recommended unless you are facing serious issues. If you follow this guide, back up your nand first so you have a backup of the older nand, then also make a back up of the nand after you update just to be safe. Make sure to label them after so you know which is which.

https://team-xecuter.com/community/...ned-nintendo-switch-with-choidujournx.128170/

To answer you question about fuses, yes there are efuses that get burned with almost every new firmware. It makes it so you cannot downgrade to an older firmware once the fuses are burned because each firmware is looking for a specific amount of fuses. If it detects more fuses than the firmware that is trying to boot, I believe it "panics" the console and it crashes or just stays at a black screen.

 

[ozzieSXOS]

my OFW is still on 4.0.1 , but honestly there is no need, just update to 6.2, do a Nand backup and then a Emunand

There are tiny physical fuses in your logic board. They are blown everytime you upgrade OFW. This is bypassed by using the choidujorNX app, which doesn't burn... but even so, if you boot OFW, it will check and blow the fuses anyway.

Best is to create an Emunand and update that... your fuses will never burn ever

 

[Dudemeister]

Thank you all for the feedback. As soon as I get the SX I'll do the update the "safe" way. If it can be done without burning the efuses, why not do it that way. I'm also thinking about doing a NAND backup for the current firmware (4.1.0), and doing another after the update to 6.2.0.

I also noticed Team-Executer just released a stable 2.5.2, which should be good to go with the latest. So it's just a matter of waiting for the hardware to come in.

Meanwhile, I also ordered a couple of 128GB Samsung Evo mSD's, which I plan on formatting to exFAT. Most of the images I have are NSP, and they are a lot bigger than 4GB that FAT32 would allow.

Speaking of NSP, Is there any reason why I should consider converting them to XCI?

 

[MorningBlunt]

Thank you all for the feedback. As soon as I get the SX I'll do the update the "safe" way. If it can be done without burning the efuses, why not do it that way. I'm also thinking about doing a NAND backup for the current firmware (4.1.0), and doing another after the update to 6.2.0. Makes sense, make sure you put backups on the cloud too just in case!

I also noticed Team-Executer just released a stable 2.5.2, which should be good to go with the latest. So it's just a matter of waiting for the hardware to come in. It is indeed.

Meanwhile, I also ordered a couple of 128GB Samsung Evo mSD's, which I plan on formatting to exFAT. Most of the images I have are NSP, and they are a lot bigger than 4GB that FAT32 would allow. Remember you can use external hard drives too!

Speaking of NSP, Is there any reason why I should consider converting them to XCI? NSP's can be ran without installing and without going into the TX menu (I guess like a .exe file on PC?), while XCI's need to be installed and selected from the TX menu before launching (It takes like 9 seconds). XCI's can just be deleted from the SD, while NSP's would need to be uninstalled, so it depends what you wanna do long term.

XCI = Cart image (Physical dump)

NSP = Nintendo Submission Package (eShop)