yashsingh1/xdaforums huggingface dataset:
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] omino:
I used the following process, after reading the various posts in this thread

1) Connect phone to PC with a USB cable
2) Put the phone in bootloader mode (coming from stock it is automatically on slot A. To get the current slot execute: fastboot getvar all)
3) Boot TWRP "fastboot boot twrp.img" (use the file name on your PC for the TWRP img file)
4) Flash copy-partitions-AB.zip
5) Reboot to booloader then boot TWRP (see step 3)
6) Format data in TWRP
7) Wipe /system, /data, & cache (not internal storage)
8) Flash lineage zip
9) Flash twrp installer zip
10) Reboot to recovery (slot automatically changes to B on reboot - B was set to active during LOS install; slot A is set to inactive so it doesn't boot anymore)
11) Flash opengapps zip (use the arm64 version)
12) Reboot to booloader then execute: fastboot -w (this will wipe your userdata partition)
13) Flash magisk zip (only if you want root)
14) Reboot to system
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] weaponG:
Given your process above, if I don't want opengapps or magisk, I can safely stop at step 9 and have a functional phone with LineageOS right? Also, for OTA updates of LineageOS, I am assuming we can just update through the GUI in LineageOS and all will be fine (or is there more that is involved)?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] omino:
I have not tried it myself, but I would probably just skip the steps related to opengapps and magisk to prevent those packages from being installed.

You can surely get the OTA updates from within LineageOS, using the Updater. The only issue I encountered (once) is that the active slot does not get automatically changed upon reboot, so you have to manually change it yourself as explained in a previous post ("fastboot getvar current-slot" and "fastboot --set-active=[slot]"). That appears to be fixed in the December 10 nightly build.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] weaponG:
I just ordered the Moto G7 from B&H Photo Video. They are currently selling it for 179.99 USD. And now the agonizing (but exciting) wait begins...
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] omino:
Does anyone knows how to pass CTS profile check? Basic integrity passes, but CTS profile check is set to false.

I have the MagiskHide Props Config add on installed and I could verify that the current fingerprint is set to the same one as in the stock rom PPOS29.114-134-4:

motorola/river/river:9/PPOS29.114-134-4/fe214:user/release-keys
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] a977427:
Hello, is there configurable LED notifications?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] droidsometimes:
Are you using printslist? Did you supply a matching security patch date?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] omino:
I did not make any changes yet. MagiskHide Props Config does not have a fingerprint for the Moto G7 in the fingerprint list, so I guess the currently configured fingerprint is set up by lineageos.

Should the security patch date match the one in the stock rom that the fingerprint refers to or the current security patch date as reported in the lineageos system settings?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Phalanx7621:
yes there are.

---------- Post added at 03:38 PM ---------- Previous post was at 03:33 PM ----------

I'd like to post this important piece of information for anyone else who may be experiencing the same thing I did --it is VITALLY important not to skip one of the last steps, booting into bootloader and using fastboot to "fastboot -w" to wipe userdata. This is crucial, you can't do it within TWRP or it won't work correctly/do the same thing. You MUST boot into bootloader, and use fastboot -w or Lineage simply won't boot. It will bootloop over and over again, it took me an hour of flashing to figure this out. I assumed (mistakenly) that the fastboot -w was a last effort to make sure we had wiped, so that we didn't run into problems later and assume it was the ROM. Basically, I thought they were trying to make it idiot proof by having us wipe it twice. Once in the process in TWRP of formatting the userdata partition, and again after, using the fastboot command -w. I was wrong. lol. So don't be like me and overthink things, just follow the instructions EXACTLY as indicated, and it'll work. Also, thanks to the team for making this official, and for the device support. Been running Cyanogenmod (now I run Lineage ;p ) since my Motorola Atrix days haha.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] weaponG:
So, if I don't need opengapps or magisk, the steps below will provide for a proper install of LineageOS?

1) Connect phone to PC with a USB cable

