OG Pixel XL 32GB on Project Fi, rooted with Magisk 17.1, previously on Android Pie 9.0.0 August security update.
Just sideloaded to September security update via the usual method. Upon booting, fingerprint sign-in was disabled, and in "Settings," it appeared that my fingerprints had been cleared. Tried enrolling fingerprints via "Pixel Imprint," but while it registers reads properly, enrollment fails at the last step with the message "Enrollment was not completed. Fingerprint enrollment didn't work. Try again or use a different finger." No luck with other fingers. Gestures (notification shade pulldown) still works. Tried flashing back to August update, but same issue persisted.
Anyone else have this issue, or know of a solution? Thanks!
davidrqli said:
OG Pixel XL 32GB on Project Fi, rooted with Magisk 17.1, previously on Android Pie 9.0.0 August security update.
Just sideloaded to September security update via the usual method. Upon booting, fingerprint sign-in was disabled, and in "Settings," it appeared that my fingerprints had been cleared. Tried enrolling fingerprints via "Pixel Imprint," but while it registers reads properly, enrollment fails at the last step with the message "Enrollment was not completed. Fingerprint enrollment didn't work. Try again or use a different finger." No luck with other fingers. Gestures (notification shade pulldown) still works. Tried flashing back to August update, but same issue persisted.
Anyone else have this issue, or know of a solution? Thanks!
Click to expand...
Click to collapse
I didn't not have that issue this upgrade or any others. The only time I have lost Fingerprints is when I have had to disable security when TWRP is unable to decrypt. But that was not the case for September update. You might try disabling security completely. Rebooting. Then reenabling security and Pixel Imprint. Maybe something didn't get cleared all the way when your Pixel Imprint got disabled or partially cleared...
sb1893 said:
I didn't not have that issue this upgrade or any others. The only time I have lost Fingerprints is when I have had to disable security when TWRP is unable to decrypt. But that was not the case for September update. You might try disabling security completely. Rebooting. Then reenabling security and Pixel Imprint. Maybe something didn't get cleared all the way when your Pixel Imprint got disabled or partially cleared...
Click to expand...
Click to collapse
Thanks for the tip. Just tried this and no dice, however. Have never had any issues with any previous updates, including with Oreo when a lot of other people were having fingerprint reader problems.
davidrqli said:
Thanks for the tip. Just tried this and no dice, however. Have never had any issues with any previous updates, including with Oreo when a lot of other people were having fingerprint reader problems.
Click to expand...
Click to collapse
Any progress on this? Were you able to get it working?
sb1893 said:
Any progress on this? Were you able to get it working?
Click to expand...
Click to collapse
Nope, still the exact same. Issues also persist in Safe Mode.
Had this issue with DP4. Had to do a factory reset. Sorry.
jaytv said:
Had this issue with DP4. Had to do a factory reset. Sorry.
Click to expand...
Click to collapse
Gotcha... thanks. Not in a position to do a factory reset now, but maybe in a week or so when I'm back from a trip. Anyone else have any luck fixing this without a factory reset?
Update: Did a full factory reset, which fixed the problem. Not an ideal situation, but at least it worked.
davidrqli said:
Update: Did a full factory reset, which fixed the problem. Not an ideal situation, but at least it worked.
Click to expand...
Click to collapse
Glad you got it sorted. That normally does the trick but it does suck if you don't have everything backed up.
Related
I love the fact that this phone is still getting security updates btw. But after the November security update TOS317M the camera and flashlight stopped working. Still running stock haven't rooted or put TWRP. Has anyone else experienced this?
Edit: Taking out the battery fixed it
dennis212 said:
I love the fact that this phone is still getting security updates btw. But after the November security update TOS317M the camera and flashlight stopped working. Still running stock haven't rooted or put TWRP. Has anyone else experienced this?
Edit: Taking out the battery fixed it
Click to expand...
Click to collapse
My camera is working but since the update it has changed the storage location with no option to change it
Had anyone gotten these yet??
cswee1932 said:
Had anyone gotten these yet??
Click to expand...
Click to collapse
I sideloaded the OTA the same day it released instead of waiting for it to be pushed to my phone.
Sent from my Pixel XL using Tapatalk
I'm still on DP2 with the Nov 5 patch level. Figured being in the beta program I'd get the official patch right away but nothing yet.
Mee too still no dec patch
my understanding is on beta you will not get the security patches, when the dp2 becomes the propper version then remember to come out the beta program
Still no OTA for my Pixel XL.
Stock 8.0 Nov security patch.
Sideloaded it here.. not waiting!
Definitely the 8.1
So, there are 2 Google Pixel 2 XL phones in the house... 1 64GB and 1 128GB. Guess which one got the 8.1 update (528GB)? That's right, the 64GB! The 128GB is still waiting...
Both phones were purchased straight from Google and added to AT&T
cswee1932 said:
Had anyone gotten these yet??
Click to expand...
Click to collapse
I did the check for updates button and installed the 1st day :good:
AddisG said:
Sideloaded it here.. not waiting!
Click to expand...
Click to collapse
Same exact thing I did the minute I got home from work the day it was released! Don't understand why all ppl won't do this instead of complaining about waiting for the OTA to get pushed to their phones!
Sent from my Pixel XL using Tapatalk
piscesjoey said:
Same exact thing I did the minute I got home from work the day it was released! Don't understand why all ppl won't do this instead of complaining about waiting for the OTA to the push to their phones!
Click to expand...
Click to collapse
Right on!:good:
In my case i just opted out beta program, check settings and received 8.0.0 notification. It erased my phone but i don't care. Installed and check for 8.1. Received as well and done.
Backup tool in pixel and auto fill for my passwords made it easy
Now I'm on 8.1 december security patch. Always locked and never with root
Cristiano Matos said:
In my case i just opted out beta program, check settings and received 8.0.0 notification. It erased my phones but i don't care. Installed and check for 8.1. Received as well and done.
Backup tool in pixel and auto fill for my passwords made it easy
Now i on 8.1 december security patch. Always locked and never with root
Click to expand...
Click to collapse
That's what's up! Not rooting this baby. Loving how smooth 8.1 is..
cswee1932 said:
Had anyone gotten these yet??
Click to expand...
Click to collapse
I also sideloaded shortly after it was posted on my Pixel XL. However, I just noticed this article...
http://www.androidpolice.com/2017/1...pulling-latest-otas-promised-itll-fixed-2018/
Apparently, the "Check for Update" button functionality was broken recently via an update to Google Play Services. That bug won't be corrected until early in 2018. So - it appears the best way to get the 8.1 update (if you don't want to wait until next year), would be to sideload the OTA or flash factory images - depending on your preference and bootloader status...
Good luck.
S
Do people still capture the incremental OTA update filename from logcat, and post for people to sideload, or since Google publishes the full OTA's, do people just sideload that? Wondering if there's really a difference? Thanks!
Got it to update! I read on another forum to put it in airplane mode, clear the cache then the data in Google services framework, and then turn airplane mode off.... almost immediately after turning airplane mode off, I got the notification for the latest update!
cswee1932 said:
Got it to update! I read on another forum to put it in airplane mode, clear the cache then the data in Google services framework, and then turn airplane mode off.... almost immediately after turning airplane mode off, I got the notification for the latest update!
Click to expand...
Click to collapse
can confirm this worked for me but had to delete data not just cache...thanks :good:
I got the OTA for DP2 yesterday afternoon (was in central time in US)
cswee1932 said:
Got it to update! I read on another forum to put it in airplane mode, clear the cache then the data in Google services framework, and then turn airplane mode off.... almost immediately after turning airplane mode off, I got the notification for the latest update!
Click to expand...
Click to collapse
Thank you. Mine didn't show up after clearing cache and data. I rebooted and there is was.
My question is that the sideload file on Google's download page is approximately 960 MB while the OTA notification I just received is about 567MB. Are they the same?
Thanks
Fouad Aslam said:
Thank you. Mine didn't show up after clearing cache and data. I rebooted and there is was.
My question is that the sideload file on Google's download page is approximately 960 MB while the OTA notification I just received is about 567MB. Are they the same?
Thanks
Click to expand...
Click to collapse
Obviously they're not the same. It seems Google only needed to update your particular rom the 567 MB. Were you on the beta?
As the title states lately I have been having fingerprint issues. Setting up fingerprint to unlock my phone works perfectly with the phone itself. When it's comes to apps Chase, Cinemark , TMobile setting up fingerprint verification goes through correctly. Now opening the apps and using my fingerprint to verify does not unlock the app. Apps just keep telling me to put my assigned fingerprint in again. Anyone noticing issues lately? Is there any way to troubleshoot this? I have reflashed the OTA (8.1 Oreo - March update) multiple times- no change.
Running stock 8.1 Oreo March update
Any other suggestions?
LubbocksFall said:
As the title states lately I have been having fingerprint issues. Setting up fingerprint to unlock my phone works perfectly with the phone itself. When it's comes to apps Chase, Cinemark , TMobile setting up fingerprint verification goes through correctly. Now opening the apps and using my fingerprint to verify does not unlock the app. Apps just keep telling me to put my assigned fingerprint in again. Anyone noticing issues lately? Is there any way to troubleshoot this? I have reflashed the OTA (8.1 Oreo - March update) multiple times- no change.
Running stock 8.1 Oreo March update
Any other suggestions?
Click to expand...
Click to collapse
I have not had any issues with apps that rely on / give the option of fingerprint authentication. I also have Chase installed and I just tested it and it works fine. I also have Amex, Bank of America, alarm.com, ADT Pulse and fingerprint access seems to be working fine on all of them. I am also running stock 8.1 Oreo / March update- but I am unlocked and rooted with Magisk. One suggestion based on some Fingerprint related struggles I had recently (when TWRP couldn't decrypt and I had to remove Fingerprint/pattern security during the update process and then add back after updating/rooting)....I found that some apps that had already had Fingerprint access enabled, didn't behave well when Fingerprints were removed then added back on the phone. The best workaround I found in those cases was to uninstall the app completely, fully setup Fingerprint security on the phone, then install the apps again. This definitely was the case with Amex, Chase, and Bank of America. Just something to try...good luck.
So using the OTA multiple times via fastboot wouldn't have cleared the apps?
LubbocksFall said:
So using the OTA multiple times via fastboot wouldn't have cleared the apps?
Click to expand...
Click to collapse
Sideloading or taking the OTA natively doesn't typically wipe app data in my experience. Flashing the factory image (without removing the -w) would wipe your data (and most everything else)...but that creates alot of work in setting up your phone again. I found uninstalling the troublesome apps, setting up fingerprint security/pattern, then reinstalling and setting up the apps relying on fingerprints worked the best for me - but the situations are a bit different as my troubles always were related to adding new fingerprints to the phone and apps that had the "old" fingerprint information already....for me - uninstalling / reinstalling the apps solved my issue.. YMMV
** Resolved: Please see post #9 below by @henderjr for a solution and don't forget to thank @henderjr!
--------------------------
Just downloaded DP4 and dirty flashed from DP3 (remove -w), everything looks normal....
Then I install Magisk 16.4 with TWRP (boot only), when I go back to system, System UI just crash continuously...
Also, even with 89% battery, the system still complain "battery low" (with message say the battery will last until tomorrow morning 7 o'clock, which is 19 hrs later! ha ha !)
When swipe down the notification area, the upper part of screen become dark... looks like UI glitch..
Anyone have same issue like this?
(Maybe I should factory reset, but I see somewhere that contact will not sync... So now stuck in the middle...)
Same issues here. And with random reboots also.
That's weird.
I clean flashed from Android 8 and haven't had any SystemUI issues.
I also use Substratum and haven't had any issues.
I've only been running it for a couple of hours, I'll report back if anything changes.
Edit: I'd suggest a clean flash, though. Stuff seems REALLY bugged lol.
For me started failing after a reboot. The first moment I got into the system, UI was broken
Tried factory reset also. Same problem after reboot
Same here (((
It seems we really need update of Magisk. @topjohnwu while your country need you, we also need you!
Even before flashing magsik CTS profile is false.
Sent from my Pixel 2 XL using XDA Labs
Has anyone confirmed this happens only after flashing Magisk? I'm currently trying to reproduce all the other steps (restore apps, config, etc) just to be sure who is guilty
Edit: well, I can't reproduce it. So everything seems to be pointing Magisk as the guilty
lssong99 said:
Just downloaded DP4 and dirty flashed from DP3 (remove -w), everything looks normal....
Then I install Magisk 16.4 with TWRP (boot only), when I go back to system, System UI just crash continuously...
Also, even with 89% battery, the system still complain "battery low" (with message say the battery will last until tomorrow morning 7 o'clock, which is 19 hrs later! ha ha !)
When swipe down the notification area, the upper part of screen become dark... looks like UI glitch..
Anyone have same issue like this?
(Maybe I should factory reset, but I see somewhere that contact will not sync... So now stuck in the middle...)
Click to expand...
Click to collapse
I had the same exact behavior yesterday. If you're still running the magisk module "[APP] 18. Feb ◦ Edge Sense Plus 1.22.0 ◦ Customize Active Edge on your Pixel 2 XL" it will cause SystemUI to behave strange and show the battery saver icon. Disable the module until it gets updated.
Mine was working normally on DP4, Substratum, Magisk...only had the ctsProfile false problems others are having.
Often upon flashing, especially dirty flashing any Rom, when opening Magisk it would force close. Found by just reinstalling the Magisk.apk it would work again.
But, since Google Pay is failing with the ctsprofile false problem, I've rolled back to DP3 for now and all is good.
No issues for me either. I dirty flashed and installed Magisk 16.4 and no issues at all besides the SafetyNet issue.
henderjr said:
I had the same exact behavior yesterday. If you're still running the magisk module "[APP] 18. Feb ◦ Edge Sense Plus 1.22.0 ◦ Customize Active Edge on your Pixel 2 XL" it will cause SystemUI to behave strange and show the battery saver icon. Disable the module until it gets updated.
Click to expand...
Click to collapse
It WORKS! It just WORKS! Thank you SOOOO Much!
It works for me too. Thanks!
...............
Insinuendi said:
So I booted into TWRP 3.2.2-0-taimen on DP4, still can't decrypt,. Tried using ADB sideload with Magisk 16.4 zip anyway, looks like it works. Then I try rebooting and it never starts.
Click to expand...
Click to collapse
Turn off your screen lock and you won't have to worry about TWRP not decrypting (settings > security & location > screen lock > none). Turn your screen lock back on after you've completed the flash.
xunholyx said:
Turn off your screen lock and you won't have to worry about TWRP not decrypting (settings > security & location > screen lock > none). Turn your screen lock back on after you've completed the flash.
Click to expand...
Click to collapse
I've tried both ways, same issue. Twice now I've had to flash DP4 again (without -w) because it gets stuck in a bootloop. Is there something I might be missing?
Sent from my Pixel 2 XL using Tapatalk
Insinuendi said:
I've tried both ways, same issue. Twice now I've had to flash DP4 again (without -w) because it gets stuck in a bootloop. Is there something I might be missing?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Since you flashed Magisk without decrypt data, it's highly likely that the data partition maybe damaged. Just flash-all with -w (don't remove -w) and your phone should boot... Anyway I think your data is already gone the moment you flashed Magisk without decryption...
My camera encountered a fatal error after Android Pie update but I'm still able to use Snapchat. I'm using a brand new Pixel 2 Xl and right after I updated to Pie yesterday I haven't been able to connect to my stock camera. Has anyone else been experiencing this?
Aerro47 said:
My camera encountered a fatal error after Android Pie update but I'm still able to use Snapchat. I'm using a brand new Pixel 2 Xl and right after I updated to Pie yesterday I haven't been able to connect to my stock camera. Has anyone else been experiencing this?
Click to expand...
Click to collapse
Try clearing data/cache
Then force stop
Then reboot phone
What he said in the post above. Had the same issue on DP4. It fixed it. Reboot after you clear.
I had the same issue. I didn't think about clearing the camera app cache. I flashed the factory stock 9.0 image, and the problem disappeared.
I've done all of the above I cleared cache and data with a restart I also updated OTA if that wasn't mentioned. I've also done a factory reset with Android Pie and still getting the crash prompt.
Aerro47 said:
I've done all of the above I cleared cache and data with a restart I also updated OTA if that wasn't mentioned. I've also done a factory reset with Android Pie and still getting the crash prompt.
Click to expand...
Click to collapse
Not cool
Sounds like a hardware issue now.
I have this issue also and no fix with it, it's hardware, at least on mine, I have try a couple things, wiping, deleting, flashing, restoring, even downgrade to Oreo and still freezing and rebooting when try to open the app and camera.
This start to happen when I update to September update.
I contacted Google support and the most rare question it was; What was the camera app version I have?ñ mine is 5.3 I said, so then he/she told me that is going to send me a replacement.
I am thinking that they know what this issue is and probably there's no fix for it with the software, only change the camera or whatever is the problem with the board.
Here are some screenshots: