Develop Bugs

Reinstall firmware

I have the 22a kdz, but the software I've downloaded to flash it onto the vk815 isn't working. Would someone please point me to valid files for downloading? I tried the apps to SD hack, and that makes my software modified. That didn't seem to work, and maybe why the 23a update still gives me unexpected SD ejection. I want a clean pure install. I'm not concerned about root.

Hi.
First, are you using the original USB cable with a USB 2.0 port that comes directly off your Windows PC's motherboard - not a USB 3.x port and not through a USB hub?
Installed the latest VK815 drivers from LG's website? Reboot the PC after while the device is disconnected from it.
Once you put the device in Download mode, check in Windows' Device Manager in the Port section to see if the device is listed "LGE...". Until it is, any attempts to flash a KDZ or TOT will be futile. It can take up to 5-10 minutes to load the driver you installed, and USB works by loading the driver separately for each different USB port you plug the same device into.
If you Google:
Code:
XDA LG Flash Tool 2014
you'll find it. If that's exactly what you're using and it's not working, could you please be more specific about how it's not working? 99% of the time (maybe only 95%) ignore any error dialog that pops up from it, move the error dialogs out of your way if necessary but don't click on any buttons in them, and within 5-10 minutes you'll find your device is flashed. This is true in general for all LG devices.
You should also be able to use the official Verizon-LG software on your tablet, if absolutely needed. When you first plug it into your Windows PC it comes up as "Installer" before it switches to MTP or another mode. Install that from Windows and the official tool will download and install the latest KDZ that's released (23A? - I have the VK810 so not sure what latest VK815 releases are). The difference between the official tool and LG Flash Tool 2014 is the official tool downloads the newest KDZ every time you choose to upgrade/update with it, and can't make use a pre-downloaded KDZ, and then deletes the KDZ when it's done flashing although if you're fast enough you can copy it elsewhere while it's flashing so you have it handy. It's the easiest way to get the latest KDZ for any LG device on Verizon these days, when it's not available any other way yet.
When you flash with LG Flash Tool 2014, use the CSE option which will wipe everything including user apps, user data and internal storage.
Lastly, if you return to stock and the problem persists and it's still under warranty, LG has excellent warranty service.

Thanks! It all seems like I was doing everything right. I'll give it another go as you've directed, to be sure. It was my understanding that perhaps when it updated to Marshmallow, the flash function was deactivated? Maybe that was just for installing images and not flashing firmware.

Yep, fails to connect. Trying to install the LG UP CY dll for vk815, getting an Error 2356. Bummer.

Crap, just lost everything I just typed.
You verified the tablet shows up in Device Manager while it's in Download mode?
You were trying both LG Flash Tool 2014 and LGUp or just LGUp? LGUp doesn't work with all devices (not the VS985 Verizon G3, and I don't think my VK810 Verizon G Pad 8.3).
On the VS985, when 35B Lollipop 5.1.1 came out, we could no longer flash older than the 35B KDZ. We could only downgrade from 100% stock on 35B and higher by using our 10B TOT along with the .DLL that's extracted from the 35B KDZ. I don't know if you can get your hands on a TOT for the VK815, they're rarer than KDZs and usually have to be leaked by someone on the inside, I think.
Also, sometimes a different Windows PC makes the difference.

Yep, turns up OK. It starts to connect in LG UP, but fails after a few seconds. The specific driver also fails to completely install.

Einsteindks said:
Yep, turns up OK. It starts to connect in LG UP, but fails after a few seconds. The specific driver also fails to completely install.
Click to expand...
Click to collapse
I don't know if LGUp works with the VK815. It doesn't work with the VS985. Good you Google for and try the LG Flash Tool 2014 I had mentioned?

There's a driver packet for the vk815, but it wasn't compiled right, or something, and fails to install. I may have a shot if a clean version can be found. Flash tool 2014 is reported to not work after Marshmallow is installed. That is true.

