[US998][STOCK][OREO]LG V30 US998 US99820h_00_0318.KDZ

[cllark1]

18.0 is fine.


Read the next paragraph:



Again 18.0 is fine. It's just your can't have any Magisk over 18.x for these Oreo TWRP flashable zips

I just read that the V30 US988 is now officially LG supported bootloader unlockable . I am guessing this would be preferred method if true.
https://www.getdroidtips.com/unlock-lg-v30-us998-bootloader/

 

[ChazzMatt]

I just read that the V30 US988 is now officially LG supported bootloader unlockable . I am guessing this would be preferred method if true.
https://www.getdroidtips.com/unlock-lg-v30-us998-bootloader/

Don't believe such trash. See screenshot of authorized LG Devices. Do you see any US998 on that list? That's the LG website crap website that doesn't know what they are talking about.

LG Bootloader Unlock Code is NOT the preferred method for US998 and it's NOT officially supported by LG.

Back in 2018, I did Bootloader Unlocked my authentic 64GB Open Market US998 through LG website, but you have to know how to "hack" the drop-down menu for LG website. LG added the IMEI for one Open Market US998 variant to their database and NEVER even posted on their website. They never released an announcement.

We found out about it. It's old news from 2018.

The 64GB Open Market US998 sold by AUTHORIZED 3rd party retailers like B&H Photo is the ONLY US998 you can Bootloader Unlock using that method. You have to provide IMEI and Device ID to LG to PROVE you have that device or you will NOT receive the unlock code.

It cannot be U.S. Cellular US998, it cannot be ANY US998 V30+ or V30S, it cannot be US998 converted from another model. Do you understand?

Whereas WTF handles ALL ALL ALL V30/V30+/V30S in the world EXCEPT for T-Mobile H932.

 

[cllark1]

Don't believe such trash. . See screenshot of.

It's NOT the preferred method and it's NOT officially supported.

I Bootloader Unlocked my 64GB Open Market US998 through LG website, but you have to know how to "hack" the drop-down menu.

The 64GB Open Market US998 sold by AUTHORIZED 3rd party retailers like B&H Photo is the ONLY US998 you can Bootloader Unlock using that method. You have to provide IMEI and Device ID to LG to PROVE your have that device.

It cannot be U.S. Cellular, it cannot be V30+, it cannot be converted from another model. Do you understand?

Whereas WTF handles ALL ALL ALL V30/V30+/V30S in the world EXCEPT for T-Mobile H932.

Thanks for the response .Coming from Droid Turbo to
LG is kind of confusing using US998 for more than one model. I have been reading over rooting instructions looks more complicated than rooting a Quark.

 

[ChazzMatt]

Thanks for the response .Coming from Droid Turbo to
LG is kind of confusing using US998 for more than one model. I have been reading over rooting instructions looks more complicated than rooting a Quark.

I owned three Quarks. Fantastic phone. BHB27 kept them alive. Changed his username a couple years ago, but that's how I know him.

USS98 is among the easiest, as it already has fastboot flash commands.

I have both 64GB V30 and 128GB V30+ USS98. I have both authentic Open Market US998 V30/V30+ as well as converted LS998 V30+ to US998 V30+.

Simple for LG V30 "JOAN" (code name like Quark). You just TEMPORARILY flash US998 to early OREO 20a or 20b firmware, then run the "WTF" fake Bootloader Unlock Code.

Then you install TWRP, reformat internal memory, flash two root related files to disable LG crap, and install Magisk last.

Then you can update to newer firmware.

Read the WTF INSTRUCTIONS in web browser, not an app. Print them out of you can.

It's a decision tree -- if you have this variant, do this. If you have that variant, do that. There's two dozen V30 variants around the world. So that's why the Instructions look complicated. They're not. By Section 5 EVERYONE is now at the same starting line...

* Section 5 is actual Bootloader Unlock
* Section 6 is TWRP and root
* Section 7 is Troubleshooting Tips

 

[xahova]

If you plug the phone into PC while in TWRP, it acts like a thumb drive/flash drive. You can drag files from PC to phone. They may end up in the basement/root folder of the phone internal memory. Drag 20e, 20f, 20g, 20h and Magisk 18.1 to your phone and reflash them all back to back, then reboot.

this didn't work.

after it failed, I reflashed TWRP from the bootloader and tried to do everything in step seven again, but now Magisk gives me ERROR: 1. I dunno if dm verity or root check disabler would do that though.

I can't seem to fix that magisk error. Even using ADB to reflash a new downloaded copy of TWRP.img doesn't work. Using a new copy of magisk 18.0 doesn't work either. I feel very dumb and stuck.

Edit for clarity.

 

[xahova]

this didn't work.

after it failed, I reflashed TWRP from the bootloader and tried to do everything in step seven again, but now Magisk gives me ERROR: 1. I dunno if dm verity or root check disabler would do that though.

