×

Discussion Board

Results 1 to 3 of 3
  1. #1
    Registered User
    Join Date
    Jul 2008
    Posts
    3

    Locking of SE in 6131 & 6212

    Dear experts

    For the last months I've been developing a midlet using se JCOP part of the secure element in the 6131. It’s been working perfectly until recently I suddenly got the “Problem with the secure element. Contact service provider” when I try to communicate with the reader (Cardman 5321). As I thought it was a failure with the phone I bought a new 6212, and after a while the same thing occurred with that one as well. The only thing I can imagine is that we’ve being doing some work with standard Mifare cards on the same reader (including changing the auth. keys). Could this have provoked the locking of the SE? Is there any way to work around the locking? If not, is it possible to change the SE in the phones?

    Best regards

  2. #2
    Registered User
    Join Date
    Jul 2008
    Posts
    3

    Re: Locking of SE in 6131 & 6212

    Does anybody know under what circumstances, apart from authenticating more that 10 times in a row with wrong keys (which is not the case), the SE in these devices locks.
    This lock does not allow any communication with the chip. Putting it in the reader the “Card failure. Contact service provider” message pops up. The reader will not detect that a card is present. None of the default application IDs:
    • D276000005AB0503E0040101
    • A0000000035350
    • D276000005AA040360010410
    • D276000005AA0503E00401
    were deleted.
    Could it for example be a bug in the Smartcafé that trigger the lock? I know the memory usage for my JavaCard app. was very near the limit, and maybe exceeded…

  3. #3
    Registered User
    Join Date
    Aug 2008
    Posts
    19

    Re: Locking of SE in 6131 & 6212

    Quote Originally Posted by pontus@telefonica.net View Post
    Dear experts

    For the last months I've been developing a midlet using se JCOP part of the secure element in the 6131. It’s been working perfectly until recently I suddenly got the “Problem with the secure element. Contact service provider” when I try to communicate with the reader (Cardman 5321). As I thought it was a failure with the phone I bought a new 6212, and after a while the same thing occurred with that one as well. The only thing I can imagine is that we’ve being doing some work with standard Mifare cards on the same reader (including changing the auth. keys). Could this have provoked the locking of the SE? Is there any way to work around the locking? If not, is it possible to change the SE in the phones?

    Best regards
    Hi,

    I have been struggeling with JCOP developpement
    no matter i use netbeans or eclipse, with any version of JCDK from sun, the mobile phone (6212) refuses to let me put my soft in it (I unlocked the device before)

    can you tell me what software do you sue?
    wich versions, did you manage to find the JCOP tools ?
    please help me out

    thx

Similar Threads

  1. Video recording length on 6131 & 6212
    By zlion in forum Streaming and Video
    Replies: 0
    Last Post: 2009-02-03, 01:40
  2. Tag emulation on 6131 or 6212
    By studioj in forum Near Field Communication
    Replies: 4
    Last Post: 2009-01-28, 15:27
  3. Any difference in NFC between 6131 and 6212
    By pclerimus1 in forum Near Field Communication
    Replies: 0
    Last Post: 2008-12-06, 18:15
  4. P2P (6131 vs 6212)
    By T5R in forum Near Field Communication
    Replies: 0
    Last Post: 2008-11-25, 16:09
  5. Nokia 6131 NFC SDK v. 1.1 has been released!
    By Raluca_ in forum Near Field Communication
    Replies: 8
    Last Post: 2008-05-29, 13:54

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×