Hi,
When I try to register my fingerprint it says continuously fingerprint hardware not available,
Now, I know that my fingerprint sensor is working beacause it was woking ok but I wanted to add more fingerprints to make it more accurate, and when I tried that it kept saying that hardware not... So I deleted all the exisiting fingerprint and now I cant register any.
Did wipe cache partition and tried to clear data from com.ztefingerprints.service but it's greyed out.
I want to avoid factory reset, or clearing the phone data.
Any solution?
Edit: stock b32
Thanks
Which rom, dirty flash the ROM !
Stock b32
I'm with g model on custom rom, just reflash the ROM from sdcard, your data should stay.
Hi, which version are your phone in, A2017 or A2017U? Seems same problem with my phone......Have you tried flash your phone?
A2017U stock b32, not custom rom.
What do mean flash my phone, can I do that with stock rom?
Will it delete all my data?
I hade that problem before I ota update to b32, and still have it..
Thanks for your answer！ You can back up your personal data to your phone'account，then try to factory reset.
I am having issues with the fingerprint sensor reading my finger but I was able to add a new finger.
Thank u guys,
I've found a fix!
For some reason "don't keep activities" on developer mode was "on", turn it "off" fixed the issue.
Glad to hear that, good luck!
Thanks for the tip, I had the same problem, but thanks to you it is solved.
Related
I've had my phone for a few months now
I flashed the Skydragon 6.0.1 ROM yesterday and I wanted to move back to 5.1.1
So I did, I flashed the TWRP for 5.1.1 and I flashed the Stock OOS 2.2.0
But now, my home button works and Im able to register my fingerprint but after I selected use fingerprint to unlock it doesn't unlock
I've tried every solution on the Internet such as
1) Force stop com.oneplus.fingerprint and hard reset
2)Use software nav buttons
3)Factory reset
Nothing seems to work
I love the fingerprint feature in the OP2
Someone please help me out.
When I dialled *#808# and checked the finger print auto test and it said PASS
So Im sure its not a Hardware error
You should probably flash the old modem back. Can you please get into the security settings inside settings and tell me if you have a force close. If you get a force close you have to flash the old modem.
By saying modem I mean firmware. You can find it in OnePlus 2 Android development > taker18's cyanpop's second post.
Or in blissmallow thread second post.
Sent from my ONE A2003 using Tapatalk
I have the exact opposite issue. My FPS works with all ROMs except H2OS 6.0.1. Let me know if you find a solution. Might help me fix my problem.
kane1234 said:
I've had my phone for a few months now
I flashed the Skydragon 6.0.1 ROM yesterday and I wanted to move back to 5.1.1
So I did, I flashed the TWRP for 5.1.1 and I flashed the Stock OOS 2.2.0
But now, my home button works and Im able to register my fingerprint but after I selected use fingerprint to unlock it doesn't unlock
I've tried every solution on the Internet such as
1) Force stop com.oneplus.fingerprint and hard reset
2)Use software nav buttons
3)Factory reset
Nothing seems to work
I love the fingerprint feature in the OP2
Someone please help me out.
When I dialled *#808# and checked the finger print auto test and it said PASS
So Im sure its not a Hardware error
Click to expand...
Click to collapse
I had the same problem. Do a wipe then flash this it worked for me
https://drive.google.com/file/d/0B97c1b2UXMxCZkh3T0VzSmlCWms/view?usp=docslist_api
Sent from my ONE A2003 using Tapatalk
Thanks guy, I fixed the problem by flashing a persist.img
Recently I made a backup before installing a ROM on my oneplus 2. When I was doing it I selected the Boot, System, Data partitions. Then after I restored it everything was working fine except when I was trying to type in my password(not SIM password) it seemed to just restart the UI, but the strange thing was that the Finger print sensor was working I could unlock it that way. So I tried to go in to security setting after that and that also made my UI restart and just threw me back to the home screen. So my question is what mistake did I make when making the backup and how not to make it again?
Perhaps your persistant-partition (where fingerprint data and other security stuff is stored) is damaged. There's an persistant.img which you can flash in fastboot to restore it somewhere here on the op2 forum which you can find if you search.
Best regards
Peter
pitrus- said:
Perhaps your persistant-partition (where fingerprint data and other security stuff is stored) is damaged. There's an persistant.img which you can flash in fastboot to restore it somewhere here on the op2 forum which you can find if you search.
Best regards
Peter
Click to expand...
Click to collapse
But when I install oxygen OS image it works, it just doesn't work when I restore it from a backup.
winVIP said:
Recently I made a backup before installing a ROM on my oneplus 2. When I was doing it I selected the Boot, System, Data partitions. Then after I restored it everything was working fine except when I was trying to type in my password(not SIM password) it seemed to just restart the UI, but the strange thing was that the Finger print sensor was working I could unlock it that way. So I tried to go in to security setting after that and that also made my UI restart and just threw me back to the home screen. So my question is what mistake did I make when making the backup and how not to make it again?
Click to expand...
Click to collapse
Were you on CM13 and installed the H2OS MM firmware? If so, I ran into a similiar thing. You'll may need to flash the Revert2Lollipop to fix.
unremarked said:
Were you on CM13 and installed the H2OS MM firmware? If so, I ran into a similiar thing. You'll may need to flash the Revert2Lollipop to fix.
Click to expand...
Click to collapse
No, I was making a backup of oxygen OS 2.2.1 before installing Resurrection Remix.
So I've been searching all the internet regarding my problem and found none to have my problem.
I was using popwiz rom and after a while my fingerprint sensor stopped working with the error "An error has occureed with the fingerprint sensor. If this message appears repeatedly, restart your device."
Because I needed my G900FQ, I ignored the issue for a while. Found S7 insanity which has a fingerprint bug and forgot about the problem.
Yesterday wanted to check out official MM for my S5, and had to reflash stock lollipop. Then I remembered my fingerprint problem so I tried to set it up. I kept getting that nasty error, tried deleting cache, tried deleting data with Titanium. Reflashed stock 2 times again, nothing worked. Until I was ready to give up and go to bed. Then it suddenly started working. Managed to set it up and activate fingerprint unlock.
Now is the bummer!
I CAN UNLOCK with fingerprint if waiting about 3 seconds after turning screen on.
I CANNOT ADD FINGER through settings, I get the nasty error message.
Tried to enter factory tests and under NormalScan button says Version 0.0.0.0 and in SensorInfo says Ready and stays that way.
I tried to enter factory tests very fast after unlocking with fingerprint and I got, only once and for a brief moment, the right Version and SensorInfo, and Normal Scan showed data and graph.
Now I will try to install official MM firmware with Odin.
Anyone has any ideas to what the cause may be ? And maybe a solution ?
Thanks in advance
L.E. I installed official MM firmware and now fingerprint sensor works when unlocking and adding fingers, but when I try to unlock my phone while it is connected to a power source I get the nasty error message again and prompts me for my backup password. Any advice would be deeply appreciated.
Flash a stock ROM and factory reset?
It seems you did not read the whole thread before suggesting me this...
I did that many times. Lollipop and MM official stock... Its like the sensor is not responding in some situations , but in other situations it does. And this seems to be pretty random..
*Detection* said:
Flash a stock ROM and factory reset?
Click to expand...
Click to collapse
laurent.siku said:
It seems you did not read the whole thread before suggesting me this...
I did that many times. Lollipop and MM official stock... Its like the sensor is not responding in some situations , but in other situations it does. And this seems to be pretty random..
Click to expand...
Click to collapse
It seems you don't even know what you typed, nowhere in your OP did you mention factory resetting and then flashing a stock ROM
Only that you flashed stock ROMs, flashing stock ROMs does nothing to reset anything and will leave behind bugs from the previous ROM if the issue is with an app / data etc
Before getting clever, read what you type
It's obvious that by flashing a stock rom over a custom one will leave bugs. Did full wipe (system, data, cache&dalvik, even phone internal sd) before flashing stock, every time. Thanks anyway..
*Detection* said:
It seems you don't even know what you typed, nowhere in your OP did you mention factory resetting and then flashing a stock ROM
Only that you flashed stock ROMs, flashing stock ROMs does nothing to reset anything and will leave behind bugs from the previous ROM if the issue is with an app / data etc
Before getting clever, read what you type
Click to expand...
Click to collapse
Well maybe next time add that fairly important info to your main post, instead of hoping everyone is psychic, and then throwing a hissy fit when they suggest something you have not stated you already tried.
Nexus 6p, unlocked bootloader and running 8.1DP.
Whenever I make a call and put the phone to my ear the screen turns off and never comes back on. I tested the sensor with the device info app and I the sensor stays in the "close" position when engaged untill the app is restarted.
I did some research and I found that some users had this issue with the Nougat update but no relevant solutions were found and the 7.1.1 update fixed the problem.
I would like to avoid factory reset or locking the bootloader if possible.
Can anyone think of a possible solution?
I tried the Proximity sensor reset app from the play store and that does absolutely nothing.
EDIT: Stable 8.1 doesn't fix the issue, even after clean install and manual flash and wipe.
I'm on SuperXe 8.0 Oreo built and it works flawlessly. I remember having that issue on nougat ROMs use to drive me nuts. Every time I needed the keypad I had to fight to get the screen back on. ?
Not a factory reset. Manually wipe the phone and apply the latest 8.0 image.
So after manually flashing the 8.0 image everything worked. I thought id give 8.1 DP2 a shot and I wiped and flashed this manually. It worked during the restore but stopped working after all my apps were back, so I thought it may be an app that's causing the problem. Strated in safe mode, issue is still there. I guess Ill just have to wait for the stable 8.1 release. If anyone else is facing the issue please post here.
Hello,
I have noticed since I have flashed the universal bootloader for LineageOS 14.1, that sometimes I am unable to perform the pull down action on the notification bar in order to open the quick settings.
Sometimes, this is fixed by locking the screen by pressing the power button and unlocking it after. This does not always work though. A more reliable way to "fix" this is to completely reboot the phone.
Can someone please advise if there's a known, more permanent, fix for this issue?
PS I went back to stock through EDL (shis should overwrite the boostack, right?), and the issue is present on stock rom too (2017G B10 7.1.1)
thanks a lot in advance!
rzarectha said:
Hello,
I have noticed since I have flashed the universal bootloader for LineageOS 14.1, that sometimes I am unable to perform the pull down action on the notification bar in order to open the quick settings.
Sometimes, this is fixed by locking the screen by pressing the power button and unlocking it after. This does not always work though. A more reliable way to "fix" this is to completely reboot the phone.
Can someone please advise if there's a known, more permanent, fix for this issue?
PS I went back to stock through EDL (shis should overwrite the boostack, right?), and the issue is present on stock rom too (2017G B10 7.1.1)
thanks a lot in advance!
Click to expand...
Click to collapse
Wait what? So you flashed the universal bootloader AFTER installing Lineage, and presumably using it?
If you installed an EDL ROM and the problem persists, it's definitely not the bootstack. are you sure there's nothing else that you installed both on stock and los?
Choose an username... said:
Wait what? So you flashed the universal bootloader AFTER installing Lineage, and presumably using it?
If you installed an EDL ROM and the problem persists, it's definitely not the bootstack. are you sure there's nothing else that you installed both on stock and los?
Click to expand...
Click to collapse
I definitely did not flash the bootloader after flashing lineage, I do not believe it's possible; my apologies if my wording was off.
As you said, it is possible that the switch to Lineage was just a coincidence.
You make a good point though, I did restore the same titanium backup apps on both ROMs. I should factory reset and see if it solves it.
cheers
rzarectha said:
I definitely did not flash the bootloader after flashing lineage, I do not believe it's possible; my apologies if my wording was off.
As you said, it is possible that the switch to Lineage was just a coincidence.
You make a good point though, I did restore the same titanium backup apps on both ROMs. I should factory reset and see if it solves it.
cheers
Click to expand...
Click to collapse
Yeah, I just didn't know what you meant. I guess it might be a root app or something. I used Material Notification Shade on stock but it had a couple of problems that i didn't figure out until some time ago (it was pretty obvious though)
And for something physical, have you fitted a screen protector lately? I had one that interfered with pull down.