Mengatasi security tes failed 5310

Discussion in 'BB5' started by ongko, Jun 17, 2010.

  1. ongko

    ongko Active Member

    Messages:
    157
    Likes Received:
    36
    Trophy Points:
    38
    Using device: UFS_USB V2.8 (c) SarasSoft 2007.
    Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)
    RAP Data :
    SYSTEM ASIC ID: 000000010000022600010006010C192101013000
    EM0 ID: 00000295
    EM1 ID: 00000B22
    PUBLIC ID: 13700215F966025464916C2628C0F794743F5A4D
    ASIC MODE ID: 00
    ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
    ROM ID: 273F6D55DFAAF68F
    SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
    Supported RAP Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
    FlashID0: 00EC 220C - 0000 8921 [Samsung K8F1215ETM,512 Mbits] type: NOR,RAP
    ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
    TransmissionMode: 16Bit
    Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 1.40.0 revision: 0.0 size: 0x22C10
    Supported RAP Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
    RAP PAPUBKEYS HASH: 3E96DE4212587183E5E16BB2C79692A53C19875D
    Original Imei: 35865301912981
    Original Product code: 0548082
    Bluetooth ID: 001D987F5926

    Phone Type: RM-303 (Nokia 5310 XpressMusic)
    SW Version: V 09.42 07-11-08 RM-303 (c) Nokia
    Imei plain: 35865301912981-0
    Product Code: 0548082
    Language Pack:
    - not available.

    SIMLOCK seems to be valid
    SUPERDONGLE_KEY seems to be valid
    WMDRM_PD seems to be valid
    SIMLOCK_TEST passed
    SECURITY_TEST failed!


    Imei net: 358653019129810
    Version: SIMLOCK SERVER
    Provider: Nokia Test, Country: Finland
    Counter: 0/3, 0/10

    CONFIG_DATA: 2440700000000000
    PROFILE_BITS: 0000000000000000

    BLOCK 1: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
    BLOCK 2: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
    BLOCK 3: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
    BLOCK 4: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
    BLOCK 5: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
    BLOCK 6: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
    BLOCK 7: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
    SERVER->Served by MXKEY - BLADE X at host2, agent version 1.1 revision 0.1

    Scanning local SX4 Card ...
    No SX4 Card found.
    Authenticating using security server ...
    Connecting to server[main.mxkey.biz] ...MXKEY SX4CARD - ID, hello 202.70.58.2
    Bad phones ack, probably SUPERDONGLE_KEY corrupted !
    Wrong response to SD verify request







    trus gimana nih solusinya........?
     
  2. boelda

    boelda Moderator Moderator

    Messages:
    942
    Likes Received:
    566
    Trophy Points:
    103
    sama ni bro kasusnya, kalo menurut ane tu server yang lagi error

    Using device: UFS_USB V2.8 (c) SarasSoft 2007.
    Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)

    Product: V 07.20 23-10-08 RM-146 (c) Nokia.

    Using cached productData[1080020BE6246F567BFF59FC087C501A1EECABB8] ...

    Authenticating to SUPERDONGLE using security server ...
    Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted !
    Wrong response to SD verify request


    tapi entahlah......... nunggu masukan rekan2 yang lebih tau dulu.
     
  3. sagala63

    sagala63 Moderator Moderator

    Messages:
    978
    Likes Received:
    1,598
    Trophy Points:
    103
    Mengenai kasus macam tu...kayaknya bisa di repair dengan mx update tan terbaru (3.4 R1.1), tadi sore 5200 kita superdongle key corrupted, macam kasus bos diatas, yg selalu muncul log :

    Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted !
    Wrong response to SD verify request.


    pada waktu mau di super SD auth dan Pmm auth.............?

    Tetapi dgn mx update tan terbaru ini Al hamdulillah berhasil direpair dan buat nota ..... deh:D:D:D coba aja, tapi jangan terkeco dgn lognya ya....soalnya agak beda update terbaru ini.



    Salam dr Siantar Man
     
    radhitya82 likes this.
  4. boelda

    boelda Moderator Moderator

    Messages:
    942
    Likes Received:
    566
    Trophy Points:
    103
    sudah nyari sana-sini kok ketemu yang rev 1.1 pak bos ?

    paling baru rev 1.0 kalo bisa di upload ya pak ???????

    dah pasti laris
    :D
     
  5. sagala63

    sagala63 Moderator Moderator

    Messages:
    978
    Likes Received:
    1,598
    Trophy Points:
    103

    Berhubung inet kita kagak kuat untuk upload, kita upload linknya aja ya gan........mudah2han langsung ketemu dan jangan lupa linknya khusus MX update ini disimpan agar kita bisa langsung cek update terbaru mx.


    RapidShare: 1-CLICK Web hosting - Easy Filehosting


    Salam dr Siantar Man
     

Share This Page