منتيات عوادي للمحمول
هل تريد التفاعل مع هذه المساهمة؟ كل ما عليك هو إنشاء حساب جديد ببضع خطوات أو تسجيل الدخول للمتابعة.

منتيات عوادي للمحمول

https://i.servimg.com/u/f41/15/41/71/88/th/410.png
 
الرئيسيةأحدث الصورالتسجيلدخول

 

 مجموعة حلول مشاكل كونتكت سرفيس في البيبي5 علي امكس كي

اذهب الى الأسفل 
كاتب الموضوعرسالة
السيد عوادي الناصر

السيد عوادي الناصر


عدد المساهمات : 1105
نقاط : 3034
تاريخ التسجيل : 08/07/2010

مجموعة حلول مشاكل كونتكت سرفيس في البيبي5 علي امكس كي  Empty
مُساهمةموضوع: مجموعة حلول مشاكل كونتكت سرفيس في البيبي5 علي امكس كي    مجموعة حلول مشاكل كونتكت سرفيس في البيبي5 علي امكس كي  Emptyالثلاثاء أغسطس 10, 2010 6:12 pm

السلام عليكم نبدا اولا
Frimware download from "IMAGE DL" button



Frimware download from "IMAGE DL" button
[ندعوك للتسجيل في المنتدى أو التعريف بنفسك لمعاينة هذه الصورة]
- enter manually product code
- press "IMAGE DL"
- after show new form ( image to download ) ,press "download"

video manual
download 1
download 2
download 3
download 4
download 5
download 6
نبدا الان السكرتي فيلد
استعمل اللغة الانكلزية لان الوق هكذا مع الدونقل لا استطيع تغيره

[ندعوك للتسجيل في المنتدى أو التعريف بنفسك لمعاينة هذه الصورة] Just in case if Recovery via Server doesn't work.......








<blockquote class="postcontent restore">
Hi,
This is just another method, let's say it is a temporary solution, will find another way to be more simple with mxkey.

It's all about HWC recovery issue.

Scan

Code:
Phone Type: RM-237 (Nokia 3110c)
SW Version: V 07.21 05-11-08 RM-237 (c) Nokia.
Imei plain: 35322503273286-5
Product Code: 0514959
Language Pack:
- not available.

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

TimeStamp: 2008-11-12T09:25:55Z
SW Version: 07.21
Variant Version: 014
ProductProfile: RM237_0514959_07.21_014.spr
Simlock: 0514959_simlock.bin

Imei net: 353225032732865
Version: SIMLOCK SERVER VERSION 63
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

BB5 Secure Storage Validation
Service > Phone Test > Various > BB5 Secure Storage Validation

Code:
SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!
Q: Why after write pm via SX4 i still end up with security failed issue?
A: Please check your phone via this feature.

BB5 Certivicate Validation
Service > Phone Test > Various > BB5 Certivicate Validation

Code:
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 094002010DA07E5652111A03CFD2350DD48AD044
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 191EC665DFAAF68F
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: 0089 8981 - 0000 0000 [Intel NU48F256,256 Mbits] type: NOR,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
ExtDEVC: FFFF 0000 - 0000 0000
Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0
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: C0E691EA16A7593A9BB28832D7312A39F7ED668D
Reading RAP NPC (0x168 bytes)
Original Product Code: 0514959
Reading RAP VARIANT (0x0 bytes)
Reading RAP CCC (0x160 bytes)
Product Code: 0514959
CCC seems to be valid
Reading RAP HWC (0x0 bytes)
HWC empty !
Recover CERT
Service > Imei Rebuild > Recover CERT

Code:
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 094002010DA07E5652111A03CFD2350DD48AD044
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 191EC665DFAAF68F
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: 0089 8981 - 0000 0000 [Intel NU48F256,256 Mbits] type: NOR,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
ExtDEVC: FFFF 0000 - 0000 0000
Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0
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: C0E691EA16A7593A9BB28832D7312A39F7ED668D
Reading RAP NPC (0x168 bytes)

Begin Certificate Request ...
Connecting to server ...OK, Login ...
Query done with status: OK
Updating PRODUCTCODE (0514959)... OK
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 094002010DA07E5652111A03CFD2350DD48AD044
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 191EC665DFAAF68F
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: 0089 8981 - 0000 0000 [Intel NU48F256,256 Mbits] type: NOR,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
ExtDEVC: FFFF 0000 - 0000 0000
Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0
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: C0E691EA16A7593A9BB28832D7312A39F7ED668D
Updating CMT NPC ...OK
Updating CMT CCC ...OK
Updating CMT HWC ...failed, Result: 06C0000000117200
Certificate programmed successfully !

In this case, you will need to write HWC certivicate ONLY.
In this example is using HWK, select HWC cert from the SAME PHONE TYPE.

Unfortunately, i don't have here on my hand a good phone to backup CRT partialy via MXKey.
Only got here collected backups on HWK format [ندعوك للتسجيل في المنتدى أو التعريف بنفسك لمعاينة هذه الصورة].
You also can read HWC CRT partialy on MXKey:
Service
> Imei & Security > Imei Rebuild > Backup RPL > Section
- Drop down, Select HWC only from a good phone.


Please Note: In this case, HWC is missing. Watch more detail on your own case.

Logs from UFSxHWK:
Code:
Certificate: Rm-237_351963038604637_1027200951214_HWCCmt.bin
CER FLASH ERASE OK, Time: 00:01
CER FLASH WRITE OK, Time: 00:00
Written: 1 Certificate(s)
Certificate(s) Write Done

Test again,
Service > Phone Test > Various > BB5 Certivicate Validation

Code:
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 094002010DA07E5652111A03CFD2350DD48AD044
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 191EC665DFAAF68F
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: 0089 8981 - 0000 0000 [Intel NU48F256,256 Mbits] type: NOR,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
ExtDEVC: FFFF 0000 - 0000 0000
Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0
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: C0E691EA16A7593A9BB28832D7312A39F7ED668D
Reading RAP NPC (0x168 bytes)
Original Product Code: 0514959
Reading RAP VARIANT (0x0 bytes)
Reading RAP CCC (0x160 bytes)
Product Code: 0514959
CCC seems to be valid
Reading RAP HWC (0xD4 bytes)
Product Code: 0514959
HWC seems to be valid
From SCAN, you will still see Security failed

Code:
Phone Type: RM-237 (Nokia 3110c)
SW Version: V 07.21 05-11-08 RM-237 (c) Nokia.
Imei plain: 35322503273286-5
Product Code: 0514959
Language Pack:
- not available.

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

TimeStamp: 2008-11-12T09:25:55Z
SW Version: 07.21
Variant Version: 014
ProductProfile: RM237_0514959_07.21_014.spr
Simlock: 0514959_simlock.bin

Imei net: 353225032732865
Version: SIMLOCK SERVER VERSION 63
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

And last step is
SX4 Online - PMM auth

Code:
Connecting to server ...OK
Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(ID), hello 114.127.220.142
SUPERDONGLE auth succeeded!

Write PM

Code:
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 86 bytes written.
- Key: 18, size 86 bytes written.
- Key: 20, size 86 bytes written.
- Key: 25, size 4 bytes written.
- Key: 29, size 6 bytes written.
- Key: 34, size 80 bytes written.
Section: 2
- Key: 0, size 432 bytes written.
Section: 4
- Key: 1, size 64 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.
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: 4, size 8 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: 5, size 6 bytes written.
- Key: 6, size 2 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 4 bytes written.
- Key: 65, size 4 bytes written.
- Key: 66, size 4 bytes written.
- Key: 67, size 4 bytes written.
- Key: 68, size 4 bytes written.
- Key: 69, size 16 bytes written.
- Key: 70, size 4 bytes written.
- Key: 71, size 2 bytes written.
- Key: 72, size 13 bytes written.
Section: 12
- Key: 0, size 102 bytes written.
Section: 13
- Key: 1, size 2 bytes written.
- Key: 3, size 2 bytes written.
- Key: 8, size 2 bytes written.
- Key: 11, size 48 bytes written.
- Key: 12, size 4 bytes written.
- Key: 15, size 886 bytes written.
- Key: 16, size 2 bytes written.
- Key: 19, size 8 bytes written.
- Key: 25, size 2 bytes written.
- Key: 37, size 4 bytes written.
- Key: 42, size 4 bytes written.
- Key: 43, size 4 bytes written.
- Key: 45, size 4 bytes written.
- Key: 46, size 4 bytes written.
- Key: 48, size 4 bytes written.
- Key: 52, size 2 bytes written.
- Key: 53, size 4 bytes written.
- Key: 54, size 4 bytes written.
- Key: 58, size 2 bytes written.
- Key: 60, size 4 bytes written.
- Key: 61, size 4 bytes written.
- Key: 63, size 4 bytes written.
- Key: 64, size 4 bytes written.
- Key: 66, size 4 bytes written.
- Key: 67, size 4 bytes written.
- Key: 71, size 4 bytes written.
- Key: 72, size 4 bytes written.
- Key: 74, size 4 bytes written.
- Key: 75, size 2 bytes written.
- Key: 76, size 2 bytes written.
- Key: 77, size 2 bytes written.
- Key: 83, size 2 bytes written.
- Key: 85, size 4 bytes written.
- Key: 86, size 4 bytes written.
- Key: 87, size 2 bytes written.
- Key: 89, size 4 bytes written.
- Key: 90, size 4 bytes written.
- Key: 91, size 2 bytes written.
- Key: 93, size 4 bytes written.
- Key: 94, size 4 bytes written.
- Key: 95, size 2 bytes written.
- Key: 97, size 4 bytes written.
- Key: 98, size 4 bytes written.
- Key: 99, size 2 bytes written.
- Key: 100, size 4 bytes written.
- Key: 101, size 2 bytes written.
- Key: 103, size 4 bytes written.
- Key: 104, size 4 bytes written.
- Key: 105, size 4 bytes written.
- Key: 106, size 4 bytes written.
- Key: 107, size 4 bytes written.
- Key: 108, size 2 bytes written.
- Key: 109, size 4 bytes written.
- Key: 110, size 4 bytes written.
- Key: 111, size 4 bytes written.
- Key: 112, size 2 bytes written.
- Key: 113, size 4 bytes written.
- Key: 114, size 4 bytes written.
- Key: 118, size 4 bytes written.
- Key: 119, size 4 bytes written.
- Key: 123, size 8 bytes written.
- Key: 129, size 4 bytes written.
- Key: 130, size 4 bytes written.
- Key: 133, size 2 bytes written.
- Key: 135, size 2 bytes written.
- Key: 138, size 4 bytes written.
- Key: 139, size 4 bytes written.
- Key: 144, size 4 bytes written.
- Key: 145, size 8 bytes written.
- Key: 146, size 4 bytes written.
- Key: 147, size 4 bytes written.
- Key: 159, size 2 bytes written.
- Key: 160, size 2 bytes written.
- Key: 167, size 8 bytes written.
- Key: 168, size 4 bytes written.
Section: 14
- Key: 0, size 6 bytes written.
Section: 31
- Key: 4, size 12 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 36 bytes written.
- Key: 8, size 36 bytes written.
- Key: 9, size 36 bytes written.
- Key: 10, size 36 bytes written.
- Key: 11, size 36 bytes written.
- Key: 12, size 36 bytes written.
- Key: 13, size 40 bytes written.
- Key: 14, size 40 bytes written.
- Key: 15, size 40 bytes written.
- Key: 16, size 40 bytes written.
- Key: 17, size 40 bytes written.
- Key: 18, size 40 bytes written.
- Key: 19, size 40 bytes written.
- Key: 20, size 40 bytes written.
Section: 50
- Key: 0, size 2 bytes written.
Section: 51
- Key: 4, size 74 bytes written.
Section: 54
- Key: 0, size 2 bytes written.
- Key: 2, size 24 bytes written.
Section: 55
- Key: 0, size 80 bytes written.
- Key: 1, size 2 bytes written.
Section: 56
- Key: 0, size 4 bytes written.
- Key: 1, size 4 bytes written.
Section: 58
- Key: 0, size 51 bytes written.
- Key: 1, size 83 bytes written.
- Key: 2, size 57 bytes written.
- Key: 3, size 63 bytes written.
- Key: 4, size 59 bytes written.
- Key: 5, size 57 bytes written.
- Key: 6, size 47 bytes written.
- Key: 7, size 57 bytes written.
- Key: 8, size 39 bytes written.
- Key: 9, size 51 bytes written.
- Key: 10, size 41 bytes written.
- Key: 11, size 49 bytes written.
- Key: 12, size 75 bytes written.
- Key: 13, size 45 bytes written.
- Key: 14, size 61 bytes written.
- Key: 15, size 59 bytes written.
- Key: 16, size 37 bytes written.
- Key: 17, size 49 bytes written.
- Key: 18, size 86 bytes written.
- Key: 19, size 51 bytes written.
- Key: 20, size 48 bytes written.
- Key: 21, size 40 bytes written.
- Key: 22, size 46 bytes written.
- Key: 23, size 64 bytes written.
- Key: 24, size 49 bytes written.
- Key: 25, size 69 bytes written.
- Key: 26, size 42 bytes written.
- Key: 27, size 61 bytes written.
- Key: 28, size 55 bytes written.
- Key: 29, size 56 bytes written.
- Key: 30, size 56 bytes written.
- Key: 31, size 61 bytes written.
- Key: 32, size 49 bytes written.
- Key: 33, size 47 bytes written.
- Key: 34, size 49 bytes written.
- Key: 35, size 69 bytes written.
- Key: 36, size 51 bytes written.
- Key: 37, size 39 bytes written.
- Key: 38, size 138 bytes written.
- Key: 39, size 42 bytes written.
- Key: 40, size 46 bytes written.
- Key: 41, size 47 bytes written.
- Key: 42, size 43 bytes written.
- Key: 43, size 43 bytes written.
- Key: 44, size 34 bytes written.
- Key: 45, size 59 bytes written.
- Key: 46, size 73 bytes written.
Section: 59
- Key: 0, size 68 bytes written.
- Key: 1, size 149 bytes written.
- Key: 2, size 101 bytes written.
- Key: 3, size 64 bytes written.
- Key: 4, size 36 bytes written.
- Key: 5, size 174 bytes written.
- Key: 6, size 66 bytes written.
- Key: 7, size 97 bytes written.
- Key: 8, size 109 bytes written.
- Key: 9, size 156 bytes written.
- Key: 10, size 36 bytes written.
- Key: 11, size 164 bytes written.
- Key: 12, size 169 bytes written.
- Key: 13, size 71 bytes written.
- Key: 14, size 178 bytes written.
- Key: 15, size 177 bytes written.
- Key: 16, size 78 bytes written.
- Key: 17, size 141 bytes written.
- Key: 18, size 68 bytes written.
- Key: 19, size 107 bytes written.
Section: 60
- Key: 0, size 95 bytes written.
- Key: 1, size 129 bytes written.
- Key: 2, size 73 bytes written.
- Key: 3, size 63 bytes written.
- Key: 4, size 25 bytes written.
- Key: 5, size 81 bytes written.
- Key: 6, size 27 bytes written.
- Key: 7, size 61 bytes written.
- Key: 8, size 67 bytes written.
- Key: 9, size 75 bytes written.
- Key: 10, size 55 bytes written.
- Key: 11, size 27 bytes written.
Section: 61
- Key: 0, size 62 bytes written.
- Key: 1, size 57 bytes written.
- Key: 2, size 99 bytes written.
- Key: 3, size 110 bytes written.
- Key: 4, size 156 bytes written.
- Key: 5, size 174 bytes written.
- Key: 6, size 64 bytes written.
- Key: 7, size 36 bytes written.
- Key: 8, size 35 bytes written.
- Key: 9, size 36 bytes written.
- Key: 10, size 36 bytes written.
- Key: 11, size 87 bytes written.
- Key: 12, size 164 bytes written.
- Key: 13, size 87 bytes written.
- Key: 14, size 90 bytes written.
- Key: 15, size 139 bytes written.
- Key: 16, size 70 bytes written.
- Key: 17, size 57 bytes written.
- Key: 18, size 156 bytes written.
- Key: 19, size 76 bytes written.
Section: 62
- Key: 1, size 15 bytes written.
- Key: 3, size 15 bytes written.
- Key: 4, size 15 bytes written.
Section: 63
- Key: 0, size 14 bytes written.
Section: 65
- Key: 0, size 11 bytes written.
- Key: 1, size 11 bytes written.
- Key: 2, size 11 bytes written.
- Key: 3, size 11 bytes written.
- Key: 4, size 11 bytes written.
Section: 66
- Key: 0, size 160 bytes written.
- Key: 1, size 160 bytes written.
- Key: 4, size 160 bytes written.
- Key: 5, size 4 bytes written.
- Key: 6, size 4 bytes written.
- Key: 7, size 4 bytes written.
- Key: 8, size 4 bytes written.
- Key: 9, size 160 bytes written.
- Key: 10, size 240 bytes written.
- Key: 12, size 192 bytes written.
- Key: 13, size 192 bytes written.
- Key: 14, size 4 bytes written.
- Key: 16, size 4 bytes written.
- Key: 19, size 4 bytes written.
- Key: 20, size 4 bytes written.
- Key: 21, size 228 bytes written.
- Key: 22, size 192 bytes written.
- Key: 23, size 192 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: 36, size 4 bytes written.
- Key: 38, size 4 bytes written.
- Key: 40, size 4 bytes written.
- Key: 47, size 251 bytes written.
- Key: 52, size 2 bytes written.
- Key: 64, size 8 bytes written.
- Key: 65, size 8 bytes written.
- Key: 66, size 8 bytes written.
- Key: 67, size 41 bytes written.
- Key: 68, size 8 bytes written.
- Key: 70, size 8 bytes written.
- Key: 82, size 9 bytes written.
- Key: 83, size 9 bytes written.
- Key: 84, size 8 bytes written.
- Key: 85, size 1001 bytes written.
- Key: 87, size 6144 bytes written.
- Key: 88, size 300 bytes written.
- Key: 89, size 40 bytes written.
- Key: 90, size 288 bytes written.
- Key: 91, size 4 bytes written.
- Key: 92, size 251 bytes written.
- Key: 97, size 251 bytes written.
- Key: 98, size 251 bytes written.
- Key: 104, size 35 bytes written.
- Key: 105, size 4 bytes written.
- Key: 106, size 4 bytes written.
- Key: 107, size 4 bytes written.
- Key: 108, size 4 bytes written.
- Key: 111, size 4 bytes written.
- Key: 112, size 4 bytes written.
- Key: 113, size 4 bytes written.
- Key: 114, size 4 bytes written.
- Key: 115, size 4 bytes written.
- Key: 116, size 4 bytes written.
- Key: 117, size 2 bytes written.
- Key: 118, size 4 bytes written.
- Key: 120, size 4 bytes written.
Section: 67
- Key: 0, size 2756 bytes written.
Section: 76
- Key: 0, size 534 bytes written.
Section: 84
- Key: 0, size 3 bytes written.
Section: 88
- Key: 0, size 36 bytes written.
Section: 91
- Key: 0, size 2048 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: 25, size 132 bytes written.
Section: 110
- Key: 0, size 6 bytes written.
Section: 111
- Key: 0, size 200 bytes written.
- Key: 1, size 20 bytes written.
- Key: 2, size 20 bytes written.
- Key: 126, size 20 bytes written.
- Key: 127, size 20 bytes written.
- Key: 150, size 8 bytes written.
- Key: 151, size 4 bytes written.
- Key: 152, size 40 bytes written.
Section: 116
- 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 36 bytes written.
- Key: 8, size 36 bytes written.
- Key: 9, size 36 bytes written.
- Key: 10, size 36 bytes written.
- Key: 11, size 36 bytes written.
- Key: 12, size 36 bytes written.
- Key: 13, size 40 bytes written.
- Key: 14, size 40 bytes written.
- Key: 15, size 40 bytes written.
- Key: 16, size 40 bytes written.
- Key: 17, size 40 bytes written.
- Key: 18, size 40 bytes written.
- Key: 19, size 40 bytes written.
- Key: 20, size 40 bytes written.
- Key: 21, size 40 bytes written.
- Key: 22, size 40 bytes written.
Section: 117
- Key: 5, size 10 bytes written.
- Key: 6, size 8 bytes written.
- Key: 8, size 40 bytes written.
Section: 123
- Key: 0, size 3 bytes written.
- Key: 4, size 3 bytes written.
Section: 153
- Key: 0, size 68 bytes written.
- Key: 1, size 68 bytes written.
- Key: 2, size 68 bytes written.
- Key: 3, size 68 bytes written.
- Key: 4, size 68 bytes written.
- Key: 5, size 68 bytes written.
Section: 163
- Key: 0, size 8 bytes written.
Section: 165
- Key: 0, size 16 bytes written.
- Key: 1, size 8 bytes written.
Section: 181
- Key: 0, size 8 bytes written.
- Key: 1, size 10 bytes written.
Section: 182
- Key: 3, size 8 bytes written.
- Key: 13, size 8 bytes written.
- Key: 18, size 8 bytes written.
- Key: 19, size 8 bytes written.
- Key: 22, size 8 bytes written.
Section: 183
- Key: 3, size 8 bytes written.
- Key: 13, size 8 bytes written.
- Key: 18, size 8 bytes written.
- Key: 19, size 8 bytes written.
- Key: 22, size 8 bytes written.
Section: 184
- Key: 3, size 8 bytes written.
- Key: 13, size 8 bytes written.
- Key: 18, size 8 bytes written.
- Key: 19, size 8 bytes written.
- Key: 22, size 8 bytes written.
Section: 185
- Key: 3, size 8 bytes written.
- Key: 13, size 8 bytes written.
- Key: 18, size 8 bytes written.
- Key: 19, size 8 bytes written.
- Key: 22, size 8 bytes written.
Section: 186
- Key: 3, size 8 bytes written.
- Key: 5, size 8 bytes written.
- Key: 12, size 12 bytes written.
- Key: 13, size 8 bytes written.
- Key: 18, size 8 bytes written.
- Key: 19, size 8 bytes written.
- Key: 22, size 8 bytes written.
Section: 187
- Key: 3, size 8 bytes written.
- Key: 13, size 8 bytes written.
- Key: 18, size 8 bytes written.
- Key: 19, size 8 bytes written.
- Key: 22, size 8 bytes written.
Section: 188
- Key: 3, size 8 bytes written.
- Key: 13, size 8 bytes written.
- Key: 18, size 8 bytes written.
- Key: 19, size 8 bytes written.
- Key: 22, size 8 bytes written.
Section: 190
- Key: 0, size 355 bytes written.
Section: 191
- Key: 0, size 5 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: 200
- Key: 0, size 5 bytes written.
Section: 202
- Key: 4, size 42 bytes written.
Section: 213
- Key: 0, size 20 bytes written.
Section: 215
- Key: 0, size 84 bytes written.
Section: 217
- Key: 0, size 32 bytes written.
Section: 218
- Key: 0, size 2 bytes written.
Section: 225
- Key: 1, size 6 bytes written.
- Key: 2, size 6 bytes written.
Section: 232
- Key: 0, size 20 bytes written.
- Key: 9, size 4 bytes written.
Section: 238
Section: 250
- Key: 1, size 1224 bytes written.
- Key: 2, size 128 bytes written.
- Key: 3, size 426 bytes written.
- Key: 4, size 36 bytes written.
Section: 301
- 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 36 bytes written.
- Key: 8, size 36 bytes written.
- Key: 9, size 36 bytes written.
- Key: 10, size 36 bytes written.
- Key: 11, size 36 bytes written.
- Key: 12, size 36 bytes written.
- Key: 13, size 40 bytes written.
- Key: 14, size 40 bytes written.
- Key: 15, size 40 bytes written.
- Key: 16, size 40 bytes written.
- Key: 17, size 40 bytes written.
- Key: 18, size 40 bytes written.
- Key: 19, size 40 bytes written.
- Key: 20, size 40 bytes written.
- Key: 21, size 40 bytes written.
- Key: 22, size 40 bytes written.
Section: 306
- Key: 0, size 2 bytes written.
- 308 skipped
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.
- Key: 22, size 12 bytes written.
Section: 319
- Key: 0, size 148 bytes written.
- Key: 1, size 148 bytes written.
- Key: 2, size 148 bytes written.
- Key: 3, size 148 bytes written.
- Key: 4, size 148 bytes written.
- Key: 5, size 148 bytes written.
- Key: 6, size 148 bytes written.
- Key: 7, size 148 bytes written.
- Key: 8, size 148 bytes written.
- Key: 9, size 148 bytes written.
- Key: 10, size 148 bytes written.
- Key: 11, size 148 bytes written.
- Key: 12, size 148 bytes written.
- Key: 13, size 148 bytes written.
- Key: 14, size 148 bytes written.
- Key: 15, size 148 bytes written.
- Key: 16, size 148 bytes written.
- Key: 17, size 148 bytes written.
- Key: 18, size 148 bytes written.
- Key: 19, size 148 bytes written.
- Key: 20, size 148 bytes written.
- Key: 21, size 148 bytes written.
- Key: 22, size 148 bytes written.
- Key: 23, size 148 bytes written.
- Key: 24, size 148 bytes written.
- Key: 25, size 148 bytes written.
- Key: 26, size 148 bytes written.
- Key: 27, size 148 bytes written.
- Key: 28, size 148 bytes written.
- Key: 29, size 148 bytes written.
- Key: 30, size 148 bytes written.
- Key: 31, size 148 bytes written.
- Key: 32, size 148 bytes written.
- Key: 33, size 148 bytes written.
- Key: 34, size 148 bytes written.
- Key: 35, size 148 bytes written.
- Key: 36, size 148 bytes written.
- Key: 37, size 148 bytes written.
- Key: 38, size 148 bytes written.
- Key: 39, size 148 bytes written.
- Key: 40, size 148 bytes written.
- Key: 41, size 148 bytes written.
- Key: 42, size 148 bytes written.
- Key: 43, size 148 bytes written.
- Key: 44, size 148 bytes written.
- Key: 45, size 148 bytes written.
- Key: 46, size 148 bytes written.
Section: 320
- Key: 0, size 148 bytes written.
- Key: 1, size 148 bytes written.
- Key: 2, size 148 bytes written.
- Key: 3, size 148 bytes written.
- Key: 4, size 148 bytes written.
- Key: 5, size 148 bytes written.
- Key: 6, size 148 bytes written.
- Key: 7, size 148 bytes written.
- Key: 8, size 148 bytes written.
- Key: 9, size 148 bytes written.
- Key: 10, size 148 bytes written.
- Key: 11, size 148 bytes written.
- Key: 12, size 148 bytes written.
- Key: 13, size 148 bytes written.
- Key: 14, size 148 bytes written.
- Key: 15, size 148 bytes written.
- Key: 16, size 148 bytes written.
- Key: 17, size 148 bytes written.
- Key: 18, size 148 bytes written.
Section: 321
- Key: 0, size 148 bytes written.
- Key: 1, size 148 bytes written.
- Key: 2, size 148 bytes written.
- Key: 3, size 148 bytes written.
- Key: 4, size 148 bytes written.
- Key: 5, size 148 bytes written.
- Key: 6, size 148 bytes written.
- Key: 7, size 148 bytes written.
Section: 322
Section: 325
- Key: 0, size 63 bytes written.
- Key: 1, size 87 bytes written.
- Key: 2, size 69 bytes written.
- Key: 3, size 73 bytes written.
- Key: 4, size 93 bytes written.
- Key: 5, size 63 bytes written.
- Key: 6, size 55 bytes written.
Section: 334
Section: 339
- Key: 0, size 511 bytes written.
- Key: 1, size 511 bytes written.
Section: 341
- Key: 3, size 4 bytes written.
- Key: 4, size 4902 bytes written.
Completed in 21.954 s

