Repairing a 7210C in Mxkey!

The phone came in with a "contact service status, till I found out that the cause of its fault was written in this LOGS: 

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)
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 0890000C69497D56992E4967934C462648A30C72
ASIC MODE ID: 00
ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
ROM ID: 273F6D55DFAAF68F
 SecondaryBoot: rap3gv3_2nd.fg [BB5]  version: 1.30.0 revision: 0.0 size: 0x3C00
FlashID0: 0089 8982  - 0000 0000 [Intel NU48F512,512 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
RAP PAPUBKEYS HASH: F1DCA5EA5203CD30A64D4D95ABCD621F4AB23026
Original Imei: 35196203288860
Original Product code: 0566921
Bluetooth ID: 00247DD36209
 
Phone Type: RM-436 (Nokia 7210 Supernova)
SW Version: V 07.23 17-07-09 RM-436 (c) Nokia             
Imei plain: 35196203288yobb
Language Pack:
- not available.

SIMLOCK invalid!
SUPERDONGLE_KEY invalid!
- WD timer enabled, phone will reboot itself after 3 min.
SIMLOCK_TEST failed!
SECURITY_TEST passed

This is some steps you have to do to repair it. Simple as 2 steps only!

First:

On your Mx dongle click the Service tab as shown in the image below, then click the Repair SD button

 Logs in SD Repair!

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.23 17-07-09 RM-436 (c) Nokia             
 
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
ROM ID: 273F6D55DFAAF68F
 
Restarting phone ...
Connecting to server[main.mxkey.biz] ...OK, secure login ...
Authenticating to SUPERDONGLE using security server ...
SUPERDONGLE authorized :)!


After repairing SD data, one new error occur.

2nd step is by writing your PM to fix the Security_Test failure.

The last image FIXED the problem! 

Final image totally repaired!