[GUIDE] Proper H815 unbrick through QFIL (Files included)

[mir2480]

after doing the process with the flashing files I can not enter the download mode that may have happened

 

[steadfasterX]

Done 15 times and nothing. With and without battery.
I taking less than 1 sec to press download button when Qualcomm is detected.

Nop 14 is the step when we trying to write in memory right ? So i think my memory is crap

Thanks a lot for your answer !

dont just "say" thanks (there is also a button..)

strange. the error is very unusual and yes it can not communicate with the firehose running in memory.
then try the sdcard unbrick (see my signature)

.

 

[sminuk]

Archive can't be downloaded

Unfortunately the link in the first post is not working anymore (G4-h815_fullunbrick_working_7a3ae5809224d.zip).
Could somebody provide a new link?

I have a strange problem:
my phone (H815P) still boots to lineageos USU. However the left side of the screen is not updated proberly. At the beginning is only noise and then it stays with old screen datas.
Furthermore I can't get to fastboot nor download mode. However recovery mode is still working (twrp for usu). But there is also the half screen problem.
That happens after I tried the command fastboot oem device-id (after I UsUed my G4). Could that have a relation?

Could I flash the usu files (iaf, resource....) with twrp?

Thanks for help.

 

[steadfasterX]

Unfortunately the link in the first post is not working anymore (G4-h815_fullunbrick_working_7a3ae5809224d.zip).
Could somebody provide a new link?

I have a strange problem:
my phone (H815P) still boots to lineageos USU. However the left side of the screen is not updated proberly. At the beginning is only noise and then it stays with old screen datas.
Furthermore I can't get to fastboot nor download mode. However recovery mode is still working (twrp for usu). But there is also the half screen problem.
That happens after I tried the command fastboot oem device-id (after I UsUed my G4). Could that have a relation?

Could I flash the usu files (iaf, resource....) with twrp?

Thanks for help.

The link is working perfectly. It serves on port 8008 which may is blocked in your environment though.
You can use the mirror link here (can be much slower to download): https://www.androidfilehost.com/?fid=1322778262904000036

You can flash the UsU files with TWRP. Just read the UsU FAQ.
What you see sounds 90% like a hardware defect though.

.

 

[sminuk]

Ok. A strange thing I noticed is that there is no LG logo anymore (not even half).
I'm going to read the UsU faq. Thanks for your super fast answer!

 

[steadfasterX]

Ok. A strange thing I noticed is that there is no LG logo anymore (not even half).
I'm going to read the UsU faq. Thanks for your super fast answer!

then your raw_resources partition is corrupted so re-flashing the 3 UsU partitions should solve at least that (if no other hardware defects exists)

.

 

[DennisO8]

Hi SteadfasterX, I am about to try and unbrick my UsU'd H815 after mistakenly flashing a non-UsU rom. Just a couple questions per step as I want to make sure I get it right and not make it any worse...
Step 1. There are 2 zip files there G4-fix-dl-mode_H815_7a3ae5809224d.zip & G4-h815_fullunbrick_working_7a3ae5809224d.zip, which do I use for my UsU'd H815?
Step 2. In the "software_drivers" folder there are 2 folders QPST.WIN.2.7 (which installed fine) and qhsusb_dload_drivers which I cannot install in Win10 as the drivers are not signed and in Win7x86 (with driver signing disabled) the Qualcomm_QDLoader_32bit_Driver.inf fails to install with "An error occurred during the installation of the device. Driver is not intended for this platform." How do I install this driver?
Thanks for your help so far.

 

[steadfasterX]

Hi SteadfasterX, I am about to try and unbrick my UsU'd H815 after mistakenly flashing a non-UsU rom. Just a couple questions per step as I want to make sure I get it right and not make it any worse...
Step 1. There are 2 zip files there G4-fix-dl-mode_H815_7a3ae5809224d.zip & G4-h815_fullunbrick_working_7a3ae5809224d.zip, which do I use for my UsU'd H815?
Step 2. In the "software_drivers" folder there are 2 folders QPST.WIN.2.7 (which installed fine) and qhsusb_dload_drivers which I cannot install in Win10 as the drivers are not signed and in Win7x86 (with driver signing disabled) the Qualcomm_QDLoader_32bit_Driver.inf fails to install with "An error occurred during the installation of the device. Driver is not intended for this platform." How do I install this driver?
Thanks for your help so far.

