How to update from already hacked switch 10.0.1 to 10.0.2 without formating or losing games/saves

https://switch.homebrew.guide/usingcfw/manualupgrade

 

Are you using a Clean SysNAND / Dirty EmuMMC setup? If so, and you don't care about burning fuses (I don't):

First make sure you're on the latest version of your CFW (Update Atmosphere/Kosmos/SX OS.)

Update your SysNAND to the latest version.

Then, you can inject TegraExplorer: https://github.com/suchmememanyskill/TegraExplorer/releases
Select Tools->Dump Firmware. This will dump the update files from your SysNAND to your SD Card.

Then boot into your CFW with EmuMMC and run ChoiDujourNX: https://switchtools.sshnuke.net/
Then you can use those dumped files to install the system update on your EmuMMC.

For more, see this guide page:
https://nh-server.github.io/switch-...-dumping-an-updated-firmware-from-your-sysmmc

 

System Settings -> System -> System Update

 

Just use ChoiDujourNX, the link arianadark gave explains everything you need to know.

 

not quite sure if this is the right place for it please let me know or move if necessasary.

so i recently bought a switch witch cfw already on it and a rcm loader included. which was what i was looking for since i don´t know much about this. and when i casuallly looked at hacking a switch i found the whole process really confusing with google searches making me even more confused and often turning up contradictory advice. hence the pre hacked switch from ebay. the card is full with all kinds of stuff i´d say it´s littered with programs mostly also duplicates of tools. but no games
so i downloaded some games. starting sxos with the rcm loader was easy enough. but of the 20 games i tried only 2 of them worked. 15 said they were damaged and needed redownloading and only 2 actually made sense with their error message since they said something about updating the firmware. i´ve used hacked psps and vitas before so this made sense but of course i knew i couldn´t just update normally since this would destroy the hack. but when looking this up people said it´s not a problem as long as your cfw supports the firmware but other people said pretty much the opposite.
i´ve already updated sxos to the newest firmware (3.05) which should support the latest ofw 10.2.00
i already got the firmware but i´m hesitant to use it. the guide here says something about using ChoiDujour for that which happens to be already on the card but it also says to give it permission to write to bis (whatever that is) by placing a flag in my athmosphere folder so does this only work with atmosphere and not with sxos?
or can i just ignore this on sxos?
it also says somethign about auto rcm and ipatched consoles so what is a ipatched console? it clearly isn´t a patched console since those can´t be hacked i thought.
other guides talk about updating my emunand or sysnand or both with hekate no idea what that is or why that matters is this a hekate thing that can be ignored on sxos?
so do i need hekate or atmosphere or both for that?. other guides also strongly advice to back up my nand(s) / emummc before that by reading out the keys. which keys? and why does it matter?

 

^ this

 

The whole "not burning fuses" thing is dumb at this point... we have physical modchips now, that information about burning fuses is trash. Just keep your system fully up to date, and you'll have far less issues with OFW and CFW in general.

 

so you´re saying i can ignore all that and just update via the normal switch menu? that sounds too easy to be true somehow.
whats ChoiDujour for then? is it just in case you got a banned switch and can´t update officially?

 

Not quite, even with a modchip the chip doesn't store data about the fuse, you can't boot higher firmware on lower fuse count on OFW.

 

There are still problems associated with updating online. For one, it exposes your console to a risk of a ban since you're connecting a hacked console to Nintendo's servers. Secondly, updating online normally burns your fuses preventing you from downgrading. While we do have modchips nowadays, very few people have the ability to install them and there is also no objective benefit in burning fuses. Its always better to have as little fuses burnt as possible. We also don't know what the future holds as an untethered coldboot exploit could be released tomorrow on a very specific firmware version.

 

Atmosphere prevents fuse burning when updating online (by preserving autoRCM) and it has done so for more than 18 months. Get with the times.

 

What I'm saying is there's no need or reason to keep the lower fuse count to boot lower FW/CFW. You either stay updated, or run into problems from not updating. Staying updated is the best thing right now. Fixes most problems with games not booting.

 

