Mx key giving me more problems than pkey

[LOCKED4EVER]

Pleaseeeee help


why does my MXKEY not pickup my 6230 i get this message at the end Performing Flash Authentication and it stops there, goes no further ?

i use PKEY and same cables and PKEY picks it up, have look below....



BUS chek MXKEY.......................

Using device: J.A.F, FW ver: 01.B1
Library version: 1.0.0.11893, Date: 26-01-2010
ASIC ID: 0x1052 [TikuEdge ver: 1.1]
SecondaryBoot: te_2nd.fia [TIKU BT2] version: 4.76.0 revision: 0.7 size: 0x2398
Supported Ids: 1051, 1052, 2051
FlashID0: 00EC 22F8 [Samsung K8S2815ETA,128 Mbits] page size: 64 K type: NOR area: 00000000-00FFFFFF
FlashID1: 00EC 0039 [Samsung KEE00E00CM Eija NAND,64 Mbits] type: NAND hw: EIJA(E)
FlashID2: 0000 0001 [unused/removed]
FlashID3: 0000 0001 [unused/removed]
ExtBUSC: 0000 0000 18F0 9FE5 18F0 9FE5 18F0 9FE5
Algorithm: te_essr.fia [TIKU EIJA SSR] version: 4.76.0 revision: 0.7 size: 0x9868
Supported Ids: 1051, 1052, 2051
Performing Flash Authentication ...









PKEY.................


MCU ID: 0x1052
FLASH ID0: 22F800EC <=> SAMSUNG (SEC) -> Type not in database Addr0: 0x00000000 - 0x00FFFFFF, SectorSize0: 10
FLASH ID1: 003900EC <=> SAMSUNG (SEC) -> Type not in database Addr1: 0x02000000 - 0x02FFFFFF, SectorSize1: 9
FLASH ID2: 00010000 <=> Flash -> not used Addr2: 0x04000000 - 0x04FFFFFF, SectorSize2: 0
FLASH ID3: 00010000 <=> Flash -> not used Addr3: 0x06000000 - 0x06FFFFFF, SectorSize3: 0
First 16 bytes: 00 00 00 00 18 F0 9F E5 18 F0 9F E5 18 F0 9F E5
Checking RAM for ALGO...
Algo is ready...
Checking FAID calculation...
P-key nokia module version 01.02
Done!
Phone Restarted...

[LOCKED4EVER]

anyoneeeeeeeeeeeeeeeeeeeeeeee

[delower10]

Performing Flash Authentication ...


Yes bro this problem coming from cable connection

[LOCKED4EVER]

Originally Posted by delower10

Performing Flash Authentication ...


Yes bro this problem coming from cable connection

Very much doubt this is a cable problem as cable works with PKEY. Evidence of this is above.

My guess is iv bought mxkey to early and should have bought the mt-box (when pkey support stopped) as mx key is still a new born baby and the only way problems are gona be fixed with mxkey is by people reporting problems.

[GSM-Telecom]

Originally Posted by LOCKED4EVER

Very much doubt this is a cable problem as cable works with PKEY. Evidence of this is above.

My guess is iv bought mxkey to early and should have bought the mt-box (when pkey support stopped) as mx key is still a new born baby and the only way problems are gona be fixed with mxkey is by people reporting problems.

I agree, it has nothing to do with cable issues as I have 3 different 6230 cables & they all fail with the same error you are having on MXkey, no problem flashing with JAF, it seems like the mods of this product are aware of the problem but do nothing about it, DCT4 handsets are still big here in the UK, MX team have now released Blackberry unlocking BEFORE they have solved problems with the Nokia tool.

[MANOLE]

Originally Posted by LOCKED4EVER

Very much doubt this is a cable problem as cable works with PKEY. Evidence of this is above.

My guess is iv bought mxkey to early and should have bought the mt-box (when pkey support stopped) as mx key is still a new born baby and the only way problems are gona be fixed with mxkey is by people reporting problems.

You have bought MXKEY because was cheap and you can make lots of
money with it.

Then go and buy mtbox, no one stop you, and be happy with their system
of credits, special system for rob you of much money possible.

We are aware of MXKEY bugs, they will be fixed. We do not consider them
so important since you can make same job with free jaf software.

BR,
Manole