yashsingh1/xdaforums huggingface dataset:
[OnePlus 8 Guides, News, & Discussion] starcms:
Ok, so apparently there is no way to relock the bootloader with a "fixed" persist because the checksum doesn't match and relocking causes FP file in persist to corrupt again. So either stay unlocked and use the fixed persist; or run MSM tool and RMA device for fingerprint calibration, make a backup of persist as soon as you get it back, and then if persist gets corrupted, you'll have a backup of the original persist with matching checksum which will allow you to restore it if it gets corrupted and relock the bootloader without it automatically being corrupted.
[OnePlus 8 Guides, News, & Discussion] dzontra83:
I think I got permission denied because It cannot be done over adb shell, without su. The fixed persist works as a charm, I restored it on my device, just on unlocked bootloader and with root - su. I also couldn't backup my persist without su, with adb shell I got permission denied also
[OnePlus 8 Guides, News, & Discussion] starcms:
I must be missing a step. Did you try it from inside Android with ADB debugging enabled instead of in recovery? Because I'm positive it's possible to at least backup persist with the bootloader locked (no root obviously). I was pretty sure it could be restored as well...

Edit: Persist can definitely be backed up with bootloader locked by using MSM tool in EDL mode and pressing F8 to select partitions to be backed up. Still not positive about restoring it with bootloader locked...
[OnePlus 8 Guides, News, & Discussion] dzontra83:
Did not know about that in msm, still, I did not find any solution to restore it without root, can msm restore or flash only a certain partition?

Edit: I tried your way but I couldn't do anything in recovery, adb did not register my phone at all. Are you Shure adb works in recovery?
[OnePlus 8 Guides, News, & Discussion] starcms:
Msm can only backup individual partitions, not restore them.

Adb most definitely works in stock recovery. I think that is where your issue is. Make sure you are using the absolute newest adb and fastboot versions from Google on your PC and also that your phone shows up correctly in device manager on your PC while in recovery. Might need newer drivers also.
[OnePlus 8 Guides, News, & Discussion] dzontra83:
Could you send me the link to latest drivers, and ADB tools you are using? Definitely I can't see my device at all when in recovery it isn't showing in device manager, but when device is powered on ADB works, and when in bootloader fastboot works. I tried booting into TWRP and ADB works then, but as I reboot back to stock recovery, it doesn't, very strange. Thnx
[OnePlus 8 Guides, News, & Discussion] ecompton59:
i fixed my one+8 5g by flashing beta that fixed network then downgraded and network fixed
[OnePlus 8 Guides, News, & Discussion] QuiDC96:
I'm confused...

If I backup the brocken persist.img and put it on the new fresh firmware it's have to still be brocken or not because the file is brocken and useless?

I believe that after I use the MSM tools its wipe all brocken/corrupt files and give me a new/unmodified persist.img that works.

Can someone explain that magic?
[OnePlus 8 Guides, News, & Discussion] starcms:
The MSM tools don't touch persist. If it's corrupt, it cannot fix it. Once you follow the directions to fix the FP, the fix will persist through OTA updates.

HOWEVER, when relocking the bootloader, which the MSM tool does automatically, it somehow determines that the "fixed" persist is not the original one, and therefore corrupts persist again. So keep a copy of your fixed persist with FP working, and therefore if you ever run the MSM tool (or otherwise relock the bootloader), you'll still have it so it can be restored.

At the current time, it is not possible to relock the bootloader (including running the MSM tool) and keep FP working if you fixed it via this guide.
[OnePlus 8 Guides, News, & Discussion] QuiDC96:
What if I never unlocked the bootloader before and I want to downgrade via MSM tools. So is there a guide to back up the persist in locked bootloader?
[OnePlus 8 Guides, News, & Discussion] starcms:
If you never unlocked the bootloader and don't intend to, nothing to worry about.
[OnePlus 8 Guides, News, & Discussion] shaneg79:
This guide no longer works for the new T-Mobile update that provides standalone 5G. I tried it with no success. It did work on the previous update that had the June security update.
[OnePlus 8 Guides, News, & Discussion] Tech_Wun:
..

---------- Post added at 08:49 AM ---------- Previous post was at 08:33 AM ----------

I've been having the same issue. Did you have any luck?
[OnePlus 8 Guides, News, & Discussion] starcms:
I'm finding this hard to believe. Persist is never touched by OTA updates.

Never ever, ever. And it's not modified by the MSM tool either (although running the msm tool or otherwise relocking the bootloader will cause persist to become corrupted again). Did you restore a backup of your fixed persist? Did you remember to make one in the first place?

