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 09-27-2012, 15:22   #1 (permalink)
Registered User
 
Join Date: Jun 2005
Location: jamnagar gujarat india
Posts: 904
Member: 149938
Status: Offline
Thanks Meter: 47
c6 contact retailer


c6 contact retailer. info here.

Phone type: RM-675 (Nokia C7-00)
SW version: V 79_sr1_12w18.5 27-07-12 RM-675 (c) Nokia
ApeCoreSw: 111.040.1511
Imei plain: 355960xxxxxxxxx
Product code: 059D9Z9
Battery voltage: 3662 mV, current: 247 mA
Language Pack:
- not available.

SLPA ver[4]: PA_SL3/PA_SIMLOC30 (15 digit NCK)
warning: avoid SW Downgrade & manual erase to this phone !

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


Imei net: 355960048211003
Version: SIMLOCK SERVER
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

tried to repair super dongle and write pm all ok.
log here.

Updating SUPERDONGLE_KEY ...OK
Authenticating to SUPERDONGLE ...
SUPERDONGLE authorized !
Writing RFBB data: modules\{3EBAF427-9F55-419F-8A75-385DFC651169}\def\rfbb\RM-675.pm ...OK
Done.
Phone authenticated to SUPERDONGLE already.
Writing PM from Node ...
Section: 1
- Key: 0, size 10 bytes written.
- Key: 1, size 94 bytes written.
- Key: 2, size 110 bytes written.
- Key: 4, size 10 bytes written.
- Key: 6, size 110 bytes written.
- Key: 7, size 450 bytes written.
- Key: 8, size 10 bytes written.
- Key: 13, size 110 bytes written.
- Key: 15, size 30 bytes written.
- Key: 16, size 30 bytes written.
- Key: 17, size 30 bytes written.
- Key: 18, size 30 bytes written.
- Key: 19, size 30 bytes written.
- Key: 22, size 24 bytes written.
- Key: 26, size 10 bytes written.
- Key: 27, size 36 bytes written.
- Key: 28, size 110 bytes written.
- Key: 29, size 10 bytes written.
- Key: 30, size 36 bytes written.
- Key: 31, size 24 bytes written.
- Key: 32, size 216 bytes written.
- Key: 33, size 36 bytes written.
- Key: 35, size 24 bytes written.
- Key: 36, size 24 bytes written.
- Key: 38, size 216 bytes written.
- Key: 39, size 36 bytes written.
- Key: 40, size 24 bytes written.
- Key: 41, size 216 bytes written.
- Key: 43, size 36 bytes written.
- Key: 44, size 216 bytes written.
- Key: 45, size 216 bytes written.
Section: 2
- Key: 0, size 2240 bytes written.
Section: 4
- Key: 3, size 10 bytes written.
- Key: 4, size 8 bytes written.
- Key: 5, size 8 bytes written.
- Key: 6, size 8 bytes written.
- Key: 9, size 5 bytes written.
Section: 6
- Key: 0, size 96 bytes written.
Section: 8
- Key: 0, size 2 bytes written.
- Key: 1, size 16 bytes written.
- Key: 2, size 16 bytes written.
- Key: 3, size 128 bytes written.
- Key: 4, size 128 bytes written.
- Key: 5, size 8 bytes written.
- Key: 8, size 8 bytes written.
- Key: 9, size 8 bytes written.
- Key: 10, size 32 bytes written.
- Key: 11, size 4 bytes written.
- Key: 12, size 4 bytes written.
Section: 11
- Key: 0, size 4 bytes written.
- Key: 1, size 4 bytes written.
- Key: 2, size 4 bytes written.
- Key: 3, size 4 bytes written.
- Key: 4, size 1059 bytes written.
Section: 12
- Key: 0, size 8 bytes written.
Section: 26
- Key: 0, size 16 bytes written.
- Key: 1, size 68 bytes written.
Section: 31
- Key: 4, size 16 bytes written.
Section: 44
- Key: 0, size 1 byte written.
Section: 50
- Key: 0, size 2 bytes written.
Section: 54
- Key: 0, size 2 bytes written.
Section: 96
- Key: 0, size 2 bytes written.
- Key: 1, size 20 bytes written.
Section: 107
- Key: 26, size 12 bytes written.
Section: 117
- Key: 0, size 4 bytes written.
- Key: 1, size 3 bytes written.
- Key: 2, size 6 bytes written.
- Key: 3, size 1 byte written.
- Key: 5, size 10 bytes written.
- Key: 6, size 8 bytes written.
- Key: 8, size 42 bytes written.
- Key: 13, size 3 bytes written.
- Key: 14, size 3 bytes written.
- Key: 16, size 40 bytes written.
- 120 skipped
Section: 122
- Key: 0, size 2 bytes written.
Section: 153
- Key: 0, size 68 bytes written.
- Key: 1, size 68 bytes written.
- Key: 2, size 68 bytes written.
- Key: 3, size 68 bytes written.
- Key: 4, size 68 bytes written.
- Key: 5, size 68 bytes written.
Section: 193
- Key: 2, size 8 bytes written.
- Key: 3, size 32 bytes written.
- Key: 4, size 32 bytes written.
- Key: 9, size 64 bytes written.
Section: 217
- Key: 0, size 32 bytes written.
- 239 skipped
Section: 291
- Key: 0, size 92 bytes written.
- 308 skipped
Section: 309
- Key: 0, size 4 bytes written.
- Key: 1, size 2 bytes written.
- Key: 2, size 12 bytes written.
- Key: 3, size 36 bytes written.
- Key: 4, size 12 bytes written.
- Key: 7, size 12 bytes written.
- Key: 17, size 12 bytes written.
Section: 313
- Key: 0, size 800 bytes written.
Section: 322
- Key: 0, size 1 byte written.
Section: 327
- Key: 0, size 2 bytes written.
Section: 329
Warning: failed to write 329 - 0 (8392 bytes)
Section: 334
- Key: 0, size 1 byte written.
Section: 341
- Key: 0, size 1 byte written.
- Key: 3, size 4 bytes written.
Warning: failed to write 341 - 4 (4516 bytes)
- Key: 10, size 4 bytes written.
- Key: 11, size 1972 bytes written.
Section: 354
- Key: 0, size 13 bytes written.
Section: 356
- Key: 0, size 2 bytes written.
Section: 360
- Key: 0, size 1 byte written.
- Key: 1, size 2 bytes written.
Section: 369
- Key: 0, size 40 bytes written.
Section: 382
- Key: 1, size 4 bytes written.
Section: 388
- Key: 0, size 4 bytes written.
Section: 395
- Key: 0, size 16 bytes written.
Completed in 4.297 s

