LG G8 Demo Unit Flash - LG G8 Questions & Answers

LG G8 Demo Unit Flash - LG G8 Questions & Answers

Hey all, I'm somewhat new to Andriod hacking, I've done some tinkering with a galaxy s2 in the past but not much. I have recently acquired a Retail Demo unit G8 and I was planning on somehow bypassing the retail to use it for listening to music. (MQA, 32bit dac)
I have been trying to get LGUP to work, but when I boot into the download mode I don't get the menu everyone else has with the USB logo. It just shows a menu on how to unlock the bootloader with REBOOT and POWER OFF in big text on the top. I have looked into the bootloader unlock (I have OEM bypass enabled in developer options) but I need an IMEI to submit a request, which I don't have. I have tried UPPERCUT with no luck, along with various methods to remove the retail mode.
In the end, a perfect solution would be:
-WiFi
-Full 128gb of storage
-Ability to pin apps.
Any help or discussion welcomed. thanks!
(Only a few demo G8's seem to be floating around so I have been following G7 guides. Passwords for the phone are: L310MC570G and 103729)

ItsMaxton said:
Hey all, I'm somewhat new to Andriod hacking, I've done some tinkering with a galaxy s2 in the past but not much. I have recently acquired a Retail Demo unit G8 and I was planning on somehow bypassing the retail to use it for listening to music. (MQA, 32bit dac)
I have been trying to get LGUP to work, but when I boot into the download mode I don't get the menu everyone else has with the USB logo. It just shows a menu on how to unlock the bootloader with REBOOT and POWER OFF in big text on the top. I have looked into the bootloader unlock (I have OEM bypass enabled in developer options) but I need an IMEI to submit a request, which I don't have. I have tried UPPERCUT with no luck, along with various methods to remove the retail mode.
In the end, a perfect solution would be:
-WiFi
-Full 128gb of storage
-Ability to pin apps.
Any help or discussion welcomed. thanks!
(Only a few demo G8's seem to be floating around so I have been following G7 guides. Passwords for the phone are: L310MC570G and 103729)
Click to expand...
Click to collapse
Hi. You do not need to put phone in download mode, LG-UP will do that for you. Just load the right kdz and try to flash using refurbished. Hope it works, but I'm pessimistic...

Inerent said:
Hi. You do not need to put phone in download mode, LG-UP will do that for you. Just load the right kdz and try to flash using refurbished. Hope it works, but I'm pessimistic...
Click to expand...
Click to collapse
Using the PARTITION DL option, I get an error at 4%: SPC Code does not match. Please, try agian.

I have the same demo unit any progress flashing firmware? Can you use a memory card in your unit? I have the same unit but memory card is not recognized.

I managed to flash some firmware following the instructions at a page called "LG G8 ThinQ: How to flash stock firmware, Unbrick/restore LG G8 ThinQ back to stock" (I cannot post a link...) and use lgup 1.15 instead of 1.14. However, the wifi appears to be not working afterwards. Not sure if it's because I used the wrong firmware.

yuyichao said:
I managed to flash some firmware following the instructions at a page called "LG G8 ThinQ: How to flash stock firmware, Unbrick/restore LG G8 ThinQ back to stock" (I cannot post a link...) and use lgup 1.15 instead of 1.14. However, the wifi appears to be not working afterwards. Not sure if it's because I used the wrong firmware.
Click to expand...
Click to collapse
Stuck at same problem. Only way to connect to internet is by otg network or gniretet for me right now, also demo unit only has 32gb of storage , the 128gb is fake. Did you find any solution to wifi?

wifi error.
yuyichao said:
I managed to flash some firmware following the instructions at a page called "LG G8 ThinQ: How to flash stock firmware, Unbrick/restore LG G8 ThinQ back to stock" (I cannot post a link...) and use lgup 1.15 instead of 1.14. However, the wifi appears to be not working afterwards. Not sure if it's because I used the wrong firmware.
Click to expand...
Click to collapse
Did you find any solution to wifi?

Has anybody found a solution to the Wi-Fi yet I have no problem flashing these firmware's onto the phone I'm only problem is I never get the Wi-Fi to workI'm guessing this is going to be a pretty rough one to figure out considering there's not that many of these out there

v8s10 said:
If you did a backup of the modem prior to flashing a different firmware with lgup you can restore the modem and have working wifi.
Click to expand...
Click to collapse
I'm I screwed if I did not make that back up

v8s10 said:
I have a backup of mine you could try, should work
Click to expand...
Click to collapse
i would like to try that thanks where do i download

v8s10 said:
I have a backup of mine you could try, should
Click to expand...
Click to collapse
I sent you a message

Gregory4621 said:
if you need my email to send the files its [email protected]
Click to expand...
Click to collapse
dont post your email in a public forum. thats how you end up with an inbox full of dic pics! just pm your email.

Hi has anyone manage to get the wifi working as I have the same issue. I have a custom software for the G8s as well but can not flash it as I can not unlock the boot loader. If anyone knows how I can do that.

Vipersla said:
Hi has anyone manage to get the wifi working as I have the same issue. I have a custom software for the G8s as well but can not flash it as I can not unlock the boot loader. If anyone knows how I can do that.
Click to expand...
Click to collapse
Im still waiting on the gentleman who replied to me

Gregory4621 said:
Im still waiting on the gentleman who replied to me
Click to expand...
Click to collapse
same here or does anyone else have a way to over come the current issue of getting the wifi to work and pick the wifi in range

Gregory4621 said:
Im still waiting on the gentleman who replied to me
Click to expand...
Click to collapse
Vipersla said:
same here or does anyone else have a way to over come the current issue of getting the wifi to work and pick the wifi in range
Click to expand...
Click to collapse
Sergio Melo said:
wifi error.
Did you find any solution to wifi?
Click to expand...
Click to collapse
Here's my modem.img backup, flash in QFIL, or use fastboot if your bootloader is unlocked.
modem
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
yuyichao said:
I managed to flash some firmware following the instructions at a page called "LG G8 ThinQ: How to flash stock firmware, Unbrick/restore LG G8 ThinQ back to stock" (I cannot post a link...) and use lgup 1.15 instead of 1.14. However, the wifi appears to be not working afterwards. Not sure if it's because I used the wrong firmware.
Click to expand...
Click to collapse
Any regular G8 firmware will break WiFi on this unit because they're different. Notice how this G8 doesn't pick up 5GHz networks but the real G8 does.

Can someone provide the right direction on how to do this and exactly the right tools with the right links and step by step.
Ive had this phone now for a year and I would so much love for it to have wifi again because bluetooth is so slow.
I remember I did like the rest in the begining upgrade it with firware and completly lost the wifi and since the phone has been collecting dust ever since.

Does flashing the modem img after flashing a stock rom fixes the wifi? and is there any way i can flash android 10 on it? i got my demo unit flashed by the person who sold it to me and it is running Android 9 G820UM10g., with WIFI and everything working. Would love to have Android 10 as it has a better dark mode which will hide the shade on screen...

Zumbuh said:
Here's my modem.img backup, flash in QFIL, or use fastboot if your bootloader is unlocked.
modem
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Any regular G8 firmware will break WiFi on this unit because they're different. Notice how this G8 doesn't pick up 5GHz networks but the real G8 does.
Click to expand...
Click to collapse
It Working!!!!!!
Thanks a lot +_+

ItsMaxton said:
Hey all, I'm somewhat new to Andriod hacking, I've done some tinkering with a galaxy s2 in the past but not much. I have recently acquired a Retail Demo unit G8 and I was planning on somehow bypassing the retail to use it for listening to music. (MQA, 32bit dac)
I have been trying to get LGUP to work, but when I boot into the download mode I don't get the menu everyone else has with the USB logo. It just shows a menu on how to unlock the bootloader with REBOOT and POWER OFF in big text on the top. I have looked into the bootloader unlock (I have OEM bypass enabled in developer options) but I need an IMEI to submit a request, which I don't have. I have tried UPPERCUT with no luck, along with various methods to remove the retail mode.
In the end, a perfect solution would be:
-WiFi
-Full 128gb of storage
-Ability to pin apps.
Any help or discussion welcomed. thanks!
(Only a few demo G8's seem to be floating around so I have been following G7 guides. Passwords for the phone are: L310MC570G and 103729)
Click to expand...
Click to collapse
note: I'm not responsible for any loss, damage, harm or anything at all.
use qfil.
1. extract any kdz you wanna flash using kdztools master with the "-c" command.
1-a. by this command you get the true GPT files needed for partitioning alongside other partitions but we just use these GPT partitions here.
2. again, extract the kdz this time using "-x" command.
2-a. running the command will give you "OP" and other partitions but we just use these OP partitions now.
2-a-a. search the forum and find the solution how to make a correct OP partitions. or use google translate on this link.
3. for the third time, extract kdz this time using "kdztools.exe". here, we use all partitions except GPT and OP the we got in steps 1 and 2.
4. go to dload.
5. run qfil and go to partition manager. (you need firehose and some settings, search for them you'll find them all in a breeze).
6. if I were you I'd back up all partitions, but for emergency just back up the ftm, modem, modemst1, modemst2, fsg and fsc partitions.
7. delete all partitions.
note: do not disconnect the phone, do not close qfil, even do not close the partition manager window or you will get into trouble.
8. now we need to re-partition the ufs flash using GPT files we got in step 1.
9. rename gpt files from the pattern "gpt_main#.anythin" to "lun#.bin". so gpt_main0.anythind will become LUN0.BIN and gpt_main1.anything will turn into LUN1.BIN.
10. copy LUN files into the qpst/bin directory.
11. go to the directory of qpst/bin and run cmd there. (hold shift button and then right click...)
12. go to device manager and find the port number of the phone connected in dload.
13. find "COM999" in codes in step 14 and then replace "999" with the port number of your device (you found in step 12) in below codes.
14. in the cmd line execute these codes:
LUN0
fh_loader.exe --port=\\.\COM999 --sendimage=LUN0_Complete.bin --start_sector=0 --lun=0 --num_sectors=4328072 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
LUN1
fh_loader.exe --port=\\.\COM999 --sendimage=LUN1_Complete.bin --start_sector=0 --lun=1 --num_sectors=2048 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
LUN2
fh_loader.exe --port=\\.\COM999 --sendimage=LUN2_Complete.bin --start_sector=0 --lun=2 --num_sectors=2048 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
LUN3
fh_loader.exe --port=\\.\COM999 --sendimage=LUN3_Complete.bin --start_sector=0 --lun=3 --num_sectors=2048 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
LUN4
fh_loader.exe --port=\\.\COM999 --sendimage=LUN4_Complete.bin --start_sector=0 --lun=4 --num_sectors=383995 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
LUN5
fh_loader.exe --port=\\.\COM999 --sendimage=LUN5_Complete.bin --start_sector=0 --lun=5 --num_sectors=3072 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
LUN6
fh_loader.exe --port=\\.\COM999 --sendimage=LUN6_Complete.bin --start_sector=0 --lun=6 --num_sectors=1024 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
15. if everything goes right you will get "done" in the cmd window.
16. after getting "done", close partition window and re-open it to see your partitions are back.
17. now you need to restore partitions.
17-a. except op partitions you made in step 2, we use files for other partitions we got in step 3.
18. make sure all partitions have the "img" extension in their names.
19. use following codes in cmd (run in qpst/bin directory), remember to correct "COM999" before executing codes.
19-a. copy partition files you got from step 2 and 3 into qpst/bin directory.
fh_loader.exe --port=\\.\COM999 --sendimage=mpt.img --start_sector=6 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=drm.img --start_sector=8198 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=p_persist_lg.img --start_sector=11782 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=sns.img --start_sector=11782 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=ssd.img --start_sector=15366 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=persist.img --start_sector=15368 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=misc.img --start_sector=23560 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=ftm.img --start_sector=23816 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=power.img --start_sector=32008 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=encrypt.img --start_sector=43272 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=eksst.img --start_sector=43400 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=rct.img --start_sector=43528 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=fota.img --start_sector=43656 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=srtc.img --start_sector=46216 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=pstore.img --start_sector=48264 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=els.img --start_sector=48776 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=operatorlogging.img --start_sector=52872 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=eri.img --start_sector=56968 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=carrier.img --start_sector=59016 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=persdata.img --start_sector=71304 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=metadata.img --start_sector=87688 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=vendor_a.img --start_sector=91784 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=vendor_b.img --start_sector=526984 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=system_a.img --start_sector=962184 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=system_b.img --start_sector=1944200 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=product_a.img --start_sector=2926216 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=product_b.img --start_sector=3450504 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=OP_a.img --start_sector=3974792 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
---------------------LUN1--------------------------------------------LUN1--------------------------------------------LUN1--------------------------------------------LUN1-----------------------
fh_loader.exe --port=\\.\COM999 --sendimage=LUN1.img --start_sector=0 --lun=1 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=xbl_a.img --start_sector=6 --lun=1 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=xbl_config_a.img --start_sector=902 --lun=1 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
---------------------LUN2--------------------------------------------LUN2--------------------------------------------LUN2--------------------------------------------LUN2-----------------------
fh_loader.exe --port=\\.\COM999 --sendimage=LUN2.img --start_sector=0 --lun=2 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=xbl_b.img --start_sector=6 --lun=2 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=xbl_config_b.img --start_sector=902 --lun=2 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
---------------------LUN4--------------------------------------------LUN4--------------------------------------------LUN4--------------------------------------------LUN4-----------------------
fh_loader.exe --port=\\.\COM999 --sendimage=aop_a.img --start_sector=6 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=tz_a.img --start_sector=134 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=hyp_a.img --start_sector=1158 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=modem_a.img --start_sector=1290 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=mdtpsecapp_a.img --start_sector=57610 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=mdtp_a.img --start_sector=58634 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=abl_a.img --start_sector=66826 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=dsp_a.img --start_sector=67082 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=keymaster_a.img --start_sector=83466 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=akmu_a.img --start_sector=83594 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=boot_a.img --start_sector=83722 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=cmnlib_a.img --start_sector=108298 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=cmnlib64_a.img --start_sector=108426 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=devcfg_a.img --start_sector=108554 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=qupfw_a.img --start_sector=108586 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=laf_a.img --start_sector=108606 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=vbmeta_a.img --start_sector=120894 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=dtbo_a.img --start_sector=120910 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=uefisecapp_a.img --start_sector=127054 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=imagefv_a.img --start_sector=127566 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=raw_resources_a.img --start_sector=128078 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=core_nhlos_a.img --start_sector=130126 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=sid_a.img --start_sector=173646 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=secdata.img --start_sector=347542 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=devinfo.img --start_sector=347549 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=dip.img --start_sector=347550 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=apdp.img --start_sector=347806 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=msadp.img --start_sector=347870 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=spunvm.img --start_sector=347934 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=splash.img --start_sector=349982 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=toolsfv.img --start_sector=358339 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=logfs.img --start_sector=358595 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=cateloader.img --start_sector=360643 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=logdump.img --start_sector=361155 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=storsec.img --start_sector=377539 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=multiimgoem.img --start_sector=377571 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=multiimgqti.img --start_sector=377579 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=uefivarstore.img --start_sector=377587 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=catefv.img --start_sector=377715 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
fh_loader.exe --port=\\.\COM999 --sendimage=catecontentfv.img --start_sector=377843 --lun=4 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
19-a. some of the partitions I wrote code for them may be missing in your files, they are not necessary.
20. in partition directory find "modem_a" partition and right click on it, press read data.
21. go to "C:\Users\YOUR_USER_NAME\AppData\Roaming\Qualcomm\QFIL\COMPORT_#".
22. you will face some files, one of them has the size of 160-170MB. open it using a hex editor.
22-a. if it is empty so the process of restoring partitions has not done in a correct way. so find the problem and solve it.
22-b. if it is not empty, go to the step 23.
23. now, close partitions manager window, wait for 10 seconds. then, press power and vol-down for 10 second. you will here a sound of unpluging device from the computer.
24. wait for 10-3- seconds, the phone will boot up. if don't you are in trouble ) and you need to restore the original partition files that I recommended to back up all of them in step 6.
25. if you get OPID Mismatched, then you need to modify OP then restore it. just restore OP after modification.
26. enjoy.
maybe I've missed sth...
for those who just try to flash their G8 (or other LG phones, just you need to find the right offset of partitions, which can be easily found by qfil partition manager, and modify my codes. as far as I know, most of paritions for sdm855 lg phones have the same characteristics) but they cannot because of OPID lock, they may follow the above instructions for any destination kdz, even Korean kdzs, then restore modemst1, modemst2 and fsg using qfil partition manager in the end.
that's all, have fun =)

Related

flashtool scatter file problem

I am using FlashTool_v5.1320.00 to restore my telephone using a scatter file from MtkDroidTools backup.
The scatter file was obtained from my telephon backup, so it is original from it.
My problem is that when I try to load it in FlashTool the scatter file from my complete backup or !FILETOFLASHTOOL directory, a popup tell me <Item failed : not file found> for all my files excluded this three files : DSP_BL, MBR,EBR1.
So I cannot restore my phone. The files are in the scatter's directory...
{
"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"
}
My phone is gt-n7102 clone :
Hardware : MT6577 (SMDK4x12 is Fake!)
Model : GT-N7102
Build number : JRO03C.N7102ZSALJ2
Build date UTC : 20130306-111329
Android v : 4.1.9
Baseband v: MAUI.11AMD.W12.22.SP.V5, 2013/01/28 11:29
Kernel v : 3.0.13 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP Wed Mar 6 19:10:15 CST 2013
Uboot build v : MAIN2.2.ubt.3877
LCD Driver IC : 1-otm8009a_6575_dsi
Thanks in advance for your support.

Reply
paxpax said:
I am using FlashTool_v5.1320.00 to restore my telephone using a scatter file from MtkDroidTools backup.
The scatter file was obtained from my telephon backup, so it is original from it.
My problem is that when I try to load it in FlashTool the scatter file from my complete backup or !FILETOFLASHTOOL directory, a popup tell me <Item failed : not file found> for all my files excluded this three files : DSP_BL, MBR,EBR1.
So I cannot restore my phone. The files are in the scatter's directory...
My phone is gt-n7102 clone :
Hardware : MT6577 (SMDK4x12 is Fake!)
Model : GT-N7102
Build number : JRO03C.N7102ZSALJ2
Build date UTC : 20130306-111329
Android v : 4.1.9
Baseband v: MAUI.11AMD.W12.22.SP.V5, 2013/01/28 11:29
Kernel v : 3.0.13 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP Wed Mar 6 19:10:15 CST 2013
Uboot build v : MAIN2.2.ubt.3877
LCD Driver IC : 1-otm8009a_6575_dsi
Thanks in advance for your support.
Click to expand...
Click to collapse
Hi there, Well Even I have been using SP Flash Tools for quiet some time. Well there may be certain obvious reasons for your Flash Tools not able to detect the files MTK Droid Tools, (happened to me 2 ) .. It is usually because the file extension is wrong.. if not try clicking in the haeding ( Like Click On the Name in the down Scatter BOX) and load it. Try Downloading Latest flash tool.
Here are a few links that may help you
http://forum.xda-developers.com/showpost.php?p=44509214&postcount=407
http://androidtronics.blogspot.in/2013/07/guide-how-to-make-backup-of-your-rom.html
http://forum.gsmhosting.com/vbb/f781/symphony-w70-mtk6577-backup-done-mtk-droid-tool-1723753/
http://forum.gsmhosting.com/vbb/f60...-mtk-droid-root-tools-backup-unbrick-1666984/
HIT THANKS IF THIS HELPS
Signature

now all is OK !!
I downloded SP flash tool v3.1328 and now all is OK !!
From my experience I Learnt two things :
1. ALWAYS make a backup of your system and scatter file with MtkDroidTools
2. Use always the latest version of MtkDroidTools and SP flash tool.
Thanks :laugh:

help unbrick gt-n7102 clone
paxpax said:
I downloded SP flash tool v3.1328 and now all is OK !!
From my experience I Learnt two things :
1. ALWAYS make a backup of your system and scatter file with MtkDroidTools
2. Use always the latest version of MtkDroidTools and SP flash tool.
Thanks :laugh:
Click to expand...
Click to collapse
Hello....I have the exactly same phone with exactly the same characteristics....could you upload your original rom ... because mine isn't working when I try to flash it with sp flash tool?
Thanks in advance....

How to Flash a Gps Tracker From FlashTool_v5.1432.00.Kindly help

i also want to make a scatter file for mtk device 6595??

SP Flash Tool on BLU cell - Error 8
Hello, when executing SP Flash Tool on BLU phone I get violet band but then appears ERROR 8 with this explanation
Error 8 (hint) Error creating collection file 'c:/documents and settings/user/.Mediatek/FlashTool\flashtool.qhc': Cannot creat
Even by creating manually this path and file, error persists
these are info of my sistem
flash tool V5.1824
sistema Windows XP
Celular BLU Dash Music 4.0 D272i
stockrom/BLU-D272i-V12-GENERIC/MT6572...scatter.txt
thanks very much any info to solve
meucat

SP Flash Tool on BLU cell - Error 8
meucat said:
Hello, when executing SP Flash Tool on BLU phone I get violet band but then appears ERROR 8 with this explanation
Error 8 (hint) Error creating collection file 'c:/documents and settings/user/.Mediatek/FlashTool\flashtool.qhc': Cannot creat
Even by creating manually this path and file, error persists
these are info of my sistem
flash tool V5.1824
sistema Windows XP
Celular BLU Dash Music 4.0 D272i
stockrom/BLU-D272i-V12-GENERIC/MT6572...scatter.txt
thanks very much any info to solve
meucat
Click to expand...
Click to collapse
I got to solve this problem by installing SP Flash Tool in that directory ...Mediatek/flashtool
But I now receive ERROR 8 without description (SPFT just opens help with no description)
I performed several tasks on SPFT and noticed these results
1) when formatting (format tab -> auto format) result successful ok
2) when download only preloader result successful ok
3) when download only all (or just any other boxes selected) results ERROR 8 no description (see details below)
4) when firmware upgrade result FAILED TO GET PMT INFO (see details below)
=============================================================================
I am copying here last lines on these logs for task 3) ERROR 8 no description
QT_FLASH_TOOL.log
11/24/2018 17:45:39.676 FlashTool[3184][2448][D]: MainWindowCallback::slot_DownloadBLoaderProgress(): The total_bytes is 100572(..\..\flashtool\UI\src\MainWindowCallback.cpp,550)
11/24/2018 17:45:39.691 FlashTool[3184][2448][D]: MainWindowCallback::slot_DownloadBLoaderProgress(): The total_bytes is 100572(..\..\flashtool\UI\src\MainWindowCallback.cpp,550)
11/24/2018 17:45:39.707 FlashTool[3184][2448][D]: MainWindowCallback::slot_DownloadBLoaderProgress(): The total_bytes is 100572(..\..\flashtool\UI\src\MainWindowCallback.cpp,550)
11/24/2018 17:45:39.723 FlashTool[3184][2448][D]: MainWindowCallback::slot_DownloadBLoaderProgress(): The total_bytes is 100572(..\..\flashtool\UI\src\MainWindowCallback.cpp,550)
11/24/2018 17:45:39.723 FlashTool[3184][2448][D]: MainWindowCallback::slot_DownloadBLoaderProgress(): The total_bytes is 100572(..\..\flashtool\UI\src\MainWindowCallback.cpp,550)
11/24/2018 17:45:39.738 FlashTool[3184][2448][D]: MainWindowCallback::slot_DownloadBLoaderProgress(): The total_bytes is 100572(..\..\flashtool\UI\src\MainWindowCallback.cpp,550)
11/24/2018 17:45:39.754 FlashTool[3184][2448][D]: MainWindowCallback::slot_DownloadBLoaderProgress(): The total_bytes is 100572(..\..\flashtool\UI\src\MainWindowCallback.cpp,550)
11/24/2018 17:45:39.754 FlashTool[3184][2448][D]: MainWindowCallback::slot_DownloadBLoaderProgress(): The total_bytes is 100572(..\..\flashtool\UI\src\MainWindowCallback.cpp,550)
11/24/2018 17:45:39.769 FlashTool[3184][2448][D]: MainWindowCallback::slot_DownloadBLoaderProgress(): The total_bytes is 100572(..\..\flashtool\UI\src\MainWindowCallback.cpp,550)
11/24/2018 17:45:39.785 FlashTool[3184][2448][D]: MainWindowCallback::slot_DownloadBLoaderProgress(): The total_bytes is 100572(..\..\flashtool\UI\src\MainWindowCallback.cpp,550)
11/24/2018 17:45:39.801 FlashTool[3184][2448][D]: MainWindowCallback::slot_DownloadBLoaderProgress(): The total_bytes is 100572(..\..\flashtool\UI\src\MainWindowCallback.cpp,550)
11/24/2018 17:45:39.801 FlashTool[3184][2448][D]: MainWindowCallback::slot_DownloadBLoaderProgress(): The total_bytes is 100572(..\..\flashtool\UI\src\MainWindowCallback.cpp,550)
11/24/2018 17:45:48.410 FlashTool[3184][1664][D]: APCore:ADownloadAll::exec(): Download result(8)(..\..\flashtool\Cmd\DADownloadAll.cpp,72)
11/24/2018 17:45:48.410 FlashTool[3184][1664][D]: APCore:ADownloadAll::exec(): Download failed.(..\..\flashtool\Cmd\DADownloadAll.cpp,83)
11/24/2018 17:45:48.426 FlashTool[3184][1664][D]: APCore::Connection:isconnect(): Disconnect!(..\..\flashtool\Conn\Connection.cpp,155)
11/24/2018 17:45:49.379 FlashTool[3184][1664][D]: BackgroundWorker::run(): BROM Exception! ( ERROR : ?? (8)
[HINT]:
)((APCore:ADownloadAll::exec,..\..\flashtool\Cmd\DADownloadAll.cpp,84))(..\..\flashtool\UI\src\BackgroundWorker.cpp,96)
BROM_DLL_V5.log
11/24/18 17:45:49.363 BROM_DLL[3184][1664]: ERROR: DA_cmd::CMD_Finish(): Error return(3). (FlashToolLib/sv5/common/generic/src/da_cmd.cpp:1084)
11/24/18 17:45:49.379 BROM_DLL[3184][1664]: DEBUG: DA_cmd::CMD_Finish(): OK! (FlashToolLib/sv5/common/generic/src/da_cmd.cpp:1090)
11/24/18 17:45:49.379 BROM_DLL[3184][1664]: ERROR: FlashTool_Disconnect(): (0x026F17D8): da_cmd.CMD_Finish(): fail! (FlashToolLib/sv5/common/generic/src/flashtool_api.cpp:2340)
11/24/18 17:45:49.379 BROM_DLL[3184][1664]: FlashTool_Disconnect(0x026F17D8): mutex: UNLOCK. (FlashToolLib/host/windows/mutex.cpp:158)
11/24/18 17:45:49.379 BROM_DLL[3184][1664]: com_sentry::Close(\\?\usb#vid_0e8d&pid_2001#5&21e739f&0&4#{a5dcbf10-6530-11d2-901f-00c04fb951ed}, 000002A8): OK! (FlashToolLib/host/windows/com_sentry.cpp:663)
11/24/18 17:45:49.379 BROM_DLL[3184][1664]: com_base::~com_base() m_hCOM(FFFFFFFF) (FlashToolLib/host/windows/com_sentry.cpp:122)
11/24/18 17:45:49.379 BROM_DLL[3184][1664]: DEBUG: FlashTool_Disconnect(): successfully done. (FlashToolLib/sv5/common/generic/src/flashtool_api.cpp:2352)
11/24/18 17:45:49.394 BROM_DLL[3184][2448]: RB_ClearAll(): RB_HANDLE->rwlock: WRITE_LOCK ... (FlashToolLib/host/windows/rwlock.cpp:460)
11/24/18 17:45:49.394 BROM_DLL[3184][2448]: RB_ClearAll(): RB_HANDLE->rwlock: WRITE_UNLOCK. (FlashToolLib/host/windows/rwlock.cpp:476)
ADPT..log
[0000152] [17:45:27:582377] [Tid0x00000680] [debug] bCheckScatter: 1 #(api.cpp, line:2021)
[0000153] [17:45:32:613627] [Tid0x00000680] [debug] <--[C72] FlashTool_Connect_Download_DA
[0000154] [17:45:32:613627] [Tid0x00000680] [debug] -->[C73] FlashTool_CheckUSBStatus #(api.cpp, line:1156)
[0000155] [17:45:32:613627] [Tid0x00000680] [debug] <--[C73] FlashTool_CheckUSBStatus
[0000156] [17:45:32:613627] [Tid0x00000680] [debug] -->[C74] FlashTool_SetupUSBDL #(api.cpp, line:1117)
[0000157] [17:45:32:629252] [Tid0x00000680] [debug] <--[C74] FlashTool_SetupUSBDL
[0000158] [17:45:34:348002] [Tid0x00000680] [debug] -->[C75] FlashTool_ChangeCOM_Ex #(api.cpp, line:1095)
[0000159] [17:45:34:348002] [Tid0x00000680] [debug] <--[C75] FlashTool_ChangeCOM_Ex
[0000160] [17:45:34:348002] [Tid0x00000680] [debug] -->[C76] FlashTool_CheckUSBStatus #(api.cpp, line:1156)
[0000161] [17:45:34:348002] [Tid0x00000680] [debug] <--[C76] FlashTool_CheckUSBStatus
[0000162] [17:45:34:348002] [Tid0x00000680] [debug] -->[C77] FlashTool_GetReservedRomSize #(api.cpp, line:1680)
[0000163] [17:45:34:348002] [Tid0x00000680] [debug] <--[C77] FlashTool_GetReservedRomSize
[0000164] [17:45:34:348002] [Tid0x00000680] [debug] -->[C78] FlashTool_RomGetCount #(api.cpp, line:1706)
[0000165] [17:45:34:348002] [Tid0x00000680] [debug] <--[C78] FlashTool_RomGetCount
[0000166] [17:45:34:348002] [Tid0x00000680] [debug] -->[C79] FlashTool_RomGetInfoAll #(api.cpp, line:1732)
[0000167] [17:45:34:348002] [Tid0x00000680] [debug] <--[C79] FlashTool_RomGetInfoAll
[0000168] [17:45:34:348002] [Tid0x00000680] [debug] -->[C80] FlashTool_ReadPartitionCount #(api.cpp, line:1636)
[0000169] [17:45:34:348002] [Tid0x00000680] [debug] <--[C80] FlashTool_ReadPartitionCount
[0000170] [17:45:34:348002] [Tid0x00000680] [debug] -->[C81] FlashTool_Download #(api.cpp, line:1302)
[0000171] [17:45:48:410502] [Tid0x00000680] [debug] <--[C81] FlashTool_Download
[0000172] [17:45:48:426127] [Tid0x00000680] [debug] -->[C82] FlashTool_Disconnect #(api.cpp, line:1035)
[0000173] [17:45:49:379252] [Tid0x00000680] [debug] <--[C82] FlashTool_Disconnect
==========================================
******************************************
==========================================
I am copying here last lines on these logs for task 4) FAILED PMT INFO
QT_FLASH_TOOL.log
11/24/2018 17:36:22.348 FlashTool[3184][2448][D]: OptionDialog::winEvent(): USB Device plug in.(..\..\flashtool\UI\src\OptionDialog.cpp,529)
11/24/2018 17:36:22.363 FlashTool[3184][3092][D]: APCore::Connection:isconnect(): Disconnect!(..\..\flashtool\Conn\Connection.cpp,155)
11/24/2018 17:36:22.613 FlashTool[3184][3092][D]: BackgroundWorker::run(): App Exception! (Failed to get PMT info.)((fw_throw_error,..\..\flashtool\Flow\ErrString.cpp,27))(..\..\flashtool\UI\src\BackgroundWorker.cpp,106)
11/24/2018 17:36:23.754 FlashTool[3184][2448][D]: OptionDialog::winEvent(): USB Device Removed.(..\..\flashtool\UI\src\OptionDialog.cpp,534)
11/24/2018 17:36:24.676 FlashTool[3184][2448][D]: OptionDialog::winEvent(): USB Device Removed.(..\..\flashtool\UI\src\OptionDialog.cpp,534)
BROM_DLL_V5.log
11/24/18 17:36:22.379 BROM_DLL[3184][3092]: FlashTool_Disconnect(0x026F17D8): mutex: UNLOCK. (FlashToolLib/host/windows/mutex.cpp:158)
11/24/18 17:36:22.613 BROM_DLL[3184][3092]: com_sentry::Close(\\?\usb#vid_0e8d&pid_2001#5&21e739f&0&4#{a5dcbf10-6530-11d2-901f-00c04fb951ed}, 00000288): OK! (FlashToolLib/host/windows/com_sentry.cpp:663)
11/24/18 17:36:22.613 BROM_DLL[3184][3092]: com_base::~com_base() m_hCOM(FFFFFFFF) (FlashToolLib/host/windows/com_sentry.cpp:122)
11/24/18 17:36:22.613 BROM_DLL[3184][3092]: DEBUG: FlashTool_Disconnect(): successfully done. (FlashToolLib/sv5/common/generic/src/flashtool_api.cpp:2352)
11/24/18 17:36:24.394 BROM_DLL[3184][2448]: RB_ClearAll(): RB_HANDLE->rwlock: WRITE_LOCK ... (FlashToolLib/host/windows/rwlock.cpp:460)
11/24/18 17:36:24.394 BROM_DLL[3184][2448]: RB_ClearAll(): RB_HANDLE->rwlock: WRITE_UNLOCK. (FlashToolLib/host/windows/rwlock.cpp:476)
ADPT..log
[0000118] [17:36:22:269877] [Tid0x00000c14] [debug] -->[C57] FlashTool_GetReservedRomSize #(api.cpp, line:1680)
[0000119] [17:36:22:269877] [Tid0x00000c14] [debug] <--[C57] FlashTool_GetReservedRomSize
[0000120] [17:36:22:285502] [Tid0x00000c14] [debug] -->[C58] FlashTool_RomGetCount #(api.cpp, line:1706)
[0000121] [17:36:22:285502] [Tid0x00000c14] [debug] <--[C58] FlashTool_RomGetCount
[0000122] [17:36:22:285502] [Tid0x00000c14] [debug] -->[C59] FlashTool_RomGetInfoAll #(api.cpp, line:1732)
[0000123] [17:36:22:285502] [Tid0x00000c14] [debug] <--[C59] FlashTool_RomGetInfoAll
[0000124] [17:36:22:285502] [Tid0x00000c14] [debug] -->[C60] DL_GetCount #(api.cpp, line:2645)
[0000125] [17:36:22:285502] [Tid0x00000c14] [debug] <--[C60] DL_GetCount
[0000126] [17:36:22:285502] [Tid0x00000c14] [debug] -->[C61] DL_Rom_GetInfoAll #(api.cpp, line:2810)
[0000127] [17:36:22:285502] [Tid0x00000c14] [debug] <--[C61] DL_Rom_GetInfoAll
[0000128] [17:36:22:285502] [Tid0x00000c14] [debug] -->[C62] FlashTool_RomGetCount #(api.cpp, line:1706)
[0000129] [17:36:22:285502] [Tid0x00000c14] [debug] <--[C62] FlashTool_RomGetCount
[0000130] [17:36:22:301127] [Tid0x00000c14] [debug] -->[C63] FlashTool_ReadPartitionCount #(api.cpp, line:1636)
[0000131] [17:36:22:301127] [Tid0x00000c14] [debug] <--[C63] FlashTool_ReadPartitionCount
[0000132] [17:36:22:363627] [Tid0x00000c14] [debug] -->[C64] FlashTool_Disconnect #(api.cpp, line:1035)
[0000133] [17:36:22:613627] [Tid0x00000c14] [debug] <--[C64] FlashTool_Disconnect

[ROM][D802][D80220G]Original open eur 80220G kdz to recovery flashable zip

Hello,
This thread just to share two roms I made from original kdz D80220G.
I've tested each, installed from TWRP 2.8.0.1, after wipe system,data,cache and dalvick.
Both can be flashed on 16Go or 32 Go device.
---
The first one is a pure stock rom without root and with the stock recovery,that can be flashed from a custom recovery.
Root and custom recovery will be lost after the flash of this one .
For the root, for my part, I let TWRP 2.8.0.1 do so by following, by accepting the proposal he made to me at my request to reboot system after the flash. I was so easily rooted again.
For the custom recovery, the patched kernel does not yet exist for this version, installing a custom recovery you would lose the benefit of the news that may contain the kernel of this new firmware version.
Download link of this pure stock rom D80220G open eur, without root and with the stock recovery:
https://www.androidfilehost.com/?fid=95747613655046456
---
And the second is the same, but prerooted (SuperSu preinstalled) and allowing to keep the custom recovery.
Custom recovery will be kept after the flash of this one .
It's prerooted and with 20D Knock code Cloudyfa kernel integrated (simple stock KC kernel, just patched).
This pure stock rom D80220G open eur, prerooted and friendly custom recovery can be downloaded here:
https://www.androidfilehost.com/?fid=95784891001602117
---
Thank's to:
@thecubed for his [python][Tool] LG Compressed KDZ Extractor
@cybojenix for his tool (system merger)
@bullghost for his windows GUI version [TOOL] KDZ and TOT Extractor
and for the one prerooted, friendly custom recovery:
@Cloudyfa for the kernel and permission to integrate it, @bender_007 and @citytrader for their advice for the integration of patched kernel, @autoprime for his ioroot25 that inspired the way I proceeded to preroot, @Chainfire for his SuperSu

Can you check if it has Danish language inside for me, please?
And thanks!
Sent from my LG-D802

natalya said:
Can you check if it has Danish language inside for me, please?
And thanks!
Sent from my LG-D802
Click to expand...
Click to collapse
Yep, Dansk language is present and apns.xml includes all Danish operators:
<!--23 Denmark - Telenor 2-->
<apn carrier="Telenor MMS" mcc="238" mnc="02" apn="telenor" user="" server="" password="" proxy="" port="" mmsproxy="212.088.064.008" mmsport="8080" mmsc="http://mms.telenor.dk" type="mms" authtype="0" />
<apn carrier="Telenor Internet" mcc="238" mnc="02" apn="internet" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" authtype="0" />
<!--24 Denmark - TDC 2-->
<apn carrier="TDC MMS" mcc="238" mnc="01" mvno_type="imsi" mvno_match_data="2380101xxxxxxxx" apn="mms" user="" server="" password="" proxy="" port="" mmsproxy="194.182.251.015" mmsport="8080" mmsc="http://mmsc.tdc.dk:8002" type="mms" authtype="0" />
<apn carrier="TDC Internet" mcc="238" mnc="01" mvno_type="imsi" mvno_match_data="2380101xxxxxxxx" apn="internet" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" authtype="0" />
<apn carrier="TDC MMS" mcc="238" mnc="01" mvno_type="imsi" mvno_match_data="2380171xxxxxxxx" apn="mms" user="" server="" password="" proxy="" port="" mmsproxy="194.182.251.015" mmsport="8080" mmsc="http://mmsc.tdc.dk:8002" type="mms" authtype="0" />
<apn carrier="TDC Internet" mcc="238" mnc="01" mvno_type="imsi" mvno_match_data="2380171xxxxxxxx" apn="internet" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" authtype="0" />
<apn carrier="TDC MMS" mcc="238" mnc="01" mvno_type="imsi" mvno_match_data="2380172xxxxxxxx" apn="mms" user="" server="" password="" proxy="" port="" mmsproxy="194.182.251.015" mmsport="8080" mmsc="http://mmsc.tdc.dk:8002" type="mms" authtype="0" />
<apn carrier="TDC Internet" mcc="238" mnc="01" mvno_type="imsi" mvno_match_data="2380172xxxxxxxx" apn="internet" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" authtype="0" />
<!--25 Denmark - Telia 3-->
<apn carrier="Telia MMS" mcc="238" mnc="20" mvno_type="imsi" mvno_match_data="2382010x" apn="www.mms.mtelia.dk" user="" server="" password="" proxy="" port="" mmsproxy="193.209.134.131" mmsport="8080" mmsc="http://mms.telia.dk" type="mms" defaultflag="0" authtype="0" />
<apn carrier="Telia SurfPort" mcc="238" mnc="20" mvno_type="imsi" mvno_match_data="2382010x" apn="www.internet.mtelia.dk" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" defaultflag="0" authtype="0" />
<apn carrier="Telia MMS" mcc="238" mnc="20" mvno_type="imsi" mvno_match_data="2382030x" apn="www.mms.mtelia.dk" user="" server="" password="" proxy="" port="" mmsproxy="193.209.134.131" mmsport="8080" mmsc="http://mms.telia.dk" type="mms" defaultflag="0" authtype="0" />
<apn carrier="Telia SurfPort" mcc="238" mnc="20" mvno_type="imsi" mvno_match_data="2382030x" apn="www.internet.mtelia.dk" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" defaultflag="0" authtype="0" />
<!--119 Denmark - 3DK 2-->
<apn carrier="3" mcc="238" mnc="06" apn="data.tre.dk" user="" server="" password="" proxy="" port="" mmsproxy="mmsproxy.3.dk" mmsport="8799" mmsc="http://mms.3.dk" type="default,mms,dun,supl" defaultflag="0" authtype="0" />
<!--143 Denmark - CBB_Mobil 2-->
<apn carrier="CBB MMS" mcc="238" mnc="02" mvno_type="spn" mvno_match_data="CBB Mobil" apn="telenor" user="" server="" password="" proxy="" port="" mmsproxy="212.088.064.008" mmsport="8080" mmsc="http://mms.telenor.dk" type="mms" authtype="0" />
<apn carrier="CBB Internet" mcc="238" mnc="02" mvno_type="spn" mvno_match_data="CBB Mobil" apn="internet" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" authtype="0" />
<!--144 Denmark - Telmore 2-->
<apn carrier="Telmore MMS" mcc="238" mnc="01" mvno_type="spn" mvno_match_data="TELMORE" apn="mms" user="" server="" password="" proxy="" port="" mmsproxy="194.182.251.015" mmsport="8080" mmsc="http://192.168.241.114:8002" type="mms" defaultflag="0" authtype="0" />
<apn carrier="Telmore Internet" mcc="238" mnc="01" mvno_type="spn" mvno_match_data="TELMORE" apn="internet" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" defaultflag="0" authtype="0" />
<!--145 Denmark - Call_me 2-->
<apn carrier="Call me MMS" mcc="238" mnc="20" mvno_type="spn" mvno_match_data="Call me" apn="mmsSP" user="" server="" password="" proxy="" port="" mmsproxy="193.209.134.131" mmsport="8080" mmsc="http://mms.telia.dk" type="mms" defaultflag="0" authtype="0" />
<apn carrier="Call me Internet" mcc="238" mnc="20" mvno_type="spn" mvno_match_data="Call me" apn="webSP" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" defaultflag="0" authtype="0" />
<!--177 Denmark - DLG_Tele 2-->
<apn carrier="DLG Tele MMS" mcc="238" mnc="20" mvno_type="spn" mvno_match_data="DLG Tele" apn="mmsSP" user="" server="" password="" proxy="" port="" mmsproxy="193.209.134.131" mmsport="8080" mmsc="http://mms.telia.dk" type="mms" defaultflag="0" authtype="2" />
<apn carrier="DLG Tele GPRS" mcc="238" mnc="20" mvno_type="spn" mvno_match_data="DLG Tele" apn="webSP" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" defaultflag="0" authtype="0" />
<!--224 Denmark - BiBoB 1-->
<apn carrier="BiBoB" mcc="238" mnc="02" mvno_type="spn" mvno_match_data="BiBoB" apn="telenor" user="" server="" password="" proxy="" port="" mmsproxy="212.088.064.008" mmsport="8080" mmsc="http://mms.telenor.dk" type="mms" defaultflag="0" authtype="0" />
<apn carrier="BiBoB Internet profil" mcc="238" mnc="02" mvno_type="spn" mvno_match_data="BiBoB" apn="internet" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" defaultflag="0" authtype="0" />

6ril1 said:
Hello,
This thread just to share this rom I made from original kdz D80220G.
it is a pure stock rom without root and with the stock recovery, that can be flashed from a custom recovery.
Root and custom recovery will be lost after the flash.
For the root, for my part, I let TWRP 2.8.0.1 do so by following, by accepting the proposal he made to me at my request to reboot system after the flash. I was so easily rooted again.
For the custom recovery, the patched kernel does not yet exist for this version, installing a custom recovery you would lose the benefit of the news that may contain the kernel of this new firmware version.
I've installed this rom from TWRP 2.8.0.1, after wipe system,data,cache and dalvick
Download link:
https://www.androidfilehost.com/?fid=95747613655046456
Thank's to:
@thecubed for his [python][Tool] LG Compressed KDZ Extractor
@cybojenix for his tool (system merger)
@bullghost for his windows GUI version [TOOL] KDZ and TOT Extractor
@somboons for his thread [GUIDE-VDO] How to make your own KitKat ROM with Root+TWRP from KDZ
Click to expand...
Click to collapse
This can be flashed via Custom Recovery on D802 ??

i wonder whats new and impoved in this version of stock rom

whats new??

-iNCEPTiON- said:
This can be flashed via Custom Recovery on D802 ??
Click to expand...
Click to collapse
Yes (wipes recommended), and you will lose your custom recovery and root after the flash.
You can then root after with ioroot, but for the custom recovery, if you want to install it again, you will lose the potential benefit of the new kernel of 20G.
If you have TWRP 2.8.0.1, it will propose you to root when you'll ask the reboot after flashing. If you accept, you'll be invited to install supersu after the boot.
It's a pure stock rom, without root, and without patched kernel for keeping recovery.
shriom_manerker said:
i wonder whats new and impoved in this version of stock rom
Click to expand...
Click to collapse
No idea. The vulnerability exploited by Towelroot seems to be patched (i 've not tried, but it's said in this thread http://forum.xda-developers.com/lg-g2/general/d80220g-update-t2904346), stock recovery is accessible, so ioroot works.
This post links a binary comparaison http://forum.xda-developers.com/showpost.php?p=56019091&postcount=45.
In France many people complained of a bug on the 20f, about inadvertent switch between silent mode and normal mode. Those high expectations of an update, but I have not read back on this 20G, if it solved the problem. Probably too early.
For my part, I was in 20f and have not found the bug in question.
For now I have not encountered any problem with this 20g

6ril1 said:
you will lose the potential benefit of the new kernel of 20G.
Click to expand...
Click to collapse
What you meant with that?
Enviado desde un lugar muy muy lejano con mi D806

For having custom recovery with kitkat d802, you must downgrade bootloader and have a patched kernel for booting behind downgraded bootloader.
And patched 80220G kernel doesn't exist yet.
So if you put a custom recovery on this 20G, you have to use older patched kernel.

6ril1 said:
For having custom recovery with kitkat d802, you must downgrade bootloader and have a patched kernel for booting behind downgraded bootloader.
And patched 80220G kernel doesn't exist yet.
So if you put a custom recovery on this 20G, you have to use older patched kernel.
Click to expand...
Click to collapse
Does this mean I cannot install recovery on v20g with autorec (errors, fail, brick device...)? Or it means I can however use autorec to install recovery and it will work, even if loosing benefits of v20g?

has anybody tried Auto Rec by Cloudyfa with this 20G rom?

zekurosu said:
has anybody tried Auto Rec by Cloudyfa with this 20G rom?
Click to expand...
Click to collapse
I tried it and it worked without problem.

titomax82 said:
Does this mean I cannot install recovery on v20g with autorec (errors, fail, brick device...)? Or it means I can however use autorec to install recovery and it will work, even if loosing benefits of v20g?
Click to expand...
Click to collapse
I think he means that autorec will flash a kernel with that patched, but it won't be the g version it will be an old version, so we are not gonna have all improves from g version
Enviado desde un lugar muy muy lejano con mi D806

titomax82 said:
Does this mean I cannot install recovery on v20g with autorec (errors, fail, brick device...)? Or it means I can however use autorec to install recovery and it will work, even if loosing benefits of v20g?
Click to expand...
Click to collapse
Tinchoska said:
I think he means that autorec will flash a kernel with that patched, but it won't be the g version it will be an old version, so we are not gonna have all improves from g version
Click to expand...
Click to collapse
That's exactly what I mean, yes.
The patched kernel can only be produced if the sources were published, and it is not the case for 20G. The latest version released back to the 20D.
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=d802
However the latest patched kernel available (the one containing knock code) should work fine.
But if changes (improvements) were made on the 20G (I do not know if this is the case), the benefit of these innovations would be lost with the installation of an older kernel (20D).
Note: It was the same situation with the 20f.
Brief ...
Yes AUTOREC should work fine, but it will install an older kernel

then it should not be an issue because we can always flash latest twrp & dorimanx kernel :good:
as of now im enjoying stock 20G thanks to you mate :good:

If I backup my current v20g stock kernel with flashify,
then use autorec to install recovery,
then I restore my previous saved stock kernel with flashify,
will work? Or do I need necessarily a patched v20g?

Thanks for this rom. It would have been great to have removed some of Google apps and added xdabbeb camera. But so far so good.

titomax82 said:
If I backup my current v20g stock kernel with flashify,
then use autorec to install recovery,
then I restore my previous saved stock kernel with flashify,
will work? Or do I need necessarily a patched v20g?
Click to expand...
Click to collapse
Don't do that !
You must have a patched kernel for booting behind downgraded bootloader (downgraded bootloader is required for having custom recovery, because LG have patch loki exploit with 4.4.2 bootloader).
You don't need a patched kernel in a 20G version, just a patched kernel.
On another subject, I edited OP for giving a link to a post, where I give links to LG server for originals 20G kdz

Thanks for the advise, I was already thinking that, but someone on other thread said it was good... but I had my doubts and you confirm them. I'm a little confused by this statment:
6ril1 said:
You don't need a patched kernel in a 20G version, just a patched kernel.
Click to expand...
Click to collapse
I'm not sure that I understood...

titomax82 said:
I'm not sure that I understood...
Click to expand...
Click to collapse
20G patched kernel doesn't exist, so when you ask
Or do I need necessarily a patched v20g?
Click to expand...
Click to collapse
I answer: no, you need just a patched kernel, not in a 20G version (not a 20G patched kernel).

LG G4 Bricked Qualcomm HS-USB QDLoader 9008

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.

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

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