yashsingh1/xdaforums huggingface dataset:
[G4 General] steadfasterX:
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 .
[G4 General] 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!)

Thanks for your patient help again,

cheers, Osimobile
[G4 General] osimobile:
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://xdaforums.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
[G4 General] steadfasterX:
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:

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

.-
[G4 General] 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!
[G4 General] steadfasterX:
Thats REALLY odd as the secure boot error should disappear at least when you boot to download mode! strange.

you have still several options to go. One would be UsU which means post #2 of this thread would be needed to achieve this but before doing that understand the whole good and bad of UsU.

After UsU'ing it should work 99,7 % ;) but it cannot be unlocked anymore officially afterwards and you cannot remove UsU ofc.

So the other option would be to flash the system and boot partitions also with QFIL. That requires to change the rawprogrammer xml but then its possible too. I fear it will still not allow to boot up but there is a chance.

The other chance is to find someone with such a box and flash all partitions of the KDZ with it instead of QFIL but still ..

I mean there is good and bad here:

good: it turns on after QFIL so PBL is accepting your bootloader stack! your GPT is fine! good!

bad: aboot loads but rejects booting

a secure boot error means: aboot rejects to boot as there was a modification detected in your system. this happens e.g. when you unlock, root, then untick the OEM unlock option in the developer options and BAM. Of course there are dozens of other ways to hit that.

the strange thing is: LAF (so download mode) should load anyways as it get flashed in its original state by QFIL! well hm... LAF will mount /system so maybe there is even a check for that here..

So what I would try first if I were you is to flash boot and system partitions via either QFIL (i guess nobody else then a few would know how to mod the xml though) or by a box.

I have such a box ofc :P but I may have not much time the next days. You can try by joining IRC (see the SALT, UsU, FWUL threads on the topic "Support" there) from Mondays-Fridays and hit me there. If I am on I may can help you there.

The other option is UsU and well the h815 is known to work very well with UsU but it still has drawbacks (especially as you can not backup before) which you have to know before (FAQ shows all).

so far ..

.-
[G4 General] osimobile:
Wow thanks again steadfasterX!

For me this is good news!

I wouldn´t have thought that I still have options!

1. QFIL

2. UsU

3. Box

Ok. I like to try flashing system and boot with QFIL

So does that means I need to act like before and also extract

boot.img and

system.img

along with the other partitions from the LP stock rom and add it to the flashing folder to replace the files and rename them accordingly?

Or do I start from your original flashing folder (from post 1) and ectract boot and system from a MM stock rom which I then add to the flashing folder?

Hmm... Ok you say it is hard to configure and change the xml of the firehose accordingly... So this means the whole option is no option anymore ;)

Since I don´t want to bother you anymore. And if it goes beyond changing paths´I might not be able to do it on my own.

But there remains the

2. option UsU!

In this case I would boot up FWUL, open SALT and run the "Unlock G4 (UsU)" button. Unlocked this way,

I could return to QFIL and flash with the UsU files from the 2nd post of this threat here.

Now it should be all good and I hopefully am able to reach download mode and can flash TWRP and a UsU compatible custom rom!

If this could work I would totally be happy!!!

One thing I read though in your UsU threat is that you say the device must be on MM, which I am not certain about. But maybe I can still do it and afterwards follow your FAQ #20 which explains how to update the bootloader to MM later.

Well, the only left catch is, if SALT will be able to UsU my device, since it doesn´t recognize it so far. (I can only make it appear in device manager as "Qualcomm HS-USB QDLoader 9008" device after shortening the pins and SALT is asking for download mode explicitly at start...).

I am really thankful for your great help so far and wish you a great weekend!
[G4 General] steadfasterX:
For UsU you would download the UsU package for the h815 and read and follow post #2 of this thread here to flash UsU by QFIL.

It doesn't matter if you're on MM or not as you can easily upgrade the bootloader stack after UsUing. On my leech server there is a TWRP flashable file for that for UsU devices .

(Having MM before UsU is mostly a precaution)
[G4 General] osimobile:
Thank you!

Great, that makes it even more easy!

Nice, I will try it and report back.

Cheers!
[G4 General] osimobile:
OK, this is what I´ve done:

1. I replaced the needed files in the flashing folder with the ones from the UsU unlock zip and renamed them so the hose file could find them.

Now I shortpinned the device to get it detected in QFIL and flashed the for UsU prepared flashing folder successfully!

When I now start the device it still gets the secure boot error (This was made clear in the UsU threat), but now saying code 1009... But... When I do as advised in the UsU threat and unplug the cable from the pc, take the battery out and back in, and while pressing volume down button and holding it plug the cable back in...

I get into fastboot mode!!!!! :laugh::good: (Thank you!!!)

It says:

[...]

secure boot - disabled

lock state - locked

[1120]

[1170] Fastboot mode started

[2780] fastboot: processing commands

:D:good:

The next step (2.), flashing the TWRP with fastboot in the console via

"fastboot flash recovery twrp-3.2.3-PREVIEW-144_g4_O.img"

as described is flashing successfully, but I somehow can not get into it.

I tried several times with the advised technique, with flashing TWRP again after every try, but could not enter.

When I flash twrp the terminal says sending and writing was OKAY and is finished with displaying the time it took to succeed.

On the device the last row says:

[...]

[592460] fastboot: flash:recovery

But trying to boot up into TWRP just is not possible.

Instead it shows me as written in the UsU threat the

Secure booting error.

This time with code 1002

OFFICIAL!

and the LG boot logo.

Shortly after it reboots and changes the code to 1009. Afterwards it is rebooting and rebooting.

Fastboot mode works without automatic rebooting though.

How to proceed from there?

I thought maybe this is the strange behaviour, in case I don´t have the MM bootloader stack, and I need to flash it from an extracted MM KDZ, but you wrote:

"4) If you want to flash a MM or N modem partition (aka firmware) you need to re-flash <model>_UsU_basebands_flash-in-twrp.zip otherwise you will bootloop, stuck on boot or see a blue screen with a modem crash (this may change if I ever get my kernel module working...)" Quote from steadfasterX in the UsU threat.

And since I can not enter TWRP to flash the UsU basebands zip, I am scared to do so.

Otherwise I would take a MM KDZ with Arb = 0 and extract via SALT and flash like you wrote in the UsU threat these files:

fastboot flash factory factory.bin

fastboot flash hyp hyp.bin

fastboot flash modem modem.bin

fastboot flash pmic pmic.bin

fastboot flash rpm rpm.bin

fastboot flash sbl1 sbl1.bin

fastboot flash sdi sdi.bin

fastboot flash sec sec.bin

fastboot flash tz tz.bin

I just dont want to hard brick it when I can not twrp the baseband zip afterwards...

This is my progress thank you so far steadfasterX!

Have a good day!
[G4 General] steadfasterX:
Don't mess with the bootloader (yet).

It MUST work to boot into TWRP . Follow the steps to boot into recovery in the UsU thread EXACTLY .

If it still fails to load flash the ILAPO TWRP version!!! If that one boots .. You have an ilapo affected device .
[G4 General] osimobile:
Well, I could not boot into TWRP, I followed your instructions in the UsU threat very precisely.

Then I decided to flash your ILAPO TWRP and did it.

So I successfully fastboot flashed

ILAPO-4cpu_twrp-3.2.3-PREVIEW-144_g4_O.img

but it didn't work booting to it, so I also tried flashing

ILAPO-2cpu_twrp-3.2.3-PREVIEW-144_g4_O.img

but it didn't work out either...

I guess that´s it with my device. :crying:

Thank you for your patient help, all your good ideas and efforts! :good:

I´ll send some server fuel ;)

Have a good weekend!
[G4 General] steadfasterX:
Well it's also possible that you have a physical defect like a button not working. Try to flash the ilapo TWRP to the BOOT partition instead of the recovery and simply let it boot. Does that work ?
[G4 General] osimobile:
It's not working either. (2 and 4 CPU version of ILAPO TWRP tested) :(
[G4 General] steadfasterX:
Well ... I'm sorry then . It may be still the ilapo though so if you like just call LG even when without guarantee and maybe you have luck .....

It you wanna do so write me a PM or come to IRC next week and I can give some tips.
[G4 General] greedo85:
It worked for my H815 with UsU - thanks a lot :) Is there any chance You could help me with bootloop? I have unlocked my H815 with usu, flashed twrp but cannot enter it. Vol down + power shows only "Recovery mode loading...." and then reboots. I have managed to enter TWRP twice, accidentally I guess. I flashed twrp from platform-tools, chose fastboot reboot recovery and then it entered TWRP for a while, but also rebooted. Now I can't do anythink except watching bootloop with "Secure booting error - error code: 1002 OFFICIAL!!". What else can I do? As far as I know I can't flash stock KDZ due to UsU, I can't flash any custom due to unable to TWRP boot :/
[G4 General] steadfasterX:
Do you had flashed the ilapo TWRP version ?
[G4 General] greedo85:
ilapo? Never heard of it... I managed to enter TWRP in a strange way, removing battery with cable connected, then immediatelly puting it back. But when I try to flash roms, they flash, but still stuck on LG logo after reboot... On one ROM (Verizon for UsU) I got memory error with blue led light. Can You guide me how to install correct TWRP and correct ROM? I would be greateful for Your help.

