Hello.
Could you please support me, after the update makes Flash a N73 and was the IMEI 12345610654321? ...
RPL I hit no double of it just formatted the machine and lost everything ....
Will could support me.
Noe After Flash "Phone Star-up Failed. Contact the Retailer"
I tried to revive:
Flash + Write Virgin RPL + Write whit SX4 Virgin PM (Stored Files)
This is Log
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 12345610654321?
IMEI Spare 1A32541660452301
IMEI SV 1332541660452371F7000000
PSN CDC924596
Product Code 0542704
Module Code 0202856
Basic Product Code 0545048
PSD 0000002200000000
RETU 15
TAHVO 22
AHNE 30
HW 6008
RFIC 17211721
DSP scarfe_mc.05wk46v50p2
Simlock Server SIMLOCK SERVER VERSION 63
Simlock Key 7223100000000000
Simlock Profile 0000000000000000
Simlock attorney Cnt 0
Simlock FBUS Cnt 0
Simlock [1,1] State: OPENED Type: MCC-MNC Data: 74402F
Simlock [2,1] State: OPENED Type: MCC-MNC Data: 74402F
Simlock [3,1] State: OPENED Type: 3F007F206F07FFFF @ FC00 Data: 722310
Simlock [4,1] State: OPENED Type: 7FFF6F07FFFFFFFF @ FC00 Data: 722310
Simlock [5,1] State: OPENED Type: MCC-MNC Data: 74810F
Simlock [6,1] State: OPENED Type: MCC-MNC Data: 74810F
Auto Selecting Flash Files on User Request...
Product Code: 0542704
This is Valid BB5 Product
No variant institute with presented Product Code, selecting first one
Security Code 19830
Attempts 01
Processing pre winkle tasks...
Backing up RPL...
RPL start started...
Processing CMT Part...
Storing Product Code...
Storing PSN...
Storing HWID...
Simlock Store not supported, not a PA_SL2 Phone
WMDRM Store not supported
Reading Security Block...
Security country OK and ransomed to "RM-133_12345610654321_26092011_201324.SecurityBlock.PM"
WARNING: "1330000756D801545B8B1A65541C21352B65698A.C0001FF6" Not Exists, Will feature it...
Reading CYC enter from phone...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.30.0, Algo: BB5
Flashbus Write baud ordered to 1.0Mbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
Exploiting - streaming preloader...
Preloader streaming OK, Running Custom Loader...
Custom loader streaming OK! Working...
Old Loader Detected
Readed OK, Saving to "1330000756D801545B8B1A65541C21352B65698A.C0001FF6"
Storing Additional Data...
Checking Superdongle Key...
Encrypting Superdongle Key...
Storing Superdongle Key...
Checking CMLA Key...
Storing CMLA Key...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
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 ordered to 1.0Mbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
Storing NPC...
CMT CCC Not Found
CMT HWC Not Found
Storing VARIANT...
CMT PARTNERC Not Found
Processing APE Part...
Storing Product Code...
Storing PSN...
Storing HWID...
APE bureau Not Found
APE CCC Not Found
APE HWC Not Found
APE VARIANT Not Found
APE PARTNERC Not Found
Restarting MCU...
RPL Saved OK
RPL patronage arrange finished, continuing...
Backing up simlock...
MCU Version V 05wk47v61
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 12345610654321?
Simlock patronage OK, ransomed to RM-133_12345610654321_26092011_201417.SLBackup.PM
Backup simlock arrange finished, continuing...
Pre winkle tasks finished, continuing...
Processing N73_4.0839.42.0.1_western_C00_PRD_cc.fpsx (CMT)...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
Processing Flash Image Failed -> Given image enter is not fit for this CMT System ASIC ID (Tick "Skip CMT ID Check" if you are trusty that presented Image File is fit for this phone!).
Failed to Process every Image files -> Failed to impact N73_4.0839.42.0.1_western_C00_PRD_cc.fpsx
Processing pre winkle tasks...
Backing up RPL...
RPL start started...
Processing CMT Part...
Storing Product Code...
Storing PSN...
Storing HWID...
Simlock Store not supported, not a PA_SL2 Phone
WMDRM Store not supported
Reading Security Block...
Security country OK and ransomed to "RM-133_12345610654321_26092011_201455.SecurityBlock.PM"
"1330000756D801545B8B1A65541C21352B65698A.C0001FF6" Exists, That is good...
Storing Additional Data...
Checking Superdongle Key...
Encrypting Superdongle Key...
Storing Superdongle Key...
Checking CMLA Key...
Storing CMLA Key...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
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 ordered to 1.0Mbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
Storing NPC...
CMT CCC Not Found
CMT HWC Not Found
Storing VARIANT...
CMT PARTNERC Not Found
Processing APE Part...
Storing Product Code...
Storing PSN...
Storing HWID...
APE bureau Not Found
APE CCC Not Found
APE HWC Not Found
APE VARIANT Not Found
APE PARTNERC Not Found
Restarting MCU...
RPL Saved OK
RPL patronage arrange finished, continuing...
Backing up simlock...
MCU Version V 05wk47v61
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 12345610654321?
Simlock patronage OK, ransomed to RM-133_12345610654321_26092011_201536.SLBackup.PM
Backup simlock arrange finished, continuing...
Pre winkle tasks finished, continuing...
Processing N73_4.0839.42.0.1_western_C00_PRD_cc.fpsx (CMT)...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
N73_4.0839.42.0.1_western_C00_PRD_cc.fpsx, Type: Flash Image, Algo: BB5, BB5 ALGORITHM, BB5, OMAP1710 UNISTORE-II-1.2.1 ALG
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud ordered to 51Kbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
Partitioning...
Partitioning OK
Started assemble winkle erase
EraseArea[0,CMT]: 0x00080000-0x0073194D, NOR
EraseArea[0,CMT]: 0x00000000-0x0005FFFF, NOR
EraseArea[0,CMT]: 0x001E0000-0x001FFFFF, NOR
EraseArea[0,CMT]: 0x00880000-0x00FEFFFF, NOR
Waiting 320s for erasure finish...
Erase condemned 44.782s
Writing every 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 ADL Certificate...
Writing CMT DSP0 Certificate...
Writing CMT MCUSW Certificate...
Programming Status OK!
All blocks cursive OK! Time condemned 50.515s
Flashing Speed: 7792,83 kBit/S
Restarting MCU...
Processing N73_4.0839.42.0.1_western_C00_PRD_cc.fpsx (APE)...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
N73_4.0839.42.0.1_western_C00_PRD_cc.fpsx, Type: Flash Image, Algo: BB5, BB5 ALGORITHM, BB5, OMAP1710 UNISTORE-II-1.2.1 ALG
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud ordered to 51Kbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
Partitioning...
Partitioning OK
Started assemble winkle erase
EraseArea[0,APE]: 0x00000000-0x0007FFFF, NAND
EraseArea[0,APE]: 0x00080000-0x000FFFFF, NAND
EraseArea[0,APE]: 0x00100000-0x0025FFFF, NAND
EraseArea[0,APE]: 0x003C0000-0x04E1FFFF, NAND
Waiting 320s for erasure finish...
Erase condemned 1.125s
Writing every 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 SOS*UPDAPP Certificate...
Writing APE SOS+UZIP Certificate...
Writing APE PAPUBKEYS Certificate...
Writing APE PASUBTOC Certificate...
Writing APE ADL Certificate...
Writing APE SOS+XZIP Certificate...
Writing APE SOS*CORE Certificate...
Writing APE SOS+ROFS Certificate...
Writing APE SOS+ROFX Certificate...
Programming Status OK!
All blocks cursive OK! Time condemned 121.734s
Flashing Speed: 3233,73 kBit/S
Restarting MCU...
Processing N73_rofx_4.0839.42.0.1_PRD.V08 (CMT)...
Processing N73_rofx_4.0839.42.0.1_PRD.V08 (APE)...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
N73_rofx_4.0839.42.0.1_PRD.V08, Type: Flash Image, Algo: BB5, OMAP1710 UNISTORE-II-1.2.1 ALG, 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 ordered to 650Kbits
Flashbus Read baud ordered to 100Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
Partitioning...
Partitioning OK
Started assemble winkle erase
EraseArea[0,APE]: 0x03920000-0x04E1FFFF, NAND
Waiting 320s for erasure finish...
Erase condemned 0.390s
Writing every blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing APE SOS+ROFX Certificate...
Programming Status OK!
All blocks cursive OK! Time condemned 117.172s
Flashing Speed: 1052,24 kBit/S
Restarting MCU...
Processing N73_userarea_4.0839.42.0.1.U01 (CMT)...
Processing N73_userarea_4.0839.42.0.1.U01 (APE)...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
N73_userarea_4.0839.42.0.1.U01, Type: Flash Image, Algo: BB5, OMAP1710 UNISTORE-II-1.2.1 ALG, 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 ordered to 650Kbits
Flashbus Read baud ordered to 100Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
Started assemble winkle erase
EraseArea[0,APE]: 0x04E20000-0x07C9FFFF, NAND
Waiting 320s for erasure finish...
Erase condemned 0.672s
Writing every blocks...
Initializing TurboCache...
TurboCache Loaded!
Programming Status OK!
All blocks cursive OK! Time condemned 13.390s
Flashing Speed: 3207,41 kBit/S
Restarting MCU...
All images computerized OK! Processing post winkle tasks...
Setting Factory Defaults...
Factory defaults OK
Reading info...
MCU Version V 05wk47v61
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 12345610654321?
IMEI Spare 1A32541660452301
IMEI SV 1332541660452371F7000000
PSN CDC924596
Product Code 0542704
Module Code 0202856
Basic Product Code 0545048
PSD 0000002200000000
RETU 15
TAHVO 22
AHNE 30
HW 6008
RFIC 17211721
DSP scarfe_mc.05wk46v50p2
Simlock Server SIMLOCK SERVER VERSION 63
Simlock Key 7223100000000000
Simlock Profile 0000000000000000
Simlock attorney Cnt 0
Simlock FBUS Cnt 0
Simlock [1,1] State: OPENED Type: MCC-MNC Data: 74402F
Simlock [2,1] State: OPENED Type: MCC-MNC Data: 74402F
Simlock [3,1] State: OPENED Type: 3F007F206F07FFFF @ FC00 Data: 722310
Simlock [4,1] State: OPENED Type: 7FFF6F07FFFFFFFF @ FC00 Data: 722310
Simlock [5,1] State: OPENED Type: MCC-MNC Data: 74810F
Simlock [6,1] State: OPENED Type: MCC-MNC Data: 74810F
Read content arrange finished, continuing...
Post winkle tasks finished!
Flashing successfully finished!
Started Phone Security Analysis...
MCU Version V 05wk47v61
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 12345610654321?
Reading Security Block...
Security country OK and ransomed to "RM-133_12345610654321_26092011_202242.SecurityBlock.PM"
Step 1 : Testing SIMLOCK
SIMLOCK SEFLTEST PASSED OK!
Step 2 : Testing SECURITY
SECURITY SEFLTEST PASSED OK!
Step 3 : Analyzing Security Block
"1330000756D801545B8B1A65541C21352B65698A.C0001FF6" 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...
CMLA KEYS FOUND AND CHECKSUM OK! PASSED!
Checking code KEYS...
Failed to rewrite Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking DIV KEYS...
DIV KEYS FOUND AND CHECKSUM OK! PASSED!
Analyze finished!
Skipping RPL decryption...
Parsing decrypted RPL...
Processing FBUS Part...
Processing FLASHBUS Part...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
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 ordered to 1.0Mbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
CMT VARIANT Erased
CMT VARIANT Written
Restarting MCU...
Write RPL Finished!
MCU Version V 05wk47v61
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 12345610654321?
IMEI Spare 1A32541660452301
IMEI SV 1332541660452371F7000000
PSN CDC924596
Product Code 0542704
Module Code 0202856
Basic Product Code 0545048
PSD 0000002200000000
RETU 15
TAHVO 22
AHNE 30
HW 6008
RFIC 17211721
DSP scarfe_mc.05wk46v50p2
Simlock Server SIMLOCK SERVER VERSION 63
Simlock Key 7223100000000000
Simlock Profile 0000000000000000
Simlock attorney Cnt 0
Simlock FBUS Cnt 0
Simlock [1,1] State: OPENED Type: MCC-MNC Data: 74402F
Simlock [2,1] State: OPENED Type: MCC-MNC Data: 74402F
Simlock [3,1] State: OPENED Type: 3F007F206F07FFFF @ FC00 Data: 722310
Simlock [4,1] State: OPENED Type: 7FFF6F07FFFFFFFF @ FC00 Data: 722310
Simlock [5,1] State: OPENED Type: MCC-MNC Data: 74810F
Simlock [6,1] State: OPENED Type: MCC-MNC Data: 74810F
SX4 Authorization / SD Repair Procedure Started....
"1330000756D801545B8B1A65541C21352B65698A.C0001FF6" Exists, That is good...
MCU Version V 05wk47v61
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 12345610654321?
Reading Security Block...
Security country OK and ransomed to "RM-133_12345610654321_26092011_202335.SecurityBlock.PM"
SX4 Status: Authorized
[1,0] Protecting
[1,2] Protecting
[1,4] Protecting
[1,6] Protecting
[1,8] Protecting
[1,13] Protecting
[1,16] Protecting
[1,18] Protecting
[1,20] Protecting
[1,22] Protecting
[1,23] Protecting
[1,24] Protecting
[1,25] Protecting
[1,26] Protecting
[1,28] Protecting
[1,29] Protecting
[1,31] Protecting
[1,33] Protecting
[1,34] Protecting
[1,44] Protecting
[309,0] Protecting
[309,1] Protecting
[309,2] Protecting
[309,4] Protecting
[309,5] Protecting
[309,7] Protecting
[309,8] Protecting
[309,17] Protecting
[309,22] Protecting
Write PM Finished, Record cursive OK: 29, Record cursive NOT OK: 0
[1,0] Protecting
[1,2] Protecting
[1,4] Protecting
[1,6] Protecting
[1,8] Protecting
[1,13] Protecting
[1,16] Protecting
[1,18] Protecting
[1,20] Protecting
[1,22] Protecting
[1,23] Protecting
[1,24] Protecting
[1,25] Protecting
[1,26] Protecting
[1,28] Protecting
[1,29] Protecting
[1,31] Protecting
[1,33] Protecting
[1,34] Protecting
[1,44] Protecting
[309,0] Protecting
[309,1] Protecting
[309,2] Protecting
[309,4] Protecting
[309,5] Protecting
[309,7] Protecting
[309,8] Protecting
[309,17] Protecting
[309,22] Protecting
Write PM Finished, Record cursive OK: 29, Record cursive NOT OK: 0
[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: 6 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,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
[309,22] Written, Length: 12 bytes, Status: OK
Write PM Finished, Record cursive OK: 29, Record cursive NOT OK: 0
Skipping RPL decryption...
Parsing decrypted RPL...
Processing FBUS Part...
Processing FLASHBUS Part...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
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 ordered to 1.0Mbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
CMT VARIANT Erased
CMT VARIANT Written
Restarting MCU...
Write RPL Finished!
MCU Version V 05wk47v61
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 12345610654321?
IMEI Spare 1A32541660452301
IMEI SV 1332541660452371F7000000
PSN CDC924596
Product Code 0542704
Module Code 0202856
Basic Product Code 0545048
PSD 0000002200000000
RETU 15
TAHVO 22
AHNE 30
HW 6008
RFIC 17211721
DSP scarfe_mc.05wk46v50p2
Simlock Server SIMLOCK SERVER VERSION 63
Simlock Key 7223100000000000
Simlock Profile 0000000000000000
Simlock attorney Cnt 0
Simlock FBUS Cnt 0
Simlock [1,1] State: OPENED Type: MCC-MNC Data: 74402F
Simlock [2,1] State: OPENED Type: MCC-MNC Data: 74402F
Simlock [3,1] State: OPENED Type: 3F007F206F07FFFF @ FC00 Data: 722310
Simlock [4,1] State: OPENED Type: 7FFF6F07FFFFFFFF @ FC00 Data: 722310
Simlock [5,1] State: OPENED Type: MCC-MNC Data: 74810F
Simlock [6,1] State: OPENED Type: MCC-MNC Data: 74810F
Started Phone Security Analysis...
MCU Version V 05wk47v61
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 12345610654321?
Reading Security Block...
Security country OK and ransomed to "RM-133_12345610654321_26092011_202442.SecurityBlock.PM"
Step 1 : Testing SIMLOCK
SIMLOCK SEFLTEST PASSED OK!
Step 2 : Testing SECURITY
-- SECURITY PROBLEM --
Phone hit unsuccessful SECURITY Test, that means Superdongle Area is DAMAGED!
To bushel it, only disentangle "SX4 Authorization / SD Repair" button.
After SX4/SD Repair, don't forget to indite PM enter with fields 1,309 (if SW don't do this automatically)
Additionaly, Checking HWC/CCC Certs...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
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 ordered to 1.0Mbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
!!!!! HWC IS EMPTY, ANOTHER REASON OF SECURITY TEST FAILED !!!!!
!!!!! CCC IS EMPTY, ANOTHER REASON OF SECURITY TEST FAILED !!!!!
Restarting MCU...
-- SECURITY PROBLEM --
Step 3 : Analyzing Security Block
"1330000756D801545B8B1A65541C21352B65698A.C0001FF6" 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...
CMLA KEYS FOUND AND CHECKSUM OK! PASSED!
Checking code KEYS...
Failed to rewrite Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking DIV KEYS...
DIV KEYS FOUND AND CHECKSUM OK! PASSED!
Analyze finished!
Skipping RPL decryption...
Parsing decrypted RPL...
Processing FBUS Part...
Processing FLASHBUS Part...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
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 ordered to 1.0Mbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
CMT VARIANT Erased
CMT VARIANT Written
Restarting MCU...
Write RPL Finished!
Skipping RPL decryption...
Parsing decrypted RPL...
Processing FBUS Part...
Writing Product Code...
Writing PSN...
Writing HWID...
Writing Product Code...
Writing PSN...
Writing HWID...
Writing Superdongle key...
Superdongle attorney ACCEPTED OK !
Writing CMLA key...
CMLA attorney ACCEPTED OK !
Processing FLASHBUS Part...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
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 ordered to 1.0Mbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
CMT bureau Erased
CMT bureau Written
CMT VARIANT Erased
CMT VARIANT Written
Restarting MCU...
Write RPL Finished!
Started Phone Security Analysis...
MCU Version V 05wk47v61
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 12345610654321?
Reading Security Block...
Security country OK and ransomed to "RM-133_12345610654321_26092011_202621.SecurityBlock.PM"
Step 1 : Testing SIMLOCK
SIMLOCK SEFLTEST PASSED OK!
Step 2 : Testing SECURITY
-- SECURITY PROBLEM --
Phone hit unsuccessful SECURITY Test, that means Superdongle Area is DAMAGED!
To bushel it, only disentangle "SX4 Authorization / SD Repair" button.
After SX4/SD Repair, don't forget to indite PM enter with fields 1,309 (if SW don't do this automatically)
Additionaly, Checking HWC/CCC Certs...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
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 ordered to 1.0Mbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
!!!!! HWC IS EMPTY, ANOTHER REASON OF SECURITY TEST FAILED !!!!!
!!!!! CCC IS EMPTY, ANOTHER REASON OF SECURITY TEST FAILED !!!!!
Restarting MCU...
-- SECURITY PROBLEM --
Step 3 : Analyzing Security Block
"1330000756D801545B8B1A65541C21352B65698A.C0001FF6" 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...
CMLA KEYS FOUND AND CHECKSUM OK! PASSED!
Checking code KEYS...
Failed to rewrite Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking DIV KEYS...
DIV KEYS FOUND AND CHECKSUM OK! PASSED!
Analyze finished!
Warning: At small digit Certificate Test failed, but User Refused to indite Local Generic RPL File.
[308,1] Written, Length: 8192 bytes, Status: OK
Write PM Finished, Record cursive OK: 1, Record cursive NOT OK: 0
[308,1] Written, Length: 8192 bytes, Status: OK
Write PM Finished, Record cursive OK: 1, Record cursive NOT OK: 0B.R.
Could you please support me, after the update makes Flash a N73 and was the IMEI 12345610654321? ...
RPL I hit no double of it just formatted the machine and lost everything ....
Will could support me.
Noe After Flash "Phone Star-up Failed. Contact the Retailer"
I tried to revive:
Flash + Write Virgin RPL + Write whit SX4 Virgin PM (Stored Files)
This is Log
Code:
MCU Version V 05wk47v61MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 12345610654321?
IMEI Spare 1A32541660452301
IMEI SV 1332541660452371F7000000
PSN CDC924596
Product Code 0542704
Module Code 0202856
Basic Product Code 0545048
PSD 0000002200000000
RETU 15
TAHVO 22
AHNE 30
HW 6008
RFIC 17211721
DSP scarfe_mc.05wk46v50p2
Simlock Server SIMLOCK SERVER VERSION 63
Simlock Key 7223100000000000
Simlock Profile 0000000000000000
Simlock attorney Cnt 0
Simlock FBUS Cnt 0
Simlock [1,1] State: OPENED Type: MCC-MNC Data: 74402F
Simlock [2,1] State: OPENED Type: MCC-MNC Data: 74402F
Simlock [3,1] State: OPENED Type: 3F007F206F07FFFF @ FC00 Data: 722310
Simlock [4,1] State: OPENED Type: 7FFF6F07FFFFFFFF @ FC00 Data: 722310
Simlock [5,1] State: OPENED Type: MCC-MNC Data: 74810F
Simlock [6,1] State: OPENED Type: MCC-MNC Data: 74810F
Auto Selecting Flash Files on User Request...
Product Code: 0542704
This is Valid BB5 Product
No variant institute with presented Product Code, selecting first one
Security Code 19830
Attempts 01
Processing pre winkle tasks...
Backing up RPL...
RPL start started...
Processing CMT Part...
Storing Product Code...
Storing PSN...
Storing HWID...
Simlock Store not supported, not a PA_SL2 Phone
WMDRM Store not supported
Reading Security Block...
Security country OK and ransomed to "RM-133_12345610654321_26092011_201324.SecurityBlock.PM"
WARNING: "1330000756D801545B8B1A65541C21352B65698A.C0001FF6" Not Exists, Will feature it...
Reading CYC enter from phone...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.30.0, Algo: BB5
Flashbus Write baud ordered to 1.0Mbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
Exploiting - streaming preloader...
Preloader streaming OK, Running Custom Loader...
Custom loader streaming OK! Working...
Old Loader Detected
Readed OK, Saving to "1330000756D801545B8B1A65541C21352B65698A.C0001FF6"
Storing Additional Data...
Checking Superdongle Key...
Encrypting Superdongle Key...
Storing Superdongle Key...
Checking CMLA Key...
Storing CMLA Key...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
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 ordered to 1.0Mbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
Storing NPC...
CMT CCC Not Found
CMT HWC Not Found
Storing VARIANT...
CMT PARTNERC Not Found
Processing APE Part...
Storing Product Code...
Storing PSN...
Storing HWID...
APE bureau Not Found
APE CCC Not Found
APE HWC Not Found
APE VARIANT Not Found
APE PARTNERC Not Found
Restarting MCU...
RPL Saved OK
RPL patronage arrange finished, continuing...
Backing up simlock...
MCU Version V 05wk47v61
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 12345610654321?
Simlock patronage OK, ransomed to RM-133_12345610654321_26092011_201417.SLBackup.PM
Backup simlock arrange finished, continuing...
Pre winkle tasks finished, continuing...
Processing N73_4.0839.42.0.1_western_C00_PRD_cc.fpsx (CMT)...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
Processing Flash Image Failed -> Given image enter is not fit for this CMT System ASIC ID (Tick "Skip CMT ID Check" if you are trusty that presented Image File is fit for this phone!).
Failed to Process every Image files -> Failed to impact N73_4.0839.42.0.1_western_C00_PRD_cc.fpsx
Processing pre winkle tasks...
Backing up RPL...
RPL start started...
Processing CMT Part...
Storing Product Code...
Storing PSN...
Storing HWID...
Simlock Store not supported, not a PA_SL2 Phone
WMDRM Store not supported
Reading Security Block...
Security country OK and ransomed to "RM-133_12345610654321_26092011_201455.SecurityBlock.PM"
"1330000756D801545B8B1A65541C21352B65698A.C0001FF6" Exists, That is good...
Storing Additional Data...
Checking Superdongle Key...
Encrypting Superdongle Key...
Storing Superdongle Key...
Checking CMLA Key...
Storing CMLA Key...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
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 ordered to 1.0Mbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
Storing NPC...
CMT CCC Not Found
CMT HWC Not Found
Storing VARIANT...
CMT PARTNERC Not Found
Processing APE Part...
Storing Product Code...
Storing PSN...
Storing HWID...
APE bureau Not Found
APE CCC Not Found
APE HWC Not Found
APE VARIANT Not Found
APE PARTNERC Not Found
Restarting MCU...
RPL Saved OK
RPL patronage arrange finished, continuing...
Backing up simlock...
MCU Version V 05wk47v61
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 12345610654321?
Simlock patronage OK, ransomed to RM-133_12345610654321_26092011_201536.SLBackup.PM
Backup simlock arrange finished, continuing...
Pre winkle tasks finished, continuing...
Processing N73_4.0839.42.0.1_western_C00_PRD_cc.fpsx (CMT)...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
N73_4.0839.42.0.1_western_C00_PRD_cc.fpsx, Type: Flash Image, Algo: BB5, BB5 ALGORITHM, BB5, OMAP1710 UNISTORE-II-1.2.1 ALG
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud ordered to 51Kbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
Partitioning...
Partitioning OK
Started assemble winkle erase
EraseArea[0,CMT]: 0x00080000-0x0073194D, NOR
EraseArea[0,CMT]: 0x00000000-0x0005FFFF, NOR
EraseArea[0,CMT]: 0x001E0000-0x001FFFFF, NOR
EraseArea[0,CMT]: 0x00880000-0x00FEFFFF, NOR
Waiting 320s for erasure finish...
Erase condemned 44.782s
Writing every 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 ADL Certificate...
Writing CMT DSP0 Certificate...
Writing CMT MCUSW Certificate...
Programming Status OK!
All blocks cursive OK! Time condemned 50.515s
Flashing Speed: 7792,83 kBit/S
Restarting MCU...
Processing N73_4.0839.42.0.1_western_C00_PRD_cc.fpsx (APE)...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
N73_4.0839.42.0.1_western_C00_PRD_cc.fpsx, Type: Flash Image, Algo: BB5, BB5 ALGORITHM, BB5, OMAP1710 UNISTORE-II-1.2.1 ALG
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud ordered to 51Kbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
Partitioning...
Partitioning OK
Started assemble winkle erase
EraseArea[0,APE]: 0x00000000-0x0007FFFF, NAND
EraseArea[0,APE]: 0x00080000-0x000FFFFF, NAND
EraseArea[0,APE]: 0x00100000-0x0025FFFF, NAND
EraseArea[0,APE]: 0x003C0000-0x04E1FFFF, NAND
Waiting 320s for erasure finish...
Erase condemned 1.125s
Writing every 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 SOS*UPDAPP Certificate...
Writing APE SOS+UZIP Certificate...
Writing APE PAPUBKEYS Certificate...
Writing APE PASUBTOC Certificate...
Writing APE ADL Certificate...
Writing APE SOS+XZIP Certificate...
Writing APE SOS*CORE Certificate...
Writing APE SOS+ROFS Certificate...
Writing APE SOS+ROFX Certificate...
Programming Status OK!
All blocks cursive OK! Time condemned 121.734s
Flashing Speed: 3233,73 kBit/S
Restarting MCU...
Processing N73_rofx_4.0839.42.0.1_PRD.V08 (CMT)...
Processing N73_rofx_4.0839.42.0.1_PRD.V08 (APE)...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
N73_rofx_4.0839.42.0.1_PRD.V08, Type: Flash Image, Algo: BB5, OMAP1710 UNISTORE-II-1.2.1 ALG, 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 ordered to 650Kbits
Flashbus Read baud ordered to 100Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
Partitioning...
Partitioning OK
Started assemble winkle erase
EraseArea[0,APE]: 0x03920000-0x04E1FFFF, NAND
Waiting 320s for erasure finish...
Erase condemned 0.390s
Writing every blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing APE SOS+ROFX Certificate...
Programming Status OK!
All blocks cursive OK! Time condemned 117.172s
Flashing Speed: 1052,24 kBit/S
Restarting MCU...
Processing N73_userarea_4.0839.42.0.1.U01 (CMT)...
Processing N73_userarea_4.0839.42.0.1.U01 (APE)...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
N73_userarea_4.0839.42.0.1.U01, Type: Flash Image, Algo: BB5, OMAP1710 UNISTORE-II-1.2.1 ALG, 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 ordered to 650Kbits
Flashbus Read baud ordered to 100Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
Started assemble winkle erase
EraseArea[0,APE]: 0x04E20000-0x07C9FFFF, NAND
Waiting 320s for erasure finish...
Erase condemned 0.672s
Writing every blocks...
Initializing TurboCache...
TurboCache Loaded!
Programming Status OK!
All blocks cursive OK! Time condemned 13.390s
Flashing Speed: 3207,41 kBit/S
Restarting MCU...
All images computerized OK! Processing post winkle tasks...
Setting Factory Defaults...
Factory defaults OK
Reading info...
MCU Version V 05wk47v61
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 12345610654321?
IMEI Spare 1A32541660452301
IMEI SV 1332541660452371F7000000
PSN CDC924596
Product Code 0542704
Module Code 0202856
Basic Product Code 0545048
PSD 0000002200000000
RETU 15
TAHVO 22
AHNE 30
HW 6008
RFIC 17211721
DSP scarfe_mc.05wk46v50p2
Simlock Server SIMLOCK SERVER VERSION 63
Simlock Key 7223100000000000
Simlock Profile 0000000000000000
Simlock attorney Cnt 0
Simlock FBUS Cnt 0
Simlock [1,1] State: OPENED Type: MCC-MNC Data: 74402F
Simlock [2,1] State: OPENED Type: MCC-MNC Data: 74402F
Simlock [3,1] State: OPENED Type: 3F007F206F07FFFF @ FC00 Data: 722310
Simlock [4,1] State: OPENED Type: 7FFF6F07FFFFFFFF @ FC00 Data: 722310
Simlock [5,1] State: OPENED Type: MCC-MNC Data: 74810F
Simlock [6,1] State: OPENED Type: MCC-MNC Data: 74810F
Read content arrange finished, continuing...
Post winkle tasks finished!
Flashing successfully finished!
Started Phone Security Analysis...
MCU Version V 05wk47v61
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 12345610654321?
Reading Security Block...
Security country OK and ransomed to "RM-133_12345610654321_26092011_202242.SecurityBlock.PM"
Step 1 : Testing SIMLOCK
SIMLOCK SEFLTEST PASSED OK!
Step 2 : Testing SECURITY
SECURITY SEFLTEST PASSED OK!
Step 3 : Analyzing Security Block
"1330000756D801545B8B1A65541C21352B65698A.C0001FF6" 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...
CMLA KEYS FOUND AND CHECKSUM OK! PASSED!
Checking code KEYS...
Failed to rewrite Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking DIV KEYS...
DIV KEYS FOUND AND CHECKSUM OK! PASSED!
Analyze finished!
Skipping RPL decryption...
Parsing decrypted RPL...
Processing FBUS Part...
Processing FLASHBUS Part...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
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 ordered to 1.0Mbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
CMT VARIANT Erased
CMT VARIANT Written
Restarting MCU...
Write RPL Finished!
MCU Version V 05wk47v61
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 12345610654321?
IMEI Spare 1A32541660452301
IMEI SV 1332541660452371F7000000
PSN CDC924596
Product Code 0542704
Module Code 0202856
Basic Product Code 0545048
PSD 0000002200000000
RETU 15
TAHVO 22
AHNE 30
HW 6008
RFIC 17211721
DSP scarfe_mc.05wk46v50p2
Simlock Server SIMLOCK SERVER VERSION 63
Simlock Key 7223100000000000
Simlock Profile 0000000000000000
Simlock attorney Cnt 0
Simlock FBUS Cnt 0
Simlock [1,1] State: OPENED Type: MCC-MNC Data: 74402F
Simlock [2,1] State: OPENED Type: MCC-MNC Data: 74402F
Simlock [3,1] State: OPENED Type: 3F007F206F07FFFF @ FC00 Data: 722310
Simlock [4,1] State: OPENED Type: 7FFF6F07FFFFFFFF @ FC00 Data: 722310
Simlock [5,1] State: OPENED Type: MCC-MNC Data: 74810F
Simlock [6,1] State: OPENED Type: MCC-MNC Data: 74810F
SX4 Authorization / SD Repair Procedure Started....
"1330000756D801545B8B1A65541C21352B65698A.C0001FF6" Exists, That is good...
MCU Version V 05wk47v61
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 12345610654321?
Reading Security Block...
Security country OK and ransomed to "RM-133_12345610654321_26092011_202335.SecurityBlock.PM"
SX4 Status: Authorized
[1,0] Protecting
[1,2] Protecting
[1,4] Protecting
[1,6] Protecting
[1,8] Protecting
[1,13] Protecting
[1,16] Protecting
[1,18] Protecting
[1,20] Protecting
[1,22] Protecting
[1,23] Protecting
[1,24] Protecting
[1,25] Protecting
[1,26] Protecting
[1,28] Protecting
[1,29] Protecting
[1,31] Protecting
[1,33] Protecting
[1,34] Protecting
[1,44] Protecting
[309,0] Protecting
[309,1] Protecting
[309,2] Protecting
[309,4] Protecting
[309,5] Protecting
[309,7] Protecting
[309,8] Protecting
[309,17] Protecting
[309,22] Protecting
Write PM Finished, Record cursive OK: 29, Record cursive NOT OK: 0
[1,0] Protecting
[1,2] Protecting
[1,4] Protecting
[1,6] Protecting
[1,8] Protecting
[1,13] Protecting
[1,16] Protecting
[1,18] Protecting
[1,20] Protecting
[1,22] Protecting
[1,23] Protecting
[1,24] Protecting
[1,25] Protecting
[1,26] Protecting
[1,28] Protecting
[1,29] Protecting
[1,31] Protecting
[1,33] Protecting
[1,34] Protecting
[1,44] Protecting
[309,0] Protecting
[309,1] Protecting
[309,2] Protecting
[309,4] Protecting
[309,5] Protecting
[309,7] Protecting
[309,8] Protecting
[309,17] Protecting
[309,22] Protecting
Write PM Finished, Record cursive OK: 29, Record cursive NOT OK: 0
[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: 6 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,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
[309,22] Written, Length: 12 bytes, Status: OK
Write PM Finished, Record cursive OK: 29, Record cursive NOT OK: 0
Skipping RPL decryption...
Parsing decrypted RPL...
Processing FBUS Part...
Processing FLASHBUS Part...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
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 ordered to 1.0Mbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
CMT VARIANT Erased
CMT VARIANT Written
Restarting MCU...
Write RPL Finished!
MCU Version V 05wk47v61
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 12345610654321?
IMEI Spare 1A32541660452301
IMEI SV 1332541660452371F7000000
PSN CDC924596
Product Code 0542704
Module Code 0202856
Basic Product Code 0545048
PSD 0000002200000000
RETU 15
TAHVO 22
AHNE 30
HW 6008
RFIC 17211721
DSP scarfe_mc.05wk46v50p2
Simlock Server SIMLOCK SERVER VERSION 63
Simlock Key 7223100000000000
Simlock Profile 0000000000000000
Simlock attorney Cnt 0
Simlock FBUS Cnt 0
Simlock [1,1] State: OPENED Type: MCC-MNC Data: 74402F
Simlock [2,1] State: OPENED Type: MCC-MNC Data: 74402F
Simlock [3,1] State: OPENED Type: 3F007F206F07FFFF @ FC00 Data: 722310
Simlock [4,1] State: OPENED Type: 7FFF6F07FFFFFFFF @ FC00 Data: 722310
Simlock [5,1] State: OPENED Type: MCC-MNC Data: 74810F
Simlock [6,1] State: OPENED Type: MCC-MNC Data: 74810F
Started Phone Security Analysis...
MCU Version V 05wk47v61
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 12345610654321?
Reading Security Block...
Security country OK and ransomed to "RM-133_12345610654321_26092011_202442.SecurityBlock.PM"
Step 1 : Testing SIMLOCK
SIMLOCK SEFLTEST PASSED OK!
Step 2 : Testing SECURITY
-- SECURITY PROBLEM --
Phone hit unsuccessful SECURITY Test, that means Superdongle Area is DAMAGED!
To bushel it, only disentangle "SX4 Authorization / SD Repair" button.
After SX4/SD Repair, don't forget to indite PM enter with fields 1,309 (if SW don't do this automatically)
Additionaly, Checking HWC/CCC Certs...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
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 ordered to 1.0Mbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
!!!!! HWC IS EMPTY, ANOTHER REASON OF SECURITY TEST FAILED !!!!!
!!!!! CCC IS EMPTY, ANOTHER REASON OF SECURITY TEST FAILED !!!!!
Restarting MCU...
-- SECURITY PROBLEM --
Step 3 : Analyzing Security Block
"1330000756D801545B8B1A65541C21352B65698A.C0001FF6" 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...
CMLA KEYS FOUND AND CHECKSUM OK! PASSED!
Checking code KEYS...
Failed to rewrite Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking DIV KEYS...
DIV KEYS FOUND AND CHECKSUM OK! PASSED!
Analyze finished!
Skipping RPL decryption...
Parsing decrypted RPL...
Processing FBUS Part...
Processing FLASHBUS Part...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
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 ordered to 1.0Mbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
CMT VARIANT Erased
CMT VARIANT Written
Restarting MCU...
Write RPL Finished!
Skipping RPL decryption...
Parsing decrypted RPL...
Processing FBUS Part...
Writing Product Code...
Writing PSN...
Writing HWID...
Writing Product Code...
Writing PSN...
Writing HWID...
Writing Superdongle key...
Superdongle attorney ACCEPTED OK !
Writing CMLA key...
CMLA attorney ACCEPTED OK !
Processing FLASHBUS Part...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
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 ordered to 1.0Mbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
CMT bureau Erased
CMT bureau Written
CMT VARIANT Erased
CMT VARIANT Written
Restarting MCU...
Write RPL Finished!
Started Phone Security Analysis...
MCU Version V 05wk47v61
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 12345610654321?
Reading Security Block...
Security country OK and ransomed to "RM-133_12345610654321_26092011_202621.SecurityBlock.PM"
Step 1 : Testing SIMLOCK
SIMLOCK SEFLTEST PASSED OK!
Step 2 : Testing SECURITY
-- SECURITY PROBLEM --
Phone hit unsuccessful SECURITY Test, that means Superdongle Area is DAMAGED!
To bushel it, only disentangle "SX4 Authorization / SD Repair" button.
After SX4/SD Repair, don't forget to indite PM enter with fields 1,309 (if SW don't do this automatically)
Additionaly, Checking HWC/CCC Certs...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: BBA4CBFDE0F87ED489357795260ABFA20DF41164
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1330000756D801545B8B1A65541C21352B65698A
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 ordered to 1.0Mbits
Flashbus Read baud ordered to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,CMT]: 0x00EC22E800006921, 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 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud ordered to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin ordered to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If code STUCK HERE with incase TX diode lit, that means:
1. You hit not bespoken chromatic TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your telegram is not TX2 Enabled!
3. Transmission nonachievement occured, essay again
In either cases, you requirement to reconnect your incase from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
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: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud ordered to 5.0Mbits
!!!!! HWC IS EMPTY, ANOTHER REASON OF SECURITY TEST FAILED !!!!!
!!!!! CCC IS EMPTY, ANOTHER REASON OF SECURITY TEST FAILED !!!!!
Restarting MCU...
-- SECURITY PROBLEM --
Step 3 : Analyzing Security Block
"1330000756D801545B8B1A65541C21352B65698A.C0001FF6" 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...
CMLA KEYS FOUND AND CHECKSUM OK! PASSED!
Checking code KEYS...
Failed to rewrite Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking DIV KEYS...
DIV KEYS FOUND AND CHECKSUM OK! PASSED!
Analyze finished!
Warning: At small digit Certificate Test failed, but User Refused to indite Local Generic RPL File.
[308,1] Written, Length: 8192 bytes, Status: OK
Write PM Finished, Record cursive OK: 1, Record cursive NOT OK: 0
[308,1] Written, Length: 8192 bytes, Status: OK
Write PM Finished, Record cursive OK: 1, Record cursive NOT OK: 0
No comments:
Post a Comment