Database Info

T-Mobile US / G710TM10N KDZ

Here is the latest T-Mobile US KDZ: G710TM10N.
Changelog only indicates November security update.
Download URL: here
Google Drive mirrors:
- KDZ
- DLL

@Joe199799 Did you see this? @ChazzMatt Also @culot did you already try to install this and if so what was the result? Also, was not able to get this extracted/decompiled as well.

Dvalin21 said:
@Joe199799 Did you see this? @ChazzMatt
Click to expand...
Click to collapse
I did yes, I should say I keep up with this stuff and know a decent amount about the front end of Android but I'm f****ing clueless about the backend, all the information I've told people is just paraphrasing from other threads on here

Dvalin21 said:
@Joe199799 Did you see this? @ChazzMatt Also @culot did you already try to install this and if so what was the result? Also, was not able to get this extracted/decompiled as well.
Click to expand...
Click to collapse
This was just pulled from LG Bridge as it updated my device.
No, I was not able to extract contents of the dz file. Someone could try to add the header info to that LG kdz python program on github maybe? A while back that used to be simple to accomplish.

Guys here is the boot_a/b for the firmware you posted here. Thanks goes out to @runningnak3d who made updates to @emdroidle's work. (KDZ extractor: Here)Amazing work guys. boot_a/b
Update: Currently trying to upload the system_a/b folders already unpacked. Ill post the link as soon as its finished
Update System_a/b Here

Been lurking and leeching since my first android, trying to contribute on this G7, just upgraded to G710TM10N on this sim-locked G7, if I can provide anything to help anywhere. I can try to pull the same files if redundancy helps

danag94 said:
Been lurking and leeching since my first android, trying to contribute on this G7, just upgraded to G710TM10N on this sim-locked G7, if I can provide anything to help anywhere. I can try to pull the same files if redundancy helps
Click to expand...
Click to collapse
Thank you sir, see if you can try to pull the recovery.img. The firmware didnt seem to include one. I may try and download an older firmware and see if i can recover it from there instead. If everyone can help with this search, it could prove important.

Recovery is included in boot_a, boot_b in system A/B phones which the LG G7 has. It is included there so phone can update without needing a reboot.

mprovi_15 said:
Recovery is included in boot_a, boot_b in system A/B phones which the LG G7 has. It is included there so phone can update without needing a reboot.
Click to expand...
Click to collapse
While you are correct that recovery is in boot, it is not needed for the A/B updates. The only rational reason they stuck recovery in boot is to make our lives difficult. Also, not all A/B phones ditched the recovery partition, just the majority of phones with Qualcomm processors that use their reference abl.
FYI - the much easier way will be to incorporate TWRP into laf ... or just forgo download mode completely, and use the laf partition.
Lastly, now that I can decompile abl -- stay tuned for ablsploit (to be used in conjunction with lafsploit). I am not saying with certainty that it is possible yet, but I am feeling confident.
Oh, one last thing for real this time -- don't think about cross flashing ANY model G7. I have downloaded all available KDZs for each model, and LG got smart and they all have different RSA certs.
-- Brian

Dvalin21 said:
Thank you sir, see if you can try to pull the recovery.img. The firmware didnt seem to include one. I may try and download an older firmware and see if i can recover it from there instead. If everyone can help with this search, it could prove important.
Click to expand...
Click to collapse
I kept hitting security key issues, possibly due to my limited usage of adb and fastboot. My phone had already updated so I don't see the download anywhere, I guess to the A/B partition setup.
and good luck to you, runningnak3d

Guys I need help! can someone drop me a dump of LG g7 G710tm. just hardbricked neeed dump to revive my phone!!!!

kumasi_kg said:
Guys I need help! can someone drop me a dump of LG g7 G710tm. just hardbricked neeed dump to revive my phone!!!!
Click to expand...
Click to collapse
you can find them here:
https://lg-firmwares.com/lg-lmg710tmp-firmwares/
Does anyone know how to change the certificates between firmwares?

Question Couldn't connect to msm op9 global. /Now connecting. !

