Bricking is the loss of a device’s normal start-up path so completely that it behaves like a useless “brick.” In practice, the hardware may still have power, but its firmware, bootloader, or storage layout no longer lets the system initialize. This can happen after a bad update, corrupted flash memory, mismatched firmware for the wrong board revision, or a failed recovery attempt.
In cyber security, bricking matters because embedded devices often depend on exact software-hardware matches. Attackers may intentionally brick equipment to cause disruption or sabotage, while defenders worry about accidental bricking during patching, incident response, or reverse-engineering. Recovery usually depends on having a trusted restore image, a rescue mode, or low-level flashing access. If those are missing, a device can become permanently unusable even though its physical components are intact.