Database Info

Question TWRP and LineageOS for OP9

Hi!
I've been trying to find TWRP and LineageOS files for OP9 without success. Both redirect to OP9pro repositories.
For instance:
× TWRP: the OP9 page links to OP9pro download mirror
× TWRP: the OP9 page links to OP9pro XDA support thread
× LineageOS: OP9 seems to be a supported device however, oddly enough, the OP9 repository is completely empty while the OP9pro repository seems quite active
Am I missing anything?
Can I assume OP9pro material can be safely used on OP9, too?
Or is OP9 in some way special and there is a lack of interest in developing for this particular phone?
Thanks in advance.

I can only speak from experience, TWRP is the same for both, although right now it is for Android 11 and the OP9 has received Android 12, it doesn't work with that version properly yet. Either way you can test it by yourself without doing anything permanent by using
Code:
fastboot boot recovery.img
As for Lineage, it seems for the OnePlus 9 they only store the latest version, but it should still be fine, most probably OnePlus 9 Pro roms would work on the OP9 thanks to the hardware similarities, but could have some issues with some more specific hardware such as the camera, I wouldn't recommend it unless otherwise stated by the developers.

The first official build for the OP9 is now available. I recommend you use that instead of the OP9pro builds if you wish to avoid hardware-specific issues.

andr01dfr3ak said:
The first official build for the OP9 is now available. I recommend you use that instead of the OP9pro builds if you wish to avoid hardware-specific issues.
Click to expand...
Click to collapse
but , like OP said, the build for TWRP OP9 on teamwins site actually just links to the pro build. noticed the same issue and contacted teamwin as it doesnt respond once loaded. At least Nebrassy's version booted and let you do some things 9except decrypt the partitons)

I don't really know anything about TWRP for the OP9, since I don't use it. I just know about official LineageOS builds for the OP9.

I know it's been awhile, have you had any luck?

Firmware partitions question???

i've never flashed firmware partitions before on my other 2 moto devices, i understand having read the install of lineage that this step is req'd for this model.
i'll be using the lineage recovery to install the rom flash, this is the method ive done before. My question is once i sideload the firmware partitions, will this automatically asign which partion the rom will be written too or do i have to tell it which one, im understanding that it will be either A or B partition??
I'd like to wipe/erase as much of the stock rom off the phone, remove everything and then flash the operating rom to a clean phone. Am i understanding this correctly or missing anything? Is there anything that i need or should know or do when at this step? any help/advice would be greatly appreciated.
This is a brand new phone out of the box, is there other ways that any of you would approach this phone to totally wipe it, i'm hoping that ill get the android 11 update immediatley over ota, i understand that i will have to go through intial setup, to get to unlocking the bootloader, wish i didnt have to do that, also i dont believe kiev has an official android 12 oem/factory rom but lineage has 19.1, im thinking install 18.1 and then later reflash android 12 when it comes out. Im talking to much.... any advice be great. TIA

