Recover Certificate on N70 successful by MXKEY - GSM-Forum

palash_c6 · 01-22-2010, 07:35

Recover Certificate on N70 successful by MXKEY

1ST DO BACKUP RPL(ALL SECTION) BEFORE RECOVER CERT

LOG:-

Quote:

APE Data :
SYSTEM ASIC ID: 17100701 [OMAP1710 ver: 1.1]
ASIC MODE ID: 00
PUBLIC ID: B130E94E8C6E1DD9BA7841450A9FBCAE76400585
ROOT KEY HASH: 2C05369F57CC3C4CF9E783E83D9B512B00000000
ROM ID: AB5E4ADB27A06946
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006000C192101002200 [RAP3G ver: PA 2.2]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 1B500118D5196851E8A107E564324562054BB09E
ASIC MODE ID: 00
ROOT KEY HASH: E9EFF4BFAA5393217CA6B17755FC3E14
ROM ID: F28A211FCEA7B19D
SecondaryBoot: rap3gv2_2nd.fg [BB5] version: 1.21.0 revision: 0.0 size: 0x3D00
Supported RAP Ids: 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200
FlashID0: 00EC 2250 - 0000 0121 [Samsung K8S6415ETB,64 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: 0F72BF9DE5D6711B3B1133EBCAB5914FA419C78D
SecondaryBoot: helen3_2nd.fg [BB5] version: 1.35.0 revision: 0.0 size: 0x3500
Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
FlashID0: 0098 0036 - 00A5 00C0 [Toshiba 512 DDP NAND,512 Mbits] type: NAND,APE
ALG [35]: OMAP1610 GBBM-1.8.1 ALG
ExtBUSC: 0002 0000 0006 0000 0000 0000 0000 0000
Algorithm: h3_sam_nand_gbbm.fg [OMAP1610 GBBM-1.8.1 ALG] version: 1.33.0 revision: 0.0 size: 0xA908
Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
APE PAPUBKEYS HASH: 0F72BF9DE5D6711B3B1133EBCAB5914FA419C78D
Reading RAP NPC (0x168 bytes)

Begin Certificate Request ...
Connecting to server ...OK, Login ...
Query done with status: OK
Updating PRODUCTCODE (0539240)... OK
APE Data :
SYSTEM ASIC ID: 17100701 [OMAP1710 ver: 1.1]
ASIC MODE ID: 00
PUBLIC ID: B130E94E8C6E1DD9BA7841450A9FBCAE76400585
ROOT KEY HASH: 2C05369F57CC3C4CF9E783E83D9B512B00000000
ROM ID: AB5E4ADB27A06946
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006000C192101002200 [RAP3G ver: PA 2.2]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 1B500118D5196851E8A107E564324562054BB09E
ASIC MODE ID: 00
ROOT KEY HASH: E9EFF4BFAA5393217CA6B17755FC3E14
ROM ID: F28A211FCEA7B19D
SecondaryBoot: rap3gv2_2nd.fg [BB5] version: 1.21.0 revision: 0.0 size: 0x3D00
Supported RAP Ids: 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200
FlashID0: 00EC 2250 - 0000 0121 [Samsung K8S6415ETB,64 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: 0F72BF9DE5D6711B3B1133EBCAB5914FA419C78D
SecondaryBoot: helen3_2nd.fg [BB5] version: 1.35.0 revision: 0.0 size: 0x3500
Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
FlashID0: 0098 0036 - 00A5 00C0 [Toshiba 512 DDP NAND,512 Mbits] type: NAND,APE
ALG [35]: OMAP1610 GBBM-1.8.1 ALG
ExtBUSC: 0002 0000 0006 0000 0000 0000 0000 0000
Algorithm: h3_sam_nand_gbbm.fg [OMAP1610 GBBM-1.8.1 ALG] version: 1.33.0 revision: 0.0 size: 0xA908
Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
APE PAPUBKEYS HASH: 0F72BF9DE5D6711B3B1133EBCAB5914FA419C78D
Updating CMT NPC ...OK
Updating CMT VARIANT ...OK
Certificate programmed successfully !

PROCESS:-

THANKS TO MX KEY TEAM

P@lash_c6

lilong_lee · 01-22-2010, 07:51

We work perfectly all bb5 is free only mxkey can repair and recover thank for good test report

Paki Mobile · 01-22-2010, 10:55

i have 6300 imei problem 123456789? n simlock ok but i cant recover ceritficate

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 ...
ERROR: No certificate found in the database !

Zegarek · 01-22-2010, 11:02

MxKey repair Cert only no imei you mast ask to rpl ...

palash_c6 · 01-22-2010, 12:50

Quote:

Originally Posted by paki mobile

i have 6300 imei problem 123456789? N simlock ok but i cant recover ceritficate

Code:

bro, already  your phone's imei is damaged(12345****??).
so, u must have to use ask to rpl service(not available now).
Recover certificate on mx key is used for those phones which have 
security test failed but all(supperdongle key,simlocks,) is ok

P@lash_c6

.::Naseer Al-islam::. · 01-22-2010, 13:01

[QUOTE=palash_c6;5299732]

Code:

bro, already  your phone's imei is damaged(12345****??).
so, u must have to use ask to rpl service(not available now).
Recover certificate on mx key is used for those phones which have 
security test failed but all(supperdongle key,simlocks,) is ok

am not agree with you look here bro

palash_c6 · 01-22-2010, 13:11

goodman1980

Code:

ITS OK. I AM  ALSO FACING PROBLEM LIKE YOU WITH E71.
BUT I HAVE REPAIRED N70(SECURITY TEST FAILED)

JACKSON999 · 01-22-2010, 13:26

APE Data :
SYSTEM ASIC ID: 17100701 [OMAP1710 ver: 1.1]
ASIC MODE ID: 00
PUBLIC ID: BB24C12370F253EC223D502E3AE4DCAA64C1BDBA
ROOT KEY HASH: 2C05369F57CC3C4CF9E783E83D9B512B00000000
ROM ID: AB5E4ADB27A06946
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006000C192101002200 [RAP3G ver: PA 2.2]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 12C0011935726B512EA63654A070BFAF24B5C3F0
ASIC MODE ID: 00
ROOT KEY HASH: E9EFF4BFAA5393217CA6B17755FC3E14
ROM ID: F28A211FCEA7B19D
SecondaryBoot: rap3gv2_2nd.fg [BB5] version: 1.21.0 revision: 0.0 size: 0x3D00
Supported RAP Ids: 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200
FlashID0: 00EC 2250 - 0000 0121 [Samsung K8S6415ETB,64 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: 0F72BF9DE5D6711B3B1133EBCAB5914FA419C78D
SecondaryBoot: helen3_2nd.fg [BB5] version: 1.35.0 revision: 0.0 size: 0x3500
Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
FlashID0: 00EC 0036 - 005A 003F [Samsung KAL00R00EM-DGXX,512 Mbits] type: NAND,APE
ALG [35]: OMAP1610 GBBM-1.8.1 ALG
ExtBUSC: 0002 0000 0006 0000 0000 0000 0000 0000
Algorithm: h3_sam_nand_gbbm.fg [OMAP1610 GBBM-1.8.1 ALG] version: 1.33.0 revision: 0.0 size: 0xA908
Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
APE PAPUBKEYS HASH: 0F72BF9DE5D6711B3B1133EBCAB5914FA419C78D
Reading RAP NPC (0x168 bytes)

Begin Certificate Request ...
Connecting to server ...OK, Login ...
Query done with status: OK
Updating PRODUCTCODE (0534441)... OK
APE Data :
SYSTEM ASIC ID: 17100701 [OMAP1710 ver: 1.1]
ASIC MODE ID: 00
PUBLIC ID: BB24C12370F253EC223D502E3AE4DCAA64C1BDBA
ROOT KEY HASH: 2C05369F57CC3C4CF9E783E83D9B512B00000000
ROM ID: AB5E4ADB27A06946
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006000C192101002200 [RAP3G ver: PA 2.2]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 12C0011935726B512EA63654A070BFAF24B5C3F0
ASIC MODE ID: 00
ROOT KEY HASH: E9EFF4BFAA5393217CA6B17755FC3E14
ROM ID: F28A211FCEA7B19D
SecondaryBoot: rap3gv2_2nd.fg [BB5] version: 1.21.0 revision: 0.0 size: 0x3D00
Supported RAP Ids: 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200
FlashID0: 00EC 2250 - 0000 0121 [Samsung K8S6415ETB,64 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: 0F72BF9DE5D6711B3B1133EBCAB5914FA419C78D
SecondaryBoot: helen3_2nd.fg [BB5] version: 1.35.0 revision: 0.0 size: 0x3500
Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
FlashID0: 00EC 0036 - 005A 003F [Samsung KAL00R00EM-DGXX,512 Mbits] type: NAND,APE
ALG [35]: OMAP1610 GBBM-1.8.1 ALG
ExtBUSC: 0002 0000 0006 0000 0000 0000 0000 0000
Algorithm: h3_sam_nand_gbbm.fg [OMAP1610 GBBM-1.8.1 ALG] version: 1.33.0 revision: 0.0 size: 0xA908
Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
APE PAPUBKEYS HASH: 0F72BF9DE5D6711B3B1133EBCAB5914FA419C78D
Updating CMT NPC ...OK
Updating CMT VARIANT ...failed, Result: 0000000000000000
Certificate programmed successfully !

01-22-2010, 13:01	#6 (permalink)
.::Naseer Al-islam::. Cheater -Don't Deal with him- Join Date: Feb 2007 Location: Palestine Posts: 2,068 Member: 452256 Status: Offline Sonork: 100.1651051 Thanks Meter: 587	[QUOTE=palash_c6;5299732] Code: bro, already your phone's imei is damaged(12345****??). so, u must have to use ask to rpl service(not available now). Recover certificate on mx key is used for those phones which have security test failed but all(supperdongle key,simlocks,) is ok am not agree with you look here bro

01-22-2010, 13:11	#7 (permalink)
palash_c6 No Life Poster Join Date: Dec 2007 Location: OrbitGsm.Com Posts: 570 Member: 650840 Status: Offline Thanks Meter: 622	goodman1980 Code: ITS OK. I AM ALSO FACING PROBLEM LIKE YOU WITH E71. BUT I HAVE REPAIRED N70(SECURITY TEST FAILED)

01-22-2010, 13:26	#8 (permalink)
JACKSON999 Freak Poster Join Date: Aug 2007 Age: 36 Posts: 317 Member: 558699 Status: Offline Thanks Meter: 21	My N70 not recover APE Data : SYSTEM ASIC ID: 17100701 [OMAP1710 ver: 1.1] ASIC MODE ID: 00 PUBLIC ID: BB24C12370F253EC223D502E3AE4DCAA64C1BDBA ROOT KEY HASH: 2C05369F57CC3C4CF9E783E83D9B512B00000000 ROM ID: AB5E4ADB27A06946 RAP Data : SYSTEM ASIC ID: 000000010000022600010006000C192101002200 [RAP3G ver: PA 2.2] EM0 ID: 00000232 EM1 ID: 00000353 PUBLIC ID: 12C0011935726B512EA63654A070BFAF24B5C3F0 ASIC MODE ID: 00 ROOT KEY HASH: E9EFF4BFAA5393217CA6B17755FC3E14 ROM ID: F28A211FCEA7B19D SecondaryBoot: rap3gv2_2nd.fg [BB5] version: 1.21.0 revision: 0.0 size: 0x3D00 Supported RAP Ids: 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200 FlashID0: 00EC 2250 - 0000 0121 [Samsung K8S6415ETB,64 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: 0F72BF9DE5D6711B3B1133EBCAB5914FA419C78D SecondaryBoot: helen3_2nd.fg [BB5] version: 1.35.0 revision: 0.0 size: 0x3500 Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708 FlashID0: 00EC 0036 - 005A 003F [Samsung KAL00R00EM-DGXX,512 Mbits] type: NAND,APE ALG [35]: OMAP1610 GBBM-1.8.1 ALG ExtBUSC: 0002 0000 0006 0000 0000 0000 0000 0000 Algorithm: h3_sam_nand_gbbm.fg [OMAP1610 GBBM-1.8.1 ALG] version: 1.33.0 revision: 0.0 size: 0xA908 Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708 APE PAPUBKEYS HASH: 0F72BF9DE5D6711B3B1133EBCAB5914FA419C78D Reading RAP NPC (0x168 bytes) Begin Certificate Request ... Connecting to server ...OK, Login ... Query done with status: OK Updating PRODUCTCODE (0534441)... OK APE Data : SYSTEM ASIC ID: 17100701 [OMAP1710 ver: 1.1] ASIC MODE ID: 00 PUBLIC ID: BB24C12370F253EC223D502E3AE4DCAA64C1BDBA ROOT KEY HASH: 2C05369F57CC3C4CF9E783E83D9B512B00000000 ROM ID: AB5E4ADB27A06946 RAP Data : SYSTEM ASIC ID: 000000010000022600010006000C192101002200 [RAP3G ver: PA 2.2] EM0 ID: 00000232 EM1 ID: 00000353 PUBLIC ID: 12C0011935726B512EA63654A070BFAF24B5C3F0 ASIC MODE ID: 00 ROOT KEY HASH: E9EFF4BFAA5393217CA6B17755FC3E14 ROM ID: F28A211FCEA7B19D SecondaryBoot: rap3gv2_2nd.fg [BB5] version: 1.21.0 revision: 0.0 size: 0x3D00 Supported RAP Ids: 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200 FlashID0: 00EC 2250 - 0000 0121 [Samsung K8S6415ETB,64 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: 0F72BF9DE5D6711B3B1133EBCAB5914FA419C78D SecondaryBoot: helen3_2nd.fg [BB5] version: 1.35.0 revision: 0.0 size: 0x3500 Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708 FlashID0: 00EC 0036 - 005A 003F [Samsung KAL00R00EM-DGXX,512 Mbits] type: NAND,APE ALG [35]: OMAP1610 GBBM-1.8.1 ALG ExtBUSC: 0002 0000 0006 0000 0000 0000 0000 0000 Algorithm: h3_sam_nand_gbbm.fg [OMAP1610 GBBM-1.8.1 ALG] version: 1.33.0 revision: 0.0 size: 0xA908 Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708 APE PAPUBKEYS HASH: 0F72BF9DE5D6711B3B1133EBCAB5914FA419C78D Updating CMT NPC ...OK Updating CMT VARIANT ...failed, Result: 0000000000000000 Certificate programmed successfully !

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
1100 IMEI Repair Successfully by MXkey	nabindra	Nokia Hardware & Hardware Repair	6	05-18-2012 05:38
camera on standby repaired by mxkey	mscomp	MXKEY Nokia Flasher and Unlocker (by Alim Hape)	13	09-03-2010 09:31
blackberry 8310 unlock success by MXKEY (Answered)	dasmeshmehatpur	MXKEY Blackberry Flasher and Unlocker (by Alim Hape)	10	07-27-2010 19:25
5130 Flash dead USB Success by Mxkey !	boycrazy	MXKEY Nokia Flasher and Unlocker (by Alim Hape)	0	12-21-2009 09:59
PLEASE HELP: HOW TO RECOVER CERTIFICATE ON K700i	AbdulKadir	SonyEricsson (USB-Smart)	6	06-24-2006 21:28

01-22-2010, 07:51	#2 (permalink)
lilong_lee No Life Poster Join Date: Jul 2009 Location: philippines now here in U.A.E Age: 38 Posts: 2,852 Member: 1070665 Status: Offline Sonork: 100.1636802 Thanks Meter: 572	We work perfectly all bb5 is free only mxkey can repair and recover thank for good test report

01-22-2010, 10:55	#3 (permalink)
Paki Mobile No Life Poster Join Date: Jan 2004 Location: Karachi, Pakistan Age: 52 Posts: 1,245 Member: 50106 Status: Offline Sonork: 100.109487 Thanks Meter: 224	i have 6300 imei problem 123456789? n simlock ok but i cant recover ceritficate 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 ... ERROR: No certificate found in the database !

01-22-2010, 11:02	#4 (permalink)
Zegarek No Life Poster Join Date: Jul 2007 Location: Poland Age: 43 Posts: 972 Member: 551345 Status: Offline Sonork: 100.1590161 Thanks Meter: 319	MxKey repair Cert only no imei you mast ask to rpl ...