The file you need is: G4-h815_fullunbrick_working_7a3ae5809224d.zip
Windows 10 (with current updates) do not need any additional drivers anymore (it seems) so you are good to skip that step (on win10).

.

 

[netready]

The file you need is: G4-h815_fullunbrick_working_7a3ae5809224d.zip
Windows 10 (with current updates) do not need any additional drivers anymore (it seems) so you are good to skip that step (on win10).

.

Thanks Maan! I got it done and have unbricked my beloved H815 so I am wrapped! Thanks again :good:. Just a couple of pointers about the steps for this, did you realise you have 2x step 3s? Also with step 4 the newer QFIL app has new options "Flat Build" (the one we want) and "Meta Build". Also the "Select Programmer" option needs to be browsed to the "...flashing\prog_emmc_firehose_8992_lite.mbn" (which isn't mentioned) as well as the "Select Build" to the "...flashing" folder, followed by "Load XML" to "flashing\rawprogram0.xml" & "flashing\patch0.xml" (none of which is clearly stated for us newbys). Your screen shot in this step shows the "Select Programmer" & "Select Build" options as blank but the "Load XML..." and "Download" buttons are not activated until the previous paths are selected.

Anyway I was able to work my through it regardless and the result is awesome! Have now installed the stock Nougat UsU rom and it's running perfect! Thanks again for your hard work!:victory:

 

[iannisb]

I had to modify the xml files , thats how it works!

 

[netready]

I had to modify the xml files , thats how it works!

Only if you don't rename the files to match the existing XML.

 

[bilal_law]

Secure booting error after sd card unbrick method

I bought used h811, but it has issue of restarting every time I tired to uninstall any app or tried to go to security setting. So I decided to downgrade it (I have no idea about ARB at that time), the device show h811-21y, So I download h811-10n firmware & use lgup to downgrade after it complete 100% it get bricked, and show qualcomm 9008 on the PC. I then open the device and found out it is h810 written on the motherboard.
I tried almost every qfil mbn files present on the internet but failed.
Then I tired this firmware
LGH810AT-01-V21y-310-410-JUN-20-2016-ARB03+0.rar
and use this youtube method to create raw programme & patch
watch?v=RhG02kmSelk
Then I use sd card method as this youtube method suggest
watch?v=kX2Fm1zEx5E
my device show sign of life but stuck in "secure booting error 1009"
At that point I am totally stuck since I does not get any help with this error on the internet

 

[osimobile]

Hi!
I have bought a used LG G4 H815 Int or EU version via Ebay. (I am in Europe.)
It seems to be a quite new Device, the S/N is starting with 609.
I opened it to make sure it is not a Frankenstein-Device.
It was not booting and only got detected in the PC as Qualcomm HS-USB QDLoader 9008 Device after shortening the pins as described here, I tried using this QFIL-Method like in page 1 of this thread.

It seems like QFIL was successful, as you can see in my bpasted QFIL-log here:
https://bpaste.net/show/47f446a9282c

But unfortunately after turning it on, it got stuck at the LG Bootlogo with the message:
[980] _________________________
[1030]
[1080] Secure Booting Error!
[1130] Error Code : 1014
[1180]
[1230] _________________________
Shortly after, it automatically reboots...

With the Volume-Up button pressed and plugging in the cable I am able to enter Download Mode, where the same Secure Booting, Error 1014 message, is displayed, followed by rebooting too.
Unfortunately the PC is not detecting the Device in Download Mode otherwise I could maybe flash a Rom...

I did not find a lot of Info about the Error Message, except this Video where someone fixed this Error Message, which looks like a professional QFIL to me: https://www.youtube.com/watch?v=_DX5fxN2sSY.

Since it seems to be a software only problem, I would highly appreciate any help.
Thank you for your hints and ideas!

 

[steadfasterX]

Hi!
I have bought a used LG G4 H815 Int or EU version via Ebay. (I am in Europe.)
It seems to be a quite new Device, the S/N is starting with 609.
I opened it to make sure it is not a Frankenstein-Device.
It was not booting and only got detected in the PC as Qualcomm HS-USB QDLoader 9008 Device after shortening the pins as described here, I tried using this QFIL-Method like in page 1 of this thread.

It seems like QFIL was successful, as you can see in my bpasted QFIL-log here:
https://bpaste.net/show/47f446a9282c

But unfortunately after turning it on, it got stuck at the LG Bootlogo with the message:
[980] _________________________
[1030]
[1080] Secure Booting Error!
[1130] Error Code : 1014
[1180]
[1230] _________________________
Shortly after, it automatically reboots...

With the Volume-Up button pressed and plugging in the cable I am able to enter Download Mode, where the same Secure Booting, Error 1014 message, is displayed, followed by rebooting too.
Unfortunately the PC is not detecting the Device in Download Mode otherwise I could maybe flash a Rom...

I did not find a lot of Info about the Error Message, except this Video where someone fixed this Error Message, which looks like a professional QFIL to me:

.

Since it seems to be a software only problem, I would highly appreciate any help.
Thank you for your hints and ideas!

Yes qfil flashing went fine.

There is a good chance you were on LP before ?!
It MIGHT be a problem due to different partition tables. Very unlikely while possible - depending on the real model.

The video shows Medusa which is a special box for operations like this. In parts it does what qfil do and some more stuff.

Just to have it said (as I said it billion of times in the past):
do not run around and search for other QFIL files ! There are evil ones out there which will convert your device without a way of return .

Ok back to your issue:
You could flash the gpt but for this you would need a box like Medusa or Infinity.
As that means high costs I would try this instead:

Use SALT (see my sig) to extract the same partitions as you can find in my qfil package from a h815 lollipop kdz. Note: emmc_appsboot = aboot partition. Put them into the flashing dir and flash these with qfil .




Sent from my OnePlus 6T using XDA Labs

 

[osimobile]

There is a good chance you were on LP before ?!
[...]
Use SALT (see my sig) to extract the same partitions as you can find in my qfil package from a h815 lollipop kdz. Note: emmc_appsboot = aboot partition. Put them into the flashing dir and flash these with qfil .

Thanks a lot for your fast and detailed answers stadfasterX!
I will try out your idea about LP and report back.
So I will replace all the exact partitions existing in your flashing folder with those extracted from a Lollipop KDZ.
But one thing is unclear to me.
What do you mean with your note? (emmc_appsboot = aboot partition)
Does that mean i need to use the Lollipop emmc_appsboot as the aboot in QFIL? (Means renamed or path changed accordingly)

 

[steadfasterX]

Thanks a lot for your fast and detailed answers stadfasterX!
I will try out your idea about LP and report back.
So I will replace all the exact partitions existing in your flashing folder with those extracted from a Lollipop KDZ.
But one thing is unclear to me.
What do you mean with your note? (emmc_appsboot = aboot partition)
Does that mean i need to use the Lollipop emmc_appsboot as the aboot in QFIL? (Means renamed or path changed accordingly)

Yes you need to rename the aboot file which you extract from the LP kdz to the emmc.... name (exactly name it like the current one).
also for the rest ensure you have the exact filenames like they are currently in the flashing folder . I would copy the whole flashing folder and then add the lollipop ones there and rename endings when needed .




Sent from my OnePlus 6T using XDA Labs

 

[osimobile]

Hi steadfasterX!
I am running FWUL and SALT fine, thank you for these awesome tools (I left a Thank You there too), but I am struggeling with finding all the files.
I tried finding the needed files in 2 different LP roms I extracted so far (Europe OPEN H81510D.kdz , and H815_EU_10C_00.kdz).
Since I could not find all of the files from your flashing folder in those roms, I researched and found your other thread, for flashing from sd card without QFIL, where you mention that only a few partitions would be needed in that particular SD-Card case.
Is this the case here too? And do I only need to replace the following quoted files? (I did find those ones easily already.)

(Reader be careful, the following Quote belongs to a different thread! And on a mobile device the list may be incomplete due to the quote being minimized for optimized reading!)

How to unbrick by sdcard from 9008 without QFIL
[...]
[*]3. Extract the KDZ but not all partitions are needed - just these:

• Primary GPT
• sbl1
• aboot
• pmic
• rpm
• tz
• laf
• sdi
• hyp

[...]

Thanks for your patient help again,
cheers, Osimobile

 

[osimobile]

Yes you need to rename the aboot file which you extract from the LP kdz to the emmc.... name (exactly name it like the current one).
also for the rest ensure you have the exact filenames like they are currently in the flashing folder . I would copy the whole flashing folder and then add the lollipop ones there and rename endings when needed .

Hi!
Like I wrote in my last post, I am struggeling with finding all the files I need to replace in the flashing folder.
I tried extracting the roms myself from the two above mentioned roms, and also from "Europe General H81510B_00.kdz" by now, but they are always missing some files inside/ or I just don´t know it better (If I really have to substitute all the exact files from the flashing folder, which I assume).

The closest match was this LP Stock Rom served by autoprime [url]http://downloads.codefi.re/autoprime/LG/LG_G4/H815/H81510C[/URL] found in this thread: [url]https://forum.xda-developers.com/g4/development/stock-h815-20a-stock-images-kdz-t3232282[/URL].

But it is still missing the files ramdisk and misc.
As well as gpt_both0.bin, gpt_main0.bin, gpt_empty0.bin, NON-HLOS.bin and superboost_header.bin which I can´t find in all of these roms.
How should I handle this problem?
I just dont want to make it worse, thats why I am asking again before flashing into the blue
All the best and a good weekend,
cheers Osimobile

 

[steadfasterX]

Hi!
Like I wrote in my last post, I am struggeling with finding all the files I need to replace in the flashing folder.
I tried extracting the roms myself from the two above mentioned roms, and also from "Europe General H81510B_00.kdz" by now, but they are always missing some files inside/ or I just don´t know it better (If I really have to substitute all the exact files from the flashing folder, which I assume).

The closest match was this LP Stock Rom served by autoprime [url]http://downloads.codefi.re/autoprime/LG/LG_G4/H815/H81510C[/URL] found in this thread: [url]https://forum.xda-developers.com/g4/development/stock-h815-20a-stock-images-kdz-t3232282[/URL].

But it is still missing the files ramdisk and misc.
As well as gpt_both0.bin, gpt_main0.bin, gpt_empty0.bin, NON-HLOS.bin and superboost_header.bin which I can´t find in all of these roms.
How should I handle this problem?
I just dont want to make it worse, thats why I am asking again before flashing into the blue
All the best and a good weekend,
cheers Osimobile

First of all: thanks for your patience. I needed some spare time to investigate the files so it took a bit. I don't wanted to post before I had the chance to do that so..

here comes the listing:

/flashing/emmc_appsboot.mbn => aboot
/flashing/gpt_backup0.bin => KEEP
/flashing/gpt_both0.bin => KEEP
/flashing/gpt_empty0.bin => KEEP
/flashing/gpt_main0.bin => KEEP
/flashing/hyp.mbn => hyp
/flashing/laf.img => laf
/flashing/misc.img => NOT NEEDED
/flashing/NON-HLOS.bin => modem
/flashing/persist.img => persist
/flashing/pmic.mbn => pmic
/flashing/ramdisk.img => NOT NEEDED
/flashing/raw_resources.img => raw_resources
/flashing/rct.img => NOT NEEDED
/flashing/recovery.img => recovery (or TWRP image when unlocked)
/flashing/rpm.mbn => rpm
/flashing/sbl1.mbn => sbl1
/flashing/sdi.mbn => sdi
/flashing/sec.dat => NOT NEEDED
/flashing/superboost_header.bin => NOT NEEDED
/flashing/tz.mbn => tz

So to resume:

now clone the "/flashing" folder and keep everything in there but replace as written above.
For this simply extract a KDZ - but use SALT! - and ensure you rename the file extension like the original one afterwards

.-

 

[osimobile]

Hi steadfasterX!

Thank you so much for your patience and the perfectly clear answer!
Sorry I am repying this late, but I wanted to try all three above mentioned LP stock roms first. (EU B, C, D).
So I extracted the necessary files, renamed some if needed and replaced them with those in the flashing folder.
All of the three variants of the flashing folders (LP EU B, C, D) flashed successfully in QFIL.

But unfortunately nothing changed on the phone...

Means I still see the Secure Boot Error 1014 message and the phone reboots automatically.
I don't know if it reboots because of this error message, or if it caught the hardware bootloop problem...

Also I can enter the download mode with button up pressed and connecting the cable, but it won't get recognised by the pc and reboots shortly after displaying the secure boot error 1014 message.
So I can't flash the complete rom.

Since the Phone seems tho be one of the newer ones, starting with 609, I don't know, If I it might be worth trying the same fixing attempt with extractions from newer stock roms? (MM versions)

Or if finding a repairshop with a box could really fix it?

Or If I have to give up on the device?

Anyways I am very grateful for your efforts helping me to revive my phone! Thank you steadfasterX!
All the best!