i535 dead after bad flashing by odin - GSM-Forum

Tommi_GSM · 11-04-2013, 16:08

Hello, after flashing phone is dead. I can't put in download mode.
After ressurection still dead, no download mode.

Code:

[2013-11-04 15:04:14] [START OPERATION_ID = RESURRECT]
[2013-11-04 15:04:15] Open serial port...OK
[2013-11-04 15:04:15] Connecting to the RIFF Box...OK
[2013-11-04 15:04:15] Firmware Version: 1.37, JTAG Manager Version: 1.55
[2013-11-04 15:04:15] Selected Resurrector: [Samsung I535 V1.0.4899.12662]
[2013-11-04 15:04:15] 
[2013-11-04 15:04:15] Connecting to the dead body...ERROR
[2013-11-04 15:04:15] ERROR: The RTCK Signal does not respond.
[2013-11-04 15:04:15] [FINISH OPERATION_ID = RESURRECT]

[2013-11-04 15:04:26] [START OPERATION_ID = RESURRECT]
[2013-11-04 15:05:06] Open serial port...OK
[2013-11-04 15:05:06] Connecting to the RIFF Box...OK
[2013-11-04 15:05:06] Firmware Version: 1.37, JTAG Manager Version: 1.55
[2013-11-04 15:05:06] Selected Resurrector: [Samsung I535 V1.0.4899.12662]
[2013-11-04 15:05:06] 
[2013-11-04 15:05:06] Connecting to the dead body...OK
[2013-11-04 15:05:06] Detected dead body ID: 0x706B10E1 - CORRECT!
[2013-11-04 15:05:06] Set I/O Voltage reads as 1.79V, TCK Frequency is RTCK
[2013-11-04 15:05:06] Adaptive Clocking RTCK Sampling is: [Sample at MAX]
[2013-11-04 15:05:06] 
[2013-11-04 15:05:06] Resurrection sequence started.
[2013-11-04 15:05:06] Establish communication with the phone...OK
[2013-11-04 15:05:06] Initializing internal hardware configuration...OK
[2013-11-04 15:05:06] Uploading resurrector data into memory...OK
[2013-11-04 15:05:06] Starting communication with resurrector...OK
[2013-11-04 15:05:06] 
[2013-11-04 15:05:06] Detected an Initialized FLASH1 Chip, ID: 0x0015/0x0000 (MAG4FB, 0x0003AB400000 Bytes = 14.68 GB)
[2013-11-04 15:05:06] Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0000 (MAG4FB, 0x000000200000 Bytes = 2.00 MB)
[2013-11-04 15:05:06] 
[2013-11-04 15:05:06] Selected Resurrection Data for the eMMC Chip with Capacity = 14,68GB
[2013-11-04 15:05:06] 
[2013-11-04 15:05:06] Flashing the dead body...OK
[2013-11-04 15:05:06] Resurrection complete!
[2013-11-04 15:05:06] [FINISH OPERATION_ID = RESURRECT]

[2013-11-04 15:05:18] [START OPERATION_ID = GET_DEVICE_ID]
[2013-11-04 15:05:18] Open serial port...OK
[2013-11-04 15:05:18] Connecting to the RIFF Box...OK
[2013-11-04 15:05:18] Firmware Version: 1.37, JTAG Manager Version: 1.55
[2013-11-04 15:05:18] Selected Resurrector: [Samsung I535 V1.0.4899.12662]
[2013-11-04 15:05:18] 
[2013-11-04 15:05:18] Connecting to the dead body...OK
[2013-11-04 15:05:18] Set I/O Voltage reads as 1.79V, TCK Frequency is RTCK
[2013-11-04 15:05:18] 
[2013-11-04 15:05:18] Detected dead body ID: 0x706B10E1
[2013-11-04 15:05:18] [FINISH OPERATION_ID = GET_DEVICE_ID]

eMMc plugin, read from device

Code:

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

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

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

Looking for the RIFF BOX DCCLoader USB Interface Port...FAILED
The DCCLoader USB Interface is not found. Communication continues over the DCC Interface

Reading FLASH1 address space from 0x000000000000 to 0x0000000001FF
Completed in 00:00:00.000 (Average Transfer Rate: N/A)

Reading FLASH1 address space from 0x000000004400 to 0x0000000045FF
Completed in 00:00:00.016 (Average Transfer Rate: 131071999.94 kB/s)