And all be done,

Code:
Phone Type: RM-237 (Nokia 3110c)
SW Version: V 07.21 05-11-08 RM-237 (c) Nokia.
Imei plain: 35322503273286-5
Product Code: 0550691
Language Pack:
- not available.

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


Imei net: 353225032732865
Version: SIMLOCK SERVER VERSION 63
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
</blockquote>
الرجوع الى أعلى الصفحة اذهب الى الأسفل
https://i.servimg.com/u/f64/15/94/99/87/25369410.gif
السيد عوادي الناصر

السيد عوادي الناصر


عدد المساهمات : 1105
نقاط : 3034
تاريخ التسجيل : 08/07/2010

مجموعة حلول مشاكل كونتكت سرفيس في البيبي5 علي امكس كي  Empty
مُساهمةموضوع: رد: مجموعة حلول مشاكل كونتكت سرفيس في البيبي5 علي امكس كي    مجموعة حلول مشاكل كونتكت سرفيس في البيبي5 علي امكس كي  Emptyالثلاثاء أغسطس 10, 2010 6:14 pm


[ندعوك للتسجيل في المنتدى أو التعريف بنفسك لمعاينة هذه الصورة] Why we need NOKIA USB ROM as interface? One of the reason....








<blockquote class="postcontent restore">
Hello,
here is another tips, how to take flashing job such phone by mxkey.

Here is boot check output by UFSxHWK.
Just example using UFS.

[ندعوك للتسجيل في المنتدى أو التعريف بنفسك لمعاينة هذه الصورة]

And this is the BUS Check by using mobileEx current version.

[ندعوك للتسجيل في المنتدى أو التعريف بنفسك لمعاينة هذه الصورة]

Try to fix the flash loader if you had problem like this.
This also fix DCT4 issue about "BootLoader not responding, mostly RAM problem !"

[ندعوك للتسجيل في المنتدى أو التعريف بنفسك لمعاينة هذه الصورة]

Nay...nay..nay.. This phone is not supported for flashing on F-Bus interface.

[ندعوك للتسجيل في المنتدى أو التعريف بنفسك لمعاينة هذه الصورة]

As told by mobileEx, that current interface is not supported, so we must use Nokia USB ROM.
And all be done without any problem.


[ندعوك للتسجيل في المنتدى أو التعريف بنفسك لمعاينة هذه الصورة]

Code:
Flashing completed in 4 min 28.672 s


Phone Type:
SW Version:
Imei plain: -
Language Pack:
- not available.



Total time to process is 4 min 55.312 s
USB Pooling failed, phone not found !
Just ignore the final error message, that is not a problem.

You can use F-Bus for any Service Operation.
It is supported. Reset, Format, write PM, etc.

Code:
Phone Type: RM-504 (Nokia 5530 XpressMusic)
SW Version: V ICPR72_09w36.5 25-09-09 RM-504 (c) Nokia
Imei plain: 35420003703310-5
Product Code: 0578167
ApeCoreSw: V 20.0.080
Language Pack:
- not available.

This phone have PM308 protected, SD security in not restorable.
- Avoid SW Downgrade & manual erase to this phone !

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

TimeStamp: 2009-12-07T11:08:23+00:00
SW Version: 20.0.080
Variant Version: 001
ProductProfile: RM504_0578167_20.0.080_001.spr
Simlock: simlock_3gstandard_bb5.bin

Imei net: 354200037033105
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

Reset:
Code:
FULL FACTORY... OK
USER DATA... OK
LEAVE FACTORY... OK
SERVICE CENTER... OK
SOFTWARE UPGRADE... OK
PRODUCTION TUNING... OK
Reset User Code (to default:12345) ... OK
Completed in 4.109 s

Format:
Code:
Formating FS: C ...
Completed in 0.172 s
Formating FS: D ...
Completed in 0.203 s
Formating FS: E ...
Completed in 1.453 s
Formating FS: Z ...
Completed in 0.203 s
</blockquote>
الرجوع الى أعلى الصفحة اذهب الى الأسفل
https://i.servimg.com/u/f64/15/94/99/87/25369410.gif
السيد عوادي الناصر

السيد عوادي الناصر


عدد المساهمات : 1105
نقاط : 3034
تاريخ التسجيل : 08/07/2010

مجموعة حلول مشاكل كونتكت سرفيس في البيبي5 علي امكس كي  Empty
مُساهمةموضوع: رد: مجموعة حلول مشاكل كونتكت سرفيس في البيبي5 علي امكس كي    مجموعة حلول مشاكل كونتكت سرفيس في البيبي5 علي امكس كي  Emptyالثلاثاء أغسطس 10, 2010 6:16 pm


[ندعوك للتسجيل في المنتدى أو التعريف بنفسك لمعاينة هذه الصورة] distinguish when using NCK and SIMLOCK Repair









NCK Calculator
Phone have LOCKED to network

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



Imei net: 3520450xxxxxxxx
Version: SIMLOCK SERVER
Provider: PT. Satelindo, Country: Indonesia
Counter: 0/3, 0/10

CONFIG_DATA: 5100100000000000
PROFILE_BITS: 8000000000000006

BLOCK 1: 1=LOCKED (MCC+MNC): 51001F, DATA=51001F
BLOCK 2: 1=LOCKED (MCC+MNC): 51001F, DATA=51001F
BLOCK 3: 1=LOCKED (MCC+MNC): 00101F, DATA=00101F

please USE "NCK Calculator" for safe UNLOCKING

>> "SCAN" for "Identify" SIMLOCK GENERATION
>> Select "Unlock by CODE"
>> "Calc NCK"

