[LG V30 Guides, News, & Discussion] ChazzMatt:
POST #2:

FAQ ON AOSP/Lineage/LOS-16 & LOS 17.x CUSTOM ROMS

1) What's the deal? Why are V30 LOS-based ROMs called "H930" ROMs? Yet everyone says they work all other variants. Why not call them "V30" ROMs?

IGNORE that V30 LOS-based ROMs are called "H930" ROMs.

They are indeed "V30" ROMs. They are "Joan" (code name for LG V30) ROMs. Do NOT try to flash stock H930* firmware over North American variants to run LOS-based "H930" ROMs!

The "H930" label is sort of a "mistake" from the beginning which we can't go back and fix in the LOS tree. ("Mistake" isn't quite the right word but will do for now.)

* ALL LOS-16 based ROMs are compatible with ANY V30 variant, including T-Mobile H932.

* LOS-17 based ROMs are compatible with ANY V30 variant --EXCEPT for U.S. T-Mobile H932.

EDIT: As of October 2020, any LOS-based custom ROMS produced AFTER that are compatible with T-Mobile H932. Thanks to the efforts of @ShapeShifter499. To be safe, only install latest ROMs made well AFTER 2020.

See Question #4 below for more information about T-mobile H932 which ARE compatible with LOS-16 ROMs.

____________

2) Uh, so I've bootloader unlocked, installed TWRP and rooted and on Nougat/early Oreo. I don't plan on running stock firmware, so I can just go install an "Android 10" (LOS-17) ROM, right?

NO.

* You need to be on most recent OREO stock rooted firmware before attempting to install AOSP/LOS-16 Pie/Android 9 custom ROMs. V30 LOS-16 ROMs need LG stock Oreo/Android 8 blobs (drivers) and you need the most RECENT for everything to work right.

* You need to be on Pie/Android 9 stock rooted firmware before attempting to install V30 AOSP/LOS-17 "Android 10" custom ROMs. V30 LOS-17 ROMs need LG stock Pie/Android 9 blobs (drivers) for everything to work right.

In particular you can NOT be on LG early Oreo or Nougat, even though you needed to be on that initial bootloader unlock. There are TWRP-flashable zips (ROMs) based on stock Oreo/Android 8 KDZ or Pie/Android 9 KDZ to help you upgrade to later stock firmware. Links for stock firmware TWRP-flashable zips are posted in the Oreo/Android 8 and Pie/Android 9 KDZ threads for most major variants. Use these TWRP-flashable zips to update to most recent Oreo/Android 8 or Pie/Android 9 stock firmware before flashing any V30 AOSP/LOS-based custom ROMs.

When rooting your V30/V30+/V30S, you will TEMPORARILY downgrade to earlier LG stock firmware which can be exploited, unless you are already on that earlier firmware. After rooting, you should immediately upgrade back to most recent stock Oreo/Android 8 firmware via those TWRP-flashable zips or else things probably won't work right.

You do need to update to stock Pie first before trying to install "Android 10" LOS-17 custom ROMs.

____________

3) Hey, my AT&T H931/Canada H933 can't boot these LOS-based ROMs. What am I doing wrong?

FYI: AT&T H931 and Canada H933 V30 variants will need additional prep work before installing AOSP/LOS-based custom ROMs.

You can do it, there are dedicated threads for it. But just warning you -- it's many additional steps besides simple bootloader unlock, TWRP and root.

* Running any AOSP ROM on an US998 converted H931

* [GUIDE] Canadian H933 compatibility with AOSP ROMs

____________

4) Tell me again about T-Mobile H932 and LOS-ROMs?

As of October 2020, any LOS-based ROMS produced after that date should be compatible with T-Mobile H932. Thanks to @ShapeShifter499. BEFORE that date, the ROM had to be specifically made for T-Mobile H932. To be safe, only install latest ROMs made well after 2020.

AFTER October 2020, ALL LOS "H930" Pie LOS-based custom ROMs are compatible with ANY V30 variant.

