DIY firmware tool safety checks #30

Open
opened 2026-04-05 17:53:51 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @ButterscotchV on 3/4/2026

DIY Firmware tool has 4 massive problems right now:

  1. There's no warning or mention at all of the fact that you can absolutely brick your trackers by configuring it wrong, so people may just think it's fine and mess stuff up
  2. There's no safeguards whatsoever for official trackers, specifically at least automatically warning for v1.0-v1.1 vs v1.2 trackers, despite the fact that we can easily differentiate them in software
  3. The firmware version list starts with the oldest one first, so people end up selecting firmware v0.7.1 despite v0.7.2 also being listed below
  4. Only trackers that have fully connected show up, so in the case that a tracker does get configured incorrectly, it won't be able to be re-flashed using the DIY tool and you must go to the more manual OTA tool or USB flashing to recover it
*Originally created by @ButterscotchV on 3/4/2026* DIY Firmware tool has 4 massive problems right now: 1. There's no warning or mention at all of the fact that you can *absolutely* brick your trackers by configuring it wrong, so people may just think it's fine and mess stuff up 2. There's no safeguards whatsoever for official trackers, specifically at least automatically warning for v1.0-v1.1 vs v1.2 trackers, despite the fact that we can easily differentiate them in software 3. The firmware version list starts with the oldest one first, so people end up selecting firmware v0.7.1 despite v0.7.2 also being listed below 4. Only trackers that have fully connected show up, so in the case that a tracker *does* get configured incorrectly, it won't be able to be re-flashed using the DIY tool and you must go to the more manual OTA tool or USB flashing to recover it
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/SlimeVR-Server#30