New REDMI 5 ROM, fingerprint does not work


Sep 19, 2018
3
0
13
#1
I installed 3 diferent xiaomi.eu roms, weekely and stable, and fingerprint does not work. At start allows you to save a fingerprint but when you are finishing, it gives a mistake.
 
Mar 17, 2019
10
1
5
#5
Hello there same problem here! My previously saved fingerprint were working but it was impossible to add new ones. So I decided to format my data, with the hope that the problem will be fixed with a fresh installation, but the problem is still there and now I I don't even have my previously added fingerprint.

Here is what I tried, with no luck.

-flash the rom again
-delete cache and dalvik cache from recovery
-deleted .key files and lockscreen.db etc... In data/system
-format data

After each step, I was trying to add a fingerprint, the process seemed to be working: it asked to move slightly the finger, then the animation of the fingerprint getting more and more precise is showing after each time I put my finger on the sensor, but at the end it goes back to the previous page with the error "could'nt add fingerprint,try again"

It seems that some people had this issue on miui9 https://en.miui.com/thread-1306988-1-1.html

And were able to fix it by going in the developer mode and turning 'memory optimisation' to high and disabling "dont keep activities"
But in my case, don't keep activities was already disabled and there is no 'memory optimisation' in miui 10...

If anyone have an idea on how to fix it... I was thinking to flash a xiaomi.eu miui 9 ROM add the fingerprints and then come back to miui 10 but It will be kinda long and I'm not sure it will work.
Any answer will be appreciated.
 
Likes: agerlanda

Igor Eisberg

Patch/Mod Developer
Staff member
Oct 6, 2016
1,451
1,101
297
#10
So by downgrading and updating the rom, just after and without wiping it worked for you? Could-it means that some files are missing in the newest updates ?
The whole system and vendor partitions are fully replaced with each update, so this is not possible. No idea why the fingerprint on that device gives issues, but since we don't have the device, we can't look into it. Even the only log that was sent to us was too vague to give any useful information.
 
Mar 26, 2018
24
3
15
#11
The whole system and vendor partitions are fully replaced with each update, so this is not possible. No idea why the fingerprint on that device gives issues, but since we don't have the device, we can't look into it. Even the only log that was sent to us was too vague to give any useful information.
System, vendor are replaced, but data remains because don't wipe anything (data, cache, davik cache).
If now I wipe the data, will not be able to add fingerprints.
 
Mar 17, 2019
10
1
5
#14
Last edited:

Igor Eisberg

Patch/Mod Developer
Staff member
Oct 6, 2016
1,451
1,101
297
#18
Go to the screen where it tells you to place your finger on the fingerprint sensor.
Write "adb logcat -c". When it's done, write "adb logcat > log.txt" and continue with the fingerprint registration until it fails.
Immediately when it fails, press Ctrl + C to stop the logging. The log file shouldn't be too large like that.
 
Likes: Pomman2
Mar 17, 2019
10
1
5
#19
Go to the screen where it tells you to place your finger on the fingerprint sensor.
Write "adb logcat -c". When it's done, write "adb logcat > log.txt" and continue with the fingerprint registration until it fails.
Immediately when it fails, press Ctrl + C to stop the logging. The log file shouldn't be too large like that.
Did what you asked ! Here is the file: https://www.dropbox.com/s/vqsq4ial9qr1sav/Log.txt?dl=0