Just to add, firmware was stock 29a so I guess its Nougat. I was able to boot it before on stock, then it probably has updated.
[G4 General] steadfasterX:
If you never heard about ilapo .. Then its time ..

Read the topic "about" here:

https://bit.do/ilapofixg4

In the same OP you will find the ilapo TWRP linked in the topic "Precautionary measure". Plus the guide to create your own boot images for the ilapo
[G4 General] greedo85:
Damn, I was afraid of that. I have already tried "freezer method", it worked for entering download mode :( . Will give a chance to other ones, but just for other lost riders: is You have to enter TWRP in such a case in H815 with UsU, when stuck on LG logo, remove battery with cable connected, immediately put it back and You should see TWRP.

[MENTION=5545101]steadfasterX[/MENTION] will any of these methods allow me to flash and boot some ROM?
[G4 General] steadfasterX:
When the freezer works for you you have 100% catch by the ilapo . So even when your device is out of guarantee you should contact LG to do a replacement because of this defect. They confirmed that they will do it even when the Warranty is over. So give that a try at least. The next thing you can do is what I recommended already so flash that ilapo TWRP version . Select the ROM of your choice and extract the boot image out of it. Create your own ilapo boot image from this as described in the linked guide. Flash the ROM and flash your ilapo boot image and hope that it will work. Again this can be only a temporary fix and it may work or not depending on how bad the device state is already.
[G4 General] psilocybindmt47:
usu compatible unbrick via QFIL!

https://xdaforums.com/g4/help/guide-h815-unbrick-via-qfil-miraclebox-t3919696
[G4 General] steadfasterX:
this guide here is compatible with UsU. See post #2. No need for a box.

-.
[G4 General] pixapo:
I could revive my h815 with your awesome tuto, thx. Now I'm getting error 7 while flashing LOS ROM which I guess is name related because it changed to chinees symbols in windows device manager. Must I rename the phone, edit the updater.script in the ROM, or perhaps flashing the appropriated bootloader? Some advise would be appreciated.
[G4 General] steadfasterX:
UsU device ? use SALT to UsU again or flash the UsU files in TWRP .

No UsU device ? Flash the latest unofficial TWRP
[G4 General] pixapo:
Flashed the UsU files and could install LOS ROM, gapps and magisk but rebooting it stops showing 'invalid RAM consolé'. Any idea?
[G4 General] steadfasterX:
outdated bootloader stack. you must follow the UsU FAQ to upgrade your bootloader

.-
[G4 General] pixapo:
Deleted
[G4 General] bazaleem818:
working well thx intelzzz and steadyfasterx that was strange it boot up again in fast mode after do your steps

then i flash twrp in fastboot again to enter recovery now iam waitting to choose best USU rom or USU rom with compatible kernal please steadyfaster x

see my problem in USU forum(can i flash rr 6.2.1 with h815_rr_boot_build-11-oreo)
[G4 General] Zanaxx:
hello brothers i wish you could help me

i have a poco f1 that is completely dead (hard hard hard brick) it doesn't go to fastboot or recovery . it just n edl mod all time . i have a nand backup twrp too but my phone do not turn on as a fastboot or recovery to restore it . i read your guide and its make me really happy . now i know there's a way to back a life my phone . if you assist me and explain it for me how to do this to my xiaomi poco f1 too . i will appreciate you allllllllll my life
[G4 General] masemoel:
Links doesn't work anymore.

I needed them for today as I accidentally bricked my phone so hard.

I found the files here http://leech.binbash.rocks:8008/unbricking/qfil/h815/
[G4 General] mkrts:
https://xdaforums.com/g4/help/h815-download-fastboot-black-screen-t4017745

did i flashed wrong rom ?
[G4 General] mkrts:
sfx please help me

https://xdaforums.com/g4/help/h815-download-fastboot-black-screen-t4017745
[G4 General] by3kk:
same problem I saved the phone with qfil. how fix this? thanks for everything
[G4 General] miracsu:
Hi all, I flashed a rom to my UsU h815 device 3 days ago. Successfuly doing that, I had no cellular, so I thought about that if I install a modem zip that compatible with the phone's system I could fix the problem. And unfortunately I did so. Finally, as soon as flashing the modem zip file, the phone closed and now there is nothing but a short-time vibration. Indeed, when connecting to PC or charger with battery, there is nothing either, the both of them don't see it. Only when shortening the pins without battery, the pc sees it as 9008. And without battery on the pc, there is a battery symbol with a question mark in it, or a flashing, blinking battery symbol appears. However, there is no led, nothing appears on screen when pressing any of the buttons, so to say it is dead. I've tried every steps mentioned at the first post; replaced UsU files, shortened the pins but no luck, every time I get QFIL fails regarding to sometimes > qsahara server fail and more of the like. So, shall I go to service as I have seen on and researched some forums that Emmc socket could be the problem and needs to be changed? I wonder your thoughts.

And sorry I couldn't find the damn >modemzip< file that you could check out.

This is the Rom I haves flashed as daily usage >>> https://androidfilehost.com/?w=files&flid=309048
[G4 General] enesacikgoz:
Başaramadik abi

I need details to do what is explained here

PLEASE ,MY G4 UsU . i couldn't. help me
[G4 General] MrAnssaien:
Never mind.
[G4 General] MrAnssaien:
Unfortunately, it didn't work for me — I have H815. For some reason, 48 hours after I removed a Magisk module called WiFi bonding, the phone just died out of the blue, and I'm not even sure that's related. I've recently bought an original G4 battery, and charger, and they've been working great (I could finally get a full charge in around an hour), my LG G4 has been rocking AOSPExtended6.7 CFW (Android 9.0) for the past few years, and I'd notice some freezes, and random restarts every now and then, but it was nothing to worry about. Anyway, when I removed the battery, and put it back, I still couldn't access any mode (no fastboot, no adb, no TWRP, nothing). When I plugged the phone into my PC, I noticed QHUSB_BULK, and that's when I started looking stuff up until I realized I bricked my phone without doing anything substantial. 🤷‍♂️ Anyway, in a few hours, I'm going to take it to a local technician to see if the IC chip got fried or some other nonsense, because nothing online worked, and I hope I haven't fallen for the "wrong MBN file" trap by changing my phone's model. 😅 Some technicians here in Morocco are pretty good at what they do, so let's hope I can find someone who can fix it. If not, I guess I'll just get a more modern phone, since this bad boy has been with me since August, 2015, and it still looks new, which makes sense, because I mostly use it to listen to music every other day. 😅 Like my bestie said, "No wonder it's still new. You only use it as a friggin' WALKMAN!" 😂

Finally, great work, steadfasterX. Kudos! 👏 And thank you, inteLzzz, for the guide!
[G4 General] steadfasterX:
Sounds like the ilapo.
[G4 General] MrAnssaien:
I noticed that with ILAPO, at least you can see the LG boot logo. I can't see anything on the screen; It's like both of my original batteries are completely dead. No light of any kind, and no vibration when I try to power it on. All button combinations that I know of don't do anything. However, while the phone's plugged in, and I try to enter download mode, it switches from QDLoader to "Device not recognized", so it could be a physical issue.
[G4 General] MrAnssaien:
This is what happens when I try to enter DOWNLOAD MODE.
[G4 General] MrAnssaien:
I'm literally looking to buy some decent MP3 player right now to keep me entertained when I'm out walking. 😂🤣 I regret giving one to a former friend. 😭 I hate it when I give something away, and then need it so badly later. 😂 I also sucked at thinking ahead anyway. Good luck, guys!
[G4 General] steadfasterX:
No thats not true. There are several stages of the ilapo (see my sig) and the last one is just 9008 mode without anything on the screen
[G4 General] MrAnssaien:
Yeah, you're right, but still, I think that, in my case,

Final destination - R.I.P. 9008 mode

, so I guess it's the end of the road for my LG G4. 😅 Cheers, bro!
[G4 General] steadfasterX:
Exactly thats what i wanted to say with that. Ofc there are some physical hackz but tbh really buy a new phone ;)
[G4 General] MrAnssaien:
Yup, that's the plan! ;) Probably Pixel 4A or if I'm planning on another 6 years with the same phone, maybe S21 Ultra, which would be my fanciest WALKMAN to date. 😂🤣

Thanks for your time, homie! Peace! ✌