Repository navigation

Name the 50.43 firmware data lock instead of advising a charger cycle - #707

Open

kurexw wants to merge 6 commits into

OpenStrap:mainfrom

kurexw:fix/firmware-data-lock-status

Open

Name the 50.43 firmware data lock instead of advising a charger cycle#707
kurexw wants to merge 6 commits into
OpenStrap:mainfrom
kurexw:fix/firmware-data-lock-status

Commits on Nov 13, 2026
- Name the 50.43 firmware data lock instead of advising a charger cycle
  uvtqt
  committed
  e0cb953
- Merge remote-tracking branch 'origin/main' into fix/firmware-data-lock-status
  uvtqt
  committed
  5af5212
- Merge main into fix/firmware-data-lock-status
  uvtqt
  committed
  4c28d55
- Firmware lock: hedge the cause, clear stale firmware on other HELLOs
  
  uvtqt
  and
  claude
  committed
  2e19ff3
- merge main
  abdulsaheel
  committed
  9373193
- firmware lock card: charging or re-pairing is still worth a try, since the flags can't tell the lock from a real fault
  abdulsaheel
  committed
  0fdaf36