GSM Shop GSM Shop
GSM-Forum  

Welcome to the GSM-Forum forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features.
Only registered members may post questions, contact other members or search our database of over 8 million posts.

Registration is fast, simple and absolutely free so please - Click to REGISTER!

If you have any problems with the registration process or your account login, please contact contact us .

Go Back   GSM-Forum > Product Support Sections > No More Supported Solutions (Dead Products) > No More Supported H/W Products > MXKEY (by Alim Hape) > MXKEY Nokia Flasher and Unlocker (by Alim Hape)


Closed Thread
 
LinkBack Thread Tools Display Modes
Old 06-04-2010, 16:42   #1 (permalink)
Freak Poster
 
chinny1982's Avatar
 
Join Date: Dec 2007
Location: india
Age: 41
Posts: 198
Member: 664681
Status: Offline
Thanks Meter: 53
5310 contact service


mx key log

Using device: POTATO BOX, FW ver: 01.B1
Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101013000
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 20800216082803540659F448EFF18673BAF78D69
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 RAP 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,RAP
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 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: 3E96DE4212587183E5E16BB2C79692A53C19875D
Original Imei: 35681702804135
Original Product code: 0565586
Bluetooth ID: 0023B42867DD

Phone Type: RM-303 (Nokia 5310 XpressMusic)
SW Version: V 10.10 23-03-09 RM-303 (c) Nokia
Imei plain: 35681702804135-5
Product Code: 0548870
Language Pack:
- not available.
SIMLOCK invalid!
SUPERDONGLE_KEY seems to be valid
CMLA_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST failed!
SECURITY_TEST passed


SIMLOCK_DATA corrupted!


unlock
SIMLOCK_DATA corrupted!

Backup already exist.
Using device: POTATO BOX, FW ver: 01.B1
Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)

Product: V 10.10 23-03-09 RM-303 (c) Nokia

SYSTEM ASIC ID: 000000010000022600010006010C192101013000
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 273F6D55DFAAF68F

Sending SecondaryBoot [rap3gv3_2nd.fg](0x3D00 bytes) ...OK
Sending PreLoader(0x2E4 bytes) ...OK
Sending ROM(0x11BC bytes) ...OK
Sending SecurityBlock(0x2000 bytes) ...OK
Sending SimlockBinary(0x190 bytes) ...OK
Sending KEYS [SLPA] (0x1940 bytes) ...OK
Calculating LOCK data ...OK
Unlocked PM saved to "C:\mobileEx\3.4\data\backup\356817028041355_UNLOC KED.PM"
Writing Unlocked PM ... OK
Completed in 32.703 s
Restarting phone ...



next coming popup and show dis mesz


access violation at address 03b79c2e . read of address 073578ec.


plz help me.........
 
Old 06-04-2010, 18:52   #2 (permalink)
No Life Poster
 
Join Date: Jan 2008
Location: Pakistan
Posts: 1,623
Member: 682736
Status: Offline
Thanks Meter: 457
Its sl3 phone you can repair SD and Security Test failed but can not repair Simlock at the moment. It will be possible when sl3 unlocking is available....
 
Old 06-04-2010, 19:02   #3 (permalink)
No Life Poster
 
jaleelkuttikkar's Avatar
 
Join Date: Sep 2007
Location: :::::::EMIRATES:::::::
Posts: 1,802
Member: 591669
Status: Offline
Sonork: 110011
Thanks Meter: 687
Quote:
Originally Posted by adnon View Post
Its sl3 phone you can repair SD and Security Test failed but can not repair Simlock at the moment. It will be possible when sl3 unlocking is available....
it's wrong.........5310 V 10.10 not sl3......this support in unlocking and repair Mxkey.

5310 XpressMusic (RM-303) v58.58 - v59.42....it's sl3
 
Old 06-05-2010, 05:29   #4 (permalink)
No Life Poster
 
