yashsingh1/xdaforums huggingface dataset:
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] TheShanMan:
About to install for the first time. Any concept of "stable" builds to install vs. nightly which could be seen as bleeding edge with more potential to run into issues? I definitely want my first experience to be a smooth one. The only options for download I see currently are from the 17th, 10th, 3rd, and 27th, all nightlies.

If it's nothing but nightlies, should I start with the oldest since that presumably has had the most usage and I don't see any reports of troubles here?

Related question: Does the updater update you from nightly to nightly? And since the nightlies in actuality appear to be weeklies, does that mean I could use the updater weekly? Or going back to my original question, does the updater have some notion of "stable" builds and those are less frequent, sort of akin to android security updates.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] omino:
I have been using this ROM since it was originally released and I keep it up to date with the weekly releases. I have zero issues with Bluetooth.

In fact, I think this is an awesome ROM. Thanks for keep developing it!
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] TheShanMan:
If I've got magisk installed, is it safer to uninstall magisk prior to letting the OTA install? Is there a better/safer way? I've read that in some cases, magisk survives the OTA, in other cases, a bootloop results, and I think I've also seen that magisk just gets lost. My phone is encrypted if that matters (didn't really intend that, but oh well). I can back up all my stuff with Titanium but if there's any risk of hosing myself by applying OTA's with magisk there, it's probably simple enough to run the magisk uninstaller, then take the OTA, then reinstall magisk. And my assumption is that uninstalling magisk would make the OTA "happy" if it would be "unhappy" with magisk present.

On my old stock + magisk phone, I just avoided OTA's entirely because I didn't want to run the risk of having to set up my phone again and possibly lose something in the process. I'd like to become confident enough in the process that I no longer avoid OTA's. So any input to help me in that regard would be awesome.

FWIW I have LineageOS for microG. Hope it's okay to ask about that variant here. I'm not sure where else I'd ask.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] NTGDeveloper:
I just did my first OTA update today and Magisk+Modules did not carry over to the other slot. They were originally installed on Slot B, but when the device switched to A, it wasn't installed. That goes for all of my boot image mods, like TWRP. It was replaced with the stock LineageOS recovery. I don't know if it will do the same thing on another OTA update that switches the slot again, but we will have to see what happens next week.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] dcybergeek:
Thank you. Your instructions helped me too :) TWRP/ROOT and Lineage all working fine. Slight ROM freeze of 2-3 secs sometimes but bearable to me.

Edit: Device - Moto G7 - XT1962-6
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] dcybergeek:
Hi, by this manual flash you mean. Flash Stock ROM/Copy partitions and then flash Lineage or simply flash Lineage over existing Lineage?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] NTGDeveloper:
I assume that by manual flash they mean flashing Lineage over lineage. Like said before, get the updated Lineage Zip and flash that, along with the other zips in the aforementioned order. You shouldn't need to flash copy partitions again. I'm pretty sure you only need to do that once when you begin flashing custom roms.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] TheShanMan:
Thanks for sharing your experience. I just did my update and had the same experience, except I just boot into twrp from adb rather than permanently installing it though. Updating was more seamless than I feared it could be though... It updated just fine and then I just had to boot into twrp and install the magisk zip. Magisk modules were in tact after reinstalling magisk itself though.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] dcybergeek:
Thanks a lot for this info :)
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Donnie267:
Is anyone aware if there's any work being done to update to 18.1? Would be nice to use a more updated version of android.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] NTGDeveloper:
Pretty sure that LOS Official doesn't announce new versions until the end of March/beginning of April. That's at least what it has been for 16 and 17 the past couple of times. Keep an eye out on https://lineageos.org for any updates.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] castleofiron:
i think my device got bricked, i got through all the steps but when the device started its first boot after whole flash, it restarted to bootloader, and now it says oem_locked.

i tried to run twrp by boot command it says permission denied.

this is what i got from getvar all

what can i do now, there is no os installed, and im stuck at bootloader that does not allow anything, and i tried again to unlock bootloader but it is not working

(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-cf76a327f28-210125
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: 9af1a87f
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-river_retail-cf76a327f28-210125
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
(bootloader) pcb-part-no:
all: listed above
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] TheShanMan:
I just installed the new OTA update, which is my 2nd update. It looks like magisk does persist in a given slot. So when I first installed LOS, I installed magisk. When I installed my first OTA update, I had to install it again (other slot), although my modules persisted. When I installed my second update just now (back to the first slot), I did NOT have to install magisk again. So in summary it seems you have to install magisk once per slot and then you're gtg from then on.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] kdm6389:
Does this ROM support VoLTE?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] SyberHexen:
There are no known issues with VoLTE
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Droid4200:
That's weird, at first I thought 17 had it, then it disappeared, I upgraded to 18, it did get volte, then downgraded back to 17 and the option in setting doesn't have volte. But speaking of volte I need to upgrade to get that back it'd a nice feature to not lose data when my phone rings. Was there an extra step or something I needed to flash to get volte on 17? I haven't reflashed in so long I actually forgot.

Thanks
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] ptn107:
I flashed mine in almost the same way. So far loving LOS 16 w/ pico gapps

1) Put the phone in bootloader mode

1.2) Connect phone to PC with a USB cable.

1.3) In a Command prompt window, run "fastboot getvar all".

1.4) Make slot A the active slot "fastboot set_active a".

Coming from stock it is automatically on slot A. Slot B on my device is blank because I clean flashed motos latest firmware.

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

1.6) check active slot in Reboot menu - set to A

Format data in TWRP

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

2) Flash lineage zip

3) Flash twrp installer zip

3.5) Format data while in TWRP.

4) Reboot to bootloader from TWRP.

5) fastboot -w (this will wipe your userdata partition)

6) Reboot to recovery (TWRP will load on slot B automatically)

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)

6.5) check active slot in Reboot menu - set to A

7) Flash opengapps zip (use the arm64 version)

fastboot -w

7.5) Flash magisk zip (optional, only if you want root)

I left out root this time.

8) Reboot system on slot A

Boot system (no slot choice B is the only active slot).

My only gripe is that updates through the LOS updater menu take like 30 minutes. They finish fine but half an hour is that normal?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] crypysmoker:
Thank you for that.

EDIT- Got it all working and booted up. Your instructions were the only ones that worked. Thank you.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] cou94114:
Excellent information. Thank you for reviewing my documentation and providing corrections.

Does slot b remain the active slot or do updates to LOS load to slot a and it becomes active?

---------- Post added at 07:33 AM ---------- Previous post was at 07:30 AM ----------

It is my understanding that the copy-partitionsAB.zip should be done first. I installed it several weeks ago when we were first alerted to no bootloader on slot b. It is only required one time installation.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] crypysmoker:
Yep. Flash copy partition right after booting twrp, then I rebooted into bootloader then back into twrp. Not sure if that was any extra steps but its been the first thing in 6 months of trying thats booted other than stock.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] reddich:
No, I boot it temporary.

In Europe, they do.

Edit: It is listed in the Wiki, too.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] SyberHexen:
Regarding NFC..

its reported the XT1962-5 European model has NFC
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] ptn107:
Correct. In my case slot B was active until I took a lineage ota. The updater flashes to the opposite slot just like twrp does. So after the 20191125 ota I'm now on slot A. Gapps are preserved.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] crypysmoker:
I apologize. The USA retail variant has no NFC chip.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] floweredup:
I can confirm the UK Amazon G7 (not power or plus) is this model and has NFC.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] SyberHexen:
Have you tried LineageOS yet?

Please let us know if NFC isn't working yet
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] droidsometimes:
According to the fastboot screen this is a 'river XT1962-5 64GB PVT' (bought off Amazon Germany).

I installed LOS last night, and I don't see NFC.

LOS is working great so far though, with OpenGapps Pico and Magisk - thank you very much for porting it to this device! :)
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] cou94114:
When Motorola releases new firmware for river that includes a newer version of bootloader.img and/or NON-HLOS.bin (modem/radio) will we need to re-run the copy-partitions-AB.zip? If I understand the process correctly, the copy-partitions zip would copy the bootloader_a to bootloader_b and we would want the newer bootloader.img on both slots.

Comments? Corrections are greatly appreciated.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] erfanoabdi:
yes but this updates from motorola are not major updates, and since it makes confusion for users to which slot have new firmware and which one is the unactive, maybe running copy partition on wrong slot corrupts the firmwares and in this case flashing OTA updates from motorola stock firmware ends to hard brick (but still unbrickable with blankflash)
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] cou94114:
Once I have installed LOS, I would no longer try to install a Motorola stock firmware OTA. But, I think it is important to install bootloader, modem, oem, and vendor updates. Maybe this is the wrong procedure for an A/B device. It is simple to extract these files from Motorola stock firmware and use fastboot to flash them to the correct partitions on my phone. The G7 (river) is fairly new hardware and I expect Motorola to release software updates for some time to come.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] erfanoabdi:
we don't need oem and vendor updates

