Well you can still get banned for even just running CFW regardless if you're offline because it leaves traces in your console but the bigger red flag is transporting a modded save to an unhacked console. Nintendo can tell if its been modified or not so you're risking getting the unhacked console banned.
If its an unpatched console, you can update your firmware 13.2 but no games require that high of a firmware plus you will burn fuses if update it before you hack it so unless you have a reason you wish to update, I would hold off.
Hey Draxzelex!
https://gbatemp.net/threads/switch-noob-paradise-ask-questions-here.488277/post-9678065 (Follow the link that goes to the guide)
Nintendo Switch firmware files are copyrighted material so they are treated the same as pirated games meaning it is against the rules to help you find them or even ask where to locate them.
Hey Microchipman,
DISCLAIMER: Only try this if you understand what I am explaining.
Considering how hard it is to actually brick a Nintendo Switch and the many ways to recover from a theoretical brick, I am doubtful you bricked your last console but I digress. As long as you make an eMMC backup with Hekate, you can recover from 99% of all potential bricks. You need BOOT0, BOOT1, and either eMMC raw GPP or eMMC SYS. Keep in mind if you only dump eMMC SYS, you will be missing any content installed to your internal memory which includes any save data or games/updates/DLC.
While I don't know what servers are used to determine the date and time, people within the community developed tools to change the time without being punished. The first one is called switch-time; its an older homebrew application though so it may not work on the higher firmware versions. The other one is called QuickNTP and it uses the overlay Tesla to sync the time. Both of these should be able to accomplish what you are looking for.
Well Hekate not only verifies the eMMC backups it makes but it also verifies them when you restore it so as long as Hekate doesn't throw any errors, that's all you need.
Fuses only matter if you want to be able to boot the console normally in order to use a better exploit that may be discovered in the future that only works on certain firmware versions. Fuses in relation to recovering from a brick by restoring an old eMMC backup are a minor inconvenience. The same principal that allows us to update without burning fuses can literally also be applied to booting lower firmware versions than the fuse count; all custom bootloaders bypass the fuse check. However if you try to boot the console normally while on a higher fuse count, you may encounter a soft brick because the console will not proceed past a black screen. This is where having something like AutoRCM is handy because it ensures you will be able to always use a custom bootloader to bypass the fuse check no matter what your firmware is. That being said, this doesn't mean that we can freely downgrade because using a custom bootloader is still using an exploit to boot the console on lower firmware versions with high fuse counts so it would be redundant to combine this with an exploit on lower firmware versions.