First things first, know your device. Is it an XT2113-2 RETUS variant or something else? As long as the bootloader can be unlocked, it seems any kiev (qualcom) variant should work with lineageos - just best to know what you started with in the event you need to ask for assistance or you want to revert back to stock.
My suggestion assuming you are starting from a new phone out of the box with the plan of putting official lineageos (either 18.1 - android 11 or 19.1 - android 12) on it:
Have the phone ota update to the most recent stock firmware. For XT2113-2 RETUS at the time of this post, this is android 11 version RZKS31.Q3-45-16-8-3 released 2022.06.30. Lineageos currently uses the binary blobs from this version. I suspect having the latest stock radios and bootloader on your device will result in fewer issues and may likely make your life easier later.
After updating to the most current stock version, request the bootloader unlock key from the moto www site. You may need to wait 24-72 hours or longer before the phone will allow unlocking. Leave the phone on, connected to your (primary) carrier, and use your carrier data (i.e. not wifi) during this time.
After updating to the most current stock version, put all the sims in the phone for the carriers you plan to use and let the phone provision the carriers (I've read this can only be done on stock firmware - switching carriers without having done this step apparently requires going back to stock). Test that you can swap sims and use the phone as you need to (e.g. wifi calling, try visual voice mail, try 5 G, etc).
Unlock the bootloader. Be sure to leave the oem unlocking toggle to allow after unlocking the bootloader.
Most important: when coming from stock (either now or in the future), follow the instructions on the lineageos www site. In particular, flash the copy-partitions.zip following the sequence described in the lineageos instructions. Don't worry about the A/B partitions for now, the device will take care of itself. You only need to flash the copy-partions.zip when comming from stock (either now or if you reflash stock in the future and then want to go back to lineageos).
Flash official linageos 18.1, android 11 (not 19.1- android 12). 19.1 is the newest version; however it may have issues. 18.1 works great (for me) and it will likely be easier for you to check if everthing is working as you expect. Upgrade (via ota) to lineageos 19.1 in a month or two.
Updating official lineageos via ota, the device will flash to the appropriate A or B partition. You should not need to do anything unless there is an issue.
I'd like to wipe/erase as much of the stock rom off the phone ...
Click to expand...
Click to collapse
Following the lineageos installation instructions will accomplish that.
Good luck.

notmyrealhandle, thanks for your time and reply, perfect write, i understood everything you said. i never thought of doing ota via data as opposed to wifi, thanks. perfect​

Official AOSP for Huawei (stanford) - LeaOS-PHH (android 13 version)

{
"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"
}
​LeaOS is a project which based on AOSP with trebledroid patches.
This build includes settings parameters for Huawei STF as well as several evolutions:
Offline charging
AGPS Supl20
SafetyNet
GCam for kirin
Installation
Download system file : "LeaOS-A13-20230224-iceows-stf.img.xz" (without google apps) or "LeaOS-A13-20230224-iceows-google-stf.img.xz" (google apps version)
Extract img file
Flash system image : fastboot flash system <drag system.img here>
Boot into recovery: power + vol+ while NOT connected to pc
Factory reset
Reboot to System and setup with android assistant
Enjoy !!!
Source Code:
https://github.com/Iceows
ROM OS Version: Android 13.0
ROM Kernel: Stock kernel
ROM Firmware Required: EMUI 9.1
Based On: Google AOSP + TrebleDroid patches
Support Group
Channel update

reserved

drm/widevine.zip patches for ab is not needed to flash?

I didn't have time to look if it was necessary. The patch is only needed if the version of emui9 you are using has a preavs partition. You can see it if you capture a logcat log with adb. If so I would make a drm patch with the correct version of the drm files for stf-l09

I have finally had the chance to fully implement it, and I'm here to give you the feedback!
Generally speaking, it can be considered a stable build and can be used on your main device. However, there's always room for improvement and the following areas should be revised:
1- The included "Android System WebView" is too old to work, rendering synchronizing with Google accounts impossible. The workaround is easy, however, as the updated versions can be downloaded from the Play store. The same applies to: "Phone", "Contacts", "Messaging" and "Browser" apps.
2- The "Search" box in the Home screen is impossible to remove.
3- The "Navigation bar inverse" option in "Phh Treble Settings -> Misc features" doesn't work, even after re-selecting navbar mode, as specified.
4- The "Adaptive Brightness" option results in more brightness than needed, where it has to be manually lowered. The cause might be related to incorrect readings from the phone's sensors, on the software side.
5- Not a problem, but rather a suggestion: More customizations in general, and in the "Status bar" specifically, can make the ROM more appealing.
Additionally, the instructions above for flashing the ROM are good enough, but it's worth adding that the bootloader of the target phone has to be unlocked first The instructions to achieve that are likely included in the "Honor 9 Guides, News, & Discussion" forum.
Keep up the great work

Barrytoo said:
I have finally had the chance to fully implement it, and I'm here to give you the feedback!
Generally speaking, it can be considered a stable build and can be used on your main device. However, there's always room for improvement and the following areas should be revised:
1- The included "Android System WebView" is too old to work, rendering synchronizing with Google accounts impossible. The workaround is easy, however, as the updated versions can be downloaded from the Play store. The same applies to: "Phone", "Contacts", "Messaging" and "Browser" apps.
2- The "Search" box in the Home screen is impossible to remove.
3- The "Navigation bar inverse" option in "Phh Treble Settings -> Misc features" doesn't work, even after re-selecting navbar mode, as specified.
4- The "Adaptive Brightness" option results in more brightness than needed, where it has to be manually lowered. The cause might be related to incorrect readings from the phone's sensors, on the software side.
5- Not a problem, but rather a suggestion: More customizations in general, and in the "Status bar" specifically, can make the ROM more appealing.
Additionally, the instructions above for flashing the ROM are good enough, but it's worth adding that the bootloader of the target phone has to be unlocked first The instructions to achieve that are likely included in the "Honor 9 Guides, News, & Discussion" forum.
Keep up the great work
Click to expand...
Click to collapse
[UPDATED GUIDE] [BOOTLOADER UNLOCK] Huawei p8 lite 2017 (pra-lx1)
This guide is the only one made and tested personally by me, I am not responsible for malfunctions or any damage to the device, carefully read every single step and everything will be successful [ATTENTION]: Before proceeding, save all your...
forum.xda-developers.com
This guide worked for me on the huawei p8 lite 2017, and i was looking around because i also have a honor 9, and dc unlocker have support for honor 9 apparently.
I'll be trying the same method of the p8 guide on honor 9 to see if it works. If i remember i'll comeback to give feedback on this

Barrytoo said:
I have finally had the chance to fully implement it, and I'm here to give you the feedback!
Generally speaking, it can be considered a stable build and can be used on your main device. However, there's always room for improvement and the following areas should be revised:
1- The included "Android System WebView" is too old to work, rendering synchronizing with Google accounts impossible. The workaround is easy, however, as the updated versions can be downloaded from the Play store. The same applies to: "Phone", "Contacts", "Messaging" and "Browser" apps.
2- The "Search" box in the Home screen is impossible to remove.
3- The "Navigation bar inverse" option in "Phh Treble Settings -> Misc features" doesn't work, even after re-selecting navbar mode, as specified.
4- The "Adaptive Brightness" option results in more brightness than needed, where it has to be manually lowered. The cause might be related to incorrect readings from the phone's sensors, on the software side.
5- Not a problem, but rather a suggestion: More customizations in general, and in the "Status bar" specifically, can make the ROM more appealing.
Additionally, the instructions above for flashing the ROM are good enough, but it's worth adding that the bootloader of the target phone has to be unlocked first The instructions to achieve that are likely included in the "Honor 9 Guides, News, & Discussion" forum.
Keep up the great work
Click to expand...
Click to collapse
For customisation and remove search bar, just change the launcher

AltairFR said:
For customisation and remove search bar, just change the launcher
Click to expand...
Click to collapse
Yep, that's what I did.
However, the small downside to that is the extra memory usage. Besides that, no launcher really bests the baked-in one in smoothness, but again, that's minor.

neves2k said:
[UPDATED GUIDE] [BOOTLOADER UNLOCK] Huawei p8 lite 2017 (pra-lx1)
This guide is the only one made and tested personally by me, I am not responsible for malfunctions or any damage to the device, carefully read every single step and everything will be successful [ATTENTION]: Before proceeding, save all your...
forum.xda-developers.com
This guide worked for me on the huawei p8 lite 2017, and i was looking around because i also have a honor 9, and dc unlocker have support for honor 9 apparently.
I'll be trying the same method of the p8 guide on honor 9 to see if it works. If i remember i'll comeback to give feedback on this
Click to expand...
Click to collapse
Sadly I still didn't managed to do it... I can't downgrade from android 9 to 8 :/ In the past i had that option, but now it's just gone...
I tried dload method with SDCard, but it fails every time. I guess that dload method only works to upgrade and not to downgrade?
If you have some tips to help me downgrade it let me know please

Hello AltairFR,
I've got a Honor 9 in quite good state, and I wanted to upgrade it to most current version before using it (I'm no real geek, set up and then "never touch a running system" is rather me).
I started with unlocking bootloader with DC-unlocker, successfully.
I installed and used adb and fastboot utils.
Then I attempted to install TWRP according to this manual https://romprovider.com/honor-9-dev-support/
As far as I understand, the trick consists of two parts, 1) proper version of TWRP (not easy to find one for Honor 9!), and 2) patched kernel to avoid restore of stock recovery, so TWRP persists.
Unfortunately I failed. After I performed all the steps, the phone got to a bootloop (booted, restarted, booted, restarted, ...)
That version of TWRP never started, it just showed the logo and hung. Patched kernel was no success either because
stock recovery is back. The only way I can resurrect TWRP is to perform factory reset in stock recovery. Then next start is TWRP, and afterwards again just bootloop and stock recovery.
Then I found and installed a working version of TWRP here https://forum.xda-developers.com/t/twrp-ish-twrp-3-2-1-for-honor-9-running-gsi-8-1-roms.3818442/
Then I attempted Android 10 according to https://theupgradeguide.com/install-android-10-on-honor-9-aosp-gsi-treble-rom-how-to-guide/
This was most successful attempt so far, except it was only installed w/o GApps and Antroid reported "There is an internal problem in your device. Please contact your manufacturer." <- not really useable.
Then I tried your Android 13 build. I installed it the way you recommend (fastboot). I got "Invalid sparse file format at header magi" and something about "device reported max upload size of" about 400MB. Nevertheless, it completed kind of successfully. But this Android never started up. It's starting and then reboots. Both with GApps and without.
I assumed the reason could be that patched Kernel I installed at the beginning. I inspected my versions with "Multi-Tool for Huawei and Honor" and found Firmware version = STF-L09 8.0.0.368(C432) Your prerequisites are
ROM Kernel: Stock kernel​ROM Firmware Required: EMUI 9.1​My EMUI is not reported by "Multi-Tool" at all, although in the video guide it's shown. (Perhaps because I don't have any EMUI at all anymore. As far as I understood, it's a Huawei version of "look-and-feel" on Android).
So now my question, how did you manage to get EMUI 9.1 ?
I searched for stock firmware to restore my phone to at least original state. I found https://huaweistockrom.com/honor-9-stf-l09 which refers to EMUI 9.1 in file name Huawei_Honor_9_STF-L09_9.1.0.210_C43 ... .0.0_R3_EMUI9.1.0_05014NMA_Dload.zip
But the free download site is not available, and it's a bit risky to go for paid one without knowing the archive file contains what it sais.
Hence my question, how did you manage to get your EMUI 9.1 ? My pretty much last hope is, if I get to that version of stock software then your Android 13 build hopefully installs successfully too.
Thank you in advance.

