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 05-20-2010, 15:39   #1 (permalink)
No Life Poster
 
meisam's Avatar
 
Join Date: Feb 2005
Location: IRAN(land of heros)
Age: 44
Posts: 2,680
Member: 115172
Status: Offline
Thanks Meter: 212
5130 CS,Security test failed...


Hi everybody;
This Nokia 5130 is most porblematic Nokia phone of all ATM ,look at the log below:

Code:
Phone Type: RM-495 (Nokia 5130c-2)
SW Version: V 07.95 03-02-10 RM-495 (c) Nokia             
Imei plain: 35153804589246-4
Product Code: 0571584
Language Pack:
- not available.

This is SL3 phone(Simlock2 format).
- Avoid SW Downgrade & manual erase to this phone !
 
SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
CMLA_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!
 
 
Imei net: 351538045892464
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
The first thing that comes to mind is writing PM fields 1 and 309 but this didn't solve the problem.Next i tried writing full modified PM and this could not help as well.All the time phone has the same identification info and shows simlock and superdongle ok and there is no need to repair SD cause i can SX4 while using PMM AUTH option.Please leave your idea about this here
 
The Following User Says Thank You to meisam For This Useful Post:
Old 05-20-2010, 15:48   #2 (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
you need..................first press Super SD Auth and write pm 1 & 309

100 % solved your problem
 
The Following 2 Users Say Thank You to jaleelkuttikkar For This Useful Post:
Old 05-20-2010, 16:31   #3 (permalink)
No Life Poster
 
meisam's Avatar
 
Join Date: Feb 2005
Location: IRAN(land of heros)
Age: 44
Posts: 2,680
Member: 115172
Status: Offline
Thanks Meter: 212
I did this now and wrote full PM but again i get "Security test fail".It does not seem to need "Repair SD" coz info shows they're safe.
 
Old 05-20-2010, 16:35   #4 (permalink)
No Life Poster
 
Join Date: Jul 2009
Location: India
Posts: 2,857
Member: 1086393
Status: Offline
Thanks Meter: 771
Hi,
Read your Rpl Back up upload here.
might be Some data missing out there.
As u had already ByPass Sx4 then no need to do Sd Auth.
will check.
thnkx
 
Old 05-20-2010, 17:12   #5 (permalink)
No Life Poster
 
meisam's Avatar
 
Join Date: Feb 2005
Location: IRAN(land of heros)
Age: 44
Posts: 2,680
Member: 115172
Status: Offline
Thanks Meter: 212
Here is the rpl bkp atteched,would be nice of you to help
Attached Files
File Type: rar BB5_35153804589246_BACK.rar (13.1 KB, 133 views)
 
The Following User Says Thank You to meisam For This Useful Post:
Old 05-20-2010, 17:20   #6 (permalink)
No Life Poster
 
Join Date: Jul 2007
Location: kingdom of saudi arabia
Posts: 735
Member: 540878
Status: Offline
Thanks Meter: 910
sd repair

super sd auth
load pm 1 and 309 only
write pm
 
Old 05-20-2010, 17:22   #7 (permalink)
No Life Poster
 
Join Date: Jul 2009
Location: India
Posts: 2,857
Member: 1086393
Status: Offline
Thanks Meter: 771
Hi,
Write this Rpl and post result here
All Should be Fine

B/R
 
Old 05-21-2010, 07:09   #8 (permalink)
No Life Poster
 
Join Date: Jul 2009
Location: India
Posts: 2,857
Member: 1086393
Status: Offline
Thanks Meter: 771
Write this Rpl and Post result here
Thnkx
 
Old 05-21-2010, 08:34   #9 (permalink)
No Life Poster
 
[Shadab_M]'s Avatar
 
Join Date: Mar 2006
Location: .: India :. Heaven on Earth
Posts: 2,496
Member: 238812
Status: Offline
Sonork: 100.1602669
Thanks Meter: 1,443
Why not try Recover CERT?

Br,
Shadab Ahmad
 
Old 05-21-2010, 10:36   #10 (permalink)
No Life Poster
 
joe cellular's Avatar
 
Join Date: Aug 2006
Location: South Africa
Posts: 659
Member: 340957
Status: Offline
Thanks Meter: 65
5130c

Phone Type: RM-495 (Nokia 5130c-2)
SW Version: V 06.65 01-04-09 RM-495 (c) Nokia
Imei plain: 35524603504280-3
Language Pack:
- not available.
SIMLOCK invalid!
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST failed!
SECURITY_TEST passed


SIMLOCK_DATA corrupted!

wat i need to do
 
Old 05-21-2010, 10:49   #11 (permalink)
Freak Poster
 
neo_2005's Avatar
 
Join Date: May 2004
Location: Silent Mode
Age: 39
Posts: 448
Member: 65656
Status: Offline
Thanks Meter: 91
Quote:
SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
CMLA_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!
1.check cert validation => ok/not
2. point 1 ok => go to modif PM area => ok

nb; posible hw area is missing
go to selftest


Code:
Phone Type: RM-495 (Nokia 5130c-2)
SW Version: V 06.65 01-04-09 RM-495 (c) Nokia
Imei plain: 35524603504280-3
Language Pack:
- not available.
SIMLOCK invalid!
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST failed!
SECURITY_TEST passed


SIMLOCK_DATA corrupted!
no backup full data npc , just ask2rpl now.



 
Old 05-22-2010, 06:01   #12 (permalink)
No Life Poster
 
Join Date: Jul 2009
Location: India
Posts: 2,857
Member: 1086393
Status: Offline
Thanks Meter: 771
Quote:
Originally Posted by shadab_a4u View Post
Why not try Recover CERT?

Br,
Shadab Ahmad
Hi,
Recover Certificate is not working..
For more Pls search.
And the Final solution Is here--
http://forum.gsmhosting.com/vbb/f550...l-here-945700/
 
Old 05-22-2010, 07:51   #13 (permalink)
No Life Poster
 
Join Date: Jul 2009
Location: India
Posts: 2,857
Member: 1086393
Status: Offline
Thanks Meter: 771
Hi,
Also Post logs of sd repair> super sd.
Try this two option and post result here


Waiting
http://forum.gsmhosting.com/vbb/f550...l-here-945700/
 
Old 05-22-2010, 08:15   #14 (permalink)
Freak Poster
 
Join Date: May 2010
Location: Pakistan
Age: 47
Posts: 295
Member: 1295798
Status: Offline
Sonork: brista786
Thanks Meter: 97
hi meisam, use this mettod 100% 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:
Old 05-22-2010, 10:30   #15 (permalink)
No Life Poster
 
StRaNgE PeRsOn's Avatar
 
Join Date: Nov 2006
Location: *P*A*K*I*S*T*A*N
Posts: 3,169
Member: 391445
Status: Offline
Sonork: 100.1583575
Thanks Meter: 392
if problem not solved with 1 and 309 then possibly you need ask2 rpl
 
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
Security Code dESiRE! Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 6 05-13-2011 22:17
5110 Security Code Help! cahrisma Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 6 07-05-2010 09:04
how to unlock 5130 accelr8 Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 4 06-24-2010 17:52
SECURITY CODE AWLABA Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 6 02-22-2000 23:38
Mti init failed dogbreak Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 3 11-22-1999 01:28

 



All times are GMT +1. The time now is 15:23.



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.27163 seconds with 10 queries

SEO by vBSEO