 Re: C5-00 RM-645 Security status : Security Damaged!!!!! :(
			
			
			#8
				Re: C5-00 RM-645 Security status : Security Damaged!!!!! :(
			
			
			#8
			
		 
		
		
		Аналогичная ситуация с С7-00 RM-675
Заводской RPL прописывается:
	Код:
	Up****** SIMLOCK...OK
Up****** SUPERDONGLE_KEY ...OK
Up****** CMLA_KEY...OK
Up****** WMDRM_PD...OK
CMT Data :
SYSTEM ASIC ID: 000000030000022600010007600C192102031104 [RAPU ver: 1.1]
EM0 ID: 00001040
EM1 ID: 00001030
PUBLIC ID: 1E200204C2D7034429512D30DA02E59A337A1569
ASIC MODE ID: 00
ROOT KEY HASH: 916F75217F32081248B15C38DFC8E81B
ROM ID: E693EF0DAC22615B
 SecondaryBoot: RAPUv11_2nd.fg [BB5]  version: 9.50.0 revision: 3.0 size: 0x3A40
 Supported Ids: 4003192102001104, 400C192102001104, 6003192102001104, 600C192102001104, 6003192102011104, 600C192102011104, 6003192102021104, 600C192102021104, 6003192102031104, 600C192102031104
TransmissionMode: DDR&TX2
FlashID0: 0000 0000  - 0000 0000 [unused/removed] type: NOR,CMT 
FlashID1: 0000 0001  - 0000 0000 [unused/removed] type: NOR,CMT 
 Algorithm: RAPUv11_XSR17_alg.fg [XSR 1.6]  version: 9.50.0 revision: 3.0 size: 0x7F29B
 Supported Ids: 4003192102001104, 400C192102001104, 6003192102001104, 600C192102001104, 6003192102011104, 600C192102011104, 6003192102021104, 600C192102021104, 6003192102031104, 600C192102031104
TransmissionMode: DDR&TX2
CMT PAPUBKEYS HASH: 95A68E9FA27B2BFA89EA204FC846EB73DEF1D93F
Up****** CMT  NPC ...OK
Up****** CMT  CCC ...OK
Up****** CMT  HWC ...OK
  Тесты ССС и HWC проходят:
	Код:
	CMT PAPUBKEYS HASH: 95A68E9FA27B2BFA89EA204FC846EB73DEF1D93F
Reading CMT NPC  (0x190 bytes)
Original Product Code: 059B662
Reading CMT VARIANT  (0x0 bytes)
Reading CMT CCC  (0x178 bytes)
 Product Code: 059B662
CCC seems to be valid
Reading CMT HWC  (0xD4 bytes)
 Product Code: 059B662
HWC seems to be valid
  SX4 авторизация проходит на нескольких продуктах BEST, ATF, MT, MXKey 1 и 309 поля записываются;
MT 
	Код:
	busy, waiting...
PMM Authorize SUCCESSFULL
PMM Send File
Operation Completed
 BEST
	Код:
	Processing Server SX4 Auth
Checking SDD key...
Check SD : Key is Ok
Operating mode is OK, no need change...
Connecting to server...
Connect to server Ok, checking
SX4 Server : Online, Ready
SX4, processing Step #1
SX4, processing Step #2
SX4, processing Step #3
SX4 Result : Ok
Uploading RF/Battery tune to phone...
Using : RM-675.pm
Operating mode is OK, no need change...
Field 1
   Record 0 write - Ok
   Record 1 write - Ok
   Record 2 write - Ok
   Record 4 write - Ok
   Record 6 write - Ok
   Record 7 write - Ok
   Record 8 write - Ok
   Record 13 write - Ok
   Record 15 write - Ok
   Record 16 write - Ok
   Record 17 write - Ok
   Record 18 write - Ok
   Record 19 write - Ok
   Record 22 write - Ok
   Record 26 write - Ok
   Record 27 write - Ok
   Record 28 write - Ok
   Record 29 write - Ok
   Record 30 write - Ok
   Record 31 write - Ok
   Record 32 write - Ok
   Record 33 write - Ok
   Record 35 write - Ok
   Record 36 write - Ok
   Record 38 write - Ok
   Record 39 write - Ok
   Record 40 write - Ok
   Record 41 write - Ok
   Record 43 write - Ok
   Record 44 write - Ok
   Record 45 write - Ok
Field 2
   Record 0 write - Ok
Field 309
   Record 0 write - Ok
   Record 1 write - Ok
   Record 2 write - Ok
   Record 3 write - Ok
   Record 4 write - Ok
   Record 7 write - Ok
   Record 17 write - Ok
Field 382
   Record 1 write - Ok
Check ST_SECURITY now...
Security status : ST_SECURITY => DAMAGED :(
 MXKey
	Код:
	Connecting to server[main.mxkey.biz] ...MXKEY SX4CARD - ID, hello 194.176.111.227
SUPERDONGLE authorized :)!
Writing PM from Node ...
Section: 1
 - Key: 0, size 10 bytes written.
 - Key: 1, size 94 bytes written.
 - Key: 2, size 110 bytes written.
 - Key: 4, size 10 bytes written.
 - Key: 6, size 110 bytes written.
 - Key: 7, size 450 bytes written.
 - Key: 8, size 10 bytes written.
 - Key: 13, size 110 bytes written.
 - Key: 15, size 30 bytes written.
 - Key: 16, size 30 bytes written.
 - Key: 17, size 30 bytes written.
 - Key: 18, size 30 bytes written.
 - Key: 19, size 30 bytes written.
 - Key: 22, size 24 bytes written.
 - Key: 26, size 10 bytes written.
 - Key: 27, size 36 bytes written.
 - Key: 28, size 110 bytes written.
 - Key: 29, size 10 bytes written.
 - Key: 30, size 36 bytes written.
 - Key: 31, size 24 bytes written.
 - Key: 32, size 216 bytes written.
 - Key: 33, size 36 bytes written.
 - Key: 35, size 24 bytes written.
 - Key: 36, size 24 bytes written.
 - Key: 38, size 216 bytes written.
 - Key: 39, size 36 bytes written.
 - Key: 40, size 24 bytes written.
 - Key: 41, size 216 bytes written.
 - Key: 43, size 36 bytes written.
 - Key: 44, size 216 bytes written.
 - Key: 45, size 216 bytes written.
Section: 2
 - Key: 0, size 2240 bytes written.
Section: 4
 - Key: 1, size 200 bytes written.
 - Key: 3, size 10 bytes written.
 - Key: 4, size 8 bytes written.
 - Key: 5, size 8 bytes written.
 - Key: 6, size 8 bytes written.
 - Key: 9, size 5 bytes written.
 - Key: 28, size 2 bytes written.
Section: 8
 - Key: 0, size 2 bytes written.
 - Key: 1, size 16 bytes written.
 - Key: 2, size 16 bytes written.
 - Key: 3, size 128 bytes written.
 - Key: 4, size 128 bytes written.
 - Key: 8, size 8 bytes written.
 - Key: 9, size 8 bytes written.
 - Key: 10, size 32 bytes written.
 - Key: 11, size 4 bytes written.
 - Key: 12, size 4 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 1059 bytes written.
Section: 12
 - Key: 0, size 8 bytes written.
Section: 26
 - Key: 0, size 16 bytes written.
 - Key: 1, size 68 bytes written.
Section: 31
 - Key: 4, size 16 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.
Section: 96
 - Key: 0, size 2 bytes written.
 - Key: 1, size 20 bytes written.
Section: 107
 - Key: 26, size 12 bytes written.
Section: 117
 - Key: 5, size 10 bytes written.
 - Key: 6, size 8 bytes written.
 - Key: 8, size 42 bytes written.
Section: 122
 - Key: 0, size 2 bytes written.
Section: 153
 - Key: 0, size 68 bytes written.
 - Key: 1, size 68 bytes written.
 - Key: 2, size 68 bytes written.
 - Key: 3, size 68 bytes written.
 - Key: 4, size 68 bytes written.
 - Key: 5, size 68 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.
Section: 212
 - Key: 1, size 4 bytes written.
Section: 217
 - Key: 0, size 32 bytes written.
Section: 239
 - Key: 6, size 218 bytes written.
Section: 291
 - Key: 0, size 92 bytes written.
Section: 309
 - Key: 0, size 4 bytes written.
 - Key: 1, size 2 bytes written.
 - Key: 2, size 12 bytes written.
 - Key: 3, size 36 bytes written.
 - Key: 4, size 12 bytes written.
 - Key: 7, size 12 bytes written.
 - Key: 17, size 12 bytes written.
Section: 313
 - Key: 0, size 800 bytes written.
Section: 322
 - Key: 0, size 1 bytes written.
Section: 327
 - Key: 0, size 2 bytes written.
Section: 329
 - Key: 0, size 8392 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 4516 bytes written.
 - Key: 10, size 4 bytes written.
 - Key: 11, size 1972 bytes written.
Section: 354
 - Key: 0, size 13 bytes written.
Section: 356
 - Key: 0, size 2 bytes written.
Section: 360
 - Key: 0, size 1 bytes written.
 - Key: 1, size 2 bytes written.
Section: 369
 - Key: 0, size 40 bytes written.
Section: 395
 - Key: 0, size 16 bytes written.
Completed in 10.234 s
 Но по прежнему:
	Код:
	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!
 У меня все идеи закончились.
Если стереть NPC, то телефон прекрасно работает.