6120c simlock invalid NOT repair by 3.5 rev 1.5 - GSM-Forum

rico_deep · 11-21-2011, 11:57

please

SIMLOCK_DATA corrupted!
SIMLOCK_DATA corrupted!
MXKEY [MxKey Team HTI Flasher Interface (WinUSB) 4], SN: xxxxxxxxxx
Using device: HTI, FW ver: 00.24, SN: xxxxxxxxx
Connection status: UHCI:HUB:USB 2.00 (Full-speed)
Driver: WinUSB, ver: 3.5.0.0
Module ver: 1.0.0.19228(10-11-2011), Library ver: 1.0.0.13150(10-11-2011)

Phone type: RM-243 (Nokia 6120)
SW version: V 05.11 21-04-08 RM-243 (c) Nokia
ApeCoreSw: 05.11

SYSTEM ASIC ID: 000000010000022600010006400C192101021103 [RAPIDO3G ver: 1.11]
ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
ROM ID: A8C1D6713E691FF8
SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 11.10.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
ERROR: Sec. data error !
Try using USB connection.

Reading Simlock info ...
SIMLOCK_DATA corrupted!
SIMLOCK_DATA corrupted!

net.tarik · 11-21-2011, 12:47

eBB5ProtocolType: NEW

Try using USB connection.

dear try it and post result.

BR

rico_deep · 11-21-2011, 12:54

Quote:

Originally Posted by net.tarik

eBB5ProtocolType: NEW

Try using USB connection.

dear try it and post result.

BR

hehehehehe Not supported interface if i use USB..

Royslade · 11-21-2011, 13:20

Try it with simlock.bin file.

BR roy

Tarikul Islam · 11-21-2011, 13:56

Quote:

Originally Posted by net.tarik

eBB5ProtocolType: NEW

Try using USB connection.

dear try it and post result.

BR

I think new bug of new update.
Same here.
i face this problem also.

maremestera · 11-22-2011, 01:21

same problem. See log:

Code:

MXKEY [MxKey Team HTI Flasher Interface (WinUSB) 3], SN: xxxxxxxx
Using device: HTI, FW ver: 00.24, SN: 0000xxxx
Connection status: UHCI:HUB:USB 2.00 (Full-speed)
Driver: WinUSB, ver: 3.5.0.0 
Module ver: 1.0.0.19228(10-11-2011), Library ver: 1.0.0.13150(10-11-2011)
 
Phone type: RM-243 (Nokia 6120)
SW version: V 07.20 05-10-09 RM-243 (c) Nokia 
ApeCoreSw: 07.20
 
SYSTEM ASIC ID: 000000010000022600010006400C192101021103 [RAPIDO3G ver: 1.11]
ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
ROM ID: A8C1D6713E691FF8
 SecondaryBoot: RAPIDOv11_2nd.fg [BB5]  version: 11.10.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
ERROR: Sec. data error !
Try using USB connection.
 
Reading Simlock info ...
SIMLOCK_DATA corrupted!
SIMLOCK_DATA corrupted!

yolem053 · 11-22-2011, 01:51

you have to buy HTI II by MANOLE again!!! heehehhehehe

phucmobilemh · 11-22-2011, 01:51

not supported repair simlock sl3 waiting please

maremestera · 11-22-2011, 02:08

REzolved by simply using mxkey 3.5_1.3

rico_deep · 11-22-2011, 03:11

Quote:

Originally Posted by phucmobilemh

not supported repair simlock sl3 waiting please

READ LOGs before replying to a thread......

Quote:

ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE

is this SL3 to you???

Quote:

REzolved by simply using mxkey 3.5_1.3

meaning............It's a BUG...

pls. fix the BUG

rico_deep · 11-22-2011, 06:35

Done.........SD repair and simlock repair.. via 3.5rev1.2

Quote:

MXKEY Serial: [MxKey Team HTI Flasher Interface (WinUSB) 4] -
Using device: HTI BOX, FW ver: 00.24
Driver: uhci:hub:ccgp:WinUSB, ver: 3.5.0.0
Module ver: 1.0.0.17743(23-06-2011), Library ver: 1.0.0.11773(23-06-2011)

Product: V 05.11 21-04-08 RM-243 (c) Nokia
ApeCoreSw: 05.11

Using cached productData.
PUBLIC ID: 141001142A730052CCBE098935B2E90758AE43A8
PRIVATE ID: EFFFED90A04571A3C5E58CF7B4323A2F97675010
Updating SUPERDONGLE_KEY ...OK
Authenticating to SUPERDONGLE ...
SUPERDONGLE authorized

!
Phone authenticated to SUPERDONGLE already.

[UnauthorizedFault] Application outdated, please get an update from MXKEY !
Phone authenticated to SUPERDONGLE already.
Writing PM from Node ...
Section: 1
- Key: 0, size 114 bytes written.
- Key: 1, size 4 bytes written.
- Key: 2, size 98 bytes written.
- Key: 4, size 110 bytes written.
- Key: 5, size 4 bytes written.
- Key: 6, size 98 bytes written.
- Key: 8, size 110 bytes written.
- Key: 13, size 98 bytes written.
- Key: 15, size 4 bytes written.
- Key: 16, size 98 bytes written.
- Key: 18, size 98 bytes written.
- Key: 20, size 98 bytes written.
- Key: 22, size 16 bytes written.
- Key: 23, size 4 bytes written.
- Key: 24, size 84 bytes written.
- Key: 25, size 4 bytes written.
- Key: 26, size 110 bytes written.
- Key: 27, size 4 bytes written.
- Key: 28, size 98 bytes written.
- Key: 29, size 10 bytes written.
- Key: 31, size 98 bytes written.
- Key: 33, size 36 bytes written.
- Key: 34, size 80 bytes written.
- Key: 40, size 16 bytes written.
- Key: 41, size 182 bytes written.
- Key: 42, size 4 bytes written.
- Key: 43, size 36 bytes written.
- Key: 44, size 182 bytes written.
- Key: 46, size 64 bytes written.
Section: 2
- Key: 0, size 440 bytes written.
Section: 4
- Key: 1, size 1020 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: 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 1 bytes written.
- Key: 5, size 6 bytes written.
- Key: 6, size 1 bytes written.
- Key: 7, size 2 bytes written.
- Key: 8, size 2 bytes written.
- Key: 9, size 2 bytes written.
- Key: 10, size 2 bytes written.
- Key: 11, size 2 bytes written.
- Key: 12, size 1 bytes written.
- Key: 13, size 1 bytes written.
- Key: 14, size 1 bytes written.
- Key: 15, size 1 bytes written.
- Key: 16, size 1 bytes written.
- Key: 17, size 1 bytes written.
- Key: 18, size 1 bytes written.
- Key: 19, size 2 bytes written.
- Key: 20, size 2 bytes written.
- Key: 21, size 1 bytes written.
- Key: 22, size 1 bytes written.
- Key: 23, size 4 bytes written.
- Key: 24, size 4 bytes written.
- Key: 25, size 2 bytes written.
- Key: 26, size 2 bytes written.
- Key: 27, size 2 bytes written.
- Key: 28, size 2 bytes written.
- Key: 29, size 1 bytes written.
- Key: 30, size 1 bytes written.
- Key: 31, size 1 bytes written.
- Key: 32, size 1 bytes written.
- Key: 33, size 1 bytes written.
- Key: 34, size 1 bytes written.
- Key: 35, size 1 bytes written.
- Key: 36, size 1 bytes written.
- Key: 37, size 1 bytes written.
- Key: 38, size 2 bytes written.
- Key: 39, size 2 bytes written.
- Key: 40, size 2 bytes written.
- Key: 41, size 2 bytes written.
- Key: 42, size 2 bytes written.
- Key: 43, size 4 bytes written.
- Key: 44, size 4 bytes written.
- Key: 45, size 4 bytes written.
- Key: 46, size 1 bytes written.
- Key: 47, size 16 bytes written.
- Key: 48, size 2 bytes written.
- Key: 49, size 2 bytes written.
- Key: 50, size 20 bytes written.
- Key: 51, size 10 bytes written.
- Key: 52, size 2 bytes written.
- Key: 53, size 20 bytes written.
- Key: 54, size 10 bytes written.
- Key: 55, size 1 bytes written.
- Key: 56, size 1 bytes written.
- Key: 57, size 1 bytes written.
- Key: 58, size 1 bytes written.
- Key: 59, size 1 bytes written.
- Key: 60, size 1 bytes written.
- Key: 61, size 1 bytes written.
- Key: 62, size 1 bytes written.
- Key: 63, size 1 bytes written.
- Key: 64, size 1 bytes written.
- Key: 65, size 1 bytes written.
- Key: 66, size 32 bytes written.
- Key: 67, size 32 bytes written.
- Key: 68, size 2 bytes written.
- Key: 69, size 2 bytes written.
- Key: 70, size 2 bytes written.
- Key: 71, size 2 bytes written.
- Key: 72, size 2 bytes written.
- Key: 73, size 2 bytes written.
- Key: 74, size 2 bytes written.
- Key: 75, size 2 bytes written.
- Key: 76, size 2 bytes written.
- Key: 77, size 2 bytes written.
- Key: 78, size 2 bytes written.
- Key: 79, size 2 bytes written.
- Key: 80, size 2 bytes written.
- Key: 81, size 2 bytes written.
- Key: 82, size 2 bytes written.
- Key: 83, size 2 bytes written.
- Key: 84, size 2 bytes written.
- Key: 85, size 2 bytes written.
- Key: 86, size 2 bytes written.
- Key: 87, size 2 bytes written.
- Key: 88, size 2 bytes written.
- Key: 89, size 2 bytes written.
- Key: 90, size 2 bytes written.
- Key: 91, size 2 bytes written.
- Key: 92, size 2 bytes written.
- Key: 93, size 2 bytes written.
- Key: 94, size 2 bytes written.
- Key: 95, size 2 bytes written.
- Key: 96, size 2 bytes written.
- Key: 97, size 2 bytes written.
- Key: 98, size 2 bytes written.
- Key: 99, size 2 bytes written.
- Key: 100, size 2 bytes written.
- Key: 101, size 2 bytes written.
- Key: 102, size 2 bytes written.
- Key: 103, size 2 bytes written.
- Key: 104, size 2 bytes written.
- Key: 105, size 2 bytes written.
- Key: 106, size 2 bytes written.
- Key: 107, size 2 bytes written.
- Key: 108, size 2 bytes written.
- Key: 109, size 2 bytes written.
- Key: 110, size 2 bytes written.
- Key: 111, size 2 bytes written.
- Key: 112, size 2 bytes written.
- Key: 113, size 2 bytes written.
- Key: 114, size 2 bytes written.
- Key: 115, size 2 bytes written.
- Key: 116, size 4 bytes written.
- Key: 117, size 4 bytes written.
- Key: 118, size 1 bytes written.
- Key: 119, size 4 bytes written.
- Key: 120, size 4 bytes written.
- Key: 121, size 4 bytes written.
- Key: 122, size 4 bytes written.
- Key: 123, size 16 bytes written.
- Key: 124, size 4 bytes written.
- Key: 125, size 2 bytes written.
- Key: 126, size 2 bytes written.
- Key: 127, size 1437 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: 31
- Key: 4, size 20 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.
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: 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: 9, size 64 bytes written.
Section: 208
- Key: 1, size 4 bytes written.
Section: 217
- Key: 0, size 32 bytes written.
Section: 309
- Key: 0, size 4 bytes written.
- Key: 1, size 2 bytes written.
- Key: 2, size 12 bytes written.
- Key: 4, size 12 bytes written.
- Key: 5, size 12 bytes written.
- Key: 7, size 12 bytes written.
- Key: 8, size 12 bytes written.
- Key: 17, size 12 bytes written.
Section: 322
- Key: 0, size 1 bytes written.
Section: 354
- Key: 0, size 13 bytes written.
Section: 356
- Key: 0, size 2 bytes written.
Completed in 15.532 s

buscheck

Quote:

MXKEY Serial: [MxKey Team HTI Flasher Interface (WinUSB) 4] -
Using device: HTI BOX, FW ver: 00.24
Driver: uhci:hub:ccgp:WinUSB, ver: 3.5.0.0
Module ver: 1.0.0.17743(23-06-2011), Library ver: 1.0.0.11773(23-06-2011)
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006400C192101021103 [RAPIDO3G ver: 1.11]
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 141001142A730052CCBE098935B2E90758AE43A8
ASIC MODE ID: 00
ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
ROM ID: A8C1D6713E691FF8
SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 11.16.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
TransmissionMode: DDR&TX2
Storage0: 0000 0000 - 0000 0000 type: RAM, asic:CMT
Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT
Storage2: 0400 0000 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT
Storage3: 0000 0001 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT
Storage4: 00EC 0030 - 0000 0221 [Samsung K5W1G13ACM-DJ60,1 Gbits] type: FLASH,MuxOneNAND, asic:CMT
Suggested algorithm: XSR 1.5
Algorithm: RAPIDOv11_XSR15_alg.fg [XSR 1.5] version: 11.16.0 revision: 2.0 size: 0x878E8
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: 0FE1BA92D924A658E4800780FA6F4868100AC947
Original Imei: 35571202332011
Original Product code: 0554021
Bluetooth ID: 0022FC6D3BA6
SIMLOCK PA identifier:
[0] PA_SL2

Phone Type: RM-243 (Nokia 6120)
SW Version: V 05.11 21-04-08 RM-243 (c) Nokia
Imei plain: 35571202332011-3
Product Code: 0552203
Battery voltage: 4473 mV, current: 9 mA
Language Pack:
- not available.

SIMLOCK seems to be valid
SUPERDONGLE_KEY[MX] seems to be valid
SECURITY_TEST passed

Imei net: 355712023320113
Version: SIMLOCK SERVER
Provider: Globe Telecom , Country: Philippines
Counter: 0/3, 0/10

CONFIG_DATA: 5150200000000000
PROFILE_BITS: 0000000000000000

BLOCK1: 1=OPEN
BLOCK2: 1=OPEN

Pls. Fix 3.5rev1.5 version

Quote:

eBB5ProtocolType: NEW
ERROR: Sec. data error !
Try using USB connection.

thanks

shamzil · 11-22-2011, 11:42

Me too have the same problem

adnon · 12-17-2011, 05:57

Now 6120c bugs fixed in latest version 3.5 rev 1.6. I did full service my 6120c and working fine...

11-21-2011, 11:57	#1 (permalink)
rico_deep No Life Poster Join Date: Jul 2005 Location: philippine Posts: 1,113 Member: 159757 Status: Offline Thanks Meter: 461	6120c simlock invalid NOT repair by 3.5 rev 1.5 please SIMLOCK_DATA corrupted! SIMLOCK_DATA corrupted! MXKEY [MxKey Team HTI Flasher Interface (WinUSB) 4], SN: xxxxxxxxxx Using device: HTI, FW ver: 00.24, SN: xxxxxxxxx Connection status: UHCI:HUB:USB 2.00 (Full-speed) Driver: WinUSB, ver: 3.5.0.0 Module ver: 1.0.0.19228(10-11-2011), Library ver: 1.0.0.13150(10-11-2011) Phone type: RM-243 (Nokia 6120) SW version: V 05.11 21-04-08 RM-243 (c) Nokia ApeCoreSw: 05.11 SYSTEM ASIC ID: 000000010000022600010006400C192101021103 [RAPIDO3G ver: 1.11] ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE ROM ID: A8C1D6713E691FF8 SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 11.10.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 ERROR: Sec. data error ! Try using USB connection. Reading Simlock info ... SIMLOCK_DATA corrupted! SIMLOCK_DATA corrupted!

11-22-2011, 02:08	#9 (permalink)
maremestera No Life Poster Join Date: Jan 2008 Location: Roumania Posts: 1,137 Member: 691388 Status: Offline Thanks Meter: 371	6120c vs mxkey 3.5rev 1.5 REzolved by simply using mxkey 3.5_1.3

11-22-2011, 11:42	#12 (permalink)
shamzil Freak Poster Join Date: Jul 2005 Location: Sri Lanka Posts: 275 Member: 164422 Status: Offline Thanks Meter: 24	Same here Me too have the same problem

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Need software upgrade for Nokia 5110	ptkrf	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	30	02-24-2016 10:21
DES key Driver	black	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	8	02-08-2014 04:50
8810 mbus-cable	zfrank	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	2	05-19-1999 13:12

11-21-2011, 12:47	#2 (permalink)
net.tarik No Life Poster Join Date: Jun 2010 Location: Green Forest Posts: 1,125 Member: 1316000 Status: Offline Sonork: 100.1624093 Thanks Meter: 348	eBB5ProtocolType: NEW Try using USB connection. dear try it and post result. BR

11-21-2011, 13:20	#4 (permalink)
Royslade No Life Poster Join Date: Aug 2002 Age: 57 Posts: 769 Member: 14515 Status: Offline Sonork: 100.77248 Thanks Meter: 15	Try it with simlock.bin file. BR roy

11-22-2011, 01:51	#7 (permalink)
yolem053 Freak Poster Join Date: Jan 2006 Location: Maniki Kapalong Norht Davao Posts: 336 Member: 227348 Status: Offline Sonork: yolem053 Thanks Meter: 44	you have to buy HTI II by MANOLE again!!! heehehhehehe

11-22-2011, 01:51	#8 (permalink)
phucmobilemh Crazy Poster Join Date: May 2010 Posts: 59 Member: 1302415 Status: Offline Thanks Meter: 8	not supported repair simlock sl3 waiting please

12-17-2011, 05:57	#13 (permalink)
adnon No Life Poster Join Date: Jan 2008 Location: Pakistan Posts: 1,623 Member: 682736 Status: Offline Thanks Meter: 457	Now 6120c bugs fixed in latest version 3.5 rev 1.6. I did full service my 6120c and working fine...