ok so, my phone's fingerprint sensor will just show "fingerprint sensor calibration needed" when trying to register a fingerprint. I've tried to nand erase and repartition, clean flash install, magisk install, hard reset etc but it wont work. It passes all the fingerprint tests fine.
I didn't buy or change any parts from the phone, it's still oem
what can i do to solve this? thanks
applesucksLmao said:
ok so, my phone's fingerprint sensor will just show "fingerprint sensor calibration needed" when trying to register a fingerprint. I've tried to nand erase and repartition, clean flash install, magisk install, hard reset etc but it wont work. It passes all the fingerprint tests fine.
I didn't buy or change any parts from the phone, it's still oem
what can i do to solve this? thanks
Click to expand...
Click to collapse
Hey, did you ever find out something?
I just got that problem too
weird. its funny how samsung killed my fingerprint all together. it died just by sitting over night. stock and Knox was intact. its permanently gone.fw downgrade doesn't help.
Captain_cookie_200 said:
weird. its funny how samsung killed my fingerprint all together. it died just by sitting over night. stock and Knox was intact. its permanently gone.fw downgrade doesn't help.
Click to expand...
Click to collapse
I *think* it has something to actually do with the calibration. The problem is that the sensor calibration needs to be performed with some application/equipment that either doesn't exist or is exclusive to samsung service centers.
I suspect we're gonna need some hacky workaround like the IMEI thing, which BTW never got really fixed.
Mighty_Rearranger said:
I *think* it has something to actually do with the calibration. The problem is that the sensor calibration needs to be performed with some application/equipment that either doesn't exist or is exclusive to samsung service centers.
I suspect we're gonna need some hacky workaround like the IMEI thing, which BTW never got really fixed.
Click to expand...
Click to collapse
i see..
Related
I need an opinion on this one. I've looked for this problem but it seems not to be clear what is causing it. I have Wildfire S (EU) Marvel. The device is S-On but I unlocked the boot loader and installed CWM. I've already tried several ROMs but it doesn't help to solve the issue. The problem appears during making the call - the screen goes black when you put the phone next to head and after that doesn't want to wake up. The only thing that wakes it up is putting it next to strong light source so I think the light sensor is the one to blame. However automatic backlight seems to be working fine. I really hope that it is not hardware problem. Please give any suggestion to try solving this problem. I would even go for the option to shut down somehow the light sensor because restarting phone after each call is kind of annoying. Thank you in advance for any help you can provide. Sorry for such a long introduction.
anubius said:
I need an opinion on this one. I've looked for this problem but it seems not to be clear what is causing it. I have Wildfire S (EU) Marvel. The device is S-On but I unlocked the boot loader and installed CWM. I've already tried several ROMs but it doesn't help to solve the issue. The problem appears during making the call - the screen goes black when you put the phone next to head and after that doesn't want to wake up. The only thing that wakes it up is putting it next to strong light source so I think the light sensor is the one to blame. However automatic backlight seems to be working fine. I really hope that it is not hardware problem. Please give any suggestion to try solving this problem. I would even go for the option to shut down somehow the light sensor because restarting phone after each call is kind of annoying. Thank you in advance for any help you can provide. Sorry for such a long introduction.
Click to expand...
Click to collapse
long introduction is far better than a short one ...
did you install rom propperly (factory reset/cache clean/dalvik clean)?
did you try using any other dialer app just to check ?
Like this, or this
I think i have read about such problem somewhere, if i find it i will post you the link to it...
also here are some apps to check your proximity sensor :
ProxyLightTester i couldn't find it on market. (not tested)
Proximity Sensor Finder Market link. (tested) and it will report 'all or nothing'
b02 said:
long introduction is far better than a short one ...
did you install rom propperly (factory reset/cache clean/dalvik clean)?
did you try using any other dialer app just to check ?
Like this, or this
I think i have read about such problem somewhere, if i find it i will post you the link to it...
also here are some apps to check your proximity sensor :
ProxyLightTester i couldn't find it on market. (not tested)
Proximity Sensor Finder Market link. (tested) and it will report 'all or nothing'
Click to expand...
Click to collapse
Hi, Thanks a lot for suggestions. So it seems to me that proximity and light sensors work. I tried several software including the one you suggested and the proximity and light sensor respond ok. I also tried different dialer but it doesn't help. I have no idea what can it be. I am thinking to put the device back to the factory state and maybe install official ROM but I am not sure if this will solve the problem. Thank you again for helping. And your device never had this problem?
Never had that problem.. Try reflashing w/o any app2sd gapps and stuff, just clean new rom and try it..
Sent from my HTC Wildfire using xda premium
anubius said:
I am thinking to put the device back to the factory state and maybe install official ROM but I am not sure if this will solve the problem.
Click to expand...
Click to collapse
Before you do that try this build.prop file and see if it helps...Just remove the ".txt" and set your permissions same as the old build.prop file you renamed.
Tera Tike said:
Before you do that try this build.prop file and see if it helps...Just remove the ".txt" and set your permissions same as the old build.prop file you renamed.
Click to expand...
Click to collapse
Thank you guys for all the suggestions I followed your advices but the phone simply refuses to wake up after the call. I am trying to go back to factory default since this is my last hope. Really confused what is causing it.
Why is it when I set a fingerprint, I set a pattern for the mandatory backup security but when I try to unlock with fingerprint it asks for a pattern saying "Pattern required to enable fingerprint"?
As far as I know, as an extra security, a pattern/pin code is necessary when the phone is restarted/ switched on, once you chose to use the fingerprint scanner.
Howling Wolf said:
As far as I know, as an extra security, a pattern/pin code is necessary when the phone is restarted/ switched on, once you chose to use the fingerprint scanner.
Click to expand...
Click to collapse
It's every time I lock it
Sent from my HTC 10 using Tapatalk
Finally figured it out.
It happens when screen is locked by a 3rd party app, in my case I use nova double tap to lock screen.
Was wondering why (and forgot to mention) it seemed random.
Edit: for Nova users looking for a workaround, if you enable screen off by root access method it will use a secure lock and enable the fingerprint to unlock.
Heisenberg420 said:
Finally figured it out.
It happens when screen is locked by a 3rd party app, in my case I use nova double tap to lock screen.
Was wondering why (and forgot to mention) it seemed random.
Edit: for Nova users looking for a workaround, if you enable screen off by root access method it will use a secure lock and enable the fingerprint to unlock.
Click to expand...
Click to collapse
yeah a lot of screenapp does ask.... if you are on elementalx you could use button mapper which gives you the same functionality of double to sleep and more doesn't ask for patter/pin everytime you unlock
This started to happen to me after a bug crashed the phone and had to force restart it holding volume down + power. I only have the default launcher so I guess it's factory reset time for me
Heisenberg420 said:
Why is it when I set a fingerprint, I set a pattern for the mandatory backup security but when I try to unlock with fingerprint it asks for a pattern saying "Pattern required to enable fingerprint"?
Click to expand...
Click to collapse
For what it's worth, I had the same issue (until I found this thread) and it was caused by Action Laucher 3. The launcher was set as a Device Administrator and was granted permission to "Power screen off". Once I removed that permission my troubles were over.
Seems to me that it makes sense once you have a fingerprint setup, to require a pin as well. Why? Because what if the fingerprint reader stops working? You won't be able to login?!?!
Not sure until the poster above mentions a pattern is required. Normally it is a pin if you want. Then the PIN required upon restart option as well that is there.
Of course, if you are rooted, you can delete the system files that control/store that...but if not rooted with TWRP, you would have to try a master reset I would assume?!?!
IDK...guess I never thought of testing that out...haha
Guys, i hope it's ok if i conquer this thread for my question but i got serious issues here.
Got my 10 back from repair today and restored my backup.
But dumb me it seems as if i set a password/patern whatever and i can't remember it.
So after the first restart i can't unlock my phone cause it's asking for the code (and won't let unlock only with fingerprint) and i can't remember.
All combination that i would have used are wrong and now i got a working phone back again (after almost 2 month of repairing) and can't unlock it.
Is there any way of bypassing/ignoring the restart password or is it possible to only unlock it again with the fingerprint that is stored?
As i don't know what i should do if i don't get my phone unlocked
bmwbasti said:
Guys, i hope it's ok if i conquer this thread for my question but i got serious issues here.
Got my 10 back from repair today and restored my backup.
But dumb me it seems as if i set a password/patern whatever and i can't remember it.
So after the first restart i can't unlock my phone cause it's asking for the code (and won't let unlock only with fingerprint) and i can't remember.
All combination that i would have used are wrong and now i got a working phone back again (after almost 2 month of repairing) and can't unlock it.
Is there any way of bypassing/ignoring the restart password or is it possible to only unlock it again with the fingerprint that is stored?
As i don't know what i should do if i don't get my phone unlocked
Click to expand...
Click to collapse
Try a factory reset via Android Device Manager.
I don't know what Android Device Manager is but I could do the reset in TWRP too. It's about not losing all of my data or a possibility to get that device unlocked without the code. It would be no problem as my fingerprint is stored. Damn, I could just hit my head against a wall or alternatively just cry like a baby. I never forgot a password or code in my whole life and by now it happens
bmwbasti said:
I don't know what Android Device Manager is but I could do the reset in TWRP too. It's about not losing all of my data or a possibility to get that device unlocked without the code. It would be no problem as my fingerprint is stored. Damn, I could just hit my head against a wall or alternatively just cry like a baby. I never forgot a password or code in my whole life and by now it happens
Click to expand...
Click to collapse
Log in here https://www.google.com/android/devicemanager
Using the account your phone is used with.
Thx, but there I only have the options of letting the phone ring, lock it down or wiping it. As stated above I could do that easily in recovery, too.
I'm looking for a way of not having to wipe the phone (if there is one....)
bmwbasti said:
Thx, but there I only have the options of letting the phone ring, lock it down or wiping it. As stated above I could do that easily in recovery, too.
I'm looking for a way of not having to wipe the phone (if there is one....)
Click to expand...
Click to collapse
To be honest, I don't think so. There were loopholes before, but they have been closed. :/
So doing a factory reset and restoring /data is the only way of getting back control of my phone again (without losing too much data)?
I think i will get rid of locking my phone with fingerprint again as there seems not ot be a failsafe mechanic for forgetting a (backup) mechanic
OK, so it seems that I have to throw that piece of aluminum against the wall. The code seems to interact with /data, because after restoring only /data I have to put in the forgotten password again.
bmwbasti said:
OK, so it seems that I have to throw that piece of aluminum against the wall. The code seems to interact with /data, because after restoring only /data I have to put in the forgotten password again.
Click to expand...
Click to collapse
I really suggest starting from zero, when you get everything set, then set a password.
Thanks for your advice, but it's not about starting from zero. I've already done this twice today
It's about at least being able to get (some of) the data of /data
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.
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.
Hi Everyone,
I recently had an issue with my phone that kept telling me my pin was incorrect when it wasn't. I did a search on the oneplus forums and was told to delete locksettings.db from /Data/System.
I was able to get back on my phone but now the option to unlock with fingerprint is gone. If I go into security it still shows my fingerprint set up but it says enrollment not complete and it just exits.
I tried reflashing the rom I am on and still have the same issues.
Any other solutions besides factory reset?
jj71787 said:
Hi Everyone,
I recently had an issue with my phone that kept telling me my pin was incorrect when it wasn't. I did a search on the oneplus forums and was told to delete locksettings.db from /Data/System.
I was able to get back on my phone but now the option to unlock with fingerprint is gone. If I go into security it still shows my fingerprint set up but it says enrollment not complete and it just exits.
I tried reflashing the rom I am on and still have the same issues.
Any other solutions besides factory reset?
Click to expand...
Click to collapse
Try clean flashing.
Flash firmware 5.0.8, this should solve your problem.
I was able to fix it by flashing a fingerprint script
jj71787 said:
I was able to fix it by flashing a fingerprint script
Click to expand...
Click to collapse
Unfortunately, I encountered the same problem. Could you give a link to this script?
SKrai said:
Unfortunately, I encountered the same problem. Could you give a link to this script?
Click to expand...
Click to collapse
Sure. Just flash in recovery and then set up new fingerprints