[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] estofjlw:
You confirm what I wrote

[MENTION=7543015]Rondeau79[/MENTION]

First let me this is a great ROM -cRDoid 9 worked well and this one on Android 10 is better as wifi can now switch between the 5 and 2.4 ghx bands, but I am sorry - every post in this forum thread tells you what I said - and as do you also admit. This ROM is ideal for Direct WIFI tethering behind a VPN so it is not monitored or throttled.

But there is a difference between the gapps install point going from PIE to 10 as an upgrade

Certainly TWRP is not your fault - but where it is buggy it should be dropped from being used formally

I - like almost every other poster here used TWRP to boot a twrp img, and then either did the copy partitions zip, wiping and flashing the ROM - and that where most of them stopped and used some other way to get around the problem coming behind the next steps where it freezes up. Even the poster after mine - though a bit wordy -at his steps 8 and 9 does the same thing I did. See https://xdaforums.com/showpost.php?p=82660297&postcount=115

The crdoid ROM install should be done with a sdcard with the needed files on it in the phone - but no SIM in the phone - for reasons a first boot may tell the carrier when it tries to negotiate the tower the bootloader is unlocked and could get the device blocked on some carriers. This really should part of the instructions for safety reason too.

I first following the instructions installed the ROM and TWRP, and where I rebooted to recovery - TWRP came back frozen, so booted it from the PC as an image again and when I went to install gapps from the sdcard - it FAILED saying the version - gapps 10 was incorrect. Of course it was incorrect - the crdroid android 10 ROM had not been actually booted into a working, operating functioning system OS

II is possible the poster at https://xdaforums.com/showpost.php?p=82106383&postcount=10 installed the wrong gapps version through TWRP as it seems it will let you

At that point it then it became obvious to re-flash the ROM - making sure I was on slot A and reboot this time immediately to system so as having destroyed the TWRP install on purpose.

cRDroid booted immediately - and then asked for a factory reset - which I did and it came up instantly.

At that point I went into settings and reset the developer options by clicking the build number the seven times - and a few other things so when I went to restart with the power button - I could go into the cRDoid recovery, where I could choose that same gapps file -which now installed (nano - 10) without error. I then followed that with Magisk

So the only difference is I side-stepped the buggy freeze ups of TWRP and ONLY this way below are the OP steps correct

ROM - Installation:

. . .

04. Flash ROM.zip ONLY (put ROM, TWRP-installer and gapps and Magisk in directory on sdcard first BEFORE starting install procedure)

05. Reboot > System - allow factory reset if prompted, and in new crdroid ROM- go to settings and re-enable developer status by clicking the build number, AND USB DEBUGGING then hold power button to choose restart to recovery, and in crdroid recovery use volume up or down to select and power key to activate selection

06 .Install Gapps + Magisk ( from sdcard - or adb sideload)

07. Reboot > System

Crdroid came right back up - quick, clean and requires no caffeine or head scratching.

This way there is no screwing around with TWRP and its buggy nature - and if one dares they can install TWRP by zip after this is complete.

So no . . . . including dealing with third party buggy software as a part of the install - especially without explicit warnings in the instructions - is NOT what one would call "correct". The correct thing to do is by-pass it or sternly warn it may not work if one takes that path.

Magisk "if you choose" with an unlocked bootloader - is also not correct. Carriers today who do not allow modified devices - some actively look for tampered with devices negotiating the tower to access the network and will block them from their Network, as their Terms of Service allow them to do so if that is what their terms say - for data access - and thus one is Sprint, and you see it in this forum also.

Magisk is NEEDED to even hope to hide the unlocked bootloader at boot . In fact Magisk may not be able to help much longer if one puts a Google Account on their phone. See https://www.xda-developers.com/magisk-no-longer-hide-bootloader-unlock-status/ Google shares info in their Carrier services app and other policies with carriers too.

My crdroid 9 version I got to pass Safety Net after some work - but this crdroid 10 version right now is two big red fails. I have not put a google account on the phone yet and will not until and if I pass Safety Net first. I disabled Carrier Services.

The build.prop file of this crdroid 10 is a bit messy. My ro.build.description is the first Moto 134 US Retail I flashed, but it went to 134-7-1 and I don't see that. The ro.build.fingerprint is google/coral/coral xxxxxxxxxx when it should be moto/ocean xxxxxx something and this with the build date - security patch date actually makes it fail Safety Net and raises red flags in general. Magisk Hide props config for the moto g7 pwer has changed and did not work - and I have not done investigation further yer

My carrier does not have stated TOS restrictions on modified devices - but only speaks to "modified devices which disrupt or affect the network", so after the third time I booted it with my SIM - it said "phone is starting up" and then I had working LTE+ - in essence "5G". I measured speed at 105 Mbps down and 33 Mbps up.

BUT that is only because the IMEI is recognized as a compatible device, and that along with a correct APN config is all that my carrier appears to need, so until I get the build.prop modded or magisk hide props config working - I am only half way there.

So asking people to be forced to deal with unexpected third party buggy software is not correct, and there is a gapps install order which is also an issue, as well as the Magisk install after first boot even you said.