Develop Bugs

Running any H930 AOSP ROM on an US998 converted H931

Hi there, I've been struggling with this for the past couple of days and have finally figured out how to reliably get AOSP H930 roms to run on H931's.
The steps are pretty straight forward actually and are taken partially from this post here for the H933: https://forum.xda-developers.com/showpost.php?p=78183349&postcount=2
Needed Files:
H933 KDZ: https://forum.xda-developers.com/lg-v30/development/h933-lg-v30-canada-h933-t3795908
H931 keep twrp: https://forum.xda-developers.com/lg-v30/development/lg-v30-att-h931-20f-rom-t3872926
Steps:
1. Starting with a US998 converted H931 with TWRP, download the H933(20G) KDZ and boot into LGUP. In LGUP choose partition dl and select everything except recovery.
2. After the phone is done flashing it should boot immediately to TWRP.
3. Immediate reboot to recovery then format data, and in advanced wipe choose dalvik, system, data, and cache and wipe that as well.
4. Now flash the H931 zip in TWRP, and dirty flash your AOSP rom of choice and whatever else you need/want (gapps, magisk, etc).
If TWRP decides it doesn't want to flash anything, then choosing wipe->format data, and restarting TWRP until it does.
That should be it! Thanks goes to @Who-Lep who originally figured it out.
If you have any questions please feel free to ask. Also let me know if anything doesn't make sense and I'll try my best to fix it.

Nice write up! And thanks for creating the thread.
I can't take all the credit tho, @losingway chimed with his success using the h933 kdz. I just filled in the blanks and did some troubling shooting and testing.

Who-Lep said:
Nice write up! And thanks for creating the thread.
I can't take all the credit tho, @losingway chimed with his success using the h933 kdz. I just filled in the blanks and did some troubling shooting and testing.
Click to expand...
Click to collapse
Forgot to mention, doing it this way fixed all the issues I was having before. Phone, videos not playing, etc. They're all fixed and I am happily typing this from liquidremix

Jkaspar said:
Forgot to mention, doing it this way fixed all the issues I was having before. Phone, videos not playing, etc. They're all fixed and I am happily typing this from liquidremix
Click to expand...
Click to collapse
Nice, that is awesome news!

You'd better not use zip of us998 20f,just use 20e.
20f will cause some problems soch as sounds

Good job. Thanks for helping others.

losingway said:
You'd better not use zip of us998 20f,just use 20e.
20f will cause some problems soch as sounds
Click to expand...
Click to collapse
Are you sure that applies to the H931 as well? I thought that was just US99820F, and it seems nobody is reporting issues in this thread so far.

ericb982 said:
Are you sure that applies to the H931 as well? I thought that was just US99820F, and it seems nobody is reporting issues in this thread so far.
Click to expand...
Click to collapse
I've flashed a multitude of different ROMs following this process throughout the last day, and haven't had any issues with sound. Just flashing the US998 and not the H931 does cause issues though.

EDIT, this post is confusing, don't worry about anything I've said below.
So I don't know which H931 issues specifically these steps are intended to resolve, but I was having video and sound not playing issues in Pixel Experience 2018-12-27 and US998 20F.
I was on US998 20E with Pixel Experience and not having those issues I just mentioned. I used the TWRP flashable US998 20F zip to upgrade firmware (and reflashed Pixel Experience and magisk before rebooting). The audio and video issues were immediately present. Downgraded back to 20E with the TWRP flashable zip (and reflashed Pixel Experience and magisk before rebooting) and things were working seemingly normally on reboot minus the various known issues that seem to be affecting everyone. Hope this helps someone. The audio and video not playing issues are gone at least.

Malnilion said:
I was on US998 20E with Pixel Experience and having those issues I just mentioned.
I used the TWRP flashable US998 20F zip to downgrade firmware (and reflashed Pixel Experience and magisk before rebooting).
Upgraded back to 20E with the newer TWRP flashable zip
Click to expand...
Click to collapse
Going from US998 20E to US998 20F would be upgrading, not downgrading.
Then going back to US998 20E from US998 20F would be downgrading, not upgrading.
US998 20F (November 2018 security patch, but released in January 2019) is newer firmware with more features, like DTS 3D stereo libs which older US998 20E (September 2018 security patch) does not have.

ChazzMatt said:
Going from 20E to 20F would be upgrading, not downgrading.
Then going back to 20E from 20F would be downgrading, not upgrading.
20F (November 2018 security patch, can but released in January 2019) is newer with more features, like DTS 3D stereo libs which older 20E (September 2018 security patch) does not have.
Click to expand...
Click to collapse
Lol, whoops, sleepy brain alphabet fail. Gonna go back and reverse those to help avoid confusion!
---------- Post added at 08:31 PM ---------- Previous post was at 08:13 PM ----------
It actually looks like US998 20F is a problem for me with Pixel Experience. I think I was actually correct before about the order I flashed the ROM firmwares and wasn't thinking about 20E being the downgrade. To clarify, do the procedures in the OP get sound and video working with AOSP ROMs ultimately with the US998 20F firmware? It appears things work just fine with the H931 20F firmware, so maybe I'll just stick with that for now.

