 |
 |
 |
|
|
|
|||||||
| Nokia Программный и Аппаратный ремонт телефонов Nokia |
 |
|
|
Опции темы | Поиск в этой теме |
29.10.2011, 20:35
|
#1 |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34    |
Nokia N79 пишет Phone start-up failed. Contact the retailer.
Подскажите как можно решить эту проблему?:confused:
|
|
|
|
29.10.2011, 20:39
|
#2 | |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,429
Вес репутации: 10  |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Цитата:
Что бы точно ответить надо посмотреть лог INFO и лог Check Security. Показывайте логи, не стесняйтесь 
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
|
29.10.2011, 20:48
|
#3 |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Лог я считал через USB:All initialized - Ready to work
[Nokia N85 USB Phonet]: Port opened OK! MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356044032081729 Mastercode 2724146425 IMEI Spare 3A65400423807102 IMEI SV 3365400423807112F2000000 PSN KTA567401 Product Code 0565728 Basic Product Code 0561379 PSD 0000000000000000 LPSN 0 WLAN MAC 1886AC866E2C APE SW 32.001 APE Variant 32.00132.001.005.132.001.53.1 APE Test eno_version APE HW 256 APE ADSP 256 RETU 16 TAHVO 22 AHNE 11 HW 6100 RFIC 17141716 DSP astro_ICPR72_09w17 Failed to read info -> Failed to read SP info Started Phone Security Analysis... [Nokia N85 USB Phonet]: Port opened OK! MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356044032081729 Mastercode 2724146425 Reading Security Block... Security block OK and saved to "RM-348_356044032081729_29.10.2011_214436.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 PROBLEM -- Phone have failed SECURITY Test, that means Superdongle Area is DAMAGED! To repair it, simply slick "SX4 Authorization / SD Repair" button. After SX4/SD Repair, don't forget to write PM file with fields 1,309 (if SW don't do this automatically) Additionaly, Checking HWC/CCC Certs... Booting CMT... [Nokia N85 USB Phonet]: Port opened OK! Switching to RAW Mode... [Nokia USB Flashing Generic]: Port opened OK! Old ROM Detected CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 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.11.24.0, Algo: BB5 Using NEW BB5 FLASHING PROTOCOL Prepare phone failed with message -> Failed to set CMT Transmission Mode Analyze Security Error -> Failed to Boot / Prepare Phone |
|
|
|
|
29.10.2011, 20:52
|
#4 | ||||
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,429
Вес репутации: 10 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Нарушена SimLockData = SLD
-- SIMLOCK PROBLEM -- Phone have failed SIMLOCK Test, that means Simlock Area is DAMAGED! Так как N79 это телефон с SL2 типом защиты, то восстановить SLD можно и без заказа RPL. И программа сама вам подсказывает, что для этого надо сделать. Цитата:
Цитата:
Так же нарушена SuperDongleData: -- SECURITY PROBLEM -- Phone have failed SECURITY Test, that means Superdongle Area is DAMAGED! И программа снова вам подсказывает как восстановить SDD. Цитата:
Цитата:
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
||||
|
|
|
|
29.10.2011, 22:02
|
#5 |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Делаю SX4
Вот лог SX4 авторизации:X4 Authorization / SD Repair Procedure Started....
WARNING: "13C00019CD810052751BD2A242C244D8E33DDFE6.C0003A5E" Not Exists, Will read it... Reading CYC file from phone... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! New_RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.16.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. CBUS Request Error -> CBUS Response wrong header Prepare phone failed with message -> Failed to get CMT Configuration Neither CYC file and exists or failed to read it from phone (Failed to Boot / Prepare Phone) Failed to obtain Phone Unique Data, Will use Server and Original Card Failed to disable VBAT -> CBUS reported an error Disconnected from Cyclone Server Failed to Authorize SX4 -> Phone not detected |
|
|
|
|
29.10.2011, 22:06
|
#6 | |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Хотел сделать
Цитата:
Вот лог:Initializing FBUS...
All initialized - Ready to work BB5 Unlock Started... MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356044032081729 Mastercode 2724146425 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-348_356044032081729_29.10.2011_230422.SecurityBlock.PM" WARNING: "13C00019CD810052751BD2A242C244D8E33DDFE6.C0003A5E" Not Exists, Will read it... Reading CYC file from phone... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! New_RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.16.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. CBUS Request Error -> CBUS Response wrong header Prepare phone failed with message -> Failed to get CMT Configuration Neither CYC file and exists or failed to read it from phone (Failed to Boot / Prepare Phone) BB5 Unlock Failed -> Failed to obtain Phone Unique Data |
|
|
|
|
|
29.10.2011, 22:20
|
#7 | |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,429
Вес репутации: 10 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Цитата:
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
|
29.10.2011, 22:30
|
#8 |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
нет вот я так и не понял куда мне подать TX2????????????????? у меня универсал ка.
|
|
|
|
|
29.10.2011, 22:39
|
#9 | |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,429
Вес репутации: 10 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Цитата:
Вот такой v1 Или такой v2 Он у вас есть? Без него Flash режим на большинстве моделей Nokia BB5 не работает.
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
|
29.10.2011, 22:45
|
#10 | |
|
Moderator
Регистрация: 23.02.2011
Адрес: Moldova-Chisinau
Сообщений: 1,975
Вес репутации: 1136 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Цитата:
|
|
|
|
|
|
29.10.2011, 23:10
|
#11 | ||
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Цитата:
Цитата:
|
||
|
|
|
|
29.10.2011, 23:27
|
#12 |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Не получатся у меня сделать SX4 почему
Лог SX4 авторизации и записи PM 1 и 309 полейSX4 Authorization / SD Repair Procedure Started....
"13C00019CD810052751BD2A242C244D8E33DDFE6.C0003A5E" Exists, That is good... MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356044032081729 Mastercode 2724146425 Reading Security Block... Security block OK and saved to "RM-348_356044032081729_30.10.2011_02249.SecurityBlock.PM" SX4 Status: Authorized [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,35] Written, Length: 16 bytes, Status: Not accepted, Code: 19 [1,37] Written, Length: 4 bytes, Status: Not accepted, Code: 19 [1,39] Written, Length: 36 bytes, Status: Not accepted, Code: 19 [1,44] Written, Length: 182 bytes, Status: Not accepted, Code: 19 [1,45] Written, Length: 182 bytes, Status: Not accepted, Code: 19 [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 [309,22] Written, Length: 12 bytes, Status: Not accepted, Code: 19 Write PM Finished, Record written OK: 0, Record written NOT OK: 37 Вот ещё лог:Started Phone Security Analysis...
MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356044032081729 Mastercode 2724146425 Reading Security Block... Security block OK and saved to "RM-348_356044032081729_30.10.2011_02614.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 PROBLEM -- Phone have failed SECURITY Test, that means Superdongle Area is DAMAGED! To repair it, simply slick "SX4 Authorization / SD Repair" button. After SX4/SD Repair, don't forget to write PM file with fields 1,309 (if SW don't do this automatically) Additionaly, Checking HWC/CCC Certs... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 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.11.24.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]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.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: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits HWC Looks OK! CCC Looks OK! Restarting MCU... -- SECURITY PROBLEM -- Step 3 : Analyzing Security Block "13C00019CD810052751BD2A242C244D8E33DDFE6.C0003A5E" 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... ECC KEYS FOUND AND CHECKSUM OK! PASSED! Checking DIV KEYS... DIV KEYS FOUND AND CHECKSUM OK! PASSED! Analyze finished! |
|
|
|
|
30.10.2011, 00:22
|
#13 |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,429
Вес репутации: 10 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
PM для N79-1_RM-348_UO5OQ_com_PM из файлового архива нашего сервера я перезалил.
По логу SX4 авторизации и записи PM всё в порядке. И лог анализа Security уже тоже в норме. Разве телефон ещё не заработал нормально?
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
30.10.2011, 00:32
|
#14 | |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Цитата:
А когда вы перелазили? что интересно я сливаю родной PM стираю оттуда все копирую всю ифу с вашего PM и сохраняю на родном PM потом делаю SX4 и вливаю родной PM все пишет ОК... а с вашим только одни ошибки может что я неправильно делаю)))) а телефон так и не заработал)))) |
|
|
|
|
|
30.10.2011, 00:39
|
#15 |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,429
Вес репутации: 10 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Только что перезалил.
Вот нормальный PM с 1 и 309 полями.
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
30.10.2011, 01:04
|
#16 |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Влил PM все супер прошло но телефон что то перезагружается.
Включился но все равно пишет Phone start-up failed. Contact the retailer. |
|
|
|
|
30.10.2011, 01:28
|
#17 |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,429
Вес репутации: 10 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Пришло время выслушать предисторию поломки этого телефона
И покажите как сейчас выглядит лог анализа Security.
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
30.10.2011, 01:34
|
#18 |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Принесли телефон якобы они пытались обновится по словам клиента....
Вот лог "Analyze Security":Initializing FBUS...
All initialized - Ready to work MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356044032081729 Mastercode 2724146425 IMEI Spare 3A65400423807102 IMEI SV 3365400423807112F2000000 CNT V 53.32.2009.43.xx PRD PSN CXB394573 Product Code 0565724 Basic Product Code 0561379 PSD 0000000000000000 LPSN 0 WLAN MAC 1886AC866E2C APE SW 32.001 APE Variant 32.00132.001.005.132.001.53.1 APE Test eno_version APE HW 256 APE ADSP 256 RETU 16 TAHVO 22 AHNE 11 HW 6000 RFIC 17141716 DSP astro_ICPR72_09w17 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 Auto Selecting Flash Files on User Request... Product Code: 0565724 Scanning avaiable products... Processing C:\Program Files\Nokia\Phoenix\Products\... Found 41 products, Filtering DCT4 Products - wait... 0 Products left after filtering. Ready. This is Valid BB5 Product Variant found for readen Product Data! Started Phone Security Analysis... MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356044032081729 Mastercode 2724146425 Reading Security Block... Security block OK and saved to "RM-348_356044032081729_30.10.2011_23133.SecurityBlock.PM" Step 1 : Testing SIMLOCK SIMLOCK SEFLTEST PASSED OK! Step 2 : Testing SECURITY -- SECURITY PROBLEM -- Phone have failed SECURITY Test, that means Superdongle Area is DAMAGED! To repair it, simply slick "SX4 Authorization / SD Repair" button. After SX4/SD Repair, don't forget to write PM file with fields 1,309 (if SW don't do this automatically) Additionaly, Checking HWC/CCC Certs... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 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.11.24.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]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.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: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits HWC Looks OK! CCC Looks OK! Restarting MCU... -- SECURITY PROBLEM -- Step 3 : Analyzing Security Block "13C00019CD810052751BD2A242C244D8E33DDFE6.C0003A5E" 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... ECC KEYS FOUND AND CHECKSUM OK! PASSED! Checking DIV KEYS... DIV KEYS FOUND AND CHECKSUM OK! PASSED! Analyze finished! |
|
|
|
|
30.10.2011, 01:37
|
#19 |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Вот только что сделал SX4 и влил PM с 1 и 309 полем
Вот лог операции:SX4 Authorization / SD Repair Procedure Started....
"13C00019CD810052751BD2A242C244D8E33DDFE6.C0003A5E" Exists, That is good... MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356044032081729 Mastercode 2724146425 Reading Security Block... Security block OK and saved to "RM-348_356044032081729_30.10.2011_23550.SecurityBlock.PM" SX4 Status: Authorized [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,35] Written, Length: 16 bytes, Status: OK [1,37] Written, Length: 4 bytes, Status: OK [1,39] Written, Length: 36 bytes, Status: OK [1,44] Written, Length: 182 bytes, Status: OK [1,45] Written, Length: 182 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 [309,22] Written, Length: 12 bytes, Status: OK Write PM Finished, Record written OK: 37, Record written NOT OK: 0 Все равно Phone start-up failed. Contact the retailer. 
|
|
|
|
|
30.10.2011, 01:46
|
#20 |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,429
Вес репутации: 10 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Та-а-к...
1. Запишите файл N79_HWC+CCC_UO5OQ_com как RPL после 2. Сделайте заново SX4 и запись PM
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
30.10.2011, 02:01
|
#21 |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
все сделал как вы сказали но ничего не помогло
|
|
|
|
|
30.10.2011, 20:40
|
#22 | |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Цитата:
|
|
|
|
|
|
30.10.2011, 20:51
|
#23 | |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,429
Вес репутации: 10 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Цитата:
Для этого сначала ОЧЕНЬ ВНИМАТЕЛЬНО забэкапьте сертификаты (RPL) и Full PM 1-512 поля. Когда забэкапите, сложите все бэкапы в архив и прикрепите к теме. Я сначала проверю их перед дальнейшими действиями.
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
|
30.10.2011, 21:37
|
#24 | |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Цитата:
вот лог:Initializing FBUS...
All initialized - Ready to work Failed to read info -> Phone not detected Failed to read info -> Phone not detected MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356044032081729 Mastercode 2724146425 IMEI Spare 3A65400423807102 IMEI SV 3365400423807112F2000000 CNT V 53.32.2009.43.xx PRD PSN CXB394573 Product Code 0565724 Basic Product Code 0561379 PSD 0000000000000000 LPSN 0 WLAN MAC 1886AC866E2C APE SW 32.001 APE Variant 32.00132.001.005.132.001.53.1 APE Test eno_version APE HW 256 APE ADSP 256 RETU 16 TAHVO 22 AHNE 11 HW 6000 RFIC 17141716 DSP astro_ICPR72_09w17 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 Auto Selecting Flash Files on User Request... Product Code: 0565724 This is Valid BB5 Product Variant found for readen Product Data! Started Phone Security Analysis... MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356044032081729 Mastercode 2724146425 Reading Security Block... Security block OK and saved to "RM-348_356044032081729_30.10.2011_233528.SecurityBlock.PM" Step 1 : Testing SIMLOCK SIMLOCK SEFLTEST PASSED OK! Step 2 : Testing SECURITY -- SECURITY PROBLEM -- Phone have failed SECURITY Test, that means Superdongle Area is DAMAGED! To repair it, simply slick "SX4 Authorization / SD Repair" button. After SX4/SD Repair, don't forget to write PM file with fields 1,309 (if SW don't do this automatically) Additionaly, Checking HWC/CCC Certs... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 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.11.24.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]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.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: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits HWC Looks OK! CCC Looks OK! Restarting MCU... -- SECURITY PROBLEM -- Step 3 : Analyzing Security Block "13C00019CD810052751BD2A242C244D8E33DDFE6.C0003A5E" 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... ECC KEYS FOUND AND CHECKSUM OK! PASSED! Checking DIV KEYS... DIV KEYS FOUND AND CHECKSUM OK! PASSED! Analyze finished! |
|
|
|
|
|
30.10.2011, 22:05
|
#25 |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
вот они файлики
|
|
|
|
|
31.10.2011, 09:10
|
#26 | |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,429
Вес репутации: 10 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Цитата:
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
|
31.10.2011, 09:31
|
#27 | |
|
Moderator
Регистрация: 23.02.2011
Адрес: Moldova-Chisinau
Сообщений: 1,975
Вес репутации: 1136 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Цитата:
|
|
|
|
|
|
31.10.2011, 09:33
|
#28 |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
по моему получилось
|
|
|
|
|
31.10.2011, 09:53
|
#29 |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,429
Вес репутации: 10 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Да, все критически важные DATA забэкаплены.
Теперь сотрите телефон Cyclone Box - Full Erase. Затем запишите только SW и больше ничего. Покажите лог чтения INFO и Analyse Security и опишите состояние телефона (включается ли полностью в таком виде с IMEI 123456....).
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
31.10.2011, 10:29
|
#30 | |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Цитата:
Вот лог:Initializing FBUS...
All initialized - Ready to work MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 12345610654321? IMEI Spare 1A32541660452301 IMEI SV 1332541660452311F2000000 PSN 0 PSD 0000000000000000 LPSN 0 APE SW 32.001 APE Variant 32.001 APE HW 256 APE ADSP 256 APE BT HCI Version 12 (rev. 8192). LMP Version 12 (rev. 0). Manufacturer 12708. RETU 16 TAHVO 22 AHNE 11 RFIC 17141716 DSP astro_ICPR72_09w17 Failed to read info -> Failed to read SP info Started Phone Security Analysis... MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 12345610654321? Reading Security Block... Read Security Block Problem -> Failed to read PM 308, this is critical Analyze Security Error -> Failed to read Security Block |
|
|
|
|
|
31.10.2011, 10:42
|
#31 | ||
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,429
Вес репутации: 10 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Цитата:
Цитата:
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
||
|
|
|
|
31.10.2011, 10:47
|
#32 | |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Цитата:
|
|
|
|
|
|
31.10.2011, 11:01
|
#33 | |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,429
Вес репутации: 10 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Цитата:
Запишите в него ТОЛЬКО SW ещё раз по INI (программа-флэшер сама расставляет файлы прошивки по местам), и покажите лог записи SW. SW должно быть из полного Nokia SW Installer, НЕ кусочки SW найденые в сети.
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
|
31.10.2011, 11:11
|
#34 | |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Цитата:
|
|
|
|
|
|
31.10.2011, 11:14
|
#35 | |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,429
Вес репутации: 10 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Цитата:
Если так есть, то это означает что железо на 99% в порядке Идём дальше. 1.) Запишите бэкап вашего RPL RM-348_35604403208172930.10.2011_235950 2.) Сделайте SX4 авторизацию и запишите PM 1 и 309 поля предлагаемый Cyclone Box, или вот этот PM N79-1_RM-348_PM После этого телефон должен полностью восстановиться.
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
|
31.10.2011, 11:50
|
#36 | |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Цитата:
Скрытый текстInitializing FBUS...
All initialized - Ready to work Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 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.11.24.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]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.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: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits Erasing flash chip... Started group flash erase EraseArea[0,CMT]: 0x00000000-0x0FFFFFFF, ONENAND Waiting 640s for erasure finish... Erase taken 1.328s Restarting MCU... BB5 Full Erase Finished! Processing pre flash tasks... Pre flash tasks finished, continuing... Processing RM-348_32.001_prd.core.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-348_32.001_prd.core.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.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]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.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-0x003FFFFF, ONENAND EraseArea[0,CMT]: 0x00800000-0x00D5FFFF, ONENAND EraseArea[0,CMT]: 0x00D60000-0x0A95FFFF, ONENAND Erase Partition (CMT) Waiting 320s for erasure finish... Erase taken 0.969s 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+ROFS1 Certificate... Programming Status OK! All blocks written OK! Time taken 119.62s Flashing Speed: 7296,75 kBit/S Restarting MCU... Processing RM-348_32.001_prd.core.fpsx (APE)... Processing RM-348_32.001_005_prd.language.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-348_32.001_005_prd.language.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.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]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.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: B2075F4B793BB9017C8C0097C783C543F2A6A303 Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x08260000-0x09F5FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.188s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS+ROFS2 Certificate... Programming Status OK! All blocks written OK! Time taken 27.844s Flashing Speed: 7247,36 kBit/S Restarting MCU... Processing RM-348_32.001_005_prd.language.fpsx (APE)... Processing RM-348_32.001_53.1_prd.customer.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-348_32.001_53.1_prd.customer.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.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]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.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: B2075F4B793BB9017C8C0097C783C543F2A6A303 Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x09F60000-0x0A95FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.94s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS+ROFS3 Certificate... Programming Status OK! All blocks written OK! Time taken 0.94s Flashing Speed: 693,96 kBit/S Restarting MCU... Processing RM-348_32.001_53.1_prd.customer.fpsx (APE)... Processing RM-348_32.001_003_000_U001.uda.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-348_32.001_003_000_U001.uda.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.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]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.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: B2075F4B793BB9017C8C0097C783C543F2A6A303 Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x0A960000-0x0F71FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.438s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Programming Status OK! All blocks written OK! Time taken 19.281s Flashing Speed: 6951,55 kBit/S Restarting MCU... Processing RM-348_32.001_003_000_U001.uda.fpsx (APE)... Processing vivien_eno_imaker_ape_only.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! vivien_eno_imaker_ape_only.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.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]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.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: B2075F4B793BB9017C8C0097C783C543F2A6A303 Flashbus Write baud set to 5.0Mbits Sending Certificates... Certificates OK Started group flash erase EraseArea[0,CMT]: 0x00400000-0x007FFFFF, 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 3.156s Flashing Speed: 6881,70 kBit/S Restarting MCU... Processing vivien_eno_imaker_ape_only.fpsx (APE)... All images processed OK! Processing post flash tasks... Setting Factory Defaults... Factory defaults OK Reading info... MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 12345610654321? IMEI Spare 1A32541660452301 IMEI SV 1332541660452311F2000000 PSN 0 PSD 0000000000000000 LPSN 0 RETU 16 TAHVO 22 AHNE 11 RFIC 17141716 DSP astro_ICPR72_09w17 Failed to read info -> Failed to read SP info Read info thread finished, continuing... Post flash tasks finished! Flashing successfully finished! Skipping RPL decryption... Parsing decrypted RPL... Processing FBUS Part... Writing Product Code... Writing PSN... Writing HWID... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock NOT ACCEPTED ! Writing Superdongle key... Superdongle Key ACCEPTED OK ! Writing WMDRM PD Data... WMDRM PD Data ACCEPTED OK ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 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.11.24.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]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.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: B2075F4B793BB9017C8C0097C783C543F2A6A303 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 Product Code... Writing PSN... Writing HWID... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock ACCEPTED OK ! Writing Superdongle key... Superdongle Key ACCEPTED OK ! Writing WMDRM PD Data... WMDRM PD Data ACCEPTED OK ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 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.11.24.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]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.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: B2075F4B793BB9017C8C0097C783C543F2A6A303 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! SX4 Authorization / SD Repair Procedure Started.... "13C00019CD810052751BD2A242C244D8E33DDFE6.C0003A5E" Exists, That is good... MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356044032081729 Mastercode 2724146425 Reading Security Block... Security block OK and saved to "RM-348_356044032081729_31.10.2011_134604.SecurityBlock.PM" SX4 Status: Not authorized (74) 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... Virgin PM Not found in local database, obtain one (with fields 1 and 309) and write it using "Write PM" Button SX4 Authorization / SD Repair Procedure Started.... "13C00019CD810052751BD2A242C244D8E33DDFE6.C0003A5E" Exists, That is good... MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356044032081729 Mastercode 2724146425 Reading Security Block... Security block OK and saved to "RM-348_356044032081729_31.10.2011_134607.SecurityBlock.PM" SX4 Status: Authorized [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,35] Written, Length: 16 bytes, Status: Not accepted, Code: 19 [1,37] Written, Length: 4 bytes, Status: Not accepted, Code: 19 [1,39] Written, Length: 36 bytes, Status: Not accepted, Code: 19 [1,44] Written, Length: 182 bytes, Status: Not accepted, Code: 19 [1,45] Written, Length: 182 bytes, Status: Not accepted, Code: 19 [2,0] Written, Length: 448 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 [8,0] Written, Length: 2 bytes, Status: OK [8,1] Written, Length: 16 bytes, Status: OK [8,2] Written, Length: 16 bytes, Status: OK [8,3] Written, Length: 128 bytes, Status: OK [8,4] Written, Length: 128 bytes, Status: OK [8,7] Written, Length: 4 bytes, Status: OK [8,8] Written, Length: 8 bytes, Status: OK [8,9] Written, Length: 8 bytes, Status: OK [8,10] Written, Length: 24 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: 2 bytes, Status: OK [11,5] Written, Length: 1 bytes, Status: OK [12,0] Written, Length: 102 bytes, Status: OK [31,4] Written, Length: 14 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 [96,0] Written, Length: 2 bytes, Status: OK [96,1] Written, Length: 20 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,24] Written, Length: 596 bytes, Status: OK [107,25] Written, Length: 132 bytes, Status: OK [107,26] Written, Length: 12 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 [122,0] Written, Length: 2 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 [291,0] Written, Length: 92 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 [309,22] Written, Length: 12 bytes, Status: Not accepted, Code: 19 [313,0] Written, Length: 173 bytes, Status: OK [322,0] Written, Length: 1 bytes, Status: OK [329,0] Written, Length: 8392 bytes, Status: OK [334,0] Written, Length: 1 bytes, Status: OK [341,0] Written, Length: 1 bytes, Status: OK [341,3] Written, Length: 4 bytes, Status: OK [341,4] Written, Length: 4524 bytes, Status: OK [354,0] Written, Length: 20 bytes, Status: OK [356,0] Written, Length: 2 bytes, Status: OK [356,1] Written, Length: 8 bytes, Status: OK Write PM Finished, Record written OK: 55, Record written NOT OK: 37 SX4 Authorization / SD Repair Procedure Started.... "13C00019CD810052751BD2A242C244D8E33DDFE6.C0003A5E" Exists, That is good... MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356044032081729 Mastercode 2724146425 Reading Security Block... Security block OK and saved to "RM-348_356044032081729_31.10.2011_134626.SecurityBlock.PM" SX4 Status: Not authorized (74) 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... Virgin PM Not found in local database, obtain one (with fields 1 and 309) and write it using "Write PM" Button SX4 Authorization / SD Repair Procedure Started.... "13C00019CD810052751BD2A242C244D8E33DDFE6.C0003A5E" Exists, That is good... MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356044032081729 Mastercode 2724146425 Reading Security Block... Security block OK and saved to "RM-348_356044032081729_31.10.2011_134630.SecurityBlock.PM" SX4 Status: Authorized [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,35] Written, Length: 16 bytes, Status: OK [1,37] Written, Length: 4 bytes, Status: OK [1,39] Written, Length: 36 bytes, Status: OK [1,44] Written, Length: 182 bytes, Status: OK [1,45] Written, Length: 182 bytes, Status: OK [2,0] Written, Length: 448 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 [8,0] Written, Length: 2 bytes, Status: OK [8,1] Written, Length: 16 bytes, Status: OK [8,2] Written, Length: 16 bytes, Status: OK [8,3] Written, Length: 128 bytes, Status: OK [8,4] Written, Length: 128 bytes, Status: OK [8,7] Written, Length: 4 bytes, Status: OK [8,8] Written, Length: 8 bytes, Status: OK [8,9] Written, Length: 8 bytes, Status: OK [8,10] Written, Length: 24 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: 2 bytes, Status: OK [11,5] Written, Length: 1 bytes, Status: OK [12,0] Written, Length: 102 bytes, Status: OK [31,4] Written, Length: 14 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 [96,0] Written, Length: 2 bytes, Status: OK [96,1] Written, Length: 20 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,24] Written, Length: 596 bytes, Status: OK [107,25] Written, Length: 132 bytes, Status: OK [107,26] Written, Length: 12 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 [122,0] Written, Length: 2 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 [291,0] Written, Length: 92 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 [309,22] Written, Length: 12 bytes, Status: OK [313,0] Written, Length: 173 bytes, Status: OK [322,0] Written, Length: 1 bytes, Status: OK [329,0] Written, Length: 8392 bytes, Status: OK [334,0] Written, Length: 1 bytes, Status: OK [341,0] Written, Length: 1 bytes, Status: OK [341,3] Written, Length: 4 bytes, Status: OK [341,4] Written, Length: 4524 bytes, Status: OK [354,0] Written, Length: 20 bytes, Status: OK [356,0] Written, Length: 2 bytes, Status: OK [356,1] Written, Length: 8 bytes, Status: OK Write PM Finished, Record written OK: 92, Record written NOT OK: 0 MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356044032081729 Mastercode 2724146425 IMEI Spare 3A65400423807102 IMEI SV 3365400423807112F2000000 CNT V 53.32.2009.43.xx PRD PSN KTA567401 Product Code 0565728 Basic Product Code 0561379 PSD 0000000000000000 LPSN 0 WLAN MAC 1886AC866E2C APE SW 32.001 APE Variant 32.00132.001.005.132.001.53.1 APE Test eno_version APE HW 256 APE ADSP 256 RETU 16 TAHVO 22 AHNE 11 HW 6100 RFIC 17141716 DSP astro_ICPR72_09w17 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 Started Phone Security Analysis... MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356044032081729 Mastercode 2724146425 Reading Security Block... Security block OK and saved to "RM-348_356044032081729_31.10.2011_134704.SecurityBlock.PM" Step 1 : Testing SIMLOCK SIMLOCK SEFLTEST PASSED OK! Step 2 : Testing SECURITY -- SECURITY PROBLEM -- Phone have failed SECURITY Test, that means Superdongle Area is DAMAGED! To repair it, simply slick "SX4 Authorization / SD Repair" button. After SX4/SD Repair, don't forget to write PM file with fields 1,309 (if SW don't do this automatically) Additionaly, Checking HWC/CCC Certs... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 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.11.24.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]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.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: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits HWC Looks OK! CCC Looks OK! Restarting MCU... -- SECURITY PROBLEM -- Step 3 : Analyzing Security Block "13C00019CD810052751BD2A242C244D8E33DDFE6.C0003A5E" 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... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Analyze finished! :confused: Последний раз редактировалось se13; 31.10.2011 в 12:25. |
|
|
|
|
|
31.10.2011, 12:51
|
#37 | |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,429
Вес репутации: 10 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Давайте заново, вот отсюда:
Цитата:
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
|
31.10.2011, 23:33
|
#38 | |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Цитата:
Cyclone выставляет по ini 5 файлов? мне прошить MCU? |
|
|
|
|
|
31.10.2011, 23:36
|
#39 | ||
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,429
Вес репутации: 10 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Цитата:
Полная прошивка SW (все файлы). Все которые Cyclone выставляет по INI (и вообще всегда именно так, по INI шейте Nokia). Цитата:
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
||
|
|
|
|
31.10.2011, 23:55
|
#40 |
|
Senior Member
Регистрация: 25.10.2011
Сообщений: 167
Вес репутации: 34 |
Re: Nokia N79 пишет Phone start-up failed. Contact the retailer.
Вот сделал полное стирание и прошил
вот логи:Initializing FBUS...
All initialized - Ready to work Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 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.11.24.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]: 0xFFFFFFFF00000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.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! APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits Erasing flash chip... Started group flash erase EraseArea[0,CMT]: 0x00000000-0x0FFFFFFF, ONENAND Waiting 640s for erasure finish... Erase taken 1.312s Restarting MCU... BB5 Full Erase Finished! Processing pre flash tasks... Backing up RPL... RPL Creation started... Processing CMT Part... Proceeding with Recovery Mode... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 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.11.24.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]: 0xFFFFFFFF00000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.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! APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits NPC Backup stored in "13C00019CD810052751BD2A242C244D8E33DDFE6_01.11.2011_14531.NPC.CMT.crt" Recovery Mode Failed, storing Certificates Only Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 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.11.24.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]: 0xFFFFFFFF00000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.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! APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits Failed to Create RPL from phone -> No target file chosen RPL backup thread finished, continuing... Backing up simlock... Simlock backup problem -> Phone not detected Backup simlock thread finished, continuing... Pre flash tasks finished, continuing... Processing RM-348_32.001_prd.core.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-348_32.001_prd.core.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.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]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.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-0x003FFFFF, ONENAND EraseArea[0,CMT]: 0x00800000-0x00D5FFFF, ONENAND EraseArea[0,CMT]: 0x00D60000-0x0A95FFFF, ONENAND Erase Partition (CMT) Waiting 320s for erasure finish... Erase taken 1.125s 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+ROFS1 Certificate... Programming Status OK! All blocks written OK! Time taken 120.719s Flashing Speed: 7196,59 kBit/S Restarting MCU... Processing RM-348_32.001_prd.core.fpsx (APE)... Processing RM-348_32.001_005_prd.language.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-348_32.001_005_prd.language.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.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]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.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: B2075F4B793BB9017C8C0097C783C543F2A6A303 Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x08260000-0x09F5FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.172s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS+ROFS2 Certificate... Programming Status OK! All blocks written OK! Time taken 28.78s Flashing Speed: 7186,96 kBit/S Restarting MCU... Processing RM-348_32.001_005_prd.language.fpsx (APE)... Processing RM-348_32.001_53.1_prd.customer.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-348_32.001_53.1_prd.customer.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.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]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.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: B2075F4B793BB9017C8C0097C783C543F2A6A303 Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x09F60000-0x0A95FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.93s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS+ROFS3 Certificate... Programming Status OK! All blocks written OK! Time taken 0.110s Flashing Speed: 593,02 kBit/S Restarting MCU... Processing RM-348_32.001_53.1_prd.customer.fpsx (APE)... Processing RM-348_32.001_003_000_U001.uda.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-348_32.001_003_000_U001.uda.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.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]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.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: B2075F4B793BB9017C8C0097C783C543F2A6A303 Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x0A960000-0x0F71FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.421s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Programming Status OK! All blocks written OK! Time taken 19.797s Flashing Speed: 6770,36 kBit/S Restarting MCU... Processing RM-348_32.001_003_000_U001.uda.fpsx (APE)... Processing vivien_eno_imaker_ape_only.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 13C00019CD810052751BD2A242C244D8E33DDFE6 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! vivien_eno_imaker_ape_only.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.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]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.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: B2075F4B793BB9017C8C0097C783C543F2A6A303 Flashbus Write baud set to 5.0Mbits Sending Certificates... Certificates OK Started group flash erase EraseArea[0,CMT]: 0x00400000-0x007FFFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.46s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS*ENO Certificate... Programming Status OK! All blocks written OK! Time taken 3.125s Flashing Speed: 6949,97 kBit/S Restarting MCU... Processing vivien_eno_imaker_ape_only.fpsx (APE)... All images processed OK! Processing post flash tasks... Setting Factory Defaults... Factory defaults OK Reading info... MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 12345610654321? IMEI Spare 1A32541660452301 IMEI SV 1332541660452311F2000000 PSN 0 PSD 0000000000000000 LPSN 0 RETU 16 TAHVO 22 AHNE 11 RFIC 17141716 DSP astro_ICPR72_09w17 Failed to read info -> Failed to read SP info Read info thread finished, continuing... Post flash tasks finished! Flashing successfully finished! Телефон включился все нормально)))) но IMEI 12345678ххххх? |
|
|
|
