Hey so I'm new to the OnlePlus 5T. I used to be on the 3T and never had any issues like this, I was a flashaholic on that device so I know my way around the process of flashing custom roms. Or at least I thought so?
So before I ask, here's what I'm running:
- Latest OOS Firmware, I believe 9.0.4
- Resurrection Remix Pie (Official), Dumpling.
- TWRP (Can't remember the version but it's the latest by codeworkx, was posted this month)
- I AM encyrpted
- I AM rooted with the latest Magisk
So here's what I did: Yesterday I got irritated by the lack of official RR updates, so I tried out an unofficial luisroms build. I reverted back because I realised not much had changed, but when I restored my backup I couldn't get into my phone as it said I needed a password even though I made sure to remove all lockscreen security before making the backup in the first place.
After a few hours of trying, I got in but couldn't register a fingerprint. It just wasn't recognising my finger when I tried to actually set it and stayed on the "Touch the fingerprint sensor" screen.
So I went back to Oxygen OS, made sure I was fully updated and encrypted and then re-flashed official Resurrection Remix Pie for Dumpling.
(Important: As of this point, the fingerprint sensor was working perfectly again, so the physical sensor is working fine!)
I've only just got the phone fully set up, I removed the lockscreen security (Including the fingerprint) and went into TWRP. I made a backup. Then I rebooted back into the OS and now when I'm trying to apply my fingerprint again, it's not recognising my finger. Exactly the same as it was before I re-installed OOS.
So summary: TWRP Backups and Restores are breaking my phone's ability to use the fingerprint sensor. Is this a known issue, and how do I fix it?
Thanks for your time, hopefully the good people of XDA can help me out here :good:
EDIT: Progress has been made, ish.
By going into root/data/system/users/0 and deleting "fpdata" and "settings_fingerprint.xml" I can now get the fingerprint setup to recognise my finger in the settings, but right as I'm about to do the final fingerprint press to set it up I get the error: "enrollment was not completed. Fingerprint enrollment didn't work. Try again or use a different finger"
FURTHER EDIT: So as unrelated as it seems, with the issue happening right after making a backup in TWRP, it appears the issue was caused by a Magisk module called NFS-INJECTOR. Not knocking that project, it's amazing and I'm still using it, but after disabling it in magisk and rebooting I was able to set a fingerprint just fine. I've now re-enabled the module and all seems to be working correctly. I've reported the issue over there and linked to here for steps to reproduce, hopefully it's something that can be fixed. I'll leave this up in case anyone else experiences the same thing.
Related
Just recently my fingerprint scanner will decide to stop working. I'll dirty flash my ROM (latest PureNexus) and it'll go back to normal for a little while. Is this a known issue with nougat I'm not aware of?
JeauxAdam said:
Just recently my fingerprint scanner will decide to stop working. I'll dirty flash my ROM (latest PureNexus) and it'll go back to normal for a little while. Is this a known issue with nougat I'm not aware of?
Click to expand...
Click to collapse
No, that is not a nougat issue or an issue with that particular rom. It's either firmware, which is in vendor our a failing fingerprint sensor. Try re flashing vendor and see if that helps
I was having that problem too. I tried several things with no luck. The menu option for the fingerprints (under personal/security) disappeared, and since I am clueless about the Nexus phone (iPhone convert), I was baffled. For a separate reason, I had used the ad blocker plus browser to clear the cache of suspicious garbage, then restarted my phone. The fingerprint menu item reappeared, and now the sensor works again....so try clearing your cache.
I got too i fixed by clean fingerprint connector in the phone.
After restarting my Mi5s the fingerprint scanner doesn't work anymore. The same issue appears when I put the phone off and I put it on a day later (I like to put the phone off while sleeping).
I know that the first time after restarting the fingerprint doesn't work by Android default. However, it also doesn't work thereafter. When I remove the fingerprints in settings and add new ones, it works again. Does anyone have the same issue and a possible solution?
Not having this issue. Which ROM version do you have installed?
I use the xiaomi.eu stable rom.
Ah ok, custom ROM then. Please ask in xiaomi.eu forum, they might know more.
donderdag said:
After restarting my Mi5s the fingerprint scanner doesn't work anymore. The same issue appears when I put the phone off and I put it on a day later (I like to put the phone off while sleeping).
I know that the first time after restarting the fingerprint doesn't work by Android default. However, it also doesn't work thereafter. When I remove the fingerprints in settings and add new ones, it works again. Does anyone have the same issue and a possible solution?
Click to expand...
Click to collapse
I had same problem here after I encrypted my device with 'encrypt device using lock screen'. When I switched encryption off the problem was solved. So seems a software problem. I am working with most recent stable Global Rom (8.0.3.0). Hope it will be solved in next release. China stable was released a few days ago.
had that problem with miui.eu , it was an outdated version of supersu and twrp, updated them and problem solved.
I believe I've deeply messed up here. I was trying to update to 8.1 while keeping Magisk root and ElementalX, but now I've got various UI problems including the home and app switch buttons not doing anything, the cell signal indicator never shows whether I'm on any data network, and notifications never show up. I also get a pop up right after boot that says my device has an internal problem, when I open up the phone app it says that my device isn't supported but I can still make and receive phone calls, and the USB OTG is not functioning at all. Almost if not everything else is working.
I followed the instructions to the T (I'll post a link to instructions a little later) then installed EX but, I didn't have root. At one point I also forced the phone off when it was presumably setting up final things after the ROM switching reboot. After booting up again, several apps were crashing and the problems above came up, so I followed different instructions specifically for installing EX and Magisk, which only fixed app crashes and Magisk.
I'm thinking where I messed up is that I didn't make a Magisk patched boot image for 8.1 before installing it, but at this point I'm not sure if that's the problem. I don't want to wipe the user data partition, but I'd do it if I have to. I have backups of everything anyways.
I just figured out that I was having the same issue as Cristiano Matos, though my OTG cable seems defective. The type-C connection is not working in one orientation, so I'll just have to use it in the other. This thread can be closed. Sorry for my stupidity
Hi
I was running Resurrection Remix on my S9 but due to my job I kept knocking the screen and pocket dialling random people.
So I wanted to revert back to another rom I had previously backed up as it had prevent accidental touches as a feature to prevent any further pocket knocks.
Yet once restored my IMEI had been lost and all three backup were now useless as it had lost the EFS Backup?!?
I had managed to get my phone working but smart switch had decided to put a v2 (binary 2) bootloader on.
Now when I attempt to boot any lineage based rom I am stuck at the bootscreen.
I have wiped everything, formatted data (by typing yes), and even tried dm verity and flashing twrp bootloader to try and trick the phone yet to no avail.
Has anyone else had this problem and found a solution or do I have to now wait until lineage based roms catch up with v2 boot images? (As most are on BRE5/8).
Thanks
Probly gotta wait till they update it. Odin back to stock
UPDATE: I have managed to get the phone to boot lineage.
I succeeded by flashing lineage, gapps, magisk and BRE5 Vendor zip file.
Seems to be all good.
How it started:
I updated Oneplus5t from 8.1 Oxygen stable to 9 Oxygen stable via official update. I used vpn (Germany) to get it a bit faster. I live in Ukraine. We usually get updates much later. At the moment i updated my phone the bug occurs.
Bug: phone randomly goes to lockscreen. Sometimes a couple times in 15 minutes, sometimes ones per day or two. No apps dropped, no any errors spotted. Just like power button was hitted twice.
Some useful info: Seems bug doesn't appear if Youtube or other app opened, that blocks autosleep.
What did i try:
-factory data reset. Bug is here to stay
-update to Beta Oxygen. bug still here but, probably, happens rarely
-Downgrade to Oxygen stable (9.0) via recovery (official) and with cache, system and data wipes. No changes
-Downgrade to last stable 8.1 Oxygen (where was no bug), all wipes, official recovery. Bug is here
-Changed to Lineageos, twrp recovery + magisk, all wipes via twrp including system, cache, data, internal storage. Bug is still here.
-Blocked magnetic sensor (the one for magnetic cases) with xposed module. No changes.
Now I,m trying to catch some logs and compare them. If you know how to read logs i can share them with you.
And I'm trying to understand, is the problem hardware or software.
If it's software, it should already gone, because i changed almost all software so far.
If it's hardware, it should affect my phone in Youtube app too, and it strange that it occurs exactly after pie update.
I'm up for any experiments, thanks a lot for every one who trying to figure out what is going on.
For everyone who will ever face same problem.
I found the solution. Problem was with my sim card (one of them). So phone thought sim card was removed, which caused it drop to lockscreen. So try to remove or replace your Sim card and check your bug, it's probably gone.
And thanks a lot for OnePlus team for helping me, while it was totally not their fault.