Join Date: Jan 2008
Location: Pakistan
Posts: 1,623
Member: 682736
Status: Offline
Thanks Meter: 457
Sorry I thought it was 5130.....

5310 is sl2... you can repair...
 
Old 06-05-2010, 07:57   #5 (permalink)
Freak Poster
 
chinny1982's Avatar
 
Join Date: Dec 2007
Location: india
Age: 41
Posts: 198
Member: 664681
Status: Offline
Thanks Meter: 53
yahoooooooooo i got solution in mt box......problem solve........ than q frdz 4 ur valueble replyes r info............thanxs alot............
 
Old 06-05-2010, 10:24   #6 (permalink)
Freak Poster
 
m_choko's Avatar
 
Join Date: Oct 2004
Location: Tunisia
Posts: 417
Member: 88177
Status: Offline
Sonork: 1594092
Thanks Meter: 71
why using other box???! with mxkey you can repair it in 5mns see this link : http://forum.gsmhosting.com/vbb/f550...rvice-1006372/
 
Old 06-05-2010, 12:13   #7 (permalink)
Freak Poster
 
juniorljs's Avatar
 
Join Date: Mar 2009
Location: Saint-Marc, Haiti
Posts: 177
Member: 992258
Status: Offline
Thanks Meter: 21
Donate money to this user
Yes it works great with MX-KEY

I have tried
 
Old 06-13-2010, 07:11   #8 (permalink)
Freak Poster
 
asif ali's Avatar
 
Join Date: Nov 2006
Location: Karachi pakistan
Age: 41
Posts: 449
Member: 388647
Status: Offline
Sonork: sheerazi
Thanks Meter: 161
5310 contact service

--------------------------------------------------------------------------------

mx key log

Using device: POTATO BOX, FW ver: 01.B1
Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101013000
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 20800216082803540659F448EFF18673BAF78D69
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 RAP 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,RAP
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 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: 3E96DE4212587183E5E16BB2C79692A53C19875D
Original Imei: 35681702804135
Original Product code: 0565586
Bluetooth ID: 0023B42867DD

Phone Type: RM-303 (Nokia 5310 XpressMusic)
SW Version: V 10.10 23-03-09 RM-303 (c) Nokia
Imei plain: 35681702804135-5
Product Code: 0548870
Language Pack:
- not available.
SIMLOCK invalid!
SUPERDONGLE_KEY seems to be valid
CMLA_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST failed!
SECURITY_TEST passed


SIMLOCK_DATA corrupted!


unlock
SIMLOCK_DATA corrupted!

Backup already exist.
Using device: POTATO BOX, FW ver: 01.B1
Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)

Product: V 10.10 23-03-09 RM-303 (c) Nokia

SYSTEM ASIC ID: 000000010000022600010006010C192101013000
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 273F6D55DFAAF68F

Sending SecondaryBoot [rap3gv3_2nd.fg](0x3D00 bytes) ...OK
Sending PreLoader(0x2E4 bytes) ...OK
Sending ROM(0x11BC bytes) ...OK
Sending SecurityBlock(0x2000 bytes) ...OK
Sending SimlockBinary(0x190 bytes) ...OK
Sending KEYS [SLPA] (0x1940 bytes) ...OK
Calculating LOCK data ...OK
Unlocked PM saved to "C:\mobileEx\3.4\data\backup\356817028041355_U NLOC KED.PM"
Writing Unlocked PM ... OK
Completed in 32.703 s
Restarting phone ...


next coming popup and show dis mesz


access violation at address 03b79c2e . read of address 073578ec.


plz help me.........
 
Old 06-14-2010, 06:08   #9 (permalink)
Freak Poster
 
chinny1982's Avatar
 
Join Date: Dec 2007
Location: india
Age: 41
Posts: 198
Member: 664681
Status: Offline
Thanks Meter: 53
Quote:
Originally Posted by asif ali View Post
5310 contact service

--------------------------------------------------------------------------------

mx key log

Using device: POTATO BOX, FW ver: 01.B1
Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101013000
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 20800216082803540659F448EFF18673BAF78D69
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 RAP 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,RAP
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 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: 3E96DE4212587183E5E16BB2C79692A53C19875D
Original Imei: 35681702804135
Original Product code: 0565586
Bluetooth ID: 0023B42867DD

Phone Type: RM-303 (Nokia 5310 XpressMusic)
SW Version: V 10.10 23-03-09 RM-303 (c) Nokia
Imei plain: 35681702804135-5
Product Code: 0548870
Language Pack:
- not available.
SIMLOCK invalid!
SUPERDONGLE_KEY seems to be valid
CMLA_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST failed!
SECURITY_TEST passed


SIMLOCK_DATA corrupted!


unlock
SIMLOCK_DATA corrupted!

Backup already exist.
Using device: POTATO BOX, FW ver: 01.B1
Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)

Product: V 10.10 23-03-09 RM-303 (c) Nokia

SYSTEM ASIC ID: 000000010000022600010006010C192101013000
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 273F6D55DFAAF68F

Sending SecondaryBoot [rap3gv3_2nd.fg](0x3D00 bytes) ...OK
Sending PreLoader(0x2E4 bytes) ...OK
Sending ROM(0x11BC bytes) ...OK
Sending SecurityBlock(0x2000 bytes) ...OK
Sending SimlockBinary(0x190 bytes) ...OK
Sending KEYS [SLPA] (0x1940 bytes) ...OK
Calculating LOCK data ...OK
Unlocked PM saved to "C:\mobileEx\3.4\data\backup\356817028041355_U NLOC KED.PM"
Writing Unlocked PM ... OK
Completed in 32.703 s
Restarting phone ...


next coming popup and show dis mesz


access violation at address 03b79c2e . read of address 073578ec.


plz help me.........

try in mt-box............its working 4 me...............
 
Old 06-14-2010, 08:20   #10 (permalink)
Freak Poster
 
Join Date: May 2010
Location: Pakistan
Age: 47
Posts: 295
Member: 1295798
Status: Offline
Sonork: brista786
Thanks Meter: 97
use this metohed i hope ur problem will be solved


Phone logs when Scanned in Mx-key:

Phone Type: RM-240 (Nokia 6500s-1)
SW Version: V 10.00 06-03-09 RM-240 (c) Nokia
Imei plain: 35765901674649-9
Language Pack:
- not available.

SIMLOCK invalid!
SUPERDONGLE_KEY invalid!
- WD timer enabled, phone will reboot itself after 3 min.
SIMLOCK_TEST failed!
SECURITY_TEST passed


SIMLOCK_DATA corrupted!


PROCEDURE TO FOLLOW

1.Repair SD
2.SUPER SD Auth
3.PM Write
4.Repair SIMLOCK


Step by Step:

1. Repair SD.

Under IMEI & Security tab click IMEI Rebuild and click "Repair SD". Wait until mx-key finishes it's job..

Sample Log:

Using device: J.A.F, FW ver: 01.B1
Library version: 1.0.0.11985, Date: 03-02-2010

Product: V 10.00 06-03-09 RM-240 (c) Nokia

SYSTEM ASIC ID: 000000010000022600010006010C192101003000 [RAP3G ver: PA 3.0]
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 273F6D55DFAAF68F
Sending SecondaryBoot ...OK
Sending PreLoader ...OK
Sending CustomLoader ...OK

Calculating SUPERDONGLE using security server ...
Connecting to server[main.mxkey.biz] ...OK, secure login ...
Completed in 4.906 s

RPL saved to "C:\mobileEx\3.3\data\backup\BB5_RM-240_357659016746499_SD.RPL"
Updating SUPERDONGLE_KEY ...OK


After repairing SUPERDONGLE_KEY, SECURITY_TEST has been damaged.

see status:

Phone Type: RM-240 (Nokia 6500s-1)
SW Version: V 10.00 06-03-09 RM-240 (c) Nokia
Imei plain: 35765901674649-9
Language Pack:
- not available.

SIMLOCK invalid!
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST failed!
SECURITY_TEST failed!


SIMLOCK_DATA corrupted!


proceed to next steps to restore SECURITY_TEST.


2. SUPER SD Auth.


Under PM tab click "SUPER SD Auth". Again wait for mx-key to finish..

Sample Log:

Using device: J.A.F, FW ver: 01.B1
Library version: 1.0.0.11985, Date: 03-02-2010

Product: V 10.00 06-03-09 RM-240 (c) Nokia

SYSTEM ASIC ID: 000000010000022600010006010C192101003000 [RAP3G ver: PA 3.0]
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 273F6D55DFAAF68F
Sending SecondaryBoot ...OK
Sending PreLoader ...OK
Sending CustomLoader ...OK

Restarting phone ...
Connecting to server[main.mxkey.biz] ...OK, secure login ...
Authenticating to SUPERDONGLE using security server ...
SUPERDONGLE authorized !

After the unit has been authorized, you can now write pm fields 1 and 309.. For my case, i use a complete pm file but chose to skip simlock area.

3. Write good pm file.


Still under PM tab..Locate "Load from file" then click it.. a folder will pop-up asking you to choose the pm file you would like to write.. pick the file then click "Open". Wait for mx-key to finish.

Sample Log:

Completed in 7.828 s
Writing PM from Node ...
Section: 1
- Key: 0, size 114 bytes written.
- Key: 2, size 98 bytes written.
- Key: 4, size 110 bytes written.
- Key: 6, size 98 bytes written.
- Key: 8, size 110 bytes written.
- Key: 13, size 98 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: 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.
Section: 2
- Key: 0, size 448 bytes written.
Section: 4
- Key: 1, size 48 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: 18, size 80 bytes written.
- Key: 19, size 4 bytes written.
- Key: 28, size 2 bytes written.
Section: 8
- Key: 1, size 12 bytes written.
- Key: 7, size 8 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 2 bytes written.
- Key: 7, size 1 bytes written.
- Key: 8, size 1 bytes written.
- Key: 9, size 1 bytes written.
- Key: 10, size 1 bytes written.
- Key: 11, size 1 bytes written.
- Key: 12, size 1 bytes written.
- Key: 13, size 1 bytes written.
- Key: 14, size 2 bytes written.
- Key: 15, size 2 bytes written.
- Key: 16, size 2 bytes written.
- Key: 17, size 2 bytes written.
- Key: 18, size 16 bytes written.
- Key: 19, size 32 bytes written.
- Key: 20, size 32 bytes written.
- Key: 21, size 2 bytes written.
- Key: 22, size 2 bytes written.
- Key: 23, size 2 bytes written.
- Key: 24, size 2 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 2 bytes written.
- Key: 30, size 2 bytes written.
- Key: 31, size 2 bytes written.
- Key: 32, size 2 bytes written.
- Key: 33, size 2 bytes written.
- Key: 34, size 2 bytes written.
- Key: 35, size 2 bytes written.
- Key: 36, size 2 bytes written.
- Key: 37, size 2 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 2 bytes written.
- Key: 44, size 2 bytes written.
- Key: 45, size 2 bytes written.
- Key: 46, size 2 bytes written.
- Key: 47, size 2 bytes written.
- Key: 48, size 2 bytes written.
- Key: 49, size 2 bytes written.
- Key: 50, size 2 bytes written.
- Key: 51, size 2 bytes written.
- Key: 52, size 2 bytes written.
- Key: 53, size 2 bytes written.
- Key: 54, size 2 bytes written.
- Key: 55, size 2 bytes written.
- Key: 56, size 2 bytes written.
- Key: 57, size 2 bytes written.
- Key: 58, size 2 bytes written.
- Key: 59, size 2 bytes written.
- Key: 60, size 2 bytes written.
- Key: 61, size 2 bytes written.
- Key: 62, size 2 bytes written.
- Key: 63, size 2 bytes written.
- Key: 64, size 2 bytes written.
- Key: 65, size 4 bytes written.
- Key: 66, size 1 bytes written.
- Key: 67, size 4 bytes written.
- Key: 68, size 4 bytes written.
- Key: 69, size 4 bytes written.
- Key: 70, size 4 bytes written.
- Key: 71, size 16 bytes written.
- Key: 72, size 4 bytes written.
- Key: 73, size 2 bytes written.
- Key: 74, size 13 bytes written.
Section: 31
- Key: 4, size 16 bytes written.
Section: 42
- Key: 0, size 2 bytes written.
- Key: 1, size 12 bytes written.
- Key: 2, size 36 bytes written.
- Key: 3, size 36 bytes written.
- Key: 4, size 36 bytes written.
- Key: 5, size 36 bytes written.
- Key: 6, size 36 bytes written.
- Key: 7, size 40 bytes written.
- Key: 8, size 40 bytes written.
- Key: 9, size 40 bytes written.
- Key: 10, size 40 bytes written.
- Key: 11, size 40 bytes written.
- Key: 12, size 40 bytes written.
- Key: 13, size 40 bytes written.
- Key: 14, size 40 bytes written.
Section: 50
- Key: 0, size 2 bytes written.
Section: 54
- Key: 0, size 2 bytes written.
Section: 66
- Key: 0, size 2050 bytes written.
- Key: 1, size 240 bytes written.
- Key: 2, size 240 bytes written.
- Key: 3, size 1 bytes written.
- Key: 4, size 1 bytes written.
- Key: 5, size 240 bytes written.
- Key: 6, size 4 bytes written.
- Key: 7, size 4 bytes written.
- Key: 8, size 4 bytes written.
- Key: 9, size 4 bytes written.
- Key: 10, size 240 bytes written.
- Key: 11, size 240 bytes written.
- Key: 12, size 1 bytes written.
- Key: 16, size 4 bytes written.
- Key: 18, size 4 bytes written.
- Key: 20, size 4 bytes written.
- Key: 22, size 4 bytes written.
- Key: 24, size 4 bytes written.
- Key: 26, size 4 bytes written.
- Key: 28, size 4 bytes written.
- Key: 30, size 4 bytes written.
- Key: 32, size 4 bytes written.
- Key: 34, size 4 bytes written.
- Key: 57, size 8 bytes written.
- Key: 58, size 8 bytes written.
- Key: 59, size 8 bytes written.
- Key: 60, size 8 bytes written.
- Key: 61, size 8 bytes written.
- Key: 75, size 8 bytes written.
- Key: 76, size 8 bytes written.
- Key: 78, size 6144 bytes written.
- Key: 79, size 300 bytes written.
- Key: 80, size 60 bytes written.
- Key: 91, size 3 bytes written.
- Key: 92, size 3 bytes written.
- Key: 93, size 3 bytes written.
- Key: 94, size 3 bytes written.
- Key: 95, size 3 bytes written.
- Key: 96, size 3 bytes written.
- Key: 98, size 4 bytes written.
- Key: 99, size 4 bytes written.
- Key: 100, size 4 bytes written.
- Key: 101, size 4 bytes written.
- Key: 102, size 4 bytes written.
- Key: 103, size 6 bytes written.
- Key: 105, size 4 bytes written.
- Key: 106, size 4 bytes written.
- Key: 107, size 4 bytes written.
- Key: 116, size 120 bytes written.
- Key: 118, size 30 bytes written.
- Key: 119, size 1 bytes written.
- Key: 120, size 8 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 89 bytes written.
- Key: 2, size 69 bytes written.
- Key: 3, size 70 bytes written.
- Key: 26, size 12 bytes written.
- 120 skipped
Section: 122
- Key: 0, size 2 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: 218
- Key: 0, size 2 bytes written.
Section: 238
- Key: 1, size 1 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: 334
- Key: 0, size 1 bytes written.
Section: 339
- Key: 0, size 511 bytes written.
- Key: 1, size 511 bytes written.
Section: 341
- Key: 0, size 1 bytes written.
- Key: 3, size 4 bytes written.
- Key: 4, size 4296 bytes written.
Section: 354
- Key: 0, size 3 bytes written.
Section: 356
- Key: 0, size 2 bytes written.
- Key: 1, size 8 bytes written.
Section: 362
- Key: 0, size 1 bytes written.
- Key: 1, size 120 bytes written.
Completed in 9.594 s



after pm write, check the status of the unit..


Phone Type: RM-240 (Nokia 6500s-1)
SW Version: V 10.00 06-03-09 RM-240 (c) Nokia
Imei plain: 35765901674649-9
Product Code: 0543754
Language Pack:
- not available.

SIMLOCK invalid!
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST failed!
SECURITY_TEST passed


SIMLOCK_DATA corrupted!


SECURITY_TEST has been restored.. Proceed to next step to repair SIMLOCK.


4.Repair SIMLOCK.

Under "IMEI & SECURITY" click Simlock locate and click "Repair SIMLOCK" in Options menu. Also click "Make SIMLOCK RPL" then then click "Update SpLock". Wait for mx-key to finish.


Sample Log:

Library version: 1.0.0.11985, Date: 03-02-2010

Product: V 10.00 06-03-09 RM-240 (c) Nokia

SYSTEM ASIC ID: 000000010000022600010006010C192101003000 [RAP3G ver: PA 3.0]
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 273F6D55DFAAF68F
Sending SecondaryBoot ...OK
Sending PreLoader ...OK
Sending CustomLoader ...OK

Calculating SIMLOCK using security server ...
Connecting to server[main.mxkey.biz] ...OK, secure login ...
Completed in 4.672 s

RPL saved to "C:\mobileEx\3.3\data\backup\BB5_RM-240_357659016746499_SIM.RPL"
Updating SIMLOCK...OK

Reading Simlock info ...
Imei net: 357659016746499
Version: SIMLOCK SERVER
Provider: Nokia Test, Country: Finland
Counter: 0/3, 0/10

CONFIG_DATA: 2440700000000000
PROFILE_BITS: 0000000000000000

BLOCK 1: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 2: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 3: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 4: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 5: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 6: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 7: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF


After all procedure's are done, scan the unit again to check it's status..


Phone Type: RM-240 (Nokia 6500s-1)
SW Version: V 10.00 06-03-09 RM-240 (c) Nokia
Imei plain: 35765901674649-9
Product Code: 0543754
Language Pack:
- not available.

SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST passed


Imei net: 357659016746499
Version: SIMLOCK SERVER
Provider: Nokia Test, Country: Finland
Counter: 0/3, 0/10

CONFIG_DATA: 2440700000000000
PROFILE_BITS: 0000000000000000

BLOCK 1: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 2: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 3: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 4: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 5: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 6: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 7: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF


Unit successfully repaired.. thanks to Mx-key team..
 
The Following User Says Thank You to True Man For This Useful Post:
Closed Thread

Bookmarks


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Service Provider Lock 1-4 ? StompSC Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 2 06-27-2012 11:00
unlock Service Provider Code for PrimeCo (USA) in 6185 Nokia Phone X-plot Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 5 05-11-2000 03:43
gsm service provider sidou Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 5 04-30-2000 11:09
FREE SP unlock service timxy Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 0 10-22-1999 16:05
NOKIA TECHNICAL SERVICE BOOK AND NOKIA SERVICING SIM CARD FOR SALE TRADE FOR 7110 andrew bennett Main Sales Section 0 07-09-1999 10:41

 



All times are GMT +1. The time now is 10:09.



Powered by Searchlight © 2024 Axivo Inc.
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2023 -
Page generated in 0.26639 seconds with 9 queries

SEO by vBSEO