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 i have n73 with contact retailer Look at this plzz (ANSWERED)
Register FAQDonate Forum Rules Root any Device ★iPhone Unlock★ ★ Direct Codes ★ Direct Unlock Source


Reply
Page 1 of 2 1 2
 
LinkBack Thread Tools Display Modes
Old 02-12-2012, 06:40   #1 (permalink)
Product Manager
 
Join Date: Jan 2012
Posts: 357
Member: 1710203
Status: Offline
Thanks Meter: 7
i have n73 with contact retailer Look at this plzz (ANSWERED)

have n73 with contact retailer

i do every thing also full erase phone

i think there is a problem with product code

Here is scan log's
----------------------------
Phone type: RM-132 (Nokia N73)
SW version: V 05wk47v51.4 29-08-07 RM-132 (c) Nokia.
Imei plain: 35419802361565-5
Product code: 0529607
Battery voltage: 4694 mV, current: 124 mA
ApeCoreSw: V 4.0738.3.1.1
Language Pack:
- not available.
SLPA ver[1]: PA_SL (15 digit NCK)

SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
CMLA_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!
Imei net: 354198023615655
Version: SIMLOCK SERVER VERSION 63
Counter: 0/3, 0/10

CONFIG_DATA: 2440700000000000
PROFILE_BITS: 0000000000000000

BLOCK1: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK2: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK3: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK4: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK5: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK6: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK7: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN

i do all that

Sd Repair pm auto
write 1.309 with sx4

SUPERDONGLE authorized !
Now you can write RFBB/PM data to the phone.
Done.
Phone authenticated to SUPERDONGLE already.
SERVER->MXKEY - BLADE X at host2, agent version 1.2 revision 0.2
Updating RFBB data ...
Writing section 1...
Writing section 309...
Done.

BUT STILL SAME PROBLEM

here is the log when recover cert

APE Data :
SYSTEM ASIC ID: 17100708 [OMAP1710 ver: 2.0]
ASIC MODE ID: 00
PUBLIC ID: 3B645B060F0EDC3D1A08E0216F0D136BF5005A96
ROOT KEY HASH: 49A97E826B93BA20B7ED0B082475C00500000000
ROM ID: 1DFD66132C872FD4
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101013000
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 18900005B0DC4F506AE55B11060BBDB2E266B1FC
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: RAP3Gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
eBB5ProtocolType: OLD
Storage0: 00EC 22E8 - 0000 6921 [Samsung K8S2815ETB,128 Mbits] type: FLASH,NOR, asic:CMT
Storage content: 0000 0000 0000 0000 0000 0000 0000 0000
Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT
TransmissionMode: 16Bit
Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 1.40.0 revision: 0.0 size: 0x22C10
Supported 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
CMT PAPUBKEYS HASH: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
TransmissionMode: DDR&TX2

Begin Certificate Request ...

[InternalErrorFault] CERT [0554355] data not available for this phone (case id=0xCE01)
And Here is BB5 cert validation

APE Data :
SYSTEM ASIC ID: 17100708 [OMAP1710 ver: 2.0]
ASIC MODE ID: 00
PUBLIC ID: 3B645B060F0EDC3D1A08E0216F0D136BF5005A96
ROOT KEY HASH: 49A97E826B93BA20B7ED0B082475C00500000000
ROM ID: 1DFD66132C872FD4
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101013000
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 18900005B0DC4F506AE55B11060BBDB2E266B1FC
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: RAP3Gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
eBB5ProtocolType: OLD
Storage0: 00EC 22E8 - 0000 6921 [Samsung K8S2815ETB,128 Mbits] type: FLASH,NOR, asic:CMT
Storage content: 0000 0000 0000 0000 0000 0000 0000 0000
Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT
TransmissionMode: 16Bit
Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 1.40.0 revision: 0.0 size: 0x22C10
Supported 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
CMT PAPUBKEYS HASH: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
TransmissionMode: DDR&TX2
SecondaryBoot: helen3_2nd.fg [BB5] version: 1.35.0 revision: 0.0 size: 0x3500
Supported Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
Storage0: 00EC 00A1 - 0080 0015 [Samsung KAL00T00EM-DGYY/66,1 Gbits] type: FLASH,NAND, asic:APE
Storage content: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
Algorithm: h3_sam_nand_xsr.fg [OMAP1710 UNISTORE-II-1.2.1 ALG] version: 1.49.0 revision: 0.0 size: 0x13AA0
Supported Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
APE PAPUBKEYS HASH: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Reading CMT NPC (0x168 bytes).
Original Product Code: 0554355
Reading CMT VARIANT (0xB8 bytes).
Product Code:
Product Code missmatch !
Reading CMT CCC (0x0 bytes).
Reading CMT HWC (0x0 bytes).

