But how does that brick the device? I guess the hour counter overflows, goes negative and that screws up a calculation later on, causing the firmware to crash (over and over again..)
If only SSD vendors would do the usual cost-cutting measure of loading firmware from the host computer, this could be trivially fixed.
If only SSD vendors would do the usual cost-cutting measure of loading firmware from the host computer, this could be trivially fixed.