LG G4 Bricked Qualcomm HS-USB QDLoader 9008 - G4 Q&A, Help & Troubleshooting

LG G4 Bricked Qualcomm HS-USB QDLoader 9008 - G4 Q&A, Help & Troubleshooting

Hello,
I know,I know, you will say yet another topic about LG G4 and Qualcomm 9008 problem.
you have right but this problem intrigues me.
Some people proposed a solution for reviving the phone without a box by short-cutting 2 testpoint on the motherbord before connecting to the computer.
so here is what I did, unfortunately without success, but together we can find where is the problem and find a final solution for this big problem.
1- ONLY connect Smartphone USB Side like this :
{
"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"
}
2- Shortcut with tweezers the two testpoints as described here :
3-On windows 10 x64 Launch QFIL V 2.0.0.5 with Admin Rights :
4- Connect USB Computer side :
5-Choose COM PORT and all settings like this :
6-Clik Download Button
7- unsuccessful operation, this is the log file
Validating Application Configuration
Load APP Configuration
COM:-1
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
SEARCHPATH:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818
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
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818
RAWPROGRAM file path: C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml
PATCH file path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\patch0.xml
Programmer Path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
Process Index:0
Start Download
Program Path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.exe -p \\.\COM4 -s 13:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn 'Current working dir: C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL
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:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
09:28:26: Requested ID 13, file: "C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn"
09:28:26: 273568 bytes transferred in 0.360000 seconds (0.7247MBps)
09:28:26: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
09:28:26: 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
Binary build date: Sep 28 2015 @ 17:28:46
Build version: 15.09.28.17.28.46
09:28:30: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM4 --sendxml=rawprogram0.xml --search_path=C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=eMMC
************************************************
09:28:30: INFO: Current working dir (cwd): C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\
09:28:30: INFO: Showing network mappings to allow debugging
09:28:30: INFO:
09:28:30: INFO: Trying to store 'rawprogram0.xml' in string table
09:28:30: INFO: Looking for file 'rawprogram0.xml'
09:28:30: INFO: User wants to talk to port '\\.\COM4'
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
09:28:40: {ERROR: It took 10.00000000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable}
Writing log to 'C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\port_trace.txt', might take a minute
Log is 'C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
Download Fail:FireHose Fail FHLoader Failrocess fail
Finish Download
port_trace.txt
Validating Application Configuration
Load APP Configuration
COM:-1
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
SEARCHPATH:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818
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
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818
RAWPROGRAM file path: C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml
PATCH file path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\patch0.xml
Programmer Path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
Process Index:0
Start Download
Program Path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.exe -p \\.\COM4 -s 13:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn 'Current working dir: C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL
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:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
09:28:26: Requested ID 13, file: "C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn"
09:28:26: 273568 bytes transferred in 0.360000 seconds (0.7247MBps)
09:28:26: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
09:28:26: 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
Binary build date: Sep 28 2015 @ 17:28:46
Build version: 15.09.28.17.28.46
09:28:30: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM4 --sendxml=rawprogram0.xml --search_path=C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=eMMC
************************************************
09:28:30: INFO: Current working dir (cwd): C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\
09:28:30: INFO: Showing network mappings to allow debugging
09:28:30: INFO:
09:28:30: INFO: Trying to store 'rawprogram0.xml' in string table
09:28:30: INFO: Looking for file 'rawprogram0.xml'
09:28:30: INFO: User wants to talk to port '\\.\COM4'
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
09:28:40: {ERROR: It took 10.00000000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable}
Writing log to 'C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\port_trace.txt', might take a minute
Log is 'C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
Download Fail:FireHose Fail FHLoader Failrocess fail
Finish Download
09:28:30: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM4 --sendxml=rawprogram0.xml --search_path=C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=eMMC
************************************************
09:28:30: DEBUG: Binary build date: Sep 28 2015 @ 17:28:46
09:28:30: DEBUG: Build Version: 15.09.28.17.28.46
09:28:30: INFO: Current working dir (cwd): C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\
09:28:30: INFO: Showing network mappings to allow debugging
09:28:30: DEBUG: Les nouvelles connexions seront m‚moris‚es.
09:28:30: DEBUG:
09:28:30: DEBUG: La liste est vide.
09:28:30: DEBUG:
09:28:30: INFO:
09:28:30: INFO: Trying to store 'rawprogram0.xml' in string table
09:28:30: DEBUG: ==================================================================================
09:28:30: DEBUG: ==================================================================================
09:28:30: INFO: Looking for file 'rawprogram0.xml'
09:28:30: DEBUG: 1. Calling stat(C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml')
09:28:30: DEBUG: 2. Calling fopen('C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml') with AccessMode='rb'
09:28:30: DEBUG: Trying get filesize, calling fseek()
09:28:30: DEBUG: Found 'C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml' (5089 bytes)
09:28:30: DEBUG: 2. Calling fopen('C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml') with AccessMode='r'
09:28:30: DEBUG: Trying get filesize, calling fseek()
09:28:30: DEBUG: User set ZLPAWAREHOST to 1
09:28:30: INFO: User wants to talk to port '\\.\COM4'
09:28:40: DEBUG: port_fd=0xC8
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
09:28:40: {ERROR: OpenPort:5566 It took 10.00000000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable
So where is the problem ? Shortcutting the two points is supposed to open the FireHose port but i tested with twezzers, cooper cable...ect nothing seem to work
any Idea ?
thank you

PS: I have the Link to the files if you want them

Hello, ¿you can share the links?, I need the files for LG H810.
Thank you in advance.

I got the same problem with my H815T. It only allows me to flash the LS991 files, but I lose the imei
serestma said:
Hello, ¿you can share the links?, I need the files for LG H810.
Thank you in advance.
Click to expand...
Click to collapse
H810: https://mega.nz/#!55tACDZC!Ci1pjEr8_wr9Ng2SrPgj42MwxnGybo60de26w2gtimg

I bought a subscription from easy-firmware hoping that they have right emmc_firehose. They are scammers. I have a bricked LG G4 too and since now I have not found a way to unbrick it. Do not waste your time. For H815 the files are wrong and we also need nonfused emmc_firehose_programmer. Also the SD Card method is not working for me tried it with 10 different images and 4 different cards. I am investigating this issue and if I find a solution I will make a tutorial for all fellas that are in trouble.

AZstyle said:
Hello,
I know,I know, you will say yet another topic about LG G4 and Qualcomm 9008 problem.
you have right but this problem intrigues me.
Some people proposed a solution for reviving the phone without a box by short-cutting 2 testpoint on the motherbord before connecting to the computer.
so here is what I did, unfortunately without success, but together we can find where is the problem and find a final solution for this big problem.
1- ONLY connect Smartphone USB Side like this :
2- Shortcut with tweezers the two testpoints as described here :
3-On windows 10 x64 Launch QFIL V 2.0.0.5 with Admin Rights :
4- Connect USB Computer side :
5-Choose COM PORT and all settings like this :
6-Clik Download Button
7- unsuccessful operation, this is the log file
Validating Application Configuration
Load APP Configuration
COM:-1
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
SEARCHPATH:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818
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
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818
RAWPROGRAM file path: C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml
PATCH file path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\patch0.xml
Programmer Path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
Process Index:0
Start Download
Program Path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.exe -p \\.\COM4 -s 13:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn 'Current working dir: C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL
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:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
09:28:26: Requested ID 13, file: "C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn"
09:28:26: 273568 bytes transferred in 0.360000 seconds (0.7247MBps)
09:28:26: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
09:28:26: 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
Binary build date: Sep 28 2015 @ 17:28:46
Build version: 15.09.28.17.28.46
09:28:30: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM4 --sendxml=rawprogram0.xml --search_path=C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=eMMC
************************************************
09:28:30: INFO: Current working dir (cwd): C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\
09:28:30: INFO: Showing network mappings to allow debugging
09:28:30: INFO:
09:28:30: INFO: Trying to store 'rawprogram0.xml' in string table
09:28:30: INFO: Looking for file 'rawprogram0.xml'
09:28:30: INFO: User wants to talk to port '\\.\COM4'
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
09:28:40: {ERROR: It took 10.00000000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable}
Writing log to 'C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\port_trace.txt', might take a minute
Log is 'C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
Download Fail:FireHose Fail FHLoader Failrocess fail
Finish Download
port_trace.txt
Validating Application Configuration
Load APP Configuration
COM:-1
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
SEARCHPATH:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818
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
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818
RAWPROGRAM file path: C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml
PATCH file path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\patch0.xml
Programmer Path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
Process Index:0
Start Download
Program Path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.exe -p \\.\COM4 -s 13:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn 'Current working dir: C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL
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:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
09:28:26: Requested ID 13, file: "C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn"
09:28:26: 273568 bytes transferred in 0.360000 seconds (0.7247MBps)
09:28:26: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
09:28:26: 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
Binary build date: Sep 28 2015 @ 17:28:46
Build version: 15.09.28.17.28.46
09:28:30: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM4 --sendxml=rawprogram0.xml --search_path=C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=eMMC
************************************************
09:28:30: INFO: Current working dir (cwd): C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\
09:28:30: INFO: Showing network mappings to allow debugging
09:28:30: INFO:
09:28:30: INFO: Trying to store 'rawprogram0.xml' in string table
09:28:30: INFO: Looking for file 'rawprogram0.xml'
09:28:30: INFO: User wants to talk to port '\\.\COM4'
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
09:28:40: {ERROR: It took 10.00000000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable}
Writing log to 'C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\port_trace.txt', might take a minute
Log is 'C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
Download Fail:FireHose Fail FHLoader Failrocess fail
Finish Download
09:28:30: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM4 --sendxml=rawprogram0.xml --search_path=C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=eMMC
************************************************
09:28:30: DEBUG: Binary build date: Sep 28 2015 @ 17:28:46
09:28:30: DEBUG: Build Version: 15.09.28.17.28.46
09:28:30: INFO: Current working dir (cwd): C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\
09:28:30: INFO: Showing network mappings to allow debugging
09:28:30: DEBUG: Les nouvelles connexions seront m‚moris‚es.
09:28:30: DEBUG:
09:28:30: DEBUG: La liste est vide.
09:28:30: DEBUG:
09:28:30: INFO:
09:28:30: INFO: Trying to store 'rawprogram0.xml' in string table
09:28:30: DEBUG: ==================================================================================
09:28:30: DEBUG: ==================================================================================
09:28:30: INFO: Looking for file 'rawprogram0.xml'
09:28:30: DEBUG: 1. Calling stat(C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml')
09:28:30: DEBUG: 2. Calling fopen('C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml') with AccessMode='rb'
09:28:30: DEBUG: Trying get filesize, calling fseek()
09:28:30: DEBUG: Found 'C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml' (5089 bytes)
09:28:30: DEBUG: 2. Calling fopen('C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml') with AccessMode='r'
09:28:30: DEBUG: Trying get filesize, calling fseek()
09:28:30: DEBUG: User set ZLPAWAREHOST to 1
09:28:30: INFO: User wants to talk to port '\\.\COM4'
09:28:40: DEBUG: port_fd=0xC8
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
09:28:40: {ERROR: OpenPort:5566 It took 10.00000000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable
So where is the problem ? Shortcutting the two points is supposed to open the FireHose port but i tested with twezzers, cooper cable...ect nothing seem to work
any Idea ?
thank you
Click to expand...
Click to collapse
qfil needs the firehose.bin i know we dont have one for the sprint varient also have u tried any debrick imgs and sd card method?

Guys just flash the ls991 files and the problem with imei is fixable by flashing some files through fastboot
Do what this says and if you bricked your phone just flash ls991 files again
Only problem which remains is sd card read and write
But you will have a full functional phone

shamescool said:
Guys just flash the ls991 files and the problem with imei is fixable by flashing some files through fastboot
Do what this says and if you bricked your phone just flash ls991 files again
Only problem which remains is sd card read and write
But you will have a full functional phone
Click to expand...
Click to collapse
Please do not mislead other people and try not to answer questions if you didn't try the fixes yourself.
Depending on the bootstack of the CPU SD method might or might nor work.
In theory you can EMMC repair with LS991 but then you will have SecureBoot problems (Error 1006). I didn't try it yet but there is a method where you force off emmc verification by shorting EMMC CMD terminal to GND. But this requires very small soldering, opening the phone and removing the motherboard. The method is tried and working on 4PDA.
EDIT: @AZstyle The firehose are scams, the only working one is the ls991 which I think is a developer one because you will get fastboot access but I can't personally flash anything in LGUP.
When I flash all partitions but bootstack I get 1006 error. I didn't try the soldering method because I have a Medusa Box on the way. I will try USB Repair and if it does not work I will just RMA.

neutrondev said:
Please do not mislead other people and try not to answer questions if you didn't try the fixes yourself.
Depending on the bootstack of the CPU SD method might or might nor work.
In theory you can EMMC repair with LS991 but then you will have SecureBoot problems (Error 1006). I didn't try it yet but there is a method where you force off emmc verification by shorting EMMC CMD terminal to GND. But this requires very small soldering, opening the phone and removing the motherboard. The method is tried and working on 4PDA.
EDIT: @AZstyle The firehose are scams, the only working one is the ls991 which I think is a developer one because you will get fastboot access but I can't personally flash anything in LGUP.
When I flash all partitions but bootstack I get 1006 error. I didn't try the soldering method because I have a Medusa Box on the way. I will try USB Repair and if it does not work I will just RMA.
Click to expand...
Click to collapse
im not misleading anyone here im just sharing my experience
yes you will get 1006 problem by flashing partitions but at least you get a fully functioning phone
the way i mentioned is actually worked for another person here in this forum please test if you still have doubt
my phone is also a refurbished h811 which has a f500l mobo on it and flashing those ls991 files made the phone alive in h811 10n but i did nt have any imei or base band no camera too(even speaker and sensors didnt work)
so i tried flashing some partitions in fastboot and then i had my imei back and also the camera
then i edited f500 tot file with winhex and my phone bricked again(obviously)so i tried flashing ls991 again and now i have a fully functioning phone which cannot be said for sd card...my phone cant write or read any sdcard and its really pissing me of
any suggest for sd card?

H810_ARecovery
¿How to use or flash this files?, tell me please.

neutrondev said:
I bought a subscription from easy-firmware hoping that they have right emmc_firehose. They are scammers. I have a bricked LG G4 too and since now I have not found a way to unbrick it. Do not waste your time. For H815 the files are wrong and we also need nonfused emmc_firehose_programmer. Also the SD Card method is not working for me tried it with 10 different images and 4 different cards. I am investigating this issue and if I find a solution I will make a tutorial for all fellas that are in trouble.
Click to expand...
Click to collapse
u are right, i already tested all this ****, its appear that the only solution is to repair the emmc boot with octopus box or medusa box
next week i'll bring my G4 to a repair store to do this operation.
and I will keep u informed with the results

AZstyle said:
u are right, i already tested all this ****, its appear that the only solution is to repair the emmc boot with octopus box or medusa box
next week i'll bring my G4 to a repair store to do this operation.
and I will keep u informed with the results
Click to expand...
Click to collapse
I bought a medusa box and did the soldering myself. It will not work -_-. I will investigate further but it might need Emmc replacement. Did you try to flash with Qfil using LS991 programmer emmc_firehose? It is very important to know

neutrondev said:
I bought a medusa box and did the soldering myself. It will not work -_-. I will investigate further but it might need Emmc replacement. Did you try to flash with Qfil using LS991 programmer emmc_firehose? It is very important to know
Click to expand...
Click to collapse
Good Remark, I can't remember if I tested with LS911 files, I tested with H815 H818p without sucess.
Do you have the files for LS911? can u share them with me please so i'll give a try.
Thanks

What about that ?
and this

serestma said:
Hello, ¿you can share the links?, I need the files for LG H810.
Thank you in advance.
Click to expand...
Click to collapse
https://mega.nz/#F!1DhXTLAa!kH8MfkbeOKcUWt3T2R6cTQ

@AZstyle Do not flash with those files because I think you will need CPU swap. I think that programmer blows fuses for US version. I did that and now I can't repair it even with MEDUSA I can flash ls991 firmware it boots but with H815 NO.

the_naxhoo said:
I got the same problem with my H815T. It only allows me to flash the LS991 files, but I lose the imei
H810: https://mega.nz/#!55tACDZC!Ci1pjEr8_wr9Ng2SrPgj42MwxnGybo60de26w2gtimg
Click to expand...
Click to collapse
No Problem If You Loosed IMEI I Can Flash IMEI For You Just Poke Me On WhatsApp Only WhatsApp !!!
7000926368
Hope I Can Help You
Sent from my LS-4004 using Tapatalk

neutrondev said:
I bought a medusa box and did the soldering myself. It will not work -_-. I will investigate further but it might need Emmc replacement. Did you try to flash with Qfil using LS991 programmer emmc_firehose? It is very important to know
Click to expand...
Click to collapse
Yes I have flashed ls991 firehose . What do you need to know?
.
Sent from my LG-H815 using XDA Labs

neutrondev said:
I bought a medusa box and did the soldering myself. It will not work -_-. I will investigate further but it might need Emmc replacement. Did you try to flash with Qfil using LS991 programmer emmc_firehose? It is very important to know
Click to expand...
Click to collapse
Medusa Pro Box Works Like Charm !!!
I Fixed 7 LG G4 With It EMMC One
And 3 LG G4 With USB One
If Someone Have Medusa Pro Box And Unable To Fix With It Thats Sure That You Might Have Not Soldered Wire Correct Or Motherboard Has Hardware Problem
Sent from my LS-4004 using Tapatalk

steadfasterX said:
Yes I have flashed ls991 firehose . What do you need to know?
.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Dont know where i find a ls992 firehose do you?
I bricked my g5 in a freak bad usb cord accident.

Related

huawei watch 2 sport 4g

bonjour
huawei watch 2 spor 4g
âpre voire flache une rom, tout effacer ecran noir pas fastboot ni recovery
j'essaie flasher qfil + Leo-L09S_Recovery ne fonction pas
Image Search Path: C:\Program Files (x86)\Qualcomm\QPST\bin\Leo-L09S_Recovery
RAWPROGRAM file path: C:\Program Files (x86)\Qualcomm\QPST\bin\Leo-L09S_Recovery\rawprogram_unsparse.xml
PATCH file path:C:\Program Files (x86)\Qualcomm\QPST\bin\Leo-L09S_Recovery\patch0.xml
Start Download
Program Path:C:\Program Files (x86)\Qualcomm\QPST\bin\Leo-L09S_Recovery\prog_emmc_firehose.mbn
***** Working Folder:C:\Users\h\AppData\Roaming\Qualcomm\QFIL\COMPORT_5
Binary build date: Nov 21 2017 @ 02:53:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\h\AppData\Roaming\Qualcomm\QFIL\COMPORT_5
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.mb 31: mba.mbn
13: C:\Program Files (x86)\Qualcomm\QPST\bin\Leo-L09S_Recovery\prog_emmc_firehose.mbn
Requested ID 13, file: "C:\Program Files (x86)\Qualcomm\QPST\bin\Leo-L09S_Recovery\prog_emmc_firehose.mbn"
281052 bytes transferred in 0.156000 seconds (1.7182MBps) File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
10:55:18: 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\h\AppData\Roaming\Qualcomm\QFIL\COMPORT_5
Base Version: 17.11.16.14.34
Binary build date: Nov 21 2017 @ 02:53:33
Incremental Build version: 17.11.21.02.53.33
10:55:21: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM5 --sendxml=rawprogram_unsparse.xml --search_path=C:\Program Files (x86)\Qualcomm\QPST\bin\Leo-L09S_Recovery --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
10:55:21: INFO: Current working dir (cwd): C:\Users\h\AppData\Roaming\Qualcomm\QFIL\COMPORT_5\
10:55:21: INFO: Showing network mappings to allow debugging
10:55:21: INFO:
10:55:21: INFO: Trying to store 'rawprogram_unsparse.xml' in string table
INFO: Looking for file 'rawprogram_unsparse.xml'
INFO: User wants to talk to port '\\.\COM5'
INFO: Took 0.00000000 seconds to open port
INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
INFO: If you don't want this, use --dontsorttags
10:55:21: INFO: Looking for file 'sbl1.mbn'
10:55:21: INFO: Looking for file 'sbl1.mbn'
10:55:21: INFO: Looking for file 'rpm.mbn'
10:55:21: INFO: Looking for file 'rpm.mbn'
10:55:21: INFO: Looking for file 'tz.mbn'
__ ____ _ _ __ _ __ _ _ __ __ _
\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
\ V V / (_| | | | | | | | | | | (_| |
\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
__/ |
|___/
WARNING: Couldn't find the file 'tz.mbn', returning NULL
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
{ERROR: 'tz.mbn' not found. You could possibly try --notfiles=tz.mbn,OtherFileToSkip.bin (note, exiting since you specified --noprompt)}
Writing log to 'C:\Users\h\AppData\Roaming\Qualcomm\QFIL\COMPORT_5\port_trace.txt', might take a minute
Log is 'C:\Users\h\AppData\Roaming\Qualcomm\QFIL\COMPORT_5\port_trace.txt'
Download Fail:FireHose Fail:FHLoader Failrocess fail
Finish Download
codialement

https://forum.xda-developers.com/watch-2
https://forum.xda-developers.com/announcement.php?a=81
Rule 4

Zenfone 3 Deluxe brick edl only

hello everyone, I humbly ask for your help, I have had this phone for 2 days, following an update, I find the phone practically dead, connecting it to my PC recognizes it as a Qualcomm driver, and it is already a good sign .... I downloaded Qfil to rifleshare the firmware and I don't complete it by giving me some errors, can I have your opinion? could you help me thank you.
ATTACH THE LOG OF THE FOLLOWING ERROR
16:49:50: INFO: Looking for file 'BTFM.bin'
16:49:50: INFO: Looking for file 'keymaster.mbn'
16:49:50: INFO: Looking for file 'keymaster.mbn'
16:49:50: INFO: Looking for file 'cmnlib.mbn'
16:49:50: INFO: Looking for file 'cmnlib.mbn'
16:49:50: INFO: Looking for file 'cmnlib64.mbn'
16:49:50: INFO: Looking for file 'cmnlib64.mbn'
16:49:50: INFO: Looking for file 'splash.img'
16:49:50: INFO: Looking for file 'gpt_main4.bin'
16:49:50: INFO: Looking for file 'gpt_backup4.bin'
16:49:50: INFO: Looking for file 'gpt_main5.bin'
16:49:50: INFO: Looking for file 'gpt_backup5.bin'
16:49:50: INFO:
Total to be tansferd with <program> or <read> is 3.88 GB
16:49:50: INFO: Sending <configure>
16:49:50: INFO: TARGET SAID: 'Binary build date: Jun 17 2016 @ 10:09:02'
16:49:50: INFO: TARGET SAID: 'Chip serial num: 3066003435 (0xb6bf7feb)'
16:49:50: INFO: TARGET SAID: 'Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke '
16:49:50: INFO: TARGET SAID: 'VIP - Validated Image Programming is enabled - Validation is enabled.'
16:49:50: INFO: TARGET SAID: 'Image Total Size = 0xE4 (228)'
16:49:50: INFO: TARGET SAID: 'HeaderIs80Bytes = 0x0'
16:49:50: INFO: TARGET SAID: 'image_info.sw_type = 0x3 (DeviceProgrammer *insists* on this)'
16:49:50: INFO: TARGET SAID: 'image_info.sw_version = 0x0'
16:49:50: INFO: TARGET SAID: 'image_info.header_len_1 = 0x28'
16:49:50: INFO: TARGET SAID: 'image_info.code_ptr_1 = 0xF54AC112'
16:49:50: INFO: TARGET SAID: 'image_info.code_len_1 = 0x6F636E65'
16:49:50: INFO: TARGET SAID: 'image_info.x509_chain_ptr = 0x1782EE58'
16:49:50: INFO: TARGET SAID: 'image_info.x509_chain_len = 0xA3E3F20'
16:49:50: INFO: TARGET SAID: 'image_info.signature_ptr = 0x5CB92A76'
16:49:50: INFO: TARGET SAID: 'image_info.signature_len = 0x5455223D'
16:49:50: INFO: TARGET SAID: 'image_info.header_ptr_1 = 0x85E14DA0'
16:49:50: INFO: TARGET SAID: 'AuthenticateImage() Returning FALSE, secboot_authenticate() returned 0x2 (not E_SECBOOT_SUCCESS=0x0)'
16:49:50: INFO: TARGET SAID: 'ERROR 1: Line 1140: AUTHENTICATE_IMAGE_FAILURE'
16:49:50: INFO: TARGET SAID: 'Failed to authenticate Digital Signature, resetting validation state'
16:49:50: INFO: TARGET SAID: 'ERROR 11: Line 790: DIGITAL_SIGNATURE_DID_NOT_PASS'
16:49:50: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
16:49:50: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
16:49:50: INFO: Something failed. The target rejected your <configure>. Please inspect log for more information
Writing log to 'C:\Users\pp\AppData\Roaming\Qualcomm\QFIL\COMPORT_5\port_trace.txt', might take a minute
Log is 'C:\Users\pp\AppData\Roaming\Qualcomm\QFIL\COMPORT_5\port_trace.txt'
Download Fail:FireHose Fail:FHLoader Failrocess fail
Finish Download

Help unbricking Xiaomi Mi Note 3 (not redmi)

hi guys i have been trying to unbrick the phone via miflash and qfil with no sucess for the past week... now im boiling... and hoping i can get some help from you guys.
The phone is on black screen so i use the 2 jumpers to enter into edl mode...
i get this error while trying to flash the rom.
If you guys can help i will totally apreciate it.
[18:40:30 COM3]:MiFlash 2017.12.12.0
[18:40:30 COM3]:flash in thread name:COM3,id:10
[18:40:30 COM3]:QSaharaServer.exe -u 3 -s 13:C:\ROM MI NOTE 3\jason_global_images_V10.4.2.0.PCHMIXM_20190906.0000.00_9.0_global_8c73072230\jason_global_images_V10.4.2.0.PCHMIXM_20190906.0000.00_9.0_global\images\prog_emmc_firehose_Sdm660_ddr.elf & fh_loader.exe --port=\\.\COM3 --sendxml=rawprogram0.xml --search_path=C:\ROM MI NOTE 3\jason_global_images_V10.4.2.0.PCHMIXM_20190906.0000.00_9.0_global_8c73072230\jason_global_images_V10.4.2.0.PCHMIXM_20190906.0000.00_9.0_global\images --noprompt --showpercentagecomplete --maxpayloadsizeinbytes=0 --zlpawarehost=1 --memoryname=ufs --verbose & fh_loader.exe --port=\\.\COM3 --sendxml=patch0.xml --search_path=C:\ROM MI NOTE 3\jason_global_images_V10.4.2.0.PCHMIXM_20190906.0000.00_9.0_global_8c73072230\jason_global_images_V10.4.2.0.PCHMIXM_20190906.0000.00_9.0_global\images --noprompt --showpercentagecomplete --maxpayloadsizeinbytes=0 --zlpawarehost=1 --memoryname=ufs --verbose & fh_loader.exe --port=\\.\COM3 --setactivepartition=1 --noprompt --showpercentagecomplete --maxpayloadsizeinbytes=0 --zlpawarehost=1 --memoryname= ufs --verbose & fh_loader.exe --port=\\.\COM3 --reset --noprompt --showpercentagecomplete --maxpayloadsizeinbytes=0 --zlpawarehost=1 --memoryname=ufs --verbose
[18:40:30 COM3]hysical Memory Usage:110592 Byte
[18:40:30 COM3]:start process id 12604 name cmd
[18:42:01 COM3]:Binary build date: May 9 2017 @ 03:56:22
[18:42:01 COM3]:QSAHARASERVER CALLED LIKE THIS: 'QSaharaServer.ex'Current working dir: C:\20171\MiFlash20171212
[18:42:01 COM3]:Sahara mappings:
[18:42:01 COM3]:2: amss.mbn
[18:42:01 COM3]:6: apps.mbn
[18:42:01 COM3]:8: dsp1.mbn
[18:42:01 COM3]:10: dbl.mbn
[18:42:01 COM3]:11: osbl.mbn
[18:42:01 COM3]:12: dsp2.mbn
[18:42:01 COM3]:16: efs1.mbn
[18:42:01 COM3]:17: efs2.mbn
[18:42:01 COM3]:20: efs3.mbn
[18:42:01 COM3]:21: sbl1.mbn
[18:42:01 COM3]:22: sbl2.mbn
[18:42:01 COM3]:23: rpm.mbn
[18:42:01 COM3]:25: tz.mbn
[18:42:01 COM3]:28: dsp3.mbn
[18:42:01 COM3]:29: acdb.mbn
[18:42:01 COM3]:30: wdt.mbn
[18:42:01 COM3]:31: mba.mbn
[18:42:01 COM3]:13: C:\ROM
[18:42:01 COM3]:18:42:00: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
[18:42:01 COM3]:18:42:00: ERROR: function: sahara_main:924 Sahara protocol error
[18:42:01 COM3]:18:42:00: ERROR: function: main:303 Uploading Image using Sahara protocol failed
[18:42:01 COM3]:Base Version: 17.04.27.14.27
[18:42:01 COM3]:Binary build date: May 9 2017 @ 03:56:18
[18:42:01 COM3]:Incremental Build version: 17.05. 9.03.56.18
[18:42:01 COM3]: _____
[18:42:01 COM3]: | ___|
[18:42:01 COM3]: | |__ _ __ _ __ ___ _ __
[18:42:01 COM3]: | __| '__| '__/ _ \| '__|
[18:42:01 COM3]: | |__| | | | | (_) | |
[18:42:01 COM3]: \____/_| |_| \___/|_|
[18:42:01 COM3]:18:42:01: {ERROR: Option 'MI' does not begin with --
[18:42:01 COM3]:}
[18:42:01 COM3]:ERROR: Could not append to 'port_trace.txt'
[18:42:01 COM3]:Log is 'C:\20171\MiFlash20171212\port_trace.txt'
[18:42:01 COM3]:Base Version: 17.04.27.14.27
[18:42:01 COM3]:Binary build date: May 9 2017 @ 03:56:18
[18:42:01 COM3]:Incremental Build version: 17.05. 9.03.56.18
[18:42:01 COM3]: _____
[18:42:01 COM3]: | ___|
[18:42:01 COM3]: | |__ _ __ _ __ ___ _ __
[18:42:01 COM3]: | __| '__| '__/ _ \| '__|
[18:42:01 COM3]: | |__| | | | | (_) | |
[18:42:01 COM3]: \____/_| |_| \___/|_|
[18:42:01 COM3]:18:42:01: {ERROR: Option 'MI' does not begin with --
[18:42:01 COM3]:}
[18:42:01 COM3]:ERROR: Could not append to 'port_trace.txt'
[18:42:01 COM3]:Log is 'C:\20171\MiFlash20171212\port_trace.txt'
[18:42:01 COM3]:Base Version: 17.04.27.14.27
[18:42:01 COM3]:Binary build date: May 9 2017 @ 03:56:18
[18:42:01 COM3]:Incremental Build version: 17.05. 9.03.56.18
[18:42:01 COM3]: _____
[18:42:01 COM3]: | ___|
[18:42:01 COM3]: | |__ _ __ _ __ ___ _ __
[18:42:01 COM3]: | __| '__| '__/ _ \| '__|
[18:42:01 COM3]: | |__| | | | | (_) | |
[18:42:01 COM3]: \____/_| |_| \___/|_|
[18:42:01 COM3]:18:42:01: {ERROR: Option 'ufs' does not begin with --
[18:42:01 COM3]:}
[18:42:01 COM3]:ERROR: Could not append to 'port_trace.txt'
[18:42:01 COM3]:Log is 'C:\20171\MiFlash20171212\port_trace.txt'
[18:42:01 COM3]:Base Version: 17.04.27.14.27
[18:42:01 COM3]:Binary build date: May 9 2017 @ 03:56:18
[18:42:01 COM3]:Incremental Build version: 17.05. 9.03.56.18
[18:42:01 COM3]:18:42:01: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
[18:42:01 COM3]:************************************************
[18:42:01 COM3]:fh_loader.exe --port=\\.\COM3 --reset --noprompt --showpercentagecomplete --maxpayloadsizeinbytes=0 --zlpawarehost=1 --memoryname=ufs --verbose
[18:42:01 COM3]:************************************************
[18:42:01 COM3]:18:42:01: INFO: Current working dir (cwd): C:\20171\MiFlash20171212\
[18:42:01 COM3]:18:42:01: INFO: Showing network mappings to allow debugging
[18:42:01 COM3]:18:42:01: INFO: User wants to talk to port '\\.\COM3'
[18:42:01 COM3]:18:42:01: INFO: Took 0.00000000 seconds to open port
[18:42:01 COM3]:18:42:01: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
[18:42:01 COM3]:18:42:01: INFO: If you don't want this, use --dontsorttags
[18:42:01 COM3]:18:42:01: INFO: Sending <configure>
[18:42:01 COM3]: _____
[18:42:01 COM3]: | ___|
[18:42:01 COM3]: | |__ _ __ _ __ ___ _ __
[18:42:01 COM3]: | __| '__| '__/ _ \| '__|
[18:42:01 COM3]rocess exit id 12604 name cmd
[18:42:01 COM3]: | |__| | | | | (_) | |
[18:42:01 COM3]:error:18:42:00: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
[18:42:01 COM3]:error:18:42:00: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
[18:42:01 COM3]rocess exit.
[18:42:01 COM3]:flashSuccess False
[18:42:01 COM3]:isFactory False CheckCPUID False
[18:42:01 COM3]:before:flashSuccess is False set IsUpdate:True set IsDone True
[18:42:01 COM3]:after:flashSuccess is False set IsUpdate:false set IsDone true

hard bricked willow (redmi note 8t) no fastboot / no recovery

I managed to flash the wrong firmware (ginkgo fw => willow) and now the thing is bricked. the only sign of life is a COM30 device under MiFlash / QFIL.
Is there any chance I can unbrick the device myself? I do not want to open it though....

I just found this: https://forum.xda-developers.com/t/...ight-turns-on-for-a-second-using-edl.4228641/
I followed the instructions, but I also get the sahara fail. QFIL says QDLoader 9008 (COM30) - is this EDL mode?

lueromat said:
....
I followed the instructions, but I also get the sahara fail. QFIL says QDLoader 9008 (COM30) - is this EDL mode?
Click to expand...
Click to collapse
Yes, this looks like EDL on com port 30.
You only get QDloader 9008 if you have installed the drivers before, so maybe these are old versions.

Elinx said:
Yes, this looks like EDL on com port 30.
You only get QDloader 9008 if you have installed the drivers before, so maybe these are old versions.
Click to expand...
Click to collapse
sorry, confused - are you sayin this is EDL mode? this is what I see in my device manager:
Qualcomm HS-USB QDLoader 9008 (COM30)

lueromat said:
sorry, confused - are you sayin this is EDL mode? this is what I see in my device manager:
Qualcomm HS-USB QDLoader 9008 (COM30)
Click to expand...
Click to collapse
Yes, if fastboot and recovery aren't possible anymore, you can with testpoint to EDL. But it looks that your device already is in EDL mode

ok - so I don't have to open it up?
does anyone have any idea why I get the error in GFIL?
or any other comments or suggestions?
sucks to have a brick

lueromat said:
...
does anyone have any idea why I get the error in GFIL?
...
Click to expand...
Click to collapse
Try first to update the drivers

Download willow fastboot ROM and extract. Download the programmer(need decompress) and replace the original one which is in "images" folder. Run Xiaomi Flash and select the fastboot ROM folder and it gets ready.
Long press your power button more than 10s so the device could do a power cycle. Then, connect the device to the computer and start flashing immediately.
The programmer posted here is for ginkgo. But ginkgo and willow have same chipset so you can try again.
Good luck.

lueromat said:
...
or any other comments or suggestions?
...
Click to expand...
Click to collapse
Yuki1001 said:
Download willow fastboot ROM and extract. ......
Click to expand...
Click to collapse
Ofcourse, as Yuki1001 said.
Don't use the mentioned Ginkgo rom of the guide, but a fastboot Willow rom. The same as your Willow was delivered from factory or newer. The patched firehose file is the same. Maybe then the flashing will run without error.

Yuki1001 said:
Download willow fastboot ROM and extract. Download the programmer(need decompress) and replace the original one which is in "images" folder. Run Xiaomi Flash and select the fastboot ROM folder and it gets ready.
Long press your power button more than 10s so the device could do a power cycle. Then, connect the device to the computer and start flashing immediately.
Click to expand...
Click to collapse
so this worked! the xiaomi flash tool did something, and it said "flashing success" afterwards. but now nothing happens. shouldn't it be able to boot now that the correct image has been flashed? or do I now have to use QFIL?

After "flashing succes", the image should be flashed. Try to boot with long press power

Elinx said:
After "flashing succes", the image should be flashed. Try to boot with long press power
Click to expand...
Click to collapse
hmm doesn't work unfortunately. I even tried the procedure again: soo it appears that something has been flashed, but afterwards I cannot get it to boot and it still says Qualcomm HS-USB QDLoader 9008 (COM30). maybe it doesn't work with xiaomi flash tool?

lueromat said:
so this worked! the xiaomi flash tool did something, and it said "flashing success" afterwards. but now nothing happens. shouldn't it be able to boot now that the correct image has been flashed? or do I now have to use QFIL?
Click to expand...
Click to collapse
Are you sure the fastboot ROM you flashed is the correct WILLOW fastboot ROM?
Download latest willow fastboot ROM here.
As I said above, extract fastboot ROM and replace the programmer in "images" folder. Then flash again. Please give a screenshot of XiaomiFlash so I could understand your problem better.
You can also try to flash using QFIL.

lueromat said:
hmm doesn't work unfortunately. I even tried the procedure again: soo it appears that something has been flashed, but afterwards I cannot get it to boot and it still says Qualcomm HS-USB QDLoader 9008 (COM30). maybe it doesn't work with xiaomi flash tool?
Click to expand...
Click to collapse
chiming in with my experience here: try to open & disconnect the battery for about 15 seconds after flashing success.
happened with my old Mi 5s Plus, it was stuck in FORCED EDL mode, no way to recover except by battery disconnection after successful flash.

Crescendo Xenomorph said:
... try to open & disconnect the battery for about 15 seconds after flashing success.
..
Click to expand...
Click to collapse
You could be right with this, because I only had a succesfull flash/startup with disconnected battery.
I'm not sure, but it could be that this was the same behaviour with my phone. Phone didn't start after EDL flash.
I hadn't noticed it because I immediately flashed (succesfull) again, with disconnected battery.
Problem is, lueromat hasn't opened his phone for EDL and tries to prevent this.
Maybe full batterydrain will work too.
Question....... is it possible to start fastboot now?
In that case you can try to flash a fastboot rom the normal way again with flashall.bat.

Elinx said:
You could be right with this, because I only had a succesfull flash/startup with disconnected battery.
I'm not sure, but it could be that this was the same behaviour with my phone. Phone didn't start after EDL flash.
I hadn't noticed it because I immediately flashed (succesfull) again, with disconnected battery.
Problem is, lueromat hasn't opened his phone for EDL and tries to prevent this.
Maybe full batterydrain will work too.
Question....... is it possible to start fastboot now?
In that case you can try to flash a fastboot rom the normal way again with flashall.bat.
Click to expand...
Click to collapse
I own a RN8(ginkgo) and it's not easy to open the back cover. I manually went to EDL with a fastboot command and do an experiment to confirm it could flash without errors.. The result is that the phone reboot and boot up with no problems.
Maybe he could try to force reboot by sending reboot command if lueromat did a correct flashing?

@lueromat Try to send reboot command manually.
XML:
<?xml version="1.0"?>
<data>
<power value="reset" />
</data>
(The power tag could let the device reboot to system/to edl with correct value)
Create a xml file and send it to the phone manually after flashing.
Rename the xml to "reboot.xml". I wondering what will happen after you send this command(xml).
Code:
fh_loader.exe --port=\\.\COM30 --sendxml=reboot.xml --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc

Elinx said:
Problem is, lueromat hasn't opened his phone for EDL and tries to prevent this.
Maybe full batterydrain will work too.
Click to expand...
Click to collapse
Yuki1001 said:
Maybe he could try to force reboot by sending reboot command if lueromat did a correct flashing?
Click to expand...
Click to collapse
I think you guys may be on to something. I was also thinking that I somehow have to get out of EDL mode, either through waiting, or forcing. Opening the device is a PITA and I'd rather wait until the battery dies (which I guess may take weeks with the screen and all off - good I ordered the poco m3 as replacement ).
So I tried the xml command via fh_loader, but it didn't quite work - see log below. either the xml syntax is wrong, or my phone is still in "sahara-mode" - whatever that is. I tried to play around with QFIL before, maybe it's because of that.
Code:
16:34:07: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
fh_loader.exe --port=\\.\COM40 --sendxml=reboot.xml --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
16:34:07: DEBUG: Binary build date: Jun 25 2019 @ 03:16:10
16:34:07: DEBUG: Build Version: 19.06.25.03.16.10
16:34:07: INFO: Current working dir (cwd): C:\Program Files (x86)\Qualcomm\QPST\bin\
16:34:07: INFO: Showing network mappings to allow debugging
16:34:07: DEBUG: New connections will be remembered.
16:34:07: DEBUG:
16:34:07: DEBUG: There are no entries in the list.
16:34:07: DEBUG:
16:34:07: INFO:
16:34:07: INFO: Trying to store 'reboot.xml' in string table
16:34:07: DEBUG: ==================================================================================
16:34:07: DEBUG: ==================================================================================
16:34:07: INFO: Looking for file 'reboot.xml'
16:34:07: DEBUG: 2. Calling stat(reboot.xml)
16:34:07: DEBUG: 2. Calling fopen('reboot.xml') with AccessMode='rb'
16:34:07: DEBUG: Trying get filesize, calling fseek()
16:34:07: DEBUG: Found 'reboot.xml' (65 bytes) in local directory 'C:\Program Files (x86)\Qualcomm\QPST\bin\
16:34:07: DEBUG: 2. Calling fopen('reboot.xml') with AccessMode='r'
16:34:07: DEBUG: Trying get filesize, calling fseek()
16:34:07: DEBUG: User set ZLPAWAREHOST to 1
16:34:07: INFO: User wants to talk to port '\\.\COM40'
16:34:07: DEBUG: port_fd=0xE0
16:34:07: INFO: Took 0.00000000 seconds to open port
16:34:07: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
16:34:07: INFO: Sending <configure>
16:34:07: DEBUG: CHANNEL DATA (P0000) (H00202) ( 228 bytes) - HOST TO TARGET -->
===========================================================================================================
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<configure MemoryName="emmc" Verbose="0" AlwaysValidate="0" MaxDigestTableSizeInBytes="8192" MaxPayloadSizeToTargetInBytes="1048576" ZlpAwareHost="1" SkipStorageInit="0" />
</data>
============================================================================================================
16:34:07: DEBUG: CharsInBuffer=0 Trying to read from USB 8192 bytes
16:34:07: DEBUG: CHANNEL DATA (64 bytes) <-- TARGET to HOST
16:34:07: DEBUG: CharsInBuffer = 64
16:34:07: DEBUG: printBuffer:6017 PRETTYPRINT Buffer is 64 bytes
16:34:07: DEBUG: printBuffer:6094 01 00 00 00 30 00 00 00 02 00 00 00 01 00 00 00 ....0...........
16:34:07: DEBUG: printBuffer:6094 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
16:34:07: DEBUG: printBuffer:6094 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
16:34:07: DEBUG: printBuffer:6094 04 00 00 00 10 00 00 00 0D 00 00 00 01 00 00 00 ................
16:34:07: DEBUG: printBuffer:6107
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
16:34:07: {ERROR: DetermineTag:6861 XML not formed correctly. Expected a < character at loc 0
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
16:34:07: {ERROR: GetNextPacket:7935 3. TAG not found or recognized
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
16:34:07: {ERROR: GetNextPacket:7945
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
This can mean
1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13:prog_emmc_firehose_8994_lite.mbn)
2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target
Regardless this program speaks FIREHOSE protocol and your target is speaking SAHARA protcol, so this will not work

lueromat said:
I think you guys may be on to something. I was also thinking that I somehow have to get out of EDL mode, either through waiting, or forcing. Opening the device is a PITA and I'd rather wait until the battery dies (which I guess may take weeks with the screen and all off - good I ordered the poco m3 as replacement ).
So I tried the xml command via fh_loader, but it didn't quite work - see log below. either the xml syntax is wrong, or my phone is still in "sahara-mode" - whatever that is. I tried to play around with QFIL before, maybe it's because of that.
Code:
16:34:07: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
fh_loader.exe --port=\\.\COM40 --sendxml=reboot.xml --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
16:34:07: DEBUG: Binary build date: Jun 25 2019 @ 03:16:10
16:34:07: DEBUG: Build Version: 19.06.25.03.16.10
16:34:07: INFO: Current working dir (cwd): C:\Program Files (x86)\Qualcomm\QPST\bin\
16:34:07: INFO: Showing network mappings to allow debugging
16:34:07: DEBUG: New connections will be remembered.
16:34:07: DEBUG:
16:34:07: DEBUG: There are no entries in the list.
16:34:07: DEBUG:
16:34:07: INFO:
16:34:07: INFO: Trying to store 'reboot.xml' in string table
16:34:07: DEBUG: ==================================================================================
16:34:07: DEBUG: ==================================================================================
16:34:07: INFO: Looking for file 'reboot.xml'
16:34:07: DEBUG: 2. Calling stat(reboot.xml)
16:34:07: DEBUG: 2. Calling fopen('reboot.xml') with AccessMode='rb'
16:34:07: DEBUG: Trying get filesize, calling fseek()
16:34:07: DEBUG: Found 'reboot.xml' (65 bytes) in local directory 'C:\Program Files (x86)\Qualcomm\QPST\bin\
16:34:07: DEBUG: 2. Calling fopen('reboot.xml') with AccessMode='r'
16:34:07: DEBUG: Trying get filesize, calling fseek()
16:34:07: DEBUG: User set ZLPAWAREHOST to 1
16:34:07: INFO: User wants to talk to port '\\.\COM40'
16:34:07: DEBUG: port_fd=0xE0
16:34:07: INFO: Took 0.00000000 seconds to open port
16:34:07: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
16:34:07: INFO: Sending <configure>
16:34:07: DEBUG: CHANNEL DATA (P0000) (H00202) ( 228 bytes) - HOST TO TARGET -->
===========================================================================================================
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<configure MemoryName="emmc" Verbose="0" AlwaysValidate="0" MaxDigestTableSizeInBytes="8192" MaxPayloadSizeToTargetInBytes="1048576" ZlpAwareHost="1" SkipStorageInit="0" />
</data>
============================================================================================================
16:34:07: DEBUG: CharsInBuffer=0 Trying to read from USB 8192 bytes
16:34:07: DEBUG: CHANNEL DATA (64 bytes) <-- TARGET to HOST
16:34:07: DEBUG: CharsInBuffer = 64
16:34:07: DEBUG: printBuffer:6017 PRETTYPRINT Buffer is 64 bytes
16:34:07: DEBUG: printBuffer:6094 01 00 00 00 30 00 00 00 02 00 00 00 01 00 00 00 ....0...........
16:34:07: DEBUG: printBuffer:6094 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
16:34:07: DEBUG: printBuffer:6094 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
16:34:07: DEBUG: printBuffer:6094 04 00 00 00 10 00 00 00 0D 00 00 00 01 00 00 00 ................
16:34:07: DEBUG: printBuffer:6107
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
16:34:07: {ERROR: DetermineTag:6861 XML not formed correctly. Expected a < character at loc 0
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
16:34:07: {ERROR: GetNextPacket:7935 3. TAG not found or recognized
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
16:34:07: {ERROR: GetNextPacket:7945
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
This can mean
1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13:prog_emmc_firehose_8994_lite.mbn)
2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target
Regardless this program speaks FIREHOSE protocol and your target is speaking SAHARA protcol, so this will not work
Click to expand...
Click to collapse
Did you send the firehose programmer before you send the reboot xml?
As the log said, may be you forgot to send programmer manually?
{
"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"
}
Do a power cycle and send "prog_emmc_firehose_Sm6125_ddr.elf" using QSaharaServer.exe first:
Code:
QSaharaServer.exe -u 40 -s 13:"prog_emmc_firehose_Sm6125_ddr.elf"
The parameter "-u" is your port number(example COM40 is -u 40).
Then send xml.
Code:
fh_loader.exe --port=\\.\COM40 --sendxml=reboot.xml --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
You need to send the programmer first to switch the communication protocol to firehose then use fh_loader send reboot xml command. Sorry forgetting to tell you that you need to send programmer first. In fact, before your any operation in EDL mode, your flashtool(miflash/qifl etc..) send the programmer automatically before sending rawprogram0.xml. You can check the flash log for this.
If device reboot but still in EDL mode, may be you need to wait until the battery runs out because I don't know more usage of power command to force reboot to system.
Hope your phone could reboot and back to life.

those commands completed without problem, and after the fh command the phone is disconnected in my device manager for a second, so it appears the xml command worked. however, when it reappears in device manager it's still on com40, and I cannot boot into bootloader. maybe a different command will do it? at least it's listening. here is the log:
Code:
C:\Program Files (x86)\Qualcomm\QPST\bin>QSaharaServer.exe -u 40 -s 13:"prog_emmc_firehose_Sm6125_ddr.elf"
Binary build date: Jun 25 2019 @ 03:16:15
QSAHARASERVER CALLED LIKE THIS: 'QSaharaServer.ex'Current working dir: C:\Program Files (x86)\Qualcomm\QPST\bin
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: prog_emmc_firehose_Sm6125_ddr.elf
18:15:01: Requested ID 13, file: "C:\Program Files (x86)\Qualcomm\QPST\bin\prog_emmc_firehose_Sm6125_ddr.elf"
18:15:01: 591740 bytes transferred in 0.125000 seconds (4.5146MBps)
18:15:01: File transferred successfully
18:15:01: Sahara protocol completed
C:\Program Files (x86)\Qualcomm\QPST\bin>fh_loader.exe --port=\\.\COM40 --sendxml=reboot.xml --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
Base Version: 19.06.10.18.44
Binary build date: Jun 25 2019 @ 03:16:10
Incremental Build version: 19.06.25.03.16.10
18:15:07: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
fh_loader.exe --port=\\.\COM40 --sendxml=reboot.xml --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
18:15:07: INFO: Current working dir (cwd): C:\Program Files (x86)\Qualcomm\QPST\bin\
18:15:07: INFO: Showing network mappings to allow debugging
18:15:07: INFO:
18:15:07: INFO: Trying to store 'reboot.xml' in string table
18:15:07: INFO: Looking for file 'reboot.xml'
18:15:07: INFO: User wants to talk to port '\\.\COM40'
18:15:07: INFO: Took 0.00000000 seconds to open port
18:15:07: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
18:15:07: INFO: Sending <configure>
18:15:07: INFO: TARGET SAID: 'INFO: Binary build date: Jul 3 2019 @ 22:23:56'
18:15:07: INFO: TARGET SAID: 'INFO: Binary build date: Jul 3 2019 @ 22:23:56
'
18:15:07: INFO: TARGET SAID: 'INFO: Chip serial num: 570422912 (0x21fff680)'
18:15:07: INFO: TARGET SAID: 'INFO: Supported Functions (14):'
18:15:07: INFO: TARGET SAID: 'INFO: program'
18:15:07: INFO: TARGET SAID: 'INFO: read'
18:15:07: INFO: TARGET SAID: 'INFO: nop'
18:15:07: INFO: TARGET SAID: 'INFO: patch'
18:15:07: INFO: TARGET SAID: 'INFO: configure'
18:15:07: INFO: TARGET SAID: 'INFO: setbootablestoragedrive'
18:15:07: INFO: TARGET SAID: 'INFO: erase'
18:15:07: INFO: TARGET SAID: 'INFO: power'
18:15:07: INFO: TARGET SAID: 'INFO: firmwarewrite'
18:15:07: INFO: TARGET SAID: 'INFO: getstorageinfo'
18:15:07: INFO: TARGET SAID: 'INFO: benchmark'
18:15:07: INFO: TARGET SAID: 'INFO: emmc'
18:15:07: INFO: TARGET SAID: 'INFO: ufs'
18:15:07: INFO: TARGET SAID: 'INFO: fixgpt'
18:15:07: INFO: TARGET SAID: 'INFO: End of supported functions 14'
18:15:07: INFO: TARGET SAID: 'INFO: Calling handler for configure'
18:15:07: INFO: TARGET SAID: 'INFO: Storage type set to value eMMC'
18:15:07: INFO: TARGET SAID: 'WARN: NAK: MaxPayloadSizeToTargetInBytes sent by host 1048576 larger than supported 16384'
18:15:07: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 16384
18:15:07: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 16384
18:15:07: INFO: Target returned NAK for your <configure> but it does not seem to be an error. This is ok, fh_loader.exe attributes updated
Send RESET to target with DelayInSeconds="2" ? (y|n):y
18:15:10: INFO: Sending <power>
18:15:10: INFO: TARGET SAID: 'INFO: Calling handler for power'
18:15:10: INFO: ==============================================================
18:15:10: INFO: Files used and their paths
18:15:10: INFO: 1 'C:\Program Files (x86)\Qualcomm\QPST\bin\port_trace.txt'
18:15:10: INFO: 2 'C:\Program Files (x86)\Qualcomm\QPST\bin\reboot.xml'
18:15:10: INFO: _ (done)
18:15:10: INFO: | |
18:15:10: INFO: __| | ___ _ __ ___
18:15:10: INFO: / _` |/ _ \| '_ \ / _ \
18:15:10: INFO: | (_| | (_) | | | | __/
18:15:10: INFO: \__,_|\___/|_| |_|\___|
18:15:10: INFO: {All Finished Successfully}
18:15:10: INFO: Overall to target 2.922 seconds (0.00 Bps)
Writing log to 'C:\Program Files (x86)\Qualcomm\QPST\bin\port_trace.txt', might take a minute
Log is 'C:\Program Files (x86)\Qualcomm\QPST\bin\port_trace.txt'

Sudden Death of Black Screen

Dear Developers.
A year ago, my Wileyfox Swift device, which was turned off and connected to the cable to charge, did not turn on when I checked again.
On the grounds that the problem is not in the hardware, an attempt was made to install a rom on the phone with different software download systems, but it was unsuccessful.
Right now, when trying to install ROM on the phone, it gives the following error.
Code:
Programmer Path:<Maincode>\prog_emmc_firehose_8916.mbn
Start Download
Program Path:<Maincode>\prog_emmc_firehose_8916.mbn
***** Working Folder:<AppData>\Roaming\Qualcomm\QFIL\COMPORT_3
Binary build date: Oct 31 2016 @ 22:51:05
QSAHARASERVER CALLED LIKE THIS: '<Program Files (x86)>\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: <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: <Maincode>\prog_emmc_firehose_8916.mbn
15:44:30: <Maincode>\prog_emmc_firehose_8916.mbn"
15:44:30: 85224 bytes transferred in 0.063000 seconds (1.2901MBps)
15:44:30: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
15:44:30: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:16384 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
***** Working Folder:<AppData>\Roaming\Qualcomm\QFIL\COMPORT_3
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
15:44:35: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
<Program Files (x86)>\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM3 --sendxml=rawprogram_unsparse.xml --search_path=<Maincode> --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
15:44:35: INFO: Current working dir (cwd): <AppData>\Roaming\Qualcomm\QFIL\COMPORT_3\
15:44:35: INFO: Showing network mappings to allow debugging
15:44:37: INFO:
15:44:37: INFO: Trying to store 'rawprogram_unsparse.xml' in string table
15:44:37: INFO: Looking for file 'rawprogram_unsparse.xml'
15:44:39: INFO: User wants to talk to port '\\.\COM3'
15:44:39: INFO: Took 0.00000000 seconds to open port
15:44:39: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
15:44:39: INFO: If you don't want this, use --dontsorttags
15:44:39: INFO: Looking for file 'sbl1.mbn'
15:44:39: INFO: Looking for file 'sbl1.mbn'
15:44:39: INFO: Looking for file 'emmc_appsboot.mbn'
15:44:39: INFO: Looking for file 'emmc_appsboot.mbn'
15:44:39: INFO: Looking for file 'rpm.mbn'
15:44:39: INFO: Looking for file 'rpm.mbn'
15:44:39: INFO: Looking for file 'tz.mbn'
15:44:39: INFO: Looking for file 'tz.mbn'
15:44:39: INFO: Looking for file 'hyp.mbn'
15:44:39: INFO: Looking for file 'hyp.mbn'
15:44:39: INFO: Looking for file 'devinfo.bin'
15:44:39: INFO: Looking for file 'dummy.bin'
15:44:39: INFO: Looking for file 'dummy.bin'
15:44:39: INFO: Looking for file 'misc.img'
15:44:39: INFO: Looking for file 'splash.img'
15:44:39: INFO: Looking for file 'oem_1.img'
15:44:40: INFO: Looking for file 'NON-HLOS.bin'
15:44:40: INFO: Looking for file 'fs_image.tar.gz.mbn.img'
15:44:40: INFO: Looking for file 'sec.dat'
15:44:40: INFO: Looking for file 'boot.img'
15:44:40: INFO: Looking for file 'system_1.img'
15:44:40: INFO: Looking for file 'system_2.img'
15:44:40: INFO: Looking for file 'system_3.img'
15:44:40: INFO: Looking for file 'system_4.img'
15:44:40: INFO: Looking for file 'system_5.img'
15:44:40: INFO: Looking for file 'system_6.img'
15:44:40: INFO: Looking for file 'system_7.img'
15:44:40: INFO: Looking for file 'system_8.img'
15:44:41: INFO: Looking for file 'system_9.img'
15:44:41: INFO: Looking for file 'system_10.img'
15:44:41: INFO: Looking for file 'system_11.img'
15:44:41: INFO: Looking for file 'system_12.img'
15:44:41: INFO: Looking for file 'system_13.img'
15:44:41: INFO: Looking for file 'system_14.img'
15:44:41: INFO: Looking for file 'system_15.img'
15:44:41: INFO: Looking for file 'system_16.img'
15:44:41: INFO: Looking for file 'system_17.img'
15:44:41: INFO: Looking for file 'system_18.img'
15:44:41: INFO: Looking for file 'system_19.img'
15:44:41: INFO: Looking for file 'system_20.img'
15:44:41: INFO: Looking for file 'system_21.img'
15:44:41: INFO: Looking for file 'recovery.img'
15:44:41: INFO: Looking for file 'persist_1.img'
15:44:41: INFO: Looking for file 'cache_1.img'
15:44:41: INFO: Looking for file 'cache_2.img'
15:44:41: INFO: Looking for file 'cache_3.img'
15:44:41: INFO: Looking for file 'cache_4.img'
15:44:41: INFO: Looking for file 'userdata_1.img'
15:44:42: INFO: Looking for file 'userdata_2.img'
15:44:42: INFO: Looking for file 'userdata_3.img'
15:44:42: INFO: Looking for file 'userdata_4.img'
15:44:42: INFO: Looking for file 'userdata_5.img'
15:44:42: INFO: Looking for file 'userdata_6.img'
15:44:42: INFO: Looking for file 'userdata_7.img'
15:44:42: INFO: Looking for file 'userdata_8.img'
15:44:42: INFO: Looking for file 'userdata_9.img'
15:44:42: INFO: Looking for file 'userdata_10.img'
15:44:42: INFO: Looking for file 'userdata_11.img'
15:44:42: INFO: Looking for file 'userdata_12.img'
15:44:42: INFO: Looking for file 'userdata_13.img'
15:44:42: INFO: Looking for file 'userdata_14.img'
15:44:42: INFO: Looking for file 'userdata_15.img'
15:44:42: INFO: Looking for file 'userdata_16.img'
15:44:42: INFO: Looking for file 'userdata_17.img'
15:44:42: INFO: Looking for file 'userdata_18.img'
15:44:42: INFO: Looking for file 'userdata_19.img'
15:44:42: INFO: Looking for file 'userdata_20.img'
15:44:42: INFO: Looking for file 'userdata_21.img'
15:44:42: INFO: Looking for file 'userdata_22.img'
15:44:42: INFO: Looking for file 'userdata_23.img'
15:44:42: INFO: Looking for file 'userdata_24.img'
15:44:42: INFO: Looking for file 'userdata_25.img'
15:44:42: INFO: Looking for file 'userdata_26.img'
15:44:42: INFO: Looking for file 'userdata_27.img'
15:44:42: INFO: Looking for file 'userdata_28.img'
15:44:42: INFO: Looking for file 'userdata_29.img'
15:44:42: INFO: Looking for file 'userdata_30.img'
15:44:42: INFO: Looking for file 'userdata_31.img'
15:44:42: INFO: Looking for file 'userdata_32.img'
15:44:42: INFO: Looking for file 'userdata_33.img'
15:44:42: INFO: Looking for file 'userdata_34.img'
15:44:42: INFO: Looking for file 'userdata_35.img'
15:44:42: INFO: Looking for file 'userdata_36.img'
15:44:42: INFO: Looking for file 'userdata_37.img'
15:44:42: INFO: Looking for file 'userdata_38.img'
15:44:42: INFO: Looking for file 'userdata_39.img'
15:44:42: INFO: Looking for file 'userdata_40.img'
15:44:42: INFO: Looking for file 'userdata_41.img'
15:44:42: INFO: Looking for file 'userdata_42.img'
15:44:42: INFO: Looking for file 'userdata_43.img'
15:44:42: INFO: Looking for file 'userdata_44.img'
15:44:42: INFO: Looking for file 'userdata_45.img'
15:44:42: INFO: Looking for file 'userdata_46.img'
15:44:42: INFO: Looking for file 'userdata_47.img'
15:44:42: INFO: Looking for file 'userdata_48.img'
15:44:42: INFO: Looking for file 'userdata_49.img'
15:44:43: INFO: Looking for file 'gpt_main0.bin'
15:44:43: INFO: Looking for file 'gpt_backup0.bin'
15:44:43: INFO:
Total to be tansferd with <program> or <read> is 673.85 MB
15:44:43: INFO: Sending <configure>
15:44:43: INFO: TARGET SAID: 'Host's payload to target size is too large'
15:44:43: INFO: TARGET SAID: '[email protected] [email protected]'
15:44:43: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 16384
15:44:43: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 16384
15:44:43: INFO: Target returned NAK for your <configure> but it does not seem to be an error. This is ok, fh_loader.exe attributes updated
15:44:43: INFO: In handleProgram('sbl1.mbn')
15:44:43: INFO: Looking for file 'sbl1.mbn'
15:44:43: INFO: =======================================================
15:44:43: INFO: {<program> FILE: '<Maincode>\sbl1.mbn'}
15:44:43: INFO: {<program> (247.07 KB) 495 sectors needed at location 131072 on LUN 0}
15:44:43: INFO: =======================================================
15:44:43: INFO: TARGET SAID: '[email protected] [email protected]'
15:44:43: INFO: TARGET SAID: 'start 131072, num 495'
15:44:43: INFO: FILE ACCESS SLOW!! 247.50 KB in 0.015 seconds ( 16.11 MBps) --- Overall to target 0.047 seconds (5.14 MBps)
15:44:43: INFO: {percent files transferred 0.04%}
15:44:43: INFO: TARGET SAID: 'Write failed Sector 131072, Errno 14'
15:44:43: INFO: TARGET SAID: 'Finished sector address 131072'
Download Fail: FireHose Fail: FHLoader Fail: Process fail
Finish Download
Of course the device does not respond at all with key combinations. There is also no response on Get Flash Information from device with software other than Qualcomm Flash Image software.
Can you help on the subject? Thank you in advance!
***
Some useful information.
* Serial code and OEM Hash Pack Locks can readable.
* It gives No Storage Drive Number error in Partition Manager operation.
* Device shows itself as MSM8909.

Develop Bugs

welcome