Maybe factory mode/calibration tool was updated in latest OTA and isn't working anymore and you need to revert to an older version of OOS as mentioned in step 2. But if you had backed up your fixed persist, all you would need to do is restore it. Even after not having taken a backup b4 persist was first corrupted is understandable, all of us in this thread did it, but then not learning from that mistake and not taking a backup of the fixed persist either? Come on...

---------- Post added at 07:49 ---------- Previous post was at 07:46 ----------

Permissions were fine/not the issue. I eventually just programmed my thumb and forefinger twice each (the only 2 fingers I use) with a perfectly clean screen and clean hands, and it unlocks on first try 95% of the time, from ambient, lock screen, and inside Android. It learns also, so the more you use it, the better it'll get. But just so you can double check, see pics for correct permissions for /persist/data. Some files/file names may differ slightly from yours. This is from my T-Mobile 7T Pro 5G McLaren, not OP8, but the instructions worked perfectly for me, and I'm positive the permissions are the same.
[OnePlus 8 Guides, News, & Discussion] starcms:
... duplicate post...
[OnePlus 8 Guides, News, & Discussion] TheKnux:
What is the file manager you're using in the screenshots above?

---------- Post added at 09:42 PM ---------- Previous post was at 09:41 PM ----------

+1
[OnePlus 8 Guides, News, & Discussion] shaneg79:
I finally got it to work I had to make a new persist backup on the previous update that ended in .10 then updated to .17 and it works not sure why that made a difference.
[OnePlus 8 Guides, News, & Discussion] starcms:
FX File Explorer
[OnePlus 8 Guides, News, & Discussion] starcms:
To [MENTION=4275707]TheKnux[/MENTION] and [MENTION=7967584]Tech_Wun[/MENTION] and anyone else that thinks after fixing the FP sensor, it doesn't work as well on ambient display and the unlock screen, but works perfectly fine in any/all apps once phone is unlocked:

Could you please check in /mnt/vendor/persist/data and check when the file gf_persist_unlock.so file is dated (was last modified)? Is it dated the same as all other files in /mnt/vendor/persist/data except for gf_persist.so?

If you open /mnt/vendor/persist/engineermode/fpcalibrationresult in any text viewer, you'll see the results of the fingerprint calibration done at 1+ when the phone was built. The very first line has the date and time this was done. This date should match all the files in /mnt/vendor/persist/data except for gf_persist.so.

However, in my case, gf_persist_unlock.so has a much newer date, which matches the date of gf_persist.so, which is the date I fixed the FP sensor thanks to [MENTION=4781115]antnyhills[/MENTION] (thank you sooo much for all the time you spent figuring this out!!!)

In my case, I'm pretty sure that is because before these genius instructions came out, I was messing around with *#808# and fingerprint calibration, trying to fix it, unsuccessfully, and wound up modifying/breaking gf_persist_unlock.so and didn't have a backup. However, I'm not positive that's what happened.

But considering the name of the file, and both of you not seeing the same reliability of the FP scanner at the lock screen as b4 breaking it in the first place, it would make sense that somehow your gf_persist_unlock.so got modified/corrupted as well.

So could you check the dates and let me know?

It's really a moot point tho. Even if your gf_persist_unlock.so somehow got modified/corrupted, they'd be no way to fix it without RMA to 1+. I'm just so happy to have my FP working again. If it's not quite as reliable at the lock screen, so be it. Much better than being without my phone for a few weeks or longer because I had to RMA it. It definitely works the majority of the time at ambient and lock screen after programming the same finger twice and giving it a week or so to auto calibrate/work even better. And once unlocked, it works 100% perfect, just like new.
[OnePlus 8 Guides, News, & Discussion] TheKnux:
[MENTION=2557531]starcms[/MENTION] if you're on Telegram, shoot me a PM. Same username as on here.
[OnePlus 8 Guides, News, & Discussion] vinayak.s19:
I followed the guide and got to the factory mode.

When I try to start the finger print calibration test, I get the following error: "The application cannot reach the android service for the sensor."

I am using the OP8 Indian Version.

Help!!!!

Edit: Fixed it by skipping the calibration test and restoring the FP data and then updating to the latest stable.
[OnePlus 8 Guides, News, & Discussion] ryanrodio:
Working for me without using MSM

I was able to backup my old persist, and perform the failed calibration test and folder merge all without downgrading.

I'm using the T-Mobile variant that is currently on the latest global build. Not sure if I was just lucky or if there is a possibility of not having to downgrade first.

Also, after breaking my FP, i never attempted to go into factory calibration mode to try and fix the problem until I began following the instructions in this thread.
[OnePlus 8 Guides, News, & Discussion] shaneg79:
Something interesting happened today, I decided to install Android 11 developer preview 4 and I decided not to root but I noticed my fingerprint scanner is working without being rooted which is strange I wonder if somehow I could go back to 10.5.20 and get fingerprint working again without root?
[OnePlus 8 Guides, News, & Discussion] naveedakhter01:
Error saving calibration

I was getting only getting 2 line of errors instead of multiple lines when calibrating. Messing around, I clicked on reliability test. Calibration was done in the same way and it finally worked *phew*.

P.S. this method does not work on 10.5.11. MSM to 10.5.4
[OnePlus 8 Guides, News, & Discussion] starcms:
That's clearly mentioned in the OP.
[OnePlus 8 Guides, News, & Discussion] dijia1124:
Thanks for your great work!

I got a strange problem that may not be related to persist.img. After flashing custom kernels ( tried cleanslate and ex kernel) on my Oneplus 8 (OOS 10.5.12.IN21AA) , the whole fingerprint feature seems to be missing: I just can't unlock my phone with fingerprint, nor can I find it in Settings. But it recovers if I restore the stock kernel.
[OnePlus 8 Guides, News, & Discussion] barisgg:
Worked for me! Thanks for the video! I lost my finger print after flashing global on my t-mobile phone, after I fixed it I made sure to have a fingerprint registered before flashing global again, didn't have the same problem again!
[OnePlus 8 Guides, News, & Discussion] risay07:
Hi [MENTION=4781115]antnyhills[/MENTION], my OP6T encounters the same error. Since the issue was caused by corrupted persist partition, do you think flashing persist partition extracted from Stock Fastboot rom via fastboot would fix it?

Edit: I have proceeded according to the instruction. The finger print calibration test fail early for me. It says:

SPI

PASS!

PASS: FLASH ID: (7 numbers),SENSOR ID: (4 numbers),MCU ID:2,PMIC ID: (4 numbers)

MT_CHECK

FAIL!

FAIL:GF_SZ_FT_ERROR_CHECK_MT_FAIL

Anyone knows what MT_CHECK means and why it fails?
[OnePlus 8 Guides, News, & Discussion] totmakina:
Hello :

I lost my fingerptomy of unbrick the oneplus 8 from MSM 10.5.9. When closing the boot I lost the track.

What I did to try to fix it was:

- Re-flash with MSM 10.5.8

-When starting the mobile I skipped all the configuration

-Go directly to developer options and activate OEM unlock and USB debugging.

. Connect the mobile to the PC and put the mobile in fastboot mode.

. Unlock by fastboot and reboot

- Agira at this time YES, start configuring the mobile including the fingerprint.

- After updating via OTA the oneplus until 10.5.12

In this way I was able to solve the loss of fingerprint

In this way I was able to solve the loss of footprint

Hope this can be of use to someone.

Thank you
[OnePlus 8 Guides, News, & Discussion] VinDw:
How to get root access to copy persist.img file

Hi there,

I'm using a OnePlus 8 (IN2010) and my fingerprint stopped working around a week ago. I'm new to this stuff & would really appreciate if someone could link me to a working method to root my device as this tutorial states that root it required.

Also, will using a OOS downgrade package do any alterations to my persist.img file?

Many thanks!
[OnePlus 8 Guides, News, & Discussion] greendragon527:
Hey man, I got the same error as you, did you fix by just copying the data from your old persist.img again?
[OnePlus 8 Guides, News, & Discussion] greendragon527:
So update, I got through with a later version of the tool, and my fingerprint reader is perfect now. Many thanks to the OP!:D
[OnePlus 8 Guides, News, & Discussion] BOHEMIA840:
Please explain how to backup our working "Modem" partition? [MENTION=4781115]antnyhills[/MENTION]
[OnePlus 8 Guides, News, & Discussion] antnyhills:
That's unrelated to my fix. If you want to find a guide look around for a thread that goes over that.
[OnePlus 8 Guides, News, & Discussion] The_Anomalist:
I tried this over and over again and I still can't get it to work. I'm now on a11 and feel I'll never have my fingerprint back again.
[OnePlus 8 Guides, News, & Discussion] GinoTonny:
Send it to Oneplus technical service. I sent it and applied warranty, they re-calibrate the fingerprint reader.
[OnePlus 8 Guides, News, & Discussion] starcms:
Root or no root has no effect on it working. If you relock the bootloader (manually or by running the MSM tool), and had applied the fix in this thread, you'll lose FP again. I'm assuming this is because the phone checks persist at that time and the checksum doesn't match the expected one so it corrupts the FP data again.

If you used this fix:

A) FP will work only with an unlocked bootloader.

B) Relocking the bootloader breaks FP again (it can be unlocked and fixed again. Very very easy if you made a backup of your fixed persist partition which I highly, highly recommend)

So it's impossible to have both FP working and a locked bootloader if you used this fix.
[OnePlus 8 Guides, News, & Discussion] Saeem:
Is there no permanent way to fix it? & Does it effect everyone who rebranded OnePlus 8?
[OnePlus 8 Guides, News, & Discussion] starcms:
The only way to permanently fix it (meaning FP sensor working with bootloader locked) is to run the MSM tool and then RMA to OnePlus asking for fingerprint recalibration. Or RMA it with a picture showing the FP error message. Believe it or not, this has occured to people who never unlocked their bootloader. And never modded their phone one bit.

If you back up your persist.img immediately when you first get the phone back before even unlocking the bootloader, you can easily restore it if/when it gets corrupted again. And not have this issue. I'd recommend backing it up even if you don't plan to unlock the bootloader again because it has happened to people that never did...

Rebranding didn't cause it. Unlocking the bootloader combined with dozens of possible different things most likely caused it.

The whole issue is due completely to OnePlus's incompetence, A10 and the new dynamic file system, OnePlus not fully understanding how it works, and putting persist in an "open" area of the phone. Instead of locking it down and making it virtually impossible to corrupt. As I said, it can even become corrupt even if the bootloader has never been unlocked...
[OnePlus 8 Guides, News, & Discussion] Saeem:
I'm having a chinese OnePlus 8 & there no way I'll be able to claim the warranty without sending it to China unless it has international warranty, which it probably doesn't have. I tried looking for authorized service centers of OnePlus & even contacted Amazon who is an authorized seller of OnePlus in UAE, they said they won't be able to do a thing in Saudi Arabia even if I have bought this device from them as I do not have the Order ID, they do not know anything about IMEI like other sellers. ?

I'm good with unlocked bootloader but I hate the fact that Fortnite has some super power to detect unlocked bootloader even with magisk hide & everything, 90fps just doesn't work & the graphics quality is poor.

Can a system update from OnePlus fix this problem or does OnePlus have any way to fix it remotely?
[OnePlus 8 Guides, News, & Discussion] Vomitblood:
Request for persist.img for OnePlus 7T Pro

Hi there, my OnePlus 7T sensors are not working.

I have found a persist.img for OnePlus 7T Pro and flashed it.

That solved the problems for all the sensors EXCEPT for this fingerprint sensor.

The persist.img's data folder only has 8 files, and it does not contain 'gf_persist.so'.

I suspect that it is not a complete persist.img, although it seems to have fixed all the other sensor problems.

May I request for another persist.img file?

Thanks.
[OnePlus 8 Guides, News, & Discussion] starcms:
You need the persist.img from your actual phone if you have any hope of fixing FP without RMA. So, your only option at this point is RMA.
[OnePlus 8 Guides, News, & Discussion] starcms:
No...and fortnite runs fine here using MagiskHide...
[OnePlus 8 Guides, News, & Discussion] Saeem:
Can you tell me how you managed to do it?

I did some digging & found a lot of people are having this problem of fortnite not running properly on their unlocked device. I used to get kicked out of the game, which i manage to fix using magisk hide & disabling developer mode. Sadly now my graphics is terrible (3D games of 2005 are better) & I cannot exceed 60fps even when i set 90fps to be the default. ?
[OnePlus 8 Guides, News, & Discussion] zizzyboi:
Do i need to lock factory mode after or not needed?
[OnePlus 8 Guides, News, & Discussion] succumbtothegreater:
Thank you so much for this guide!!! I broke my screen and replaced the screen/frame myself and when I booted up, I had no use of the fingerprint scanner. It said "Fingerprint Hardware Not Available". After following this guide, I'm able to use it again!
[OnePlus 8 Guides, News, & Discussion] PP1723:
Same problem for me. if Bootloader is unlocked the FP is working fine, but if I relock the bootloader I got the FP enrollment error. What's wrong with Oneplus? Do you think they manage to fix this problem? Otherwise I think I will sell my phone and switch to Xiaomi
[OnePlus 8 Guides, News, & Discussion] mrshahriar:
Brother have the save device and the same problem, i couldn't find "gf_persist.so" file, Did you get any solution? Or could you give me the persist files you have? It will be a great help brother, you can contact me through my mail - mahi2723shahriar@gmail.com
[OnePlus 8 Guides, News, & Discussion] mrshahriar:
What is RMA?
[OnePlus 8 Guides, News, & Discussion] ccgauvin94:
Has anyone been able to do this on LineageOS? When I run the *#808#, I get a popup saying "Connection problem or invalid MMI code"
[OnePlus 8 Guides, News, & Discussion] afiqz1996:
i followed every step, but in my backed up persistent img only have this file in persistent/data :

