[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Life_goes_on:
I did finally got a stable RR ROM. I went of mostly of the instructions but went a little off of them also. This is what I learned which may help people, but realize this is n1.

On my SD card I had copy-partitions-payton.zip, RR ROM.zip, Open Gapps.zip, the correct Twrp image and zip. My Migrate Backup.

I had multiple failures installing the RR ROM. I would get it up and running but it would crash and stop after installing any Open Gapps. I had been using XT1955-2_OCEAN_RETLA_SS_9.0_PPOS29.114-134-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml stock firmware which could be my main reason. Do not use.

I wiped Dalvik/Art Cache, Data, Internal Storage, System. Did Not wipe Micro SD card (all files I needed were on it) and USB-OTG. This gave me a clean internal storage.

The stock firmware I used that was successful was XT1955-2_OCEAN_RETAR_9.0_PPOS29.114-134-4_cid50_subsidy-DEFAULT_regulatory-XT1955-2-ARGENTINA_CFC.xml in the RETAR folder from lolinet. This should be good for any International Model many sold from Amazon.

Put all the stock firmware files and the twrp.img file, which I renamed to twrp.img, in the same folder on your computer as the adb and fastboot files. Open CMD or PowerShell window in that folder (online instructions as to how). The PowerShell is easier as it allows copy/paste.

I fastboot the stockfirmware pretty much the same that TheLastAlphaUK has posted, except for the first line. All Motorola G7 have a flashfile.xml that if you open it, it tells you exactly the order and how to fastboot the file. The lines in the file look look like this:

<step operation="getvar" var="max-sparse-size"/>

Or

<step MD5="38890d25dfb4e786c3a288c2aefd1162" filename="boot.img" operation="flash" partition="boot"/>

You just have to rearrange the command to: fastboot ‘operation command’ ‘partition location’ ‘filename’

fastboot getvar max-sparse-size

fastboot oem fb_mode_set

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot flash modem NON-HLOS.bin

fastboot flash fsg fsg.mbn

fastboot erase modemst1

fastboot erase modemst2

fastboot flash dsp adspso.bin

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash dtbo dtbo.img

fastboot flash system system.img_sparsechunk.0

fastboot flash system system.img_sparsechunk.1

fastboot flash system system.img_sparsechunk.2

fastboot flash system system.img_sparsechunk.3

fastboot flash system system.img_sparsechunk.4

fastboot flash system system.img_sparsechunk.5

fastboot flash system system.img_sparsechunk.6

fastboot flash system system.img_sparsechunk.7

fastboot flash system system.img_sparsechunk.8

fastboot flash system system.img_sparsechunk.9

fastboot flash system_b system_b.img_sparsechunk.0

fastboot flash system_b system_b.img_sparsechunk.1

fastboot flash system_b system_b.img_sparsechunk.2

fastboot flash vendor vendor.img_sparsechunk.0

fastboot flash vendor vendor.img_sparsechunk.1

fastboot flash oem oem.img

fastboot flash oem_b oem_other.img

fastboot erase userdata

fastboot erase DDR

fastboot oem fb_mode_clear

fastboot reboot-bootloader

This will put the stock system in slot A

Then I went off script and booted the stock system in slot _a up to the beginning menu did nothing else but poweroff.

Then bootloader (hold power+volume down buttons)

Back on original instructions:

fastboot set_active a

fastboot reboot-bootloader

sleep 5

fastboot getvar max-sparse-size

fastboot oem fb_mode_set

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot reboot-bootloader

sleep 5

fastboot flash modem_a NON-HLOS.bin

fastboot flash fsg_a fsg.mbn

fastboot flash dsp_a adspso.bin

fastboot flash logo_a logo.bin

fastboot flash boot_a boot.img

fastboot flash dtbo_a dtbo.img

fastboot flash vendor_a vendor.img_sparsechunk.0

fastboot flash vendor_a vendor.img_sparsechunk.1

fastboot flash vendor_a vendor.img_sparsechunk.2

fastboot flash vendor_b vendor.img_sparsechunk.0

fastboot flash vendor_b vendor.img_sparsechunk.1

fastboot flash vendor_b vendor.img_sparsechunk.2

fastboot flash oem_a oem.img

fastboot flash oem_b oem.img

fastboot oem fb_mode_clear

fastboot reboot-bootloader

Except “vendor.img_sparsechunk.2” does not exist in any Moto G7 Power Stock ROM that I could find. You can skip or put in the fastboot command for “vendor.img_sparsechunk.2” but it will do nothing but give you an error message.

You can also fastboot any custom logo.bin to hide the bad key. I have my own, which looks like a normal Motorola logo bootup to make everything not look custom.

Then on original instructions: In terminal CMD or Powershell on your computer temporarily install twrp.img "fastboot boot twrp.img"

Boot to recovery Twrp

Off script I did what linux suggested in a previous post: In twrp Reboot>Picked Slot B> Back> Wipe> , did the factory reset option before installing the RR ROM.

Then Reboot switch back to Slot A.

Installed copy-partitions-payton.zip while in slot a

Twrp>Reboot>Bootloader

In terminal CMD or Powershell on your computer temporarily, install twrp.img "fastboot boot twrp.img".

Boot to recovery Twrp

Twrp Installed RR ROM.zip from SD card while in slot a

In Twrp permanently install twrp.zip file from SD card

Twrp Reboot picked slot_b

Reboot> Bootloader

In the rebooted bootloader you need to do: fastboot -w and/or fastboot erase userdata before starting the RR ROM.

If you get a RR startup logo that goes for sometime, you will probably eventually boot to a Lineage OS recovery. Use the up, down and power buttons to get to factory reset. The reset should get you to boot into RR the next time. You can then go back and reinstall Twrp permanently again . Why did the Twrp recovery disappear and get replace? Do not know. Thanks Seniorween.

I started RR ROM a few times before installing magisk or open gapps.

You do not have to do this: I also went off script and rebooted back into twrp switched to slot a and reboot system into the stock ROM and that booted up to start. I got a message saying something to the effect changes made may make the system unstable and require a factory rest. I ignored this message and powered off.

Booted into recovery Twrp switched to slot b in recovery and rebooted to bootloader.

You need to do: fastboot -w and/or fastboot erase userdata before starting RR ROM.

Started RR ROM no problems.

End of you do not need to do this. Informational purposes only.

Back in twrp I installed magisk.zip and open gapps. RR ROM stable on startup.

You may need to do "Format Data" in TWRP slot b and rebooted to RR ROM after installing magisk.zip and open gapps. Info: Cybertom3000 post. I think these small tweaks people may need to do are based on the stock firmware they start with or some small variation they may have inadvertently made.

I did have a problem with magisk showing that the system rooted (green checks) and root checkers showed rooted, but Migrate or other root apps were not getting root access. Tried many things, but what worked was: I uninstall magisk. Reboot to RR ROM. Then boot into twrp, switch to slot a, install magisk.zip, switch to slot b, install magisk.zip. Interesting both installs of magisk said they were installing in slot b at the beginning of the script. Rebooted to RR ROM and all apps had roots access.

Everything is working fine.