only modem and bootloader, and bootloader firmwares is super hard to take from zips
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] SyberHexen:
Thx will see about getting NFC working on your model
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] GamingHero:
I'm glad this device is not born dead and that the custom rom became official

---------- Post added at 07:04 PM ---------- Previous post was at 07:01 PM ----------

LOS 17 soon??
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] SyberHexen:
Likely, polishing 16.0 up first
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] floweredup:
Same experience with same phone from Amazon UK. The stock had NFC.

Thanks also for the work on this!
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] steba248:
I have a problem after trying to install LOS on my G7. I followed the guide on the lineageos wiki. I unlocked the bootloader, installed twrp and from there used adb sideload to flash the lineage image. Up to that point everything went fine. Next I wanted to flash gapps, so I executed step 7 in the guide and executed the "adb reboot sideload". The screen went black and the phone does not react to anything now.

These are the commands I executed in sequence:

$ fastboot devices

ZY225F3SRQ fastboot

$ fastboot flash boot twrp-3.3.1-2-river.img

target reported max download size of 536870912 bytes

sending 'boot_a' (27096 KB)...

OKAY [ 1.104s]

writing 'boot_a'...

(bootloader) Image not signed or corrupt

OKAY [ 0.166s]

finished. total time: 1.270s

At this point I booted into twrp, executed steps 3-5.

$ adb sideload lineage-16.0-20191128-nightly-river-signed.zip

Total xfer: 1.00x

$ adb reboot sideload

The reaction on the phone was a black screen and the phone does not react anymore. I tried holding power button pressed for long time, also vol down + power. Any idea what happened here or how I can bring the phone back to live?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] KyBoi1128:
yes!!! your instructions are the ones to follow, all others lead to no avail....A big THANK YOU for posting these steps:good::good::good:
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] weaponG:
Instructions for TWRP and LineageOS Install

I am ready to buy a Moto G7 and flash TWRP and LineageOS onto the device. I don't need Gapps or Magisk. Are the instructions on the LineageOS website below correct?

https://wiki.lineageos.org/devices/river/install
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] floweredup:
I would read through this thread and what people did. The a and b slots are fiddly.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Ratzinc:
Stuck on the lineage bootup screen.

I unlocked my bootloader, installed twrp (although it flashes lineageos bootloader).

installed the partition zip, then tried to install the official nightly and it threw up an error code (7? I think?)

Installed the newest unofficial

swapped partition to b since a tells me I have no OS on a

swapped to B and now it just stays on the lineage bootscreen.

What did I do wrong? Trying to flash the official releases errors out saying that the zip isn't signed correctly on 2 of the newest releases, and the unofficial release won't boot all the way.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] tommytomato123:
I think i ran in to the same issue. You probably should do a "blankflash". Then you can get back in to the bootloader.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] :
xt1962-6, unable to set bluetooth triger profiles and (no) NFC crashes spaming logs

Successfully installed 16.0-20191204-NIGHTLY-river and then OTA updated to 16.0-20191206-NIGHTLY-river on xt1962-6. Mostly w Working. However, whenever I try to set a bluetooth trigger on profiles, the settings (profile) app crashes.

Note while examining the logcat, I see it is being spammed with crash reports related to NFC (the xt1962-6 is a dual sim device but AFAIK does not have a NFC chip).

EDIT: issues fixed on 4.9.203-perf+ #1 SMP PREEMPT Sun Dec 8 23:13:54 UTC 2019 build. Thank you.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] dlfuller:
Google Assistant Voice Input not Working

I recently clean flashed lineage-16.0-20191203-nightly-river-signed.zip. Thanks, it's great.

But now Access with Voice Match cannot be enabled. It goes through the Google Assistant device setup but toggles that setting off.

Any possibility this is a ROM issue? I've tried all of the Google recommended troubleshooting steps.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] omino:
I installed the lineage-16.0-20191201-nightly-river-signed.zip build (latest one at the time of the flashing) successfully, then updated it to the December 6 update through the Updater. Everything went well.