my device is OP7T. i tried calibrate using *#808#. it didnt work.

*i can enroll my fp but i cannot unlock the device from lock screen. fingerprint not recognize
[OnePlus 8 Guides, News, & Discussion] shakathesaint:
Thanks for the explanation. My phone has exactly the same problem you described.

I'm just wondering, since it's been a while since your post, if in the meanwhile some new solution has possibly been found to avoid the need of RMA.

Thank you very much! :giggle:
[OnePlus 8 Guides, News, & Discussion] jiehao258:
帮顶了，嘿嘿
[OnePlus 8 Guides, News, & Discussion] waleedbinwaheed:
Hi All respected seniors!

can anybody please explain procedure for original persist.img backup. I have a TMO 7T PRO Mclaren and after bootloader unlock at android 11 after magisk i took all partition backup including then working finger print persist.img but after installing several magisk mods one day i woke up with no fingerpring hardware error. now i have my original persist.img at hand. i also backed up this corrupt fp persist.img.

every one here has workaround for broken persist.img but i want to know the restoration method of original woking persist.img backed up before any sensor issues..

please help!
[OnePlus 8 Guides, News, & Discussion] starcms:
Simply take your backed up, original, persist.img, go to bootloader, and type

fastboot flash persist name_of_backup.img

And you'll be good as new. I recommend deleting the backup of the corrupt fp persist.img so you don't get them mixed up.

And if/when it ever happens again, simply do the same. Make sure you never ever ever lose that backup copy of original, uncorrupted persist.img
[OnePlus 8 Guides, News, & Discussion] waleedbinwaheed:
First of all thanks for your swift response!

Dear when i try to flash persist.img from bootloader it gives error saying its a critical partition and fastboot command not allowed, done on unlocked bootloader but error is same. Im sure this backup of persist.img was taken right away after initial bootloader unlock. So as additional precaution i took backup or broken persist.img also and double checked that both backups were separately stored.

Now for temporary solution i fillowed your guide from other thread and fp sensor is back to life again. But it worked on broken persist.img

But i want to use and learn to flash my original persist.img backup.

Kindly help in this regard.
[OnePlus 8 Guides, News, & Discussion] starcms:
I've never ever, ever seen or heard that error reported. If you unlocked the bootloader using the token from OnePlus and did "fastboot oem unlock", there are no such thing as protected, critical partitions anymore -- hence the problem with persist being able to be so easily corrupted in the first place.

It doesn't matter if the file being flashed is "valid" or not, it will let you fastboot flash any and all partitions with literally any file.

Did you unlock the bootloader using the unofficial instructions and the unofficial MSM package that unlocks the bootloader without using the token from OnePlus and without having the phone carrier unlocked by T-Mobile?

Or did you do it the official way having the phone carrier unlocked by T-Mobile, requesting the unlock token from OnePlus, and used that along with fastboot oem unlock?
[OnePlus 8 Guides, News, & Discussion] waleedbinwaheed:
Yes i understand about unlocked bootloader power of flashing any partition and i have handsome experience of flashing partitions, but this error that i reported, in the first place made me post in this thread. When i rebooted to fastboot and run the command it responded with the error. I will later share screenshot with you also..

Also Im certain that this device is network unlocked because when in settings i tap on network lock it says it is unlocked and can be used with any other carrier.

And yes i bootloader unlocked this device myself after getting unlock token from oneplus after 7 days waiting period and by using cust-unlock flash method..

Should i backup my current working fixed persist.img partition before try again to flash original persist in its place? Would original partition work even after fixing broken persist?

PS i never used any MSM tool on this device uptill this moment. It came with android 10 and officially updated to android 11 OTA. I then bootloader unlocked and magisked it.