mx.key kill 2 hp today ,,,,,,,,,

[cahdesa]

mx.key version 1.8 has killed 2 hp today, why? victims were 5300 and 5130 ,,,,,

5130
1ST BOOT : C0,07 [Rm-495] [2.0.8.5]
RAPx ID : 000000010000022600010006030C192101033000
EM 1 ID : 00000296
EM 2 ID : 00000B22
RAPx PBID : 27B0000D20497F563957DB5168E08FC5DE2E4B54
RAPx MODE : 00
RAPx HASH : 9DDBFCFE6E73CED7D8C6268C8EB85723
RAPx ROID : 273F6D55DFAAF68F
CMT 1ST Boot OK
CMT 2ND Bt: RAP3Gv3_2nd.fg, Ver: 9.11.1
CMT FLID0 : 00898982-00008A31, Int NU48F512
CMT FLCNT : 00000000000000000000000000000000000000
CMT MCID0 : FFFF0000-00000000
CMT 2ND Boot OK
CMT ALGO : RAP3Gv3_algo_v1331.fg, Ver: 1.33.1
CMT KSIG0 : 0C917F11196FDB7378C18EF7260698CA4489DCA0
CMT VPP : Internal
DUAL LINE : True
CMT ALG Boot OK
IMAGE : rm495__06.65.mcusw
CMT NOR Erase Area: 0x00000000-000006BF
CMT NOR Erase Area: 0x000006C0-0001FFFF
CMT NOR Erase Area: 0x00040000-000BFFFF
CMT NOR Erase Area: 0x000C0000-0013FFFF
CMT NOR Erase Area: 0x00140000-0137FFFF
CMT NOR Erase Area: 0x01380000-0151FFFF
CMT FLASH ERASE OK, Time: 00:34
DATA_MISMATCH: RX2 Pin not Connected, or Used 5 Pin Cable !
DATA_MISMATCH: RX2 Pin not Connected, or Used 5 Pin Cable !
DATA_BLK_ERROR at: 0x00660400, 03
ERR: CMT FLASH WRITE D_BLK C7012D0103CD000010000000F172, LN: 0x004000, Time: 00:59
Process Failed, Repowering Mobile


5300
1ST BOOT : C0,07 [Rm-146] [2.0.8.5]
RAPx ID : 000000010000022600010006010C192101001101
EM 1 ID : 00000232
EM 2 ID : 00000353
RAPx PBID : 2450000FA64500586931402AD9EF77212C0B30F6
RAPx MODE : 00
RAPx HASH : BAF3A9C3DBFA8454937DB77F2B8852B1
RAPx ROID : 191EC665DFAAF68F
CMT 1ST Boot OK
CMT 2ND Bt: RAP3Gv3_2nd.fg, Ver: 9.11.1
CMT FLID0 : 00EC22FE-00006921, Sam K8S5615ETA
CMT FLCNT : 0000000000FFFFFFFFFFFFFFFFFFFFFFFFFFFF
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 : rm146__07.20.mcusw
CMT NOR Erase Area: 0x00000000-000006BF
CMT NOR Erase Area: 0x000006C0-0001FFFF
CMT NOR Erase Area: 0x00020000-0007FFFF
CMT NOR Erase Area: 0x00080000-000DFFFF
CMT NOR Erase Area: 0x00100000-001FFFFF
CMT NOR Erase Area: 0x00200000-0031FFFF
CMT NOR Erase Area: 0x00320000-0105FFFF
CMT NOR Erase Area: 0x01060000-01067FFF
CMT NOR Erase Area: 0x01068000-0107FFFF
CMT FLASH ERASE OK, Time: 00:05
DATA_MISMATCH: RX2 Pin not Connected, or Used 5 Pin Cable !
DATA_BLK_ERROR at: 0x00020000, 03
ERR: CMT FLASH WRITE D_BLK C7012D0103CD000010000000F172, LN: 0x000280, Time: 00:10
Process Failed, Repowering Mobile

[Riteshgpt60]

And where is the logs Of MX.
Your Cable is the Killer not by mx
And the solution is already Given by HWK--

DATA_MISMATCH: RX2 Pin not Connected, or Used 5 Pin Cable !

[cahdesa]

sorry logged on using this HWK log using mx.key ,,,,,,,



sing device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.8009(15-04-2010), 1.0.0.12756(15-04-2010)
Processing file: rm495__07.91.mcusw as MCU
[BB5,BB5 ALGORITHM] size: 18.20 MB
Supported RAP Ids: 010C192101013000, 0103192101003000, 0303192101033000, 030C192101033000
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000296
EM1 ID: 00000B22
PUBLIC ID: 27B0000D20497F563957DB5168E08FC5DE2E4B54
ASIC MODE ID: 00
ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
Supported RAP Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
FlashID0: 0089 8982 - 0000 0000 [Intel NU48F512,512 Mbits] type: NOR,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
TransmissionMode: 16Bit
Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0
Supported RAP 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
RAP PAPUBKEYS HASH: 0C917F11196FDB7378C18EF7260698CA4489DCA0
Storing certificate ...OK
Erase size: 21.00 MB
CMT NOR area [00000000-000006BF] erased in 0.563 s
CMT NOR area [000006C0-0001FFFF] erased in 0.187 s
CMT NOR area [00040000-000BFFFF] erased in 2.203 s
CMT NOR area [000C0000-0013FFFF] erased in 0.234 s
CMT NOR area [00140000-0137FFFF] erasing ...
Aborting operation ...
Error while erasing 02 area 0x00140000-0x0137FFFF, Result: B3720000000000 , 51
Flashing terminated with error(s) in 39.640 s
RX Buffer: B372

[cahdesa]

Originally Posted by Riteshgpt60

And where is the logs Of MX.
Your Cable is the Killer not by mx
And the solution is already Given by HWK--

I have been using the 5 pin on the results remained nil HWK ,,,,,

[cahdesa]

sorry you had one post,,, my first flash and then I try mx.key pake pake HWK and results as above

[curvenger]

Originally Posted by cahdesa

I have been using the 5 pin on the results remained nil HWK ,,,,,

Bro that is what the log said, u have used 5 pin cable. So use 7 pin cable and try again, your problem will be solved.

[MOBILECHANNEL]

I also faced this problem killed 5130,n82,3110c these model phone after flash dead with mx key again i flash with jaf problem solve what happened to mx newest version

[faurionutz]

I've killed an 5610 with new version using ufs, with new loader and tried with old loaders too but same problem. Jaf box is dead, so I can see if there are same results

[digitalgsm_cora]

Post your log brother those are just words in the wind....

B.R.

[gustiputra]

if you use mxkey beter use usb for flashsing

[bolutic]

Originally Posted by faurionutz

I've killed an 5610 with new version using ufs, with new loader and tried with old loaders too but same problem. Jaf box is dead, so I can see if there are same results

[SIZE=5]pls take note ufs can not flash bb5 phones like jaf box so use usb to flash bb5 phones.4 me to flash any bb5 phone with mx-key i use usb 100% ok if phone do not have hardware problem.search 4 nokia usb driver install it once u do dat u can flash any bb5 with usb cable.u can do security code of x3 and x6 with usb cable.using mx-key.even i will say usb flashing is good with mx-key.use usb cable b/4 mx key do her own interface

[faurionutz]

Thanks for advices, problem already solved by phoenix. What really matters from this post is that mxkey has bugs flashing bb5 and dct4, is not a safe tool with fbus flashing, so Alim must work at this to fix this bugs

[cahdesa]

thanks for the advice from the master of all nokia 5300 IMEI so oooooooo.........

[jawi]

I don't blve u.. Ur bully man

[ferdie1969]

yes big bug in 1.8 is a phone killer.after flash either phone not responding or rx buffer. i hope alim fix it n that forever problem with dct4 mostly ram problem.instead of always adding more stuff with mx key fix bug first