Why SHV-E160S dead after write full dump

[>>pakfones<<]

Hi,
Dear Riff Team plz help me to alive SHV-E160S again. problem was only HW not active. so i write full dump phone dead after writing dump file SHV-E160k first 512mb live phone.bin SHV-E160S_REV14 written on board. i also checked resurrect again after writing full dump. but phone only asking qualcomm cdma technologies drivers.

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.55
Selected Resurrector: [Samsung E160K V1.0.4535.7001]

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]
Settings Code: 0x600400000000000000000003AB400000

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 (KTS00M, 0x0003AB400000 Bytes = 14.68 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0000 (KTS00M, 0x000000200000 Bytes = 2.00 MB)

Writting FLASH1 memory from 0x000000000200 to 0x0000064001FF
Completed in 00:15:32.156 (Average Transfer Rate: 109.85 kB/s)

Writting FLASH1 memory from 0x000006400200 to 0x00000647D1FF
Completed in 00:00:04.844 (Average Transfer Rate: 103.22 kB/s)

Writting FLASH1 memory from 0x00000647D200 to 0x0000065F41FF
Completed in 00:00:14.297 (Average Transfer Rate: 104.92 kB/s)

Writting FLASH1 memory from 0x000006800000 to 0x00000687CFFF
Completed in 00:00:05.234 (Average Transfer Rate: 95.53 kB/s)

Writting FLASH1 memory from 0x000006C00000 to 0x000006DFFFFF
Completed in 00:00:22.594 (Average Transfer Rate: 90.64 kB/s)

Writting FLASH1 memory from 0x000007000000 to 0x000007270FFF
Completed in 00:00:34.907 (Average Transfer Rate: 71.62 kB/s)

Writting FLASH1 memory from 0x000007400000 to 0x000007DFFFFF
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
Completed in 00:02:18.094 (Average Transfer Rate: 74.15 kB/s)

Writting FLASH1 memory from 0x000008000000 to 0x00000807CFFF
Completed in 00:00:05.500 (Average Transfer Rate: 90.91 kB/s)

Writting FLASH1 memory from 0x000008400000 to 0x00000847CFFF
Completed in 00:00:04.593 (Average Transfer Rate: 108.86 kB/s)

Writting FLASH1 memory from 0x000008800000 to 0x00000887CFFF
Completed in 00:00:04.422 (Average Transfer Rate: 113.07 kB/s)

Writting FLASH1 memory from 0x000008C00000 to 0x0000095FFFFF
Completed in 00:01:32.516 (Average Transfer Rate: 110.68 kB/s)

Writting FLASH1 memory from 0x000009800000 to 0x00000F9FFFFF
Completed in 00:17:59.063 (Average Transfer Rate: 93.00 kB/s)

Writting FLASH1 memory from 0x00000FC00000 to 0x00000FEFFFFF
Completed in 00:00:50.531 (Average Transfer Rate: 60.79 kB/s)

Writting FLASH1 memory from 0x000010000000 to 0x0000102FFFFF
Completed in 00:00:53.422 (Average Transfer Rate: 57.50 kB/s)

Writting FLASH1 memory from 0x000010400000 to 0x0000106FFFFF
Completed in 00:00:27.360 (Average Transfer Rate: 112.28 kB/s)

Writting FLASH1 memory from 0x000010800000 to 0x0000169FFFFF
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
Completed in 00:18:52.766 (Average Transfer Rate: 88.59 kB/s)

Writting FLASH1 memory from 0x000016C00000 to 0x000016EFFFFF
Completed in 00:00:33.203 (Average Transfer Rate: 92.52 kB/s)

Writting FLASH1 memory from 0x000017000000 to 0x0000172FFFFF
Completed in 00:00:38.281 (Average Transfer Rate: 80.25 kB/s)

Writting FLASH1 memory from 0x000017400000 to 0x0000176FFFFF
Completed in 00:00:27.422 (Average Transfer Rate: 112.03 kB/s)

Writting FLASH1 memory from 0x000017800000 to 0x0000181FFFFF
Completed in 00:01:35.265 (Average Transfer Rate: 107.49 kB/s)

Writting FLASH1 memory from 0x000018400000 to 0x000018DFFFFF
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
Completed in 00:02:42.938 (Average Transfer Rate: 62.85 kB/s)

Thanks in advance.

[>>pakfones<<]

Plz give me solution for this device this model have 16 GB EMMC and i need to repair boot only plz anyone give me full dump fro this device as i have seen many user have same problem like. and have never success.

[soidihoang]

Plz give me solution for this device this model have 16 GB EMMC and i need to repair boot only plz anyone give me full dump fro this device as i have seen many user have same problem like. and have never success.

use e160k resurrect for e160s. After repair boot reflash with firmware e160k download from sammobile and your phone will ok. If not it's may be hardware problem, change emmc chip

[>>pakfones<<]

use e160k resurrect for e160s. After repair boot reflash with firmware e160k download from sammobile and your phone will ok. If not it's may be hardware problem, change emmc chip

Thanks for ur reply here because of in this official forum for riff box no one reply me three days gone. but i have told i do resurrect with e160k dll but not work afyter write dump emmc is also good accepting read write and erase.

[Tedjo]

its mean riff not support e160s ???

OMG

[Tedjo]

I have repaired SHV-E160s done ...

newbie in riff box just buy this box this july ...

got a little hard work repair this e160s

BR,

[riteshgpt60]

I need e210k 32gb , dump.

br

[sunday_unlocker]

no one sharing the repair process off this SHV-E160s phone, succes log or etc




CMIIW

[chandarakk]

if ur phone 100% dead by software riff 100% can do it use f160K instead so mean if ur not sovt by riff mean is HW 100%

[>>pakfones<<]

i done that phone months ago sorry for late reply i done by erasing full flash then writing dump to phone.