What roms are you running? I've been running BoomBox with no issues but I'd like to run a rom that has WiFi calling. What roms are you running for your TMobile service? How stable?
EDIT: ah, I see you clarified the question in the title.
KanBorges said:
What roms are you running? I've been running BoomBox with no issues but I'd like to run a rom that has WiFi calling. What roms are you running for your TMobile service? How stable?
Click to expand...
Click to collapse
You're talking about T-Mobile users on US998 (either converted or original) or T-Mobile users on T-Mobile H932?
Because there's a vast difference what ROMs can be run, depending on the model you have. T-mobile users on newly rooted T-mobile H932 can't run ANY custom ROMs right now.
But there are lots of T-mobile users on US998 (either converted or original). Depending on what they converted from, they can run custom ROMs. However, former H933 and H931 converted to US998 cannot run AOSP custom ROMs -- but can run stock-based custom ROMs. Original US998 or converted from Sprint LS998, regional carrier AS998, Verizon VS996 have no such restrictions.
ChazzMatt said:
EDIT: ah, I see you clarified the question in the title.
You're talking about T-Mobile users on US998 (either converted or original) or T-Mobile users on T-Mobile H932?
Because there's a vast difference what ROMs can be run, depending on the model you have. T-mobile users on newly rooted T-mobile H932 can't run ANY custom ROMs right now.
But there are lots of T-mobile users on US998 (either converted or original). Depending on what they converted from, they can run custom ROMs. However, former H933 and H931 converted to US998 cannot run AOSP custom ROMs -- but can run stock-based custom ROMs. Original US998 or converted from Sprint LS998, regional carrier AS998, Verizon VS996 have no such restrictions.
Click to expand...
Click to collapse
Yeah mine is a (Not converted)US998 running BoomBox on TMobile.
This one seems good. I have WiFi calling and it's running smooth on my US998 with T-Mobile. Lastest Magisk is good as well. ?
ROM Thread: https://forum.xda-developers.com/lg-v30/development/rom-lg-us998-20d-rom-t3830318
Screenshots attached.
Im running Invictrix 9.0 as my daily. need to fix ims system to get wfc so thats one of my goals(im an invictrix dev. thats why i have it even though its not released.)
KanBorges said:
This one seems good. I have WiFi calling and it's running smooth on my US998 with T-Mobile. Lastest Magisk is good as well. ?
ROM Thread: https://forum.xda-developers.com/lg-v30/development/rom-lg-us998-20d-rom-t3830318
Screenshots attached.
Click to expand...
Click to collapse
That's just stock US998 20D. @westwood24 made it into a TWRP flashable zip file, so you can flash it like a ROM.
It's great for updating like from 20A or 20B, after bootloader unlock, installing TWRP.
You can get the same firmware by flashing 20D KDZ... But it's harder than just flashing that with TWRP.
me2151 said:
Im running Invictrix 9.0 as my daily. need to fix ims system to get wfc so thats one of my goals(im an invictrix dev. thats why i have it even though its not released.)
Click to expand...
Click to collapse
Interested in seeing it when it's finished
US998 seems to be working with T-Mobile wifi calling well. I tried to enable it on At&t and it told me that I have not configured my T-Mobile SIM right. It's obvious that that this is designed for T-Mobile wifi calling.
Anyway to get this enabled for 9 GSI?
Related
Sorry about creating a thread but wanted to make sure I can flash Sprint LG v30+ to T-Mobile without issue. Tried to read a few threads but from my understanding Oreo had messed things up at one point.
Does it have to be unlocked through Sprint first?
Simple flash T-Mobile or international rom makes it usable?
intruda119 said:
Sorry about creating a thread but wanted to make sure I can flash Sprint LG v30+ to T-Mobile without issue. Tried to read a few threads but from my understanding Oreo had messed things up at one point.
Does it have to be unlocked through Sprint first?
Simple flash T-Mobile or international rom makes it usable?
Click to expand...
Click to collapse
No, doesn't have to be unlocked through Sprint first. And Oreo didn't mess up anything.
Some of the T-Mobile guys are complaining about T-mobile Oreo. I own five US998 and don't see anything they are complaining about. Must be a T-Mobile H932 issue.
You will convert LS998 V30+ to official carrier unlocked model US998 V30+ with Oreo, and run on T-Mobile. Converting to US998 carrier unlocks the phone and gives it fastboot flash commands.
You can stop there, or you can bootloader unlock, install TWRP and root the phone.
Whatever you do after that (Install ROMs or whatever) is your choice.
You will NOT flash T-Mobile firmware onto the phone or you will brick the phone.
Many T-Mobile users are running rooted US998 (original or converted) on T-Mobile.
ChazzMatt said:
No, doesn't have to be unlocked through Sprint first. And Oreo didn't mess up anything.
Some of the T-Mobile guys are complaining about T-mobile Oreo. I own five US998 and don't see anything they are complaining about. Must be a T-Mobile H932 issue.
You will convert LS998 V30+ to official carrier unlocked model US998 V30+ with Oreo, and run on T-Mobile. Converting to US998 carrier unlocks the phone and gives it fastboot flash commands.
You can stop there, or you can bootloader unlock, install TWRP and root the phone.
Whatever you do after that (Install ROMs or whatever) is your choice.
You will NOT flash T-Mobile firmware onto the phone or you will brick the phone.
Many T-Mobile users are running rooted US998 (original or converted) on T-Mobile.
Click to expand...
Click to collapse
Thank you for clearing that up for me.
My Sprint V30+ is sim unlocked. If I flash it to carrier unlocked phone and toss a TMobile sim in it, will I get access to VoLTE?
Right now when I toss a TMobile sim in it, calls drop to 2G/3G.
red_dog007 said:
My Sprint V30+ is sim unlocked. If I flash it to carrier unlocked phone and toss a TMobile sim in it, will I get access to VoLTE?
Right now when I toss a TMobile sim in it, calls drop to 2G/3G.
Click to expand...
Click to collapse
If flashed to US998 Oreo you will definitely get T-Mobile Wi-Fi calling.
T-Mobile users can answer specifically about T-Mobile VoLTE on US998.
But since you can temporarily drop down to HSPA for phone calls and still get data, it's not critical. I don't have VoLTE on my AT&T Prepaid plan and I don't care.
I currently have a Sprint LS998 which I've been using for almost a year, with the recent OTA update LTE calling is getting disable which is a real bummer and Sprint's VoLTE isn't available in my area. After looking on the forum pages I found out that it is possible to flash my Sprint LS998 to a US998 but had a couple of questions before I attempted it.
1. Will it work with on TMobile/AT&T/Verizon?
2. If i do decide to flash will I still retain VoLTE, HD Calling, Wifi Calling when switching to a new network?
3. Once I've flashed will I still be able to obtain OTA updates?
Sorry if these are noob questions, I am quite new to this. Thanks.
myroofisonfire said:
I currently have a Sprint LS998 which I've been using for almost a year, with the recent OTA update LTE calling is getting disable which is a real bummer and Sprint's VoLTE isn't available in my area. After looking on the forum pages I found out that it is possible to flash my Sprint LS998 to a US998 but had a couple of questions before I attempted it.
1. Will it work with on TMobile/AT&T/Verizon?
2. If i do decide to flash will I still retain VoLTE, HD Calling, Wifi Calling when switching to a new network?
3. Once I've flashed will I still be able to obtain OTA updates?
Sorry if these are noob questions, I am quite new to this. Thanks.
Click to expand...
Click to collapse
Yes to most of your questions.
I believe you can get T-Mobile VoLTE converting LS998 to US998 KDZ, just through Frankenstein. I know there's lots of US998 on T-mobile.
I KNOW you can get Verizon VoLTE/WiFi calling by converting LS998 to VS996 with KDZ, via Frankenstein. But you would need already-activated Verizon SIM card.
However, for AT&T features like that, you need bootloader unlock, TWRP and then flash AT&T stock firmware ROM. Which means you would Frankenstein to US998 to get fastboot flash commands. If you were bootloader unlocking and installing TWRP, you could also afterwards flash the latest Verizon stock firmware "ROM" (built from the latest Verizon KDZ), if you didn't want AT&T. However, I recommend AT&T just because I use them.
So, you have options with both stock firmware KDZ or options after bootloader unlock and TWRP -- whatever you prefer.
----
You may not receive OTA after converting from LS998 -- but you don't need it. We have all the latest firmware posted here (in both KDZ and TWRP flashable zip "ROM") in this forum. For reasons unexplained, my wife has not received any OTA for her totally stock US998 since January 2018, but she's still on the latest firmware. I flashed it via LGUP. For myself, I use TWRP-flashable zip (since I'm bootloader unlocked and have TWRP). Easy to flash newer firmware in less than 5 minutes, which is typically released every 2 or 3 months.
ChazzMatt said:
Yes to most of your questions.
I believe you can get T-Mobile VoLTE converting LS998 to US998 KDZ, just through Frankenstein. I know there's lots of US998 on T-mobile.
I KNOW you can get Verizon VoLTE/WiFi calling by converting LS998 to VS996 with KDZ, via Frankenstein. But you would need already-activated Verizon SIM card.
However, for AT&T features like that, you need bootloader unlock, TWRP and then flash AT&T stock firmware ROM. Which means you would Frankenstein to US998 to get fastboot flash commands. If you were bootloader unlocking and installing TWRP, you could also afterwards flash the latest Verizon stock firmware "ROM" (built from the latest Verizon KDZ), if you didn't want AT&T. However, I recommend AT&T just because I use them.
So, you have options with both stock firmware KDZ or options after bootloader unlock and TWRP -- whatever you prefer.
----
You may not receive OTA after converting from LS998 -- but you don't need it. We have all the latest firmware posted here (in both KDZ and TWRP flashable zip "ROM") in this forum. For reasons unexplained, my wife has not received any OTA for her totally stock US998 since January 2018, but she's still on the latest firmware. I flashed it via LGUP. For myself, I use TWRP-flashable zip (since I'm bootloader unlocked and have TWRP). Easy to flash newer firmware in less than 5 minutes, which is typically released every 2 or 3 months.
Click to expand...
Click to collapse
Just to confirm in order to get the phone working on AT&T I need to first Frankenstein it to US998, then unlock the bootloader, and finally flash an AT&T stock firmware ROM? From then I should be able to put an AT&T sim card and activate service?
myroofisonfire said:
Just to confirm in order to get the phone working on AT&T I need to first Frankenstein it to US998, then unlock the bootloader, and finally flash an AT&T stock firmware ROM? From then I should be able to put an AT&T sim card and activate service?
Click to expand...
Click to collapse
We're getting into a lot of scenarios here. I don't want to tell you wrong, but there's lots of options. For ME, I care about bootloader unlock and root and my answers are going to be skewed that way.
1) If you do NOT want that, just buy an AT&T H931. Done.
2) My phone works on AT&T as US998 -- but I don't have Wi-Fi calling. I have AT&T Prepaid and I don't care.
3) If you buy another North America variant (say fantastic price) that can be Frankensteined, and you want all the options and privileges on AT&T you will need to flash it first to US998 -- bootloader unlock/install TWRP -- and then flash the AT&T zipped firmware file.
The only caveat is most people who do this already have activated AT&T SIM card. US998 and H931 will activate on AT&T just fine. BUT they may balk at "Sprint" LS998 IMEI even though it may have US998 or H931 firmware. Depends on the store you use. There are other North America variants you can buy but for some reason the LS998 V30+ (whether actual or already flashed to US998) is ridiculously inexpensive.
Hello guys, if I bought a Sprint lg v30 with a bad imei, can I Frankenstein to US998 and use it with T mobile and ATT?
fubugang said:
Hello guys, if I bought a Sprint lg v30 with a bad imei, can I Frankenstein to US998 and use it with T mobile and ATT?
Click to expand...
Click to collapse
Frankensteining doesn't change the IMEI.
Talk about changing the IMEI is not allowed on XDA, as I recall... you may have to look elsewhere.
I'm gonna hijack this thread to ask a couple questions about Frankenstein v30's. I'm a Canadian on Bell and want to pick up a v30. I found a bunch on ebay us998 for a good price, how can I tell if it's been done? Will it really affect me at all if it is? I do travel to the US sometimes does that mean anything for when I try to use it down there?
mistaliu said:
I'm gonna hijack this thread to ask a couple questions about Frankenstein v30's. I'm a Canadian on Bell and want to pick up a v30. I found a bunch on ebay us998 for a good price, how can I tell if it's been done?
Click to expand...
Click to collapse
At worst you would need an already activated SIM card, if it's LS998 to US998. I've owned two and two friends have a couple -- all of us are on AT&T and just put in our SIM cards. A friend just went today with a converted LS998/US998 and AT&T ACTIVATED a new SIM card for her. She called me to tell me of the success. I was a little worried. For her other LS998/US998 phone (a few months ago) it was an already activated SIM card, but this "new" phone (today) was for her sister.
I can't tell you about Canadian carriers' views on that subject.
mistaliu said:
I do travel to the US sometimes does that mean anything for when I try to use it down there?
Click to expand...
Click to collapse
You would just need to find a carrier who doesn't care it was possibly a Sprint phone but is now a carrier unlocked US998. Shouldn't be an issue unless you are trying to use Verizon or Sprint.
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
which room you guys like more
Well. If aosp rom support night sight and work greate. I will use aosp which stable. My v30 on havoc now. But too lazy to back stock rom
And i try to add my device to dualbootpatcher to use dual boot. My v30 is v300k. And dualboot already add ls998 but not working. Flash havoc multiboot when i boot it just reboot to recovery
Havoc is all the way good for me, no problems so far, just waiting on the update build,and like I said before if we can get Ground Zero ROMs || Validus - Tesla - Tipsy, that's when I'm leaving my havoc rom
"Important notice"???
Mohzuned said:
[Important notice] [LG V30- h930, h931, h932, h933] [ roms]
which room you guys like more
Click to expand...
Click to collapse
B3311 said:
"Important notice"???
Click to expand...
Click to collapse
Yeah, I'm a little confused too. What EXACTLY is the question? What if I like US998 or AS998 stock ROM more? Why are they not listed? Where's LS998? Where's VS996?
To bootloader unlock, TWRP installation, and root, ALL the North American variants (EXCEPT for the T-mobile H932) have to at least temporarily convert to US998 or already be a US998 for fastboot flash commands. Afterwards users can flash what they want -- including TWRP flashable zip files to convert back to former model (H931, VS996, H933, AS998) if they desire to regain carrier-specific options like VoLTE/Wi-Fi calling. (Depends on the carrier if they limit those to their branded models.) Or users can go flash custom ROMs. But many STAY on US998 as it is carrier unlocked and devoid of most bloatware. Even when flashing a custom ROM, they are most often flashing FROM US998 stock rooted firmware. So, very strange it's not listed whatsoever.
H930 is Europe open market carrier unlocked.
H931 is AT&T, but carrier locked to AT&T. Only AT&T customers want that.
H932 is T-mobile but has different RSA encryption from other North American carriers.
H933 is the Canada model, for all Canadian carriers -- but it is carrier unlocked.
US998 is the official open market North American carrier unlocked model -- while also being sold by U.S. Cellular as their V30. V30S is also a US998 variant -- US998R.
Of ALL the North American variants, the US998 is the ONLY one with fastboot flash commands.
AS998 is the "regional carrier" version of the US998, but it doesn't have fastboot flash commands.
LS998 is Sprint's carrier locked V30/V30+.
VS996 is Verizon's V30, and is carrier unlocked.
Then there's H930DS (middle East/Africa/Asia) -- which is the dual SIM V30+, as well as the H930D (Middle East) -- which is the dual SIM version of the V30.
There's also three Korean carrier variants, plus a somewhat strange Japanese V30+.
Right now most custom ROMs are compatible with MOST of the the V30 series. However, H931/H933 has issues booting Oreo custom ROMs. H932 has different RSA encryption, so needs a separate ROM version. The goal would be to UNIFY all the variants so all ROMs would be compatible with ALL variants.
I would be happy with anything that boots on h931.
ChazzMatt said:
Yeah, I'm a little confused too. What EXACTLY is the question? What if I like US998 or AS998 stock ROM more? Why are they not listed? Where's LS998? Where's VS996?
To bootloader unlock, TWRP installation, and root, ALL the North American variants (EXCEPT for the T-mobile H932) have to at least temporarily convert to US998 or already be a US998 for fastboot flash commands. Afterwards users can flash what they want -- including TWRP flashable zip files to convert back to former model (H931, VS996, H933, AS998) if they desire to regain carrier-specific options like VoLTE/Wi-Fi calling. (Depends on the carrier if they limit those to their branded models.) Or users can go flash custom ROMs. But many STAY on US998 as it is carrier unlocked and devoid of most bloatware. Even when flashing a custom ROM, they are most often flashing FROM US998 stock rooted firmware. So, very strange it's not listed whatsoever.
H930 is Europe open market carrier unlocked.
H931 is AT&T, but carrier locked to AT&T. Only AT&T customers want that.
H932 is T-mobile but has different RSA encryption from other North American carriers.
H933 is the Canada model, for all Canadian carriers -- but it is carrier unlocked.
US998 is the official open market North American carrier unlocked model -- while also being sold by U.S. Cellular as their V30. V30S is also a US998 variant -- US998R.
Of ALL the North American variants, the US998 is the ONLY one with fastboot flash commands.
AS998 is the "regional carrier" version of the US998, but it doesn't have fastboot flash commands.
LS998 is Sprint's carrier locked V30/V30+.
VS996 is Verizon's V30, and is carrier unlocked.
Then there's H930DS (middle East/Africa/Asia) -- which is the dual SIM V30+, as well as the H930D (Middle East) -- which is the dual SIM version of the V30.
There's also three Korean carrier variants, plus a somewhat strange Japanese V30+.
Right now most custom ROMs are compatible with MOST of the the V30 series. However, H931/H933 has issues booting Oreo custom ROMs. H932 has different RSA encryption, so needs a separate ROM version. The goal would be to UNIFY all the variants so all ROMs would be compatible with ALL variants.
Click to expand...
Click to collapse
In our Kernel there need to add us998 or us996 defconfig.
So yeah in coming up days, I will build for models of lg v30.
I mean h930, h931, h932, h933, us998 or something like this. All models..
Mohzuned said:
In our Kernel there need to add us998 or us996 defconfig.
So yeah in coming up days, I will build for models of lg v30.
I mean h930, h931, h932, h933, us998 or something like this. All models..
Click to expand...
Click to collapse
H930 (and D/DS), US998, LS998, VS996, and 2 of the 3 Korean models work fine with the H930 build.
H931 and H933 can boot us998 stock rom, but even with using full us998 blobs + kernel config, it doesnt work (i think @me2151 also tried H931 blobs?)... and theres 1 case of a H933 which can boot all AOSP ROMs... so it has to be something else (maybe certain combination of bootloader + modem... who knows)
And H932 needs their own firmware files, but that works already.
I would be happy with anything that actually works on a 933 that isn't just a modified stock firmware with root and twrp ability.
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.
Probably a stupid question, but just trying to understand why no 10.0 rom can boot yet on the h932. Curious if it may not be possible on this variant for some reason. Thanks.
bigcletus said:
Probably a stupid question, but just trying to understand why no (LOS-17.x) 10.0 rom can boot yet on the h932. Curious if it may not be possible on this variant for some reason. Thanks.
Click to expand...
Click to collapse
First you need to look at the history of the T-mobile H932.
1) The T-mobile H932 has different RSA encryption, is an island unto itself. With the other variants, especially North America, you can cross flash to actually convert (Frankenstein) to those variants. US998, AT&T H931, Sprint LS998, Verizon VS996, Canada H933, regional AS998 are all totally cross compatible as long as you follow the Frankenstein instructions; you can convert to any of those models gaining all the respective CDMA/HSPA/LTE bands of that different model.
Between the various H930 variants, the North America and the Asian variants you have somewhat less compatibility. However, you can still flash other stock firmware -- but have to omit certain partitions (like modem, which cancels out the reason most people want to cross flash).
With T-mobile H932 it's totally different.
This is why the T-mobile H932 can't use the WTF method to unlock bootloader, install TWRP and root. (It can't convert -- even temporarily to US998 -- for necessary fastboot flash commands.) T-mobile H932 only got root three months later through genius @runningnak3d LAF exploit, which is totally different method. All other V30 variants use WTF exploit (unless eligible for LG's official bootloader unlock -- but even many of those use WTF as it's easier).
The first dev who created the LOS tree for V30/Joan (SGCMarkus) owned an H930. It was relatively simple to then make "H930" LOS compatible with all other variants -- EXCEPT for T-mobile H932. "H390" LOS ROMs are really "V30" or "Joan" ROMs -- except for T-mobile H932. Stay on latest stock firmware for your variant and just flash LOS ROM + Magisk.
2) For T-mobile H932 the main LOS tree was NOT compatible. There's a separate T-Mobile H932 LOS tree.
For LOS-16 ROMs, initially, Devs had to create both the "H930" (all variants except for T-mobile H932) and then create completely separate "T-mobile H932" ROMs. A few devs did this, but it got tiresome.
3) Then SGCMarkus created a zip file T-mobile H932 users could flash AFTER installing LOS-16 "H930" to implement the changes needed to make it compatible with T-mobile H932. A conversion zip, so devs didn't need to create separate T-mobile H932 ROMs He looked at the differences between the regular "H930" LOS-16 ROMs and the specific "T-mobile H932" LOS-16 ROMs and his conversion zip turned H930 ROM into T-mobile H932 ROM.
Now, all T-mobile H932 users could use ANY LOS-16 ROM!
4) But with LOS-17.x (Android 10), this LOS-16 T-mobile H932 conversion zip no longer works. Also, no dev has come along to make a separate LOS-17.x T-mobile H932 compatible ROM, so SGCMarkus can make a newer conversion/compatibility zip. He's also working on V40 and V50 ROMs, besides being in university full time... So he would need a dev to create a T-mobile H932 LOS-17.x ROM to begin, with so he could have a blueprint for any possible LOS-17.x conversion zip. Even then he would need to find time to do it.
5) There was a dev (@ShapeShifter499) who was working towards that goal. He had T-mobile H932 and had even updated LOS-16 to current security patch. He had even made SEPARATE T-mobile H932 updated LOS-16 ROM.
He was very energetic about it, and his eventual end game was to start working on LOS-17 ROMs with SGCMarkus to make them compatible with T-mobile H932. (He wasn't actually a T-mobile customer, I don't believe, but he had "accidentally" bought a T-mobile H932). But then he bricked his phone experimenting, trying to cross flash other stock Pie V30 variant kernels (or something like that). The different RSA encryption is a bear and the notes in LG's Pie kernel source code are not clear. The LG notes make it seem that with Pie kernels, the RSA incompatibility no longer exists -- but it does. I think he got a US998 V30+ as replacement, so I don't believe he is working on that anymore.
ShapeShifter499 said:
I HAVE BRICKED MY PHONE
I know what I did wrong but I was able to return the phone and will be getting another soon.
I probably will not get another h932 model so I can't support that.
Click to expand...
Click to collapse
________
Devs, if I have said anything incorrect, feel free to clarify. This is the situation as I understand it.
EDIT: ShapeShifter499 does use a T-mobile MVNO.
ChazzMatt said:
5) There was a dev (@ShapeShifter499) who was working towards that goal. He had T-mobile H932 and had even updated LOS-16 to current security patch. He had even made SEPARATE T-mobile H932 updated LOS-16 ROM.
He was very energetic about it, and his eventual end game was to start working on LOS-17 ROMs with SGCMarkus to make them compatible with T-mobile H932. (He wasn't actually a T-mobile customer, I don't believe, but he had "accidentally" bought a T-mobile H932). But then he bricked his phone experimenting, trying to cross flash other stock Pie V30 variant kernels (or something like that). The different RSA encryption is a bear and the notes in LG's Pie kernel source code are not clear. The LG notes make it seem that with Pie kernels, the RSA incompatibility no longer exists -- but it does. I think he got a US998 V30+ as replacement, so I don't believe he is working on that anymore.
________
Devs, if I have said anything incorrect, feel free to clarify. This is the situation as I understand it.
Click to expand...
Click to collapse
Mostly correct but I do not have a new v30 yet of any kind yet. I ended up needing the money I got from returning the device for other things more, then also there's this virus thing. So I don't know when I can obtain another. I'm on the telegram chat for v30 owners if anyone wants to help or ask any questions about support.
I do have T-Mobile, it's through a third party so I don't pay them directly but the SIM I use is T-Mobile.
EDIT: In the mean time I have a old Google Tango (Yellowstone) Tablet that works fine with the T-Mobile sim, no calls which sucks if there was ever an emergency but I don't actually call much to matter.