-
-
Notifications
You must be signed in to change notification settings - Fork 900
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not read tag [Pixel 8/8 Pro] #441
Comments
Hi! Thanks for reporting. I have no idea what could cause this. Unfortunately, I do not have a Pixel 8 Pro laying around to recreate the issue. I will try to reach out to some people who may have a Pixel 8 (Pro). Of course, if you are familiar with Android debugging you can try it your self. |
Anything special with this tag? Does it have default keys? Did you try other apps (e.g. NFC TagInfo by NXP, full scan)? |
I don't know android debug, but I'll try to experiment. I inserted all the keys. |
Hi! I also have a Pixel 8 Pro and I confirm that I cannot interact with a tag that I have always used on any other phone. The association with the keys is not recognized |
Hi ! |
Does any of you have a factory formatted (empty) MIFARE Classic tag? I would be interested to know if an app like NFC TagInfo by NXP can read it (using the "full scan" feature/tab). |
Same here, does not work on pixel 8 pro. Also had this working perfectly fine on Pixel 6 pro. |
Damn. I thought we might be one step closer. But if it can be read by either application, I don't know for sure that the bug is in MCT. It could be somewhere in Android or drivers of a Google Pixel 8 Pro. |
Does this testing version make any difference? |
For me, nothing new, the problem remains |
Thanks for testing. Other idea: Could you try the "Retry authentication" option and set it so something like 5? |
Unfortunately it doesn't work anyway |
Fyi same thing with pixel 8. |
Just update my Pixel 8 to latest OTA from november 2023 : shiba-ota-ud1a.231105.004-49029a3a.zip changelog HERE NFC
|
Thanks @imfloflo! This is great news. So it was a ROM/driver issue after all (which makes a ton of sense). I hope this update will roll out fast. I will close this issue for now. Feel free to to open another issue if there issues with the app itself. |
I updated my Pixel 8 Pro to the same version (UD1A.231105.004) but I still have the same problem... |
I feel like the NFC chip is quite sensitive. Some badges are read, others are not. And those that are read don't work all the time. The only one I need to read every day I can't read it. |
@CleverManDev But what are the correct keys? Do you know them? Do you know that they are in the file(s)? |
Google Pixel 7 Pro reads this tags without problems. |
Any ideas with this problem? |
I have the same symptoms with a Pixel 8 (non-pro). The phone has the latest update from January.. |
Hi. Sorry, still not idea what can cause this. I really need to get my hands on a Google Pixel 8... |
Maybe we can help you with some log files? I have root privileges on my Pixel 8 Pro if it can help. |
I believe it could be a problem on Android-level, since other apps like nfcTags and my custom app are also not able to read a Mifare card and show similar symptoms as described here on my Pixel 8. They worked before on my Pixel 5. |
Opened the dump from Pixel 7 Pro, saved keys and read std.keys and extended-std.keys. Dump attached: |
I've just bought an Pixel 8. I can confirm. It can not read a genuine MIFARE Classic EV 1 card (with valid originality signature by NXP). It does not work on MCT, NXP TagInfo and NFC tools. A quick debug shows: the error seems to be within Android. Using the MifareClassic.authenticateSectorWithKeyA(...) function from the Android API returns |
I've tried to contact the Pixel 8 customer service, because someone said the general Android bug tracker is not for device specific issues. Let's see how this goes. Not sure why it works for @imfloflo. Sure, there might be different Android versions depending on regions. But e.g. different NFC drivers for the same device... odd. Not sure if |
I also posted on the pixel forum just now to see if anyone has an idea or if Google sees the message... |
I am using the custom ROM GrapheneOS and even I have this issue.. |
I get a "This page is no longer available" for this link. @alexg-k: Tanks for the feedback. This makes it look more like a NFC driver/firmware issue I've also installed the |
@ikarus23 |
@ikarus23 I just try again with my P8 on latest version to read a NFC Aztec badge. |
EDIT: Turned out this is not the solution. Good news: I'm now able to read MIFARE Classic tags with my Pixel 8! Let's try to recreate it. Here is what I did:
Some things that would be interesting:
|
By now I've locked down my bootloader again, reverted everything to stock, did a full factory reset, aaaaaand it still works! I guess, yay?! ¯_(ツ)_/¯ |
Great progress ! |
I did all the operation step by step with a restart and a reading test between each step and it still does not work for me once everything is activated. on the other hand, have you tried with a badge that has default keys? because if all the blocks have a default key it works. but does not work if at least one of the keys is not in the default key. |
Uff, yes, I only tested against a card with default keys. I tired different dumps and tags and my results got even worse.
Are there only issues with MIFARE Classic EV1 tags? |
I can confirm that the symptoms persist after the developer options are enabled on my custom rom. |
Hi, I confirm that even by activating NFC debugging I cannot read the tag. |
Hi, just wanted to add my 2 cents to the debugging effort: I run the latest stable Graphene OS on a Pixel 8. Example of a tag that is read just fine: Example of a tag that fails to be read (despite correct keys, tested to work on another phone): Note that Metrodroid also seems to be affected by this inability to read. Also tried enabling the three NFC debug options as per this comment but didn't do me any good. |
@Holbormon Thanks. Unfortunately MCT's tag detection is not the best. NXP's TagInfo is way better (https://play.google.com/store/apps/details?id=com.nxp.taginfolite). It might be giving you information about the chip used in the tag. So far, MIFARE Classic EV1 chips seem to be the main issue. (But their could be more.) |
@ikarus23 Using that other app I can confirm that the affected tag is indeed a Mifare Classic MF1S50 (a.k.a EV1). Aside from mentioning that my chinese Mifare Classic 1K keyfobs are working just fine, there's not much else I can say. Hope we crack this case soon 💪 |
@ikarus23 here are more details on the issue: The call to I enabled NFC stack debug log and NFC NCI unfiltered log in the developer options. It gives the following log lines when the tag is discovered:
Which corresponds to the file Note that the NXP TagInfo App [4] also fail to read the tag. Also, the following error log is triggered for every call to
Happening in My conclusion is: unless there is a way to fix it by providing custom parameters to the NFC interface, it has to be fixed in the Android codebase. [1] https://android.googlesource.com/platform/frameworks/base/+/refs/heads/android14-release/core/java/android/nfc/tech/BasicTagTechnology.java#149 |
Wow, thanks for the research! I tried to reach out the Pixel support. So far, they were not very helpful. I referenced this issue multiple times and did send them the logs files. Communication came to a halt and after the last update the just asked: "is it fixed now?". Not sure how to continue from here... |
Tested on android 15 beta2, and still the same faulty behavior on pxiel 8 pro :( And this morning with the beta 3.1, build AP31.240517.031 and also still not working |
tested with today release of the newest android 15 beta, and now it works : AP31.240617.009 |
Sorry for the late response. I was/am on holidays. Thins sounds like great news! Unfortunately I only have one Pixel 8 as my personal daily driver. I'm not willing to switch over to beta with that. I guess we have to find another person or wait for the release |
EDITED/REMOVED: This seems to have been an error somewhere else. A MF1S50 card failed to read with my pm3 (on Linux) after trying MFC (on Pixel 8 Pro). I tried the NXP taginfo app, and that ID'd the card again, and after that it worked with my proxmark. I suppose there is some issue with the proxmark, since other cards seem to have problems now as well. This was probably just a coincidence. Sorry if I scared anyone! (You can check my original message by clicking the "edited" button above - you want the one at the bottom of the list) |
HI @archi. I guess your issue is off topic from this issue, but it looked like you have an issue with the BCC ( |
Phone: Google Pixel 8 Pro
App version 4.1.0
Display Tag Info works well.
Start Mapping and Read Tag doesn't work.
Output:
New tag found (UID:XXXXX)
7 keys loaded. Creating key map This might take a while
No valid key found in chosen key file
Same Tag and same key file in another phone (Pixel 6 pro with Android 14) work.
Thank you!
The text was updated successfully, but these errors were encountered: