My phone rebooted on me today while using the flashlight (something that occasionally happens from time to time), and now my fingerprint reader doesn't seem to work.
It says Fingerprint Hardware Not Available when I try to use it from the lock screen. The actual hardware itself is working, as I can still go into settings and try to set up a new fingerprint, it will vibrate and show that I touched the sensor as I move my finger, but then it fails at the end saying "enrollment not completed".
I also can't delete any of my saved fingerprints. It seems to get stuck trying to delete when I click one to remove. I'm thinking some sort of security thing got messed up when it rebooted, and I don't know how to fix it. I am rooted, so I already tried wiping cache and dalvik from TWRP. Not sure how to remove fingerprint data and start over... is there a way to do that?
I'm running the latest PE rom (flashed last week), and no, I didn't flash from Nougat in case anyone thinks this is that common issue some people have. I would try the fix for that, but since it isn't the cause of my problem I'm afraid it might mess things up more. Would really rather not hard reset again, took too long to get my phone set up with everything and paired again.
Dishe said:
My phone rebooted on me today while using the flashlight (something that occasionally happens from time to time), and now my fingerprint reader doesn't seem to work.
It says Fingerprint Hardware Not Available when I try to use it from the lock screen. The actual hardware itself is working, as I can still go into settings and try to set up a new fingerprint, it will vibrate and show that I touched the sensor as I move my finger, but then it fails at the end saying "enrollment not completed".
I also can't delete any of my saved fingerprints. It seems to get stuck trying to delete when I click one to remove. I'm thinking some sort of security thing got messed up when it rebooted, and I don't know how to fix it. I am rooted, so I already tried wiping cache and dalvik from TWRP. Not sure how to remove fingerprint data and start over... is there a way to do that?
I'm running the latest PE rom (flashed last week), and no, I didn't flash from Nougat in case anyone thinks this is that common issue some people have. I would try the fix for that, but since it isn't the cause of my problem I'm afraid it might mess things up more. Would really rather not hard reset again, took too long to get my phone set up with everything and paired again.
Click to expand...
Click to collapse
Reflash PE. If that doesn't work do a clean flash.
Boot into TWRP
Go to advanced>filemanager to acces the files in your phone.
Enter the folder /data/system/user/0
Delete following files: ./fpdata/user.db, settings_fingerprint.xml
Reboot to system and set up new fingerprints with the fingerprint wizard
Everything should work normal
Related
Well this is my 1st post so first of all hey everyone
I just spent a week in Amsterdam and my phone restarted twice, different times different days and I dont remember what I was doing with it back then.
But as I landed back home I put the phone back from "Airplane Mode" and went on to toggle "Cellular Data" on.
The second I pressed the cellular data shortcut on my the phone restarted itself but this time whenever it would finish the screen would be on but fully black and sometimes it'll show battery precentage at the top but then will restart again in an infinite loop.
Sometimes it'll pop up the "Optimizing Apps" window and will go through all 24, upon finishing it will restart once more and do the same.
I tried using the bootloader and it worked (the bootloader that is) but the phone would do the same thing even after Rebooting from there or shutting down from there and then turning back on.
I contacted tech support on chat but they couldnt help past telling me to go to bootloader and reboot, said I should factory wipe when it failed.
Also tried wiping cache but to no avail.
I have no backup of my phone (wanted to do one before the flight but got lazy and I suck for not doing one sooner) since probably October and google doesnt backup my contacts properly for some unknown reason.
I already downloaded Android Studio with everything included for me to try using adb to sideload stock without wiping but its my first time and I couldnt get it to do anything at all...
I already got the official stock .gz file from the motorola website.
Anyway here are the specs to my phone:
XT1575
Everything is stock. didn't root or change recovery once in my life.
Was fully updated and had plenty of drive space (I have almost 128GB with the 64GB version + 64GB SD)
I'm really lost here so help will be very appreciated.
Thanks in advance,
-Noam
Start with a full wipe and if that doesn't work flash the stock image. Not sure what your question is though as you never really say. Once fixed I would unlock and make a backup so you don't have to deal with this again.
lafester said:
Start with a full wipe and if that doesn't work flash the stock image. Not sure what your question is though as you never really say. Once fixed I would unlock and make a backup so you don't have to deal with this again.
Click to expand...
Click to collapse
The thing I pretty much want to know is if theres a way to either backup the phone now with it connected to the computer while in bootloader or recovery. or a way to flash the stock rom without wiping which I read someone did with his tablet. I cant post source normally because I'm a new user so here it is but change spaces to dots: schnouki net/posts/2014/08/13/flashing-a-stock-android-image-without-wiping-user-data/
Also while in recovery I noticed 2 options under wipe: 1. userdata only. 2. userdata+(insert something I dont remember here) and I was wondering what gets deleted in both? if I delete only userdata what data will remain? something helpful?
Sure you can try flashing without wiping data but being locked I personally wouldn't risk it. No idea about backing up in your state... somewhere I remember a thread on backing up without root try searching in q&a.
lafester said:
Sure you can try flashing without wiping data but being locked I personally wouldn't risk it. No idea about backing up in your state... somewhere I remember a thread on backing up without root try searching in q&a.
Click to expand...
Click to collapse
Out of curiosity why shouldnt I try flashing with no wipe if ill lose the data anyway? worst case wont I just have to wipe after it fails and flash again?
And I will try thank you
Do you have any knowledge about the 2 wipe options?
Thanks in advance
Well I tried turning the phone on and it took a couple of minutes before loading to a fresh start. It apparently wiped itself on its own. Managed to restore almost everything.
Anyhow the phone takes too long to boot now. Was even stuck at boot and I had to restart it.
Anyway to fix my software? Or at least check for corruption?
Sent from my XT1575 using XDA-Developers mobile app
This is on two standard Galaxy S5's, with standard ROM, etc - not rooted, or anything else.
Every time I turn off WiFi, or enable Mobile Hotspot, I get 'Unfortunately System UI has stopped'.
To fix I have to Power off/on the phone.
(Turning on WiFi is no problem, just turning it off.)
I have gone into 'Safe Mode', and same issue, so it looks to not be a bad App.
I have also uninstalled 'Google' updates, and again no change...
Any thoughts?
All of a sudden my S5 showed the exact same error message for no aparent reason... I didn't do anything, and now I can't use my phone at all because of that bug. It happens on every boot so I can't even unlock my phone. Tried reinstalling everything, ROM, recovery, kernel, with/without root = still same, what just happened here??
EDIT: Same thing if I'm in Safe Mode -_-
Seeing noone knows a solution here's what I did yesterday.
1. Backed up all my stuff from internal storage to the sd card
2. Did factory reset in TWRP recovery
3. Flashed completely stock official firmware from Samsung
4. Waited for it to boot up and try to restore some of my settings (it restored all folders on their places, made same amount of home screens as I had before the reinstall and downloaded all of my previously installed apps from the Play Store, ofcourse without the cracked ones, and it also restored most apps' data as well so it's not as bad as you may think to factory reset and reinstall everything)
5. Started rooting, flashing TWRP again, installing Dolby Audio, Xposed and everything I had before, took me one full day to set it up as it was before.
Now when I set it up I always make a nandroid backup from when things are working fine, in case it goes crazy for no reason again... Good luck!
when the wifi radio is acting weird, a dirty flash of your current ROM susually fixes is as its probably a radio issue. Id do that before doing anything drastic like the boot-n-nuke Odin flash and starting from scratch (which will fix that issue)
I don't think I have a ROM issue, as I have two S5's, and both have the same issue... and both are standard ROMs.
I will do a factory re-set on one at some point, but this looks to be a 'simpler' issue.
I have tried a full Cache delete, as well as other 'clean' processes.
Nothing works.
I tried to re-flash my stock ROM as @youdoofus said but still had that annoying popup. Try everything you can think of, if all else fails, reset.
koragg97 said:
I tried to re-flash my stock ROM as @youdoofus said but still had that annoying popup. Try everything you can think of, if all else fails, reset.
Click to expand...
Click to collapse
well, you can wipe cache, and dalvik 3x each (not kidding about the 3x each), then dirty flash the rom, pray to the gods of android, reboot. If failure occurs, its Odin Nuke time unless you want to try to flash an individual radio file by itself (not recommended)
Hey folks,
I did not find anything on this issue, seems to be rather unique. Let me describe the problem.
This is my father's Axon 7 and he wanted me to get him a different ROM on there, which I did, and it worked smoothly until today. It kept crashing, freezing and was literally unusable for unknown reasons.
So since he was going to be gone for the next few days, I had no choice but to remove the ROM and data and reflash it. HOWEVER I did not delete the internal storage since I did not think it would be necessary. Sitting in the setup, I had issues getting through it, it will not pop up the keyboard to let me type the wifi password neither does it let me pass through if I wanted to use mobile data. It simply gets stuck. Sometimes random android processes tend to crash and put me at the start of the setup and I can't get to the settings which does prevent me from enabling USB-debugging or OEM unlock.
If I try to get into the recovery (which is still on there) it will simply get stuck on the screen that says ZTE, did not work through fastboot either, same issue.
(I do personally think that some app data is corrupted and causes the issue, since I wiped everything except internal storage and I still have major issues)
So here am I, stuck. I hope someone can enlighten me, or tell me how stupid I am and point me at something completely obvious. Thanks
OmegaFighter said:
Hey folks,
I did not find anything on this issue, seems to be rather unique. Let me describe the problem.
This is my father's Axon 7 and he wanted me to get him a different ROM on there, which I did, and it worked smoothly until today. It kept crashing, freezing and was literally unusable for unknown reasons.
So since he was going to be gone for the next few days, I had no choice but to remove the ROM and data and reflash it. HOWEVER I did not delete the internal storage since I did not think it would be necessary. Sitting in the setup, I had issues getting through it, it will not pop up the keyboard to let me type the wifi password neither does it let me pass through if I wanted to use mobile data. It simply gets stuck. Sometimes random android processes tend to crash and put me at the start of the setup and I can't get to the settings which does prevent me from enabling USB-debugging or OEM unlock.
If I try to get into the recovery (which is still on there) it will simply get stuck on the screen that says ZTE, did not work through fastboot either, same issue.
(I do personally think that some app data is corrupted and causes the issue, since I wiped everything except internal storage and I still have major issues)
So here am I, stuck. I hope someone can enlighten me, or tell me how stupid I am and point me at something completely obvious. Thanks
Click to expand...
Click to collapse
well, you can use EDL maybe?
The fastest way out is downloading the A2017G_FULL_EDL file from our Russian friends and use MiFlash while in EDL mode to flash the cluster**ck of a phone that you have.
The closest thing I've seen was a friend's Galaxy Grand 2 (like 5 years old) that maybe had a part of the system corrupted or a slightly dead eMMC. a bunch of stuff just crashed for no apparent reason. I reflashed the system and it got fixed for some time, then it started doing some weird sh!t again (after booting, you have an 80% chance that it will just freeze forever, hard reboot needed). But let's hope for the best and see if you can recover it by reflashing stock totally. If it still doesn't work you might be able to relock the BL and claim the warranty
Choose an username... said:
well, you can use EDL maybe?
The fastest way out is downloading the A2017G_FULL_EDL file from our Russian friends and use MiFlash while in EDL mode to flash the cluster**ck of a phone that you have.
The closest thing I've seen was a friend's Galaxy Grand 2 (like 5 years old) that maybe had a part of the system corrupted or a slightly dead eMMC. a bunch of stuff just crashed for no apparent reason. I reflashed the system and it got fixed for some time, then it started doing some weird sh!t again (after booting, you have an 80% chance that it will just freeze forever, hard reboot needed). But let's hope for the best and see if you can recover it by reflashing stock totally. If it still doesn't work you might be able to relock the BL and claim the warranty
Click to expand...
Click to collapse
Hey,
After a long day I managed to fix it, I was able to use the adb in fastboot and could reinstall the recovery and managed to run it, deleted internal storage and reinstalled everything. Seems to have done the trick. I hope it will keep working now.
OmegaFighter said:
Hey,
After a long day I managed to fix it, I was able to use the adb in fastboot and could reinstall the recovery and managed to run it, deleted internal storage and reinstalled everything. Seems to have done the trick. I hope it will keep working now.
Click to expand...
Click to collapse
good
Hello guys !
I was rocking OOS 4.5.3 with TWRP and root all fine, and I tried some dualboot stuff that I saw here on XDA (plot twist, don't try it) and then I ran into issues
I managed to reinstall the rom fine, but at the reboot, my fingerprint sensor wasn't picking up my fingers
I found out that when I try to register a fingerprint, it works fine, untill the last step where it stop picking my finger (not even vibrates)
I also noticed that it's impossible to delete a stored fingerprint
Any ideas ?
GMX1PT said:
Hello guys !
I was rocking OOS 4.5.3 with TWRP and root all fine, and I tried some dualboot stuff that I saw here on XDA (plot twist, don't try it) and then I ran into issues
I managed to reinstall the rom fine, but at the reboot, my fingerprint sensor wasn't picking up my fingers
I found out that when I try to register a fingerprint, it works fine, untill the last step where it stop picking my finger (not even vibrates)
I also noticed that it's impossible to delete a stored fingerprint
Any ideas ?
Click to expand...
Click to collapse
On man I'm in totally the same situation with you! I tried that dualboot too and stuck in boot screen, so i flashed the original rom zip and managed to boot well but the fingerprint isn't working any more......:crying:waiting for solutions
Okay, now that I woke up I will try to do a data wipe, I'll tell you about it, please do tell me if you find something
I'm also unable to activate wifi
Sounds like a good question for the dual boot thread.
If I remember right from previous threads about dual boot on other devices is, you should delete your original fingerprint or set it up as no lock before doing all the stuff with dual boot. I might be wrong.
ab7casper said:
Sounds like a good question for the dual boot thread.
If I remember right from previous threads about dual boot on other devices is, you should delete your original fingerprint or set it up as no lock before doing all the stuff with dual boot. I might be wrong.
Click to expand...
Click to collapse
Well, can't see where it is listed in the instructions, but thankfully this issue is nothing a full wipe can't fix
GMX1PT said:
Well, can't see where it is listed in the instructions, but thankfully this issue is nothing a full wipe can't fix
Click to expand...
Click to collapse
It's not, it was just a user having that issue on a Nexus 6P. Reset should fix. Set it up without a lock on it, then you should be able to set up fingerprints for each rom.
Thinking about. It, that sounds like a lot of hassle if you just want to try out different roms quickly.
GMX1PT said:
I'm also unable to activate wifi
Click to expand...
Click to collapse
I did not do this dual boot but I ran into WiFi not activating (endless searching for a WiFi access point), but I was able to fix it. Your probably uninterested in how I got into the situation but I fixed it with a previous nandroid backup done with one of the earlier versions of TWRP. Here are the steps that recovered WiFi:
Using TWRP, advance wipe Dalvik & Cache
Restore from a nandroid backup (OOS v4.5.2 in this case) ONLY system & /System
Reboot into the system and ignore TWRP's no OS warning
Using TWRP, advance wipe Dalvik & Cache
Reboot back into TWRP recovery and flash the Full v4.5.5 OTA file (~1.6GB) AND flash root (e.g. SuperSU)
Clear Dalvik&Cache and reboot into the system
After I did that everything return back to normal including the WiFI issue. The fingerprint scanner is working normally and I never lost any data what so ever.
i successfully downgraded my A2017G to Oreo b02 from b03 about a week ago. I had to do a factory reset, then set it up with my Google account and after that it allowed to install b02.
After that I've only installed a few basic apps for my bank and so on while waiting for b04 to show up through OTA.
Anyway, fast forward to today. I haven't had any issues with it. But all of a sudden when coming back from working in another town its rebooted and ask me to enter PIN to start Android. After that when it's done rebooting I got some weird double spacing between rows of icons.
So, I reboot again and once more i have to enter pin to start Android.. But it looks better when finished. However, this Enter PIN to start Android feels a bit annoying. Apparently it's because Android thinks my phone is behaving strange. Is there a way to find out what it thinks is strange and stop it?
It may be a security requirement for your banking app. It's secure boot.
This is part of the options with lock screen method. Maybe try setting the phone back to a swipe unlock and restart, see if it stops the problem. If so, set up you preferred lock arrangement again.
Thanks. Sounds reasonable although I've been running these apps on this phone since I bought it back in 2016(maybe it's time for a new phone) with various Android versions and never had this before. The phone has also been running for about a week with the same ROM and app version before this happened.
I'd backup data and reset it. See if it runs better, but you could try going to stock recovery and clear the cache first, just in case that helps.
There may be some junk from flashing it.
Seems like a factory reset did the trick. It's been running smoothly for some time nu despite installing the same apps again. I even got the b04 upgrade through OTA. Thanks!
Cool, so you're happy with the A7 again?
I regressed mine from B03 to B02 and did forced update to B04 from stock recovery. Had a few hiccups but sorted them and it works ok now. Do want to reset it when practical though. I use it for work so not in a huge hurry, setup is a big deal........
RobboW said:
Cool, so you're happy with the A7 again?
Click to expand...
Click to collapse
Sort of happy I guess. There are still a few things like it not automatically mounting my sdcard after reboot and I'm a little thoughtful about how many more updates it will receive. But it works rather well now and I haven't found a suitable replacement yet so I'm happy with it for the moment.