Database Info

Lg g4 h810 files for qfil

Can someone provide me these files of LG G4 H810 for QFIL Hard Brick flashing.?
Help me plz

pchacker47 said:
Can someone provide me these files of LG G4 H810 for QFIL Hard Brick flashing.?
Help me plz
Click to expand...
Click to collapse
https://forum.xda-developers.com/att-g4/general/unbrick-9008-mode-h810-100-method-t3555231
---------- Post added at 04:52 PM ---------- Previous post was at 04:47 PM ----------
elcoya06 said:
https://forum.xda-developers.com/att-g4/general/unbrick-9008-mode-h810-100-method-t3555231
Click to expand...
Click to collapse
There is already a post with the same theme and files

Thank u so much
elcoya06 said:
https://forum.xda-developers.com/att-g4/general/unbrick-9008-mode-h810-100-method-t3555231
---------- Post added at 04:52 PM ---------- Previous post was at 04:47 PM ----------
There is already a post with the same theme and files
Click to expand...
Click to collapse
Thank u so much brother but its late now i gave my mobile to repair shop with cost of 20$ and i take my mobile on monday
any way thank u so much!

I Flash my G4 H810 with Qfil the result log is below: What does this mean ?
pchacker47 said:
Can someone provide me these files of LG G4 H810 for QFIL Hard Brick flashing.?
Help me plz
Click to expand...
Click to collapse
Validating Application Configuration
Load APP Configuration
COM:6
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:\LG\H810 firmware\prog_emmc_firehose_8992_lite.mbn
RESETSAHARASTATEEMACHINE:False
SEARCHPATH:\LG\H810 firmware
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
AUTOPRESERVEPARTITIONS:False
PARTITIONPRESERVEMODE:0
PRESERVEDPARTITIONS:0
PRESERVEDPARTITIONS:
ERASEALL:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: D:\LG\H810 firmware
RAWPROGRAM file path: D:\LG\H810 firmware\rawprogram0.xml
PATCH file path:\LG\H810 firmware\patch0.xml
Programmer Path:\LG\H810 firmware\prog_emmc_firehose_8992_lite.mbn
Process Index:0
Programmer Path:C:\Users\SADIK\Desktop\RecoveryImage\prog_emmc_firehose_8992_lite.mbn
Image Search Path: C:\Users\SADIK\Desktop\RecoveryImage
RAWPROGRAM file path: C:\Users\SADIK\Desktop\RecoveryImage\rawprogram0.xml
PATCH file path:C:\Users\SADIK\Desktop\RecoveryImage\patch0.xml
Image Search Path: C:\Users\SADIK\Desktop\RecoveryImage
RAWPROGRAM file path: C:\Users\SADIK\Desktop\RecoveryImage\rawprogram0.xml
PATCH file path:C:\Users\SADIK\Desktop\RecoveryImage\patch0.xml
Start Download
Program Path:C:\Users\SADIK\Desktop\RecoveryImage\prog_emmc_firehose_8992_lite.mbn
***** Working Folder:C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
Binary build date: Oct 31 2016 @ 22:51:05
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\Users\SADIK\Desktop\RecoveryImage\prog_emmc_firehose_8992_lite.mbn
13:33:56: Requested ID 13, file: "C:\Users\SADIK\Desktop\RecoveryImage\prog_emmc_firehose_8992_lite.mbn"
13:33:56: 273568 bytes transferred in 0.125000 seconds (2.0872MBps)
13:33:56: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
13:33:56: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
***** Working Folder:C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
Base Version: 16.10.28.15.28
Binary build date: Oct 31 2016 @ 22:51:02
Incremental Build version: 16.10.31.22.51.02
13:34:00: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM6 --sendxml=rawprogram0.xml --search_path=C:\Users\SADIK\Desktop\RecoveryImage --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
13:34:00: INFO: Current working dir (cwd): C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\
13:34:00: INFO: Showing network mappings to allow debugging
13:34:00: INFO:
13:34:00: INFO: Trying to store 'rawprogram0.xml' in string table
13:34:00: INFO: Looking for file 'rawprogram0.xml'
13:34:00: INFO: User wants to talk to port '\\.\COM6'
13:34:00: INFO: Took 0.00000000 seconds to open port
13:34:00: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
13:34:00: INFO: If you don't want this, use --dontsorttags
13:34:00: INFO: Looking for file 'pmic.mbn'
13:34:00: INFO: Looking for file 'sbl1.mbn'
13:34:00: INFO: Looking for file 'tz.mbn'
13:34:00: INFO: Looking for file 'sdi.mbn'
13:34:00: INFO: Looking for file 'hyp.mbn'
13:34:00: INFO: Looking for file 'rpm.mbn'
13:34:00: INFO: Looking for file 'emmc_appsboot.mbn'
13:34:00: INFO: Looking for file 'laf.img'
13:34:00: INFO: Looking for file 'gpt_main0.bin'
13:34:00: INFO: Looking for file 'gpt_backup0.bin'
13:34:00: INFO:
Total to be tansferd with <program> or <read> is 39.71 MB
13:34:00: INFO: Sending <configure>
13:34:00: INFO: TARGET SAID: 'Binary build date: Mar 3 2015 @ 19:29:19'
13:34:00: INFO: TARGET SAID: 'Chip serial num: 8063555 (0x7b0a43)'
13:34:00: INFO: TARGET SAID: 'Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke '
13:34:00: INFO: TARGET SAID: 'fh.attrs.MaxPayloadSizeToTargetInBytes _ FIREHOSE_CHANNEL_BUFFER_SIZE'
13:34:00: INFO: TARGET SAID: 'Calling hotplug_poll_device('MMC')'
13:34:00: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 8192
13:34:00: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 8192
13:34:00: INFO: Target returned NAK for your <configure> but it does not seem to be an error. This is ok, fh_loader.exe attributes updated
13:34:00: INFO: In handleProgram('pmic.mbn')
13:34:00: INFO: Looking for file 'pmic.mbn'
13:34:00: INFO: =======================================================
13:34:00: INFO: {<program> FILE: 'C:\Users\SADIK\Desktop\RecoveryImage\pmic.mbn'}
13:34:00: INFO: {<program> (36.73 KB) 74 sectors needed at location 229376 on LUN 0}
13:34:00: INFO: =======================================================
13:34:00: INFO: TARGET SAID: 'start 229376, num 74'
13:34:00: INFO: FILE ACCESS SLOW!! 37.00 KB in 0.015 seconds ( 2.41 MBps) --- Overall to target 0.016 seconds (2.26 MBps)
13:34:00: INFO: {percent files transferred 0.09%}
13:34:00: INFO: TARGET SAID: 'Finished sector address 229450'
13:34:00: INFO:
13:34:00: INFO: =======================================================
13:34:00: INFO: ==================== {SUCCESS} ========================
13:34:00: INFO: =======================================================
13:34:00: INFO: {percent files transferred 0.09%}
13:34:00: INFO: In handleProgram('sbl1.mbn')
13:34:00: INFO: Looking for file 'sbl1.mbn'
13:34:00: INFO: =======================================================
13:34:00: INFO: {<program> FILE: 'C:\Users\SADIK\Desktop\RecoveryImage\sbl1.mbn'}
13:34:00: INFO: {<program> (575.50 KB) 1151 sectors needed at location 230400 on LUN 0}
13:34:00: INFO: =======================================================
13:34:00: INFO: TARGET SAID: 'start 230400, num 1151'
13:34:01: INFO: FILE ACCESS SLOW!! 575.50 KB in 0.015 seconds ( 37.47 MBps) --- Overall to target 0.312 seconds (1.80 MBps)
13:34:01: INFO: {percent files transferred 1.51%}
13:34:01: INFO: TARGET SAID: 'Finished sector address 231551'
13:34:01: INFO:
13:34:01: INFO: =======================================================
13:34:01: INFO: ==================== {SUCCESS} ========================
13:34:01: INFO: =======================================================
13:34:01: INFO: {percent files transferred 1.51%}
13:34:01: INFO: In handleProgram('tz.mbn')
13:34:01: INFO: Looking for file 'tz.mbn'
13:34:01: INFO: =======================================================
13:34:01: INFO: {<program> FILE: 'C:\Users\SADIK\Desktop\RecoveryImage\tz.mbn'}
13:34:01: INFO: {<program> (560.20 KB) 1121 sectors needed at location 232448 on LUN 0}
13:34:01: INFO: =======================================================
13:34:01: INFO: TARGET SAID: 'start 232448, num 1121'
13:34:01: INFO: FILE ACCESS SLOW!! 560.50 KB in 0.015 seconds ( 36.49 MBps) --- Overall to target 0.312 seconds (1.75 MBps)
13:34:01: INFO: {percent files transferred 2.88%}
13:34:01: INFO: TARGET SAID: 'Finished sector address 233569'
13:34:01: INFO:
13:34:01: INFO: =======================================================
13:34:01: INFO: ==================== {SUCCESS} ========================
13:34:01: INFO: =======================================================
13:34:01: INFO: {percent files transferred 2.88%}
13:34:01: INFO: In handleProgram('sdi.mbn')
13:34:01: INFO: Looking for file 'sdi.mbn'
13:34:01: INFO: =======================================================
13:34:01: INFO: {<program> FILE: 'C:\Users\SADIK\Desktop\RecoveryImage\sdi.mbn'}
13:34:01: INFO: {<program> (27.88 KB) 56 sectors needed at location 234496 on LUN 0}
13:34:01: INFO: =======================================================
13:34:01: INFO: TARGET SAID: 'start 234496, num 56'
13:34:01: INFO: FILE ACCESS SLOW!! 28.00 KB in 0.015 seconds ( 1.82 MBps) --- Overall to target 0.016 seconds (1.71 MBps)
13:34:01: INFO: {percent files transferred 2.95%}
13:34:01: INFO: TARGET SAID: 'Finished sector address 234552'
13:34:01: INFO:
13:34:01: INFO: =======================================================
13:34:01: INFO: ==================== {SUCCESS} ========================
13:34:01: INFO: =======================================================
13:34:01: INFO: {percent files transferred 2.95%}
13:34:01: INFO: In handleProgram('hyp.mbn')
13:34:01: INFO: Looking for file 'hyp.mbn'
13:34:01: INFO: =======================================================
13:34:01: INFO: {<program> FILE: 'C:\Users\SADIK\Desktop\RecoveryImage\hyp.mbn'}
13:34:01: INFO: {<program> (92.30 KB) 185 sectors needed at location 235520 on LUN 0}
13:34:01: INFO: =======================================================
13:34:01: INFO: TARGET SAID: 'start 235520, num 185'
13:34:01: INFO: FILE ACCESS SLOW!! 92.50 KB in 0.015 seconds ( 6.02 MBps) --- Overall to target 0.047 seconds (1.92 MBps)
13:34:01: INFO: {percent files transferred 3.18%}
13:34:01: INFO: TARGET SAID: 'Finished sector address 235705'
13:34:01: INFO:
13:34:01: INFO: =======================================================
13:34:01: INFO: ==================== {SUCCESS} ========================
13:34:01: INFO: =======================================================
13:34:01: INFO: {percent files transferred 3.18%}
13:34:01: INFO: In handleProgram('rpm.mbn')
13:34:01: INFO: Looking for file 'rpm.mbn'
13:34:01: INFO: =======================================================
13:34:01: INFO: {<program> FILE: 'C:\Users\SADIK\Desktop\RecoveryImage\rpm.mbn'}
13:34:01: INFO: {<program> (187.04 KB) 375 sectors needed at location 236544 on LUN 0}
13:34:01: INFO: =======================================================
13:34:01: INFO: TARGET SAID: 'start 236544, num 375'
13:34:01: INFO: FILE ACCESS SLOW!! 187.50 KB in 0.015 seconds ( 12.21 MBps) --- Overall to target 0.094 seconds (1.95 MBps)
13:34:01: INFO: {percent files transferred 3.64%}
13:34:01: INFO: TARGET SAID: 'Finished sector address 236919'
13:34:01: INFO:
13:34:01: INFO: =======================================================
13:34:01: INFO: ==================== {SUCCESS} ========================
13:34:01: INFO: =======================================================
13:34:01: INFO: {percent files transferred 3.64%}
13:34:01: INFO: In handleProgram('emmc_appsboot.mbn')
13:34:01: INFO: Looking for file 'emmc_appsboot.mbn'
13:34:01: INFO: =======================================================
13:34:01: INFO: {<program> FILE: 'C:\Users\SADIK\Desktop\RecoveryImage\emmc_appsboot.mbn'}
13:34:01: INFO: {<program> (635.64 KB) 1272 sectors needed at location 237568 on LUN 0}
13:34:01: INFO: =======================================================
13:34:01: INFO: TARGET SAID: 'start 237568, num 1272'
13:34:02: INFO: FILE ACCESS SLOW!! 636.00 KB in 0.015 seconds ( 41.41 MBps) --- Overall to target 0.343 seconds (1.81 MBps)
13:34:02: INFO: {percent files transferred 5.20%}
13:34:02: INFO: TARGET SAID: 'Finished sector address 238840'
13:34:02: INFO:
13:34:02: INFO: =======================================================
13:34:02: INFO: ==================== {SUCCESS} ========================
13:34:02: INFO: =======================================================
13:34:02: INFO: {percent files transferred 5.20%}
13:34:02: INFO: In handleProgram('laf.img')
13:34:02: INFO: Looking for file 'laf.img'
13:34:02: INFO: =======================================================
13:34:02: INFO: {<program> FILE: 'C:\Users\SADIK\Desktop\RecoveryImage\laf.img'}
13:34:02: INFO: {<program> (37.62 MB) 77036 sectors needed at location 393216 on LUN 0}
13:34:02: INFO: =======================================================
13:34:02: INFO: TARGET SAID: 'start 393216, num 77036'
13:34:04: INFO: Overall to target 2.012 seconds (1.76 MBps)
13:34:04: INFO: {percent files transferred 14.13%}
13:34:06: INFO: Overall to target 4.025 seconds (1.76 MBps)
13:34:06: INFO: {percent files transferred 23.04%}
13:34:08: INFO: Overall to target 6.037 seconds (1.76 MBps)
13:34:08: INFO: {percent files transferred 31.96%}
13:34:10: INFO: Overall to target 8.049 seconds (1.76 MBps)
13:34:10: INFO: {percent files transferred 40.91%}
13:34:12: INFO: Overall to target 10.062 seconds (1.76 MBps)
13:34:12: INFO: {percent files transferred 49.84%}
13:34:14: INFO: Overall to target 12.074 seconds (1.76 MBps)
13:34:14: INFO: {percent files transferred 58.77%}
13:34:16: INFO: Overall to target 14.087 seconds (1.76 MBps)
13:34:16: INFO: {percent files transferred 67.72%}
13:34:18: INFO: Overall to target 16.099 seconds (1.76 MBps)
13:34:18: INFO: {percent files transferred 76.65%}
13:34:20: INFO: Overall to target 18.111 seconds (1.76 MBps)
13:34:20: INFO: {percent files transferred 85.60%}
13:34:22: INFO: Overall to target 20.124 seconds (1.76 MBps)
13:34:22: INFO: {percent files transferred 94.55%}
13:34:23: INFO: Overall to target 21.325 seconds (1.76 MBps)
13:34:23: INFO: {percent files transferred 99.92%}
13:34:23: INFO: TARGET SAID: 'Finished sector address 470252'
13:34:23: INFO:
13:34:23: INFO: =======================================================
13:34:23: INFO: ==================== {SUCCESS} ========================
13:34:23: INFO: =======================================================
13:34:23: INFO: {percent files transferred 99.92%}
13:34:23: INFO: In handleProgram('gpt_main0.bin')
13:34:23: INFO: Looking for file 'gpt_main0.bin'
13:34:23: INFO: =======================================================
13:34:23: INFO: {<program> FILE: 'C:\Users\SADIK\Desktop\RecoveryImage\gpt_main0.bin'}
13:34:23: INFO: {<program> (17.00 KB) 34 sectors needed at location 0 on LUN 0}
13:34:23: INFO: =======================================================
13:34:23: INFO: TARGET SAID: 'start 0, num 34'
13:34:23: INFO: FILE ACCESS SLOW!! 17.00 KB in 0.015 seconds ( 1.11 MBps) --- Overall to target 0.015 seconds (1.11 MBps)
13:34:23: INFO: {percent files transferred 99.96%}
13:34:23: INFO: TARGET SAID: 'Finished sector address 34'
13:34:23: INFO:
13:34:23: INFO: =======================================================
13:34:23: INFO: ==================== {SUCCESS} ========================
13:34:23: INFO: =======================================================
13:34:23: INFO: {percent files transferred 99.96%}
13:34:23: INFO: In handleProgram('gpt_backup0.bin')
13:34:23: INFO: Looking for file 'gpt_backup0.bin'
13:34:23: INFO: =======================================================
13:34:23: INFO: {<program> FILE: 'C:\Users\SADIK\Desktop\RecoveryImage\gpt_backup0.bin'}
13:34:23: INFO: {<program> (16.50 KB) 33 sectors needed at location 0 on LUN 0}
13:34:23: INFO: =======================================================
13:34:23: INFO: TARGET SAID: 'start 61071327, num 33'
13:34:23: INFO: FILE ACCESS SLOW!! 16.50 KB in 0.015 seconds ( 1.07 MBps) --- Overall to target 0.010 seconds (1.61 MBps)
13:34:23: INFO: {percent files transferred 100.00%}
13:34:23: INFO: TARGET SAID: 'Finished sector address 61071360'
13:34:23: INFO:
13:34:23: INFO: =======================================================
13:34:23: INFO: ==================== {SUCCESS} ========================
13:34:23: INFO: =======================================================
13:34:23: INFO: {percent files transferred 100.00%}
13:34:23: INFO: ==============================================================
13:34:23: INFO: Files used and their paths
13:34:23: INFO: 1 'C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt'
13:34:23: INFO: 2 'C:\Users\SADIK\Desktop\RecoveryImage\rawprogram0.xml'
13:34:23: INFO: 3 'C:\Users\SADIK\Desktop\RecoveryImage\pmic.mbn'
13:34:23: INFO: 4 'C:\Users\SADIK\Desktop\RecoveryImage\sbl1.mbn'
13:34:23: INFO: 5 'C:\Users\SADIK\Desktop\RecoveryImage\tz.mbn'
13:34:23: INFO: 6 'C:\Users\SADIK\Desktop\RecoveryImage\sdi.mbn'
13:34:23: INFO: 7 'C:\Users\SADIK\Desktop\RecoveryImage\hyp.mbn'
13:34:23: INFO: 8 'C:\Users\SADIK\Desktop\RecoveryImage\rpm.mbn'
13:34:23: INFO: 9 'C:\Users\SADIK\Desktop\RecoveryImage\emmc_appsboot.mbn'
13:34:23: INFO: 10 'C:\Users\SADIK\Desktop\RecoveryImage\laf.img'
13:34:23: INFO: 11 'C:\Users\SADIK\Desktop\RecoveryImage\gpt_main0.bin'
13:34:23: INFO: 12 'C:\Users\SADIK\Desktop\RecoveryImage\gpt_backup0.bin'
13:34:23: INFO: _ (done)
13:34:23: INFO: | |
13:34:23: INFO: __| | ___ _ __ ___
13:34:23: INFO: / _` |/ _ \| '_ \ / _ \
13:34:23: INFO: | (_| | (_) | | | | __/
13:34:23: INFO: \__,_|\___/|_| |_|\___|
13:34:23: INFO: {All Finished Successfully}
13:34:23: INFO: Overall to target 23.525 seconds (1.69 MBps)
13:34:23: INFO: {percent files transferred 100.00%}
Writing log to 'C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt', might take a minute
Log is 'C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt'
***** Working Folder:C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
Base Version: 16.10.28.15.28
Binary build date: Oct 31 2016 @ 22:51:02
Incremental Build version: 16.10.31.22.51.02
13:34:24: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM6 --sendxml=patch0.xml --search_path=C:\Users\SADIK\Desktop\RecoveryImage --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
13:34:24: INFO: Current working dir (cwd): C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\
13:34:24: INFO: Showing network mappings to allow debugging
13:34:24: INFO:
13:34:24: INFO: Trying to store 'patch0.xml' in string table
13:34:24: INFO: Looking for file 'patch0.xml'
13:34:24: INFO: User wants to talk to port '\\.\COM6'
13:34:24: INFO: Took 0.00000000 seconds to open port
13:34:24: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
13:34:24: INFO: If you don't want this, use --dontsorttags
13:34:24: INFO: Sending <configure>
13:34:24: INFO: TARGET SAID: 'fh.attrs.MaxPayloadSizeToTargetInBytes _ FIREHOSE_CHANNEL_BUFFER_SIZE'
13:34:24: INFO: TARGET SAID: 'Calling hotplug_poll_device('MMC')'
13:34:24: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 8192
13:34:24: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 8192
13:34:24: INFO: Target returned NAK for your <configure> but it does not seem to be an error. This is ok, fh_loader.exe attributes updated
13:34:24: INFO: TARGET SAID: 'Patched sector 15 with 03A3DFDE'
13:34:24: INFO: TARGET SAID: 'Patched sector 61071340 with 03A3DFDE'
13:34:24: INFO: TARGET SAID: 'Patched sector 1 with 03A3DFDE'
13:34:24: INFO: TARGET SAID: 'Patched sector 61071359 with 03A3DFDE'
13:34:24: INFO: TARGET SAID: 'Patched sector 1 with 03A3DFFF'
13:34:24: INFO: TARGET SAID: 'Patched sector 61071359 with 03A3DFFF'
13:34:24: INFO: TARGET SAID: 'Patched sector 61071359 with 03A3DFDF'
13:34:24: INFO: TARGET SAID: 'crc start sector 2, over bytes 7168'
13:34:24: INFO: TARGET SAID: 'Patched sector 1 with DA92707B'
13:34:24: INFO: TARGET SAID: 'crc start sector 61071327, over bytes 7168'
13:34:25: INFO: TARGET SAID: 'Patched sector 61071359 with DA92707B'
13:34:25: INFO: TARGET SAID: 'Patched sector 1 with 00000000'
13:34:25: INFO: TARGET SAID: 'crc start sector 1, over bytes 92'
13:34:25: INFO: TARGET SAID: 'Patched sector 1 with 016ABE28'
13:34:25: INFO: TARGET SAID: 'Patched sector 61071359 with 00000000'
13:34:25: INFO: TARGET SAID: 'crc start sector 61071359, over bytes 92'
13:34:25: INFO: TARGET SAID: 'Patched sector 61071359 with BD45EE20'
13:34:25: INFO: ==============================================================
13:34:25: INFO: Files used and their paths
13:34:25: INFO: 1 'C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt'
13:34:25: INFO: 2 'C:\Users\SADIK\Desktop\RecoveryImage\patch0.xml'
13:34:25: INFO: _ (done)
13:34:25: INFO: | |
13:34:25: INFO: __| | ___ _ __ ___
13:34:25: INFO: / _` |/ _ \| '_ \ / _ \
13:34:25: INFO: | (_| | (_) | | | | __/
13:34:25: INFO: \__,_|\___/|_| |_|\___|
13:34:25: INFO: {All Finished Successfully}
13:34:25: INFO: FILE ACCESS SLOW!! 0.00 B in 0.015 seconds ( 0.00 Bps) --- Overall to target 0.639 seconds (0.00 Bps)
Writing log to 'C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt', might take a minute
Log is 'C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt'
***** Working Folder:C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
Base Version: 16.10.28.15.28
Binary build date: Oct 31 2016 @ 22:51:02
Incremental Build version: 16.10.31.22.51.02
13:34:25: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM6 --setactivepartition=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
13:34:25: INFO: Current working dir (cwd): C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\
13:34:25: INFO: Showing network mappings to allow debugging
13:34:25: INFO: User wants to talk to port '\\.\COM6'
13:34:25: INFO: Took 0.00000000 seconds to open port
13:34:25: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
13:34:25: INFO: If you don't want this, use --dontsorttags
13:34:25: INFO: Sending <configure>
13:34:25: INFO: TARGET SAID: 'fh.attrs.MaxPayloadSizeToTargetInBytes _ FIREHOSE_CHANNEL_BUFFER_SIZE'
13:34:25: INFO: TARGET SAID: 'Calling hotplug_poll_device('MMC')'
13:34:25: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 8192
13:34:25: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 8192
13:34:25: INFO: Target returned NAK for your <configure> but it does not seem to be an error. This is ok, fh_loader.exe attributes updated
13:34:25: INFO: Sending <setbootablestoragedrive>
13:34:25: INFO: ==============================================================
13:34:25: INFO: Files used and their paths
13:34:25: INFO: 1 'C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt'
13:34:25: INFO: _ (done)
13:34:25: INFO: | |
13:34:25: INFO: __| | ___ _ __ ___
13:34:25: INFO: / _` |/ _ \| '_ \ / _ \
13:34:25: INFO: | (_| | (_) | | | | __/
13:34:25: INFO: \__,_|\___/|_| |_|\___|
13:34:25: INFO: {All Finished Successfully}
13:34:25: INFO: FILE ACCESS SLOW!! 0.00 B in 0.015 seconds ( 0.00 Bps) --- Overall to target 0.062 seconds (0.00 Bps)
Writing log to 'C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt', might take a minute
Log is 'C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt'
Download Succeed
Finish Download

noel figueroa said:
Validating Application Configuration
Load APP Configuration
COM:6
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:\LG\H810 firmware\prog_emmc_firehose_8992_lite.mbn
RESETSAHARASTATEEMACHINE:False
SEARCHPATH:\LG\H810 firmware
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
AUTOPRESERVEPARTITIONS:False
PARTITIONPRESERVEMODE:0
PRESERVEDPARTITIONS:0
PRESERVEDPARTITIONS:
ERASEALL:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: D:\LG\H810 firmware
RAWPROGRAM file path: D:\LG\H810 firmware\rawprogram0.xml
PATCH file path:\LG\H810 firmware\patch0.xml
Programmer Path:\LG\H810 firmware\prog_emmc_firehose_8992_lite.mbn
Process Index:0
Programmer Path:C:\Users\SADIK\Desktop\RecoveryImage\prog_emmc_firehose_8992_lite.mbn
Image Search Path: C:\Users\SADIK\Desktop\RecoveryImage
RAWPROGRAM file path: C:\Users\SADIK\Desktop\RecoveryImage\rawprogram0.xml
PATCH file path:C:\Users\SADIK\Desktop\RecoveryImage\patch0.xml
Image Search Path: C:\Users\SADIK\Desktop\RecoveryImage
RAWPROGRAM file path: C:\Users\SADIK\Desktop\RecoveryImage\rawprogram0.xml
PATCH file path:C:\Users\SADIK\Desktop\RecoveryImage\patch0.xml
Start Download
Program Path:C:\Users\SADIK\Desktop\RecoveryImage\prog_emmc_firehose_8992_lite.mbn
***** Working Folder:C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
Binary build date: Oct 31 2016 @ 22:51:05
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\Users\SADIK\Desktop\RecoveryImage\prog_emmc_firehose_8992_lite.mbn
13:33:56: Requested ID 13, file: "C:\Users\SADIK\Desktop\RecoveryImage\prog_emmc_firehose_8992_lite.mbn"
13:33:56: 273568 bytes transferred in 0.125000 seconds (2.0872MBps)
13:33:56: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
13:33:56: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
***** Working Folder:C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
Base Version: 16.10.28.15.28
Binary build date: Oct 31 2016 @ 22:51:02
Incremental Build version: 16.10.31.22.51.02
13:34:00: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM6 --sendxml=rawprogram0.xml --search_path=C:\Users\SADIK\Desktop\RecoveryImage --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
13:34:00: INFO: Current working dir (cwd): C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\
13:34:00: INFO: Showing network mappings to allow debugging
13:34:00: INFO:
13:34:00: INFO: Trying to store 'rawprogram0.xml' in string table
13:34:00: INFO: Looking for file 'rawprogram0.xml'
13:34:00: INFO: User wants to talk to port '\\.\COM6'
13:34:00: INFO: Took 0.00000000 seconds to open port
13:34:00: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
13:34:00: INFO: If you don't want this, use --dontsorttags
13:34:00: INFO: Looking for file 'pmic.mbn'
13:34:00: INFO: Looking for file 'sbl1.mbn'
13:34:00: INFO: Looking for file 'tz.mbn'
13:34:00: INFO: Looking for file 'sdi.mbn'
13:34:00: INFO: Looking for file 'hyp.mbn'
13:34:00: INFO: Looking for file 'rpm.mbn'
13:34:00: INFO: Looking for file 'emmc_appsboot.mbn'
13:34:00: INFO: Looking for file 'laf.img'
13:34:00: INFO: Looking for file 'gpt_main0.bin'
13:34:00: INFO: Looking for file 'gpt_backup0.bin'
13:34:00: INFO:
Total to be tansferd with <program> or <read> is 39.71 MB
13:34:00: INFO: Sending <configure>
13:34:00: INFO: TARGET SAID: 'Binary build date: Mar 3 2015 @ 19:29:19'
13:34:00: INFO: TARGET SAID: 'Chip serial num: 8063555 (0x7b0a43)'
13:34:00: INFO: TARGET SAID: 'Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke '
13:34:00: INFO: TARGET SAID: 'fh.attrs.MaxPayloadSizeToTargetInBytes _ FIREHOSE_CHANNEL_BUFFER_SIZE'
13:34:00: INFO: TARGET SAID: 'Calling hotplug_poll_device('MMC')'
13:34:00: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 8192
13:34:00: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 8192
13:34:00: INFO: Target returned NAK for your <configure> but it does not seem to be an error. This is ok, fh_loader.exe attributes updated
13:34:00: INFO: In handleProgram('pmic.mbn')
13:34:00: INFO: Looking for file 'pmic.mbn'
13:34:00: INFO: =======================================================
13:34:00: INFO: {<program> FILE: 'C:\Users\SADIK\Desktop\RecoveryImage\pmic.mbn'}
13:34:00: INFO: {<program> (36.73 KB) 74 sectors needed at location 229376 on LUN 0}
13:34:00: INFO: =======================================================
13:34:00: INFO: TARGET SAID: 'start 229376, num 74'
13:34:00: INFO: FILE ACCESS SLOW!! 37.00 KB in 0.015 seconds ( 2.41 MBps) --- Overall to target 0.016 seconds (2.26 MBps)
13:34:00: INFO: {percent files transferred 0.09%}
13:34:00: INFO: TARGET SAID: 'Finished sector address 229450'
13:34:00: INFO:
13:34:00: INFO: =======================================================
13:34:00: INFO: ==================== {SUCCESS} ========================
13:34:00: INFO: =======================================================
13:34:00: INFO: {percent files transferred 0.09%}
13:34:00: INFO: In handleProgram('sbl1.mbn')
13:34:00: INFO: Looking for file 'sbl1.mbn'
13:34:00: INFO: =======================================================
13:34:00: INFO: {<program> FILE: 'C:\Users\SADIK\Desktop\RecoveryImage\sbl1.mbn'}
13:34:00: INFO: {<program> (575.50 KB) 1151 sectors needed at location 230400 on LUN 0}
13:34:00: INFO: =======================================================
13:34:00: INFO: TARGET SAID: 'start 230400, num 1151'
13:34:01: INFO: FILE ACCESS SLOW!! 575.50 KB in 0.015 seconds ( 37.47 MBps) --- Overall to target 0.312 seconds (1.80 MBps)
13:34:01: INFO: {percent files transferred 1.51%}
13:34:01: INFO: TARGET SAID: 'Finished sector address 231551'
13:34:01: INFO:
13:34:01: INFO: =======================================================
13:34:01: INFO: ==================== {SUCCESS} ========================
13:34:01: INFO: =======================================================
13:34:01: INFO: {percent files transferred 1.51%}
13:34:01: INFO: In handleProgram('tz.mbn')
13:34:01: INFO: Looking for file 'tz.mbn'
13:34:01: INFO: =======================================================
13:34:01: INFO: {<program> FILE: 'C:\Users\SADIK\Desktop\RecoveryImage\tz.mbn'}
13:34:01: INFO: {<program> (560.20 KB) 1121 sectors needed at location 232448 on LUN 0}
13:34:01: INFO: =======================================================
13:34:01: INFO: TARGET SAID: 'start 232448, num 1121'
13:34:01: INFO: FILE ACCESS SLOW!! 560.50 KB in 0.015 seconds ( 36.49 MBps) --- Overall to target 0.312 seconds (1.75 MBps)
13:34:01: INFO: {percent files transferred 2.88%}
13:34:01: INFO: TARGET SAID: 'Finished sector address 233569'
13:34:01: INFO:
13:34:01: INFO: =======================================================
13:34:01: INFO: ==================== {SUCCESS} ========================
13:34:01: INFO: =======================================================
13:34:01: INFO: {percent files transferred 2.88%}
13:34:01: INFO: In handleProgram('sdi.mbn')
13:34:01: INFO: Looking for file 'sdi.mbn'
13:34:01: INFO: =======================================================
13:34:01: INFO: {<program> FILE: 'C:\Users\SADIK\Desktop\RecoveryImage\sdi.mbn'}
13:34:01: INFO: {<program> (27.88 KB) 56 sectors needed at location 234496 on LUN 0}
13:34:01: INFO: =======================================================
13:34:01: INFO: TARGET SAID: 'start 234496, num 56'
13:34:01: INFO: FILE ACCESS SLOW!! 28.00 KB in 0.015 seconds ( 1.82 MBps) --- Overall to target 0.016 seconds (1.71 MBps)
13:34:01: INFO: {percent files transferred 2.95%}
13:34:01: INFO: TARGET SAID: 'Finished sector address 234552'
13:34:01: INFO:
13:34:01: INFO: =======================================================
13:34:01: INFO: ==================== {SUCCESS} ========================
13:34:01: INFO: =======================================================
13:34:01: INFO: {percent files transferred 2.95%}
13:34:01: INFO: In handleProgram('hyp.mbn')
13:34:01: INFO: Looking for file 'hyp.mbn'
13:34:01: INFO: =======================================================
13:34:01: INFO: {<program> FILE: 'C:\Users\SADIK\Desktop\RecoveryImage\hyp.mbn'}
13:34:01: INFO: {<program> (92.30 KB) 185 sectors needed at location 235520 on LUN 0}
13:34:01: INFO: =======================================================
13:34:01: INFO: TARGET SAID: 'start 235520, num 185'
13:34:01: INFO: FILE ACCESS SLOW!! 92.50 KB in 0.015 seconds ( 6.02 MBps) --- Overall to target 0.047 seconds (1.92 MBps)
13:34:01: INFO: {percent files transferred 3.18%}
13:34:01: INFO: TARGET SAID: 'Finished sector address 235705'
13:34:01: INFO:
13:34:01: INFO: =======================================================
13:34:01: INFO: ==================== {SUCCESS} ========================
13:34:01: INFO: =======================================================
13:34:01: INFO: {percent files transferred 3.18%}
13:34:01: INFO: In handleProgram('rpm.mbn')
13:34:01: INFO: Looking for file 'rpm.mbn'
13:34:01: INFO: =======================================================
13:34:01: INFO: {<program> FILE: 'C:\Users\SADIK\Desktop\RecoveryImage\rpm.mbn'}
13:34:01: INFO: {<program> (187.04 KB) 375 sectors needed at location 236544 on LUN 0}
13:34:01: INFO: =======================================================
13:34:01: INFO: TARGET SAID: 'start 236544, num 375'
13:34:01: INFO: FILE ACCESS SLOW!! 187.50 KB in 0.015 seconds ( 12.21 MBps) --- Overall to target 0.094 seconds (1.95 MBps)
13:34:01: INFO: {percent files transferred 3.64%}
13:34:01: INFO: TARGET SAID: 'Finished sector address 236919'
13:34:01: INFO:
13:34:01: INFO: =======================================================
13:34:01: INFO: ==================== {SUCCESS} ========================
13:34:01: INFO: =======================================================
13:34:01: INFO: {percent files transferred 3.64%}
13:34:01: INFO: In handleProgram('emmc_appsboot.mbn')
13:34:01: INFO: Looking for file 'emmc_appsboot.mbn'
13:34:01: INFO: =======================================================
13:34:01: INFO: {<program> FILE: 'C:\Users\SADIK\Desktop\RecoveryImage\emmc_appsboot.mbn'}
13:34:01: INFO: {<program> (635.64 KB) 1272 sectors needed at location 237568 on LUN 0}
13:34:01: INFO: =======================================================
13:34:01: INFO: TARGET SAID: 'start 237568, num 1272'
13:34:02: INFO: FILE ACCESS SLOW!! 636.00 KB in 0.015 seconds ( 41.41 MBps) --- Overall to target 0.343 seconds (1.81 MBps)
13:34:02: INFO: {percent files transferred 5.20%}
13:34:02: INFO: TARGET SAID: 'Finished sector address 238840'
13:34:02: INFO:
13:34:02: INFO: =======================================================
13:34:02: INFO: ==================== {SUCCESS} ========================
13:34:02: INFO: =======================================================
13:34:02: INFO: {percent files transferred 5.20%}
13:34:02: INFO: In handleProgram('laf.img')
13:34:02: INFO: Looking for file 'laf.img'
13:34:02: INFO: =======================================================
13:34:02: INFO: {<program> FILE: 'C:\Users\SADIK\Desktop\RecoveryImage\laf.img'}
13:34:02: INFO: {<program> (37.62 MB) 77036 sectors needed at location 393216 on LUN 0}
13:34:02: INFO: =======================================================
13:34:02: INFO: TARGET SAID: 'start 393216, num 77036'
13:34:04: INFO: Overall to target 2.012 seconds (1.76 MBps)
13:34:04: INFO: {percent files transferred 14.13%}
13:34:06: INFO: Overall to target 4.025 seconds (1.76 MBps)
13:34:06: INFO: {percent files transferred 23.04%}
13:34:08: INFO: Overall to target 6.037 seconds (1.76 MBps)
13:34:08: INFO: {percent files transferred 31.96%}
13:34:10: INFO: Overall to target 8.049 seconds (1.76 MBps)
13:34:10: INFO: {percent files transferred 40.91%}
13:34:12: INFO: Overall to target 10.062 seconds (1.76 MBps)
13:34:12: INFO: {percent files transferred 49.84%}
13:34:14: INFO: Overall to target 12.074 seconds (1.76 MBps)
13:34:14: INFO: {percent files transferred 58.77%}
13:34:16: INFO: Overall to target 14.087 seconds (1.76 MBps)
13:34:16: INFO: {percent files transferred 67.72%}
13:34:18: INFO: Overall to target 16.099 seconds (1.76 MBps)
13:34:18: INFO: {percent files transferred 76.65%}
13:34:20: INFO: Overall to target 18.111 seconds (1.76 MBps)
13:34:20: INFO: {percent files transferred 85.60%}
13:34:22: INFO: Overall to target 20.124 seconds (1.76 MBps)
13:34:22: INFO: {percent files transferred 94.55%}
13:34:23: INFO: Overall to target 21.325 seconds (1.76 MBps)
13:34:23: INFO: {percent files transferred 99.92%}
13:34:23: INFO: TARGET SAID: 'Finished sector address 470252'
13:34:23: INFO:
13:34:23: INFO: =======================================================
13:34:23: INFO: ==================== {SUCCESS} ========================
13:34:23: INFO: =======================================================
13:34:23: INFO: {percent files transferred 99.92%}
13:34:23: INFO: In handleProgram('gpt_main0.bin')
13:34:23: INFO: Looking for file 'gpt_main0.bin'
13:34:23: INFO: =======================================================
13:34:23: INFO: {<program> FILE: 'C:\Users\SADIK\Desktop\RecoveryImage\gpt_main0.bin'}
13:34:23: INFO: {<program> (17.00 KB) 34 sectors needed at location 0 on LUN 0}
13:34:23: INFO: =======================================================
13:34:23: INFO: TARGET SAID: 'start 0, num 34'
13:34:23: INFO: FILE ACCESS SLOW!! 17.00 KB in 0.015 seconds ( 1.11 MBps) --- Overall to target 0.015 seconds (1.11 MBps)
13:34:23: INFO: {percent files transferred 99.96%}
13:34:23: INFO: TARGET SAID: 'Finished sector address 34'
13:34:23: INFO:
13:34:23: INFO: =======================================================
13:34:23: INFO: ==================== {SUCCESS} ========================
13:34:23: INFO: =======================================================
13:34:23: INFO: {percent files transferred 99.96%}
13:34:23: INFO: In handleProgram('gpt_backup0.bin')
13:34:23: INFO: Looking for file 'gpt_backup0.bin'
13:34:23: INFO: =======================================================
13:34:23: INFO: {<program> FILE: 'C:\Users\SADIK\Desktop\RecoveryImage\gpt_backup0.bin'}
13:34:23: INFO: {<program> (16.50 KB) 33 sectors needed at location 0 on LUN 0}
13:34:23: INFO: =======================================================
13:34:23: INFO: TARGET SAID: 'start 61071327, num 33'
13:34:23: INFO: FILE ACCESS SLOW!! 16.50 KB in 0.015 seconds ( 1.07 MBps) --- Overall to target 0.010 seconds (1.61 MBps)
13:34:23: INFO: {percent files transferred 100.00%}
13:34:23: INFO: TARGET SAID: 'Finished sector address 61071360'
13:34:23: INFO:
13:34:23: INFO: =======================================================
13:34:23: INFO: ==================== {SUCCESS} ========================
13:34:23: INFO: =======================================================
13:34:23: INFO: {percent files transferred 100.00%}
13:34:23: INFO: ==============================================================
13:34:23: INFO: Files used and their paths
13:34:23: INFO: 1 'C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt'
13:34:23: INFO: 2 'C:\Users\SADIK\Desktop\RecoveryImage\rawprogram0.xml'
13:34:23: INFO: 3 'C:\Users\SADIK\Desktop\RecoveryImage\pmic.mbn'
13:34:23: INFO: 4 'C:\Users\SADIK\Desktop\RecoveryImage\sbl1.mbn'
13:34:23: INFO: 5 'C:\Users\SADIK\Desktop\RecoveryImage\tz.mbn'
13:34:23: INFO: 6 'C:\Users\SADIK\Desktop\RecoveryImage\sdi.mbn'
13:34:23: INFO: 7 'C:\Users\SADIK\Desktop\RecoveryImage\hyp.mbn'
13:34:23: INFO: 8 'C:\Users\SADIK\Desktop\RecoveryImage\rpm.mbn'
13:34:23: INFO: 9 'C:\Users\SADIK\Desktop\RecoveryImage\emmc_appsboot.mbn'
13:34:23: INFO: 10 'C:\Users\SADIK\Desktop\RecoveryImage\laf.img'
13:34:23: INFO: 11 'C:\Users\SADIK\Desktop\RecoveryImage\gpt_main0.bin'
13:34:23: INFO: 12 'C:\Users\SADIK\Desktop\RecoveryImage\gpt_backup0.bin'
13:34:23: INFO: _ (done)
13:34:23: INFO: | |
13:34:23: INFO: __| | ___ _ __ ___
13:34:23: INFO: / _` |/ _ \| '_ \ / _ \
13:34:23: INFO: | (_| | (_) | | | | __/
13:34:23: INFO: \__,_|\___/|_| |_|\___|
13:34:23: INFO: {All Finished Successfully}
13:34:23: INFO: Overall to target 23.525 seconds (1.69 MBps)
13:34:23: INFO: {percent files transferred 100.00%}
Writing log to 'C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt', might take a minute
Log is 'C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt'
***** Working Folder:C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
Base Version: 16.10.28.15.28
Binary build date: Oct 31 2016 @ 22:51:02
Incremental Build version: 16.10.31.22.51.02
13:34:24: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM6 --sendxml=patch0.xml --search_path=C:\Users\SADIK\Desktop\RecoveryImage --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
13:34:24: INFO: Current working dir (cwd): C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\
13:34:24: INFO: Showing network mappings to allow debugging
13:34:24: INFO:
13:34:24: INFO: Trying to store 'patch0.xml' in string table
13:34:24: INFO: Looking for file 'patch0.xml'
13:34:24: INFO: User wants to talk to port '\\.\COM6'
13:34:24: INFO: Took 0.00000000 seconds to open port
13:34:24: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
13:34:24: INFO: If you don't want this, use --dontsorttags
13:34:24: INFO: Sending <configure>
13:34:24: INFO: TARGET SAID: 'fh.attrs.MaxPayloadSizeToTargetInBytes _ FIREHOSE_CHANNEL_BUFFER_SIZE'
13:34:24: INFO: TARGET SAID: 'Calling hotplug_poll_device('MMC')'
13:34:24: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 8192
13:34:24: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 8192
13:34:24: INFO: Target returned NAK for your <configure> but it does not seem to be an error. This is ok, fh_loader.exe attributes updated
13:34:24: INFO: TARGET SAID: 'Patched sector 15 with 03A3DFDE'
13:34:24: INFO: TARGET SAID: 'Patched sector 61071340 with 03A3DFDE'
13:34:24: INFO: TARGET SAID: 'Patched sector 1 with 03A3DFDE'
13:34:24: INFO: TARGET SAID: 'Patched sector 61071359 with 03A3DFDE'
13:34:24: INFO: TARGET SAID: 'Patched sector 1 with 03A3DFFF'
13:34:24: INFO: TARGET SAID: 'Patched sector 61071359 with 03A3DFFF'
13:34:24: INFO: TARGET SAID: 'Patched sector 61071359 with 03A3DFDF'
13:34:24: INFO: TARGET SAID: 'crc start sector 2, over bytes 7168'
13:34:24: INFO: TARGET SAID: 'Patched sector 1 with DA92707B'
13:34:24: INFO: TARGET SAID: 'crc start sector 61071327, over bytes 7168'
13:34:25: INFO: TARGET SAID: 'Patched sector 61071359 with DA92707B'
13:34:25: INFO: TARGET SAID: 'Patched sector 1 with 00000000'
13:34:25: INFO: TARGET SAID: 'crc start sector 1, over bytes 92'
13:34:25: INFO: TARGET SAID: 'Patched sector 1 with 016ABE28'
13:34:25: INFO: TARGET SAID: 'Patched sector 61071359 with 00000000'
13:34:25: INFO: TARGET SAID: 'crc start sector 61071359, over bytes 92'
13:34:25: INFO: TARGET SAID: 'Patched sector 61071359 with BD45EE20'
13:34:25: INFO: ==============================================================
13:34:25: INFO: Files used and their paths
13:34:25: INFO: 1 'C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt'
13:34:25: INFO: 2 'C:\Users\SADIK\Desktop\RecoveryImage\patch0.xml'
13:34:25: INFO: _ (done)
13:34:25: INFO: | |
13:34:25: INFO: __| | ___ _ __ ___
13:34:25: INFO: / _` |/ _ \| '_ \ / _ \
13:34:25: INFO: | (_| | (_) | | | | __/
13:34:25: INFO: \__,_|\___/|_| |_|\___|
13:34:25: INFO: {All Finished Successfully}
13:34:25: INFO: FILE ACCESS SLOW!! 0.00 B in 0.015 seconds ( 0.00 Bps) --- Overall to target 0.639 seconds (0.00 Bps)
Writing log to 'C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt', might take a minute
Log is 'C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt'
***** Working Folder:C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
Base Version: 16.10.28.15.28
Binary build date: Oct 31 2016 @ 22:51:02
Incremental Build version: 16.10.31.22.51.02
13:34:25: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM6 --setactivepartition=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
13:34:25: INFO: Current working dir (cwd): C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\
13:34:25: INFO: Showing network mappings to allow debugging
13:34:25: INFO: User wants to talk to port '\\.\COM6'
13:34:25: INFO: Took 0.00000000 seconds to open port
13:34:25: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
13:34:25: INFO: If you don't want this, use --dontsorttags
13:34:25: INFO: Sending <configure>
13:34:25: INFO: TARGET SAID: 'fh.attrs.MaxPayloadSizeToTargetInBytes _ FIREHOSE_CHANNEL_BUFFER_SIZE'
13:34:25: INFO: TARGET SAID: 'Calling hotplug_poll_device('MMC')'
13:34:25: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 8192
13:34:25: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 8192
13:34:25: INFO: Target returned NAK for your <configure> but it does not seem to be an error. This is ok, fh_loader.exe attributes updated
13:34:25: INFO: Sending <setbootablestoragedrive>
13:34:25: INFO: ==============================================================
13:34:25: INFO: Files used and their paths
13:34:25: INFO: 1 'C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt'
13:34:25: INFO: _ (done)
13:34:25: INFO: | |
13:34:25: INFO: __| | ___ _ __ ___
13:34:25: INFO: / _` |/ _ \| '_ \ / _ \
13:34:25: INFO: | (_| | (_) | | | | __/
13:34:25: INFO: \__,_|\___/|_| |_|\___|
13:34:25: INFO: {All Finished Successfully}
13:34:25: INFO: FILE ACCESS SLOW!! 0.00 B in 0.015 seconds ( 0.00 Bps) --- Overall to target 0.062 seconds (0.00 Bps)
Writing log to 'C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt', might take a minute
Log is 'C:\Users\SADIK\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\port_trace.txt'
Download Succeed
Finish Download
Click to expand...
Click to collapse
lütfen banada yardım et

