[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor

Were you successful?


  • Total voters
    86
Search This thread
I think maybe try to extract data and engineermode files from the backup persist.img and try again
is this gonna work?
i also got a persist.img backup from when everything used toi work, latest updated ****ed up FP.
Curious how to restore the working files

EDIT: Doesnt work, just gave it a try
 
Last edited:

Extreme_Ninja2099

Senior Member
Jan 1, 2017
616
293
OnePlus 3
OnePlus 6T
is this gonna work?
i also got a persist.img backup from when everything used toi work, latest updated ****ed up FP.
Curious how to restore the working files

EDIT: Doesnt work, just gave it a try
Have u tried re-calibrating the fingerprint, then transfer the old files from your persist.img and keep just the gf_persist.so file (Don't replace it with the same file name from your persist.img)? This worked for me
 
Have u tried re-calibrating the fingerprint, then transfer the old files from your persist.img and keep just the gf_persist.so file (Don't replace it with the same file name from your persist.img)? This worked for me
well no, just extracted data and engeniermode folder and replaced it in persist folder on phone.
withg old files you mean the files extracted from the working persist.img ?
 

Extreme_Ninja2099

Senior Member
Jan 1, 2017
616
293
OnePlus 3
OnePlus 6T
well no, just extracted data and engeniermode folder and replaced it in persist folder on phone.
withg old files you mean the files extracted from the working persist.img ?
Didn't u read the instructions? that's is what ur supposed to do... Try replacing the files except for gf_persist.so from ur "working" persist.img. But u have to recalibrate ur fod before doing this like stated in the instructions
 
Didn't u read the instructions? that's is what ur supposed to do... Try replacing the files except for gf_persist.so from ur "working" persist.img. But u have to recalibrate ur fod before doing this like stated in the instructions
thanks!
sure i did, but since instructions are for case if you aint have a working backup persist.img., i was not sure which image you was talking about.
thought it might be easier if i have a persist.img from working status.
gonna give it a try tomorrow.
thanks again
 
Didn't u read the instructions? that's is what ur supposed to do... Try replacing the files except for gf_persist.so from ur "working" persist.img. But u have to recalibrate ur fod before doing this like stated in the instructions

i cant find the FP test which is stated. or did i get something wrong?
hope its Optical calibration?

when i hit Optical calibration i get this popup....
 

Attachments

  • Screenshot_2022-06-08-07-46-04-54_40dbc481ca5b738a325e5182fc08a331.jpg
    Screenshot_2022-06-08-07-46-04-54_40dbc481ca5b738a325e5182fc08a331.jpg
    168.2 KB · Views: 144
  • Screenshot_2022-06-08-08-16-15-99_40dbc481ca5b738a325e5182fc08a331.jpg
    Screenshot_2022-06-08-08-16-15-99_40dbc481ca5b738a325e5182fc08a331.jpg
    218.3 KB · Views: 146
Last edited:
i cant find the FP test which is stated. or did i get something wrong?
hope its Optical calibration?

when i hit Optical calibration i get this popup....
just realized i can type in numbers in the popup
anyone an idea what i could do here?
 

Attachments

  • Screenshot_2022-06-08-11-39-37-69_40dbc481ca5b738a325e5182fc08a331.jpg
    Screenshot_2022-06-08-11-39-37-69_40dbc481ca5b738a325e5182fc08a331.jpg
    249.4 KB · Views: 58

Extreme_Ninja2099

Senior Member
Jan 1, 2017
616
293
OnePlus 3
OnePlus 6T
i cant find the FP test which is stated. or did i get something wrong?
hope its Optical calibration?

when i hit Optical calibration i get this popup....
  • Enter Factory Mode as shown in the previous guide. (*#808# in the stock dialer)
  • Swipe over to "Device Debugging"
  • Select "Finger print test"
  • Select "Finger print calibration test (Pure White - 90% Blue)
  • Select "Start Test"
  • Keep on going through the tests (You must hold an object or your finger over sensor on all BUT THE BLACK RUBBER TEST of these test for it to work!)
  • The test will fail and this is what we want. There should be a lot of red lines, if you only have one or two try again.
 
  • Like
Reactions: qriozum
  • Enter Factory Mode as shown in the previous guide. (*#808# in the stock dialer)
  • Swipe over to "Device Debugging"
  • Select "Finger print test"
  • Select "Finger print calibration test (Pure White - 90% Blue)
  • Select "Start Test"
  • Keep on going through the tests (You must hold an object or your finger over sensor on all BUT THE BLACK RUBBER TEST of these test for it to work!)
  • The test will fail and this is what we want. There should be a lot of red lines, if you only have one or two try again.
thanks, but only calibration option i have, is this Fingeg print optical calibration, which gives me this popup when i hit it.
Auto test says "Pass"
 

Attachments

  • Screenshot_2022-06-08-11-36-24-35_40dbc481ca5b738a325e5182fc08a331.jpg
    Screenshot_2022-06-08-11-36-24-35_40dbc481ca5b738a325e5182fc08a331.jpg
    195.2 KB · Views: 47
  • Screenshot_2022-06-08-11-37-05-96_40dbc481ca5b738a325e5182fc08a331.jpg
    Screenshot_2022-06-08-11-37-05-96_40dbc481ca5b738a325e5182fc08a331.jpg
    114.1 KB · Views: 48
SOLVED!!
I removed all screenlocks, cleared cache, moved data and engeneermode folder, reinstalled update....
dont know what did the trick, but FP is working again.
cheers

EDIT:
Now i know what caused fingerprint no to work.
it was "Universal Savetynet fix" Magisk module.
but there is also a solution module for this issue.
 
Last edited:
  • Like
Reactions: raymann89

ziedje

Senior Member
Feb 28, 2014
117
26
Dhaka
SOLVED!!
I removed all screenlocks, cleared cache, moved data and engeneermode folder, reinstalled update....
dont know what did the trick, but FP is working again.
cheers

EDIT:
Now i know what caused fingerprint no to work.
it was "Universal Savetynet fix" Magisk module.
but there is also a solution module for this issue.
Thank you bro, I was afraid I had to reset my device, but the module fixed it.
 
  • Like
Reactions: SchWeinSAuG

faysal0

New member
Apr 27, 2018
3
0
New video guide below

VIDEO GUIDE


1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device.

*IF YOU LOOSE THIS PERSIST.IMG BEFORE WE MODIFY IT WITH A CALIBRATION, YOU LOOSE ALL CHANCE OF FIXING THIS YOURSELF*

*IT HOLDS IMPORTANT FP CALIBRATION DATA THAT WE WILL BE OVERWRITTEN IN THE NEXT FEW STEPS*

Note: This requires root​

Type this into terminal or ADB shell with root privileges.
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img

Backup the partition to another device. Preferably a PC as you may need one in the later steps.

2. Next we have to restore our OS to an earlier OOS. (10.5.4 is what I used and recomended)

Use the MSMTool to restore your device to 10.5.4.​
Note: You will loose your unlocked bootloader and will be required to unlock your bootloader once more.​

Guide and Source for MSMTool
MSMTool 10.5.4 Download

3. Next step is to unlock the built in 'Factory Mode' I have a guide on how to do this below.

[GUIDE] Unlock Factory Mode *root*

4. Now we need to perform a FP calibration. We want to fail.

  • Enter Factory Mode as shown in the previous guide. (*#808# in the stock dialer)
  • Swipe over to "Device Debugging"
  • Select "Finger print test"
  • Select "Finger print calibration test(Pure White - 90% Blue)
  • Select "Start Test"
  • Keep on going through the tests (You must hold an object or your finger over sensor on all BUT THE BLACK RUBBER TEST of these test for it to work!)
  • The test will fail and this is what we want. There should be a lot of red lines, if you only have one or two try again.

5. We need to extract the the old broken persist.img
NOTE: It is important that we extract the backed up persist.img as it has been unmodified by our recent calibration. This persist.img although broken still has all our working calibrations on it including Finger Print calibrations.

The way I did this is by opening it extracting it via 7-ZIP on my PC​

Once extracted move the 'DATA' folder and the 'ENGINEERMODE' folder to the root of your sdcard.​


6. Download a root explorer. I highly recommend 'Solid Explorer' from the Play Store.

  • Open 'DATA' folder and delete 'gf_persist.so'
  • Select the 'DATA' and 'ENGINEERMODE' folders you just put on the device and place them at /mnt/vendor/persist/
  • It should ask you if you want to keep the old or new files. Select to keep the new.
  • Reboot.

7. If you followed all my steps correctly this you should be able to go into settings and add your fingerprints.


Why does this work?

Good question... I think what is happening is something in the persist partition breaks which causes the device to think that the sensor is not calibrated when in fact it still is.
When we start and fail a new calibration this fixes whatever was broken in our partition. But now we have a failed calibration.
So what we do is take the files from our backed up persist partition and move over all the necessary files that have our original calibration. But now our partition has the part of it that wasn't working fixed.

I spent a good many days working on this fix (1-2 hundred hours or so). I hope you can be respectful if you have issues. Please kindly ask below and I'll do my best to help.
Does this formula and msm tool apply to op7t?
 

PeachMode

New member
Apr 22, 2016
1
0
Hello!
I had my screen replaced and now my fingerprint sensor doesn't work properly. It still detects fingers and lets me register new fingerprints but it seems to be offset a bit. Does this tutorial apply to my problem? I tried doing the calibration test in engineering mode and follow the steps but I don't have the proper tools for the rubers so it failed some bits of the calibration.
 

parcou

Senior Member
Jun 7, 2008
1,462
196
TN
SOLVED!!
I removed all screenlocks, cleared cache, moved data and engeneermode folder, reinstalled update....
dont know what did the trick, but FP is working again.
cheers

EDIT:
Now i know what caused fingerprint no to work.
it was "Universal Savetynet fix" Magisk module.
but there is also a solution module for this issue.
Thank you....I was about the downgrade, wipe, and redo my entire device and this simple fix worked.
 
  • Like
Reactions: SchWeinSAuG

Avneeshan

New member
Jul 15, 2022
3
0
hi i am facing a issue after flashing custom rom fails. That the fingerprint is working and it glowing light in screen but it not taking the reading(no improvement in enroll progress). I tried with deleting and flashing the persist file but no improvement. Can you help me with it. https://t.me/T4Tamilan this is my telegram account please help me with this.
 

Avneeshan

New member
Jul 15, 2022
3
0
hi i am facing a issue after flashing custom rom fails. That the fingerprint is working and it glowing light in screen but it not taking the reading(no improvement in enroll progress). I tried with deleting and flashing the persist file but no improvement. Can you help me with it. https://t.me/T4Tamilan this is my telegram account please help me with this.
i am having realme 7 pro rmx2170
 

dlads

Senior Member
Aug 24, 2010
16,715
6,436
Liverpool
Nothing Phone 2
Sort of done the same thing on my 10 pro.

Hoping this could fix my phone too, really miss my 8 pro with I'd never got this turd.

Do you think this method would work?

Proximity,, brightness sensor, compass all missing.

Fingerprint still working
 
  • Like
Reactions: ps000000

skyraven83

Senior Member
Apr 27, 2014
61
5
Does anyone have a valid Oneplus 8 Pro European version persist.img that I can flash?
Or any other method that does not involve flashing everything and losing everything?

Currently my fingerprint works only if I go in the Engineering Menu and then at the end I specify the test has failed (there's a button that asks me on the newer version).
I use *#899# to access it and 6776 then to do the calibration.
This workaround lasts until the next reboot..so there has to be some local file that if I delete/replace then the setting remains after reboot.

Anyone, any clue?

p.s. already used msm tool and lost most of my stuff once as while trying to remediate the fingerprint I followed a thread that told me to delete locksettings.db. After that one the sdcard did not mount anymore... and later I managed to brick my device => EDL + MSM.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 66
    New video guide below

    VIDEO GUIDE


    1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device.

    *IF YOU LOOSE THIS PERSIST.IMG BEFORE WE MODIFY IT WITH A CALIBRATION, YOU LOOSE ALL CHANCE OF FIXING THIS YOURSELF*

    *IT HOLDS IMPORTANT FP CALIBRATION DATA THAT WE WILL BE OVERWRITTEN IN THE NEXT FEW STEPS*

    Note: This requires root​

    Type this into terminal or ADB shell with root privileges.
    Code:
    dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img

    Backup the partition to another device. Preferably a PC as you may need one in the later steps.

    2. Next we have to restore our OS to an earlier OOS. (10.5.4 is what I used and recomended)

    Use the MSMTool to restore your device to 10.5.4.​
    Note: You will loose your unlocked bootloader and will be required to unlock your bootloader once more.​

    Guide and Source for MSMTool
    MSMTool 10.5.4 Download

    3. Next step is to unlock the built in 'Factory Mode' I have a guide on how to do this below.

    [GUIDE] Unlock Factory Mode *root*

    4. Now we need to perform a FP calibration. We want to fail.

    • Enter Factory Mode as shown in the previous guide. (*#808# in the stock dialer)
    • Swipe over to "Device Debugging"
    • Select "Finger print test"
    • Select "Finger print calibration test(Pure White - 90% Blue)
    • Select "Start Test"
    • Keep on going through the tests (You must hold an object or your finger over sensor on all BUT THE BLACK RUBBER TEST of these test for it to work!)
    • The test will fail and this is what we want. There should be a lot of red lines, if you only have one or two try again.

    5. We need to extract the the old broken persist.img
    NOTE: It is important that we extract the backed up persist.img as it has been unmodified by our recent calibration. This persist.img although broken still has all our working calibrations on it including Finger Print calibrations.

    The way I did this is by opening it extracting it via 7-ZIP on my PC​

    Once extracted move the 'DATA' folder and the 'ENGINEERMODE' folder to the root of your sdcard.​


    6. Download a root explorer. I highly recommend 'Solid Explorer' from the Play Store.

    • Open 'DATA' folder and delete 'gf_persist.so'
    • Select the 'DATA' and 'ENGINEERMODE' folders you just put on the device and place them at /mnt/vendor/persist/
    • It should ask you if you want to keep the old or new files. Select to keep the new.
    • Reboot.

    7. If you followed all my steps correctly this you should be able to go into settings and add your fingerprints.


    Why does this work?

    Good question... I think what is happening is something in the persist partition breaks which causes the device to think that the sensor is not calibrated when in fact it still is.
    When we start and fail a new calibration this fixes whatever was broken in our partition. But now we have a failed calibration.
    So what we do is take the files from our backed up persist partition and move over all the necessary files that have our original calibration. But now our partition has the part of it that wasn't working fixed.

    I spent a good many days working on this fix (1-2 hundred hours or so). I hope you can be respectful if you have issues. Please kindly ask below and I'll do my best to help.
    2
    This didn't work for me. My wifi and bluetooth are also not working so @dladz thought that fixing the fingerprint issue may help with wifi/bt.

    Precise log of the steps I took, after I took them.
    1. Factory reset using MSM tool-10.5.4
    2. Oem unlock
    3. Install MMv805 (stable channel)
    4. MM: Patch boot.img
    5. Flash boot_patched.img
    6. Backup persist.img to PC
    7. Extract persist.img files/folders
    8. Copy data/ and engineermode/ to phone/Download
    9. Phone: delete phone/data/gf_persist.so
    10. SKIP /mnt/vendor/persist/engineermode/engineermode_config first 2 lines already set to false
    11. Start fingerprint calibration
    12. Keep finger OFF sensor for Black rubber test
    13. Test successfully failed (several pages worth of red lines; last line: FAIL:GF_ERROR_PRESS_INCOMPLETE)
    (did not reboot)
    14. Copy data/ and engineermode/ over to /mnt/vendor/persist/ (merge, remember; new, remember **I didn't like this part, would have prefered to delete these folders. What do you recommend?)
    15. Reboot
    16. Fail fingerprint setup: Enrollment was not completed. Fingerprint registration error, please try again.

    This was my forth or so attempt. This last attempt (the one posted above), however, I deleted all previous .imgs/persists/everything and started from scratch just to be safe. Model of my device is IN2025.

    Did I go astray somewhere? Please see step 14.

    Thanks for this guide!
    2
    It's great that somebody finally figured it out! I spent many hours trying so, analyzing persist partition, but I gave up. So I need to have unlocked bootloader? I'm rooted and unlocked already, my fp is fine (lost it earlier but restored my own persist backup), but I want to lock bootloader and I'm afraid of this fp issue to come back to me once more.
    So for now it's impossible to relock bootloader without losing fingerprint scanner?
    2
    I've just been brainstorming a potential way to keep the fingerprint working after we re-lock our bootloaders (Haven't tested it at all though, just ideas right now).

    As you know, the MSM tool uses a file ending in the extension ".ops", for example, "instantnoodlep_15_E.34_210201.ops" and this is around 6.5GB in size and contains all of the partitions/data required by the tool to unbrick a OnePlus device.

    Now, there's a tool on GitHub that allows you to decrypt .ops files, so that you can see each file inside of it (A bit like extracting a zip file for example). The tool is located here - https://github.com/bkerler/oppo_decrypt.

    The tool also allows you to re-compile the individual files back into a .ops file once you have finished doing whatever changes you want to them.

    So, if we are able to extract the .ops file, replace the persist file with our working one and then re-compile the .ops file and use it to restore our phones via MSM it would hopefully use the working persist partition AND re-lock the bootloader at the same time.

    I no longer have a OnePlus 8 Pro so I can't test this but thought it might help for anyone willing to investigate it further.

    (Happy to be told this idea is stupid and won't work by the way, I won't be offended!).

    EDIT 1: I've also stumbled across this thread in the OnePlus 7 Pro section where people are trying to do a similar thing but with a different goal - Having a magisk patched boot.img on a locked bootloader. They've been able to edit the files and re-flash them using MSM tool. It looks like this definitely could work for our persist partition issue for anyone willing to try it.

    EDIT 2: Another thread to read through with a similar idea and some success for what they were trying to achieve (They can flash a different ROM version with a locked bootloader).
    2
    @antnyhills this is great work! But I assume you need to use device spesific persist.img? Even if its broken. I needed to rma mine because changing my display at service center broke my FP. And I think that even that I had backed up working persist.img it some how thinked that my device was different caused by different ID on a display? I tried to ask but no-one knew for sure..And that was result after talking to customer service dude who I spoke same language with..

    Correct, you need your personal persist.img

    Even though it is broken it still has all over your original factory calibrations including the fingerprint calibrations.