Develop Bugs

Understanding the correct KDZ file, help!

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.

Guide: How to upgrade/downgrade/restore official firmware on your V30.

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?

Moto G5+ XT1687 RETUS (U.S. Unlocked Retail) EASY LTE FIX FOR VERIZON USERS IMEI 0 !!

Hello all,
Follow my guide at your own risk. Read everything SUPER carefully to fix your Verizon LTE network connectivity on your US Retail unlocked Motorola G5 Plus.
I am here to save you all from flashing your phone countless times to try to bring back LTE with no EFS backup and no persist backup.
Here is a guide for XT1687 U.S. version of Moto G5+ (potter) that brings back Verizon LTE on STOCK Firmware/Rom and gives you OTA updates after downgrading from custom 8.1 Oreo roms.
I have not been able to relock bootloader, but that is okay. I am on stock firmware with OTA updates working and LTE working again.
Here is what I did:
I went ahead and flashed POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml to bring my phone back to stock from OMNI Rom 8.1 Oreo custom rom.
Obviously there is a bug that makes your IMEI 0 and loses all network connectivity after you flash back to stock from Oreo 8.1 64 bit roms on this phone.
1) Download the STOCK firmware/rom for XT1687 I used and extract the files: POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2.) Install ADB
https://forum.xda-developers.com/showthread.php?t=2588979
3)Extract the firmware to a folder using 7zip or right-click and extract all to folder in windows, then
4.) boot into your Moto G5+ bootloader by holding: Volume Down + Power button
Open a command prompt, copy and paste the following commands after installing ADB & Fastboot, make sure you launch command prompt or change directory to the same directory as the extracted rom files (cd C:/rom files):
You can type in CMD: fastboot devices to see if your device serial number shows up and you are ready to flash, make sure you are in bootloader mode first.
Paste the following commands in cmd prompt:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
Boot into your new stock rom now and use WIFI to update OTAs:
Make sure USB debugging is enabled > goto settings > click on build number 5 times then go back and goto developer options > usb debugging checked on
Your network connectivity will still be broken until we patch persist file but continue through the whole bootup for stock rom, set it up from new, and install all the OTA updates available through WIFI first.
5.) Install OTA updates over WIFI even though your network connectivity still doesn't work yet. Your IMEI will be 0 and you will have no network access.
Install all OTA updates with WIFI until your phone is on Build number: NPNS25.137-93-10, there is no firmware file to download this build, so it must be updated through OTA on wifi (all OTAs together should be ~300-500mb total).
6.)Download TWRP 3.2.1.0 and flash it using the following command: fastboot flash recovery twrp-3.2.1-0-potter.img:
https://dl.twrp.me/potter/twrp-3.2.1-0-potter.img.html
7.) Go into TWRP > backup > check EFS so it creates a folder in your phone storage TWRP folder, and then copy it into to a folder on your computer for future backups.
8.) Download Persist file linked here and boot phone in bootloader mode, use PC to copy persist file into TWRP folder > Newly created EFS backup folder > Persist file in your phone storage:
Code:
[url="https://nofile.io/f/RuxbqZAQayH/persist.ext4.win"]https://nofile.io/f/RuxbqZAQayH/persist.ext4.win[/url]
9.) TWRP > restore > check EFS backup folder you made earlier with your new persist file in it (should be 193kb for persist file). > restore the backup for EFS & Persist > reboot phone once its done.
10.) Ta-dah! The Verizon LTE network signal should be instantly back after you rebooted your phone into android OS.
Let me know if it worked for you on other versions as well. Everything is at your own risk. It worked for me and I just flashed it today 06/20/2018.
Also, files are from other devs on XDA, just made the guide to highlight the process steps that worked for me.
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

vwfan511 said:
Hello all,
Follow my guide at your own risk. Read everything SUPER carefully to fix your Verizon LTE network connectivity on your US Retail unlocked Motorola G5 Plus.
I am here to save you all from flashing your phone countless times to try to bring back LTE with no EFS backup and no persist backup.
Here is a guide for XT1687 U.S. version of Moto G5+ (potter) that brings back Verizon LTE on STOCK Firmware/Rom and gives you OTA updates after downgrading from custom 8.1 Oreo roms.
I have not been able to relock bootloader, but that is okay. I am on stock firmware with OTA updates working and LTE working again.
........
5.) Install OTA updates over WIFI even though your network connectivity still doesn't work yet. Your IMEI will be 0 and you will have no network access.
Install all OTA updates with WIFI until your phone is on Build number: NPNS25.137-93-10, there is no firmware file to download this build, so it must be updated through OTA on wifi (all OTAs together should be ~300-500mb total).
Click to expand...
Click to collapse
Nice guide, just a little correction: There is in fact a fastboot flashable NPNS25.137-93-10 stock firmware, here's a mirror, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud (the one where customer service get the firmware) but not everyone was able to download it from there.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
Nice guide, just a little correction: There is in fact a fastboot flashable NPNS25.137-93-10 stock firmware, here's a mirror, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud (the one where customer service get the firmware) but not everyone was able to download it from there.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
thanks but the link is dead there, know anywhere else to get it? and there the same for ATT and verizon right?

