Related
Earlier today I was mucking about and decided to play around with the fingerprint scanner for the first time. When I went in to settings and clicked the fingerprint manager, I received an error stating that the scanner is borked, and to reset my device to fix it. Rebooting did not fix the issue.
Soon I found another person with the same issue, who said that he was able to fix it by flashing stock NJ7 via Odin. After a bit of chatter we realized that neither he nor I had set up the fingerprint scanner before flashing a ROM. We basically booted the phone and went straight to rooting it, and flashing ROMs on it.
I can confirm that re-flashing the stock ROM via odin allowed me to set up the scanner successfully, and that the functionality has not been affected by any subsequent ROM flashing.
I do not understand the mechanism behind why this happens, it is just my experience. Perhaps there is some sort of validation that is run the first time you use the scanner, making sure you are running official firmware, and then setting a flag somewhere? How then would that flag be saved for all subsequent rom flashes? Hidden partition or some ****? Hardware flag? I dunno I don't get it, but I figured out how to fix it by golly. Hopefully this helps someone else.
If any others can confirm the same issue, we may want to add this as a step in the rooting/romming how-to threads, so that others don't run into the same issue.
One good thing is that when I flashed stock via odin, it didn't wipe my data. I was able to then flash TWRP and then Dynamic Kat again, keeping all of my settings the whole way through. Ended up not being as much of a hassle as I thought it was going to be :good:
Thank you for sharing this, I have to say in my case it is not working now i did get the phone rooted and then added jovys rom then did my setup the fingerprint scanner worked for me, then i installed dynamic rom and then the later update of same rom and then the fingerprint scanner is no longer working for me there is a new update for the rom i am going to flash and see if it works now as in a previous version the bloat from samsu g had been removed and with jovys rom being stock rooted it was still there, so i am wondering if it has to do with some of the bloat from Samsung and it being removed that breaks the fingerprint scanner, i will report after i flash the new version of dynamic.
santos.moreno3 said:
Thank you for sharing this, I have to say in my case it is not working now i did get the phone rooted and then added jovys rom then did my setup the fingerprint scanner worked for me, then i installed dynamic rom and then the later update of same rom and then the fingerprint scanner is no longer working for me there is a new update for the rom i am going to flash and see if it works now as in a previous version the bloat from samsu g had been removed and with jovys rom being stock rooted it was still there, so i am wondering if it has to do with some of the bloat from Samsung and it being removed that breaks the fingerprint scanner, i will report after i flash the new version of dynamic.
Click to expand...
Click to collapse
I first noticed the problem while I was on Dynamic Kat 1.1 and thought the same thing, that it was something to do with the Sammy apps, but it still didn't work after updating to DK 1.2. I've had it both working and non-working whilst running the same ROM (1.2,) and the only thing different between the two instances was the fact that I configured it while I was in stock in one instance.
This is important information. Hopefully the devs will be able to fix this asap. Thanks!!
Wow thank you BotsOne! I'm having the same issue. I'll try this in the morning. Before I rooted, I set up the fingerprint scanner and it worked fine the I switched back to swipe, then rooted. After rooting I installed Jovys rom and lo it hasn't worked since. Does the lock screen have to be set to fingerprint scanner at the time of flashing roms or can you set it up once and move on from that point forward? Thanks again!
android242 said:
Wow thank you BotsOne! I'm having the same issue. I'll try this in the morning. Before I rooted, I set up the fingerprint scanner and it worked fine the I switched back to swipe, then rooted. After rooting I installed Jovys rom and lo it hasn't worked since. Does the lock screen have to be set to fingerprint scanner at the time of flashing roms or can you set it up once and move on from that point forward? Thanks again!
Click to expand...
Click to collapse
Honestly I'm not sure. We need a few more people with the same error to get to the bottom of what's going on here. I could be way off with my assumption. We need a bit more info.
Cool I'll try tomorrow and report back..
BotsOne said:
Earlier today I was mucking about and decided to play around with the fingerprint scanner for the first time. When I went in to settings and clicked the fingerprint manager, I received an error stating that the scanner is borked, and to reset my device to fix it. Rebooting did not fix the issue.
Soon I found another person with the same issue, who said that he was able to fix it by flashing stock NJ7 via Odin. After a bit of chatter we realized that neither he nor I had set up the fingerprint scanner before flashing a ROM. We basically booted the phone and went straight to rooting it, and flashing ROMs on it.
I can confirm that re-flashing the stock ROM via odin allowed me to set up the scanner successfully, and that the functionality has not been affected by any subsequent ROM flashing.
I do not understand the mechanism behind why this happens, it is just my experience. Perhaps there is some sort of validation that is run the first time you use the scanner, making sure you are running official firmware, and then setting a flag somewhere? How then would that flag be saved for all subsequent rom flashes? Hidden partition or some ****? Hardware flag? I dunno I don't get it, but I figured out how to fix it by golly. Hopefully this helps someone else.
If any others can confirm the same issue, we may want to add this as a step in the rooting/romming how-to threads, so that others don't run into the same issue.
One good thing is that when I flashed stock via odin, it didn't wipe my data. I was able to then flash TWRP and then Dynamic Kat again, keeping all of my settings the whole way through. Ended up not being as much of a hassle as I thought it was going to be :good:
Click to expand...
Click to collapse
Yes, I am quoting the entire op...
Give me some more evidence of this and I will edit the Root & Recovery Guide immediately... I have seen conflicting posts on this matter too... Also, is not clear if private mode does continue to work after rooting or not... Can anyone confirm... (without flashing any roms... from original unrooted to rooted) Private mode... does work or not??? (Private mode is not suppose to work after rooting... but some say it does work???)
Nice post! Come on people... help...
Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.
inphamous36 said:
Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.
Click to expand...
Click to collapse
I think this may be an additional problem for flashers, but not necessarily the same one I am addressing. The reason I say this is because I hadn't configured the scanner at all previous to when I discovered that mine didn't work, the error completely prevents me from opening the fingerprint manager. I couldn't even enable the fingerprint function to begin with. Does that make sense?
Not trying to argue just trying to make sure we are on the same page =)
Just noticed my fingerprint scanner isn't working. Wtf lol
Sent from my SM-N910T using Tapatalk
i notice this problem as soon as i flashed first rom the only way o get it working again is flashing back to stock odin but no matter what i do as soon as i flash a rom I get a error message ? here the post another member had the same problem
http://forum.xda-developers.com/note-4-tmobile/help/fingerprint-sensor-error-t2918069
inphamous36 said:
Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.
Click to expand...
Click to collapse
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+
So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?
force70 said:
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+
Click to expand...
Click to collapse
Have you tried restoring a backup and using the scanner? That's when it breaks. I can flash roms fine without having to disable it, but it didn't work after I restored a rom that had it enabled. Locked out of it
JawjaBill said:
So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?
Click to expand...
Click to collapse
I can tell you my history. I setup the fingerprint scanner right away before flashing anything as it is a must have feature for me. Later, I flashed a couple different ROM's and never had an issue. Just had to setup the fingerprint again. So my guess is if you set it up before flashing any ROM, you should be good. At least I was. I haven't had to disable before flashing or anything like that.
COCODRILO45 said:
i notice this problem as soon as i flashed first rom the only way o get it working again is flashing back to stock odin but no matter what i do as soon as i flash a rom I get a error message ? here the post another member had the same problem
http://forum.xda-developers.com/note-4-tmobile/help/fingerprint-sensor-error-t2918069
Click to expand...
Click to collapse
force70 said:
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+
Click to expand...
Click to collapse
JawjaBill said:
So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?
Click to expand...
Click to collapse
inphamous36 said:
Have you tried restoring a backup and using the scanner? That's when it breaks. I can flash roms fine without having to disable it, but it didn't work after I restored a rom that had it enabled. Locked out of it
Click to expand...
Click to collapse
keitht said:
I can tell you my history. I setup the fingerprint scanner right away before flashing anything as it is a must have feature for me. Later, I flashed a couple different ROM's and never had an issue. Just had to setup the fingerprint again. So my guess is if you set it up before flashing any ROM, you should be good. At least I was. I haven't had to disable before flashing or anything like that.
Click to expand...
Click to collapse
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...
TEKHD said:
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...
Click to expand...
Click to collapse
I think once you root the KNOX counter gets tripped preventing private mode.
keitht said:
I think once you root the KNOX counter gets tripped preventing private mode.
Click to expand...
Click to collapse
Yeap I know... but there is this:
http://forum.xda-developers.com/galaxy-s5/development/mod-enable-private-mode-knox-0x1-t2904723
That almost nobody seems to know... It's actually possible to regain Private Mode after a tripped Knox... (Not impossible)
TEKHD said:
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...
Click to expand...
Click to collapse
Well now....never tried it but just did and its working for me. Rooted, jovy23 deodexed stock, twrp.
The day i got my phone i odin'd update then installed twrp, then wiped everything but int & ext sdcard, rebooted to recovery, wiped again then flashed the deodexed stock rom.....just tested fingerprint unlock last night for the first time, no problems and just now tested private mode and again that works for me.
keitht said:
I think once you root the KNOX counter gets tripped preventing private mode.
Click to expand...
Click to collapse
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.
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
Hi,
who has experienced the same loss of HDR/HD streaming support with update 10.5.5/10.5.6 (Bootloader wasn't unlocked)?
Anyone got a solution to get back Widevine L1?
As far as we found out in the Oneplus forum all model and firmware variants are effected.
I sent logs to Oneplus through the community app but the answers were more or less prepared and only telling me that they research on this issue. Someone got the info from German support that it will be fixed through OTA, but I don't think this will be possible and most likely we have to go for RMA.
To find out about DRM/Widevine level you can use DRM Info app or Netflix in the player properties.
Best regards,
Bernd
This happened to me as well. Noticed the other day on 10.5.8 that Netflix wasn't in HD anymore. Did not unlock bootloader, just did OTA's through the system, no Oxygen Updater .
I tried unlocking and then re locking the bootloader but this did not fix the issue, I still have L3.
Really hoping I don't have to RMA for this.
Okay I was thinking about doing the same, but obviously it didn't fix it for you so I skip it...
Coming from Oneplus 5 with it's DRM drama this really annoys me.
See this post in OnePlus forum:
https://forums.oneplus.com/threads/...int-registration-error.1218379/#post-21604919
As far as I understood, flashing or in our case updating causes the persistent partition (which is encrypted with the first registered fingerprint) to get unreadable, if you removed the first fingerprint data (which I did when I registered my fingerprints freshly, after applying a screen protector) - but I could be also wrong as I used Google Translate read the original post. Maybe someone who is deeper in the rabbit hole can confirm this theory, cause it would be great to know at least where the issue comes from and if a RMA is required or a solution can be achieved via OTA.
Bernd
So removing FP data corrupts the persist partition, correct?
Of that so;
Removing FP breaks FP
Cross flashing breaks FP
Magisk Canary breaks FP
Relocking breaks FP
I did send my phone for RMA after having it for only two days. So I've been reading up on this issue and for now I have this.
Backup your persist partition
Root only with Stable Magisk 20.4
Make your own patched image
Don't relock your bootloader
Altho I can't seem to find how to backup that partition without unlocking the bootloader
I wouldn't had unlocked my bootloader if I knew it's causing so many issues. Honestly I need root just for vanced yt... So it's not worth the troubles I had ?
Balthazard said:
So removing FP data corrupts the persist partition, correct?
Click to expand...
Click to collapse
possible, as said I'm neither that far in the android rabbit hole nor is my Chinese that good but it's possible that FP is the bad guy in this game.
Not possible to backup with ADB or Fastboot?
But as far as I've read through this thread https://forum.xda-developers.com/showpost.php?p=80139723&postcount=26 even a backup/restore doesn't help. For the moment I hope for a workaround the DRM sh*t by OnePlus - I mean who the hell would use an Android Phone for content piracy...
Bootloader still locked on INAA 10.5.8, Im on L1. I had installed and uninstalled fp, now its back in, no changes
Patching your own is the smart move inho
bigjailerman said:
I had installed and uninstalled fp, now its back in, no changes
Patching your own is the smart move inho
Click to expand...
Click to collapse
Didn't touch my bootloader so far. Original FP was with 10.5.4 and deleted/readded with 10.5.6.
Did you mean by re-adding them with 10.5.8 was bringing L1 back? What should be patched?
Although my setup isn't the same as everyone else here, (bl unlocked, rooted & custom kernel. Also on beta 11). Noticed that Netflix had dropped to L3 in the playback settings section. Cleared storage on the app from settings & used magiskhide on Netflix. Seemed to put the app back on L1.
I accidentally lost the persist.img and I can't fix the fingerprint issue, even with a custom rom the issue is still here.
Would anyone be able to give me there persist.img file? Thank you
MuhannadYT said:
I accidentally lost the persist.img and I can't fix the fingerprint issue, even with a custom rom the issue is still here.
Would anyone be able to give me there persist.img file? Thank you
Click to expand...
Click to collapse
I'm pretty sure persist.img is unique to each individual's phone so it's not something someone else can give without consequence.
Curious as to what actions you performed that resulted in it being lost?
Artimis said:
I'm pretty sure persist.img is unique to each individual's phone so it's not something someone else can give without consequence.
Curious as to what actions you performed that resulted in it being lost?
Click to expand...
Click to collapse
I bought a device that previously had a custom o, when I installed the original from the fingerprint didn't work. I tried crdroid same issue, anyways it was due to the persist.img being messed up, I tried to fix it but I lost the backup, so basically, the fingerprint sensor no longer works now. I found a backup of it but for the 7pro, But that didn't work as well
Did you try this: https://forum.xda-developers.com/t/...r-with-corrupt-persist-in-15-minutes.4129711/