2) Put the phone in bootloader mode (coming from stock it is automatically on slot A. To get the current slot execute: fastboot getvar all)

3) Boot TWRP "fastboot boot twrp.img" (use the file name on your PC for the TWRP img file)

4) Flash copy-partitions-AB.zip

5) Reboot to booloader then boot TWRP (see step 3)

6) Format data in TWRP

7) Wipe /system, /data, & cache (not internal storage)

8) Flash lineage zip

9) Flash twrp installer zip

10) Reboot to recovery (slot automatically changes to B on reboot - B was set to active during LOS install; slot A is set to inactive so it doesn't boot anymore)

11) Flash opengapps zip (use the arm64 version)

12) Reboot to booloader then execute: fastboot -w (this will wipe your userdata partition)

13) Flash magisk zip (only if you want root)

14) Reboot to system
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] a977427:
Do you have this phone? Where is these settings? I cant find these options. I want LED notification for incoming email.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Phalanx7621:
Yep. Here are the settings. I'm not sure I don't use them, you might be able to set it for your email. I know it automatically does it for all notifications.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Phalanx7621:
Well, if you already have TWRP you don't need to boot from it you can just boot into recovery. Flashing the a b partition file is only required one time. so you can start from step 6 if you already have TWRP and you've already flash the a b partition file.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] weaponG:
Thanks for the reply, I don't have TWRP and am actually expecting to get the phone itself today . I just wanted to make sure that I have the steps down correctly so that I can: (1) document a clear and efficient installation of LineageOS on the device; and (2) provide such documentation via this thread.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] crypysmoker:
Weird problem with updater

Is no one else having the same problem I am with updater?

I update, reboot and phone is encrypted again and twrp is no longer installed.

Every single time.

Not using it after this last time but just wondering if I'm the only person having this happen.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Phalanx7621:
I haven't tried to use the updated yet I'm on 12/12. I'll try on my next day off on Saturday.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] gerchla:
Hi all - does somebody know if this rom can also be applied to Moto G7 Plus?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] weaponG:
After Unlocking Bootloader, Current Slot is B

I received the Moto G7 last night and made the mistake of connecting it to WiFi after turning it on for the first time. This prompted it to install the latest Motorola update putting the phone to version PPOS29.114-16-5-2. (This update may have changed the current slot to slot "b"). After the update, I powered off the phone. This morning, I was I was successfully able to unlock the bootloader. Immediately after doing so, I check the current slot, it shows up as "b". If I switch to slot "a", the phone will not boot and gives me an error message with two options: Try Again or Factory Reset. However, if I switch my current slot back to slot "b", I am able to boot into the phone without any issues. So now, I have an unlocked bootloader, an unbootable slot "a" and bootable slot "b".

How should I continue? With "b" as my current slot which actually boots, am I safe to run the copy-partitions.zip?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] HueyT:
I would download latest stock rom for your variant from lolinet mirrors and manually install latest rom to fix this problem
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] weaponG:
So, I should install the stock rom on slot "a" using adb sideload? Then ensure that active slot is "a" and perform copypartitions.zip? I haven't dealt with a dual slot phone and want to make sure that I don't mess things up. Detailed instructions are greatly appreciated.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] cou94114:
According to the "other" group, the high level steps to update LOS (dirty flash) are

put phone in fastboot mode

boot twrp (fastboot boot twrp-3.3.1-2-river.img) (this is the current version, if a newer twrp is released adjust accordingly)

flash the new lineageOS zip file

flash twrp installer zip file

reboot twrp (you will be running twrp from the device, not your PC)

flash opengapps (or your fav apps cluster)

flash magisk zip file

flash disable_dm-verity_forceencrypt zip file (my data partition is unencrypted and flashing this zip keeps it unencrypted)

reboot system

