[Google Pixel 6] DropSequence:
So i have a Pixel 6 (not the pro). I love it, despite it being a bit buggy at times. My girlfriend loves it too so she also got one. Her screen got damaged and we took it to a local repair place. They ordered the part (took about 5 days to come in) and the repair took about an hour. The repair seems to be of decent quality work. Then we realized that the fingerprint sensor was not being detected and the option to use fingerprints was no longer available in the settings. A little bit of research and i found that this is a common problem which google has failed to provide any kind of solution for.

I read through googles bug report page found here ( https://issuetracker.google.com/issues/218761008?pli=1 ) as well as a couple other pages on google, reddit, etc. I am creating this thread because i am fairly certain that a solution to this problem can be engineered by the community but personally lack the skills required to accomplish this single handedly...

So...

The issue is that the fingerprint sensor needs to be calibrated after being replaced using the official tool found here ( https://pixelrepair.withgoogle.com/udfps )

There are two ways to connect to your phone when you run this tool. Using fastboot (via "adb reboot bootloader) or fastbootd (via "adb reboot fastboot:)

When attempting to run the tool via fastboot the tool fails at the download step saying "Couldn't find the unique calibration software for this device"

when attempting to run the tool via fastbootd it fails at the installation step saying "Couldn’t install the software" (seemingly having successfully downloaded the tool but being unable to install it in fastbootd)

Certain posts on the google bug report page have claimed success by running the tool on different firmware builds. I have tried flashing the oldest 12.0 build, the current 12.1 build, and the beta 13 builds as suggested by various reports to no avail.

However, when i run this tool on my own device which has the factory original screen, it runs and completes flawlessly. This leads me to believe that reports saying the issue is with the build quality of the screen replacements being sources by boutique repair shops causing the tool to not recognize the screen may have some merit.

Now...

At the bug report page I linked to above, post #20, it shows a user who inspected the url for the command which is failing with a 404 code. I assume this is what happens when running via fastboot and it fails to download the tool...

This is where i lack the skills needed to implement a solution. Im pretty sure that there is a way to redirect the failing url to a destination of ones choosing. If so, it should be possible to extract the url used by the tool when it succeeds on the downloading step (either via the fastbootd method or when used on a device that has not been repaired). The URL could then be used as a redirection target for the tool, or possibly downloaded (or extracted from the browser cache) and run independently.

I dont know if any of my ideas here are viable, but there seems to be a disturbingly large number of users who would benefit from a solution.

Any ideas?

PS: please forgive any formatting failures on my part