MifareClassicTool
MifareClassicTool copied to clipboard
ikarus23
Can not read tag [Pixel 8/8 Pro]
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!
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 tried the other recommended application, but the behavior is strange. See image: https://i.imgur.com/PwTlcN8.png first line pixel 6 second line pixel 8
I inserted all the keys. I obtained the keys with the milazy, mfoc, mfcuk tools. I confirm that the keys work because with the pixel 6 I read and write correctly.
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 ! I have the exact same problem on Pixel 8 Pro. Try on several badges, none work...
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.
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).
Hi, a blank badge seems to be read from the application you mentioned.
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).
But this same badge also seems to be read from MCT
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.
Thanks for testing.
Other idea: Could you try the "Retry authentication" option and set it so something like 5?
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. Pixel 5 read the tag and find the keys. Try to import Key files and read it from pixel8 nothing work.
Just update my Pixel 8 to latest OTA from november 2023 : shiba-ota-ud1a.231105.004-49029a3a.zip MCT no works great with tag 😃
changelog HERE
NFC
Fix for issue occasionally causing NFC and related services to have instability in certain conditions
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. I also did update UD1A.231105.004, before this update I could only read blank badges. It's a shame for this type of phone....
The problem not gone with the latest updates for Pixel 8 Pro.
I'm trying read tag but get message "no valid key found in choosen key file". The problem was on the november patch and now this problen on the latest december patch.
Yes, I tried extended key, it reading about 30 min. and the same message at end.
@CleverManDev But what are the correct keys? Do you know them? Do you know that they are in the file(s)?
@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. The result of reading attached to this post (in zip). UID_34B22531D78436_2023-12-11_12-39-56.zip
I have the same symptoms with a Pixel 8 (non-pro). The phone has the latest update from January.. This app and one I developed myself to read Mifare Classic cards worked on my Pixel 5, but stopped working on the Pixel 8 using the same cards.
Hi. Sorry, still not idea what can cause this. I really need to get my hands on a Google Pixel 8...
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.
Hi @CleverManDev. As a first try you could open the dump in the editor, then press on the menu an select "Save Keys". After this, go back to reading the tag and only select the new key file.
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.
Hi @CleverManDev. As a first try you could open the dump in the editor, then press on the menu an select "Save Keys". After this, go back to reading the tag and only select the new key file.
Opened the dump from Pixel 7 Pro, saved keys and read std.keys and extended-std.keys.
Dump attached: UID_34B22531D78436_2024-02-06_15-06-59.zip
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 false even if the key is correct.