Skip to content

Add support for sensor type 0xd51 (138a:00ab HP 840 G5, 06cb:00b7 HP G6) - #256

Open
SimpleX-T wants to merge 42 commits into
uunicorn:masterfrom
SimpleX-T:feat/sensor-type-0xd51
Open

SimpleX-T wants to merge 42 commits into
uunicorn:masterfrom
SimpleX-T:feat/sensor-type-0xd51

Conversation

@SimpleX-T

Copy link
Copy Markdown

Summary

Adds support for sensor type 0xd51, which covers at least two USB IDs in the wild:

  • 138a:00ab — HP EliteBook 840 G5 (Synaptics "VFS7552 Touch with PurePrint")
  • 06cb:00b7 — HP G6-series laptops (Synaptics fingerprint reader [HP G6])

Verified working end-to-end on 138a:00ab (HP EliteBook 840 G5, Ubuntu 25.10): enrollment, verify (matches the correct finger, rejects others), and PAM-based sudo fingerprint auth. 06cb:00b7 is included by symmetry — same sensor type, same chip family — but I do not have that hardware to test on; would appreciate verification from the reporter of #225.

Closes #181 · Closes #225 · Closes #238

Why this is non-trivial (the missing piece)

Several users have previously tried the obvious patches — adding the PID to SupportedDevices, aliasing the crypto blob to blobs_97/blobs_9a, spoofing the sensor type to 0x199 — and consistently hit a wall where the service starts but fprintd-verify hangs forever or enroll-retry-scan loops indefinitely. Issue #225 documents exactly this flow.

The actual blocker is a protocol-level difference in interrupt delivery, not calibration or blobs:

The 0xd51 chip does not emit the b[0]=2 "finger detected" interrupt during a capture. It sends the start-ack (b[0]=0), and then jumps directly to b[0]=3 capture events. Sensor.capture()'s while True: if b[0]==2: break loop therefore hangs forever, even though everything else is working.

