Anyone else experience this? It happened after upgrading magisk, then reflashing dtbo and re patching with an earlier version of magisk.
Fingerprint gestures still works inside the OS. And when I try to register a new fingerprint, it reads my finger up until the last "read" then throws an error that the fingerprint registration has failed.
I actually have had this error, wifi also stopped working. It's something to do with Flash Kernel and the current way we have to be unlock. If you flash a stock kernel or the modded one with safteynet pass it should go back to normal.
Thanks for the reply, I wiped and started over before I saw your reply. Next time I'll try the OEM kernel first!
Anyone still having the issues with Fingerprint Hardware and Wifi after updating Magisk and flashing a new kernel? I updated Magisk to 15.3 today and also tried flashing Flash Kernel, and I can't get Wifi or fingerprint to work. Have tried flashing back to the Stock+Safetynet Pass Kernel, but still having the same issues.
I just received this error this week.
So, I should just flash stock firmware and it should be good?
Same description: fingerprint won't unlock/verify, but the gestures still work within the OS. Very annoying.
I had to flash a factory image to fully wipe in order to fix this error.
Swiftkey might be the issue
On mine -- Swiftkey was the culprit. Try removing Swiftkey.
Related
Alright, This is just because I am trying to take precautions so that way I do not end up with a brick.
Currently I am rocking 5.1 PAC-MAN and things are going well. But LineageOS for MM for 6045 came already and I want to use that as my daily driver.
Here is where I run into a problem. For those of you that know I only have LP radios and modems on my system. Main problem I am having and is keeping me from flashing is the lack of a MM radio and or modem. Is there anyone that is on 6045O that had tried this out without having that lockscreen problem?
If you don't flash the MM radios, you will end up with lock screen issues, unfortunately.
-EDIT-
So apparently I can't read. I have the 6045O and this link has the correct modem files to fix the lock screen issues.
https://mega.nz/#F!u0UBAICD!DzKYnswfK5J6dw5WQNgEDg
6.0.1 modem is the file you need.
magus7091 said:
If you don't flash the MM radios, you will end up with lock screen issues, unfortunately.
-EDIT-
So apparently I can't read. I have the 6045O and this link has the correct modem files to fix the lock screen issues.
https://mega.nz/#F!u0UBAICD!DzKYnswfK5J6dw5WQNgEDg
6.0.1 modem is the file you need.
Click to expand...
Click to collapse
Attempted. Everything but the pin issue is good. Weird how it trips badly with the PIN. Installing SuperSU as we speak.
EDIT: Looped after SuperSU flash..
EDIT2: Going back to 5.1. Thank you very much for the support.
Huskied said:
Attempted. Everything but the pin issue is good. Weird how it trips badly with the PIN. Installing SuperSU as we speak.
EDIT: Looped after SuperSU flash..
EDIT2: Going back to 5.1. Thank you very much for the support.
Click to expand...
Click to collapse
While playing around with ROMs for the phone I had some odd issues here and there. As far as the SuperSU flash, it almost always loops a couple times during the reboot process, but I've switched to the lineageOS official su addon because I like native support and root management. Also it never did those initial boot loops. When I did have an issue (just recently, in fact) I ran a wipe of the system partition, then installed the rom, and ran the repair file system option in TWRP, and since then it's been smooth as butter. If you're interested in giving it another go, just let me know and I should be able to link you the files, as they're on my google drive.
magus7091 said:
While playing around with ROMs for the phone I had some odd issues here and there. As far as the SuperSU flash, it almost always loops a couple times during the reboot process, but I've switched to the lineageOS official su addon because I like native support and root management. Also it never did those initial boot loops. When I did have an issue (just recently, in fact) I ran a wipe of the system partition, then installed the rom, and ran the repair file system option in TWRP, and since then it's been smooth as butter. If you're interested in giving it another go, just let me know and I should be able to link you the files, as they're on my google drive.
Click to expand...
Click to collapse
May I ask one more thing? Have you ever gotten the PIN lock or password or pattern lock to work?
EDIT: Nvm. Using Hi-Locker for now. All is good.
I use a pattern lock on mine, and after flashing the modem files, the lock screen functions as it should with all methods. Consider re-flashing the modem and ROM if you get to where you want to play with it, full wipe prior, no dirty flash.
I searched for hours and only found incomplete bits and pieces, so I hope you guys can help me.
I flashed my G920F with FrankensteinS6 (a custom rom with the latest stock kernel) and everything works fine, but I can't get the fingerprint sensor to work, it always prompts me to restart the device.
I found a few posts stating that I have to flash the correct bootloader in order to get fingerprints to work again.
I just flashed the BL/AP/CP and CSC of the latest stock firmware. I tried to activate the fingerprint lock on the stock os to eliminate the custom ROM as a factor. However, it didn't work: I get the exact same error. Even after wiping the cache and performing a factory reset, it still shows that error. Also, the fingerprint sensors shows "Version: Null" in the *#0#* menu. Any ideas?
Strel0ka said:
I searched for hours and only found incomplete bits and pieces, so I hope you guys can help me.
I flashed my G920F with FrankensteinS6 (a custom rom with the latest stock kernel) and everything works fine, but I can't get the fingerprint sensor to work, it always prompts me to restart the device.
I found a few posts stating that I have to flash the correct bootloader in order to get fingerprints to work again.
I just flashed the BL/AP/CP and CSC of the latest stock firmware. I tried to activate the fingerprint lock on the stock os to eliminate the custom ROM as a factor. However, it didn't work: I get the exact same error. Even after wiping the cache and performing a factory reset, it still shows that error. Also, the fingerprint sensors shows "Version: Null" in the *#0#* menu. Any ideas?
Click to expand...
Click to collapse
There's a zip floating around that flashes the stuff for the fingerprint sensor
I'm still on 47.1.A.5.51 and was having some issues with my phone frequently restarting itself and I tried updating Magisk from 14.3 to 18.0 and TWRP from 3.1.1.0 to 3.2.X.X (can't remember offhand). It seems to have stopped the rebooting issue but now DRM fix doesn't seem to work anymore. I am using the kernel and fix provided by shoey63.
I did consider updating to Pie but it seems that there's still a bunch of bugs and stuff. Also couldn't find a proper step by step guide of what the flash order is for it to not lose userdata.
Help would be much appreciated. I just need to hold on to this device for another couple of months before XZ4.
EDIT: It's Magisk that is causing the problem, updating it makes the rebooting issue disappear. Can't update because the free version of DRM fix isn't updated for the newer versions of Magisk.
EDIT2: To heck with it, I installed the DRM and kernel from Janjan's thread even though my firmware is an older version and everything seems to work. It's on Magisk 17.1 and not the latest 18.0 but as long as it doesn't reboot it's mission accomplished for now. Bonus points because now it passes SafetyNet too.
I obviously have clean flashed OOS on both slots before installing this ROM.
I checked the vendor directory, the file doesn't exist.
Would really like to use it, puzzling why it doesn't work. Am I missing something?
EDIT: SOLVED
Firmware was the issue. I followed a thread that let me flash firmware manually, and I was only flashing the firmware through fastboot. There was another section that involved flashing other parts in TWRP ADB, which couldn't be flashed in fastboot. I must have missed those.
Also, after I updated the firmware properly, the error changed. It complained about a DNS error, of which the magisk module dnscrypt- proxy was the culprit.
Long story short, make sure firmware is COMPLETELY upgraded.
I was flashing firmware with official OOS zips, but I don't think they were full updates, only OTAs that didn't have all of the firmware included, causing some wierd errors. I'm surprised that the hotspot was the only thing broken.
Well I just checked it on another OP6, the driver doesn't exist, but hotspot works? Really puzzling.
Well I just flashed every single partition of v9.0.7 by hand, besides boot and system.
Still doesn't work.
Hi everyone, this is my first post here on XDA but i'm a very looong passionate of this forum.
Recently my loved one plus 7 pro has experience some weird mic issues so I changed the motherboard and this resolved every problem.
But now I'm experience some really strange software issues, I'm able to flash the stock OOS but I can't upgrade OOS, I always get a "signature verification failed" or when I'm able to pass the verification (by downloading many times the update) the update fails, only once I was able to update. The firmware, flashed with msmdownloadtool, works fine. The problem is that often many app crash and the ui reboots randomly. I've also tried to install pixelexperience ROM but it's the same with the apps, the continue to crash, I always clean flash everything.
Do you have any idea why app continues to crash?