My Alpha was working normally for 3 weeks, and then a day, it started to give an error when trying to unlock with fingerprint: "an error has occurred with the fingerprint sensor"
I unlocked it with password, then switched off fingerprint lockscreen. Then when I tried to turn it back on (click on the fingerprint manager) it dropped this error again "an error has occurred with the fingerprint sensor".
I have done factory reset, reinstalled with odin, downgraded to 4.4.4, no success. Then I took it to the service centre, they have replaced the home button and updated the software (to the same it was on it previously: 5.0.2 COI3, XEH region). The fingerprint worked at the service centre when I tried it. Then I went back home, done factory reset, few hours elapsed, then I tried to register my fingerprint, and this error showed up again. I reinstalled it with odin, with kies, downgraded to 4.4.4, deleted fingerprint app data, no success. I have found nothing helpful on the internet with hours of searching. It should be software related I think, it's very unlikely, that the hardware error (like unglued home button or something) occurred again, within this kinda short time.
Please help me, what to do. I would be very grateful
Im also having this problem, and many more people i believe. There are some fixes to this like heating it up or something. For some people it works, for some it doesn't.
EDIT: there's a video on youtube about it, you can try it.
https://www.youtube.com/watch?v=jrpnlP4_MvU
knijntjes said:
Im also having this problem, and many more people i believe. There are some fixes to this like heating it up or something. For some people it works, for some it doesn't.
EDIT: there's a video on youtube about it, you can try it.
https://www.youtube.com/watch?v=jrpnlP4_MvU
Click to expand...
Click to collapse
I've seen it but I'm afraid that the screen or something will unglue due to the heat...
I ordered Premium Warranty Shipping, with spare phone, I hope they fix it but I will tell them firmly to replace the full phone or refund me the 510$ what's on the receipt.
But I'm open for any solution if anybody have it.
anderledani said:
My Alpha was working normally for 3 weeks, and then a day, it started to give an error when trying to unlock with fingerprint: "an error has occurred with the fingerprint sensor"
I unlocked it with password, then switched off fingerprint lockscreen. Then when I tried to turn it back on (click on the fingerprint manager) it dropped this error again "an error has occurred with the fingerprint sensor".
I have done factory reset, reinstalled with odin, downgraded to 4.4.4, no success. Then I took it to the service centre, they have replaced the home button and updated the software (to the same it was on it previously: 5.0.2 COI3, XEH region). The fingerprint worked at the service centre when I tried it. Then I went back home, done factory reset, few hours elapsed, then I tried to register my fingerprint, and this error showed up again. I reinstalled it with odin, with kies, downgraded to 4.4.4, deleted fingerprint app data, no success. I have found nothing helpful on the internet with hours of searching. It should be software related I think, it's very unlikely, that the hardware error (like unglued home button or something) occurred again, within this kinda short time.
Please help me, what to do. I would be very grateful
Click to expand...
Click to collapse
you're not missing out on anything , the finger print scanner is garbage , it works on my phone and its complete garbage
it dosent work 80 percent of the times its basically garbage , the whole phone is honestly but thats another story , iregret buyign this crap 0 roms 0 support fk this phone
Andraxo said:
you're not missing out on anything , the finger print scanner is garbage , it works on my phone and its complete garbage
it dosent work 80 percent of the times its basically garbage , the whole phone is honestly but thats another story , iregret buyign this crap 0 roms 0 support fk this phone
Click to expand...
Click to collapse
Your way of handling the phone is garbage. You are for sure an iPhone fan.
Sensor works 100%.
UniversalKID said:
Your way of handling the phone is garbage. You are for sure an iPhone fan.
Sensor works 100%.
Click to expand...
Click to collapse
Going to second this, the fingerprint scanner works great for me, also slating a phone because it doesn't have any unofficial support is stupid.
Anyway probably best to send it back
anderledani said:
I've seen it but I'm afraid that the screen or something will unglue due to the heat...
I ordered Premium Warranty Shipping, with spare phone, I hope they fix it but I will tell them firmly to replace the full phone or refund me the 510$ what's on the receipt.
But I'm open for any solution if anybody have it.
Click to expand...
Click to collapse
i had this issue hair dryer really fix this issue ... if you are afraid of your screen ..put something on a screen like a book or anyother everything will be fine but .. it just a temporary fix u will get the issue again after 3 to 4 days again heat it up then problem will disapper and it will go on and on ....
Hi all, i was using LG g4 h811 Tmobile variant and it was working great but all of a sudden the wifi stopped working, the wifi icon keeps pulsating and it does not connect, i tried to fix that issue by simply googling it and found out there's no other solution except replacing it. unfortunatel i don't have warranty so my only shot i to try to root it and flash a custom rom. Now i started finding threads about how to root my G4 and theres nothing on H81120o, i downloaded the rooted image from a thread but it found out it was for H81110h.
This can be both hardware and software issue, if you gently smack your hand on the back of your phone, does it work? If you enable airplane mode for a minute and then disable it, does it work? If it works by smacking it, it is a hardware issue, if it works by the airplane mode method, it is a software issue. If the smacking thing doesn't work try putting the phone upside down and spinning it around for different positions to smack it (it is starting to sound like something else here, if you know what I mean) and see if that works, if it eventually works, you know were the problem is coming from and it is a loose wifi chip. If none of this works, consider resetting the phone to see if that works. Also, was your phone hot whenthis issue occured?
most likely a hardware issue...
I agree with what RAZERZDAHACKER said, and I believe it's a hardware issue.
I have written a detailed summary (including a potential solution) here, in case you want to check it out: http://forum.xda-developers.com/general/help/qa-wifi-stuck-mac-020000000000-g2-g3-g4-t3452133
Good luck.
So I have this Verizon unlocked SM-G965U and decided to flash it with firmware SM-G965U1, after setting up the fingerprint lock, it will shut off a few seconds after the screen goes off. If I remove the option to unlock the phone with the fingerprint it will not shut off. It started happening after I flashed it, and it did not happen before today.
I already tried flashing a second firmware, right now it’s currently on build PPR1.180610.011.G965U1UE6CSI1
I decided to update and change the firmware to SM-G965U1 because the one I got from Verizon wasn’t giving me updates at all (it was stuck on security updates from April 2019). I’m not in the US so I decided to go for the unlocked firmware model to get updates.
I found people who have had this in the past but no one seems to give a definitive fix. I don’t think this is a hardware issue.
Has anyone found this issue before and fixed it?
Should I try flashing another firmware coming back to the original model (SM-G965U)? (Is there any risk if I flash the firmware with carrier?)
Thank you!
So pretty much two days later and I have come to the conclusion that the issue with the phone is hardware related. I've don research online and several report they had the same problem after getting it wet, while others never got it wet, so that's why I had hopes mine was not a hardware issue. Granted I DID get the phone wet but the symptom described on the first post started after the second day i got it wet and right after I flashed my unit.
Just for the record, I flashed the phone back and forth from SM-G965U to SM-G965U1 (that's when I got the shutting down issue when fingerprint lock is enabled), reverted it to SM-G965U (tried at least two different firmwares), and finally settled in SM-G965U1 (I mean, why not?). I did try firmware with security patch prior to September 1st 2019 (since a user suggested that's when he got the issue on his phone).
Firmwares used to test:
SM-G965U1_1_20190816080114_wltpjfnoy9_fac
SM-G965U_1_20190910091240_jebmc6r22k_fac
VZW-G965USQS6CSH3-20190822152617
Now I see why nobody dared to reply to my post... I think I covered all the bases here, otherwise please let me know.
rstevep8 said:
So pretty much two days later and I have come to the conclusion that the issue with the phone is hardware related. I've don research online and several report they had the same problem after getting it wet, while others never got it wet, so that's why I had hopes mine was not a hardware issue. Granted I DID get the phone wet but the symptom described on the first post started after the second day i got it wet and right after I flashed my unit.
Just for the record, I flashed the phone back and forth from SM-G965U to SM-G965U1 (that's when I got the shutting down issue when fingerprint lock is enabled), reverted it to SM-G965U (tried at least two different firmwares), and finally settled in SM-G965U1 (I mean, why not?). I did try firmware with security patch prior to September 1st 2019 (since a user suggested that's when he got the issue on his phone).
Firmwares used to test:
SM-G965U1_1_20190816080114_wltpjfnoy9_fac
SM-G965U_1_20190910091240_jebmc6r22k_fac
VZW-G965USQS6CSH3-20190822152617
Now I see why nobody dared to reply to my post... I think I covered all the bases here, otherwise please let me know.
Click to expand...
Click to collapse
Turn off the fingerprint gestures I had that problem and after turning the gestures off it started to be Normal
pshrey said:
Turn off the fingerprint gestures I had that problem and after turning the gestures off it started to be Normal
Click to expand...
Click to collapse
Nah... I never had those gestures activated to begin with. Besides, I performed a hard reset and even flashed different firmwares with no luck. Only option now is to replace the fingerprint sensor.
You're not the only one with this problem. The solution is to turn off fingerprint unlocked.
https://us.community.samsung.com/t5...screen-shut-off-fingerprint/m-p/470863#M13720
I hate to bump a old thready but I just got the s9 new to replace my s7. Upon setting up the phone with my finger print I am experiencing the same exact problem... Has this not been solved? Also turning off finger print log in seems like it's not addressing the issue. I've never had this problem with my s7 and feel like this isn't going to be good if a new s9 is already experiencing this problem...
Thanks,
-Nigel
I have as SM-G991U (256 GB S21 US version, stock everything but using Nova Launcher) that is randomly freezing/crashing then rebooting on me 1-2 times/day. Does android have any kind of crash log I could look at to try and figure out what's causing the problem? On the samsung forums, their support reps suggest running in Safe Mode, which I have, but it's not very useful because I can't reproduce the problem on demand and it usually happens 1-2/day, but sometimes less, so unless I just ran in safe mode all the time, that wouldn't tell me much. Plus, it would only tell me it's an issue caused by one of a hundred or so apps which, again, is not helpful.
So I'm hoping there is a crash log or something somewhere because I have no idea what triggers the crashes. The other night, it was sitting on a wireless charger, the screen wasn't on, then all the sudden it rebooted. It's not specific to any app or anything I'm doing. If there are no crash logs (which would be frustrating and disappointing), any other troubleshooting ideas are welcome!
Look for a memory leak. Typically a poorly written 3rd party apk.
Try clearing system cache.
Make sure auto restart isn't enabled...
dougleto said:
I have as SM-G991U (256 GB S21 US version, stock everything but using Nova Launcher) that is randomly freezing/crashing then rebooting on me 1-2 times/day. Does android have any kind of crash log I could look at to try and figure out what's causing the problem? On the samsung forums, their support reps suggest running in Safe Mode, which I have, but it's not very useful because I can't reproduce the problem on demand and it usually happens 1-2/day, but sometimes less, so unless I just ran in safe mode all the time, that wouldn't tell me much. Plus, it would only tell me it's an issue caused by one of a hundred or so apps which, again, is not helpful.
So I'm hoping there is a crash log or something somewhere because I have no idea what triggers the crashes. The other night, it was sitting on a wireless charger, the screen wasn't on, then all the sudden it rebooted. It's not specific to any app or anything I'm doing. If there are no crash logs (which would be frustrating and disappointing), any other troubleshooting ideas are welcome!
Click to expand...
Click to collapse
Hi mate
For logs info check here and here
You can always flash firmware , using home_csc , to avoid factory reset the phone , if the problem is system related it will help
If is app related
Try booting in safe mode to see if problem goes away...
MAX 404 said:
Hi mate
For logs info check here and here
You can always flash firmware , using home_csc , to avoid factory reset the phone , if the problem is system related it will help
If is app related
Try booting in safe mode to see if problem goes away...
Click to expand...
Click to collapse
Thanks! I'll definitely try these out. I tried safe mode, the trouble is it's not really great as a diagnostic because the phone will go from 4-24 hrs between resets during normal operation, and since a phone in safe mode isn't terribly useful, it's hard to keep it in safe mode for long enough to see if that fixed the issue, if that makes sense. And then, if it did fix the issue, it just narrows it down to 1 out of a hundred apps! But maybe I'm missing something. Is there additional information I can find if I run in safe mode that would help suss out the problem?
blackhawk said:
Look for a memory leak. Typically a poorly written 3rd party apk.
Try clearing system cache.
Make sure auto restart isn't enabled...
Click to expand...
Click to collapse
Thanks! I know how to clear cache but not how to check for memory leaks. Do you have a tool you'd recommend to do that? And I had never heard of auto restart before, so thanks for that. I confirmed that it is NOT enabled (that would have been a face palm moment!).
dougleto said:
Thanks! I'll definitely try these out. I tried safe mode, the trouble is it's not really great as a diagnostic because the phone will go from 4-24 hrs between resets during normal operation, and since a phone in safe mode isn't terribly useful, it's hard to keep it in safe mode for long enough to see if that fixed the issue, if that makes sense. And then, if it did fix the issue, it just narrows it down to 1 out of a hundred apps! But maybe I'm missing something. Is there additional information I can find if I run in safe mode that would help suss out the problem?
Click to expand...
Click to collapse
Is not easy , you just need to be methodic
See if you can find anything useful in the logs first
Reflash firmware , use home-csc , see if it help
Have you notice if the phone fails under any specific circumstances?
If that does not help and if you can really relate the problem with any specific app you may try to freeze or uninstall suspicious app and let it run for a day , Package disabler app is a good option , it is easy to enable or disable app but is not free, you could try this one , is a debloater tool , it allow you to disable app... may be easy that having to uninstall / install by hand
I'm also having the same problem. Had the phone since June, it didn't start to occur until late August, which leads me to suspect it is an update related issue.
GillBates21 said:
I'm also having the same problem. Had the phone since June, it didn't start to occur until late August, which leads me to suspect it is an update related issue.
Click to expand...
Click to collapse
I'm glad you posted today, I've been meaning to post again here because I tried troubleshooting and am still having issues. In fact, it crashed twice today when I was trying to send a text message.
I installed one of the log applications (can't remember which one at the moment) but it wasn't really helpful. They didn't seem to catch any information related to a crash even though they were logging data at least twice when it crashed.
Then I tried reflashing using home-csc using ODIN and that ended up soft-bricking my phone (and yes, I followed all the instructions and used home-csc) so I had to reflash everything and do a full factory reset. That seemed to help, reducing the crashes from once/day to once/2-3 days for a few weeks, but now it's back to ~once a day (sometimes more, sometimes less).
So if anyone has any other idea, I'm all ears. When I was reflashing and stuff, I noticed in the recovery mode (or whatever it's called) options that you can look at logs. Does anyone know if one of those logs would have crash-related data or any other ideas of what to try? This is incredibly frustrating, especially that it's persisting after a factory reset. Argh!
dougleto said:
I'm glad you posted today, I've been meaning to post again here because I tried troubleshooting and am still having issues. In fact, it crashed twice today when I was trying to send a text message.
I installed one of the log applications (can't remember which one at the moment) but it wasn't really helpful. They didn't seem to catch any information related to a crash even though they were logging data at least twice when it crashed.
Then I tried reflashing using home-csc using ODIN and that ended up soft-bricking my phone (and yes, I followed all the instructions and used home-csc) so I had to reflash everything and do a full factory reset. That seemed to help, reducing the crashes from once/day to once/2-3 days for a few weeks, but now it's back to ~once a day (sometimes more, sometimes less).
So if anyone has any other idea, I'm all ears. When I was reflashing and stuff, I noticed in the recovery mode (or whatever it's called) options that you can look at logs. Does anyone know if one of those logs would have crash-related data or any other ideas of what to try? This is incredibly frustrating, especially that it's persisting after a factory reset. Argh!
Click to expand...
Click to collapse
So what I tried to do is roll back all the default google app updates. Ex: Android system webview, Google app itself, etc etc. I factory reset it without backing up any apps (but pictures and messages etc), It was working for a few days and then it happened again. Which further reinforces my thinking that my problem is software based.
GillBates21 said:
So what I tried to do is roll back all the default google app updates. Ex: Android system webview, Google app itself, etc etc. I factory reset it without backing up any apps (but pictures and messages etc), It was working for a few days and then it happened again. Which further reinforces my thinking that my problem is software based.
Click to expand...
Click to collapse
So I'm curious why you think that means it's a software issue. If this isn't a widespread issue with the S21 and after we've both done a factory reset and still have the issue, that makes me think it could be a hardware issue. Of course, there could be some software incompatibility with an app that most people don't have installed or a bluetooth connection or something, which is why I really want to find a useful crash log (and find it rather absurb how hard it is to find a useful crash log on android, come on guys, it's a mature OS, some kind of crash log seems pretty basic!), because otherwise, it could be a ton of issues and I can't reproduce it. Ugh.
The reason is that the "few days" after the reset and restoring pictures, messages (but not apps) from backup, where there were no crashes at all (where previously it would happen at least 2 times per day).
GillBates21 said:
The reason is that the "few days" after the reset and restoring pictures, messages (but not apps) from backup, where there were no crashes at all (where previously it would happen at least 2 times per day).
Click to expand...
Click to collapse
Got it, that makes sense. I'm on t-mobile and just got an update this morning. We'll see if that improves anything because my device restarted 4 times yesterday
I havent had a crash like this since i disabled chrome and other google stuff, and downgrading google apps lol.
GillBates21 said:
I havent had a crash like this since i disabled chrome and other google stuff, and downgrading google apps lol.
Click to expand...
Click to collapse
How did you disable chrome and what other google stuff did you disable? (There's obviously quite a lot of google services that can't be disabled)
After the most recent monthly update, my phone has gone from rebooting multiple times/day to once every 2-3 days, which is more manageable but still super annoying. It is incredibly frustrating to me that there are no good tools to troubleshoot a crash (at least that I've ben able to find). Honestly, it's driven me to consider an iPhone for the first time in my life .
My trouble is back... I will be scheduling a fix with samsung soon so I can RMA it
Check the below link. This seems to be a hardware problem which got solved after Samsung replaced the motherboard.
Samsung Restart problem
So I bought this phone for my wife. Since I received the phone, after a day the phone started crashing whatever app she was on and then take you back to lock screen without having to go through a full restart process but it was definitely a restart as you would need to enter your pin again as opposed to fingerprints.
Since it was within 15 days of purchase I returned and reordered another one from Samsung, and to my surprise exact same issue. What are the odds of having two brand new phones having exact same issues.
This leads me to believe it must be a software issue. I just received this 2nd new phone last Friday.
Yeah, I think what I was experiencing was a hardware issue (it definitely went through the full restart process, not what is described in the previous post). And from the link posted by sandystays above, it looks pretty common. I contacted Samsung support and was not impressed at all. They walked me through a number of troubleshooting steps that weren't helpful then had me take my phone to UBreakIFix. I did, they ran a diagnostic and their tools couldn't find anything wrong so they said Samsung should replace it.
Contacted Samsung, told them I had taken it in. They said I needed to take it to a technician (again, right after telling them I just had). They then said, oh, you'll have to mail it to us and you'll get your phone back in 7-10 business days. Their suggestion for what to do for a phone in the meantime? Buy a prepaid phone then return it when I get my phone back (which a) is unethical and b) wouldn't work anyways since they're locked). Ridiculous. They also admitted that this is a very common problem, so I asked why they just won't send me a replacement device if it's so common to which they had no real answer, just "that's our policy".
Eventually, I contacted T-mobile (my carrier) and was very pleasantly surprised. After me telling them the issue and the steps I'd taken to troubleshoot it, they sent me a replacement phone (recertified, but still) that arrived in 2 days. WAAAYYYY better than Samsung. The entire process made me a bit jealous of my wife's iPhone. If she had had a similar issue, we could have taken it to an apple store and not had the whole "our policy is that you have no phone for 7-10 business days" nonsense from Samsung AND the backup and restore process is still way better on iPhones than on any android I've ever owned. How there is no easy and reliable backup/restore mechanism on android after so long is beyond me.
Bottome line: if you have a similar issue, it's very likely a hardware problem (my replacement phone has been fine for 3 days now). And avoid Samsung support if you can!
dougleto said:
Yeah, I think what I was experiencing was a hardware issue (it definitely went through the full restart process, not what is described in the previous post). And from the link posted by sandystays above, it looks pretty common. I contacted Samsung support and was not impressed at all. They walked me through a number of troubleshooting steps that weren't helpful then had me take my phone to UBreakIFix. I did, they ran a diagnostic and their tools couldn't find anything wrong so they said Samsung should replace it.
Contacted Samsung, told them I had taken it in. They said I needed to take it to a technician (again, right after telling them I just had). They then said, oh, you'll have to mail it to us and you'll get your phone back in 7-10 business days. Their suggestion for what to do for a phone in the meantime? Buy a prepaid phone then return it when I get my phone back (which a) is unethical and b) wouldn't work anyways since they're locked). Ridiculous. They also admitted that this is a very common problem, so I asked why they just won't send me a replacement device if it's so common to which they had no real answer, just "that's our policy".
Eventually, I contacted T-mobile (my carrier) and was very pleasantly surprised. After me telling them the issue and the steps I'd taken to troubleshoot it, they sent me a replacement phone (recertified, but still) that arrived in 2 days. WAAAYYYY better than Samsung. The entire process made me a bit jealous of my wife's iPhone. If she had had a similar issue, we could have taken it to an apple store and not had the whole "our policy is that you have no phone for 7-10 business days" nonsense from Samsung AND the backup and restore process is still way better on iPhones than on any android I've ever owned. How there is no easy and reliable backup/restore mechanism on android after so long is beyond me.
Bottome line: if you have a similar issue, it's very likely a hardware problem (my replacement phone has been fine for 3 days now). And avoid Samsung support if you can!
Click to expand...
Click to collapse
On the second phone I still have the 2wk window to return. I am contemplating if I should just return altogether. I had bought an s21 Ultra as well and that seem to be working OK.
Two s21+ phones with same issue, what are the odds of hardware problem? But what if it is the entire batch that is bad.
isiddiqi said:
On the second phone I still have the 2wk window to return. I am contemplating if I should just return altogether. I had bought an s21 Ultra as well and that seem to be working OK.
Two s21+ phones with same issue, what are the odds of hardware problem? But what if it is the entire batch that is bad.
Click to expand...
Click to collapse
Your issue sounds different to me. Mine definitely fully rebooted, I have no idea what is going on with yours, it sounds like your crashes are locking the phone or something, that could definitely be software. Good luck!
Cheers everyone,
have been using my Asus ROG Phone 6 (12GB/256GB version) for 2 weeks now and have several issues.
The main issue is that the phone will freeze, especially when using the camera app, then crash and sometimes won't reboot and is stuck in a boot loop.
Happened to me twice already so had to set it up twice now, which takes quite some time until everything is set up again.
Does anyone know if there is already a solution for this? Does anyone else had this problem already?
Baseband-Version is: M2.13.33.16-Dallas_000370
Kernel-Version: 5.10.101-android12-9-00001
Build Number: SKQ1.220406.001.WW_Phone-32.2810.2207.134-0 release keys
Thanks everyone!
Scrutinize your 3rd party apps... especially power management or 3rd party launchers if any.
Likely an app with cam permissions otherwise.
Possible firmware corruption or a hardware failure.
Yesterday, when it happened, I tried and had no other apps installed other than the ones from the factory. Launcher has been stock all the time.
Will investigate further, thanks for your hints! Will contact Asus for an update.
Sent it back. That's not normal...
Yeah, opened up a ticket already, waiting for them to get back to me though.
I thought there was maybe an easy fix for this or that it is a known issue with a fix around though.
Hi GrossmeisterB, i am new here, my Rog Phone 6 keep boot loop as well, when i power on after half way charging for zero %. may i know, do you flash rom or just factory reset? i tried factory reset, but problem still not solved
Hi there, first, short update on my phone: sent it back to the shop and got a new one that is now working flawlessly. So it seems the camera issue was due to a hardware error.
I just did factory resets to not void the warranty.
It seems like you need to return yours, too...