Hardware:
Laptop: ThinkPad T470p (Type 20J7S0QH00)
Sensor: 138a:0097 Validity Sensors, Inc., bcdDevice 1.64
Device serial: ff1b8019142e
OS: Ubuntu 26.04 LTS ("Resolute Raccoon")
What happened:
I initially (mistakenly) used 3v1n0/libfprint's validity-sensors-tools.initializer snap instead of this project. It ran a factory reset, then failed pairing repeatedly with:
Exception: Unexpected TLS version 4 0
after 5 retries.
I then removed that tool and installed the correct stack (open-fprintd, fprintd-clients, python3-validity via ppa:ubuntuhandbook1/open-fprintd, since the official PPA doesn't yet support 26.04). Since then, every attempt — including factory-reset.py — fails with:
Exception: Failed: 0401
This happens even after doing a full BIOS-level fingerprint reset (Security → Fingerprint → Reset Fingerprint Data on the T470p), so it's not a leftover software/USB state issue — I've ruled out driver conflicts, stale USB sessions, and service race conditions.
Raw trace (via playground, tls.trace_enabled=True, usb.trace_enabled=True):
open9x()
DEBUG:root:>cmd> 3e
DEBUG:root:<cmd< 0104
Exception: Failed: 0401
The device responds promptly (no timeout) — it's explicitly returning a failure status on the very first get_flash_info call, before any pairing/TLS negotiation happens.
What I no longer have: I don't have a working Windows install on this machine to re-pair through the genuine Synaptics driver, so I can't recover that way.
Given that this looks like a corrupted/inconsistent partition table left over from the earlier failed pairing attempt (similar to issues #55, #87, #129), would it be possible to push a corrected partition table for this device, similar to what's been done for others in this tracker? Happy to provide any additional trace/log output needed.
Hardware:
Laptop: ThinkPad T470p (Type 20J7S0QH00)
Sensor: 138a:0097 Validity Sensors, Inc., bcdDevice 1.64
Device serial: ff1b8019142e
OS: Ubuntu 26.04 LTS ("Resolute Raccoon")
What happened:
I initially (mistakenly) used 3v1n0/libfprint's validity-sensors-tools.initializer snap instead of this project. It ran a factory reset, then failed pairing repeatedly with:
Exception: Unexpected TLS version 4 0
after 5 retries.
I then removed that tool and installed the correct stack (open-fprintd, fprintd-clients, python3-validity via ppa:ubuntuhandbook1/open-fprintd, since the official PPA doesn't yet support 26.04). Since then, every attempt — including factory-reset.py — fails with:
Exception: Failed: 0401
This happens even after doing a full BIOS-level fingerprint reset (Security → Fingerprint → Reset Fingerprint Data on the T470p), so it's not a leftover software/USB state issue — I've ruled out driver conflicts, stale USB sessions, and service race conditions.
Raw trace (via playground, tls.trace_enabled=True, usb.trace_enabled=True):
The device responds promptly (no timeout) — it's explicitly returning a failure status on the very first get_flash_info call, before any pairing/TLS negotiation happens.
What I no longer have: I don't have a working Windows install on this machine to re-pair through the genuine Synaptics driver, so I can't recover that way.
Given that this looks like a corrupted/inconsistent partition table left over from the earlier failed pairing attempt (similar to issues #55, #87, #129), would it be possible to push a corrected partition table for this device, similar to what's been done for others in this tracker? Happy to provide any additional trace/log output needed.