For LOS-based custom ROMs, the "H930" description in the ROM title simply means ANY V30 variant can run it. "H930" is often the generic name for the V30 series. I could explain why, but it doesn't matter. The exception is if you are installing H930 stock ROMs. Do NOT try to do that with H932! You will brick your phone. That's just how it is.

NOTE: For LOS-16 you need most recent stock Oreo blobs (drivers), NOT stock Pie. You need to be on last stock Oreo firmware for LOS-16. THIS is last T-Mobile H932 Oreo:

[STOCK] [H932] [20s] [Oreo] T-Mobile LG V30 Stock Collection (Includes Debloated) by weakNPCdotCom

https://xdaforums.com/lg-v30/development/stock-t-mobile-lg-v30-stock-collection-t3917560

____________

5) I need VoLTE!

I have India Jio carrier and they only have LTE, with no 3G HSPA to temporarily drop down to for voice calls.

Also, in the U.S., Verizon, AT&T and T-Mobile are shutting down their 3G CDMA and HPSA in 2022.

I need VoLTE!

No VoLTE or VoWiFi on LOS-based ROMs. Stop asking. (Stock based ROMs like A.I.X. do have VoLTE.)

If you absolutely need VoLTE you need to flash back to stock firmware or possibly check out A.I.X. (But no promises about VoLTE on AIX for everyone. It also depends on the carrier.)

* Most Verizon users need Verizon VS996 firmware for VoLTE, but US998 can work.

* T-Mobile SIM card users can get VoLTE on both US998 firmware or T-Mobile H932 firmware

(WARNING: T-Mobile H932 firmware is only compatible with T-Mobile H932 phones. US998 firmware is NOT compatible with T-Mobile H932 phones, but can be flashed to any other North American V30 variant).

* India Jio users can use EAS (India) H930DS Pie firmware. Also, last Oreo EU H930 firmware has Jio VolTE, but not the EU H930 Pie firmware.

____________

6) What is this A.I.X. ROM I hear people talk about? I can't find it on XDA.

It's a Pie stock-based ROM. Like stock on steroids. Vast improvements in camera and battery usage. No, not found on XDA can be found elsewhere. Not for newbies, but users swear by it.

EDIT: The A.I.X. dev has pulled all files from public view.

____________

7) What if I don't like LOS-based custom ROMs? I hear there are bugs, we can't use LG camera, and there's no VoLTE.

Bugs in LOS-17 are slowly going away, but everything on stock rooted firmware does work just fine. I actually suggest you unlock bootloader, install TWRP and root and run rooted most-recent Oreo stock firmware -- with some Magisk mods -- for awhile before jumping into the custom LOS ROMs. (See point #1 about not updating to stock Pie until you are sure.) Read the various custom ROM threads -- see what works, what doesn't.

If you just want to run rooted stock firmware with Magisk and edXposed (to pass Safety Net) mods, last stock Oreo firmware is the most stable and stock Pie is not really an improvement.

____________

8) Why do I need TWRP? I just want ROOT!

PLEASE make TWRP backups, so you can restore back to rooted stock firmware in case you mess up something!

TWRP custom recovery is a magical time machine which can help you go back before you did something you shouldn't have. ;) But it can only help you if you have a backup to restore. One of the best feelings in the world is when you done something idiotic on your rooted phone -- and then you remember you have a recent TWRP backup. You don't need to ask for help and no one even needs to know. ;)

Also there are some mods you can only flash in TWRP.

____________

WARNING: Pedantic complaint ahead! TLDR: Calling a ROM by the letter Q is ignorant. I don't care who is doing it, it shows they don't understand the Android naming system.

9) What is the difference between Android "Q" ROMs and "Android 10" ROMs? I see both names, sometimes used interchangeably.

Please don't call Android 10 "Q". Q was the beta name. It's now graduated. It's no longer beta. It's "Android 10" -- and has the Android statue at Google HQ to prove it. ;) LOS-17.x custom ROMs are based on Android 10 -- not made from beta "Q" (pre-Android 10) software. :rolleyes:

