Load RFBB from server

mobilchiki · 20.07.2012, 12:46

Load RFBB from server

Authenticating using [MX] security server
Connecting to server[main.mxkey.biz] ...MXKEY SX4CARD - ID, hello 95.153.175.236
SUPERDONGLE authorized

!
Writing RFBB data: modules\{3EBAF427-9F55-419F-8A75-385DFC651169}\def\rfbb\5530_RM-504.txt ...
Writing RF settings to phone ...OK, finished. 16 Records found.
Writing BB settings to phone ...OK, finished. 8 Records found.
Done.
SERVER->MXKEY - BLADE X at host1, agent version 1.2 revision 0.4

Updating RFBB data ...
Writing section 1...
Writing section 309...
Done.

Запись 1 и 309 блоков не по момогает

SCAN

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!

BB5 Certificate Validation

CMT Data :
SYSTEM ASIC ID: 000000010000022600010006400C192101051105 [RAPIDOYAWE ver: 1.1x]
EM0 ID: 00000296
EM1 ID: 00000B22
PUBLIC ID: 0CA000011688005231E027FB23EE9686576FE36A
ASIC MODE ID: 00
ROOT KEY HASH: B8C3ADECFC997FCD8081D3DEAF870B8C
ROM ID: 4B9B75103E691FF8
SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 12.8.0 revision: 2.0 size: 0x3B80
Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105
eBB5ProtocolType: NEW
TransmissionMode: DDR&TX2
Storage0: 0000 0000 - 0000 0000 type: RAM, asic:CMT
Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT
Storage2: 0020 0040 - 0000 0031 [ST NAND KAT00F00RA] type: FLASH,NOR, asic:CMT
Storage3: 0000 0001 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT
Storage4: 0020 0040 - 0000 0031 [ST NAND KAT00F00RA] type: FLASH,MuxOneNAND, asic:CMT
Suggested algorithm: XSR 1.5
Algorithm: RAPIDOv11_XSR15_alg.fg [XSR 1.5] version: 12.8.0 revision: 2.0 size: 0x8B49D
Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105
TransmissionMode: DDR&TX2
FUR: Adding Asic CMT as client OK
CMT PAPUBKEYS HASH: F2B05364E563A348608C1C3C9E54FE42AAAA1ACF
Reading CMT NPC (0x190 bytes).
Original Product Code: 0577619
Reading CMT VARIANT (0x0 bytes).
Reading CMT CCC (0x160 bytes).
Product Code: 0577619
CCC seems to be valid
Reading CMT HWC (0xD4 bytes).
Product Code: 0577619
HWC seems to be valid

как можно вылечить?

20.07.2012, 12:46	#1
mobilchiki Senior Member Регистрация: 02.05.2012 Адрес: Krasnodar-Cherkessk Russia Сообщений: 164 Вес репутации: 63	5530 RM-504 SECURITY_TEST failed! Load RFBB from server Authenticating using [MX] security server Connecting to server[main.mxkey.biz] ...MXKEY SX4CARD - ID, hello 95.153.175.236 SUPERDONGLE authorized ! Writing RFBB data: modules\{3EBAF427-9F55-419F-8A75-385DFC651169}\def\rfbb\5530_RM-504.txt ... Writing RF settings to phone ...OK, finished. 16 Records found. Writing BB settings to phone ...OK, finished. 8 Records found. Done. SERVER->MXKEY - BLADE X at host1, agent version 1.2 revision 0.4 Updating RFBB data ... Writing section 1... Writing section 309... Done. Запись 1 и 309 блоков не по момогает SCAN 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! BB5 Certificate Validation CMT Data : SYSTEM ASIC ID: 000000010000022600010006400C192101051105 [RAPIDOYAWE ver: 1.1x] EM0 ID: 00000296 EM1 ID: 00000B22 PUBLIC ID: 0CA000011688005231E027FB23EE9686576FE36A ASIC MODE ID: 00 ROOT KEY HASH: B8C3ADECFC997FCD8081D3DEAF870B8C ROM ID: 4B9B75103E691FF8 SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 12.8.0 revision: 2.0 size: 0x3B80 Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105 eBB5ProtocolType: NEW TransmissionMode: DDR&TX2 Storage0: 0000 0000 - 0000 0000 type: RAM, asic:CMT Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT Storage2: 0020 0040 - 0000 0031 [ST NAND KAT00F00RA] type: FLASH,NOR, asic:CMT Storage3: 0000 0001 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT Storage4: 0020 0040 - 0000 0031 [ST NAND KAT00F00RA] type: FLASH,MuxOneNAND, asic:CMT Suggested algorithm: XSR 1.5 Algorithm: RAPIDOv11_XSR15_alg.fg [XSR 1.5] version: 12.8.0 revision: 2.0 size: 0x8B49D Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105 TransmissionMode: DDR&TX2 FUR: Adding Asic CMT as client OK CMT PAPUBKEYS HASH: F2B05364E563A348608C1C3C9E54FE42AAAA1ACF Reading CMT NPC (0x190 bytes). Original Product Code: 0577619 Reading CMT VARIANT (0x0 bytes). Reading CMT CCC (0x160 bytes). Product Code: 0577619 CCC seems to be valid Reading CMT HWC (0xD4 bytes). Product Code: 0577619 HWC seems to be valid как можно вылечить?