5310 RM-495 RPL или бутер?

[ra9mtv]

Доброго здравия ВСЕМ! Пришол тел вот с таким диагнозом.

инфо

TransmissionMode: DDR&TX2
Original Imei: 35************
Original Product code: 0571631
Bluetooth ID: 0025CF8E89CE

Phone type: RM-495 (Nokia 5130c-2)
SW version: V 07.95 03-02-10 RM-495 (c) Nokia
Imei plain: 35*********-2
Battery voltage: 4052 mV, current: 93 mA
Language Pack:
- not available.

SLPA ver[1]: PA_SL (15 digit NCK)
Camera config: NIMMIIIIRRFF094B2F01, ver: XXX.XXX
warning: DCC corrupted !

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


SIMLOCK_DATA corrupted!
SIMLOCK_DATA corrupted!

тест

Phone Type: RM-495
SW version: V 07.95 03-02-10 RM-495 (c) Nokia

ID Test name Startup Result
3 EAR_DATA_LOOP Y passed
12 SIM_CLK_LOOP Y passed
13 SIM_IO_CTRL_LOOP Y passed
15 SLEEP_X_LOOP Y passed
46 UEM_CBUS_IF Y passed
7 KEYBOARD_STUCK N passed
22 CAMERA_IF N !no signal
20 BACKUP_BATT N passed
43 LCD N passed
21 LPRF_IF N passed
44 LPRF_AUDIO_LINES N passed
2 CURRENT_CONS N passed
42 RADIO N passed
69 BACKLIGHT Y passed
33 SIM_LOCK N !failed !
93 SECURITY N passed
71 BT_WAKEUP N passed
96 HOOKINT N passed
88 TAHVOINT Y passed
101 BTEMP N passed
119 IIC N passed
108 EXT_DEVICE N passed
56 CDSP_SLEEPCLK_FREQ N passed
128 CDSP_SLEEPCLOCK_FREQ N passed
86 CDSP_RF_BB_IF N passed
83 CDSP_RF_SUPPLY N passed
80 CDSP_TX_PLL_PHASE_LOCK N passed
81 CDSP_RX_IQ_LOOP_BACK N passed
77 CDSP_GSM_TX_POWER N !unknown(14 0) -

Вроде бы так как тел SL3 надо заказывать RPL
Бэкапы РПЛ и РМ сделал
Решил пролить бэкап РПЛ обратно в тел

прошиваю РПЛ

Imei: 35**********
Restoring RF/BB DATA from backup ...
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000296
EM1 ID: 00000B22
PUBLIC ID: 18200101036C7D5689026A108D598AF0507DF17A
ASIC MODE ID: 00
ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: RAP3Gv3_2nd.fg [BB5] version: 9.11.1 revision: 0.0 size: 0x3C00
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
eBB5ProtocolType: OLD
Storage0: 0089 8982 - 0000 8A31 [Intel NU48F512,512 Mbits] type: FLASH,NOR, asic:CMT
Storage content: 0000 0000 0000 0000 0000 0000 0000 0000
Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT
TransmissionMode: 16Bit
Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 9.50.0 revision: 0.0 size: 0x23010
Supported 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
CMT PAPUBKEYS HASH: 0C917F11196FDB7378C18EF7260698CA4489DCA0
TransmissionMode: DDR&TX2
Erasing CMT NPC ... OK
Updating RF ...OK
Updating BB ...OK
Updating WARRANTY ...OK
Updating BT ...OK
MXKEY [MxKey Team HTI Flasher Interface (WinUSB) 4], SN: C0851880
Using device: HTI, FW ver: 00.50, SN: 00015249
Connection status: UHCI:HUB:USB 2.00 (Full-speed)
Driver: WinUSB, ver: 3.5.1.0
Module ver: 1.0.0.19798(05-01-2012), Library ver: 1.0.0.13703(05-01-2012)
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000296
EM1 ID: 00000B22
PUBLIC ID: 18200101036C7D5689026A108D598AF0507DF17A
ASIC MODE ID: 00
ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: RAP3Gv3_2nd.fg [BB5] version: 9.11.1 revision: 0.0 size: 0x3C00
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
eBB5ProtocolType: OLD
Storage0: 0089 8982 - 0000 8A31 [Intel NU48F512,512 Mbits] type: FLASH,NOR, asic:CMT
Storage content: 0000 0000 0000 0000 0000 0000 0000 0000
Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT
TransmissionMode: 16Bit
Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 9.50.0 revision: 0.0 size: 0x23010
Supported 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
CMT PAPUBKEYS HASH: 0C917F11196FDB7378C18EF7260698CA4489DCA0
TransmissionMode: DDR&TX2
Updating CMT NPC ...OK
Updating CMT CCC ...OK
Updating CMT HWC ...OK
Prog.status for Asic CMT ...
NOR: OK
Updating LOCK ...error 0x0
Updating SUPERDONGLE_KEY ...OK

В итоги даже родной не залился(.
Сам тел чистый следов влаги нет, бутер прогрел.
Отсюда вопрос Ето так и должно быть или
всетаки бутер надо менять? Почему не прописался то?