NFC Miflare Classic 1K full emulation not working? #1862
Comments
netdoggy
changed the title
|
Is this a bug or I have a hw problem, can someone check? |
|
There are some hardware limitations: we do emulation in software and some readers behave not as we expect. @gornekich and @Astrrra will help you |
|
My reader is just nfc Samsung Galaxy S20+ and HTC U11
I was looking for information on how to correctly create debug.pcap in flipper zero and could not find it. |
|
I logged into cli Is there anything else I can do? |
|
Hello @netdoggy
There is not good way to log information with flipper and be sure that it will not affect emulation timings. The best option would be to sniff communication between flipper and phone with proxmark or hydranfc |
|
@gornekich In theory, the phone in this mode, as far as I understand, reads only id and "flags" ? To be honest, I don’t quite understand why it even writes about keyA block 3
I have only ACR122U in my arsenal, and I have not yet tried to read the emulated label.
Upd: On successful reading of emulation via ACR122U + mfclassic.exe, the following log appears And I still would like to understand, everyone has such a problem with reading mifare classic emulation through android nfc reader. Or is it just me. I tested on phones of completely different generations. |
Just curious, in the absence of these two devices, can a second flipper, or an android phone, be used to sniff communication between a flipper and a reader, to collect a useful pcap file that could help identify issues with MFC emulation? |
|
@gornekich What else can i do to help? |
|
Here, for comparison, a real tag was read, from an android phone, without errors. The same tag, read and stimulated by the flipper, and traced through proxmark. |
|
Hi @netdoggy. I have the same issue. Have two readers - acr122u and asus zenfone 5. |
|
I have the same problem under Mitfahre Classic 1k. with me also shows in debug mode that he tries to read only the block 3 on the reader. Have written the data with the acr122u on another and lo and behold the card works. Do you have approaches here or can you support? |
I need to get myself a ProxMark! Log from FZ when card is read: |
3 tasks
|
@giacomoferretti @AloneLiberty Hello. I checked the reader in the Samsung Galaxy S22+ and it began to read the tag. She didn't react before. I also checked the intercom that had not previously seen emulation, and it also, albeit with a lag, began to work. So yes, probably this improvement greatly improved the performance of the emulator. |
|
Seems to be working now! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug.
Please tell me, should Miflare Classic 1K be emulated with a flipper completely or only UID?
If I take the saved Miflare Classic 1K file (from the intercom), together with the keys in the sectors, and click emulate, my android does not react to it in any way. At the same time, it perfectly reads the original chip.
The intercom is also not working by Flipper but it is trying to read sector 0 with the key.
Upd:
It seems that according to the documentation MIFARE Classic 1K and 4K has full support.
I tried running the emulation via NFC->Add Manually -> Mifare Classic 1-4k* and none of the "Mifacre classic" emulation seems to work with scanning from an android phone,
but some others seem to work like Mf Ultralight.
I thought maybe this is a hardware problem, but it looks like it's still software?
Reproduction
NFC->Add Manually -> Mifare Classic 1-4k* and check by android mobile phone
Target
dev-3fd30a91
Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: