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)

Reply
 
LinkBack Thread Tools Display Modes
Old 04-24-2012, 17:48   #1 (permalink)
Junior Member
 
Join Date: Apr 2012
Posts: 9
Member: 1751744
Status: Offline
Thanks Meter: 0
n73 SECURITY_TEST failed! (ANSWERED)


n73 SECURITY_TEST failed!

ppm auth offline

Authenticating using [MX] security server ...
Connecting to server[main.mxkey.biz] ...Connection timed out
Connecting to server[main.mxkey.biz] ...Connection timed out
Connecting to server[main.mxkey.biz] ...Connection timed out

and recover cert

[InternalErrorFault] CERT [0539295] data not available for this phone (case id=0xCE01)

i Tried all solutions

This problem two days ago, I did't find a solution
i have 4 Mobile like that

When the server is work

  Reply With Quote
Old 04-25-2012, 14:13   #2 (permalink)
No Life Poster
 
gbluez's Avatar
 
Join Date: Jul 2004
Posts: 11,049
Member: 73565
Status: Offline
Thanks Meter: 5,062
NO NEED ANY SERVER.

Press Repair SD, follow on screen message.
All is stand alone, no need internet.
  Reply With Quote
Old 04-25-2012, 18:14   #3 (permalink)
Junior Member
 
Join Date: Apr 2012
Posts: 9
Member: 1751744
Status: Offline
Thanks Meter: 0
SIMLOCK seems to be valid
SUPERDONGLE_KEY[MX] seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!


Phone version(2.0628.0.0.1) outdated, selected version is: 4.812.4.0
Imei net: 353548026079427
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






SUPERDONGLE





Using cached productData.
PUBLIC ID: 1BD00116339602542D3FFC3C61DFB06DBD1B93A0
PRIVATE ID: 1C755E6354562B523F3D3B8974F38CD185448961
Updating SUPERDONGLE_KEY ...OK
Authenticating to SUPERDONGLE ...
SUPERDONGLE authorized !
Writing RFBB data: modules\{3EBAF427-9F55-419F-8A75-385DFC651169}\def\rfbb\N73_RM-133.txt ...
Writing RF settings to phone ...OK, finished. 20 Records found.
Writing BB settings to phone ...OK, finished. 9 Records found.
Done.



super sd auth


Using cached productData.
PUBLIC ID: 1BD00116339602542D3FFC3C61DFB06DBD1B93A0
PRIVATE ID: 1C755E6354562B523F3D3B8974F38CD185448961
Updating SUPERDONGLE_KEY ...OK
Authenticating to SUPERDONGLE ...
SUPERDONGLE authorized !
Writing RFBB data: modules\{3EBAF427-9F55-419F-8A75-385DFC651169}\def\rfbb\N73_RM-133.txt ...
Writing RF settings to phone ...OK, finished. 20 Records found.
Writing BB settings to phone ...OK, finished. 9 Records found.
Done.


write pm 1 _ 309




Writing PM from Node ...
Section: 1
- Key: 0, size 114 bytes written.
- Key: 2, size 98 bytes written.
- Key: 4, size 110 bytes written.
- Key: 6, size 98 bytes written.
- Key: 8, size 110 bytes written.
- Key: 13, size 98 bytes written.
- Key: 16, size 98 bytes written.
- Key: 18, size 98 bytes written.
- Key: 20, size 98 bytes written.
- Key: 22, size 16 bytes written.
- Key: 23, size 4 bytes written.
- Key: 24, size 84 bytes written.
- Key: 25, size 4 bytes written.
- Key: 26, size 110 bytes written.
- Key: 28, size 98 bytes written.
- Key: 29, size 6 bytes written.
- Key: 31, size 98 bytes written.
- Key: 33, size 36 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.486 s




after all those







SLPA ver[1]: PA_SL (15 digit NCK)

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


Phone version(2.0628.0.0.1) outdated, selected version is: 4.812.4.0
Imei net: 353548026079427
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






recover cert



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: 1BD00116339602542D3FFC3C61DFB06DBD1B93A0
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)







sx4 now online




Scanning local SX4 Card ...
No SX4 Card found.
SERVER->MXKEY - BLADE X at host2, agent version 1.2 revision 0.3

Authenticating using [MX] security server ...
Connecting to server[main.mxkey.biz] ...Connection timed out
Connecting to server[main.mxkey.biz] ...Wrong response to SD verify request
Retrying ...
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY SX4CARD - ID, hello 41.235.210.209
Wrong response to SD verify request
Retrying ...
Authenticating using [MX] security server ...
Connecting to server[main.mxkey.biz] ...MXKEY SX4CARD - ID, hello 41.235.210.209
SUPERDONGLE authorized !
Writing RFBB data: modules\{3EBAF427-9F55-419F-8A75-385DFC651169}\def\rfbb\N73_RM-133.txt ...
Writing RF settings to phone ...OK, finished. 20 Records found.
Writing BB settings to phone ...OK, finished. 9 Records found.
Done.
Writing PM from Node ...
Section: 1
- Key: 0, size 114 bytes written.
- Key: 2, size 98 bytes written.
- Key: 4, size 110 bytes written.
- Key: 6, size 98 bytes written.
- Key: 8, size 110 bytes written.
- Key: 13, size 98 bytes written.
- Key: 16, size 98 bytes written.
- Key: 18, size 98 bytes written.
- Key: 20, size 98 bytes written.
- Key: 22, size 16 bytes written.
- Key: 23, size 4 bytes written.
- Key: 24, size 84 bytes written.
- Key: 25, size 4 bytes written.
- Key: 26, size 110 bytes written.
- Key: 28, size 98 bytes written.
- Key: 29, size 6 bytes written.
- Key: 31, size 98 bytes written.
- Key: 33, size 36 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 2.894 s




after




SLPA ver[1]: PA_SL (15 digit NCK)

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


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

SW version 4.0839.42.0.1 released for Nokia N73


i was erase flash after then flash old version

aftr then write npc only

and Repair all but SECURITY_TEST failed!
didt fix

after this I tried edit rpl





i was fix This problem In five minutes

now i dont fix it

Please help me
  Reply With Quote
Old 04-26-2012, 18:16   #4 (permalink)
No Life Poster
 
gbluez's Avatar
 
Join Date: Jul 2004
Posts: 11,049
Member: 73565
Status: Offline
Thanks Meter: 5,062
- Are you sure need to recover cert? Please perform BB5 cert. validation, post the logs.
- Start self test, to see any other possible error. Post the logs.
- Try other FULL PM. Use this way http://forum.gsmhosting.com/vbb/f550...error-1465035/
  Reply With Quote
Old 07-03-2012, 17:18   #5 (permalink)
Junior Member
 
Join Date: Apr 2012
Posts: 9
Member: 1751744
Status: Offline
Thanks Meter: 0
I tried all the solutions
Please see this video
Movie - YouTube
  Reply With Quote
Old 07-04-2012, 17:45   #6 (permalink)
Product Manager
 
Mehmood Riaz 1's Avatar
 
Join Date: Mar 2012
Location: Some Where
Posts: 3,639
Member: 1737175
Status: Offline
Sonork: 100.1667675
Thanks Meter: 10,465
Quote:
Originally Posted by maged nashaat View Post
I tried all the solutions
Please see this video
Movie - YouTube

Hi brother , just try to catch me on my yahoo id or on QQ .. I will surely try to solve your problem through team viewer...

[email protected]

QQ: 1926867655
  Reply With Quote
Old 07-05-2012, 11:27   #7 (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 Mehmood Riaz 1 View Post
Hi brother , just try to catch me on my yahoo id or on QQ .. I will surely try to solve your problem through team viewer...

[email protected]

QQ: 1926867655
u r late for one year n three months...







br
  Reply With Quote
Old 07-06-2012, 15:23   #8 (permalink)
Junior Member
 
Join Date: Apr 2012
Posts: 9
Member: 1751744
Status: Offline
Thanks Meter: 0
Quote:
Originally Posted by Mehmood Riaz 1 View Post
Hi brother , just try to catch me on my yahoo id or on QQ .. I will surely try to solve your problem through team viewer...

[email protected]

QQ: 1926867655
i send you add on yahoo
[email protected]
  Reply With Quote
Old 07-06-2012, 20:31   #9 (permalink)
No Life Poster
 
Join Date: Apr 2006
Location: Hafizabad, Pakistan
Posts: 1,035
Member: 269126
Status: Offline
Sonork: 100.1616382
Thanks Meter: 370
yes! we have this solution
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)
9. give full factory reset


your phone must come back from security test failed
it is 100% tasted by me.
  Reply With Quote
Old 07-07-2012, 00:29   #10 (permalink)
Junior Member
 
Join Date: Apr 2012
Posts: 9
Member: 1751744
Status: Offline
Thanks Meter: 0
Quote:
Originally Posted by malikasim View Post
yes! we have this solution
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)
9. give full factory reset


your phone must come back from security test failed
it is 100% tasted by me.
i tried your answer in the new video Please see it
and not solved
http://www.youtube.com/watch?v=r4JU1...ture=*********
  Reply With Quote
Old 07-07-2012, 14:04   #11 (permalink)
No Life Poster
 
achintya's Avatar
 
Join Date: Jul 2007
Location: kolkata, india
Posts: 939
Member: 553420
Status: Offline
Sonork: 100.1624012
Thanks Meter: 129
same problem happened with me and my n73 is now what it was.........


We need recover certificate option working for n73........
  Reply With Quote
Old 07-07-2012, 14:12   #12 (permalink)
No Life Poster
 
achintya's Avatar
 
Join Date: Jul 2007
Location: kolkata, india
Posts: 939
Member: 553420
Status: Offline
Sonork: 100.1624012
Thanks Meter: 129
BUSCHECK LOG>>>

MXKEY [MxKey Team HTI Flasher Interface (WinUSB) 4], SN: C081164E
Using device: HTI, FW ver: 00.50, SN: 0000C373
Connection status: UHCI:HUB:HUB:USB 2.00 (Full-speed)
Driver: WinUSB, ver: 3.5.1.0
Module ver: 1.0.0.21064(15-06-2012), Library ver: 1.0.0.14102(15-06-2012)
APE Data :
SYSTEM ASIC ID: 17100708 [OMAP1710 ver: 2.0]
ASIC MODE ID: 00
PUBLIC ID: 1056A79CA8D1A357AAF5A2C981619A4A13F87B1F
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: 148001126EBD58502A452A9FCEBA0DE326C686E3
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
SecondaryBoot: helen3_2nd.fg [BB5] version: 1.35.0 revision: 0.0 size: 0x3500
Supported Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
Storage0: 0098 01A1 - 0090 0095 [Toshiba ] 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
Original Imei: 3535**********
Original Product code: 0564012
Bluetooth ID: 002108610CBD
SIMLOCK PA identifier:
[0] PA_SL

Phone type: RM-133 (Nokia N73)
SW version: V 05wk47v61.1 09-07-08 RM-133 (c) Nokia.
Imei plain: 35354***********
Product code: 0539101
Battery voltage: 4573 mV, current: 45 mA
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: 35354**********
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


BB5 CERTIFICATE VALIDATION CHECK>>>>



APE Data :
SYSTEM ASIC ID: 17100708 [OMAP1710 ver: 2.0]
ASIC MODE ID: 00
PUBLIC ID: 1056A79CA8D1A357AAF5A2C981619A4A13F87B1F
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: 148001126EBD58502A452A9FCEBA0DE326C686E3
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
SecondaryBoot: helen3_2nd.fg [BB5] version: 1.35.0 revision: 0.0 size: 0x3500
Supported Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
Storage0: 0098 01A1 - 0090 0095 [Toshiba ] 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: 0564012
Reading CMT VARIANT (0xB8 bytes).
Product Code:
Product Code missmatch !
Reading CMT CCC (0x0 bytes).
Reading CMT HWC (0x0 bytes).
  Reply With Quote
Old 07-07-2012, 18:40   #13 (permalink)
No Life Poster
 
Join Date: Apr 2006
Location: Hafizabad, Pakistan
Posts: 1,035
Member: 269126
Status: Offline
Sonork: 100.1616382
Thanks Meter: 370
contavt me on TV...............
  Reply With Quote
Old 07-07-2012, 19:11   #14 (permalink)
Junior Member
 
Join Date: Apr 2012
Posts: 9
Member: 1751744
Status: Offline
Thanks Meter: 0
Quote:
Originally Posted by malikasim View Post
contavt me on TV...............
i don't understand you
  Reply With Quote
Old 07-08-2012, 20:46   #15 (permalink)
No Life Poster
 
Join Date: Apr 2006
Location: Hafizabad, Pakistan
Posts: 1,035
Member: 269126
Status: Offline
Sonork: 100.1616382
Thanks Meter: 370
pm me on yahoo and u already install team viewer then i can help u ok
  Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

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
3330 v 412 fail with dfs 211 denn Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 1 09-19-2001 22:06
In wintesla 3310, what does cobba parrarel failed means brittnee Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 10 05-18-2001 16:05
MCU EEPROM contents: failed phr3ak Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 0 02-12-2001 15:58
Nokia 5110 v. 5.24 Unlock Failed! Cybertooth Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 3 02-28-2000 15:35
Mti init failed dogbreak Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 3 11-22-1999 01:28

 



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



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

SEO by vBSEO