6120C надпись "Nokia" и перезагруз

[Fluderator]

Приветствую вас братья по разуму,у меня следующая проблема.Принесли nokia 6120 RM-243 с диагнозом не включается после другой мастерской,но визуально было заметно что Betty не сидит на месте,после перекатал и телефон стал включаться,но при включении загорается белый экран потом надпиь "Nokia" и черный дисплей,через секунды снова загорается белый экран надпись "nokia" и снова тухнет,и так по кругу до безконечности.Прошил телефон,в телефоне была версия 05,11 и инфо считывалось нормально SelfTest не догадался сделать,вот лог инфо предыдущей версии ПО телефона:
MCU SW : V 05.11 21-04-08 RM-243 (c) Nokia
PPM SW : 05.11
Product : Nokia 6120
Prd.Code: 0546330
Bpr.Code: 0539292
Prod.Sn : KBN156686
HW Vers : 1002
EM VILMA: 15
EM BETTY: 21
RFIC Ver: 17141715
DSP Vers: 06w41pb_08w08.0.1_rm243
IMEI : 359808-01-643918-7
SL Serv : SIMLOCK SERVER
SL Conf : 244-07-00000000000
SL Prof : 0000000000000000
SL Count: 02 00
BLK1= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN
BLK2= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN
BLK3= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN
BLK4= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN
BLK5= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN
BLK6= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN
BLK7= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN
Provider: Nokia Test;Finland

После прошивки на 07.10 версию в локал не заходит,нет сбросов и не читает инфо.Поменял Betty и Avilmas толку нет,состояние пациента такое же,что посоветует сделать консилиум мастеров на форуме?

[raxim]

Пролей ему e51blank как mcu и будет тебе счастье.

[Fluderator]

Я ему прошил E71_blank_pmm или есть разница с e51blan?

[aq7]

Я ему прошил E71_blank_pmm или есть разница с e51blan?

нет разницы, у этой модели часто помогает пропай проца

[Vano37]

Если тело падало в локал, то замена питалова это лишние действия, у меня, например, ни разу не было случая, когда пара авилма-бетти была причиной невключения, если тело шилось. Потом если тело после других рук, смотрите внимательней плату, может она вспученая, попробуйте погнуть при включении

[saw74]

Если есть бэкапы сертификатов, не лишнее попробовать полное стирание. Мне приносили раз висящий на черном экране и весь ужареный - полное стирание помогло. Кстати, он-же sl2, так что можно и без бэкапов.

[nics]

Кстати, он-же sl2, так что можно и без бэкапов.
Ну-ну, не перегибайте. Как минимум NPC нужен.

[yurii-62]

Приветствую вас братья по разуму,у меня следующая проблема.Принесли nokia 6120 RM-243 с диагнозом не включается после другой мастерской,но визуально было заметно что Betty не сидит на месте,после перекатал и телефон стал включаться,но при включении загорается белый экран потом надпиь "Nokia" и черный дисплей,через секунды снова загорается белый экран надпись "nokia" и снова тухнет,и так по кругу до безконечности.Прошил телефон,в телефоне была версия 05,11 и инфо считывалось нормально SelfTest не догадался сделать,вот лог инфо предыдущей версии ПО телефона:

После прошивки на 07.10 версию в локал не заходит,нет сбросов и не читает инфо.Поменял Betty и Avilmas толку нет,состояние пациента такое же,что посоветует сделать консилиум мастеров на форуме?

Маловато информации по ТА. что по току потребления, динамика, что из оборудования имеется? (желательно делать) по Fbus Бестом считать NPC (для данного ТА. достаточно чтоб восстановить) Бест вычитает и без лакала, стереть (ERASE FLASH) пролить SW 05.11 полный инстал, должен появиться лакал, ТА должно включиться и проработать несколько минут, восстановить ТА., делаем SelfTest если необходимо, что делать дальше он подскажет...;)

[Fluderator]

Запись Full RPL (можно без NPC и SLD) считанного из такой же (полностью рабочей) модели.Кто скинет такой RPL?

[yurii-62]

Запись Full RPL (можно без NPC и SLD) считанного из такой же (полностью рабочей) модели.Кто скинет такой RPL?

Нужно только свае NPC, оно индивидульно для каждого ТА.
ЗЫ. что написал выше сделали??? логи где.. с другого ТА можно пролить PM. без 308 и 120 поля..
Держи, считан UFS, в данный момент поможет ли он?

[Fluderator]

Фул еразе с Циклоном
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1730001978B901584A11D929C0CF1AE792AD304A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC003000000221, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0030 (Samsung), Size: 128MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.12.8.0, Algo: XSR 1.5
Initializing TurboCache...
TurboCache Loaded!
Writing CMT PASUBTOC Certificate...
Writing CMT ALG Certificate...
CMT Algorithm Ready!
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Adding FUR Client (CMT, State: Ready)...
CMT FUR Ready!
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 0FE1BA92D924A658E4800780FA6F4868100AC947
APE Subsystem Not Found
Flashbus Write baud set to 5.0Mbits
Erasing flash chip...
Started group flash erase
EraseArea[0,CMT]: 0x00000000-0x07FFFFFF, ONENAND
Waiting 640s for erasure finish...
Erase taken 1.422s
Restarting MCU...
BB5 Full Erase Finished!


Пришивка с циклон

