I have the LG G8 Thinq Sprint Model (LM-G820UMKIT) bought it pre-owned. I recently saw that there was a guide to unlock and root the LG G8 however the requirements is for the device to be on Android 10. I'm currently still on Android 9 and I am unable to update via software update, or through LG Suite. Is there anyway to update to A10?
Adelino80 said:
I have the LG G8 Thinq Sprint Model (LM-G820UMKIT) bought it pre-owned. I recently saw that there was a guide to unlock and root the LG G8 however the requirements is for the device to be on Android 10. I'm currently still on Android 9 and I am unable to update via software update, or through LG Suite. Is there anyway to update to A10?
Click to expand...
Click to collapse
It's unfortunate, but the guide is a bit misleading. I'd bet the person that wrote it had a specific version of android, and didn't know / want to indicate it would work on any other as they hadn't tested it.
But, there's virtually zero reason the unlock procedure shouldn't work on any version of android. The reason is very simple; all you do in that guide is use edl mode (any qualcomm device can do that), you flash the engineering abl to abl partition (it won't matter what version of android the rest of the system is), you go to fastboot (that's what the eng abl gives you), you unlock the boot-loader, you use fastboot to flash the original abl back.
Makes sense? See, you don't use that eng abl to boot the OS, you don't use it for anything at all, except to unlock the boot-loader. That's it. Period. There's no reason for it to not work no matters what version of android your system is.
As far as Sprint update goes... talk to sprint, ask them for help getting it updated. Sprint does not make their kdz available, if you don't get any OTA update from them, you'll then be faced with finding someone's partition backup, and all the complications involved / and danger, of flashing that.
The other option would be to crossflash to a rom that has a kdz. It too is involved and complicated, and potentially dangerous.
good luck
AsItLies said:
It's unfortunate, but the guide is a bit misleading. I'd bet the person that wrote it had a specific version of android, and didn't know / want to indicate it would work on any other as they hadn't tested it.
But, there's virtually zero reason the unlock procedure shouldn't work on any version of android. The reason is very simple; all you do in that guide is use edl mode (any qualcomm device can do that), you flash the engineering abl to abl partition (it won't matter what version of android the rest of the system is), you go to fastboot (that's what the eng abl gives you), you unlock the boot-loader, you use fastboot to flash the original abl back.
Makes sense? See, you don't use that eng abl to boot the OS, you don't use it for anything at all, except to unlock the boot-loader. That's it. Period. There's no reason for it to not work no matters what version of android your system is.
As far as Sprint update goes... talk to sprint, ask them for help getting it updated. Sprint does not make their kdz available, if you don't get any OTA update from them, you'll then be faced with finding someone's partition backup, and all the complications involved / and danger, of flashing that.
The other option would be to crossflash to a rom that has a kdz. It too is involved and complicated, and potentially dangerous.
good luck
Click to expand...
Click to collapse
Thanks for the advice! Yeah I wouldn't see why the device shouldn't be able to boot into EDL mode. I don't mind trying the unlock procedure with the guide, just sucks that there is no MSM tool to unbrick the device if anything does happen. As for updating to A10 I can live without, I only asked because the guide specified A10 as an requirement, which you already answered.
Adelino80 said:
Thanks for the advice! Yeah I wouldn't see why the device shouldn't be able to boot into EDL mode. I don't mind trying the unlock procedure with the guide, just sucks that there is no MSM tool to unbrick the device if anything does happen. As for updating to A10 I can live without, I only asked because the guide specified A10 as an requirement, which you already answered.
Click to expand...
Click to collapse
I would suggest that you look at the bkerler edl tools. Don't do anything until you backed up the device completely.
Related
Hello XDA,
I got an LG G4 gifted, and as one of the first things I want to do is to root it. However I seem to have quite some difficulties with it.
My previous phone was a Nexus 4, and I simply rooted with 'Nexus Root Toolkit'.
For this phone there appears to be many, different ways to do that.
First thing I need to be sure is what exact model my G4 is.
In 'Phone Info > Hardware' it simply says H815. In the LG Mobile Support Tool it says H815B (Which gives no result on Google). The phone is from Germany if it helps.
Second thing is that it says I can update to SW version v10c. But when I download the update, it simply throws a 'Invalid Software Package' error at the end of it. The LG Mobile Support Tool says I have no update avalaible instead.
Third thing is that I don't remember if I have to unlock the bootloader to root my phone (did that only once on my N4, forgot if it's needed). If yes, can somebody link me to the appropriate page? (I've read around LG itself released a tool to unlock that?) (Also, I will loose all my data IIRC?)
Last thing, obviously, the most appropriate Root guide for my model. I've read many of them, one requires you to have linux on your PC (Which is a nope), others mentions '10c' (which I suppose is the update I'm unable to get). So far I got myself only very confused. (Root voids warranty? IIRC LG still covers phone with root?)
Thanks in advanced for your help
EDIT: Currently trying with LG Bridge software, seems to work and says my phone is H81520A (So I suppose the part after the device code is the 'SW Version' ?).
EDIT2: Apparently updating with that software worked. Now on v10c (Marshmallow 6.0 - Unless there are other updates waiting)
You can indentify your model by adding your IMEI to the following link: csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=
(look for the field buyer)
The unlock process is described in this thread.
But don't fash SuperSu If you are on Android 6.0, because it will fail to boot. First flash an custom kernel (like this) and then SuperSu.
If you're unable to unlock the bootloader, then there is no possibilty to get root on Android 6.0.
Thanks. It says DEU at the buyer line.
D(eutschland)EU(Europe) I suppose.
And thanks for the link. In the kernel page it says 'download 20a or 20b? What's that number? So I need a Kernel that inclused SuperSU as flashing it on its own will cause that problem in few words?
What about this? http://forum.xda-developers.com/g4/development/repack-kernel-root-android-6-0-t3232387
From what it seems, it's a custom kernel + root. Would I still need to unlock the bootloader? Perhaps using the 'LG Site' section from the thread you linked (http://forum.xda-developers.com/g4/general/unlock-bootloader-install-twrp-root-t3128241)?
The software versions are quite strange on lg phones. 20A was the first test version that was released in poland. The official version now is 20B but phones with a branding have different versions. For example my phone has a vodafone branding and has the version 20A, but it is the same as unbranded 20B. (so it's really strange some times)
Look what is written in the settings under software information.
You need to unlock your bootloader to root your phone on Android 6.0 (this will void your warranty). You're right, it seems that SuperSu is already integrated in the kernel so you don't have flash SuperSu separately. But i am not complete sure because i didn't unlock my bootloader.
Thanks a lot for your help.
I managed to unlock the bootloader, but then I fuffed up..
Accidentally installed SuperSU (Was following that guide, and forgot about what you said).
Now the phone is kinda stuck at the very start, with the LG Logo (Not the animated one, the very first one)...
I'm hopeless now? D:
EDIT
I'm trying to recover with this video (LG G4 KDZ Firmware Restore Unbrick and unroot tutorial -- can't post links yet..)
But the LGFlashTool throws an error at 9% (imgur link -- can't post them fully yet) imgurDOTcom/pR1NYHD
EDIT2
Apparently I'm trying to flash a KDZ with Android 5.x while I'm on 6.0, which is a no. Will try with a 6.0 KDZ if I find one...
Else I hope for LG assistance (Or Amazon support, since the phone is less than 1 week old)
EDIT3
No luck with KDZ, but now the phone is going past to the animated logo, but being stuck there..
EDIT4
This saved me: http://forum.xda-developers.com/showpost.php?p=63843511&postcount=146
Worked perfectly, my phone is back and fully working
Sorry, i wasn't online the last couple of hours, but i'm glad that all worked out for you
X0rzist said:
Sorry, i wasn't online the last couple of hours, but i'm glad that all worked out for you
Click to expand...
Click to collapse
No problem, you were of great help.
I'm currently not trying to root until there is a safe procedure to do so for 6.0
I don't think that there will be an easier option in the near future. You can make a backup with twrp and try to flash the kernel again.
Mmm, currently I have only the bootloader unlocked. No root, no custom recovery.
I don't feel like to play more with these stuff in the near future, after I nearly bricked the G4
Perhaps later on.
Hi,
I purchased the phone in the UK from the network carrier Vodafone. I have done a fair bit of research on the rooting and unrooting process mainly via videos and reading tutorials on XDA.
I would like to root the phone and gain super user access and install some Xposed modules but would also like to be able to unroot and flash back to a stock Vodafone firmware encase I need to claim under warranty. I have been trolling the internet to get the correct KDZ file and found this site (ttp://devtester.ro/projects/lg-firmwares/country.php?country=United+Kingdom). I believe that the correct firmware may be on here but am a little confused on what the suffix and software version means to be honest.
The reason for my confusion is that I updated the firmware to 6.0 Marshmallow through the LG bridge but when I now check my phones software version it states v20b-234-15. I assume this is right but from memory the first software version when I got the phone was something like H81510B_00.
I cant remember exactly what it was before unfortunately but the KDZ files I have found state H81510C_00 (Suffix - AVDFVK) and H81510C_00 (AVDFLR) and this does seem to make sense but I'm thinking it was B instead of C but and not 100% on that.
Do you think these KDZ files would be the correct one to flash back to encase I run in to some problems rooting?
I am also assuming that this KDZ is Android Lollipop and not Marshmallow so is it OK to use this to revert back from Marshmallow?
Thanks and any help would be much appreciated.
Ross
The 10X version are all Lollipop, 20X is marshmallow.
When flashing a KDZ on your phone, what's important is what model your phone is. H815 in your case.
If you want to restore to stock in case something goes wrong, you can find everything here: http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
In there is a link to this directory: http://storagecow.eu/index.php?dir=Xda/LG+G4/ where you find pretty much all KDZ files for G4 phones.
I'm not that experienced myself, but I rooted my phone just recently and I can share my experience with you.
I have a H815. It was a V10c-TWN-XX version (Taiwan). I updated to Marshmallow with LG Bridge also and the new software version was V20b-TWN-XX.
Marshmallow rooting is not possible on my phone because I can't unlock the bootloader on it. And Marshmallow rooting is only possible with an unlocked bootloader. Unlocking the bootloader is only possible on European phones (http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS). I asked autoprime (renown user and developer here) if I can unlock bootloader after flashing an European KDZ on it. He said no, having European software on it is not enough, it has to be a phone manufactured for the european market. Dont know why, guess because of different hardware.
So, not being able to root MM, I had to revert back to stock (downgrade) using one of the KDZs.
I chose the most recent one in the directory I linked (which is the Poland H81510E). In the "Go Back to Stock" thread I linked the OP says to use LG Flash Tool 2014, which unfortunately doesn't work with Marshmallow. But fret not, it works with LG UP! http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
When I tried flashing the KDZ with Flash Tool 2014, the process failed with an error at 5%. It worked flawlessly with LG UP. Here's more information regarding downgrading, but it really isnt hard. Just download + install LG UP. Launch it. Connect your phone. Choose KDZ file. Select option "upgrade". Hit start.
NOTE: after the firmware update was done, the phone rebooted automatically and for me it stuck at at the LG Logo (bootloop). But a simple hard factory reset did it, the phone booted and my new version was 10e-something. With Lollipop 5.1 of course.
After that, I rooted my phone using this pre-rooted image: http://forum.xda-developers.com/g4/development/h815-eu-l-p-t-sea-twn-t3176195
and this guide: http://forum.xda-developers.com/g4/...-tmo-vzw-intl-variants-soon-root-lg-t3164765/
I now have a "H81510e-EUR-XX" Lollipop 5.1 with root (SuperSU 2.49).
I don't really know about Vodafone and if carrier specific firmware is necessary in this case. If not, you could use any 815 firmware.
From the site you have linked with the KDZ files..... it seems they are all the same.
If you check the table for H815 KDZs from Vodafone, there are some 10C and 10D versions. Now I compared the fileKey parameter in the URL to the 10C files and the 10D files and also the bytes of the files.
All the 10C version are identical to each other, same for 10D.
Check out this screenshot I made for you: http://i.imgur.com/Ie0w4us.png
Bytes are also identical, so it's pretty safe to say those are the same files.
Dont know why they are listed several times there. The suffix doesnt matter.
I'd grab a 10D if I were you. But I think the Poland 10E should work, too. Better confirm it with somebody else though.
If you flash your system to 10e, you can use the pre-rooted image I used. Otherwise you will have to inject root yourself: http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586. In this method you create an image of your system and inject root into the image, which you then flash back on your phone.
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!
So, I picked up a used G710VM 64GB Storage/4GB RAM, I specifically wanted this model because I'm on Verizon and wanted to ensure that my phone would work with their wack-as-all-hell network. Upon booting it up on the stock firmware for the first time, and intentionally not putting in my SIM, nor getting it online, I saw it using up 16 GBs of storage right out of the gate, and about 2.8 or so GBs of RAM. I thought this unacceptable, and so began my journey of putting custom ROM on it.
I was looking at putting either Lineage OS or AOSP, but both guides require getting TWRP on there first, and that has been my hang-up.
I followed this guide on getting the bootloader unlocked, and got that done.
Now my problem is fastboot mode, with the bootloader unlocked, and on the G710ULM11g firmware, I can get into it just fine. But on the G710EM20b, G710EM20d, and G710ULM20d firmwares I follow the steps to get into fastboot mode, get a warning about the bootloader being unlocked, and then it just does a proper boot up into the OS, every. single. time. And I've gone back and forth between my 8.0 and 9.0 versions of Android a few times, and confirmed it's only the 9.0 ones that are giving me this issue, the 8.0 one lets me in without fail.
Did I unlock the bootloader wrong? Or am I just using the wrong firmware? Has anyone else had luck with a G710VM version of the phone? Or did I hose myself by not buying a ULM or EM version?
Out of appreciation for all the work that everyone in this community does (I read lots but don't post often) I would say, you need to search and skim through at least an hour worth of posts to find that answer, but I'll link it here to say thanks. Short answer- PIE loses Fastboot commands. You can flash to Oreo, and then you should be able to use fastboot commands. I still haven't found a posted method for installing TWRP. I just acquired an 'unlocked' Sprint model with the ULM firmware and would love to explore rom options.
https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
In the same guide post if you look on page 6 you will find how people have updated to pie retaining fastboot.
It can also be used to use a pie vm rooted stock rom also.
MaitiuD2 said:
Out of appreciation for all the work that everyone in this community does (I read lots but don't post often) I would say, you need to search and skim through at least an hour worth of posts to find that answer, but I'll link it here to say thanks. Short answer- PIE loses Fastboot commands. You can flash to Oreo, and then you should be able to use fastboot commands. I still haven't found a posted method for installing TWRP. I just acquired an 'unlocked' Sprint model with the ULM firmware and would love to explore rom options.
https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
Click to expand...
Click to collapse
Thank you very much for responding.
And that really sucks about fastboot and Pie, now I have to wonder how LameMonster82 did it in his guide . Someone else there tried installing that TWRP from Oreo, and got his phone bricked for it.
Halogen_03 said:
So, I picked up a used G710VM 64GB Storage/4GB RAM, I specifically wanted this model because I'm on Verizon and wanted to ensure that my phone would work with their wack-as-all-hell network. Upon booting it up on the stock firmware for the first time, and intentionally not putting in my SIM, nor getting it online, I saw it using up 16 GBs of storage right out of the gate, and about 2.8 or so GBs of RAM. I thought this unacceptable, and so began my journey of putting custom ROM on it.
I was looking at putting either Lineage OS or AOSP, but both guides require getting TWRP on there first, and that has been my hang-up.
I followed this guide on getting the bootloader unlocked, and got that done.
Now my problem is fastboot mode, with the bootloader unlocked, and on the G710ULM11g firmware, I can get into it just fine. But on the G710EM20b, G710EM20d, and G710ULM20d firmwares I follow the steps to get into fastboot mode, get a warning about the bootloader being unlocked, and then it just does a proper boot up into the OS, every. single. time. And I've gone back and forth between my 8.0 and 9.0 versions of Android a few times, and confirmed it's only the 9.0 ones that are giving me this issue, the 8.0 one lets me in without fail.
Did I unlock the bootloader wrong? Or am I just using the wrong firmware? Has anyone else had luck with a G710VM version of the phone? Or did I hose myself by not buying a ULM or EM version?
Click to expand...
Click to collapse
Weird, I'm using G710EM20d firmware on my G710ULM and it boots to fastboot.
"Weird, I'm using G710EM20d firmware on my G710ULM and it boots to fastboot."
-----------------------------------------------------------------------------------------
I have the ULM model as well but the G710EM20d Model doesnt boot to fastboot. Could you tell me the KDZ file you used?
Example, "G710EM10b_00_0521.kdz"
I'd really appreciate the help
u should cross flash the ulm firmware by lg up and then boot ur device in to the download mode after erase laf partition
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