That is true but some people like to preserve their fuse so they can go back to lower firmware.

 

Also some people (like myself) would literally have to go out of their way and send extra time to burn fuses

 

Nobody mentioned updating in Atmosphere except you. Your username really fits you if you remove the k.

 

thanks for the replies guys but you seem to be having a nice chat amongst yourselves without really adressing my original post ^^
you´re talking to a noob here please have mercy.

the modchip is kind of expensive and i´m quite sure i´d turn my switch into some kind of modern art installation if i tried to solder it myself.

yeah that´s why i was holding off on just updating it without further research. i take that to mean booting into cfw without manually injecting a payload each time you turn it on. like on the vita for example. the contingency might be a remote one but still if possible without too much hassle i´d like to avoid it.

so as i was asking in my orignal post do i absolutely need atmosphere for that? i was talking about sxos since it bootet wthout problems for me and the update was easy . when i tried to boot athmosphere just out of curiousity i was greeted with a host of error messages and missing files warnings. also what´s autorcm ? the guide linked above mentioned to avoid checking the auto rcm box since it could brick my console but that was when using ChoiDujourNX and you were talking about updating online with athmosphere so i don´t know if these are related at all.

also i don´t even know if my switch is banned in which case i presume i couldn´t use the official update?. it might very well be. i bought it half a year ago and believe it might have been banned since it was really cheap and i couldn´t care less about playing online anyway. that i might need to use the official update function never even occured to me.

so if i´m able to officially update under sxos i couldn´t go back to a lower firmware. but i could with atmosphere?
and what about using ChoiDujourNX with sxos can i ignore the bis flag and leave the auto rcm unchecked?

the guide said Hekate, ReiNX and SXOS bypass these fuse checks and the fuse burns but when was this guide written does this apply to the newest 3.05 version of sxos too? to prevent burnign fuses i need to enable auto rcm it seems but if i enable autorcm on an ipatched switched i might end uo with an overoriced paperweight.
what is an ipatched switch and how do i find out if i got one?

other guides talk about updating / backing up my emummc and / or sysnand with hekate no idea what that is or why that matters. is this a hekate thing that can be ignored on sxos?
so do i need hekate or atmosphere or both for that?

 

The only other ways to hack the console involve using Pegascape if your firmware is 4.1 and below which requires being tethered to a Wi-Fi network or installing a modchip which requires soldering. The first method is arguably worse than Fusee Gelee (e.g. pushing a payload) since you can just buy a dongle and inject payloads on-the-go and the second method requires skill. Outside of those two, there are no signs of any better or alternative exploits so if you're waiting for a better one, that day may never ever come.

• There are a few different ways of updating without burning fuses. One is using ChoiDujourNX. Another method involves installing system updates while running Atmosphere and having AutoRCM pre-enabled. And the way AutoRCM works is that it technically bricks your console in that it will not boot without sending a payload
• There are several different types of bans however the most common type does not prevent system updates so you can be banned but be able to update online
• SX OS does not protect BOOT0 which is where AutoRCM is enabled but Atmosphere does hence why updating in Atmosphere and not SX OS will prevent your fuses from being burnt. If you use ChoiDujourNX and leave AutoRCM enabled, then your choice of CFW is irrelevant
• Unless TX took out the fuse code, newer versions would carry on with features introduced in older updates
• Patched units are not susceptible to the Fusee Gelee exploit which is where you send payloads. Typically users check to see if it is patched before they buy a console by checking the serial number here. This however is not a guaranteed method as the only way to be sure is to try sending a payload
• All of your console's files are stored on your eMMC. If your console is bricked and you do not have a copy of these files, then your system will become a paperweight. This is why all guides recommend you to backup your eMMC. Also there is no such thing as "sysNAND" as the Switch does not use a NAND chip, it uses an eMMC. You can use either Hekate or SX OS to make a backup of the eMMC but its recommended to use Hekate as it verifies the dump. Also several of TX's top members were arrested so its possible that SX OS will stop being updated