Have you found any solution or do yo know another rom that works well in redmi 5? ThanksI have the same problem in Redmi 5 (rosy)
Can you explain how to do it ? Would be glad to help.Send us a log...
I fixed it this way but everyone ignored it
https://xiaomi.eu/community/threads/how-to-solve-fingerprint-error-bug-in-8-11-15-rom.47752/
Send us a log...
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 ?I fixed it this way but everyone ignored it
https://xiaomi.eu/community/threads/how-to-solve-fingerprint-error-bug-in-8-11-15-rom.47752/
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.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 ?
Thanks for your recommendation! How recovery and fingerprints are connected? I'll try tonight and update this post if it worksDid you tried to update your TWRP?
https://xiaomi.eu/community/threads...ashing-8-11-15-no-mount-data-partition.47704/
I downgraded to 8.11.8_v10-7.1 and got "encryption was interrupted and can't complete..." at the boot of the device.Yes, it always work for me
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.
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=ubject_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=ubject_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
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 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.
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation