Spank
Well-Known Member
There's a post on the very first page of this thread of an OTA update downloading, the aircard eating shit immediately afterwards, and the resulting update bricking the device. And while a dead aircard isn't the only reason for a failed update, it is the most common. This is because UConnect updates also update firmware on the aircard and the update process isn't developed in a way to deal with that failure properly. There's also the possibility that an aircard going bad (but still works generally for GPS) corrupts an update download which also results in bricking the device.Sure, maybe. But none of us here did that, I don't think. We all got the OTA update and woke up to a white screen.
Regardless of such, how the update is delivered is irrelevant. My original reply was a comment on the update process itself and how it's poorly written. A dead aircard or bad download shouldn't brick a device during an update and the software should be written in a manner to restore its previous state regardless.
Sponsored