[Moto G Power Questions & Answers] Folcra:
I'm not having any success with getting Android 10 installed on my Moto G Power 2020 (Sofia). I've messed around with this device so much now that I'm worried it's irreparable.

After many failed attempts at installing custom ROMs, I found some info somewhere saying that I'd be more likely to find success if I started with Android 10. By this point I had wiped the OS off the phone entirely, so I used Lenovo's RSA tool to rescue to Android 11, which was successful. After this repair, my TWRP installation seems to have been replaced by fastbootd (which is what I seem to want, according to this thread). However, when I follow the various steps listed by users above and try to flash the Android 10 image I've downloaded, trying to boot to Android results in a bootloop. Interestingly, TWRP returns as my recovery software at this point. I have not yet successfully gotten this phone to boot Android 10.

Some things of note to future readers on Windows who have found this thread but are getting stuck while following the steps outlined by other users:

If following auhsoj200's instructions listed here, you may find it easier to extract your firmware files to the "Place_Extracted_Firmware_Here" folder than to the root folder. This way you won't have to paste files back and forth.

When they say to extract the Minimal ADB Fastboot files, you may be confused because the zip file you get from downloading Minimal ADB Fastboot doesn't have the necessary files for this installation, but rather has an executable file which will install these files for you, so extracting the zip doesn't get you very far. Extract them to wherever you want and then run the installer and point it to to the "Place_Extracted_Firmware_Here" folder. Don't let it make a new folder, have it install directly to this folder. This provides you with the needed files for running commands.

When running "2-rsd-flash-flashfile-windows.bat" you might get an error 'findstr' is not recognized as an internal or external command. In this case, you'll need to add your system32 folder to your path environment variable by going to environment variables (search in the start menu, System Properties will open, click "Environment Variables" at the bottom) and editing the "path" system variable, adding a new variable, and targeting "C:\WINDOWS\system32" (no quotes). If Windows is installed to a different drive, replace C as appropriate. The findstr function is used by this batch file to extract the file names from flashfile.xml, so if it's not recognized as a command your flashfile.bat will be constructed incompletely.

These notes are just meant to aid in troubleshooting, but as stated, even with these adjustments I haven't found any success. I've followed every different set of instructions I could find to a T, with and without my own listed changes. If anyone has any further suggestions I'd love to hear them. I think I've either done something during all of these installation attempts that is now blocking the downgrade, or else something has changed fairly recently with some of these softwares or steps that means this is downgrade is no longer possible.

Edit: Something else that may be important: whenever using TWRP, I'm prompted to give a passcode despite my device (when Android 11 is installed) not having a passcode. Nothing should be locked, but when I choose to cancel the passcode input I'm not able to perform wipes as desired and the internal storage appears to be encrypted. I can still access an external SD card without issue, which has been very useful for flashing other images. I think I've read that this encryption is a bug in some versions of TWRP, and since this release is unofficial (there is no official release for this model) I can't expect to find a version where I can get past this issue.