RR oreo treble build, sensor were working perfectly and something happened and no sensor is working. Which partition should i flash for sensor recovery?
Related
proximity sensor is not working, i flashed ddjg6, jpm, kyrillos 4.1 but in any rom my phones proximity sensor not working.
is it not always working or not working sometimes?
did you try clearing cache and factory reset?
Proximity sensor
yes hard resed, wipe frow recovery in ddjg6, jpf,jpm every rom but nothing happene' i think it is a hardware problem.
Well then flash the stock firmware with which your phone came and give it to the samsung centre
Hello. I have 2 questions for you. 1st is i flashed pacman rom to my device. After that my proximity sensor killed. I formatted my phone and flashed previous rom. Proximity still not working. I tested it with sensor tester. It says your phone not allows proximity. How can i fix it?
And second question is, how can i back to stock system on g7? I cant install system with dload. Thank you all!
So I installed the revolution mod (nougat) and my fingerprint sensor was not working so I installed the stock firmware and because there were no fingerprints saved on stock, I factory reseted the phone, then I installed the revolution rom again and it was working for few days but now it stopped working again (sometimes it does not recognize it and sometimes it doesnt even vibrate... Like i would not even have my finger on it)
Hi guys,
Recently, I have installed Arrow OS 9.0 and I was unable to enroll my fingerprint (But I can use my fp sensor as home button).
Currently I have flashed stock ROM and restored IMEI. I was able to use both my SIM slots and device name shows xt1643. Again, I was not able to enroll my fingerprint. The error message reads "INTERNAL ERROR, Sorry your fingerprint can not be enrolled due to internal error". But, after rooting my device i was able to use it as home button.
Is there any thing that i have missed? Or is my fp sensor gone?
askreddy2 said:
Hi guys,
Recently, I have installed Arrow OS 9.0 and I was unable to enroll my fingerprint (But I can use my fp sensor as home button).
Currently I have flashed stock ROM and restored IMEI. I was able to use both my SIM slots and device name shows xt1643. Again, I was not able to enroll my fingerprint. The error message reads "INTERNAL ERROR, Sorry your fingerprint can not be enrolled due to internal error". But, after rooting my device i was able to use it as home button.
Is there any thing that i have missed? Or is my fp sensor gone?
Click to expand...
Click to collapse
I am using Redmi Note 4 and facing same problem after flashing Aosp Extended Pie ....The fingerprint sensor wouldn't just work. As if it is dead
Tried deleting these files
Root/data/system/users/0/settings_fingerprint.xml
And
Root/data/system/users/0/fpdata/users.db
Now the files are gone and sensor is dead ....Works when Miui is flashed but dont know what is going wrong in custom Rom
marzipan sasquatch said:
I am using Redmi Note 4 and facing same problem after flashing Aosp Extended Pie ....The fingerprint sensor wouldn't just work. As if it is dead
Tried deleting these files
Root/data/system/users/0/settings_fingerprint.xml
And
Root/data/system/users/0/fpdata/users.db
Now the files are gone and sensor is dead ....Works when Miui is flashed but dont know what is going wrong in custom Rom
Click to expand...
Click to collapse
Thankyou brother for the info. But even after reverting back to stock rom, my fp sensor was not working properly. Maybe some of my vendor files were messed up.
So I flashed lineageOs 17.1 unofficial build on my phone earlier to test it out. After booting into it, I realized the fingerprint sensor wasn't working so I flashed the stock rom using odin. After boot, fingerprint sensor still didn't respond and when I try to add a print, I get an error,"make sure the home key is clean and dry, then try again.", so I used the dailer code (*#0*#) to run sensor diagnostics. The results are as seen attached. Is there anything I can do about it? The home button still works fine so I doubt its a hardware problem. If anyone has a fix for this i'd be grateful for you to share.