ClanGSM.com

Bienvenido, invitado ( Identificarse | Registrarse )

 
Reply to this topicStart new topic
Cyclone Mata Nokia 6085, Tratando de flashear
Aliosky
mensaje Feb 19 2014, 08:58 PM
Publicado: #1

Miembro del Clan
*

Grupo: Miembros
Mensajes: 8
Agradecimientos: 0
Registrado: 17-June 13
Miembro No.: 482,684



Hola amigos necesito ayuda mi cyclone ha matado un nokia 6085 tratando de flashearlo ahora no me lo reconoce, cuento con UFC4

Detalles del proceso:
Processing pre flash tasks...
Backing up RPL...
RPL Creation started...
Processing CMT Part...
Storing Product Code...
Storing PSN...
Storing HWID...
Simlock Store not supported, not a PA_SL2 Phone
Trying to store WMDRM RPL...
Reading Keys...
Storing WMDRM PD...
Reading Security Block...
Security block OK and saved to "RM-198_353958010667725_19022014_123619.SecurityBlock.PM"
WARNING: "16600209E8380058B6681A8FF795FAD3F1BC298B.B0002845" Not Exists, Will read it...
Reading CYC file from phone...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101001101
CMT_EM_ASIC_ID: 00000232
CMT_EM_ASIC_ID: 00000353
CMT_PUBLIC_ID: 16600209E8380058B6681A8FF795FAD3F1BC298B
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 191EC665
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.30.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
Exploiting - running preloader...
Preloader running OK, Running Custom Loader...
Custom loader running OK! Working...
Old Loader Detected
Readed OK, Saving to "16600209E8380058B6681A8FF795FAD3F1BC298B.B0002845"
Storing Additional Data...
Checking Superdongle Key...
Encrypting Superdongle Key...
Storing Superdongle Key...
Checking CMLA Key...
CMLA Key Store Problem -> Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101001101
CMT_EM_ASIC_ID: 00000232
CMT_EM_ASIC_ID: 00000353
CMT_PUBLIC_ID: 16600209E8380058B6681A8FF795FAD3F1BC298B
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 191EC665
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0001002F00006921, AMD, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x0001002F (AMD), Size: 32MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: C44614CCC0A09C4A52B890FA55B4B31AF4787668
APE Subsystem Not Found
Flashbus Write baud set to 5.0Mbits
Storing NPC...
Storing CCC...
Storing HWC...
Storing VARIANT...
CMT PARTNERC Not Found
Restarting MCU...
RPL Saved OK
RPL backup thread finished, continuing...
Pre flash tasks finished, continuing...
Processing rm198__05.03.mcusw.bin (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101001101
CMT_EM_ASIC_ID: 00000232
CMT_EM_ASIC_ID: 00000353
CMT_PUBLIC_ID: 16600209E8380058B6681A8FF795FAD3F1BC298B
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 191EC665
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
rm198__05.03.mcusw.bin, Type: Flash Image, Algo: BB5, BB5 ALGORITHM
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 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]: 0x0001002F00006921, AMD, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x0001002F (AMD), Size: 32MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: C44614CCC0A09C4A52B890FA55B4B31AF4787668
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x00000000-0x000DFFFF, NOR
EraseArea[0,CMT]: 0x00100000-0x0110FFFF, NOR
Waiting 320s for erasure finish...
Erase taken 16.344s
Processing Flash Image Failed -> Group Erase failed
Failed to Process all Image files -> Failed to process rm198__05.03.mcusw.bin
Failed to disable VBAT -> CBUS reported an error
Go to the top of the page
 
+Quote Post
Anunciante Autorizado
mensaje Feb 19 2014, 08:58 PM
Publicado: #

Auspiciador de ClanGSM

Estas ofertas
pudieran interesarte.











Go to the top of the page
 
Quote Post
karapacho27
mensaje Feb 19 2014, 10:07 PM
Publicado: #2

Colaborador del Clan
**

Grupo: Miembros
Mensajes: 486
Agradecimientos: 313
Registrado: 8-March 13
Miembro No.: 444,826



amigo la cyclone no mata esos modelos solo debes ser cuidadoso al flashearlo no puedes tener problemas de conexion con el cel porque ahi si, trata de escribirle la ultima version y si no escribele la flash coincidente con el product code original del cel. Por que lo flasheaste??

saludos


--------------------
Herramientas: UFS/HWK, Setool full con LGTool y SgTool, HXC Dongle, Infinity Box Plus Pinfinder, Cyclone, MXBox, Polar Box 3, Z3X Pro, Sigmabox, Vygis, DC Unlocker, Scout Dongle, GSM Finder, NCK Dongle, Medusa, Octoplus LG
Go to the top of the page
 
+Quote Post
fhenix_dss1
mensaje Feb 20 2014, 09:31 AM
Publicado: #3

Colaborador del Clan
**

Grupo: Miembros
Mensajes: 446
Agradecimientos: 681
Registrado: 20-July 12
Desde: Pirané - Formosa
Miembro No.: 364,949
Pais:ar


Si, claro que los mata... todos los bb5 que intentes flashear usando el ufc 4 de dist. A mi me a pasado con 6131, 5310, e5 y otros. He podido revivir un 6131 que me mato cyclone con jaf. Preferente si vas a intentar flashear otro bb5 con cyclone hazlo por usb.


--------------------
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

"SR. Cliente: No hay reparación imposible,
sólo tardan y cuestan ($$$$) más... :-) "



>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<,<<<<

Mis Nenas: SigmaBox (Pack 1 y pack 2 Act), Z3X (Full Act), Cyclone Reload + UFC4, Best Dongle + SPT Act., Vygis Box, SETool3 + LGTool, HWK + UfS Micro, J.A.F., Octuplus Box (Full Act) y BST Dongle!!!
Go to the top of the page
 
+Quote Post
Aliosky
mensaje Feb 20 2014, 07:15 PM
Publicado: #4

Miembro del Clan
*

Grupo: Miembros
Mensajes: 8
Agradecimientos: 0
Registrado: 17-June 13
Miembro No.: 482,684



Gracias por responder resulta que lo flashe por que encendía y se apagaba, ahora no me lo reconoce así que no le puedo pasar nada con UCF será que lo reconocerá por USB?, o existe otra herramienta que lo reviva?
Gracias
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 usuario(s) está(n) leyendo este tema (1 invitado(s) y 0 usuario(s) anónimo(s))
0 usuarios(s) registrado(s):

 



Ver Visitas Fecha y Hora actual: 18th April 2026 - 08:11 PM
►Reglamento      ►Política de Privacidad
Este sitio web usa cookies, puedes ver la política de cookies, aquí -
Política de cookies +