• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[GUIDE] How to unbrick LG L Fino from Qualcomm 9008 & LGE AndroidNet mode!

Did this worked for you?


  • Total voters
    29
Search This thread

juniopms

Member
Nov 17, 2009
8
1
São Paulo
Read back verify failed at sector

I tried several times but it did not work

Start Download
Program Path:E:\LG Unbrick Tools\D295F UNBRICK\prog_emmc_firehose_8x10.mbn
COM Port number:23
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
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
COM Port number:23
Sending NOP
FireHose NOP sent successfully
Sending Configuration
Device Type:eMMC
Platform:8x26
Set TxBuffer 0xc000, RxBuffer 0x4000
Firehose configure packet sent successfully!
ReadBackMode:No_Readback
Disable read back
Fim de arquivo inesperado. Os seguintes elementos não estão fechados: xml. Linha 37, posição 1.
Download Image
PROGRAM: Partition 0, Sector: 0, Length: 1024 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\PrimaryGPT_0.bin
FireHose Log: start 0, num 1024
FireHose Log: Finished sector address 1024
PROGRAM: Written Bytes 0x80000 (64)
Program Size: 0.50 MB
PROGRAM: Partition 0, Sector: 8192, Length: 67584 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\modem_8192.bin
FireHose Log: start 8192, num 67584
FireHose Log: Finished sector address 75776
PROGRAM: Written Bytes 0x2100000 (64)
Program Size: 33.00 MB
PROGRAM: Partition 0, Sector: 139264, Length: 1024 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\sbl1_139264.bin
FireHose Log: start 139264, num 1024
FireHose Log: Finished sector address 140288
PROGRAM: Written Bytes 0x80000 (64)
Program Size: 0.50 MB
PROGRAM: Partition 0, Sector: 141312, Length: 1024 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\rpm_141312.bin
FireHose Log: start 141312, num 1024
FireHose Log: Finished sector address 142336
PROGRAM: Written Bytes 0x80000 (64)
Program Size: 0.50 MB
PROGRAM: Partition 0, Sector: 142336, Length: 1024 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\tz_142336.bin
FireHose Log: start 142336, num 1024
FireHose Log: Finished sector address 143360
PROGRAM: Written Bytes 0x80000 (64)
Program Size: 0.50 MB
PROGRAM: Partition 0, Sector: 143360, Length: 1024 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\sdi_143360.bin
FireHose Log: start 143360, num 1024
FireHose Log: Finished sector address 144384
PROGRAM: Written Bytes 0x80000 (64)
Program Size: 0.50 MB
PROGRAM: Partition 0, Sector: 144384, Length: 2048 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\aboot_144384.bin
FireHose Log: start 144384, num 2048
FireHose Log: Finished sector address 146432
PROGRAM: Written Bytes 0x100000 (64)
Program Size: 1.00 MB
PROGRAM: Partition 0, Sector: 148480, Length: 1024 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\rpmb_148480.bin
FireHose Log: start 148480, num 1024
FireHose Log: Finished sector address 149504
PROGRAM: Written Bytes 0x80000 (64)
Program Size: 0.50 MB
PROGRAM: Partition 0, Sector: 149504, Length: 1024 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\tzb_149504.bin
FireHose Log: start 149504, num 1024
FireHose Log: Finished sector address 150528
PROGRAM: Written Bytes 0x80000 (64)
Program Size: 0.50 MB
PROGRAM: Partition 0, Sector: 150528, Length: 2048 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\abootb_150528.bin
FireHose Log: start 150528, num 2048
FireHose Log: Finished sector address 152576
PROGRAM: Written Bytes 0x100000 (64)
Program Size: 1.00 MB
PROGRAM: Partition 0, Sector: 204800, Length: 10240 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\persist_204800.bin
FireHose Log: start 204800, num 10240
FireHose Log: Finished sector address 215040
PROGRAM: Written Bytes 0x500000 (64)
Program Size: 5.00 MB
PROGRAM: Partition 0, Sector: 270336, Length: 30720 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\laf_270336.bin
FireHose Log: start 270336, num 30720
FireHose Log: Finished sector address 301056
PROGRAM: Written Bytes 0xf00000 (64)
Program Size: 15.00 MB
PROGRAM: Partition 0, Sector: 319488, Length: 18432 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\boot_319488.bin
FireHose Log: start 319488, num 18432
FireHose Log: Finished sector address 337920
PROGRAM: Written Bytes 0x900000 (64)
Program Size: 9.00 MB
PROGRAM: Partition 0, Sector: 364544, Length: 20480 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\recovery_364544.bin
FireHose Log: start 364544, num 20480
FireHose Log: Finished sector address 385024
PROGRAM: Written Bytes 0xa00000 (64)
Program Size: 10.00 MB
PROGRAM: Partition 0, Sector: 475136, Length: 23552 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\factory_475136.bin
FireHose Log: start 475136, num 23552
FireHose Log: Finished sector address 498688
PROGRAM: Written Bytes 0xb80000 (64)
Program Size: 11.50 MB
PROGRAM: Partition 0, Sector: 581632, Length: 1024 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\sbl1b_581632.bin
FireHose Log: start 581632, num 1024
FireHose Log: Finished sector address 582656
PROGRAM: Written Bytes 0x80000 (64)
Program Size: 0.50 MB
PROGRAM: Partition 0, Sector: 655360, Length: 17408 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\cust_655360.bin
FireHose Log: start 655360, num 17408
FireHose Log: Finished sector address 672768
PROGRAM: Written Bytes 0x880000 (64)
Program Size: 8.50 MB
PROGRAM: Partition 0, Sector: 770048, Length: 263168 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\system_770048.bin
FireHose Log: start 770048, num 263168
FireHose Log: Finished sector address 1033216
PROGRAM: Written Bytes 0x8080000 (64)
Program Size: 128.50 MB
PROGRAM: Partition 0, Sector: 1036984, Length: 258048 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\system_1036984.bin
FireHose Log: start 1036984, num 258048
FireHose Log: Read back verify failed at sector 1990951131,num sectors 1036984
FireHose Log: Finished sector address 1036984
PROGRAM: Written Bytes 0x7e00000 (64)
Program Size: 126.00 MB
PROGRAM: Partition 0, Sector: 1298352, Length: 259072 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\system_1298352.bin
FireHose Log: start 1298352, num 259072
FireHose Log: Read back verify failed at sector 1078186316,num sectors 1298352
FireHose Log: Finished sector address 1298352
PROGRAM: Written Bytes 0x7e80000 (64)
Program Size: 126.50 MB
PROGRAM: Partition 0, Sector: 1561272, Length: 258048 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\system_1561272.bin
FireHose Log: start 1561272, num 258048
FireHose Log: Read back verify failed at sector -181514164,num sectors 1561272
FireHose Log: Finished sector address 1561272
PROGRAM: Written Bytes 0x7e00000 (64)
Program Size: 126.00 MB
PROGRAM: Partition 0, Sector: 1822640, Length: 259072 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\system_1822640.bin
FireHose Log: start 1822640, num 259072
FireHose Log: Read back verify failed at sector -1582530653,num sectors 1822640
FireHose Log: Finished sector address 1822640
PROGRAM: Written Bytes 0x7e80000 (64)
Program Size: 126.50 MB
PROGRAM: Partition 0, Sector: 2085560, Length: 258048 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\system_2085560.bin
FireHose Log: start 2085560, num 258048
FireHose Log: Read back verify failed at sector 533166350,num sectors 2085560
FireHose Log: Finished sector address 2085560
PROGRAM: Written Bytes 0x7e00000 (64)
Program Size: 126.00 MB
PROGRAM: Partition 0, Sector: 2346928, Length: 259072 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\system_2346928.bin
FireHose Log: start 2346928, num 259072
FireHose Log: Read back verify failed at sector 1300209030,num sectors 2346928
FireHose Log: Finished sector address 2346928
PROGRAM: Written Bytes 0x7e80000 (64)
Program Size: 126.50 MB
PROGRAM: Partition 0, Sector: 2609848, Length: 258048 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\system_2609848.bin
FireHose Log: start 2609848, num 258048
FireHose Log: Read back verify failed at sector -1971928944,num sectors 2609848
FireHose Log: Finished sector address 2609848
PROGRAM: Written Bytes 0x7e00000 (64)
Program Size: 126.00 MB
PROGRAM: Partition 0, Sector: 2871216, Length: 259072 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\system_2871216.bin
FireHose Log: start 2871216, num 259072
FireHose Log: Read back verify failed at sector 1817658694,num sectors 2871216
FireHose Log: Finished sector address 2871216
PROGRAM: Written Bytes 0x7e80000 (64)
Program Size: 126.50 MB
PROGRAM: Partition 0, Sector: 3134136, Length: 258048 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\system_3134136.bin
FireHose Log: start 3134136, num 258048
FireHose Log: Read back verify failed at sector -902669599,num sectors 3134136
FireHose Log: Finished sector address 3134136
PROGRAM: Written Bytes 0x7e00000 (64)
Program Size: 126.00 MB
PROGRAM: Partition 0, Sector: 3395504, Length: 253952 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\system_3395504.bin
FireHose Log: start 3395504, num 253952
FireHose Log: Read back verify failed at sector -846644525,num sectors 3395504
FireHose Log: Finished sector address 3395504
PROGRAM: Written Bytes 0x7c00000 (64)
Program Size: 124.00 MB
PROGRAM: Partition 0, Sector: 3653632, Length: 1024 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\system_3653632.bin
FireHose Log: start 3653632, num 1024
FireHose Log: Read back verify failed at sector 2037061107,num sectors 3653632
FireHose Log: Finished sector address 3653632
PROGRAM: Written Bytes 0x80000 (64)
Program Size: 0.50 MB
PROGRAM: Partition 0, Sector: 7633920, Length: 1024 Sectors, Sector Size: 512 Bytes
File: E:\LG Unbrick Tools\D295F UNBRICK\BackupGPT_7633920.bin
FireHose Log: start 7633920, num 1024
FireHose Log: Read back verify failed at sector 381093650,num sectors 7633920
FireHose Log: Finished sector address 7633920
PROGRAM: Written Bytes 0x80000 (64)
Program Size: 0.50 MB
Total Size: 1487.50 MB
Total Time: 75 Seconds
Throughput: 19.83 MB/Seconds
Total download file size: 1487,5MB
Total download time: 1 Min 15 Sec
Throughput: 19,81964MB/s
FireHose Log: Set bootable drive to 0.
Reset Phone
Waiting for reset done...
Download Succeed
Finish Download
 

SkEvol

Member
Sep 7, 2012
44
6
Fixing an LG 295 here..

A general comment about fixing the LF lfie phones... ---they seem uncommon.
A lot of the fix it videos on youtube are in non-english language. - this phone is more popular in asia?
Fixing this does seem to be a nightmare.

MY PROBLEM:
I'm stuck at 'DEMIGOD CRASH HANDLER: DBI APPS WATCHDOG RESET' screen

I thknk it almost goes without saying that the phone is not showing up in windows explorer. (incidentally, Win7, 32bit here), admin account.

I've followed all the steps up until STEP 8, the guide suggests you click the DOWNLOAD button.
-- big problem, for me...... the DOWNLOAD button is unclicklable (it is 'greyed-out' esssentailly)

a quick SEARCH on this thread for 'DOWNLOAD' shows no results --- one guy mentioned he got stuck on step 8 also, but his query was never answered.

----So what do I do guys?

again, for the record, I've got an LG D295, I'm using the D295 unbrick files, I've installed QPST 2.7.347
 

not_sahil

Member
Oct 6, 2017
11
0
Hi/Cześć

I have an problem i tried to reflash my Fino like an 200 times already still getting :

22:16:44: ERROR: function: is_ack_successful:943 SAHARA_NAK_INVALID_IMAGE_TYPE
22:16:44: ERROR: function: sahara_start:825 Exiting abruptly
22:16:44: ERROR: function: sahara_main:854 Sahara protocol error
22:16:44: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail:process fail
Finish Download


