I have successfully setup face unlock on my Pixel 4 xl and it won't recognize my face to unlock the phone. I've deleted my face data several times and set it up again and it keeps doing the same thing. I just factory reset my phone and am going to try it again.
Are you wearing sunglasses or trying to use it out in the sun?
jimv1983 said:
Are you wearing sunglasses or trying to use it out in the sun?
Click to expand...
Click to collapse
No
Today my phone alerted me I need to re-enroll my face(although the unlock has been working fine...). Tried to reboot to ignore that message, then eventually I've deleted the face data and re-enrolled. Now I have the same issue like the OP starter. Will try to flash factory image but next week once I get my bank account pins sent. Probably some permission issue, where the data doesn't get saved properly or can't be read or something..but no time to fiddle around.
bender_007 said:
Today my phone alerted me I need to re-enroll my face(although the unlock has been working fine...). Tried to reboot to ignore that message, then eventually I've deleted the face data and re-enrolled. Now I have the same issue like the OP starter. Will try to flash factory image but next week once I get my bank account pins sent. Probably some permission issue, where the data doesn't get saved properly or can't be read or something..but no time to fiddle around.
Click to expand...
Click to collapse
Same thing happened to me today. I have been ignoring the message.
Sent from my phone
I have been having the same issue as of today. I was going to flash the Full January stock image but I had to redownload it. I looked on the factory image website and the January image has been removed? I have it on my work computer and am currently transferring it to the one im currently on. Does anyone know why it was suddenly removed? the OTA image is still available on the website.
Buddyjohn said:
I have been having the same issue as of today. I was going to flash the Full January stock image but I had to redownload it. I looked on the factory image website and the January image has been removed? I have it on my work computer and am currently transferring it to the one im currently on. Does anyone know why it was suddenly removed? the OTA image is still available on the website.
Click to expand...
Click to collapse
I'm seeing it on there now. I had the same problem and had to factory reset to fix it.
brandon5491 said:
I'm seeing it on there now. I had the same problem and had to factory reset to fix it.
Click to expand...
Click to collapse
since i didnt see the january update i flashed the december image with the wipe and the face unlock still is not working? will try january next i guess...
Buddyjohn said:
since i didnt see the january update i flashed the december image with the wipe and the face unlock still is not working? will try january next i guess...
Click to expand...
Click to collapse
I tried reflashing the Jan update and then the Dec one too. No luck. I read somewhere else speculation it has something to do with the Titan M chip and only a factory reset would clear/fix it. And that's what worked for me in the end. Huge PITA.
brandon5491 said:
I tried reflashing the Jan update and then the Dec one too. No luck. I read somewhere else speculation it has something to do with the Titan M chip and only a factory reset would clear/fix it. And that's what worked for me in the end. Huge PITA.
Click to expand...
Click to collapse
That is a huge flaw! I downloaded a fresh december factory image as well as the january image. used the flash all.bat and everything. left the "-w" to wipe the personal data as well. it still didnt work. the fix was to factory reset through the settings! atleast in my mind it makes sense that when you flash a factory image that wipes the phone that would also get reset. may not a huge flaw but still. really annoying. thanks for the help!
brandon5491 said:
I tried reflashing the Jan update and then the Dec one too. No luck. I read somewhere else speculation it has something to do with the Titan M chip and only a factory reset would clear/fix it. And that's what worked for me in the end. Huge PITA.
Click to expand...
Click to collapse
Buddyjohn said:
That is a huge flaw! I downloaded a fresh december factory image as well as the january image. used the flash all.bat and everything. left the "-w" to wipe the personal data as well. it still didnt work. the fix was to factory reset through the settings! atleast in my mind it makes sense that when you flash a factory image that wipes the phone that would also get reset. may not a huge flaw but still. really annoying. thanks for the help!
Click to expand...
Click to collapse
Unfortunately true. Take a look at this post, there are some explanations.
Related
My Nook just auto downloaded and installed an update that screwed up my device! Anyone else see this? WTF?
Does it automatically do the update? was your Nook Color rooted?
foxfire235 said:
My Nook just auto downloaded and installed an update that screwed up my device! Anyone else see this? WTF?
Click to expand...
Click to collapse
Yeah, does it do it automatically. I have my Nook Color at home connected to my Wi-Fi. Hopefully, it doesn't download just download it without me being there =T
foxfire235 said:
My Nook just auto downloaded and installed an update that screwed up my device! Anyone else see this? WTF?
Click to expand...
Click to collapse
How did it screw it up? I haven't received an update, been tethering all day
What is your software version in settings after the update?
I was using a rooted nook. It bricked it, and I couldn't get past the B&N logo on boot. I just had to do a factory reset.
After the factory reset, I got a confirmation dialog that said - "your nook has been updated to software version 1.0.0" ??? that doesn't seem like an update. Although maybe that's the factory default?
foxfire235 said:
I was using a rooted nook. It bricked it, and I couldn't get past the B&N logo on boot. I just had to do a factory reset.
Click to expand...
Click to collapse
Not to be a pr*ck, but if you're still able to do a factory reset, that would mean it wasn't "bricked", or did I miss something there?
Did the unit want to auto-update again once you reset?
-CC
clockcycle said:
Not to be a pr*ck, but if you're still able to do a factory reset, that would mean it wasn't "bricked", or did I miss something there?
-CC
Click to expand...
Click to collapse
I guess we have different definitions of brick. What would you call a device that doesn't boot?
A
A device that doesn't boot is a soft-brick
a brick cannot be fixed through trivial methods.
foxfire235 said:
I guess we have different definitions of brick. What would you call a device that doesn't boot?
Click to expand...
Click to collapse
As I understood "brick" means it's totally useless, other than as a paper weight or a door stop, essentially just dead weight.
I think if your device doesn't boot, but you can still recover, would be exactly that. {my device didn't boot, I had to factory reset it}
-CC
I wonder if they have something in there to detect a change to the OS that forces it to re-download ?
clockcycle said:
As I understood "brick" means it's totally useless, other than as a paper weight or a door stop, essentially just dead weight.
I think if your device doesn't boot, but you can still recover, would be exactly that. {my device didn't boot, I had to factory reset it}
-CC
Click to expand...
Click to collapse
in the venacular, "brick" means that the device is dead and cannot be fixed without replacing hardware. If a 'simple' reset will restore the device to working order, it isn't bricked it is just in a bad state.
We try to avoid the term "brick" when describing anything else because we don't want to gve the impression that we might be saying "I just did what I read in your post on the forum and now my device is broken beyond repair".
I'm fairly certain (but not 100% positive) that FW version 1.0.0 is installed automatically when you are registering the NC for the first time (like when the OOB setup is first done). After my initial setup I checked the version and 1.0.0 was installed.
And I've also noticed that if you do a factory reset and re-initiate the device 1.0.0 is automatically installed.
I'd like to see some verification that there is new software out there than this one user's report. Confirmation?
PHiZ said:
I'd like to see some verification that there is new software out there than this one user's report. Confirmation?
Click to expand...
Click to collapse
I remember somewhere, that there was a way to trigger it, or something like that... but its not a new firmware but just a redownload of 1.0
I think this is a known issue for some users after they root. I've read it before on here somewhere and in IRC.
MBM or Pokey9000 can confirm but i'm pretty sure it's nothing to be concerned with. Just re-root and see if you have anymore issues.
Mine was updated to 1.0.0 as well but I was still able to root it and do Angry Birds though.
nk414 said:
Mine was updated to 1.0.0 as well but I was still able to root it and do Angry Birds though.
Click to expand...
Click to collapse
People need to clarify more what they are talking about here.
Did you have it rooted before it was "updated" ?
Apparently these devices were rooted. While I'm sure there's a small, very small minority of XDA-ers who don't mess with their devices, the rest of us do. From a statistical standpoint it would stand to reason that these NCs were rooted.
My 64GB Nexus is now saying it has 23gb of total storage and 21gb available. I had to reflash the stock ROM after a failed twrp flash. Is there anyway to fix this? I have already tried reflashing and wiping the phone 2 times but the storage decreases each time.
Use a factory image and start over.
ericsignals said:
Use a factory image and start over.
Click to expand...
Click to collapse
I've already done that twice
Pilz said:
I've already done that twice
Click to expand...
Click to collapse
Double check and make sure you have the latest SDK and/or just download the latest regardless. N5 folks have been having similar issues since the Lollipop release.
jhax01 said:
Double check and make sure you have the latest SDK and/or just download the latest regardless. N5 folks have been having similar issues since the Lollipop release.
Click to expand...
Click to collapse
I can try to redownload the SDK, but my question is what does the SDK have to do with losing space on my phone?
I don't pretend to know what the cause is behind it but when the 5.0 factory images were released, people who flashed it with an older version of fastboot were losing storage on the Nexus 5.
Sent from my Nexus 5 using Tapatalk
I fixed it after doing a factory reset then flashing it again. I double checked and I already had the latest SDK. Its really weird how it took flashing 3 times to work.
Pilz said:
I fixed it after doing a factory reset then flashing it again. I double checked and I already had the latest SDK. Its really weird how it took flashing 3 times to work.
Click to expand...
Click to collapse
I am in the same boat. Even did a factory reset and flashed the factory image but still stuck with 23GB on my 64GB. What exactly did you do to fix this?
the.emilio said:
I am in the same boat. Even did a factory reset and flashed the factory image but still stuck with 23GB on my 64GB. What exactly did you do to fix this?
Click to expand...
Click to collapse
I re-downloaded the latest SDK and then reflashed the images again. It took a few times before it reset. I also used fastboot erase system if I remember correctly.
Pilz said:
I re-downloaded the latest SDK and then reflashed the images again. It took a few times before it reset. I also used fastboot erase system if I remember correctly.
Click to expand...
Click to collapse
Did you flash each image individually since the flash all gives that no system.img error? Just want to make sure I can duplicate what you did.
the.emilio said:
Did you flash each image individually since the flash all gives that no system.img error? Just want to make sure I can duplicate what you did.
Click to expand...
Click to collapse
I flashed each one manually. The bat file doesn't work so that's the only way to do it. I don't remember the order I flashed everything in, but I remember that I used fastboot to wipe the phone before flashing. I kept trying different things until it showed the right storage then I decrypted it and flashed TWRP and used CF auto root. One of my mistakes was rooting before checking because it was a waste of time if I had to flash it again.
I may have done a factory reset st one point but I don't remember because it was late and I was watching TV with my wife whole doing this.
Pilz said:
I flashed each one manually. The bat file doesn't work so that's the only way to do it. I don't remember the order I flashed everything in, but I remember that I used fastboot to wipe the phone before flashing. I kept trying different things until it showed the right storage then I decrypted it and flashed TWRP and used CF auto root. One of my mistakes was rooting before checking because it was a waste of time if I had to flash it again.
I may have done a factory reset st one point but I don't remember because it was late and I was watching TV with my wife whole doing this.
Click to expand...
Click to collapse
Figured. I will keep trying. Thanks!
---------- Post added at 11:56 PM ---------- Previous post was at 11:08 PM ----------
After about 10 attempts it turns out all i had to do was fastboot format cache then fastboot format userdata. Reboot and boom restored to normal. LMAO! Wasted 4 hours tonight just for that. Live and learn!
Just do a factory reset in recovery WITHOUT reflashing and the problem is taken care of.
Seems a like a bug in the factory images that can cause of wrong partition sizes.
Worked on my N9 (which I already sent back to Google due to excessive lightbleed lol)
I had the same issue after trying to root the phone showed 23 GB.
I was able to get back to 53 GB after wipine cache and formatting user data, but that still seems like I'm missing something . I did not check how much storage was available before I started.
Can any one tell me what the storage numbers should be on like on a stock device with nothing installed please?
I remember hearing about this same issue with the Nexus 5. Don't recall the cause though. Sorry folks I know this post is useless I'm just excited to be getting my Nexus 6 so I perusing the forums.
Hey All,
Finally got my nexus 6 and I'm pumped to have a developer phone again. Haven't done anything since I got rid of my galaxy nexus a year or so ago, so I'm a bit rusty. Sorry if this has been posted before, I searched but couldn't find anything related to this. Long story short, I had my phone unlocked and rooted and have TWRP installed fine. I just went in and cleared the cache, dalvik cache, and fixed permissions... and now I'm stuck in a bootloop. After researching I'm pretty sure it was the fixed permissions that messed it up, I didn't know that it didn't work on lollipop at the time. I've come to the conclusion I need to reflash the stock images and start from scratch. The only problem is I'm currently stuck at work for another 4 hours and can't use adb at all on this computer. So I'm wondering if anyone knew of another way to fix from just the phone. Thanks in advanced guys!
rev89 said:
Hey All,
Finally got my nexus 6 and I'm pumped to have a developer phone again. Haven't done anything since I got rid of my galaxy nexus a year or so ago, so I'm a bit rusty. Sorry if this has been posted before, I searched but couldn't find anything related to this. Long story short, I had my phone unlocked and rooted and have TWRP installed fine. I just went in and cleared the cache, dalvik cache, and fixed permissions... and now I'm stuck in a bootloop. After researching I'm pretty sure it was the fixed permissions that messed it up, I didn't know that it didn't work on lollipop at the time. I've come to the conclusion I need to reflash the stock images and start from scratch. The only problem is I'm currently stuck at work for another 4 hours and can't use adb at all on this computer. So I'm wondering if anyone knew of another way to fix from just the phone. Thanks in advanced guys!
Click to expand...
Click to collapse
you can try flashing any rom, since you have twrp installed, or you can try wiping data(factory reset).
simms22 said:
you can try flashing any rom, since you have twrp installed, or you can try wiping data(factory reset).
Click to expand...
Click to collapse
Unfortunately, I do not have any ROMs saved on my phone yet. I just got it last night with only maybe an hour or two of playing time. I also tried factory reset through TWRP and am still experiencing the bootloop. Would formatting data help? I feel like it would, but like I said, I'm rusty.
rev89 said:
Unfortunately, I do not have any ROMs saved on my phone yet. I just got it last night with only maybe an hour or two of playing time. I also tried factory reset through TWRP and am still experiencing the bootloop. Would formatting data help? I feel like it would, but like I said, I'm rusty.
Click to expand...
Click to collapse
you can try, i dont think itll help. all you got to do is download any rom/gapps/supersu to your phone then flash it. i use rastapop.
simms22 said:
you can try, i dont think itll help. all you got to do is download any rom/gapps/supersu to your phone then flash it. i use rastapop.
Click to expand...
Click to collapse
I know, but I can't boot my phone to download it. Hence, why I'm going to have to flash the stock images when I get home. How is rastapop? I need to find something since the big names aren't out yet. I'll try it out later once everything is fixed. I'm mad I ran into this boot loop because custom rom was next on my list of things to do haha
rev89 said:
I know, but I can't boot my phone to download it. Hence, why I'm going to have to flash the stock images when I get home. How is rastapop? I need to find something since the big names aren't out yet. I'll try it out later once everything is fixed. I'm mad I ran into this boot loop because custom rom was next on my list of things to do haha
Click to expand...
Click to collapse
you didnt happen to make a backup in recovery, did you? if you did, just restore it.
simms22 said:
you didnt happen to make a backup in recovery, did you? if you did, just restore it.
Click to expand...
Click to collapse
Nope, would have made life a lot easier if I did. I was just kicking myself in the ass for that earlier.
Edit: nvm, forgot you don't have adb access
Sent from my Nexus 6 using XDA Free mobile app
Thanks for the help guys. I'm just gonna start from scratch when I get home... god I hate not having a phone.
Yah I realized fixing permissions messes it up. And also if u wipe internal storage the phone looses the system ui and the back home menu buttons as well
well thats good to know. Will it still do that if I'm not encrypted?
rev89 said:
Unfortunately, I do not have any ROMs saved on my phone yet. I just got it last night with only maybe an hour or two of playing time. I also tried factory reset through TWRP and am still experiencing the bootloop. Would formatting data help? I feel like it would, but like I said, I'm rusty.
Click to expand...
Click to collapse
Probably too late to do, but USB-OTG cable and a jump drive. I have downloaded stuff on work PC, copied to jump drive and flashed it on phone with TWRP from the jump drive.
I can personally confirm the permission fix in TWRP recovery breaks the stock L5.0.0 and 5.0.1 and I assume probably most ROMs? There seems to be several threads about this.
githyanki said:
Probably too late to do, but USB-OTG cable and a jump drive. I have downloaded stuff on work PC, copied to jump drive and flashed it on phone with TWRP from the jump drive.
Click to expand...
Click to collapse
you can flash from a jump drive? I didn't know that
has any one been having any trouble with their wifi on their nexus 6, randomly the wifi toggle will stop working the toggle will be off and it still says "Turning Wi-Fi on..." i've booted into recovery and cleared cache and rebooted the phone and it worked the first time and it's been acting up again and this time clearing the cache isn't working does anyone else have any ideas without doing a factory reset.
humpty123 said:
has any one been having any trouble with their wifi on their nexus 6, randomly the wifi toggle will stop working the toggle will be off and it still says "Turning Wi-Fi on..." i've booted into recovery and cleared cache and rebooted the phone and it worked the first time and it's been acting up again and this time clearing the cache isn't working does anyone else have any ideas without doing a factory reset.
Click to expand...
Click to collapse
maybe try just flashing the system img, then wipe cache's again before booting. if that doesnt work, its may be time for the dreaded fdr.
I've never been into flashing system img & fdr? It's just sad because I had the same issue before also losing signal with my device. Til I got a replacement and the replacement device is starting to act up also.
Sent from my Nexus 6 using XDA
bweN diorD said:
maybe try just flashing the system img, then wipe cache's again before booting. if that doesnt work, its may be time for the dreaded fdr.
Click to expand...
Click to collapse
okay so put the phone in recovery and did cache wipe and reset it from recovery also and got everything set up again and still it shows Wi-Fi toggled off and saying turning on Wi-Fi im not sure what todo at this point.
https://goo.gl/photos/bdHB8Nw2tbH71LMj6
humpty123 said:
okay so put the phone in recovery and did cache wipe and reset it from recovery also and got everything set up again and still it shows Wi-Fi toggled off and saying turning on Wi-Fi im not sure what todo at this point.
Click to expand...
Click to collapse
my only other suggestion would be to re-flash. you could try just the system partition, but if it were me i would just go all in for full clean flash.
im sure Simms will get on me for saying so, but you can just grab wugs toolkit and be done in 20min or so.
bweN diorD said:
my only other suggestion would be to re-flash. you could try just the system partition, but if it were me i would just go all in for full clean flash.
im sure Simms will get on me for saying so, but you can just grab wugs toolkit and be done in 20min or so.
Click to expand...
Click to collapse
I've never flashed before i know from what i hear its really easy for Nexus devices. but i'm just curious what would of caused this like from my first N6 since December and it acts up now in Sept and having the replacement N6 acting up the same way.
Is it rooted with mods or completely stock? If stock, try deleting the saved wireless networks..
danarama said:
Is it rooted with mods or completely stock? If stock, try deleting the saved wireless networks..
Click to expand...
Click to collapse
100% stock I can't get access to any saved networks at all
https://goo.gl/photos/34veZPQvW3pLiB5YA
humpty123 said:
I've never flashed before i know from what i hear its really easy for Nexus devices. but i'm just curious what would of caused this like from my first N6 since December and it acts up now in Sept and having the replacement N6 acting up the same way.
Click to expand...
Click to collapse
these random issues usually come from a corrupt file, either by an update or some other means. its hard to impossible to pinpoint the cause usually.
if you never flashed before, its best to read up on it a bit first. wugs walks you through the steps, from downloading the files, and drivers, to the flashing. its not foolproof, but if you follow the lead of the script, its not hard to figure out.
bweN diorD said:
these random issues usually come from a corrupt file, either by an update or some other means. its hard to impossible to pinpoint the cause usually.
if you never flashed before, its best to read up on it a bit first. wugs walks you through the steps, from downloading the files, and drivers, to the flashing. its not foolproof, but if you follow the lead of the script, its not hard to figure out.
Click to expand...
Click to collapse
well i have before but that was so long ago and that was for my MyTouch and HTC Sensation but that was years ago. Now I know things are easier but I've never really been into flashing and the only reason I did back then was for updates and different version of Sense UI but since I've been using Nexus Devices I didn't have a need or desire to actually flash. Pretty much I'm a NOOB! :laugh:
but I don't see why wouldn't a factory reset fix it. even if it was temp.
humpty123 said:
well i have before but that was so long ago and that was for my MyTouch and HTC Sensation but that was years ago. Now I know things are easier but I've never really been into flashing and the only reason I did back then was for updates and different version of Sense UI but since I've been using Nexus Devices I didn't have a need or desire to actually flash. Pretty much I'm a NOOB! :laugh:
but I don't see why wouldn't a factory reset fix it. even if it was temp.
Click to expand...
Click to collapse
a factory reset only deletes data, it does not restore any of the file system to its original state.
bweN diorD said:
a factory reset only deletes data, it does not restore any of the file system to its original state.
Click to expand...
Click to collapse
oh... so when I called Motorola they told me to wipe cache how did that help the first time ?
humpty123 said:
oh... so when I called Motorola they told me to wipe cache how did that help the first time ?
Click to expand...
Click to collapse
clearing the cache is always a good idea, i think i suggested that earlier.
i dont know how to explain well what cache is exactly, its not part of the file system, its more like temp data storage i believe.
bweN diorD said:
clearing the cache is always a good idea, i think i suggested that earlier.
i dont know how to explain well what cache is exactly, its not part of the file system, its more like temp data storage i believe.
Click to expand...
Click to collapse
yeah i tried that a few times today and it did nothing... i'm about to give up since i don't have a PC anymore i use a Chromebook
humpty123 said:
yeah i tried that a few times today and it did nothing... i'm about to give up since i don't have a PC anymore i use a Chromebook
Click to expand...
Click to collapse
def of cache from google
"In cell phones and networks, a cache usually refers to a memory storage area in the phone or network that stores copies of information that is likely to be needed in the near future, so it can be accessed faster."
i dont know how to flash with a chrome book, if possible. sorry
bweN diorD said:
def of cache from google
"In cell phones and networks, a cache usually refers to a memory storage area in the phone or network that stores copies of information that is likely to be needed in the near future, so it can be accessed faster."
i dont know how to flash with a chrome book, if possible. sorry
Click to expand...
Click to collapse
all i know it happened a day after i got the last update from T-Mobile. i should them back and tell them i'm having the same issues with my phone have them replace it for me again.
humpty123 said:
all i know it happened a day after i got the last update from T-Mobile. i should them back and tell them i'm having the same issues with my phone have them replace it for me again.
Click to expand...
Click to collapse
thats pretty consistent with what i said earlier. these type of issues frequently arise after updates. files dont update exactly right and something gets corrupted.
bweN diorD said:
thats pretty consistent with what i said earlier. these type of issues frequently arise after updates. files dont update exactly right and something gets corrupted.
Click to expand...
Click to collapse
i decided to call T-Moblie and talk to them they told me to take it to a store and get it dianogsed and they will call to get it replaced since it is the 64GB and stores don't have it.... I just want the Wi-Fi to work even though i don't use it all the time but still.
Can't figure out how to disable it asking for the PIN at initial boot.. I'm returning to Tmobile(JUMP).. I'm assuming they'll have a problem with this. I miss good 'ol odin , just flash stock. Any info or help to get it back to stock would be appreciated, it's been well over a year since I've rooted/unlocked and I'm going to start restoring tonight.
Odin?!?! With Nexus devices you can use fastboot which is much more powerful than Odin.
Here are factory images for Nexus devices and on the page are included instructions on how to return to stock.
its a google security feature. even if you factory reset 10 times, itll still ask for your pin. just enter it, then you can change it. or did you steal the phone? btw, thats why its there, so no one can steal your phone, factory reset it, then use it.
Thanks for the input.. didn't know it was a google feature, was thinking it was something with the rom I installed since it started around that time(cataclysm). Anyway.. I got it figured out.. downloaded stock image and ran the flashalll.bat .. sheesh that was easy.
tri0xinn said:
Thanks for the input.. didn't know it was a google feature, was thinking it was something with the rom I installed since it started around that time(cataclysm). Anyway.. I got it figured out.. downloaded stock image and ran the flashalll.bat .. sheesh that was easy.
Click to expand...
Click to collapse
the only issue others could have is flash-all not working. to get around that, you just flash each part separately.