If you are not aware...

With Google's long-time naming scheme for Android, first they released beta "alphabet letter", then revealed full name + statue at graduation from beta status. Final release name was based on a sweet snack/dessert. Many times over the years Google teased devs/users what the REAL name was going to be with false clues. If you keep using beta letter, you are REALLY referring to the old beta software, not current Android software. What confused some people with Android 10 is the escort dessert name never came. Instead of naming it after a dessert, Google decided beta Q would simply became Android 10. The statue at Google headquarters is "Android 10."

CONCLUSION:

No actual "Q" ROMs exist, to my knowledge or they are very outdated. "Q" was the beta letter for what became Android 10. Like a caterpillar vs butterfly. You don't keep calling it a caterpillar once it's turned into a butterfly!

"Q" on the left, "Android 10" on the right

People who call Android 10 by beta letter "Q" are committing a faux pas -- or simply they have no clue what they are talking about. If they are too lazy to say "Android 10", then just call it "10". Like they will eventually do with "11" or "12". Regrettably this includes some younger users -- even some Devs -- who came along recently and don't understand Google's historical naming convention. Starting with 2020 "Android 11", Google is ditching the beta "alphabet letter" entirely. It's simply called "Android 11 Developer Preview", and will be called Android 11 upon release. Same with 2021 "Android 12"... No more beta letters! But also no more dessert names, which were fun.

____________

But for those of you who don't know how it all worked over the past decade, read on...

When Google graduated an OS from beta to official release, they give it FULL name and a statue on Google Headquarters. The Naming/Statue Ceremony is a BIG deal and no one uses the beta letter again -- because it's officially out of beta.

"K", "L", "M", "N", "O", "P", "Q" were merely the beta letters before release and Google officially named them. I could go all the way back to beta "C" which became "Cupcake" -- but you get the point.

In the past, the official name was always a full dessert/snack name based on the beta letter. What the official name was going to be was always a matter of intense speculation in the months prior to release/naming ceremony and Google would often put false clues in the beta "letter" firmware. Only when the statue was revealed would you know the official name.

Beta "K" became "Kitkat" (Android 4.4, 2013) and got Kitkat statue

Beta "L" became "Lollipop" (Android 5, 2014) and got Lollipop statue

Beta "M" became "Marshmallow" (Android 6, 2015) and got Marshmallow statue

Beta "N" became "Nougat" (Android 7, 2016) and got Nougat statue

Beta "O" became "Oreo" (Android 8, 2017) and got Oreo statue

Beta "P" became "Pie" (Android 9, 2018) and got Pie statue

However, for Beta "Q" graduation, Google jettisoned the dessert name and only went with the version NUMBER, Android 10.

Beta Q became "Android 10" (2019) and got Android 10 statue.

It's no longer Q, because it's no longer beta OS. It's officially Android 10 with statue to prove it. If you speak of Q, you are talking about the beta firmware that came prior to "Android 10".

____________

WARNING: Sarcastic question ahead!

10) When I want to ask a question, I just post in the nearest thread I can find. Even if sort of on topic, I don't bother reading anything in that thread. Because my question is unique. No one in the past 3 years could have ever had a similar situation with this phone. Right?

Actually would be good for you to search relevant threads. 50 other people probably had the same issue, same question last year. Quick keyword search in a thread can give you immediate answer, without even posting your question. Besides simple keyword search, read the last few posts of a thread. Don't be narcissistic and assume ONLY YOU have ever encountered this issue or have this question. :p This phone was released in 2017 and I bet there's NOTHING we haven't seen, many times.

But if you have a question you can't find an answer for, ASK first in the Q&A forum before you screw up your phone. Those of us who have gone through it multiple times can help! You really don't want to 9008 brick your awesome phone... There's some actions even TWRP can't help you recover from. :rolleyes: