I only know for Nokia phones (symbian):
http://84productions.blogspot.com/2008/ … nokia.html
http://www.securityfocus.com/archive/1/468652/30/
If sms are stored in your SIM card, it´s possible to do it with this tool:
http://vidstrom.net/stools/undeletesms/
You´ll need a SIM smartcard reader for connecting it to your pc.
Regards.
]]>if (!nfc_initiator_transceive_bits(r.pdi, AuthEnc, 32, AuthEncPar,Rx, &RxLen, RxPar)) {, there is no communication with the reader while
for (m = d->median-d->tolerance; m <= d->median+d->tolerance; m +=2) { is running. This also explains why setting the "distance" option (-T) low helps mfoc to continue (See remarks at http://www.libnfc.org/community/topic/2 … ng-mfoc/).
I don't know what causes this, and why some ACR122's are affected and some (notably: yours) are not; but putting the
nfc_configure(pdi,NDO_HANDLE_CRC,true);
nfc_configure(pdi,NDO_HANDLE_PARITY,true);code inside mf_enhanced_auth() did the trick. Some of the folks at http://www.ov-chipkaart.org/?page_id=24 already tested this and so far, it seems to work well (it does for me).
The patch so far is rather intrusive, as I removed all calls to mf_configure, to replace these with individual nfc_configure() calls. This doesn't always work out well: sometimes, resetting the CRC or parity-handling at the end of mf_enhanced_auth still fails - and will stop mfoc. Also, my current mfoc.c code is a mess, with out-commented printf() and sleep() calls all over the place.
As a stop gap, for those that do have the problem, there's a link to the hacked up source code at my blog (I won't repeat it here, see above links). I'll fix the minor issues in a few days, clean up the source; then I'll file a proper bug and put a (proper, cleaned up) patch in the issue tracker.
So I started hacking around in MFOC and was able to filter out most of the problems.
Nice, what was the problem ?
So I have only two questions: are there any volunteers with crashing ACR122U207 readers out there?
I have some ACR122U102 and one ACR122U206, I can test... BTW, I don't have these problems before.
And where should I send the source?
You can create an issue on the issue tracker and submit your patch(es) or you can directly send it to me.
]]>So I have only two questions: are there any volunteers with crashing ACR122U207 readers out there? And where should I send the source?
Volunteers with non-crashing ACR122U207 readers are most welcome, too, because I would hate to see their readers crash now.
]]>configure:3760: $PKG_CONFIG --exists --print-errors "libnfc >= $LIBNFC_REQUIRED_VERSION"
Package libnfc was not found in the pkg-config search path.
Perhaps you should add the directory containing `libnfc.pc'
to the PKG_CONFIG_PATH environment variable
so please read:
man 1 pkg-configand you will see that works with something like:
PKG_CONFIG_PATH=/additionnal/path/ ./configure --your-optionsEDIT:
configure:3760: $PKG_CONFIG --exists --print-errors "libnfc >= $LIBNFC_REQUIRED_VERSION"
Package libnfc was not found in the pkg-config search path.
Perhaps you should add the directory containing `libnfc.pc'
to the PKG_CONFIG_PATH environment variable
I 've two libnfc.pc files:
* /usr/local/lib/pkgconfig/libnfc.pc
* /usr/local/lib64/pkgconfig/libnfc.pc
configure: error: libnfc >= 1.4.0 is mandatory.
Ideas?
]]>btw, could you solve to problem?
After some research, "Invalid Parameter" was not a correct error string. Since r825, its fixed and now you will have "Invalid Received Frame".
See http://code.google.com/p/libnfc/issues/detail?id=132
So, the libnfc is fixed now maybe we could enhance a bit nfc-mfclassic to handle the case..
]]>btw, could you solve to problem? i've been busy these days and didn't have the opportunity to check it out. also i checked out the code but couldn't find any problems.
]]>Using Mifare Classic, even if an Auth command pass (without errors), Read cmd can fail with "Invalid Params" if the key you are using don't allow you to read the block you ask.
So, mfoc and nfc-mfclassic have to be fixed in order to workaround this "bug".
first off, I thought it was a mfoc problem because it showed me the same error messages. but when I tried mfcuk and it gave me no errors.
I am beginning to think it must be a libnfc problem. or is it a driver problem?
I goes deeper in this problem and that error comes from the chip.
So, there is a bug... reported by the NFC chip, in "special" conditions... I'll report as soon as I found the problem source.
Connected to NFC reader: ACS ACR122U 00 00 / ACR122U102 - PN532 v1.4 (0x07)
Found MIFARE Classic 4k card with UID: cff21c44
Reading out 256 blocks |..................nfc_initiator_transceive_bytes: Invalid Parameter
!
Error: unable to read block 0x56first off, I thought it was a mfoc problem because it showed me the same error messages. but when I tried mfcuk and it gave me no errors.
I am beginning to think it must be a libnfc problem. or is it a driver problem?