vonwap said:
thanks but the link is dead there, know anywhere else to get it? and there the same for ATT and verizon right?
Click to expand...
Click to collapse
Hmm, I've just tried the link and it works - I'm downloading the NPNS25.137-93-10 stock ROM as I write this from that provided Google Drive link.
As for the AT&T or Verizon versions, I'm not sure (though I think that retus devices on Verizon may have NPNS25.137-93-10, someone with a US device would be better suited to comment). Also, if I recall, devices on Verizon were on a different update path, from NPN25.137-33 to NPN25.137-35 (March 2017 security patch), then to NPN25.137.43-5 (May 2017 security patch), then to NPN25.137-83 (Aug 2017 security patch) before NPN25.137-93 (Nov 2017 security patch), then you should also get NPNS25.137-93-4 (Jan 2018 security patch), NPNS25.137-93-8 (March 2018 security patch), then NPNS25.137-93-10 (April 2018 security patch).
I would also caution against downgrading to NPNS25-137-33-5 (May 2017 security patch), as described in the guide, if your stock firmware was updated to a version newer than the May 2017 security patch. The reason being that if you have a device with a newer stock firmware previously flashed to it, downgrading to the May 2017 firmware may go okay, but you run the risk of hard bricking your device (as installing old OTA updates overwrites your bootloader, which is still present from the newer stock firmware). If your device was previously on the May 2017 stock security patch or older, you may not risk a hard brick but downgrading comes with risks.
Thus, it's probably best to attempt to flash NPNS25.137-93-10 for EU, US and Asia devices or NPNS25.137-92-10 for Brazil and Indian devices to avoid a downgrade.

vonwap said:
thanks but the link is dead there, know anywhere else to get it? and there the same for ATT and verizon right?
Click to expand...
Click to collapse
The link should be working as you see above in the post of @echo92 who has also answered your question as good as I could, maybe better.
I'm also not sure about the firmware path. 33-5 was May security patch here too but as you can see on the screenshot below August 2017 security patch was 33-11, at least here in Europe.
I'm pretty sure that there's no difference in the latest Verizon or AT&T firmwares but as @echo92 said, maybe a US user knows more about that (if you want to be 100% sure about that).
Imo if you go with the latest 93-10 (April security patch) firmware you should be on the safe side as a US user. Firmwares ending on 92-x are for India,Brasil and Asia Pacific, they should work but you won't receive any OTA updates as the updates pushed in the US an Europe search for 93-x firmwares.
Try the link again, maybe in a different browser.
If you can't download it at all I will mirror it on another hoster. Just send me a PM.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
The link should be working as you see above in the post of @echo92 who has also answered your question as good as I could, maybe better.
I'm also not sure about the firmware path. 33-5 was May security patch here too but as you can see on the screenshot below August 2017 security patch was 33-11, at least here in Europe.
I'm pretty sure that there's no difference in the latest Verizon or AT&T firmwares but as @echo92 said, maybe a US user knows more about that (if you want to be 100% sure about that).
Imo if you go with the latest 93-10 (April security patch) firmware you should be on the safe side as a US user. Firmwares ending on 92-x are for India,Brasil and Asia Pacific, they should work but you won't receive any OTA updates as the updates pushed in the US an Europe search for 93-x firmwares.
Try the link again, maybe in a different browser.
If you can't download it at all I will mirror it on another hoster. Just send me a PM.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
thanks worked with firefox, Ima try and get my VoLTe back on x1687? flashed to pixle 4g works but just left b/c scared to mess it up again. backed up my efs though. what is the persist ?

