So I was running CF 1.3 base for quite a while with no issues. Two days ago my phone shut down on me and would not boot. I wipe everything multiple times. I wiped cache. I did a factory reset, nothing... I wiped again. Nothing.
It gets past the Motorola logo and then just sits at the boot screen. A couple of times it would say updating android, it would finish, but then it would go right back to the boot screen. After about 8 hours it finally booted and I used it all day yesterday. This morning my issue is back. I've flashed different images to see if it has something to do with 1.3. It's all the same. I think I might try to go back to kit kat. It seems to be a software problem, but I am starting to think that something most be wrong with my hardware.
I found this thread: https://forums.motorola.com/posts/b0021413e7
I think my phone is shot... Any ideas?
When I had my Razr Maxx I had an issue that was similar and nothing I tried would fix it. Factory reset cache wipe flashing different roms nothing. Finally I decided to factory restore it with RSD Lite and after that the problem went away and I was able to do everything again like normal. I don't know why a factory reset wouldn't fix it and that did but it did.
Thanks. That is my next step. Do you know where I can find the RSD image?
Is this what I need? http://forum.xda-developers.com/dro...quark-stock-firmware-moto-maxx-droid-t3063470
Do I need to worry about flashing radios and stuff back to 4.4.4?
Seems to be. Honestly I've used it on many Motorolas in the past but I haven't read much about using RSDlite on the turbo. I would just do some googling around I'm sure you'll find it
my2cents said:
So I was running CF 1.3 base for quite a while with no issues. Two days ago my phone shut down on me and would not boot. I wipe everything multiple times. I wiped cache. I did a factory reset, nothing... I wiped again. Nothing.
It gets past the Motorola logo and then just sits at the boot screen. A couple of times it would say updating android, it would finish, but then it would go right back to the boot screen. After about 8 hours it finally booted and I used it all day yesterday. This morning my issue is back. I've flashed different images to see if it has something to do with 1.3. It's all the same. I think I might try to go back to kit kat. It seems to be a software problem, but I am starting to think that something most be wrong with my hardware.
I found this thread: https://forums.motorola.com/posts/b0021413e7
I think my phone is shot... Any ideas?
Click to expand...
Click to collapse
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
Click to expand...
Click to collapse
That makes sense, after I finally got mine going, I updated Moto Actions and all the other apps it crashed again in about 12 hours. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Edit, which rootjunky image did you flash? SU2-12?
my2cents said:
That makes sense. Like an idiot, after I finally got mine going, I updated Moto Actions and it crashed again. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Click to expand...
Click to collapse
I did get it booted again. I flashed the kitkat update (not the stock, stock update 1, which is what you should be on if you're using mofo) file on the firmware thread that was posted here using the version of RSDlite that was posted there. The key is just to wait a really, really long time. Even if the screen goes black, it could potentially still be booting, especially if the back of the phone gets warm. I left it plugged in, let it get to the boot animation and left the house for several hours, and when I got back it appeared to be functional, but things were slow and choppy at times and my home button didn't work. The settings menu from the pull down menu didn't work either. I had to access settings from the app drawer. I tried a factory reset from the settings menu, and that just re-broke everything. So now I'm back at square one. I re-flashed the same image using RSDlite again, and now I've waited about 10 minutes and I'm still looking at the boot screen, which at this point is normal since the problem occurred.
I got a hold of an old copy of the Motorola Sensor Services apk. As far as I can tell, this is the apk that is replaced by Moto Actions, which according to Google Play is only compatible with 5.0 and above. My plan for tonight is to wait until the thing decides to boot, attempt to start the stock Sensor Services app and get it to do the sensor firmware uninstall that I mentioned in my other post. If that doesn't work, I'm going to try to install the apk that I found and see if I have any more luck with that. I'll report back here when I get a chance to do that. Let me know if you figure out a solution.
---------- Post added at 03:48 PM ---------- Previous post was at 03:33 PM ----------
my2cents said:
That makes sense, after I finally got mine going, I updated Moto Actions and all the other apps it crashed again in about 12 hours. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Edit, which rootjunky image did you flash? SU2-12?
Click to expand...
Click to collapse
Yeah, I used SU2-12.
I followed the procedure outlined here to go back to stock. https://www.youtube.com/watch?v=6avEPGWB8E0 I used the SU2-12 file, but I lost everything... Thanks for the help. I hope there is a fix for this soon! I'll test your idea about MOTO Actions and report.
Edit: Well, I thought my phone was booting when I wrote the above, but it has been 30 minutes and it has not booted...
So, I can get it to boot - although it is not easy and it takes me like 30 minutes and I haven't found a full proof method yet, but after it goes to sleep I have to start the process all over. It has been a frustrating 3 days.
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
Click to expand...
Click to collapse
I think you are onto something. I'm currently on 4.4.4 and it is bone stock. When I go into the Play Store it shows that I have Moto Actions installed, but when I click on the app it says that it is not compatible with my device. I've tried wiping the data from the app, force closing it, and clearing the cache. None of that has prompted me to uninstall the sensors. By the way, I found the Moto sensors app and tried doing the same thing, no luck.
So, I think I have the 5.1 Moto Actions installed still, which is causing the 4.4.4 image to freak out. I've thought about trying to go official 5.1 and see if that fixes it, but since I have a replacement on the way, think I might just leave it be - unless someone (like you) figures this thing out.
my2cents said:
I think you are onto something. I'm currently on 4.4.4 and it is bone stock. When I go into the Play Store it shows that I have Moto Actions installed, but when I click on the app it says that it is not compatible with my device. I've tried wiping the data from the app, force closing it, and clearing the cache. None of that has prompted me to uninstall the sensors. By the way, I found the Moto sensors app and tried doing the same thing, no luck.
So, I think I have the 5.1 Moto Actions installed still, which is causing the 4.4.4 image to freak out. I've thought about trying to go official 5.1 and see if that fixes it, but since I have a replacement on the way, think I might just leave it be - unless someone (like you) figures this thing out.
Click to expand...
Click to collapse
I ended up getting a replacement from Motorola too. If it has 5.1 on it, I'll sell it and get one with 4.4.4. Thanks a lot for the tip, by the way. I might still work on it just as a hobby, but I'm out of ideas. Of all the many, many devices I've tinkered with, this is the first one that I ever permanently messed up, so I'd like to fix it as a matter of pride, but I now only have 48 hours to do so. After looking at logcats, the partition table of the phone and the androidmanifest.xml of the motorola sensor services apk, I'm pretty much certain that this app writes those sensor drivers to a partition other than the ones that get flashed when we up/downgrade (ie system, boot, recovery, etc.), which is why these processes don't fix the problem. Theoretically, if I knew which partition that was, I could find someone with a working Turbo who could dump that image, and if I get lucky and it's a partition that isn't sig checked by the bootloader (like the radios, for example), I could flash that and be good to go. I have no idea how to figure out which partition that would be, though. The obvious choice was the "firmware" partition, but that partition has a lot of drivers that seem to relate to lots of different important things, so messing with that seems scary. I also don't know anyone who is knowledgeable enough to generate that image (myself included), so it's a moot point.
TheSt33v said:
I ended up getting a replacement from Motorola too. If it has 5.1 on it, I'll sell it and get one with 4.4.4. Thanks a lot for the tip, by the way. I might still work on it just as a hobby, but I'm out of ideas. Of all the many, many devices I've tinkered with, this is the first one that I ever permanently messed up, so I'd like to fix it as a matter of pride, but I now only have 48 hours to do so. After looking at logcats, the partition table of the phone and the androidmanifest.xml of the motorola sensor services apk, I'm pretty much certain that this app writes those sensor drivers to a partition other than the ones that get flashed when we up/downgrade (ie system, boot, recovery, etc.), which is why these processes don't fix the problem. Theoretically, if I knew which partition that was, I could find someone with a working Turbo who could dump that image, and if I get lucky and it's a partition that isn't sig checked by the bootloader (like the radios, for example), I could flash that and be good to go. I have no idea how to figure out which partition that would be, though. The obvious choice was the "firmware" partition, but that partition has a lot of drivers that seem to relate to lots of different important things, so messing with that seems scary. I also don't know anyone who is knowledgeable enough to generate that image (myself included), so it's a moot point.
Click to expand...
Click to collapse
My question is why hasn't anyone else's device gotten borked since the update? I've had it since the update was distributed with no issues and use Moto Actions continuously. Seems like if it really is a combination of writing drivers to a partition that isn't compatible it would be a universal issue. If only 2 people who have a mofo'd 5.1 IMG (out of probably hundreds) experienced issues my bet is on some weird glitch that occured when you initially flashed the updated firmware to get 5.1 working on the mofo'd device, rather than some general driver incompatibility.
GeoFX said:
My question is why hasn't anyone else's device gotten borked since the update? I've had it since the update was distributed with no issues and use Moto Actions continuously. Seems like if it really is a combination of writing drivers to a partition that isn't compatible it would be a universal issue. If only 2 people who have a mofo'd 5.1 IMG (out of probably hundreds) experienced issues my bet is on some weird glitch that occured when you initially flashed the updated firmware to get 5.1 working on the mofo'd device, rather than some general driver incompatibility.
Click to expand...
Click to collapse
I agree. Either it was a corrupt driver installation that worked just well enough for the app not to realize it, or the firmware update happens silently only when requested (similar to Google play services), and we're all one chop chop flashlight away from a phone apocalypse. Hopefully it's the former.
So, I went ahead and updated my device to official 5.1 and the problem is still there. The moto actions app that is installed still says that it is not compatible with my phone. I have cant figure out how to clear it or delete it or anything. And when I think I have it, I let the phone sleep and I can't bring it back to life again without waiting for a 15 min+ boot. Oh well, at least the bootloader says "official" now rather than "modified." So, Motorola should not complain about it. Thanks for trying to figure it out @TheSt33v
my2cents said:
So, I went ahead and updated my device to official 5.1 and the problem is still there. The moto actions app that is installed still says that it is not compatible with my phone. I have cant figure out how to clear it or delete it or anything. And when I think I have it, I let the phone sleep and I can't bring it back to life again without waiting for a 15 min+ boot. Oh well, at least the bootloader says "official" now rather than "modified." So, Motorola should not complain about it. Thanks for trying to figure it out @TheSt33v
Click to expand...
Click to collapse
Good to know. I picked the $25 option specifically because the free one requires an inspection, but I'll probably update it anyway. I'm not surprised that it didn't solve the problem though. When we flash those upgrade/downgrade images, we're basically just doing manually what RSD lite/Verizon upgrade agent does automatically.
ctopher4
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.[/QUOTE]
you called it! Just spent 2 hours reflashing 1.3 first repeated V4A, then Base. flashing sick Android upon Recovery attempt, FAIL. reflashed radios and such and with different "vol& pwr" sequence was able to get in to wipe cache. Not hat it would help me but i viewed chche Logs and im wondering if, to the right person, it would help to have copies of them?? It's a bunch of pages tho and and not sure if it would help.
My plan it to, in Recovery, Factory wipe, then reboot to Bootloader and attempt to flash base. W/ all sys.img's, then wipe caches again. ihave read the whole thread early yesterday morning but i fell asleep prob 20 times during. it was like 3 ishi think SO, i'll now go re read probably to find that you've already ruled out "my plan"
Click to expand...
Click to collapse
ctopher4 said:
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.[/QUOTE]
you called it! Just spent 2 hours reflashing 1.3 first repeated V4A, then Base. flashing sick Android upon Recovery attempt, FAIL. reflashed radios and such and with different "vol& pwr" sequence was able to get in to wipe cache. Not hat it would help me but i viewed chche Logs and im wondering if, to the right person, it would help to have copies of them?? It's a bunch of pages tho and and not sure if it would help.
My plan it to, in Recovery, Factory wipe, then reboot to Bootloader and attempt to flash base. W/ all sys.img's, then wipe caches again. ihave read the whole thread early yesterday morning but i fell asleep prob 20 times during. it was like 3 ishi think SO, i'll now go re read probably to find that you've already ruled out "my plan"
Click to expand...
Click to collapse
Damn. I was hoping I was wrong. Yeah, I did what you suggested many, many times. If you end up reflashing 4.4.4 and you see the message to uninstall the sensor firmware, do it and FLASH NOTHING ELSE until a solution is found. If not, it's really easy to get a new one from Motorola.
Click to expand...
Click to collapse
TheSt33v said:
ctopher4 said:
Damn. I was hoping I was wrong. Yeah, I did what you suggested many, many times. If you end up reflashing 4.4.4 and you see the message to uninstall the sensor firmware, do it and FLASH NOTHING ELSE until a solution is found. If not, it's really easy to get a new one from Motorola.
Click to expand...
Click to collapse
O Jeez, xda gave me a " token timed out message" but only after I hit post reply and, it was a novel! I have to get at least 2.5 hours sleep tonight because that been normal lately. Besides setting up Moto functionality, I'm golden and I do have their updates blocked best I can anyway. Hope all is working.
Click to expand...
Click to collapse
ctopher4 said:
TheSt33v said:
O Jeez, xda gave me a " token timed out message" but only after I hit post reply and, it was a novel! I have to get at least 2.5 hours sleep tonight because that been normal lately. Besides setting up Moto functionality, I'm golden and I do have their updates blocked best I can anyway. Hope all is working.
Click to expand...
Click to collapse
Awesome! Well I managed to fix it too, Moto functionality included!!!! I'll explain on my other thread.
Click to expand...
Click to collapse
What was the solution that found? I'm going through the same problem.
I'd like to unlock the phone legitimately, using the T-Mobile app. I'm rooting and running a custom ROM, though, so it's no surprise that it didn't work when I tried it earlier ("not compatible with this device") or after I unrooted with SuperSu's builtin function. I assume I need to unroot and then install the stock firmware before it'll work. I just want to try to get some confirmation before I go through all that. Will that do the trick or am I SOL?
I am rooted and have a custom ROM and as long as the efs folder is stock it will work. I was able to install the sim unlock app from the play store and just click unlock and it worked.
In that case, what else could be causing my incompatibility? I talked to customer service last night and they weren't helpful. I said the app wasn't working and maybe it was because I was on a custom ROM and she just said "Yeah, maybe that's it." Maybe I should call back and try to find someone more knowledgeable.
Thought I had it when I noticed my model number was SM-G920F. Edited the build.prop to make it 920T, uninstalled and reinstalled the app, and that still didn't do it.
robosllim said:
Thought I had it when I noticed my model number was SM-G920F. Edited the build.prop to make it 920T, uninstalled and reinstalled the app, and that still didn't do it.
Click to expand...
Click to collapse
You should just look at my post about perm unlocking the phone by modifying the NV_Data.bin file. I have not tested this 100% but it currently seems to be working on My phone and my wifes phone.
djalup said:
You should just look at my post about perm unlocking the phone by modifying the NV_Data.bin file. I have not tested this 100% but it currently seems to be working on My phone and my wifes phone.
Click to expand...
Click to collapse
I saw your post, but it was the night before my departure, and I just decided to go with the legit route for the sake of time. Hopefully your method will get further testing at some point, though, because it sounds interesting.
Also, to answer the question of the thread: yes.
So last night my face unlocked just stopped working. I deleted my face data and added it again and now it still doesn't work. It just says can't verify face. Anyone else experience this?
sruel3216 said:
So last night my face unlocked just stopped working. I deleted my face data and added it again and now it still doesn't work. It just says can't verify face. Anyone else experience this?
Click to expand...
Click to collapse
Not just spontaneously as you described. It's happened to many ppl but usually immediately after they updated, or tried a custom kernel. If you are unlocked try re-flashing the last image (or probably just boot.img). If not, you could try flashing the latest OTA image via recovery.
v12xke said:
Not just spontaneously as you described. It's happened to many ppl but usually immediately after they updated, or tried a custom kernel. If you are unlocked try re-flashing the last image (or probably just boot.img). If not, you could try flashing the latest OTA image via recovery.
Click to expand...
Click to collapse
Im locked. Never unlocked or rooted. It hasn't worked ever after it stopped last night. Multiple face deletes and re-adds. Also haven't updated since last ota 3 weeks ago.
sruel3216 said:
Im locked. Never unlocked or rooted. It hasn't worked ever after it stopped last night. Multiple face deletes and re-adds. Also haven't updated since last ota 3 weeks ago.
Click to expand...
Click to collapse
...If not, you could try flashing the latest OTA image via recovery. You can find the OTA's and instructions on how to perform a "rescue OTA" on Google's Dev Site. I know it sucks not having FR because it happened to me playing around with a kernel that wasn't updated for December. I got FR back by flashing a different, updated kernel. Let us know what you decide to do and how it turns out. No telling when you will get the next OTA!
v12xke said:
...If not, you could try flashing the latest OTA image via recovery. You can find the OTA's and instructions on how to perform a "rescue OTA" on Google's Dev Site. I know it sucks not having FR because it happened to me playing around with a kernel that wasn't updated for December. I got FR back by flashing a different, updated kernel. Let us know what you decide to do and how it turns out. No telling when you will get the next OTA!
Click to expand...
Click to collapse
Ok il try that thanks!
It's just annoyed cuz my phone has been the same for weeks and never rooted. It began with a notification saying I needed to re-registered my face or it might now work. So I deleted and added and then it's never worked since
v12xke said:
...If not, you could try flashing the latest OTA image via recovery. You can find the OTA's and instructions on how to perform a "rescue OTA" on Google's Dev Site. I know it sucks not having FR because it happened to me playing around with a kernel that wasn't updated for December. I got FR back by flashing a different, updated kernel. Let us know what you decide to do and how it turns out. No telling when you will get the next OTA!
Click to expand...
Click to collapse
I dont understand why i am getting this error:
PS C:\adb> adb sideload flame-ota-qq1b.191205.012.a1-59de0d4d
adb: failed to stat file flame-ota-qq1b.191205.012.a1-59de0d4d: No such file or directory
I have the file in the adb folder where i am launching cmd. adb devices shows my device ID and "sideload"
sruel3216 said:
I dont understand why i am getting this error:
PS C:\adb> adb sideload flame-ota-qq1b.191205.012.a1-59de0d4d
adb: failed to stat file flame-ota-qq1b.191205.012.a1-59de0d4d: No such file or directory
I have the file in the adb folder where i am launching cmd. adb devices shows my device ID and "sideload"
Click to expand...
Click to collapse
Make sure you have the correct image for your device. Flame is for the 4, not 4XL. If that is the correct image for you, most errors are caused by either 1) you are not using the latest adb/fastboot binaries. If you type adb version you should get a return of 29.0.5 (October 2019). or 2) you have multiple versions of adb on your machine and verifying the version as in #1 above will alert you to that. Even if you are in the same folder, if an older version is in your PATH statement it can/will cause issues. Good luck.:good:
PS.. or you forgot to add the ZIP extension in your command? The image is a zipfile and you have to include the entire filename including the file extension. eg. flame-ota-qq1b.191205.012.a1-59de0d4d.zip
v12xke said:
Make sure you have the correct image for your device. Flame is for the 4, not 4XL. If that is the correct image for you, most errors are caused by either 1) you are not using the latest adb/fastboot binaries. If you type adb version you should get a return of 29.0.5 (October 2019). or 2) you have multiple versions of adb on your machine and verifying the version as in #1 above will alert you to that. Even if you are in the same folder, if an older version is in your PATH statement it can/will cause issues. Good luck.:good:
Click to expand...
Click to collapse
Ahh it's prob 2). I have the 4 I just posted in XL cuz there is more activity.
sruel3216 said:
Ahh it's prob 2). I have the 4 I just posted in XL cuz there is more activity.
Click to expand...
Click to collapse
Ah, ok ... just remember the file extension too. Best of luck.
v12xke said:
Ah, ok ... just remember the file extension too. Best of luck.
Click to expand...
Click to collapse
got it to flash. i forgot to add the .zip part when sideloading.
now to see if faceunlock is fixed
Edit: Faceunlock still doesnt work...
is there an app in settings that controls faceunlock that i can clear data/cache and force stop?
sruel3216 said:
got it to flash. i forgot to add the .zip part when sideloading.
now to see if faceunlock is fixed
Edit: Faceunlock still doesnt work...
is there an app in settings that controls faceunlock that i can clear data/cache and force stop?
Click to expand...
Click to collapse
Not that I am aware of... it's the phone security so I'm sure it's encrypted and on the Titan M chip (but I don't know for sure). Some folks have had to do a factory reset to fix the issue, especially if BL locked. Highly unlikely next months OTA will fix your issue. Do you have the option of unlocking? If so, now would seem a good time because you're going to lose your data either way. Anyway, start backing your stuff up and it may be time for a FDR. :crying:
v12xke said:
Not that I am aware of... it's the phone security so I'm sure it's encrypted and on the Titan M chip (but I don't know for sure). Some folks have had to do a factory reset to fix the issue, especially if BL locked. Highly unlikely next months OTA will fix your issue. Do you have the option of unlocking? If so, now would seem a good time because you're going to lose your data either way. Anyway, start backing your stuff up and it may be time for a FDR. :crying:
Click to expand...
Click to collapse
damn it lol. yeah i have the option so i might as well unlock. Il do that tonight i guess. thanks for the help!
my phone wasnt ready for 2020
sruel3216 said:
...my phone wasnt ready for 2020
Click to expand...
Click to collapse
Live and learn. Next time unlock out of the box before setting up. Even if you have no intention of ever rooting, if the "fit hits the shan"- you have more tools (and options) being BL unlocked. Cheers! :good:
v12xke said:
Live and learn. Next time unlock out of the box before setting up. Even if you have no intention of ever rooting, if the "fit hits the shan"- you have more tools (and options) being BL unlocked. Cheers! :good:
Click to expand...
Click to collapse
unlocked and faceunlock works again...for now. hopefully that doesnt happen again. Thanks for the help!
Any idea what got it back going? Mine started repeatedly notifying me last night to update my face recognition data. As soon as I deleted the old data and enrolled again, it stopped working completely. Been broken 100% ever since. Tried reenrolling a couple more times. Reboot. So far no improvement. It just rhythmically flashes 'Can't verify face. Try again.'
fastpakr said:
Any idea what got it back going? Mine started repeatedly notifying me last night to update my face recognition data. As soon as I deleted the old data and enrolled again, it stopped working completely. Been broken 100% ever since. Tried reenrolling a couple more times. Reboot. So far no improvement. It just rhythmically flashes 'Can't verify face. Try again.'
Click to expand...
Click to collapse
This same exact thing happened to me last night. Message on the lockscreen saying to re-enroll my face or it may not unlock. What was funny was that it was able to unlock every time I tried. After re-enrolling, I get the same flashing "Can't verify face. Try again." message. Wonder if there was an A/B test that went out that messed things up. Do you happen to be rooted or have any other modifications?
Tried flashing a few different kernels to see if anything would change. I'm away from my computer for another week so I can't try reflashing images. Booting into safe mode did not work. Uninstalling Magisk did not work either.
sruel3216 said:
Im locked. Never unlocked or rooted. It hasn't worked ever after it stopped last night. Multiple face deletes and re-adds. Also haven't updated since last ota 3 weeks ago.
Click to expand...
Click to collapse
Same boat (locked and stock - Verizon....tried to BL unlock when first turning on phone (removed SIM as to not activate) but that didn't work so locked it is). 2 days ago got the android notification to update my face data so I deleted it and went to re add and nothing but the cannot verify face try again messages. I just deleted face data and use my fitbit to smart unlock for now until this gets fixed to avoid having to repeatedly type my PIN in. To note I did the December update back in early December so it's odd that this has now reared it's ugly head.
Seems to have happened to a lot of people after the new year. Y2K bug twenty years later perhaps? lol
tysj said:
This same exact thing happened to me last night. Message on the lockscreen saying to re-enroll my face or it may not unlock. What was funny was that it was able to unlock every time I tried. After re-enrolling, I get the same flashing "Can't verify face. Try again." message. Wonder if there was an A/B test that went out that messed things up. Do you happen to be rooted or have any other modifications?
Click to expand...
Click to collapse
Yep, that's precisely how mine is behaving. I'm 100% stock.
The same just happened to me the last evening. Suddenly that message popped in and when I tried to delete and re-add the face unlock it completely stopped working. Pretty sure there is some Google A/B testing going on.
People reported factory reset should be the only way to fix this, so I'm gonna wait till tomorrow for the new security patches.
bakemcbride21 said:
Same boat (locked and stock - Verizon....tried to BL unlock when first turning on phone (removed SIM as to not activate) but that didn't work so locked it is). 2 days ago got the android notification to update my face data so I deleted it and went to re add and nothing but the cannot verify face try again messages. I just deleted face data and use my fitbit to smart unlock for now until this gets fixed to avoid having to repeatedly type my PIN in. To note I did the December update back in early December so it's odd that this has now reared it's ugly head.
Seems to have happened to a lot of people after the new year. Y2K bug twenty years later perhaps? lol
Click to expand...
Click to collapse
fastpakr said:
Yep, that's precisely how mine is behaving. I'm 100% stock.
Click to expand...
Click to collapse
TENN3R said:
The same just happened to me the last evening. Suddenly that message popped in and when I tried to delete and re-add the face unlock it completely stopped working. Pretty sure there is some Google A/B testing going on.
People reported factory reset should be the only way to fix this, so I'm gonna wait till tomorrow for the new security patches.
Click to expand...
Click to collapse
yup pretty annoying. think factory reset is the only fix
I have been having my phone act really messed up, even after factory reset. Here is what is happening:
Play Store freezes: Will freeze at various %, often 99 or 100, then won't install and other apps wait
When above is going on, then other things don't work: widgets don't update
Notifications don't fire, or fire very late
It is very annoying. I have tried:
Factory Refresh then restore from SmartSwitch
Factory Reset, then restore from Google
Factory REfresh and restoreo nothing
IN all those cases, it still does the same thing.
Last night, it was frozen with 20 updates waiting...when I got up this morning, they all installed 6 hours before I got up.
So, I have no confidence this will help, but I"m thinking I need to Odin a firmware down, and then install app one at a time, not restore. Maybe there is some virus in it or something.
So, I check Sammobile, and find zero firmwares for Note 9. I went to the Guides and Discussion section, and haven't found one for the SM-960U. I did find one for SM-960U1, which said was for VZW. Mine is AT&T .
If anyone can point me in the right direction, or has suggestions for fix to the problem, it would be appreciated. In the meantime, I'm going to search some more.
By the way, my current firmware is: N960SQ3CSJ1.
I have found a thread in an earlier version, but it is indicated it says this which makes me leary about using it:
Obsolete firmware
Since this firmware is long outdated and Samsung & every U.S. carrier has made their Pie firmware available to the public, this thread will be closed. Please find your carrier's current firmware from their support website or visit updato.com
Click to expand...
Click to collapse
I have also found a site or two (not sammobile.com) that list the firmware, but no instructions for install. Given some of the things that must be considered/done on these, I hope to find a thread with good instructions for doing it. It's been a few years since I have done updates and rooting, etc. (I'm aware this still has no root).
I found a download site that lists my number, but says T-Mobile. I'm aware that supposedly that should work on AT&T. I'd think if there were no difference, it would list both. So, stall wary...
Maybe I have found a thread that will get me going, here.
All the firmware is the same. It will provision to the sim you have. Use Frija. But Sammobile does have the firmware also don't know why you say it doesn't.
Sent from my SM-N975U using Tapatalk
ewingr said:
Maybe I have found a thread that will get me going, here.
Click to expand...
Click to collapse
https://www.sammobile.com/samsung/galaxy-note9/firmware/SM-N960U/USC/download/N960USQS3CSK1/307167/
I was successful installing from the site I linked.
It made zero difference to the problem. I did the firmwsre install and loaded apps one by one. Worked fine most of the day. Tonight so the problems are back.
Sigh...
Oh reason I said Sammobike didn't have it is because when I entered the one I need in the search bar of the site nothing came back.