Once that loop is taught to also accept b[0]=3 (and pass the interrupt through to the next loop so it isn't lost), the rest of the existing pipeline — TLS-wrapped commands, image capture, the on-chip matcher, enrollment template accumulation — works correctly. The 0x199 alias for type, capture program, and calibration switch is enough for the matcher to accept real fingerprints and reject wrong ones.

What changed

File Change
validitysensor/usb.py Add DEV_AB = (0x138a, 0x00ab) and DEV_B7 = (0x06cb, 0x00b7) to SupportedDevices
validitysensor/blobs.py Route 0x00ab → blobs_97, 0x00b7 → blobs_9a. Verified accepted by the 0xd51 chip cleartext during init
validitysensor/firmware_tables.py Map both new IDs to HP's xpfwext filename (6_07f_hp_cmit_mis_qm.xpfwext, extracted from HP softpaq sp135736.exe). 0xd51 ships with firmware pre-loaded so upload_fwext returns early in normal use
validitysensor/sensor.py (a) Add 0xD51 to line_update_type1_devices. (b) In Sensor.open(), save the real device type and alias 0xd51 → 0x199 before downstream lookups (no native SensorTypeInfo/SensorCaptureProg exists for 0xd51). (c) In Sensor.capture(), accept b[0]=3 in the wait-for-finger loop only when the real device type is 0xd51, and pass the interrupt through to the wait-capture-complete loop so it isn't consumed twice
debian/python3-validity.udev Add 138a:00ab and 06cb:00b7 to the auto-start match block

Constraints and design choices

  • The interrupt-handling change is gated on self.real_device_type == 0xd51. Existing chips (0090/0097/9a/9d) take the unchanged code path. No behavioral change for users who aren't on this sensor type.
  • The 0x199 alias is a working compromise, not a perfect profile. A real SensorTypeInfo and SensorCaptureProg for 0xd51 would be better — extracting them from a Windows USB capture is the future work. Empirically the 0x199 profile produces images the on-chip matcher accepts; the 0xdb profile does not.
  • SensorTypeInfo for 0x199 is reused rather than introducing a new entry. The on-chip image processor uses the chip's own calibration; the wrong bytes_per_line is masked because matching happens on the chip side.
  • 0xd51 has no native SensorCaptureProg — the spoof lets the existing 0x199 program be reused. Comments in the code make this explicit so the future-correct fix is obvious.
  • No dev.reset() defensive patches in usb.py. Those were useful during development for recovering from unclean exits but shouldn't be on the normal-use path.

Test plan

Verified on Ubuntu 25.10 / kernel 6.17 / HP EliteBook 840 G5 (138a:00ab):

  • python3-validity.service reaches active (running) (previously failed at init_flash, sensor.open, or capture() depending on which patch combo was tried)
  • fprintd-enroll completes with real enroll-stage-passed events (not auto-completed fillers)
  • fprintd-verify returns verify-match for the enrolled finger
  • fprintd-verify returns verify-no-match for a different finger (proves the matcher actually distinguishes)
  • sudo -k && sudo whoami unlocks via fingerprint touch, no password
  • Captured image frames dumped via temporary logging show real fingerprint ridge data; enrollment templates (cmd6b responses) grow with each scan as features accumulate (5040 → 23304 bytes across 8 stages)

For 06cb:00b7: untested by me. The protocol-level fix is sensor-type-keyed and should apply, but matching specifically warrants verification from someone with the hardware.

Chip identification (for reference)

USB: 138a:00ab Validity Sensors, Inc. (HP EliteBook 840 G5)
Endpoints: 0x01 OUT bulk, 0x81/0x82 IN bulk, 0x83/0x84 IN interrupt (5 endpoints, vendor class)
identify_sensor name : "57K0 FM- 154-120"
device_info.type     : 0xd51
RomInfo              : timestamp=1415491824, build=164, major=6, minor=7, product=48
init_hardcoded blob  : blobs_97 (verified accepted, status 0000)
get_fw_info(2)       : returns valid partition info — firmware pre-loaded
TLS handshake        : ECDH P-256, succeeds against factory tls flash state

The 0xd51 chip does not emit the b[0]=2 "finger detected" interrupt
during capture, so the wait-finger loop in Sensor.capture() hangs
forever. Accept b[0]=3 as a substitute (gated on the real device
type so existing chips are unaffected) and pass the interrupt
through to the wait-capture-complete loop.

Also wires the two known USB IDs through SupportedDevices, blobs,
firmware_tables, the udev rule, and aliases sensor type 0xd51 to
the 0x199 profile so SensorTypeInfo / SensorCaptureProg lookups
succeed (no native profile exists yet).

Closes uunicorn#181
Closes uunicorn#225
Closes uunicorn#238
@DataConnection

Copy link
Copy Markdown

Thank you very much, @SimpleX-T! I was looking forward to use the fingerprint reader for 06cb:00b7 quite some time, and this looks promising!
Unfortunately it doesn't work out of the box - I get this error when running validity-sensors-firmware:

Traceback (most recent call last):
  File "/bin/validity-sensors-firmware", line 101, in <module>
    fwpath = download_and_extract_fw(dev_type, fwdir, fwuri=args.driver_uri)
  File "/bin/validity-sensors-firmware", line 39, in download_and_extract_fw
    fwuri = fwuri if fwuri else FIRMWARE_URIS[dev_type]['driver']
                                ~~~~~~~~~~~~~^^^^^^^^^^
KeyError: <SupportedDevices.DEV_B7: (1739, 183)>

Unfortunately I am unable to find the reason - my coding experience is not sufficient.

Without these entries `validity-sensors-firmware` crashes with a
KeyError for users on 138a:00ab and 06cb:00b7 who follow the README's
standard install flow. The 0xd51-family chips ship with firmware
pre-loaded so the downloader is only needed for factory-reset chips,
but the script should not crash.

Both PIDs point at HP softpaq sp135736.exe (the same blob extracted
to 6_07f_hp_cmit_mis_qm.xpfwext in FIRMWARE_NAMES). sha512 verified
against the canonical ftp.hp.com URL.

Reported by a 06cb:00b7 user on PR uunicorn#256.
@SimpleX-T

Copy link
Copy Markdown
Author

Hey @DataConnection, sorry, this is on me. When I added 06cb:00b7 to the supported devices list, I forgot to also add an entry to the firmware download table. That's exactly what that KeyError is telling us.

The good news: you almost certainly don't need to run validity-sensors-firmware at all. Your chip (the 0xd51-family one) ships with firmware already loaded from the factory. The downloader is only needed for factory-reset / unprovisioned chips. So just skip that step:

sudo systemctl restart python3-validity.service
fprintd-enroll
fprintd-verify

If fprintd-enroll asks you to swipe and fprintd-verify matches your finger, you're done — the firmware download wasn't needed.

If you hit a different error from that point on, paste the output and I'll take a look.

I pushed 20df336 to the PR branch - pulling the latest will give you a working validity-sensors-firmware too, in case you need it later.

SimpleX-T added 4 commits May 21, 2026 13:04
The chip's database rejects creating a second finger record with the
same subtype for the same user, which previously caused fprintd-enroll
to fail at the final stage with enroll-failed after all per-stage
captures had passed. Detect and delete any pre-existing record with the
same subtype right before db.new_finger.

Placing the delete here (inside do_create_finger, after all captures
have completed) rather than at EnrollStart matters: pre-deleting before
the enrollment session starts left the chip in a state where every
subsequent capture returned retry-scan indefinitely until the daemon
was restarted. By the time do_create_finger runs the captures are done
and the chip is ready to accept the save, so deletion at this point
doesn't disrupt session state.
Lenovo softpaqs (the previously supported devices) ship as Inno Setup
installers, which is what innoextract handles. HP softpaqs (sp135736.exe
used for the new DEV_AB and DEV_B7 entries) are CAB-wrapped self-
extracting exes — innoextract rejects them with "Not a supported Inno
Setup installer!" and the postinst surfaces a noisy Python traceback.

Try innoextract first; on CalledProcessError or FileNotFoundError, fall
back to cabextract. The standalone tool-availability check accepts
either extractor so installations on either family work out of the box.

Note: dropped the `-F <fwname>` filter from cabextract — its pattern
matches the full path inside the cab (e.g. src/driver/INF/x64/6_07f_...
xpfwext) not just the basename, so -F would silently skip the target.
Extract everything; the existing `find` afterward locates the file
regardless of the subdirectory it landed in.
debian/python3-validity.postinst: run pam-auth-update --package --enable
fprintd so sudo / screen-unlock / GNOME Settings fingerprint flows work
immediately after install, without the user having to know about
pam-auth-update.

debian/control: recommend libpam-fprintd (the PAM module our postinst
enables) and cabextract (the fallback extractor used by the new
validity-sensors-firmware path for HP softpaqs).

Bumped changelog through 0.16~hp1/hp2/hp3, with hp3 documenting the
same-finger re-enroll fix shipped this release.
pam_fprintd re-prints "Place your finger on the reader" for every
verify-retry-scan signal it receives. On the 0xd51 chip the capture
loop is chatty — a single 10-second verify window can fire the signal
20+ times, flooding the terminal during sudo authentication.

Suppress all but the first verify-retry-scan per VerifyStart so the
user sees one initial prompt and one early "place again" hint, then
silence until match or timeout. Enrollment behavior is unchanged
because per-stage retry hints are useful there (each stage is a
discrete user action where lift-and-retry feedback matters).
@DataConnection

Copy link
Copy Markdown

Thanks a lot for your effort and the additional commits - now it installs flawlessly (despite showing one error when running validity-sensors-firmware:

# validity-sensors-firmware 
Downloading https://ftp.hp.com/pub/softpaq/sp135501-136000/sp135736.exe to extract 6_07f_hp_cmit_mis_qm.xpfwext
Done with 1 error.
Found firmware at /tmp/tmp8n2xqp6t/src/driver/INF/x64/6_07f_hp_cmit_mis_qm.xpfwext

# ls -la /var/run/python-validity/
insgesamt 216
drwxr-xr-x  2 root root     80 21. Mai 17:43 .
drwxr-xr-x 44 root root    960 21. Mai 17:42 ..
-rw-r--r--  1 root root 216973 21. Mai 17:44 6_07f_hp_cmit_mis_qm.xpfwext
-rw-r--r--  1 root root     72 21. Mai 17:42 backoff

But starting python3-validity.service fails:


Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:>cmd> 3e
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:<cmd< 0000ef004000001001000001010005000104070000100000001000000201020000200000005005000606030000700500008000000302170000f0050000f004000403050000e00a0000200500
Mai 21 17:42:23 monstar python3[38905]: INFO:root:Flash has 5 partitions.
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:>cmd> 01
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:<cmd< 0000f0b05e54a40000000607013000010000b00d48c86dd80023000000000100000003d10007
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:>cmd> 19
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:<cmd< 000002002100100100000000000000000000000075a60c5e0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:>cmd> 4302
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:<cmd< 0000010002000800a558265e0100344602000700d03c00000100840801000700800600000200842803001200701000000200763601000c00000a00000100864700000100505a00000200237700000100c02f00000>
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:>cmd> 06020000014a231406e5542fc6dc3b1aedebe68f55596ad3ca13f6e019994c6f71672fff756fbde0511d09d45978b12ba415b3694a0e76348c8cfe9dbb9abf86813fc0c67c1005519a6f87360c2fb3e12bd0a9e01>
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:<cmd< 0000
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:>cmd> 40010100000000000000100000
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:<cmd< 0000001000000000000001006e340b9cffb37a989ca544e6bb780a2c78901d3fb33738768511a30617afa01d000400a10030b14a20d3c19fcfc5a7f3bedb1ff6fbb9c82b44155f7dc3d6de0300a30023a6026b385>
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:block id 0000 (1 bytes)
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:block id 0004 (161 bytes)
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:Private key:
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:x=0xfc54faebebce6dd7e6c0a7fc62243cf64c4db896369a959c1e28c6b2d7b96083
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:y=0x10244b044f3d053d6f269b88a0975ec9110d993ba511e4a14864ec16741dfd08
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:d=0x448339900fb96ff97c5af985ee063d36b158e20d75ee36e21177f66be15def06
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:block id 0003 (184 bytes)
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:TLS cert blob: b'17000000200000008360b9d7b2c6281e9c959a3696b84d4cf63c2462fca7c0e6d76dceebebfa54fc00000000000000000000000000000000000000000000000000000000000000000000000008fd1d>
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:block id 0005 (420 bytes)
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:unhandled block id 0005 (420 bytes): b'170000000001000001000000fcffffffffffffffffffffff00000000000000000000000001000000ffffffff000000000000000000000000000000000000000000000000>
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:block id 0001 (256 bytes)
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:block id 0002 (256 bytes)
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:block id 0006 (400 bytes)
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:ECDH params:
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:x=0x79a81bae246821dcef190879aa21440302da3c6b50187f4dfe11f71fc6c1d299
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:y=0xcd52fde145924a11f2bb63c112ab14749956fee81302a3d7fe5f4053e20933a7
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:>cmd> 440000001603030045010000410303e6094fe662a9457ce3865895fc1a5895bf1403507e49aac38c28758a5a555bcd07000000000000000006c005003d008d00000a000400020017000b00020100
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:<cmd< 160303003d0200002d0303606956f090a77aaa7990e0359a10b506808cfc4623391da7840c1a5cc6f8d02b07544c5390a77aaac005000d000004014000000e000000
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:>tls> 16: 1400000c50f089f919149d8f0b29b4b5
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:>cmd> 4400000016030301540b0000c00000b80000b8ac1617000000200000008360b9d7b2c6281e9c959a3696b84d4cf63c2462fca7c0e6d76dceebebfa54fc00000000000000000000000000000000000000000000000>
Mai 21 17:42:23 monstar systemd[1]: Reloaded D-Bus System Message Bus.
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:<cmd< 1403030001011603030050c01085ff0098a726b6df8b39fef38e9a8f1599f64b3d02d74a4b1e53b38de5b14e65202924a02c6cf6826ff982c172d9f50d18474efecf5c08727f636ffb1f7454535853dd68ea8eb70>
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:<tls< 16: 1400000ceee4a374e4cb18f940eba896
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:>tls> 17: 4302
Mai 21 17:42:23 monstar python3[38905]: DEBUG:root:>cmd> 170303004006c3b771504bdf7f0d028aaea633f5e569271df2b0a4e19d75d289d3ab23dfa312bad972a8423857a624ae250fe1015bfe988d7f4e012a60a17202a4fa01f829
Mai 21 17:42:24 monstar python3[38905]: DEBUG:root:<cmd< 17030300a09a886bc438ddf20ff24cd324f7bcb19d5d0b221f71cde3e0d927fa9239eb577f0b7dc103ce4a237aa1b103750b4ccca3aacc163e60bf4291f11674e09cb227b6403293227cf2616190eccaa22e11d42>
Mai 21 17:42:24 monstar python3[38905]: DEBUG:root:<tls< 17: 0000010002000800a558265e0100344602000700d03c00000100840801000700800600000200842803001200701000000200763601000c00000a00000100864700000100505a00000200237700000100c02f0>
Mai 21 17:42:24 monstar python3[38905]: INFO:root:Detected firmware version 1.2 (Tue Jan 21 02:49:25 2020))
Mai 21 17:42:24 monstar python3[38905]: DEBUG:root:>tls> 17: 75
Mai 21 17:42:24 monstar python3[38905]: DEBUG:root:>cmd> 170303004063b20803e1bbaf4361bcdbe42ccdf809b92dabc5e13f45e54c995a4d225723849075d94875d6569ce22b4fb8b78e58f6101995867f8d1f92835b33cca21724dc
Mai 21 17:42:24 monstar python3[38905]: DEBUG:root:<cmd< 170303004031342ecab785767e736b3000fbc56e51f76520470bbd99abbe2109d63ebfcb239dce6a6f8a050c5fe6fed46c703c701ec7e462d42dc034cfa81644b4a6e6604c
Mai 21 17:42:24 monstar python3[38905]: DEBUG:root:<tls< 17: 00000000000085009001
Mai 21 17:42:24 monstar python3[38905]: INFO:root:Opening sensor: 57K0 FM-3439-002
Mai 21 17:42:24 monstar dbus-service[38905]: Traceback (most recent call last):
Mai 21 17:42:24 monstar dbus-service[38905]:   File "/usr/lib/python-validity/dbus-service", line 316, in <module>
Mai 21 17:42:24 monstar dbus-service[38905]:     main()
Mai 21 17:42:24 monstar dbus-service[38905]:     ~~~~^^
Mai 21 17:42:24 monstar dbus-service[38905]:   File "/usr/lib/python-validity/dbus-service", line 273, in main
Mai 21 17:42:24 monstar dbus-service[38905]:     init.open()
Mai 21 17:42:24 monstar dbus-service[38905]:     ~~~~~~~~~^^
Mai 21 17:42:24 monstar dbus-service[38905]:   File "/usr/lib/python3.14/site-packages/validitysensor/init.py", line 50, in open
Mai 21 17:42:24 monstar dbus-service[38905]:     open_common()
Mai 21 17:42:24 monstar dbus-service[38905]:     ~~~~~~~~~~~^^
Mai 21 17:42:24 monstar dbus-service[38905]:   File "/usr/lib/python3.14/site-packages/validitysensor/init.py", line 36, in open_common
Mai 21 17:42:24 monstar dbus-service[38905]:     sensor.open()
Mai 21 17:42:24 monstar dbus-service[38905]:     ~~~~~~~~~~~^^
Mai 21 17:42:24 monstar dbus-service[38905]:   File "/usr/lib/python3.14/site-packages/validitysensor/sensor.py", line 252, in open
Mai 21 17:42:24 monstar dbus-service[38905]:     raise Exception('Device %s is not supported (sensor type 0x%x)' %
Mai 21 17:42:24 monstar dbus-service[38905]:                     (self.device_info.name, self.device_info.type))
Mai 21 17:42:24 monstar dbus-service[38905]: Exception: Device 57K0 FM-3439-002    is not supported (sensor type 0x969)
Mai 21 17:42:24 monstar systemd[1]: python3-validity.service: Main process exited, code=exited, status=1/FAILURE
Mai 21 17:42:24 monstar systemd[1]: python3-validity.service: Failed with result 'exit-code'.
Mai 21 17:42:24 monstar systemd[1]: python3-validity.service: Scheduled restart job, restart counter is at 4.
Mai 21 17:42:24 monstar systemd[1]: python3-validity.service: Start request repeated too quickly.
Mai 21 17:42:24 monstar systemd[1]: python3-validity.service: Failed with result 'start-limit-hit'.
Mai 21 17:42:24 monstar systemd[1]: Failed to start python-validity driver dbus service.

USB devices:


# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0408:5373 Quanta Computer, Inc. HP HD Camera
Bus 001 Device 003: ID 06cb:00b7 Synaptics, Inc. Fingerprint reader [HP G6]
Bus 001 Device 004: ID 8087:0029 Intel Corp. AX200 Bluetooth
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Any ideas? I'm stuck.

@SimpleX-T

Copy link
Copy Markdown
Author

Hi @DataConnection, I have been working on this fix, and I have come up with an easier way to implement it. You can now pull it from the apt store:

sudo add-apt-repository ppa:devtochukwu/fingerprint
sudo apt install python3-validity

Let me know if this works

SimpleX-T added 2 commits May 21, 2026 19:30
debian/source/options: tar-ignore .pybuild, build, *.egg-info,
__pycache__, *.pyc.

3.0 (native) source packages bundle the working tree verbatim, so
any leftover pybuild cache from prior local debuild runs gets shipped
to Launchpad. pybuild's cached state embeds the developer's absolute
paths (e.g. /home/<dev>/.../python-validity/.pybuild/...), which the
build chroot can't write to. The first per-series build succeeded
because pybuild created the cache fresh; subsequent series builds
inherited the dirty cache and failed with Permission denied trying
to write into the baked-in path.

This is a packaging-only change; no source code differs.
sensor.py: log resolved capture geometry once at chip open. Useful
when investigating whether the 0x199 spoof produces appropriate
dimensions for whatever chip the daemon is talking to. The log line
includes real_type vs spoofed_type, lines_2d from the capture
program, computed lines_per_frame, bytes_per_line, line_width, and
lines_per_calibration_data — everything needed to recognize a
profile mismatch without re-instrumenting.

dbus-service: in VerifyStart, log every internal chip retry-scan to
the journal independent of the D-Bus signal throttle. Lets users
and support tickets quantify capture quality without manual
instrumentation — `journalctl -u python3-validity.service | grep
'Chip capture retry-scan'` gives the raw count immediately.

Both changes are INFO-level log lines, no functional impact. About
1 log per chip open + 0-3 lines per verify in normal use.
@mpsijm

mpsijm commented May 24, 2026

Copy link
Copy Markdown

Hi @SimpleX-T, thank you so much for working on this! I never thought I'd still be able to use the fingerprint scanner on my 6½-year-old HP ZBook Studio G5 😄 It does not work for me yet, but hopefully we can help each other debug the issue!

According to lsusb, my laptop has scanner ID 138a:00ab Validity Sensors, Inc.

I installed your branch by patching the PKGBUILD from the AUR as follows:
diff --git a/PKGBUILD b/PKGBUILD
index ad31986..d1378b1 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -2,7 +2,7 @@
 # Contributor: j.r <j.r@jugendhacker.de>
 # Contributor: Matthew Murray <matt@mattmurr.xyz>
 pkgname=python-validity
-pkgver=0.15
+pkgver=0.15+0xd51
 pkgrel=1
 pkgdesc="Validity fingerprint sensor driver"
 arch=(any)
@@ -12,22 +12,22 @@ depends=(python python-yaml python-pyusb python-cryptography python-dbus python-
 makedepends=(python-setuptools glib2-devel)
 conflicts=($pkgname)
 provides=($pkgname)
-url="https://github.com/uunicorn/${pkgname}"
+url="https://github.com/SimpleX-T/${pkgname}"
 source=(
-  "$pkgname-$pkgver.tar.gz::${url}/archive/${pkgver}.tar.gz"
+  "$pkgname-$pkgver.tar.gz::${url}/archive/refs/heads/feat/sensor-type-0xd51.tar.gz"
   python3-validity-suspend-hotfix.service 
 )
-md5sums=('7134839860dea1caafa5ae5024536385'
+md5sums=('SKIP'
          'cf8c944df027bbb349c56710c9755cbe')
 install=$pkgname.install
 
 build() {
-  cd $srcdir/$pkgname-$pkgver
+  cd $srcdir/$pkgname-feat-sensor-type-0xd51
   python setup.py build
 }
 
 package() {
-  cd $srcdir/$pkgname-$pkgver
+  cd $srcdir/$pkgname-feat-sensor-type-0xd51
   python setup.py install --prefix=/usr --root $pkgdir || return 1
 
   sed -i 's/^Restart=.*/Restart=on-failure/' debian/python3-validity.service

Then, I ran makepkg and pacman -U python-validity-0.15+0xd51-1-any.pkg.tar.zst. Just to be sure, I verified that the contents of /usr/bin/validity-sensor-firmware, /usr/lib/python3.14/site-packages/validitysensor, etc. are indeed the same as on your branch.

However, both fprintd-enroll and sudo fprintd-enroll -f right-index-finger $USER fail with exit code 1, printing only list_devices failed:. I have also followed the steps at https://github.com/uunicorn/python-validity#error-situations, but that did not help either.

Logs from these "Error situations" commands:

Logs from sudo journalctl -u python3-validity -b (the service kept rebooting itself every 15 seconds, so simply running sudo systemctl status python3-validity wasn't helpful):

May 24 13:18:22 maarten-zbook-g5 systemd[1]: python3-validity.service: Scheduled restart job, restart counter is at 13.
May 24 13:18:22 maarten-zbook-g5 systemd[1]: Started python-validity driver dbus service.
May 24 13:18:22 maarten-zbook-g5 python3[164883]: DEBUG:root:>cmd> 3e
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]: Traceback (most recent call last):
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:   File "/usr/lib/python-validity/dbus-service", line 324, in <module>
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:     main()
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:     ~~~~^^
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:   File "/usr/lib/python-validity/dbus-service", line 281, in main
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:     init.open()
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:     ~~~~~~~~~^^
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:   File "/usr/lib/python3.14/site-packages/validitysensor/init.py", line 50, in open
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:     open_common()
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:     ~~~~~~~~~~~^^
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:   File "/usr/lib/python3.14/site-packages/validitysensor/init.py", line 31, in open_common
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:     init_flash()
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:     ~~~~~~~~~~^^
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:   File "/usr/lib/python3.14/site-packages/validitysensor/init_flash.py", line 122, in init_flash
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:     info = get_flash_info()
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:   File "/usr/lib/python3.14/site-packages/validitysensor/flash.py", line 40, in get_flash_info
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:     rsp = tls.cmd(unhex('3e'))
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:   File "/usr/lib/python3.14/site-packages/validitysensor/tls.py", line 124, in cmd
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:     rsp = self.usb.cmd(cmd)
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:   File "/usr/lib/python3.14/site-packages/validitysensor/usb.py", line 106, in cmd
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:     self.dev.write(1, out)
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:     ~~~~~~~~~~~~~~^^^^^^^^
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:   File "/usr/lib/python3.14/site-packages/usb/core.py", line 1003, in write
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:     return fn(
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:             self._ctx.handle,
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:     ...<3 lines>...
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:             self.__get_timeout(timeout)
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:         )
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:   File "/usr/lib/python3.14/site-packages/usb/backend/libusb1.py", line 841, in bulk_write
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:     return self.__write(self.lib.libusb_bulk_transfer,
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:            ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:                         dev_handle,
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:                         ^^^^^^^^^^^
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:     ...<2 lines>...
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:                         data,
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:                         ^^^^^
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:                         timeout)
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:                         ^^^^^^^^
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:   File "/usr/lib/python3.14/site-packages/usb/backend/libusb1.py", line 942, in __write
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:     _check(retval)
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:     ~~~~~~^^^^^^^^
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:   File "/usr/lib/python3.14/site-packages/usb/backend/libusb1.py", line 602, in _check
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]:     raise USBTimeoutError(_strerror(ret), ret, _libusb_errno[ret])
May 24 13:18:37 maarten-zbook-g5 dbus-service[164883]: usb.core.USBTimeoutError: [Errno 110] Operation timed out
May 24 13:18:37 maarten-zbook-g5 systemd[1]: python3-validity.service: Main process exited, code=exited, status=1/FAILURE
May 24 13:18:37 maarten-zbook-g5 systemd[1]: python3-validity.service: Failed with result 'exit-code'.

After stopping the service, I tried:

$ sudo validity-sensors-firmware
Downloading https://ftp.hp.com/pub/softpaq/sp135501-136000/sp135736.exe to extract 6_07f_hp_cmit_mis_qm.xpfwext
Done with 1 error.
Found firmware at /tmp/tmpghvxw95v/src/driver/INF/x64/6_07f_hp_cmit_mis_qm.xpfwext
$ sudo python3 /usr/share/python-validity/playground/factory-reset.py
Traceback (most recent call last):
  File "/usr/share/python-validity/playground/factory-reset.py", line 6, in <module>
    factory_reset()
    ~~~~~~~~~~~~~^^
  File "/usr/lib/python3.14/site-packages/validitysensor/sensor.py", line 87, in factory_reset
    assert_status(usb.cmd(reset_blob))
    ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.14/site-packages/validitysensor/util.py", line 12, in assert_status
    raise Exception('Failed: %04x' % s)
Exception: Failed: 0401

If there's anything else I can do to debug or gather more information, let me know 🙂

Multiple users reported the 0xd51-family chips (138a:00ab, 06cb:00b7)
getting stuck after cold boot, unclean exit, or suspend/resume — the
chip accepts the bulk-OUT but never responds on bulk-IN, so the first
cleartext cmd (cmd 3e get_flash_info) times out and the daemon
restart-loops every 15 seconds. The workaround users were running
manually is a USB-level reset:

    sudo systemctl stop python3-validity open-fprintd
    sudo udevadm trigger --attr-match=idVendor=138a --attr-match=idProduct=00ab
    sudo systemctl start python3-validity open-fprintd

The reset call here is the in-driver equivalent. The chip's USB
address can shift after reset, so we re-find by vid/pid.

Reported by Killersparrow1 (issue uunicorn#238, Fedora 44, sensor vanishes
on reboot) and a separate Arch / ZBook G5 user (USBTimeoutError on
cmd 3e). The patch matches what the project memory has flagged for
the past two sessions as "kept local and not in PR" — turns out it
was the actually-load-bearing piece.

Locally confirmed: clean daemon restart, sudo matches in 1 retry,
no traceback, no "USB reset failed" warning.
@SimpleX-T

Copy link
Copy Markdown
Author

Hi @mpsijm — sorry for the slow reply. That USBTimeoutError on the very first cmd 3e is the chip stuck in a TLS-pending state from a previous boot or unclean exit — the bulk-OUT goes through but the chip never replies on bulk-IN, so get_flash_info() times out and the daemon restart-loops every 15s.

Just pushed cd0def0 to the branch, which fixes it: a defensive USB reset at the start of Usb.open_dev(). Same effect as a manual udevadm trigger --attr-match=idVendor=138a --attr-match=idProduct=00ab, but built into the driver so it runs every time the daemon opens the chip.

To update on Arch via your patched AUR PKGBUILD: since you have md5sums=('SKIP' ...) and the source pointing at refs/heads/feat/sensor-type-0xd51.tar.gz, just rerun makepkg -f and pacman -U python-validity-0.15+0xd51-1-any.pkg.tar.zst. It'll pull the latest branch tip. Then sudo systemctl restart python3-validity.service.

Re your factory-reset.py returning Failed: 0401 — that's the chip refusing the reset because it's already in a clean factory state. You don't actually need to factory-reset on a fresh install; that script is only for recovering from a corrupted enrollment session.

Let me know how the rebuild goes!

@mpsijm

mpsijm commented May 25, 2026

Copy link
Copy Markdown

No need to apologize for inherently asynchronous communication! You already reply faster than most people do on open-source repositories 😄

Long ago, I used the fingerprint scanner on Windows (dual-boot). Haven't switched back to Windows in years, but no clue if the unclean exit could be caused by this. At least good to hear that the error I receive on factory reset is not actually an error 😂

Note that skipping the md5sum check does not automatically trigger a re-download, but deleting the previous source .tar.gz works 🙂 After reinstalling, Pacman automatically restarts the service, and I now receive different errors (after which the service restarts itself five times before giving up). So, your defensive USB reset appears to have effect, thanks for that fix! 🎉

Excerpt from sudo journalctl -u python3-validity -b again:
May 25 10:20:44 maarten-zbook-g5 systemd[1]: python3-validity.service: Scheduled restart job, restart counter is at 4.
May 25 10:20:44 maarten-zbook-g5 systemd[1]: Started python-validity driver dbus service.
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:>cmd> 3e
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:<cmd< 0000ef004000001001000001010005000104070000100000001000000201020000200000005005000606030000700500008000000302170000f0050000f004000403050000e00a0000200500
May 25 10:20:45 maarten-zbook-g5 python3[239261]: INFO:root:Flash has 5 partitions.
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:>cmd> 01
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:<cmd< 0000f0b05e54a4000000060701300001000045a64a706abf0023000000000100000003d10007
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:>cmd> 19
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:<cmd< 0000000301020001000000000000000000000000d8fc6e5c0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:>cmd> 4302
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:<cmd< 0000010002000800a558265e0100344602000700d03c00000100840801000700800600000200842803001200701000000200763601000c00000a00000100864700000100505a00000200237700000100c02f00000200003700000100b0080200010025560000010060040000
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:>cmd> 06020000014a231406e5542fc6dc3b1aedebe68f55596ad3ca13f6e019994c6f71672fff756fbde0511d09d45978b12ba415b3694a0e76348c8cfe9dbb9abf86813fc0c67c1005519a6f87360c2fb3e12bd0a9e012b06d9f5c9b44ccc6645b0fbd47afe45c8c874fcb88fbfd18fb7a9b3241351f256acce689f9586a52b01f8fdcb66cdf3b340b1f9f386d58ca24fdfcdfbcebefb5f3a3c2a08357721040235a20ce1ee2f4f7856e0d9c27b92cd9b975c86f>
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:<cmd< 0000
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:>cmd> 40010100000000000000100000
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:<cmd< 0000001000000000000001006e340b9cffb37a989ca544e6bb780a2c78901d3fb33738768511a30617afa01d000400a10037fd204a4991b240b272611c2f0f2aab72da709dd5e57d4dcab4d267bd72fede025e4faa932fac83966840cd24f623e0518cf16eaa9feaa16c929daca3a088fb9a497337434b23751f4a270df60de62c36e22a7bf7a9fd5dbc4da179858a6c1176c38c64705ec45bd31f070798fdafe6c72d119c018c65b7f575e4f63b67bc934d>
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:block id 0000 (1 bytes)
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:block id 0004 (161 bytes)
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:Private key:
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:x=0x32c050a000d9989775f0afe7657ff2f764c500d34042db660f5272f81dcbf1d6
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:y=0x69e6577e7035e0d4d7d70fbe723cb71b8dd3151710e298595fc27ad74bee4751
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:d=0x80c11ea182beb8b539eb9a15eee134fc64e6d915b34fa6d3748e0c50085f820
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:block id 0003 (184 bytes)
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:TLS cert blob: b'1700000020000000d6f1cb1df872520f66db4240d300c564f7f27f65e7aff0759798d900a050c0320000000000000000000000000000000000000000000000000000000000000000000000005147ee4bd77ac25f5998e2101715d38d1bb73c72be0fd7d7d4e035707e57e6690000000000000000000000000000000000000000000000000000000000000000000000000000000000000000f37003cf483a409947b6b5466a106efb2466764d6>
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:block id 0005 (420 bytes)
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:unhandled block id 0005 (420 bytes): b'170000000001000001000000fcffffffffffffffffffffff00000000000000000000000001000000ffffffff0000000000000000000000000000000000000000000000000000000000000000000000004b60d2273e3cce3bf6b053ccb0061d65bc86987655bdebb3e7933aaad835c65a00000000000000000000000000000000000000000000000000000000000000000000000096c298d84539a1f4a033eb2d817>
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:block id 0001 (256 bytes)
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:block id 0002 (256 bytes)
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:block id 0006 (400 bytes)
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:ECDH params:
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:x=0xe150956fee2ffdfcf381ce2e271090d195de484da702e167d9161595513dd67
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:y=0x730476c78477e9daf76a557ddce958002ee4c538e1283b8227d84064844c4c3e
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:>cmd> 440000001603030045010000410303841b81c402a302c295f59d3d84f10843b420e5f12883303b6963e0a67ec1de6107000000000000000006c005003d008d00000a000400020017000b00020100
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:<cmd< 160303003d0200002d030300012f7630226d678fed5aeafe5cd952ebee6e25f2648a7a452077aab2d05c4507544c5330226d67c005000d000004014000000e000000
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:>tls> 16: 1400000cfbbd5ffb5b08790422090de3
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:>cmd> 4400000016030301540b0000c00000b80000b8ac161700000020000000d6f1cb1df872520f66db4240d300c564f7f27f65e7aff0759798d900a050c0320000000000000000000000000000000000000000000000000000000000000000000000005147ee4bd77ac25f5998e2101715d38d1bb73c72be0fd7d7d4e035707e57e6690000000000000000000000000000000000000000000000000000000000000000000000000000000000000000f37003cf48>
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:<cmd< 140303000101160303005016094c8318c6d30dbb8bbde65cb3bb206bf878413df90db0acc01cd6195a5694cba813ddfad17d425e3f2abbcda3c939763275fee1dcbc3e1e3e5ce16af4687f395236a9ce2c604784b2a1f81a46d0f3
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:<tls< 16: 1400000cd516a345b5547d185ba7d280
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:>tls> 17: 4302
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:>cmd> 1703030040911b65f37082fc767da00529a066d2d3b2f3b1bead1f86622e868a8f8a24bab2a453ea960acb7eca0107edb6a2ce70dfdc29ad0d2f8267b502d5a698efc0dbf3
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:<cmd< 17030300a0196eb567d8a9ab185fcc2d8e1c4dc348ca583dc7e1b081cfdfd097dbfc72a5aec5b0967e532bfb03f296c974832728967dfa20d0c606b39f5b0d6fa7252ed37589e0b5f947b9b552a6164efe731534c2cf5a11fc152428acca99e5c617aa49d8b7838e9765b0a03bb7ed9d90bd43bd7b6bf3ee7b1a34bc506dbfef138bedca28c7ddf0c98d2deea84ba517e50eba6d7caa834d26df6a2418749fa734649b6ff7
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:<tls< 17: 0000010002000800a558265e0100344602000700d03c00000100840801000700800600000200842803001200701000000200763601000c00000a00000100864700000100505a00000200237700000100c02f00000200003700000100b0080200010025560000010060040000
May 25 10:20:45 maarten-zbook-g5 python3[239261]: INFO:root:Detected firmware version 1.2 (Tue Jan 21 02:49:25 2020))
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:>tls> 17: 75
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:>cmd> 1703030040e1063cff21a4963fea16ef7142a142a7ee9b7d0b166829fea36b40ee0a9ddd899704bf973382f53b284f084f73829764d2c8d22b8ce5340d7e205c079aee13d4
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:<cmd< 1703030040addc1ff2fb6d995b3276cb508ddf0d44b1c490f0a8248f42188aa03960a31921e78a079fbfc42dbdb3693ea2643cdec350aea1319c8ee0d52be0c9446ce1d248
May 25 10:20:45 maarten-zbook-g5 python3[239261]: DEBUG:root:<tls< 17: 00000000000071009001
May 25 10:20:45 maarten-zbook-g5 python3[239261]: INFO:root:Opening sensor: 57K0 FM- 154-123
May 25 10:20:45 maarten-zbook-g5 dbus-service[239261]: Traceback (most recent call last):
May 25 10:20:45 maarten-zbook-g5 dbus-service[239261]:   File "/usr/lib/python-validity/dbus-service", line 324, in <module>
May 25 10:20:45 maarten-zbook-g5 dbus-service[239261]:     main()
May 25 10:20:45 maarten-zbook-g5 dbus-service[239261]:     ~~~~^^
May 25 10:20:45 maarten-zbook-g5 dbus-service[239261]:   File "/usr/lib/python-validity/dbus-service", line 281, in main
May 25 10:20:45 maarten-zbook-g5 dbus-service[239261]:     init.open()
May 25 10:20:45 maarten-zbook-g5 dbus-service[239261]:     ~~~~~~~~~^^
May 25 10:20:45 maarten-zbook-g5 dbus-service[239261]:   File "/usr/lib/python3.14/site-packages/validitysensor/init.py", line 50, in open
May 25 10:20:45 maarten-zbook-g5 dbus-service[239261]:     open_common()
May 25 10:20:45 maarten-zbook-g5 dbus-service[239261]:     ~~~~~~~~~~~^^
May 25 10:20:45 maarten-zbook-g5 dbus-service[239261]:   File "/usr/lib/python3.14/site-packages/validitysensor/init.py", line 36, in open_common
May 25 10:20:45 maarten-zbook-g5 dbus-service[239261]:     sensor.open()
May 25 10:20:45 maarten-zbook-g5 dbus-service[239261]:     ~~~~~~~~~~~^^
May 25 10:20:45 maarten-zbook-g5 dbus-service[239261]:   File "/usr/lib/python3.14/site-packages/validitysensor/sensor.py", line 252, in open
May 25 10:20:45 maarten-zbook-g5 dbus-service[239261]:     raise Exception('Device %s is not supported (sensor type 0x%x)' %
May 25 10:20:45 maarten-zbook-g5 dbus-service[239261]:                     (self.device_info.name, self.device_info.type))
May 25 10:20:45 maarten-zbook-g5 dbus-service[239261]: Exception: Device 57K0 FM- 154-123    is not supported (sensor type 0x969)
May 25 10:20:45 maarten-zbook-g5 systemd[1]: python3-validity.service: Main process exited, code=exited, status=1/FAILURE
May 25 10:20:45 maarten-zbook-g5 systemd[1]: python3-validity.service: Failed with result 'exit-code'.
May 25 10:20:46 maarten-zbook-g5 systemd[1]: python3-validity.service: Scheduled restart job, restart counter is at 5.
May 25 10:20:46 maarten-zbook-g5 systemd[1]: python3-validity.service: Start request repeated too quickly.
May 25 10:20:46 maarten-zbook-g5 systemd[1]: python3-validity.service: Failed with result 'start-limit-hit'.
May 25 10:20:46 maarten-zbook-g5 systemd[1]: Failed to start python-validity driver dbus service.

There's a lot of debug output that I don't understand, but the most important line appears to be near the end:

Exception: Device 57K0 FM- 154-123 is not supported (sensor type 0x969)

@DataConnection

Copy link
Copy Markdown

I was getting a similar error - it seems that the sensor is not 0xd51 but 0x969 for the HP ZBook G6. I changed (without actually knowing what I'm doing) the lines 238 in sensors.py to

        if self.device_info.type == **0x969:**
            logging.info('Sensor type 0x969 — aliasing to 0x199 profile')
            self.device_info.type = 0x199
    

Afterwards I could start the python3-validity service and enroll my fingerprint. But fprintd-verify won't work.
Maybe the solution lies in the hardware.py - my device 06cb:00b7 is referred as 57K0 FM-3439-002:

DeviceInfo(0x0190, 0x0969, 0x85, 0xff, '57K0 FM-3439-002   '),

There is also a line for mpsijm's device, referring to the same sensor type:
DeviceInfo(0x0190, 0x0969, 0x71, 0xff, '57K0 FM- 154-123 '),

@mpsijm : thanks for the adapted makepkg file - I'm also using Arch.

@mpsijm

mpsijm commented May 27, 2026

Copy link
Copy Markdown

Nice progress! 😄 After making the same change in sensor.py:238, I can confirm the same symptoms:

$ fprintd-enroll 
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-stage-passed
Enroll result: enroll-retry-scan
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-retry-scan
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-completed

For the output above, I put my finger on the scanner between each line.

$ fprintd-verify 
Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
 - #0: right-index-finger

No matter how often I put my finger on the scanner, nothing happens, until I hit Ctrl+C to terminate the command.

Also, here's the log for sudo journalctl -u python3-validity -b when I run fprintd-verify (the only logs are from starting the command and interrupting it, nothing in between):

(lines truncated due to lengthy hex strings and no clue if I'd be leaking cryptographic secrets)

May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:In ListEnrolledFingers maarten
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:>tls> 17: 4b00000b0053746757696e64736f7200
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:>cmd> 1703030050965b4c906b71a0be1a3603[...total 170 hex digits...]
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:<cmd< 1703030050c2b3a8f7f1781a1d3658a1[...total 170 hex digits...]
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:<tls< 17: 0000030002000b00000005004c000d004c0053746757696e64736f7200
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:>tls> 17: 4a000003004c00030000001c00000001[...total 166 hex digits...]
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:>cmd> 17030300903b6c04228ef9ee7d61d893[...total 298 hex digits...]
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:<cmd< 170303009068733d24e10137c0719cc0[...total 298 hex digits...]
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:<tls< 17: 00000d00010000004c000e0002000300[...total 188 hex digits...]
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:['right-index-finger']
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:In VerifyStart for maarten, right-index-finger
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:>tls> 17: 4b00000b0053746757696e64736f7200
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:>cmd> 1703030050d0dc510e6f7b8fadb27988[...total 170 hex digits...]
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:<cmd< 1703030050d3891ae29b0db5b407b1b8[...total 170 hex digits...]
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:<tls< 17: 0000030002000b00000005004c000d004c0053746757696e64736f7200
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:>tls> 17: 4a000003004c00030000001c00000001[...total 166 hex digits...]
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:>cmd> 1703030090658f595efe4ec53c2279c9[...total 298 hex digits...]
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:<cmd< 1703030090966f209226e8a4dad32d19[...total 298 hex digits...]
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:<tls< 17: 00000d00010000004c000e0002000300[...total 188 hex digits...]
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:VerifyFingerSelected
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:>tls> 17: 3920bf0200ffff000001990020000000[...total 250 hex digits...]
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:>cmd> 17030300b02336dbe9291e541063585b[...total 362 hex digits...]
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:<cmd< 170303004059fe0bf0cb7478403e3b9d[...total 138 hex digits...]
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:<tls< 17: 0000
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:>tls> 17: 02780000002300000020000800002000[...total 27482 hex digits...]
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:>cmd> 17030335e027c198d2df9faf50dd944f[...total 27594 hex digits...]
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:<cmd< 17030307e06c82354482100856e36ec8[...total 4042 hex digits...]
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:<tls< 17: 0000880200305e000000eaf7f9fcfefe[...total 3932 hex digits...]
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:<int< 0000000000
May 27 22:26:14 maarten-zbook-g5 python3[27645]: DEBUG:root:<int< 0320070000
May 27 22:27:40 maarten-zbook-g5 python3[27645]: DEBUG:root:>tls> 17: 04
May 27 22:27:40 maarten-zbook-g5 python3[27645]: DEBUG:root:>cmd> 1703030040ef8bac142fd7df8cbf2411[...total 138 hex digits...]
May 27 22:27:40 maarten-zbook-g5 python3[27645]: DEBUG:root:<cmd< 1703030040ee977ce4d6d984e3588608[...total 138 hex digits...]
May 27 22:27:40 maarten-zbook-g5 python3[27645]: DEBUG:root:<tls< 17: 1204
May 27 22:27:40 maarten-zbook-g5 python3[27645]: DEBUG:root:>tls> 17: 39f4010000f401000001ff0020000000[...total 250 hex digits...]
May 27 22:27:40 maarten-zbook-g5 python3[27645]: DEBUG:root:>cmd> 17030300b08a3239c81a97fb1d046061[...total 362 hex digits...]
May 27 22:27:40 maarten-zbook-g5 python3[27645]: DEBUG:root:<cmd< 17030300405da64d716bfc75fc92d084[...total 138 hex digits...]
May 27 22:27:40 maarten-zbook-g5 python3[27645]: DEBUG:root:<tls< 17: 0000
May 27 22:27:40 maarten-zbook-g5 ERROR:root[27645]: Traceback (most recent call last):
                                                      File "/usr/lib/python3.14/site-packages/validitysensor/usb.py", line 161, in wait_int
                                                        resp = self.dev.read(131, 1024, timeout=100)
                                                      File "/usr/lib/python3.14/site-packages/usb/core.py", line 1043, in read
                                                        ret = fn(
                                                                self._ctx.handle,
                                                        ...<2 lines>...
                                                                buff,
                                                                self.__get_timeout(timeout))
                                                      File "/usr/lib/python3.14/site-packages/usb/backend/libusb1.py", line 868, in intr_read
                                                        return self.__read(self.lib.libusb_interrupt_transfer,
                                                               ~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                                                                           dev_handle,
                                                                           ^^^^^^^^^^^
                                                        ...<2 lines>...
                                                                           buff,
                                                                           ^^^^^
                                                                           timeout)
                                                                           ^^^^^^^^
                                                      File "/usr/lib/python3.14/site-packages/usb/backend/libusb1.py", line 958, in __read
                                                        _check(retval)
                                                        ~~~~~~^^^^^^^^
                                                      File "/usr/lib/python3.14/site-packages/usb/backend/libusb1.py", line 602, in _check
                                                        raise USBTimeoutError(_strerror(ret), ret, _libusb_errno[ret])
                                                    usb.core.USBTimeoutError: [Errno 110] Operation timed out
                                                    
                                                    During handling of the above exception, another exception occurred:
                                                    
                                                    Traceback (most recent call last):
                                                      File "/usr/lib/python-validity/dbus-service", line 142, in run
                                                        usrid, subtype, hsh = sensor.identify(update_cb)
                                                                              ~~~~~~~~~~~~~~~^^^^^^^^^^^
                                                      File "/usr/lib/python3.14/site-packages/validitysensor/sensor.py", line 953, in identify
                                                        raise e
                                                      File "/usr/lib/python3.14/site-packages/validitysensor/sensor.py", line 947, in identify
                                                        self.capture(CaptureMode.IDENTIFY)
                                                        ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
                                                      File "/usr/lib/python3.14/site-packages/validitysensor/sensor.py", line 739, in capture
                                                        b = usb.wait_int()
                                                      File "/usr/lib/python3.14/site-packages/validitysensor/usb.py", line 168, in wait_int
                                                        raise CancelledException()
                                                    validitysensor.usb.CancelledException
May 27 22:27:40 maarten-zbook-g5 python3[27645]: DEBUG:root:VerifyStatus

@bcoutts

bcoutts commented May 30, 2026

Copy link
Copy Markdown

This is looking great! I'm running into issues with the python3-validity service after going through this on an HP ProBook 445R G6.

Omarchy
0 partitions, reset_blob returns 0404, chip is a fresh 0xd51 after UEFI reset.

sudo /usr/lib/python-validity/dbus-service --debug 2>&1 | head -50
Traceback (most recent call last):
  File "/usr/lib/python-validity/dbus-service", line 324, in <module>
    main()
    ~~~~^^
  File "/usr/lib/python-validity/dbus-service", line 281, in main
    init.open()
    ~~~~~~~~~^^
  File "/usr/lib/python3.14/site-packages/validitysensor/init.py", line 50, in open
    open_common()
    ~~~~~~~~~~~^^
  File "/usr/lib/python3.14/site-packages/validitysensor/init.py", line 31, in open_common
    init_flash()
    ~~~~~~~~~~^^
  File "/usr/lib/python3.14/site-packages/validitysensor/init_flash.py", line 130, in init_flash
    assert_status(usb.cmd(reset_blob))
    ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.14/site-packages/validitysensor/util.py", line 12, in assert_status
    raise Exception('Failed: %04x' % s)
Exception: Failed: 0404

@Karloss1234

Karloss1234 commented Jun 3, 2026 •

Copy link
Copy Markdown

hI have HP zBook WorkStation G6 with 06cb:00b7 (0x969 variant).
I can enrol. I can also verify with mixed results. I get about 20% verified finger presses rate, the rest, bad finger presses. Perhaps 0x969 variant is very sensitive. (I have later learned in my next message that this is due to Linux enrol templates competing and losing against Windows Hello templates)

karlc@karl-hpzbook17g6:/python-validity$ fprintd-verify -f right-index-finger
Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
#0: right-index-finger
Verify result: verify-retry-scan (not done)
Verify result: verify-match (done)
karlc@karl-hpzbook17g6:/python-validity$

karlc@karl-hpzbook17g6:/python-validity$ fprintd-verify -f right-index-finger
Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
#0: right-index-finger
Verify result: verify-retry-scan (not done)
Verify result: verify-no-match (done)
karlc@karl-hpzbook17g6:/python-validity$

To get beyond enrolling to verifying, in sensor.py I changed:

    if self.device_info.type == 0xd51:
        logging.info('Sensor type 0xd51 — aliasing to 0x199 profile')
        self.device_info.type = 0x199

into

    if self.device_info.type == 0xd51:
        logging.info('Sensor type 0xd51 — aliasing to 0x199 profile')
        self.device_info.type = 0x199
    elif self.device_info.type == 0x969:
        logging.info('Sensor type 0x969 — aliasing to 0x199 profile')
        self.device_info.type = 0x199

and changed

            if b[0] == 3 and getattr(self, 'real_device_type', None) == 0xd51:    

into

            if b[0] == 3 and getattr(self, 'real_device_type', None) in (0xd51, 0x969):

Lock screen acknowledges my finger, but I haven't been able to get a correct finger scan on lock screen yet.

@Karloss1234 Karloss1234 left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additional support for sensor type 0x969 (06cb:00b7 HP G6 series) 

sensor.py

Summary 
This report documents the seamlessly working end-to-end fingerprint authentication on Kubuntu 26.04 with a Synaptics VFS7552 with PurePrint sensor (06cb:00b7, sensor type 0x969) on an HP ZBook 17 G6.
The sensor now works for fprintd-verify, sudo authentication, KDE lock screen, and resume from suspend.

All code additions are confined to a single file: validitysensor/sensor.py. All of the original PR #256 code is untouched (just a few lines added). If you can’t wait for the project update, just switch your current sensor.py out for this one (Link at top).

I am not a developer, but spent many days with Claude, stumbling across a few critical bugs and glitches that users of these drivers need to be aware of to get the driver working properly. It also appears that if I had read the installation instructions, many of the following points wouldn't be necessary. PR#256 seems to be a very solid and stable effort.........if you follow the python-validity installation instructions.

Point 1 — Introduce Basic 0x969 support 
Sensor type 0x969 behaves identically to 0xd51 with respect to interrupt handling. The chip does not emit the b[0]=2 "finger detected" interrupt — it jumps directly from start ack (b[0]=0) to capture complete (b[0]=3).
The fix was to add 0x969 alongside 0xd51 everywhere the existing PR #256 code already handled 0xd51:

line_update_type1_devices list (Including 0x969 in this list doesn't seem to have any effect)
Sensor type alias (0x969 → 0x199 profile)
saved_b interrupt fix in capture()
real_device_type checks

No new logic was required — 0x969 simply needed to be treated identically to 0xd51 throughout.
Note for other 0x969 users: The USB IDs and sensor names vary across HP models:

06cb:00b7 — 57K0 FM-3439-xxx (HP ZBook G6, HP ProBook G6 etc.)
06cb:00b7 — 57K0 FM- 154-xxx (HP ZBook G5 etc.)

Point 2 — Windows Hello template competition 
If I had followed the 'Windows interoperability' installation instruction for python-validity then the rest of this point is irrelevant, but I leave it here for information anyway.
Important finding for dual-boot users: The fingerprint chip's flash database is shared between Windows and Linux. Windows Hello templates and Linux fprintd templates coexist in the same on-chip database and compete during every verify operation. The chip's on-chip matcher compares every captured image against ALL enrolled templates simultaneously and returns the best match.
Practical consequence: If Windows Hello has a high-quality template enrolled for the same finger as Linux fprintd, Windows Hello will win most comparisons, causing Linux verify to fail. The Linux usrid is only returned when the Linux template scores higher than all competing templates.
Workaround: Enroll different fingers in Windows Hello and Linux fprintd. For example, enroll the right index finger in Linux and the right middle finger in Windows Hello. This eliminates template competition entirely.
Alternative: Erase the on-chip database partition from Linux (erase_flash(4)) and enroll Linux only, accepting the loss of Windows Hello fingerprint authentication.

Point 3 — Blank capture wording could be improved 
I spent many hours with Claude trying to work out what caused verify-retry-scan to be emitted immediately on every verify attempt.
It turned out that it is some code in dbus-service. The code says 'verify-retry-scan'. It was annoying because I hadn’t tried at all. I disabled it with retry_emitted = [True].
Perhaps the PR #256 author would update the wording to say ‘Ready for finger Press’, or perhaps do away with it altogether. My file can be edited with this command, for anyone wanting to dissable/tweak it: 

kate /usr/lib/python-validity/dbus-service

Point 4 — Resume from suspend fix Specific to 0x969 chips. 
After resume from suspend, the 0x969 chip reports sensor type 0x199 directly rather than 0x969. This causes sensor.open() to skip the 0x969 alias and the saved_b interrupt fix, resulting in verify hanging indefinitely after resume.
Root cause: On cold boot the chip reports 0x969. After USB power cycle (suspend/resume), it reports 0x199.
Fix: Added detection in sensor.open() using the chip's device name, which remains consistent across boot and resume:

pythonelif self.device_info.type == 0x199 and ('FM-3439' in self.device_info.name or 'FM- 154' in self.device_info.name):
logging.info('Sensor %s reporting 0x199 on resume — treating as 0x969' % self.device_info.name.strip())
self.real_device_type = 0x969

This covers all known 0x969 model variants (FM-3439-xxx and FM- 154-xxx) while safely excluding genuine 0x199 chips (FM-3367-xxx, FM-3380-xxx, FM-155-xxx).
Note: It is unknown whether 0xd51 chips exhibit the same resume behaviour. Testing by 0xd51 users is needed. Perhaps PR#256 has existing code to fix this issue for 0xd51, and this existing code can be applied to 0x969.

Point 5 - OS configuration to get Finger sensor working in Lock Screen (Kubuntu specific) 
I have subsequently found that the python-validity installation instructions address this. I'm not sure if what follows is 'new' or useful or specific to Kubuntu. I can do some tinkering for Kubuntu if you would like me to.

The following system files required modification on Kubuntu 26.04 to get Lock Screen finger print working. At least one of these file creations/changes worked. I'm not sure if all of them are required. Ubuntu and other distributions may differ.

Created /etc/pam.d/kde-fingerprint:
#%PAM-1.0
auth sufficient pam_fprintd.so max_tries=3 timeout=10
auth required pam_unix.so

Created /etc/pam.d/kde-smartcard:
#%PAM-1.0
auth sufficient pam_fprintd.so max_tries=3 timeout=10
auth required pam_unix.so

Created /etc/pam.d/kde:
#%PAM-1.0
auth sufficient pam_fprintd.so max_tries=3 timeout=10
auth required pam_unix.so

Modified /etc/pam.d/sddm-greeter: Changed pam_permit.so to pam_unix.so as fallback (security fix — previously the lock screen would unlock without authentication after fingerprint timeout).
Modified /etc/pam.d/common-auth: Moved max_tries=3 before inline comment to ensure it is not ignored by PAM parser.

Point 6 — Flash database management and memory full error 
Critical finding for all users and developers. I'm not sure if this is a new problem. Let me know if it is helpful.

The problem
Enrollment consistently failed with enroll-failed after all capture stages completed successfully. Journal logs showed:

Exception: Failed: 04b5

at db.new_finger() → new_record(). The error occurred specifically when the chip attempted to write the finger template to flash — not during capture or matching.

Root cause — insufficient flash space
The chip's database partition has 328KB total (total=335872 bytes). A single Linux finger template requires approximately 23KB (datalen=23176). The partition was full due to accumulated deleted records that had not been compacted.

Diagnosis command:

bashsudo python3 -c "
import sys
sys.path.insert(0, '/usr/lib/python3/dist-packages')
sys.path.insert(0, '/usr/lib/python-validity')
from validitysensor import init
init.open()
from validitysensor.db import db
db.dump_all()
info = db.db_info()
print('total=%d used=%d free=%d records=%d' % (info.total, info.used, info.free, info.records))
"

Typical output showing the problem:
total=335872 used=90112 free=11008 records=29

Only 11008 bytes free with 23176 bytes needed — enrollment impossible.

Why deleting templates doesn't free space
Two related bugs were discovered:
Bug 1 — del_record() missing db_write_enable:
The del_record() function in db.py does not call db_write_enable before the delete command (0x48). On 0x969 chips this returns error 04b6 ("delete not permitted"), meaning the delete command silently fails and flash space is never reclaimed.

Bug 2 — Flash compaction not triggered by deletions:

Even when records are successfully deleted (marked as free), the chip does not automatically compact the flash partition. Deleted records continue to occupy physical flash space until a compaction is triggered. On this chip, compaction was only observed to occur when Windows Hello re-enrolled after a TPM reset — the Windows driver appears to trigger compaction as part of its enrollment process.

Solution — erase database partition

The reliable solution is to erase the database partition directly. This is safe because the partition contains only user templates and database records — it does not affect firmware (partition 0x02), TLS/PurePrint keys (partition 0x06), or TLS session data (partition 0x03).

Flash structure for reference:
Partition 0x01 type=04 offset=0x001000 size=4KB ← config/header
Partition 0x02 type=01 offset=0x002000 size=340KB ← firmware
Partition 0x06 type=06 offset=0x057000 size=32KB ← TLS/PurePrint keys
Partition 0x03 type=02 offset=0x05f000 size=316KB ← TLS session data
Partition 0x04 type=03 offset=0x0ae000 size=328KB ← DATABASE ← erase this

Erase script (stop services first):

bashsudo systemctl stop python3-validity open-fprintd
sleep 2
sudo python3 -c "
import sys
sys.path.insert(0, '/usr/lib/python3/dist-packages')
sys.path.insert(0, '/usr/lib/python-validity')
from validitysensor import init
init.open()
from validitysensor.flash import erase_flash
print('Erasing database partition 0x04...')
erase_flash(4)
print('Done')
"
sudo systemctl start python3-validity open-fprintd
sleep 3
sudo reboot

Important: Reboot after erasing — the chip needs a full USB power cycle to reinitialise cleanly after partition erase. Attempting to enroll without rebooting may result in Unexpected TLS version errors.

Verify clean state after reboot:

bashsudo python3 -c "
import sys
sys.path.insert(0, '/usr/lib/python3/dist-packages')
sys.path.insert(0, '/usr/lib/python-validity')
from validitysensor import init
init.open()
from validitysensor.db import db
db.dump_all()
info = db.db_info()
print('total=%d used=%d free=%d records=%d' % (info.total, info.used, info.free, info.records))
"

Expected output after successful erase:
total=335872 used=768 free=335104 records=1
used=768 represents only the root StgWindsor storage record — the database is essentially empty and ready for fresh enrollment.

Warning for dual-boot users
Erasing partition 0x04 removes ALL finger templates including Windows Hello enrollments. Windows Hello PIN and TPM state are unaffected (stored elsewhere), but fingerprint login will need to be re-enrolled in Windows after the erase.
Recommended enrollment order after erase:

Windows Hello needs to be enrolled first. If you do it after Linux, Windows HEllo enrol will say 'having difficulty identifying you', and you therefore can't enrol.

Boot Windows → enroll Windows Hello fingerprint first
Boot Linux → enroll Linux fprintd fingers
Use different fingers for Windows Hello and Linux to avoid template competition (see Point 2)

Testing
Verified working end-to-end on:

Hardware: HP ZBook 17 G6, sensor 06cb:00b7 - 0x969 alias, device name 57K0 FM-3439-002
OS: Kubuntu 26.04
Kernel: 6.x
fprintd-verify — 100% match rate (single user, no competing templates)
sudo fingerprint authentication
KDE lock screen fingerprint unlock
Resume from suspend fingerprint unlock

@RamcharanRajpurohit

Copy link
Copy Markdown

Validated on Fedora 43 — 06cb:00b7 enroll + verify working ✅

Tested this PR on Fedora 43 (kernel 7.0, Python 3.14) with a Synaptics 06cb:00b7 reader (HP G6 laptop). It works end to end.

Setup: applied this PR's diff onto current master, installed open-fprintd + fprintd-clients from the sneexy/python-validity COPR, then installed the patched validitysensor package + service/udev.

Results:

  • Sensor identifies as 57K0 FM-3439-001, real type 0xd51, aliased to 0x199 as this PR does.
  • Firmware was already on-chip (v1.2) — no softpaq / xpfwext upload needed, matching the PR comment that 0xd51 variants ship pre-provisioned.
  • Calibration succeeds.
  • Enroll succeeded (6 stages) and identify/verify matches the enrolled finger.
  • fprintd-list shows the device and the enrolled right-index-finger.
  • The b[0]=3 interrupt substitution for 0xd51 is what makes capture work — without it the capture loop hangs.

Relevant log:

INFO Detected firmware version 1.2
INFO Sensor type 0xd51 — aliasing to 0x199 profile
INFO Opening sensor: 57K0 FM-3439-001
INFO Capture geometry: real_type=0xd51 spoofed_type=0x199 lines_2d=112 ...
=== ENROLL SUCCESS — finger record dbid 13 ===
=== MATCH! user recid=12  finger subtype=0x2 ... ===

Minor notes for Fedora users: needed python3-pyusb, python3-pyte, python3-crcmod, cabextract from the Fedora repos; the debian/ packaging bits don't apply on Fedora, but the validitysensor/ source changes are all that's needed for the driver itself. Happy to help with a Fedora .spec bump if useful.

Thanks @SimpleX-T — this is the only thing that's made 06cb:00b7 work for me.

@ntoyiakhona06-creator

Copy link
Copy Markdown

Device: HP EliteBook 840 G5, 138a:00ab Validity Sensors fingerprint reader
Setup: EndeavourOS (Arch-based), built from PR #256 (commit cd0def0)
Built and installed successfully — package installs clean, systemd service enabled, udev rules applied. However, python3-validity.service crash-loops on start with:

' ' '
File "/usr/lib/python3.14/site-packages/validitysensor/tls.py", line 512, in handle_priv
raise Exception(
'Signature verification failed. This device was probably paired with another computer.'
)
Exception: Signature verification failed. This device was probably paired with another computer
' ' '

Steps taken so far:
Ran playground/factory-reset.py with the 00ab → blobs_97 mapping from this PR — failed with Exception: Failed: 0404 at assert_status(usb.cmd(reset_blob)) in sensor.py.
Tried substituting blobs_9d instead of blobs_97 for the 0x00ab mapping — same 0404 failure, byte-for-byte identical error.
Uninstalled the Windows fingerprint driver via Device Manager (checked "delete driver software") and let Windows reinstall it fresh, hoping it would re-pair and clear whatever the Linux driver is checking. Rebooted into Linux — identical "Signature verification failed" error persists, unchanged.
Worth noting: the 0404 status differs from 0x44f, which util.py's assert_status seems to treat as the dedicated "signature validation failed" code — so 0404 may indicate a different failure mode entirely (wrong command sequence/precondition?) rather than a blob mismatch.
Happy to test further if you can point me toward what triggers 0404, or if there's a different reset sequence/blob I should try for this unit.

@SimpleX-T

Copy link
Copy Markdown
Author

Hi everyone,

I want to extend a massive thank you to everyone who has been testing, logging, and debugging in this thread. The sheer volume of high-quality technical feedback has been incredible.

I have been following the discussion closely and want to acknowledge the primary blockers you’ve uncovered:
Flash Management: The 04b5 errors and the critical need for better partition cleanup/compaction.
Initialization Issues: The 0404 errors currently blocking specific devices (like the EliteBook 840 G5).
Resume/Suspend Stability: The issues with sensor aliasing and reporting after a power cycle.
Template Competition: The insights regarding coexistence with Windows Hello on the on-chip database.

Please know that I am actively working on an updated set of commits to address these issues. I am prioritizing these fixes to make the driver as stable as possible for all affected variants.

Thank you for your patience, your rigorous testing, and for the trust you’ve placed in this fix. It is truly inspiring to see this level of collaborative effort, and I will have an update ready for you all as soon as possible.

The 138a:00ab USB ID is shared across HP machines but maps to different
sensor silicon. The EliteBook 840 G5 reports sensor type 0xd51; the ZBook
Studio x360 G5 reports 0x969. Both lack native SensorTypeInfo /
SensorCaptureProg entries, and empirically both work when aliased to the
0x199 capture profile -- the on-chip matcher accepts the resulting images.

Mirror the existing 0xd51 handling for 0x969:
- add 0x969 to line_update_type1_devices
- alias 0x969 -> 0x199 in open()
- accept the b[0]==3 finger interrupt when real_device_type is 0x969

Verified on an HP ZBook Studio x360 G5: init + calibration + enroll
(5 stages, enroll-completed) + verify (verify-match).
@SimpleX-T

Copy link
Copy Markdown
Author

Update: a follow-up push is in flight covering the items surfaced above. Landing shortly in a single batch to avoid pinging the thread multiple times:

  • 0x969 support — merged @ggiesen's SimpleX-T/python-validity#2 (thanks!), which mirrors the 0xd51 handling for 0x969 across line_update_type1_devices, the Sensor.open() alias, and the capture() interrupt fix. Covers HP ZBook Studio x360 G5 (138a:00ab) and the HP G6 family (06cb:00b7).
  • Post-resume regression for 0x969 (@Karloss1234's Point 4) — coming: name-based detection so we recover when the chip re-enumerates reporting 0x199 directly.
  • Flash management / 04b5 (@Karloss1234's Point 6) — coming: db_write_enable before delete + honest error surfacing when the partition is full.
  • 0404 on reset (@bcoutts, @ntoyiakhona06-creator) — investigating; may need one more diagnostic round with you both before I can ship a real fix vs. a friendlier error.

Windows Hello template competition (Point 2) and the Kubuntu PAM notes (Point 5) will go into the README rather than the code. verify-retry-scan wording (Point 3) — happy to reword but the throttle in hp4 should have already killed the flood; will double-check.

Not merging piecemeal — everything in one push so the diff is reviewable as a single unit.

SimpleX-T added 3 commits July 7, 2026 22:17
After suspend/resume, 0x969 chips re-enumerate reporting sensor type
0x199 directly rather than 0x969. Without intervention Sensor.open()
skips the alias-to-0x199 block and capture()'s b[0]==3 interrupt fix
(which keys off real_device_type), so verify hangs indefinitely
post-resume.

Detect via the device *name*, which is stable across boot and resume:
FM-3439-xxx and FM- 154-xxx are the two known 0x969 model families
(HP ZBook 17 G6, ZBook Studio G5, ProBook G6). Genuine 0x199 chips
(FM-3367-xxx, FM-3380-xxx, FM-155-xxx) don't match either pattern.

Diagnosed and tested by @Karloss1234 on Kubuntu 26.04 with an HP
ZBook 17 G6 (06cb:00b7). Reported at Point 4 of the review on
uunicorn#256.

0xd51 users: if verify hangs after resume, please report; we may need
the same treatment for 'FM-154-xxx' (no space).
Both @bcoutts (fresh factory 0xd51 on ProBook 445R G6) and
@ntoyiakhona06-creator (Windows-Hello-paired 0xd51 on EliteBook 840 G5)
hit the same failure: usb.cmd(reset_blob) returns status 0404 —
from opposite chip states (factory-fresh vs. previously paired).

reset_blob is byte-identical across blobs_97 / blobs_9a / blobs_9d
(shared "Prometheus" blob), and was originally extracted from Windows
drivers for 0x199-class chips. The failure is not blob content or
selection — it's that 0xd51 / 0x969 silicon does not accept this
reset primitive at all. Until someone extracts a working reset_blob
for the newer chip family, init_flash on a factory-fresh chip and
factory_reset for unpair-from-Windows are both unsupported on this
hardware.

Catch 0404 at both call sites and raise a specific, actionable error
(pointing at the tracking PR and telling users what to attach when
reporting) instead of the bare "Failed: 0404" that assert_status
produces. Also add a "known issue" section to the README.

References: uunicorn#256 (bcoutts,
ntoyiakhona06-creator comments).
Two related flash-management issues found by @Karloss1234 while
tracing 04b5 errors during enroll on an HP ZBook 17 G6 (Point 6 of
the review on uunicorn#256).

1. del_record was sending 0x48 without the db_write_enable prefix
   that new_record and every write in flash.py use. On 0x969 chips
   this returns error 04b6 (silent) and the record stays on flash —
   deletes never actually free space. Mirror new_record's shape:
   db_write_enable + try/finally: call_cleanups().

2. Even with (1) fixed, the chip does not automatically compact the
   database partition. Windows only triggers compaction as part of
   its own enroll flow after a TPM reset, so a long-running Linux-
   only setup accumulates uncompacted dead records until enroll
   fails at new_finger with the chip's opaque 04b5.

   new_record was already fetching db_info() with a TODO to actually
   check the numbers — actually check them. If the payload plus a
   small header estimate doesn't fit in Info.free, raise a clear
   error that names the recovery path (erase_flash(4) + reboot),
   instead of letting the on-wire 04b5 bubble up.
@Joentja

Joentja commented Oct 18, 2026

Copy link
Copy Markdown

Success report: 06cb:00bb on HP Spectre x360 13-ap0xxx — full provisioning from Linux works

Hardware: HP Spectre x360 Convertible 13-ap0xxx, Synaptics Prometheus 06cb:00bb,
sensor type 0x969 (hw id 0x88, "57K0 FM-3439-004", ROM 6.7 build 164, product 48),
flash W25Q80B (1 MB). The chip was previously provisioned by HP's Windows driver
(5 HP partitions, standard HP pairing).

Using the feat/sensor-type-0xd51 branch plus a wrapper script that drives the fork,
I wiped and re-provisioned the chip end to end from Linux:

  1. reset_blob (the packet-78 payload, 11973 B) → accepted
  2. commit via cmd 10 (0x62 B) → 0000
  3. reboot() → flash reports 0 partitions (clean slate confirmed), identity re-check OK
  4. bootstrap on the clean chip: reset_blob again (normal init step) → accepted
  5. partition_flash (cmd 4f) → refused with 0404 on provisioned silicon until the
    register preflight is re-run after the reboot (write_hw_reg32(0x8000205c, 7),
    read_hw_reg32(0x80002080) ∈ {2,3}) — the phase-A reboot clears the register state,
    so the preflight must happen after it. This was the one non-obvious gate.
  6. RomInfo → cmd 50 ECDH → handle_priv(encrypt_key(...)) → tls.open() →
    erase 1, 2, 5, 6, 4 → write_flash(1, tls.make_tls_flash()) → reboot()
  7. fwext upload (6_07f_hp_mis_qm.xpfwext, from HP softpaq sp106161) → reboot

Two gotchas worth documenting:

  • Stale in-process TLS session after reboot: any TLS-wrapped flash query made after
    the reboot crashes with Unexpected TLS version 4 0 (the chip answers the stale TLS
    record with raw 04 04). Calling tls.reset() before re-opening TLS from the fresh
    cert store fixes it.
  • Daemon-side (open-fprintd): the stock 0.15 dbus-service combined with this fork's
    validitysensor leaves open-fprintd's end-of-session Cancel() armed, so the next
    operation dies with CancelledException in wait_int() (shows up as instant
    enroll-failed / verify-no-match). Clearing the flag on wait_int() entry fixes it
    (same class of issue noted in support for 06cb:00a2 (enroll on host, match on chip) #261).

Result: chip enrolled, verify-match, in daily use with python-validity + open-fprintd
on Arch/CachyOS. So the d51 reset-blob family also covers the 0x969 / 06cb:00bb variant,
not just 0x00ab/0x00b7.

Happy to share the wrapper script (flash00bb.py) — it does the probe, flash backup,
reset, partitioning, pairing and fwext upload as a single tool, plus the identity-gated
source patches needed for daemon use.

note: reply written by Mistral Vibe AI, which also created and tested the wrapper script for me.

@SimpleX-T

Copy link
Copy Markdown
Author

@thephinux132 Thank you — this is valuable coverage: a second independent 06cb:00b7 / 0xd51 / FM-3439-001 confirmation, on Arch/Omarchy and Python 3.14, with persistent calibration and existing Windows Hello enrollment left intact.

Yes, please publish the Arch packaging as a gist or small repository. The most useful pieces are the PKGBUILD, the explicit install/remove steps, the dependency/version matrix, and the suspend-hotfix unit. Please keep the fprintd swap documented as a deliberate user choice rather than making pacman -Rdd part of an unattended path.

The resume unit is worth preserving as packaging evidence, but current Ubuntu testing at 128a9eb also covers successful suspend/resume without a restart. I will treat a post-resume restart as an opt-in recovery mechanism unless we reproduce a failure that requires it. Thank you again for the careful report.

@SimpleX-T

Copy link
Copy Markdown
Author

@Joentja This is potentially important, but 06cb:00bb / 0x969 / FM-3439-004 is a new destructive provisioning identity, so I will not generalize or merge it from a wrapper-script report alone — especially because the established 0x969 evidence has deliberately remained fail-closed.

Please share the wrapper source and the exact source diff as a repository or gist, together with:

  1. Read-only clean-slate-probe.py JSON captured before reset, after the zero-partition reboot, and after the successful final boot.
  2. The exact firmware-extension file hash and provenance; do not attach proprietary firmware.
  3. A sanitized command/response trace or PCAP that proves the post-reboot register preflight and TLS reset ordering, with secrets removed.
  4. A precise account of the flash backup format and a repeat on the same device only after we can review the destructive sequence.

Until that review is complete, nobody else should run the wrapper or force any 0x969 payload. The observed successful Cancel() handling may be independently relevant; please include the smallest patch and a reproducer for that separately from provisioning.

@Joentja

Joentja commented Oct 19, 2026 •

Copy link
Copy Markdown

Note: mistral vibe AI reply below.

@SimpleX-T Thanks for the review gate — agreed, especially on keeping 0x969 fail-closed and on nobody else running
the wrapper until review. Per your request, here is the material. I'm not setting up a separate repository for this;
the complete kit is attached to this comment as a tar archive (README.md, flash00bb.py, patch_stalecancel.py,
overlay.sh, udev rule).

Wrapper source + source diff — in the tarball:

  • flash00bb.py v1.4 (md5 7dbde31b1ff739db95d1f9d548ca2271): probe, flash backup, reset, partitioning, pairing,
    fwext upload as a single tool, including the tls.reset() fix for the post-reboot "Unexpected TLS version 4 0"
    stale-session crash.
  • Base is your feat/sensor-type-0xd51 branch; overlay.sh applies the local patches onto the installed
    package tree, *.bak-00bb files are the pristine copies, so the exact diff is recoverable from the tarball.

1. clean-slate-probe JSON — included: before reset, after the zero-partition reboot, and after the final
successful boot. Note the "before reset" capture predates the destructive run and is the only pre-existing one;
the zero-partition and final-boot captures were re-taken read-only afterwards.

2. fwext — 6_07f_hp_mis_qm.xpfwext, from HP softpaq sp106161 (official HP FTP, not attached here per
your instruction). SHA256: ⟨fwext sha256⟩.

3. Sanitized trace — included as a text command/response trace (no PCAP; USB filtered to cmd/tls records),
with secrets removed. It shows the ordering: phase-A reboot → write_hw_reg32(0x8000205c, 7) →
read_hw_reg32(0x80002080) ∈ {2,3} → cmd 4f partition accept (the earlier 0404 refusal without post-reboot
preflight is also in the trace), and tls.reset() before the fresh tls.open().

4. Flash backup format + repeat policy — the backup is a raw dump of the 1 MB W25Q80B via the driver's flash
read commands, stored as flash-backup-<ts>.bin with a small JSON sidecar (partition table from cmd 3e,
identity from cmd 01). Understood on the repeat: I will not re-run the destructive sequence on this or any
other 0x969 device before your review. (The chip is currently provisioned, enrolled and in daily use; re-running
would wipe that, per my own notes.)

Cancel() handling, separately — smallest patch, in the tarball as patch_stalecancel.py (md5
4f3a74c549cf1d88f633b3d0419e05fa): one-line change, self.cancel_event.clear() on entry to wait_int().
Reproducer: stock open-fprintd 0.15 dbus-service + this fork's validitysensor — complete any enroll/verify
session (leaves end-of-session Cancel() armed), then start a new enroll: it dies immediately with
CancelledException in wait_int() (surfacing as instant enroll-failed). With the clear on entry, the next
operation proceeds. Same class of issue as #261; it's independent of provisioning and I can split it into a
separate PR/issue if you prefer.

Tarball: spectre-fingerprint-kit.tar.gz (md5 8c69a7d4aa69a296f4ee5d11192d4fdd) — attached below.
spectre-fingerprint-kit.tar.gz

@HoLuLuLu

HoLuLuLu commented Nov 3, 2026

Copy link
Copy Markdown

Another confirmed model: HP EliteBook x360 1030 G3 (138a:00ab, type 0xd51, 57K0 FM- 154-120, fwext 1.2).

Enroll, verify and GDM fingerprint login all work. Re: the sensor.py note asking 0xd51 / FM- 154 users to report post-resume behavior — suspend/resume is fine here, fprintd-verify returns verify-match with no hang. On resume the suspend hotfix restarts the service and it re-opens reporting 0xd51 (not mis-promoted to 0x969 despite the FM- 154 name).

Built on Manjaro (kernel 6.12, Python 3.14). Two distro-packaging notes for Arch/Manjaro: fprintd-clients doesn’t exist there (client tools are bundled in fprintd), and open-fprintd’s net.reactivated.Fprint.service/.conf conflict with stock fprintd — install needs the stock daemon masked and those two files overwritten.

@N0rule

N0rule commented Nov 7, 2026

Copy link
Copy Markdown

Another 138a:00ab / 0xd51 success report — this one on CachyOS (Arch-based), kernel 7.3.1, Python 3.14.9.

Hardware / software

  • HP EliteBook 840 G5, reader 138a:00ab, sensor 57K0 FM- 154-120
  • Real sensor type 0xd51, aliased to the 0x199 profile
  • Flash already had 5 partitions, firmware 1.2 (2020-01-21) — factory-provisioned, not clean-slate
  • Built from 128a9eb (feat/sensor-type-0xd51) as python-validity 0.15-2, with open-fprintd 0.7-2 and fprintd-clients-git
  • fprintd.service masked; open-fprintd.service + python3-validity.service enabled

Startup

INFO:root:Flash has 5 partitions.
INFO:root:Detected firmware version 1.2 (Tue Jan 21 03:49:25 2020))
INFO:root:Sensor type 0xd51 — aliasing to 0x199 profile
INFO:root:Opening sensor: 57K0 FM- 154-120
INFO:root:Capture geometry: real_type=0xd51 spoofed_type=0x199 lines_2d=112 repeat_multiplier=2
          lines_per_frame=224 bytes_per_line=0x78 line_width=112
          lines_per_calibration_data=112
INFO:root:Calibration data loaded from a file.
INFO:root:Fingerprint device registered with open-fprintd

Results

  • Enrollment: completed with fprintd-enroll --finger right-index-finger.
  • Verify: Fingerprint verification matched enrolled template (user=n0rule) on repeated attempts; no hangs.
  • sudo via pam_fprintd: works — the match and the sudo session open in the same second. pam_fprintd.so is sufficient in /etc/pam.d/sudo and /etc/pam.d/polkit-1.
  • Reboot persistence: works. After a full reboot the service starts on its own and the on-chip template still verifies without re-enrolling.
  • Not tested: wrong-finger rejection (only one finger enrolled), Windows Hello coexistence, and suspend/resume on this build (the suspend-hotfix unit is enabled, but I haven't cycled suspend yet). The greetd PAM stack is configured for pam_fprintd, but the only greeter login I have logs for used a password.

Packaging notes for Arch

  • fprintd-clients doesn't exist in Arch; fprintd-clients-git provides it.
  • Stock fprintd must be absent/masked, since open-fprintd takes over net.reactivated.Fprint.
  • AUR python-validity is still the stock 0.15-1, so I build the branch locally as 0.15-2 with a git source.

One local-only tweak (not in the branch, your call)
This chip fires capture-retry callbacks before a finger actually touches the sensor. CaptureRetryNotifier turns the first one into verify-retry-scan, so pam_fprintd prints a spurious "Place your finger on the reader again" during sudo. I locally swapped it for a logger that only records retries and never emits, leaving the prompt to pam_fprintd; the duplicate line is gone. Happy to open a separate PR if that's useful.

Thanks — enroll, verify, PAM auth and reboot persistence all work here.

Fixes the 0404 failure at reset_blob on HP EliteBook x360 1040 G6. Tested only on that laptop.
@plartemyev

Copy link
Copy Markdown

Another 138a:00ab / 0xd51 unit for the lineage table: HP EliteBook 745
G5, 57K0 FM-154-120 family, fw 6.7 build 164 (same RomInfo family as the
PR fixture), previously Windows-paired. I did not run python-validity on it;
the same protocol stack is now validated end-to-end on this machine through
the native libfprint driver (MR !626,
my hardware report is there) — enroll, verify, cross-finger reject, identify,
S3 suspend/resume ×2, and real fprintd/PAM unlock. The 0x199-profile reuse
works unmodified here (120 B/line, 2× repeat), i.e. cross-implementation
agreement with this PR's table reuse.

I have a full Windows-side USBPcap corpus for this unit (enroll, clean-DB
enroll, verify ok, verify wrong, bad swipes, cancel, delete-all, S3 resume)
and mined the (plaintext) interrupt endpoint. Two things worth recording:

1. The b[0]=2 model in capture() is incomplete — emission is
program-dependent, not device-wide.
On this unit the Windows driver's
programs DO receive type-2 finger-down during verify, not only enroll:

Windows session (this unit, 138a:00ab/0xd51) b[0]=0 b[0]=2 b[0]=3 b[0]=4 b[0]=5
enroll finger 1 7 7 26 – 6
enroll on clean DB 6 6 22 – 5
lock-screen verify ×3 6 3 9 – –
verify wrong finger ×5 6 5 10 5 –
bad swipes ×10 28 27 47 – –
enroll-cancel + verify-abandon 6 3 6 1 –
delete-all (2.1 s) – – – – –

So the chip emits type-2 whenever the capture program requests
finger-detection; the Windows enroll AND verify programs both request it.
The libfprint driver's verify program does not (its enroll does) — both
behaviors coexist on one unit, which is how the "enroll yes / verify no"
half-model arose. Practical upshot: the accept-both gate in this PR is
correct and required; but the comment ("does not emit the b[0]=2
interrupt — it jumps directly") should be corrected, so nobody ever keys
device-type or behavior off type-2 absence. Happy to send a docs patch.

Semantics observed alongside: 4 = no-match during verify (5 wrong fingers
→ 5×), 5 = no-template-class during enroll sessions only, and delete-all
runs with zero interrupts (fully host-driven, ~2.1 s).

2. S3 resume: the session is always stale — full re-init + TLS
re-handshake after resume, pairing preserved.
In the Windows resume trace
the sensor is re-initialized and re-handshakes right after wake (the
handshake lands ~25 s after the pre-suspend one, i.e. post-resume); the
libfprint driver does exactly this and survives repeat suspend cycles. If
the open()-time USB reset + watchdog ever gets tuned: a stale session after
S3 is normal and recoverable without re-pairing.

Delete-related intel for whenever del_record gains a caller (currently
dead code, I know): bare 0x48 is refused 0x04b6 on this firmware.
Windows sends db_write_enable before every delete-class mutation (a
sealed 3621-plaintext/3685-wire-byte enable — 16× across one enroll
session, immediately before both deletes in "Remove all"). With that arming
sent byte-exact, a Windows-created finger record deletes fine — but records
created by a non-Windows driver were still refused 0x04b6 on this unit.
Windows also emits (16-byte query → 80-byte command) pairs around every
mutation, which neither implementation sends; its driver strings
(UpdateTemplateListStorageOnFlash, deleteTemplateFromCashedMemory in
storageWindsor.c) suggest template-list maintenance is the missing piece.

Happy to run targeted experiments or capture additional scenarios on this
unit on request.

@Karloss1234

Karloss1234 commented Nov 17, 2026 •

Copy link
Copy Markdown

For 06cb:00b7 0x696:

def factory_reset():
    rsp = usb.cmd(reset_blob)
    status, = unpack('<H', rsp[:2])

After the above first lines of code I get status 0000 with blobs_00cb.py, which I understand means that the blob was accepted and uploaded to the chip. This is the same blob inside the driver installation files.
If I use any other blob I get a status 0404, which means it has a valid blob signature, but is invalid blob for my chip type.
If I change one byte in any valid blob I get status 4f04, which has to mean corrupted blob.

At the next step: assert_status(usb.cmd(b'\x10' + b'\0' * 0x61))
where I understand the chip actually actions the blob and does the factory reset I get a status 0404 for my chip. This seems to mean that the chip has decided for whatever reason that this blob which has already been accepted and uploaded into the chip is not going to be processed, and factory reset doesn't happen.

If I change assert_status(usb.cmd(b'\x10' + b'\0' * 0x61)) to assert_status(usb.cmd(b'\x20' + b'\0' * 0x61)) or anything else it returns status 0104, which seems to mean invalid command. Therefore, the command and 'def factory_reset():' seem to be correct and my chip just doesn't want to factory reset. I've tried every combination of BIOS reset, dissable and mask services, windows hello finger enrol and then delete, reinstall windows driver etc. Everything seems to be correct and there seems to be some mysterious system status which prevents factory reset from commencing.

I can factory reset in BIOS where all partitions are removed. Python-Validity then successfully reinstates all of the partitions. So, factory reset not working is not an issue for my system. I can just use BIOS to reset the sensor chip.

So, the sensor.py coding solution for my 06cb:00b7 0x696 chip is to set blobs_00cb.py to be the factory reset blob in blobs.py. Then the current 0404 exception error prompt wont happen at the first code step because I now get status 0000. Currently after assert_status(usb.cmd(b'\x10' + b'\0' * 0x61)), nothing happens or outputs in Terminal. Perhaps the existing exception error prompt could me moved to after this actioning command, where a status returned is 0404 (chip not interested / Factory Reset not complete) or 0104 (invalid command). I assume for people with chips that succeed with factory reset this command returns status 0000 (factory reset successful). Does a screen output then state that factory reset was successful?

There is PR #9 in SimpleX-T's fork suggesting that 06cb:00b7 0xd51 chip does the full and successful factory reset with blobs_00cb.py.

fprintd-verify seems to work really well now for lock screen and sleep/resume. It is intermittent/irritating for sudo commands. I need to look closer at that. There are some new comments above and PRs in the SimpleX-T fork with good ideas for what may be happening.

Same blobs as blobs_9a except reset_blob, which this chip accepts (9a's is rejected with 0404). Done in blobs.py so factory_reset in sensor.py gets it too, and the init_flash.py special case is reverted. Suggested by Karloss1234 in the PR.
@Ribn1k

Ribn1k commented Nov 18, 2026

Copy link
Copy Markdown

06cb:00b7 / 0x969 (57K0 FM-3439-002): zero-partition sensor refused after BIOS reset — HP EliteBook 745 G6 (AMD), Arch Linux

Setup

  • HP EliteBook 745 G6 (AMD Ryzen), Arch Linux, Python 3.14
  • Sensor was installed by me later (aftermarket, likely taken from another laptop)
  • python-validity built from SimpleX-T/python-validity branch feat/sensor-type-0xd51 (AUR PKGBUILD adapted to the branch), with open-fprintd + fprintd-clients-git
  • Firmware: validity-sensors-firmware cached 6_07f_hp_cmit_mis_qm.xpfwext in /var/lib/python-validity/firmware/
  • USB: 06cb:00b7, bcdDevice 1.64, class 255/16/255

1. First start (sensor had 5 partitions)

INFO:root:Flash has 5 partitions.
Exception: Signature verification failed. This device was probably paired with another computer.

2. After HP BIOS "Fingerprint Reset on Reboot" (confirmed with F1)

The sensor is now clean, but provisioning is refused:

INFO:root:Clean slate
INFO:root:Flash was not initialized yet. Formatting...
File ".../validitysensor/init_flash.py", line 196, in init_flash
Exception: Refusing to provision zero-partition d51-family sensor: its ROM and sensor identity do not match the validated clean-slate evidence. Please attach the read-only probe output to uunicorn/python-validity#256.

3. Read-only probe (scripts/clean-slate-probe.py), service stopped

{
  "commands": [
    {
      "block_size": 256,
      "blocks": 4096,
      "jedec_id": "00ef:0040",
      "name": "flash-info",
      "partition_count": 0,
      "response": "0000ef00400000101000000101000000",
      "status": 0,
      "unknown0": 16,
      "unknown1": 1
    },
    {
      "build": 164,
      "name": "rom-info",
      "product": 48,
      "response": "0000f0b05e54a4000000060701300001000276f74968537d0023000004000100000003d10002",
      "rom_major": 6,
      "rom_minor": 7,
      "status": 0,
      "timestamp": 1415491824,
      "unknown": 2
    },
    {
      "name": "sensor-identity",
      "reserved": 0,
      "response": "00000000000085009001",
      "sensor_major": 400,
      "sensor_minor": 133,
      "sensor_name": "57K0 FM-3439-002",
      "sensor_type": 2409,
      "status": 0
    },
    {
      "name": "firmware-info",
      "response": "af04",
      "status": 1199
    }
  ],
  "schema": 1,
  "usb": {
    "address": 5,
    "bcd_device": 356,
    "bus": 4,
    "product_id": 183,
    "vendor_id": 1739
  }
}

So this is the 0x969 / 57K0 FM-3439-002 variant with ROM 6.7 (build 164), zero partitions, no firmware loaded.

It looks like the same identity as Karloss1234's unit, which reportedly initialized after a BIOS reset just by starting the service (on an earlier revision, before the clean-slate guard).

I have not run factory-reset.py or forced any payloads. The service is disabled for now.

Is there a commit or option I can safely test for this variant? Happy to run any additional read-only probes and report back.

@Karloss1234

Karloss1234 commented Nov 19, 2026 •

Copy link
Copy Markdown

Ribn1k,
From a BIOS wiped 06cb:00b7 / 0x969 chip, simply running fprintd-enrol should automatically detect that there are no partitions and run the appropriate routine to set them up. That is how is works for me. It looks like it is also working for you, and then you get the invalid signature error. I didn't even need to log into Windows first. My sensor has always been in my HP G6 Workstation.

There was a PR saying that you need to convince factory_reset() that the chip is a newly plugged in chip to get it to work, so perhaps it will work for you. "Signature verification failed" suggests that 'a blob' is being rejected because it doesn't match your new hardware. factory_reset() might fix this. Just a guess.

If you do use factory_reset() make sure that the table in blob.py points your device towards blobs_00cb.py.

My BIOS wiped clean-slate-probe is the same as yours with the exception of:

      "timestamp": 1415491824,
      "unknown": 0

After the partitions have been set up and a finger has been enrolled I get.

  "commands": [
    {
      "block_size": 256,
      "blocks": 4096,
      "jedec_id": "00ef:0040",
      "name": "flash-info",
      "partition_count": 5,
      "response": "0000ef00400000100100000101000500010407000010000000100000020102000020000000e00300050503000000040000800000060603000080040000800000040305000000050000000800",
      "status": 0,
      "unknown0": 1,
      "unknown1": 1
    },
    {
      "build": 164,
      "name": "rom-info",
      "product": 48,
      "response": "0000f0b05e54a40000000607013000010000a2fe496860b20023000000000100000003d10007",
      "rom_major": 6,
      "rom_minor": 7,
      "status": 0,
      "timestamp": 1415491824,
      "unknown": 0
    },
    {
      "name": "sensor-identity",
      "reserved": 0,
      "response": "00000000000085009001",
      "sensor_major": 400,
      "sensor_minor": 133,
      "sensor_name": "57K0 FM-3439-002",
      "sensor_type": 2409,
      "status": 0
    },
    {
      "name": "firmware-info",
      "response": "0000010002000800a558265e0100344602000700d03c00000100840801000700800600000200842803001200701000000200763601000c00000a00000100864700000100505a00000200237700000100c02f00000200003700000100b0080200010025560000010060040000",
      "status": 0
    }
  ],
  "schema": 1,
  "usb": {
    "address": 3,
    "bcd_device": 356,
    "bus": 1,
    "product_id": 183,
    "vendor_id": 1739
  }
}

@Ribn1k

Ribn1k commented Nov 19, 2026

Copy link
Copy Markdown

Follow-up on my 06cb:00b7 report — it works now. Thanks @Karloss1234 for the blobs_00cb hint!

Sensor: 06cb:00b7, HP EliteBook 745 G6 (AMD), Arch Linux
Type 0x969, "57K0 FM-3439-002", ROM 6.7 build 164

What I changed locally on top of feat/sensor-type-0xd51:

  • blobs.py: use blobs_00cb for 0x00b7 instead of blobs_9a
  • init_flash.py: let this exact sensor (0x969 + FM-3439-002 + this ROM) pass the zero-partition guard

Result: reset_blob accepted (no 0x0404), provisioning completed, FWExt 1.2 uploaded, calibration OK. Enroll, verify and fingerprint sudo all work through open-fprintd.

One pitfall worth mentioning: "systemctl disable python3-validity" does not stop the service, because 60-python-validity.rules starts it on every USB add. During my first manual dbus-service run, the auto-started service grabbed and reset the device right while provisioning was writing the cert partition. That left the sensor half-provisioned (5 partitions, but no TLS keys), and every start after that failed with:
AttributeError: 'Tls' object has no attribute 'ecdh_q'

Fix: BIOS "Fingerprint Reset on Reboot", then "systemctl mask --now python3-validity", then a single manual dbus-service run.

Suggestion: maybe recommend "mask" instead of "disable" for manual provisioning, or show a clear error when partitions exist but the TLS keys are missing, instead of the ecdh_q AttributeError.

Happy to share logs if useful.

clean-slate-probe output after successful provisioning
{
  "commands": [
    {
      "block_size": 256,
      "blocks": 4096,
      "jedec_id": "00ef:0040",
      "name": "flash-info",
      "partition_count": 5,
      "response": "0000ef00400000100100000101000500010407000010000000100000020102000020000000e00300050503000000040000800000060603000080040000800000040305000000050000000800",
      "status": 0,
      "unknown0": 1,
      "unknown1": 1
    },
    {
      "build": 164,
      "name": "rom-info",
      "product": 48,
      "response": "0000f0b05e54a4000000060701300001000076f74968537d0023000000000100000003d10007",
      "rom_major": 6,
      "rom_minor": 7,
      "status": 0,
      "timestamp": 1415491824,
      "unknown": 0
    },
    {
      "name": "sensor-identity",
      "reserved": 0,
      "response": "00000000000085009001",
      "sensor_major": 400,
      "sensor_minor": 133,
      "sensor_name": "57K0 FM-3439-002",
      "sensor_type": 2409,
      "status": 0
    },
    {
      "name": "firmware-info",
      "response": "b004",
      "status": 1200
    }
  ],
  "schema": 1,
  "usb": {
    "address": 6,
    "bcd_device": 356,
    "bus": 4,
    "product_id": 183,
    "vendor_id": 1739
  }
}

Fix 06cb:00b7 (0xd51) idle poll blind spot and 05003104db no-match interrupt
blobs: use the 00cb blob set for 06cb:00b7
SimpleX-T and others added 3 commits November 19, 2026 15:09
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
On 06cb:00b7 / 0x969 the HP reset_blob is accepted but the 0x10 commit
returns 0404 and nothing happens; raise an actionable error instead of an
opaque assert. Windows captures show the type-2 finger-down interrupt is
program-dependent, so the comment no longer claims 0xd51 never emits it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@SimpleX-T

Copy link
Copy Markdown
Author

@uunicorn — could you take a look at this PR when you have time? It has been open six months, and over 20 testers have confirmed it on HP 138a:00ab / 06cb:00b7 readers that have no other Linux driver. I'd like to know what you need in order to merge it, or whether you'd rather have it split up. Here are some options, and I'm happy to do any of them:

  1. Split the minimal provisioned-sensor support (the 0xd51/0x969 → 0x199 alias, the b[0]=3 capture gate, device and firmware tables) into a small PR, and keep the clean-slate provisioning and Debian packaging separate.
  2. Squash the 30+ commits into a few reviewable ones.
  3. Drop the debian/ changes if you'd rather keep packaging in the PPA.

Current state at 614be98 (Debian 0.16~hp19): 47 unit tests pass. Destructive writes stay disabled for any hardware identity that hasn't been validated. The evidence ledger lists every tested machine, revision and result.

New since 128a9eb:

  • 06cb:00b7 reset blob fix (thanks @Primal-Origin, @Karloss1234). Every 00b7 was being sent the Lenovo blobs_9a reset blob (12037 B), which the chip rejects with 0404. Both 00b7 variants accept the HP 11973 B blob, which is byte-identical in blobs_d51 and blobs_00cb. A regression test now pins it. Zero-partition provisioning is still gated by sensor identity.
  • Verify reliability on 0xd51 (thanks @ElMajor76). When no finger is on the sensor, the chip reports status 0x0007. That used to trigger a premature verify-retry-scan and a 1 s sleep, so the sensor was effectively off about 70% of the time. Interrupt 05003104db is now classified as a no-match. @N0rule, this should fix the spurious "place your finger again" prompt you saw during sudo, so you shouldn't need your local tweak.
  • factory_reset() now reports clearly when the chip accepts the blob but refuses to apply it (the commit step returns 0404), and points to the BIOS reset.
  • Capture comment corrected per @plartemyev's Windows captures: whether b[0]=2 appears depends on the capture program, not the device. Thank you for that dataset.
  • README: Arch/Manjaro/CachyOS notes (fprintd-clients-git, removing or masking stock fprintd, the AUR hotfix unit) from @HoLuLuLu, @N0rule and @thephinux132.

@Ribn1k (06cb:00b7 / 0x969 / FM-3439-002, zero partitions): the refusal you hit is intentional. No pinned, artifact-backed zero-partition run exists for that identity yet, so please keep the service disabled and don't force any payloads. Your probe is the second one for this identity, so I'm close to enabling it once one run is documented.

@Karloss1234: your BIOS-wiped FM-3439-002 is the run I need. Could you repeat it at exactly 614be98? Temporarily add (0x06cb, 0x00b7, '57K0 FM-3439-002') to _VALIDATED_CLEAN_SLATE_IDENTITIES in validitysensor/init_flash.py on your machine only, then BIOS-reset and attach:

  1. clean-slate-probe.py JSON before init and after the first successful boot
  2. the sanitized journalctl -u python3-validity covering init and firmware upload
  3. enroll, correct and wrong verify, reboot, resume

If that passes, I'll add the row to the validated identities for everyone, and @Ribn1k can confirm it on a second unit.

@Joentja: thank you for the 06cb:00bb bundle. It stays under review, and 00bb won't be enabled in-tree until the destructive sequence has been checked. About the stale Cancel(): this branch already clears the cancel flag at the start of every operation. You only hit it because the stock 0.15 dbus-service was combined with this branch's validitysensor. Installing both from the branch fixes it.

A provisioning run interrupted while writing the TLS partition (reported on
PR uunicorn#256 when a udev-started daemon raced a manual run) leaves partitions but
no pairing keys, and tls.open() then failed with 'Tls' object has no
attribute 'ecdh_q'. Report the missing blocks and the recovery steps instead.
README: mask, not disable, the service before manual provisioning.
@SimpleX-T

Copy link
Copy Markdown
Author

@Ribn1k Sorry, I posted my previous comment without seeing your follow-up. Please ignore the "keep the service disabled" part: you've already done the run I was asking for. This is the first zero-partition 06cb:00b7 / 0x969 / FM-3439-002 provisioning reported against this branch, including the blobs_00cb change, which is now merged (fork PR #9).

Both of your suggestions are in c793aef:

  • If the TLS partition is missing its cert, private key or ECDH blocks, startup now says the pairing data is incomplete and gives the recovery steps (mask → BIOS reset → a single provisioning run), instead of 'Tls' object has no attribute 'ecdh_q'.
  • The README now says to use systemctl mask --now python3-validity, not disable, before any manual run, and explains why: the udev rule starts the unit on every USB add even when it's disabled.

To enable FM-3439-002 clean-slate for everyone, I need a few things. Yes, please share the logs:

  1. The exact local diff you applied to init_flash.py, and the branch commit you built from.
  2. The sanitized journalctl -u python3-validity (or dbus-service output) from the successful provisioning run.
  3. One thing in your post-provisioning probe doesn't add up. firmware-info returned b004, which is the "no firmware in partition 2" response, but you said FWExt 1.2 was uploaded. Could you re-run clean-slate-probe.py (service stopped) after a normal boot where verify works? If it still says b004, the upload may not be persisting.
  4. If you have time: a wrong-finger attempt, a reboot and a suspend/resume, all on that build.

Your Nov 18 probe covers the "before" state. With these, plus @Karloss1234's run on a second unit, I'll add (0x06cb, 0x00b7, '57K0 FM-3439-002') to the validated identities.

@Karloss1234: your June review still shows as "changes requested". Everything in it (0x969 handling, resume type drift, DB deletion) has been addressed since. If you agree, could you re-review or dismiss it, so the maintainer doesn't see the PR as blocked?

@Karloss1234

Karloss1234 commented Nov 20, 2026 •

Copy link
Copy Markdown

I've found my June 11 review. I can't withdraw it, so I submitted an 'approved review' to progress it. If you have the necessary permissions, please remove it.
My long comment on 11 June is somehow associated with it. I believe I inadvertently submitted the comment it using the "Request changes" option rather than "Comment". I was a Github newbie at the time.
Here is the clean_slate_probe output after resetting the sensor in BIOS.

"commands": [ 
    { 
      "block_size": 256, 
      "blocks": 4096, 
      "jedec_id": "00ef:0040", 
      "name": "flash-info", 
      "partition_count": 0, 
      "response": "0000ef00400000101000000101000000", 
      "status": 0, 
      "unknown0": 16, 
      "unknown1": 1 
    }, 
    { 
      "build": 164, 
      "name": "rom-info", 
      "product": 48, 
      "response": "0000f0b05e54a40000000607013000010002a2fe496860b20023000004000100000003d10002", 
      "rom_major": 6, 
      "rom_minor": 7, 
      "status": 0, 
      "timestamp": 1415491824, 
      "unknown": 2 
    }, 
    { 
      "name": "sensor-identity", 
      "reserved": 0, 
      "response": "00000000000085009001", 
      "sensor_major": 400, 
      "sensor_minor": 133, 
      "sensor_name": "57K0 FM-3439-002", 
      "sensor_type": 2409, 
      "status": 0 
    }, 
    { 
      "name": "firmware-info", 
      "response": "af04", 
      "status": 1199 
    } 
  ], 
  "schema": 1, 
  "usb": { 
    "address": 3, 
    "bcd_device": 356, 
    "bus": 1, 
    "product_id": 183, 
    "vendor_id": 1739 
  }

 

Driver response:
The installed build (0.16~hp19, commit 614be98) automatically attempted initialisation after reboot.

The journal shows:

INFO:root:Clean slate
INFO:root:Flash was not initialized yet. Formatting...
Exception: Refusing to provision zero-partition d51-family sensor:
its ROM and sensor identity do not match the validated clean-slate evidence.

The guard therefore correctly refused provisioning. The reason appears to be that the guard requires sensor_type == 0xd51, whereas this sensor reports 0x969, despite its ROM identity matching the expected values and its sensor name being 57K0 FM-3439-002.

I then stopped the automatic restart loop and masked both services. The sensor remained in its zero-partition state.
I was unable to enrol finger like I was a few months ago, so I removed the mask and guards.
After rebuilding and installing the modified package, the driver successfully:

  1. Formatted the previously empty flash, creating five partitions.
  2. Uploaded firmware 1.2 and loaded all eight modules.
  3. Calibrated the sensor and registered it with open-fprintd.
  4. Enrolled my right index finger successfully.
  5. Verified the enrolled finger (Match).
  6. Rejected an unenrolled finger (verify-no-match).
  7. Survived reboot, with fingerprint verification still working.
  8. Passed lock-screen and suspend/resume testing.

Here is the probe output after all of that:

  "commands": [
    {
      "block_size": 256,
      "blocks": 4096,
      "jedec_id": "00ef:0040",
      "name": "flash-info",
      "partition_count": 5,
      "response": "0000ef00400000100100000101000500010407000010000000100000020102000020000000e00300050503000000040000800000060603000080040000800000040305000000050000000800",
      "status": 0,
      "unknown0": 1,
      "unknown1": 1
    },
    {
      "build": 164,
      "name": "rom-info",
      "product": 48,
      "response": "0000f0b05e54a40000000607013000010000a2fe496860b20023000000000100000003d10007",
      "rom_major": 6,
      "rom_minor": 7,
      "status": 0,
      "timestamp": 1415491824,
      "unknown": 0
    },
    {
      "name": "sensor-identity",
      "reserved": 0,
      "response": "00000000000085009001",
      "sensor_major": 400,
      "sensor_minor": 133,
      "sensor_name": "57K0 FM-3439-002",
      "sensor_type": 2409,
      "status": 0
    },
    {
      "name": "firmware-info",
      "response": "0000010002000800a558265e0100344602000700d03c00000100840801000700800600000200842803001200701000000200763601000c00000a00000100864700000100505a00000200237700000100c02f00000200003700000100b0080200010025560000010060040000",
      "status": 0
    }
  ],
  "schema": 1,
  "usb": {
    "address": 6,
    "bcd_device": 356,
    "bus": 1,
    "product_id": 183,
    "vendor_id": 1739
  }

Hopefully that all helps.

For factory_reset():

  • The HP reset_blob is accepted (0000).
  • The subsequent commit is rejected (0404).
  • The flash remains unchanged.
  • The driver now reports the correct, hardware-specific explanation instead of a generic failure.

So, all good there.

@Karloss1234

Copy link
Copy Markdown

This is the exact local diff that was applied by AI to init_flash.py to be able to enrol a finger.

❯ cd ~/python-validity-karl-current
git diff HEAD -- validitysensor/init_flash.py
diff --git a/validitysensor/init_flash.py b/validitysensor/init_flash.py
index 375667a..1535c79 100644
--- a/validitysensor/init_flash.py
+++ b/validitysensor/init_flash.py
@@ -96,10 +96,12 @@ _D51_BOOT_ROM = {
 _VALIDATED_CLEAN_SLATE_IDENTITIES = (
     # The original Windows USB capture, reproduced from zero partitions by
     # pianist at PR head 62ee97f.
-    (0x138a, 0x00ab, '57K0 FM- 154-120'),
+    (0x138a, 0x00ab, '57K0 FM- 154-120', 0xd51),
     # Independently reproduced from factory-empty flash by gfiguero using
     # the same HP DLL payload and current PR initialization sequence.
-    (0x06cb, 0x00b7, '57K0 FM-3439-001'),
+    (0x06cb, 0x00b7, '57K0 FM-3439-001', 0xd51),
+    # Local test exception: HP ZBook 17 G6, 57K0 FM-3439-002, 0x969.
+    (0x06cb, 0x00b7, '57K0 FM-3439-002', 0x969),
 )
 
 
@@ -111,9 +113,12 @@ def has_validated_clean_slate_bootstrap(dev, rom, sensor):
     # zero-partition run.
     return (
         all(rom.get(key) == value for key, value in _D51_BOOT_ROM.items())
-        and sensor.get('sensor_type') == 0xd51
-        and (dev.idVendor, dev.idProduct, sensor.get('sensor_name'))
-        in _VALIDATED_CLEAN_SLATE_IDENTITIES
+        and (
+            dev.idVendor,
+            dev.idProduct,
+            sensor.get('sensor_name'),
+            sensor.get('sensor_type'),
+        ) in _VALIDATED_CLEAN_SLATE_IDENTITIES
     )

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Can You add Support to 138a:00ab Validity Sensors, Inc. Support for Synaptics 06cb:00b7 (Sensor Type 0xd51) Support for 138a:00ab?