yashsingh1/xdaforums huggingface dataset:
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] estofjlw:
Cannot be a reply to post 111 ???

This cannot be a reply to post 111 ???

I ran and still running crdroid9 and had no problems installing it at all

In this case the instructions of the OP post is wrong - in the instructions - and even [MENTION=7543015]Rondeau79[/MENTION] you say so as I point out in the post at 111.

I know how to flash a custom rom, but as others report TWRP locks up - and you cannot flash the gapps where the instruction say- because the system does not see Android 10 yet and it will report the gapps version 10 is the wrong one, and will let you install the wrong version 9 gapps. As you say Magisk cannot be installed also until after the first system boot - but the instructions are a cut and paste from the cRDroid 9 instructions

Further as [MENTION=2920715]cgrimm9[/MENTION] says - as quoted at post 45 at https://xdaforums.com/showpost.php?p=82230411&postcount=45 in actuality the only thing one can install is the ROM and then boot the system - or you will get a TWRP that is locked up and if gapps is installed it won't boot at all and as you say if Magisk is installed it won't boot either

So the OP instructions need to be modified - people need to deal with the included cRDroid recovery to get the rest installed using either the sdcard or adb sideloiad as the recovery provides for

I got it to boot but it has no data working through T-Mobile though I get the LTE served up - and it is not T-Mobile blocking anything as when I put the SIM back in my cRDroid 9 phone which was working but for the display - it comes right in and the Hotspot works with no problem

A similar issue in https://xdaforums.com/showpost.php?p=82124837&postcount=16 wherre Mobile Data is is not working and continuing at https://xdaforums.com/showpost.php?p=82135327&postcount=28 and at https://xdaforums.com/showpost.php?p=82230411&postcount=45 where cgrimm9 downgraded to and earlier version to get the data network to work.

So I will try to upgrade via dirty flash the latest version and see if that solves the data issue., because I am on 412 and I see there is a 423 version available directly to the server.

BUT . . . the OP instructions really need to be fixed to say install ONLY the ROM and do the rest through the crRDroid provided recovery because TWRP locks up. I booted twrp as an image and installed the copy partitions zip and was able to flash the ROM from the sdcard and wipe everything from both slots - but that is all - and I verified I was on slot A that way for all flashing.

So [MENTION=7543015]Rondeau79[/MENTION] if you are "obligated to provide proper instructions how to do so" on how to get this ROM installed then the OP instruction need to be completely overhauled.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Rondeau79:
The ROM install instructions are correct. Official TWRP for this device has been buggy for a long time. It will freeze and lose touch.

I do not developed TWRP for this device you would have to contact the developer on that project.

When I say the method used to flash this ROM is correct it is the truth.

There is no difference in flashing instructions between this ROM version vs CrDroid PIE for this device.

With the updated kernel source TWRP is running a lot better on this device. I maintain the ROM not the recovery.

Since CrDroid is based off of Lineage it automatically comes with Lineage recovery. That needs to be over written by flashing TWRP right after the ROM zip.

Then you need go manually reboot back into recovery where TWRP will switch the boot slot for you and then you can flash Gapps.

The A/B partitions layout has made it more complicated to flash ROMs.

If you run into issues on TWRP keep rebooting back into recovery and eventually it will work. But it should be good to go with the kernel source used in the ROM.

I follow the same procedure every time I flash on this device, it works.

You can always use another custom recovery if you choose.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Luiggi360:
I installed it this way, I do not ensure its functionality with another custom rom and I do not ensure its operation, at the moment this method has served me and I have it as daily use, no single error I have had for 3 weeks.

you take the risk

this was written in spanish and translated into google translator, any translation problem let me know.

need to have

adb files on pc

have crdroid 10 rom, magisk, opengapps and copy_partitions.zip on the phone's sd card

1-start in bootloader

2- connect phone to pc, "have adb folder on pc desktop, if you don't know what they are, google it". inside the adb folder we press shift and at the same time right click and select "open the powershell window here", IF YOU EXIT IN POWERSHELL, WRITE CMD and give enter TO WRITE THROUGH THE SYSTEM SYMBOL, type fastboot devices to see if you have recognized the device, if no code appears, install motorola drivers.

3-download twrp ocean and place it inside the desktop adb folder.

4-with the phone already recognized write FASTBOOT BOOT and after having made a space drag the TWRP file to the powershell window and press enter. You will be left with something like "fastboot boot c: /users/user1/desktop/adb/twrpocean.img." sin las comillas.

