Hi all, I recently just bought a V30 so I'm all very new to this. I have the US998 model and from what I've gathered so far in this forum is that the US998 model seems to play a very significant role here. Seems like owners of H931/H933 models have to convert their devices into the US998 model in order to install custom Oreo ROMs. But having said that, I haven't seen any ROMs with links to a US998 version, just the H930 and H932. I'm sort of confused, so does that mean owners of the US998 model can flash any ROM version they want?
NeonHD said:
Hi all, I recently just bought a V30 so I'm all very new to this. I have the US998 model and from what I've gathered so far in this forum is that the US998 model seems to play a very significant role here. Seems like owners of H931/H933 models have to convert their devices into the US998 model in order to install custom Oreo ROMs. But having said that, I haven't seen any ROMs with links to a US998 version, just the H930 and H932. I'm sort of confused, so does that mean owners of the US998 model can flash any ROM version they want?
Click to expand...
Click to collapse
@ChazzMatt created this thread for just that reason. If you have a US998, follow it below:
https://forum.xda-developers.com/showpost.php?p=76584629&postcount=193
NeonHD said:
Hi all, I recently just bought a V30 so I'm all very new to this. I have the US998 model and from what I've gathered so far in this forum is that the US998 model seems to play a very significant role here. Seems like owners of H931/H933 models have to convert their devices into the US998 model in order to install custom Oreo ROMs. But having said that, I haven't seen any ROMs with links to a US998 version, just the H930 and H932. I'm sort of confused, so does that mean owners of the US998 model can flash any ROM version they want?
Click to expand...
Click to collapse
TLDR:
ALL AOSP/Lineage ROMs (unless specifically H932-only) are compatible with ALL V30/V30+/V30S.
Complete answer:
You've asked a complicated question.
* For the discussion below we are mostly talking about North America variants only.
* Some of this below does not apply to H930/H930DS/H930D/H930G (the 930's).
* Some of this below is also not just to answer this question but for other people who want to buy this fantastic phone.
1) For any V30/V30+/V30S, you have to have fastboot flash commands and have a specific date range of stock Oreo firmware to use the WTF exploit to unlock the bootloader and root. (This does not apply to the T-mobile H932. It has its own root method, has different RSA encryption and is an island to itself. My opinion is to stay away from H932, unless you are a T-mobile customer and specifically want H932 for the T-mobile LTE band 71. I welcome all H932 development, of course and am thankful we finally have root, etc for it. But no need to go out and buy it if you're not a T-mobile customer who wants LTE band 71. Other T-mobile customers have US998 -- original or converted from like LS998 -- and use it on T-mobile.)
Of the North American variants, only the US998 has fastboot flash commands AND has firmware which is totally compatible with all other North America variants, EXCEPT for H932. So, you at least temporarily convert to US998 to unlock bootloader, root. You can stay on US998 if you like, or you can flash back to another North America variant firmware at that point and still retain unlocked bootloader and TWRP (with ability to root). US998 is the official carrier unlocked North American variant, so works with most North American carries. However, some carriers only give some service options on their own firmware; Wi-Fi calling, etc. Your choice whether to stay on US998 firmware or flash to another carrier firmware. I'm on AT&T, but I am still running US998 rooted stock firmware.
2) Once bootloader unlocked and rooted, you can also install custom AOSP ROMs -- but some are easier than others. Former VS998, LS9998, AS998 and original US998 have no problems. AT&T H931 and Canada H933 have issues getting ASOP ROMs to boot up; however there's a complicated workaround was developed where you re-flash different firmware a few times for it to work. You can now run AOSP ROMs on H931/H933, but unless you already have those, there's no reason to specifically buy them if your desire is to run AOSP ROMs. T-mobile H932 has different RSA encryption and needs separate ROMs for that model.
3) The first dev to make several AOSP/Lineage ROMs registered his H930 on AFH server website (which a lot of XDA devs use, and which I use as they give free server space for development), and now AFH thinks ALL V30 are "H930". Even VS996, H933, US998 V30 KDZ which I upload to H930 are categorized by AFH as "H930" when it's not. Confuses people when they click on a link, goes to AFH website and says "H930". ALL AOSP/Lineage ROMs (unless specifically H932-only) are compatible with ALL V30/V30+/V30S.
4) For North American variants, you cannot cross flash H930 or H930DS full stock firmware "ROMs". Stock firmware ROMs are just stock KDZ in TWRP-flashable format. Do NOT try to flash a North American variant to a stock firmware H930/H930DS ROM. You can only flash other North American stock firmware (except for H932) and AOSP/Lineage ROMs. The ONE exception to that is the Boombox ROM -- which is BASED on H930 stock firmware, but IS compatible with all V30/V30+/V30S (except for T-mobile H932).
CONCLUSION
Anyway, that's why you see "H930" AOSP ROMS (they are not really just for H930) as well as H932 ROMs (and they ARE only for H932). The best North America variant phones to buy for AOSP/Lineage ROMS are LS998, VS996, AS998, and original US998. H931 and H933 can flash AOSP/Lineage ROMs but after bootloader unlock and root, you have to then go through another flashing procedure to make it work. T-mobile H932 has different RSA encryption and devs have to release separate ROMs for them.
After you bootloader unlock and root, I suggest trying out rooted stock firmware for awhile. Everything works, and on US998 20F we even now have DTS 3D stereo. There are Magisk mods you can flash which give even more capabilities. The only reason I suggest that is because it helps to have a baseline comparison. Then try the AOSP/Linage ROMs. That way if something doesn't work right, you know whether it's the ROM or the phone.
ChazzMatt said:
TLDR:
ALL AOSP/Lineage ROMs (unless specifically H932-only) are compatible with ALL V30/V30+/V30S.
Complete answer:
You've asked a complicated question.
* For the discussion below we are mostly talking about North America variants only.
* Some of this below does not apply to H930/H930DS/H930D/H930G (the 930's).
* Some of this below is also not just to answer this question but for other people who want to buy this fantastic phone.
1) For any V30/V30+/V30S, you have to have fastboot flash commands and have a specific date range of stock Oreo firmware to use the WTF exploit to unlock the bootloader and root. (This does not apply to the T-mobile H932. It has its own root method, has different RSA encryption and is an island to itself. My opinion is to stay away from H932, unless you are a T-mobile customer and specifically want H932 for the T-mobile LTE band 71. I welcome all H932 development, of course and am thankful we finally have root, etc for it. But no need to go out and buy it if you're not a T-mobile customer who wants LTE band 71. Other T-mobile customers have US998 -- original or converted from like LS998 -- and use it on T-mobile.)
Of the North American variants, only the US998 has fastboot flash commands AND has firmware which is totally compatible with all other North America variants, EXCEPT for H932. So, you at least temporarily convert to US998 to unlock bootloader, root. You can stay on US998 if you like, or you can flash back to another North America variant firmware at that point and still retain unlocked bootloader and TWRP (with ability to root). US998 is the official carrier unlocked North American variant, so works with most North American carries. However, some carriers only give some service options on their own firmware; Wi-Fi calling, etc. Your choice whether to stay on US998 firmware or flash to another carrier firmware. I'm on AT&T, but I am still running US998 rooted stock firmware.
2) Once bootloader unlocked and rooted, you can also install custom AOSP ROMs -- but some are easier than others. Former VS998, LS9998, AS998 and original US998 have no problems. AT&T H931 and Canada H933 have issues getting ASOP ROMs to boot up; however there's a complicated workaround was developed where you re-flash different firmware a few times for it to work. You can now run AOSP ROMs on H931/H933, but unless you already have those, there's no reason to specifically buy them if your desire is to run AOSP ROMs. T-mobile H932 has different RSA encryption and needs separate ROMs for that model.
3) The first dev to make several AOSP/Lineage ROMs registered his H930 on AFH server website (which a lot of XDA devs use, and which I use as they give free server space for development), and now AFH thinks ALL V30 are "H930". Even VS996, H933, US998 V30 KDZ which I upload to H930 are categorized by AFH as "H930" when it's not. Confuses people when they click on a link, goes to AFH website and says "H930". ALL AOSP/Lineage ROMs (unless specifically H932-only) are compatible with ALL V30/V30+/V30S.
4) For North American variants, you cannot cross flash H930 or H930DS full stock firmware "ROMs". Stock firmware ROMs are just stock KDZ in TWRP-flashable format. Do NOT try to flash a North American variant to a stock firmware H930/H930DS ROM. You can only flash other North American stock firmware (except for H932) and AOSP/Lineage ROMs. The ONE exception to that is the Boombox ROM -- which is BASED on H930 stock firmware, but IS compatible with all V30/V30+/V30S (except for T-mobile H932).
CONCLUSION
Anyway, that's why you see "H930" AOSP ROMS (they are not really just for H930) as well as H932 ROMs (and they ARE only for H932). The best North America variant phones to buy for AOSP/Lineage ROMS are LS998, VS996, AS998, and original US998. H931 and H933 can flash AOSP/Lineage ROMs but after bootloader unlock and root, you have to then go through another flashing procedure to make it work. T-mobile H932 has different RSA encryption and devs have to release separate ROMs for them.
After you bootloader unlock and root, I suggest trying out rooted stock firmware for awhile. Everything works, and on US998 20F we even now have DTS 3D stereo. There are Magisk mods you can flash which give even more capabilities. The only reason I suggest that is because it helps to have a baseline comparison. Then try the AOSP/Linage ROMs. That way if something doesn't work right, you know whether it's the ROM or the phone.
Click to expand...
Click to collapse
Ahhh okay this all makes sense now
And yeah that's exactly what I'm planning to do, I'll try the stock ROM for a while first.
Thanks so much for the clarification.
NeonHD said:
Ahhh okay this all makes sense now
And yeah that's exactly what I'm planning to do, I'll try the stock ROM for a while first.
Thanks so much for the clarification.
Click to expand...
Click to collapse
Be sure to flash this module on US998 20F...
https://forum.xda-developers.com/lg-v30/themes/anxiousv30-magisk-mod-t3865146
This is also cool:
https://forum.xda-developers.com/lg-v30/themes/enable-native-call-recording-lg-v30-t3869260
My LG US998 can't seem to boot any custom rom pass the boot animation screen
ChazzMatt said:
TLDR:
ALL AOSP/Lineage ROMs (unless specifically H932-only) are compatible with ALL V30/V30+/V30S.
Complete answer:
You've asked a complicated question.
* For the discussion below we are mostly talking about North America variants only.
* Some of this below does not apply to H930/H930DS/H930D/H930G (the 930's).
* Some of this below is also not just to answer this question but for other people who want to buy this fantastic phone.
1) For any V30/V30+/V30S, you have to have fastboot flash commands and have a specific date range of stock Oreo firmware to use the WTF exploit to unlock the bootloader and root. (This does not apply to the T-mobile H932. It has its own root method, has different RSA encryption and is an island to itself. My opinion is to stay away from H932, unless you are a T-mobile customer and specifically want H932 for the T-mobile LTE band 71. I welcome all H932 development, of course and am thankful we finally have root, etc for it. But no need to go out and buy it if you're not a T-mobile customer who wants LTE band 71. Other T-mobile customers have US998 -- original or converted from like LS998 -- and use it on T-mobile.)
Of the North American variants, only the US998 has fastboot flash commands AND has firmware which is totally compatible with all other North America variants, EXCEPT for H932. So, you at least temporarily convert to US998 to unlock bootloader, root. You can stay on US998 if you like, or you can flash back to another North America variant firmware at that point and still retain unlocked bootloader and TWRP (with ability to root). US998 is the official carrier unlocked North American variant, so works with most North American carries. However, some carriers only give some service options on their own firmware; Wi-Fi calling, etc. Your choice whether to stay on US998 firmware or flash to another carrier firmware. I'm on AT&T, but I am still running US998 rooted stock firmware.
2) Once bootloader unlocked and rooted, you can also install custom AOSP ROMs -- but some are easier than others. Former VS998, LS9998, AS998 and original US998 have no problems. AT&T H931 and Canada H933 have issues getting ASOP ROMs to boot up; however there's a complicated workaround was developed where you re-flash different firmware a few times for it to work. You can now run AOSP ROMs on H931/H933, but unless you already have those, there's no reason to specifically buy them if your desire is to run AOSP ROMs. T-mobile H932 has different RSA encryption and needs separate ROMs for that model.
3) The first dev to make several AOSP/Lineage ROMs registered his H930 on AFH server website (which a lot of XDA devs use, and which I use as they give free server space for development), and now AFH thinks ALL V30 are "H930". Even VS996, H933, US998 V30 KDZ which I upload to H930 are categorized by AFH as "H930" when it's not. Confuses people when they click on a link, goes to AFH website and says "H930". ALL AOSP/Lineage ROMs (unless specifically H932-only) are compatible with ALL V30/V30+/V30S.
4) For North American variants, you cannot cross flash H930 or H930DS full stock firmware "ROMs". Stock firmware ROMs are just stock KDZ in TWRP-flashable format. Do NOT try to flash a North American variant to a stock firmware H930/H930DS ROM. You can only flash other North American stock firmware (except for H932) and AOSP/Lineage ROMs. The ONE exception to that is the Boombox ROM -- which is BASED on H930 stock firmware, but IS compatible with all V30/V30+/V30S (except for T-mobile H932).
CONCLUSION
Anyway, that's why you see "H930" AOSP ROMS (they are not really just for H930) as well as H932 ROMs (and they ARE only for H932). The best North America variant phones to buy for AOSP/Lineage ROMS are LS998, VS996, AS998, and original US998. H931 and H933 can flash AOSP/Lineage ROMs but after bootloader unlock and root, you have to then go through another flashing procedure to make it work. T-mobile H932 has different RSA encryption and devs have to release separate ROMs for them.
After you bootloader unlock and root, I suggest trying out rooted stock firmware for awhile. Everything works, and on US998 20F we even now have DTS 3D stereo. There are Magisk mods you can flash which give even more capabilities. The only reason I suggest that is because it helps to have a baseline comparison. Then try the AOSP/Lineage ROMs. That way if something doesn't work right, you know whether it's the ROM or the phone.
Click to expand...
Click to collapse
Hello there i have rooted my us998 and unlocked the bootloader, i am able to flash custom roms in TWRP but they never seem to boot pass the boot animation screen. I have tried LOS16, Pixel experience and DOT OS, they all cant seem to boot pass that screen, so i am certain its not the ROMs (i downloaded the ROMS for h930).
Any help will be appreciated
6R1M_R34P3R said:
Hello there i have rooted my us998 and unlocked the bootloader, i am able to flash custom roms in TWRP but they never seem to boot pass the boot animation screen. I have tried LOS16, Pixel experience and DOT OS, they all cant seem to boot pass that screen, so i am certain its not the ROMs (i downloaded the ROMS for h930).
Any help will be appreciated
Click to expand...
Click to collapse
Then you've read Root Sticky Guide part about custom ROMs? It's linked in the WTF INSTRUCTIONS. (See attached screenshot.)
See post #2 of that thread: https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
What US998 firmware are you on? For LOS-16 PIE ROMS, your need to update to most recent Oreo. Or it won't boot/work right.
Was your phone always USS98 or is it former H931/H933? If you read the guide, you know why I'm asking. There's more stuff you would need to do. Or it won't boot.
ChazzMatt said:
Then you've read Root Sticky Guide part about custom ROMs? It's linked in the WTF INSTRUCTIONS. (See attached screenshot.)
See post #2 of that thread: https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
What US998 firmware are you on? For LOS-16 PIE ROMS, your need to update to most recent Oreo. Or it won't boot/work right.
Was your phone always USS98 or is it former H931/H933? If you read the guide, you know why I'm asking. There's more stuff you would need to do. Or it won't boot.
Click to expand...
Click to collapse
Yes i followed that guide word for word, and then updated to the latest rooted oreo firmware which is 20h after unlocking bootloader, by flashing from 20e to 20h back to back and then flashed magisk aftewards just as the guide said.
I honestly can't tell if this has always been a US998 model but then looking up the IMEI online shows its a V30 instead of a V30+
6R1M_R34P3R said:
Yes i followed that guide word for word, and then updated to the latest rooted oreo firmware which is 20h after unlocking bootloader, by flashing from 20e to 20h back to back and then flashed magisk aftewards just as the guide said.
I honestly can't tell if this has always been a US998 model but then looking up the IMEI online shows its a V30 instead of a V30+
Click to expand...
Click to collapse
Good that you updated to the latest Oreo.
Does your V30 have 128GB of memory or 64GB of internal memory? IF 128GB of internal memory then it's a V30+. It never could have been an AT&T H931 or Canada H933 as they don't natively have the 30+. It could have been a Sprint LS998 V30+ at one point in time, but there's no issues with former LS998 running custom roms.
It's just the we get people in here who go through the bootloader unlock -- but don't bother update to latest Oreo or don't read the part about h931 and h933, and then wonder why they can't boot to custom ROMs. I apologize, I thought you were one of those people.
Hello
I have Lg v30 model H933 and this guy who repaired my phone after it got bricked, flashed boot loader version of US998, now my question is if a flash firmware US99810c_03_1216.kdz will it brick my phone? It did brick my phone when I flashed US99810d_01_0411.kdz which is an Android oreo firmware.
SO my phone is booting up and working right now with firmware H93320h_00_OPEN_CA_OP_1123.kdz which is an oreo android version, this phone came with a nougat version and wifi was working on nougat so now i am trying and testing all the different available nougat firmwares available for V30 phones and even for different models just to see if any one of them would work so far none of the nougat firmwares have ever made further than lg logo screen at the startup of boot, and this is with any nougat version firmware i try regardless of their models of course still all for LG v30 .
Flashing Android oreo firmwares always started and booted nicely with any suitable model so far that I have tried but no wifi still and nougat no matter whichever model LG v30's firmware i try never made it past lg logo screen.
Please let me know any possible solution or idea anyone may have.
Thanks
sam_guy said:
It did brick my phone when I flashed US99810d_01_0411.kdz which is an Android oreo firmware.
Click to expand...
Click to collapse
For all V30...
10d is still Nougat.
Oreo starts with 20a, and goes up higher.
First Pie will be 30a.
ChazzMatt said:
10d is still Nougat, from April 2018.
Oreo starts with 20a, and goes up higher.
First Pie will be 30a.
Click to expand...
Click to collapse
Sorry my bad You are right, I flashed US99820d_01_0710.kdz and it got bricked and thats when I had the guy flash the boot loader again to get it to download mode again and then I flashed H93320h_00_OPEN_CA_OP_1123 the oreo version and phone is booting fine but no wifi so i am trying to get the nougat version flashed in this phone and get it to boot properly to see if wifi will work on nougat or not.
Thanks
ChazzMatt said:
For all V30...
10d is still Nougat.
Oreo starts with 20a, and goes up higher.
First Pie will be 30a.
Click to expand...
Click to collapse
so chazz what do you think in my situation. Should i try us998 10 c nougat?
i dont know why 20 d bricked my phone? do you have any idea? i am asking this just to make sure 10 c nougat of us998 wont brick my phone, just trying to understand the issue.
thanks a lot
sam_guy said:
so chazz what do you think in my situation. Should i try us998 10 c nougat?
i dont know why 20 d bricked my phone? do you have any idea? i am asking this just to make sure 10 c nougat of us998 wont brick my phone, just trying to understand the issue.
thanks a lot
Click to expand...
Click to collapse
The wild card is whatever the guy did to unbrick your phone. You may no longer have a "normal" phone. You SHOULD be able to flash US998 Nougat, master reset, then flash any version of US998 Oreo. With H933 you would have to DL Partition to US998 both times or even use Refurbish. It's in the Frankenstein instructions and countless people have done it. But the repair guy may have done something to interfere with that happening.
Hello. Im using lgv30 korean variant v300k. I have already talked to some other korean variant users and they say that they can use every non stock rom like pe havoc pixys and such. Currently im still at boombox v1.3 with twrp 3.2.7 dataimg. What i always do is reboot to recovery, wipe data/dalvik and cache/system. Then flash rom+gapps then reboot. Then icalways get stuck at boot animation regardless of what rom it is. I need help :crying:
awerqw22 said:
Hello. Im using lgv30 korean variant v300k. I have already talked to some other korean variant users and they say that they can use every non stock rom like pe havoc pixys and such. Currently im still at boombox v1.3 with twrp 3.2.7 dataimg. What i always do is reboot to recovery, wipe data/dalvik and cache/system. Then flash rom+gapps then reboot. Then icalways get stuck at boot animation regardless of what rom it is. I need help :crying:
Click to expand...
Click to collapse
These roms doesn't work on korean models. Havoc is only fro h930 and h932.
awerqw22 said:
Hello. Im using lgv30 korean variant v300k. I have already talked to some other korean variant users and they say that they can use every non stock rom like pe havoc pixys and such.
Currently im still at boombox v1.3 with twrp 3.2.7 dataimg.
What i always do is reboot to recovery, wipe data/dalvik and cache/system. Then flash rom+gapps then reboot. Then i always get stuck at boot animation regardless of what rom it is. I need help :crying:
Click to expand...
Click to collapse
1) I would flash a NEWER stock ROM first before flashing current AOSP/Lineage based ROMs. Boombox (based on early H930 stock Oreo) is very old, from 2018. You need a newer foundation.
[STOCK] Korean flashable ROM Zip for LGM-V300S/K (Maybe L)
Install that by @koo04034. Make a TWRP backup, then try flashing an AOSP/Lineage ROM.
2) Also try different GAPPS? See what GAPPS are recommended for each ROM.
---------- Post added at 03:55 PM ---------- Previous post was at 03:46 PM ----------
trouble. said:
These roms doesn't work on korean models. Havoc is only for h930 and h932.
Click to expand...
Click to collapse
Uh, no. Every V30 variant in the world can use Havoc if they wish. "H930" just means it's for every variant, except U.S. T-mobile H932. It has to say "H932" for U.S. T-mobile H932. U.S. T-mobile H932 is the only V30 variant which cannot install "H930" AOSP/Lineage ROMs.
Go read this sticky:
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
Specifically, see post #2, point 3:
Chazzmatt said:
3) ALL AOSP/LOS-based "H930" ROMs are compatible with ANY V30 variant, EXCEPT for U.S. T-mobile H932.
For AOSP/LOS-based custom ROMs, the "H930" description in the ROM title simply means ANY V30 variant can run it -- EXCEPT for U.S. T-mobile H932. That's just how it is. For T-mobile H932, the custom ROM description or download link must explicitly say "H932".
Click to expand...
Click to collapse
Some variants have problems installing AOSP/Lineage custom ROMs, like H931 and H933. Those need more prep work beforehand. And the sticky talks about that also... But all V30 variants can eventually install/run AOSP/Lineage custom ROMs (with the aforementioned restrictions on U.S. T-mobile H932).
@awerqw22 even said he talked to other Korean V30 owners who were running custom ROMs. He just can't figure out why HE can't install them.
Hi Folks,
I am new to community. Have been getting help from all of you but posting for the 1st time. I have At&t H931 V30. Stuck on android Oreo July 2018 security patch. Have gone through Frankenstein process post and ready to convert to US998 carrier just to enjoy the slice of pie.
Now Im confused it to the point that do I need to do WTF method as well to unlock bootloader for pie upgradation. I don't want to root the device. Just want to flash latest android pie on my V30. At&t has officially launched pie update in sept 2019 but I understand there is no kdz file and this is the only way.
Help would be much appreciated. LGUP dual mode also confused me. What if i only follow LGUP method and not go with the repatched version.
Thanks in advance
rundownaliabbas said:
Hi Folks,
I am new to community. Have been getting help from all of you but posting for the 1st time. I have At&t H931 V30. Stuck on android Oreo July 2018 security patch. Have gone through Frankenstein process post and ready to convert to US998 carrier just to enjoy the slice of pie.
Now Im confused it to the point that do I need to do WTF method as well to unlock bootloader for pie upgradation. I don't want to root the device. Just want to flash latest android pie on my V30. At&t has officially launched pie update in sept 2019 but I understand there is no kdz file and this is the only way.
Help would be much appreciated. LGUP dual mode also confused me. What if i only follow LGUP method and not go with the repatched version.
Thanks in advance
Click to expand...
Click to collapse
You don't need to use WTF INSTRUCTIONS just to Frankenstein to US998 and update to US998 Pie.
WTF instructions are ONLY for Bootloader Unlock, installing TWRP and Root.
This is what you want. See post #1:
AT&T H931/Sprint LS998 conversion to US998 to be able to get updates
https://forum.xda-developers.com/lg-v30/how-to/ls998-h931-how-to-update-t3927155
It will explain and take you to Frankenstein instructions...
After TEMPORARILY downgrading to US998 Nougat, then Master Reset (all explained in the Frankenstein instructions). But instead of upgrading to Oreo, you would flash US998 Pie from the Pie KDZ thread.
See post #2 for Pie KDZ:
https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99830a000704-kdz-t3952256
EDIT:
However, some people have not been able to update to the US998 Pie. If that happens, you can always use the Canada H933 Nougat then Pie KDZ conversion.
Since you don't care about root, that would work well for you, if you can't update to US998 Pie (it's a wonky KDZ).
H933 has more LTE bands than US998, actually...
Thanks will do that
Just one more thing I also checked my phones imei is not of original at&t LG V30 infact it is showing of some other phone. Its working till now. Would pie update change the imei or if not can it cause some issue later on? I hope imei would remain the same
rundownaliabbas said:
Just one more thing I also checked my phones imei is not of original at&t LG V30 infact it is showing of some other phone. Its working till now. Would pie update change the imei or if not can it cause some issue later on? I hope imei would remain the same
Click to expand...
Click to collapse
No, IMEI is not touched by anything we do in this V30 forum. At least nothing in any of my instructions. Your IMEI will remain the same.
Hello friends, I do not know if I have really damaged my phone. It is the h931 model converted to us998. Because of my desire to have a foot, I installed a KDZ of the European model h930. At the beginning the rom started without problems, after I noticed that it had no signal, I installed the Oreo us998 modem and it was still without a signal, so I went back to oreo us99820h and when it starts the screen it is welcome, the touch does not work for me. Any solution to this problem, I would appreciate suggestions and help. Thank you so much ♥
Yeriorlando said:
Hello friends, I do not know if I have really damaged my phone. It is the h931 model converted to us998. Because of my desire to have a foot, I installed a KDZ of the European model h930. At the beginning the rom started without problems, after I noticed that it had no signal, I installed the Oreo us998 modem and it was still without a signal, so I went back to oreo us99820h and when it starts the screen it is welcome, the touch does not work for me. Any solution to this problem, I would appreciate suggestions and help. Thank you so much
Click to expand...
Click to collapse
You screwed up.
NEVER NEVER NEVER flash stock H930* firmware over any North American variants. It says so in all the Instructions.
You ignored all warnings. WHY? Every Pie H93O* KDZ and TWRP flashable zip says "ONLY for H930, H930G, H930D, H930DS. Do NOT ask if others can flash this!"
Flash back to US998 Nougat to repair your damage. PARTITION DL, all partitions in Dev Patched LGUP.
Then use one of the 4 workarounds in post #6 of the US998 PIE KDZ thread to update to US998 Pie.
Did you not read about those? They are mentioned top of post #2. Go to Post #6 of the US998 Pie KDZ. Workaround #3 and #4 work for everyone. Two people yesterday said #4 worked for them.
Here's one:
sisiimaji said:
This is great, I have follow Method #4 it works very well, I've been waiting for so long to achieved it . :good:
Click to expand...
Click to collapse
Go to first page and scroll down to post #6...
https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99830a000704-kdz-t3952256