Develop Bugs

[Q] Secure Booting Error! Cause: boot certification verify

Hello all,
Well, it's here... Unfortunately my phone got bricked last night
Can't boot into main screen and can't go to download mode anymore. The cause is, my phone was stuck when upgrading firmware and there's nothing to do about it except remove the battery, and then, BOOM!... "Secure Booting Error! Cause: boot certification verify"
Any LG G3 users here already experienced this problem?
I followed the solution on LG G2 sub-forum, but my ubuntu doesn't detect the port, although Windows recognized it.
If this happens to your G3 and you solved it, please share your experience
Thanks

haris182 said:
Hello all,
Well, it's here... Unfortunately my phone got bricked last night
Can't boot into main screen and can't go to download mode anymore. The cause is, my phone was stuck when upgrading firmware and there's nothing to do about it except remove the battery, and then, BOOM!... "Secure Booting Error! Cause: boot certification verify"
Any LG G3 users here already experienced this problem?
I followed the solution on LG G2 sub-forum, but my ubuntu doesn't detect the port, although Windows recognized it.
If this happens to your G3 and you solved it, please share your experience
Thanks
Click to expand...
Click to collapse
Help me too

haris182 said:
Hello all,
Well, it's here... Unfortunately my phone got bricked last night
Can't boot into main screen and can't go to download mode anymore. The cause is, my phone was stuck when upgrading firmware and there's nothing to do about it except remove the battery, and then, BOOM!... "Secure Booting Error! Cause: boot certification verify"
Any LG G3 users here already experienced this problem?
I followed the solution on LG G2 sub-forum, but my ubuntu doesn't detect the port, although Windows recognized it.
If this happens to your G3 and you solved it, please share your experience
Thanks
Click to expand...
Click to collapse
If Windows recognizes it then try using LGflashtool again.
Sent from my LG-D851 using Tapatalk

Skizzy034 said:
If Windows recognizes it then try using LGflashtool again.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Windows does not recognize the phone...

Skizzy034 said:
If Windows recognizes it then try using LGflashtool again.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Not at all.
Finally, I claimed my warranty with LG, and the motherboard got replaced.
It's all working now

You could have unbricked it... I've done that twice already

im stuck in this, how?