5- "SKIP THIS STEP IF YOU COME FROM ANOTHER CUSTOM ROM" within twrp, ONLY IF THEY COME FROM STOCK, they will install the folder where you have the copypartitions.zip and install, this will copy the partitions of the stock system.

6- after copying partitions, touch clean, touch format data and write yes if asked.

7- formatted we go and install crdroid.

8-installed we will format and then restart in bootloader.

9-already in bootloader, we go to the pc inside the powershell window and press the up arrow key to repeat the twrp start command line. "fastboot boot c: /users/user1/desktop/adb/twrpocean.img."

10- in twrp we are going to install gaps, I recommend the pico to avoid problems, optional we install magisk.

11- format data and right there we press restart system.

CAUTION: IT IS POSSIBLE THAT IT DOES NOT START THE FIRST TIME, BY THE SECOND YOU MAY GET THIS MESSAGE "CANT LOAD ANDROID OR SO"

there they give the option to format system, it will restart automatically and load the crdroid normally.

I hope it serves you, ask if you have doubts and I collaborate with you.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Rondeau79:
I have done all I can to help people. After a certain point it is up to them to figure things out.

If people want to use this ROM that is there choice.

There is a big FAT disclaimer at the beginning of the OP, if things go wrong or sideways I am not responsible.

Magisk does work, I have Gapps, Google account and pass safety net. Hide Magisk props works for safety net passing. Google has made it quite difficult for developers these days.

There are other custom recoveries available but I include the one I use in my OP.

My flashing instructions are not the only way to flash custom ROMs on the device, but it's the way I do it so I include them in the OP. If I included every other way in the OP it will only cause confusion and will only crowd the OP.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] estofjlw:
It is not about needing help . . .

I do not need help . . . I am trying to show exactly why there are all the posts doing it different ways because the instructions have issues - that make people have to "figure it out"

It is working as far as it is going to work - this ROM - because I think the last link I provided shows that Google has broken much of Magisk's code and hiding the unlocked device from them

I think there is something in the ROM and build.prop which is triggering SafetyNet on this version because PIE worked fine.

I do not know why the ro.build.fingerprint was set to google/coral/coral xxxxx and you did not say so so I have figured it out enough to know that you do not know either. I think until I can try a true moto android 10 ro.build.fingerprint key and security patch date it will not work on Safety Net.

Those build.prop files can cause serious trouble if not built to look like a true stock device. I got a Thunderbolt (MECHA) to work on 4.4 KitKat by making the build.prop look like 4.04 ICS stock.

This ROM is working for what I need it do - albeit crippled slightly though nothing has gone sideways . . . I will just never put a google account on it unless I fix this issue

If you count the posts saying or dealing with the same things I have said - you would see the problem

Thanks for a great ROM - down the road I will de-construct the problems and fix them - and oh yes the built in Android hotspot for me also did not work
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Rondeau79:
If you didn't need help and it wasn't an issue with the ROM then don't waste my time.

It was off topic, I don't have a lot of time to deal with other issues that really have nothing to do with the system issues. Those problems should be dealt with on a different thread.

I will not apologize for that! That is the way this device is. Clearly it was not a ROM problem.

I am fully aware of the hotspot issue, eventually it will get fixed.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] estofjlw:
I am sorry you cannot tell . . .

I am sorry you cannot tell when someone is trying to help YOU and this CAUSE.

If you were fully aware of the hotspot issue it should be listed at the OP page in this space below

Known issues:

<!-- list here -->

There is a problem with the ROM in the build.prop which caused eventually my IMEI to be blocked on that device. It has happened to others in both this and the version 9 forum also for reasons I have previously said in other posts

Android 10 is not rolled fully out yet on the Moto G7 Power and so the ROM did fail CTS Profile even when I got the basic integrity fixed for Safety Net and the ro.build.fingerprint really does not exist yet for the Moto G7 Power with Android 10. Using a google/coral/ xxxx fingerprint I do not see worked either, even though you say it does for your device.

I only paid $40 for the phone to set it up and test it so I will now find out if I can flash it back stock and re-lock the bootloader if it will clear the tower again.

I just ordered another one instead with an IMEI the tower has not flagged and so now I know what to do first and that you do not want any help in identifying issues others are running into - I will not post anymore what I discover. I have been doing this with phones and as a network engineer for many years - for quite a while - and simply put - for the reasons I have said - the instructions ARE wrong. At the very least as the software says - you cannot install gapps 10 on the phone when it still has a version 9 PIE - as an OS on it until it is rebooted.

No need to reply - I am sure you are busy . . . .
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] danny8:
I am a happy user of this ROM for months. I've upgraded a couple of times. Once or twice I've had a problem. I think it was my fault each time. I always figured it out.

