LG D325 dead

[turca]

I read backup user data D35 good:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.49 (RIFFBOX1), JTAG Manager Version: 1.77

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

Memory Type .......................... eMMC
Manufacturer ID ...................... 0x15
OEM/Application ID ................... 0x00
Product Name ......................... "K5XVMB"
Package .............................. BGA
User Area Partition Size ............. 0x0000E9000000 Bytes (3.64 GB)
Boot Partition Size .................. 0x000000400000 Bytes (4.00 MB)
RPMB Partition Size .................. 0x000000080000 Bytes (512.00 KB)
OCR Register ......................... 0xC0FF8080 (Dual Voltage, High Capacity)
Write Protection Bits ................ NONE
ExtCSD Register Fields ............... [177] = 0x00, [179] = 0x38, [162] = 0x00
Boot Configuration ................... Boot from User Area (Bus Width = 1Bit)
Chip Revision ........................ 0.6
Multimedia Card Revision ............. 1.7 (eMMC v5.0)
Serial Number ........................ 0x614B4274
Memory Manufacturing Date ............ October, 2014


This information D325 bad:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.49 (RIFFBOX1), JTAG Manager Version: 1.77

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

Memory Type .......................... eMMC
Manufacturer ID ...................... 0x65
OEM/Application ID ................... 0x6F
Product Name ......................... "M MOR "
Package .............................. Removable
User Area Partition Size ............. 0x000075700000 Bytes (1.83 GB)
Boot Partition Size .................. 0x000000200000 Bytes (2.00 MB)
RPMB Partition Size .................. 0x000000020000 Bytes (128.00 KB)
OCR Register ......................... 0xC0FF8080 (Dual Voltage, High Capacity)
Write Protection Bits ................ NONE
ExtCSD Register Fields ............... [177] = 0x00, [179] = 0x78, [162] = 0x00
Boot Configuration ................... Boot from User Area (Bus Width = 1Bit)
Chip Revision ........................ 8.1
Multimedia Card Revision ............. 1.5 (eMMC v4.41)
Serial Number ........................ 0x00000615
Memory Manufacturing Date ............ May, 2017


I need change boot configuration?

[Legija]

On bad phone it looks like just half of NAND is accesible to emmc controller. Not sure if it's possible to repair this problem without replacing the chip.

Any information on how phone died ?

[turca]

Phone dead after firmware other phone

[Albun]

It definitely looks like bad communication, some bits are lost.
Check wires, try with different voltages (2,8, 2.7, 2.6, 2.2, 1.8 etc)
Try adding pull-ups to CMD, DAT, CLK lines (100Ohm, 50Ohm, etc)

[turca]

My phone good after read user data, now is dbi fatal error

[turca]

It definitely looks like bad communication, some bits are lost.
Check wires, try with different voltages (2,8, 2.7, 2.6, 2.2, 1.8 etc)
Try adding pull-ups to CMD, DAT, CLK lines (100Ohm, 50Ohm, etc)

I read other devices normally, with the same wires and adapters, very strange this, is it possible even?

[Legija]

Increasing VCCIO in steps enhances stability in communication.

For example, instead of using 1.8v VCCIO, if You use 2.00v can help with communication errors.

It's not same for all devices even with same model it can be different.

[Albun]

I read other devices normamelte, with the same wires and adapters, very strange this, is it possible even?

Of course it is possible. Alive device may use peripherals in different ways. Some may be configured and consume definite currents. Some peripherals may be switched off and not consume any current.
Dead device may consume current in the other, unknown, way.
Thus it is possible that for a dead state there were conditions under which the eMMC chip's CMD DAT or CLK lines were 'overloaded' or 'over-noised' with whatever signals happen to take place in that state. So in that case the more stable or robust signals could be required to 'get through' the PCB's dead-state electronics. In which case playing with voltages and pull-ups may solve the unstability.

[turca]

I make new test thanks