Einsteindks said:
There's a driver packet for the vk815, but it wasn't compiled right, or something, and fails to install. I may have a shot if a clean version can be found. Flash tool 2014 is reported to not work after Marshmallow is installed. That is true.
Click to expand...
Click to collapse
If LG Flash Tool 2014 can't flash your older KDZ while you're on Marshmallow, then LGUp won't be able to, either, as far as I know. LGUp doesn't get around stock bootloader and laf (Download mode) limitations.
Is there a TOT for the VK815? That and using the newer .DLL that comes inside the latest stock KDZ is the only way to downgrade from Lollipop 5.1.1 and Marshmallow on the VS985.

roirraW "edor" ehT said:
If LG Flash Tool 2014 can't flash your older KDZ while you're on Marshmallow, then LGUp won't be able to, either, as far as I know. LGUp doesn't get around stock bootloader and laf (Download mode) limitations.
Is there a TOT for the VK815? That and using the newer .DLL that comes inside the latest stock KDZ is the only way to downgrade from Lollipop 5.1.1 and Marshmallow on the VS985.
Click to expand...
Click to collapse
I suspect the new dll pack is for LG UP, because Mm update 'closed out' the old flashers.
Shoot! I just realized you may be thinking I want to downgrade. Nope, only wanna clean install of Mm, as mine currently reads as 'modified'.

The other day, I was messing around and got into recovery where there is an option for debug mode! Gonna have to try that to see if anyone will see the tablet. Not sure, but it may be feasible to push the system image via ADB?

Update: debugging mode yielded no change. Guess I'll just have to wait until either Verizon or LG gets their thumb out their ass and develop a better driver file for the LG G Pad X 8.3.

im looking for the same thing, trying to get my vk815 back to stock, its currently rooted on lollipop. the only kdz files i could find are MM but flash tool wont flash them, if i could find an older lollipop kdz i think it would work.

I recently found/installed new drivers/programs, but haven't bothered with them. My tablet still has the mysterious sd ejection bug, despite the latest update.
Sent from my XT1254 using Tapatalk

so did you figure out how to flash a kdz file with the vk815 tablet? if so which flash tool and files were you using, if possible could you please share a link? I have both LGFlashTool2014 as well as LGUP, but the only kdz files I have are all marshmallow, and I could not find a dll file to use LGUP for the vk815.

I played stupid and sent my tablet back to LG to have them reflash official firmware. I haven't messed with it since.
Sent from my XT1254 using Tapatalk

hmm well, i sure hope I dont have to send it back to LG, the root method I used was posted by player911, he also posted a method to unroot, but the KDZ files are no longer on the internet.

Help save a bricked lg g3

:crying:
My issues is quite complicated. Please be patient and read on.
Less than a week ago, I bought an LG G3 D855. It wasn't brand new and definitely out of warranty.
It was on the 4.4.2 Os version but I couldn't update it because I couldn't locate the UPDATE CENTER and after some research online, I found out it was because it was rooted. I couldn't find a Supersu application anywhere on the phone anyways but Root checker confirmed that it was rooted.
I downloaded the stock kitkat firmware in a .tot format and I tried flashing using LG Flash Tool for TOT but it failed because "Device version is different"
I checked the Imei online and it stated that the device is a Sprint LS990 but the details embedded in the phone all say it is D855
I checked online and found a couple of posts about this error and one user said he was able to fix it by flashing the actual Sprint .tot with the lg flash tool. I tried that but it didn't work. It still said "Device version is different. Check BIN or dll"
I checked online and found results pointing to a generic .dll file for G3s and I downloaded it but when I used it on the Flash tool, it resulted to an error "CrossDL blah blah"
So I found a Marshmallow kdz file. LGUP won't see my device model so I was able to flash it after editting the software in my build.prop to D85510n.
***I have always changed the port to COM41 in all the steps I used
The LG UP detected my model and it flashed to 100% but got stuck on a bootloop by loading the lg screen, freezing and restarting by it self. It never gets to the homescreen.
I downloaded lollipop kdz reflashed using LGUP in a form of downgrade and it got to 100% and got stuck at the lg screen while trying to reboot.
I redownloaded the stock kitkat rom and used the Lg flash tool but it failed. It said 'PID null IMEI Null"
I used LGUP to reflashed. It came to my understanding that the LGUP can flash both kdz and tot. So it flashed to 100% but got stuck at the lg screen and I have tried all I can but it is stuck. It can go into download tho. I don't know what to do about the IMEI. I don't know if the last flash retrieved it. I don't kniw what to do.
It no longer shows as LGE AndroidNet USB Serial
Please can anyone help me?
I just need my phone to work again. I was stubborn and now I regret it. I should have just stuck to kitkat. I'm so desperate to get my phone working that I wouldn't mind Android Froyo Os if it was ever possible.
PLEASE HELP!!!

I think you have to repair the IMEI...
maybe this can help
https://youtu.be/nwzgs1Cmr9k
Sent from my LG-D855 using XDA Free mobile app

I think that he forgot to hard reset after flashing the kdz.

i completly know what you should do:
1: force your phone into qualcomm 9008 mod.
2: use board diag unbrick instruction and it will boot on download mod. for unbrick you will need best kitkat tot for your G3 model.
3: flash best lollipop or kitkat tot to make your phone alive
and then flash it with any kdz you want(it should be for your G3 model)
my telegram ID : @Erfan_rv

pls help me
Apparently, it seems my bricked phone keeps disconnecting during flashing process. I dont think it the fault of the cable because I have used different ones and they all seem to work fine with other phones. I have tried a different computer and still the same results. it connects as qualcom 9008 but once I try to start flashing, it disconnects and interrupts the flashing process. my phone just shows a grey screen now when I power it up with the battery in. also, I was trying to upgrade from linear os to the latest linear os. I cant fine the tot out there so im using zv6 currently. could this also be the problem? thanks in advance

Unknown baseband along with null IMEI

So, recently, I've been struggling with a strange issue which I think that it's a hardware issue. Let me explain you all the things I've done so far.
I was on LOS 14.1 and wanted to go back to stock rom. I had used Nougat for long time and never used stock MM on my G4. I just wanted to give MM a try. Maybe it could give me better battery life and performance. I don't know.
Since I have an UsU'd H815, I properly flashed stock mm boot, mm system, mm modem and then the UsU H815 baseband. However, when the device boots, I got "com.android.phone stopped" warning all the time. Then I went into recovery mode, flashed UsU mm boot and stock MM modem. Now, I got cellular working, set up everything but then I realized that camera didn't work this time. So, basically,
Stock boot + stock modem + UsU baseband = no cellular - camera works
UsU boot + stock modem + stock baseband = cellular works - no camera
Stock boot + stock modem + stock baseband = must crash with blue screen. But now, it just boots and everything works except cellular
Thinking that since I had on LS991 bootloader and maybe it is necessary for both baseband and the bootloader to be the same model/version, I flashed LS991 baseband. During boot animation, the phone got an instant reboot. I don't remember if it booted to either that blue modem crash screen or android system. Most probably it was Android system. Anyway, cellular didn't work anymore.
I've flashed whole backup (except aboot, laf, raw_resources) that I had created with SALT before UsU'ing my device. Still no luck. I always get null imei from *#06# and unknown baseband. When I launch hidden menu (*#546368*#815#), I also get force close on SVC Test > Version info. The information there about baseband, hw version, and NT code say that 'should be implemented'. So far, I think that it's a hardware issue.
Well, but with
Code:
cat /data/loggers/modem**a file including modem in its name**
, I see my IMEI and factory version. Somehow, some things recongize my imei number. I also see my imei on imei screen (power off the phone and hold down vol -, vol +, and the power button at the same time until it gets into imei screen).
I tried erasing modemst1, modemst2, and fcg which a reboot followed that proccess as it's stated and confirmed by some others to work here (ofc I restored my backup, still no luck).
Everything made me think that it was a software issue until I see this thread. The screenshot that the op shared on his 2nd post is same with mine. It says null for everything. And his 8th reply and the 3rd option I listed above (Stock boot + stock modem + stock baseband) makes me think that this is totally a hardware issue. Why the 3rd option makes me think that this is a hardware issue is that some/a part is damaged on the main board, and the device/chip/whatever cannot connect to it. Thus, cellular service cannot start, and since it cannot start, the things that must be going wrong with modem just go well.
I feel like I'm ready to try anything (which won't make it completely dead) to get cellular work on my G4, including flashing LS991's ARB 2 TOT file. I'm open to new thoughts and ideas.
Edit: So, according to my researches, I have found out that RX Module is about cellular (@madiweb also stated that on his 8th post on his thread I linked above). I've checked the service manual of H815. It is told there that if there is no gsm/wcdma/lte signal, RX Module (EAT62994301) has to be replaced. I'll ask to LG Customer Care and surely will add info here for the ones who need it.

berkantkz said:
[....]
Thinking that since I had on LS991 bootloader and maybe it is necessary for both baseband and the bootloader to be the same model/version, I flashed LS991 baseband.
[....]
Edit: So, according to my researches, I have found out that RX Module is about cellular (@madiweb also stated that on his 8th post on his thread I linked above). I've checked the service manual of H815. It is told there that if there is no gsm/wcdma/lte signal, RX Module (EAT62994301) has to be replaced. I'll ask to LG Customer Care and surely will add info here for the ones who need it.
Click to expand...
Click to collapse
I never wrote anywhere that you should flash a baseband of another device. Just think about it: I have created for every model its very own baseband package. Why should I do that when you could cross flash them? Wouldn't make sense right? The main reason (while there are others) is: ARB and signature checking within the modem files. I knew it from VS986 which also heavily uses the ARB "feature" in their firmwares: when you flash a modem firmware of the vs986 to the h815 it will break signal forever. The same may apply to others liek the LS991 which also makes heavy use of the ARB "feature" in their firmwares.
The ONLY way I know to recover from here (for the h815) is replacing the hardware (or in my case faking the device as bootloop affected and sending it to LG for repair). I cannot tell you which one blows the fuse but maybe it is that module you found above.
.-

steadfasterX said:
I never wrote anywhere that you should flash a baseband of another device. Just think about it: I have created for every model its very own baseband package. Why should I do that when you could cross flash them? Wouldn't make sense right? The main reason (while there are others) is: ARB and signature checking within the modem files. I knew it from VS986 which also heavily uses the ARB "feature" in their firmwares: when you flash a modem firmware of the vs986 to the h815 it will break signal forever. The same may apply to others liek the LS991 which also makes heavy use of the ARB "feature" in their firmwares.
The ONLY way I know to recover from here (for the h815) is replacing the hardware (or in my case faking the device as bootloop affected and sending it to LG for repair). I cannot tell you which one blows the fuse but maybe it is that module you found above.
.-
Click to expand...
Click to collapse
So, my G4 tour ends here. I'd make it bootlooped and send to LG for repair. However, it has been more than 2 years, and the warranty time is 24 months. So, I am out of warranty. Instead of repairing this device, I guess I would buy something new.
Thank you for your help. Fortunately, G4 community have a person like you!

The correct way to update an AT&T model

So I've just recovered my phone from my 1st attempt at updating to Pie on my unlocked AT&T v35.
But I'm left wondering if the process for updating from Oreo to Pie is somehow different than when I successfully updated from Marshmallow to Oreo.
The process I thought was:
1. Put phone in download mode
2. Connect phone to pc
3. Run the Modified version of LGUP
4. Select your ULM KDZ choice (any of the three will do)
5. Select Upgrade
6. Flash phone
Are any of these steps incorrect and should step 5 be Refurbish instead of Upgrade?

X-Nemesis said:
So I've just recovered my phone from my 1st attempt at updating to Pie on my unlocked AT&T v35.
But I'm left wondering if the process for updating from Oreo to Pie is somehow different than when I successfully updated from Marshmallow to Oreo.
The process I thought was:
1. Put phone in download mode
2. Connect phone to pc
3. Run the Modified version of LGUP
4. Select your ULM KDZ choice (any of the three will do)
5. Select Upgrade
6. Flash phone
Are any of these steps incorrect and should step 5 be Refurbish instead of Upgrade?
Click to expand...
Click to collapse
I used upgrade, when going from ULM 8.0 to ULM 9.0. I would assume you would use refurbish if going from stock to another firmware. Of course assumptions aren't really reliable.

I've been trying to figure out if I should do UPGRADE or REFURBISH as well.
I found this: https://forum.xda-developers.com/lg-v30/how-to/guide-how-to-upgrade-downgrade-restore-t3738917
Says REFURBISH wipes user data, UPGRADE does not. If moving from one image say from AT&T, to the Unlocked firmware I'd assume you want REFURBISH.

