Looking for some guru help here...
My S5 has fallen to the fingerprint reader bug... I was able to get in and switch to a pin unlock, but I put off having the phone RMA'ed for convenience reasons... but now I've stumbled onto something...
Used Safestrap to take a nandroid backup of /data and then did a factory reset. This caused the fingerprint functionality to revert to the unprogrammed factory state where I was able to program new fingerprints successfully. After this, I restored the nandroid and it was back to its broken state. Conclusion: the hardware is fine and the problem is somewhere in the /data partition.
I found a DB in /data/data/com.samsung.android.fingerprint.service/databases/fingerprint.db, which contains one row for each fingerprint, but obviously does not contain the actual fingerprint data as there are no BLOB type data in it. Also, clearing that DB alone doesn't help. Any other ideas where I might look?
My S5 has fallen to the fingerprint reader bug... I was able to get in and switch to a pin unlock, but I put off having the phone RMA'ed for convenience reasons... but now I've stumbled onto something...
Used Safestrap to take a nandroid backup of /data and then did a factory reset. This caused the fingerprint functionality to revert to the unprogrammed factory state where I was able to program new fingerprints successfully. After this, I restored the nandroid and it was back to its broken state. Conclusion: the hardware is fine and the problem is somewhere in the /data partition.
I found a DB in /data/data/com.samsung.android.fingerprint.service/databases/fingerprint.db, which contains one row for each fingerprint, but obviously does not contain the actual fingerprint data as there are no BLOB type data in it. Also, clearing that DB alone doesn't help. Any other ideas where I might look?
Last edited:
