The EFI variables are just that. <i>Variables</i> not an entire firmware. I think this is where you confusion is. What is happening here is that these variables are presented to the user as a filesystem under &#x2F;sys. If you run &#x27;rm -rf &#x2F;&#x27; (or even &#x27;rm -rf &#x2F;sys&#x27;), you will start &quot;deleting&quot; these variables (which I assume either sets them to a null-equivalent value, or somehow removes them entirely from wherever they are stored). It sounds like:<p><pre><code>  rm &#x2F;sys&#x2F;efivar&#x2F;MyVariable
</code></pre>
is roughly equivalent to:<p><pre><code>  var obj = {MyVariable: 1};
  obj.MyVariable = null;
</code></pre>
or:<p><pre><code>  var obj = {MyVariable: 1};
  delete obj.MyVariable;
</code></pre>
This bricks the firmware, because some of these variables end up being required. It&#x27;s on the firmware maker &#x2F; motherboard manufacturer to make sure that there is a way to recover from this rather than having the firmware fail to startup because some variables are missing.<p>My understanding is that firmware made to spec would <i>not</i> brick over the the EFI variables getting wiped. The motherboards that are encountering these issues are running firmware that is cutting corners. Unfortunately cutting corners and ignore specs is nothing new for hardware manufacturers who are more concerned with the manufacture of the physical devices and usually put only the minimum amount of effort into getting any sort of software components (firmware, OS device drivers, etc) running.