As far as I can tell, you took two tutorials mixed up the steps to go into the most unfitting order - without outright bricking the process - then opted to go with a package not to have to learn which software does what, then opted to use a service website for that, then wanted an insurance policy on not being bricked by a malicious intent that - in all fairness is covered by your nand backup.
Then didnt mention anything about your firmware version or your want to be able to downgrade eventually - then wanted someone to walk you through the process once more - personally.
What you'll get as a result in most cases, is people giving you a thumbs up - when you didnt just manage to destroy your device.
So thumbs up.
- How about you perform a nand backup as soon as you got hekate booting? I know - its so sensible - lets see how far back you can move it until things start to break.
- How about you use a 32GB sdcard formated to exfat for that (hekate has its own exfat driver support), so you can have "the most easy way to restore your nand backup" - and a second fat32 card for your daily operation, that is less prone to file corruption. Because if you stay on exfat, you may bother people in here with file system issues eventually - to which they will tell you "start over" - and if you skip your easily resorable nand backup, you'll might be under an actual risk to brick your switch.
- How about you dont activate autorcm until the very last step, or until - you use choixdujournx to update your current firmware? (in which case choixdujour will set it by default and you optionally save a step)
- How about you kick those "package deals" into the wind, and actually use a tutorial that tells you which files from whom you put where to do the things they are supposed to? Because later down the road, package people tend to update parts of a package to be "more current" - that might conflict with kips, causing package people to complain that "stuff dont work" - having no idea why waiting for people to tell them, that they are now reliant on an update to their package again. This is the hardest one to argue for, because I understand peoples need for most easy - but if things break, they literally have no idea where to start.
- How about you configure 90DNS first, because if you misstep in any of the following steps, and actually boot into Atmosphere there is a (at that specific point low) ban risk.
But then - if you expect us to give this spiel to every person that shows up with a "hey I read something, now I would do this - should I" spiel, you cant really expect that either - can you.
So consider yourself lucky, that you dindt just get the "thumbs up, you didnt brick your device" treatment.
Also you are missing a step, if you want to pirate - which by the sound of it you'd very much want to.
And - you'd want a virus scanner - because someone wrote brickware. Having no idea about virus propagation vectors, profitability of "virus creation", or working security measures (hint virus scanners dont work in general). Because?
Here is a deal. A guy wanted to be funny. Now hes been cast out of the scene, doxxed and shunned. And made no money. He maybe effected 0.01% of pirates. His actions where fixed by reapplying a nand backup. If you want to be the guy, who from now on wants to implement an additional step - before installing any nsp - be my guest (its very sensible of you) - but you could just as well take the chance, that this will never happen again. (Something about probability not being able to be applied to single occurrences.) But then it feels good to some people to play white knight and tell others to do an additional thing from now on so that they can be safe again. Its called security theatre.
(If you make it a checklist item at the "before release state" of certain sources, it is not - but if you expect everyone in the switch scene to to it - Id maybe expect a 1% adaption rate - until literally ever second nsp is brickware.)
Also - to write this a s negative for the nsp format - doesnt quite jell either. Ecxept for people that expect their formats to be artifically dumbed down to make them feel more secure. Capability is hardly ever a negative. If so - everyone on this earth would be on iOS and Chrome OS devices by now. (Wait a second...)
