datiko1
29.07.2013, 15:24
2700с rm-561 вклучалса писал нокиа ибелии дисплеи маленкими красними
палосками и виклучалса прашил сиклоном тело вафше перестал вклучатса
вот лог чек и прашивки сиклоном
Establishing Connection with Box in Main Mode...
Handling device: [Cyclone Team], [Cyclone Box], [Platform: Classic]
Initializing box...
Box Firmware: Cyclone Main Application v02.11, (Nov 10 2012 00:51:46, gcc v4.3.3, RTOS V6.0.1), Type: Signed Production Application, (C) KarwosSoft 2012
Hardware Platform: Cyclone Classic Flasher Interface (c) 2008,2009 KarwosLabs
Box Serial Number: C000097A
HW Revision: A, Suitable for: Production, Case: First Plastic Case, MCU Manufacture Time: 2008, wk27
Initializing security card...
Card Serial Number: D20004D1
Card Firmware Revision: 0109
Card is activated
Box is activated
Started box selftests procedure
USB Voltage 5,00v PASSED
MCU Voltage 3,30v PASSED
Core Voltage 1,80v PASSED
VBAT Voltage 0,01v PASSED
VBAT Voltage 4,78v PASSED
Box VPP disabled
VPP Voltage 0,04v PASSED
Internal Box VPP Enabled
VPP Voltage 4,79v PASSED
Box VPP disabled
VPP Voltage 0,00v PASSED
External Box VPP Enabled
VPP Voltage 0,00v FAILED - IGNORED - Probably power supply is not connected
Box VPP disabled
All box selftests passed!
Super DCT4 Activation: TRUE
XGold/Blackberry Service Running, Counter: 95
Avaiable Physical Memory: 1.1023GB
Avaiable Virtual Memory: 1.901GB
Avaiable Pagefile: 3.1023GB
Initializing FBUS...
All initialized - Ready to work
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006030C192101033000
CMT_EM_ASIC_ID: 00000296
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 15800111A84C0056D29B6559F2A1A61249834B05
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
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]: 0x00EC240000008A31, Samsung, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC2400 (Samsung), Size: 64MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 3EA22A1DDA660002E56108DB5072A10F8709443F
APE Boot skipped on user request
Flashbus Write baud set to 5.0Mbits
Restarting MCU...
Box VPP disabled
All box selftests passed!
Super DCT4 Activation: TRUE
XGold/Blackberry Service Running, Counter: 95
Avaiable Physical Memory: 1.1023GB
Avaiable Virtual Memory: 1.901GB
Avaiable Pagefile: 3.1023GB
Initializing FBUS...
All initialized - Ready to work
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006030C192101033000
CMT_EM_ASIC_ID: 00000296
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 15800111A84C0056D29B6559F2A1A61249834B05
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
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]: 0x00EC240000008A31, Samsung, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC2400 (Samsung), Size: 64MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 3EA22A1DDA660002E56108DB5072A10F8709443F
APE Boot skipped on user request
Flashbus Write baud set to 5.0Mbits
Restarting MCU...
Retrieving Variants for Product RM-561 - wait...
Failed to retrieve BB5 Variants -> Unexpected error, no VPL or neither INI files found inside Product Directory
Processing pre flash tasks...
Pre flash tasks finished, continuing...
Processing rm561__09.98.mcusw (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006030C192101033000
CMT_EM_ASIC_ID: 00000296
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 15800111A84C0056D29B6559F2A1A61249834B05
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
rm561__09.98.mcusw, Type: Flash Image, Algo: BB5, BB5 ALGORITHM
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
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]: 0x00EC240000008A31, Samsung, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC2400 (Samsung), Size: 64MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 3EA22A1DDA660002E56108DB5072A10F8709443F
Flashbus Write baud set to 5.0Mbits
Sending Certificates...
Certificates OK
Started group flash erase
EraseArea[0,CMT]: 0x00000000-0x000006BF, NOR
EraseArea[0,CMT]: 0x000006C0-0x0001FFFF, NOR
EraseArea[0,CMT]: 0x00040000-0x000BFFFF, NOR
EraseArea[0,CMT]: 0x000C0000-0x0013FFFF, NOR
EraseArea[0,CMT]: 0x00140000-0x0137FFFF, NOR
EraseArea[0,CMT]: 0x01380000-0x0151FFFF, NOR
Waiting 320s for erasure finish...
Erase taken 77.890s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT NOLO Certificate...
Writing CMT KEYS Certificate...
Writing CMT PRIMAPP Certificate...
Writing CMT PASUBTOC Certificate...
Block Write Failed -> Failed to write CMT cert data (3), Programming Status Error
Processing Flash Image Failed -> Failed to write all blocks
Failed to Process all Image files -> Failed to process rm561__09.98.mcusw
Processing pre flash tasks...
Pre flash tasks finished, continuing...
Processing rm561__09.98.mcusw (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006030C192101033000
CMT_EM_ASIC_ID: 00000296
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 15800111A84C0056D29B6559F2A1A61249834B05
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
rm561__09.98.mcusw, Type: Flash Image, Algo: BB5, BB5 ALGORITHM
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
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]: 0x00EC240000008A31, Samsung, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC2400 (Samsung), Size: 64MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
Warning: PAPUBKEYS Hash Missing!
Flashbus Write baud set to 5.0Mbits
Sending Certificates...
Certificates OK
Started group flash erase
EraseArea[0,CMT]: 0x00000000-0x000006BF, NOR
EraseArea[0,CMT]: 0x000006C0-0x0001FFFF, NOR
EraseArea[0,CMT]: 0x00040000-0x000BFFFF, NOR
EraseArea[0,CMT]: 0x000C0000-0x0013FFFF, NOR
EraseArea[0,CMT]: 0x00140000-0x0137FFFF, NOR
EraseArea[0,CMT]: 0x01380000-0x0151FFFF, NOR
Waiting 320s for erasure finish...
Erase taken 5.890s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT NOLO Certificate...
Writing CMT KEYS Certificate...
Writing CMT PRIMAPP Certificate...
Writing CMT PASUBTOC Certificate...
WARNING: CMT PAPUBKEYS Hash is Empty, writing first found PAPUBKEYS
Writing CMT PAPUBKEYS Certificate...
Writing CMT UPDAPP Certificate...
Writing CMT DSP0 Certificate...
Writing CMT MCUSW Certificate...
Programming Status OK!
All blocks written OK! Time taken 66.797s
Flashing Speed: 2437,28 kBit/S
Restarting MCU...
Processing rm561__09.98.mcusw (APE)...
Processing rm561__09.98.ppm_t (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006030C192101033000
CMT_EM_ASIC_ID: 00000296
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 15800111A84C0056D29B6559F2A1A61249834B05
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
rm561__09.98.ppm_t, Type: Flash Image, Algo: BB5, BB5 ALGORITHM
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
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]: 0x00EC240000008A31, Samsung, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC2400 (Samsung), Size: 64MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 3EA22A1DDA660002E56108DB5072A10F8709443F
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x01520000-0x01DBFFFF, NOR
Waiting 320s for erasure finish...
Erase taken 25.766s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Programming Status OK!
All blocks written OK! Time taken 23.172s
Flashing Speed: 2395,44 kBit/S
Restarting MCU...
Processing rm561__09.98.ppm_t (APE)...
Processing rm561__09.98.image_ctv_nz_gray (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006030C192101033000
CMT_EM_ASIC_ID: 00000296
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 15800111A84C0056D29B6559F2A1A61249834B05
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
rm561__09.98.image_ctv_nz_gray, Type: Flash Image, Algo: BB5, BB5 ALGORITHM
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
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]: 0x00EC240000008A31, Samsung, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC2400 (Samsung), Size: 64MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 3EA22A1DDA660002E56108DB5072A10F8709443F
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x01DC0000-0x0215FFFF, NOR
EraseArea[0,CMT]: 0x02160000-0x03FBFFFF, NOR
Waiting 320s for erasure finish...
Erase taken 50.31s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Programming Status OK!
All blocks written OK! Time taken 36.188s
Flashing Speed: 2523,86 kBit/S
Restarting MCU...
Processing rm561__09.98.image_ctv_nz_gray (APE)...
All images processed OK! Processing post flash tasks...
Setting Factory Defaults...
на шилдике написанно 2700с-2 rm-561
может ест 2700с с другим rm и вписал там rm-561 тело вафше перестало вклучатса даже вибро нет
до прашивки сделал бекапи и сделал full errase и потом прашивка всеравно труп
палосками и виклучалса прашил сиклоном тело вафше перестал вклучатса
вот лог чек и прашивки сиклоном
Establishing Connection with Box in Main Mode...
Handling device: [Cyclone Team], [Cyclone Box], [Platform: Classic]
Initializing box...
Box Firmware: Cyclone Main Application v02.11, (Nov 10 2012 00:51:46, gcc v4.3.3, RTOS V6.0.1), Type: Signed Production Application, (C) KarwosSoft 2012
Hardware Platform: Cyclone Classic Flasher Interface (c) 2008,2009 KarwosLabs
Box Serial Number: C000097A
HW Revision: A, Suitable for: Production, Case: First Plastic Case, MCU Manufacture Time: 2008, wk27
Initializing security card...
Card Serial Number: D20004D1
Card Firmware Revision: 0109
Card is activated
Box is activated
Started box selftests procedure
USB Voltage 5,00v PASSED
MCU Voltage 3,30v PASSED
Core Voltage 1,80v PASSED
VBAT Voltage 0,01v PASSED
VBAT Voltage 4,78v PASSED
Box VPP disabled
VPP Voltage 0,04v PASSED
Internal Box VPP Enabled
VPP Voltage 4,79v PASSED
Box VPP disabled
VPP Voltage 0,00v PASSED
External Box VPP Enabled
VPP Voltage 0,00v FAILED - IGNORED - Probably power supply is not connected
Box VPP disabled
All box selftests passed!
Super DCT4 Activation: TRUE
XGold/Blackberry Service Running, Counter: 95
Avaiable Physical Memory: 1.1023GB
Avaiable Virtual Memory: 1.901GB
Avaiable Pagefile: 3.1023GB
Initializing FBUS...
All initialized - Ready to work
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006030C192101033000
CMT_EM_ASIC_ID: 00000296
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 15800111A84C0056D29B6559F2A1A61249834B05
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
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]: 0x00EC240000008A31, Samsung, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC2400 (Samsung), Size: 64MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 3EA22A1DDA660002E56108DB5072A10F8709443F
APE Boot skipped on user request
Flashbus Write baud set to 5.0Mbits
Restarting MCU...
Box VPP disabled
All box selftests passed!
Super DCT4 Activation: TRUE
XGold/Blackberry Service Running, Counter: 95
Avaiable Physical Memory: 1.1023GB
Avaiable Virtual Memory: 1.901GB
Avaiable Pagefile: 3.1023GB
Initializing FBUS...
All initialized - Ready to work
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006030C192101033000
CMT_EM_ASIC_ID: 00000296
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 15800111A84C0056D29B6559F2A1A61249834B05
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
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]: 0x00EC240000008A31, Samsung, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC2400 (Samsung), Size: 64MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 3EA22A1DDA660002E56108DB5072A10F8709443F
APE Boot skipped on user request
Flashbus Write baud set to 5.0Mbits
Restarting MCU...
Retrieving Variants for Product RM-561 - wait...
Failed to retrieve BB5 Variants -> Unexpected error, no VPL or neither INI files found inside Product Directory
Processing pre flash tasks...
Pre flash tasks finished, continuing...
Processing rm561__09.98.mcusw (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006030C192101033000
CMT_EM_ASIC_ID: 00000296
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 15800111A84C0056D29B6559F2A1A61249834B05
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
rm561__09.98.mcusw, Type: Flash Image, Algo: BB5, BB5 ALGORITHM
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
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]: 0x00EC240000008A31, Samsung, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC2400 (Samsung), Size: 64MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 3EA22A1DDA660002E56108DB5072A10F8709443F
Flashbus Write baud set to 5.0Mbits
Sending Certificates...
Certificates OK
Started group flash erase
EraseArea[0,CMT]: 0x00000000-0x000006BF, NOR
EraseArea[0,CMT]: 0x000006C0-0x0001FFFF, NOR
EraseArea[0,CMT]: 0x00040000-0x000BFFFF, NOR
EraseArea[0,CMT]: 0x000C0000-0x0013FFFF, NOR
EraseArea[0,CMT]: 0x00140000-0x0137FFFF, NOR
EraseArea[0,CMT]: 0x01380000-0x0151FFFF, NOR
Waiting 320s for erasure finish...
Erase taken 77.890s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT NOLO Certificate...
Writing CMT KEYS Certificate...
Writing CMT PRIMAPP Certificate...
Writing CMT PASUBTOC Certificate...
Block Write Failed -> Failed to write CMT cert data (3), Programming Status Error
Processing Flash Image Failed -> Failed to write all blocks
Failed to Process all Image files -> Failed to process rm561__09.98.mcusw
Processing pre flash tasks...
Pre flash tasks finished, continuing...
Processing rm561__09.98.mcusw (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006030C192101033000
CMT_EM_ASIC_ID: 00000296
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 15800111A84C0056D29B6559F2A1A61249834B05
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
rm561__09.98.mcusw, Type: Flash Image, Algo: BB5, BB5 ALGORITHM
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
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]: 0x00EC240000008A31, Samsung, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC2400 (Samsung), Size: 64MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
Warning: PAPUBKEYS Hash Missing!
Flashbus Write baud set to 5.0Mbits
Sending Certificates...
Certificates OK
Started group flash erase
EraseArea[0,CMT]: 0x00000000-0x000006BF, NOR
EraseArea[0,CMT]: 0x000006C0-0x0001FFFF, NOR
EraseArea[0,CMT]: 0x00040000-0x000BFFFF, NOR
EraseArea[0,CMT]: 0x000C0000-0x0013FFFF, NOR
EraseArea[0,CMT]: 0x00140000-0x0137FFFF, NOR
EraseArea[0,CMT]: 0x01380000-0x0151FFFF, NOR
Waiting 320s for erasure finish...
Erase taken 5.890s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT NOLO Certificate...
Writing CMT KEYS Certificate...
Writing CMT PRIMAPP Certificate...
Writing CMT PASUBTOC Certificate...
WARNING: CMT PAPUBKEYS Hash is Empty, writing first found PAPUBKEYS
Writing CMT PAPUBKEYS Certificate...
Writing CMT UPDAPP Certificate...
Writing CMT DSP0 Certificate...
Writing CMT MCUSW Certificate...
Programming Status OK!
All blocks written OK! Time taken 66.797s
Flashing Speed: 2437,28 kBit/S
Restarting MCU...
Processing rm561__09.98.mcusw (APE)...
Processing rm561__09.98.ppm_t (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006030C192101033000
CMT_EM_ASIC_ID: 00000296
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 15800111A84C0056D29B6559F2A1A61249834B05
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
rm561__09.98.ppm_t, Type: Flash Image, Algo: BB5, BB5 ALGORITHM
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
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]: 0x00EC240000008A31, Samsung, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC2400 (Samsung), Size: 64MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 3EA22A1DDA660002E56108DB5072A10F8709443F
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x01520000-0x01DBFFFF, NOR
Waiting 320s for erasure finish...
Erase taken 25.766s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Programming Status OK!
All blocks written OK! Time taken 23.172s
Flashing Speed: 2395,44 kBit/S
Restarting MCU...
Processing rm561__09.98.ppm_t (APE)...
Processing rm561__09.98.image_ctv_nz_gray (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006030C192101033000
CMT_EM_ASIC_ID: 00000296
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 15800111A84C0056D29B6559F2A1A61249834B05
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
rm561__09.98.image_ctv_nz_gray, Type: Flash Image, Algo: BB5, BB5 ALGORITHM
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
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]: 0x00EC240000008A31, Samsung, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC2400 (Samsung), Size: 64MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 3EA22A1DDA660002E56108DB5072A10F8709443F
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x01DC0000-0x0215FFFF, NOR
EraseArea[0,CMT]: 0x02160000-0x03FBFFFF, NOR
Waiting 320s for erasure finish...
Erase taken 50.31s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Programming Status OK!
All blocks written OK! Time taken 36.188s
Flashing Speed: 2523,86 kBit/S
Restarting MCU...
Processing rm561__09.98.image_ctv_nz_gray (APE)...
All images processed OK! Processing post flash tasks...
Setting Factory Defaults...
на шилдике написанно 2700с-2 rm-561
может ест 2700с с другим rm и вписал там rm-561 тело вафше перестало вклучатса даже вибро нет
до прашивки сделал бекапи и сделал full errase и потом прашивка всеравно труп