So since I used refurbish to go to the ulm software from 7 to 8, do I still need to refurbish going to any of the ulm pie variants?

Shawnashley said:
I used upgrade, when going from ULM 8.0 to ULM 9.0. I would assume you would use refurbish if going from stock to another firmware. Of course assumptions aren't really reliable.
Click to expand...
Click to collapse
That's what threw me for a loop on my first attempt. Since I'd successfully upgrade from the AT&T 7.0 firmware to I believe the Amazon 8.0 ULM firmware without issues, I thought the process would be the same going to 9.0. But I ran the upgrade through LGUP which was the modified version, and it crashed at 74% and sent me down a wonderful rabbits hole of brickage.

X-Nemesis said:
So I've just recovered my phone from my 1st attempt at updating to Pie on my unlocked AT&T v35.
But I'm left wondering if the process for updating from Oreo to Pie is somehow different than when I successfully updated from Marshmallow to Oreo.
The process I thought was:
1. Put phone in download mode
2. Connect phone to pc
3. Run the Modified version of LGUP
4. Select your ULM KDZ choice (any of the three will do)
5. Select Upgrade
6. Flash phone
Are any of these steps incorrect and should step 5 be Refurbish instead of Upgrade?
Click to expand...
Click to collapse
I don't understand how were you on Marshmallow before flashing to Oreo. I'm pretty sure the the V35 launched on Oreo 8.0. But I'm also looking for a way to get from Oreo to Pie on ULM kdz.
I went from AWM12k to ULM10i choosing REFURB and all went well (I followed xatokk's post on the lgV35 subreddit).
When I try to get from ULM10i to ULM20d (Pie .kdz) I guess I only have to drag ULM20d kdz in LGUP window?
I just want to make sure that's not how you bricked your phone before I try REFURB from ULM10i to ULM20d
Any advice would help, I'm a noob at this.

FWIW, partition DL worked fine going first from AT&T firmware to Oreo ULM and then again to Pie. Sadly I had to set up the phone again.

Neophy said:
I don't understand how were you on Marshmallow before flashing to Oreo. I'm pretty sure the the V35 launched on Oreo 8.0. But I'm also looking for a way to get from Oreo to Pie on ULM kdz
Click to expand...
Click to collapse
Sorry, Brainfart, I was completely out to lunch on that. I wanted to flash the latest available security update, but since I'm in Canada I could never get that from AT&T so I had to find a way to flash it and that led me to XDA and the whole LGUP process. So you were correct on that, and I did flash the Amazon 8.0 KDZ I believe without issue.
My brick happened when using the Amazon pie KDZ and using the same Upgrade process in LGUP. The update got to 74% and then crashed. I then tried to run the refurbish option but that crashed as well so by that time, my phone was beyond my knowledge of how to fix it

cmrntnnr said:
FWIW, partition DL worked fine going first from AT&T firmware to Oreo ULM and then again to Pie. Sadly I had to set up the phone again.
Click to expand...
Click to collapse
Partition DL was not available in the process list of the modded version of LGUP I used. Which one did you use? I think I found the right one.
Now, selecting PARTITION DL, do I need to select all like mentioned in the Frankenstein Phone thread for the V30?

Neophy said:
I don't understand how were you on Marshmallow before flashing to Oreo.
Click to expand...
Click to collapse
This phone launched with Oreo and had nothing prior. He's mistaken, confusing some other model.

That's what I did.
The error you experience may be due to a usb cable. a particular usb port on your computer, other software on your computer, and maybe bios settings. The v30 WTF and Frankenphone forums would be good places for background and solutions.
Fingers crossed for a successful flash.
Neophy said:
Partition DL was not available in the process list of the modded version of LGUP I used. Which one did you use? I think I found the right one.
Now, selecting PARTITION DL, do I need to select all like mentioned in the Frankenstein Phone thread for the V30?
Click to expand...
Click to collapse

Here's what I did if you don't already found a way. I also faced an error trying to flash to Pie ULM.kdz.
I don't know why but LGUP for developer patched from 9to5lg.com didn't work for me. I tried PARTITION DL it crashed at 91% and I also had to reboot my PC. I kept the phone plugged and reinstalled LGUP.
My V35 was on AWM12k when I got it. I followed xatokk's post on the lgV35 subreddit to get it to to ULM10i choosing REFURB.
I kept the same .dll I extracted from to ULM10i and I did a REFURB to ULM20d .kdz just dragging it to LGUP.
I hope this can help you.

To update my earlier reply on this topic. Somehow flashing REFURBISH from AT&T stock Oreo to ULM(Unlocked) Pie it failed and bricked my phone. As mentioned in another thread regarding unlocking the bootloader and root, I had to call on @motogvasyag to not only unbrick my phone remotely but he also unlocked the bootloader and rooted it. If anyone has any issues with bricking you might want to contact him. He's fast and does amazing work. I only mention this because I am very appreciative of him and his work. I'm not sure why my flashing failed at around 70 something percent but I'm glad to have my phone working again along with the update to pie and root.

Truth
MorningStarGG said:
To update my earlier reply on this topic. Somehow flashing REFURBISH from AT&T stock Oreo to ULM(Unlocked) Pie it failed and bricked my phone. As mentioned in another thread regarding unlocking the bootloader and root, I had to call on @motogvasyag to not only unbrick my phone remotely but he also unlocked the bootloader and rooted it. If anyone has any issues with bricking you might want to contact him. He's fast and does amazing work. I only mention this because I am very appreciative of him and his work. I'm not sure why my flashing failed at around 70 something percent but I'm glad to have my phone working again along with the update to pie and root.
Click to expand...
Click to collapse
@motogvasyag unbricked my AT&T V35 that was stuck in fastboot from a failed flash. Took care of it right away. Phone is now factory LG on Google Fi, Pie, wifi calling and all three carriers. Highly recommended!

LG G8 (LM-G820QM) Unlocked

I have LG G8 Alexa variant. Model LM-G820QM.
I think ts on latest firmware "qm21e". Right now I live in India so the VoLTE is not working. I tried to cross-flash it to Open firmware but LGUP gave error "Cant change the device(AMZ_US > OPEN_US)".
I have three questions.
Can I cross flash Korean firmware ?
And if so, will i get VoLTE working ?
And my G8 has 2 cams while the Korean varient has 3 cams. Will my cams work with Korean firmware ?
Thank you.

Do you by any chance still have the OPEN_US Firmware?
I've been looking everywhere for it but I can't find it.

Download LG Firmware for LG G8 ThinQ LMG820QM Android 10 Q kdz stock BPT Rom
Download Android 10 Q KDZ stock firmware for download with direct link
lg-roms.com
--------
| Firmware Update Android 10 Q kdz stock AMZ Rom
Download Android 10 Q KDZ stock firmware for download with direct link
lg-firmware.net
I think any of this 2 are OPEN. If not then reply me back I will deep search on google. I happend to found it somewhere but can't remember where exactly.

Thanks for your reply
Unfortunately, neither one worked.
I tried the first one, however the flash tool didn't work because (OPEN_US_>NAO_US)
The second one would not download at all. I don't think it would have worked anyway since my phone is not the Alexa version. It's factory unlocked, purchased from Best Buy.

Hey man, I was able to figure out my problem! Not only that, I discovered one of the NAO_US Firmwares was actually OPEN_US, and that worked for my phone. I am now back up and running, with an unlocked bootloader and Root!
I appreciate your help, and I want to help you if I can.
As for the cross-flashing, you can't do it via LGUP. The only possible way is to download the firehose for your phone and to use the Qualcomm Image Flash Loader(QIFL) tool. You can extract the firmware you want to flash, and load all the images into the QIFL partition manager. There is no guarantee your phone will boot from it, but you can try it. NOTE: Do NOT modify the OP partitions! This will cause your phone to throw an OPID mismatch error and it won't boot!
As for the cameras, you may be able to extract the current Camera APK from your phone and install that on the Korean firmware so that you are still able to use them. No guarantee this will work, and they might work fine with the Korean camera APK, but it's worth doing before you flash.

awgybop1 said:
Hey man, I was able to figure out my problem! Not only that, I discovered one of the NAO_US Firmwares was actually OPEN_US, and that worked for my phone. I am now back up and running, with an unlocked bootloader and Root!
I appreciate your help, and I want to help you if I can.
As for the cross-flashing, you can't do it via LGUP. The only possible way is to download the firehose for your phone and to use the Qualcomm Image Flash Loader(QIFL) tool. You can extract the firmware you want to flash, and load all the images into the QIFL partition manager. There is no guarantee your phone will boot from it, but you can try it. NOTE: Do NOT modify the OP partitions! This will cause your phone to throw an OPID mismatch error and it won't boot!
As for the cameras, you may be able to extract the current Camera APK from your phone and install that on the Korean firmware so that you are still able to use them. No guarantee this will work, and they might work fine with the Korean camera APK, but it's worth doing before you flash.
Click to expand...
Click to collapse
I see, but I just want VoLTE to work. I don't mind using stock rom or custom rom too. So keeping that in mind what do you suggest? And also, Do you think that your solution " I discovered one of the NAO_US Firmwares was actually OPEN_US, and that worked for my phone. I am now back up and running, with an unlocked bootloader and Root! " could work for me too ? If so do let me know how did you figured that NAO_US was actually OPEN_US. Maybe I can find out one for AMZ_US.
On the box Model : G820QM
SKU : G820QM8 (QM8 stands for AMZ)
Thank you.

I'm really not sure how VoLTE works internally, so I couldn't tell you if using another firmware would actually work for you - but the way I found out one of the firmwares was actually OPEN_US was by extracting it using the KMZ extractor tool someone made. This is how I was able to reflash the partition on my phone that I screwed up on in the first place and created a brick with. Like I said, you could manually reflash all those partitions one-by-one in QFIL, but i don't recommend it as it may not even work and could potentially brick your device. It's really up to you in this case, if you'd like to try though:
Download the firmware you want to try, search for KZM extractor on Google, download QFIL and all of it's prerequisites, and finally the firehose.
Use the KZM extractor and place the firmware inside of it.
Once it is done extracting all the files, put your phone into download mode and open QFIL
NOTE: DO NOT FLASH THE PARTITIONS WITH 'OP' IN THEM! Your phone won't boot for sure!
From QFIL use the firehose file and manually, one by one, sort through the output files of the KZM extractor and find the partitions that match their name and flash them with the file.
Zero guarantees this will work, and you may end up with a brick for a phone at the end of the day, but if you're that desperate it just might work.

Hi there.
I am still looking for solutions for VoLTE to work. I googled a lot and came on this post " https://piunikaweb.com/2021/06/07/unlocked-lg-g8-thinq-now-supports-att-volte-after-april-update/ "
Mine is Amazon version "QM8". Yet I did received april update via OTA. But still no VoLTE. I can OEM unlock from devs. Can I flash AT&T "QM7" on Amazon "QM8" ?
What do you think of this please let me know.
Thank you

VoLTE seems to depend on files in the OP partition, so crossflashing other partitions but not OP will not get VoLTE to work. LGUP will not allow crossflashing.
See my experience to get working VoLTE and Wifi Calling: https://forum.xda-developers.com/t/lg-g8-volte-fix.4113291/post-85455109
You will need to be bootloader unlocked and rooted.

awgybop1 said:
Hey man, I was able to figure out my problem! Not only that, I discovered one of the NAO_US Firmwares was actually OPEN_US, and that worked for my phone. I am now back up and running, with an unlocked bootloader and Root!
I appreciate your help, and I want to help you if I can.
As for the cross-flashing, you can't do it via LGUP. The only possible way is to download the firehose for your phone and to use the Qualcomm Image Flash Loader(QIFL) tool. You can extract the firmware you want to flash, and load all the images into the QIFL partition manager. There is no guarantee your phone will boot from it, but you can try it. NOTE: Do NOT modify the OP partitions! This will cause your phone to throw an OPID mismatch error and it won't boot!
As for the cameras, you may be able to extract the current Camera APK from your phone and install that on the Korean firmware so that you are still able to use them. No guarantee this will work, and they might work fine with the Korean camera APK, but it's worth doing before you flash.
Click to expand...
Click to collapse
Pls how to extract kdz,mine get error bad header