PLZ HELP ME MASTERS

Shibu


  Reply With Quote
Old 02-12-2012, 06:48   #2 (permalink)
Product Supporter
 
Prem_India's Avatar
 
Join Date: Mar 2008
Location: India
Posts: 1,959
Member: 718725
Status: Offline
Sonork: 100.1604953 QQ 2339690693
Thanks Meter: 6,701
Same Problem Here

I have N73 This Time Same COND.

SECURITY_TEST failed!


try All Method SD repair. Simlock Repair PM AUTH.. But Same

  Reply With Quote
The Following User Says Thank You to Prem_India For This Useful Post:
Old 02-12-2012, 06:50   #3 (permalink)
No Life Poster
 
Tarikul Islam's Avatar
 
Join Date: May 2010
Location: BaNgLaDeSh
Posts: 583
Member: 1310148
Status: Offline
Sonork: 100.1601928
Thanks Meter: 293
Thumbs up write this rpl
Write Rpl without NPC Data
Take backup rpl then write

N73_without_NPC_DATA__made_by_MxKey.rar - 4shared.com - online file sharing and storage - download

It Showing RM-132

http://www.4shared.com/file/9qbZpbgd/N73RM-132.html

Write this pm with Supersd auth
post result
  Reply With Quote
Old 02-12-2012, 06:57   #4 (permalink)
Product Manager
 
Join Date: Jan 2012
Posts: 357
Member: 1710203
Status: Offline
Thanks Meter: 7
Quote:
Originally Posted by Tarikul Islam View Post
Write Rpl without NPC Data
Take backup rpl then write

N73_without_NPC_DATA__made_by_MxKey.rar - 4shared.com - online file sharing and storage - download

It Showing RM-132

N73.RM-132.pm - 4shared.com - online file sharing and storage - download

Write this pm with Supersd auth
post result

Bro Its Rm 132 Type Not Rm 133

And i try to write ( clone Rpl )

Here Is Logs Problem Still Same

Phone type: RM-132 (Nokia N73)
SW version: V 05wk47v51.4 29-08-07 RM-132 (c) Nokia.
Imei plain: 35419802361565-5
Product code: 0529607
Battery voltage: 4885 mV, current: 56 mA
Language Pack:
- not available.
SLPA ver[1]: PA_SL (15 digit NCK)

SIMLOCK seems to be valid
SUPERDONGLE_KEY[MX] seems to be valid
CMLA_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!


Imei net: 354198023615655
Version: SIMLOCK SERVER VERSION 63
Counter: 0/3, 0/10

CONFIG_DATA: 2440700000000000
PROFILE_BITS: 0000000000000000

BLOCK1: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK2: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK3: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK4: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK5: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK6: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK7: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
  Reply With Quote
Old 02-12-2012, 06:59   #5 (permalink)
No Life Poster
 
specta's Avatar
 
Join Date: Oct 2009
Posts: 1,130
Member: 1149800
Status: Offline
Thanks Meter: 211
Quote:
Originally Posted by Shahid kapoor View Post
have n73 with contact retailer

i do every thing also full erase phone

i think there is a problem with product code

Here is scan log's
----------------------------
Phone type: RM-132 (Nokia N73)
SW version: V 05wk47v51.4 29-08-07 RM-132 (c) Nokia.
Imei plain: 35419802361565-5
Product code: 0529607
Battery voltage: 4694 mV, current: 124 mA
ApeCoreSw: V 4.0738.3.1.1
Language Pack:
- not available.
SLPA ver[1]: PA_SL (15 digit NCK)

SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
CMLA_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!
Imei net: 354198023615655
Version: SIMLOCK SERVER VERSION 63
Counter: 0/3, 0/10

CONFIG_DATA: 2440700000000000
PROFILE_BITS: 0000000000000000

BLOCK1: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK2: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK3: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK4: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK5: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK6: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK7: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN

i do all that

Sd Repair pm auto
write 1.309 with sx4

SUPERDONGLE authorized !
Now you can write RFBB/PM data to the phone.
Done.
Phone authenticated to SUPERDONGLE already.
SERVER->MXKEY - BLADE X at host2, agent version 1.2 revision 0.2
Updating RFBB data ...
Writing section 1...
Writing section 309...
Done.

BUT STILL SAME PROBLEM

here is the log when recover cert

APE Data :
SYSTEM ASIC ID: 17100708 [OMAP1710 ver: 2.0]
ASIC MODE ID: 00
PUBLIC ID: 3B645B060F0EDC3D1A08E0216F0D136BF5005A96
ROOT KEY HASH: 49A97E826B93BA20B7ED0B082475C00500000000
ROM ID: 1DFD66132C872FD4
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101013000
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 18900005B0DC4F506AE55B11060BBDB2E266B1FC
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: RAP3Gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
eBB5ProtocolType: OLD
Storage0: 00EC 22E8 - 0000 6921 [Samsung K8S2815ETB,128 Mbits] type: FLASH,NOR, asic:CMT
Storage content: 0000 0000 0000 0000 0000 0000 0000 0000
Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT
TransmissionMode: 16Bit
Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 1.40.0 revision: 0.0 size: 0x22C10
Supported 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
CMT PAPUBKEYS HASH: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
TransmissionMode: DDR&TX2

Begin Certificate Request ...

[InternalErrorFault] CERT [0554355] data not available for this phone (case id=0xCE01)
And Here is BB5 cert validation

APE Data :
SYSTEM ASIC ID: 17100708 [OMAP1710 ver: 2.0]
ASIC MODE ID: 00
PUBLIC ID: 3B645B060F0EDC3D1A08E0216F0D136BF5005A96
ROOT KEY HASH: 49A97E826B93BA20B7ED0B082475C00500000000
ROM ID: 1DFD66132C872FD4
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101013000
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 18900005B0DC4F506AE55B11060BBDB2E266B1FC
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: RAP3Gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
eBB5ProtocolType: OLD
Storage0: 00EC 22E8 - 0000 6921 [Samsung K8S2815ETB,128 Mbits] type: FLASH,NOR, asic:CMT
Storage content: 0000 0000 0000 0000 0000 0000 0000 0000
Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT
TransmissionMode: 16Bit
Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 1.40.0 revision: 0.0 size: 0x22C10
Supported 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
CMT PAPUBKEYS HASH: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
TransmissionMode: DDR&TX2
SecondaryBoot: helen3_2nd.fg [BB5] version: 1.35.0 revision: 0.0 size: 0x3500
Supported Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
Storage0: 00EC 00A1 - 0080 0015 [Samsung KAL00T00EM-DGYY/66,1 Gbits] type: FLASH,NAND, asic:APE
Storage content: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
Algorithm: h3_sam_nand_xsr.fg [OMAP1710 UNISTORE-II-1.2.1 ALG] version: 1.49.0 revision: 0.0 size: 0x13AA0
Supported Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
APE PAPUBKEYS HASH: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Reading CMT NPC (0x168 bytes).
Original Product Code: 0554355
Reading CMT VARIANT (0xB8 bytes).
Product Code:
Product Code missmatch !
Reading CMT CCC (0x0 bytes).
Reading CMT HWC (0x0 bytes).

