Today I updated my G32 to Android 13 and the fingerprint is not responding nor its accepting any new fingerprints.
help me. What to do ?
Hi piiertopier,
I understand your frustration and I'm sorry for the inconvenience you're experiencing. Our best advice for this situation is that you submit your device for review and repair at one of our service centers so that repair engineer could examine your unit and provide a proper resolution. Please follow the mentioned link here for repair options.
Best regards,
Amit
Did someone help you today? Give them a kudo by pressing the thumbs-up icon!
Did your topic get solved? Mark the response by pressing the "Accept Solution"!
¿Alguien te ayudó hoy? ¡Haz clic en el botón Me gusta para agradecer con un Kudo!
Si encuentra útil una publicación y responde a su pregunta, márquela como "Aceptar solución"!
Was this solution helpful?
Your feedback helps us improve!Hi Ridwan_2001,
I'm sorry to hear that you're having trouble with your fingerprint sensor after updating to Android 13. Here are a few steps you can try:
Restart your device: Sometimes, a simple restart can fix minor software glitches.
Clear cache for fingerprint service: Go to Settings > Apps > Show system > Fingerprint > Storage > Clear Cache.
Safe Mode: Boot your device in safe mode to check if any third-party app is causing the issue. If the fingerprint sensor works in safe mode, then a third-party app is the culprit. You can then uninstall apps one by one to find the problematic app.
Factory Reset: If none of the above steps work, you may need to perform a factory reset. Please remember to back up your data before doing this as it will erase everything on your device.
If the problem persists, please let us know.
Regards,
Jess
Motorola Support
Did someone help you today? Give them a kudo by pressing the thumbs-up icon!
Did your topic get solved? Mark the response by pressing the "Accept Solution"!
¿Alguien te ayudó hoy? ¡Haz clic en el botón Me gusta para agradecer con un Kudo!
Si encuentra útil una publicación y responde a su pregunta, márquela como "Aceptar solución"!
Today I installed Android 13 update on my Moto G32. Initially it was fine. After 4/5 hrs of installation my Moto 32 is not unlocking after applied the pattern I use to open it. It did not read the pattern also. It is Not saying wrong pattern or something else. Not able to switch off it also....
Mine also, finger print is not working on my moto g32, also no finger print option on settings and app list.
Today i done safe mode ,rest phone , but nothing works on me
Mine also. No fingerprint option like it's never been there.
We're not alone and seems is quite a widespread issue.
No solution seems forthcoming.
Hi,
In this case, we would suggest you try using the Rescue and Smart Assistance tool and perform the Rescue function. Please go through the link here for instructions. This process will wipe all data from the phone. Make sure that you have taken all data back up before you can perform the Rescue function on your phone. Please go through the backup instructions here.
Regards,
Amit
Did someone help you today? Give them a kudo by pressing the thumbs-up icon!
Did your topic get solved? Mark the response by pressing the "Accept Solution"!
¿Alguien te ayudó hoy? ¡Haz clic en el botón Me gusta para agradecer con un Kudo!
Si encuentra útil una publicación y responde a su pregunta, márquela como "Aceptar solución"!
Thanks but I'm a Mac user so version available.
It's not limited to G32 phones, or any Moto G phone for that matter. There are plenty of others facing the same situation.
A further update is required rather than a restore on individual phones.
Same problem with my Moto G32 after Android 13 and believe that only can be solved with next update.
@KD_Moto_G32 wrote:
Same problem with my Moto G32 after Android 13 and believe that only can be solved with next update.
I've done everything from the (limited) suggestions to resolve this and nothing has worked. Have resigned myself to either wait for next update or a new mobile. Main feature of fingerprint sensor redundant. Not sure there will be a further update that would resolve this though.