Now I am trying to update to a more recent build (December 8 or December 10) via Updater. I can download the build and install it. Then, on reboot, the device boots up the December 6 build, not the new one. I guess something went wrong but I am not sure how to identify what.

Does anyone have an idea? Other than that, this rom rocks!

Thanks.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] :
This also happened for me. I was able to boot the next build by using twrp (i.e. fastboot boot twrp-*river.img ) to boot the new updated image - for me this was slot b. I haven't tried again to see if this issue is an artifact or if there is something I am missing as well.

[MENTION=6298645]erfanoabdi[/MENTION] do you want bug reports specific to river on xda? I'm preparing several, but the most immediate is system profiles related (again) and likely not river specific.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] ptn107:
Same back on 20191125 -> 20191128 i had to manually go into fastboot and change slots to the updated one.

fastboot --set-active=<slot>
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] omino:
Ok, that seems to be easy enough. In case something goes wrong with booting the new build, I guess I can simply change it back to the previous slot with the same command (different slot ofc), correct?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] ptn107:
yup
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] omino:
Switching slot worked perfectly. Thanks for your help!
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] rudolfm:
In the first Post, you suggest to install copypartitions.zip. Could you please write when (at which point in the process) and how (I assume with twrp) this is to be done. Someone new to this device cannot know this, and needs clear instructions. Trial and error isn't good if error gives me a brick.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Droid4200:
LineageOS not working with DJI

Hi, I got a Motorola g7 a while ago and wanted to install Lineage to get all the apps off that come with the phone. I installed DJI Go 4 (drone app) the app itself seems to run, but when I plugged the remote in to the OTG on the phone, it reads the remote wrong , says its for a model I dont have plugged in and wants to download the wrong software. I gave up and put Stock moto g7 back on and it works fine. Does anyone know what I can do to run DJI OTG with lineageOS?

Thank you,
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Phalanx7621:
Anytime. You only do it once, he's saying make sure you do it before installing Lineage because of having to switch slots and boot back into TWRP recovery.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] ptn107:
Anyone updating LOS monthly FYI the December security patch is included in the next build.

https://download.lineageos.org/river/changes/
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] SyberHexen:
This should be fixed in the new official builds starting at the 12.10.2019 build.

For reporting bugs please use

https://wiki.lineageos.org/bugreport-howto.html
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] ptn107:
What's the procedure to dirty flash this device (since it's a/b) boot recovery on the opposite (inactive) slot and flash so it installs to the right place?

ex: So I have LOS on 'b' and I can dirty flash from 'a' recovery and it will install to 'b' like a clean flash?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] crypysmoker:
So I got a weird problem. Ive been using the updater in the rom to do what I thought was updating nightlies. Till I started to get errors constantly with either downloading or installing the updates. Then I see it was still on 11/26 build. I then tried to reboot into twrp but got the lineage recovery. Then, I find out that my phone is re-encrypted. I had to revert back to stock because when I finally got 12/10 installed with temp booting twrp I got google services crash. Ill reinstall this tomorrow when I have the couple hours to argue with it not installing again lol But, YEah... Just a weird problem I encountered while using the built in updater.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] droidsometimes:
Not really. Just embrace the true nature of a/b. Use it what it's made for. ;)

(I assume 'recovery' = TWRP?)
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Ratzinc:
Thanks for the help everyone, sold it on craigslist after flashing back to stock.W
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] :
ota update slot not changing after reboot regression

EDIT: fixed in #1473

ota updating to 12.10.2019 the slot did change automatically after reboot

ota updating to 12.12.2019 from 12.10.2019 (observed toast message saying successful update before reboot) but after reboot still on 12.10.2019.

after:

(p380.ob) [105] $ fastboot getvar current-slot
current-slot: a
(p380.ob) [113] $ fastboot --set-active=b
Setting current slot to 'b' OKAY [ 0.187s]
Finished. Total time: 0.189s

the device booted into 12.12.2019

on a related note, I have not been able to locate ota update logs.

I found

constexpr const char* LOG_FILE = "/cache/recovery/log"

in otautil/logging.cpp. However, I find no such file after the update to 12.12.2019 (cache was not wiped during the update as I still see a file present in this directory before the update). Perhaps I need to activate ota logging, ota logging is broken, or this is just outdated/not applicable.

Any clues about finding (or enabling) OTA update logs?