Hello. I think you've complicated yourself. The procedure is much simpler, you just need to flash the right twrp and then install LeaOS. I look on my stf the version of emui that I have. I will answer you later

k0a1a said:
Hello AltairFR,
I've got a Honor 9 in quite good state, and I wanted to upgrade it to most current version before using it (I'm no real geek, set up and then "never touch a running system" is rather me).
I started with unlocking bootloader with DC-unlocker, successfully.
I installed and used adb and fastboot utils.
Then I attempted to install TWRP according to this manual https://romprovider.com/honor-9-dev-support/
As far as I understand, the trick consists of two parts, 1) proper version of TWRP (not easy to find one for Honor 9!), and 2) patched kernel to avoid restore of stock recovery, so TWRP persists.
Unfortunately I failed. After I performed all the steps, the phone got to a bootloop (booted, restarted, booted, restarted, ...)
That version of TWRP never started, it just showed the logo and hung. Patched kernel was no success either because
stock recovery is back. The only way I can resurrect TWRP is to perform factory reset in stock recovery. Then next start is TWRP, and afterwards again just bootloop and stock recovery.
Then I found and installed a working version of TWRP here https://forum.xda-developers.com/t/twrp-ish-twrp-3-2-1-for-honor-9-running-gsi-8-1-roms.3818442/
Then I attempted Android 10 according to https://theupgradeguide.com/install-android-10-on-honor-9-aosp-gsi-treble-rom-how-to-guide/
This was most successful attempt so far, except it was only installed w/o GApps and Antroid reported "There is an internal problem in your device. Please contact your manufacturer." <- not really useable.
Then I tried your Android 13 build. I installed it the way you recommend (fastboot). I got "Invalid sparse file format at header magi" and something about "device reported max upload size of" about 400MB. Nevertheless, it completed kind of successfully. But this Android never started up. It's starting and then reboots. Both with GApps and without.
I assumed the reason could be that patched Kernel I installed at the beginning. I inspected my versions with "Multi-Tool for Huawei and Honor" and found Firmware version = STF-L09 8.0.0.368(C432) Your prerequisites are
ROM Kernel: Stock kernel​ROM Firmware Required: EMUI 9.1​My EMUI is not reported by "Multi-Tool" at all, although in the video guide it's shown. (Perhaps because I don't have any EMUI at all anymore. As far as I understood, it's a Huawei version of "look-and-feel" on Android).
So now my question, how did you manage to get EMUI 9.1 ?
I searched for stock firmware to restore my phone to at least original state. I found https://huaweistockrom.com/honor-9-stf-l09 which refers to EMUI 9.1 in file name Huawei_Honor_9_STF-L09_9.1.0.210_C43 ... .0.0_R3_EMUI9.1.0_05014NMA_Dload.zip
But the free download site is not available, and it's a bit risky to go for paid one without knowing the archive file contains what it sais.
Hence my question, how did you manage to get your EMUI 9.1 ? My pretty much last hope is, if I get to that version of stock software then your Android 13 build hopefully installs successfully too.
Thank you in advance.
Click to expand...
Click to collapse
Can you give me an explanation of how did you managed to unlock the bootloader of our honor 9 please?
For the stock ROM you can find it here for free https://androidhost.ru/

