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 3110-security test failed!!!
Register FAQDonate Forum Rules Root any Device ★iPhone Unlock★ ★ Direct Codes ★ Direct Unlock Source


Reply
 
LinkBack Thread Tools Display Modes
Old 02-27-2010, 11:15   #1 (permalink)
No Life Poster
 
Join Date: Jul 2009
Location: India
Posts: 2,857
Member: 1086393
Status: Offline
Thanks Meter: 771
3110-security test failed!!!

SCAN--

Code:
SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
CMLA_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!
PM AUTH--

Code:
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(ID),  hello 117.205.192.176
Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request
Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(ID),  hello 117.205.192.176
Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request
Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(ID),  hello 117.205.192.176
Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request

REPAIR S/D

Code:
 
Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.7687(12-02-2010), 1.0.0.12095(13-02-2010)
 
Product: V 07.21 05-11-08 RM-237 (c) Nokia.            
 
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 191EC665DFAAF68F
 
Calculating SUPERDONGLE using security server ...
Connecting to server[main.mxkey.biz] ... 
Connecting to server[main.mxkey.biz] ...OK, secure login ...
Connecting to server[main.mxkey.biz] ... 
Connecting to server[main.mxkey.biz] ...OK, secure login ...
Completed in 54.953 s
 
RPL saved to "C:\mobileEx\3.3\data\backup\BB5_RM-237_356**************_SIMSD.RPL" 
Updating SUPERDONGLE_KEY ...OK
Updating SIMLOCK...OK
S/D AUTH & PM--
Code:
 
Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.7687(12-02-2010), 1.0.0.12095(13-02-2010)
 
Product: V 07.21 05-11-08 RM-237 (c) Nokia.            
 
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 191EC665DFAAF68F
 
Restarting phone ...
Connecting to server[main.mxkey.biz] ... 
Connecting to server[main.mxkey.biz] ...OK, secure login ...
Authenticating to SUPERDONGLE using security server ...
SUPERDONGLE authorized :)!
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 86 bytes written.
 - Key: 18, size 86 bytes written.
 - Key: 20, size 86 bytes written.
 - Key: 25, size 4 bytes written.
 - Key: 29, size 6 bytes written.
 - Key: 34, size 80 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: 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 3.344 s

Code:
SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
CMLA_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!
RECOVER CERT
Code:
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 14000215433A7D56FDBA6C6121C5F96BD34CBBEE
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: 0089 8981  - 0000 6A21 [Intel NU48F256,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
Reading RAP NPC  (0x168 bytes)
 
Begin Certificate Request ...
Connecting to server ...OK, Login ...
Query done with status: OK
 
Updating PRODUCTCODE (0566963)... OK
Updating CMLA_KEY...OK
Updating WMDRM_PD...OK
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 14000215433A7D56FDBA6C6121C5F96BD34CBBEE
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: 0089 8981  - 0000 6A21 [Intel NU48F256,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
Updating CMT  NPC ...OK
Updating CMT  CCC ...OK
Updating CMT  HWC ...OK
Certificate programmed successfully !
Code:
SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
CMLA_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!
I DID ERASE EDITING REPLACING HWC,CCC ETCCC
BUT FAILED!!
  Reply With Quote
Old 02-27-2010, 11:35   #2 (permalink)
Freak Poster
 
kirta's Avatar
 
Join Date: Nov 2008
Posts: 252
Member: 898963
Status: Offline
Thanks Meter: 69
1 rd cert with ufs
2 erase with file erase bb5 with ufs
3 full flash again with ufs
4 write cert only npc with ufs
5 repair sd with mx key
6 S/D AUTH
7 write full pm without 308
8 write rpl without npc by mx key

100% work tested by me

br;
  Reply With Quote
Old 02-27-2010, 11:49   #3 (permalink)
No Life Poster
 
Join Date: Jul 2009
Location: India
Posts: 2,857
Member: 1086393
Status: Offline
Thanks Meter: 771
http://forum.gsmhosting.com/vbb/show...36&postcount=1


THIS IS WAT I DID--I THINK ITS ENOUGH
  Reply With Quote
Old 02-27-2010, 19:25   #4 (permalink)
No Life Poster
 
Andra's Avatar
 
Join Date: Feb 2005
Location: AD
Posts: 4,665
Member: 976728
Status: Offline
Sonork: 1589709
Thanks Meter: 4,775
what result in " BB5 secure Validation " ?
some phone have unique security.

try this pm after "Super SD Auth"
RM-237 3110

br,
  Reply With Quote
The Following User Says Thank You to Andra For This Useful Post:
Reply

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
5300 and 3110 security test failed kamal07 MXKEY Nokia Flasher and Unlocker (by Alim Hape) 7 05-12-2010 08:55
3110 security test failed SAN INFOTECH MXKEY Nokia Flasher and Unlocker (by Alim Hape) 9 03-24-2010 14:55
3110 security test failed ? GSMBALOCH MXKEY Nokia Flasher and Unlocker (by Alim Hape) 19 03-13-2010 21:55
3110 security test failed.. help pls appu2009 MXKEY Nokia Flasher and Unlocker (by Alim Hape) 3 02-19-2010 11:03
security test failed 3110 c help gopalhot MXKEY Nokia Flasher and Unlocker (by Alim Hape) 5 02-04-2010 14:12

 



All times are GMT +1. The time now is 23: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.20857 seconds with 9 queries

SEO by vBSEO