PLZ HELP ME MASTERS

Shibu



probably pm 1 & 309 not written correctly, u should try write it manually from pm file bro

click repair sd, when superdongle is ok, if pop up menu ask u to write from rfbb data, click NO. DO NOT tick write from server, load file pm N73 (full or just 1 & 309), write it manually...


i feel like dejavu keep giving such instructions again and again, lol...


next search first bro, check here too http://forum.gsmhosting.com/vbb/f550...ailed-1214364/


good luck bro


br
  Reply With Quote
Old 02-12-2012, 06:59   #6 (permalink)
No Life Poster
 
mobilehelper's Avatar
 
Join Date: Nov 2011
Posts: 1,921
Member: 1696653
Status: Offline
Sonork: 100.1638410
Thanks Meter: 809
Quote:
Originally Posted by Shahid kapoor View Post
have n73 with contact retailer

i do every thing also full erase phone

i think there is a problem with product code

Here is scan log's
----------------------------
Phone type: RM-132 (Nokia N73)
SW version: V 05wk47v51.4 29-08-07 RM-132 (c) Nokia.
Imei plain: 35419802361565-5
Product code: 0529607
Battery voltage: 4694 mV, current: 124 mA
ApeCoreSw: V 4.0738.3.1.1
Language Pack:
- not available.
SLPA ver[1]: PA_SL (15 digit NCK)

SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
CMLA_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!
Imei net: 354198023615655
Version: SIMLOCK SERVER VERSION 63
Counter: 0/3, 0/10

CONFIG_DATA: 2440700000000000
PROFILE_BITS: 0000000000000000

BLOCK1: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK2: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK3: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK4: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK5: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK6: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK7: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN

i do all that

Sd Repair pm auto
write 1.309 with sx4

SUPERDONGLE authorized !
Now you can write RFBB/PM data to the phone.
Done.
Phone authenticated to SUPERDONGLE already.
SERVER->MXKEY - BLADE X at host2, agent version 1.2 revision 0.2
Updating RFBB data ...
Writing section 1...
Writing section 309...
Done.

BUT STILL SAME PROBLEM

here is the log when recover cert

APE Data :
SYSTEM ASIC ID: 17100708 [OMAP1710 ver: 2.0]
ASIC MODE ID: 00
PUBLIC ID: 3B645B060F0EDC3D1A08E0216F0D136BF5005A96
ROOT KEY HASH: 49A97E826B93BA20B7ED0B082475C00500000000
ROM ID: 1DFD66132C872FD4
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101013000
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 18900005B0DC4F506AE55B11060BBDB2E266B1FC
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: RAP3Gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
eBB5ProtocolType: OLD
Storage0: 00EC 22E8 - 0000 6921 [Samsung K8S2815ETB,128 Mbits] type: FLASH,NOR, asic:CMT
Storage content: 0000 0000 0000 0000 0000 0000 0000 0000
Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT
TransmissionMode: 16Bit
Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 1.40.0 revision: 0.0 size: 0x22C10
Supported 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
CMT PAPUBKEYS HASH: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
TransmissionMode: DDR&TX2

Begin Certificate Request ...

[InternalErrorFault] CERT [0554355] data not available for this phone (case id=0xCE01)
And Here is BB5 cert validation