neves2k said:
Can you give me an explanation of how did you managed to unlock the bootloader of our honor 9 please?
Click to expand...
Click to collapse
Here is the way https://romprovider.com/unlock-bootloader-huawei/
I paid 4.31 EUR (4 credits).
> For the stock ROM you can find it here for free https://androidhost.ru/
Thank you, I found the site in the meantime. The latest version there is C432B130 while mine is B368. (Is it the reason why patched Kernel B366 silently failed to install?..)

k0a1a said:
Here is the way https://romprovider.com/unlock-bootloader-huawei/
I paid 4.31 EUR (4 credits).
> For the stock ROM you can find it here for free https://androidhost.ru/
Thank you, I found the site in the meantime. The latest version there is C432B130 while mine is B368. (Is it the reason why patched Kernel B366 silently failed to install?..)
Click to expand...
Click to collapse
For TWRP I will use this twrp :
altairfr-huawei - Browse /TWRP-Recovery at SourceForge.net
sourceforge.net
For stock ROM download a old EMUI 9.1 ROM and update it with hisuite or stock system huawei OTA. Don't flash kernel

AltairFR said:
For TWRP I will use this twrp
Click to expand...
Click to collapse
It worked, thank you.
> For stock ROM download a old EMUI 9.1 ROM and update it with hisuite or stock system huawei OTA. Don't flash kernel
I'm too far away from HiSuite yet.
I managed to start installation of stock firmware from SD card. "Installing EMUI" after 5% progress breaks with "Software install failed, reboot system now" :-/
In TWRP file manager I see a couple of directories were created on SD card [perhaps by installation routine, who else] with "android" in their names, and a couple of files. Just a couple of, not more.

