[ROM][OFFICIAL][CrDroid][PIE]

Search This thread

Rondeau79

Senior Member
Jun 19, 2016
353
340

crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!

BE3pE0l.png

Features
Click for feature list (helps shorten the OP.)

Always Have a full functional Backup. Just in case!

DOWNLOAD ROM

*****Disclaimer*****
Important note before proceeding!!!
The copy A/B partions zip is crucial in order to prevent bricks. It only needs to be done if your coming from the stock ROM or you recently restored stock firmware manually. Other wise without it you can brick due to Motorola's A/B partition scheme.

Preparation for A/B Roms:
01. Download TWRP.
02. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
03. Unlock your bootloader
04. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
05. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmwares.)
06. While in TWRP choose Reboot > bootloader
07. Now you're ready for ROM Steps below

ROM - Installation:
01. Download the ROM.
02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
03. Wipe data, dalvik, system and internal storage, then format userdata.
04. Flash ROM.zip + TWRP_installer
05. Reboot > Recovery
06.Install Gapps + Magisk (if you choose)
07. Reboot > System

Updating (AKA 'dirty flash'):
01. Download the updated ROM
02. Boot into recovery
03. Install ROM.zip + TWRP_installer
04. Reboot > Recovery
05. flash gapps + Magisk (if you choose)
06. Reboot > System
Notes:
Any time your internal storage aka "Userdata" is from a stock install you must "format data" in recovery before using ROMS

Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.

KNOWN ISSUES
LIST-KNOWN-ISSUES-ON-YOUR-DEVICE-HERE
None

Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files

Thanks to:

- ENTER-SPECIFIC-THANKS-HERE-IF-YOU-HAVE-THEM
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )


Device tree: https://github.com/Rondeau79/android...motorola_ocean
Vendor tree: https://github.com/Rondeau79/proprie...g/lineage-16.0

Download Link: https://androidfilehost.com/?w=files&flid=302315
AB copy partitions Download Link: https://androidfilehost.com/?fid=4349826312261636295

XDA:DevDB Information
CrDroid Pie, ROM for the Moto G7 Power

Contributors
Rondeau79
Source Code: https://github.com/crdroidandroid/android/tree/9.0
Kernel tree:https://github.com/Rondeau79/android_kernel_motorola_sdm632/tree/lineage-16.0

ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest bootloader and TWRP recovery
Based On: Lineage OS

Version Information
Status: Stable
Current Stable Version: 5.11
Stable Release Date: 2019-11-25

Created 2019-11-27
Last Updated 2019-12-23​
 
Last edited:

Rondeau79

Senior Member
Jun 19, 2016
353
340
Reserved
 

Attachments

  • Screenshot_20191123-002610.jpg
    Screenshot_20191123-002610.jpg
    126.6 KB · Views: 4,964
  • Screenshot_20191123-002622.jpg
    Screenshot_20191123-002622.jpg
    252.9 KB · Views: 4,943
  • Screenshot_20191122-053437.jpg
    Screenshot_20191122-053437.jpg
    130.3 KB · Views: 4,909
  • Screenshot_20191122-053407.jpg
    Screenshot_20191122-053407.jpg
    171.8 KB · Views: 4,748
Last edited:

Gabe29

Member
May 6, 2019
5
2
Just installed the rom a couple of hours ago, and damn it's good! Only a small problem though, when you make a screenshot the little menu that appears where you can edit and take extended screenshots closes after a few seconds on its own. Is this intended or a bug? If so I hope you can fix it in the next update. Thanks a lot for the rom!
 

Rondeau79

Senior Member
Jun 19, 2016
353
340
Thank you Rom is really stable and beautiful plenty of customization baked in. Been running it for 4 days no problems at all OTA is also working great two updates already love it

Just installed the rom a couple of hours ago, and damn it's good! Only a small problem though, when you make a screenshot the little menu that appears where you can edit and take extended screenshots closes after a few seconds on its own. Is this intended or a bug? If so I hope you can fix it in the next update. Thanks a lot for the rom!

You can change the animation speeds in developer options to slow down that screenshot options. That will allow that edit page to stay on your screen longer.
 
  • Like
