LG G7 ThinQ T mobile hard brick - LG G7 ThinQ Questions & Answers

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.

Related

[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

unbrick lg g3 please help

i flashed the wrong baseband and rom by mistake. how? well i rename it and got confused and mix it with other roms.well the point now is my lg g3 is bricked and i need help to get it back to life please anyone help
anyone? please help.
anyone please help i will give 40dlls on paypal to anyone how can get my phone working again.i will give the 40 bucks seriously
Can you get into recovery or download mode?
nothing just black screen no led either but the computer recognizes the phone on devices settings it shows LGE androidnet usb serial port.
i tried every guide here on xda to unbrick and a few on other sites and noghting
the only thing i did not try yet is a tool called lg smart boot diagnosis tool that theres nowhere to download only an xda member seems to have this tool but im waiting to see if he can share the tool or no
I dont have much experience with lg yet but if there is a flashing tool for it since u can still get the computer to read you just the tool and stock rom reflash and startover
i tried that already the problem i got now is the phone cannot get to be on download mode lg flash tool gets me an error that can't change to dlmode. it seems im running out of options maybe i should send my phone to lg for repair but i rather not i would like to try a little more before doing that
brigantti said:
i tried that already the problem i got now is the phone cannot get to be on download mode lg flash tool gets me an error that can't change to dlmode. it seems im running out of options maybe i should send my phone to lg for repair but i rather not i would like to try a little more before doing that
Click to expand...
Click to collapse
To put it simply if you cannot get to download mode, at this time you are sol. Maybe in the future if we get the qualcomm files you could fix it if your pc recognizes in one way or another it is connected under ports. But right now as we stand we do not have the files to recover from your type of brick.
thanks for you reply it seems that im gonna have to send it to lg for repair i bought it second hand so t-mobile will not help me with this.
Can you get adb to recognize it? You might be able to extract the laf.img and use adb to flash it back to your phone. Then you'll have download mode back.
no adb either i tried that. i try all kdz methods,flash tool with tot file and modded dll it gets stuck on can"t change to download mode. thanks for asking
the only method i did no try yet is the lg smart boot diagnosis tool that a xda member has but dont wants to share the tool
brigantti said:
the only method i did no try yet is the lg smart boot diagnosis tool that a xda member has but dont wants to share the tool
Click to expand...
Click to collapse
So... if you turn off your phone and then push VOL up and insert a USB doesn't go in laf mode?
Sent from my SM-N910F using XDA Free mobile app
Skin1980 said:
So... if you turn off your phone and then push VOL up and insert a USB doesn't go in laf mode?
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
no nothing happens just a black screen
Black screen might not mean its not doing anything
deron37129 said:
Black screen might not mean its not doing anything
Click to expand...
Click to collapse
This is true but two problems exist:
1) Correct me if this is wrong, if you brick your phone and don't automatically boot into fastboot mode there is no way to do it. You need to flash the full fledged laf.img so it is booted when you do the vol + plug in instead of booting to lg boot loader.
2) Even if his computer can recognize the phone what he has done probably makes it boot into QHSUSB mode and at this time we have no solution to fix it.
I have read somewhere on the g2 forum of fixing one of the types of QHSUSB bricks (they come in a couple of flavors) but I can't remember which one. I do remember he needed to flash the full fledged fastboot laf somehow then flash the aboot partition via fastboot. So if I was you I would do some digging in the g2 forums.
thanks everyone for trying to help.well i just send my phone back to lg for repair i will inform everyoneif lg repair my g3 or not thanks again
I am also facing this problem it's completely bricked when I connect device to computer it shows LGE ANDROIDNET SERIAL please help to solve this problem
On the computer or the phone

LG G3 dead. Black screen. No booting. Help????