totally bricked a Xiaomi 6, could anyone help?

Hello everyone,
I own a Xiaomi 6 (6GB/64GB), two weeks before, I have received a update notification from Xiaomi. When the update package was downloaded, and the phone restarted automatically. I left the phone alone, without any attention to it. Several minutes later, I found its screen was still dark, and I thought maybe something bad had happened. So I long pressed the power button, but nothing happens. Now it is, a totally bricked phone. It can't enter fastboot mode in any way. Once connected to a computer with USB cable, the computer detects a Qualcomm HS-USB QDLoader 9008 device. I have searched a lot, trying MIFlash and QPST, but noting helps. The QSPT can detect a com port, but it show the phone is Unkonwn and the ESN is No ESN. I have tried all and I am almost give up now. Please help me, or maybe I should consider buy another phone.
Thank you very much.
error log:
Validating Application Configuration
Load APP Configuration
COM:0
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:
RESETSAHARASTATEEMACHINE:False
SEARCHPATH:C:\
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
AUTOPRESERVEPARTITIONS:False
PARTITIONPRESERVEMODE:0
PRESERVEDPARTITIONS:0
PRESERVEDPARTITIONS:
ERASEALL:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\
Process Index:0
Programmer Path:\MIUI\sagit_images_V9.5.8.0.OCACNFA_20180509.0000.00_8.0_cn\images\prog_ufs_firehose_8998_ddr.elf
Image Search Path: D:\MIUI\sagit_images_V9.5.8.0.OCACNFA_20180509.0000.00_8.0_cn\images
Image Search Path: D:\MIUI\sagit_images_V9.5.8.0.OCACNFA_20180509.0000.00_8.0_cn\images
RAWPROGRAM file path: D:\MIUI\sagit_images_V9.5.8.0.OCACNFA_20180509.0000.00_8.0_cn\images\rawprogram0.xml
PATCH file path:\MIUI\sagit_images_V9.5.8.0.OCACNFA_20180509.0000.00_8.0_cn\images\patch0.xml
Start Download
Program Path:\MIUI\sagit_images_V9.5.8.0.OCACNFA_20180509.0000.00_8.0_cn\images\prog_ufs_firehose_8998_ddr.elf
***** Working Folder:C:\Users\zxw-hu\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
Binary build date: Oct 31 2016 @ 22:51:05
QSAHARASERVER CALLED LIKE THIS: 'D:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\zxw-hu\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: D:\MIUI\sagit_images_V9.5.8.0.OCACNFA_20180509.0000.00_8.0_cn\images\prog_ufs_firehose_8998_ddr.elf
17:29:36: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
17:29:36: ERROR: function: sahara_main:924 Sahara protocol error
17:29:36: ERROR: function: main:303 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download