Any ideas please help me :(

Dude You Found Any Solution?
I'm Getting Same Error
 

Elavarasan01

Member
Apr 25, 2016
7
0
Same problem bro

22kCBmq.png
I tried to do what the instructions say, but when I try to press the "download" button, it doesn't let me, because of no port selected. when i select a port (wich is the one my lg is connected) it let's me download but gives me "failed to switch to emergency download mode"

---------- Post added at 23:41 ---------- Previous post was at 23:15 ----------

Also when i plug in my phone, it installs a "relink hs-usb qdloader 9008" driver, how do I prevent this?


How did you solved that error bro please tell me
 

Attachments

  • _20171022_120718.JPG
    _20171022_120718.JPG
    63.8 KB · Views: 240

Elavarasan01

Member
Apr 25, 2016
7
0
Same problem bro

Mine is LG d295F but windows isn't detecting as "qualcomm..." its only showing "LG Androidnet USB Serial Port"


When I try to use this on QIFL, give an error "Start Download
COM Port number:12
Switch To EDL
Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode
Finish Download"



Sorry, Bad english i'm Brazilian <3


Here too same problem bro how did you solved that error please tell me bro help me iam waiting
 

Attachments

  • _20171022_120718.JPG
    _20171022_120718.JPG
    63.8 KB · Views: 82

Elavarasan01

Member
Apr 25, 2016
7
0
For all that have error with "Emergency MODE"!!

If you have phone showing as 4GB drive try format it and delete partition via EaseUS Partition Master!

Bro in easy use partition mater it is showing as unallocated drive but in the computer disk manager it is showing as many partition bro what to do now please tell bro wait for your reply. I attached the screen shot bro please check that
 

Attachments

  • _20171022_130734.JPG
    _20171022_130734.JPG
    135 KB · Views: 338
  • _20171022_130810.JPG
    _20171022_130810.JPG
    79.1 KB · Views: 334

DavRei

Senior Member
Nov 3, 2016
52
21
Chełmno
I can't unbrick my LG L Fino anymore. I have "Read back verify failed" error as few users from this topic. I now have a something that I can work at. Hope I'll do it so you'll can do it too
 
Last edited:

dukatino

New member
Jan 12, 2018
2
0
22:44:19: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM12 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=eMMC --setactivepartition=0
************************************************

22:44:19: DEBUG: Binary build date: Jun 3 2015 @ 17:12:06

22:44:19: DEBUG: Build Version: 15.06. 3.17.12.06

22:44:19: INFO: Current working dir (cwd): C:\Users\Zahid\AppData\Roaming\Qualcomm\QFIL\
22:44:19: INFO: Showing network mappings to allow debugging
22:44:19: DEBUG: New connections will be remembered.

22:44:19: DEBUG:

22:44:19: DEBUG: There are no entries in the list.

22:44:19: DEBUG:

22:44:20: DEBUG: User set ZLPAWAREHOST to 1

22:44:20: INFO: User wants to talk to port '\\.\COM12'
22:44:20: DEBUG: port_fd=0x4C

22:44:20: INFO: Took 0.01600000 seconds to open port
22:44:20: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
22:44:20: INFO: If you don't want this, use --dontsorttags

22:44:20: INFO: Sending <configure>
22:44:20: DEBUG: CHANNEL DATA (P0000) (H00202) ( 246 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" TargetName="8960" />
</data>

============================================================================================================

22:44:20: DEBUG: CharsInBuffer=0 Trying to read from USB 8192 bytes
22:44:20: DEBUG: CHANNEL DATA (407 bytes) <-- TARGET to HOST
22:44:20: DEBUG: CharsInBuffer = 407
22:44:20: DEBUG: printBuffer:4243 PRETTYPRINT Buffer is 407 bytes

22:44:20: DEBUG: printBuffer:4320 3C 3F 78 6D 6C 20 76 65 72 73 69 6F 6E 3D 22 31 <?xml version="1
22:44:20: DEBUG: printBuffer:4320 2E 30 22 20 65 6E 63 6F 64 69 6E 67 3D 22 55 54 .0" encoding="UT
22:44:20: DEBUG: printBuffer:4320 46 2D 38 22 20 3F 3E 3C 64 61 74 61 3E 3C 6C 6F F-8" ?><data><lo
22:44:20: DEBUG: printBuffer:4320 67 20 76 61 6C 75 65 3D 22 48 6F 73 74 27 73 20 g value="Host's
22:44:20: DEBUG: printBuffer:4320 70 61 79 6C 6F 61 64 20 74 6F 20 74 61 72 67 65 payload to targe
22:44:20: DEBUG: printBuffer:4320 74 20 73 69 7A 65 20 69 73 20 74 6F 6F 20 6C 61 t size is too la
22:44:20: DEBUG: printBuffer:4320 72 67 65 22 20 2F 3E 3C 2F 64 61 74 61 3E 3C 3F rge" /></data><?
22:44:20: DEBUG: printBuffer:4320 78 6D 6C 20 76 65 72 73 69 6F 6E 3D 22 31 2E 30 xml version="1.0
22:44:20: DEBUG: printBuffer:4320 22 20 65 6E 63 6F 64 69 6E 67 3D 22 55 54 46 2D " encoding="UTF-
22:44:20: DEBUG: printBuffer:4320 38 22 20 3F 3E 3C 64 61 74 61 3E 3C 72 65 73 70 8" ?><data><resp
22:44:20: DEBUG: printBuffer:4320 6F 6E 73 65 20 76 61 6C 75 65 3D 22 4E 41 4B 22 onse value="NAK"
22:44:20: DEBUG: printBuffer:4320 20 4D 69 6E 56 65 72 73 69 6F 6E 53 75 70 70 6F MinVersionSuppo
22:44:20: DEBUG: printBuffer:4320 72 74 65 64 3D 22 31 22 20 4D 65 6D 6F 72 79 4E rted="1" MemoryN
22:44:20: DEBUG: printBuffer:4320 61 6D 65 3D 22 65 4D 4D 43 22 20 4D 61 78 50 61 ame="eMMC" MaxPa
22:44:20: DEBUG: printBuffer:4320 79 6C 6F 61 64 53 69 7A 65 46 72 6F 6D 54 61 72 yloadSizeFromTar
22:44:20: DEBUG: printBuffer:4320 67 65 74 49 6E 42 79 74 65 73 3D 22 34 30 39 36 getInBytes="4096
22:44:20: DEBUG: printBuffer:4320 22 20 4D 61 78 50 61 79 6C 6F 61 64 53 69 7A 65 " MaxPayloadSize
22:44:20: DEBUG: printBuffer:4320 54 6F 54 61 72 67 65 74 49 6E 42 79 74 65 73 3D ToTargetInBytes=
22:44:20: DEBUG: printBuffer:4320 22 34 39 31 35 32 22 20 4D 61 78 50 61 79 6C 6F "49152" MaxPaylo
22:44:20: DEBUG: printBuffer:4320 61 64 53 69 7A 65 54 6F 54 61 72 67 65 74 49 6E adSizeToTargetIn
22:44:20: DEBUG: printBuffer:4320 42 79 74 65 73 53 75 70 70 6F 72 74 65 64 3D 22 BytesSupported="
22:44:20: DEBUG: printBuffer:4320 34 39 31 35 32 22 20 4D 61 78 58 4D 4C 53 69 7A 49152" MaxXMLSiz
22:44:20: DEBUG: printBuffer:4320 65 49 6E 42 79 74 65 73 3D 22 34 30 39 36 22 20 eInBytes="4096"
22:44:20: DEBUG: printBuffer:4320 56 65 72 73 69 6F 6E 3D 22 31 22 20 54 61 72 67 Version="1" Targ
22:44:20: DEBUG: printBuffer:4320 65 74 4E 61 6D 65 3D 22 38 78 31 30 22 20 2F 3E etName="8x10" />
22:44:20: DEBUG: printBuffer:4320 3C 2F 64 61 74 61 3E </data>
22:44:20: DEBUG: printBuffer:4333


22:44:20: DEBUG: XML FILE (110 bytes): CharsInBuffer=407-110=297
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Host's payload to target size is too large" /></data>
-------------------------------------------------------------------------------------------

22:44:20: INFO: TARGET SAID: 'Host's payload to target size is too large'
22:44:20: DEBUG: XML FILE (297 bytes): CharsInBuffer=297-297=0
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?><data><response value="NAK" MinVersionSupported="1" MemoryName="eMMC" MaxPayloadSizeFromTargetInBytes="4096" MaxPayloadSizeToTargetInBytes="49152" MaxPayloadSizeToTargetInBytesSupported="49152" MaxXMLSizeInBytes="4096" Version="1" TargetName="8x10" /></data>
-------------------------------------------------------------------------------------------

22:44:20: DEBUG: Response was 'NAK'
22:44:20: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 49152
22:44:20: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 49152
22:44:20: INFO: Target returned NAK for your <configure> but it does not seem to be an error. This is ok, fh_loader.exe attributes updated
22:44:20: INFO: Sending <setbootablestoragedrive>
22:44:20: DEBUG: CHANNEL DATA (P0001) (H00203) ( 93 bytes) - HOST TO TARGET -->
===========================================================================================================
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<setbootablestoragedrive value="0" />
</data>

============================================================================================================

22:44:20: DEBUG: CharsInBuffer=0 Trying to read from USB 4096 bytes
22:44:20: DEBUG: CHANNEL DATA (168 bytes) <-- TARGET to HOST
22:44:20: DEBUG: CharsInBuffer = 168
22:44:20: DEBUG: printBuffer:4243 PRETTYPRINT Buffer is 168 bytes

22:44:20: DEBUG: printBuffer:4320 3C 3F 78 6D 6C 20 76 65 72 73 69 6F 6E 3D 22 31 <?xml version="1
22:44:20: DEBUG: printBuffer:4320 2E 30 22 20 65 6E 63 6F 64 69 6E 67 3D 22 55 54 .0" encoding="UT
22:44:20: DEBUG: printBuffer:4320 46 2D 38 22 20 3F 3E 3C 64 61 74 61 3E 3C 6C 6F F-8" ?><data><lo
22:44:20: DEBUG: printBuffer:4320 67 20 76 61 6C 75 65 3D 22 53 65 74 20 62 6F 6F g value="Set boo
22:44:20: DEBUG: printBuffer:4320 74 61 62 6C 65 20 64 72 69 76 65 20 74 6F 20 30 table drive to 0
22:44:20: DEBUG: printBuffer:4320 2E 22 20 2F 3E 3C 2F 64 61 74 61 3E 3C 3F 78 6D ." /></data><?xm
22:44:20: DEBUG: printBuffer:4320 6C 20 76 65 72 73 69 6F 6E 3D 22 31 2E 30 22 20 l version="1.0"
22:44:20: DEBUG: printBuffer:4320 65 6E 63 6F 64 69 6E 67 3D 22 55 54 46 2D 38 22 encoding="UTF-8"
22:44:20: DEBUG: printBuffer:4320 20 3F 3E 3C 64 61 74 61 3E 3C 72 65 73 70 6F 6E ?><data><respon
22:44:20: DEBUG: printBuffer:4320 73 65 20 76 61 6C 75 65 3D 22 41 43 4B 22 20 2F se value="ACK" /
22:44:20: DEBUG: printBuffer:4320 3E 3C 2F 64 61 74 61 3E ></data>
22:44:20: DEBUG: printBuffer:4333


22:44:20: DEBUG: XML FILE (92 bytes): CharsInBuffer=168-92=76
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Set bootable drive to 0." /></data>
-------------------------------------------------------------------------------------------

22:44:20: INFO: TARGET SAID: 'Set bootable drive to 0.'
22:44:20: DEBUG: XML FILE (76 bytes): CharsInBuffer=76-76=0
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" /></data>
-------------------------------------------------------------------------------------------

22:44:20: DEBUG: Response was 'ACK'
22:44:20: DEBUG: Got the ACK
22:44:20: INFO: ==============================================================
22:44:20: INFO: Files used and their paths
22:44:20: INFO: 1 'C:\Users\Zahid\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
22:44:20: INFO: _ (done)
22:44:20: INFO: | |
22:44:20: INFO: __| | ___ _ __ ___
22:44:20: INFO: / _` |/ _ \| '_ \ / _ \
22:44:20: INFO: | (_| | (_) | | | | __/
22:44:20: INFO: \__,_|\___/|_| |_|\___|
22:44:20: INFO: {All Finished Successfully}

22:44:20: INFO: FILE ACCESS SLOW!! 0.00 B in 0.015 seconds ( 0.00 Bps) --- Overall to target 0.203 seconds (0.00 Bps)


++This is my log after installing, giving me few error logs,but install is finished 100% correctly. After that im still not able to turn on phone,still giving me that qualcom usb port and nothing else. Any solutions_
 

thecadaz

Member
Nov 16, 2016
10
0
I tried this method, but it ain't working for my d295. Followed all the steps, but all I get is error, error...

I've attached logs, if it's any help. Thanks
 

Attachments

  • 131641046391771408.rar
    5.7 KB · Views: 101

sunmartin

Member
Apr 18, 2015
7
0
isfahan
sahra error

22:44:19: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM12 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=eMMC --setactivepartition=0
************************************************

22:44:19: DEBUG: Binary build date: Jun 3 2015 @ 17:12:06

22:44:19: DEBUG: Build Version: 15.06. 3.17.12.06

22:44:19: INFO: Current working dir (cwd): C:\Users\Zahid\AppData\Roaming\Qualcomm\QFIL\
22:44:19: INFO: Showing network mappings to allow debugging
22:44:19: DEBUG: New connections will be remembered.

22:44:19: DEBUG:

22:44:19: DEBUG: There are no entries in the list.

22:44:19: DEBUG:

22:44:20: DEBUG: User set ZLPAWAREHOST to 1

22:44:20: INFO: User wants to talk to port '\\.\COM12'
22:44:20: DEBUG: port_fd=0x4C

22:44:20: INFO: Took 0.01600000 seconds to open port
22:44:20: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
22:44:20: INFO: If you don't want this, use --dontsorttags

22:44:20: INFO: Sending <configure>
22:44:20: DEBUG: CHANNEL DATA (P0000) (H00202) ( 246 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" TargetName="8960" />
</data>

============================================================================================================

22:44:20: DEBUG: CharsInBuffer=0 Trying to read from USB 8192 bytes
22:44:20: DEBUG: CHANNEL DATA (407 bytes) <-- TARGET to HOST
22:44:20: DEBUG: CharsInBuffer = 407
22:44:20: DEBUG: printBuffer:4243 PRETTYPRINT Buffer is 407 bytes

22:44:20: DEBUG: printBuffer:4320 3C 3F 78 6D 6C 20 76 65 72 73 69 6F 6E 3D 22 31 <?xml version="1
22:44:20: DEBUG: printBuffer:4320 2E 30 22 20 65 6E 63 6F 64 69 6E 67 3D 22 55 54 .0" encoding="UT
22:44:20: DEBUG: printBuffer:4320 46 2D 38 22 20 3F 3E 3C 64 61 74 61 3E 3C 6C 6F F-8" ?><data><lo
22:44:20: DEBUG: printBuffer:4320 67 20 76 61 6C 75 65 3D 22 48 6F 73 74 27 73 20 g value="Host's
22:44:20: DEBUG: printBuffer:4320 70 61 79 6C 6F 61 64 20 74 6F 20 74 61 72 67 65 payload to targe
22:44:20: DEBUG: printBuffer:4320 74 20 73 69 7A 65 20 69 73 20 74 6F 6F 20 6C 61 t size is too la
22:44:20: DEBUG: printBuffer:4320 72 67 65 22 20 2F 3E 3C 2F 64 61 74 61 3E 3C 3F rge" /></data><?
22:44:20: DEBUG: printBuffer:4320 78 6D 6C 20 76 65 72 73 69 6F 6E 3D 22 31 2E 30 xml version="1.0
22:44:20: DEBUG: printBuffer:4320 22 20 65 6E 63 6F 64 69 6E 67 3D 22 55 54 46 2D " encoding="UTF-
22:44:20: DEBUG: printBuffer:4320 38 22 20 3F 3E 3C 64 61 74 61 3E 3C 72 65 73 70 8" ?><data><resp
22:44:20: DEBUG: printBuffer:4320 6F 6E 73 65 20 76 61 6C 75 65 3D 22 4E 41 4B 22 onse value="NAK"
22:44:20: DEBUG: printBuffer:4320 20 4D 69 6E 56 65 72 73 69 6F 6E 53 75 70 70 6F MinVersionSuppo
22:44:20: DEBUG: printBuffer:4320 72 74 65 64 3D 22 31 22 20 4D 65 6D 6F 72 79 4E rted="1" MemoryN
22:44:20: DEBUG: printBuffer:4320 61 6D 65 3D 22 65 4D 4D 43 22 20 4D 61 78 50 61 ame="eMMC" MaxPa
22:44:20: DEBUG: printBuffer:4320 79 6C 6F 61 64 53 69 7A 65 46 72 6F 6D 54 61 72 yloadSizeFromTar
22:44:20: DEBUG: printBuffer:4320 67 65 74 49 6E 42 79 74 65 73 3D 22 34 30 39 36 getInBytes="4096
22:44:20: DEBUG: printBuffer:4320 22 20 4D 61 78 50 61 79 6C 6F 61 64 53 69 7A 65 " MaxPayloadSize
22:44:20: DEBUG: printBuffer:4320 54 6F 54 61 72 67 65 74 49 6E 42 79 74 65 73 3D ToTargetInBytes=
22:44:20: DEBUG: printBuffer:4320 22 34 39 31 35 32 22 20 4D 61 78 50 61 79 6C 6F "49152" MaxPaylo
22:44:20: DEBUG: printBuffer:4320 61 64 53 69 7A 65 54 6F 54 61 72 67 65 74 49 6E adSizeToTargetIn
22:44:20: DEBUG: printBuffer:4320 42 79 74 65 73 53 75 70 70 6F 72 74 65 64 3D 22 BytesSupported="
22:44:20: DEBUG: printBuffer:4320 34 39 31 35 32 22 20 4D 61 78 58 4D 4C 53 69 7A 49152" MaxXMLSiz
22:44:20: DEBUG: printBuffer:4320 65 49 6E 42 79 74 65 73 3D 22 34 30 39 36 22 20 eInBytes="4096"
22:44:20: DEBUG: printBuffer:4320 56 65 72 73 69 6F 6E 3D 22 31 22 20 54 61 72 67 Version="1" Targ
22:44:20: DEBUG: printBuffer:4320 65 74 4E 61 6D 65 3D 22 38 78 31 30 22 20 2F 3E etName="8x10" />
22:44:20: DEBUG: printBuffer:4320 3C 2F 64 61 74 61 3E </data>
22:44:20: DEBUG: printBuffer:4333


22:44:20: DEBUG: XML FILE (110 bytes): CharsInBuffer=407-110=297
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Host's payload to target size is too large" /></data>
-------------------------------------------------------------------------------------------

22:44:20: INFO: TARGET SAID: 'Host's payload to target size is too large'
22:44:20: DEBUG: XML FILE (297 bytes): CharsInBuffer=297-297=0
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?><data><response value="NAK" MinVersionSupported="1" MemoryName="eMMC" MaxPayloadSizeFromTargetInBytes="4096" MaxPayloadSizeToTargetInBytes="49152" MaxPayloadSizeToTargetInBytesSupported="49152" MaxXMLSizeInBytes="4096" Version="1" TargetName="8x10" /></data>
-------------------------------------------------------------------------------------------

22:44:20: DEBUG: Response was 'NAK'
22:44:20: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 49152
22:44:20: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 49152
22:44:20: INFO: Target returned NAK for your <configure> but it does not seem to be an error. This is ok, fh_loader.exe attributes updated
22:44:20: INFO: Sending <setbootablestoragedrive>
22:44:20: DEBUG: CHANNEL DATA (P0001) (H00203) ( 93 bytes) - HOST TO TARGET -->
===========================================================================================================
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<setbootablestoragedrive value="0" />
</data>

============================================================================================================

22:44:20: DEBUG: CharsInBuffer=0 Trying to read from USB 4096 bytes
22:44:20: DEBUG: CHANNEL DATA (168 bytes) <-- TARGET to HOST
22:44:20: DEBUG: CharsInBuffer = 168
22:44:20: DEBUG: printBuffer:4243 PRETTYPRINT Buffer is 168 bytes

22:44:20: DEBUG: printBuffer:4320 3C 3F 78 6D 6C 20 76 65 72 73 69 6F 6E 3D 22 31 <?xml version="1
22:44:20: DEBUG: printBuffer:4320 2E 30 22 20 65 6E 63 6F 64 69 6E 67 3D 22 55 54 .0" encoding="UT
22:44:20: DEBUG: printBuffer:4320 46 2D 38 22 20 3F 3E 3C 64 61 74 61 3E 3C 6C 6F F-8" ?><data><lo
22:44:20: DEBUG: printBuffer:4320 67 20 76 61 6C 75 65 3D 22 53 65 74 20 62 6F 6F g value="Set boo
22:44:20: DEBUG: printBuffer:4320 74 61 62 6C 65 20 64 72 69 76 65 20 74 6F 20 30 table drive to 0
22:44:20: DEBUG: printBuffer:4320 2E 22 20 2F 3E 3C 2F 64 61 74 61 3E 3C 3F 78 6D ." /></data><?xm
22:44:20: DEBUG: printBuffer:4320 6C 20 76 65 72 73 69 6F 6E 3D 22 31 2E 30 22 20 l version="1.0"
22:44:20: DEBUG: printBuffer:4320 65 6E 63 6F 64 69 6E 67 3D 22 55 54 46 2D 38 22 encoding="UTF-8"
22:44:20: DEBUG: printBuffer:4320 20 3F 3E 3C 64 61 74 61 3E 3C 72 65 73 70 6F 6E ?><data><respon
22:44:20: DEBUG: printBuffer:4320 73 65 20 76 61 6C 75 65 3D 22 41 43 4B 22 20 2F se value="ACK" /
22:44:20: DEBUG: printBuffer:4320 3E 3C 2F 64 61 74 61 3E ></data>
22:44:20: DEBUG: printBuffer:4333


22:44:20: DEBUG: XML FILE (92 bytes): CharsInBuffer=168-92=76
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Set bootable drive to 0." /></data>
-------------------------------------------------------------------------------------------

22:44:20: INFO: TARGET SAID: 'Set bootable drive to 0.'
22:44:20: DEBUG: XML FILE (76 bytes): CharsInBuffer=76-76=0
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" /></data>
-------------------------------------------------------------------------------------------

22:44:20: DEBUG: Response was 'ACK'
22:44:20: DEBUG: Got the ACK
22:44:20: INFO: ==============================================================
22:44:20: INFO: Files used and their paths
22:44:20: INFO: 1 'C:\Users\Zahid\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
22:44:20: INFO: _ (done)
22:44:20: INFO: | |
22:44:20: INFO: __| | ___ _ __ ___
22:44:20: INFO: / _` |/ _ \| '_ \ / _ \
22:44:20: INFO: | (_| | (_) | | | | __/
22:44:20: INFO: \__,_|\___/|_| |_|\___|
22:44:20: INFO: {All Finished Successfully}

22:44:20: INFO: FILE ACCESS SLOW!! 0.00 B in 0.015 seconds ( 0.00 Bps) --- Overall to target 0.203 seconds (0.00 Bps)


++This is my log after installing, giving me few error logs,but install is finished 100% correctly. After that im still not able to turn on phone,still giving me that qualcom usb port and nothing else. Any solutions_

i have error with this metod QFIL when i chose mbn & path & rawprogram begin error
i find that rawprogram and pach disnt sutable with QFIL true raw must be raw program :rawprogram_unsparse
and patch2 .....rawprogram_unsparse xml file but not found in frimware d295 or 295f where is find that file or creat own?:rolleyes:
 

faizm26

Member
Aug 13, 2013
19
0
my pc install thedriver automatically everytime i plug my phone how do i stop this? and am getting sahara fail everytime i click download
 

sunmartin

Member
Apr 18, 2015
7
0
isfahan

LukaRuso

Member
Feb 15, 2015
23
4
I'm having problems. Every time I try this method i get errors. Even though it finishes doing its thing, it never works.
This is the code.

Code:
22:22:26: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM99 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=eMMC --setactivepartition=0 
************************************************

22:22:26: DEBUG: Binary build date: Jun  3 2015 @ 17:12:06

22:22:26: DEBUG: Build Version: 15.06. 3.17.12.06

22:22:26: INFO: Current working dir (cwd): C:\Users\LukaRuso\AppData\Roaming\Qualcomm\QFIL\
22:22:26: INFO: Showing network mappings to allow debugging
22:22:26: DEBUG: New connections will be remembered.

22:22:26: DEBUG: 

22:22:26: DEBUG: There are no entries in the list.

22:22:26: DEBUG: 

22:22:26: DEBUG: User set ZLPAWAREHOST to 89058307251109889

22:22:26: INFO: User wants to talk to port '\\.\COM99'
22:22:26: DEBUG: port_fd=0xC0

22:22:26: INFO: Took       0.00000000 seconds to open port
22:22:26: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
22:22:26: INFO: If  you don't want this, use --dontsorttags

22:22:26: INFO: Sending <configure>
22:22:26: DEBUG: CHANNEL DATA (P0000) (H00202) (    246 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" TargetName="8960" />
</data>

============================================================================================================

22:22:26: DEBUG: CharsInBuffer=0 Trying to read from USB 8192 bytes
22:22:26: DEBUG: CHANNEL DATA (407 bytes) <-- TARGET to HOST
22:22:26: DEBUG: CharsInBuffer = 407
22:22:26: DEBUG: printBuffer:4243 PRETTYPRINT Buffer is 407 bytes

22:22:26: DEBUG: printBuffer:4320 3C 3F 78 6D 6C 20 76 65 72 73 69 6F 6E 3D 22 31 <?xml version="1
22:22:26: DEBUG: printBuffer:4320 2E 30 22 20 65 6E 63 6F 64 69 6E 67 3D 22 55 54 .0" encoding="UT
22:22:26: DEBUG: printBuffer:4320 46 2D 38 22 20 3F 3E 3C 64 61 74 61 3E 3C 6C 6F F-8" ?><data><lo
22:22:26: DEBUG: printBuffer:4320 67 20 76 61 6C 75 65 3D 22 48 6F 73 74 27 73 20 g value="Host's 
22:22:26: DEBUG: printBuffer:4320 70 61 79 6C 6F 61 64 20 74 6F 20 74 61 72 67 65 payload to targe
22:22:26: DEBUG: printBuffer:4320 74 20 73 69 7A 65 20 69 73 20 74 6F 6F 20 6C 61 t size is too la
22:22:26: DEBUG: printBuffer:4320 72 67 65 22 20 2F 3E 3C 2F 64 61 74 61 3E 3C 3F rge" /></data><?
22:22:26: DEBUG: printBuffer:4320 78 6D 6C 20 76 65 72 73 69 6F 6E 3D 22 31 2E 30 xml version="1.0
22:22:26: DEBUG: printBuffer:4320 22 20 65 6E 63 6F 64 69 6E 67 3D 22 55 54 46 2D " encoding="UTF-
22:22:26: DEBUG: printBuffer:4320 38 22 20 3F 3E 3C 64 61 74 61 3E 3C 72 65 73 70 8" ?><data><resp
22:22:26: DEBUG: printBuffer:4320 6F 6E 73 65 20 76 61 6C 75 65 3D 22 4E 41 4B 22 onse value="NAK"
22:22:26: DEBUG: printBuffer:4320 20 4D 69 6E 56 65 72 73 69 6F 6E 53 75 70 70 6F  MinVersionSuppo
22:22:26: DEBUG: printBuffer:4320 72 74 65 64 3D 22 31 22 20 4D 65 6D 6F 72 79 4E rted="1" MemoryN
22:22:26: DEBUG: printBuffer:4320 61 6D 65 3D 22 65 4D 4D 43 22 20 4D 61 78 50 61 ame="eMMC" MaxPa
22:22:26: DEBUG: printBuffer:4320 79 6C 6F 61 64 53 69 7A 65 46 72 6F 6D 54 61 72 yloadSizeFromTar
22:22:26: DEBUG: printBuffer:4320 67 65 74 49 6E 42 79 74 65 73 3D 22 34 30 39 36 getInBytes="4096
22:22:26: DEBUG: printBuffer:4320 22 20 4D 61 78 50 61 79 6C 6F 61 64 53 69 7A 65 " MaxPayloadSize
22:22:26: DEBUG: printBuffer:4320 54 6F 54 61 72 67 65 74 49 6E 42 79 74 65 73 3D ToTargetInBytes=
22:22:26: DEBUG: printBuffer:4320 22 34 39 31 35 32 22 20 4D 61 78 50 61 79 6C 6F "49152" MaxPaylo
22:22:26: DEBUG: printBuffer:4320 61 64 53 69 7A 65 54 6F 54 61 72 67 65 74 49 6E adSizeToTargetIn
22:22:26: DEBUG: printBuffer:4320 42 79 74 65 73 53 75 70 70 6F 72 74 65 64 3D 22 BytesSupported="
22:22:26: DEBUG: printBuffer:4320 34 39 31 35 32 22 20 4D 61 78 58 4D 4C 53 69 7A 49152" MaxXMLSiz
22:22:26: DEBUG: printBuffer:4320 65 49 6E 42 79 74 65 73 3D 22 34 30 39 36 22 20 eInBytes="4096" 
22:22:26: DEBUG: printBuffer:4320 56 65 72 73 69 6F 6E 3D 22 31 22 20 54 61 72 67 Version="1" Targ
22:22:26: DEBUG: printBuffer:4320 65 74 4E 61 6D 65 3D 22 38 78 31 30 22 20 2F 3E etName="8x10" />
22:22:26: DEBUG: printBuffer:4320 3C 2F 64 61 74 61 3E                            </data>
22:22:26: DEBUG: printBuffer:4333 


22:22:26: DEBUG: XML FILE (110 bytes): CharsInBuffer=407-110=297
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Host's payload to target size is too large" /></data>
-------------------------------------------------------------------------------------------

22:22:26: INFO: TARGET SAID: 'Host's payload to target size is too large'
22:22:26: DEBUG: XML FILE (297 bytes): CharsInBuffer=297-297=0
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?><data><response value="NAK" MinVersionSupported="1" MemoryName="eMMC" MaxPayloadSizeFromTargetInBytes="4096" MaxPayloadSizeToTargetInBytes="49152" MaxPayloadSizeToTargetInBytesSupported="49152" MaxXMLSizeInBytes="4096" Version="1" TargetName="8x10" /></data>
-------------------------------------------------------------------------------------------

22:22:26: DEBUG: Response was 'NAK'
22:22:26: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 49152
22:22:26: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 49152
22:22:26: INFO: Target returned NAK for your <configure> but it does not seem to be an error. This is ok, fh_loader.exe attributes updated
22:22:26: INFO: Sending <setbootablestoragedrive>
22:22:26: DEBUG: CHANNEL DATA (P0001) (H00203) (     93 bytes) - HOST TO TARGET -->
===========================================================================================================
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<setbootablestoragedrive value="0" />
</data>

============================================================================================================

22:22:26: DEBUG: CharsInBuffer=0 Trying to read from USB 4096 bytes
22:22:27: DEBUG: CHANNEL DATA (168 bytes) <-- TARGET to HOST
22:22:27: DEBUG: CharsInBuffer = 168
22:22:27: DEBUG: printBuffer:4243 PRETTYPRINT Buffer is 168 bytes

22:22:27: DEBUG: printBuffer:4320 3C 3F 78 6D 6C 20 76 65 72 73 69 6F 6E 3D 22 31 <?xml version="1
22:22:27: DEBUG: printBuffer:4320 2E 30 22 20 65 6E 63 6F 64 69 6E 67 3D 22 55 54 .0" encoding="UT
22:22:27: DEBUG: printBuffer:4320 46 2D 38 22 20 3F 3E 3C 64 61 74 61 3E 3C 6C 6F F-8" ?><data><lo
22:22:27: DEBUG: printBuffer:4320 67 20 76 61 6C 75 65 3D 22 53 65 74 20 62 6F 6F g value="Set boo
22:22:27: DEBUG: printBuffer:4320 74 61 62 6C 65 20 64 72 69 76 65 20 74 6F 20 30 table drive to 0
22:22:27: DEBUG: printBuffer:4320 2E 22 20 2F 3E 3C 2F 64 61 74 61 3E 3C 3F 78 6D ." /></data><?xm
22:22:27: DEBUG: printBuffer:4320 6C 20 76 65 72 73 69 6F 6E 3D 22 31 2E 30 22 20 l version="1.0" 
22:22:27: DEBUG: printBuffer:4320 65 6E 63 6F 64 69 6E 67 3D 22 55 54 46 2D 38 22 encoding="UTF-8"
22:22:27: DEBUG: printBuffer:4320 20 3F 3E 3C 64 61 74 61 3E 3C 72 65 73 70 6F 6E  ?><data><respon
22:22:27: DEBUG: printBuffer:4320 73 65 20 76 61 6C 75 65 3D 22 41 43 4B 22 20 2F se value="ACK" /
22:22:27: DEBUG: printBuffer:4320 3E 3C 2F 64 61 74 61 3E                         ></data>
22:22:27: DEBUG: printBuffer:4333 


22:22:27: DEBUG: XML FILE (92 bytes): CharsInBuffer=168-92=76
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Set bootable drive to 0." /></data>
-------------------------------------------------------------------------------------------

22:22:27: INFO: TARGET SAID: 'Set bootable drive to 0.'
22:22:27: DEBUG: XML FILE (76 bytes): CharsInBuffer=76-76=0
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" /></data>
-------------------------------------------------------------------------------------------

22:22:27: DEBUG: Response was 'ACK'
22:22:27: DEBUG: Got the ACK
22:22:27: INFO: ==============================================================
22:22:27: INFO: Files used and their paths
22:22:27: INFO:   1 'C:\Users\LukaRuso\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
22:22:27: INFO:      _             (done)
22:22:27: INFO:     | |                 
22:22:27: INFO:   __| | ___  _ __   ___ 
22:22:27: INFO:  / _` |/ _ \| '_ \ / _ \
22:22:27: INFO: | (_| | (_) | | | |  __/
22:22:27: INFO:  \__,_|\___/|_| |_|\___|
22:22:27: INFO: {All Finished Successfully}

22:22:27: INFO: FILE ACCESS SLOW!!     0.00 B in  0.015 seconds (    0.00 Bps) --- Overall to target  0.203 seconds (0.00 Bps)
 

maxtaxx

New member
May 26, 2018
1
0
i need de rawprogram and pacth

---------- Post added at 01:31 AM ---------- Previous post was at 01:27 AM ----------

i need the files rawprogram and patch please i cant did for myself:confuso:
 

PHENOM X4

New member
Jun 13, 2018
1
0
error fix

error 237 unable to read packet header
error 924 sahara protocol error
error 303 uploading image using sahara protocol failed

Please tell me how to fix these
 

sevo1984

Member
Dec 9, 2014
5
0
Does a bricked D290N displays “insert battery” screen when plugged into charger with no battery?
I tested two bricked Finos.
1. The first one showing “Qualcomm HS-USB QDLoader 9008” (without “mass storage” component), but with no “insert battery screen” screen.
2. The second phone which could not be detected by a computer (nothing happens when plugged in), which does have “insert battery screen” and it vibrates when powered on but nothing happens after this and it doesn't continue to boot.
I flashed the first one successfully with QFIL but the phone remaines dead (although still indicating QDLoader 9008 mode when plugged in).
The other phone could not be flashed for obvious reasons. Is it possible that its condition (inability to be recognized by a computer) was caused by some other hardware failure (e.g. faulty usb port issue) rather than the brick itself?
It is particularly confusing given that I understand there is more than one QDLoader modes:
(cannot paste link but search: unbrick-qualcomm-mobiles on droidsavvy forum)
Either way, this model (LG fino) has terrible reputation in my country judging by endless supply of ads for bricked finos on sale .
My point here was that various other hardware failures seemed to often accompany dead boot???
 

Top Liked Posts

  • There are no posts matching your filters.
  • 13
    Guide for unbricking LG L Fino from Qualcomm 9008 and LGE AndroidNet mode
    I'm not responsible for any damage. You do this on your own risk

    Short message from me: I searched ALL the web and found nothing needed files for unbricking L Fino so I discovered myself how to make rawprogram0.xml and finally IT WORKED!

    Symtomps:
    - While you connect phone to computer in device menager you have "Qualcomm HS-USB QDLoader 9008" (or similar), or probably QHSUSB BULK (or similar).
    - You can't boot your device to download mode, recovery etc. Just black screen


    Let's start unbricking! :)

    Required things:
    - Qualcomm mobile drivers
    - QPTS
    - Unbricking ROM (I made it)
    - ROM for your country (if it don't exist you can download ROM for another country) - you must download it here: http://lg-phone-firmware.com/index.php?id_mod=103 (choose your ROM, look at country and model D290N, D295 or D295F)
    - USB - Micro USB cable
    - LG Flash Tool

    Download all these files here: https://mega.nz/#F!m5MCzRJA!KFh_25WI3a13B8Ek2QpApg

    _____________________________________

    INSTRUCTIONS:

    0. (Only if you have LGE AndroidNet mode and your phone is showing as a drive) Make a partition from empty space on that "drive". I recommend "EaseUS Partition Master" program. Then plug off phone from computer.

    [Make sure that your LG L Fino is disconnected from PC]
    1. First you have to disabe driver signature verification. To do that open CMD as administrator and enter these commands:

    bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS

    bcdedit -set TESTSIGNING ON
    After that restart your computer. You will have text "Test mode" on right bottom corner of desktop.

    2. Unpack "LG Unbrick Tools.zip" to folder on your desktop and "DXXX UNBRICK.zip" to folder without spaces (thanks to user mountaser halak for sending me logs so I found out that QFIL doesn't correctly recognizes spaces) that is in root of the drive.

    3. Install Qualcomm Driver from "LG Unbrick Tools" (You have to uninstall Qualcomm driver first - plug-in phone for this, right click on Qualcomm 9008 in device menager and uninstall) - choose your system architecture and click dpinst.exe (name will be with 32 or 64 at the end)

    4. Install QPST from "LG Unbrick Tools"

    5. After installing QPST open QFIL - it will be in start menu. If it won't - go to C:/Program Files (x86)/Qualcomm/QPST and open QFIL.

    6. In QFIL select "Flat build". In programmer patch go to folder with "DXXX UNBRICK" files and select "prog_emmc_firehose_8x10.mbn", click on load XML and select files that will be showed. Or look at the attachment

    7. NOW Plug-in USB cable to your computer.

    8. Remove the battery from your LG and wait 3 seconds. Insert the battery again. Plug USB to your phone, wait about 3 seconds and click DOWNLOAD button on PC.
    (notice that download in this case doesn't mean download something from internet. It mean "(down) load firmware from computer to phone")

    9. Wait to complete process. (It will take about 10 minutes) If you get error try put D290N Unbrick files folder directly on disk (I prefer on another partition)

    10. Disconnect LG from PC, remove and insert the battery. If phone is discharged, charge it with a normal charger to 4-5%.

    11. NOW you can turn on LG L Fino to check if phone works.


    After that LG L Fino will have many bugs and do factory reset in every reboot. To avoid this we will flash LG with Download Mode. I prefer charge phone to min. 20%

    To enter download mode turn off device and plug-in USB cable to phone while holding Volume Up button.
    After that, follow this tutorial (I prefer selecting CSE flash)
    If Flash Tool doesn't work properly try on another PC or install clean Windows on another partition and run it on it.

    After all done you can enable "Driver signature verification" again to delete "Test mode" text on desktop. Just open CMD as administrator and enter command:
    bcdedit -set TESTSIGNING OFF

    Issues:
    - IMEI is setting to 0 after every ROM flashing. It can be changed with this Xposed module: https://play.google.com/store/apps/details?id=com.phoneinfo.changer
    - Problems with boot into a custom ROM (maybe only me have this problem)
    - 3G don't working (or only I have this problem)
    - List of languages is strange
    If you found other issues tell me about them


    I hope I helped many people! This is the first real tutorial for unbricking L Fino from this mode! If you want donate contact me [email protected] ! ;)
    PS: I have 13 years ;) If you found any mistakes tell me about it. Sorry for them in the poll (I can't edit them)
    2
    I finally have time to make D295F and D295 files so I will make it today and upload it at night
    2
    Great, will try it later. Just to check - how can I recognize D295F or D295 or D295N I have?

    If it's a single SIM phone it will probably be D290N,
    If it's a dual SIM phone it will be D295 or D295F

    The easiest way to know the model: in the attachment
    1
    Thank you, do you think I messed up the device by using D290N files? Or do I have a chance for recovery?

    I think you didn't messed up device if you still have Qualcomm 9008... In device menager
    1
    Mine is LG d295F but windows isn't detecting as "qualcomm..." its only showing "LG Androidnet USB Serial Port"


    When I try to use this on QIFL, give an error "Start Download
    COM Port number:12
    Switch To EDL
    Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode
    Finish Download"



    Sorry, Bad english i'm Brazilian <3

    Hmmm... Have you googled it? I will search web about your problem at weekend