4 ms·

But bricking retroactively in the field is a bad move, and sends even more anger and RMA requests back towards parties. https://github.com/therealdreg/ftdibric

by kotaKat 12d ago

But bricking retroactively in the field is a bad move, and sends even more anger and RMA requests back towards parties. https://github.com/therealdreg/ftdibrick https://github.com/therealdreg/ftdibrick Pepperidge Farm remembers the FTDI driver bricking.

undersuit 12d ago
It's not bricked retroactively from what I've read.
- kotaKat 12d ago
  https://github.com/raspberrypi/rpi-eeprom/issues/761 https://github.com/raspberrypi/rpi-eeprom/issues/761 If someone gets updated in the wild (like this person did without realizing they had a counterfeit board), they'll fail to boot.
  - undersuit 12d ago
    Consider that that happened a year ago and this submission may be about the fix.
    - abracadaniel 12d ago
      The "fix" in the thread is just not updating ever again.
      - undersuit 12d ago
        There is no fix that can be suggested in that thread. Pi LTD doesn't have the modified RAM Pis to test their firmware against nor should they be required to support modified hardware.
kiicia 12d ago
gateway 3ds tried to brick 3ds-es of users of cloned cards, bricked whole swaths of actual users instead https://www.eurogamer.net/3ds-flashcard-includes-secret-kill-switch-that-bricks-handhelds https://www.eurogamer.net/3ds-flashcard-includes-secret-kill...