J200H/DS Dead

[ajubaba]

Dear all


Working on J200h/dS dead due to flash (some google app error).



with reference to this Unlock Forum - RIFF Box support forum


Read eMMC log

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.51 (RIFFBOX1), JTAG Manager Version: 1.86
Selected Resurrector: [Samsung J200H ISP V1.0.6552.55523, <RJ-45>, 1 Bit Bus Width (DAT0)]

Connecting to the SD/eMMC Card...OK
Set I/O Voltage reads as 1.81V, SD_CLK Frequency is 960 KHz

Memory Type .......................... eMMC
Manufacturer ID ...................... 0x90
OEM/Application ID ................... 0x4A
Product Name ......................... "H8G4t!"
Package .............................. BGA
User Area Partition Size ............. 0x0001D2000000 Bytes (7.28 GB)
Boot Partition Size .................. 0x000000400000 Bytes (4.00 MB)
RPMB Partition Size .................. 0x000000400000 Bytes (4.00 MB)
OCR Register ......................... 0xC0FF8080 (Dual Voltage, High Capacity)
Write Protection Bits ................ NONE
ExtCSD Register Fields ............... [177] = 0x00, [179] = 0x08, [162] = 0x00
Boot Configuration ................... Boot from Boot Partition 1 (Bus Width = 1 Bit)
Chip Revision ........................ 0.1
Multimedia Card Revision ............. 1.7 (eMMC v5.0)
Serial Number ........................ 0xBB022932
Memory Manufacturing Date ............ November, 2015

Resurection Log:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.51 (RIFFBOX1), JTAG Manager Version: 1.86
Selected Resurrector: [Samsung J200H ISP V1.0.6552.55523, <RJ-45>, 1 Bit Bus Width (DAT0)]

Connecting to the SD/eMMC Card...OK
Set I/O Voltage reads as 1.81V, SD_CLK Frequency is 960 KHz

Detected eMMC Chip, ID: 0x90/0x4A (H8G4t!), User Area Partition = 0x0001D2000000 Bytes (7.28 GB)

Selected Resurrection Data for the eMMC Chip with Capacity = 7.28 GB

Flashing the dead body...OK
Resurrection complete!

No download mode


Used the dump provided by black-micron. Here is the log


USER DATA PARTITION 1

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.51 (RIFFBOX1), JTAG Manager Version: 1.86
Selected Resurrector: [Samsung J200H ISP V1.0.6552.55523, <RJ-45>, 1 Bit Bus Width (DAT0)]

Connecting to the SD/eMMC Card...OK
Set I/O Voltage reads as 1.81V, SD_CLK Frequency is 960 KHz

Detected eMMC Chip, ID: 0x90/0x4A (H8G4t!), User Area Partition = 0x0001D2000000 Bytes (7.28 GB)

Writting "User Area Partition" memory from 0x000000000000 to 0x0000001FFFFF
Completed in 00:00:18.143 (Average Transfer Rate: 112.88 kB/s)

BOOT AREA PARTITION:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.51 (RIFFBOX1), JTAG Manager Version: 1.86
Selected Resurrector: [Samsung J200H ISP V1.0.6552.55523, <RJ-45>, 1 Bit Bus Width (DAT0)]

Connecting to the SD/eMMC Card...OK
Set I/O Voltage reads as 1.81V, SD_CLK Frequency is 960 KHz

Detected eMMC Chip, ID: 0x90/0x4A (H8G4t!), User Area Partition = 0x0001D2000000 Bytes (7.28 GB)

Writting "Boot Area Partition 1" memory from 0x000000000000 to 0x0000001FFFFF
Completed in 00:00:17.394 (Average Transfer Rate: 117.74 kB/s)

Still no luck.Any other ways to revive it.




Best regards
~Aju

[Legija]

Phone dead after flashing with Odin ?


Please read 128mb from user area and upload here.

[ajubaba]

Phone dead after flashing with Odin ?


Please read 128mb from user area and upload here.

Thanks for your reply,


Yes it is dead due ODIN.


Reading 128 MB User Area Partition, at 98 KBS estimated time 22 mins. its too slow





Best regards


~Aju

[ajubaba]

here 128 mb user partition read

[Legija]

SBOOT not present, looks like bad emmc.

[ajubaba]

SBOOT not present, looks like bad emmc.

So, there is no way to revive it?


Even I noticed when using it with emmc plugin, when I inject sboot.bin, it completes flashing but after parse memory again this partition is blank. Seems like it became READONLY.



Just a question, Can't we remove readonly lock from the chip?



Best Regards
~Aju

[Legija]

emmc ->advanced> remove write protection.


But this wont work if emmc controller "thinks" nand is faulty.