I can't seem to fix that magisk error. Even using ADB to reflash a new downloaded copy of TWRP.img doesn't work. Using a new copy of magisk 18.0 doesn't work either. I feel very dumb and stuck.

Edit for clarity.

Progress! I used LGUP to flash 20b using download mode. Bootloader is already unlocked and I have a copy of android that works again. I can do steps 6 and 7 but correct this time.

 

[mon0theist]

Just checking in, still chugging along on rooted 30b, have there been any more Pie updates (especially TWRP-flashable ones )? Or did the blobs ever get updated/fixed so that LineageOS can be flashed without having to go back to Oreo? I saw the post in Q&A that there will be no official Android 10 release which doesn't surprise me but I'd like to stretch this phone out as long as possible with LineageOS. Thanks in advance!

EDIT: Just realized I posted this in the wrong thread sorry lol

 

[damadikaz]

It is stated in the thread that I have to flash 20e zip, then 20f zip, 20g zip, 20h zip back-to-back when I just unlocked bootloader from downgrading method. Does it only applies to TWRP flashables only? I mean is it fine if I just flash 20h KDZ right after 20a?

I flashed 20h KDZ over 20a, but i still can't boot LOS16. what did I do wrong?
======
EDIT: My device is US998 V30+. I use the H930 build in the LOS thread.

 

[PNT5V]

I'm in 10c. Am I able to flash straight to 20h or do I need to flash 10d then 20a then 20h, or just 10d to 20h?
I don't care about unlock stuff
And also, I am trying to flash Pie. If I get stuck at logo, can I easily hold the power button to turn off and easily go to Download Mode to flash Oreo, or if not, is there any combined button to go to Download Mode, or let the battery drain for the logo to disable and then access, or simply smash it?
And if I am able to access to Download Mode, do I have to flash 20h and then 20a, or go straight to 20a, in case I really need to do unlock bootloader

 

[ChazzMatt]

I'm in 10c. Am I able to flash straight to 20h or do I need to flash 10d then 20a then 20h, or just 10d to 20h?
I don't care about unlock stuff
And also, I am trying to flash Pie. If I get stuck at logo, can I easily hold the power button to turn off and easily go to Download Mode to flash Oreo, or if not, is there any combined button to go to Download Mode, or let the battery drain for the logo to disable and then access, or simply smash it?
And if I am able to access to Download Mode, do I have to flash 20h and then 20a, or go straight to 20a, in case I really need to do unlock bootloader

If you are flashing KDZ, which is full image, you can go straight from Nougat 10c to whatever you want. You don't need to flash other in between.

 

[TPMJB]

On topic, I extracted the modem from the 20h build for use in Pie. My Pie build of Havoc is flawless so far except for one, minor glitch. For some reason when I used this modem, my fingerprint reader started acting weird. I have to touch the reader just right for it to register my fingerprint.

Truly strange.

 

[larciel]

I'm having trouble installing xposed framework and device ID changer on Pie so I'm moving back to Oreo.

US998 from Pie to Oreo 20e is best way?

It says to install Magisk v18.x on OREO TWRP files. Can I update to latest magisk v21 after that?

what'd be best way to install xposed framework on Oreo?

~~~~~~~~~~~~~~~~~~~~~
just flashed 20e and magisk v18.1 . Magisk is not installed!?. I flashed Magisk after 20e, reboot into recovery and flashed again just in case.

 

[ChazzMatt]

I'm having trouble installing xposed framework and device ID changer on Pie so I'm moving back to Oreo.

US998 from Pie to Oreo 20e is best way?

It says to install Magisk v18.x on OREO TWRP files. Can I update to latest magisk v21 after that?

what'd be best way to install xposed framework on Oreo?

~~~~~~~~~~~~~~~~~~~~~
just flashed 20e and magisk v18.1 . Magisk is not installed!?. I flashed Magisk after 20e, reboot into recovery and flashed again just in case.

Need to install Magisk 18.x before flashing any of the TWRP flashable zips.

 

[larciel]

Need to install Magisk 18.x before flashing any of the TWRP flashable zips.

thx Chazz.

Just flashed v19 I had and it worked.

xposed oTOH is a pain to get working...

 

[mpicasso]

On topic, I extracted the modem from the 20h build for use in Pie. My Pie build of Havoc is flawless so far except for one, minor glitch. For some reason when I used this modem, my fingerprint reader started acting weird. I have to touch the reader just right for it to register my fingerprint.

Truly strange.

Did the modem from 20H fix the problem? Back on 20H, stock, trying to decide if I want to stay, go back to Havoc, or upgrade to 10. Preference would be to go back to Havoc, Pie version.

 

[TPMJB]

Did the modem from 20H fix the problem? Back on 20H, stock, trying to decide if I want to stay, go back to Havoc, or upgrade to 10. Preference would be to go back to Havoc, Pie version.