I tried using the LineageOS updater one time and had issues. I had to blankflash my phone to recover functionality. I joined the "other" group to get the blankflash file and learned these steps for dirty flash (update) LineageOS. This process has worked for me several times. I'm finally getting comfortable with the ROM installation and update procedures on an A/B partition device.

Recovery is part of the boot partition. When you update LOS, it overwrites the boot partition. This is why you don't have TWRP and magisk.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Phalanx7621:
Whatever slot you are on when you flash Lineage it flashes it to the other slot.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] weaponG:
I wrote this post below earlier. Does this mean that I can go ahead and copy-paritions and flash lineageos now?

Originally Posted by weaponG:

I received the Moto G7 last night and made the mistake of connecting it to WiFi after turning it on for the first time. This prompted it to install the latest Motorola update putting the phone to version PPOS29.114-16-5-2. (This update may have changed the current slot to slot "b"). After the update, I powered off the phone. This morning, I was I was successfully able to unlock the bootloader. Immediately after doing so, I check the current slot, it shows up as "b". If I switch to slot "a", the phone will not boot and gives me an error message with two options: Try Again or Factory Reset. However, if I switch my current slot back to slot "b", I am able to boot into the phone without any issues. So now, I have an unlocked bootloader, an unbootable slot "a" and bootable slot "b".

How should I continue? With "b" as my current slot which actually boots, am I safe to run the copy-partitions.zip?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] weaponG:
Thank you, all. I was able to successfully install LineageOS. My phone was using Slot B as the slot for the OEM Android OS. Slot A was empty. I kept Slot B as the current slot and then followed this process precisely.

1) Connect phone to PC with a USB cable

2) Put the phone in bootloader mode (coming from stock it is automatically on slot A B. To get the current slot execute: fastboot getvar all)

3) Boot TWRP "fastboot boot twrp.img" (use the file name on your PC for the TWRP img file)

4) Flash copy-partitions-AB.zip

5) Reboot to booloader then boot TWRP (see step 3)

6) Format data in TWRP

7) Wipe /system, /data, & cache (not internal storage)

8) Flash lineage zip

9) Flash twrp installer zip

10) Reboot to recovery (slot automatically changes to B on reboot - B was set to active during LOS install; slot A is set to inactive so it doesn't boot anymore)

11) Reboot to booloader then execute: fastboot -w (this will wipe your userdata partition)

12) Reboot to system
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] gerchla:
I didn't flash LineageOS yet, but I'm a bit confused by the dual slots, too.

From my understanding, the OEM Android is installed on one slot, and LineageOS could be/is flashed to the other one. So there should always be a backup OS, in case the flashing goes wrong. Why can there still be any hardbricks?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] erfanoabdi:
Problem is Motorola kept slot B(inactive slot) blank

Without any required bootloader firmwares for boot, and flashing to lineage on blank slot and trying to boot from it bricks device
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Phalanx7621:
The moral of the story is, the first thing you should do before you do anything else is to flash copy partitions zip in TWRP.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] SgtDork:
Copy that, over . . .
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] gerchla:
Would we be able to "flash" the content of the first/second slot to sd card to have a backup of the OEM android (for example if you want to go back to stock for any reasons)?

---------- Post added at 06:46 AM ---------- Previous post was at 06:37 AM ----------