APE Data :
SYSTEM ASIC ID: 17100708 [OMAP1710 ver: 2.0]
ASIC MODE ID: 00
PUBLIC ID: 3B645B060F0EDC3D1A08E0216F0D136BF5005A96
ROOT KEY HASH: 49A97E826B93BA20B7ED0B082475C00500000000
ROM ID: 1DFD66132C872FD4
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101013000
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 18900005B0DC4F506AE55B11060BBDB2E266B1FC
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: RAP3Gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
eBB5ProtocolType: OLD
Storage0: 00EC 22E8 - 0000 6921 [Samsung K8S2815ETB,128 Mbits] type: FLASH,NOR, asic:CMT
Storage content: 0000 0000 0000 0000 0000 0000 0000 0000
Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT
TransmissionMode: 16Bit
Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 1.40.0 revision: 0.0 size: 0x22C10
Supported 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
CMT PAPUBKEYS HASH: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
TransmissionMode: DDR&TX2
SecondaryBoot: helen3_2nd.fg [BB5] version: 1.35.0 revision: 0.0 size: 0x3500
Supported Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
Storage0: 00EC 00A1 - 0080 0015 [Samsung KAL00T00EM-DGYY/66,1 Gbits] type: FLASH,NAND, asic:APE
Storage content: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
Algorithm: h3_sam_nand_xsr.fg [OMAP1710 UNISTORE-II-1.2.1 ALG] version: 1.49.0 revision: 0.0 size: 0x13AA0
Supported Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
APE PAPUBKEYS HASH: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Reading CMT NPC (0x168 bytes).
Original Product Code: 0554355
Reading CMT VARIANT (0xB8 bytes).
Product Code:
Product Code missmatch !
Reading CMT CCC (0x0 bytes).
Reading CMT HWC (0x0 bytes).

PLZ HELP ME MASTERS

Shibu


1st try recover cert.after ppmuthod,ya supersd repair ya sdrepair,repair is ok after load prfect pm file without 308 or write and after reset all ur problem will be solve.
  Reply With Quote
Old 02-12-2012, 07:05   #7 (permalink)
No Life Poster
 
Tarikul Islam's Avatar
 
Join Date: May 2010
Location: BaNgLaDeSh
Posts: 583
Member: 1310148
Status: Offline
Sonork: 100.1601928
Thanks Meter: 293
Thumbs up
Quote:
Originally Posted by Shahid kapoor View Post
Bro Its Rm 132 Type Not Rm 133

And i try to write ( clone Rpl )

Here Is Logs Problem Still Same

Phone type: RM-132 (Nokia N73)
SW version: V 05wk47v51.4 29-08-07 RM-132 (c) Nokia.
Imei plain: 35419802361565-5
Product code: 0529607
Battery voltage: 4885 mV, current: 56 mA
Language Pack:
- not available.
SLPA ver[1]: PA_SL (15 digit NCK)

SIMLOCK seems to be valid
SUPERDONGLE_KEY[MX] seems to be valid
CMLA_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!


Try this method post result

1. first backup rpl ( go > imei and security tab > imei rebuild > backup rpl)
2. erase old pm ( go > pm tab > erase )
3. Reset npc data ( go> imei and security tab> reset NPC data)( must backup rpl before do this)
4. Erase pm again (go > pm tab > erase )
5.Write rpl from backup ( go > imei and security tab > imei rebuild > restore imei)
6. go pm tab > super sd auth or pmm auth > than write good or modified pm ( must need pm 1 & 309)

7. erase pm again

8. Recover CERT ( go>imei and security tab> imei rebuild > recover cert)
  Reply With Quote
The Following User Says Thank You to Tarikul Islam For This Useful Post:
Old 02-12-2012, 07:09   #8 (permalink)
Product Manager
 
Join Date: Jan 2012
Posts: 357
Member: 1710203
Status: Offline
Thanks Meter: 7
Quote:
Originally Posted by specta View Post
probably pm 1 & 309 not written correctly, u should try write it manually from pm file bro

click repair sd, when superdongle is ok, if pop up menu ask u to write from rfbb data, click NO. DO NOT tick write from server, load file pm N73 (full or just 1 & 309), write it manually...


i feel like dejavu keep giving such instructions again and again, lol...


next search first bro, check here too http://forum.gsmhosting.com/vbb/f550...ailed-1214364/


good luck bro


br
I TRY THISS ALL ......HERE IS LOGS



MXKEY [FT SCR2000 0], SN: C08543B3
Using device: HTI, FW ver: 00.50, SN: 000014F4
Connection status: UHCI:HUB:USB 2.00 (Full-speed)
Driver: WinUSB, ver: 3.5.1.0
Module ver: 1.0.0.19798(05-01-2012), Library ver: 1.0.0.13703(05-01-2012)