Processing pre flash tasks...
Pre flash tasks finished, continuing...
Processing rm243_07.10_prd_core.fpsx (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1730001978B901584A11D929C0CF1AE792AD304A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
rm243_07.10_prd_core.fpsx, Type: Flash Image, Algo: BB5, XSR 1.5
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.0, Algo: BB5
Flashbus Write baud set to 650Kbits
Flashbus Read baud set to 98Kbits
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,CMT]: 0xFFFFFFFF00000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC003000000221, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0030 (Samsung), Size: 128MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.12.8.0, Algo: XSR 1.5
Initializing TurboCache...
TurboCache Loaded!
Writing CMT PASUBTOC Certificate...
Writing CMT ALG Certificate...
CMT Algorithm Ready!
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Adding FUR Client (CMT, State: Ready)...
CMT FUR Ready!
Box VPP disabled
Internal CMT Phone VPP Enabled
Warning: PAPUBKEYS Hash Missing!
Flashbus Write baud set to 5.0Mbits
Sending Certificates...
Certificates OK
Partitioning...
Partitioning OK
Started group flash erase
EraseArea[0,CMT]: 0x00040000-0x00082FFF, ONENAND
EraseArea[0,CMT]: 0x00083400-0x0087FFFF, ONENAND
EraseArea[0,CMT]: 0x00B80000-0x04DFFFFF, ONENAND
Erase Partition (CMT)
Waiting 320s for erasure finish...
Erase taken 0.953s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT ADA Certificate...
Writing CMT KEYS Certificate...
Writing CMT PRIMAPP Certificate...
Writing CMT RAP3NAND Certificate...
Writing CMT PASUBTOC Certificate...
WARNING: CMT PAPUBKEYS Hash is Empty, writing first found PAPUBKEYS
Writing CMT PAPUBKEYS Certificate...
Writing CMT SOS*UPDAPP Certificate...
Writing CMT SOS*DSP0 Certificate...
Writing CMT SOS*ISASW Certificate...
Writing CMT SOS*CORE Certificate...
Writing CMT SOS+ROFS Certificate...
Programming Status OK!
All blocks written OK! Time taken 48.672s
Flashing Speed: 7520,34 kBit/S
Restarting MCU...
Processing rm243_07.10_prd_core.fpsx (APE)...
Processing E51_blank_504KB_pmm_10.fpsx (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1730001978B901584A11D929C0CF1AE792AD304A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
E51_blank_504KB_pmm_10.fpsx, Type: Flash Image, Algo: BB5, XSR 1.5
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.0, Algo: BB5
Flashbus Write baud set to 650Kbits
Flashbus Read baud set to 98Kbits
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC003000000221, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0030 (Samsung), Size: 128MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.12.8.0, Algo: XSR 1.5
Initializing TurboCache...
TurboCache Loaded!
Writing CMT PASUBTOC Certificate...
Writing CMT ALG Certificate...
CMT Algorithm Ready!
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Adding FUR Client (CMT, State: Ready)...
CMT FUR Ready!
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 0FE1BA92D924A658E4800780FA6F4868100AC947
Flashbus Write baud set to 5.0Mbits
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Programming Status OK!
All blocks written OK! Time taken 0.656s
Flashing Speed: 6297,99 kBit/S
Restarting MCU...
Processing E51_blank_504KB_pmm_10.fpsx (APE)...
Processing rm243_07.10_prd_UDA_Nokia_Noir.fpsx (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1730001978B901584A11D929C0CF1AE792AD304A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
Processing Flash Image Failed -> Given image file is not suitable for this CMT System ASIC ID (Tick "Skip CMT ID Check" if you are sure that given Image File is suitable for this phone!).
Failed to Process all Image files -> Failed to process rm243_07.10_prd_UDA_Nokia_Noir.fpsx

Инфо с циклоном
MCU Version V 07.10
MCU Date 15-07-09
Product RM-243 (Nokia 6120 classic)
Manufacturer (c) Nokia
IMEI 12345610654321?
IMEI Spare 1A32541660452301
IMEI SV 1332541660452351F9000000
PPM 07.10qLHHCI Version 8 (rev. 0). LMP Version 32 (rev. 4127). Manufacturer 13064.n256o256
PSN 0
PSD 0000000000000000
LPSN 0
APE SW 07.10
APE HW 256
APE ADSP 256
APE BT HCI Version 8 (rev. 0). LMP Version 32 (rev. 4127). Manufacturer 13064.
RETU 15
TAHVO 21
AHNE 11
HW 07.10qLHHCI Version 8 (rev. 0). LMP Version 32 (rev. 4127). Manufacturer 13064.n256o256
PCI i07.10qLHHCI Version 8 (rev. 0). LMP Version 32 (rev. 4127). Manufacturer 13064.n256o256
UEM 07.10qLHHCI Version 8 (rev. 0). LMP Version 32 (rev. 4127). Manufacturer 13064.n256o256u
UPP 07.10qLHHCI Version 8 (rev. 0). LMP Version 32 (rev. 4127). Manufacturer 13064.n256o256u
RFIC 17141715
DSP 06w41pb_08w28.0.1_rm243
LCD 07.10qLHHCI Version 8 (rev. 0). LMP Version 32 (rev. 4127). Manufacturer 13064.n256o256
BT 07.10qLHHCI Version 8 (rev. 0). LMP Version 32 (rev. 4127). Manufacturer 13064.n256o256u
ADSP Sw 07.10qLHHCI Version 8 (rev. 0). LMP Version 32 (rev. 4127). Manufacturer 13064.n256o256
ADSP DevID 07.10qLHHCI Version 8 (rev. 0). LMP Version 32 (rev. 4127). Manufacturer 13064.n256o256
ADSP RevID 07.10qLHHCI Version 8 (rev. 0). LMP Version 32 (rev. 4127). Manufacturer 13064.n256o256u
AEM 07.10qLHHCI Version 8 (rev. 0). LMP Version 32 (rev. 4127). Manufacturer 13064.n256o256u
Flip MCUSW 07.10qLHHCI Version 8 (rev. 0). LMP Version 32 (rev. 4127). Manufacturer 13064.n256o256
Failed to read info -> Failed to read SP info


Т.к.циклон полностью не может прошить ТА,прошивал после фул еразе УФСом вот логи:
Прошивка с УФСом
1ST BOOT : C0,07 [Rm-243] [2.2.0.3]
CMT ASICID: 000000010000022600010006400C192101031103
EM 1 ID : 00000295
EM 2 ID : 00000B21
CMT PUBID : 1730001978B901584A11D929C0CF1AE792AD304A
CMT MODE : 00
CMT HASH : CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT ROMID : 4B9B75103E691FF8
CMT 1ST Boot OK
CMT 2ND Bt: RAPIDOv11_2nd.fg, Ver: 1.37.1
CMT FLID0 : 00EC0030-00400221, Sam OneNAND-1G
CMT FLCNT : 00030000000000000000000000000000000000
CMT MCID0 : FFFF0000-00000000
CMT 2ND Boot OK
CMT ALGO : RAPIDOv11_algo.fg, Ver: 1.40.0
CMT KSIG0 : 0FE1BA92D924A658E4800780FA6F4868100AC947
CMT VPP : Internal
DUAL LINE : True
CMT ALG Boot OK
IMAGE : rm243_07.10_prd_core.fpsx
CMT NAND Erase Area: 0x00040000-00082FFF
CMT NAND Erase Area: 0x00083400-0087FFFF
CMT NAND Erase Area: 0x00B80000-04DFFFFF
CMT NAND Partition Format
CMT FLASH ERASE OK, Time: 00:00
Written: 11 Certificate(s)
CMT FLASH WRITE OK, Time: 03:50
IMAGE : rm243_07.10_prd_UDA_Nokia_Noir.fpsx
CMT NAND Erase Area: 0x04E00000-07B3FFFF
CNT FLASH ERASE OK, Time: 00:00
CNT FLASH WRITE OK, Time: 00:01
IMAGE : rm243_07.10_prd_vB05_03_russian.fpsx
CMT NAND Erase Area: 0x03300000-04DFFFFF
PPM FLASH ERASE OK, Time: 00:00
Written: 1 Certificate(s)
PPM FLASH WRITE OK, Time: 02:15
Flashing Completed, Rebooting Mobile
UI Defaults Ok, Time: 00:24
Set UI Factory Defaults Ok, Time: 00:00
Set Full Factory Defaults Ok, Time: 00:00
Set Software Upgrade Defaults Ok, Time: 00:00
Set Security Ok, Time: 00:00

Инфо:
MCU SW : V 07.10 15-07-09 RM-243 (c) Nokia
PPM SW : 07.10
Product : Nokia 6120
Prd.Code:
Bpr.Code:
Prod.Sn : 0
HW Vers :
EM VILMA: 15
EM BETTY: 21
RFIC Ver: 17141715
DSP Vers: 06w41pb_08w28.0.1_rm243
IMEI : 123456-10-654321-
SL Serv : SIMLOCK SERVER
SL Conf : 000-00-00000000000
SL Prof : 0142196900000000
SL Count: 00 00
SL Data Corrupted
Provider: Not Found


Еще РПЛ не записал,но памоему телефон должен работать с 12345 имеем,но сейчас при включении опять моргалик.Сейчас RPL запишу и отпишусь о состоянии пациента.

[yurii-62]

Еще РПЛ не записал,но памоему телефон должен работать с 12345 имеем,но сейчас при включении опять моргалик.Сейчас RPL запишу и отпишусь о состоянии пациента.

Да, должен включится и проработать некоторое время, если с железом все в порядке, ТА в лакал падает,
сделай тесты UFS..
ЗЫ. сейчас попробуй фениксом прошить..

[saw74]

Ну-ну, не перегибайте. Как минимум NPC нужен.
Точно!!!! Как это я забыл? Спасибо, что вовремя поправили.

[Fluderator]

Вот селфтест УФСом после чистой прошивки SW без заливки RPL:
107771
Послет того как заливаю РПЛ селфтест не дает.

И вот лог Циклона,при Analyse Security:
Security Analysis for Cyclone

Started Phone Security Analysis...
MCU Version V 07.10
MCU Date 15-07-09
Product RM-243 (Nokia 6120 classic)
Manufacturer (c) Nokia
IMEI 359808016439187
Mastercode 2523163761
Reading Security Block...
Security block OK and saved to "RM-243_359808016439187_02.03.2013_113002.SecurityBlock.PM"
Step 1 : Testing SIMLOCK
-- SIMLOCK PROBLEM --

Phone have failed SIMLOCK Test, that means Simlock Area is DAMAGED!
To repair simlock area, Select Unlock method : "RPL CALCULATION",
And then click DIRECT UNLOCK. SL Area will be re-formatted.

-- SIMLOCK PROBLEM --
Step 2 : Testing SECURITY
SECURITY SEFLTEST PASSED OK!
Step 3 : Analyzing Security Block
"1730001978B901584A11D929C0CF1AE792AD304A.C00045B2" Exists, That is good...
Checking SUPERDONGLE...
Failed to decode Security Section, Box Reported: Security Section Checksum Error (decryption fails?)
Checking SIMLOCK...
SIMLOCK FOUND AND CHECKSUM OK! PASSED!
Checking MCU&DSP TIMESTAMPS...
MCU&DSP TIMESTAMPS FOUND AND CHECKSUM OK! PASSED!
Checking CMLA KEYS...
Failed to decode Security Section, Box Reported: Security Section Checksum Error (decryption fails?)
Checking ECC KEYS...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking DIV KEYS...
Failed to decode Security Section, Box Reported: Security Section Checksum Error (decryption fails?)
Analyze finished!

[yurii-62]

Вот селфтест УФСом после чистой прошивки SW без заливки RPL:
107771
Послет того как заливаю РПЛ селфтест не дает.


По тестам вроде все в норме, за исключением этого >> EAR_DATA_LOOP_TEST<< эта ошибка (в вашем случае) у Вас связанна с сертификатами, Послет того как заливаю РПЛ селфтест не дает. похоже что NPC_DATA битая, бекап Rpl. делали чем? Пролить только NPC_DATA, имя восстанавливается.. SLD зону UFS не восстановите, про циклон сказать не могу, у меня нет, Вам нужен МХвох, Бест, АТФ.
ЗЫ. в поиске про это много инфы >> EAR_DATA_LOOP_TEST

[Fluderator]

Бекап делал Циклоном,имей восстанавливается,но еще есть один момент,под Betty нет одного пятака "G7",но он на USB идет и не должен влиять на работу Т.А.может из-за него "EAR_DATA_LOOP_TEST"?

[yurii-62]

Бекап делал Циклоном,имей восстанавливается,но еще есть один момент,под Betty нет одного пятака "G7",но он на USB идет и не должен влиять на работу Т.А.может из-за него "EAR_DATA_LOOP_TEST"?

Восстановить что не возможно???
По восстановлению ТА. здесь смотрел, принцип одинаков >>
http://www.gsmforum.su/showthread.php?t=75237
http://forum.gsmhosting.com/vbb/f528/faq-about-nokia-bb5-detailed-procedures-manuals-871121/
http://www.gsmforum.su/showthread.php?t=73508

[Fluderator]

Т.к. Analyse Security дает ошибку вот вообщем последовательность моих действий с помощью циклона:

RPL calculation

BB5 Unlock Started...
MCU Version V 07.10
MCU Date 15-07-09
Product RM-243 (Nokia 6120 classic)
Manufacturer (c) Nokia
IMEI 359808016439187
Mastercode 2523163761
Simlock Server SIMLOCK SERVER
Simlock Key 2440700000000000
Simlock Profile 8000000000000006
Simlock Key Cnt 0
Simlock FBUS Cnt 0
Simlock [1,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [1,2] State: OPENED Type: GID Data: FFFF
Simlock [1,3] State: OPENED Type: GID Data: FFFF
Simlock [1,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [1,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [2,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [2,2] State: OPENED Type: GID Data: FFFF
Simlock [2,3] State: OPENED Type: GID Data: FFFF
Simlock [2,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [2,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [3,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [3,2] State: OPENED Type: GID Data: FFFF
Simlock [3,3] State: OPENED Type: GID Data: FFFF
Simlock [3,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [3,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [4,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [4,2] State: OPENED Type: GID Data: FFFF
Simlock [4,3] State: OPENED Type: GID Data: FFFF
Simlock [4,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [4,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [5,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [5,2] State: OPENED Type: GID Data: FFFF
Simlock [5,3] State: OPENED Type: GID Data: FFFF
Simlock [5,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [5,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [6,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [6,2] State: OPENED Type: GID Data: FFFF
Simlock [6,3] State: OPENED Type: GID Data: FFFF
Simlock [6,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [6,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [7,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [7,2] State: OPENED Type: GID Data: FFFF
Simlock [7,3] State: OPENED Type: GID Data: FFFF
Simlock [7,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [7,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Reading Security Block...
Security block OK and saved to "RM-243_359808016439187_08.03.2013_130224.SecurityBlock.PM"
"1730001978B901584A11D929C0CF1AE792AD304A.C00045B2" Exists, That is good...
Checking for Rootkey Hash support with selected Unlock Method...
Selected Unlock Method: RPL Calculation
Asking box to calculate RPL...
Received RPL from Box OK!
Writing Simlock...
Simlock ACCEPTED OK !
MCU Version V 07.10
MCU Date 15-07-09
Product RM-243 (Nokia 6120 classic)
Manufacturer (c) Nokia
IMEI 359808016439187
Mastercode 2523163761
Simlock Server SIMLOCK SERVER
Simlock Key 2440700000000000
Simlock Profile 8000000000000006
Simlock Key Cnt 0
Simlock FBUS Cnt 0
Simlock [1,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [1,2] State: OPENED Type: GID Data: FFFF
Simlock [1,3] State: OPENED Type: GID Data: FFFF
Simlock [1,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [1,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [2,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [2,2] State: OPENED Type: GID Data: FFFF
Simlock [2,3] State: OPENED Type: GID Data: FFFF
Simlock [2,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [2,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [3,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [3,2] State: OPENED Type: GID Data: FFFF
Simlock [3,3] State: OPENED Type: GID Data: FFFF
Simlock [3,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [3,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [4,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [4,2] State: OPENED Type: GID Data: FFFF
Simlock [4,3] State: OPENED Type: GID Data: FFFF
Simlock [4,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [4,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [5,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [5,2] State: OPENED Type: GID Data: FFFF
Simlock [5,3] State: OPENED Type: GID Data: FFFF
Simlock [5,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [5,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [6,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [6,2] State: OPENED Type: GID Data: FFFF
Simlock [6,3] State: OPENED Type: GID Data: FFFF
Simlock [6,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [6,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [7,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [7,2] State: OPENED Type: GID Data: FFFF
Simlock [7,3] State: OPENED Type: GID Data: FFFF
Simlock [7,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [7,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Unlock finished! Time taken 3.969s


SX4 Authorization / SD Repair

SX4 Authorization / SD Repair Procedure Started....
"1730001978B901584A11D929C0CF1AE792AD304A.C00045B2" Exists, That is good...
MCU Version V 07.10
MCU Date 15-07-09
Product RM-243 (Nokia 6120 classic)
Manufacturer (c) Nokia
IMEI 359808016439187
Mastercode 2523163761
Reading Security Block...
Security block OK and saved to "RM-243_359808016439187_08.03.2013_130401.SecurityBlock.PM"
SX4 Status: Not authorized (76)
Started mutual authenthication with card...
Receiving Phone Seed 1...
Phone Seed 1 Received
Sending calculated Data 1, and expecting Seed 2...
Calculated Data 1 accepted, Phone Seed 2 Received
Sending calculated Data 2
Calculated Data 2 sent, Checking Authorization Status again
Authorization successfully finished!
Looking for Virgin PM In Database...
Found, writing...
[1,0] Written, Length: 114 bytes, Status: OK
[1,1] Written, Length: 4 bytes, Status: OK
[1,2] Written, Length: 98 bytes, Status: OK
[1,4] Written, Length: 110 bytes, Status: OK
[1,5] Written, Length: 4 bytes, Status: OK
[1,6] Written, Length: 98 bytes, Status: OK
[1,8] Written, Length: 110 bytes, Status: OK
[1,13] Written, Length: 98 bytes, Status: OK
[1,15] Written, Length: 4 bytes, Status: OK
[1,16] Written, Length: 98 bytes, Status: OK
[1,18] Written, Length: 98 bytes, Status: OK
[1,20] Written, Length: 98 bytes, Status: OK
[1,22] Written, Length: 16 bytes, Status: OK
[1,23] Written, Length: 4 bytes, Status: OK
[1,24] Written, Length: 84 bytes, Status: OK
[1,25] Written, Length: 4 bytes, Status: OK
[1,26] Written, Length: 110 bytes, Status: OK
[1,27] Written, Length: 4 bytes, Status: OK
[1,28] Written, Length: 98 bytes, Status: OK
[1,29] Written, Length: 10 bytes, Status: OK
[1,31] Written, Length: 98 bytes, Status: OK
[1,33] Written, Length: 36 bytes, Status: OK
[1,34] Written, Length: 80 bytes, Status: OK
[1,40] Written, Length: 16 bytes, Status: OK
[1,41] Written, Length: 182 bytes, Status: OK
[1,42] Written, Length: 4 bytes, Status: OK
[1,43] Written, Length: 36 bytes, Status: OK
[1,44] Written, Length: 182 bytes, Status: OK
[1,46] Written, Length: 64 bytes, Status: OK
[309,0] Written, Length: 4 bytes, Status: OK
[309,1] Written, Length: 2 bytes, Status: OK
[309,2] Written, Length: 12 bytes, Status: OK
[309,4] Written, Length: 12 bytes, Status: OK
[309,5] Written, Length: 12 bytes, Status: OK
[309,7] Written, Length: 12 bytes, Status: OK
[309,8] Written, Length: 12 bytes, Status: OK
[309,17] Written, Length: 12 bytes, Status: OK
Write PM Finished, Record written OK: 37, Record written NOT OK: 0


После выше проделанной работы должен восстановиться Security Analysis,но ситуация не меняется

Started Phone Security Analysis...
MCU Version V 07.10
MCU Date 15-07-09
Product RM-243 (Nokia 6120 classic)
Manufacturer (c) Nokia
IMEI 359808016439187
Mastercode 2523163761
Reading Security Block...
Security block OK and saved to "RM-243_359808016439187_08.03.2013_132807.SecurityBlock.PM"
Step 1 : Testing SIMLOCK
-- SIMLOCK PROBLEM --

Phone have failed SIMLOCK Test, that means Simlock Area is DAMAGED!
To repair simlock area, Select Unlock method : "RPL CALCULATION",
And then click DIRECT UNLOCK. SL Area will be re-formatted.

-- SIMLOCK PROBLEM --
Step 2 : Testing SECURITY
SECURITY SEFLTEST PASSED OK!
Step 3 : Analyzing Security Block
"1730001978B901584A11D929C0CF1AE792AD304A.C00045B2" Exists, That is good...
Checking SUPERDONGLE...
SUPERDONGLE FOUND AND CHECKSUM OK! PASSED!
Checking SIMLOCK...
SIMLOCK FOUND AND CHECKSUM OK! PASSED!
Checking MCU&DSP TIMESTAMPS...
MCU&DSP TIMESTAMPS FOUND AND CHECKSUM OK! PASSED!
Checking CMLA KEYS...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking ECC KEYS...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking DIV KEYS...
DIV KEYS FOUND AND CHECKSUM OK! PASSED!
Analyze finished!


Проделав Селфы
Selftests to proceed: 23
Passed ST_TAHVOINT_TEST
Passed ST_UEM_CBUS_IF_TEST
Failed ST_EAR_DATA_LOOP_TEST
Passed ST_SIM_CLK_LOOP_TEST
Passed ST_SIM_IO_CTRL_LOOP_TEST
Passed ST_SECURITY_TEST
Passed ST_PWR_KEY_TEST
Passed ST_CURRENT_CONS_TEST
Passed ST_BACKUP_BATT_TEST
Passed ST_SLEEPCLK_FREQ_TEST
Passed ST_HOOKINT_TEST
Passed ST_BTEMP_TEST
Passed ST_EXT_DEVICE_TEST
Passed ST_CDSP_RF_BB_IF_TEST
Passed ST_CDSP_RF_SUPPLY_TEST
Passed ST_CDSP_TX_IQ_TEST
Passed ST_CDSP_TXC_DATA_TEST
Passed ST_CDSP_PWR_DETECTOR_BIAS_TEST
Passed ST_CDSP_RX_PLL_PHASE_LOCK_TEST


Спецы как тест Security Analysis не все в норме помоему,оцените?Прихожу к выводу все таки это проблема из-за Авилмы,т.к.после замены на новые первые две аппарат вообще не вкл.только когда третью поставил аппарат завелся.В нашем регионе в двух местах брал новые Авилмы,но гарантий как сами понимаете нет.И весь "Failed ST_EAR_DATA_LOOP_TEST"исходит по моему от бракованной Авилмы.Возможна ли связь между ST_EAR_DATA_LOOP_TEST и ошибккой Security Analysis "Failed to decode Security Section""-- SIMLOCK PROBLEM --",и естественно с самой бракованной Авилмой?

[SUHROB9966]

Пропаяйте проц и флеш......

[denis78]

Пропаяйте проц и флеш......

Я думаю, подходящее решение, замена пары," не из новых моделей,можно найти",процессор выходит из строя, было пару случаев.

[Fluderator]

Пропаяйте проц и флеш......

Пропаял,забыл написать выше,не помогает.

[renat_d]

Спецы как тест Security Analysis не все в норме помоему,оцените?Прихожу к выводу все таки это проблема из-за Авилмы,т.к.после замены на новые первые две аппарат вообще не вкл.только когда третью поставил аппарат завелся.В нашем регионе в двух местах брал новые Авилмы,но гарантий как сами понимаете нет.
И весь "Failed ST_EAR_DATA_LOOP_TEST"исходит по моему от бракованной Авилмы.Возможна ли связь между ST_EAR_DATA_LOOP_TEST и ошибккой Security Analysis "Failed to decode Security Section""-- SIMLOCK PROBLEM --",и естественно с самой бракованной Авилмой?

ST_EAR_DATA_LOOP_TEST - стандартный тест у линейки BB5 - примерный перевод говорит - тест для проверки цепей цифрового аудиосигнала CPU<>ASIC ( а именно - RAP_RETU_TAHVO , RAPIDO_AVILMA_BETTY и RAPU_GAZOO_(PEARL) ) , в твоём случае второй вариант .


Вот пример из мануала Level 3/4 ( на базе RAP , типа 6233 etc) :

если :
ST_EAR_DATA_LOOP_TEST : FAILED!
ST_SIM_CLK_LOOP_TEST : FAILED!
ST_SIM_IO_CTRL_LOOP_TEST : FAILED!

то неисправен/намочен КП RETU.
Checking or Replacing the IC RETU can probably fix this
.IC RETU ( проблема с SIM , динамик микрофон громкая связь вибро и тд) , если замена не помогла , так же потребуется замена IC TAHVO.

Соответственно в новых поколениях платформ в качестве ASIC/UI будут использоваться aVILMA / BETTY , а также в совсем новых уже совмещённый GAZOO_(PEARL)

Вообщем я думаю ты понял мысль . Ну а так мне кажется у тебя всё таки программная неисправность , тем более у тебя есть Cyclone и я не знаю почему ты не смог с самого начала сделать этот SL2 ТА :eek: Не стал сильно вдаваться в подробности ( у самого времени наотрез нету) , потому что как то неудачно ты оформил свои посты , честно каша из информации ... Удачи !

----------------------------------------------------------------------------

Сделай erase циклоном , потом запиши чистый SW ( 7.10 , + должен быть файл APE_Variant rm243_07.10_prd_UDA_Nokia_Noir.fpsx ) и проверь - включи , можно даже SELF_TEST ( на этом этапе с IMEI 123456 - simlock и security покажет PASSED !!! ) , никакие E71_E51_blank не пиши !!! Потом восстанови *npc ( IMEI ) , следом RPL_Calculation , потом SX4_rep_SD ( можно даже несколько раз) , следом Analyse_Security и выложи лог в одном посте/

[yurii-62]

Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking ECC KEYS...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking DIV KEYS...
DIV KEYS FOUND AND CHECKSUM OK! PASSED!
Analyze finished!
Это не может быть связанно с этим? >> Модели Rapido SL2:
(ПРИМЕЧАНИЕ: версии V30/V31/V300/V400 имеют защиту от перезаписи PM308 поэтому могут быть раскодированы только через метод unlocked RPL)
5320, 5800 (бывают и SL3), 6110, 6120c, 6121c, N705i, N706i, 6124c, 6210, 6220c, 6290, 6650, 6760, 6790, E51, E63, E66 (бывают и SL3), E71, E75, N78, N79, N81, N81 8gb, N82, N85, N95 8gb, N96
Модели поддерживаемые для раскодировки через расчёт NCK кода (новый метод) Cyclone, JAF, MX-KEY

PS.Может стоит откатить на v05.11, и сделать как советовал renat_d :confused:

[Fluderator]

тест для проверки цепей цифрового аудиосигнала[/I] CPU<>ASIC RAPIDO_AVILMA_BETTYНу а так мне кажется у тебя всё таки программная неисправность

Renat спасибо за информативное сообщение,но вот обрати внимание Cyclone box пишет "Failed ST_EAR_DATA_LOOP_TEST",т.к.большего он сказать пока не может при ошибке,но вот UFSовский скриншот селфа если ты посмотрел выше я выложил ,пишет "ST_EAR_DATA_LOOP_TEST -No Signal"при ошибке UFS пишет "Minor Error" или опять таки "Failed".В большинстве случаев я все таки думаю что Уфса наверняка говорит правду,так как до него доходит результат "EAR_DATA_LOOP_"теста и он честно пишет "No Signal",и это подтверждает помоему наличие железной проблемы (обрыва в плате или брака какой-то из"RAPIDO_AVILMA_BETTY" микросхем).

[чайник]

... "EAR_DATA_LOOP_"теста и он честно пишет "No Signal",....
всего лишь вышло время отклика на поданную команду от бокса. практически ни очем не говорит. проверяется повторным (сразу) тестом.

ТС. вы сначало сделайте что-либо, в соответствии данных вам рекомендаций. если что-то не выходит, то выкладываете результаты и снова спрашиваете.

[Fluderator]

После FullErase,во время прошивки SW с циклоном файла rm243_07.10_prd_UDA_Nokia_Noir.fpsx выходит следующая ошибка
Processing rm243_07.10_prd_UDA_Nokia_Noir.fpsx (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1730001978B901584A11D929C0CF1AE792AD304A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
Processing Flash Image Failed -> Given image file is not suitable for this CMT System ASIC ID (Tick "Skip CMT ID Check" if you are sure that given Image File is suitable for this phone!).
Failed to Process all Image files -> Failed to process rm243_07.10_prd_UDA_Nokia_Noir.fpsx


Из-за этого прошил Уфсом без проблем


1ST BOOT : C0,07 [Rm-243] [2.2.0.3]
CMT ASICID: 000000010000022600010006400C192101031103
EM 1 ID : 00000295
EM 2 ID : 00000B21
CMT PUBID : 1730001978B901584A11D929C0CF1AE792AD304A
CMT MODE : 00
CMT HASH : CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT ROMID : 4B9B75103E691FF8
CMT 1ST Boot OK
CMT 2ND Bt: RAPIDOv11_2nd.fg, Ver: 1.37.1
CMT FLID0 : 00EC0030-00400221, Sam OneNAND-1G
CMT FLCNT : 00030000000000000000000000000000000000
CMT MCID0 : FFFF0000-00000000
CMT 2ND Boot OK
CMT ALGO : RAPIDOv11_algo.fg, Ver: 1.40.0
CMT KSIG0 : 0FE1BA92D924A658E4800780FA6F4868100AC947
CMT VPP : Internal
DUAL LINE : True
CMT ALG Boot OK
IMAGE : rm243_07.10_prd_core.fpsx
CMT NAND Erase Area: 0x00040000-00082FFF
CMT NAND Erase Area: 0x00083400-0087FFFF
CMT NAND Erase Area: 0x00B80000-04DFFFFF
CMT NAND Partition Format
CMT FLASH ERASE OK, Time: 00:01
Written: 11 Certificate(s)
CMT FLASH WRITE OK, Time: 03:52
IMAGE : rm243_07.10_prd_UDA_Nokia_Noir.fpsx
CMT NAND Erase Area: 0x04E00000-07B3FFFF
CNT FLASH ERASE OK, Time: 00:00
CNT FLASH WRITE OK, Time: 00:01
IMAGE : rm243_07.10_prd_vB05_03_russian.fpsx
CMT NAND Erase Area: 0x03300000-04DFFFFF
PPM FLASH ERASE OK, Time: 00:00
Written: 1 Certificate(s)
PPM FLASH WRITE OK, Time: 02:17
Flashing Completed, Rebooting Mobile
UI Defaults Ok, Time: 00:05
Set UI Factory Defaults Ok, Time: 00:00
Set Full Factory Defaults Ok, Time: 00:00
Set Software Upgrade Defaults Ok, Time: 00:00
Set Security Ok, Time: 00:00
All Done, Time: 06:44


Вот инфо с Уфсом

MCU SW : V 07.10 15-07-09 RM-243 (c) Nokia
PPM SW : 07.10
Product : Nokia 6120
Prd.Code:
Bpr.Code:
Prod.Sn : 0
HW Vers :
EM VILMA: 15
EM BETTY: 21
RFIC Ver: 17141715
DSP Vers: 06w41pb_08w28.0.1_rm243
IMEI : 123456-10-654321-
SL Serv : SIMLOCK SERVER
SL Conf : 000-00-00000000000
SL Prof : 0140196B00000000
SL Count: 00 00
SL Data Corrupted
Provider: Not Found


Но в режим селф теста не заходит ни в какую.Заходит только если сделать заново фуллеразе Циклоном и вместо ппм Уфсом записать бланк файл.И этому уже наверное железо виной?

[KorAll]

Привет. Fluderator. Тебе же Ренат всё разжевал, зачем по кускам докладывать. Делай как он пишет дальше - прошей NPC сертификат и т.д. и т.п.

Потом восстанови *npc ( IMEI ) , следом RPL_Calculation , потом SX4_rep_SD ( можно даже несколько раз) , следом Analyse_Security и выложи лог в одном посте/

Если чего не знаешь как делать, так и спрашивай.

Удачи.

P.S. А вообще запомни "золотое правило" прошивки - прежде чем шить, надо сохранить то что есть.

[yurii-62]

Но в режим селф теста не заходит ни в какую.Заходит только если сделать заново фуллеразе Циклоном и вместо ппм Уфсом записать бланк файл.И этому уже наверное железо виной?

Уже два раза писал, пробуем на v05.11 или старше, стереть пролить полный инстал v05.11, пост #22 в помощь... Все разжёвано...;) Сделать восстановление другим продуктом не пробовали, АТФ. Бест, МТвох, МХвох наконец, неужели нет ни у кого знакомых данных программаторов....

[Fluderator]

запиши чистый SW ( 7.10 , + должен быть файл APE_Variant rm243_07.10_prd_UDA_Nokia_Noir.fpsx )

Сколько всего файлов надо выбирать при прошивке этого тела.Вот мой выбор:
MCU-rm243_07.10_prd_core.fpsx
PPM-rm243_07.10_prd_vB05_03_russian.fpsx
CNT-rm243_07.10_prd_UDA_Nokia_Noir.fpsx

Это верный выбор файлов или нет?

[yurii-62]

Сколько всего файлов надо выбирать при прошивке этого тела.Вот мой выбор:
MCU-rm243_07.10_prd_core.fpsx
PPM-rm243_07.10_prd_vB05_03_russian.fpsx
CNT-rm243_07.10_prd_UDA_Nokia_Noir.fpsx

Это верный выбор файлов или нет?
А что Циклон автоматом не ставит?? или Вы не полным прошиваете?, ещё скачайте SW PM c другого ресурса, мож прошивка битая (как вариант).
Для прошивки нужно 4 файла АТФ ставит так, второй скрин с МХвох..

ЗЫ.
Пропаяйте проц и флеш......
Пропаял,забыл написать выше,не помогает.
Проребболь, пропай это не всегда помогает, отгнили или отбиты пятаки..;)

[Fluderator]

Для прошивки нужно 4 файла АТФ ставит так

У меня не хватает ENO файла в прошивке,вопрос:он обязательно должен совпадать с версией прошивки?

[yurii-62]

Держи.......................

[KorAll]

Подсказка, почему не смог прошить циклоном:

После FullErase,во время прошивки SW с циклоном файла rm243_07.10_prd_UDA_Nokia_Noir.fpsx выходит следующая ошибка

Processing Flash Image Failed -> Given image file is not suitable for this CMT System ASIC ID (Tick "Skip CMT ID Check" if you are sure that given Image File is suitable for this phone!).
Failed to Process all Image files -> Failed to process rm243_07.10_prd_UDA_Nokia_Noir.fpsx

Почти дословно выделенный текст - Обработка Flash Image прекращена -> Данный image file не соответствует CMT System ASIC ID (Отметте "Skip CMT ID Check" если вы уверены что данный Image File соответствует этому телефону!)

Tick - поставить галку
Untick - снять галку.

Удачи.

[Fluderator]

Вот весь лог проделанный Циклоном в порядке его последовательности

Фулл Еразе
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1730001978B901584A11D929C0CF1AE792AD304A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC003000000221, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0030 (Samsung), Size: 128MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.12.8.0, Algo: XSR 1.5
Initializing TurboCache...
TurboCache Loaded!
Writing CMT PASUBTOC Certificate...
Writing CMT ALG Certificate...
CMT Algorithm Ready!
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Adding FUR Client (CMT, State: Ready)...
CMT FUR Ready!
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 0FE1BA92D924A658E4800780FA6F4868100AC947
APE Subsystem Not Found
Flashbus Write baud set to 5.0Mbits
Erasing flash chip...
Started group flash erase
EraseArea[0,CMT]: 0x00000000-0x07FFFFFF, ONENAND
Waiting 640s for erasure finish...
Erase taken 1.437s
Restarting MCU...
BB5 Full Erase Finished!

Прошивка
Processing pre flash tasks...
Pre flash tasks finished, continuing...
Processing rm243_07.10_prd_core.fpsx (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1730001978B901584A11D929C0CF1AE792AD304A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
rm243_07.10_prd_core.fpsx, Type: Flash Image, Algo: BB5, XSR 1.5
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.0, Algo: BB5
Flashbus Write baud set to 650Kbits
Flashbus Read baud set to 98Kbits
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,CMT]: 0xFFFFFFFF00000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC003000000221, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0030 (Samsung), Size: 128MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.12.8.0, Algo: XSR 1.5
Initializing TurboCache...
TurboCache Loaded!
Writing CMT PASUBTOC Certificate...
Writing CMT ALG Certificate...
CMT Algorithm Ready!
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Adding FUR Client (CMT, State: Ready)...
CMT FUR Ready!
Box VPP disabled
Internal CMT Phone VPP Enabled
Warning: PAPUBKEYS Hash Missing!
Flashbus Write baud set to 5.0Mbits
Sending Certificates...
Certificates OK
Partitioning...
Partitioning OK
Started group flash erase
EraseArea[0,CMT]: 0x00040000-0x00082FFF, ONENAND
EraseArea[0,CMT]: 0x00083400-0x0087FFFF, ONENAND
EraseArea[0,CMT]: 0x00B80000-0x04DFFFFF, ONENAND
Erase Partition (CMT)
Waiting 320s for erasure finish...
Erase taken 0.953s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT ADA Certificate...
Writing CMT KEYS Certificate...
Writing CMT PRIMAPP Certificate...
Writing CMT RAP3NAND Certificate...
Writing CMT PASUBTOC Certificate...
WARNING: CMT PAPUBKEYS Hash is Empty, writing first found PAPUBKEYS
Writing CMT PAPUBKEYS Certificate...
Writing CMT SOS*UPDAPP Certificate...
Writing CMT SOS*DSP0 Certificate...
Writing CMT SOS*ISASW Certificate...
Writing CMT SOS*CORE Certificate...
Writing CMT SOS+ROFS Certificate...
Programming Status OK!
All blocks written OK! Time taken 48.828s
Flashing Speed: 7496,31 kBit/S
Restarting MCU...
Processing rm243_07.10_prd_core.fpsx (APE)...
Processing rm243_07.10_prd_vB05_03_russian.fpsx (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1730001978B901584A11D929C0CF1AE792AD304A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
rm243_07.10_prd_vB05_03_russian.fpsx, Type: Flash Image, Algo: BB5, XSR 1.5
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.0, Algo: BB5
Flashbus Write baud set to 650Kbits
Flashbus Read baud set to 98Kbits
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC003000000221, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0030 (Samsung), Size: 128MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.12.8.0, Algo: XSR 1.5
Initializing TurboCache...
TurboCache Loaded!
Writing CMT PASUBTOC Certificate...
Writing CMT ALG Certificate...
CMT Algorithm Ready!
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Adding FUR Client (CMT, State: Ready)...
CMT FUR Ready!
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 0FE1BA92D924A658E4800780FA6F4868100AC947
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x03300000-0x04DFFFFF, ONENAND
Waiting 320s for erasure finish...
Erase taken 0.329s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT SOS+ROFX Certificate...
Programming Status OK!
All blocks written OK! Time taken 27.781s
Flashing Speed: 7175,30 kBit/S
Restarting MCU...
Processing rm243_07.10_prd_vB05_03_russian.fpsx (APE)...
Processing rm243_ENO_A_2009wk15v0.100.fpsx (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1730001978B901584A11D929C0CF1AE792AD304A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
rm243_ENO_A_2009wk15v0.100.fpsx, Type: Flash Image, Algo: BB5, XSR 1.5
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.0, Algo: BB5
Flashbus Write baud set to 650Kbits
Flashbus Read baud set to 98Kbits
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC003000000221, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0030 (Samsung), Size: 128MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.12.8.0, Algo: XSR 1.5
Initializing TurboCache...
TurboCache Loaded!
Writing CMT PASUBTOC Certificate...
Writing CMT ALG Certificate...
CMT Algorithm Ready!
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Adding FUR Client (CMT, State: Ready)...
CMT FUR Ready!
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 0FE1BA92D924A658E4800780FA6F4868100AC947
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x00880000-0x00B7FFFF, ONENAND
Waiting 320s for erasure finish...
Erase taken 0.47s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT SOS*ENO Certificate...
Programming Status OK!
All blocks written OK! Time taken 1.687s
Flashing Speed: 6991,72 kBit/S
Restarting MCU...
Processing rm243_ENO_A_2009wk15v0.100.fpsx (APE)...
Processing rm243_07.10_prd_UDA_Pink.fpsx (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1730001978B901584A11D929C0CF1AE792AD304A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
rm243_07.10_prd_UDA_Pink.fpsx, Type: Flash Image, Algo: BB5, XSR 1.5
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.0, Algo: BB5
Flashbus Write baud set to 650Kbits
Flashbus Read baud set to 98Kbits
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC003000000221, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0030 (Samsung), Size: 128MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.12.8.0, Algo: XSR 1.5
Initializing TurboCache...
TurboCache Loaded!
Writing CMT PASUBTOC Certificate...
Writing CMT ALG Certificate...
CMT Algorithm Ready!
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Adding FUR Client (CMT, State: Ready)...
CMT FUR Ready!
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 0FE1BA92D924A658E4800780FA6F4868100AC947
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x04E00000-0x07B3FFFF, ONENAND
Waiting 320s for erasure finish...
Erase taken 0.531s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Programming Status OK!
All blocks written OK! Time taken 0.953s
Flashing Speed: 956,90 kBit/S
Restarting MCU...
Processing rm243_07.10_prd_UDA_Pink.fpsx (APE)...
All images processed OK! Processing post flash tasks...
Post flash tasks finished!
Flashing successfully finished!


В одно сообщение не помещается,продолжение лога ниже...

[Fluderator]

Продолжение выше изложенного лога:

СелфТест
Selftests to proceed: 31
Passed ST_TAHVOINT_TEST
Passed ST_UEM_CBUS_IF_TEST
Failed ST_EAR_DATA_LOOP_TEST
Passed ST_SIM_CLK_LOOP_TEST
Passed ST_SIM_IO_CTRL_LOOP_TEST
Passed ST_SECURITY_TEST
Passed ST_PWR_KEY_TEST
Passed ST_CURRENT_CONS_TEST
Passed ST_BACKUP_BATT_TEST
Passed ST_SLEEPCLK_FREQ_TEST
Passed ST_HOOKINT_TEST
Passed ST_BTEMP_TEST
Passed ST_EXT_DEVICE_TEST
Passed ST_CDSP_RF_BB_IF_TEST
Passed ST_CDSP_RF_SUPPLY_TEST
Passed ST_CDSP_TX_IQ_TEST
Passed ST_CDSP_TXC_DATA_TEST
Passed ST_CDSP_PWR_DETECTOR_BIAS_TEST
Passed ST_CDSP_RX_PLL_PHASE_LOCK_TEST
Passed ST_CDSP_TX_PLL_PHASE_LOCK_TEST



Запись РПЛ и НПС
Skipping RPL decryption...
Parsing decrypted RPL...
Processing FBUS Part...
Writing Simlock...
Handling as SL1/SL2 Simlock Data
Simlock NOT ACCEPTED !
Processing FLASHBUS Part...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1730001978B901584A11D929C0CF1AE792AD304A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC003000000221, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0030 (Samsung), Size: 128MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.12.8.0, Algo: XSR 1.5
Initializing TurboCache...
TurboCache Loaded!
Writing CMT PASUBTOC Certificate...
Writing CMT ALG Certificate...
CMT Algorithm Ready!
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Adding FUR Client (CMT, State: Ready)...
CMT FUR Ready!
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 0FE1BA92D924A658E4800780FA6F4868100AC947
APE Subsystem Not Found
Flashbus Write baud set to 5.0Mbits
CMT NPC Erased
CMT NPC Written
CMT HWC Erased
CMT HWC Written
CMT CCC Erased
CMT CCC Written
Restarting MCU...
Processing FBUS Part...
Writing Simlock...
Handling as SL1/SL2 Simlock Data
Simlock NOT ACCEPTED !
Processing FLASHBUS Part...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1730001978B901584A11D929C0CF1AE792AD304A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC003000000221, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0030 (Samsung), Size: 128MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.12.8.0, Algo: XSR 1.5
Initializing TurboCache...
TurboCache Loaded!
Writing CMT PASUBTOC Certificate...
Writing CMT ALG Certificate...
CMT Algorithm Ready!
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Adding FUR Client (CMT, State: Ready)...
CMT FUR Ready!
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 0FE1BA92D924A658E4800780FA6F4868100AC947
APE Subsystem Not Found
Flashbus Write baud set to 5.0Mbits
CMT NPC Erased
CMT NPC Written
CMT HWC Erased
CMT HWC Written
CMT CCC Erased
CMT CCC Written
Restarting MCU...
Write RPL Finished!
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1730001978B901584A11D929C0CF1AE792AD304A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC003000000221, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0030 (Samsung), Size: 128MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.12.8.0, Algo: XSR 1.5
Initializing TurboCache...
TurboCache Loaded!
Writing CMT PASUBTOC Certificate...
Writing CMT ALG Certificate...
CMT Algorithm Ready!
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Adding FUR Client (CMT, State: Ready)...
CMT FUR Ready!
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 0FE1BA92D924A658E4800780FA6F4868100AC947
APE Subsystem Not Found
Flashbus Write baud set to 5.0Mbits
Processing 1730001978B901584A11D929C0CF1AE792AD304A_28.02.2013_110039.NPC.CMT.crt...
CMT NPC Erased
CMT NPC Written
Write CMT NPC Certificate finished
Restarting MCU...
All files processed OK!


RPL Calculation
BB5 Unlock Started...
MCU Version V 07.10
MCU Date 15-07-09
Product RM-243 (Nokia 6120 classic)
Manufacturer (c) Nokia
IMEI 359808016439187
Mastercode 2523163761
Warning: Failed to read SP Info, Assuming defaults
Simlock Server SIMLOCK SERVER
Simlock Key 0000000000000000
Simlock Profile
Simlock Key Cnt 0
Simlock FBUS Cnt 0
Reading Security Block...
Security block OK and saved to "RM-243_359808016439187_17.03.2013_132008.SecurityBlock.PM"
"1730001978B901584A11D929C0CF1AE792AD304A.C00045B2" Exists, That is good...
Checking for Rootkey Hash support with selected Unlock Method...
Selected Unlock Method: RPL Calculation
Asking box to calculate RPL...
Received RPL from Box OK!
Writing Simlock...
Simlock ACCEPTED OK !
MCU Version V 07.10
MCU Date 15-07-09
Product RM-243 (Nokia 6120 classic)
Manufacturer (c) Nokia
IMEI 359808016439187
Mastercode 2523163761
Simlock Server SIMLOCK SERVER
Simlock Key 2440700000000000
Simlock Profile 8000000000000006
Simlock Key Cnt 0
Simlock FBUS Cnt 0
Simlock [1,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [1,2] State: OPENED Type: GID Data: FFFF
Simlock [1,3] State: OPENED Type: GID Data: FFFF
Simlock [1,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [1,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [2,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [2,2] State: OPENED Type: GID Data: FFFF
Simlock [2,3] State: OPENED Type: GID Data: FFFF
Simlock [2,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [2,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [3,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [3,2] State: OPENED Type: GID Data: FFFF
Simlock [3,3] State: OPENED Type: GID Data: FFFF
Simlock [3,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [3,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [4,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [4,2] State: OPENED Type: GID Data: FFFF
Simlock [4,3] State: OPENED Type: GID Data: FFFF
Simlock [4,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [4,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [5,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [5,2] State: OPENED Type: GID Data: FFFF
Simlock [5,3] State: OPENED Type: GID Data: FFFF
Simlock [5,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [5,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [6,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [6,2] State: OPENED Type: GID Data: FFFF
Simlock [6,3] State: OPENED Type: GID Data: FFFF
Simlock [6,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [6,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [7,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [7,2] State: OPENED Type: GID Data: FFFF
Simlock [7,3] State: OPENED Type: GID Data: FFFF
Simlock [7,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [7,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Unlock finished! Time taken 3.391s


SX4_rep_SD
SX4 Authorization / SD Repair Procedure Started....
"1730001978B901584A11D929C0CF1AE792AD304A.C00045B2" Exists, That is good...
MCU Version V 07.10
MCU Date 15-07-09
Product RM-243 (Nokia 6120 classic)
Manufacturer (c) Nokia
IMEI 359808016439187
Mastercode 2523163761
Reading Security Block...
Security block OK and saved to "RM-243_359808016439187_17.03.2013_132134.SecurityBlock.PM"
Superdongle Key is probably CORRUPTED, Writing custom keys...
Received SD Keys from box, writing to phone...
Superdongle Key ACCEPTED OK !
SX4 Status: Not authorized (76)
Started mutual authenthication with card...
Receiving Phone Seed 1...
Phone Seed 1 Received
Sending calculated Data 1, and expecting Seed 2...
Calculated Data 1 accepted, Phone Seed 2 Received
Sending calculated Data 2
Calculated Data 2 sent, Checking Authorization Status again
Authorization successfully finished!
Looking for Virgin PM In Database...
Found, writing...
[1,0] Written, Length: 114 bytes, Status: OK
[1,1] Written, Length: 4 bytes, Status: OK
[1,2] Written, Length: 98 bytes, Status: OK
[1,4] Written, Length: 110 bytes, Status: OK
[1,5] Written, Length: 4 bytes, Status: OK
[1,6] Written, Length: 98 bytes, Status: OK
[1,8] Written, Length: 110 bytes, Status: OK
[1,13] Written, Length: 98 bytes, Status: OK
[1,15] Written, Length: 4 bytes, Status: OK
[1,16] Written, Length: 98 bytes, Status: OK
[1,18] Written, Length: 98 bytes, Status: OK
[1,20] Written, Length: 98 bytes, Status: OK
[1,22] Written, Length: 16 bytes, Status: OK
[1,23] Written, Length: 4 bytes, Status: OK
[1,24] Written, Length: 84 bytes, Status: OK
[1,25] Written, Length: 4 bytes, Status: OK
[1,26] Written, Length: 110 bytes, Status: OK
[1,27] Written, Length: 4 bytes, Status: OK
[1,28] Written, Length: 98 bytes, Status: OK
[1,29] Written, Length: 10 bytes, Status: OK
[1,31] Written, Length: 98 bytes, Status: OK
[1,33] Written, Length: 36 bytes, Status: OK
[1,34] Written, Length: 80 bytes, Status: OK
[1,40] Written, Length: 16 bytes, Status: OK
[1,41] Written, Length: 182 bytes, Status: OK
[1,42] Written, Length: 4 bytes, Status: OK
[1,43] Written, Length: 36 bytes, Status: OK
[1,44] Written, Length: 182 bytes, Status: OK
[1,46] Written, Length: 64 bytes, Status: OK
[309,0] Written, Length: 4 bytes, Status: OK
[309,1] Written, Length: 2 bytes, Status: OK
[309,2] Written, Length: 12 bytes, Status: OK
[309,4] Written, Length: 12 bytes, Status: OK
[309,5] Written, Length: 12 bytes, Status: OK
[309,7] Written, Length: 12 bytes, Status: OK
[309,8] Written, Length: 12 bytes, Status: OK
[309,17] Written, Length: 12 bytes, Status: OK
Write PM Finished, Record written OK: 37, Record written NOT OK: 0


Analyse_Security
Started Phone Security Analysis...
MCU Version V 07.10
MCU Date 15-07-09
Product RM-243 (Nokia 6120 classic)
Manufacturer (c) Nokia
IMEI 359808016439187
Mastercode 2523163761
Reading Security Block...
Security block OK and saved to "RM-243_359808016439187_17.03.2013_132323.SecurityBlock.PM"
Step 1 : Testing SIMLOCK
-- SIMLOCK PROBLEM --

Phone have failed SIMLOCK Test, that means Simlock Area is DAMAGED!
To repair simlock area, Select Unlock method : "RPL CALCULATION",
And then click DIRECT UNLOCK. SL Area will be re-formatted.

-- SIMLOCK PROBLEM --
Step 2 : Testing SECURITY
SECURITY SEFLTEST PASSED OK!
Step 3 : Analyzing Security Block
"1730001978B901584A11D929C0CF1AE792AD304A.C00045B2" Exists, That is good...
Checking SUPERDONGLE...
SUPERDONGLE FOUND AND CHECKSUM OK! PASSED!
Checking SIMLOCK...
SIMLOCK FOUND AND CHECKSUM OK! PASSED!
Checking MCU&DSP TIMESTAMPS...
MCU&DSP TIMESTAMPS FOUND AND CHECKSUM OK! PASSED!
Checking CMLA KEYS...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking ECC KEYS...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking DIV KEYS...
DIV KEYS FOUND AND CHECKSUM OK! PASSED!
Analyze finished!


На данный момент аппарат ведет себя так-же,включается надпись "Nokia" и перезагруз.Все мои программные действия в логе.Думаю что ПМ пролился во все блоки при Sx4 или его отдельно надо записывать?

[KorAll]

Что бросилось в глаза при просмотре:

Phone have failed SIMLOCK Test, that means Simlock Area is DAMAGED!
To repair simlock area, Select Unlock method : "RPL CALCULATION",
And then click DIRECT UNLOCK. SL Area will be re-formatted.

Дословно - ТА имеет повреждённый SIMLOCK Test, что означает Simlock Area повреждена. Для ремонта выберите анлок метод:"RPL CALCULATION".
Затем клик DIRECT UNLOCK. Ты так делал или иначе? Если так не делал - то пробуй.


Checking CMLA KEYS...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)

Это наверно только ATF сделать может? Поэтому на будущее - 1, 120, 308 и 309 блоки PM сохраняй перед любым стиранием.

Удачи.

P.S. Думаю что ПМ пролился во все блоки при Sx4 или его отдельно надо записывать?
При Sx4 ты записал 1 и 309 блоки, а главный гемор из-за 120 и 308 которых нет или разрушены! Поправте если я ошибаюсь.

[Fluderator]

должен быть файл APE_Variant rm243_07.10_prd_UDA_Nokia_Noir.fpsx

Вот эти все файлы в моей прошивке относятся к APE_Variant проверьте пожалуйста спецы они ли это:
1)rm243_07.10_prd_UDA_Classic_Red.fpsx
2)rm243_07.10_prd_UDA_Pearl_White.fpsx
3)rm243_07.10_prd_UDA_Sand_Gold.fpsx
4)rm243_07.10_prd_UDA_Classic_Blue.fpsx
5)rm243_07.10_prd_UDA_Nokia_Noir.fpsx
6)rm243_07.10_prd_UDA_Pink.fpsx

Из них Циклон записывает только этот rm243_07.10_prd_UDA_Pink.fpsx,на других ошибку дает выше описануую.

Вот скрин циклона с порядком выбора файлов для прошивки 108433 верный ли выбор файлов?

[Shmastik]

Вот эти все файлы в моей прошивке относятся к APE_Variant проверьте пожалуйста спецы они ли это:
1)rm243_07.10_prd_UDA_Classic_Red.fpsx
2)rm243_07.10_prd_UDA_Pearl_White.fpsx
3)rm243_07.10_prd_UDA_Sand_Gold.fpsx
4)rm243_07.10_prd_UDA_Classic_Blue.fpsx
5)rm243_07.10_prd_UDA_Nokia_Noir.fpsx
6)rm243_07.10_prd_UDA_Pink.fpsx

Из них Циклон записывает только этот rm243_07.10_prd_UDA_Pink.fpsx,на других ошибку дает выше описануую.

Вот скрин циклона с порядком выбора файлов для прошивки 108433 верный ли выбор файлов?

Опять 25. Возьми и скачай полную прошивку, желательно по продукт коду и тогда Циклон сам выставит нужные тебе файлы.
Есть такая программка NaviFirm она тебе поможет качнуть прошивочку с серверов нокиа.

[yurii-62]

На данный момент аппарат ведет себя так-же,включается надпись "Nokia" и перезагруз.Все мои программные действия в логе.Думаю что ПМ пролился во все блоки при Sx4 или его отдельно надо записывать?
Офф.Переводчик Google - Google Translate>> http://www.google.ru/search?client=opera&rls=ru&q=http://translate.google.com/?hl=ru&sourceid=opera&ie=utf-8&oe=utf-8&channel=suggest
Попробуйте пользоваться этим, для прочтения Ваших логов, 2 в разделах ATF, BEST, MXbox, Циклон есть даже видео инструкции по решению Вашего вопроса, думаю что при внимательном прочтении, и просмотре как это делать вопросы отпадут сами собой..;)Хотя если вдумчиво прочитать эту тему тут Все разжёвано, ток осталось собраться форумом приехать и сделать Вам эту несчастную NOKIA.. :D

[yurii-62]

Fluderator

PS.
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
Обратите внимание на это, кабель необходим 7 пиновый или он дефектный.
2. В Циклоне вроде должен использоваться адаптер JAF/UFS? для кабеля.

После успешного ремонта SuperDongle и/или Simlock это происходит из-за отсутствия HWC и CCC полей. Из-за этого телефон находится в Contact Retailer или Contact Service даже если Simlock и SuperDongle в порядке.

Решение 1 (помогает не всегда, зависит от степени повреждения ПО телефона):

Запишите полный PM от телефона той же модели (с тем же product code) без полей 1, 308, 309 (и без поля 120 для SL20 телефонов)
Отключите / подключите телефон боксу !!!
Сделайте Simlock RPL repair
Сделайте SD RPL repair
Отключите / подключите телефон к боксу !!!
Сделайте SUPER SX4 Auth и затем запишите 1 и 309 поля PM

Если это не помогает, то используйте Решение 2:

Сделайте бэкап RPL (NPC, CCC, HWC, ...), назов***1104;м его ORIGINAL RPL
Сделайте бэкап RPL из другого рабочего телефона (такой же модели) с таким же product code
Отредактируйте этот хороший RPL из другого телефона удалив NPC секцию (все линии которые начинаются с NPC_DATA_1 ... NPC_DATA_xx), будем называть этот отредактированный файл CLONE RPL

Сделайте бэкап PM из другого рабочего телефона (такой же модели) с таким же product code,
назов***1104;м этот файл CLONE PM
Полностью сотрите флэш чип
Прошейте телефон (CMT, APE, ...)
Загрузите CLONE RPL
Загрузите ORIGINAL RPL
Запишите полный CLONE PM без 1,120,308,309 полей
Отключите / подключите телефон боксу !!!
Сделайте Simlock RPL repair
Сделайте SD RPL repair
Отключите / подключите телефон боксу !!!
Сделайте SUPER SX4 Auth и затем запишите 1 и 309 поля PM
Приложил что необходимо для этого, рабочие. Как это сделать циклоном думаю разберётесь..

[Fluderator]

В Циклоне вроде должен использоваться адаптер JAF/UFS? для кабеля.

Этот кабель я использую,желтый адаптер,без него Bb5 платформы не прошивает,а вот почему это ошибка выходит не пойму.Кабель разбирал,прозванивал все гуд.

[yurii-62]

Этот кабель я использую,желтый адаптер,без него Bb5 платформы не прошивает,а вот почему это ошибка выходит не пойму.Кабель разбирал,прозванивал все гуд.

Встречался с таким, все вроде в норме а не работает, может зависеть от качества самих проводов, береш другой все гуд, но вообще сейчас пользуюсь прищепками удобно, и с сопротивлением поиграть можно что не мало важно особенно с проблемными телами, советую...;)
ЗЫ. а по USB делать пробовал..? Проребболь все таки проц флеш, начни с флеш, может по ими какая бяка или отбито чо.

[Fluderator]

чек

Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1730001978B901584A11D929C0CF1AE792AD304A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC003000000221, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0030 (Samsung), Size: 128MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.12.8.0, Algo: XSR 1.5
Initializing TurboCache...
TurboCache Loaded!
Writing CMT PASUBTOC Certificate...
Writing CMT ALG Certificate...
CMT Algorithm Ready!
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Adding FUR Client (CMT, State: Ready)...
CMT FUR Ready!
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 0FE1BA92D924A658E4800780FA6F4868100AC947
APE Boot skipped on user request
Flashbus Write baud set to 5.0Mbits
Restarting MCU...


РПЛ
Skipping RPL decryption...
Parsing decrypted RPL...
Processing FBUS Part...
Processing FLASHBUS Part...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1730001978B901584A11D929C0CF1AE792AD304A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC003000000221, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0030 (Samsung), Size: 128MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.12.8.0, Algo: XSR 1.5
Initializing TurboCache...
TurboCache Loaded!
Writing CMT PASUBTOC Certificate...
Writing CMT ALG Certificate...
CMT Algorithm Ready!
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Adding FUR Client (CMT, State: Ready)...
CMT FUR Ready!
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 0FE1BA92D924A658E4800780FA6F4868100AC947
APE Subsystem Not Found
Flashbus Write baud set to 5.0Mbits
CMT HWC Erased
CMT HWC Written
CMT CCC Erased
CMT CCC Written
Restarting MCU...
Write RPL Finished!


PM
[1,0] Written, Length: 114 bytes, Status: Not accepted, Code: 19
[1,1] Written, Length: 4 bytes, Status: Not accepted, Code: 19
[1,2] Written, Length: 98 bytes, Status: Not accepted, Code: 19
[1,4] Written, Length: 110 bytes, Status: Not accepted, Code: 19
[1,5] Written, Length: 4 bytes, Status: Not accepted, Code: 19
[1,6] Written, Length: 98 bytes, Status: Not accepted, Code: 19
[1,8] Written, Length: 110 bytes, Status: Not accepted, Code: 19
[1,13] Written, Length: 98 bytes, Status: Not accepted, Code: 19
[1,15] Written, Length: 4 bytes, Status: Not accepted, Code: 19
[1,16] Written, Length: 98 bytes, Status: Not accepted, Code: 19
[1,18] Written, Length: 98 bytes, Status: Not accepted, Code: 19
[1,20] Written, Length: 98 bytes, Status: Not accepted, Code: 19
[1,22] Written, Length: 16 bytes, Status: Not accepted, Code: 19
[1,23] Written, Length: 4 bytes, Status: Not accepted, Code: 19
[1,24] Written, Length: 84 bytes, Status: Not accepted, Code: 19
[1,25] Written, Length: 4 bytes, Status: Not accepted, Code: 19
[1,26] Written, Length: 110 bytes, Status: Not accepted, Code: 19
[1,27] Written, Length: 4 bytes, Status: Not accepted, Code: 19
[1,28] Written, Length: 98 bytes, Status: Not accepted, Code: 19
[1,29] Written, Length: 10 bytes, Status: Not accepted, Code: 19
[1,31] Written, Length: 98 bytes, Status: Not accepted, Code: 19
[1,33] Written, Length: 36 bytes, Status: Not accepted, Code: 19
[1,34] Written, Length: 80 bytes, Status: Not accepted, Code: 19
[1,40] Written, Length: 16 bytes, Status: Not accepted, Code: 19
[1,41] Written, Length: 182 bytes, Status: Not accepted, Code: 19
[1,42] Written, Length: 4 bytes, Status: Not accepted, Code: 19
[1,43] Written, Length: 36 bytes, Status: Not accepted, Code: 19
[1,44] Written, Length: 182 bytes, Status: Not accepted, Code: 19
[1,46] Written, Length: 64 bytes, Status: Not accepted, Code: 19
[2,0] Written, Length: 440 bytes, Status: OK
[4,1] Written, Length: 1020 bytes, Status: OK
[4,3] Written, Length: 10 bytes, Status: OK
[4,4] Written, Length: 8 bytes, Status: OK
[4,5] Written, Length: 8 bytes, Status: OK
[4,9] Written, Length: 5 bytes, Status: OK
[4,28] Written, Length: 2 bytes, Status: OK
[8,0] Written, Length: 12 bytes, Status: OK
[8,1] Written, Length: 12 bytes, Status: OK
[8,2] Written, Length: 128 bytes, Status: OK
[8,3] Written, Length: 128 bytes, Status: OK
[8,6] Written, Length: 4 bytes, Status: OK
[8,7] Written, Length: 8 bytes, Status: OK
[8,8] Written, Length: 8 bytes, Status: OK
[8,9] Written, Length: 16 bytes, Status: OK
[11,0] Written, Length: 4 bytes, Status: OK
[11,1] Written, Length: 4 bytes, Status: OK
[11,2] Written, Length: 4 bytes, Status: OK
[11,3] Written, Length: 4 bytes, Status: OK
[11,4] Written, Length: 1 bytes, Status: OK
[11,5] Written, Length: 6 bytes, Status: OK
[11,6] Written, Length: 1 bytes, Status: OK
[11,7] Written, Length: 2 bytes, Status: OK
[11,8] Written, Length: 2 bytes, Status: OK
[11,9] Written, Length: 2 bytes, Status: OK
[11,10] Written, Length: 2 bytes, Status: OK
[11,11] Written, Length: 2 bytes, Status: OK
[11,12] Written, Length: 1 bytes, Status: OK
[11,13] Written, Length: 1 bytes, Status: OK
[11,14] Written, Length: 1 bytes, Status: OK
[11,15] Written, Length: 1 bytes, Status: OK
[11,16] Written, Length: 1 bytes, Status: OK
[11,17] Written, Length: 1 bytes, Status: OK
[11,18] Written, Length: 1 bytes, Status: OK
[11,19] Written, Length: 2 bytes, Status: OK
[11,20] Written, Length: 2 bytes, Status: OK
[11,21] Written, Length: 1 bytes, Status: OK
[11,22] Written, Length: 1 bytes, Status: OK
[11,23] Written, Length: 4 bytes, Status: OK
[11,24] Written, Length: 4 bytes, Status: OK
[11,25] Written, Length: 2 bytes, Status: OK
[11,26] Written, Length: 2 bytes, Status: OK
[11,27] Written, Length: 2 bytes, Status: OK
[11,28] Written, Length: 2 bytes, Status: OK
[11,29] Written, Length: 1 bytes, Status: OK
[11,30] Written, Length: 1 bytes, Status: OK
[11,31] Written, Length: 1 bytes, Status: OK
[11,32] Written, Length: 1 bytes, Status: OK
[11,33] Written, Length: 1 bytes, Status: OK
[11,34] Written, Length: 1 bytes, Status: OK
[11,35] Written, Length: 1 bytes, Status: OK
[11,36] Written, Length: 1 bytes, Status: OK
[11,37] Written, Length: 1 bytes, Status: OK
[11,38] Written, Length: 2 bytes, Status: OK
[11,39] Written, Length: 2 bytes, Status: OK
[11,40] Written, Length: 2 bytes, Status: OK
[11,41] Written, Length: 2 bytes, Status: OK
[11,42] Written, Length: 2 bytes, Status: OK
[11,43] Written, Length: 4 bytes, Status: OK
[11,44] Written, Length: 4 bytes, Status: OK
[11,45] Written, Length: 4 bytes, Status: OK
[11,46] Written, Length: 1 bytes, Status: OK
[11,47] Written, Length: 16 bytes, Status: OK
[11,48] Written, Length: 2 bytes, Status: OK
[11,49] Written, Length: 2 bytes, Status: OK
[11,50] Written, Length: 20 bytes, Status: OK
[11,51] Written, Length: 10 bytes, Status: OK
[11,52] Written, Length: 2 bytes, Status: OK
[11,53] Written, Length: 20 bytes, Status: OK
[11,54] Written, Length: 10 bytes, Status: OK
[11,55] Written, Length: 1 bytes, Status: OK
[11,56] Written, Length: 1 bytes, Status: OK
[11,57] Written, Length: 1 bytes, Status: OK
[11,58] Written, Length: 1 bytes, Status: OK
[11,59] Written, Length: 1 bytes, Status: OK
[11,60] Written, Length: 1 bytes, Status: OK
[11,61] Written, Length: 1 bytes, Status: OK
[11,62] Written, Length: 1 bytes, Status: OK
[11,63] Written, Length: 1 bytes, Status: OK
[11,64] Written, Length: 1 bytes, Status: OK
[11,65] Written, Length: 1 bytes, Status: OK
[11,66] Written, Length: 32 bytes, Status: OK
[11,67] Written, Length: 32 bytes, Status: OK
[11,68] Written, Length: 2 bytes, Status: OK
[11,69] Written, Length: 2 bytes, Status: OK
[11,70] Written, Length: 2 bytes, Status: OK
[11,71] Written, Length: 2 bytes, Status: OK
[11,72] Written, Length: 2 bytes, Status: OK
[11,73] Written, Length: 2 bytes, Status: OK
[11,74] Written, Length: 2 bytes, Status: OK
[11,75] Written, Length: 2 bytes, Status: OK
[11,76] Written, Length: 2 bytes, Status: OK
[11,77] Written, Length: 2 bytes, Status: OK
[11,78] Written, Length: 2 bytes, Status: OK
[11,79] Written, Length: 2 bytes, Status: OK
[11,80] Written, Length: 2 bytes, Status: OK
[11,81] Written, Length: 2 bytes, Status: OK
[11,82] Written, Length: 2 bytes, Status: OK
[11,83] Written, Length: 2 bytes, Status: OK
[11,84] Written, Length: 2 bytes, Status: OK
[11,85] Written, Length: 2 bytes, Status: OK
[11,86] Written, Length: 2 bytes, Status: OK
[11,87] Written, Length: 2 bytes, Status: OK
[11,88] Written, Length: 2 bytes, Status: OK
[11,89] Written, Length: 2 bytes, Status: OK
[11,90] Written, Length: 2 bytes, Status: OK
[11,91] Written, Length: 2 bytes, Status: OK
[11,92] Written, Length: 2 bytes, Status: OK
[11,93] Written, Length: 2 bytes, Status: OK
[11,94] Written, Length: 2 bytes, Status: OK
[11,95] Written, Length: 2 bytes, Status: OK
[11,96] Written, Length: 2 bytes, Status: OK
[11,97] Written, Length: 2 bytes, Status: OK
[11,98] Written, Length: 2 bytes, Status: OK
[11,99] Written, Length: 2 bytes, Status: OK
[11,100] Written, Length: 2 bytes, Status: OK
[11,101] Written, Length: 2 bytes, Status: OK
[11,102] Written, Length: 2 bytes, Status: OK
[11,103] Written, Length: 2 bytes, Status: OK
[11,104] Written, Length: 2 bytes, Status: OK
[11,105] Written, Length: 2 bytes, Status: OK
[11,106] Written, Length: 2 bytes, Status: OK
[11,107] Written, Length: 2 bytes, Status: OK
[11,108] Written, Length: 2 bytes, Status: OK
[11,109] Written, Length: 2 bytes, Status: OK
[11,110] Written, Length: 2 bytes, Status: OK
[11,111] Written, Length: 2 bytes, Status: OK
[11,112] Written, Length: 2 bytes, Status: OK
[11,113] Written, Length: 2 bytes, Status: OK
[11,114] Written, Length: 2 bytes, Status: OK
[11,115] Written, Length: 2 bytes, Status: OK
[11,116] Written, Length: 4 bytes, Status: OK
[11,117] Written, Length: 4 bytes, Status: OK
[11,118] Written, Length: 1 bytes, Status: OK
[11,119] Written, Length: 4 bytes, Status: OK
[11,120] Written, Length: 4 bytes, Status: OK
[11,121] Written, Length: 4 bytes, Status: OK
[11,122] Written, Length: 4 bytes, Status: OK
[11,123] Written, Length: 16 bytes, Status: OK
[11,124] Written, Length: 4 bytes, Status: OK
[11,125] Written, Length: 2 bytes, Status: OK
[11,126] Written, Length: 2 bytes, Status: OK
[11,127] Written, Length: 1437 bytes, Status: OK
[12,0] Written, Length: 102 bytes, Status: OK
[26,0] Written, Length: 16 bytes, Status: OK
[26,1] Written, Length: 68 bytes, Status: OK
[31,4] Written, Length: 20 bytes, Status: OK
[44,0] Written, Length: 1 bytes, Status: OK
[50,0] Written, Length: 2 bytes, Status: OK
[54,0] Written, Length: 2 bytes, Status: OK
[54,2] Written, Length: 24 bytes, Status: OK
[88,0] Written, Length: 36 bytes, Status: OK
[96,0] Written, Length: 24 bytes, Status: OK
[107,0] Written, Length: 21 bytes, Status: OK
[107,1] Written, Length: 79 bytes, Status: OK
[107,2] Written, Length: 79 bytes, Status: OK
[107,3] Written, Length: 70 bytes, Status: OK
[107,25] Written, Length: 132 bytes, Status: OK
[117,0] Written, Length: 4 bytes, Status: OK
[117,1] Written, Length: 3 bytes, Status: OK
[117,2] Written, Length: 6 bytes, Status: OK
[117,3] Written, Length: 1 bytes, Status: OK
[117,5] Written, Length: 10 bytes, Status: OK
[117,6] Written, Length: 8 bytes, Status: OK
[117,8] Written, Length: 42 bytes, Status: OK
[117,13] Written, Length: 3 bytes, Status: OK
[117,14] Written, Length: 3 bytes, Status: OK
[117,19] Written, Length: 40 bytes, Status: OK
[120,0] Written, Length: 88 bytes, Status: OK
[120,1] Written, Length: 80 bytes, Status: OK
[120,2] Written, Length: 20 bytes, Status: OK
[120,3] Written, Length: 112 bytes, Status: OK
[193,2] Written, Length: 8 bytes, Status: OK
[193,3] Written, Length: 32 bytes, Status: OK
[193,4] Written, Length: 32 bytes, Status: OK
[193,9] Written, Length: 64 bytes, Status: OK
[208,1] Written, Length: 4 bytes, Status: OK
[217,0] Written, Length: 32 bytes, Status: OK
[309,0] Written, Length: 4 bytes, Status: Not accepted, Code: 19
[309,1] Written, Length: 2 bytes, Status: Not accepted, Code: 19
[309,2] Written, Length: 12 bytes, Status: Not accepted, Code: 19
[309,4] Written, Length: 12 bytes, Status: Not accepted, Code: 19
[309,5] Written, Length: 12 bytes, Status: Not accepted, Code: 19
[309,7] Written, Length: 12 bytes, Status: Not accepted, Code: 19
[309,8] Written, Length: 12 bytes, Status: Not accepted, Code: 19
[309,17] Written, Length: 12 bytes, Status: Not accepted, Code: 19
[322,0] Written, Length: 1 bytes, Status: OK
[354,0] Written, Length: 13 bytes, Status: OK
[356,0] Written, Length: 2 bytes, Status: OK
Write PM Finished, Record written OK: 181, Record written NOT OK: 37

Серты
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1730001978B901584A11D929C0CF1AE792AD304A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC003000000221, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0030 (Samsung), Size: 128MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.12.8.0, Algo: XSR 1.5
Initializing TurboCache...
TurboCache Loaded!
Writing CMT PASUBTOC Certificate...
Writing CMT ALG Certificate...
CMT Algorithm Ready!
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Adding FUR Client (CMT, State: Ready)...
CMT FUR Ready!
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 0FE1BA92D924A658E4800780FA6F4868100AC947
APE Subsystem Not Found
Flashbus Write baud set to 5.0Mbits
CMT NPC Ok
CMT HWC Ok
CMT CCC Ok
CMT R&D Ok
CMT PARTNERC Not Found
CMT VARIANT Not Found
CMT PAPUBKEYS Ok
CMT KEYS Ok
Restarting MCU...
Read all certificates finished

Селв
Selftests to proceed: 31
Passed ST_TAHVOINT_TEST
Passed ST_UEM_CBUS_IF_TEST
Failed ST_EAR_DATA_LOOP_TEST
Passed ST_SIM_CLK_LOOP_TEST
Passed ST_SIM_IO_CTRL_LOOP_TEST
Passed ST_SECURITY_TEST
Passed ST_PWR_KEY_TEST
Passed ST_CURRENT_CONS_TEST
Passed ST_BACKUP_BATT_TEST
Passed ST_SLEEPCLK_FREQ_TEST
Passed ST_HOOKINT_TEST
Passed ST_BTEMP_TEST
Passed ST_EXT_DEVICE_TEST
Passed ST_CDSP_RF_BB_IF_TEST
Passed ST_CDSP_RF_SUPPLY_TEST
Passed ST_CDSP_TX_IQ_TEST
Passed ST_CDSP_TXC_DATA_TEST
Passed ST_CDSP_PWR_DETECTOR_BIAS_TEST
Passed ST_CDSP_RX_PLL_PHASE_LOCK_TEST
Failed ST_CDSP_TX_PLL_PHASE_LOCK_TEST
Passed ST_CDSP_WCDMA_TX_POWER_TEST
Passed ST_CDSP_RX_IQ_LOOP_BACK_TEST
Passed ST_CDSP_GSM_TX_POWER_TEST
Passed ST_KEYBOARD_STUCK_TEST
Passed ST_LPRF_IF_TEST
Passed ST_CAMERA_IF_TEST
Passed ST_SEC_CAMERA_IF_TEST
Passed ST_LPRF_AUDIO_LINES_TEST
Passed ST_MAIN_LCD_IF_TEST
Passed ST_BT_WAKEUP_TEST
Passed ST_RADIO_TEST
Selftests done, Tests total: 31, Tests passed: 29, Tests not passed: 2



Started Phone Security Analysis...
MCU Version V 07.10
MCU Date 15-07-09
Product RM-243 (Nokia 6120 classic)
Manufacturer (c) Nokia
IMEI 359808016439187
Mastercode 2523163761
Reading Security Block...
Security block OK and saved to "RM-243_359808016439187_21.03.2013_190814.SecurityBlock.PM"
Step 1 : Testing SIMLOCK
-- SIMLOCK PROBLEM --

Phone have failed SIMLOCK Test, that means Simlock Area is DAMAGED!
To repair simlock area, Select Unlock method : "RPL CALCULATION",
And then click DIRECT UNLOCK. SL Area will be re-formatted.

-- SIMLOCK PROBLEM --
Step 2 : Testing SECURITY
SECURITY SEFLTEST PASSED OK!
Step 3 : Analyzing Security Block
"1730001978B901584A11D929C0CF1AE792AD304A.C00045B2" Exists, That is good...
Checking SUPERDONGLE...
SUPERDONGLE FOUND AND CHECKSUM OK! PASSED!
Checking SIMLOCK...
SIMLOCK FOUND AND CHECKSUM OK! PASSED!
Checking MCU&DSP TIMESTAMPS...
MCU&DSP TIMESTAMPS FOUND AND CHECKSUM OK! PASSED!
Checking CMLA KEYS...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking ECC KEYS...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking DIV KEYS...
DIV KEYS FOUND AND CHECKSUM OK! PASSED!
Analyze finished!


Это железная проблема yurii-62глянь на лог,некотрых ПО операций не выложил,но по этому логу видно думаю будет,твой RPL залил и PM.
P.S.сто пудово железо!

[yurii-62]

Тяжело судить о ТА. в чужих руках да еще на расстоянии, мултиметр схему и смотрим наличие питание вторичных цепей, ОК, дальше реболлим последовательно флеш затем проц...
Если нет результата все-таки не плохо было-бы проверить на другом программаторе.. ЗЫ. хотя я бы это сделал в первую очередь, UFS не в счёт.. ;)