Some of the advanced problems and solutions do not really belong in this thread. A carrier may have blocking motives that thwart you – mine does not. T-Mobile. I own a refurbished LG that was blocked by Metro PCS. I knew that before buying it. I won't waste my time trying to end-run around this. I'm happy to have found a ROM for that LG based on a newer version of Android. The LG is somewhat obscure and out-of-date. I'm happy it works.

It is the purview of the thread author to determine what goes in his original post.

Motorola sill haven't rolled out Android 10 to this phone as far as I know. Most of us here are running Android 10 / crDroid happily. I suspect most people have zero or few problems with the OP instructions. I can't prove this. But I would council anyone to research re-installing stock firmware before undertaking a ROM upgrade.

Please do not take my comment as an inducement for flaming on about the topic. I'm glad you resolved your issue and want to contribute.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] patate29284:
Does the Rom support MicroG?

---------- Post added at 12:23 AM ---------- Previous post was at 12:02 AM ----------

You know, I'm Chilean, and I've had many issues flashing different Roms for my Ocean device, mainly with instructions not working for me... I've come to the conclussion that there are some differences between devices, even though they appear to have the same model number. This because when I followed the tutorial to reflash stock Rom, there were some lines that didn't work for me. And then I came across a post of someone that had found the same thing, and he said that for flashing he had to do some extra booting into bootloader and twrp for roms to work. I've followed those instructions, which are basically what you've said, and that has worked for me, although not with every Rom.

Now, I'm trying to get this Rom going, but after flashing the Rom and starting it up, I went back to recovery (lineage recovery) to flash Gapps and Magisk and it bootlooped into bootloader... So now I'm going to flash it again, but this time, after starting up the Rom, I'll boot back into TWRP and flash Gapps and Magisk and see if it works this time.

Edit: The other thing I've noticed is that TWRP frozens only when I boot it with slot b as active, so I have to go back to bootloader and set_active a and then boot TWRP. After it boots, I have to manually turn to slot b to flash Gapps and Magisk.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] skodayeti:
Selfie kamera

Hello the Rom is ok

i am have install micro gapps but selfie kamera does not work

cann you help me please ?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Rondeau79:
Micro G is supported but it takes some work to get it going. I don't know much about Micro G so do some research.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Rondeau79:
The forward facing camera works depending on what camera app you are using, the issue might be there.

As far as the built in camera app it will work on the ROM. The only way to really figure the issue out is to flash a different version of Gapps and go from there. Or just flash the ROM and install without Gapps.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] xyzex:
where?

where is copy partitions zip? there is no info about it in OP post; is it the same as in instructions for PIE version?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] patate29284:
Thanks for the response... I just wanted to know if it works... I'll do my research to try it on, and if I get it going, I can post my steps in case anyone wants to try...

I got the Rom going last night, but I have an issue with Google Play Services (I flashed nano gapps). It has some compatibility issues with some apps I use (not everyday, but I use them) and I wasn't able to complete the Google set up (it crashes). However, I don't mind too much for those issues, since the device is still running smooth, but I'd like to try MicroG since I don't like Google services all over my device, gathering information and stuff.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Rondeau79:
Yes
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] arkansawdave74:
Me too. Seemed like a pretty sweet ROM, but I went back to crDroid 9. Can't handle low speakers. They're not quite loud in 9 either. Good enough though, usually.

---------- Post added at 08:51 PM ---------- Previous post was at 08:42 PM ----------

I had that problem in crDroid 9. Did you format data after the install? That's what fixed it for me. You probably already know but, in TWRP go to Wipe, then Format Data. you have to type "yes". I did that before 1st boot and made it through setup.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] patate29284:
Yes I did... As I said, I've had problems with other roms too, and I think it might be my variant, since no one else has come across the same issues...

By the way... How many hours of Screen On Time have you managed to get? In stock 9 I used to get around 12 - 14 hrs SoT, but now I'm getting 8.5 at most, with 2% remaining. I was used to having around 40% when going to sleep, but now it won't get that far on the day. It's not like it would be the endo of the world for me, since due to the efin quarantines I'm home all day and run wifi only, but if I have to get out, I don't think my battery will last too much. I'm guessing on LTE I won't get over 4 - 5 hrs of SoT (on stock I'd get 12 - 14 on wifi, but 8 - 8.5 on LTE)...
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] arkansawdave74:
Oops. double post.

---------- Post added at 04:49 AM ---------- Previous post was at 04:45 AM ----------