Phone type: RM-132 (Nokia N73)
SW version: V 05wk47v51.4 29-08-07 RM-132 (c) Nokia.
ApeCoreSw: V 4.0738.3.1.1

Using cached productData.
PUBLIC ID: 18900005B0DC4F506AE55B11060BBDB2E266B1FC
PRIVATE ID: 7599724385F32B03B8531E44D1FAAB7F9FCB3861
Updating SUPERDONGLE_KEY ...OK
Authenticating to SUPERDONGLE ...
SUPERDONGLE authorized !
Now you can write RFBB/PM data to the phone.
Done.
Phone authenticated to SUPERDONGLE already.
Phone authenticated to SUPERDONGLE already.
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: 26, size 110 bytes written.
- Key: 28, size 98 bytes written.
- Key: 29, size 6 bytes written.
- Key: 31, size 98 bytes written.
- Key: 34, size 80 bytes written.
- Key: 44, size 182 bytes written.
- 239 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.
Completed in 1.781


Phone type: RM-132 (Nokia N73)
SW version: V 05wk47v51.4 29-08-07 RM-132 (c) Nokia.
Imei plain: 35419802361565-5
Product code: 0529607
Battery voltage: 4699 mV, current: 154 mA
ApeCoreSw: V 4.0738.3.1.1
Language Pack:
- not available.
SLPA ver[1]: PA_SL (15 digit NCK)

SIMLOCK seems to be valid
SUPERDONGLE_KEY[MX] seems to be valid
CMLA_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!
  Reply With Quote
Old 02-12-2012, 07:13   #9 (permalink)
Product Supporter
 
Prem_India's Avatar
 
Join Date: Mar 2008
Location: India
Posts: 1,959
Member: 718725
Status: Offline
Sonork: 100.1604953 QQ 2339690693
Thanks Meter: 6,701
Recover CERT


APE Data :
SYSTEM ASIC ID: 17100708 [OMAP1710 ver: 2.0]
ASIC MODE ID: 00
PUBLIC ID: 4E4769A66651E1C435AD1619199C2D05B0A15374
ROOT KEY HASH: 49A97E826B93BA20B7ED0B082475C00500000000
ROM ID: 1DFD66132C872FD4
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101003000 [RAP3G ver: PA 3.0]
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 08F0010BEFF301544E164371B431C37E92DC5372
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: RAP3Gv3_2nd.fg [BB5] version: 9.11.1 revision: 0.0 size: 0x3C00
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
eBB5ProtocolType: OLD
Storage0: 00EC 22E8 - 0000 6921 [Samsung K8S2815ETB,128 Mbits] type: FLASH,NOR, asic:CMT
Storage content: 0000 0000 0000 0000 0000 0000 0000 0000
Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT
TransmissionMode: 16Bit
Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 9.50.0 revision: 0.0 size: 0x23010
Supported 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
CMT PAPUBKEYS HASH: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
TransmissionMode: DDR&TX2

Begin Certificate Request ...

[InternalErrorFault] CERT [0539295] data not available for this phone (case id=0xCE01)
  Reply With Quote
Old 02-12-2012, 07:44   #10 (permalink)
Insane Poster
 
Join Date: Oct 2011
Location: pakistan m.b.din
Posts: 97
Member: 1678694
Status: Offline
Sonork: 100.1602333
Thanks Meter: 8
n73 contact retalar proble solve
write pm by maxkey online setup2:unlock phone mobile ok
result send
  Reply With Quote
Old 02-12-2012, 08:03   #11 (permalink)
No Life Poster
 
rahihimkhan's Avatar
 
Join Date: Oct 2007
Location: Dera Ismail Khan (KPK) Pak
Posts: 2,544
Member: 613449
Status: Offline
Sonork: 100.1614074
Thanks Meter: 634
fast backup rpl , full erase wjth hwk with erase files , writhe full pm,write rpl , super dongel and post res
  Reply With Quote
