samsung i727 - GSM-Forum

nadim electro · 10-14-2013, 14:45

samsung i727 boot repair error but set in recovery mode thanks jtag team error but solve
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.54
Selected Resurrector: [Samsung I727 V1.0.4455.8370]

Connecting to the dead body...OK
Detected dead body ID: 0x106A10E1 - CORRECT!
Set I/O Voltage reads as 1.81V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at MAX]

Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK

Detected an Initialized FLASH1 Chip, ID: 0x0015/0x0000 (KYL00M, 0x0003AB400000 Bytes = 14.68 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0000 (KYL00M, 0x000000080000 Bytes = 0.50 MB)

Flashing the dead body...
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
ERROR: Stopped due to multiple communication errors. Terminating at 0x000006418200

**legija** · 10-14-2013, 14:49

RIFF JTAG Box FAQ - ERROR: Failed due to multiple communication errors.

nadim electro · 10-15-2013, 09:08

Quote:

Originally Posted by legija

RIFF JTAG Box FAQ - ERROR: Failed due to multiple communication errors.

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.54
Selected Resurrector: [Samsung I727 V1.0.4455.8370]

Connecting to the dead body...OK
Detected dead body ID: 0x106A10E1 - CORRECT!
Set I/O Voltage reads as 1.81V, TCK Frequency is 1 MHz

Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK

Detected an Initialized FLASH1 Chip, ID: 0x0015/0x0000 (KYL00M, 0x0003AB400000 Bytes = 14.68 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0000 (KYL00M, 0x000000080000 Bytes = 0.50 MB)

Flashing the dead body...OK
Resurrection complete!
set is now odin mode firmware upgrade encountered an issue,please select recovery mode in kies &try again but odin will not flash it what can i do ?

nadim electro · 10-15-2013, 12:02

i have done with odin

<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I727UCMC1_I727ATTMC1_844945_REV02_user_l ow_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> amss.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> cache.img.ext4
<ID:0/006> mdm.bin
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> tomb.img.ext4
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!

10-14-2013, 14:45	#1 (permalink)
nadim electro No Life Poster Join Date: Oct 2006 Location: pakistan Posts: 669 Member: 361094 Status: Offline Sonork: 100.1597521 Thanks Meter: 172	samsung i727 samsung i727 boot repair error but set in recovery mode thanks jtag team error but solve Connecting to the RIFF Box...OK Firmware Version: 1.37, JTAG Manager Version: 1.54 Selected Resurrector: [Samsung I727 V1.0.4455.8370] Connecting to the dead body...OK Detected dead body ID: 0x106A10E1 - CORRECT! Set I/O Voltage reads as 1.81V, TCK Frequency is RTCK Adaptive Clocking RTCK Sampling is: [Sample at MAX] Resurrection sequence started. Establish communication with the phone...OK Initializing internal hardware configuration...OK Uploading resurrector data into memory...OK Starting communication with resurrector...OK Detected an Initialized FLASH1 Chip, ID: 0x0015/0x0000 (KYL00M, 0x0003AB400000 Bytes = 14.68 GB) Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0000 (KYL00M, 0x000000080000 Bytes = 0.50 MB) Flashing the dead body... ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK ERROR: Stopped due to multiple communication errors. Terminating at 0x000006418200

10-14-2013, 14:49	#2 (permalink)
legija Product Manager Join Date: Apr 2006 Age: 55 Posts: 5,746 Member: 256342 Status: Offline Sonork: None Thanks Meter: 28,276	RIFF JTAG Box FAQ - ERROR: Failed due to multiple communication errors.

10-15-2013, 12:02	#4 (permalink)
nadim electro No Life Poster Join Date: Oct 2006 Location: pakistan Posts: 669 Member: 361094 Status: Offline Sonork: 100.1597521 Thanks Meter: 172	i have done with odin <ID:0/006> Added!! <OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> KIES_HOME_I727UCMC1_I727ATTMC1_844945_REV02_user_l ow_ship.tar.md5 is valid. <OSM> Checking MD5 finished Sucessfully.. <OSM> Leave CS.. <ID:0/006> Odin v.3 engine (ID:6).. <ID:0/006> File analysis.. <ID:0/006> SetupConnection.. <ID:0/006> Initialzation.. <ID:0/006> Get PIT for mapping.. <ID:0/006> Firmware update start.. <ID:0/006> amss.bin <ID:0/006> NAND Write Start!! <ID:0/006> boot.img <ID:0/006> cache.img.ext4 <ID:0/006> mdm.bin <ID:0/006> recovery.img <ID:0/006> system.img.ext4 <ID:0/006> tomb.img.ext4 <ID:0/006> RQT_CLOSE !! <ID:0/006> RES OK !! <ID:0/006> Completed.. <OSM> All threads completed. (succeed 1 / failed 0) <ID:0/006> Removed!!