No valid key found in chosen key file #129
Comments
|
In addition even if I'm using same sets of key file, mapping process now takes longer compare on the time when the message 'No valid key found in chosen key file' is not appearing. |
|
As far as I remember, the keys I used for A and B is 000000000000 |
|
Hi, Maybe this has something to do with #66. However, I was never able to reproduce this behavior. What device are you using? Do you have access to another device to verify that behavior? |
|
Yes, after increment function. But the weird thing is, before it happened, I can use increment/decrement function on the same sector/block without having any problem; and during that time key A & B is FFFFFFFFFFFF, the problem arises when key A and B becomes 000000000000. I'm using xperia XA ultra, android Marshmallow, no firmware upgrade made, the version of the app that I'm using is the latest in playstore as of this writing (2.1.0) |
|
adb logcat might show something useful
|
|
Here's adb log on my device while doing 'READ TAG' function that generates same error message 'No valid key found in chosen key file': The keys in my key file are: which are used before the issue occur. |
|
All the things you are describing really sounds like #66. You have a Xperia too. I thing this issues is a result of bug with Xperia devices. @alfs said
|
|
It looks like this is nothing new: https://forum.xda-developers.com/xperia-z2-tablet/help/mifare-classic-support-z2-t2874883 |
|
It would be really interesting to see if this issue is fixed in CyanogenMod / LinageOS >= 13.x. @ArchangeGabriel reported in #127 that CM fixes the Mifare Classic compatibility issues on the OnePlus One. Maybe it's the same here. |
Closed
|
Same problem on Nexus 6P😂 |
|
Clone card, read&write successfully. Then, can not access the card and same notification like Mark said. |
|
So not exactly the same problem. @mark-monserrat is expecting issues after using the increment/decrement function. Sorry to ask you that: you are sure the keys of the tag you just wrote are in one of the key files you selected, right? Also, there are issues with Mifare Classic and the Nexus 5X. Maybe the 6P has issues as well?! Furthermore, were (some of) the keys of the tag "000000000000"? |
|
@mark-monserrat as I can catch from the log You have broadcom (not nxp) nfc chip compatibility for which has not been confirmed probably. |
|
@osysltd good catch! So the Sony Xperia XA Ultra has a Broadcom chip?. Unfortunately I was not able to confirm this by a quick google search. |
|
Original card 3FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 00455622000413180516000000000000 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 00000000000000000000000000000000 |
|
Interesting. So it seems this is connected to #66... |
Is there anyone with such a device an CM / LinageOS who can test this? But maybe it is just based on the same consistency issue I have with my Nexus 5X (#106). And it looks like Google is responsible for this. |
|
Yes, CyanogenMod fixed the NFC issues with the OPO a long time ago, this app works perfectly fine on mine. (using sultanxda's lineage 14.1 ROM-9 |
|
So it looks like this is an Android issue. I don't think there is anything I can do. Closing this issue until proven otherwise ;). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The app works fine at first, I can read/write data on d card. Then all of a sudden when I tried to increment sector 1 block 0, a toast appear saying No valid key found in chosen key file'. I'm sure I have the right keys. From then on I can't access the card anymore. It keeps showing 'No valid key found in chosen key file'.
The text was updated successfully, but these errors were encountered: