LineageOS 17.1 Keeps rebooting during initial setup screen unless USB cable is connected to computer

[freedomer]

I installed LineageOS 17.1 (12-22, 12-15, 12-08 with respective recoveries, all of which have the same results) on my brand new Moto G7 Plus and LineagOS gets to the setup screen and then a message says “Powering off, Shutting down….” and the phone reboots. LineageOS Recovery then loads and gives the “try again option” or “Factory data reset”. If I try again it boots to LineageOS setup screen then Powers off and reboots. If I Perform Factory data reset and format data it Powers off and reboots after the setup screen is shown. This continually happens. But If I keep my phone plugged into my laptop through the USB cable, it does not power off and reboot. But as soon as I unplug the USB cable the phone Powers off and reboots. The battery is at 100%. Anyone know why this is happening? Thanks for your help!

I purchased this phone directly from Motorola and it is not a T-Mobile phone. I successfully unlocked the bootloader at the Motorola website.

Phone original data before LineageOS install:
Model: Motorola Moto G7 Plus XT1965-T
Hardware version: pvt
Android Version: 10
Android security patch level: August 1, 2020
Kernel version: 4.4.192-perf+
#11 Tue Sep 29 19–13 CDT2020
Build number QW30.61-21-18-4
Software Channel: retla

 

[tsvortex]

I installed LineageOS 17.1 (12-22, 12-15, 12-08 with respective recoveries, all of which have the same results) on my brand new Moto G7 Plus and LineagOS gets to the setup screen and then a message says “Powering off, Shutting down….” and the phone reboots. LineageOS Recovery then loads and gives the “try again option” or “Factory data reset”. ...

Confirmed with the same issue here as well. I had started out with the 12-22 and then the 12-01 with the EXACT same result. I ended up falling back to the 11-24 image (as suggested in another thread) which allowed the phone to boot, acquire cellular service and work as expected. Something got borked in the later builds that's causing things to be broken for fresh loads. (I've yet to work up the courage to try the OTA)