GSM-Forum - MXKEY / MXBOX v3.5 revision 1.1 discussion thread (STANDALONE Nokia and Blackberry)

GSM-Forum (https://forum.gsmhosting.com/vbb/)

- MXKEY Nokia Flasher and Unlocker (by Alim Hape) (https://forum.gsmhosting.com/vbb/f550/)

- - MXKEY / MXBOX v3.5 revision 1.1 discussion thread (STANDALONE Nokia and Blackberry) (https://forum.gsmhosting.com/vbb/f550/mxkey-mxbox-v3-5-revision-1-1-discussion-thread-standalone-nokia-blackberry-1287713/)

is not working....i update it but whent i want to start.it goes in error

mr.Manole

Where the answers?
This is a forum thread about MXbox?
Tell me when I can possibility correcting this phones

http://forum.gsmhosting.com/vbb/f550...r-sdd-1289039/

Everything installed at first try without any problems. MX v3.5 revision 1.1 work very good with HTI and finally standalone sl3 code calculating, thats nice ;) sl3 reading hash bugs disappear.
UFS work also good as interface.
5+

Br.

I am using ver 3.5 rev 1.1 (not upgraded partially yet)

phone: 5300 rm-146 shows contact service

want to try standalone :D

scan log:

Quote:

Phone Type: RM-146 (Nokia 5300)
SW Version: V 07.20 23-10-08 RM-146 (c) Nokia.
Imei plain: 35309502768787-3
Product Code: 0536680
Battery voltage: 4904 mV, current: 17 mA
Language Pack:
- not available.

SIMLOCK seems to be valid
SUPERDONGLE_KEY[MX] seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!

Imei net: 353095027687873
Version: SIMLOCK SERVER VERSION 63
Counter: 0/3, 0/10

CONFIG_DATA: FFFFFFFFFFFFFFFF
PROFILE_BITS: FFFFFFFFFFFFFFFF

BLOCK1: 1=CLOSED(MCCMNC), DATA=00101F

repair security procedure (sx4) log (standalone) log:

Quote:

MXKEY Serial: bla bla bla
Using device: HTI BOX, FW ver: 00.17
Driver: USBUHCI:WinUSB, ver: 3.5.0.0
Module ver: 1.0.0.17602(14-06-2011), Library ver: 1.0.0.11291(14-06-2011)

Product: V 07.20 23-10-08 RM-146 (c) Nokia.

Using cached productData.
PUBLIC ID: 2120020CADDA7A56AB33D5D09713086D04D838AA
PRIVATE ID: C0D6D302CBE9EBD3875259D576152B43B9FD2A9E
E-FUSE: 025B2301
SEC ROM CRC: 40830040
SUPERDONGLE authorized :)!

lazy to search pm 1 & 309 file, so just load it from server (not standalone), log:

Quote:

SERVER->Served by MXKEY - BLADE X at host1, agent version 1.1 revision 0.7

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

scan log after repair security test:

Quote:

Phone Type: RM-146 (Nokia 5300)
SW Version: V 07.20 23-10-08 RM-146 (c) Nokia.
Imei plain: 35309502768787-3
Product Code: 0536680
Battery voltage: 4890 mV, current: 18 mA
Language Pack:
- not available.

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

Imei net: 353095027687873
Version: SIMLOCK SERVER VERSION 63
Counter: 0/3, 0/10

CONFIG_DATA: FFFFFFFFFFFFFFFF
PROFILE_BITS: FFFFFFFFFFFFFFFF

BLOCK1: 1=CLOSED(MCCMNC), DATA=00101F

unlock (standalone) log:

Quote:

Imei net: 353095027687873
Version: SIMLOCK SERVER VERSION 63
Counter: 0/3, 0/10

CONFIG_DATA: FFFFFFFFFFFFFFFF
PROFILE_BITS: FFFFFFFFFFFFFFFF

BLOCK1: 1=CLOSED(MCCMNC), DATA=00101FMXKEY Serial: bla bla bla
Using device: HTI BOX, FW ver: 00.17
Driver: USBUHCI:WinUSB, ver: 3.5.0.0
Module ver: 1.0.0.17602(14-06-2011), Library ver: 1.0.0.11291(14-06-2011)

Product: V 07.20 23-10-08 RM-146 (c) Nokia.

Using cached productData.
PUBLIC ID: 2120020CADDA7A56AB33D5D09713086D04D838AA
PRIVATE ID: C0D6D302CBE9EBD3875259D576152B43B9FD2A9E
E-FUSE: 025B2301
SEC ROM CRC: 40830040
Updating SIMLOCK...OK

Reading Simlock info ...
Imei net: 353095027687873
Version: SIMLOCK SERVER VERSION 63
Counter: 0/3, 0/10

CONFIG_DATA: 2440700000000000
PROFILE_BITS: 0000000000000000

BLOCK1: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK2: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK3: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK4: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK5: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK6: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK7: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN

forget to save the scan log after all done :D

br

btw, i got the same error too while flashing phone (5310 rm-303) but flashing done as well...

it shows: error code: 8000001F! <<< new bugs :D

the log:

Quote:

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Driver: USBUHCI:UFS2XX, ver: 3.4.16.0 , NTMP ver: 2.4.16.0
Module ver: 1.0.0.17602(14-06-2011), Library ver: 1.0.0.11291(14-06-2011)
Reading Important data ...
Reading RPL backup ...
Reading Phone IDs ...
SYSTEM ASIC ID: 000000010000022600010006010C192101013000
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: RAP3Gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 52.99 KB
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
Sending Overflow Loader(0x2E4 bytes) ...
error code: 8000001F!
Restarting phone ...
Reading Secure Storage ...
Reading SIMLOCK data ...
Reading CERT data ...
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101013000
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 11A00214AF2503545F10694114CFE827C720DB73
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
FlashID0: 0001 003F - 0000 8A21 [AMD 72NS512PD,512 Mbits] type: NOR,CMT
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
TransmissionMode: 16Bit
Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 1.40.0 revision: 0.0 size: 0x22C10
Supported 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
CMT PAPUBKEYS HASH: 3E96DE4212587183E5E16BB2C79692A53C19875D
TransmissionMode: DDR&TX2
Reading CMT NPC (0x168 bytes).
Reading CMT VARIANT (0x0 bytes).
Reading CMT CCC (0x160 bytes).
Reading CMT HWC (0xD4 bytes).
Flash Imei: 35641902891113
NPC_DATA saved OK
CCC_DATA saved OK
HWC_DATA saved OK
SIMLOCK_DATA saved OK
SIMLOCK_KEY_DATA saved OK
WMDRM_PD_DATA saved OK
RF_DATA saved OK
WARRANTY_DATA saved OK
PROD_DATA saved OK
BT_DATA saved OK
LOCK_DATA saved OK
LOCK120_DATA saved OK
BB_DATA saved OK
RPL saved to "C:\mobileEx\3.5\data\backup\BB5_35641902891113_BA CK.rpl"
Processing CNT file: rm303__10.10.image_x_blue
[BB5,BB5 ALGORITHM] page size: 128 K size: 10.64 MB
Supported Ids: 010C192101013000, 0103192101003000, 030C192101033000
NOR page size in the phone is 128 K.
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101013000
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 11A00214AF2503545F10694114CFE827C720DB73
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
FlashID0: 0001 003F - 0000 8A21 [AMD 72NS512PD,512 Mbits] type: NOR,CMT
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
TransmissionMode: 16Bit
Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 1.40.0 revision: 0.0 size: 0x22C10
Supported 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
CMT PAPUBKEYS HASH: 3E96DE4212587183E5E16BB2C79692A53C19875D
TransmissionMode: DDR&TX2
Erase size: 39.12 MB
CMT NOR area [018A0000-01B1FFFF] erased in 11.781 s

CMT NOR area [01B20000-03FBFFFF] erased in 2 min 30.969 s

Converting UCP blocks to 128 K.
Flash programming ...
Programming completed in 1 min 15.109 s
Total time for flashing process(boot+erase+write) was 4 min 24.094 s

Phone Type: RM-303 (Nokia 5310 XpressMusic)
SW Version: V 07.01 23-05-08 RM-303 (c) Nokia
Imei plain: 35641902891113-1
Product Code: 0564418
Battery voltage: 4680 mV, current: 15 mA
Language Pack:
- not available.

Imei net: 356419028911131
Version: SIMLOCK SERVER
Counter: 0/3, 0/10

CONFIG_DATA: 2440700000000000
PROFILE_BITS: 0000000000000000

BLOCK1: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK2: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK3: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK4: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK5: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK6: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK7: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN

please fix it team :D

br

Bugs in bb5 language only mode flash, its flash all files ????

Quote:

Originally Posted by teaitiana (Post 7436501)

they put new update only for one purpose, to buy new hti cos ours ufs or hwk interface are blocked in this so call update, are you seen anywhere in forum somebody from mxkey team answer on this error ,nothing silence
error access violation address xxxxxxx

bro, i have hwk as well... and it works perfectly as interface for mxkey dongle :D

the problem is:
mxkey can't or u can't? no offense bro...

u should try using SEARCH button :D

br

So , WE, MxKey users, with bunch of purchased credit on our dongle, and without HTI, are forgotten, and we cannot use MxKey software anymore. Nice update , and Thanks for Support.

I ve this problem in instaling 3.5 rev 1.1 in xp

Quote:

Originally Posted by jaijee (Post 7433176)

http://www.yukleresim.com/images/021...6127661469.jpg

same problem,,,,,,,
any help please........[/QUOTE]

update driver card C:\mobileEx\3.5\data\drivers\hti (mxkeycard.inf) ;)

new bugs please correct it i just install several times with no luck

Mxkey should ADD "READ FIRMWARE COMPATIBILITY"

~~Mxkey is the best

After updating hti sw my first job was N73 start up failur (simlock data corrupted)
after doing repair sim lock i got this message again (simlock data corrupted) can any body help me in this matter logs posted below

SIMLOCK_DATA corrupted!
SIMLOCK_DATA corrupted!
MXKEY Serial: [MxKey Team HTI Flasher Interface (WinUSB) 4] - C0848F6A
Using device: HTI BOX, FW ver: 00.17
Driver: USBEHCI:WinUSB, ver: 3.5.0.0
Module ver: 1.0.0.17626(14-06-2011), Library ver: 1.0.0.11296(14-06-2011)

Product: V 05wk47v61 09-07-08 RM-133 (c) Nokia.

Using cached productData.
PUBLIC ID: 1A200102419C0154CDF1E98AC05EC1BD2C953D86
PRIVATE ID: 53245C4CA7D523282A6F037CD86FEE0E8699D446
E-FUSE: 025B2301
SEC ROM CRC: 40830040
Updating SIMLOCK...error 0x1

Reading Simlock info ...
Imei net: 352757013768931
Version: SIMLOCK SERVER VERSION 63
Counter: 0/3, 0/10

CONFIG_DATA: 2440700000000000
PROFILE_BITS: 0000000000000000

BLOCK1: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK2: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK3: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK4: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK5: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK6: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK7: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN

Quote:

Originally Posted by teaitiana (Post 7436501)

yes your statement seems to be true.if that is the case there should be a warning note on this new update about ufs and jaf.else is there is a solution mxkey should help fast.thanks

shall we can expect an update with hwk interface