[GUIDE] How to dump and write back the storage on most of Qualcomm devices

This is a generic guide that could be suitable for many Qualcomm based devices, once the phone can be triggered to EDL mode.
To make sure this guide will work as expect, following requirements are needed:
- Know how to trigger the phone to EDL mode, and you can force reboot the phone (Required for Driver Changing)
- Qualcomm EDL mode doesn't require service authentication, or specially modded (e.g. Lumia Emergency Files)
- Firehose file for your SoC and storage type (eMMC or UFS storage)
- Latest Qualcomm USB Drivers (at least 2.1.2.0 or newer, you can check yourself in Device Manager) and QPST Tool
Driver version is pretty important. If older than 2.1.2.0, it won't support partition dumping properly.
You may need to reboot your Windows PC to Disable Driver Signature Enforcement mode to allow you use the driver.
I won't provide any download link of the proper drivers, please find yourself.
Click to expand...
Click to collapse
For non-Android Smartphones, HP Elite X3 (At least for prototype unit) is confirmed working with this method.
Most of Android Smartphones should work as well.
Step 1: Trigger the phone to EDL mode
Following methods can be used as reference:
- Connect your phone to PC with a specific key pressed
e.g. TCL / Alcatel / Blackberry Android Smartphones can use Volume Down key to trigger to EDL mode
- EDL cable (DIY or order it on eBay / AliExpress, keyword: Xiaomi EDL cable)
e.g. Smartisan Smartphones that made recently can use EDL cable to unlock the bootloader.
- Fastboot command
e.g. Few Xiaomi Phones
- Wire trick
If you know where's the test point / components (like resistant) on CLK pin of eMMC/UFS storage is connected as well, short it to the GND will trigger your phone to EDL mode.
This will be usable for almost every Qualcomm devices, once you have schematic provided by the manufacturer.
- Erase aboot / abl / xbl / UEFI from your phone
This method is dangerous, do it at your own risk!
Step 2: Change the Driver to Qualcomm HS-USB QDLoader 9008
Skip this step if it's already indicated as HS-USB QDLoader 9008 in Device Manager, "Ports (COM or LPT)" category.
If it's indicated as HS-USB Diagnostics 9008 in "Ports (COM or LPT)" category, or "QHSUSB__BULK" in "Universal Serial Bus devices" category, you must update the driver to Qualcomm HS-USB QDLoader 9008, then reboot your phone to Qualcomm EDL mode again to ensure the EDL port will not throttle.
To reboot your phone, you need to perform hard reboot until you see the port disappeared immediately or refresh (in case the phone is bricked).
Step 3: Open QFIL, load Firehose file
You must choose correct storage type in right down corner.
In many cases keep it as "emmc" for default, otherwise choose "ufs" for flagship devices. In this case we choose emmc.
Then choose "Flat Build" as Build Type, and select the firehose file for your phone. If there's no firehose file specifically for your device, you may want to choose another firehose file for the same SoC, same storage type for different phone.
For example, I used the "prog_emmc_firehose_8996_ddr.elf" for ZUK Z2 on HP Elite X3 and it works perfectly.
In many cases, you can obtain firehose file for your phone from stock firmware.
Click to expand...
Click to collapse
Step 4: Open Partition Manager
Now choose "Tools" - "Partition Manager", and please pay attention to the Status box.
When it indicates:
Code:
2019-07-18 20:04:19.775 20:04:19: Sahara protocol completed
2019-07-18 20:04:19.776 Sending Programmer Finished
2019-07-18 20:04:19.776 Switch To FireHose
2019-07-18 20:04:19.777 Wait for 3 seconds...
If you didn't see the output above, then the firehose file is incorrect or the EDL port is throttled. Reboot your phone to EDL mode again.
Then you've partially succeeded, just wait for the Partition Manager appears.
This is the partition table of your phone. Please take note on the Start LBA and LBA number of the last partition.
Take HP Elite X3 partition table for example, the last partition is "Data", it's Start LBA and LBA number are 0x01E20000 and 0x0565BFDF. Add both of them will get the total sector numbers of whole eMMC storage - in this case, 0x0747BFDF, or 122,142,687 sectors. Multiple the sector numbers with 512 will get the total bytes of the eMMC storage, in this case, the capacity of eMMC storage is 62,537,055,744‬ bytes.
You'll need the number 122,142,687 for later use.
If you don't want to dump userdata partition, just use the Start LBA value of userdata partition and convert it to decimal values - the overall dump will not contain actual userdata.
Don't close Partition Manager, we need to keep it for later use.
Now choose either Step 5A or 5B as your wish.
Step 5A: Dump the storage
Please copy following path to your File Explorer:
Code:
%AppData%\Qualcomm\QFIL
This will redirect you to C:\Users\[your_user_name]\AppData\Roaming\Qualcomm\QFIL .
Find the COMPORT_XX directory respective to your exact COM port - in this case, I choose COMPORT_8 for example.
And open a command prompt or PowerShell window here.
Execute following command here, remember to change the COM port number and num_sectors to your exact number, or the actual path of fh_loader.exe and your dump if possible:
Note, this command will not create the path of your dump for you, you must create yourself.
Code:
"C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe" --port=\\.\COM8 --search_path=D:\path\to\your\dump --convertprogram2read --sendimage=full_dump.bin --start_sector=0 --lun=0 --num_sectors=122142687 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
Now just wait for dumping procedure complete.
Expected output should look like this:
Code:
20:45:50: INFO: Current working dir (cwd): C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\
20:45:50: INFO: Showing network mappings to allow debugging
20:45:50: INFO: Looking for file 'full_dump.bin'
(_)
__ ____ _ _ __ _ __ _ _ __ __ _
\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
\ V V / (_| | | | | | | | | | | (_| |
\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
__/ |
|___/
20:45:50: WARNING: Couldn't find the file 'full_dump.bin', returning NULL
(_)
__ ____ _ _ __ _ __ _ _ __ __ _
\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
\ V V / (_| | | | | | | | | | | (_| |
\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
__/ |
|___/
20:45:50: WARNING: User specified --num_sectors=524288 but file only has 524288 sectors. **Ignoring --num_sectors
20:45:50: INFO: User wants to talk to port '\\.\COM8'
20:45:50: INFO: Took 0.00000000 seconds to open port
20:45:50: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
20:45:50: INFO: If you don't want this, use --dontsorttags
20:45:50: INFO: Looking for file 'full_dump.bin'
(_)
__ ____ _ _ __ _ __ _ _ __ __ _
\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
\ V V / (_| | | | | | | | | | | (_| |
\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
__/ |
|___/
20:45:50: WARNING: Couldn't find the file 'full_dump.bin', returning NULL
20:45:50: INFO: Sending <configure>
20:45:50: INFO: TARGET SAID: 'Calling usb_al_bulk_set_zlp_mode(TRUE) since ZlpAwareHost='1''
20:45:50: INFO: TARGET SAID: 'Calling hotplug_poll_device('MMC')'
20:45:50: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
20:45:50: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
20:45:50: INFO: In handleRead('full_dump.bin')
20:45:50: INFO: Looking for file 'full_dump.bin'
(_)
__ ____ _ _ __ _ __ _ _ __ __ _
\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
\ V V / (_| | | | | | | | | | | (_| |
\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
__/ |
|___/
20:45:50: WARNING: Previous Filesize is 0 bytes. Therefore reading size of partition!! Please check 'full_dump.bin'
20:45:50: INFO: =======================================================
20:45:50: INFO: <read> (262144.0KB) 524288 sectors from location 0 FILE: 'full_dump.bin'
20:45:50: INFO: =======================================================
20:45:52: INFO: Overall to target 2.000 seconds (32.34 MBps)
20:45:54: INFO: Overall to target 4.000 seconds (32.38 MBps)
20:45:56: INFO: Overall to target 6.000 seconds (32.37 MBps)
20:45:58: INFO: Overall to target 7.844 seconds (32.64 MBps)
20:45:58: INFO: TARGET SAID: 'Finished reading from sector address 0 to 524288'
20:45:58: INFO: =======================================================
20:45:58: INFO: ===================== SUCCESS =========================
20:45:58: INFO: =======================================================
20:45:58: INFO: ==============================================================
20:45:58: INFO: Files used and their paths
20:45:58: INFO: 1 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\port_trace.txt'
20:45:58: INFO: 2 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\full_dump.bin'
(_)
__ ____ _ _ __ _ __ _ _ __ __ _
\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
\ V V / (_| | | | | | | | | | | (_| |
\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
__/ |
|___/
20:45:58: INFO: ==============================================================
20:45:58: INFO: NOTE: There were WARNINGS!! Repeated here, but please see log for more detail
Couldn't find the file 'full_dump.bin', returning NULL
User specified --num_sectors=524288 but file only has 524288 sectors. **Ignoring --num_sectors
Couldn't find the file 'full_dump.bin', returning NULL
Previous Filesize is 0 bytes. Therefore reading size of partition!! Please check 'full_dump.bin'
NOTE: There were WARNINGS!! Repeated above, but please see log for more detail
20:45:58: INFO: ==============================================================
20:45:58: INFO: _ (done)
20:45:58: INFO: | |
20:45:58: INFO: __| | ___ _ __ ___
20:45:58: INFO: / _` |/ _ \| '_ \ / _ \
20:45:58: INFO: | (_| | (_) | | | | __/
20:45:58: INFO: \__,_|\___/|_| |_|\___|
20:45:58: INFO: {All Finished Successfully}
20:45:58: INFO: Overall to target 7.969 seconds (32.12 MBps)
Writing log to 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\port_trace.txt', might take a minute
Log is 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\port_trace.txt'
You can use 7-Zip archiver to open this dump and extract any partition you want.
Step 5B: Write the dump back to storage
Open Partition Manager, and don't close it.
Please copy following path to your File Explorer:
Code:
%AppData%\Qualcomm\QFIL
This will redirect you to C:\Users\[your_user_name]\AppData\Roaming\Qualcomm\QFIL .
Find the COMPORT_XX directory respective to your exact COM port - in this case, I choose COMPORT_8 for example.
And open a command prompt or PowerShell window here.
Execute following command here, remember to change the COM port number and num_sectors to your exact number, or the actual path of fh_loader.exe and your dump if possible:
In this case, the dump is located at D:\path\to\your\dump\full_dump.bin .
Code:
"C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe" --port=\\.\COM8 --search_path=D:\path\to\your\dump --sendimage=full_dump.bin --start_sector=0 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
Now just wait for the procedure complete.
The output should look like this:
Code:
20:05:30: INFO: Current working dir (cwd): C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\
20:05:30: INFO: Showing network mappings to allow debugging
20:05:30: INFO: Looking for file 'full_dump.bin'
20:05:31: INFO: User wants to talk to port '\\.\COM8'
20:05:31: INFO: Took 0.01600000 seconds to open port
20:05:31: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
20:05:31: INFO: If you don't want this, use --dontsorttags
20:05:31: INFO: Looking for file 'full_dump.bin'
20:05:31: INFO:
Total to be tansferd with <program> or <read> is 36.09 GB
20:05:31: INFO: Sending <configure>
20:05:31: INFO: TARGET SAID: 'Calling usb_al_bulk_set_zlp_mode(TRUE) since ZlpAwareHost='1''
20:05:31: INFO: TARGET SAID: 'Calling hotplug_poll_device('MMC')'
20:05:31: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
20:05:31: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
20:05:31: INFO: In handleProgram('full_dump.bin')
20:05:31: INFO: Looking for file 'full_dump.bin'
20:05:31: INFO: =======================================================
20:05:31: INFO: {<program> FILE: 'D:\path\to\your\dump\full_dump.bin'}
20:05:31: INFO: {<program> (36.09 GB) 75685888 sectors needed at location 0 on LUN 0}
20:05:31: INFO: =======================================================
20:05:31: INFO: TARGET SAID: 'start 0, num 75685888'
20:05:33: INFO: Overall to target 2.031 seconds (26.59 MBps)
20:05:33: INFO: {percent files transferred 0.15%}
20:05:35: INFO: Overall to target 4.063 seconds (26.34 MBps)
20:05:35: INFO: {percent files transferred 0.29%}
20:05:37: INFO: Overall to target 6.094 seconds (26.26 MBps)
20:05:37: INFO: {percent files transferred 0.43%}
20:05:39: INFO: Overall to target 8.110 seconds (26.26 MBps)
20:05:39: INFO: {percent files transferred 0.58%}
20:05:41: INFO: Overall to target 10.125 seconds (26.27 MBps)
20:05:41: INFO: {percent files transferred 0.72%}
20:05:43: INFO: Overall to target 12.141 seconds (26.27 MBps)
20:05:43: INFO: {percent files transferred 0.86%}
20:05:45: INFO: Overall to target 14.141 seconds (26.31 MBps)
20:05:45: INFO: {percent files transferred 1.01%}
20:05:47: INFO: Overall to target 16.156 seconds (26.49 MBps)
20:05:47: INFO: {percent files transferred 1.16%}
20:05:49: INFO: Overall to target 18.172 seconds (26.52 MBps)
20:05:49: INFO: {percent files transferred 1.30%}
20:05:51: INFO: Overall to target 20.188 seconds (26.55 MBps)
20:05:51: INFO: {percent files transferred 1.45%}
20:05:53: INFO: Overall to target 22.188 seconds (26.59 MBps)
20:05:53: INFO: {percent files transferred 1.60%}
20:05:55: INFO: Overall to target 24.188 seconds (26.62 MBps)
20:05:55: INFO: {percent files transferred 1.74%}
20:05:57: INFO: Overall to target 26.188 seconds (26.62 MBps)
20:05:57: INFO: {percent files transferred 1.89%}
20:05:59: INFO: Overall to target 28.188 seconds (26.61 MBps)
20:05:59: INFO: {percent files transferred 2.03%}
20:06:01: INFO: Overall to target 30.235 seconds (26.59 MBps)
20:06:01: INFO: {percent files transferred 2.18%}
20:06:03: INFO: Overall to target 32.266 seconds (26.56 MBps)
20:06:03: INFO: {percent files transferred 2.32%}
20:06:05: INFO: Overall to target 34.281 seconds (26.57 MBps)
20:06:05: INFO: {percent files transferred 2.47%}
20:06:07: INFO: Overall to target 36.328 seconds (26.56 MBps)
20:06:07: INFO: {percent files transferred 2.61%}
20:06:09: INFO: Overall to target 38.328 seconds (26.56 MBps)
20:06:09: INFO: {percent files transferred 2.75%}
20:06:11: INFO: Overall to target 40.360 seconds (26.56 MBps)
20:06:11: INFO: {percent files transferred 2.90%}
20:06:13: INFO: Overall to target 42.391 seconds (26.56 MBps)
20:06:13: INFO: {percent files transferred 3.05%}
(ignored too many logs)
20:28:17: INFO: Overall to target 1366.235 seconds (26.33 MBps)
20:28:17: INFO: {percent files transferred 97.33%}
20:28:19: INFO: Overall to target 1368.266 seconds (26.33 MBps)
20:28:19: INFO: {percent files transferred 97.48%}
20:28:21: INFO: Overall to target 1370.281 seconds (26.33 MBps)
20:28:21: INFO: {percent files transferred 97.63%}
20:28:23: INFO: Overall to target 1372.313 seconds (26.33 MBps)
20:28:23: INFO: {percent files transferred 97.78%}
20:28:25: INFO: Overall to target 1374.313 seconds (26.33 MBps)
20:28:25: INFO: {percent files transferred 97.93%}
20:28:27: INFO: Overall to target 1376.344 seconds (26.34 MBps)
20:28:27: INFO: {percent files transferred 98.08%}
20:28:29: INFO: Overall to target 1378.344 seconds (26.34 MBps)
20:28:29: INFO: {percent files transferred 98.22%}
20:28:31: INFO: Overall to target 1380.360 seconds (26.34 MBps)
20:28:31: INFO: {percent files transferred 98.37%}
20:28:33: INFO: Overall to target 1382.375 seconds (26.34 MBps)
20:28:33: INFO: {percent files transferred 98.51%}
20:28:35: INFO: Overall to target 1384.406 seconds (26.34 MBps)
20:28:35: INFO: {percent files transferred 98.66%}
20:28:37: INFO: Overall to target 1386.438 seconds (26.34 MBps)
20:28:37: INFO: {percent files transferred 98.80%}
20:28:39: INFO: Overall to target 1388.438 seconds (26.34 MBps)
20:28:39: INFO: {percent files transferred 98.94%}
20:28:41: INFO: Overall to target 1390.453 seconds (26.34 MBps)
20:28:41: INFO: {percent files transferred 99.09%}
20:28:43: INFO: Overall to target 1392.485 seconds (26.34 MBps)
20:28:43: INFO: {percent files transferred 99.25%}
20:28:45: INFO: Overall to target 1394.516 seconds (26.34 MBps)
20:28:45: INFO: {percent files transferred 99.40%}
20:28:47: INFO: Overall to target 1396.531 seconds (26.34 MBps)
20:28:47: INFO: {percent files transferred 99.55%}
20:28:49: INFO: Overall to target 1398.750 seconds (26.33 MBps)
20:28:49: INFO: {percent files transferred 99.66%}
20:28:51: INFO: Overall to target 1400.766 seconds (26.33 MBps)
20:28:51: INFO: {percent files transferred 99.81%}
20:28:53: INFO: Overall to target 1402.797 seconds (26.33 MBps)
20:28:53: INFO: {percent files transferred 99.96%}
20:28:54: INFO: Overall to target 1403.422 seconds (26.33 MBps)
20:28:54: INFO: {percent files transferred 100.00%}
20:28:54: INFO: TARGET SAID: 'Finished programming start_sector 75685888 and TotalSectorsToProgram 75685888'
20:28:54: INFO:
20:28:54: INFO: =======================================================
20:28:54: INFO: ==================== {SUCCESS} ========================
20:28:54: INFO: =======================================================
20:28:54: INFO: {percent files transferred 100.00%}
20:28:54: INFO: ==============================================================
20:28:54: INFO: Files used and their paths
20:28:54: INFO: 1 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\port_trace.txt'
20:28:54: INFO: 2 'D:\path\to\your\dump\full_dump.bin'
20:28:54: INFO: _ (done)
20:28:54: INFO: | |
20:28:54: INFO: __| | ___ _ __ ___
20:28:54: INFO: / _` |/ _ \| '_ \ / _ \
20:28:54: INFO: | (_| | (_) | | | | __/
20:28:54: INFO: \__,_|\___/|_| |_|\___|
20:28:54: INFO: {All Finished Successfully}
20:28:54: INFO: Overall to target 1403.578 seconds (26.33 MBps)
20:28:54: INFO: {percent files transferred 100.00%}
Writing log to 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\port_trace.txt', might take a minute
Log is 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\port_trace.txt'
If you only want to write back only one specific partition, you need to specify the start_sector value to the decimal value of a partition's Start LBA.
Always keep the Partition Manager window opened!
Step 6: Quit Partition Manager
After everything dumped, you can close Partition Manager, the QFIL will reboot your phone back to EDL mode or reboot your phone back to normal mode.
Then you can force reboot your phone or mess up your phone as you want.

reserved

Awesome Guide!

Qualcomm HS-USB QD loader 9008 drivers showing briefly in device manager
I put Samsung Note 3 ( N9005) Qualcomm based mobile on EDL by ADB Command. The command does work & phone reboot to show in device manager Qualcomm usb Driver, BUT Qualcomm USB drivers disappear after few seconds .... What could be the issue....as i wanted to use QPST ( QFil) to flash the phone but its giving error that no port is selected.
How to make " Qualcomm HS-USB QD loader 9008 " drivers to appear permanently in Device manager.
searched a lot on goolge but nothing is working...
Pls any one help.

user agent said:
I put Samsung Note 3 ( N9005) Qualcomm based mobile on EDL by ADB Command. The command does work & phone reboot to show in device manager Qualcomm usb Driver, BUT Qualcomm USB drivers disappear after few seconds .... What could be the issue....as i wanted to use QPST ( QFil) to flash the phone but its giving error that no port is selected.
How to make " Qualcomm HS-USB QD loader 9008 " drivers to appear permanently in Device manager.
searched a lot on goolge but nothing is working...
Pls any one help.
Click to expand...
Click to collapse
I remember Galaxy Note 3 can remove the battery right?
In may cases, Qualcomm based phone can stay at EDL mode without battery.

the partitiion maneger do not appear
Hey, Thank you so much for prividing this GUIDE!
I just try to maake a backup of my data. I followed the steps above but the partition manager do not appear. Anyone know what is the problem? Log see below. Thank you for any coming tipps!
2020-04-19 23:31:12.778 Validating Application Configuration
2020-04-19 23:31:12.790 Load APP Configuration
2020-04-19 23:31:12.810 COM:12
2020-04-19 23:31:12.810 PBLDOWNLOADPROTOCOL:0
2020-04-19 23:31:12.810 PROGRAMMER:True
2020-04-19 23:31:12.810 PROGRAMMER:\Firefox_download\01\images\prog_ufs_firehose_sdm845_ddr.elf
2020-04-19 23:31:12.810 RESETSAHARASTATEMACHINE:False
2020-04-19 23:31:12.810 SAHARAREADSERIALNO:False
2020-04-19 23:31:12.810 SEARCHPATH:\Firefox_download\01\images
2020-04-19 23:31:12.810 ACKRAWDATAEVERYNUMPACKETS:False
2020-04-19 23:31:12.810 ACKRAWDATAEVERYNUMPACKETS:100
2020-04-19 23:31:12.810 MAXPAYLOADSIZETOTARGETINBYTES:False
2020-04-19 23:31:12.810 MAXPAYLOADSIZETOTARGETINBYTES:49152
2020-04-19 23:31:12.810 DEVICETYPE:ufs
2020-04-19 23:31:12.810 PLATFORM:8x26
2020-04-19 23:31:12.810 VALIDATIONMODE:0
2020-04-19 23:31:12.811 RESETAFTERDOWNLOAD:False
2020-04-19 23:31:12.811 MAXDIGESTTABLESIZE:8192
2020-04-19 23:31:12.811 SWITCHTOFIREHOSETIMEOUT:30
2020-04-19 23:31:12.811 RESETTIMEOUT:200
2020-04-19 23:31:12.811 RESETDELAYTIME:2
2020-04-19 23:31:12.811 METABUILD:
2020-04-19 23:31:12.811 METABUILD:
2020-04-19 23:31:12.811 FLATBUILDPATH:C:\
2020-04-19 23:31:12.811 FLATBUILDFORCEOVERRIDE:True
2020-04-19 23:31:12.811 QCNPATH:C:\Temp\00000000.qcn
2020-04-19 23:31:12.811 QCNAUTOBACKUPRESTORE:False
2020-04-19 23:31:12.811 SPCCODE:000000
2020-04-19 23:31:12.811 ENABLEMULTISIM:False
2020-04-19 23:31:12.811 AUTOPRESERVEPARTITIONS:False
2020-04-19 23:31:12.811 PARTITIONPRESERVEMODE:0
2020-04-19 23:31:12.811 PRESERVEDPARTITIONS:0
2020-04-19 23:31:12.811 PRESERVEDPARTITIONS:
2020-04-19 23:31:12.811 ERASEALL:False
2020-04-19 23:31:12.812 Load ARG Configuration
2020-04-19 23:31:12.888 Validating Download Configuration
2020-04-19 23:31:12.890 Image Search Path: D:\Firefox_download\01\images
2020-04-19 23:31:12.895 Programmer Path:\Firefox_download\01\images\prog_ufs_firehose_sdm845_ddr.elf
2020-04-19 23:31:13.548 Process Index:0
2020-04-19 23:31:13.567 Qualcomm Flash Image Loader (QFIL) 2.0.2.3
2020-04-19 23:32:56.567 Start Download
2020-04-19 23:32:56.588 Program Path:\Firefox_download\01\images\prog_ufs_firehose_sdm845_ddr.elf
2020-04-19 23:32:56.593 ***** Working Folder:C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12
2020-04-19 23:32:57.013 Binary build date: Apr 27 2018 @ 03:04:33
2020-04-19 23:32:57.015 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\QUALCOMM\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12
2020-04-19 23:32:57.018 Sahara mappings:
2020-04-19 23:32:57.020 2: amss.mbn
2020-04-19 23:32:57.020 6: apps.mbn
2020-04-19 23:32:57.021 8: dsp1.mbn
2020-04-19 23:32:57.022 10: dbl.mbn
2020-04-19 23:32:57.022 11: osbl.mbn
2020-04-19 23:32:57.023 12: dsp2.mbn
2020-04-19 23:32:57.023 16: efs1.mbn
2020-04-19 23:32:57.024 17: efs2.mbn
2020-04-19 23:32:57.024 20: efs3.mbn
2020-04-19 23:32:57.025 21: sbl1.mbn
2020-04-19 23:32:57.025 22: sbl2.mbn
2020-04-19 23:32:57.026 23: rpm.mbn
2020-04-19 23:32:57.027 25: tz.mbn
2020-04-19 23:32:57.027 28: dsp3.mbn
2020-04-19 23:32:57.028 29: acdb.mbn
2020-04-19 23:32:57.030 30: wdt.mbn
2020-04-19 23:32:57.031 31: mba.mbn
2020-04-19 23:32:57.032 13: D:\Firefox_download\01\images\prog_ufs_firehose_sdm845_ddr.elf
2020-04-19 23:32:57.032
2020-04-19 23:32:57.033 23:32:56: Requested ID 13, file: "D:\Firefox_download\01\images\prog_ufs_firehose_sdm845_ddr.elf"
2020-04-19 23:32:57.033
2020-04-19 23:32:57.034 23:32:57: 715496 bytes transferred in 0.391000 seconds (1.7451MBps)
2020-04-19 23:32:57.034
2020-04-19 23:32:57.035
2020-04-19 23:32:57.035
2020-04-19 23:32:57.036 23:32:57: File transferred successfully
2020-04-19 23:32:57.036
2020-04-19 23:32:57.036
2020-04-19 23:32:57.037
2020-04-19 23:32:57.038 23:32:57: Sahara protocol completed
2020-04-19 23:32:57.038 Sending Programmer Finished
2020-04-19 23:32:57.039 Switch To FireHose
2020-04-19 23:32:57.039 Wait for 3 seconds...
2020-04-19 23:33:00.041 Max Payload Size to Target:49152 Bytes
2020-04-19 23:33:00.041 Device Type:ufs
2020-04-19 23:33:00.042 Platform:8x26
2020-04-19 23:33:00.043 Disable Ack Raw Data Every N Packets
2020-04-19 23:33:00.044 Skip Write:False
2020-04-19 23:33:00.044 Always Validate:False
2020-04-19 23:33:00.045 Use Verbose:False
2020-04-19 23:33:00.050 ***** Working Folder:C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12
2020-04-19 23:33:00.124
2020-04-19 23:33:00.126 Base Version: 18.02.16.18.26
2020-04-19 23:33:00.131 Binary build date: Apr 27 2018 @ 03:04:29
2020-04-19 23:33:00.131 Incremental Build version: 18.04.27.03.04.29
2020-04-19 23:33:00.138
2020-04-19 23:33:00.138 23:33:00: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
2020-04-19 23:33:00.139 ************************************************
2020-04-19 23:33:00.140 C:\Program Files (x86)\QUALCOMM\QPST\bin\fh_loader.exe --port=\\.\COM12 --search_path=C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12 --convertprogram2read --sendimage=fh_gpt_header_0 --start_sector=1 --lun=0 --num_sectors=1 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
2020-04-19 23:33:00.142 ************************************************
2020-04-19 23:33:00.142
2020-04-19 23:33:00.143 23:33:00: INFO: Current working dir (cwd): C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12\
2020-04-19 23:33:00.144 23:33:00: INFO: Showing network mappings to allow debugging
2020-04-19 23:33:00.145 23:33:00: INFO: Looking for file 'fh_gpt_header_0'
2020-04-19 23:33:00.147
2020-04-19 23:33:00.147
2020-04-19 23:33:00.148 (_)
2020-04-19 23:33:00.149 __ ____ _ _ __ _ __ _ _ __ __ _
2020-04-19 23:33:00.150 \ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
2020-04-19 23:33:00.151 \ V V / (_| | | | | | | | | | | (_| |
2020-04-19 23:33:00.151 \_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
2020-04-19 23:33:00.152 __/ |
2020-04-19 23:33:00.153 |___/
2020-04-19 23:33:00.153
2020-04-19 23:33:00.154
2020-04-19 23:33:00.154 23:33:00: WARNING: Couldn't find the file 'fh_gpt_header_0', returning NULL
2020-04-19 23:33:00.156
2020-04-19 23:33:00.156
2020-04-19 23:33:00.157 (_)
2020-04-19 23:33:00.158 __ ____ _ _ __ _ __ _ _ __ __ _
2020-04-19 23:33:00.158 \ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
2020-04-19 23:33:00.159 \ V V / (_| | | | | | | | | | | (_| |
2020-04-19 23:33:00.160 \_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
2020-04-19 23:33:00.160 __/ |
2020-04-19 23:33:00.161 |___/
2020-04-19 23:33:00.161
2020-04-19 23:33:00.162
2020-04-19 23:33:00.163 23:33:00: WARNING: User specified --num_sectors=1 but file only has 1 sectors. **Ignoring --num_sectors
2020-04-19 23:33:00.163
2020-04-19 23:33:00.164
2020-04-19 23:33:00.164 23:33:00: INFO: User wants to talk to port '\\.\COM12'
2020-04-19 23:33:00.165 23:33:00: INFO: Took 0.01500000 seconds to open port
2020-04-19 23:33:00.166 23:33:00: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
2020-04-19 23:33:00.167 23:33:00: INFO: If you don't want this, use --dontsorttags
2020-04-19 23:33:00.167
2020-04-19 23:33:00.168 23:33:00: INFO: Looking for file 'fh_gpt_header_0'
2020-04-19 23:33:00.171
2020-04-19 23:33:00.172
2020-04-19 23:33:00.172 (_)
2020-04-19 23:33:00.173 __ ____ _ _ __ _ __ _ _ __ __ _
2020-04-19 23:33:00.174 \ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
2020-04-19 23:33:00.174 \ V V / (_| | | | | | | | | | | (_| |
2020-04-19 23:33:00.175 \_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
2020-04-19 23:33:00.176 __/ |
2020-04-19 23:33:00.177 |___/
2020-04-19 23:33:00.178
2020-04-19 23:33:00.179
2020-04-19 23:33:00.179 23:33:00: WARNING: Couldn't find the file 'fh_gpt_header_0', returning NULL
2020-04-19 23:33:00.180 23:33:00: INFO: Sending <configure>
2020-04-19 23:33:00.181
2020-04-19 23:33:00.181 23:33:00: INFO: TARGET SAID: 'INFO: Binary build date: Dec 27 2019 @ 18:17:54'
2020-04-19 23:33:00.182
2020-04-19 23:33:00.182 23:33:00: INFO: TARGET SAID: 'INFO: Binary build date: Dec 27 2019 @ 18:17:54
2020-04-19 23:33:00.183 '
2020-04-19 23:33:00.184
2020-04-19 23:33:00.184 23:33:00: INFO: TARGET SAID: 'INFO: Chip serial num: 2650911984 (0x9e01b4f0)'
2020-04-19 23:33:00.185
2020-04-19 23:33:00.186 23:33:00: INFO: TARGET SAID: 'INFO: Supported Functions (14):'
2020-04-19 23:33:00.187
2020-04-19 23:33:00.188 23:33:00: INFO: TARGET SAID: 'INFO: program'
2020-04-19 23:33:00.188
2020-04-19 23:33:00.189 23:33:00: INFO: TARGET SAID: 'INFO: read'
2020-04-19 23:33:00.190
2020-04-19 23:33:00.190 23:33:00: INFO: TARGET SAID: 'INFO: nop'
2020-04-19 23:33:00.191
2020-04-19 23:33:00.191 23:33:00: INFO: TARGET SAID: 'INFO: patch'
2020-04-19 23:33:00.192
2020-04-19 23:33:00.192 23:33:00: INFO: TARGET SAID: 'INFO: configure'
2020-04-19 23:33:00.193
2020-04-19 23:33:00.194 23:33:00: INFO: TARGET SAID: 'INFO: setbootablestoragedrive'
2020-04-19 23:33:00.194
2020-04-19 23:33:00.195 23:33:00: INFO: TARGET SAID: 'INFO: erase'
2020-04-19 23:33:00.196
2020-04-19 23:33:00.196 23:33:00: INFO: TARGET SAID: 'INFO: power'
2020-04-19 23:33:00.197
2020-04-19 23:33:00.198 23:33:00: INFO: TARGET SAID: 'INFO: firmwarewrite'
2020-04-19 23:33:00.198
2020-04-19 23:33:00.199 23:33:00: INFO: TARGET SAID: 'INFO: getstorageinfo'
2020-04-19 23:33:00.199
2020-04-19 23:33:00.200 23:33:00: INFO: TARGET SAID: 'INFO: benchmark'
2020-04-19 23:33:00.201
2020-04-19 23:33:00.201 23:33:00: INFO: TARGET SAID: 'INFO: emmc'
2020-04-19 23:33:00.202
2020-04-19 23:33:00.202 23:33:00: INFO: TARGET SAID: 'INFO: ufs'
2020-04-19 23:33:00.203
2020-04-19 23:33:00.203 23:33:00: INFO: TARGET SAID: 'INFO: fixgpt'
2020-04-19 23:33:00.204
2020-04-19 23:33:00.205 23:33:00: INFO: TARGET SAID: 'INFO: End of supported functions 14'
2020-04-19 23:33:00.205
2020-04-19 23:33:00.207 23:33:00: INFO: TARGET SAID: 'ERROR: Only nop and sig tag can be recevied before authentication.'
2020-04-19 23:33:00.208 23:33:00: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
2020-04-19 23:33:00.210 23:33:00: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
2020-04-19 23:33:00.211 23:33:00: INFO: Something failed. The target rejected your <configure>. Please inspect log for more information
2020-04-19 23:33:00.211
2020-04-19 23:33:00.212 Writing log to 'C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12\port_trace.txt', might take a minute
2020-04-19 23:33:00.213
2020-04-19 23:33:00.213
2020-04-19 23:33:00.214 Log is 'C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12\port_trace.txt'
2020-04-19 23:33:00.215
2020-04-19 23:33:00.215 Download Fail:FireHose Fail:FHLoader Fail:FHLoader Failrocess fail
2020-04-19 23:33:00.225 Finish Get GPT
the other Log is attached here.
View attachment port_trace.txt

Excuse me, do you happen to have any official documentation on EDL?
Sorry for the slight offtopic.

Phone stuck in EDL Mode
Hello hikari, my device Nokia 4.2 (TA-1152) is stuck in EDL MODE after dumping the boot image file.
Can you please help me to exit from EDL mode?

Hi! even with another firehose, Crosscall Core-X3 won't accept entering Sahara mode. wrong 'pkhash'.
Recovery show HS8917QC, modem show 8937. I tried many of each without success. I don't know which one is relevant.
[ro.product.device]: [HS8917QC]
[ro.hmct.modem.version]: [MSM8937.LA.3.0.1-00490-STD.PROD-1]
[ro.fota.oem]: [hisense8917_8.1]
[ro.fota.platform]: [MSM8917_8.1]
[ro.bootimage.build.fingerprint]: [CROSSCALL/L750/HS8917QC:8.1.0....]
[gsm.version.baseband]: [MPSS.JO.3.0-00464-8937_GENNS_PACK-1]
[gsm.version.baseband1]: [MPSS.JO.3.0-00464-8937_GENNS_PACK-1]
fastboot getvar all : https://pastebin.com/pmPDpeJ8
Of course no firehose neither full image is available for this exotic device.
Bless you.

Thank you for providing the instructions!
I'd like to extract LeEco Le Max 2 (X820) but QFIL won't bring me the Partition Table.
Device recognized as "Qualcomm HS-USB QDLoader 9008 (COM12)" in Device Manager.
QFIL tells me 10:52:37: ERROR: function: sahara_rx_data:276 Unable to read packet header. Only read 0 bytes.
(Log attached.)
I used "prog_emmc_firehose_8996_ddr.elf" because I didn't find a firehose for X820. May this error be caused by a wrong firehose file? If yes, is it safe to have a try with one of the firmware image files without bricking the device or destroying data?
Length Name
------ ----
16777216 adspso.bin
405504 BTFM.bin
201304 cmnlib.mbn
256008 cmnlib64.mbn
1048576 ddr.mbn
39976 devcfg.mbn
296 devinfo.bin
793040 emmc_appsboot.mbn
264120 hyp.mbn
226008 keymaster.mbn
85004288 NON-HLOS.bin
42728 pmic.elf
229540 rpm.mbn
1634304 tz.mbn
1836136 xbl.elf
Or is it more likely that this model just doesn't respond?

Anyone ever tried this on an ROG phone 2?

Step 3: Open QFIL, load Firehose file
Hello everyone. I have nokia 1.4 TA-1322. I have downloaded several firmwares from the different websites but the emmc filefouse prog_emmc_firehose *** ddr.mbn and Rawprogram .xml files missing in all of them.
Do someone know where can I fount the emmc Firehose and Rawprogram .xml files?

hikari_calyx said:
This is the partition table of your phone. Please take note on the Start LBA and LBA number of the last partition.
Take HP Elite X3 partition table for example, the last partition is "Data", it's Start LBA and LBA number are 0x01E20000 and 0x0565BFDF. Add both of them will get the total sector numbers of whole eMMC storage - in this case, 0x0747BFDF, or 122,142,687 sectors. Multiple the sector numbers with 512 will get the total bytes of the eMMC storage, in this case, the capacity of eMMC storage is 62,537,055,744‬ bytes.
Click to expand...
Click to collapse
Hello, my partitions on my phone are wildly different compared to these. The userdata partition says it's only about 3,933,729,792 bytes. It's a 32GB phone, any reasons why it's so tiny?

Thanks for taking time to write all this out and help out a lot of people. Everything made sense until I got to
"it's Start LBA and LBA number are 0x01E20000 and 0x0565BFDF. Add both of them will get the total sector numbers of whole eMMC storage - in this case, 0x0747BFDF, or 122,142,687 sectors"
I don't think this is common knowledge. Could you please explain or just point me in the right direction to understand how adding 0x01E20000 and 0x0565BFDF resulted in 0x0747BFDF, and how we translate that string of characters into 122,142,687?
Thank you!

Hello everyone. I have a bricked Asus Zenfone 8 and I'm trying to recover userdata partitiion from it using 9008 mode. I have correct Firehose file and everything should work fine. I've easily recovered data from system partition using this manual, but I have problem with userdata. This partition is huge, around 230 GB, and phone just disconnects from PC in the middle of the process. First time it downloaded 98GB, second time - 60GB, so I don't think this is because of broken flash memory or smth. What can be a reason of this problem and how to solve that? Thanks for any reply!

Cirrus9 said:
Thanks for taking time to write all this out and help out a lot of people. Everything made sense until I got to
"it's Start LBA and LBA number are 0x01E20000 and 0x0565BFDF. Add both of them will get the total sector numbers of whole eMMC storage - in this case, 0x0747BFDF, or 122,142,687 sectors"
I don't think this is common knowledge. Could you please explain or just point me in the right direction to understand how adding 0x01E20000 and 0x0565BFDF resulted in 0x0747BFDF, and how we translate that string of characters into 122,142,687?
Thank you!
Click to expand...
Click to collapse
Hi. This string of characters is hexadecimal numeral system. You can use standart Windows calculator in programmer mode to convert these numbers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thank you! Learned something new today!

Hi! This guide is great. I have an issue with the firehose file where I found the right firehose file from my device using firehose finder on GitHub. However, that file is in .bin format instead of .elf. How can I convert it, and is that safe?

kjullian19 said:
However, that file is in .bin format instead of .elf. How can I convert it, and is that safe?
Click to expand...
Click to collapse
Firehose loaders are technically ELF 32 or 64 bit files but may be named elf, bin, img, mbn, whatever.
Use a hex editor and look at the start of the file.
It should be 7f 45 4c 46
Or use my elfview.exe (in the sig) to check it out.
Or use my qcomview.exe (in the sig) to check it out.
Code:
C:\>elfview /p motog.bin
# Type Flags Size Offset Address
-- ------- ----- ------- ------ --------
0 null 7 1016 000000 00000000
1 null 2.2 7384 001000 4602c000
2 load RWZ 0 06b4b0 0c100000
3 load RX 7772 0549f0 0c119000
4 load RWZ 0 056850 0c11c000
5 load RWZ 0 06b4b0 0c11e000
6 load RWZ 0 0549f0 0c219000
7 load RX 301376 003000 0c225000
8 load RWZ 0 04c940 0c276c00
9 load RW 32932 04c940 0c279c00
10 load RWZ 0 0549f0 0c286c00
11 load RWX 85080 056850 0c29b000
12 load 1RWX 84 06b4b0 0c2c9000
13 load 1RWX 29168 06b504 0c2c9054
14 load 1RWX 1496 0726f4 0c2d0244
15 load 5RX 139264 072ccc 0c350000
16 load RWZ 0 0549f0 45e11000
C:\>qcomview /h motog.bin
64 bit ELF, Version 6, SHA384
0 00000000 000003f8 a3836cd6c3e2dbed 5dd00c97349c8598 92a5051c08ae65d4 171ba1ece407a7b2 1cdf27a97ff437c7 0488bb944956fbc2 Ok
1 00001000 00001cd8
2 0006b4b0 00000000
3 000549f0 00001e5c 3972d9e5346b52cc e71c31a437500b8f 57f2fc8124e97cd5 b2f70a4829e98196 03d89d4b946261e2 9b2a58949b92b7dc Ok
4 00056850 00000000
5 0006b4b0 00000000
6 000549f0 00000000
7 00003000 00049940 503b424c75f6d657 e4363c830deeebee afe0ac82ce04dfec e8ac03fb47b129a3 fc221acc0d515b22 ed17d86b0f6b585c Ok
8 0004c940 00000000
9 0004c940 000080a4 2f7aec3605fbce70 ec0c83a703435845 e969988f390787d7 aa8d0a13a6d9e06f ee2af4e9b86b8a75 fc81fbe1017d1c64 Ok
10 000549f0 00000000
11 00056850 00014c58 fec3a6b9f6d71a18 aadd3f722fc73bea d3197c24c397d55d 4f3d4a9c25661db1 152c60664fcbe4a6 c2441120afc4b3c9 Ok
12 0006b4b0 00000054 db139c6f70d88269 a61cb1a7be2ce363 55faf1ff1c3b9c3d 27cd8d65bef7f710 9bc83c6255ea8104 6d7ac582cc778f15 Ok
13 0006b504 000071f0 a27a7dc0040a1bfa 8e24e4a42bead90e ae10a91c37d19105 bce9da69383004ea c933b87ac4a88653 ccbb4a6b1407d15d Ok
14 000726f4 000005d8 8dcaae787361a3c4 3bad6d344641d061 35170b5a30607e20 a30cd23884bbc0b0 790681aa36a1fe60 98501a103b62088a Ok
15 00072ccc 00022000 1f939df47e7fae80 2c127e10474ff9e6 2faecd5fab873bf8 928cab0a5ef28261 5d4b19cc57cca817 37fa9fad42971c40 Ok
16 000549f0 00000000

Thanks Renate. I'm new to this stuff, so you might have to ELI5, I'm not seeing 7f 45 4c 46 in your log.
Ultimately, I need to learn how to convert the binary file into a compatible .elf file. Will either elfview or qcomview do that?
Thanks again and sorry for the dumb questions

Flashed Note 7 Pro with Lavender rom

Okay I am new to the MIUI phones and after unlocking my device; I tried flashing TWRP (every one official, unofficial, orange, peters) with the Violet version. Nothing worked. I found a forum page stating that we had to format the userdata. I tried but TWRP still would get stuck in a bootloop to the fastboot page.
I tried downloading what I thought was the Violet fastboot rom but accidentally downloaded and flashed the lavender rom instead. I flashed it and it started up. I proceded to try installing TWRP again with the same results. I tried installing the Lavender version of TWRP and it worked.
I still have the 128 GB storage space and the camera still has the 48 MP option. I am in the process of downloading the Violet fastboot rom as I type this up. I am surprised that the Lavender version installed and booted up. I will be erasing the phone and fastbooting the Violet version after it completes.
I have not done benchmarks to see if they are different. Does the Lavender version of the rom run different than the Violet version? Is the Violet version supposed to be faster?

Both are made for different chipsets. Never ever do this blunder again.

Yeah that was a major screw up. Device is bricked. Can't flash with MIFLASH anymore. Phone is in edl mode but I am getting errors trying to flash the phone back to normal. I will try again tomorrow and post the log.

I have tried researching how to get the Note 7 Pro out of edl mode but I keep getting errors when I try to flash the phone. Both with the MiFlash tool and the QFIL tool I am getting errors. I have tried renaming and moving the main Violet folder. Moving the ports and trying different cables. Resetting the phone and holding all three buttons, flashing as soon as the QFIL sees the phone in the port. I also tried using the lavender flashboot image again just to see if it would work. I tried using an older version of the QFIL app but I am still getting an error.
QFIL log:
2019-12-22 10:01:45.194 Programmer Path:C:\Users\Christopher\Desktop\violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in\images\prog_emmc_firehose_Sm6150_ddr.elf
2019-12-22 10:01:45.195 Image Search Path: C:\Users\Christopher\Desktop\violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in\images
2019-12-22 10:01:51.945 Image Search Path: C:\Users\Christopher\Desktop\violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in\images
2019-12-22 10:01:51.950 RAWPROGRAM file path: C:\Users\Christopher\Desktop\violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in\images\rawprogram0.xml
2019-12-22 10:01:51.951 PATCH file path:C:\Users\Christopher\Desktop\violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in\images\patch0.xml
2019-12-22 10:01:54.345 Start Download
2019-12-22 10:01:54.354 Program Path:C:\Users\Christopher\Desktop\violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in\images\prog_emmc_firehose_Sm6150_ddr.elf
2019-12-22 10:01:54.366 ***** Working Folder:C:\Users\Christopher\AppData\Roaming\Qualcomm\QFIL\COMPORT_115
2019-12-22 10:01:54.435 Binary build date: Nov 21 2017 @ 02:53:37
2019-12-22 10:01:54.438 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Christopher\AppData\Roaming\Qualcomm\QFIL\COMPORT_115
2019-12-22 10:01:54.440 Sahara mappings:
2019-12-22 10:01:54.441 2: amss.mbn
2019-12-22 10:01:54.442 6: apps.mbn
2019-12-22 10:01:54.442 8: dsp1.mbn
2019-12-22 10:01:54.443 10: dbl.mbn
2019-12-22 10:01:54.444 11: osbl.mbn
2019-12-22 10:01:54.444 12: dsp2.mbn
2019-12-22 10:01:54.445 16: efs1.mbn
2019-12-22 10:01:54.445 17: efs2.mbn
2019-12-22 10:01:54.446 20: efs3.mbn
2019-12-22 10:01:54.447 21: sbl1.mbn
2019-12-22 10:01:54.447 22: sbl2.mbn
2019-12-22 10:01:54.448 23: rpm.mbn
2019-12-22 10:01:54.449 25: tz.mbn
2019-12-22 10:01:54.449 28: dsp3.mbn
2019-12-22 10:01:54.450 29: acdb.mbn
2019-12-22 10:01:54.450 30: wdt.mbn
2019-12-22 10:01:54.451 31: mba.mbn
2019-12-22 10:01:54.452 13: C:\Users\Christopher\Desktop\violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in\images\prog_emmc_firehose_Sm6150_ddr.elf
2019-12-22 10:01:54.453
2019-12-22 10:01:54.453 10:01:54: Requested ID 13, file: "C:\Users\Christopher\Desktop\violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in\images\prog_emmc_firehose_Sm6150_ddr.elf"
2019-12-22 10:01:54.454
2019-12-22 10:01:54.455 10:01:54: ERROR: function: is_ack_successful:1169 Invalid status field 40
2019-12-22 10:01:54.456
2019-12-22 10:01:54.456 10:01:54: ERROR: function: sahara_start:895 Exiting abruptly
2019-12-22 10:01:54.457
2019-12-22 10:01:54.457 10:01:54: ERROR: function: sahara_main:924 Sahara protocol error
2019-12-22 10:01:54.458
2019-12-22 10:01:54.459 10:01:54: ERROR: function: main:303 Uploading Image using Sahara protocol failed
2019-12-22 10:01:54.460
2019-12-22 10:01:54.460
2019-12-22 10:01:54.461 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2019-12-22 10:01:54.462 Finish Download
MiFlash Log:
[11:35:55 AM COM19]:MiFlash 2018.11.15.0
[11:35:55 AM COM19]:factory:
[11:35:55 AM COM19]:factory env
[11:35:55 AM COM19]:flash in thread name:COM19,id:13
[11:35:55 AM COM19]:sw in images
[11:35:55 AM COM19]:flash in thread name:COM19,id:13
[11:35:55 AM COM19]:[COM19]:start flash.
[11:35:55 AM COM19]:received hello packet
[11:35:55 AM COM19]:download programmer C:\violet\images\prog_emmc_firehose_Sm6150_ddr.elf
[11:35:55 AM COM19]:sahara read 64b data:imgID 13,offset 0,length 64
[11:35:55 AM COM19]:sahara read 64b data:imgID 13,offset 64,length 952
[11:35:55 AM COM19]:sahara read end error with status:40
[11:35:55 AM COM19]:sahara read end imgID:13 status:40
[11:35:55 AM COM19]:Send done packet
[11:35:55 AM COM19]:System.Exception: programmer transfer error 4
at XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer()
at XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash() at XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer()
at XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash()
[11:35:55 AM COM19]:no provision exit:COM19
[11:35:56 AM COM19]:flashSuccess False
[11:35:56 AM COM19]:isFactory True CheckCPUID False
[11:35:56 AM COM19]:before:flashSuccess is False set IsUpdate:True set IsDone True
[11:35:56 AM COM19]:after:flashSuccess is False set IsUpdate:false set IsDone true
QFIL 2.0.0.0 log:
Validating Application Configuration
Load APP Configuration
COM:19
SEARCHPATH:C:\violet\images
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:emmc
PLATFORM:8x26
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
METABUILD:
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
Load ARG Configuration
Process Index:0
Validating Download Configuration
Image Search Path: C:\violet\images
RAWPROGRAM file path: C:\violet\images\rawprogram0.xml
PATCH file path:C:\violet\images\patch0.xml
Invalid Device Type emmc, Ignored
Programmer Path:C:\violet\images\prog_emmc_firehose_Sm6150_ddr.elf
Image Search Path: C:\violet\images
RAWPROGRAM file path: C:\violet\images\rawprogram0.xml
PATCH file path:C:\violet\images\patch0.xml
Start Download
Program Path:C:\violet\images\prog_emmc_firehose_Sm6150_ddr.elf
COM Port number:19
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Download Fail:Unable to download Flash Programmer using Sahara Protocol
Download Fail:Sahara FailSahara Fail
Finish Download
Start Download
Program Path:C:\violet\images\prog_emmc_firehose_Sm6150_ddr.elf
COM Port number:19
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:Unable to download Flash Programmer using Sahara Protocol
Download Fail:Sahara FailSahara Fail
Finish Download
Start Download
Program Path:C:\violet\images\prog_emmc_firehose_Sm6150_ddr.elf
COM Port number:19
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:Unable to download Flash Programmer using Sahara Protocol
Download Fail:Sahara FailSahara Fail
Finish Download
Start Download
Program Path:C:\violet\images\prog_emmc_firehose_Sm6150_ddr.elf
COM Port number:19
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:Unable to download Flash Programmer using Sahara Protocol
Download Fail:Sahara FailSahara Fail
Finish Download

Go to service center and tell them, that device is not booting. They ll fix it and give back.

cealaska said:
I have tried researching how to get the Note 7 Pro out of edl mode but I keep getting errors when I try to flash the phone. Both with the MiFlash tool and the QFIL tool I am getting errors. I have tried renaming and moving the main Violet folder. Moving the ports and trying different cables. Resetting the phone and holding all three buttons, flashing as soon as the QFIL sees the phone in the port. I also tried using the lavender flashboot image again just to see if it would work. I tried using an older version of the QFIL app but I am still getting an error.
QFIL log:
2019-12-22 10:01:45.194 Programmer Path:C:\Users\Christopher\Desktop\violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in\images\prog_emmc_firehose_Sm6150_ddr.elf
2019-12-22 10:01:45.195 Image Search Path: C:\Users\Christopher\Desktop\violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in\images
2019-12-22 10:01:51.945 Image Search Path: C:\Users\Christopher\Desktop\violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in\images
2019-12-22 10:01:51.950 RAWPROGRAM file path: C:\Users\Christopher\Desktop\violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in\images\rawprogram0.xml
2019-12-22 10:01:51.951 PATCH file path:C:\Users\Christopher\Desktop\violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in\images\patch0.xml
2019-12-22 10:01:54.345 Start Download
2019-12-22 10:01:54.354 Program Path:C:\Users\Christopher\Desktop\violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in\images\prog_emmc_firehose_Sm6150_ddr.elf
2019-12-22 10:01:54.366 ***** Working Folder:C:\Users\Christopher\AppData\Roaming\Qualcomm\QFIL\COMPORT_115
2019-12-22 10:01:54.435 Binary build date: Nov 21 2017 @ 02:53:37
2019-12-22 10:01:54.438 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Christopher\AppData\Roaming\Qualcomm\QFIL\COMPORT_115
2019-12-22 10:01:54.440 Sahara mappings:
2019-12-22 10:01:54.441 2: amss.mbn
2019-12-22 10:01:54.442 6: apps.mbn
2019-12-22 10:01:54.442 8: dsp1.mbn
2019-12-22 10:01:54.443 10: dbl.mbn
2019-12-22 10:01:54.444 11: osbl.mbn
2019-12-22 10:01:54.444 12: dsp2.mbn
2019-12-22 10:01:54.445 16: efs1.mbn
2019-12-22 10:01:54.445 17: efs2.mbn
2019-12-22 10:01:54.446 20: efs3.mbn
2019-12-22 10:01:54.447 21: sbl1.mbn
2019-12-22 10:01:54.447 22: sbl2.mbn
2019-12-22 10:01:54.448 23: rpm.mbn
2019-12-22 10:01:54.449 25: tz.mbn
2019-12-22 10:01:54.449 28: dsp3.mbn
2019-12-22 10:01:54.450 29: acdb.mbn
2019-12-22 10:01:54.450 30: wdt.mbn
2019-12-22 10:01:54.451 31: mba.mbn
2019-12-22 10:01:54.452 13: C:\Users\Christopher\Desktop\violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in\images\prog_emmc_firehose_Sm6150_ddr.elf
2019-12-22 10:01:54.453
2019-12-22 10:01:54.453 10:01:54: Requested ID 13, file: "C:\Users\Christopher\Desktop\violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in\images\prog_emmc_firehose_Sm6150_ddr.elf"
2019-12-22 10:01:54.454
2019-12-22 10:01:54.455 10:01:54: ERROR: function: is_ack_successful:1169 Invalid status field 40
2019-12-22 10:01:54.456
2019-12-22 10:01:54.456 10:01:54: ERROR: function: sahara_start:895 Exiting abruptly
2019-12-22 10:01:54.457
2019-12-22 10:01:54.457 10:01:54: ERROR: function: sahara_main:924 Sahara protocol error
2019-12-22 10:01:54.458
2019-12-22 10:01:54.459 10:01:54: ERROR: function: main:303 Uploading Image using Sahara protocol failed
2019-12-22 10:01:54.460
2019-12-22 10:01:54.460
2019-12-22 10:01:54.461 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2019-12-22 10:01:54.462 Finish Download
MiFlash Log:
[11:35:55 AM COM19]:MiFlash 2018.11.15.0
[11:35:55 AM COM19]
[11:35:55 AM COM19]:factory env
[11:35:55 AM COM19]:flash in thread name:COM19,id:13
[11:35:55 AM COM19]:sw in images
[11:35:55 AM COM19]:flash in thread name:COM19,id:13
[11:35:55 AM COM19]:[COM19]:start flash.
[11:35:55 AM COM19]:received hello packet
[11:35:55 AM COM19]:download programmer C:\violet\images\prog_emmc_firehose_Sm6150_ddr.elf
[11:35:55 AM COM19]:sahara read 64b data:imgID 13,offset 0,length 64
[11:35:55 AM COM19]:sahara read 64b data:imgID 13,offset 64,length 952
[11:35:55 AM COM19]:sahara read end error with status:40
[11:35:55 AM COM19]:sahara read end imgID:13 status:40
[11:35:55 AM COM19]:Send done packet
[11:35:55 AM COM19]:System.Exception: programmer transfer error 4
at XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer()
at XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash() at XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer()
at XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash()
[11:35:55 AM COM19]:no provision exit:COM19
[11:35:56 AM COM19]:flashSuccess False
[11:35:56 AM COM19]:isFactory True CheckCPUID False
[11:35:56 AM COM19]:before:flashSuccess is False set IsUpdate:True set IsDone True
[11:35:56 AM COM19]:after:flashSuccess is False set IsUpdate:false set IsDone true
QFIL 2.0.0.0 log:
Validating Application Configuration
Load APP Configuration
COM:19
SEARCHPATH:C:\violet\images
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:emmc
PLATFORM:8x26
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
METABUILD:
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
Load ARG Configuration
Process Index:0
Validating Download Configuration
Image Search Path: C:\violet\images
RAWPROGRAM file path: C:\violet\images\rawprogram0.xml
PATCH file path:C:\violet\images\patch0.xml
Invalid Device Type emmc, Ignored
Programmer Path:C:\violet\images\prog_emmc_firehose_Sm6150_ddr.elf
Image Search Path: C:\violet\images
RAWPROGRAM file path: C:\violet\images\rawprogram0.xml
PATCH file path:C:\violet\images\patch0.xml
Start Download
Program Path:C:\violet\images\prog_emmc_firehose_Sm6150_ddr.elf
COM Port number:19
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Download Fail:Unable to download Flash Programmer using Sahara Protocol
Download Fail:Sahara FailSahara Fail
Finish Download
Start Download
Program Path:C:\violet\images\prog_emmc_firehose_Sm6150_ddr.elf
COM Port number:19
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:Unable to download Flash Programmer using Sahara Protocol
Download Fail:Sahara FailSahara Fail
Finish Download
Start Download
Program Path:C:\violet\images\prog_emmc_firehose_Sm6150_ddr.elf
COM Port number:19
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:Unable to download Flash Programmer using Sahara Protocol
Download Fail:Sahara FailSahara Fail
Finish Download
Start Download
Program Path:C:\violet\images\prog_emmc_firehose_Sm6150_ddr.elf
COM Port number:19
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:Unable to download Flash Programmer using Sahara Protocol
Download Fail:Sahara FailSahara Fail
Finish Download
Click to expand...
Click to collapse
how'd u fix it? MI store?

Xiaomi MiFlash Tool 2023.4.14.0 No Auth EDL Flashing

Xiaomi MiFlash Tool 2023.4.14.0 No Auth EDL Flashing Modified by Zesuga​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​​Features:​
Free auth bypass (EDL Mobile)
No need credit balance or activation
Free unlock EDL Auth device and flash
Only need to boot the device in EDL mode
What's new​Added EDL Auth-Supported Devices​
- Redmi Note 9 4G / Redmi 9T (lime)
- Redmi Note 8 (ginkgo)
- Redmi Note 8T (willow)
- Redmi Note 5 Pro (whyred)
- Redmi Note 6 Pro (tulip)
- Redmi Note 7 Pro (violet)
- Redmi Note 7 (lavendar)
- Mi 8 (dipper)
- Mi 8 Lite (platina)
- Mi 8 SE(srius)
- Mi 8 EE(equuleus)
- Mi 8 Pro/UD(ursa)
- Mi 9 SE (grus)
- Mi CC9 (pyxis)
- Mi CC9E (laurus)
- Mi 6X (wayne)
- Mi Max 3 (nitrogen)
- Mi 5X (tiffany)
- Mi A2 Lite (daisy)
- Redmi 6 Pro (sakura)
- Redmi 7A (pine)
- Redmi 8 (olive)
- Redmi 8A (olivelite)
- Redmi 8 Pro/DUAL (olivewood)
- Redmi S2 (ysl)
I have successully tested this tool to flash Redmi 8A, Redmi 8A Dual and Redmi 7A, Redmi Note 7, Poco F1 and Redmi 9T.
You can read more about it in the below post as a reference.
[GUIDE] No Auth Xiaomi Redmi 8A, Redmi 8A Dual and Redmi 7A EDL Flashing using Mi Flash Tool.
[GUIDE] Xiaomi Redmi 8A EDL Flashing using Mi Flash Tool. (Also works for Redmi 7A). This tutorial has been successfully tested with Redmi 8A, Redmi 8A Dual and Redmi 7A all featuring a Qualcomm SDM439 Chipset. WARNING: DO NOT SHORT THE TEST...
forum.xda-developers.com
Also you can check No auth collection for your phone if available here
[No auth collection] Xiaomi No Auth Firehose Files for Qualcomm based phones.
What is this file? As we all know that Xiaomi has blocked offline flashing with authentication to flash their device. This files will ultimately help you to fix the Mi Account Authorization issue and hence unbrick your Xiaomi device via EDL mode...
forum.xda-developers.com
Please test on your Qualcomm based Xiaomi phone and let me know about it.

Redmi k20 pro stuck in edl how can i flash wihout authorised account

mirasif said:
Redmi k20 pro stuck in edl how can i flash wihout authorised account
Click to expand...
Click to collapse
Please try using mi flash that I have uploaded already in this post or
or else I have a paid tool (screenshot below) but I will help you for free.

mvikrant97 said:
Please try using mi flash that I have uploaded already in this post or
or else I have a paid tool (screenshot below) but I will help you for free.
View attachment 5919599
Click to expand...
Click to collapse
How can i contact u

mvikrant97 said:
Please try using mi flash that I have uploaded already in this post or
or else I have a paid tool (screenshot below) but I will help you for free.
View attachment 5919599
Click to expand...
Click to collapse
can you help me? my RedMi K20 Pro(raphael) stuck on "cannot read hello packet". Please help me.. m

Can this work on poco f3? // If not can you add support for poco f3 on next update?

**C007** said:
Can this work on poco f3? // If not can you add support for poco f3 on next update?
Click to expand...
Click to collapse
Please try it for your phone.
I'm not the developer of the software.
I just shared what I found on the internet.

mvikrant97 said:
Xiaomi MiFlash Tool 2023.4.14.0 No Auth EDL Flashing Modified by Zesuga​View attachment 5918703​​​Features:​
Free auth bypass (EDL Mobile)
No need credit balance or activation
Free unlock EDL Auth device and flash
Only need to boot the device in EDL mode
What's new​Added EDL Auth-Supported Devices​
- Redmi Note 9 4G / Redmi 9T (lime)
- Redmi Note 8 (ginkgo)
- Redmi Note 8T (willow)
- Redmi Note 5 Pro (whyred)
- Redmi Note 6 Pro (tulip)
- Redmi Note 7 Pro (violet)
- Redmi Note 7 (lavendar)
- Mi 8 (dipper)
- Mi 8 Lite (platina)
- Mi 8 SE(srius)
- Mi 8 EE(equuleus)
- Mi 8 Pro/UD(ursa)
- Mi 9 SE (grus)
- Mi CC9 (pyxis)
- Mi CC9E (laurus)
- Mi 6X (wayne)
- Mi Max 3 (nitrogen)
- Mi 5X (tiffany)
- Mi A2 Lite (daisy)
- Redmi 6 Pro (sakura)
- Redmi 7A (pine)
- Redmi 8 (olive)
- Redmi 8A (olivelite)
- Redmi 8 Pro/DUAL (olivewood)
- Redmi S2 (ysl)
I have successully tested this tool to flash Redmi 8A, Redmi 8A Dual and Redmi 7A, Redmi Note 7, Poco F1 and Redmi 9T.
You can read more about it in the below post as a reference.
[GUIDE] No Auth Xiaomi Redmi 8A, Redmi 8A Dual and Redmi 7A EDL Flashing using Mi Flash Tool.
[GUIDE] Xiaomi Redmi 8A EDL Flashing using Mi Flash Tool. (Also works for Redmi 7A). This tutorial has been successfully tested with Redmi 8A, Redmi 8A Dual and Redmi 7A all featuring a Qualcomm SDM439 Chipset. WARNING: DO NOT SHORT THE TEST...
forum.xda-developers.com
Also you can check No auth collection for your phone if available here
[No auth collection] Xiaomi No Auth Firehose Files for Qualcomm based phones.
What is this file? As we all know that Xiaomi has blocked offline flashing with authentication to flash their device. This files will ultimately help you to fix the Mi Account Authorization issue and hence unbrick your Xiaomi device via EDL mode...
forum.xda-developers.com
Please test on your Qualcomm based Xiaomi phone and let me know about it.
Click to expand...
Click to collapse
i need edl bypass for poco x3 pro

Can u revive poco x3 nfc (surya) stuck on edl mode ?

hamawolf98k said:
i need edl bypass for poco x3 pro
Click to expand...
Click to collapse
It does not support your phone.

Ojha Baba said:
Can u revive poco x3 nfc (surya) stuck on edl mode ?
Click to expand...
Click to collapse
Yes but it will need a different tool.
This will not work.

mvikrant97 said:
Please try using mi flash that I have uploaded already in this post or
or else I have a paid tool (screenshot below) but I will help you for free.
View attachment 5919599
Click to expand...
Click to collapse
sir can you help me in my redmi note 9 pro I need authorize account to flash, youre mi flash tool didnt work hopefully you can help me

dark2133 said:
sir can you help me in my redmi note 9 pro I need authorize account to flash, youre mi flash tool didnt work hopefully you can help me
Click to expand...
Click to collapse
If your device is Curtana which has Snapdragon 720 then it can be done using paid tool only at the moment.

mvikrant97 said:
If your device is Curtana which has Snapdragon 720 then it can be done using paid tool only at the moment.
View attachment 5940667
Click to expand...
Click to collapse
Paid It

can you help with redmi note 8 im getting error on that modded miflasher as well via qfil
ERROR: sparse_open:2628 Unknown chunk type cac2

tonystark006 said:
can you help with redmi note 8 im getting error on that modded miflasher as well via qfil
ERROR: sparse_open:2628 Unknown chunk type cac2
Click to expand...
Click to collapse
Redmi Note 8 (ginkgo)
Is it this device?

mvikrant97 said:
Redmi Note 8 (ginkgo)
Is it this device?
Click to expand...
Click to collapse
yes ginkgo

2023-06-27 14:29:03.703 Image Search Path: C:\12.5\images
2023-06-27 14:29:03.703 RAWPROGRAM file path: C:\12.5\images\rawprogram0.xml
2023-06-27 14:29:03.703 RAWPROGRAM file path: C:\12.5\images\rawprogram0_xiaomi.xml
2023-06-27 14:29:03.703 PATCH file path:C:\12.5\images\patch0.xml
2023-06-27 14:29:18.218 Start Download
2023-06-27 14:29:18.223 Program Path:C:\Users\Hanzen\Desktop\prog_emmc_firehose_Redmi_Note_8.elf
2023-06-27 14:29:18.223 ***** Working Folder:C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2023-06-27 14:29:18.418 Binary build date: Apr 27 2018 @ 03:04:33
2023-06-27 14:29:18.418 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2023-06-27 14:29:18.418 Sahara mappings:
2023-06-27 14:29:18.418 2: amss.mbn
2023-06-27 14:29:18.418 6: apps.mbn
2023-06-27 14:29:18.426 8: dsp1.mbn
2023-06-27 14:29:18.426 10: dbl.mbn
2023-06-27 14:29:18.426 11: osbl.mbn
2023-06-27 14:29:18.426 12: dsp2.mbn
2023-06-27 14:29:18.426 16: efs1.mbn
2023-06-27 14:29:18.426 17: efs2.mbn
2023-06-27 14:29:18.426 20: efs3.mbn
2023-06-27 14:29:18.434 21: sbl1.mbn
2023-06-27 14:29:18.435 22: sbl2.mbn
2023-06-27 14:29:18.435 23: rpm.mbn
2023-06-27 14:29:18.435 25: tz.mbn
2023-06-27 14:29:18.435 28: dsp3.mbn
2023-06-27 14:29:18.435 29: acdb.mbn
2023-06-27 14:29:18.435 30: wdt.mbn
2023-06-27 14:29:18.435 31: mba.mbn
2023-06-27 14:29:18.435 13: C:\Users\Hanzen\Desktop\prog_emmc_firehose_Redmi_Note_8.elf
2023-06-27 14:29:18.435
2023-06-27 14:29:18.435 14:29:18: Requested ID 13, file: "C:\Users\Hanzen\Desktop\prog_emmc_firehose_Redmi_Note_8.elf"
2023-06-27 14:29:18.435
2023-06-27 14:29:18.435 14:29:18: 591740 bytes transferred in 0.109000 seconds (5.1773MBps)
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451 14:29:18: File transferred successfully
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451 14:29:18: Sahara protocol completed
2023-06-27 14:29:18.451 Sending Programmer Finished
2023-06-27 14:29:18.451 Switch To FireHose
2023-06-27 14:29:18.466 Wait for 3 seconds...
2023-06-27 14:29:21.485 Max Payload Size to Target:49152 Bytes
2023-06-27 14:29:21.485 Device Type:emmc
2023-06-27 14:29:21.485 Platform:8x26
2023-06-27 14:29:21.493 Disable Ack Raw Data Every N Packets
2023-06-27 14:29:21.493 Skip Write:False
2023-06-27 14:29:21.501 Always Validate:False
2023-06-27 14:29:21.501 Use Verbose:False
2023-06-27 14:29:21.509 ***** Working Folder:C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2023-06-27 14:29:21.728
2023-06-27 14:29:21.743 Base Version: 18.02.16.18.26
2023-06-27 14:29:21.743 Binary build date: Apr 27 2018 @ 03:04:29
2023-06-27 14:29:21.743 Incremental Build version: 18.04.27.03.04.29
2023-06-27 14:29:21.743
2023-06-27 14:29:21.743 14:29:21: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
2023-06-27 14:29:21.743 ************************************************
2023-06-27 14:29:21.743 C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM3 --sendxml=rawprogram0.xml,rawprogram0_xiaomi.xml --search_path=C:\12.5\images --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
2023-06-27 14:29:21.743 ************************************************
2023-06-27 14:29:21.743
2023-06-27 14:29:21.743 14:29:21: INFO: Current working dir (cwd): C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\
2023-06-27 14:29:21.743 14:29:21: INFO: Showing network mappings to allow debugging
2023-06-27 14:29:21.759 14:29:21: INFO:
2023-06-27 14:29:21.759
2023-06-27 14:29:21.759
2023-06-27 14:29:21.759
2023-06-27 14:29:21.759 14:29:21: INFO: Trying to store 'rawprogram0.xml' in string table
2023-06-27 14:29:21.759 14:29:21: INFO: Looking for file 'rawprogram0.xml'
2023-06-27 14:29:21.759 14:29:21: INFO: Looking for file 'metadata.img'
2023-06-27 14:29:21.759 14:29:21: INFO: Reading through sparse file 'metadata.img' and pulling out relevant header information...
2023-06-27 14:29:21.759 14:29:21: INFO: File metadata.img is a sparse file, being split up into 2 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'cust.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'cust.img' and pulling out relevant header information...
2023-06-27 14:29:21.774 14:29:21: INFO: File cust.img is a sparse file, being split up into 10 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'vendor.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'vendor.img' and pulling out relevant header information...
2023-06-27 14:29:21.774 14:29:21: INFO: File vendor.img is a sparse file, being split up into 13 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'system.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'system.img' and pulling out relevant header information...
2023-06-27 14:29:21.774 14:29:21: INFO: File system.img is a sparse file, being split up into 39 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'userdata.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'userdata.img' and pulling out relevant header information...
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790 _____
2023-06-27 14:29:21.790 | ___|
2023-06-27 14:29:21.790 | |__ _ __ _ __ ___ _ __
2023-06-27 14:29:21.790 | __| '__| '__/ _ \| '__|
2023-06-27 14:29:21.790 | |__| | | | | (_) | |
2023-06-27 14:29:21.790 \____/_| |_| \___/|_|
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790 14:29:21: {ERROR: Unknown chunk type cac2
2023-06-27 14:29:21.790 }
2023-06-27 14:29:21.790
2023-06-27 14:29:21.806 Writing log to 'C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt', might take a minute
2023-06-27 14:29:21.806
2023-06-27 14:29:21.806
2023-06-27 14:29:21.806 Log is 'C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt'
2023-06-27 14:29:21.806
2023-06-27 14:29:21.806 Download Fail:FireHose Fail:FHLoader Failrocess fail
2023-06-27 14:29:21.806 Finish Download
here is the full error message

tonystark006 said:
2023-06-27 14:29:03.703 Image Search Path: C:\12.5\images
2023-06-27 14:29:03.703 RAWPROGRAM file path: C:\12.5\images\rawprogram0.xml
2023-06-27 14:29:03.703 RAWPROGRAM file path: C:\12.5\images\rawprogram0_xiaomi.xml
2023-06-27 14:29:03.703 PATCH file path:C:\12.5\images\patch0.xml
2023-06-27 14:29:18.218 Start Download
2023-06-27 14:29:18.223 Program Path:C:\Users\Hanzen\Desktop\prog_emmc_firehose_Redmi_Note_8.elf
2023-06-27 14:29:18.223 ***** Working Folder:C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2023-06-27 14:29:18.418 Binary build date: Apr 27 2018 @ 03:04:33
2023-06-27 14:29:18.418 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2023-06-27 14:29:18.418 Sahara mappings:
2023-06-27 14:29:18.418 2: amss.mbn
2023-06-27 14:29:18.418 6: apps.mbn
2023-06-27 14:29:18.426 8: dsp1.mbn
2023-06-27 14:29:18.426 10: dbl.mbn
2023-06-27 14:29:18.426 11: osbl.mbn
2023-06-27 14:29:18.426 12: dsp2.mbn
2023-06-27 14:29:18.426 16: efs1.mbn
2023-06-27 14:29:18.426 17: efs2.mbn
2023-06-27 14:29:18.426 20: efs3.mbn
2023-06-27 14:29:18.434 21: sbl1.mbn
2023-06-27 14:29:18.435 22: sbl2.mbn
2023-06-27 14:29:18.435 23: rpm.mbn
2023-06-27 14:29:18.435 25: tz.mbn
2023-06-27 14:29:18.435 28: dsp3.mbn
2023-06-27 14:29:18.435 29: acdb.mbn
2023-06-27 14:29:18.435 30: wdt.mbn
2023-06-27 14:29:18.435 31: mba.mbn
2023-06-27 14:29:18.435 13: C:\Users\Hanzen\Desktop\prog_emmc_firehose_Redmi_Note_8.elf
2023-06-27 14:29:18.435
2023-06-27 14:29:18.435 14:29:18: Requested ID 13, file: "C:\Users\Hanzen\Desktop\prog_emmc_firehose_Redmi_Note_8.elf"
2023-06-27 14:29:18.435
2023-06-27 14:29:18.435 14:29:18: 591740 bytes transferred in 0.109000 seconds (5.1773MBps)
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451 14:29:18: File transferred successfully
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451 14:29:18: Sahara protocol completed
2023-06-27 14:29:18.451 Sending Programmer Finished
2023-06-27 14:29:18.451 Switch To FireHose
2023-06-27 14:29:18.466 Wait for 3 seconds...
2023-06-27 14:29:21.485 Max Payload Size to Target:49152 Bytes
2023-06-27 14:29:21.485 Device Type:emmc
2023-06-27 14:29:21.485 Platform:8x26
2023-06-27 14:29:21.493 Disable Ack Raw Data Every N Packets
2023-06-27 14:29:21.493 Skip Write:False
2023-06-27 14:29:21.501 Always Validate:False
2023-06-27 14:29:21.501 Use Verbose:False
2023-06-27 14:29:21.509 ***** Working Folder:C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2023-06-27 14:29:21.728
2023-06-27 14:29:21.743 Base Version: 18.02.16.18.26
2023-06-27 14:29:21.743 Binary build date: Apr 27 2018 @ 03:04:29
2023-06-27 14:29:21.743 Incremental Build version: 18.04.27.03.04.29
2023-06-27 14:29:21.743
2023-06-27 14:29:21.743 14:29:21: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
2023-06-27 14:29:21.743 ************************************************
2023-06-27 14:29:21.743 C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM3 --sendxml=rawprogram0.xml,rawprogram0_xiaomi.xml --search_path=C:\12.5\images --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
2023-06-27 14:29:21.743 ************************************************
2023-06-27 14:29:21.743
2023-06-27 14:29:21.743 14:29:21: INFO: Current working dir (cwd): C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\
2023-06-27 14:29:21.743 14:29:21: INFO: Showing network mappings to allow debugging
2023-06-27 14:29:21.759 14:29:21: INFO:
2023-06-27 14:29:21.759
2023-06-27 14:29:21.759
2023-06-27 14:29:21.759
2023-06-27 14:29:21.759 14:29:21: INFO: Trying to store 'rawprogram0.xml' in string table
2023-06-27 14:29:21.759 14:29:21: INFO: Looking for file 'rawprogram0.xml'
2023-06-27 14:29:21.759 14:29:21: INFO: Looking for file 'metadata.img'
2023-06-27 14:29:21.759 14:29:21: INFO: Reading through sparse file 'metadata.img' and pulling out relevant header information...
2023-06-27 14:29:21.759 14:29:21: INFO: File metadata.img is a sparse file, being split up into 2 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'cust.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'cust.img' and pulling out relevant header information...
2023-06-27 14:29:21.774 14:29:21: INFO: File cust.img is a sparse file, being split up into 10 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'vendor.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'vendor.img' and pulling out relevant header information...
2023-06-27 14:29:21.774 14:29:21: INFO: File vendor.img is a sparse file, being split up into 13 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'system.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'system.img' and pulling out relevant header information...
2023-06-27 14:29:21.774 14:29:21: INFO: File system.img is a sparse file, being split up into 39 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'userdata.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'userdata.img' and pulling out relevant header information...
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790 _____
2023-06-27 14:29:21.790 | ___|
2023-06-27 14:29:21.790 | |__ _ __ _ __ ___ _ __
2023-06-27 14:29:21.790 | __| '__| '__/ _ \| '__|
2023-06-27 14:29:21.790 | |__| | | | | (_) | |
2023-06-27 14:29:21.790 \____/_| |_| \___/|_|
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790 14:29:21: {ERROR: Unknown chunk type cac2
2023-06-27 14:29:21.790 }
2023-06-27 14:29:21.790
2023-06-27 14:29:21.806 Writing log to 'C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt', might take a minute
2023-06-27 14:29:21.806
2023-06-27 14:29:21.806
2023-06-27 14:29:21.806 Log is 'C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt'
2023-06-27 14:29:21.806
2023-06-27 14:29:21.806 Download Fail:FireHose Fail:FHLoader Failrocess fail
2023-06-27 14:29:21.806 Finish Download
here is the full error message
Click to expand...
Click to collapse
Extract and Replace the fh_loader with the attached file in xiaomi flash tool

If the above loader does not work please see this post below
phone stuck in edl mode please help
Happened to me while installing eu rom with mi flash.
forum.xda-developers.com