I had installed havok 3.4 and used it with lockscreen and fingerprint sensor working.i removed both before clean flashing havok 3.5 but havok 3,5 was buggy so i restored havok 3.4 backup after formatting my device. but my lockscreen is stuck on swipe only cannot set any other lockscreen now. pls help as it is a fairly new device around 5 months old. and cannot buy a new phone.
Related
So I installed the revolution mod (nougat) and my fingerprint sensor was not working so I installed the stock firmware and because there were no fingerprints saved on stock, I factory reseted the phone, then I installed the revolution rom again and it was working for few days but now it stopped working again (sometimes it does not recognize it and sometimes it doesnt even vibrate... Like i would not even have my finger on it)
So I just updated Magisk from v11 to v12 and my phone is totally douched up. After rebooting there's an "Unable to use fingerprints" message at the bottom of the screen, the touch screen is janky and my unlock pattern no longer works. The screen goes to sleep randomly too and then comes on without being touched. On the off occasson that the unlock pattern DOES work, the screen loads with no icons, just the page dots and status bar with my wallpaper and nav buttons. Uninstalled Magisk and got the same. Rebooted after uninstall, same thing. I guess I'll be reflashing the ROM, but this is a huge pain in the ass. :/
This isn't a question--more of an answer. DO NOT UPDATE to v12. If you did and have trouble, downgrade to 11.x.
I can second this. Updated to 12.0 and my phone started rebooting randomly and fingerprints started not working. Thought it was something with the rom so clean flashed it again, all was fine till I updated Magisk again. Downgraded to 11.6 and so far no more reboots and fingerprint works.
that's odd. it is working great for me. (currently using Weta 4.9.2 and Tilde's latest kernel + latest magisk manager and magisk 12.0 zip flashed)
Def breaks the systemui and causes the device to repeatedly crash on the ls997.
Was how it acted on pre 11.0 builds for us on v20.
Im testing with the dev on magisk now.
Updated to the latest, no issues here on RR with original kernel.
xxxrichievxxx said:
Updated to the latest, no issues here on RR with original kernel.
Click to expand...
Click to collapse
yeah aosp versus stock lg os act differently
i believe last time ls997 was the only one really having issues, but its breaking ui on the ls997
don't do it
I updated also, put phone in a never-ending 30 seconds to reboot. Had to restore.
Hey!
today I noticed something very weird on my OnePlus 5 (64GB)
somehow unlocking the phone with the fingerprint scanner isn't working anymore!
it always says that I have to use my code, like when you unlock it the first time after powering on!
the hardware is working, fingerprint scan works for example fine with my banking app and the option is still available in the settings menu!
Android 7.1.1
security patch 1st september 2017
francokernel 4.4.21
xxx nolimits rom 4.2 based on oos 4.5.14
rooted with magisk
xposed framework v88.2 installed
I did not make any changes to the phone, it simply stopped working!
I have already removed the security unlock and added new fingerprint scans, it did not work...
can anybody help me?
Are you using Greenify? If so, make sure "Alternative Screen Off mode" is enabled in Settings.
Sent from my ONEPLUS A5000 using Tapatalk
Just restart your phone and all works fine again...
If your fingerprint unlock still doesn't work I would try stock OOS instead of xXx No Limits and see if you still have the issue. I found that ROM extremely buggy both times I tried to run it and the other stock based ROM I tried (Freedom) really wasn't much better.
okey I fixed it by wiping cache and dalvik
thanks for your answers
Hi guys,
Recently, I have installed Arrow OS 9.0 and I was unable to enroll my fingerprint (But I can use my fp sensor as home button).
Currently I have flashed stock ROM and restored IMEI. I was able to use both my SIM slots and device name shows xt1643. Again, I was not able to enroll my fingerprint. The error message reads "INTERNAL ERROR, Sorry your fingerprint can not be enrolled due to internal error". But, after rooting my device i was able to use it as home button.
Is there any thing that i have missed? Or is my fp sensor gone?
askreddy2 said:
Hi guys,
Recently, I have installed Arrow OS 9.0 and I was unable to enroll my fingerprint (But I can use my fp sensor as home button).
Currently I have flashed stock ROM and restored IMEI. I was able to use both my SIM slots and device name shows xt1643. Again, I was not able to enroll my fingerprint. The error message reads "INTERNAL ERROR, Sorry your fingerprint can not be enrolled due to internal error". But, after rooting my device i was able to use it as home button.
Is there any thing that i have missed? Or is my fp sensor gone?
Click to expand...
Click to collapse
I am using Redmi Note 4 and facing same problem after flashing Aosp Extended Pie ....The fingerprint sensor wouldn't just work. As if it is dead
Tried deleting these files
Root/data/system/users/0/settings_fingerprint.xml
And
Root/data/system/users/0/fpdata/users.db
Now the files are gone and sensor is dead ....Works when Miui is flashed but dont know what is going wrong in custom Rom
marzipan sasquatch said:
I am using Redmi Note 4 and facing same problem after flashing Aosp Extended Pie ....The fingerprint sensor wouldn't just work. As if it is dead
Tried deleting these files
Root/data/system/users/0/settings_fingerprint.xml
And
Root/data/system/users/0/fpdata/users.db
Now the files are gone and sensor is dead ....Works when Miui is flashed but dont know what is going wrong in custom Rom
Click to expand...
Click to collapse
Thankyou brother for the info. But even after reverting back to stock rom, my fp sensor was not working properly. Maybe some of my vendor files were messed up.
Fingerprint Scanner Null after Pie ROM Flash - Custom ROM won't fix. Stock Only
Ok, the story.... Moto G5+ retail, running 8.1 Oreo, Bootloader Unlocked, rooted using Magisk 16.7 and was able to backup my Stock Oreo ROM once rooted, or I'd be dead in the water.
So wanting to stay ahead, I tried my hand at RR v7's Pie version, which, after some troubleshooting, was able to install successfully; but I don't much care for the google bar and other hard-coded "pure android" features. Same thing with Pixel Exp. Not to mention that Pie disallows call recording among a few other things Google decided to stifle its customers with. Deal breaker. So - moving on...or back for that matter.
I proceeded to download RRv6, which is btw running nicely on a 2nd G5+, same GApps, installs perfect except - FingerPrint Reader is not acknowledged. Period. No Security settings, No RR Config to access it, Nada. No matter what ROM I flash outside of the StockROM I backed up, it won't recognize the fp reader upon boot up. Whether I clear Dalvik/Cache, All DATA, do a full Wipe, DATA WIPE, REPAIR, FORMAT, nothing allows me to install RR v6.0 or any other flavor, Oreo or Pie, even while trying a dirty flash over Stock Oreo on this Moto G5+. Tried with several SD Cards, downloading fresh zip files from RR. I even went so far as to image the working G5+, then copy into the 2nd G5's SN folder, and do a restore, just loops - even after repairing the partition. I managed to work around that, Restored the image, but still no FP recognized by the initial Google startup/setup. It's almost as if the phone's been "firmwared" or "tagged".
Any ideas what could be lingering from Android Pie that would survive a F2FS/exT Format? Because something updated some kind of firmware on the phone during a Pie ROM flash, that now won't let me go back to anything below Pie, with a working fingerprint reader. The only difference between the G5 that works and this one is the working one has never seen Android 9. And it's staying that way til we come up with a way to hack the google crap.
Any help would be - awesome to say the least.
Thanks for looking.
Hello,
The issue with fingerprint is that after flashing stock Oreo ROM it replaces some files related to fingerprint sensor.
Hence all the newer custom ROM builds use the Oreo firmware related files. Hence it worked on the Pie ROM.
RR v6 would be still using the old nougat firmware hence you need to flash a file for it work. Which will replace the fingerprint related files for Nougat Stock firmware:
https://androidfilehost.com/?fid=1322778262904029634
In case you want to revert the changes and use Pie ROMs:
https://androidfilehost.com/?fid=1322778262904029635
sharan.nyn said:
Hello,
The issue with fingerprint is that after flashing stock Oreo ROM it replaces some files related to fingerprint sensor.
Hence all the newer custom ROM builds use the Oreo firmware related files. Hence it worked on the Pie ROM.
RR v6 would be still using the old nougat firmware hence you need to flash a file for it work. Which will replace the fingerprint related files for Nougat Stock firmware:
https://androidfilehost.com/?fid=1322778262904029634
In case you want to revert the changes and use Pie ROMs:
https://androidfilehost.com/?fid=1322778262904029635
Click to expand...
Click to collapse
That would make sense if PHONE1 manifested the same thing. But I went from StockOreo to RRv6-Oreo w/out losing anything and having to flash any FP Firmware. I used the RRv6 Official from 18-0911. Which is what's been leading me to believe there's something awry with this 2nd G5. I wonder is it possible PHONE2 has some slight firmware variance that is simply ignoring during the RR flash? Anyway, I'll give this a shot. this is TWRP flash, not fastboot, yes? Just being clear as I'm not proficient at this just yet.
Thanks Sharan!
DJScribe said:
That would make sense if PHONE1 manifested the same thing. But I went from StockOreo to RRv6-Oreo w/out losing anything and having to flash any FP Firmware. I used the RRv6 Official from 18-0911. Which is what's been leading me to believe there's something awry with this 2nd G5. I wonder is it possible PHONE2 has some slight firmware variance that is simply ignoring during the RR flash? Anyway, I'll give this a shot. this is TWRP flash, not fastboot, yes? Just being clear as I'm not proficient at this just yet.
Thanks Sharan!
Click to expand...
Click to collapse
Yeah, give it a try. And yes it's to be flashed via TWRP.
[SOLVED]
sharan.nyn said:
Yeah, give it a try. And yes it's to be flashed via TWRP.
Click to expand...
Click to collapse
Sweet! I had to reflash from scratch as for some reason it wouldn't let me update the ROM already running. But once I re-flashed RRv6-8.1, then flashed FP, it's now back. You rock Sharyn - nice work!
Now if only we found a way to cleanup that Pie - hate the perpetual time stamp, search bar and inability to record voice. Which is why I'm staying on Oreo til further notice. I know it was Google who took it away on v9.
Thanks again Shar!
:good::victory:
DJScribe said:
Sweet! I had to reflash from scratch as for some reason it wouldn't let me update the ROM already running. But once I re-flashed RRv6-8.1, then flashed FP, it's now back. You rock Sharyn - nice work!
Now if only we found a way to cleanup that Pie - hate the perpetual time stamp, search bar and inability to record voice. Which is why I'm staying on Oreo til further notice. I know it was Google who took it away on v9.
Thanks again Shar!
:good::victory:
Click to expand...
Click to collapse
Crap - so turns out this solution was short-lived. FingerPrint Scanner is back to inactive and FPzip isn't fixing it. Only StockOreo brings it back. Tried a plethora of ROMs from Nougat to Oreo, nothing but Pie and stock Oreo. Symptoms say it's the ROM, but a ROM that is currently working on the 1st G5 won't work either. Still looking for solutions, anyone...