k0a1a said:
It worked, thank you.
> For stock ROM download a old EMUI 9.1 ROM and update it with hisuite or stock system huawei OTA. Don't flash kernel
I'm too far away from HiSuite yet.
I managed to start installation of stock firmware from SD card. "Installing EMUI" after 5% progress breaks with "Software install failed, reboot system now" :-/
Click to expand...
Click to collapse
Do you have tried sevice repair firmware for stf-l09 ?.
You have a post here
Firmware Huawei Honor 9 STF-L09 - Stock service full rom
Update Instructions: Normal update dload/update.app [Main firmware file] Copy required vendor pack Example : [/dload/venrod/update_****_hw_eu.app] after rename the file in update.app Update dload/update.app [Required vendor file] Manually reset...
forum.xda-developers.com

AltairFR said:
Do you have tried sevice repair firmware for stf-l09 ?.
Click to expand...
Click to collapse
Yes I downloaded this one, a .rar achive with dload directory inside:
Service repair firmware [ Скачать / Download ]​File: STF-L09 C432B130 Belgium Germany France Netherlands Portugal Switzerland Spain Italy Austria Bosnia and Herzegovina Poland Denmark Finland Czech Lithuania Romania Serbia Slovenia Hungary Android 7.0 EMUI 5.1​Model: STF-L09​Build Number: C432B130​Vendor: [ hw/eu ]​Country: [ Belgium Germany France Netherlands Portugal Switzerland Spain Italy Austria Bosnia and Herzegovina Poland Denmark Finland Czech Lithuania Romania Serbia Slovenia Hungary ]​

