3110c Repair SD contact service

mình vừa Repair SD con 3110c 3phut mât nguồn(WD timer enabled, phone will reboot itself after 3 min.) xong nhưng bị contact service
SUPER SD Auth báo thế này
SUPERDONGLE authorized :)!
warning: SD authorized but verify failed !

log Bus check
Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.11985, Date: 03-02-2010
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 29500102CF517E564308D5006AD3C5A0D8B6EA36
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 191EC665DFAAF68F
SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 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 0000 [Intel NU48F256,256 Mbits] type: NOR,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
ExtDEVC: FFFF 0000 - 0000 0000
Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0
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
Original Imei: 35196303111679
Original Product code: 0514949
Bluetooth ID: 00247D6A5B2A

Phone Type: RM-237 (Nokia 3110c)
SW Version: V 07.21 05-11-08 RM-237 (c) Nokia.
Imei plain: 35196303111679-5
Product Code: 0514950
Language Pack:
- not available.

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

"RM-237" folder created.

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

SX4 >>> write Pm phát.

Trích:

---

Được post bởi DinhKha™

SX4 >>> write Pm phát.

---

làm theo bác dinhkha đi bạn chúc thành công

Trích:

---

Được post bởi DinhKha™

SX4 >>> write Pm phát.

---

không đc mod ơi
Completed in 27.484 s
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 123.12.167.41
Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request

Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request

Máy không bị mà nó báo cái MXkey có vấn đề ..

Trích:

---

Được post bởi jerrylevu

Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request

Máy không bị mà nó báo cái MXkey có vấn đề ..

---

bạn nói rõ tý đc không mx_key mình update, chạy và nạp imei cho dct4 vẫn bình thường mà

Scanning local SX4 Card ...
No SX4 Card found.

Bạn có thể lấy 1 cây khác thử , vì giống như vầy là nó báo không kiếm thấy sx4 card .superdongle key bị lỗi nên không thể kết nối với sever. cái tốt nhất là kiếm 1 cây khác thử .rồi mới biết chắc là bị gì

Trích:

---

Được post bởi jerrylevu

Scanning local SX4 Card ...
No SX4 Card found.

Bạn có thể lấy 1 cây khác thử , vì giống như vầy là nó báo không kiếm thấy sx4 card .superdongle key bị lỗi nên không thể kết nối với sever. cái tốt nhất là kiếm 1 cây khác thử .rồi mới biết chắc là bị gì

---

ok vậy để mình mượn mxkey khác thử cái có gj mình báo kết quả

Repair SD thì làm sao Sx4 đuợc nữa. Làm đi, cuối cùng ......ko đuợc

SUPERDONGLE authorized !
warning: SD authorized but verify failed !
SECURITY_TEST failed!
bác này mới thấy mxkey nó cho repair sd nên mang ra làm phát đây mà.mấy thằng tây cũng bị y như vậy.nhưng có con báo ok có con báo như bạn,những con báo ok nhưng ko biết thế nào hay là nghe nhạc vẫn sụp nguồn.manole nó có nói nè,tham khảo nhé
If after repair SD and/or Simlock (Super Dongle RPL and Simlock RPL upload) you get "SECURITY_TEST failed!" and/or "warning: SD authorized but verify failed!".
This is comming usually because some PM fields and/or RPL sections are missing from your phone (e.g. DRM keys, CCC, ...).

Solution 1 (easy way, maybe not work all time, depends how phone was damaged):
- write full PM from SAME phone model (product number) WITHOUT fields 1, 308, 309 (and WITHOUT field 120 for SL20 based phones)
- unplug/replug phone from JAF/UFS box
- make Simlock RPL repair
- make SD RPL repair
- unplug/replug phone from JAF/UFS box
- make SUPER SX4 Auth then write PM1 and PM309

if still have problems, use Solution 2:

- backup RPL (NPC, CCC, HWC, ...), will call this ORIGINAL RPL
- backup RPL from another working phone (same model) with SAME product code
- edit this good RPL from another phone and remove NPC section (all lines who start with NPC_DATA_1 ... NPC_DATA_xx), will call this edited file CLONE RPL
- backup full PM from another working phone (same model) with SAME product code, will call this file CLONE PM
- full erase flash chip (use erase file regarding flash chip size)
- flash phone (CMT, APE, ...)
- upload CLONE RPL
- upload ORIGINAL RPL
- write full CLONE PM without fields 1,120,308,309
- unplug/replug phone from JAF/UFS box
- make Simlock RPL repair
- make SD RPL repair
- unplug/replug phone from JAF/UFS box
- make SUPER SX4 Auth then write PM1 and PM309