Saturday, 19 December 2015

Fingerprint hardware unavailable? Enrollment didn't work?



Recipe:
  1. TWRP 2.8.7.2

  2. TWO Nexus 6Ps on 6.0.1

  3. One N6P systemless rooted

  4. Official Android SDK (fastboot)


So I got a replacement N6P from Fi as I noticed some slight bending on my original, and I was working on moving my data over using TWRP so I could keep all my app data, etc. When I backed up my original 6P, I forgot to remove screen and boot security, so when I flashed on to my new 6P, I was locked out (as expected, known bug). I tried this fix to get in to my system, and it worked! I was able to log in. However, I noticed that my old fingerprints were still enrolled and I wanted to start those fresh, so I tried to remove them. When I selected "Delete" for each enrolled fingerprint, nothing happened. This was the first clue. I then tried to enroll new fingerprints and got the following message:


Code:


Enrollment was not completed
Fingerprint enrollment didn't work. Try again or use a different finger.


The other odd thing is that on the lockscreen, I was getting a red text error message that read something like "Fingerprint hardware not available."

So I figured something got messed up security wise from the fix I tried after flashing a locked nandoird. I then went back and made a new nandroid backup (boot, system, data) on my old phone making sure that all security was turned off. Same thing!

Wondering if the hardware did actually get messed up somehow, I flashed back to official stock 6.0.1 from Google. Fingerprinting then started working!

So nothing I have done since then has made any difference when trying to restore my userdata from my old phone. I've tried wiping cache/dalvik, and removing the locksettings.db file, but these didn't change anything either.

Has anyone had this issue before? It seems really bizarre to me. I'm probably going to end up flashing stock and restoring userdata via TB, but that is a headache compared to nandroid so if possible I'd like to get this to work.

Download from this link

No comments:

Post a Comment