Dis is nice. How bout RROS?

electronic_dream said:
Dis is nice. How bout RROS?
Click to expand...
Click to collapse
Btw have a question about device. I have bootloader unlocked years ago now, i had code but lost in a virus attack. Found that potato method that worked for honor 8. My question is if i flash those service firmwares to oreo or pie bootloader will relock? In 8 it did. Is there any way to flash oreo and pie roms without having to flash firmwares? If the only way is test point to get unlock code i'll do that when battery will die or smth like that.

electronic_dream said:
Btw have a question about device. I have bootloader unlocked years ago now, i had code but lost in a virus attack. Found that potato method that worked for honor 8. My question is if i flash those service firmwares to oreo or pie bootloader will relock? In 8 it did. Is there any way to flash oreo and pie roms without having to flash firmwares? If the only way is test point to get unlock code i'll do that when battery will die or smth like that.
Click to expand...
Click to collapse
And another. I've seen out there harmonyos firmware. That's only chinese? And after flashing that is possible go android again and have twrp etc.?

Question Weird problem on my OnePlus 9: my screen doesn't respond anymore after updating

XDA, we've had a problem here.
Hello everyone!
I'm throwing a bottle into the sea because I don't feel that other people have had the same problem.
I've been on the latest version of Lineage OS 18.1 until now. Having seen the latest version released (20.0) I tried to update my smartphone but the screen became unresponsive (plus there was no network: I'm in France #andr01dfr3ak).
So I used Scrcpy and I could use the phone "normally". I decided to redo a fresh installation from OOS (I had to downgrade) and install the latest version of Lineage OS 19.1 (and wait for the 20.0 to be stable).
So I used MSM and installed an Indian version of OOS on my phone. My screen was responding again. Wanting to put the latest version of OOS in order to reinstall Lineage OS, I have updated OOS via OTA and I had the same problem as before: the screen does not respond anymore but now without any possibility to activate anything in the developer options.
Thus, in summary: I'm currently stuck with (the last?) OOS because the screen that doesn't respond anymore (but it's on and all the buttons work) and I have no possibility to activate anything in the developer options (so no USB debugging etc.).
What do you think I should do?

When you flashed the wrong firmware and wonder why the display doesn't work. The firmware you flashed thinks your phone is the India 9r version and all updates will only give you india stuff now. You must flash EU version of firmware. Link https://github.com/libxzr/FastbootEnhance

[Guide] Stock Verizon G7 (A8) to Rooted LineageOS 20 (A13)

I would just like to say that I was a late comer to this phone and its been a long time since I've had a decent phone I could BL unlock, root, and tweak to my geek hearts content. The information on this particular forum, is so spread out and contradicting, it was a bit disheartening, but I eventually took my Verizon G7 from the original stock fw
G710VM10f to LOS20 without a single issue, and I'd like to just relay the exact steps I took, just in case some one might find it helpful.
So, starting from 100% stock Verizon fw...
***CREATED BACKUPS***​and then:
1. Unlocked Bootlader - I followed the steps exactly, skipping 15-23
2. Crossflashed to g710em30f - LGUP DUAL or any LG UP with Partition DL option is acceptable.
3. Added OrangeFox | LineageOS 20 | MindTheGapps to my SD Card.
4. Rebooted into EDL
5. Used QFIL to flash ofox_metadata.img to boot_a and boot_b
6. Rebooted into OF recovery and did a full format and typed 'YES'.
7. Flashed LineageOS .zip (DO NOT REBOOT)
8. Flashed OrangeFox-R11.0_2.3-Stable-judyln.zip (Reboots to recovery automatically)
9. Flashed MindTheGapps
10. Flashed Magisk (Using OrangeFox built-in method)
11. OrangeFox Menu --> Manage Partitions --> Select Data --> Change FS --> F2FS
12. Reboot
13. PROFIT!
NOTE: I included my rooted boot img file just in case anyone needs it (30G EM FW)
I had to install the Magisk Manager upon completion of setup, but everything else went flawlessly, my service works just fine, all the other weird little issues I've seen people having were absent in my particular experience. So, follow my steps and I would imagine the same would be allowed for others. If there is any questions on specifics, I'd be happy to answer them. Also, its been a while since I've been active here, but hope all is well with everyone and glad to be back.
Good luck!

Sweet!I'm a newbie on the G7 side as well,and have the same Verizon variant!Sad fact,I have AT&T as my carrier and in the states I haven't seen not 1 CFW works with the service due to IMS b.s.!I did manage to switch to the Brightpoint ULM firmware and it works 100%.Good post though!Good to see others are still using the G7!

I'm still running my LG G7 (Verizon, Verizon as the carrier, stock, rooted, debloated, etc) on Android 9.
Nice to see this guide here, just in case I want/need to switch.
You mentioned that your service works fine, which is great to hear:
Some questions:
- Are you on Verizon as a carrier?
- do you have VoLTE working? (I'm assuming 'yes', since you said service is fine.)
I had heard that LineageOS and VoLTE (and anything else that required IMS) was a problem -- has this been fixed? Or, perhaps, was it that your phone was previously activated using the stock ROM?
thanks!

swinokur said:
I'm still running my LG G7 (Verizon, Verizon as the carrier, stock, rooted, debloated, etc) on Android 9.
Nice to see this guide here, just in case I want/need to switch.
You mentioned that your service works fine, which is great to hear:
Some questions:
- Are you on Verizon as a carrier?
- do you have VoLTE working? (I'm assuming 'yes', since you said service is fine.)
I had heard that LineageOS and VoLTE (and anything else that required IMS) was a problem -- has this been fixed? Or, perhaps, was it that your phone was previously activated using the stock ROM?
thanks!
Click to expand...
Click to collapse
I am currently on Verizon, yes, in Michigan if that helps, the service works great, if not better because I opened up a few other bands myself, but I wont be explaining all that here.
As for Volte, as far as I'm aware, Volte will never work on an Android 10+ rom, and that isn't likely to change unfortunately, but I can live without Volte if it means I can run A13 on this bad boy...lol
If you try A13 out. lemme know how it goes and if you thought it was worth it, if you wouldn't mind.
Thanks!

IJoxer said:
I am currently on Verizon, yes, in Michigan if that helps, the service works great, if not better because I opened up a few other bands myself, but I wont be explaining all that here.
As for Volte, as far as I'm aware, Volte will never work on an Android 10+ rom, and that isn't likely to change unfortunately, but I can live without Volte if it means I can run A13 on this bad boy...lol
If you try A13 out. lemme know how it goes and if you thought it was worth it, if you wouldn't mind.
Thanks!
Click to expand...
Click to collapse
I think I'll give it a try later this evening,and see how it goes.I'm thinking VoLTE won't work,but I'm already crossflashed with ULM and IMS is working.I might get lucky?

IJoxer said:
I would just like to say that I was a late comer to this phone and its been a long time since I've had a decent phone I could BL unlock, root, and tweak to my geek hearts content. The information on this particular forum, is so spread out and contradicting, it was a bit disheartening, but I eventually took my Verizon G7 from the original stock fw
G710VM10f to LOS20 without a single issue, and I'd like to just relay the exact steps I took, just in case some one might find it helpful.
So, starting from 100% stock Verizon fw...
***CREATED BACKUPS***​and then:
1. Unlocked Bootlader - I followed the steps exactly, skipping 15-23
2. Crossflashed to g710em30f - LGUP DUAL or any LG UP with Partition DL option is acceptable.
3. Added OrangeFox | LineageOS 20 | MindTheGapps to my SD Card.
4. Rebooted into EDL
5. Used QFIL to flash ofox_metadata.img to boot_a and boot_b
6. Rebooted into OF recovery and did a full format and typed 'YES'.
7. Flashed LineageOS .zip (DO NOT REBOOT)
8. Flashed OrangeFox-R11.0_2.3-Stable-judyln.zip (Reboots to recovery automatically)
9. Flashed MindTheGapps
10. Flashed Magisk (Using OrangeFox built-in method)
11. OrangeFox Menu --> Manage Partitions --> Select Data --> Change FS --> F2FS
12. Reboot
13. PROFIT!
NOTE: I included my rooted boot img file just in case anyone needs it (30G EM FW)
I had to install the Magisk Manager upon completion of setup, but everything else went flawlessly, my service works just fine, all the other weird little issues I've seen people having were absent in my particular experience. So, follow my steps and I would imagine the same would be allowed for others. If there is any questions on specifics, I'd be happy to answer them. Also, its been a while since I've been active here, but hope all is well with everyone and glad to be back.
Good luck!
Click to expand...
Click to collapse
I wanted to add the link for the G710em30f firmware is dead in KDZ downloader.Here's an updated link to the firmware if you want to change it or if anyone else is looking for it?
LG G710EM | LG G7 ThinQ | Version: G710EM30f_00_OPEN_EU_OP_1124 | Firmware for Region: NEU from NEU/NORTHERN EUROPE - Lg-firmwares.com
LG G710EM Download the latest version of firmware | OS Version: Android 10 Q | Firmware version: G710EM30f_00_OPEN_EU_OP_1124 | NEU - Fan club LG-firmwares
lg-firmwares.com

Surgemanxx said:
I think I'll give it a try later this evening,and see how it goes.I'm thinking VoLTE won't work,but I'm already crossflashed with ULM and IMS is working.I might get lucky?
Click to expand...
Click to collapse
I'm sure curious to hear if IMS/VoLTE work on this Lineage rom for you!

swinokur said:
I'm sure curious to hear if IMS/VoLTE work on this Lineage rom for you!
Click to expand...
Click to collapse
It doesn't!I have have already tried it myself.Like he stated in his last post,IMS will probably never work on any custom rom.Not as of yet anyway!

Well the thing is, since Verizon turned off all the 3G service at the end of the year, and @IJoxer was saying above that his service is working fine -- sure seems like there's gotta be IMS working somehow? (It is also highly possible that I don't understand all the details about how voice can be made to work in a post 3G world...)

swinokur said:
Well the thing is, since Verizon turned off all the 3G service at the end of the year, and @IJoxer was saying above that his service is working fine -- sure seems like there's gotta be IMS working somehow? (It is also highly possible that I don't understand all the details about how voice can be made to work in a post 3G world...)
Click to expand...
Click to collapse
The Verizon variant is the easiest to cross flash!No partition erasing needed,and I'm using Brightpoint firmware on my Verizon variant and my carrier is AT&T.Everything works except wifi calling,but I didn't care about that anyway!As goes for CFW's,it's a lost cause at the moment in the states unless some magical trick surfaces.