Did I get it right that the problem waa NOT the latest Motorola update but rather slot mixup?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] uuriroad:
Just wanted to verify if I have something wrong prior to submitting a bug report or if this expected behavior for an official build (I'd hope not).

Awhile ago I downloaded and installed lineage-16.0-20191210-nightly-river-signed.zip without any issues. Last week while going through settings/configs and getting read to install a nightly updated I noticed that my build number contains "userdebug" in the build number string: lineage_river-userdebug.

Tonight I installed a nightly update and rebooted while connected to my computer and got a notification on the phone that it was in debug mode and to tap to disable. I went in and disabled Android debugging, rebooted and android debugging was enabled automatically again. Disconnecting my phone from my computer, disabling android debugging and rebooting reproduces this as well.

Anyone else with this issue by chance? My initial LineageOS download was from the official download.lineageos.org link for the Moto G7.

LineageOS Version: 16.0-20191226-NIGHTLY-river

Kernal version: 4.9.203-perf+ #1 Thu Dec 26 19:31:19 UTC 2019

Build date: Thu Dec 26 19:22:49 UTC 2019

Build number: lineage_river-userdebug 9 PQ3A.190801.002 de6641b459
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] gerchla:
Quick question: does this ROM also support Moto G7 Plus?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] uuriroad:
It is not. Keep an eye on the G7 Plus unofficial lake build thread. With the base official we'll hopefully see the other versions quickly follow.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] geosnipe:
Hey Folks, I just installed per the guide and now I am in a boot loop. Any suggestions?

"1) Connect phone to PC with a USB cable

2) Put the phone in bootloader mode (coming from stock it is automatically on slot A. To get the current slot execute: fastboot getvar all)

3) Boot TWRP "fastboot boot twrp.img" (use the file name on your PC for the TWRP img file)

4) Flash copy-partitions-AB.zip

5) Reboot to booloader then boot TWRP (see step 3)

6) Format data in TWRP

7) Wipe /system, /data, & cache (not internal storage)

8) Flash lineage zip

9) Flash twrp installer zip

10) Reboot to recovery (slot automatically changes to B on reboot - B was set to active during LOS install; slot A is set to inactive so it doesn't boot anymore)

11) Flash opengapps zip (use the arm64 version)

12) Reboot to booloader then execute: fastboot -w (this will wipe your userdata partition)

13) Flash magisk zip (only if you want root)

14) Reboot to system"

DID NOT WORK FOR ME :(

* I did get back to stock :) but that's not what I want..
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] uuriroad:
The instructions have changed since I ran my install. They previously did not have the copy partitions section of the instructions. I could very well have done it prior when I was going to install the unofficial version but I can't remember. I did not install gapps or root my device during my install.

I doubt I'll be able to help much but have you checked what slot is active prior to running through the install? fastboot getvar all will contain the variable of the active slot.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] fadestyle:
This set of instructions seem to work for any nightly LineageOS install so far:

1. put phone in fastboot mode: adb reboot bootloader

2. boot twrp (fastboot boot twrp-3.3.1-2-river.img) (this is the current version, if a newer twrp is released adjust accordingly)

3. flash (twrp install) new lineageOS zip file

4. flash (twrp install) twrp installer zip (twrp-3.3.1-2-river.zip) file

5. reboot twrp recovery (you will now be running twrp from the device)

6. flash (twrp install) opengapps (or your fav apps cluster)

7. flash (twrp install) magisk zip file

8. reboot.... golden.

I wish someone would update the LineageOS install instructions on the official Lineage site. Those instructions brick your phone every time and thats BS to give someone instructions to brick your phone.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] uuriroad:
Glad you got it sorted out. That is pretty much what the instructions were when I ran my install (what was originally on the lineage site) except I don't believe that I flashed TWRP directly, just booted from to do the install. If I go into recovery now I boot into the Lineage recovery instead of TWRP.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] weaponG:
I am unsure of what the Motorola update did exactly. I took the brand new phone out of the box and connected to WiFi. It began an update from Motorola. Thereafter, I rebooted and began the LOS install process. The current slot was "B". Anytime I tried to switch slots and boot from "A" using fastboot, I ran into an error screen which asked me to either Try Again or Factory Restore the phone. The only slot which worked for me was slot "B". I had to set the slot to "B" using fastboot and then reboot the phone.

---------- Post added at 04:44 PM ---------- Previous post was at 04:42 PM ----------