I'm stuck at the same thing since yesterday.
could you tell us the solution @nofait?
I've been researching about this and noticed one thing,
if I hold the lg combo (vol up + usb cable), and keep holding it until it passes the secure boot error and the screen becomes black,
my device (d855) goes to the Qualcomm Download Mode (it's detected as ''Qualcomm HS-USB QDLoader 9008'' on windows 8.1 x64)
Apparently, on that mode we could use Qualcomm tools (QPST) to reflash the bootloader and the matching laf image (the one that brings up the download mode)
so we could then flash any KDZ using LG Flash Tool.
To do so we need to extract the bootloader files, sbl1.bin, aboot.bin, rpm.bin, tz.bin, boot.bin, and laf.bin, from a tot/kdz firmware converting them to mbn format.
Then using QPST eMMC Download Tool, we load the partition table xml and 2 image files: the flash programmer file and the qcom boot image, which I'm still trying to figure out where to get them since I can't dump my own phone, and then we might be able to recover it.
I'm still looking into it and hopefully we can find a way.
I did not send my phone to lg service, yet, because I think they will take too long to fix it.

It happened to me a few days ago, but i had TWRP fully working so i could simply flash a ROM and then recover my things.
That thing about windows recognizing it as a msm8474 was a drivers issue (al least for me), i have a S5 too, i think that when i was tryng to get Heimdall working it changed the drivers (as you may know, s5 and g3 have the same board), so i just simply uninstalled it and then reinstall everything using .exe files from LG's website, after that windows 8.1 recognize it perfectly and i could flash KDZ without problems.
Other experience i had and that may help is what happened to me using an LGOG, couldn't boot, no recovery, no nothing, just trying to turn it on, it managed to get in fastboot mode (but with screen off and red LED all the time),from that point it was just about typing commands and flashing img to get it working

diego-ch said:
I'm stuck at the same thing since yesterday.
could you tell us the solution @nofait?
I've been researching about this and noticed one thing,
if I hold the lg combo (vol up + usb cable), and keep holding it until it passes the secure boot error and the screen becomes black,
my device (d855) goes to the Qualcomm Download Mode (it's detected as ''Qualcomm HS-USB QDLoader 9008'' on windows 8.1 x64)
Apparently, on that mode we could use Qualcomm tools (QPST) to reflash the bootloader and the matching laf image (the one that brings up the download mode)
so we could then flash any KDZ using LG Flash Tool.
To do so we need to extract the bootloader files, sbl1.bin, aboot.bin, rpm.bin, tz.bin, boot.bin, and laf.bin, from a tot/kdz firmware converting them to mbn format.
Then using QPST eMMC Download Tool, we load the partition table xml and 2 image files: the flash programmer file and the qcom boot image, which I'm still trying to figure out where to get them since I can't dump my own phone, and then we might be able to recover it.
I'm still looking into it and hopefully we can find a way.
I did not send my phone to lg service, yet, because I think they will take too long to fix it.
Click to expand...
Click to collapse
Hi,
You'll need to use a Windows 7 machine and the proper LG USB Driver (first post of this message) and change it to the COM41.
Do a BOARD DL and when the screen comes up and tells you to not touch it, ignore and press OK. Then press the power button and at the same type touch the "Normal +power". It should reboot and everything should be fine
Cheers!

nofait said:
Hi,
You'll need to use a Windows 7 machine and the proper LG USB Driver (first post of this message) and change it to the COM41.
Do a BOARD DL and when the screen comes up and tells you to not touch it, ignore and press OK. Then press the power button and at the same type touch the "Normal +power". It should reboot and everything should be fine
Cheers!
Click to expand...
Click to collapse
So,
Should I use windows 7 32 bit or is it fine with 64 bit?
Will I need a .TOT file and a DLL for my model ( D855P 16gb ) or can I use a KDZ file?
EDIT: ok so I tried it, but flash tool failed to get model information from the phone.
were you in download mode? I can't get to download mode here.

diego-ch said:
So,
Should I use windows 7 32 bit or is it fine with 64 bit?
Will I need a .TOT file and a DLL for my model ( D855P 16gb ) or can I use a KDZ file?
EDIT: ok so I tried it, but flash tool failed to get model information from the phone.
were you in download mode? I can't get to download mode here.
Click to expand...
Click to collapse
I send my phone to warranty service, where they changed all the motherboard with new IMEI and SN.
Hope that they don't ask for money to repair the phone.

hi all, having this problem as well. anyone resolve this?? Need help!

[/COLOR]
nofait said:
Hi,
You'll need to use a Windows 7 machine and the proper LG USB Driver (first post of this message) and change it to the COM41.
Do a BOARD DL and when the screen comes up and tells you to not touch it, ignore and press OK. Then press the power button and at the same type touch the "Normal +power". It should reboot and everything should be fine
Cheers! .
Click to expand...
Click to collapse
hi thanks for idea but could you explain in detail because is not working on my end. what screen comes up? i get ready in com41 . then download fail! (0 sec)
---------- Post added at 11:29 AM ---------- Previous post was at 11:26 AM ----------
paolotheking said:
I send my phone to warranty service, where they changed all the motherboard with new IMEI and SN.
Hope that they don't ask for money to repair the phone.
Click to expand...
Click to collapse
did you get it back?

prana_Sky said:
did you get it back?
Click to expand...
Click to collapse
Yes, with new mainboard.

prana_Sky said:
hi all, having this problem as well. anyone resolve this?? Need help!
Click to expand...
Click to collapse
I have the same problem did you find any solution ?
edit: solved somehow

LG G4 bootloop.... Need expert help... Ready to pay the price

Hello,
I had been using a H815T, locked bootloader, running Seven HD rom v6.1 for more than 2 months flawlessly. Suddenly yesterday my phone was in charge and it restarted and went into bootloop. Since I tried many things and I went to some local technicians as well as one LG engineer, but all failed to gimme any solution. And I don't have any warrenty, I couldn't ask for a replacement for anyone.
So here's what I tried:
1. Flashing international KDZ
2. Flashing default KDZ
3. Formatting from recovery mode
4. Changing battery
Here's what works:
1. Download mode
2. Recovery mode
So I am ready to pay if anyone gimme a solution out of this. Any help will be appreciated as I am in real trouble coz I cannot afford a new phone now.
With thanks

nipun1110 said:
Hello,
I had been using a H815T, locked bootloader, running Seven HD rom v6.1 for more than 2 months flawlessly. Suddenly yesterday my phone was in charge and it restarted and went into bootloop. Since I tried many things and I went to some local technicians as well as one LG engineer, but all failed to gimme any solution. And I don't have any warrenty, I couldn't ask for a replacement for anyone.
So here's what I tried:
1. Flashing international KDZ
2. Flashing default KDZ
3. Formatting from recovery mode
4. Changing battery
Here's what works:
1. Download mode
2. Recovery mode
So I am ready to pay if anyone gimme a solution out of this. Any help will be appreciated as I am in real trouble coz I cannot afford a new phone now.
With thanks
Click to expand...
Click to collapse
that block at 9% and told you to remove batery unplug phone etc etc?

i have same problem and no 2nd phone here -.- we need a Updated LG Flash Tool 2014 to flash the 20A.kdz

fr33kiLL said:
i have same problem and no 2nd phone here -.- we need a Updated LG Flash Tool 2014 to flash the 20A.kdz
Click to expand...
Click to collapse
unfortunaly we can wait a long time maybe ...

nipun1110 said:
Hello,
I had been using a H815T, locked bootloader, running Seven HD rom v6.1 for more than 2 months flawlessly. Suddenly yesterday my phone was in charge and it restarted and went into bootloop. Since I tried many things and I went to some local technicians as well as one LG engineer, but all failed to gimme any solution. And I don't have any warrenty, I couldn't ask for a replacement for anyone.
So here's what I tried:
1. Flashing international KDZ
2. Flashing default KDZ
3. Formatting from recovery mode
4. Changing battery
Here's what works:
1. Download mode
2. Recovery mode
So I am ready to pay if anyone gimme a solution out of this. Any help will be appreciated as I am in real trouble coz I cannot afford a new phone now.
With thanks
Click to expand...
Click to collapse
stock recovery or twrp..

Google~Android said:
stock recovery or twrp..
Click to expand...
Click to collapse
we have not access at twrp anymore .... and kdz method doesnt work . phone recognized in all lg software ... support tool 9% and issue

shudoha said:
we have not access at twrp anymore .... and kdz method doesnt work . phone recognized in all lg software ... support tool 9% and issue
Click to expand...
Click to collapse
did you have an unlocked bl or not?

Google~Android said:
did you have an unlocked bl or not?
Click to expand...
Click to collapse
of course for flash first twrp and after flash all autoprime files and after this .. impossible to have access at twrp . hard reset work . but nothing happens boot loop kdz for rollback doesnt work too . still blocked at 9% on the tool and 0 on my phone and ask me to remove the battery etc etc i did that too much time . but for nothing and the worst . bridge .. support tool recognize my phone like H815 then no driver problem

i have unlocked BL but didnt have access to ADB and Fastboot(idk why) and got stock recovery after flashing so no chance to go in TWRP

Does the phone freeze at random times? Like no matter where its at, sometimes it boots to the operating system?

Hardware
It's starting to sound more and more like a MEM BLOCK corruption..

Have you tried this: Firmware to Stock with kdz and tot?

Noo

shudoha said:
that block at 9% and told you to remove batery unplug phone etc etc?
Click to expand...
Click to collapse
No..nothing like that

mr turtle droid said:
It's starting to sound more and more like a MEM BLOCK corruption..
Click to expand...
Click to collapse
What's that and what's the remedy? And usually what causes it?

martinsavvy said:
Does the phone freeze at random times? Like no matter where its at, sometimes it boots to the operating system?
Click to expand...
Click to collapse
To me it used to happen sometimes while charging. I had to manually switch off the screen and when i switched on the screen, it became normal for a while. I thought it was due to heavy xposed customizations.

michael08071984 said:
Have you tried this: Firmware to Stock with kdz and tot?
Click to expand...
Click to collapse
That's the KDZ method. Yah I tried it as I mentioned.

michael08071984 said:
Have you tried this: Firmware to Stock with kdz and tot?
Click to expand...
Click to collapse
tested but like i told you .... blocked at 9% and remove battery unplug etc etc and nothing happend

Try this:
copy all zip files you need to reflash (10D or similar) to a memcard
Also download latest twrp and copy it to the directory where you have adb.exe
Open a Command prompt on your PC (where adb is located) and powerup the phone,
open up the Device Manager on your PC to see when the adb device is there,
in the moment where you see the adb device fire up the comand:
adb reboot bootloader
if that works enter the comand:
fastboot boot twrp-2.8.7.0-h815.img
this will boot directly into Twrp without flashing twrp and you can try things from twrp
I hope this will help here, helped me with the phone from a friend of me who had a similar problem.

fire3d said:
Try this:
copy all zip files you need to reflash (10D or similar) to a memcard
Also download latest twrp and copy it to the directory where you have adb.exe
Open a Command prompt on your PC (where adb is located) and powerup the phone,
open up the Device Manager on your PC to see when the adb device is there,
in the moment where you see the adb device fire up the comand:
adb reboot bootloader
if that works enter the comand:
fastboot boot twrp-2.8.7.0-h815.img
this will boot directly into Twrp without flashing twrp and you can try things from twrp
I hope this will help here, helped me with the phone from a friend of me who had a similar problem.
Click to expand...
Click to collapse
problem boot loop when i open my phone even with hard reset that change nothing and adb said : device not found when all program like lg support or bridge recognize my phone like h815 ... then not solution

Unbrick bricked by writing boot.img to wrong mmcblk

Hello community members,
TL;DR no adb, no fastboot, no flashmode, no QDloader (or similar) ... how to unbrick it?
I was trying to force Android to allow lower lcd backlight brightness levels by patching framework-res.apk and I had the edited zip file ready to flash. Then I realized that my Android 7 Ressurection remix ROM (thread) flashed Cyanogenmod recovery, which I don't like. So I decided to reflash TWRP 3.0.2 (link) ( edit: using "fastboot flash boot twrp.img", which was almost fatal mistake) and it has gone almost well. The phone started to boot into recovery mode everytime (and took a long time doing so). So I googled a bit and found this thread which lead me to this thread. I was looking forward to seeing my display brightness at lower than default values, so I probably skipped some security checks and texts with red color, so I flashed the zip with the boot.img replaced. After flashing I chose reboot and nothing happened since.
The problem is I flashed something that was not for my device (extracted boot.img to wrong mmcblk). The command that bricked my phone is (from META-INF/com/google/android/updater-script):
Code:
package_extract_file("boot.img", "/dev/block/mmcblk0p6");
After that it doesn't boot, doesn't light up LED (even when charging), doesn't get detected by PC in any state.
So I have no adb, no fastboot and no flashmode and not even a QDloader or similar mode.
Is there a way to unbrick it?
EDIT: How to unbrick it using JTAG interface? If I find somebody that has the required equipment, what data do I need to give them?

Hey there! Did you manage to solve the issue, because I just got into the same situation after the zip didn't save the corrected partitions but the initial ones... So i ended up without any signs of life in my phone

valkata752 said:
Hey there! Did you manage to solve the issue, because I just got into the same situation after the zip didn't save the corrected partitions but the initial ones... So i ended up without any signs of life in my phone
Click to expand...
Click to collapse
Nope, I found no solution ... even some kind of Qualcomm flashing mode via COM (serial port over USB) does not show up nowhere. I gave up and bought a used S5 mini, which is full of features I appreciate.
I'm gonna keep this Xperia M for some time if some solution comes up.

hi , can you boot into recovery ? ..if yes, i can maybe help

olibub said:
hi , can you boot into recovery ? ..if yes, i can maybe help
Click to expand...
Click to collapse
No, as I said, the phone does not react on anything. I would be able to put it back together if this was possible.

mik13ST said:
No, as I said, the phone does not react on anything. I would be able to put it back together if this was possible.
Click to expand...
Click to collapse
:/ this will be a problem... try look here http://rootmyandroid.org/how-to-unbrick-your-android-device-the-ultimate-guide.html/
and find this article "Unbrick any android device with Once Click Unbrick tool"

mik13ST said:
No, as I said, the phone does not react on anything. I would be able to put it back together if this was possible.
Click to expand...
Click to collapse
can you still access fastboot mode? anyway you need to know first what is exactly partition that you overwrite with boot.img :/
. That was really critical -_-

olibub said:
:/ this will be a problem... try look here http://rootmyandroid.org/how-to-unbrick-your-android-device-the-ultimate-guide.html/
and find this article "Unbrick any android device with Once Click Unbrick tool"
Click to expand...
Click to collapse
Nice looking tutorial, but I cannot find any download link for that One Click Unbrick Tool in that article. I doubt it would work, they are not explaining what it does.
Nicklas Van Dam said:
can you still access fastboot mode? anyway you need to know first what is exactly partition that you overwrite with boot.img :/
. That was really critical -_-
Click to expand...
Click to collapse
No, as I said. The partition that got overwritten was /dev/block/mmcblk0p6. It was overwritten by boot.img from LG OPTIMUS 3D that I link to in the main post.

here you can download unbrick tool https://forum.xda-developers.com/showthread.php?t=1153310

olibub said:
here you can download unbrick tool https://forum.xda-developers.com/showthread.php?t=1153310
Click to expand...
Click to collapse
I don't think this has any chance that it will work.
"This Software:
Will work on all Samsung devices which use Odin3"

Do you know how to use Flashtool?
If so, did you already attempt flashing a ftf via Flashmode (Hold VolDown)?

PhoenixTwoFive said:
Do you know how to use Flashtool?
If so, did you already attempt flashing a ftf via Flashmode (Hold VolDown)?
Click to expand...
Click to collapse
I know what Flashtool is. I know what ftf is. I used it once I think.
But the phone does not boot into flashmode as I mention in the main post.

LG G7 ThinQ T mobile hard brick

Hi guys!
I tried to put the android 10 korean beta on my LG G7 ThinQ g710TM T-Mobile, and now it doesn't turn on, the laptop recognizes it as QUALCOMM 9008 MODE I just need to know if its trash already or there's a way that can unbrick the phone (really stupid I know)
Thank you in advance!

If the phone wasn't a T-Mobile:
May be able to flash v35.eng img onto the phone's abl_a partition (make sure this is backed up), then use fastboot commands to copy over the laf_a/_b files of the stock img. Then use download mode to revert back to Android 8/oreo.
May need to use, fastboot boot laf.img, to get onto download mode, as suggested here.

It was a t mobile damn never go for a t mobile again REALLY
paxar331 said:
If the phone wasn't a T-Mobile:
May be able to flash v35.eng img onto the phone's abl_a partition (make sure this is backed up), then use fastboot commands to copy over the laf_a/_b files of the stock img. Then use download mode to revert back to Android 8/oreo.
May need to use, fastboot boot laf.img, to get onto download mode, as suggested here.
Click to expand...
Click to collapse
It was a t mobile damn never go for a t mobile again REALLY

Pocketjam347 said:
It was a t mobile damn never go for a t mobile again REALLY
Click to expand...
Click to collapse
You can try my method to fix it?
https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841
I

I don't understand one part
Awesomeslayerg said:
You can try my method to fix it?
https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841
I
Click to expand...
Click to collapse
I tried this method 2 days ago but for some reason when I try STEP 7: It says "Extracting kdz to ..." so I tried to wait a WHILE but after 4 hours of wait nothing happened so I was unable to do the next steps
Does it matter if the Phyton says that it was the end of its life?
Thank you so much for your post tho I believe you helped other people

Don't throw it away, I think there's a fix with QFIL.

I'm having a similar problem, but in my case I managed to accidentally erase laf_b from QFIL and this has corrupted my GPT. Now the QFIL partitioner can't see my partitions. Can you help? I may need a flat pack or something? I'm stuck in 9008 mode. The bootloader was unlocked but I couldn't get into fastboot to install TWRP and Lineage OS, so I ended up trying to erase laf_a and laf_b like it says to do in the V40 Qfil guide. Big mistake. Qfil and windows both recognize it as a 9008 device on Com3, but can't access the partitions.

I got the phone from a friend and i'm in the same position. The method from Awesomeslayerg just gives me sahara error

THE KHAMELEON said:
I got the phone from a friend and i'm in the same position. The method from Awesomeslayerg just gives me sahara error
Click to expand...
Click to collapse
See the FAQ in that guide.
Restart edl when connected to qfil or try different USB port or different PC.

lefttobleed said:
See the FAQ in that guide.
Restart edl when connected to qfil or try different USB port or different PC.
Click to expand...
Click to collapse
I don't have another PC to try it on. I been trying other ports and nothing. As I use my tweezers to put the phone in EDL I press download and still the error.
I don't know if this phone is T-Mobile or not. The IMEI shows T-Mobile but inside the phone shows numbers for Verizon

THE KHAMELEON said:
I don't have another PC to try it on. I been trying other ports and nothing. As I use my tweezers to put the phone in EDL I press download and still the error.
I don't know if this phone is T-Mobile or not. The IMEI shows T-Mobile but inside the phone shows numbers for Verizon
Click to expand...
Click to collapse
Not sure what's wrong with your phone...
Once I got out of this error by quickly pressing download when phone enters edl. Need to be fast.
Try that.

lefttobleed said:
Not sure what's wrong with your phone...
Once I got out of this error by quickly pressing download when phone enters edl. Need to be fast.
Try that.
Click to expand...
Click to collapse
To be honest I think it could be me just having the files in the wrong place or something else I'm doing wrong. All I get is Sahara error

Pocketjam347 said:
Hi guys!
I tried to put the android 10 korean beta on my LG G7 ThinQ g710TM T-Mobile, and now it doesn't turn on, the laptop recognizes it as QUALCOMM 9008 MODE I just need to know if its trash already or there's a way that can unbrick the phone (really stupid I know)
Thank you in advance!
Click to expand...
Click to collapse
Same problem with my phone.
I also try these things.
If you solved that problem then please share with me.

HEEEEEEEELLLPP!!! i think i bricked my G7! QUICK!!

im super worried right now, this is my only phone and really need it these days, thing is i tried to flash a kdz to my phone with lg up 1.14 and worked, everything was fine, but it had a may 2019 security patch and didnt want to update via OTA, so i downloaded a more recent kdz and did the same, but now with LG UP 1.15, thing is, this time, when it was supposed to reboot and show a circle that says "erasing" it stayed off.
now it doesnt react to anything, not even the volume down+power or the volume up and conecting to acces download mode it stays at a blank screen with no reaction, not even a vibration.
however, when changing ports, it stared installing a divice, however it said this:
qusb_bulk_cid:0402 _sn:c9aaeafb is set up and ready to go
i sherched and this appears to be a qualcomm brick, please tell me i can recover my phone.
someone help me quick please

ok, i installed qualcomm drivers and now my phone is detected as hs usb qdloader 9008 (COM9), which indeed is a qualcomm brick.
does anyone knows what to do next?

I think you can flash with qfil but I don't have much knowledge about that, sorry ... I hope someone who knows about it will help you soon

Ricky Almonte said:
I think you can flash with qfil but I don't have much knowledge about that, sorry ... I hope someone who knows about it will help you soon
Click to expand...
Click to collapse
yeah, i read that, got the files, even the firehose and did it. but now i have a new problem, im still brick but now my phone cant be recognice, every time it is conected the only thing it happens is the led blinking red, which i read it is the worst possible outcome. (im sure i did the qfile process correctly, i did it very carfully and only after reading like 6 posts so that i could be well informed.... it got quite techy)
why!! :crying::crying:
i read that mostly happens to the t mobile version of the phone, but mine is the cannadian one, i dont get it.
can someone now help me with this red blinking led?? i read a lot but the only thing i found is that ill need to open my phone and use the test points to access qualcomm mode, but it doesnt say more, i dont know where to begin:crying:

did u flash on lgup via cmd or via GUI? if gui, u picked refurbish or other command? Some guys erase their imei mac etc picking other commands in the gui (dl partition is safe), making their smartphone become a thing made of hardware with no identity.

manuhuelva said:
did u flash on lgup via cmd or via GUI? if gui, u picked refurbish or other command? Some guys erase their imei mac etc picking other commands in the gui (dl partition is safe), making their smartphone become a thing made of hardware with no identity.
Click to expand...
Click to collapse
mmmm... i used the lgup version 1.13 via GUI, for my first time, i used refurbish since it was the default, it worked fine.
when i downloaded a more recent kdf for my second install, i also downloaded the version 1.14 for the lgup, i tried to acces the gui like normal but didnt work since it asked me to log in, so i read i could also do it via CMD, so i used CMD for my second test.
Thats when my phone began intalling like normal, but in the reboot section of the install, it turned off to never turn on again

ThePanhead said:
mmmm... i used the lgup version 1.13 via GUI, for my first time, i used refurbish since it was the default, it worked fine.
when i downloaded a more recent kdf for my second install, i also downloaded the version 1.14 for the lgup, i tried to acces the gui like normal but didnt work since it asked me to log in, so i read i could also do it via CMD, so i used CMD for my second test.
Thats when my phone began intalling like normal, but in the reboot section of the install, it turned off to never turn on again
Click to expand...
Click to collapse
I hope u could resolve it. try other lgup versions. If u cant go download mode, hold vol- and power with plugged usb to pc and when the phone restarts u have to release too fast the buttons and hold vol+ until u get into download mode.

Hi, so my phone boots to lg g7 thinq splash screen and gets stuck there. I have a PM flashed to 11g. I can access download mode, edl, fastboot, and I can access all partitions in qfil. Can anyone send a copy of their mpt partition? I think I overwrote it on accident. Thanks.

Try this method...
https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841

Reyklein said:
Try this method...
https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841
Click to expand...
Click to collapse
I'm currently trying that out now. Can you backup your mpt partition in qfil so I can download it? Thank you.

I was actually successful in using qfil to flash but sadly it still isn't enough to fix my problem. It still stays stuck at "lg g7 thinq" splash screen. Also lost access to fastboot.

damprobot said:
I was actually successful in using qfil to flash but sadly it still isn't enough to fix my problem. It still stays stuck at "lg g7 thinq" splash screen. Also lost access to fastboot.
Click to expand...
Click to collapse
In edl mode load xml file 0 and again edl mode load xml1 ......... Repaet till xml6

Baijoosharma said:
In edl mode load xml file 0 and again edl mode load xml1 ......... Repaet till xml6
Click to expand...
Click to collapse
I flashed them one by one this time and still it won't boot completely. If anyone can share their mpt partition from qfil it'd be much appreciated.

damprobot said:
I flashed them one by one this time and still it won't boot completely. If anyone can share their mpt partition from qfil it'd be much appreciated.
Click to expand...
Click to collapse
This is the only option i did it in 4 days repeat and repeat thats it r u usung same ezdextrat file attached in thread ir your own extracted files ? Doenload from here and repeat 0123456 untill monile turn on you will loss imei

I know I'm doing it correctly, as you can see in my screenshot above. The extracted files are not what I need. I need mpt partition, which isn't part of the kdz.
In other words, I messed up a partition the kdz won't fix.

I fixed my issue. Turns out my mpt partition WAS the issue. What I did was wipe mpt in Qfil then reflash everything and it finally booted.
Just an FYI for anyone flashing blindly like me: double check which partition is highlighted in blue before flashing! Lol

Congrats your imei is still there ?

Baijoosharma said:
Congrats your imei is still there ?
Click to expand...
Click to collapse
Yes, everything working well. I'm currently on evolution x now

damprobot said:
Yes, everything working well. I'm currently on evolution x now
Click to expand...
Click to collapse
same issues i faced but lost imei strange

damprobot said:
I fixed my issue. Turns out my mpt partition WAS the issue. What I did was wipe mpt in Qfil then reflash everything and it finally booted.
Just an FYI for anyone flashing blindly like me: double check which partition is highlighted in blue before flashing! Lol
Click to expand...
Click to collapse
would you pls tell that what is mpt partotions. and what if the partitions is blue then whats the case? and what to look at. and 2nd i also unbrick ny phone using 9008 method eith 11g dzextracted. i was then flashed my own stock of eaw but my dual sim phone was now showing single sim. after that i flash many kdzs but no success.