I can't see any option in settings to encrypt the phone, so is that not possible with Realme 5i/ColorOS? I would never buy a phone without that option but I assumed it was standard on all Android phones.
doveman said:
I can't see any option in settings to encrypt the phone, so is that not possible with Realme 5i/ColorOS? I would never buy a phone without that option but I assumed it was standard on all Android phones.
Click to expand...
Click to collapse
Full-device encryption was deprecated with Android 10 because it blocks Accessibility Services, the dialler & other useful things till the device is unlocked, File Based Encryption was introduced with Android 7 & is now used instead, this allows these functions to be encrypted with the device's keys (rather than the user's password) so remaining functional before the user unlocks the device.
https://source.android.com/security/encryption/
The Pixel 4a is the first phone in 10 years I didn't root because of the hardware check, but nevertheless Google Pay doesn't work for me on this phone. I had no single problem on my OnePlus 6 with Magisk. Is there a known bug? Does anybody know if usb debugging enabled is a problem for Google Pay? It's very frustrating to go back to the plastic card to pay.
Did you unlock bootloader? That'd cause it to fail the check even if not rooted.
fleischbanane said:
The Pixel 4a is the first phone in 10 years I didn't root because of the hardware check, but nevertheless Google Pay doesn't work for me on this phone. I had no single problem on my OnePlus 6 with Magisk. Is there a known bug? Does anybody know if usb debugging enabled is a problem for Google Pay? It's very frustrating to go back to the plastic card to pay.
Click to expand...
Click to collapse
USB debugging enabled kills some streaming services; wouldn't be surprised if Google Pay is sensitive to this
No, I didn't unlock the bootloader. I think this triggers the Google checks.
The only thing I did was enabling the developer options in order to give Tasker and some other apps special permissions.
I have a 4a on Android 10 with developer options enabled. I've used GPay once, and it worked ok for me.
woody1 said:
I have a 4a on Android 10 with developer options enabled. I've used GPay once, and it worked ok for me.
Click to expand...
Click to collapse
Thanks a lot, so I have to check my card. As mentioned before it worked last week on my OnePlus 6, so it's really strange.
Will try another card next time.
Not sure if it helps but sometimes I have run into an issue with using magnet mounts on the back of my phone case with pay terminals.
It's very frustrating. I tried three different cards and looked up the NFC location which is very different to my OnePlus 6. Under the fingerprint scanner instead of in the camera module. I really don't want to factory reset because I already set up all banking apps.
Thank you all for your help.
Edit: I found on Reddit, that there seems to be s a problem with Tasker, so I uninstalled it and also disabled the developer options. Will see if this works for me.
To be clear, is Google Pay telling you your device is ineligible / incompatible etc and refusing to let you set up a card? Or is the issue that it simply doesn't work at a payment terminal?
If doesn't work at the terminal. The app tells me everything is fine. I also tested the NFC chip with a German ID card. The phone can read all information stored in the ID.
Ok. That clarifies things a bit. If Google Pay isn't complaining about device eligibility then that's not what your issue is.
It's still not impossible that it's a hardware problem. Maybe it still works correctly for reading other unpowered devices like an ID card, but doesn't work for being read by payment terminals.
I'm not alone. :highfive:
The process in the video is the exact same I see every time I try it: https://9to5google.com/2020/10/26/some-pixel-5-owners-cant-make-nfc-payments-with-google-pay/
Luckily I didn't try a factory reset. :fingers-crossed:
Google Pay Not working
I have the exact same problem but this also happens on Oneplus Nord and Pixle 4a i have both devices and i get the same error on both devices .
Google pay works on
S10 Android 10
realmme 6 pro
Realme x50 5g
Fossil gen 5 Wear os Watch
pixel 3axl Android 11 beta
Will not work on
Pixel 4a Android 11
Oneplus Nord Android 10
have uninstalled the app and reinstalled
Cleared cache
Cleared storage
Cleared play services
removed account
removed card
re added card
re added account
reset device one plus nord only
none of the above methods worked for me
also i can connect my watch to the phone not working and the app on watch will work for making a contactless payment
the Nfc is working on my phone i have tested it with other NFC device and it works as intended
Called the bank No blocks on my card and it is setup correctly
Called google asked a million times the same question over and over and talking with support at the moment
so sorry i cant solve the issue but just thought id let you know what i have been doing
Also tried on different card machine get the same error all the time
Version 2.119.338332786 solved all my issues!
https://www.apkmirror.com/apk/google-inc/google-pay/google-pay-2-119-338332786-release/
I am using ArrowOS 11 on a POCO X3 NFC.
I have enabled the Multiple users option and created a second user profile, but for that one it's not possible to enroll fingerprints with the following error message after the fingerprint has successfully been scanned:
Enrolment was not completedFingerprint enrolment didn't work. Try again or use a different finger.
Click to expand...
Click to collapse
For the device owner there are already 4 fingerprints stored, but that's not the limit (I have tested this by enroling a 5th fingerprint without problems). The used finger is also not causing the issue (I have tried with a different finger).
I'm not sure if this is an Android design limitation, so that only the device owner is supposed to enrol fingerprints, or if this is a bug with ArrowOS (possibly a permission issue?), but with the fingerprint option present in the additional user profile (in contrast to the developer options for example, which can only be activated for the device owner), I assume this is rather a bug than a feature?
My intention was to install some banking apps in an additional user profile as well, so that I can manage online banking access and pushTANs for my wife and myself using only one (backup) phone, but without working fingerprint authentication in the additional user profile that endeavor is completely pointless.
P.S. Since it's unclear to me, if this is a feature or bug, I have opened an issue at the ArrowOS GitLab Tracker, if anyone is interested.
I'm having the same issue. Not only from ArrowOS (Android 12), but also CrDroid (Android 11).
Not only that, fingerprint scanning of the original account fail to work once I switch to the 2nd user. Checking the security setting, my finger print was removed from my orig account. This was what happend on CrDroid (11).
Now I'm on ArrowOS (12), the fingerprint of the 1st account is not removed, but fails to work until I reboot. Fingerprint does not work again after I switch to the other user.
I found this older thread about the POCO X3 NFC: https://forum.xda-developers.com/t/phone-says-its-encrypted-but-is-it-really.4167645/
I do not know if the info there is also valid for the X3 Pro ... or if it even was correct in the first place. (Cause just 1 other user mentioned this and no one else talked about it.)
In the 2nd post there is tha guy mentioning that MIUI is not changing the decryption keys when changing the password. Is this a problem?
I have bootloader unlocked and Magisk + LSposed installed. Using the latest stock MIUI. From what I have read online ... unlocking hte bootloader just allows to tamper more with the device - and allows an attacker to bypass the hardware security stuff to run brute force without using the phone (to bypass rate limits and run brute force very fast) - shouldn'd that still be safe with a long password?
Well Android allows at max 16 chars and I am using 16 chars letter, numbers, special chars now + biometrics for screen unlock. After the boot it seems it forces you to put in the password. (Biometrics not working.) TWRP decryption is working - and only works with the password I put. (Not with "default_password".) Even when adb is enabled (I usually leave USB debugging disabled) it seems not to work unless I also change the charging options to allow file transfer (not only charging battery) - which always seems to reset to recharging battery only after a reboot. (And not allow for changes unless passwort is put in once at least.)
I am talking mainly about attacks where you are able to power off your phone and someone else gets physical access to it. (Like police or NSA lol. After I got it back I would always completely wipe it to make sure they have not installed some keyloggers.) Unless the bootloader and internal keystore somehow (I do not have much knowledge about this) just checks your passwort but is still using "default_password" in the background (and TWRP also works using this) should not a strong password be safe?
I think the key generation with "default_password" itself still would have some random compoment (every time you reset the sytsem and it gets newly encrypted)? And it only matters if that "key encryption key" gets re-encrypted when changing the password. (And not only encrypted/hashed with "default_password".) As mentioned here by Elcomsoft: https://blog.elcomsoft.com/2018/05/demystifying-android-physical-acquisition/
"It still takes effort to decrypt the smartphone even if the data is encrypted with “default_password”. Much depends on the encryption implementation of a particular vendor. As an example, some vendors will not re-encrypt the KEK (Key Encryption Key) when the user changes their passcode; this in turn allows decrypting the data regardless of the current passcode by simply using “default_password”. The same situation occurs if, at the time of the initial setup, the vendor opts to start encrypting the phone before the user sets the passcode. According to Oxygen, this is exactly what happens on Motorola smartphones, which can be extracted and decrypted regardless of the lock screen password – but only if Secure Startup is not enabled."
(This info still seems to be for the old FDE but I think it should be similar fo file based encryption which is used in the POCO X3 Pro?)
If the TWRP only works with the correct password (otherwise showing encrypted stuff for the files that are supposed to be encrypted in th FBE - not everything like in the FDE but still enough I think) ... is it safe to say that this key encryption key is getting re-encrypted?
Hi XDA peoples. I come to you in times of great need, and to satisfy your curiosity.
Recently, my mother enabled biometrics on her discover banking app, specifically face ID. However, this enabled face unlock on the entire phone and, in doing so, set a password for the phone. Note, there was no password or any other authentication on this phone before - completely open device. Now she is completely locked out of the device due to the default security settings requiring a password every 4 hours. Remote unlock is disabled, so there is no hope of that working.
Now, my question is this: is there a password that the device would automatically apply if needed? And if so, does anybody know what it is?
Thanks.
Device is a T-mobile S21+, 8G RAM 128GB Storage.
I appreciate all help.
factory reset from recovery mode + unlock FRP with google account