 |
 |
 |
|
|
|
|||||||
| RPL Nokia BB5 и DCT4 Помощь по записи RPL, поддержка пользователей. |
 |
|
|
Опции темы | Поиск в этой теме |
01.12.2011, 14:22
|
#1 |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21  |
N79 не могу записать RPL
Всем привет. Вкратце тел принесли именно на восстановление сертификатов, rpl готов, пытаюсь влить - нифига. Superdongle не ремонтируется, SX4 не проходит.
Скрытый текстMXKEY [FT SCR2000 0], SN: C08192DF
Using device: HTI, FW ver: 00.24, SN: 00005ACF Connection status: OHCI:HUB:USB 2.00 (Full-speed) Driver: WinUSB, ver: 3.5.0.0 Module ver: 1.0.0.19045(08-10-2011), Library ver: 1.0.0.12920(08-10-2011) CMT Data : SYSTEM ASIC ID: 000000010000022600010006400C192101021103 [RAPIDO3G ver: 1.11] EM0 ID: 00000295 EM1 ID: 00000B22 PUBLIC ID: 146000112A650052CF5A1A498A81FA9F9245546F ASIC MODE ID: 00 ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE ROM ID: A8C1D6713E691FF8 SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 11.24.0 revision: 2.0 size: 0x3B80 Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105 eBB5ProtocolType: NEW TransmissionMode: DDR&TX2 Storage0: 0000 0000 - 0000 0000 type: RAM, asic:CMT Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT Storage2: 0400 0000 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT Storage3: 0000 0001 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT Storage4: 00EC 0040 - 0000 0121 [Samsung 2Gb DDP OneNAND,2 Gbits] type: FLASH,MuxOneNAND, asic:CMT Suggested algorithm: XSR 1.5 Algorithm: RAPIDOv11_XSR15_alg.fg [XSR 1.5] version: 11.24.0 revision: 2.0 size: 0x87D1A Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105 TransmissionMode: DDR&TX2 FUR: Adding Asic CMT as client OK CMT PAPUBKEYS HASH: B2075F4B793BB9017C8C0097C783C543F2A6A303 Original Imei: 35638xxxxxxxxx Original Product code: 0565702 Bluetooth ID: 0025CFD58B2A WLAN ID: 0025CFD6758A SIMLOCK PA identifier: [0] PA_SL2 Phone type: RM-348 (Nokia N79) SW version: V ICPR72_09w18.4 14-10-09 RM-348 (c) Nokia Imei plain: 12345610654321-? Product code: 0565724 Battery voltage: 4742 mV, current: 0 mA ApeCoreSw: 32.001 Language Pack: - not available. SIMLOCK invalid! SUPERDONGLE_KEY seems to be valid CMLA_KEY seems to be valid WMDRM_PD seems to be valid SIMLOCK_TEST passed SECURITY_TEST failed! warning: phone version(32.001) outdated, latest version on server is: 31.002 Imei plain is invalid !!! SIMLOCK_DATA corrupted! SIMLOCK_DATA corrupted! Scanning local SX4 Card ... No SX4 Card found. SERVER->Served by MXKEY - BLADE X at host2, agent version 1.1 revision 0.9 Authenticating using security server ... Connecting to server[main.mxkey.biz] ...MXKEY SX4CARD - ID, hello 85.173.248.246 Bad phones ack, probably SUPERDONGLE_KEY corrupted ! Wrong response to SD verify request Retrying ... SERVER->Served by MXKEY - BLADE X at host2, agent version 1.1 revision 0.9 Authenticating using security server ... Connecting to server[main.mxkey.biz] ...MXKEY SX4CARD - ID, hello 85.173.248.246 Bad phones ack, probably SUPERDONGLE_KEY corrupted ! Wrong response to SD verify request Retrying ... SERVER->Served by MXKEY - BLADE X at host2, agent version 1.1 revision 0.9 Authenticating using [MX] security server ... Connecting to server[main.mxkey.biz] ...MXKEY SX4CARD - ID, hello 85.173.248.246 SUPERDONGLE get challenge failed ! Попытка циклоном это же сделать вроде получилась Скрытый текстBooting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Boot skipped on user request Flashbus Write baud set to 5.0Mbits Restarting MCU... Skipping RPL decryption... Parsing decrypted RPL... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock ACCEPTED OK ! Writing Superdongle key... Superdongle Key ACCEPTED OK ! Writing CMLA key... CMLA Key NOT ACCEPTED ! Writing WMDRM PD Data... WMDRM PD Data NOT ACCEPTED ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Write RPL Finished! SX4 Authorization / SD Repair Procedure Started.... WARNING: "146000112A650052CF5A1A498A81FA9F9245546F.C0000CC9" Not Exists, Will read it... Reading CYC file from phone... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! New_RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.16.0, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Sending Auxiliary Loader... Auxiliary Loader Sent! 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. Loader: RAPxx CommonBoot v1.06 (C) 2011 KarwosLabs Custom loader running OK! Working... Readed OK, Saving to "146000112A650052CF5A1A498A81FA9F9245546F.C0000CC9" MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 12345610654321? Reading Security Block... Security block OK and saved to "RM-348_12345610654321_01.12.2011_153045.SecurityBlock.PM" SX4 Status: Not authorized (74) Started mutual authenthication with card... Receiving Phone Seed 1... Phone Seed 1 Received Sending calculated Data 1, and expecting Seed 2... Calculated Data 1 accepted, Phone Seed 2 Received Superdongle Key is probably CORRUPTED, Writing custom keys... Received SD Keys from box, writing to phone... Failed to Repair Superdongle Key (Superdongle Key NOT ACCEPTED !), Will use Server and Original Card SX4 Status: Not authorized (74) Started mutual authenthication with card... Cyclone Server (1.0.0.677), Cyclone Box Team 2008-2011 - Ready. Receiving Phone Seed 1... Phone Seed 1 Received Sending calculated Data 1, and expecting Seed 2... Calculated Data 1 accepted, Phone Seed 2 Received Disconnected from Cyclone Server Failed to Authorize SX4 -> Failed to receive mutual Data 2 from server SX4 Authorization / SD Repair Procedure Started.... Failed to obtain Phone Unique Data, Will use Server and Original Card MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 12345610654321? SX4 Status: Not authorized (74) Started mutual authenthication with card... Cyclone Server (1.0.0.677), Cyclone Box Team 2008-2011 - Ready. Receiving Phone Seed 1... Phone Seed 1 Received Sending calculated Data 1, and expecting Seed 2... Calculated Data 1 accepted, Phone Seed 2 Received Disconnected from Cyclone Server Failed to Authorize SX4 -> Failed to receive mutual Data 2 from server SX4 Authorization / SD Repair Procedure Started.... Failed to obtain Phone Unique Data, Will use Server and Original Card MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 12345610654321? SX4 Status: Not authorized (74) Started mutual authenthication with card... Cyclone Server (1.0.0.677), Cyclone Box Team 2008-2011 - Ready. Receiving Phone Seed 1... Phone Seed 1 Received Sending calculated Data 1, and expecting Seed 2... Calculated Data 1 accepted, Phone Seed 2 Received Disconnected from Cyclone Server Failed to Authorize SX4 -> Failed to receive mutual Data 2 from server Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits Erasing flash chip... Started group flash erase EraseArea[0,CMT]: 0x00000000-0x0FFFFFFF, ONENAND Waiting 640s for erasure finish... Erase taken 1.344s Restarting MCU... BB5 Full Erase Finished! Scanning avaiable products... Processing C:\Program Files\Nokia\Phoenix\Products\... Found 55 products, Filtering BB5 Products - wait... 24 Products left after filtering. Ready. Retrieving Variants for Product RM-348 - wait... 1 Variants Retrieved Processing pre flash tasks... Pre flash tasks finished, continuing... Processing RM-348_32.001_prd.core.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-348_32.001_prd.core.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0xFFFFFFFF00000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled Warning: PAPUBKEYS Hash Missing! Flashbus Write baud set to 5.0Mbits Sending Certificates... Certificates OK Partitioning... Partitioning OK Started group flash erase EraseArea[0,CMT]: 0x00040000-0x00082FFF, ONENAND EraseArea[0,CMT]: 0x00083400-0x003FFFFF, ONENAND EraseArea[0,CMT]: 0x00800000-0x00D5FFFF, ONENAND EraseArea[0,CMT]: 0x00D60000-0x0A95FFFF, ONENAND Erase Partition (CMT) Waiting 320s for erasure finish... Erase taken 1.0s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT ADA Certificate... Writing CMT KEYS Certificate... Writing CMT PRIMAPP Certificate... Writing CMT RAP3NAND Certificate... Writing CMT PASUBTOC Certificate... WARNING: CMT PAPUBKEYS Hash is Empty, writing first found PAPUBKEYS Writing CMT PAPUBKEYS Certificate... Writing CMT SOS*UPDAPP Certificate... Writing CMT SOS*DSP0 Certificate... Writing CMT SOS*ISASW Certificate... Writing CMT SOS+CORE Certificate... Writing CMT SOS+ROFS1 Certificate... Programming Status OK! All blocks written OK! Time taken 115.984s Flashing Speed: 7490,39 kBit/S Restarting MCU... Processing RM-348_32.001_prd.core.fpsx (APE)... Processing RM-348_32.001_005_prd.language.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-348_32.001_005_prd.language.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x08260000-0x09F5FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.156s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS+ROFS2 Certificate... Programming Status OK! All blocks written OK! Time taken 27.328s Flashing Speed: 7384,20 kBit/S Restarting MCU... Processing RM-348_32.001_005_prd.language.fpsx (APE)... Processing RM-348_32.001_53.1_prd.customer.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-348_32.001_53.1_prd.customer.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x09F60000-0x0A95FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.62s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS+ROFS3 Certificate... Programming Status OK! All blocks written OK! Time taken 0.78s Flashing Speed: 836,31 kBit/S Restarting MCU... Processing RM-348_32.001_53.1_prd.customer.fpsx (APE)... Processing RM-348_32.001_003_000_U001.uda.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-348_32.001_003_000_U001.uda.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x0A960000-0x0F71FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.406s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Programming Status OK! All blocks written OK! Time taken 19.188s Flashing Speed: 6985,24 kBit/S Restarting MCU... Processing RM-348_32.001_003_000_U001.uda.fpsx (APE)... Processing vivien_eno_imaker_ape_only.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! vivien_eno_imaker_ape_only.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 Flashbus Write baud set to 5.0Mbits Sending Certificates... Certificates OK Started group flash erase EraseArea[0,CMT]: 0x00400000-0x007FFFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.16s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS*ENO Certificate... Programming Status OK! All blocks written OK! Time taken 2.984s Flashing Speed: 7278,37 kBit/S Restarting MCU... Processing vivien_eno_imaker_ape_only.fpsx (APE)... All images processed OK! Processing post flash tasks... Setting Factory Defaults... Factory defaults OK Reading info... MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 12345610654321? IMEI Spare 1A32541660452301 IMEI SV 1332541660452311F2000000 PSN 0 PSD 0000000000000000 LPSN 0 RETU 15 TAHVO 22 AHNE 11 RFIC 17141715 DSP astro_ICPR72_09w17 Failed to read info -> Failed to read SP info Read info thread finished, continuing... Post flash tasks finished! Flashing successfully finished! Skipping RPL decryption... Parsing decrypted RPL... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock NOT ACCEPTED ! Writing Superdongle key... Superdongle Key ACCEPTED OK ! Writing CMLA key... CMLA Key NOT ACCEPTED ! Writing WMDRM PD Data... WMDRM PD Data NOT ACCEPTED ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock ACCEPTED OK ! Writing Superdongle key... Superdongle Key ACCEPTED OK ! Writing CMLA key... CMLA Key NOT ACCEPTED ! Writing WMDRM PD Data... WMDRM PD Data NOT ACCEPTED ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Write RPL Finished! SX4 Authorization / SD Repair Procedure Started.... Failed to obtain Phone Unique Data, Will use Server and Original Card MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356387xxxxxxxxx Mastercode 737507162 SX4 Status: Not authorized (74) Started mutual authenthication with card... Cyclone Server (1.0.0.677), Cyclone Box Team 2008-2011 - Ready. Receiving Phone Seed 1... Phone Seed 1 Received Sending calculated Data 1, and expecting Seed 2... Calculated Data 1 accepted, Phone Seed 2 Received Sending calculated Data 2 Calculated Data 2 sent, Checking Authorization Status again Authorization successfully finished! Looking for Virgin PM In Database... Virgin PM Not found in local database, obtain one (with fields 1 and 309) and write it using "Write PM" Button Disconnected from Cyclone Server [1,0] Written, Length: 114 bytes, Status: OK [1,1] Written, Length: 4 bytes, Status: OK [1,2] Written, Length: 98 bytes, Status: OK [1,4] Written, Length: 110 bytes, Status: OK [1,5] Written, Length: 4 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,15] Written, Length: 4 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,27] Written, Length: 4 bytes, Status: OK [1,28] Written, Length: 98 bytes, Status: OK [1,29] Written, Length: 10 bytes, Status: OK [1,31] Written, Length: 98 bytes, Status: OK [1,33] Written, Length: 36 bytes, Status: OK [1,34] Written, Length: 80 bytes, Status: OK [1,35] Written, Length: 16 bytes, Status: OK [1,37] Written, Length: 4 bytes, Status: OK [1,39] Written, Length: 36 bytes, Status: OK [1,44] Written, Length: 182 bytes, Status: OK [1,45] Written, Length: 182 bytes, Status: OK [2,0] Written, Length: 448 bytes, Status: OK [4,1] Written, Length: 1020 bytes, Status: OK [4,3] Written, Length: 10 bytes, Status: OK [4,4] Written, Length: 8 bytes, Status: OK [4,5] Written, Length: 8 bytes, Status: OK [4,9] Written, Length: 5 bytes, Status: OK [4,28] Written, Length: 2 bytes, Status: OK [8,0] Written, Length: 2 bytes, Status: OK [8,1] Written, Length: 16 bytes, Status: OK [8,2] Written, Length: 16 bytes, Status: OK [8,3] Written, Length: 128 bytes, Status: OK [8,4] Written, Length: 128 bytes, Status: OK [8,7] Written, Length: 4 bytes, Status: OK [8,8] Written, Length: 8 bytes, Status: OK [8,9] Written, Length: 8 bytes, Status: OK [8,10] Written, Length: 24 bytes, Status: OK [11,0] Written, Length: 4 bytes, Status: OK [11,1] Written, Length: 4 bytes, Status: OK [11,2] Written, Length: 4 bytes, Status: OK [11,3] Written, Length: 4 bytes, Status: OK [11,4] Written, Length: 2 bytes, Status: OK [11,5] Written, Length: 1 bytes, Status: OK [12,0] Written, Length: 102 bytes, Status: OK [26,0] Written, Length: 16 bytes, Status: OK [26,1] Written, Length: 68 bytes, Status: OK [31,4] Written, Length: 14 bytes, Status: OK [44,0] Written, Length: 1 bytes, Status: OK [50,0] Written, Length: 2 bytes, Status: OK [54,0] Written, Length: 2 bytes, Status: OK [96,0] Written, Length: 2 bytes, Status: OK [96,1] Written, Length: 20 bytes, Status: OK [107,0] Written, Length: 21 bytes, Status: OK [107,1] Written, Length: 79 bytes, Status: OK [107,2] Written, Length: 79 bytes, Status: OK [107,3] Written, Length: 70 bytes, Status: OK [107,25] Written, Length: 132 bytes, Status: OK [107,26] Written, Length: 12 bytes, Status: OK [117,5] Written, Length: 10 bytes, Status: OK [117,6] Written, Length: 8 bytes, Status: OK [117,8] Written, Length: 42 bytes, Status: OK [120,0] Written, Length: 944 bytes, Status: OK [120,1] Written, Length: 80 bytes, Status: OK [120,2] Written, Length: 20 bytes, Status: OK [120,3] Written, Length: 112 bytes, Status: OK [122,0] Written, Length: 2 bytes, Status: OK [193,2] Written, Length: 8 bytes, Status: OK [193,3] Written, Length: 32 bytes, Status: OK [193,4] Written, Length: 32 bytes, Status: OK [193,9] Written, Length: 64 bytes, Status: OK [208,1] Written, Length: 4 bytes, Status: OK [217,0] Written, Length: 32 bytes, Status: OK [291,0] Written, Length: 92 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 [313,0] Written, Length: 173 bytes, Status: OK [322,0] Written, Length: 1 bytes, Status: OK [329,0] Written, Length: 8392 bytes, Status: OK [334,0] Written, Length: 1 bytes, Status: OK [341,0] Written, Length: 1 bytes, Status: OK [341,3] Written, Length: 4 bytes, Status: OK [341,4] Written, Length: 4524 bytes, Status: OK [354,0] Written, Length: 20 bytes, Status: OK [356,0] Written, Length: 2 bytes, Status: OK [356,1] Written, Length: 8 bytes, Status: OK Write PM Finished, Record written OK: 99, Record written NOT OK: 0 MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356387xxxxxxxxxx Mastercode 737507162 IMEI Spare 3A6583xxxxxxxxxxxx IMEI SV 336583078xxxxxxxxxxx CNT V 53.32.2009.43.xx PRD PSN CXB394573 Product Code 0565724 Basic Product Code 0561379 PSD 0000000000000000 LPSN 0 WLAN MAC 0025CFD6758A APE SW 32.001 APE Variant 32.00132.001.005.132.001.53.1 APE Test eno_version APE HW 256 APE ADSP 256 RETU 15 TAHVO 22 AHNE 11 HW 6000 RFIC 17141715 DSP astro_ICPR72_09w17 Simlock Server SIMLOCK SERVER Simlock Key 2440700000000000 Simlock Profile 0000000000000000 Simlock Key Cnt 0 Simlock FBUS Cnt 0 Simlock [1,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [1,2] State: OPENED Type: GID Data: FFFF Simlock [1,3] State: OPENED Type: GID Data: FFFF Simlock [1,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [1,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [2,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [2,2] State: OPENED Type: GID Data: FFFF Simlock [2,3] State: OPENED Type: GID Data: FFFF Simlock [2,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [2,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [3,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [3,2] State: OPENED Type: GID Data: FFFF Simlock [3,3] State: OPENED Type: GID Data: FFFF Simlock [3,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [3,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [4,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [4,2] State: OPENED Type: GID Data: FFFF Simlock [4,3] State: OPENED Type: GID Data: FFFF Simlock [4,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [4,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [5,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [5,2] State: OPENED Type: GID Data: FFFF Simlock [5,3] State: OPENED Type: GID Data: FFFF Simlock [5,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [5,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [6,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [6,2] State: OPENED Type: GID Data: FFFF Simlock [6,3] State: OPENED Type: GID Data: FFFF Simlock [6,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [6,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [7,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [7,2] State: OPENED Type: GID Data: FFFF Simlock [7,3] State: OPENED Type: GID Data: FFFF Simlock [7,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [7,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Superdongle циклоном отремонтировался, но при считывании mxkey снова та же байда. Растолкуйте пожалуйста. Последний раз редактировалось CAIIIA; 01.12.2011 в 14:30. |
|
|
|
01.12.2011, 14:40
|
#2 |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21 |
Re: N79 не могу влить rpl
Вот лог при записи rpl
Скрытый текстImei: 356387xxxxxxxxx
CMT Data : SYSTEM ASIC ID: 000000010000022600010006400C192101021103 [RAPIDO3G ver: 1.11] EM0 ID: 00000295 EM1 ID: 00000B22 PUBLIC ID: 146000112A650052CF5A1A498A81FA9F9245546F ASIC MODE ID: 00 ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE ROM ID: A8C1D6713E691FF8 SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 11.24.0 revision: 2.0 size: 0x3B80 Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105 eBB5ProtocolType: NEW TransmissionMode: DDR&TX2 Storage0: 0000 0000 - 0000 0000 type: RAM, asic:CMT Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT Storage2: 0400 0000 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT Storage3: 0000 0001 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT Storage4: 00EC 0040 - 0000 0121 [Samsung 2Gb DDP OneNAND,2 Gbits] type: FLASH,MuxOneNAND, asic:CMT Suggested algorithm: XSR 1.5 Algorithm: RAPIDOv11_XSR15_alg.fg [XSR 1.5] version: 11.24.0 revision: 2.0 size: 0x87D1A Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105 TransmissionMode: DDR&TX2 FUR: Adding Asic CMT as client OK CMT PAPUBKEYS HASH: B2075F4B793BB9017C8C0097C783C543F2A6A303 Updating CMT NPC ...OK Updating CMT CCC ...OK Updating CMT HWC ...OK Prog.status for Asic CMT ... NAND: OK Updating SIMLOCK...error 0x1 Updating SUPERDONGLE_KEY ...error 0x3 Updating CMLA_KEY...OK Updating WMDRM_PD...OK Phone type: RM-348 (Nokia N79) SW version: V ICPR72_09w18.4 14-10-09 RM-348 (c) Nokia Imei plain: 12345610654321-? Product code: 0565724 Battery voltage: 4756 mV, current: 0 mA ApeCoreSw: 32.001 Language Pack: - not available. SIMLOCK invalid! SUPERDONGLE_KEY seems to be valid CMLA_KEY seems to be valid WMDRM_PD seems to be valid SIMLOCK_TEST passed SECURITY_TEST failed! Imei plain is invalid !!! SIMLOCK_DATA corrupted! SIMLOCK_DATA corrupted! |
|
|
|
|
01.12.2011, 15:21
|
#3 |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,425
Вес репутации: 10   |
Re: N79 не могу влить rpl
Судя по последнему и предпоследнему логам, ничего не восстановилось, даже IMEI.
Так что до ремонта SDD ещё далеко. А то что при дефолтном IMEI = 123456... MX-KEY пишет: Код:
SUPERDONGLE_KEY seems to be valid Для начала надо восстановить IMEI, а потом уже будет видно состояние SDD и SLD. Полностью сотрите телефон. Запишите соответствующую железу прошивку SW (соответствующего RM). Несколько раз подряд запишите полученный RPL. После этого покажите лог записи RPL и лог чтения INFO (scan от MX-KEY). P.S. Всё это проделайте разными боксами, несколько раз, пока не восстановится хотя бы IMEI.
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
01.12.2011, 18:06
|
#4 |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21 |
Re: N79 не могу влить rpl
стираю прошиваю, все нормально, далее rpl вот результат
Скрытый текстCMT Data :
SYSTEM ASIC ID: 000000010000022600010006400C192101021103 [RAPIDO3G ver: 1.11] EM0 ID: 00000295 EM1 ID: 00000B22 PUBLIC ID: 146000112A650052CF5A1A498A81FA9F9245546F ASIC MODE ID: 00 ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE ROM ID: A8C1D6713E691FF8 SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 11.24.0 revision: 2.0 size: 0x3B80 Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105 eBB5ProtocolType: NEW TransmissionMode: DDR&TX2 Storage0: 0000 0000 - 0000 0000 type: RAM, asic:CMT Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT Storage2: 0400 0000 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT Storage3: 0000 0001 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT Storage4: 00EC 0040 - 0000 0121 [Samsung 2Gb DDP OneNAND,2 Gbits] type: FLASH,MuxOneNAND, asic:CMT Suggested algorithm: XSR 1.5 Algorithm: RAPIDOv11_XSR15_alg.fg [XSR 1.5] version: 11.24.0 revision: 2.0 size: 0x87D1A Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105 TransmissionMode: DDR&TX2 FUR: Adding Asic CMT as client OK CMT PAPUBKEYS HASH: B2075F4B793BB9017C8C0097C783C543F2A6A303 Erasing CMT NPC ... OK Updating CMT NPC ...OK Erasing CMT CCC ... OK Updating CMT CCC ...OK Erasing CMT HWC ... OK Updating CMT HWC ...OK Prog.status for Asic CMT ... NAND: OK Updating SIMLOCK...OK Updating SUPERDONGLE_KEY ...error 0x3 Updating CMLA_KEY...OK Updating WMDRM_PD...OK Phone type: RM-348 (Nokia N79) SW version: V ICPR72_09w09 02-03-09 RM-348 (c) Nokia Imei plain: 12345610654321-? Product code: 0565724 Battery voltage: 4832 mV, current: 0 mA ApeCoreSw: 20.175 Language Pack: - not available. SIMLOCK invalid! SUPERDONGLE_KEY invalid! - WD timer enabled, phone will reboot itself after 3 min. WMDRM_PD seems to be valid SIMLOCK_TEST passed SECURITY_TEST failed! Imei plain is invalid !!! Failed to read SP data |
|
|
|
|
01.12.2011, 19:36
|
#5 | |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,425
Вес репутации: 10 |
Re: N79 не могу влить rpl
Цитата:
Вроде в одном из логов выше есть нормальный IMEI.
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
|
02.12.2011, 00:58
|
#6 |
|
Super Moderator
Регистрация: 26.05.2011
Адрес: Ивано-Франковск =)
Сообщений: 502
Вес репутации: 233 |
Re: N79 не могу влить rpl
Код:
MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356387xxxxxxxxxx Mastercode 737507162 IMEI Spare 3A6583xxxxxxxxxxxx IMEI SV 336583078xxxxxxxxxxx CNT V 53.32.2009.43.xx PRD PSN CXB394573 Product Code 0565724 Basic Product Code 0561379 PSD 0000000000000000 LPSN 0 WLAN MAC 0025CFD6758A APE SW 32.001 APE Variant 32.00132.001.005.132.001.53.1 APE Test eno_version APE HW 256 APE ADSP 256 RETU 15 TAHVO 22 AHNE 11 HW 6000 RFIC 17141715 DSP astro_ICPR72_09w17 Simlock Server SIMLOCK SERVER Simlock Key 2440700000000000 Simlock Profile 0000000000000000 Simlock Key Cnt 0 Simlock FBUS Cnt 0 Simlock [1,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [1,2] State: OPENED Type: GID Data: FFFF Simlock [1,3] State: OPENED Type: GID Data: FFFF Simlock [1,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [1,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [2,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [2,2] State: OPENED Type: GID Data: FFFF Simlock [2,3] State: OPENED Type: GID Data: FFFF Simlock [2,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [2,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [3,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [3,2] State: OPENED Type: GID Data: FFFF Simlock [3,3] State: OPENED Type: GID Data: FFFF Simlock [3,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [3,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [4,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [4,2] State: OPENED Type: GID Data: FFFF Simlock [4,3] State: OPENED Type: GID Data: FFFF Simlock [4,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [4,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [5,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [5,2] State: OPENED Type: GID Data: FFFF Simlock [5,3] State: OPENED Type: GID Data: FFFF Simlock [5,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [5,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [6,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [6,2] State: OPENED Type: GID Data: FFFF Simlock [6,3] State: OPENED Type: GID Data: FFFF Simlock [6,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [6,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [7,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [7,2] State: OPENED Type: GID Data: FFFF Simlock [7,3] State: OPENED Type: GID Data: FFFF Simlock [7,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [7,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF |
|
|
|
|
02.12.2011, 13:49
|
#7 |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21 |
Re: N79 не могу влить rpl
После поднятия циклоном подключаю к mxkey и опять вижу два имей и симлок инвалид и прочую хрень, ничего не могу понять
чек и стирание циклоном Скрытый текстBooting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Boot skipped on user request Flashbus Write baud set to 5.0Mbits Restarting MCU... MCU Version V ICPR72_09w09 MCU Date 02-03-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 12345610654321? IMEI Spare 1A32541660452301 IMEI SV 1332541660452301F7000000 CNT V 53.32.2009.14.xx PRD PSN 0 PSD 0000000000000000 LPSN 0 APE SW 20.175 APE Variant 20.17520.175.005.120.175.53.1 APE HW 256 APE ADSP 256 APE BT HCI Version 12 (rev. 8192). LMP Version 12 (rev. 0). Manufacturer 12708. RETU 15 TAHVO 22 AHNE 11 RFIC 17141715 DSP ICPR72_09w09 Failed to read info -> Failed to read SP info Retrieving Variants for Product - wait... Failed to retrieve BB5 Variants -> Unexpected error, no VPL or neither INI files found inside Product Directory Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052BBC5A3AE0A16202166A81910 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits Erasing flash chip... Started group flash erase EraseArea[0,CMT]: 0x00000000-0x0FFFFFFF, ONENAND Waiting 640s for erasure finish... Erase taken 1.343s Restarting MCU... BB5 Full Erase Finished! вот прошивка после стирания Скрытый текстProcessing pre flash tasks...
Pre flash tasks finished, continuing... Processing RM-348_20.175_prd.core.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052BBC5A3AE0A16202166A81910 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-348_20.175_prd.core.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0xFFFFFFFF00000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled Warning: PAPUBKEYS Hash Missing! Flashbus Write baud set to 5.0Mbits Sending Certificates... Certificates OK Partitioning... Partitioning OK Started group flash erase EraseArea[0,CMT]: 0x00040000-0x00082FFF, ONENAND EraseArea[0,CMT]: 0x00083400-0x003FFFFF, ONENAND EraseArea[0,CMT]: 0x00800000-0x00D5FFFF, ONENAND EraseArea[0,CMT]: 0x00D60000-0x0A95FFFF, ONENAND Erase Partition (CMT) Waiting 320s for erasure finish... Erase taken 1.31s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT ADA Certificate... Writing CMT KEYS Certificate... Writing CMT PRIMAPP Certificate... Writing CMT RAP3NAND Certificate... Writing CMT PASUBTOC Certificate... WARNING: CMT PAPUBKEYS Hash is Empty, writing first found PAPUBKEYS Writing CMT PAPUBKEYS Certificate... Writing CMT SOS*UPDAPP Certificate... Writing CMT SOS*DSP0 Certificate... Writing CMT SOS*ISASW Certificate... Writing CMT SOS+CORE Certificate... Writing CMT SOS+ROFS1 Certificate... Programming Status OK! All blocks written OK! Time taken 108.344s Flashing Speed: 7676,60 kBit/S Restarting MCU... Processing RM-348_20.175_prd.core.fpsx (APE)... Processing RM-348_20.175_005_prd.language.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052BBC5A3AE0A16202166A81910 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-348_20.175_005_prd.language.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x08260000-0x09F5FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.188s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS+ROFS2 Certificate... Programming Status OK! All blocks written OK! Time taken 26.437s Flashing Speed: 7591,65 kBit/S Restarting MCU... Processing RM-348_20.175_005_prd.language.fpsx (APE)... Processing RM-348_20.175_53.1_prd.customer.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052BBC5A3AE0A16202166A81910 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-348_20.175_53.1_prd.customer.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x09F60000-0x0A95FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.78s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS+ROFS3 Certificate... Programming Status OK! All blocks written OK! Time taken 0.78s Flashing Speed: 504,21 kBit/S Restarting MCU... Processing RM-348_20.175_53.1_prd.customer.fpsx (APE)... Processing RM-348_20.175_002_000_U001.uda.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052BBC5A3AE0A16202166A81910 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-348_20.175_002_000_U001.uda.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x0A960000-0x0F71FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.437s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Programming Status OK! All blocks written OK! Time taken 16.16s Flashing Speed: 7069,40 kBit/S Restarting MCU... Processing RM-348_20.175_002_000_U001.uda.fpsx (APE)... All images processed OK! Processing post flash tasks... Setting Factory Defaults... Factory defaults OK Reading info... MCU Version V ICPR72_09w09 MCU Date 02-03-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 12345610654321? IMEI Spare 1A32541660452301 IMEI SV 1332541660452301F7000000 CNT V 53.32.2009.14.xx PRD PSN 0 PSD 0000000000000000 LPSN 0 APE SW 20.175 APE Variant 20.17520.175.005.120.175.53.1 APE HW 256 APE ADSP 256 APE BT HCI Version 12 (rev. 8192). LMP Version 12 (rev. 0). Manufacturer 12708. RETU 15 TAHVO 22 AHNE 11 RFIC 17141715 DSP ICPR72_09w09 Failed to read info -> Failed to read SP info Read info thread finished, continuing... Post flash tasks finished! Flashing successfully finished! 1 раз проливка rpl Скрытый текстSkipping RPL decryption...
Parsing decrypted RPL... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock NOT ACCEPTED ! Writing Superdongle key... Superdongle Key NOT ACCEPTED ! Writing CMLA key... CMLA Key ACCEPTED OK ! Writing WMDRM PD Data... WMDRM PD Data ACCEPTED OK ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock NOT ACCEPTED ! Writing Superdongle key... Superdongle Key NOT ACCEPTED ! Writing CMLA key... CMLA Key ACCEPTED OK ! Writing WMDRM PD Data... WMDRM PD Data ACCEPTED OK ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Write RPL Finished! 2 проливка rpl Скрытый текстSkipping RPL decryption...
Parsing decrypted RPL... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock NOT ACCEPTED ! Writing Superdongle key... Superdongle Key NOT ACCEPTED ! Writing CMLA key... CMLA Key ACCEPTED OK ! Writing WMDRM PD Data... WMDRM PD Data ACCEPTED OK ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock NOT ACCEPTED ! Writing Superdongle key... Superdongle Key NOT ACCEPTED ! Writing CMLA key... CMLA Key ACCEPTED OK ! Writing WMDRM PD Data... WMDRM PD Data ACCEPTED OK ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Write RPL Finished! SX4 Скрытый текстSX4 Authorization / SD Repair Procedure Started....
WARNING: "146000112A650052BBC5A3AE0A16202166A81910.C0000CC9" Not Exists, Will read it... Reading CYC file from phone... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! New_RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.16.0, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Sending Auxiliary Loader... Auxiliary Loader Sent! 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. Loader: RAPxx CommonBoot v1.06 (C) 2011 KarwosLabs Custom loader running OK! Working... Readed OK, Saving to "146000112A650052CF5A1A498A81FA9F9245546F.C0000CC9" MCU Version V ICPR72_09w09 MCU Date 02-03-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 12345610654321? Reading Security Block... Security block OK and saved to "RM-348_12345610654321_02.12.2011_160439.SecurityBlock.PM" Superdongle Key is probably CORRUPTED, Writing custom keys... Received SD Keys from box, writing to phone... Failed to Repair Superdongle Key (Phone is not responding for Superdongle Request), Will use Server and Original Card Disconnected from Cyclone Server Failed to Authorize SX4 -> Failed to get SX4 Status Последний раз редактировалось CAIIIA; 02.12.2011 в 14:14. |
|
|
|
|
02.12.2011, 13:55
|
#8 | |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,425
Вес репутации: 10 |
Re: N79 не могу влить rpl
Цитата:
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
|
02.12.2011, 14:30
|
#9 |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21 |
Re: N79 не могу влить rpl
Phone start-up failed. Contact the retailer
|
|
|
|
|
02.12.2011, 14:38
|
#10 | |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,425
Вес репутации: 10 |
Re: N79 не могу влить rpl
Цитата:
Потом сделайте с помощью Cyclone Box настоящую серверную SX4 авторизацию и сразу же запишите PM из Файловый архив После этого телефон должен полностью заработать.
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
|
02.12.2011, 14:40
|
#11 |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21 |
Re: N79 не могу влить rpl
чек mxkey
Скрытый текстMXKEY [FT SCR2000 0], SN: C08192DF
Using device: HTI, FW ver: 00.24, SN: 00005ACF Connection status: OHCI:HUB:USB 2.00 (Full-speed) Driver: WinUSB, ver: 3.5.0.0 Module ver: 1.0.0.19045(08-10-2011), Library ver: 1.0.0.12920(08-10-2011) CMT Data : SYSTEM ASIC ID: 000000010000022600010006400C192101021103 [RAPIDO3G ver: 1.11] EM0 ID: 00000295 EM1 ID: 00000B22 PUBLIC ID: 146000112A650052CF5A1A498A81FA9F9245546F ASIC MODE ID: 00 ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE ROM ID: A8C1D6713E691FF8 SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 11.24.0 revision: 2.0 size: 0x3B80 Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105 eBB5ProtocolType: NEW TransmissionMode: DDR&TX2 Storage0: 0000 0000 - 0000 0000 type: RAM, asic:CMT Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT Storage2: 0400 0000 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT Storage3: 0000 0001 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT Storage4: 00EC 0040 - 0000 0121 [Samsung 2Gb DDP OneNAND,2 Gbits] type: FLASH,MuxOneNAND, asic:CMT Suggested algorithm: XSR 1.5 Algorithm: RAPIDOv11_XSR15_alg.fg [XSR 1.5] version: 11.24.0 revision: 2.0 size: 0x87D1A Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105 TransmissionMode: DDR&TX2 FUR: Adding Asic CMT as client OK CMT PAPUBKEYS HASH: B2075F4B793BB9017C8C0097C783C543F2A6A303 Original Imei: 356387xxxxxxxx Original Product code: 0565702 Bluetooth ID: 0025CFD58B2A WLAN ID: 0025CFD6758A SIMLOCK PA identifier: [0] PA_SL2 Phone type: RM-348 (Nokia N79) SW version: V ICPR72_09w09 02-03-09 RM-348 (c) Nokia Imei plain: 12345610654321-? Battery voltage: 4852 mV, current: 0 mA Language Pack: - not available. SIMLOCK invalid! SUPERDONGLE_KEY invalid! - WD timer enabled, phone will reboot itself after 3 min. SIMLOCK_TEST passed SECURITY_TEST failed! Imei plain is invalid !!! SIMLOCK_DATA corrupted! SIMLOCK_DATA corrupted! запись rpl mxkey-ем Скрытый текстImei: 35638702897862
CMT Data : SYSTEM ASIC ID: 000000010000022600010006400C192101021103 [RAPIDO3G ver: 1.11] EM0 ID: 00000295 EM1 ID: 00000B22 PUBLIC ID: 146000112A650052CF5A1A498A81FA9F9245546F ASIC MODE ID: 00 ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE ROM ID: A8C1D6713E691FF8 SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 11.24.0 revision: 2.0 size: 0x3B80 Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105 eBB5ProtocolType: NEW TransmissionMode: DDR&TX2 Storage0: 0000 0000 - 0000 0000 type: RAM, asic:CMT Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT Storage2: 0400 0000 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT Storage3: 0000 0001 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT Storage4: 00EC 0040 - 0000 0121 [Samsung 2Gb DDP OneNAND,2 Gbits] type: FLASH,MuxOneNAND, asic:CMT Suggested algorithm: XSR 1.5 Algorithm: RAPIDOv11_XSR15_alg.fg [XSR 1.5] version: 11.24.0 revision: 2.0 size: 0x87D1A Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105 TransmissionMode: DDR&TX2 FUR: Adding Asic CMT as client OK CMT PAPUBKEYS HASH: B2075F4B793BB9017C8C0097C783C543F2A6A303 Updating CMT NPC ...OK Updating CMT CCC ...OK Updating CMT HWC ...OK Prog.status for Asic CMT ... NAND: OK Updating SIMLOCK...OK Updating SUPERDONGLE_KEY ...error 0x3 Updating CMLA_KEY...OK Updating WMDRM_PD...OK Phone type: RM-348 (Nokia N79) SW version: V ICPR72_09w09 02-03-09 RM-348 (c) Nokia Imei plain: 12345610654321-? Battery voltage: 4855 mV, current: 0 mA ApeCoreSw: 20.175 ремонт SD Скрытый текстMXKEY [FT SCR2000 0], SN: C08192DF
Using device: HTI, FW ver: 00.24, SN: 00005ACF Connection status: OHCI:HUB:USB 2.00 (Full-speed) Driver: WinUSB, ver: 3.5.0.0 Module ver: 1.0.0.19045(08-10-2011), Library ver: 1.0.0.12920(08-10-2011) Phone type: RM-348 (Nokia N79) SW version: V ICPR72_09w09 02-03-09 RM-348 (c) Nokia ApeCoreSw: 20.175 SYSTEM ASIC ID: 000000010000022600010006400C192101021103 [RAPIDO3G ver: 1.11] ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE ROM ID: A8C1D6713E691FF8 SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 11.10.0 revision: 2.0 size: 0x3B80 Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105 eBB5ProtocolType: NEW ERROR: Sec. data error ! вот analyze security Скрытый текстStarted Phone Security Analysis...
MCU Version V ICPR72_09w09 MCU Date 02-03-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 3563870xxxxxxxx Mastercode 737507162 Reading Security Block... Security block OK and saved to "RM-348_3563870xxxxxxxxx_02.12.2011_165134.SecurityBlock.PM" Step 1 : Testing SIMLOCK -- SIMLOCK PROBLEM -- Phone have failed SIMLOCK Test, that means Simlock Area is DAMAGED! To repair simlock area, Select Unlock method : "RPL CALCULATION", And then click DIRECT UNLOCK. SL Area will be re-formatted. -- SIMLOCK PROBLEM -- Step 2 : Testing SECURITY SECURITY SEFLTEST PASSED OK! Step 3 : Analyzing Security Block "146000112A650052CF5A1A498A81FA9F9245546F.C0000CC9" Exists, That is good... Checking SUPERDONGLE... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Checking SIMLOCK... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Checking MCU&DSP TIMESTAMPS... MCU&DSP TIMESTAMPS FOUND AND CHECKSUM OK! PASSED! Checking CMLA KEYS... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Checking ECC KEYS... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Checking DIV KEYS... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Analyze finished! а вот SX4 циклоном Скрытый текстSX4 Authorization / SD Repair Procedure Started....
Failed to obtain Phone Unique Data, Will use Server and Original Card MCU Version V ICPR72_09w09 MCU Date 02-03-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 12345610654321? SX4 Status: Not authorized (74) Started mutual authenthication with card... Cyclone Server (1.0.0.677), Cyclone Box Team 2008-2011 - Ready. Receiving Phone Seed 1... Phone Seed 1 Received Sending calculated Data 1, and expecting Seed 2... Calculated Data 1 accepted, Phone Seed 2 Received Disconnected from Cyclone Server Failed to Authorize SX4 -> Failed to receive mutual Data 2 from server дальше не пойму что делать Последний раз редактировалось CAIIIA; 02.12.2011 в 14:54. |
|
|
|
|
02.12.2011, 14:44
|
#12 | |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,425
Вес репутации: 10 |
Re: N79 не могу влить rpl
Цитата:
Используйте Cyclone Box. Сделайте ЭТО >>
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
|
02.12.2011, 16:16
|
#13 |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21 |
Re: N79 не могу записать RPL
ЭТО >> не помогает, но не пойму почему через раз SD то пишется то нет
Скрытый текстHandling device: [Cyclone Team], [Cyclone Bootloader]
Handling device: [Cyclone Team], [Cyclone Box] Initializing box... Box Firmware: Cyclone Nokia/Blackberry Application v01.82, (Nov 12 2011 09:45:38, gcc v4.3.3, RTOS V6.0.1), Type: Signed Production Application, (C) KarwosSoft 2011 Hardware Platform: Cyclone Classic Flasher Interface (c) 2008,2009 KarwosLabs Box Serial Number: C0000CC9 HW Revision: A, Suitable for: Production, Case: First Plastic Case, MCU Manufacture Time: 2009, wk01 / wk06 Initializing security card... Card Serial Number: D00005D0 Card Firmware Revision: 0109 Card is activated Box is activated Started box selftests procedure USB Voltage 5,00v PASSED MCU Voltage 3,28v PASSED Core Voltage 1,77v PASSED VBAT Voltage 1,44v PASSED VBAT Voltage 4,92v PASSED Box VPP disabled VPP Voltage 0,02v PASSED Internal Box VPP Enabled VPP Voltage 4,83v PASSED Box VPP disabled VPP Voltage 0,00v PASSED External Box VPP Enabled VPP Voltage 0,02v FAILED - IGNORED - Probably power supply is not connected Box VPP disabled All box selftests passed! Super DCT4 Activation: TRUE Initializing FBUS... All initialized - Ready to work Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052BBC5A3AE0A16202166A81910 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Boot skipped on user request Flashbus Write baud set to 5.0Mbits Restarting MCU... Started Phone Security Analysis... MCU Version V ICPR72_09w09 MCU Date 02-03-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 12345610654321? Reading Security Block... Security block OK and saved to "RM-348_12345610654321_02.12.2011_180751.SecurityBlock.PM" Step 1 : Testing SIMLOCK SIMLOCK SEFLTEST PASSED OK! Step 2 : Testing SECURITY -- SECURITY PROBLEM -- Phone have failed SECURITY Test, that means Superdongle Area is DAMAGED! To repair it, simply slick "SX4 Authorization / SD Repair" button. After SX4/SD Repair, don't forget to write PM file with fields 1,309 (if SW don't do this automatically) Additionaly, Checking HWC/CCC Certs... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits HWC Looks OK! CCC Looks OK! Restarting MCU... -- SECURITY PROBLEM -- Step 3 : Analyzing Security Block "146000112A650052CF5A1A498A81FA9F9245546F.C0000CC9" Exists, That is good... Checking SUPERDONGLE... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Checking SIMLOCK... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Checking MCU&DSP TIMESTAMPS... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Checking CMLA KEYS... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Checking ECC KEYS... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Checking DIV KEYS... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Analyze finished! Skipping RPL decryption... Parsing decrypted RPL... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock NOT ACCEPTED ! Writing Superdongle key... Superdongle Key NOT ACCEPTED ! Writing CMLA key... CMLA Key ACCEPTED OK ! Writing WMDRM PD Data... WMDRM PD Data ACCEPTED OK ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock NOT ACCEPTED ! Writing Superdongle key... Superdongle Key NOT ACCEPTED ! Writing CMLA key... CMLA Key ACCEPTED OK ! Writing WMDRM PD Data... WMDRM PD Data ACCEPTED OK ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Write RPL Finished! Skipping RPL decryption... Parsing decrypted RPL... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock ACCEPTED OK ! Writing Superdongle key... Superdongle Key ACCEPTED OK ! Writing CMLA key... CMLA Key NOT ACCEPTED ! Writing WMDRM PD Data... WMDRM PD Data NOT ACCEPTED ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Write RPL Finished! Skipping RPL decryption... Parsing decrypted RPL... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock ACCEPTED OK ! Writing Superdongle key... Failed to Write RPL File -> Phone is not responding for Superdongle Request Skipping RPL decryption... Parsing decrypted RPL... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock NOT ACCEPTED ! Writing Superdongle key... Superdongle Key NOT ACCEPTED ! Writing CMLA key... CMLA Key ACCEPTED OK ! Writing WMDRM PD Data... WMDRM PD Data ACCEPTED OK ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock ACCEPTED OK ! Writing Superdongle key... Superdongle Key ACCEPTED OK ! Writing CMLA key... CMLA Key NOT ACCEPTED ! Writing WMDRM PD Data... WMDRM PD Data NOT ACCEPTED ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Write RPL Finished! [1,0] Written, Length: 114 bytes, Status: Not accepted, Code: 19 [1,1] Written, Length: 4 bytes, Status: Not accepted, Code: 19 [1,2] Written, Length: 98 bytes, Status: Not accepted, Code: 19 [1,4] Written, Length: 110 bytes, Status: Not accepted, Code: 19 [1,5] Written, Length: 4 bytes, Status: Not accepted, Code: 19 [1,6] Written, Length: 98 bytes, Status: Not accepted, Code: 19 [1,8] Written, Length: 110 bytes, Status: Not accepted, Code: 19 [1,13] Written, Length: 98 bytes, Status: Not accepted, Code: 19 [1,15] Written, Length: 4 bytes, Status: Not accepted, Code: 19 [1,16] Written, Length: 98 bytes, Status: Not accepted, Code: 19 [1,18] Written, Length: 98 bytes, Status: Not accepted, Code: 19 [1,20] Written, Length: 98 bytes, Status: Not accepted, Code: 19 [1,22] Written, Length: 16 bytes, Status: Not accepted, Code: 19 [1,23] Written, Length: 4 bytes, Status: Not accepted, Code: 19 [1,24] Written, Length: 84 bytes, Status: Not accepted, Code: 19 [1,25] Written, Length: 4 bytes, Status: Not accepted, Code: 19 [1,26] Written, Length: 110 bytes, Status: Not accepted, Code: 19 [1,27] Written, Length: 4 bytes, Status: Not accepted, Code: 19 [1,28] Written, Length: 98 bytes, Status: Not accepted, Code: 19 [1,29] Written, Length: 10 bytes, Status: Not accepted, Code: 19 [1,31] Written, Length: 98 bytes, Status: Not accepted, Code: 19 [1,33] Written, Length: 36 bytes, Status: Not accepted, Code: 19 [1,34] Written, Length: 80 bytes, Status: Not accepted, Code: 19 [1,35] Written, Length: 16 bytes, Status: Not accepted, Code: 19 [1,37] Written, Length: 4 bytes, Status: Not accepted, Code: 19 [1,39] Written, Length: 36 bytes, Status: Not accepted, Code: 19 [1,44] Written, Length: 182 bytes, Status: Not accepted, Code: 19 [1,45] Written, Length: 182 bytes, Status: Not accepted, Code: 19 [2,0] Written, Length: 448 bytes, Status: OK [4,1] Written, Length: 1020 bytes, Status: OK [4,3] Written, Length: 10 bytes, Status: OK [4,4] Written, Length: 8 bytes, Status: OK [4,5] Written, Length: 8 bytes, Status: OK [4,9] Written, Length: 5 bytes, Status: OK [4,28] Written, Length: 2 bytes, Status: OK [8,0] Written, Length: 2 bytes, Status: OK [8,1] Written, Length: 16 bytes, Status: OK [8,2] Written, Length: 16 bytes, Status: OK [8,3] Written, Length: 128 bytes, Status: OK [8,4] Written, Length: 128 bytes, Status: OK [8,7] Written, Length: 4 bytes, Status: OK [8,8] Written, Length: 8 bytes, Status: OK [8,9] Written, Length: 8 bytes, Status: OK [8,10] Written, Length: 24 bytes, Status: OK [11,0] Written, Length: 4 bytes, Status: OK [11,1] Written, Length: 4 bytes, Status: OK [11,2] Written, Length: 4 bytes, Status: OK [11,3] Written, Length: 4 bytes, Status: OK [11,4] Written, Length: 2 bytes, Status: OK [11,5] Written, Length: 1 bytes, Status: OK [12,0] Written, Length: 102 bytes, Status: OK [26,0] Written, Length: 16 bytes, Status: OK [26,1] Written, Length: 68 bytes, Status: OK [31,4] Written, Length: 14 bytes, Status: OK [44,0] Written, Length: 1 bytes, Status: OK [50,0] Written, Length: 2 bytes, Status: OK [54,0] Written, Length: 2 bytes, Status: OK [96,0] Written, Length: 2 bytes, Status: OK [96,1] Written, Length: 20 bytes, Status: OK [107,0] Written, Length: 21 bytes, Status: OK [107,1] Written, Length: 79 bytes, Status: OK [107,2] Written, Length: 79 bytes, Status: OK [107,3] Written, Length: 70 bytes, Status: OK [107,25] Written, Length: 132 bytes, Status: OK [107,26] Written, Length: 12 bytes, Status: OK [117,5] Written, Length: 10 bytes, Status: OK [117,6] Written, Length: 8 bytes, Status: OK [117,8] Written, Length: 42 bytes, Status: OK [120,0] Written, Length: 944 bytes, Status: OK [120,1] Written, Length: 80 bytes, Status: OK [120,2] Written, Length: 20 bytes, Status: OK [120,3] Written, Length: 112 bytes, Status: OK [122,0] Written, Length: 2 bytes, Status: OK [193,2] Written, Length: 8 bytes, Status: OK [193,3] Written, Length: 32 bytes, Status: OK [193,4] Written, Length: 32 bytes, Status: OK [193,9] Written, Length: 64 bytes, Status: OK [208,1] Written, Length: 4 bytes, Status: OK [217,0] Written, Length: 32 bytes, Status: OK [291,0] Written, Length: 92 bytes, Status: OK [309,0] Written, Length: 4 bytes, Status: Not accepted, Code: 19 [309,1] Written, Length: 2 bytes, Status: Not accepted, Code: 19 [309,2] Written, Length: 12 bytes, Status: Not accepted, Code: 19 [309,4] Written, Length: 12 bytes, Status: Not accepted, Code: 19 [309,5] Written, Length: 12 bytes, Status: Not accepted, Code: 19 [309,7] Written, Length: 12 bytes, Status: Not accepted, Code: 19 [309,8] Written, Length: 12 bytes, Status: Not accepted, Code: 19 [309,17] Written, Length: 12 bytes, Status: Not accepted, Code: 19 [309,22] Written, Length: 12 bytes, Status: Not accepted, Code: 19 [313,0] Written, Length: 173 bytes, Status: OK [322,0] Written, Length: 1 bytes, Status: OK [329,0] Written, Length: 8392 bytes, Status: OK [334,0] Written, Length: 1 bytes, Status: OK [341,0] Written, Length: 1 bytes, Status: OK [341,3] Written, Length: 4 bytes, Status: OK [341,4] Written, Length: 4524 bytes, Status: OK [354,0] Written, Length: 20 bytes, Status: OK [356,0] Written, Length: 2 bytes, Status: OK [356,1] Written, Length: 8 bytes, Status: OK Write PM Finished, Record written OK: 62, Record written NOT OK: 37 [1,0] Written, Length: 114 bytes, Status: Not accepted, Code: 19 [1,1] Written, Length: 4 bytes, Status: Not accepted, Code: 19 [1,2] Written, Length: 98 bytes, Status: Not accepted, Code: 19 [1,4] Written, Length: 110 bytes, Status: Not accepted, Code: 19 [1,5] Written, Length: 4 bytes, Status: Not accepted, Code: 19 [1,6] Written, Length: 98 bytes, Status: Not accepted, Code: 19 [1,8] Written, Length: 110 bytes, Status: Not accepted, Code: 19 [1,13] Written, Length: 98 bytes, Status: Not accepted, Code: 19 [1,15] Written, Length: 4 bytes, Status: Not accepted, Code: 19 [1,16] Written, Length: 98 bytes, Status: Not accepted, Code: 19 [1,18] Written, Length: 98 bytes, Status: Not accepted, Code: 19 [1,20] Written, Length: 98 bytes, Status: Not accepted, Code: 19 [1,22] Written, Length: 16 bytes, Status: Not accepted, Code: 19 [1,23] Written, Length: 4 bytes, Status: Not accepted, Code: 19 [1,24] Written, Length: 84 bytes, Status: Not accepted, Code: 19 [1,25] Written, Length: 4 bytes, Status: Not accepted, Code: 19 [1,26] Written, Length: 110 bytes, Status: Not accepted, Code: 19 [1,27] Written, Length: 4 bytes, Status: Not accepted, Code: 19 [1,28] Written, Length: 98 bytes, Status: Not accepted, Code: 19 [1,29] Written, Length: 10 bytes, Status: Not accepted, Code: 19 [1,31] Written, Length: 98 bytes, Status: Not accepted, Code: 19 [1,33] Written, Length: 36 bytes, Status: Not accepted, Code: 19 [1,34] Written, Length: 80 bytes, Status: Not accepted, Code: 19 [1,35] Written, Length: 16 bytes, Status: Not accepted, Code: 19 [1,37] Written, Length: 4 bytes, Status: Not accepted, Code: 19 [1,39] Written, Length: 36 bytes, Status: Not accepted, Code: 19 [1,44] Written, Length: 182 bytes, Status: Not accepted, Code: 19 [1,45] Written, Length: 182 bytes, Status: Not accepted, Code: 19 [2,0] Written, Length: 448 bytes, Status: OK [4,1] Written, Length: 1020 bytes, Status: OK [4,3] Written, Length: 10 bytes, Status: OK [4,4] Written, Length: 8 bytes, Status: OK [4,5] Written, Length: 8 bytes, Status: OK [4,9] Written, Length: 5 bytes, Status: OK [4,28] Written, Length: 2 bytes, Status: OK [8,0] Written, Length: 2 bytes, Status: OK [8,1] Written, Length: 16 bytes, Status: OK [8,2] Written, Length: 16 bytes, Status: OK [8,3] Written, Length: 128 bytes, Status: OK [8,4] Written, Length: 128 bytes, Status: OK [8,7] Written, Length: 4 bytes, Status: OK [8,8] Written, Length: 8 bytes, Status: OK [8,9] Written, Length: 8 bytes, Status: OK [8,10] Written, Length: 24 bytes, Status: OK [11,0] Written, Length: 4 bytes, Status: OK [11,1] Written, Length: 4 bytes, Status: OK [11,2] Written, Length: 4 bytes, Status: OK [11,3] Written, Length: 4 bytes, Status: OK [11,4] Written, Length: 2 bytes, Status: OK [11,5] Written, Length: 1 bytes, Status: OK [12,0] Written, Length: 102 bytes, Status: OK [26,0] Written, Length: 16 bytes, Status: OK [26,1] Written, Length: 68 bytes, Status: OK [31,4] Written, Length: 14 bytes, Status: OK [44,0] Written, Length: 1 bytes, Status: OK [50,0] Written, Length: 2 bytes, Status: OK [54,0] Written, Length: 2 bytes, Status: OK [96,0] Written, Length: 2 bytes, Status: OK [96,1] Written, Length: 20 bytes, Status: OK [107,0] Written, Length: 21 bytes, Status: OK [107,1] Written, Length: 79 bytes, Status: OK [107,2] Written, Length: 79 bytes, Status: OK [107,3] Written, Length: 70 bytes, Status: OK [107,25] Written, Length: 132 bytes, Status: OK [107,26] Written, Length: 12 bytes, Status: OK [117,5] Written, Length: 10 bytes, Status: OK [117,6] Written, Length: 8 bytes, Status: OK [117,8] Written, Length: 42 bytes, Status: OK [120,0] Written, Length: 944 bytes, Status: OK [120,1] Written, Length: 80 bytes, Status: OK [120,2] Written, Length: 20 bytes, Status: OK [120,3] Written, Length: 112 bytes, Status: OK [122,0] Written, Length: 2 bytes, Status: OK [193,2] Written, Length: 8 bytes, Status: OK [193,3] Written, Length: 32 bytes, Status: OK [193,4] Written, Length: 32 bytes, Status: OK [193,9] Written, Length: 64 bytes, Status: OK [208,1] Written, Length: 4 bytes, Status: OK [217,0] Written, Length: 32 bytes, Status: OK [291,0] Written, Length: 92 bytes, Status: OK [309,0] Written, Length: 4 bytes, Status: Not accepted, Code: 19 [309,1] Written, Length: 2 bytes, Status: Not accepted, Code: 19 [309,2] Written, Length: 12 bytes, Status: Not accepted, Code: 19 [309,4] Written, Length: 12 bytes, Status: Not accepted, Code: 19 [309,5] Written, Length: 12 bytes, Status: Not accepted, Code: 19 [309,7] Written, Length: 12 bytes, Status: Not accepted, Code: 19 [309,8] Written, Length: 12 bytes, Status: Not accepted, Code: 19 [309,17] Written, Length: 12 bytes, Status: Not accepted, Code: 19 [309,22] Written, Length: 12 bytes, Status: Not accepted, Code: 19 [313,0] Written, Length: 173 bytes, Status: OK [322,0] Written, Length: 1 bytes, Status: OK [329,0] Written, Length: 8392 bytes, Status: OK [334,0] Written, Length: 1 bytes, Status: OK [341,0] Written, Length: 1 bytes, Status: OK [341,3] Written, Length: 4 bytes, Status: OK Failed to Write PM -> [341,4] Critical Error -1 occured Skipping RPL decryption... Parsing decrypted RPL... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock NOT ACCEPTED ! Writing Superdongle key... Superdongle Key NOT ACCEPTED ! Writing CMLA key... CMLA Key ACCEPTED OK ! Writing WMDRM PD Data... WMDRM PD Data ACCEPTED OK ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock NOT ACCEPTED ! Writing Superdongle key... Superdongle Key NOT ACCEPTED ! Writing CMLA key... CMLA Key ACCEPTED OK ! Writing WMDRM PD Data... WMDRM PD Data ACCEPTED OK ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Write RPL Finished! Skipping RPL decryption... Parsing decrypted RPL... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock ACCEPTED OK ! Writing Superdongle key... Superdongle Key ACCEPTED OK ! Writing CMLA key... CMLA Key NOT ACCEPTED ! Writing WMDRM PD Data... WMDRM PD Data NOT ACCEPTED ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Write RPL Finished! Skipping RPL decryption... Parsing decrypted RPL... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock NOT ACCEPTED ! Writing Superdongle key... Superdongle Key NOT ACCEPTED ! Writing CMLA key... CMLA Key ACCEPTED OK ! Writing WMDRM PD Data... WMDRM PD Data ACCEPTED OK ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock NOT ACCEPTED ! Writing Superdongle key... Superdongle Key NOT ACCEPTED ! Writing CMLA key... CMLA Key ACCEPTED OK ! Writing WMDRM PD Data... WMDRM PD Data ACCEPTED OK ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Write RPL Finished! Skipping RPL decryption... Parsing decrypted RPL... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock ACCEPTED OK ! Writing Superdongle key... Superdongle Key ACCEPTED OK ! Writing CMLA key... CMLA Key NOT ACCEPTED ! Writing WMDRM PD Data... WMDRM PD Data NOT ACCEPTED ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Write RPL Finished! |
|
|
|
|
02.12.2011, 16:37
|
#14 |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,425
Вес репутации: 10 |
Re: N79 не могу записать RPL
Возможно флэшка непропаяна или не совсем исправная с "плавающими" секторами.
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
02.12.2011, 16:56
|
#15 |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21 |
Re: N79 не могу записать RPL
:rolleyes:я очень рад
|
|
|
|
|
02.12.2011, 17:01
|
#16 | |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,425
Вес репутации: 10 |
Re: N79 не могу записать RPL
Цитата:
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
|
02.12.2011, 20:54
|
#17 |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21 |
Re: N79 не могу записать RPL
Бляха-муха, тел разобрал а там следы флюса, и как всегда не предупредили. Сейчас перекатал флешь (не грел)
Скрытый текстSkipping RPL decryption...
Parsing decrypted RPL... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock NOT ACCEPTED ! Writing Superdongle key... Superdongle Key NOT ACCEPTED ! Writing CMLA key... CMLA Key ACCEPTED OK ! Writing WMDRM PD Data... WMDRM PD Data ACCEPTED OK ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock ACCEPTED OK ! Writing Superdongle key... Superdongle Key ACCEPTED OK ! Writing CMLA key... CMLA Key NOT ACCEPTED ! Writing WMDRM PD Data... WMDRM PD Data NOT ACCEPTED ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Write RPL Finished! Skipping RPL decryption... Parsing decrypted RPL... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock ACCEPTED OK ! Writing Superdongle key... Superdongle Key ACCEPTED OK ! Writing CMLA key... CMLA Key NOT ACCEPTED ! Writing WMDRM PD Data... WMDRM PD Data NOT ACCEPTED ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Write RPL Finished! что делать с ним? обратите внимание на то что сначала пишет так ---------------------------------------------- Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock NOT ACCEPTED ! Writing Superdongle key... Superdongle Key NOT ACCEPTED ! Writing CMLA key... CMLA Key ACCEPTED OK ! Writing WMDRM PD Data... WMDRM PD Data ACCEPTED OK ! ---------------------------------------------- и тут же повторяет, но уже так --------------------------------------------- Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock ACCEPTED OK ! Writing Superdongle key... Superdongle Key ACCEPTED OK ! Writing CMLA key... CMLA Key NOT ACCEPTED ! Writing WMDRM PD Data... WMDRM PD Data NOT ACCEPTED ! -------------------------------------------- что мне кажется что rpl кривой, сначала Simlock и Superdongle NOT ACCEPTED, а CMLA Key и WMDRM PD Data ACCEPTED, второй раз все наоборот! Последний раз редактировалось CAIIIA; 02.12.2011 в 21:14. |
|
|
|
|
02.12.2011, 21:23
|
#18 |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,425
Вес репутации: 10 |
Re: N79 не могу записать RPL
RPL или есть, или его нет, совсем нет
 Телефон же периодически восстанавливается (IMEI, SLD), следовательно RPL DATA проверены на валидность. Да и в данном случае (SL2 телефон), нужна только NPC_DATA из полученного RPL, что бы восстановить IMEI. Всё остальное (SLD, SDD) восстанавливается Cyclone Box или MX-KEY автономно. Такое периодически нестабильное поведение телефона явно указывает на аппаратную неисправность. Если его полностью стереть и записать только SW. Как он ведёт себя? Работает ли нормально хотя бы 3-4 минуты с IMEI 123456... ?
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
03.12.2011, 12:50
|
#19 |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21 |
Re: N79 не могу записать RPL
стираю, шью, работает 3 минуты (как положено ))) и откл - собака работает в нем.
Скрытый текстProcessing pre flash tasks...
Pre flash tasks finished, continuing... Processing RM-348_10.046_prd.core.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052BBC5A3AE0A16202166A81910 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-348_10.046_prd.core.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0xFFFFFFFF00000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled Warning: PAPUBKEYS Hash Missing! Flashbus Write baud set to 5.0Mbits Sending Certificates... Certificates OK Partitioning... Partitioning OK Started group flash erase EraseArea[0,CMT]: 0x00040000-0x00082FFF, ONENAND EraseArea[0,CMT]: 0x00083400-0x003FFFFF, ONENAND EraseArea[0,CMT]: 0x00800000-0x00D5FFFF, ONENAND EraseArea[0,CMT]: 0x00D60000-0x0A95FFFF, ONENAND Erase Partition (CMT) Waiting 320s for erasure finish... Erase taken 0.922s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT ADA Certificate... Writing CMT KEYS Certificate... Writing CMT PRIMAPP Certificate... Writing CMT RAP3NAND Certificate... Writing CMT PASUBTOC Certificate... WARNING: CMT PAPUBKEYS Hash is Empty, writing first found PAPUBKEYS Writing CMT PAPUBKEYS Certificate... Writing CMT SOS*UPDAPP Certificate... Writing CMT SOS*DSP0 Certificate... Writing CMT SOS*ISASW Certificate... Writing CMT SOS+CORE Certificate... Writing CMT SOS+ROFS1 Certificate... Programming Status OK! All blocks written OK! Time taken 109.782s Flashing Speed: 7440,94 kBit/S Restarting MCU... Processing RM-348_10.046_prd.core.fpsx (APE)... Processing RM-348_10.046_005_prd.rofs2.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-348_10.046_005_prd.rofs2.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x08260000-0x09F5FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.171s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS+ROFS2 Certificate... Programming Status OK! All blocks written OK! Time taken 27.250s Flashing Speed: 7333,44 kBit/S Restarting MCU... Processing RM-348_10.046_005_prd.rofs2.fpsx (APE)... Processing RM-348_10.046_53.1_prd.customer.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-348_10.046_53.1_prd.customer.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x09F60000-0x0A95FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.63s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS+ROFS3 Certificate... Programming Status OK! All blocks written OK! Time taken 0.62s Flashing Speed: 634,32 kBit/S Restarting MCU... Processing RM-348_10.046_53.1_prd.customer.fpsx (APE)... Processing RM-348_10.046_013_000_U001.uda.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-348_10.046_013_000_U001.uda.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x0A960000-0x0F71FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.406s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Programming Status OK! All blocks written OK! Time taken 13.610s Flashing Speed: 6773,32 kBit/S Restarting MCU... Processing RM-348_10.046_013_000_U001.uda.fpsx (APE)... All images processed OK! Processing post flash tasks... Setting Factory Defaults... Factory defaults OK Reading info... MCU Version V ICPR72_08w36.1 MCU Date 07-10-08 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 12345610654321? IMEI Spare 1A32541660452301 IMEI SV 1332541660452301F4000000 CNT U001 PSN 0 PSD 0000000000000000 LPSN 0 APE SW 10.046 APE Variant 10.04610.046.005.110.046.53.1 APE HW 256 APE ADSP 256 APE BT HCI Version 12 (rev. 8192). LMP Version 12 (rev. 0). Manufacturer 12708. RETU 15 TAHVO 22 AHNE 11 RFIC 17141715 DSP ICPR72_08w36 Failed to read info -> Failed to read SP info Read info thread finished, continuing... Post flash tasks finished! Flashing successfully finished! |
|
|
|
|
03.12.2011, 13:00
|
#20 | |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,425
Вес репутации: 10 |
Re: N79 не могу записать RPL
Цитата:
И это на 99% показывает, что аппаратная часть в порядке. Теперь запишите только RPL, что бы получился вот такой лог INFO: Код:
Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356387xxxxxxxxxx Mastercode 737507162 IMEI Spare 3A6583xxxxxxxxxxxx IMEI SV 336583078xxxxxxxxxxx CNT V 53.32.2009.43.xx PRD PSN CXB394573 Product Code 0565724 Basic Product Code 0561379 PSD 0000000000000000 LPSN 0 WLAN MAC 0025CFD6758A APE SW 32.001 APE Variant 32.00132.001.005.132.001.53.1 APE Test eno_version APE HW 256 APE ADSP 256 RETU 15 TAHVO 22 AHNE 11 HW 6000 RFIC 17141715 DSP astro_ICPR72_09w17 Simlock Server SIMLOCK SERVER Simlock Key 2440700000000000 Simlock Profile 0000000000000000 Simlock Key Cnt 0 Simlock FBUS Cnt 0
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
|
03.12.2011, 13:51
|
#21 |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21 |
Re: N79 не могу записать RPL
после записи rpl
Скрытый текстSkipping RPL decryption...
Parsing decrypted RPL... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock NOT ACCEPTED ! Writing Superdongle key... Superdongle Key ACCEPTED OK ! Writing CMLA key... CMLA Key NOT ACCEPTED ! Writing WMDRM PD Data... WMDRM PD Data NOT ACCEPTED ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Processing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock ACCEPTED OK ! Writing Superdongle key... Superdongle Key ACCEPTED OK ! Writing CMLA key... CMLA Key NOT ACCEPTED ! Writing WMDRM PD Data... WMDRM PD Data NOT ACCEPTED ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Write RPL Finished! MCU Version V ICPR72_08w36.1 MCU Date 07-10-08 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356387xxxxxxxxxxx Mastercode 737507162 IMEI Spare 3A6583xxxxxxxxx IMEI SV 33658307xxxxxxxxxxxxxx CNT U001 PSN 0 PSD 0000000000000000 LPSN 0 WLAN MAC 0025CFD6758A APE SW 10.046 APE Variant 10.04610.046.005.110.046.53.1 APE HW 256 APE ADSP 256 APE BT HCI Version 12 (rev. 8192). LMP Version 12 (rev. 0). Manufacturer 12708. RETU 15 TAHVO 22 AHNE 11 RFIC 17141715 DSP ICPR72_08w36 Simlock Server SIMLOCK SERVER Simlock Key 2440700000000000 Simlock Profile 0000000000000000 Simlock Key Cnt 0 Simlock FBUS Cnt 0 Simlock [1,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [1,2] State: OPENED Type: GID Data: FFFF Simlock [1,3] State: OPENED Type: GID Data: FFFF Simlock [1,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [1,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [2,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [2,2] State: OPENED Type: GID Data: FFFF Simlock [2,3] State: OPENED Type: GID Data: FFFF Simlock [2,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [2,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [3,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [3,2] State: OPENED Type: GID Data: FFFF Simlock [3,3] State: OPENED Type: GID Data: FFFF Simlock [3,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [3,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [4,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [4,2] State: OPENED Type: GID Data: FFFF Simlock [4,3] State: OPENED Type: GID Data: FFFF Simlock [4,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [4,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [5,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [5,2] State: OPENED Type: GID Data: FFFF Simlock [5,3] State: OPENED Type: GID Data: FFFF Simlock [5,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [5,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [6,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [6,2] State: OPENED Type: GID Data: FFFF Simlock [6,3] State: OPENED Type: GID Data: FFFF Simlock [6,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [6,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [7,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [7,2] State: OPENED Type: GID Data: FFFF Simlock [7,3] State: OPENED Type: GID Data: FFFF Simlock [7,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [7,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF и сразу анализ security Скрытый текстStarted Phone Security Analysis...
MCU Version V ICPR72_08w36.1 MCU Date 07-10-08 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 12345610654321? Reading Security Block... Security block OK and saved to "RM-348_12345610654321_03.12.2011_154807.SecurityBlock.PM" Step 1 : Testing SIMLOCK SIMLOCK SEFLTEST PASSED OK! Step 2 : Testing SECURITY -- SECURITY PROBLEM -- Phone have failed SECURITY Test, that means Superdongle Area is DAMAGED! To repair it, simply slick "SX4 Authorization / SD Repair" button. After SX4/SD Repair, don't forget to write PM file with fields 1,309 (if SW don't do this automatically) Additionaly, Checking HWC/CCC Certs... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits HWC Looks OK! CCC Looks OK! Restarting MCU... -- SECURITY PROBLEM -- Step 3 : Analyzing Security Block WARNING: "146000112A650052BBC5A3AE0A16202166A81910.C0000CC9" Not Exists, Will read it... Reading CYC file from phone... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! New_RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.16.0, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Sending Auxiliary Loader... Auxiliary Loader Sent! 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. Loader: RAPxx CommonBoot v1.06 (C) 2011 KarwosLabs Custom loader running OK! Working... Readed OK, Saving to "146000112A650052CF5A1A498A81FA9F9245546F.C0000CC9" Checking SUPERDONGLE... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Checking SIMLOCK... SIMLOCK FOUND AND CHECKSUM OK! PASSED! Checking MCU&DSP TIMESTAMPS... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) 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... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Analyze finished! |
|
|
|
|
03.12.2011, 14:06
|
#22 |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,425
Вес репутации: 10 |
Re: N79 не могу записать RPL
Тоесть получается записью RPL телефон восстанавливается, но при передёргивании питания снова нарушаются CRT ?
В таком случае это 100% проблемма аппаратной части. Хотя... не мешает ещё проверить такой вариант: N79 бывают разных RM И мне известны случаи, когда даже при родном шильдике с одним RM, телефон оживал только при записи в него другого (отличающегося от шильдика RM). Попробуйте восстанавливать этот N79 при разных RM Если и это не поможет, то остаётся менять Flash IC.
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
03.12.2011, 20:57
|
#23 |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21 |
Re: N79 не могу записать RPL
RM-349 и RM-350 вливаются но все абсолютно так же
|
|
|
|
|
04.12.2011, 00:27
|
#24 | ||
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,425
Вес репутации: 10 |
Re: N79 не могу записать RPL
Цитата:
Доведите телефон до такого состояния: Лог INFOProduct RM-348 (Nokia N79)
Manufacturer (c) Nokia IMEI 356387xxxxxxxxxx Mastercode 737507162 IMEI Spare 3A6583xxxxxxxxxxxx IMEI SV 336583078xxxxxxxxxxx CNT V 53.32.2009.43.xx PRD PSN CXB394573 Product Code 0565724 Basic Product Code 0561379 PSD 0000000000000000 LPSN 0 WLAN MAC 0025CFD6758A APE SW 32.001 APE Variant 32.00132.001.005.132.001.53.1 APE Test eno_version APE HW 256 APE ADSP 256 RETU 15 TAHVO 22 AHNE 11 HW 6000 RFIC 17141715 DSP astro_ICPR72_09w17 Simlock Server SIMLOCK SERVER Simlock Key 2440700000000000 Simlock Profile 0000000000000000 Simlock Key Cnt 0 Simlock FBUS Cnt 0 Цитата:
Если Phone start-up failed. Contact the retailer не уйдёт, то Cyclone сделайте SX4 и запись PM.
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
||
|
|
|
|
05.12.2011, 14:24
|
#25 | |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21 |
Цитата:
Скрытый текстCMT Data :
SYSTEM ASIC ID: 000000010000022600010006400C192101021103 [RAPIDO3G ver: 1.11] EM0 ID: 00000295 EM1 ID: 00000B22 PUBLIC ID: 146000112A650052CF5A1A498A81FA9F9245546F ASIC MODE ID: 00 ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE ROM ID: A8C1D6713E691FF8 SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 11.34.0 revision: 2.0 size: 0x3B80 Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105 eBB5ProtocolType: NEW TransmissionMode: DDR&TX2 Storage0: 0000 0000 - 0000 0000 type: RAM, asic:CMT Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT Storage2: 0400 0000 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT Storage3: 0000 0001 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT Storage4: 00EC 0040 - 0000 0121 [Samsung 2Gb DDP OneNAND,2 Gbits] type: FLASH,MuxOneNAND, asic:CMT Suggested algorithm: XSR 1.5 Algorithm: RAPIDOv11_XSR15_alg.fg [XSR 1.5] version: 11.34.0 revision: 2.0 size: 0x8FE30 Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105 TransmissionMode: DDR&TX2 FUR: Adding Asic CMT as client OK CMT PAPUBKEYS HASH: B2075F4B793BB9017C8C0097C783C543F2A6A303 Begin Certificate Request ... SERVER->Served by MXKEY - BLADE X at host2, agent version 1.1 revision 0.9 Updating PRODUCTCODE (0565702)... OK MXKEY [FT SCR2000 0], SN: C08192DF Using device: HTI, FW ver: 00.24, SN: 00005ACF Connection status: OHCI:HUB:USB 2.00 (Full-speed) Driver: WinUSB, ver: 3.5.0.0 Module ver: 1.0.0.19228(10-11-2011), Library ver: 1.0.0.13150(10-11-2011) CMT Data : SYSTEM ASIC ID: 000000010000022600010006400C192101021103 [RAPIDO3G ver: 1.11] EM0 ID: 00000295 EM1 ID: 00000B22 PUBLIC ID: 146000112A650052CF5A1A498A81FA9F9245546F ASIC MODE ID: 00 ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE ROM ID: A8C1D6713E691FF8 SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 11.34.0 revision: 2.0 size: 0x3B80 Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105 eBB5ProtocolType: NEW TransmissionMode: DDR&TX2 Storage0: 0000 0000 - 0000 0000 type: RAM, asic:CMT Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT Storage2: 0400 0000 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT Storage3: 0000 0001 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT Storage4: 00EC 0040 - 0000 0121 [Samsung 2Gb DDP OneNAND,2 Gbits] type: FLASH,MuxOneNAND, asic:CMT Suggested algorithm: XSR 1.5 Algorithm: RAPIDOv11_XSR15_alg.fg [XSR 1.5] version: 11.34.0 revision: 2.0 size: 0x8FE30 Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105 TransmissionMode: DDR&TX2 FUR: Adding Asic CMT as client OK CMT PAPUBKEYS HASH: B2075F4B793BB9017C8C0097C783C543F2A6A303 Updating CMT NPC ...OK Updating CMT CCC ...OK Updating CMT HWC ...OK Prog.status for Asic CMT ... NAND: OK опять то же самое Скрытый текстMXKEY [FT SCR2000 0], SN: C08192DF
Using device: HTI, FW ver: 00.24, SN: 00005ACF Connection status: OHCI:HUB:USB 2.00 (Full-speed) Driver: WinUSB, ver: 3.5.0.0 Module ver: 1.0.0.19228(10-11-2011), Library ver: 1.0.0.13150(10-11-2011) CMT Data : SYSTEM ASIC ID: 000000010000022600010006400C192101021103 [RAPIDO3G ver: 1.11] EM0 ID: 00000295 EM1 ID: 00000B22 PUBLIC ID: 146000112A650052CF5A1A498A81FA9F9245546F ASIC MODE ID: 00 ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE ROM ID: A8C1D6713E691FF8 SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 11.34.0 revision: 2.0 size: 0x3B80 Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105 eBB5ProtocolType: NEW TransmissionMode: DDR&TX2 Storage0: 0000 0000 - 0000 0000 type: RAM, asic:CMT Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT Storage2: 0400 0000 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT Storage3: 0000 0001 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT Storage4: 00EC 0040 - 0000 0121 [Samsung 2Gb DDP OneNAND,2 Gbits] type: FLASH,MuxOneNAND, asic:CMT Suggested algorithm: XSR 1.5 Algorithm: RAPIDOv11_XSR15_alg.fg [XSR 1.5] version: 11.34.0 revision: 2.0 size: 0x8FE30 Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105 TransmissionMode: DDR&TX2 FUR: Adding Asic CMT as client OK CMT PAPUBKEYS HASH: B2075F4B793BB9017C8C0097C783C543F2A6A303 Original Imei: 356387xxxxxxxxxx Original Product code: 0565702 Bluetooth ID: 0025CFD58B2A WLAN ID: 0025CFD6758A SIMLOCK PA identifier: [0] PA_SL2 Phone type: RM-348 (Nokia N89) SW version: V ICPR72_08w36.1 07-10-08 RM-348 (c) Nokia Imei plain: 12345610654321-? Product code: 0565702 Battery voltage: 4849 mV, current: 255 mA ApeCoreSw: 10.046 Language Pack: - not available. SLPA ver[1]: PA_SL (15 digit NCK) SIMLOCK invalid! SUPERDONGLE_KEY invalid! - WD timer enabled, phone will reboot itself after 3 min. SIMLOCK_TEST passed SECURITY_TEST failed! Imei plain is invalid !!! SIMLOCK_DATA corrupted! SIMLOCK_DATA corrupted! достало |
|
|
|
|
|
05.12.2011, 14:33
|
#26 |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,425
Вес репутации: 10 |
Re: N79 не могу записать RPL
Ну что ж.
По программной части проделано всё и даже более чем всё. Остаётся грешить на железо. Я бы начал с замены Flash IC.
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
05.12.2011, 14:35
|
#27 |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21 |
Re: N79 не могу записать RPL
да, так брыкается у меня тел в первый раз, хорошо, поищу флешку
|
|
|
|
|
21.12.2011, 17:09
|
#28 |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21 |
Re: N79 не могу записать RPL
Решил отписать по этому телефону, почти весь отреболил, но все на том же месте, а флешку не нашел, вроде подходит с 5800, N97, 6760s. Доноров нет, может принесут, буду ждать.
|
|
|
|
|
21.12.2011, 17:15
|
#29 | |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,425
Вес репутации: 10 |
Re: N79 не могу записать RPL
Цитата:
Можно установить любую Flash от любой Nokia, подходящую по цоколёвке и объёму памяти. Может тольо не стоит брать с совсем свежих моделей.
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
|
21.12.2011, 17:28
|
#30 |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21 |
Re: N79 не могу записать RPL
Стало быть должны подойти все эти, они все в одинаковых корпусах
|
|
|
|
|
21.12.2011, 17:33
|
#31 | |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,425
Вес репутации: 10 |
Re: N79 не могу записать RPL
Цитата:
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
|
21.12.2011, 19:02
|
#32 |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21 |
Re: N79 не могу записать RPL
Вместо флешки SAMSUNG K5W2G1GACH поставил флешку ST M39B0RB0A0, снимал с 5530, но то ли с этой флешкой тоже какой-то косяк то ли я не пойму что ещё надо. После снятия с кабеля и запуска от батареи все опять слетает. Тот донор, с которого снята флешка тоже был с какой-то проблемой. он после прошивки и включения писал - ошибка самотестирования телефона.
Скрытый текстProcessing FBUS Part... Writing Simlock... Handling as SL1/SL2 Simlock Data Simlock ACCEPTED OK ! Writing Superdongle key... Superdongle Key ACCEPTED OK ! Writing CMLA key... CMLA Key NOT ACCEPTED ! Writing WMDRM PD Data... WMDRM PD Data NOT ACCEPTED ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 146000112A650052CF5A1A498A81FA9F9245546F CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: A8C1D671 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0020004000000031, ST, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x0020004000000031, ST, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00200040 (ST), Size: 256MBytes, VPP: Not Supported FlashChip 0x00200040 (ST), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: B2075F4B793BB9017C8C0097C783C543F2A6A303 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Write RPL Finished! SX4 Authorization / SD Repair Procedure Started.... "146000112A650052CF5A1A498A81FA9F9245546F.C0000CC9" Exists, That is good... MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 35638702xxxxxxxxxxx Mastercode 737507162 Reading Security Block... Security block OK and saved to "RM-348_3563870xxxxxxxxxx_21.12.2011_203836.SecurityBlock.PM" SX4 Status: Not authorized (74) Started mutual authenthication with card... Receiving Phone Seed 1... Phone Seed 1 Received Sending calculated Data 1, and expecting Seed 2... Calculated Data 1 accepted, Phone Seed 2 Received Sending calculated Data 2 Calculated Data 2 sent, Checking Authorization Status again Authorization successfully finished! Looking for Virgin PM In Database... Virgin PM Not found in local database, obtain one (with fields 1 and 309) and write it using "Write PM" Button [1,0] Written, Length: 114 bytes, Status: OK [1,1] Written, Length: 4 bytes, Status: OK [1,2] Written, Length: 98 bytes, Status: OK [1,4] Written, Length: 110 bytes, Status: OK [1,5] Written, Length: 4 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,15] Written, Length: 4 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,27] Written, Length: 4 bytes, Status: OK [1,28] Written, Length: 98 bytes, Status: OK [1,29] Written, Length: 10 bytes, Status: OK [1,31] Written, Length: 98 bytes, Status: OK [1,33] Written, Length: 36 bytes, Status: OK [1,34] Written, Length: 80 bytes, Status: OK [1,35] Written, Length: 16 bytes, Status: OK [1,37] Written, Length: 4 bytes, Status: OK [1,39] Written, Length: 36 bytes, Status: OK [1,44] Written, Length: 182 bytes, Status: OK [1,45] Written, Length: 182 bytes, Status: OK [2,0] Written, Length: 448 bytes, Status: OK [4,1] Written, Length: 1020 bytes, Status: OK [4,3] Written, Length: 10 bytes, Status: OK [4,4] Written, Length: 8 bytes, Status: OK [4,5] Written, Length: 8 bytes, Status: OK [4,9] Written, Length: 5 bytes, Status: OK [4,28] Written, Length: 2 bytes, Status: OK [8,0] Written, Length: 2 bytes, Status: OK [8,1] Written, Length: 16 bytes, Status: OK [8,2] Written, Length: 16 bytes, Status: OK [8,3] Written, Length: 128 bytes, Status: OK [8,4] Written, Length: 128 bytes, Status: OK [8,7] Written, Length: 4 bytes, Status: OK [8,8] Written, Length: 8 bytes, Status: OK [8,9] Written, Length: 8 bytes, Status: OK [8,10] Written, Length: 24 bytes, Status: OK [11,0] Written, Length: 4 bytes, Status: OK [11,1] Written, Length: 4 bytes, Status: OK [11,2] Written, Length: 4 bytes, Status: OK [11,3] Written, Length: 4 bytes, Status: OK [11,4] Written, Length: 2 bytes, Status: OK [11,5] Written, Length: 1 bytes, Status: OK [12,0] Written, Length: 102 bytes, Status: OK [26,0] Written, Length: 16 bytes, Status: OK [26,1] Written, Length: 68 bytes, Status: OK [31,4] Written, Length: 14 bytes, Status: OK [44,0] Written, Length: 1 bytes, Status: OK [50,0] Written, Length: 2 bytes, Status: OK [54,0] Written, Length: 2 bytes, Status: OK [96,0] Written, Length: 2 bytes, Status: OK [96,1] Written, Length: 20 bytes, Status: OK [107,0] Written, Length: 21 bytes, Status: OK [107,1] Written, Length: 79 bytes, Status: OK [107,2] Written, Length: 79 bytes, Status: OK [107,3] Written, Length: 70 bytes, Status: OK [107,25] Written, Length: 132 bytes, Status: OK [107,26] Written, Length: 12 bytes, Status: OK [117,5] Written, Length: 10 bytes, Status: OK [117,6] Written, Length: 8 bytes, Status: OK [117,8] Written, Length: 42 bytes, Status: OK [120,0] Written, Length: 944 bytes, Status: OK [120,1] Written, Length: 80 bytes, Status: OK [120,2] Written, Length: 20 bytes, Status: OK [120,3] Written, Length: 112 bytes, Status: OK [122,0] Written, Length: 2 bytes, Status: OK [193,2] Written, Length: 8 bytes, Status: OK [193,3] Written, Length: 32 bytes, Status: OK [193,4] Written, Length: 32 bytes, Status: OK [193,9] Written, Length: 64 bytes, Status: OK [208,1] Written, Length: 4 bytes, Status: OK [217,0] Written, Length: 32 bytes, Status: OK [291,0] Written, Length: 92 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 [313,0] Written, Length: 173 bytes, Status: OK [322,0] Written, Length: 1 bytes, Status: OK [329,0] Written, Length: 8392 bytes, Status: OK [334,0] Written, Length: 1 bytes, Status: OK [341,0] Written, Length: 1 bytes, Status: OK [341,3] Written, Length: 4 bytes, Status: OK [341,4] Written, Length: 4524 bytes, Status: OK [354,0] Written, Length: 20 bytes, Status: OK [356,0] Written, Length: 2 bytes, Status: OK [356,1] Written, Length: 8 bytes, Status: OK Write PM Finished, Record written OK: 99, Record written NOT OK: 0 MCU Version V ICPR72_09w18.4 MCU Date 14-10-09 Product RM-348 (Nokia N79) Manufacturer (c) Nokia IMEI 356387xxxxxxxxxx Mastercode 737507162 IMEI Spare 3A65830xxxxxxxxx IMEI SV 3365830782xxxxxxxxxxxx CNT V 53.32.2009.43.xx PRD PSN CXB394573 Product Code 0565724 Basic Product Code 0561379 PSD 0000000000000000 LPSN 0 WLAN MAC 0025CFD6758A APE SW 32.001 APE Variant 32.00132.001.005.132.001.53.1 APE Test eno_version APE HW 256 APE ADSP 256 RETU 15 TAHVO 22 AHNE 11 HW 6000 RFIC 17141715 DSP astro_ICPR72_09w17 Simlock Server SIMLOCK SERVER Simlock Key 2440700000000000 Simlock Profile 0000000000000000 Simlock Key Cnt 0 Simlock FBUS Cnt 0 Simlock [1,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [1,2] State: OPENED Type: GID Data: FFFF Simlock [1,3] State: OPENED Type: GID Data: FFFF Simlock [1,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [1,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [2,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [2,2] State: OPENED Type: GID Data: FFFF Simlock [2,3] State: OPENED Type: GID Data: FFFF Simlock [2,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [2,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [3,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [3,2] State: OPENED Type: GID Data: FFFF Simlock [3,3] State: OPENED Type: GID Data: FFFF Simlock [3,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [3,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [4,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [4,2] State: OPENED Type: GID Data: FFFF Simlock [4,3] State: OPENED Type: GID Data: FFFF Simlock [4,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [4,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [5,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [5,2] State: OPENED Type: GID Data: FFFF Simlock [5,3] State: OPENED Type: GID Data: FFFF Simlock [5,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [5,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [6,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [6,2] State: OPENED Type: GID Data: FFFF Simlock [6,3] State: OPENED Type: GID Data: FFFF Simlock [6,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [6,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [7,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [7,2] State: OPENED Type: GID Data: FFFF Simlock [7,3] State: OPENED Type: GID Data: FFFF Simlock [7,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [7,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Последний раз редактировалось CAIIIA; 21.12.2011 в 19:27. |
|
|
|
|
21.12.2011, 19:39
|
#33 |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21 |
Re: N79 не могу записать RPL
Что за хрень происходит? стер, прошил, рпл, sx4, pm, OK. делаю selftest, опять слетело все.
Скрытый текстSelftests to proceed: 47
Passed ST_TAHVOINT_TEST Passed ST_UEM_CBUS_IF_TEST Passed ST_EAR_DATA_LOOP_TEST Passed ST_SIM_CLK_LOOP_TEST Passed ST_SIM_IO_CTRL_LOOP_TEST Passed ST_SIM_LOCK_TEST Failed ST_SECURITY_TEST Passed ST_PWR_KEY_TEST Passed ST_CURRENT_CONS_TEST Passed ST_BACKUP_BATT_TEST Passed ST_HOOKINT_TEST Passed ST_BTEMP_TEST Passed ST_AMB_LIGHT_SENSOR_TEST Passed ST_FMTX_TEST Failed ST_HEADSET_AMPLIFIER_TEST Passed ST_EXT_DEVICE_TEST Passed ST_CDSP_SLEEPCLK_FREQ_TEST Passed ST_CDSP_SLEEPCLOCK_FREQ_TEST Passed ST_CDSP_RF_BB_IF_TEST Passed ST_CDSP_RF_SUPPLY_TEST Passed ST_CDSP_TX_IQ_TEST Passed ST_CDSP_TXC_DATA_TEST Passed ST_CDSP_PWR_DETECTOR_BIAS_TEST Passed ST_CDSP_RX_PLL_PHASE_LOCK_TEST Passed ST_CDSP_TX_PLL_PHASE_LOCK_TEST |
|
|
|
|
21.12.2011, 21:05
|
#34 | |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,425
Вес репутации: 10 |
Re: N79 не могу записать RPL
Цитата:
Вот же геммор получился с этим телефоном. Выходит не во флэшке дело. В чём то другом. Может даже и в процессоре 
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
|
21.12.2011, 21:53
|
#35 |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21 |
Re: N79 не могу записать RPL
завтра снятую самсунг воткну в 5530 и попробую её там завести, бэкапы слил. Хотел сегодня ещё мхкеем попарить телефон, но после обновления проги дрова мхбокс не ставятся. Ошибка 10. Не знаю есть ли она у других, но у меня есть, тоже чехарда с коробками, жаль что BEST-а нет я бы им попробовал тоже.
|
|
|
|
|
21.12.2011, 21:58
|
#36 | |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,425
Вес репутации: 10 |
Re: N79 не могу записать RPL
Цитата:
Ведь телефон одинаково восстанавливается с любой из 3-х уже перепробованых вами флэшек. Или не одинаково ведёт себя с разными флэшками?
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
|
21.12.2011, 22:28
|
#37 |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21 |
Re: N79 не могу записать RPL
в том то и дело, что разница все же есть. с самсунговой флешью рпл слетал прямо перед SX4, а с ST флешью пока на кабеле сидит телефон все пишется как надо.
|
|
|
|
|
21.12.2011, 22:33
|
#38 |
|
ADMINISTRATOR
Регистрация: 01.01.2011
Адрес: www.UO5OQ.com
Сообщений: 14,425
Вес репутации: 10 |
Re: N79 не могу записать RPL
Хм... ну поэкпериментируйте конечно.
Это редчайший случай. Раза 2 за всю практику припоминаю. И оба раза замена флэш сразу же помогла.
__________________
ASK->RPL , NCK Коды, Логи и Активации на www.UO5OQ.com |
|
|
|
|
22.12.2011, 13:17
|
#39 |
|
Member
Регистрация: 20.08.2011
Сообщений: 55
Вес репутации: 21 |
Re: N79 не могу записать RPL
Ну и как же это понимать? снятая с N79 флешка Samsung (с которой все и началось) воткнута в 5530 телефон поднят, работает. Avilma, betty, RAPIDO, flash ни при чем, у кого есть мысли по поводу?
Скрытый текстBooting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 1D500103BC840052C50B7E9B68EBA70A140FC214 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled Warning: PAPUBKEYS Hash Missing! APE Boot skipped on user request Flashbus Write baud set to 5.0Mbits Restarting MCU... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 1D500103BC840052C50B7E9B68EBA70A140FC214 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled Warning: PAPUBKEYS Hash Missing! APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits Erasing flash chip... Started group flash erase EraseArea[0,CMT]: 0x00000000-0x0FFFFFFF, ONENAND Waiting 640s for erasure finish... Erase taken 1.328s Restarting MCU... BB5 Full Erase Finished! Processing pre flash tasks... Pre flash tasks finished, continuing... Processing RM-504_31.0.005_prd.core.C00 (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 1D500103BC840052C50B7E9B68EBA70A140FC214 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-504_31.0.005_prd.core.C00, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0xFFFFFFFF00000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled Warning: PAPUBKEYS Hash Missing! Flashbus Write baud set to 5.0Mbits Sending Certificates... Certificates OK Partitioning... Partitioning OK Started group flash erase EraseArea[0,CMT]: 0x00040000-0x00082FFF, ONENAND EraseArea[0,CMT]: 0x00083400-0x003FFFFF, ONENAND EraseArea[0,CMT]: 0x00400000-0x007FFFFF, ONENAND EraseArea[0,CMT]: 0x00800000-0x00D5FFFF, ONENAND EraseArea[0,CMT]: 0x00D60000-0x09E5FFFF, ONENAND Erase Partition (CMT) Waiting 320s for erasure finish... Erase taken 0.906s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT ADA Certificate... Writing CMT KEYS Certificate... Writing CMT PRIMAPP Certificate... Writing CMT RAP3NAND Certificate... Writing CMT PASUBTOC Certificate... WARNING: CMT PAPUBKEYS Hash is Empty, writing first found PAPUBKEYS Writing CMT PAPUBKEYS Certificate... Writing CMT SOS*UPDAPP Certificate... Writing CMT SOS*ENO Certificate... Writing CMT SOS*DSP0 Certificate... Writing CMT SOS*ISASW Certificate... Writing CMT SOS+CORE Certificate... Writing CMT SOS+ROFS1 Certificate... Programming Status OK! All blocks written OK! Time taken 110.953s Flashing Speed: 7773,96 kBit/S Restarting MCU... Processing RM-504_31.0.005_prd.core.C00 (APE)... Processing RM-504_31.0.005_prd.rofs2.V05 (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 1D500103BC840052C50B7E9B68EBA70A140FC214 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-504_31.0.005_prd.rofs2.V05, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: F2B05364E563A348608C1C3C9E54FE42AAAA1ACF Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x07260000-0x0935FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.188s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS+ROFS2 Certificate... Programming Status OK! All blocks written OK! Time taken 30.531s Flashing Speed: 7655,60 kBit/S Restarting MCU... Processing RM-504_31.0.005_prd.rofs2.V05 (APE)... Processing RM-504_31.0.005_C06_prd.rofs3.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 1D500103BC840052C50B7E9B68EBA70A140FC214 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-504_31.0.005_C06_prd.rofs3.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: F2B05364E563A348608C1C3C9E54FE42AAAA1ACF Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x09360000-0x09E5FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.63s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS+ROFS3 Certificate... Programming Status OK! All blocks written OK! Time taken 6.703s Flashing Speed: 7591,04 kBit/S Restarting MCU... Processing RM-504_31.0.005_C06_prd.rofs3.fpsx (APE)... Processing RM-504_31.0.005_007_000_U001.uda.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 1D500103BC840052C50B7E9B68EBA70A140FC214 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-504_31.0.005_007_000_U001.uda.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: F2B05364E563A348608C1C3C9E54FE42AAAA1ACF Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x09E60000-0x0F71FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.484s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Programming Status OK! All blocks written OK! Time taken 7.766s Flashing Speed: 6625,19 kBit/S Restarting MCU... Processing RM-504_31.0.005_007_000_U001.uda.fpsx (APE)... All images processed OK! Processing post flash tasks... Setting Factory Defaults... Factory defaults OK Reading info... MCU Version V ICPR72_10w21 MCU Date 26-05-10 Product RM-504 (Nokia 5530 XpressMusic) Manufacturer (c) Nokia IMEI 12345610654321? IMEI Spare 1A32541660452301 IMEI SV 1332541660452311F7000000 CNT v 30.0.001_001_000_U001, 05-03-10, vanilla, RM504 PSN 0 PSD 0000000000000000 LPSN 0 APE SW V 31.0.005 APE Variant V 31.0.005V 31.0.005 V 31.0.005 APE Test 09wk19v0.130 APE HW 256 APE ADSP 256 RETU 16 TAHVO 22 AHNE 11 RFIC 17141716 DSP ICPR72_10w16p1 Failed to read info -> Failed to read SP info Read info thread finished, continuing... Post flash tasks finished! Flashing successfully finished! Skipping RPL decryption... Parsing decrypted RPL... Processing FBUS Part... Writing Product Code... Writing PSN... Writing HWID... Writing Simlock... Handling as SL3 Simlock Data Handling as SIMLOCK1 Format Reading Security Block... Security block OK and saved to "RM-504_12345610654321_22.12.2011_143640.SecurityBlock.PM" 15 Digits NCK Found Simlock ACCEPTED OK ! Writing Superdongle key... Superdongle Key ACCEPTED OK ! Writing CMLA key... CMLA Key ACCEPTED OK ! Writing WMDRM PD Data... WMDRM PD Data ACCEPTED OK ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 1D500103BC840052C50B7E9B68EBA70A140FC214 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 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]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: F2B05364E563A348608C1C3C9E54FE42AAAA1ACF APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits CMT NPC Erased CMT NPC Written CMT HWC Erased CMT HWC Written CMT CCC Erased CMT CCC Written Restarting MCU... Write RPL Finished! SX4 Authorization / SD Repair Procedure Started.... "1D500103BC840052C50B7E9B68EBA70A140FC214.C0000CC9" Exists, That is good... MCU Version V ICPR72_10w21 MCU Date 26-05-10 Product RM-504 (Nokia 5530 XpressMusic) Manufacturer (c) Nokia IMEI 358253чччччччччч Mastercode 3256165650 Reading Security Block... Security block OK and saved to "RM-504_358253037560946_22.12.2011_143655.SecurityBlock.PM" SX4 Status: Not authorized (74) Started mutual authenthication with card... Receiving Phone Seed 1... Phone Seed 1 Received Sending calculated Data 1, and expecting Seed 2... Calculated Data 1 accepted, Phone Seed 2 Received Sending calculated Data 2 Calculated Data 2 sent, Checking Authorization Status again Authorization successfully finished! Looking for Virgin PM In Database... Found, writing... [1,0] Written, Length: 114 bytes, Status: OK [1,2] Written, Length: 98 bytes, Status: OK [1,4] Written, Length: 110 bytes, Status: OK [1,6] Written, Length: 98 bytes, Status: OK [1,8] Written, Length: 110 bytes, Status: OK [1,13] Written, Length: 98 bytes, Status: OK [1,16] Written, Length: 98 bytes, Status: OK [1,18] Written, Length: 98 bytes, Status: OK [1,20] Written, Length: 98 bytes, Status: OK [1,24] Written, Length: 84 bytes, Status: OK [1,25] Written, Length: 4 bytes, Status: OK [1,26] Written, Length: 110 bytes, Status: OK [1,28] Written, Length: 98 bytes, Status: OK [1,29] Written, Length: 10 bytes, Status: OK [1,31] Written, Length: 98 bytes, Status: OK [1,34] Written, Length: 80 bytes, Status: OK [309,0] Written, Length: 4 bytes, Status: OK [309,1] Written, Length: 2 bytes, Status: OK [309,2] Written, Length: 12 bytes, Status: OK [309,4] Written, Length: 12 bytes, Status: OK [309,5] Written, Length: 12 bytes, Status: OK [309,7] Written, Length: 12 bytes, Status: OK [309,8] Written, Length: 12 bytes, Status: OK [309,17] Written, Length: 12 bytes, Status: OK Write PM Finished, Record written OK: 24, Record written NOT OK: 0 MCU Version V ICPR72_10w21 MCU Date 26-05-10 Product RM-504 (Nokia 5530 XpressMusic) Manufacturer (c) Nokia IMEI 358253чччччччччч Mastercode 3256165650 IMEI Spare 3A85520чччччччччч IMEI SV 338552чччччччччччччччч00 CNT v 30.0.001_001_000_U001, 05-03-10, vanilla, RM504 PSN CCJ673375 Product Code 0573173 PSD 0000000000000000 LPSN 0 WLAN MAC 347E3985995A APE SW V 31.0.005 APE Variant V 31.0.005V 31.0.005 V 31.0.005 APE Test 09wk19v0.130 APE HW 256 APE ADSP 256 RETU 16 TAHVO 22 AHNE 11 HW 0802 RFIC 17141716 DSP ICPR72_10w16p1 Simlock Server SIMLOCK SERVER Simlock Key 2440700000000000 Simlock Profile 0000000000000000 Simlock Key Cnt 0 Simlock FBUS Cnt 0 Simlock [1,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [1,2] State: OPENED Type: GID Data: FFFF Simlock [1,3] State: OPENED Type: GID Data: FFFF Simlock [1,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [1,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [2,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [2,2] State: OPENED Type: GID Data: FFFF Simlock [2,3] State: OPENED Type: GID Data: FFFF Simlock [2,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [2,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [3,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [3,2] State: OPENED Type: GID Data: FFFF Simlock [3,3] State: OPENED Type: GID Data: FFFF Simlock [3,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [3,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [4,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [4,2] State: OPENED Type: GID Data: FFFF Simlock [4,3] State: OPENED Type: GID Data: FFFF Simlock [4,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [4,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [5,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [5,2] State: OPENED Type: GID Data: FFFF Simlock [5,3] State: OPENED Type: GID Data: FFFF Simlock [5,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [5,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [6,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [6,2] State: OPENED Type: GID Data: FFFF Simlock [6,3] State: OPENED Type: GID Data: FFFF Simlock [6,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [6,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [7,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [7,2] State: OPENED Type: GID Data: FFFF Simlock [7,3] State: OPENED Type: GID Data: FFFF Simlock [7,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [7,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Последний раз редактировалось CAIIIA; 22.12.2011 в 14:30. |
|
|
|
|
22.12.2011, 13:22
|
#40 | |
|
Moderator
Регистрация: 23.02.2011
Адрес: Moldova-Chisinau
Сообщений: 1,975
Вес репутации: 1136  |
Re: N79 не могу записать RPL
Цитата:
|
|
|
|
|