Ive uploaded signed Qualcomm driver's I found that install on windows and don't turn on test mode. These work. Then afterwards toggle USB options with device plugged in PC ,change from charging to PTP and let it automatically install drivers. Rebooted and opened msm tool and Is connecting and now showing 2 ports. Hope this works for anyone having trouble ; as earlier I had no Qualcomm driver's installed and no ports showing on msm tool after many attempts to install drivers. I'm now ready when something comes along to flash. After rebooting PC use cmd window adb reboot edl. Will then show up on msm tool as connected. When installing Qualcomm driver's choose first option Wwan is not used to get Ip address. If this works for you hit the like button "it's free". I've seen many people complaining they can't connect to msm tool. This fixed my issues. Tested on windows 10 pro
Driver's. https://drive.google.com/file/d/1AOeuMj6D5f6H4yhAC1QKGN437qV9YmJs/view?usp=drivesdk

Mattie69 can you explain how to work the MSMTool to me? It wants a login and i dont understand exactly what to do.

Do these overwrite existing drivers (used for rooting), or just add additional drivers to Windows?

XNine said:
Do these overwrite existing drivers (used for rooting), or just add additional drivers to Windows?
Click to expand...
Click to collapse
No additional driver's need to make Qualcomm devices/one plus phones to connect to msm tool.

illusiveairforce said:
Mattie69 can you explain how to work the MSMTool to me? It wants a login and i dont understand exactly what to do.
Click to expand...
Click to collapse
You don't use the factory one use the one above or below. It's a tool that relocks bootloader and flashes device to original firmware that it was shipped with. It's an anti-brick tool so to speak.

I still cant get it to work. the driver looks to be working and MSM identifying it
but no matter what i do it wont progress. i cant adb reboot because adnb nor fastboot are responsive. the phone just disconnectes and reconnects USB over and over and thats it. no button combo of volume keys and power being held for along time seems to work either.

I finally got it functional and now at "Image does not match" tried on 3 other machines with 3 seperate MSm installs.
9 5G LE2115 is my phone I bought directly form OnePlus. Idk what to do from here.

Usually kicks up that warning if your trying to use the wrong msm tool.?

i tried this one, the one from reddits backup area and the offical one linked to me by the angriest technician alive. it just boots and reboots and reboots. no matter the cable, version, cord. port, usb standard, serial setting or any combination of drivers form signed, unsigned and official, everything always leads to that same error.
its insane. the tech said "i didnt say run that (MSM he linked me) , were not liable to what it did"
I replied with " it didnt flash anything, thats why im contacting you and its qualcomms software, youre the company official making customers download altered /unofficial builds of another companies intellectual property. Im sure theyll be so happy to find out what you are doing"
he just logged after that. The balls on that guy. They Qualcomm didnt incorporate region based logins and VM Protect into MSM because its fun.
So yeah, hopefully i fix it before qualcomm returns my my emails.

applyscience said:
i tried this one, the one from reddits backup area and the offical one linked to me by the angriest technician alive. it just boots and reboots and reboots. no matter the cable, version, cord. port, usb standard, serial setting or any combination of drivers form signed, unsigned and official, everything always leads to that same error.
its insane. the tech said "i didnt say run that (MSM he linked me) , were not liable to what it did"
I replied with " it didnt flash anything, thats why im contacting you and its qualcomms software, youre the company official making customers download altered /unofficial builds of another companies intellectual property. Im sure theyll be so happy to find out what you are doing"
he just logged after that. The balls on that guy. They Qualcomm didnt incorporate region based logins and VM Protect into MSM because its fun.
So yeah, hopefully i fix it before qualcomm returns my my emails.
Click to expand...
Click to collapse
What about that global fastboot rom I linked you to?

mattie_49 said:
What about that global fastboot rom I linked you to?
Click to expand...
Click to collapse
man, sorry super tired. yeah no fastboot at all.no screen activity ever, all i get is usb plug in and out sounds every 3 seconds on my computer.
no fastboot, no adb. nothing.

applyscience said:
man, sorry super tired. yeah no fastboot at all.no screen activity ever, all i get is usb plug in and out sounds every 3 seconds on my computer.
no fastboot, no adb. nothing.
Click to expand...
Click to collapse
You were able to get back from aospa though right? Via msm

mattie_49 said:
You were able to get back from aospa though right? Via msm
Click to expand...
Click to collapse
i always had fastboot access during that, i just was too stupid to extract my own img files form the paylod dumps (theres so many guides online, i just suck with it) anyhow, after you hooked me up with download i just ran the the imgs in a flash-all bat file to clean up both slots of the phone and it was wonderful. as soon as i went to the unofficial lineage my phone just gave up. 2 reboots later.
im not sure what im going to do. its been a long day and not too pleased with myself so im trying to just procrastinate it till tmw or sunday.

[17784][07-04 07:23:08.893]<4> [3] [CSerialCommHelper] No data in buffer to be sent 0
[17784][07-04 07:23:11.061]<4> [3] [SP][195] Check cmd done status failed. 1​
this is the 2 lines in the log that have ruined my weekend.

I'm investigating possible solutions to common MSM errors that prevent flashing.
See the following thread and feel free to try the steps outlined if you're brave enough.
Please report back your findings.
[ADVANCED] [UNTESTED] Possible Fix - MSM Errors (Sahara, Param info, etc)
WARNING: THE FOLLOWING IS FOR INFORMATIONAL PURPOSES ONLY AND MAY FURTHER DAMAGE YOUR DEVICE. EXERCISE EXTREME CAUTION. USE ONLY AS A LAST RESORT. This was tested with a Global OnePlus 9 LE2115 Overview So I was encountering an error with MSM...
forum.xda-developers.com

Can you re-up these? I'm getting a 404 on the google drive link.

Ethanadams642 said:
Can you re-up these? I'm getting a 404 on the google drive link.
Click to expand...
Click to collapse
Index of /list/Unbrick_Tools

Bricked V450 sprint attempting to unlock bootloader

I was following a guide on unlocking the bootloader and rooting my v450 device, this was using QFIL to load the abl_a and abl_b files but made a mistake and accidentally loaded the file to the MPT partition on the device. I made a backup of the abl_a partition but not of any other partitions.
Now the device gets stuck on the LG V50 boot screen and I can't get it to boot into any mode other than EFL.
One way I feel might work is by obtaining a backup of the MPT file, if this is correct does anyone know where I can find this,
Does anyone know whether this is something I can fix or if the phone is dead, any help is appreciated.
Thanks.

The phone is not necessarily dead!
Search google for your models QFIL dump, I found someone has uploaded a set of files for the Sprint 450. Download all, or the file you need and write using QFIL. I would download all and replace with all. Just in case there is a miss-match across versions, for example you might have one date version of boot and a different one for the MPT.
It is very difficult to fully break any android phone, time and effort will find you a solution. I broke mine for a short time trying to do the same process and ultimately fixed by trying a whole bunch of troubleshooting before I found what I needed to do.
In your case if you can find a set of files online and write each partition one by one, I think you will be good. Of course you will have to restart the whole process of bootloader changes if you want that.
Good luck

feyd2blak said:
The phone is not necessarily dead!
Search google for your models QFIL dump, I found someone has uploaded a set of files for the Sprint 450. Download all, or the file you need and write using QFIL. I would download all and replace with all. Just in case there is a miss-match across versions, for example you might have one date version of boot and a different one for the MPT.
It is very difficult to fully break any android phone, time and effort will find you a solution. I broke mine for a short time trying to do the same process and ultimately fixed by trying a whole bunch of troubleshooting before I found what I needed to do.
In your case if you can find a set of files online and write each partition one by one, I think you will be good. Of course you will have to restart the whole process of bootloader changes if you want that.
Good luck
Click to expand...
Click to collapse
Thank you man, this is reassuring to hear, I'm going to look for a QFIL dump now, will update this post if I find any success.

T
feyd2blak said:
The phone is not necessarily dead!
Search google for your models QFIL dump, I found someone has uploaded a set of files for the Sprint 450. Download all, or the file you need and write using QFIL. I would download all and replace with all. Just in case there is a miss-match across versions, for example you might have one date version of boot and a different one for the MPT.
It is very difficult to fully break any android phone, time and effort will find you a solution. I broke mine for a short time trying to do the same process and ultimately fixed by trying a whole bunch of troubleshooting before I found what I needed to do.
In your case if you can find a set of files online and write each partition one by one, I think you will be good. Of course you will have to restart the whole process of bootloader changes if you want that.
Good luck
Click to expand...
Click to collapse
This worked, I manually replaced every partition and the phone is working now. thank you so much, I probably wouldn't have tried this without the info you provided.
link to dump used: https://drive.google.com/file/d/13AJ8SnKmpOrTQF2EQ1odJK7-4qfUTIdF/view