Maybe the answer is somewhere here:
03-21 21:32:10.479 847 1300 D android.hardware.biometrics.fingerprint@2.1-service: onAcquired(0)
03-21 21:32:10.479 847 1300 I [GF_HAL][gf_hal_common]: [hal_milan_f_series_image_irq] image_quality=65
03-21 21:32:10.479 847 1300 I [GF_HAL][gf_hal_common]: [hal_milan_f_series_image_irq] valid_area=100
03-21 21:32:10.479 847 1300 I [GF_HAL][gf_hal_common]: [hal_milan_f_series_image_irq] key_point_num=170
03-21 21:32:10.479 847 1300 I [GF_HAL][gf_hal_common]: [hal_milan_f_series_image_irq] increase_rate=17
03-21 21:32:10.479 847 1300 I [GF_HAL][gf_hal_common]: [hal_milan_f_series_image_irq] overlay=64
03-21 21:32:10.479 847 1300 I [GF_HAL][gf_hal_common]: [hal_milan_f_series_image_irq] get_raw_data_time=40ms
03-21 21:32:10.479 847 1300 I [GF_HAL][gf_hal_common]: [hal_milan_f_series_image_irq] preprocess_time=14ms
03-21 21:32:10.479 847 1300 I [GF_HAL][gf_hal_common]: [hal_milan_f_series_image_irq] get_feature_time=31ms
03-21 21:32:10.479 847 1300 I [GF_HAL][gf_hal_common]: [hal_milan_f_series_image_irq] enroll_time=29ms
03-21 21:32:10.479 847 1300 I [GF_HAL][gf_hal_common]: [hal_milan_f_series_image_irq] total time=158ms
03-21 21:32:10.479 847 1300 D [gf_ca_entry]: [gx_ta_send_modified_cmd_req] begin token 118, cmd_id=1012
03-21 21:32:10.482 471 471 W qseecomd: type=1400 audit(0.0:41857): avc: denied { write } for name="fpdata" dev="mmcblk0p49" ino=1479870 scontext=u:r:tee:s0 tcontext=u:eek:bject_r:system_data_file:s0 tclass=dir permissive=0
03-21 21:32:10.492 471 471 W qseecomd: type=1400 audit(0.0:41858): avc: denied { write } for name="fpdata" dev="mmcblk0p49" ino=1479870 scontext=u:r:tee:s0 tcontext=u:eek:bject_r:system_data_file:s0 tclass=dir permissive=0
03-21 21:32:10.503 847 1300 D [gf_ca_entry]: [gx_ta_send_modified_cmd_req] end
03-21 21:32:10.503 847 1300 D [gf_ca_entry]: [gf_ca_invoke_command] gx_ta_send_modified_cmd_req success
03-21 21:32:10.503 847 1300 E [gf_ca_entry]: [gf_ca_invoke_command] ta execution failed, errno=1035
03-21 21:32:10.503 847 1300 E [GF_HAL][gf_hal_milan_f_series]: [hal_milan_f_series_invoke_command] exit. err=GF_ERROR_WRITE_SECURE_OBJECT_FAILED, errno=1035
03-21 21:32:10.503 847 1300 E [GF_HAL][gf_hal_common]: [gf_hal_invoke_command] exit. err=GF_ERROR_WRITE_SECURE_OBJECT_FAILED, errno=1035
03-21 21:32:10.504 847 1300 E [GF_HAL][gf_hal_common]: [gf_hal_save] exit. err=GF_ERROR_WRITE_SECURE_OBJECT_FAILED, errno=1035
03-21 21:32:10.504 847 1300 D android.hardware.biometrics.fingerprint@2.1-service: onError(4)
03-21 21:32:10.504 847 1300 E [GF_HAL][gf_hal_milan_f_series]: [hal_milan_f_series_image_irq] exit. err=GF_ERROR_WRITE_SECURE_OBJECT_FAILED, errno=1035
03-21 21:32:10.504 847 1300 E [GF_HAL][gf_hal_milan_f_series]: [hal_milan_f_series_irq] exit. err=GF_ERROR_WRITE_SECURE_OBJECT_FAILED, errno=1035
03-21 21:32:10.504 847 1300 E [GF_HAL][gf_hal]: [gf_hal_irq] exit. err=GF_ERROR_WRITE_SECURE_OBJECT_FAILED, errno=1035
 
Dec 3, 2016
187
78
40
#20
Thanks for your recommendation! How recovery and fingerprints are connected? I'll try tonight and update this post if it works

Edit: just tried, It nothing changed, still the same error ... "could'nt add fingerprint, try again"
You asked: how recovery and fingerprints are connected. After upgrading to Android version 8, known official TWRP could not mount data partition. You can check this in TWRP with trying to mount data partition. No writing access to data partition results in no adding fingerprint, because can't write.
 
Likes: Pomman2
Mar 17, 2019
10
1
5
#21
You asked: how recovery and fingerprints are connected. After upgrading to Android version 8, known official TWRP could not mount data partition. You can check this in TWRP with trying to mount data partition. No writing access to data partition results in no adding fingerprint, because can't write.
Thanks for the info, I see my data partition with a modded TWRP (the same one that is linked in your post). But still can't add my fingerprints :/