[LG V30 Questions & Answers] ChazzMatt:
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 [MENTION=3167089]runningnak3d[/MENTION] 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. :rolleyes:

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.

________

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.