[ندعوك للتسجيل في المنتدى أو التعريف بنفسك لمعاينة هذه الصورة]

Code:
Imei net: 3520450xxxxxxxx
Version: SIMLOCK SERVER
Provider: PT. Satelindo, Country: Indonesia
Counter: 0/3, 0/10

CONFIG_DATA: 5100100000000000
PROFILE_BITS: 8000000000000006

BLOCK 1: 1=LOCKED (MCC+MNC): 51001F, DATA=51001F
BLOCK 2: 1=LOCKED (MCC+MNC): 51001F, DATA=51001F
BLOCK 3: 1=LOCKED (MCC+MNC): 00101F, DATA=00101F


Backup saved to "BB5_3520450xxxxxxxx_SIMLOCK.back"
Using device: J.A.F, FW ver: 01.B1
Library version: 1.0.0.12027, Date: 06-02-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 ...OK
Sending PreLoader ...OK
Sending CustomLoader ...OK

Calculating NCK using security server ...
Connecting to server[main.mxkey.biz] ...OK, secure login ...

#pw+ 693402639114130 +1 #
#pw+ 592385163892314 +2 #
#pw+ 858969064820817 +3 #
#pw+ 912863836291037 +4 #
#pw+ 818484633555523 +5 #
#pw+ 049580344180624 +6 #
#pw+ 488738539254885 +7 #

Sending NCK code ...
Trying NCK lock 7 ... OK: code accepted.
Completed in 23.516 s

Restarting phone ...

Reading Simlock info ...
Imei net: 3520450xxxxxxxx
Version: SIMLOCK SERVER
Provider: PT. Satelindo, Country: Indonesia
Counter: 0/3, 0/10

CONFIG_DATA: 5100100000000000
PROFILE_BITS: 8000000000000006

BLOCK 1: 1=OPEN, DATA=51001F
BLOCK 2: 1=OPEN, DATA=51001F
BLOCK 3: 1=OPEN, DATA=00101F

SIMLOCK REPAIR
when Phone have DAMAGE SIMLOCK

Code:
SIMLOCK invalid!
SUPERDONGLE_KEY seems to be valid
SECURITY_TEST failed!

SIMLOCK_DATA corrupted!

then use

>> REPAIR SIMLOCK
>> tick "Make SIMLOCK RPL"
>> "Repair SPLOCK"

[ندعوك للتسجيل في المنتدى أو التعريف بنفسك لمعاينة هذه الصورة]

Code:
Updating SIMLOCK...OK

Reading Simlock info ...
Imei net: 3520450xxxxxxxx
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
الرجوع الى أعلى الصفحة اذهب الى الأسفل
https://i.servimg.com/u/f64/15/94/99/87/25369410.gif
السيد عوادي الناصر

السيد عوادي الناصر


عدد المساهمات : 1105
نقاط : 3034
تاريخ التسجيل : 08/07/2010

مجموعة حلول مشاكل كونتكت سرفيس في البيبي5 علي امكس كي  Empty
مُساهمةموضوع: رد: مجموعة حلول مشاكل كونتكت سرفيس في البيبي5 علي امكس كي    مجموعة حلول مشاكل كونتكت سرفيس في البيبي5 علي امكس كي  Emptyالثلاثاء أغسطس 10, 2010 6:18 pm


Re: distinguish when using NCK and SIMLOCK Repair









Just an information.
starting from mobileEx 3.3 Rev1.5, now repair SL and SD is done by single button "repair SD".
So if you want to repair SL, the whole procedure is as simple as:

1. backup RPL(just in case).
2. erase EEPROM.
3. Repair SD
4. Full Factory
5. SUPER SD Auth + Write PM1,309

if these steps still not fix the phone, please do BB5 Cert Validation + repair procedure as described on previous post above.

BR
الرجوع الى أعلى الصفحة اذهب الى الأسفل
https://i.servimg.com/u/f64/15/94/99/87/25369410.gif
 
مجموعة حلول مشاكل كونتكت سرفيس في البيبي5 علي امكس كي
الرجوع الى أعلى الصفحة 
صفحة 1 من اصل 1
 مواضيع مماثلة
-
» بعض الحلول لحل مشكلة كونتكت سرفيس لهاتف 5130 حتي سيم لو انفليد
» مجموعة دروس مهم في امكس كي
» احسن برنامج لفك شفرات البيبي5 بدون مشاكل
» مجموعة كبيرة من ملفات الايريز خاصة البيبي5
» فديو يوضح عملية التفلايش يوسبي علب امكس كي

صلاحيات هذا المنتدى:لاتستطيع الرد على المواضيع في هذا المنتدى
منتيات عوادي للمحمول :: منتدى السوفت ويير والبرمجة للتليفون المحمول ( Software ) :: قسم النوكيا(nokia) :: السوفت(SOFTWARE) :: bb5-
انتقل الى: