SD Repair Poll For MX-Key

[Andra]

can we closed this fool polling ???



br,

[booreck]

Originally Posted by MobileEx-Team

can we closed this fool polling ???



br,

Yes, please close this 'fool poll' BUT! after you repair your buggy soft!
And at last say to users: "Yes, we fuked up, we are sorry, SD repair is fake, we are waiting to other teams to public their solution and then we could add this to our"

FACTS: 99 users said: "yes it works" VERSUS 265 users who said: "not work" in this poll - what u say bout this?

[adnann5]

Originally Posted by MobileEx-Team

can we closed this fool polling ???



br,

Please stop calling it fool poll....there was a problem in the software.....
now since its solved u can delete it..... see the result of the poll and accept reality my dear.....

Br

[Andra]

hello .

can u try .
do some job and post in our thread.
prove by your self

br,

[pritech]

Originally Posted by adnann5

Please stop calling it fool poll....there was a problem in the software.....
now since its solved u can delete it..... see the result of the poll and accept reality my dear.....

Br

don't close this tread......let he know's......NOW SD REPAIR ON MXKEY IS WORKED 100000%,...OTHER WISE ON SL1 & SL2...AND SOME SL3.......OPEN YOUR EYES sIR........

RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 29D00019FB566F5624E76833A34BD4CE43494526
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 191EC665DFAAF68F
SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 9.11.1 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 2208 - 0000 6921 [Samsung K8F5615ETM,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: 9.17.0 revision: 0.0 size: 0x22E90
Supported RAP Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
RAP PAPUBKEYS HASH: C0E691EA16A7593A9BB28832D7312A39F7ED668D
NPC verified Ok.
Updating CMT CCC ...OK
Updating CMT HWC ...OK
Certificate programmed successfully !

Phone Type: RM-272 (Nokia 3500c)
SW Version: V 07.21 05-11-08 RM-272 (c) Nokia.
Imei plain: 35308002169929-8
Product Code: 0549189
Language Pack:
- not available.

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


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

CONFIG_DATA: 2440700000000000
PROFILE_BITS: 0000000000000000

BLOCK 1: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 2: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 3: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 4: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 5: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 6: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 7: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF

[javar_mfc]

it's true... repaire WD-> security_test failed succes with mx-key

thanx mx-key

[jaysukh]

for me working every time thanks to mx key team