Anyone have issue with the Fingerprint not working after updating and putting magisk on it? Can't do anything to make it work.
Removed everything from /data/adb/service.d
Fingerprint works again
I'm having the same issue also. Did removing that directory actually fix the problem? Does anything else have to be redone after removing that directory? Do I need to backup anything up or restore after?
Sorry for the late reply but it was service.d and post-fs-data.d folder. I removed the scripts in them, you can back them up if needed. Starcms said it was substranium magisk mod that caused issues as another possible culprit.
Related
I have yet to get the FP Nav to properly work (or work at all) in either weekly.
I installed weekly 6 with a fresh install and it worked until I restored my apps with Titanium.
Any ideas as to apps that would prevent this from working?
I have tried DPAD, Trackball, and Mouse. and NAV Enable IS set to Enable.
3 day bump 10char
Don't restore random stuff with Titanium and you'll be fine. Just restore the apps you got from the market or sideloaded.
Hmm. I just tried to enable FP nav on weekly #6 (I had it disabled since right after install) and it wouldn't work. Moreover, the FP reader, which had been working, now doesn't work either (I get "Enroll Not Successful"). I'm sure I installed/updated an app or two in the interim, but just through the Market--I did not restore anything via Titanium.
Ah well, I don't completely trust the FP reader anyway, although when it was working it worked pretty well. If there's a way to get it working again without reflashing CM7 I'd be interested. I tried to find the settings discussed in the following thread:
forum.xda-developers.com/showthread.php?t=977600
. . . but there is no "com.motorola.android.providers.settings" directory in /data/data. I guess those settings might be for stock roms, not CM7?
I had a lot of random reboots with FP in weekly #6 so I ended up disabling it and deleting the apks associated with it just to be sure it wouldn't reboot.
I deleted the following apks and I haven't had any random reboots since then.
Atrix Settings 1.0
Fingerprint sensor
com.cyanogenmod.truemobileaudio
Big fan of the Skydragon ROM. :good:
The issues Im having are after the 1.1 update
I applied the update to fix (primarily) the gallery issue (as without it you cant view images in MMS messages)
The issue appears to be access to the SD card once the update has been applied (as well as the already acknowledged Gmail crash)
Both gallery and music are unable to access the external SD card, yet ES file explorer can.
I've tried to 'fix permissions' , and it seems to fix it temporarily, but after a reboot the issue returns.
Hope MaartenXDA can reproduce the issue and its an easy fix!
Cheers for the hard work..its really appreciated!
Okay, thanks for the report.
The fixing permissions should fix it even trough reboots. (In theory). But apparently it doesn't.
If you fix the permissions again, is the issue solved?
Sent from my awesome fridge
MaartenXDA said:
Okay, thanks for the report.
The fixing permissions should fix it even trough reboots. (In theory). But apparently it doesn't.
If you fix the permissions again, is the issue solved?
Sent from my awesome fridge
Click to expand...
Click to collapse
Send them and OTA with an init.d script to fix permissions in /system/etc/init.d. That should work...
Stereo8 said:
Send them and OTA with an init.d script to fix permissions in /system/etc/init.d. That should work...
Click to expand...
Click to collapse
Thanks. I've already been testing a set permissions script and it seems to work.
But @OP, is the issue solved after you set permissions?
MaartenXDA said:
Thanks. I've already been testing a set permissions script and it seems to work.
But @OP, is the issue solved after you set permissions?
Click to expand...
Click to collapse
Maarten..sorry for the late reply.
Im just doing a NAND backup and I`ll let you know in a little while. Ive just re-downloaded the OTA just in case something has changed/corrupted etc.
Cheers
Maarten,
unfortunately fix permissions isn't retained after a reboot.
on the plus side, when you do fix permissions, all issues I'm having, gmail, gallery and music are fixed.
cheers
chocyman said:
Maarten,
unfortunately fix permissions isn't retained after a reboot.
on the plus side, when you do fix permissions, all issues I'm having, gmail, gallery and music are fixed.
cheers
Click to expand...
Click to collapse
Thanks, that's what I needed.
For now I'll just add an init.d script that will fix the permissions on boot. After that I'll look at the problem, it's possible the installation doesn't set the right permissions.
Sent from my awesome fridge
MaartenXDA said:
Thanks, that's what I needed.
For now I'll just add an init.d script that will fix the permissions on boot. After that I'll look at the problem, it's possible the installation doesn't set the right permissions.
Sent from my awesome fridge
Click to expand...
Click to collapse
One suggestion, there are probably some problems inside updater-script, cause permissions are set while flashing. So I think it would be much better to recheck the updater-script than to build scripts to run on boot.
nlooooo said:
One suggestion, there are probably some problems inside updater-script, cause permissions are set while flashing. So I think it would be much better to recheck the updater-script than to build scripts to run on boot.
Click to expand...
Click to collapse
I know, that was my plan. But to keep the users happy while I'm checking the installation, I'll give them a fix first.
MaartenXDA said:
I know, that was my plan. But to keep the users happy while I'm checking the installation, I'll give them a fix first.
Click to expand...
Click to collapse
Thanks for looking at this. Speaking for myself, its no big thing having to manually set permissions when my phone reboots. Unless I'm flashing ROMs, it rarely reboots. If a permanent fix is simpler then perhaps just post the work-around on the ROM thread until it gets included in the next update.
If the init.d script is easy to apply, then I guess its a good way to as you say "keep the users happy ". We are quite a demanding lot aren't we
Top work...keep it up! Lots of ppl are liking this ROM.
cheers
Just applied the 1.2 update and although I can see there's a temp init.d fix, it hasn't worked on my DX.
Same as before, reboot in twrp, fix permissions and app good.
Haven't had a chance to check the other additions. So can't comment on those.
cheers
After restoring an backup via TWRP I had to remove/bypass lockscreen with TWRP to access my android. Still I found my fingerprint reader not working. I fixed this by deleting the fingerprint profile with TWRP.
Symptoms of the issue I had:
Fingerprint is not working to unlock the phone. Lockscreen gives me an error about missing fingerprint hardware.
I can't add new fingerprints. The fingerprint wizard gives me an error message "Enrollment was not completed" and closes the wizard
How to remove the pin/pattern you can find here: https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
Solution for fingerprinter:
Boot into TWRP
Go to advanced>filemanager to acces the files in your phone.
Enter the folder /data/system/user/0
Delete following files: ./fpdata/user.db, settings_fingerprint.xml
Reboot to system and set up new fingerprints with the fingerprint wizard
Everything should work normal
Hope it helps
Thanks!
Only works until the following reboot. So you need to go through the procedure again. Soft reboot leave the fingerprints intact. Tested on Moto G5.
Thanks a lot man! Saved myself from clean flashing on my Oneplus 5!!
Thanks!
On my HTC A9 I had the message "PIN required to enable fingerprint reader". It is an at&t a9 that I've rooted and running the unlocked developer version. I used these steps in TWRP and my fingerprint reader was fixed.
Legend! Thank you for posting this! Saved me from factory resetting my HTC 10!
unfortunatley my fpdata folder is empty... but I still get this "Enrollment was not completed" when around 80% done.... It looks like the very last fingerprint touch is needed. However the whole process still looks broken because sometimes it accept when I touch next time it roll back. It didn't behave like that on stock. Is there any way to fix this problem except flash stock ? BTW I'm now on custom 7.1.2 ROM Resurrection Remix N v5.8.5
Go to /data/system and delete locksettings.db
And then go to /data/system/users/0/settings_fingerprint.xml and delete it.
Worked for me on AEX Oreo.
I sent my OnePlus 3T in for an RMA, when I received it back and restored the TWRP backup my FP was not working anymore. Tried this fix and everything is fine again
Still works after a reboot
thanks konzi.. couldn't remove fingerprints (lineage os 15.1 on redmi note 4 mido)
I gave root access to my file explorer app (es file explorer) and renamed those files (to .bak) and it fixed the issue for me.
I did as it said on OP, but it didn't work :/
This does not seem to work under Android Pie. Only the lockscreen.db file is present, but the fpdata folder is empty and I am unable to remove old fingerprints in settings.
Any ideas.
I hate to revive an old dead thread, but I can confirm that this DOES work on Android Pie (9.0) 181005.003 October security release. Thank you so much OP!!!
One step that may have not been included is to be sure to "mount" the "data" partition or you may not be able to properly "write" and/or delete and/or display the right files...
The user.db file didn't exist for me, but deleting the settings_fingerprint.xml solved the problem for me m
can't delete fingerprint
stitchyman said:
thanks konzi.. couldn't remove fingerprints (lineage os 15.1 on redmi note 4 mido)
I gave root access to my file explorer app (es file explorer) and renamed those files (to .bak) and it fixed the issue for me.
Click to expand...
Click to collapse
Hey bro! Actually I'm using dotos v2.5 on my redmi note 4 and I'm facing problem in deleting fingerprint . plz help
---------- Post added at 08:33 AM ---------- Previous post was at 08:30 AM ----------
stitchyman said:
thanks konzi.. couldn't remove fingerprints (lineage os 15.1 on redmi note 4 mido)
I gave root access to my file explorer app (es file explorer) and renamed those files (to .bak) and it fixed the issue for me.
Click to expand...
Click to collapse
Hey bro! Actually I'm using dotos v2.5 on my redmi note 4 and I'm facing problem in deleting fingerprint . plz help . and also can't add more because only 5 could be added .
appy.79 said:
Go to /data/system and delete locksettings.db
And then go to /data/system/users/0/settings_fingerprint.xml and delete it.
Worked for me on AEX Oreo.
Click to expand...
Click to collapse
Thank you, this saved me from having to do a full clean install.
I confirm this worked on Android Pie (9)
HTC 10. Not working for me. It cleared my fingerprints, but I am unable to register any new ones. It instantly claims "Fingerprint setup was cancelled. Please try again."
Cyber Akuma said:
HTC 10. Not working for me. It cleared my fingerprints, but I am unable to register any new ones. It instantly claims "Fingerprint setup was cancelled. Please try again."
Click to expand...
Click to collapse
I don't know anything about the HTC's...but have you "reset-ted" or, if you have an unlocked bootloader, maybe re-flashing the Full Factory image -- I know with the Pixel's, you can reflash the Full Factory image without wiping the device...
Good luck and hope this helps...
appy.79 said:
Go to /data/system and delete locksettings.db
And then go to /data/system/users/0/settings_fingerprint.xml and delete it.
Worked for me on AEX Oreo.
Click to expand...
Click to collapse
can confirm working on crDroid 9.0 thanks!
simplepinoi177 said:
I don't know anything about the HTC's...but have you "reset-ted" or, if you have an unlocked bootloader, maybe re-flashing the Full Factory image -- I know with the Pixel's, you can reflash the Full Factory image without wiping the device...
Good luck and hope this helps...
Click to expand...
Click to collapse
Forgot to reply earlier. Well, I am attempting to avoid doing a reset, since I just did a backup restore, resetting the phone would be counter-productive.
Regardless, I found the issue, there was a backup file for the prints too, deleting that fixed everything.
Following what appy.79 told solved for me too... crush on lockscreen setting and deleted fingerprints all OK now
I rooted my S9+ following this thread:
https://forum.xda-developers.com/galaxy-s9-plus/how-to/guide-root-s9-oem-fix-t3763974
Since I tempered with some files in the folders data & android and a few others the root access for the modded camera app from zeroprobe says: „check root access“ and it won’t work properly.
In twrp boot mode, I tried wiping and all the apps I previously installed were gone, but upon reinstallation of said modding app the problem remains.
Is there a specific folder I should wipe or how would I go about starting from scratch?
And no, I didn't take a backup yet... (at least not on this phone, but on a second S9+, could I use that one?)
got it working again. As so often when assuming something, the problem was apparently not that I copied some files around. It seems that I needed to start magisk at least once. After that it worked. The modding differs slightly, maybe due to an update of the app. Just guessing here, but at least i got it working.
I have recently rooted my S21, and it works perfectly except for apps such as Paypal having issues around the use of fingerprints.
I can unlock the phone with fingerprints, but every app with the ability to read fingerprints fails. Is this happening for anyone else, and does anyone have any tips?
you needed to backup the DRM keys or use hacked kernal .img
i dont know if there is workaround yet for the S21 series
some app can hack this, but its ilegal AFAIK
also netflix and similar apps might not work well or at all for you
I seem to have fixed the issue. I traced it down to being related to the safety-net magisk module I had flashed. It turns out there seem to be known issues with it, and have been resolved in a test release (version 2.0 I believe)
Pisaman2 where did you get ver 2.0 from plz. Also did you have to use magisk props to change fingerprint like before? Or can you just install ver 2.0 and it will work without issues.