Skip to content

138a:0097 (ThinkPad T470p) stuck with Failed: 0401 on get_flash_info after mismatched pairing attempt + BIOS reset #275

Open

Description

@Hammamjs

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.

Activity

  1. Dasero197 commented on Aug 1, 2026

    @Dasero197

    Hello,
    If you encounter initialization errors with python3-validity after resetting or clearing your BIOS, the reader may lose its initialized state and fail to re-initialize under Linux alone.

    Passing the USB fingerprint reader through to a QEMU/KVM Windows VM does not work. The reader must be loaded on a native / bare-metal Windows environment (e.g., dual-boot or Windows To Go) for the hardware provisioning to succeed.

    Workaround Steps:

    1. Boot into a native Windows environment (dual-boot, Windows To Go USB, etc.).
    2. Install the official fingerprint drivers for your device.
    3. Enroll at least one fingerprint in Windows Hello to trigger the hardware re-initialization.
    4. Clear/remove the enrolled fingerprint once Windows confirms it works.
    5. Reboot back into Ubuntu.

    Upon returning to Ubuntu, python3-validity should function normally without the initialization error.

    Technical Hypothesis:

    python3-validity and VM USB passthrough setups appear unable to perform the low-level firmware/hardware provisioning required by the reader after a hard BIOS reset. The proprietary HP driver needs direct, bare-metal access under Windows to initialize the chip at the lowest level.

    I have tried this on my Hp Elitebook 850 G5 with this sensor (138a:00ab Validity Sensors) and it worked.
    Good Luck

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions