As topic states, I wonder if it's possible, or do I have to send the phone away for service? There are fixes fot those who have fingerprint issues, but all require root. I want to restore full stock OOS to my OP8Pro, so those fixes don't solve my problem.
For most people yes it is AFAIK.
Have you had the persist issue prior to relocking?
Related
How to be on N modem? And how to check whether, I am on N modem or M modem?
Bunny 2886 said:
How to be on N modem? And how to check whether, I am on N modem or M modem?
Click to expand...
Click to collapse
Check your baseband version, if it's ending in .52R (Nougat soak test, Oct 2016 security patch), .60R (Nougat v7.0, Nov 2016 security patch) or. 62R ( v7.0, Dec 2016 or March 2017 security patches), you're on a Nougat modem. If your baseband is. 48R or a lower version, then you're likely on marshmallow. If you're on a G4, you may not see much difference updating to the N modem if you're using a custom ROM, however for G4 plus devices you will have issues with the fingerprint sensor if you're on a MM modem with a Nougat based custom ROM.
If you want to update to the. 62R modem (the latest version we have), your best best is to flash the stock fastboot ROM. Be aware to back up your data beforehand and move your back up off your device if possible https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
I am on .62R and using the latest package NPJS25.93-14-4. But, I am still facing the fingerprint enrollment issue, can you help me on this?
Bunny 2886 said:
I am on .62R and using the latest package NPJS25.93-14-4. But, I am still facing the fingerprint enrollment issue, can you help me on this?
Click to expand...
Click to collapse
I take it you're on the stock ROM? What device are you running?
What do you mean by fingerprint enrolment issue, as in you can't get more than one fingerprint registered or are you referring to the ghost fingerprint issue as you posted previously? https://forum.xda-developers.com/moto-g4-plus/help/fingerprint-enrollment-issue-t3590634
Xt1643 and that ghost enrollment issue.
Bunny 2886 said:
Xt1643 and that ghost enrollment issue.
Click to expand...
Click to collapse
I'm having difficulty finding reports for others that have had that particular issue (it's usually been users trying to register more than one fingerprint, then having a enrolment error, but the fingerprint is recorded and usable).
I guess you've tried the usual wipe cache/Dalvik and/or a factory reset (of course, back up your data), does the issue still persist?
If it does still persist after a factory reset, then perhaps a re-flash of the firmware is required, is your bootloader locked or unlocked?
No, my bootloader is locked!
Bunny 2886 said:
No, my bootloader is locked!
Click to expand...
Click to collapse
Do you see this issue when you factory reset (if you did that)?
Hmm, in which case if a factory reset doesn't work (by wiping out your existing fingerprint records, then you start fresh), you could take your device to a service centre to re-flash the firmware, see if that fixes the issue (might be a dodgy flash of the modem). With a locked bootloader our options are limited and anything else may require unlocking your bootloader (even downgrading to 93-14) and thus voiding your warranty.
The other way is to ignore the ghost fingerprints (provided they are of your fingerprints), do you still see them listed if you reboot or do a cache/Dalvik wipe?
Yeah, it still persist. I did a factory reset.
Bunny 2886 said:
Yeah, it still persist. I did a factory reset.
Click to expand...
Click to collapse
That suggests an issue with your firmware or device, which a service centre will be able to help you with. I'd suggest asking them to help you with a re-flash, and if that doesn't solve it, perhaps a warranty repair (if you're willing to go down that route).
I flashed March Update with MiFlash Clean all and Lock but I'm able to unlock the bootloader again with the developer settings disabled, that is a big security risk because someone with physical access to the device will be able to unlock the bootloader without permission and maybe decrypt personal data.
I have also noticed similar behavior recently. Great that issue is not specific to me only. Bad it exists.
Hi, after over a year without unlocking my Moto G 5 Plus I'm eager to make the move to unlock and root it. But I've seen that things have changed quite a bit since the last time I rooted my old phone.
As far as I know unlocking the bootloader wipes the DRM keys for ever. What implications does that have? Is there any way to back them up before unlocking to restore them later? What won't work without them?
Will it influence Netflix and Banking apps like Mobilepay (Denmark)? From what I could find out Magisk can help to patch the system without being detected. How does Safety net detect system changes? How to prevent an accidental system change that would break SafetyNet? What about future updates to SaftyNet?
I'm mainly planning to unlock Camera2 API and Miracast. And also install XPosed and some audio enhancement mod if possible. Would any of these break SafetyNet? Would a 64bit ROM break SafetyNet?
Any information is highly appreciated.
Hey guys...I know I posted this in the persist thread, but I figured it might deserve a dedicated post here just in case there's a bigger issue at play or is something that's relatively unknown.
So long story short, unlike many on here I wanted to go back to a stock, locked, unrooted state after being unlocked & rooted (otherwise stock OOS) for a couple months. Unfortunately, upon doing this my fingerprint scanner stopped working (instantly errors with "enrollment was not completed - fingerprint registration error, please try again" when trying to enroll a fingerprint).
So when the guide came out the other day to repair the fingerprint scanner I tried it. I started off by re-unlocking my bootloader (from full stock, locked, unrooted) so that I could grab the persist partition backup that I hadn't done before. After rebooting suddenly, magically my fp scanner started working again. Then after verifying I could enroll several fingerprints, I booted to TWRP (didn't flash it, just booted) and flashed the magisk zip.
After this, I rebooted and backed up my now-working persist.img partition.
I then did a factory reset from the settings menu, which should return the device to 100% stock. After the reset, I verified during initial setup that the fp scanner was still working properly. I then rebooted to fastboot, and upon re-locking the bootloader received a g.co/ABH message in red saying the device was corrupt and that it would not boot.
I then used the latest 10.5.10 MSM tool to re-flash back to full stock again, which caused it to then boot up as expected. At this point, I tested the fp scanner again during initial device setup and it was once again back to not working.
I then re-enabled OEM unlocking in settings and rebooted to fastboot again. Another bootloader unlock. After reboot I tested the fp scanner again during initial device setup. Lo and behold, it's back to working again.
So I stopped midway through the fp enrollment (just hit back, didn't complete) and rebooted back into fastboot mode. Re-locked bootloader again and booted back up. FP scanner again back to not working with the same "enrollment was not completed - fingerprint registration error, please try again" error.
And once again I re-unlocked the bootloader, enrolled a FP during setup, and then used the MSM tool again. After MSM it again produced the same results - FP scanner wouldn't work upon reboot.
And before anyone asks - I am in contact with OP support for either a warranty replacement or a repair...but this whole situation just doesn't make even the slightest bit of sense to me. Basically my FP scanner works perfectly fine with an unlocked bootloader, but any attempt at re-locking it renders it useless. I do have a working persist backup, but obviously can't flash it from a locked state. Anyone else have any suggestions on something to try, or at least have any sort of theory as to why this behavior would be happening? I have never had a phone where attempting to RE-lock the bootloader has been such a freaking pain.
No one has any idea on this, or theories as to what could be taking place and causing this? OP support has been a total trainwreck so far.
Hi, Did you get a solution for this ? I am facing the same issue of fingerprint sensor not working after relocking the bootloader, although in my case I did not have to reflash the persist img. It works when unlocked and stops working when locked. As usual OP after sales are not really helpful. Thanks
Greetings,
same issue here.. has anybody an answer to this problem? It's driving me crazy...
Thank you very much!
shakathesaint said:
Greetings,
same issue here.. has anybody an answer to this problem? It's driving me crazy...
Thank you very much!
Click to expand...
Click to collapse
I've been trying to solve this issue today, as we speak. However, it seems like the guide to restore the FP reader does not apply to our phone (I have the OP8, but it behaves exactly the same) because we still need root to restore the FP reader, and it will be lost upon relock. In other words, we are stuck. OEM repair/replacement seems to be the only solution.
AarSyl said:
I've been trying to solve this issue today, as we speak. However, it seems like the guide to restore the FP reader does not apply to our phone (I have the OP8, but it behaves exactly the same) because we still need root to restore the FP reader, and it will be lost upon relock. In other words, we are stuck. OEM repair/replacement seems to be the only solution.
Click to expand...
Click to collapse
I'm glad there's someone else who's trying to figure it out!
I'd like to do two more tests, but I can't until this weekend since I'm out of town.
But maybe you already tried and it doesn't work anyway:
Since the md5 checksum of "persist.img" is different whether the lockscreen is set or not, I'd like to unset any kind of lockscreen in Oxygen's settings before relocking the bootloader, in order to see if it makes any difference;
if 1. doesn't work, try to overwrite "persist.img" in fastboot with an image saved BEFORE relocking the bootloader (it should be fastboot flash persist persist.img).
At the moment I'm out of ideas.
Related, on 11.0.2.2 magisk and unlocked, my fingerprint sometimes won't recognize at all and forces password unlocks. No corrupt persist or delete and re register a finger solved it.
shakathesaint said:
I'm glad there's someone else who's trying to figure it out!
I'd like to do two more tests, but I can't until this weekend since I'm out of town.
But maybe you already tried and it doesn't work anyway:
Since the md5 checksum of "persist.img" is different whether the lockscreen is set or not, I'd like to unset any kind of lockscreen in Oxygen's settings before relocking the bootloader, in order to see if it makes any difference;
if 1. doesn't work, try to overwrite "persist.img" in fastboot with an image saved BEFORE relocking the bootloader (it should be fastboot flash persist persist.img).
At the moment I'm out of ideas.
Click to expand...
Click to collapse
Oh, thank you! I will certainly try!
shakathesaint said:
I'm glad there's someone else who's trying to figure it out!
I'd like to do two more tests, but I can't until this weekend since I'm out of town.
But maybe you already tried and it doesn't work anyway:
Since the md5 checksum of "persist.img" is different whether the lockscreen is set or not, I'd like to unset any kind of lockscreen in Oxygen's settings before relocking the bootloader, in order to see if it makes any difference;
if 1. doesn't work, try to overwrite "persist.img" in fastboot with an image saved BEFORE relocking the bootloader (it should be fastboot flash persist persist.img).
At the moment I'm out of ideas.
Click to expand...
Click to collapse
I'm writing just to update about the tests above: unfortunately neither of them is working, so I'm starting to think there's no other solution than sending the phone to RMA.
Has any one found a solution for this? Im facing exactly the same problem.
So I’m thinking about using MSM Tool to restore my OP8 Pro right now so I can fully update and get my firmware up to date for the new Lineage OS 19.1 builds, however, there isn’t a full update file available for that required update, only an incremental, hence needing to use the application to roll back to older software and apply each incremental. Seeing as I was on Lineage 18 before, I’m not using stock, and my attempt to update things didn’t go smoothly, as half the hardware is malfunctioning in LOS19. So, I’ve got a few questions as I’ve never used MSM Tool before:
1. I’ve read that using it breaks the fingerprint sensor calibration after the restore. I have a backup of my persist partition which should help me with fixing that, but it seems that root is required to fix that. Is it also possible to just take my backed up persist partition and write it back using fastboot to fix the issue? I know there’s already a set of instructions but I’m not sure if there’s perhaps an easier way.
2. Should I have to root to fix that partition, would that break my ability to install OTAs? If I recall, unlocking the bootloader stops OTAs from working.
Basically, what’s the best path to take such I can ensure my fingerprint scanner still works, but I can fully update the stock software so I can meet the requirements of the new Lineage update? (Perhaps be able to keep the bootloader locked after all is said and done to ensure everything is 100% stock again)