I can't tell you about 10 because I didn't run it very long, but on CR Droid 9 I get about 60% of what I did on stock 9. I'm used to a Galaxy S5 though which I had to carry around two extra batteries for everyday so I'm still happy with the battery life.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] danny8:
It sounds like you were real close to a successful flash.

From the tenor of your post, it's unclear if you are asking for help or throwing shade on the OP. If it's the former, best to avoid the later. You know: flys, vinegar, et cetera.

At least you can restore your phone to stock. You probably should have read or skimmed the entire thread -- all fourteen pages -- to get the gist of possible issues before commencing. (I plead guilty to not always doing this, so...) There are also ROM flashing procedures that involve USB / laptop connection explained in some of these posts. I only did this (USB ADB) back when Lineage OS was the only alternative ROM for this phone. And, um, once when I hosed my phone (mea culpa) and had to revert to stock.

I also get the five second delay every time I boot my device. That shows the warning message about bootloader being unlocked. And yes a further delay if it's booting on the wrong slot. But I've had to manually change the boot slot once or twice and that fixed it. I wonder if manually changing slots after flashing gapps and rebooting would have helped you.

For interested observers reading this post, it might be worth pointing out every upgrade flash switches your phone to boot from the opposite slot. It's best to just let this happen and not worry which slot it uses, as long as the phone boots OK.

I flashed different images (display images, AKA logo.bin) on slot A and slot B so I know which slot boots by simply looking at the phone. (This was done using ADB via laptop.) The boot image (display image) covers the text warning screen. That bootloader warning text annoys me, as does the five second delay. I guess I'm lucky that TWRP never failed to register touch for me. I'm running Orange Fox now and I like it.

I think this is where I got the logo files:

https://xdaforums.com/moto-g7/themes/custom-logo-bins-moto-g7-power-rid-root-t3967463

Realizing this does not fix your problem. Maybe try a different ROM if you can overcome your issues with TWRP.

Best of luck.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] arkansawdave74:
I feel your pain. I had countless fails from the instructions. Try formatting /data after the install, before 1st boot. I also use a dm-verity/force encryption killer zip myself before 1st boot to make TWRP restores work. I've not had install problems since implementing those unlisted steps. The dev is a good dude and helpful, even taking time to help in PMs for specific issues. Please forgive the lack of OP updates. That's not to say I don't think the OP should be updated. This is just a tricky phone.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
Heard that the dm verity thing causes problems I don't see how but I'm new to a b device's .I hear people can't get twrp to restore back up of stock ROM will this fix that problem makes since to me cause I had to do that on some a device's to get things done
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] danny8:
Just updated to crDroid 6.7 via dirty flash. All good.

[MENTION=7543015]Rondeau79[/MENTION], props!
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Johnfoo19:
Is colour saturation adjusment working in settings > display? Not working at all here
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] patate29284:
Did you get the "Trust" notification?

I just updated it and got a notification that reads "SELinux is not active, your security has been reduced" (Translated, cause I set it up in Spanish so it should read something like that). When I go to Settings, It shows SELinux as inactive and I can't set it either as Enforcing nor Permissive.

As I'm setting up my Google account right now, I'm also facing a problem with Google Play Services... It says that I need to give permission to access everything, but Storage permission won't get active. Though I tap on it and grant permission, it still goes under the "Rejected" category. I assume it's because SELinux is inactive.

The Rom is also asking for a Sim to be inserted, even though my Sim is actually in the slot.

I must say that I tried a clean flash, because I messed up the first time... So I had to reflash stock and do all over again...

I think I'll go back to April 22nd build, cause I had some crashes on the 23rd build too... I only used it for like a week, and it was my 1st build of this Rom, which I liked, but I think it was a little buggy (at least for me). Wanted to flash another build when I happened to see the notification for a newer build, so I figured I'd try it... I don't know if it's just me, or maybe my device, but it doesn't seem to work for me.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] danny8:
Yes, I got that notification also. I simply turned it off without addressing the underlying security issue. The switch is in

settings / privacy / trust / (switch near bottom)

I performed the steps in 'dirty flash': I flashed the ROM + recovery-installer (in my case, Orange Fox). Then I rebooted back to recovery and flashed gapps + magisk-installer.

I'm one of the lucky ones who does not have issues when the OP steps are followed.

In the past, I've failed to follow the steps, made it worse trying to correct, and ended up re-installing everything from scratch. This time apps, settings, and magisk+edxposed modules appeared without a hitch.

Not working for me either.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Rondeau79:
Don't use the latest TWRP, use 3.3.1 it has the recovery reboot fix.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] danny8:
I noticed the Orange Fox recovery I'm using (R1.4) is based on TWRP 3.3.1.