[LeEco Le Pro3 Guides, News, & Discussion] Dr. Jackal:
Hi to all, news news news...

In these days i tried to debug my dead phone with QPST, but many tools don't work because my phone is detected with only 9008 mode instead it should be detected in 9006 mode for debug.

I tried to send configuration xml file that is inside stock ROM with a tool of QPST that allow you to send single file to the phone and then I went to look LOG file:

14:27:57: DEBUG: XML FILE (113 bytes): CharsInBuffer=462-113=349

-------------------------------------------------------------------------------------------

<?xml version="1.0" encoding="UTF-8" ?>

<data>

<log value="Call to ufs_open(0, UFS_WLUN_DEVICE) failed"/>

</data>

-------------------------------------------------------------------------------------------

14:27:57: INFO: TARGET SAID: 'Call to ufs_open(0, UFS_WLUN_DEVICE) failed'

14:27:57: DEBUG: XML FILE (114 bytes): CharsInBuffer=349-114=235

-------------------------------------------------------------------------------------------

<?xml version="1.0" encoding="UTF-8" ?>

<data>

<log value="ERROR 2: Line 711: UFS_COMMIT_EXTRAS_FAILURE"/>

</data>

-------------------------------------------------------------------------------------------

14:27:57: INFO: TARGET SAID: 'ERROR 2: Line 711: UFS_COMMIT_EXTRAS_FAILURE'

14:27:57: DEBUG: XML FILE (156 bytes): CharsInBuffer=235-156=79

-------------------------------------------------------------------------------------------

<?xml version="1.0" encoding="UTF-8" ?>

<data>

<log value="Failed to set storage extra parameters - storage_device_commit_extras() returned FALSE"/>

</data>

-------------------------------------------------------------------------------------------

14:27:57: INFO: TARGET SAID: 'Failed to set storage extra parameters - storage_device_commit_extras() returned FALSE'

14:27:57: DEBUG: XML FILE (79 bytes): CharsInBuffer=79-79=0

-------------------------------------------------------------------------------------------

<?xml version="1.0" encoding="UTF-8" ?>

<data>

<response value="NAK" />

</data>

-------------------------------------------------------------------------------------------

14:27:57: DEBUG: Response was 'NAK'

I selected only last part of LOG file, he send all configuration succefully but when he send command "0, UFS_WLUN_DEVICE" for configure storage state it don't recognizes or don't see the storage and than "Failed to set storage extra parameters - storage_device_commit_extras() returned FALSE".

Second try... in new version of QFIL tool there is a function under tools menu named "Patition manager", i used it for get info about phone storage, this function is used for phones like my phone that can't enter in 9006 mode with debug port and storage visible in devices manager, i started it and the first thing it does is copy file of partion table but it don't find any partition table file! this is the LOG file:

14:48:33: INFO: User wants to talk to port '\\.\COM3'

14:48:33: DEBUG: port_fd=0xCC

14:48:33: INFO: Took 0.01600000 seconds to open port

14:48:33: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>

14:48:33: INFO: If you don't want this, use --dontsorttags

14:48:33: DEBUG: ==================================================================================

14:48:33: DEBUG: ==================================================================================

14:48:33: INFO: Looking for file 'fh_gpt_header_0'

14:48:33: DEBUG: 1. Calling stat('C:\Users\drjac\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\fh_gpt_header_0')

14:48:33: DEBUG: 2. Calling stat(fh_gpt_header_0)

(_)

__ ____ _ _ __ _ __ _ _ __ __ _

\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |

\ V V / (_| | | | | | | | | | | (_| |

\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |

__/ |

|___/

14:48:33: WARNING: find_file:7808 Couldn't find the file 'fh_gpt_header_0', returning NULL

14:48:33: DEBUG: 2. Calling fopen('fh_gpt_header_0') with AccessMode='wb'

14:48:33: INFO: Sending <configure>

14:48:33: DEBUG: CHANNEL DATA (P0000) (H00202) ( 227 bytes) - HOST TO TARGET -->

Now it's possible that i don't have access to the storage? Or it's damaged?

I would try to send it a partition table file but I don't find it because he should already be present when one tries to send ROM for flash phone, I need tool that formats the storage from the outside, but the difficulty is that i can reach only 9008 mode and not 9006 mode... at least to understand if the storage is good or inaccessible or broken....:eek::eek: