Нокиа N85 не получается восстановить сертификаты

[RUSLAN417]

мне не понятно почему поэтому? объясните пожалуйста
------------------------------------------------
Добавлено позже:
все вышеописанное делал! хочу купить на днях MXKey . может он поможет залить нормально RPL. тогда отпишусь

[RUSLAN417]

Всем привет!Хочу продолжить начатую тему!так и не получается восстановить сертификаты N85. Купил MXKey. все делал по видеомануалу для MXKey. стирал всю память телефона и прошивал полностью. телефон после этого включался работал но имей 12345...после этого заливаю заказанный RPL. имей восстанавливается. вот лог:mei: 35570802567970

Updating PRODUCTCODE (0560578)... OK
Updating PSN (CSE704954)... OK
Updating HWID (1405)... OK
Updating SIMLOCK...OK
Updating SUPERDONGLE_KEY ...OK
Updating CMLA_KEY...OK
Updating WMDRM_PD...OK
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006400C192101031103 [RAPIDO3G ver: 1.13]
EM0 ID: 00000296
EM1 ID: 00000B22
PUBLIC ID: 1E20010AADDA0158123CEBE034787D593308CE93
ASIC MODE ID: 00
ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
ROM ID: 4B9B75103E691FF8
 SecondaryBoot: RAPIDOv11_2nd.fg [BB5]  version: 1.37.1 revision: 0.0 size: 0x3B80
 Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105
FlashID0: 00EC 0040  - 0080 0121 [Samsung 2Gb DDP OneNAND,2 Gbits] type: MuxOneNAND,RAP 
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000 
TransmissionMode: 16Bit
 Algorithm: RAPIDOv11_algo.fg [XSR 1.5]  version: 1.40.0 revision: 0.0 size: 0x27520
 Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105
RAP PAPUBKEYS HASH: B5385A493D2188678E1FD88DA506480F874E2949
NPC verified Ok.
Updating CMT  NPC ...OK
Updating CMT  CCC ...OK
Updating CMT  HWC ...OK
Certificate programmed successfully !
после этого пытаюсь пролить PM вот лог
Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(ID),  hello 178.177.50.189
Wrong response to SD update hash request
SUPERDONGLE auth failed!
ъ’
У[чp„•Њї“kќ хDл¤э/уµђ
Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(ID),  hello 178.177.50.189
Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(ID),  hello 178.177.50.189
SUPERDONGLE authorized :)!
Writing PM from Node ...
Section: 1
Warning: failed to write 1 - 0 (114 bytes)
Warning: failed to write 1 - 2 (10 bytes)
Warning: failed to write 1 - 4 (110 bytes)
Warning: failed to write 1 - 6 (10 bytes)
Warning: failed to write 1 - 7 (214 bytes)
Warning: failed to write 1 - 8 (110 bytes)
Warning: failed to write 1 - 13 (10 bytes)
Warning: failed to write 1 - 16 (208 bytes)
Warning: failed to write 1 - 18 (208 bytes)
Warning: failed to write 1 - 20 (208 bytes)
Warning: failed to write 1 - 22 (16 bytes)
Warning: failed to write 1 - 23 (4 bytes)
Warning: failed to write 1 - 24 (84 bytes)
Warning: failed to write 1 - 26 (110 bytes)
Warning: failed to write 1 - 28 (10 bytes)
Warning: failed to write 1 - 29 (10 bytes)
Warning: failed to write 1 - 31 (208 bytes)
Warning: failed to write 1 - 33 (36 bytes)
Warning: failed to write 1 - 34 (376 bytes)
Warning: failed to write 1 - 35 (16 bytes)
Warning: failed to write 1 - 37 (4 bytes)
Warning: failed to write 1 - 39 (36 bytes)
Warning: failed to write 1 - 40 (16 bytes)
Warning: failed to write 1 - 41 (182 bytes)
Warning: failed to write 1 - 42 (4 bytes)
Warning: failed to write 1 - 43 (36 bytes)
Warning: failed to write 1 - 44 (182 bytes)
Warning: failed to write 1 - 45 (182 bytes)
Section: 2
 - Key: 0, size 448 bytes written.
Section: 4
Warning: failed to write 4 - 1 (1020 bytes)
Warning: failed to write 4 - 3 (10 bytes)
Warning: failed to write 4 - 4 (8 bytes)
Warning: failed to write 4 - 5 (8 bytes)
Warning: failed to write 4 - 9 (5 bytes)

если проливаю PM без авторизации то при включении телефон выдает: Phone start-up failed.contact the retailer.

[borg]

выложи лог МХ при нажатии bus check

[RUSLAN417]

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.8069(22-04-2010), 1.0.0.12811(22-04-2010)
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006400C192101031103 [RAPIDO3G ver: 1.13]
EM0 ID: 00000296
EM1 ID: 00000B22
PUBLIC ID: 1E20010AADDA0158123CEBE034787D593308CE93
ASIC MODE ID: 00
ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
ROM ID: 4B9B75103E691FF8
 SecondaryBoot: RAPIDOv11_2nd.fg [BB5]  version: 1.37.1 revision: 0.0 size: 0x3B80
 Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105
FlashID0: 00EC 0040  - 0080 0121 [Samsung 2Gb DDP OneNAND,2 Gbits] type: MuxOneNAND,RAP 
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000 
TransmissionMode: 16Bit
 Algorithm: RAPIDOv11_algo.fg [XSR 1.5]  version: 1.40.0 revision: 0.0 size: 0x27520
 Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105
RAP PAPUBKEYS HASH: B5385A493D2188678E1FD88DA506480F874E2949
Original Imei: 35570802567970
Original Product code: 0560578
Bluetooth ID: 0022FCCA4392
WLAN ID: 0022FCD985D2
 
Phone Type: RM-333 (Nokia N85)
SW Version: V ICPR72_09w18.6 15-10-09 RM-333 (c) Nokia 
Imei plain: 35570802567970-4
Product Code: 0560502
Language Pack:
- not available.

SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
CMLA_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!
 
 
Imei net: 355708025679704
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