Reading FLASH1 address space from 0x000000000000 to 0x0000000001FF
Completed in 00:00:00.016 (Average Transfer Rate: 1312.50 kB/s)

Reading FLASH1 address space from 0x000000004400 to 0x0000000053FF
Completed in 00:00:00.032 (Average Transfer Rate: 656.25 kB/s)

Analizing the FullImage File...OK
Current Phone/Image File has PIT Structure.

PIT Descriptor: COM_TAR2MSM8960
Total quantity of listed partitions: 27

and check blank

Code:

Checking which Partition is blank...COMPLETE!
Following partitions are found to be completely blank:
  Partition: MD5 at 0x000000006400
  Partition: MODEM at 0x000000400000
  Partition: SBL1 at 0x000004000000
  Partition: SBL2 at 0x000004020000
  Partition: SBL3 at 0x000004060000
  Partition: ABOOT at 0x0000040E0000
  Partition: RPM at 0x0000042E0000
  Partition: BOOT at 0x000004360000
  Partition: TZ at 0x000004D60000
  Partition: PAD at 0x000004DE0000
  Partition: PARAM at 0x000004E60000
  Partition: EFS at 0x000005860000
  Partition: MODEMST1 at 0x000006600000
  Partition: MODEMST2 at 0x000006900000
  Partition: SYSTEM at 0x000006C00000
  Partition: USERDATA at 0x000064800000
  Partition: PERSIST at 0x000373C00000
  Partition: CACHE at 0x000374400000
  Partition: RECOVERY at 0x0003A8C00000
  Partition: FOTA at 0x0003A9600000
  Partition: BACKUP at 0x0003AA000000
  Partition: FSG at 0x0003AA600000
  Partition: SSD at 0x0003AA900000
  Partition: GROW at 0x0003AA902000
  Partition: SGPT at 0x0003AB3FBE00
Thus in total, there are 25 blank partitions.

What can I do now? Repartition by i535file or write full dump (I don't have fulldump)

br
Tommi

**legija** · 11-04-2013, 17:20

It looks like odin flash failed due to bad eMMC.

Tommi_GSM · 11-04-2013, 17:47

This phone worked correctly before a customer flash by odin. Probably brick after boot flashing.
Can I unbrick this phone?

**legija** · 11-04-2013, 18:55

Quote:

Originally Posted by Tommi_GSM

This phone worked correctly before a customer flash by odin. Probably brick after boot flashing.
Can I unbrick this phone?

Can i jump as Bubka? LOL

If phone HW is okay, yes You can. If phone HW is NOT OK, again You can, if You repair HW.
But since I don't know You personally and have no idea about Your skills, this is in "might be" domain.

Tommi_GSM · 11-04-2013, 20:30

Ha ha

We laughed but now it's time to work.
Phone worked fine and was bricked when the customer flashed it.

I wanted to ask HOW to do it because I resurrected it by riff and the phone is still dead.
How to repair and put it into download mode because now screen is only black.

I know You CAN help me

**legija** · 11-05-2013, 12:20

There is one thing to be checked, You'll have to contact me via ICQ.

11-04-2013, 17:20	#2 (permalink)
legija Product Manager Join Date: Apr 2006 Age: 55 Posts: 5,746 Member: 256342 Status: Offline Sonork: None Thanks Meter: 28,276	It looks like odin flash failed due to bad eMMC.

11-04-2013, 17:47	#3 (permalink)
Tommi_GSM Insane Poster Join Date: Nov 2006 Posts: 66 Member: 393902 Status: Offline Thanks Meter: 4	This phone worked correctly before a customer flash by odin. Probably brick after boot flashing. Can I unbrick this phone?

11-04-2013, 20:30	#5 (permalink)
Tommi_GSM Insane Poster Join Date: Nov 2006 Posts: 66 Member: 393902 Status: Offline Thanks Meter: 4	Ha ha We laughed but now it's time to work. Phone worked fine and was bricked when the customer flashed it. I wanted to ask HOW to do it because I resurrected it by riff and the phone is still dead. How to repair and put it into download mode because now screen is only black. I know You CAN help me

11-05-2013, 12:20	#6 (permalink)
legija Product Manager Join Date: Apr 2006 Age: 55 Posts: 5,746 Member: 256342 Status: Offline Sonork: None Thanks Meter: 28,276	There is one thing to be checked, You'll have to contact me via ICQ.