Android and Windows
I've managed to brick two computers in two months, and it wasn't even my fault!
I bought earlier in the year a new Android tablet, and each month the manufacturer issued a system update. After I applied the September update, the tablet would not reboot into Android. (See Figure 1.)
"No Command" means Android can't find the code it needs to finish booting
I spent quite a lot of time using different methods Android has for self-resuscitation, but to no avail. One brick.
Last week, the same scenario occurred in Windows. My $1000, 14-month-old Lenovo Yoga had a BIOS update from Lenovo. After applying it, Windows would not finishing starting up, complaining of an error. (See Figure 2.)
Windows giving bad advice on how to fix its problem
I have a System Restore USB that I made when I first got the Lenovo, but Windows wouldn't finish booting from it either, complaining of the same error. Two bricks.
For the Lenovo, my next step was to try to boot it with Linux on a DVD drive, but the machine refused.
I have heard of vendor updates bricking devices, most recently with Samsung SolidState drives (which I use in my computers exclusively). It is a sign of the complexity of our times that even vendor updates can no longer be trusted.
So take to heart my advice: "If the thing works, don't update it."