Ok. What happens if I backup on 4.1.0, update to current OFW, and later wish to restore using the backup I made? Is this a situation where I must use the method that does not burn fuses?
You would have to update without burning fuses if you wish to restore your backup on 4.1. Otherwise, you have to make a new backup if you update with burnt fuses because your console won't boot with a 4.1 backup and the current number of burnt fuses required on 5.1
Is going online after update w/o burning fuses equivalent to going online after doing an official update?
You're good. It should be around 29 GB in size uncompressed.
Not entirely since you will have less burnt fuses than you should which makes going online with that not 100% safe but no one has been banned yet due to this alone so its considered safe for now.
Outside of what Shourk3n said, it would also help if you told us the last things you remembered about the Switch scene. Its not like we catalog everything that happens here on a calendar or something.
The only thing I recalled was the ktemin drama. Then everyone went off to make their own Atmosphere spin-offs, and then just yesterday was the fake CFW, and now Fake DevMenu.
Oh something else that happened was there was this supposed crack of SX OS released but it was really an irreversible brick code unless you made a full backup beforehand. You can read about it here: https://gbatemp.net/threads/anybody-bricked-with-the-fake-sx-payload.512285/ The end of the thread has a link to the GitHub page of the code used to brick the consoles.
Ahhh, I see now.
How so? When it came to the Wii and Wii u the word implies that the devices were factory and not once modified.
https://gbatemp.net/threads/switch-hacking-101-how-to-launch-the-homebrew-menu-on-all-fw.504012/
It's assumed to be stored somewhere in the NAND but there are no tools that can erase that data. And as long the NAND backup was made before you began hacking, all traces should be gone.
Make the NAND backup as soon as possible. The more homebrew and hacks you perform on the console, the greater the risk of getting a ban would become. The bare minimum hack needed to backup the NAND is running the bootloader known as Hekate which is included in that tutorial. Its the first thing it has you do for good reasons outside of avoiding a ban.
