Related
Is there a way to stop my Droid from updating OTA to FroYo? I have flashed my Droid over to Cricket and have Bugless Beast v0.4 installed, and now since the 2.2 OTA update has been released I get a constant notification that the update is available. The only options I get are to install now or to install later, but what if I don't want to install it all and just get rid of the pesky notification that keeps popping up every so often after I press install later. I already have 2.2 on my system with Bugless Beast so I'm not really missing out on anything. I don't want to update and have to reroot, reinstall Bugless Beast, and reflash my Droid to Cricket again. I'm happy where my system is at
If you have a custom recovery, then as soon as you reboot into the installation your phone thinks that you've accepted, but the custom recovery blocks the installation and you stay on BB.
What do you mean by reboot into installation?
I've booted into clockwork recovery and then restarted the phone, but nothing seemed to change. Is that what you meant to do?
Flash SPRecovery. Then select "install now". It will send a notification that it has been installed on your phone to the servers that send out the OTA but SPRecovery will block the installation of it onto your phone, thus stopping the notifications of an update and keeping you on BB v.04 w/ Cricket. You can flash back to CW Recovery if you want to afterwards.
Sent from my Droid using XDA App
Im also running BB.04 and got the OTA notification today. Glad I found this thread because I was starting to get worried. I clicked 'install now', rebooted and so far no notification and I am still on BB.04. Woot!
Thank you for this!
Running BB 0.4. I saw the verizon 2.2 Froyo upgrade this morning, and for a second I was psyched verizon finally pushed it out... then I was a little worried about what was going to happen to mine since it was rooted and running a 2.2 Rom I was already happy with. Just like this thread says, I clicked install, and the phone rebooted right back up to my BB 0.4 without any issues.
I'd hate to say I'm a leech, but you guys have so much information here, and I cannot stop reading lol. I commend everyone one of you Devs for all the work you do!
Thank you again,
-Dano
Yup, it worked perfectly! Thank you!
Interesting. I was able to block it the first time but it popped up again. Anyone know why? Maybe there is another update to the 2.2 OTA update?
I was having the same issue with the ota update until I came across this:
http://www.peteralfonso.com/2010/08/how-to-stop-ota-notifications-on.html#more
it says it is for Buggles rom but I am using a different rom and it worked just fine
I had received this notification about four times before it recognized that I'm updated without rebooting the phone for it to be blocked. Nothing else had to be done except for saying yes.
stephen730 said:
whatchoo mean able to block it? You mean you clicked install later? Or you let it run and it goes away?
If you let it run/fail it will just come back again a day later, a week later, next time you reboot, next time you come out of screen off, etc... Its done it to me and it sucks cause it won't go away number 1, and number 2, i hate to keep rebooting to fail and possibly missing calls/texts... especially when you first wake up and the message is there like a nagscreen or advert.
Click to expand...
Click to collapse
I clicked install now and my recovery image blocks the installation when rebooted. It shows the Android guy with the exclamtion point but it doesnt finish the install. Reboot then im back to the way I was. Im running BBv.4 btw. I havent got another prompt yet.
So I just got a notification from ATT saying that there is a software update available. Has anyone else gotten this and installed it? Is it jelly bean or a minor update? I haven't tried it myself because I am rooted.
Sent from my HTC PH39100 using xda app-developers app
Bigluc said:
So I just got a notification from ATT saying that there is a software update available. Has anyone else gotten this and installed it? Is it jelly bean or a minor update? I haven't tried it myself because I am rooted.
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Yes just got it I'm Rooted & S-OFF
it won't be jelly bean since the ONE X series doesn't have it yet haha just a minor I bet
Can someone detail this update?
*Edit* Called AT&T the Update was released October 9th it an 13mb update so yea Minor the girl
on the phone was talking to fast for me to listen what it offers
Got it last night. Android version did not change. Couldn't tell for sure if any other numbers updated. It wouldn't kill AT&T to send out an e-mail or text message telling us what the update was for.
got the same thing i have no idea what is the update
Update has my phone stuck in a darn boot loop..any idea what it is?
Sorry bludiamond.
Since my phone is rooted, I did not want to install this update. It's quite upsetting that AT&T forces the update unconditionally.
Anyway, I had let the download to complete, but did not let it to install. The update did prompt me, whether I want it to install now, or later. I had opted for later.
Then, after some Googling, I had deleted the download (from /sdcard/Download), and had un-installed the following services: com.htc.demoflopackageinstaller and com.smithmicro.dm.
Then, I've rebooted the phone. Afterwards, the phone still had a notification, that there's an update ready to be installed. When, selecting the notification, updater did realize that the downloaded file is gone, and had prompted me whether or not I'd like to download the update again, on which, I had responded no. The notification is gone, and AT&T did not prompt me to download and install the update again, at least not yet.
My phone seems to be OK.
I was hoping for a new Radio/RIL. That's not what this is...
New Kernel & Recovery. If you are rooted and on a custom rom Do Not run the update. I'm sure the developer of the rom you are on will work to add anything useful to future updates.
The dates on these files is 7/27/12 so it took At$t over to months to test & release.
To delete it look in /cache/fota/OTAPkg.zip
Once gone you shouldn't be bothered by it anymore.
Have anyone successfuly downloaded and installed it?
What's new? Bluetooth bugs fixes? Usable Voice Dialer? Better battery life?
Sense 4.0?
Please comment.
Sent from my HTC PH39100 using xda app-developers app
gattech said:
Have anyone successfuly downloaded and installed it?
What's new? Bluetooth bugs fixes? Usable Voice Dialer? Better battery life?
Sense 4.0?
Please comment.
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Think the majority of users on here are rooted and running custom roms so they wouldnt' be installing this.
I forgot I was unlocked and rooted. Now I am really stuck. How do I get out of the dead Android loop?
I googled the update, and found this on the ATT Support website.
Beginning on October 9, 2012, AT&T and HTC have released an additional software update for the HTC Vivid that will be available via firmware over-the-air (FOTA). This 13MB software package updates the firmware version to 3.26.502.56_R23 and improves sensor performance.
NOTE: Customers must have a data SOC in order to obtain any FOTA updates. Customers who have a data opt-out SOC are not able to receive FOTA updates.
strose09 said:
Think the majority of users on here are rooted and running custom roms so they wouldnt' be installing this.
Click to expand...
Click to collapse
Hmmm....
Sent from my HTC PH39100 using Tapatalk 2
For the users in boot loop I just recovered from it. Boot into cwm and clear the cache a couple of times and reboot.
Sent from my HTC PH39100 using xda app-developers app
kos26 said:
For the users in boot loop I just recovered from it. Boot into cwm and clear the cache a couple of times and reboot.
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
This Fix works. My phone no longer boot loops
3f62011 said:
Sorry bludiamond.
Since my phone is rooted, I did not want to install this update. It's quite upsetting that AT&T forces the update unconditionally.
Anyway, I had let the download to complete, but did not let it to install. The update did prompt me, whether I want it to install now, or later. I had opted for later.
Then, after some Googling, I had deleted the download (from /sdcard/Download), and had un-installed the following services: com.htc.demoflopackageinstaller and com.smithmicro.dm.
Then, I've rebooted the phone. Afterwards, the phone still had a notification, that there's an update ready to be installed. When, selecting the notification, updater did realize that the downloaded file is gone, and had prompted me whether or not I'd like to download the update again, on which, I had responded no. The notification is gone, and AT&T did not prompt me to download and install the update again, at least not yet.
My phone seems to be OK.
Click to expand...
Click to collapse
After getting my phone out of the boot loop I tried this and am no longer prompted to update. Thank you for the help
Apatche69 said:
This Fix works. My phone no longer boot loops
After getting my phone out of the boot loop I tried this and am no longer prompted to update. Thank you for the help
Click to expand...
Click to collapse
I had the looping issue too. I cleared the cache once and rebooted. Received a message that there was a problem with the update and to wait for the next update. Phone seems to be okay since.
I'm unlocked s/on..no custom rom..it was so early, I must have hit the wrong button, so I'm stuck in the loop and can't seem to get into recovery either..ugh
I'm stock - not rooted. I did do the download without any problems, although you do have to manually reboot after the update.
It supposedly improves the sensor. Not sure what that means, but that's what the ATT website says. Other than it changing my default ringtone, I don't see any difference.
Could not get it out of the loop. Took it to the service center and neither could they..they ended up replacing it under warranty..thank goodness. Said that another lady came in with the same issue as well.
AT&T Upgrade to Nowhere
I'm running stock on the HTC Vivid and got this upgrade pushed out by AT&T. This is the second AT&T upgrade I've done on this phone (the first was to ICS not long after I got the phone).
I ran the update yesterday, which force rebooted my phone and I watched as the upgrade downloaded and installed, then came back up.
NOTHING has changed. I don't know what AT&T supposedly upgraded, but it's certainly nothing noticeable.
I didn't even get the "3.26.502.56_R23" software designation that the AT&T help article says I was supposed to see.
It was literally an upgrade to nowhere. Not sure why I wasted time off the grid and battery power on it.
As usual-- AT&T fail.
At least no harm was done.
I was rooted, stock ROM, and got the notification yesterday. I postponed as much as I could but it finally wouldn't let me anymore and I let it try to update.
Of course, went into a boot loop. I did eventually get the boot looping to stop by reflashing the wxc recovery image and CWM-root, but then my wifi wouldn't work. I suspected some difference in the kernel version or some other borking of the update.
Long story short, I had to re-lock, go back to stock, and re-unlock and root again. Then spend the time (ongoing) to get my environment back. Thank goodness for Titanium backup pro and Dropbox. LOL.
Wish I could bill AT&T for the 18 hours I've spent. And if they push it to me again, I'll be irritated.
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