I've had a Pixel 4 XL since launch and just did a fresh install of the December update. Now my face unlock no longer works. I get "Can't verify face. Try again" every time. I've tried deleting face data and setting it up again and numerous reboots. Any ideas?
I'm no expert on the matter but I had to do a factory reset to get it to work again. Maybe flashing the boot.img from the December update might do it
pwnsicle said:
I'm no expert on the matter but I had to do a factory reset to get it to work again. Maybe flashing the boot.img from the December update might do it
Click to expand...
Click to collapse
Really hope I don't have to do a factory reset. It takes forever to completely set everything up again.
Delete. My old tired eyes missed a part of your post. Carry on lol.
czonin said:
I've had a Pixel 4 XL since launch and just did a fresh install of the December update. Now my face unlock no longer works. I get "Can't verify face. Try again" every time. I've tried deleting face data and setting it up again and numerous reboots. Any ideas?
Click to expand...
Click to collapse
You might have the wrong update version installed. This happened to me with the Nov releases. Try flashing a different version. I'm willing to bet it fixes it.
Are you running a custom kernel or stock?
brandon5491 said:
You might have the wrong update version installed. This happened to me with the Nov releases. Try flashing a different version. I'm willing to bet it fixes it.
Click to expand...
Click to collapse
I'm pretty sure you're right. Trying a different version now.
Edit: I was on the wrong version but i've flashed the correct one and re-setup face unlock and it still isn't working.
Alcolawl said:
Are you running a custom kernel or stock?
Click to expand...
Click to collapse
Stock, rooted.
czonin said:
Stock, rooted.
Click to expand...
Click to collapse
Unfortunately I've seen this happen to one other person. A factory reset was the only way he was able to fix it.
Alcolawl said:
Unfortunately I've seen this happen to one other person. A factory reset was the only way he was able to fix it.
Click to expand...
Click to collapse
yep had this issue earlier and only factory reset helped.
Alcolawl said:
Unfortunately I've seen this happen to one other person. A factory reset was the only way he was able to fix it.
Click to expand...
Click to collapse
ceelos218 said:
yep had this issue earlier and only factory reset helped.
Click to expand...
Click to collapse
Ya I couldn't find any way to fix it. Ended up having to factory reset and it's all working now.
czonin said:
Ya I couldn't find any way to fix it. Ended up having to factory reset and it's all working now.
Click to expand...
Click to collapse
I'm having the same issue but I think I'd rather live without Face Unlock than have to do a factory reset, re-root, etc. Back to the pattern for me!
---------- Post added at 10:35 AM ---------- Previous post was at 10:26 AM ----------
tonyfiore75 said:
I'm having the same issue but I think I'd rather live without Face Unlock than have to do a factory reset, re-root, etc. Back to the pattern for me!
Click to expand...
Click to collapse
Never mind. It was Elemental X kernel that broke Face Unlock. I flashed another kernel and Face Unlock is working again. :good:
tonyfiore75 said:
Never mind. It was Elemental X kernel that broke Face Unlock. I flashed another kernel and Face Unlock is working again. :good:
Click to expand...
Click to collapse
Same here. Went to factory kernel and all is well.
I had to factory reset to fix this. No flashing stock dtbo, stock boot image, or even reflashing stock factory images worked. Even with the -w I had no face unlock. I had to factory reset again after flashing factory images with the -w flag to fix it. It works now though.
czonin said:
I've had a Pixel 4 XL since launch and just did a fresh install of the December update. Now my face unlock no longer works. I get "Can't verify face. Try again" every time. I've tried deleting face data and setting it up again and numerous reboots. Any ideas?
Click to expand...
Click to collapse
Same thing here. Unlock was working well right up until I flashed the Dec. update. I'm on 191205.012.A1 build for AT&T (my carrier). Stock, rooted, ex kernel. I'm going to try the stock boot image route when I get home tonight. What a PITA.
tonyfiore75 said:
Never mind. It was Elemental X kernel that broke Face Unlock. I flashed another kernel and Face Unlock is working again. :good:
Click to expand...
Click to collapse
Which kernel did you switch to? There isn't an EX Kernel thread for the P4 XL (yet) to corroborate and report this. Mentioning @flar2 in hopes he sees this and can look into it.
EDIT: Flashing Kirisakura kernel 2.1.0 restored face recognition using my existing face profile.
v12xke said:
Which kernel did you switch to? There isn't an EX Kernel thread for the P4 XL (yet) to corroborate and report this. Mentioning @flar2 in hopes he sees this and can look into it.
EDIT: Flashing Kirisakura kernel 2.1.0 restored face recognition using my existing face profile.
Click to expand...
Click to collapse
Yup - that's exactly what I did as well. Worked like a charm. I'm waiting to see if another EX Kernel version comes out soon (keeping track on the EX app itself).
tonyfiore75 said:
I'm having the same issue but I think I'd rather live without Face Unlock than have to do a factory reset, re-root, etc. Back to the pattern for me!
---------- Post added at 10:35 AM ---------- Previous post was at 10:26 AM ----------
Never mind. It was Elemental X kernel that broke Face Unlock. I flashed another kernel and Face Unlock is working again. :good:
Click to expand...
Click to collapse
Thanks a lot, tonyfiore75!
Somehow I wanted to do a backup of the stock kernel before flashing Elementalx after flashing Dec 2019 update. Restored and face unlock works again!
wrongway213 said:
I had to factory reset to fix this. No flashing stock dtbo, stock boot image, or even reflashing stock factory images worked. Even with the -w I had no face unlock. I had to factory reset again after flashing factory images with the -w flag to fix it. It works now though.
Click to expand...
Click to collapse
Same thing for me
Flashed Dec update with factory images and it broke face unlock. Had to factory reset through the app settings to get it working again.
I hear that the updated FrankenKernel works. RQ10. https://forum.xda-developers.com/showpost.php?p=81165507&postcount=109
Edit: Look for 10.1 later in the thread. There is a minor update.
Edit: Just read the thread, there is also a 10.3 update!
Related
Sorry for this annoying thread, but I'm sure everyone wants to know
https://developers.google.com/android/nexus/images#hammerheadlrx22c
ragnarokx said:
Sorry for this annoying thread, but I'm sure everyone wants to know
https://developers.google.com/android/nexus/images#hammerheadlrx22c
Click to expand...
Click to collapse
Haha - I've been hitting F5 every 10 minutes or so for the past few hours
Direct link to save a few clicks for some - https://dl.google.com/dl/android/aosp/hammerhead-lrx22c-factory-0f9eda1b.tgz
Does not work for me.
edit: sorry, it works now.
---------- Post added at 07:32 PM ---------- Previous post was at 07:20 PM ----------
New radio: m8974a-2.0.50.2.22
You guys know about Pushbullet, right?
Seriously, who spams F5 all day anymore?
About damn time. We must be the very last device to get it. Even the N4 got 5.01 like a week ago
is there anyway change log by google?
Lol, but in https://developers.google.com/android/nexus/images#hammerheadlrx22c doesnt appear... how did you do? jajajaja thx
tdimarzio thx for https://dl.google.com/dl/android/aosp/hammerhead-lrx22c-factory-0f9eda1b.tgz
While flashing I'm getting the error that the zip file is missing system.img, I checked the file and it was there, redownloading now and will update.
**Update** Redownloaded, MD5 Checksum matches source, still having the same issue.
Just finished flash
Not that I was expecting anything different but no obvious changes.
BirchBarlow said:
About damn time. We must be the very last device to get it. Even the N4 got 5.01 like a week ago
Click to expand...
Click to collapse
If it fixes all the bugs related to this phone I wouldn't have minded if it was released in January
mrmidnight said:
While flashing I'm getting the error that the zip file is missing system.img, I checked the file and it was there, redownloading now and will update.
**Update** Redownloaded, MD5 Checksum matches source, still having the same issue.
Click to expand...
Click to collapse
Extract and flash manually.
Aerowinder said:
Extract and flash manually.
Click to expand...
Click to collapse
Will do
In 5.0.1 maybe the battery will be better?
I was waiting for 5.0.1 with my 4.4.4... but i don't know if I switch now.
And here is the ota zip file!! ??
http://android.clients.google.com/p...ed-hammerhead-LRX22C-from-LRX21O.785a2f7a.zip
I am going to do a complete wipe and reinstallation to ensure the best chance of working.
We are good to go now. Manually flashed and it worked. Appears the issue is with Windows Technical Preview. Thanks!
You can flash/root with the Wug toolkit too.
I can connect to corporate wifi now. At least one bug is fixed for me.
Duilio Patiño said:
And here is the ota zip file!! ??
http://android.clients.google.com/p...ed-hammerhead-LRX22C-from-LRX21O.785a2f7a.zip
Click to expand...
Click to collapse
I haven't done this in a while, do we need custom recovery to flash or can we flash this with stock recovery. I am completely stock with just an unlocked Bootloader.
Raistlin1 said:
I haven't done this in a while, do we need custom recovery to flash or can we flash this with stock recovery. I am completely stock with just an unlocked Bootloader.
Click to expand...
Click to collapse
If you are using the factory image, you can do it with the stock. Haven't done it using ota image so not sure about it.
Hi all,
I flashed the factory image from developer.google.com version 5.1 for my Nexus 6. After installing all my phone keeps rebooting and optimizing apps. It keeps doing this and i cant seem to find a way to get in my phone.
I relocked bootloader and cannot unlock it now because it says i need to check OEM unlock in developer options.
Any idea how i can fix this? it looks like im stuck and cannot find a way to unlock anymore to flash something else.
also, i went back into recovery and formatted data and cache. no effects after this.
help
haruryu said:
Hi all,
I flashed the factory image from developer.google.com version 5.1 for my Nexus 6. After installing all my phone keeps rebooting and optimizing apps. It keeps doing this and i cant seem to find a way to get in my phone.
I relocked bootloader and cannot unlock it now because it says i need to check OEM unlock in developer options.
Any idea how i can fix this? it looks like im stuck and cannot find a way to unlock anymore to flash something else.
also, i went back into recovery and formatted data and cache. no effects after this.
help
Click to expand...
Click to collapse
Did you use WUG's toolkit?
I had this, just had to reflash the image again but I didn't relock it first, so cant help with that.
Amos91 said:
Did you use WUG's toolkit?
I had this, just had to reflash the image again but I didn't relock it first, so cant help with that.
Click to expand...
Click to collapse
no this doesnt work
because i have no more unlocked bootloader.
@haruyu I'm in a similar situation ... Sadly I see no fix
Only thing I can think of is flashing something in stock recovery (if at all possible) ... But I don't if there is a stock recovery compatible files to flash
haruryu said:
no this doesnt work
because i have no more unlocked bootloader.
Click to expand...
Click to collapse
As yet, there is nothing we have found to fix this issue. I can't think if a fix anyway. maybe someone more familiar than me will find one but for now no-one has.
im guessing my phone is bricked.
haruryu said:
im guessing my phone is bricked.
Click to expand...
Click to collapse
Yes (and hopefully no) .... we can access fastboot, but that doesn't help because (as you know) we can flash stock images with a locked bootloader. I am hoping some of our brilliant devs can come up with a solution (they like a good challenge LOL) being we can get to fastboot, but if not, yes, we are essentially bricked
There's an option in advance that force flashes the stock image...trying going back to 5.01 then 5.1. I tried doing the flash files like some did and got stuck in a infinite bootloop so I went into the advanced thing and done it there.
HI all,
I also faced same issues Nexus 6 keep rebooting after updating to 5.1.
Locked Bootloader
any positive help would be highly appreciated
deeplyyoung said:
HI all,
I also faced same issues Nexus 6 keep rebooting after updating to 5.1.
Locked Bootloader
any positive help would be highly appreciated
Click to expand...
Click to collapse
You could try sideloading the Marshmallow update to see if that helps, sideload it and then factory reset. See if it boots fine then.
nms247 said:
You could try sideloading the Marshmallow update to see if that helps, sideload it and then factory reset. See if it boots fine then.
Click to expand...
Click to collapse
will check & revert
Please if someone can take the time to help me save a lot of time.
So I had to restore my Nexus 6 back to stock from CM12 to unlock the phone so I could start using Project Fi. So I went back set it up and was ready to restore back to cm12. Well every time I try to go back to one of my updates it runs for maybe a min and then the phone restarts and then just stays on start up screen without starting up.
this has nothing to do with the unlocking of the phone because 2 months ago when I needed to restore from cm12 it did the same thing!
So why cant I restore using twarp on my device and what do I have to do to get back my restore.
also when I try to just reload cm12 it fails .
PLEASE HELP ME SOMEONE! LOL
CM is your first problem. LOL All that aside. Usually when it stops on startup screen the kernel is borked. Try fastbooting/flashing a compatible kernel.
Try wipe cache and dalvik from recovery. If it still doesn't boot, wipe data, then restore apps using titanium
Can you guys please look at clip I made of the issue. Thanks so much!
https://youtu.be/3C8LtPu9LsA
<iframe width="420" height="315" src="https://www.youtube.com/embed/3C8LtPu9LsA" frameborder="0" allowfullscreen></iframe>
No need. Follow our advice
enzosly said:
Can you guys please look at clip I made of the issue. Thanks so much!
https://youtu.be/3C8LtPu9LsA
<iframe width="420" height="315" src="https://www.youtube.com/embed/3C8LtPu9LsA" frameborder="0" allowfullscreen></iframe>
Click to expand...
Click to collapse
To start I would actually wipe. Dalvik and cache is not a wipe. This only affects apps saved in ram.. Wipe system. Your flashing over old system and data. It is different flashing images than it is flashing restores. Can have files that are not overwritten. Basically a full dirty flash. Can't go stock and then dirty flash rom over the top. Especially CM. Too much doesn't match. Your flashing different bases over the top of each other. This is why people need permission fixes. The UID's don't match between the different bases. Have never used fix permissions unless testing and then shows us need to fully wipe.
prdog1 said:
To start I would actually wipe. Dalvik and cache is not a wipe. This only affects apps saved in ram.. Wipe system. Your flashing over old system and data. It is different flashing images than it is flashing restores. Can have files that are not overwritten. Basically a full dirty flash. Can't go stock and then dirty flash rom over the top. Especially CM. Too much doesn't match. Your flashing different bases over the top of each other. This is why people need permission fixes. The UID's don't match between the different bases. Have never used fix permissions unless testing and then shows us need to fully wipe.
Click to expand...
Click to collapse
ok so do a full wipe is what your saying then? Ill give it a try
enzosly said:
ok so do a full wipe is what your saying then? Ill give it a try
Click to expand...
Click to collapse
Yes. Also make sure boot is checked when make a backup. If restore doesn't contain kernel CM won't boot with stock kernel.
prdog1 said:
Yes. Also make sure boot is checked when make a backup. If restore doesn't contain kernel CM won't boot with stock kernel.
Click to expand...
Click to collapse
Ok so I did a full wipe and still same thing. I also went into fixing permissions and nothing.
what should I do next I guess? again thank you for taking the time
enzosly said:
Ok so I did a full wipe and still same thing. I also went into fixing permissions and nothing.
what should I do next I guess? again thank you for taking the time
Click to expand...
Click to collapse
Backup may be bad. Wipe everything and flash a full image/rom. Stopping on the splash usually means corrupted kernel. Rom not booting. If get to boot animation it is rom related. Need to start fresh. Google saves your apps so it no big deal. Rather have clean working rom than worry about apps and resetup.
enzosly said:
Ok so I did a full wipe and still same thing. I also went into fixing permissions and nothing.
what should I do next I guess? again thank you for taking the time
Click to expand...
Click to collapse
NEVER fix permissions.
Download the rom and flash it. Then use titanium to restore apps.extracted from.your nandroid.backup, if it can.
danarama said:
NEVER fix permissions.
Download the rom and flash it. Then use titanium to restore apps.extracted from.your nandroid.backup, if it can.
Click to expand...
Click to collapse
I agree if have to fix permissions rom is borked. Still looks like corrupted backup. Wipe all and fastboot stock or flash clean rom.
danarama said:
NEVER fix permissions.
Download the rom and flash it. Then use titanium to restore apps.extracted from.your nandroid.backup, if it can.
Click to expand...
Click to collapse
fix_permissions works, but not via recovery. i use stericsons fix_permissions app. it goes through and fixes permissions, per each app, when you are fully booted.
simms22 said:
fix_permissions works, but not via recovery. i use stericsons fix_permissions app. it goes through and fixes permissions, per each app, when you are fully booted.
Click to expand...
Click to collapse
It fixes mismatched UIDs which means you have a corrupt install. LOL
simms22 said:
fix_permissions works, but not via recovery. i use stericsons fix_permissions app. it goes through and fixes permissions, per each app, when you are fully booted.
Click to expand...
Click to collapse
Thing is they can't know what permissions everything is supposed to have, so its guess work and can lead to more problems l. Besides, permissions should never need fixing anyway
prdog1 said:
It fixes mismatched UIDs which means you have a corrupt install. LOL
Click to expand...
Click to collapse
whatever.. last time i installed anything was when m came out. honestly, ill use that app maybe twice a year, but it does work.
---------- Post added at 03:10 PM ---------- Previous post was at 03:08 PM ----------
danarama said:
Thing is they can't know what permissions everything is supposed to have, so its guess work and can lead to more problems l. Besides, permissions should never need fixing anyway
Click to expand...
Click to collapse
na, it doesnt ever need fixin', its just something ill do every once in a while. kind of a habit leftover from the older android days.
simms22 said:
whatever.. last time i installed anything was when m came out. honestly, ill use that app maybe twice a year, but it does work.
Click to expand...
Click to collapse
Just saying after years as a tester and thousands of builds. Was a big thing when they were porting roms to a different device. UIDs were broke all over the place. See the same thing if dirty flash different bases like Lolli over KitKat or a complete base change as an example ( L to M). Don't see mismatched UID's on updates made on same base.
prdog1 said:
Just saying after years as a tester and thousands of builds. Was a big thing when they were porting roms to a different device. UIDs were broke all over the place. See the same thing if dirty flash different bases like Lolli over KitKat or a complete base change as an example ( L to M). Don't see mismatched UID's on updates made on same base.
Click to expand...
Click to collapse
im very known as a dirty flasher btw :angel:
(and i did dirty flash m over terminus)
simms22 said:
im very known as a dirty flasher btw :angel:
(and i did dirty flash m over terminus)
Click to expand...
Click to collapse
Some have the luck. Apparently this poster don't.
prdog1 said:
Some have the luck. Apparently this poster don't.
Click to expand...
Click to collapse
its not luck, its all about doing it properly
After I flashed Android M Preview 3 this came up but I am able to boot fine and have already tried flashing back to 5.1.1 and repeating it. Any help? I have experience rooting and modifying system but this has never came up before.
SomeArabDude said:
After I flashed Android M Preview 3 this came up but I am able to boot fine and have already tried flashing back to 5.1.1 and repeating it. Any help? I have experience rooting and modifying system but this has never came up before.
Click to expand...
Click to collapse
No worries, it's a new feature that comes with preview 3 and the bootloader.
Never mind.
obtained said:
No worries, it's a new feature that comes with preview 3 and the bootloader.
Click to expand...
Click to collapse
Thanks! I was freaking out at first because I read in an article that is it says device is corrupt then that is very dangerous and your device could give out at any time.
i had the same prob.
stopped when i flashed the non encrypted bootloader i think fixed it for me
I got that too! What's up with that? Others have seen it here...
---------- Post added at 11:14 AM ---------- Previous post was at 11:11 AM ----------
http://forum.xda-developers.com/gen...or-message-t3156708/post61848119#post61848119
I did a factory reset and it disappeared!
kidhudi said:
i had the same prob.
stopped when i flashed the non encrypted bootloader i think fixed it for me
Click to expand...
Click to collapse
Really? I never heard of such a thing... Where did you find it?
cam30era said:
Really? I never heard of such a thing... Where did you find it?
Click to expand...
Click to collapse
I'm guessing he meant "boot.img"?
edved said:
I got that too! What's up with that? Others have seen it here...
---------- Post added at 11:14 AM ---------- Previous post was at 11:11 AM ----------
http://forum.xda-developers.com/gen...or-message-t3156708/post61848119#post61848119
I did a factory reset and it disappeared!
Click to expand...
Click to collapse
I did a factory rest and it didn't work for me?
kidhudi said:
i had the same prob.
stopped when i flashed the non encrypted bootloader i think fixed it for me
Click to expand...
Click to collapse
The bootloader has nothing to do with encryption. This doesn't exist.
Is it not this? http://www.droid-life.com/2015/07/27/operating-system-warnings-may-soon-come-to-your-boot-screen/
If it is, your device is fine. It just means your modified the operating system, and Google would like you to know that your data may no longer be safe with a modified system.
Further explanation of the warning here: https://support.google.com/nexus/answer/6185381?p=verified_boot&rd=1
SomeArabDude said:
After I flashed Android M Preview 3 this came up but I am able to boot fine and have already tried flashing back to 5.1.1 and repeating it. Any help? I have experience rooting and modifying system but this has never came up before.
Click to expand...
Click to collapse
Ignore. It's Google-policy. Google is growing and also the distance to the users. They don't like that we will modify the phone to our needs instead of the needs of Google or Telecom providers.
Its weird for me as I got the message but my system hasnt been rooted or anything (on my N9). was thinking of doing a factory reset. Still might do that just to get rid of it. (I did dirty flash preview 3 over preview 2)
y2whisper said:
Its weird for me as I got the message but my system hasnt been rooted or anything (on my N9). was thinking of doing a factory reset. Still might do that just to get rid of it. (I did dirty flash preview 3 over preview 2)
Click to expand...
Click to collapse
Factory reset won't fix it. Out of curiosity, do you have a decrypted kernel? Or TWRP recovery installed?
cam30era said:
Factory reset won't fix it. Out of curiosity, do you have a decrypted kernel? Or TWRP recovery installed?
Click to expand...
Click to collapse
neither left my n9 alone on that front.
y2whisper said:
neither left my n9 alone on that front.
Click to expand...
Click to collapse
Hhmm.. So you have the M3 system.img, bootloader, vendor.img, and stock recovery and still getting the message?
cam30era said:
Hhmm.. So you have the M3 system.img, bootloader, vendor.img, and stock recovery and still getting the message?
Click to expand...
Click to collapse
Correct. Thus me thinking it was just something went wrong by dirty flashing over preview 2 (which was completely stock as well)
y2whisper said:
Correct. Thus me thinking it was just something went wrong by dirty flashing over preview 2 (which was completely stock as well)
Click to expand...
Click to collapse
Yes, makes sense. If it bothers you, you could do a clean install....
Yeah plus the new restore feature on M works pretty well with restoring app data (provided you don't cut off your connection during the restore)
My nexus 6 is completely stock and i get that annoying " corrupt " message as well. It is just my bootloader that is unlocked if it's the reason of that message.
edit : i fixed my issue, check here if anyone have corrupt warning with a fully stock system.
Just manually updated to build QD1A.190821.014 Face Unlock was working fine before uodating now it won't let me Unlock for the life of me. I can still register my face just can't do the actual unlocking with it. It says Can't verify face Everytime.
I am having the same problem. This issue started after I flashed the November image. Would that be a problem caused by magisk?
Falargi said:
I am having the same problem. This issue started after I flashed the November image. Would that be a problem caused by magisk?
Click to expand...
Click to collapse
I'm not sure. I rooted it as soon as I flashed it. Maybe I will unroot it when I have more time and see what happens.
RLKirk said:
I'm not sure. I rooted it as soon as I flashed it. Maybe I will unroot it when I have more time and see what happens.
Click to expand...
Click to collapse
That's exactly what I did too. Let me know how it goes. I'll probably do the same.
When you flashed the November Image did you flash the correct one? As in you said you flashed the .014 version but was that the version you were on before? I have seen several posts where people were on the .007 and flashed the .014 or vis versa and it borked the face unlock. From what I have seen if you were on one of the other images you should be able to flash say the .007 version and it will fix the issue. If you are not sure which version you were on before it wouldn't hurt to try.
murphyjasonc said:
When you flashed the November Image did you flash the correct one? As in you said you flashed the .014 version but was that the version you were on before? I have seen several posts where people were on the .007 and flashed the .014 or vis versa and it borked the face unlock. From what I have seen if you were on one of the other images you should be able to flash say the .007 version and it will fix the issue. If you are not sure which version you were on before it wouldn't hurt to try.
Click to expand...
Click to collapse
This happened to me. The .007.A3 flash fixed it.
murphyjasonc said:
When you flashed the November Image did you flash the correct one? As in you said you flashed the .014 version but was that the version you were on before? I have seen several posts where people were on the .007 and flashed the .014 or vis versa and it borked the face unlock. From what I have seen if you were on one of the other images you should be able to flash say the .007 version and it will fix the issue. If you are not sure which version you were on before it wouldn't hurt to try.
Click to expand...
Click to collapse
I will try that. Thanks.
Should I go back to October and then flash November image then?
Sorry... Noob here
Falargi said:
I will try that. Thanks.
Should I go back to October and then flash November image then?
Sorry... Noob here
Click to expand...
Click to collapse
You should be fine flashing the .007 image over the .114. I know it will work if you clean flash by leaving the -W in. It should work taking the -W out. That just basically wipes all user data.
murphyjasonc said:
You should be fine flashing the .007 image over the .114. I know it will work if you clean flash by leaving the -W in. It should work taking the -W out. That just basically wipes all user data.
Click to expand...
Click to collapse
Yeah I was definitely on 007 before. I flashed 014 just assuming it was the newest so it would stop bugging me about the failed update. Where do I remove the -W at?
RLKirk said:
Yeah I was definitely on 007 before. I flashed 014 just assuming it was the newest so it would stop bugging me about the failed update. Where do I remove the -W at?
Click to expand...
Click to collapse
You edit the flash-all.bat file. The -w will be towards the end. Just delete it and save. Make sure you keep only one space between each word when you remove it. If the spacing is wrong it will fail. Then you can click on the file to flash like normal without wiping.
murphyjasonc said:
You edit the flash-all.bat file. The -w will be towards the end. Just delete it and save. Make sure you keep only one space between each word when you remove it. If the spacing is wrong it will fail. Then you can click on the file to flash like normal without wiping.
Click to expand...
Click to collapse
Cool thanks dude
murphyjasonc said:
You should be fine flashing the .007 image over the .114. I know it will work if you clean flash by leaving the -W in. It should work taking the -W out. That just basically wipes all user data.
Click to expand...
Click to collapse
It worked. Since I'm on T-Mobile I thought I would take .014, I guess I was wrong. Face unlock working again...
Thanks a lot.
Falargi said:
It worked. Since I'm on T-Mobile I thought I would take .014, I guess I was wrong. Face unlock working again...
Thanks a lot.
Click to expand...
Click to collapse
Glad I could help. :good:
I sent my Pixel 4 XL back in for a warranty replacement because of this issue. I wasn't sure if it was hardware related or not. Didn't want to take a chance on it being a hardware defect. I was on the November security update. I updated it as soon as I set up my phone so I didn't have a chance test it out on the October update.
murphyjasonc said:
Glad I could help. :good:
Click to expand...
Click to collapse
I'm having the same issue again.
Just flashed December image. I flashed .016A1.
Which the correct image for me?
I wish Google could make this easier.
Falargi said:
I'm having the same issue again.
Just flashed December image. I flashed .016A1.
Which the correct image for me?
I wish Google could make this easier.
Click to expand...
Click to collapse
https://support.google.com/pixelphone/thread/21769134?hl=en/
Falargi said:
I'm having the same issue again.
Just flashed December image. I flashed .016A1.
Which the correct image for me?
I wish Google could make this easier.
Click to expand...
Click to collapse
Which image were you on before? Google isn't making it easy this time around. You flashed the image for Japan and Taiwan. Depending on your carrier you should flash either the 011 or the 012.A1. Here is what Google support says
Pixel 4 (XL):
T-Mobile, Fi, EMEA: QQ1B.191205.011
Japan & Taiwan: QQ1C.191205.016.A1
All other carriers: QQ1B.191205.012.A1
There is a bug with the December image also. If you flash the December image with the -W doing a complete wipe face unlock will not work. If you remove the -W and upgrade from November it will do like it should. That was my experience anyway. If you did happen to wipe your phone on the December image you will have to flash the November image with the -W. Set your phone up again and the flash the December image without the -W and it will be fixed.
murphyjasonc said:
Which image were you on before? Google isn't making it easy this time around. You flashed the image for Japan and Taiwan. Depending on your carrier you should flash either the 011 or the 012.A1. Here is what Google support says
Pixel 4 (XL):
T-Mobile, Fi, EMEA: QQ1B.191205.011
Japan & Taiwan: QQ1C.191205.016.A1
All other carriers: QQ1B.191205.012.A1
There is a bug with the December image also. If you flash the December image with the -W doing a complete wipe face unlock will not work. If you remove the -W and upgrade from November it will do like it should. That was my experience anyway. If you did happen to wipe your phone on the December image you will have to flash the November image with the -W. Set your phone up again and the flash the December image without the -W and it will be fixed.
Click to expand...
Click to collapse
I was on .007.A3 (November) but I'm on T-Mobile.
I will try fishing November again and do as you said.
Thank you
Falargi said:
I was on .007.A3 (November) but I'm on T-Mobile.
I will try fishing November again and do as you said.
Thank you
Click to expand...
Click to collapse
I think your best bet is to flash the 011 image. I would try flashing it first with the -W removed. You might get lucky and save yourself some time. If that doesn't work then flash November again and go from there.
Is this issue related to root? I had a fresh install with the latest December patches (qq1b.191205.011) that did not work with Face Unlock. However, that attempt was also rooted in the typical fashion with Magisk. After performing a full re-install of qq1b, I was able to use Fack Unlock normally. I'll re-apply root later today and let you know if that was the tipping point.