Related
Verizon 6 here...got prompted to update. Downloaded and was ready for the install and reboot. Phone rebooted. Still 5.0? And device up to date. How can i redownload? Please help
StrangeTimes said:
Verizon 6 here...got prompted to update. Downloaded and was ready for the install and reboot. Phone rebooted. Still 5.0? And device up to date. How can i redownload? Please help
Click to expand...
Click to collapse
Do you have a custom recovery and/or rooted? If so, the OTA fails. The reminder will probably come back in a day or so.
Same thing happened to me. I received the notice literally seconds after rooting and flashing custom recovery. I tried it anyway for ****s and grins, and it failed of course. After rebooting post failure, mine also stated it was up to date.
I did it the hard way, flashed system and radio using fastboot. All up to date now. :good:
Bone stock no root or anything. Would hard reset work? Or will it reprompt soon?
It's hard to say exactly, but given the image was just posted by Google today, and OTAs are already pushing out, you may see it again tomorrow.
I cleared the framework. Still nothing.
Connect to a charger, it reappear and I was able to update. BTW make sure you on WiFi
So wifi connect to charger and clear framework. Will try. Anyone else have solutions?
Yet to repop update. Still getting the up to date...
StrangeTimes said:
Verizon 6 here...got prompted to update. Downloaded and was ready for the install and reboot. Phone rebooted. Still 5.0? And device up to date. How can i redownload? Please help
Click to expand...
Click to collapse
Same thing is happening on my Nexus 7 2013. I've tried it 5 different times.
Sent from my SM-N900V
Same here... fully stock and unrooted Nexus 6 with VZW sim. Got an update notification. Tried to update and the notification just went away and now says I'm up-to-date even thought the update never installed... still on 5.0.
Any solutionsnyet? Hard reset phone does nothing btw
Man... Was really hoping to wake up to the update popping up again. No dice.
att nexus 6 failed 5.0.1
Got notification on att nexus 6 completely stock, for the update to 5.0.1, after accepting the install and agreeing for the restart, it never restarted or updated anything. Still on 5.0. Checking for updates shows that i'm "up to date" and attempting to side load the update via ADB fails.
Got the ota update just now. Install was successful.
Hey all,
Thought I'd let those of you that have an AT&T Tab S 8.4 know that Lollipop has been released today. Happened to be on the AT&T Software update page here: http://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB425812&cv=820 and noticed it listed the update.
Manually checked for updates on my tablet, it's downloading now. My 8.4 on AT&T is totally stock.
Downloading now... 1.1GB
manually checking shows nothing for me
Mine wasn't too laggy after the upgrade. But as I know from places like XDA usually a very good idea to do a full system wipe which I did.
What I am most thankful for is there is now an option to remove that Samsung screen that has those Samsung widgets that go full page. Can't recall what it is called. Yeah I know could have got rid of that using a 3rd party launcher in 4.4 but so happy Samsung put option there to disable it finally. To get rid of it, long press blank space like you were going to add a widget, then click Home Screen Settings, then uncheck "Content Home Screen".
Has anyone who rooted with kingroot updated? I'm assuming it'll kill root, just curious if I need to unroot prior, or if the update will still install. I'll post the answer tomorrow after I update.
I've had some Samsung devices which will update while rooted, and some that will not.
Russ77 said:
Has anyone who rooted with kingroot updated? I'm assuming it'll kill root, just curious if I need to unroot prior, or if the update will still install. I'll post the answer tomorrow after I update.
I've had some Samsung devices which will update while rooted, and some that will not.
Click to expand...
Click to collapse
Not sure it will work.
Maybe try to adapt the method given by ashyx here: http://forum.xda-developers.com/galaxy-tab-s/general/guide-how-to-root-tripping-knox-kitkat-t3129484
It worked successfully for me on the T800
Russ77 said:
Has anyone who rooted with kingroot updated? I'm assuming it'll kill root, just curious if I need to unroot prior, or if the update will still install. I'll post the answer tomorrow after I update.
I've had some Samsung devices which will update while rooted, and some that will not.
Click to expand...
Click to collapse
I'm rooted with Kingroot and it's currently downloading the update. If you load Xposed Framework and Wanam Xposed, under Security hacks there's a setting for Fake System Status that allows you to set it to Original.
I'll follow up when the download finishes.
Update: The download completed but the install failed and then got stuck in a boot loop. Ended up having to go to the Samsung place at Best Buy to have them re-flash KitKat. Now the tab is telling me I have to wait 24 hours to check for updates. I'm sure everything will be good now that I'm back on a factory image.
fleabeard said:
I'm rooted with Kingroot and it's currently downloading the update. If you load Xposed Framework and Wanam Xposed, under Security hacks there's a setting for Fake System Status that allows you to set it to Original.
I'll follow up when the download finishes.
Update: The download completed but the install failed and then got stuck in a boot loop. Ended up having to go to the Samsung place at Best Buy to have them re-flash KitKat. Now the tab is telling me I have to wait 24 hours to check for updates. I'm sure everything will be good now that I'm back on a factory image.
Click to expand...
Click to collapse
Turn off automatic date and time and manually advance it by a day, and try again.
When they re-flashed KitKat did it wipe your tablet? The OTA failed me when rooted, failed me after un-installing adaway and un-rooting and removing KingUser. I cannot do a firmware upgrade via Kies 3 as it's not available. I cannot do an emergency firmware recover via Kies 3 as it's not soft bricked. I can't find either the KitKat or the Lollipop firmwares online anywhere... Currently I have a tablet, works fine, I did a factory reset (in the back of my mind knew this wouldn't work) that has a custom status and won't take the OTA.
If anyone knows where I can find the KitKat firmware, or the OTA, please let me know.
Or maybe someone could grab the OTA off their tablet after downloading prior to updating and share the wealth with the community???
Has any kingroot user tried triangle away, unroot via kinguser, and take the OTA?
Also just realized that if I can fail the OTA, I can obviously download it... Where do I grab it from if I wanted to flash it with odin or sideload?
Russ77 said:
Has anyone who rooted with kingroot updated? I'm assuming it'll kill root, just curious if I need to unroot prior, or if the update will still install. I'll post the answer tomorrow after I update.
I've had some Samsung devices which will update while rooted, and some that will not.
Click to expand...
Click to collapse
Russ77 said:
Turn off automatic date and time and manually advance it by a day, and try again.
When they re-flashed KitKat did it wipe your tablet? The OTA failed me when rooted, failed me after un-installing adaway and un-rooting and removing KingUser. I cannot do a firmware upgrade via Kies 3 as it's not available. I cannot do an emergency firmware recover via Kies 3 as it's not soft bricked. I can't find either the KitKat or the Lollipop firmwares online anywhere... Currently I have a tablet, works fine, I did a factory reset (in the back of my mind knew this wouldn't work) that has a custom status and won't take the OTA.
If anyone knows where I can find the KitKat firmware, or the OTA, please let me know.
Or maybe someone could grab the OTA off their tablet after downloading prior to updating and share the wealth with the community???
Click to expand...
Click to collapse
OTA came down successfully while not rooted. The reflash at Best Buy didn't wipe it.
As far as I know, the factory images for the AT&T versions aren't available anywhere, or at least I've been unable to find them. They obviously exist because I'm pretty sure the guy at Best Buy used Kies to flash with an image that's available to him from Samsung.
I re-rooted last night in the attempt of using triangle away to clear customs status, then un-rooting. This was odd because device status still shows custom but download mode shows official and Knox is 0.
While I was briefly rooted again I downloaded the OTA in the hopes of copying it to my PC and updating via ADB Sideload... Couldn't find it. If anyone knows where Samsung puts these I'll grab it and post it to share.
im not rooted, performed a factory reset, and my device still doesn't see any updates. Can somebody provide a link to the ROM?
Same situation here - no root, no mods, no available update
Sent from my SM-G925V using XDA Premium HD app
Same Thing Here Also
bshaw100 said:
Same situation here - no root, no mods, no available update
Sent from my SM-G925V using XDA Premium HD app
Click to expand...
Click to collapse
I've got the same thing: no root, no mods, no update available! Darn!!!!
I've got the same thing: no root, no mods, no update available!
Russ77 said:
I re-rooted last night in the attempt of using triangle away to clear customs status, then un-rooting. This was odd because device status still shows custom but download mode shows official and Knox is 0.
While I was briefly rooted again I downloaded the OTA in the hopes of copying it to my PC and updating via ADB Sideload... Couldn't find it. If anyone knows where Samsung puts these I'll grab it and post it to share.
Click to expand...
Click to collapse
The OTA gets downloaded to /cache. If you are rooted you can see it. But the OTA is not a complete ROM, just a differential to the ROM you have.
Sent from my SM-T707V using XDA Premium HD app
still nothing
gshaw_nash said:
I've got the same thing: no root, no mods, no update available! Darn!!!!
Click to expand...
Click to collapse
gshaw1967 said:
I've got the same thing: no root, no mods, no update available!
Click to expand...
Click to collapse
I've reset several time and cannot download the update. I get "Connecting to DM Server" and then update interrupted. Has anyone gotten around this?
---------- Post added at 08:58 AM ---------- Previous post was at 08:11 AM ----------
gshaw1967 said:
I've reset several time and cannot download the update. I get "Connecting to DM Server" and then update interrupted. Has anyone gotten around this?
Click to expand...
Click to collapse
Turns out there is a imei problem with the tablet that is preventing the download. My imei number is paired with a IPhone 4. Anyway will take a few day to fix then the upgrade should work.
I get the same. I wiped my device hoping for a different outcome, and still no update.
I found this in the thread below.
It is an old tread but I'll comment anyway. SM-T807 is the 3G version while SM-T805 is the LTE version. Both Hardware (CPU/GPU) and comms modules are different. So 805 LTE (which has Lollipop) firmware won't work for 807 (no Lollipop is currently available nor Samsung plans to release soon).
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-tab-s/help/sm-t805-sm-t807a-t2961117
John.
After not being able to take the OTA after rooting, even after un rooting, not being able to find the OTA and sideload (not in /cache), and not able use Kies or Odin I finally took it to the Samsung kiosk at my bestbuy.
They reflashed 4.4.2, didn't wipe anything, and immediately downloaded and successfully installed the lollipop update after getting home and on WiFi.
Just don't mention that you rooted ;')
Not sure what this is yet. Non rooted, stock image.
5.1.1?? Will report back...
Not 5.1.1
No idea as they haven't posted changelog, but hopefully a fix for MicroCell issues everyone is experiencing.
Let us know if you see any changes.
Update downloaded.
Real upgrade from OE2 to OF3. Thats all it says.
@Globalrebel where are you looking for change logs?
Update just finished. Yeah Android version is still 5.0.2. Baseband G925AUCU2AOF3 now.
Getting it now.
http://www.att.com/esupport/softwar...are&siteId=JAF5WzpxbKM-uxPru.0S4qk9EABb6wNW3Q
Change Log
Ssj237 said:
http://www.att.com/esupport/softwar...support/sharedSegments/supportViewService.jsp
Change Log
Click to expand...
Click to collapse
Session timed out. Please use the back button, reload and try again.
That build date of june 18th piss anyone else off lol
veener79 said:
Session timed out. Please use the back button, reload and try again.
Click to expand...
Click to collapse
Should be fix now
msfguard said:
That build date of june 18th piss anyone else off lol
Click to expand...
Click to collapse
You mean since 5.1.1 was supposed to hit the S6's "in June?"
This is getting ridiculous, we need an update from 5.0.2, the memory issues I'm dealing with even on XtreStoLite are almost unbearable
Exactly and as updates for 5.1 come out for other carriers we get updates for random att crap that are almost a month old
It's sad to say that the latest AT&T OTA patches the export for ping pong root, don't take the OTA, because you cannot downgrade the Odin fails
dnp77 said:
It's sad to say that the latest AT&T OTA patches the export for ping pong root, don't take the OTA, because you cannot downgrade the Odin fails
Click to expand...
Click to collapse
how you know? you ota it ?
i was "downloading" then saw your post. so i reboot my phone to cancel it.
netnerd said:
how you know? you ota it ?
i was "downloading" then saw your post. so i reboot my phone to cancel it.
Click to expand...
Click to collapse
They know because it says on the Ping Pong Root thread not to update for anything past May 15th as the method for root has been patched
I'm curious if there are any other undocumented changes besides the 2 official changes listed earlier. It feels like a fairly big patch for a fix to an phone location and a kernel security fix.
Is there any hope, luck or signs of achieving root on this new firmware
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Wow, what a crappy push out by AT&T.
In any case, what process do i need to freeze in TB to stop my phone from trying to download and/or annoying me with that pop-up when it does happen?
aidanipod said:
Is there any hope, luck or signs of achieving root on this new firmware
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Click to expand...
Click to collapse
Please see just ONE post above yours........ we have just been talking about the exploit being patched
Globalrebel said:
Wow, what a crappy push out by AT&T.
In any case, what process do i need to freeze in TB to stop my phone from trying to download and/or annoying me with that pop-up when it does happen?
Click to expand...
Click to collapse
AT&T Software Update is the main one, but there are a few others - I don't have an AT&T ROM on mine right now to help out, but it's been posted a few times already (I think I even posted those once)
Just freeze att software update. Then it can't even run so no downloads. I got lucky I clicked on update after reading it in Android central but didn't want to install it. Postponed couple of times but somehow it automatically loaded the update process. I was like sh#t. When it booted up it said a problem updating. And then I blocked the updater. My root almost gone lol
Sent from my SAMSUNG-SM-T337A using Tapatalk
saketkutta said:
Just freeze att software update. Then it can't even run so no downloads. I got lucky I clicked on update after reading it in Android central but didn't want to install it. Postponed couple of times but somehow it automatically loaded the update process. I was like sh#t. When it booted up it said a problem updating. And then I blocked the updater. My root almost gone lol
Sent from my SAMSUNG-SM-T337A using Tapatalk
Click to expand...
Click to collapse
Same thing happened to me being rooted. It just tried to install automatically. Woke up to my phone restarting but then I got the error "problem updating". I was pretty relieved on that error lol... :victory:
Hi,
I'm French and I 'very got a stock nexus 6.
I have the 5.1.1 android (LMY48T) and as I noticed a notification about 6.0 I started the update.
After few minutes, the update was DLed and a rebootr was announced... But nothing.
I waited for a bit.
And tried to shut-off the phone for a manual reboot... Now I'm still in 5.1.1, and when I check the update it's says that my phone is up-to-date..
Any help?
Thanks for reading.
Greg
Happened to me too on my Nexus 6
Thanks for the contribution, did you find any piece of information anywhere else?
no not at all :/
Bummer...
hello gregaste
i can confirm the exact same problem downloaded the ota and pressed restart and install and nothing happened it its telling me ur device is up to date ! i hope somone can help us
Are you rooted? Not sure what "very stock" means. OTAs will fail if you are.
Had the same thing happen to me. Twice. Got a replacement N6 last week and I was letting all the OTAs go through before unlocking the bootloader and rooting. When I got the 6.0 update notification I let it download. After rebooting it didn't update and when I checked system update it saif I was up to date despite still being on 5.1.1. Then, for fun, after returning my original Nexus to stock I decided to let the 6.0 update download. After rebooting I was still on 5.1.1 and again it said I was up to date. Very weird. I got impatient and flashed the factory images.
I'm stock, and i'm not sure about my first message, but I'm positive that "very stock" is an auto-correct fail...
I phone to Google android help yesterday, and a guy told me something like "s-h1t happens" more polite though, and that I should wait for another notification... let's hope.
Happened to me as well. Once the ota is downloaded, give time to the phone to restart itself in recovery, it takes about 10 mintutes to go into recovery and dont interfere with soft reset.
Sent from my Nexus 6 using XDA Free mobile app
Semseddin said:
Happened to me as well. Once the ota is downloaded, give time to the phone to restart itself in recovery, it takes about 10 mintutes to go into recovery and dont interfere with soft reset.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
i restarted the phone my self and nothing happened but later i also cleared the cashe still it tells me ur system is up to date
phlimsh said:
i restarted the phone my self and nothing happened but later i also cleared the cashe still it tells me ur system is up to date
Click to expand...
Click to collapse
turn on your wifi, connect to wifi, then check if you are up to date.
gregaste said:
I'm stock, and i'm not sure about my first message, but I'm positive that "very stock" is an auto-correct fail...
I phone to Google android help yesterday, and a guy told me something like "s-h1t happens" more polite though, and that I should wait for another notification... let's hope.
Click to expand...
Click to collapse
let us hope it will show again soon !
Thank you for the tip. Maybe I didn't wait because no message told me to... Lesson learned.
So you had a second ota notification? How long after the first one who failed?
simms22 said:
turn on your wifi, connect to wifi, then check if you are up to date.
Click to expand...
Click to collapse
i ve done that like 100 times and nothing still says " your system is up to date " i guess i will wait for about a month maybe another ota will show up if not then i will flash although iam afraid something goes wrong and i will regret messing up my phone cause i have not done that before
phlimsh said:
i restarted the phone my self and nothing happened but later i also cleared the cashe still it tells me ur system is up to date
Click to expand...
Click to collapse
Go to Settings / About / Send feedback ; tell them you haven't recieved MArshallow OTA, that's how i got my 6.0 ota for the second time without waiting hours.
Semseddin said:
Go to Settings / About / Send feedback ; tell them you haven't recieved MArshallow OTA, that's how i got my 6.0 ota for the second time without waiting hours.
Click to expand...
Click to collapse
I followed your steps, but it feels like a coincidence to me... we'll see.
gregaste said:
Hi,
I'm French and I 'very got a stock nexus 6.
I have the 5.1.1 android (LMY48T) and as I noticed a notification about 6.0 I started the update.
After few minutes, the update was DLed and a rebootr was announced... But nothing.
I waited for a bit.
And tried to shut-off the phone for a manual reboot... Now I'm still in 5.1.1, and when I check the update it's says that my phone is up-to-date..
Any help?
Thanks for reading.
Greg
Click to expand...
Click to collapse
That may have been the October security download. After getting Marshmallow on my N5 and N9 weeks before, I got that update notice, downloaded it, rebooted and noticed the old Lollypop boot animation. I thought the update didn't get applied and never got another notification. I later ran Stagefright Detector and noticed that the two latest CVEs were remediated. So I'm still waiting for Android 6 for my Nexus 6.
stevemw said:
That may have been the October security download. After getting Marshmallow on my N5 and N9 weeks before, I got that update notice, downloaded it, rebooted and noticed the old Lollypop boot animation. I thought the update didn't get applied and never got another notification. I later ran Stagefright Detector and noticed that the two latest CVEs were remediated. So I'm still waiting for Android 6 for my Nexus 6.
Click to expand...
Click to collapse
Thank you for your input.
I'm not sure it's related to the secrity update though, because I was already up to date on this matter (LMY48T) , ain't I ?
gregaste said:
Thank you for your input.
I'm not sure it's related to the secrity update though, because I was already up to date on this matter (LMY48T) , ain't I ?
Click to expand...
Click to collapse
I went from LYZ28J to LYZ28K with that update. I believe T-Mobile and Sprint are on different forks of Lollypop.
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