N91-8gb phone start-up failed

[lokolok1]

Всем привет!!! Пришла N91-8gb с phone start-up failed, при скане mx-key имей в норме все пассед кроме Sec Test failed, pm какие только строки непроливал через sx, какиеток анлоки неделал непомогает, стирал подчастую потом новой прошивкой прошивал, rpl бекапенный заливал, серты заливал, в конец RPL заказал и вот что имею:

Лог

Imei: 35276501062337
Updating SIMLOCK...OK
Updating SUPERDONGLE_KEY ...OK
Updating CMLA_KEY...OK
APE Data :
SYSTEM ASIC ID: 17100708 [OMAP1710 ver: 2.0]
ASIC MODE ID: 00
PUBLIC ID: 7523ADDF5379000DBC07A7FE3D84028FFAF0CC77
ROOT KEY HASH: 49A97E826B93BA20B7ED0B082475C00500000000
ROM ID: 1DFD66132C872FD4
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006000C192101002200 [RAP3G ver: PA 2.2]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 14100006145E5A5136DB4DCE4E5D2A2D2379F647
ASIC MODE ID: 00
ROOT KEY HASH: E9EFF4BFAA5393217CA6B17755FC3E14
ROM ID: F28A211FCEA7B19D
SecondaryBoot: rap3gv2_2nd.fg [BB5] version: 1.21.0 revision: 0.0 size: 0x3D00
Supported Ids: 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200
FlashID0: 00EC 2250 - 0000 0121 [Samsung K8S6415ETB,64 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: 6E25F5B4407C1CBD0598994502C24000F3657C18
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 0036 - 00A5 00C0 [Samsung KAL00R00EM-DGXX,512 Mbits] type: NAND,APE
ALG [35]: OMAP1710 UNISTORE-II-1.2.1 ALG
ExtBUSC: 0002 0000 0006 0000 0000 0000 0000 0000
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: 6E25F5B4407C1CBD0598994502C24000F3657C18
Updating CMT NPC ...OK
Updating CMT VARIANT ...failed, Result: 0230000000717200

Phone Type: RM-43 (Nokia N91-2)
SW Version: V w33_07w11v1 14-03-07 RM-43 (c) Nokia.
Imei plain: 35276501062337-1
Product Code: 0538601
Battery voltage: 4699 mV, current: 23 mA
Language Pack:
- not available.

SIMLOCK seems to be valid
SUPERDONGLE_KEY[MX] seems to be valid
CMLA_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!


Imei net: 352765010623371
Version: SIMLOCK SERVER VERSION 62
Counter: 0/3, 0/10

CONFIG_DATA: 2440700000000000
PROFILE_BITS: 0000000000000000

BLOCK1: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK2: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK3: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK4: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK5: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK6: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK7: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN

Помогите мужики, клиент гавнистый как на зло попался.

[UO5OQ]

RPL записался полностью?
Покажите лог записи RPL
И сразу же запишите PM 1 и 309 поля поля с SX4 Авторизацией и покажите лог записи PM тоже.

[lokolok1]

Как просили RPL

Лог записи RPL

Imei: 35276501062337
Updating SIMLOCK...OK
Updating SUPERDONGLE_KEY ...OK
Updating CMLA_KEY...OK
APE Data :
SYSTEM ASIC ID: 17100708 [OMAP1710 ver: 2.0]
ASIC MODE ID: 00
PUBLIC ID: 7523ADDF5379000DBC07A7FE3D84028FFAF0CC77
ROOT KEY HASH: 49A97E826B93BA20B7ED0B082475C00500000000
ROM ID: 1DFD66132C872FD4
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006000C192101002200 [RAP3G ver: PA 2.2]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 14100006145E5A5136DB4DCE4E5D2A2D2379F647
ASIC MODE ID: 00
ROOT KEY HASH: E9EFF4BFAA5393217CA6B17755FC3E14
ROM ID: F28A211FCEA7B19D
SecondaryBoot: rap3gv2_2nd.fg [BB5] version: 1.21.0 revision: 0.0 size: 0x3D00
Supported Ids: 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200
FlashID0: 00EC 2250 - 0000 0121 [Samsung K8S6415ETB,64 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: 6E25F5B4407C1CBD0598994502C24000F3657C18
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 0036 - 00A5 00C0 [Samsung KAL00R00EM-DGXX,512 Mbits] type: NAND,APE
ALG [35]: OMAP1710 UNISTORE-II-1.2.1 ALG
ExtBUSC: 0002 0000 0006 0000 0000 0000 0000 0000
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: 6E25F5B4407C1CBD0598994502C24000F3657C18
Updating CMT NPC ...OK
Updating CMT VARIANT ...failed, Result: 0230000000717200

Phone Type: RM-43 (Nokia N91-2)
SW Version: V w33_07w11v1 14-03-07 RM-43 (c) Nokia.
Imei plain: 35276501062337-1
Product Code: 0538601
Battery voltage: 4686 mV, current: 26 mA
Language Pack:
- not available.

SIMLOCK seems to be valid
SUPERDONGLE_KEY[MX] seems to be valid
CMLA_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!


Imei net: 352765010623371
Version: SIMLOCK SERVER VERSION 62
Counter: 0/3, 0/10

CONFIG_DATA: 2440700000000000
PROFILE_BITS: 0000000000000000

BLOCK1: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK2: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK3: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK4: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK5: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK6: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK7: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN

и PM с SX4

Лог записи PM с SX4 Авторизацией

SERVER->Served by MXKEY - BLADE X at host1, agent version 1.1 revision 0.7
MXKEY Serial: [FT SCR2000 0] - C0847F00
Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Driver: UFS2XX, ver: 3.4.16.0, NTMP ver: 2.2.4.1
Module ver: 1.0.0.16662(04-05-2011), Library ver: 1.0.0.9921(04-05-2011)

Product: V w33_07w11v1 14-03-07 RM-43 (c) Nokia.

Using cached productData[14100006145E5A5136DB4DCE4E5D2A2D2379F647] ...
Calculating using security server ...
SUPERDONGLE authorized !
Writing PM from Node ...
Section: 1
- Key: 0, size 114 bytes written.
- Key: 1, size 4 bytes written.
- Key: 2, size 86 bytes written.
- Key: 4, size 110 bytes written.
- Key: 5, size 4 bytes written.
- Key: 6, size 86 bytes written.
- Key: 8, size 110 bytes written.
- Key: 13, size 86 bytes written.
- Key: 15, size 4 bytes written.
- Key: 16, size 86 bytes written.
- Key: 18, size 86 bytes written.
- Key: 20, size 86 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: 29, size 6 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.
Completed in 0.765 s

[UO5OQ]

По логам всё в порядке.
RPL сделал своё дело:

SIMLOCK seems to be valid
SUPERDONGLE_KEY[MX] seems to be valid
CMLA_KEY seems to be valid
SIMLOCK_TEST passed

А вот:

SECURITY_TEST failed!

Исправляется с помощью записи PM с SX4 Авторизацией.

Сделайте так:

- Полное стирание телефона файлом BB5Erase_16MBrap.rar (IMEI должен стать 12345...)
- Запись SW соответствующего железу RM-xxx
- Запись заводского RPL
- Запись полного PM N91_RM-43_UO5OQ_com_PM.rar с настоящей SX4 Авторизацией (кнопка PMM Auth в MX-KEY)

[lokolok1]

человеки, помогите пожауйста!!!!! тема еще актуальна,клиент немного потерпит, а я его нет. 8mb ерайзит нормально а 16 нехочет

[UO5OQ]

Сообщение от lokolok1

человеки, помогите пожауйста!!!!! тема еще актуальна,клиент немного потерпит, а я его нет. 8mb ерайзит нормально а 16 нехочет

Для стирания 1-го поля PM запишите вот этот PM из Файлового Архива нашего сервера: 6303c_RM-443_ZERO_PM_UO5OQ_com.rar

И покажите лог записи эттого PM и лог INFO после этого.

[lokolok1]

Лог записи PM

Writing PM from Node ...
Section: 1
- Key: 0, size 0 bytes written.
- Key: 1, size 0 bytes written.
- Key: 2, size 0 bytes written.
- Key: 3, size 0 bytes written.
- Key: 4, size 0 bytes written.
- Key: 5, size 0 bytes written.
- Key: 6, size 0 bytes written.
- Key: 7, size 0 bytes written.
- Key: 8, size 0 bytes written.
- Key: 9, size 0 bytes written.
- Key: 10, size 0 bytes written.
- Key: 11, size 0 bytes written.
- Key: 12, size 0 bytes written.
- Key: 13, size 0 bytes written.
- Key: 14, size 0 bytes written.
- Key: 15, size 0 bytes written.
- Key: 16, size 0 bytes written.
- Key: 17, size 0 bytes written.
- Key: 18, size 0 bytes written.
- Key: 19, size 0 bytes written.
- Key: 20, size 0 bytes written.
- Key: 21, size 0 bytes written.
- Key: 22, size 0 bytes written.
- Key: 23, size 0 bytes written.
- Key: 24, size 0 bytes written.
- Key: 25, size 0 bytes written.
- Key: 26, size 0 bytes written.
- Key: 27, size 0 bytes written.
- Key: 28, size 0 bytes written.
- Key: 29, size 0 bytes written.
- Key: 30, size 0 bytes written.
- Key: 31, size 0 bytes written.
- Key: 32, size 0 bytes written.
- Key: 33, size 0 bytes written.
Warning: failed to write 1 - 34 (0 bytes)
Warning: failed to write 1 - 35 (0 bytes)
Warning: failed to write 1 - 36 (0 bytes)
Warning: failed to write 1 - 37 (0 bytes)
Warning: failed to write 1 - 38 (0 bytes)
Warning: failed to write 1 - 39 (0 bytes)

инфо UFS:

MCU SW : V w33_07w11v1 14-03-07 RM-43 (c) Nokia.
APE Core:
APE Var :
Product : Nokia N91-1
Prd.Code: 0523198
Bpr.Code: 0519850
Prod.Sn : SFF309457
HW Vers : 0600
APE HW :
APE Adsp:
EM RETU : 32
EM TAHVO: 53
RFIC Ver: 150a160f
DSP Vers: nemo_w_05wk32v33b
IMEI : 123456-10-654321-?
SL Serv : SIMLOCK SERVER VERSION 62
SL Conf : FFF-FF-FFFFFFFFFFF
SL Prof : FFFFFFFFFFFFFFFF
SL Count: 00 01
BLK1= L1: CLOS
Provider: Not Found

[UO5OQ]

А что теперь с security test?

[lokolok1]

немогу пройти тесты изза битого имея

[UO5OQ]

А после чего, к стати, испортился IMEI и SLD ?
После записи ZERO PM ?

[lokolok1]

после прошивки

[UO5OQ]

Сообщение от lokolok1

после прошивки

Значит прошили НЕсоответствующий железу RM-xxx
Давайте всё с начала.
- SW (соответствующее железу)
- RPL
- PM c SX4

И смотрим логи.

[lokolok1]

возможно вы правы а как по железу пробить 4gb или 8 gb N91 потомучто кузов и наклейка 8GB

[UO5OQ]

Подзабыл уже. Давно не видел их.
Запишите самую старую SW для одного типа и для другого.
На которой IMEI выровняется - та и его.

[lokolok1]

На прошиве 4 gb невходит в локал пробить нечего нельзя, на 8gb IMEI стал восстановился. Получили:

Лог записи SW

** User Break **
1ST BOOT : C0,0C [Rm-43] [2.1.0.0]
OMAP ID : 17100708
OMAP MODE : 00
OMAP PBID : 7523ADDF5379000DBC07A7FE3D84028FFAF0CC77
OMAP HASH : 49A97E826B93BA20B7ED0B082475C005
OMAP ROID : 1DFD66132C872FD4
RAPx ID : 000000010000022600010006000C192101002200
EM 1 ID : 00000232
EM 2 ID : 00000353
RAPx PBID : 14100006145E5A5136DB4DCE4E5D2A2D2379F647
RAPx MODE : 00
RAPx HASH : E9EFF4BFAA5393217CA6B17755FC3E14
RAPx ROID : F28A211FCEA7B19D
CMT 1ST Boot OK
CMT 2ND Bt: RAP3Gv2_2nd.fg, Ver: 1.21.0
CMT FLID0 : 00EC2250-00000121, Sam K8S6415ETB
CMT FLCNT : 00000000000000000000000000000000000000
CMT MCID0 : FFFF0000-00000000
CMT 2ND Boot OK
CMT ALGO : RAP3Gv3_algo.fg, Ver: 9.17.0
CMT VPP : Internal
DUAL LINE : True
CMT ALG Boot OK
IMAGE : RM43_V3.10.023.core
CMT NOR Erase Area: 0x00000000-00530561
CMT NOR Erase Area: 0x006A0000-006BFFFF
CMT NOR Erase Area: 0x006DF000-006EFFFF
CMT NOR Erase Area: 0x00700000-007EFFFF
CMT FLASH ERASE OK, Time: 00:41
Written: 8 Certificate(s)
CMT FLASH WRITE OK, Time: 00:27
1ST BOOT : C0,0C [Rm-43] [2.1.0.0]
OMAP ID : 17100708
OMAP MODE : 00
OMAP PBID : 7523ADDF5379000DBC07A7FE3D84028FFAF0CC77
OMAP HASH : 49A97E826B93BA20B7ED0B082475C005
OMAP ROID : 1DFD66132C872FD4
RAPx ID : 000000010000022600010006000C192101002200
EM 1 ID : 00000232
EM 2 ID : 00000353
RAPx PBID : 14100006145E5A5136DB4DCE4E5D2A2D2379F647
RAPx MODE : 00
RAPx HASH : E9EFF4BFAA5393217CA6B17755FC3E14
RAPx ROID : F28A211FCEA7B19D
CMT 1ST Boot OK
CMT 2ND Bt: RAP3Gv2_2nd.fg, Ver: 1.21.0
CMT FLID0 : 00EC2250-00000121, Sam K8S6415ETB
CMT FLCNT : 00000000000000000000000000000000000000
CMT MCID0 : FFFF0000-00000000
CMT 2ND Boot OK
CMT ALGO : RAP3Gv3_algo.fg, Ver: 9.17.0
CMT KSIG0 : 6E25F5B4407C1CBD0598994502C24000F3657C18
CMT VPP : Internal
DUAL LINE : True
CMT ALG Boot OK
APE 2ND Bt: helen3_2nd.fg, Ver: 1.35.0
APE FLID0 : 00EC0036-00A500C0, Sam KAL00R00EB
APE RQALG : OMAP1710 UNISTORE-II-1.2.1 ALG
APE FLCNT : 01010000020000000600000000000000000000
APE 2ND Boot OK
APE ALG0 : h3_sam_nand_xsr_small.fg, Ver: 1.35.0
APE VPP : Internal
DUAL LINE : True
APE ALG Boot OK
IMAGE : RM43_V3.10.023.core
APE NAND Erase Area: 0x00000000-0000FFFF
APE NAND Erase Area: 0x00010000-0001FFFF
APE NAND Erase Area: 0x00020000-000203FF
APE NAND Erase Area: 0x00028000-02F3CFFF
APE FLASH ERASE OK, Time: 00:05
Written: 11 Certificate(s)
APE FLASH WRITE OK, Time: 02:50
1ST BOOT : C0,0C [Rm-43] [2.1.0.0]
OMAP ID : 17100708
OMAP MODE : 00
OMAP PBID : 7523ADDF5379000DBC07A7FE3D84028FFAF0CC77
OMAP HASH : 49A97E826B93BA20B7ED0B082475C005
OMAP ROID : 1DFD66132C872FD4
RAPx ID : 000000010000022600010006000C192101002200
EM 1 ID : 00000232
EM 2 ID : 00000353
RAPx PBID : 14100006145E5A5136DB4DCE4E5D2A2D2379F647
RAPx MODE : 00
RAPx HASH : E9EFF4BFAA5393217CA6B17755FC3E14
RAPx ROID : F28A211FCEA7B19D
CMT 1ST Boot OK
CMT 2ND Bt: RAP3Gv2_2nd.fg, Ver: 1.21.0
CMT FLID0 : 00EC2250-00000121, Sam K8S6415ETB
CMT FLCNT : 00000000000000000000000000000000000000
CMT MCID0 : FFFF0000-00000000
CMT 2ND Boot OK
CMT ALGO : RAP3Gv3_algo.fg, Ver: 9.17.0
CMT KSIG0 : 6E25F5B4407C1CBD0598994502C24000F3657C18
CMT VPP : Internal
DUAL LINE : True
CMT ALG Boot OK
APE 2ND Bt: helen3_2nd.fg, Ver: 1.35.0
APE FLID0 : 00EC0036-00A500C0, Sam KAL00R00EB
APE RQALG : OMAP1710 UNISTORE-II-1.2.1 ALG
APE FLCNT : 01010000020000000600000000000000000000
APE 2ND Boot OK
APE ALG0 : h3_sam_nand_xsr_small.fg, Ver: 1.35.0
APE VPP : Internal
DUAL LINE : True
APE ALG Boot OK
IMAGE : RM43_V3.10.023.04.variant
APE NAND Erase Area: 0x01F90000-02F3CFFF
PPM FLASH ERASE OK, Time: 00:01
Written: 1 Certificate(s)
PPM FLASH WRITE OK, Time: 01:37
Flashing Completed, Rebooting Mobile

Лог записи RPL:

Imei: 35276501062337
Updating WARRANTY ...OK
Updating PROD ...OK
Updating BT ...OK
Updating PRODUCTCODE (0538601)... OK
Updating PSN (SEK556292)... OK
Updating HWID (1000)... OK
Updating LOCK ...OK
Updating SUPERDONGLE_KEY ...OK
APE Data :
SYSTEM ASIC ID: 17100708 [OMAP1710 ver: 2.0]
ASIC MODE ID: 00
PUBLIC ID: 7523ADDF5379000DBC07A7FE3D84028FFAF0CC77
ROOT KEY HASH: 49A97E826B93BA20B7ED0B082475C00500000000
ROM ID: 1DFD66132C872FD4
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006000C192101002200 [RAP3G ver: PA 2.2]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 14100006145E5A5136DB4DCE4E5D2A2D2379F647
ASIC MODE ID: 00
ROOT KEY HASH: E9EFF4BFAA5393217CA6B17755FC3E14
ROM ID: F28A211FCEA7B19D
SecondaryBoot: rap3gv2_2nd.fg [BB5] version: 1.21.0 revision: 0.0 size: 0x3D00
Supported Ids: 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200
FlashID0: 00EC 2250 - 0000 0121 [Samsung K8S6415ETB,64 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: 6E25F5B4407C1CBD0598994502C24000F3657C18
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 0036 - 00A5 00C0 [Samsung KAL00R00EM-DGXX,512 Mbits] type: NAND,APE
ALG [35]: OMAP1710 UNISTORE-II-1.2.1 ALG
ExtBUSC: 0002 0000 0006 0000 0000 0000 0000 0000
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: 6E25F5B4407C1CBD0598994502C24000F3657C18
Updating CMT NPC ...OK

Phone Type: RM-43 (Nokia N91-2)
SW Version: V w33_07w11v1 14-03-07 RM-43 (c) Nokia.
Imei plain: 35276501062337-1
Product Code: 0538601
Battery voltage: 4632 mV, current: 25 mA
Language Pack:
- not available.

SIMLOCK seems to be valid
SUPERDONGLE_KEY[MX] seems to be valid
CMLA_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!


Imei net: 352765010623371
Version: SIMLOCK SERVER VERSION 62
Counter: 0/3, 0/10

CONFIG_DATA: 2440700000000000
PROFILE_BITS: 0000000000000000

BLOCK1: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK2: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK3: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK4: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK5: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK6: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK7: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN

Лог записи моего родного PM:

Scanning local SX4 Card ...
No SX4 Card found.
SERVER->Served by MXKEY - BLADE X at host1, agent version 1.1 revision 0.7

Authenticating using [MX] security server ...
Connecting to server[main.mxkey.biz] ...MXKEY SX4CARD - ID, hello 2.133.198.81
SUPERDONGLE authorized !
Writing PM from Node ...
Section: 1
- Key: 0, size 114 bytes written.
- Key: 1, size 4 bytes written.
- Key: 2, size 86 bytes written.
- Key: 4, size 110 bytes written.
- Key: 5, size 4 bytes written.
- Key: 6, size 86 bytes written.
- Key: 8, size 110 bytes written.
- Key: 13, size 86 bytes written.
- Key: 15, size 4 bytes written.
- Key: 16, size 86 bytes written.
- Key: 18, size 86 bytes written.
- Key: 20, size 86 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: 29, size 6 bytes written.
Section: 2
- Key: 0, size 360 bytes written.
Section: 4
- Key: 0, size 1 bytes written.
- Key: 1, size 36 bytes written.
- Key: 2, size 44 bytes written.
- Key: 3, size 10 bytes written.
- Key: 4, size 8 bytes written.
- Key: 5, size 8 bytes written.
- Key: 9, size 5 bytes written.
Section: 8
- Key: 0, size 12 bytes written.
- Key: 1, size 12 bytes written.
- Key: 6, size 4 bytes written.
- Key: 7, size 8 bytes written.
Section: 11
- Key: 0, size 4 bytes written.
- Key: 1, size 4 bytes written.
- Key: 2, size 4 bytes written.
- Key: 3, size 4 bytes written.
- Key: 4, size 1 bytes written.
- Key: 5, size 6 bytes written.
- Key: 6, size 1 bytes written.
- Key: 7, size 2 bytes written.
- Key: 8, size 2 bytes written.
- Key: 9, size 2 bytes written.
- Key: 10, size 2 bytes written.
- Key: 11, size 2 bytes written.
- Key: 12, size 1 bytes written.
- Key: 13, size 1 bytes written.
- Key: 14, size 1 bytes written.
- Key: 15, size 1 bytes written.
- Key: 16, size 1 bytes written.
- Key: 17, size 1 bytes written.
- Key: 18, size 1 bytes written.
- Key: 19, size 2 bytes written.
- Key: 20, size 2 bytes written.
- Key: 21, size 1 bytes written.
- Key: 22, size 1 bytes written.
- Key: 23, size 4 bytes written.
- Key: 24, size 4 bytes written.
- Key: 25, size 2 bytes written.
- Key: 26, size 2 bytes written.
- Key: 27, size 2 bytes written.
- Key: 28, size 2 bytes written.
- Key: 29, size 1 bytes written.
- Key: 30, size 1 bytes written.
- Key: 31, size 1 bytes written.
- Key: 32, size 1 bytes written.
- Key: 33, size 1 bytes written.
- Key: 34, size 1 bytes written.
- Key: 35, size 1 bytes written.
- Key: 36, size 1 bytes written.
- Key: 37, size 1 bytes written.
- Key: 38, size 2 bytes written.
- Key: 39, size 2 bytes written.
- Key: 40, size 2 bytes written.
- Key: 41, size 2 bytes written.
- Key: 42, size 2 bytes written.
- Key: 43, size 4 bytes written.
- Key: 44, size 4 bytes written.
- Key: 45, size 4 bytes written.
- Key: 46, size 1 bytes written.
- Key: 47, size 16 bytes written.
- Key: 48, size 2 bytes written.
- Key: 49, size 2 bytes written.
- Key: 50, size 20 bytes written.
- Key: 51, size 10 bytes written.
- Key: 52, size 2 bytes written.
- Key: 53, size 20 bytes written.
- Key: 54, size 10 bytes written.
- Key: 55, size 1 bytes written.
- Key: 56, size 1 bytes written.
- Key: 57, size 1 bytes written.
- Key: 58, size 1 bytes written.
- Key: 59, size 1 bytes written.
- Key: 60, size 1 bytes written.
- Key: 61, size 1 bytes written.
- Key: 62, size 1 bytes written.
- Key: 63, size 1 bytes written.
- Key: 64, size 1 bytes written.
- Key: 65, size 1 bytes written.
- Key: 66, size 32 bytes written.
- Key: 67, size 32 bytes written.
- Key: 68, size 2 bytes written.
- Key: 69, size 2 bytes written.
- Key: 70, size 2 bytes written.
- Key: 71, size 2 bytes written.
- Key: 72, size 2 bytes written.
- Key: 73, size 2 bytes written.
- Key: 74, size 2 bytes written.
- Key: 75, size 2 bytes written.
- Key: 76, size 2 bytes written.
- Key: 77, size 2 bytes written.
- Key: 78, size 2 bytes written.
- Key: 79, size 2 bytes written.
- Key: 80, size 2 bytes written.
- Key: 81, size 2 bytes written.
- Key: 82, size 2 bytes written.
- Key: 83, size 2 bytes written.
- Key: 84, size 2 bytes written.
- Key: 85, size 2 bytes written.
- Key: 86, size 2 bytes written.
- Key: 87, size 2 bytes written.
- Key: 88, size 2 bytes written.
- Key: 89, size 2 bytes written.
- Key: 90, size 2 bytes written.
- Key: 91, size 2 bytes written.
- Key: 92, size 2 bytes written.
- Key: 93, size 2 bytes written.
- Key: 94, size 2 bytes written.
- Key: 95, size 2 bytes written.
- Key: 96, size 2 bytes written.
- Key: 97, size 2 bytes written.
- Key: 98, size 2 bytes written.
- Key: 99, size 2 bytes written.
- Key: 100, size 2 bytes written.
- Key: 101, size 2 bytes written.
- Key: 102, size 2 bytes written.
- Key: 103, size 2 bytes written.
- Key: 104, size 2 bytes written.
- Key: 105, size 2 bytes written.
- Key: 106, size 2 bytes written.
- Key: 107, size 2 bytes written.
- Key: 108, size 2 bytes written.
- Key: 109, size 2 bytes written.
- Key: 110, size 2 bytes written.
- Key: 111, size 2 bytes written.
- Key: 112, size 2 bytes written.
- Key: 113, size 4 bytes written.
- Key: 114, size 4 bytes written.
- Key: 115, size 1 bytes written.
- Key: 116, size 4 bytes written.
- Key: 117, size 4 bytes written.
- Key: 118, size 4 bytes written.
- Key: 119, size 4 bytes written.
- Key: 120, size 16 bytes written.
- Key: 121, size 4 bytes written.
- Key: 122, size 2 bytes written.
- Key: 123, size 2 bytes written.
Section: 50
- Key: 0, size 2 bytes written.
Section: 54
- Key: 0, size 2 bytes written.
Section: 88
- Key: 0, size 36 bytes written.
Section: 92
- Key: 0, size 10 bytes written.
Section: 96
- Key: 0, size 24 bytes written.
Section: 107
- Key: 0, size 21 bytes written.
- Key: 1, size 79 bytes written.
- Key: 2, size 79 bytes written.
- Key: 3, size 70 bytes written.
- Key: 25, size 132 bytes written.
Section: 193
- Key: 2, size 8 bytes written.
- Key: 3, size 32 bytes written.
- Key: 4, size 32 bytes written.
- Key: 9, size 64 bytes written.
- 308 skipped
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.
Section: 313
- Key: 0, size 615 bytes written.
Section: 322
- Key: 0, size 1 bytes written.
Completed in 6.235 s

Спасибо за поддержку!!!!

[UO5OQ]

Так что наконец SECURITY_TEST passed
?

[lokolok1]

неа все по старому, просто приятно с профессионалом общаться!!!!

и как этот sec test побороть?

[UO5OQ]

Сообщение от lokolok1

неа все по старому, просто приятно с профессионалом общаться!!!!

и как этот sec test побороть?

Сейчас сделайте как тут: http://www.uo5oq.com/forum/showpost....41&postcount=6

[lokolok1]

запись pm а инфо непроходит

Лог записи ZERO_PM

LogFile: .\_!_LOG\73528_20052011_230659_LOG.txt
PM File: 6303c_RM-443_ZERO_PM_UO5OQ_com.pm
Group Id: [1] Rec: 0 Len: 0 ...... Ok 1
Group Id: [1] Rec: 1 Len: 0 ...... Ok 1
Group Id: [1] Rec: 2 Len: 0 ...... Ok 1
Group Id: [1] Rec: 3 Len: 0 ...... Ok 1
Group Id: [1] Rec: 4 Len: 0 ...... Ok 1
Group Id: [1] Rec: 5 Len: 0 ...... Ok 1
Group Id: [1] Rec: 6 Len: 0 ...... Ok 1
Group Id: [1] Rec: 7 Len: 0 ...... Ok 1
Group Id: [1] Rec: 8 Len: 0 ...... Ok 1
Group Id: [1] Rec: 9 Len: 0 ...... Ok 1
Group Id: [1] Rec: 10 Len: 0 ...... Ok 1
Group Id: [1] Rec: 11 Len: 0 ...... Ok 1
Group Id: [1] Rec: 12 Len: 0 ...... Ok 1
Group Id: [1] Rec: 13 Len: 0 ...... Ok 1
Group Id: [1] Rec: 14 Len: 0 ...... Ok 1
Group Id: [1] Rec: 15 Len: 0 ...... Ok 1
Group Id: [1] Rec: 16 Len: 0 ...... Ok 1
Group Id: [1] Rec: 17 Len: 0 ...... Ok 1
Group Id: [1] Rec: 18 Len: 0 ...... Ok 1
Group Id: [1] Rec: 19 Len: 0 ...... Ok 1
Group Id: [1] Rec: 20 Len: 0 ...... Ok 1
Group Id: [1] Rec: 21 Len: 0 ...... Ok 1
Group Id: [1] Rec: 22 Len: 0 ...... Ok 1
Group Id: [1] Rec: 23 Len: 0 ...... Ok 1
Group Id: [1] Rec: 24 Len: 0 ...... Ok 1
Group Id: [1] Rec: 25 Len: 0 ...... Ok 1
Group Id: [1] Rec: 26 Len: 0 ...... Ok 1
Group Id: [1] Rec: 27 Len: 0 ...... Ok 1
Group Id: [1] Rec: 28 Len: 0 ...... Ok 1
Group Id: [1] Rec: 29 Len: 0 ...... Ok 1
Group Id: [1] Rec: 30 Len: 0 ...... Ok 1
Group Id: [1] Rec: 31 Len: 0 ...... Ok 1
Group Id: [1] Rec: 32 Len: 0 ...... Ok 1
Group Id: [1] Rec: 33 Len: 0 ...... Ok 1
Group Id: [1] Rec: 34 Len: 0 ...... Ok 1
Group Id: [1] Rec: 35 Len: 0 ...... Ok 1
Group Id: [1] Rec: 36 Len: 0 ...... Ok 1
Group Id: [1] Rec: 37 Len: 0 ...... Ok 1
Group Id: [1] Rec: 38 Len: 0 ...... Ok 1
Group Id: [1] Rec: 39 Len: 0 ...... Ok 1
Group Id: [1] Rec: 4 Len: 0 ...... Ok 1
Group Id: [1] Rec: 41 Len: 0 ...... Ok 1
Group Id: [1] Rec: 42 Len: 0 ...... Ok 1
Group Id: [1] Rec: 43 Len: 0 ...... Ok 1
Group Id: [1] Rec: 44 Len: 0 ...... Ok 1
Group Id: [1] Rec: 45 Len: 0 ...... Ok 1
Group Id: [1] Rec: 46 Len: 0 ...... Ok 1
Group Id: [1] Rec: 47 Len: 0 ...... Ok 1
Group Id: [1] Rec: 48 Len: 0 ...... Ok 1
Write PM Done, Time: 00:01

[UO5OQ]

А SCAN MX-KEYем?

[lokolok1]

скан стал определять rm-43 с номером продукта, уже чтото

[UO5OQ]

А вы записывали НЕ ваш родной PM?

Вот сделайте так: http://www.uo5oq.com/forum/showpost....03&postcount=4

[lokolok1]

и мой и ваш

[UO5OQ]

А после полного стирания и записи только SW он полностью включается?

[lokolok1]

неа те же грабли phone start-up... имей тож слетел

[UO5OQ]

Сообщение от lokolok1

неа те же грабли phone start-up... имей тож слетел

Я думал вы знаете.
Что любая Nokia полностью стёртая и записаная только SW, обязана полностью включаться.

Выходит вам нужно смотреть железо.

[lokolok1]

спасибо пнятно, буду ковырять. Вероятней всего rap omap и флеш??

[UO5OQ]

Сообщение от lokolok1

спасибо пнятно, буду ковырять. Вероятней всего rap omap и флеш??

При таких симптомах, может даже мелочь какая то.
Посмотрите результат SELF TEST, может там что-то конкретнее будет видно.