Care Unlock  
Your online unlock store
GSM-Forum  

Welcome to the GSM-Forum forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!

If you have any problems with the registration process or your account login, please contact contact us.

Go Back   GSM-Forum > Product Support Sections > Hard/Software Products (official support) > Cyclonebox

Reply
 
LinkBack Thread Tools Display Modes
Old 05-11-2012, 12:06   #1 (permalink)
Freak Poster
 
Join Date: Jul 2010
Posts: 357
Member: 1343907
Status: Offline
Thanks: 38
Thanked 32 Times in 22 Posts
6500c Failed ST_CAMERA_IF_TEST

Retrieving Variants for Product RM-265 - wait...
1 Variants Retrieved
Processing pre flash tasks...
Pre flash tasks finished, continuing...
Processing rm265__10.50.mcusw (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101003000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1C200108D1F50154B00288D72E2AA2F6AB2639B5
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
rm265__10.50.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]: 0x00EC220C00008921, 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 0x00EC220C (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: D0D8948DEF333BF18141EF4C3D0FB1B002EB5D88
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x00000000-0x0001FFFF, NOR
EraseArea[0,CMT]: 0x00040000-0x000BFFFF, NOR
EraseArea[0,CMT]: 0x000C0000-0x0013FFFF, NOR
EraseArea[0,CMT]: 0x013C0000-0x0153FFFF, NOR
EraseArea[0,CMT]: 0x00140000-0x013BFFFF, NOR
Waiting 320s for erasure finish...
Erase taken 6.312s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT NOLO Certificate...
Writing CMT KEYS Certificate...
Writing CMT PRIMAPP Certificate...
Writing CMT PASUBTOC Certificate...
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 112.344s
Flashing Speed: 1353.58 kBit/S
Restarting MCU...
Processing rm265__10.50.mcusw (APE)...
Processing rm265__10.50.ppm_a (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101003000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1C200108D1F50154B00288D72E2AA2F6AB2639B5
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
rm265__10.50.ppm_a, 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]: 0x00EC220C00008921, 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 0x00EC220C (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: D0D8948DEF333BF18141EF4C3D0FB1B002EB5D88
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x01540000-0x01BBFFFF, NOR
Waiting 320s for erasure finish...
Erase taken 1.484s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Programming Status OK!
All blocks written OK! Time taken 33.141s
Flashing Speed: 1330.96 kBit/S
Restarting MCU...
Processing rm265__10.50.ppm_a (APE)...
Processing rm265__10.50_ISM_011.image_tdc_dk (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101003000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1C200108D1F50154B00288D72E2AA2F6AB2639B5
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
rm265__10.50_ISM_011.image_tdc_dk, Type: Flash Image, Algo: BB5, XSR 1.5
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 51Kbits
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]: 0x00EC220C00008921, 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 0x00EC220C (Samsung), Size: 64MBytes, VPP: 9V
RAP3Gv3_algo_xsr15.fg, Type: Algorithm, Rev: 0.1.40.0, Algo: XSR 1.5
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: D0D8948DEF333BF18141EF4C3D0FB1B002EB5D88
Flashbus Write baud set to 5.0Mbits
Sending Certificates...
Certificates OK
Sending XSR Configuration...
XSR Configuration OK
Started group flash erase
EraseArea[0,CMT]: 0x01EC0000-0x03F9FFFF, NOR
EraseArea[0,CMT]: 0x01BC0000-0x01EBFFFF, NOR
Waiting 320s for erasure finish...
Erase taken 16.687s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Programming Status OK!
All blocks written OK! Time taken 320.625s
Flashing Speed: 277.11 kBit/S
Restarting MCU...
Processing rm265__10.50_ISM_011.image_tdc_dk (APE)...
All images processed OK! Processing post flash tasks...
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: 000000010000022600010006010C192101003000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1C200108D1F50154B00288D72E2AA2F6AB2639B5
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
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]: 0x00EC220C00008921, 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 0x00EC220C (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: D0D8948DEF333BF18141EF4C3D0FB1B002EB5D88
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 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: 000000010000022600010006010C192101003000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1C200108D1F50154B00288D72E2AA2F6AB2639B5
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
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]: 0x00EC220C00008921, 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 0x00EC220C (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: D0D8948DEF333BF18141EF4C3D0FB1B002EB5D88
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!
MCU Version V 10.50
MCU Date 26-06-09
Product RM-265 (Nokia 6500 classic)
Manufacturer (c) Nokia
IMEI 357683011895069
Mastercode 5357772353
IMEI Spare 3A75860311980506
IMEI SV 3375860311980586F0000000
PPM V 10.50, 26-06-09, RM-265, (c) Nokia , A
CNT Content: tdc_dk, V 10.50, 26-06-09, RM-265, (c) Nokia , ,
PSN M9F210015
Product Code 0556153
PSD 0000000000000000
LPSN 0
RETU 15
TAHVO 22
AHNE 30
HW 1002
RFIC 17141715
DSP ICPR71_08w30
LCD SEIKO
BT 06cc-P9.2
Failed to read info -> Failed to read SP info
Started Phone Security Analysis...
MCU Version V 10.50
MCU Date 26-06-09
Product RM-265 (Nokia 6500 classic)
Manufacturer (c) Nokia
IMEI 357683011895069
Mastercode 5357772353
Reading Security Block...
Security block OK and saved to "RM-265_357683011895069_5112012_64453 PM.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: 000000010000022600010006010C192101003000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1C200108D1F50154B00288D72E2AA2F6AB2639B5
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
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]: 0x00EC220C00008921, 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 0x00EC220C (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: D0D8948DEF333BF18141EF4C3D0FB1B002EB5D88
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
"1C200108D1F50154B00288D72E2AA2F6AB2639B5.C0000366 " Exists, That is good...
Checking SUPERDONGLE...
SUPERDONGLE FOUND AND CHECKSUM OK! PASSED!
Checking SIMLOCK...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
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!
SX4 Authorization / SD Repair Procedure Started....
Failed to obtain Phone Unique Data, Will use Server and Original Card
MCU Version V 10.50
MCU Date 26-06-09
Product RM-265 (Nokia 6500 classic)
Manufacturer (c) Nokia
IMEI 357683011895069
Mastercode 5357772353
SX4 Status: Not authorized (74)
Started mutual authenthication with card...
Cyclone Server (2.0.0.32), Cyclone Box Team 2008-2012 - Ready.
Receiving Phone Seed 1...
Phone Seed 1 Received
Sending calculated Data 1, and expecting Seed 2...
Calculated Data 1 accepted, Phone Seed 2 Received
Disconnected from Cyclone Server
Failed to Authorize SX4 -> Failed to receive mutual Data 2 from server
Failed to Write PM -> No file assigned by user
SX4 Authorization / SD Repair Procedure Started....
Failed to obtain Phone Unique Data, Will use Server and Original Card
MCU Version V 10.50
MCU Date 26-06-09
Product RM-265 (Nokia 6500 classic)
Manufacturer (c) Nokia
IMEI 357683011895069
Mastercode 5357772353
SX4 Status: Not authorized (74)
Started mutual authenthication with card...
Cyclone Server (2.0.0.32), Cyclone Box Team 2008-2012 - Ready.
Receiving Phone Seed 1...
Phone Seed 1 Received
Sending calculated Data 1, and expecting Seed 2...
Calculated Data 1 accepted, Phone Seed 2 Received
Disconnected from Cyclone Server
Failed to Authorize SX4 -> Failed to receive mutual Data 2 from server
BB5 Unlock Started...
MCU Version V 10.50
MCU Date 26-06-09
Product RM-265 (Nokia 6500 classic)
Manufacturer (c) Nokia
IMEI 357683011895069
Mastercode 5357772353
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-265_357683011895069_5112012_64622 PM.SecurityBlock.PM"
"1C200108D1F50154B00288D72E2AA2F6AB2639B5.C0000366 " Exists, That is good...
Checking for Rootkey Hash support with selected Unlock Method...
Selected Unlock Method: RPL Calculation
Asking box to calculate RPL...
Received RPL from Box OK!
Writing Simlock...
Simlock ACCEPTED OK !
MCU Version V 10.50
MCU Date 26-06-09
Product RM-265 (Nokia 6500 classic)
Manufacturer (c) Nokia
IMEI 357683011895069
Mastercode 5357772353
Simlock Server SIMLOCK SERVER
Simlock Key 2440700000000000
Simlock Profile 8000000000000006
Simlock Key Cnt 0
Simlock FBUS Cnt 0
Simlock [1,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [1,2] State: OPENED Type: GID Data: FFFF
Simlock [1,3] State: OPENED Type: GID Data: FFFF
Simlock [1,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [1,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [2,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [2,2] State: OPENED Type: GID Data: FFFF
Simlock [2,3] State: OPENED Type: GID Data: FFFF
Simlock [2,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [2,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [3,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [3,2] State: OPENED Type: GID Data: FFFF
Simlock [3,3] State: OPENED Type: GID Data: FFFF
Simlock [3,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [3,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [4,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [4,2] State: OPENED Type: GID Data: FFFF
Simlock [4,3] State: OPENED Type: GID Data: FFFF
Simlock [4,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [4,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [5,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [5,2] State: OPENED Type: GID Data: FFFF
Simlock [5,3] State: OPENED Type: GID Data: FFFF
Simlock [5,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [5,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [6,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [6,2] State: OPENED Type: GID Data: FFFF
Simlock [6,3] State: OPENED Type: GID Data: FFFF
Simlock [6,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [6,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [7,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [7,2] State: OPENED Type: GID Data: FFFF
Simlock [7,3] State: OPENED Type: GID Data: FFFF
Simlock [7,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [7,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Unlock finished! Time taken 3.593s
MCU Version V 10.50
MCU Date 26-06-09
Product RM-265 (Nokia 6500 classic)
Manufacturer (c) Nokia
IMEI 357683011895069
Mastercode 5357772353
IMEI Spare 3A75860311980506
IMEI SV 3375860311980586F0000000
PPM V 10.50, 26-06-09, RM-265, (c) Nokia , A
CNT Content: tdc_dk, V 10.50, 26-06-09, RM-265, (c) Nokia , ,
PSN M9F210015
Product Code 0556153
PSD 0000000000000000
LPSN 0
RETU 15
TAHVO 22
AHNE 30
HW 1002
RFIC 17141715
DSP ICPR71_08w30
LCD SEIKO
BT 06cc-P9.2
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: 0556153
This is Valid BB5 Product
No variant found with given Product Code, selecting first one
Started Phone Security Analysis...
MCU Version V 10.50
MCU Date 26-06-09
Product RM-265 (Nokia 6500 classic)
Manufacturer (c) Nokia
IMEI 357683011895069
Mastercode 5357772353
Reading Security Block...
Security block OK and saved to "RM-265_357683011895069_5112012_64649 PM.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: 000000010000022600010006010C192101003000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1C200108D1F50154B00288D72E2AA2F6AB2639B5
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
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]: 0x00EC220C00008921, 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 0x00EC220C (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: D0D8948DEF333BF18141EF4C3D0FB1B002EB5D88
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
"1C200108D1F50154B00288D72E2AA2F6AB2639B5.C0000366 " 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!
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101003000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1C200108D1F50154B00288D72E2AA2F6AB2639B5
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
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]: 0x00EC220C00008921, 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 0x00EC220C (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: D0D8948DEF333BF18141EF4C3D0FB1B002EB5D88
APE Boot skipped on user request
Flashbus Write baud set to 5.0Mbits
Restarting MCU...
SX4 Authorization / SD Repair Procedure Started....
"1C200108D1F50154B00288D72E2AA2F6AB2639B5.C0000366 " Exists, That is good...
MCU Version V 10.50
MCU Date 26-06-09
Product RM-265 (Nokia 6500 classic)
Manufacturer (c) Nokia
IMEI 357683011895069
Mastercode 5357772353
Reading Security Block...
Security block OK and saved to "RM-265_357683011895069_5112012_65638 PM.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...
Found, writing...
[1,0] Written, Length: 114 bytes, Status: OK
[1,2] Written, Length: 98 bytes, Status: OK
[1,4] Written, Length: 110 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,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,28] Written, Length: 98 bytes, Status: OK
[1,29] Written, Length: 10 bytes, Status: OK
[1,31] Written, Length: 98 bytes, Status: OK
[1,33] Written, Length: 36 bytes, Status: OK
[1,34] Written, Length: 80 bytes, Status: OK
[1,40] Written, Length: 16 bytes, Status: OK
[1,41] Written, Length: 182 bytes, Status: OK
[1,42] Written, Length: 4 bytes, Status: OK
[1,43] Written, Length: 36 bytes, Status: OK
[1,44] Written, Length: 182 bytes, Status: OK
[309,0] Written, Length: 4 bytes, Status: OK
[309,1] Written, Length: 2 bytes, Status: OK
[309,2] Written, Length: 12 bytes, Status: OK
[309,4] Written, Length: 12 bytes, Status: OK
[309,5] Written, Length: 12 bytes, Status: OK
[309,7] Written, Length: 12 bytes, Status: OK
[309,8] Written, Length: 12 bytes, Status: OK
[309,17] Written, Length: 12 bytes, Status: OK
Write PM Finished, Record written OK: 32, Record written NOT OK: 0
Started Phone Security Analysis...
MCU Version V 10.50
MCU Date 26-06-09
Product RM-265 (Nokia 6500 classic)
Manufacturer (c) Nokia
IMEI 357683011895069
Mastercode 5357772353
Reading Security Block...
Security block OK and saved to "RM-265_357683011895069_5112012_65652 PM.SecurityBlock.PM"
Step 1 : Testing SIMLOCK
SIMLOCK SEFLTEST PASSED OK!
Step 2 : Testing SECURITY
SECURITY SEFLTEST PASSED OK!
Step 3 : Analyzing Security Block
"1C200108D1F50154B00288D72E2AA2F6AB2639B5.C0000366 " Exists, That is good...
Checking SUPERDONGLE...
SUPERDONGLE FOUND AND CHECKSUM OK! PASSED!
Checking SIMLOCK...
SIMLOCK FOUND AND CHECKSUM OK! PASSED!
Checking MCU&DSP TIMESTAMPS...
MCU&DSP TIMESTAMPS FOUND AND CHECKSUM OK! PASSED!
Checking CMLA KEYS...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking ECC KEYS...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking DIV KEYS...
DIV KEYS FOUND AND CHECKSUM OK! PASSED!
Analyze finished!
Selftests to proceed: 34
Passed ST_TAHVOINT_TEST
Passed ST_EAR_DATA_LOOP_TEST
Passed ST_SIM_CLK_LOOP_TEST
Passed ST_SIM_IO_CTRL_LOOP_TEST
Passed ST_SIM_LOCK_TEST
Passed ST_SLEEP_X_LOOP_TEST
Passed ST_SLEEPCLK_FREQ_TEST
Passed ST_UEM_CBUS_IF_TEST
Passed ST_KEYBOARD_STUCK_TEST
Failed ST_CAMERA_IF_TEST
Passed ST_BACKUP_BATT_TEST
Passed ST_LPRF_IF_TEST
Passed ST_LPRF_AUDIO_LINES_TEST
Passed ST_CURRENT_CONS_TEST
Passed ST_LCD_TEST
Passed ST_BACKLIGHT_TEST
Passed ST_SECURITY_TEST
Passed ST_PWR_KEY_TEST
Passed ST_BT_WAKEUP_TEST
Passed ST_BTEMP_TEST
Passed ST_BT_SLEEP_CLK_TEST
Passed ST_AMB_LIGHT_SENSOR_TEST
Passed ST_MASS_MEMORY_IF_TEST
Passed ST_EXT_DEVICE_TEST
Passed ST_CDSP_RF_BB_IF_TEST
Passed ST_CDSP_RF_SUPPLY_TEST
Passed ST_CDSP_TX_IQ_TEST
Passed ST_CDSP_TXC_DATA_TEST
Passed ST_CDSP_PWR_DETECTOR_BIAS_TEST
Passed ST_CDSP_RX_PLL_PHASE_LOCK_TEST
Passed ST_CDSP_TX_PLL_PHASE_LOCK_TEST
Passed ST_CDSP_WCDMA_TX_POWER_TEST
Passed ST_CDSP_RX_IQ_LOOP_BACK_TEST
Passed ST_CDSP_GSM_TX_POWER_TEST
Selftests done, Tests total: 34, Tests passed: 33, Tests not passed: 1
  Reply With Quote
Old 05-11-2012, 12:09   #2 (permalink)
Freak Poster
 
Join Date: Jul 2010
Posts: 357
Member: 1343907
Status: Offline
Thanks: 38
Thanked 32 Times in 22 Posts
Analyzing Dynamic Camera Configuration...

--> Primary Camera Not Exists

Secondary Camera: STMMIIIIRRFFMMIIIIRRXXXXXX
Secondary Camera Configuration is destroyed, writing factory one...
Configuration file not exists, Contact Support to obtain one!

Dynamic Camera Configuration Analyze/Repair Finished!
  Reply With Quote
Old 05-11-2012, 12:57   #3 (permalink)
Super Moderator
 
moulnisky's Avatar
 
Join Date: Jan 2009
Location: England
Age: 48
Posts: 14,885
Member: 947561
Status: Offline
Thanks: 2,690
Thanked 11,397 Times in 5,004 Posts
Change the camera module or try cleaning the contacts in tis own one

BR

Alex
  Reply With Quote
Old 05-12-2012, 00:17   #4 (permalink)
No Life Poster
 
Join Date: Feb 2010
Location: Pinas
Posts: 898
Member: 1243303
Status: Offline
Sonork: 1591167
Thanks: 203
Thanked 496 Times in 204 Posts
i think no one repair dcc problem for that phone
  Reply With Quote
Old 05-12-2012, 00:22   #5 (permalink)
Super Moderator
 
moulnisky's Avatar
 
Join Date: Jan 2009
Location: England
Age: 48
Posts: 14,885
Member: 947561
Status: Offline
Thanks: 2,690
Thanked 11,397 Times in 5,004 Posts
STMMIIIIRRFFMMIIIIRRXXXXXX

The red part indicates a problem in reading properly the camera hence why I go for the hardware issue

BR

Alex
  Reply With Quote
Old 05-12-2012, 02:22   #6 (permalink)
Freak Poster
 
Join Date: Jul 2010
Posts: 357
Member: 1343907
Status: Offline
Thanks: 38
Thanked 32 Times in 22 Posts
thanks for reply

going to hardware
  Reply With Quote
Old 05-13-2012, 01:30   #7 (permalink)
Freak Poster
 
Join Date: Jul 2010
Posts: 357
Member: 1343907
Status: Offline
Thanks: 38
Thanked 32 Times in 22 Posts
update

camera ok and this phone problem before flash is memory full

more ideas please
  Reply With Quote
Old 05-15-2012, 01:05   #8 (permalink)
Freak Poster
 
Join Date: Jul 2010
Posts: 357
Member: 1343907
Status: Offline
Thanks: 38
Thanked 32 Times in 22 Posts
hello

camera ok any link DCC file for this phone?
  Reply With Quote
Old 05-15-2012, 04:23   #9 (permalink)
Product Supporter
 
Mr.3.'s Avatar
 
Join Date: Feb 2009
Location: CMB/Ceylon
Posts: 5,542
Member: 962029
Status: Offline
Sonork: ( Protected )
Thanks: 247
Thanked 3,490 Times in 1,068 Posts
Is built in Memory working ?
  Reply With Quote
Old 05-15-2012, 07:47   #10 (permalink)
Super Moderator
 
moulnisky's Avatar
 
Join Date: Jan 2009
Location: England
Age: 48
Posts: 14,885
Member: 947561
Status: Offline
Thanks: 2,690
Thanked 11,397 Times in 5,004 Posts
do you have any pm back-up done before the flashing?

BR

Alex
  Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
thread Thread Starter Forum Replies Last Post
3330 v 412 fail with dfs 211 denn Nokia Legacy Phones ( DCT-1 , DCT-2 , DCT-3 , DCT-L ) 1 09-19-2001 22:06
In wintesla 3310, what does cobba parrarel failed means brittnee Nokia Legacy Phones ( DCT-1 , DCT-2 , DCT-3 , DCT-L ) 10 05-18-2001 16:05
MCU EEPROM contents: failed phr3ak Nokia Legacy Phones ( DCT-1 , DCT-2 , DCT-3 , DCT-L ) 0 02-12-2001 14:58
Nokia 5110 v. 5.24 Unlock Failed! Cybertooth Nokia Legacy Phones ( DCT-1 , DCT-2 , DCT-3 , DCT-L ) 3 02-28-2000 14:35
Mti init failed dogbreak Nokia Legacy Phones ( DCT-1 , DCT-2 , DCT-3 , DCT-L ) 3 11-22-1999 00:28


All times are GMT +1. The time now is 21:51.



Powered by Searchlight © 2013 Axivo Inc.
- GSM Hosting Ltd. - 1999-2013 -
Page generated in 0.44609 seconds with 11 queries

SEO by vBSEO