You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Support for 06cb:00a2 Synaptics, Inc. Metallica MOH Touch Fingerprint Reader #170
I have a 06cb:00a2 (Synaptics Metallica MOH) on a ThinkPad L390 and have got python-validity most of the way through init on it. Posting the details in case they're useful to anyone else with this chip.
Environment
ThinkPad L390, Arch Linux
Sensor: 06cb:00a2 Synaptics, Inc. Metallica MOH Touch Fingerprint Reader
Byte-for-byte identical except the 6-byte serial field in the middle. Same firmware version (060701), same sensor type. So MIS and MOH appear to be the same silicon and the same ROM, the distinction must live above this layer.
Changes I made to get this far
usb.py: added DEV_a2 = (0x06cb, 0x00a2) to SupportedDevices
firmware_tables.py: copied the DEV_9a entries into FIRMWARE_URIS and FIRMWARE_NAMES verbatim (same installer, same sha512, same 6_07f_lenovo_mis_qm.xpfwext)
blobs.py: added an 0x00a2 branch importing blobs_9a
usb.pyopen_dev(): added self.dev.reset() + 1s sleep after self.dev = dev, before set_configuration()
init.pyopen_common(): added a usb.cmd(b'\x01') before init_flash()
On (4) and (5): without the wake command, get_flash_info (cmd 3e) fails with status 0304. With it, 3e returns a full 76-byte header + partition table and status 0000. Probing by hand, cmd 01 answers correctly on the first attempt and 3e answers correctly once 01 has been sent first, so this looks like a variant of the transient-busy behaviour described in #271/#272, but with a different status code.
The firmware fetcher works unmodified once the table entries are added, it downloads nz3gf07w.exe and extracts the standard MIS blob, hash matches.
Where it stops
init_flash() now completes successfully (flash formatted, partition table written). It then fails in usb.send_init():
File "validitysensor/usb.py", line 92, in send_init
assert_status(self.cmd(init_hardcoded))
Exception: Failed: 04be
So every generic command works, and the one device-specific payload, init_hardcoded from blobs_9a, is rejected with 04be. Which is roughly what you'd expect if the MOH part needs its own configuration blob.
Questions
Does anyone recognise status 04be, or 0304 from get_flash_info?
Does anyone with a 00a2 and a Windows install have the ability to capture the init traffic? What I'm missing is the init_hardcoded payload the Windows driver sends to this device. That's the one piece blocking further progress, and I can't produce it myself.
Is init_hardcoded known to be a fixed per-device constant, or is it derived from something at runtime? If it's a constant, a single capture would likely be enough to add a blobs_a2.py.
I'd be happy to run any experiments on this hardware and report back with my findings!
Activity
qkyubit commentedon Sep 20, 2026
I have a 06cb:00a2 (Synaptics Metallica MOH) on a ThinkPad L390 and have got python-validity most of the way through init on it. Posting the details in case they're useful to anyone else with this chip.
Environment
Most important finding: the ROM info is identical to a 009a apart from the serial.
Comparing my
cmd 01response against the one posted in #272 for a 06cb:009a (T480s):Byte-for-byte identical except the 6-byte serial field in the middle. Same firmware version (060701), same sensor type. So MIS and MOH appear to be the same silicon and the same ROM, the distinction must live above this layer.
Changes I made to get this far
usb.py: addedDEV_a2 = (0x06cb, 0x00a2)toSupportedDevicesfirmware_tables.py: copied theDEV_9aentries intoFIRMWARE_URISandFIRMWARE_NAMESverbatim (same installer, same sha512, same6_07f_lenovo_mis_qm.xpfwext)blobs.py: added an0x00a2branch importingblobs_9ausb.pyopen_dev(): addedself.dev.reset()+ 1s sleep afterself.dev = dev, beforeset_configuration()init.pyopen_common(): added ausb.cmd(b'\x01')beforeinit_flash()On (4) and (5): without the wake command,
get_flash_info(cmd 3e) fails with status0304. With it, 3e returns a full 76-byte header + partition table and status0000. Probing by hand,cmd 01answers correctly on the first attempt and 3e answers correctly once 01 has been sent first, so this looks like a variant of the transient-busy behaviour described in #271/#272, but with a different status code.The firmware fetcher works unmodified once the table entries are added, it downloads nz3gf07w.exe and extracts the standard MIS blob, hash matches.
Where it stops
init_flash()now completes successfully (flash formatted, partition table written). It then fails inusb.send_init():So every generic command works, and the one device-specific payload,
init_hardcodedfromblobs_9a, is rejected with04be. Which is roughly what you'd expect if the MOH part needs its own configuration blob.Questions
04be, or0304from get_flash_info?init_hardcodedpayload the Windows driver sends to this device. That's the one piece blocking further progress, and I can't produce it myself.init_hardcodedknown to be a fixed per-device constant, or is it derived from something at runtime? If it's a constant, a single capture would likely be enough to add ablobs_a2.py.I'd be happy to run any experiments on this hardware and report back with my findings!