[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Pay_It_Forward_Pete:
Unnecessary Wasted Energy

Excited to get this ROM working but am getting stuck. I have an ocean XT1955-5 M3DE6 retail US that I first updated to the latest OTA. Then I unlocked the bootloader no problem and then started out just wanting to install TWRP like I'd normally done on all my Nexus/Pixel devices. Booted twrp-3.3.1-2-ocean.img fine and flashed twrp-installer-3.3.1-2-ocean.zip.

I then moved on to CrDroid since I've had good experiences with crDroid ROMs in the past. Saw the instruction to flash copypartitions.zip first. Cringe. That is omitted from the TWRP instruction page for ocean.

I went ahead and flashed copypartitions.zip at that point in the hopes I wasn't already hosed. Then I followed all the CrDroid flash instruction sequence precisely. Booting the img. Confirmed on slot A. Wiped data, dalvik, system, internal storage, then formatting userdata. Then flashing crDroidAndroid-10.0-20200412-ocean-v6.5.zip and twrp-installer-3.3.1-2-ocean.zip. Rebooting to recovery and installing open_gapps-arm64-10.0-pico-20200530.zip.

Unfortunately, the outcome was the handset presenting the 5 second logo screen twice, then booting to TWRP every time with no touch function but ADB would work fine. Given the TWRP instructions omitting copypartitions.zip I thought I'd just start over from stock and precisely followed the instructions [URL="https://xdaforums.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138”] HERE[/URL] to flash XT1955-5_OCEAN_RETUS_9.0_PPOS29.114-134-13 (The May 2020 stock ROM from Lolinet). Doing so the handset booted and ran the stock rom no problem. I didn't re-lock the bootloader.

Then I started over executing the crDroid instructions precisely again (this time running copypartitions.zip before twrp-installer-3.3.1-2-ocean.zip. Everything went as expected. On reboot I was presented with cannot load Android with the retry boot/reformat options. I selected retry boot, yet once again the end result was the handset presenting the 5 second logo screen twice, then booting to TWRP every time with no touch function. I repeated booting the handset and noticed that on the 3rd or 4th boot of TWRP that touch mysteriously worked so I checked was slot I was on. I was on slot B. I switched to slot A and rebooted. Same 5 second logo screen twice, then booted to TWRP without touch function again. I rebooted seven more times and mysteriously touch function resumed again and again TWRP showed I was on slot B. My guess is the reason why I'm seeing the 5 second logo screen twice is because it's first trying slot A then trying slot B??

Logs Attached.

I now understand TWRP is buggy for this handset after its zip installer plus a ROM is installed. At that point not even booting the img works every time. However, touch in TWRP has always resumed with persistent boot attempts so I won't worry about that unless there's a TWRP programming problem that also impedes the successful flash of this ROM?? If so, let me know if there is another recovery I should use instead.

***EDIT*** Nevermind. Originally I'd only read the last page of this thread to see the latest discourse. However, as soon as I went back a couple pages to posts 113-119 it looks like I'm running into the same challenge as other users dating back to at least 10 days ago. (looks like what would work is described there instead of OP)

I'm sure the maintainer is a talented developer, put a ton of effort into this rom, and deserves far more gratitude then he receives.

However, what a bummer that instead the maintainer at least saying he'd look into what users indicate is presently necessary to successfully flash this rom, or he needs more contributors so he's able to keep up with the basics like the OP info (because no one else can amend the OP) . . . he's just telling people to kick rocks.

If unable to get around to looking into it for a week or two, he could have asked others to verify what was being shared and/or amended the OP with a disclaimer along with link to what recent users indicate is necessary to get this working. He's not even willing to amend the "known issues list" on the OP? Cringe.

Also, the maintainer posted deep in the thread a couple weeks ago "Official TWRP for this device has been buggy for a long time. It will freeze and lose touch." Yet the maintainer hasn't noted that in the OP?? To lessen confusion, it's reasonable to let users know to anticipate that may happen, and to just repeat TWRP boot attempts (installed TWRP, img, etc).

Given others upvotes letting the maintainer know amending the OP would save users a lot of wasted energy, I know I'm not alone. I imagine the maintainer is overextended. I sympathize with that. However, if despite common sense, and constructive feedback, he won't acknowledge there's opportunity to handle the OP information better, I and others will heed his words and "move on."