Reactions: sdmf1918 and Gabe29

Gabe29

Member
May 6, 2019
5
2
You can change the animation speeds in developer options to slow down that screenshot options. That will allow that edit page to stay on your screen longer.

I see, I set the duration scale to 0.5x so no wonder it closed so fast. Anyways is there a way to make opengl skia the default gpu renderer? Because it switches back to default after a reboot.
 

joefidler

Member
Sep 27, 2007
44
14
As it is getting regular updates I though I would give this ROM a try on my new G7 Power. To be honest it works much better than I expected, not seeing any stability problems and it has some nice features. Still testing, but will probably start using this ROM + phone as my daily.

I did however have a heck of a time installing and getting both the ROM and TWRP to boot on the phone. That mostly had nothing to do with this ROM and more to do with the A/B partitions thingy Google has done on recent phones (which I have grown to hate). Also the ROM's install instructions are a bit vague in parts, so there was a bit of a learning curve (for me at least).

One the upside everything I have tested so far works. Storage encryption is enabled by default and working, wifi works (even with hidden SSIDs), dual SIMS works, camera app works, fingerprint works , call quality seems good. SELinux is disabled, which is not good but I can live with.

A big thanks for the all the done work on this!!
 

Rondeau79

Senior Member
Jun 19, 2016
353
340
As it is getting regular updates I though I would give this ROM a try on my new G7 Power. To be honest it works much better than I expected, not seeing any stability problems and it has some nice features. Still testing, but will probably start using this ROM + phone as my daily.

I did however have a heck of a time installing and getting both the ROM and TWRP to boot on the phone. That mostly had nothing to do with this ROM and more to do with the A/B partitions thingy Google has done on recent phones (which I have grown to hate). Also the ROM's install instructions are a bit vague in parts, so there was a bit of a learning curve (for me at least).

One the upside everything I have tested so far works. Storage encryption is enabled by default and working, wifi works (even with hidden SSIDs), dual SIMS works, camera app works, fingerprint works , call quality seems good. SELinux is disabled, which is not good but I can live with.

A big thanks for the all the done work on this!!

Download terminal emulator
Su
setenforce 1
SeLinux will be enforcing
 
  • Like
Reactions: flug32
Dec 26, 2016
26
2
Hey @Rondeau79, thank you for the rom, this was actually the only one I was able to flash. (But I think the problem is on my side of the table ;)

Is there any way to get rid of the google-parts of the rom (searchbar etc.)? Thx in advance!
 

Rondeau79

Senior Member
Jun 19, 2016
353
340
Hey @Rondeau79, thank you for the rom, this was actually the only one I was able to flash. (But I think the problem is on my side of the table ;)

Is there any way to get rid of the google-parts of the rom (searchbar etc.)? Thx in advance!

The search bar is apart of the launcher, it is based off the Lawn chair launcher. You could always not flash Gapps and use Aptoide as store for apps..
 

jhjhjhjhjhjh

Senior Member
Mar 14, 2017
418
201
Thanks again for this port o.p
Ive tried all roms accept omni and this rom by far exceeds expectations. The Best Gaming Rom ive used.
I dont know what changes were made from the kernel between the 11/19 build and the 11/28 build. But I got better performance with the 11/19 kernel so i lm using the 11/19 build boot.img on the 11/28 rom update.
Battery drain is less noticeable on the latest build as the 11/19 build was draining very fast.
Once one roots this rom with a few tweaks, one will see a huge boost in performance.
Resurrection Remix was my daily driver prior because of the Led Notification light in which i love on this phone.
@Rondeau79 can the notification light get added to CRDroid like on RR and Aospex...?cOther than that no bugs to report.
You rock o.p..!!!
 

Attachments

  • Screenshot_20191204-023056.jpg
    Screenshot_20191204-023056.jpg
    123.7 KB · Views: 462
  • Screenshot_20191204-023123.jpg
    Screenshot_20191204-023123.jpg
    252.8 KB · Views: 458
  • Like
Reactions: twfs