Malnilion said:
PM ----------
It actually looks like US998 20F is a problem for me with Pixel Experience. I think I was actually correct before about the order I flashed the ROM firmwares and wasn't thinking about 20E being the downgrade.
Click to expand...
Click to collapse
It's possible you need the "older" US998 firmware instead of "newer" firmware as a base to flash AOSP custom ROM.
But the recent US998 20F firmware is much better with lots of fixes and even added features than the older US998 20E, if you're just running rooted stock firmware.
US998 20F V30 ThinQ performance update progress
- DTS: X 3D stereo effect function has been added.
- Improved accessibility.
- Improved keyboard performance
- Improved the delay of keyboard input when installing multiple market apps at once.
- Photo display error in some apps since Google's latest security patch has been improved.
- Improved to keep app aspect ratio settings after app updates.
- Improved the phenomenon that fine lines are displayed on some screens when power saving mode is executed.
- Google Security Update has enhanced your phone's security.
Click to expand...
Click to collapse

ChazzMatt said:
It's possible you need the "older" US998 firmware instead of "newer" firmware as a base to flash AOSP custom ROM.
But the recent US998 20F firmware is much better with lots of fixes and even added features than the older US998 20E, if you're just running rooted stock firmware.
Click to expand...
Click to collapse
Yeah, I'm guessing kernel sources will have to be updated in AOSP ROMs for the newer US998 20F firmware.

@Malnilion
I tried it today with just flashing the US998 firmware, and not flashing the H931 and the sound and video were both not working for me. As far as I've found dirty flashing AOSP over the H931 zip is the only way to have it working.

Jkaspar said:
@Malnilion
I tried it today with just flashing the US998 firmware, and not flashing the H931 and the sound and video were both not working for me. As far as I've found dirty flashing AOSP over the H931 zip is the only way to have it working.
Click to expand...
Click to collapse
Sound and video work on top of US998 20E firmware as well. I think we'll just have to wait and see when ROMs incorporate the kernel changes to work with US998 20F. Maybe we can get DTS X support when that happens as well!

@Jkaspar could you clarify step 5 in your write up? It says "repeat step two," which is just "After the phone is done flashing it should boot immediately to TWRP." Does this mean we should let the device reboot to TWRP or does it mean we should proceed to step 3, which is wiping partitions with TWRP?

Do you know if this can be used to install H930 AOSP roms on US998 converted H933 devices? Thank you in advance.

hossein7292 said:
Do you know if this can be used to install H930 AOSP roms on US998 converted H933 devices? Thank you in advance.
Click to expand...
Click to collapse
Some people try to use a similar method,it works on 933,but his phone can't call.

ericb982 said:
@Jkaspar could you clarify step 5 in your write up? It says "repeat step two," which is just "After the phone is done flashing it should boot immediately to TWRP." Does this mean we should let the device reboot to TWRP or does it mean we should proceed to step 3, which is wiping partitions with TWRP?
Click to expand...
Click to collapse
Sorry, I'll edit the post to clarify. It should say let the phone restart and try to boot the US998 zip you just flashed. It will bootloop and you'll need to then return to TWRP. With out doing that I was getting some weird errors with the phone not being able to Mount the cache.

Wait... so all we needed all along was the H933 partition scheme? (I'm assuming that's the main reason why we needed to flash the H933 KDZ to begin with.) If that's so, then why do we need to flash the US998 20e/20f when we could just go to the H931 20f zip and then dirty flash an AOSP ROM? (I'm asking for clarification)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[GUIDE] How to convert US998 20H Oreo to H930 30B Pie

HTML:
I am NOT responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about breaking your
phone after do this mod.
YOU are choosing to make these modifications, and if you
point the finger at me for messing up your device, I will laugh at you.
Ok guys, so after waiting for too long for Pie to land on US998, i decided to figure out how to do this myself.
Please read the disclaimer above before doing this
If you dont understand any term like using LGUP, where to get KDZ file, what is download mode, and how to get out of a brick situation then i suggest you dont try doing this
So far, i can only test this method on 2 device with US998 and LS998 converted US998 on a GSM network outside US, I cant confirm if this will work with CDMA network or any other carrier in US. So if it work for you, then good, if it doesnt work, try to partition DL back to Oreo via the Frankeinstein method
​So here are the step you need.
Prerequisite: Us998 20H kdz and H930 30B kdz, working LG up for Pie (attached file), and backup all your data first
Make sure you are on a completely clean Us998 20H base, i recommend refurbish to us998 20H
When on US998 20H, get to download mode via power off + vol up while plugin your PC
Open your LG up, select partition DL and select the H930 30B kdz
Select all partition except the following 3: modem, xbl, xbl 2, click Ok and accept partition changes
Let it complete and restart, if you stuck on LG logo, try reboot again, it will boot completely
Result: H930 30B on a US998 with working network and stuff working (testing on GSM network outside US only, cant confirm Vowifi, VoLTE or any other netwrok stuff.)
Bonus: if you go back to oreo and cant boot any AOSP rom (AOSP rom still do not suport PIE) you can try following my other guide here
Edit: to get back to us998, you need to partition DL to Us998 nougat then do a master reset, let it boot, then get to downlaod mode and do a refurbish to 20h or any other oreo us998

