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)
Reload this Page Problem in BB5 Certificate Validation
Register FAQDonate Forum Rules Root any Device ★iPhone Unlock★ ★ Direct Codes ★ Direct Unlock Source


Closed Thread
 
LinkBack Thread Tools Display Modes
Old 01-16-2010, 17:48   #1 (permalink)
Freak Poster
 
Join Date: Jun 2006
Posts: 301
Member: 290637
Status: Offline
Thanks Meter: 24
Problem in BB5 Certificate Validation

PHP Code:
Reading Simlock info ...
Imei net: 3542xxxxxxxxxxxx
Version: SIMLOCK SERVER
Provider: Orange - Partner Communications, Country: Israel
Counter: 0/3, 0/10

CONFIG_DATA: 4250100000000000
PROFILE_BITS: 0000000000000000

BLOCK 1: 1=LOCKED (MCC+MNC): 42501F, DATA=42501F
BLOCK 2: 1=LOCKED (MCC+MNC): 42510F, DATA=42510F
BLOCK 3: 1=LOCKED (MCC+MNC): 42510F, DATA=42510F
BLOCK 4: 1=LOCKED (MCC+MNC): 42501F, DATA=42501F
SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006400C192101031103 [RAPIDO3G ver: 1.13]
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 19A00002107A00529F88344B0D2763DB9245703D
ASIC MODE ID: 00
ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
ROM ID: 4B9B75103E691FF8
SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 1.37.1 revision: 0.0 size: 0x3B80
Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105
FlashID0: 00EC 0040 - 0080 0121 [Samsung 2Gb DDP OneNAND,2 Gbits] type: ONENAND,RAP 
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000 
ExtDEVC: FFFF 0000 - 0000 0000
Algorithm: RAPIDOv11_algo.fg [XSR 1.5] version: 1.40.0 revision: 0.0 size: 0x27520
Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105
RAP PAPUBKEYS HASH: 76A20187051C30162EE91C77AE5E6011F5F1BA61
Reading RAP NPC (0x190 bytes)
Original Product Code: 0577252
Reading RAP VARIANT (0x0 bytes)
Reading RAP CCC (0x160 bytes)
Product Code: 0577252
CCC seems to be valid
Reading RAP HWC (0x0 bytes)
HWC empty !
Recover CERT
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006400C192101031103 [RAPIDO3G ver: 1.13]
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 19A00002107A00529F88344B0D2763DB9245703D
ASIC MODE ID: 00
ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
ROM ID: 4B9B75103E691FF8
SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 1.37.1 revision: 0.0 size: 0x3B80
Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105
FlashID0: 00EC 0040 - 0080 0121 [Samsung 2Gb DDP OneNAND,2 Gbits] type: ONENAND,RAP 
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000 
ExtDEVC: FFFF 0000 - 0000 0000
Algorithm: RAPIDOv11_algo.fg [XSR 1.5] version: 1.40.0 revision: 0.0 size: 0x27520
Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105
RAP PAPUBKEYS HASH: 76A20187051C30162EE91C77AE5E6011F5F1BA61
Reading RAP NPC (0x190 bytes)

Begin Certificate Request ...
Connecting to server ...OK, Login ...
Invalid account.
ERROR: No certificate found in the database !
CalcNCK
Imei net: 3542xxxxxxxxxxxx
Version: SIMLOCK SERVER
Provider: Orange - Partner Communications, Country: Israel
Counter: 0/3, 0/10

CONFIG_DATA: 4250100000000000
PROFILE_BITS: 0000000000000000

BLOCK 1: 1=LOCKED (MCC+MNC): 42501F, DATA=42501F
BLOCK 2: 1=LOCKED (MCC+MNC): 42510F, DATA=42510F
BLOCK 3: 1=LOCKED (MCC+MNC): 42510F, DATA=42510F
BLOCK 4: 1=LOCKED (MCC+MNC): 42501F, DATA=42501F


Backup already exist.
Using device: J.A.F, FW ver: 01.B1
Library version: 1.0.0.11685, Date: 15-01-2010

Product: V ICPR72_09w20.12 10-09-09 RM-356 (c) Nokia 
ApeCoreSw: V 31.0.101

SYSTEM ASIC ID: 000000010000022600010006400C192101031103 [RAPIDO3G ver: 1.13]
ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
ROM ID: 4B9B75103E691FF8

Sending SecondaryBoot [rapidov11_2nd.fg](0x3AC0 bytes) ...OK
Sending PreLoader(0x2E4 bytes) ...OK
Sending CustomLoader(0x5E7C bytes) ...OK

Calculating NCK using security server ...
Connecting to server[main.mxkey.biz] ...OK, Secure Login ...


ERROR: SP BLOCK corrupted or not supported.!
Please "Identify" PA_SIMLOCK type, PA_SL3 is not supported (yet!).

Reading Simlock info ...
Imei net: 354216033640800
Version: SIMLOCK SERVER
Provider: Orange - Partner Communications, Country: Israel
Counter: 0/3, 0/10

CONFIG_DATA: 4250100000000000
PROFILE_BITS: 0000000000000000

BLOCK 1: 1=LOCKED (MCC+MNC): 42501F, DATA=42501F
BLOCK 2: 1=LOCKED (MCC+MNC): 42510F, DATA=42510F
BLOCK 3: 1=LOCKED (MCC+MNC): 42510F, DATA=42510F
BLOCK 4: 1=LOCKED (MCC+MNC): 42501F, DATA=42501F 
 
Old 01-16-2010, 18:04   #2 (permalink)
No Life Poster
 
Join Date: Nov 2006
Location: turkey
Posts: 768
Member: 384775
Status: Offline
Sonork: 100.1605469
Thanks Meter: 159
your phone is sl3. now not supported.
 
Old 01-17-2010, 04:46   #3 (permalink)
No Life Poster
 
Andra's Avatar
 
Join Date: Feb 2005
Location: AD
Posts: 4,665
Member: 976728
Status: Offline
Sonork: 1589709
Thanks Meter: 4,775
what do u want doing here ??

perhaps u read every changes in each update.

Quote:
Added, BB5 Certificate Validation
~ Usefull to identify SECURITY_TEST problem specially if SUPERDONGLE is valid
Button located to [Phone Test->Various]
Added, FREE BB5 Certificate Recovery to reflect the CERT validation features
~ This will make restore CCC,HWC or VARIANT by product code from server database.
Button located to [IMEI & Security->Recover CERT]
~ Minor bug fixes
br,
 
The Following User Says Thank You to Andra For This Useful Post:
Old 01-17-2010, 08:41   #4 (permalink)
Freak Poster
 
xahin's Avatar
 
Join Date: Jun 2007
Location: OUT OF CONTROL
Posts: 276
Member: 536012
Status: Offline
Sonork: 100.1660617
Thanks Meter: 120
Quote:
Originally Posted by burhan barq View Post
PHP Code:
Reading Simlock info ...
Imei net: 3542xxxxxxxxxxxx
Version: SIMLOCK SERVER
Provider: Orange - Partner Communications, Country: Israel
Counter: 0/3, 0/10

CONFIG_DATA: 4250100000000000
PROFILE_BITS: 0000000000000000

BLOCK 1: 1=LOCKED (MCC+MNC): 42501F, DATA=42501F
BLOCK 2: 1=LOCKED (MCC+MNC): 42510F, DATA=42510F
BLOCK 3: 1=LOCKED (MCC+MNC): 42510F, DATA=42510F
BLOCK 4: 1=LOCKED (MCC+MNC): 42501F, DATA=42501F
SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006400C192101031103 [RAPIDO3G ver: 1.13]
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 19A00002107A00529F88344B0D2763DB9245703D
ASIC MODE ID: 00
ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
ROM ID: 4B9B75103E691FF8
SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 1.37.1 revision: 0.0 size: 0x3B80
Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105
FlashID0: 00EC 0040 - 0080 0121 [Samsung 2Gb DDP OneNAND,2 Gbits] type: ONENAND,RAP 
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000 
ExtDEVC: FFFF 0000 - 0000 0000
Algorithm: RAPIDOv11_algo.fg [XSR 1.5] version: 1.40.0 revision: 0.0 size: 0x27520
Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105
RAP PAPUBKEYS HASH: 76A20187051C30162EE91C77AE5E6011F5F1BA61
Reading RAP NPC (0x190 bytes)
Original Product Code: 0577252
Reading RAP VARIANT (0x0 bytes)
Reading RAP CCC (0x160 bytes)
Product Code: 0577252
CCC seems to be valid
Reading RAP HWC (0x0 bytes)
HWC empty !
Recover CERT
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006400C192101031103 [RAPIDO3G ver: 1.13]
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 19A00002107A00529F88344B0D2763DB9245703D
ASIC MODE ID: 00
ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
ROM ID: 4B9B75103E691FF8
SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 1.37.1 revision: 0.0 size: 0x3B80
Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105
FlashID0: 00EC 0040 - 0080 0121 [Samsung 2Gb DDP OneNAND,2 Gbits] type: ONENAND,RAP 
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000 
ExtDEVC: FFFF 0000 - 0000 0000
Algorithm: RAPIDOv11_algo.fg [XSR 1.5] version: 1.40.0 revision: 0.0 size: 0x27520
Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105
RAP PAPUBKEYS HASH: 76A20187051C30162EE91C77AE5E6011F5F1BA61
Reading RAP NPC (0x190 bytes)

Begin Certificate Request ...
Connecting to server ...OK, Login ...
Invalid account.
ERROR: No certificate found in the database !
CalcNCK
Imei net: 3542xxxxxxxxxxxx
Version: SIMLOCK SERVER
Provider: Orange - Partner Communications, Country: Israel
Counter: 0/3, 0/10

CONFIG_DATA: 4250100000000000
PROFILE_BITS: 0000000000000000

BLOCK 1: 1=LOCKED (MCC+MNC): 42501F, DATA=42501F
BLOCK 2: 1=LOCKED (MCC+MNC): 42510F, DATA=42510F
BLOCK 3: 1=LOCKED (MCC+MNC): 42510F, DATA=42510F
BLOCK 4: 1=LOCKED (MCC+MNC): 42501F, DATA=42501F


Backup already exist.
Using device: J.A.F, FW ver: 01.B1
Library version: 1.0.0.11685, Date: 15-01-2010

Product: V ICPR72_09w20.12 10-09-09 RM-356 (c) Nokia 
ApeCoreSw: V 31.0.101

SYSTEM ASIC ID: 000000010000022600010006400C192101031103 [RAPIDO3G ver: 1.13]
ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
ROM ID: 4B9B75103E691FF8

Sending SecondaryBoot [rapidov11_2nd.fg](0x3AC0 bytes) ...OK
Sending PreLoader(0x2E4 bytes) ...OK
Sending CustomLoader(0x5E7C bytes) ...OK

Calculating NCK using security server ...
Connecting to server[main.mxkey.biz] ...OK, Secure Login ...


ERROR: SP BLOCK corrupted or not supported.!
Please "Identify" PA_SIMLOCK type, PA_SL3 is not supported (yet!).

Reading Simlock info ...
Imei net: 354216033640800
Version: SIMLOCK SERVER
Provider: Orange - Partner Communications, Country: Israel
Counter: 0/3, 0/10

CONFIG_DATA: 4250100000000000
PROFILE_BITS: 0000000000000000

BLOCK 1: 1=LOCKED (MCC+MNC): 42501F, DATA=42501F
BLOCK 2: 1=LOCKED (MCC+MNC): 42510F, DATA=42510F
BLOCK 3: 1=LOCKED (MCC+MNC): 42510F, DATA=42510F
BLOCK 4: 1=LOCKED (MCC+MNC): 42501F, DATA=42501F 

U --- dont apply any dirty color in your eye
 
Old 01-17-2010, 09:25   #5 (permalink)
Freak Poster
 
digicomm's Avatar
 
Join Date: Dec 2006
Posts: 475
Member: 413149
Status: Offline
Thanks Meter: 83
my problom is this and what i do?

Phone Type: RM-217 (Nokia 6300)
SW Version: V 07.30 07-05-09 RM-217 (c) Nokia.
Imei plain: 3564360xxxxxxx
Product Code: 0538331
Language Pack:
- not available.
SIMLOCK seems to be valid
SUPERDONGLE_KEY invalid!
- WD timer enabled, phone will reboot itself after 3 min.
SIMLOCK_TEST passed
SECURITY_TEST passed

TimeStamp: 2008-11-13T16:01:08Z
SW Version: 07.21
Variant Version: 018
ProductProfile: RM217_0538331_07.21_018.spr
Simlock: 0538331_simlock.bin

Imei net: 35643601xxxxxxx
Version: SIMLOCK SERVER VERSION 63
Provider: Nokia Test, Country: Finland
Counter: 0/3, 0/10

CONFIG_DATA: 2440700000000000
PROFILE_BITS: 8000000000000000

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
 
Old 01-17-2010, 09:27   #6 (permalink)
Freak Poster
 
digicomm's Avatar
 
Join Date: Dec 2006
Posts: 475
Member: 413149
Status: Offline
Thanks Meter: 83
my phone log this.


RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 16E00117FA336B566AA2F17155FED5924086CE11
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: 00EC 22FE - 0000 6921 [Samsung K8S5615ETA,256 Mbits] type: NOR,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
ExtDEVC: FFFF 0000 - 0000 0000
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: 7F7E6491E8D30494B45630BB3A8599F4E1C674C9
Reading RAP NPC (0x168 bytes)

Begin Certificate Request ...
Connecting to server ...OK, Login ...
Query done with status: OK
Updating PRODUCTCODE (0538331)... OK
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 16E00117FA336B566AA2F17155FED5924086CE11
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: 00EC 22FE - 0000 6921 [Samsung K8S5615ETA,256 Mbits] type: NOR,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
ExtDEVC: FFFF 0000 - 0000 0000
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: 7F7E6491E8D30494B45630BB3A8599F4E1C674C9
Updating CMT NPC ...OK
Updating CMT CCC ...OK
Updating CMT HWC ...failed, Result: 06C0000000117200Certificate programmed successfully !
 
Old 01-17-2010, 09:55   #7 (permalink)
No Life Poster
 
*Diablo*'s Avatar
 
Join Date: Mar 2004
Location: pccomp
Age: 42
Posts: 1,399
Member: 59173
Status: Offline
Sonork: 100.1585568
Thanks Meter: 225
Donate money to this user
How you get it ?
Check in few phones:

RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 2020010D543A0058E741D328448999287B3FAE28
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: 00EC 22FE - 0000 6921 [Samsung K8S5615ETA,256 Mbits] type: NOR,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
ExtDEVC: FFFF 0000 - 0000 0000
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: 7F7E6491E8D30494B45630BB3A8599F4E1C674C9
Reading RAP NPC (0x0 bytes)

Begin Certificate Request ...
Connecting to server ...OK, Login ...
Invalid account.
ERROR: No certificate found in the database !
 
Old 01-17-2010, 10:06   #8 (permalink)
No Life Poster
 
Umair Rashid's Avatar
 
Join Date: Dec 2006
Location: Rawalpindi, Pakistan
Posts: 2,292
Member: 421117
Status: Offline
Sonork: +92 346 5544377 (PHONE)
Thanks Meter: 2,522
Quote:
Originally Posted by digicomm View Post
my problom is this and what i do?


SIMLOCK seems to be valid
SUPERDONGLE_KEY invalid!
- WD timer enabled, phone will reboot itself after 3 min.
SIMLOCK_TEST passed
SECURITY_TEST passed
"Recover CERT" does not repair Superdongle Key !!!
This button is used to rebuild HWC CCc and Variant data .
Plz read FAQ first it won't take more than 1 minute.
http://forum.gsmhosting.com/vbb/showthread.php?t=903537
 
Old 01-17-2010, 10:13   #9 (permalink)
No Life Poster
 
*Diablo*'s Avatar
 
Join Date: Mar 2004
Location: pccomp
Age: 42
Posts: 1,399
Member: 59173
Status: Offline
Sonork: 100.1585568
Thanks Meter: 225
Donate money to this user
Quote:
Originally Posted by Umair Rashid View Post
"Recover CERT" does not repair Superdongle Key !!!
This button is used to rebuild HWC CCc and Variant data .
Plz read FAQ first it won't take more than 1 minute.
http://forum.gsmhosting.com/vbb/showthread.php?t=903537
c log pls
its not repair even HWC CCC
 
Old 01-17-2010, 19:10   #10 (permalink)
Freak Poster
 
digicomm's Avatar
 
Join Date: Dec 2006
Posts: 475
Member: 413149
Status: Offline
Thanks Meter: 83
yes its not repair even HWC . see my log


RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 16E00117FA336B566AA2F17155FED5924086CE11
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: 00EC 22FE - 0000 6921 [Samsung K8S5615ETA,256 Mbits] type: NOR,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
ExtDEVC: FFFF 0000 - 0000 0000
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: 7F7E6491E8D30494B45630BB3A8599F4E1C674C9
Reading RAP NPC (0x168 bytes)

Begin Certificate Request ...
Connecting to server ...OK, Login ...
Query done with status: OK
Updating PRODUCTCODE (0538331)... OK
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 16E00117FA336B566AA2F17155FED5924086CE11
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: 00EC 22FE - 0000 6921 [Samsung K8S5615ETA,256 Mbits] type: NOR,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
ExtDEVC: FFFF 0000 - 0000 0000
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: 7F7E6491E8D30494B45630BB3A8599F4E1C674C9
Updating CMT NPC ...OK
Updating CMT CCC ...OK
Updating CMT HWC ...failed, Result: 06C0000000117200
Certificate programmed successfully !
 
Old 01-17-2010, 19:14   #11 (permalink)
Freak Poster
 
abuscoking's Avatar
 
Join Date: Feb 2008
Location: Germany
Posts: 118
Member: 705320
Status: Offline
Thanks Meter: 27
I´ve unlocked a lot of Nokia 6300 with JAF BB5 so try JAF.
 
Closed Thread

Bookmarks

« Previous Thread | Next Thread »

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
very big problem in bb5 nobody helping me in this forum sanjayvikas Nokia Base Band 5 ( BB-5 ) 3 09-22-2010 19:03
problem in BB5 flashing. mayank bajaj Nokia Base Band 5 ( BB-5 ) 10 08-24-2008 13:51
Post Here The Method You Use In Preventing/solving The Problem In Bb5 Unlocking amar22ado Nokia Base Band 5 ( BB-5 ) 23 08-10-2007 11:19

 



All times are GMT +1. The time now is 19:53.

Contact Us - GSM-Forum - Archive - Top


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.35544 seconds with 9 queries

SEO by vBSEO