Old 02-12-2012, 08:14   #12 (permalink)
Product Supporter
 
Prem_India's Avatar
 
Join Date: Mar 2008
Location: India
Posts: 1,959
Member: 718725
Status: Offline
Sonork: 100.1604953 QQ 2339690693
Thanks Meter: 6,701
See This

  Reply With Quote
Old 02-12-2012, 09:28   #13 (permalink)
No Life Poster
 
specta's Avatar
 
Join Date: Oct 2009
Posts: 1,130
Member: 1149800
Status: Offline
Thanks Meter: 211
Quote:
Originally Posted by Shahid kapoor View Post
I TRY THISS ALL ......HERE IS LOGS



MXKEY [FT SCR2000 0], SN: C08543B3
Using device: HTI, FW ver: 00.50, SN: 000014F4
Connection status: UHCI:HUB:USB 2.00 (Full-speed)
Driver: WinUSB, ver: 3.5.1.0
Module ver: 1.0.0.19798(05-01-2012), Library ver: 1.0.0.13703(05-01-2012)

Phone type: RM-132 (Nokia N73)
SW version: V 05wk47v51.4 29-08-07 RM-132 (c) Nokia.
ApeCoreSw: V 4.0738.3.1.1

Using cached productData.
PUBLIC ID: 18900005B0DC4F506AE55B11060BBDB2E266B1FC
PRIVATE ID: 7599724385F32B03B8531E44D1FAAB7F9FCB3861
Updating SUPERDONGLE_KEY ...OK
Authenticating to SUPERDONGLE ...
SUPERDONGLE authorized !
Now you can write RFBB/PM data to the phone.
Done.
Phone authenticated to SUPERDONGLE already.
Phone authenticated to SUPERDONGLE already.
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: 26, size 110 bytes written.
- Key: 28, size 98 bytes written.
- Key: 29, size 6 bytes written.
- Key: 31, size 98 bytes written.
- Key: 34, size 80 bytes written.
- Key: 44, size 182 bytes written.
- 239 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.
Completed in 1.781


Phone type: RM-132 (Nokia N73)
SW version: V 05wk47v51.4 29-08-07 RM-132 (c) Nokia.
Imei plain: 35419802361565-5
Product code: 0529607
Battery voltage: 4699 mV, current: 154 mA
ApeCoreSw: V 4.0738.3.1.1
Language Pack:
- not available.
SLPA ver[1]: PA_SL (15 digit NCK)

SIMLOCK seems to be valid
SUPERDONGLE_KEY[MX] seems to be valid
CMLA_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!

u write pm for rm-133 or rm-132 bro?

if not worked, i suggest u do erase, before erasing, u must have a full rpl back up. good luck bro




br
  Reply With Quote
The Following 2 Users Say Thank You to specta For This Useful Post:
Old 02-12-2012, 12:17   #14 (permalink)
Product Manager
 
Join Date: Jan 2012
Posts: 357
Member: 1710203
Status: Offline
Thanks Meter: 7
Not done.....................
  Reply With Quote
Old 02-13-2012, 07:05   #15 (permalink)
No Life Poster
 
iftikhar_246's Avatar
 
Join Date: Nov 2006
Location: pakistan
Age: 39
Posts: 3,224
Member: 384949
Status: Offline
Sonork: 1611265
Thanks Meter: 523
f1st rapeir super dongle
and super sd outh
and write good pm file
  Reply With Quote
Reply
Page 1 of 2 1 2

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
I neeeeed NCDS 2.0!!!! plzz!!!! ratzfatz Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 3 02-27-2022 22:12
How can I do a Welcome note for my 6110 a dosn't have any one ? Viper Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 8 06-27-2015 11:57
Help with 6110 paulomt1 Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 2 05-25-2009 16:29
Netmonitor with FBus???? ratzfatz Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 4 06-09-1999 17:04

 



All times are GMT +1. The time now is 01:45.

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

SEO by vBSEO