tavianator Did it again by copying the command, same result.

$ adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
here_some_id	device

$ adb reboot fastboot
$ fastboot oem udfps status
FAILED (remote: 'Unable to do OEM command Status(-8, EX_SERVICE_SPECIFIC): '1: Error Unknown OEM command'')
fastboot: error: Command failed
$ fastboot oem udfps get-cal-url
FAILED (remote: 'Unable to do OEM command Status(-8, EX_SERVICE_SPECIFIC): '1: Error Unknown OEM command'')
fastboot: error: Command failed
$ fastboot --version
fastboot version 35.0.2-android-tools
Installed as /usr/bin/fastboot
$ adb --version
Android Debug Bridge version 1.0.41
Version 35.0.2-android-tools
Installed as /usr/bin/adb
Running on Linux 6.13.6-hardened1-1-hardened (x86_64)

Meta:
Arch Linux fastboot version 35.0.2-android-tools
Bootloader version: ripcurrentpro-15.2-12817298

My fingerprint worked, after rebooting again it doesn't anymore.
The universally fix is not rebooting x amount of times.

    I got a pixel 9. Shutdown and/or restarted about 7-8 times and then it worked. I had to go into settings to re-activate the fingerprint unlock. good luck.

      tavianator Here you can see a reddit user had the same problem using an Pixel 8.

      thegustavo Maybe this has something to do with it. In this thread there is another Pixel 8 user.

      Would love to see the output of
      $adb logcat | grep -i -E "fingerprint|fpc"
      while the error happens

          So I lost the fingerprint reader after the update and after a dozen restarts I got it back.

          Well, I lost it again two more times since then so I booted into recovery mode both times and I rebooted the system from the recovery menu and both times the fingerprint reader was active again in just one try.

          Sooo, someone else give it a try and post if it works as well.

          PS: If you don't know how to get into recovery mode Google it don't ask here :)

          .

            rlw63ig0
            Nevermind, i rebooted and the fingerprint thingy disappeared again. Need a permanent fix asap. my passwords are too crazy long.

              jimmycinla I performed numerous reboots and power cycles with no effect. I confirm that booting from recovery worked fine at the first try.

                I'm also getting a glitch before first unlock after charging phone I'm not able to unlock phone without screen dimming and switching off while I'm still in the process of typing the password.

                I would need to reset the phone in order for me to login this has occurred a few times post latest release

                Well it just happened to me on my Pixel 9 Pro

                Glad I saw this thread, going to try the shutdown and reboot sequences now.
                I was using my main user account ( only one so far) however I did setup Private Spaces for a few apps that have problems with MullvadVPN in some locations.
                Read on here about memory leaks a little while ago IIRC so locked Private Spaces and then rebooted and that's when my fingerprint disappeared.

                I left my phone off for about 10 minutes and then it worked on the first try.

                Had to login to a few apps again and reset the Biometrics again. Rebooted again and seems OK.
                Just going to leave it for now.
                It happened just as I was heading out to go to bank, shopping... so needed to access the Private Spaces app right before and did not have time to research what was going on.
                It even reset Futo Keyboard, now all seems ok.

                r0bi this problem just happened again when upgrading to 2025031400. A full power cycle successfully fixed it again.

                  FWIW last update seems to have repaired the problem.

                    Updated to 2025031400, faced the issue after reboot and fixed after one power cycle.

                    GrapheneOS i have the fingerprint issue on my pixel 7. This is not exclusive to 9. Only a hard reboot brought it back.
                    You are repackaging Android and naming it GrapheneOS. You can't blame upstream for everything. You let this easy to repro issue past QA. If Ford rebadges a mazda caf and has an issue it is still on ford.
                    This fingerprint and not being able to take screenshots immediately until some kind of process wakes up (just says unable to save) are unacceptable.
                    Look how many releases there have been the past 1.5 months. Almost as many as in 6 months. Get your stuff together. We rely on you for a rock solid daily driver. I won't be donating more until I see improvements.