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
Related
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.
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.
Guide: How to upgrade/downgrade/restore OFFICIAL firmware on your V30.
Requirements:
LG V30
Windows PC
Official Firmware file for your V30 ending with .kdz. You can find it here https://forum.xda-developers.com/lg-v30/development or here https://lg-firmwares.com/
Bootloader does not need to be unlocked. All variants can be flashed using this method.
Only fully official, LG signed and blessed, unmodified firmware can be flashed using this method. No custom roms or recoveries!
Lets go:
Download and install LG USB drivers from here.
Download and install LG UP 1.14.3 from here.
Download .dll file for our V30, attached at the bottom of this post.
Navigate to C:\Program Files (x86)\LG Electronics\LGUP\model
Create folder called "common" and unzip the .dll file inside of it.
Connect the phone to your PC
[Optional]Open Device Manager and verify if under Ports you can see LGE Mobile USB Serial Port (COM...) to make sure the LG driver was installed correctly and the phone is visible.
Launch LGUP.exe
Select process called "UPGRADE" Warning: Selecting Refurbish will wipe user data.
Select the firmware file.
Click Start!
Your phone will automatically reboot into Download mode and upgrade firmware.
There's no need to do a factory reset afterwards but you can if you encounter any issues ofc. (I haven't)
Thanks for the guide.
thank you. I would love to try the MIUI ROM on this device.
padmanek said:
Requirements:
LG V30
Windows PC
Official Firmware file for your V30 ending with .kdz. You can find it here https://forum.xda-developers.com/lg-v30/development or here https://lg-firmwares.com/
Bootloader does not need to be unlocked. All variants can be flashed using this method.
Lets go:
Download and install LG USB drivers from here.
Download and install LG UP 1.14.3 from here.
Download .dll file for our V30, attached at the bottom of this post.
Navigate to C:\Program Files (x86)\LG Electronics\LGUP\model
Create folder called "common" and unzip the .dll file inside of it.
Connect the phone to your PC
[Optional]Open Device Manager and verify if under Ports you can see LGE Mobile USB Serial Port (COM...) to make sure the LG driver was installed correctly and the phone is visible.
Launch LGUP.exe
Select process called "UPGRADE" Warning: Selecting Refurbish will wipe user data.
Select the firmware file.
Click Start!
Your phone will automatically reboot into Download mode and upgrade firmware.
There's no need to do a factory reset afterwards but you can if you encounter any issues ofc. (I haven't)
Click to expand...
Click to collapse
My apologies if I misunderstood. Is this a way to apply alternative ROMs even on models with locked bootloaders and the ADB Commands stripped out such as the H 933? I know you said already that it will work on any variant but I had lost hope that this model would ever allow modding of the rum. I just want to make sure I'm not misunderstanding the intention of your guide.
Sent from my LG-H933 using Tapatalk
Mad Medik said:
My apologies if I misunderstood. Is this a way to apply alternative ROMs even on models with locked bootloaders and the ADB Commands stripped out such as the H 933? I know you said already that it will work on any variant but I had lost hope that this model would ever allow modding of the rum. I just want to make sure I'm not misunderstanding the intention of your guide.
Click to expand...
Click to collapse
It clearly says in the title of the thread and in the requirements that you can only flash full official (stock) firmware using this method...
Nothing custom. Everything needs to be RSA signed by LG.
astikv said:
thank you. I would love to try the MIUI ROM on this device.
Click to expand...
Click to collapse
Like above, only official (stock), LG signed and blessed firmware can be flashed using this method.
padmanek said:
It clearly says in the title of the thread and in the requirements that you can only flash full official (stock) firmware using this method...
Nothing custom. Everything needs to be RSA signed by LG.
Like above, only official (stock), LG signed and blessed firmware can be flashed using this method.
Click to expand...
Click to collapse
Oh well, wishful thinking amd my mistake. I read it as upgrade or downgrade (eg various images) or restore stock.
Sent from my LG-H933 using Tapatalk
padmanek said:
It clearly says in the title of the thread and in the requirements that you can only flash full official (stock) firmware using this method...
Nothing custom. Everything needs to be RSA signed by LG.
Like above, only official (stock), LG signed and blessed firmware can be flashed using this method.
Click to expand...
Click to collapse
I meant in 1 future.
padmanek said:
Requirements:
LG V30
Windows PC
Official Firmware file for your V30 ending with .kdz. You can find it here https://forum.xda-developers.com/lg-v30/development or here https://lg-firmwares.com/
Bootloader does not need to be unlocked. All variants can be flashed using this method.
Only fully official, LG signed and blessed, unmodified firmware can be flashed using this method. No custom roms or recoveries!
Lets go:
Download and install LG USB drivers from here.
Download and install LG UP 1.14.3 from here.
Download .dll file for our V30, attached at the bottom of this post.
Navigate to C:\Program Files (x86)\LG Electronics\LGUP\model
Create folder called "common" and unzip the .dll file inside of it.
Connect the phone to your PC
[Optional]Open Device Manager and verify if under Ports you can see LGE Mobile USB Serial Port (COM...) to make sure the LG driver was installed correctly and the phone is visible.
Launch LGUP.exe
Select process called "UPGRADE" Warning: Selecting Refurbish will wipe user data.
Select the firmware file.
Click Start!
Your phone will automatically reboot into Download mode and upgrade firmware.
There's no need to do a factory reset afterwards but you can if you encounter any issues ofc. (I haven't)
Click to expand...
Click to collapse
Out of interest, will this work on a rooted V30. I seem to struggle to get LGUP to boot my phone into download mode. Is it because I have twrp as recovery?
Sent from my LG-H930 using Tapatalk
thenoble06 said:
Out of interest, will this work on a rooted V30. I seem to struggle to get LGUP to boot my phone into download mode. Is it because I have twrp as recovery?
Sent from my LG-H930 using Tapatalk
Click to expand...
Click to collapse
It will work as long as your /laf partition is in tact. It containts the DL mode. It has nothing to do with /recovery partition where you most likely flashed TWRP.
Read this: https://forum.xda-developers.com/v20/how-to/laf-download-mode-how-root-t3676011
Just so I don't brick my device, I have an H930DS, therefore any firmware marked for this model (https://lg-firmwares.com/lg-h930ds-firmwares/), regardless of region, would work on my phone? My phone is currently on HK region version, can I flash the Indian firmware for the same model?
sasc said:
Just so I don't brick my device, I have an H930DS, therefore any firmware marked for this model (https://lg-firmwares.com/lg-h930ds-firmwares/), regardless of region, would work on my phone? My phone is currently on HK region version, can I flash the Indian firmware for the same model?
Click to expand...
Click to collapse
Probably not but feel free to try it and let us know how that goes.
sasc said:
Just so I don't brick my device, I have an H930DS, therefore any firmware marked for this model (https://lg-firmwares.com/lg-h930ds-firmwares/), regardless of region, would work on my phone? My phone is currently on HK region version, can I flash the Indian firmware for the same model?
Click to expand...
Click to collapse
I have no idea about cross region firmware flashing. I have not found any official documentation about how each of LG UP's functions exactly works, it's all user experience here on XDA. Supposedly, every region has firmware signed with different RSA key which is verified upon trying to flash and it will reject you if it's a mismatch. Also I doubt Indian region has the same bands as HK so you might cripple your mobile signal if you happen to be on a band that is not supported in Indian firmware. Personally I don't recommend trying it but its up to you Please share your experience if you do
I know for sure that all H930 sold in EU, regardless of what carrier can be flashed with the same H930 unbranded EU firmware, which removes all carrier bloat and branding.
@sasc Check the RSA signature of your firmware and compare it to the firmware you want to flash. If they match, then it won't brick your phone. Your phone may not work, but at least your will have access to DL mode. If they don't match, you will definitely brick your phone..
-- Brian
padmanek said:
I have no idea about cross region firmware flashing. I have not found any official documentation about how each of LG UP's functions exactly works, it's all user experience here on XDA. Supposedly, every region has firmware signed with different RSA key which is verified upon trying to flash and it will reject you if it's a mismatch. Also I doubt Indian region has the same bands as HK so you might cripple your mobile signal if you happen to be on a band that is not supported in Indian firmware. Personally I don't recommend trying it but its up to you Please share your experience if you do
I know for sure that all H930 sold in EU, regardless of what carrier can be flashed with the same H930 unbranded EU firmware, which removes all carrier bloat and branding.
Click to expand...
Click to collapse
India and HK are both global GSM regions. The bands are the same, just like Europe.
runningnak3d said:
@sasc Check the RSA signature of your firmware and compare it to the firmware you want to flash. If they match, then it won't brick your phone. Your phone may not work, but at least your will have access to DL mode. If they don't match, you will definitely brick your phone..
-- Brian
Click to expand...
Click to collapse
Could you please tell us what's the best way to check the signatures?
Okay.. I bring good news! You can definitely flash any KDZ as long as the model number is exactly the same. I flashed the HK Reginal kdz on my H930DS from India and I now have working VoLTE and VoWiFi.
In short, get the CORRECT kdz of the desired region for your model number, use LGUP, Upgrade option, and let it do its thing. Simple. This keeps the device official and under warranty.
PS - Please backup all data before doing this. Even though it is just an upgrade, play it safe. Just in case!
spacebar2011 said:
Okay.. I bring good news! You can definitely flash any KDZ as long as the model number is exactly the same. I flashed the HK Reginal kdz on my H930DS from India and I now have working VoLTE and VoWiFi.
In short, get the CORRECT kdz of the desired region for your model number, use LGUP, Upgrade option, and let it do its thing. Simple. This keeps the device official and under warranty.
PS - Please backup all data before doing this. Even though it is just an upgrade, play it safe. Just in case!
Click to expand...
Click to collapse
Thats great news ?. One question - to get VoWifi working, person at the other end should also have VoWifi? Or we can call VoWifi to VoLte. I have never tried VoWifi so just curious to know.
manishvy said:
Thats great news . One question - to get VoWifi working, person at the other end should also have VoWifi? Or we can call VoWifi to VoLte. I have never tried VoWifi so just curious to know.
Click to expand...
Click to collapse
VoWiFi does not need the person at the other end to have any special call options.
spacebar2011 said:
Okay.. I bring good news! You can definitely flash any KDZ as long as the model number is exactly the same. I flashed the HK Reginal kdz on my H930DS from India and I now have working VoLTE and VoWiFi.
In short, get the CORRECT kdz of the desired region for your model number, use LGUP, Upgrade option, and let it do its thing. Simple. This keeps the device official and under warranty.
PS - Please backup all data before doing this. Even though it is just an upgrade, play it safe. Just in case!
Click to expand...
Click to collapse
Thanks amazing news! I will try this asap to get Volte on my HG 930DS (India carrier)
spacebar2011 said:
Okay.. I bring good news! You can definitely flash any KDZ as long as the model number is exactly the same. I flashed the HK Reginal kdz on my H930DS from India and I now have working VoLTE and VoWiFi.
In short, get the CORRECT kdz of the desired region for your model number, use LGUP, Upgrade option, and let it do its thing. Simple. This keeps the device official and under warranty.
PS - Please backup all data before doing this. Even though it is just an upgrade, play it safe. Just in case!
Click to expand...
Click to collapse
So...kind of didn't work.
I used the H930DS marked India in lgfirmwares. The flashing process went fine, except for the phone getting stuck right after the last restart and the screen went blank. Waited a couple of mins and forced a restart using the power button..booted fine but all data was gone. Thankfully i did backup some stuff, but not all..
Checked the Software version, it says V11i-GLOBAL-COM, which is obviously not the India version. And, I still dont have Volte!! So, this was futile..
Can anyone point me to a certified H930DS India KDZ?
Can someone please point me in the direction to Unlock Bootloader and Root the OnePlus 9 Pro T-Mobile Version? I had the Global US Unlocked OnePlus 8 Pro and it was simple. Thank you in advance!
How To: Unlock the T-Mobile Bootloader
Hello all, this is a quick and simple guide to unlocking your T-Mobile locked bootloader. Just a reminder: unlocking the bootloader will wipe your data. The instructions here will apply to all T-Mobile OnePlus devices. Unlock your SIM. Some...
forum.xda-developers.com
Have u received token from tmo
Alright, my bootloader is unlocked now, but I'm not sure how to root at this point. My software version is 11.2.2.2.LE54CB. I can't find that last part (LE54CB) anywhere for download, so I'm not sure where to get my boot.img from. Anybody have some ideas?
Since there's no TWRP for this phone (yet), you have to get the boot.img file and use Magisk to directly patch it. I'm about to embark down this path, I got the T-Mobile version, also on 11.2.2.2 and I just got the bootloader unlocked. Now I need to root it.
glitchsys said:
Since there's no TWRP for this phone (yet), you have to get the boot.img file and use Magisk to directly patch it. I'm about to embark down this path, I got the T-Mobile version, also on 11.2.2.2 and I just got the bootloader unlocked. Now I need to root it.
Click to expand...
Click to collapse
Please let me know if you find a way. I'm super hesitant because of this other thread but I'm not willing to stop using my rooted OP7pro until my 9 is rooted.
I'm about to use https://forum.xda-developers.com/t/...ot-image-and-apply-root-to-the-phone.4263811/ djsubterrain's guide. Seems straight-forward.
1. I downloaded the Payload_Dumper program
2. I grabbed the official ROM from OnePlus's support site (https://www.oneplus.com/support/softwareupgrade/details?code=PM1617074857015) which is the same version my phone is already running.
3. I unzipped the OnePlus9ProOxygen_22.O.05_OTA_0050_all_2103242259_3611e0858f954e7d.zip file I got from OnePlus and there is a payload.bin file
I have to reboot out of linux and into my Windows partition in order to do the next part. But the Payload_Dumper program is supposed to extract a "boot.img" file from the payload.bin; I copy the boot.img file to my phone, into a temporary directory or whatever, and I use the Magisk application on my phone (which can be installed even if not rooted) to patch the boot.img file. I can then use fastboot to flash that image file. (Fastboot Boot rooted_boot.img) and after I reboot, I should, in theory, be rooted.
Since I didn't touch the stock recovery, I should also, in theory, be able to accept OTA updates pushed to my phone. Just normally an OTA update would "unroot" your phone, but guide has a "To retain root access after ROM/OTA update" section that I'm sure to try out next time an update is available. Worst case scenario though, the OTA update unroots me and I have to grab the new version from OnePlus's support site and go through the procedure again to extract the boot.img, patch it on the phone then flash it.
hmm. technically my phone is currently on "11.2.2.2.LE5ACB" and the one on OnePlus's support site is "11.2.2.2.LE15AA"
So there is a slight difference. Meh, should be ok. Worst case scenario I have to flash the entire "11.2.2.2.LE15AA "from OnePlus and I get T-Mobile De-Bloated.
Yeah, I had the exact same hesitation. I'm sorely curious to see how it goes for you. Because I have the OTA for the global rom, and I'm about to use the payload dumper. But if you're a step ahead of me, I'm happy to wait and see if it works for you.
jfsat said:
Yeah, I had the exact same hesitation. I'm sorely curious to see how it goes for you. Because I have the OTA for the global rom, and I'm about to use the payload dumper. But if you're a step ahead of me, I'm happy to wait and see if it works for you.
Click to expand...
Click to collapse
Happy to report it worked just fine. I was able to grab the boot.img from the "11.2.2.2.LE15AA" file on OnePlus's support site. I was able to use Magisk to patch the boot.img file. Then moment of truth..
"fastboot boot 11.2.2.2.LE15AA_patched_boot.img"
And my phone booted just fine. And it was now (temporarily) rooted. I was able to then go back into Magisk and direct-install root. Then reboot.
Magisk confirmed I'm still rooted.
So to all those curious, the boot.img from OnePlus Stock 11.2.2.2.LE15AA works fine on the T-Mobile 11.2.2.2.LE5ACB version.
I may look into using OOM or something to try and force-flash 11.2.2.2.LE5ACB onto my phone and completely De-T-Mobile this phone. I suspect I'll get OTA updates faster from OnePlus than I will from T-Mobile.
so I flashed to global coming from T-Mobile to global 11.2.2.2.
Everything went well. Until I system updated to 11.2.4.4. I realize now it didn't switch to full update and installed the incremental instead. After reboot I no longer have service.sim card is detected but again no service. Don't all the basics, so hopefully someone can help...
ryantf420 said:
so I flashed to global coming from T-Mobile to global 11.2.2.2.
Everything went well. Until I system updated to 11.2.4.4. I realize now it didn't switch to full update and installed the incremental instead. After reboot I no longer have service.sim card is detected but again no service. Don't all the basics, so hopefully someone can help...
Click to expand...
Click to collapse
How did you flash from T-Mobile's 11.2.2.2.LE5ACB over to the Global/USA 11.2.2.2.LE15AA ? The instructions say to put the zip file on the "sdcard" and then go to the update section and do a manual update. However T-Mobile conveniently removed that manual update option. So I was thinking I'd need to use msmtool or something to flash it.
Also you installed the AA version of the ROM, right? That's the U.S (not international) version, but it's generic, not T-Mobile modified. That's the one we should be flashing over our T-Mobile phones, converting them to the U.S Generic version, not the international version. AFAIK the U.S version isn't running 11.2.4.x yet, so not sure why you would get an OTA prompt about 11.2.4.x unless you'd flashed (again, how did you do this?) the international version and not the U.S version.
glitchsys said:
How did you flash from T-Mobile's 11.2.2.2.LE5ACB over to the Global/USA 11.2.2.2.LE15AA ? The instructions say to put the zip file on the "sdcard" and then go to the update section and do a manual update. However T-Mobile conveniently removed that manual update option. So I was thinking I'd need to use msmtool or something to flash it.
Also you installed the AA version of the ROM, right? That's the U.S (not international) version, but it's generic, not T-Mobile modified. That's the one we should be flashing over our T-Mobile phones, converting them to the U.S Generic version, not the international version. AFAIK the U.S version isn't running 11.2.4.x yet, so not sure why you would get an OTA prompt about 11.2.4.x unless you'd flashed (again, how did you do this?) the international version and not the U.S version.
Click to expand...
Click to collapse
flashing like always... unpack payload.bin and flash imgs files... but for some reason I have no service but sim card says tmo.... I've flashed back to stock global and problem still exist.. Also it says unable to find networks manually.. no service. this sucks 7series was so much easier..
ryantf420 said:
flashing like always... unpack payload.bin and flash imgs files... but for some reason I have no service but sim card says tmo.... I've flashed back to stock global and problem still exist.. Also it says unable to find networks manually.. no service. this sucks 7series was so much easier..
Click to expand...
Click to collapse
Using fastboot to flash the img files? There's liike 34 img files. (abl.img, aop.img, bluetooth.img, boot.img, cpucp.img, ..., ..., xbl.img, xbl_config.img). You flashed all 34?
If you're still having problems, I'm rooted and am on the stock 11.2.2.2.LE5ACB from T-Mobile. I can dd up certian partitions and provide them to you if you need. It may help you get back to stock.
glitchsys said:
Using fastboot to flash the img files? There's liike 34 img files. (abl.img, aop.img, bluetooth.img, boot.img, cpucp.img, ..., ..., xbl.img, xbl_config.img). You flashed all 34?
If you're still having problems, I'm rooted and am on the stock 11.2.2.2.LE5ACB from T-Mobile. I can dd up certian partitions and provide them to you if you need. It may help you get back to stock.
Click to expand...
Click to collapse
yes yes please that would help
Rooting is simple. Once your boot loader is unlocked head over to the thread on how to unlock the boot loader. He posted a patched boot IMG for T-Mobile. Flash it in fast boot restart open open magisk manager click direct install it will detect your boot IMG is patched it installs and reboot.
MurphSAN84 said:
How To: Unlock the T-Mobile Bootloader
Hello all, this is a quick and simple guide to unlocking your T-Mobile locked bootloader. Just a reminder: unlocking the bootloader will wipe your data. The instructions here will apply to all T-Mobile OnePlus devices. Unlock your SIM. Some...
forum.xda-developers.com
Click to expand...
Click to collapse
ryantf420 said:
flashing like always... unpack payload.bin and flash imgs files... but for some reason I have no service but sim card says tmo.... I've flashed back to stock global and problem still exist.. Also it says unable to find networks manually.. no service. this sucks 7series was so much easier..
Click to expand...
Click to collapse
Flash your tmobile modem over global.
Where to get tmo modem img?
ryantf420 said:
Where to get tmo modem img?
Click to expand...
Click to collapse
You were supposed to back your's up prior to conversion...
I have a WW version of ROG Phone 6. I have had it since mid-July.
Previously, I had ROG 2 but it died on me unexpectedly and I switched to Pixel 6, which was very underwhelming. I pre-ordered ROG 6 as soon as it became available.
I have not seen a concise guide to rooting ROG 6. I think it should be the same as ROG 2 but just in case, I read guide to rooting ROG 5.
Are the steps to rooting ROG 6 the same as ROG 5?
Asus ROG phone 5: unlock bootloader and root guide
Asus rog phone 5 guide note: you follow this guide on your own responsibility. also You should note that unlocking via the official Asus app will void warranty and blacklist the device for future otas. bootloader unlock: ! note that unlocking...
forum.xda-developers.com
Thank you!
I sure hope so. . . I cant find much material online but I'm going to try to just run this tool from asus https://rog.asus.com/phones/rog-phone-6-model/helpdesk_download/ and then flash magisk via recovery.
Sorry extract boot.img move it to phone, patch it with magisk and then run
Code:
fastboot flash boot magisk_patched.img
and that should do it. Although you may want/need to flash the official files first by running the flashall_AFT.cmd file.
Found this all on https://forum.xda-developers.com/t/...e-6-can-be-used-for-cn-ww-converting.4474383/ and https://forum.xda-developers.com/t/...-guide-you-should-read.4474241/#post-87255303
It worked for me without even needing to flash the full firmware (you'd have to, to switch versions though) let me know if you need help. the guides I linked might be overkill.
Just
1.) Fully update on phone.
2.) Install apk to unlock bootloader from my first link
3.) reboot to fastboot and run the command I gave above. (after extracting the boot.img from payload.bin and patching it, although the last link includes one prepatched that may work)
leathan said:
It worked for me without even needing to flash the full firmware (you'd have to, to switch versions though) let me know if you need help. the guides I linked might be overkill.
Just
1.) Fully update on phone.
2.) Install apk to unlock bootloader from my first link
3.) reboot to fastboot and run the command I gave above. (after extracting the boot.img from payload.bin and patching it, although the last link includes one prepatched that may work)
Click to expand...
Click to collapse
Thank you for replying.
I read the guide about "flashall_AFT". I think the guy needed to do that because he was converting CN to WW. So, I think you are right in that the guide might be overkill since my phone is WW.
Thank you for taking time to outline the steps. The steps you outlined seems the same as for ROG 5. Glad to know that ASUS is consistent on this.
ROG 6 is the first phone that I ever pre-ordered. Usually, I buy phones when there are already guides on rooting. So, I am a bit nervous on rooting ROG 6 since there is not dedicated and concise guide yet.
ausaras said:
Thank you for replying.
I read the guide about "flashall_AFT". I think the guy needed to do that because he was converting CN to WW. So, I think you are right in that the guide might be overkill since my phone is WW.
Thank you for taking time to outline the steps. The steps you outlined seems the same as for ROG 5. Glad to know that ASUS is consistent on this.
ROG 6 is the first phone that I ever pre-ordered. Usually, I buy phones when there are already guides on rooting. So, I am a bit nervous on rooting ROG 6 since there is not dedicated and concise guide yet.
Click to expand...
Click to collapse
Your good, just proceed as normal, I already got LSPosed, Zygisk+safteynet and all the goodies running. I see why you preordered this thing, its an absolute beast!! I am in love with it.
I wasn't even aware these phones existed but when I saw them and saw ASUS releases bootloader unlock publicly I instantly bought one as in general that's the main thing needed for rooting.
If you need any help It only took me about 15 minutes to root everything without using the guides at all as like you said it was pretty standard process. Like I said I extracted and patched the boot myself but just to potentially save time as I'm almost positive the patched image in the last link will work, and if it does not you can just reflash the one from the OTA.zip.
Good luck! (if you decide to root it will work fine)
leathan said:
Your good, just proceed as normal, I already got LSPosed, Zygisk+safteynet and all the goodies running. I see why you preordered this thing, its an absolute beast!! I am in love with it.
I wasn't even aware these phones existed but when I saw them and saw ASUS releases bootloader unlock publicly I instantly bought one as in general that's the main thing needed for rooting.
If you need any help It only took me about 15 minutes to root everything without using the guides at all as like you said it was pretty standard process. Like I said I extracted and patched the boot myself but just to potentially save time as I'm almost positive the patched image in the last link will work, and if it does not you can just reflash the one from the OTA.zip.
Good luck! (if you decide to root it will work fine)
Click to expand...
Click to collapse
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
ausaras said:
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
Click to expand...
Click to collapse
You should be done. I just fully updated and then rooted and set up my phone.
The firmware flash would have been to swap over to CN or WW. If you do that then yes you would re-factory reset + re flash stock boot.img. Then afterwards repeat the boot.img patch to obtain root + repeat setting up your safteynetfix + any other magisk modules.
ausaras said:
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
Click to expand...
Click to collapse
Hi, I am sorry the last answer I gave you was just wrong. I totally forgot when we root we wont get automatic OTA updates. Which for me is a really good thing anyway. But to get the OTA updates we need to download the firmware files from ASUS website. The same place we downloaded the unlock app but its under firmware. Download every WW firmware and put them one by one in order from oldest to newest on the /sdcard and boot up and it will detect an update. I'm pretty sure we cannot just skip to the latest update like we can with custom rom otas so I am going in order.
I left root, and when done updating will again patch the boot.img and flash it over.
Over the weekend I helped a guy root and set up safteynet and if it helps others I might just write up a tutorial.
Cheers!
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strage (or are least I think It strage):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
i need fastboot driver for win 64
Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route
can anyone provide the patched boot image to have root? Tried looking and asking in other areas but no luck. Or is there a way to patch a bot image that contains root already?