Normally for the finger to be registered, one finger is scanned like 7 times....but mine scan the finger 2 times or 3 and then refuses to continue! I brought this phone in April and except known previous issues, i have almost used my fingerprint fairly good! I tried MiFlash with clean all, custom rom like RR all latest....still the same....2 scans and then the process could not be completed...!
Plz help....
Addymore said:
Normally for the finger to be registered, one finger is scanned like 7 times....but mine scan the finger 2 times or 3 and then refuses to continue! I brought this phone in April and except known previous issues, i have almost used my fingerprint fairly good! I tried MiFlash with clean all, custom rom like RR all latest....still the same....2 scans and then the process could not be completed...!
Plz help....
Click to expand...
Click to collapse
I deleted persist contents in twrp zcx and the fingerprint scanner worked again....! Now everything is ok....
Addymore said:
I deleted persist contents in twrp zcx and the fingerprint scanner worked again....! Now everything is ok....
Click to expand...
Click to collapse
How did you do the procedure?
Aldeirto said:
How did you do the procedure?
Click to expand...
Click to collapse
Install twrp zcx, mount persist then delete its contents...using file explorer in advanced tab
Related
Hello everyone!
So my problem started a few weeks ago when i flashed ABC Rom on my MiMix2, the proximity sensor, in calls, started to not work after a time, but it was a gradual process, until it didn't work at all. So a few days ago i decided to try and solve the problem. I've read in different places that it could be the persist partition, that holds the drivers for the sensor.
I have tried flashing the persist.img with fastboot from the original xiaomi site, but it kept telling me the partition is write protected. Tried with adb but then i couldn't mount the partition. In the end i ended up reflashing the original image with MIUI Flashing Tool, modifying the image to flash the persist image, with no positive results, except i could mount the partition again. I then looked in the persist.img file to find out it is empty, all of them that i could find are almost empty(some empty folders).
I fount a thread on XDA with some sensor files for my phone that i had to copy in my root/sensors directory, so i did and nothing changed.
The weird thing is that after all of this, when i enter the calibration app that that MIUI has and hold my hand on the sensor sometimes it detects my hand.
Sooo.... after all of this is my problem a software one or a hardware one (if its a hardware one, its a strage one, because the sensor works but its just weak).
Can anyone help me with some answers please. Thanks and sorry for the long post.
bzadi said:
Hello everyone!
So my problem started a few weeks ago when i flashed ABC Rom on my MiMix2, the proximity sensor, in calls, started to not work after a time, but it was a gradual process, until it didn't work at all. So a few days ago i decided to try and solve the problem. I've read in different places that it could be the persist partition, that holds the drivers for the sensor.
I have tried flashing the persist.img with fastboot from the original xiaomi site, but it kept telling me the partition is write protected. Tried with adb but then i couldn't mount the partition. In the end i ended up reflashing the original image with MIUI Flashing Tool, modifying the image to flash the persist image, with no positive results, except i could mount the partition again. I then looked in the persist.img file to find out it is empty, all of them that i could find are almost empty(some empty folders).
I fount a thread on XDA with some sensor files for my phone that i had to copy in my root/sensors directory, so i did and nothing changed.
The weird thing is that after all of this, when i enter the calibration app that that MIUI has and hold my hand on the sensor sometimes it detects my hand.
Sooo.... after all of this is my problem a software one or a hardware one (if its a hardware one, its a strage one, because the sensor works but its just weak).
Can anyone help me with some answers please. Thanks and sorry for the long post.
Click to expand...
Click to collapse
Probably the custom ROM causing the issue
This is what i assumed at first, but i flashed the original xiaomi image with their tool, and still the same behavior. This problem now persists on all the roms i flash.
I've got the exact same problem, now proximity sensor doesn't work at all
bzadi said:
This is what i assumed at first, but i flashed the original xiaomi image with their tool, and still the same behavior. This problem now persists on all the roms i flash.
Click to expand...
Click to collapse
Nvjoel said:
I've got the exact same problem, now proximity sensor doesn't work at all
Click to expand...
Click to collapse
Do you have any kind of screen protection?
XDRdaniel said:
Do you have any kind of screen protection?
Click to expand...
Click to collapse
Nope, no screen protector, no case.
XDRdaniel said:
Do you have any kind of screen protection?
Click to expand...
Click to collapse
No case and no screen protection.
let me preface this by saying
My Pixel3XL is the first phone i have purchased that came with Pie out of the box
my oneplus 6 came with oreo.
I had decrpyted my OP6 successfully as soon as i rooted it with TWRP (edited the fstab and removed force encrypt to encryptable) formatted data, and flashed magisk.
after that it worked fine with PIN and Finger prints.
i attempted to do the same with my Pixel 3XL however after i have decrypted i run into an issue relating to PIN/Lockscreen
firstly, the option to add a fingerprint in settings has disappeared - whats up with that?
also once i set a pin successfully (and works in unlocking the lock screen even though after i unlock the LS a toast notification comes up and says "wrong pin") i can not change it - if i attempt to change it, it comes back with "wrong pin" but the same pin unlocks my screen.
can anyone shed some light on how i can get these issues fixed?
i believe it may have to do with android 9 as i have heard of reports with the oneplus 6T having the same issue.
(p.s sorry if this is in the wrong forum)
No answer, did you? I'm going nuts here too! Exact same preamble (experience), currently stuck at the exact same spot! 6T here!
Why would you want to use an unencrypted device? Because of the performance gains? I guess those are merely negligible.
alpinista82 said:
Why would you want to use an unencrypted device? Because of the performance gains? I guess those are merely negligible.
Click to expand...
Click to collapse
I have no problem telling you why, but is your presence here to make me desist? Because what I'm looking for is knowledge.
Having said that, i have no issues with performance, i have a mate 10 pro and a 6T. It's just that it's a hassle sometimes wanting to flash this or that and coming to find out that for whatever reason, not interested in those yet, i may turn out to be encrypted in my recovery, and I'm effed if I'm away from an otg or i misplace it.
Sent from my Mate 10 Pro using XDA Labs
So, in short: Android 9 is not meant to be run from unencrypted data partition.
alpinista82 said:
So, in short: Android 9 is not meant to be run from unencrypted data partition.
Click to expand...
Click to collapse
not if you want a fingerprint or a PIN working
for some reason they break when you run decrypted
unsure if its android 9 or the pixel 3xl that causes this
but i had no issue decrypting my OP6 on Oreo
alpinista82 said:
So, in short: Android 9 is not meant to be run from unencrypted data partition.
Click to expand...
Click to collapse
Ok, i believe you missed how i run decrypted on my mate 10 pro on pie
Sent from my Mate 10 Pro using XDA Labs
culiacanazo said:
Ok, i believe you missed how i run decrypted on my mate 10 pro on pie
Sent from my Mate 10 Pro using XDA Labs
Click to expand...
Click to collapse
but still no FP or PIN ?
i found that my op6 came with Oreo upgraded to PIE was able to decrypt without issues
but my 6T that came with PIE had issues (no fp or pin recognized)
virtyx said:
but still no FP or PIN ?
i found that my op6 came with Oreo upgraded to PIE was able to decrypt without issues
but my 6T that came with PIE had issues (no fp or pin recognized)
Click to expand...
Click to collapse
Without issues! With fp, face unlock, pattern working!
Maybe it's because it too came with Oreo and upgraded to pie, at this point is the best guess!
culiacanazo said:
Without issues! With fp, face unlock, pattern working!
Maybe it's because it too came with Oreo and upgraded to pie, at this point is the best guess!
Click to expand...
Click to collapse
but my pixel 3xl doesnt work with fp or pin if i decrypt
virtyx said:
but my pixel 3xl doesnt work with fp or pin if i decrypt
Click to expand...
Click to collapse
do you flash one of those decrypting zips after wiping? not sure if its related, but i do...
didnt that one come with pie out of the box?
culiacanazo said:
do you flash one of those decrypting zips after wiping? not sure if its related, but i do...
didnt that one come with pie out of the box?
Click to expand...
Click to collapse
yes came with Pie
doesnt work
fp and face and pin dont work
virtyx said:
yes came with Pie
doesnt work
fp and face and pin dont work
Click to expand...
Click to collapse
That might be why. See, i don't develop even my plan for the day, so what i (think i) know, is mostly thru researching, trial and error, and once in a blue moon, asking.
I'll say it again, that might be why!
Also, and in my other pie-born device, it's possible to set and use face unlock, but it's a hassle since after a reboot, you need the "actual" credentials, thus warranting a trip to recovery to anhiliate your friends-turned-foes in /data/system (hoping to all the Android deities you don't somehow reencrypt on your way there.
Also, Google Pay will bug and impede you in spite of the face, as the system will present itself as having no screen lock, conveniently annoyingly, for those purposes only, while giving you the no-password-no-access treatment!
Some days ago I bricked my phone, but made it work again with the EDL method. Everything works again, apart from the Fingerprint sensor. I'm quite sure that I assembled it correctly, because it's clearly recognized(also when I use the swipe on fingerprint sensor to see notifications feature). It's recognized until the last bar at the registration, but then it always fails. I've tried several roms(stock and custom), but always the same.
Any suggestions for a fix?
Thanks in advance
Veran125 said:
Some days ago I bricked my phone, but made it work again with the EDL method. Everything works again, apart from the Fingerprint sensor. I'm quite sure that I assembled it correctly, because it's clearly recognized(also when I use the swipe on fingerprint sensor to see notifications feature). It's recognized until the last bar at the registration, but then it always fails. I've tried several roms(stock and custom), but always the same.
Any suggestions for a fix?
Thanks in advance
Click to expand...
Click to collapse
Have the same problem. It has something to do with your persist partition. Perhaps you saved it via twrp? I had a save but don´t find it. **** happens.
I erased everything and flashed every fastboot rom via edl or normally. My fingerprint is broken!
Yeah, I used TWRP back in time. But I start to think that's it's a hardware issue. It happened after I had to open my phone to get into EDL mode.
Veran125 said:
Yeah, I used TWRP back in time. But I start to think that's it's a hardware issue. It happened after I had to open my phone to get into EDL mode.
Click to expand...
Click to collapse
In my case it´s a software issue... I used to open my phone, but when my fp broke when I was trying to fix goodix for our new bootleggers rom. I did the fix from official telegram group and a after that, root explorer could mount persist (this was the issue, why fp couldn´t be safed in gsi´s using a pie vendor), but the fp still couldn´t be safed. That means, now it could connect data and changed sth. badly...
I had the same problem. But I had a backup of the twrp sections of the persist and efs. I restored these partitions and flashed 9640 miflash. now the fingerprint works fine
So as long as my fingerprint sensor is recognized, it's most likely not a hardware issue? Furthermore did I unbrick my phone by flashing with EDL mode. Isn't everything formatted then? But I also downgraded to Oreo after that, could that be the reason?
Veran125 said:
But I also downgraded to Oreo after that, could that be the reason?
Click to expand...
Click to collapse
No
My fingerprint recognition works now with rr gsi. I will try wheather the problem is solved on stock too. I just went back too rr gsi, becouse I have a fully working data partition for it and luckily my fp started to work again. Idk what´s the problem.
Veran125 said:
Some days ago I bricked my phone, but made it work again with the EDL method. Everything works again, apart from the Fingerprint sensor. I'm quite sure that I assembled it correctly, because it's clearly recognized(also when I use the swipe on fingerprint sensor to see notifications feature). It's recognized until the last bar at the registration, but then it always fails. I've tried several roms(stock and custom), but always the same.
Any suggestions for a fix?
Thanks in advance
Click to expand...
Click to collapse
Thanks to @eremitein we have a flashable zip that restores the persist image. Just flash via twrp - works for me!
https://forum.xda-developers.com/showpost.php?p=79368367&postcount=25
Thanks a lot, it really works.
Good that I wrote here before I reopened my phone.
Has anyone else had an issue with finger print scanner not working on stock 10.0.8.0?
Mine works well just after setting up fingerprint, but then deteriorates and I have to enter PIN. Deleting fp and setting up again and works for a day or two. Just wonder if fingerprint fix for 10.0.7.0 will fix?
Thanks to @eremitein we have a flashable zip that restores the persist image. Just flash via twrp -
https://forum.xda-developers.com/sho...7&postcount=25
bonzoe said:
Mine works well just after setting up fingerprint, but then deteriorates and I have to enter PIN. Deleting fp and setting up again and works for a day or two. Just wonder if fingerprint fix for 10.0.7.0 will fix?
Thanks to @eremitein we have a flashable zip that restores the persist image. Just flash via twrp -
https://forum.xda-developers.com/sho...7&postcount=25
Click to expand...
Click to collapse
I ended up finding it. Thank you. I appreciate the response.
Did you apply the fix and did it cure the fault?
bonzoe said:
Did you apply the fix and did it cure the fault?
Click to expand...
Click to collapse
It did. I should state what my issue was. I couldn't register more than one finger print and then woke up one morning and it just didn't respond at all. It was weird. But after applying the fix it worked and could register multiple finger prints.
i was able to install the latest official havoc os and i installed gaps, but i didn't figure out how to register my fingerprint, does anybody succsesfull try it?
thank you
Wow, u are amazing, first u cant install gapps and now u cant register ur finger print lol, use telegram group please or post your noobs cuestions in the right section please
mhm which is the right section?
For fingerprint read faq, point 2 and 3.
LazyT said:
For fingerprint read faq, point 2 and 3.
Click to expand...
Click to collapse
thank you but it won't work
the persist folder didn't contain a folder called data, i created it, but still not working, them i installed the zipfile, same error
I found a solution, i flashed the Stock Rom 9.6.11.0, than the havoc-os 2.0 from 27.10.18, finished Fingerprint Registration and flashed havoc os 2.7 from 12.07.19 without wiping, after flashing of the Image to system Partition, restarted the Phone and voila, everithing is now fine?