AutoRCM is a soft brick from my understanding, what I want to know is if there is any way to permabrick with autorcm.Yes you can and that is the third option for being able to update your firmware without burning fuses. The problem is that method relies solely on your jig. That is to say if your jig fails to boot RCM, your fuses will be burnt so unless you have a jig with 100% efficacy, its an incredibly big risk which is pointless when there are safer and far more effective methods available. You see threads like that all the time where the user is not able to boot back into RCM despite using the same jig again. And that's because jigs cause wear and tear on your right Joy-Con rail so there is no jig with 100% effectiveness meaning its a big risk if you want to update this way.
Also, the device is technically already bricked from AutoRCM. I don't see how it can get any worse than that.
Post automatically merged:
Are your fuses burnt? Not sure why I would go into emunand to update, emunand is already on latest FW. My sysnand is on 4.x while I decide if I want to burn fuses or get autorcm.Some people are still holding onto hope that a coldboot exploit will come out for fw ~4.0 or some such, and they don't want to burn fuses. The stock option in Hekate prevents fuses from being burned, on top of preventing AutoRCM from being overwritten. Maybe even prevents the game slot from being updated.
I think it's all a big hassle and just boot OFW to update, then dump the update to install in emummc.
AutoRCM is technically a brick. Done on purpose. As long as you keep a backup of boot0/boot1 on your computer, you can always fix it within nyx.