Some days ago I bricked my phone, but made it work again with the EDL method. Everything works again, apart from the Fingerprint sensor. I'm quite sure that I assembled it correctly, because it's clearly recognized(also when I use the swipe on fingerprint sensor to see notifications feature). It's recognized until the last bar at the registration, but then it always fails. I've tried several roms(stock and custom), but always the same.
Any suggestions for a fix?
Thanks in advance
Veran125 said:
Some days ago I bricked my phone, but made it work again with the EDL method. Everything works again, apart from the Fingerprint sensor. I'm quite sure that I assembled it correctly, because it's clearly recognized(also when I use the swipe on fingerprint sensor to see notifications feature). It's recognized until the last bar at the registration, but then it always fails. I've tried several roms(stock and custom), but always the same.
Any suggestions for a fix?
Thanks in advance
Click to expand...
Click to collapse
Have the same problem. It has something to do with your persist partition. Perhaps you saved it via twrp? I had a save but don´t find it. **** happens.
I erased everything and flashed every fastboot rom via edl or normally. My fingerprint is broken!
Yeah, I used TWRP back in time. But I start to think that's it's a hardware issue. It happened after I had to open my phone to get into EDL mode.
Veran125 said:
Yeah, I used TWRP back in time. But I start to think that's it's a hardware issue. It happened after I had to open my phone to get into EDL mode.
Click to expand...
Click to collapse
In my case it´s a software issue... I used to open my phone, but when my fp broke when I was trying to fix goodix for our new bootleggers rom. I did the fix from official telegram group and a after that, root explorer could mount persist (this was the issue, why fp couldn´t be safed in gsi´s using a pie vendor), but the fp still couldn´t be safed. That means, now it could connect data and changed sth. badly...
I had the same problem. But I had a backup of the twrp sections of the persist and efs. I restored these partitions and flashed 9640 miflash. now the fingerprint works fine
So as long as my fingerprint sensor is recognized, it's most likely not a hardware issue? Furthermore did I unbrick my phone by flashing with EDL mode. Isn't everything formatted then? But I also downgraded to Oreo after that, could that be the reason?
Veran125 said:
But I also downgraded to Oreo after that, could that be the reason?
Click to expand...
Click to collapse
No
My fingerprint recognition works now with rr gsi. I will try wheather the problem is solved on stock too. I just went back too rr gsi, becouse I have a fully working data partition for it and luckily my fp started to work again. Idk what´s the problem.
Veran125 said:
Some days ago I bricked my phone, but made it work again with the EDL method. Everything works again, apart from the Fingerprint sensor. I'm quite sure that I assembled it correctly, because it's clearly recognized(also when I use the swipe on fingerprint sensor to see notifications feature). It's recognized until the last bar at the registration, but then it always fails. I've tried several roms(stock and custom), but always the same.
Any suggestions for a fix?
Thanks in advance
Click to expand...
Click to collapse
Thanks to @eremitein we have a flashable zip that restores the persist image. Just flash via twrp - works for me!
https://forum.xda-developers.com/showpost.php?p=79368367&postcount=25
Thanks a lot, it really works.
Good that I wrote here before I reopened my phone.
Related
Hey there, everyone! Three days ago, I dropped my phone in water and it hard-bricked. I followed Naman Bhalla's amazing un-brick guide, and it worked wonders! However, I've been reverted to OOS 3.1.2, and WiFi and BlueTooth don't work at all. I was able to bypass the initial help screens using mobile data.
I tried flashing the OOS 5.1 onto my phone by downloading it from the official site. However, as soon as I flash it and restart, the boot gets stuck mid-way and the phone reboots repeatedly.
Which (stable) version should I flash? Also, how do I get my WiFi and bluetooth to work? I can make and receive calls without any problem. Also, what is the highest version I can safely flash to?
rahulkulhalli said:
Hey there, everyone! Three days ago, I dropped my phone in water and it hard-bricked. I followed Naman Bhalla's amazing un-brick guide, and it worked wonders! However, I've been reverted to OOS 3.1.2, and WiFi and BlueTooth don't work at all. I was able to bypass the initial help screens using mobile data.
I tried flashing the OOS 5.1 onto my phone by downloading it from the official site. However, as soon as I flash it and restart, the boot gets stuck mid-way and the phone reboots repeatedly.
Which (stable) version should I flash? Also, how do I get my WiFi and bluetooth to work? I can make and receive calls without any problem. Also, what is the highest version I can safely flash to?
Click to expand...
Click to collapse
Your phone bricked after it dropped in water? I would say hardware damage... Does the phone survive a reboot on 3.1.2?
Puddi_Puddin said:
Your phone bricked after it dropped in water? I would say hardware damage... Does the phone survive a reboot on 3.1.2?
Click to expand...
Click to collapse
To be honest, I don't think water damage was even involved here. In my panic, I restarted the phone multiple times because the touch suddenly stopped working. A few hours later, the touch returned, but I was experiencing a bootloop.
There have been several qualms about WiFi and Bluetooth not working after the Step 2 recovery in the thread comments, though. Someone suggested rebooting to fastboot and deleting the 'modemts' lines. However, the said person also mentioned that a flash to Stock ROM was needed.
After recovering my phone, I tried to flash the latest OOS from the official website, but then I experience the same bootloop I was experiencing before.
Edit: To answer your question - Yes. The phone does reboot without a hitch when flashed to OOS 3.1.2
Edit 2: I'd like to rephrase the original message in the thread - it did NOT hard-brick, but soft-brick. Utterly sorry for the stupid mistake.
rahulkulhalli said:
To be honest, I don't think water damage was even involved here. In my panic, I restarted the phone multiple times because the touch suddenly stopped working. A few hours later, the touch returned, but I was experiencing a bootloop.
There have been several qualms about WiFi and Bluetooth not working after the Step 2 recovery in the thread comments, though. Someone suggested rebooting to fastboot and deleting the 'modemts' lines. However, the said person also mentioned that a flash to Stock ROM was needed.
After recovering my phone, I tried to flash the latest OOS from the official website, but then I experience the same bootloop I was experiencing before.
Edit: To answer your question - Yes. The phone does reboot without a hitch when flashed to OOS 3.1.2
Edit 2: I'd like to rephrase the original message in the thread - it did NOT hard-brick, but soft-brick. Utterly sorry for the stupid mistake.
Click to expand...
Click to collapse
Try to remove the modem files indeed. I bricked it once and my wifi wasn't working. And that fixed it. Remove those files then flash the same OOS if possible. And OTA upgrade. See if it works!
Edit:
This did fix my WiFi.
simonsmh said:
for those lost modem imei wifi carrier etc
Flash stock oos or h2os ROM then reboot to fastboot
fastboot erase modemst1
fastboot erase modemst2
good luck!
Click to expand...
Click to collapse
Puddi_Puddin said:
Try to remove the modem files indeed. I bricked it once and my wifi wasn't working. And that fixed it. Remove those files then flash the same OOS if possible. And OTA upgrade. See if it works!
Edit:
This did fix my WiFi.
Click to expand...
Click to collapse
Oh, I see. I have to be honest, I'm a complete amateur in this domain.
I did try to issue those two commands, but they don't seem to make any difference. Just to make sure, let me reiterate the steps I followed. Please let me know if I did anything wrong:
Followed method 2 in the un-brick guide, which flashed my phone to OOS 3.1.2.
Booted successfully and skipped the initial setup part using mobile data (which is working perfectly).
Went into settings and activated the 'Allow OEM unlocking' and 'Allow USB debugging' switches.
Rebooted phone to fastboot and unlocked bootloader using 'oem unlock bootloader'.
Typed in both the 'modemst1' and 'modemst2' commands, which were successful.
Used fastboot reboot to reboot the system.
As you mentioned above, you said (and I quote)
Remove those files then flash the same OOS if possible
Click to expand...
Click to collapse
Should I do this?
Reboot phone into fastboot and delete the two files.
Reboot the phone.
Flash the same OOS again.
Thanks!
rahulkulhalli said:
Oh, I see. I have to be honest, I'm a complete amateur in this domain.
I did try to issue those two commands, but they don't seem to make any difference. Just to make sure, let me reiterate the steps I followed. Please let me know if I did anything wrong:
Followed method 2 in the un-brick guide, which flashed my phone to OOS 3.1.2.
Booted successfully and skipped the initial setup part using mobile data (which is working perfectly).
Went into settings and activated the 'Allow OEM unlocking' and 'Allow USB debugging' switches.
Rebooted phone to fastboot and unlocked bootloader using 'oem unlock bootloader'.
Typed in both the 'modemst1' and 'modemst2' commands, which were successful.
Used fastboot reboot to reboot the system.
As you mentioned above, you said (and I quote)
Should I do this?
Reboot phone into fastboot and delete the two files.
Reboot the phone.
Flash the same OOS again.
Thanks!
Click to expand...
Click to collapse
Probably you meet the hardware issues. You can try it because it has no damage to your device.
simonsmh said:
Probably you meet the hardware issues. You can try it because it has no damage to your device.
Click to expand...
Click to collapse
Um, does that mean the h/w is faulty?
Hello everyone!
So my problem started a few weeks ago when i flashed ABC Rom on my MiMix2, the proximity sensor, in calls, started to not work after a time, but it was a gradual process, until it didn't work at all. So a few days ago i decided to try and solve the problem. I've read in different places that it could be the persist partition, that holds the drivers for the sensor.
I have tried flashing the persist.img with fastboot from the original xiaomi site, but it kept telling me the partition is write protected. Tried with adb but then i couldn't mount the partition. In the end i ended up reflashing the original image with MIUI Flashing Tool, modifying the image to flash the persist image, with no positive results, except i could mount the partition again. I then looked in the persist.img file to find out it is empty, all of them that i could find are almost empty(some empty folders).
I fount a thread on XDA with some sensor files for my phone that i had to copy in my root/sensors directory, so i did and nothing changed.
The weird thing is that after all of this, when i enter the calibration app that that MIUI has and hold my hand on the sensor sometimes it detects my hand.
Sooo.... after all of this is my problem a software one or a hardware one (if its a hardware one, its a strage one, because the sensor works but its just weak).
Can anyone help me with some answers please. Thanks and sorry for the long post.
bzadi said:
Hello everyone!
So my problem started a few weeks ago when i flashed ABC Rom on my MiMix2, the proximity sensor, in calls, started to not work after a time, but it was a gradual process, until it didn't work at all. So a few days ago i decided to try and solve the problem. I've read in different places that it could be the persist partition, that holds the drivers for the sensor.
I have tried flashing the persist.img with fastboot from the original xiaomi site, but it kept telling me the partition is write protected. Tried with adb but then i couldn't mount the partition. In the end i ended up reflashing the original image with MIUI Flashing Tool, modifying the image to flash the persist image, with no positive results, except i could mount the partition again. I then looked in the persist.img file to find out it is empty, all of them that i could find are almost empty(some empty folders).
I fount a thread on XDA with some sensor files for my phone that i had to copy in my root/sensors directory, so i did and nothing changed.
The weird thing is that after all of this, when i enter the calibration app that that MIUI has and hold my hand on the sensor sometimes it detects my hand.
Sooo.... after all of this is my problem a software one or a hardware one (if its a hardware one, its a strage one, because the sensor works but its just weak).
Can anyone help me with some answers please. Thanks and sorry for the long post.
Click to expand...
Click to collapse
Probably the custom ROM causing the issue
This is what i assumed at first, but i flashed the original xiaomi image with their tool, and still the same behavior. This problem now persists on all the roms i flash.
I've got the exact same problem, now proximity sensor doesn't work at all
bzadi said:
This is what i assumed at first, but i flashed the original xiaomi image with their tool, and still the same behavior. This problem now persists on all the roms i flash.
Click to expand...
Click to collapse
Nvjoel said:
I've got the exact same problem, now proximity sensor doesn't work at all
Click to expand...
Click to collapse
Do you have any kind of screen protection?
XDRdaniel said:
Do you have any kind of screen protection?
Click to expand...
Click to collapse
Nope, no screen protector, no case.
XDRdaniel said:
Do you have any kind of screen protection?
Click to expand...
Click to collapse
No case and no screen protection.
I am using Pixy Os 9.0 on Default Kernel And Phone Sensors are stopped Working like (accelerometer, proximity etc.).
I've tried going back to Oreo roms but not success.
Should I try changing kernel or something?
Try flashing this
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
That worked. Thank You
That sensor flashing is easy way. However I took a different time consuming way. Writing it down so that it may help some one else.
When I switched from Oreo AiCP to latest Pie AEX, I went via the hard way. You may read it here https://forum.xda-developers.com/le...bootloader-t3868174/post78256476#post78256476
AEX 6.0 worked well but I too was facing sensor issue. I re-flashed the ROM but no effect. CPU-Z sensor page was complete blank. Yes, I knew the sensor.zip available for flashing but I went ahead to REDO the entire ZUI 1.9 to AEX flashing process.
This time around, all sensors are working fine.
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
How to flash the sensor.zip fie?
I have ZUK Z2131, Android 9 and a problem with proximity sensor, when I answer to a call the display goes black, but I hold the phone in my hand and I can stop the call only with the power button. Will this zip helpinng me? And please tell me how to use it! Many thanks!
mirkios said:
How to flash the sensor.zip fie?
I have ZUK Z2131, Android 9 and a problem with proximity sensor, when I answer to a call the display goes black, but I hold the phone in my hand and I can stop the call only with the power button. Will this zip helpinng me? And please tell me how to use it! Many thanks!
Click to expand...
Click to collapse
Just goto recovery and flash the sensor.zip file.
Yes if the is due to sensors not working then it will help you but if the issue is from rom side code then it might not resolve the issue.
Are other sensors such as auto rotation working? If yes that might indicate that the issue is from rom side
satyen_ said:
Just goto recovery and flash the sensor.zip file.
Yes if the is due to sensors not working then it will help you but if the issue is from rom side code then it might not resolve the issue.
Are other sensors such as auto rotation working? If yes that might indicate that the issue is from rom side
Click to expand...
Click to collapse
I don't know what about the rom, because in the first place I changed the entire frame+screen+touch, all came in one piece. Until then the phone has no OTA, was stock international rom. I changed to Chinese rom because of this problem and step by step, I updated the stock rom until I reached the last version. After that I tried a custom room (this is actually on the phone, Android 9/AospExtended-v6.5-OFFICIAL), but with all rom the phone has the same behavior. So, what do you think?
mirkios said:
I don't know what about the rom, because in the first place I changed the entire frame+screen+touch, all came in one piece. Until then the phone has no OTA, was stock international rom. I changed to Chinese rom because of this problem and step by step, I updated the stock rom until I reached the last version. After that I tried a custom room (this is actually on the phone, Android 9/AospExtended-v6.5-OFFICIAL), but with all rom the phone has the same behavior. So, what do you think?
Click to expand...
Click to collapse
I think the issue is not with any ROM, it is due to the screen and all other replacements, may be after the replacement your proximity sensor is always covered or blocked with something. There are apps on playstore to see the proximity sensor data check if the always shows the same distance/reading i.e. 0 while waving your hand over it, and if yes then the issue might be what I mentioned above. If that's the case you would have to take of the screen and adjust the proximity sensory properly.
Check with this app :
https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
I have AOSP 10 on my ZUK. The sensors did not work.
Thank you. Now everything works well.
Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM
the_mentor said:
Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM
Click to expand...
Click to collapse
Take a backup of your personal files and then wipe system, data, internal storage and both caches. Then flash OOS 5.0.8 and without adding any apps, check the calling function. If it still happens, then most likely a hardware issue.
tnsmani said:
Take a backup of your personal files and then wipe system, data, internal storage and both caches. Then flash OOS 5.0.8 and without adding any apps, check the calling function. If it still happens, then most likely a hardware issue.
Click to expand...
Click to collapse
If it's a hardware problem which part should I replace?
I already ordered a battery before this issue started and I was planning on replacing it once it gets here maybe I can replace one of the parts in order to resolve this issue
the_mentor said:
If it's a hardware problem which part should I replace?
I already ordered a battery before this issue started and I was planning on replacing it once it gets here maybe I can replace one of the parts in order to resolve this issue
Click to expand...
Click to collapse
You will need to replace the main board if the issue persist.
Same problem here
Hello mate, I've got the exact same problem with my wife's OP3. What did you do eventually? Did you find out? Please help. Thanks
New geek said:
Hello mate, I've got the exact same problem with my wife's OP3. What did you do eventually? Did you find out? Please help. Thanks
Click to expand...
Click to collapse
Hmmm quite strange that you're having the same issue.
I didnt find a solution yet i gave her a temp replace phone that we had in a drawer somewhere.
Did your wife do anything out of the ordinary when it happened? are you having the same issue that LOS works but stock rom shows factory reset?
thanks.
-DM.
the_mentor said:
Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM
Click to expand...
Click to collapse
try using msm v3.0 tool fixes most problems not hardware though
the_mentor said:
Hmmm quite strange that you're having the same issue.
I didnt find a solution yet i gave her a temp replace phone that we had in a drawer somewhere.
Did your wife do anything out of the ordinary when it happened? are you having the same issue that LOS works but stock rom shows factory reset?
thanks.
-DM.
Click to expand...
Click to collapse
No, She did not do anything out of the ordinary. But weirdly I have exactly the same things happening. Lineage works but no sound. Everything else factory resets. I have tried quite a few ROM'swithout any luck. So far the only ROM which worked for some time(1day) was 6.0.1 . I have spent quite a long time on this flashing various ROM and dont know what to do now.
New geek said:
No, She did not do anything out of the ordinary. But weirdly I have exactly the same things happening. Lineage works but no sound. Everything else factory resets. I have tried quite a few ROM'swithout any luck. So far the only ROM which worked for some time(1day) was 6.0.1 . I have spent quite a long time on this flashing various ROM and dont know what to do now.
Click to expand...
Click to collapse
Update: @ireaper4592 might have a point here. I have gone one level up and I tried msm v3.0 tool, thus doing a complete reinstall including firmware. The factory resetting stopped but the sound was not working (I thought that it could be the ROM and the security patches). So I updated to the latest ROM available from Oneplus and evrything has been working since. I did this last night so not sure how long this is going to stay like that. I will give it some time and update later. Wife is using it now!
what you will need to do is download the oneplus 3 recovery tool and put the phone into qualcolm mode and restore the phone that way. here is a link https://www.androidexplained.com/oneplus-3-unbrick-return-stock/
New geek said:
Update: @ireaper4592 might have a point here. I have gone one level up and I tried msm v3.0 tool, thus doing a complete reinstall including firmware. The factory resetting stopped but the sound was not working (I thought that it could be the ROM and the security patches). So I updated to the latest ROM available from Oneplus and evrything has been working since. I did this last night so not sure how long this is going to stay like that. I will give it some time and update later. Wife is using it now!
Click to expand...
Click to collapse
its really good to know.
did you have to wipe the internal storage for this process to work ?
Do you have a guide that you've used to get this working?
Thanks in advanced.
-DM
the_mentor said:
its really good to know.
did you have to wipe the internal storage for this process to work ?
Do you have a guide that you've used to get this working?
Thanks in advanced.
-DM
Click to expand...
Click to collapse
That tool/procedure will reset your phone. So you will lose everything on the phone. Take a backup beforehand.
The link posted in the post above yours contains the guide as well as the tools. It also has links to the original guide here on XDA.
tnsmani said:
That tool/procedure will reset your phone. So you will lose everything on the phone. Take a backup beforehand.
The link posted in the post above yours contains the guide as well as the tools. It also has links to the original guide here on XDA.
Click to expand...
Click to collapse
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM
the_mentor said:
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM
Click to expand...
Click to collapse
Please share the guide as I am also suffering with same problem.
Still not working
the_mentor said:
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM
Click to expand...
Click to collapse
I was about to update here with good news but wife's phone went back to restart loop the next day. I am not sure but probably triggered by her installing whatsapp and facebook. I put the phone away because I have already spend quite a lot of time behind this. Is your's still going? Please list the step by step procedure. Thanks
download from here https://mega.nz/#!zsdnkCDA!UyJRwbJK6kHTDpmesBYao0knaOTwbgu4dSiokV1XLYU then turn off phone run tool,connect phone with volume up pressed,should have a com in the list if so just click start thats it and wait for it to turn green or device restart
ok so, my phone's fingerprint sensor will just show "fingerprint sensor calibration needed" when trying to register a fingerprint. I've tried to nand erase and repartition, clean flash install, magisk install, hard reset etc but it wont work. It passes all the fingerprint tests fine.
I didn't buy or change any parts from the phone, it's still oem
what can i do to solve this? thanks
applesucksLmao said:
ok so, my phone's fingerprint sensor will just show "fingerprint sensor calibration needed" when trying to register a fingerprint. I've tried to nand erase and repartition, clean flash install, magisk install, hard reset etc but it wont work. It passes all the fingerprint tests fine.
I didn't buy or change any parts from the phone, it's still oem
what can i do to solve this? thanks
Click to expand...
Click to collapse
Hey, did you ever find out something?
I just got that problem too
weird. its funny how samsung killed my fingerprint all together. it died just by sitting over night. stock and Knox was intact. its permanently gone.fw downgrade doesn't help.
Captain_cookie_200 said:
weird. its funny how samsung killed my fingerprint all together. it died just by sitting over night. stock and Knox was intact. its permanently gone.fw downgrade doesn't help.
Click to expand...
Click to collapse
I *think* it has something to actually do with the calibration. The problem is that the sensor calibration needs to be performed with some application/equipment that either doesn't exist or is exclusive to samsung service centers.
I suspect we're gonna need some hacky workaround like the IMEI thing, which BTW never got really fixed.
Mighty_Rearranger said:
I *think* it has something to actually do with the calibration. The problem is that the sensor calibration needs to be performed with some application/equipment that either doesn't exist or is exclusive to samsung service centers.
I suspect we're gonna need some hacky workaround like the IMEI thing, which BTW never got really fixed.
Click to expand...
Click to collapse
i see..