doublespicc said:
T
This worked, I manually replaced every partition and the phone is working now. thank you so much, I probably wouldn't have tried this without the info you provided.
link to dump used: https://drive.google.com/file/d/13AJ8SnKmpOrTQF2EQ1odJK7-4qfUTIdF/view
Click to expand...
Click to collapse
Glad I could help!

Tell me, in the dump that is uploaded there are files rawprogram0.xml, rawprogram1.xml, etc. How to flash them?

BlankFlash for Pixel 3

Well, it seems my daughter has been the unfortunate one of many that has been hit by her Pixel 3 being "bricked" for no apparent reason.
After a full afternoon of research, I now understand the state it's in and that it's sitting in EDL and won't cycle out of it. I'm a Linux guy, and can plainly see that lsusb is reporting it being 05c6:9008 in "QDL" mode. So I've got the QDL tool for Linux, I understand fastboot and adb, etc. HOWEVER, I'm rather foggy about how to acquire, or perhaps create, a "blankflash" for the Pixel 3. (Or maybe I'm just tired...) In any case, is there anyone here that might point me in the right direction of how to get, or even create, a blankflash for this phone?
So ANY pointers in the right direction on a blankflash for the Pixel 3 would be appreciated. Thanks all!

TechnicalJohn said:
Well, it seems my daughter has been the unfortunate one of many that has been hit by her Pixel 3 being "bricked" for no apparent reason.
After a full afternoon of research, I now understand the state it's in and that it's sitting in EDL and won't cycle out of it. I'm a Linux guy, and can plainly see that lsusb is reporting it being 05c6:9008 in "QDL" mode. So I've got the QDL tool for Linux, I understand fastboot and adb, etc. HOWEVER, I'm rather foggy about how to acquire, or perhaps create, a "blankflash" for the Pixel 3. (Or maybe I'm just tired...) In any case, is there anyone here that might point me in the right direction of how to get, or even create, a blankflash for this phone?
So ANY pointers in the right direction on a blankflash for the Pixel 3 would be appreciated. Thanks all!
Click to expand...
Click to collapse
I believe this is the best thread for anyone with this issue to be reading. The issue is discussed and unfortunately, there is no resolution.
That said, I've never heard of a 'blank flash'. But, what we do know is that a device that is stuck in edl mode means u can't get to the normal recovery utilities like fastboot or adb. And because google won't release the 'programmer firehose' so that qfil can access the device in edl mode, there's really no way to 'flash' anything, blank or otherwise.
I wish I was wrong, but am quite sure this is the unfortunate situation, unless google releases the firehose.
(When u say 'QDL tool for linux', do u mean the bkerler edl python utilities? Unfortunately, they too will of course require the programmers firehose. If that's available somewhere, would luv to know about it).
cheers

AsItLies said:
I believe this is the best thread for anyone with this issue to be reading. The issue is discussed and unfortunately, there is no resolution.
That said, I've never heard of a 'blank flash'. But, what we do know is that a device that is stuck in edl mode means u can't get to the normal recovery utilities like fastboot or adb. And because google won't release the 'programmer firehose' so that qfil can access the device in edl mode, there's really no way to 'flash' anything, blank or otherwise.
I wish I was wrong, but am quite sure this is the unfortunate situation, unless google releases the firehose.
(When u say 'QDL tool for linux', do u mean the bkerler edl python utilities? Unfortunately, they too will of course require the programmers firehose. If that's available somewhere, would luv to know about it).
cheers
Click to expand...
Click to collapse
Hey, thanks for the input as well as the move of my post to a more appropriate forum. I felt like I had hit the end of the road, but was hopeful maybe there was an off-road path
Here are a couple sources for my references...
I found this XDA post mentioning the EDL and QDL:
[GUIDE] unbrick and flash Official ROM in EDL on linux
I'm running Kubuntu 20.04, and you can install QDL using snap: https://snapcraft.io/qdl
The "blank flash" reference came from this guide for a Moto G7:
Hard Bricked My Moto G7 Plus after Downgrade: How to Fix
LOL, ironically the blankflash.zip is hosted here on XDA somewhere.
I'm in the process of evaluating "new to her" phones for her to replace this Pixel 3... but I'm still hoping to resurrect this thing, since the knowledge would be invaluable.

TechnicalJohn said:
Hey, thanks for the input as well as the move of my post to a more appropriate forum. I felt like I had hit the end of the road, but was hopeful maybe there was an off-road path
Here are a couple sources for my references...
I found this XDA post mentioning the EDL and QDL:
[GUIDE] unbrick and flash Official ROM in EDL on linux
I'm running Kubuntu 20.04, and you can install QDL using snap: https://snapcraft.io/qdl
The "blank flash" reference came from this guide for a Moto G7:
Hard Bricked My Moto G7 Plus after Downgrade: How to Fix
LOL, ironically the blankflash.zip is hosted here on XDA somewhere.
I'm in the process of evaluating "new to her" phones for her to replace this Pixel 3... but I'm still hoping to resurrect this thing, since the knowledge would be invaluable.
Click to expand...
Click to collapse
I certainly understand the desire to fix the device, I mean, there's nothing wrong with them, they work fine, normally.
But, even the first link you mention has the following pre-reqs: and it's the 3rd item listed that no one has (afaik). The patch xml isn't needed, the rawprogram xml can be created / modified from another source, but not the firehose file. It's specific to the device, and google, as said, won't release it. So just to clarify, I've used edl mode on numerous LG devices (as their firehose file is available), I've used both qfil and bkerler edl utilities (python based), and neither of them can access a device without the firehose file, it's just not possible.
Truly wish that if anyone has that file, pls let us know, because without it, these devices are bricks.
patch0.xml
rawprogram_unparse0.xml,
prog_firehose_ddr.elf (could have also a .mbn file extension, it's the same)

AsItLies said:
I certainly understand the desire to fix the device, I mean, there's nothing wrong with them, they work fine, normally.
But, even the first link you mention has the following pre-reqs: and it's the 3rd item listed that no one has (afaik). The patch xml isn't needed, the rawprogram xml can be created / modified from another source, but not the firehose file. It's specific to the device, and google, as said, won't release it. So just to clarify, I've used edl mode on numerous LG devices (as their firehose file is available), I've used both qfil and bkerler edl utilities (python based), and neither of them can access a device without the firehose file, it's just not possible.
Truly wish that if anyone has that file, pls let us know, because without it, these devices are bricks.
patch0.xml
rawprogram_unparse0.xml,
prog_firehose_ddr.elf (could have also a .mbn file extension, it's the same)
Click to expand...
Click to collapse
Yeah, I was just giving reference to what lead me to the awareness of the QDL and the fact that it's possible to flash these Qualcomm devices. I could see that I was missing a piece there, and now that you've pointed me in the direction of the other thread I see things a bit more clearly after a sleep.
All good info, and perhaps we'll get the needed piece at some point! Too bad we can't construct that file from a dump or something.

Question Your device is corrupt. Oneplus 9

I tried putting the beta of OOS13 on my Oneplus and now i get that error message and ive been trying for so long.
the serial number is fb7b98a9

Flash by edl if you can't do it then pm I'll fix it by tv

Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck

applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Click to expand...
Click to collapse
applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck
Click to expand...
Click to collapse
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day

SubColdSnow said:
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day
Click to expand...
Click to collapse
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above

rizzmughal said:
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above
Click to expand...
Click to collapse
i tried and just get device does not match image

SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try it again. if anything, you will be attempting on the other slot. Many haves had issues and it just started working.
it could have been slot related, or possibly some minor detail that is finicky. (ex. you usually want to start the msmtoolkit and let it stay in the "waiting for device" phase and plug in your phone (which should be in EDL mode . youll know by the peeps of it habitually connecting/disconnecting on your PC)
assure you have india selected, assure you have the proper conditionals on/off per the guide's explication.
Assure you have the qualcom drivers installed, and they reflect the naming convention.
follow along the guide again and Just keep attempting it and don't get discouraged. Part of the reason people offer guides here is that they themselves failed many times until they got they figured it out and are trying to save people from it.
youll get it, dont worry.

I had this problem because I flashed a custom kernel on a custom rom today

SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try the modded msm tool. it worked for me.