Hi.
I've been looking for similar problem here but I've found nothing.
Here's my situation.
Stock rom
Unlocked bootloader, changed recovery to TWRP
Backed up stock rom, flashed CM13
*CM13 apps are crappy* Backed up CM13 and restored stock rom.
Current status: fingerprint sensor freaks out. I've came up to this in camera app as soon as it started to take billions of selfies (idiotic feature of taking picture by fingerprint sensor). Then checked if I can set finger pattern - not at all, ZUK started to take thousands of patterns and vibrating all the time. It's hard to explain, but it seems that sensor stucks in a loop that scan fingerprint and somehow founds it (even if ZUK is lying down untouched).
Best of all is that, when I restore CM13, sensor does fine as new, so it can't be strictly hardware issue, drivers perhaps?
The fact is I don't really need fingerprint scanner and best solution would be disabling it.
Any ideas how to do this? Or what really happened and how to restore its functionality?
macnow30 said:
Hi.
I've been looking for similar problem here but I've found nothing.
Here's my situation.
Stock rom
Unlocked bootloader, changed recovery to TWRP
Backed up stock rom, flashed CM13
*CM13 apps are crappy* Backed up CM13 and restored stock rom.
Current status: fingerprint sensor freaks out. I've came up to this in camera app as soon as it started to take billions of selfies (idiotic feature of taking picture by fingerprint sensor). Then checked if I can set finger pattern - not at all, ZUK started to take thousands of patterns and vibrating all the time. It's hard to explain, but it seems that sensor stucks in a loop that scan fingerprint and somehow founds it (even if ZUK is lying down untouched).
Best of all is that, when I restore CM13, sensor does fine as new, so it can't be strictly hardware issue, drivers perhaps?
The fact is I don't really need fingerprint scanner and best solution would be disabling it.
Any ideas how to do this? Or what really happened and how to restore its functionality?
Click to expand...
Click to collapse
You can try to delete /data/system/users/0/fpdata/user.db and /data/system/0/users/settings_fingerprint.xml. Then reboot.
Another possibility is to reflash stock rom, not restore backup!
I have also been through the same situation. Restoring the COS 12.1 will freak out the Fingerprint scanner and camera issue as well. The best option is to flash the Stock ROM COS 12.1.
Happened to me aswell.
I did this:
http://forum.xda-developers.com/zuk-z1/help/fingerprint-stopped-t3290228/post69030576#post69030576
macnow30 said:
Hi.
I've been looking for similar problem here but I've found nothing.
Here's my situation.
Stock rom
Unlocked bootloader, changed recovery to TWRP
Backed up stock rom, flashed CM13
*CM13 apps are crappy* Backed up CM13 and restored stock rom.
Current status: fingerprint sensor freaks out. I've came up to this in camera app as soon as it started to take billions of selfies (idiotic feature of taking picture by fingerprint sensor). Then checked if I can set finger pattern - not at all, ZUK started to take thousands of patterns and vibrating all the time. It's hard to explain, but it seems that sensor stucks in a loop that scan fingerprint and somehow founds it (even if ZUK is lying down untouched).
Best of all is that, when I restore CM13, sensor does fine as new, so it can't be strictly hardware issue, drivers perhaps?
The fact is I don't really need fingerprint scanner and best solution would be disabling it.
Any ideas how to do this? Or what really happened and how to restore its functionality?
Click to expand...
Click to collapse
You can't downgrade android version via backup because each Android version needs different firmware files so if you want to roll back from mm to lollipop you must flash the needed firmware files, you can do that flashing cos12.1 via twrp or fastboot.
Enviado desde mi ZUK Z1 mediante Tapatalk
Related
Hi,
I have a very big problem.
After I’ve flashed this rom (Unofficial cm13 Mr. Coldbird), the fingerprint sensor disappeared from the settings
How can I fix it?
P.s
It 's my first message , I hope I used the correct section of the forum
Do you flash mm-firmware.zip?
for me it works sometimes and sometimes keep hanging " just vibrating without unlock " .. sometimes it says " hardware is not found "
i entered the recovery and flashed mm-firmware.zip again and the same problem exist ... i'm thinking to back to COS 12.1 it was working perfectly !
I have exactly the same problem, fingerprint option totally disappeared from my lockscreen settings. No idea how to fix it.
Shivver said:
I have exactly the same problem, fingerprint option totally disappeared from my lockscreen settings. No idea how to fix it.
Click to expand...
Click to collapse
when I'm looking for a setting, that I can't find in the settings dialog, I'm using the search function, there. This showed already quite some features.
I'm still on original Cyanogen OS 12.1 (5.1.1), though...
best regards
m
meikelrix said:
when I'm looking for a setting, that I can't find in the settings dialog, I'm using the search function, there. This showed already quite some features.
I'm still on original Cyanogen OS 12.1 (5.1.1), though...
best regards
m
Click to expand...
Click to collapse
Install mm firmware.zip
Sent from Zuk Z1 using Tapatalk
Same Problem here.. In cm13 official and Mr coldbirds Version.. Even with installing mmfirmware.zip
I have the same problem too. It have tested on official CM13 and om Mr.Colbird CM13 versions.
me too
the problem of vibrating that was because of third party app like " screen lock " but if you locked it with power button or double tap the fingerprint sensor will work perfectly :good:
I happen the same. Since I installed unofficial CM 13 (Mr. Coldbird) fingerprint sensor has disappeared.
I have even tried to solve it installing stock COS with qfil, but although the app has appeared again, the sensor doesn't work. I put the finger on it, but no signal arrives to the phone.
I have tried hard reset, install mmfimware, official CM 12 and 13, unofficial 13, but nothing work.
Any idea? Thanks.
Vfc73 said:
I happen the same. Since I installed unofficial CM 13 (Mr. Coldbird) fingerprint sensor has disappeared.
I have even tried to solve it installing stock COS with qfil, but although the app has appeared again, the sensor doesn't work. I put the finger on it, but no signal arrives to the phone.
I have tried hard reset, install mmfimware, official CM 12 and 13, unofficial 13, but nothing work.
Any idea? Thanks.
Click to expand...
Click to collapse
Try this method I have described earlier. It has recovered my Fingerprints already twice. Also because of trying unofficilal cm13. http://forum.xda-developers.com/showpost.php?p=64742948&postcount=2
Planet X said:
Try this method I have described earlier. It has recovered my Fingerprints already twice. Also because of trying unofficilal cm13. http://forum.xda-developers.com/showpost.php?p=64742948&postcount=2
Click to expand...
Click to collapse
I'll try and report. Thanks!!!
I've tries, but it hasn't worked.
Just one question, how do you exit fastboot mode?. I'm a beginner, sorry.
Vfc73 said:
I've tries, but it hasn't worked.
Just one question, how do you exit fastboot mode?. I'm a beginner, sorry.
Click to expand...
Click to collapse
Fastboot reboot or just press the power button until the phone shut down. I don't know went it didn't help you but i have recovered my fingerprint reader already twice with that procedure. You will lose nothing when just flashing the modem and the bootloader. My guess is that the persist.img is the partition you need to restore for the fingerprints. My fingerprint reader has been acted really crazy when i tried the unofficial cm13. Until it stopped working. I restored my backup and did the procedure to recover my fingerprint reader. I'm now on self built odexed cm13 nightly 's with working fingerprint reader.
Stopped working here too. Tried to restore COS but even if the setting is there, fingerprint doesn't get detected (phone keeps vibrating)
simoneser said:
Stopped working here too. Tried to restore COS but even if the setting is there, fingerprint doesn't get detected (phone keeps vibrating)
Click to expand...
Click to collapse
Read my post above. I have recovered two times from this issue. I had it also because of trying unofficial cm13. You will loose nothing but get back your fingerprints.
I have tried but it doesn't work
Inviato dal mio Z1 utilizzando Tapatalk
I have tried too, but it doesn't work.
Vfc73 said:
I have tried too, but it doesn't work.
Click to expand...
Click to collapse
Yesterday my fingerprint stopped again too. So I did the same procedure again and it didn't work anymore for me too. So I tried to flash the official cm13 again. First it didn't work but after a few minutes it started to work again. I really don't know how this is possible but there is one difference. The radio from official cm13 is newer than the one from COS. I'm happy that it works fine again but I'm afraid it will stop again when I try a different rom again.
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've been without sensors nor camera for a while now (almost a year), got broken because an OTA update. Tried downgrading, didn't work.
Yesterday I managed to root and install TWRP, did some research and heard about ''persist'' partition. I've been searching for similar cases but no luck. Also tried deleting sns.reg
Can someone provide me the persist.img stock file? So I can finally fix my sensors.
Broken sensors:
Gyroscope
Ambient light
Accelerometer
Proximity
Fingerprint
Camera Flash isn't working either.
Foxxo990 said:
Hello,
I've been without sensors nor camera for a while now (almost a year), got broken because an OTA update. Tried downgrading, didn't work.
Yesterday I managed to root and install TWRP, did some research and heard about ''persist'' partition. I've been searching for similar cases but no luck. Also tried deleting sns.reg
Can someone provide me the persist.img stock file? So I can finally fix my sensors.
Broken sensors:
Gyroscope
Ambient light
Accelerometer
Proximity
Fingerprint
Camera Flash isn't working either.
Click to expand...
Click to collapse
Solved, download the firmware version you have here and look for persist.img. The firmware comes with it but the install script doesn't use it. Just flash it:
Code:
fastboot devices
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot
Hello friend,i have similar problems,apart from fingerprint sensor,all my sensors and cameras,camera light are not working,will i loose imei numbers if i flash the persist img ? i dont know how to flash persist img,can you help me please?
Edit: hi i actually fixed my problem by flashing persist.img, all sensors and cameras are working now
Thank you so much
I would like to thank you for this solution, finally, after 2 days trying I have my ZS570KL alive and working faster, I had to try rooting, then it was bricked for some hours, finally I got it rooted, but after deleting that persist/sensors/and.reg it was the same... until i found this thread, everything works good!!! thank you very much
3sgebeams said:
I would like to thank you for this solution, finally, after 2 days trying I have my ZS570KL alive and working faster, I had to try rooting, then it was bricked for some hours, finally I got it rooted, but after deleting that persist/sensors/and.reg it was the same... until i found this thread, everything works good!!! thank you very much
Click to expand...
Click to collapse
Did you also have broken sensors issue and it is fixed now? I want to try it on my ZS570KL too, but is there a persist.img for this phone?
DIXES said:
Did you also have broken sensors issue and it is fixed now? I want to try it on my ZS570KL too, but is there a persist.img for this phone?
Click to expand...
Click to collapse
Depending on your OS version yes, contact me on Telegram @GuerrillaRadi0 (the last character is zero) maybe I can help you, after I fixed the problem I configured fingerprint security and the problem came back, so I tried to flash persist.img again and it didn't work, so I got the raw rom of the Oreo version I have; WW-15.0210.1810.73, which comes with its own ADB, and flashed from there, the same raw rom has the persist.img. After that all sensors worked again, so I configured fingerprint security again just to be sure, and again I lost all the sensors, but after deactivate fingerprint again everything worked fine, I guess I have some hardware issue related to fingerprint sensor, I guess it was because a technician opened the phone to replace screen and battery 2 months ago. I always used fingerprint so I need to go back to pattern.
Good luck
After some days without any issue the problem came back, I flashed persist.img twice and it worked, but about 3 days ago I can't solve this flashing persist.img, I tried wiping everything, downgrading to Nougat, then flashing Oreo, with TWRP and via flashtool, no solution, any other idea?? all sensors are not working.
Thanks in advance
Hello,
I just upgraded my phone to OOS 9.0.13 and xXx to 6.0. Since then, I can no longer use my fingerprint sensor properly. I can see the icon on my phone but it's a bit darker and when I place my finger on it to unlock, nothing happens. However, if I tap it multiple times, it tells me I'm pressing it too fast but there's no animation like there is when you unlock your phone.
I deleted the fingerprint I had already and now I can't setup a new one because of what it's doing. I power cycled the device, cleared dalvik cache.. still no luck. All I did was booted to recover, flashed the new OOS version, flashed TWRP installer, rebooted to recovery, flashed magisk, flashed Blu_Spark kernel, rebooted system. I've never had this issue before and the fingerprint sensor was working just fine before I made this change.
Any ideas? I've disabled xXx in Magisk and it still didn't work.
Thanks!
mobbdeep said:
Hello,
I just upgraded my phone to OOS 9.0.13 and xXx to 6.0. Since then, I can no longer use my fingerprint sensor properly. I can see the icon on my phone but it's a bit darker and when I place my finger on it to unlock, nothing happens. However, if I tap it multiple times, it tells me I'm pressing it too fast but there's no animation like there is when you unlock your phone.
I deleted the fingerprint I had already and now I can't setup a new one because of what it's doing. I power cycled the device, cleared dalvik cache.. still no luck. All I did was booted to recover, flashed the new OOS version, flashed TWRP installer, rebooted to recovery, flashed magisk, flashed Blu_Spark kernel, rebooted system. I've never had this issue before and the fingerprint sensor was working just fine before I made this change.
Any ideas? I've disabled xXx in Magisk and it still didn't work.
Thanks!
Click to expand...
Click to collapse
It could be the kernel. Doing a search found results in the blu_spark thread with fingerprint issues.
dj_ooms said:
It could be the kernel. Doing a search found results in the blu_spark thread with fingerprint issues.
Click to expand...
Click to collapse
Definitely makes sense now that I think about it. I thought at first only custom ROM's were having that issue
mobbdeep said:
Hello,
I just upgraded my phone to OOS 9.0.13 and xXx to 6.0. Since then, I can no longer use my fingerprint sensor properly. I can see the icon on my phone but it's a bit darker and when I place my finger on it to unlock, nothing happens. However, if I tap it multiple times, it tells me I'm pressing it too fast but there's no animation like there is when you unlock your phone.
I deleted the fingerprint I had already and now I can't setup a new one because of what it's doing. I power cycled the device, cleared dalvik cache.. still no luck. All I did was booted to recover, flashed the new OOS version, flashed TWRP installer, rebooted to recovery, flashed magisk, flashed Blu_Spark kernel, rebooted system. I've never had this issue before and the fingerprint sensor was working just fine before I made this change.
Any ideas? I've disabled xXx in Magisk and it still didn't work.
Thanks!
Click to expand...
Click to collapse
i have the same issue with mine. but i have the stock rom so i dont have any idea how to fix it. i hope there's something wrong with some software update but i rly dont know. If you find something let me know
how is everyones fingerprint scanner? I don't wanna do onscreen cause it's slower than the rear, what about the 7? I'm almost gonna stay with my 6 just because there's no rear anymore....
with every update it becomes quicker, no issues.. there is a big difference since the early updates.
entwicklun said:
how is everyones fingerprint scanner? I don't wanna do onscreen cause it's slower than the rear, what about the 7? I'm almost gonna stay with my 6 just because there's no rear anymore....
Click to expand...
Click to collapse
Traditional sensors are superior in speed and accuracy the in-display fingerprint is garbage and not ready for market. If it's a dealbreaker for you stay with the 6.
entwicklun said:
how is everyones fingerprint scanner? I don't wanna do onscreen cause it's slower than the rear, what about the 7? I'm almost gonna stay with my 6 just because there's no rear anymore....
Click to expand...
Click to collapse
I find it to be excellent. Slightly slower than my 3T, but just as accurate. And MUCH more accurate than my work-provided iPhone 6. The reader learns over time; after about a week or two it was working optimally.
Rear facing FP scanners are the worst in my opinion. A common use case for me is to have the phone on my desk and I like unlocking it without having to pick up the phone to access anything on the back.
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...