Hi,
I tried to install a custom rom on my LG G3 d858hk model. I was in twrp recovery and trying to install rom. Suddenly the phone got stuck. I waited for some time and then pulled the battery out and reinserted it. But still no light etc. Even nothing happens when I plug in charger. Looks like its completely dead. Any body any idea, how can i recover it from the black screen.
Regards,
Khurram.
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 follow this guide just download ure files
Hi. am facing the same issue. Is there any other way to fix it, that doesn't include opening up the phone?
antony990 said:
Hi. am facing the same issue. Is there any other way to fix it, that doesn't include opening up the phone?
Click to expand...
Click to collapse
Do you have a warranty for you phone ? do you tried to download mode, fastboot mode and not working? In case the phone is completely dead, I can suggest you the option boarddiag (open phone) and jtag.
cesarandres_8911 said:
Do you have a warranty for you phone ? do you tried to download mode, fastboot mode and not working? In case the phone is completely dead, I can suggest you the option boarddiag (open phone) and jtag.
Click to expand...
Click to collapse
Yes I have a warranty. But I had installed a custom ROM (cloudy g3), so I guess that violates mine. The phone is dead, and shows up in device manager as LGE AndroidNet USB Serial Port. Don't even know why its showing up like that
Okay, am i'm searching for any available software fix that's gonna work for me at least before I resort to opening up the phone
Let me shed some light on what caused my phone to go dark, to save someone else from repeating the same mistake... I was trying to upgrade twrp from version 2.8 to 3.0. I thought using autorec would help me achieve that. But once it had finished, I attempted to boot to recovery and since then my phone has gone completely dark
OK, you could try to carry the cellphone to LG support and you can tell that after an upgrade, your phone has not returned to turn on. Usually, they change the motherboard. If you want to do it through BoardDiag, here is an explanation:
http://forum.xda-developers.com/showpost.php?p=65003040&postcount=300
cesarandres_8911 said:
OK, you could try to carry the cellphone to LG support and you can tell that after an upgrade, your phone has not returned to turn on. Usually, they change the motherboard. If you want to do it through BoardDiag, here is an explanation:
http://forum.xda-developers.com/showpost.php?p=65003040&postcount=300[/url]
Click to expand...
Click to collapse
Thanks for your help. Ive been able to get my phone to 9008 mode. So, am getting the part where I have to use the boarddiag tool, but am abit confused. What should be the value of my target dir, and AP chipset?. For the chipset, i'm thinking I should use the value that's similar to the one at this guide
http://forum.xda-developers.com/spr....
My phone is an LG g3 d855, so please guide
antony990 said:
Thanks for your help. Ive been able to get my phone to 9008 mode. So, am getting the part where I have to use the boarddiag tool, but am abit confused. What should be the value of my target dir, and AP chipset?. For the chipset, i'm thinking I should use the value that's similar to the one at this guide
http://forum.xda-developers.com/spr...and "TARGET DIR" should be the same location.
Click to expand...
Click to collapse
cesarandres_8911 said:
The first thing you should do is download the .tot file corresponding to your Variant (D855), I think that you can find it here: http://forum.xda-developers.com/lg-g3/help/tot-dll-file-d855-t2859828
Follow this guide to use boarddiag:
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
In the "Image EXTRACTION" sections, in "BIN" must locate the file .tot that you downloaded.
In "DIR" you put the location where will be extracted the content of the .tot file.
Note that "DIR" and "TARGET DIR" should be the same location.
Click to expand...
Click to collapse
Yes. Iam following the guide you provided. But am stuck at this error. Check the image attached
antony990 said:
Yes. Iam following the guide you provided. But am stuck at this error. Check the image attached
Click to expand...
Click to collapse
And then, every time I unplug the device and plug it back into the PC, the device ends up being undetected by windows, and I have to redo the shorting procedure again. Is this normal behaviour, or something is wrong??
Also, when I put the battery back, and plug the device, it shows up as LGE androidnet usb
Anyone explain to me what this means. Please check the image attached
antony990 said:
Anyone explain to me what this means. Please check the image attached
Click to expand...
Click to collapse
I have the same error, and have tried about everything including 4 different computers and OSs, different cables, different versions of BoardDiag 2.99a - 3.99c, and still the same error.
singingandroid said:
I have the same error, and have tried about everything including 4 different computers and OSs, different cables, different versions of BoardDiag 2.99a - 3.99c, and still the same error.
Click to expand...
Click to collapse
It could also mean your device isn't in EDL mode 9008.
TheMadScientist said:
It could also mean your device isn't in EDL mode 9008.
Click to expand...
Click to collapse
I believe I am in the right 9008 mode. Screenshot is attached.
singingandroid said:
I believe I am in the right 9008 mode. Screenshot is attached.
Click to expand...
Click to collapse
I had be not dealt with edl on LG in a long time been on Samsung for a while that being said i could suggest maybe be uninstall the current 9008 driver and try to find a different source or updated and or try other usb ports. We on s8 have a lot of issues with usb 3.0 ports on pc's
TheMadScientist said:
I had be not dealt with edl on LG in a long time been on Samsung for a while that being said i could suggest maybe be uninstall the current 9008 driver and try to find a different source or updated and or try other usb ports. We on s8 have a lot of issues with usb 3.0 ports on pc's
Click to expand...
Click to collapse
Yeah, I've tried pretty much everything, but thank you for the reply.

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.

Question Soft Bricked T-Mobile OnePlus 9 Pro