Top Liked Posts

  • There are no posts matching your filters.
  • 21

    crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!

    BE3pE0l.png

    Features
    Click for feature list (helps shorten the OP.)

    Always Have a full functional Backup. Just in case!

    DOWNLOAD ROM

    *****Disclaimer*****
    Important note before proceeding!!!
    The copy A/B partions zip is crucial in order to prevent bricks. It only needs to be done if your coming from the stock ROM or you recently restored stock firmware manually. Other wise without it you can brick due to Motorola's A/B partition scheme.

    Preparation for A/B Roms:
    01. Download TWRP.
    02. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
    03. Unlock your bootloader
    04. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
    05. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmwares.)
    06. While in TWRP choose Reboot > bootloader
    07. Now you're ready for ROM Steps below

    ROM - Installation:
    01. Download the ROM.
    02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
    03. Wipe data, dalvik, system and internal storage, then format userdata.
    04. Flash ROM.zip + TWRP_installer
    05. Reboot > Recovery
    06.Install Gapps + Magisk (if you choose)
    07. Reboot > System

    Updating (AKA 'dirty flash'):
    01. Download the updated ROM
    02. Boot into recovery
    03. Install ROM.zip + TWRP_installer
    04. Reboot > Recovery
    05. flash gapps + Magisk (if you choose)
    06. Reboot > System
    Notes:
    Any time your internal storage aka "Userdata" is from a stock install you must "format data" in recovery before using ROMS

    Upgrading from earlier version of crDroid:
    The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.

    KNOWN ISSUES
    LIST-KNOWN-ISSUES-ON-YOUR-DEVICE-HERE
    None

    Don't expect any support if you:
    - are not running the included kernel
    - have installed any mods such as Xposed!
    - have modified system files

    Thanks to:

    - ENTER-SPECIFIC-THANKS-HERE-IF-YOU-HAVE-THEM
    - Google
    - LineageOS
    - SlimRoms
    - AOSPA (Paranoid Android)
    - OmniRom
    - NamelessROM
    - Many others... (if you're feeling upset being out of the thanks list just send a PM )


    Device tree: https://github.com/Rondeau79/android...motorola_ocean
    Vendor tree: https://github.com/Rondeau79/proprie...g/lineage-16.0

    Download Link: https://androidfilehost.com/?w=files&flid=302315
    AB copy partitions Download Link: https://androidfilehost.com/?fid=4349826312261636295

    XDA:DevDB Information
    CrDroid Pie, ROM for the Moto G7 Power

    Contributors
    Rondeau79
    Source Code: https://github.com/crdroidandroid/android/tree/9.0
    Kernel tree:https://github.com/Rondeau79/android_kernel_motorola_sdm632/tree/lineage-16.0

    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 4.x
    ROM Firmware Required: Latest bootloader and TWRP recovery
    Based On: Lineage OS

    Version Information
    Status: Stable
    Current Stable Version: 5.11
    Stable Release Date: 2019-11-25

    Created 2019-11-27
    Last Updated 2019-12-23​
    9
    Thanks! I run it as my daily driver. My first official ROM! I have built plenty in the past, but decided to make the jump. As soon as a few bugs get straighten out I will be moving it to Android 10!
    5
    Like so many other users here, I've been having a difficult time getting this ROM installed and working. If I follow the instructions above exactly as written, when I reboot to the system at step #06, the original stock Moto ROM is loaded again and no sign whatsoever that I ever installed the CrDroid ROM.

    There are no issues or errors when I perform any of the above steps. I've verified I'm on Slot A and installed copypartitions.zip with no error; then rebooted to bootloader; then loaded TWRP again with the fastboot command; installed crDroidAndroid-9.0-20191223-ocean-v5.11.zip and TWRP; rebooted to recovery; installed Gapps (pico) and Magisk v20.1; rebooted to system and my phone loads the stock Moto ROM.

    I have also attempted to use the different instructions provided by the OP in post #31. These instructions include the following new steps:
    3. Wipe system, data, internal storage and cache
    4. Format data under wipe>advanced>format data

    Whenever I have followed these instructions and rebooted to the system, it directly loads TWRP instead of any ROM.

    I have attempted to install multiple times using both sets of instructions and results are consistently the same. Double and triple checked my work each step of the way and I am not doing anything that's contrary to what the instructions are which have been provided. If I am reading the first post, then I follow those instructions to the letter. If I am reading the instructions as provided in post #31, I am also following those instructions to the letter. I have also re-downloaded all the files to make sure I hadn't received any faulty or damaged files originally.

    In addition, after each failed install, I return to the stock Moto ROM (XT1955-5_OCEAN_RETUS_9.0_PPOS29.114-134-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) using the RSD Lite tool and start each install from a fresh ROM with no Google account details entered into the phone (I install the stock ROM and then immediately power off before any type of setup and power back on in bootloader state).

    If anyone could provide any helpful feedback, it would be most welcome. I'm completely at a loss as to what I could try next.

    By the way, I was able to successfully install the Resurrection Remix ROM using the instructions provided with it and had no problems whatsoever. It loads and operates just fine. I would probably be willing to use that as my daily driver, but I would like the opportunity to give CrDroid a try first if I could ever figure out a way to install it.

    Cheers and Happy New Year all, Amy

    These are the steps I used to get it working. Remove the microSD card from your phone as it will not be needed and might cause bootloops.

    1) Extract stock rom to ADB folder and follow these steps from the command prompt to go 100% back to stock

    fastboot set_active a
    fastboot reboot-bootloader
    fastboot getvar max-sparse-size
    fastboot oem fb_mode_set
    fastboot flash partition gpt.bin
    fastboot flash bootloader bootloader.img
    fastboot flash modem NON-HLOS.bin
    fastboot flash fsg fsg.mbn
    fastboot erase modemst1
    fastboot erase modemst2
    fastboot flash dsp adspso.bin
    fastboot flash logo logo.bin
    fastboot flash boot boot.img
    fastboot flash dtbo dtbo.img
    fastboot flash system system.img_sparsechunk.0
    fastboot flash system system.img_sparsechunk.1
    fastboot flash system system.img_sparsechunk.2
    fastboot flash system system.img_sparsechunk.3
    fastboot flash system system.img_sparsechunk.4
    fastboot flash system system.img_sparsechunk.5
    fastboot flash system system.img_sparsechunk.6
    fastboot flash system system.img_sparsechunk.7
    fastboot flash system system.img_sparsechunk.8
    fastboot flash system system.img_sparsechunk.9
    fastboot flash system_b system_b.img_sparsechunk.0
    fastboot flash system_b system_b.img_sparsechunk.1
    fastboot flash system_b system_b.img_sparsechunk.2
    fastboot flash vendor vendor.img_sparsechunk.0
    fastboot flash vendor vendor.img_sparsechunk.1
    fastboot flash oem oem.img
    fastboot flash oem_b oem_other.img
    fastboot erase userdata
    fastboot erase DDR
    fastboot oem fb_mode_clear
    fastboot reboot-bootloader

    Boot system to welcome screen to verify clean flash.

    2) Power down system and boot to bootloader (Vol down + Power). Follow these steps to get the system ready for copy-partitions. (Note: some steps are redundant and/or will give errors, disregard these errors)

    fastboot set_active a
    fastboot reboot-bootloader
    fastboot getvar max-sparse-size
    fastboot oem fb_mode_set
    fastboot flash partition gpt.bin
    fastboot flash bootloader bootloader.img
    fastboot reboot-bootloader
    fastboot flash modem_a NON-HLOS.bin
    fastboot flash fsg_a fsg.mbn
    fastboot flash dsp_a adspso.bin
    fastboot flash logo_a logo.bin
    fastboot flash boot_a boot.img
    fastboot flash dtbo_a dtbo.img
    fastboot flash vendor_a vendor.img_sparsechunk.0
    fastboot flash vendor_a vendor.img_sparsechunk.1
    fastboot flash vendor_a vendor.img_sparsechunk.2
    fastboot flash vendor_b vendor.img_sparsechunk.0
    fastboot flash vendor_b vendor.img_sparsechunk.1
    fastboot flash vendor_b vendor.img_sparsechunk.2
    fastboot flash oem_a oem.img
    fastboot flash oem_b oem.img
    fastboot oem fb_mode_clear
    fastboot reboot-bootloader

    3) Download TWRP image and put it in your ADB folder, rename to twrp.img

    4) Boot into recovery by using the following command:
    fastboot boot twrp.img

    5) Once in TWRP, we'll wipe slot B as we'll be installing the ROM there. To do that, from the TWRP menu:

    Select 'Reboot'
    Select 'Slot B'
    Hit 'Back'
    Verify it says 'Current Slot: B'
    Hit the back arrow
    Select 'Wipe'
    Select 'Advanced Wipe'
    Select 'Dalvik / ART Cache' 'Data' & 'System'
    Swipe to wipe
    Once wiped, return to the TWRP main menu
    Select 'Reboot'
    Select 'Slot A'
    Hit 'Back'
    Verify it says 'Current Slot: A'
    Hit the back arrow

    6) Now we're ready to flash the copy-partitions.zip.

    Copy that file to your adb folder and rename it 'copy-partitions.zip'

    From the TWRP main menu:
    Select 'Advanced'
    Select 'ADB Sideload'
    Swipe to start sideload

    From the command prompt type:
    adb sideload copy-partitions.zip

    Once it's done flashing return to the TWRP main menu, select 'Reboot' and select 'Bootloader'

    7) Now we're ready to flash the rom and twrp recovery. Copy the desired rom and TWRP zip file to your ADB folder. Rename TWRP to 'twrp.zip' From the bootloader, boot to TWRP using:
    fastboot boot twrp.img

    In the TWRP main menu:
    Select 'Advanced'
    Select 'ADB Sideload'
    Swipe to start sideload

    From the command prompt type:
    adb sideload nameofrom.zip (replace nameofrom.zip with the name of the rom you're flashing)

    Once it's done flashing we need to flash twrp.zip using the same method
    In the TWRP main menu:
    Select 'Advanced'
    Select 'ADB Sideload'
    Swipe to start sideload

    From the command prompt type:
    adb sideload twrp.zip

    8) Don't reboot the system quite yet. The rom and recovery should now be flashed, but we need to wipe userdata in order for the rom to boot. Return to TWRP main menu:

    Select 'Reboot'
    Select 'Slot B'
    Hit 'Back'
    Verify it says 'Current Slot: B'
    Select 'Bootloader'

    You should now be back from the bootloader. From the command prompt type:
    fastboot erase userdata
    fastboot reboot

    Your system will boot to your Rom.

    Optional) To install gapps/magisk:

    Turn the phone off & reboot to bootloader
    Select recovery mode.
    Phone will boot to recovery. Copy gapps and magisk to adb folder

    In the TWRP main menu:
    Select 'Advanced'
    Select 'ADB Sideload'
    Swipe to start sideload

    From the command prompt type:
    adb sideload gapps.zip (replace gapps.zip with name of gapps)

    Return to the ADB sideload menu. Swipe to start sideload

    From the command prompt type:
    adb sideload magisk.zip (replace magisk.zip with name of magisk)

    Reboot the system

    Done!
    5
    Thanks again for this port o.p
    Ive tried all roms accept omni and this rom by far exceeds expectations. The Best Gaming Rom ive used.
    I dont know what changes were made from the kernel between the 11/19 build and the 11/28 build. But I got better performance with the 11/19 kernel so i lm using the 11/19 build boot.img on the 11/28 rom update.
    Battery drain is less noticeable on the latest build as the 11/19 build was draining very fast.
    Once one roots this rom with a few tweaks, one will see a huge boost in performance.
    Resurrection Remix was my daily driver prior because of the Led Notification light in which i love on this phone.
    @Rondeau79 can the notification light get added to CRDroid like on RR and Aospex...?cOther than that no bugs to report.
    You rock o.p..!!!

    I will look into a light Hal fix. As CrDroid PiE is stable and up and running the updates will come in small fixes and security patches. I am working on bring up CrDroid ten for this device, but it will take a good amount of time.