Interesting.
H930 and US998 radios are incompatible -- so I see you are keeping US998 radios.
There's nothing about LG Pie I'm dying to get. You flash this and stuff like Anxious V30 Magisk module no longer works (until the VS996 gets Pie and then she'll update her module).
I'll wait for US998 Pie, but thanks for the efforts.

ChazzMatt said:
H930 and US998 radios are incompatible, so I see you are keeping US998 radios.
There's nothing about LG Pie I'm dying to get. You flash this and stuff like Anxious V30 Magisk module no longer works (until the VS996 gets Pie and then she'll update her module). I'll wait for US998 Pie, but thanks for the efforts.
Click to expand...
Click to collapse
Not only this is an update to Pie, it also is a method to convert us998 to h930 in the future, if this method is working for many people

Mrxyzl said:
Not only this is an update to Pie, it also a method to convert us998 to h930 in the future, if this method is working for many people
Click to expand...
Click to collapse
OK, I'm genuinely asking, I'm not trying to be a smart aleck. But except for getting Pie a couple of weeks early, what other advantage to converting US998 to H930 firmware? Especially since users are not REALLY converting everything -- they are keeping the US998 radios by necessity.
Is there something about H930 firmware which is better than US998 (which is fairly bloat free)? Status bar icons, some other difference? I've never used H930 myself. I'm just asking, because in the past people who wanted to convert like H930DS to US998 or vice versa were interested in the RADIOs. They wanted the OTHER variants' bands -- the way that H931/H933/VS996/LS998/AS998 actually BECOMES a US998 (with all radio frequencies) with Frankenstein.
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/13/(17)/20/25/66
H930
2G GSM: 900 / 1800 / 1900
3G (HSPA): 850 / 900 / 1900 / 2100
4G LTE: 1/2/3/4/5/8/12/17/20/28/38
And if you say, the advantage is just to try something different -- that's OK. I just want to understand.

ChazzMatt said:
OK, I'm genuinely asking, I'm not trying to be a smart aleck. But except for getting Pie a couple of weeks early, what else is any advantage to converting US998 to H930 firmware? Especially since you are not REALLY converting everything -- you are keeping the US998 radios by necessity.
Is there something about H930 firmware which is better than US998 (which is fairly bloat free)? Status bar icons, some other difference? I've never used H930 myself. I'm just asking, because in the past people who wanted to convert like H930DS to US998 or vice versa were interested in the RADIOs. They wanted the OTHER variants' bands -- the way that H931/H933/VS996/LS998/AS998 actually BECOMES a US998 (with all radio frequencies) with Frankenstein.
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/13/(17)/20/25/66
Click to expand...
Click to collapse
Sorry if i mean to offend you or anything.
Well US998 outside of US have very weak signal (around 2-3 bar) in my country. So yes change to H930 improve signal (not sure how it work). And yes US998 lately download a buch of random app (like candy crush etc...) (Mobile service manager in system app is at fault) so moving to H930 to have a clean system is better
Edit: Mobile service manager is the LG default app, not some random app installed

Mrxyzl said:
Sorry if i mean to offend you or anything.
Click to expand...
Click to collapse
There's no offense, I'm just trying to understand what advantage H930 firmware would have if you are keeping the same US998 radios. Yes, I see Pie for people who don't want to wait another couple of weeks for US998 Pie.... But after everyone gets Pie, would there be any reason? I was genuinely asking.
They both have fastboot flash commands, so no difference there.
Mrxyzl said:
Well US998 outside of US have very weak signal (around 2-3 bar) in my country. So yes change to H930 improve signal (not sure how it work).
Click to expand...
Click to collapse
Hmmmm.... if you are keeping the US998 radios, how would the H930 firmware magnify US998 radio signals? I'm never saying never, because I've seen strange things before that defy logical explanation, so that's interesting if true. There are also people who claim Canada H933 has "stronger" signals than US998, even though they have almost identical frequencies. I would be interested in seeing some more data on that or more people's testimonials.
Mrxyzl said:
And yes US998 lately download a buch of random app (like candy crush etc...) (Mobile service manager in system app is at fault) so moving to H930 to have a clean system is better
Click to expand...
Click to collapse
Candy crush? OK, here's where you'll get offended. Between me, 4 family members and 5 different friends who have US998 phone (10 people), that's never happened to any of us. It just means you downloaded some malware app or something. Could happen again on H930.

ChazzMatt said:
Candy crush? OK, here's where you'll get offended. Between me, 4 family members and 5 different friends who have US998 phone (10 people), that's never happened to any of us. It just means you downloaded some malware app or something. Could happen again on H930.
Click to expand...
Click to collapse
No idea, but it happens on everytime i do a refurbished (app download while i'm doing the setup) so basically, it has a very low low chance to be malware since i do a refurbished flash via KDZ. and i check the app download these and it is an LG app Mobile sevice manager, you can read about it here

Qualcomm 9008 mode for my US998 though I did it differently a bit (removed these 3 files from seadersn H930_30B zip and then clean flashed it via TWRP). Waiting on Ebay from Moldova to see if they can fix it for $35 USD .
Thus, flash with caution as I'm no noob but there are risks in cross-flashing. Looking back, I'd just wait but what's the fun in that? I'm running rooted Pixel 2 XL on Q beta 6 which is AWESOMELY smooth and fast so I'm in no rush. If your phone is critical to you and not just a $150 toy (I bought my V30 with mildly burnt screen noticeable on white background only on ebay), don't do it
P.S. Getting to Qualcomm 9008 mode is not easy: black screen, not dected by PC at all. Had to open phone up, unhook battery cable, and short 9008 test point (same as V20's test point) with wire.

HueyT said:
Qualcomm 9008 mode for my US998 though I did it differently a bit (removed these 3 files from seadersn H930_30B zip and then clean flashed it via TWRP). Waiting on Ebay from Moldova to see if they can fix it for $35 USD .
Thus, flash with caution as I'm no noob but there are risks in cross-flashing. Looking back, I'd just wait but what's the fun in that? I'm running rooted Pixel 2 XL on Q beta 6 which is AWESOMELY smooth and fast so I'm in no rush. If your phone is critical to you and not just a $150 toy (I bought my V30 with mildly burnt screen noticeable on white background only on ebay), don't do it
P.S. Getting to Qualcomm 9008 mode is not easy: black screen, not dected by PC at all. Had to open phone up, unhook battery cable, and short 9008 test point (same as V20's test point) with wire.
Click to expand...
Click to collapse
Well sad to hear that. I never mess with the zip file since they have very different script to point to which partiton to flash which img. So your case maybe flashing the wrong img to wrong partiton which is very very bad
Edit: or maybe the zip erase those partition and dont flash anything there

By converting US998 to H930, would it be possible to receive updates from international centre for H930? Or there would be no updates like other models.

Jahanzaibawan said:
By converting US998 to H930, would it be possible to receive updates from international centre for H930? Or there would be no updates like other models.
Click to expand...
Click to collapse
1) Anytime you convert a phone, you will NEVER receive inferior partial image OTA updates any more. You will have to flash full image KDZ for updates or use TWRP-flashable zips.
I prefer to flash my own updates from full image KDZ. If something goes wrong, I have resources at hand to fix, whereas with partial image OTA you do not.
2) Also, with this method, you have to be careful to NEVER flash over the partitions the instructions say should be excluded. Flashing H930 to US998 is how WTF creator @TxanMoe bricked his phone. Yes, XDA Dev @runningnak3d helped him recover, but if you brick your phone you won't have a good day.
So, flashing future updates with H930 Pie, you would want to be in total control of which partitions you flash, which you have no control with when using OTA updates (even if it were possible). If you receive an OTA update notice on H930, do NOT take it!

https://www.ebay.com/itm/Remote-Ser...e=STRK:MEBIDX:IT&_trksid=p2060353.m2749.l2649
I used his service personally for my Qualcomm 9008 US998_20H while crossflashing H930_30b as too impatient to wait for PIE. $37 with tax. Teamviewer used to remotely install drivers and software for JTAG writting using Octopus box remotely. Worked great. I highly recommend this guy, Tennolee. He even have all the KDZ at his disposal and up to date. He asked via messaging, which software: I said 20H so he did it. Took 15 min. max.

I've converted my V30 US998 (who was before Canadian H933) to the H930 and everything it's fine for now. I've the H930 30b with my 4G! But, I needed to enter the APN for Bell Mobility manually to have my 4G :good:
EDIT: My phone was with the US998 28a beta when I've convert it

Can confirm that this works on my H933 converted to US998, data also. Can't check on VoLTE or any network stuff though since I do not use them.

Stuck on boot
I did exactly what's in the guide. Everything seemed to work, but after flashing the H93030b_00_OPEN_EU_OP_0704.kdz got stuck on LG boot logo.
I tried to reboot by pressing Vol up+Power for 8 sec and it did reboot but stuck again.
I left "to boot" for a while, then I couldn't even reboot it. Now I can't just watch that stupid LG logo :crying:
Any idea what to do?
Btw, I wanted this conversion for a while now, I just haven't find a proper guide so far. I knew there is some small difference between the US998 and H930 and you just seemed to give the answer (modem,xbl,xbl2 stuff).
I needed the H930 version because of other, European languages.
Hope there is some way to get it back..
Thx

TiborAdam said:
I did exactly what's in the guide. Everything seemed to work, but after flashing the H93030b_00_OPEN_EU_OP_0704.kdz got stuck on LG boot logo.
I tried to reboot by pressing Vol up+Power for 8 sec and it did reboot but stuck again.
I left "to boot" for a while, then I couldn't even reboot it. Now I can't just watch that stupid LG logo :crying:
Any idea what to do?
Btw, I wanted this conversion for a while now, I just haven't find a proper guide so far. I knew there is some small difference between the US998 and H930 and you just seemed to give the answer (modem,xbl,xbl2 stuff).
I needed the H930 version because of other, European languages.
Hope there is some way to get it back..
Thx
Click to expand...
Click to collapse
What is your model? Try a hard reset

Mrxyzl said:
What is your model? Try a hard reset
Click to expand...
Click to collapse
OK. I managed to get into download mode again and load an older rom, then root it, then update to 20h again and go to 30b and everything seem to be working perfectly.

TiborAdam said:
OK. I managed to get into download mode again and load an older rom, then root it, then update to 20h again and go to 30b and everything seem to be working perfectly.
Click to expand...
Click to collapse
Ok glad for you. Thats why i said it need to refurbish to a completly clean 20h

This is so neat! I was wondering if this would ever be possible. h930 is almost always the most up-to-date model, from what I've seen
Hmm, wonder if I can do it without losing twrp.. Never done an lgup refurbish. Maybe I can do a fullwipe on twrp, flash 20h twrp zip from there, then do the kdz as per instruction, but omit recovery as well? Might report back here o.o;
Edit: Well, I'm running pie, but I no longer have TWRP, even though I didn't flash those with the kdz XD

Ruvaldak said:
This is so neat! I was wondering if this would ever be possible. h930 is almost always the most up-to-date model, from what I've seen
Hmm, wonder if I can do it without losing twrp.. Never done an lgup refurbish. Maybe I can do a fullwipe on twrp, flash 20h twrp zip from there, then do the kdz as per instruction, but omit recovery as well? Might report back here o.o;
Edit: Well, I'm running pie, but I no longer have TWRP, even though I didn't flash those with the kdz XD
Click to expand...
Click to collapse
Re-flash TWRP in bootloader mode using fastboot commands

Stock Pie to AOSP/Lineage Pie Fix

Stock Pie to AOSP/Lineage Oreo/Pie Fix
Does not work on the H932 as tested by Mattgyver here
Use at your own risk on a h930
After testing for a month I am confident that I have found a way to "reset" the phone after flashing Stock Pie, fixing the many problems outlined here:
* ALSO do NOT update to LG stock Pie yet if you wish to run LOS-16 "Pie" custom ROMs -- at least for now. See REASON HERE. Stock Pie update conflicts with LOS-16 Pie, even if you downgrade back to stock Oreo. After stock Pie update, your phone has been permanently changed/degraded when going back to Oreo for custom ROMs. Using Permissive kernel can overcome some of those issues, but you have been warned.
Click to expand...
Click to collapse
By following the steps below users will be able to flash AOSP/Lineage roms after having already installed stock Pie, doing so without any of the issues caused by the "permanent" changes left by stock Pie. AOSP/Lineage roms will work as if stock pie was never even installed.
INSTRUCTIONS
1. Follow the instructions here to flash the nougat rom I made over your current rom
2. Reinstall TWRP if it was wiped out on reboot (if TWRP remains for you, please let me know in the thread so I can remove this step. It stayed for me at least.)
3. Follow the instructions here to flash Stock Oreo over Nougat
4. After that you should be free to flash your favorite Pie AOSP/Lineage rom without issue! Youtube/camera/flashlight/lag should all be fixed!
I tested this on a US998, but I believe it should work for the H930 as well. If anyone tries the fix with an H930 please let me know in the thread.

^I'm_With_Stupid said:
Stock Pie to AOSP/Lineage Oreo/Pie Fix
After testing for a month I am confident that I have found a way to "reset" the phone after flashing Stock Pie, fixing the many problems outlined here:
By following the steps below users will be able to flash AOSP/Lineage roms after having already installed stock Pie, doing so without any of the issues caused by the "permanent" changes left by stock Pie. AOSP/Lineage roms will work as if stock pie was never even installed.
INSTRUCTIONS
1. Follow the instructions here to flash the nougat rom I made over your current rom
2. Reinstall TWRP if it was wiped out on reboot (if TWRP remains for you, please let me know in the thread so I can remove this step. It stayed for me at least.)
3. Follow the instructions here to flash Stock Oreo over Nougat
4. After that you should be free to flash your favorite Pie AOSP/Lineage rom without issue! Youtube/camera/flashlight/lag should all be fixed!
I tested this on a US998, but I believe it should work for the H930 as well. If anyone tries the fix with an H930 please let me know in the thread.
Click to expand...
Click to collapse
So now camera and flashlight work for you on enforcing on pie aosp roms?

tech_infinity said:
So now camera and flashlight work for you on enforcing on pie aosp roms?
Click to expand...
Click to collapse
Yes. I've been using a pie Lineage rom (Liquid Remix) as my daily driver for the past month and no problems whatsoever. Completely stable.

interesting, just asking do we need to use only the zips? or kdz files will also work?

^I'm_With_Stupid said:
Yes. I've been using a pie Lineage rom (Liquid Remix) as my daily driver for the past month and no problems whatsoever. Completely stable.
Click to expand...
Click to collapse
Why have you linked h930 oreo ROM though?
H930 ROM over us998 bricked @HueyT or someone else's phone it I remember correctly

tech_infinity said:
Why have you linked h930 oreo ROM though?
H930 ROM over us998 bricked @HueyT or someone else's phone it I remember correctly
Click to expand...
Click to collapse
I have a US998 and it worked for me. I believe this rom was confirmed working for the US998 even before I flashed it.

So, you're basically just saying to flash back to stock nougat, then stock oreo, then flash some los-16 ROMs? Hmm.... I wonder if it'll work on an H932... I'll need a spare phone before I can try. can't even joke about bricking the only phone I have, when I'm 24/7 tech support.

mattgyver said:
So, you're basically just saying to flash back to stock nougat, then stock oreo, then flash some los-16 ROMs? Hmm.... I wonder if it'll work on an H932... I'll need a spare phone before I can try. can't even joke about bricking the only phone I have, when I'm 24/7 tech support.
Click to expand...
Click to collapse
@mattgyver, please do not use these files on your T-mobile H932. But yes you could possibly use this method. (see last paragraph, the rest of this is explainer.)
Let me explain about the method.
Starting with this thread, written in August 2019...
[GUIDE] Booting AOSP after stock Pie (US998 tested only)
What had been discussed informally, a set of instructions were made for US998 (including other North American variants converted to US998) to revert back from LG stock Pie while fixing any/most degradation.
Many had had upgraded to Pie to use the newer "bleeding edge" LOS-17/Android 10 ROMs or just see if Pie was any better than last stock Oreo (it's not). The LOS-17 ROMs had tons of bugs at the time, and many people immediately retreated back to stock Oreo then found they couldn't install LOS-16 ROMs anymore, and that even on stock Oreo camera/flashlight didn't work -- as well as other sensors. The "temporary" upgrade to stock Pie had made "permanent" changes. People then experimented and found they could use "permissive" kernels to mitigate some of those handicaps -- but they had to even use those custom kernels on stock Oreo and stuff didn't work as well as before.
This is why I have warnings to this day in all KDZ threads to NOT update to stock Pie without understanding the consequences.
However, we found that for North American variants (excluding T-mobile H932 because it has different RSA encryption), they could Partition DL to Canada H933 Nougat and that would re-set the clock in a way. Then flash back to US998 firmware. Canada H933 has different partition system than the other North American variants and is more difficult to work with in some aspects -- but in this case works like rough sandpaper scrubbing clean.
But even that guide above was not perfect. People would partition DL to H933 Nougat but could only come back to US998 20e -- which is right before the DTS libs were introduced and portrait selfie mode was given, as well as a bunch of other features. US998 20f, 20g, 20h (especially 20h) are the gold standard.
US009 20f had these log changes alone:
- DTS: X 3D stereo effect function has been added.
- New Always On Display options
- Selfie camera portrait mode
- Improved accessibility.
- Improved keyboard performance
- Improved the delay of keyboard input when installing multiple market apps at once.
- Photo display error in some apps since Google's latest security patch has been improved.
- Improved to keep app aspect ratio settings after app updates.
- Improved the phenomenon that fine lines are displayed on some screens when power saving mode is executed.
- Google Security Update has enhanced your phone's security.
And that's not counting US998 20g and US998 20h.
But after updating to stock Pie, that is all people could do.
Also, using Partition DL they were flashing all partitions EXCEPT for "recovery" which was supposed to keep TWRP. But people make mistakes and sometimes wiped out TWRP or couldn't correctly perform the "hardware button dance" needed to get back into TWRP and wiped everything. Then they had to use WTF Section 6 to re-install TWRP, etc. (which as you know doesn't work with T-mobile H932, as it doesn't have fastboot flash commands).
______
What @^I'm_With_Stupid has done to improve this is create an H933 Nougat TWRP-flashable zip. So, users are not having to flash via LGUP Partition DL. They flash to Nougat H933 via "ROM", then flash to Oreo TWRP flashable zip. (For US998 20h, you should still flash 20e, 20f, 20g, 20h all back to back to get all the incremental changes. You should also make sure you are on Magisk 18.x for the Oreo TWRP flashable zips.)
______
While this H933 Canada Nougat "scrubbing" method has been confirmed to work on North American variants (but cannot work on T-mobile H932 due to different RSA encryption), I'm concerned about the H930 variants using this. If it works, OK. But the instructions clearly link to H930 Oreo, whereas I would have linked to US998 Oreo. US998 is proven, but H930 is not (even for the original Partition DL guide I linked above) and @^I'm_With_Stupid who wrote this has US998:
^I'm_With_Stupid said:
I tested this on a US998, but I believe it should work for the H930 as well. If anyone tries the fix with an H930 please let me know in the thread.
Click to expand...
Click to collapse
I thank him for his immense contribution, and I am in no way criticizing him! This H933 Nougat TWRP flashable zip will be valuable for people who wish to "start clean".
I am curious if it indeed works for H930. I normally urge people NOT to flash stock H930 variant firmware over North American variant firmware, and vice versa -- as modems are not compatible and you can't really "Frankenstein" them (no full conversion). But maybe in this case it's a necessary temporary stage. I don't know.
________
Where the method would work for T-mobile H932 -- but you may mess up -- would be basically going back to the beginning. Partition DL back to T-mobile H932 Nougat 10d -- but leave off Recovery partitions. Theoretically you would still have TWRP. You would then have to use "hardware button dance" to get back to TWRP, and then you could flash the T-mobile H932 20s Oreo TWRP-flashable zip (stock ROM). While flashing back to T-mobile H932 Nougat is not quite the same as flashing a completely different model, it's all you can do on T-mobile H932. And people have found that flashing back to Nougat -- even on their own variant -- does make changes. In fact, in the US998 Pie thread, one of the suggestions to successfully flash that very wonky KDZ is to Refurbish back to US998 Nougat first, THEN use Update mode to flash Pie KDZ.

ChazzMatt said:
@mattgyver, please do not use these files on your T-mobile H932.
Click to expand...
Click to collapse
:laugh: :silly: Come on, @ChazzMatt. Why wouldn't a US998 file work on my H932 :silly: You know I'm not just a typical user
I pulled the stock nougat and oreo files for the H932. Just figuring out which tmobile phone to buy as a spare in case I brick this. I need the 600mhz support. There are dead spots where I work, and I knew the second they got band 71 running because I had service everywhere.
Even still, I haven't really needed to worry about los. stock pie actually hasn't been terrible. I got used to it, which was surprising. I will try the method, just to see if it's possible. Like I said, just need a fallback device, in case something catastrophically fails!

mattgyver said:
:laugh: :silly: Come on, @ChazzMatt. Why wouldn't a US998 file (or any other North American V30 variant file EXCEPT for T-mobile H932) work on my H932 :silly: You know I'm not just a typical user
I pulled the stock nougat and oreo files for the H932. Just figuring out which tmobile phone to buy as a spare in case I brick this. I need the 600mhz support. There are dead spots where I work, and I knew the second they got band 71 running because I had service everywhere.
Even still, I haven't really needed to worry about los. stock pie actually hasn't been terrible. I got used to it, which was surprising. I will try the method, just to see if it's possible. Like I said, just need a fallback device, in case something catastrophically fails!
Click to expand...
Click to collapse
No, you aren't typical user! But other people not as knowledgeable as you will read this thread perhaps months from now. When I answer a question, I try to also talk to general audience, many of whom may not even own this phone yet.
For LTE band 71 on T-Mobile, you can always buy the 128GB T-mobile H932 V30+
($180 right now, which is decent price for "renewed" 128GB H932 V30+ -- which was limited edition offered by T-mobile during the 2017 Holidays. A lot of people don't realize the T-mobile H932 V30+ even exists...)
or buy another 64GB T-mobile H932 V30: (less than $100)

Flashed this on my open market us998. Rebooted to recovery to make sure I hadn't lost TWRP, which I hadn't. Rebooted to system. Booted up fine, but couldn't get past setup keeps force closing. Button danced back to TWRP, and reinstalled the nougat zip, and bootlooped on LG screen. Back to recovery, and installed 20e,f, g, and h. Restored back up. Any thoughts on setup force closing?

Got the itch to flash something (that wouldn't send me to jail )
Confirming that this method DOES NOT work with TMo's H932.
Wiped everything on my phone, flashed the H932 Nougat FullStock zip then the H932 Oreo FullStock zip, both by @weakNPCdotCom
Once I got back to Oreo, I flashed los16. Camera crashes on open. Flashlight doesn't ever activate.
I at least wanted to try. Was definitely hoping it would work, if for nothing else, more up to date security patches. Oh well ..

mattgyver said:
Got the itch to flash something (that wouldn't send me to jail )
Confirming that this method DOES NOT work with TMo's H932.
Wiped everything on my phone, flashed the Nougat FullStock zip then the Oreo FullStock zip, both by @weakNPCdotCom
Once I got back to Oreo, I flashed los16. Camera crashes on open. Flashlight doesn't ever activate.
I at least wanted to try. Was definitely hoping it would work, if for nothing else, more up to date security patches. Oh well ..
Click to expand...
Click to collapse
Guess then you'll have to use aosp pie ROMs on permissive only for camera to work

tech_infinity said:
Guess then you'll have to use aosp pie ROMs on permissive only for camera to work
Click to expand...
Click to collapse
Back on stock pie for now. I only tried so that all would know if that procedure might work for the h932. I'd rather my device break than anyone else's

mattgyver said:
Back on stock pie for now. I only tried so that all would know if that procedure might work for the h932. I'd rather my device break than anyone else's
Click to expand...
Click to collapse
Hehe you make a good point. Especially because a less experienced user is more likely to break his phone if he tried, so good thing you tried it.
Thanks for trying and sharing

@^I'm_With_Stupid - can you add to the OP that this doesn't work on the H932. Granted, no one ever reads the OP of most threads.

Ballroomblitz said:
Flashed this on my open market us998. Rebooted to recovery to make sure I hadn't lost TWRP, which I hadn't. Rebooted to system. Booted up fine, but couldn't get past setup keeps force closing. Button danced back to TWRP, and reinstalled the nougat zip, and bootlooped on LG screen. Back to recovery, and installed 20e,f, g, and h. Restored back up. Any thoughts on setup force closing?
Click to expand...
Click to collapse
Sorry for taking so long to reply. Did you wipe your device before doing everything? Nougat zip should not bootloop no matter what. Also, you might not be able to restore the entire backup if it's a twrp backup. That might bring back the same problems as before. You might have to try and backup and restore another way, like using titanium.
mattgyver said:
@^I'm_With_Stupid - can you add to the OP that this doesn't work on the H932. Granted, no one ever reads the OP of most threads.
Click to expand...
Click to collapse
Done! Thanks for testing.

This does NOT work for h930!!!

HEADS UP: US998 "Frankenstein" Auto Updates

I didn't see this mentioned anywhere, however, my "Frankenstein" H3931 phone running US998 Oreo tried to auto update last night and I found it boot looping this morning. Luckily I keep regular backups of my phone and was able to quickly restore.
Just giving a quick heads up because I didn't see this posted.

Oh god, can't wait until @ChazzMatt refutes this as anything other than operator error...

betam4x said:
I didn't see this mentioned anywhere, however, my "Frankenstein" H3931 phone running US998 Oreo tried to auto update last night and I found it boot looping this morning. Luckily I keep regular backups of my phone and was able to quickly restore.
Just giving a quick heads up because I didn't see this posted.
Click to expand...
Click to collapse
I'm curious what update it was trying to download and install?
Your H931no longer has AT&T firmware. (Are you an AT&T customer?)
* AT&T device can't receive OTA update without original firmware and AT&T SIM card.
* Converted USS98 device can't receive OTA updates as they don't have native US998 IMEI.
Unless you have a very strange phone. So, did it tell you what update it was trying to install?
Where we've seen this happen -- and is easily explained -- are AT&T H931 converted to US998 for Bootloader Unlock and TWRP, then flashed back to H931 TWRP flashable zip (with AT&T SIMs inside). Or same thing with VS996, flashed back to VS996 TWRP flashable zip. But those have enough stock firmware to trigger the OTA as well as valid IMEI for those carrier updates.
But you should turn off the auto update function. And freeze those updater files in Titanium Backup.
___
P.S. I have native US998 on rooted stock Oreo 20h, my wife as well as my mom have native US998 on stock Oreo 20h, and we've never been offered OTA updates on Oreo -- even though we have correct IMEI. Last one I was offered was back on Nougat over a year ago.

Nothing strange, that is why I am raising a heads up. I am running the US998 20b firmware on an H931; the H931 is being used on a Verizon MVNO. I do not know which update it downloaded (it was stuck at the boot screen), but I know that it updated, because my system partition had evidence of changes. Unfortunately I did not think to look closer, because I overslept thanks to my alarm not going off. If it happens again I will let everyone know. I did not disable software updates.
Note that this was not malware or anything, as I only use a few mainstream apps and root is disabled, though the bootloader is unlocked.

betam4x said:
Nothing strange, that is why I am raising a heads up. I am running the US998 20b firmware on an H931; the H931 is being used on a Verizon MVNO. I do not know which update it downloaded (it was stuck at the boot screen), but I know that it updated, because my system partition had evidence of changes.
Click to expand...
Click to collapse
You shouldn't still be on USS98 20b. The universe is telling you to update to US998 20h (last Oreo), so you can have DTS 3D Stereo, tons of fixes and camera improvements...
US998 20f had all these changes below just by itself!
US998 20f change log:
- DTS: X 3D stereo effect function has been added.
- New Always On Display options
- Selfie camera portrait mode
- Improved accessibility.
- Improved keyboard performance
- Improved the delay of keyboard input when installing multiple market apps at once.
- Photo display error in some apps since Google's latest security patch has been improved.
- Improved to keep app aspect ratio settings after app updates.
- Improved the phenomenon that fine lines are displayed on some screens when power saving mode is executed.
- Google Security Update has enhanced your phone's security.