So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
I did that to an HTC U11 once - Never got it recovered, had to toss it...
Never dared relock a bootloader since...
I had the same thing happen to me.
The only thing that worked for me is to boot recovery and wipe system. Good luck
Jhoopes517 said:
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
Click to expand...
Click to collapse
i have the same problem let me know if you figure out a way around this !
For all of you having this issue, simply use the msm for your respective device by unplugging your phone, select power off, enter edl mode with cable plugged in and run the tool. I know another solution, but please PM me if this one doesn't work.
I had this issue as well, but you better not have messed with the sensitive partitions without a backup, otherwise there's no way to repair it.
razercortex said:
For all of you having this issue, simply use the msm for your respective device by unplugging your phone, select power off, enter edl mode with cable plugged in and run the tool. I know another solution, but please PM me if this one doesn't work.
Click to expand...
Click to collapse
i cannot figure out how to run the msm tool properly it always throws an error message
KidSudo6969 said:
i cannot figure out how to run the msm tool properly it always throws an error message
Click to expand...
Click to collapse
what is the error message? Maybe you dont have the correct one.
Jhoopes517 said:
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
Click to expand...
Click to collapse
Here is the msm tool
This was fixed via MSM. But I had another issue come up where MSM doesn't work.
Jhoopes517 said:
This was fixed via MSM. But I had another issue come up where MSM doesn't work.
Click to expand...
Click to collapse
What do you mean doesnt work? What did it do?
its not responding at all. no boot loop, no logo, no nothing. just a blackscreen no matter how long i charge it or hold the buttons down.
Aleena1217 said:
its not responding at all. no boot loop, no logo, no nothing. just a blackscreen no matter how long i charge it or hold the buttons down.
Click to expand...
Click to collapse
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
ekin_strops said:
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
Click to expand...
Click to collapse
after installing driver it recognized it in EDL mode. Im also JUST seeing that this is for the 9 and not the 9 pro. im guessing thats the issue? ii cant believe i missed that
Aleena1217 said:
after installing driver it recognized it in EDL mode. Im also JUST seeing that this is for the 9 and not the 9 pro. im guessing thats the issue? ii cant believe i missed that
Click to expand...
Click to collapse
Yes, it's for the Pro, but the procedure is the same. A good thing is that EDL works. Now just grab the MSM Tool for your model and flash it.
ekin_strops said:
Yes, it's for the Pro, but the procedure is the same. A good thing is that EDL works. Now just grab the MSM Tool for your model and flash it.
Click to expand...
Click to collapse
thank you so much. msm is downloading now. while I have you, do you have a link for the 9 pro conversion files? id really like to get that xpan update finally...
ekin_strops said:
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
Click to expand...
Click to collapse
im sorry i just realized i jumped in the middle of a different thread. This happened while trying to flash tmobile oneplus 9 pro to global firmware and after trying to enter recovery mode. Im guessing it happened because the files are for one plus 9, so im looking for the files for a 9 pro conversion but only am finding msm tool downloads for conversion instead of flashbin files.
Aleena1217 said:
im sorry i just realized i jumped in the middle of a different thread. This happened while trying to flash tmobile oneplus 9 pro to global firmware and after trying to enter recovery mode. Im guessing it happened because the files are for one plus 9, so im looking for the files for a 9 pro conversion but only am finding msm tool downloads for conversion instead of flashbin files.
Click to expand...
Click to collapse
Before I jump to conclusions, could you explain exactly which model you have and what is your goal?
ekin_strops said:
Before I jump to conclusions, could you explain exactly which model you have and what is your goal?
Click to expand...
Click to collapse
i have the le 2127 from tmobile because i didnt know any better. i dont want to root or do anything crazy. I just want to be able to flash to global or eu firmware so i can upgrade as oneplus releases the updates and not be a year behind on tmobiles schedule. I have the sim and bootloader unlocked successfully. I started to flash to the one plus 9 firmware because i somehow missed that it did not say pro. So now my phone in unresponsive except for QDL 9008 mode. MSM tool recognizes it and begins to update it but then gets a param preload "device not image match" message in red and stops. So once i figure out how to get past that and get this set to factory, i want to properly flash it to global or eu, whichever is available, and upgrade it to the latest version.
Aleena1217 said:
i have the le 2127 from tmobile because i didnt know any better. i dont want to root or do anything crazy. I just want to be able to flash to global or eu firmware so i can upgrade as oneplus releases the updates and not be a year behind on tmobiles schedule. I have the sim and bootloader unlocked successfully. I started to flash to the one plus 9 firmware because i somehow missed that it did not say pro. So now my phone in unresponsive except for QDL 9008 mode. MSM tool recognizes it and begins to update it but then gets a param preload "device not image match" message in red and stops. So once i figure out how to get past that and get this set to factory, i want to properly flash it to global or eu, whichever is available, and upgrade it to the latest version.
Click to expand...
Click to collapse
Are you getting the mismatch on the global/eu MSM or are you trying to flash back to stock T-Mobile? You're getting a mismatch because you're most likely using the wrong version of a firmware (msm).

Categories

Resources