N73 Muerto Por Flash. |
 |
|
Bienvenido, invitado ( Identificarse | Registrarse )
 Clan GSM - Unión de los Expertos en Telefonía Celular > Cajas y Dongles GSM > Cementerio de Cajas (Sin Actualizaciones ni Soporte) > CYCLONE Box
|
  |
N73 Muerto Por Flash. |
 Oct 16 2012, 10:53 AM
Publicado:
#1
|
|
 Miembro del Clan  Grupo: Miembros Mensajes: 246 Agradecimientos: 1162 Registrado: 8-December 11 Miembro No.: 283,015  |
Saludos foro, mi problema es el siguiente, tengo un N73 el cual encendia perfectamente el día de ayer pero tenía el problema que estaba muy lento y se pasmaba por ratos así que me dispuse a pasarle flash, mi error fue no darme cuenta que version de flash trenía previamente y le pase la version que tenia en mi base, por tanto no descarto un downgrade. La cosa es que ahora el equipo solo enciende en pantalla azul y nada más. Ya probé montarle varias flash y siempre obtengo el mismo resultado, ya intenté con las versiones más altas de RM-132 y RM-133 y lo mismo, cuando intento hacer downgrade marcando la respectiva casilla el programa me marca error aplicando el parche para downgrade y así me veo en la necesidad de pedir sus puntos de vista compañeros, alguno sabe el modo de salir de este embrollo?? De antemano gracias.
-------------------- Y ES QUE TUVE DOS MAESTROS, SEÑOR LIBRO Y SEÑOR CALLE..." |
 |
 
|
| Anunciante Autorizado |
Oct 16 2012, 10:53 AM
Publicado:
#
|
 Estas ofertas pudieran interesarte. |
