E-70 RM-10 dead after flash
 

Establishing Connection with Box in Main Mode...
Handling device: [Cyclone Team], [Cyclone Box], [Platform: Classic]
Initializing box...
Box Firmware: Cyclone Main Application v02.04, (Jun 10 2012 18:37:23, 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: C0002DB5
HW Revision: A, Suitable for: Production, Case: First Plastic Case, MCU Manufacture Time: 2009, wk32
Initializing security card...
Card Serial Number: DC0000F8
Card Firmware Revision: 0109
Card is activated
Box is activated
Started box selftests procedure
USB Voltage 4,93v PASSED
MCU Voltage 3,30v PASSED
Core Voltage 1,80v PASSED
VBAT Voltage 0,01v PASSED
VBAT Voltage 4,85v PASSED
Box VPP disabled
VPP Voltage 0,04v PASSED
Internal Box VPP Enabled
VPP Voltage 4,79v PASSED
Box VPP disabled
VPP Voltage 0,04v PASSED
External Box VPP Enabled
VPP Voltage 0,02v FAILED - IGNORED - Probably power supply is not connected
Box VPP disabled
All box selftests passed!
Super DCT4 Activation: TRUE
XGold/Blackberry Service Running, Counter: 100
Avaiable Physical Memory: 1023.1023MB
Avaiable Virtual Memory: 1.713GB
Avaiable Pagefile: 1023.1023MB
Initializing FBUS...
All initialized - Ready to work
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: 4D3A2D41D952D8276C1178CB709489DB6445527E
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006000C192101002200
CMT_EM_ASIC_ID: 00000232
CMT_EM_ASIC_ID: 00000352
CMT_PUBLIC_ID: 05600109AD985451E22F01B9F4F7D977C94A4173
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: E9EFF4BFAA5393217CA6B17755FC3E14
CMT_BOOT_ROM_CRC: F28A211F
CMT_SECURE_ROM_CRC: CEA7B19D
CMT Ready!
Searching for BootCode: DualLine 32Bit (Forcing OLD Protocol)
RAP3Gv2_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.21.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]: 0x00EC225000000121, 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 (Forcing OLD Protocol)
FlashChip 0x00EC2250 (Samsung), Size: 8MBytes, 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: 934BAFC08E9C7E8E99878E3AD8AC3C198071CBB4
APE Boot skipped on user request
Flashbus Write baud set to 5.0Mbits
Restarting MCU...
Scanning avaiable products...
Processing C:\Program Files (x86)\Nokia\Phoenix\Products\...
Processing C:\Program Files (x86)\Common Files\Nokia\DataPackage\Products\...
Processing C:\ProgramData\Nokia\Packages\Products\...
Found 153 products, Filtering BB5 Products - wait...
Failed to Substitue INI Variant Data -> Access violation at address 006A5962 in module 'Cyclone.exe'. Read of address 00000000
79 Products left after filtering. Ready.
Retrieving Variants for Product RM-10 - wait...
53 Variants Retrieved
Processing pre flash tasks...
Read RPL operation not possible for Old USB Flashing Method
Pre flash tasks finished, continuing...
Processing rm10_m128_h20_kz_prod_306330904_c00_combined.bin (CMT)...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: 4D3A2D41D952D8276C1178CB709489DB6445527E
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006000C192101002200
CMT_EM_ASIC_ID: 00000232
CMT_EM_ASIC_ID: 00000352
CMT_PUBLIC_ID: 05600109AD985451E22F01B9F4F7D977C94A4173
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: E9EFF4BFAA5393217CA6B17755FC3E14
CMT_BOOT_ROM_CRC: F28A211F
CMT_SECURE_ROM_CRC: CEA7B19D
CMT Ready!
rm10_m128_h20_kz_prod_306330904_c00_combined.bin, Type: Flash Image, Algo: BB5, BB5 ALGORITHM, BB5, OMAP1710 UNISTORE-II-1.2.1 ALG
Searching for BootCode: DualLine 32Bit (Forcing OLD Protocol)
RAP3Gv2_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.21.0, Algo: BB5
Flashbus Write baud set to 650Kbits
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]: 0x00EC225000000121, 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 (Forcing OLD Protocol)
FlashChip 0x00EC2250 (Samsung), Size: 8MBytes, 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: 934BAFC08E9C7E8E99878E3AD8AC3C198071CBB4
Flashbus Write baud set to 5.0Mbits
Sending Certificates...
Certificates OK
Partitioning...
Partitioning OK
Started group flash erase
EraseArea[0,CMT]: 0x00000000-0x00530AA9, NOR
EraseArea[0,CMT]: 0x006A0000-0x006EFFFF, NOR
EraseArea[0,CMT]: 0x00700000-0x007EFFFF, NOR
Waiting 320s for erasure finish...
Erase taken 39.608s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT NOLO Certificate...
Writing CMT KEYS Certificate...
Writing CMT PRIMAPP Certificate...
Writing CMT DSP0 Certificate...
Writing CMT MCUSW Certificate...
Writing CMT ADL Certificate...
Writing CMT PASUBTOC Certificate...
Writing CMT PAPUBKEYS Certificate...
Programming Status OK!
All blocks written OK! Time taken 31.543s
Flashing Speed: 8589,44 kBit/S
Restarting MCU...
Processing rm10_m128_h20_kz_prod_306330904_c00_combined.bin (APE)...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: 4D3A2D41D952D8276C1178CB709489DB6445527E
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006000C192101002200
CMT_EM_ASIC_ID: 00000232
CMT_EM_ASIC_ID: 00000352
CMT_PUBLIC_ID: 05600109AD985451E22F01B9F4F7D977C94A4173
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: E9EFF4BFAA5393217CA6B17755FC3E14
CMT_BOOT_ROM_CRC: F28A211F
CMT_SECURE_ROM_CRC: CEA7B19D
CMT Ready!
rm10_m128_h20_kz_prod_306330904_c00_combined.bin, Type: Flash Image, Algo: BB5, BB5 ALGORITHM, BB5, OMAP1710 UNISTORE-II-1.2.1 ALG
Searching for BootCode: DualLine 32Bit (Forcing OLD Protocol)
RAP3Gv2_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.21.0, Algo: BB5
Flashbus Write baud set to 650Kbits
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]: 0x00EC225000000121, 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 (Forcing OLD Protocol)
FlashChip 0x00EC2250 (Samsung), Size: 8MBytes, 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: 934BAFC08E9C7E8E99878E3AD8AC3C198071CBB4
Searching for BootCode: DualLine 32Bit (Forcing OLD Protocol)
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
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,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit (Forcing OLD Protocol)
FlashChip 0x00EC00A1 (Samsung), Size: 128MBytes, VPP: 21V
h3_sam_nand_xsr.fg, Type: Algorithm, Rev: 0.1.49.0, Algo: OMAP1710 UNISTORE-II-1.2.1 ALG
Box VPP disabled
Internal APE Phone VPP Enabled
PAPUBKEYS Hash for APE: 5C7C2BDE2E6456F2BD186CE0F16555246134EB8B
Flashbus Write baud set to 5.0Mbits
Sending Certificates...
Certificates OK
Partitioning...
Partitioning OK
Started group flash erase
EraseArea[0,APE]: 0x00000000-0x0007FFFF, NAND
EraseArea[0,APE]: 0x00080000-0x000803FF, NAND
EraseArea[0,APE]: 0x000C0000-0x0377FFFF, NAND
Waiting 320s for erasure finish...
Erase taken 0.843s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing APE KEYS Certificate...
Writing APE X-LOADER Certificate...
Writing APE PRIMAPP Certificate...
Writing APE SOS+LOADER Certificate...
Writing APE ADL Certificate...
Writing APE SOS+XZIP Certificate...
Writing APE PASUBTOC Certificate...
Writing APE PAPUBKEYS Certificate...
Skipping APE PAPUBKEYS Certificate (already sent)...
Writing APE SOS*CORE Certificate...
Programming Status OK!
All blocks written OK! Time taken 43.119s
Flashing Speed: 6283,46 kBit/S
Restarting MCU...
Processing rm10_m128_h20_kz_prod_306330904_v01_variant.bin (CMT)...
Processing rm10_m128_h20_kz_prod_306330904_v01_variant.bin (APE)...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: 4D3A2D41D952D8276C1178CB709489DB6445527E
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006000C192101002200
CMT_EM_ASIC_ID: 00000232
CMT_EM_ASIC_ID: 00000352
CMT_PUBLIC_ID: 05600109AD985451E22F01B9F4F7D977C94A4173
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: E9EFF4BFAA5393217CA6B17755FC3E14
CMT_BOOT_ROM_CRC: F28A211F
CMT_SECURE_ROM_CRC: CEA7B19D
CMT Ready!
rm10_m128_h20_kz_prod_306330904_v01_variant.bin, Type: Flash Image, Algo: BB5, OMAP1710 UNISTORE-II-1.2.1 ALG, BB5, BB5 ALGORITHM
Searching for BootCode: DualLine 32Bit (Forcing OLD Protocol)
RAP3Gv2_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.21.0, Algo: BB5
Flashbus Write baud set to 650Kbits
Flashbus Read baud set to 100Kbits
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]: 0x00EC225000000121, 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 (Forcing OLD Protocol)
FlashChip 0x00EC2250 (Samsung), Size: 8MBytes, 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: 934BAFC08E9C7E8E99878E3AD8AC3C198071CBB4
Searching for BootCode: DualLine 32Bit (Forcing OLD Protocol)
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
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,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit (Forcing OLD Protocol)
FlashChip 0x00EC00A1 (Samsung), Size: 128MBytes, VPP: 21V
h3_sam_nand_xsr.fg, Type: Algorithm, Rev: 0.1.49.0, Algo: OMAP1710 UNISTORE-II-1.2.1 ALG
Box VPP disabled
Internal APE Phone VPP Enabled
PAPUBKEYS Hash for APE: 5C7C2BDE2E6456F2BD186CE0F16555246134EB8B
Flashbus Write baud set to 5.0Mbits
Partitioning...
Partitioning OK
Started group flash erase
EraseArea[0,APE]: 0x02180000-0x0377FFFF, NAND
Waiting 320s for erasure finish...
Erase taken 0.312s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Programming Status OK!
All blocks written OK! Time taken 26.520s
Flashing Speed: 4352,05 kBit/S
Restarting MCU...
All images processed OK! Processing post flash tasks...
Setting Factory Defaults...