Wolfcity said:
The link should be working as you see above in the post of @echo92 who has also answered your question as good as I could, maybe better.
I'm also not sure about the firmware path. 33-5 was May security patch here too but as you can see on the screenshot below August 2017 security patch was 33-11, at least here in Europe.
I'm pretty sure that there's no difference in the latest Verizon or AT&T firmwares but as @echo92 said, maybe a US user knows more about that (if you want to be 100% sure about that).
Imo if you go with the latest 93-10 (April security patch) firmware you should be on the safe side as a US user. Firmwares ending on 92-x are for India,Brasil and Asia Pacific, they should work but you won't receive any OTA updates as the updates pushed in the US an Europe search for 93-x firmwares.
Try the link again, maybe in a different browser.
If you can't download it at all I will mirror it on another hoster. Just send me a PM.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Confusingly, the US series of firmwares seemed to be on different update paths until recently, when Motorola wisely appeared to unify them. The US equivalent of the 33-11 Aug 2017 update for EU/Brazil (and India?), as you posted, was NPN25.137-83, which was a follow on from either NPNS25.137-33-5 (May 2017) or NPNS25.137-35-5 or NPN25.137.43-5 (depending on which US network you were on). Needless to say, it got messy with regards to firmware updates...
But yes, I concur with you that the NPNS25.137-93-10 firmware should be a safe bet (especially as it's currently the latest firmware we have available anyway).

vonwap said:
thanks worked with firefox, Ima try and get my VoLTe back on x1687? flashed to pixle 4g works but just left b/c scared to mess it up again. backed up my efs though. what is the persist ?
Click to expand...
Click to collapse
It's a part of the nandroid backup.
persist.img is "persist" which contains data which shouldn't be changed after the device shipped, for example: calibration data of chips(wifi, bt, camera, etc.), certificates and other security related files. I heard it should contain the IMEI too but I'm not sure about that. You can't back it up with the official TWRP but with some unofficial versions, take a look here: https://forum.xda-developers.com/g5-plus/how-to/psa-efs-persist-t3807240
There are persist files uploaded here on XDA but it's a very hacky way as you have to use a file from the Moto G4 with side effects like yellowish photos.
Check the related threads.
Sent from my Moto G5 Plus using XDA Labs

Hmm sort of worried b/c im on att not sure if it makes a difference. Ill try and report back.

Wolfcity said:
Imo if you go with the latest 93-10 (April security patch) firmware you should be on the safe side as a US user. Firmwares ending on 92-x are for India,Brasil and Asia Pacific
Click to expand...
Click to collapse
Just a correction to the above, Asia Pacific (retapac) uses the 93 series as well.

NZedPred said:
Just a correction to the above, Asia Pacific (retapac) uses the 93 series as well.
Click to expand...
Click to collapse
Ok, thx for the info. So the 92-x firmware is only for India and Brazil.
Sent from my Moto G5 Plus using XDA Labs

Dont use if on any other carrier than verizon
Don't use this if you are not on verizon, I flashed this thinking it would fix some issues I was having with camera on my XT1687 and cricket wireless but now my imei is 0 and unrecoverable. If some on has a presist file and using cricket or att please share so I can see if that will help get LTE and IMEI back.

What firmware rom did you flash?
Did you follow guide and flash persist in TWRP that I linked to? Are you coming from custom Oreo rom?
When you flash back to stock from Oreo roms you will automatically lose IMEI and network connectivity.
Persist file is linked in first post :good::
Code:
https://www23.zippyshare.com/v/13MfpRhg/file.html
TWRP recovery needs to be flashed again after you flash the stock firmware.
You need to make an EFS backup in TWRP Recovery to create the EFS folder in your phone storage, after you finish flashing stock rom.
The persist.img backup needs to be restored in TWRP after you place it in your newly created EFS folder in your TWRP folder on phone storage.
Restore persist.img in TWRP after flashing stock firmware, you should not be flashing firmware only. Persist.img is what gives you your LTE network signal and IMEI back.
Let me know if you have further issues.

vwfan511 said:
Did you follow guide and flash persist in TWRP that I linked to? Are you coming from custom Oreo rom?
When you flash back to stock from Oreo roms you will automatically lose IMEI and network connectivity.
Persist file is linked in first post :good::
Code:
https://www23.zippyshare.com/v/13MfpRhg/file.html
TWRP recovery needs to be flashed again after you flash the stock firmware.
You need to make an EFS backup in TWRP Recovery to create the EFS folder in your phone storage, after you finish flashing stock rom.
The persist.img backup needs to be restored in TWRP after you place it in your newly created EFS folder in your TWRP folder on phone storage.
Restore persist.img in TWRP after flashing stock firmware, you should not be flashing firmware only. Persist.img is what gives you your LTE network signal and IMEI back.
Let me know if you have further issues.
Click to expand...
Click to collapse
Yep flashed presist file in link along with efs after rolling back to the firmware version you recommend, even went back to the the one prior to that after losing IMEI. Whatever I did screwed me up big time. Was able to get 3G back on stock but still no IMEI number. Really not sure what changed or went differently this time compared to other times that I've followed similar steps with no problems but whatever it was has caused me to lose 4G and IMEI completely without being able to recover it by flashing Oreo ROMs. Ohhh well I'll be keeping my eye out on deals at best buy now lol.

Wolfcity said:
Nice guide, just a little correction: There is in fact a fastboot flashable NPNS25.137-93-10 stock firmware, here's a mirror, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud (the one where customer service get the firmware) but not everyone was able to download it from there.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
tuxattack80 said:
Yep flashed presist file in link along with efs after rolling back to the firmware version you recommend, even went back to the the one prior to that after losing IMEI. Whatever I did screwed me up big time. Was able to get 3G back on stock but still no IMEI number. Really not sure what changed or went differently this time compared to other times that I've followed similar steps with no problems but whatever it was has caused me to lose 4G and IMEI completely without being able to recover it by flashing Oreo ROMs. Ohhh well I'll be keeping my eye out on deals at best buy now lol.
Click to expand...
Click to collapse
Try flashing Omni rom.. when I lost mine it wasn't working on other Oreo roms and PixelExperience was forceclosing nonstop, couldn't even get it to boot.
Code:
[URL="http://dl.omnirom.org/potter/"]http://dl.omnirom.org/potter/[/URL]
. My IMEI and 3g came back on Omni, then went back to stock and flashed persist..
Also make sure your TWRP is fully updated to 3.2.1.0, wipe cache dalvik...etc

vwfan511 said:
Try flashing Omni rom.. when I lost mine it wasn't working on other Oreo roms and PixelExperience was forceclosing nonstop, couldn't even get it to boot.
Code:
[URL="http://dl.omnirom.org/potter/"]http://dl.omnirom.org/potter/[/URL]
. My IMEI and 3g came back on Omni, then went back to stock and flashed persist..
Also make sure your TWRP is fully updated to 3.2.1.0, wipe cache dalvik...etc
Click to expand...
Click to collapse
okay thanks i'll give it a shot

Does anyone have a different way to get the persist file. The little zippy thing wants to have me downloading other crap that i dont want??

this worked fine for me on att, coming from google pixle oreo with working efs, restored my efs and this persists,
but my bootloader still says "ID: bad key" not sure if it matters. should i relock my boot loader? or not worry

Archangel said:
Does anyone have a different way to get the persist file. The little zippy thing wants to have me downloading other crap that i dont want??
Click to expand...
Click to collapse
Here's a mirror link for you:
https://nofile.io/f/RuxbqZAQayH/persist.ext4.win
https://nofile.io/g/ZH3emEjoBxxnId89k5DfprKEpe4Ikpis5p85S8edrSibxiLtMzbfYNS0tAx9qE4Q/persist.ext4.win/
Click to expand...
Click to collapse
Reuploaded for you on a different mirror as zippyshare has ads/bs now.

vonwap said:
this worked fine for me on att, coming from google pixle oreo with working efs, restored my efs and this persists,
but my bootloader still says "ID: bad key" not sure if it matters. should i relock my boot loader? or not worry
Click to expand...
Click to collapse
Relocking bootloader may not be possible unless you're on the latest firmware, I haven't relocked mine yet.
I am waiting for official Oreo update to go ahead and try... you can try the relock commands with the latest OTA firmware file.. but I can't guarantee it will work.

[ROM/FW][STOCK]LG Joan H930DS OPEN ESA IND 20f 0517 FW TWRP-zip (incl. ROM and OP)

LG Joan H930DS OPEN ESA IND 20f 0517 ROM including new OP partition offering airtel VoLTE​
Hi!
This Rom is 100% Stock. Most recent TWRP should first be installed. Then you can install this Rom and have Oreo with working TWRP. It should be installed only when coming from a previous full original (kdz or flashable fw zip, possibly rooted) firmware for H930DS Plus.
This zip is created from the original KDZ (IND H930DS20F_00_OPEN_ESA_DS_OP_0517.kdz, this time resulting in the correct version number, because OP partition is included, which at the same time gives you VoLTE functionality for airtel. It contains almost the complete 20f firmware, but the partition table rewriting part and recovery image (beside five to eight other images) is removed. I changed the system.img, so you do not have to reinstall TWRP (recovery-from-boot.p deleted) when ROM once booted. I also changed the partition size of system.img, so the vendorized people can install this too without having problems because of a too small system partition.
This is a continuation of westwood24's idea and work, I've updated it to the newest fw version and edited it a bit. I followed his idea and made this for users who can not take OTA's because they have Custom Recovery / Root installed.
​
Features
Stock build made from official KDZ
Stock Build.prop
Unrooted
system.img modified to keep TWRP
System image size shrunk for being able to flash this on a smaller system partition, mainly caused by vendorizing
Removed dm-verity
Removed rctd (LG's root checker tool daemon)
Enabled opt-encrypt, it's your choice now if you want to encrypt your phone, it's no more forced. TWRP now is capable of decryption (both AOSP and stock) since a few versions
New version of OP partition included, pls see above
Installation
What you need
Unlocked Bootloader [How to do]
Working TWRP installed (should be installed already)[Link to newest unofficial TWRP]
When you need Root, Latest Magisk [Download]
The TWRP flashable zip file (MD5: visible on AFH, it's correct)
How to install
When you are still on Nougat,
you should start fresh: Reboot to recovery using button combo or reboot app (needs root; btw, Magisk offers this possibility too: Menu -> Modules -> three dot menu top right - Reboot to recovery)
Then flash this latest TWRP.img via image flashing function in TWRP, reboot to recovery again (for fully working new recovery) and do a backup, then copy this backup to your PC.
Then initiate a factory reset. Wipe your system partition too in TWRP advanced wiping menu, copy the 20f firmware zip to your SD and install it. Reboot and enjoy
From Oreo:
For clean install: Factory reset and wipe system
You can also keep your data by simply dirty flashing the zip. *Be aware that problems may occure, maybe you need to do a factory reset to start fresh*
Flash the 20f zip, then Magisk zip when you need root, then reboot to System = you're DONE
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no (in newest TWRP SU is disabled, and the option to install the TWRP app is disabled too.)​
Just give a thanks if you like the zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...

Am i the first one?:victory:

looks like you want to test? looks like too i send you the link

seadersn said:
looks like you want to test? looks like too i send you the link
Click to expand...
Click to collapse
Sure,but I have a question,can I flash other stock zips like V300l into my ls998?

this info needs to be given by another person, don't know this. i don't even know 100% if you can flash this one on your phone if it's not h930ds plus. am h930 eu open user :good:
better do not flash until you know if this works as this zip doesn't contain only system and boot, but bootloader, modem and other stuff too. not that you end up with a non working phone!

seadersn said:
this info needs to be given by another person, don't know this. i don't even know 100% if you can flash this one on your phone if it's not h930ds plus. am h930 eu open user :good:
better do not flash until you know if this works as this zip doesn't contain only system and boot, but bootloader, modem and other stuff too. not that you end up with a non working phone!
Click to expand...
Click to collapse
Ok,thanks

link.added, testing done

Libart said:
Sure,but I have a question,can I flash other stock zips like V300l into my ls998?
Click to expand...
Click to collapse
No. These "stock" zips are for people who have TWRP and want to update to newer stock firmware very easily. These are not conventional ROMs that any variant can flash. They are merely TWRP flashable versions of full image KDZ. If you live in India/Philippines/Indonesia and have an H930DS this "EAS" region firmware is for you. For instance it would (should) give you India Jio VoLTE with a Jio SIM card and is currently the newest firmware available for that region.
This "ROM" (really TWRP flashable KDZ) is probably compatible with Europe H930 phones as some have flashed other H930DS firmware onto H930 -- but they have slight bugs like showing phantom 2nd SIM card. However someone flashing this "ROM" over H930 should have very good reason for doing so, not just for fun.
But for you specifically, I wouldn't flash LS998 to any other variant other than North America, and even then you can't flash T-mobile H932. Do you have a reason you want V300l firmware?

thanks for these flashable versions, really helps a lot
I'm assuming this is for any V30+?
I've flashed this one for h930 before and it worked.

dave_id said:
thanks for these flashable versions, really helps a lot
I'm assuming this is for any V30+?
I've flashed this one for h930 before and it worked.
Click to expand...
Click to collapse
Theoretically, yes. But if you have specific carrier needs (like India does) having your specific region/country firmware helps. This was for the region (ESA) that includes India.
However, if you flashed H930 then this should also be OK for you...

ChazzMatt said:
No. These "stock" zips are for people who have TWRP and want to update to newer stock firmware very easily. These are not conventional ROMs that any variant can flash. They are merely TWRP flashable versions of full image KDZ. If you live in India/Philippines/Indonesia and have an H930DS this "EAS" region firmware is for you. For instance it would (should) give you India Jio VoLTE with a Jio SIM card and is currently the newest firmware available for that region.
This "ROM" (really TWRP flashable KDZ) is probably compatible with Europe H930 phones as some have flashed other H930DS firmware onto H930 -- but they have slight bugs like showing phantom 2nd SIM card. However someone flashing this "ROM" over H930 should have very good reason for doing so, not just for fun.
But for you specifically, I wouldn't flash LS998 to any other variant other than North America, and even then you can't flash T-mobile H932. Do you have a reason you want V300l firmware?
Click to expand...
Click to collapse
Because I think ls998 is lacks of some LG's applications such as LGmessage and I'm living without computer, but this is a small problem so you just ignore it

Libart said:
Because I think ls998 is lacks of some LG's applications such as LGmessage and I'm living without computer, but this is a small problem so you just ignore it
Click to expand...
Click to collapse
Then convert your Sprint LS98 to US998 via Frankenstein or some other carrier unlocked North American variant. You should NOT be flashing Sprint LS998 to any firmware outside of North America, especially a dual SIM H930DS firmware.

k, updated the op, new links available, and added a firmware only zip (with system and boot excluded, OP included for both zips).

Dirty flashed from v20b (v30+, hd930ds, Philippines) using the latest TWRP from the TWRP thread. Everything is working quite well. Also flashed updated driver from https://forum.xda-developers.com/lg...no-540-gpu-update-boost-gaming-t3844132/page3 and xposed if anyone is interested.
Will report if I encounter any bugs as I just flashed it literally jist about 10 mins ago lol.
Thanks so much OP. Would have been stuck at v20b if it weren't for this! Kind of uncomfortable using KDZs.
Edit:
Wait... It still shows up as v20b (see attachment - is that normal?)? I thought this is v20c? I'm confused... :silly:
Checked the downloaded zip and it's the correct one... On the other hand, checking the update center shows i have the latest software (asked me to update before flashing).

the build.prop thingy already caused me headaches, we don't know why it shows 20a, 10b or even 21c for different persons who installed this rom. security patch is the most recent available, so this rom installed succesfully, but the version numbering is a mysery in build.prop of this software is written 21c for example. it looks like it depends on the firmware version from which it was upgraded to this rom version. and it looks like there's something inside system which keeps the actual version numbering.
guess: maybe the system is configured in a way to use the before used version number because nothing else but security patch changed and the kdz creating ppl thought "hey, nothing beside security changed, no reason for a new version lettering, let's stay at the actual version number, no reason to raise it." i don't know but it works

seadersn said:
the build.prop thingy already caused me headaches, we don't know why it shows 20a, 10b or even 21c for different persons who installed this rom. security patch is the most recent available, so this rom installed succesfully, but the version numbering is a mysery in build.prop of this software is written 21c for example. it looks like it depends on the firmware version from which it was upgraded to this rom version. and it looks like there's something inside system which keeps the actual version numbering.
guess: maybe the system is configured in a way to use the before used version number because nothing else but security patch changed and the kdz creating ppl thought "hey, nothing beside security changed, no reason for a new version lettering, let's stay at the actual version number, no reason to raise it." i don't know but it works
Click to expand...
Click to collapse
Ok. Great.
I was just worried I made a mistake or something. I haven't experienced any issues so I'm happy with it.
(you also mentioned to give feedback about what version appears so I thought there was something I wasn't aware of). Thanks again! You made updating so much easier for me. :good:

FOR INDIA USERS
[email protected] said:
i just tried jio volte on my phone and it works
i flashed 21w eur firmware.... And jio works....to my surprise...i have attached few screenshots as proof.
Screenshot 1- you can see the jan security patch....
Screenshot 2- new aod features..for reference
Click to expand...
Click to collapse
chazzmatt said:
wow!
Lg must have added india jio volte to h930 eu firmware.
This also means you can have the dts 3d stereo, if you have root:
FULLY ENABLE DTS 3D STEREO (root needed)
https://forum.xda-developers.com/lg-v30/how-to/enable-dts-3d-stereo-lg-v30-variants-t3887139
Click to expand...
Click to collapse
chazzmatt said:
JIO VOLTE is supported on ESA region (India) H930DS firmware. The problem is you had to use ESA region, you couldn't use any other H939DS firmware or H930 ER firmware, if you wanted JIO VOLTE -- even though they were compatible in every other way. Jio users can't drop down to HSPA like other carriers -- they only have LTE.
Now apparently H930 firmware does support JIO VOLTE and also has the new DTS 3D framework. plus H930 firmware still gives H930DS dual sim card capability, and keeps the H930DS bands.
This is very big news.
And there's also H930 TWRP flashable zip for those who have TWRP... Thanks to @seadersn.
Click to expand...
Click to collapse
[email protected] said:
yes ....i am using dts surround sound too....
Click to expand...
Click to collapse
This won't show as "21W" for India users but WILL show current security patch, be updated firmware internally, and have DTS libs.

https://androidfilehost.com/?fid=1395089523397929907
20E fw zip with dts-x activated available updating first post soon :good: (edit: updated)

seadersn said:
https://androidfilehost.com/?fid=1395089523397929907
20E fw zip with dts-x activated available updating first post soon :good: (edit: updated)
Click to expand...
Click to collapse
tech_infinity said:
Here's a screenshot.
Click to expand...
Click to collapse
@tech_infinity confirms ESA 20e has February 2019 security patch. I knew with 0213 (February 13) build date, it would at least be January security patch but possibly February. It's February.

ChazzMatt said:
@tech_infinity confirms ESA 20e has February 2019 security patch. I knew with 0213 (February 13) build date, it would at least be January security patch but possibly February. It's February.
Click to expand...
Click to collapse
Dts activated???? So no need of root???????

Stock Frankenstein Post-July Oreo->TWRP (Also, fixing no sound issue)

I'd like to update to a more recent security version....
I bought my V30+ online from BREED (an Amazon reseller). The hardware model number, according to the phone, is LG-US998. According to LG (on their website), it's an LG V30+T (Sprint). I'm on AT&T. The phone works on AT&T just fine.
I called Sprint, and they have the IMEI in their system, no lost or stolen, but they won't unlock it.
I'm stuck on US99820e (September 1), and LG Bridge says "Cannot check the software version. Try again." (MTP, backup, everything else works). I've tried it on my Macbook, and on a Windows 10 machine. Neither option works, and both give the same error.
I called LG, and they couldn't find any way to connect to LG Bridge.
No OTA update available.
What are my options for updating here? The phone is not currently unlocked (checked this via ADB). Do I need to unlock to use LGUP and flash a later kdz file, or can I just flash it on top of what I have? I'm aware I'd need to unlock the bootloader, etc, in order to use TWRP. Or should I just wait?

Bought US998, found out it's former LS998 -- no updates
Former LS998 orH931 converted to US998 -- no updates
hellodmo said:
The hardware model number, according to the phone, is LG-US998. According to LG (on their website), it's an LG V30+T (Sprint). I'm on AT&T. The phone works on AT&T just fine.
I called Sprint, and they have the IMEI in their system, no lost or stolen, but they won't unlock it.
I'd like to update to a more recent security version....
I'm stuck on US99820e (September 1), and LG Bridge says "Cannot check the software version. Try again." (MTP, backup, everything else works). I've tried it on my Macbook, and on a Windows 10 machine. Neither option works, and both give the same error.
I called LG, and they couldn't find any way to connect to LG Bridge. No OTA update available.
What are my options for updating here? The phone is not currently unlocked (checked this via ADB). Do I need to unlock to use LGUP and flash a later kdz file, or can I just flash it on top of what I have? I'm aware I'd need to unlock the bootloader, etc, in order to use TWRP. Or should I just wait?
Click to expand...
Click to collapse
Many of the US998 found on eBay are actually former North America variants from other carriers -- most often from carrier locked Sprint LS998 and AT&T H931. Flashing to US998 firmware SIM card unlocks these phones and gives them fastboot flash commands. Here on XDA, we do this all the time, either for carrier unlock/updates and/or part of the WTF bootloader unlock and root process.
This North American variant conversion is called "Frankenstein" conversion. Your former LS998 is fully US998 and now has these bands:
http://www.lg.com/us/cell-phones/lg-US998-Unlocked-v30
US998
CDMA: 800 MHz CDMA
2G GSM: 850/900/1800/1900 MHz
3G UMTS (HSPA):850/900/1900/2100 MHz
4G LTE Bands: 1/2/3/4/5/7/12(17)/13/20/25/66
Many eBay dealers use the Frankenstein conversion because it's easier to sell carrier unlocked US998 phones than Sprint locked LS998 phones. Also, for AT&T H931 and Sprint LS988, those carriers only give updates to current customers via OTA; they do not publicly release KDZ. So, for non-customers with those phones, converting to US998 gives easy access to KDZ updates -- like posted in this forum. I've bought LS998 V30+ phones myself and immediately converted them to US998 via Frankenstein to use on AT&T.
UPDATE THE PHONE:
Just update via LGUP from the US998 KDZ thread. Takes 5 minutes and you can be on latest US998 KDZ.
Download the most recent KDZ from the US998 KDZ thread and use "Upgrade" option in LGUP. Use attached LGUP in post #1 of that thread. Installation instructions for LGUP are also in post #1 of that thread.
No need to unlock bootloader and install TWRP just for updating stock firmware. However, you can do that in the future if you want to add additional functionality. For instance, to fully enable DTS 3D stereo on the US998 you need root. To have the call recording feature, you need root. To enable all the LG lock screen weather animations you need root. To enable dual speaker mode, you need root. But just to update stock firmware you do not need root.

ChazzMatt said:
Update via LGUP from the US998 KDZ thread. Takes 5 minutes and you can be on US998 20G.
Download the KDZ and use "Upgrade" option in LGUP. Use attached LGUP in post #1 of that thread.
https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99820a040330-kdz-t3786337
No need to unlock bootloader and install TWRP just for updating stock firmware. However, you can do that in the future if you want to add additional functionality.
Click to expand...
Click to collapse
Okay, so bizarrely, I think I was trying that at the same time as you writing this....
I'm getting an odd SPC Code does not match when the progress is at about 4% :/ Any idea what that is?

hellodmo said:
Okay, so bizarrely, I think I was trying that at the same time as you writing this....
I'm getting an odd SPC Code does not match when the progress is at about 4% :/ Any idea what that is?
Click to expand...
Click to collapse
May need to reinstall drivers, may need to go into Download mode manually before opening LGUP. May need to change ports.
Look at the troubleshooting tips in this post:
CONVERTING ANY NORTH AMERICA V30/V30+ TO US998 OREO
Your phone had already been Frankenstein converted by the eBay dealer, but the troubleshooting tips still apply for any LGUP updates.
Sent via open market LG US998 V30/V30+

I almost always have a heart attack and think my old Windows computer is going to pick the upgrade moment to crap out on me and it never does. I imagine myself out $400 for a nice new phone, and crying about it to my wife, who would certainly be rolling her eyes, and wondering why I don't just stick with iPhone because it's easier.
None of that happened. Except for me inadvertently choosing "refurb" mode instead of upgrade mode, and thus wiping all my user data and having to get it from the cloud all over again, everything looks like it went swimmingly well and I'm on the latest update.
Thanks!
(Just to confirm... I DID hit the refurb button, right? Even in download mode, hitting upgrade wouldn't have cleared my data, correct? No big deal either way. I'm used to setting up my phone again and again, but I just wanted to confirm.)

hellodmo said:
I almost always have a heart attack and think my old Windows computer is going to pick the upgrade moment to crap out on me and it never does. I imagine myself out $400 for a nice new phone, and crying about it to my wife, who would certainly be rolling her eyes, and wondering why I don't just stick with iPhone because it's easier.
None of that happened. Except for me inadvertently choosing "refurb" mode instead of upgrade mode, and thus wiping all my user data and having to get it from the cloud all over again, everything looks like it went swimmingly well and I'm on the latest update.
Thanks!
(Just to confirm... I DID hit the refurb button, right? Even in download mode, hitting upgrade wouldn't have cleared my data, correct? No big deal either way. I'm used to setting up my phone again and again, but I just wanted to confirm.)
Click to expand...
Click to collapse
Refurb is the default option in LGUP -- so you probably did not choose anything. If you have chosen upgrade, that would have kept your data. About a month ago I was updating my wife's phone while doing three other things at once... It quickly and completely wiped the entire phone because "refurbish" was chosen. ARghhhh. I spent the next three hours setting up her phone again. Normally I'm more careful.
Refurb can be useful in some situations, but in your instance (and my recent one) "upgrade" is what was wanted. This screenshot below is from months ago, but still shows the two "refurbish" and "upgrade" options.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Still you now have your US998 updated, and you know what to do in the future.

And then I woke up this morning and installed TWRP and Magisk to get Dolby.
I'm hopeless.

hellodmo said:
And then I woke up this morning and installed TWRP and Magisk to get Dolby.
I'm hopeless.
Click to expand...
Click to collapse
Which means you after refurb-upgrading to US998 20G last night and setting up your phone again... Then this morning you temporarily downgraded back to US998 20a or 20b, unlocked the bootloader using the WTF instructions, installed TWRP and Magisk. And by now you've probably flashed the @JohnFawkes TWRP-flashable US998 20G zip file to upgrade back to current firmware, while having additional functionality with root -- and actually being the admin of your phone.
(The only thing you didn't have to do was the Frankenstein from Sprint LS998 firmware to US998 in the first place. The dealer did that for you.)
Still, I'm actually impressed you did all that in so little time from knowing basically nothing about this phone last night. Kudos. I like success stories like that.

ChazzMatt said:
Which means you temporarily downgraded back to US998 20a or 20b, unlocked the bootloader using the WTF instructions, installed TWRP and Magisk. And by now you've probably flashed the @JohnFawkes TWRP-flashable US998 20G zip file to upgrade back to current firmware, while having additional functionality (and actually being the admin of your phone).
The only thing you didn't have to do was the Frankenstein from Sprint LS998 firmware to US998 in the first place. The dealer did that for you.
Still, I'm actually impressed you did all that in so little time from knowing basically nothing about this phone last night. Kudos. I like success stories like that.
Click to expand...
Click to collapse
I'm a software dev myself (NodeJS/AngularJS), so computers and stuff aren't foreign to me. I'm just cautious by nature when it comes to this stuff.
Full sequence (for posterity, or anyone else looking to do the same)
Last night: (using patched LGUP) Set to download mode and upgrade to 20G.
(This morning): Download Nougat kdz, Oreo Pre-July kdz, new_unlock.bin, encryption de-verifier, rctd disabler, Magisk 18, TWRP, TWRP-enabled 20g zip.
Set to download and downgrade to Nougat (refurb mode) (per your instructions)
Factory reset the phone (to be safe)
Set to download and upgrade to Oreo "a" (upgrade mode).
Partial phone setup - enable USB debugging and Unlocking bootloader.
Connect phone to Mac (More comfortable there)
adb reboot bootloader
fastboot flash unlock new_unlock.bin
fastboot reboot
(Setup steps to reenable USB debugging)
adb reboot bootloader
fastboot getvar unlocked (verified unlocked)
fastboot flash recovery TWRP.img.
fastboot boot TWRP.img.
Swipe to allow modifications.
Backed up the system to SD Card.
Wipe Data -> Factory Reset.
Wipe Data - Format Data (this failed initially)
Reboot to recovery.
Redo step 18, this time with success.
Install magisk.
Install encryption disabler.
Install root check disabler.
Reboot (I'm honestly not sure if the last three steps are necessary)
Reboot to bootloader (force phone to "factory reset" menu, and click yes through it... that got me to TWRP.)
Flash 20g.zip.
Flash Magisk.
Reboot.
Setup for real.
Download AnxiousOS Magisk module and install (within phone).
Currently waiting for the phone to restore apps, etc, then I'll reboot.

hellodmo said:
I'm a software dev myself (NodeJS/AngularJS), so computers and stuff aren't foreign to me. I'm just cautious by nature when it comes to this stuff.
Full sequence (for posterity, or anyone else looking to do the same)
Last night: (using patched LGUP) Set to download mode and upgrade to 20G.
(This morning): Download Nougat kdz, Oreo Pre-July kdz, new_unlock.bin, encryption de-verifier, rctd disabler, Magisk 18, TWRP, TWRP-enabled 20g zip.
Set to download and downgrade to Nougat (refurb mode) (per your instructions)
Factory reset the phone (to be safe)
Set to download and upgrade to Oreo "a" (upgrade mode).
Partial phone setup - enable USB debugging and Unlocking bootloader.
Connect phone to Mac (More comfortable there)
adb reboot bootloader
fastboot flash unlock new_unlock.bin
fastboot reboot
(Setup steps to reenable USB debugging)
adb reboot bootloader
fastboot getvar unlocked (verified unlocked)
fastboot flash recovery TWRP.img.
fastboot boot TWRP.img.
Swipe to allow modifications.
Backed up the system to SD Card.
Wipe Data -> Factory Reset.
Wipe Data - Format Data (this failed initially)
Reboot to recovery.
Redo step 18, this time with success.
Install magisk.
Install encryption disabler.
Install root check disabler.
Reboot (I'm honestly not sure if the last three steps are necessary)
Reboot to bootloader (force phone to "factory reset" menu, and click yes through it... that got me to TWRP.)
Flash 20g.zip.
Flash Magisk.
Reboot.
Setup for real.
Download AnxiousOS Magisk module and install (within phone).
Currently waiting for the phone to restore apps, etc, then I'll reboot.
Click to expand...
Click to collapse
Great.
The only thing you personally didn't have to do -- since you were already on US998 Oreo -- was downgrade back to Nougat. You just needed to downgrade from US998 20G back to pre-July US998 Oreo (20a or 20b).
For people converting from LS998 to US998, they HAVE to do the US998 Nougat first before going to US998 Oreo -- they can't just jump from LS998 firmware to US998 Pre-July Oreo; LG put some check in there that prevents that. So, going to US998 Nougat bypasses that, then they can upgrade to US998 Pre-July Oreo. Still, those extra steps I'm sure gave you more practice with LGUP.
But your checklist is perfect for those having to convert from LS998 to US998 and then going through the bootloader unlock/TWRP/root process.

ChazzMatt said:
Great.
The only thing you personally didn't have to do -- since you were already on US998 Oreo -- was downgrade back to Nougat. You just needed to downgrade from US998 20G back to pre-July US998 Oreo (20a or 20b).
For people converting from LS998 to US998, they HAVE to do the US998 Nougat first before going to US998 Oreo -- they can't just jump from LS998 firmware to US998 Pre-July Oreo; LG put some check in there that prevents that. So, going to US998 Nougat bypasses that, then they can upgrade to US998 Pre-July Oreo. Still, those extra steps I'm sure gave you more practice with LGUP.
But your checklist is perfect for those having to convert from LS998 to US998 and then going through the bootloader unlock/TWRP/root process.
Click to expand...
Click to collapse
Hrm... not so fast... I have NO sound for media (ringtones work. Spotify and Music don't)... gonna have to look into that... any ideas?

hellodmo said:
Hrm... not so fast... I have NO sound for media (ringtones work. Spotify and Music don't)... gonna have to look into that... any ideas?
Click to expand...
Click to collapse
Try flashing just 20G TWRP flashable zip and reflash Magisk. Set up, see if you have audio.
It not, then flash 20F TWRP flashable zip and reflash Magisk. Set up see if you have audio.
Hold off on Anxious module until you verify audio.
Sent via open market LG US998 V30/V30+

Hmmm....
I noticed that the link for the 20G TWRP is actually for the H930, could that be the issue? I have a US998.... (previously LS998)
https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99820a040330-kdz-t3786337

I'm getting some errors in the logs.... something about denied (find) vendor.lge.hardware.configstore.... That sounds iffy.
Also, audio_hw_primary start_output_stream: pcm_prepare returned -1.
Here's the iffiest:
msm8974_platform platform_check_backends_match: invalid_snd_device =
Uh oh.

hellodmo said:
Hmmm....
I noticed that the link for the 20G TWRP is actually for the H930, could that be the issue? I have a US998.... (previously LS998)
https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99820a040330-kdz-t3786337
Click to expand...
Click to collapse
No, it's not for h930. That's an issue with the hosting site which categorizes all V30 as H930, due to the first developer who registered his H930 V30.

Reinstalled 20G, no-go.
Downgraded to 20F, worked fine.
Upgraded back to 20G, worked fine.
Looks like newcomers may have some issues, but those who went through 20F will be fine.
I have the logs for @JohnFawkes if he wants them.

hellodmo said:
I'm getting some errors in the logs.... something about denied (find) vendor.lge.hardware.configstore.... That sounds iffy.
Also, audio_hw_primary start_output_stream: pcm_prepare returned -1.
Here's the iffiest:
msm8974_platform platform_check_backends_match: invalid_snd_device =
Uh oh.
Click to expand...
Click to collapse
@JohnFawkes
---------- Post added at 06:00 PM ---------- Previous post was at 05:57 PM ----------
hellodmo said:
I'm getting some errors in the logs.... something about denied (find) vendor.lge.hardware.configstore.... That sounds iffy.
Also, audio_hw_primary start_output_stream: pcm_prepare returned -1.
Here's the iffiest:
msm8974_platform platform_check_backends_match: invalid_snd_device =
Uh oh.
Click to expand...
Click to collapse
This is after reflashing just 20G zip and Magisk?
Never mind, I see answer above.
---------- Post added at 06:25 PM ---------- Previous post was at 06:00 PM ----------
hellodmo said:
Reinstalled 20G, no-go.
Downgraded to 20F, worked fine.
Upgraded back to 20G, worked fine.
Looks like newcomers may have some issues, but those who went through 20F will be fine.
I have the logs for @JohnFawkes if he wants them.
Click to expand...
Click to collapse
You can now flash the Anxious Magisk module if you wish. Of course, make TWRP backup...

hellodmo said:
Reinstalled 20G, no-go.
Downgraded to 20F, worked fine.
Upgraded back to 20G, worked fine.
Looks like newcomers may have some issues, but those who went through 20F will be fine.
I have the logs for @JohnFawkes if he wants them.
Click to expand...
Click to collapse
There isn't anything I can do about the no sound thing. Since you bought a phone that was already converted it is most likely a refurb. It seems like other users who had this issue (its mentioned in the us998 thread) were coming from aosp and had no sound. It's very likely your device was on aosp at one time. The flashable zip is just the kdz converted into a flashable zip. If its not giving sound its nothing I can fix. Its on lg unfortunately.

After installing Magisk and AnxiousV30, it all seems to work, with the sole exception of the dual-speaker mod (I'm not sure what to expect here... I try playing music through the speaker, and I'm kinda expecting it to come through the earpiece and the speaker at the same time). In any case, all seems well.

hellodmo said:
After installing Magisk and AnxiousV30, it all seems to work, with the sole exception of the dual-speaker mod (I'm not sure what to expect here... I try playing music through the speaker, and I'm kinda expecting it to come through the earpiece and the speaker at the same time). In any case, all seems well.
Click to expand...
Click to collapse
Yeah, with dual speaker it does come through the earpiece also, but can't be as loud as the bottom speaker. Now when watching videos for instance, helps to have some audio directed towards your face.
---------- Post added at 08:44 PM ---------- Previous post was at 08:39 PM ----------
JohnFawkes said:
There isn't anything I can do about the no sound thing. Since you bought a phone that was already converted it is most likely a refurb. It seems like other users who had this issue (its mentioned in the us998 thread) were coming from aosp and had no sound. It's very likely your device was on aosp at one time. The flashable zip is just the kdz converted into a flashable zip. If its not giving sound its nothing I can fix. Its on lg unfortunately.
Click to expand...
Click to collapse
Yeah, but he flashed full KDZ in refurbished mode in LGUP at least twice before even unlocking his bootloader.
Issue is fixed now by flashing 20F, then 20G. Strange...
Maybe the issue stemmed from trying to flash the Anxious Magisk module before setting up the phone? It changes some stuff with audio. Maybe the phone was confused.