but same. security test failed.

write ccc and hwc rpl file. log here.

Connecting to server[main.mxkey.biz] ...MXKEY [MxKey Team HTI Flasher Interface (WinUSB) 4], SN: C08025F2
Using device: USB Phonet and HTI, FW ver: 00.50, SN: 0000491A
Connection status: EHCI:HUB:HUB:USB 2.00 (High-speed)
Driver: nmwcdc, ver: 7.1.32.75
Module ver: 1.0.0.21151(13-07-2012), Library ver: 1.0.0.14195(13-07-2012)
Battery voltage: 3614 mV
Warning battery voltage is less, phone might not detected after flash !
Phone type: RM-675 (Nokia C7-00)
Product code: 059D9Z9
SW version: 111.040.1511
LanguagePkg version: 111.040.1511111.040.1511.24.01111.040.1511.C00.01
Waiting for USB device removal ...
CMT SYSTEM ASIC ID: 000000030000022600010007600C192102031104 [RAPUYAMA ver: 1.1]
CMT EM0 ID: 00001040
CMT EM1 ID: 00001030
CMT PUBLIC ID: 0CC0010728A7034401B3BF489DFFA07894D4F434
CMT ASIC MODE ID: 00
CMT ROOT KEY HASH: 916F75217F32081248B15C38DFC8E81B
CMT ROM ID: E693EF0DAC22615B
Loading CMT secondary boot code
SecondaryBoot: RAPUv11_2nd.fg [BB5] version: 11.14.0 revision: 3.0 size: 0x3B40
Supported Ids: 4003192102001104, 400C192102001104, 6003192102001104, 600C192102001104, 6003192102011104, 600C192102011104, 6003192102021104, 600C192102021104, 6003192102031104, 600C192102031104
eBB5ProtocolType: NEW
Secondary boot loaded.
Storage0: 0000 0000 - 0000 0000 type: RAM, asic:CMT
Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT
Storage2: 0000 0000 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT
Storage3: 0000 0001 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT
Storage4: 00EC 0068 - 0000 0131 [Samsung LH28F160BG] type: FLASH,MuxOneNAND, asic:CMT
Suggested algorithm: XSR 1.6
Loading CMT update server data
Algorithm: RAPUv11_XSR17_alg.fg [XSR 1.6] version: 11.14.0 revision: 3.0 size: 0xC66D5
Supported Ids: 4003192102001104, 400C192102001104, 6003192102001104, 600C192102001104, 6003192102011104, 600C192102011104, 6003192102021104, 600C192102021104, 6003192102031104, 600C192102031104
Update server code loaded.
Waiting for USB device removal ...
Device connected: nmwcdnsuc\Nokia USB Flashing Generic, PORT_ID: 262F1828
FUR: Adding Asic CMT as client OK.
Erasing CMT CCC ... OK
Updating CMT CCC ...OK
Erasing CMT HWC ... OK
Updating CMT HWC ...OK
Waiting for USB device removal ...OK
Waiting for USB device arrival ...OK
Waiting for device boot up ...
Device connected: nmwcdc\Nokia C7-00 USB Phonet, PORT_ID: 395A04F0
Verifying communication to device OK.


Phone type: RM-675 (Nokia C7-00)
SW version: V 79_sr1_12w18.5 27-07-12 RM-675 (c) Nokia
ApeCoreSw: 111.040.1511
Imei plain: 35596004821100-3
Product code: 059D9Z9
Battery voltage: 3614 mV, current: 221 mA
Language Pack:
- not available.

SLPA ver[4]: PA_SL3/PA_SIMLOC30 (15 digit NCK)
warning: avoid SW Downgrade & manual erase to this phone !

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


Imei net: 355960048211003
Version: SIMLOCK SERVER
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

anyone can guide.
  Reply With Quote
Old 09-27-2012, 15:41   #2 (permalink)
No Life Poster
 
.::ZUBER::.'s Avatar
 
Join Date: Apr 2006
Location: MXBOX THUNDER Helpdesk
Age: 50
Posts: 4,273
Member: 262425
Status: Offline
Sonork: 100.1617691
Thanks Meter: 1,264
Bro.

Go to Service Tab > Click Load from File > Select Address: C:\mobileEx\3.5\modules\{3EBAF427-9F55-419F-8A75-385DFC651169}\def\rfbb & Select RM-675.PM file,

Now click Repair SD & click no to Pop Up Window, Click Write & Buscheck you will see the positive Result.


BR,
ZUBER
  Reply With Quote
Old 09-27-2012, 15:55   #3 (permalink)
Registered User
 
Join Date: Jun 2005
Location: jamnagar gujarat india
Posts: 904
Member: 149938
Status: Offline
Thanks Meter: 47
thx
solved ok

br
  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


 



All times are GMT +1. The time now is 15:02.



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.12723 seconds with 8 queries

SEO by vBSEO