5300 conser

Discussion in 'BB5' started by cemete, Dec 12, 2009.

  1. cemete

    cemete New Member

    Messages:
    6
    Likes Received:
    1
    Trophy Points:
    0
    tolng para master 5300 conser...dah aku pake unlock pake zulea masih tetap konser....
    [​IMG]Using device: UFS_USB V2.8 (c) SarasSoft 2007.
    RAP Data :
    SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
    EM1 ID: 00000232
    EM2 ID: 00000353
    PUBLIC ID: 2DA00007653D6F56C989F263394A61A7B624D9B7
    ASIC MODE ID: 00
    ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
    ROM ID: 191EC665DFAAF68F
    SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 9.11.1 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 2208 - 0000 6921 [Samsung K8F5615ETM,256 Mbits] type: NOR,RAP
    ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
    ExtDEVC: FFFF 0000 - 0000 0000
    Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 9.17.0 revision: 0.0 size: 0x22E90
    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: 7C1A1F5C3DB717937F54455937AF9DA76AA2EE13
    Original Imei: 35309502153854
    Original Product code: 0551188
    Bluetooth ID: 001F5D75C456

    Phone Type: RM-146 (Nokia 5300)
    SW Version: V 07.20 23-10-08 RM-146 (c) Nokia.
    Imei plain: 35309502153854-4
    Product Code: 0532162
    Language Pack:
    - not available.

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

    TimeStamp: 2006-09-18T13:30:17Z
    SW Version: V 03.50
    Variant Version: 004
    ProductProfile: RM146_0532162_03.50_004.spr
    Simlock: 0532162_simlock.bin

    Imei: 353095021538544
    Version: SIMLOCK SERVER VERSION 63
    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
     
  2. gerhana

    gerhana New Member

    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    0


    coba sx4 tembak pm...kalau masih tetap
    ym saya bos..........
     
  3. Setia_One

    Setia_One Jalmi Alit tea Super Moderator

    Messages:
    2,149
    Likes Received:
    11,232
    Trophy Points:
    123
    Yups setuju,masalah pm : SECURITY_TEST failed!
    klo pake mxkey bisa tuh sbb SUPERDONGLE_KEY seems to be valid


    coba masuk di tab service>PM,lalu klik PMM auth ,lalu write full pm yg ok,terus full factory,terus bikin nota deh
     
    alirosidialirosidi likes this.

Share This Page