GSM-Forum - View Single Post - N73 phone start_up failed contact the retaier

R@jusat · 11-04-2009, 09:55

APE Data :
SYSTEM ASIC ID: 17100708 [OMAP1710 ver: 2.0]
ASIC MODE ID: 00
PUBLIC ID: 2B45835FB40D2FDC8E4D5C909461FECF8F822463
ROOT KEY HASH: 49A97E826B93BA20B7ED0B082475C00500000000
ROM ID: 1DFD66132C872FD4
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101003000 [RAP3G ver: PA 3.0]
EM1 ID: 00000295
EM2 ID: 00000B22
PUBLIC ID: 16200105BB1D7D56C1DEB5296DC539BD223D2C93
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 273F6D55DFAAF68F
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 22E8 - 0000 6921 [Samsung K8S2815ETB,128 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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
SecondaryBoot: helen3_2nd.fg [BB5] version: 1.35.0 revision: 0.0 size: 0x3500
Supported APE 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.47.0 revision: 0.0 size: 0x13598
Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
APE PAPUBKEYS HASH: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Original Imei: 356xxxxxxxxxxxxxxxxxxx
Original Product code: 0539335
Bluetooth ID: 0023B456DDFD

Phone Type: RM-133 (Nokia N73)
SW Version: V 05wk47v53 26-10-07 RM-133 (c) Nokia.
Imei plain: 356xxxxxxxxxxxxxxxxxx
Product Code: 0529607
Language Pack:
- not available.

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

TimeStamp: 2006-07-12T17:32:12+03:00
SW Version: 2.0628.0.0.1
Variant Version: 001
ProductProfile: RM133_0529607_2.0628.0.0.1_001.spr
Simlock: simlock_3gstandard_bb5.bin

Imei: 35xxxxxxxxxxxxxxxx
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
Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[mxkey.selfip.biz] ...MXKEY-SX4 ver 2.5(CN), hello 202.56.7.172
SUPERDONGLE auth succeeded!
Writing PM from Node ...
Section: 1
- Key: 0, size 114 bytes written.
- Key: 2, size 98 bytes written.
- Key: 4, size 110 bytes written.
- Key: 6, size 98 bytes written.
- Key: 8, size 110 bytes written.
- Key: 13, size 98 bytes written.
- Key: 16, size 98 bytes written.
- Key: 18, size 98 bytes written.
- Key: 20, size 98 bytes written.
- Key: 22, size 16 bytes written.
- Key: 23, size 4 bytes written.
- Key: 24, size 84 bytes written.
- Key: 25, size 4 bytes written.
- Key: 26, size 110 bytes written.
- Key: 28, size 98 bytes written.
- Key: 29, size 6 bytes written.
- Key: 31, size 98 bytes written.
- Key: 33, size 36 bytes written.
- Key: 34, size 80 bytes written.
- Key: 44, size 182 bytes written.
Section: 309
- Key: 0, size 4 bytes written.
- Key: 1, size 2 bytes written.
- Key: 2, size 12 bytes written.
- Key: 4, size 12 bytes written.
- Key: 5, size 12 bytes written.
- Key: 7, size 12 bytes written.
- Key: 8, size 12 bytes written.
- Key: 17, size 12 bytes written.
- Key: 22, size 12 bytes written.
Completed in 0.750 s

write pm with sx4 but problem same.........

11-04-2009, 09:55	#1 (permalink)
R@jusat No Life Poster Join Date: Apr 2008 Location: IN MY PC Posts: 1,582 Member: 745721 Status: Offline Sonork: 100.1605292 Thanks Meter: 2,390	N73 phone start_up failed contact the retaier APE Data : SYSTEM ASIC ID: 17100708 [OMAP1710 ver: 2.0] ASIC MODE ID: 00 PUBLIC ID: 2B45835FB40D2FDC8E4D5C909461FECF8F822463 ROOT KEY HASH: 49A97E826B93BA20B7ED0B082475C00500000000 ROM ID: 1DFD66132C872FD4 RAP Data : SYSTEM ASIC ID: 000000010000022600010006010C192101003000 [RAP3G ver: PA 3.0] EM1 ID: 00000295 EM2 ID: 00000B22 PUBLIC ID: 16200105BB1D7D56C1DEB5296DC539BD223D2C93 ASIC MODE ID: 00 ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1 ROM ID: 273F6D55DFAAF68F 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 22E8 - 0000 6921 [Samsung K8S2815ETB,128 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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC SecondaryBoot: helen3_2nd.fg [BB5] version: 1.35.0 revision: 0.0 size: 0x3500 Supported APE 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.47.0 revision: 0.0 size: 0x13598 Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708 APE PAPUBKEYS HASH: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Original Imei: 356xxxxxxxxxxxxxxxxxxx Original Product code: 0539335 Bluetooth ID: 0023B456DDFD Phone Type: RM-133 (Nokia N73) SW Version: V 05wk47v53 26-10-07 RM-133 (c) Nokia. Imei plain: 356xxxxxxxxxxxxxxxxxx Product Code: 0529607 Language Pack: - not available. SIMLOCK seems to be valid SUPERDONGLE_KEY seems to be valid SIMLOCK_TEST passed SECURITY_TEST passed TimeStamp: 2006-07-12T17:32:12+03:00 SW Version: 2.0628.0.0.1 Variant Version: 001 ProductProfile: RM133_0529607_2.0628.0.0.1_001.spr Simlock: simlock_3gstandard_bb5.bin Imei: 35xxxxxxxxxxxxxxxx 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 Scanning local SX4 Card ... No SX4 Card found. Authenticating using security server ... Connecting to server[mxkey.selfip.biz] ...MXKEY-SX4 ver 2.5(CN), hello 202.56.7.172 SUPERDONGLE auth succeeded! Writing PM from Node ... Section: 1 - Key: 0, size 114 bytes written. - Key: 2, size 98 bytes written. - Key: 4, size 110 bytes written. - Key: 6, size 98 bytes written. - Key: 8, size 110 bytes written. - Key: 13, size 98 bytes written. - Key: 16, size 98 bytes written. - Key: 18, size 98 bytes written. - Key: 20, size 98 bytes written. - Key: 22, size 16 bytes written. - Key: 23, size 4 bytes written. - Key: 24, size 84 bytes written. - Key: 25, size 4 bytes written. - Key: 26, size 110 bytes written. - Key: 28, size 98 bytes written. - Key: 29, size 6 bytes written. - Key: 31, size 98 bytes written. - Key: 33, size 36 bytes written. - Key: 34, size 80 bytes written. - Key: 44, size 182 bytes written. Section: 309 - Key: 0, size 4 bytes written. - Key: 1, size 2 bytes written. - Key: 2, size 12 bytes written. - Key: 4, size 12 bytes written. - Key: 5, size 12 bytes written. - Key: 7, size 12 bytes written. - Key: 8, size 12 bytes written. - Key: 17, size 12 bytes written. - Key: 22, size 12 bytes written. Completed in 0.750 s write pm with sx4 but problem same.........