I either replied to you or another person in a different thread. I ended up deleting the fingerprint file in the system so it would populate a new one when I installed Havoc. This *should* fix the issue, but I think I screwed it up somewhere because it didn't. If someone can comment on the exact process I'd be appreciative.

It fixed Wifi, but my fingerprint reader is still not as good as it used to be.

 

[mpicasso]

I either replied to you or another person in a different thread. I ended up deleting the fingerprint file in the system so it would populate a new one when I installed Havoc. This *should* fix the issue, but I think I screwed it up somewhere because it didn't. If someone can comment on the exact process I'd be appreciative.

It fixed Wifi, but my fingerprint reader is still not as good as it used to be.

What was going on with your WiFI? The only Havoc-Pie “concern” I had (definitely no problems) was the fingerprint and how long it took for my phone to respond, if it actually did.

Even with the fingerprint reader causing frustrations, considering what is currently available, I will deal with my V30 for a little while longer. OnePlus 7Pro is still going for $500+, S8/S9/Note 9, all have their typical Samsung issues; only other option for me is the Pixel 2 or 3, as the 4 has no fingerprint. Amazing how well this phone still runs, this far out (probably should go knock on some wood or at least hop on Swappa and get looking for another one!!!).

 

[TPMJB]

What was going on with your WiFI? The only Havoc-Pie “concern” I had (definitely no problems) was the fingerprint and how long it took for my phone to respond, if it actually did.

Even with the fingerprint reader causing frustrations, considering what is currently available, I will deal with my V30 for a little while longer. OnePlus 7Pro is still going for $500+, S8/S9/Note 9, all have their typical Samsung issues; only other option for me is the Pixel 2 or 3, as the 4 has no fingerprint. Amazing how well this phone still runs, this far out (probably should go knock on some wood or at least hop on Swappa and get looking for another one!!!).

Oh, that was very early in our Android 10 development and I couldn't figure out how to get wifi working. Simply flashing the 20H modem fixed it.

OnePlus refuses to put in either an SD slot, headphone jack, or both (I forget) so that's gonna be a no from me, dawg. Same with any "Google" phones.

I'm looking into upgrading to the V50 or G8, as root is veeeeeery close with both phones.

With fingerprint, someone else posted the "fix" in a reply to me. I haven't tried it so I don't know if it works: https://xdaforums.com/mi-5x/how-to/rooted-fix-fingerprint-upgrade-to-t3897423

Edit: Does not fix it for me

 

[mpicasso]

OnePlus refuses to put in either an SD slot, headphone jack, or both (I forget) so that's gonna be a no from me, dawg. Same with any "Google" phones.

I'm looking into upgrading to the V50 or G8, as root is veeeeeery close with both phones.

Yes, the OnePlus lost headphone jack after 6. Not sure they have ever had SD card, as I have not always religiously followed. But most of these phones are pushing 128 to 256GB, so for me, SD card is not as important. And for headphones, not using anything spectacular with my phone (Sony WH-1000MX3’s or B&W PX7’s) so if I migrate away from LG’s DAC, will be looking at this BT badboy.

https://www.whathifi.com/reviews/audiolab-m-dac-nano

Honestly, my problem has been the lack of development and though I realize some has been due to a lack of root/locked bootloaders, there are some phones that get absolutely NO LOVE (will never forget my HTC Inspire...)!!! Before I even consider pulling the trigger, XDA/Telegram are the 1st places I look, to see how they are progressing. I have neither the time, nor patience, to learn how to do what most of these developers are able to do, and though thankful, will bypass a perfectly good phone that does not have an AOSP-based ROM.

 

[TPMJB]

Yes, the OnePlus lost headphone jack after 6. Not sure they have ever had SD card, as I have not always religiously followed. But most of these phones are pushing 128 to 256GB, so for me, SD card is not as important. And for headphones, not using anything spectacular with my phone (Sony WH-1000MX3’s or B&W PX7’s) so if I migrate away from LG’s DAC, will be looking at this BT badboy.

https://www.whathifi.com/reviews/audiolab-m-dac-nano

Honestly, my problem has been the lack of development and though I realize some has been due to a lack of root/locked bootloaders, there are some phones that get absolutely NO LOVE (will never forget my HTC Inspire...)!!! Before I even consider pulling the trigger, XDA/Telegram are the 1st places I look, to see how they are progressing. I have neither the time, nor patience, to learn how to do what most of these developers are able to do, and though thankful, will bypass a perfectly good phone that does not have an AOSP-based ROM.

SD is very important to me, as I had the terrible Google Nexus 5X that decided to just die on me one day. My storage was encrypted. There was no way to get my data. I used the freezer trick several times and got it to boot long enough to pull my necessary data. Never again will I buy a phone where the company is removing features to save money.

We're not Apple users.