n76 ищу RPL c рабочего тела

[KARHer]

Здравствуйте!
Знакомый принес Nokia n76 с SECURITY_TEST failed!
Лог Bus check:

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006400C192101011103 [RAPIDO3G ver: 1.11]
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 1700011570580058C85CF9CD0D12C0661F6FCF16
ASIC MODE ID: 00
ROOT KEY HASH: 9A28E119033B91D14D22838C86D0D53C
ROM ID: F2C6EBADC86E6189
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 0030 - 0060 0121 [Samsung K5W1G13ACM-DJ60,1 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: 500F1CC61F6C1F570D3EF99F62B9AA86C53B2049
Original Imei: 35626201157169
Original Product code: 0543074
Bluetooth ID: 001BAFA0F131

Phone Type: RM-135 (Nokia N76)
SW Version: V 06wk41v46 06-11-07 RM-135 (c) Nokia
Imei plain: 35626201157169-8
Product Code: 0543073
Language Pack:
- not available.

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


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

собственно ищу Cert и pm слитый с рабочего тела, хочу влить заведомо рабочие блоки HWС, CCC.
Заранее благодарен.

[REKs]

мне кажется, достаточно будет влить PM (естесственно, без 120 и 308 блоков) с настоящей SX4...

[KARHer]

мне кажется, достаточно будет влить PM (естесственно, без 120 и 308 блоков) с настоящей SX4...
Super SD Auth

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)

Product: V 06wk41v46 06-11-07 RM-135 (c) Nokia
ApeCoreSw: 31.0.014

Using cached productData[1700011570580058C85CF9CD0D12C0661F6FCF16] ...

Authenticating to SUPERDONGLE using security server ...
SUPERDONGLE authorized :)!
SERVER->Served by MXKEY - BLADE X at host2, agent version 1.1 revision 0.0

Phone authenticated to SUPERDONGLE already.
Writing PM from Node ...
Section: 1
Warning: failed to write 1 - 0 (114 bytes)
Warning: failed to write 1 - 1 (4 bytes)
Warning: failed to write 1 - 2 (98 bytes)
Warning: failed to write 1 - 4 (110 bytes)
Warning: failed to write 1 - 5 (4 bytes)
Warning: failed to write 1 - 6 (98 bytes)
Warning: failed to write 1 - 8 (110 bytes)
Warning: failed to write 1 - 13 (98 bytes)
Warning: failed to write 1 - 15 (4 bytes)
Warning: failed to write 1 - 16 (98 bytes)
Warning: failed to write 1 - 18 (98 bytes)
Warning: failed to write 1 - 20 (98 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 - 25 (4 bytes)
Warning: failed to write 1 - 26 (110 bytes)
Warning: failed to write 1 - 27 (4 bytes)
Warning: failed to write 1 - 28 (98 bytes)
Warning: failed to write 1 - 29 (10 bytes)
Warning: failed to write 1 - 31 (98 bytes)
Warning: failed to write 1 - 33 (36 bytes)
Warning: failed to write 1 - 34 (80 bytes)
Warning: failed to write 1 - 44 (182 bytes)
Section: 2
- Key: 0, size 440 bytes written.
Section: 4
- Key: 1, size 60 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.
- Key: 28, size 2 bytes written.
Section: 8
- Key: 0, size 12 bytes written.
- Key: 1, size 12 bytes written.
- Key: 2, size 128 bytes written.
- Key: 3, size 128 bytes written.
- Key: 4, size 8 bytes written.
- Key: 6, size 4 bytes written.
- Key: 7, size 8 bytes written.
- Key: 8, size 8 bytes written.
- Key: 9, size 16 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 2 bytes written.
- Key: 5, size 1 bytes written.
Section: 12
- Key: 0, size 102 bytes written.
Section: 26
- Key: 0, size 16 bytes written.
- Key: 1, size 68 bytes written.
Section: 29
- Key: 2, size 8 bytes written.
Section: 31
- Key: 4, size 14 bytes written.
Section: 44
- Key: 0, size 1 bytes written.
Section: 50
- Key: 0, size 2 bytes written.
Section: 54
- Key: 0, size 2 bytes written.
- Key: 2, size 24 bytes written.
Section: 88
- Key: 0, size 36 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.
- Key: 26, size 16 bytes written.
Section: 117
- Key: 0, size 4 bytes written.
- Key: 1, size 3 bytes written.
- Key: 2, size 6 bytes written.
- Key: 3, size 1 bytes written.
- Key: 4, size 9 bytes written.
- Key: 5, size 10 bytes written.
- Key: 6, size 8 bytes written.
- Key: 8, size 42 bytes written.
- Key: 13, size 3 bytes written.
- Key: 14, size 3 bytes written.
- Key: 19, size 40 bytes written.
Section: 193
- Key: 2, size 8 bytes written.
- Key: 3, size 32 bytes written.
- Key: 4, size 32 bytes written.
- Key: 7, size 1 bytes written.
- Key: 9, size 64 bytes written.
Section: 208
- Key: 1, size 4 bytes written.
Section: 217
- Key: 0, size 32 bytes written.
Section: 239
- Key: 0, size 2 bytes written.
- Key: 1, size 2632 bytes written.
- Key: 2, size 2632 bytes written.
- 308 skipped
Section: 309
Warning: failed to write 309 - 0 (4 bytes)
Warning: failed to write 309 - 1 (2 bytes)
Warning: failed to write 309 - 2 (12 bytes)
Warning: failed to write 309 - 4 (12 bytes)
Warning: failed to write 309 - 5 (12 bytes)
Warning: failed to write 309 - 7 (12 bytes)
Warning: failed to write 309 - 8 (12 bytes)
Warning: failed to write 309 - 17 (12 bytes)
Warning: failed to write 309 - 22 (12 bytes)
Section: 322
- Key: 0, size 1 bytes written.
Section: 334
- Key: 0, size 1 bytes written.
Section: 341
- Key: 0, size 1 bytes written.
- Key: 3, size 4 bytes written.
- Key: 4, size 4402 bytes written.
Section: 354
- Key: 0, size 23 bytes written.
Section: 356
- Key: 0, size 2 bytes written.
- Key: 1, size 8 bytes written.
Completed in 7.531 s

[globotel]

Ну так 309 и 1 блоки не прописались.
Вот рабочий ПМ, пробуйте проливать только 1 и 309

[Meowt]

Что есть "RPL слитый с рабочего тела"?? :eek:

[REKs]

что-то у вас не проходит sx4. вы пробуете супер SD auth? или PMM auth? если SD не восстанавливали то нужно через PMM. хотя наверно уже SD покоцали. попробуйте репайр SD сделать и syper SD auth + PM.

[KARHer]

Что есть "RPL слитый с рабочего тела"?? :eek:

Да, не проснулся, исправил (спасибо что указали) нужны сертефикаты, но думаю что вы поняли что имелось ввиду?
SX4

SERVER->Served by MXKEY - BLADE X at host2, agent version 1.1 revision 0.0

Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY SX4CARD - ID, hello ля-ля-ля
SUPERDONGLE authorized :)!
Writing PM from Node ...
Section: 1
Warning: failed to write 1 - 0 (114 bytes)
Warning: failed to write 1 - 1 (4 bytes)
Warning: failed to write 1 - 2 (98 bytes)
Warning: failed to write 1 - 4 (110 bytes)
Warning: failed to write 1 - 5 (4 bytes)
Warning: failed to write 1 - 6 (98 bytes)
Warning: failed to write 1 - 8 (110 bytes)
Warning: failed to write 1 - 13 (98 bytes)
Warning: failed to write 1 - 15 (4 bytes)
Warning: failed to write 1 - 16 (98 bytes)
Warning: failed to write 1 - 18 (98 bytes)
Warning: failed to write 1 - 20 (98 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 - 25 (4 bytes)
Warning: failed to write 1 - 26 (110 bytes)
Warning: failed to write 1 - 27 (4 bytes)
Warning: failed to write 1 - 28 (98 bytes)
Warning: failed to write 1 - 29 (10 bytes)
Warning: failed to write 1 - 31 (98 bytes)
Warning: failed to write 1 - 33 (36 bytes)
Warning: failed to write 1 - 34 (80 bytes)
Warning: failed to write 1 - 44 (182 bytes)
Section: 2
- Key: 0, size 440 bytes written.
Section: 4
- Key: 1, size 60 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.
- Key: 28, size 2 bytes written.
Section: 8
- Key: 0, size 12 bytes written.
- Key: 1, size 12 bytes written.
- Key: 2, size 128 bytes written.
- Key: 3, size 128 bytes written.
- Key: 4, size 8 bytes written.
- Key: 6, size 4 bytes written.
- Key: 7, size 8 bytes written.
- Key: 8, size 8 bytes written.
- Key: 9, size 16 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 2 bytes written.
- Key: 5, size 1 bytes written.
Section: 12
- Key: 0, size 102 bytes written.
Section: 26
- Key: 0, size 16 bytes written.
- Key: 1, size 68 bytes written.
Section: 29
- Key: 2, size 8 bytes written.
Section: 31
- Key: 4, size 14 bytes written.
Section: 44
- Key: 0, size 1 bytes written.
Section: 50
- Key: 0, size 2 bytes written.
Section: 54
- Key: 0, size 2 bytes written.
- Key: 2, size 24 bytes written.
Section: 88
- Key: 0, size 36 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.
- Key: 26, size 16 bytes written.
Section: 117
- Key: 0, size 4 bytes written.
- Key: 1, size 3 bytes written.
- Key: 2, size 6 bytes written.
- Key: 3, size 1 bytes written.
- Key: 4, size 9 bytes written.
- Key: 5, size 10 bytes written.
- Key: 6, size 8 bytes written.
- Key: 8, size 42 bytes written.
- Key: 13, size 3 bytes written.
- Key: 14, size 3 bytes written.
- Key: 19, size 40 bytes written.
Section: 193
- Key: 2, size 8 bytes written.
- Key: 3, size 32 bytes written.
- Key: 4, size 32 bytes written.
- Key: 7, size 1 bytes written.
- Key: 9, size 64 bytes written.
Section: 208
- Key: 1, size 4 bytes written.
Section: 217
- Key: 0, size 32 bytes written.
Section: 239
Warning: failed to write 239 - 0 (2 bytes)
Warning: failed to write 239 - 1 (2632 bytes)
Warning: failed to write 239 - 2 (2632 bytes)
- 308 skipped
Section: 322
Warning: failed to write 322 - 0 (1 bytes)
Section: 334
Warning: failed to write 334 - 0 (1 bytes)
Section: 341
Warning: failed to write 341 - 0 (1 bytes)
Warning: failed to write 341 - 3 (4 bytes)
Warning: failed to write 341 - 4 (4402 bytes)
Section: 354
Warning: failed to write 354 - 0 (23 bytes)
Section: 356
Warning: failed to write 356 - 0 (2 bytes)
Warning: failed to write 356 - 1 (8 bytes)
Completed in 6.703 s

[globotel]

В РПЛе присутствует NPC, так что аккуратно, не забудьте вырезать.

[KARHer]

В РПЛе присутствует NPC, так что аккуратно, не забудьте вырезать.
Спасибо, я просто поочереди волью HWС а потом ССС, да и бекап сертифактов есть

[KARHer]

В РПЛе присутствует NPC, так что аккуратно, не забудьте вырезать.
NPC вырезаны, Security Test - passed :0

EM1 ID: 00000B22
PUBLIC ID: 1700011570580058C85CF9CD0D12C0661F6FCF16
ASIC MODE ID: 00
ROOT KEY HASH: 9A28E119033B91D14D22838C86D0D53C
ROM ID: F2C6EBADC86E6189
SecondaryBoot: RAPIDOv11_2nd.fg 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 0030 - 0060 0121 [Samsung K5W1G13ACM-DJ60,1 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: 500F1CC61F6C1F570D3EF99F62B9AA86C53B2049
NPC verified Ok.
[B]Updating CMT CCC ...OK
Updating CMT HWC ...OK
Certificate programmed successfully !

Phone Type: RM-135 (Nokia N76)
SW Version: V 06wk41v46 06-11-07 RM-135 (c) Nokia
Imei plain: 35626201157169-8
Product Code: 0543073
ApeCoreSw: 31.0.014
ApeVariant: 31.0.014, ApeTest: rm135_ENO_x_2007wk07v0.080
Language Pack:
- not available.

SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
CMLA_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST passed:icon14:


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