|
Welcome to the GSM-Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. Only registered members may post questions, contact other members or search our database of over 8 million posts. Registration is fast, simple and absolutely free so please - Click to REGISTER! If you have any problems with the registration process or your account login, please contact contact us . |
|
Register | FAQ | Donate | Forum Rules | Root any Device | ★iPhone Unlock★ | ★ Direct Codes ★ | Direct Unlock Source |
| LinkBack | Thread Tools | Display Modes |
09-27-2011, 01:38 | #1 (permalink) |
No Life Poster Join Date: Jun 2009 Location: Paraguay
Posts: 778
Member: 1064967 Status: Offline Thanks Meter: 131 | Cant Help me Please N73 Imei 12345610654321? Could you please help me, after the update makes Flash a N73 and was the IMEI 12345610654321? ... RPL I have no copy of it just formatted the computer and lost everything .... Will could help 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 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 Key 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 found with given Product Code, selecting first one Security Code 19830 Attempts 01 Processing pre flash tasks... Backing up RPL... RPL Creation 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 block OK and saved to "RM-133_12345610654321_26092011_201324.SecurityBlock.PM" WARNING: "1330000756D801545B8B1A65541C21352B65698A.C0001FF6" Not Exists, Will read it... Reading CYC file 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 set to 1.0Mbits Flashbus Read baud set to 98Kbits Using OLD BB5 FLASHING PROTOCOL Exploiting - running preloader... Preloader running OK, Running Custom Loader... Custom loader running 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 set to 1.0Mbits Flashbus Read baud set to 98Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 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 set to 2.0Mbits Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: DualLine 32Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: DualLine 32Bit 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 set 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 NPC Not Found APE CCC Not Found APE HWC Not Found APE VARIANT Not Found APE PARTNERC Not Found Restarting MCU... RPL Saved OK RPL backup thread 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 backup OK, saved to RM-133_12345610654321_26092011_201417.SLBackup.PM Backup simlock thread finished, continuing... Pre flash 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 file is not suitable for this CMT System ASIC ID (Tick "Skip CMT ID Check" if you are sure that given Image File is suitable for this phone!). Failed to Process all Image files -> Failed to process N73_4.0839.42.0.1_western_C00_PRD_cc.fpsx Processing pre flash tasks... Backing up RPL... RPL Creation 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 block OK and saved 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 set to 1.0Mbits Flashbus Read baud set to 98Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 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 set to 2.0Mbits Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: DualLine 32Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: DualLine 32Bit 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 set 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 NPC Not Found APE CCC Not Found APE HWC Not Found APE VARIANT Not Found APE PARTNERC Not Found Restarting MCU... RPL Saved OK RPL backup thread 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 backup OK, saved to RM-133_12345610654321_26092011_201536.SLBackup.PM Backup simlock thread finished, continuing... Pre flash 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 set to 51Kbits Flashbus Read baud set to 98Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 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 set to 2.0Mbits Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Flashbus Write baud set to 5.0Mbits Partitioning... Partitioning OK Started group flash 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 taken 44.782s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT NOLO Certificate... Writing CMT KEYS Certificate... Writing CMT PRIMAPP Certificate... Writing CMT PASUBTOC Certificate... Writing CMT PAPUBKEYS Certificate... Writing CMT UPDAPP Certificate... Writing CMT ADL Certificate... Writing CMT DSP0 Certificate... Writing CMT MCUSW Certificate... Programming Status OK! All blocks written OK! Time taken 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 set to 51Kbits Flashbus Read baud set to 98Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 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 set to 2.0Mbits Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: DualLine 32Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: DualLine 32Bit 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 set to 5.0Mbits Partitioning... Partitioning OK Started group flash 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 taken 1.125s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing APE KEYS Certificate... Writing APE X-LOADER Certificate... Writing APE PRIMAPP Certificate... Writing APE SOS+LOADER Certificate... Writing APE 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 written OK! Time taken 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 set to 650Kbits Flashbus Read baud set to 100Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 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 set to 2.0Mbits Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: DualLine 32Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: DualLine 32Bit 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 set to 5.0Mbits Partitioning... Partitioning OK Started group flash erase EraseArea[0,APE]: 0x03920000-0x04E1FFFF, NAND Waiting 320s for erasure finish... Erase taken 0.390s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing APE SOS+ROFX Certificate... Programming Status OK! All blocks written OK! Time taken 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 set to 650Kbits Flashbus Read baud set to 100Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 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 set to 2.0Mbits Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: DualLine 32Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: DualLine 32Bit 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 set to 5.0Mbits Started group flash erase EraseArea[0,APE]: 0x04E20000-0x07C9FFFF, NAND Waiting 320s for erasure finish... Erase taken 0.672s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Programming Status OK! All blocks written OK! Time taken 13.390s Flashing Speed: 3207,41 kBit/S Restarting MCU... All images processed OK! Processing post flash 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 Key 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 info thread finished, continuing... Post flash 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 block OK and saved 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 ECC KEYS... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Checking DIV KEYS... DIV KEYS FOUND AND CHECKSUM OK! PASSED! Analyze finished! 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 set to 1.0Mbits Flashbus Read baud set to 98Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 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 set to 2.0Mbits Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: DualLine 32Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: DualLine 32Bit 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 set 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 Key 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 block OK and saved 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 written OK: 29, Record written 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 written OK: 29, Record written 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 written OK: 29, Record written 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 set to 1.0Mbits Flashbus Read baud set to 98Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 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 set to 2.0Mbits Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: DualLine 32Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: DualLine 32Bit 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 set 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 Key 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 block OK and saved to "RM-133_12345610654321_26092011_202442.SecurityBlock.PM" Step 1 : Testing SIMLOCK SIMLOCK SEFLTEST PASSED OK! Step 2 : Testing SECURITY -- SECURITY PROBLEM -- Phone have failed SECURITY Test, that means Superdongle Area is DAMAGED! To repair it, simply slick "SX4 Authorization / SD Repair" button. After SX4/SD Repair, don't forget to write PM file with fields 1,309 (if SW don't do this automatically) Additionaly, Checking HWC/CCC Certs... Booting CMT... 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 set to 1.0Mbits Flashbus Read baud set to 98Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 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 set to 2.0Mbits Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: DualLine 32Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: DualLine 32Bit 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 set 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 ECC KEYS... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Checking DIV KEYS... DIV KEYS FOUND AND CHECKSUM OK! PASSED! Analyze finished! 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 set to 1.0Mbits Flashbus Read baud set to 98Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 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 set to 2.0Mbits Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: DualLine 32Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: DualLine 32Bit 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 set 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 Key ACCEPTED OK ! Writing CMLA key... CMLA Key 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 set to 1.0Mbits Flashbus Read baud set to 98Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 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 set to 2.0Mbits Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: DualLine 32Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: DualLine 32Bit 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 set to 5.0Mbits CMT NPC Erased CMT NPC 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 block OK and saved to "RM-133_12345610654321_26092011_202621.SecurityBlock.PM" Step 1 : Testing SIMLOCK SIMLOCK SEFLTEST PASSED OK! Step 2 : Testing SECURITY -- SECURITY PROBLEM -- Phone have failed SECURITY Test, that means Superdongle Area is DAMAGED! To repair it, simply slick "SX4 Authorization / SD Repair" button. After SX4/SD Repair, don't forget to write PM file with fields 1,309 (if SW don't do this automatically) Additionaly, Checking HWC/CCC Certs... Booting CMT... 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 set to 1.0Mbits Flashbus Read baud set to 98Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 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 set to 2.0Mbits Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: DualLine 32Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: DualLine 32Bit 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 set 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 ECC KEYS... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Checking DIV KEYS... DIV KEYS FOUND AND CHECKSUM OK! PASSED! Analyze finished! Warning: At least one Certificate Test failed, but User Refused to write Local Generic RPL File. [308,1] Written, Length: 8192 bytes, Status: OK Write PM Finished, Record written OK: 1, Record written NOT OK: 0 [308,1] Written, Length: 8192 bytes, Status: OK Write PM Finished, Record written OK: 1, Record written NOT OK: 0 |
09-27-2011, 02:17 | #2 (permalink) | |
Freak Poster Join Date: Feb 2008 Location: MON-KEY is the BEST NOKIA TOOL
Posts: 264
Member: 704498 Status: Offline Thanks Meter: 51 | If you hav backup rpl... Write it... If dont! You need rpl services Quote:
| |
09-27-2011, 06:54 | #4 (permalink) |
No Life Poster Join Date: Jan 2009 Location: England Age: 59
Posts: 17,681
Member: 947561 Status: Offline Thanks Meter: 14,053 | Try the function autorecovery imei/npc may be you are lucky and have an autoback-up BR Alex |
The Following User Says Thank You to moulnisky For This Useful Post: |
09-27-2011, 15:45 | #5 (permalink) |
No Life Poster Join Date: Jun 2009 Location: Paraguay
Posts: 778
Member: 1064967 Status: Offline Thanks Meter: 131 | Hi Alex Thanks for you time. The truth now I'm going to try a Full Erase Flash .... I have no hope to solve this Fono back then: Saturday after upgrading my machine works with the N73 ... Full Flash Ok Supposedly, in the amount of work and had no control if the Imei Ok, just Turn On and deliver. Domingo Formatting my computer really was too slow ... Monday N73 irate customer who is restarted, Off, Sometimes you do not call ... Today, worried about possibly having to replace a new phone ... B.R. |
09-27-2011, 15:51 | #6 (permalink) | |
No Life Poster Join Date: Jan 2009 Location: England Age: 59
Posts: 17,681
Member: 947561 Status: Offline Thanks Meter: 14,053 | Quote:
I keep all the RPL back-ups I did in my life just cos ofter a mobile can come back for fixing BR Alex | |
09-28-2011, 11:08 | #7 (permalink) | |
No Life Poster Join Date: Sep 2009
Posts: 1,311
Member: 1128573 Status: Offline Thanks Meter: 242 | Quote:
we founded daily, 2700c, 5130c, 3110c, 2690, 2730, phone IMEI is 123456.............? you know, how much this phone price and RPL price for each phone. so, how can we buy new RPL ? it's better buy a new phone for customer. others problem is SL DATA CORRUPTED, need new RPL. every day we founded this problem. but sorry, we can't repair. we belived it's all possible next coming day, when ????? this is indifinte. i give to one nice example, 5/6 years ago, we flash phone 1100, 1600, we founded IMEI is ????????????????4. we reply to costomer not possible. then next story we know everybody. Yes Boss, we are waiting, waiting for touch new RPL. thnaks with best regards, mahir | |
Bookmarks |
| |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
HELP!!! BACKGROUND SCREEN LOGO | Michael Go | Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) | 8 | 11-23-2017 08:11 |
my 8810 is phone locked ,can somebody please help | duyphuc | Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) | 18 | 12-23-2014 09:03 |
Eeprom dump lost, help needed. | CAMILO | Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) | 6 | 11-29-2010 19:04 |
Help with 6110 | paulomt1 | Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) | 2 | 05-25-2009 16:29 |
Winlock 1.10 - Help | rdmfs | Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) | 3 | 06-25-1999 08:21 |
|