|
|
|
|
|
Oct 16 2012, 11:28 AM
Publicado:
#2
|
|
|
Miembro del Clan Grupo: Miembros Mensajes: 246 Agradecimientos: 1162 Registrado: 8-December 11 Miembro No.: 283,015 |
Este el el log de operaciones del full flash, me acabo de percatar que el imei lo marca corrupto:
Processing pre flash tasks... Backing up RPL... RPL Creation started... Processing CMT Part... Warning: Phone not detected, using Rap Public ID in FileName and reading Certificates Only Booting CMT... APE_SYSTEM_ASIC_ID: 17100708 APE_ASIC_MODE_ID: 00 APE_PUBLIC_ID: 677E981EEF4809315F90F27446CA3499647FD59B APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000 APE_BOOT_ROM_CRC: 1DFD6613 APE_SECURE_ROM_CRC: 2C872FD4 CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 0700010DD6F10154C0AE959254B9BE5697782144 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1 CMT_BOOT_ROM_CRC: 273F6D55 CMT_SECURE_ROM_CRC: DFAAF68F CMT Ready! Searching for BootCode: Single Line 8Bit RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.30.0, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 0x00EC22E800006921, Samsung, NOR FlashContent[0,CMT]: 00000000000000000000000000000000, NOR FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Searching for BootCode: Single Line 8Bit FlashChip 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V RAP3Gv3_algo_fps8.fg, Type: Algorithm, Rev: 0, Algo: BB5 ALGORITHM Flashbus Write baud set to 2.0Mbits Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: Single Line 8Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: Single Line 8Bit FlashChip 0x00EC00A1 (Samsung), Size: 128MBytes, VPP: 21V h3_sam_nand_xsr.fg, Type: Algorithm, Rev: 0.1.49.0, Algo: OMAP1710 UNISTORE-II-1.2.1 ALG Box VPP disabled Internal APE Phone VPP Enabled PAPUBKEYS Hash for APE: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Flashbus Write baud set to 5.0Mbits Storing NPC... CMT CCC Not Found CMT HWC Not Found Storing VARIANT... CMT PARTNERC Not Found Processing APE Part... Storing Product Code... Storing PSN... Storing HWID... APE NPC Not Found APE CCC Not Found APE HWC Not Found APE VARIANT Not Found APE PARTNERC Not Found Restarting MCU... RPL Saved OK RPL backup thread finished, continuing... Pre flash tasks finished, continuing... Processing N73_4.0850.43.1.1_western_C00_PRD_cc.fpsx (CMT)... Booting CMT... APE_SYSTEM_ASIC_ID: 17100708 APE_ASIC_MODE_ID: 00 APE_PUBLIC_ID: 677E981EEF4809315F90F27446CA3499647FD59B APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000 APE_BOOT_ROM_CRC: 1DFD6613 APE_SECURE_ROM_CRC: 2C872FD4 CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 0700010DD6F10154C0AE959254B9BE5697782144 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1 CMT_BOOT_ROM_CRC: 273F6D55 CMT_SECURE_ROM_CRC: DFAAF68F CMT Ready! N73_4.0850.43.1.1_western_C00_PRD_cc.fpsx, Type: Flash Image, Algo: BB5, BB5 ALGORITHM, BB5, OMAP1710 UNISTORE-II-1.2.1 ALG Searching for BootCode: Single Line 8Bit RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.30.0, Algo: BB5 Flashbus Write baud set to 51Kbits Flashbus Read baud set to 98Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 0x00EC22E800006921, Samsung, NOR FlashContent[0,CMT]: 00000000000000000000000000000000, NOR FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Searching for BootCode: Single Line 8Bit FlashChip 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V RAP3Gv3_algo_fps8.fg, Type: Algorithm, Rev: 0, Algo: BB5 ALGORITHM Flashbus Write baud set to 2.0Mbits Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Flashbus Write baud set to 5.0Mbits Partitioning... Partitioning OK Started group flash erase EraseArea[0,CMT]: 0x00080000-0x007318CD, NOR EraseArea[0,CMT]: 0x00000000-0x0005FFFF, NOR EraseArea[0,CMT]: 0x001E0000-0x001FFFFF, NOR EraseArea[0,CMT]: 0x00880000-0x00FEFFFF, NOR Waiting 320s for erasure finish... Erase taken 41.625s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT NOLO Certificate... Writing CMT KEYS Certificate... Writing CMT PRIMAPP Certificate... Writing CMT PASUBTOC Certificate... Writing CMT PAPUBKEYS Certificate... Writing CMT UPDAPP Certificate... Writing CMT ADL Certificate... Writing CMT DSP0 Certificate... Writing CMT MCUSW Certificate... Programming Status OK! All blocks written OK! Time taken 41.359s Flashing Speed: 9375.57 kBit/S Restarting MCU... Processing N73_4.0850.43.1.1_western_C00_PRD_cc.fpsx (APE)... Booting CMT... APE_SYSTEM_ASIC_ID: 17100708 APE_ASIC_MODE_ID: 00 APE_PUBLIC_ID: 677E981EEF4809315F90F27446CA3499647FD59B APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000 APE_BOOT_ROM_CRC: 1DFD6613 APE_SECURE_ROM_CRC: 2C872FD4 CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 0700010DD6F10154C0AE959254B9BE5697782144 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1 CMT_BOOT_ROM_CRC: 273F6D55 CMT_SECURE_ROM_CRC: DFAAF68F CMT Ready! N73_4.0850.43.1.1_western_C00_PRD_cc.fpsx, Type: Flash Image, Algo: BB5, BB5 ALGORITHM, BB5, OMAP1710 UNISTORE-II-1.2.1 ALG Searching for BootCode: Single Line 8Bit RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.30.0, Algo: BB5 Flashbus Write baud set to 51Kbits Flashbus Read baud set to 98Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 0x00EC22E800006921, Samsung, NOR FlashContent[0,CMT]: 00000000000000000000000000000000, NOR FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Searching for BootCode: Single Line 8Bit FlashChip 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V RAP3Gv3_algo_fps8.fg, Type: Algorithm, Rev: 0, Algo: BB5 ALGORITHM Flashbus Write baud set to 2.0Mbits Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: Single Line 8Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: Single Line 8Bit FlashChip 0x00EC00A1 (Samsung), Size: 128MBytes, VPP: 21V h3_sam_nand_xsr.fg, Type: Algorithm, Rev: 0.1.49.0, Algo: OMAP1710 UNISTORE-II-1.2.1 ALG Box VPP disabled Internal APE Phone VPP Enabled PAPUBKEYS Hash for APE: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Flashbus Write baud set to 5.0Mbits Partitioning... Partitioning OK Started group flash erase EraseArea[0,APE]: 0x00000000-0x0007FFFF, NAND EraseArea[0,APE]: 0x00080000-0x000FFFFF, NAND EraseArea[0,APE]: 0x00100000-0x0025FFFF, NAND EraseArea[0,APE]: 0x003C0000-0x04E1FFFF, NAND Waiting 320s for erasure finish... Erase taken 1.63s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing APE KEYS Certificate... Writing APE X-LOADER Certificate... Writing APE PRIMAPP Certificate... Writing APE SOS+LOADER Certificate... Writing APE SOS*UPDAPP Certificate... Writing APE SOS+UZIP Certificate... Writing APE PAPUBKEYS Certificate... Writing APE PASUBTOC Certificate... Writing APE ADL Certificate... Writing APE SOS+XZIP Certificate... Writing APE SOS*CORE Certificate... Writing APE SOS+ROFS Certificate... Writing APE SOS+ROFX Certificate... Programming Status OK! All blocks written OK! Time taken 133.750s Flashing Speed: 2899.17 kBit/S Restarting MCU... Processing N73_rofx_4.0850.43.1.1_PRD.VS4 (CMT)... Processing N73_rofx_4.0850.43.1.1_PRD.VS4 (APE)... Booting CMT... APE_SYSTEM_ASIC_ID: 17100708 APE_ASIC_MODE_ID: 00 APE_PUBLIC_ID: 677E981EEF4809315F90F27446CA3499647FD59B APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000 APE_BOOT_ROM_CRC: 1DFD6613 APE_SECURE_ROM_CRC: 2C872FD4 CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 0700010DD6F10154C0AE959254B9BE5697782144 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1 CMT_BOOT_ROM_CRC: 273F6D55 CMT_SECURE_ROM_CRC: DFAAF68F CMT Ready! N73_rofx_4.0850.43.1.1_PRD.VS4, Type: Flash Image, Algo: BB5, OMAP1710 UNISTORE-II-1.2.1 ALG, BB5, BB5 ALGORITHM Searching for BootCode: Single Line 8Bit RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.30.0, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 100Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 0x00EC22E800006921, Samsung, NOR FlashContent[0,CMT]: 00000000000000000000000000000000, NOR FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Searching for BootCode: Single Line 8Bit FlashChip 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V RAP3Gv3_algo_fps8.fg, Type: Algorithm, Rev: 0, Algo: BB5 ALGORITHM Flashbus Write baud set to 2.0Mbits Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: Single Line 8Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: Single Line 8Bit FlashChip 0x00EC00A1 (Samsung), Size: 128MBytes, VPP: 21V h3_sam_nand_xsr.fg, Type: Algorithm, Rev: 0.1.49.0, Algo: OMAP1710 UNISTORE-II-1.2.1 ALG Box VPP disabled Internal APE Phone VPP Enabled PAPUBKEYS Hash for APE: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Flashbus Write baud set to 5.0Mbits Partitioning... Partitioning OK Started group flash erase EraseArea[0,APE]: 0x03920000-0x04E1FFFF, NAND Waiting 320s for erasure finish... Erase taken 0.296s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing APE SOS+ROFX Certificate... Programming Status OK! All blocks written OK! Time taken 55.406s Flashing Speed: 2320.18 kBit/S Restarting MCU... Processing N73_userarea_4.0850.43.1.1.U03 (CMT)... Processing N73_userarea_4.0850.43.1.1.U03 (APE)... Booting CMT... APE_SYSTEM_ASIC_ID: 17100708 APE_ASIC_MODE_ID: 00 APE_PUBLIC_ID: 677E981EEF4809315F90F27446CA3499647FD59B APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000 APE_BOOT_ROM_CRC: 1DFD6613 APE_SECURE_ROM_CRC: 2C872FD4 CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 0700010DD6F10154C0AE959254B9BE5697782144 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1 CMT_BOOT_ROM_CRC: 273F6D55 CMT_SECURE_ROM_CRC: DFAAF68F CMT Ready! N73_userarea_4.0850.43.1.1.U03, Type: Flash Image, Algo: BB5, OMAP1710 UNISTORE-II-1.2.1 ALG, BB5, BB5 ALGORITHM Searching for BootCode: Single Line 8Bit RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.30.0, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 100Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 0x00EC22E800006921, Samsung, NOR FlashContent[0,CMT]: 00000000000000000000000000000000, NOR FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Searching for BootCode: Single Line 8Bit FlashChip 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V RAP3Gv3_algo_fps8.fg, Type: Algorithm, Rev: 0, Algo: BB5 ALGORITHM Flashbus Write baud set to 2.0Mbits Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: Single Line 8Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: Single Line 8Bit FlashChip 0x00EC00A1 (Samsung), Size: 128MBytes, VPP: 21V h3_sam_nand_xsr.fg, Type: Algorithm, Rev: 0.1.49.0, Algo: OMAP1710 UNISTORE-II-1.2.1 ALG Box VPP disabled Internal APE Phone VPP Enabled PAPUBKEYS Hash for APE: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,APE]: 0x04E20000-0x07C9FFFF, NAND Waiting 320s for erasure finish... Erase taken 0.640s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Programming Status OK! All blocks written OK! Time taken 17.375s Flashing Speed: 2471.78 kBit/S Restarting MCU... All images processed OK! Processing post flash tasks... Setting Factory Defaults... Factory defaults OK Reading info... MCU Version V 05wk47v62 MCU Date 05-12-08 Product RM-132 (Nokia N73) Manufacturer © Nokia. IMEI 12345610654321? IMEI Spare 1A32541660452301 IMEI SV 1332541660452381F0000000 PSD 0000002200000000 RETU 15 TAHVO 22 AHNE 30 RFIC 17211721 DSP scarfe_05wk46v50P1 Simlock Server SIMLOCK SERVER VERSION 63 Simlock Key 2440700000000000 Simlock Profile 8000000000000006 Simlock Key Cnt 0 Simlock FBUS Cnt 0 Simlock [1,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [1,2] State: OPENED Type: GID Data: FFFF Simlock [1,3] State: OPENED Type: GID Data: FFFF Simlock [1,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [1,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [2,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [2,2] State: OPENED Type: GID Data: FFFF Simlock [2,3] State: OPENED Type: GID Data: FFFF Simlock [2,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [2,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [3,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [3,2] State: OPENED Type: GID Data: FFFF Simlock [3,3] State: OPENED Type: GID Data: FFFF Simlock [3,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [3,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [4,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [4,2] State: OPENED Type: GID Data: FFFF Simlock [4,3] State: OPENED Type: GID Data: FFFF Simlock [4,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [4,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [5,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [5,2] State: OPENED Type: GID Data: FFFF Simlock [5,3] State: OPENED Type: GID Data: FFFF Simlock [5,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [5,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [6,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [6,2] State: OPENED Type: GID Data: FFFF Simlock [6,3] State: OPENED Type: GID Data: FFFF Simlock [6,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [6,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [7,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [7,2] State: OPENED Type: GID Data: FFFF Simlock [7,3] State: OPENED Type: GID Data: FFFF Simlock [7,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [7,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Read info thread finished, continuing... Post flash tasks finished! Flashing successfully finished! Alguna sugerencia compañeros?? -------------------- Y ES QUE TUVE DOS MAESTROS, SEÑOR LIBRO Y SEÑOR CALLE..." |
|
|
|
|
Oct 16 2012, 11:37 AM
Publicado:
#3
|
|
 Sensei Supremo del Clan Grupo: Miembros Mensajes: 3,967 Agradecimientos: 10347 Registrado: 1-September 09 Desde: La Serena & Arica - Chile Miembro No.: 57,097 |
CITA(Vers3k @ Oct 16 2012, 11:28 AM)  Este el el log de operaciones del full flash, me acabo de percatar que el imei lo marca corrupto: Processing pre flash tasks... Backing up RPL... RPL Creation started... Processing CMT Part... Warning: Phone not detected, using Rap Public ID in FileName and reading Certificates Only Booting CMT... APE_SYSTEM_ASIC_ID: 17100708 APE_ASIC_MODE_ID: 00 APE_PUBLIC_ID: 677E981EEF4809315F90F27446CA3499647FD59B APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000 APE_BOOT_ROM_CRC: 1DFD6613 APE_SECURE_ROM_CRC: 2C872FD4 CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 0700010DD6F10154C0AE959254B9BE5697782144 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1 CMT_BOOT_ROM_CRC: 273F6D55 CMT_SECURE_ROM_CRC: DFAAF68F CMT Ready! Searching for BootCode: Single Line 8Bit RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.30.0, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 0x00EC22E800006921, Samsung, NOR FlashContent[0,CMT]: 00000000000000000000000000000000, NOR FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Searching for BootCode: Single Line 8Bit FlashChip 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V RAP3Gv3_algo_fps8.fg, Type: Algorithm, Rev: 0, Algo: BB5 ALGORITHM Flashbus Write baud set to 2.0Mbits Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: Single Line 8Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: Single Line 8Bit FlashChip 0x00EC00A1 (Samsung), Size: 128MBytes, VPP: 21V h3_sam_nand_xsr.fg, Type: Algorithm, Rev: 0.1.49.0, Algo: OMAP1710 UNISTORE-II-1.2.1 ALG Box VPP disabled Internal APE Phone VPP Enabled PAPUBKEYS Hash for APE: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Flashbus Write baud set to 5.0Mbits Storing NPC... CMT CCC Not Found CMT HWC Not Found Storing VARIANT... CMT PARTNERC Not Found Processing APE Part... Storing Product Code... Storing PSN... Storing HWID... APE NPC Not Found APE CCC Not Found APE HWC Not Found APE VARIANT Not Found APE PARTNERC Not Found Restarting MCU... RPL Saved OK RPL backup thread finished, continuing... Pre flash tasks finished, continuing... Processing N73_4.0850.43.1.1_western_C00_PRD_cc.fpsx (CMT)... Booting CMT... APE_SYSTEM_ASIC_ID: 17100708 APE_ASIC_MODE_ID: 00 APE_PUBLIC_ID: 677E981EEF4809315F90F27446CA3499647FD59B APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000 APE_BOOT_ROM_CRC: 1DFD6613 APE_SECURE_ROM_CRC: 2C872FD4 CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 0700010DD6F10154C0AE959254B9BE5697782144 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1 CMT_BOOT_ROM_CRC: 273F6D55 CMT_SECURE_ROM_CRC: DFAAF68F CMT Ready! N73_4.0850.43.1.1_western_C00_PRD_cc.fpsx, Type: Flash Image, Algo: BB5, BB5 ALGORITHM, BB5, OMAP1710 UNISTORE-II-1.2.1 ALG Searching for BootCode: Single Line 8Bit RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.30.0, Algo: BB5 Flashbus Write baud set to 51Kbits Flashbus Read baud set to 98Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 0x00EC22E800006921, Samsung, NOR FlashContent[0,CMT]: 00000000000000000000000000000000, NOR FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Searching for BootCode: Single Line 8Bit FlashChip 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V RAP3Gv3_algo_fps8.fg, Type: Algorithm, Rev: 0, Algo: BB5 ALGORITHM Flashbus Write baud set to 2.0Mbits Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Flashbus Write baud set to 5.0Mbits Partitioning... Partitioning OK Started group flash erase EraseArea[0,CMT]: 0x00080000-0x007318CD, NOR EraseArea[0,CMT]: 0x00000000-0x0005FFFF, NOR EraseArea[0,CMT]: 0x001E0000-0x001FFFFF, NOR EraseArea[0,CMT]: 0x00880000-0x00FEFFFF, NOR Waiting 320s for erasure finish... Erase taken 41.625s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT NOLO Certificate... Writing CMT KEYS Certificate... Writing CMT PRIMAPP Certificate... Writing CMT PASUBTOC Certificate... Writing CMT PAPUBKEYS Certificate... Writing CMT UPDAPP Certificate... Writing CMT ADL Certificate... Writing CMT DSP0 Certificate... Writing CMT MCUSW Certificate... Programming Status OK! All blocks written OK! Time taken 41.359s Flashing Speed: 9375.57 kBit/S Restarting MCU... Processing N73_4.0850.43.1.1_western_C00_PRD_cc.fpsx (APE)... Booting CMT... APE_SYSTEM_ASIC_ID: 17100708 APE_ASIC_MODE_ID: 00 APE_PUBLIC_ID: 677E981EEF4809315F90F27446CA3499647FD59B APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000 APE_BOOT_ROM_CRC: 1DFD6613 APE_SECURE_ROM_CRC: 2C872FD4 CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 0700010DD6F10154C0AE959254B9BE5697782144 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1 CMT_BOOT_ROM_CRC: 273F6D55 CMT_SECURE_ROM_CRC: DFAAF68F CMT Ready! N73_4.0850.43.1.1_western_C00_PRD_cc.fpsx, Type: Flash Image, Algo: BB5, BB5 ALGORITHM, BB5, OMAP1710 UNISTORE-II-1.2.1 ALG Searching for BootCode: Single Line 8Bit RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.30.0, Algo: BB5 Flashbus Write baud set to 51Kbits Flashbus Read baud set to 98Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 0x00EC22E800006921, Samsung, NOR FlashContent[0,CMT]: 00000000000000000000000000000000, NOR FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Searching for BootCode: Single Line 8Bit FlashChip 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V RAP3Gv3_algo_fps8.fg, Type: Algorithm, Rev: 0, Algo: BB5 ALGORITHM Flashbus Write baud set to 2.0Mbits Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: Single Line 8Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: Single Line 8Bit FlashChip 0x00EC00A1 (Samsung), Size: 128MBytes, VPP: 21V h3_sam_nand_xsr.fg, Type: Algorithm, Rev: 0.1.49.0, Algo: OMAP1710 UNISTORE-II-1.2.1 ALG Box VPP disabled Internal APE Phone VPP Enabled PAPUBKEYS Hash for APE: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Flashbus Write baud set to 5.0Mbits Partitioning... Partitioning OK Started group flash erase EraseArea[0,APE]: 0x00000000-0x0007FFFF, NAND EraseArea[0,APE]: 0x00080000-0x000FFFFF, NAND EraseArea[0,APE]: 0x00100000-0x0025FFFF, NAND EraseArea[0,APE]: 0x003C0000-0x04E1FFFF, NAND Waiting 320s for erasure finish... Erase taken 1.63s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing APE KEYS Certificate... Writing APE X-LOADER Certificate... Writing APE PRIMAPP Certificate... Writing APE SOS+LOADER Certificate... Writing APE SOS*UPDAPP Certificate... Writing APE SOS+UZIP Certificate... Writing APE PAPUBKEYS Certificate... Writing APE PASUBTOC Certificate... Writing APE ADL Certificate... Writing APE SOS+XZIP Certificate... Writing APE SOS*CORE Certificate... Writing APE SOS+ROFS Certificate... Writing APE SOS+ROFX Certificate... Programming Status OK! All blocks written OK! Time taken 133.750s Flashing Speed: 2899.17 kBit/S Restarting MCU... Processing N73_rofx_4.0850.43.1.1_PRD.VS4 (CMT)... Processing N73_rofx_4.0850.43.1.1_PRD.VS4 (APE)... Booting CMT... APE_SYSTEM_ASIC_ID: 17100708 APE_ASIC_MODE_ID: 00 APE_PUBLIC_ID: 677E981EEF4809315F90F27446CA3499647FD59B APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000 APE_BOOT_ROM_CRC: 1DFD6613 APE_SECURE_ROM_CRC: 2C872FD4 CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 0700010DD6F10154C0AE959254B9BE5697782144 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1 CMT_BOOT_ROM_CRC: 273F6D55 CMT_SECURE_ROM_CRC: DFAAF68F CMT Ready! N73_rofx_4.0850.43.1.1_PRD.VS4, Type: Flash Image, Algo: BB5, OMAP1710 UNISTORE-II-1.2.1 ALG, BB5, BB5 ALGORITHM Searching for BootCode: Single Line 8Bit RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.30.0, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 100Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 0x00EC22E800006921, Samsung, NOR FlashContent[0,CMT]: 00000000000000000000000000000000, NOR FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Searching for BootCode: Single Line 8Bit FlashChip 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V RAP3Gv3_algo_fps8.fg, Type: Algorithm, Rev: 0, Algo: BB5 ALGORITHM Flashbus Write baud set to 2.0Mbits Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: Single Line 8Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: Single Line 8Bit FlashChip 0x00EC00A1 (Samsung), Size: 128MBytes, VPP: 21V h3_sam_nand_xsr.fg, Type: Algorithm, Rev: 0.1.49.0, Algo: OMAP1710 UNISTORE-II-1.2.1 ALG Box VPP disabled Internal APE Phone VPP Enabled PAPUBKEYS Hash for APE: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Flashbus Write baud set to 5.0Mbits Partitioning... Partitioning OK Started group flash erase EraseArea[0,APE]: 0x03920000-0x04E1FFFF, NAND Waiting 320s for erasure finish... Erase taken 0.296s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing APE SOS+ROFX Certificate... Programming Status OK! All blocks written OK! Time taken 55.406s Flashing Speed: 2320.18 kBit/S Restarting MCU... Processing N73_userarea_4.0850.43.1.1.U03 (CMT)... Processing N73_userarea_4.0850.43.1.1.U03 (APE)... Booting CMT... APE_SYSTEM_ASIC_ID: 17100708 APE_ASIC_MODE_ID: 00 APE_PUBLIC_ID: 677E981EEF4809315F90F27446CA3499647FD59B APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000 APE_BOOT_ROM_CRC: 1DFD6613 APE_SECURE_ROM_CRC: 2C872FD4 CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 0700010DD6F10154C0AE959254B9BE5697782144 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1 CMT_BOOT_ROM_CRC: 273F6D55 CMT_SECURE_ROM_CRC: DFAAF68F CMT Ready! N73_userarea_4.0850.43.1.1.U03, Type: Flash Image, Algo: BB5, OMAP1710 UNISTORE-II-1.2.1 ALG, BB5, BB5 ALGORITHM Searching for BootCode: Single Line 8Bit RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.30.0, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 100Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 0x00EC22E800006921, Samsung, NOR FlashContent[0,CMT]: 00000000000000000000000000000000, NOR FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Searching for BootCode: Single Line 8Bit FlashChip 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V RAP3Gv3_algo_fps8.fg, Type: Algorithm, Rev: 0, Algo: BB5 ALGORITHM Flashbus Write baud set to 2.0Mbits Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: Single Line 8Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: Single Line 8Bit FlashChip 0x00EC00A1 (Samsung), Size: 128MBytes, VPP: 21V h3_sam_nand_xsr.fg, Type: Algorithm, Rev: 0.1.49.0, Algo: OMAP1710 UNISTORE-II-1.2.1 ALG Box VPP disabled Internal APE Phone VPP Enabled PAPUBKEYS Hash for APE: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,APE]: 0x04E20000-0x07C9FFFF, NAND Waiting 320s for erasure finish... Erase taken 0.640s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Programming Status OK! All blocks written OK! Time taken 17.375s Flashing Speed: 2471.78 kBit/S Restarting MCU... All images processed OK! Processing post flash tasks... Setting Factory Defaults... Factory defaults OK Reading info... MCU Version V 05wk47v62 MCU Date 05-12-08 Product RM-132 (Nokia N73) Manufacturer © Nokia. IMEI 12345610654321? IMEI Spare 1A32541660452301 IMEI SV 1332541660452381F0000000 PSD 0000002200000000 RETU 15 TAHVO 22 AHNE 30 RFIC 17211721 DSP scarfe_05wk46v50P1 Simlock Server SIMLOCK SERVER VERSION 63 Simlock Key 2440700000000000 Simlock Profile 8000000000000006 Simlock Key Cnt 0 Simlock FBUS Cnt 0 Simlock [1,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [1,2] State: OPENED Type: GID Data: FFFF Simlock [1,3] State: OPENED Type: GID Data: FFFF Simlock [1,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [1,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [2,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [2,2] State: OPENED Type: GID Data: FFFF Simlock [2,3] State: OPENED Type: GID Data: FFFF Simlock [2,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [2,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [3,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [3,2] State: OPENED Type: GID Data: FFFF Simlock [3,3] State: OPENED Type: GID Data: FFFF Simlock [3,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [3,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [4,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [4,2] State: OPENED Type: GID Data: FFFF Simlock [4,3] State: OPENED Type: GID Data: FFFF Simlock [4,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [4,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [5,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [5,2] State: OPENED Type: GID Data: FFFF Simlock [5,3] State: OPENED Type: GID Data: FFFF Simlock [5,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [5,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [6,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [6,2] State: OPENED Type: GID Data: FFFF Simlock [6,3] State: OPENED Type: GID Data: FFFF Simlock [6,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [6,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [7,1] State: OPENED Type: MCC-MNC Data: FFFFFF Simlock [7,2] State: OPENED Type: GID Data: FFFF Simlock [7,3] State: OPENED Type: GID Data: FFFF Simlock [7,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Simlock [7,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF Read info thread finished, continuing... Post flash tasks finished! Flashing successfully finished! Alguna sugerencia compañeros?? BB5 > Security > Auto-Recovery IMEI (NCP) y ve si recuperas el Imei. -------------------- No Se Te Descuentan Agradecimientos por Darle A El Botón Dar Gracias!
|
|
|
|
A continuacion 1 usuario(s) le Agradece(n) a 3zr3vnoc por su Colaboracion: Vers3k | |
|
Oct 16 2012, 11:59 AM
Publicado:
#4
|
|
|
Miembro del Clan Grupo: Miembros Mensajes: 246 Agradecimientos: 1162 Registrado: 8-December 11 Miembro No.: 283,015 |
Esto fue lo que conseguí con Auto Recovery:
Started IMEI Recovery... Booting CMT... APE_SYSTEM_ASIC_ID: 17100708 APE_ASIC_MODE_ID: 00 APE_PUBLIC_ID: 677E981EEF4809315F90F27446CA3499647FD59B APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000 APE_BOOT_ROM_CRC: 1DFD6613 APE_SECURE_ROM_CRC: 2C872FD4 CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 0700010DD6F10154C0AE959254B9BE5697782144 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1 CMT_BOOT_ROM_CRC: 273F6D55 CMT_SECURE_ROM_CRC: DFAAF68F CMT Ready! Searching for BootCode: Single Line 8Bit RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.30.0, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 0x00EC22E800006921, Samsung, NOR FlashContent[0,CMT]: 00000000000000000000000000000000, NOR FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Searching for BootCode: Single Line 8Bit FlashChip 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V RAP3Gv3_algo_fps8.fg, Type: Algorithm, Rev: 0, Algo: BB5 ALGORITHM Flashbus Write baud set to 2.0Mbits Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: Single Line 8Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: Single Line 8Bit FlashChip 0x00EC00A1 (Samsung), Size: 128MBytes, VPP: 21V h3_sam_nand_xsr.fg, Type: Algorithm, Rev: 0.1.49.0, Algo: OMAP1710 UNISTORE-II-1.2.1 ALG Box VPP disabled Internal APE Phone VPP Enabled PAPUBKEYS Hash for APE: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Flashbus Write baud set to 5.0Mbits Looking NPC for 0700010DD6F10154C0AE959254B9BE5697782144... Failed to Recovery IMEI -> Range check error Y esto es lo que me da el Analize Security: Started Phone Security Analysis... MCU Version V 05wk47v62 MCU Date 05-12-08 Product RM-133 (Nokia N73) Manufacturer © Nokia. IMEI 12345610654321? Reading Security Block... Security block OK and saved to "RM-133_12345610654321_16102012_115256 a.m..SecurityBlock.PM" Step 1 : Testing SIMLOCK SIMLOCK SEFLTEST PASSED OK! Step 2 : Testing SECURITY SECURITY SEFLTEST PASSED OK! Step 3 : Analyzing Security Block "0700010DD6F10154C0AE959254B9BE5697782144.C0002D15" Exists, That is good... 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... 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! -------------------- Y ES QUE TUVE DOS MAESTROS, SEÑOR LIBRO Y SEÑOR CALLE..." |
|
|
|
 Oct 16 2012, 12:56 PM
Publicado:
#5
|
|
|
Sensei Supremo del Clan Grupo: Miembros Mensajes: 3,967 Agradecimientos: 10347 Registrado: 1-September 09 Desde: La Serena & Arica - Chile Miembro No.: 57,097 |
CITA(Vers3k @ Oct 16 2012, 11:59 AM) Esto fue lo que conseguí con Auto Recovery: Started IMEI Recovery... Booting CMT... APE_SYSTEM_ASIC_ID: 17100708 APE_ASIC_MODE_ID: 00 APE_PUBLIC_ID: 677E981EEF4809315F90F27446CA3499647FD59B APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000 APE_BOOT_ROM_CRC: 1DFD6613 APE_SECURE_ROM_CRC: 2C872FD4 CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101013000 CMT_EM_ASIC_ID: 00000295 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 0700010DD6F10154C0AE959254B9BE5697782144 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1 CMT_BOOT_ROM_CRC: 273F6D55 CMT_SECURE_ROM_CRC: DFAAF68F CMT Ready! Searching for BootCode: Single Line 8Bit RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.30.0, Algo: BB5 Flashbus Write baud set to 1.0Mbits Flashbus Read baud set to 98Kbits Using OLD BB5 FLASHING PROTOCOL If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 0x00EC22E800006921, Samsung, NOR FlashContent[0,CMT]: 00000000000000000000000000000000, NOR FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Searching for BootCode: Single Line 8Bit FlashChip 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V RAP3Gv3_algo_fps8.fg, Type: Algorithm, Rev: 0, Algo: BB5 ALGORITHM Flashbus Write baud set to 2.0Mbits Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Searching for BootCode: Single Line 8Bit helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND Searching for BootCode: Single Line 8Bit FlashChip 0x00EC00A1 (Samsung), Size: 128MBytes, VPP: 21V h3_sam_nand_xsr.fg, Type: Algorithm, Rev: 0.1.49.0, Algo: OMAP1710 UNISTORE-II-1.2.1 ALG Box VPP disabled Internal APE Phone VPP Enabled PAPUBKEYS Hash for APE: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Flashbus Write baud set to 5.0Mbits Looking NPC for 0700010DD6F10154C0AE959254B9BE5697782144... Failed to Recovery IMEI -> Range check error Y esto es lo que me da el Analize Security: Started Phone Security Analysis... MCU Version V 05wk47v62 MCU Date 05-12-08 Product RM-133 (Nokia N73) Manufacturer © Nokia. IMEI 12345610654321? Reading Security Block... Security block OK and saved to "RM-133_12345610654321_16102012_115256 a.m..SecurityBlock.PM" Step 1 : Testing SIMLOCK SIMLOCK SEFLTEST PASSED OK! Step 2 : Testing SECURITY SECURITY SEFLTEST PASSED OK! Step 3 : Analyzing Security Block "0700010DD6F10154C0AE959254B9BE5697782144.C0002D15" Exists, That is good... 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... 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! Perdiste el imei, tenias que hacer Backup RPL antes de todo. Te fijaste si ya tenia el imei así de antes? Sigue intentando ese método para ver si te deja el serial bien, si no a comprar un RPL se ha dicho. -------------------- No Se Te Descuentan Agradecimientos por Darle A El Botón Dar Gracias!
|
|
|
|
|
Oct 16 2012, 12:58 PM
Publicado:
#6
|
|
|
Miembro del Clan Grupo: Miembros Mensajes: 27 Agradecimientos: 6 Registrado: 13-October 09 Desde: en casa Miembro No.: 64,706 |
no tenes mxkey o fenix key?
|
|
|
|
|
Oct 16 2012, 01:04 PM
Publicado:
#7
|
|
|
Miembro del Clan Grupo: Miembros Mensajes: 246 Agradecimientos: 1162 Registrado: 8-December 11 Miembro No.: 283,015 |
Pues, acabo de adquirir MXBox pero aun no la instalo y mucho menos tengo experiencia en su uso.
-------------------- Y ES QUE TUVE DOS MAESTROS, SEÑOR LIBRO Y SEÑOR CALLE..." |
|
|
|
|
Oct 16 2012, 01:07 PM
Publicado:
#8
|
|
|
Miembro del Clan Grupo: Miembros Mensajes: 246 Agradecimientos: 1162 Registrado: 8-December 11 Miembro No.: 283,015 |
Y tengo una duda, es debido a la cuestion del imei que el equipo solo prende en azul?? Es decir, aun con el imei dañado debería encender normal ¿no?
-------------------- Y ES QUE TUVE DOS MAESTROS, SEÑOR LIBRO Y SEÑOR CALLE..." |
|
|
|
 Oct 16 2012, 01:51 PM
Publicado:
#9
|
|
|
Sensei Supremo del Clan Grupo: Miembros Mensajes: 3,967 Agradecimientos: 10347 Registrado: 1-September 09 Desde: La Serena & Arica - Chile Miembro No.: 57,097 |
CITA(efron @ Oct 16 2012, 12:58 PM) no tenes mxkey o fenix key? Para que necesita esas Dongle cuando está dañado el imei sin RPL? CITA(Vers3k @ Oct 16 2012, 01:07 PM) Y tengo una duda, es debido a la cuestion del imei que el equipo solo prende en azul?? Es decir, aun con el imei dañado debería encender normal ¿no? No es por el imei que prende azul, es porque le pusiste una versión mas baja y para eso se necesita hacer Full Erase y hace como 5 o 6 pasos para revivirlo, pero como no tienes el RPL te quedará en Fallo de encendido. -------------------- No Se Te Descuentan Agradecimientos por Darle A El Botón Dar Gracias!
|
|
|
|
A continuacion 1 usuario(s) le Agradece(n) a 3zr3vnoc por su Colaboracion: Vers3k | |
|
Oct 17 2012, 08:08 AM
Publicado:
#10
|
|
|
Miembro del Clan Grupo: Expulsados Mensajes: 276 Agradecimientos: 332 Registrado: 20-May 10 Desde: Nicaragua Miembro No.: 104,759 Pais: 
|
porque no posteas el selstest amigo no revisaste el telefono porque si dañaste el simlock te tendria que dar la pantalla y decirte contac service
pero no te tendria quedar en azul supongo Mensaje modificado por galois01 el Oct 17 2012, 08:13 AM |
|
|
|
|
Oct 18 2012, 10:29 AM
Publicado:
#11
|
|
|
Miembro del Clan Grupo: Miembros Mensajes: 246 Agradecimientos: 1162 Registrado: 8-December 11 Miembro No.: 283,015 |
He aquí los Selftests que no me sorprende que no hallan salido completos:
Selftests to proceed: 28 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 Passed ST_SECURITY_TEST Passed ST_PWR_KEY_TEST Passed ST_CURRENT_CONS_TEST Passed ST_BACKUP_BATT_TEST Failed ST_CMT_APE_WAKEUP_TEST Passed ST_SLEEPCLK_FREQ_TEST Passed ST_RADIO_TEST Passed ST_HOOKINT_TEST Passed ST_BTEMP_TEST Passed ST_VIBRA_TEST Passed ST_MBUS_RX_TX_LOOP_TEST Passed ST_EXT_DEVICE_TEST Passed ST_CDSP_RF_BB_IF_TEST Passed ST_CDSP_RF_SUPPLY_TEST Passed ST_CDSP_TX_IQ_TEST Passed ST_CDSP_TXC_DATA_TEST Failed ST_CDSP_PWR_DETECTOR_BIAS_TEST Passed ST_CDSP_RX_PLL_PHASE_LOCK_TEST Passed ST_CDSP_TX_PLL_PHASE_LOCK_TEST Failed ST_CDSP_WCDMA_TX_POWER_TEST Passed ST_CDSP_RX_IQ_LOOP_BACK_TEST Failed to make Selftests -> Phone is not responding for Selftest Request Estoy por hacer el Full Erase para aunque sea encenderlo pero no estoy del todo seguro ya que todavía creo en los Reyes Magos y espero poder recuperarlo. -------------------- Y ES QUE TUVE DOS MAESTROS, SEÑOR LIBRO Y SEÑOR CALLE..." |
|
|
|
|
Oct 24 2012, 12:49 AM
Publicado:
#12
|
|
|
Miembro del Clan Grupo: Miembros Mensajes: 75 Agradecimientos: 63 Registrado: 11-October 12 Miembro No.: 393,065 |
ahora dale en recovery imei alo mejor ¡guardo copia cyclone
Mensaje modificado por myking el Oct 24 2012, 12:49 AM -------------------- cyclone box jaf box setool box activada a full z3 samsung adition by gpg medusa jtag |
|
|
|
|
Oct 24 2012, 07:05 AM
Publicado:
#13
|
|
 Colaborador del Clan Grupo: Miembros Mensajes: 544 Agradecimientos: 514 Registrado: 17-July 12 Desde: Argentina Miembro No.: 364,028 |
Tienes RPL dañado...unicamente con uno nuevo vas a poder levantarlo..recuerda para la proxima SIEMPRE Backup de RPL esto es fundamental.
Saludos -------------------- La Tortuga Puede Hablar Más Del Camino Que La Liebre...
|
|
|
|
|
|
|
Fecha y Hora actual: 21st April 2026 - 09:27 AM |
