I accidentally lost the persist.img and I can't fix the fingerprint issue, even with a custom rom the issue is still here.
Would anyone be able to give me there persist.img file? Thank you
MuhannadYT said:
I accidentally lost the persist.img and I can't fix the fingerprint issue, even with a custom rom the issue is still here.
Would anyone be able to give me there persist.img file? Thank you
Click to expand...
Click to collapse
I'm pretty sure persist.img is unique to each individual's phone so it's not something someone else can give without consequence.
Curious as to what actions you performed that resulted in it being lost?
Artimis said:
I'm pretty sure persist.img is unique to each individual's phone so it's not something someone else can give without consequence.
Curious as to what actions you performed that resulted in it being lost?
Click to expand...
Click to collapse
I bought a device that previously had a custom o, when I installed the original from the fingerprint didn't work. I tried crdroid same issue, anyways it was due to the persist.img being messed up, I tried to fix it but I lost the backup, so basically, the fingerprint sensor no longer works now. I found a backup of it but for the 7pro, But that didn't work as well
Did you try this: https://forum.xda-developers.com/t/...r-with-corrupt-persist-in-15-minutes.4129711/
Related
Just as the title says, after flashing the bootstack, rom and gapps countless times, i still dont have auto rotate or auto brighness. all the sensors seem to be dead except for wifi, gps and mobile network. did anyone else experience this? how did you resolve it??? please help!!
I had the same problem after dirty flashing from 13.1. I did a factory reset and reflashed and all was well.
whoiswes said:
I had the same problem after dirty flashing from 13.1. I did a factory reset and reflashed and all was well.
Click to expand...
Click to collapse
thanks for the reply. i did a clean flash. didnt work.
i flashed the boostack, rebooted back to recovery, flashed the rom and gapps, wiped cache and rebooted. it boots fine. but then i still dont have auto rotate. seems like the drivers werent installed or something
Obvious questions, but did you check the rotation settings inside the display menu? Also, is Adaptive brightness toggled on?
MiMtnBiker said:
Obvious questions, but did you check the rotation settings inside the display menu? Also, is Adaptive brightness toggled on?
Click to expand...
Click to collapse
i did. i installed an app that checks the phones sensors. they are all undetected. i think its a driver issue. i'm at my wits end
crazynitro said:
i did. i installed an app that checks the phones sensors. they are all undetected. i think its a driver issue. i'm at my wits end
Click to expand...
Click to collapse
Check the md5 on your download to make sure it is not bad Install twrp 3.0.4.0 you could also move everything you want to keep to a sdcard so you can do a total wipe. Now install rom and gapps only and check to see how everything works before adding root or apps.
crazynitro said:
Just as the title says, after flashing the bootstack, rom and gapps countless times, i still dont have auto rotate or auto brighness. all the sensors seem to be dead except for wifi, gps and mobile network. did anyone else experience this? how did you resolve it??? please help!!
Click to expand...
Click to collapse
This is an old thread, but I am hoping you found a fix for these issues. I am having the same issue. If you have a solution to share I would greatly appreciate it.
lkiefer said:
This is an old thread, but I am hoping you found a fix for these issues. I am having the same issue. If you have a solution to share I would greatly appreciate it.
Click to expand...
Click to collapse
I lost my phone so i currently have another one. i can t remember what i did to fix it though
crazynitro said:
I lost my phone so i currently have another one. i can t remember what i did to fix it though
Click to expand...
Click to collapse
That's a drag. Thanks for the quick response though.
Hello, I also have an issue with the accelerometer (and by consequence the auto rotate function).
I am on full stock Nougat B09 (no root) and the issue was also present on B06.
Rebooting the device solve the issue, and factory reset does not make this bug disappear.
That being said, I think I located the root cause.
The magnetometer seems to be never working, even after a reboot. When an app wants to use the magnetometer (like Google map, or the compass), it make the accelerometer crash....
Anyone else having this issue ?
Does you magnetometer works flawlessly ?
Thanks.
@arachneon,
Hi, you can change it in the tools---compass, and in that compass you can waggle the phone in the way of "8", if all that cannot fixed you can also seek help in the nearby ZTE after sales service repair center. Thanks!
Hello,
I've been without sensors nor camera for a while now (almost a year), got broken because an OTA update. Tried downgrading, didn't work.
Yesterday I managed to root and install TWRP, did some research and heard about ''persist'' partition. I've been searching for similar cases but no luck. Also tried deleting sns.reg
Can someone provide me the persist.img stock file? So I can finally fix my sensors.
Broken sensors:
Gyroscope
Ambient light
Accelerometer
Proximity
Fingerprint
Camera Flash isn't working either.
Foxxo990 said:
Hello,
I've been without sensors nor camera for a while now (almost a year), got broken because an OTA update. Tried downgrading, didn't work.
Yesterday I managed to root and install TWRP, did some research and heard about ''persist'' partition. I've been searching for similar cases but no luck. Also tried deleting sns.reg
Can someone provide me the persist.img stock file? So I can finally fix my sensors.
Broken sensors:
Gyroscope
Ambient light
Accelerometer
Proximity
Fingerprint
Camera Flash isn't working either.
Click to expand...
Click to collapse
Solved, download the firmware version you have here and look for persist.img. The firmware comes with it but the install script doesn't use it. Just flash it:
Code:
fastboot devices
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot
Hello friend,i have similar problems,apart from fingerprint sensor,all my sensors and cameras,camera light are not working,will i loose imei numbers if i flash the persist img ? i dont know how to flash persist img,can you help me please?
Edit: hi i actually fixed my problem by flashing persist.img, all sensors and cameras are working now
Thank you so much
I would like to thank you for this solution, finally, after 2 days trying I have my ZS570KL alive and working faster, I had to try rooting, then it was bricked for some hours, finally I got it rooted, but after deleting that persist/sensors/and.reg it was the same... until i found this thread, everything works good!!! thank you very much
3sgebeams said:
I would like to thank you for this solution, finally, after 2 days trying I have my ZS570KL alive and working faster, I had to try rooting, then it was bricked for some hours, finally I got it rooted, but after deleting that persist/sensors/and.reg it was the same... until i found this thread, everything works good!!! thank you very much
Click to expand...
Click to collapse
Did you also have broken sensors issue and it is fixed now? I want to try it on my ZS570KL too, but is there a persist.img for this phone?
DIXES said:
Did you also have broken sensors issue and it is fixed now? I want to try it on my ZS570KL too, but is there a persist.img for this phone?
Click to expand...
Click to collapse
Depending on your OS version yes, contact me on Telegram @GuerrillaRadi0 (the last character is zero) maybe I can help you, after I fixed the problem I configured fingerprint security and the problem came back, so I tried to flash persist.img again and it didn't work, so I got the raw rom of the Oreo version I have; WW-15.0210.1810.73, which comes with its own ADB, and flashed from there, the same raw rom has the persist.img. After that all sensors worked again, so I configured fingerprint security again just to be sure, and again I lost all the sensors, but after deactivate fingerprint again everything worked fine, I guess I have some hardware issue related to fingerprint sensor, I guess it was because a technician opened the phone to replace screen and battery 2 months ago. I always used fingerprint so I need to go back to pattern.
Good luck
After some days without any issue the problem came back, I flashed persist.img twice and it worked, but about 3 days ago I can't solve this flashing persist.img, I tried wiping everything, downgrading to Nougat, then flashing Oreo, with TWRP and via flashtool, no solution, any other idea?? all sensors are not working.
Thanks in advance
Hello,
I have noticed since I have flashed the universal bootloader for LineageOS 14.1, that sometimes I am unable to perform the pull down action on the notification bar in order to open the quick settings.
Sometimes, this is fixed by locking the screen by pressing the power button and unlocking it after. This does not always work though. A more reliable way to "fix" this is to completely reboot the phone.
Can someone please advise if there's a known, more permanent, fix for this issue?
PS I went back to stock through EDL (shis should overwrite the boostack, right?), and the issue is present on stock rom too (2017G B10 7.1.1)
thanks a lot in advance!
rzarectha said:
Hello,
I have noticed since I have flashed the universal bootloader for LineageOS 14.1, that sometimes I am unable to perform the pull down action on the notification bar in order to open the quick settings.
Sometimes, this is fixed by locking the screen by pressing the power button and unlocking it after. This does not always work though. A more reliable way to "fix" this is to completely reboot the phone.
Can someone please advise if there's a known, more permanent, fix for this issue?
PS I went back to stock through EDL (shis should overwrite the boostack, right?), and the issue is present on stock rom too (2017G B10 7.1.1)
thanks a lot in advance!
Click to expand...
Click to collapse
Wait what? So you flashed the universal bootloader AFTER installing Lineage, and presumably using it?
If you installed an EDL ROM and the problem persists, it's definitely not the bootstack. are you sure there's nothing else that you installed both on stock and los?
Choose an username... said:
Wait what? So you flashed the universal bootloader AFTER installing Lineage, and presumably using it?
If you installed an EDL ROM and the problem persists, it's definitely not the bootstack. are you sure there's nothing else that you installed both on stock and los?
Click to expand...
Click to collapse
I definitely did not flash the bootloader after flashing lineage, I do not believe it's possible; my apologies if my wording was off.
As you said, it is possible that the switch to Lineage was just a coincidence.
You make a good point though, I did restore the same titanium backup apps on both ROMs. I should factory reset and see if it solves it.
cheers
rzarectha said:
I definitely did not flash the bootloader after flashing lineage, I do not believe it's possible; my apologies if my wording was off.
As you said, it is possible that the switch to Lineage was just a coincidence.
You make a good point though, I did restore the same titanium backup apps on both ROMs. I should factory reset and see if it solves it.
cheers
Click to expand...
Click to collapse
Yeah, I just didn't know what you meant. I guess it might be a root app or something. I used Material Notification Shade on stock but it had a couple of problems that i didn't figure out until some time ago (it was pretty obvious though)
And for something physical, have you fitted a screen protector lately? I had one that interfered with pull down.
Hi,
who has experienced the same loss of HDR/HD streaming support with update 10.5.5/10.5.6 (Bootloader wasn't unlocked)?
Anyone got a solution to get back Widevine L1?
As far as we found out in the Oneplus forum all model and firmware variants are effected.
I sent logs to Oneplus through the community app but the answers were more or less prepared and only telling me that they research on this issue. Someone got the info from German support that it will be fixed through OTA, but I don't think this will be possible and most likely we have to go for RMA.
To find out about DRM/Widevine level you can use DRM Info app or Netflix in the player properties.
Best regards,
Bernd
This happened to me as well. Noticed the other day on 10.5.8 that Netflix wasn't in HD anymore. Did not unlock bootloader, just did OTA's through the system, no Oxygen Updater .
I tried unlocking and then re locking the bootloader but this did not fix the issue, I still have L3.
Really hoping I don't have to RMA for this.
Okay I was thinking about doing the same, but obviously it didn't fix it for you so I skip it...
Coming from Oneplus 5 with it's DRM drama this really annoys me.
See this post in OnePlus forum:
https://forums.oneplus.com/threads/...int-registration-error.1218379/#post-21604919
As far as I understood, flashing or in our case updating causes the persistent partition (which is encrypted with the first registered fingerprint) to get unreadable, if you removed the first fingerprint data (which I did when I registered my fingerprints freshly, after applying a screen protector) - but I could be also wrong as I used Google Translate read the original post. Maybe someone who is deeper in the rabbit hole can confirm this theory, cause it would be great to know at least where the issue comes from and if a RMA is required or a solution can be achieved via OTA.
Bernd
So removing FP data corrupts the persist partition, correct?
Of that so;
Removing FP breaks FP
Cross flashing breaks FP
Magisk Canary breaks FP
Relocking breaks FP
I did send my phone for RMA after having it for only two days. So I've been reading up on this issue and for now I have this.
Backup your persist partition
Root only with Stable Magisk 20.4
Make your own patched image
Don't relock your bootloader
Altho I can't seem to find how to backup that partition without unlocking the bootloader
I wouldn't had unlocked my bootloader if I knew it's causing so many issues. Honestly I need root just for vanced yt... So it's not worth the troubles I had ?
Balthazard said:
So removing FP data corrupts the persist partition, correct?
Click to expand...
Click to collapse
possible, as said I'm neither that far in the android rabbit hole nor is my Chinese that good but it's possible that FP is the bad guy in this game.
Not possible to backup with ADB or Fastboot?
But as far as I've read through this thread https://forum.xda-developers.com/showpost.php?p=80139723&postcount=26 even a backup/restore doesn't help. For the moment I hope for a workaround the DRM sh*t by OnePlus - I mean who the hell would use an Android Phone for content piracy...
Bootloader still locked on INAA 10.5.8, Im on L1. I had installed and uninstalled fp, now its back in, no changes
Patching your own is the smart move inho
bigjailerman said:
I had installed and uninstalled fp, now its back in, no changes
Patching your own is the smart move inho
Click to expand...
Click to collapse
Didn't touch my bootloader so far. Original FP was with 10.5.4 and deleted/readded with 10.5.6.
Did you mean by re-adding them with 10.5.8 was bringing L1 back? What should be patched?
Although my setup isn't the same as everyone else here, (bl unlocked, rooted & custom kernel. Also on beta 11). Noticed that Netflix had dropped to L3 in the playback settings section. Cleared storage on the app from settings & used magiskhide on Netflix. Seemed to put the app back on L1.
Hi,
So I have had some trouble with the fingerprint scanner on my OnePlus 8 Pro. So I followed the persist.img fix guide but unfortunately the issue was not fixed. I assumed that this would mean the phone had no chance of regaining the use of fingerprint scanner. But I decided to reflash with msm as the guide requires and follow all the steps from the beginning again. Still no luck.
The third time, instead of replacing the data and engineermode (not replacing gf_persist.so) as the guide says, I just tried using the fingerprint scanner. It worked perfectly. I could enroll new fingerprints and even use them to unlock as usual. The issue is that this only lasts until the next shutdown/reboot. After that, I must redo the fingerprint test (and fail it) to regain use of fingerprint.
Can anybody recommend some sort of solution for this. I would like to be able to run lineage on here as I have on other phones in the past but I dont think i'm able to use the fingerprint test in the phone app as I can while running oxygen. Thanks for any help.
I have the same problem. Any solutions?
zioloiso said:
I have the same problem. Any solutions?
Click to expand...
Click to collapse
No, still nothing. Tried following again and again but still no luck.
kaxp said:
No, still nothing. Tried following again and again but still no luck.
Click to expand...
Click to collapse
Its another solution, do you have magisk?
I have the same and on top of that my other sensors seem messed up as well...banging my head against the wall
I have no clean persist backup ...
Can anyone please send me their persist.img if you have Oneplus 8 Pro European version?
I know it might give me problems with the fingerprint sensor but at least the others would work..
Did you ever get your fingerprint scanner working? I know it's a long shot u seeing this reply since it's old lol. But Im having same issue after msm and upgrading to OS 13..