need solusi n73 phone startup

Discussion in 'BB5' started by dwieboyke, Feb 8, 2010.

  1. dwieboyke

    dwieboyke Member

    Messages:
    24
    Likes Received:
    17
    Trophy Points:
    13
    Phone Type: RM-133 (Nokia N73)
    SW Version: V 05wk47v61.1 09-07-08 RM-133 (c) Nokia.
    Imei plain: 35640601217705-0
    Product Code: 0539299
    ApeCoreSw: V 4.0839.42.2.1 27-09-2008 RM-133
    ApeVariant: V 4.0839.42.2.1-12 27-09-2008 RM-133
    Language Pack:
    English,02 Uk

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


    Imei net: 356406012177050
    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


    please solusinya OM sekalian,aku udah tembak full pm 1-309 tapi masih tetap phone startup....:cry::cry::cry:
     
  2. HARDHIKA

    HARDHIKA New Member

    Messages:
    574
    Likes Received:
    258
    Trophy Points:
    0
    write pm dng mx key pake s4x moga behasil
     
  3. Vianik

    Vianik Well-Known Member

    Messages:
    239
    Likes Received:
    536
    Trophy Points:
    103
    jangan lupa backup,backup,backup, dulu crt sama pm nya
     
  4. wayanpdcell

    wayanpdcell New Member

    Messages:
    116
    Likes Received:
    122
    Trophy Points:
    0
    Ada 3 point penting pada sekuriti Nokia BB5 :

    1. Imei ==> nomor Identitas HP yg tentunya harus valid

    imei yg valid ==> 358997011554867 (contoh)
    imei yg tidak valid / corrupted ==> 12345610654321?

    2. Simlock Data ==> berisi data simlock yg tersimpan di area 308 pd pm

    simlock data yg valid :

    hasil read info

    SL Conf : 244-07-00000000000
    SL Prof : 0000000000000000
    SL Count: 00 00
    Provider: Nokia Test;Finland


    simlock data yg corrupted / tidak valid :
    hasil read info

    simlock corrupted

    SL Conf : FFFFFFFFFFFFFFFF
    SL Stat : FFFFFFFFFFFFFF
    SL Count: 00 00
    Provider: unknown provider

    simlock kosong

    SL Conf : 0000000000000000
    SL Stat : 0000000000000000
    SL Count: 00 00
    Provider: not found

    3. Sekuriti SX4 ==> Otoritas untuk melakukan perubahan pada area PM yg terproteksi ( field 1 & field 309 )

    hasil self test

    ST_Security_Test = Passed ==> sekuriti normal
    ST_Security_Test = Failed ==> memerlukan SX4 auth + write pm field 1 & field 309



    Nah jika salah satu saja dari ketiga point di atas ada yg corrupted / tidak valid.., maka kinerja HP tidak akan normal..., biasanya kerusakanya berupa :

    1. Contact Service
    2. Contact Retailer
    3. Sim not valid
    4. Phone Resticted
    5. Watch Dog ( WD ) ==> HP akan otomatis reset / mati setiap kurang lebih 3 menit


    Berikut troubleshooting untuk masalah di atas..,

    1. Untuk point no [1] ( imei )..., lakukan read info pd box flasher / ketik *#06# pd HP...,
    jika hasil read info :

    a. imei normal/valid ==> lanjutkan ke troubleshooting no 2
    b. imei 12345----/ tidak valid ==> Lakukan Kalkulasi RPL

    2. Untuk point no [2] ( simlock data )..., lakukan read info pd box flasher...,

    jika hasil read info :

    a. simlock data normal ==> lanjutkan ke troubleshooting no 3
    b. simlock data kosong ==> Kalkulasi RPL
    c. simlock data corrupted :
    * Repair SL zone pake BB5King,BB5Prince dsb
    * Jika reapir SL zone berhasil tp masih WD( watchdog ) ==> Kalkulasi RPL

    3. Untuk point no [3] ( sekuriti SX4 )..., Gunakan fasilitas Selftest pd box flasher..., jika hasil selftest :

    a. ST_Security_Test = Passed / normal ==> Lanjutkan ke troubleshooting no 4
    b. ST_Security_Test = Failed ==> Lakukan SX4 auth + write pm field 1 & field 309

    4. Jika dari ketiga point di atas semua normal kemungkinan masalah ada pada bagian Hardware yang diantaranya bisa diketahui dari hasil selftest...,


    Ya..., tulisan singkat di atas mudah2an bisa menjadi penerangan bagi kita tentang pemahaman Konsep Sekuriti Nokia BB5..,

    Jika ada kekurangan mohon ditambahkan..,
    Jika ada kesalahan mohon untuk dikoreksi...,


    full eris bos, coba pakae teick yg ini
     
    indricellular and frienando like this.
  5. risza408

    risza408 New Member

    Messages:
    27
    Likes Received:
    4
    Trophy Points:
    0
    master mau nanya
    kalau gini gimana solusinya
    MXKEY Serial: [FT SCR2000 0] - C0842042
    Using device: UFS_USB V2.8 (c) SarasSoft 2007.
    Driver: UFS2XX, ver: 3.6.0.0, NTMP ver: 2.6.0.0
    Module ver: 1.0.0.16662(04-05-2011), Library ver: 1.0.0.9100(23-12-2010)
    APE Data :
    SYSTEM ASIC ID: 17100708 [OMAP1710 ver: 2.0]
    ASIC MODE ID: 00
    PUBLIC ID: C58E546F878E1BEE383699AD0B1B25312DDE31E4
    ROOT KEY HASH: 49A97E826B93BA20B7ED0B082475C00500000000
    ROM ID: 1DFD66132C872FD4
    CMT Data :
    SYSTEM ASIC ID: 000000010000022600010006010C192101003000 [RAP3G ver: PA 3.0]
    EM0 ID: 00000295
    EM1 ID: 00000B22
    PUBLIC ID: 1040011540CF0154B40FAADA85EACCD6CCD88D1C
    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 Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
    FlashID0: 00EC 22E8 - 0000 6921 [Samsung K8S2815ETB,128 Mbits] type: NOR,CMT
    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 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
    CMT PAPUBKEYS HASH: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
    TransmissionMode: DDR&TX2
    SecondaryBoot: helen3_2nd.fg [BB5] version: 1.35.0 revision: 0.0 size: 0x3500
    Supported Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
    FlashID0: 00EC 00A1 - 0080 0015 [Samsung KAL00T00EM-DGYY/66,1 Gbits] type: NAND,APE
    ExtBUSC: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
    Algorithm: h3_sam_nand_xsr.fg [OMAP1710 UNISTORE-II-1.2.1 ALG] version: 1.49.0 revision: 0.0 size: 0x13AA0
    Supported Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
    APE PAPUBKEYS HASH: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
    Original Imei: 35640601264020
    Original Product code: 0539352
    Bluetooth ID: 001BEE936A5C

    Phone Type: RM-133 (Nokia N73)
    SW Version: V 05wk47v61.1 09-07-08 RM-133 (c) Nokia.
    Imei plain: 35640601264020-6
    Product Code: 0539352
    Battery voltage: 4748 mV, current: 0 mA
    Language Pack:
    - not available.

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


    Imei net: 356406012640206
    Version: SIMLOCK SERVER VERSION 63
    Counter: 0/3, 0/10

    CONFIG_DATA: FFFFFFFFFFFFFFFF
    PROFILE_BITS: FFFFFFFFFFFFFFFF

    BLOCK1: 1=CLOSED(MCCMNC), DATA=00101F
     
  6. racingzzz

    racingzzz Moderator Moderator

    Messages:
    688
    Likes Received:
    2,347
    Trophy Points:
    103
    SIMLOCK invalid!
    SUPERDONGLE_KEY seems to be valid
    CMLA_KEY seems to be valid
    SIMLOCK_TEST failed!
    SECURITY_TEST passed


    Imei net: 356406012640206
    Version: SIMLOCK SERVER VERSION 63
    Counter: 0/3, 0/10

    CONFIG_DATA: FFFFFFFFFFFFFFFF
    PROFILE_BITS: FFFFFFFFFFFFFFFF

    BLOCK1: 1=CLOSED(MCCMNC), DATA=00101F[/QUOTE]


    yg bold merah yg bermasalah.
    silahkan lakukan update SP lock lebih dulu dengan MX key.
     
    dsbc likes this.
  7. indricellular

    indricellular Active Member

    Messages:
    146
    Likes Received:
    80
    Trophy Points:
    38
    mantapp bosss, trims.
     

Share This Page