python-validity icon indicating copy to clipboard operation
python-validity copied to clipboard
verified publisher icon uunicorn

T480s(06cb:009a), factory reset failed.

Open phtty opened this issue 3 months ago • 4 comments

I followed the instructions in the manual: after running yay -S python-validity, I entered sudo fprintd-enroll and saw list_devices failed:. Then I attempted a factory reset. When I ran the command sudo python3 /usr/share/python-validity/playground/factory-reset.py, it either returned a timeout or error code 0401, making it completely non-functional. Even resetting the fingerprint settings in BIOS didn't help. Here is the error message:

Traceback (most recent call last): File "/usr/share/python-validity/playground/factory-reset.py", line 6, in factory_reset() ~~~~~~~~~~~~~^^ File "/usr/lib/python3.13/site-packages/validitysensor/sensor.py", line 86, in factory_reset assert_status(usb.cmd(reset_blob)) ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.13/site-packages/validitysensor/util.py", line 12, in assert_status raise Exception('Failed: %04x' % s) Exception: Failed: 0401

Or such a situation may occur:

Traceback (most recent call last): File "/usr/share/python-validity/playground/factory-reset.py", line 6, in factory_reset() ~~~~~~~~~~~~~^^ File "/usr/lib/python3.13/site-packages/validitysensor/sensor.py", line 86, in factory_reset assert_status(usb.cmd(reset_blob)) ~~~~~~~^^^^^^^^^^^^ File "/usr/lib/python3.13/site-packages/validitysensor/usb.py", line 105, in cmd resp = self.dev.read(129, 100 * 1024) File "/usr/lib/python3.13/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.13/site-packages/usb/backend/libusb1.py", line 850, in bulk_read return self.__read(self.lib.libusb_bulk_transfer, ~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ dev_handle, ^^^^^^^^^^^ ...<2 lines>... buff, ^^^^^ timeout) ^^^^^^^^ File "/usr/lib/python3.13/site-packages/usb/backend/libusb1.py", line 958, in __read _check(retval) ~~~~~~^^^^^^^^ File "/usr/lib/python3.13/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

phtty avatar Oct 08 '25 12:10 phtty

same issue. which is weird because it was working before I did a reinstall. Only difference was switching from yay to paru.

EDIT(SOLVED): I have solved my issue. I believe I was removing my finger from the reader too quickly. I also was not using sudo command when running fprintd-enroll. These both solved my issue.

connorblevins avatar Oct 10 '25 06:10 connorblevins

同样的问题。这很奇怪，因为在我重新安装之前它就已经工作了。唯一的区别是从 yay 切换到 paru。

Unfortunately, I have never succeeded from the very beginning. I once saw a method that was said to work, but it was too complicated, and I had no interest in trying it. Some people say that in a Windows and Linux dual-boot setup, you can install the fingerprint driver in Windows and register a fingerprint, then delete that fingerprint in Linux and re-register it to succeed.

phtty avatar Oct 10 '25 14:10 phtty

Same model and same issue

matteodev8 avatar Nov 02 '25 14:11 matteodev8

Exactly the same issue here. Worked previously but fingerprints weren't recognised after enrollment. Reset the reader in BIOS and now I get this. Will try with an older snapshot to see if it's software related or somehow the reader is now broken.

EDIT After some investigating with old snapshots, I managed to get it working again doing the following:

  1. Obtained the firmware with sudo validity-sensors-firmware
  2. Copied the firmware from /var/run/python-validity/6_07f_lenovo_mis_qm.xpfwext to somewhere safe (home directory in my case).
  3. Uninstalled python-validity with yay -R python-validity
  4. Rebooted with sudo systemctl reboot
  5. Recreated the folder for the firmware with sudo mkdir /var/run/python-validity.
  6. Copied the firmware to that folder with sudo cp $HOME/6_07f_lenovo_mis_qm.xpfwext /var/run/python-validity.
  7. Reinstalled with yay -S python-validity.

There seems to be some error with the flow of downloading the firmware and also re-initialising the device once the firmware upload or the unit start has failed (the reader seems to just throw those exceptions after that). Also disabling the unit somehow didn't work as it was re-enabled on reboot (?). So only the above procedure worked for me.

I don't have the time to pinpoint the exact problem but I hope the info above helps. Could be an issue with the AUR package and not python-validity maybe..?

preciserobot avatar Nov 14 '25 17:11 preciserobot

Hey, I can confirm that @phtty suggestion works. If you factory reset your fingerprint reader in the BIOS or python util you need to first use windows to register one fingerprint, after that sudo fprintd-enroll works like a charm.

For my use case I don't dual boot windows/linux so I've inserted a windows 11 live usb stick (always good to have one at hand)

After registering the first fingerprint it's also required to remove it using the fingerprint manager, otherwise the verify will never succeed:

https://github.com/uunicorn/python-validity/issues/189#issuecomment-2294960949

jaecktec avatar Dec 27 '25 12:12 jaecktec