I am on LOS 16 (December 18, 2019 nightly) and have had issues receiving phone calls (GSM SIM). If I don't reboot the phone daily, I run into the issue of calls going straight to voicemail without even ringing my phone. The caller experiences no rings either from their end is passed directly to voicemail. Is anyone else having this issue?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] SyberHexen:
What carrier?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] weaponG:
My carrier is Ting (using the T-Mobile network). I contacted Ting and they had me enable Airplane Mode, Shutdown the Phone, Power up the phone, and disable Airplane Mode. Ting also re-associated the phone with their towers on their end. I hope that this solves the issue.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] :
i found the above symptoms common when using t-mobile in the US regardless of device (several iphones/ios versions as well as android - stock or lineage).

On lineage with no gapps, a lack of any response is exacerbated. I once misplaced a lineage device (moto but not the g7) at a residence, despite a strong cell signal it did not receive phone calls, sms texts, mms texts, nor did it responds to pings despite still being "connected" to the wifi network. this behavior persisted over a 10+min time span. I don't know how long it would have stayed in a "deep sleep" state as I eventually found it. (it did not register any of the sms/mms texts or even the phone messages for some time after I found it).

HTH
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] weaponG:
Thanks for the above reply. This makes me feel better about the LOS build that is installed on the device as it seems to be a carrier-specific issue.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] mightysween:
Hey, y'all... just picked up a G7. Been away for awhile but I see that we are still having to re-invent the wheel as each device comes along :)

Google Fi isn't working as data connections are denied on Sprint and USCC (T-Mobile is working). Maybe will see about fixing that...
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] SyberHexen:
Welcome to the mix!

Hmm Initial testing with our Fi fixes worked for me on all 3 carriers.

What's your gapps setup like?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] mightysween:
Stock OpenGapps... Fi is working in that the app is trying to switch networks appropriately. Just that there is no data connection on Sprint or USCC. Voice/wifi calling works fine. Same problem bringing up the Moto X4 a couple years ago.

Will log it when I have a chance
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] SyberHexen:
Hmm stock opengapps installs?

phone, messages, contacts, Fi, carrier services, gcs?

Only other thing I can think is download and flash premissiver V4

Might be related to moticcid prop
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] HT123:
turn on data roaming? I had issues with no data connection the first time until i enable data roaming with custom roms?

I had to switch the preferred network type to Global and enable data roaming. I am on Verizon for which is why the Sprint made me thing of that

just a wild ass guess.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] death_jester:
I somehow bricked my device while trying to install this Lineage OS build. Just to clarify my knowledge base, I have previously flashed several other devices. But somehow managed to f*** this up. I followed the updated steps from this thread. First I unlocked my bootloader with the Moto website, etc., then I started TWRP and first thing was to install the "Copy Partitions Zip". I assume this one installs a minimal recovery on both slots, right? Ok anyway, then I flashed TWRP and Lineage. Somehow it didn't boot so I switched slots, and I did some other stuff (it seems I did a mess). Long story short, I'm now in some mode which says "AP Fastboot Flash Mode (Secure)". It looks similar to the standard one, when you press the down + power button. But it is much more rudimentary. There is, e.g., no Android robot in the background. Almost all fastboot commands either return disabled or permission denied:

fastboot boot twrp-3.3.1-0-river.img
downloading 'boot.img'...
OKAY [ 0.778s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.778s

or:

fastboot oem unlock
...
(bootloader) feature disabled
OKAY [ 0.001s]
finished. total time: 0.001s

Any chance I can recover my phone from this state? It also says "oem_locked", even though I unlocked the bootloader before. I also tried the recovery software RSDLite. But to me it seems this one is just using fastboot to reset the partitions, etc. I tried this manually, with a stock firmware image, but no success:

sudo fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.001s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.033s

Any help or suggestion is greatly appreciated.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] death_jester:
Ok I found the solution myself. Before being able to blank flash, a

sudo fastboot oem blankflash

is necessary to get the phone into this qcom mode. After the blank flash I was able to just flash a stock firmware. Thanks anyway. And thank you for the good work on the Lineage port!